APAR Identifier ...... II13276 Last Changed ........ 06/07/25
HELP FOR CBRXLCS " NO DEVICE POOLS EXIST ..."
Symptom ...... MS MSGIGD306I Status ........... CLOSED CAN
Severity ................... 4 Date Closed ......... 02/04/25
Component .......... INFOV2LIB Duplicate of ........
Reported Release ......... 001 Fixed Release ............
Component Name V2 LIB INFO ITE Special Notice
Current Target Date .. Flags
SCP ...................
Platform ............
Status Detail: Not Available
PE PTF List:
PTF List:
Parent APAR:
Child APAR list:
ERROR DESCRIPTION:
There are several variations of this error. For example, you
might see:
IGD330I ERROR OCCURRED DURING CBRXLCS PROCESSING- (msgIGD330I)
NO DEVICE POOLS EXIST TO FULFILL REQUEST FOR TDSI SPECIFICATION
IGD306I UNEXPECTED ERROR DURING CBRXLCS PROCESSING
RETURN CODE 12 REASON CODE 49 (rc12 rsn49)
THE MODULE THAT DETECTED THE ERROR IS IGDIDMUS
SMS MODULE TRACE BACK - IDMUS IDMSU IDM00 SSIRT
SYMPTOM RECORD CREATED, PROBLEM ID IS IGD00094
.
With the IGD306I, you might also see:
NO DEVICE POOLS EXIST TO FULFILL REQUEST FOR SPECIFIED RECORDING
TECHNOLOGY. ( RETURN CODE 12 REASON CODE 66 rc12 rsn66)
or
NO DEVICE POOLS TO FULFILL REQUEST FOR SPECIFIED MEDIA TYPE
( RETURN CODE 12 REASON CODE 67 rc12 rsn67)
.
Things to check:
1) For SCRATCH allocations it is usually a problem with Data
Class. Verify that the correct Data Class is being selected
and that the ISMF definition is correct.
.
Check your job output to determine which Data Class was
assigned. If it is not the correct one, check your ACS
routine logic. If it is the one you expect, display the Data
Class definition in ISMF and look at the recording technology
and/or media type specified.
Verify that the recording technology and/or media type
specified is appropriate for the devices in your library(s).
For instance, if you have upgraded all of your devices to a
new model (3590 Model B -> 3590 Model E) and your data class
still referenced the old recording technology, this could be
one cause for the failure.
Assigning a Data Class is optional, and if one is specified,
assigning a media type and recording technology is used to
direct your allocations to a particular device type within a
library (or set of libraries). This is especially important
if your library contains multiple device types.
2) For PRIVATE allocations, display the volume with:
D SMS,VOL(volser) to determine which library the volume
resides in, then display the library with:
D SMS,LIB(libname),DETAIL and the drives with:
LI DD,libname
Make sure the ATL and drives are ONLINE and OPERATIONAL and
that the DEVICE TYPE is correct
.
If you have just upgraded your drives to a new recording
technology, (this is especially important if all of the
drives in your library have been upgraded) you may need to
set the Special Attribute ( READCOMPAT ) indicator in your
volume records to be able to read your old PRIVATE tapes on
your new drives.
RMM users can build a CLIST as follows:
RMM SV VOLUME(*) OWNER(*) LIMIT(*) STATUS(MASTER) -
LOCATION(libname) -
CLIST('RMM CHANGEVOLUME ' , ' SPECIALATTRIBUTES(RDCOMPAT) ')
.
To update only the TCDB, you can use IDCAMS:
Example:
//ALTERVOL JOB ...
//STEP1 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=A
//SYSIN DD *
ALTER VAL0001 -
VOLUMEENTRY -
SATTR(RDCOMPAT)
/*
or "ALTER 'Vvolser' VOLENT SATTR(RDCOMPAT)" TSO command.
For DFSMS releases below R1F0, verify that you have the fix
for APAR OW41005 as it corrects a problem with this ALTER
command.
.
See section below on "Other 3590B to E migration issues:"
.
3) For new installs or upgrade of existing drives:
- Verify device type is correct in displays resulting from
the following commands:
.
LI DD,name:
example output: CBR1220I Tape drive status:
DRIVE DEVICE LIBRARY ON OFFREASN LM ICL ICL MOUNT
NUM TYPE NAME LI OP PT AV CATEGRY LOAD VOLUME
0BA4 3590-E LIB1 Y N N N A NONE N
.
DS QTAPE,drive_num,1,RDC,UCB
example output:
UNIT DTYPE DSTATUS CUTYPE DEVTYPE CU-SER DEV-SERIAL ACL LIBID
1200 3590L ON-NRD 3590A60 3590B1A 0113-4 0113-46559 I 15191
READ DEVICE CHARACTERISTIC
3590603590100110 4EDC0000B0D7CC00 (16 digits) 3590603590100000
(here were)
(deleted to) ||
(fit display) ||
for example this byte should be x'09'
for a 3590E (256 track)
If this is wrong and you have all the
required software from the PSP
buckets, contact Hardware support.
It could be a H/W setup or microcode
level problem.
If the above displays are incorrect, check PSP buckets (like
3494DEVICE and 3590DEVICE) for missing maintenance. For example
if you have just upgraded from 128 track 3590 Model B drives to
256 track 3590 Model E drives and are not yet at R1F0, you may
be missing the ENABLING APAR OW38744
.
If you can't resolve the problem using the steps above, please
collect the SYSLOG, JOBLOG, software LOGREC entry (logrec ID
included in the IGD306I message) and take a dump of the MASTER
address space so our Devices Services group can analyze the
library control blocks. Please use the following SDATA parms:
SDATA=(TRT,LPA,CSA,PSA,GRSQ,SUM,ALLNUC,SQA,LSQA,RGN,SWA)
.
Other 3590B to E migration issues:
From text of APAR OW38975 NEW FUNCTION - D/T3590-E1X :
Note: With this new function, it is now possible to have either
128 or 256 track recording technology on MEDIA3 and MEDIA4
tapes. Previously, only 128 was possible so during cartridge
entry (of a previously unknown volser), prior to invoking the
cartridge entry exit CBRUXENT, OAM would always set the
recording technology (field UXEREC) with 128 track, regardless
of whether the entry default use attribute was SCRATCH or
PRIVATE. Now with this support, for media types MEDIA3 and
MEDIA4, OAM will only set 128 track if the entry default use
attribute is PRIVATE (set in field UXEUSEA) and no recording
technology has been supplied via the entry default dataclass.
(A recording technology may be supplied via a default Entry
Data Class, but in a mixed 128/256 environment, it could be
wrong). So either way (default is SCRATCH then to PRIVATE, or
default is PRIVATE), if it is going to end up PRIVATE, the exit
needs to supply or verify that the recording technology is
correct. Check with your tape management system to ensure that
the supplied exit properly verifies and/or sets the recording
technology.
Also, if a library is upgraded or installed with only 3590-E1x
devices, to be able to read a 128-TRACK volume:
1> for a library resident volume, IDCAMS VOLUME ALTER can be
used to set the read-compatibility indicator in the special
attribute field SPECIALATTRIBUTE RDCOMPAT .
2> for a shelf-resident volume being entered into the library,
the entry exit can set the read-compatibility indicator in
the special attribute field UXESPEC to UXERDCOM.
3> or on an individual usage of the volume, LABEL=(,,,IN) can
be specified on the DD statement of your JCL..
.
Refer to the OAM PISA for Tape Libraries (SC35-0427) for
details: http://www.ibm.com/servers/eserver/zseries/zos/bkserv/
LOCAL FIX:
For any HW changes, review informational apar
II09065. Adding new drives, new port assignments,
HW microcode upgrades, general upgrades to the
ATL/VTS/Peer to Peer, control units, or LM's in general
will require an IODF activate. In some cases an IPL, or
an IML of the control unit or mainframe may be needed.
Confidentiality notice: The information included in this e-mail,
including any attachments, is for the sole use of the intended recipient
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure, distribution or similar action is
prohibited. If you are not the intended recipient, please contact the
sender and delete all copies of the original message immediately.
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Crispin Hugo
Sent: Monday, July 09, 2007 10:46 AM
To: [email protected]
Subject: Re: 3590-e11
Can anybody out there get a copy of II13276 from IBM. Is about
converting 3590b to 3590e but I can't get it to download. It just times
out.
Crispin Hugo
Systems Programmer, Macro 4
http://www.macro4.com/
Macro 4 plc, The Orangery, Turners Hill Road, Worth, Crawley, RH10 4SS
Direct Line: +44 (0)1293 872121 Switchboard: +44 (0) 1293 872000
Fax: +44 (0) 1293 872001
________________________________________________________________________
This email has been scanned for all known viruses by the MessageLabs
Email Security Service and the Macro 4 plc internal virus protection
system.
________________________________________________________________________
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send
email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search
the archives at http://bama.ua.edu/archives/ibm-main.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
