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



Hi Violaine,
 
I recently applied Interim Fix 6.0.1.2, but I am afraid it seems to have
made no difference - if I submit a command from WDSC and examine the
Commands Log view, I still only see the first 32 messages that the
command has output.  
 
I can see that 6.0.1.2 has made a difference when WDSC commands are run
interactively:
Before 6.0.1.2 the Commands Log view seemed to show the first 10 msgs
that were sent to the interactive job's msgq after the command had
started.
After 6.0.1.2, the Commands Log view seems to show all the msgs in the
interactive joblog that were sent after the command had started.
 
Surely this can't be right!
 
If a command completed normally, I used to just get a single completion
msg confirming that the command was successful. Now I also get numerous
irrelevant operating system msgs.
If a command failed, I used to just get diagnostic msgs explaining the
problem. Now I have to trawl through the joblog msgs to find these
diagnostics.
 
I guess I just cannot see the logic of dumping the joblog to the
Commands Log view. Commands are normally designed to diagnose their own
problems and give suitable msgs. Surely the joblog is an instrument of
last resort.
And anyway, even when I have had to resort to the joblog, it's only a
few clicks away:
--> iSeries Jobs --> My active jobs --> QUSRWRK -->
999999/QUSER/QZRCSRVS --> Display job log
(An option to be able to see the 2nd level text for the msgs would be
nice!)
 
I was hoping that 6.0.1.2 would simply remove the limits on the number
of msgs returned to the Commands Log view - i.e. 10 msgs for interactive
commands, 32 msgs for submitted commands.
 
Am I missing something?
 
Regards,
 
John Skehan       
 
 
 
 
 
Hi John,
 
This is a bug in the command log.
See APAR SE26008 (will be fixed in iFix 2):
http://www-1.ibm.com/support/docview.wss?rs=715&context=SSZND2&dc=DB550&;
uid=swg1SE26008&loc=en_US&cs=utf-8&lang=en
 
thanks,
 
Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab
 
 
 
wdsci-l-bounces@xxxxxxxxxxxx wrote on 07/06/2006 11:14:52 AM:
 
Hi,
 
 
 
I wonder if anyone can help.
 
 
 
We have a command that outputs many messages.  If I submit this command
from WDSC and examine the iSeries Commands log view, I only see the
first 32 messages that were output.
 
Is there a setting that I can change to increase the number of messages
that are returned from a submitted job?
 
 
 
We are on WDSC Version 6.0.1  Build 20050725_1800
 
 
 
Regards,
 
 
 
John Skehan
 

 

 


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.