jin@opus.UUCP (05/28/86)
Please add me to the INFO-VAX mailing list. We are planning a conversion from VMS 3.7 to 4.0, with future conversions taking us to the current VMS version. We support many RSX/IAS tasks including the TKB associated with VMS 3.0 (don't ask why, we must be able to continue using it). I have heard that AME does not support as many executive functions as are supported in VMS 3.7 but have not been able to find a specific list of changes from 3.7 to 4.0 (the SPD lists changes from a real RSX to AME but not what we need). Any info on this, or any other pitfalls of going to 4.0 (user-written drivers etc.) would be greatly appreciated. -- Bring back the Sixties! Bear ihnp4!houxm!hropus!jin
cetron%utah-cbd@UTAH-CS.ARPA (Ed Cetron) (05/31/86)
Then early VMS 3.x systems had what was known as the Applications Migration Executive (AME) which would allow RSX programs to run (sort-of) under VMS. It was supported by the VMS group and had some real problems. Around VMS 3.5 or 3.6 (roughly) the AME effort was removed from the VAX group and moved over to the RSX development team. The end result was VAX-11 RSX as a layered product. The bigger change was a strong commitment by the RSX team to make VAX RSX much more compatible with RSX-11M/M+, including fuller implementation of executive functions, PLAS directives,etc. In addition, this allowed 'tracking' of the standard releases of RSX-11M/M+ and in fact, the newest version of VAX RSX is very close to the current RSX-11M+ V3.0 . I found that with few exceptions, the newer VAX RSX's are pretty close - the clincher is that you can now do an entire RSX-11M/M+ sysgen under VAX RSX. The only problem that you will encounter is that the taskbuilder (TKB) for RSX-11M/M+ has changed drastically over the past few releases and the one from VMS 3.0 is quite likely NOT compatible with current RSX-11M/M+ releases... If you need more information, contact me directly.... Ed Cetron Center for Engineering Design, Univ of Utah DECUS RSX SIG Executive Committee arpa: cetron%utah-cbd@utah-cs.arpa