|
midrange.com
Rick,
I am a little confused as to exactly what you are trying to do.
I assume that you are using WDSC 4.0 SP3.
You have downloaded the payroll example and there is an RPG program you
want to verify that references some database and display files in a
library.
You find the RPG member in RSE and then you launch the Classic CODE Editor
on that member from within RSE.
You then do a verify from within the editor and the verify fails because it
cannot find the database or display files in the library list.
Is this the scenario?
Other people have run into problems where there is a similarly named object
found in a library at the top of the library list.
---------------------------------------------------------------------------------------------
Edmund Reinhardt, AS/400 AD Tools, reinhard@xxxxxxxxxx
Dept 607, IBM Canada Lab TL 969-4392 Phone 905-413-4392
|---------+-------------------------------->
| | "Chevalier, Rick" |
| | <Rick.Chevalier@xxxxx|
| | credit.com> |
| | Sent by: |
| | code400-l-bounces@xxx|
| | range.com |
| | |
| | |
| | 2003/04/04 10:00 |
| | Please respond to |
| | CODE/400 Discussion &|
| | Support |
| | |
|---------+-------------------------------->
>---------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: "'CODE/400 Discussion & Support'" <code400-l@xxxxxxxxxxxx>
|
| cc:
|
| Subject: RE: CODE400 library list in WDSc environment
|
|
|
|
|
>---------------------------------------------------------------------------------------------------------------------------------|
Don,
I think your reply is right on. Here's how it's going.
What I really want to be able to do is use your last suggestion, manipulate
the library list dynamically. When I issue the ADDLIBLE command the
completed successfully message is received and displaying the library list
shows the library. There is no change when verifying the program however.
Thinking it might be related to the server I switched servers (don't know
why I have more than 1) and added the library to the library list there
also. Same result. I even closed CODE, returned to the RSE and opened the
source member again.
Next I tried your suggestion for adding the library to the library list in
the RSE. I opened the iSeries Objects properties and added the library to
the library list. I then restarted RSE. The library doesn't show in the
library list drop down under iSeries Objects-> Default Filter Pool but does
show in the library list if I open a member in CODE and issue the DSPLIBL
command from the command shell. When I verify, the file is still not
found.
Lastly I tried placing the library in the library list using the
communications daemon. I ended all the servers and started CODE again.
Same result.
FYI I am working on a CODE/400 lab downloaded from one of the IBM sites.
Things go fine until I need to verify the payroll program code.
Rick
-----Original Message-----
From: Don Yantzi [mailto:yantzi@xxxxxxxxxx]
Sent: Thursday, April 03, 2003 8:57 PM
To: CODE/400 Discussion & Support
Subject: Re: CODE400 library list in WDSc environment
Rick,
Are you opening the member from within the CODE editor directly or are you
launching the CODE editor on the member from the RSE in WDSc? If you are
using CODE editor exclusively then you can add the library to the library
list for the CODE server in the library list page in the CODE
communications properties (right click on the Communications daemon and
select Properties).
If you are launching the CODE editor from the RSE then you should add the
library to the library list for the RSE connection. Right click on the
iSeries Objects subsystem under the RSE connection and select properties.
Add the library in the library list properties page. In this case you may
need to shutdown the Workbench and the CODE communications to force the RSE
to re-register the RSE connection with CODE communications with your
updated library list settings.
The two options above both persist the setting so it doesn't get lost on
reboots, etc... If you just want to add the library dynamically you can
open the command shell and just run ADDLIBLE MYLIB. To open the Command
Shell just press F9, to switch which CODE server you are using select
Options -> Servers -> ....
Please excuse me if I am over simplifying the problem, I have only been
loosely following this thread. But you did ask for an easier way : )
Don Yantzi
WebSphere Development Studio Client for iSeries
IBM Toronto Lab
Phone: (905) 413-4476
IBM internal: IBMCA(yantzi) - Internet: yantzi@xxxxxxxxxx
"Chevalier, Rick"
<Rick.Chevalier@xxxxx To: "CODE400
Mailing List (E-mail)" <code400-l@xxxxxxxxxxxx>
credit.com> cc:
Sent by: Subject: CODE400
library
list in WDSc environment
code400-l-bounces@xxx
range.com
03/04/2003 06:43 PM
Please respond to
CODE/400 Discussion &
Support
Surely there's an easier way. I have tried to find documentation on adding
a library to the current library list used by CODE for a verify but without
success. Several of you have replied to a previous post with information
and pointed me to archived posts with macros for setting the library list.
After two days I know more about the editor but am no closer to solving my
problem. I'm sorry for the repetition but I really want to figure this
out.
I have tried adding the library to the job description on the AS/400,
pointed my user profile to the job description and even going into the WDSc
filter and specifying the library as part of the library list. When I try
to verify the program it still can't find the files. I have confirmed they
do indeed exist in the libraries I am trying to add.
One of the suggestions was to create a macro that changed the library list.
When I tried that an error of '-1' was returned and I was told to look at
the job log. Sounds good, but where is the job log? Trying to display it
from the CODE toolbar didn't work. Maybe if someone can tell me how to
locate the server side job this might make sense.
I apologize if I'm rambling but it has been a very frustrating couple of
days trying to resolve this and I want to try and include as much
information as possible. Any help would be greatly appreciated.
Rick
_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/code400-l
or email: CODE400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.
NOTE: WDSc for iSeries disucssion has it's own mailing list.
Information can be found at
http://lists.midrange.com/cgi-bin/listinfo/wdsc-l
_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/code400-l
or email: CODE400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.
NOTE: WDSc for iSeries disucssion has it's own mailing list.
Information can be found at
http://lists.midrange.com/cgi-bin/listinfo/wdsc-l
_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/code400-l
or email: CODE400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.
NOTE: WDSc for iSeries disucssion has it's own mailing list.
Information can be found at
http://lists.midrange.com/cgi-bin/listinfo/wdsc-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.
