Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Infrastructure 7.1 .

Activating the VTAM application major node

To initialize, the LAS requires that VTAM be available and the VTAM application major node be active.

Best practice
BMC recommends placing the LAS in your IPL procedure; however, VTAM can take a long time to initialize at IPL and might not be available by the time the LAS initializes. If VTAM is not available, the following message is issued:

BBVL385I VTAM is inactive, waiting 15 seconds for retry

The LAS automatically waits 15 seconds and checks for VTAM again. The LAS performs this waiting function 20 times before terminating.

VTAM might be available but the major node might not be active. If the major node is not active when the LAS is started, the following message is issued:

BBVL485I VTAM applid applid is inactive; vary the major node active

The LAS automatically waits 15 seconds and attempts to connect again. The LAS performs this waiting function 20 times before terminating.

Note

You can configure the VTAM application major node name to be directly activated at VTAM startup by adding the major node name to SYS1.VTAMLST member ATCCONxx.

To activate the VTAM major node for Alternate Access

  1. Verify that VTAM is available.

  2. Activate the VTAM application major node definition by issuing the following operator command:V NET,ID=BBVTASA,ACT

    This command assumes that the default VTAM application major node name, BBVTASA, was not changed during customization.


Related topic

Logging-on-and-off-a-VTAM-terminal

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*