I know I should know this pt 2

[steven.donnellan@xxxxxxxxxxxxxxx]

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
(This could be a long one - avoid Reply with history!!)
Thanks to everybody who has helped so far.  Now this is where I'm at;
PC FILE SPECS
Column  emid            Number (Double) 8
Column  branch          Text    3
Column  active          Text    1
Column  mail            Text    1
        *SNIP!*
Column  newcty          Text    25
Column  newctry         Text    20
Column  newpost         Text    10
Column  adid            Number (Double) 8
Column  jba seq         Text    3

AS/400 File Description
Field       Size   Typ
EMID           8  0 S
BRANCH         3    A
ACTIVE         1    A
        *SNIP!*
NEWPOST       10    A
ADID           8  0 S
JBASEQ         3    A

A file transfer falls down saying that Row 1 Column 1 is the 'wrong type'.
 FTP produces the following log;

Connected to Jersey.
220-QTCP at JERSEY.
220 Connection will close if idle more than 5 minutes.
User (Jersey:(none)): qsecofr
331 Enter password.
Password:
230 QSECOFR logged on.
ftp> put ukgrou~1.txt jbadata/qasspd
200 PORT subcommand request successful.
150 Sending file to member QASSPD in file QASSPD in library JBADATA.
> Netout :10054
426-Cannot write to member QASSPD in file QASSPD in library JBADATA.
426 Data transfer ended.
ftp: 225280 bytes sent in 2.31Seconds 97.52Kbytes/sec.
ftp>

I'm supposed to roll this out in such a way a User can get the file to the
'400 and I'm struggling myself!
HELP!

Steven Donnellan
AS/400 Systems Manager
IBM Certified Specialist - AS/400 Professional Operator
Simon Jersey Ltd

http://www.simonjersey.com

**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please delete
it immediately and notify the sender, do not discuss or disclose the contents.
The views expressed in the e-mail are those of the author and not necessarily
those of Simon Jersey Limited.
**********************************************************************
--