Status Information

The command INGJLM STATUS which can also be issued in a NetView PIPE returns the current status of the monitoring task and its monitored data sets:

Figure 1. Job Log Monitoring status information
Status of task INGTJLM: {ACTIVE|INACTIVE|SUSPENDED}
Monitoring on recycle : {RESUME|RESET|N/A}
Owner    Jobname  Jobid    DDname   Status    Freq. Last        Read  Passed
         Procstep Step                                         LRead LPassed
-------- -------- -------- -------- --------- ----- -------- ------- -------
xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxxx mm:ss hh:mm:ss       n       n
                                                                   n       n
xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxxx mm:ss hh:mm:ss       n       n
         xxxxxxxx xxxxxxxx                                         n       n
xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxxx mm:ss hh:mm:ss       n       n
                  xxxxxxxx                                         n       n
*** Status complete ***
The status of a data set shows the following information:
  E........
The data set is marked "in error" and is not monitored any longer.
  .A.......
The data set is allocated.
  ..O......
The data set has been opened successfully.
  ...U.....
The user is not allowed to read the data set.
  ....S....
The monitoring of the data set is ACF-based.
  .....M...
All messages are passed to automation.
  ......J..
The corresponding job has not been found on the chain of active address spaces.
  .......I.
The spool data set is not initialized. The allocation of the data set is retried at the next monitoring interval. This repeats until the data set has been initialized.
  ........N
The ddname has defined the SPIN attribute. That means the corresponding spool data set can be spun off during processing.
The frequency shows the interval in minutes and seconds between two checks for accumulated messages. The next column shows the time when the last check occurred. The last two numbers show the total number of messages that have been read as well as the number of messages that have been passed to the automation table. The second status line of each data set shows the number of message read and passed to automation since the last check.