remoteSystemID

The sysVar.remoteSystemID system variable contains the system name for the location of a remote entity: a program, a data file, an asynchronous transaction, or transient data queue. This variable does not support dynamic definition of files or programs, but does support dynamic selection from a predefined set of locations.

sysVar.remoteSystemID is initialized to blanks and must be set before doing any call, vgLib.startTransaction() function, or file I/O function that requires use of this variable.

In COBOL, the value in sysVar.remoteSystemID is folded to uppercase prior to use. Regardless of the target language, any comparison of sysVar.remoteSystemID and a character string is case sensitive and is based on the value assigned to the variable. For example, the comparison in the following code resolves to false:
  sysVar.remoteSystemID = "myWin";

  // resolves to false
  if (sysVar.remoteSystemID == "MYWIN")
    record1.resourceAssociation = "myCorp.txt";
  end
You can use sysVar.remoteSystemID in most places where a variable is allowed:

The value of sysVar.remoteSystemID provides access to the remote entity only if the linkage options part used at generation time specifies PROGRAMCONTROLLED as the value for the location property in the callLink element or specifies PROGRAMCONTROLLED as the value for the locationSpec property in the asynchLink or fileLink elements. For more information about linkage options parts, refer to the EGL Generation Guide.

You can only use sysVar.remoteSystemID to access remote files, transient data queues, or transactions in the CICS® environment. For details, see "Compatibility" below.

Characteristics

sysVar.remoteSystemID has the following characteristics:
Primitive type
CHAR
Data length
8 (padded with blanks)
Value saved across segmented converse?
Yes

Example

  sysVar.remoteSystemID = "myCICS";
  call myRemoteProgram myRecord;
  end

Compatibility

Table 1. Compatibility considerations for remoteSystemID
Platform Issue
Java™ generation and debug

sysVar.remoteSystemID provides access to a remote call to a CICS program only if the locationSpec property of the callLink element in the linkage options part is set to PROGRAMCONTROLLED.

sysVar.remoteSystemID has no effect on the vgLib.startTransaction() function or on remote VSAM files.

CICS for z/OS®

The program, transaction, or file must be defined in the appropriate CICS table.

sysVar.remoteSystemID provides access to a remote call to a CICS program only if the locationSpec property of the callLink element in the linkage options part is set to PROGRAMCONTROLLED.

sysVar.remoteSystemID provides access to a remote VSAM file or transient data queue only when the linkage options part used at generation sets the locationSpec property for the fileLink element to PROGRAMCONTROLLED.

For remote files, the system name is the CICS system identifier.

sysVar.remoteSystemID provides access to a remote CICS transaction only in the following case:
  • You use the vgLib.startTransaction() function to initiate the transaction
  • The linkage options part used at generation sets the locationSpec property for the asynchLink element to PROGRAMCONTROLLED.
For remote transactions, the system name is the CICS system identifier.
IMS™ BMP Not supported. sysVar.remoteSystemID has no effect because access to remote programs and files is not supported.
IMS/VS Not supported. sysVar.remoteSystemID has no effect because access to remote programs and files is not supported.
iSeries® COBOL Not supported
z/OS batch Not supported

Feedback