By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.
Privacy

Processing your response...

Discuss This Question: 2 &nbspReplies

There was an error processing your information. Please try again later.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.
Privacy

AFAIK, the only useful feature at the system level would be an *AFTER/*READ trigger. The trigger would log some row identifier/key, the user, the timestamp and perhaps the program.
The logging might be done via SNDJRNE or the Send Journal Entry (QJOSJRNE) API. The journal entry itself will contain some useful data elements so that the trigger doesn't have to supply those.
If such logging is required, logging in a journal is probably best and easiest. You'd possibly want to save and generate receivers regularly. The journal should perhaps be created with JRNCACHE(*YES), though that does carry some small risk.
Any "read" logging at the row level necessarily brings up the issue of volume. You might put some limited intelligence into the trigger program to bypass entries caused by significant batch processes for example.
Tom

Tom,
I came to a similar solution re; using the SNDJRNE with a Journal code of U, User Defined. Although instead of using a trigger I am going to suggest we add it to selected Inquiry Programs to avoid creating entries for batch and subfile processing.
I thank you for your input.
Bill Poulin

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.
Privacy

Processing your reply...

Ask a Question

Free Guide: Managing storage for virtual environments

Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!

Share this item with your network:

To follow this tag...

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.
Privacy