This section outlines the required steps to install and implement Production Control Services (PCS).

The BMC AMI Ops Automation for Batch ThruPut fully supports PCS but there are a few additional steps required in order that the function can be activated. The Install data set member (TTM7191) provides an SMP/E stream that will rename TM CA 7 exit points and link a new module. The member contains everything that is necessary. Simply run an SMP/E RECEIVE and APPLY in the SMP/E environment where BMC AMI Ops Automation for Batch ThruPut was previously installed.

10.1 Install CA 7 exits

PCS uses CA 7 exits 2 or 20, 5, 11, 13 and 17. These exits are included with the BMC ThruPut Manager Base in DTMLINK as DTMC7Xnn modules. When PCS is installed from the apply of TTM7191 above, these modules are automatically renamed to the proper CA 7 exit names, SASSXXnn. As a result, the SASSXXnn exit modules will be located within DTMLINK so they must be the first like named modules encountered in the link list.

The exits must then be enabled in the CA 7 "UCC7IN" options as illustrated below, and a recycle of CA 7 is required to activate them.

Consult the CA 7 Workload Automation manual for directions to dynamically install CA 7 exits.

10.1.1. Conflicts with existing CA 7 installation exits

If your installation currently uses any of the exits previously mentioned, PCS calls these exits before performing PCS processing. Therefore you must do the following to ensure PCS exits gain control at the appropriate point.

1. Rename the installation defined CA 7 exit routines, SASSXXnn, to SASSX$nn. (After PTF TMT6217, the relink for these exit points is no longer required making job CA7XLINK, found in the INSTALL data set, obsolete). The INSTALL data set includes member @UMODCA7, which provides SMP/e USERMODs (UCA7Xnn), to do the rename of each duplicate exit point. It also contains sample JCL to RECEIVE and APPLY the necessary USERMODs to your CA 7 SMP/e environment.
2. Add an "APPLCTN,NAME=SASSX$nn" statement to the initialization deck for each renamed exit point.

10.2. Set up authorizations

10.2.1. Set up RACF (or equivalent) security

Two different types of authorizations are required for PCS. Standard security authorizations to RACF (or equivalent) are required for the PCS control region, the PCS Forecast Collection Utility and TSO userids that will be accessing the PCS ISPF Dialog. This authorization will allow access to PCS data sets.

If communication is required across SYSPLEX's, the RACF User ID associated with the TM started task and PCS control region must have a RACF OMVS segment, otherwise TCPIP initialization will fail with message.

10.2.2 Update CA 7 security table

In addition, specific CA 7 authorities are required for the userid associated with PCS control region and the Collection Utility along with any TSO userids that will access the dialog. All of the userids mentioned above must be defined to the CA 7 security table. The security table is assembled and loaded into CA 7. The source resides in the SASSSECI member of the CAISRC library associated with your CA 7 (for example CAS.CAI.CA7.CAISRC (SASSSECI)).

A sample entry for a userid PCSUSER would be:

For more information, refer to the CA 7 Workload Automation Security Reference Guide.

The table below shows the CA 7 functions that PCS uses, and the required minimum function authority.

Various PCS interfaces retrieve information and use CA 7 functions utilizing CCI facilities. A CCI Session is created for every PCS interface with CA 7. This interface must be active and available on any system that runs these functions. The userid under which the CCI session is running must be authorized in order to communicate with CA 7. The CA CAILIB data set is a required linklisted data set. If this library is NOT in the linklist, the library must be allocated via STEPLIB or ISPLLIB.

The PCS control region uses these CA 7 functions:

The Forecast Collection Utility uses these CA 7 functions:

The PCS Dialog uses these functions:

10.3. Customize the PCS control region

PCS requires a separate control region for each CA 7 control region. It must run in the same JESplex member as its corresponding CA 7 control region. The control region module (DTMPCSVn) must reside in a linklisted data set, and must run as a started task in its own address space.

PCS follows the IBM architecture of JESplex and SYSPLEX. When communicating within a SYSPLEX, PCS uses XCF. Communication across SYSPLEXes uses TCP/ IP.

All systems to which CA 7 submits work to, must communicate information to PCS. Therefore, PCS must be implemented in all systems that execute CA 7 jobs, because this is how information about CA 7 jobs is communicated back to the PCS control region.

10.3.1. PCS JCL sample procedure

This sample procedure below is found in the TMPCS member of the install data set.

The DD statement SYSPARM points to the data set containing the PCS Initialization Statements. Two of the parameters in the sample proc are used to indicate where PCS can find its Initialization Statements. These are:

