×
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.
Thanks ladies & gentlemen, for all the valuable information.
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Tom Liotta
Sent: Friday, July 17, 2009 9:39 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Transfering Objects & Source From between Systems
Larenzo Alexander wrote:
How do you transfer Objects and Source Codes between different Remote
System Connections with RSE? I normally use a SAVEFILE and FTP in a
5250
session. I copied an object from my production side and tried to
paste
it in a library on the development side, I received a message saying
it
could not do the transfer.
Larenzo:
For the systems in the network that I work within, I usually use two
general methods depending on circumstances.
For simple source file members, when I have the proper
communications setups available, I'll often use FTS through a PDM
option. Years ago (like a number of others here), I created a
command wrapper for QY2FTML to handle the parms. Works very slick
for PUTs and GETs when available.
For savefile transfers, I almost always have a savefile simply named
SAVF in my current library. I save whatever needs to be sent into
SAVF and start FTP. The FTP subcommands are almost always exactly
the same:
bin
na 1
put savf.savf
quit
Pretty straightforward. It even auto-creates the savefile in my
remote current library if I've never done it to there before. I just
re-use SAVF over and over.
Tom Liotta
midrange.com
