|
|
Despite the documentation states so, tracing of report processing seems to be not possible with NOM running under Unix. If you choose this option (command TRACE, for instance) you'll get a screen "Trace Report Processing JES" with z/OS related input fields. An appropriate way to trace report processing under Linux together with a Linux version of that screen would be a real improvement!
Thats true, with NOM 3.5 the report tracing function is available for Report Identifications POWER, JES and BS2000 and only on the corresponding monitor operating system.
So this function is not available
on monitor operating system Unix
for other Report Identifications like Natural or Unix
with the multinode concept (only local monitor operating system)
There was the idea to use the API NOMLGUSN to write user log entries from the separation exit as alternative.
with version 3.5 the multinode concept was introduced; the report tracing depends no more on the monitor operating system; now there could be many different source operating systems side by side; there should be a dialogue where you can choose the node, the report is to be read from for tracing; depending on the selection you can present the specific trace processing screen for the choosen plattform