IBM Support

PI16985: DSNJLOGF SHOULD ISSUE MSGDSNJ990I WITH RC04 WHEN ACTIVE LOG DATA SET IS GREATER THAN 4 GB IN SIZE.

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

  • The DSNJLOGF utility should issue MSGDSNJ099I with a return
code of 4 when the new active log data set is 4 GB or greater
in size.  The DSNJLOGF utility should then complete with
completion code 8.  The active log data sets must be less than
4 GB in size.

Local fix

  • 



Problem summary


    

  • ****************************************************************
* USERS AFFECTED: All DB2 for zOS Version 11 users.            *
****************************************************************
* PROBLEM DESCRIPTION: The DSNJLOGF utility does not issue     *
*                      MSGDSNJ990I when formatting a log       *
*                      data set that is 4 GB or greater in     *
*                      size.                                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
DB2 only supports active log data sets less than 4 GB in
size.  The log format utility, DSNJLOGF, should issue
DSNJ990I SHOWCB ERROR, DDNAME = SYSUT1 RETURN CODE = 0004
REASON CODE = 0000
when attempting to format a log data set that is 4 GB or
greater in size, and the DSNJLOGF job should complete with
return code 8.

    



Problem conclusion


    

  • DSNJLOGF has been changed to issue MSGDSNJ990I when attempting
to format a new active log data set that is 4 GB or greater in
size.

    



Temporary fix


    

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    PI16985
    • 

  • Reported component name
    DB2 OS/390 & Z/
    • 

  • Reported component ID
    5740XYR00
    • 

  • Reported release
    B10
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt
    • 

  • Submitted date
    2014-04-29
    • 

  • Closed date
    2014-05-15
    • 

  • Last modified date
    2014-06-03
    • 





    

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

    • 

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

    
UI18031
    

    • 



Modules/Macros


    

  • DSNJLOGF

    



Fix information


    

  • Fixed component name
    DB2 OS/390 & Z/
    • 

  • Fixed component ID
    5740XYR00
    • 



Applicable component levels


    

  • RB10  PSY  UI18031
       UP14/05/31  P  F405
    • 



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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"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":"11.0","Edition":"","Line of Business":{"code":"","label":""}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            03 June 2014
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback