Perform certain actions against a specified CorbaServer.
The PERFORM CORBASERVER command allows you to:
Publishing a bean means binding a reference to the home of the bean in the namespace. The naming context in which the bean is bound is named, relative to the initial context defined for the CICS region, using a concatenation of the JNDI PREFIX attribute of the CorbaServer and the name of the bean.
The Generic factory is bound with the name GenericFactory concatenated to the PREFIX attribute of the Corbaserver.
If no action is specified, the command has no effect.
You can issue a PERFORM CORBASERVER command only when the CorbaServer is in a steady state--that is, when it is in ENABLED or DISABLED state, but not when it is in ENABLING, DISABLING, or DISCARDING state.
In addition to the traditional DFSMS-managed data sets, such as partitioned data sets (PDS), CICS requires access to z/OS® UNIX System Services and the hierarchical file store (HFS) in order to launch a JVM. This requires that the CICS region userid is authorized to z/OS UNIX System Services to enable CICS to access the required HFS directories, such as those specified on the JVMPROPS, LIBPATH, and CLASSPATH parameters.
The Generic Factory Interoperable Object Reference (GenFacIOR) of the CorbaServer is also bound in the namespace in the same way.
The GenFacIOR of the CorbaServer is also unbound.
If CICS finds any new deployed JAR files in the pickup directory, it copies them to its shelf directory and dynamically creates and installs DJAR definitions for them.
If CICS finds any updated deployed JAR files in the pickup directory, it updates both the LASTMODTIME, DATESTAMP, and TIMESTAMP attributes of the installed DJAR definitions and the shelf copies of the deployed JAR files.
To avoid this error:
For more information about DJAR naming conflicts and how to avoid them, see the CICS® Resource Definition Guide.