A simple phrase...
PUT AN EXIT PROGRAM ON THE DDM/DRDA EXIT POINT!
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Eric Lehti
Sent: Wednesday, June 12, 2013 12:05 PM
To: Midrange Systems Technical Discussion
Subject: WHO is connecting via QRWTSRVR jobs and editing data?
Or stated more accurately . . .
When user BOB or TED or CAROL or ALICE edits IBM i records via our web portal, can I easily prove who the user is?
Our portal application, written in PHP, is hosted on a Windows server, and runs Apache.
The portal connects to our IBM i with QRWTSRVR jobs active in QUSRWRK subsystem, and runs under user profile APACHE which I created specifically for connections from that web server.
Is there a simple configuration so that:
1. when user BOB logs into our web portal, he runs a QRWTSRVR job under profile BOB 2. when user TED logs into our web portal, he runs a QRWTSRVR job under profile TED 3. when user CAROL logs into our web portal, she runs a QRWTSRVR job under profile CAROL 4. when user ALICE logs into our web portal, she runs a QRWTSRVR job under profile ALICE
That functionality would enable all data edits to be audited under each user's profile (BOB, TED, CAROL, ALICE) instead of the connection profile APACHE.
While you ponder whether to share your simple solution to my elementary question, enjoy this trip down memory
lane: (
http://en.wikipedia.org/wiki/Bob_%26_Carol_%26_Ted_%26_Alice)
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
