How to list and update Processor Group symbolic in Endevor Batch

Products

• Endevor

Issue/Introduction

Sites may need to update a lot of symbolic overrides in processor group definitions, and using the panels to do that can be problematic.

Examples of this include adjusting for a new compiler version, or porting processor groups to a new inventory location.
In all these cases, it would be useful to do these changes in batch, as described below. 

                             

Resolution

LIST PROCESSOR GROUPS

The LIST Element is a function of the Endevor CSV utility, and is recommended to obtain the processor group information. JCL sample found at *.CSIQJCL(BC1JCSVU)

Use the  LIST PROCESSOR GROUP function to extract processor group information from the MCF that satisfies your criteria. 
The output report can be sent to a sequential file, then create an Excel Spreadsheet to review all the information. 
Note the LIST JOB should be submitted via batch job.

Here is a JCL sample: 

//STEP1    EXEC PGM=NDVRC1,REGION=4M,
//         PARM='CONCALL,DDN:CONLIB,BC1PCSV0'
//STEPLIB  DD DISP=SHR,DSN=your.endevor.CSIQAUTU
//         DD DISP=SHR,DSN=your.endevor.CSIQAUTH
//CONLIB   DD  DISP=SHR,DSN=your.endevor.CSIQLOAD
//CSVLST   DD DSN=your.csv.dataset,
//         DISP=(NEW,CATLG,DELETE),
//         DCB=(DSORG=PS,RECFM=VB,LRECL=4092),
//         SPACE=(CYL,(5,5),RLSE)
//CSVMSGS1 DD SYSOUT=*
//C1MSGSA  DD SYSOUT=*
//BSTERR   DD SYSOUT=*
//SYMDUMP  DD DUMMY
//SYSUDUMP DD SYSOUT=*
//CSVIPT01 DD *
LIST PROCESSOR GROUP '*' TO FILE 'CSVLST'
    FROM ENV *
         SYS *
         TYP *
         STA *
    OPTIONS PATH PHYSICAL SEARCH RETURN ALL .

Note that the LIST example added above will search for:
All processor Groups
From all ENVironments, all SYStems, all TYPes and all STAges.
Feel free to edit it as desired.

UPDATING PROCESSOR GROUPS VIA BATCH

For this purpose, use the batch maintenance utility ENBE1000 - JCL sample found at *.CSIQJCL(ENBE1000).
- Use Build SCL for Processor Symbol Syntax to extract the existing definitions in form of DEFINE PROCESSOR SYMBOL statements.

1) Run the JCL sample below with the BUILD statement, so it would create a list of DEFINE statements that will be used on step 2.

//********************************************       
//* BUILD STATMENTS FOR PROCESSOR GROUPS             
//********************************************       
//*                                                  
//ENBE1000 EXEC PGM=NDVRC1,                          
//             PARM='ENBE1000',                       
//             REGION=4096K                                                     
//STEPLIB  DD DISP=SHR,DSN=your.endevor.CSIQAUTU
//         DD DISP=SHR,DSN=your.endevor.CSIQAUTH
//CONLIB   DD DISP=SHR,DSN=your.endevor.CSIQLOAD
//SYSPRINT DD SYSOUT=*                               
//SYSOUT   DD SYSOUT=*                               
//SYSTERM  DD SYSOUT=*                               
//C1MSGS1  DD SYSOUT=*                                
//C1MSGS2  DD SYSOUT=*      
//SYSUDUMP DD SYSOUT=*                       
//SYMDUMP  DD DUMMY                          
//BUILD1   DD DSN=your.build.output,   
//         DISP=(NEW,CATLG,DELETE),          
//         DCB=(DSORG=PS,RECFM=VB,LRECL=4092),
//         SPACE=(CYL,(5,5),RLSE)            
//ENESCLIN DD *                              
BUILD SCL FOR PROCESSOR SYMBOL               
FROM ENVIRONMENT "environmentname"                  
SYSTEM *                        
TYPE *                                       
STAGE ID *                                   
PROCESSOR GROUP *                            
TO DDNAME "BUILD1" .         

Note that it is possible to use * or add the actual name. Tailor this job according to the needs.



2) Once the job above completed successfully and the DEFINE statements has been created:
- Edit the ouput dataset (your.build.output) created above, with the new information required.

This is one example on how the DEFINE statement might be:

DEFINE PROCESSOR SYMBOL                                 
    TO ENVIRONMENT 'SMPLTEST'                           
       SYSTEM 'FINANCE'                                 
       TYPE 'COBOL'                                     
       STAGE NUMBER 1                                   
       PROCESSOR GROUP 'CLENBL'                         
       PROCESSOR TYPE = GENERATE                        
    SYMBOL PRMXCOB2="CODEPAGE(500)"
.                                 

The syntax is SYMBOL symbolicname=”newvalue”
Note that more symbolics could be added within the same Define statement, such as:
SYMBOL PRMXCOB2="CODEPAGE(500)"
SYMBOL CSYSLIB3="uprfx.uqual.FINANCE.&C1SU..S3.COPYLIB"
SYMBOL CSYSLIB4="uprfx.uqual.FINANCE.&C1SU..S4.COPYLIB" 


3) Once the editing of the DEFINE statement  described above is finished, double check the information entered, as this will be the input for the changes that will be done on Endevor.

4) Once the information is correct, use the JCL sample bellow to submit the job which will update Endevor:

//********************************************       
//* DEFINE/UPDATE PROCESSOR GROUPS             
//********************************************       
//*                                                  
//ENBE1000 EXEC PGM=NDVRC1,                          
//             PARM='ENBE1000',                       
//             REGION=4096K                                                     
//STEPLIB  DD DISP=SHR,DSN=your.endevor.CSIQAUTU
//         DD DISP=SHR,DSN=your.endevor.CSIQAUTH
//CONLIB   DD DISP=SHR,DSN=your.endevor.CSIQLOAD
//SYSPRINT DD SYSOUT=*                               
//SYSOUT   DD SYSOUT=*                               
//SYSTERM  DD SYSOUT=*                               
//C1MSGS1  DD SYSOUT=*                                
//C1MSGS2  DD SYSOUT=*      
//SYSUDUMP DD SYSOUT=*                       
//SYMDUMP  DD DUMMY                            
//ENESCLIN DD DSN=your.build.output


- Submit the batch job which will update the processor groups with the new information.