OS/390 Job executes JCL defined in Process Tab, even if JCL Type is "OS/390"

book

Article ID: 195709

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic Workload Automation - Automation Engine

Issue/Introduction

In OS/390 jobs if we select Type as OS/390 JCL then the Job JCL is taken from the OS/390 system and it is not defined in the Automation Engine. But the job executes the JCL defined in the process tab which should not be the case.

Steps to reproduce

In OS/390 section the type is selected as OS/390 JCL

For testing purposes, there is some JCL in the process tab, but this should not be considered in the script:

//* DIESER STEP KOMMT AUS DEM AUTOMIC SCRIPT
//STEP1  EXEC   PGM=XXXXX

Execute the job

In the generated job we can see the JCL inserted in the process tab

//JMLDS    EXEC PGM= ,COND=EVEN,
// PARM='TRAP(OFF)/JNR=1111111 MNR=100 PNR=0 IPA=
//             TYP=S DBG=0 RET=&RETCODE 2>&1'
//STEPLIB  DD  DISP=SHR,DSN= 
//SYSPRINT DD SYSOUT=*
// SET RETCODE='HIGHEST'
//* <-------- END_HEADER -------->
//* DIESER STEP KOMMT AUS DEM AUTOMIC SCRIPT
//STEP1  EXEC   PGM=XXXXX


//* <------- BEGIN_TRAILER ------>
//JMLDE    EXEC PGM= ,COND=EVEN,REGION=64M,
// PARM='JNR=1111111 MNR=100 PNR=0 IPA=
//             TYP=E STP=1 RET=&RETCODE 2>&1'
//STEPLIB  DD  DISP=SHR,DSN= 
//SYSPRINT DD SYSOUT=*
//*

Environment

Automic Engine version '12.3.3+build.1591966211565

Resolution

This as a bug. This will be fixed in a future release.

Customers are invited to register into the Support Portal to get information about products/features and new fixes will be referenced accordingly.