Re: snads support

We ran into serious issues in V7R1 with SNADs and SNDDST where an older app was sending files from QDLS. The routine was failing because QDLS is single threaded and that created havoc with V7R1.

Certainly it is time to let go of QDLS and SNDDST at least in this situation. SNDSMTPEMM can send IFS files as attachments without SNADS.

Jerry


On 2/20/2015 11:00 AM, Jim Oberholtzer wrote:

What you need is enterprise extenders which is similar to and enables SNADS
but again, it's not distribution services. That's different. Example, in
order to make these commands work you do not need to start QSNADS subsystem
nor do you need the jobs that normally run in QSNADS running.

I know I'm being a bit pedantic about what's what, but it's important to
keep the distinction.

SNADS is hard to set up, no one remembers it anymore, and it's dated.
Enterprise Extenders while similar takes 10 minutes to get running, lot's
of folks know how to do it, and it's still current. Does it use APPC/APPN
yep, it does but that's not SNADS.

On Fri, Feb 20, 2015 at 12:09 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

The SAVRST* set of commands is what I'd need snads for - or they can work
over OptiConnect, if I read the help text rightly.

Is OptiConnect something that comes when using fibre channel networking?

On 2/20/2015 11:02 AM, rob@xxxxxxxxx wrote:

If strpasthr is the only command the 'users' are using of snads, it's
really easy to create a proxy command for telnet that uses that name.


Rob Berendt

--
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.