Collecting Abend Information

When an AVS abend occurs, perform the following steps:

1. Collect information about the error.
   • Save the console sheet or spooled console output from the AVS virtual machine.
   • Save and process any dumps that AVS produces, using Dump Viewing Facility commands (see Using AVS Dumps to Diagnose Problems).
   • Save any TRSOURCE file that contains AVS data (see Using System Trace Data to Diagnose Problems).
2. Collect system status information. The following information can help you better determine problems:
   • The system load at the time of the failure on any systems using AVS and the status of each system (for example, did another system abend?).
   • The types of applications using AVS at the time and any information about them.
   • The physical configuration of the systems in use.
3. Recover from the abend to continue processing.

   When an abend occurs in AVS, either because AVS issued an abend or because an AVS or GCS operation caused a program exception, AVS produces a dump using the VMDUMP command (described in the z/VM: CP Commands and Utilities Reference).

z/VM: Other Components Messages and Codes lists AVS abend codes. See z/VM: Diagnosis Guide for more information about diagnosing problems in AVS.