IBM Support

PM98323: DB2 RECORDS IN A DYNAMIC EXTRACT FILE ARE NOT CORRECTLY IDENTIFIED AND ARE PROCESSED AS IMS RECORDS

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

  • IMS/DB2 log records extract fine, but when trying to process the
extract log file, it no longer correctly identifes the DB2 log
records. It either flags them as unknown type ( code ) or
incorrectly identifes them as an IMS log record type that
happens to have the same identifier code.

Local fix

  • 



Problem summary


    

  • ****************************************************************
* USERS AFFECTED: Users of IMS Problem Investigator V2.3       *
****************************************************************
* PROBLEM DESCRIPTION: DB2 records in a dynamic extract file   *
*                      are not correctly identified and are    *
*                      processed as IMS records                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
IMS PI uses record/file heuristics to identify input record
types, these heuristics are lost when a dynamic extract file
is created which results in DB2 records not being correctly
identified.

    



Problem conclusion


    

  • Place a record identifier in DB2 records that are extracted
using the dynamic extract facility so that they may be
subsequently reprocessed.

    



Temporary fix


    

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    PM98323
    • 

  • Reported component name
    IMS PROBLEM INV
    • 

  • Reported component ID
    5655K5000
    • 

  • Reported release
    230
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2013-10-02
    • 

  • Closed date
    2013-12-03
    • 

  • Last modified date
    2014-01-02
    • 





    

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

    • 

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

    
UI13143
    

    • 



Modules/Macros


    

  • ALZBRFMT ALZCSQIO ALZD01   H28T230J

    



Fix information


    

  • Fixed component name
    IMS PROBLEM INV
    • 

  • Fixed component ID
    5655K5000
    • 



Applicable component levels


    

  • R230  PSY  UI13143
       UP13/12/05  P  F312
    • 



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":"2.3.0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX8A4","label":"IMS Problem Investigator"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.3.0","Edition":"","Line of Business":{"code":"","label":""}}]
              

                                                                    

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            02 January 2014
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback