Why is CA JCLCheck not using SIGNON USERID when validating JCL with use of CA ENDEVOR?

Article Id: 15468
Status: Published
Updated On: 14-02-2018 07:49
Legacy Id: TEC1813555
Products:
CA JCLCheck Workload Automation
Issue/Introduction:



Why is CA JCLCheck not using the SIGNON USERID value when validating JCL with use of CA ENDEVOR?

Environment:

Release:
Component: JCLCHK

Resolution:

When running CA JCLCheck under the CA Endevor processor with the alternate ID feature, and also using the CA JCLCheck SIGNON option, you will need to use option ALTID=N.  

Example:
//JCLC EXEC PGM=JCLCHECK,ALTID=N 

 

The Endevor's ALTID=N option will prevent CA Endevor from applying the CA Endevor alternate ID during the processing of JCLCheck.  This allows JCLCheck to use the USER= value on the JOB statement of the validating JCL, or the USER(userid) in the CA JCLCheck runtime option for security validation. 

 

 

Additional Information:

- CA JCLCheck USER(userid) option:
https://docops.ca.com/display/CJWA12/USER

- CA JCLCheck SIGNON option: 
https://docops.ca.com/display/CJWA12/SIGNON

- CA JCLCheck SECURITY option:
https://docops.ca.com/display/CJWA12/SECURITY

- CA Endevor Alternate ID feature: 
https://docops.ca.com/ca-endevor-SCM/18-0/en/securing/data-set-security#DataSetSecurity-HowtoActivatetheAlternateID