Ronald,

I have a three page document titled "Patching Subroutines Compiled on
MPE/iX 6.5 to Earlier Versions of MPE/iX" that I got from one of our
vendors (who shall remain nameless, since they are trying to force all
their clients to go to 6.5 by 10-1-00... but I digress...). It details the
problem you're having and describes a work-around whereby you link the
6.5-compiled object module into its own separate XL file on the 6.5
machine, transfer it to the 5.5 (or 6.0) system, and then use the COPYXL
command in LINKEDIT instead of ADDXL to put the module into the XL file on
the 5.5 system.

If you want a copy I'll be happy to fax it, email your fax number to me.

Patrick
--
Patrick Santucci
Technical Services Analyst
Seabury & Smith, Inc.

-------------------- Lotus "Knots" Reply Separator --------------------



Please respond to Ronald La Pierre <[log in to unmask]>
To:     [log in to unmask]
cc:      (bcc: Patrick Santucci/DSM/Seabury)

Subject:        [HP3000-L] Cobol compiled on 6.5 and run pre 6.5



Our software provider has recently upgraded to 6.5.  We are on 5.5 PP7.
They typically compile on their machine, transfer to ours and link it on
our machine (the executables are large to transfer).

We are now getting the unsatisfied symbols of $$div2I, $$mul12U, etc (as
stated in the the communicator for 6.5) when linked.

Does anyone know of a workaround to prevent us from upgrading our 3000's.
I don't know if it's possible to use the 6.5 milli.lib.sys on a 5.5
system.

Thanks in advance for any input.