This topic applies only on the z/OS operating system.

Cataloged procedures

Cataloged procedures are generated by the Customization Dialog. They set system requirements and parameters.

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 servant as generated by the Customization Dialog:

Procedure library member BBO6ASR:
//BBO6ASR  PROC ENV=,Z=BBO6ASRZ                                  
//  SET™ ROOT='/WebSphere/V6R0'                                   
//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                                            
Procedure library member BBO6ASRZ:
//*                                                                 
//* 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.V60.SBBOLD2                          
//         DD DISP=SHR,DSN=WAS.V60.SBBOLOAD                         
The PGM= parameter on the EXEC statement in the cataloged procedure specifies the type of WebSphere Application Server for z/OS server. The program names are as follows:
The PARM= parameter on the EXEC PGM statement contains the parameters that are passed to the program identified by the PGM= parameter.
Customization Note: The appropriate interface for making changes to the language environment (LE) parameters is through the PARM= parameter; however, do not modify any LE parameters without first consulting with the IBM® support team. The LE parameters are set internally to ensure the best possible performance of the WebSphere Application Server, which is the main LE application running in the address space. If you need to add or change LE parameters, make sure that you work with the IBM WebSphere support team to ensure that the internally set parameters are not compromised.

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 STEPLIB DD statement for the location service daemon determines the WebSphere Application Server for z/OS code base intended for use. If the location service daemon finds the SBBOLPA modules in its STEPLIB concatenation, it loads them into common storage. If the modules are not found in STEPLIB, then the location service daemon checks for their presence in the system link pack area.
Note: If the modules are found in neither location, the location service daemon reports an error and terminates.
Once the modules are located (and loaded if necessary), the location service daemon holds a vector table of load module addresses that the rest of the cell's servers will use.
All other servers for the location service daemon's cell on the same z/OS system must use the same product code base as the location service daemon: The controller cataloged procedure includes some additional statements before the EXEC statement that invokes BBOCTL. 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.

Cataloged procedures for standalone application servers

A standalone application server uses the following cataloged procedures with corresponding INCLUDE JCL members for each: 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. 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.

Cataloged procedures for Network Deployment cells

A Network Deployment cell uses the following cataloged procedures, with corresponding INCLUDE JCL members for each:

For the deployment manager:
  • Deployment manager controller cataloged procedure
  • Deployment manager servant cataloged procedure
For each application server node:
  • Application server controller cataloged procedure (also used for the node agent)
  • Application server servant cataloged procedure
  • Adjunct process cataloged procedure
For the location service daemon (one per z/OS system):
  • Location service daemon cataloged procedure
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 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.

A recommended cataloged procedure naming convention

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."

For example, the following convention works for either a standalone application server or Network Deployment cell, where cc is a two-character cell identifier:
Deployment manager controller cc6DCR
Deployment manager servant cc6DSR
Location service daemon controller cc6DMN
Application server controller cc6ACR
Application server servant cc6ASR
If you require separate cataloged procedures for nodes on different systems in a sysplex (if they need independently settable STEPLIB statements to allow for a nondisruptive restart for example), either place the location service daemon and application server procedures in system-specific proclibs, or append a one-character system identifier to the cataloged procedure names for the location service daemon and application servers.

Assigning user IDs to WebSphere Application Server for z/OS address spaces

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.

Whenever it creates a controller or daemon cataloged procedure, the Customization Dialog also creates a STARTED profile that associates all controllers using that cataloged procedure with the appropriate controller user ID and configuration group. Therefore, if you set up a standalone application server with default names, the Customization Dialog would create the following STARTED profiles for controllers:
  • RDEFINE STARTED BBO6ACR.* STDATA(USER(ASCR1) GROUP(WSCFG1) TRACE(YES))
  • RDEFINE STARTED BBO6DMN.* STDATA(USER(WSDMNCR1) GROUP(WSCFG1) TRACE(YES))
Note: TRACE(YES) writes message IRR812I to the MVS console whenever the profile is used.

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.

Unfortunately, there is no way to assign all servers using a particular servant cataloged procedure to a servant user ID. Therefore, the Customization Dialog creates both a generic STARTED profile for servants, based on the jobname prefix BBO, and a specific STARTED profile for any servant whose jobname does not begin with BBO, that assign their servants to the servant user ID, and a specific STARTED profile for the adjunct process that assigns it to the CRA user ID. If default names are chosen, the following servant STARTED profiles are created for a standalone application server:
  • RDEFINE STARTED BBO*.* STDATA(USER(ASSR1) GROUP(WSCFG1) TRACE(YES))
  • RDEFINE STARTED BBOS001A.* STDATA(USER(ASCRA1) GROUP(WSCFG1) TRACE(YES))
When you choose cataloged procedure names, make sure that the appropriate STARTED profile is in place to map the server to its appropriate SAF user ID. Use the RACF ISPF panels or the RLIST STARTED command to display the STARTED profiles.

If you use another SAF-compliant security system, contact the security server vendor for WebSphere Application Server for z/OS setup information.

Cataloged procedure for the administrative asynchronous task

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.




Related concepts
HFS configuration strategy
Concept topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 10:43:27 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v602web&product=was-nd-mp&topic=cins_plancatpro
File name: cins_plancatpro.html