Appendix: Editing JCL Templates in OS390 for COBOL and SQR

This appendix provides an overview of JCL templates and discusses how to:

• Customize the PeopleSoft Process Scheduler shell JCL template.

• Run PeopleSoft Process Scheduler or Application Engine from a JCL in OS390.

• Understand the limitations of Process Scheduler server running from USS (UNIX System Services).

Understanding JCL Templates

The PeopleSoft Server Transfer program creates a directory $PS_HOME/appserv/prcs/shelljcl in the OS390 UNIX Services to store a master copy of the shell JCL templates. When you create a PeopleSoft Process Scheduler Server configuration, it copies the shell JCL templates into the $PS_HOME/appserv/prcs/<database name>/shelljcl directory. This includes all of the JCLs used for running COBOL and SQR through PeopleSoft Process Scheduler.

The following table lists the shell JCL templates used in PeopleSoft Process Scheduler:

You must modify these shell JCL templates to comply with your site standards.

PSADMIN has an Edit a Shell JCL template to enable you to edit a JCL using the VI editor. If you are not familiar with the VI editor and prefer to edit the JCLs using the ISPF editor, you can use the TSO oedit command in the TSO session. The IBM TSO oedit command enables you to modify any files residing in USS from a TSO session. You can edit any of the shell JCL templates found in $PS_HOME/appserv/prcs/<database name>/shelljcl directory as shown in the following example. Please consult your OS390 system administrator for using the oedit command at your site.

Example of editing shell JCL templates

Customizing the PeopleSoft Process Scheduler Shell JCL Template

All of the PeopleSoft Process Scheduler shell JCLs use meta-strings to pass data stored in the database or PeopleSoft Process Scheduler configuration files. PeopleSoft Process Scheduler uses meta-strings to generate the JCL based on one of these sources:

• The profile of the user who initiated the request.

• Parameters defined in the PeopleSoft Process Scheduler configuration file.

• Parameters defined on the Process Type Definition page or the Process Definition page.

A good example of data that can be passed includes job account and job name. Enter the values of some of these variables by selecting PeopleTools, Security, Permissions & Roles, Permission Lists.

The shell JCL templates are tunable and should be changed according to your site-specific standards. The following table identifies the meta-strings that you can use in a shell JCL template.

If you create a new JCL template, be aware that:

• The Shell ID is restricted to three characters.

• The Shell ID is associated with the process type definition.

Following is a sample job control card in one of the shell JCLs:

//%JOBNAME%%SFX% JOB %JOBACCT%,'PS-PRCS ',CLASS=E,MSGCLASS=X,

// NOTIFY=%OPRID%

If you do not use meta-strings, you can also update the job cards to remove these variables and replace them with actual values.

In the SHELL JCL for SQR, OUTNODE denotes either an OS390 partitioned dataset (PDS) or a sequential dataset. The PDS is a requirement for SQR output. If the SQR report XRFPANEL is directed to file output, the following substitution occurs:

In SHELSQRF.JCT, change// OUTNODE='%OUTDEST%' to // OUTNODE='HR.H800RAB', .

If an SQR process is directed to print, the following substitutions occur:

// OUTNODE='DEST=U3', OPTIONAL:USER-DEF OUTPUT . .

//*********************************************************************

//* Main portion of JCL Shell *

//*********************************************************************

..

//SQROUTP DD SYSOUT=*,DEST=U3

OS390 Job Controls

OS390 job controls specify the OS390 job name to assign to each process that is submitted. This value can be up to seven characters. Do not use lowercase letters or quotation marks. If you included the %SFX% meta-string as part of the job name, PeopleSoft Process Scheduler appends a one-character alphabetical suffix to this name (A through Z, chosen randomly) before the job submission.

For example, if you entered USRMVS1, the assigned job name becomes USRMVS1A through USRMVS1Z. After you enter the OS390 job name, enter the job account number that you used in the installation. Specify an account code to be inserted as the JCL accounting code.

Running PeopleSoft Process Scheduler or Application Engine From a JCL in OS390

PeopleSoft Process Scheduler is customarily started and stopped from a JCL sample. JCLs are provided to accomplish this task. An Application Engine program must also be run from a JCL in some business cases. Any PeopleSoft executable residing in the UNIX System Services (USS) can be invoked from a JCL using the IBM BPXBATCH utility.

In the high-level qualifier where PeopleSoft is installed in OS390, a partitioned dataset (HLQ.JCLLIB) contains the following JCL:

• PRCSSTRT,JCL: JCL to start PeopleSoft Process Scheduler.

• PRCSSTOP.JCL: JCL to stop PeopleSoft Process Scheduler.

• AESAMP.JCL: Sample JCL to run an Application Engine program.

The following table identifies the meta-strings to use, in the order specified in a shell JCL template, for USS scheduler to pass COBOL parameters so that it can, in turn, call Application Engine:

Limitations of Process Scheduler Server

In the USS environment, Process Scheduler submits COBOL and SQR by means of a JCL. Although Process Scheduler can capture the job name of a JCL, it is incapable of capturing the job ID assigned by TSO. Consequently, Process Scheduler does not have the ability to query or manage a JCL that has been submitted to the TSO environment.

As a result, Process Scheduler does not have the ability to cancel a JCL job when a user requests to cancel an SQR or COBOL process using the Process Monitor page. While Process Scheduler does not kill the JCL associated with the process, it does make the slot available for any other queued SQR or COBOL processes. Therefore, you must manually cancel the JCL from a TSO session.

Note. This limitation does not apply to Application Engine requests initiated from z/OS. The executable of an Application Engine is terminated when a user cancels the submitted request from the Process Monitor page.