View previous topic :: View next topic
|
Author |
Message |
technut
New User
Joined: 27 Dec 2007 Posts: 73 Location: India
|
|
|
|
Hi,
We are converting FTP2 (CA protocol) ftp methodology to IBM TCP ACCESS FTP methodology.
There is few bytes difference between these two ftp process while we ty to send files with FBA format. Please see the below snapshots of the jobs that we used.
Below is the IBM TCPIPaccess methodology of ftp...
Code: |
//STEP01 EXEC PGM=FTP,PARM='(TCP IBMTCPIP EXIT)'
//SYSTCPD DD DSN=NETPRD.TCPIP.DATA(SYTA),DISP=SHR
//SYSPRINT DD SYSOUT=*
<servername>
<userid>
<password>
<server path>
ascii
put 'useris.acrstats(+0)' +
test1.acr
close |
Below is the older CA ftp methopdology code
Code: |
//STEP03 EXEC FTP2,PARM='/FIOS'
//SYSPRINT DD SYSOUT=*
//SYSPUT DD DCB=BLKSIZE=133,
// SYSOUT=*
//SYSGET DD *
<servername>
<userid>
<password>
<server path>
ascii
PUT 'LAPP.NT.T103.ACRSTATS(+0)'
test3.ACR
CLOSE
BYE
END
|
Can somebody suggest as to what command we have to use in the IBM ftp methodology so that files generated by both the ftp types are exactly the same?
Thanks! |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10873 Location: italy
|
|
|
|
Quote: |
There is few bytes difference between these two ftp process |
until You describe better the differences very little can be said
but just to start with, You are showing different file names, so after all the differences might be correct,
what happens when You send exactly the same file |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
You'll probably need to change the translate table ... IIRC, CA and IBM TCP stacks use different translation tables so characters do not come across exactly the same. Check the Communications Server manuals for IBM -- I don't know which manuals have the CA information. |
|
Back to top |
|
|
technut
New User
Joined: 27 Dec 2007 Posts: 73 Location: India
|
|
|
|
The difference is basically just a "SPACE". While we do a IBM type transfer a space is added to the front of the a every record. I could see from the job logs that while using CA the job is accepting a FBA file format transission whera IBM type doesnt seem to do it.
Thanks for looking into this.. |
|
Back to top |
|
|
technut
New User
Joined: 27 Dec 2007 Posts: 73 Location: India
|
|
|
|
Regarding the suggestion of sending same files, I obviosuly sent the same files only through both ftp moded. Just the name was mistyped in the snippet. Apologize for the confusion there.. |
|
Back to top |
|
|
Craq Giegerich
Senior Member
Joined: 19 May 2007 Posts: 1512 Location: Virginia, USA
|
|
|
|
What I have seen with FTP is that the carriage control character in the first position of an FBA file is translated. A "1" becomes a FORMFEED, a "2" becomes a LINEFEED etc, and each records is terminated with CR/LF. Since windows doesn't have a way to view a raw file in hex mode it is hard to see just what the changes are. |
|
Back to top |
|
|
technut
New User
Joined: 27 Dec 2007 Posts: 73 Location: India
|
|
|
|
I went into the server and caught the differences on a hope that it might help. Below is the snapshot of the same,
Code: |
(lawapsx101c)/apps/lawson/fin/data/test_comp> diff ibmtest.acr catest.acr
1,24c1,24
< 1 LAP1103 FORMAT LAWSON RECEIPTS PROCESS
< 08/31/09 18:32:33 LAP1103 - CONTROL TOTALS
<
< RECEIPT RECORDS READ (CNT) 80,196
< RECEIPT RECORDS READ (AMT) 89,186,150.78
<
< IMPORT RECEIPT RECORDS (BYPASSED) (CNT) 0
< IMPORT RECEIPT RECORDS (BYPASSED) (AMT) 0.00
<
< STORE PLANNING RECEIPTS (BYPASSED) (CNT) 0
< STORE PLANNING RECEIPTS (BYPASSED) (AMT) 0.00
<
<
< NON-STORE/NON-DC RECEIPT RECORDS (BYPASSED) (CNT) 0
< NON-STORE/NON-DC RECEIPT RECORDS (BYPASSED) (AMT) 0.00
<
< RECEIPTS OUT OF TOLERANCE (EXCEPTION REPORT) (CNT) 3
< RECEIPTS OUT OF TOLERANCE (EXCEPTION REPORT) (AMT) 121,025.98
<
< RECEIPT RECORDS WRITTEN FOR TRANSMIT TO LAWSON (CNT) 80,196
< RECEIPT RECORDS WRITTEN FOR TRANSMIT TO LAWSON (AMT) 89,186,153.92
<
< ITEM RECORDS WRITTEN FOR TRANSMIT TO LAWSON (CNT) 933,745
< ITEM RECORDS WRITTEN FOR TRANSMIT TO LAWSON (AMT) 89,186,153.92
---
>
LAP1103 FORMAT LAWSON RECEIPTS PROCESS
> 08/31/09 18:32:33 LAP1103 - CONTROL TOTALS
>
> RECEIPT RECORDS READ (CNT) 80,196
> RECEIPT RECORDS READ (AMT) 89,186,150.78
>
> IMPORT RECEIPT RECORDS (BYPASSED) (CNT) 0
> IMPORT RECEIPT RECORDS (BYPASSED) (AMT) 0.00
>
> STORE PLANNING RECEIPTS (BYPASSED) (CNT) 0
> STORE PLANNING RECEIPTS (BYPASSED) (AMT) 0.00
>
>
> NON-STORE/NON-DC RECEIPT RECORDS (BYPASSED) (CNT) 0
> NON-STORE/NON-DC RECEIPT RECORDS (BYPASSED) (AMT) 0.00
>
> RECEIPTS OUT OF TOLERANCE (EXCEPTION REPORT) (CNT) 3
> RECEIPTS OUT OF TOLERANCE (EXCEPTION REPORT) (AMT) 121,025.98
>
> RECEIPT RECORDS WRITTEN FOR TRANSMIT TO LAWSON (CNT) 80,196
> RECEIPT RECORDS WRITTEN FOR TRANSMIT TO LAWSON (AMT) 89,186,153.92
>
> ITEM RECORDS WRITTEN FOR TRANSMIT TO LAWSON (CNT) 933,745
> ITEM RECORDS WRITTEN FOR TRANSMIT TO LAWSON (AMT) 89,186,153.9 |
[/code][/quote] |
|
Back to top |
|
|
technut
New User
Joined: 27 Dec 2007 Posts: 73 Location: India
|
|
|
|
The command "Locsite ASATRANS" has worked for us finally.
Converting the file from FBA to FB also is working. |
|
Back to top |
|
|
|