Actually the OS/390 upgrade maight have everything to do with your problems.
Did you use a severpac for the upgrade?  Did you order ADSM in the
serverpac?  I suspect this is what happened.  Check with your OS/390
systems programmers.  Ask them if ADSM was integrated into the serverpac.
You just might have installed the version 3 server by installing the OS/390
upgrade.  Ask the syspgmrs to 'query LMOD ANRSERV' in the smp/e dialogs.


--
--------------------------
--------------------------
Bill Colwell
Bill Colwell
C. S. Draper Lab
Cambridge, Ma.
bcolwell AT draper DOT com
--------------------------
In <9909209378.AA937851652 AT ccmail.adp.wisc DOT edu>, on 09/20/99
In <9909209378.AA937851652 AT ccmail.adp.wisc DOT edu>, on 09/20/99
   at 01:20 PM, James SPORER <james.sporer AT CCMAIL.ADP.WISC DOT EDU> said:

>     This dd card //DSMAMENG DD in your adsm server jcl is not pointing to
>     the most current file.  Your upgrade of the operating system had
>     nothing to do with this problem.  You installed some maintenance on
>     your adsm system and this is causing the problem.
>     Jim Sporer
>


>______________________________ Reply Separator 
>_________________________________
>Subject: Problem with ADSM on OS/390
>Author:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>  at IPNET
>Date:    9/20/99 2:09 PM


>We migrated our OS to OS/390 ver. 2.5. We have ADSM for MVS ver 2. The
>clients are ADSM ver. 3. I had several problems with the DB but I could 
>solve it. Now, the ADSM server is showing the follow message:
>
>10.51.29 STC05063  << Message number 2121 not available for language AMENG
>>>
>11.02.44 STC05063  << Message number 406 not available for language AMENG >>
>
>This kind of message is shown frequently, and when I start the ADSM
>Administrative GUI, this shows the same message in the panels.
>
>Thanks in advance.
>
>Jorge Rodríguez
>ADSM Adminstrator
>CANTV
>Caracas-Venezuela
>