Specifies the name of a cataloged partitioned data set that contains a member specifying the PCS Initialization Statements.

Specifies the member name within the partitioned data set that contains the PCS Initialization Statements.

The sample procedure accepts the following options in the EXEC PARM field:

Specifies the Command Character sequence to be used to communicate with this address space. This keyword is required.

Specifies the CA 7 Instance that is to be managed. It's used to uniquely identify PCS and the associated CA 7. This keyword is required.

Required only if you want to reinitialize the file. The first time the Battle Plan file is initialized automatically. Any Cold-Start of a file must be done with care as all the information is lost.

Required only if you want to reinitialize the file. The first time the PCS control region is initiated, the Experience Collection file is initialized automatically. Any Cold-Start of a file must be done with care as all the information is lost.

Required only if you want to reinitialize the file. The first time the PCS control region is initiated, the PCS SMF Data Collection file is initialized automatically. Any Cold-Start of a file must be done with care as all the information is lost.

Specifies the name of the CCI receiver with which this PCS control region must communicate. This keyword is required for installations using multiple CCI receivers.

Using CCI receivers

As many installations do not make use of the CCI facility, they may be unaware of the available definitions within CA 7. Consult the CA 7 external interface documentation for full details. The following describes the implications for connecting a particular PCS control region and PCS Dialog to its associated Instance.

If you are running multiple Instances of CA 7 in the same LPAR, the CCI receiver must be uniquely identified. The CCI receiver for a given CA 7 Instance is determined by the following:

• If the XTMNAME keyword has a value in the initial SVCNO statement, that is the CCI receiver name for that CA 7 Instance.
• If the XTMNAME keyword is not coded, but the RNAME keyword has a value, then that is the CCI receiver name for that CA 7 Instance.
• If neither the XTMNAME keyword or RNAME keyword are coded, then the CA 7 Instance name is the CCI receiver name.

The CCI Receiver name is used in two distinct places by PCS. It is one of the parameters used to start the PCS control region. If nothing is coded, the default is the CA 7 Instance name. If values have been coded in the CA 7 SVCNO initialization statement this will result in an error. So make sure that you determine the actual name and provide it to the PCS PROC.

Unfortunately, there is a further complication. You might have CA 7 Instances in your installation with the same name. In fact, you cannot avoid this if you have CA 7 Instances using NCF for NJE processing since only the CA71 Instance name is supported by CA 7. Consequently, you may be running several CA71 Instances.

If you are not using the CA 7 CCI interface, then there might not be any customized unique naming for the corresponding CCI Receivers.

You could have addressed the RNAME if you used the "hot" backup capability to avoid confusion with ENQs. In that case, use the RNAME specified in the CA 7 SVCNO Initialization Statement.

If you have done nothing, you must create unique names for the CCI receivers using the XTMNAME keyword in each of the CA 7 SVCNO Initialization Statement associated with the CA 7 Instances with the same name. This is a must, not an option.

The PCS PROC includes the parameter substitution of XTM. This covers both situations: the RNAME or the XTMNAME, whichever applies.

The second area where the CCI Receiver name is used is in the dialog panel where you indicate the Instance of CA 7 with which you want to communicate. The same requirements as the ones for the PCS control region apply here.

10.3.2. Initialization statements

PCS dynamically allocates the required files as specified in the Initialization Statements pointed to by the SYSPARM DD.

The following TMSS Initialization Statements have been changed to support PCS.

PCS requires TCP/IP connections when supporting a CA 7 that submits jobs for execution on another z/OS SYSPLEX. If CA 7 does not submit jobs to execute on another SYSPLEX, neither PCS nor BMC ThruPut Manager needs TCP/IP connections.

For PCS to function properly when supporting a CA 7 which submits jobs to be executed on another SYSPLEX, TCP/IP connections must be defined to both the PCS control region and the BMC ThruPut Manager started tasks. This is necessary to allow PCS data about the job to be communicated to the originating SYSPLEX. The Initialization Statement is used to make the necessary definitions for both PCS and BMC ThruPut Manager control region (the syntax is identical).

The Initialization Statement allows the installation to define the necessary TCP/IP connections to other z/OS systems on neighboring SYSPLEXs. Note that the definitions must be specified for all instances of TMSS in both SYSPLEXes. The syntax is:

For the BMC ThruPut Manager started task, HOSTNAME specifies a system on which a PCS control region might be running. For PCS, HOSTNAME specifies a system on which TMSS might be running.

For the BMC ThruPut Manager started task, IP specifies a valid TCP/IP address for a system on which a PCS control region might be running. For PCS, IP specifies a valid TCP/IP address for a system on which TMSS might be running. BMC ThruPut Manager makes use of TCP/IP ports 9666-9675 inclusively.

