Identifying code that could fail the “2039 problem” [email protected] (Simon Hutchinson)

​[[{“value”:”As soon as we handled Y2K I thought when we reached date 2039 we would have something in place to prevent the “2039 problem”.
What is the “2039 problem”? This only occurs with dates with years that are just two characters. A date data type, character or numeric representation of a date, that has a two character year uses the following rule to determine the century:

40 – 99:  Century is assumed to be “19”
00 – 39:  The assumption is that the century is “20”

We are 24 years away from 2039, but soon there a going to be applications that will need to use dates beyond that year. When I attended COMMON’s Navigate in Toronto, in November 2024, Barbara Morris, IBM’s lead developer for the RPG compiler, told us that it would be up to us, the IBM i developers, to remedy the issue. The way RPG handles dates will remain unchanged.
Read more »”}]] Read More 

Vulnerability Archeology: Stealing Passwords with IBM i Access Client Solutions b

​As part of our ongoing research of the IBM i platform we monitor news and updates related to the platform. Two weeks ago IBM published a support article about a compatibility issue affecting IBM i Access Client Solutions (ACS) when running on Windows 11 24H2. The “no man’s land” between system boundaries is always a playground for hackers, and this article was fascinating because it pointed to the Local Security Authority subsystem of Windows: Read More 

Verified by MonsterInsights