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



I have to laugh - you are telling all the terrible tales of tech support - how customers don't know that a screen shot from CALL QCMD after pressing F10 is just NOT adequate is beyond me. But then, I'm old, I guess - been here too long!

I've helped our tech support to know to go F1-F9 to customers for single messages - and to get the entire job log, as you say, for collateral-damage kinds of things.

Thx
Vern

On 1/11/2012 11:31 AM, CRPence wrote:
On 11-Jan-2012 05:59 , Vern Hamberg wrote:
You mention using F6=print after F1=Help - I've never used that and
probably will in the future.
Only for one specific message, when that message is already _known_
to be the only message for which details are necessary [or desirable at
the moment]; i.e. as requested by the technical person, of the user.
This method of doc collection is *very* poor for when the problem to be
described is incorrectly *assumed* to require only details from that one
message. The DSPJOBLOG with LOG(4 0 *SECLVL) is the better option for
more general collection.

What I HAVE used and recommend to our tech staff and customers is
F9=Display message details - the latter is good, in my view, for a
quick look, F6 looks great for sending the information to us here or
to some other tech support agent.
F9 details are the important details typically lacking from poor
attempts at doc collection for a message; i.e. the typical copy\paste or
print screen of a [menu or] command entry. However unfortunately, if
asked for the F9 details, then someone typically just gives a
print-screen of just those _other_ details, omitting all of the details
from the toggled-from form of the Display Message screen; i.e. going
from one means of providing insufficient information including
effectively only message identifier and text, to another providing
insufficient information including effectively only message identifier
and context.

I do not understand why they do not have a form of the Display
Message panel which combines all of the details for *EXPERT users :-( on
the initially [and thus only] presented Additional Message Information
panel.?

And speaking of that toggle, and the Display Message screen in
general, I presume they still have not _corrected_ F3 to really effect
an Exit :-( as the function key claims to effect. That Enter=F3=F12
from the F9 variant [the Display Message Details] is as incorrect as I
can imagine. And another reason all of the details should be available
to prevent having to f-key twice to exit.... yes I really hate that, it
is that obvious.

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.