Summary -

In this topic, we described about the 53 SYSIDERR with detailed example.

If this error condition occurred, the task gets abnormally terminated.

CommandRESP2, Description & Solution
CANCEL 130 - The SYSID name specified is neither the local region nor a remote system or the link to the remote system is closed.

Solution: - The specified SYSID name is not related to any system. Correct it.
If the link to the remote system is closed, that might be due to the remote system is not up and running. Contact remote system support team.
DELETE 130 - The SYSID name specified is neither the local region nor a remote system or the link to the remote system is closed.

Solution: - The specified SYSID name is not related to any system. Correct it.
If the link to the remote system is closed, that might be due to the remote system is not up and running. Contact remote system support team.
DELETEQ TD Occurs when the SYSID option specifies a name that is neither the local system nor a remote system.

Solution: - The specified SYSID name is not related to any system. Correct it to resolve the issue.
DELETEQ TS 4 - Occurs in any of the following situations:
  • The specified SYSID name is not the local system or a remote system.

    Solution: - The specified SYSID name is not related to any system. Correct it if required.
  • The link to the remote system is closed.

    Solution: - This might be due to the remote system is not up and running. Contact remote system support team.
  • The CICS region specified fails to connect to the TS server supports the referenced temporary storage queue.

    Solution: - This issue due to the connectivity issue. Restart the CICS region might solve the issue. Otherwise, contact the system administrator to resolve the issue.
ENDBR 130 - The SYSID name specified is neither the local region nor a remote system or the link to the remote system is closed.

Solution: - The specified SYSID name is not related to any system. Correct it.
If the link to the remote system is closed, that might be due to the remote system is not up and running. Contact remote system support team.
LINK 18 - The SYSID specified cannot be found in the intersystem table.

Solution: - Check the SYSID and modify the program to correct it.
20 - The remote system specified in SYSID is not supports distributed program link requests.

Solution: - Change the remote system id if specified wrongly or contact system administrator if the remote system id is specified correctly.
21 - The remote system specified in LINK with CHANNEL option does not support CHANNEL option.

Solution: - Contact System administrator to rectify the error.
28 - The remote system specified by SYSID is not in service and transaction has not been defined on the remote system.

Solution: - Change the remote system id if specified wrongly or contact system administrator if the remote system id is specified correctly.
29 - The remote system specified by SYSID is in service, but there are no sessions available and the dynamic routing program has chosen not to queue the link request.

Solution: - Contact System administrator to rectify the error.
31 - The request to allocate a session to the remote system has been rejected.

Solution: - Contact System administrator to rectify the error.
32 - The queue of allocate requests for sessions to the remote system has failed because the session allocation queue is full or has been purged.

Solution: - Contact System administrator to rectify the error or request them after some time.
READ 130 - The SYSID name specified is neither the local region nor a remote system or the link to the remote system is closed.

Solution: - The specified SYSID name is not related to any system. Correct it.
If the link to the remote system is closed, that might be due to the remote system is not up and running. Contact remote system support team.
READNEXT 130 - The SYSID name specified is neither the local region nor a remote system or the link to the remote system is closed.

Solution: - The specified SYSID name is not related to any system. Correct it.
If the link to the remote system is closed, that might be due to the remote system is not up and running. Contact remote system support team.
READPREV 130 - The SYSID name specified is neither the local region nor a remote system or the link to the remote system is closed.

Solution: - The specified SYSID name is not related to any system. Correct it.
If the link to the remote system is closed, that might be due to the remote system is not up and running. Contact remote system support team.
READQ TD Occurs when the SYSID option specifies a name that is neither the local system nor a remote system.

Solution: - The specified SYSID name is not related to any system. Correct it.
READQ TS 4 - Occurs in any of the following situations:
  • The specified SYSID name is not the local system or a remote system.

    Solution: - The specified SYSID name is not related to any system. Correct it if required.
  • The link to the remote system is closed.

    Solution: - This might be due to the remote system is not up and running. Contact remote system support team.
  • The CICS region specified fails to connect to the TS server supports the referenced temporary storage queue.

    Solution: - This issue due to the connectivity issue. Restart the CICS region might solve the issue. Otherwise, contact the system administrator to resolve the issue.
RESETBR 130 - The SYSID name specified is neither the local region nor a remote system or the link to the remote system is closed.

Solution: - The specified SYSID name is not related to any system. Correct it.
If the link to the remote system is closed, that might be due to the remote system is not up and running. Contact remote system support team.
REWRITE 130 - The SYSID name specified is neither the local region nor a remote system or the link to the remote system is closed.

Solution: - The specified SYSID name is not related to any system. Correct it.
If the link to the remote system is closed, that might be due to the remote system is not up and running. Contact remote system support team.
STARTBR 130 - The SYSID name specified is neither the local region nor a remote system or the link to the remote system is closed.

Solution: - The specified SYSID name is not related to any system. Correct it.
If the link to the remote system is closed, that might be due to the remote system is not up and running. Contact remote system support team.
UNLOCK 130 - The SYSID name specified is neither the local region nor a remote system or the link to the remote system is closed.

Solution: - The specified SYSID name is not related to any system. Correct it.
If the link to the remote system is closed, that might be due to the remote system is not up and running. Contact remote system support team.
WRITE 130 - The SYSID name specified is neither the local region nor a remote system or the link to the remote system is closed.

Solution: - The specified SYSID name is not related to any system. Correct it.
If the link to the remote system is closed, that might be due to the remote system is not up and running. Contact remote system support team.
WRITEQ TD Occurs when the SYSID option specifies a name that is neither the local system nor a remote system.

Solution: - The specified SYSID name is not related to any system. Correct it.
Occurs when the link to the remote system is closed.

Solution: - This might be due to the remote system is not up and running. Contact remote system support team.
WRITEQ TS 4 - Occurs in any of the following situations:
  • The specified SYSID name is not the local system or a remote system.

    Solution: - The specified SYSID name is not related to any system. Correct it.
  • The link to the remote system is closed.

    Solution: - This might be due to the remote system is not up and running. Contact remote system support team.
  • The CICS region specified fails to connect to the TS server supports the referenced temporary storage queue.

    Solution: - This issue due to the connectivity issue. Restart the CICS region might solve the issue. Otherwise, contact the system administrator to resolve the issue.