|
midrange.com
It should work, I've done it couple of times to communicate to remote
ATM device attached to remote AS/400 system.
I have to apologize for a mistake in my previous note. It should read
like this:
- AS/400#2 will have 3270 (LU 2) device description downstream to
AS/400#1 (configuration should be similar to what is now on AS/400#1)
- AS/400#1 will have *SNPT *UP device description upstream to AS/400#2
and *SNPT *DOWN device description downstream to remote system.
Additional trick is that of course, controller type on AS/400#1 will
have to be different - you are absolutely correct that SNPT will not
work for remote work station controller type. But this is not needed in
this case.
AS/400#2 has to think that remote controller, where 3270 device is
attached, is a remote workstation controller (so there should be a
separate controller description on AS/400#2 for AS/400#1 and it has to
be remote work station controller. AS/400 does support this type of
connection).
For AS/400#1 exact type of controller is not important as soon as it is
PU type 2.0 SNA node.
Important thing here is that these are two different things:
- controller (PU) type as it is used by SNA layer of AS/400. In
our case we need PU type 2 on both levels
- AS/400 controller type - it can be remote workstation
controller, APPC controller, finance controller etc - as it is used by
other functions on AS/400. They all can be PU type 2 controllers with
some specific characteristics.
To say it in different terms - AS/400 controller description should be
of specific type only on the AS/400 which uses remote node for some
specific purpose.
For all other AS/400s involved any PU type 2 controller will do (say
3174 or 3274 type).
Hope I did not increase confusion still more...
Best regards,
Alexei Pytel
-----Original Message-----
From: Tim McCarthy [SMTP:twmac@mindspring.com]
Sent: Friday, June 12, 1998 2:33 PM
To: MIDRANGE-L@midrange.com
Subject: RE: Remote Communication - HELP!
Correct me if I'm wrong, but I don't think using SNPT will work
with a
remote work station controller. If the case was AS/400 users or
RJE type
jobs running on the mainframe then you'd be O.K. Since this is a
batch job
I'd need to ask how it's working and what it does. If you could
switch to a
host controller and say a SNUF device you could still start the
job (on the
second AS/400) from the mainframe, but it would be the mainframe
host
controlling the session rather than the other way around.
At 09:45 AM 6/12/98 +0100, you wrote:
>
>You can try a feature called SNA Passthrough.
>It will do exactly what you want:
> - AS/400#2 will have *SNPT device description downstream to
AS/400#1.
>- AS/400#1 will have *SNPT device description upstream to
AS/400#2 and
>3270 (LU 2) device description downstream to remote system.
>
>AS/400#2 will establish and control the session, while AS/400#1
will
>essentially pass all session traffic unchanged from AS/400#2
down to
>remote system.
>
>Instructions for setup and sample configurations can be found
in "AS/400
>Remote Workstation Guide".
>
>Hope this will help.
>
>
> Best regards,
>
> Alexei Pytel
>
>
>
>
> -----Original Message-----
> From: Jeff Carey [SMTP:jeffreycarey@usa.net]
> Sent: Friday, June 12, 1998 12:41 AM
> To: MIDRANGE-L@midrange.com
> Subject: Re: Remote Communication - HELP!
>
> Here is the current situation:
>
> AS/400 #1 connected to a SDLC line to remote mainframe
> Batch job on AS/400 #1 one uses 3277 devices to pass
data back
>and forth with
> mainframe. These 3277 devices hang off of a 3274 ctld
that in
>turn hangs off the
> SDLC lind.
>
> What we want:
> AS/400 #2 currently attached to AS/400 #1 over TR LAN.
> Want to move batch job to AS/400 #2, but keep physical
>connection to mainframe on
> AS/400 #1.
>
> No one on AS/400 #1 will need to access the mainframe
after the
>application is
> moved.
>
>
>
>
> Carl Galgano wrote:
>
> > If I understand your question (you want to use a line
>description from one
> > AS400 and a controller and device from another AS400,
both on
>the same
> > LAN/WAN and have the controller connect to the line),
the
>answer is NO.
> > However, there are usually more that one way to skin a
cat, so
>exactly what
> > are you trying to do, if you are trying to access data
across
>the line,
> > perhaps you could use the existing AS400 for the
physical
>link, and use
> > something like DDM to have the data actually appear on
the new
>AS400. Some
> > more details might be helpful.
> > HTH,
> > Carl
> >
> > At 10:51 AM 6/11/98 -0500, you wrote:
> > >We need to sole a problem - we have an AS/400 with an
SDLC
>link to a
> > credit card
> > >service - this line has a 3274 ctld attached to it,
and the
>controller has
> > two
> > >3277 display sessions attached to it.
> > >
> > >Now we need to move the application using thast line
to
>another AS/400 on
> > our LAN
> > >(but not at the same location, so I can't just change
the
>physical connection
> > >(RS232 into a modem into a leased line).
> > >
> > >Is there a way for me to create a ctld and devd on
the new
>AS/400, and
> > have them
> > >communicate over the SDLC line on the current AS/400?
> > >
> > >
> > >
> > >+---
> > >| This is the Midrange System Mailing List!
> > >| To submit a new message, send your mail to
>MIDRANGE-L@midrange.com.
> > >| To subscribe to this list send email to
>MIDRANGE-L-SUB@midrange.com.
> > >| To unsubscribe from this list send email to
>MIDRANGE-L-UNSUB@midrange.com.
> > >| Questions should be directed to the list
owner/operator:
>david@midrange.com
> > >+---
> > >
> > Carl J. Galgano
> >
> > http://cgalgano.home.mindspring.com
> > mailto:cgalgano@ediconsulting.com
> > EDI Consulting Services, Inc.
> > 540 Powder Springs Street
> > Suite C19
> > Marietta, GA 30064
> > 770-422-2995
> > +---
> > | This is the Midrange System Mailing List!
> > | To submit a new message, send your mail to
>MIDRANGE-L@midrange.com.
> > | To subscribe to this list send email to
>MIDRANGE-L-SUB@midrange.com.
> > | To unsubscribe from this list send email to
>MIDRANGE-L-UNSUB@midrange.com.
> > | Questions should be directed to the list
owner/operator:
>david@midrange.com
> > +---
>
>
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to
>MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to
>MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
>MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list
owner/operator:
>david@midrange.com
> +---
>+---
>| This is the Midrange System Mailing List!
>| To submit a new message, send your mail to
MIDRANGE-L@midrange.com.
>| To subscribe to this list send email to
MIDRANGE-L-SUB@midrange.com.
>| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
>| Questions should be directed to the list owner/operator:
david@midrange.com
>+---
>
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to
MIDRANGE-L@midrange.com.
| To subscribe to this list send email to
MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
