IBM Support

OA47290: ++HOLD FOR DOC IS INCOMPLETE FOR OA46090 PTFS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ++HOLD for REASON(DOC) against PTFs for OA46090 do not include
    what the documentation changes are.
    The documentation changes are as follows:
    DFSMS Using Data Sets is updated with the following changes:
    Under Chapter 16. Coding VSAM User-Written Exit Routines.
    Under EXCEPTIONEXIT Exit Routine, Programming Considerations
    The following line is added as the first line of this section
    Users of this exit must have READ authority to the resource
    IDA.VSAMEXIT.xxxxxxxx in the FACILITY class where xxxxxxxx is
    the EXITNAME parameter value of EXCEPTIONEXIT.
    
    Under SYNAD Exit Routine to Analyze Physical Errors, Programming
    Considerations
    The following line is added as the first line of this section
    Users of this exit must have READ authority to the resource
    IDA.VSAMEXIT.xxxxxxxx in the FACILITY class where xxxxxxxx is
    the EXITNAME parameter value of SYNAD parameter.
    
    The book "MVS System Messages Volume 7 (IEB-IEE)" is updated
    with the following changes:
    Under Chapter 2 IEC messages
    Under IEC161I (return code 040)
    Under Explanation, add the following to the end
    Add a table with the title "SFI Reason Codes for Code 040"
    Two columns of the table with title "SFI Dec Value" and
    "Description"
    Table 4. VSAM OPEN SFI Reason Codes for Return Code 040
    SFI Decimal Value   Description
    001                 Named exit specified in the EXCEPTIONEXIT
                          keyword is not loaded due to a SAF return
                        code 4 (no decision).
    002                 Named exit specified in the SYNAD keyword
                        is not loaded due to a SAF return code 4
                        (no decision).
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: VSAM users specifying any named exit under   *
    *                 the EXCEPTIONEXIT keyword of the IDCAMS      *
    *                 DEFINE function or SYNAD= sub-parameter      *
    *                 of the AMP= keyword on the DD card in        *
    *                 the JCL statement.                           *
    ****************************************************************
    * PROBLEM DESCRIPTION: The named exit program can be invoked   *
    *                      as a VSAM physical I/O error exit that  *
    *                      is not intended to be invoked, allowing *
    *                      an unauthorized program to run as a     *
    *                      VSAM physical I/O error exit.           *
    ****************************************************************
    * RECOMMENDATION: Review all usages of these types of exits    *
    *                 for obsolescence and security, then set      *
    *                 up read authority appropriately.             *
    *                                                              *
    *                 The CATSRCHI program can be used to find     *
    *                 data sets that have an EXCEPTIONEXIT         *
    *                 specified. Information about this tool       *
    *                 can be found in APAR II14316.                *
    *                                                              *
    *                 For example:                                 *
    *                 CATSRCHI ** CAT(catalog name) TYPES(C)       *
    *                   FIELDNAMES(EXCPEXIT)                       *
    *                                                              *
    *                 From the report generated, any data set      *
    *                 that does not come back with:                *
    *                   EXCPEXIT = x'FFFFFFFFFFFFFFFF'             *
    *                 would need to be set up with the necessary   *
    *                 facility class.                              *
    ****************************************************************
    The named exit can be any program that is found in an
    APF-authorized library in the system LNKLST concatenation or
    from LPA. This allows a program of a user's choosing to be
    invoked as a VSAM physical I/O error exit that is not
    intended to be invoked. This can allow an unauthorized program
    to run as VSAM physical I/O error exit from an APF-authorized
    environment program such as IDCAMS.
    

Problem conclusion

  • For data sets that are DEFINEd with the EXCEPTIONEXIT or
    programs that specify the SYNAD parm on allocation, VSAM will
    now check at Open time for READ authority to the resource
    IDA.VSAMEXIT.xxxxxxx in the FACILITY class where xxxxxxx is
    the named exit value of the EXCEPTIONEXIT or SYNAD parameter.
    Whether the exit actually exists or not will not matter,
    the Open will fail if it gets a SAF return code of 4.
    
    Exit lists built by the program will not be affected by this
    change.
    
    "DFSMS Using Data Sets" is updated with the following changes:
    Chapter 16. Coding VSAM User-Written Exit Routines,
    under EXCEPTIONEXIT Exit Routine, Programming Considerations,
    the following line is added as the first line of this section.
    
    Users of this exit must have READ authority to the resource
    IDA.VSAMEXIT.xxxxxxxx in the FACILITY class where xxxxxxxx is
    the EXITNAME parameter value of EXCEPTIONEXIT.
    
    Under SYNAD Exit Routine to Analyze Physical Errors, Programming
    Considerations,
    the following line is added as the first line of this section:
    
    Users of this exit must have READ authority to the resource
    IDA.VSAMEXIT.xxxxxxxx in the FACILITY class where xxxxxxxx is
    the EXITNAME parameter value of SYNAD parameter.
    
    The book "MVS System Messages Volume 7 (IEB-IEE)" is updated
    with the following changes:
    
    Under Chapter 2 IEC messages
    Under IEC161I (return code 040)
    Under Explanation, the following table is added to the end.
    
    Table 4. VSAM OPEN SFI Reason Codes for Return Code 040
    SFI Decimal Value   Description
    001                 Named exit specified in the EXCEPTIONEXIT
                        keyword is not loaded due to a SAF return
                        code 4 (no decision).
    002                 Named exit specified in the SYNAD keyword
                        is not loaded due to a SAF return code 4
                        (no decision).
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA47290

  • Reported component name

    DFSMS VSAM

  • Reported component ID

    5695DF106

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-03-11

  • Closed date

    2015-06-09

  • Last modified date

    2015-07-01

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

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

    UA77645 UA77646 UA77650

Modules/Macros

  • IDA0192A
    

Publications Referenced
SC23685500SA22763721   

Fix information

  • Fixed component name

    DFSMS VSAM

  • Fixed component ID

    5695DF106

Applicable component levels

  • RC10 PSY UA77645

       UP15/06/25 P F506

  • RD10 PSY UA77650

       UP15/06/25 P F506

  • R210 PSY UA77646

       UP15/06/25 P F506

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":"210","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 July 2015