WebSphere® Application Server for z/OS® server uses the JCL cataloged procedures for standalone application servers and Network Deployment cells. Learn about recommended naming conventions and assigning user IDs to WebSphere Application Server for z/OS address spaces.
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 Profile Management Tool or the zpmt command:
//BBO8ACR PROC ENV=,PARMS=' ',REC=N,AMODE=00
// SET ROOT='/wasv8config/bbobase/bbonode'
// SET FOUT='properties/service/logs/applyPTF.out'
// SET WSDIR='AppServer'
//*************************************************************
//* Test that OMVS can successfully launch a shell and return *
//*************************************************************
//TOMVS EXEC PGM=BPXBATCH,REGION=0M,
// PARM='SH exit 13'
//SYSOUT DD PATH='&ROOT./&ENV..HOME/&FOUT.',
// PATHOPTS=(OWRONLY,OCREAT,OAPPEND),PATHMODE=(SIRWXU,SIRWXG)
//SYSPRINT 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'
//SYSOUT DD PATH='&ROOT./&ENV..HOME/&FOUT.',
// PATHOPTS=(OWRONLY,OCREAT,OAPPEND),PATHMODE=(SIRWXU,SIRWXG)
//SYSPRINT 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=BPXBATA2,REGION=0M,TIME=MAXIMUM,MEMLIMIT=NOLIMIT,
// PARM='PGM &ROOT./&WSDIR./lib/s390-common/bbooctlm &AMODE. &PARMS.
//REC=&REC' STDENV DD PATH='&ROOT/&ENV/was.env'
//*
//* Output DDs
//*
//CEEDUMP DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE
//SYSOUT DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE
//SYSPRINT DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE
//DEFALTDD DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE
//HRDCPYDD DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE
// ENDIF
//IFTSTEND ENDIF
Procedure library member BBO8ASR://BBO8ASR PROC ENV=,AMODE=00
// SET ROOT='/wasv8config/bbobase/bbonode'
// SET WSDIR='AppServer'
//STEP1 EXEC PGM=BPXBATSL,REGION=0M,TIME=NOLIMIT,MEMLIMIT=NOLIMIT,
// PARM='PGM &ROOT./&WSDIR./lib/s390-common/bboosrmr &AMODE.'
//STDENV DD PATH='&ROOT/&ENV/was.env'
//*
//* Output DDs
//*
//CEEDUMP DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE
//SYSOUT DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE
//SYSPRINT DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE
//DEFALTDD DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE
//HRDCPYDD DD SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE
The STDENV 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 controller cataloged procedure includes some additional statements before the EXEC statement that invokes BPXBATA2. These are used to invoke the post installer program that applies any needed maintenance to the configuration HFS and its home directories when service is applied to the product HFS and load modules.
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.
You can use the same cataloged procedures for different standalone servers if the configuration HFS and product code level (including STEPLIB) are the same for both servers.
A Network Deployment cell uses the following cataloged procedures:
The application server servant cataloged procedure is the only one likely to require modification, in order to place libraries (CICS®, DB2®, and so on) in the STEPLIB concatenation.
You can use the same cataloged procedures for several nodes in a Network Deployment cell, or even for several cells, if the configuration HFS is the same for all of them.
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 and configuration HFS
Procedure | Recommended Name |
---|---|
Deployment manager controller | cc8DCR |
Deployment manager servant | cc8DSR |
Location service daemon controller | cc8DMN |
Application server controller | cc8ACR |
Application server servant | cc8ASR |
Control region adjunct | cc8AAR |
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 batch jobs created by the Profile Management Tool or the zpmt command. Update these STARTED profiles as needed to place servers that 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.