Re: Triggers and *Inzsr

[rob@xxxxxxxxx]

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Yes, but how did you populate that field in the first place?  Did you use
either:
     D* Program status data structure
     D f              SDS
     D P_JOB_NAME            244    253      * Job name
     D P_USER                254    263      * User name
     D P_JOB_NUM             264    269S 0      * Job number
or RTVJOBA?  If so, then both would be in error.  Instead you might want
to look at the JOBI0600 format returned by the QUSRJOBI API and the field
'Current User Profile'.  See:
http://publib.boulder.ibm.com/iseries/v5r2/ic2924/info/apis/qusrjobi.htm

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




Stephane Leon <StephaneLeon_ml@Bluewin.ch>
Sent by: midrange-l-admin@midrange.com
11/05/2002 02:22 PM
Please respond to midrange-l

        To:     midrange-l@midrange.com
        cc:
        Fax to:
        Subject:        Re: Triggers and *Inzsr


Ok, if i have to pick the usrprf ''who did this change, add, or
delete'' i 'll pick it from the data itself (field
on record) , not from the job.

--
Stephane

> With each 5250 user it will load a copy into their job.
> With C/S I am not exactly sure how it works.  There will be some job in
> either QSYSWRK or QUSRWRK that is running this.  This job will probably
> not be under the user profile maintaining the file.  Instead it will be
> under some IBM profile.  However you should be able to see which job
> it is
> by doing a WRKOBJLCK myuser *USRPRF.  Even though the job is running
> under
> that IBM profile, it will have a lock on the user profile of the job
> it is
> currently servicing.  A good reason to be careful in your PSDS to pick
> the
> right user profile field when determining which user is modifying the
> data.  It does little good to report the IBM user profile.
>
> Rob Berendt

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.