For many messages, the second level text is also required.  If it 
were just one [or maybe even a couple] message then F6=Print includes 
everything for each message.  If more than one message, best just to 
issue CHGJOB LOG(4 0 *SECLVL) and then request the DSPJOBLOG 
OUTPUT(*PRINT) which will give _all_ of the information in the QPJOBLOG 
spool file.  And if only several messages since the request message are 
of interest, then the snippet of joblog to include the request message 
up to the Escape which describes the failure or possibly up to the *FC 
message.  However to someone providing support, versus for example here 
on a public group, best not to short the information; i.e. best include 
the entire spooled joblog in most cases, because prior activity in the 
joblog might prove to be insightful, for diagnosing the origin of the 
problem.  For example for an ALTER against a PF over which a join 
logical exists, and the later ALTER over another PF which is the other 
based-on for that JLF, then seeing that prior activity may indicate the 
problem is specific to the existence of that JLF; and so supporting doc 
including the DBF network confirms the relations and shows the defined keys.
Regards, Chuck
vhamberg@xxxxxxxxxxx wrote:
To help out Mike and others - when you press F1 on the message, that
is not all you should do - once in the displayed message, press F9 to
get the stuff Chuck is talking about - the from and to information,
all that. <<SNIP>>
As an Amazon Associate we earn from qualifying purchases.
	
 
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.