Operator-requested simultaneous dump data capture

The MVS console operator might want to issue a dump request simultaneously to several CICS regions in the sysplex. There might be a problem in the sysplex where one or more CICS regions is hanging and, to fully diagnose and solve the problem, dump data captured at the same time is required.

Without this facility, such simultaneous dump data capture across multiple CICS regions in the sysplex is impossible.

Use the following command at the console:
DUMP COMM=()
R x,REMOTE=(SYSLIST=*),PROBDESC=(SYSDCOND,SYSDLOCL,(DFHJOBN,jobnames))
where:
  • REMOTE controls the issuing of dumps on remote systems.
  • SYSLIST=* means the request is to be routed to all remote systems.
  • PROBDESC is problem description information, as follows:
    • SYSDCOND is an MVS keyword that specifies that a dump is to be taken on remote MVS images if the IEASDUMP.QUERY exit responds with return code 0. CICS supplies DFHDUMPX as the IEASDUMP.QUERY exit.
    • SYSDLOCL is an MVS keyword that drives the IEASDUMP.QUERY exit on the local and remote MVS images. This allows the CICS regions on the local MVS region to be dumped.
    • DFHJOBN is a CICS keyword. The operator should include the generic job name. This is used by DFHDUMPX to determine which address spaces to dump.

For a description of all command options, see z/OS MVS System Commands.

If you adopt a suitable naming convention for your CICS regions, this can be used to define suitable generic job names to determine which CICS regions to dump. For recommendations on naming conventions, see z/OS V1R1.0-V1R12.0 Parallel Sysplex Application Migration. If you follow these recommendations, the generic job name for all CICS regions in the sysplex would be CICS*.



dfhs1c00245.html | Timestamp icon Last updated: Monday, 5 June 2017