RE: Getting errors back from CRTICFF -- WDSCI-L

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

There's no reason to go back into SEU.

Simply download Softlandings free Spool file plugin for WDSc.  Then you can 
pull up the spool file in WDSc, do a split screen between the source and the 
spool file and use Ctrl-F to find the errors.

HTH,

Charles Wilt
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: wdsci-l-bounces@xxxxxxxxxxxx
> [mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of Dave Shaw
> Sent: Thursday, January 20, 2005 4:21 PM
> To: wdsci-l@xxxxxxxxxxxx
> Subject: Re: [WDSCI-L] Getting errors back from CRTICFF
> 
> 
> Sarah,
> 
> When I get caught with stuff like that, I always end up 
> taking the low-tech approach - go to the green screen, browse 
> the member in SEU, use F15 to pull up the spool file in split 
> screen, and then use the old F *ERR search.  I hate it - but 
> it still works, while we wait for IBM to come up with a better way.
> 
> Dave Shaw
>

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.