An NJE job is a job submitted by the Control‑M monitor for execution on a remote node. Control‑M can detect the status of jobs running on a remote node, and when these jobs finish executing, Control‑M can assign a status to them.
To analyze how a job finished executing, Control‑M uses JES services to read the job’s output. If Control‑M detects a critical error in JES operation, it shuts itself down. This prevents the incorrect submission of jobs due to a JES malfunction.
Errors can occur under the following circumstances:
Control‑M cannot read the job SYSOUT.
The job returned with a temporary job status because its current job number is not the same as the job number it had when it started. Control‑M must know that the job number changed and must change the previous job number to the new one. The Control‑M monitor can detect that the original job ID of the NJE job is being used by another job and continue to search for a job to match the new job ID.
If the assigned job number changes, Control‑M may act as if the old job disappeared.
The job can have more than one sysout when it returns with a temporary job status. This gives it 2 separate ID numbers.
A job was purged from the spool on the remote node. The following message may be displayed each time Control-M attempts to find the job on the remote node:
HASP693 JOB NOT FOUND
BMC recommends that you do not do purge jobs on the remote node.
If the remote node is not active or not connected to the home node, the following message may be displayed each time Control-M attempts to find the job on the remote node:
HASP674 SYSTEM UNCONNECTED
This can be rectified by activating the remote node or by reconnecting the home node and the remote node.
To determine the cause of a specific error, it may be necessary to provide the Control‑M administrator with specific information about the job. The following suggestions can help resolve the problem:
Check the maintenance levels of the CTMSUB module and the CTMSPY module.
Check the job in the Zoom screen (Option Z on the Active Environment screen). Verify that the NJE field is set to Y (Yes) and that the NODE field contains the correct name of the remote node.
Look at the job’s JCL stream and see whether any statement contains parameter ‘FREE=CLOSE’.
Send the Control‑M administrator the job SYSOUT and the SDSF screen or the output of any other comparable product showing the SYSOUT datasets.
The SYSOUT status and whether the job was deleted or purged displays in the SDSF screen. If, for example, the SYSOUT datasets are in the wrong OUTPUT CLASS, Control‑M cannot read them.
Indicate if this problem occurs frequently and whether it occurs for all jobs or for just specific types of jobs.
Indicate the type of job (for example, cyclic, short or long term, regular, CICS).
Ensure that parameter ENHNJE (in the CTMPARM member of the IOA PARM library) is set to Y.
Ensure that the messages $HASP890, $HASP608, $HASP693, $HASP826, and $HASP650 are not suppressed. Also, do not suppress messages starting with the name of the remote system.
BMC recommends that you do not purge jobs from the spool on the remote node. However, if a job was purged from the spool on the remote node, you must notify Control‑M of the event, by changing the value in the NJE field in the Active Environment Zoom screen (Screen 3.Z) to ' ' (Blank). After a short time, the status of the job changes to Disappeared.
If the remote node is not active or not connected to the home node, you should activate the remote node or reconnect the home node and the remote node. If this is not possible, you must notify Control-M of the event by changing the value in the NJE field in the Active Environment Zoom screen (Screen 3.Z) to ' ' (Blank). After a short time, the status of the job changes to Disappeared.
If the previous suggestions do not resolve the problem, perform the following procedure:
To open a BMC Customer Support case for an NJE issue
In member CTMPARM of the IOA PARM library, set parameter DBGMCS=Y.
Restart the Control-M monitor
Set traces 33, 39, and 79 by issuing the following MVS modify command:
F ctm, TRACE=(33,39,79)
where ctm is the name of your Control-M monitor STC.
Reproduce the problem.
Reset the CTMPARM parameters to their original value and turn off the traces.
Send the following documentation to BMC Customer Support:
Job print-screen of 3.Z
Complete joblog of Control-M monitor STC
IOALOG from the relevant period of time (Use IOACPLG1 from IOA.JCL library to copy the log to a sequential file.)
Extracts from the syslogs of the system where CTM runs and the remote system
NJE job sysout and the SDSF screen (or the output of any other comparable product) showing the sysout datasets
