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

Document ID:  TEC1813555
Last Modified Date:  08/08/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details


  • CA JCLCheck Workload Automation


  • CA JCLCheck Workload Automation:Release:12.0
  • CA JCLCheck Workload Automation:Release:12.0.0


  • CA JCLCheck workload Automation:JCLCHK

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


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



The ALTIDD=N will prevent CA Endevor from applying the CA Endevor alternate ID during the processing of JCLCheck.  The ID used will be USERID value in the CA JCLCheck runtime option. 



Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255


Not what you were looking for?

Search Again >

Product Information

Support by Product >


Join a Community >