Re: Using FTP to transmit a file in the IFS

If it's not a copy/paste error your override to INPUT you have INTPUT, not
INPUT...


Thanks,
Tommy Holden



From: Jeff Young <jyoung0950@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 07/15/2014 09:59 AM
Subject: Re: Using FTP to transmit a file in the IFS
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I am now having another issue with FTP.
I have an FTP Script file with the following commands:
close
open MUSSONJAMAICA.COM
USER xxx yyyy
ascii
locsite namefmt 1
cd /ffff/vvvv
put '/zzzz/gg/inbox/14072014 Creation Report.txs'
close
quit

Prior to issuing the FTP command, I issue an OVRDBF command to file INPUT
AND OUTPUT
INTPUT DB TOFILE(QTEMP/STVFTINST) MBR(STV150714)
OUTPUT DB TOFILE(T37MODSDTA/STVFTPLOG) MBR(STV150714)

When I issue the FTP Command, I get what appears to be a "terminal window"
This is a mostly blank screen with the text Press ENTER to end terminal
session. near the top and the following command keys on the bottom:
F3=Exit F4=End of File F6=Print F9=Retrieve F17=Top
F18=Bottom F19=Left F20=Right F21=User Window

The screen appears to have a command line above the command keys, but
ignores anything I key.

If I press F3 and then Enter, my job ends.

Below is the output from the FTP Log file:
Output redirected to a file.
Connecting to host S105RHXM at address nn.nn.nn.nnn using port 21.
220-QTCP at Sxxxxxxxx.
220 Connection will close if idle more than 5 minutes.
Enter login ID (vai):
331 Enter password.
OS/400 is the remote operating system. The TCP/IP version is "V6R1M0".
250 Now using naming format "0".
Enter an FTP subcommand.

Enter an FTP subcommand.

Enter an FTP subcommand.

What am I missing here?

Jeff Young
Sr. Programmer Analyst


On Tue, Jul 15, 2014 at 10:34 AM, CRPence <CRPbottle@xxxxxxxxx> wrote:

On 15-Jul-2014 08:47 -0500, Jeff Young wrote:

On 15-Jul-2014 08:14 -0500, Jeff Young wrote:

I managed to solve the initial issue with the database extension,
but now have another problem.
The file that I am attempting to send has embedded blanks in the
name, and is a long name - 15012014 Creation Report.txt
I have tried to place quotes around it, but it still can not find
the file. When I change the name to use the _ character instead of
blank, I receive an error 5012014_Creation not found. Is there a
limit on the size of the file name in the PUT sub command?

I managed to solve the problem.
It appears that even though I used the locsite namefmt 1 command and
set the local directory using the lcd command, the put command needs
the full path name with the file or I get errors.

Specifying the path name is optional, if the named file is in the
Current Directory that has been established within the FTP session.

Having

correctly placed "quotes around" the name with embedded blanks, the PUT
should function as expected.

Once I used the full path name, and surrounded the file name with

single quotes, it worked fine. <<SNIP>>

After LCD FTP subcommand is used to establish a pathname outside the
default in /QSYS.LIB, the PUT should locate the named file within that
newly establisehd Current Directory [outside of /QSYS.LIB]. Simply

having

delimited the file name with either double-quote or apostrophe

characters,

just as was noted to be successful when fully qualified with the

pathname.

There should be no reason to specify the path redundantly; if an error
persists, either something was still incorrect in the setup, or there is

a

defect. The following script should successfully PUT the data from a
client localfile name that includes embedded blanks] from within the
current directory [of the FTP session], into a file named tofilename at

the

server:

LOCSITE NAMEFMT 1
LCD /myChosenDirectoryPath
PUT "15012014 Creation Report.txt" tofilename

--
Regards, Chuck

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.