Re: Large workspace .log entires

Violaine,
        My setting for " Window->Preferences->Remote Systems->Logging" is to 
log only errors.  The only reason it came to light for me was I was going 
through the plug-in development articles.  Whenever I go into a perspective 
that opens the error log view and the log is big, its sits there and churns 
away attempting to do something for me for each log entry.  I do delete the log 
when I can remember, but it still grows.   

Since, "Apr 10, 2006 09:21:01.739" the log has reached 1065kb.  All I have done 
in these past two days has been RSE work.   I have started WDSC twice since 
this latest log began.  I only have two perspectives defined to be available 
when WDSC starts. They are the iSeries project and my own perspective for 
remote iSeries work (based on Softlanding's iSeriesEditing perspective). 

Since I sent this initially, I have consistently seen issues 1 and 4 appear.  

I ran the clean up option in the updater, hoping this would solve issue 4, but 
it has not. 

Thanks, Matt



-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On 
Behalf Of Violaine Batthish
Sent: Wednesday, April 12, 2006 10:36 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Large workspace .log entires

Hi Matt,

You can try to check your logging preferences for RSE (ensure it is set to
Errors only)
Window->Preferences->Remote Systems->Logging

I'm not familiar with Sample 1 (although it does appear to be DDS outline
view related)

Samples 2 & 3 happen when the communication wait timeout period has been
triggered (default 60 seconds) and you would have seen a message asking you
if you wanted to terminate the last request as it was taking too long.
This is deemed an error condition, so it will appear regardless of your
logging level.

Sample 4 is not iSeries stuff and I'm not familiar with this either.

I recommend deleting the workspace\.metatdata\.log file out periodically.

thanks,

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab

You know you've achieved perfection in design, not when you have nothing
more to add, but when you have nothing more to take away. - Antoine de
Saint-Exupéry



wdsci-l-bounces@xxxxxxxxxxxx wrote on 28/03/2006 03:05:04 PM:

> WDSC Team,
>
>    I am getting large logs.  There are many entries from the DDS
> source parse/verifier(?), entries from 5250 session job logs, RSE server
> job logs and plugin reports.  How do I set of the feature that puts the
> log entries (like the samples below)?
>    My Main reason for complaining about the log is when I go into
> the PDE perspective the error view chunks through the log, one entry at
> a time, processing which seems like one entry per second.  The
> perspective keeps refreshing after the error log view finishes with each
> step.  Once its done doing what ever the error log view does over the
> .log file, the system reacts as normal.  Is there a severity level
> option some where to not show items like the samples below?
>
>
> Thanks, Matt
>
> ***Sample 1***
> !ENTRY com.ibm.etools.systems.core 4 0 Mar 28, 2006 08:14:11.175
> !MESSAGE Might reparse because of delete after the 33th line
> '003300060328     A            AUGIFTC   R
> REFFLD(POSFLAG)'
>
> !ENTRY com.ibm.etools.systems.core 4 0 Mar 28, 2006 08:14:11.253
> !MESSAGE Might reparse because of delete after the 33th line
> '003300060328     A            AUGIFTC   R
> REFFLD(POSFLAG)'
>
> ***Sample 2***
> !ENTRY com.ibm.etools.systems.core 4 0 Mar 28, 2006 10:53:40.399
> !MESSAGE ISeriesCommunicationsDiagnostic.working: server job
> "D000D238A/PGMT/844130" is *ACTIVE
>
> !ENTRY com.ibm.etools.systems.core 4 0 Mar 28, 2006 10:53:45.137
> !MESSAGE ISeriesCommunicationsDiagnostic.working.D000D238A.job log: 400
> - RTVJOBA JOB(&JOB) USER(&USR)
>
> !ENTRY com.ibm.etools.systems.core 4 0 Mar 28, 2006 10:53:45.153
> !MESSAGE ISeriesCommunicationsDiagnostic.working.D000D238A.job log: 600
> - CHGMSGQ MSGQ(*WRKSTN) DLVRY(*BREAK) PGM(*LIBL/MSTCMSGDC)
>
> !ENTRY com.ibm.etools.systems.core 4 0 Mar 28, 2006 10:53:45.153
> !MESSAGE ISeriesCommunicationsDiagnostic.working.D000D238A.job log: 2600
> - RTVJOBA USER(&USER)
>
> ***Sample 3***
>
> !ENTRY com.ibm.etools.systems.core 4 0 Mar 28, 2006 10:52:44.227
> !MESSAGE ISeriesCommunicationsDiagnostic.working started.
>
> !ENTRY com.ibm.etools.systems.core 4 0 Mar 28, 2006 10:52:44.243
> !MESSAGE ISeriesCommunicationsDiagnostic.working: ping server 400DEVL
> successful
>
> !ENTRY com.ibm.etools.systems.core 4 0 Mar 28, 2006 10:52:45.677
> !MESSAGE ISeriesCommunicationsDiagnostic.working: list of active server
> jobs detected for user ID PGMT...
>
> !ENTRY com.ibm.etools.systems.core 4 0 Mar 28, 2006 10:53:33.354
> !MESSAGE ISeriesCommunicationsDiagnostic.working: server job
> "QZRCSRVS/QUSER/843611" is *ACTIVE
>
> !ENTRY com.ibm.etools.systems.core 4 0 Mar 28, 2006 10:53:40.274
> !MESSAGE ISeriesCommunicationsDiagnostic.working.QZRCSRVS.job log:
> CPF2110 Library QSYS2924 not found.
>
> !ENTRY com.ibm.etools.systems.core 4 0 Mar 28, 2006 10:53:40.274
> !MESSAGE ISeriesCommunicationsDiagnostic.working.QZRCSRVS.job log:
> CPF2104 Library ACMSLIB not removed from the library list.
>
> ***Sample 4***
> !SUBENTRY 1 com.ibm.esupport.client.SSCM4C 1 1 Mar 28, 2006 07:54:33.62
> !MESSAGE This plug-in (located at "c:\Program
> Files\IBM\Rational\SDP\6.0\eclipse\plugins\com.ibm.esupport.client.SSCM4
> C") was ignored because another version of the same plug-in (located at
> "c:\Program
> Files\IBM\Rational\SDP\6.0\eclipse\plugins\com.ibm.esupport.client.SSCM4
> C_1.0.1") was picked
> !SUBENTRY 1 com.ibm.esupport.client.SSCM6C 1 1 Mar 28, 2006 07:54:33.78
> !MESSAGE This plug-in (located at "c:\Program
> Files\IBM\Rational\SDP\6.0\eclipse\plugins\com.ibm.esupport.client.SSCM6
> C") was ignored because another version of the same plug-in (located at
> "c:\Program
> Files\IBM\Rational\SDP\6.0\eclipse\plugins\com.ibm.esupport.client.SSCM6
> C_1.0.1") was picked
>
>