Common Initialization Parameters

Common initialization parameters are those that can be declared in all Substation ES SIP members.

Common Initialization Parameters
Parameter Description
INTF-TYPE = {number} The INTF-TYPE parameter identifies the type of interface that is being defined within this member. This must be the first keyword defined for each SIP interface. Typically, you must have one member for the transaction processing interface (CICS/IMS) and another that specifies the details for the Substation ES ESB (XFR), as described in ESB Interface Parameters.
The valid values are as follows:
  • 2=MAIN: this is the SIP member of the main task for Substation ES.
  • 7=ADMIN: this is the Substation ES administration and operational interface.
  • 8=CICS: this selection is for configuring the CICS functions.
  • 12=IMS: this selection is for configuring the IMS functions.
  • 16=XFR: this selection is for the Substation ES ESB.
  • 28=RED: this selection is for configuring the RED functions.
  • 32=TCP: this selection is for configuring Substation ES TCP.
  • 40=Test: this selection is reserved for the Substation ES test interfaces.
INTF-ID = {name} The INTF-ID parameter specifies a one- to eight-character identifier that is assigned to the Substation ES task or interface.
Warning: Be very careful when changing this value. Substation ES also uses the values in the configuration items (recipes and triggers) to transfer data between Substation ES interfaces, for example, ESB Interface and CICS Interface.

After changing this value, be sure to also change its associated references in the configuration items.

DESCR = {description} The DESCR parameter specifies a one- to 40-character description of the interface or task. This description is important because it identifies the actions performed by a task in the log and trace files.
START-YN = {Yes, No} The START-YN parameter specifies whether to load the interface referenced by this member at Substation ES startup. The valid values are as follows:
  • Yes: the member should be automatically loaded at system startup.
  • No: the member should not be automatically loaded at system startup.