z/vm: cp messages and codes(ptfs) for authorized pr ogram analysis r eports (ap ars). gc24-6177-12,...

z/VM

CP Messages and CodesVersion 6 Release 4

GC24-6177-12

IBM

Note:Before you use this information and the product it supports, read the information in “Notices” on page 705.

This edition applies to version 6, release 4, modification 0 of IBM z/VM (product number 5741-A07) and to allsubsequent releases and modifications until otherwise indicated in new editions.

This edition replaces GC24-6177-11.

© Copyright IBM Corporation 1991, 2018.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

About This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiIntended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiWhere to Find More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Links to Other Documents and Websites . . . . . . . . . . . . . . . . . . . . . . . . vii

How to Send Your Comments to IBM . . . . . . . . . . . . . . . . . . . . . . . ix

Summary of Changes for z/VM CP Messages and Codes . . . . . . . . . . . . . . xiGC24-6177-12, z/VM Version 6 Release 4 (March 2018) . . . . . . . . . . . . . . . . . . . . . xiGC24-6177-11, z/VM Version 6 Release 4 (December 2017) . . . . . . . . . . . . . . . . . . . . xiGC24-6177-10, z/VM Version 6 Release 4 (August 2017). . . . . . . . . . . . . . . . . . . . . xiGC24-6177-09, z/VM Version 6 Release 4 (March 2017) . . . . . . . . . . . . . . . . . . . . . xiGC24-6177-08 z/VM Version 6 Release 4 . . . . . . . . . . . . . . . . . . . . . . . . . xiiGC24-6177-07, z/VM Version 6 Release 3 (February 2016) . . . . . . . . . . . . . . . . . . . . xiiGC24-6177-06, z/VM Version 6 Release 3 (May 2015) . . . . . . . . . . . . . . . . . . . . . xiiGC24-6177-05, z/VM Version 6 Release 3 (June 2014) . . . . . . . . . . . . . . . . . . . . . xiiiGC24-6177-04, z/VM Version 6 Release 3 . . . . . . . . . . . . . . . . . . . . . . . . . xiii

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

z/VM XEDIT Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Messages with 4nxx Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Messages From Other Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Unnumbered Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

z/VM Message Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Displaying Messages at the Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Messages Sent Through IUCV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Displaying Messages in Other Languages. . . . . . . . . . . . . . . . . . . . . . . . . . 7Using the Online HELP Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Getting Information for a Message with No Message ID . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2. System Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9General User Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9System Operator Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9CP Abend Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Abend Dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Abend Code Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Abend Codes A - M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Abend Codes N - Z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Wait States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170CP Enabled and Disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Common Hardware Wait States . . . . . . . . . . . . . . . . . . . . . . . . . . . 171DDR Automatic Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Stand-Alone Dump Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Chapter 3. System Messages . . . . . . . . . . . . . . . . . . . . . . . . . 173CP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

HCP001E - HCP499E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173HCP500I - HCP999W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227HCP1001E - HCP1999E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279HCP2000E - HCP2991I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

© Copyright IBM Corp. 1991, 2018 iii

HCP3001E - HCP5769E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458HCP6000E - HCP6899E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498HCP8000E - HCP8706E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604HCP9000W - HCP9968I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644

Installation Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667VM Dump Tool Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707Terms and Conditions for Product Documentation . . . . . . . . . . . . . . . . . . . . . . 707IBM Online Privacy Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709

Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711Where to Get z/VM Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711z/VM Base Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711z/VM Facilities and Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712Prerequisite Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713

iv z/VM: CP Messages and Codes

Tables

1. z/VM Message Prefixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22. Message Prefixes for Other Products . . . . . . . . . . . . . . . . . . . . . . . . . 43. Displaying Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64. PSW code format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1715. DDRFLAG3 Error Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . 1726. Return code meanings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1727. Record format for SECTABLE FILE. . . . . . . . . . . . . . . . . . . . . . . . . . 6318. Error codes in message HCQ004E. . . . . . . . . . . . . . . . . . . . . . . . . . 687

© Copyright IBM Corp. 1991, 2018 v

vi z/VM: CP Messages and Codes

About This Document

This document contains reference information that is intended to help youunderstand the control program (CP) and VM Dump Tool (VMDT) messages andcodes produced by version 6 release 4 of IBM® z/VM®, and recommends actionsyou can take in response to them. This document also explains message formats,conventions, and where to find additional information.

Intended AudienceThis information is intended for anyone using z/VM who wants descriptiveexplanations, system actions, and suggested responses to system issued CP andVMDT messages and codes. A general knowledge of z/VM commands is usefulfor implementing recommended responses.

Where to Find More InformationFor information about related documents, see “Bibliography” on page 711.

Links to Other Documents and WebsitesThe PDF version of this document contains links to other documents and websites.A link from this document to another document works only when both documentsare in the same directory or database, and a link to a website works only if youhave access to the Internet. A document link is to a specific edition. If a newedition of a linked document has been published since the publication of thisdocument, the linked document might not be the latest edition.

© Copyright IBM Corp. 1991, 2018 vii

viii z/VM: CP Messages and Codes

How to Send Your Comments to IBM

We appreciate your input on this publication. Feel free to comment on the clarity,accuracy, and completeness of the information or give us any other feedback thatyou might have.

Use one of the following methods to send us your comments:1. Send an email to [email protected]. Go to IBM z/VM Reader's Comments (www.ibm.com/systems/z/os/zvm/

zvmforms/webqs.html).

Include the following information:v Your namev Your email addressv The publication title and number:

z/VM V6.4 CP Messages and CodesGC24-6177-12

v The topic name or page number related to your commentv The text of your comment

When you send comments to IBM®, you grant IBM a nonexclusive right to use ordistribute your comments in any way it believes appropriate without incurring anyobligation to you.

IBM or any other organizations will use the personal information that you supplyonly to contact you about the issues that you submit to IBM.

If You Have a Technical Problem

Do not use the feedback methods listed above. Instead, do one of the following:v Contact your IBM service representative.v Contact IBM technical support.v See IBM: z/VM Support Resources (www.ibm.com/vm/service).v Go to IBM Support Portal (www.ibm.com/support/entry/portal/Overview).

© Copyright IBM Corp. 1991, 2018 ix

http://www.ibm.com/systems/z/os/zvm/zvmforms/webqs.htmlhttp://www.ibm.com/systems/z/os/zvm/zvmforms/webqs.htmlhttp://www.ibm.com/vm/service/http://www.ibm.com/support/entry/portal/Overview/

x z/VM: CP Messages and Codes

Summary of Changes for z/VM CP Messages and Codes

