I don't recall seeing this mentioned explicitly (and I apologize for the
wasted bandwidth if it was and I was asleep), so...
 
Conner Peripherals updated a couple systems to MPE/iX 5.0 just recently,
with a few more still to come. I don't know about the Systems Management
side, but the Applications Support area has hit only a couple snags in the
first couple weeks.
 
1. FORTRAN '77 (now at A.05.00, versus the former A.04.32) now checks
substring constants at compile time to verify they are in range. (It still
does not check array constants at compile time.) For example:
 
   integer    iarray (10)
   character  string*10
   ...
   iarray (12) = 12     !still NOT flagged as error at compile time
   string (12:12) = "X" !flagged twice at compile time,
                        !since both START and END positions are out of
range
 
   While this enhancement is really a Good Thing, it caught a few
(extensively modified) MANMAN routines by surprise.
 
2. MPEX was upgraded to Version 25. We had cloned N3.LISTF.VESOFT (used to
generate the %LISTF,3 output) and made some modifications. This routine
(N3) uses a function (?) called MPEXFILESETGENERAL. For Version 25, VEsoft
added a required parameter to this undocumented function, causing our
cloned code to break.
 
Otherwise, so far, so good (though we haven't done a thing with POSIX yet).
 
--Glenn Cole
  Software al dente, Inc.
  [log in to unmask]