MPE and the Year 2028 (Y2028)

​

Much has been written about the MPE Year 2028 (Y2028) issue, with some comparing it to “Y2K revisited.” While there are similarities, the impact of Y2028 is far less severe than Y2K. Your HP 3000 system will not crash when the date rolls over to January 1, 2028. However, it will report the system date as January 1, 1900, which can lead to significant application and operational issues.

 

Addressing Y2028 requires a two-part approach:

​

1. Operating System Patch
The MPE operating system must be patched to correctly handle dates beyond December 31, 2027. LCI’s longtime partner, Beechglen Development, provides a solution for this. 

More information about their solution can be found here:  Beechglen 2028 Solution

 

2. Application Remediation
Applications that rely on the HP calendar must also be reviewed and, if necessary, modified. This is where LCI can assist. We offer application support and Y2028 remediation services to ensure your systems continue to operate smoothly before, during, and after the transition.

 

Our services include:

​

• Reviewing and modifying application code

• Assisting with testing and implementation planning

• Providing solutions even when source code is unavailable

 

Third-party tools such as BRW, PowerHouse, and others may also be affected, depending on how they are used. We can help ensure these tools continue to function properly after the date transition.

 

Doug Werth of Beechglen Development has published an excellent detailed technical explanation of the issue, available here: Beechglen 2028 Explanation

 

Additionally, longtime partner Adager has certified its software as Y2028 compliant, ensuring continued reliability. Adager remains an essential tool for managing, repairing, and optimizing IMAGE databases on the HP 3000.  Adager can be found here: Adager

​

Contact us to discuss your environment and ensure you’re prepared for Y2028.