Communication between jobs

Aside from opening up a loopback TCP connection, or temporarily some object in a library (such as the *USRQs that are so ubiquitous in socket hand-off), does anybody know of a good way for one job to talk to another?

Scenario (somewhat oversimplified): a server job has the authority to launch child-server jobs (or any other kind of submitted jobs) under the connecting client user's profile, even if that user's password is expired, but not to change that user's expired password. Nor can the server job do a QWTSETP (assuming that would give it the ability to change the expired passwords) to an account with an expired password, because the expired password blocks QSYGETPH.

But jobs submitted by the server job under the connecting client user CAN change that expired password, because it's their own.

But they would need to pass back the success/failure of the password change, or else it would be blind. And of course, even with encryption applied to the parameters, it would be more secure to pass them as something other than command-line parameters on the SBMJOB.

Of course, the scenario is a non-issue if the server job runs under sufficient authority to do the password changes itself, but that's not always the case.