Вот по этому адресу: https://www-304.ibm.com/support/docview.wss?uid=swg21474380 Раньше распологалась статья о Hot-fix'ах, теперь ее нет.
Поэтому привожу не только ссылку, на случай, если она появится, но и саму статью
General FAQs about Hot-fixes Technote (FAQ) РаньшеQuestionsQ1 : What is a Hot-fix ?
Q2 : What kind of fixes are included in the Hot-fix and which versions of Hot-fixes are provided?
Q3 : How can you determine if any Hot-fix is installed on your environment or not ? Which level of Hot-fix is installed ?
Q4 : Hot-fix process
A1 : What is a Hot-fix ?
A Hotfix is a group of fixes for critical issues that have been repaired since the product's most recent fixpack / patch was released.
There are two types of Hot-fixes.
1) Cumulative Hotfixes: This includes the fixes for all issues that have been resolved since the product's most recent fix pack / patch was released.
We strongly recommend clients to apply "Cumulative Hot-fixes" as a standard deliverable from IBM.
2) One-Off Hot-fixes: This includes a single fix for a specific issue. It is not a standard deliverable from IBM.
In order to obtain a One-Off Hot-fix,clients need to provide the business impact about precisely how this issue affects your daily business operations. Once your business impact is accepted by IBM from an importance and urgency perspective, IBM will provide a One-Off Hotfix.
However, clients need to acknowlege the potential risk of One-Off Hotfixes. Please refer to the information below:
<< Prior to delivering your product update, IBM is providing notice that a "One-Off" hot-fix is not a standard deliverable from IBM Support & Development. Unlike formal FixPacks, and to a certain degree,
cumulative hot-fixes, one-off hot fixes do not undergo a full testing and validation effort. Although the one-off fix is designed to correct a specific reported defect or issue, the nature of this type of update can introduce unrelated problems. It is the responsibility of the customer to perform thorough testing effort in their environment. Fixes delivered in this capacity can also cause supportability issues in the future for the customer as well as IBM Support and Development. These issues include, but not limited to, latency on turn around time for future fix deliverables as well as root cause analysis of potential future reported problems. IBM Support recommends that the customer obtain fixes through the standard FixPack delivery method. If a customer's business needs cannot accommodate a FixPack, then the next
favourable correction should be applied and contained in a cumulative hot-fix. If a hot-fix cannot be applied
and a one-off fix is requested, customers must acknowledge the potential immediate and future risk in
implementing a singular fix. >>
A2 : What kind of fixes are included in the Hot-fix and which versions of Hot-fixes are provided?
Whenever a Hot-fix file is provided, you can find the readme file which includes the information about how to install the Hot-fix and which specific issues are addressed in this Hot-fix.
The Hot-fix Version and the date of the Hot-fix Build will also be provided.
This is one example of a 7116 Hot-fix readme file.
Hotfix version : 007
Build Date : March 10, 2010
A3 : How can you determine if any Hot-fix is installed on your environment or not ? Which level of Hot-fix is installed ?
In order to get the correct Hot-fix for your environment, you need to know if any Hot-fix has previously been applied to your environment.
Please get your exact version information thus:
- Log into Maximo / Go to StartCenter /Help /System Information.
If a Hot-fix has been applied, Base Services 18.104.22.168 version includes 'LA' word.
It means that the version information has its own format to indicate if a Hot-fix has been applied or not.
If the version includes LAYYYYMMDD ( ex. LA2011018), it means that a Hot-fix was applied.
A4 : Hot-fix process
1. If you meet any issue on your environment, please provide the exact version and steps to replicate, etc.
2. Tivoli Support will try to replicate this issue or check if there is any known issue.
3. If Support finds out if this is a known issue or this can be considered as a bug, an existing or a new APAR will be referenced.
4. The Hot-fix requested will be submitted to the IBM Maximo Development team.
5. The IBM Maximo Development team will check if this issue can be considered as bug. If so, they will fix the problem in the latest Hot-fix level on the same version as the client's.
6. After QA process, the formal Hot-fix will be released.
Hot-fix files have a naming format . "MBS"_BS Version_"LAFIX."Date Of Release"
7. Maximo Support will send the Hot-fix file to the client.
8. Before applying the Hot-fix into the production system, Maximo Support strongly recommend you to test in a non-Production environment first.