×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 20-Feb-2015 13:06 -0600, Jerry Draper wrote:
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.
The intended implication is that access to /QDLS must not be done
within a multi-threaded process.? Presumably whatever was the issue has
since been resolved by a PTF.?
Since I seemed to recall such a discussion, I found the following
message [oddly I wrote /QDLO vs /QDLS] where I imply the described
failure should result in an APAR to ensure IBM documented the problem
and if\what they were offering as resolution:
<
http://archive.midrange.com/midrange-l/201401/msg00035.html>
The topic thread spanned two months:
<
http://archive.midrange.com/midrange-l/201312/threads.html#00528>
<
http://archive.midrange.com/midrange-l/201401/threads.html#00026>
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.
Sure. But much easier to say than to do; doing that surely depends
greatly on the level of dependence on the older features and the
resources to effect the necessary changes, as well as if the replacement
feature is able to provide the same or equivalent capabilities as the
old feature. The old stuff should continue to work on N+1 except
whatever is documented in the MTU as being removed or replaced.
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.