PM/400 record locks -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: PM/400 record locks
From: Neil Palmer/DPS <neilp@xxxxxxxxxxx>
Date: Thu, 4 Nov 2004 11:07:29 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Has anyone else seen record locks in the Q1PDR job (in QSYSWRK subsystem) 
at month-end, because IBM's default settings for scheduling jobs has 
Q1PMONTH run at the same time at month-end that the Q1PDR job is running? 
I've seen this on 3 customer V5R2 systems at the October month-end.  They 
have three single thread job queues (Q1PSCHQ, Q1PSCHQ2 & Q1PSCHQ3) so it 
looks like someone coding PM/400 screwed up and didn't submit Q1PDR & 
Q1PMONTH to the same job queue.

...Neil

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2026 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.