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


Programming considerations

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

The CONSPROF exits must follow standard linkage conventions. They must save the registers on entry and restore the registers when they return. The exits must be re-entrant, refreshable, reusable, and APF-authorized.

The exits can use any of the TSO/E service routines. For a description of the service routines, see .

In some cases, you may not need to write a termination exit. This depends on:
  • Whether the processing that the initialization exit performs requires a termination exit to perform clean-up activities.
  • How you use the exits to customize CONSPROF processing.

If the initialization exit obtains a system resource, you must write a termination exit to free the resource. For example, if the initialization exit obtains storage to return a new command buffer to the CONSPROF command processor, you must provide a termination exit to free the storage.

The initialization exit can change CONSPROF operands using the command buffer. The exit checks the command buffer it receives and determines whether to change any operands. To change operands, the exit must:
  • Obtain storage for a new command buffer
  • Build the new command buffer
  • Update the key, length, and data fields for the new command buffer (parameter entry 2)
  • Set return code 0 and return control to CONSPROF

For more information about the parameter entries, see TSO/E standard exit parameter list. For more information about the format of the command buffer, see Command buffer.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014