z/OS Connect interface codes

z/OS Connect interface codes can be returned in a request.

When an error occurs, the JSON response is as follows:
{
 "Errmsg": "CQD2700E Error bb-ccc ddd Processing request. Extra information: eee",
 "Result": -99bbccc
}
where:
  • CQD is the message prefix, as set by a Data Service server region startup parameter
  • bb is a major error number. See Code categories.
  • ccc is a minor error number
  • ddd is a short description of the error
  • Extra Information: eee provides extra information, if available.
    Note: Extra Information: eee appears only if extra information is available.

The Result number will be a negative number from -9901001 to -9909005. The number has the major and minor error codes in it.

Code categories

The major error codes group the error codes based on processing phases. The following table lists the major error code categories:
Table 1. Code categories
Code category Description
01 Storage error
02 Input data error
Note: There are no minor error codes associated with this category. These messages appear as 02-000.
03 Input vectors error
04 Input JSON parsing error
05 Input JSON interpretation error
06 Processing error
09 Miscellaneous error

Error codes

The tables in this section list the possible errors codes and messages. Corrective action is provided where available. When considering corrective action, note the following points:
  • The Data Service server region parameters can be changed. While the region is running, permanent changes will require changes to be made to the CQDIN00 member.
  • The Data Service server region must be restarted after making changes to the JCL and/or the CQDIN00 member.

Note that with the Data Service service provider in use, the user does not provide the JSON input directly, but rather the service provider will build the input JSON string from the parameters provided by the user. However, the Data Service server interface does not see the original parameters, just the JSON string. Errors related to JSON parsing could reflect something wrong in the original data, or an error in the service provider. Each case would need to be examined individually.

Also, when interpreting the input, some errors may not make sense for the same reason.

The following tables list the possible errors codes, messages, and corrective action, if available. The tables also indicate if Extra information is provided with the error message.

