Re: Put to Host and Skeletons

[haklui@xxxxxxxxxx]

David:

I do not know what the design is for this.  Indeed, you can see the
original copy source on the properties after the rename.
I will check to see if what can be done to avoid this hassle.

So for the time being, maybe you have to use the editor to 'save as' on the
host.


Hak Lui
AS/400 AD, IBM Canada Ltd.
e-mail: haklui@ca.ibm.com




                    David Wright
                    <dwright@celsinc.c       To:     "CODE400-L (E-mail)" 
<CODE400-L@midrange.com>
                    om>                      cc:
                    Sent by:                 Subject:     Put to Host and 
Skeletons
                    code400-l-admin@mi
                    drange.com


                    02/09/02 05:05 PM
                    Please respond to
                    code400-l





Hi All,

Maybe I am missing a simple solution here...

I have a few 'skeleton' programs that I routinely use as the base for a new
app.  In the old days, I would edit the existing program, then 'Save As' to
a new name.

This works fine with CODE when you are working on a Host-based source
member.

The problem is that if you Get from Host, modify, and save as to a
different
name (or just rename it), you will blow away the original source when you
do
a Put to Host...

CPO keeps track of where you got the source, and puts it back even if you
changed the name...

Is this by design?
Is there a better way to handle this?
Or should I always do my copy or rename on the Host first?

Thanks,
David

_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.