Updates to DB2 Utilities Enhancement Tool for z/OS V2.1 User's Guide

Product documentation


Abstract

Updates that apply to DB2® Utilities Enhancement Tool for z/OS® V2.1 User's Guide (SC19-1224-03)

Content

The most recent update is listed first.




Update 9
Date of change: December 19, 2012
Topic: Customization worksheets
Change description: Variable names changed for the primary DB2 subsystem as follows:

?ABPMAPBP? changed to ?ABPTMPBP?.
?ABPMAPDB? changed to ?ABPTMPDB?.
?ABPMAPSG? changed to ?ABPTMPSG?.



Update 8
Date of change: December 19, 2012
Topic: Hardware and software prerequisites
Change description: The following documentation change was made in support of APAR PM09829 (PTF UK60173), which introduced the PRACTICE element.

Software prerequisites
To use the enhancements and fixes provided by PTF UK60173 and later PTFs, DB2 UET requires the following software:
DB2 UDB for z/OS Version 8 in new function mode, or a later version of DB2 with the corresponding version of the DB2 Utilities Suite for z/OS.



Update 7
Date of change: June 25, 2011
Topic: DB2 LOAD utility enhancements, PRESORT option
Change description: The following restriction has been added to the usage considerations:

Restriction: A failure in the DB2 Utilities Enhancement Tool parser will now occur (including the informative message ABPP9939E) when the PRESORT option is used with the FORMAT UNLOAD, FORMAT SQLDS, FORMAT INTERNAL keywords and in those instances where no field specifications are supplied with the LOAD utility. DB2 Utilities Enhancement Tool will terminate the utility before the utility is executed by DSNUTILB.



Update 6
Date of change: June 25, 2011
Topic: Messages
Change description: The following parser component message has been added:

ABPP9939E Keyword PRESORT is incompatible with &VARIABLE (where &VARIABLE can be one of the following values: FORMAT UNLOAD, FORMAT SQLDS, FORMAT INTERNAL, or NO FIELD SPECS).

Explanation: PRESORT is not supported with the specified criteria.

User response: Correct the syntax and resubmit the job.


