RE: SNADS

I doubt if SNA will ever go away - there's waaaaay too much critical
business data being transported using SNA.

Regardless, SNADS has basically four components:

Sending files (SNDNETF);
sending messages (SNDNETMSG) ;
sending spooled files (SNDNETSPLF);
and submitting jobs (SBMNETJOB).

Of course, you can always configure AnyNet and run SNADS over a TCP/IP
network, but in terms of TCP/IP only with no SNADS components, the only
thing you can't do is send a message across a network. You can send
files with FTP, and there are some packages that can give you pretty
much guaranteed delivery. You could also use MQ Series for that too.
Spooled files can be sent queue to queue with an output queue
definition. Programs can be executed on remote systems with REXEC.

And of course, you could build your own SNADS wannabe...

> -------- Original Message --------
> Subject: SNADS
> From: "Bob Kohlndorfer" <bkohlndorfer@xxxxxxxxxx>
> Date: Wed, January 05, 2005 1:06 pm
> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> 
> I am looking for some feedback on the use of SNADS.
> My understanding is that SNA may be going away.  
> I am looking at a product that can do the functionality of SNADS using TCP/IP.
> 
> My question is how much demand for a product like this exists in the midrange 
> market?
> 
> Thanks for your thoughts,
> Bob Kohlndorfer
> Unbeaten Path International
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.