Hello Everyone,

We had something happen here that led me to do some looking at our
linklists.  To make a long story short, our z/OS guys had to update the
linklist and we ended up with three sets called L0 (the original after the
last IPL), N0 (the 1st new one), and N1 (the 2nd new one).

In the course of researching the first issue I found that we had 3 CICS
regions that were using set L0.  The sequence of events were...

7/7 - IPL with set L0
7/15 - An old SDFHLINK was removed from the linklist and set N0 was
ACTIVATE'd.
7/20 - The 3 subject CICS's were cycled (as they are every week) with
START=COLD.
7/21 - Our original issue was encountered so the old SDFHLINK was put back
in the linklist and set N1 was ACTIVATE'd.

So today I used "D PROG,LNKLST,USERS,NOTCURRENT" and there I find my 3
CICS regions still using set L0.

My understanding of linklist and new set activations is that once a task
is stopped and restarted, the new iteration of the task will start using
the currently active linklist set.  If this is the case, why did the new
iterations of these regions start back up using the original set L0?  What
am I missing?

These are CICS/TS 4.2 regions run as jobs under JES3 under z/OS 1.12.

Thanks,
Howard

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to