This diagnostic message was inadvertently left in the PTF level code for
V3.1.1.3.
     The problem was originally reported on AIX with APAR IX77359 and was
sysrouted to MVS APAR PQ16078.
      The problem is fixed in the 3.1.2.0 PTF level (UQ20342)... the APAR
(PQ16078) never made into theV3.1.1.3 README.
       Apply the following ZAP and recycle ADSM.  The ZAP will "nop" the BALR
to our debug message.
       Sorry for the inconvenience.

    //ZAP JOB MSGLEVEL=(1,1),MSGCLASS=H,REGION= 1024K
//*  Job to eliminate the ANR9999D message from ADMFS during select
//*  processing. Apply ZAP to V3.1.1.3 level server.
//*  This problem is documented in APAR PQ16078 and the fix was included
//*  and ADSM EM PTF UQ20342.
//STEP1 EXEC PGM=AMASPZAP
//SYSPRINT DD SYSOUT=*
//SYSLIB DD DSN='ADSM.V3113.LINKLIB',DISP=SHR
//SYSIN DD *
 NAME DSMSERV  ADMFS$
 VER 00631A 05EF
 REP 00631A 0700
 *
/*
Thanks, Bob La Brie  ADSM
Development


ADSM-L AT VM.MARIST DOT EDU on 10-09-98 07:07:39 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: ADMFS(2200) message


This line is generated by some "select" requests in the admin cmdline
client or odbc interface and not solved (as far as I know, I see the lines,
too). You may contact your IBM Software Support, they know further details.

Regards
Roger