Brian:
I did contact Aldon and they said to shorten up the Workspace path. It was a long path of 50 to 60 characters in length, which when the rest of the path information was added for other functions outside of WDSC, exceeded the 128 character limit, causing the problem. I did shorten up the Workspace path, and it corrected the issue.
Thanks!
Ken
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of BMay@xxxxxxxxx
Sent: Friday, September 11, 2009 2:35 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Adding filters with Aldon LM(i) causing problems
Have you contacted Aldon? I have always had good experiences with their
support. Are you sure you have the right version of the plugin for your
version of WDSC?
Brian May
Project Lead
Management Information Systems
Garan, Incorporated
Starkville, Mississippi
Young i Professionals
http://www.youngiprofessionals.com
"Tarr, Kenneth" <Kenneth.Tarr@xxxxxxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
09/11/2009 09:30 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
To
"'wdsci-l@xxxxxxxxxxxx'" <wdsci-l@xxxxxxxxxxxx>
cc
Subject
[WDSCI-L] Adding filters with Aldon LM(i) causing problems
Long time WDSC user, first time poster... :)
We use Aldon LM(i) with our WebSphere product (WDSC 7.0). I am trying to
create a filter to access different objects (program source, etc.) and am
able to do so successfully. However when the PC is rebooted, I am greeted
with an error message, and after the PC reboots, the filters are lost. (In
fact, any PC settings for that session appear to be lost, too.)
Here's how I do it: I right click on "Aldon LM(i)" in the Remote Systems
view, selecting New...Aldon LM(i) Filter... I then make my selections in
the first view (Group, Application, Release, etc.). On the second view, I
provide a Filter Name. I have a checkbox "Only create filter in this
connection". Here's where the issue starts. If I leave this box checked,
the filter is successfully created. I can create more filters at this
point too. When I exit WDSC and reenter the application, the filters are
still there. It's when I reboot the PC that I receive an error message
saying I couldn't save a file (I believe it's a roaming profile). The
error message in short is "Filename is too long". When the PC reboots, I
go back into WDSC, and note the filters are missing. If I leave this box
unchecked, I then have to select a profile. I have two profiles: Team,
and a profile which is comprised of my machine name. I select the machine
name, the filter is created, and rebo!
oting the machine doesn't cause the error. However I can't create
another filter with the machine name...and I need more than one filter to
view different areas of source members. I did find a workaround...I can
Copy the filter, which appears to let me create more filters...and
rebooting doesn't cause a problem. However this creates more than one
connection (?) to the System i. Ten filters...ten connections?
The purpose of the filters are several, including being able to quickly
access source listings to review a program, doing source compares between
two members in different filters, etc...lots of different things which I
have found easy to do this way.
So my question is...how do I get it to NOT lose my filters when the box is
checked, and subsequently lose any WDSC settings made during the current
PC session? Is there some other setting(s) I can check to eliminate this
issue?
Thanks in advance...
K. R. Tarr
*********************** NOTICE***********************
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
midrange.com
