Use this job level rule to define the header information used in the error file if an error occurs during the processing of a transaction. You can use any global variable (GVM) in the text defined to the system.
Parameter |
Description |
Token |
A string of characters used to denote the beginning and end of a global variable name. Use a colon (:) to terminate the token string of characters. To substitute a global variable into the text, surround the name of the global variable with the token string. Be sure to use a string of unique characters for the token that are not defined in the text. For example, you could use '***'. You cannot use a colon (:) in the TOKEN string. |
Text |
A text string. The text string may include embedded tokens and global variables. Do not start the text string with a colon (:). |
Note | Use a colon (:) to separate the token from the text. You must use a token even if there are no embedded global variables in the text string. |
;SetErrHdr;;***: Transaction: ***PolicyNum***;
;SetErrHdr;;***:Company Name: ***Company***;
This example substitutes the global variables, PolicyNum and Company, into the error file header information. If the global variable PolicyNum was equal to MVF10002 and Company was equal to ABC Insurance Company, the text output to the error file would be:
Transaction: MVF10002
Company Name: ABC Insurance Company
To add lines to the header, use the rule multiple times. Each time you use the rule, the system adds a line to the header, which you will see in the error file (ERRFILE.DAT).
Note | The global variable names must be spelled exactly as they are defined to the system. |
© Copyright 2014, Oracle and/or its affiliates. All rights reserved. Legal notices.