IBM Support

II14879: IOSHM0501I RESPONSE FROM API FOR FC = 13 RC = 12 RSN = 3 & IOSHM0504I FUNCTION FAILED ON PAIR RC = 12 RSN = 3, STEP = 1300

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • Attempting to Load a Hyper Swap configuration from CSM
    after devices have been added or modified.
    
    In this case system was using JES3.
    HyperSwap disabled due to One or more members unable to verify
    PPRC secondary device connectivity
    D HS,STATUS shows:
    .
    IOSHM0303I HyperSwap Status
    
    Number of configurations: 1
    Replication Session: PLEXA_______H1H2
    HyperSwap disabled:
    One or more members unable to verify PPRC secondary device
    connectivity
    SSS: Member unable to verify PPRC secondary device connectivity
    YYY:
    

Local fix

  • SYSLOG Shows:
    
    IOSHM0501I Response from API for FC = 13, RC = 12, Rsn = 3
    IOSHM0504I Function Code failed on device pair = 01000,05000 RC
    = 12,  Rsn = 3, Step = 1300
    IOSHM0504I Function Code failed on device pair = 01001,05001 RC
    = 12, Rsn = 3, Step  = 1300
    .
    etc etc for several device pairs until...
    *IOSHM0803E HYPERSWAP DISABLED
    IOSHM0200I HyperSwap Configuration LoadTest complete
    IOSHM0501I Response from API for FC = 15, RC = 12, Rsn = 3
    .
    Solution - both H1 and H2 devices must be in the same Esoteric.
    Modify the EDT in the Activate IODF to include both primary and
    secondary
    devices and ACTIVATE a new IODF.
    
    The activate can be performed as a SOFTWARE ONLY ACTIVATE.
    As per Redbook:
    Best Practices for IBM DS8000 and IBM z/OS HyperSwap with IBM
    Copy Services Manager
    .
    https://www.redbooks.ibm.com/redbooks/pdfs/sg248431.pdf
    .
    6.2.11  Allocation and esoteric names
    
    Esoteric definitions such as SYSDA must specify both primary
    and secondary devices for allocations to succeed, regardless of
    which set of disks is currently considered primary.
    

Problem summary

Problem conclusion

Temporary fix

Comments

  •  Info APAR
    

APAR Information

  • APAR number

    II14879

  • Reported component name

    V2 LIB INFO ITE

  • Reported component ID

    INFOV2LIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-03-27

  • Closed date

    2025-03-27

  • Last modified date

    2025-03-31

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"001","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
31 March 2025