×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Your right on the money, I use iSeries Projects to help with the following:
1. Group code and build with a single step (Build CL gets created).
2. Work Offline, this works ok but does still require iSeries connection for
alot of the functions. Basically coding changes and try compile when iSeries is
available approach.
3. Keeps a local history of your source changes which doesnt happen in RSE.
4. Transfer projects from one iSeries to another. Just change the connection
and/or library property of the project. Easier ways for a few source members
but this is good for large amount of source.
Hope this helps
Don Nitke
Sr. P/A Friedman Corp.
----------------------------------------
From: "Rob Rogerson"
<rrogerson@xxxxxxxxxxxxxxxxx>
Sent: Monday, May 28, 2007 8:27 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: [WDSCI-L] Advise for new user...
I'm just starting to use WDSC 7.0. At this point my only concern is for
working with RPG related objects so RSE gives me most of what I want. I
have a question for experienced users who can advise me if my plan would
work or there is a better way of accomplishing what I wish to do.
I am assigned a project which may include 10 old programs, displays, CL,
etc. and 10 new. I would like to organize this in a way make it easier to
access the required source. If I create a new iSeries Project (File -> New
-> Iseries Project ) and add the source from RSE to the project ( right
click on source and add to project ) is this the correct approach or is this
not what projects in WDSc were intended for?
Regards,
Robert A. Rogerson
Senior Programmer/Analyst
Kohl & Frisch Ltd
Ext. 652
905-660-7622
rrogerson@xxxxxxxxxxxxxxxxx
www.kohlandfrisch.com
This message (including attachments, if any) is confidential, may be
privileged and is intended for the above-named recipient(s) only. If you
have received this message in error, please notify me by return email and
delete this message from your system. Any unauthorized use or disclosure of
this message is strictly prohibited.
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.