HP3000-L Archives

July 2000, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Schick, John" <[log in to unmask]>
Reply To:
Schick, John
Date:
Tue, 11 Jul 2000 15:41:24 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (70 lines)
As the author of the document "Patching Subroutines Compiled on MPE/iX 6.5
to Earlier Versions of MPE/iX" which Ronald mentioned, I'd like to comment
about Patrick's question concerning using the 6.5 version of milli.lib.sys
on a 5.5 system.

I tried this very thing during my research of the issue.  I moved
milli.lib.sys from a 6.5 system to a 5.5 system and was able to successfully
compile and link several COBOL routines.  However, my testing was very
limited and I would be extremely hesitant to recommend this solution without
the endorsement of HP.

Patrick, in the case of receiving stand-alone programs from your vendor, I
think you are best off to "bite the bullet" and have your vendor send you
the linked program files.  As Ronald pointed out, in the case of receiving
subroutines, ask your vendor to send you an XL file that you can "COPYXL"
into your production XL.

John Schick
Sr. Technical Development Advisor
McKessonHBOC (AMISYS)


-----Original Message-----
From: Patrick Santucci [mailto:[log in to unmask]]
Sent: Tuesday, July 11, 2000 10:52 AM
To: [log in to unmask]
Subject: Re: Cobol compiled on 6.5 and run pre 6.5


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.

ATOM RSS1 RSS2