Languages and Scripting
Showing results for 
Search instead for 
Do you mean 

DECnet Phase IV porting issue

SOLVED
Go to Solution
Frequent Advisor

DECnet Phase IV porting issue

Hi,

 

I'm trying to port some very old stuff from VAX to I64.

The software is written in VAX Fortran and uses DECnet IV nontransparent task-to-task communiation.

 

The software compiles fine on I64 using HP Fortran V8.2 but during runtime I get

%SYSTEM-F-BADPARAM, bad parameter value

 

This comes from a call to $QIO where the program tries to register itself as a DECnet object

(function code IO$_ACPCONTROL)

 

Attached you may find a reproducer.

 

Any help would be greatly appreciated.

 

 

1 ACCEPTED SOLUTIONS
Honored Contributor

Re: DECnet Phase IV porting issue

[ Edited ]

Mike is absolutely right: you need to enclose the DECLNAME Structure definition like this:

 

!DEC$ OPTIONS/NOWARN/ALIGN=(RECORDS=PACKED,COMMONS=PACKED)
        STRUCTURE /DECLNAME/
            BYTE                FUNCTION
            UNION
                MAP
                    INTEGER*4   FILLER                  ! "name" case
                END MAP

                MAP
                    INTEGER*4   OBJ_NUM                 ! "name" case
                END MAP
            END UNION
        END STRUCTURE
!DEC$ END OPTIONS

 

Otherwise the NFB is not filled correctly, because the INTEGER*4 longword is put at the next LONGWORD boundary after the BYTE. This has nothing to do with Itanium, it also fails on Alpha.

 

Volker.

5 REPLIES
Highlighted
Valued Contributor Valued Contributor

Re: DECnet Phase IV porting issue

My very first thought would be alignment when switching architectures.  Since you can't use a supplied library module (I don't know why that is omitted from FORSYSDEF - maybe there is an SDL equivalent that you could use the freeware SDL package to generate an include file for it), you should probably wrap your structure definitions with

 

!DEC$ OPTIONS/NOWARN/ALIGN=(RECORDS=PACKED,COMMONS=PACKED)

!DEC$ END OPTIONS

 

like the library modules do.

 

Since you are using your own PARAMETER definitions, I'd also verify them against the values on your target system, but I'd be very surprised if they have changed - but, trust AND verify :-).

 

If that fails to resolve it, I'd start with a /NOOPT/DEBUG version and examine everything, including addresses, just before and after the call.

 

I'd also look at promoting any of the non-record I*2 values just from a performance perspective and change the event flag to the ENF value - it doesn't look like you use it for anything.

 

Practice Random Acts of VMS Marketing
Honored Contributor

Re: DECnet Phase IV porting issue

[ Edited ]

Mike is absolutely right: you need to enclose the DECLNAME Structure definition like this:

 

!DEC$ OPTIONS/NOWARN/ALIGN=(RECORDS=PACKED,COMMONS=PACKED)
        STRUCTURE /DECLNAME/
            BYTE                FUNCTION
            UNION
                MAP
                    INTEGER*4   FILLER                  ! "name" case
                END MAP

                MAP
                    INTEGER*4   OBJ_NUM                 ! "name" case
                END MAP
            END UNION
        END STRUCTURE
!DEC$ END OPTIONS

 

Otherwise the NFB is not filled correctly, because the INTEGER*4 longword is put at the next LONGWORD boundary after the BYTE. This has nothing to do with Itanium, it also fails on Alpha.

 

Volker.

Frequent Advisor

Re: DECnet Phase IV porting issue

Thank you very much.

 

 

Frequent Advisor

Re: DECnet Phase IV porting issue

Mike, Volker,

 

I tried to give you 10 points, but I'm still fighting with this user interface.

 

Sorry

Acclaimed Contributor Acclaimed Contributor

Re: DECnet Phase IV porting issue

>I tried to give you 10 points,

 

One Kudos ~= a bunny.