HP3000-L Archives

February 1995, Week 1

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:
Jerry Fochtman <[log in to unmask]>
Reply To:
Date:
Sun, 5 Feb 1995 19:15:00 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (35 lines)
Chris Breemer ([log in to unmask]) wrote (1/23):
 
> Has anybody got experience with running MPE 4.0 applications on MPE 5.0?
 
[..snip..]
 
We've been on MPE 5.0.20 'push' release since August because of this OS
release being required for the 987/200 processor.  By far the largest
majority of problems we've had are related to MPEX from Vesoft.  I
believe we basically were one of the first ones to test-out their updated
product on the new POSIXs file environment.  By now I believe most of the
bugs have been worked out.
 
In terms of HP's products on this release, networking/telecom has tended to
be where we've had several problems.  Although we've been told that most
everything we've seen has been resolved for the 'pull' release, there are
still a couple of items we're awaiting feedback on:
 
1 - If connected to a DTC and the session uses network services to obtain
    another pseudo terminal and logon again under another session, attempts
    to use X-on/X-off/Control-Y will cause the session to 'hang'.  Clearing
    this requires aborting both sessions and then resetting the DTC itself.
 
2 - Routing output from NRJE via output management to a MSG file results in
    the records being padded with null characters as opposed to spaces.  If
    sent to a standard MPE file this is not a problem.  Also, under 4.0
    records sent to a MSG file were padded with spaces.
 
All in all, 5.0 has been an excellent release.  Given the amount of change it
represents, the efforts HP has placed into the quality of the release
certainly deserves recognition.  The lab teams need to be commended for all
their efforts towards making the move to 5.0 a 'non-event'!
 
Regards -- Jerry Fochtman

ATOM RSS1 RSS2