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



Phil,

I don't think I understand your question. Is the CPD7902 being filtered
by the 'Show Severity' menu? If you get CPD7902, 'File specified on
keyword not found.' that's accurate as far as the error goes, it's not
finding a physical by that name which the compiler can access. If you
want more, you could write some custom code to record the information in
the event file. The format of the events file is documented (version 7.0)
in help under "Websphere Development Studio Client for iSeries",
"Reference", "User interface reference". I found it by searching on
'events file format' in help contents.

wdsci-l-bounces@xxxxxxxxxxxx wrote on 12/02/2009 01:00:08 PM:
----- Message from ssc1478 <ssc1478@xxxxxxx> on Wed, 2 Dec 2009 10:
08:13 -0500 -----

To:

Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>

Subject:

[WDSCI-L] compile feedback for LF's when you don't have authority to the
PF

Is there a way to get compile feedback for LF's when you don't have
authority to the PF? From what I can tell, the only place there is an
indication of a problem is in the Commands View. But there appears to
be nothing prompting you to look there since the Error List view says
"Events file contains no messages".

The spooled file has both CPF3223 and CPF7302 in it. Is there a way
to get those messages into the event file?

If the PF doesn't exist, then the error list gets CPD7902.

Thanks,

Phil

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.