TAAV6R1 Upgrading to the System V6R1 Release

Upgrading to System Release V6R1M0
The AS/400 - System i V6R1 release requires that programs contain 'creation data' necessary to re-create the program when the operating system is installed. See the more detailed later discussion of this requirement. Not all versions of the TAA Productivity Tools product meet this criteria. Other vendor and user programs may also not meet this criteria. This document is divided into 4 sections: - Checking the TAA Productivity Product - Checking your programs and vendor programs - Options for V5R3 users of the TAA Productivity Tools - Installing the fix for the TAA Productivity Tools (use only if directed) If you need to contact the TAA Productivity Tools owner, call 914-251-9494 or send an E-mail from the www.taatool.com web site. Checking the TAA Productivity Tools Product ------------------------------------------- ------------------------------------------- Begin by checking the Operating System release of your system: DSPOBJD OBJ(QCMD) OBJTYPE(*PGM) DETAIL(*SERVICE) ** The 'System level' describes your release. If you are at V5R4, you will be able to use the TAA tools when you install the Operating System for V6R1. You will have 60 days from the time the System i V6R1 version is installed to get a compatible version of the TAA Productivity Tools. No further action is needed. ** If your 'System Level' is V5R2 or earlier, you will not be able to install the V6R1 level of the Operating system. You must be at V5R3 or later. You should also get a Jan 1, 2008 or later version of the TAA Productivity tools for V5R3. Once these are installed, you may upgrade to the system V6R1 version and the TAA Productivity Tools will be operational. You will have 60 days from the time the system V6R1 release is installed to get a compatible version of the TAA Productivity Tools. ** If your system level is V5R3, you must check the version date of the TAA Productivity Tools. DSPDTAARA DTAARA(TAATOOL/TAACTL) Rollup to offset 450. If the date of your version is Sept 15, 2007 or later, you do not need the V5R3 fix. Your version of the tools will operate on the system V6R1 release. You will have 60 days from the time the system V6R1 release is installed to get a compatible version of the TAA Productivity Tools. No further action is needed. However, you will need the Jan 1, 2008 version or later to run the most current changes for CHKMINRLS (described in the next section). If your TAA version is prior to Sept 15, 2007, you must do something to make the TAA Productivity Tools product operational when the system V6R1 release is installed. See the section on 'Options for V5R3 Users of the TAA Productivity Tools'. Checking your programs and vendor programs ------------------------------------------ ------------------------------------------ When you install the system V6R1M0 version, any program type object (*PGM, *MODULE, *SRVPGM, and *SQLPKG) must be re-created from 'creation data' to the V6R1M0 version of the object code. All program type objects created on or after V5R1M0 always have creation data. Using the CHGPGM/CHGMOD/CHGSRVPGM RMVOBS parameter typically removes the debug capability of a program, but retains the creation information that will allow the system to re-create the program. For example, CHGPGM RMVOBS(*ALL) will remove the debug capability, but retains 'creation data'. The system does not allow 'creation data' to be removed by a CHG command. Re-creation will happen automatically at the time of install and no user action is required. Any program type object that was created prior to V5R1 and does not have 'creation data' must be re-created on your current release before attempting to restore V6R1M0. You can check individual objects with the following commands. ** DSPPGM. For OPM programs, the line for 'Observable information' must be *ALL or *UNOBS to allow re-creation. It must not be *NONE. For ILE programs, rollup to the second page. The line for 'All Creation data' must be *YES or *UNOBS to allow re-creation. It must not be *NO. ** DSPMOD. The line for 'Creation data' must be *ALL or *UNOBS to allow re-creation. It must not be *NO. ** DSPSRVPGM. Rollup to the second page. The line for 'All creation data' must be *ALL or *UNOBS to allow re-creation. It must not be *NO. The system has an ANZOBJCVN command that can be acquired via PTF if it is not already on your system. A RedBook describes what conversion is required and the use of ANZOBJCVN. A PDF of the RedBook is available at: http://www.redbooks.ibm.com/redpieces/pdfs/red4293.pdf The TAA Productivity Tools also support the CHKMINRLS and FIXMINRLS commands that allow you to determine what programs will cause a problem and to fix those that have the source used to create the objects. These commands are available as of the Sept 1, 2007 version, but an important fix for ILE programs was added in the Jan 1, 2008 version. You may run CHKMINRLS by library or against all user libraries. If you have IASPs, they should be varied online. If you run against all user libraries, you would normally submit the following command: CHKMINRLS LIB(*ALLUSR) MINRLS(V5R1M0) BYPCRTDTA(*YES) The objects that will not convert properly to V6R1 will be flagged. Additional flagging occurs for those objects that do not have source where the objects were originally created from. All *SQLPKG objects are flagged and you must consider them individually. If many of your objects that will not convert properly still have the source in the same member that created the object, the FIXMINRLS command can be run. If you have IASPs, they should be varied online. FIXMINRLS LIB(xxx) MINRLS(V5R1M0) BYPCRTDTA(*YES) This will attempt to re-create the required objects. Running the command by library rather than LIB(*ALLUSR) may be desirable to help control the process. The internal TAA RPLxxx commands will access the file/libraries that are used in the objects and temporarily add the libraries to the library list before re-creating the objects. Objects without source or those that cannot be re-created will be flagged. Neither CHKMINRLS or FIXMINRLS will report on objects in the TAATOOL library as all objects are ready. CHKMINRLS may be used as often as necessary to ensure that all objects are ready. Options for V5R3 Users of the TAA Productivity Tools ---------------------------------------------------- ---------------------------------------------------- Not every user of the TAA Productivity Tools needs to consider this section. Be sure you have been directed here by the section on 'Checking the TAA Productivity Tools product'. Three options exist for upgrading your V5R3 version of the TAA Productivity Tools to allow objects to be re-created when you install the system V6R1 version. - Install a current TAA V5R3 version (Sept 15, 2007 or later) - Install a TAA version of V6R1 - Install the fix required for early V5R3 versions ** Install a current TAA V5R3 version. You could install a TAA Version of V5R3 dated Sept 15, 2007 or later while still on the system V5R3 release and before installing the V6R1 system release. This will provide you with new tools, fixes, and enhancements. There is a media charge of $30. This will avoid additional considerations when attempting to become operational on the new system release and avoid dealing with the 'fix' instructions. Installing the Jan 1, 2008 version (or later) will also allow you to run the CHKMINRLS/FIXMINRLS commands to assist in finding and re-creating your objects that will require action (this includes an important fix for ILE programs). After you install the system V6R1 version, you will have 60 days to get a V6R1 version of the TAA Productivity Tools. ** Install a V6R1 version of the TAA Productivity Tools at the same time you install the Operating System V6R1 release. You must have ordered the TAA version ahead of time so that it is available when you need it. Note that this technique will not work if you have TAA commands in your IPL startup program (system value QSTRUPPGM). ** Install the V5R3 fix either before or after installing the V6R1 system release. The fix must be on your system before attempting to run a TAA Tool on the system V6R1 release. Note that you can install the fix while you are still on the system V5R3 release. Installing the fix after installing the system release will not work if you have TAA commands in your IPL startup program. Installing the fix for the TAA Productivity Tools ------------------------------------------------- ------------------------------------------------- These instructions describe how to install the fix for TAA Productivity Tools product for a V5R3 version prior to Sept 15, 2007. This is required for operating the tools on the V6R1M0 version of the system. Not every user of the TAA Productivity Tools needs to consider this section. Be sure you have been directed to this by the section on 'Checking the TAA Productivity Tools product' and have considered the other choices in the section on 'Options for V5R3 Users of the TAA Productivity Tools'. If you are not sure you have installed the fix, enter TAATOOL/CHKV5R3 If the command does not exist, you have not installed the fix nor the Sept 15, 2007 (or later) version of the TAA Productivity Tools. If the command exists, a message will describe that the tools will be operational if you install the V6R1M0 system release. The fix was prepared by placing objects in library TAAV5R3FIX, the library was saved to a save file, and then copied to the PF528 stream file. Processing the fix from an E-mail attachment -------------------------------------------- If you receive the fix via E-mail, the stream file was attached. The easiest solution to handle the fix is: ** Save the attachment to your home directory. If you are not sure you have a home directory, see the later section on 'Home Directory'. ** Ensure the TAAV5R3FIX library does not exist. DSPLIB LIB(TAAV5R3FIX) You should see the message that the library does not exist. The library will be created in a later step. ** Use the TAA RSTTAASTMF command to copy the stream file and restore library TAAV5R3FIX. RSTTAASTMF DIR('/home/xxx') SAVLIB(TAAV5R3FIX) Where xxx is typically your user profile name. ** While the fix program can normally be called at any time, it is best done when no one is using the TAA Productivity Tools. ** Ensure you are signed on as an *ALLOBJ special authority user. ** Call the fix program which will typically run in less than 5 seconds. CALL PGM(TAAV5R3FIX/TAAV5R3FIX) You should see a completion message describing that the fix has been installed. ** To ensure the fix is working, enter: CHKV5R3 You should see a completion describing that the TAA Productivity Tools will be operational when V6R1 is installed. Processing the fix from a download ---------------------------------- To receive the fix from a download from the TAATOOL.COM web site, do: ** Browse to http:/www.taatool.com/TAAV5R3FIX.SAVF.exe If you are given the choice of whether to save/copy the file to disk or execute it, choose save/copy. Do either of the following: -- Place the file on your PCs hard drive and then copy it to the IFS of your System i. -- If you have a network drive mapped to your System i, then simply save it directly to your "home" directory. If you are not sure you have a home directory, see the later section on 'Home Directory'. ** Use the TAA RSTTAASTMF command to copy the stream file and restore library TAAV5R3FIX. RSTTAASTMF DIR('/home/xxx') SAVLIB(TAAV5R3FIX) FROMSTMF('/TAAV5R3FIX.SAVF.exe') Where xxx is typically your user profile name. ** While the fix program can normally be called at any time, it is best done when no one is using the TAA Productivity Tools. ** Ensure you are signed on as an *ALLOBJ special authority user. ** Call the fix program which will typically run in less than 5 seconds. CALL PGM(TAAV5R3FIX/TAAV5R3FIX) You should see a completion message describing that the fix has been installed. ** To ensure the fix is working, enter: CHKV5R3 You should see a completion describing that the TAA Productivity Tools will be operational when V6R1 is installed. Home Directory -------------- ** When a user profile is created, the default is to use a value of '/home/xxx' as a home directory where xxx is the same name as the user profile. Use DSPUSRPRF to determine your home directory: DSPUSRPRF USRPRF(xxx) where xxx is your user profile name. Rollup to the last page and check your home directory name. ** While the user profile may refer to a home directory, it does not mean that a home directory exists. Use WRKLNK to see if a home directory exists in the IFS. The following assumes that your home directory is '/home/xxx' where xxx is your user profile name. WRKLNK OBJ('/home/xxx') If you do not have a home directory, you may create one with the MKDIR command. The following assumes your user profile home directory will be '/home/xxx' where xxx is your user profile name: MKDIR OBJ('/home/xxx')


