MainForm IT

The MainForm IT architecture is based on a client/server model, with the Client Application running on a workstation and the Server Engine residing on the z/OS mainframe. The Client Application communicates with the Server Engine via TCP/IP. The Server Engine is responsible for processing merge requests, interacting with the print spooler, and managing print jobs.

The Print Spooler Interface handles the interaction with the z/OS print subsystem. The system uses flat files for storing configuration data, including print queue definitions, output formats, and user profiles. The REST API provides programmatic access to core functionalities, with endpoints such as `/api/merge` and `/api/print`.

The API uses JSON for data exchange. The system supports user authentication via user ID and password. Access control is managed using RBAC, with roles and permissions defined in the configuration files.

The system uses standard TCP ports for communication, which are configurable during installation. The `MFIT_MERGE` command takes parameters for form and data file locations, output format, and other options. The `MFIT_PRINT` command specifies the print queue, number of copies, and other print-related settings.

The `MFIT_STATUS` command provides information about the status of print jobs and the server.