What does “Job is not waiting for a specific message.” mean?

620 pts.
Tags:
AS/400
AS/400 Active Jobs
AS/400 jobs
My batch-job is most of the time in MSGW status, but when I take opt-7 against it it shows..."Job is not waiting for a specific message." What does it mean basically? I run EOD (End-Of-Day) job (i.e. my batch job), but these days it is taking much much longer time than usual. Please advice. Thanks a lot! -Svanky

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: 5  Replies

 
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
  • philpl1jb
    Your job is waiting for resources.Other jobs of higher priority might be grabbing resources.Your job may be waiting for some system request that it's made to be completed. 
    50,385 pointsBadges:
    report
  • TomLiotta
    It means that the job is waiting for a message to arrive somewhere. When WRKACTJOB option 7 is used, it only works if the job is waiting for a *RPY message that relates to a *INQ message that was sent by the job. In your case, the current program is just waiting for any message.   You'll have to look at the source code to determine which message queue the program is trying to receive from and to see what the program is expecting.   (Technically, it could also mean that the program had finished waiting before you finished typing "7" and pressing <Enter>.)   Tom
    125,585 pointsBadges:
    report
  • TomLiotta
    BTW, in short, option 7 is not relevant for the job. -- Tom
    125,585 pointsBadges:
    report
  • Splat
    I'd suspect this is similar to a technique used by our software provider where a message queue is monitored by a major process to determine when subsidiary processes have completed prior to initiating further processes. 
    7,395 pointsBadges:
    report
  • ToddN2000
    Sounds like it waiting on an event. Most likely waiting for a MSGQ or DTAQ to trigger an event that will force the job to continue or terminate the job. We use this method a lot with our ASYNC jobs that run all day.To end we writ to the MSGQ an * in position 1. The job wakes up reads the MSGQ. This then causes the program to shut down.
    12,745 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