Stupid question, but I have to ask.  You DO have a PROD=xx statement in
    IEASYSxx pointing to your IFAPRDxx member, don't you?  Try issuing the
    following console command:

    D PROD,REG

    to list all of the registered products.  Returned output should be of
    the format (sans word-wrap); verify that ADSM is in the list (it's not
    in mine because we don't run it on S/390 - yet):

    TA  RCS   D PROD,REG
      -          IFA111I 14.52.15 PROD DISPLAY 550                    C
      - S OWNER            NAME             FEATURE          VERSION  ID
      - E IBM CORP         OS/390           DFSMSHSM         **.**.**
    5645-001
      - E IBM CORP         OS/390           DFSMSRMM         **.**.**
    5645-001
      - N IBM CORP         OS/390           JES2             01.01.00
    5645-001
      - E IBM CORP         OS/390           OS/390           01.02.00
    5645-001
      - E IBM CORP         PSF/MVS          PSF/MVS          02.02.00
    5695-040
      - E IBM CORP         TCP/IP FOR MVS   TCP/IP BASE      03.02.00
    5655-HAL

    ==============================================================
    Hi,

        We are upgrading from MVS 5.2 and , yes, ADSM is running fine on
    it.
        I spoke initially with ADSM Level 1 and they suggested I update
        IGDDFPKG with 'DFSMS_FEATURE=ADSM'.  It was tried but I still got
    the
        ANR9954S msg.  I have since heard from IBM MVS support that
    IGDDFPKG
        is no longer used for licensing features (apparently it was
    replaced
        with IFAPRDxx in OS/390 V1.2 and later).  We have coded IFAPRDxx
    with
        ADSM and it still fails.

        Frank Rehor
        The Clorox Services Company
        frank.rehor AT clorox DOT com