Substation ES Operations

You can implement different operational functions on Substation ES Interface.

The operations functions include the following ones:

  • Auto Recovery of Messages When EMS is the ESB
    Substation ES attempts to recover any Guaranteed messages waiting in a queue on the TIBCO EMS server, as well as messages that are used in Guaranteed Services where delivery failed to a z/OS transaction. These are active Recipes in the configuration file, with an SMSL of GA or GS.
  • System Property Fields
    Substation ES system fields, or properties as they are known in JMS (EMS), are mostly optional, but might either be present in the message or as a property in message.
  • Substation ES HeartBeat Events
    HeartBeat is a message or an event that is sent to a destination, informing the recipients that Substation ES is running. Additionally, the Substation ES instance issues the specified internal operational commands. The contents of the commands are then sent to a destination defined in a trigger service.
  • Writing Substation ES Messages to SYSLOG
    Substation ES provides the option to write messages to SYSLOG so that you can trap and automate the setup on selected Substation ES messages.
  • Sites with Multiple Stacks
    If the system uses multiple TCP/IP stacks, insert the following JCL statement before the Substation ES application execution steps:
  • Detecting Network Connection Failures with EMS ESB
    If network issues disrupt the connection between EMS and Substation ES, unexpected errors might result if Substation ES does not detect the connection failure.
  • Sending Variable Length Messages
    Some business applications always send the same size output; other applications send out different length messages based on business criteria.
  • Exceptional Cases
    When you use Substation ES, you might encounter and should be aware of some exceptional cases. The exceptional cases are described as follows.