Enables a IBM Session Manager Sysplex group name to be specified.
This parameter is applicable to the SYSTEM control statement (see SYSTEM statement).
SYSPLEXGroup xxxx
GLOBALMessages Yes|No|ON|OFF
LINKTRace Yes|No|ON|OFF
LINKNEtctl Yes|No|ON|OFF
LOGSTREAMName logstreamname
PSTIMER pstimer
STANDBYTaketime standbytaketime
USERStructure Yes|No|ON|OFF
WAITFORCntltime waitforcntltime
xxxx is the 1 to 4 character IBM Session Manager Sysplex group suffix. The name will be prefixed with ISM to form a Sysplex group name of ISMxxxx.
If a SYSPLEXGroup is specified on start-up the IBM Session Manager instance will join this group. If a number of other IBM Session Manager instances specify the same group name, they will automatically connect to each other using the z/OS XCF (syspleX Coupling Facility) mechanism.
Note: Each IBM Session Manager instance must be in the same Sysplex, either in the same instance of z/OS or other z/OS instances.
In a Sysplex environment where the multiple IBM Session Manager instances are assigned to the same SYSPLEXGroup it is mandatory that all the IBM Session Manager instances must share the same configuration data sets. Also any given SYSPLEXGroup must not have a mix of Classic and OLA IBM Session Manager instances.
If the group name is altered through an Update or Pupdate or in OLA then the change will have no effect but message 499 will be issued. To implement the change IBM Session Manager must be recycled.
Subparameters under the SYSPLEXGROUP parameter are:
Controls the scope of all broadcasts and messages sent with the BROADCAST and MESSAGE commands. If GLOBALMessages has been set to (or defaults to) YES or ON, then broadcasts and messages will be distributed across the Sysplex. For example, if a BROADCAST was issued in one IBM Session Manager instance the command would be sent to all IBM Session Manager instances in the same Sysplex group. By specifying GLOBALMessages NO or OFF the broadcasts and messages are restricted to the issuer's instance.
If GLOBALMessages YES or ON is in effect then a script or panel can set the variable t_global_msg to N for a task, and any subsequent BROADCAST or MESSAGE command issued on the task will cause the message to be restricted to the issuer's instance. Setting t_global_msg to Y sets the scope of further BROADCAST and MESSAGE commands issued on the task to the GLOBALMessages setting.
LINKTRace Yes|No|ON|OFF
LINKNEtctl Yes|No|ON|OFF
The LINKTRace and LINKNEtctl subparameters can be specified if your local representative requires a trace of all Sysplex links. See 'TRACE LINK administrator command' in the Technical Reference manual.
Is a 1 to 26 character name which corresponds to the z/OS system logger log stream defined by an installation, to capture audit messages across a Sysplex group. If the LOGSTREAMNAME subparameter is not specified then IBM Session Manager will not store audit messages on a common Sysplex log that can be viewed by any instance in the group.
Specifies the time, in seconds, that data required for session recovery will be retained by VTAM after a IBM Session Manager Controller failure. The value can be 1 to 32767. Default 120.
Note: For application sessions specified with a recovery level of High, IBM Session Manager utilizes the VTAM Multi Node Persistent Sessions (MNPS) facility.
STANDBYTaketime standbytaketime
Is the time, in seconds, that the IBM Session Manager Standby Controller will wait before assuming the role of the IBM Session Manager Controller, if the Sysplex Controller is not active. The value can be 0 to 32767 (no default).
Used to switch off the Coupling Facility User List structure. The default is Yes which means that by default, if SYSPLEXGroup is specified, IBM Session Manager will maintain a User List structure, to be accessed by all IBM Session Manager instances in the Sysplex group. The structure ensures all users having VTAM-connected terminals can reconnect to their disconnected sessions.
Note: This mechanism replaces the "Sample sign-on validation exit script (E21)" used in previous releases (see 'Parallel Sysplex support' in the Installation and Customization manual). The structure is also used to support the SPLXLOCUSER TPSL function (see Panels, Scripts and Variables manual).
WAITFORCntltime waitforcntltime
Used when running in an environment which has been configured for application recovery. The value can be 0 to 32767. Default 60. Here, the IBM Session Manager instance will, during its initialization, ask the Controller to identify whether there are any open ACBs that are in the instance's RANGE tables.
An instance's ACBs can be open either if the instance was the subject of a SWITCHPLX command or if the instance failed and its Standby had taken over its RECOVERYLevel ACBs and sessions. If the instance is unable to contact the Controller within the WAITFORCntltime then the instance concludes that the Controller has yet to be started and therefore none of the ACBs will be in use.
The WAITFORCntltime time should be sufficient to allow the network session between the instance and the Controller to become active. If the Controller has not started then the instance initialization will be suspended for the WAITFORCntltime before finalizing its initialization.