|
From iSeries Error list:Click on the downward pointing triangle in the top right corner
under Show Severity, which message levels are checked?
Steven Morrison
Fidelity Express
903-885-1283 ext. 479
"Gene Burns" <burns.gene@xxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
08/10/2007 10:39 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
To
"Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
cc
Subject
Re: [WDSCI-L] iSeries Error List stopped working
I have it open. I keep it open, along with the iSeries Commands Log,
iSeries Table View, etc.
Gene
On 8/10/07, smorrison@xxxxxxxxxxxxxxxxxxx <smorrison@xxxxxxxxxxxxxxxxxxx>
wrote:
List
What happens if you open the iSeries Error List view? Try Window->Show
View->iSeries Error List.
Steve
Steven Morrison
Fidelity Express
"Gene Burns" <burns.gene@xxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
08/10/2007 10:26 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
To
WDSCI-L@xxxxxxxxxxxx
cc
Subject
[WDSCI-L] iSeries Error List stopped working
We are on v6, running V5R2. We have been compiling in batch for over 2
years in WDSC with no problems. The compile listing go to our own outqs
that do not have printers attached to them. The iSeries Error List
display
worked just fine.
Yesterday I stopped getting the iSeries Error List when compiling. My
preference settings are still set to compile in batch and my listings go
to
my outq.
If I change my preferences, by unchecking Compile in batch either in
Windows
-> Preferences -> Remote Systems -> iSeries -> Command Execution OR in
iSeries Objects -> Properties -> Command Execution the iSeries Error
displays but my compile listing goes to the system printer.on
I already have an initial command to set my library list.
I have tried an override command, from the command line in the Commands
Log
view before compiling interactive but my compile listing still printed
the system printer.working
My manager is set up the same way, batch compiles with Error List
and compile listings not printing.still
Does anyone know of a way to get the Error List to show up again when
compiling in batch or to stop the compile listing from printing. I
need the compile listing as I often write embedded SQLRPGLE programs. Myhope
only other option that I can think of is to rebuild my workspace and
that it works.--
Gene
--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.
--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.
--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.
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.