EX – Exits
The following figure defines the execution (processing) exits to ISPW for each operation that can be executed against tasks.
Exits
Exits Definition Screen
The following figure is a list of Exits. It is the first screen displayed after entering option EX and selecting a version.
Exits Definition Screen
Detail Screen
The following figure shows the Exit details displayed when a specific Exit is selected from the Exit List screen.
Detail Screen
Field Descriptions
The following table describes each field for an external reference definition:
Field Descriptions
Field Name | Description |
|---|---|
Operation | A valid task operation, for example, S for Select (or edit). |
Exit Key | Type of processing exit. Valid values:
|
Description | A description of the purpose of the exit. |
Pre-Op Routine | The invocation of a routine to be run prior to standard ISPW processing. For a ‘$$$$’ exit definition, this is the name of the standard routine. Enter either the invocation of a panel, CLIST, or program. The field can be several lines to handle long parameters. For a ‘####’ definition, this routine is called from the standard routine prior to standard processing for all types. |
Post-Op Routine | The invocation or a routine to run after standard ISPW processing. For a ‘$$$$’ definition, this value is ignored. Enter either the invocation of a panel, CLIST, or program. The field can be several lines long to handle parameters. For a ‘####’ definition, this routine is called from the standard routine after standard processing for all types. |
Valid in Environment Fields | A flag to indicate in which environments this operation is valid. Some operations are only valid when the task is at a specific point in the TEST, HOLD, PROD cycle. Example: Operation B is valid at any time, while the S operation can only be used in the TEST environment. These fields only affect standard processing entries (exit key ‘$$$$’). Other entries are valid in the same environments as the standard exit they affect. A standard exit can be valid in one or more environments. The following is a description of the environments. Each environment requires a Y or N value. |
OUTS | The task is Outstanding. It has not been checked out and may exist in another assignment. |
TEST | The task has been checked out into the TEST level. This is where updates and component testing takes place. |
HOLD | The task is at a HOLD level but has not been promoted to production. |
PROD | The task has been promoted to the production level. |
Update Last Operation Code | A flag that indicates whether or not the task status fields LAST OP, LAST OP USER, LAST OP DATE, and LAST OP TIME should be updated when the operation completes successfully. The status fields are used to show information about the last significant operation for each task. Example: The browse operation B is not significant, but the edit operation S is. Enter Y for all operations that should update the task statistics and N for those that shouldn’t. This field is only used for standard processing entries (exit key $$$$). Example: If the browse operation was specified as Y, the LAST OP would be set to B when a task in production was browsed. This would overlay the LAST OP of P. |