|
On Oct 10, 2024, at 11:34 AM, smith5646midrange@xxxxxxxxx wrote:--
SITE is not a valid command from windows FTP.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
MidrangeL
Sent: Thursday, October 10, 2024 12:10 PM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>; Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re[2]: Weird result creating a SAVF via FTP
From a PC don't you need the "site" keyword?
So: site quote crtsavf mylib/mysavf
The rules are not the same from a PC as they are between real systems.
--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
------ Original Message ------
From "Javier Sanchez" <javiersanchezbarquero@xxxxxxxxx> To "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxxxxxxxx>
Date 10/10/2024 10:57:52 AM
Subject Re: Weird result creating a SAVF via FTP
Not sure, I have a similar script, but this one saves first to an--
existing save file.
The difference I notice is that in my script just after the QUOTE
subcommand I always use RCMD like:
QUOTE RCMD SAVOBJ(...)....
It looks like the RCMD may be optional but better use it always.
If you always use the same name for the save file, I recommend to
create it first and leave it alive always and use the SAVLIB or the
SAVOBJ commands, whatever your design is. You only need to make sure
to include CLEAR(*YES) so that it won't send an inquiry message
asking if you want to Go and replace the contens.
Try to add the RCMD keyword, maybe this helps, but I'm not sure if
this will fix that.
JS
El jue, 10 oct 2024 a las 9:34, <smith5646midrange@xxxxxxxxx> escribió:--
I have a .bat file on my windows PC that needs to connect to an IBM
I, create a SAVF, and then upload a file from the PC into the SAVF.
My script file is as follows:
open systemname
userid
password
quote "CRTSAVF MYLIB/MYSAVF"
bin
put file.savf mylib/mysavf
close
quit
This creates a PF named mylib/myfile. It does not create a SAVF.
If the file already exists, I get an error that CRTSRCPF failed.
Why is it converting the CRTSAVF to a CRTSRCPF? How do I get it to create the SAVF?
This is on a 7.4 machine that is current (as of Monday) with PTFs.
This is going to connect to 8 different machines so I'd rather not
log into each one of them to do the CRTSAVF.
--
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.
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.