RE: SNADS over Anynet

Option one is not happening with this client. They're pretty, uh,
'Frugal'. 

Not sure what you mean about 'share'. But I can check it out. I guess I
could set up a 'dummy' remote outq and monitor it for any spooled files
that are dropped into it, then move them to the Twinax Queue. Seems like
a bit of work, though. Half to think that one through.

Thanks for the suggestions. 

Mark. 


Mark Walter
Senior Programmer/Analyst
Hainey Business Systems
(717) 718-9601 x7148
mwalter@xxxxxxxxxxx
http://www.hbs-inc.com
 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, October 05, 2005 11:17 AM
To: Midrange Systems Technical Discussion
Subject: RE: SNADS over Anynet

Convince your management that they might potentially increase the uptime
of the printer by switching from twinax to lan.  If systema is down then
systemb can still print to it.

Or, can you set up the twinax printer as a 'share' and access that some
way?  I have some PC technicians do most of the printer configuring
around here and I'm a bit rusty on it.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Mark Walter" <mwalter@xxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
10/05/2005 10:01 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
RE: SNADS over Anynet






Well, let's take this a bit further. SNADS isn't an absolute must if I
can find a way to print from one system to another using Twinax attached
printers. This is my first foray into multi iSeries networks. 


Mark Walter
Senior Programmer/Analyst
Hainey Business Systems
(717) 718-9601 x7148
mwalter@xxxxxxxxxxx
http://www.hbs-inc.com
 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, October 05, 2005 10:56 AM
To: Midrange Systems Technical Discussion
Subject: Re: SNADS over Anynet

I used to have this problem with regular SNADS on occasion.  Somewhere
there will be an obscure code that IBM will not publish on a publicly
available web site (at least back when we still used snads).  I think
you'll be referred to 'SNA formats' or some such manual.  Sometimes
varying off the controllers on both machines, deleting the device
descriptions associated with the controllers, varying on the controllers
and letting them rebuild the devices helped.  SNA is just kind of shaky
that way.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Mark Walter" <mwalter@xxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
10/05/2005 08:18 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
<midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
SNADS over Anynet






Hello all,

I'm having a problem doing SNADS stuff over Anynet. I have two systems 
that are tied together with a T1. Let's call them SystemA and SystemB. I

can VPN into SystemA's network, start a session and establish a Passthru

session to SystemB. I can SNDNETSPLF or SNDNETMSG from SystemB to
SystemA. 
But not from SystemA to SystemB. Make sense? 

Thanks,

Mark.

Mark Walter
Senior Programmer/Analyst
Hainey Business Systems
(717) 718-9601 x7148
mwalter@xxxxxxxxxxx
http://www.hbs-inc.com