Title: Continuing FTP script statement.
As I 
said, I've extended the record length and that works. I'm not keen on 
transferring  my own commands to a remote system. That raises a whole set 
of new issues concerned with version control. The initial problem was raised 
simply because I couldn't get all of the RSTOBJ command on one line of a normal 
80 byte source line. 
I 
looked at the midrange archive and Dennis Loveday had replied to the same 
question thinking that a back slah provided some sort of continuity (just like 
in the UNIX implementation), but on testing at V4.3 it didn't 
work. The person who raised the issue found the same 
solution as I did........create a longer record length! In fact he hit the same 
limit as I did - 240 byte.
 
This 
must be a common problem!
 
FTP 
seems to be a worm-hole into another system and now I'm concerned about the 
issue of a user id/password being held in a script file for anyone to 
see.
And 
I'm even more concerned with the idea of placing a command on a client's system. 
perhaps PWRDWNSYS? DLTF A* Access some source? Yee  Gods! Change some 
production source? 
I've 
printed off section 9 of the TCP/IP Configuration reference which contains the 
FTP implementation.  
My 
wife is going to love me bringing another sexy book to bed tonight! 
 
Looks 
like I need to sniff around a lot more to get a bigger grip on all the security 
scenarios. 
  
  I need to run a longish command to restore a save 
  file after an FTP transfer and the AS400 command statement along with the 
  QUOTE and RCMD verbs is longer than the standard source file record length of 
  80 bytes.
  Is there a way of continuing a script line over two 
  source lines or do I have to create a ridiculously long record length to cater 
  for large script statements?
  Thanks in advance, 
  Mike Pantzopoulos 
 
As an Amazon Associate we earn from qualifying purchases.
	
 
This mailing list archive is Copyright 1997-2025 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.