How to keep QUSRTOOL up to date and avoid problems.
Brief: IBM continues to enhance the QUSRTOOL library by adding new tools and fixing bugs in existing tools. It's to your advantage to keep this library running well and updated with the latest tools.
The QUSRTOOL library is full of great tools that can benefit most any AS/400 site. The library is not officially supported by IBM, so getting new versions and correcting bugs is not something that happens automatically. Here is some important information that will help you manage this tool chest.
We'll start with how to report problems and obtain the latest version and finish with how to avoid common mistakes made when using the library. Whether you're just getting started with the QUSRTOOL library or you have been using it for years, keep it up to date and running smoothly by following these few simple suggestions.
Getting It Fixed
If you find bugs in QUSRTOOL, the correct procedure is to have your system engineer (SE) send a note explaining the problem to: QUSRTOOL at RCHASA04, which is a node in Rochester that controls QUSRTOOL. The node is also used for questions concerning QUSRTOOL as well as to request the update to QUSRTOOL.
One thing to remember is that the QUSRTOOL library is never changed by a PTF. Requesting updates is the only means of obtaining fixes during a release. The updates also contain enhancements and new tools, so it makes sense to get an update at least once per release. For example, the update dated August 25, 1993 has about 60 new tools that are not in the shipped version of the V2R2M0 release. You don't have to wait until the next release before ordering an update. If you order one now, you can start using the new tools right away. It is also a good idea to order an update every time you install a new release.
The update is a very informal process. There is no announcement of a new version, no guarantee there will ever be another one, and no automatic distribution. The update is shipped to SEs on 1/4-inch cartridge media. It is the local SE's responsibility to place the update on your favorite media.
Update installation is easy. You restore the library TAAUPD and then execute the following command:
This displays a menu of options (see 1). The best choice to take is Option 1 which installs the update and creates all of the tools. Because some of the tools require data files, you have to name a library where they should reside (see 2). This option submits a long-running batch job (there are lots of tools to create). It is recommended that you create all of the tools in order to avoid all of the prerequisite problems you might otherwise encounter. The whole process takes about 10 hours on a Model D02 or one hour on a Model F95. It's a good overnight job.
This displays a menu of options (see Figure 1). The best choice to take is Option 1 which installs the update and creates all of the tools. Because some of the tools require data files, you have to name a library where they should reside (see Figure 2). This option submits a long-running batch job (there are lots of tools to create). It is recommended that you create all of the tools in order to avoid all of the prerequisite problems you might otherwise encounter. The whole process takes about 10 hours on a Model D02 or one hour on a Model F95. It's a good overnight job.
Biggest Mistakes Users Make
There are three predictable mistakes that users of QUSRTOOL typically make. To keep you from encountering them, I've detailed what they are and suggested ways to avoid them.
1. Forgetting to unpackage the save files. In V2R2M0, the source files in QUSRTOOL (except for QATTINFO) are shipped in save files. This speeds up the install and saves space for those who are not interested in the tools. The first step is to convert the save files to normal source files (called "unpackaging"). To unpackage, run the following commands:
ADDLIBLE LIB(QUSRTOOL) SBMJOB CMD(CALL PGM(UNPACKAGE) + PARM('*ALL' 1)) RMVLIBLE LIB(QUSRTOOL)
2. Forgetting to recreate the CRTTAATOOL command on every release. The create process is driven from source-and there are source changes in every release. You need to recreate the CRTTAATOOL command to get the new changes in.
If you don't have the update, run the following commands:
CRTCLPGM PGM(TAATOOL/TAATOLAC) +
SBMJOB CMD(CALL +
Note: The batch job takes several minutes.
3. Forgetting that the objects only get fixed and enhanced by recreating. You need to recreate the tools on every release. It is important to recreate the dependencies (the tools used by the tool you are using) as well as the tool you are executing. The easiest solution is to create all of the tools every release. If you create all of the tools, you have to specify a library where certain data files will be placed to hold your data.
If you don't have the update, run the following command (it can take one to eight hours, depending on the model):
SBMJOB CMD(CRTTAATOOL TOOL(*ALL) + CRTFILLIB(xxx))
Jim Sloan is president of Jim Sloan Inc., a consulting company, and a retired IBMer. Jim wrote the TAA tools that exist in QUSRTOOL. He has been a speaker at COMMON and IBM AS/400 Technical Conferences for many years.
Tips for Managing the QUSRTOOL Library
Figure 1 TAAUPD Menu
TAAUPD Menu Select one of the following: 1. Install TAA updates and create all tools - Prompt 2. Display current TAATOOL update status 3. Print cover sheet for TAAUPD distribution 4. Initialize tape media - Prompt 5. Save TAAUPD library - Prompt 6. Display help text for the menu options 7. Display or print changes in the update - Prompt 8. Install update only - Prompt
Tips for Managing the QUSRTOOL Library
Figure 2 Option 1 of the TAAUPD MenuInstall and Create TAA Tools (INSCRTTAA) Library to create files in . . . Name Command library . . . . . . . . TAATOOL Name Job description . . . . . . . . *USRPRF Name, *USR Library name . . . . . . . . . *LIBL Name, *LIB Job queue . . . . . . . . . . . *JOBD Name, *JOB Library name . . . . . . . . . Name, *LIB Delay execution time in hours . 0 0-24