Character# causes truncation of file name in SSH 6.6

10 pts.
Tags:
SSH
Why does the # character truncate the file name in a get in SSH 6.6, it does not in SSH 4.7


Software/Hardware used:
OS/400 RELEASE IS V7R1M0
0

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • TheRealRaven
    It might be because a bug was fixed to make it work correctly now, or because something changed on the remote site, or because a job or system CCSID attribute was changed, or a number of things.

    In some cases, a "#" character in a filename has caused problems in Unix-style network transfers. I've seen them cause trouble even in plain FTP. Using characters like that is simply not a good idea.

    That's especially true in any EBCDIC-based system. A "#" character is not in the invariant character set, so they should never be used in any kind of identifier name, e.g., in a filename, in a column name or similar.

    Use single-quote marks around the full filename in scp or other ssh transfer utilities when special characters might be in a name. That's perhaps the first thing to try. Also, many special characters can be escaped to have their 'special' meaning suppressed. But it might be easiest just to quote most names.
    35,620 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: