Submitting the same Job from multiple users to a single threaded jobq. Output from one job going to another jobs printer?

10 pts.
Tags:
AS/400
JOBQ
OVRPRTF
SBMJOB
We have a Work Order Create program that gets invoked by multiple users multiple times throughout the day. The jobs are submitted to a jobq that is single threaded. Within the calling CL there is a SBMJOB of a secondary job that also gets submitted to the same single threaded jobq. The problem is somehow the output (reports) are sometimes going to a different printer. For example: User A submits job with printer PRT1, User B submits the same job with printer PRT2 and User C submits the same job with PRT3. User A's output may end up on User B's printer? If the queue is single threaded how is this possible? thanks in advance :)

Software/Hardware used:
AS/400 and JDEdwards

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta
    If the queue is single threaded how is this possible?   It isn't. But you probably guessed.   That is, the job queue doesn't matter. Single-threade, multi-threaded, different queues per user, same results are possible no matter which.   The problem is probably somewhere in the structural relationship between the initial submission by a user and the execution of the final step in the series.   A hypothetical scenario might be something like:   User A runs the Work Order Create option and gets the first job started. User B gets a second request on the job queue while the first step of User A's job is running.   When a user executes the initial request, various attributes for that user are stored somewhere, perhaps in a file but perhaps in a data area or other container. These attributes are retrieved when the second steps of the submitted jobs run.   If a single data area was used, it might be clear how a second user's attributes could overlay the first user's. If a file is used, it might depend on how keys are constructed or the physical sequence compares to logical sequence or even the same record might be used for all requests. Records might be written in one sequence and retrieved in another.   Regardless, that's all hypothetical. We'd need to know a lot more about how it all is configured and how the steps are programmed. About all we can say is that the job queue is most likely irrelevant (unless the programming is somehow using it in its logic; and the logic is most likely where the problem is).   If you can show us some detail about the process, particularly the exact way that the final printer choice is determined and used, we can probably work it through. Many large packages still have basic internal modules that could have been written originally many years ago. As long as they "work", there is no profit in replacing them. Storing user attributes, such as associated printers, in files rather than in job descriptions or other system objects isn't unusual. As system complexity grows, potential conflicts might show up unexpectedly.   Tom
    125,585 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following