Embedded Files
Subscribe to keep this site alive! Under new management but as always, still 100% FREE. Anyone with the IBM i is a friend of ours.
The Challenge: There are times when we need to resend EDI files as they we previously submitted (resending the document via the mailbox will change the control numbers). Or as a requirement of migrating to a management services where a mass submission is required.
The Challenge: There are times when we need to resend EDI files as they we previously submitted (resending the document via the mailbox will change the control numbers). Or as a requirement of migrating to a management services where a mass submission is required.
The Solution: The solution starts by querying the target communication session numbers (commsessions) via QRYCOMSN which produces the ED230P1 report (given a network/'*ALL' and a date range). The commsessions are then "scraped" from the report and brought into the COMSSN database file.
The Solution: The solution starts by querying the target communication session numbers (commsessions) via QRYCOMSN which produces the ED230P1 report (given a network/'*ALL' and a date range). The commsessions are then "scraped" from the report and brought into the COMSSN database file.
Because there might be a need to remove commsessions from the batch of resubmission, the mailbox details are grabbed using the UGETMBXS API and is recorded in the MAILBOX database. This is only possible if the mailbox information is still present in the system.
Because there might be a need to remove commsessions from the batch of resubmission, the mailbox details are grabbed using the UGETMBXS API and is recorded in the MAILBOX database. This is only possible if the mailbox information is still present in the system.
Note: The next step reads to the net records in the COMSSN file. To remove records from the COMSSN file is to do a subquery against the MAILBOX file and DELETE by selection or omission:
DELETE COMSSN where COMMSSN not IN(SELECT COMMSSN from MAILBOX where Target)
DELETE COMSSN where COMMSSN IN(SELECT COMMSSN from MAILBOX where Anti-Target)
The purpose of this second part is to programmatically "Bring the commsession to an EDI readable text file" based on the net COMSSN file. By default the SSNCPYPRT produces a file that is 135 bytes in length, because our ENDLINFMT parameter when we run the CPYTOSTMF iSeries command is "*FIXED", the extra spaces at the end of each record will be included in the output stream file. And besides the option of using *CRLF will not work with files with imbedded CRLF's within the data. In this CL program, the SSNCPYPRT is ran to produce the default-length SSNCPYW database. The @@LENGTH RPGLE program checks its length by reading its first record. Then a temporary communications file interface file (CFI file) is created and populated with the records captured in SSNCPYW database file.
The purpose of this second part is to programmatically "Bring the commsession to an EDI readable text file" based on the net COMSSN file. By default the SSNCPYPRT produces a file that is 135 bytes in length, because our ENDLINFMT parameter when we run the CPYTOSTMF iSeries command is "*FIXED", the extra spaces at the end of each record will be included in the output stream file. And besides the option of using *CRLF will not work with files with imbedded CRLF's within the data. In this CL program, the SSNCPYPRT is ran to produce the default-length SSNCPYW database. The @@LENGTH RPGLE program checks its length by reading its first record. Then a temporary communications file interface file (CFI file) is created and populated with the records captured in SSNCPYW database file.
Do you have a new CHALLENGE? Let us know HERE.
Page updated
Google Sites
Report abuse