IBM Support

LISTCAT of NONVSAM ALIAS receives IDC3009I RC8 RSN42

Question & Answer


Question

1. DEFINE USERCATALOG TEST1CAT 2. DEFINE USERCATALOG TEST2CAT 3. DEFINE ALIAS TEST1 RELATE(TEST1CAT) 4.

Answer

      • Description:

        1. DEFINE USERCATALOG TEST1CAT
        2. DEFINE USERCATALOG TEST2CAT
        3. DEFINE ALIAS TEST1 RELATE(TEST1CAT)
        4. DEFINE ALIAS TEST2 RELATE(TEST2CAT)
        5. DEFINE NONVSAM TEST2.NONVSAM
        6. DEFINE ALIAS TEST1.ALIAS RELATE (TEST2.NONVSAM)

        The expectation is that the alias, TEST1. ALIAS for the NONVSAM data set should be cataloged in user catalog TEST1CAT as the catalog alias TEST1 points to user catalog TEST1CAT. Instead the alias TEST1.ALIAS is cataloged in TEST2CAT with its' associated NONVSAM data set TEST2.NONVSAM.

        A subsequent LISTCAT fails with:

        LISTCAT ENT(TEST1.ALIAS) ALL
        IDC3012I ENTRY TEST1.ALIAS NOT FOUND
        IDC3009I ** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLEG-42
        IDC1566I ** TEST1.ALIAS NOT LISTED


        Resolution:

        An alias of a NON-VSAM data set must be defined in the same catalog as the data set. For the data set to be found by its alias, there must be an alias in the master catalog pointing to the catalog that contains the alias name. Both the data set alias, and the data set name MUST be in the SAME catalog.

        IBM is not in a position to change this because of the impact it could have on existing installations as well as the technical issues it would introduce in the catalog code.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG90","label":"z\/OS"},"Component":"5695DF103 - DFSMS ACCESS METHOD SERVICES","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"1.1;1.2;1.3;1.4;1.5;1.6;1.7;1.8;1.9;1.10;1.11;1.12;1.13;2.1;2.2;2.3;2.4","Edition":"","Line of Business":{"code":"LOB56","label":"Z HW"}}]

Historical Number

8704440

Document Information

Modified date:
03 September 2021

UID

isg3S1000158