Upgrading to System Release V6R1M0
The AS/400 - System i V6R1 release requires that programs contain 'creation data' necessary to re-create the program when the operating system is installed. See the more detailed later discussion of this requirement. Not all versions of the TAA Productivity Tools product meet this criteria. Other vendor and user programs may also not meet this criteria. This document is divided into 4 sections: - Checking the TAA Productivity Product - Checking your programs and vendor programs - Options for V5R3 users of the TAA Productivity Tools - Installing the fix for the TAA Productivity Tools (use only if directed) If you need to contact the TAA Productivity Tools owner, call 914-251-9494 or send an E-mail from the www.taatool.com web site. Checking the TAA Productivity Tools Product ------------------------------------------- ------------------------------------------- Begin by checking the Operating System release of your system: DSPOBJD OBJ(QCMD) OBJTYPE(PGM) DETAIL(SERVICE) The 'System level' describes your release. If you are at V5R4, you will be able to use the TAA tools when you install the Operating System for V6R1. You will have 60 days from the time the System i V6R1 version is installed to get a compatible version of the TAA Productivity Tools. No further action is needed. If your 'System Level' is V5R2 or earlier, you will not be able to install the V6R1 level of the Operating system. You must be at V5R3 or later. You should also get a Jan 1, 2008 or later version of the TAA Productivity tools for V5R3. Once these are installed, you may upgrade to the system V6R1 version and the TAA Productivity Tools will be operational. You will have 60 days from the time the system V6R1 release is installed to get a compatible version of the TAA Productivity Tools. ** If your system level is V5R3, you must check the version date of the TAA Productivity Tools. DSPDTAARA DTAARA(TAATOOL/TAACTL) Rollup to offset 450. If the date of your version is Sept 15, 2007 or later, you do not need the V5R3 fix. Your version of the tools will operate on the system V6R1 release. You will have 60 days from the time the system V6R1 release is installed to get a compatible version of the TAA Productivity Tools. No further action is needed. However, you will need the Jan 1, 2008 version or later to run the most current changes for CHKMINRLS (described in the next section). If your TAA version is prior to Sept 15, 2007, you must do something to make the TAA Productivity Tools product operational when the system V6R1 release is installed. See the section on 'Options for V5R3 Users of the TAA Productivity Tools'. Checking your programs and vendor programs ------------------------------------------ ------------------------------------------ When you install the system V6R1M0 version, any program type object (PGM, MODULE, SRVPGM, and SQLPKG) must be re-created from 'creation data' to the V6R1M0 version of the object code. All program type objects created on or after V5R1M0 always have creation data. Using the CHGPGM/CHGMOD/CHGSRVPGM RMVOBS parameter typically removes the debug capability of a program, but retains the creation information that will allow the system to re-create the program. For example, CHGPGM RMVOBS(ALL) will remove the debug capability, but retains 'creation data'. The system does not allow 'creation data' to be removed by a CHG command. Re-creation will happen automatically at the time of install and no user action is required. Any program type object that was created prior to V5R1 and does not have 'creation data' must be re-created on your current release before attempting to restore V6R1M0. You can check individual objects with the following commands. * DSPPGM. For OPM programs, the line for 'Observable information' must be ALL or UNOBS to allow re-creation. It must not be NONE. For ILE programs, rollup to the second page. The line for 'All Creation data' must be YES or UNOBS to allow re-creation. It must not be NO. ** DSPMOD. The line for 'Creation data' must be ALL or UNOBS to allow re-creation. It must not be NO. * DSPSRVPGM. Rollup to the second page. The line for 'All creation data' must be ALL or UNOBS to allow re-creation. It must not be NO. The system has an ANZOBJCVN command that can be acquired via PTF if it is not already on your system. A RedBook describes what conversion is required and the use of ANZOBJCVN. A PDF of the RedBook is available at: http://www.redbooks.ibm.com/redpieces/pdfs/red4293.pdf The TAA Productivity Tools also support the CHKMINRLS and FIXMINRLS commands that allow you to determine what programs will cause a problem and to fix those that have the source used to create the objects. These commands are available as of the Sept 1, 2007 version, but an important fix for ILE programs was added in the Jan 1, 2008 version. You may run CHKMINRLS by library or against all user libraries. If you have IASPs, they should be varied online. If you run against all user libraries, you would normally submit the following command: CHKMINRLS LIB(ALLUSR) MINRLS(V5R1M0) BYPCRTDTA(YES) The objects that will not convert properly to V6R1 will be flagged. Additional flagging occurs for those objects that do not have source where the objects were originally created from. All SQLPKG objects are flagged and you must consider them individually. If many of your objects that will not convert properly still have the source in the same member that created the object, the FIXMINRLS command can be run. If you have IASPs, they should be varied online. FIXMINRLS LIB(xxx) MINRLS(V5R1M0) BYPCRTDTA(YES) This will attempt to re-create the required objects. Running the command by library rather than LIB(ALLUSR) may be desirable to help control the process. The internal TAA RPLxxx commands will access the file/libraries that are used in the objects and temporarily add the libraries to the library list before re-creating the objects. Objects without source or those that cannot be re-created will be flagged. Neither CHKMINRLS or FIXMINRLS will report on objects in the TAATOOL library as all objects are ready. CHKMINRLS may be used as often as necessary to ensure that all objects are ready. Options for V5R3 Users of the TAA Productivity Tools ---------------------------------------------------- ---------------------------------------------------- Not every user of the TAA Productivity Tools needs to consider this section. Be sure you have been directed here by the section on 'Checking the TAA Productivity Tools product'. Three options exist for upgrading your V5R3 version of the TAA Productivity Tools to allow objects to be re-created when you install the system V6R1 version. - Install a current TAA V5R3 version (Sept 15, 2007 or later) - Install a TAA version of V6R1 - Install the fix required for early V5R3 versions Install a current TAA V5R3 version. You could install a TAA Version of V5R3 dated Sept 15, 2007 or later while still on the system V5R3 release and before installing the V6R1 system release. This will provide you with new tools, fixes, and enhancements. There is a media charge of $30. This will avoid additional considerations when attempting to become operational on the new system release and avoid dealing with the 'fix' instructions. Installing the Jan 1, 2008 version (or later) will also allow you to run the CHKMINRLS/FIXMINRLS commands to assist in finding and re-creating your objects that will require action (this includes an important fix for ILE programs). After you install the system V6R1 version, you will have 60 days to get a V6R1 version of the TAA Productivity Tools. Install a V6R1 version of the TAA Productivity Tools at the same time you install the Operating System V6R1 release. You must have ordered the TAA version ahead of time so that it is available when you need it. Note that this technique will not work if you have TAA commands in your IPL startup program (system value QSTRUPPGM). Install the V5R3 fix either before or after installing the V6R1 system release. The fix must be on your system before attempting to run a TAA Tool on the system V6R1 release. Note that you can install the fix while you are still on the system V5R3 release. Installing the fix after installing the system release will not work if you have TAA commands in your IPL startup program. Installing the fix for the TAA Productivity Tools ------------------------------------------------- ------------------------------------------------- These instructions describe how to install the fix for TAA Productivity Tools product for a V5R3 version prior to Sept 15, 2007. This is required for operating the tools on the V6R1M0 version of the system. Not every user of the TAA Productivity Tools needs to consider this section. Be sure you have been directed to this by the section on 'Checking the TAA Productivity Tools product' and have considered the other choices in the section on 'Options for V5R3 Users of the TAA Productivity Tools'. If you are not sure you have installed the fix, enter TAATOOL/CHKV5R3 If the command does not exist, you have not installed the fix nor the Sept 15, 2007 (or later) version of the TAA Productivity Tools. If the command exists, a message will describe that the tools will be operational if you install the V6R1M0 system release. The fix was prepared by placing objects in library TAAV5R3FIX, the library was saved to a save file, and then copied to the PF528 stream file. Processing the fix from an E-mail attachment -------------------------------------------- If you receive the fix via E-mail, the stream file was attached. The easiest solution to handle the fix is: Save the attachment to your home directory. If you are not sure you have a home directory, see the later section on 'Home Directory'. Ensure the TAAV5R3FIX library does not exist. DSPLIB LIB(TAAV5R3FIX) You should see the message that the library does not exist. The library will be created in a later step. Use the TAA RSTTAASTMF command to copy the stream file and restore library TAAV5R3FIX. RSTTAASTMF DIR('/home/xxx') SAVLIB(TAAV5R3FIX) Where xxx is typically your user profile name. While the fix program can normally be called at any time, it is best done when no one is using the TAA Productivity Tools. Ensure you are signed on as an ALLOBJ special authority user. * Call the fix program which will typically run in less than 5 seconds. CALL PGM(TAAV5R3FIX/TAAV5R3FIX) You should see a completion message describing that the fix has been installed. To ensure the fix is working, enter: CHKV5R3 You should see a completion describing that the TAA Productivity Tools will be operational when V6R1 is installed. Processing the fix from a download ---------------------------------- To receive the fix from a download from the TAATOOL.COM web site, do: Browse to http:/www.taatool.com/TAAV5R3FIX.SAVF.exe If you are given the choice of whether to save/copy the file to disk or execute it, choose save/copy. Do either of the following: -- Place the file on your PCs hard drive and then copy it to the IFS of your System i. -- If you have a network drive mapped to your System i, then simply save it directly to your "home" directory. If you are not sure you have a home directory, see the later section on 'Home Directory'. Use the TAA RSTTAASTMF command to copy the stream file and restore library TAAV5R3FIX. RSTTAASTMF DIR('/home/xxx') SAVLIB(TAAV5R3FIX) FROMSTMF('/TAAV5R3FIX.SAVF.exe') Where xxx is typically your user profile name. While the fix program can normally be called at any time, it is best done when no one is using the TAA Productivity Tools. ** Ensure you are signed on as an ALLOBJ special authority user. * Call the fix program which will typically run in less than 5 seconds. CALL PGM(TAAV5R3FIX/TAAV5R3FIX) You should see a completion message describing that the fix has been installed. To ensure the fix is working, enter: CHKV5R3 You should see a completion describing that the TAA Productivity Tools will be operational when V6R1 is installed. Home Directory -------------- When a user profile is created, the default is to use a value of '/home/xxx' as a home directory where xxx is the same name as the user profile. Use DSPUSRPRF to determine your home directory: DSPUSRPRF USRPRF(xxx) where xxx is your user profile name. Rollup to the last page and check your home directory name. ** While the user profile may refer to a home directory, it does not mean that a home directory exists. Use WRKLNK to see if a home directory exists in the IFS. The following assumes that your home directory is '/home/xxx' where xxx is your user profile name. WRKLNK OBJ('/home/xxx') If you do not have a home directory, you may create one with the MKDIR command. The following assumes your user profile home directory will be '/home/xxx' where xxx is your user profile name: MKDIR OBJ('/home/xxx')

Added to TAA Productivity Tools January 1, 2008

Home Page

Last modified on June 2, 2008