• Subject: RE: Trigger pgm: user & pgm id
  • From: "Kahn, David" <KAHN@xxxxxxxxxxxxxxxxxx>
  • Date: Fri, 7 Nov 1997 00:28:28 +0500

Karen,

Wouldn't it be easier just to switch on journalling for that file?
You'll get what you want automatically, controllably, and reliably with
no need to write a trigger.

Dave Kahn, TCO, Kazakstan
=========

kahn@tengizchevroil.com   (to November 25)
dkahn@cix.compulink.co.uk (from November 26)


>-----Original Message-----
>From:  Karen Bellecci [SMTP:KBellecci@osfa.state.la.us]
>Sent:  Wednesday, November 05, 1997 7:33 AM
>To:    MIDRANGE-L@midrange.com
>Subject:       Trigger pgm: user & pgm id
>
>I would like to identify the program and user that tripped the *UPDATE
>trigger when
>they were updating a database file.  We are using V3R1, not under journaling,
>commitment control, or ILE.  Just OPM Cobol at the moment.  What (CL) command
>can
>I use in my (Cobol) trigger program to identify this?  (We want to place the
>before and
>after images of the database change in a history file, with time, user and
>program that
>made the change.)
>uucp
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].