TSO considerations

Information about the TSO-related steps that must be performed before a TSO/VTAM terminal user logs on is in z/OS TSO/E Customization and in information about initialization and tuning for your operating system. (Make sure you have updated these books with TSO/VTAM supplements before referring to them.) The following list outlines the steps and refers you to the appropriate publication:

Write LOGON cataloged procedures, and include them in SYS1.PROCLIB. See z/OS TSO/E Customization.
Construct the TSOKEY00 member or an alternate parmlib member (or an alternate data set) to set VTIOC parameters. See information about initialization and tuning for your operating system.
Include SYS1.CMDLIB in a LNKLSTxx parmlib member or in a LOGON cataloged procedure. See information about initialization and tuning for your operating system.
Create or convert the user attribute data set (UADS) and the broadcast data set. See z/OS TSO/E Customization.
Build translation tables if you want character translation. See z/OS TSO/E Customization.
Write the procedure that starts TSO/VTAM time sharing. See z/OS TSO/E Customization.
Write any command exit routines you plan to use. See z/OS TSO/E Customization.

Note: You are strongly encouraged not to VARY LOGON to TSO or code TSO as a LOGAPPL because unpredictable results can occur. For instance, if the original BIND fails, TSO messages and VTAM® messages may be repeatedly issued to the console indicating the session setup failure. In some cases this may not stop even if the VARY NOLOGON command is used to break the automatic logon relationship.