ADSM-L

Re: error on 3590 definition

1997-03-10 12:41:56
Subject: Re: error on 3590 definition
From: Zoltan Forray <ZForray AT MAIL.UCC.VCU DOT EDU>
Date: Mon, 10 Mar 1997 12:41:56 EST
 Yes, you were right. That is exactly what I did. I didn't have any
 documentation that told me otherwise.

 When I searched IBMLINK for ADSM 3590, I found APAR PQ00236 that stated that
 3590 support was for ADSM MVS/VM SRV was targeted for 97/04/14 and is still
 open.

 How do I get PTF12 ?  I just implemented PUT9701 on my base system. And the
 ADSM Web site says the current maintenance level is .09 (I am at .10).


______________________________ Reply Separator _________________________________
Subject: error on 3590 definition
Author:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> at 
Internet-Mail
Date:    3/10/97 12:08 PM


Zoltan....
it sounds like you may have defined the 3590 device class with
DEVTYPE=CARTRIDGE.  You need to define the DEVTYPE=3590 for this
devclass.  The 3590 support on ADSM/MVS came out in ptf 10, so
it's not documented in the manuals...if you are prior to pft 10 service
level, I would suggest applying the latest ptf (12)...check the online
help (HELP DEFINE DEVCLASS) for details...greg tevis

 ============================================================================
We just attached our 3590 via ESCON channel to our 9672 from inside our 3494
ATL.

I tried to get ADSM to talk to it. I get the message:

       ANR9999D PVRCART(1572): UCB Device Type bytes 3/4 are 80/83, not a
       recognized CARTRIDGE device.
<Prev in Thread] Current Thread [Next in Thread>