Hi Duane

> I ran tests on a 5.5 system that had the updated routines and
> on an older system that did not. Lets call the 5.5 system 'a' and
> the older 'non-updated routines' system 'b'.

  I guess, the system 'b' is pre-MPE/iX 5.0.

> 2. NL (Native Language) routines (like nlconvcustdate, nlfmtcustdate,
>    nlfmtdate, etc) accessed on 'a' treated 2 digit years < 50 as 20xx
>    dates and years >= 50 seemed to be 19xx dates.

   YY:Split century method (2 digit years < 50 as 20xx and so on)
   does not apply to these intrinsics.

   These NL intrinsics takes input date in CALENDAR format where the
   year field can be from 0..127. So, if you pass 25 in the year field,
   you should be getting the result as 1925 (not as 2025) from the above
   intrinsics. I verified this behavior in 5.0 and 5.5.

   As you have mentioned (in MPE/XL 4.0), calendar.year >= 100 gives err=3
   for almanac and other NL intrinsics.

> Quick Conclusions
> -----------------
> 1. The NL routines assumption of century being changed might bite you

    No, it is not changed. It is simply a 1900 + calendar_year.


Hope this helps,

gopi ([log in to unmask])
CSY R&D India, Bangalore.