RE: QCMDEXC

[D.BALE@xxxxxxxxxxxxx]

Not if the application was testing for the lock.

Another possibility that I didn't think of earlier is where a record is locked
for update in another job and this job attempts to retrieve it from a file
opened for update; if the program is "smart" enough to code for the error
indicator on the CHAIN, it may be doing the QCMDEXC 'DLYJOB...' at that point.

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 --------------------------
IF it were a lock wait .. wouldn't the job status be LCKW ?

Is it perhaps only a coincidence that these delays are hitting us when the
AS/400 is at its most heavily utilised ever ?

It is like we are being penalised by a CFINT-like clone.

Jeff B

-----Original Message-----
From: D.BALE@handleman.com [mailto:D.BALE@handleman.com]
Sent: Wednesday, April 25, 2001 3:11 PM
To: MIDRANGE-L@midrange.com
Subject: RE: QCMDEXC


Assuming that the DLYs were the byproduct of a locked object:

I suppose it's possible that you had one monster job (or maybe several) that
had a lock on an object for most of the day?  That's all it would take to
trigger those DLYs you've been seeing, if all of those "many different jobs"
were trying to use the object that was locked.

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 --------------------------
... but why would this suddenly start to happen to so many different jobs ?

Yesterday was a particularly busy day on the system with Disk-arm util%
through the roof - so I guess that locking waits could be the answer.

It is strange that I have never seen symptoms like this before - on this
particular AS/400, or any others.  Yes, I've seen DLY-nnn's before, but on
monitor or service jobs, not on application jobs.

Perhaps today it will disappear as mysteriously as it appeared ?

Jeff Bull

-----Original Message-----
From: Bull, Jeff [mailto:BullJ1@Midas-Kapiti.com]
Sent: Tuesday, April 24, 2001 5: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.
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 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 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
+---