The number of logon procedures you need depends on the different types of users at your installation and the applications and data sets to which the users need to access. Using multiple logon procedures allows you to give users access to only the resources they need. For example, you can create a logon procedure that gives users access to line-mode TSO/E only, or one that also gives users access to the TSO/E Information Center Facility.

One way of minimizing the number of logon procedures at your installation is to create a few logon procedures that allocate the data sets most users require, and allocate the data sets required by individuals in a CLIST or REXX exec. Individuals can maintain their own CLISTs or REXX execs. Specify the name of the CLIST or REXX exec in the logon procedure as the first command that is executed when the user logs on.

Note, however, that when you allocate data sets from CLISTs or REXX execs, the data sets are not permanently allocated, and a user can accidentally deallocate them. To avoid the possibility of a user accidentally deallocating a data set, you can write a command processor to permanently allocate the data sets for the duration of the user's session. For more information about writing command processors, see .