IBM Support

II08325: VTAM CTC (OR MPC) ACTIVATION FAILS WITH MSGIST380I ACTLINK 081C003C -- RESOLVED AT VTAM 4.3 FOR AHHC (APPN) USERS.

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

  • When an ESCON CTC SCTC device used for communications by VTAM
    does not come up online during MVS system initialization at IPL,
    any attempt to issue a VTAM VARY NET,ACT,ID=Linename involving
    that device, will fail with MSGIST380I ACTLINK 081C003C.
    The definition for SNA sense 081C003C indicates that the device
    has not been made available by the operating system.
      For the VTAM activate to succeed, the device must be VARY'd
    online using the MVS VARY online command.  Once it is
    accessible, reissue the VTAM VARY NET,ACT command.
    
    CONFIGURATION explained:
      One of the two systems using the SCTC device has it attached
    via a CTC type chpid.  The other system using the SCTC device
    has it attached via a CNC type chpid.  Hereafter, these
    systems will be referred to as the CTC system and the CNC
    system, respectively.
          ______            ____            ______
         |      |   CTC    /    \   CNC    |      |
         | SYSx |<-------->|SCTC|<-------->| SYSy |
         |______|  chpid   \____/  chpid   |______|
    
      The SCTC will not come up online to the CNC system when the
    CTC system does not have a logical path established to the
    device.  This condition will occur, for example, when the
    CTC system has done an I/O Interface Reset (but NOT a System
    Reset).  An I/O Interface Reset would have occurred if a
    recovery action of F1 was selected from the SYSDEF frame and
    the system subsequently entered a disabled wait state.  One
    common circumstance under which a system will enter a disabled
    wait state is when it is partitioned out of a SYSPLEX.
      Other conditions causing the SCTC to not come up online to
    the CNC system are:
      - The processor on the CTC side is powered off.
      - The CTC and CNC chpids attach to an ESCON director
        and either port is blocked, or the path within the
        director is prohibited.
      - The CTC chpid has been configured off from the system
        (hardware) console.
    

Local fix

  • If the CTC system is in a disabled wait state, system reset
    it or IPL it before IPL'ing the CNC system.
      If the CNC system has already been IPL'd but the SCTC device
    is offline to it, the device must be MVS VARY'd online in order
    for a VTAM VARY NET to be successful.  It cannot be MVS VARY'd
    online with the CTC system still in the disabled wait state.
    Either system reset the CTC system or IPL it.
    ---------------------------------------------------------------
    ---------------------------------------------------------------
    --------  NOTE WELL!!!   THIS PROBLEM IS RESOLVED  ------------
    --------     AT VTAM 4.3 FOR AHHC (APPN) USERS.    ------------
    ---------------------------------------------------------------
    ---------------------------------------------------------------
    

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II08325

  • 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

    1994-11-16

  • Closed date

  • Last modified date

    1996-01-15

  • 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:
15 January 1996