I did not mention that I consider the behavior "wrong". I was surprised that I noticed the behavior that late and I miss a "Replace initial library list" checkbox.
I have a whole bunch of different tiny things to do and a lot of those things require a different library list. Writing a CL for each new thing is not my prefered way.
Von: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxxxxxxxx] Im Auftrag von Justin Taylor
Gesendet: Donnerstag, 23. Januar 2020 14:53
An: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Betreff: Re: [WDSCI-L] RSE library list problem
Personally, I never considered the behavior "wrong".
We don't use the RDi library list. We just use the "Initial command" to call a CL to do the setup.
From: Thomas Raddatz [mailto:thomas.raddatz@xxxxxx]
Sent: Thursday, January 23, 2020 1:20 AM
Subject: [WDSCI-L] RSE library list problem
Although I use RDi for a couple of years, I did not yet notice the following problem before. But now I run into a problem when running a certain unit test. I always thought that the libraries that I specify at "Connection - Subsystem - Objects Tab - Library list" are used for building the library list when establishing a connection to a remote system.
But apparently that is wrong, since in fact the libraries are added to the initial library list of my user profile. For example:
This behavior makes it difficult to specify the proper library list for a connection. Sadly I cannot use "CHGLIBL *NONE" as the "Initial command" of the connection to clear the library list before, because the initial command is execute after the library list was built.
Of course I can fix the library list when I specify the libraries with "library position" *FIRST in reverse order. That is not nice and hard to read, but at last it works.
How do you specify the library list of your RSE connections to get the right list?
Things would be so easy if there was a checkbox "Replace initial library list" on the properties dialog of the RSE connection.
This email is confidential, may be legally privileged, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone else is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.