z/OS TSO/E Customization
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Using TSO/E

z/OS TSO/E Customization
SA32-0976-00

The following steps must be performed before users can use TSO/E:
  1. Initialize time sharing using the VTAM® access method.

    Before terminal users can log on to TSO/E, VTAM must be active on the system. For how to initialize VTAM, see Defining and customizing TSO/VTAM and TSO/TCAM time sharing

  2. To define users to the system, you can use either the user-attribute data set (SYS1.UADS) or the RACF® data base, as described in Maintaining the UADS, RACF data base, and broadcast data set.
    If your installation has not installed TSO/E before and you intend to use SYS1.UADS rather than the RACF data base, make the following changes to the UADS:
    • Use the UADSREFM program to reformat SYS1.UADS, expanding it to 172 bytes for each user ID.
    • Optionally, use the ADD or CHANGE subcommand of the TSO/E ACCOUNT command to assign the RECOVER user attribute. Users must be authorized by the RECOVER attribute to use TSO/E EDIT command recovery. Also, assign installation defaults for the following user attributes:
      HOLD
      to assign a default for output class
      JOBCLASS
      to assign a default for job class
      MSGCLASS
      to assign a default for message class
      SYSOUT
      to assign a default for SYSOUT class

    You can convert some or all of the user IDs from SYS1.UADS to the RACF data base using the RACONVRT command. After UADS has been converted, you can use RACF commands to maintain the user information in the RACF data base. For more information about converting UADS, see Using the RACF data base to maintain TSO/E users.

  3. If you have not installed TSO/E before and you are not using individual user logs, you must reformat the broadcast data set using the SYNC command to allow the new broadcast data set to be used. Reformatting with the SYNC command also reduces channel, control unit, and device busy time when a new record is written to the broadcast data set. For more information about the SYNC command, see . For more information about reformatting the broadcast data set, see Working with the UADS and broadcast data set.

    To reduce contention for the broadcast data set, you can use individual user logs to store messages (mail) for users instead of using the broadcast data set. To use individual user logs, update the SEND command defaults in SYS1.PARMLIB member IKJTSOxx, as described in Customizing how users send and retrieve messages.

  4. If you have existing versions of CSECTs INMXPARM, IKJEFTE2, IKJEFTE8, IKJEFTNS, and IKJEFTAP, you can reinstall the CSECTs, or you can use SYS1.PARMLIB member IKJTSOxx to perform the functions of those CSECTs.

    If you have no existing versions of the CSECTs, use IKJTSOxx instead. If you decide to use the CSECTs, you must modify them as described.

    For more information on CSECTs and IKJTSOXX, see Specifying authorized commands/programs, and commands not supported in the background and on INMXPARM see Setting up the TRANSMIT and RECEIVE environment.

  5. New RACF programs need to get control authorized. If you have the existing version of CSECT IKJEFTE8, you can reinstall it, or you can use SYS1.PARMLIB member IKJTSOxx to perform the function of IKJEFTE8.

    If you have no existing version of CLIST IKJEFTE8, use IKJTSOxx instead. If you decide to use IKJEFTE8, you must modify it as described.

  6. IPL, specifying "clpa" to refresh the LPA.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014