Logon problems

This information provides documentation requirements and diagnosis procedures for logon problems.

The recommended documentation is:

VTAM® full buffer contents trace.
To see the data in the buffer contents trace, set CONFTXT=NO in the TSOKEY00 member of SYS1.PARMLIB before starting TSO/VTAM.
VTAM internal trace with MODE=EXT and OPTION=(API, MSG, NRM, PIU, SSCP, PSS).
The VTAM internal trace may not be required. Review the diagnosis procedure for your problem to see whether it is required.

Note: API, MSG, NRM, PIU, and SSCP are always running internally.

Did your first logon using USS commands fail?
If so, continue with the next step.

Otherwise, go to step 5.
Under the information about unformatted system services (USS) tables in the z/OS Communications Server: SNA Resource Definition Reference, review the process for setting up the USS table and using USS commands.Check for the following errors:
- Is your logon command syntax incorrect?
  If so, try to log on using the correct command syntax.
  
  Otherwise, continue with the next step.
- Is the logmode name incorrect?
  If the logmode name is specified incorrectly, or if a default logmode entry that is inappropriate for the device type is used, you will get USSMSG7. Look up the accompanying sense code in z/OS Communications Server: IP and SNA Codes and correct the logmode name.
Can you log on to TSO without using USS commands?
If you cannot log on at all, go to step 4.

If you can log on, start the VTAM buffer contents trace and log on again. Look at the trace output to see what session parameters are contained in the BIND, and compare those parameters to the ones in your logmode table.

If the session parameters in your logmode table are incorrect, make the necessary corrections. Also, make sure that the DLOGMOD operand specifies the correct logmode table entry. (For more information about defining TSO/VTAM session parameters, see z/OS Communications Server: SNA Network Implementation Guide.)

If you still cannot identify the problem, go to Reporting the problem to IBM.
Are you unable to log on at all?
- If this is your first logon attempt from the device as well as your first logon attempt using USS commands, go to step 5.
- If this is not your first logon attempt from the device, go to Reporting the problem to IBM.
Did your first logon from a particular device fail?
If so, continue with the next step.

Otherwise, go to step 7.
Check for an error in the logmode table, or the MODEENT macro.
(These are described in z/OS Communications Server: SNA Resource Definition Reference.)
1. If you receive message IKT029I with return code X'210000' or X'220000', the BIND has been rejected. The following steps can help you find the portion of the BIND that is not valid:
  1. Locate the BINFM in the BIND. BINFM must be X'02' or X'03'. (For more information on coding the BIND, see z/OS Communications Server: SNA Programming.)
  2. If a PSERVIC is coded, see z/OS Communications Server: SNA Resource Definition Reference to make sure that all fields are coded correctly.
2. Check to see whether the DLOGMOD name on the terminal definition statement is a valid logmode table entry.
  If it does not match an entry in the logmode table, the first entry in the logmode table is used as the default. The parameters on the default logmode table entry may not be appropriate for your device type, and as a result, the wrong BIND image may be passed to the logon exit and a CLSDST PASS failure may occur.
  
  Note: You can see this failure in the VTAM internal trace using the API option. For more information on the VTAM internal trace, see z/OS Communications Server: SNA Diagnosis Vol 2, FFST Dumps and the VIT.
3. Check the logmode table entry to see whether the parameters are specified correctly for your device type.
  If not, the wrong BIND image may be passed to the logon exit and a CLSDST PASS failure may occur.
4. Check to see whether the MODEENT macro is defined correctly.
  If it is not, the terminal may reject the BIND, or the terminal may indicate to the logon exit that the terminal is not supported by TSO/VTAM.
5. If you have not identified the problem, and if users can log on to TSO from other terminals, start the VTAM buffer contents trace and check the BIND.
6. If logon attempts fail for all terminals, or if the BIND in the buffer contents trace is what you expected, run the VTAM internal trace with options API, PIU, SSCP, and MSG.
7. If you still have not resolved the problem, go to Reporting the problem to IBM.
Did previous logons succeed, but now you cannot log on?
If so, continue with the next step.
Did you get message IKJ608I?
If not, go to step 12.

If so, continue with the next step.
Is message IKJ608I followed by messages IST804I, IST400I, and IST805I?
If so, the CLSDST PASS or OPEN ACB may have failed. Continue with the next step.
Is this a cross-domain logon?
If not, go to step 11.

If this is a cross-domain logon, you may have a VTAM definition problem.For more information on defining TSO/VTAM and logical units that must access TSO/VTAM in a cross-domain environment, see z/OS Communications Server: SNA Network Implementation Guide.
Is there a TSO/VTAM APPLID that is not valid? (For more information on defining APPLIDs, see z/OS Communications Server: SNA Network Implementation Guide .)
If so, correct the APPLID. After you have corrected the APPLID, you must deactivate the application and reactivate it to cause VTAM to reload the correct APPLID. This should fix the problem.

If not, continue with step 12.
Did you get message IKT111I?
If not, go to step 13.

If so, check the message text to determine the reason for the logon failure. See z/OS Communications Server: SNA Messages for additional diagnostic information for particular messages.

Is an ABEND0AB with return code X'0105' or X'0203' associated with the logon attempt?

If not, go to step 14.

If so, check the LOGREC entry for the additional information shown in Table 1.

Table 1. ABEND0AB information in LOGREC
Reason code	Register	Contents
X'0105'	6	RPLRTNCD, RPLFDB2, and RPLDAF
	7	RPLFDBK2 (the word of sense)
X'0201'	8	ACBERFLG (for OPEN ACB failure)
	9, 10	TVWA ACB Name (TSOnnnn)
X'0202'	8	ACBERFLG (for OPEN ACB failure)
	9, 10	TVWA ACB Name (TSOnnnn)
X'0203'	5	ACBERFLG (for CLOSE ACB failure)
	6, 7	TVWA ACB Name (TSOnnnn)

Then go to Reporting the problem to IBM.

If none of the previous situations apply, start the VTAM buffer contents trace and the VTAM internal trace, and trace the logon attempt. Then go to Reporting the problem to IBM.