z/VM: CP Commands and Utilities Reference - z/VM - IBM

RETRIEVE
2. You can interrupt RETRIEVE processing by entering the EXTERNAL command.
You can then decide to stop processing altogether or request a summary of the
records collected so far and resume processing by responding to a prompting
message issued by the RETRIEVE utility.
3. As records are collected, they are placed in one or more CMS files based upon
their type.
System accounting records are placed in a file named ACCOUNT $Ammddyy
where mmddyy indicates the month, day, and year on which the files were
collected.
Error recording records are added either to the file XAEREPIO RECORD for
outboard type records, or the file XAEREPMC RECORD for inboard type
records. The CPEREPXA utility needs these files for its processing. Error
recording records are also placed in XAEREPSD RECORD when LOGROUTE
is specified.
Note: Short object recording (OBR) records are not useful for configuration and
error management and are not routed by the LOGROUTE parameter.
Each symptom record is placed in a separate CMS file whose name is based
on the time the symptom record was processed by CP. All symptom record files
have the characters SYM as the last three characters of the file type. You can
use the CMS VIEWSYM command to select symptom records for viewing based
on user-specified criteria. If a symptom record is received that contains
unformatted dump-related data supplied by a virtual machine, the portion of the
symptom record containing the dump data is not formatted by the VIEWSYM
command; it is presented as raw hexadecimal data. The maximum size
symptom record supported by z/VM is 4K bytes.
4. At least eight 800-byte CMS disk records must be available on your A-disk and
your virtual machine storage size must be at least 512K bytes in size in order to
use this command.
5. When LOGROUTE is specified, the user ID and node ID can be either a VM or
TSO system.
6. When LOGROUTE is specified, RETRIEVE utility processing accumulates
certain error records in a CMS file named XAEREPSD RECORD A. The records
collected are ones which should be handled as soon as possible. The records
include: long outboard type records for permanent errors on 3380 models D, E,
J, and K; long outboard type records for serial switches (9033 and 9032);
temporary outboard type records with a fault symptom code of 9F9F; service
alert records (type A3); and serial incident records (type A2).
The file is routed to the specified user ID every time the indicated time interval
elapses. It is also routed when a service alert or serial incident record is
received, even if the time interval has not yet elapsed. After the file is sent, it is
erased.
If you used a CP EXTERNAL command to halt RETRIEVE processing, any
accumulated records will be routed to the user ID.
7. The RETRIEVE utility does not support recording retrieval to SFS directories.
8. The RETRIEVE utility attempts to periodically close the files which it creates
and updates. The committing of the close can be delayed if there are other files
on the disk which are open. This can occur when RETRIEVE has been invoked
by an EXEC and files were opened but not closed prior to invoking RETRIEVE.
It is recommended that all files be closed on the target disk prior to invoking
RETRIEVE so that the closes performed by RETRIEVE are not delayed.
Chapter 3. CP Utilities 1863