Setting Up a Test Environment for CA Jobtrac Job Management
search cancel

Setting Up a Test Environment for CA Jobtrac Job Management

book

Article ID: 28123

calendar_today

Updated On:

Products

Jobtrac

Issue/Introduction

CA-Jobtrac Job Management is designed to help you in this situation where the environment is limited to one LPAR for both test and production.   There are considerations to be made whether you have one or multiple systems.

If you have only one production LPAR an easy way to solve this dilemma would be to have two occurrences of CA-Jobtrac, one for production and the other for test. You must make sure that each occurrence of CA-Jobtrac has its own checkpoint, history and capture files. Each occurrence requires different tokens (DDNAMES) for the checkpoint and history files. Each occurrence of CA-Jobtrac will also need its own CA GSS subsystem. Only one occurrence of CA GSS can execute program GSSMAIN. Therefore, the other CA GSS subsystem must run program SRVSYS. 

 

Environment

Release: JOBT..00200-11-Jobtrac-Job Management
Component:

Resolution

 

Below is a table of items for the settings necessary to run two occurrences of CA-Jobtrac on one LPAR. Each occurrence of CA-Jobtrac will have its own libraries.

Item

Production System

Test System

CA-Jobtrac started task name

JOBTRAC3

JOBTRAC5

CA-GSS

GSSA, pgm=GSSMAIN

GSSB, pgm=SRVSYS

Checkpoint DDNAME

JOBTRAC3

JOBTRAC5

History DDNAME

JOBHIST3

JOBHIST5

Sysout Capture DDNAME

CAPTURE

CAPTURE

DATELIB DDNAME

DATELIB

DATELIB

PARMLIB DDNAME

PPOPTION

PPOPTION

STEPLIB

Production CAILIB

Test CAILIB

For sites that have more than one LPAR and are in a shared dasd/spool or Sysplex environment and are using CA-Jobtrac in a Primary/Monitor configuration, there are considerations that need to be made if you wish to setup a test Primary/Monitor environment. The Primary/Monitor implementation requires that all files be shared between the Primary/Monitor systems. Your test Primary/Monitor systems will share a token that cannot match the production token. To implement the test environment all you need to do is install a test CA-Jobtrac on both LPARS. The test Primary/Monitor systems will need to share the checkpoint, history, capture, DATELIB and PPOPTION files and use the same token. You will also need to specify parameters (SYNCSYS1 and SYNCSYS2) in member JOBTRA00 located in the PPOPTION library to denote which CA-Jobtrac is the primary and monitor systems. With this setup you will be able to test a CA-Jobtrac Primary/Monitor environment. 

Below is a table of items needed to setup the Primary/Monitor test environment:

Item

Primary

Monitor

CA-GSS

GSSB, pgm=SRVSYS

GSSB, pgm=SRVSYS

Checkpoint DDNAME

JOBTRAC2

JOBTRAC2

History DDNAME

JOBHIST2

JOBHIST2

Sysout Capture DDNAME

CAPTURE

CAPTURE

PPOPTION Parameter

SYNCSYS1

SYNCSYS2

DASD and SPOOL

Shared

Shared

 

 


 

Additional Information

Additional information on Primary/Monitor setup can be found in chapter 8 of the CA Jobtrac Job Management Planing and Implementation Guide.