--- Maximo Base Services Release 7.1.1.1 Hot Fixes A Hot Fix is a group of critical issues that have been repaired since the product patch was released. The Hot Fix is cumulative and may contain other fixes in addition to the issue(s) that affect your site. The Hot Fix must be applied in full in order to be supportable. Customers should validate this Hot Fix in a test environment prior to rolling it out to a production environment. Hot Fixes by their very nature do not go through a full quality assurance cycle and may or may not be included in the latest available program patch. The recommended steps for applying the Hot Fix are as follows: 1. Ensure that no database configuration changes are pending 2. Shutdown the MAXIMO application server 3. Backup the database 4. Make a copy of the Maximo directory 5. Unzip the files into the MAXIMO root folder, selecting the Overwrite existing files and the Use folder names options 6. Run the database scripts using runscriptfile.bat (The runscriptfile tool will employ the correct extension for your database platform.) Note that some of the scripts require that you run Database Configuration before continuing with the next script. You do not need to rerun scripts that were run when you applied an earlier Hot Fix. 1. Copy all scripts from hotfix_scripts\HF*.* into the following directory: a. C:\\tools\maximo\en\script 2. Open a DOS prompt: a. cd \\tools\maximo\internal b. runscriptfile -fHF_001 c. runscriptfile -fHF_002 d. runscriptfile -fHF_003 e. runscriptfile ... for each HF script in the folder. 3. If errors, check log: a. cd \\tools\maximo\log b. Mxserver_RUNSCRIPT…log 7. Apply any manual updates listed in the readme.txt file. These can be found by searching for the value 'Comments:' 8. Run Database Configuration (ConfigDB.bat) to apply any changes to the database 9. Delete the application server cache, for example: WebLogic - c:\bea\user_projects\domains\mydomain\MAXIMOSERVER\.wlnotdelete WebSphere - c:\IBM\WebSphere\AppServer\profiles\Custom01\temp\Node01\MAXIMOSERVER 10. Rebuild and redeploy the EAR files and then restart the application server Please retest the problem scenario. --- Date: 07/29/2008 APAR(s): IZ27040 Issue(s): 08-18620 Description: THE EXPECTED LIST OF ITEMS TO BE REORDERED DOES NOT POP UP AFTER CLICKING THE PREVIEW BUTTON. --- Date: 08/12/2008 APAR(s): IZ28090, IZ28100 Issue(s): 08-19066, 08-19068 Description: The Required Date on a Reservation was the creation date, not the Required Date of the associated WPMaterial (Planned Material) record, as desired; issue 08-19066 (APAR IZ28090) fixes this. Issue 08-19068 (APAR IZ28100) was to change things so that when the Required Date of a WPMaterial (Planned Material) record is changed, the Required Date of the associated Reservation is also changed. The fix for issue 08-19066 accomplished this as well. --- Date: 09/08/2008 APAR(s): n/a Issue(s): 08-20493 Description: Customers who upgraded on SqlServer platform may have rows in condition with conditionid = 0. Run HF7111_001 using runscriptfile to fix this data. --- Date: 09/17/2008 APAR(s): IZ30269 Issue(s): 08-20514 Description: DIRECT PRINT NOT WORKING BIRT MAXIMO 7 Browser JRE version related problem is solved by this issue. But 08-21515 hotfix is also required to solve the issue fully. Deployment Instructions : This issue has changes to applet code and new jar files. So it important to make sure the Client Browser cache is cleared up to make sure older applet code instances are not present. This is important for the hotfixed applet and the support classes to take into effect. --- Date: 09/18/2008 APAR(s): IZ32596 Issue(s): 08-21779 Description: IN THE SELECT DATE AND TIME DIALOG-BOX, MAXIMO JUMPS THE HOUR DIRECTLY FROM 11 TO 01 --- Date: 09/24/2008 APAR(s): IZ31200 Issue(s): 08-21126 Description: Error message when Resync used in WFDesign. --- Date: 08/26/2008 APAR #: IZ30028,IZ35589 Issue(s): 08-20381,08-23468 Description: When you add a new sigoption to a field and do not grant access to that option .. you will still see the field and you should not. CONDITIONAL PROPERTIES NOT SHOWING IN APPLICATION DESIGNER DESPITE BEING SET --- Date: 11/18/2008 APAR(s): IZ28717 Issue(s): 08-19506 Description: Fixed the unique key check error when classifying a service request with a new classification that has the same attributes as those of the existing classification on the SR. --- Date: 11/26/2008 APAR(s): IZ38495 Issue(s): 08-24919 Description: Fixed the issue with importing reports that are exported using the exportReport command in a multi-language environment. The export operation is generating an xml file that contained all the localized properties entries and the import tools is including them behind the scenes and when it tries to add the localized properties as resources, it results in duplicate entry error. The issue is addressed by checking whether the resource is already added or not in the import tool. --- Date: 12/01/2008 APAR(s): IZ38341 Issue(s): 08-24850 Description: When duplicating a workorder with a hierarchy, the tasks from the Activity/Jobplan are visible on the new workorder before saving the record. --- Date: 12/03/2008 APAR(s): I239092 Issue(s): 08-25270 Description: PROBLEM WITH THE ROUTE WORKFLOW BUTTON NOT BEING DISPLAYED ON THE TOOLBAR IN GERMAN ENVIRONMENT 7.1.1.1 --- Date: 12/03/2008 APAR(s): IZ38969 Issue(s): 08-25165 Description: WORKFLOW ADMINISTRATION: UNABLE TO STOP ANY WORFKLOW PROCESS IN THE LIST TAB AFTER SORTING THE LIST OF ACTIVE PROCESSES. --- Date: 01/06/2008 APAR #: IZ39641 Issue(s): 08-25527 Description: MAKING MEASURE UNIT OPTIONAL FOR RECON COMPARISON RULES. --- Date: 09/11/2009 APAR #: IZ54640 Issue(s): 09-15856 Description: ASSET ASSEMBLY CAN BE MODIFIED EVEN WHEN EITHER THE PARENT OR THE CHILD IS IN A STOREROOM. --- Date: 09/28/2009 APAR #: IZ54568 Issue(s): 09-15778 Description: SESSION DOESN'T GET REMOVED FROM MAXSESSION TABLE FOR INACTIVE USER --- Date: 10/28/2009 APAR #: IZ35631 Issue(s): 08-23473 Description: UNABLE TO CHANGE DEFAULT QUERY AFTER ENTERING APP RESTRICTION --- Date: 11/30/2009 APAR #: IZ40726 Issue(s): 08-25708 Description: DEFAULT VALUE DOES NOT WORK ON CHILD TABLE --- # # FOOTER - DO NOT DELETE - # # Notes to developers updating this file: # # This file may be sent to customers. # # The only files that need to be listed here are the ones that are used for DB scripts. # # Other files used for the fixes need not be listed here. # # For consistency follow the format exactly for each entry.