IBM Support

OA41555: WHEN MORE THEN 59 VOLSERS ARE SPECIFIED IN JCL SER FIELD SMS WILL MOVE ALLOCATION TO NON-SMS ALLOCATION WITHOUT ANY MESSAGES.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • When more then 59 volsers are specified in the JCL SER field for
SMS allocation, SMS will move the allocation to non-SMS without
any messages or indications that it did so.  Other documentation
indicated that 255 TAPE volumes can be used in SMS.  However,
SMS has a limitation that only up to 59 volsers can be specified
in the JCL.

As an FYI, this problem has also occurred at z/OS 1.6 level.

Local fix

  • Use less than 60 volsers in JCL SER field.
Addtional Keywords:
IGD11103I MSGIGD11103I

Problem summary

  • ****************************************************************
* USERS AFFECTED: HDZ1B10 USERS AND ABOVE                      *
****************************************************************
* PROBLEM DESCRIPTION: SEE ERROR DESCRIPTION                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
SUMMARY: SMS has a limitation that only up to 59 volsers can be
specified in the JCL. When more than 59 volsers are specified,
SMS will process the allocation as non-SMS managed.

Problem conclusion

  • 



Temporary fix


    

  • 



Comments


    

  • CONTROL NUMBER: SM01467

This APAR is being closed FIN with concurrence of the submitting
customer. A solution to this problem will be delivered in a
DFSMS release, if there is one,  to be available within the next
18 - 24 months.

This problem is fixed in z/OS DFSMS V2R1.

    



APAR Information




    

  • APAR number
    OA41555
    • 

  • Reported component name
    STORAGE MGMT SU
    • 

  • Reported component ID
    5695DF101
    • 

  • Reported release
    C10
    • 

  • Status
    CLOSED  FIN
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt
    • 

  • Submitted date
    2013-02-26
    • 

  • Closed date
    2013-03-07
    • 

  • Last modified date
    2015-08-11
    • 





    

  • 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


    

  • RC10  PSY
       UP
    • 








      
              
                            

              

              [{"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":"C10","Edition":"","Line of Business":{"code":"","label":""}}]
              

                                                                    

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            11 August 2015
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback