APAR status
Closed as canceled.
Error description
MSGIEF506I occurred stating that there were no storage volumes to allocate to temporary datasets, however, there were a number of 3380 D/T3380 DASD devices that were online, ready, and mounted as storage volumes. Also, trying to submit a job through ISPF received a message indicating that ISPF could not allocate the control dataset for the submitted JCL. Jobs submitted through batch worked when specifying temp datasets that contained UNIT information on the JCL statement. Additional Symptoms: MsgIKJ56221I Volume necessary to satisfy your request not on system and cannot be mounted . MsgIKJ58508I Dataset Not Allocated System or Installation error. msgIKJ56223I Space Request Denied by Installation Exit, Installation Exit Reason Code IS X'nnnn' SVC99 ALLOCATE RC0218 rc021C msgIEF290E IEF290E EDIT &EDIT msgIEF238D msgIEF244I - UNABLE TO ALLOCATE xxx UNIT(S) msgIEF877E - NEEDS xxx UNIT(S) FOR VOLUME SCRTCH See Responder's Text of this Info APAR for further information. See, also, the responder's Text of OW21591. Beware: The 'LISTU userid TSO' command may not work on all systems, you may need to use 'LISTUSER userid TSO' Additional Keywords: Howto
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
When a DYNAMIC allocation is being performed and UNIT information is required but not specified (no DALUNIT text unit) then the system defaults the unit required. If the dynamic allocation is being done under TSO in Foreground, then the system will use the default unit from the PSCB (Protected Step Control Block), which may contain information from SYS1.UADS or the TSO segment of a security system's (such as RACF) file. If the PSCB does not contain a default unit OR if the dynamic allocation is NOT being done under TSO running in the foreground, then: - the system will use the default unit specified in the ALLOCXX parmlib member (or the allocation default CSECT IEFAB445 for pre-MVS 4.1.0 (R410) systems). ==> - For *NON* SMS managed data sets with DISP = NEW or MOD, SMS will then OVERRIDE the dynamic allocation default unit with the SMS default unit specified in the SMS Source Control Data Set (SCDS). For batch processing (i.e., JCL DD statement allocations), SMS will supply the default unit from the SMS Control Data Set for NEW or MOD requests which have no UNIT coded. You may get msgIEF210I when an invalid unit is included in the SMS Source Control Data Set or when there is no active SMS configuration. Summary of the above "where defaults are taken from": - SMS-managed dataset o dynamic allocation -- ACS routines decide o batch allocation -- ACS routines decide - non-SMS-managed dataset o dynamic allocation + TSO in Foreground -- Default comes from TSO segment of RACF or other security system's file, or SYS1.UADS if no TSO segment, or SCDS if no SYS1.UADS info, or ALLOCxx if no SCDS info. + all else -- Default comes from SCDS EXCEPT --Default comes from ALLOCxx if: o DISP = SHR or OLD, or o If no SCDS info o batch allocation -- default comes from SCDS. Note to Level 2: If the customer absolutely needs to change the default UNIT value in his ALLOCxx member, see the Scratch Pad for an UNSUPPORTED, USE-AT- YOUR-OWN-RISK method of doing that. Since there is currently no "SET ALLOC=" command to change any ALLOCxx values, this is the only way such a change can be accomplished. Note: If the default UNIT parameter which Allocation retrieves is invalid (for example if the defaulted UNIT is not in the EDT), that defaulted UNIT parameter will be error flagged and the allocation failed IF AND ONLY IF that UNIT parameter is REQUIRED for the allocation. If the default UNIT is "thrown away" by Allocation (as it would be for DISP=SHR or OLD datasets) then the invalid default UNIT parameter will not be error flagged. To verify the SCDS parms, you may enter SMS via ISMF. You must be a Storage Administrator, so you may need to select option 0.0 and select #2 for Storage Administrator (versus #1 for User Mode). Exit and re-enter ISMF and select option 8, CONTROL DATA SET section. Select option 1 to DISPLAY the configuration and the next panel will show the default unit. This may be a generic (eg. 3380) or an esoteric (eg. SYSDA). You may be seeing an 'error' in device allocation if the devices being allocated are not included in the default unit group. This default unit specification is the group of devices that will be used when unit info is required but not provided on the allocation request. It does NOT indicate which devices SMS is to default to for SMS managed datasets. The default unit could also be specified in the ALLOCxx parmlib member. Check this member and look for the UNIT NAME(unit-name) statement and change it accordingly. You can check for the default RACF UNIT (TSO segment) by issuing the 'LISTU userid TSO' command. This will display the UNIT default for the userid. ISPF has its own default for allocations done via option 3.2 A (ISPF32 ISPF32A), which is stored in the ISPF Configur- ation table. Information about the IBM-supplied default and how to modify it (and other options) using the ISPF Configur- ation Utility is discussed in detail in the ISPF Planning and Customizing manual (SC28-1298), Chapter 4 (Customizing PDF), Section 4.12 (The ISPF Configuration Table). The keyword whose default value you'll want to change is PDF_DEFAULT_UNIT. Customers who have older systems which do not have the ISPF Configuration Table and Utility should contact the IBM Support Center and ask for the comparable information for older systems which is on the Scratch Pad of this APAR. It is not being included here in the main text of the APAR simply to avoid the potential problem of someone thinking that THAT is the current information. For datasets allocated with SDSF, see PN64879.
APAR Information
APAR number
II06423
Reported component name
V2 LIB INFO ITE
Reported component ID
INFOV2LIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1992-10-06
Closed date
1992-10-06
Last modified date
2007-06-06
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
13 December 2020