OnDemand User Group

Tips and Tricks => Tips and Tricks => Topic started by: Ed_Arnold on November 06, 2020, 08:36:31 AM

Title: z/OS - Using system symbols as indexing parameters
Post by: Ed_Arnold on November 06, 2020, 08:36:31 AM

Environment: 

JES2 MAS

Output can be ingested into CMOD from spool from any system in the MAS

Requirement:

Make the system that created the output part of the indexing parameters.

The hard way:

This information is available in fields reachable via exits

The easier way:

Exploit using symbols in JES in-stream data

Have the load job be the last step in the job that creates the output.

The ARSLOAD step parms:

//CMODSTEP EXEC PGM=ARSLOAD,REGION=0M,
//         PARM='/-V //DD:PARM'   
.
.
The JCL contains this DD:
 
//PARM   DD DISP=SHR,DSN=IBM.ARS.PARMFILE
 
- In IBM.ARS.PARMFILE are these parms:
 
-h       
 ARCHIVE 
 -a       
 BANK     
 -g       
 BANK     
 -u       
blahblah   
 -p       
 ******** 
 -v       
 -s       
 OBJINPT   
 -j                  <===== These are the key parameters         
 '//DD:J'            <=====
 /dev/null
 
The DD definition for J:
 
//J      DD *,SYMBOLS=EXECSYS                     
FIELD7='&SYSNAME'                                     
INDEX2=X'E2E8E2D5C1D4C5',FIELD7,(TYPE=GROUP,BREAK=YES)
/*

Note the index on SYSNAME, which has been added as an index field in the AG definition.   
 
Then when you run the load job you will see these messages indicating that the field added via the -j parm has been recognized by the indexer:

ARS5481I FIELD7='MVS222'                                       
ARS5481I INDEX2=X'E2E8E2D5C1D4C5',FIELD7,(TYPE=GROUP,BREAK=YES)     
 
After loading the data, when you view the application group data table, you will see the new index called SYSNAME appended as the last column:
 
SYSNAME
--------
MVS222 

Per the MVS JCL Reference you could use any system symbol.