OPSREST: Unable to submit API event. Reason = 'rc=255, type=Errmsg, msg=Internal error. (rc=255)

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

Getting the following error trying some of the OPSREST endpoints from the Swagger page:

Error: response status is 400

Response body

Download

 

Error: response status is 400

Response body
Download
{
  "messages": [
    {
      "messageType": "ERROR",
      "messageNumber": "OPS$6392",
      "messageContent": "Unable to submit API event. Reason = 'rc=255, type=Errmsg, msg=Internal error. (rc=255)'",
      "messageKey": "com.ca.automation.opsmvs.rest.submitEventException",
      "messageParameters": [
        "rc=255, type=Errmsg, msg=Internal error. (rc=255)"
      ],
      "messageInstanceId": "03a83d92-4c93-42cd-810e-4e26f9e3142f",
      "messageComponent": "com.ca.automation.opsmvs.rest.api.RestExceptionHandler",
      "messageSource": "hostname:port:bcmopsrestsysplex"
    }
  ]

The OPSRest.log file shows additional symptoms if DEBUG is enabled:

DEBUG WebSvcUtil.zOSRunRexxGet: TRACEMSG = OPRShttp.rex executing 'CAI.OPS.CCLXEXEC(OPRSAOF)' POST OPSS event   EVTCODE('WSAPIEVT') EVTTEXT('The text of the event.')
DEBUG WebSvcUtil.zOSRunRexxGet: TRACEMSG = OPS9999T OPRShttp.rex: execute complete; rc:-3
DEBUG WebSvcUtil.zOSRunRexxGet: TRACEMSG = OPS9999T OPRShttp.rex: ended; RC=-3 ETIME=0.018 SUBSYS=OPSS

 

Environment

OPS/MVS

Cause

The RC=-3 running an OPS/REXX program may be caused by the fact that the OPSREST started task doesn't have access to the CCLXLOAD library through LNKLST or STEPLIB.

Resolution

Add the CCLXLOAD library to the STEPLIB concatenation of the OPSREST started task or to the system LNKLST.