Method-Calling Sequence during File Creation

When the Distribution engine receives a request to build the cash letter file, a similar process is followed. The user exit is first instantiated and the following methods are called to access the information used to build the records:
  • setBank()
  • setPartner()
  • setFileDef()
  • setChannelDef()
  • setOutboundPresGrp()
The calling sequence for building a file is as follows:
  1. The engine creates a filename and passes it to modifyFilename(). The method returns either a different filename or null. If null is returned, the engine uses the original filename it created.
  2. A Type01Record object is built
  3. The modifyRecord() method is called for the Type01Record
  4. As each new batch (ICL) is processed, the engine calls setOutboundPres()
  5. A Type10Record object is built
  6. The modifyRecord() method is called for the Type10Record
  7. All the bundle files for that batch (ICL) are read from disk and written to the cash letter file.
  8. After all bundle files have been written, a Type90Record object is built
  9. The modifyRecord() method is called for the Type90Record
The above process is repeated for each batch (ICL) in the file. After all batches (ICLs) have been processed, a Type99Record is built and sent to modifyRecord().
Note: When creating the cash letter file, the setOutboundSegment, setEndpoint, and setBuildingOpts methods are not called because there is not just one outbound segment, endpoint, or set of building options associated with a batch (ICL). If the getOutboundSegment, getEndpoint, or getBuildingOpts methods are called while writing the cash letter file, a null is returned to the caller.