HP3000-L Archives

March 2002, 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:
Re: migration
From:
"Wayne R. Boyer" <[log in to unmask]>
Reply To:
[log in to unmask]
Date:
Fri, 8 Mar 2002 11:09:23 EST
Content-Type:
text/plain
Parts/Attachments:
text/plain (19 lines) 
In a message dated 3/8/02 12:33:53 AM Pacific Standard Time,
[log in to unmask] writes:


> 2) An additional option is to do as much as you can whilst still on the
> HP3000 to remove replace 3000 specific operations, functions and
> software, so that later migration becomes more feasible.

I strongly agree with this recommendation.  Eliminating MPE-isms from your
application makes it much more portable.  Part of the way to do this in COBOL
is to isolate MPE-specific constructs into your COPYLIB.  That's usually easy
to do.  Once an MPE-specific construct is only located in the COPYLIB, you
can re-write it to be less OS specific.

Wayne Boyer

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2