IBM Support

II14241: FCTC DEVICES NOT ONLINE (FOR A PREVIOUSLY KNOWN WORKING FCTC CONNECTION AFTER IPL)

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • INTRAN

Error description

  • FCTC devices not online  (for a previously known working FCTC
    connection after IPL)
    This situation could be due to:
    A) Not having Images and Channels involved in the FCTC
    connections online.
                                            OR
    B) The inability of the channel to complete a successful Port
    Log In.
    For A:
    
    1. Verify the state of the Images and Channels involved in the
       FCTC connection:
       -A defined Image to that FCTC path is activated to both
        sides of the FICON CTC.
       -The CHPID must be online and operating at the
        Support Element to those Images (Channel Workplace).
    Not having any one of the above conditions prior to the IPL
    could result in not having a FCTC device online at IPL time.
    NOTE:
    Not having the Images activated on the other side of the CTC
    could be due to some disruptive action on that system or it
    simply hasn't been activated yet.
    Recovery Action:
    Activate the the appropriate image and or bring the appropriate
    channel online.
    After having done so vary the FICON CTC devices online.
    V xxxx,online
    For B:
    FICON CTC Devices will appear offline after IPL yet all
    appropriate areas of the Fibre Channel Fabric are online and
    activated.
    
    If channel can not complete a  Port LOG In (PLOGI) to the other
    side of the CTC the devices will remain offline.  There could be
    some condition within the Fibre Channel Fabric that might be
    stopping the PLOGI from completing.
    Use the HMC/SE to get more information about the Port Log In
    condition.
    1) Establish a CPC/SE Session (Single Object Operations).
    2) Select the appropriate CPC.
    3) Select Images.
    4) Highlight the image, right mouse click, select chpids
    5) Highlight the appropriate channel.
    6) Toggle to the CHPID OPERATIONS task and select Channel
       problem Determination.
    7) Select ANALYZE SERIAL LINK STATUS.
    8) Look at the Status of the LINK if it is anything OTHER than
       INIT Complete report this to the
       Support center.
    
    Recovery actions for anything OTHER than INIT Complete:
    Contact your IBM Hardware Support personnel for assistance.
    There are Hardware tips available to the support center to
    assist you  in recovering the FCTC devices and or assist your
    IBM CE with data collection Procedures for potential problems -
    H183685.
    9) If the status of the link IS: LINK COMPELETE attempt to vary
       the devices online again.
       Report this problem to the hardware support center as well
       as the software support center.
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II14241

  • Reported component name

    V2 LIB INFO ITE

  • Reported component ID

    INFOV2LIB

  • Reported release

    001

  • Status

    INTRAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2006-12-01

  • Closed date

  • Last modified date

    2006-12-01

  • 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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"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":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
01 December 2006