If these are “disconnected jobs”, they should have status DSC. They should show up in WRKACTJOB with <F14=Include> just like SRQ and GRP jobs.

If they’re disconnected, users can enter their profile and password, and they should be able to jump back into whatever they were doing — if things are configured appropriately.

Tom

There shouldn’t be anything about QDFTJOBD that would keep an active job from being visible in WRKACTJOB — unless the QDFTJOBD is badly misconfigured (or the job simply routed to a subsystem that was in an unexpected segment of the WRKACTJOB display and scrolling would show where it was).

The QDFTJOBD might have the USER() parameter configured with a name instead of USER(*RQD) for example. If the problem user then also had *USE authority to the profile on QDFTJOBD, then jobs could be submitted to run under the other user’s authority. That is an extremely risky item that should be changed ASAP.

But an incorrect *JOBD could easily cause a job to end abnormally for many reasons.

So, perhaps the “most common” reason that a job doesn’t show up in WRKACTJOB is simply that the job isn’t active.

If there was some other reason, could you let us know what it was?

Tom