After you get those MVS messages for about 5 minutes, it is followed by
 ANR5373I  UNABLE TO ALLOCATE TAPE DRIVE WITH DEVICE TYPE device type FOR
TAPE
 ..,R


 IEE305I ..,R     COMMAND INVALID

 volume ID. REPLY 'C' TO CANCEL OR 'R' TO RETRY.



Usually "r" is your best response. We have it automated. ADSM keeps retrying
until it finally gets a drive.
Incidentally, the "Vnnnn" is a suffix ADSM adds internally to identify the
tape dsn; the suffix only appears on some of the MVS messages, I've never
bothered to figure out which ones and why.



Bob Siska
National Computer Systems
Iowa City IA
Bob_Siska AT ncs DOT com
 ----------
"Let's pretend you're Sherman and I'm Mister Peabody..."
 ----------
From: owner-adsm-l
To: ADSM-L
Subject: DATASET NOT ALLOCATED
Date: Tuesday, May 27, 1997 10:58AM

Hi there!

Can somebody please help, we've been receiving the following message on
ADSM MVS server for quite some time, so this came to our attention to
find out what does it mean and what effect does it have to the ADSM
database.

IEC705I TAPE ON 360, A04425,SL,COMP,ADSM,ADSM,ADSM.BFS
IEC271I MESSAGE DISPLAY 'A04425' ON 360 ISSUED BY JOB ADSM
IKJ56241I DATA SET ADSM.BFS.V206 NOT ALLOCATED+
IKJ56241I NO UNIT AVAILABLE

Any help please will be highly appreciated.

Thanks in advance

Brenda Mekgwe
Datavia, Transnet
South Africa


BRENDA MEKGWE