Example: Creating a basic CICSPlex SM CICSplex environment
This example provides sample JCLs that set up a basic CICSplex spanning multiple LPARs. The configuration of such a basic CICSplex involves setting up a CMAS on each LPAR and connecting them so that they can talk to each other. You can customize the sample JCLs to create your own CICSplex environments.
Note: This example is based on a simplified CICSplex topology with CICSPlex® SM components to help you get a grasp of
the basic concepts of CICSPlex SM
environments. The information contained within is provided for simplicity and ease of understanding
and may diverge from best practices. For example, the maintenance point CMAS created in this example
uses a CICS SYSIDNT value of CM01, whereas as best practise the maintenance point CMAS should use
the highest alphanumeric SYSIDNT value of any connected CMAS.
Scenario
Figure 1 gives you an overview of the topology of a CICSplex called PRODPLEX that spans two LPARs with application regions running on both LPARs.
The example CICSplex, PRODPLEX, spans two z/OS LPARs. Each LPAR has a CMAS region and a CICSPlex SM WUI server region. Each LPAR has a
number of CICS regions such as AORs, FORs, and so on. Key attributes of these regions are provided
in Table 1.
| Name | APPLID | SYSIDNT | Description |
|---|---|---|---|
| CMAS001 | CMAS001 | CM01 | The CMAS managing LPAR 1 CMAS001 is the maintenance point CMAS. |
| WUI001 | WUI001 | WU01 | The CICSPlex SM WUI server region in LPAR 1 |
| AOR001 | AOR001 | AOR1 | An AOR in LPAR 1 |
| CMAS002 | CMAS002 | CM02 | The CMAS managing LPAR 2 |
| WUI002 | WUI002 | WU02 | The CICSPlex SM WUI server region in LPAR 2 |
| FOR001 | FOR001 | FOR1 | An FOR in LPAR 2 |
The version of CICSPlex SM in this example assumes Version 6 Release 2.
About this task
The major steps to set up CICSplex PRODPLEX include:
- Specify the parameters that are related to CICSPlex SM for the DFHISTAR job.
- Create the data sets needed to run CMAS001, including its EYUDREP file.
- Create the data sets needed to run CMAS002, including its EYUDREP file.
- Define the connection from CMAS001 to CMAS002, and indicate that CMAS002 is going to help manage PRODPLEX.
- Define the connection from CMAS002 back to CMAS001.
- Run a batch job to define additional CICS regions such as TORs, AORs, FORs, and CICSPlex SM WUI servers, as needed.
When you set up a basic CICSplex like PRODPLEX, it can easily be extended across many more LPARs.
Procedure
- Step 1. Set up the CMAS region on LPAR 1
-
- Customize your CICS installation by setting DFHISTAR attributes specific to CICSPlex SM, and then run the DFHISTAR job. For
details, see Specifying attributes specific to CICSPlex SM. The following attributes match the sample
environment as shown in Figure 1.
If you have run DFHISTAR already, review the job and assess what was done. You can edit and re-run the DFHISTAR job multiple times.
Attribute Value Note CMASNAME CMAS001 CMSSYSID CM01 CSYSNAME AOR001 CSYSPLEX PRODPLEX NEWDREP-PREFIX . OLDDREP . TCPIPHST This attribute is deprecated. The value, if specified, is ignored. The hostname of the CICSPlex SM WUI server is the name of the host where the CICSPlex SM WUI is executing.
Check with your system programmer for the hostname and port to be used for your environment.
CMCIPORT 11111 Check with your system programmer. TCPIPPRT 22222 Check with your system programmer. TIMEZONE U See Time zone codes. WUI YES WUINAME WUI001 WUIPLEX PRODPLEX WUISYSID WU01 - Edit and run the EYUCMSDS postinstallation job.
One of the customized jobs produced by DFHISTAR is EYUCMSDS. This job creates the necessary data sets to run a CMAS. The first three steps in that job (see Figure 2) delete, define and initialize the EYUDREP file for CMAS001. The EYUDREP file is the CICSPlex SM data repository file where a CMAS keeps all of its information. One EYUDREP file is required for each CMAS. They should not be shared.
It is important that the EYUDREP file never run out of space. Note that in Figure 2 the space is specified as
CYL(100,50).Figure 2. Extract of the EYUCMSDS job for CMAS001 //DELDREP EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSIN DD * DELETE EXAMPLE.CMAS001.EYUDREP SET MAXCC=0 //DEFDREP EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSIN DD * DEFINE CLUSTER - (NAME(EXAMPLE.CMAS001.EYUDREP) - CYL(100,50) - CISZ(8192) - RECSZ(200,6550) - KEYS(64,0) - SHR(2) - INDEXED - SPEED - REUSE) /* //*************************************************** //DREPINIT EXEC PGM=EYU9XDUT, // COND=(8,LT), // PARM=('CMASNAME=CMAS001', // 'DAYLIGHT=N', // 'TIMEZONE=U', // 'SYSID=CM01', // 'ZONEOFFSET=0') //EYUXDPRM DD * WUI=YES WUIPLEX=PRODPLEX WUINAME=WUI001 WUIAPPLID=WUI001 WUISYSID=WU01 /* //STEPLIB DD DISP=SHR,DSN=CICSTS62.CPSM.SEYUAUTH //EYUDREP DD DISP=OLD,DSN=EXAMPLE.CMAS001.EYUDREP //SYSPRINT DD SYSOUT=* //After you run the EYUCMSDS job, the EYUDREP file is ready for use with a definition of PRODPLEX and an entry for the CICSPlex SM WUI server region to run in that CICSplex.
- Start CMAS001, pointing it to the EYUDREP file you just created. It is critical that the CMAS
name and SYSIDNT match the EYUDREP file it is using. If it does not, the CMAS issues an error
message, produces an SVC dump, and terminates.When CMAS001 has fully initialized, you can see the following message at the bottom of the JOBLOG:
EYUXL0010I CMAS001 CMAS initialization complete.
- Customize your CICS installation by setting DFHISTAR attributes specific to CICSPlex SM, and then run the DFHISTAR job. For
details, see Specifying attributes specific to CICSPlex SM. The following attributes match the sample
environment as shown in Figure 1.
- Step 2. Set up the CMAS region on LPAR 2
- Run the EYUCMSDS postinstallation job to create CICSPlex SM data sets for your second CMAS,
CMAS002. You are not creating a CICSplex in this step. You create just an empty EYUDREP file for
CMAS002 to use. The EYUDREP parts of that job are shown in Figure 3.
Figure 3. Extract of the EYUCMSDS job for CMAS002, EYUDREP parts //DELDREP EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSIN DD * DELETE EXAMPLE.CMAS002.EYUDREP SET MAXCC=0 //DEFDREP EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSIN DD * DEFINE CLUSTER - (NAME(EXAMPLE.CMAS002.EYUDREP) - CYL(100,50) - CISZ(8192) - RECSZ(200,6550) - KEYS(64,0) - SHR(2) - INDEXED - SPEED - REUSE) /* //*************************************************** //DREPINIT EXEC PGM=EYU9XDUT, // COND=(8,LT), // PARM=('CMASNAME=CMAS002', // 'DAYLIGHT=N', // 'TIMEZONE=U', // 'SYSID=CM02', // 'ZONEOFFSET=0') //EYUXDPRM DD * WUI=NO /* //STEPLIB DD DISP=SHR,DSN=CICSTS62.CPSM.SEYUAUTH //EYUDREP DD DISP=OLD,DSN=EXAMPLE.CMAS002.EYUDREP //SYSPRINT DD SYSOUT=* //When this EYUCMSDS job finishes, you can start CMAS002 on LPAR 2. When CMAS002 has fully initialized, you should see the following message at the bottom of its JOBLOG:EYUXL0010I CMAS002 CMAS initialization complete.
At this point, you have two CMAS regions running, but they're not talking to each other yet. So you need to define a connection from each side pointing to the other.
- Step 3. Define the connection from CMAS001 to CMAS002
- Where CMAS001 is currently executing (LPAR 1 in this example), run the EYU9XDBT CICSPlex SM definition utility to create a
CMAS001-to-CMAS002 link connection. This also indicates that CMAS002 is supposed to manage PRODPLEX.
For details about this utility, see The CICSPlex SM definition utility (EYU9XDBT).
Figure 4. Extract of job card to run EYU9XDBT for CMAS001-to-CMAS002 connection definition //************************************************************* //* * //************************************************************* //* // SET CPSMHLQ=CICSTS62.CPSM CICSPLEX SM DATASET HLQ // JCLLIB ORDER=(&CPSMHLQ..SEYUPROC) <- Location of EYUJXBTP //* //EYU9XDBT EXEC EYUJXBTP, // CPSMHLQ=&CPSMHLQ //* //EYU9XDBT.SYSIN DD * CONTEXT CMAS001 OPTION FEEDBACK VERBOSE IMPORT RESDEFS * * /* //EYU9XDBT.RESDEFS DD * DEFINE CMTCMDEF CMAS002 CMTCMDEF_DESCCODEPAGE = "37"; CMTCMDEF_PROTOCOL = "MRO"; CMTCMDEF_RECVBUF = "8192"; CMTCMDEF_RECVPFX = "<"; CMTCMDEF_SECATTACH = "LOCAL"; CMTCMDEF_SENDBUF = "8192"; CMTCMDEF_SENDPFX = ">"; CMTCMDEF_SYSID = "CM02"; CMTCMDEF_TARGETAPPL = "CMAS002"; CMTCMDEF_TARGETNAME = "CMAS002"; DEFINE CPLXCMAS CMAS002 PRODPLEX CPLXCMAS_BOTRSUPD = "10"; CPLXCMAS_CICSPLEX = "PRODPLEX"; CPLXCMAS_CMASNAME = "CMAS002"; CPLXCMAS_DAYLGHTSV = "YES"; CPLXCMAS_INTERVAL = "480"; CPLXCMAS_MPNAME = "CMAS001"; CPLXCMAS_MPSTATUS = "NO"; CPLXCMAS_READRS = "200"; CPLXCMAS_RODMPOP = "NO"; CPLXCMAS_RSPOOLID = "DFHRSTAT"; CPLXCMAS_SECBYPASS = "NO"; CPLXCMAS_SECCMDCHK = "YES"; CPLXCMAS_SECRESCHK = "YES"; CPLXCMAS_STATE = "NORMAL"; CPLXCMAS_STATUS = "2"; CPLXCMAS_SYSID = "CM02"; CPLXCMAS_TMEZONE = "T"; CPLXCMAS_TMEZONEO = "0"; CPLXCMAS_TOPRSUPD = "5"; CPLXCMAS_UPDATERS = "15"; /* //The job should end with RC=0. You can look at the job's SYSTSPRT output to see that both DEFINE commands were successful. Further, if you look at the EYULOG from the running CMAS001, you can see messages showing that the batch job did connect and define what it was supposed to.EYUCP0200I CMAS001 CMAS CMAS002 Being added to CMAS directory in CMAS CMAS001. EYUXD0002I CMAS001 Add CONTEXT(CMAS001) MAJOR_ID(CMTCMDEF) MAJOR_NAME(CMAS002) MAJOR_VER(NONE) EYUXD0002I CMAS001 MINOR_ID(NONE) MINOR_NAME(NONE) MINOR_VER(NONE) By User(******) On System(CMAS001) EYUXD0002I CMAS001 Date(08615) Time(19:33:47). EYUXD0002I CMAS001 Add CONTEXT(CMAS002) MAJOR_ID(CPLXCMAS) MAJOR_NAME(CMAS002) MAJOR_VER(NONE) EYUXD0002I CMAS001 MINOR_ID(CPLEXDEF) MINOR_NAME(PRODPLEX) MINOR_VER(NONE) By User(******) On EYUXD0002I CMAS001 System(CMAS001) Date(08615) Time(19:33:47).
- Step 4. Define the connection from CMAS002 to CMAS001
- Where CMAS002 is currently executing (LPAR 2 in this example), run the EYU9XDBT CICSPlex SM definition utility to create a
CMAS002-to-CMAS001 link definition.
Figure 5. Extract of job card to run EYU9XDBT for CMAS002-to-CMAS001 connection definition //************************************************************* //* * //************************************************************* //* // SET CPSMHLQ=CICSTS62.CPSM CICSPLEX SM DATASET HLQ // JCLLIB ORDER=(&CPSMHLQ..SEYUPROC) <- Location of EYUJXBTP //* //EYU9XDBT EXEC EYUJXBTP, // CPSMHLQ=&CPSMHLQ //* //EYU9XDBT.SYSIN DD * CONTEXT CMAS002 OPTION FEEDBACK VERBOSE IMPORT RESDEFS * * /* //EYU9XDBT.RESDEFS DD * DEFINE CMTCMDEF CMAS001 CMTCMDEF_DESCCODEPAGE = "37"; CMTCMDEF_PROTOCOL = "MRO"; CMTCMDEF_RECVBUF = "8192"; CMTCMDEF_RECVPFX = "<"; CMTCMDEF_SECATTACH = "LOCAL"; CMTCMDEF_SENDBUF = "8192"; CMTCMDEF_SENDPFX = ">"; CMTCMDEF_SYSID = "CM01"; CMTCMDEF_TARGETAPPL = "CMAS001"; CMTCMDEF_TARGETNAME = "CMAS001"; /* //This job should also end with RC=0, and if you look at the output, you can see the connection is defined.
If you look at the EYULOG for CMAS002, you see a bit more. After message EYUXL0010I, you can see a connection definition made going back to CMAS001. But you can also see that the connection is acquired and the two CMAS regions start talking when Repository Synchronization takes place. Finally, you can see messages in CMAS002 that show it has imported the definition for PRODPLEX and is now participating in the management of it.EYUCP0200I CMAS002 CMAS CMAS001 Being added to CMAS directory in CMAS CMAS002. EYUXD0002I CMAS002 Add CONTEXT(CMAS002) MAJOR_ID(CMTCMDEF) MAJOR_NAME(CMAS001) MAJOR_VER(NONE) EYUXD0002I CMAS002 MINOR_ID(NONE) MINOR_NAME(NONE) MINOR_VER(NONE) By User(******) On System(CMAS002) EYUXD0002I CMAS002 Date(08615) Time(19:48:50). EYUCL0015I CMAS002 Receive Link Task initiated for MRO Network connection with CMAS CMAS001. EYUCS0010I CMAS002 Enhanced MRO Network connection to CMAS CMAS001 being initialized. EYUCL0015I CMAS002 Send Link Task initiated for MRO Network connection with CMAS CMAS001. EYUCL0012I CMAS002 Connection of CMAS002 to CMAS001 started. EYUCS0006I CMAS002 MRO network connection CM01SEND assigned to link set. EYUCP0030I CMAS002 Connected directly to CMAS CMAS001. EYUCL0012I CMAS002 Connection of CMAS002 to CMAS001 complete. EYUCP0203I CMAS002 Repository Synchronization started with CMAS CMAS001. EYUCP0204I CMAS002 Repository Synchronization successfully ended with CMAS CMAS001. EYUXD0004I CMAS002 Import of PLEX(PRODPLEX) from CMAS(CMAS001) successful. EYUTS0006I CMAS002 Topology Add of CICSPlex PRODPLEX Initiated. EYUTS0008I CMAS002 Topology Add of CICSPlex PRODPLEX Complete. EYUCW0107I CMAS002 Plex end-of-interval is set to occur once every 480 minutes for context (PRODPLEX). EYUBI0004I CMAS002 BAS initialization for CICSplex PRODPLEX has started. EYUBI0005I CMAS002 BAS initialization for CICSplex PRODPLEX is complete.
At this point, you can start up WUI001, and sign on through CICS Explorer. You can then use CICS Explorer to do any further customization and definitions, including adding a CSYSDEF (CICS System Definition) for a second CICSPlex SM WUI region, WUI002, to PRODPLEX so that it can connect directly to CMAS002.
- Step 5. Add definitions for more CICS regions in batch
- Alternatively, you can add a large numbers of definitions in batch by using the batched
repository-update facility (BATCHREP). For details about this utility, see The batched repository-update facility.You can run this utility in several ways. The following example shows to how to run it with a submitted batch job. Figure 6 gives you a sample JCL to run the utility.
Figure 6. Extract of job card to run BATCHREP //BTCHUPD EXEC PGM=EYU9XDBC,REGION=5M //STEPLIB DD DISP=SHR,DSN=CICSTS62.CPSM.SEYUAUTH // DD DISP=SHR,DSN=CICSTS62.CPSM.SEYULOAD //SYSPRINT DD SYSOUT=* //SYSABEND DD SYSOUT=* //SYSIN DD * CMASNAME(CMAS001) EXECUTE INPUTDSN(EXAMPLE.BATCHREP.INPUT) INPUTMEMBER(CSYSDEF) OUTPUTUSER(EXUSER) PRINTNODE(LOCAL) PRINTCLASS(A) /* //This job just submits the request to CMAS001. The details about what you're asking to be done are in the INPUTDSN and INPUTMEMBER. In the sample above, the contents of EXAMPLE.BATCHREP.INPUT(CSYSDEF) contains:CONTEXT PRODPLEX; CREATE CSYSDEF NAME(AOR001) APPLID(AOR001) SYSID(AOR1) DESC(CICS REGION AOR001) ACTVTIME( ) AINSFAIL(CONTINUE) AUTOINST(COLDONLY) BOTRSUPD(*) CICSSAMP(*) CONNSAMP(*) DAYLGHTSV(INHERIT) DBXSAMP(*) DESCCODEPAGE(37) DYNROUTE(YES) FILESAMP(*) GLBLSAMP(*) HOST( ) JRNLSAMP(*) MONSTATUS(INHERIT) MXTACTION( ) MXTSEV(N_A) NETWORKID( ) NRMACTION( ) NRMSEV(N_A) PORT( ) PROGSAMP(*) READRS(*) RETENTION(*) RTASTATUS(YES) SAMACTION( ) SAMSEV(N_A) SDMACTION( ) SDMSEV(N_A) SECBYPASS(INHERIT) SECCMDCHK(INHERIT) SECRESCHK(INHERIT) SOSACTION( ) SOSSEV(N_A) STLACTION( ) STLSEV(N_A) TDMACTION( ) TDMSEV(N_A) TDQSAMP(*) TERMSAMP(*) TMEZONE(*) TMEZONEO(*) TOPRSUPD(*) TRANSAMP(*) UPDATERS(*) WLMOPTEN(ENABLED) WLMQMODE(ALL) WLMSTATUS(YES) WLMTHRSH(60) ;Note: Note that commands can span multiple lines, but each command terminates with a semicolon (;) character. As most of the parameters for defining a CSYSDEF don't change, the ones that do need to be changed are specified up to the top.When you submit the batch JCL to run BATCHREP, it should end with RC=00, which indicates that the batch submission process completed successfully. However, that does not mean that the definitions were created successfully. To check whether your CREATE requests worked, you need to look at the SYSOUT from the CMAS (CMAS001 in this case). Each time you submit a BATCHREP job, the CMAS creates a new SYSOUT with a system-generated name in the CMAS job output. In SDSF, if you look at the CMAS output, you should see the following content:Figure 7. SYSOUT from CMAS001 SDSF JOB DATA SET DISPLAY - JOB CMAS001 COMMAND INPUT ===> SCROLL ===> NP DDNAME StepName ProcStep DSID Owner C Dest Rec-Cnt JESMSGLG JES2 2 ****** A 4 JESJCL JES2 3 ****** A 143 JESYSMSG JES2 4 ****** A 2 DFHCXRF CMAS001 CICS 103 ****** A 0 MSGUSR CMAS001 CICS 105 ****** A 2,846 COUT CMAS001 CICS 107 ****** A 0 EYULOG CMAS001 CICS 108 ****** A 0 CEEMSG CMAS001 CICS 109 ****** A 0 CEEOUT CMAS001 CICS 110 ****** A 0 CRPO CMAS001 CICS 111 ****** A 0 S0000003 CMAS001 CICS 114 ****** A EXUSER 6 S0000005 CMAS001 CICS 116 ****** A EXUSER 5 S0000007 CMAS001 CICS 118 ****** A EXUSER 7 S0000009 CMAS001 CICS 120 ****** A EXUSER 71 S0000011 CMAS001 CICS 122 ****** A EXUSER 7 S0000013 CMAS001 CICS 124 ****** A EXUSER 137 S0000015 CMAS001 CICS 126 ****** A EXUSER 24 S0000017 CMAS001 CICS 128 ****** A EXUSER 24You can duplicate the CREATE command as many times as needed. For example, to define three TOR regions, TOR001, TOR002, and TOR003, you can use the following sample JCL.Figure 8. Example JCL to define three TOR regions CONTEXT PRODPLEX; CREATE CSYSDEF NAME( TOR001 ) APPLID(TOR001) SYSID(TOR1) DESC(CICS REGION TOR001) ACTVTIME( ) AINSFAIL(CONTINUE) AUTOINST(COLDONLY) BOTRSUPD(*) CICSSAMP(*) CONNSAMP(*) DAYLGHTSV(INHERIT) DBXSAMP(*) DESCCODEPAGE(37) DYNROUTE(YES) FILESAMP(*) GLBLSAMP(*) HOST( ) JRNLSAMP(*) MONSTATUS(INHERIT) MXTACTION( ) MXTSEV(N_A) NETWORKID( ) NRMACTION( ) NRMSEV(N_A) PORT( ) PROGSAMP(*) READRS(*) RETENTION(*) RTASTATUS(YES) SAMACTION( ) SAMSEV(N_A) SDMACTION( ) SDMSEV(N_A) SECBYPASS(INHERIT) SECCMDCHK(INHERIT) SECRESCHK(INHERIT) SOSACTION( ) SOSSEV(N_A) STLACTION( ) STLSEV(N_A) TDMACTION( ) TDMSEV(N_A) TDQSAMP(*) TERMSAMP(*) TMEZONE(*) TMEZONEO(*) TOPRSUPD(*) TRANSAMP(*) UPDATERS(*) WLMOPTEN(ENABLED) WLMQMODE(ALL) WLMSTATUS(YES) WLMTHRSH(60) ; CREATE CSYSDEF NAME(TOR002) APPLID(TOR002) SYSID(TOR2) DESC(CICS REGION TOR002) ACTVTIME( ) AINSFAIL(CONTINUE) AUTOINST(COLDONLY) BOTRSUPD(*) CICSSAMP(*) CONNSAMP(*) DAYLGHTSV(INHERIT) DBXSAMP(*) DESCCODEPAGE(37) DYNROUTE(YES) FILESAMP(*) GLBLSAMP(*) HOST( ) JRNLSAMP(*) MONSTATUS(INHERIT) MXTACTION( ) MXTSEV(N_A) NETWORKID( ) NRMACTION( ) NRMSEV(N_A) PORT( ) PROGSAMP(*) READRS(*) RETENTION(*) RTASTATUS(YES) SAMACTION( ) SAMSEV(N_A) SDMACTION( ) SDMSEV(N_A) SECBYPASS(INHERIT) SECCMDCHK(INHERIT) SECRESCHK(INHERIT) SOSACTION( ) SOSSEV(N_A) STLACTION( ) STLSEV(N_A) TDMACTION( ) TDMSEV(N_A) TDQSAMP(*) TERMSAMP(*) TMEZONE(*) TMEZONEO(*) TOPRSUPD(*) TRANSAMP(*) UPDATERS(*) WLMOPTEN(ENABLED) WLMQMODE(ALL) WLMSTATUS(YES) WLMTHRSH(60) ; CREATE CSYSDEF NAME(TOR003) APPLID(TOR003) SYSID(TOR3) DESC(CICS REGION TOR003) ACTVTIME( ) AINSFAIL(CONTINUE) AUTOINST(COLDONLY) BOTRSUPD(*) CICSSAMP(*) CONNSAMP(*) DAYLGHTSV(INHERIT) DBXSAMP(*) DESCCODEPAGE(37) DYNROUTE(YES) FILESAMP(*) GLBLSAMP(*) HOST( ) JRNLSAMP(*) MONSTATUS(INHERIT) MXTACTION( ) MXTSEV(N_A) NETWORKID( ) NRMACTION( ) NRMSEV(N_A) PORT( ) PROGSAMP(*) READRS(*) RETENTION(*) RTASTATUS(YES) SAMACTION( ) SAMSEV(N_A) SDMACTION( ) SDMSEV(N_A) SECBYPASS(INHERIT) SECCMDCHK(INHERIT) SECRESCHK(INHERIT) SOSACTION( ) SOSSEV(N_A) STLACTION( ) STLSEV(N_A) TDMACTION( ) TDMSEV(N_A) TDQSAMP(*) TERMSAMP(*) TMEZONE(*) TMEZONEO(*) TOPRSUPD(*) TRANSAMP(*) UPDATERS(*) WLMOPTEN(ENABLED) WLMQMODE(ALL) WLMSTATUS(YES) WLMTHRSH(60) ;
What to do next
These samples help you get started configuring your own CICSPlex SM environment. Given the sample JCL above, you are able to customize them into your own jobs, provide a JOBCARD, and perform CHANGE ALL commands so that the names of data sets and regions follow your own local naming standards.