Re: Program run using user actions runs in RSE runs as QUSER - correction in subject

wdsci-l-bounces@xxxxxxxxxxxx wrote on 07/05/2005 03:59:56 PM:

> We have our own source control programs that check AS/400 items in/out 
we
> are developing.
> 
> I created a user action to run from RSE and checked out a program using 
it.
> It added a record
> to our log file saying QUSER checked it out. These showed up shortly 
after
> we were enduring our
> SOX audit, and caused our staff some distress as they just assured the
> auditors, no one can sign on
> and execute programs with this ID.
> 
> Our staff responded by banning programmers on our staff from using user
> actions to run programs.
> Does this work this way by design or is it just because QUSER is the 
default
> user. If we are to
> use RSE as a replacement for PDM, we need to have values like this on 
follow
> through.
> 
> On many programs it doesn't matter who ran it, and QUSER is fine but in 
this
> instance and many
> similar ones, it does matter. Is there a setting I can use to set this, 
or
> is it an unreported bug?

The USER portion of the job identifier is QUSER since your program runs in 
a pre-start server job, but the current user of the job will be the signed 
on profile.  You just need to change your program that is determining the 
user to run RTVJOBA CURUSER() or RTVUSRPRF *CURRENT

Mark



_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services 
powered by MessageLabs. 
_____________________________________________________________________________