This chapter contains these topics:
Sleeper may need to be used when files are open and existing locks prevent triggers from being applied or if the processing is to be done after hours. By running audit programs in batch mode, use Sleeper with hidden selection 82 to hold the JOBQ and release in sleeper at a later time. When using sleeper it is necessary to review the sleeper log for successful completion. For more information about hidden selection 82 or sleeper, refer to the JD Edwards World Technical Foundation Guide.
OS V5R1 allows you to place multiple triggers on a database file (300). Prior to V5R1, the maximum triggers on a file were six: one for each event (action) Add/Change/Delete, and one for each time *BEFORE/*AFTER the file was updated.
An audit file created using the Database Audit Manager tool cannot be audited by DBAM.
Triggers running within interactive jobs have negligible performance impacts. It is the same as taking a menu option, a selection or function exit from another program. Batch jobs are where the impact can be significant as the trigger fires for every record add/change/delete. DBAM trigger code has been highly optimized to minimize performance issues in batch programs as much as possible. For extremely high volume transaction processing, analysis and consideration of trigger removal, then reapplying may be feasible or necessary.
Customers who are coexistent with both JD Edwards World and JD Edwards EnterpriseOne must determine if the file to be audited is used and maintained by JD Edwards World and JD Edwards EnterpriseOne applications in the designated audit environments. Some customers choose to coexist with certain applications and not others and so it may be difficult to establish if a file is truly coexisting--you can use cross-reference tools to help determine this. If it is found that the file to be audited is maintained by both JD Edwards World and JD Edwards EnterpriseOne, it must be setup under the JD Edwards EnterpriseOne audit tool rather than the JD Edwards World audit tool. If the file is only used and maintained through the JD Edwards World applications, then the file should be setup under the JD Edwards World audit tool.
Trigger programs can affect system performance. The generated trigger programs will be designed to minimize adverse system performance.
Reporting on audit files may be created using the JD Edwards World Writer programs. For assistance, contact the JD Edwards World Support Services - JD Edwards World technical.
Each audit file will contain 12 fields in addition to the fields selected on the Field Selection List (P98203) screen. Note the file prefix on these fields will be the same as the file that is setup for auditing; this is used to avoid any possible duplication of fields from the audited file.
| Name | Description |
|---|---|
| TRGEVT | Trigger event (A/C/D) |
| RCDIMP | Record image type (Before/After) |
| SRLNBR | Reason code serial number |
| ESGVFY | Signature verified |
| ESGUSR | Signature UserID |
| ESGRSN | Signature description reason |
| TXUnid | Associated text key |
| JOBNAM | Updated by Job Name |
| PGMNAM | Updated by Program |
| USERID | Updated by UserID |
| UPDDAT | Updated on Date |
| UPDTIM | Updated at time |