Seems like this health check should recognize when no jobs are using an
obsolete LNKLST set and stop complaining without having to update the
check PARM with NEW(xxxx).
I put a load library on the IPL-time LNKLST with a secondary space
amount, forced it to add an extent, ran this health check and, as
expected, received RC=12 with the following report:
|CSVH0969I LNKLST set IPLTIME
|
|The error status is in column one:
|C = Confirmed error * = New error - = Unknown
|
| ORIG CURR VOLUME DSNAME
|* 5 6 MVSSY1 SYS2.E450.SEJELPA
| TOTAL EXTENTS ORIG: 205 CURR: 206
I then activated a new LNKLST set called OCT09A. Re-ran the check and
got exactly the same return code and report with the following two
additional lines at the bottom:
CSVH0974I LNKLST set OCT09A is using 206 extents, which has not changed
since it was activated.
I then issued SETPROG LNKLST,UPDATE,JOB=* on all systems and re-ran the
check again. Same report; same RC=12!
But, when I issue D PROG,LNKLST,USERS,NAME=IPLTIME, I get:
CSV481I THERE ARE NO USERS OF LNKLST SET IPLTIME
Shouldn't the health check understand this condition?
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
