These days MVS uses an ICF catalog, which has two components, a Basic Catalog
Structure (BCS) and a VSAM Volume Data Set (VVDS). On the volume containing the
catalog, you should have an entry in the VVDS. In the BCS for the master
catalog, you should have an entry for the catalog and an entry for each alias.
In z/OS Version 2 Release 4 DFSMS Access Method Services Commands IBM,
SC23-6846-40,
https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R4sc236846/$file/idai200_v2r4.pdf,
read up on
DEFINE ALIAS
DEFINE USERCATALOG
DIAGNOSE
IMPORT CONNECT
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
________________________________________
From: IBM Mainframe Discussion List [[email protected]] on behalf of
Charles Mills [[email protected]]
Sent: Tuesday, January 26, 2021 1:49 PM
To: [email protected]
Subject: Help with non-existent catalog
I've got a catalog problem. I have no reason to believe it is the most
obscure problem in the world; it's just that I am a catalog ignoramus.
I *think* the problem is that the catalog is cataloged but the underlying
dataset does not exist. Does that make sense? If I enter an ISPF 3.4 D
against it ISPF tells me "Dataset not found." That's a problem, right?
If I enter a U against it ISPF tells me Catalog/uncatalog request via SVC 26
failed, return code = 60, reason code = 4, module id = FM.
Thanks for your help. I believe I would be fine if I could just delete it
and start over. I don't know quite how this situation came to be.
Charles
----------------------------------------------------------------------
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
