Re: FTP security question...

What I meant to say is that SAVRST now works over an *IP connection, or an *SNA connection, at V7R4 and above.

On Wednesday, April 10, 2024 at 10:44:58 PM EDT, Mark Waterbury <mark.s.waterbury@xxxxxxxxxxxxx> wrote:

Hi, Bryan,
You are (of course) correct, sir.   What I was referring to is that with V7R4 and above, you no longer need AnyNet or Enterprise Extenders to create an *SNA connection (for SNADS) between the systems.   
With SAVRST at V7R4 and above, IBM now works over an *IP connection.
Mark
    On Wednesday, April 10, 2024 at 10:36:26 PM EDT, Bdietz400 <bdietz400@xxxxxxxxx> wrote: 

Mark, the SAVRST* commands have been around for a long time.  LPP is Object Connect. 
When it first came out it was a “with cost” licensed program.  Somewhere around V3R2 it became “no charge”.  I recall that IBM did it to assist with CISC-RISC migrations.
It was not a good fit for those as it was slower than 8mm tape. :-)

--
Bryan Dietz

On Apr 10, 2024, at 8:13 PM, Mark Waterbury <mark.s.waterbury@xxxxxxxxxxxxx> wrote:

 SAVRST is okay but it only works on V7R4 or V7R5, not V7R3 or prior.
    On Wednesday, April 10, 2024 at 07:39:51 PM EDT, Glenn Gundermann <glenn.gundermann@xxxxxxxxx> wrote: 

Hi Rob,

SAVRST is the easiest but SNDNETF is also easy.

For SNDNETF, first check that your SNADS is working.  Do a SNDNETMSG to the
other system.
You need an entry in the system directories for the user.
If you receive the message, great.
CRTSAVF on both systems.  I use the name TRANSFER in library QGPL.
Then perform your save command to the save file.  On subsequent saves, it
will say it is not empty and you can proceed with a 'G'.
SNDNETF of the save file to the other system.
WRKNETF or RCVNETF and receive it.  On subsequent calls, it will say the
save file is not empty.  'G' to proceed.
Perform your restore.

Yours truly,

Glenn Gundermann
Email: glenn.gundermann@xxxxxxxxx
Cell: (416) 317-3144
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.