When I do WRKACTJOB, why is the host server job running under QUSER instead of the profile specified on the AS400 object?
To improve performance, the host server jobs are prestarted jobs running under QUSER. When the Toolbox connects to a host server job in order to perform an API call, run a command, etc, a request is sent from the Toolbox to an available prestarted job. This request includes the user profile specified on the AS400 object that represents the connection. The host server job receives the request and swaps to the specified user profile before it runs the request. The host server itself originally runs under the QUSER profile, so output from the WRKACTJOB command will show the job as being owned by QUSER. However, the job is in fact running under the profile specified on the request. To determine what profile is being used for any given host server job, you can do one of three things: • Display the job log for that job and find the message indicating which user profile is used as a result of the swap. • Work with the job and display job status attributes to view the current user profile. • U
Related Questions
- I am using a PC host running Microsoft Windows for a home application. Should I use a ShortStack Micro Server to attach the PC to a LonWorks network?
- Can I use VSMT to move virtual machines from one host running Virtual Server 2005 to another?
- Is there a way to host a WoW private server without running it off you own computer?
