Migrating TSO/E commands

During the installation of TSO/E, SMP/E will link edit all TSO/E commands into the data set pointed to by the CMDLIB DDDEF or the CMDLIB DD statement in the SMP/E procedure. If you have previously copied any TSO/E commands to LPALIB, and do not identify them to SMP/E, they will not be deleted or replaced by the installation.

Add SYS1.CMDLIB to LNKLSTxx in SYS1.PARMLIB if:

the TSO logon procedures do not specifically have a STEPLIB assigned to SYS1.CMDLIB, or
the commands were not copied to SYS1.LPALIB.

If you have not previously copied TSO/E commands from CMDLIB to LPALIB, skip the rest of this section.

If you have previously copied TSO/E commands from CMDLIB to LPALIB, the old copies must be deleted from LPALIB or replaced with the new version of the commands. IBM® suggests you to MLPA the commands or add CMDLIB to the LPA list rather than copy the commands to LPALIB.

Note: If you choose to add CMDLIB to the LPA list, it must also be added to the APF list.

However, if you choose to copy the commands to LPALIB, you should also identify this dual residency to SMP/E, so that future product and service installations do not cause problems.

Do not move TSO/E commands from CMDLIB; if the commands are copied to LPALIB, do not delete them from CMDLIB. However, if you choose to move modules to LPALIB from CMDLIB, this movement should be identified to SMP/E, so that future product and service installations do not cause problems.

You can use the SMP/E UCLIN command to identify dual residency, or movement, of the modules for TSO/E commands. For more information about UCLIN, see the .