Each WebSphere® Application Server for z/OS® server uses a JCL cataloged procedure. These procedures are all fairly similar and consist of a main cataloged procedure and an INCLUDE member that contains DD statements.
Here are sample cataloged procedure library members for a controller as generated by the Customization Dialog:
//BBO6ACR PROC ENV=,PARMS=' ',REC=N,Z=BBO6ACRZ,AMODE= // SET ROOT='/WebSphere/V6R1' // SET FOUT='properties/service/logs/applyPTF.out' //************************************************************* //* Test that OMVS can successfully launch a shell and return * //************************************************************* //TOMVS EXEC PGM=BPXBATCH,REGION=0M, // PARM='SH exit 13' //STDOUT DD PATH='&ROOT./&ENV..HOME/&FOUT.', // PATHOPTS=(OWRONLY,OCREAT,OAPPEND),PATHMODE=(SIRWXU,SIRWXG) //STDERR DD PATH='&ROOT./&ENV..HOME/&FOUT.', // PATHOPTS=(OWRONLY,OCREAT,OAPPEND),PATHMODE=(SIRWXU,SIRWXG) //********************************************************* //* If the shell RC code is as expected (13) - proceed * //********************************************************* //IFTST IF (RC = 13) THEN //********************************************************* //* Start the Multi-Product PTF Post-Installer * //********************************************************* //APPLY EXEC PGM=BPXBATCH,REGION=0M, // PARM='SH &ROOT./&ENV..HOME/bin/applyPTF.sh inline' //STDOUT DD PATH='&ROOT./&ENV..HOME/&FOUT.', // PATHOPTS=(OWRONLY,OCREAT,OAPPEND),PATHMODE=(SIRWXU,SIRWXG) //STDERR DD PATH='&ROOT./&ENV..HOME/&FOUT.', // PATHOPTS=(OWRONLY,OCREAT,OAPPEND),PATHMODE=(SIRWXU,SIRWXG) // IF (APPLY.RC <= 4) THEN //********************************************************* //* If the RC from the Post-Installer is LE 4 then start * //* the WebSphere Application Server * //********************************************************* //STEP1 EXEC PGM=BBOOMTST,PARM='&AMODE.' // INCLUDE MEMBER=&Z //TEST1 IF (STEP1.RC = 0) THEN //BBOCTL EXEC PGM=BBOCTL,REGION=0M,TIME=MAXIMUM, // PARM='TRAP(ON,NOSPIE),ENVAR("_EDC_UMASK_DFLT=007") / // &PARMS. REC=&REC' //BBOENV DD PATH='&ROOT/&ENV/was.env' // INCLUDE MEMBER=&Z // ELSE //BBGCTL EXEC PGM=BBGCTL,REGION=0M,TIME=MAXIMUM,MEMLIMIT=NOLIMIT, // PARM='TRAP(ON,NOSPIE),ENVAR("_EDC_UMASK_DFLT=007") / // &PARMS. REC=&REC' //BBOENV DD PATH='&ROOT/&ENV/was.env' // INCLUDE MEMBER=&Z // ENDIF // ENDIF //IFTSTEND ENDIFThis cataloged procedures contains the following:
//* //* Output DDs //* //CEEDUMP DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE //SYSOUT DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE //SYSPRINT DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE //* //*Steplib Setup //* //STEPLIB DD DISP=SHR,DSN=WAS.V61.SBBOLD2 // DD DISP=SHR,DSN=WAS.V61.SBBOLOAD // DD DISP=SHR,DSN=WAS.V61.SBBGLOAD //
Here are sample cataloged procedure library members for a servant as generated by the Customization Dialog. The servant does not require the post-installer or addressing-mode selection.
//BBO6ASR PROC ENV=,Z=BBO6ASRZ,AMODE= // SET ROOT='/WebSphere/V6R1' //STEP1 EXEC PGM=BBOOMTST,PARM='&AMODE.' // INCLUDE MEMBER=&Z //TEST1 IF (STEP1.RC = 0) THEN //BBOSR EXEC PGM=BBOSR,REGION=0M,TIME=NOLIMIT, // PARM='TRAP(ON,NOSPIE),ENVAR("_EDC_UMASK_DFLT=007") /' //BBOENV DD PATH='&ROOT/&ENV/was.env' // INCLUDE MEMBER=&Z // ELSE //BBGSR EXEC PGM=BBGSR,REGION=0M,TIME=NOLIMIT,MEMLIMIT=NOLIMIT, // PARM='TRAP(ON,NOSPIE),ENVAR("_EDC_UMASK_DFLT=007") /' //BBOENV DD PATH='&ROOT/&ENV/was.env' // INCLUDE MEMBER=&Z // ENDIF
//* //* Output DDs //* //CEEDUMP DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE //SYSOUT DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE //SYSPRINT DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE //* //*Steplib Setup //* //STEPLIB DD DISP=SHR,DSN=WAS.V61.SBBOLD2 // DD DISP=SHR,DSN=WAS.V61.SBBOLOAD // DD DISP=SHR,DSN=WAS.V61.SBBGLOAD
The BBOENV DD statement points to the was.env (startup parameter) file for the server. The path to this file consists of the configuration HFS directory name (hardcoded using the ROOT JCL variable) and the symbolic link for this particular server, which is specified at startup using the ENV= parameter.
The INCLUDE statement in the main cataloged procedure causes the incorporation of all JCL statements from the INCLUDE member (in this case, BBO6ASRZ). By convention, the INCLUDE member's name consists of the name of the main cataloged procedure with the letter "Z" appended to the end. The INCLUDE member provides common DD statements for the started task.
The following sections describe the cataloged procedures required for each configuration, provide a recommended naming convention, and explain how the SAF user ID for each server is determined.
A Network Deployment cell uses the following cataloged procedures, with corresponding INCLUDE JCL members for each:
You can use the same cataloged procedures for several nodes in a Network Deployment cell, or even for several cells, IF the configuration HFS and product code level (including STEPLIB) are the same for both servers. The Customization Dialog will overwrite identically-named proclib members if identical names are chosen or if customization jobs and files are regenerated. If you have a local STEPLIB or make other changes to the procedures, therefore, make sure that they are reapplied after you use the Customization Dialog.
Use a consistent naming convention for your WebSphere Application Server for z/OS cataloged procedures. The procedure name should distinguish between WebSphere Application Server for z/OS version, configuration HFS, and which data sets are listed in STEPLIB. Limit cataloged procedure names to seven characters to allow the Customization Dialog to create INCLUDE JCL member names by appending the letter "Z."
Deployment manager controller | cc6DCR |
Deployment manager servant | cc6DSR |
Location service daemon controller | cc6DMN |
Application server controller | cc6ACR |
Application server servant | cc6ASR |
Control region adjunct | cc6CRA |
If you use z/OS Security Server (RACF®) as your SAF-compliant security system on z/OS, then STARTED class profiles are used to assign started task user IDs to each WebSphere Application Server for z/OS server. These STARTED profiles are set up by the Customization Dialog batch jobs. Update these STARTED profiles as needed to place servers you create yourself under the appropriate user IDs.
Controllers (deployment manager, location service daemon, node agent or applications server controller) are started using a console START command that you issue either from the MVS™ console or internally. For these servers, the STARTED profile name that is checked is of the form procname.jobname.
Servant regions (application server servants and adjunct processes) are started using Workload Manager (WLM). For these servers, the STARTED profile name that is checked is of the form jobname.jobname.
If you use another SAF-compliant security system, contact the security server vendor for WebSphere Application Server for z/OS setup information.
The asynchronous administrative task also requires a cataloged procedure. This very simply cataloged procedure does not include a STEPLIB or configuration HFS pointer. However, since it must run under a specific user ID and group associated with the security domain of the cell for which it runs, you must choose a different cataloged procedure name for each security domain or cell.
Recommendation:
Name the administrative asynchronous task cataloged procedure "cc6SH," where cc is a two-character cell identifier.