Re: user id when vb program calls rpgle

Come on boys, join the 21st century..

agreed!  my only excuse is the sds is a /copy originally from early 90's
jim

To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, May 19, 2006 10:39 AM
Subject: RE: user id when vb program calls rpgle

Come on boys, join the 21st century..

    d gProgramStatus...
    d                sds                  qualified
    d  procName         *PROC
    d  currStatus       *STATUS
    d  prevStatus                    5s 0 overlay(gProgramStatus:16)
    d  jobUser                      10a   overlay(gProgramStatus:254)
    d  currentUser                  10a   overlay(gProgramStatus:358)

See, you don't have to worry about getting the to-pos correct. <grin>

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Franz
Sent: Friday, May 19, 2006 10:13 AM
To: Midrange Systems Technical Discussion
Subject: Re: user id when vb program calls rpgle

Thanks Rob - the pgm status data structure is good (but it is
358 - 367)
D USER          254   263       value=QUSER
D CUSER       358   367       value=JIMF

jim franz

----- Original Message ----- From: <rob@xxxxxxxxx>

To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, May 19, 2006 8:24 AM
Subject: Re: user id when vb program calls rpgle


> Instead of using
>     D USER                  254    263          * User name
> Have you tried
>     D Curr_User             358    360a         * Current user
>     D*      * see profile handle
>     D*      *   api's
> If that doesn't cut it, one of these might
>
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/ap
is/sec1.htm
> "profile handle"
>
> Rob Berendt

> -- > Group Dekko Services, LLC

> Dept 01.073
> PO Box 2000
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> "Jim Franz" <franz400@xxxxxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 05/18/2006 10:40 PM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
> To
> <MIDRANGE-L@xxxxxxxxxxxx>
> cc
>
> Subject
> user id when vb program calls rpgle
>
>
>
>
>
>
> How can I retreive the logged on user id when a pc VB
program calls a
> rpgle.
> I need to write an audit record of who accessed the record
- and the rpgle
> program data structure says QUSER called it.
> Is there an api or some way to get logged in user.
>
> jim franz

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

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


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

--

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.