Writing the controller application program with MFS and XRF

If your system uses MFS and XRF, there are certain actions you must take when writing a controller application program.

• Specify the PS (page size) option on the 4700 controller's TERMINAL macro only if EJECT is specified on the IMS MFS DEV statement.
  If PS is not specified, the EJECT from IMS results in a new line function. If the end-of-page condition occurs on a workstation, an unexpected Finance system data exception error can occur. An EJECT from IMS resets the line count, resulting in an end-of-page condition.
  If the CFOLD option is specified on the 4700 controller's TERMINAL macro instruction, the formats defined for MFS should not cause spacing for the center fold on a passbook. The SLU P system performs this function automatically.
• Check to see if the IMS MFS DFLD statement specifies ATTR=YES.
  If it does, any attempt to print an underscore (X'6D') can result in either of the following:

  • A data check on a 3610/3612

    Specify a print position for the EBCDIC value (X'6D') when the OUTRTBL statement specifies other than the 128-character set for the 3610/3612 device.

  • Printing of a blank on a 3618 device

    Specify a print position for the EBCDIC value (X'6D') when the OUTRTBL statement specifies the 48-character set for a 3618 device.

• Check to see if the MFS DEV statement option of EJECT, BGNMXG, BGNPP, or ENDPP is used to send eject characters (X'0C') within one IMS output transmission (other than the last character).
  If so, an intervention-required condition occurs on the passbook printer after the eject. In this situation, your application program in the controller must be capable of issuing multiple LWRITE instructions to the passbook printer to print the IMS output transmission. Each LWRITE should include the data up to and including an eject character, or up to the end of the transmission.