ZIS message codes
ZIS message codes
The following codes can appear in either the ZIS SYSPRINT or JESMSGLG log, or both. Use the following message code references and the corresponding reasons and actions to help troubleshoot issues.
ZIS cross-memory server messages
ZWES0001I
ZSS Cross-Memory Server starting, version is major.minor.patch+datestamp
Reason:
The cross-memory server with the specified version is starting.
Action:
No action required.
ZWES0002I
Input parameters at address:
hex_dump
Reason:
The message shows a hex dump of the parameters passed in the started task JCL.
Action:
No action required.
ZWES0003I
Server name not provided, default value 'name' will be used
Reason:
The user did not provide a server name.
Action:
The cross-memory server uses the indicated default value name. If needed,
specify a server name either via the NAME
parameter in the JCL or via
the ZWES.NAME
parameter in the PARMLIB member; the JCL parameter takes
precedence.
ZWES0004I
Server name is 'name'
Reason:
The message indicates this server's name.
Action:
No action required.
ZWES0005E
ZSS Cross-Memory server not created, RSN = reason_code
Reason:
The cross-memory server failed to create the cross-memory server's data structure.
Action:
The cross-memory server terminates. Contact support.
ZWES0006E
ZSS Cross-Memory server resource not allocated (resource_name)
Reason:
The cross-memory server failed to allocate storage for a resource.
Action:
The cross-memory server terminates. Contact support.
ZWES0007E
ZSS Cross-Memory server PARMLIB member suffix is incorrect - 'suffix'
Reason:
The cross-memory's PARMLIB member suffix is invalid.
Action:
The cross-memory server terminates. Ensure that the suffix consists of two characters that are allowed in a member name.
ZWES0008E
ZSS Cross-Memory server configuration not read, member = 'member_name', RC = return_code_1 (return_code_2, reason_code_2)
Reason:
The cross-memory server failed to read the specified PARMLIB member.
Action:
The cross-memory server terminates. Review the error codes and contact support if you cannot resolve the issue.
Possible return codes and the corresponding actions:
return_code_1 | return_code_2 | reason_code_2 | Action |
---|---|---|---|
RC_ZISPARM_MEMBER_NOT_FOUND(2) | N/A | N/A | Ensure the member exists |
RC_ZISPARM_DDNAME_TOO_LONG(8) | N/A | N/A | Contact support |
RC_ZISPARM_MEMBER_NAME_TOO_LONG(9) | N/A | N/A | Contact support |
RC_ZISPARM_PARMLIB_ALLOC_FAILED(10) | Return code from IEFPRMLB REQUEST=ALLOCATE | Reason code from IEFPRMLB REQUEST=ALLOCATE | Review the IEFPMLB return and reason codes |
RC_ZISPARM_READ_BUFFER_ALLOC_FAILED(11) | N/A | N/A | Contact support |
RC_ZISPARM_PARMLIB_READ_FAILED(12) | Return code from IEFPRMLB REQUEST=READMEMBER | Reason code from IEFPRMLB REQUEST=READMEMBER | Review the IEFPMLB return and reason codes |
RC_ZISPARM_PARMLIB_FREE_FAILED(13) | Return code from IEFPRMLB REQUEST=FREE | Reason code from IEFPRMLB REQUEST=FREE | Review the IEFPMLB return and reason codes |
RC_ZISPARM_SLH_ALLOC_FAILED(16) | Start line number | End line number | Contact support |
RC_ZISPARM_CONTINUATION_TOO_LONG(19) | Start line number | End line number | Review the lines and fix continuation |