If the VVDS was created automatically by SMS when the first dataset was created on the volume, then it was catalogued in the same catalog as that dataset. Usually, the dataset is a user dataset and the VVDS ends up being catalogued in the corresponding user catalog. However, LISTCAT (which produced the messages you quoted) looks for catalog entries in "normal search order" (unless you direct otherwise) and for SYS1 this means master catalog only.
SYS1 VSAM datasets can be catalogued in multiple catalogs so you could add the VVDS to the master catalog to eliminate the error messages. On the other had, the system is quite capable of finding any VVDS it needs without resorting to "normal search order" so there is no need. :>: -----Original Message----- :>: From: IBM Mainframe Discussion List [mailto:[email protected]] On :>: Behalf Of Buckton, T. (Theo) :>: Sent: Friday, February 24, 2012 1:33 AM :>: To: [email protected] :>: Subject: VVDS with no catalog pointers :>: :>: Hi There, :>: :>: Please explain why not all VVDSs catalog pointers. When doing a listcat, :>: the return is as follows: :>: :>: IDC3012I ENTRY SYS1.VVDS.VAPBPC7 NOT FOUND+ :>: IDC1566I ** SYS1.VVDS.VAPBPC7 NOT LISTED :>: IDC0014I LASTCC=4 :>: IDC3009I ** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLEG-42 :>: *** :>: Apparently this is normal. :>: :>: I want to see the logic here. :>: :>: BTW, these are sms-managed volumes. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
