End Of Support for EOS 7.6

If IBM follow past practice then version 7.6 specific technotes will be removed from the technote database.

If you have “saved” this page on your computer as a HTML file then you are likely to find that the content is no longer there after the article is removed from the server.

It appears that the saved page checks the main IBM website to retrieve its contents and the page will fail to display properly once the page has gone

How can you prepare?

Visit the technotes that you use regularly and print them to a file and store the files. I print them off to PDF format and keep them in case the technotes disappear.

Technotes can disappear even when a version is supported although this is rare.

Download the latest fix packs for your version. When 7.1 went EOS some fix packs were removed in just before the EOS date so don’t wait until the last minute.

What will EOS actually mean when it happens?

• Maximo installations will carry on working even though the EOS date has passed. Cohesive companies have supported customers running on systems that were unsupported versions.
• Purely 7.6 related support materials will be removed from the IBM website
• IBM will not accept new PMRs for 7.6 components
• From past experience the latest 7.6 version files should be available on the IBM fix central site for customers with active support agreements - these will only be available for the purpose of upgrading to MAS
• Existing license agreements will still be valid e.g. customers are not allowed to decompile / recompile the IBM code

Moving to MAS

The MAS software delivers a lot of additional features / capabilities - Cohesive have experts who can help you upgrade to use the new features

This blog series

This article is one of a series of articles to help system administrators understand the Maximo logs and the underlying architecture.

If you like this article then please share or like it.

Whilst I support the wider Maximo community and encourage the spread of knowledge, when republishing content from this blog please include the originating author along with the article or parts of.

If people do find parts of this blog coming up in blogs/newsletters/communications then please contact me directly. I’m happy to connect on LinkedIn to discuss.

Disclaimer

The postings on this blog are my own and don't necessarily represent Cohesive's positions, strategies or opinions.

The materials on this site are provided "AS IS" and the author will not be liable for any direct, indirect or incidental damages arising out or relating to any use or distribution of them. Readers are advised to test any changes/recommendations thoroughly before use