You can specify as many TM TCPIP ADD statements as necessary:

• For PCS, include the IPs of all systems in neighboring SYSPLEXes where jobs could potentially execute.
• For TMSS, include the IPs of all systems where PCS might execute.

10.3.3 Allocate and initialize files

Allocate the following files for the PCS control region:

• Job Experience Collection file
• Job Experience files
• Battle Plan file

Job Experience Collection file

The Job Experience Collection file is used to collect execution time job information data generated by the TM running in the JESplex member where the job executed, and passed to PCS. The data is in the form of transactions that are used to update the Experience files via a batch utility program.

To identify the Job Experience Collection file to PCS, you must use the PCS Initialization Statement:

Allocate the Job Experience Collection file with a DSORG of PS (Physical Sequential). PCS forces the file attributes RECFM=F and BLKSIZE=4096.

Here is a typical DD statement allocating the Job Experience Collection file:

The approximate size of the file can be estimated with the formula:

X(504 + 200Y)where:

X = number of Job Instances for which data is collected before the file wraps.

Y = average number of steps per Job Instance.

For example:

X = 10000 Job Instances

Y = 5 steps per Job Instance

Job Experience Collection file size in bytes:

10000 (504 + 200(5)) = 15,040,000

15,040,000 / 56,754 = 256 tracks

256 / 15 = 18 cylinders

The first time the PCS control region procedure is started the empty Job Experience Collection file is initialized automatically. The file can be reinitalized using the EXPC=COLD keyword on the TMPCS STC procedure.

Job Experience files

Identify two Job Experience files to PCS using the PCS Initialization Statements:

The Job Experience files are VSAM linear data sets, and can be created with the following IDCAMS JCL:

The Job Experience file size in bytes is estimated by this formula:

X * (168 + Y * (400 + Z *104))where:

X = # of Jobname / ScheduleID combinations that are to be tracked by PCS.

Y = average # of job executions that will be recorded for each Jobname/ScheduleID combination (maximum kept is 15).

Z = average # of steps per job.

For example:

X = 10000 Jobname / ScheduleID combinations

Y = 15 executions recorded

Z = 5 steps per job

The Job Experience file size in bytes:

10000 * ( 168 + 15 * (400 + 5 * 104 )) = 139,680,000 bytes

139,680,000 / 5 6,754 = 2,462 tracks

2,462 / 15 = 165 cylinders

Both Job Experience files should be the same size.

Initialize both Job Experience files with the utility program DTMPEFCn, which initializes the files with zero jobs. Here is an example of the JCL:

Battle Plan file

The Battle Plan file is a VSAM linear file that is used to maintain the Active Battle Plan. Identify the Battle Plan file to PCS using the PCS Initialization Statement:

Allocate the Battle Plan file using the following IDCAMS JCL:

To estimate the size of the Battle Plan file, refer to the following table.

Once you have created the Battle Plan file, the first time the PCS control region is started this file is initialized automatically. The file can be initialized using the BPF=COLD keyword on the TMPCS STC procedure.

Application Management Database (AMD)

The AMD is allocated using the TMISPF dialog for PCS and no action is required at this time. Details are described in the BMC AMI Ops Automation for Batch ThruPut PCS Usage Guide.

10.4. Start the PCS control region

Use the MVS START command to start the PCS control region.

Once the PCS control region has started, messages are issued regarding the initialization of the PCS files. Message "DTM0023I TM/PCS (CAnn) Initialization Complete" is issued to signify that the control region has started successfully.

10.5. Define PCS class

When in Managed Mode, BMC AMI Ops Automation for Batch ThruPut uses a single JES2 JOB class to manage the Production Batch. Use the TM CLASS command to define this class to the BMC ThruPut Manager started task.

10.6. Verify installation is complete

The PCS D Level and PCS D PARMS commands may be used to verify that the task is responding normally.

PCS is now installed and active.

10.7. Set up the Collection file utility

This step is not required to bring up the control region, but is required to collect experience data.

10.7.1. Job Experience file housekeeping

PCS creates transaction records that are written to the Job Experience Collection file. These records are used to maintain the Job Experience file, using the DTMWDXn Extract and DTMPEFUn Update utilities. This task should be scheduled regularly, at least once daily. A sample job (PCSEXPUn) is included in the TM Install data set. The job consists of three steps as follows:

