IBM Support

PM66742: TSO SESSION HANGS WHEN CREATING VSAM FILE AND CHOOSING NON-VSAM AS A "LIKE" DATASET.

A fix is available

Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Error DescriptionÏ
When a user created a new VSAM dataset and selected a 'like
existing VSAM dataset'.  Instead of choosing option 5 - LDS,
they accidentally chose the wrong option (6) which is NON VSAM.

The user's TSO session hung, requiring it to be cancelled.

Local fix

  • Local FixÏ
n/a

Problem summary

  • ****************************************************************
* USERS AFFECTED: All File Manager users                       *
****************************************************************
* PROBLEM DESCRIPTION: When copying to an LDS data set and the *
*                      data set is to be defined using an      *
*                      existing LDS data set as the model and  *
*                      option 6 (Non VSAM) is selected on the  *
*                      data set allocation selection panel     *
*                      FMNPPALN, File Manager may loop.        *
****************************************************************
* RECOMMENDATION: Apply the provided PTF.                      *
****************************************************************
The correct parameters are not being set for the data set
allocation routine.

Problem conclusion

  • File Manager has been modified to correct the problem.

Temporary fix

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    PM66742
    • 

  • Reported component name
    FILE MANAGER Z/
    • 

  • Reported component ID
    5655W4700
    • 

  • Reported release
    B10
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2012-06-13
    • 

  • Closed date
    2012-07-25
    • 

  • Last modified date
    2012-08-08
    • 





    

  • APAR is sysrouted FROM one or more of the following:
    

    • 

  • APAR is sysrouted TO one or more of the following:
    

    
PM69901
    

    • 



Modules/Macros


    

  • FMN0LVL

    



Fix information


    

  • Fixed component name
    FILE MANAGER Z/
    • 

  • Fixed component ID
    5655W4700
    • 



Applicable component levels


    

  • RB10  PSY  UK80527
       UP12/08/02  P  F207
    • 



Fix is available


    

  • Select the PTF appropriate for your component level.
You will be required to sign in. Distribution on physical
media is not available in all countries.
    








      
              
                            

              

              [{"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":"B10","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSXJAV","label":"File Manager for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B10","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            08 August 2012
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback