z/vm: system messages and codes . cp · system messages and codes ... system messages and codes-cms...

z/VM

System Messages and Codes CP Version 5 Release 1

GC24-6119-01

Note! Before using this information and the product it supports, be sure to read the general information under Notices on page 487.

Second Edition (December 2004)

This edition applies to version 5, release 1, modification 0 of IBM z/VM (product number 5741-A05) and to all subsequent releases and modifications until otherwise indicated in new editions.

This edition replaces GC24-6119-00.

Copyright International Business Machines Corporation 1991, 2004. All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

About this Book . . . . . . . . . . . . . . . . . . . . . . . . v Who Should Read This Book . . . . . . . . . . . . . . . . . . . . v What You Should Know before Reading This Book . . . . . . . . . . . . v What This Book Contains . . . . . . . . . . . . . . . . . . . . . v Where to Find More Information . . . . . . . . . . . . . . . . . . . vi

PDF Links to Other Books . . . . . . . . . . . . . . . . . . . . vi How to Send Your Comments to IBM . . . . . . . . . . . . . . . . . vi

Summary of Changes . . . . . . . . . . . . . . . . . . . . . . vii GC24-6119-01, z/VM Version 5 Release 1, Updated Edition . . . . . . . . vii GC24611900, z/VM Version 5 Release 1 . . . . . . . . . . . . . . vii GC24603004, z/VM Version 4 Release 4 . . . . . . . . . . . . . . viii GC24603003, z/VM Version 4 Release 3 . . . . . . . . . . . . . . viii

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . 1 z/VM Message Format . . . . . . . . . . . . . . . . . . . . . . 1

Spool File Bridge Messages . . . . . . . . . . . . . . . . . . . 3 z/VM XEDIT Messages . . . . . . . . . . . . . . . . . . . . . 3 Messages with 4nxx Identifiers . . . . . . . . . . . . . . . . . . 3 Messages From Other Products . . . . . . . . . . . . . . . . . . 3 Unnumbered Responses . . . . . . . . . . . . . . . . . . . . . 6

z/VM Message Syntax Conventions . . . . . . . . . . . . . . . . . . 6 Message Variables . . . . . . . . . . . . . . . . . . . . . . . 6

Displaying Messages at the Terminal . . . . . . . . . . . . . . . . . 9 Messages Sent Through IUCV . . . . . . . . . . . . . . . . . . . 10 Displaying Messages in Other Languages . . . . . . . . . . . . . . . 10 Using the Online HELP Facility . . . . . . . . . . . . . . . . . . . 10 Getting Information for a Message with No Message ID . . . . . . . . . . 10

Chapter 2. System Codes . . . . . . . . . . . . . . . . . . . . 13 General User Action . . . . . . . . . . . . . . . . . . . . . . . 13 System Operator Action . . . . . . . . . . . . . . . . . . . . . 13 Control Program (CP) Abend Codes . . . . . . . . . . . . . . . . . 14 Abnormal Termination (Abend) Dumps . . . . . . . . . . . . . . . . 14 Abend Codes, Explanations, and Recommended Actions . . . . . . . . . 14 Abend Code Format . . . . . . . . . . . . . . . . . . . . . . . 14 Wait States . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Control Program (CP) Enabled and Disabled . . . . . . . . . . . . 133 Where to Find the Disabled Wait State Code . . . . . . . . . . . . 133

DDR Automatic Restore Waitstate PSWS . . . . . . . . . . . . . . . 134 Stand-Alone Dump Utility . . . . . . . . . . . . . . . . . . . . . 134 Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . 136

Chapter 3. System Messages . . . . . . . . . . . . . . . . . . 137 Control Program (CP) Messages . . . . . . . . . . . . . . . . . . 137 VM Dump Tool (VMDT) Messages . . . . . . . . . . . . . . . . . 471 Spool File Bridge (XSPOOL) Messages . . . . . . . . . . . . . . . 485

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . 487 Programming Interface Information . . . . . . . . . . . . . . . . . 488 Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . 489

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . 491

Copyright IBM Corp. 1991, 2004 iii

Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . 493 Where to Get z/VM Books . . . . . . . . . . . . . . . . . . . . 493 z/VM Base Library . . . . . . . . . . . . . . . . . . . . . . . 493

System Overview . . . . . . . . . . . . . . . . . . . . . . 493 Installation and Service . . . . . . . . . . . . . . . . . . . . 493 Planning and Administration . . . . . . . . . . . . . . . . . . . 493 Customization . . . . . . . . . . . . . . . . . . . . . . . . 493 Operation . . . . . . . . . . . . . . . . . . . . . . . . . 493 Application Programming . . . . . . . . . . . . . . . . . . . . 493 End Use . . . . . . . . . . . . . . . . . . . . . . . . . . 494 Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . 494

Books for z/VM Optional Features . . . . . . . . . . . . . . . . . 494 Data Facility Storage Management Subsystem for VM . . . . . . . . . 494 Directory Maintenance Facility . . . . . . . . . . . . . . . . . . 494 Performance Toolkit for VM . . . . . . . . . . . . . . . . . . . 495 Resource Access Control Facility . . . . . . . . . . . . . . . . . 495

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497

iv z/VM: System Messages and Codes CP

About this Book

This reference book is intended to help you understand the CP, VM Dump Tool and Spool File Bridge messages and codes produced by z/VM, and recommends actions you can take in response to them.

Who Should Read This Book This book is intended for all users of z/VM who want information about CP, VM Dump Tool and Spool File Bridge messages and codes the system issues.

What You Should Know before Reading This Book A general knowledge of commands is useful for implementing recommended actions.

What This Book Contains This book is divided into the following sections:

The Introduction contains:

v The format of messages that z/VM generates v Notational conventions this publication uses (Syntax) v Information on displaying messages at the terminal v Using the Online HELP Facility.

The System Codes are divided into the following categories:

v Control Program (CP) Abend Codes v Wait State codes v Return codes

The System Messages section of this publication is divided as follows:

v Control Program (CP) Messages v VM Dump Tool (VMDT) Messages v Spool File Bridge Messages.

z/VM Programming Interfaces::

This book contains information on z/VM Programming Interfaces. z/VM provides you with a broad range of Programming Interfaces, which are available using the following facilities:

v CP DIAGNOSE instructions v Certain z/VM control blocks v Data record formats, such as accounting records, intended to be processed by

application programs

v CP system services (such as *MSG) v CP assembler macros (such as IUCV and APPCVM)

In general, z/VM Programming Interfaces are designed to be used exclusively from programs (often using binary or other machine-level formats as parameter values) and are usually supported in a compatible manner from release to release.

Copyright IBM Corp. 1991, 2004 v

IBM may also ship other program materials (primarily macros), but these are internal facilities designed only for use between z/VM components and modules and are not intended to be used as Programming Interfaces.

Where to Find More Information See the Bibliography at the back of this book.

PDF Links to Other Books The PDF version of this book provides links to other IBM books by file name. The name of the PDF file for an IBM book is unique and identifies the book and its edition. The book links provided in this book are for the editions (PDF file names) that were current when this PDF file was generated. Newer editions of some books (with different file names) may exist. A PDF link from this book to another book works only when a PDF file with the requested file name resides in the same directory as this book.

How to Send Your Comments to IBM IBM welcomes your comments. You can send us comments about this book or other VM documentation using any of the following methods:

v Complete and mail the Readers Comments form (if one is provided at the back of this book) or send your comments to the following address:

IBM Corporation Department 55JA, Mail Station P384 2455 South Road Poughkeepsie, New York 12601-5400 U.S.A.

FAX (United States and Canada): 1-845-432-9405 FAX (Other Countries): +1 845 432 9405

v Send your comments by electronic mail to one of the following addresses: Internet: [email protected]

IBMLink (US customers only): IBMUSM10(MHVRCFS)

v Submit your comments through the VM Feedback page (Contact z/VM) on the z/VM Web site at www.ibm.com/eserver/zseries/zvm/forms/.

Please provide the following information in your comment or note:

v Title and complete publication number of the book (including the suffix) v Page number, section title, or topic you are commenting on

If you would like a reply, be sure to include your name, postal or email address, and telephone or FAX number.

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.

vi z/VM: System Messages and Codes CP

http://www.ibm.com/eserver/zseries/zvm/forms/

Summary of Changes

This book contains terminology, maintenance, and editorial changes. Technical changes or additions to the text and illustrations are indicated by a vertical line to left of the change.

GC24-6119-01, z/VM Version 5 Release 1, Updated Edition This edition includes support announced after the announcement of z/VM Version 5 Release 1 (z/VM V5R1) or programming enhancements provided after the general availability of z/VM V5R1. These programming enhancements may be provided through z/VM service by program temporary fixes (PTFs) for authorized program analysis reports (APARs), as indicated.

The following changes and additions have been made for this edition:

v Most of the new and changed messages, codes, and related text in this book are the result of the following z/VM Version 5 Release 1.0 functions and routines that have been added or enhanced (this list is in alphabetical order and not all inclusive):

FCP LUN Access Support (APAR VM63328)

Enabled for LookAt

The messages documented in this book can also be accessed by using the LookAt online message retrieval tool.

GC24611900, z/VM Version 5 Release 1 This edition supports the General Availability of z/VM Version 5 Release 1 (z/VM V5R1).


v Most of the new and changed messages, codes, and related text in this book are the result of the following z/VM Version 5 Release 1.0 functions and routines that have been added or enhanced (this list is in alphabetical order and not all inclusive):

Layer 2 LAN Switching and Transport

SCSI FCP Disk Support

v z/VM V5R1 is designed to operate only on IBM zSeries, or equivalent servers that support IBM z/Architecture (64-bit). As a result, certain functions are not provided by z/VM V5R1:

IPL from a 31-bit image of the CP nucleus

Preferred (V=R and V=F) virtual machines

Paging of the CP nucleus

Messages and abend codes related to these functions have been removed. The descriptions of many other messages and abend codes have been modified.

v The SPTAPE command is not supported on z/VM V5R1. Messages and abend codes for SPTAPE have been removed.

v System/370 architecture (370 mode) virtual machines are not supported on z/VM Version 4 or later. Obsolete 370 references have been removed. However, 370 Accommodation is still supported.

Copyright IBM Corp. 1991, 2004 vii

Enabled for LookAt

The messages documented in this book can also be accessed by using the LookAt online message retrieval tool.



v Information about HCP8300HCP8499 messages, formerly in z/VM: Guide for Automated Installation and Service, have been moved to this manual.

v Most of the new and changed messages, codes, and related text in this book are the result of the following z/VM V4R4 functions and routines that have been added or enhanced (this list is in alphabetical order and not all inclusive):

ESS Flash Copy

Ficon Cascading Switches

I/O Configuration with HCD/HCM

Virtual Switch and VLAN Enhancements

VM Dump Tool Enhancements

3590 H Tape


Most of the new and changed messages, codes and related text in this book are the result of the following z/VM V4R3 functions and routines that have been added or enhanced (this list is in alphabetical order and not all inclusive):

v Automated Shutdown Support v Virtual Machine Accounting Improvements v Shared Tape Support v Virtual Machine Resource Manager Support

viii z/VM: System Messages and Codes CP

Chapter 1. Introduction

There are three system messages and codes books: z/VM: System Messages and Codes - CMS and REXX/VM, z/VM: System Messages and Codes - CP, and z/VM: System Messages and Codes - AVS, Dump Viewing Facility, GCS, TSAF, and VMSES/E. For diagnosis of system problems, use these books in conjunction with the z/VM: Diagnosis Guide.

Refer to the z/VM: Migration Guide for a list of changed messages.

Although no attempt is being made to define job responsibilities, for the purposes of clarifying responses to messages, this manual uses the terms user, operator, and programmer in the following manner:

User Someone who logs onto a virtual machine.

Operator The person responsible for keeping the system running. This person does the IPL, the running, and the shutdown of the system. This work can be done from a real system console or a virtual system console.

Programmer The person responsible for keeping the system running and making software and storage changes.

z/VM Message Format Messages consist of a message identifier (for example, DMSACC017E) and message text. The identifier distinguishes messages from each other. The text is a phrase or sentence describing a condition that has occurred or requesting a response from the user.

The format of most message identifiers is:

xxxmmm###s

or

xxxmmm####s

This message format consist of four fields:

xxx The 3-character prefix indicates which z/VM component or facility, or which other product, contains the module that generated the message.

mmm The 3-character module code indicates which module generated the message. This field is usually an abbreviation of the name of the module in which the error occurred.

Note: Most z/VM books that provide reference information for messages omit this field from the listed messages. (A message may be issued by several modules.) If you request HELP information for a message, you can include the module code or omit it. (HELP ignores it.)

### or #### The numeric message number consists of three or four digits that are associated with the condition that caused the message to be generated.

Copyright IBM Corp. 1991, 2004 1

s The 1-character severity code is a letter that indicates what kind of condition caused the message. The definition of the severity codes depends on the nature of the routine producing the message.

Table 1 summarizes the message type, its corresponding prefix, the severity codes and their meaning for each of the z/VM components.

Table 1. Types and Meanings of Severity Codes

Message Type Prefix Severity Code

Meaning

AVS (APPC/VM VTAM Support) AGW I W E S

Information only Warning Error Severe error

CMS (Conversational Monitor System)

DMS R I

W E S T

Response Information only Warning Error Severe Error Terminating error

CMS Pipelines FPL I W E

Information only Warning Error

CP (Control Program) HCP A D E I

W

Immediate action required Decision Error Information System Wait

Dump Viewing Facility HCS A E I

Immediate action required Error Information

GCS (Group Control System) GCT R I E S T

Response Information only Error Severe error Terminating error

TCP/IP (Transmission Control Protocol/Internet Protocol)

DTC SNALNK SNMP SQE TCP TFTP UFT X25

E I R W

Error Information Response Warning

TSAF (Transparent Services Access Facility)

ATS I W E S T

Information only Warning Error Severe error Terminating error

VM Dump Tool HCQ E I

W

Error Information Warning

VMRM (Virtual Machine Resource Manager)

IRM E I

W


Introduction

2 z/VM: System Messages and Codes CP

Table 1. Types and Meanings of Severity Codes (continued)

Message Type Prefix Severity Code

Meaning

VMSES/E (Virtual Machine Service Enhancements Staged/Extended)

VMFITN

R I

W E S T

Response Information only Warning Error Severe Error Terminating error

LE (Language Environment) CEE EDC IBM IGZ

E I

W


Spool File Bridge Messages Spool File Bridge messages can be found in z/VM: System Messages and Codes - CP. They are somewhat unique and do not follow the convention described for the other messages. They are referred to as XSPOOL messages.

z/VM XEDIT Messages Error messages for XEDIT are located in the CMS section of this publication. z/VM XEDIT messages are spread between message numbers 497E and 700E. However, the messages within the 500 range (DMSmmm500E - DMSmmm599S) are issued only for XEDIT.

Messages with 4nxx Identifiers All messages issued from the CMSBAM saved segment, as well as many of the messages issued from the CMSVSAM and CMSAMS saved segments are identified by a 4nxx prefix. The text of these messages is in VSE format rather than the standard CMS format. Explanations for these messages are not in this manual. The appropriate message manual to be used for reference for 4nxx prefix messages is determined by the associated access method. Messages relating to Sequential Access Method (SAM) are described in VSE/Advanced Functions Messages. Messages relating to Virtual Storage Access Method (VSAM) are described in VSE/VSAM Messages and Codes.

Messages From Other Products Many products are available for z/VM, but the messages generated by those products are not documented in this publication. The z/VM message prefixes included in this publication can be found in Table 1 on page 2.

Messages for other products usually have a 3-character or 4-character message prefix that is unique to that product. Table 2 on page 4 lists many of those message prefixes you may encounter and provides you with the corresponding product names that are not part of the z/VM component set. Even though this list is not all inclusive, it should help you determine the source of most messages not documented in this book. If you need assistance with or publications for these products, please contact your IBM representative or the IBM branch office serving your locality.

Introduction

Chapter 1. Introduction 3

Table 2. Other Message Prefixes and the Products That Generate Them

Prefix Product Name

ACG Remote Spooling Communications Subsystem (RSCS)

ACH Remote Spooling Communications Subsystem (RSCS)

ADM Graphical Data Display Manager (GDDM)

AKQ Page Printer Formatting Aid/370 (PPFA/370)

APB Print Services Facility/VM (PSF/VM)

APK Print Services Facility/VM (PSF/VM)

APQ Print Services Facility/VM (PSF/VM)

APR Print Services Facility/VM (PSF/VM)

APS Print Services Facility/VM (PSF/VM)

ASM High Level (HL) Assembler

CBD Hardware Configuration Definition (HCD)

CXA Network Control Program (NCP)

CXB Network Control Program (NCP)

CXC Network Control Program (NCP)

CXD Network Control Program (NCP)

CXS Network Control Program (NCP)

CXT Network Control Program (NCP)

DAS Application System (AS)

DCH Cross-System Product (CSP)

DDD DisplayWrite

DGT Data Facility Storage Management Subsystem/VM (DFSMS/VM)

DIT Data Interfile Transfer, Testing, & Operations (DITTO)

DKL DisplayWrite

DMT Remote Spooling Communications Subsystem (RSCS)

DSI NetView

DSM Document Composition Facility (DCF)

DSQ Query Management Facility (QMF)

DTI VM Systems Network Architecture (SNA) Service Application

DTO Data Interfile Transfer, Testing, & Operations (DITTO)

DUI NetView

DUT Data Interfile Transfer, Testing, & Operations (DITTO)

DVH Directory Maintenance Program (DIRMAINT)

DVI Structured Query Language/Data System/VM (SQL/DS/VM)

DVM Pass Through/VM (PVM)

DWM DisplayWrite

DWO NetView

DZA ProcessMaster

DZG Cross-System Product (CSP) or VisualGen Host Services

DZI Overlay Generation Language (OGL/370)

EDD DisplayWrite

Introduction


Table 2. Other Message Prefixes and the Products That Generate Them (continued)

Prefix Product Name

EDF BookMaster

EDJ BookManager

EEQ Hardware Configuration Manager (HCM)

EFG Master Pass Through VM (MPVM)

EGV NetView

EIJ BookManager

EKG NetView

EKL DisplayWrite

EKZ Cross-System Product (CSP)

ELA Cross-System Product (CSP) or VisualGen Host Services

EMG Graphical Display and Query Facility (GDQF)

EMH Graphical Display and Query Facility (GDQF)

EMI Graphical Display and Query Facility (GDQF)

EPU Office Vision/VM (OV/VM)

EUW Cross-System Product (CSP)

EUY NetView

EYV NetView

EZA Transmission Control Protocol/Internet Protocol (TCP/IP)

EZE Cross-System Product (CSP)

EZF Cross-System Product (CSP)

EZG Cross-System Product (CSP)

EZH Cross-System Product (CSP)

FZE Cross-System Product (CSP)

GSU OpenExtensions Shell and Utilities

IBM Programming Language 1 (PL/1)

IBM SAA AD/Cycle Language Environment/370 (LE/370)

ICH Resource Access Control Facility (RACF)

ICK Device Support Facilities (ICKDSF)

IEL Programming Language 1 (PL/1)

IFC Environmental Error Record Editing and Printing (EREP)

IGZ SAA AD/Cycle Language Environment/370 (LE/370)

IKF VS COBOL/FORTRAN

ILB SAA AD/Cycle Language Environment/370 (LE/370)

ILX VS COBOL/FORTRAN

IRR Resource Access Control Facility (RACF)

ISP Interactive System Productivity Facility (ISPF)

IST Virtual Telecommunications Access Method (VTAM)

ITN Advanced Digital Delivery: See the Advanced Digital Delivery Users Guide, SC23-3281, for more information on these messages.

ITP Teleprocessing Network Simulator (TPNS)

Introduction


Table 2. Other Message Prefixes and the Products That Generate Them (continued)

Prefix Product Name

RPI Resource Access Control Facility (RACF)

Unnumbered Responses All unnumbered responses indicating the successful completion of a command (such as ready messages) are included in the following publications:

v z/VM: CP Commands and Utilities Reference v z/VM: CMS Commands and Utilities Reference.

Unnumbered responses can also be the result of executing system generation macro instruction or service programs. These responses, referred to as MNOTES, are documented in logic listings only.

z/VM Message Syntax Conventions The syntax used in the z/VM messages as printed in this book is as follows:

v For uppercase messages (some CMS and TSAF messages), variables are denoted by lowercase; for mixed-case messages (most CMS, most CP, most TSAF, all GCS, and all AVS messages), variables are denoted by italics. These variable names are replaced at execution time with the information they describe.

Note: There may be situations where the same message is displayed in both mixed and uppercase.

See Table 3 for a partial list of variables used in this publication. (This table does not contain every message variable, just those that might be a little more difficult to identify.)

