SYSID

The SYSID option appears on the ALLOCATE command and most file services, timer services, program execution, temporary storage, and transient data commands. It is a four-character name. Each CICS® region has a local SYSID. On CICS, it is configured in the LocalSysId attribute of the Region Definition (RD) entry. In addition, a CICS region can have entries in the Communications Definitions (CD), each of which defines a connection to a remote system. The name of a CD entry is referred to as a remote SYSID or a connection name. These remote SYSIDs are known only to the local region and do not have to match the name of the remote system at the other end of the connection.

The SYSID option on the ALLOCATE command allows an application to specify a remote SYSID only. This is because ALLOCATE is starting a Distributed Transaction Processing (DTP) conversation with a program that is running on a remote system.

The SYSID option on other commands can be a local or a remote SYSID. It is used to specify where the resource resides.
  • If the local SYSID is specified, the resource resides on the local CICS region. The resource must be defined in the local resource definition. In addition, the local definition for the resource must not have the RemoteSysId attribute set to a remote SYSID, otherwise CICS generates an AEY9 abnormal termination.
  • If a remote SYSID is specified, CICS uses an intersystem request to send the command on the connection that is defined for the SYSID. The system that receives the request must be a CICS region.

If the SYSID option is not specified on a file services, timer services, program execution, temporary storage, or transient data command, it defaults to the value that is in the RemoteSysId attribute of the resource’s local definition. If RemoteSysId="", or it is set to the local SYSID, the command runs locally. If RemoteSysId is set to a remote SYSID, CICS uses an intersystem request to send the command on the connection that is defined for the SYSID. Again, the receiving system must be CICS.

Any application that is using the SYSID option on file services, timer services, program execution, temporary storage, or transient data commands to request a remote SYSID, must have RSLCheck=none set in Transaction Definitions (TD) entry of the invoking transaction. Otherwise, CICS raises the NOTAUTH condition. This is because the SYSID option causes local security checking to be bypassed, so CICS allows its use only by transactions that do not require RSL checking.

For more information about DTP conversations and the use of intersystem requests to access resources on other CICS regions, see Conversations and Conversation states.

For more information about DTP conversations and the use of intersystem requests to access resources on other CICS regions, see TXSeries® for Multiplatforms Intercommunication Guide.