This document contains terminology, maintenance, and editorial changes. Technicalchanges or additions to the text and illustrations are indicated by a vertical line tothe left of the change. Product updates are provided as program temporary fixes(PTFs) for authorized program analysis reports (APARs).

GC24-6177-12, z/VM Version 6 Release 4 (March 2018)This edition includes changes to support product changes provided or announcedafter the general availability of z/VM® V6.4.

The supported product changes include:v [VM65414] Support to control the enablement of certain security modes in z/VMv [VM66098] z-Thin Provisioningv [VM66105] Enhanced support for external management of z/VM CPU resources

GC24-6177-11, z/VM Version 6 Release 4 (December 2017)This edition includes changes to support product changes provided or announcedafter the general availability of z/VM V6.4.

The supported product changes include:v [VM65918] VSwitch Link Aggregation Load Balancing Enhancementsv [VM65993] Encrypted Paging

GC24-6177-10, z/VM Version 6 Release 4 (August 2017)This edition includes changes to support product changes provided or announcedafter the general availability of z/VM V6.4.

The supported product changes include:v [VM65942] z/VM support for the IBM z14TM

v [VM65943] Extended Address Volume (EAV) minidisk supportv [VM65988] Processor Scalability Efficiency improvements

GC24-6177-09, z/VM Version 6 Release 4 (March 2017)This edition includes changes to support product changes provided or announcedafter the general availability of z/VM V6.4.

The supported product changes include:v [VM65872] Distributed IUCV enhancementsv [VM65925] NICDEF Security Controls

© Copyright IBM Corp. 1991, 2018 xi

GC24-6177-08 z/VM Version 6 Release 4This edition includes changes to support the general availability of z/VM V6.4.

The supported product changes include:v Architecture level set (ALS)v CP environment variablesv Determine installed servicev Dynamic simultaneous multithreading levelv ESA/390 removalv Expanded storage (XSTORE) support removedv FlashSystem support for FCP-attached SCSI disksv Guest Transactional Execution supportv HyperPAV technology exploitationv IBM z13® (Driver D27) and z13s I/O supportv LOGON security improvementv Non-default tape mode supportv QUERY SHUTDOWN commandv SCSI management queriesv SCSI reliability, availability, and serviceability (RAS) enhancementsv zManager support removed

A new section has been added with a list of some common hardware wait states.See “Common Hardware Wait States” on page 171.

GC24-6177-07, z/VM Version 6 Release 3 (February 2016)This edition includes changes to support product changes provided or announcedafter the general availability of z/VM V6.3.

The supported product changes include:v Vector Facility for z/Architecture® supportv Support for relocating the SSI persistent data record (PDR) without a planned

outage

GC24-6177-06, z/VM Version 6 Release 3 (May 2015)This edition includes changes to support product changes provided or announcedafter the general availability of z/VM V6.3.

The supported product changes include:v Support for z13®

v Crypto Express5S and enhanced domain supportv Simultaneous multithreading (SMT) supportv Increased CPU scalabilityv Multi-VSwitch Link Aggregation support

xii z/VM: CP Messages and Codes

GC24-6177-05, z/VM Version 6 Release 3 (June 2014)This edition includes changes to support product changes provided or announcedafter the general availability of z/VM V6.3.

The supported product changes include:v CPU pooling supportv PCIe Guest Direct Attach Supportv Soft Fence and Query Host Access GDPS Enhancements

GC24-6177-04, z/VM Version 6 Release 3This edition includes changes to support the general availability of z/VM V6.3.

The supported product changes include:v HiperDispatch supportv HiperSocket Completion Queue Guest Exploitation supportv IPL support for NSS in a Linux dumpv Large Memory Dump supportv Live Guest Relocation support for port based virtual switchesv Memory Scalabilityv Multiple Subchannel Set support for Mirrored DASDv Virtual Switch Recovery Stall Preventionv Prefix for installation messages changed from HCP to IUGv Cross System Extensions (CSE) support removedv User Class Restructure (UCR) support removed

Summary of Changes for z/VM CP Messages and Codes xiii

xiv z/VM: CP Messages and Codes

Chapter 1. Introduction

This book documents a subset of the messages issued by z/VM. (For other booksthat document z/VM messages, see Table 1 on page 2.) In general, messages areissued to alert you to a problem, to request that you perform some action, or toprovide information. For diagnosis of system problems, use this book inconjunction with the z/VM: Diagnosis Guide.

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

This book does not attempt to define job responsibilities or indicate who mightreceive a particular message.

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

The format of most message identifiers is:

xxxmmm###s or xxxmmm####s.

The message format consists of four fields:

xxx The 3-character prefix indicates which z/VM component, facility, orfeature, or which other product, contains the module that generated themessage. See Table 1 on page 2 and Table 2 on page 4.

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

Note: Most z/VM books that provide reference information for messagesomit this field from the listed messages as a message might be issued byseveral modules. If you request HELP information for a message, you caninclude the module code or omit it. (HELP ignores it.)

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

s The 1-character severity code is a letter that indicates what kind ofcondition caused the message. The severity codes used by z/VM and theirmeanings are:A Immediate action requiredD DecisionE ErrorI Information onlyR ResponseS Severe errorT Terminating errorW System wait (CP only), warning (all others)

© Copyright IBM Corp. 1991, 2018 1

Table 1 lists the message prefixes used by z/VM components, facilities, andfeatures, and indicates where those messages are documented.

Table 1. z/VM Message Prefixes

Prefix z/VM Component, Facility, orFeature

Where the Messages Are Documented

ACHA RSCS Data Interchange Manager z/VM: RSCS Networking Messages and Codes

AGW AVS (APPC/VM VTAM® Support) z/VM: Other Components Messages and Codes

ATS TSAF (Transparent Services AccessFacility)

z/VM: Other Components Messages and Codes

CBD HCD (Hardware ConfigurationDefinition)

z/OS and z/VM: Hardware Configuration ManagerUser's Guide (www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sc342670/$file/eequ100_v2r3.pdf)

CEE Language Environment® z/OS: Language Environment Runtime Messages(www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sa380686/$file/ceea900_v2r3.pdf)

CST RACF®® Security Server for z/VM z/VM: RACF Security Server Messages and Codes

DGT DFSMS/VM (Data Facility StorageManagement Subsystem for VM)

z/VM: DFSMS/VM Messages and Codes

DMKRPD RACF Security Server for z/VM z/VM: RACF Security Server Messages and Codes

DMKRPI RACF Security Server for z/VM z/VM: RACF Security Server Messages and Codes

DMS CMS (Conversational MonitorSystem)

z/VM: CMS and REXX/VM Messages and Codes

DMSFLD RACF Security Server for z/VM z/VM: RACF Security Server Messages and Codes

