TRAC017S SCHEDULE ALLOCATION ERROR: SDAILY DD=SYSPRINT, ERROR=0218041D

Products

• Jobtrac

Issue/Introduction

Getting the following error message when trying to load any SCL:

TRAC017S SCHEDULE ALLOCATION ERROR: eventname   DD=SYSPRINT, ERROR=0218041D .

The SCL is being put on HOLD after this error.

Environment

Release : 11.0

Resolution

This error indicates that Jobtrac is not able to allocate the required temporary datasets when loading the SCLs.

The specific dynamic allocation error code can be seen in this message:

 

TRAC017S SCHEDULE ALLOCATION ERROR: eventname DD=SYSPRINT, ERROR=0218041D 

 

*-----                                                                  
Explanation:  The dynamic allocation error code is 0218.                
                                                                         
This message indicates that the volume specified as input to dynamic    
allocation is not mounted on any of the devices associated with the      
specified or defaulted UNIT parameters. Some possible reasons for this  
error are:                                                              
                                                                         
o   The dynamic allocation tried to use a VIO-eligible unit, but the data
    set name was not a temporary dsname (DSN=&&dsname).                  
                                                                         
o   The dynamic allocation tried to put a data set with a non-temporary  
    dsname (DSN=dsname) onto a real DASD volume but                      
                                                                         
    1.  No volume serial number was supplied, and                        
                                                                         
    2.  no volumes on the system were mounted with a USE attribute of    
        STORAGE.                                                        

 

 

Jobtrac uses the JOBTRA00 parameter AUNIT to indicate what type of device will be used.

 

The root cause of the problem that originated this document was that all the DASD volumes mounted with the STORAGE attribute were full