|
I went into DSPLOGBRM and got pretty much the exact second that I saw
"Starting save of list *LINK to devices". Then I searched the flight
recorder for that date. Once I found the date I scanned for that time.
2/03/15 1:41:14 Starting save of list *LINK to devices TAPKVL01.
wrklnk '/tmp/brms/flight*'
Picked the one without an extension.
02/03/15 01:41:14.114 072687 BACKUP q1aOL
q1aCallQsrSaveApi::q1aCallQsrSaveApi - Backup Item: *LINK
02/03/15 01:41:14.114 072687 BACKUP q1aOL
q1aCallQsrSaveApi::q1aCallQsrSaveApi - Control group: MONDAY
02/03/15 01:41:14.114 072687 BACKUP q1aOL
q1aCallQsrSaveApi::q1aCallQsrSaveApi - Backup Item: *PROCESS
02/03/15 01:41:14.114 072687 BACKUP q1aOL
q1aCallQsrSaveApi::q1aCallQsrSaveApi - Here is the command: QSYS/SAV
DEV('/QSYS.LIB/TAPKVL01.DEVD') OUTPUT('/tmp/brms/q1asav072687')
INFTYPE(*ALL) CHGPERIOD(*ALL *ALL ) PRECHK(*NO) CLEAR(*NONE)
DTACPR(*DEV) COMPACT(*DEV) USEOPTBLK(*YES) UPDHST(*YES) TGTRLS(*CURRENT)
PVTAUT(*NO) SEQNBR(*END) EXPDATE(031015) ENDOPT(*LEAVE) SAVACT(*YES)
SAVACTMSGQ(*NONE) SYNCID(*NONE ) ASPDEV(*ALLAVL)
It repeats this command a few times in the flight recorders:
02/03/15 01:41:14.114 072687 BACKUP q1aOL
q1aCallQsrSaveApi::q1aCallQsrSaveApi - Here is the command: QSYS/SAV
DEV('/QSYS.LIB/T
02/03/15 01:41:14.117 072687 BACKUP q1aMS q1aSysObjCommand::execute()
- Command for user 1 to *LCL QSYS/CHKOBJ OBJ(QTEMP/QBRMSP
02/03/15 01:41:14.117 072687 BACKUP q1aMS q1aSysObjCommand::execute()
- Command for user 1 to *LCL QSYS/CHKOBJ OBJ(QTEMP/QBRMSP
02/03/15 01:41:14.118 072687 BACKUP q1aMS q1aSysObjCommand::execute()
- Command for user 1 to *LCL QSYS/CHKOBJ OBJ(QTEMP/Q1AUSA
02/03/15 01:41:14.119 072687 BACKUP q1aMS q1aSysObjCommand::execute()
- Command for user 1 to *LCL QSYS/CHKOBJ OBJ(QTEMP/QBRMSP
02/03/15 01:41:14.119 072687 BACKUP q1aMS q1aSysObjCommand::execute()
- Command for user 1 to *LCL QSYS/CHKOBJ OBJ(QTEMP/QBRMSP
02/03/15 01:41:14.120 072687 BACKUP q1aMS q1aSysObjCommand::execute()
- Command for user 1 to *LCL QSYS/CHKOBJ OBJ(QTEMP/Q1AUSA
02/03/15 01:41:14.120 072687 BACKUP q1aOB
q1aListOfLinkObjectsEntry::setRefreshCriteria() setting criteria
02/03/15 01:41:14.122 072687 BACKUP q1aQS
q1aSQLConnection::checkSQLConnection() - already connected to *LCL
02/03/15 01:41:14.122 072687 BACKUP q1aDB q1aSQLImpl::bind() - SELECT
* FROM QUSRBRM.QA1AFS WHERE FSNAME = 'QLNKOMT' AND
02/03/15 01:41:14.136 072687 BACKUP q1aOL q1aCallQsrSaveApi::process
- Current Command Built: QSYS/SAV DEV('/QSYS.LIB/TAPKVL01.
02/03/15 01:41:14.137 072687 BACKUP q1aU1
q1aIFSApiSaveOS400::q1aIFSApiSaveOS400() ctor saveCmd: QSYS/SAV
DEV('/QSYS.LIB/TAPKVL
...
02/03/15 01:41:14.148 072687 BACKUP q1aU1
q1aIFSApiSaveOS400::initAsynchronousBring ASYNCBRING not specified no data
area, key not added to api.
Even then I'd bet that it doesn't use the command, based on this:
02/03/15 01:41:14.153 072687 BACKUP q1aU1 q1aIFSApiSaveOS400::doit -
QsrSave API start
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
From: Frederick Boniholmes <seft2011@xxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Date: 02/03/2015 03:04 PM
Subject: Re: Added 39.6GB file to backup, time only grew 4 minutes.
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Hi Rob,
I have checked the flight recorders, but I have not seen any commands
you pasted here. Is it a setting somewhere?
Regards,
Bon
On Tue, 3 Feb 2015 09:15:42 -0500, rob@xxxxxxxxx wrote:
http://www-01.ibm.com/support/docview.wss?uid=nas8N1011242SAVACTMSGQ(*NONE)
CALL PGM(QBRM/Q1AOLD) PARM('PARMOVR' '*DISPLAY' 'ASYNCBRING')
ASYNCBRING:.
Comparing that with the BRMS flight recorder and it doesn't look like we
are using that.
02/02/15 22:59:50.741 724038 ROB q1aOL
q1aCallQsrSaveApi::q1aCallQsrSaveApi
- Here is the command: QSYS/SAV DEV('/QSYS.LIB/TTAPKVL01.DEVD')
OUTPUT('/tmp/brms/
q1asav724038') INFTYPE(*ALL) CHGPERIOD(*ALL *ALL ) PRECHK(*NO)
CLEAR(*NONE)
DTACPR(*DEV) COMPACT(*DEV) USEOPTBLK(*YES) UPDHST(*YES) TGTRLS(*CURRENT)
PVTAUT(*NO)
SEQNBR(*END) EXPDATE(030915) ENDOPT(*LEAVE) SAVACT(*YES)
minutes.
SYNCID(*NONE ) ASPDEV(*ALLAVL)
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
From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'midrange-l@xxxxxxxxxxxx'" <midrange-l@xxxxxxxxxxxx>
Date: 02/03/2015 08:41 AM
Subject: RE: Added 39.6GB file to backup, time only grew 4
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20i%20Technology%20Updates/page/Achieve%20faster%20IFS%20save%20times%20using%20SAV%20with%20ASYNCBRING
Rob,
Are you using ASYNCBRING, default is *NO.
You may see even faster results.
My entire IFS save is only 5 minutes, LTO5 fiber.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Tuesday, February 03, 2015 8:22 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Added 39.6GB file to backup, time only grew 4 minutes.
Added a 39.6GB stream file to our backup. The save time only grew four
minutes. Yes, I am rather fond of fiber LTO4 drives.
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
--
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.