DMT RSCS Networking for z/VM z/VM: RSCS Networking Messages and Codes

DTC TCP/IP for z/VM z/VM: TCP/IP Messages and Codes

DVH Directory Maintenance Facility forz/VM

z/VM: Directory Maintenance Facility Messages

EDC Language Environment z/OS: Language Environment Runtime Messages(www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sa380686/$file/ceea900_v2r3.pdf)

EEQ HCM (Hardware ConfigurationManager)

z/OS and z/VM: Hardware Configuration ManagerUser's Guide (www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sc342670/$file/eequ100_v2r3.pdf)

FCX Performance Toolkit for VM™ z/VM: Performance Toolkit Reference

FPL CMS Pipelines z/VM: CMS Pipelines User's Guide and Reference

FSM DFSMS/VM (Data Facility StorageManagement Subsystem for VM)


GCT GCS (Group Control System) z/VM: Other Components Messages and Codes

GSU OpenExtensions™ Shell and Utilities z/VM: OpenExtensions Commands Reference

HCP CP (Control Program) z/VM: CP Messages and Codes

HCPRPD RACF Security Server for z/VM z/VM: RACF Security Server Messages and Codes

HCPRPI RACF Security Server for z/VM z/VM: RACF Security Server Messages and Codes

HCPRPW RACF Security Server for z/VM z/VM: RACF Security Server Messages and Codes

HCQ VM Dump Tool z/VM: CP Messages and Codes

HCS Dump Viewing Facility z/VM: Other Components Messages and Codes

Introduction

2 z/VM: CP Messages and Codes

https://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sc342670/$file/eequ100_v2r3.pdfhttps://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sc342670/$file/eequ100_v2r3.pdfhttps://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sc342670/$file/eequ100_v2r3.pdfhttps://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sc342670/$file/eequ100_v2r3.pdfhttps://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sa380686/$file/ceea900_v2r3.pdfhttps://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sa380686/$file/ceea900_v2r3.pdfhttps://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sa380686/$file/ceea900_v2r3.pdfhttps://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sa380686/$file/ceea900_v2r3.pdfhttps://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sa380686/$file/ceea900_v2r3.pdfhttps://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sa380686/$file/ceea900_v2r3.pdfhttps://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sc342670/$file/eequ100_v2r3.pdfhttps://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sc342670/$file/eequ100_v2r3.pdfhttps://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sc342670/$file/eequ100_v2r3.pdfhttps://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sc342670/$file/eequ100_v2r3.pdf

Table 1. z/VM Message Prefixes (continued)

Prefix z/VM Component, Facility, orFeature

Where the Messages Are Documented

IBM Language Environment z/OS: Language Environment Runtime Messages(www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sa380686/$file/ceea900_v2r3.pdf)

ICH RACF Security Server for z/VM z/VM: RACF Security Server Messages and Codes

IGC Language Environment z/OS: Language Environment Runtime Messages(www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sa380686/$file/ceea900_v2r3.pdf)

IGD DFSMS/VM (Data Facility StorageManagement Subsystem for VM)


IKJ RACF Security Server for z/VM z/VM: RACF Security Server Messages and Codes

IOA OSA/SF (Open Systems AdapterSupport Facility)

Open Systems Adapter-Express Customer's Guide andReference (www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sa227935/$file/ioaz100_v2r3.pdf)

IRM VMRM (Virtual Machine ResourceManager)

z/VM: CMS and REXX/VM Messages and Codes

IRR RACF Security Server for z/VM z/VM: RACF Security Server Messages and Codes

ITN VMSES/E (Virtual Machine ServiceEnhancements Staged/Extended)


RAC RACF Security Server for z/VM z/VM: RACF Security Server Messages and Codes

RPI RACF Security Server for z/VM z/VM: RACF Security Server Messages and Codes

SNM TCP/IP for z/VM z/VM: TCP/IP Messages and Codes

SQE TCP/IP for z/VM z/VM: TCP/IP Messages and Codes

TCP TCP/IP for z/VM z/VM: TCP/IP Messages and Codes

UFT TCP/IP for z/VM z/VM: TCP/IP Messages and Codes

VMF VMSES/E (Virtual Machine ServiceEnhancements Staged/Extended)


VSM Ensemble No longer supported

z/VM XEDIT MessagesError messages for XEDIT are located in z/VM: CMS and REXX/VM Messages andCodes. z/VM XEDIT messages are spread between message numbers 497E and700E. However, the messages within the 500 range (DMSmmm500E -DMSmmm599S) are issued only for XEDIT.

Messages with 4nxx IdentifiersAll messages issued from the CMSBAM saved segment, as well as many of themessages issued from the CMSVSAM and CMSAMS saved segments are identifiedby a 4nxx prefix. The text of these messages is in z/VSE™ format rather than thestandard CMS format. Explanations for these messages are not in this manual.

The appropriate message manual to be used for referencing 4nxx prefix messages isdetermined by the associated access method. Messages relating to SequentialAccess Method (SAM) are described in z/VSE publications. Messages relating toVirtual Storage Access Method (VSAM) are described in VSAM publications.

Introduction

Chapter 1. Introduction 3

https://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sa380686/$file/ceea900_v2r3.pdfhttps://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sa380686/$file/ceea900_v2r3.pdfhttps://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sa380686/$file/ceea900_v2r3.pdfhttps://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sa380686/$file/ceea900_v2r3.pdfhttps://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sa380686/$file/ceea900_v2r3.pdfhttps://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sa380686/$file/ceea900_v2r3.pdfhttps://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sa227935/$file/ioaz100_v2r3.pdfhttps://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sa227935/$file/ioaz100_v2r3.pdfhttps://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sa227935/$file/ioaz100_v2r3.pdfhttps://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sa227935/$file/ioaz100_v2r3.pdf

Messages From Other ProductsMany products are available for z/VM, but the messages generated by thoseproducts are not documented in this publication. Messages for other productsusually have a 3-character or 4-character message prefix that is unique to thatproduct. Table 2 lists many of those message prefixes you may encounter andprovides you with the corresponding product names. Even though this list is notall inclusive, it should help you determine the source of most messages not issuedby z/VM.

Table 2. Message Prefixes for Other Products

Prefix Product Name

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)

ARI Db2® Server for VM

ASM High Level (HL) Assembler

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)

DDD DisplayWrite®

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

DKL DisplayWrite

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)

DVM VM/Pass-Through Facility (PVM)

DWM DisplayWrite

DWO NetView

DZA ProcessMaster®

DZG VisualGen Host Services

DZI Overlay Generation Language (OGL/370)

EAG REXX Runtime Library

EDD DisplayWrite

Introduction


Table 2. Message Prefixes for Other Products (continued)

Prefix Product Name

EDF BookMaster®

EDJ BookManager®

EFG VM/Pass-Through Facility (PVM)

EGV NetView

EIJ BookManager

EKG NetView

EKL DisplayWrite

ELA 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 OfficeVision/VM (OV/VM)

EUW Cross-System Product (CSP)

EUY NetView

EYV NetView

FAN REXX Compiler

IBM Programming Language 1 (PL/1)

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

ICK Device Support Facilities (ICKDSF)

IEL Programming Language 1 (PL/1)

IFC Environmental Error Record Editing and Printing (EREP)

IKF VS COBOL/FORTRAN

ILX VS COBOL/FORTRAN

ISP Interactive System Productivity Facility (ISPF)

IST Virtual Telecommunications Access Method (VTAM)

ITP Teleprocessing Network Simulator (TPNS)

Unnumbered ResponsesAll 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 Referencev z/VM: CMS Commands and Utilities Reference.

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

z/VM Message Syntax ConventionsThe syntax used in the z/VM messages is as follows:v Some messages are displayed in uppercase while others are displayed in mixed

or lowercase. However, there are many situations where the same message isdisplayed in both mixed and uppercase

Introduction


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

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

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

Displaying Messages at the TerminalMessages are displayed differently depending on how you enter the CP SET EMSGcommand. The commands, what they display, and their format are:

Table 3. Displaying Messages

Command Displays Format

SET EMSG CODE Message identifier only. xxxmmm####s

SET EMSG OFF Nothing. NA

SET EMSG ON Message identifier and text. xxxmmm####s text

SET EMSG TEXT Message text only. text

SET EMSG IUCV See “Messages Sent ThroughIUCV” for a description ofthe output if EMSG is set toIUCV.

xxxmmm####s text

Note: CMS messages with a severity of “S” for severe or “T” for terminating aredisplayed as if the CP EMSG setting was ON, regardless of what CP SET EMSGsetting is in effect at the time. For more information about message severity codesand the message format, refer to “z/VM Message Format” on page 1.

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

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

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

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

Messages Sent Through IUCVIf SET EMSG IUCV has been specified and a connection to the message systemservice exists, then both the error code and text are to be passed to the virtualmachine through IUCV. The application or code running in the virtual machinewould then be responsible for processing the message and displaying it ifnecessary. If no IUCV connection exists, the message is handled as if SET EMSGON 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:

Introduction


xxxmmm####s text

For more information about the message format, refer to “z/VM Message Format”on page 1.

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

Using the Online HELP FacilityYou can receive information about the messages described in this book using thez/VM HELP Facility. To display information about a message enter one of thefollowing commands:help msgid or help msg msgid

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

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

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

Getting Information for a Message with No Message IDIf you receive a message without a message ID, it could be because you haveissued the CP command SET EMSG TEXT to display only message text, or anapplication program might have issued this command. Without the message ID,you might not be able to determine which z/VM component or feature issued themessage, and therefore you might not know where to find information about themessage. In that case, you can go to the IBM Knowledge Center - z/VM(www.ibm.com/support/knowledgecenter/SSB27U) and use the search capabilityto search for a portion of the message text.

Note: For your search string, do not use any portion of the message textcontaining values provided by the system. The documentation for the messageuses variables to represent fields in which data is returned. If you use actualvalues, your search string will not match.

Introduction


http://www.ibm.com/support/knowledgecenter/SSB27Uhttp://www.ibm.com/support/knowledgecenter/SSB27U

Introduction


Chapter 2. System Codes

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

For more in-depth information about the z/VM functions these codes originatefrom, see the z/VM documentation related to the function in question.

General User ActionIf error messages in the range of 001 to 349 persist while using z/VM commands,you should perform the following steps before contacting your systemrepresentative for programming assistance.1. Keep the console listing identifying the problem.2. Attempt to reproduce the problem with full error message turned on.

SET EMSG ON

3. Obtain the virtual machine's current configuration.QUERY VIRTUAL

4. Where appropriate, and depending upon conditions, obtain a virtual storagedump.VMDUMP 0-END or DUMP 0-END

System Operator ActionSystem operators (classes A, B, C, and D) should do the following when theyobserve problems with z/VM commands.1. Keep the console listing identifying the problem.2. Attempt to reproduce the problem with full error message turned on.

SET EMSG ON

3. Obtain the real machine's current configuration.QUERY ALL

4. Enter the failing CP command again. If the problem recurs, obtain a CP dumpby entering the SNAPDUMP command. Use the DUMPLOAD utility and theVM Dump Tool to inspect the dump.For more information about SNAPDUMP and DUMPLOAD, refer to z/VM: CPCommands and Utilities Reference. For more information about the VM DumpTool, refer to z/VM: VM Dump Tool.

CP Abend CodesCP issued abend codes (hard, soft, and SNAP dump) are listed in alphanumericorder and include an explanation of why the abend occurred and a suggested userresponse.

Hard abends occur when CP detects an error condition that it cannot isolate to asingle virtual machine or when system integrity is endangered. All abends are hardabends unless otherwise noted.

© Copyright IBM Corp. 1991, 2018 9

Soft abends occur when an error condition can be isolated to a single virtualmachine or when system integrity is not endangered. Soft abends apply to CPabends only and automatic recovery (auto-restart) is attempted. You can control thetype of dump that is created as a result of a soft abend by using the CP SETABEND command. Soft abends are indicated by the following notation at thebeginning of the explanation: (soft).

SNAP dump abends occur when the SNAPDUMP command is issued by a user (orcalled by a module) to generate a system dump, identical to a hard abend dump,without terminating the system. SNAP dump abends are indicated by thefollowing notation at the beginning of the explanation: (snap).

Note that if more than one dump type is possible for an abend, all possible typesare indicated in the parentheses.

For more information on abends, see z/VM: System Operation and z/VM: VirtualMachine Operation .

Abend DumpsCP generates an abend dump whenever the system is restarted using the systemconsole (hardware), or when a software error occurs while CP is still operational.You should collect and save the dump for problem diagnosis and for your IBMSupport Center personnel.

Abend Code FormatThe format of an abend code is mmm###, where:

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

### Is the code number. If the abend is issued from CP module PRG, this valueis the program exception number.

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

System Codes


Abend Codes A - M

AAK001

Explanation: (soft) The activation block lock has beendestroyed. The lock word should never be destroyedwhen the activation block is found. The transaction isdiscarded.

User response: See z/VM: Diagnosis Guide forinformation on gathering the documentation you needto assist IBM in diagnosing the problem; then contactyour IBM Support Center personnel.

