Does Endevor support REFERBACK coded in a Processor?

book

Article ID: 140832

calendar_today

Updated On:

Products

CA Endevor Software Change Manager (SCM) CA Endevor Software Change Manager - Natural Integration (SCM) CA Endevor Software Change Manager - ECLIPSE Plugin (SCM) CA Endevor Software Change Manager - Enterprise Workbench (SCM)

Issue/Introduction

I produced some test JCL which created the temporary file as:

//SYSUT2    DD DISP=(NEW,PASS,DELETE),         

//             LRECL=80,BLKSIZE=0,RECFM=FB,    

//             SPACE=(TRK,(1,5),RLSE)          

 

Then referenced in a later step as:

//SYSUT1    DD DSN=*.TEST01.SYSUT2,            

//             VOL=REF=*.TEST01.SYSUT2,        

 

In standard JCL this did work and produced two unique temporary datasets:

SYS19330.T101818.RA000.TTOSJWL2.R0545973

SYS19330.T101818.RA000.TTOSJWL1.R0747508             

 

Can we use REFERBACK in an Endevor Processor and expect it to act in the same way?

 

Environment

Release : 18.0

Component : CA Endevor Software Change Manager

Resolution

REFERBACK being used in an Endevor Processor it is not supported - See the below reference from the processors section of the documentation (https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-mainframe-software/devops/ca-endevor-software-change-manager/18-0/administrating/processors/unsupported-parameters.html)

EXEC Statement Parameters

CA Endevor Software Change Manager

 processors support the EXEC statement, but they do not support backward reference (REFERBACK), or these EXEC statement parameters:

  • ACCT
  • ADDRSPC
  • CCSID 
  • DYNAMNBR
  • MEMLIMIT
  • PARMDD 
  • PERFORM
  • PROC
  • RD
  • REGION
  • REGIONX
  • RLS
  • TMOUT 
  • TIME