DRS/Natural

The architecture of DRS/Natural comprises several key components that work together to route Natural output to the JES SPOOL. The Natural Interface acts as the entry point, intercepting output from Natural applications. The Output Router is responsible for analyzing the output based on predefined rules.

These rules are defined in configuration files, which specify criteria for redirecting Natural output to the JES SPOOL. The JES Spool Interface handles the interaction with the JES SPOOL, submitting the output for printing. Communication between these components relies on standard z/OS interfaces.

The Natural Interface hooks into the Natural runtime environment, capturing the output stream. The Output Router reads the configuration files to determine the destination for the output. The JES Spool Interface then submits the output to the JES SPOOL.

No specific databases or storage mechanisms are used beyond the JES SPOOL itself. The system does not expose any APIs. Administration is performed through the z/OS console and the DRS print management interface.

Security relies on the z/OS security infrastructure, including user authentication and access control lists (ACLs) for resources. Audit logs track user activities and system events related to print jobs. The configuration files use a specific syntax to define routing rules.

For example, a rule might specify that all output from a particular Natural program should be routed to a specific printer.