Question & Answer
Question
IDC3009I RC140 RSN60 When attempting to define a new alias, and running the batch job:
DEFINE ALIAS -
(NAME(MYALIAS) -
RELATE(SYS1.CATALOG.TSO)) -
CAT(SYS1.CATALOG)
Answer
- Description:
IDC3009I RC140 RSN60
When attempting to define a new alias, and running the batch job:
DEFINE ALIAS -
(NAME(MYALIAS) -
RELATE(SYS1.CATALOG.TSO)) -
CAT(SYS1.CATALOG.MASTER)
The following messages are received:
IDC3014I CATALOG ERROR
IDC3009I ** VSAM CATALOG RETURN CODE IS 140 - REASON CODE IS IGG0CLEF-60
IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12
ERROR MSG:
IDC3009I VSAM CATALOG RETURN CODE IS return code value - REASON CODE IS IGGOCLaa - reason code value
Explanation: Catalog management returned this return code and reason code as a result of a catalog error or exceptional condition.
RETURN CODE 140
Explanation: Inconsistent or conflicting arguments were provided.
60 Explanation: The logical record size for an ICF catalog has been exceeded. The DEFINE ALIAS has caused the updated catalog record to exceed the catalog's logical record size.
Programmer Response: Redefine the catalog record size to increase the logical record size to a value up to the 32,400 byte maximum. Run the DEFINE of the alias again.
Excerpt from APAR OZ94146:
With ICF catalogs a single cell cannot exceed the size of a single catalog record. The association cell contains the name of every alias defined over an object. Because of this, there is a limit to the number of alias entries that can be associated with one catalog. This limit varies with the average alias name length. For example, if the average alias name length is 8 bytes the limit is about 3660. If it is 25 bytes, it is about 1300. The documentation does not indicate there is a limit to the number of alias entries that may be associated with one catalog.
The number of ALIASES has exceeded the record capacity of the master catalog (maximum record size is 32,400). The record that has the associations for the ALIASES is the UCAT connector record for the catalog. The UCAT connector record is in the Master catalog. This record contains the USERCATALOG name and all the ALIASES names associated with it.
Resolution:
To check what the LRECL is set at you want to do a LISTCAT against the user catalog:
LISTCAT ENT(catname) CAT(catname) ALL
and find:
MAXLRECL-----------XXXXX
The Programmer Response is trying to tell you that if your catalog isn't already DEFINEed with the maximum LRECL size of 32400, to redefine it with the maximum LRECL size. This is only possible for catalogs defined before z/OS 1.3. At z/OS release 1.3 and higher, DEFINE of a new USERCATALOG was defaulted to the max record size. To change the LRECL to the max size:
EXPORT the user catalog:
EXPORT USERCAT4 OUTFILE(DD1) TEMPORARY
DELETE with RECOVERY:
DELETE USERCAT4 FILE(DD1) RECOVERY USERCATALOG
DEFINE UCAT:
DEFINE USERCATALOG (NAME(USERCAT4)ICFCATALOG )
IMPORT into empty
IMPORT INFILE(DD1) ALIAS LOCK INTOEMPTY
OUTDATASET(USERCAT4)
If you are already at the maximum LRECL size, you will need to SPLIT the USERCATALOG into two or more USERCATALOGS using REPRO MERGECAT which will allow you to DELETE ALIASES from the old USERCATALOG and reDEFINE ALIASES to the new USERCATALOG(s).
NOTE: at the z/OS 1.13 and higher levels, there is an extended alias function which greatly increases the number of aliases that can be associated with a catalog.
See the Manual DFSMS: Managing catalogs for more on this function available in z/OS 1.13 and higher releases
Related Information
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG90","label":"z\/OS"},"Component":"5695DF105 - DFSMS CATALOG","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"1.1;1.10;1.11;1.12;1.13;1.2;1.3;1.4;1.5;1.6;1.7;1.8;1.9;2.1;2.2;2.3;2.4","Edition":"","Line of Business":{"code":"LOB56","label":"Z HW"}}]
Historical Number
4902309
Was this topic helpful?
Document Information
Modified date:
03 September 2021
UID
isg3S1000464