This chapter contains these topics:
JD Edwards World highly recommends that you always upgrade your software in an alternate (test) environment before you upgrade your production environment. This benefits you in the following ways:
Allows users to test the upgraded JD Edwards World software with copies of your data files. When you are satisfied with the testing, you can then upgrade your production environment.
Users can be trained in the alternate environment while continuing your daily processing in the production environment.
Modified or custom programs can be updated and tested in the alternate environment to verify they work with the upgraded software.
Timings from file conversions in the alternate environment will help you plan for upgrading the production environment.
The procedures in this publication guide you through upgrading an alternate environment and then using the alternate to upgrade your production environment.
Note:
Before setting up the Alternate Environment, make sure you have performed the instructions in the A9.3 Update 1 Quick Installation Guide.The libraries that exist in the alternate environment before you start the A9.3 Update 1 upgrade are full copies of your A9.3 production libraries. This includes JDFDATA, JDFOBJ, JDFSRC, data, control, and security files libraries. You must restore the libraries from a backup tape.
The upgrade process does not allow duplicate files to exist in the customer data libraries defined in an upgrade plan (control, data, and security files). In preparation for the upgrade in the alternate environment, remove duplicate files from the appropriate library. The validation process of the upgrade identifies any remaining duplicate files and produces a report. Any duplicate files on the report need to be cleaned up before initiating the upgrade. Evaluate the number of records in each duplicate file and note that the system updates the first file in the library list before removing a duplicate file. The file that is going to be deleted must not contain any records needed for processing.
To avoid problems when you use or upgrade JD Edwards World software, make sure specific sets of control files and their associated logical files are together in the same library on your machine. For a list of the control files, see Appendix A, "Control File Dependencies."
You will need to apply manual changes to the JD Edwards World control files (for example, data dictionary, menus, DREAM Writer, and so on) as part of the upgrade process. If you can follow one of the three methods below, you will need to perform most of the changes only once. If not, you will need to apply all manual changes twice (to the alternate environment, and then to the production environment).
Apply all changes made to the JD Edwards World production control files and the alternate environment. Synchronize the files in both places. For a list of control files, refer to the Control File Changes Monitored chart in Section 6.5, "Update Your Applications."
Note:
If you use system 12 (Fixed Assets) or system 83 (FASTR) and plan to monitor the changes to DREAM Writer, you must use the dual maintenance method to monitor your changes and maintain your STAR and FASTR versions in both the production and alternate environments. When you upgrade your production environment in Phase Six, you need to copy these system files along with the DREAM Writer files. For more information, see the Note in the Section 6.5, "Update Your Applications."Do not allow users to change JD Edwards World production control files between the time you create the alternate environment and the time you upgrade the production environment.
Make note of all changes made to JD Edwards World production control files after you create the alternate environment, and then apply the same changes to the alternate environment.
You can use Data Base Audit Manager to track changes made to control files. For more information, refer to the JD Edwards World Database Audit Manager Guide
The instructions in this section should be performed in your production environment. In the next Phase, you will back up and restore the libraries from your A9.3 production environment to set up your A9.3 Update 1 alternate (test) environment.
Note:
If your production environment is NOT A9.3, perform the Pre-Upgrade Application and Technical Instructions in your A9.3 alternate (test) environment.Note:
As of A9.3, J98INIT as the Initial Program on the IBM profile is obsolete. Only J98INITA is supported for A9.3 and above.Run all standard integrity reports to ensure that all critical files are in balance before starting the upgrade.
The F04571, F04572, and F04573 files will be cleared in your data library as part of the upgrade process. If you have open payment groups, you need to use the Undo key to remove payments that cannot be completed before the upgrade.
If you have Custom menus that begin with 'G', you need to have them coded to systems 55-59.
All Invoice Generation and Journal Generation processes should be completed before starting the upgrade process. By completing these processes the F48910 and F48911 work files will be empty.
If you have used Database Audit Manager to attach triggers to files in your production environment, you must deactivate the triggers in your production environment before you save the copy of the production data libraries which you will restore in Phase Two to set up the alternate environment.
Access menu G946 option 4 and verify if any files have the Status *ACTIVE, if yes, then enter a 5 in front of each file listed to turn the trigger off. If you have Option 7, Deactivate All Configurations, on menu G946, you can use this option.
Note:
Triggers cannot be turned off or on if the file is locked.If you have triggers attached to other files, they must also be removed before saving the production libraries. To identify files with triggers attached, use the PRTTRGPGM command to produce a report. Use the RMVPFTRG command to remove triggers from the files.
Step 2 of the upgrade process will halt if triggers are attached to files and you will need to remove the triggers in the alternate environment before continuing with file conversion.
After the production data libraries are saved you can reactivate the Database Audit Manager triggers in the production environment (menu G946 option 8). For other triggers you removed, use the results from the PRTTRGPGM report and then ADDPFTRG command or whatever method you use to add the triggers back to the production files.