|
What if one is using the connection to access/compile source from multiple locations on the iSeries? Do you need to include every possible library on the libl for it to work or are you supposed to create a connection for each "environment" you are likely to be using ? Either way seems to be a large overhead. Would it not be better if the function that builds the outline looked in the same library as the source member being outlined to get the references? -----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Nazmin Haji Sent: 21 February 2006 16:25 To: Websphere Development Studio Client for iSeries Subject: Re: [WDSCI-L] Source outline problems Hi, If your source does contain external descriptions or /copy members, these should be present in your library list. The same idea as verifying the program. If the program verifier does not find the external descriptions nor will the outline view. Regards, Nazmin Haji "Kevin Turner" <kevin.turner@cor altree.co.uk> To Sent by: <wdsci-l@xxxxxxxxxxxx> wdsci-l-bounces+h cc aji=ca.ibm.com@mi drange.com Subject [WDSCI-L] Source outline problems 02/21/2006 07:46 AM Please respond to Websphere Development Studio Client for iSeries I logged this once before but don't recall seeing anyone responding. I am getting worried that it is unique to my PC ! I have a standard iSeries Connection in RSE. I have RPGLE service programs that have all their exported procedures prototyped in external /copy members. When I try to refresh the outline of these service members, it very often gives me **UNDEF** against each of the exported procedures - as if it could not find the /copy member containing the prototypes. Sometimes it works and sometimes it does not. What does the outline builder rely on to ensure it can get all the information it needs? Do I need to set the library list on the connection in anyway? If so, what if I am using RSE to explore source from various locations? Any help gratefully received. "NOTICE: The information in this electronic mail transmission is intended by CoralTree Systems Ltd for the use of the named individuals or entity to which it is directed and may contain information that is privileged or otherwise confidential. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email or by telephone, so that the sender's address records can be corrected." -- 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. -- 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.
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.