CAPTURE (capturing and printing a table)
The CAPTURE command captures the communication between an API program,
including a WUI session, and its connected CMAS when API resource
table records are requested, or the communication between CICSPlex
SM monitor programs and a MAS when Monitor data is collected in the
MAS. In either case, data is written to a JES spool file called Sxxxxxxx,
where xxxxxxx is a numeric identifier, under the
CMAS (tblname option) or MAS (*MASMON option).
The format of the CAPTURE command is one of the following:
CAPTURE tblname userid count (available in a CMAS only)
CAPTURE *MASMON montype count (available in a MAS only)- tblname
- Is an API resource table name. The Resource Tables Reference manual lists all API resource tables.
- userid
- Is the API/WUI user ID. Only requests from this user are captured.
- count
- Is a number from 0 though 999. the number indicates how many times
a capture is performed.
You can reissue the CAPTURE command with the same table name and user ID to update the count. A count of zero deletes the CAPTURE entry.
- *MASMON
- Captures monitor data as it is collected by a MAS.
- montype
- Is the type of monitor data to be captured:
- MCICS
- CICS regions
- MCONN
- Connections
- MDBX
- Db2® and DBCTL resources
- MFILE
- Files
- MGLBL
- Global resources
- MJRNL
- Journals
- MPROG
- Programs
- MTDQS
- Transient data queues
- MTERM
- Terminals
- MTRAN
- Transactions
Note: For tblname, the count is the number of GET
requests captured. For *MASMON, the count is the
number of monitor intervals captured.
For example:
CAPTURE MONDEF USER39 3captures the next three MONDEF table API/WUI GET requests issued by USER39. All related MALs and queues are printed.