The following example is for an SAP application environment that is using an iSeries high availability software product, which is typically used for disaster recovery purposes. Because of this, the tape backup is performed on the replication target (backup) system.
The data library for the SAP environment is being saved with the Save While Active command:
Display Backup Control Group Entries S102XXXX
Group . . . . . . . . . . : R3PRDDATA
Default activity . . . . : *BKUPCY
Text . . . . . . . . . . : Save of R3PRDDATA - High Availability End and Start
Auxiliary Weekly Retain Save SWA
Backup List Storage Activity Object While Message
Seq Items Type Pool Device SMTWTFS Detail Active Queue
10 *EXIT *DFTACT
20 *EXIT *DFTACT
30 R3PRDDATA *SYSBAS *DFTACT *ERR *YES *LIB
The first user exit point in the BRMS Control Group ends the replication data group target processes:
User Exit Maintenance S102XXXX
Type command, press Enter.
Sequence number . . . . . . . : 10
Where used . . . . . . . . . : *EXIT
Weekly activity . . . . . . . : *DFTACT SMTWTFS
Command . . . . . . . . . . . . ENDDG DGDFN(R3PRD) PRC(*ALLTGT) ENDOPT(*CNTRLD) WAIT(500) TIMOUTOPT(*ENDIMMED)
The second user exit point uses the BRMS MONSWABRM process that watches for the Save While Active checkpoint message. Once the checkpoint message is received, the replication data group target side processes are restarted:
User Exit Maintenance S102XXXX
Type command, press Enter.
Sequence number . . . . . . . : 20
Where used . . . . . . . . . : *EXIT
Weekly activity . . . . . . . : *DFTACT SMTWTFS
Command . . . . . . . . . . . . MONSWABRM LIB(R3PRDDATA) CMD(STRDG DGDFN(R3PRD)) WAITMSG(7200)
Disclaimer:
Vision Solutions makes every effort to provide accurate system management information and programming code; however the company cannot be held liable for the accuracy of information nor its compatibility in your own environment. Please review and test thoroughly before implementing. © Copyright 2009, Vision Solutions, Inc. All rights reserved. IBM, System i, iSeries, and AS/400 are trademarks of International Business Machines Corporation. All other brands are property of their respective registered owners.
03/25/09 Using the Save While Active command within IBM's BRMS backup management software
03/16/09 Two ways to see what is using disk space
Method #1
Use the commands: RTVDSKINF and PRTDSKINF. The retrieve command will build a file that can then be printed with the print command by *LIB, *FLR, *OWN, *OBJ, *SYS
Method #2
Run a query on file QAEZDISK for more granular detail.
Still another method can be found at the blog post located at: http://visionsolutionsinc.blogspot.com/2008/04/easy-way-to-figure-out-what-is-eating.html
Disclaimer: Vision Solutions makes every effort to provide accurate system management information and programming code; however the company cannot be held liable for the accuracy of information nor its compatibility in your own environment. Please review and test thoroughly before implementing. © Copyright 2008, Vision Solutions, Inc. All rights reserved. IBM, System i, iSeries, and AS/400 are trademarks of International Business Machines Corporation. All other brands are property of their respective registered owners.
3/6/09 How to change System Request options
Although what is displayed on the System Request menu screen isn't easy to change, it easy to change what the options shown on that screen actually do.
The commands executed by the system request menu are stored in a message called CPX2313, which is located in QSYS/QCPFMSG. Keep in mind that the commands are not exactly in order, so you have to be careful with making changes to this message file.
Use the command DSPMSGD CPX2313 and you will see see how easy it is to change, for instance, DSPJOB to WRKJOB.
Caution: Whenever you make changes to CPX2313 it is important to remember the change is a global one and should not be used lightly!
Disclaimer: Vision Solutions makes every effort to provide accurate system management information and programming code; however the company cannot be held liable for the accuracy of information nor its compatibility in your own environment. Please review and test thoroughly before implementing. © Copyright 2009, Vision Solutions, Inc. All rights reserved. IBM, System i, iSeries, i5/OS and AS/400 are trademarks of International Business Machines Corporation. All other brands are property of their respective registered owners.
02/23/09 Learn more about any IPL process
Want to know more about an IPL than simply the date and time of the last IPL? Sometimes, the information provided by system values is just not sufficient. For instance,
- Did your last IPL take longer than usual?
- Did you recently apply PTFs and wanted to know how long that IPL step took?
- Need to know how long your system spent doing journal recovery?
- Need to know how long it actually takes to "power down"?
By making a simple program call, you can get a spool file that shows your last
power-down and IPL in full detail - Every system reference code and sub-code
is shown, along with the date and timestamp it was issued.
CALL QWCCRTEC
This program runs very quickly, and does not issue any messages. It produces
a QPSRVDMP spool file of about 15-20 pages. Look beyond column 85 for the
information you need. Here's a sample :
*XPF PWRDWN 10/25/08 07:14:20*
* D900 2740 10/25/08 07:14:21*
* D900 2750 10/25/08 07:14:22*
* D900 2770 10/25/08 07:14:22*
* D900 2780 10/25/08 07:14:22*
* D900 2790 10/25/08 07:14:22*
* D900 27C0 10/25/08 07:14:22*
*End PWRDWN 10/25/08 07:14:25*
*XPF IPL 10/25/08 12:40:05*
* C900 2810 10/25/08 12:40:05*
* C900 2820 10/25/08 12:40:05*
* 10 20 0010 10/25/08 12:40:05*
* 10 20 0020 10/25/08 12:40:05*
* 10 30 0010 10/25/08 12:40:05*
* 10 30 0020 10/25/08 12:40:05*
* 10 30 0030 10/25/08 12:40:05*
* 10 30 0040 10/25/08 12:40:05*
* 10 30 0050 10/25/08 12:40:05*
* 10 3A 0010 10/25/08 12:40:05*
* C900 2830 10/25/08 12:40:05*
Disclaimer: Vision Solutions makes every effort to provide accurate system management information and programming code; however the company cannot be held liable for the accuracy of information nor its compatibility in your own environment. Please review and test thoroughly before implementing. © Copyright 2009, Vision Solutions, Inc. All rights reserved. IBM, System i, iSeries, i5/OS and AS/400 are trademarks of International Business Machines Corporation. All other brands are property of their respective registered owners.
2/15/09 Quickly see every physical and logical file on a system
Display the file QSYS/QADBXREF
Caution: Never change anything in this file!
Disclaimer: Vision Solutions makes every effort to provide accurate system management information and programming code; however the company cannot be held liable for the accuracy of information nor its compatibility in your own environment. Please review and test thoroughly before implementing. © Copyright 2009, Vision Solutions, Inc. All rights reserved. IBM, System i, iSeries, i5/OS and AS/400 are trademarks of International Business Machines Corporation. All other brands are property of their respective registered owners.
2/05/09 How to quickly delete multiple unsaved journal receivers
If you need to delete several journal receivers that have not been saved there are several ways to go about it.
If you use OPTION 4 from PDM or WRKOBJ screens you will receive an *INQUIRY message for each unsaved receiver telling you that is has not been saved and asking you to Ignore or Cancel. Deleting the receiver from within the WRKJRNA display will give you the same messages.
There is a quicker way.
From the command line enter
DLTJRNRCV JRNRCV(receiverlib/receivername) DLTOPT(*IGNINQMSG)
The DLTOPT(*IGNINQMSG) parameter will suppress the messages.
Note: You can enter a generic for the receiver name.
Disclaimer: Vision Solutions makes every effort to provide accurate system management information and programming code; however the company cannot be held liable for the accuracy of information nor its compatibility in your own environment. Please review and test thoroughly before implementing. © Copyright 2009, Vision Solutions, Inc. All rights reserved. IBM, System i, iSeries, i5/OS and AS/400 are trademarks of International Business Machines Corporation. All other brands are property of their respective registered owners.
01/28/09 How to change the object ownership of all objects in a library
The CHGOBJOWN command doesn't accept *ALL as an object name, but you can use a "UNIX-like" approach to the problem through the IFS representation of the i5/OS libraries:
CHGOWN OBJ('QSYS.LIB/yourlib.LIB/*.*') NEWOWN(newuser)
Disclaimer: Vision Solutions makes every effort to provide accurate system management information and programming code; however the company cannot be held liable for the accuracy of information nor its compatibility in your own environment. Please review and test thoroughly before implementing. © Copyright 2009, Vision Solutions, Inc. All rights reserved. IBM, System i, iSeries, i5/OS and AS/400 are trademarks of International Business Machines Corporation. All other brands are property of their respective registered owners.