v Any single quote (') in a message text in the book will be displayed when the message appears on your screen.

v Anything within braces {...|...} indicates alternate text that will be selected at execution time.

v Anything within brackets [...] may be optionally left out, depending on the condition arising.

Message Variables Table 3 contains the selected message variables that are used in this book.

Table 3. Selected Message Variables

Variable Meaning

a... alphabetic or numeric information

bbcchh bin, cylinder, and head

cc cylinder number

cchhr cylinder, head, record

char character

col column

cm command code, in hexadecimal

cpuaddr A virtual CPU address in hexadecimal.

cpuid central processing unit identification

Introduction


Table 3. Selected Message Variables (continued)

Variable Meaning

csw channel status word

date system date

ddname data definition name (for OS Simulation)

devclass class of IBM device

devname mnemonic name for an IBM device type

devtype IBM device type

dirid directory ID

execname filename of an exec

exectype filetype of an exec

fileid fn ft [fm]

fm file mode

fn file name

ft file type

form A form name specifying the type of paper or cards on which to print or punch an output file. The form name is one to eight characters in length.

hexloc A 1-digit to 8-digit hexadecimal number that represents a location in storage. The maximum value is 7FFFFFFF.

Of course, when you substitute a value for hexloc, it can never be larger than the size of the real or virtual machine storage to which it refers.

imagelib 3800 printer image library

ldev The letter L followed by a 1-digit to 4-digit hexadecimal number that represents a logical device number. Note that L1, L01, L001, and L0001 all represent the same logical device number.

ldev-ldev A range of logical device numbers. The second logical device number must be greater than or equal to the first. For example, L2A0-L2A2 refers to the logical device numbers L2A0, L2A1, and L2A2.

libname library name

libnum The library sequence number that identifies a 3495 Tape Library Dataserver.

lrecl logical record length

luname A 1-character to 8-character logical unit name that identifies a SNA terminal or printer. It is the name from the VTAM definition of the device as a SNA logical unit.

membername library member name

mode mode letter, or mode letter and mode number

mmm module name code

name The 1-character to 8-character name of a saved segment.

n... decimal information

nodeid node of a user

page page number

Introduction



Variable Meaning

pathid virtual machine path identification

prefix prefix subcommand or macro

psw program status word

range range (of addresses or registers)

rdev A 1-digit to 8-digit hexadecimal number that represents a real device number. This is the hardware configured physical device number.

rdev-rdev A range of real device numbers. The second device number must be greater than or equal to the first. For example, 02A0-02A2 refers to real device numbers 02A0, 02A1, and 02A2.

recfm record format

rid resource identifier

routine CMS or GCS routine

rr record number

rstor real storage address

segname segment name

sense sense bytes

spoolid The spool file identification number that CP assigns to each spool file for a user ID. The ID number ranges from one to four decimal digits.

storarea storage area

subl.book a book of a sublibrary

svc supervisor call number

sysname system name

type One of the following device types: CONS Console CTCA Channel-to-channel adapter CTLR communications controller DASD Direct access storage device DEV Any other device GRAF Display device KBD 3215 (non-console) LINE 270X device MSC Mass storage controller PRT Printer PUN Card punch RDR Card reader TAPE Tape drive

userid The 1-character to 8-character name that identifies the user to z/VM. This is essentially the name by which the system knows you.

vdev A 1-digit to 4-digit hexadecimal number that represents a virtual device number.

vdev-vdev A range of virtual device numbers. The second device number must be greater than or equal to the first. For example, 01D0-01D2 refers to virtual device numbers 01D0, 01D1, and 01D2.

Introduction



Variable Meaning

vname virtual screen name

volid volume identifier of the device

vstor virtual storage address

wname window name

x... hexadecimal information

yyyy reason code (GCS abend)

Displaying Messages at the Terminal Messages are displayed differently depending on how you enter the CP SET EMSG command. The choices and their resulting displays are:

Command Display

SET EMSG CODE xxxmmm####s

SET EMSG OFF No message number or text

SET EMSG ON xxxmmm####s message text

SET EMSG IUCV See Messages Sent Through IUCV on page 10 for a description of the output if EMSG is set to IUCV.

SET EMSG TEXT only message text.

Note: CMS messages with a severity of S for Severe or T for Terminating are displayed as if the CP EMSG setting was ON, regardless of what CP SET EMSG setting is in effect at the time. For more information about message severity codes, refer to Table 1 on page 2. For a description of xxxmmm####s format, refer to z/VM Message Format on page 1.

When you log onto z/VM, the initial setting for the display of messages is installation dependent. Use the CP QUERY SET command to determine the current EMSG setting.

Use the message number to refer to the appropriate messages section of this book for a description of the message.

Note that in some cases, the text of a message is longer than a line on the display screen. The message text may be divided in the middle of a word and continued on the next line.

For a more detailed description of the SET EMSG command, refer to the z/VM: CP Commands and Utilities Reference.

Introduction


Messages Sent Through IUCV If SET EMSG IUCV has been specified and a connection to the message system service exists, then both the error code and text are to be passed to the virtual machine through IUCV. The application or code running in the virtual machine would then be responsible for processing the message and displaying it if necessary. If no IUCV connection exists, the message is handled as if SET EMSG ON had been entered. For a more detailed description of the SET EMSG command, refer to the z/VM: CP Commands and Utilities Reference.

The format of the information sent using IUCV is: xxxmmm####s message text

Refer to z/VM Message Format on page 1 for a description of xxxmmm####s format.

Displaying Messages in Other Languages All messages are documented in this book in American English; however, most messages are displayed at your terminal in the language set for your virtual machine. If your virtual machine is set to another language (either by the SET LANGUAGE command or the OPTION LANG directory statement), you will receive most z/VM messages in that language.

Using the Online HELP Facility You can receive online information about the messages described in this book using the z/VM HELP Facility. You can display information about a message by entering one of the following commands: help msgid or help msg msgid

For example, to display information about message DMS001E, you can enter one of the following commands: help dms001e or help msg dms001e

For more information about using the HELP Facility, see the z/VM: CMS Users Guide. To display the main HELP Task Menu, enter: help

For more information about the HELP command, see the z/VM: CMS Commands and Utilities Reference or enter: help cms help

Getting Information for a Message with No Message ID If you receive a message without a message ID, it could be because you have issued the CP command SET EMSG TEXT to display only message text, or an application program might have issued this command.

You can get information about a message with no message ID by searching for a portion of the message text using one of the following methods:

v Use the IBM LookAt Internet message search tool, located at http://www.ibm.com/servers/s390/os390/bkserv/lookat/.

Introduction


http://www.ibm.com/eserver/zseries/zos/bkserv/lookat/

Select the product release and enter the message text fragment in the Message ID field.

v Search for the message text in the PDF file or BookManager BOOK file for the appropriate messages book.

Use the VM Collection CD-ROM or go to the z/VM Internet Library, located at www.ibm.com/eserver/zseries/zvm/library/.

Note: With either method, do not use any portion of the message text containing values in your search string. The documentation for the message uses variables to represent fields in which data is returned. If you use actual values, your search string will not match.

Introduction


http://www.ibm.com/eserver/zseries/zvm/library/

Introduction


Chapter 2. System Codes

Codes are generated by the system in response to either an action or lack of action that has been detected. This section provides a summary of the various z/VM codes the user may receive. However, this summary is not all inclusive because of the unique codes that are generated for specific applications.

For more indepth information about the z/VM functions these codes originate from, refer to the z/VM publication related to the function in question.

General User Action When using z/VM commands, if error messages in the range of 001 to 349 persist, you should perform the following steps before contacting your system representative for programming assistance.

1. Keep the console listing that identifies the problem.

2. Attempt to reproduce the problem, making sure that the full error message function is in effect by entering the CP command: SET EMSG ON

3. Obtain the virtual machine's current configuration by entering the CP command: QUERY VIRTUAL

4. Where appropriate, and depending upon conditions, obtain a virtual storage dump by entering the CP command: VMDUMP 0-END

or DUMP 0-END

System Operator Action System operators (classes A, B, C, and D) who observe problems with z/VM commands should do the following:

1. Keep the console listing identifying the problem.

2. Attempt to reproduce the problem with full error message by entering the z/VM command: SET EMSG ON

3. Obtain the real machine's configuration status by entering the z/VM command: QUERY ALL

4. Enter the CP command again that has been causing the errors. If the problem recurs, obtain a CP dump by entering the SNAPDUMP command. Use the DUMPLOAD utility and the VM Dump Tool to inspect the dump.

For more information about SNAPDUMP and DUMPLOAD, refer to z/VM: CP Commands and Utilities Reference. For more information about the VM Dump Tool, refer to z/VM: VM Dump Tool.

Copyright IBM Corp. 1991, 2004 13

Control Program (CP) Abend Codes This section lists and explains the abend codes that z/VM CP issues.

Soft abends, taken when an error condition can be isolated to a single virtual machine or when system integrity is not endangered, are listed here along with hard abends. Soft abends are indicated by the words (soft abend) at the beginning of the explanation portion of the abend codes. Soft abends apply only to CP abends. Soft abends automatically try to recover (auto-restart).

Hard abends occur when CP detects an error condition that it cannot isolate to a single virtual machine or when system integrity is endangered.

Those abend codes that are not indicated as soft are hard abends. For more information on abends, refer to z/VM: System Operation and z/VM: Virtual Machine Operation.

Abnormal Termination (Abend) Dumps CP generates an abend dump whenever the system operator restarts the system using the system console (hardware), or when a software error occurs and CP is still operational. The operator should collect and save the dump for the system programmer and service personnel.

Abend Codes, Explanations, and Recommended Actions The abend codes are listed in alphanumeric order and include an explanation of why the abend occurred as well as suggestions for programmer responses.

Abend Code Format The format of an abend code is as follows:

mmm###

where:

mmm is the name, without its prefix, of the module that issued the abend. The complete module name is prefaced by HCP (for example, HCPmmm).

### is the code number, except for CP module PRG, when it is the program exception number.

The names of registers are abbreviated, for example, R3 for register 3.

The following is a list of the CP abend codes and in some cases the modules that issue them, the causes of the abnormal termination, and the actions the user should take to recover and continue.

AAK001

Explanation: (soft abend) The activation block lock has been destroyed.

User Response: The transaction is discarded. The lock word should never be destroyed when the activation block is found. Refer to z/VM: Diagnosis Guide for information on gathering the documentation

you need to assist IBM in diagnosing the problem, then contact your IBM support personnel.

AAL001

Explanation: (soft abend) The activation block lock has been destroyed.

User Response: The transaction is discarded and a

AAK001 AAL001


close is sent to the partner. The lock word should never be destroyed when the activation block is found. Refer to z/VM: Diagnosis Guide for information on gathering the documentation you need to assist IBM in diagnosing the problem, then contact your IBM support personnel.

AAS001

Explanation: (soft abend) A non-zero condition code was returned on an IUCV SEVER in the ISFC APPC mailbox.

User Response: The IUCV SEVER should always complete with condition code zero. Conversation clean up will continue. Refer to z/VM: Diagnosis Guide for information on gathering the documentation you need to assist IBM in diagnosing the problem, then contact your IBM support personnel.

AAS002

Explanation: (soft abend) A condition code of zero was returned on an APPCVM RECEIVE in the ISFC APPC mailbox.

User Response: At this point in the APPC mailbox processing, a Message Pending Interrupt has been received. A condition code of zero (indicating receive-ahead) should never occur. Processing continues as if an error occurred on the APPCVM RECEIVE (condition code 1). Refer to z/VM: Diagnosis Guide for information on gathering the documentation you need to assist IBM in diagnosing the problem, then contact your IBM support personnel.

AAT001

Explanation: (soft abend) A non-zero condition code was returned on an IUCV SEVER in the ISFC APPC mailbox.

User Response: The IUCV SEVER should always complete with condition code zero. Conversation clean up will continue. Refer to z/VM: Diagnosis Guide for information on gathering the documentation you need to assist IBM in diagnosing the problem, then contact your IBM support personnel.

AAT002

Explanation: (soft abend) During open_complete processing in the ISFC APPC mailbox, the target side of the APPC conversation is expecting PIP data on the connect, but the source side never indicated that it was sending PIP data.

User Response: This is most likely a timing problem. The APPC conversation is severed. Refer to z/VM: Diagnosis Guide for information on gathering the documentation you need to assist IBM in diagnosing the problem, then contact your IBM support personnel.

AAU001

Explanation: (soft abend) A non-zero condition code was received on an IUCV SEVER of the *IDENT path for an ISFC owned gateway in the ISFC APPC mailbox.

User Response: The IUCV SEVER should always complete with condition code zero. The cleanup of the gateway path will continue. Refer to z/VM: Diagnosis Guide for information on gathering the documentation you need to assist IBM in diagnosing the problem. Then contact your IBM support personnel.

ABC001

Explanation: (soft abend) HCPABC received an unexpected return code when scanning for or opening a soft abend dump file.

User Response: If message HCPABC9309E preceded this abend, the return code from an attempt to open a soft abend dump file is in R3. Otherwise, the return code is from a scanning operation and is in R15. Determine what the return code is, then contact your IBM support personnel.

ABF001

Explanation: An unexpected return code was received when opening the system dump spool file.

User Response: Contact your IBM support personnel.

ABF002

Explanation: An unexpected return code was received when reading, writing, or positioning the system dump spool file.


ABF003

Explanation: An unexpected return code was received when closing the system dump spool file.


ABN001

Explanation: An incorrect PSW address was calculated as the return address in the abending module when an asynchronous dump was requested.


ABN002

Explanation: Not enough storage was available to provide the necessary amount of static save areas for the soft abend process.


AAS001 ABN002

Chapter 2. System Codes 15

ABR001

Explanation: (soft abend) This is a generic abend that CP takes when it receives an unexpected return code from a routine.


ABR002

Explanation: (Soft abend) CP detected an unsupported return code being returned from an exit routine.

User Response: Check the trace table to determine which exit and entry point was called. Review the code associated with this entry point to determine the reason for returning an unsupported return code and correct the error. This is an error in customer or vendor written code; contact the author for additional assistance.

ACP002

Explanation: (soft abend) Issued when two or more journaling messages for the same failed Directory Broadcast request are received by an ISFC node with enhanced broadcast routing capabilities.

User Response: The directory broadcast completes normally, but no journaling messages are sent to any nodes that responded with invalid password on a failed userid/password directory broadcast. There is a programming error either in ISFC directory broadcast code, or in APPC delayed-connect processing. Refer to z/VM: Diagnosis Guide for information on gathering the documentation you need to assist IBM in diagnosing the problem, then contact your IBM support personnel.

ACR100

Explanation: (Soft abend) An attempt to acquire the System Resource Table lock (LKWRD defined in SSCSRTLK) failed because it had been destroyed. This indicates a programming error.

User Response: Refer to the z/VM: Diagnosis Guide to determine what data you will need to provide IBM to assist you with diagnosing this problem. Then contact IBM support personnel.

ACS001

Explanation: (soft abend) The ISFC directory broadcast routine was called with an invalid value in the field containing the number of requests (DBHNREQS). The value was either zero or negative.

User Response: The directory broadcast does not complete. There is a programming error either in the ISFC directory broadcast code or in APPC delayed-connect processing. Refer to z/VM: Diagnosis Guide for information on gathering the documentation you need to assist IBM in diagnosing the problem, then

contact your IBM support personnel.

ACV100

Explanation: (Soft abend) An attempt to acquire the System Resource Table lock (LKWRD defined in SSCSRTLK) failed because it had been destroyed. This indicates a programming error.

User Response: Refer to the z/VM: Diagnosis Guide to determine what data you will need to provide IBM to assist you with diagnosing this problem. Then contact IBM support personnel.

AFF001

Explanation: Issued by the HCPAFF module. This module is distributed as object code only. Therefore, no source program materials are available.

This module supports the processor affinity function, where an error has occurred due to a virtual processing unit establishing a processor feature requirement for a feature it had already required.

You cannot directly circumvent this problem.

User Response: Refer to z/VM: Diagnosis Guide for information on gathering the documentation you need to assist IBM in diagnosing the problem, then contact your IBM support personnel.

AFF002


This module supports the processor affinity function, where an error has occurred due to a feature manager being called to force an unload of a feature, and the feature was not unloaded.



AFF003


This module supports the processor affinity function, where an error has occurred due to a feature manager being called to handle a situation that is outside the scope of expected parameters.


User Response: Refer to z/VM: Diagnosis Guide for information on gathering the documentation you need to

ABR001 AFF003


assist IBM in diagnosing the problem, then contact your IBM support personnel.

AFF004


This module supports the processor affinity function, where an error has occurred due to an attempt to add a feature that the processor already had.



AFF005


This module supports the processor affinity function, where an error has occurred due to an attempt to delete a feature that the processor did not have.



AFF006


This module supports the processor affinity function, where an error has occurred due to an attempt to indicate that a processor feature has been loaded which the virtual processing unit did not require.



AFF007


This module supports the processor affinity function, where an error has occurred due to an attempt to indicate that a processor feature has been loaded which the virtual processing unit already had loaded.



AFF008


This module supports the processor affinity function, where an error has occurred due to an attempt to indicate that a feature is not loaded for a feature that the virtual processing unit did not have loaded.



AFS001

Explanation: The address passed to the aligned free storage manager (detected on block release only) was not valid because of one of these reasons:

v The block is not contained in an aligned free storage frame.

v The address of the block is not properly aligned. v The block already resides on an aligned free storage

available block list.


AFS002

Explanation: Aligned free storage internal chain damage occurred (detected on block release only) because of one of these reasons:

v The size of the block in FRMTE has been destroyed. v The FRMTE representing storage is not on the

SUBBK list, but it should be.


AIS001

Explanation: Issued by the HCPAIS module. This module is distributed as object code only. Therefore, no source program materials are available.

This module supports the Vector function, where an error has occurred due to an incorrect vector instruction issued from a users program.

You can circumvent this problem by branching around the user code for this vector instruction.

User Response: Refer to z/VM: Diagnosis Guide for

AFF004 AIS001


information on gathering the documentation you need to assist IBM in diagnosing the problem, then contact your IBM support personnel.

ALC001

Explanation: (soft abend) The module that issues this abend is distributed as object code only; therefore, no source program materials are available.


ALC002

Explanation: The module that issues this abend is distributed as object code only; therefore, no source program materials are available.


ALC003



ALC004



ALC005



ALE001

Explanation: Issued by the HCPALE module. This module is distributed as object code only. Therefore, no source program materials are available.


ALE002

Explanation: Issued by the HCPALE module. This module is distributed as object code only. Therefore, no source program materials are available.


ALF001

Explanation: The available list replenishment function was attempting to take a frame from a frame list, but the frames on the list were chained improperly.

User Response: Inspect the process of chaining and unchaining frames from the user-owned frame list. Examine the dump and determine which VMDBK or SNTBK owns this user-owned frame list. VMDFR1ST should point to the first frame on the list, and VMDFRLST should point to the last frame on the list. The frame being unchained at the time of the abend may not have been chained properly when it was put on the user-owned frame list. R14 points to the address in HCPALF where CP detected the abend.

ALF002

Explanation: An attempt was made to reclaim a real storage frame currently containing a pageable page, but the required serialization (the owning virtual configurations base VMDBK VMDPTIL Page Table Invalidation Lock) is not held shared or exclusive.


ALF010

Explanation: While adding a frame to the available list or taking a frame from the available list, CP determined that the frames on the list were chained improperly. It may also be that the count of available frames became negative.

User Response: Inspect the process of chaining and unchaining frames on the available list. Examine the dump for previous manipulations of the available list to

ALC001 ALF010


see when and where the damage occurred. Examine the code for the module that caused the damage. R14 points to the address in HCPALF where CP detected the abend.

ALF013

Explanation: The available list replenishment function was attempting to decrease the count of resident pages for an address space (ASCCTPRS), but the count was already negative.

User Response: Inspect the process of increasing and decreasing the count of resident pages (ASCCTPRS). Examine the dump and determine the ASCBK or SNTBK for which this count is being decreased. A negative count indicates an incorrect list. This count increases when a frame is added to the list and decreases when a frame is taken from the list. Inspect the validity of the list. R14 points to the address in HCPALF where CP detected the abend.

ALL001

Explanation: (soft abend) CP could not delete the VMDBK block from the VMDBK hash table for a user who issued the LOGOFF command. The hash key specified in VMDUSER does not exist in the VMDBK hash table. System execution will continue.

User Response: There is probably a software problem. Contact your IBM support personnel to diagnose and correct the problem.

ALL002

Explanation: While processing the cyclic list, module HCPALL required the VMDBK to be in a hold lock state and it is not. If an internal logic problem exists, HCPALLVM traverses the list. If the lock was improperly obtained, HCPALLLR releases the lock.

User Response: Examine the storage dump. You can use the abend address to determine whether the failure occurred in an HCPALLVM call or an HCPALLLR call. The address of the VMDBK being examined is in R1 for HCPALLVM or R10 for HCPALLLR. Look at the system trace table for the sequence of events that led to this situation.

ALL015

Explanation: A user was completing the LOGOFF process and was no longer eligible to execute work on the system. VMDCTCRT, the count of critical processes in progress, was still a positive value. This indicates that some CP code has incremented the counter (generally when the user becomes a defer-lock owner) without ever decrementing it appropriately.

User Response: Use the CP trace table to attempt to locate code that incremented VMDCTCRT without

decrementing it appropriately. Contact your IBM support personnel.

ALL020

Explanation: Subroutine RELCYCLH was called to release the cyclic list hold lock for a particular VMDBK when that lock was not held.

User Response: Normally, RELCYCLH is called following GETCYCLH when dequeuing a VMDBK from the global or a local cyclic list. Examine the registers to determine the caller of RELCYCLH, and the VMDBKs involved. R10 points to the VMDBK being detached. R1 points to the corresponding origin VMDBK, which contains the cyclic list lockword, VMDCYCLH.

ALM001



ALM002

Explanation: (soft abend) Parameters were passed in R2 to an entry point in HCPALM that does not accept parameters. The parameter register must be zeros to allow for possible future enhancements to the module.

User Response: Using the trace table, determine the caller of the HCPALM entry point, and why a nonzero parameter was passed.

ALM003



ALP001

Explanation: The available list replenishment function was attempting to take a frame from a user-owned frame list, but the frames on the list were chained improperly. It may also be that a frame on the user-owned frame list does not have the FRMOWNED bit on.

User Response: Inspect the process of chaining and unchaining frames from the user-owned frame list. Examine the dump and determine the VMDBK or SNTBK that owns the user-owned frame list.

ALF013 ALP001


VMDFR1ST should point to the first frame on the list, and VMDFRLST should point to the last frame on the list. FRMFPNT is the forward pointer to the next frame on the list, and FRMBPNT is the backward pointer to the previous frame on the list. The frame being unchained at the time of the abend may not have been chained properly on the user-owned frame list. Another possibility is that the FRMOWNED flag is not on in the frame table entry, indicating that this frame may not belong to this VMDBK. R14 points to the address in HCPALP where CP detected the abend.

ALP003

Explanation: The available list replenishment function was attempting to take a frame from a user-owned frame list, but the frame state was incorrect.

User Response: FRMPTE field in the frame table entry contains an address of zero. This indicates the frame is incorrect, since it is on a user-owned frame list but does not point to a valid page table entry. Inspect the process of chaining and unchaining frames from the user-owned frame list. Examine the dump to determine the VMDBK or SNTBK control block that owns the frame. R14 points to the address in HCPALP where CP detected the abend.

ALS002


User Response: Inspect the process of chaining and unchaining frames from the user-owned frame list. Examine the dump and determine the VMDBK or SNTBK that owns the user-owned frame list. VMDFR1ST should point to the first frame on the list, and VMDFRLST should point to the last frame on the list. FRMFPNT is the forward pointer to the next frame on the list, and FRMBPNT is the backward pointer to the previous frame on the list. The frame being unchained at the time of the abend may not have been chained properly on the user-owned frame list. Another possibility is that the FRMOWNED flag is not on in the frame table entry, indicating that this frame may not belong to this VMDBK.

ALS003

Explanation: The available list replenishment function was attempting to decrease the count of resident pages for a VMDBK or an ASCBK, but the count was already negative or would go negative.

User Response: Inspect the process of increasing and decreasing the count of resident pages. Examine the dump and determine the VMDBK or ASCBK for

which this count is being decreased. A negative count indicates an incorrect user-owned frame list. This count increases when a frame is added to the list and decreases when a frame is taken from the list. Inspect the validity of the user-owned frame list.

ALS004

Explanation: The available list replenishment function was attempting to take a frame from a user-owned frame list, but the frame state was incorrect.

User Response: FRMPTE field in the frame table entry contains an address of zero. This indicates the frame is incorrect, since it is on a user-owned frame list but does not point to a valid page table entry. Inspect the process of chaining and unchaining frames from the user-owned frame list. Examine the dump to determine the VMDBK or SNTBK control block that owns the frame.

ALT001


User Response: Inspect the process of chaining and unchaining frames from the user-owned frame list. Examine the dump and determine the VMDBK or SNTBK that owns the user-owned frame list. VMDFR1ST should point to the first frame on the list, and VMDFRLST should point to the last frame on the list. FRMFPNT is the forward pointer to the next frame on the list, and FRMBPNT is the backward pointer to the previous frame on the list. The frame being unchained at the time of the abend may not have been chained properly on the user-owned frame list. Another possibility is that the FRMOWNED flag is not on in the frame table entry, indicating that this frame may not belong to this VMDBK.

ALT002

Explanation: The available list replenishment function was attempting to decrease the count of resident pages for a VMDBK or an SNTBK, but the count was already negative.

User Response: Inspect the process of increasing and decreasing the count of resident pages (VMDCTPRS). Examine the dump and determine the VMDBK or SNTBK for which this count is being decreased. A negative count indicates an incorrect user-owned frame list. This count increases when a frame is added to the list and decreases when a frame is taken from the list. Inspect the validity of the user-owned frame list. R14 points to the address in HCPALP where CP detected the abend.

ALP003 ALT002


AMD001

Explanation: (soft abend) Indicates an incorrect number of extents were passed to HCPMSM.


AMD002

Explanation: (soft abend) Indicates an insufficient number of DX2BKs were passed to HCPMSM.


APJ001

Explanation: (Soft abend) This module is distributed as object code only; therefore, no source program materials are available.


APU001

Explanation: (Soft abend) This module is distributed as object code only; therefore, no source program materials are available.


ARR001

Explanation: (Soft abend) An unexpected and unrecoverable error occurred during Diagnose x254 processing. R14 in the system dump contains the address of where the error occurred in module HCPARR.


ARS001

Explanation: (Soft abend) An unexpected and unrecoverable error occurred during Diagnose x254 processing. R14 in the system dump contains the address of where the error occurred in module HCPARS.


ASD001

Explanation: (Soft abend) A newly created ASIT was found to not be valid.


ASI002

Explanation: Issued by the HCPASI module. This module is distributed as object code only. Therefore, no source program materials are available.


ASM002

Explanation: (soft abend) Parameters were passed in R2 to an entry point in HCPASM that does not accept parameters. The parameter register must be zeros to allow for possible future enhancements to the module.

User Response: Using the trace table, determine the caller of the HCPASM entry point, and why a non-zero parameter was passed.

ASM012

Explanation: The count of the total size, in pages, of all private spaces owned by this user has gone negative. This value should never be less than zero.


ASN001



ASN002

Explanation: (soft abend) Parameters were passed in R2 to an entry point in HCPASN that does not accept parameters. The parameter register must be zeros to allow for possible future enhancements to the module.

User Response: Using the trace table, determine the caller of the HCPASN entry point, and why a non-zero parameter was passed.

AMD001 ASN002


ASN012

Explanation: The count of the total size, in pages, of all private spaces owned by this user has gone negative. This value should never be less than zero.


ASR001

Explanation: This abend may be soft or hard. An untrue assertion has been encountered. Assertions are made by modules using the HCPASERT macro. When a false assertion is discovered, an ASR001 abend results. Whether it is a hard abend or a soft abend depends on what the invoker specified for the ABEND parameter of the HCPASERT macro. This abend does not indicate an error in HCPASR, but rather an error in the code that uses the HCPASERT macro.

User Response: R13 at the time of the abend contains the address of a SAVBK which contains the contents of the invokers registers at the time of the failure. The WRKPRGOP field in the savearea contains the program old PSW at the time of the monitor event. The instruction address in that PSW points just past the Monitor Call instruction in the failing HCPASERT macro. The WRKGRPCT field in the savearea contains the number of the failing assertion within the assertion group, or 1 if the assertion is not in a group. If the abend is hard, assertion checking will not be activated during recovery, to avoid a possible abend loop. It may be reactivated with the SET CPCHECKING command.

ASR002

Explanation: (soft abend) An unrecognized assertion code is found in the HCPASERT parameter list.

User Response: This condition indicates a mismatch between the parameter list generated by the HCPASERT macro and the parameter-list parsing in HCPASR. Either the parameter list has become corrupted, or the HCPASERT invocation and HCPASR module are at different update levels. The WRKPRGOP field in the savearea contains the program old PSW at the time of the monitor event. The instruction address in that PSW points just past the Monitor Call instruction in the failing HCPASERT macro. The WRKGRPCT field in the savearea contains the number of the failing assertion within the assertion group, or 1 if the assertion is not in a group.

ASR003

Explanation: (soft abend) An illegal length was specified for the source storage operand of a VALUE assertion, made with the HCPASERT macro, and associated with the SET CPCHECKING command. Valid lengths are 1 through 4. This abend does not indicate an error in HCPASR, but rather an error in code which uses the HCPASERT macro.

User Response: Examine the HCPASERT invocation and correct the length on the source value. The WRKPRGOP field in the savearea contains the program old PSW at the time of the monitor event. The instruction address in that PSW points just past the Monitor Call instruction in the failing HCPASERT macro. The WRKGRPCT field in the savearea addresses by R13 contains the number of the failing assertion within the assertion group, or 1 if the assertion is not in a group.

ASR004

Explanation: Code invoked for a CODE assertion did not return with R13 unchanged. R13 must be left unchanged, because it contains the address of the savearea used to remember information about the invoker. This abend does not indicate an error in HCPASR, but rather an error in the code that uses the HCPASERT macro.

User Response: Examine the HCPASERT invocation and correct the length on the source value. If it has been overlaid since the original monitor event, the instruction address in the program old PSW points just past the Monitor Call instruction in the failing HCPASERT macro.

ASR005

Explanation: Code invoked for a CODE assertion itself caused another recursive CODE assertion to be invoked. CODE assertion code may not issue CODE assertions or call code that makes CODE assertions. This abend does not indicate an error in HCPASR, but rather an error in code that uses the HCPASERT macro.

User Response: Examine the HCPASERT invocation and correct it. CODE assertion code may not issue CODE assertions or call code that makes CODE assertions. The WRKPRGOP field in the save area contains the program old PSW at the time of the monitor event. The instruction address in that PSW points just past the Monitor Call instruction in the failing HCPASERT macro.

ASR006

Explanation: A CODE assertion savearea has not been allocated (or its address has been zeroed).

User Response: Refer to z/VM: Diagnosis Guide for information to gather the documentation you need to assist IBM in diagnosing the problem, then contact your IBM support personnel.

ASR007

Explanation: Code invoked for a CODE assertion apparently lost control because it returned on a different processor than the one from which it was called. This abend does not indicate an error in HCPASR, but rather

ASN012 ASR007


an error in code that uses the HCPASERT macro.

User Response: Examine the HCPASERT invocation and correct it. Code invoked for a CODE assertion may not lose control. The WRKPRGOP field in the savearea contains the programs old PSW at the time of the monitor event. The instruction address in that PSW points just past the monitor call instruction in the failing HCPASERT macro.

ATL001

Explanation: (soft abend) HCPATLDV was entered using a VMDBK that was not a base VMDBK.

User Response: R13 points to a save area. Identify the caller by the return address and base register in the save area pointed to by R13. The caller did not provide the base VMDBK.

ATL002

Explanation: HCPATLDV was entered on the system VMDBK.

User Response: R13 points to a save area. Identify the caller by the return address and base register in the save area pointed to by R13. The caller did not provide the VMDBK of the currently dispatched user.

ATR001

Explanation: (soft abend) HCPATRDV was entered using a VMDBK that was not a base VMDBK.

User Response: R13 points to a save area. Identify the caller by the return address and base register in the save area pointed to by R13. The caller did not provide the base VMDBK.

ATR002

Explanation: HCPATRDV was erroneously entered when the system VMDBK was the current VMDBK.

User Response: R13 points to a save area. Identify the caller by the return address and base register in the save area pointed to by R13. The caller did not provide the VMDBK of the currently dispatched user.

BID001

Explanation: (soft abend) An unexpected return code was returned to HCPBID (the main processing routine for DIAGNOSE code x250). The return code is in R15; the address of the routine that returned the code is in R14.

User Response: Determine what the return code and routine address is, then contact your IBM support personnel.

BID002

Explanation: (soft abend) The host-ART lookaside block (HALBK) is full and no more entries can be added. This condition was discovered while processing block I/O entry-list block (BELBK) entries for DIAGNOSE code x250 and trying to add an entry to the HALBK. R7 contains the address of the HALBK.


BIE001

Explanation: Issued by the HCPBIE module. This module is distributed as object code only. Therefore, no source program materials are available.


BIE002

Explanation: Issued by the HCPBIE module. This module is distributed as object code only. Therefore, no source program materials are available.


BIM001

Explanation: (soft abend) What should be an impossible situation occurred while processing a Block I/O SEND Request. The type of error is determined by the code stored in R1.

The following is a description of these codes:

R1 = 1 A SEND Request Block (SNDBK) is being FRETed that is not on the SEND Request Queue. The SEND Request may not have been performed.

R1 = 2 An incorrect return code was found in a DVIOP Block.

R1 = 3 An incorrect or unexpected return code was received from a called routine.

R1 = 4 The number of I/O operations scheduled for a single SEND Request exceeded 256.

R1 = 5 A greater number of I/O Operations occurred for a SEND Request than there was scheduled.

User Response: Examine the internal trace table and storage dump to determine which routine within HCPBIM is detecting the error condition. R3 holds the address of the routine that caused the abend.

ATL001 BIM001


BIN001

Explanation: (soft abend) During initialization of the ISFC subsystem, the outbound APPC mailbox was found to be non-empty. This queue of work for ISFC should be empty on ISFC start-up.

User Response: This can indicate some problem in the ISFC clean-up code. Refer to z/VM: Diagnosis Guide for information on gathering the documentation you need to assist IBM in diagnosing the problem, then contact your IBM support personnel.

BIN002

Explanation: (soft abend) During initialization of the ISFC subsystem, the inbound APPC mailbox was found to be non-empty. This queue of work for ISFC should be empty on ISFC start-up.


BIN003

Explanation: (soft abend) During initialization of the ISFC subsystem, the ISFC APPC/IUCV path table was found to be non-empty. This table should be empty on ISFC start-up.


BIN004

Explanation: (soft abend) During initialization of the ISFC subsystem, the ISFC session table was found to be non-empty. This table should be empty on ISFC start-up.


BIN005

Explanation: (soft abend) During initialization of the ISFC subsystem, the ISFC resource/gateway identifier table was found to be non-empty. This table should be empty on ISFC start-up.

User Response: This can indicate some problem in the ISFC clean-up code. Refer to z/VM: Diagnosis Guide for information on gathering the documentation you need to assist IBM in diagnosing the problem, then

contact your IBM support personnel.

BIN006

Explanation: (soft abend) During initialization of the ISFC subsystem, the ISFC node table was found to be non-empty. This table should be empty on ISFC start-up.


BIN007

Explanation: (soft abend) During initialization of the ISFC subsystem, the ISFC link table was found to be non-empty. This table should be empty on ISFC start-up.


BIN008

Explanation: (soft abend) During initialization of the ISFC subsystem, the ISFC directory broadcast response list was found to be non-empty. This list should be empty on ISFC start-up.


BIN009

Explanation: (soft abend) During initialization of the ISFC subsystem, the ISFC directory broadcast list was found to be non-empty. This list should be empty on ISFC start-up.


BIN011

Explanation: (soft abend) During initialization of the ISFC subsystem, the ISFC queue of work to be resumed was found to be non-empty. This queue should be empty on ISFC start-up.

User Response: This can indicate some problem in the ISFC clean-up code. Refer to z/VM: Diagnosis

BIN001 BIN011


Guide for information on gathering the documentation you need to assist IBM in diagnosing the problem, then contact your IBM support personnel.

BIN012

Explanation: (soft abend) During initialization of the ISFC subsystem, the ISFC queue of work to be processed was found to be non-empty. This queue should be empty on ISFC start-up.


BIN013

Explanation: (soft abend) During initialization of the ISFC subsystem, the ISFC link mailbox work queue was found to be non-empty. This queue should be empty on ISFC start-up.


BIN015

Explanation: (soft abend) During initialization of the ISFC subsystem, the outbound CPAP mailbox work queue was found to be non-empty. This queue should be empty on ISFC start-up.


BIN016

Explanation: (soft abend) During initialization of the ISFC subsystem, the inbound CPAP mailbox work queue was found to be non-empty. This queue should be empty on ISFC start-up.


BIN017

Explanation: (soft abend) During initialization of the ISFC subsystem, the CPAP mailbox input queue was found to be non-empty. This queue should be empty on ISFC start-up.


BIO001

Explanation: (soft abend) The DASD block I/O message handler or sever handler failed to locate the block I/O connect block associated with an IUCV SEND or an IUCV SEVER request. The request was made to a device that is connected to the DASD block I/O system service.

User Response: Verify the VDEVBIOA in the VDEVBK that points to the block I/O block to ensure that the device is still connected to the DASD block I/O system service.

BIR001

Explanation: (soft abend) An error occurred while processing a DIAGNOSE code x250 request. The type of error can be determined by the reason code stored in register 1. The codes are:

R1 = 1 An attempt was made to dequeue a BRQBK from the request chain, but the block was not found.

R1 = 4 The count of active I/O operations for a request (BRQDBICT) is about to go negative. Either too many interrupts have come in for this request, or (more likely) someone isnt incrementing or decrementing the count properly.

R1 = 5 The BKIBK lock was found to be destroyed while attempting to process an interruption.

R1 = 6 The VDISK I/O lock was found to be destroyed while attempting to process an asynchronous request.

User Response: Determine what the return code is, then contact your IBM support personnel.

BIT001

Explanation: (Hard abend) An attempted release occurred of a lock that is not held. An attempt was made to relinquish the lock for a bit map, or to switch the lock from one state to another. However, upon entry to HCPBIT, register 2 did not point to the address of a BITMP control block; register 2 pointed to a fullword of zeros.

User Response: Examine the routine that called HCPBIT and determine why R2 pointed where it did.

BIN012 BIT001


BIT002

Explanation: (Hard abend) A module called HCPBITRL while the BITMPLCK lock was held. A call was made to HCPBIT to release storage for the bit map, but the bit map lock was still held.

User Response: Examine the dump. Determine why the lock was not previously relinquished.

BIT008

Explanation: (Hard abend) The address of the frame is not page aligned. The address of a frame that is being processed by HCPBITRL is not a 4K boundary. R2 contains the address of the frame.

User Response: Examine the dump. Trace back th

z/vm: system messages and codes . cp · system messages and codes ... system messages and codes-cms...

Documents