IBM Support

PI11470: GETTING UNRECOVERABLE ERRORS SWAPPING SSIDS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • While on a DB2 test platform (DB2 V10 NFM) we try to use the
    location name of a DB2 V8 CM system.
    
    We expect to get a -805 (as a bind has not been done on V8 to
    match what V10 is calling on the remote system). This is
    understandable and reasonable. What is not reasonable is that
    FM, once it hits this -805 situation, cannot recover even when
    the LOCATION name is changed back to the local subsystem.
    
    The only way to recover is to exit completely out of FM DB2 and
    go back in.
    

Local fix

  • Exit FM completely and restart with desired system.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of File Manager DB2 component.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: An SQLCODE-805 at a remote DB2 system   *
    *                      can prevent subsequent processing.      *
    ****************************************************************
    * RECOMMENDATION: Apply the provided PTF.                      *
    ****************************************************************
    An SQLCODE-805 indicates an installation or configuration
    problem.  In the problem scenario there are two DB2 systems:
    DSNA at DB2 V10 NFM and DSNB at DB2 V10 CM9.  Maintenance
    requiring a rebind of the FM/DB2 packages is applied to DSNA,
    but not DSNB.  When an attempt is made to access DSNB remotely
    from DSNA, by specifying a location value, an SQLCODE-805
    occurs.  Clearing the location value erroneously results in
    subsequent SQLCODE-805 mesages.  The problem arises because the
    connection to DSNB is not reset after the initial SQLCODE-805.
    

Problem conclusion

  • File Manager DB2 component has been updated to correct the
    problem.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI11470

  • Reported component name

    FILE MANAGER Z/

  • Reported component ID

    5655Q1200

  • Reported release

    D12

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-02-11

  • Closed date

    2014-04-13

  • Last modified date

    2014-05-02

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

    PM98566

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

Modules/Macros

  • FMN2LVL
    

Fix information

  • Fixed component name

    FILE MANAGER Z/

  • Fixed component ID

    5655Q1200

Applicable component levels

  • RD12 PSY UI17000

       UP14/04/19 P F404

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSXJAV","label":"File Manager for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"D12","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
02 May 2014