EDO350A calls EDO350B for each outgoing or inward going file set as outlined above.
EDO350B logic as follows:
EDO350F – Get TMSDS/EDI-FTP path details for file copies
EDO350E – Get TMSDS/EDI-FLOG path details for FTP log folder/file names. Look up EDSAN00P trading partner to determine IP and FTP script lib/file/mbr to be used.
For outgoing documents, the first record of source data (EDO331W1, DSEAA00P, EDO600W1 or EDO432W1) is used to get TPID! This assumes all data in outgoing file can be sent using common script! 7.4 version looks different – may be resolved?
For incoming documents, the &TYP variable from EDO350A is used as TPID (eg. “PO-IN”) to do the ftp pick up details.
Check script member exists
Create or clear FTP log member
Transfer data
For outgoing (file parameter not blank), copy IBM Power System source data to relevant IFS folder, then clear IBM Power System source data.
In or out:
FTP data
EDO350C checks FTP log for successful FTP. If outgoing failed, copies IFS data back to source data file and returns message.
Incoming: EDO350D used to bring incoming data into relevant IBM Power System files based on “format” passed in (refer TMSDS/EDI-FTP for formats supported)
