Jim,

Using AJS and BRMS, I do a full save, while active, every night, at 10:00 PM, done by 00:15.
I avoid any scheduled batch jobs during this window.
Less than 20 interactive users, low activity.


Weekly Retain Save SWA
Backup List ASP Activity Object While Message Sync
Seq Items Type Device SMTWTFS Detail Active Queue ID

10 *EXIT *******
20 *SAVSECDTA FFFFFFF *NO
30 *SAVCFG FFFFFFF *NO
40 *ALLUSR *SYSBAS FFFFFFF *ERR *YES QSYSOPR *NONE
50 *ALLDLO FFFFFFF *NO *YES
60 *LINK *ALLAVL FFFFFFF *NO *NO
70 *EXIT *******

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Franz
Sent: Wednesday, August 05, 2015 11:27 AM
To: Midrange Systems Technical Discussion
Subject: Re: WRKSPLF MCH5804 error during SAVLIB *ALLUSR getting checkpoint

So do you enforce any "quiet time" to get a clean checkpoint across many libs or just deal with some app issues?
Thinking of not syncing QUSRSYS with other libs...
Jim

On Wed, Aug 5, 2015 at 11:02 AM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
wrote:

Jim,

I've seen not only issues with WRKSPLF while QUSRSYS is being saved,
1) jobs trying to end that need to create a joblog
2) Any kind of activity to an outq

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Jim Franz
Sent: Wednesday, August 05, 2015 10:44 AM
To: Midrange Systems Technical Discussion
Subject: WRKSPLF MCH5804 error during SAVLIB *ALLUSR getting
checkpoint

Was somewhat surprised to see users have issues with WRKSPLF command
with default to *CURRENT user during save operation . at V7R1


SAVLIB LIB(*ALLUSR) DEV(&DRIVE) ENDOPT(*LEAVE) +
USEOPTBLK(*YES) SAVACT(*SYNCLIB) +
SAVACTMSGQ(QUSRSYS/SAVACTMSGQ) +
SPLFDTA(*ALL) QDTA(*DTAQ) OMITLIB(ME_*) +
OUTPUT(*OUTFILE) OUTFILE(QGPL/SAVLIBHST) +
OUTMBR(*FIRST *ADD) INFTYPE(*ERR)

I assume it's the SPLFDTA(*ALL)
Once checkpoint achieved and tape started to roll, WRKSPLF worked with
no errors.
Most outqs in QUSRSYS, and could not sync QUSRSYS with others?

Jim Franz
--
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.


--
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 thread ...

Follow-Ups:
Replies:

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

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