Hi Rob,
I had indeed seen the IFS objects that were not saved. These also show on our current system where the backup completes without any errors. So like you say, this is not causing the backup to complete with errors:
Message . . . . : 50 objects not saved.
Cause . . . . . : 45 objects were not saved due to the ALWSAV attribute set
to *NO. A CPD37C3 message was sent for each of those objects. 5 objects
were not saved because the system has indicated they should not be saved.
I do not see any other errors about objects not being saved because of a lock. These should show up in the log if there are any, right?
About the PTF's:
WRKPTFGRP
SF99724 30 Installed
SF99724 19 Installed
DSPPTF 5770BR1
PTF
ID Status
SI68856 Temporarily applied
SI68846 Permanently applied
SI68568 Superseded
Regards,
Erwin Donker
-----Oorspronkelijk bericht-----
Van: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> Namens Rob Berendt
Verzonden: dinsdag 6 augustus 2019 13:24
Aan: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Onderwerp: RE: BRMS backup completes with untraceable errors
I am also getting the CPD37C4: 46 objects not saved.
You need to press F4 on that. The details should show:
41 objects were not saved due to the ALWSAV attribute set to *NO.
5 objects were not saved because the system has indicated they should not be saved.
This will not cause the "completed with errors", as I am getting " Control group VUMONDAY type *BKU processing is complete.". What may cause errors if some stream files are not saved because they were locked. Let's face it, save while active is a sick joke when it comes to IFS. I take these objects and add them to QLNKOMT. Normally they are log files and that genre. The other option is to quiesce the process locking them. Or become numb to the "completed with errors" which I highly discourage.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Erwin Donker via MIDRANGE-L
Sent: Tuesday, August 6, 2019 5:46 AM
To: 'midrange-l@xxxxxxxxxxxxxxxxxx' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Erwin Donker <erwin.donker@xxxxxxxxxx>
Subject: BRMS backup completes with untraceable errors
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi,
We are currently in the process of migrating our system (V7R3) to a new machine. The new machine is installed and a full backup from our old machine has been restored on the new one.
On the new machine we have scheduled backups with BRMS the same way as we have on the old machine. The only differences are a few exit points in the control groups that deal with stopping and starting the system and sending reports. However, every backup we do on the new system ends with message BRM10A1 (Control group DAILY type *BKU completed with errors). But when I check the BRMS logs I don't find any errors. A few *LINK objects can not be saved, but these are all severity 00 and also happen on our old system (where the backup completes normally). The highest severity I can find in the BRMS log (other than the BRM10A1 message itself) is 20, which are regular CPC3701 (x objects saved from library y) messages.
This is an excerpt from the latest backup logs (XXXXXX are application libraries):
6-08-19 11:00:00 Begin processing for control group DAILY type *BKU.
6-08-19 11:06:18 Starting SAVSECDTA to devices TAPMLB02.
6-08-19 11:09:00 All security objects saved.
6-08-19 11:09:00 Save security data (SAVSECDTA) complete.
6-08-19 11:09:00 Starting SAVCFG to devices TAPMLB02.
6-08-19 11:09:03 All configuration objects saved.
6-08-19 11:09:03 Save configuration (SAVCFG) complete.
6-08-19 11:09:03 Starting *IBM backup, type *FULL.
6-08-19 11:10:57 156 libraries saved.
6-08-19 11:11:04 Backup *IBM, type *FULL complete.
6-08-19 11:11:05 Starting save of library or special value XXXXXX
6-08-19 11:11:05 Starting save of library or special value XXXXXX
6-08-19 11:11:05 Starting save of library or special value XXXXXX
6-08-19 11:11:05 Starting save of library or special value XXXXXX
6-08-19 11:11:14 4 libraries saved.
6-08-19 11:11:16 Starting save of library or special value QUSRSYS
6-08-19 11:11:29 2961 objects saved from library QUSRSYS.
6-08-19 11:11:29 Starting *ALLUSR backup, type *FULL.
6-08-19 11:11:31 Starting save of library or special value *ALLUSR
6-08-19 11:17:48 278 libraries saved.
6-08-19 11:18:33 Starting save of library or special value QUSRBRM
6-08-19 11:19:00 250 objects saved from library QUSRBRM.
6-08-19 11:19:01 Backup *ALLUSR, type *FULL complete.
6-08-19 11:20:57 72485 document library objects saved.
6-08-19 11:21:07 Starting save of list LNK_ALL to devices TAPMLB02.
6-08-19 11:24:36 50 objects not saved.
6-08-19 11:24:36 212597 objects saved.
6-08-19 11:24:58 Save of list LNK_ALL complete.
6-08-19 11:25:00 Starting save of media information at level *LIB to device TAPMLB02
6-08-19 11:25:02 16 objects saved from library QUSRBRM.
6-08-19 11:25:03 Save of BRM media information at level *LIB complete.
6-08-19 11:25:05 Control group DAILY type *BKU completed with errors.
I have no idea why the backup says it ended with errors. At first I thought it might have to do with the fact that we scheduled it in the Advanced Scheduler (QIJS) in stead of the regular wrkjobscde, but I just tested it from wrkjobscde and it's giving the same results.
Does anyone have an idea what could be causing our backups to end with "errors"?
Regards,
Erwin Donker
De disclaimer van toepassing op e-mail van de gemeente Den Haag vindt u op:
http://www.denhaag.nl/disclaimer
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
De disclaimer van toepassing op e-mail van de gemeente Den Haag vindt u op:
http://www.denhaag.nl/disclaimer
midrange.com
