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



Bingo! That worked. On the first attempt to use verify, it was successful in filtering out all unwanted messages (severity 0 in this case) and it picked up on the display file changes. It's probably a setting that I set early on in my use of the product, and given I never referenced it again afterwards, forgot all about it.

Thanks!

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Susan Gantner
Sent: Wednesday, November 03, 2010 1:44 PM
To: 'Rational Developer for IBM i / Websphere Development Studio Clientfor System i & iSeries'
Subject: Re: [WDSCI-L] RDP V8.0 Verify option

Hi Ken,

The display file info is cached in your workspace, so you need to refresh
the cached info. Right click on the DSPF object in the Remote Systems view
and select Cache File Descriptions. Or else verify with prompt and select
the "refresh cache" option.

This would have happened in earlier versions of RDP as well.

Good luck.

Susan Gantner

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Tarr, Kenneth
Sent: Wednesday, November 03, 2010 2:16 PM
To: WDSCI-L@xxxxxxxxxxxx
Subject: [WDSCI-L] RDP V8.0 Verify option

One of the things I like to use is the Verify option. I've had to add a
library or two to the list to get it to work in our environment, but then I
can easily identify the lines that are in error, correct them, and see them
get checked off in the error list. Nice feature.

However, it's not working as before in RDP V8.0, and I am wondering if it's
an issue with our setup or if there's a legitimate bug out there. So here's
what I am doing:

-- First, I click Verify, and it doesn't pick up the latest changes to a
display file. Therefore all the fields I added to the display file are
considered undefined (RNF7030), which in turn causes other errors in the
program to surface.
-- Through the Commands Log tab, I enter an ADDLIBLE command with the
library the display file is checked out in. (This required a STRRSESVR on a
session to also allow me to use the EDTLIBL command to verify it's there,
and even once I tried to add the library there at the beginning of the
list.) The source is located in the library I am specifying where the
display file object is located.
-- On my next attempt to click Verify, there's no change. It continues to
recognize the earlier version of the display file, without my changes.
-- Through the Remote Systems Detail tab, I right click on the connection
and select Properties. In the window that appears, I click on Subsystems.
The Objects tab is now displayed, and I can add the library there. I do so,
and even specify *FIRST. I then disconnect, then reconnect, to make sure it
picks up the change (the Commands Log tab also shows this picked up).
-- On my next attempt to click Verify, again there's no change...same as
before.

It's probably something simple that I'm overlooking. Or...is this now a
bug?

Any assistance would be appreciated. FYI, we use Aldon LM(i) as our
checkout tool. What I am doing is outside this tool, but again what I've
done worked prior to V8.0.

Ken Tarr
Associated Banc Corp
Green Bay Service Center, Mail Stop 7055 2870 Holmgren Way, Green Bay, WI
54304 www.associatedbank.com This e-mail and attachment(s) may contain
information that is privileged, confidential, and/or exempt from disclosure
under applicable law. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution, or
copy of this message is strictly prohibited. If received in error, please
notify the sender immediately and delete/destroy the message and any copies
thereof. Although Associated Banc-Corp and/or its affiliates (collectively
"Associated") attempt to prevent the passage of viruses via e-mail and
attachments thereto, Associated does not guarantee that either are
virus-free, and accepts no liability for any damage sustained as a result of
any such viruses. Any federal tax advice contained in this communication
(including any attachments) is not intended or written to be used or
referred to in the promoting, marketing, or recommending of any entity,
investment plan or agreement, nor is such advice intended or written !
to be used, and cannot be used, by a taxpayer for the purpose of avoiding
penalties under the Internal Revenue Tax Code

--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & 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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.