Thomas,

Normally this would be for the IBMTCP-L list/group but you've started it
here so we'll continue here. In any case I get the impression that most who
are active on IBMTCP-L are active here also.

It's implied that you run SNA applications on your AS/400 so the first thing
we need to know is whether or not you continue to run SNA applications on
your AS/400. For example, it's possible though something like
infinitesimally unlikely that you run the MPTN (Multiprotocol Transport
Network) socket programming over SNA function on your AS/400 and mainframe
so that all the applications you care about are IP-based applications.

The next question worth asking is, if you need to continue to run SNA
applications, how did the person who was managing the discontinuation - as
they say - of the 3745 manage to forget about your poor AS/400. Perhaps a
number of other SNA requirements have been forgotten about. You might like
to ask around, gang up together, and halt the decline into chaos.

Having got this far into your post, I'm a bit lost. If the AS/400 has been
replaced why are you worrying? What is this about identity?

I can only proceed by making the assumption you still have an AS/400 and
that the rather careless person who is supposedly managing the replacement
of the 3745 is giving you an IP address in order - somehow - to identify the
mainframe.

It's possible that the person managing the change at the mainframe has done
a good job and that you don't really understand what you are being told. It
may be that he/she has set up one end of the reverse MPTN "trick" which is
AnyNet SNA over IP, the mainframe end has been set up and he/she is
expecting you to set up the AS/400 end, one key parameter of which would be
the associated IP addresses on your corporate IP intranet, I expect.

Just to muddy the water, there is another way to perform this task of
transporting SNA over an IP network - I'm not considering DLSw - which is
Enterprise Extender. Again, key parameters would be the IP addresses. What's
a bit complicated about this in your circumstances is that I believe the
AS/400 range (aren't we supposed to call it the iSeries these days?) has
only just got Enterprise Extender support.

I think you'd better post again after clarifying your situation somewhat and
probably you'd better make it a joint exercise with the relevant mainframer.

Chris Mason

----- Original Message ----- 
From: "Thomas Lawrence" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To: <[email protected]>
Sent: Thursday, 20 April, 2006 5:10 PM
Subject: Need Help defining an AS400 with an IP address to the mainframe


> I hope I don't sound too stupid here, but I am trying to define an AS400
to
> the mainframe (a z/os system). Previously this AS400 was defined using a
> SWNET definition which pointed to a TIC off a 3745. Now the AS400 has been
> replaced and only has an IP address to identify it. Someone been this
route?
> Thanks.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to