Sterling Connect:Enterprise for z/OS considerations

You need to be aware of considerations for Sterling Connect:Enterprise® for z/OS® servers when you are integrating them with IBM® Sterling Control Center Monitor.

Observe the following special considerations when managing Sterling Connect:Enterprise for z/OS servers:

• Only PKCS #12 base64 encoded certificates can be imported into Sterling Connect:Enterprise for z/OS V5.0. Binary encoded PKCS#12 certificates cannot be imported.
• When processes end for reasons such as session outages, and remain in the Sterling Connect:Direct® TCQ to attempt to run again, rather than generate a Process End event, IBM Sterling Control Center Monitor generates a Process Interrupted event. See Functionality by server type in Release Notes for a list of servers that support Process Interrupted events. If you have rules in a previous IBM Sterling Control Center Monitor release that watch for Process End events, these rules will no longer be triggered under such circumstances. Therefore, to achieve the same behavior, add rules that watch for events with an event type of Process Interrupted.
• Sterling Connect:Enterprise for z/OS nodes require the fix for SR1344775 to address the lack of a Process interrupted record being written at appropriate times by Sterling Connect:Enterprise for z/OS nodes. The lack of Process interrupted records can cause issues with the High Watermark Report, SLC processing, and other areas of IBM Sterling Control Center Monitor functionality.
• You must configure Sterling Connect:Enterprise for z/OS to send traps to the active event processor. You can configure Sterling Connect:Enterprise for z/OS to send traps to all the event processors you defined with the same port number. If the active event processor fails, you must reconfigure Sterling Connect:Enterprise for z/OS to send traps to the new active event processor.