Analysis

Table 1 shows some of the common SNALINK LU6.2 address space startup problems.

Table 1. Common SNALINK LU6.2 address space startup problems
If this is displayed. . .	Then this might have occurred . . .	Resolution
The message `Errors Detected - Address Space will Terminate` has been displayed on the MVS™ system console with no other error messages.	This error message indicates that an error has occurred with the SNALINK LU6.2 configuration data set	Check the SNALINK LU6.2 SYSPRINT output for messages that tell what kind of syntax error might have occurred. If a syntax error has occurred in the configuration data set, correct it and restart the SNALINK LU6.2 address space. See the z/OS Communications Server: IP Configuration Reference for details about the SNALINK LU6.2 configuration data set statement syntax.
The message `Error in open of LU62CFG - no data will be read` has been displayed on the MVS system console.	The SNALINK LU6.2 address space cannot access a SNALINK LU6.2 configuration data set. The LU62CFG ddname might have been omitted from the SNALINK LU6.2 cataloged procedure.	Check the SNALINK LU6.2 cataloged procedure. Ensure that the LU62CFG ddname is assigned a valid SNALINK LU6.2 configuration data set. See the z/OS Communications Server: IP Configuration Reference for an example of a SNALINK LU6.2 cataloged procedure.
The message `Address Space Already Active - this Address Space will Terminate` has been displayed on the MVS system console.	An address space with the same name as the SNALINK LU6.2 address space is already active.	Check to see whether the address space with the same name is no longer required before stopping it, or rename the SNALINK LU6.2 address space. Restart the SNALINK LU6.2 address space.
The messages `Error 0000005A in VTAM OPEN` and `Errors detected in VTAM Initialization - Address Space will terminate` have been displayed on the MVS system console.	The SNALINK LU6.2 address space has not been able to find the VTAM® application LU that has been defined in the VTAM statement of the SNALINK LU6.2 configuration data set.	This problem might be resolved by one or both of the following solutions: Check the status of the SNALINK LU6.2 VTAM application LU and its VTAM major node. If it is not in a CONCT state, the VTAM major node and then the VTAM application LU must be activated. See Useful VTAM operations for a detailed description of the VTAM operations that display the status of VTAM application LUs and activate them. Check the VTAM application LU specified in the VTAM statement of the SNALINK LU6.2 configuration data set. Ensure that it exists and is not duplicated within the domain in which the SNALINK LU6.2 application program resides. See z/OS Communications Server: IP Configuration Reference for details about the SNALINK LU6.2 VTAM statement syntax and the SNALINK LU6.2 VTAM application LU definition.
The messages `Error 00000024 in VTAM OPEN` and `Errors detected in VTAM Initialization - Address Space will terminate` have been displayed on the MVS system console.	VTAM security is not allowing the SNALINK LU6.2 address space to access the VTAM application LU.	Check to see whether the SNALINK LU6.2 configuration data set VTAM statement password matches the password set in the VTAM application LU definition and correct it, if necessary. See z/OS Communications Server: IP Configuration Reference for details about the SNALINK LU6.2 VTAM statement syntax and the SNALINK LU6.2 VTAM application LU definition.
The SNALINK LU6.2 address space abends with a system abend code of 300 after the `SNALINK LU6.2 address space STARTED` message.	The abend code of 300 indicates that there is insufficient storage for the SNALINK LU6.2 address space.	Either increase the value of the REGION parameter for the address space or reduce the number of buffers specified in the SNALINK LU6.2 configuration data set. See z/OS Communications Server: SNA Messages and z/OS Communications Server: IP and SNA Codes for detailed SNALU6.2 abend code descriptions.
The SNALINK LU6.2 address space abends with an abend code of S0F8 after the `Initialization Complete...` message.	The MVS S0F8 abend code indicates that an SVC was issued in SRB mode. SNALINK LU6.2 is not designed to run with VTAM in SRB mode.	The SRBEXIT option in the VTAM application LU definition has been set to “Yes.” Correct the VTAM application LU definition. See z/OS Communications Server: IP Configuration Reference for details about the SNALINK LU6.2 VTAM application LU definition.

If, after investigation, you do not find the SNALINK LU6.2 startup problem, obtain a description of all abend codes and errors written to the SYSPRINT data set and MVS system console. Most solutions to SNALINK LU6.2 address space starting problems can be solved by reading the error message or abend code descriptions.

See Finding abend and sense code documentation and Finding error message documentation for a list of references that contain SNALINK LU6.2 error message and abend code documentation.