Gang;
From Mr. Abootorab's message below and from examining our system here, I
have gleaned the following:
FTN - CM compiler
FTN2 - CM compiler, part two
FTNCAT - error messages
FNTCAT2 - error messages, part two
FTNCMDS - commands for conversion program
FTNCOMP - NM compiler
FTNCVT - conversion program
FTNXL, FTNXLGO, FTNXLLK - NM compiler command files
My sitiuation is:
We have a number of source files that appear to be FORTRAN 66. It is
suggested, below, that we convert from 66/V to 77/V before going NM. My
question then is this: What program do I use to compile those 77/V programs,
or am SOL?
Thanks!
Don Harrington
Sr. Programmer/Analyst
FacApps Support
Standard Services Group
Facilities Computing Services
PO Box 3707 M/C 6C-AK
Seattle, WA 98124-2207
(v) 425-234-1145 (f) 425-234-0464 (p) 206-797-6360
Location: 7-42.1, 1C3-2
The opinions expressed in this e-mail reflect those of the sender. They do
not necessarily reflect the opinions of The Boeing Company unless
specifically stated otherwise.
On , [log in to unmask] wrote:
>Hi,
>
>The followings are from Migration guide(MPE/V).
>I would suggest you do this in 2 steps:
>
>FORTRAN 66/V to FORTRAN 77/V (both CM) and then convert to Native mode.
>
>Hope this helps.
>
>Michael Abootorab
>
>*******************************************************
>FORTRAN 66/V to HP FORTRAN 77/V Migration Guide The Migration Process
>
>Several changes must be made to a FORTRAN 66/V program before it can be
>compiled by HP FORTRAN 77/V. The FORTRAN 66/V to HP FORTRAN 77/V
>Migration Aid allows you to automatically make most of these changes.
>The migration aid reads a FORTRAN 66/V source file, performs a number of
>transformations, and places the results in a new file. The new file can
>then be processed by the HP FORTRAN 77/V compiler. When the new file is
>compiled, those constructs that differ in HP FORTRAN 77/V from FORTRAN
>66/V but are not detected by the migration aid cause the compiler to
>generate a warning or an error message. The source file can then be
>manually changed in those places.
>
>The migration aid can also be modified to automatically perform specific
>changes required by your programs.
>
>The following are list of program and command files from pub.sys that you
might
>need:
>
>FTN PROG
>FTN2 PROG
>FTNCAT
>FTNCAT2
>FTNCMDS
>FTNCOMP NMPRG
>FTNCVT PROG
>FTNUDC
>FTNXL
>FTNXLGO
>FTNXLLK
>
>you wrote:
>
>Fortran is not my language of choice, however I have been given the task
>of converting a very old Financial application from Fortran/66 (MPE/V)
>running in compatibility mode on MPE/iX 5.5, to Fortan77/iX. Then once
>converted to the 32 bit Fortran77/iX, I'll need to address all the Y2K
>issues in this app as well.
>So all that said, does anyone know of a good debugger? I have already
>run the migration utility on the source code, compiled the NEW
>Fotran77/iX code with NO ERRORS :-) The app runs, but goes into loops,
>and appears to be walking all over it's own stack, output on reports
>contains non-ascii characters, it's bad. A good debugger is almost
anecessity!
>Also, any pointers (in reference to 66/77 differences) from anyone that
>knows both Fortran 66 and 77, will be very much appreciated.Thank in
advance,
>Michael Anderson,Sr. Systems ProgrammerTIW CorporationHouston, Texas
>(713) 729-2110 ext:287
>---------------------------------------------------------------------------
-----
>and then from CM to NM conversion guide :
>
>HP3000_16 Directive
>
>The HP3000_16 compiler directive specifies various options for
>compatibility with HP FORTRAN 77/V.
>
>These are the options:
> $HP3000_16 REALS Specifies MPE V format for floating-point
> data.
> $HP3000_16 ALIGNMENT Specifies alignment of noncharacter data on
> 16-bit boundaries.
> $HP3000_16 STRING_MOVE Specifies that overlapping character
> strings are moved.
> $HP3000_16 ON Specifies all the above options.
> $HP3000_16 Same as $HP3000_16 ON.
> $HP3000_16 OFF Specifies none of the above options.
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
