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


Customizing the TEST command

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

Users can invoke the TEST command to test unauthorized assembler programs. This includes testing APPC/MVS transaction programs written in assembler language. This chapter describes how you can customize TEST command processing for your users. For information about how to customize the testing of authorized assembler programs, see Customizing the TESTAUTH command.

You can customize the TEST command in several ways:
  • You can supply unauthorized installation-written subcommands of the TEST command, and unauthorized installation-written command processors to be invoked under TEST. You must define those subcommands and command processors to TEST, using CSECT IKJEGSCU or member IKJTSOxx in SYS1.PARMLIB.
  • You can write exit routines to tailor the processing of the TEST command and its subcommands.
TSO/E provides the following exits for the TEST command and TEST subcommands:
  • IKJEGMIE -- Initialization exit for the TEST command
  • IKJEGMTE -- Termination exit for the TEST command
  • IKJEGCIE -- Initialization exit for TEST subcommands
  • IKJEGCTE -- Termination exit for TEST subcommands
Using the TEST exits, you can:
  • Restrict certain users from using the TEST command or TEST subcommands.
  • Change the operands a user specifies on the command or subcommands. For example, you can correct a user's errors or restrict users from using certain operands.
For more information about the TEST command exits, see Writing exits for the TEST command. For more information about the TEST subcommand exits, see Writing exits for subcommands of the TEST command.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014