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



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 List
displays but my compile listing goes to the system printer.

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 on
the system printer.

My manager is set up the same way, batch compiles with Error List working
and compile listings not printing.

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 still
need the compile listing as I often write embedded SQLRPGLE programs. My
only other option that I can think of is to rebuild my workspace and hope
that it works.

Gene

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.