AAL001

Explanation: (soft) The activation block lock has beendestroyed. The transaction is discarded and a close issent to the partner. The lock word should never bedestroyed when the activation block is found.


AAS001

Explanation: (soft) A nonzero condition code wasreturned on an IUCV SEVER in the ISFC APPCmailbox. The IUCV SEVER should always completewith condition code zero. Conversation clean up willcontinue.


AAS002

Explanation: (soft) A condition code of zero wasreturned on an APPCVM RECEIVE in the ISFC APPCmailbox.

At this point in the APPC mailbox processing, aMessage Pending Interrupt has been received. Acondition code of zero (indicating receive-ahead)should never occur. Processing continues as if an erroroccurred on the APPCVM RECEIVE (condition code 1).


AAT002

Explanation: (soft) During open_complete processingin the ISFC APPC mailbox, the target side of the APPCconversation is expecting PIP data on the connect, but

the source side never indicated that it was sending PIPdata.

This is most likely a timing problem. The APPCconversation is severed.


AAU001

Explanation: (soft) A non-zero condition code wasreceived on an IUCV SEVER of the *IDENT path for anISFC owned gateway in the ISFC APPC mailbox. TheIUCV SEVER should always complete with conditioncode zero. The cleanup of the gateway path willcontinue.


ABC001

Explanation: (soft) HCPABC received an unexpectedreturn code when scanning for or opening a soft abenddump file.

User response: If message HCPABC9309E precededthis abend, the return code from an attempt to open asoft abend dump file is in R3. Otherwise, the returncode is from a scanning operation and is in R15.Determine what the return code is and see z/VM:Diagnosis Guide for information on gathering theadditional documentation you need to assist IBM indiagnosing the problem; then contact your IBMSupport Center personnel.

ABF001

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


ABF002

Explanation: An unexpected return code was receivedwhen reading, writing, or positioning the system dumpspool file.


AAK001 • ABF002

Chapter 2. System Codes 11

ABF003

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


ABN001

Explanation: An incorrect PSW address was calculatedas the return address in the abending module when anasynchronous dump was requested.


ABN002

Explanation: Not enough storage was available toprovide the necessary amount of static save areas forthe soft abend process.


ABR001

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


ABR002

Explanation: (soft) CP detected an unsupported returncode being returned from an exit routine.

User response: Check the trace table to determinewhich exit and entry point was called. Review the codeassociated with this entry point to determine the reasonfor returning an unsupported return code and correctthe error. This is an error in customer or vendor writtencode; contact the author for additional assistance.

ACP002

Explanation: (soft) Issued when two or morejournaling messages for the same failed DirectoryBroadcast request are received by an ISFC node withenhanced broadcast routing capabilities.

The directory broadcast completes normally, but no

journaling messages are sent to any nodes thatresponded with 'invalid password' on a faileduserid/password directory broadcast. There is aprogramming error either in ISFC directory broadcastcode, or in APPC delayed-connect processing.


ACR100

Explanation: (soft) An attempt to acquire the SystemResource Table lock (LKWRD defined in SSCSRTLK)failed because it had been destroyed. This indicates aprogramming error.


ACS001

Explanation: (soft) The ISFC directory broadcastroutine was called with an incorrect value in the fieldcontaining the number of requests (DBHNREQS). Thevalue was either zero or negative.

The directory broadcast does not complete. There is aprogramming error either in the ISFC directorybroadcast code or in APPC delayed-connect processing.


ACV100

Explanation: (soft) An attempt to acquire the SystemResource Table lock (LKWRD defined in SSCSRTLK)failed because it had been destroyed. This indicates aprogramming error.


AFF001

Explanation: Issued by the HCPAFF module. Thismodule is distributed as object code only; therefore, nosource program materials are available.

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

You cannot directly circumvent this problem.

ABF003 • AFF001



AFF002


This module supports the processor affinity function,where an error has occurred attempting to find aprocessor that can satisfy a user's feature requirements.



AFF004


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



AFF005


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



AFR001

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

v The block is not contained in an absolute aligned freestorage frame.

v The address of the block is not properly aligned.

v The block already resides on an absolute aligned freestorage available block list.


AFR002

Explanation: Absolute aligned free storage internalchain damage occurred (detected on block release only)because of one of these reasons:

v The size of the block in the FRMTE has beendestroyed.

v The FRMTE representing storage is not on theSUBBK list, but it should be.


AFR003

Explanation: An invalid size was specified for anabsolute aligned free storage block.


AFS001

Explanation: The address passed to the aligned freestorage manager (detected on block release only) wasnot valid because of one of these reasons:

v The block is not contained in an aligned free storageframe.

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 chaindamage occurred (detected on block release only)because of one of these reasons:

v The size of the block in the SXSTE has beendestroyed.

v The SXSTE representing storage is not on the SUBBKlist, but it should be.

User response: See z/VM: Diagnosis Guide forinformation on gathering the documentation you need

AFF002 • AFS002


to assist IBM in diagnosing the problem; then contactyour IBM Support Center personnel.

AFS003

Explanation: An invalid size was specified for a hostlogical aligned free storage block.


ALC001

Explanation: (soft) The module that issues this abendis distributed as object code only; therefore, no sourceprogram materials are available.


ALC002

Explanation: The module that issues this abend isdistributed as object code only; therefore, no sourceprogram materials are available.


ALC003



ALC004



ALC005



ALD003

Explanation: An attempt was made to decrement acount of resident pages for a VMDBK or ASCBK, butthe count was already negative or would go negative.


ALD004

Explanation: A non-pageable FRMTE was found on aframe-owned list (UFO, VUFO, or SUFO).


ALD005

Explanation: During the demand scan phase ofavailable list replenishment, a required address ingeneral register 9 did not point a Frame Table Entry(FRMTE).


ALD007

Explanation: An attempt was made to decrement acount of invalid-but-resident pages for a VMDBK, butthe count was already negative or would go negative.


ALD008

Explanation: VMDBK global cyclic lock not heldshared as expected.


AFS003 • ALD008


ALE001

Explanation: (soft) Issued by the HCPALE module.This module is distributed as object code only;therefore, no source program materials are available.


ALE002

Explanation: (soft) Issued by the HCPALE module.This module is distributed as object code only;therefore, no source program materials are available.


ALF002

