Out of curiosity...
 
     We have a third-party application now running on our system.  It
     requires that a background job be running.  The application is a
     data-base access process that issues SQL calls against a TurboImage
     data base for an on-line user on some server off-site.  The job logs
     on as THIRDPTY,MGR.THIRDPTY.  Thus a SHOWJOB will display:
 
     #J403   EXEC        10S LP       WED  8:27A  THIRDPTY,MGR.THIRDPTY
 
     When a user invokes this process, the request for data come through
     the background job.  I understand that a change of logon is executed
     to service that request.  However, the identity of the job logon
     changes to correspond to the changed logon.  We do not see any
     additional sessions or jobs.  Here is what happens:
 
     #J403   EXEC        10S LP       WED  8:27A  USER3PTY,USER3PTY.ACCOUNT
 
     Two questions:
 
     1.  How does the identity of a job change once it is in the EXEC
     state?
 
     2.  Why might the developers of this software want to do this (or why
     would MPE/iX require them to do it)?