There are several ways you can start a CAS. You can start a CAS:
This is the recommended method for starting a CAS. To use this method:
To start a CAS from the system console:
To start a CAS as a batch job:
A sample procedure that you can use to start a CAS is supplied in the member EYUCAS and is illustrated in Figure 55. This member was generated when you ran the EYUISTAR job, as described in Generating post-installation members. The member is stored in the library you specified on the LIB parameter of the EYUISTAR job.
//EYUCAS PROC SSID=CPSM, MVS/ESA Subsystem ID
// XDM=N, Extended diagnostic mode
// SPCF=N,CONVXCF=N, SysPlex Coupling Facility
// COLD=N, Cold start option
// DUMP=ALL Capture all dumps
//*
//CPSMCAS EXEC PGM=BBM9ZA00,
// PARM=('SSID=&SSID,XDM=&XDM,SPCF=&SPCF,CONVXCF=&CONVXCF'
// 'COLD=&COLD,DUMP=&DUMP'),
// TIME=1440,
// REGION=4096K
//*
//STEPLIB DD DISP=SHR,DSN=CICSTS31.CPSM.SEYUAUTH
//BBACTDEF DD DISP=SHR,DSN=CICSTS31.CPSM.SEYUADEF
//BBVDEF DD DISP=SHR,DSN=CICSTS31.CPSM.SEYUVDEF
//BBIPARM DD DISP=SHR,DSN=CICSTS31.CPSM.EYUIPRM
//BBSECURE DD DISP=SHR,DSN=CICSTS31.CPSM.SEYUPARM
//*
The syntax of the command you can use to start a CAS is:
START procname [,SSID=ssid][,XDM=Y|N] [,SPCF=Y|N][,CONVXCF=Y|N]
[,COLD=Y|N][,DUMP=Y|N|ALL]
where:
The distributed sample startup JCL uses CPSM as the default subsystem identifier. (EYUX is used as the subsystem identifier for the Environment Services System Services (ESSS) and, therefore, cannot be used as a CAS subsystem ID.)
Make sure that you use this subsystem ID with the CASNAME parameter, described in topic CASNAME(name).
If your enterprise has more than one CAS, make sure your TSO users know the subsystem ID of each CAS. In the Subsystem ID field on the Session Control Parameters panel, they can specify a different CAS than the one they first connect to. (The Session Control Parameters panel is described in the CICSPlex System Manager User Interface Guide)
XDM, which is described in the CICSPlex System Manager Problem Determination manual, should be activated only when requested by IBM® Support Personnel. Specifying XDM=Y disables certain error recovery mechanisms and issues extensive diagnostic messages to the console.
When the CAS is initialized, several control blocks are built in common storage. Most of these blocks are freed when the CAS terminates. However, some blocks (with a total of less than 4KB of CSA) are retained to permit the reuse of previously allocated system resources--in particular, MVS system linkage indexes (LXs).
When you reinitialize the CAS with COLD=N, the control blocks from the preceding invocation of the CAS are used--rather than building new ones--and, thus, do not consume additional common storage or valuable LXs. By contrast, COLD=Y causes new control blocks to be built. This means that all previously built control blocks continue to occupy common storage until the system is IPLed.
Specify COLD=Y only when requested to do so by IBM Support Personnel in an attempt to clear an error condition.
When DUMP=ALL is in effect, an SDUMP is attempted for all unexpected abends.
If you specify DUMP=Y, the recovery manager attempts to take an SDUMP only when the failing function is running in supervisor state. If you specify DUMP=N, the recovery manager does not take an SDUMP for any abend, regardless of the PSW state at the time of the failure.
The first time a user accesses CICSPlex SM, CPSM is used as the default CAS subsystem ID. If this is not the appropriate subsystem ID, the user’s profile must be changed. To do this, the user must select option 0 from the CICSPlex SM entry panel. Then select suboption 1 and change CPSM to the appropriate subsystem ID.
When the user displays the CICSPlex SM entry panel, the names of the context and scope that are to be in effect for the user’s CICSPlex SM session are shown. When the user selects either option 1 or 2, CICSPlex SM establishes connection between the CAS and the CMAS responsible for managing the CICSplex identified as the context.
If, after a CAS connection has been established, the user decides to use option 0.1 to identify a different CAS, the user must use the END command to exit ISPF to FREE the current BBILINK allocations. From the TSO READY prompt, the user must restart the CICSPlex SM session in order to establish a connection to the new CAS.
[[ Contents Previous Page | Next Page Index ]]