×
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 03-Jul-2011 14:24 , Douthat, Trent A wrote:
<<SNIP>>
When I actually attempt to use the DDM file, I get an error
like so:
SBMRMTCMD CMD(WRKSPLF) DDMFILE(QTEMP/TEMPDDMF)
Cannot establish DDM connection with remote system.
<<SNIP>>
Ignoring SSH, concentrating only on the above snippet showing a
failing request to [further] describe the problem, I offer FWiW:
The first level message text of an error following a request message
is not a generally worthwhile and appropriate means to [further]
describe a problem. Presumably the quoted message text is from the
message identifier CPF9162 for which the second level text suggests to
"See previously listed message &1". Both the message identifier and the
replacement text for &1 probably would have been included if the text
had been copied either from a spooled joblog taken with filtering level
LOG(4 0 *SECLVL) or F6=Print [after F1=Help]; though with either, the
previous logged message(s) still could just as easily have been omitted.
Presenting the full second-level details from the spooled joblog
including the request message up to and including the final [exception]
message preceding the next request, is generally the more worthwhile
text to provide to describe a failure. From such a spooled joblog with
second-level text included, the message identifiers, the context of the
messages, and the message replacement data would all be available for
further review.
Of course having suggested that, there was no attempt to imply that
just having that [missing] data become available would surely provide
anyone with the necessary details to enable them to assist [beyond the
other details already provided, though snipped in the quoted text]. But
surely the more complete error details would be better than just some
first-level message text copied and pasted from an interactive joblog
[which apparently had not even expanded the message view with the use of
F10=Include detailed messages].
Regards, Chuck
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.