Procedure for setting up EXTERNAL DATASET TRACKING/TRIGGERING with CA 7 Workload Automation.
Article ID: 24108
Updated On:
Products
Issue/Introduction
This Knowledge Document describes procedures for setting up EXTERNAL DATASET TRACKING/TRIGGERING.
Environment
Component: 7
Resolution
Procedure for setting up external dataset triggering
External Data Set Tracking/Triggering is a CA 7 Workload Automation feature that allows you to track data sets not created under CA 7 Workload Automation control. Tracking these data sets gives you the opportunity to perform external data set posting or job triggering. In order to have an external data set be used for posting for triggering you must first define the data set to the CA 7 Workload Automation database. Once this definition has occurred and the table properly loaded, CA 7 Workload Automation will then monitor the system for SMF 15 records containing your data set.
This document is intended to be a quick reference for setting up this process. For job triggering to occur for these data sets, you perform the following steps. Each step is further described below.
STEP 1. Define the dataset to the SASSXDSN table.
STEP 2. Define the job to CA 7 Workload Automation (DB.1 Job Definition screen entry).
STEP 3. Define the data set to CA 7 Workload Automation as NORM (DB.6 Data Set Definition screen entry).
STEP 4. Set up the data set trigger (DB.2.6 Data Set Triggering screen entry).
STEP 5. Refresh LLA.
STEP 6. Reinitialize CAS9 to load SASSXDSN.
STEP 1: Define the dataset to the SASSSXDSN table.
The External Data Set Tracking Criteria Table is comprised of one or more $L2XDSN macro calls. After the module is coded, it must be assembled and linked. The module must be accessible to the CAIRIM procedure and identified using the XDSN parameter in the CA 7 Workload Automation System Configuration File.
For a sample SMP USERMOD to create the table, see member AL2UM37 in CAL2OPTN.
Here is an example of a SASSXDSN exit:
----+----1----+----2----+----3----+----4----+----5----+
COLUMN 10 16
| |
TITLE 'EXTERNAL DATA SET TRACKING CRITERIA'
SASSXDSN START
PRINT ON
$L2XDSN JOB=ABCDE
$L2XDSN DSN=TEST.DATA.SET
$L2XDSN JOB=STC1,DSN=TRANSMIT.6
$L2XDSN DSN=PROD.D???.DATA
END
Note: If you are tracking external jobs/tasks and also tracking data sets in those jobs/tasks, you must specify RQMT=Y and TRIG=Y in the SASSEXTT definitions for those jobs/tasks.
Also, you have the ability to mask your data set names. You can use a question mark (?) to mask the length of a node, and/or you can use an asterisk (*) to mask the end of the data set name.
REMEMBER: you must assemble and link SASSXDSN to the correct CA 7 load library when done.
STEP 2: Define the job to CA 7 (DB.1 Job Definition screen entry).
Example:
------------------------- CA-7 CPU JOB DEFINITION -----------------------
FUNCTION: ADD (ADD,DELETE,DD,PURGE,DELPRRN,FORMAT,LIST,UPD)
JOB: JOB1A
GENERAL: SYSTEM: JOBNET: LVL1 OWNER: LVL1 UID: 10
JOBL:
JCL: ID: 0 MEMBER: JOB1A RELOAD: Y EXEC: N RETAIN-JCL: N
LIB:
REQUIREMENTS: HOLD: N JCL-OVRD: N USE-OVRD-LIB: N VERIFY: N MAINT: Y
SATISFACTION LEAD-TIME: JOB: 0 DSN: 0 ARFSET:
EXECUTION: MAINID: ALL INSERT-RMS: N COND-CODE: 4 RO: LT
DONT SCHEDULE -- BEFORE: 00000 0000 AFTER: 99999 0000
MESSAGES: LTERM: REQUIREMENT-LIST: Y PROMPTS: N
ERROR MSGS -- RQMTS NOT USED: Y DSN NOT FOUND: Y
RESOURCES: REGION: 0 CLOCK-TIME: 0000 CPU-TIME: 00010
CLASS: PRTY: 000 MSGCLASS: DRCLASS:
TAPE DRIVES...TYPE1: 001 M 000 C TYPE2: 000 M 000 C
PROGRAM: SM20 MSG-INDX: 00 -- DB.1 -- 22.125 / 10:12:53
MESSAGE: ADD SUCCESSFUL, DEFAULTJOB USED FOR DEFAULT VALUES
STEP 3: Define the data set to CA-7 as NORM (DB.6 Data Set Definition screen entry).
Example:
------------------------- CA-7 DATA SET DEFINITION -------------------------
FUNCTION: ADD (ADD,DELETE,FORMAT,LIST,RENAME,UPD)
DSN: TEST.DATA.SET DSNBR: 83
NEWNAME:
TYPE: NORM GDG: N
SMF FEEDBACK REQUIRED: Y POST AT CLOSE TIME: N
DEVICE:
DSORG:
RECFM:
LRECL: 0
BLKSIZE: 0
PROGRAM: SM30 MSG-INDX: 00 -- DB.6 -- 22.125 / 10:15:27
MESSAGE: ADD FUNCTION SUCCESSFUL
STEP 4. Set up the data set trigger (DB.2.6 Data Set Triggering screen entry).
Example:
------------------------- CA-7 DATA SET TRIGGERING -------------------------
FUNCTION: UPD (FORMAT,LIST,UPD) PAGE 0001
DSN: TEST.DATA.SET DSNBR: 83
OPT SCHID TRGD-JOB TRGID DOTM QTM LDTM SBTM *---- EXCEPTIONS ----*
a 000 JOB1A 000 0010
OPTIONS: A=ADD,D=DELETE,U=UPDATE,*=PROCESSED,?=ERROR
PROGRAM: SM75 MSG-INDX: 00 -- DB.2.6 -- 22.125 / 10:21:09
MESSAGE: UPD FUNCTION SUCCESSFUL
STEP 5. Refresh LLA.
When updating members in LNKLST (linklist) datasets, always remember to refresh LLA's directory table after completing the updates if you want to have the changes take effect immediately. Use the MODIFY LLA command to change LLA dynamically. Key in: MODIFY LLA,REFRESH.
STEP 6. Reinitialize CAS9 to load SASSXDSN.
- Create a new member in your L2OPTS PDS called XDSNUPD and it will have the following control card: CA71 UPDATE XDSN(SSASXDSN).
- Change the CAS9 CAIRIM procedure to point to the new L2OPTS file AND change the RIMPARM to be just the CA 7 Workload Automation statement (remove the KEYS and AUTOCMDS).
- Next you will run CAS9 (CAIRIM) to load the new table using the following OS command: S CAS9,L2OPTS=XDSNUPD
The following is a sample JCL for CAS9(CAIRIM):
//CAIRIM EXEC PGM=CAIRIM,REGION=0M
//STEPLIB DD DISP=SHR,DSN=your.common.services.loadlib
// DD DISP=SHR,DSN=your.CA7.loadlib
//PARMLIB DD *
PRODUCT(CA-7) VERSION(L2C1)
//L2OPTS DD *
CA71 UPDATE XDSN(SASSXDSN)
//KEYS DD DISP=SHR,DSN=your.lmp.codes.dsn
//
TROUBLESHOOTING:
- Reply to ICOM's WTOR with D=EXTDSN to make sure you see your newly added data set names.
- Perform the top-line command in CA 7, LCTLG,DSN=data.set.name (If CA 7 received the SMF type 15 record, the DATE and TIME the data set was created or updated appears here).
Feedback
