On Thu, Feb 4, 2021 at 5:35 PM Mark Waterbury
<mark.s.waterbury@xxxxxxxxxxxxx> wrote:
The main problem with FTP is, you must manually adjust the source member (SEU) type and member text after the FTP GET or PUT command, for each member.
As Thomas already indicated, your DDM suggestion works well for him,
and I'm sure most other midrangers.
But for whatever reason, I have always had trouble getting DDM to
work. And all the other common methods seem clunky to me. That's
without even accounting for trying to cross too many versions.
So what I did (and admittedly, this is a fairly long way to go for
initial setup) was to use iSeriesPython on both sides, with one side
being an RPC server and the other being an RPC client.
The current version of iSeriesPython is definitely obsolete, in terms
of the Python world, but it does have the property that it installs on
V5R3 and up, so it would work for OP's situation (transferring between
V5R4 and 7.3). And even old Pythons are really, really great
languages.
Python's standard library already comes with the RPC stuff ready to
use, and even has an example in the docs which I used almost verbatim
as a starting point. I created little PDM shortcuts for the various
functions, and now I just use those options to transfer from the "Work
with Members Using PDM" view. Once set up, if you have a PDM-centric
workflow (which I realize not all of you do, but then again, not all
of you have the need to even touch a V5R4 machine anymore either),
this arrangement is extremely slick, easy, and fast.
My iSeriesPython code handles the (re)setting of member type and text.
I also have an option for comparing members across systems (quick and
easy way to verify that they're the same on both sides).
It was fun to build, and now very nice to use. Hard to imagine
anything faster or more convenient, if you use PDM. I'm happy to share
code and discuss with anyone, if interested.
John Y.
midrange.com
