Greetings
Some weeks ago we started having problems with incoming ftp. Once in a
while it seems like the ftp-server (or whoever creates incoming
files...) does not read the bldparms file, but creates files with the
default record-width. That causes loss of information (surprise :), and
the job handling the files to abend. The sending system gets a '226
Transfer complete.'-message, only these times the warning 'Some records
were truncated during transfer.' is appended.
22 out of 23 bad files were created during on-line backup, only 3 of
them when the backup included the .SYS-account. Has anyone had problems
like this? Anyone know what might be the problem? Any thoughts...

background info:
* we're on RELEASE: C.55.00   MPE/iX HP31900 C.05.08   USER VERSION:
C.55.06
* ~900 incomming files/day
* sending system is HP-UX 10.x, running AMTrix 'EDI-server' (that uses
the hp-ux ftp-client, I'm told)
* backup-command: STORE <fileset>;*t;online;directory... (i.e. we use
the older variant of TurboStore24*7 on-line-options)
* problem show up maybe once a week, usually 'spread out' over the
backup, i.e. not during any special phase of store
* nothing odd in the $stdlist of ftpmon, nor in ftplog.arpa.sys
* first line of bldparms.arpa.sys ';REC=-500,,F,ASCII;DISC=204800' but
these files get built as ;REC=-80,,F,ASCII;DISC=204800

tia
/per
--------------------------------------------
Per Ostberg  / [log in to unmask]
phone +46-8-58581213 / fax +46-8-58587710
Huddinge University Hospital
ChemLab / C1 74 / S-141 86  HUDDINGE / SWEDEN
--------------------------------------------