Hope it was ok to post this question here. I've seen script questions here before.

[Steve Young]

This is a multi-part message in MIME format.

------=_NextPartTM-000-c4f7d4f4-47e4-11d6-8b86-00d0b79a4f1a
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hope it was ok to post this question here.  I've seen script questions =
here before.

I seem to have a problem with a KORN shell script I'm using on a AIX box =
that ftp's to an NT box.  The script makes a macro file that is fed to the =
ftp command the script uses and then letter the script rm the macro file. =
The part of the script I'm having a problem with goes like this:

print prompt > $FTP_FIL                                                    =
      =20
print macdef login >> $FTP_FIL                                             =
    =20
print "open $FTPSITE" >> $FTP_FIL                                          =
     =20
print 'user steve\\ftpaix passwd' >> $FTP_FIL              =20
# Insert a blank line to denote the end of the macro                       =
    =20
print >> $FTP_FIL =20

It's the line:

print 'user ecom\\ftpaix m1cr0age' >> $FTP_FIL  =20

that seems to create the prob for me.  It comes out right with just one =
backslash in the file I make, however the ftp shell (I believe) picks it =
up as an escape character.  I was wondering how to get around this of if =
there were even a way to do it.

Steve


------=_NextPartTM-000-c4f7d4f4-47e4-11d6-8b86-00d0b79a4f1a
Content-Type: text/plain;
	name="InterScan_Disclaimer.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="InterScan_Disclaimer.txt"

The information in this E-mail message is confidential and for 
the sole use of the intended recipient.  If you are not the 
intended recipient, you are hereby notified that any 
dissemination, distribution, copying or use of this information 
is strictly prohibited.  If you received this communication in 
error, please notify the sender immediately.  Blue Cross and 
Blue Shield of Arizona, Inc. and its subsidiaries and affiliates 
are not responsible for errors, omissions or personal comments 
in this E-mail message.

------=_NextPartTM-000-c4f7d4f4-47e4-11d6-8b86-00d0b79a4f1a--