migrate FMS from VAX to AXP = error ...

[Stéphane Boneff]

Hello,

wa are trying to migrate foRtran sources from vax VMS 6.1 to AXP VMS 6.2.

We have a problem with FMS.
On vax, FMS 2.4
on AXP, our support seemed to have install FMS 2.5.

after creating a .OBJ from .FLB (that contain all the FMS forms), the link send the warning :
%LINK-W-ILLRECTYP, illegal record type (8176.)
in module FDV$MEMRES record 7 file DISK3:[POCHES6M.APPLICATION.OBJ]FORM_POCHES6M.OBJ;11
%LINK-W-ILLRECTYP, illegal record type (8176.)
in module FDV$MEMRES record 7 file DISK3:[POCHES6M.APPLICATION.OBJ]FORM_POCHES6M.OBJ;11


and the exe modul crashs :

%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0001F783, PC=0017CB68, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
Image Name Module Name Routine Name Line Number rel PC abs PC
FDVSHR FDV$FORMS2 FDV$$FIND_MRF_B 779 000005B8 0017CB68
FDVSHR FDV$FORMS1 FDV$$MRF 1477 00001174 001839D4
FDVSHR FDV$FORMS1 FDV$$FNDFORM 612 000002CC 00182B2C
FDVSHR FDV$FORMS FDV$$LOAD 716 0000064C 00186B4C
FDVSHR FDV$FORMS1 FDV$$DFORM 493 00000100 00182960
FDVSHR FDV$FORMS FDV$$CDISP 470 000003F4 001868F4
FDVSHR FDV$DISPCH ISOLATE 876 000007BC 0018B04C
FDVSHR FDV$DISPCH FDV$$DISPATCH 414 000001D0 0018AA60
FDVSHR FDV$PLIDIS FDV$$PLIDISPATC 523 000003B0 0018A130
FDVSHR FDV$PLINTR FDV$CDISP 158 000050A8 00181D98
SUIVI_CORREC SUIVI_CORRECTEU SUIVI_CORRECTEU 7420 000004E8 000304E8
SUIVI_CORREC 0 0002DED8 0003DED8
DEC$FORRTL 0 00072818 00250818
SUIVI_CORREC 0 0002DED8 0003DED8
0 8A1AC170 8A1AC170


the form works fine with FMS editor.

have you some idea ?

thanks !

[Wim Van den Wyngaert]

How did you create the obj ? Any command can create output files with type obj.

Wim

[Kris Clippeleyr]

Hi,
According to the SPD at
http://h71000.www7.hp.com/commercial/cpss.html#fms
FMS 2.5 seems to be supported on OpenVMS Alpha V7.3-1 and higher.
Over here, we use FMS 2.4 without problems (lowest VMS version = 7.2-2).
Maybe you can downgrade to FMS 2.4. I don't think it will make any "functional" difference.
Regards,
Kris (aka Qkcl)

[Karl Rohwedder]

Did the FMS/OBJECT command produce an errors or warnings?

regards Kalle

[Karl Rohwedder]

Maybe the TIMA article
http://h18000.www1.hp.com/support/asktima/appl_tools/CHAMP_SRC950927005327.html
is of some help.

You did recreate the.OBJ on the alpha, did you?

regards Kalle

[Kris Clippeleyr]

Hi,
According to the SW-rollout at
http://h71000.www7.hp.com/openvms/os/swroll/VAROL.HTML
The minimal version of VMS for FMS 2.5 is 7.3-2.
Regards,
Kris (aka Qkcl)

[Stéphane Boneff]

thanks to everybody.

it's my first question on that forum and i got answers in a sort time.

I don't know yet how use corectly the reply interface.

For my pb : i will ask to support to instal the FMS 2.4 AXP version.

I will give here some news.

thanks

[Volker Halle]

Stephane,

welcome to the OpenVMS ITRC forum.

Please re-read the error message %LINK-W-ILLRECTYP and make sure you've really created the FORM_POCHES6M.OBJ file on the OpenVMS Alpha system.

%LINK-W-ILLRECTYP errors typically show that you're linking an object file created on a different architecture.

Try $ ANAL/OBJ FORM_POCHES6M.OBJ /SELECT=(ARCH,FILE) to find out...

Volker.

[Stéphane Boneff]

Hello,

I'm sur of every .OBJ modules, including the FORM_POCHES6M.OBJ .
At the start of the migrate, i deleted all .OBJ modules and all .EXE modules.

At that moment, I have been waiting for the installation of the FMS 2.4.

thanks.

[Stéphane Boneff]

Hello,

a version FMS was installed (2.4 I hope)
and after recompiling the forms (.FLB --> .OBJ) and after linking, i have the same error (for another form).

error = %FDV-E-FRM, Invalid binary form

