The TEST command includes a number of subcommands that users can issue while the TEST command is executing. For example, under the TEST command, users can issue the LIST subcommand to display the contents of a virtual storage area or registers, or the DELETE subcommand to delete a load module from virtual storage. For more information about using TEST with subcommands, see . For information about TEST and its subcommands, see .

TSO/E provides an initialization exit and a termination exit for the subcommands of the TEST command. You can use the exits to customize TEST subcommand processing for your users. The initialization exit receives control before the TEST command invokes the subcommand. The termination exit receives control just before the TEST subcommand completes processing.

If the initialization exit returns successfully to the TEST subcommand and the TEST command processor itself abends, the TEST command processor invokes the subcommand termination exit before ending.

You can use the subcommand initialization exit to change the operands that users specify on the subcommand or correct user errors when they issue the subcommand. You can use the termination exit to perform clean-up or special processing prior to subcommand completion. Depending on the processing your subcommand initialization exit performs, you may not need a corresponding subcommand termination exit.