Writing Flat Files on iSeries

Lynnol

Active Member
Hi All,

I have created a custom BSFN from a copy BSFN B0001002 Text File Processor Export. The reason for changing this BSFN is to remove the new line characters when it writes to the flat file. This BSFN writes records from F007101 and F0071111 to the flat file. The desired result is that records from F007101/F007111 are written in a single line record.

When writing records to F007101/F007111, I have left the URC1 value blank, as new line characters are not required as delimiters from udc 00|TP.

When this was tested on fat client, it worked beautifully. But when ran on thin client, which is on iSeries, it seems like it is concatenating the records with "F007101" as the delimiter.

The required setting in P98301 is also turned on for the IV that calls the BSFN to IBM-37.

Does anyone know what might be causing this problem?

Lynnol
E900|8.98.10 AS/400
 
Suggestions anyone? I've tried using different BSFNs but they all append a new line when writing the record to flat file.
confused.gif
 
If it works on your fat client but not on the iseries. Either DB2 is forcing something into the file or you have an ASCII/ EBCDIC issue somewhere conversion process.

Can you provide actually data samples of what you have and what you expect? That might help a little.

Rob
 
Thanks, Rob. If the following strings are listed in file F007111 for a particular batch:
String 1: "ABC 123 "
String 2: "DEF 456 "
String 3: "GHI 789 "

They will be concatenated together as
"ABC 123 F007101DEF 456 F007101GHI 789 F007101"

Note that string "F007101" seems to be used as the delimiter between the strings.

The correct output should be the following:
"ABC 123 DEF 456 GHI 789 "

jdeFprintfConvert was used to write to the file.

I can't debug B5500102, as this issue does not even happen on web local cleint. And when debug was turned on the server, nothing useful was captured in the log other than the parameters parsed in to the BSFN.
 
Posting the relevant B5500102 code may be helpful.

Also, you can try adding some calls to jdeWriteLogEntry to the bsfn in strategic places to log various values that are pertinent to your processing. It is a pain to have a server build for all such changes, but when dealing with iSeries/Win differences, it's about the only good method of function debugging between the 2 platforms.
 
Thanks, Jeremy. Went through a list of similar business functions, and got it working by modifying a copy of B34A1010
grin.gif


Lynnol
 
Back
Top