|
|
|
|
Position |
Field Length |
Field Name |
Notes |
|---|---|---|---|
|
1 |
1 |
Set Code |
|
|
2-9 |
8 |
Card Type |
EXITS |
|
10-17 |
8 |
Exit Name #1 |
Before Calculation of Charges |
|
18-25 |
8 |
Exit Name #2 |
After Calculation of Charges |
|
26-33 |
8 |
Exit Name #3 |
Output Phase |
|
34-80 |
39 |
Reserved |
Not used |
This statement, identified by the statement type EXITS, is optional. Its presence tells the Report Writer that you will use at least one exit at various phases during processing. Three exits allow you to edit, modify, and delete accounting information in the reporting phase. Details regarding these exits are discussed in the User Exit Routines section of this chapter.
The set code for the EXITS statement can be left blank; however, such a statement is overridden if the Report Writer encounters an EXITS statement with a nonblank set code.
If an Exit Name field on the EXITS statement is omitted, no exit is taken. A nonblank field sets up the exit and must be the one to eight-character load module name of the user-coded exit routine to be accessed. An exit program must be available to the Report Writer as a member of a z/OS or VSE executable library.
The Load Library containing the EXIT modules can be any z/OS PDS. If you choose to use &CAIPRFX..CAJRLOAD, be sure not to replace a member supplied by CA. If you prefer a user exit library, concatenate it to the //STEPLIB DD statement.
| Copyright © 2012 CA. All rights reserved. |
|