HP3000-L Archives

September 1997, 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:
Undetermined origin c/o LISTSERV administrator <[log in to unmask]>
Reply To:
Undetermined origin c/o LISTSERV administrator <[log in to unmask]>
Date:
Tue, 9 Sep 1997 08:14:33 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (37 lines)
Hello. Here I am again, coming around with hat in hand,  begging for some
crumbs of knowledge and wisdom from the HP3K geniuses that so profusely
dominate this list <is it spread too thick, you think?>

Anyway - here is the setup: I have three systems, A, B and F that
communicate using SNA to an IBM 3270 at a remote location. Systems A and F
use a product called SNA Server Access to communicate with B which is
running SNA Server. The kicker? System B is a series 37. System A is a 967
and System F is a 987, both running MPE 5.0. System A is in the process of
being replaced with a 979/200 running MPE 5.5. The products mentioned are
for MPE iX to V communications, allowing data to flow to and from the
server.  As I am sure everyone is aware, HP will no longer support any
"Classic" machines after Sept. 98, and this needs to continue to take place
well past that date.

Our original solution was to find another machine - System N, which is a
925, to become our new SNA Server. Too easy, right? RIGHT. HP has now
informed me that the products we have been using, SNA Server and SNA Server
Access (product numbers 30254A and 30255A, respectively) will not only be
going out of support, but there is no iX to iX software to take its place!
And that there are no plans to do so! My bosses are not satisfied with this
answer from the response center, and don't like the idea of keeping the 37
around. (Oh yeah, and the 2680, too!)

I am posing this question: Does anyone out there know of any other way to
do this? A simple DSLINE won't cut it. We transmit data from A(or F) to B
to IBM back to B and then to A(or F) in the form of a data file. We have
looked at :REMOTEing, but then the data does not end up back on the
originating machine.  Any assistance in solving this problem is greatly
appreciated!

Thanks in advance

Lisa Leidig
Informations Systems Consultant
Metro Information Services

ATOM RSS1 RSS2