The link warnings are still the same :
FDV$MEMRES V2.5 49144 FORM_POCHES6M.OBJ;1 1-FEB-2006 10:18 VAX FMS V2.5
%LINK-W-ILLRECTYP, illegal record type (8176.)
in module FDV$MEMRES record 16 file DISK3:[POCHES6M.APPLICATION.OBJ]FORM_POCHES6M.OBJ;1
%LINK-W-ILLRECTYP, illegal record type (8176.)
in module FDV$MEMRES record 16 file DISK3:[POCHES6M.APPLICATION.OBJ]FORM_POCHES6M.OBJ;1
CLEAR_IM1 840 POCHES6M.OLB;1 16-JAN-2006 15:04 DEC Fortran V6.3-711
COMPILER_NOM 1200 [STANDARD.OBJ_ALPHA]STANDARD.OLB;1 28-NOV-1996 16:18 DEC Fortran V6.3-711
LIRE_PT 1828 [STANDARD.OBJ_ALPHA]STANDARD.OLB;1 28-NOV-1996 16:19 DEC Fortran V6.3-711
FDV$PLITRM V2.1-005 1380 SYS$COMMON:[SYSLIB]STARLET.OLB;2 29-OCT-1992 18:27 BLISS-32E T1.0-019G
LIB$INITIALIZE X-4 508 SYS$COMMON:[SYSLIB]STARLET.OLB;2 4-MAY-1995 19:10 AMAC V2.0-22
AMAC$EMUL_CALL X-3 544 SYS$COMMON:[SYSLIB]STARLET.OLB;2 4-MAY-1995 19:50 AMAC V2.0-22
DEC$FORRTL V01-05.171 0 SYS$COMMON:[SYSLIB]DEC$FORRTL.EXE;1 4-MAY-1995 22:35 Linker A11-12
FDVSHR FMS V2.4 0 SYS$COMMON:[SYSLIB]FDVSHR.EXE;2 29-OCT-1992 19:00 Linker T10-48

[Karl Rohwedder]

What puzzled me is the line:
The link warnings are still the same :
FDV$MEMRES V2.5 49144 FORM_POCHES6M.OBJ;1 1-FEB-2006 10:18 VAX FMS V2.5

esp. the mention of VAX FMS V2.5

Pls. post the result of the ANA/OBJ Volker mentioned some replies ago.

regards Kalle

[Stéphane Boneff]

sorry but no /SELECT on my AXP VMS 6.2.

with /obj, i have these options :
/DBG /EOM /GSD /INCLUDE /INTERACTIVE /LNK /MHD /OUTPUT /TBT /TIR

i tryed :
$ ANAL/OBJ FORM_POCHES6M.OBJ /inter
1. MODULE HEADER (EOBJ$C_EMH), 82 bytes

structure level: 2
maximum record size: 8192



Other options :

$ ANAL/OBJ FORM_POCHES6M.OBJ /lnk


Analyze Object File 1-FEB-2006 12:12:39.20 Page 1
DISK3:[POCHES6M.APPLICATION.OBJ]FORM_POCHES6M.OBJ;1
ANALYZ A05-19

This is an OpenVMS Alpha object file

1. MODULE HEADER (EOBJ$C_EMH), 82 bytes

structure level: 2
maximum record size: 8192
module name: "FDV$MEMRES"
module version: "V2.5"
creation date/time: 1-FEB-2006 10:18


2. LANGUAGE PROCESSOR HEADER (EMH$C_LNM), 18 bytes

Textual information:
"VAX FMS V2.5"


*** Object record 16 has a length of zero.


27. END OF MODULE (EOBJ$C_EEOM), 10 bytes

severity: successful (0)
Highest conditional linkage index: 0
module name: "FDV$MEMRES"
module version: "V2.5"
creation date/time: 1-FEB-2006 10:18

2. LANGUAGE PROCESSOR HEADER (EMH$C_LNM), 18 bytes

Textual information:
"VAX FMS V2.5"
Analyze Object File 1-FEB-2006 12:12:39.33 Page 2
DISK3:[POCHES6M.APPLICATION.OBJ]FORM_POCHES6M.OBJ;1
ANALYZ A05-19

SUMMARY STATISTICS:

Record Type Count Total Bytes

OBJ$C_DBG 0 0
OBJ$C_TBT 0 0
EOBJ$C_EMH 2 100
EOBJ$C_EEOM 1 10
EOBJ$C_EGSD 0 0
EOBJ$C_ETIR 0 0
EOBJ$C_EDBG 0 0
EOBJ$C_ETBT 0 0

Totals 3 110


The analysis uncovered 1 error.


ANAL/OBJ FORM_POCHES6M.OBJ/LNK


One question : how to know the version of my AXP FMS ???
For my DEC support, it is 2.4 but in .MAP module, i see 2.5 (like in the lines above).

I feel lost with this pb of version ...

[Volker Halle · Accepted solution]

Stephane,

