|
Sorry I could not answer before Kushal, one of those "focus on this and leave everything else" things happened. I think makes it makes sense to do it using iSeries Project as you mentioned. However, the purpose was not to have an off-line project (I.e. named something like "Miscellaneous") to do this kind of development; I just wanted to have something quick for those quick fixes that always happen. I guess the question would be, maybe it does not work the way I was trying to do it even though IBM's tutorials use the iSeries as one of the servers to achieve it? Again, you can check the "End-to-End development using the RSE" tutorial. Thank you very much for your help, and thank you also to Rob Berendt for quick response and help. Martin -----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Kushal Munir Sent: Wednesday, September 14, 2005 12:44 PM To: Websphere Development Studio Client for iSeries Subject: Re: [WDSCI-L] Problems Importing/Editing iSeries code in RSE Hi Martin, Are you using iSeries Projects to store your source locally? From RSE, you can right click on a member or source physical file and add it to an iSeries Project. You can then edit and verify the member locally, and submit builds to your DEV LPAR, before exporting it to PROD LPAR (by changing the associated connection and library). Cheers, Kushal Munir Websphere Development Studio Client for iSeries IBM Toronto Lab, 8200 Warden Ave., Markham, ON Phone: (905) 413-3118 Tie-Line: 969-3118 Email: kmunir@xxxxxxxxxx "Moraga, Martin" <Martin.Moraga@bb dodetroit.com> To Sent by: <wdsci-l@xxxxxxxxxxxx> wdsci-l-bounces@m cc idrange.com Subject [WDSCI-L] Problems 09/14/2005 11:26 Importing/Editing iSeries code in AM RSE Please respond to Websphere Development Studio Client for iSeries Hello, This is what we need to do: we have two partitions on our system (I.e Prod and Dev); for simple modification projects we wanted to create a simple project in RSE, create two connections (One for each LPAR), and then import code from the source files to the local workspace, edit the code there, save it, export it to the DEV LPAR, test it there, and once is OK, export the fine tuned code from the local workspace to the PROD LPAR. However, 1) Since we have hundreds of libraries and source physical files within them the first time it takes forever to browse the connection to either Remote server (Later it gets much better but only up to the point when I get the SRC-PF where it takes forever again to show me the members. 2) It does not recognize the type of the sources (I.e. CL, CLLE, RPG38, RPGLE, etc.) when browsing them so I can import only ".MBR" resources, which brings problem 3. 3) When trying to open an RPGLE member, since the import has returned the source as "xxx.mbr" it takes forever to open it and then it shows a corrupted horizontal screen with thousands of columns and corrupted code. 4) When I rename the member (To have extension RPGLE) it does the same thing. It does not crash but it does work. I do not know if I am missing something, but it does not work as it is supposed to. I have even seen a tutorial called "End to End Development using RSE" from the "Welcome" view and have followed the instructions which are the same to what I have done. I believe that tutorial has been made by Linux people and has not been tried with the iSeries. If somebody can help me I would really appreciate it. This message and any attachments contain information, which may be confidential or privileged. If you are not the intended recipient, please refrain from any disclosure, copying, distribution or use of this information. Please be aware that such actions are prohibited. If you have received this transmission in error, kindly notify us by calling 1-800-262-4723 or e-mail to helpdesk@xxxxxxxxx We appreciate your cooperation.-- 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.