I found this same problem with a FORTRAN program a year or so ago.  It's a
known problem - not likely to get fixed.  I forget the details, but I think
you get different results whether the subroutine is included in the program
or in an XL.

Jack


                -----Original Message-----
                From:   Tony Summers [mailto:[log in to unmask]]
                Sent:   Wednesday, September 13, 2000 12:22 PM
                To:     [log in to unmask]
                Subject:        Cobol, Loader and HP3000 problem

                I have a cobol subprogram that has 4 parameters

                I have called that subprogram from my main program twice -
once with all 4 parameters and once with just two.

                If the code is organised thus

                if <condition which happens to be false>
                     CALL "X" USING A, B.
                end if
                CALL "X" USING A,B,C,D.

                then the program fails to load - as I would expect.

                If, however, the code is organized thus :

                if <condition which happens to be false>
                    CALL "X" USING A, B,C,D
                end if
                CALL "X" USING A,B.

                then the program loads, but then aborts on bound violation
when the second call to the subroutine is made.

                Note it appears to be important that the first call to the
correct version of the subroutine is not "executed" .

                Can anyone suggest a method that prevents the program from
either being compiled in the first place or have
                I discovered a little known bug in the loader ?

                Many thanks.