Troubleshooting
Problem
IST1139I or IST380I ACTLINK for LINEname failed - sense: 081C0000 After configuring OSA-2 for SNA support and activating the XCA major node, the error message is received. OSA is currently working for TCP/IP on port 0 device F00/F01. The configuration attempted to activate SNA on the same port as device F0A.
Cause
This error usually indicates a mismatch in some configuration parameter.
Resolving The Problem
There are several areas that need to be checked:
1) Verify that OSA is loaded with SNA code.
2) Verify that the ADAPNO and SAPADDR on the XCA PORT statement for Enterprise
Extender connections in the VTAM definitions (see SNA Resource Definitions Reference manual) match the OSA configuration.
3) The failure could be a dynamic allocation failure. Look for an IST1386I message. Is DFSMS introducing a cause for the allocation failure, that is, a wrong device type?
A VTAM Internal Trace (VIT) with OPT=(LCS,CIO,PIU,PSS,MSG) will help to isolate the problem if you fail in finding a configuration error.
If the trace shows a RC x'0001' to the Start_System request, this indicates the SNA image is not loaded.
To verify the SNA image is loaded:
1. Start IOACMD.
2. Specify QUERY command.
3. Look at the query dataset it creates, search for Flash Image Level. If this is not filled in or it says incomplete, the image is not loaded.
To install the SNA image onto the OSA adapter:
1. Start IOACMD.
2. Specify the CONFIG_OSA command.
This command will ask you what configuration mode you would like. Specify TCPIP & SNA. It will also ask for the dataset name of your OAT table.
3. Once the command completes successfully, configure the CHPID OFF for all of the LPARS that it is assigned as a resource.
4. Next configure the CHPID back ONLINE.
5. Start IOACMD again.
6. Specify QUERY command.
7. Look at the query dataset it creates, search for Flash Image Level. If this is not filled in or it says incomplete, the image is not loaded. You will have to call for OSA support.
The CONFIG_OSA command will download the SNA (or ATM) image, and also download the OAT table. Downloading a new OAT table is disruptive because you have to configure the CHPID OFF from all LPARs. What you can do is an ACTIVATE/NO INSTALL which will update the pointers to the correct files but will not download anything until you issue the MVS command to install it.
Insure that the channel device is not being monitored by DFSMS.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21166465