NJE Diagram

What is the NJE/IP?

Sine Nomine Associates’ NJE/IP allows a user to interconnect NJE communication services on unmodified OS/390, VM, z/VM, z/OS, VSE, TPF, and -- for the first time – open systems (such as Linux (Intel) and Linux (Mainframe), Solaris connected to IPv4 and IPv6 IP networks.

***Now supports SNMP***

NJE/IP incorporates a complete bi-directional NJE implementation for a large range of mainframe, midrange, and desktop computing environments, and supports integration of development environments, workstation applications, and system management tasks into a reliable, stable, completely IP-based environment that is transparent to end user awareness.

Target Audience for the NJE/IP

NJE/IP meets the needs of users who:

  • Need to move NJE connectivity to a pure IP environment to eliminate legacy SNA hardware and software: NJE/IP enables file transfer, interactive messaging, and print to flow between NJE-capable system using only IP connectivity. 

  • Need to provide encrypted file transfer between NJE implementations not on z/OS: IBM provides SSL encryption for NJE traffic only in the z/OS JES implementations. The NJE/IP code can connect to any NJE implementation and provide SSL-encrypted connections to other remote systems as a intermediate node. Traffic within a system or LPAR is unaware of the encryption, and requires no modifications to any IBM code to provide this feature.

  • Need to incorporate automated hands-off file transfer from non-IBM systems to IBM NJE-capable systems leveraging existing automation and file arrival triggers: NJE/IP allows files, interactive messages, and print jobs to be transmitted and received from open systems and Windows workstations/servers as if they came from a peer IBM system. The transfer of the file is managed completely without human intervention, and does not require a user login on the target system. By using NJE, the file transfer process can leverage already implemented automation and file arrival triggers present in all major job scheduling systems on IBM operating systems. 

  • Need to permit IBM operating systems to securely submit commands and data to a remote Unix/Linux system for execution, with job results and output returned to any designated NJE destination using natural and compatible syntax (Unix and Linux implementations only): The NJE/IP package on Unix/Linux systems provides a job queing system that can accept jobs and data files for remote execution on the Unix/Linux system and return job logs, listings and output to a designated NJE destination according to specifications supplied by the job creator. Commands and data are authenticated/authorized based on information supplied by the user, and the execution scope of commands is limited to what the authenticated user's privileges and capabilities (on the target Unix/Linux system). The job queuing system supports pools of Unix/Linux systems for execution and can provide multiple execution queues and resource limits. 

  • Need to implement low-cost advanced printing support for IBM operating systems: NJE/IP implements advanced printing capabilities for mainframe users to route output to any LAN-based printer with Linux, Windows, or OS X support from the command line or in JCL. The printing code provides printer-independent forms and overlay controls, page composition, automatic PostScript to printer-dependent format conversion, and a easy to use WWW-based print control system allowing authorized users to modify and control printing without granting elevated privileges at the mainframe host. No special hardware or software is required in the printer and conversion tasks can be performed on inexpensive resources rather than on the mainframe CP engines.

  • Need to centralize and automate system management using existing powerful mainframe tools: In most organizations, the mainframe environment already has advanced automation and system management capabilities fully implemented. NJE/IP allows open systems log and error messages to be delivered to a central automation system, and allows the automation system to securely respond if action is warranted without granting direct login capability to operators.

NJE/IP Features

The most outstanding features of NJE/IP are:

  • No SNA connectivity or special hardware/software products are required to support NJE on a wide range of IBM and non-IBM platforms: NJE connectivity can be supported with no SNA network at all on all IBM operating systems, plus most popular non-IBM systems. In many cases NJE/IP can replace 2780/3780 remote job entry equipment as well, permitting retirement of many obsolete and expensive to support outboard systems and software licenses.

  • Encryption for connections is transparently supported and negotiated on all NJE platforms: Older legacy NJE implementations can be made compliant with encryption requirements without modification, and can be extended to interaction with open systems and Windows without compromising encryption capability.

  • Integration of non-IBM systems into the NJE world, simplifying file delivery and automation: NJE/IP extends the NJE capability to many popular non-IBM platforms. See the NJE/IP Supported Platforms list for a complete list of supported platforms and operating systems.

  • IPv4 and IPv6 are natively supported: NJE/IP supports both IP version 4 and IP version 6 connectivity natively. The application is completely compatible with pure environments and dual stack environments. 

  • NAT-friendly Tools and Implementation: NJE/IP is capable of coexisting comfortably in an environment using multiple levels of network address translation (NAT). The IBM implementations do not adapt well to environments where both ends of a connection use NAT.

  • Very low cost "one link" option for z/VM environments: NJE/IP VM Spool Interface optional component for z/VM allows leaf z/VM systems to transfer files and messages to a central NJE implementation without requiring the full complexity of the NJE routing tables and link infrastructure. NJE/IP Connector for z/VM is substantially less expensive per z/VM system than a full RSCS license and can leverage any existing NJE implementation as its core hub (e.g., a star topology of z/VM systems using a z/OS system as a core hub). This capability dramatically simplifies using the VM Programmable Operator function and centralized automation already built in to both VM and other IBM operating systems.


NJE/IP requires a supported operating system and IPv4/IPv6 connectivity to at least one NJE host. For System z, both an individual application package (for customers with an existing preferred Linux on System z distribution choice) or a self-contained appliance suitable for z/VM or native LPAR installation are available. On all other platforms, only the application package is available.

Delivery and Installation

NJE/IP code is delivered electronically by download from a password-protected repository. Installation and configuration documentation is included with the package in PDF form.

NJE/IP is available for immediate access upon payment of the invoice. 


NJE/IP is licensed based on the types of system and major release of the operating system desired. A separate maintenance subscription is available if you wish to receive support and updates.

Ready to test out the product for free? The trial license paperwork is located here

Where Can You Find Out More About NJE/IP?

  • A printable brochure describing NJE/IP is available here.
  • A list of supported platforms and operating systems is available here.
  • A white paper describing a complex implementation of NJE/IP is available here.
  • A helpful SHARE presentation on TCPNJE support and implementation on z/OS is available here.
  • An example of the necessary configuration statements for implementing TCPNJE on JES2 is available here. 

Product Documentation