maybe downgrading FMS did not work correctly ?!

Find any of the images, that come with FMS (e.g. SYS$SYSTEM:*FMS*.EXE and SYS$SAHRE:*FMS*.EXE) and do an ANAL/IMA/INTER and look for the image file identification. Normally, you'll find the product name and version in those images.

An explanation for the error you're seeing could be, that a new object record format is being generated by FMS V2.5, which is not supported by the LINKER in V6.2...

Volker.

[Volker Halle]

Stephane,

the image invoked with FMS/OBJECT is SYS$SYSTEM:FMSFAA.EXE and it reports an image ident of "FMS V2.4" (when FMS V2.4 is installed).

SYS$SHARE:FDVSHR also shows "FMS V2.4", both images are linked 29-OCT-1992.

If you have any FMS images more recent than that and showing "FMS V2.5", the downgrade of FMS did NOT work. Have your support show you the terminal session logfile from the installation of FMS V2.4...

Volker.

[Stéphane Boneff]

Volker,

First of all, tranks to helping me.
(and sorry for my bad english)

Here is the data :
image name: "FMSFAA"
image file identification: "FMS V2.4"

image name: "FMSFED"
image file identification: "FMS V2.4"

image name: "FMSFLG"
image file identification: "FMS V2.4"

image name: "FMSFLI"
image file identification: "FMS V2.4"

image name: "FMSFTE"
image file identification: "FMS V2.4"

image name: "FMSFUU"
image file identification: "FMS V2.4"


sys$share : no *FMS*.EXE, only FDV :

image name: "FDVSHR"
image file identification: "FMS V2.4"

image name: "FDVSHR_TV"
image file identification: "FMS V2.4"

every *fms*.exe or *fdv*.exe of system directory has a date
of 1992 (oct & nov)

--> so I think I have the 2.4 version ...

about the line in error in link :
FDV$MEMRES V2.5 49144 FORM_POCHES6M.OBJ;1 1-FEB-2006 14:26 VAX FMS V2.5
%LINK-W-ILLRECTYP, illegal record type (8176.)
in module FDV$MEMRES record 17 file DISK3:[POCHES6M.APPLICATION.OBJ]FORM_POCHES6M.OBJ;1
%LINK-W-ILLRECTYP, illegal record type (8176.)
in module FDV$MEMRES record 17 file DISK3:[POCHES6M.APPLICATION.OBJ]FORM_POCHES6M.OBJ;1


what is that mean ?

to what is FDV$MEMRES ?
$anal /obj -->
. LANGUAGE PROCESSOR HEADER (EMH$C_LNM), 18 bytes

Textual information:
"VAX FMS V2.5"

[Hein van den Heuvel]

The VAX FMS 2.5 is probably comming from teh forms editor there.


Do you have more than 75 fields on the form?
Check out:
http://ftp.support.compaq.com.au/pub/patches/vms/axp/v1.5/fms/2.4/fmsaxpeco04024.html
btw... i found this with a simple google: fms illrectype

If you keep getting problems with your main application on Alpha then i suggest taking babysteps to find out what works/fails:
- First try a simple "hello world" form with single field and getal from a library.
- Now compile the form, link with the code and try
- Now you main application, using a library.
- ...

hth,
Hein.

[Volker Halle]

Stephan,

Hein's answer looks very proising.

Also note that your ANAL/OBJ did actually report an error:

...

*** Object record 16 has a length of zero
...
The analysis uncovered 1 error.
ANAL/OBJ FORM_POCHES6M.OBJ/LNK

Unless ANAL/OBJ is error-free, you don't even want to try LINK...

Volker.

[Stéphane Boneff]

the line
"If there are more than 75 fields in a form, the LINK-W-ILLRECTYP
error would appear when linking the form
" seems to be interesting for me.
(but there is no information about the result (despite the warning, the image can be use ??) )+

Because :
- 2 other forms work fine in AXP version.
- the form that don't work contain :
3 singles field
13 fields "index 1 of 50"
i don't know if it counts for 650 + 3 fields.

When I delete some fields, the warning is still here but the form is displayed.

[Hein van den Heuvel]

>>> despite the warning, the image can be use ??

IMHO linker unexplained warnings are not acceptable.
The only one I will allows is where the compiler issued an informational and I understand the implications of the informational and decided to link anyway.

>> - 2 other forms work fine in AXP version.

Good to know!

>>. 13 fields "index 1 of 50" i don't know if it counts for 650 + 3 fields.

I think is does. Easy enough to check? Change to "index 1 of 5"?

>> When I delete some fields, the warning is still here but the form is displayed.

I would interpret that as a strong indication that you are expereincing that know problem, it is just confused in a different way.

fwiw,
Hein.

[Stéphane Boneff]

The solution was to instal ECO 5 of FMS.

no warning any more at link

the .exe run fines and form is ok on screen.

Thanks to everybody !