There are several ways to start a CMAS.
You can start a CMAS:
To use this method:
The START command to be included is described in START command for a CMAS.
To start a CMAS from the system console:
To start a CMAS as a batch job:
No matter which method you use to start a CMAS, be sure to verify that the procedure references the appropriate:
A sample procedure that you can use to start a CMAS is supplied in the member EYUCMAS. 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.
You must create the data sets for this CICS region. JCL to create the CICS region data sets for the CMAS is supplied in member EYUDFHDS of CICSTS31.CPSM.XEYUINST. This member was generated when you ran the EYUISTAR job.
Figure 56 illustrates segments of the EYUCMAS procedure that are unique to CICSPlex SM.
//EYUCMAS PROC DSNCSD=CICSTS31.CPSM.DFHCSD, CSD Data Set name
// DSNTBL=CICSTS31.CPSM.RGNLOAD, CICS Table Module library
// RGNHLQ=CICSTS31.CPSM, CICS Region DSN qualifier
// CICSPRM=EYUCnnI0, CICS Parameters
// CPSMPRM=EYUCMS0P CPSM Parameters
//*
//CICS EXEC PGM=EYU9XECS, CMAS Startup program
// PARM='SYSIN', CICS Parameters location
// REGION=0K Region Size
//*
//STEPLIB DD DISP=SHR,DSN=CICSTS31.CPSM.SEYUAUTH
// DD DISP=SHR,DSN=CICSTS31.CPSM.CICS.SDFHAUTH
//DFHRPL DD DISP=SHR,DSN=CICSTS31.CPSM.SEYULOAD
// DD DISP=SHR,DSN=CICSTS31.CPSM.CICS.SDFHLOAD
// DD DISP=SHR,DSN=&DSNTBL
·
·
·
//EYULOG DD SYSOUT=*
//DFHJ25A DD DISP=SHR,DSN=CICSTS31.CPSM.SDFHJ25A
//DFHJ25B DD DISP=SHR,DSN=CICSTS31.CPSM.SDFHJ25B
·
·
·
//EYUDREP DD DISP=SHR,DSN=CICSTS31.CPSM.EYUDREP.cmasname
//EYUPARM DD DISP=SHR,DSN=CICSTS31.CPSM.SEYUPARM(&CPSMPRM)
//BBACTDEF DD DISP=SHR,DSN=CICSTS31.CPSM.SEYUADEF
//BBVDEF DD DISP=SHR,DSN=CICSTS31.CPSM.SEYUVDEF
//BBIPARM DD DISP=SHR,DSN=CICSTS31.CPSM.EYUIPRM
Review the following statements in the sample JCL that are illustrated in Figure 56. Verify that the JCL has been modified so that the:
You should not include application load libraries in the DFHRPL concatenation.
When you are using a sequential data set for the EYULOG, allocate 3 primary cylinders and 1 secondary cylinder.
Member EYUCMS0P, in the CICSTS31.CPSM.SEYUPARM data set, contains sample parameters for a CMAS; this member must be edited. (See CICSPlex SM system parameters for a detailed description of each parameter.)
When the CMAS is to connect to a MAS for which security is active (the CICS SIT parameter for the MAS is SEC=YES), the CMAS must have CICSPlex SM security active. When CICSPlex SM security is not activated in the CMAS, the connection between the CMAS and the MAS cannot be established. If this is attempted, the following message is issued to the console, the CMAS joblog, and the CMAS EYULOG:
EYUCR0007E Security mismatch between CMAS cmasname and
MAS masname. Connection terminating.
To activate CICSPlex SM security in the CMAS, you must specify the CICSPlex SM system parameter SEC(YES). The default is SEC(NO). (For more information about the SEC parameter, see CICSPlex SM system parameters.) Specifying SEC=YES in the CICS SIT parameters for the CMAS does not affect CICSPlex SM security.
The CICSTS31.CPSM.SEYUPARM library contains CICS system initialization table (SIT) parameters that should be included in the sequential data set or partitioned data set member EYUC64I0 as identified by the CICS SYSIN statement.
Table 22 identifies the CMAS-related CICS SIT parameters.
Parameter | Your value | Explanation |
---|---|---|
AIEXIT=DFHZATDX | VTAM® terminal autoinstall program. | |
APPLID= | * | VTAM application ID for this CICS, which is acting as a CMAS. Used as CMAS name when NAME(value) is not specified as a CICSPlex SM system parameter. |
![]() ![]() |
![]() ![]() |
![]() ![]() |
AUXTR=ON | Auxiliary trace - Exception records. | |
AUXTRSW=ALL | Continuous auxiliary trace switching. | |
CICSSVC=216 | * | CICS SVC installed in LPA. |
CPSMCONN=CMAS | Initialize this region as a CMAS | |
DFLTUSER= | * | Non-CESN RACF® user Id. |
DSALIM=4M | Limit of DSA storage below 16MB. | |
DUMPDS=A | * | Transaction dump data set. |
DUMPSW=NEXT | * | Switch to next transaction dump data set. |
EDSALIM=100M | Limit of EDSA storage above 16MB.This is a minimum initial value. See Controlling CICS storage in a CMAS for additional information. | |
FCT=NO | No File control table. | |
GMTEXT='CICSPlex SM / ESA' | * | Default logon message. |
GRPLIST=EYU310L0 | CSD group list having group EYU310G0. See Updating the CSD files using DFHCSDUP (CMAS) for additional information. | |
ICV=100 | Region exit interval. | |
ICVR=20000 | Runaway task interval.
Note:
For
a CMAS running on a small processor and having a large number of resources
defined through BAS, this value may need to be increased to about 90000. |
|
ICVTSD=1 | Terminal scan delay interval. | |
INTTR=ON | Activate main storage trace. | |
IRCSTRT=YES | IRC started at system initialization. | |
ISC=YES | Load programs required for interregion or intersystem communications during initialization. | |
MXT=300 | Maximum tasks to exist.This is a minimum initial value. See Controlling CICS storage in a CMAS for additional information. | |
RENTPGM=PROTECT | Specifies that CICS will allocate ERDSA from readonly key 0 protected storage. | |
SEC=
{YES|NO} |
![]() The CICS external security checking SIT option can be specified in the normal way, along with the other CICS security related options (for example, XTRAN and XCMD). CICS command or resource security is not appropriate in a CMAS. The XTRAN SIT option is typically used to control access to the various CICSPlex SM transactions used in a CMAS. For more information, see CICS RACF Security Guide. Note:
No CICSPlex SM supplied
transaction definitions have CMDSEC=YES or RESSEC=YES. If this definition
is changed, or the CMDSEC=ALWAYS or RESSEC=ALWAYS SIT parameters are set in
a CMAS, and a CICSPlex SM transaction receives a NOTAUTH response, results
are unpredictable. ![]() |
|
SIT=6$ | System initialization table suffix. | |
SPOOL=YES | System spooling interface. Required when you are going to use the CICSPlex SM batched repository-update facility. | |
START=AUTO | You can normally specify START=AUTO and let CICS initialization decide the type of start to perform.
The first time you start a CMAS, ensure the CICS global and local catalog data sets are newly initialized. Use DFHRMUTL and DFHCCUTL respectively, with AUTOINIT on the SET_AUTO_START parameter of DFHRMUTL. This makes sure that the CMAS performs an initial start, which installs the necessary CICS resource definitions and establishes CMAS-to-CMAS connections. Subsequently, you can manipulate the type of start for a CMAS by resetting the global catalog data set, using DFHRMUTL to specify either AUTOINT or AUTOCOLD. For more information, see Restarting a CMAS. |
|
STGPROT=NO | No storage protection. | |
SUBTSKS=1 | Use additional concurrent mode TCB. | |
SYSIDNT= | * | CICS System Id.
Note:
The SYSIDNT
value must match the EYU9XDUT SYSID parameter value used to initialize the data repository
being referenced by the EYUDREP DD statement. |
SYSTR=OFF | No system activity trace. | |
TCT=NO | No TCT needed. | |
TRANISO=NO | No transaction isolation. | |
TRTABSZ=2048 | Kilobytes for trace table. | |
TS=COLD | Cold start temporary storage. | |
TST=NO | No temporary storage table required. | |
USERTR=ON | Enable user trace facility. | |
WRKAREA=2048 | Bytes for Common Work Area. | |
XRF=NO | No XRF support.
Note:
The extended recovery facility (XRF)
is not supported because of the way in which a CMAS uses MVS data spaces. |
Many operations within a CMAS are achieved by multiple asynchronous tasks. This is especially true of operations that are performed between CMASs in a CMAS network, such as data repository synchronisation, workload management state sharing and single system image. Any of these operations, and others, can result in a number of interdependent asynchronous tasks being established or used to execute the request. The number of tasks that can be used is based on other factors, such as the size of a CMAS network, how many MASs are being managed, how many CICSplexes are defined, how much API activity is performed, the scope of EUI/WUI/API/RTA requests and so on for all the major functionality offered by CPSM.
Even though a CMAS can self regulate its tasking model and has tolerance of delayed requests and responses through timeout mechanisms, MXT is a concept that is not applicable to controlling an interdependent multitasked asynchronous tasking model. Set inappropriately, you may also experience EUI and WUI hang' for long durations if one or more of the asynchronous tasks required to execute the requested function are delayed waiting for an MXT slot. It is therefore strongly recommended that MXT should be set to avoid any delays in task attachment.
As task usage within a CMAS grows with the additional requirements that are placed upon it, such as but not limited to, increased use of the API, more CMASs, more MAS's, new function use, and so on, you should set the MXT value to a level that continues to avoid MXT delays.
It is recommended that you monitor any MXT value for its relationship against the task activity within each CMAS at regular intervals. If the CMAS is starting to experience MXT delays, you should adjust the MXT value to avoid these delays.
To monitor the tasking activity within an individual CMAS, it is recommended that you collect and study the statistics generated by the CICS system that underlies the CMAS that it hosts. CICS transaction manager global statistics contain information on the effect the MXT value has on task attachment. For more information and guidance on using CICS statistics see the CICS Performance Guide.
A CMAS is a special application dedicated to the task of managing and controlling MASs. Even though a CMAS does this with an atypical tasking model and with extensive use of MVS dataspace storage, it still has major uses of the storage provided by the CICS system that hosts the CMAS. With an interdependent multitasked asynchronous tasking model there is a reliance on shared storage to perform the communication between the tasks and the functions being performed. Also, according to the requirements that are placed upon a CMAS, there is a large reliance on shared storage to perform the buffering of requests and responses to be transmitted via CMAS to CMAS and CMAS to MAS links. The shared storage to support such operational characteristics is managed by the CICS system that hosts the CMAS.
As CICS storage usage within a CMAS grows with the additional requirements that are placed upon it, such as, increased use of the API, more CMASs, more MASs, increased CMAS to CMAS network traffic and new function use,you should set the EDSALIM value to a level that provides the CMAS with the amount of storage it needs to perform its operations unimpeded. CMAS to CMAS and CMAS to MAS network traffic, in particular, is critical to EUI and WUI response times because large amounts of data may be awaiting shipment on any of the links that a CMAS communicates on
It is recommended that you monitor any EDSALIM value for its effect on the storage usage within each CMAS at regular intervals. If the CMAS is experiencing short on storage (SOS) or storage fragmentation or trending towards such conditions, you should consider increasing the EDSALIM value to meet the storage requirements of the CMAS. Storage fragmentation below a largest free area of 64KB will begin to adversely effect throughput and response times.
To monitor the storage usage within an individual CMAS, it is recommended that you collect and study the statistics generated by the CICS system that underlies the CMAS that it hosts. CICS storage manager global statistics contain information on the overall usage of CICS storage by the CMAS that it hosts. For more information and guidance on using CICS Statistics see the CICS Performance Guide.
The syntax of the command you can use to start a CMAS is:
START procname [,DSNCSD=dsn][,DSNTBL=dsn][,RGNHLQ=idx]
[,CICSPRM=mem][,CPSMPRM=mem]
where:
The EYUINST EXEC parameter CINDEX establishes the high-level qualifier that is used with CICS data sets that are shared between systems.