|
midrange.com
I have had a problem with object locks since we went to V5R2. When the
system is brought down to restricted mode, there is still a PM400 job that
locks an object, and that causes the dedicated save to fail. I have to
kill the PM400 job after the system comes down to a restricted mode. This
has been a thorn in my side for a quite a while.
Jim Essinger
208-452-4058 ext 133
At 01:41 PM 11/4/2004, you wrote:
Yes, we have seen a few systems that occasionally encounter record locks
between Q1PDR and Q1PMONTH jobs. We are modifying the PM iSeries code
for
new systems to run these jobs at completely different times to avoid
these
locks. If this is a problem on your system, it is recommended that you
change the time of the Q1PMONTH job via GO PM400, Work with
automatically
scheduled jobs, option 2 to change on Q1PMONTH. Change it to a time
that
no PM iSeries jobs are scheduled; by default 03:00 would work.
Royan Bartley
IBM Rochester
207-230-0416
T/L 776-9966
Internet: royan@xxxxxxxxxx
PM eServer iSeries: http://www.ibm.com/eserver/iseries/pm
"It's kind of fun to do the impossible." Walt Disney
----- Forwarded by Royan Bartley/Rochester/IBM on 11/04/2004 02:58 PM
-----
Neil
Palmer/DPS
<neilp@xxxxxxxxxx
m>
To
Sent by: Midrange Systems
Technical
midrange-l-bounce
Discussion
s@xxxxxxxxxxxx
<midrange-l@xxxxxxxxxxxx>
cc
11/04/2004 10:07
Subject
AM PM/400 record
locks
Please respond
to
Midrange
Systems
Technical
Discussion
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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.
