The procedures for the recovery of InFlight and InDoubt work have been described in some detail, but how is new work handled on a recovered server? Once the InDoubt and InFlight work has been completed, the WebSphere Application Server for z/OS server shuts down. A new application server configured for that system may now be started up to accept new work.
Special considerations must be taken to begin new work on a WebSphere Application Server for z/OS using IMS Connect after recovering to an alternate system. Once the recovery has been completed, IMS Connect starts, but is not usable without some manual intervention. On the current IMS Connect WTOR perform the following commands nn,viewhws followed by nn,opends XXX where XXX is the IMS subsystem name displayed in the result of the nn,viewhws query. The IMS datastore needs to reflect 'active' status, which can be seen in the example below:
*17 HWSC0000I *IMS CONNECT READY* IMSCONN R 17,VIEWHWS IEE600I REPLY TO 17 IS;VIEWHWS HWSC0001I HWS ID=IMSCONN Racf=N HWSC0001I Maxsoc=100 Timeout=12000 HWSC0001I Datastore=IMS Status=ACTIVE HWSC0001I Group=IMSGROUP Member=IMSCONN HWSC0001I Target Member=IMSA HWSC0001I Port=9999 Status=ACTIVE HWSC0001I No active Clients HWSC0001I Port=LOCAL Status=ACTIVE HWSC0001I No active Clients
Once this has been completed IMS Connect is ready for new work to be completed on the server.