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


Writing exits for the TEST command

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

Users issue the TEST command to test assembler programs in an unauthorized state. The TEST command lets the user trace a program's execution and diagnose possible errors. Users can issue the TEST command to debug active programs, or they can execute programs under the TEST command to test the programs before putting them into production. For more information about using TEST, see . For information about TEST and its operands, see .

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

If the initialization exit returns successfully to the TEST command processor and TEST processing itself abends, the TEST command processor invokes the termination exit before it terminates.

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

The following highlights some ways you can use the TEST exits. For more information about how you can use the exits, see Possible uses.
  • Restrict certain users from using the TEST command
  • Correct a user's errors on the TEST command
  • Change the operands a user specifies on the command

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014