Explanation: An attempt was made to reclaim a realstorage frame currently containing a pageable page, butthe required serialization (the owning virtualconfiguration's base VMDBK VMDPTIL Page TableInvalidation Lock) is not held shared or exclusive.


ALF003

Explanation: An attempt was made to discard backingstorage for a guest page declared as unused, volatile, orpotentially volatile and unchanged, but HCPHPCCRreported the page unexpectedly resident.


ALF010

Explanation: While adding a frame to the availablelist or taking a frame from the available list, CPdetermined that the frames on the list were chainedimproperly. It may also be that the count of availableframes became negative.

User response: Inspect the process of chaining andunchaining frames on the available list. Examine thedump for previous manipulations of the available listto see when and where the damage occurred. Examinethe code for the module that caused the damage. R14points to the address in HCPALF where CP detectedthe abend.

ALF013

Explanation: The available list replenishment functionwas attempting to decrease the count of resident pagesfor an address space (ASCCTPRS), but the count wasalready negative.

User response: Inspect the process of increasing anddecreasing the count of resident pages (ASCCTPRS).Examine the dump and determine the ASCBK orSNTBK for which this count is being decreased. Anegative count indicates an invalid list. This countincreases when a frame is added to the list anddecreases when a frame is taken from the list. Inspectthe validity of the list. R14 points to the address inHCPALF where CP detected the abend.

ALF014

Explanation: One of the following invalid page stateswas detected:

v Logically-zero with a valid PTE.v Logically-zero, with an invalid PTE, and not

invalid-but-resident (IBR).


ALG001

Explanation: Incorrect input parameters wereprovided to a routine called during the demand scanphase of available list replenishment.


ALG003

Explanation: An attempt was made to decrement acount of resident pages for a VMDBK or ASCBK, butthe count was already negative or would go negative.


ALL001

Explanation: (soft) CP could not delete the VMDBKblock from the VMDBK hash table for a user whoissued the LOGOFF command. The hash key specifiedin VMDUSER does not exist in the VMDBK hash table.System execution will continue.


ALE001 • ALL001



ALL002

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

User response: Examine the storage dump. You canuse the abend address to determine whether the failureoccurred in an HCPALLVM call or an HCPALLLR call.The address of the VMDBK being examined is in R1 forHCPALLVM or R10 for HCPALLLR. Look at the systemtrace table for the sequence of events that led to thissituation.

ALL015

Explanation: A user was completing the LOGOFFprocess and was no longer eligible to execute work onthe system. VMDCTCRT, the count of "criticalprocesses" in progress, was still a positive value. Thisindicates that some CP code has incremented thecounter (generally when the user becomes a defer-lockowner) without ever decrementing it appropriately.

User response: Use the CP trace table to attempt tolocate code that incremented VMDCTCRT withoutdecrementing it appropriately. After attempting tolocate the failing code, see z/VM: Diagnosis Guide forinformation on gathering the documentation you needto assist IBM in diagnosing the problem; then contactyour IBM Support Center personnel.

ALL020

Explanation: Subroutine RELCYCLH was called torelease the cyclic list hold lock for a particular VMDBKwhen that lock was not held.

User response: Normally, RELCYCLH is calledfollowing GETCYCLH when dequeuing a VMDBKfrom the global or a local cyclic list. Examine theregisters to determine the caller of RELCYCLH, and theVMDBKs involved. R10 points to the VMDBK beingdetached. R1 points to the corresponding originVMDBK, which contains the cyclic list lockword,VMDCYCLH.

ALM001



ALM002

Explanation: (soft) Parameters were passed in R2 toan entry point in HCPALM that does not acceptparameters. The parameter register must be zeros toallow for possible future enhancements to the module.

User response: Using the trace table, determine thecaller of the HCPALM entry point, and why a nonzeroparameter was passed.

AMD001

Explanation: (soft) Indicates an incorrect number ofextents were passed to HCPMSM.


AMD002

Explanation: (soft) Indicates an insufficient number ofDX2BKs were passed to HCPMSM.


APJ001

Explanation: This module is distributed as object codeonly; therefore, no source program materials areavailable.


APU001

Explanation: (soft) This module is distributed as objectcode only; therefore, no source program materials areavailable.


ARD001

Explanation: Issued by the HCPARD module. Thismodule is distributed as object code only; therefore, nosource program materials are available.


ALL002 • ARD001


ARD002

Explanation: Issued by the HCPARD module. Thismodule is distributed as object code only, therefore nosource program materials are available.


ARD003



ARD004



ARD005



ARD006



ARD007




ARD008



ARD009



ARD010



ARD011

Explanation: An attempt was made to either read orwrite an architecture description block on the PersistentData Record (PDR) during system initialization. Theoperation failed for some reason. This means there is aproblem with the SSI cluster's PDR. It is likely one ofthe following problems:

v The SYSTEM CONFIG file statement is pointing tothe wrong PDR volume.

v The PDR volume is not accessible in R/W mode.v The PDR has not been properly created using the

appropriate FORMSSI utility.

v There is a problem with the DASD device.v The PDR lock could not be acquired after repeated

attempts.

User response: Check for each of the above problems.First verify that your SSI statement in SYSTEMCONFIG is correct and that your system has R/Waccess to the volume. Check for possible I/O errors tothat volume. Use the dump to determine if the PDRlock is held and by which SSI member.

ARD002 • ARD011


ARD012



ARR001

Explanation: (soft) An unrecoverable error occurredduring DIAGNOSE code X'254' processing. R14 in thesystem dump contains the address of where the erroroccurred in module HCPARR.


ARS001

Explanation: (soft) An unrecoverable error occurredduring DIAGNOSE code X'254' processing. R14 in thesystem dump contains the address of where the erroroccurred in module HCPARS.


ASD001

Explanation: (soft) A newly created ASIT was foundto not be valid.


ASI002

Explanation: (soft) Issued by the HCPASI module.This module is distributed as object code only;therefore, no source program materials are available.


ASM002

Explanation: (soft) Parameters were passed in R2 toan entry point in HCPASM that does not acceptparameters. The parameter register must be zeros toallow for possible future enhancements to the module.

User response: Using the trace table, determine thecaller of the HCPASM entry point, and why a non-zeroparameter was passed.

ASM012

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


ASN001



ASN002

Explanation: (soft) Parameters were passed in R2 toan entry point in HCPASN that does not acceptparameters. The parameter register must be zeros toallow for possible future enhancements to the module.

User response: Using the trace table, determine thecaller of the HCPASN entry point, and why a non-zeroparameter was passed.

ASN012

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


ASR001

Explanation: (hard, soft) An untrue assertion has beenencountered. Assertions are made by modules using theHCPASERT macro. When a false assertion isdiscovered, an ASR001 abend results. Whether it is ahard abend or a soft abend depends on what theinvoker specified for the ABEND parameter of theHCPASERT macro. This abend does not indicate anerror in HCPASR, but rather an error in the code thatuses the HCPASERT macro. Note that this abend maybe issued in places other than HCPASR.

This abend may be issued when CPCHECKING is OFF.This abend can also mean that CP detected the wrong

ARD012 • ASR001


TMODE (Primary Mode or Access Register mode).

User response: R13 at the time of the abend containsthe address of a SAVBK which contains the contents ofthe invokers registers at the time of the failure. TheWRKPRGOP field in the savearea contains the programold PSW at the time of the monitor event. Theinstruction address in that PSW points just past theMonitor Call instruction in the failing HCPASERTmacro. The WRKGRPCT field in the savearea containsthe number of the failing assertion within the assertiongroup, or 1 if the assertion is not in a group. If theabend is hard, assertion checking will not be activatedduring recovery, to avoid a possible abend loop. It maybe reactivated with the SET CPCHECKING command.

ASR002

Explanation: (soft) An unrecognized assertion code isfound in the HCPASERT parameter list.

User response: This condition indicates a mismatchbetween the parameter list generated by theHCPASERT macro and the parameter-list parsing inHCPASR. Either the parameter list has becomecorrupted, or the HCPASERT invocation and HCPASRmodule are at different update levels. The WRKPRGOPfield in the savearea contains the program old PSW atthe time of the monitor event. The instruction addressin that PSW points just past the Monitor Callinstruction in the failing HCPASERT macro. TheWRKGRPCT field in the savearea contains the numberof the failing assertion within the assertion group, or 1if the assertion is not in a group.

ASR003

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

User response: Examine the HCPASERT invocationand correct the length on the source value. TheWRKPRGOP field in the savearea contains the programold PSW at the time of the monitor event. Theinstruction address in that PSW points just past theMonitor Call instruction in the failing HCPASERTmacro. The WRKGRPCT field in the savearea addressesby R13 contains the number of the failing assertionwithin the assertion group, or 1 if the assertion is not ina group.

ASR004

Explanation: Code invoked for a CODE assertion didnot return with R13 unchanged. R13 must be leftunchanged, because it contains the address of thesavearea used to remember information about the

invoker. This abend does not indicate an error inHCPASR, but rather an error in the code that uses theHCPASERT macro.

User response: Examine the HCPASERT invocationand correct the length on the source value. If it hasbeen overlaid since the original monitor event, theinstruction address in the program old PSW points justpast the Monitor Call instruction in the failingHCPASERT macro.

ASR005

Explanation: Code invoked for a CODE assertion itselfcaused another recursive CODE assertion to beinvoked. CODE assertion code may not issue CODEassertions or call code that makes CODE assertions.This abend does not indicate an error in HCPASR, butrather an error in code that uses the HCPASERT macro.

User response: Examine the HCPASERT invocationand correct it. CODE assertion code may not issueCODE assertions or call code that makes CODEassertions. The WRKPRGOP field in the save areacontains the program old PSW at the time of themonitor event. The instruction address in that PSWpoints just past the Monitor Call instruction in thefailing HCPASERT macro.

ASR007

Explanation: Code invoked for a CODE assertionapparently lost control because it returned on adifferent processor than the one from which it wascalled. This abend does not indicate an error inHCPASR, but rather an error in code that uses theHCPASERT macro.

User response: Examine the HCPASERT invocationand correct it. Code invoked for a CODE assertion maynot lose control. The WRKPRGOP field in the saveareacontains the program's old PSW at the time of themonitor event. The instruction address in that PSWpoints just past the “monitor call” instruction in thefailing HCPASERT macro.

ASR008

Explanation: An HCPASERT macro was incorrectlycoded. Assertions are not supported if the invoker is insecondary-space mode or running DAT-off.

User response: Examine the HCPASERT invocationand determine if it was issued appropriately. With thisinformation, see z/VM: Diagnosis Guide for informationon gathering the additional documentation you need toassist IBM in diagnosing the problem; then contactyour IBM Support Center personnel.

ASR002 • ASR008


ASY001

Explanation: (soft) A connection attempt to theAsynchronous CP Command Response (*ASYNCMD)system service has detected that the FOR control block(FORBK) is marked as an orphan on entry to theroutine that processes the connection attempt. Theconnection attempt is severed.


ASY002

Explanation: (soft) A connection attempt to theAsynchronous CP Command Response (*ASYNCMD)system service has received an error when attemptingto acquire the FOR control block (FORBK) lock,indicating the lock has been destroyed. The connectionattempt is severed.


ASY003

Explanation: (soft) A connection attempt to theAsynchronous CP Command Response (*ASYNCMD)system service has determined that the path identifierfor the connection attempt is already assigned and inuse. The connection attempt is severed.


ASY004

Explanation: (soft) An attempt to end a connection tothe Asynchronous CP Command Response(*ASYNCMD) system service has detected that theuser's FOR control block (FORBK) does not exist. Theconnection attempt is severed.


ASY005

Explanation: (soft) While processing the end of a FORcommand, specifying a PATH to the Asynchronous CPCommand Response (*ASYNCMD) system service, theFOR control block (FORBK) was expected to be markedas an orphan but was not.

User response: See z/VM: Diagnosis Guide for

information on gathering the documentation you needto assist IBM in diagnosing the problem; then contactyour IBM Support Center personnel.

ASY006

Explanation: (soft) While processing the end of a FORcommand, specifying a PATH to the Asynchronous CPCommand Response (*ASYNCMD) system service, anerror occurred while attempting to acquire the IUCVlock for the issuer of the FOR command. This abendindicates the lock has been destroyed.


ASY007

Explanation: (soft) While processing the end of a FORcommand, specifying a PATH to the Asynchronous CPCommand Response (*ASYNCMD) system service, anerror occurred while attempting to acquire the FORcontrol block (FORBK) lock for the issuer of the FORcommand. This abend indicates the lock has beendestroyed.


ASY008

Explanation: (soft) While processing the end of a FORcommand, specifying a PATH to the Asynchronous CPCommand Response (*ASYNCMD) system service, theentry in the connection table (FORTBL) could not befound for the path identifier being processed.


ATL001

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

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

ATL002

Explanation: HCPATLDV was entered on the systemVMDBK.

User response: R13 points to a save area. Identify thecaller by the return address and base register in the

ASY001 • ATL002


save area pointed to by R13. The caller did not providethe VMDBK of the currently dispatched user.

ATR001

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

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

ATR002

Explanation: HCPATRDV was erroneously enteredwhen the system VMDBK was the current VMDBK.

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

B9S001

Explanation: (soft) Certain instructions with anopcode of B9xx are simulated by CP when executedwith a function code of zero. This function codeindicates a query request that can be used to determinewhich other functions are available with the instruction.CP should only get control to simulate them if thefunction code is zero. This abend occurs if thesimulation code for one of these instructions is invokedwhen the requested function code is non-zero.

User response: Look at the SIEINST field in the SIEBKin R11 to determine which instruction simulation wasrequested. Register 0 contains the function code thatwas requested. Determine why the simulation code wasinvoked for this particular instruction when thefunction code is non-zero.

BID001

Explanation: (soft) An unexpected return code wasreturned to HCPBID (the main processing routine forDIAGNOSE code X'250'). The return code is in R15; theaddress of the routine that returned the code is in R14.

User response: Determine the return code and routineaddress, and see z/VM: Diagnosis Guide for informationon gathering the additional documentation you need toassist IBM in diagnosing the problem; then contactyour IBM Support Center personnel.

BID002

Explanation: (soft) The host-ART lookaside block(HALBK) is full and no more entries can be added.This condition was discovered while processing blockI/O entry-list block (BELBK) entries for DIAGNOSEcode X'250' and trying to add an entry to the HALBK.

R7 contains the address of the HALBK.


BIE001

Explanation: (soft) Issued by the HCPBIE module.This module is distributed as object code only;therefore, no source program materials are available.


BIM001

Explanation: (soft) What should be an impossiblesituation occurred while processing a Block I/O SENDRequest. The type of error is determined by the codestored in R1.

The following is a description of these codes:

R1 = 1 A SEND Request Block (SNDBK) is beingFRETed that is not on the SEND RequestQueue. The SEND Request may not have beenperformed.

R1 = 2 An invalid return code was found in a DVIOPBlock.

R1 = 3 An invalid or unexpected return code wasreceived from a called routine.

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

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

User response: Examine the internal trace table andstorage dump to determine which routine withinHCPBIM is detecting the error condition. R3 holds theaddress of the routine that caused the abend.

BIO001

Explanation: (soft) The DASD block I/O messagehandler or sever handler failed to locate the block I/Oconnect block associated with an IUCV SEND or anIUCV SEVER request. The request was made to adevice that is connected to the DASD block I/O systemservice.

User response: Verify the VDEVBIOA in the VDEVBKthat points to the block I/O block to ensure that thedevice is still connected to the DASD block I/O systemservice.

ATR001 • BIO001


BIR001

Explanation: (soft) An error occurred while processinga DIAGNOSE code X'250' request. The type of error canbe determined by the reason code stored in register 1.The codes are:

R1 = 1 An attempt was made to dequeue a BRQBKfrom the request chain, but the block was notfound.

R1 = 4 The count of active I/O operations for arequest (BRQDBICT) is about to go negative.Either too many interrupts have come in forthis request, or (more likely) someone isn'tincrementing or decrementing the countproperly.

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

R1 = 6 The VDISK I/O lock was found to bedestroyed while attempting to process anasynchronous request.

User response: Determine the reason code and seez/VM: Diagnosis Guide for information on gathering theadditional documentation you need to assist IBM indiagnosing the problem; then contact your IBMSupport Center personnel.

BIT001

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

User response: Examine the routine that calledHCPBIT and determine why R2 pointed where it did.

BIT002

Explanation: A module called HCPBITRL while theBITMPLCK lock was held. A call was made to HCPBITto release storage for the bit map, but the bit map lockwas still held.

User response: Examine the dump. Determine whythe lock was not previously relinquished.

BIT008

Explanation: The address of the frame is not pagealigned. The address of a frame that is being processedby HCPBITRL is not a 4K boundary. R2 contains theaddress of the frame.

User response: Examine the dump and trace backthrough the system execution to the point wheregeneration of the erroneous address occurred anddetermine the cause of the erroneous address. If you

are unable to resolve the problem, see z/VM: DiagnosisGuide for information on gathering the documentationyou need to assist IBM in diagnosing the problem; thencontact your IBM Support Center personnel.

BIU001

Explanation: An error occurred while processing aDIAGNOSE code X'250' request. The type of error canbe determined by the reason code stored in register 1.The codes are:

R1 = 2 A return code that was not valid was found ina DVIOP. The return code is in register 14.

R1 = 3 An unexpected return code, or one that wasnot valid, was received from the routine calledto build channel programs. The return code isin register 15.

User response: Determine the return code and seez/VM: Diagnosis Guide for information on gathering theadditional documentation you need to assist IBM indiagnosing the problem; then contact your IBMSupport Center personnel.

BIU002

Explanation: The TCHBK lock was found to be in aninvalid state during minidisk cache back-endprocessing.


BIU003

Explanation: While doing back-end processing forminidisk cache, the count of blocks processed wentnegative.


BMS001

Explanation: HCPBMS is trying to obtain a spinlockthat was already obtained, but never released byHCPBMS.

User response: R1 addresses the spinlock. The secondfullword of the spinlock contains the address of thecode that last obtained the spinlock. If the spinlock waslast obtained by HCPBMSTM, then HCPBMSTM hasbeen called to terminate the BMSBK, and another entrypoint in HCPBMS was called with the address of aterminated BMSBK. In this case, the error is outsideHCPBMS. Otherwise, one of the entry points in

BIR001 • BMS001


HCPBMS may be obtaining the BMSLOCK withoutreleasing it.

BSC002

Explanation: (soft) Invalid parameters were passed toHCPBSCAA, HCPBSCAK, or HCPBSCSL.

For HCPBSCSL:

R1 contains the address of the SNTBK for which anSTLBK is to be built. The address range that specifiesthe segments to be built is located at SNTRANGE inthe SNTBK. Either no range was specified, or the flagbytes for ranges in the same segment indicate differentshared/exclusive modes.

For HCPBSCAA and HCPBSCAK:

R0 and R1 contain the supplied address range. Eachmust refer to a page within the STLBK pointed to inR2. R3 contains the address of a list of input ASAs orKEYs and must not be zero.

User response: R1 contains the pointer to an SNTBKthat contains a list of page address start-end pairs (seeHCPBSCSL prologue or HCPSNTBK for the format anduse of these range pairs). Determine why the ranges orflags are considered invalid. Examine the logic thatbuilds the ranges and flags in the SNTBK to determinehow the invalid data was placed in the SNTBK.

If R14 indicates the abend was from HCPBSCSL,examine the contents of R1. R1 contains a pointer to alist of page address start-end pairs on a fullwordboundary.

Each pair is of the form SSSSS0GG EEEEE000 where:

SSSSS is the start page address

EEEEE is the end page address

GG is a flag byte

For each pair: 0 Segments are exclusive.

Bit 6: x'02'0 = > PTEs a