• Step 1: DTMWDXTn Extract utility selects records from the Job Experience Collection file - The Extract utility DTMWDXTn is used to extract some or all of the records from the Job Experience Collection file and copy them as variable length records (RECFM=VB) to one of two Job Experience files (sequential files). Records maintain their original length and the data is an exact replica of the original data that was written to the Job Experience Collection file.
• Step 2: Sort the records by jobname/CA 7 schid - The extracted Job Experience Collection file records must be sorted before being used as input to the Job Experience file Update utility DTMPEFUn. These sorted records are then used to update the appropriate Job Experience file.
• Step 3: DTMPEFUn Update Utlity - As input, the Update utility combines the extracted records with records from the most recently updated (active) Job Experience file. The oldest (inactive) Job Experience file is automatically selected as output. Because the Update utility only reads from the active Job Experience file, it can run while PCS is active.

The Job Experience Collection file is a wrap-around file, so it can never run out of space, however data (transactions) are eventually overwritten. To avoid data loss, you must use the Extract utility to copy the records to the oldest of two rotating Job Experience files, essentially emptying the Job Experience Collection file. The records are then sorted and used as input to update the appropriate Job Experience file.

10.7.2. Monitor Job Experience Collection file space

The PCS control region issues warning messages when the Job Experience Collection file reaches 80%, 90%, and 100% full since the last data transfer:

DTM8203W EXPERIENCE COLLECTION : nn PERCENT USED SINCE THE LAST DATA EXTRACTIONWhen the usage exceeds 100%, the oldest transactions are overwritten with the newest transactions. It is therefore important to extract the data before this occurs. The warning messages can serve as triggers for automated commands to accomplish this.

Sample extract and update utility JCL

The Extract utility DTMWDXTn is used to extract some or all of the records from the Job Experience Collection file and copy them as variable length records (RECFM=VB) to one of two Job Experience files (sequential files). Records maintain their original length and the data is an exact replica of the original data that was written to the Job Experience Collection file.

The extracted Job Experience Collection file records must be sorted before being used as input to the Job Experience file Update utility DTMPEFUn. These sorted records are then used to update the appropriate Job Experience file.

As input, the Update utility combines the extracted records with records from the most recently updated (active) Job Experience file. The oldest (inactive) Job Experience file is automatically selected as output. Because the Update utility only reads from the active Job Experience file, it can run while PCS is active.

The following sample JCL (member PCSEXPUn in the install data set) extracts transaction records from the Job Experience Collection file, sorts them, and then updates the appropriate Job Experience file. The sample JCL includes the extraction, sort, and update steps.

where:

PARMS='FROMLAST'Requests that the utility extract the transactions beginning with the first transaction that was not previously extracted.

INPUTIs the Job Experience Collection file. The data set name should match the data set name specified in the PCS Initialization Statement FILE EXPERIENCE_ COLLECTION.

OUTPUTIs the temporary sequential file to which the extracted records are written using BSAM. This file is used as input to the SORT step.

where:

SORTINIs the output file from the EXTRACT step.

SORTOUTIs the temporary output file used as input to the UPDATE step.

where:

EXPFILAIs one of the PCS Job Experience files defined in the PCS Initialization Statements.

EXPFILBIs the other PCS Job Experience file defined in the PCS Initialization Statements.

PEFTRANIs the output file from the SORT step.

PEFWORKIs a temporary work file.

Once the update has completed successfully, issue the PCS SELECT EXP operator command to activate the updated Job Experience file in PCS. Alternatively, automate this task as a fourth step in the Experience Update Utility JCL.

10.8 PCS Forecast Collection Utility

The PCS Forecast Utility (DTM4CSTn) communicates with CA 7 to populate the AMD with upcoming scheduled jobs and their relationships to one another. The utility should be scheduled to run after CA 7 changes are complete and prior to the start of the next PCS production cycle.

The utility requires the name of the name of the AMD to be updated is provided through the PARM field and it must execute where the CA 7 scheduler the PCS task is to support, is also executing.

The utility uses the CA 7 API CAL2X2WP to request the relevant data. If this is not in a linklist library then a STEPLIB pointing to it must also be included.

Sample JCL is as follows (see member PCSGDATA in the TM Install data set):

where:

AMD=AMDdsnameSpecifies the name of the AMD to be updated. This keyword is mandatory.

DTMCA7R DDProvides information on the Forecast process and is useful in the event there is a problem. The DD is mandatory unless the NOLOG.

Installations running CA 7 R12 can see improved run times for this process if they activate RUN-DBSQLDR option and add required DD statements to the forecast JCL. PCSGDATA in the INSTALL data set provides a sample. See the PCS Usage Guide appendices for detailed information.