Porting VMS to Windows
|
Original Message
|
Name: shelleyb
Date: May 23, 2004 at 03:19:09 Pacific
Subject: Porting VMS to Windows
OS: VMS
CPU/Ram: Alpha
|
Comment: We would like to port our application written in Cobol and Fortran on VMS to NT. We have Cobol program that call Fortran routines and pass parameters of type integer, float and string. We also have Fortran routines/programs that call Cobol routines and pass parameters of similar types.
Can this be handled on NT?
Can this be handled on .NET?
What issues should we consider and problems to look out for in this conversion process?
Report Offensive Message For Removal
|
|
Response Number 1
|
Name: jubalsams
Date: May 25, 2004 at 03:02:53 Pacific
Subject: Porting VMS to Windows |
Reply: (edit)There are plenty of FORTRAN compilers, namely Compaq Fortran and Intel Fortran, even free ones GFORCE and Watcom. There must be some old Cobol compilers around ... try Google, but what you really need is a dev system with both cobol and fortran ... maybe some very old dos dev systems. I seem to remember IBM had a dev with both fortran and cobol. Best
 Report Offensive Follow Up For Removal
|
|
Response Number 2
|
Name: WillemGrooters
Date: May 26, 2004 at 05:24:20 Pacific
Subject: Porting VMS to Windows
|
Reply: (edit)If the modules that form your application are written in different languages, you may run in trouble when porting it to NT: it might not be possible on other platforms.
You need to be aware of diffenences in implementations in both COBOL and FORTRAN on VMS,and NT - even within different compilers on NT.
If your programs use system services, be aware that you'll need to port these - or find similar routines on NT. Some facilities in VMS do not even exist so you'll have to re-program, even redesign modules. Willem Grooters
Report Offensive Follow Up For Removal
|
|
Response Number 3
|
Name: WillemGrooters
Date: June 9, 2004 at 07:16:43 Pacific
Subject: Porting VMS to Windows
|
Reply: (edit)Are you running VAX?
You _may_ consider CharonVAX. Running on Intel hardware, under WindowsServer2000 or 2003 (Linux to come), this whole package replaces your VAX. Fully supported by HP when installed on HP hardware. Requirements: 2 processors at least, 4 times the memory as you have on your VAX. We've installed it with a number of customers, the biggest gain is the possibility to use new hardware architecturees that were never avialbale on VAX (SAN, GigabitEthernet), speed of IO (500%!) and some win in CPU performance. Advantage: you don't have to change ANYTHING on your VMS environment (up to re-tuning VMS).
(Security: No rpoblem. If you have 1 NIC in your system AND specify this one for VMS, Windowes has NOT ANY control over it.) Willem Grooters
Report Offensive Follow Up For Removal
|
Use following form to reply to current message:
