The error is clear. When you first IPL'd the catalog for the four datasets you name pointed to a specific volume. You recataloged them using the exact same name to volume ****** which does not match the volume the ACTIVE LNKLST has for them. I have found that the LNKLST does not like identically named datasets on different volumes. (this was around z/OS 1.7 or 1.9)
Last time I was here, I found I couldn't figure the correct incantation sequence of SETPROG and I IPL'd. I try very hard not to get here again. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Mainframe Mainframe > Sent: Sunday, February 21, 2016 9:13 AM > To: [email protected] > Subject: Re: DASD device not going offline > > Answers for the query raised. > > 1) Is this a production or TEST or DEV environment where this problem is > occurring? > Ans : This is production system. > a) How long can this system be unusable? If not much longer, open an SR > to IBM for assistance. > Ans : If this > 2) When you recataloged the datasets for Indirect, did you do it on the > system where this is now failing? > Ans : Yes, I did it from the system its failing. > 3) Look at output from the catalog function (control cards and results - all > messages) Ans : I am unable to check output because SDSF is not accessible > even from Ready prompt. > 4) Look at APF Definition statements (The beginning of the APF list > definition > in PARMLIB and the entries for these datasets) ans : There is no entry for > these four dataset in APF. > 5) Look at Link List Definition statements (the beginning of the link list > definition in PARMLIB and the entries for these datasets) Ans : > > LNKLST DEFINE NAME(LNKLST00) /* DEFINE */ > LNKLST ADD NAME(LNKLST00) DSNAME(SYS1.SERBLINK) /* RMF */ > LNKLST ADD NAME(LNKLST00) DSNAME(SYS1.SCSFMOD0) /* ICSF */ > LNKLST ADD NAME(LNKLST00) DSNAME(SYS1.SISFLOAD) /* SDSF */ > LNKLST ADD NAME(LNKLST00) DSNAME(SYS1.SASMMOD1) /* HL/ASM > */ > LNKLST ACTIVATE NAME(LNKLST00) /* ACTIVATE */ > > > 6) Look at attributes of the datasets (are they PDS or PDSE datasets?) Ans : > All these four dataset are PDS. > 7) Look at D PROG,LNKLIST > For these four dataset, still showing old volume. > SYS1.SCSFMOD0 > SYS1.SISFLOAD > SYS1.SASMMOD1 > SYS1.SERBLINK > 8) Look at D PROG,APF > Nothing wrong I see in this. > > 9) Why did you need to recatalog the datasets? > a) What was the requirement? > Ans : In our system we have two res volume (primary and alt) and we use > indirect catalogging.But in recent changes, > these four dataset was directly pointing to primary RES volume, which > was > wrong. So, I run indirect catalog > Job to change them to point to ****** volume. > b) What action occurred to cause them to no longer be indirectly > cataloged? > Ans : Couldnt understand this question. > 10) When you recataloged the datasets indirectly, did you do it on the LPAR > having issues? > a) Or did you do it from a different LPAR? > Ans : I did it from failing LPAR. > b) Is the Master Catalog Shared or Unique? > Ans : We are in Sysplex env and master catalog in not shared. > c) What was the job used to recatalog the datasets? Review all output. > Ans : Used Below Job. > //INDIRECT JOB 'MAINFRAM',CLASS=A,MSGCLASS=A,NOTIFY=&SYSUID > //STEP010 EXEC PGM=IDCAMS > //SYSPRINT DD SYSOUT=* > //SYSIN DD * > DEL (SYS1.SERBLINK) - > NSCR CAT(ZOS.MASTER.CATALOG) > /* */ > DEF NVSAM(NAME(SYS1.SERBLINK) - > VOL(******) DEVT(3390)) - > CAT(ZOS.MASTER.CATALOG) > /* * * * * * * * * * * * * * * * * * * * * * * * * * */ > > On Sun, Feb 21, 2016 at 6:44 PM, Lizette Koehler <[email protected]> > wrote: > > > The list cannot replace a vendor support function. > > > > > > This message: CSV540E LNKLST SET LNKLST00 is in error. > > DATASET SET SYS1.SERBLINK > > HAS VOLUME ID DOESNT NOT MATCH WITH CATALOG. > > Is telling you exactly what is wrong. The linklist entry and the > > catalog entry do not match on that lpar. You need to validate how you > > recataloged the dataset. > > > > > > I also recommend using SETPROG LNKLST,TEST to validate before doing > > the SETPROG command. Check the MVS Commands manual for complete > > description of the command. > > > > Here is the information you need to look at (this is a checklist for > > diagnosing this issue): > > > > 1) Is this a production or TEST or DEV environment where this problem > > is occurring? > > a) How long can this system be unusable? If not much longer, open > > an SR to IBM for assistance. > > 2) When you recataloged the datasets for Indirect, did you do it on > > the system where this is now failing? > > 3) Look at output from the catalog function (control cards and > > results - all messages) > > 4) Look at APF Definition statements (The beginning of the APF list > > definition in PARMLIB and the entries for these datasets) > > 5) Look at Link List Definition statements (the beginning of the link > > list definition in PARMLIB and the entries for these datasets) > > 6) Look at attributes of the datasets (are they PDS or PDSE > > datasets?) > > 7) Look at D PROG,LNKLIST > > 8) Look at D PROG,APF > > 9) Why did you need to recatalog the datasets? > > a) What was the requirement? > > b) What action occurred to cause them to no longer be indirectly > > cataloged? > > 10) When you recataloged the datasets indirectly, did you do it on the > > LPAR having issues? > > a) Or did you do it from a different LPAR? > > b) Is the Master Catalog Shared or Unique? > > c) What was the job used to recatalog the datasets? Review all output. > > > > > > > > You have two options > > 1) Fix it dynamically (I think you should be able to fix this > > dynamically) > > 2) IPL > > Even if you IPL you may not come up as the catalog entries and the > > definitions do not match. > > > > > > Since this has been going on for a couple of days, you might need to IPL. > > Even if you IPL you may not come up as the catalog entries and the > > definitions do not match. > > > > > > The List is a guide or mentor. The list is not a help desk. > > > > You need to Look at following for these files: > > > > LISTC ENT('xxxx') ALL for each dataset on the LPAR where it is failing > > All of the Link list entries and their definitions The attributes of > > the datasets All of the APF List entries and their definitions > > > > Even if you IPL you may not come up as the catalog entries and the > > definitions do not match. > > > > After you review all of this information, it might be quicker to open > > an SR with IBM for assistance. > > > > After you copy the LINKLIST to new name, you may need to delete the > > current entry and add new entry. However, you should do this with > > IBM's assistance. I do not recommend you do the delete/add in the > > LNKLST without some assistance from IBM. You will need IBM to help > > you verify your LINKLST and APF list definitions so that everything is > correct. > > > > > > Lizette > > > > > > > -----Original Message----- > > > From: IBM Mainframe Discussion List > > > [mailto:[email protected]] On Behalf Of Mainframe > Mainframe > > > Sent: Saturday, February 20, 2016 10:52 PM > > > To: [email protected] > > > Subject: Re: DASD device not going offline > > > > > > When I am trying to run SETPROG LNKLST,ALLOCATE command , I am > > > getting below error on console, > > > > > > CSV540E LNKLST SET LNKLST00 is in error. > > > DATASET SET SYS1.SERBLINK > > > HAS VOLUME ID DOESNT NOT MATCH WITH CATALOG. > > > > > > When I already run indirect catalog JCL for these dataset, why > > > linklist > > is not > > > able to take this new update. How we can do it dynamically or only > > > IPL > > is the > > > only option. > > > > > > > > > On Sun, Feb 21, 2016 at 10:07 AM, Mainframe Mainframe < > > > [email protected]> wrote: > > > > > > > Hello Lizette, > > > > After making indirect catalog, I checked > > > > through listcat and it shows ****** which is correct now. But D > > > > PROG,lnklst still show these dataset on old RES volume which is > > > > not correct. How do I change this to point to current IPL'd RES volume. > > > > > > > > > > > > > > > > On Sun, Feb 21, 2016 at 2:52 AM, Lizette Koehler > > > > <[email protected]> > > > > wrote: > > > > > > > >> You do not need ISPF to run SDSF. You can issue SDSF from the > > > >> READY Prompt in native TSO. It does not have all of the niceties > > > >> it has under ISPF, but is very functional. > > > >> > > > >> Check your catalog entries. Make sure the LISTC ENT('xxxx') ALL > > > >> shows the indirect catalog entry > > > >> > > > >> Lizette > > > >> > > > >> > > > >> > -----Original Message----- > > > >> > From: IBM Mainframe Discussion List > > > >> > [mailto:[email protected]] > > > >> On > > > >> > Behalf Of Mainframe Mainframe > > > >> > Sent: Saturday, February 20, 2016 10:11 AM > > > >> > To: [email protected] > > > >> > Subject: Re: DASD device not going offline > > > >> > > > > >> > Hello Lizette, > > > >> > Thanks for suggestion. As expected, > > > >> > command D PROG,LINKLIST showing my dataset on wrong volume. > > > >> > Basically we have two > > > >> RES > > > >> > volume ZS21P1( primary ) and ZS21T1 ( Ale RES volume) , and > > > >> > system is indirectlry catalogged. My system is curently IPL'd > > > >> > from Alt Res > > > >> volume, But > > > >> > today I noticed that > > > >> > > > > >> > SYS1.SCSFMOD0 > > > >> > SYS1.SISFLOAD > > > >> > SYS1.SASMMOD1 > > > >> > SYS1.SERBLINK > > > >> > > > > >> > dataset were pointing to Primary res volume,So I updated and > > > >> > made it > > > >> indirect > > > >> > cataloged. So, that it will point to ZS21T1 now as currently > > > >> > system is > > > >> IPL'd > > > >> > from ZS21T1. > > > >> > > > > >> > Now when I issued D PROG,LINKLST , these dataset still showing > > > >> > me in > > > >> ZS21P1 > > > >> > which is wrong. > > > >> > > > > >> > In my PROG00, we dont put volume serial number , like below. > > > >> > > > > >> > LNKLST DEFINE NAME(LNKLST00) /* DEFINE > > */ > > > >> > LNKLST ADD NAME(LNKLST00) DSNAME(SYS1.SISFMOD1) /* > SDSF > > */ > > > >> > > > > >> > We don't use CSVLLAxx member in our system . > > > >> > > > > >> > Now I tried to run below command from HMC console, as I am not > > > >> > able to > > > >> access > > > >> > SDSF because of this issue, > > > >> > > > > >> > SETPROG LNKLST,DEFINE,NAME=LNKLST01,COPYFROM=LNKLST00 > > > >> > SETPROG LNKLST,ACTIVATE,NAME=LNKLST01 SETPROG > > > >> > LNKLST,UPDATE,JOB=* > > > >> > > > > >> > But I am not able to run these command anY get syntax issue etc. > > > >> > > > > >> > Please suggest > > > >> > > > > >> > > > >> ----------------------------------------------------------------- > > > >> ---- > > > >> - For IBM-MAIN subscribe / signoff / archive access instructions, > > > >> send email to [email protected] with the message: INFO > > > >> IBM-MAIN > > > >> > > > > > > > > > > > > > > -------------------------------------------------------------------- > > > -- For IBM-MAIN subscribe / signoff / archive access instructions, > > > send > > email to > > > [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
