×
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 07-Jul-2016 14:36 -0500, Roger Harman wrote:
<<SNIP>> What options would you suggest for the trace?
I suppose what John_Maassel has replied very recently will resolve.
But FWiW: For tracing I typically still [though mostly I am not
authorized, so I have no capability for any tracing] just use the
simpler but deprecated Trace Job (TRCJOB) command with the defaults
[possibly increasing MAXSTG setting for longer-running requests] for
starting, and then just TRCJOB *OFF [which defaults to OUTPUT(*PRINT)];
afterward the result used to be accessed with DSPSPLF QPSRVTRC
SPLNBR(*LAST), but the TRCJOB actually invokes a newer trace feature
[¿Start Job Trace (STRJOBTRC)?] that uses a different printer file [of
which I do not recall the name -- and the invocation by TRCJOB does not
effect an override to establish the SPLFNAME(QPSRVTRC) attribute to
ensure *compatibility* with the older feature :-( ].
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
