RE: WRKSPLF MCH5804 error during SAVLIB *ALLUSR getting checkpoint

Jim,

1) I fought BRMS at first too, now, could do without.
You should really reconsider BRMS.
No coding, lots of configuration.
Especially from managing the media, logs etc. no more manual logs or processes.

2) Libraries hardly ever give me an issue with the save.
IFS objects are another story, simply because sav while active does nothing for IFS objects, actually, it makes the IFS save longer.

3) We also have web activity during the save, part of which are temp objects on the IFS.
We solved those issues by writing all the web IFS object to TMP, which by default is not saved.
The entire IFS save is only 7 minutes, thanks to ASYNCBRING and other recent improvements.

http://www-01.ibm.com/support/docview.wss?uid=nas8N1011242

I do have other IFS save issues.
If the save gets the object first, then the app will probably fail.
If the app get the object first, object is skipped during the save.

Paul




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

Mine is pretty much the same, just no BRMS (on the system but not used (others did not want to deal with the retraining time plus code changes).
Low activity, but our activity is mostly web clients (both read and write/updates).
We start some heavy batch edi once user libs and IFS complete Jim.

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

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.

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