Program run using user commands runs in RSE runs as QUSER -- WDSCI-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Program run using user commands runs in RSE runs as QUSER
From: "Dwight Hogancamp" <dhogancamp@xxxxxxxxx>
Date: Tue, 5 Jul 2005 15:48:44 -0400
List-archive: <http://archive.midrange.com/wdsci-l>
List-help: <mailto:wdsci-l-request@midrange.com?subject=help>
List-id: Websphere Development Studio Client for iSeries <wdsci-l.midrange.com>
List-post: <mailto:wdsci-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=unsubscribe>

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 since they 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?


Dwight HoganCamp
Newport NH

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.