Jeff,

That does suggest that there might be an issue with the library lists.  I 
wonder if IBM will do anything with it?  <sarcasm>After all, CODE is 'dead', 
right?</sarcasm>

I have noticed that it requires the file name and record format to verify, but 
I haven't needed to qualify the library name in anything that I've done.  Our 
standard is supposed to be to state record format name anyway, so that hasn't 
been a problem for me.

Dave Shaw

----- Original Message ----- 
From: "Jeff Young" <cooljeff913@xxxxxxxxx>
To: "Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
Sent: Monday, October 24, 2005 10:25 AM
Subject: Re: [WDSCI-L] Code Designer


> Dave,
> I worked when I placed the libraries in the *ALL server.
> Does this indicate that there is a (gasp) bug in the CODE Designer when using 
> separate library lists for different servers and no library list for the 
> *ALL, or do I need to do something special to tell it to ignore *ALL when 
> there are no libraries in it.
> I have not had to do this in the past.
> 
> Also, it seems that the CODE designer requires a fully qualified file name if 
> using the REF keyword at the file level.  I had a REF statement with the name 
> *LIBL/FILE and used the "R" in the DDS at the record field level to indicate 
> a referenced field.  Designer would not recognize the REF field until I 
> qualified the REF with a Library AND Record name.
> 
> Thanks,
> 
> 
> Dave Shaw <daveshaw@xxxxxxxxxxxxx> wrote:
> Jeff,
> 
> That's very peculiar. I wonder if something happened with the 5.1.2.6 patch? 
> I didn't have any problems with 5.1.2.5, and I'm not having any problems with 
> 6.0, but I haven't used 5.1.2.6.
> 
> As an experiment, have you tried setting a library list for the *ALL server 
> in CODE? It's probably not a good long-term solution, but it might produce 
> some additional info.
> 
> Dave Shaw
> 
> ----- Original Message ----- 
> From: "Jeff Young" 
> To: "Websphere Development Studio Client for iSeries" 
> Sent: Monday, October 24, 2005 9:21 AM
> Subject: Re: [WDSCI-L] Code Designer
> 
> 
>> Dave,
>> I am aware of that, and have set my library list in the CODE Communication 
>> Properties for the server name that RSE generates.
>> My problem is that CODE does not seem to recognize it.
>> I have shutdown the CODE server and restarted it as directed and still no 
>> change.
>> I have been using CODE for years now, and this is the first time that I have 
>> had this problem.
>> 
>> Thanks,
>> 
>> 
>> 
>> Dave Shaw wrote:
>> Jeff,
>> 
>> CODE doesn't use the RSE library list. You have to set up your library list 
>> in the CODE Communication Properties.
>> 
>> HTH.
>> 
>> Dave Shaw
>> 
>> ----- Original Message ----- 
>> From: "Jeff Young" 
>> To: "Websphere Development Studio Client for iSeries" 
>> Sent: Sunday, October 23, 2005 11:42 AM
>> Subject: [WDSCI-L] Code Designer
>> 
>> 
>>>I am using the CODE Designer from RSE to edit my display file source.
>>> I have setup a library list for the server that it created, but when I 
>>> load a source member that uses a REF file, the Designer does not seem to 
>>> use the library list associated with the server. It seems to be using 
>>> *no* library list at all.
>>> I am using WDSC 5.1.2.6, and CODE Designer 5.1.2
>>> Any ideas?
>>>
>>> Thanks,
>>>
>> Jeff Young 
>> Sr. Programmer Analyst
>> Dynax Solutions, Inc.
>> A wholly owned subsidiary of enherent Corp.
>> IBM -e(logo) server Certified Systems Exper - iSeries Technical Solutions 
>> V5R2 
>> IBM Certified Specialist- e(logo) server i5Series Technical Solutions 
>> Designer V5R3
>> IBM Certified Specialist- e(logo)server i5Series Technical Solutions 
>> Implementer V5R3 


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.