NJE
Network Job Entry: the JES feature that sends jobs, output and files between separate mainframe systems.
Also written Network Job Entry, NJE node, JES node
NJE, Network Job Entry, connects separate JES systems so they can send work to each other. Each connected system is a node with a name. Nodes may be in the same building or in different countries.
Over NJE, a job submitted on one node can run on another, for example by using a /*XEQ statement or the XMIT JCL statement. Output can be sent back to the node where the job came from, or to a printer elsewhere. The TSO TRANSMIT and RECEIVE commands also travel over NJE when they send datasets to users on other systems.
NJE is separate from the sysplex. Systems in a sysplex share a JES2 spool and already see each other's jobs. NJE is for systems that do not share a spool, such as two different sysplexes, or a site and its disaster recovery location.
You may never set up NJE, but you will see node names in job output, routing statements and TRANSMIT commands, and it explains how a job submitted in one place can run in another.
Where can I learn this hands-on?
Right here, at ZedBank. You take a junior job at a simulated bank and learn each part of the work by doing it, with Zed beside you. There's nothing to install.
Start at ZedBankRelated
- JES2The job entry subsystem: the part of z/OS that queues jobs, decides when they run, and collects their output.
- JES2 control statementsLines in a job that start with /* and a keyword, which give instructions to JES2 rather than to z/OS.
- TRANSMITSends members of a library to a user on another system.
- RECEIVECollects data that someone sent you with TRANSMIT.
- SysplexA group of mainframe systems joined together so they behave as one, sharing work and data so that no single failure stops the service.