Restarting a connection to a remote IMS Connect instance for IMS-to-IMS TCP/IP communications

You can restart a stopped IMS-to-IMS TCP/IP connection in a local IMS Connect instance by issuing an online IMS Connect command.

Depending on whether the connection is used for Multiple Systems Coupling (MSC) or Open Transaction Manager (OTMA), the implications of restarting an IMS-to-IMS TCP/IP connection from IMS Connect are different.

If you are restarting a connection that is used for MSC, MSC communication does not resume until the MSC physical link is also started in the local IMS Connect instance.

If you are restarting a connection that is used for OTMA, the following actions occur when the connection is started:
  • If the IMS-to-IMS TCP/IP connection is defined locally with AUTOCONN=Y, the local IMS Connect establishes socket connections with the remote IMS Connect instance. The number of socket connections opened is determined by the RESVSOC parameter in the RMTIMSCON configuration statement.
  • The local IMS Connect notifies the local OTMA that the connection has been restarted and OTMA resumes sending messages on the connection.

To restart an IMS-to-IMS TCP/IP connection from the local IMS Connect instance:

Procedure

  1. Issue any one of the following IMS Connect commands:
    • In the IMS type-2 format, UPDATE IMSCON TYPE(RMTIMSCON) NAME(rmtimscon_name) START(COMM)
    • In the WTOR format, STARTRMT
    • In the z/OS® MODIFY format, UPDATE RMTIMSCON START(COMM)
  2. If the connection is used for MSC, start the MSC physical link in the local IMS Connect by issuing any one of the following IMS Connect commands:
    • In the IMS type-2 format, UPDATE IMSCON TYPE(MSC) NAME(lclPlkid) START(COMM)
    • In the WTOR format, STARTMSC lclplk_id
    • In the z/OS MODIFY format, UPDATE MSC NAME(lclPlkid) START(COMM)
IMS Connect issues message HWS3500I after the connection is restarted.