Table 2. Storage errors (01)
Error code Message Description or corrective action Extra information
01-001 No storage for control block (1) No storage for the OPC3 control block  
01-002 No storage for input No storage for the input data etc.  
Table 3. Input data error (02)
Error code Message Description or corrective action Extra information
02-000   Unable to receive input data.  
Note: There are no minor error codes associated with the input data error.
Table 4. Input vectors error (03)
Error code Message Description or corrective action Extra information
03-001 No room left for vector Offset in I/P
03-002 Length in vector header too short Offset in I/P
03-003 Found first vector code but not first vector Offset in I/P
03-004 First vector bad length Offset in I/P
03-005 First vector bad data Offset in I/P
03-006 Found last vector code but not last vector Offset in I/P
03-007 Last vector bad length Offset in I/P
03-008 Last vector bad data Offset in I/P
03-009 Uid vector already seen Offset in I/P
03-010 Uid vector bad length Offset in I/P
03-011 Uid vector bad data Offset in I/P
03-012 Http verb vector already seen Offset in I/P
03-013 Http verb vector bad length Offset in I/P
03-014 Http verb vector bad data Offset in I/P
03-015 Passticket vector already seen Offset in I/P
03-016 Passticket vector bad length Offset in I/P
03-017 Passticket vector bad data Offset in I/P
03-018 Req values vector already seen Offset in I/P
03-019 Req values vector bad length Offset in I/P
03-020 Req values vector bad data Offset in I/P
03-021 Refr url vector already seen Offset in I/P
03-022 Refr url vector bad length Offset in I/P
03-023 Refr url vector bad data Offset in I/P
03-024 Sp cap l vector already seen Offset in I/P
03-025 Sp cap l vector bad length Offset in I/P
03-026 Sp cap l vector bad data Offset in I/P
03-027 Req name vector already seen Offset in I/P
03-028 Req name vector bad length Offset in I/P
03-029 Req name vector bad data Offset in I/P
03-030 Lst ip @ vector already seen Offset in I/P
03-031 Lst ip @ vector bad data Offset in I/P
03-032 Usr ip @ vector already seen Offset in I/P
03-033 Usr ip @ vector bad data Offset in I/P
Table 5. Input JSON parsing errors (04)
Error code Message Description or corrective action Extra information
04-001 No data (or all white space) Offset in I/P
04-002 No opening { Offset in I/P
04-003 Trailing data after } Offset in I/P
04-004 Unexpected end-data Offset in I/P
04-005 No space in storage area Offset in I/P
04-006 Too much nesting Offset in I/P
04-007 Unrecognized json node Offset in I/P
04-021 Object - eod after { Offset in I/P
04-022 Object - expected : Offset in I/P
04-023 Object - no data after : Offset in I/P
04-024 Object - no data after value Offset in I/P
04-025 Object - no data after , Offset in I/P
04-026 Object - expected , or } Offset in I/P
04-027 Object - null name Offset in I/P
04-028 Object - expected " after , Offset in I/P
04-029 Object - duplicate name Offset in I/P
04-031 Array - eod after [ Offset in I/P
04-032 Array - no data after value Offset in I/P
04-033 Array - no data after , Offset in I/P
04-034 Array - expected , or ] Offset in I/P
04-035 Array - found ] after , Offset in I/P
04-041 Word - unrecognized Offset in I/P
04-051 String - no data Offset in I/P
04-052 String - no closing quote Offset in I/P
04-053 String - no character after \ Offset in I/P
04-054 String - no xxxx after \u Offset in I/P
04-055 String - invalid xxxx after \u Offset in I/P
04-056 String - unrec character after \ Offset in I/P
04-057 String - bad 2-byte sequence Offset in I/P
04-058 String - bad 3-byte sequence Offset in I/P
04-059 String - bad 4-byte sequence Offset in I/P
04-060 String - > 4-byte sequence Offset in I/P
04-061 String - control character found Offset in I/P
04-071 Number - nothing after - Offset in I/P
04-072 Number - no integer part or too large Offset in I/P
04-073 Number - nothing after . Offset in I/P
04-074 Number - no fraction part or too long Offset in I/P
04-075 Number - nothing after e Offset in I/P
04-076 Number - nothing after exponent sign Offset in I/P
04-077 Number - exponent value missing or too long Offset in I/P
04-078 Number - exponent too large Offset in I/P
04-079 Number - leading zeros Offset in I/P
04-090 Value - character after value is invalid Offset in I/P
04-099 unknown json parsing error Offset in I/P
Table 6. Input JSON interpretation errors (05)
Error code Message Description or corrective action Extra information
05-001 Root node is not an object Field name
05-002 Request object not found Field name
05-003 Request is not an object Field name
05-004 Duplicate field found in request object Field name
05-005 Unknown field found in request object Field name
05-006 Field operation not found Field name
05-007 Field fields not found Field name
05-008 Field operation found Field name
05-009 Field fields found Field name
05-010 Not a json value Field name
05-011 Not a json string Field name
05-012 Not a json number Field name
05-013 Not an integer Field name
05-014 Bad value (e.g. not in range or unknown) Field name
05-020 Field fields has children Field name
05-021 Field fields is not an object Field name
05-022 Field fields child is not a json value Field name
05-031 Field operation invalid length (1) Field name
05-032 Field operation has blanks in the value Field name
05-033 Field operation invalid length (2) Field name
05-034 Field operation first character is not / Field name
05-035 Field operation has less than 3 segs Field name
05-036 Field operation has a bad virt dir name Field name
05-037 Field operation has a bad web service name Field name
05-038 Field operation has a bad operation name Field name
05-061 Lookup operation - virt dir not found Field name
05-062 Lookup operation - virt dir not auth Field name
05-063 Lookup operation - web service not found Field name
05-064 Lookup operation - web service not auth Field name
05-065 Lookup operation - operation name not found Field name
05-066 Lookup operation - operation name not auth Field name
05-067 Lookup operation - call not supported Field name
05-068 Lookup operation - not select Field name
05-069 Lookup operation - sql statement too long Field name
05-070 Lookup operation - sql statement map not found Field name
05-071 Lookup operation - input map not found Field name
05-072 Lookup operation - return map not found Field name
05-073 Lookup operation - more than 1 schema name field Field name
05-074 Lookup operation - schema name field can be null Field name
05-081 Input field - field not found (no default) Field name
05-082 Input field - field already used Field name
05-083 Input field - field not used Field name
05-084 Input field - null & null value is not allowed Field name
05-085 Input field - string expected Field name
05-086 Input field - number expected Field name
05-087 Input field - number is not an integer Field name
05-088 Input field - string expected Field name
05-089 Input field - number expected Field name
05-090 Input field - invalid hex string Field name
05-091 Input field - invalid date Field name
05-092 Input field - invalid time Field name
05-093 Input field - invalid timestamp Field name
05-095 Input field - tgt hex float length not 4/8/16 Field name
05-096 Input field - tgt bin float length not 4/8/16 Field name
05-097 Input field - tgt dec float length not 8/16 Field name
05-098 Input field - character lob not supported Field name
05-099 Input field - binary lob not supported Field name
05-100 Input field - graphic lob not supported Field name
05-101 Input field - unknown internal format Field name
05-111 Input field - ccsid not supported Field name
05-112 Return field - ccsid not supported Field name
05-120 SQL verb/HTTP verb mismatch Field name
Table 7. Request processing error (06)
Error code Message Description or corrective action Extra information
06-001 No space in return area
06-002 No space in work area
06-003 Communications data return error
06-004 Unknown/not found provider
06-005 No space in field area
06-006 Unable to log user on
06-007 Unsupported return field format
06-008 An abend occurred during request processing
06-009 Request has timed out
06-010 No staging storage
06-011 No default for schema name
06-012 Sql statement overflow
06-013 Didnt find schema name parameter marker
06-014 Null or blank schema name
06-015 Overflow when converting single quotes to double quotes
06-020 Input sqlda overflow
06-030 No data for subs point
06-040 Not internal character set
06-050 Cmbu build failed (internal)
06-051 Sqlb build failed (internal)
06-052 Ret fields # mismatch
06-053 Ret field data type mismatch
06-054 Ret field has invalid data
06-060 Processing error
06-090 Binary input not supported yet
Table 8. Miscellaneous error (09)
Error code Message Description or corrective action Extra information
09-001 Request has timed out

Timed out.

The request has taken too long to process. There is a parameter that nominates the maximum time that a request can take, and this time has been exceeded. Either increase the allowed time or ensure that the request does not take too long.
09-002 Server inactive

The server has been set as inactive.

An administrator has set the server as inactive.
09-003 Server retry after error

The server is retrying after a communications error.

The request can be resent after waiting a few seconds.
09-004 Communications error The communications between z/OS Connect and the Data Service server region has failed. (Hard WOLA Error)
09-005 Server or region is terminating The Data Service server is shutting down.