×
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.
Actually, I think there need to be two filter strings if you might have
any source files originally generated on the System 38. (Yes, we do and
some of the code still runs great--unchanged since the S/38 days.) The
way filter strings are displayed can appear confusing. The filter string
is displayed as *FILE:PF-SRC and/or *FILE:PF38-SRC. Going with just the
PF-SRC string would return any source files generated since the 38 days,
but PF38-SRC is required to get the rest of the possible source files.
Could it be a typo? Attribute should be 'PF-SRC', without the asterisk.
Joep Beckeringh
"Bill Barnes" <bbarnes@xxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
21-09-2007 17:04
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
To
<wdsci-l@xxxxxxxxxxxx>
cc
Subject
[WDSCI-L] V7
I just loaded V7 on my laptop. I am trying to duplicate the workspace
from my desktop. I have created the workspace OK but when I try to
create an object filter like I do in V6 there is a problem.
I right click on iSeries Objects and select object filter Library:
GPSTEST Object:Q* Object Type:*File Object Attribute: *PF-SRC.
After doing the previous and giving it a name the filter name pops up
but when I click it, it says it is any empty filter.
I have gone back to V6 and tried adding a new filter as above and it
does show all pf_src that begin with Q. Is there something different
about V7 filters?
Thanks
Bill Barnes
Sr Analyst/Programmer
The Pantry, Inc
919-774-6700
ext 5211
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.