SET CORBASERVER

Set various attributes of a specified CorbaServer.

Read syntax diagramSkip visual syntax diagramSET CORBASERVER
 
>>-SET CORBASERVER(data-value)--+-------------------+----------->
                                +-AUTOPUBLISH(cvda)-+
                                +-AUTOPUB-----------+
                                '-NOAUTO------------'
 
>--+--------------------+--+--------------------------+--------><
   +-ENABLESTATUS(cvda)-+  '-SESSBEANTIME(data-value)-'
   +-ENABLED------------+
   '-DISABLED-----------'
 

Conditions: INVREQ, NOTAUTH, NOTFND

For more information about the use of CVDAs, see CICS-value data areas (CVDAs).

Description

The SET CORBASERVER command allows you to:

Options

AUTOPUBLISH(cvda)
specifies whether the contents of a deployed JAR file should be automatically published to the namespace when the DJAR definition is successfully installed into this CorbaServer.
NOAUTO
The contents of the deployed JAR file will not be automatically published to the namespace.
AUTOPUB
The contents of the deployed JAR file will be automatically published to the namespace.

Changing the setting of AUTOPUBLISH affects only DJAR definitions installed after the SET CORBASERVER command is executed. It has no effect on previously-installed DJAR definitions.

CORBASERVER(data-value)
specifies the 4-character name of a CorbaServer.
ENABLESTATUS(cvda)
specifies whether to enable or disable the CorbaServer. CVDA values are:
DISABLED
The CorbaServer is to be disabled.

In a CICS region containing multiple CorbaServers, putting one of the CorbaServers into disabled state allows you to apply maintenance to it without bringing down CICS; the other CorbaServers remain available.

Similarly, in a logical EJB/CORBA server containing multiple AORs (each containing multiple CorbaServers), putting a CorbaServer on one of the AORs into disabled state allows you to apply maintenance to the CorbaServer without needing to remove the AOR from the routing set.

You can disable a CorbaServer that is in any state except ENABLING or DISCARDING. When you do so, any currently-executing methods are allowed to continue to completion. Until all its objects have been destroyed or passivated, the CorbaServer enters DISABLING state. Note that:

  • Any instance of an enterprise bean or CORBA stateless object that is not participating in an OTS transaction is destroyed or passivated at the end of the currently-executing method.
  • Any instance of an enterprise bean or CORBA stateless object that is participating in an OTS transaction is not destroyed or passivated until the end of the OTS transaction; typically, any future method calls against this instance (within the scope of the OTS transaction) will succeed. At the end of the OTS transaction, the instance is destroyed or passivated.

If the workload manager directs new work to an AOR in which the target CorbaServer is in DISABLING or DISABLED state, it is informed that the CorbaServer is disabled.

Note:
By "new work" we mean:
  • Requests for methods that will run under a new OTS transaction. (By a "new" OTS transaction we mean an OTS transaction in which none of the AORs in the logical server is already participating, prior to the method call; not necessarily an OTS transaction that is started immediately before or after the method call.)
  • Requests for methods that will run under no OTS transaction.
ENABLED
The CorbaServer is to be enabled. You can enable a CorbaServer that is in any state except DISABLING or DISCARDING.
SESSBEANTIME(data-area)
Fullword area containing the elapsed time period in minutes, in the range 0 through 143999 (99 days, 23 hours, 59 minutes), of inactivity after which a session bean may be discarded. A value of 0 indicates that beans are not timed out.

The new timeout value applies only to session beans created after the SESSBEANTIME value has been set. It does not affect existing session beans.

Conditions

INVREQ
RESP2 values
4
The specified session bean timeout value is invalid.
15
An attempt was made to enable or disable a CorbaServer that is in an invalid state.
21
Object store error.
NOTAUTH
RESP2 values:
100
The user associated with the issuing task is not authorized to use this command.
NOTFND
RESP2 values:
2
The specified CorbaServer was not found.
[[ Contents Previous Page | Next Page Index ]]