USER vs CURUSER

Buck,

I am not aware of any document that lists those functions which might
swap to a current user during their processing.  Most, if not all, of
the various server type jobs should be swapping to the current user
though (FTP and HTTP to name two others that come immediately to mind).

In general I would recommend always accessing CURUSER if you are
interested in knowing who is currently running within a process (as
opposed to who initiated the process).

Bruce Vining

>
>There's an API (QWTSETP?) that allows you to change
>the user profile that the job runs under.  It's designed
>for server type jobs, where you may need this invocation
>to use USER1 and the next invocation to use USER2 instead of
>all invocations using a generic profile like QUSER.  Cool.
>
>I think IBM is using this for VaRPG/ODBC/Client Access, because
>when I do a RTVJOBA USER(&USER) in a VaRPG program, I get
>QUSER.  When I do a RTVJOBA CURUSER(&USER) I get BUCK.
>Can anyone refer me to a document that explains what other
>programs IBM has done this with?
>
>Buck Calabro
>Commsoft, Albany, NY
>mailto:mcalabro@commsoft.net
>

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---