Hi Scott, If that can helps...
FYI and As per documented . Demanding a job into the request queue does not automatically result in immediate submission for execution. When a DEMAND is issued for a job, that job is placed in the request queue where the availability of its input requirements is determined. (To request immediate scheduling without requirements checking, use the RUN and RUNH commands.) The same process occurs when a job is automatically scheduled into the queues. So a DEMANDed job might not start immediately and might also triggers other job depending on SCHID (So be careful when demanding a job as it might trigger a long jobs chain , if you want to submit a unique job prefer the RUN command) . Hi Lucas, Basically to identify the reason for which a job stands in the QUEUE and is not submitted as we are expected to is to use the command : LQP,JOB=jobname,LIST=STATUS This usually display a second line of meaningful info . Thanks and regards, Eric Goldenberg RSD SA ego@com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
