^J - Unix

[ABlipInContinuity]

Hi,

I FTP'ed a bunch of very similar Unix shell scripts from 'doze to HPUX.
Now, I've seen files FTP'ed with ^M at the end of each line because I've used the wrong transfer mode before.

But on some lines, I have the ^J demarking the end of the line.

The files were editted using Notepad++ prior to transfer, using Unix ANSI encoding. Only one of the files I editted and transferred is affected.

Any thoughts please.

Incidentally, these symbols cannot be seen in vi, but when I try and execute the shell script the error output displays them.

./bmra_8F025_install.ksh[266]: pkg_bmr_syswarn_load.sql^J^JNEW_PACKAGE_FILES=pkg_etso_vista_email_hdr.sql:  not found
./bmra_8F025_install.ksh[305]: pkg_etso_vista_email_body.sql^J^JDB_TRIGGERS=cre_pf_bi_ber_trg.sql^J^JNEW_DB_TRIGGERS=^JPACKAGES_TO_DROP=^J^J# V1.10 Files listed here will end up in database/tables and be run against the database.^J# Typically pxa_.sql files. Note there is only a NEW_ version of this variable. My definition each drop (and hence change script)^J# has a unique compontnet in its name^JNEW_DB_ALTER_SCHEMA_FILES=^J^J# V1.10 Files listed here will end up in database/tables and NOT run against the database.^J# Typically used to get the pxa backout files into the dir. Note there is only...

[ABlipInContinuity]

Nothing to do with FTP.

I'd dropped a quote!

A PICNIC moment.

[Zipperhead]

Incidentally, these symbols cannot be seen in vi, but when I try and execute the shell script the error output displays them.

:set list

is useful for showing such stuff

[Greenbank]

The files were editted using Notepad++ prior to transfer, using Unix ANSI encoding.

Are you sure it was ANSI encoding? I'd expect this behaviour if the file had been saved as UTF-16 (which many Windows files actually are).

[D0m1n1c Burford]

Make sure you are sending the files using ASCII by typing:

ascii

at the FTP command prompt.

[Greenbank]

Make sure you are sending the files using ASCII by typing:

ascii

at the FTP command prompt.

^M end of line characters - Win to Unix FTP

It's nothing to do with ascii/bin mode within FTP.

That only removes/inserts Carriage Return (^M) characters alongside linefeed characters (^J). It leaves linefeed characters (^J) alone and doesn't insert/remove any of them.