RE: QCMDEXC

[D.BALE@xxxxxxxxxxxxx]

I think the only way to tell for sure is to get a snapshot of the program
stack when a job exhibiting the behavior you described in a DLY-30 state.

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 --------------------------
The HLL programs are not executing the DLYJOB; I suspect this is an IBM
system function within QCMDEXC - at least that is what it appears to be on
the face of it.

Jeff B

-----Original Message-----
From: Buck Calabro [mailto:Buck.Calabro@commsoft.net]
Sent: Tuesday, April 24, 2001 8:00 PM
To: MIDRANGE-L@midrange.com
Subject: RE: QCMDEXC


Jeff, It sounds as if an HLL is using QCMDEXC to do execute the DLYJOB
command.  I've run across this in early attempts to deal with file locks.
The program attempts to OPEN the file, discovers that it's allocated, does a
DLYJOB for 5 minutes and tries again.

Buck Calabro
Commsoft; Albany, NY
"Nothing is so firmly believed as
 that which we least know" -- Michel Montaigne
Visit the Midrange archives at http://www.midrange.com

> -----Original Message-----
> From: Bull, Jeff
> Sent: Tuesday, April 24, 2001 12:15 PM
> To:   'MIDRANGE-L@midrange.com'
> Subject:      QCMDEXC
>
> 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.
+---
| 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
+---