JES DataGateway Modernization Guide

JES DataGateway transmits JES2 and JES3 output to non-mainframe servers. It operates as a JES Functional Subsystem (FSS) within the z/OS environment, capturing spool data and routing it over TCP/IP.

Configuration is primarily managed through the FSS parmlib member. Parameters control TCP/IP settings, target server addresses, data transformation options, and security configurations. The FSS definition in IEFSSNxx also plays a role.

JES DataGateway uses TCP/IP for communication. The specific port is configurable in the FSS parmlib member. Ensure that the target servers are reachable via the configured port.

JES DataGateway exposes a proprietary API for interaction with Nearstar products on non-mainframe servers. The API uses a TCP/IP socket connection for communication. Specific method names and data structures are defined in the product's integration documentation.

The main components include the FSS Interface Module, the TCP/IP Communication Module, and the Data Transformation Module. The FSS Interface Module interacts with JES, the TCP/IP Communication Module handles network communication, and the Data Transformation Module converts data formats.

JES DataGateway does not directly use a database. It captures spool data from JES and transmits it over TCP/IP. The target server is responsible for data storage.

By offloading print processing to non-mainframe servers, JES DataGateway reduces the processing load on the mainframe, potentially lowering mainframe costs. It also enables integration with distributed systems.

JES DataGateway facilitates the integration of mainframe output with distributed systems, enabling workflows that span both environments. This can improve overall business process efficiency.

JES DataGateway supports authentication via RACF (Resource Access Control Facility) or other z/OS security managers. It leverages existing z/OS security infrastructure.

JES DataGateway uses the z/OS security model, which is primarily an Access Control List (ACL) based model. Access to JES resources is controlled by RACF profiles.

Data transmitted over TCP/IP can be encrypted using TLS (Transport Layer Security). Configuration options control the level of encryption.

JES DataGateway provides logging to the z/OS system log (SYSLOG). Log entries include information about connection status, data transmission, and errors.

User management is handled through z/OS security. User access to JES resources is controlled by RACF profiles. JES DataGateway leverages the existing z/OS user management infrastructure.

The main configuration parameters are defined in the FSS parmlib member. These parameters control TCP/IP settings, target server addresses, data transformation options, and security configurations.