USER vs CURUSER

[Buck Calabro <mcalabro@xxxxxxxxxxxx>]

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