My guess would be that your program calls QCMDEXC with the first parameter
coded as a variable.  That variable most likely contains a "DLYJOB DLY(300)".
To find where it's coming from, you may have to trace the variable value
backwards to programs higher in the program stack.

I don't believe that job logs ever show program parameter values when calling
the program.

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952
D.Bale@Handleman.com
  Quiquid latine dictum sit altum viditur.
  (Whatever is said in Latin seems profound.)

-------------------------- Original Message --------------------------
Hi all,
        has anyone come across this event and know of a solution ?

I have a number of batch jobs with a status of ACTIVE and the function
DLY-300;
The programs being executed do not have this coded in them;
The program-stacks of all these jobs have QCMDEXC and QWCDLYJB at the lowest
2 levels;
They go active at the end of the wait, but then go to DLY-300 again;
There is nothing in the job log;

Kind regards,
Jeff Bull.
Senior Support Consultant
Certified IBM AS/400 System Administrator
Midas Kapiti International Ltd
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].