×
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 06-Mar-2014 11:13 -0800, Dave Boettcher wrote:
<<SNIP>> Bit of a challenge. <<SNIP>>
A trace is likely to be very revealing. Used to be TRCJOB *ON,
perform the failing request, and then TRCJOB *OFF. Though in this or
similar scenarios whereby the problem involves some authority [or
capability] issue(s), perhaps those TRCJOB requests should be invoked
from a user\job that has previously requested STRSRVJOB against the job
that will exhibit the failing request. I presume using those TRCJOB
invocations is still supported, although the underlying implementation
was actually changed to: STRTRC, ENDTRC, and then another /print trace/
feature [of which I do not recall the name].
This mailing list archive is Copyright 1997-2025 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.
midrange.com
