How to update processor group for a whole environment
Article ID: 258976
Updated On:
Products
Issue/Introduction
The processor group execution is limited to allow delete processor in batch execution only.
How to change the processor group option to allow foreground execution for delete processor?
Environment
Component : ENDEVOR
Version : all
Resolution
For this purpose, use the batch maintenance utility ENBE1000 - JCL sample found at *.CSIQJCL(ENBE1000).
- Use Build SCL for Processor Group Syntax to extract the existing definitions in form of Define Processor Group Syntax 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
//SCLOUT DD DSN=your.build.scl.output,
// DISP=(NEW,CATLG,DELETE),
// DCB=(DSORG=PS,RECFM=VB,LRECL=4092),
// SPACE=(CYL,(5,5),RLSE)
//ENESCLIN DD *
BUILD SCL FOR PROCESSOR GROUP *
FROM ENVIRONMENT "environmentname"
SYSTEM *
TYPE *
STAGE ID *
TO DDNAME "SCLOUT" .
Note that it is possible to use *, a mask or the processor group 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.scl.output) created above, with the new information required.
This is one example on how the DEFINE statement might be from SCLOUT file:
DEFINE PROCESSOR GROUP '*NOPROC*'
TO ENVIRONMENT 'SMPLTEST'
SYSTEM 'FINANCE'
TYPE 'COBOL'
STAGE NUMBER 1
DESCRIPTION "ASSEMBLER MACROS AND COPY BOOKS"
PROCESSOR OUTPUT TYPE "TEST1 *NOPROC*"
NEXT PROCESSOR GROUP '*NOPROC*'
GENERATE PROCESSOR NAME IS '*NOPROC*'
ALLOW FOREGROUND EXECUTION
MOVE PROCESSOR NAME IS '*NOPROC*'
ALLOW FOREGROUND EXECUTION
DELETE PROCESSOR NAME IS '*NOPROC*'
DO NOT ALLOW FOREGROUND EXECUTION
.
The option “DO NOT ALLOW FOREGROUND EXECUTION“ must be replaced by “ALLOW FOREGROUND EXECUTION” in order to allow foreground execution of the DELETE PROCESSOR, to do so, research SCL “DELETE PROCESSOR NAME” and remove the words ‘DO NOT’ in the following line.
Warning: The use of EDIT command “REPLACE ’DO NOT ALLOW FOREGROUND EXECUTION’ ’ALLOW FOREGROUND EXECUTION’ ALL” will allow the foreground execution of all processor, i.e. GENERATE, MOVE and DELETE.
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.scl.output
- Submit the batch job which will update the processor groups with the new information.
Feedback
