Re: Copy program from one connection to another

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

 David

As far as I know, the only object type that can be copied from one 
connection to another is a save file. Programs cannot be copied. I have 
rdp7.6 and tried to drag a program from one to another - got your 
message. Tried dragging a save file, worked fine.

This is how things work now on the i - you have to make a save file of 
any object to get it to another system. I'm talking of using FTP - there 
is a way using the FileSvr.400 - whatever it's called - but that might 
not be available through the client.

I wish the client could do what SAVRSTOBJ does - then anything could be 
copy/pasted.

Now you can drag any member to another connection - just have to drop it 
on the container source file. You can't drop it within the content list 
of a source file, even though, to me, the icon shown while dragging 
suggests that you can, based on other windows behavior. Sigh!

That's my experience, anyhow - maybe I'm missing something, too.

Vern

On 10/6/2010 3:55 AM, David FOXWELL wrote:
> Hi,
>
> I'm having trouble with this on Rdp7.6. I don't remember such a problem on WDSc6, just that I didn't do it much because of the time it took.
>
> In Connection1, I drill down into my object filter (or the same if I drill into the libraries filter), select my program object right click and copy.
>
> In Connection2, I do the same. I have a filter pool with the same object filters. The library list for the connection determines the objects displayed. If I right click the paste option will show if I want to paste in the libraries filter. I select the library name, click paste and get :
>
> Invalid transfer operation
> The source mylib/mypgm OBJTYPE(*PGM),
>   cannot be transferred into the target myotherlib OBJTYPE(*LIB:TEST-CUR)
>
> Here, the target lib is the curlib for the connection. If I choose another library, I get no message, but no copy either.
>
> Bug or me?