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



Mike,

Search your C: drive for the source member name.  You should find several xml 
files (and some associated resource files) for that source member.  You may 
need to exit WDSCi before you delete these.  Once deleted, then start WDSC and 
refresh your outline.

This is just a blind stab in the dark, but this seemed to fix MY problem.  As I 
recall, the problem had to do with the cache used for iSeries projects.  It was 
some time ago, and I tried so many things, so perhaps I'm not remembering what 
I should....  Still, worth a look....

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-297-2863 or ext. 1863



-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of Mike
Sent: Monday, July 03, 2006 2:02 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Physical File Information Not Coming Into WDSc


I just installed WDSc lite and it refreshed the outline properly. Is there a
way to force a cleanup or something? Not sure where I need to go to get this
to work.

On 7/3/06, Mike <koldark@xxxxxxxxx> wrote:

I am doing a read and a chain to the file. Still nothing.


On 7/3/06, Rick.Chevalier@xxxxxxxxxxxxxxx < Rick.Chevalier@xxxxxxxxxxxxxxx>
wrote:


Mike,

I have experienced an issue with the outline where the file definition
is not included until the file is referenced in the calculations.  I
would add the F-spec then update the outline.  The file appeared but
drilling down wouldn't get the fields.  Adding a file op-code did the
trick.  IIRC someone from IBM gave me this tip a while back.  It should
be in the archives.

HTH,

Rick

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike
Sent: Monday, July 03, 2006 11:53 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Physical File Information Not Coming Into WDSc

Weirder yet... verify works. Seems to be something only with
the outline.

On 7/3/06, Mike <koldark@xxxxxxxxx> wrote:

Any other ideas on this?

Files I have just created are not coming into WDSc. Old
files before
this project come in just fine and new display files come in just
fine. The files are in the library list (although lib is called
QMFILES). I have cleared the cache several times and done
the verify
with clearing cache. None of that works. At one point they
where in a
different library but got moved to QMFILES (the main DB
lib), could this cause a problem?

--

Mike Wills
koldark@xxxxxxxxx
http://theriverbendpodcast.com

Privileged and Confidential.  This e-mail, and any attachments there to,
is intended only for use by the addressee(s) named herein and may contain
privileged or confidential information.  If you have received this e-mail in
error, please notify me immediately by a return e-mail and delete this
e-mail.  You are hereby notified that any dissemination, distribution or
copying of this e-mail and/or any attachments thereto, is strictly
prohibited.

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




--

Mike Wills
koldark@xxxxxxxxx
http://theriverbendpodcast.com





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.