IBM SC34-7012-01 manual CICS TS for z/OS 4.1 Recovery and Restart Guide

effect in CICS region ADSWA03C was shown by the following response to an INQUIRE UOWDSNFAIL command for data set RLSADSW.VF01D.BANKACCT:

INQUIRE UOWDSNFAIL DSN(RLSADSW.VF01D.BANKACCT)
STATUS: RESULTS
Dsn(RLSADSW.VF01D.BANKACCT	) Dat Ope
Uow(ADD19B8166268E02)	Rls
Dsn(RLSADSW.VF01D.BANKACCT	) Rls Com
Uow(ADD19B9D93DE1200)	Rls

After the SMSVSAM servers terminated, all RLS-mode files were automatically closed by CICS and further RLS access prevented.

6.When we were sure that all servers were down, we deleted the IGWLOCK00 lock structure with the MVS command:

VARY SMS,SMSVSAM,FORCEDELETELOCKSTRUCTURE

followed by the response “FORCEDELETELOCKSTRUCTURESMSVSAMYES” to allow the lock structure deletion to continue.

Successful deletion of the lock structure was indicated by the following message:

IGW527I SMSVSAM FORCE DELETE LOCK STRUCTURE PROCESSING IS NOW COMPLETE

7.It was safe at this point to restart the SMSVSAM servers with the MVS command:

ROUTE *ALL,VARY SMS,SMSVSAM,ACTIVE

Initialization of the SMSVSAM servers resulted in the creation of a new lock structure, shown by the following message:

IGW453I SMSVSAM ADDRESS SPACE HAS SUCCESSFULLY CONNECTED TO DFSMS LOCK STRUCTURE IGWLOCK00 STRUCTURE VERSION: ADD1A77F0420E001 SIZE: 35072K bytes MAXIMUM USERS: 32 REQUESTED:32

LOCK TABLE ENTRIES: 2097152 REQUESTED: 2097152

RECORD TABLE ENTRIES: 129892 USED: 0

The SMSVSAM server reported that there were no longer any retained locks but that instead there were data sets in the “lost locks” condition:

IGW414I SMSVSAM SERVER ADDRESS SPACE IS NOW ACTIVE. IGW321I No retained locks

IGW321I 45 spheres in Lost Locks

CICS was informed during dynamic RLS restart about the data sets for which it must perform lost locks recovery. In our example, CICS issued messages such as the following to tell us that lost locks recovery was needed on one or more data sets:

DFHFC0555 ADSWA04A One or more data sets are in lost locks status. CICS will perform lost locks recovery.

8.(If we had quiesced data sets before terminating the servers (see the comments between steps 3 and 4) this is the point at which we would unquiesce those data sets before continuing with the recovery.

If there were many data sets in lost locks it would take some time for lost locks recovery to complete. Error responses are returned on open requests issued by any CICS region that was not sharing the data set at the time SMSVSAM servers were terminated, and on RLS access requests issued by any new UOWs in CICS regions that were sharing the data set. Also, it may be necessary to open explicitly files that suffer open failures during lost locks recovery.

Each data set in a lost locks state is protected from new updates until all CICS regions have completed lost locks recovery for the data set. This means that all shunted UOWs must be resolved before the data set is available for new

194CICS TS for z/OS 4.1: Recovery and Restart Guide