Update 5
Date of change: March 31, 2011
Topic: Multiple
Change description: In APAR PM22685, the following updates were made for DB2 V10 exploitation: Support Hash Table keys using the LOAD utility and PRESORT functionality.

  • In Chapter 3, “Customizing and starting DB2 Utilities Enhancement Tool”, section “Running the Customization Utility for the primary DB2 subsystem”, Step 8 has been updated with the following information:

    8. Choose option 2 (Installation customization) from the Customization Menu to customize the primary DB2 subsystem. The Install Customization - Variables panel is displayed as follows:
     
    Figure 6. Install Customization - Variables panel
     
    IBM DB2 Utilities Enhancement Tool                                    
    Installation Customization - Variables                                    
                                                                More:     +
                                                                                 
    ABPID ................................ ____      (?ABPID?)          
    SVC Number ........................... ___       (?SVC?)            
    ABP Started Task User ID ............. ________  (?ABPSTCID?)        
    ABP Started Task SYSOUT Class ........ _         (?SOUT?)            
    DB2 Database Name .................... ________  (?ABPDB?)          
        Drop Database .................... _         Y or N              
    DB2 SSID ............................. ____      (?SSID?)            
        DBCS ............................. _         (?DBCS?)            
        V10 or later ..................... Y         (?DBVER?)          
    Plan Name ............................ ________  (?ABPPLAN?)        
    Plan Qualifier ....................... ________  (?ABPQUAL?)        
    DSNTEP2 Plan Name .................... ________  (?TEP2PLAN?)        
    Workfile SMS Data Class Name ......... ________  (?ABPWKDC?)        
    Workfile SMS Management Class Name ... ________  (?ABPWKMC?)        
    Workfile SMS Storage Class Name ...... ________  (?ABPWKSC?)        
    Workfile Unit Name ................... ________  (?ABPWKUNIT?)      
    Temp Object Bufferpool Name .......... BP0       (?ABPTMPBP?)        
    Temp Object Database Name ............ ABPGG01T  (?ABPTMPDB?)        
        Drop Temp Object Database ........ Y         Y or N              
    Temp Object Stogroup Name ............ SYSDEFLT  (?ABPTMPSG?)        
    Override Mapping Table ............... _         (?ABPOVRMAP?)      
                                                                                 
    DB2 DSNLOAD Library Name:                                    
    ____________________________________________    (?DSNLOAD?)
    DB2 RUNLIB Library Name:                                    
    ____________________________________________    (?RUNLIB?)  
                                                                     
                                                                     
    Proceed with Customization: N                                
                                                                     
         <ENTER> accept & proceed  <PF3> cancel  

                             
    Important: After applying APAR PM22685, take note of the new ISPF dialog V10 or later field. Type Y if the DB2 SSID being customized is V10 or higher, or N if V9 or lower. If Y, the customization process includes new DBRMs that are necessary in the V10 bind job(s).

  • In Chapter 10, “DB2 LOAD utility enhancements”, in the second paragraph, the PRESORT option description has been updated with the following information:
      PRESORT
      Sorts the rows in the input data set by table object identifier (OBID) and by clustering index key (or by the oldest defined index if no clustering index key is available), or by Hash key prior to loading the data into the target tables.

  • In Chapter 10, “DB2 LOAD utility enhancements”, section “PRESORT option”, the introductory paragraph has been updated with the following information:
      Use the PRESORT option for the DB2 LOAD utility to sort the rows in the input data set by table object identifier (OBID) and by clustering index key (or by the oldest defined index if no clustering index key is available), or by Hash key prior to loading the data into the target tables.

  • In Chapter 10, “DB2 LOAD utility enhancements”, section “PRESORT option”, the subsection “Sort criteria” has been updated with the following information:
      DB2 Utilities Enhancement Tool determines which sort criteria to use based on the type of table space to be loaded, as indicated in the following table:
       
      Table15. PRESORT sort criteria by table space type
       
      Table space/ Table type
      Sort rows by
        Partitioned or universal
        By clustering index key, or if no clustering index key exists, by the oldest defined index if available.
        Simple or segmented
        By table OBID first and then by clustering index key. If no clustering index key is available, sort rows by the oldest defined index instead.
        ORGANIZE BY HASH
        Hash key

       
      If a sort criterion is not defined and no other valid sort criterion is available for a table space, the rows to be loaded into the tables in that table space will not be presorted. For example, if no clustering index key or index is defined for a universal table space, DB2 Utilities Enhancement Tool does not presort rows prior to loading them into tables in that table space. A table defined as ORGANIZE BY HASH is always sorted by the Hash key.

  • In Chapter 10, “DB2 LOAD utility enhancements”, section “PRESORT option”, the fourth bulleted item in the subsection “Usage considerations” has been updated with the following information:

    DB2 Utilities Enhancement Tool does not sort data by an index key (a clustering index key, or if no clustering index is available, the key of the oldest defined index) if the key includes one or more columns with one of the following unsupported data types: DISTINCT, DECFLOAT.




    Update 4
    Date of change: December 20, 2010
    Topic: Messages
    Change description: Modified batch interface message ABPB6050I and started task message ABPS0822I for APAR PM26046, which implemented extended DB2 VSN checking.

    ABPB6050I Initialization is complete.
    DB2SSID=db2_ssid
    DB2REL=db2_version
    NETID=network_name
    LUNAME=logical_unit_name
    LOCNAME=location_name

    Explanation: Initialization processing completed. This message identifies the DB2 subsystem identifier, the DB2 version and release, the network identifier, the LU name, and the local location name.

    User response: None required.

    ABPS0822I
    DB2SSID=db2_ssid
    DB2VER=db2_version
    ABPID= instance_id
    DSNUTILB interception is
    DSNUTILB_interception_status

    Explanation: This message presents the DSNUTILB intercept status for the specified DB2 subsystem.

    User response: None required.




    Update 3
    Date of change: December 20, 2010
    Topic: Multiple
    Change description: Several documentation changes were made for the various usability fixes that are delivered in APAR PM21934:
    • Added new messages
    • Added new option to print a Module Entry Point (MEPL)
    • Added the parameter DISPLAY after the REPORT_TYPE parameter in the Global parameters syntax diagram
    • Corrected the description of the ADD attribute for the Utility Monitor options
    • Removed a sentence in the Introduction to the batch interface topic

    1. New messages
    • Added DSNUTILB intercept message ABPU5907E for utility jobs that abend with SOC4 error message if SYSPRINT is absent.
    • Added DSNUTILB intercept messages ABPU5020E and ABPU5021E for the situation where STC does not fail initialization when encountering invalid OPTIONS parameters specified for ABPBMAIN_CANCEL_MEMBER or ABPBMAIN_GLOBAL_MEMBER.
    • Added batch interface messages ABPB6800I and ABPB6801I

    ABPU5907E SYSPRINT DD is missing or unusable.

    Explanation: SYSPRINT DD is missing, or is allocated to DUMMY or NULLFILE.

    User Response: Supply a valid SYSPRINT DD statement in the JCL.

    ABPU5020E Cancel syntax member cancel_syntax_member was not found.

    Explanation: The ABPBMAIN cancel syntax member specified in the ABPBMAIN_CANCEL_MEMBER of the OPTIONS was not found in the parameters library.

    User Response: Make sure that the required member exists in the parameters library and is correctly specified in the options member.


    ABPU5021E Global syntax member global_syntax_member was not found.

    Explanation: The ABPBMAIN global syntax member specified in the ABPBMAIN_GLOBAL_MEMBER of the OPTIONS was not found in the parameters library.

    User Response: Make sure that the required member exists in the parameters library and is correctly specified in the options member.

    ABPB6800I MODULE LEVEL DATE TIME EPA RREPA CC F1 F2 F3 SEQ

    Explanation: This message displays the fields in the Module Entry Point List (MEPL) control block.

    User Response: None required.


    ABPB6801I
    module_name maintenance_level
    assembly_date assembly_time
    entry_point_address rr_entry_point_address
    component_code flag_byte_1 flag_byte_2
    flag_byte_3 sequence_number

    Explanation: This message displays the data in the fields of the Module Entry Point List (MEPL) control block.

    User response: None required.

    2. Add new option to print a Module Entry Point (MEPL)
    In Chapter 16 Canceling threads by using the batch interface, section “Global parameters”, under subsection “Descriptions of global parameters”, added the following DISPLAY (MEPL) parameter:

    DISPLAY (MEPL)
    (Optional parameter) Enables the user to print a report of all DB2 Utilities Enhancement Tool modules that are allocated to the started task whose ABPID is specified in the parameter ABPID. For each module, the list shows the module maintenance level, the date and time when the module was built, and APAR level applied to each module for diagnostic use. Usually, this diagnostic information is requested by customer support.

    3. Add the parameter DISPLAY after the REPORT_TYPE parameter in the Global parameters syntax diagram
    In Chapter 16 Canceling threads by using the batch interface, section “Global parameters”, under subsection “Syntax diagram for the global parameters”, added the parameter DISPLAY after the REPORT_TYPE parameter, as follows:

    DB2 Utilities Enhancement Tool global parameters

    >>-+----------------------------------+--DB2SSID----(ssid)------>
          |       (1)                        |                        
          '-ABPID------(product_instance_id)-'                        

    >--+----------------------------------+------------------------->
          |           .- + --------------.   |  
          '-ESCAPE--(-+-single_character-+-)-'  

    >--+-----------------------------------+------------------------>
          |           (2)    .-EXECUTE----.   |  
          '-EXEC_TYPE------(-+-SIMULATE---+-)-'  
                          '-CHECKPARMS-'      

    >--+-----------------------------------------------------------------+-->
          |               .-CONTINUE------------------------------------.   |  
          '-ON_FAILURE--(-+-TERMINATE--+------------------------------+-+-)-'  
                                     |                      .-YES-. |        
                                     '-RESET_OBJECT_STATUS--+-NO--+-'        

    >--+----------------------------------+------------------------->
          |             (3)    .-SUMMARY-.   |  
          '-REPORT_TYPE------(-+-DETAIL--+-)-'  

    >--+-----------------------+------------------------------------>
          '-DISPLAY--(---MEPL---)-'  

    >--+------------------------------------------------+----------><
          |                        .- 0 ---------------.   |  
          '-THREAD_QUIESCE_TIME--(-+-number_of_seconds-+-)-'  

    Notes:
    1. The ABPID parameter is required for all thread-blocker actions.
    2. The EXEC_TYPE parameter must be set to EXECUTE for all thread-blocker actions. If you specify SIMULATE instead, the job will run in simulation mode but the output will not include thread-blocker activities.
    3. The REPORT_TYPE parameter is not supported for any thread-blocker actions.


    4. Correct the description of the ADD attribute for the Utility Monitor options

    In Chapter 8 The DSNUTILB intercept Utility Monitor, section “How the Utility Monitor works” and section “Utility Monitor option descriptions”, change the description of the ADD attribute to:

    ADD

      A text string is added to the utility statement if the specified string is not found in the utility statement syntax. The text string is appended to the end of the utility statement. Note that this action occurs for each qualifying utility statement. If multiple utility statements were specified, as in the example below, the ADDed text would be appended to each utility statement in the SYSIN.


      //SYSIN DD *
      REBUILD INDEX ( <IXcreator>.<IXname1> ) ==>added text
      REBUILD INDEX ( <IXcreator>.<IXname2> ) ==>added text
      REBUILD INDEX ( <IXcreator>.<IXname3> ) ==>added text
       /*

    5. Remove a sentence in the introduction to the batch interface chapter.
    In Chapter 15 Introduction to the batch interface, removed the following introductory sentence:

    Learn about key thread blocking and cancellation features of the IBM DB2 Utilities Enhancement Tool for z/OS batch interface.




    Update 2
    Date of change: December 9, 2010
    Topic: Multiple
    Change description: Several documentation changes were made for APAR PM22762 (Parsing failure occurs when encountering CREATOR.TABLE_NAME where CREATOR is greater than 8 bytes):

    1. Chapter 6, Chapter 14, and Chapter 16
    Changed all occurrences of "A creator ID can be up to eight characters long" to "A creator name can be up to 128 characters long" in the following places:
    • Chapter 6. "The DSNUTILB intercept policy", Table 10. Utility object <RULE> attribute
    • Chapter 14. "Canceling threads by using the ISPF interface", section “Filtering threads”, and in
    • Chapter 16. "Canceling threads by using the batch interface", section “Descriptions of cancel parameters”

    2. Chapter 14
    In Chapter 14. "Canceling threads by using the ISPF interface" in Figure 20. "Specify Thread Filter Criteria panel", modified all CREATOR fields to allow for 128 characters.




    Update 1
    Date of change: November 1, 2010
    Topic: Messages
    Change description: For APAR PM18555, which provides the ability to use IBM DB2 Sort as an alternative sort method in ABPUMAIN, five DSNUTILB intercept messages were added.

    ABPU5908I IBM DB2 SORT found and will be used

    Explanation:
    IBM DB2 SORT was found and will be used for PRESORT on LOAD.

    User Response:
    None.


    ABPU5909W IBM DB2 SORT cannot be utilized. Not all modules found

    Explanation
    : Not all modules for IBM DB2 SORT were found. Sorts will be performed by the default sort.

    User Response
    : Ensure that IBM DB2 SORT has been installed correctly.


    ABPU5910I DB2 Sort Program=progname returned non-zero return code, RC=return_code

    Explanation:
    An internal error occurred.

    User Response
    : Contact IBM Software Support. Provide the support representative with the complete text of this message. Sorts will be performed by the default sort.


    ABPU5911I DB2 Sort Program=progname abended. Default sort will be used

    Explanation:
    A DB2 Sort program abended.

    User Response:
    Contact IBM Software Support. Provide the support representative with the complete text of this message. Sorts will be performed by the default sort.


    ABPU5912I ESTAE SDUMPX call RC=return_code, RS=reason_code

    Explanation:
    During ESTAE processing, a call to the z/OS SDUMPX facility returned the displayed return code and reason code.

    User Response:
    If RC=08, review the reason code in the appropriate SDUMPX documentation. Then make any changes to Dump Services that are needed to obtain proper diagnostic dumps. If you need assistance, contact IBM Software Support.
  • Related information

    DB2 Utilities Enhancement Tool

    Publication number

    SC19-1224-03

    Original publication date

    2009/12/20

    Rate this page:

    (0 users)Average rating

    Add comments

    Document information


    More support for:

    DB2 Tools for z/OS
    DB2 Utilities Enhancement Tool

    Software version:

    2.1.0

    Operating system(s):

    z/OS

    Reference #:

    7017868

    Modified date:

    2011-03-31

    Translate my page

    Machine Translation

    Content navigation