Re: Triggers and *Inzsr

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Each copy of the program should only initiate *INZSR once.

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
--
"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 01:43 PM
Please respond to midrange-l

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


Yes,  userS update the file (Differents jobs)
5250 for now only.
Later CS (visual rpg).

--
Stephane

> Well it depends.  Are there more than one user updating the file?  Is
> the
> file only being updated via 5250 or is it a C/S or web program?

_______________________________________________
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.