PERFORM CORBASERVER

Perform certain actions against a specified CorbaServer.

Read syntax diagramSkip visual syntax diagramPERFORM CORBASERVER
 
>>-PERFORM --CORBASERVER(data-value)--+--------------+---------><
                                      +-ACTION(cvda)-+
                                      +-PUBLISH------+
                                      +-RETRACT------+
                                      '-SCAN---------'
 

Conditions: DUPRES, INVREQ, NOTAUTH, NOTFND

Description

The PERFORM CORBASERVER command allows you to:

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.

Options

CORBASERVER(data-value)
specifies the 4-character name of a CorbaServer.
ACTION(cvda)
returns a CVDA value indicating the action to be taken on the CorbaServer. CVDA values are:
PUBLISH
publish all the beans installed in the CorbaServer. Publishing a bean means binding a reference to the home of each bean in a 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 Interoperable Object Reference (GenFacIOR) of the CorbaServer is also bound in the namespace in the same way.

RETRACT
retract all the beans installed in the CorbaServer. Retracting a bean means unbinding a reference to the home of the bean from 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 GenFacIOR of the CorbaServer is also unbound.

SCAN
scan the CorbaServer’s deployed JAR file directory (also known as the pickup directory) for new or updated deployed JAR files.

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.

Notes:
  1. CICS ignores any deployed JAR files in the pickup directory that have the same name and the same date and time stamps as currently-installed DJAR resources. A deployed JAR file with the same name but a later date-and-time stamp than an installed DJAR is treated as an update.
  2. An error in installing one deployed JAR file has no effect on the success or failure of installing any others in the deployed JAR file directory.

Conditions

DUPRES
RESP2 values:
29
During a scan, one or more deployed JAR files failed to install due to a DJAR naming conflict. This error can occur for two reasons:
  1. The name of a DJAR definition created by the scanning mechanism conflicts with that of a previously-installed dynamic definition that targets a different CorbaServer. The scanned-in definition cannot be treated as an update, because the installed definition refers to a different CorbaServer.
  2. The name of a DJAR definition created by the scanning mechanism conflicts with that of a statically-installed definition. You cannot use the scanning mechanism to update a static DJAR definition.

To avoid this error:

  1. If your CICS region contains multiple CorbaServers, use a different pickup directory for each CorbaServer.
  2. Do not place identically-named deployed JAR files into multiple pickup directories in the same CICS region.
  3. If you use static DJAR definitions, do not give them names that might conflict with those created by the scanning mechanism.

For more information about DJAR naming conflicts and how to avoid them, see the CICS® Resource Definition Guide.

INVREQ
RESP2 values:
5
The specified CVDA value is invalid; that is, it is neither PUBLISH, RETRACT, nor SCAN.
9
The state of the CorbaServer is not ENABLED.
10
At least one deployed JAR file belonging to the CorbaServer is in a state other than INSERVICE.
13
CorbaServer publish error.
14
CorbaServer retract error.
25
CorbaServer scan error.
26
A scan of this CorbaServer’s deployed JAR file directory is already in progress.
27
The CorbaServer’s deployed JAR file directory (DJARDIR) could not be accessed.
NOTAUTH
RESP2 values:
100
The user associated with the issuing task is not authorized to use this command.
NOTFND
RESP2 values:
2
The named CorbaServer cannot be found.
[[ Contents Previous Page | Next Page Index ]]