Hmmm.... Although it is sort of frustrating for debug, I doubt you'll see
this change in OS/400.
Those jobs are actually started long before you login with your user id,
and they have to be started with some user id.
The jobs are there in order to make your connect or login very fast. I.e.
you don't start a new job for your user, user just take an existing one
that happen to be started with QUSER to run your request.
That job then authenticates with your user id and changes user profile of
the job (swaps) to that user so all work occurs under it.
The job NAME stays the same (QUSER) while the job identity is changed to
the login user.
I could have sworn that work management changed so that spooled files get
owned by the user that was actually in effect when the spooled file was
created. (Note that the NAME will still be quser probably).
Another thing you can do is in your application that you run, get the fully
qualified job name QUSRJOBI and return it to your client so that it can be
used for debug purposes. Client access does this a lot.
OR
Insert a record in a log somewhere with unique characteristics of your
client that helps you track it down.
i.e. user, time, application name.
"Do you believe that my being stronger or faster has anything
to do with my muscles in this place?" ... "Free your mind."
Laurence Fishburne as Morpheus in 'The Matrix'.
Fred A. Kulack - AS/400e Java and Java DB2 access, Jdbc, JTA, etc...
IBM in Rochester, MN (Phone: 507.253.5982 T/L 553-5982)
mailto:kulack@us.ibm.com Personal: mailto:kulack@bresnanlink.net
AOL Instant Messenger: Home:FKulack Work:FKulackWrk
+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---
