|
|
|
The EXITS statement is optional. Its presence tells CA JARS 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 your Systems Programmer Guide.
The set code for the EXITS statement may be left blank; however, such a statement is overridden if CA JARS 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.
|
Position |
Field Length |
Field Name |
Notes |
|
|---|---|---|---|---|
|
1 |
1 |
Set Code |
|
|
|
2-9 |
8 |
Statement Type |
EXITS |
|
|
10-17 |
8 |
Exit Name #1 |
Before calculation of charges |
Use blanks if there is no exit. Use xxxxxxxx for a member or alias name. |
|
18-25 |
8 |
Exit Name #2 |
After calculation of charges |
Use blanks if there is no exit. Use xxxxxxxx for a member or alias name. |
|
26-33 |
8 |
Exit Name #3 |
Output Phase |
Use blanks if there is no exit. Use xxxxxxxx for a member or alias name. |
|
34-80 |
39 |
Reserved |
Not used |
|
| Copyright © 2012 CA. All rights reserved. |
|