> > [...]  You may need to use some imagination, and
> > try some things.  For example:
> 
> > FTP> hash             ! I never do this.  What happens without it?

> The hash is only for show the advance of transaction

   Thanks, but I know what it's supposed to do.  The question is
whether it's causing a problem.

> > FTP> mput prueba.txt  ! What about "put"?  "get"?

> put is only for transfer a one file, mput many files same time, but
> not works also

   Thanks, but I know what they're supposed to do.  The question is
whether one of them is causing a problem.  And did you answer the
question about "get"?

> > FTP> prompt           ! With "put" or "get", you wouldn't need that.

> prompt is when mput is used, not ask avery time (y/n) for transfer

   Thanks, but I know what it's supposed to do.  The question is
whether it's causing a problem.

   So, as I read this, "hash" was not necessary to cause the problem,
"mput" was not necessary to cause the problem, and "prompt" was not
necessary to cause the problem.  Have you ever tried to solve a
user-reported problem before?  Do you think that a longer, more
complicated problem report is easier to work with than a shorter,
simpler one?

> > FTP> set def sys$sysdevice:[acms]     ! Always the same dev:[dir]?
> 
>    Have you tried using some other source and destination disks and
> directories?
> [...]
> 
> Yes diferent directories, without acl, diferent users same issue :(

   Did I ask about only "directories", or did I ask about "other source
and destination disks and directories"?  How many parts of that question
did you answer?  (Almost one?)

> If I send to alpha machine send/receive very well, no issues in both
> directions, the issue is integrity/integrity

   How many questions did I ask?  How many of them does this answer?

> Today try also SFTP and same issue :(

   Exactly the same?

>    Show actual commands with their actual output.

   Apparently I was wasting my time with that advice.  Did you try
adding "-v" (or "-vv", or "-vvv") to your (secret) SFTP command?

   FTP and SFTP are very different parts of TCPIP.  If you have a
problem with both FTP and SFTP, then I would expect the problem to be in
some fundamental part of the networking software/hardware, not in the
FTP- or SFTP-specific parts.  How many other network tasks have you
tried between these systems?  Have you looked at the low-level network
statistics?  I know nothing about your network hardware, but a command
like the following (with some appropriate device name or names) might be
interesting:

      mcr lancp show devi /coun ewb0

You might try comparing the results bewteen systems without problems and
systems with problems.  (It's still not clear to me which systems have
the problem, and which do not.  "the issue is integrity/integrity" tells
me nothing about Alpha/IA64 or IA64/Alpha.  I believe that I did ask.)

> >    Or, call HP.

> Yes I have a mission critical support ticket opened in HP but not
> answers about this issue :(

   They may still be trying to figure out which parts of your problem
report are significant, and which parts are in there only to waste
everyone's time.

   Have the people at HP asked you any questions?  Did they get any
better answers than I did?