PM91639: LOAD/UNLOAD FORMAT INTERNAL MISMATCH CAN CAUSE AND STORAGE OVERLAY, MAY CAUSE DB2 TO CRASH

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • LOAD/UNLOAD FORMAT INTERNAL mismatch can cause a storage
    overlay, may cause DB2 to crash. Whenever LOAD specifications
    are not done correctly there is a chance that Load can overlay
    storage and bad things can happen.  But it seems more the case
    with FORMAT INTERNAL. With this APAR, LOAD will check if the
    FORMAT matchs the input data and end gracefully with an error
    message if not.
    

Local fix

  • be sure Unload FORMAT matches LOAD FORMAT
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS and DB2  *
    *                 11 for z/OS utility users of LOAD FORMAT     *
    *                 INTERNAL                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: LOAD FORMAT INTERNAL using an input     *
    *                      data set, SYSREC, that is not in        *
    *                      internal format may cause DB2 to crash  *
    ****************************************************************
    * RECOMMENDATION: Apply corrective PTF when available          *
    ****************************************************************
    LOAD FORMAT INTERNAL using an input data set, SYSREC, that
    contained data that was not in internal format caused DB2 to
    crash.  FORMAT INTERNAL is a performance option that bypasses
    all data validity checks to improve performance and incorrect
    usage may result in numerous types of errors if the procedures
    outlined in the Utility Guide and Reference are not followed.
    To minimize problems caused by usage error, LOAD FORMAT INTERNAL
    will be modified to validate that the actual length of the
    internal format record equals the length specified in the
    internal format record header.
    

Problem conclusion

  • LOAD FORMAT INTERNAL has been modified to help validate that the
    input data is in fact in internal format by validating the
    actual record length against the length specified in the record
    header.
    
    Please note no other validity checking of the data will be done
    so users must follow the procedures described in the Utility
    Guide and Reference when using the FORMAT INTERNAL option.
    
    With this APAR when using the FORMAT INTERNAL option and the
    actual record length does not match the length specified in the
    record header message MSGDSNU334I will be issued with reason
    code 34 with field-name 'RECORD HEADER LENGTH FOR FORMAT
    INTERNAL' and the job will abend with ABEND04E RC00E40323.
    
    Example message text for DSNU334I with reason code 34:
    DSNU334I -INPUT FIELD 'RECORD HEADER LENGTH FOR FORMAT INTERNAL'
    INVALID FOR 'table.name' ERROR CODE '34'
    
    The Messages manual has been changed to add the new reason code
    34 for message DSNU334I:
    
    DSNU334I csect-name INPUT FIELD field-name INVALID FOR
    table-name, ERROR CODE error-code
    
    Explanation: The LOAD utility found incorrect input data.
    
    csect-name:
    The name of the control section that issued the message.
    
    field-name:
    The name of the field for which incorrect data was provided.
    
    table-name:
    The name of the table.
    
    error-code:
    Description of the problem. Possible error codes are:
    01 Input numeric value is out of the range for the table column.
    02 Input numeric field contains invalid numeric data.
    03 An error occurred when converting input numeric data to
    floating-point data.
    04 Input packed decimal data is in error.
    05 Input is too long for a date column.
    06 Input is too short for a date column.
    07 Input is too long for a time column.
    08 Input is too short for a time column.
    09 Input is too long for a timestamp column.
    10 Input is too short for a timestamp column.
    11 Input character field is too long for the table column.
    12 Input variable character field is too long for the table
    column.
    13 Input is out of range for the date/time column.
    14 Input is invalid for the date/time column.
    15 Input length is incorrect for numeric column.
    16 Input contains a blank character.
    17 Input is too long for a graphic column.
    18 Input is invalid for a graphic column.
    19 Input is too long for the table column after a required CCSID
    conversion.
    20 Input contained an invalid code point for a required CCSID
    conversion.
    21 Input does not conform to the rules for valid data for a
    required CCSID conversion.
    22 Input causes an error during CCSID conversion. An example
    of this type of error would be an error
    in a user exit routine.
    23 Input is invalid for a ROWID column.
    24 Input contained a code point that when translated from the
    source resulted in a substitution character being placed in
    the target string.
    This condition can occur when the NOSUBS keyword was specified
    and no discard data set was specified.
    25 The range of values for an identity column is exhausted.
    26 A null value has been supplied for a not null column.
    27 Input is invalid for a security label column.
    28 Input is a valid security label, but the SECLABEL and the
    user's does not have the authority to load this SECLABEL.
    29 Decimal floating point conversion error.
    31 XML is not well formed.
    >>34 The FORMAT INTERNAL record header length is invalid. <<
    
    System action: Further utility processing is terminated.
    User response: Correct the input data and resubmit the job.
    Make sure that the field specification on the LOAD
    statement is consistent with the table definition and the
    input data.
    Correcting this error might mean changing:
    v The table definition
    v The LOAD statement
    v The input data
    
    Severity: 8 (error)
    
    Related reference:
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PM91639

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-06-23

  • Closed date

    2013-09-24

  • Last modified date

    2013-11-04

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

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

    UK97707 UK97768 UK97769

Modules/Macros

  • DSNURWBF
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK97707

       UP13/10/15 P F310 ½

  • RB10 PSY UK97768

       UP13/10/15 P F310 ½

  • R910 PSY UK97769

       UP13/10/15 P F310 ½

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.



Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 for z/OS

Software version:

A10

Reference #:

PM91639

Modified date:

2013-11-04

Translate my page

Machine Translation

Content navigation