JES2DIAG - Individual Download
==============================

SOURCE
------
This source is taken directly from the supplied zDIAG Stable 3.2 self-contained package.
The REXX member retains CRLF line endings and is intended for text/ASCII transfer to z/OS.

PURPOSE
-------
Correlate JES2 Health Monitor alerts, PCE delays, checkpoint/MAS state, CPU context, XCF evidence and concurrent JES2 resource shortages.

STANDALONE USE
--------------
Place JES2DIAG in a site-approved SYSPROC or SYSEXEC library and invoke it from TSO/E.
Use TSO JES2DIAG HELP for the built-in usage/reference text.
Use TSO JES2DIAG SAMPLE to create the utility's built-in synthetic sample report.

zDIAG SUITE USE
---------------
For the normal zDIAG panel/batch workflow, use the full self-contained package instead of installing
individual utilities into the foreground SYSPROC/SYSEXEC concatenation. In suite mode the diagnostic
members are stored in <SITEHLQ>.EXEC and the ZDIAG launcher submits them through ZDBATCH.

INVOCATION EXAMPLES
-------------------
  TSO JES2DIAG
  TSO JES2DIAG 60
  TSO JES2DIAG 9203 60
  TSO JES2DIAG 9207 60
  TSO JES2DIAG CKPT 60
  TSO JES2DIAG HEALTH 30
  TSO JES2DIAG SAMPLE
  TSO JES2DIAG HELP

REQUIREMENTS / AUTHORIZATION
----------------------------
The utility is read-only, but the evidence it can collect depends on the TSO user's SDSF, SAF,
console-command and other z/OS authorities required by that utility. Review the built-in HELP text and
the full zDIAG README/INSTALL files before production use.

RETURN CODE POLICY
------------------
RC 00 means a usable diagnostic report was produced. A HIGH/CRITICAL finding does not by itself make
the utility return non-zero. Non-zero RCs represent invocation, collection or execution/report failure.
