JCLCheck REST API - Error CAY6Z17 in job AJ6ZJCKD.

Products

• JCLCheck Workload Automation

Issue/Introduction

During JCLCHECK REST API setup, executing the check dataset API generate the following error: 

{
  "messages": [
    {
      "messageType": "ERROR",
      "messageNumber": "CAY6Z17",
      "messageContent": "Pipe communication failure. RC=51. Details follow:\nFail:  caz1zjni:1028 Failed to spawn child = './lib/caz1zsvr'. errno = 129. Reason: EDC5129I No such file or directory.\n\nMessages also sent to job's SYSPRINT.",
      "messageKey": "com.broadcom.jclcheck.JclCheckCommException",
      "messageParameters": [
        51,
        "Fail:  caz1zjni:1028 Failed to spawn child = './lib/caz1zsvr'. errno = 129. Reason: EDC5129I No such file or directory.\n"
      ],
      "messageInstanceId": "22353f14-fc19-4533-afa8-6fc537abc178",
      "messageComponent": "com.broadcom.jclcheck.api.v1.handler.JCLCheckControllerExceptionHandler",
      "messageSource": "secure3.os390.ao-srv.com:8560:cajclcheck"
    }
  ]
}              

 

Environment

Component: JCLCheck Workload Automation

Release: 12.0

Cause

The issue is caused by running a version of job AJ6ZJCKD not in sync with the product maintenance deployed. The maintenance applied introduced enhancements to JCLCheck, including modifications to job AJ6ZJCKD. After applying the maintenance, the new source of AJ6ZJCKD wasn't deployed to runtime libraries and the old version of the job was being run.

PTFs SO11500 and SO15115  have updated job AJ6ZJCKD from the CAZ2JCL library.

Resolution

Review and run job AJ6ZJCKD from the most current CAZ2JCL library.  

The JCLCheck load library also needs to have Program Control granted on the system. Otherwise the application will fail with security errors.

 

 

 

Additional Information

For more information regarding job AJ6ZJCKD, please read the Configure and Deploy the JCLCheck REST API.

For more information regarding the Program Control, please read the Manage JCLCheck Program Control.