z/VM V6.4 Other Components Messages and Codes · xxx The 3-character pr efix indicates which z/VM component, facility , or featur e, or which other pr oduct, contains the module that

z/VM

Other Components Messages and CodesVersion 6 Release 4

GC24-6207-05

IBM

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

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-6207-04.

© Copyright IBM Corporation 1991, 2017.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 Other Components Messages and Codes . . . . . . . xiGC24-6207-05, z/VM Version 6 Release 4 (December 2017) . . . . . . . . . . . . . . . . . . . . xiGC24-6207-04, z/VM Version 6 Release 4 (August 2017). . . . . . . . . . . . . . . . . . . . . xiGC24-6207-03, z/VM Version 6 Release 4 . . . . . . . . . . . . . . . . . . . . . . . . . xiGC24-6207-02, z/VM Version 6 Release 3 . . . . . . . . . . . . . . . . . . . . . . . . . xi

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

z/VM XEDIT Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Messages with 4nxx Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Messages From Other Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Unnumbered 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9AVS Abend Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10GCS Abend Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Overview of Problem Determination Facilities . . . . . . . . . . . . . . . . . . . . . . . 11Abend Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

TSAF Abend Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Return Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 3. System Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 35AVS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36DVF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56GCS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89TSAF Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134VMSES/E Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

VMF002E - VMF1490E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149VMF1507E - VMF3064I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175ITN2000E - ITN2050E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265Programming Interface Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 267Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267Terms and Conditions for Product Documentation . . . . . . . . . . . . . . . . . . . . . . 267IBM Online Privacy Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

© Copyright IBM Corp. 1991, 2017 iii

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Bibliography. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271Where to Get z/VM Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271z/VM Base Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271z/VM Facilities and Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272Prerequisite Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

iv z/VM V6.4 Other Components Messages and Codes

Tables

1. z/VM Message Prefixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22. Message Prefixes for Other Products . . . . . . . . . . . . . . . . . . . . . . . . . 33. Displaying Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64. Execs and their associated modules . . . . . . . . . . . . . . . . . . . . . . . . . 56

© Copyright IBM Corp. 1991, 2017 v

vi z/VM V6.4 Other Components Messages and Codes

About This Document

This document contains reference information that is intended to help youunderstand the APPC/VM VTAM® Support (AVS), Dump Viewing Facility (DVF),Group Control System (GCS), Transparent Services Access Facility (TSAF), andVirtual Machine Service Enhancements Staged/Extended (VMSES/E) messages andcodes produced by version 6 release 4 IBM® z/VM®, and recommends actions youcan 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 AVS, DVF,GCS, TSAF and VMSES/E messages and codes. A general knowledge of z/VMcommands is useful for implementing recommended responses.

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

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, 2017 vii

viii z/VM V6.4 Other Components 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 Other Components Messages and CodesGC24-6207-05

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 Service Resources (www.ibm.com/vm/service/).v Go to IBM Support Portal (www.ibm.com/support/entry/portal/Overview/).

© Copyright IBM Corp. 1991, 2017 ix

http://www.ibm.com/systems/z/os/zvm/zvmforms/webqs.html

http://www.ibm.com/vm/service/

http://www.ibm.com/support/entry/portal/Overview/

x z/VM V6.4 Other Components Messages and Codes

Summary of Changes for z/VM Other Components Messagesand Codes

This document contains terminology, maintenance, and editorial changes. Technicalchanges are indicated by a vertical line to the left of the change. Some productchanges might be provided through service and might be available for some priorreleases.

GC24-6207-05, 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 following message has been added:v “VMF1242I” on page 167

The following message has been updated:v “VMF1216E” on page 163

GC24-6207-04, 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 following message has been updated:v “VMF2205I” on page 210

GC24-6207-03, 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 Determine installed service

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

© Copyright IBM Corp. 1991, 2017 xi

xii z/VM V6.4 Other Components 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 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 3.

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, 2017 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 DefinitionMessages

CEE Language Environment® z/OS: Language Environment Run-Time Messages

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 Run-Time Messages

EEQ HCM (Hardware ConfigurationManager)

z/OS and z/VM: Hardware Configuration Manager User'sGuide

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

IBM Language Environment z/OS: Language Environment Run-Time Messages

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

IGC Language Environment z/OS: Language Environment Run-Time Messages

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


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

Introduction

2 z/VM V6.4 Other Components Messages and Codes

Table 1. z/VM Message Prefixes (continued)

Prefix z/VM Component, Facility, orFeature

Where the Messages Are Documented

IOA OSA/SF (Open Systems AdapterSupport Facility)

Open Systems Adapter-Express Customer's Guide andReference

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.

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®)

Introduction

Chapter 1. Introduction 3

Table 2. Message Prefixes for Other Products (continued)

Prefix Product Name

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)

EDD DisplayWrite

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)

Introduction


Table 2. Message Prefixes for Other Products (continued)

Prefix Product Name

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

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 Reference

v 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

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.

Introduction


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:xxxmmm####s text

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

Introduction


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 z/VM V6.3 Information Center(publib.boulder.ibm.com/infocenter/zvm/v6r3/) and use the search capability tosearch 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


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 the user may 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, refer to the z/VM publication 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.


AVS Abend CodesWhen an AVS abend occurs, the following actions are required:v Collect information about the error.

– Print the console log for the time that the error occurred. Save the consolesheet or spooled console output from the AVS virtual machine.

– Save and process any dumps that AVS produces.– Enter the MAP command to convert the GCS load map to a format that

allows the Dump Viewing Facility to append the GCS load map to the dump.– Enter the CP DUMPLOAD command to load the dump from a reader spool

file into a CMS dump file.– Enter the DUMPSCAN command with the necessary subcommands to look at

the contents of the dump.– Save any TRSOURCE file that may contain AVS data.

v Collect system status information. The following information can help betterdetermine problems:– The system load at the time of failure on any systems using AVS and the

status of each system (for example, did another system abend?).– The types of applications that are using AVS at the time and any information

about them.– The physical connection configuration of the systems in use.

v Recover from the abend to continue processing.– When an abend occurs in AVS, either because AVS issued an ABEND or

because an AVS or GCS operation caused a program exception, AVS producesa dump via the CP VMDUMP command, and uses DIAGNOSE X'94' to dothe dump. More information about the CP VMDUMP command is describedin the z/VM: CP Commands and Utilities Reference. A more detailed explanationon AVS problem determination and DIAGNOSE X'94' can be found in thez/VM: Diagnosis Guide.

80C

Explanation: Ran out of AVS stack storage. There wasno more storage available for the AVS stack manager.

System action: AVS processing is terminated. A dumpis produced.

User response: Increase the size of the virtual machinein which AVS resides.

80C


GCS Abend Codes▌PI▐

If an abend occurs in a GCS application program:1. The GCS supervisor will clean up the GCS system resources that the failed

application was using. In addition, the application can specify exit routines todo further cleaning up and to try to resume processing.

2. If the application has no exit routines that try to restart it, the operator mustmanually restart it. If the GCS system itself has failed, the operator must re-IPLthe system.

3. If the application includes the ERRET parameter on the LOAD macro, theapplication branches to the specified address instead of abending.

GCS provides several aids for diagnosing and correcting the problem that causedthe abend.

For some problems, you might find that the following list of GCS abend codes willprovide all the information you need.

For more difficult problems, GCS provides trace and dump facilities, interactivedump analysis using the DVF and interactive debugging under CP.

For more information, see:v “Overview of Problem Determination Facilities”v “Abend Codes” on page 13

Overview of Problem Determination FacilitiesGCS supports both internal and external tracing for error analysis. Internally, theGCS trace table automatically records GCS supervisor activity. With the ITRACEcommand and GTRACE macro, you can record other activity in particular GCSvirtual machines or in the GCS group as a whole. External tracing, usingTRSOURCE and GCS ETRACE commands, records activity in a spool file. This filecan then be formatted for viewing using the DVF.

If a GCS application program fails, GCS will automatically produce a dump when:v The GCS supervisor terminated the program by issuing the ABEND macro.v The failing application program issued ABEND with the DUMP operand.v The exit routine specified in an ESTAE, TASKEXIT, or MACHEXIT macro

requested a dump.

The dump will be sent to the designated dump receiver, if there is one, or to thereader of the virtual machine in which the application failed. You can manuallyrequest a dump of GCS storage by issuing the GDUMP command from the GCSconsole.

Your installation may want to set up application programs to produce dumpsautomatically if they abend. Dumps produced during abend processing maycapture more information about an error than dumps produced with GDUMP orVMDUMP, after abend processing has been completed.

If a severe error occurs and the GCS supervisor abends, the GCS machinetermination module will try to take a dump of GCS storage. If the machine

System Codes

Chapter 2. System Codes 11

termination module is unable to get the dump, you can use the CP VMDUMPcommand to get it. The CP command SYSTEM RESTART will also produce adump of GCS storage.

Once storage has been dumped, you can interactively analyze the dump using theDVF.

If you are authorized to do so, you can also use CP debugging commands such asBEGIN, DISPLAY, DUMP, TRACE, and STORE to trace GCS execution interactively.

System Codes


Abend CodesThe following is a list of the GCS abend codes, the modules that issue them, anexplanation of the abend, and responses the user should take to recover andcontinue.

▌PI end▐

001

Explanation: An input/output error occurred duringBSAM or QSAM processing.

User response: Error message GCT306S (input errors)or GCT307S (output errors) will have preceded thisabend message. Look up the error code from the errormessage under message 306 or 307 in the GCS messagereference. Use the error code tables for 'SER' or 'SCT'messages, and respond accordingly.

Module: GCTSCT

005

Explanation: An error occurred during GET, PUT,READ, or WRITE macro processing. A required addresswas not specified or was not valid. The requiredaddress may have been the DCB address, theDCBRECAD address, the DCBEOBAD address or thearea address.

User response: Correct the invalid address

Module: GCTSQS, GCTSBS

00A

Explanation: An error occurred during CHECK,NOTE, or POINT macro processing. A required addresswas missing or was invalid. The required address mayhave been the DCB address or the DECB address.

User response: Correct the invalid address.

Module: GCTSCT

010

Explanation: An error occurred during READ macroprocessing because the SB option was specified. Thisoption is not supported by GCS.

User response: Remove the 'SB' option.

Module: GCTSBS

013

Explanation: An error occurred during the executionof an OPEN macro instruction.

User response: Error message GCT308E or GCT348E(OPEN errors) will have preceded this abend. Pleasesee the 'User Response' sections for those messages andrespond as indicated.

Module: GCTSOP

014

Explanation: An error occurred during execution of aCLOSE macro instruction.

User response: Error message GCT309E or GCT349E(CLOSE errors) will have preceded this abend message.Please see the 'User Response' sections for thosemessages and respond as indicated.

Module: GCTSCL

035

Explanation: An error was detected by VSE/VSAMfor which there is no equivalent OS/VS VSAM errorcode.

User response: A GCS error message will havepreceded this abend message. Please see the 'UserResponse' section for the error message that appearedand respond as indicated.

Module: GCTVIP

036

Explanation: An error was detected while trying toaccess the VSAM, BAM, or VTAM shared systems.


Module: GCTVIB, GCTVSI

037

Explanation: A disk defined for use with a VSAMprogram could not be used. The disk was in the wrongformat, was not accessed, or was not attached.

User response: A GCS error message precedes thisabend message; see the 'User Response' section for theerror message that appeared and respond as indicated.

Module: GCTDAS, GCTDOS, GCTVIP

038

Explanation: An I/O error occurred on a disk beingused for VSAM processing.

User response: A GCS error message will have

001 • 038


preceded this abend message. Please see the 'UserResponse' section for the error message that appearedand respond as indicated.

Module: GCTDOS

039

Explanation: An internal error occurred during VSAMprocessing.


Module: GCTVIP, GCTDAS, GCTDOS, GCTLDF

03A

Explanation: The number of exits defined for use withVSAM exceeded the limit of 128 exits.


Module: GCTVIP

03B

Explanation: An invalid address was detected in aVSAM control block or VSAM parameter list. Theaddress is not located in storage that the currentprogram has access to.


Module: GCTVIP, GCTVIR

03B

Explanation: A TYPE parameter of CHK or DRBA wasspecified and those parameters are not supported.


Module: GCTVIP

0Cn

Explanation: A program check has occurred. The 'n' inthe Abend Code column for this entry stands for thenumber of the program check that has occurred. 'n'should be one of the following in your message:

Code Meaning

0 A program check other than 1-F has occurred.

1 Operation

2 Privileged operation

3 Execute

4 Protection

5 Addressing

6 Specification

7 Data

8 Fixed-point overflow

9 Fixed-point division

A Decimal overflow

B Decimal divide

C Exponent overflow

D Exponent underflow

E Significance

F Floating-point divide

User response: Examine the Program Old PSW atlocation 40 (x'28') to find out the cause of the programcheck.

Module: GCTITP

0F3

Explanation: An SVC 202 or 203 routine indicated thatan error occurred in processing the SVC, but noprovision has been made for an error return from theroutine processing the SVC.

User response: Find out why the error occurred, orindicate that an error return is desired. To allow for anerror return, provide an error address for the SVC 202,or negate the halfword code for the SVC 203 andreissue the command.

Module: GCTITS

0F8

Explanation: A task has issued an SVC 202, butregister 1 was pointing to non-addressable storage.

User response: Find out why the contents of register 1were not valid, and correct the problem.

Module: GCTITS

Severity: 12

0F8

Explanation: A branch entered to GCS enabled forinterrupts.

User response: Disable for interrupts before branchingto GCS.

039 • 0F8


Module: GCTEST GCTFSV GCTGIM GCTGSVGCTIUS GCTPOS GCTSDX GCTWAI

Severity: 12

0F8

Explanation: A user exit returned to GCS in accessregister mode.

User response: Get out of access register mode beforereturning to GCS.

Module: GCTDSP GCTPMC

Severity: 14

0F8

Explanation: GCS was branch entered in accessregister mode.

User response: Get out of access register mode beforebranch entering GCS.

Module: GCTEST GCTFSV GCTGIM GCTGSVGCTIUS GCTSDX GCTPOS GCTWAI

Severity: 16

0F8

Explanation: An SVC was entered in access registermode.

User response: Get out of access register mode beforeentering an SVC again.

Module: GCTITS

Severity: 18

0FA

Explanation: GCS could not process an SVC issued bya user program that was running in problem state. Thefailure occurred because the DOS bit-- a flag controlledby the GCS supervisor--was on when the SVC wasissued. This bit must always be off when a problemstate program issues an SVC.

User response: Find out why the DOS bit was on andcorrect the problem. The DOS bit may have beenturned on by mistake by an authorized GCS program,or the GCS supervisor may have malfunctioned.

Module: GCTITS

101

Explanation: Invalid parameter list for the WAITmacro. WAIT was issued with other than 0 or 1 enteredas the number of events to be completed before thewaiting task can proceed.

User response: Correct the WAIT macro parameter

specifying the number of events. That parameter mustbe either 0 or 1.

Module: GCTWAI

102

Explanation: A POST macro has been issued with aninvalid ECB address. The user is not authorized toaccess the storage specified by the ECB address.

User response: Check to see that the ECB address iscorrect. If you are posting an ECB that is part of anECBLIST, check that the task that issued the WAIT isstill authorized over its storage area. The ECBLISTaddresses may have been overwritten.

Module: GCTWAI

106

Explanation: An unrecoverable error occurred whilereading the file from the disk. The supervisor wasunable to fetch the program requested in a LINK,LOAD, or XCTL macro into virtual storage because thegiven file was not found.

This abend can result when a user program issues aLINK, LOAD, or XCTL macro directly or when anATTACH macro or an OSRUN or LOADCMDcommand is issued, because they call the LINK orLOAD macro.

User response: Check to be sure you have the diskaccessed properly (for example, the disk should not beaccessed as shared read/write). Rerun the job. If theproblem persists call your system support personnel.

Module: GCTLOS GCTPMC GCTPML

Severity: 010B

106

Explanation: An unrecoverable error occurred whilereading the file from the disk. The supervisor wasunable to fetch the program requested in a LINK,LOAD, or XCTL macro into virtual storage because thebuffer area was not within the user storage limits.




Severity: 020B

0F8 • 106


106

Explanation: An unrecoverable error occurred whilereading the file from the disk. The supervisor wasunable to fetch the program requested in a LINK,LOAD, or XCTL macro into virtual storage because of apermanent disk error from RDTK.




Severity: 030B

106

Explanation: An unrecoverable error occurred whilereading the file from the disk. The supervisor wasunable to fetch the program requested in a LINK,LOAD, or XCTL macro into virtual storage because thenumber of items was equal to 0.




Severity: 050B

106

Explanation: An unrecoverable error occurred whilereading the file from the disk. The supervisor wasunable to fetch the program requested in a LINK,LOAD, or XCTL macro into virtual storage because thefixed/variable flag in the first entry is not F or V.




Severity: 070B

106

Explanation: An unrecoverable error occurred whilereading the file from the disk. The supervisor wasunable to fetch the program requested in a LINK,LOAD, or XCTL macro into virtual storage because thegiven storage area was smaller than the size of the itemto be read. The number of bytes corresponding to thesize of the buffer have been read.




Severity: 080B

106

Explanation: An unrecoverable error occurred whilereading the file from the disk. The supervisor wasunable to fetch the program requested in a LINK,LOAD, or XCTL macro into virtual storage because thenumber of items was greater than 1 for a variablelength file.




Severity: 0B0B

106

Explanation: An unrecoverable error occurred whilereading the file from the disk. The supervisor wasunable to fetch the program requested in a LINK,LOAD, or XCTL macro into virtual storage because thenumber of items specified exceeds the number of itemsin the file.


106




Severity: 0C0B

106

Explanation: An unrecoverable error occurred whilereading the file from the disk. The supervisor wasunable to fetch the program requested in a LINK,LOAD, or XCTL macro into virtual storage because avariable field has an invalid displacement in the activefile table. This is a coding error.




Severity: 0D0B

106

Explanation: An unrecoverable error occurred whilereading the file from the disk. The supervisor wasunable to fetch the program requested in a LINK,LOAD, or XCTL macro into virtual storage becauseinsufficient free storage is available for file managementcontrol areas.




Severity: 190B

106

Explanation: An unrecoverable error occurred whilereading the file from the disk. The supervisor wasunable to fetch the program requested in a LINK,LOAD, or XCTL macro into virtual storage because anegative number or the item number plus number ofitems too large.




Severity: 1A0B

106

Explanation: The supervisor was unable to fetch theprogram requested in a LINK, LOAD, or XCTL macrointo virtual storage because sufficient storage was notavailable.


User response: Use a larger virtual storage size, deleteunneeded modules, or take other steps to make moreefficient use of storage.


Severity: 000C

112

Explanation: Invalid input was passed to a BLDLmacro. The problem may have been that (1) the start orend of the BLDL list referred to an address that was ina different key than that of the calling program; or (2)the number of entries was less than 1; or (3) the lengthof a list entry was less than 58 bytes.

User response: Check that the parameter list is notbeing incorrectly modified. Make sure that the startingaddress, number of entries, and length-of-entry fieldsare correct.

Module: GCTPMB

12C

Explanation: The task ID that has been passed to aCHAP macro is invalid for one of the followingreasons:

v The task ID is associated with a system task insteadof a user task. That is, the task id was 1 or 2.

v The task ID does not exist.

v The task identified by the task ID is not animmediate descendant of the task that issued theCHAP. A task must have ATTACHed a sub-task inorder to issue a CHAP for the sub-task.

106 • 12C


v The task identified by the task ID has alreadyterminated.

User response: Correct the faulty CHAP parameter.Make sure that the task ID address is a fullword withthe task ID in the two low-order bytes. Make sure thatthe task ID matches the task ID that was returnedwhen the ATTACH macro was issued for this sub-task.

Module: GCTATT

12F

Explanation: The time interval address passed to theSTIMER macro is invalid for one of the followingreasons:

v The storage key for the time interval address differsfrom that of the task that issued the STIMER macro,and the address is located in fetch-protected storage.

v The time interval passed in the DINTVL or TODparameter was not in unpacked decimal format.

User response: Correct the time interval addresses.

Module: GCTTIM

130

Explanation: The resource to be released by a DEQmacro was not previously obtained by an ENQ fromthe same task, and the RET=HAVE operand was notcoded in the call to DEQ.

User response: Issue ENQ to obtain the resourcebefore issuing DEQ, or include the RET=HAVEoperand as a DEQ parameter.

Module: GCTENQ

138

Explanation: Two ENQ macros were issued in thesame task for the same resource without a DEQ macrocall in between. The second ENQ did not specify TEST,USE, CHNG, or HAVE in the RET operand.

User response: Check to see if you intended to useanother resource name for the second ENQ. If not, youcan (1) issue a DEQ to release the resource after thefirst ENQ; or (2) specify TEST, USE, CHNG, or HAVEin the RET operand in the second ENQ macro.

Module: GCTENQ

13C

Explanation: An invalid parameter list was specifiedon an ESTAE macro by a problem state program. Thestorage key for the parameter list differed from thestorage key for the problem state program.

User response: Check to see if the correct parameterlist was passed to ESTAE.

Module: GCTABD

13E

Explanation: A DETACH has been issued for asub-task that has not yet terminated. The sub-task hasabnormally terminated with this code. The sub-task'sETXR (exit routine) was not executed.

User response: Be sure that the subtask completesexecution before a DETACH is issued. To synchronizethe DETACH with task completion, you can use theECB or ETXR parameter on the ATTACH macro. ThisECB is posted or the ETXR exit runs when the sub-taskterminates.

Module: GCTATT

144

Explanation: An error occurred during execution ofthe SYNADAF macro. An invalid access method codewas specified in the high order byte of register 15.

User response: Make sure that the ACSMETHparameter on the SYNADAF macro is correctly coded,or that the high order byte of register 15 contains avalid access method code, before SVC 68 SYNADAF isissued.

Module: GCTSER

1CB

Explanation: An unauthorized caller issued an SVC203. Either a system-only SVC 203 was requested, or aprogram running in problem state tried to issue theSVC 203. An SVC 203 can only be issued by a programrunning in supervisor state.

User response: If a system-only SVC was attempted,find out what SVC should have been issued and correctthe problem. Otherwise, find out if the calling programshould have been running in supervisor state or shouldhave issued another SVC.

Module: GCTITS

201

Explanation: The user is not authorized to access thestorage specified by the ECB in a WAIT macroparameter list.

User response: Check the ECB address entered in theWAIT macro.

Module: GCTWAI

202

Explanation: The state block address in an ECB that isbeing POSTed does not refer to a state block in thecaller's task block/state block structure. The state blockaddress loaded into the WAIT ECB may have beenaltered, or the state block may have been destroyed.

12F • 202


The POST routine will reduce the state block's waitcount--allowing the waiting program to move out ofthe wait state--only if the state block address that wasloaded into the WAIT ECB is still valid.

User response: Make sure that ECB contents are notbeing changed, and that the waiting program stateblock has not been destroyed.

Module: GCTWAI

206

Explanation: The parameter list address or an addressin the parameter list (1) was undefined; or (2) was in adifferent key than that of the calling program and waslocated in fetch-protected storage.

Code Meaning

04 Address is not within caller's private storagelocation.

A reason code of 04 occurs only when the ERRETparameter of the LOAD macro is specified.

User response: Make sure that no parameter list isbeing incorrectly modified. Ensure that all addressesare correct.

Module: GCTPMC, GCTPMD, GCTPML, GCTLOS

Severity: 04

20D

Explanation: A subtask of the current program hasended abnormally with the STEP parameter. STEPcauses GCS to abnormally end all tasks and commandsthat are related to the ABENDed subtask.

User response: Correct the problem in the subtaskthat failed.

Module: GCTABD

22A

Explanation: Invalid parameters were passed to anATTACH macro. A share subpool value greater than127 was specified on the SHSPV parameter, or a sharesubpool value greater than 127 was included in a listwhose address was coded in the SHSPL parameter.

User response: Correct the SHSPV or SHSPLparameter. Make sure that the parameter address iscorrect if an SHSPL parameter is used.

Module: GCTATT

22C

Explanation: The storage key for the id addresspassed to a CHAP macro differs from that of the taskthat issued the CHAP, and the address is located infetch-protected storage.

User response: Provide a valid task id address.

Module: GCTATT

230

Explanation: A length of zero was specified for thename representing a resource in a call to the DEQmacro.

User response: First, check to see if the RNAMELENGTH parameter for the DEQ macro is zero. If it iszero, then the first byte of the minor name field shouldcontain the length of the minor name field and mustnot be zero. Note that no explicit length need be coded;RNAME length defaults to the assembled length ofRNAME if the value is not given elsewhere.

Module: GCTENQ

233

Explanation: A user program has called the SDUMPmacro with an invalid parameter list address.

User response: Correct the user program to pass avalid parameter list address.

Module: GCTDUM

Severity: 8

233

Explanation: A user program has called the SDUMPXmacro with a parameter list structure that is not valid.

User response: Correct the user program to pass avalid parameter list structure.

Module: GCTDUX

Severity: 4

233

Explanation: A user program has called the SDUMPXmacro with a parameter list address that is not valid.

User response: Correct the user program to pass avalid parameter list address.

Module: GCTDUX

Severity: 8

238

Explanation: A length of zero was specified for theRNAME in an ENQ macro parameter list.

User response: First, check to see if the RNAMELENGTH parameter is zero. If it is zero, then the firstbyte of the minor name field must contain its lengthand must not have a value of zero. A non-zero lengthmust be coded in one of these fields.

206 • 238


Module: GCTENQ

23E

Explanation: The address of the task id supplied tothe DETACH macro is invalid for one of the followingreasons:

v The storage key for the task id address differs fromthat of the issuing task and the address is infetch-protected storage.

v The task id is zero.

v The task id does not exist.

v The sub-task identified by the task id is not a directdescendant of the task that issued the DETACH.Tasks may DETACH only tasks that theyATTACHed.

User response: Correct the parameter on the DETACHmacro. Make sure that the task id address is a fullwordwith the task id in the two low- order bytes. Also makesure that this task id matches the task id returned whenthe ATTACH macro was issued for this sub-task.

Module: GCTATT

240

Explanation: No work area was provided in theparameter list for an OS RDJFCB macro.

User response: Check RDJFCB specification.

Module: GCTSVT

244

Explanation: The address of the caller's savearea (inregister 13) was found to be invalid during execution ofthe SYNADAF macro.

User response: Make sure that register 13 points to aregister savearea within user storage when SYNADAFSVC 68 is issued. If SYNADAF is issued from aSYNAD routine, make sure that register 13 has notbeen altered since the SYNAD routine was entered, andthat register 13 contained the address of a valid registersavearea when the last data management macro wasissued.

Module: GCTSER

2CB

Explanation: An SVC 203 was issued, but thehalfword code issued with the SVC did not match anyvalid SVC 203 function.

User response: Correct the halfword code so that itspecifies the desired function.

Module: GCTITS

301

Explanation: The wait flag is already on for the ECBcoded in a WAIT macro parameter list.

User response: Check to see if two WAIT macros areunintentionally being issued for the same ECB. Zeroout the ECB before it is used by a WAIT macro.

Module: GCTWAI

305

Explanation: An error occurred when (1) an SVC 5FREEMAIN tried to release storage belonging to anunsupported subpool; or (2) an SVC 5 FREEMAIN triedto release storage belonging to a subpool requiringauthorization, and the program that issued the requestis not authorized; or (3) the storage being released hasa subpool number different from the number of thesubpool from which the storage was obtained.

User response: Check the FREEMAIN causing theerror and make sure that the subpool specified iscorrect.

Module: GCTFSV

30A

Explanation: A program has issued an SVC 10FREEMAIN, and one of the following three errors hasresulted: (1) the task has released storage belonging toan unsupported subpool; (2) the task has releasedstorage belonging to a subpool for which authorizationis required, and the program is not an authorizedprogram; or (3) the storage being released has asubpool number different than the number of thesubpool from which the storage was obtained.

User response: Make sure that the subpool is codedcorrectly in the FREEMAIN.

Module: GCTFSV

344

Explanation: An invalid DCB address or DCB DEB(DCBDEBAD) address was encountered duringexecution of the SYNADAF macro.

User response: Correct the invalid address. ForQSAM, the DCB address should be passed toSYNADAF as the PARM1 operand on the SYNADAFmacro instruction. (For BSAM and QSAM, the DCBaddress is in register 1 on entry to the user's SYNADroutine.)

Module: GCTSER

23E • 344


378

Explanation: A program has issued an SVC 120FREEMAIN and (1) has tried to release storagebelonging to an unsupported subpool; (2) the task hastried to release storage belonging to a subpool forwhich authorization is required, and the task is notauthorized; or (3) the storage being released has asubpool number that is different from the number ofthe subpool from which it was obtained.

User response: Make sure that the subpool beingpassed to the FREEMAIN is correct.

Module: GCTFSV

406

Explanation: The module that was to be LINKed,XCTLed, ATTACHed or OSRUNed was marked 'OnlyLoadable' by the linkage editor. The failure may haveoccurred when the user program issued a LINK orXCTL macro directly. But the failure may also haveresulted when an ATTACH macro or an OSRUNcommand called the LINK macro.

User response: LOAD should be used to bring amodule marked 'Only Loadable' into storage beforeother operations are performed. If the module is notonly loadable, relink the module to remove theattribute.

Module: GCTPMC

42A

Explanation: The ECB address specified in the ECBparameter for an ATTACH macro is invalid. Theaddress is in a different storage protection key thanthat of the program that issued the ATTACH.

User response: Provide a valid address for the ECBparameter.

Module: GCTATT

430

Explanation: An invalid parameter list was coded in acall to the DEQ macro. The calling program is notauthorized to access the storage area specified in theparameter list.

User response: Check the list address and theaddresses of major and minor names in the DEQparameter list.

Module: GCTENQ

438

Explanation: An invalid parameter list was entered ina call to the ENQ macro. The calling task is notauthorized to access the storage area specified in theparameter list.

User response: Check the list address input parameterand the addresses of major and minor names in theENQ parameter list.

Module: GCTENQ

43E

Explanation: An invalid address was passed to aDETACH macro. The ECB address was valid, but nowis not in the same storage key as the task that issuedthe ATTACH.

User response: GCS system storage has been modifiedsince your sub-task was attached. Contact your systemprogrammer.

Module: GCTATT

444

Explanation: An invalid DECB address wasencountered during execution of the SYNADAF macro.

User response: For BSAM, the DECB address shouldbe passed to SYNADAF as the PARM2 operand on themacro instruction. (The DECB address is in register 0on entry to the user's SYNAD routine.)

Module: GCTSER

530

Explanation: A DEQ has been issued before an ENQfor the same resource could be filled. The same taskissued both the ENQ and the DEQ, and RET=HAVEwas not coded in the DEQ call.

User response: Try coding RET=HAVE as a DEQparameter. The DEQ request will not be honored and areturn code will be produced if the ENQ has not beencompleted before the DEQ is issued. But withRET=HAVE, the task will not abend.

Module: GCTENQ

604

Explanation: The GETMAIN macro just issued had (1)an invalid address in the A or LA operand; or (2) aninvalid parameter list address. The address in the A orLA operand was invalid because it specified a locationoutside the virtual storage assigned to the task.

User response: Check the coding of the GETMAINmacro instruction, and re-execute the program aftercorrecting the instruction.

378 • 604


Module: GCTGSV

605

Explanation: A program has issued an SVC 5FREEMAIN (E-type or V-type FREEMAIN), but theFREEMAIN parameter lists were protected by a storagekey that the issuing program could not read from.

User response: Check to see that the storageprotection key for the FREEMAIN parameter lists iscorrect.

Module: GCTFSV

638

Explanation: The storage requested by the ENQ macrowas not available. GETMAIN could not get the storagenecessary for control blocks.

User response: Re-execute the program.

Module: GCTENQ

704

Explanation: An uncorrectable machine, system orindeterminate error occurred while processing aGETMAIN macro call. An improper mode byte mayhave been sent to the GETMAIN entry module, orthere may not be sufficient system storage to processthe GETMAIN.

User response: Check to see if the mode byte iscorrect if the user is coding his own mode byte.Otherwise, increase the size of the virtual machine andre-IPL it.

Module: GCTGSV, GCTATT

705

Explanation: There was not enough storage availableto meet the internal processing needs of an SVC 5FREEMAIN.

User response: Increase the size of the virtual machineand re-IPL it.

Module: GCTFSV, GCTATT

706

Explanation: The module requested in a LINK, LOAD,XCTL, or ATTACH macro, or OSRUN or LOADCMDcommand could not be used. Either the module wasmarked as not executable by the linkage editor, or themodule is an overlay module, which is not allowed inGCS.

This abend can result when a user program issues aLINK, LOAD, or XCTL macro directly. But the failuremay also occur when an ATTACH macro or an OSRUN

or LOADCMD command is issued, since these callLINK or LOAD.

A reason code of 04 occurs only when the ERRETparameter of the LOAD macro is specified.

User response: Correct the problem in the requestedload module and relink-edit it into a LOADLIB.

Module: GCTLOS

70A

Explanation: An uncorrectable machine, system orindeterminate error occurred while processing anR-type GETMAIN or FREEMAIN (an SVC 10GETMAIN or FREEMAIN). The abnormal end mayhave occurred because an improper mode byte wassent to the GETMAIN entry module, or because therewas not enough storage to process the GETMAIN.

User response: Check to see that the mode byte iscorrect if the user is coding his own mode byte.Otherwise, increase the amount of storage and re-IPLthe virtual machine.

Module: GCTFSV, GCTGSV

72A

Explanation: An address passed to the ATTACHmacro is invalid because the storage key for theaddress differs from that of the calling program, andbecause the address is in fetch-protected storage. Theaddress is one of the following:

v the address of the ATTACH parameter list

v the EPLOC or DE address

v the SHSPL address (the address is invalid or the firstbyte in the list has a value of zero).

User response: Provide a valid address for theincorrect parameter.

Module: GCTATT

778

Explanation: An uncorrectable machine, system, orindeterminate error occurred while processing anRU-type GETMAIN or FREEMAIN macro. The problemmay have occurred because an improper mode bytewas sent to the GETMAIN entry module, or becausenot enough storage was available to complete theGETMAIN or FREEMAIN.

User response: Ensure the mode byte is correct if theuser coded it. Increase the amount of storage andre-IPL the virtual machine.

Module: GCTFSV GCTGSV GCTTKS

605 • 778


778

Explanation: A GETMAIN or FREEMAIN issued bySTIMER or ATTACH has failed because not enoughstorage was available to complete the GETMAIN orFREEMAIN.

User response: Ensure the mode byte is correct if theuser coded it. Increase the amount of storage andre-IPL the virtual machine.

Module: GCTATT GCTTIM

804

Explanation: The length field passed to a GETMAINmacro contained either a negative or zero length, orspecified a length that exceeded the available virtualstorage.

User response: Choose the appropriate action fromamong the following:

v Check the coding of the LV operand. Re-execute theprogram after making corrections.

v Change the problem program so that it requests asmaller amount of storage.

v Increase the amount of storage in the virtual machineand re-IPL it.

Module: GCTGSV

806

Explanation: A LINK, LOAD, XCTL, or ATTACHmacro requested a program that could not be found, oran I/O error occurred while processing the request.Register 15 contains a hexadecimal reason code:

Code Meaning

04 The program could not be found or noLOADLIBs were defined by the GLOBALcommand.

08 An uncorrectable I/O error occurred when theBLDL control program routine attempted tosearch the directory.

10 CLOSE gave a non-zero return code after themodule was loaded.

User response: If the reason code is 04, be sure thatyou issued the GLOBAL command with the LOADLIBparameter and the names of the LOADLIBs which maycontain the requested module. If the reason code is 08,correct the cause of the I/O error. Note that this isprobably not a user program error. If the code is 10,rerun the job. Note that this is probably not a userprogram error.

Module: GCTLOS

Severity: 04, 08, or 10

80A

Explanation: The length field passed to an R-typeGETMAIN macro contained either a zero length or avalue too large for available storage.


1. Check the coding of the LV operand and re-executethe program.

2. Change the problem program so that it requests lessstorage.

3. Increase the amount of storage and re-IPL thevirtual machine.

Module: GCTGSV

878

Explanation: The length field passed to an RU-typeGETMAIN macro contained either a negative or zerovalue, or specified a length too large for availablestorage.


1. Check the coding of the LV operand and re-executethe program.

2. Change the problem program so that it requests lessstorage.

3. Increase the amount of storage and re-IPL thevirtual machine.

Module: GCTGSV

905

Explanation: A task issued an SVC 5 FREEMAIN, butthe address of the storage being released is not on adoubleword boundary.

User response: Correct the address parameter for theFREEMAIN.

Module: GCTFSV

906

Explanation: The Load and/or Use count for themodule requested by a LINK, LOAD, XCTL, orATTACH macro is already the maximum of 32767.

A Reason Code of 04 occurs only when the ERRETparameter of the LOAD macro is specified.

User response: Check for loops which cause the samemacro instruction to be issued too often.

Module: GCTLOS

778 • 906


90A

Explanation: A task has issued an SVC 10FREEMAIN, but the address of the storage that is beingreleased is not on a doubleword boundary.

User response: Correct the address parameters for theFREEMAIN.

Module: GCTFSV

944

Explanation: An invalid savearea address wasencountered during execution of SYNADRLS. Theinvalid address was either the SYNADAF saveareaaddress in register 13, or the pointer to the caller'ssavearea.

User response: Make sure that register 13 points tothe savearea address that was provided by SYNADAF.Also, make sure that the user's savearea address,(located 4 bytes into the savearea pointed to by theaddress in register 13), has not been altered.

Module: GCTSER

978

Explanation: A task has issued an SVC 120FREEMAIN, but the address of the storage beingreleased is not on a doubleword boundary.

User response: Correct the address parameter beingpassed to FREEMAIN.

Module: GCTFSV

A03

Explanation: This abnormal end occurred duringnormal task termination. The task that was terminatinghad a sub-task that had not been DETACHed.

User response: Make sure that all sub-tasks areDETACHed before a task terminates.

Module: GCTATT

A05

Explanation: A task issued an SVC 5 FREEMAIN and(1) the storage being released overlaps storage that isalready free; or (2) the storage being released is on apage that has been locked by PGLOCK.

User response: Check the parameters for theFREEMAIN to make sure that all addresses and lengthshave been coded correctly. Also check to see that anylocked storage has been unlocked before it is released.

Module: GCTFSV

A06

Explanation: The current task is already waiting forthe serially reusable module that has been requested byLINK, XCTL, or ATTACH.

User response: Do not allow an asynchronous exit toreference the same serially reusable module as the taskit is running for, at the same time as the task it isrunning for. Also, do not allow simultaneous referenceto the same serially reusable module by twoasynchronous exits running for the same task. Finally,do not allow a serially reusable module to try tore-enter itself.

Module: GCTPMC

A0A

Explanation: A task has issued an SVC 10FREEMAIN, and (1) the storage being released overlapsstorage that is already free; or (2) the storage beingreleased is on a page that has been locked by PGLOCK.

User response: Make sure that the address and lengthparameters passed to FREEMAIN are correct. Alsocheck to see that any storage that has been locked isunlocked before it is released.

Module: GCTFSV

A78

Explanation: A task has issued an SVC 120FREEMAIN, and (1) the task-related storage that isbeing released overlaps storage that is already free; or(2) the storage that is being released is on a page thathas been locked by PGLOCK.

User response: Check to make sure that address andlength parameters passed to FREEMAIN are correct.Also check to see that any storage that has been lockedis unlocked before it is released.

Module: GCTFSV

B03

Explanation: Normal termination of a task has beeninterrupted because the task that was terminating stillholds a common lock.

User response: Make sure that all locks are releasedbefore a task terminates.

Module: GCTATT

B04

Explanation: An invalid subpool number wasspecified on an E- or V-type GETMAIN macro. Thenumber may have been invalid because:

90A • B04


1. A program running in problem state tried to accessa subpool with a number outside the 0-127 range;or

2. A program running in supervisor state tried toaccess an unsupported subpool. (Supervisor stateprograms can access subpools with numbers in the0-127 range, PLUS subpools 229, 230, 231, 241, 243,and 244.)

User response: Check the coding of the SP operand ofthe GETMAIN macro.

Module: GCTGSV

B0A

Explanation: A subpool number greater than 127 waspassed to a R-type GETMAIN macro. An invalidsubpool number was specified on an E- or V-typeGETMAIN macro. The number may have been invalidbecause:



User response: Check the coding of the SP operand ofthe GETMAIN instruction.

Module: GCTGSV

B78

Explanation: A subpool number greater than 127 waspassed to a RU-type GETMAIN macro. An invalidsubpool number was specified on an E- or V-typeGETMAIN macro. The number may have been invalidbecause:



User response: Check the coding of the SP operand ofthe GETMAIN instruction.

Module: GCTGSV

C03

Explanation: Normal termination of the current taskhas been interrupted because the task still holdsresources through ENQs.

User response: Make sure that all resources have been

released by DEQ before a task terminates.

Module: GCTATT

D03

Explanation: A program tried to terminate withresources still held by ENQ.

User response: Make sure that all resources arereleased by DEQ before exiting the program.

Module: GCTFSV

D05

Explanation: A program has issued an SVC 5FREEMAIN, and (1) the task-related storage that isbeing released is not owned by the active task or by atask that is sharing storage with the active task; or (2)the storage has had its storage key changed since itwas obtained.

User response: Check to see that the address andlength parameters of the FREEMAIN are correct. Alsocheck to see that storage keys that were changed havebeen reset to what they were when the storage wasobtained. Lastly, make sure that the task releasing thestorage owns the subpool specified in the FREEMAINmacro, or shares the subpool with an ancestor.

Module: GCTFSV

D0A

Explanation: A program has issued an SVC 10FREEMAIN, and (1) the task-related storage that isbeing released is not owned by the current task or by atask sharing storage with the current task; or (2) thestorage that is being released has had its storageprotection key changed since the storage was obtained.

User response: Check that the address and lengthparameters passed to the FREEMAIN are correct. Makesure that a storage key that has been changed has beenreset to its original setting. Also make sure that the taskwhich is releasing the storage owns the subpoolspecified in the FREEMAIN macro, or shares thesubpool with an ancestor.

Module: GCTFSV

D23

Explanation: A validate was issued for the replybuffer address specified in the ORE (Operator ReplyElement) Data Area. The return code from validateindicates the address is inaccessible to the user. Thetask that issued the WTOR will be abnormallyterminated.

User response: Specify a reply buffer address withinthe range of your virtual storage.

Module: GCTRPY

B0A • D23


D23

Explanation: One of two errors has occurred: (1) Aninvalid address was passed to a WTO or WTOR macro.The address or addresses passed in the parameter listare located in storage that the user cannot access. (2) AGETMAIN macro was unable to get a WQE or OREbuffer because not enough storage was available.

User response: To correct the first problem, make sureall parameter list addresses are within your range ofstorage. To correct the second problem, either increasethe amount of virtual storage available to the programor reduce the program's storage needs.

Module: GCTWTR

D78

Explanation: A task has issued an SVC 120FREEMAIN, and (1) the task-related storage that isbeing released is not owned by the active task or by atask that shares storage with the active task; or (2) thestorage key for the storage that is being released hasbeen changed since the storage was obtained.

User response: Make sure that the address and lengthparameters being passed to FREEMAIN are correct.Check to see that a storage key that has been changedis reset to its original setting before the storage isreleased. Also make sure that the task that is releasingthe storage owns the subpool specified in theFREEMAIN macro, or shares the subpool with anancestor.

Module: GCTFSV

E04

Explanation: A GETMAIN macro has been called withan MVS parameter that is not supported in the GCSenvironment. The unsupported parameter is either LCor LU mode.

User response: Rewrite the problem program so thatit requests allocation of only one storage area at a time.

Module: GCTGSV

E05

Explanation: A task has issued an SVC 5 FREEMAINusing an unsupported MVS parameter. The parameteris one of the following:

v EC

v VC

v LC

v L

User response: Change the macro call so that it usesonly supported parameters.

Module: GCTFSV

E0A

Explanation: A task has issued an SVC 10FREEMAIN, but (1) the SVC 10 was called without anLV parameter; or (2) a zero length was specified as theLV parameter for the FREEMAIN.

User response: Change the macro call to use an LVparameter with a non-zero length.

Module: GCTFSV

E0B

Explanation: A parameter that is not supported byGCS was used in a call to the TIME macro.Unsupported parameters include TU, MIC, STCK, andZONE=GMT.


Module: GCTTIM

E23

Explanation: A validate was issued for the ECBaddress specified in the ORE (Operator Reply Element)Data Area. The return code from validate indicates theaddress is inaccessible to the user. The task that issuedthe WTOR will be abnormally terminated.

User response: Specify a reply buffer address withinthe range of your virtual storage.

Module: GCTRPY

E23

Explanation: An invalid ECB or reply area addresshas been passed to the WTOR macro. The error orreply area address is located in storage that the userprogram cannot access.

User response: Make sure that the ECB or replyareaaddress passed to WTOR is within your storage range.

Module: GCTWTR

E2E

Explanation: The CANCEL parameter for the TTIMERmacro was not specified, or a parameter that is notsupported by GCS was passed to TTIMER.Unsupported parameters include TU and MIC.


Module: GCTTIM

D23 • E2E


E2F

Explanation: A parameter that is not supported byGCS was passed to the STIMER macro. Unsupportedparameters include TASK, GMT, TUINTVL, andMICVL.


Module: GCTTIM

E30

Explanation: A parameter that is not supported in theGCS environment was coded in a call to the DEQmacro. The parameter is one of the following:

v GENERIC=YES

v RMC=STEP

v SYSTEM

v SYSTEMS

v TCB

v UCB

v Multiple requests in one macro call.


Module: GCTENQ

E38

Explanation: A parameter that is not supported in theGCS environment was coded in a call to the ENQmacro. The parameter is one of the following:

v SMC=STEP

v SYSTEM, SYSTEMS

v TCB

v Multiple requests with one macro call.


Module: GCTENQ

E78

Explanation: A task has issued an SVC 120FREEMAIN and (1) the SVC 120 was called without anLV parameter; or (2) A zero length was specified in theLV parameter and a zero address was specified in theA parameter.

User response: Change the FREEMAIN call so that ituses an LV parameter with a non-zero length, and/orchange the A parameter to specify a non-zero address.

Module: GCTFSV

Severity:

Fxx

Explanation: The SVC number that was issued is notsupported. The numbers replacing the 'xx' in the abendcode represent the unsupported SVC number.

User response: Correct the SVC number and reissuethe command.

Module: GCTITS

FCA

Explanation: GCS internal error.

User response: Contact your system supportpersonnel.

Module: GCTRSS

Severity: 0108

FCA



Module: GCTRSS

Severity: 0109

FCA

Explanation: GENIO STARTR is an authorizedfunction, and the calling program was not in supervisorstate.

User response: Make sure that the calling program isin supervisor state before GENIO STARTR is issued.

Module: GCTGIM

Severity: 0501

FCA

Explanation: GCS Internal error.


Module: GCTRSS

Severity: 0666

FCA



Module: GCTREX

Severity: 0950

E2F • FCA


FCA



Module: GCTRSS

Severity: 095C

FCA



Module: GCTRSS

Severity: 095F

FCA



Module: GCTRSS

Severity: 0BBC

FCA

Explanation: User is not authorized to access thestorage specified in the plist.

User response: Check the address in the plist to makesure that the fetch access is possible.

Module: GCTACC GCTARE GCTEIO GCTERSGCTGLB GCTOSR GCTSTT

Severity: 0C00

FCA

Explanation: Module was called by a non-REXX™

module below start of GCS nucleus.

User response: Correct your program to not call asystem module.

Module: GCTRSS

Severity: 0CF0

FCA

Explanation: Module was called by a non-REXXmodule outside the GCS nucleus.

User response: Correct your program to not call asystem module.

Module: GCTRSS

Severity: 0CF9

FCA

Explanation: An invalid parameter list has beenpassed to the REXX processor. Either the parameter listaddress itself is invalid, or an address within theparameter list is invalid.

User response: Ensure that the parameter list and anyaddresses contained in the parameter list reside instorage accessible to the issuing program.

Module: GCTREX

Severity: 0E01

FCA

Explanation: A user program issued a FILEDEFcommand with an invalid parameter list address.

User response: Correct the program so that it passes avalid parameter list address.

Module: GCTFLD

Severity: 0F00

FCA

Explanation: A FREEMAIN macro has returned anon-zero return code, indicating a failure to releasestorage.

User response: Re-IPL the system. If the problempersists, contact your IBM support personnel.

Module: GCTNXT

Severity: 1001

FCA

Explanation: A GETMAIN issued by the current taskhas failed.

User response: First, try re-executing the program inwhich the failure occurred. If the problem persists,increase the size of the virtual machine and re-IPL it.

Module: GCTIUE, GCTIUX

Severity: 1101

FCA

Explanation: The GCS QUERY command has beencalled with an invalid parameter list. The return codefrom a VALIDATE issued on addresses in the listindicates that the parameter list address or addresseswithin the parameter list are not accessible to the user.

User response: Make sure that parameter listaddresses are within the range of your storage.

Module: GCTQRY

Severity: 1200

FCA


FCA

Explanation: The GCS REPLY command has beencalled with an invalid parameter list. The return codefrom a VALIDATE issued on addresses in the listindicates that the parameter list address or addresseswithin the parameter list are not accessible to the user.


Module: GCTRPY

Severity: 1300

FCA

Explanation: The GCS LOADCMD command hasbeen called with an invalid parameter list. The returncode from a VALIDATE issued on addresses in the listindicates that the parameter list address or addresseswithin the parameter list are not accessible to the user.


Module: GCTLDC

Severity: 1400

FCA

Explanation: A user program has invoked theETRACE command with an invalid parameter listaddress.

User response: Correct the user program so that itpasses a valid parameter list address.

Module: GCTYTE

Severity: 1500

FCA

Explanation: A user program has invoked the ITRACEcommand with an invalid parameter list address.

User response: Correct the user program so that itpasses a valid parameter list address.

Module: GCTYTG

Severity: 1600

FCA

Explanation: An invalid address was detected duringSET command processing.

User response: A GCS error message will usually havepreceded this abend message. Please see the 'UserResponse' section for the error message that appearedand respond as indicated.

Module: GCTDLB

Severity: 1700

FCA

Explanation: An invalid address was detected duringDLBL command processing.

User response: A GCS error message will usually havepreceded this abend message. Please see the 'UserResponse' section for the error message that appearedand respond as indicated.

Module: GCTDLB

Severity: 1800

FCB

Explanation: An AUTHCALL macro was issued, butthe issuing program did not have access to the addressof the name of the authorized program.

User response: Correct the problem in the applicationprogram.

Module: GCTLAC

Severity: 0100

FCB

Explanation: A program tried to acquire the commonlock on GCS common storage without first getting thelocal lock on resources in the program's own virtualmachine.

User response: Make sure the program acquires thelocal lock before requesting the GCS common lock.

Module: GCTLLK

Severity: 0601

FCB

Explanation: Not enough free storage was availablefor GETMAIN to secure an AEB for the SCHEDEXmacro.

User response: Check to make sure the abend is notbeing caused by an error in the application program.Correct the application program if it is at fault.Otherwise, increase the size of storage.

Module: GCTSDX

Severity: 0A01

FCB

Explanation: User is not authorized to access thestorage specified by the parameter list (plist) address,or the address of NAME, or TOKEN contained withinthe plist.

User response: Check the address of the plist, theaddress of the NAME, and the TOKEN (if specified),within the plist to ensure fetch access is possible.

FCA • FCB


Module: GCTTKN

Severity: 0C00

FCB

Explanation: User is not authorized to update thestorage specified by the address of TOKEN in theparameter list (plist).

User response: Check the address specified byTOKEN in the plist to ensure write access is possible.

Module: GCTTKN

Severity: 0C0A

FCB

Explanation: The GCSTOKEN parameter list (plist)contained an address of zero for either the NAME,TOKEN, or both.

User response: Check the address of the NAME andthe TOKEN within the plist to ensure each is properlyspecified.

Module: GCTTKN

Severity: 0C0B

FCB

Explanation: A FREEMAIN of private storage issuedby GCSTOKEN has failed because not enough storagewas available to complete the FREEMAIN.

User response: Define a larger virtual storage size forthe virtual machine and re-IPL GCS.

Module: GCTTKN

Severity: 0C1F

FCB

Explanation: A FREEMAIN of common storage issuedby GCSTOKEN has failed because not enough storagewas available to complete the FREEMAIN.

User response: If you have high common storagecapabilities, ask your system programmer or your IBMsupport representative to define a larger high commonstorage area using the GROUP EXEC, and rebuild GCS.Re-IPL GCS with the larger common storage area.

Module: GCTTKN

Severity: 0C2F

FCB



Module: GCTTKN

Severity: 0C3F

FCB

Explanation: Invalid shared variable request blockaddresses were passed to the EXECCOMM routine.

User response: Make sure that the addresses havebeen coded correctly.

Module: GCTREX

Severity: 0D01

FCB


TSAF Abend CodesWhen a TSAF abend occurs, the TSAF operator must follow several steps:1. Collect information about the error.

Save the console sheet or spooled console output of the TSAF virtual machine.Save and process, using the CMS DUMPLOAD and the DVF MAP commands,any dumps produced by TSAF. Save any TRSOURCE file that may containTSAF data.

2. Collect information about the system status.The following information can be useful and even necessary in problemdetermination:v The status of real and virtual devices in use by TSAFv The level of system load at the time of failure on any of the systems using

TSAF and the status of each system (for example, did one abend?)v The types of applications that are using TSAF at the time and any

information about them that can be freely providedv The physical connection configuration of the systems in use.

3. Recover from the abend so processing can continue.When an abend occurs in TSAF, either because TSAF issued an ABEND orbecause a TSAF or CMS operation caused a program exception, TSAF producesa dump by way of the CP VMDUMP command. The dump is placed in TSAF'svirtual reader. TSAF then issues a CP SYSTEM RESET command. If theCONCEAL option is on, as recommended, CP automatically IPLs CMS.Otherwise, operator intervention is required to re-IPL CMS. Similarly, if TSAF isnot invoked from the PROFILE EXEC, the operator must restart it manually.For more information on TSAF problem determination, consult the z/VM:Diagnosis Guide.

The following is a list of the TSAF abend codes, the modules that issue them, anexplanation of the abend, and responses the user should take to recover andcontinue.

Note: xxx represents any TSAF module that issues this message.

ATS010

Explanation: Error return from ABNEXIT.

This is a system error. The TSAF abend exit was notestablished, so no dump was taken, nor will the normalproblem determination information be displayed on theconsole.

User response: Save any problem information thatCMS or TSAF presents. Issue a VMDUMP command todump the contents of the virtual machine. Contact yourservice representative.

Module: ATSCTL

ATS300

Explanation: Error on the HNDIUCV SET CMSfunction.

This is a system error. TSAF was unable to successfully

issue an HNDIUCV SET CMS function duringinitialization.

User response: Save any problem information thatCMS or TSAF presents. Contact your servicerepresentative.

Module: ATSIIN

ATS302

Explanation: *CRM is already in use by anothervirtual machine.

There is already another virtual machine that has aconnection to the *CRM system service. CP allows onlyone virtual machine at a time to be connected to thissystem service.

User response: Determine what other virtualmachine(s) are authorized to connect to this systemservice. Make the necessary corrections to the systemdirectory and perform the local procedures for starting

ATS010 • ATS302


these virtual machines. Then restart TSAF on theappropriate virtual machine. If this does not correct theproblem, save any problem information that CMS orTSAF presents, and contact your service representative.

Module: ATSIH1

ATS303

Explanation: Not authorized to connect to *CRM.

This virtual machine is not authorized in the systemdirectory to connect to the *CRM system service. TSAFdoes not take a dump on this abend.

User response: Make any needed corrections to thesystem directory, and restart TSAF on the appropriatevirtual machine. If this does not correct the problem,save any problem information that CMS or TSAFpresents, and contact your service representative.

Module: ATSIIN

ATS304

Explanation: Error on the CMSIUCV CONNECT to*CRM.

This is a system error. TSAF was unable to successfullyissue the CMSIUCV SET necessary to establish anIUCV path to the *CRM system service.


Module: ATSIIN

ATS310

Explanation: Error on a CMSIUCV CONNECT withprogram initialization parameters (PIP).

This is either a system error or a transmission error.The PIP data that TSAF attempted to pass to the targetof the request could not be received by the target.


Module: ATSIG2

ATS800

Explanation: Attempted to pop a frame from anempty stack.

A TSAF module encountered an empty stack becauseTSAF ran out of CMS free storage. The problem mayhave occurred because the TSAF virtual machine wasgiven insufficient virtual storage.

User response: Provide more storage for the TSAFvirtual machine, and restart TSAF. If it fails again,contact your system programmer.

Module: ATSxxx

ATS801

Explanation: Obtained a frame from a stack but theframe was already in use.

This is a TSAF system error. A TSAF moduleencountered a condition that should not have occurred.TSAF will have taken a dump and entered a disabledwait state.

User response: Save the problem information andcontact your system programmer or servicerepresentative.

Module: ATSxxx

ATS802

Explanation: Attempted to push a frame onto a stackbut the frame is already on a stack.

This is a TSAF system error. A TSAF moduleencountered a condition that should not have occurred.TSAF will have taken a dump and entered a disabledwait state.


Module: ATSxxx

ATS888

Explanation: Unable to obtain required storage.

A specific TSAF module requested free storage fromCMS. CMS diagnosed an error on that request. Theproblem may have occurred because the TSAF virtualmachine was given insufficient virtual storage.

User response: Provide more storage for the TSAFvirtual machine, and restart TSAF. If it fails again,contact your system programmer.

Module: ATSxxx

ATS890

Explanation: Unable to release storage.

A specific TSAF module tried to return storage to CMS.CMS diagnosed an error on that request. TSAF willhave taken a dump and entered a disabled wait state.


Module: ATSxxx

ATS303 • ATS890


ATS999

Explanation: TSAF system error.

A TSAF module encountered a condition that shouldnot have occurred. TSAF will have taken a dump andentered a disabled wait state.


Module: ATSxxx

Return CodesRefer to z/VM: CMS and REXX/VM Messages and Codes for information about returncodes produced by APPC/VM VTAM, CMS, CP, and VMSES/E.

ATS999



Chapter 3. System Messages

Messages are generated by the system in response to either an action or lack ofaction that has been detected. This section provides complete descriptions of thevarious z/VM messages the user may receive.


AVS Messages

AGW000E ERROR - No text found formessage/response number xxxx,yy

Explanation: An unrecognized error condition wascreated; the AVS repository has no entry for messagexxxx, response yy

System action: The system does not recognize andcannot effectively respond to the displayed message.

Operator response: Report the message, the format,and the system response to the appropriate systempersonnel.

AGW001I AVS initialization is complete. Theservice level is level.

Explanation: The operator has issued an AGW STARTcommand and AVS is initialized and ready for normaloperation. The service level is indicated by level.

System action: AVS is up and running normally.

Operator response: Commands can now be entered.

AGW002I Gateway gatelu is activated

Explanation: A gateway has been defined to VTAMand the CP. Normal conversation can now begin.

System action: Gateway gatelu is running normally.

Operator response: None.

AGW003I Gateway gatelu is deactivated

Explanation: The gateway is inactive - either forceddown by VM/VTAM or by an operator-issuedQUIESCE or DEACTIVE GATEWAY command.

System action: Gateway gatelu is deactivated. Noactive conversations exist.


AGW004I Gateway gatelu was severed

Explanation: Ownership of gateway gatelu wasrevoked and the connection severed.

System action: The connection is severed. CP will notattempt to reroute the connection to another gateway.


AGW005I External trace started

Explanation: AVS processed a SET ETRACE ONcommand.

System action: The system will write AVS tracerecords to a CPTRAP spool file.

Note: Nothing will be recorded by CPTRAP untilCPTRAP is appropriately enabled.


AGW006I External trace ended

Explanation: AVS processed a SET ETRACE OFFcommand.

System action: AVS will write trace records only toAVS virtual storage. No external tracing is performed.


AGW007I Trace table initialized. Table size =tablesize.

Explanation: An AGW START command was issued,automatically creating the internal trace table. Thetablesize is optionally defined; the default is 20 1K-byteblocks of virtual storage. Note that the displayedtablesize is a decimal value.

System action: The START command initializes theinternal trace table at the specified size.


AGW008I AGWPROF GCS initialization file wasnot found.

Explanation: GCS was unable to define the commandhandling routine to AVS.

System action: AVS initializes normally.


AGW013I A CNOS for gatelu, remotelu, modename isquiesced. Gateway is not active.

Explanation: When a gateway is not active, CNOScommands remain quiesced until the gateway isactivated.

System action: Once the gateway is established andactive, the system executes the specified CNOSinstructions.

Operator response: Activate the gateway to releasethe quiesced CNOS condition. Executed CNOScommands require no operator action.

AGW015I Conversation conid on gateway gatelu isdeactivated

Explanation: Conversation conid on gatelu isdeactivated as the result of a DEACTIVE CONVcommand.

System action: The conversation is ended.

AGW000E • AGW015I



AGW017I Quiesce is in progress.

Explanation: The system is being brought to a gradualhalt.

System action: New work is rejected.


AGW018I Attempting to renegotiate CNOS forgatelu, remotelu, modename for the originalcommand values.

Explanation: A CNOS from gatelu to remotelu failedbecause remotelu was not active. When it was activated,it issued a CNOS to gatelu for a session limit that washigher than the original session limit requested bygatelu.

System action: AVS is attempting to renegotiate theCNOS values back down to the originally requestedvalues from gatelu.


AGW021W Active conversations are stilloutstanding. Deactivation of gatewaygatelu will be completed when theconversations are terminated.

Explanation: The specified gateway cannot bedeactivated until all active conversations are completed.

System action: When the conversations are finished,the gateway will be deactivated.

User response: No response is needed. If you wantthe gateway to be deactivated immediately, issue theAGW DEACTIVE GATEWAY command with theFORCE option.

AGW041E Required parameter parmid is missing

Explanation: A required parameter is missing from theinput command.

System action: AVS ignores the command.

Operator response: Enter the required parameter andcorrect command.

AGW043E Parameter parmid is not valid

Explanation: The entered command parameter isinvalid.

System action: The command is ignored and thesystem is ready for another.

Operator response: Enter the correct parameter andcommand.

AGW044E Parameter parmid is too long

Explanation: The entered parameter had more thanthe allowable number of characters.


Operator response: Correct the command and re-enterit.

AGW047E Activate gateway gatelu failed. message.

Explanation: An AVS gateway cannot be establishedfor the reasons described in message. The variations ofmessage are:

v gatelu already exists

v AVS is not authorized for IUCV connectors

v Command is ignored

v Conversation manager conman could not be loaded.GCS ABEND code = abendrc, reason code = reasonrc

v Invalid addressing mode

v IUCV CONNECT errors errors

v IUCV CONNECT to *IDENT failed, RC=rcode

v Maximum number of AVS-IUCV connectionsreached

v OPEN ACB error

v SETLOGON error

v The CP installed does not include conversationmanager support.

System action: The command is ignored and thegateway is not activated.

Operator response: Note the corresponding failuremessage and correct the problem using the appropriateresponse listed below. Enter the gateway activationrequest again.

v gatelu already exists

A gateway with this name already exists in this GCSgroup. Either attempt to activate a different gateway,or contact the system administrator to have the useof this gateway restricted.

v AVS is not authorized for IUCV connectors

The AVS virtual machine is missing the IUCV*IDENT statement in its directory that allows theAVS virtual machine to connect to the IdentifySystem Service to identify gateways. Stop the AVSmachine, and have the system administrator add thisstatement to the AVS directory entry. Refer to z/VM:Connectivity for an example of a directory entry forthe AVS virtual machine.

v Command is ignored

While processing an ACTIVATE GATEWAYcommand, AVS encountered a programming error ora storage failure. Message 280S will precede message047E. Follow the actions described under message280S.

AGW017I • AGW047E

Chapter 3. System Messages 37

v Conversation manager conman could not be loaded.GCS ABEND code = abendrc, reason code = reasonrc

The conversation manager specified on theACTIVATE GATEWAY command could not beloaded with the GCS LOAD macro. Use the abendand reason codes that are returned to determine thecause of the failure and the appropriate response.

v Invalid addressing mode

The conversation management routine specified onthe ACTIVATE GATEWAY command was loadedusing 24 bit addressing mode while AVS was using31 bit addressing mode. This may cause theconversation management routine to functionincorrectly since it will not be able to access theparameters passed to it by AVS. The addressingmode being used by either the conversationmanagement routine or AVS must be changed. Formore information about conversation managementroutines, refer to z/VM: Connectivity.

v IUCV CONNECT errors errors

An IUCVCOM CONNECT failed while trying toactivate this gateway. Use the returned error code todetermine the cause of the failure and theappropriate response. For more information, refer toIUCVCOM in z/VM: Group Control System.

v IUCV CONNECT to *IDENT failed, RC=rcode

AVS received an IUCV sever in response to theIUCVCOM CONNECT to the *IDENT systemservice. Use the returned reason code to determinethe cause of the failure and the appropriate response.For more information, refer to “Identify SystemService” in z/VM: CP Programming Services.

v Maximum number of AVS-IUCV connectionsreached

The number of IUCV and APPC/VM connections toand from the AVS virtual machine have exceeded thenumber specified on the OPTION MAXCONNstatement in the AVS virtual machine's directoryentry. Have the system administrator increase thenumber of connections allowed to and from the AVSvirtual machine. For an example of a directory entryfor the AVS virtual machine, refer to z/VM:Connectivity.

v OPEN ACB error

While attempting to define an LU, AVS encountereda storage error, or VTAM did not accept the requestfrom AVS. Message 250E or 345E will precedemessage 047E. Follow the actions described underthese messages to determine the cause of the failureand the appropriate response.

v SETLOGON error

While attempting to activate a gateway, a VTAMSETLOGON request either was not accepted byVTAM, or failed. Message 047E may be preceded bymessage 365S or 375S. Follow the actions describedunder these messages to determine the cause of thefailure and the appropriate response. If message 047Eis not preceded by either of these messages, then the

SETLOGON request was not accepted by VTAMbecause the ACB was not properly opened or hasbeen closed. Attempt to activate the gateway again.If it fails again, contact your system personnel.

v The CP installed does not include conversationmanager support.

The release of CP on which this AVS machine isrunning does not support service pool machines orconversation managers. The CP level must at least bethe VM V1R1 level. Either activate the gatewaywithout specifying the MANAGER option, or notifysystem personnel that a different CP level is needed.

AGW049E Value value is too large

Explanation: The CNOS value is greater than themaximum value (32788) allowed by VTAM.

System action: The command is ignored.

Operator response: Enter a corrected value.

AGW050E CNOS for gatelu remotelu modename failed

Explanation: VTAM was unable to define the sessionsfor the specified gateway.

System action: The CNOS command fails.

Operator response: A previously issued error messagegave the VTAM reason code. Report that reason codeand the system response to the appropriate systempersonnel.

AGW051E CNOS for gatelu remotelu modenamefailed. Error creating gateway gatelu.

Explanation: A CNOS command failed as the result ofa gateway creation failure.

System action: The CNOS request is terminated.

Operator response: A previously issued message gavethe reason error code. If the error occurred as the resultof a program error, the system will initiate a dump.Based on the previously provided reason code (anddump where available), correct the problem andre-enter the CNOS request.

AGW053E No command was entered. AVS requestis ignored.

Explanation: No recognizable AVS command wasentered.


Operator response: Enter the correct command.


AGW054E START has terminated. GCS IDENTIFYfor AGWDSPMN failed. RC = num.

Explanation: The AVS START command was halted asa result of a failed GCS IDENTIFY macro command.

System action: AVS is not started.

Operator response: Look up the return code specifiedin the message in z/VM: CP Programming Services andz/VM: Group Control System. Correct the problem, andre-enter the START command.

AGW055E Command ignored. message.

Explanation: AVS is unable to successfully completeexecution of the function described in message. Thevariations of message are:

v Initialization is still in progress

v START command already issued

v Invalid START command parameter

v More than one ETRACE on START command

v Quiesce is in progress

v Gateway gatelu activation is in process

v AVS is stopping

v Gateway gatelu deactivation is in process

v Gateway gatelu already exists

v Gateway gatelu does not exist

v CNOS for gatelu remotelu modename is in process

v Non-numeric value value in number field

v Maximum number of trace blocks is 1000

v Only a START command is allowed


Operator response: Use the information contained inmessage to correct the command, or wait for the currentcommand to finish processing and enter the nextcommand.

AGW056S Deactivate for gatelu may not becomplete. IUCVINI CLR error error.

Explanation: An error occurred on a GCS IUCVINICLR during a DEACTIVE GATEWAY. There is apossibility that the gateway is not completelydeactivated, and thus cannot be re-activated.

System action: The system will execute a dump.

Operator response: Deliver the dump results to theappropriate system personnel.

AGW057S ITRACE not set. Programming error, RC= num.

Explanation: Internal tracing is not active.

System action: The system will execute a dump.

Operator response: To start internal tracing, use the

SET ITRACE ON command.

AGW060E Command ignored. {Userid|Logicalunit} for remotelu remuser {alreadyexists|does not exist}.

Explanation: Either the ADD USERID command failedbecause the local user ID for remotelu remuser alreadyexists, or the DELETE USERID command failed becausethe local user ID or the remote logical unit for remoteluremuser, does not exist.


Operator response: If the command was issued withincorrect parameters, re-issue the command with thecorrect parameters. Otherwise, there is no need tore-issue the command.

AGW066S {Define | Display} not issued for gateluremotelu modename. Storage failure RC =rc.

Explanation: A storage failure prevented anAPPCCMD OPRCNTL=DEFINE or an APPCCMDOPRCNTL=DISPLAY from being issued. Thesefunctions are issued as a result of a CNOS.

System action: The CNOS processing will continue.

User response: Use the STOP command to end AVS,then attempt to define more virtual storage. Restart theAVS virtual machine, and start your applications again.

AGW070E Command ignored. Conversation coniddoes not exist for gateway gatelu.

Explanation: Conversation conid on gatelu does notexist.


Operator response: Specify a valid conversation ID(conid) and gateway, and re-enter the connectionrequest.

AGW075S AVS is terminated. Programming errorduring Quiesce, RC = num.

Explanation: A programming error occurred whenAVS attempted to enter a quiesced state.

System action: AVS is terminated immediately.


AGW076E {Initial number of elements in PIP stackmust be greater than zero. | Storagefailure. Unable to create PIP buffer stackwith num elements.} [Stack will becreated with num elements.]

Explanation: An error occurred creating the AVS PIPbuffer stack. The error was caused by requesting zero

AGW054E • AGW076E


elements in the PIP stack or by a storage failure. Astorage failure occurred because there was not enoughstorage for the requested stack elements or because therequested number of stack elements exceeded thepredefined default number of elements.

System action: The system will try to create the AVSPIP buffer stack with the predefined number ofelements when the error occurred by requesting zeroelements or by a storage failure where the requestednumber of stack elements exceeded the predefineddefault number of elements.

If the error occurs by a storage failure because therewas not enough storage for the requested stackelements or if the error occurs a second time, thecommand fails.

Operator response: If the command fails, issue the CPDEFINE command to increase the size of the virtualmachine, IPL GCS, re-start AVS, and re-enter thecommand.

AGW080S Command ignored. Insufficient storageto process request.

Explanation: The requesting program cannot obtainthe required storage, buffers, or control blocks.

System action: The requested action is not performed.

Operator response: Notify the appropriate systempersonnel.

AGW081S Command failed. message

Explanation: The multiple variations of message belowall concern a severe lack of available virtual storage toexecute the command successfully.

v AVS stack storage depleted

v GETMAIN for trace table failed

v GETMAIN for SGB block failed

v GETMAIN for EXLST failed. RC=num

System action: The command fails.

Operator response: Attempt to define more virtualstorage and enter the command again. If this does notwork, contact the appropriate system personnel.

AGW082S Command failed. message

Explanation: There is insufficient virtual storageavailable to create either an ordered list or a stack. Thepossible variations of message are shown below.

v Error occurred creating AVS stack

v Error occurred creating AVS indexed ordered list

v Error occurred creating AVS ordered list


Operator response: Enter the CP DEFINE commandto increase the size of the virtual machine, IPL GCS,

restart AVS, and enter the command again.

AGW083S {Command failed. | Storage failure.}{IUCV QUERY {error occurred. | can notbe issued.} | GCS {ESTAE | IDENTIFY| IUCVINI} error occurred.} {RC=num. |PIP data can not be allowed.}

Explanation: The specified IUCV or GCS macro failed.

System action: The system terminates.

Operator response: Look up the macro return codespecified in the message, correct the problem, andre-IPL the system. For more information about IUCVmacros, refer to z/VM: CP Programming Services. Formore information about GCS macros, refer to z/VM:Group Control System.

AGW084S {Deactivate|Activate} gateway gatelufailed. {Programming error|Storagefailure}, RC = num.

Explanation: The system was unable to ACTIVATE orDEACTIVE the specified gateway due to a severeprogramming or storage failure error.

System action: The command fails, and in the case ofa programming error, the system will execute a dump.

Operator response: Report the return code and systemresponse (and deliver the dump results whereavailable) to the appropriate system personnel.

AGW086S {CNOS for gatelu remotelu modenamefailed. | CNOS cannot be issued as theresult of a {deactivate|activate} gatewaygatelu.} {Programming error|Storagefailure}, RC = num.

Explanation: The system was unable to execute theCNOS command because of a severe programming orstorage failure error.

System action: The command fails and, in the case ofa programming error, the system executes a dump.

Operator response: Note the return code, and deliverthe code and dump (when available) to the appropriatesystem personnel.

AGW087S {Gateway command | A gatewaycommand for gatelu} terminated.Programming error, RC = num.

Explanation: The system was unable to successfullycomplete execution of the GATEWAY command due toa severe programming error.

System action: The command fails and the systemexecutes a dump.

Operator response: Deliver the dump and the

AGW080S • AGW087S


corresponding return code to the appropriate systempersonnel.

AGW088S An unsolicited CNOS for gatelu remotelumodename completed, but a {storagefailure | programming error} occurred.Unpredictable results. RC = num

Explanation: A remote logical unit issued a CNOS tothe specified gateway LU. The CNOS completed, buterrors occurred during AVS processing. The results areunpredictable.

System action: Conversations are not able to beestablished. In the case of a programming error, adump is taken.

Operator response: Note the return code, and deliverthe code and corresponding dump to the appropriatesystem personnel.

AGW089S QUERY {CNOS | CONVERSATION} ongateway gatelu terminated. Programmingerror, RC = rc.

Explanation: The requested QUERY command faileddue to a programming error.

System action: The command fails, and the systemexecutes a dump.

User response: Deliver the dump and thecorresponding return code to the appropriate systempersonnel.

AGW090S Query failure on gateway gateluProgramming error, RC = num.

Explanation: The system was not able to successfullyexecute the QUERY command.


Operator response: Note the return code, and deliverthe code and corresponding dump to the appropriatesystem personnel.

AGW091E Deactivation of conversation for gateluconid failure. Storage error, RC = rc

Explanation: The system was unable to deallocateconversations for gateway gatelu due to a storagefailure.


Operator response: Note the storage failure code, anddeliver the code to the appropriate system personnel.

AGW091S Deactivation of conversation for gateluconid failure. Programming error, RC =rc

Explanation: The system was unable to deallocateconversations for gateway gatelu due to a severeprogramming error.


Operator response: Note the return code, and deliverthe code (and dump when available) to the appropriatesystem personnel.

AGW093S Query USERID command terminated.Programming error, RC = num

Explanation: The system was unable to execute theQuery USERID command because of a severeprogramming error.


Operator response: Note the return code, and deliverthe code and dump to the appropriate systempersonnel.

AGW094S Add USERID failed.{Storage|Programming} error, RC = num

Explanation: The system was unable to execute theAdd USERID command because of a severeprogramming or storage failure error.

System action: The command fails and, in the case ofa programming error, the system executes a dump.

Operator response: Note the return code, and deliverthe code and dump (when available) to the appropriatesystem personnel.

AGW095S Delete USERID failed. Programmingerror, rc = num

Explanation: The system was unable to execute theDelete USERID command because of a severeprogramming error.


Operator response: Note the return code, and deliverthe code and dump to the appropriate systempersonnel.

AGW096S AVS timer disabled. Programming error,RC = num

Explanation: The AVS timer has become disabled,causing a programming error.

System action: The system will initiate a dump andshutdown.

AGW088S • AGW096S


Operator response: Give the return code andaccompanying dump to the appropriate systempersonnel.

AGW149I End

Explanation: This message signifies the end of an AVSQUERY command or an AVS CNOS command.

System action: None.


AGW201I AVS termination completed

Explanation: AVS has ended execution.

System action: The system has shut down.


AGW240E Storage failure. message [Gateway =gatelu.] | [Gateway = gatelu,Conversation = conid.]

Explanation: Due to a storage failure, the system isunable to successfully complete the operation specifiedin message for the named gatelu and conid The multiplevariations of message are shown below.

v Unable to forward CONFIRM indication on VMpath pathid.

v Unable to forward DATA on VM path pathid.

v Unable to forward DEALLOCATE_CONFIRMindication on VM path pathid.

v Unable to forwardPREPARE_TO_RECEIVE_CONFIRM on VM pathpathid.

v Unable to forward REQUEST_TO_SEND indicationon VM path pathid.

v Unable to forward SEND indication on VM pathpathid.

v Unable to forward {QUIESCE|RESUME} indicationon {VM|VTAM} path pathid.

v Unable to issue APPCVM SENDPREP on VM pathpathid.

v Unable to issue APPCVM SENDRQCM on VMpath pathid.

v Unable to issue APPCVM SENDCMTD on VMpath pathid.

v Unable to issue APPCVM SENDFRGT on VM pathpathid.

v Unable to issue APPCVM SENDHMIX on VM pathpathid.

v Unable to issue APPCVM SENDLUW on VM pathpathid.

v Unable to communicate with Recovery Server.

v Unable to issue APPCVM SETMODFY on VM pathpathid.


Operator response: Use the STOP command to endthe AVS application and attempt to allocate morestorage. If this fails, contact the appropriate systempersonnel.

AGW241E Storage failure. Unable to issueAPPCCMD CONTROL = RECEIVE,QUALIFY = ANY command. GETMAINRC = num. Gateway = gatelu

Explanation: AVS encountered a storage failure inattempting to issue the APPCCMD CONTROL =RECEIVE function for the specified gateway.

System action: The system is unable to issue thenecessary number of RECEIVEs.

Operator response: If existing conversations appear tobe running normally, wait until a convenient time andthen bring AVS down. With the system down, use thereturn code to determine the cause of the failure andcorrect the problem. If no conversations can beallocated, bring AVS down immediately and correct theproblem.

AGW242E Storage failure. Unable to receive {logdata on | PS Header on | PIP datavariable.} VTAM path pathid [will bedeallocated]. Gateway = gatelu

Explanation: The system is unable to receive data overthe specified gateway due to a shortage of availablestorage.

System action: The system cannot receive the data.

Operator response: Use the STOP command to endthe AVS application and attempt to define morestorage. If this does not work, contact the appropriatesystem personnel.

AGW243E Storage failure. Unable to completeconnection request {on VM path pathid |. VTAM path pathid will be deallocated}.[Gateway = gatelu]

Explanation: Due to a shortage of available storage,the system is unable to complete a connection requestfor the specified pathid.

System action: No connection is formed.

Operator response: Use the STOP command to endthe AVS application and attempt to define more virtualstorage. If this does not work, contact the appropriatesystem personnel.


AGW244E Storage failure. Unable to continuereceiving data on VM path pathid.Gateway = gatelu, Conversation = conid

Explanation: Due to a shortage of available storagespace, the system is unable to continue receiving dataover the specified VM path.

System action: The system cannot receive any moredata.

Operator response: Attempt to define more virtualstorage. If this does not work, contact the appropriatesystem personnel.

AGW245E Storage failure. Unable to forward anyfurther indications or data on {VM |VTAM} path pathid. Gateway = gatelu [,Conversation = conid]

Explanation: Due to a shortage of available storage,outstanding functions on the VTAM or VM work queuewere not flushed. VTAM or VM cannot send any dataon the specified pathid.


Operator response: Use the STOP command to endthe AVS application and attempt to define morestorage. If this does not work, contact the appropriatesystem personnel.

AGW246E [Storage failure.] Unable to{deallocate|reject| deactivate gatewaygatelu.} [{VM|VTAM} path pathid.Gateway = gatelu [, Conversation =conid]]

Explanation: Due to a shortage of available storage,the system is either unable to deallocate or unable toreject the path for the specified gateway, or it is unableto deactivate gateway gatelu. Note that when no conid isgiven, the conid is the same as the gatelu.

System action: The path or gateway remains in place.

Operator response: Use the DEACTIVATE GATEWAYgatelu FORCE command option to bring AVS down,and attempt to allocate more storage. If this fails,contact the appropriate system personnel.

AGW247E Unable to Quiesce AVS

Explanation: AVS is unable to enter a quiesced state.


Operator response: Attempt to define more virtualstorage and re-execute the command. If this does notwork, contact the appropriate system personnel.

AGW248E Storage failure. Unable to receive FMH5

Explanation: The system is unable to receive thecorrect format information contained in the FMH5header.


Operator response: Use the DEFINE command toattempt to obtain more virtual storage. If that actionfails, contact the appropriate system personnel.

AGW249E Storage failure. Unable to {sendHEURISTIC_MIXED PS header | sendBACKOUT | send CONFIRM | sendFORGET PS Header | sendCOMMITTED PS header | issueAPPCCMD SETSESS | issueAPPCCMD SEND_ERROR} on VTAMpath pathid. Gateway = gatelu. [Unable tostore session_id sessid in the impliedforget ordered list]

Explanation: Due to a shortage of available storage,the system is unable to complete a send request on thespecified pathid.


Operator response: Use the STOP command to endthe AVS application and attempt to define more virtualstorage. If this is unsuccessful, contact the appropriatesystem personnel.

AGW250E GETMAIN failed. Unable to create ACB,RC = rc

Explanation: A GCS GETMAIN macro failed whiletrying to get storage for an ACB during an AGWACTIVATE GATEWAY command.

System action: The AGW ACTIVATE GATEWAYcommand fails, and a dump of the AVS virtual machineis taken.

User response: Deliver the return code and theassociated system dump to the appropriate systempersonnel.

AGW280S {Programming error detected, | Storagefailure,} RC = num

Explanation: The system has encountered a severestorage or programming failure.

System action: In the case of a programming error, thesystem will execute a dump.

Operator response: Give the return code and thesystem response (and the dump, when available) to theappropriate system personnel.

AGW244E • AGW280S


AGW281S FREEMAIN command failed.Programming error, RC = num

Explanation: The system was unable to free thespecified amount of main storage due to a severeprogramming error.


Operator response: Using the provided return code,determine the cause of the FREEMAIN error andattempt to correct the situation. If this does not work,report the return code and system response to theappropriate system personnel.

AGW282S Storage failure. {VM|VTAM} path pathidwill be deallocated. Gateway = gatelu. [,Conversation = conid]

Explanation: The system is unable to maintain the VMor VTAM path pathid to the specified gatelu due to asevere storage failure. Note that when no conid is given,the conid is the same as the gatelu.

System action: The path will be deallocated.

Operator response: Attempt to define more virtualstorage and reconnect the path. If this fails, contact theappropriate system personnel.

AGW301I VTAM {is ending | has cancelled theapplication for gateway gatelu}

Explanation: Either the VTAM virtual machine hasbeen halted, or the VTAM virtual machine has canceledthe application associated with the displayed gateway.

System action: If VTAM is ending, all gateways willbe deactivated, and all conversations will be stopped. Ifan application has been canceled, conversationsthrough that gateway will be stopped, and thatgateway will be deactivated.

User response: Contact the appropriate systempersonnel to restart the VTAM virtual machine, or tofind out why VTAM canceled the application, and tocorrect the problem.

AGW302I The CNOS limit of limit for gatewaygatelu, remote LU remotelu has beenexceeded. The allocation request hasbeen queued.

Explanation: The application has attempted toestablish more conversations through a particulargateway than the session limit allows.

System action: As conversations through this gatewaycomplete, the queued allocation requests will beprocessed.

User response: To avoid this message, issue the AGWCNOS command to increase the session limits.

AGW303E ATTN(LOSS) received for gatewaygatelu, remote LU remotelu, modemodename, SENSE = num

Explanation: AVS has received an ATTN(LOSS) fromVTAM, which indicates that sessions have been lost forthe LU-LU pair. The SENSE code indicates the reasonfor the network failure.

System action: The cause of the network failure mayhave to be resolved. The session limits established bythe AGW CNOS command may also have beenaffected.

User response: You should follow establishedprocedures for reporting network failures. For moreinformation about SENSE codes and network failurecauses, refer to SNA Formats.

AGW321E Invalid {data | operation code} receivedfrom the CRR recovery server [on anexchange log names completion | on ahold session completion | on a releasesession request |. Unable to completedeallocate session request.]

Explanation: The AVS communications server receivedunknown data or operation code from the CRRrecovery server.

System action: The data or operation code is ignored.


AGW322E Control links to the CRR recovery serverare not operational. Protectedconversations are not allowed. Existingprotected conversations will bedeallocated.

Explanation: Protected conversations are not allowedbecause AVS is unable to communicate with the CRRrecovery server.

System action: Any protected conversations aredeallocated and no new protected conversations areallowed.

Operator response: Make the CRR recovery serveravailable if you need a protected conversation and tryto allocate the protected conversation again. For moreinformation, refer to z/VM: CMS File Pool Planning,Administration, and Operation.

AGW323S APPCVM SENDDATA to the CRRrecovery server failed {. Programmingerror, IPAUDIT= num. |, IPRCODE =num.}

Explanation: An attempt by the AVS communicationsserver to send data to the CRR recovery server failed.

System action: The path to the CRR recovery server is

AGW281S • AGW323S


deallocated and all protected conversations aredeallocated.

Operator response: Note the IPRCODE or IPAUDITcode and contact the appropriate system personnel.

AGW324S {APPCVM | IUCVCOM} SEVER{TYPE=ABEND for the CRR recoveryserver path failed. Programming error,IPAUDIT= num. | for the CRR recoveryserver failed, {IPRCODE | RC}= num.}

Explanation: An attempt by the AVS communicationsserver to deallocate paths to the CRR recovery serverfailed.

System action: All protected conversations aredeallocated.

Operator response: Note the IPAUDIT code or returncode and contact the appropriate system personnel.

AGW325S {IUCV | IUCVCOM} ACCEPT functionfailed on a CRR recovery server path,{IPRCODE | RC} = nn.

Explanation: An attempt by the AVS communicationsserver to accept a connection to the CRR recoveryserver failed.

System action: The path to the CRR recovery server isdeallocated.

Operator response: Note the IPRCODE or RC codeand contact the appropriate system personnel.

AGW326S The CRR recovery server is unavailable.[{APPCVM | IUCVCOM} CONNECT{IPRCODE | RC} = num.]

Explanation: An attempt by the AVS communicationsserver to allocate a conversation to the CRR recoveryserver failed.

System action: Any pending protected conversationsare deallocated.

Operator response: Make the CRR recovery serveravailable if you desire a protected conversation. Formore information on how to make the CRR recoveryserver available, refer to z/VM: CMS File Pool Planning,Administration, and Operation. When available, note theIPRCODE or return code and contact the appropriatesystem personnel.

AGW327S APPCVM RECEIVE on a CRR recoveryserver path failed {. Programming error,IPAUDIT = num | , RC = num}

Explanation: An attempt by the AVS communicationsserver to receive data from the CRR recovery serverfailed.

System action: Paths to the CRR recovery server are

deallocated and any protected conversations aredeallocated.

Operator response: Note the return code or IPRCODEcode and contact the appropriate system personnel.

AGW328S Protocol error on a CRR recovery servercontrol link. Existing protectedconversations will be deallocated.

Explanation: The CRR recovery server issued anunexpected function on the control path.

System action: Paths to the CRR recovery server aredeallocated and protected conversations aredeallocated.

Operator response: Contact the appropriate systempersonnel.

AGW329E Protected conversations not allowedwith single session partners. {Changingnumber of sessions to 0. | Deallocatingthe conversation.}

Explanation: Protected conversations require a parallelsession partner. Single session partners cannotcommunicate with protected conversations.

System action: No session is allowed between the AVScommunications server and the communication partnerand no conversation will be allowed with this partneruntil it is set up for parallel sessions. Non-protectedconversations will be allowed after the CNOScommand is issued.

Operator response: Change the partner LU to useparallel sessions if they want to use protectedconversations.

AGW330E Programming error. Exchange log namesrequest could not be completed.

Explanation: The AVS communications server isunable to complete the exchange log names request dueto a severe programming error.


Operator response: Deliver the dump to theappropriate system personnel.

AGW331E Invalid state was found in exchange lognames table.

Explanation: The AVS communications server is notable to determine if an exchange log names is necessarydue to a severe programming error.


Operator response: Deliver the dump to theappropriate system personnel.


AGW332E Exchange log names for gatelu, remotelu,modename failed

Explanation: The CRR recovery server reports that arequest for exchange log names failed.

System action: Any pending protected conversationsfor this LU pair are deallocated.

Operator response: Issue AGW Q CNOS to verify thatCNOS was completed for the gateways listed. If CNOScompleted successfully, then look to the CRR recoveryserver for further action.

AGW333E The CRR Recovery Server was unable tocomplete a hold session request. VMpath pathid will be deallocated. Gateway= gatelu, Conversation = conid

Explanation: The CRR recovery server detected anerror condition on the hold session request sent fromAVS. For instance, the LUWID sent on the request wasunknown to the recovery server.

System action: The session is released and theconversation is deallocated.

User response: This situation should not occur. If itdoes, get a dump of the AVS virtual machine andgather diagnostic data from the CRR recovery server.Contact the designated support group for yourinstallation.

AGW345E Error on {OPEN|CLOSE} ACB, R15 =num, ERROR field = field.

Explanation: The system encountered an errorcondition in attempting to define or drop an LU usedfor access to global resources.

System action: The LU is not defined, or cannot beclosed.

Operator response: Note the reported contents of R15and the ERROR field, and report these to theappropriate system personnel.

AGW346E Unable to allocate conversation. No TPNis in the FMH5. Gateway = gatelu. VMpath pathid will be deallocated.

Explanation: No transaction program name wasavailable in the FMH5. There is no target for thisconnection. The path will be deallocated.

System action: The allocation fails.

User response: Cause the application to place a TPNin the FMH5 before issuing the APPCVM CONNECTmacro.

AGW347E Invalid LU name name specified onconnection request. VM path pathid willbe deallocated. Gateway = gatelu.

Explanation: The LU name entered with theconnection request for the specified gatelu is invalid.

System action: The system ignores the command andwill sever the path.

Operator response: Correct the LU name and re-enterthe last entered command.

AGW348E Invalid mode name modename specifiedon connection request. VM path pathidwill be deallocated. Gateway = gatelu.

Explanation: The mode name specified in theconnection request for the specified gatelu is invalid.


Operator response: Correct the mode name andre-enter the connection request.

AGW349E Gateway LU name gatelu does notcorrespond with an existing gateway.VM path pathid will be deallocated.

Explanation: The gateway ID specified in theconnection request is invalid. The conid is provided as areference.


Operator response: Correct the gateway name andre-enter the connection request.

AGW350E Invalid APPC/VM interrupt interruptreceived. VM path pathid will bedeallocated. Gateway = gatelu,Conversation = conid.

Explanation: An invalid APPC/VM interrupt wasreceived, probably as the result of an IUCV CONNECTmacro error, for the specified gatelu.

System action: The system will sever the VM path.

Operator response: Verify that the requester issued avalid APPC/VM function. If this is the case, report theerror message and system action to the appropriatesystem personnel.

AGW351E FMH5 rejected; LU name luid and modename modename unknown

Explanation: Session information (luid, modename)passed with the function management header isinaccurate.

System action: No connection is allowed.

AGW332E • AGW351E


Operator response: Correct the LU name and modename and re-enter the connection request.

AGW352E Unable to {allocate a conversation |deallocate the VTAM path} on gatewaygatelu, remote LU luid, because theCNOS limit is zero.

Explanation: VM/VTAM initially defines gatewayswith the maximum number of allowable sessions set tozero.

System action: When the session limit is zero, noconversations may be allocated and outboundconnection or deallocation requests are rejected by AVS.

Operator response: After defining the gateway, usethe CNOS command to enter the desired number ofallowable sessions for this gateway.

AGW353E PIP data is not allowed after FMH5. Theconnection is rejected.

Explanation: Program Initialization Parameter (PIP)data is not allowed after the gateway has receivedFMH5.

System action: The connection attempt is rejected.

Operator response: Re-issue the connection request,establishing the desired initialization parameters beforeFMH5 is sent.

AGW354E User userid can not use gateway gatelu,which is restricted for user userid

Explanation: Gateway gatelu is a dedicated privategateway. The user ID specified on the AGW ACTIVATEGATEWAY command is the only user ID allowed toinitiate connections to the SNA network through thisgateway.

System action: The allocation attempt fails.

User response: Issue the allocation through a global ornon-dedicated private gateway.

AGW355E PIP data is not allowed. The connectionis rejected

Explanation: PIP data was presented in the FMH5area but the AVS running on the system does notsupport PIP data.

System action: The system will deallocate the VTAMpath.

Operator response: If you are communicating throughan AVS that does not support PIP, then do not send PIPdata. If PIP data is desired, install a version of AVS thatsupports PIP data.

AGW356E Unable to save Fully Qualified LU namefor gateway gatelu

Explanation: The AVS communications server was notable to find the network name or the application namein the ACB's resource identification vector list. The fullyqualified LU name for this LU is not available.

System action: The ACTIVATE GATEWAY commandcompletes.

Operator response: Because the fully qualified LUname is not available, the exchange of log names willnot be possible. Protected conversations will not be ableto flow through this gateway. If protected conversationsare desired, dump the AVS virtual machine (using theCP VMDUMP command) and notify your systempersonnel.

AGW360S {APPCCMD CONTROL = SENDcommand not accepted by VTAM. |APPCCMD CONTROL = {PREPRECV |SEND}, QUALIFY = {DATAFLU |ERROR | FLUSH | RQSEND}command failed.} {RTNCD = num.,FDBK2 = num. [, RCPRI = num, RCSEC= num.] | R15 = num, R0 = num.} [VTAMpath pathid will be deallocated. Gateway= gatelu.] [Unable to issue{REQUEST_COMMIT | COMMITTED| New LUWID | PREPARE}.]

Explanation: The APPCCMD macro's SEND orPrepare_to_Receive call was rejected by VTAM.

System action: The system cannot enablecommunications.

Operator response: When provided, note the RTNCD,FDBK2, RCPRI, RCSEC codes, the contents of R0, R15,or the return code. Report these and the systemresponse to the appropriate system personnel.

AGW361S APPCCMD {CONTROL=PREPRECV |CONTROL=RECEIVE,QUALIFY=SPEC| CONTROL=ALLOC} command notaccepted by VTAM. [Unable to receivelog data.] {RTNCD = num, FDBK2 =num.|R15 = num, R0 = num.|RTNCD =num, FDBK2 = num, RCPRI = num,RCSEC = num.} [VTAM Path pathid willbe deallocated. Gateway = id.]

Explanation: The APPCCMD macroPREPARE_TO_RECEIVE (PREPRCV) call has beenrejected by VTAM.

System action: No communication is allowed. In somecases, the conversation is deallocated.

Operator response: Note the return code and thecontents of FDBK2 (and the contents of RCPRI andRCSEC where provided) or the contents of R0 and R15,and report these and the system response to the

AGW352E • AGW361S


appropriate system personnel.

AGW362S APPCCMD CONTROL=ALLOCcommand not accepted by VTAM.{RTNCD = num, FDBK2 = num|R15 =num, R0 = num|RTNCD = num, FDBK2= num, RCPRI = num, RCSEC = num}.

Explanation: The APPCCMD macro's allocate requestis rejected by VTAM.

System action: The specified resource cannot beallocated.

Operator response: Note the return code and thecontents of FDBK2 (and the contents of RCPRI andRCSEC where provided), or the contents of R0 and R15,and report these and the system response to theappropriate system personnel.

AGW363S APPCCMD CONTROL=SETSESScommand not accepted by VTAM.{RTNCD = number, FDBK2 = number |R15 = number, R0 = number | RTNCD =number, FDBK2 = number, RCPRI =number, RCSEC = number. Gateway =number, Conversation = number}.

Explanation: VTAM rejected the attempt to issue theAPPCCMD CONTROL=SETSESS macro.

System action: The function fails, and a dump of theAVS virtual machine is taken.

User response: Note the returned values from themessage, and deliver this information and the systemdump to the appropriate system personnel.

AGW364S APPCCMDCONTROL={DEALLOC|REJECT}command not accepted by VTAM.{RTNCD = num, FDBK2 = num|R15 =num, R0 = num|RTNCD = num, FDBK2= num, RCPRI = num, RCSEC = num}.[Gateway = id, Conversation = num.]

Explanation: The APPCCMD macro's DEALLOCrequest failed because of either a severe programmingerror or it was rejected by VTAM.


Operator response: Note the return code and thecontents of FDBK2 (and the contents of RCPRI andRCSEC where provided), or the contents of R0 and R15,and report these and the system response to theappropriate system personnel.

AGW365S SETLOGON command not accepted byVTAM. R15 = num, R0 = num.

Explanation: AVS's attempt to issue a SETLOGONcommand has been rejected by VTAM.

System action: The command is rejected by VTAM.

Operator response: Note the return code and thecontents of FDBK2, or the contents or R0 and R15, andreport these and the system response to the appropriatesystem personnel.

AGW366S APPCCMD CONTROL = OPRCNTL,QUALIFY = {DEFINE command failed.|DISPLAY command failed,| CNOScommand not accepted by VTAM.} {R15= num, R0 = num. | RTNCD = num,FDBK2 = num [, RCPRI = num, RCSEC =num]} [Gateway LU name = gatelu,Remote LU name = remotelu, Mode name= modename. The {DEFINE | DISPLAY}command was issued due to a CNOS.]

Explanation: The APPCCMD macro call is rejecteddue to a severe programming error.

System action: The command fails. In some cases,AVS initializes a dump.

Operator response: Note the contents of R0 and R15or the contents of RTNCD and FDBK2 (and thecontents of RCPRI and RCSEC where provided), andreport these and the system response to the appropriatesystem personnel.

AGW367S Local userid not found for remote userremuser at remote LU remotelu. VTAMpath pathid will be deallocated. Gateway= gatelu

Explanation: The specified local user was not found.A connection request was received with a security levelof SAME specified and a security user ID of remuser.However, a mapping from remlu remuser to a local userID does not exist.

System action: The system ignores the command andsevers the connection.

Operator response: If a mapping from remlu remuserto a local user ID is required, ask your system supportpersonnel (or the IBM Support Center for assistance) toadd one using the AGW ADD USERID command.Otherwise, action my be necessary to correct remuser atthe origin of the connection.

AGW369S Log data is too long. VTAM path pathidwill be rejected. Gateway = gatelu

Explanation: The partner sent more than themaximum amount of log data (512 bytes).

System action: The conversation will be deallocated.

Operator response: Change the partner application toprevent sending more than 512 bytes of log data.


AGW370S Unable to find the {gateway block forgateway gatelu | remote LU block forLU luid, mode name modename.}

Explanation: AVS is unable to find the pointer blocksfor the specified luid or gatelu.


Operator response: Make sure that the desiredgateway and/or logical unit are correctly defined andre-enter the command.

AGW371S APPCVM {SEND function | CONNECTcommand | SEVER TYPE=ABENDcommand} failed {. | , IPSENDOP =num.} Programming error, IPAUDIT =num. VM path pathid will be deallocated.Gateway = gatelu, Conversation = conid

Explanation: AVS encountered an APPCVM macroerror in requesting to send data, connect to a partner,or sever a partner over gatelu.

System action: The command fails and the VM pathwill be deallocated.

Operator response: Note the IPAUDIT return codeand report the code, system response, gatelu, and conidto the appropriate system personnel.

AGW372S APPCVM {RECEIVE | SETMODFY}command failed. [Unable to receive logdata. | Unable to receive PIP data. |Unable to receive allocation data.][Programming error, ] {IPAUDIT = num.| RC = num.} VM path pathid [andVTAM path pathid] will be deallocated.Gateway = gatelu [, Conversation =conid].

Explanation: The APPCVM RECEIVE or SETMODFYcommand failed due to a severe programming error.

System action: The VM path (and possibly the VTAMpath) is disabled.

Operator response: Note the return or IPAUDIT codeand when provided, the gatelu and conid. Report thisinformation along with the system response to theappropriate system personnel.

AGW373S APPCCMD CONTROL = ALLOCcommand failed. RTNCD = num, FDBK= num, RCPRI = num, RCSEC = num

Explanation: The APPCMD macro's ALLOC requestfailed because of a severe programming error.


Operator response: Report the system response andcorresponding return codes to the appropriate systempersonnel.

AGW374S APPCCMD CONTROL = DEALLOC,QUALIFY = {CONFIRM | DATAFLU}command failed. RTNCD = num, FDBK2= num, RCPRI = num, RCSEC = num.VTAM path pathid will be deallocated.Gateway = gatelu.

Explanation: The APPCCMD macro's DEALLOCrequest failed because of a severe programming error.

System action: The command fails, and the path willbe deallocated.

Operator response: Report the system response, returncode, and gatelu to the appropriate system personnel.

AGW375S {APPCCMD CONTROL = OPRCNTL,QUALIFY = CNOS command failed |SETLOGON command failed.} RTNCD= num, FDBK2 = num, RCPRI = num,RCSEC = num.

Explanation: Either the APPCCMD macro's OPRCNTLrequest, or the SETLOGON command failed because ofa severe programming error.


Operator response: Report the system response andcorresponding return codes to the appropriate systempersonnel.

AGW376S APPCCMD CONTROL = PREPRCV,QUALIFY = {CONFIRM | DATAFLU |FLUSH} command failed. RTNCD =num, FDBK2 = num, RCPRI = num,RCSEC = num. VTAM path pathid willbe deallocated. Gateway = gatelu

Explanation: The APPCCMD macro's PREPRCVrequest failed because of a severe programming error.

System action: The command fails, and the path willbe deallocated.

Operator response: Report the system response, thereturn code and the gatelu to the appropriate systempersonnel.

AGW377S APPCCMD CONTROL = {RECEIVE{command failed. Unable to receive PIPdata. |, QUALIFY = ANY commandfailed. | QUALIFY = SPEC commandfailed. Unable to receive log data.} |REJECT command failed.} RTNCD =num, FDBK2 = num, RCPRI = num,RCSEC = num. [VTAM path pathid willbe {deallocated. | rejected.}] [Gateway =gatelu] [, Conversation = conid]

Explanation: The APPCCMD macro's RECEIVE orREJECT request failed because of a severeprogramming error.

AGW370S • AGW377S



Operator response: Report the system response andcorresponding return code to the appropriate systempersonnel.

AGW378S APPCCMD CONTROL = SEND,QUALIFY = {CONFIRM | CONFRMD |DATA} command failed. RTNCD = num,FDBK2 = num, RCPRI = num, RCSEC =num. VTAM path pathid will bedeallocated. Gateway = gatelu.

Explanation: The APPCCMD macro's SEND requestfailed because of a severe programming error.

System action: The command fails and the VTAMpath will be deallocated.

Operator response: Report the system response, theRTNCD code, and the gatelu to the appropriate systempersonnel.

AGW379S APPCCMD, CONTROL = RCVFMH5command failed. RTNCD = num, FDBK2= num, RCPRI = num, RCSEC = num. Nopath established. Gateway = gatelu.

Explanation: The APPCCMD macro's RCVFMH5request failed because of a severe programming error.

System action: The command fails and the pathcannot be established.

Operator response: Report the system response, thereturn code, and the gatelu to the appropriate systempersonnel.

AGW380S Invalid APPC/VTAM commandrequested. Command code = code.VTAM path pathid and VM path pathidwill be deallocated. Gateway = gatelu.

Explanation: The VTAM path is deallocated as theresult of an invalid command request.

System action: The communication path and gatewaygatelu will be deallocated.

Operator response: Report the system response, gatelu,and pathid to the appropriate system personnel.

AGW381S {APPCVM | IUCVCOM} SEVERcommand failed on VM path pathid.{IPRCODE | RC} = num. Gateway =gatelu.

Explanation: A SEVER command failed. The specifiedVM pathway still exists.

System action: The SEVER command is ignored.

Operator response: Report the system response, theIPRCODE, and the gatelu to the appropriate systempersonnel.

AGW382S {APPCVM|IUCVCOM} CONNECT to{resource|service} id failed,{IPRCODE|RC} = num. VTAM pathpathid will be deallocated. Gateway =gatelu.

Explanation: APPC/VM or IUCVCOM was unable toexecute the CONNECT macro function. Return codepossibilities and explanations include:

v Target communicator is not logged on.

v Target has not invoked DCLBFR function.

v Maximum number of connections for this gatewayexceeded

v Connection unauthorized

v IUCV system name not valid.

System action: No connection is established.

Operator response: Use the displayed IPRCODE orreturn code to determine the problem and make thenecessary corrections.

AGW383S APPCVM SEND function failed on VMpath pathid, IPRCODE = num. VTAMpath pathid will be deallocated. Gateway= gatelu.

Explanation: APPC/VM was unable to execute theSEND macro function. Possible explanations include:

v Invalid path ID

v Path quiesced - SENDs not allowed

v Message limit exceeded

v Priority messages not allowed on this path

v Message length is negative


Operator response: Use the displayed IPRCODE todetermine the problem and make the necessarycorrections.

AGW384S {IUCV | IUCVCOM} ACCEPT functionfailed on VM path pathid, {IPRCODE |RC} = num. VTAM path pathid will bedeallocated. Gateway = gatelu.

Explanation: IUCV or IUCVCOM was unable toexecute the ACCEPT macro function. Possibleexplanations include:

v Connection is not pending on this path

v Originator has severed path


Operator response: Use the displayed IPRCODE orreturn code to determine the problem and make thenecessary corrections.


AGW388S Remote {userid userid|passwordpassword} is too long. VTAM path pathidwill be deallocated. Gateway = gatelu.

Explanation: This message is issued in the followingcases:

v The userid or password is greater than 10 characters(this is the architected length)

v An already verified userid that is 9 or 10 characters inlength has non-blank characters beyond character 8.

Additionally, for some applications (for example,private server), the system requires a correct user ID.For Security(PGM), a password is also required.

System action: The system will deallocate the VTAMpath.

Operator response: Enter the correct password or userID.

AGW389S APPCCMD CONTROL = RESETRCVcommand failed. RTNCD = num, FDBK2= num, RCPRI = num, RCSEC = num.Conversation = convid, Gateway = gatelu

Explanation: The RESETRCV parameter of theCONTROL macro failed due to a severe programmingerror.

System action: The command fails and the VTAMpath will be deallocated.

Operator response: Report the displayed return codes,system state, and gateway identifier to the appropriatesystem personnel.

AGW390E VTAM path specified by conversationmanager cmrname does not exist.Gateway gatelu will be deactivated.

Explanation: The conversation management routinerequested that AVS attempt to allocate a conversationfor which a corresponding VTAM path does not exist.AVS and the CMR no longer agree about what VTAMpaths are active, making further interactions betweenthis gateway and the CMR unreliable.

System action: The gateway will be quiesced. No newconversations will be accepted, and when the lastconversation ends, the gateway will be deactivated.

Operator response: Issue the ACTIVATE GATEWAYcommand to re-start the gateway gatelu and theconversation manager routine cmrname.

AGW391S APPCCMD CONTROL=SETSESScommand failed. Unable to {hold |release} session sessid. RTNCD = nn,FDBK2 = nn, RCPRI = nn, RCSEC = nn.VTAM path pathid will be deallocated.Gateway = gatelu.

Explanation: The APPCCMD macro's SETSESS faileddue to a programming error.

System action: The command fails and the session isdeallocated.

Operator response: Note the return codes and providethem, along with the dump, to the appropriate systempersonnel.

AGW392E Invalid completion flag fromconversation manager cmrname.

Explanation: The CMR has supplied an invalidcompletion flag to AVS on an inbound conversationfrom VTAM.

System action: The connection will be rejected withno further effect on the gateway or any existingconversations.

Operator response: A programming error exists in theCMR. Consult your system programmer or the vendorof the CMR.

AGW393E A network definition problem has beendetected. The length of a PIU exceededthe specified limit for gateway gatelu,remotelu remotelu, mode modename.VTAM path <pathid> will bedeallocated. Userid = userid,{Resource|Service} = id

Explanation: VTAM has reported a network definitionerror. Specifically, sense code X'800A0000' was returnedon a function issued on the VTAM path shown. Thissense code indicates that the length of a PIU that wastransmitted exceeded the maximum length allowed bya node in the path to the target LU. The maximumlength PIU that will be built is determined by theRUSIZES parameter in the logon mode name definitionfor the specified mode.

System action: The conversation is deallocated andthe associated session is deactivated. The PIU involvedis truncated, some of the data may be received by thepartner application.

Operator response: Report the system response to theappropriate system personnel.

Programmer response: Correct the mismatch betweenthe maximum length PIU that will be built and themaximum length PIU that the network can tolerate.This may be accomplished either by increasing thebuffer sizes on the link definition statements in thenetwork, or by decreasing the RUSIZES parameter ofthe logon mode name entry. For more informationabout the RUSIZES parameter of the logon mode nameentry and the various link definition statements thatdefine the maximum buffer size, refer to VTAMResource Definition Reference.

AGW388S • AGW393E


AGW400I A PDUMP is in progress on behalf ofthe following message

Explanation: The system displays the message thatcalled for a problem dump. DIAGNOSE code X'94'(VMDUMP) is used to take the dump of the AVSvirtual machine.

System action: The system continues to execute theproblem dump.


AGW401I A PDUMP could not be taken on behalfof the following message. The dumpcount was exceeded or abend is inprogress

Explanation: The system attempted to take a problemdump for the given message, but was unable to do sobecause of an exceeded dump count or an abend.DIAGNOSE code X'94' (VMDUMP) is used to take theproblem dump.

System action: The problem dump is not taken.

Operator response: Deliver this information to theappropriate system personnel. If you desire to allowmore AVS dumps, modify the AGWTUN ASSEMBLEfile. For more information about tuning AVS, refer toz/VM: Connectivity.

AGW440E Operand missing or invalid

Explanation: A missing or invalid operand wasentered.

System action: The command is ignored, and thesystem is ready for another.

Operator response: Correct or enter the appropriateoperand.

AGW441E Conflicting operand: operand

Explanation: The message occurs when the sameoption is specified twice in the same command, or thefunction required by the given option is incompatiblewith a previously specified operand.

System action: The command fails and the system isready for another.

Operator response: Re-enter the command with thecorrect operands.

AGW442E Address entered is not in AVS

Explanation: The address specified on the GDISPLAYMAPN command is not contained within AVS.


Operator response: Correct the address and re-enterthe command.

AGW443E Name entered was not found in AVS

Explanation: The name entered in the GDISPLAYMAPN command is not defined in AVS.


Operator response: Enter a correct name and re-issuethe command.

AGW444E AGWZAM table was not found

Explanation: The system was unable to locate theAGWZAM table in the dump data set.

System action: The command fails and the system isready for another.


AGW445E The pointer to the xxx is invalid

Explanation: AVS has encountered an invalid pointerin attempting to format the xxx block.

System action: The xxx block is not formatted.


AGW446E The pointer to the xxx was not found

Explanation: AVS cannot find a specific pointer in thedump when attempting to find the xxx block.

System action: The xxx block cannot be formatted.


AGW447E Trace table pointers invalid. Start = startEnd = end Current = current

Explanation: While attempting to display AVS tracetable entries, it was determined that the AVS trace tablepointers contained in the dump are invalid. Possiblecauses for this error include:

v The trace table start address indicates the trace tablebegins at zero.

v The trace table start address is greater than the tracetable end address.

v The current trace table address is outside of the tracetable.

v The current trace table address is not on a 16 byteboundary, or the trace table start address or trace endaddress is not on a page boundary.

v The trace table is less than a page in size.

System action: If a FROM location was specified, theprocessing of the subcommand will continue at theFROM location. The display will not wrap at the trace

AGW400I • AGW447E


table start position and will stop when:

v The specified count (or default count, if the countwas not specified) has been reached.

v The address of the next trace entry to display is lessthan or equal to zero.

If a FROM location was not specified, the processing ofthe subcommand will be terminated.

Operator response: If a FROM location was specified,ignore the message. If a FROM was not specified,determine the location of the trace table and reissue theTRACE subcommand with a FROM location specified.

AGW448E Page page not found in dump

Explanation: The virtual address identified in themessage was not found in the dump. This means it wasnot dumped at the time the dump was taken.

System action: The subcommand terminates andIPCSSCAN processing continues.


AGW449E Non-numeric character in count; retry

Explanation: The count field has non-numericcharacters.

System action: Subcommand terminates.

Operator response: Correct and re-issue thecommand.

AGW450E FROM location outside of trace tablerange: addr. Start = start End = endCurrent = current

Explanation: The FROM location specified on theTRACE subcommand of IPCSSCAN is not within thetrace table range.

System action: The TRACE subcommand terminates.IPCSSCAN processing continues.

Operator response: Reissue the TRACE subcommandwith the correct FROM location specified.

AGW451E FROM location is not a valid traceentry: addr

Explanation: The FROM location specified on theTRACE subcommand of IPCSSCAN is not a valid traceentry.

System action: The TRACE subcommand terminates.IPCSSCAN processing continues.

Operator response: Reissue the TRACE subcommandwith the correct FROM location.

AGW452E Invalid trace entry found at addr

Explanation: The data at location addr is not a validtrace table entry.


Operator response: If another message follows,respond to it. Otherwise, re-issue the subcommand,specifying a different address.

AGW453E Required resources are not available

Explanation: An error occurred while IPCS wasgetting work buffers to process the TRACEsubcommand.



AGW454E No trace entries found

Explanation: The TRACE subcommand did not findany trace entries at the specified address. This is causedby all or a portion of a trace entry being on a page thatis not present in the dump.


Operator response: Enter a TRACE subcommand withthe FROM option to return to the trace table.

AGW455E Attempted to go beyond storageboundary

Explanation: Either the TRACE subcommand with theSCROLL or SCROLLU operand, or the SCROLL orSCROLLU command was entered following a previoustrace table display that stopped at the end of storage.This means that the address of the next entry displaywould be negative. Since negative addresses areimpossible in a dump, no trace table data can bedisplayed.

System action: The system will stop processing thecommand and will not display any trace entries.

Operator response: Enter a TRACE subcommandwithout the SCROLL or SCROLLU operands.

AGW456E Unable to locate trace table pointers

Explanation: One of the following occurred:

v IPCS could not find the pointers in the load map, orthe map may be missing or invalid.

v The pointers are on a page that is not present in thedump.

System action: Subcommand terminates and tracetable wrapping is disabled.

Operator response: If the map is missing, make itavailable.


AGW457E Trace entry search stopped at addr1: Tosearch to lower dump addresses, tryaddress addr2. To search to higher dumpaddresses, try addresses addr3 addr4.

Explanation: IPCS found an invalid entry, and thereare no valid entries between the invalid entry specifiedat addr1 and the search end address.

System action: The command terminates.

Operator response: To continue looking for a traceentry, either issue the TRACE subcommand withFROM using addr2 or addr3, or, issue the TRACEsubcommand with the SCROLL operand (depending onthe information in the message and the direction inwhich you want to search).

Note: When searching toward the lower dumpaddresses by specifying FROM, the search proceedsfrom the FROM location toward the higher dumpaddresses. Therefore, the first entry found may not bethe entry with the highest address. To view all of thevalid entries that may be present, display the possiblevalid entry and scroll downward until an invalid traceentry is reached.

AGW458E Possible trace entry at addr1. Use theFROM operand to display the entry

Explanation: IPCS found an invalid entry, but found apossible valid entry at addr1.


Operator response: Issue a TRACE subcommand withthe address as the FROM location and a FOR count of1 to display the entry.

AGW459E Invalid trace entry found in CPTRAPfile

Explanation: The current CPTRAP entry beingformatted is not a valid trace entry. This could becaused if any part of the entry was not collected byCPTRAP.

System action: The system displays the entry in dumpformat without any formatting.


AGW460E Data field overlaps trailer record

Explanation: The address range of the specified inputfield overlaps either partially or completely the addressrange of the trailer record.

System action: Processing stops.

Operator response: Determine whether the input fieldor the trailer record is in error, and re-issue thecommand using the proper addresses.

AGW461E Formatted data entry exceeds maximumsize

Explanation: Either a SCROLL subcommand or aTRACE subcommand with the FORMAT option wasentered without the FOR count option - displaying atrace entry that is too big to fit on the screen.

System action: The output is truncated for thedisplayed entry and terminates the subcommand.

Operator response: View the entry by doing thefollowing:

* Note the address of the entry.* Issue a TRACE subcommand with the FROM

and FOR count options.

AGW462E Virtual storage exceeded

Explanation: The maximum amount of storage in yourvirtual machine was exceeded.


Operator response: Issue the CP DEFINE command toincrease the size of the virtual machine, IPL CMS again,and re-enter the command.

AGW463E Unable to list the control blockaddresses

Explanation: IPCS was unable to locate all of thespecified control block addresses. There may be morein the dump.

System action: Subcommand lists as many addressesas possible.


AGW464E The pointer to the named ordered list isinvalid

Explanation: IPCS has encountered an invalid AVSordered list pointer.


Operator response: Use the CP DISPLAY andLOCATE subcommands to try to locate the ordered list.

AGW465E The pointer to the named ordered listwas not found

Explanation: IPCS cannot find a pointer for the namedAVS ordered list.


Operator response: Use the CP DISPLAY andLOCATE subcommands to try to locate the ordered list.

AGW457E • AGW465E


AGW466E The gateway was not found.

Explanation: AVS was unable to locate a specifiedgateway.


Operator response: Re-enter the previous command,using the correct gateway name.

AGW500I AVS Accounting records are beingcreated

Explanation: Either the CP directory ACCT optionwas set, or a user-created exit (AGWACI) indicated thataccounting is active.

System action: Records are created.


AGW501W AVS Accounting was not started

Explanation: Either AVS cannot record active sessions(the ACCT DIRECTORY option is not activated), or inthe case of a user-created exit, the ACCT DIRECTORYoption IS activated.

System action: No records are created.

Operator response: If accounting is desired, activatethe ACCT DIRECTORY option. For user-created exit,verify that the ACCT DIRECTORY option is notactivated.

AGW502W AVS Accounting has ended

Explanation: The accounting function is complete.

System action: Records are available for review.


AGW503I Intermediate AVS Accounting Recordshave ended, a timer error has occurred.

Explanation: A timer error occurred when AVSaccounting tried to set the accounting interval.

System action: The intermediate AGWA-conversationactive records are discontinued. All other accountingwill continue.


AGW466E • AGW503I


DVF MessagesDVF execs issue messages having a module identifier that corresponds to theassociated exec. For example, the BLOCKMAP EXEC issues messages of the formHCSBKMnnnnt. Each exec and its associated three-character module identifier isshown in the following table:

Table 4. Execs and their associated modules

EXEC Name Module ID

BLOCKDEF BKD

BLOCKMAP BKM

CPEBK CPE

DVFXEDIT DVF

FINDCPE FIN

HC HCA

REAL REA

TIMEDIFF TIM

TODCLK TOD

VDATE VDA

VIEWSYM VSE

VIEWSYMP VSP

VIEWSYMU VSU

VIEWSYMX VSX

VIRT VIR

VTIME VTM

HCS010A ENTER TRACE ENTRY SELECTIONCRITERIA, NULL LINE TO ENDSELECTION, OR QUIT TO ENDTRACERED COMMAND

Explanation: You are being prompted for traceselection criteria to be used in TRACERED commandprocessing.

System action: The z/VM: Dump Viewing Facilitywaits for your response.

User response: Enter one of the responses describedunder

keyword value(s)To specify selection criteria

For TRSOURCE data, the only applicableselection criteria is TIME.

CMS To enter CMS subset mode

HELP To invoke the TRACERED help panel

QUIT To terminate the TRACERED command

(null line)To indicate that you have finished enteringcriteria and want to end prompting.

If you enter a null line as soon as you receive theprompt, TRACERED selects all trace entries. If youenter selection criteria, the system will continueprompting until you enter a null line to indicate thatyou have finished entering criteria. For details andusage notes on entering selection criteria using theSELECT option, refer to z/VM: Dump Viewing Facility.

HCS015A WILL YOU BE MOUNTING ANOTHERTRSAVE TAPE? ENTER YES OR NO

Explanation: TRACERED encountered end-of-volumeon the current trace input tape. If you enter YES,TRACERED:

1. Rewinds and unloads the current tape

2. Waits for the next tape mount.

If you enter NO, TRACERED completes processing.


User response: Enter one of the following:

YES if you want additional trace data to beprocessed.

HCS010A • HCS015A


NO if you don't want additional data to beprocessed.

HCS020E ‘operand1’ AND ‘operand2’ ARECONFLICTING KEYWORDOPERANDS

Explanation: You entered conflicting TRACEREDoperands (operand1 and operand2).

System action: The TRACERED command terminates.

User response: Specify operands that do not conflictand enter the TRACERED command again.

HCS021E TAPE DEVICE ADDRESS INVALID

Explanation: You specified an invalid tape deviceaddress when you entered the TRACERED command.Only virtual tape addresses 181 through 184 aresupported.


User response: Enter the TRACERED command again.Specify a tape device within the 181 through 184 range.

HCS030I PROCESSING TRSAVE TAPE - VOLSEQ # nn - CREATED mm/dd/yy hh:mm:ss

Explanation: The TRACERED command successfullyread the volume label of the current TRSAVE inputtrace tape. TRACERED identifies the sequence number(nn) and date the tape was created (mm/dd/yy).

System action: TRACERED processes trace entriesfrom the specified tape until encountering theend-of-volume.

User response: Message 015A appears whenend-of-volume is reached. You may end processing orcontinue with additional tape volumes.

HCS031I END OF TAPE ENCOUNTERED

Explanation: TRACERED has encountered theend-of-volume condition on the current input tape.

System action: The input tape is rewound.

User response: None.

HCS032I WAITING FOR TAPE MOUNT

Explanation: You replied “yes” when message 015Aasked if you wanted to mount a new TRSAVE tape.TRACERED is now waiting for the tape to be mounted.

System action: Once the input tape is mounted,TRACERED begins processing it.

User response: Instruct the operator to mount thedesired TRSAVE tape.

HCS040E TIME SELECTION RANGE MAY BESPECIFIED ONLY ONCE

Explanation: You entered more than one timeselection range when prompted for trace selectioncriteria. You may specify only one time selection rangefor a single TRACERED command.

System action: All of the selection criteria you enteredin response to previous prompts remain in effect.TRACERED ignores the selection criteria you specifiedin the most recent response and reprompts you foradditional trace selection criteria.


additional valuesto process additional data

(null line)to end the selection process

QUIT to terminate TRACERED processing.

HCS041E A MAXIMUM OF SIXTEEN CPUADDRESSES MAY BE SPECIFIED

Explanation: One of the following conditionsoccurred:

1. You entered more than 16 processor address valueswhen prompted for trace selection criteria. You maynot specify more than 16 processor address valuesfor one TRACERED command, although you mayspecify selection criteria on many different lines.

2. You entered more than 16 processor address valuesunder the SELECT subcommand of DUMPSCAN.You may not specify more than 16 processoraddress values for one SELECT subcommand,although you may specify selection criteria on manydifferent lines.

System action: Selection criteria that you enteredpreviously remain in effect. The selection criteriaspecified in your most recent response are ignored.

If TRACERED detects this condition, it reprompts youfor additional trace selection criteria.

User response: If TRACERED detects this condition,you may enter additional trace selection criteria or anull line to end the selection process.

If SELECT detects this condition, you may reenterselection criteria, enter another subcommand, or quitDUMPSCAN processing.

HCS042E A MAXIMUM OF SIXTEEN TRACECODES MAY BE SPECIFIED


1. You entered more than 16 trace code values whenprompted for trace selection criteria. You may notspecify more than 16 trace code values for one

HCS020E • HCS042E


TRACERED command, although you may specifyselection criteria on many different lines.

2. You entered more than 16 trace code values underthe SELECT subcommand of DUMPSCAN. Youmay not specify more than 16 trace code values forone SELECT subcommand, although you mayspecify selection criteria on many different lines.


If TRACERED detected this condition, it reprompts youfor additional trace selection criteria.

User response: If TRACERED detected this condition,you may enter additional trace selection criteria or anull line to end the selection process.

If SELECT detected this condition, you may reenterselection criteria, enter another subcommand, or quitDUMPSCAN processing.

HCS043E A MAXIMUM OF SIXTEEN VMDBKADDRESSES MAY BE SPECIFIED


1. You entered more than 16 VMDBK address valueswhen prompted for trace selection criteria. You maynot specify more than 16 VMDBK address valuesfor one TRACERED command, although you mayspecify selection criteria on many different lines.

2. You entered more than 16 VMDBK address valuesunder the SELECT subcommand of DUMPSCAN.You may not specify more than 16 VMDBK addressvalues for one SELECT subcommand, although youmay specify selection criteria on many differentlines.





HCS044E A MAXIMUM OF SIXTEEN RDEVNUMBERS MAY BE SPECIFIED


1. You entered more than 16 RDEV values whenprompted for trace selection criteria. You may notspecify more than 16 RDEV values for one

TRACERED command, although you may specifyselection criteria on many different lines.

2. You entered more than 16 RDEV values under theSELECT subcommand of DUMPSCAN. You maynot specify more than 16 RDEV values for oneSELECT subcommand, although you may specifyselection criteria on many different lines.





HCS045E A MAXIMUM OF SIXTEEN VDEVNUMBERS MAY BE SPECIFIED


1. You entered more than 16 VDEV values whenprompted for trace selection criteria. You may notspecify more than 16 VDEV values for oneTRACERED command, although you may specifyselection criteria on many different lines.

2. You entered more than 16 VDEV values under theSELECT subcommand of DUMPSCAN. You maynot specify more than 16 VDEV values for oneSELECT subcommand, although you may specifyselection criteria on many different lines.





HCS046E A MAXIMUM OF SIXTEEN USERIDSMAY BE SPECIFIED

Explanation: You entered more than 16 USERIDvalues under the SELECT subcommand ofDUMPSCAN. You may not specify more than 16USERID values for one SELECT subcommand,although you may specify selection criteria on manydifferent lines.

HCS043E • HCS046E



User response: You may reenter selection criteria,enter another subcommand, or quit DUMPSCANprocessing.

HCS049E LEADING ZEROS REQUIRED FORCODE SELECTION VALUE ‘value’


1. You entered a CODE value without leading zeros inresponse to the prompt for trace selection criteria onthe TRACERED command. TRACERED requires a4-digit trace selection code with leading zeros.

2. You entered a CODE value without leading zeros asan operand on the SELECT subcommand ofDUMPSCAN. SELECT requires a 4-digit traceselection code with leading zeros.



User response: If TRACERED detected this condition,you may reenter the trace code value with leadingzeros. To end the selection process, enter a null line.

If SELECT detected this condition, you may reenter theSELECT subcommand, specifying the trace code valuewith leading zeros.

HCS050E ‘value’ IS NOT A VALID SELECTIONVALUE


1. You entered an invalid value when TRACEREDprompted you for trace selection criteria.

2. You entered an invalid value on the SELECTsubcommand of DUMPSCAN.



User response: If TRACERED detected this condition,you may enter additional values. To end the selectionprocess, enter a null line.

If SELECT detected this condition, reenter the SELECTsubcommand with valid selection criteria.

HCS051E THE KEYWORD OPERAND ‘value’WAS NOT PREVIOUSLY SELECTED

Explanation: You did not previously select thespecified value, so you may not reset it.

System action: Selection criteria that you enteredpreviously remain in effect. SELECT ignores the resetcriteria in your most recent response.

User response: Reenter the SELECT subcommand ofDUMPSCAN with the QUERY keyword. Verify theselection criteria that you want to reset. Enter either therevised request, another DUMPSCAN subcommand, orQUIT.

HCS052E CP SELECTION KEYWORD(S)SPECIFIED FOR GUEST TRACETABLES - KEYWORD(S) IGNORED

Explanation: You specified a selection keyword that isnot valid for guest trace tables.

System action: TRACERED ignores all CP selectionkeywords. TRACERED reprompts you for a validkeyword.

User response: Enter the valid keyword (TIME). Toend the prompt, enter a null line.

HCS060E TAPE WAS NOT CREATED BY THETRSAVE COMMAND

Explanation: The input tape does not contain a validvolume label created by the TRSAVE command.

System action: The system rewinds the input tape andallows you to mount another tape.

User response: To process additional trace data,specify an input tape created by the TRSAVEcommand.

HCS061E TAPE vdev IS NOT ATTACHED

Explanation: The virtual tape device specified in thismessage is not attached to your virtual machine.


User response: Attach a real tape device to yourvirtual machine as indicated by the virtual deviceaddress variable. Make sure your TRSAVE input tape ismounted, and reenter the TRACERED command.

HCS062E PERMANENT TAPE I/O ERROR

Explanation: A permanent I/O error occurred whileTRACERED was reading the TRSAVE input tape.


User response: Ask the operator to take correctiveaction to avoid the I/O error. Reenter the TRACERED

HCS049E • HCS062E


command. If the problem persists, contact IBM servicepersonnel.

HCS070I NO TRACE ENTRIES FOUNDMEETING THE REQUESTEDSELECTION CRITERIA

Explanation: The TRACERED command or theTRACE subcommand of DUMPSCAN successfullyprocessed the current TRSAVE input tape or tracetable(s) in the dump file, but no trace entries met theselection criteria you specified.

System action: For TRACERED, the system allowsyou to mount another TRSAVE input tape or to endTRACERED command processing. Subcommandprocessing continues for TRACE. You may enteranother subcommand or quit DUMPSCAN processing.

User response: If you are using the TRACEREDcommand, check the selection criteria you specified inresponse to the 010A prompt. For both TRACERED andTRACE, verify that you entered the data reductionvalues correctly.

If you entered the correct values for TRACERED,reenter that command. Specify a different set ofselection criteria when you respond to the 010A prompton TRACERED. Or, mount a tape created in anothertime interval and issue the TRACERED command withthe same selection criteria.

For TRACE, verify the selection criteria that youspecified with the SELECT subcommand. If youexpected trace entries to meet your selection criteria,verify the data reduction values. If you entered thosevalues correctly, reenter the SELECT subcommand witha different set of selection criteria and enter the TRACEsubcommand again.

HCS071I ONE OR MORE TRACE ENTRIESMISSING FROM TRSAVETAPE(S)--VOL SEQ # nn

Explanation: While processing TRSAVE input tapes,TRACERED encountered records indicating that traceentries were missing. Missing entries occur when tracetable entries wrap faster than CP can write the entriesto an output device or file. The wrapping situation isrecorded in TRACERED print or CMS output files withthe CPU address from which the data was lost. Normalprocessing continues with the next available trace entryfrom that processor.

System action: Command processing continues.

User response: Examine the TRACERED output bychecking the TRACERED print or CMS output files. Allrecords identifying lost data are preceded and followedby a blank line.

HCS074E THE SYSTEM TRACE FILE NAME‘filename’ WAS NOT FOUND

Explanation: TRACERED could not find the systemtrace file you specified.

System action: Command processing terminates.

User response: Use the QUERY TRFILES command toverify the system trace file name.

HCS075E ERROR{OPENING|READING|CLOSING}CMS TRACE FILE filename filetype

Explanation: TRACERED received an error during anopen, read, or close of a CMS trace file.


User response: For an explanation of CMS FSxxxxmacro return codes, refer to z/VM: CMS Macros andFunctions Reference.

HCS076E THE OPERAND GTRACE IS NOTVALID FOR CP TRACE TABLE DATA

Explanation: You requested that TRACERED producean output file in OS QSAM format containing guestvirtual machine recorded trace events, but youspecified an input file containing CP trace table datarather than guest trace data defined by TRSOURCE.

System action: TRACERED command processing isrejected.

User response: Reenter the TRACERED command,specifying the correct input file. Use the QUERYTRFILES command to determine the spool ID of thesystem trace file containing the GCS GTRACE recordsyou want to process.

HCS077E THE OPERAND GTRACE IS NOTVALID FOR I/O OR DATA TRSOURCETRACES

Explanation: You requested that TRACERED producean output file in OS QSAM format containing guestvirtual machine recorded trace events, but youspecified an input file containing TRSOURCE definedI/O or DATA type trace data rather than guest tracedata also defined by TRSOURCE.

System action: TRACERED command processing isrejected.

User response: Reenter the TRACERED command,specifying the correct input file. Use the QUERYTRFILES command to determine the spool ID of thesystem trace file containing the GCS GTRACE recordsyou want to process.


HCS078I PROCESSING CMS TRACE FILE(S)FOR filename filetype filemode

Explanation: TRACERED is processing the file forfilename filetype filemode.

System action: TRACERED processes trace entriesfrom the specified CMS trace file.


HCS079E CMS TRACE FILE filename filetypefilemode WAS NOT FOUND

Explanation: TRACERED could not find the CMStrace file that was specified.


User response: Verify the filename filetype filemode ofthe referenced CMS trace file.

HCS080E DUPLICATE INPUT SYSTEM TRACEFILES WERE SPECIFIED


1. You entered two identical file names or spool IDs

2. You entered a spool ID and then a file name, butthe spool ID was within a set designated by the filename.


User response: Reenter the TRACERED commandwith correct input.

HCS081E SYSTEM TRACE FILE spoolid ISINVALID

Explanation: You entered an invalid system trace filespool ID for the TRACERED command. The parametermust be a decimal number from 1 to 9999 for the spoolID.


User response: Use the QUERY TRFILES command tofind the associated file name. Reenter the TRACEREDcommand with a valid spool ID.

HCS082E ERROR{OPENING|READING|CLOSING}SYSTEM TRACE FILE spoolid, CODE nn

Explanation: TRACERED received an error during anopen, read, or close of a system trace file.


User response: For an explanation of diagnose codeX'E0', refer to z/VM: CP Commands and UtilitiesReference.

HCS083I PROCESSING SYSTEM TRACE FILESspoolid CREATED mm/dd hh:mm:ss

Explanation: TRACERED is processing the file forspoolid.

System action: TRACERED processes trace entriesfrom the specified system file.


HCS084I PROCESSING COMPLETE - nnnnnnnnTRACE ENTRIES FORMATTED

Explanation: The TRACERED command has finishedprocessing. nnnnnnnn specifies the total number oftrace entries processed by the TRACERED command.

System action: Command processing completesnormally.


HCS085I SYSTEM TRACE FILENAME ‘filename’HAS FILES FROM MORE THAN ONEORIGINATOR.

Explanation: The file name entered was created bytwo different originators.



Commands That Detect Condition: TRACERED

HCS086E SYSTEM TRACE FILE spoolid ISCURRENTLY IN USE

Explanation: TRACERED attempted a DIAGNOSEX'E0' OPEN and failed on the specific system trace filebecause it was in use.


User response: Enter the QUERY TRSAVE commandto determine whether tracing is still active and whetherthe specific system trace file you requested is still inuse. If the file is still in use and you want to processimmediately, set TRSAVE OFF for that user. Afterprocessing, you may turn TRSAVE on for the user,specifying a different file name. Reenter theTRACERED command for that user.

HCS087I INVALID TRACE ENTRY LENGTHFOUND IN SYSTEM TRACE FILESPOOLID spoolid

Explanation: The length field for a trace entry withina system trace file is not invalid. TRACERED expectsthe first two bytes of IO, DATA, and guest trace entriesto contain the length of its trace data, including itslength field. A length of two or less is considered notvalid.

HCS078I • HCS087I


System action: All trace entries previously processedon this invocation of TRACERED are saved. The blockof trace entries in which the invalid length exists isignored. TRACERED attempts to continue reading inblocks of trace entries if they exist, and processingcontinues.

User response: When a program uses the DIAGNOSEcode X'E0' interface for writing blocks of trace data, thefirst two bytes of each trace entry recorded mustcontain a length definition. DIAGNOSE code X'E0'writes are permitted after the TRSOURCE command isenabled for guest trace data and block mode isspecified.

HCS088E THE SYSTEM TRACE FILE SPOOLID‘spoolid’ WAS NOT FOUND

Explanation: TRACERED could not find the systemtrace file spool ID you specified.


User response: Use the QUERY TRFILES command toverify the spool ID of the referenced system trace file.

HCS089E ONLY ONE CP TAPE OR CP SYSTEMTRACE FILE IS ALLOWED

Explanation: You may merge a total of five systemtrace files, but you may only include one CP systemtrace file or tape. You need to specify one of thefollowing:

v One CP system trace file with up to four TRSOURCEsystem trace files

v One CP tape with up to four TRSOURCE systemtrace files

v Up to five TRSOURCE system trace files.


User response: Reenter the TRACERED command andspecify only one CP tape or file.

HCS090E DUPLICATE KEYWORDS WERESPECIFIED

Explanation: You entered a duplicate keyword in theTRACERED command, or you entered the TIMEselection keyword twice.

System action: Processing ends if you specified aduplicate keyword in the TRACERED command.Processing continues for selection criteria. TRACEREDignores current time parameters.

User response: Reenter the TRACERED command.Omit the duplicate keyword, or continue enteringselection criteria.

HCS091I ONE OR MORE TRACE ENTRIESMISSING FROM SYSTEM TRACEFILE(S) FOR spoolid

Explanation: While processing system trace files,TRACERED encountered records indicating that traceentries were missing. Missing entries occur when tracetable entries wrap faster than CP can write the entriesto an output device or file. The wrapping situation isrecorded in TRACERED print or CMS output files withthe CPU address from which the data was lost. Normalprocessing continues with the next available trace entryfrom that processor.


User response: Examine the TRACERED output bychecking the TRACERED print or CMS output files. Allrecords identifying lost data are preceded and followedby a blank line.

HCS092I TIME ZONES ARE DIFFERENT FORSPOOLID spoolid. FILE IS NOTPROCESSED

Explanation: You cannot merge files that were createdin different time zones.


User response: Reenter the TRACERED commandwith files from the same time zone.

HCS093I TIME ZONES ARE DIFFERENT FORTAPE - VOL SEQ# nn. FILE IS NOTPROCESSED.

Explanation: You cannot merge a tape and a file thatwere created in different time zones.



HCS094E THE STARTING DATE AND TIMEMUST BE LESS THAN THE ENDINGDATE AND TIME

Explanation: The starting date or time that youspecified is later than the ending date or time.

System action: TRACERED prompts you for newselection criteria.

User response: Reenter the TIME keyword and astarting date that is earlier than the ending date. Entera null line to end the prompt.


HCS095E THE SYSTEM TRACE FILE SPOOLID‘spoolid’ WAS NOT FOUND WITHINFILENAME ‘filename’

Explanation: You specified a spool ID that is notassociated with the file filename.


User response: Use the QUERY TRFILES command toverify the spool ID of the referenced system trace file.

HCS096E RE-IPL CMS. TRACERED HAD ASEVERE ERROR

Explanation: An I/O error occurred while TRACEREDwas writing to a file.


User response: Re-IPL CMS and reenter theTRACERED command.

HCS097E THE ORIGINID 'userid' WAS NOTFOUND WITHIN FILENAME 'filename'

Explanation: You specified a system trace file namewith a user ID as input to the TRACERED command,and that user ID is not associated with the file name.

System action: Command processing is terminated.

User response: You can verify the user ID of thereferenced system trace file by using the QUERYTRFILES command.

HCS098E THE SYSTEM TRACE FILE SPOOLID‘spoolid’ WAS NOT FOUND WITHINORIGINID ‘userid’

Explanation: You issued the TRACERED command inthe form NAME fn ORIG userid. The id that representsa spool ID is associated with the file name but not thisuser ID.

System action: Command processing is terminated.

User response: Use the QUERY TRFILES command toverify the spoolid of the referenced system trace file.

HCS099I TIME ZONES ARE DIFFERENT FORCMS TRACE FILES filename filetype.FILE IS NOT PROCESSED

Explanation: You cannot merge files that were createdin different time zones.



HCS110E THE FILE NAME ‘filename’ IS NOTVALID

Explanation: For ADDMAP, DUMPSCAN, orPRTDUMP, the dump file name entered is not valid. Ifin MAP mode, the file name entered is not valid.Acceptable file names are the file names for a CMS file:a 1- to 8-character string with the characters limited to0-9, A-Z, #, @, +, -, _, :, and $.

System action: If in ADDMAP, DUMPSCAN, orPRTDUMP mode, the message 120A is issued toprompt you for the correct name of the CMS filecontaining the dump. If in MAP mode, either message121A or 122A is issued to prompt you for the correctname of the CMS file containing either the load map orthe module map.

User response: If in ADDMAP, DUMPSCAN, orPRTDUMP mode, enter the correct dump file name. Ifin MAP mode, enter either the correct load map ormodule map name.

HCS111E THE FILE TYPE filetype IS NOT VALID

Explanation: The dump file type entered is not valid.Only CMS file types are acceptable. Valid CMS filetypes consist of a 1- to 8-character string from thecharacters 0-9,A-Z,#,@,+,-, _,:, and $.

System action: The message HCS120A will be issuedto prompt you for the correct file identifier of the CMSfile containing the dump.

User response: Enter the correct file identifier.

HCS112E FILENAME FILETYPE SPECIFIED ONDUMPSCAN SUBCOMMANDDUPLICATES AN EXISTINGDUMPSCAN SESSION, DUMPSCANSUBCOMMAND FAILED

Explanation: User entered the DUMPSCANsubcommand specifying a dump file with the same filename and file type as a dump file that is already in theDUMPSCAN file ring, but its file mode is different. Thesame dump file ID is located on at least two accesseddisks.

System action: DUMPSCAN subcommand processingterminates.

User response: Respond with one of the following:

v Enter the DUMPSCAN subcommand again withoutspecifying a file mode to return to the existingDUMPSCAN session (if you are not alreadypositioned there).

v Quit from the duplicate dump DUMPSCAN session.Then enter the DUMPSCAN subcommand again forthe dump file name, file type, and file mode youwish to view.

HCS095E • HCS112E


HCS120A ENTER DUMP FILE IDENTIFIER INTHE FORM FILENAME, ORFILENAME FILETYPE, OR FILENAMEFILETYPE FILEMODE

Explanation: A command was issued to process aspecific dump file, and you are being asked to specifywhich file you wish to process.


User response: Specify a valid dump file ID tocontinue command processing, or enter HX toterminate the command.

HCS121A ENTER THE FILENAME FILETYPEFILEMODE OF THE INPUT type LOADMAP, A NULL LINE, SUBSET OR HX

Explanation: You are prompted for the file name, filetype, and file mode of an input load map to process.The variable type refers to a type of load map. For a listof supported types and their default file IDs, see theMAP command.

If MAP cannot find the file you specify, it repeats thisprompt.

System action: The dump viewing facility waits for aresponse.

User response: Choose one of the following:

1. To accept the default file ID, enter a null line.

2. To process a specific file, enter the file ID.

3. To invoke CMS subset mode, enter SUBSET.

4. To terminate the MAP command, enter HX.

HCS122A ENTER THE FILENAME FILETYPEFILEMODE OF THE OUTPUT typeMODULE MAP, A NULL LINE,SUBSET, OR HX

Explanation: You are prompted for the file name, filetype, and file mode that will contain the createdmodule map. The variable type refers to a type ofmodule map. For a list of supported types and theirdefault file IDs, see the MAP command.

System action: The dump viewing facility waits for aresponse.


1. To accept the default file ID, enter a null line.

2. To process a specific file, enter the file ID.



HCS123A ENTER THE MAP TYPE, A NULLLINE, SUBSET, OR HX

Explanation: You entered the MAP PROMPT or MAPcommand. The z/VM: Dump Viewing Facility wants toknow what type of module map to create. For a list ofsupported types and their default file IDs, see the MAPcommand.

System action: The z/VM: Dump Viewing Facilitywaits for a response.


1. To accept the default type (CP), enter a null line.

2. To create a specific type of module map, enter thetype.



HCS130E THE type FILE filename filetype filemodeWAS NOT FOUND

Explanation: You specified a file to process, and thez/VM: Dump Viewing Facility couldn't find that file.For MAP, type indicates a type of load map. See theMAP command for a list of types.

For VREG, VPAIR, or VSTAT processing, you wereprocessing a dump other than the primary. Theprimary dump that contains the vector facility datacould not be located on any accessed disk.

System action: Depending on the command youissued, command processing terminates or the z/VM:Dump Viewing Facility prompts you for the correct fileID.

User response: Verify the name of the file you wish toprocess. Also verify you are currently accessing thedisk in which the file resides. If prompted, enter thecorrect file ID. Otherwise, enter the command againwith the correct file ID.

HCS135E THE FILE filename filetype filemodeALREADY EXISTS

Explanation: The output file specified on thecommand exists already.

System action: If you included the specified fileidentifier in the TRACERED or MAP command, thecommand terminates. If you entered the specified fileID as a response to a MAP prompt, you arereprompted for another file ID.

User response: Check to see that you typed the file IDcorrectly. If you did not enter the file ID correctly, do soon either the TRACERED or MAP command line or inresponse to the MAP prompt. If you did enter the fileID correctly, try renaming the file and reentering thecommand or response.

HCS120A • HCS135E


HCS140E THE FILE filename filetype filemode ISNOT A VALID type FILE

Explanation: The specified file does not contain validdata for the specified type of file.


User response: Verify the file ID. Enter the correct fileID or a new command.

HCS141E FIRST MODULE'S NAME IN LOADMAP filename filetype filemode IS NOTTHE SAME AS THE FIRST MODULENAME SPECIFIED IN THE TABLE

Explanation: The first module name in the specifiedfile is not the same as the first module name for thedump type entry specified in the HCSTAB table.


User response: Verify that the file is a load map. If itis, then change the first module field for the entry ofthe dump type in HCSTAB to the actual first module'sname in the load map file. The changing of HCSTABshould be done by changing the FMODNAME operandin the coded TABENTRY assembler macro invocationfor the dump type entry within the HCSTAB file. If youare using the MAP syntax where you specify all the fileIds on one line, make sure the file Ids are in the correctorder.

HCS145E THE DUMP FILE REQUESTED IS NOTA VALID DUMP

Explanation: The specified dump file was not a validCP or virtual machine dump.


User response: Reenter the command with the correctfile name.

HCS148I STORAGE ADDRESSES FROM addr1TO addr2 ARE MISSING FROM THEDUMP

Explanation: The dump truncated and some pages aremissing. The addr1 is the first missing storage address,and addr2 is the highest possible address if the dumpdid not truncate.


User response: Continue working with the dump. Themissing pages are not available, but the remainder ofthe pages are available for normal processing.

HCS150I THE type FILE filename filetype filemode ISINCOMPLETE

Explanation: The file that you specified was notcomplete.

System action: For ADDMAP, processing terminates.For DUMPSCAN and PRTDUMP, processing continues.

User response: Reenter the command with the full filename, file type, and file mode.

HCS151I LAST MODULE'S NAME IN LOADMAP filename filetype filemode IS NOTTHE SAME AS THE LAST MODULENAME SPECIFIED IN THE TABLE

Explanation: The last module name in the specifiedfile is not the same as the last module name for thedump type entry specified in the HCSTAB table.


User response: Verify that the file is a load map. If itis, then change the last module field for the entry ofthe dump type in HCSTAB to the actual first module'sname in the load map file. The changing of HCSTABshould be done by changing the LMODNAME operandin the coded TABENTRY assembler macro invocationfor the dump type entry within the HCSTAB file.

HCS200I PROCESSING FILE filename filetypefilemode

Explanation: DUMPSCAN issues this message foreach dump being viewed in the session.



HCS210I THE SUMMARY REPORTS HAVEBEEN PRINTED FOR FILE filenamefiletype filemode

Explanation: The PRTDUMP command has finishedprocessing the specified dump file.



HCS220I THE type SUMMARY REPORT IS NOTCOMPLETE; SEE REPORT FORDETAILS

Explanation: An error was encountered in thePRTDUMP processing of the specified summary report,and it was not possible to print the entire summaryreport. The type variable can be any of the following:

FRMTB

FRAMETBL

MAP

HCS140E • HCS220I


PROCESSOR

RIOBLOK

SYMPTOM

TRACE

USER

VMDBK

DUMPID

System action: The system continues printing otherdump data.

User response: Refer to the printed summary reportfor the detailed reasons why the summary report wasnot complete.

HCS230A DO YOU WANT PRINTING TOCONTINUE? ENTER YES OR NO

Explanation: A condition has been detected that mightcause you not to want the dump summary reportsprinted. This message is preceded by another message,which explains the condition. You have the choice ofwhether or not to continue printing the dumpsummary reports.

System action: If you enter an invalid response, theprompt is reissued. If you respond YES, commandprocessing continues. If you respond NO, commandprocessing terminates.

User response: You must say whether the printing ofthe dump summary reports should continue. Validresponses are YES or NO.

HCS240E ACCESS LIST ENTRIES ARE INdumpname DUMP0001, WHICH IS NOTON ANY ACCESSED DISK

Explanation: The access lists are in virtual machinedumps that are created with the file type ofDUMP0001. While trying to read dump DUMP0001, itcould not be located on any accessed disks.

System action: The subcommand ends andDUMPSCAN waits for you to enter anothersubcommand.

User response: Access the disk that contains theDUMP0001 file and retry the ACCLIST subcommand.

HCS241I THE HOST ACCESS LIST IS EMPTY

Explanation: You have requested host access listinformation for an address space where the host accesslist is empty. Either it was never used or it containedonly deleted entries.


User response: Enter a new subcommand.

HCS242I THE HOST ACCESS LIST IS NOTAVAILABLE FOR SPACE spaceid

Explanation: You have requested access listinformation for an address space when the host accesslist status was one of the following:

v Not accessible. (This address space was no longeraccessible when virtual machine dump processingtried to dump its access lists.)

v Not included in virtual machine dump. (Host accesslists are only dumped for an address space if it is theprimary address space of one or more virtualprocessors in the dump.)



HCS244E THE ADDRESS SPACEINFORMATION WAS NOT FOUND INdumpname dumptype

Explanation: The address space information should bein every virtual machine dump. There is either aproblem with a CMS file, or there is a virtual machinedump processing error.

System action: If ALL was specified, the subcommandwill continue to process the related dumps. Otherwise,the subcommand ends.

User response: Notify your system programmer.

HCS250I THE EXTRACTION ROUTINE routineFOR type COULD NOT BE FOUND

Explanation: The z/VM: Dump Viewing Facility couldnot find the specified routine on any disk that youhave accessed.

System action: DUMPSCAN and PRTDUMP do nottake a user exit. No information will be extracted fromor added to the dump.

User response: Verify the name of the file you want touse. Also verify that it is located on a disk you haveaccessed. See the HCSTBL ASSEMBLE file forsupported dump types and the extraction routineassociated with each type.

HCS260I THE FORMATTING ROUTINE routineFOR type COULD NOT BE FOUND

Explanation: The z/VM: Dump Viewing Facility couldnot find the specified routine on any disk that youhave accessed.

System action: DUMPSCAN and PRTDUMP do nottake a user exit. You may not enter licensed programproduct subcommands.

User response: Verify the name of the file you want to

HCS230A • HCS260I


use. Also verify that it is located on a disk you haveaccessed. See the HCSTBL ASSEMBLE file forsupported dump types and the formatting routinenames associated with each type.

HCS265I PRINTING DUMP STORAGESUPPORTED IN PRTDUMP FORVIRTUAL MACHINE DUMPS OF TYPEFILE ONLY

Explanation: You have tried to print a formatteddump from 0 to the end with a program productformatting routine. This is supported only by thez/VM: Dump Viewing Facility for virtual machinedumps having the FILE virtual machine typedesignation. For more information about the FORMAToperand of the VMDUMP command, refer to z/VM: CPCommands and Utilities Reference.

System action: The load maps, registers, and PSW areprinted.

User response: Use the FORMAT subcommand ofDUMPSCAN to change the type of virtual machinedump to the default type of FILE. Then enter thePRTDUMP command again with the STORAGEoperand to print out the dumped storage. When thePRTDUMP command has completed successfully, enterthe FORMAT subcommand of DUMPSCAN again tochange the dump format back to its original typedesignation.

HCS266I THE ROUTINE routine_name FOR spoolidCANNOT BE FOUND

Explanation: The user exit necessary for trace fileprocessing was not found.

System action: Processing continues. If the missingexit routine is a merge/selection exit, the trace record isconsidered to have no timestamp. If records are beingselected by time or if multiple traces are being merged,the record is not selected. Otherwise, the record isselected for processing.

If the missing exit routine is a formatting exit, the tracerecord is output in a default hexadecimal format.

Note: This message will only appear once for eachroutine missing. There may be other SPIDs requiringthis routine.

User response: Run the TRACERED command againafter accessing the disks that contain the required exits.

HCS267I THE ROUTINE routine_name FOR CMSTRACE FILE filename filetype CANNOTBE FOUND

Explanation: The user exit necessary for trace fileprocessing was not found.

System action: Processing continues. If the missing

exit routine is a merge/selection exit, the trace record isconsidered to have no timestamp. If records are beingselected by time or if multiple traces are being merged,the record is not selected. Otherwise, the record isselected for processing.

If the missing exit routine is a formatting exit, the tracerecord is output in a default hexadecimal format.

Note: This message will only appear once for eachroutine missing. There may be other CMS TRACEFILES requiring this routine.

User response: Run the TRACERED command againafter accessing the disks that contain the required exits.

HCS270I ROUTINE routine RETURNED CODEcode WHILE PROCESSINGSUBCOMMAND subcommand

Explanation: You entered a subcommand that washandled by an external formatting routine. This routinedetected an error while processing this subcommand.

System action: After issuing the message,DUMPSCAN waits for you to enter anothersubcommand.

User response: Continue to analyze the dump byentering a new subcommand.

HCS300I THE DUMP HAS NO MODULE MAP

Explanation: A module map was not found at the endof the dump file currently being processed.

System action: If the FINDMOD subcommand wasissued, subcommand processing is terminated, and thez/VM: Dump Viewing Facility waits for a newsubcommand to be entered.

If the PRTDUMP command was issued, printing ofother dump data will continue. A note is printed in theoutput indicating that the module map was notavailable.

User response: The ADDMAP command may be usedto append a module map to the dump file.

HCS301I DUMP filename filetype filemodeALREADY HAS A MODULE MAP

Explanation: The specified dump file already has anappended module map.

System action: Message 302A is issued.


HCS302A DO YOU WANT TO REPLACE THEPREVIOUS MAP? ENTER YES OR NO

Explanation: You are attempting to add a map to adump that already has a map appended. You have the

HCS265I • HCS302A


option of replacing the pointer to the old map with apointer to the new map.



YES Append the new map to the dump andupdate the pointer.

NO Terminate the ADDMAP command.

Any other responseReprompt.

HCS304E THE MODULE MAP CANNOT BEAPPENDED TO A type DUMP

Explanation: You tried to append a module map to adump of the type specified. The type is a soft abend.



HCS305I THE FORMAT OF THE DUMP IS NOTSUPPORTED BY THIS PROGRAM.USE VM DUMP TOOL INSTEAD.

Explanation: A dump was taken that is not supportedby the z/VM Dump Viewing Facility.

System action: The user is returned to the commandline.

User response: Use VM DUMP TOOL to work withthe dump. For more information, refer to z/VM: VMDump Tool.

HCS310E THE FILES filename filetype filemode ANDfilename filetype filemode AREINCOMPATIBLE

Explanation: The dump file and the module map filerepresent two different levels of the system.


User response: Verify that the correct file IDs werespecified.

HCS311E THE type1 MODULE MAP FILE filenamefiletype filemode DOES NOT MATCHTHE type2 DUMP filename filetypefilemode

Explanation: The type of the module map to beappended does not match the type of the dump. Thetype1 variable is a CP, CMS, PVM, or RSCS modulemap, and type2 is the dump file type.

System action: Command processing terminates, andthe module map is not appended to the dump.

User response: Verify that the correct file IDs werespecified on the command. Reenter the command with

the correct files specified or enter another command.

HCS315E THE LOAD MAP filename filetype filemodeOVERLAPS A PREVIOUS MAP

Explanation: The address range of the PVM inputload map overlaps either partially or completely theaddress range of the previously included CMS nucleusload map in the output z/VM: Dump Viewing Facilitymodule map.

System action: Command processing terminates andthe module map is not created.

User response: Reenter the command with the properinput load maps.

HCS320I THE MODULE MAP filename filetypefilemode HAS BEEN CREATED FROMLOAD MAP filename filetype filemode

Explanation: The module map has been successfullycreated from the input load map.

System action: Command processing is finished.


HCS321I THE MAP filename filetype filemode HASBEEN APPENDED TO DUMP filename

Explanation: The module map has been successfullyappended to the dump indicated.

System action: Command processing is finished.


HCS330I THE INPUT type LOAD MAP NAME ISfilename filetype filemode

Explanation: You entered a null line when MAPprompted you for a load map name. MAP used thedefault file ID for the specified type of map. See theMAP command for a list of map types and theirassociated file IDs.


User response: Continue or terminate commandprocessing.

HCS331I MAP TYPE IS CMS

Explanation: You entered a null line in response toprompting message 123A, or the map type was notspecified on the MAP command line. Consequently,CMS map type processing is used.


User response: Continue or terminate commandprocessing when possible.


HCS332I THE LOAD MAP filename filetype filemodeHAS BEEN APPENDED TO MODULEMAP filename filetype filemode

Explanation: The load map has been successfullyappended to the module map.



HCS340I DYNAMICALLY CREATING MODULEMAP

Explanation: You entered the DUMPSCAN orPRTDUMP command with a CP dump on a writabledisk that has no appended module map. A map isbeing built and appended to the dump file specified inthe command.



HCS341I DISK nn IS READ ONLY, DYNAMICMAP NOT CREATED

Explanation: The disk containing the dump file yourequested is a read-only disk. The module map cannotbe appended to the dump.


User response: If you do not need the functions ofeither the FINDMOD subcommand of the DUMPSCANcommand or the module map summary of thePRTDUMP command, no response is necessary. If youdo need these functions, copy the dump file to a CMSdisk where you have write access. Then reenter theDUMPSCAN or PRTDUMP command specifying thedump file on the CMS disk to which you have writeaccess.

HCS342I INSUFFICIENT DASD SPACE,DYNAMIC MAP NOT CREATED

Explanation: While the z/VM: Dump Viewing Facilityattempted to append the dynamically created modulemap to the requested dump file, the disk containing thedump became full. The load map is not appended.


User response: If you do not need the functions ofeither the FINDMOD subcommand of the DUMPSCANcommand or the module map summary of thePRTDUMP command, no user response is necessary. Ifyou do need these functions, delete any unwanted filesfrom the disk containing the dump file to secure spacefor the appended module map. Then reenter theDUMPSCAN or PRTDUMP command.

HCS350I THE MODULE OR ENTRY POINT nameWAS NOT IN STORAGE AT THETIME OF THE DUMP

Explanation: The specified module or entry point wasnot in real storage at the time of the dump.

System action: Subcommand processing terminates,and the z/VM: Dump Viewing Facility waits for a newsubcommand.


HCS351E THE ADDRESS address IS NOT IN AMODULE

Explanation: The address specified on the FINDMODsubcommand is not contained in any module in thedump.



HCS352I THE MODULE OR ENTRY POINT nameWAS NOT FOUND IN THE MODULEMAP

Explanation: The specified module or entry pointname was not found in the module map appended tothe dump.


User response: Check if the correct module or entrypoint name was entered. Correct the name and reenterthe subcommand, or enter a new subcommand.

HCS353I THE MODULE OR ENTRY POINT nameIS LOCATED AT ADDRESS address

Explanation: The specified module or entry pointname was found to be in storage at the time of thedump, but the page was not included in the dump.

System action: This message is followed by a messageindicating why the page was not found.

Subcommand processing terminates, and the z/VM:Dump Viewing Facility waits for a new subcommand.


HCS380E THE EXTRA OPERAND operand IS NOTVALID

Explanation: The indicated additional operand wasspecified on the command line.

System action: Subcommand processing is terminated.


HCS332I • HCS380E


HCS400E subcommand IS NOT A RECOGNIZEDSUBCOMMAND

Explanation: The indicated subcommand you enteredis not a known DUMPSCAN subcommand.

System action: The z/VM: Dump Viewing Facilitywaits for you to enter another DUMPSCANsubcommand.


HCS401I READY, DUMP TYPE IS type

Explanation: This message is issued wheneverDUMPSCAN is waiting for a subcommand.

System action: The z/VM: Dump Viewing Facilitywaits for the next subcommand.

User response: Enter a DUMPSCAN subcommand.

Note: The type value in the dump file will be used.

HCS402E THE subcommand SUBCOMMAND ISNOT VALID FOR type DUMPS

Explanation: The DUMPSCAN subcommand enteredis not valid for the specified type of dumps. The typevariable is the dump type.

System action: The subcommand is not processed.After issuing the message, the z/VM: Dump ViewingFacility waits for you to enter another subcommand.

User response: You may continue analyzing the dumpby entering a new subcommand.

HCS403E THE option OPTION IS NOT VALIDFOR type DUMPS

Explanation: The PRTDUMP option entered is notsupported for the specified type of dump.


User response: Correct and reenter the request, orenter a new request.

HCS404E THE ‘operand’ OPERAND IS NOTVALID FOR type DUMPS

Explanation: When you issued a subcommand ofDUMPSCAN, you entered an operand that was notvalid for that type of dump.

System action: The subcommand terminates.DUMPSCAN waits for you to enter a newsubcommand.

User response: Reissue the subcommand withoutusing the specified operand.

HCS405E THE SUBCOMMAND subcommand ISNOT SUPPORTED FOR type DUMPS

Explanation: When you issued the external formattingroutine subcommand, you entered a subcommand thatis not supported for the specified type of dump by thedump viewing facility.

System action: The subcommand is not processed.After issuing the message, DUMPSCAN waits for youto enter another subcommand.

User response: Enter a new subcommand to continueanalyzing your dump.

HCS406I THIS IS THE ONLY DUMP FILE INTHE XEDIT RING

Explanation: DUMPSCAN issues this message when auser attempts to switch to the next dump file in thering, but one is not there.



HCS446I BLOCK INITIALIZATION HASSTARTED, PLEASE BE PATIENT

Explanation: The BLOCK subcommand is building thecontrol block look-up table.

System action: BLOCK processes the control blockdefinitions specified in the control block.


HCS447I BLOCK INITIALIZATION HASCOMPLETED SUCCESSFULLY

Explanation: The BLOCK subcommand has beensuccessful in building the look-up table.

System action: BLOCK processes the user request todisplay a control block.


HCS448I BLOCK INITIALIZATION HASFAILED

Explanation: The BLOCK subcommand has beenunsuccessful in building the look-up table.

System action: The subcommand terminates. You willreceive an additional message or messages indicatingthe cause of the error.

User response: Correct the error, then reenter theBLOCK subcommand.

HCS400E • HCS448I


HCS449I UNABLE TO PROCESS THE BLOCKSUBCOMMAND

Explanation: The BLOCK subcommand cannot beexecuted because of an error condition.

System action: The subcommand terminates. You willreceive a second message to further explain the error.

User response: Correct the error, then reenter theBLOCK subcommand.

HCS450I THE BLOCK TABLE ‘tablename’ WASNOT FOUND

Explanation: The indicated block table name was notfound on any disk you have accessed.

System action: Command processing continues, butthe BLOCK subcommand cannot format control blockscontained in the specified table.

User response: You can terminate the DUMPSCANcommand, then access the disk containing the table.Reenter the DUMPSCAN command and then theBLOCK subcommand.

HCS451I THE ‘cbname’ CONTROL BLOCKCANNOT BE FOUND IN ANY BLOCKTABLE

Explanation: The control block name you specifiedwas not found in any of the BLOCK table files.

System action: Subcommand processing terminates.

User response: Reenter the BLOCK subcommand witha correct control block name.

HCS452I THE FIELD ‘field name’ WAS NOTFOUND

Explanation: The field name you specified was notfound in the block table entry for that control block.

System action: You receive message 455A, whichreprompts you for the correct field name. Any fieldnames already entered that were correct are saved andused by the BLOCK subcommand.

User response: Reenter the field name correctly or endthe prompt.

HCS454I UNKNOWN CONTROL BLOCK ID,RE-ENTER BLOCK SUBCOMMANDUSING THE CONTROL BLOCK NAME

Explanation: You entered an asterisk (*) for a controlblock name. The Dump Viewing Facility could not findthe actual control block name in its internal table.

System action: The subcommand terminates, andDUMPSCAN waits for you to enter a newsubcommand.

User response: Enter the BLOCK subcommand againusing the control block name instead of an asterisk.

HCS455A ENTER FIELD NAME(S) TO BEFORMATTED, QUIT TO ENDSUBCOMMAND OR NULL LINE TOEND PROMPT

Explanation: This is a prompt for you to enter thenames of specific fields for formatting.


User response: You should enter either the fieldnames, separated by blanks, or a null line to indicatethat there are no more field names requested. If youenter QUIT, the BLOCK subcommand processing ends.If you enter a null line in response to the first prompt,only entries flagged as default fields are formatted.

HCS456I TOO MANY FIELD NAMESSPECIFIED. THE EXTRA AREIGNORED

Explanation: You have requested more than 512 fieldnames for formatting.

System action: The first 512 field names are used. Theextra ones are ignored. You are not prompted for morecontrol block names and processing continues.

User response: None. If you want to see more than512 fields, reenter the BLOCK subcommand and specifyALL instead of PROMPT.

HCS457E BLOCK SUBCOMMAND NOTSUPPORTED FOR type DUMP

Explanation: The BLOCK subcommand is notsupported for the specified type of dump.

System action: The subcommand terminates, andDUMPSCAN waits for a new subcommand to beentered.


HCS458E THE CONTROL FILE filename filetypeWAS NOT FOUND

Explanation: The BLOCK subcommand is notsupported because a control file was not found for thespecified type of dump you requested.


User response: You should access the disk containingthe necessary control file and reenter the DUMPSCANcommand, or you should enter another subcommand.

HCS449I • HCS458E


HCS459E CANNOT LOCATE ANY OF THEBLOCK TABLE FILES

Explanation: The z/VM: Dump Viewing Facilitycannot locate any of the BLOCK table files used toformat control blocks.

System action: The subcommand terminates andDUMPSCAN waits for a new subcommand to beentered.

User response: Access the disk containing the BLOCKtables and reenter the BLOCK subcommand, or issueanother subcommand.

HCS510I THE &NAME TABLE IS FULL

Explanation: The space available in the &name tableis not sufficient for the entry being added.

System action: The z/VM: Dump Viewing Facilitywaits for the next subcommand.

User response: You may redefine previous entrieswith shorter entries to make space available in the&name table, or you may enter a new subcommand.

HCS511E &name IS NOT IN THE &NAME TABLE

Explanation: You invoked &name, and it was not inthe table.


User response: Enter the & subcommand to list allentries in the table and then reenter a valid &name orany other DUMPSCAN subcommand.

HCS512I THE &NAME TABLE IS EMPTY

Explanation: There are no entries in the &name table.


User response: Use the &name subcommand to addentries to the &name table or enter anotherDUMPSCAN subcommand.

HCS520I A LOOP WAS DETECTED IN THE typeCHAIN

Explanation: An unexpected loop was detected in thespecified control block chain currently being processed.

System action: If a DUMPSCAN subcommand wasentered, subcommand processing is terminated with thedetection of the loop. Any output that was completedbefore the detection of the loop will be displayed.

If the PRTDUMP command was entered, this messageis printed in the output to indicate why the particular

summary report was not complete. A message will beissued indicating that the summary report beingprocessed is not complete. The printing of other dumpdata continues.

User response: If you are in DUMPSCAN mode, youmay enter a new subcommand.

CommandType

PRTDUMPVMDBK

CHAIN subcommandCONTROL BLOCK

VIOBLOK subcommandVMDBK

VMDBK subcommandVMDBK

HCS521I CONTROL BLOCK AT address POINTSTO CONTROL BLOCK AT address

Explanation: The control block at the addressspecified points to another control block already in thechain.

System action: Additional informational messages willbe issued. Then subcommand processing terminates.


HCS522I CONTROL BLOCK #nnnn POINTS TOCONTROL BLOCK #nnnn

Explanation: The control block specified by thevariable nnnn points to another control block specifiedby the second nnnn variable that is already in thechain.

System action: An additional informational messagemay be issued. Then subcommand processingterminates.


HCS523I nnnn ENTRIES WERE FOUND IN THECHAIN

Explanation: This message tells you how many entrieswere found in the chain.

System action: The z/VM: Dump Viewing Facilitywaits for a new subcommand.


HCS524I THE FIRST CONTROL BLOCKPOINTS TO ITSELF

Explanation: The first control block on a chain pointsto itself.


HCS459E • HCS524I



HCS525I CB # nnnn AT address

Explanation: The control block specified by thevariable nnnn is located at the address indicated by thevariable address.

System action: Subcommand processing continues.


HCS526I THE LAST CONTROL BLOCK POINTSTO THE FIRST

Explanation: The last control block on a chain pointsto the first control block on the same chain. Thismessage appears for noncyclic chains only.



HCS527I THE LAST CONTROL BLOCK POINTSTO ITSELF

Explanation: The last control block on a chain pointsto itself.



HCS528I CHAIN MAXIMUM OF 4096CONTROL BLOCKS REACHED

Explanation: The maximum number of entries is 4096in a chain for which the CHAIN subcommand is ableto detect a loop. That maximum has been reached.

System action: The system waits for a null line (thenull line subcommand) or another subcommand to beentered.

User response: If you wish to continue CHAINsubcommand processing for this chain, enter a null line(the null line subcommand). Subcommand processingthen continues from the last entry found.

HCS529I nnnn ENTRIES - PROCESSINGCONTINUES

Explanation: You entered the COUNT operand on theCHAIN subcommand. The subcommand is working.

System action: System processing continues.


HCS530I THE STRING string WAS NOT FOUND

Explanation: The string (hexadecimal or EBCDIC) wasnot found between the starting and ending addressesspecified on the input.

System action: Subcommand processing terminates,

and the z/VM: Dump Viewing Facility waits for a newsubcommand.


HCS540E THE STARTING ADDRESS addressMUST BE LESS THAN THE ENDINGADDRESS

Explanation: The starting address specified with theLOCATE subcommand is greater than the endingaddress.


User response: Correct the input and reenter thesubcommand or enter a new subcommand.

HCS541E THE STARTING ADDRESS addressMUST BE GREATER THAN THEENDING ADDRESS

Explanation: The starting address specified with theLOCATE subcommand is less than the ending address.


User response: Correct the input and reenter thesubcommand or enter a new subcommand.

HCS543I THE BEGINNING OF THE DUMPWAS REACHED

Explanation: The beginning of the dump was reached.



HCS544E A VALID SCROLLING ADDRESS HASNOT YET BEEN ESTABLISHED

Explanation: A FORWARD or BACKWARD requestmust follow some other request that generates adisplay address. This has not yet happened in thisDUMPSCAN session.


User response: Enter an address in the area you wishto examine by using a subcommand such as DISPLAYor LOCATE, or enter a new subcommand.


HCS545E SCROLLING BEYOND OFFSET offset ISINVALID

Explanation: The OFFSET value has gone beyond 0 orhexadecimal FFF0 while using one of the followingsubcommands: FORWARD, BACKWARD, SCROLL,SCROLLUP, +, or -.


User response: Either set the OFFSET value within thelimits by entering the appropriate FORWARD,BACKWARD, SCROLL, SCROLLUP, +, or -subcommand or enter another DISPLAY subcommand.

DUMPSCAN SubcommandOffset (Hex)

+ 0 or FFF0

- 0 or FFF0

BACKWARD0 or FFF0

FORWARD0 or FFF0

SCROLL0 or FFF0

SCROLLUP0 or FFF0

HCS560I THE CPU ADDRESS cpuaddr IS NOTIN THE DUMP

Explanation: You tried to display or refer to a CPUaddress that was not in the dump.


User response: Enter a new subcommand or use theCPU subcommand to determine which processors arein the dump.

HCS570I VECTOR INFORMATION IS NOTAVAILABLE FOR THIS VIRTUALMACHINE

Explanation: The dump being viewed byDUMPSCAN contains no vector register contents orstatus for any virtual CPU. You have requested vectorinformation for a virtual machine where the VectorFacility was one of the following:

v Undefined

v Never used

v Unavailable because of Vector Facility failure.

System action: Subcommand processing terminates,and DUMPSCAN waits for a new subcommand to beentered.

User response: Ensure that the correct dump is beingviewed.

HCS571I VECTOR INFORMATION IS NOTAVAILABLE FOR THIS CPU

Explanation: Although vector information is availablein the dump being viewed, the Vector Facility was notdefined or not functional for the processor requested,or no data had been placed in it.

System action: Subcommand processing terminates,and DUMPSCAN waits for a new subcommand to beentered.

User response: Issue the subcommand withoutspecifying a CPU address. Or, correct the addressspecified. You can use the CPU subcommand ofDUMPSCAN to obtain all processor identifiers in thedump.

HCS576E SPECIFYING AN ODD REGISTER ISINVALID FOR VPAIR

Explanation: You specified an odd register as thestarting or ending register for the VPAIR subcommand.Only even number register pairs can be specified.

System action: Subcommand processing terminates.The z/VM: Dump Viewing Facility waits for a newsubcommand.

User response: Reenter the VPAIR subcommandspecifying even register numbers as operands.

HCS577E THE STARTING REGISTER ISGREATER THAN THE ENDINGREGISTER

Explanation: You entered a range of registers in whichthe first register was larger than the last.


User response: Reenter the subcommand specifying avalid range of registers.

HCS578E THE STARTING ELEMENT ISGREATER THAN THE ENDINGELEMENT

Explanation: You entered a range of elements inwhich the first element was larger than the last.


User response: Reenter the subcommand specifying avalid range of elements.

HCS545E • HCS578E


HCS579E THE REGISTER OPERAND ‘operand’ ISGREATER THAN numberCHARACTERS

Explanation: When you entered the VPAIR or VREGsubcommand, you specified characters in excess of themaximum number allowed for a register operand. Forexample, you entered “003” when only two charactersare permitted.


User response: Reenter the subcommand specifying avalid register number.

HCS580E THE ELEMENT OPERAND ‘operand’ ISGREATER THAN numberCHARACTERS

Explanation: When you entered the VPAIR or VREGsubcommand, you specified characters in excess of themaximum number allowed for an element operand. Forexample, you entered “0123” when only threecharacters are permitted.


User response: Reenter the subcommand specifying avalid element number.

HCS600I NO VALID TRACE ENTRIES WEREFOUND FOR CPU ADDRESS cpuaddr

Explanation: The value contained in control register12 for the specified processor pointed to an invalidtrace entry that did not contain hexadecimal 74 in thefirst byte.



HCS601I NO VALID TRACE ENTRY WASFOUND AT ADDRESS address

Explanation: The input address pointed to an invalidtrace entry that did not contain hexadecimal 74 in thefirst byte.

System action: If the command was DUMPSCAN,subcommand processing terminates, and the z/VM:Dump Viewing Facility waits for a new subcommand.

If the command was PRTDUMP, message 602I isprinted in the summary report and processingcontinues.


HCS602I THE TRACE SUMMARY WILLCONTINUE WITHOUT CPU cpuaddr

Explanation: An error occurred preventing the tracefunction of PRTDUMP from locating all or some of thetrace entries for the processor indicated.

System action: The summary printout continueswithout the identified processor. The summary containsa list of all merged trace entries up to the point oferror, and all except those from the identified processorafter the error.


HCS603I THE TRACE ENTRY AT address IS NOTIN THE TRACE TABLE FOR CPUcpuaddr

Explanation: The address specified by the FROMkeyword in the command is missing from either of thefollowing:

v The trace table for the processor specified, if thecommand includes a single processor address

v All trace tables for all processors whose dumps wereto be merged, if the command specifies or defaults toALL.

System action: Subcommand processing terminates.DUMPSCAN waits for a new subcommand to beentered.

User response: Correct the FROM address or the CPUaddress and reenter the subcommand. Otherwise, enteranother DUMPSCAN subcommand, HX, END, orQUIT.

HCS610I THERE IS NO SELECTION CRITERIAIN EFFECT

Explanation: You entered SELECT QUERY but youhave not previously specified any selection criteria.

System action: Subcommand processing terminates.DUMPSCAN waits for a new subcommand to beentered.

User response: Enter any DUMPSCAN subcommand.

HCS611I THE USER ‘userid’ DOES NOT APPEARIN THE DUMP

Explanation: The user ID you specified is not locatedin the dump file.

System action: Subcommand processing for therequested user ID is terminated. The user ID youspecified is not saved for future trace table entryselection.

Subcommand processing is continued for any otheruser ID that may be requested in the same SELECTinvocation.

HCS579E • HCS611I


User response: Correct the input and reenter theSELECT subcommand or a new subcommand.

HCS641I THE type device DOES NOT EXIST INTHE DUMP

Explanation: The device for the real device or logicaldevice specified did not exist in the dump.

System action: Subcommand processing terminatesand the z/VM: Dump Viewing Facility waits for a newsubcommand.


HCS642I NO type [FOR USER userid] COULD BEFOUND

Explanation: No I/O device blocks of the specifiedtype could be found in the dump.

System action: The printing of other dump datacontinues.


Command TypePRTDUMP real devices

virtual devicesRIOBLOK (DUMPSCANsubcommand)

real deviceslogical devices

VIOBLOK (DUMPSCANsubcommand)

virtual devicesvirtual subchannels

HCS643I THE type DEVICE BLOCKS FORDEVICES nnnn TO mmmm ARE NOTAVAILABLE

Explanation: The I/O device blocks of the specifiedtype in the indicated range could not be found in thedump.

System action: The printing of other dump datacontinues.


HCS660I THE ENTRY AT address IS NOTWITHIN THE FRAME TABLE

Explanation: The address specified by the user is notthe address of an entry in the frame table.

System action: Processing continues and the storage atthe frame table entry address is formatted anddisplayed.


HCS661I THE ENDING ADDRESS OF THEFRAME TABLE IS BEYOND THEDUMP STORAGE SIZE OF size

Explanation: The upper boundary of the frame tableexceeds the size of the dump.

System action: If the command was DUMPSCAN, theentry is displayed, if possible.

If the command was PRTDUMP, the FRAMETBLsummary is not complete.

User response: If you are in DUMPSCAN, enter anew subcommand.

HCS670I NO SNAP DATA IS PRESENT

Explanation: The soft abend dump you requested forprocessing contains no SNAPLIST data or snappedsave areas.

System action: DUMPSCAN processing continues.

User response: Enter any DUMPSCAN subcommand.

HCS690I THE DUMP SYMPTOM RECORD ISMISSING FROM FILE filename filetypefilemode

Explanation: The first record of the specified dumpfile is not a valid dump symptom record. The first 2bytes should contain the characters “SR”, and they donot.

System action: If the SYMPTOM subcommand wasentered, no summary information is displayed and thesubcommand terminates. The z/VM: Dump ViewingFacility waits for a new subcommand.

If the PRTDUMP command was entered, you areprompted to specify whether printing the dumpsummary reports should continue.

Note: Results of further processing are unpredictable.

User response: IBM recommends that you verify thatthe specified file ID actually contains a valid z/VM CPabend, stand-alone, virtual machine, or soft-abenddump. The user may continue analyzing the dump.

HCS701I THE type ADDRESS address MUST BEON A boundary BOUNDARY

Explanation: An address needed for processing wasnot on the correct boundary for the type of address.The address may be one that was specified on thesubcommand line, or may be an intermediary addressused in processing.

System action: If the error was encountered whileprocessing a DUMPSCAN subcommand, subcommand

processing continues if possible. If the error was

HCS641I • HCS701I


encountered in PRTDUMP, the printing of other dumpdata will continue.

User response: If you specified the address on aDUMPSCAN subcommand, you may correct thespecified input address and reenter the subcommand,or enter a new subcommand.

Command Type Boundary

PRTDUMP CHRBK DoublewordFrame table 4KBRDEV DoublewordSystem commonarea

4KB

Trace table page 4KBVDEV DoublewordVMDBK 4KB

DUMPSCANsubcommands Type BoundaryFRAMETBL Frame table 4KB

Frame table entry 16 BYTERIOBLOK CHRBK Doubleword

RDEV DoublewordRSPBK DoublewordSystem commonarea

4KB

VMDBK 4KBIORBK Doubleword

TRACE Trace table entry 32 BYTETrace table page 4KB

VIOBLOK CACBK DoublewordCHRBK DoublewordIORBK DoublewordRDEV DoublewordSystem commonarea

4KB

VDEV DoublewordVDSBK DoublewordVMDBK 4KB

VMDBK VMDBK 4KB

HCS702I THE type ADDRESS address EQUALSOR EXCEEDS THE DUMP STORAGESIZE OF size

Explanation: The address to be displayed orreferenced equals or exceeds the storage size of thedump.

System action: If a DUMPSCAN subcommand wasentered, subcommand processing continues, if possible.

If the PRTDUMP command was entered, the printing ofother dump data continues.

User response: If the address specified was on aDUMPSCAN subcommand, correct the specified input

address and reenter the subcommand, or enter a newsubcommand.

Commands TypeADDMAP System VMDBK

System segment tableSystem page table

PRTDUMP Address of RADIX treeCHRBKFrame tableReal device blockSystem common areaTrace table pageVirtual device blockVMDBK

DUMPSCANsubcommands

Type

-+BACKWARDCHAINDISPLAYFINDMODFRAMETBL Frame table

Frame table entryLOCATELOCATEUPRIOBLOK Address of RADIX tree

CHRBKIORBKRADIX treeReal device blockRSPBKVMDBK

SCROLLSCROLLUPSNAPLISTTRACE Trace table pageVIOBLOK CACBK

CHRBKIORBKReal device blockSystem common areaVirtual device blockVMDBK

VMDBK VMDBK

HCS703I THE type ADDRESS IS ZERO

Explanation: The address represented by type ormentioned in a previous message is zero.

System action: If the error was encountered whileprocessing a DUMPSCAN subcommand, subcommandprocessing continues, if possible.

HCS702I • HCS703I


If the error was encountered in PRTDUMP, the printingof other dump data continues.


Commands TypeADDMAP System VMDBK

System segment tableSystem page table

PRTDUMP Address of RADIX treeCHRBKFrame tableRDEVSystem common areaVDEVVMDBK

DUMPSCANsubcommands

Type

FRAMETBL Frame tableRIOBLOK Address of RADIX tree

RADIX treeRDEVRSPBKSystem common area

VIOBLOK CACBKRADIX treeSystem common areaVDEVVDSBKVMDBK

VMDBK VMDBK page

HCS720I THE type CHAIN IS BROKEN

Explanation: The specified control block chain was notcomplete in the dump because either an invalid pointerwas found or a necessary page was not in the dump.

System action: If a DUMPSCAN subcommand wasentered, subcommand processing is terminated with thedetection of a broken chain. Any output that wascompleted before the detection of the broken chain isdisplayed.

If the PRTDUMP command was entered, the printing ofother dump data continues. A message is displayedindicating that the summary report currently beingprinted is incomplete. The partial summary reportindicates where the chain was broken.

User response: If you are in DUMPSCAN, you mayenter a new subcommand.

Subcommands TypeRIOBLOK Real device

Subcommands TypeLogical device

VIOBLOK VMDBKVirtual deviceVirtual subchannel

VMDBK VMDBK

HCS730I THE type PAGE WITH ADDRESSaddress IS NOT IN THE DUMP

Explanation: In attempting to locate data in the dump,a pointer referenced a page that was not in the dump.

System action: If the error was encountered while aDUMPSCAN subcommand was being processed,processing continues, if possible.

If the error was encountered during PRTDUMPprocessing, the printing of other dump data continues.


Commands Page TypeADDMAP System page table

System segment tableSystem VMDBK

PRTDUMP CHRBKFrame tableReal device blockSystem common areaTrace table pageVirtual device blockVMDBK

DUMPSCANsubcommands

Type

FRAMETBL Frame tableRIOBLOK CHRBK

IORBKRADIX treeRDEVRSPBKSystem common areaVDEVVMDBK

TRACE Trace tableVIOBLOK CACBK

CHRBKIORBKRDEVSystem common areaVDEVVDSBKVMDBK

HCS720I • HCS730I


DUMPSCANsubcommands

Type

VMDBK VMDBKAll others

HCS740I THE PREFIX PAGE COULD NOT BEFOUND

Explanation: The pointer to the prefix page was eitherzero, not on a 4KB boundary, or pointed to an addressthat is not in the dump.

System action: Processing continues, if possible.


HCS741I THE PREFIX PAGE FOR CPU cpuaddr ISNOT AVAILABLE

Explanation: The prefix page for the specifiedprocessor is not in the dump, or the page could not beread, or the prefix page could not be located.



HCS750I DUMPID DATA WAS NOT PROVIDED

Explanation: The dumpid operand of the VMDUMPcommand was not used to provide descriptive text ofthe dump.



HCS800I THE EXTRA OPERAND ‘operand’ ISIGNORED

Explanation: A valid operand (other than USER) isspecified multiple times.

System action: Printing of other dump data continues.


HCS801E THE OPERAND ‘operand’ IS NOTVALID

Explanation: The operand specified on the commandline is not a recognized operand.

System action: Command or subcommand processingterminates, or you are prompted for the correctoperand.

User response: If prompted, enter the correct operand,or correct and reenter the request, or else enter a newrequest.

HCS802E THE REQUIRED operand OPERAND ISMISSING

Explanation: A required operand was not specified onthe command line.

System action: Command or subcommand processingterminates with the exception of TRACERED selectionprompts.

User response: Correct and reenter the request, orenter a new request.

HCS803E TOO {MANY|FEW} FILEIDOPERANDS FOR MAPTYPE type

Explanation: You entered either too many or too fewfile ID operands for the specified module map type.The MAP command shows the number of file IDsassociated with each type.


User response: Correct the operands and reenter theMAP command.

HCS804E REQUIRED OPERAND MISSING FOR‘keyword’ KEYWORD

Explanation: An operand value is required followingthe specified keyword.

System action: The subcommand terminates, andDUMPSCAN waits for a new subcommand to beentered.

User response: Enter the HELP subcommand, or findthe correct subcommand syntax. Then correct and enterthe subcommand again. For more information aboutsubcommand syntax, refer to z/VM: Dump ViewingFacility.

HCS810E CONFLICT BETWEEN OPERANDSoperand1 AND operand2

Explanation: You entered the specified conflictingoperands on the command line.


User response: Reenter the subcommand correctly orenter a new subcommand.

Subcommand Operand1 Operand2TRACE HEX

FORMATFORMATHEX

CPUALL

ALLCPU

VMDBK LISTAny operand

Any operandLIST

HCS740I • HCS810E


Subcommand Operand1 Operand2FORAT

ATFOR

BLOCK ALL PROMPT

HCS811E THE OPERAND ‘operand’ MUST BE AHEXADECIMAL NUMBER

Explanation: An operand that must be a hexadecimalnumber contains nonhexadecimal characters.


User response: Reenter the subcommand correctly orenter a new subcommand.

HCS812E THE type OPERAND ‘operand’ ISGREATER THAN MAXIMUM VALUEOF value

Explanation: An operand exceeded its maximumpermissible value.

System action: Subcommand processing terminatesand the z/VM: Dump Viewing Facility waits for a newsubcommand.

User response: Correct the input and reenter or entera new subcommand.

HCS813E THE type OPERAND ‘operand’ MUSTBE A DECIMAL NUMBER

Explanation: In response to a prompt message forselection criteria, you specified nondecimal charactersfor an operand that must be a decimal number.

System action: Your response is ignored. You will bereprompted.

User response: Reenter the keyword and a validdecimal number. If you want to end the prompt, entera null line.

HCS814E ‘operand’ OPERAND SPECIFIED TWICE

Explanation: You entered the displayed operand twicewhile entering a DUMPSCAN subcommand.

System action: Subcommand processing terminates,and DUMPSCAN waits for you to enter a newsubcommand.

User response: Reenter the subcommand using thespecified operand only once.

HCS852I THE USER PAGES CANNOT BESUPPRESSED; ALL DUMPED PAGESWILL BE PRINTED

Explanation: The frame table pages cannot be locatedin the dump. Therefore, the control program pagescannot be distinguished from user pages. All of thepages will be printed instead of just the requested CPpages.

System action: Message HCS854A is issued,prompting you to decide whether the storage summaryshould be printed. If you answer NO, the storagesummary will not be in the summary file, but othersummaries requested will appear. If you answer YES,all dumped pages will appear in the storage summary.

User response: Provide an answer to the promptrequested by HCS854A.

HCS853E THE CP OPTION IS ONLY ALLOWEDFOR A STORAGE SUMMARY

Explanation: The CP option was entered as the firstoption or following an option other than STORAGE.CP is only valid immediately following the STORAGEoption.

System action: The PRTDUMP command terminateswithout printing any summaries.

User response: Enter the PRTDUMP command again,either without the CP option or with the CP optioncorrectly placed after the STORAGE option.

HCS854A DO YOU WANT PRINTING OF THESTORAGE SUMMARY TOCONTINUE? ANSWER YES OR NO

Explanation: The condition explained by the previousmessage may affect your decision to print the storagesummary report. You may choose whether to continueprinting the storage summary report. Your answer hasno effect on other summary reports if any wererequested.

System action: If you enter a response that is notvalid, the prompt is reissued. If you respond YES,storage summary processing continues. If you respondNO, storage summary processing is terminated.

User response: You must respond YES or NO towhether the printing of the storage summary reportshould continue.

HCS900E PROCESSING ERROR FROM name,CODE nnn

Explanation: A nonzero return code was returnedfrom the indicated routine or macro name and thereturn code was nnn. This indicates an internalprocessing error.

HCS811E • HCS900E


System action: Command processing continues, ifpossible.

User response: If the condition continues, notify yourservice representative.

HCS910E THE VIRTUAL STORAGE CAPACITYIS EXCEEDED

Explanation: There is not enough virtual storageavailable for the command or subcommand to completeprocessing. This may be the result of a system problem,such as storage not being properly released, or the usermay have attempted to use the command in a virtualmachine that was not of the required virtual size.


User response: Verify the storage size of the virtualmachine is large enough. If it is not, define a larger sizeand re-IPL.

HCS920I THE DISK filemode IS NOT ACCESSED

Explanation: This message is generated byDUMPSCAN when a return code of 36 is issued by theFSSTATE macro while trying to locate the dump filespecified on the DUMPSCAN command orsubcommand.

System action: DUMPSCAN command orsubcommand processing terminates.

User response: The user should ensure the disk isaccessed that contains the desired dump.

HCS930E DISK nn IS READ ONLY

Explanation: You are trying to write to a read-onlydisk.


User response: Reenter TRACERED and specify adifferent file mode.

HCS950E ERROR READING FILE filename filetypefilemode, CODE nn

Explanation: An error occurred preventing the z/VM:Dump Viewing Facility from reading the data. FSREADfailed with the CMS return code indicated.



HCS960E ERROR PRINTING DATA, CODE nn

Explanation: An error occurred preventing the z/VM:Dump Viewing Facility from printing the requesteddata. PRINTL failed with the CMS return codeindicated.


User response: Refer to the appropriate systempublications for the return code definition.

HCS970E ERROR WRITING filename filetypefilemode, CODE nnn

Explanation: An error occurred preventing the z/VM:Dump Viewing Facility from writing the requesteddata. FSWRITE failed with the CMS return codeindicated.


User response: Refer to the appropriate systempublications for the return code definitions.

HCS1101E Additional operands are not allowedwith the INCIDENT keyword.

Explanation: The INCIDENT keyword tells theVIEWSYM command you are interested in a particularincident. Additional operands are used when you wantto specify a set of incidents based on their date andtime, processors, or primary symbol stringcharacteristics.

System action: The current the VIEWSYM commandprocessing terminates and control returns to the callingprogram.

User response: Retype the command usingINCIDENT filename ftypeSYM without any extraoperands.

HCS1102E The FROM time value must be less than24:00:01.

Explanation: This is a time value, and values largerthan 24:00:00 are ambiguous.

System action: The current VIEWSYM processingends. Control returns to the calling program.

User response: Change the time value.

HCS1105E Change the non-numeric character inxxxxxxxx to a numeric character 0through 9.

Explanation: Time and date field must containdecimal values.


User response: Enter a numeric value.

HCS1106E The parameter parameter must be nncharacters or less.

Explanation: In a VIEWSYM command, the indicatedparameter was found to be longer than the indicated

HCS910E • HCS1106E


maximum number of characters; it may be one of thefollowing:

Parameternn

SYMPTOM15

COMPONENT9

CPUSERIAL6

MODULE10

System action: The current VIEWSYM processingends, and control returns to the calling program.

User response: Verify the specified parameter is nolonger than the maximum characters allowed, andreenter the command.

HCS1108E The {month|day} specified does notexist.

Explanation: In a VIEWSYM command, the valueentered for {month|day} is incorrect.


User response: Verify you specified the valuecorrectly, and reenter the command.

HCS1109E The {INCIDENT | FROM | TO |COMPONENT | CPUSERIAL |MODULE | SYMPTOM} option cannotbe used more than once.

Explanation: In a VIEWSYM command, the indicatedoption can be specified only once.


User response: Reenter the command using thespecified option only once.

HCS1110E The operand xxxxxxxx is invalid.

Explanation: The command did not recognize theoperand. It may be misspelled or invalid in thiscontext.


User response: Check the spelling of the operand andthe context in which you used it.

HCS1111E The INCident filename xxxxxxxxcontains a character other than 0..9 orA..F.

Explanation: The command did not recognize acharacter. The file name or file type may have beenentered incorrectly.

System action: VIEWSYM processing terminates.Control returns to the calling environment.

User response: Verify that you specified the file namecorrectly.

HCS1112E The INCident filetype xxxxxxxx containsa character other than 0..9 or A..F. in thefirst 5 positions.

Explanation: The command did not recognize acharacter. The file name or file type may have beenentered incorrectly.


User response: Verify that you specified the file namecorrectly.

HCS1113E Change the TO time value to greaterthan or equal to the FROM time value.

Explanation: The times entered must be in the orderof the earliest time (FROM) to the latest time (TO) sothe selected entries will fall within the specified range.

System action: The menu panel is redisplayed toallow you to change the values entered.

User response: Retry the search with new time-rangevalues.

HCS1114E The INCident filename should be 8characters long.

Explanation: In a VIEWSYM command, the file nameof the file specified with INCIDENT was found to beless than 8 characters long.


User response: Verify the file name is 8 characterslong, and reenter the command.

HCS1115E The INCident filetype should be 8characters long.

Explanation: In a VIEWSYM command, the file typeof the file specified with INCIDENT was found to beless than 8 characters long.




User response: Verify the file type is 8 characters long,and reenter the command.

HCS1116E The INCident filetype should end with'SYM'.

Explanation: In a VIEWSYM command, the file typeprovided did not have the characters SYM in positions6-8.


User response: Verify the file type ends with SYM asthe 6-8th characters, and reenter the command.

HCS1117E The symptom record filetype must bespecified.

Explanation: In a VIEWSYM command, the file typewas not included after INCIDENT and file name.


User response: Reenter the command following thefile name with the file type.

HCS1118E A value must be specified following thekeyword keyword.

Explanation: In a VIEWSYM command, the keywordkeyword was found, but no parameter was entered.


User response: Reenter the command using aparameter with the keyword.

HCS1201E The INCident filename and filetypemay not be used with other searcharguments.

Explanation: The INCIDENT keyword is tellingVIEWSYM you know exactly which incident you wishto view, while the other keywords are asking for a listof incidents for you to choose from. The keywords aremutually exclusive.

System action: The command ends and controlreturns to CMS.

User response: Reenter the VIEWSYM command withonly the INCIDENT arguments or the search keywordarguments.

HCS1306E The segment table pointer could not befound.

Explanation: The address you requested to translate isonly reachable through a page that is not in the dump.

System action: None

User response: None

HCS1310E The virtual address address is outside theuser's address space.

Explanation: The address you requested to translate isbeyond the size of the virtual machine for the user IDyou specified.

System action: None

User response: Verify that the value you entered is avirtual address.

HCS1314E The real address ‘address’ is not in avirtual address space.

Explanation: The address requested could not befound within the address space of any virtual machinein the dump.

System action: None

User response: Verify that the value you enteredshould be a real address.

HCS1324E The operand Operand must be a decimalnumber.

Explanation: The MAX keyword must be followed bya decimal number.

System action: Subcommand processing ends.

User response: Verify that the value you enteredcontains only the characters A through Z.

HCS1325E Start of CPE area cannot be found.

Explanation: The FINDCPE command begins lookingfor CPEBK at the address located 12 bytes into entrypoint HCPRCCCM. The entry point could not belocated. Check that the FINDMOD subcommand canlocate the entry point. If not, it is usually because thereisn't a module map appended to the dump.

System action: Subcommand processing ends.

User response: Access the disk that contains thedump read/write and reenter the DUMPSCANcommand. The dynamic map build process will buildand append a module map. Retry the FINDCPEsubcommand. If it still does not work, the pagecontaining HCPRCCCM is not in the dump.

HCS1601E No symptom records match thespecified values.

Explanation: The VIEWSYM command cannot findany symptom records containing the primary symptomstrings or within the time range you have requested.




User response: Broaden the time range or use fewersymptom strings and try the search again.

HCS1602E One match found for the specifiedsearch arguments.

Explanation: There was only one record that matchedall the search arguments you specified.

System action: None

User response: None

HCS1603E The requested INCident is not found.

Explanation: The VIEWSYM command cannot find asymptom record with the file name and file typeshown.


User response: Verify that you entered the file nameand file type correctly.

HCS1604E The subcommand xxxxxxxx is invalid inVIEWSYM.

Explanation: The VIEWSYM command cannot processthe subcommand you entered.


User response: Verify that you entered thesubcommand correctly.

HCS1605E The subcommand xxxxxxxx is invalidfrom this panel.

Explanation: The subcommand entered is ambiguousor invalid for the panel it is issued from.

System action: VIEWSYM processing terminates andreturns control to the calling environment.

User response: Verify that you entered thesubcommand correctly.

HCS1606E Position the cursor on an INCident touse RESPECIFY.

Explanation: The cursor must be positioned on anincident to use the RESPECIFY subcommand.

System action: The list panel is redisplayed.

User response: Position the cursor to a valid incidentand press the ENTER key.

HCS1607E Position the cursor on an INCident touse Enter incident select

Explanation: The cursor must be positioned on anincident in order to select it with the Enter key.

System action: The list panel is displayed again.

User response: Position the cursor on a valid incidentand press the ENTER key.

HCS1608E Position the cursor on an INCident touse SEARCH

Explanation: The cursor must be positioned on anincident to use SEARCH.

System action: The list panel is displayed again.

User response: Position the cursor on a valid incidentand press the ENTER key.

HCS1701E No Symptom Records can be found onyour accessed disks.

Explanation: The correct disk containing the symptomrecords has not been accessed.

System action: The current VIEWSYM commandterminates and the user is returned to the commandline.

User response: Access the correct symptom recorddisk and enter the VIEWSYM command again.

HCS2002E “DSECT” control card missing.

Explanation: In searching the input file, no DSECTcontrol statement was found. Either the statement ismissing, does not contain a name field, or wasmisspelled.

System action: BLOCKMAP processing ends. Controlreturns to the calling program.

User response: Provide the necessary correction andreenter the BLOCKMAP command.

HCS2003E Image file identifier same as work fileidentifier

Explanation: The file name of the input file is thesame as the DSECT name and the file type of the inputfile is “$COPY”.


User response: This is the file ID generated byBLOCKMAP for its work file. The user should changethe file name or file type (or both) of the input file torelieve the conflict. Correct the statement and tryentering BLOCKMAP again.


HCS2005E Invalid length modifier - data_length

Explanation: The prefix length value specified isinvalid. The length should be consistent with the datatype. For example an A data type should not have alength of 5.


User response: Verify that the failing assemblerstatement follows BLOCKMAP conventions. Correct thestatement and try entering BLOCKMAP again.

HCS2006E Label previously defined at hex locationhexaddr.

Explanation: The label specified on the current linehas been previously defined at the specified hexlocation.

System action: BLOCKMAP processing ends, andcontrol returns to the calling program.

User response: Provide the necessary correction andreenter the BLOCKMAP command.

HCS2007E Alignment error, expecting offsetalignment.

Explanation: The alignment implied by the currentdata type operand will result in an undefined holebeing generated for the control block.


User response: Verify that the failing assemblerstatement follows BLOCKMAP conventions. Correct thestatement and try BLOCKMAP again.

HCS2009E Abbreviated label field name too long forbyte definition.

Explanation: The abbreviated field name for a bytedefinition has greater that six characters to fit in thefield box.



HCS2010E “ORG” label label has not beenpreviously defined.

Explanation: The specified label for this ORGstatement has not been previously defined in thiscontrol block. An ORG statement must be a previouslydefined field but cannot be the label on a DSECT oranother ORG statement.

System action: BLOCKMAP processing ends, and

control returns to the calling program.

User response: Verify that the label is spelledcorrectly. Correct the statement and try BLOCKMAPagain.

HCS2011E Invalid hex value for bit definitiontable.

Explanation: The operand of the EQU defining anentry in the bit definition table is not in the followingform:

fieldname EQU X’nn’

Or the hex value contains an invalid value (that is,nonhexadecimal number).



HCS2012E Entry field name greater than 8characters -fieldname.

Explanation: A field name has been encountered thatis greater than 8 characters in length.


User response: Shorten the field name and tryBLOCKMAP again.

HCS2013E Byte nnnnnnnn in bit definition table isundefined.

Explanation: The field name for which the current bitdefinition table applies has not been previously definedin this control block.



HCS2014E Missing continuation statement.

Explanation: This error indicates that column 72 of thecurrent input statement is nonblank and that nosubsequent statement followed.





HCS2015E Externally referenced copy namecopyname not found.

Explanation: The copy file specified in a BITS/CODESDEFINED FOR statement was not found. Verify thespelling of the copy file name and that the correct diskswere accessed at the time.


User response: Correct the statement and tryBLOCKMAP again.

HCS2016E BYtename not found in externallyreferenced copy file'

Explanation: The byte specified as containing a list ofbit definitions was not found in the external file. Verifythat the file name and field name were specifiedcorrectly. The field definition in the external file mustbe specified by:

BITS/CODES DEFINED IN ..., orfieldname BITS/CODES DEFINITIONstatement.


User response: Verify that the externally referencedfile contains the fields that are referenced and that theyare preceded by the BITS/CODES DEFINITIONcomment.

HCS2017E Blockmap does not map control blockfilename.

Explanation: Blockmap requires the PREFIX_LEN = nto appear in the control block prologue.


User response: Add the Blockmap control statementPREFIX_LEN = n to your control block prologue andtry BLOCKMAP again.

HCS2018E Module prologue missingDESCRIPTIVE NAME string.

Explanation: Every prologue must contain theDESCRIPTIVE NAME string. This is used whilebuilding the storage map.


User response: Add the DESCRIPTIVE NAME stringto your prologue and try BLOCKMAP again.

HCS2019E Bit/code definitions missing.

Explanation: No bit definitions found following aBITS DEFINED IN statement.


User response: Verify that the EQU statements thatdefine the bit usage follow the BITS DEFINED INcomment.

HCS2021E Invalid code value -code for name field.

Explanation: Invalid value specified for a code typeEQU statement.


User response: Check for a typing error, correct thestatement, and try BLOCKMAP again.

HCS2024E Variable data allowed only with zeroreplication factor.

Explanation: The control phrase START OFVARIABLE LENGTH DATA was found on an operandwhose implicit or explicit length was not zero.


User response: Figure out a different way to specifythe replication factor. Correct the statement and tryBLOCKMAP again.

HCS2025E Data defining operand follows variabledata field.

Explanation: Variable length data fields must be thelast definition of the main picture or any redefinition.



HCS2026E Implicit length error for operand:operand.

Explanation: A “C” type operand has unbalancedapostrophes.





HCS2027E Null line encountered in source inputfile.

Explanation: Null lines are not allowed. They willcause assembly errors.



HCS2101E Convention violation, datatype operandis invalid.

Explanation: The data type operand is invalid or isnot one of those recognized by BLOCKMAP.


User response: Verify that the failing assemblerstatement follows BLOCKMAP. conventions. Correctthe statement and try BLOCKMAP again.

HCS2102E Convention violation, length qualifier“L” is invalid.

Explanation: A length operand qualifier “L” has beendetected on a data type operand for which it isdisallowed.



HCS2103E Convention violation, length qualifiervalue is invalid.

Explanation: A length operand qualifier “L” has beendetected which is not followed by a valid length value.



HCS2104E Convention violation, replication factornot supported.

Explanation: A replication factor greater than 1 hasbeen detected on a data type operand that also has alength operand associated with it. This combination isvalid on only certain data type operands.


User response: Verify that the failing assembler

statement follows BLOCKMAP conventions. Correct thestatement and try BLOCKMAP again.

HCS2105E Convention violation, prefix does notmatch DSECT prefix.

Explanation: A field name does not start with thedefined control block prefix character(s).



HCS2106E Convention violation, sequential “ORG”statements.

Explanation: Two consecutive ORG statements havebeen encountered with no intervening data definitions.



HCS2107E Convention violation, missing operandon “ORG” statement.

Explanation: An ORG statement has been encounteredthat has no operand associated with it.



HCS2108E Convention violation “ORG” definitionout of bounds.

Explanation: The current ORG redefinition exceedsthe bounds of the main picture definition.



HCS2109E Convention violation, comment requiredon bit “EQU”.

Explanation: A bit defining EQU has beenencountered for which no comment or description hasbeen found.





HCS2110E Convention violation, variable lengthdata not defined in main picture.

Explanation: Variable length fields cannot be definedin redefinitions if the main picture did not also specifyvariable length data.



HCS2111E Variable data keyword encountered onundefined field.

Explanation: The control phrase START OFVARIABLE LENGTH DATA was found as a commenton a statement without a label.



HCS2112E Equated field size informationincorrectly specified

Explanation: The field size information is not numeric.Possibly an apostrophe or other delimiter is missing.




GCS Messages

GCT001E Invalid option ‘option’

Explanation: An invalid option has been entered. Theoption may have been misspelled, it may conflict withanother option on the command line, or it may havebeen entered twice. The option may also have beenabbreviated incorrectly.

System action: The command terminates, and systemstatus is not changed.

User response: Correct and reissue the command.

GCT002E Invalid parameter ‘parameter’ in theoption ‘option’ field

Explanation: The parameter entered after ‘option’ wasinvalid.

System action: RC=24. The command terminates, andsystem status is not changed.

User response: Correct the option and reissue thecommand.

GCT003E ‘option’ option specified twice

Explanation: This option was specified more thanonce in the command line.



GCT004E ‘option1’ and ‘option2’ are conflictingoptions

Explanation: The options named in the message aremutually exclusive and must not be coded in the samecommand.



GCT005S Virtual storage capacity exceeded

Explanation: There is not enough storage available tocomplete the requested operation.

System action: No action is taken on the command,and system status is not changed. For querycommands, the return code is 8; otherwise, the returncode is 25 or 104.

User response: You must either free some virtualstorage or increase the size of your virtual machine. Tofree some virtual storage, issue the RELEASE commandfor any minidisks that you no longer need; then reissuethe original command. To increase the size of yourvirtual machine, use the DEFINE command; then re-IPL

GCS and reissue the original command.

GCT005T Virtual storage capacity exceeded

Explanation: There is not enough virtual storageavailable for file management control blocks.

System action: The virtual machine is placed in adisabled wait state and the disk is not updated.

User response: Use the CP command DEFINE toincrease the size of the virtual machine, re-IPL GCS,and reissue the command.

GCT006E Invalid parameter ‘parameter’

Explanation: An invalid operand, an extraneousoperand, or too many operands were coded in thecommand line or EXEC statement.

System action: RC=24. The command or EXECstatement terminates, and system status is not changed.


GCT007E Extraneous parameter ‘parameter’

Explanation: Too many operands were specified forthe GROUP EXEC.

System action: RC=24. The GROUP EXEC is notexecuted.

User response: Check the GROUP EXEC format andre-execute the GROUP EXEC.

GCT009E Operand is missing or invalid

Explanation: One of the following:

1. An operand was coded incorrectly in a command;or

2. A required operand was not coded; or

3. A duplicate operand was coded.

System action: The command terminates with noaction taken.

User response: Correct the operand and reissue thecommand.

GCT010I Command complete

Explanation: The GDUMP command was completedsuccessfully. All requested areas were dumped.

System action: Processing continues.


GCT001E • GCT010I


GCT011E Invalid character in fileid ‘fn ft’.

Explanation: An invalid character was specified in thefile ‘fn ft’.

System action: RC=20. Execution of the command isterminated. The system status remains the same.

User response: Check the description of the commandformat and reissue the command.

GCT012E No options allowed

Explanation: An option was specified as part of theACCESS command.

System action: RC=24. No action is taken on thecommand, and system status is not changed.


GCT013E No function specified

Explanation: No functions were entered with aQUERY, GLOBAL, or SET command.


User response: Include the desired function andreissue the command.

GCT014E Invalid function ‘function’

Explanation: The GLOBAL command has beenentered with a function other than LOADLIB. GCS cansupport only the LOADLIB function of the GLOBALcommand.


User response: Correct the command to ‘GLOBALLOADLIB [libname1...libname8]’ and reissue thecommand.

GCT015E ‘parameter’ is invalid for the ‘function’function

Explanation: A QUERY DISK command has beenissued with an invalid parameter.

System action: RC=24. The command is not executed.

User response: Correct and reissue the QUERYcommand.

GCT016E Disk vdev not attached

Explanation: The disk identified in the message is notattached to the virtual machine.

System action: The task which attempted to use thedisk ends abnormally with an abend code of 037.

User response: Use the CP LINK command to connect

the proper disk to the virtual machine, and re-executethe program.

GCT017E Disk ‘{mode|vdev|volid}’ not accessed

Explanation: The disk identified in the message hasnot been accessed.

System action: Execution of the command or task isterminated. System status is not changed if a commandwas issued, but if the error occurred in a task, the taskends abnormally with an abend code of 037. The returncode from a command is 0.

User response: Access the disk and re-execute thecommand or program.

GCT018E Disk mode is Read/Only

Explanation: The file mode of the output file specifiesa read-only disk, which cannot be written on.

System action: If the problem occurred when youissued a GROUP or GENERATE EXEC, these EXECsterminate with no action taken and RC=36. If the prefixis ‘GCTXCP’ or ‘GCTVIP,’ then the problem occurredwhen a task attempted to write to a R/O disk. The taskends abnormally with an abend code of 037.

User response: Please do one of the following:

v If you have read/write authority over the disk thatthe output file resides, use the CMS ACCESScommand to reaccess the disk as a read/write disk,and then execute the command or program again.

v Use the CP LINK command to reset the disk toread/write mode (entering a password if necessary),reaccess the disk, and then execute the command orprogram again.

GCT019E No Read/Write mode disk accessed

Explanation: The user does not have access to aread/write disk in file mode ‘mode’ on which thecommand can write its output. The command, in orderto be executed, requires that the disk be accessed inread/write mode.

System action: Execution of the command isterminated. The return code is 36 from the modules;return code is 1 from QUERY DISK R/W.

User response:

1. Access a read/write disk in the mode you requireand reissue the command, or

2. Use the CP LINK command to reset the disk toread/write mode, access the disk again, and thenreissue the command.

GCT011E • GCT019E


GCT020E No Read/Write disk with space availableaccessed

Explanation: All read/write disks currently accessedare full.

System action: No action is taken on the command,and system status is not changed. The QUERYcommand issues RC=2.

User response: Access additional read/write disks, orremove unneeded files.

GCT021E Invalid mode ‘mode’

Explanation: This message can occur for any one ofthe following reasons:

1. The file mode was not entered correctly.

2. The file mode number, if entered, is not between 0and 6.

3. More than two characters were specified for the filemode.


User response: Reissue the command with the filemode specified correctly.

GCT022E No filename specified

Explanation: The OSRUN command has been enteredwithout specifying the name of the application programto be run.

System action: No action is taken on the command,and system status is not changed.

User response: Correct and reissue the OSRUNcommand.

GCT023E No filetype specified

Explanation: The FILEDEF command requires thatyou specify both file name and file type.

System action: RC=24. No action is taken on thecommand and system status is not changed.

User response: Reissue the command, specifying thefile name and file type.

GCT024E File ‘fileid’ not found

Explanation: The file named in the message was notfound on any accessed disks.

System action: RC=36. The file in question is not putin the GLOBAL LOADLIB list and the system continueswith the next file, if any.

User response: Ensure the ‘system name’ file has beencreated and it is on a disk that is accessed.

GCT025E System ‘sysname’ does not exist

Explanation: The system named in the message hasnot been defined to the Control Program.

System action: If the message prefix is ‘GCTGRP’,then the failure occurred during system generation, andsystem status is not changed.

User response: Contact the system programmer, whowill generate a saved system using the correct systemname.

GCT028S Device vdev not attached

Explanation: An input or output operation has beenattempted against a device which is not defined in yourvirtual machine.

System action: If the user‘s SYNAD exit was specifiedin the DCB, it will be executed. Otherwise, message 306or 307 is issued and the task is abnormally terminatedwith system abend code 001.

User response: DEFINE or ATTACH the desireddevice to your virtual machine.

GCT029S Unit check on device vdev. CSW = csw,SCSW = scsw, SENSE = sense

Explanation: A unit check has occurred on thespecified device.

System action: The channel status word (CSW), thesubchannel status word (SCSW) and any availablesense information is displayed. If the first two bytes ofsense information are X'1070', no sense information wasavailable. If the user‘s SYNAD exit was specified in theDCB, it will be executed. Otherwise, message 306S or307S is issued and the task is abnormally terminatedwith system abend code 001.

User response: Examine the device-dependent senseinformation for details concerning the error. Themeaning of the sense information can be found in thedocumentation for that device or its control unit. Formore information about the CSW and SCSW, refer toEnterprise Systems Architecture/390 Principles of Operationand z/Architecture Principles of Operation.

GCT030T Unrecoverable I/O error on device vdev.CSW = csw SCSW = scsw

Explanation: An unrecoverable I/O error has occurredon the virtual device with address ‘vdev’. The twoCSW bytes at the time of the error appear in the cswposition in the message, as do the SCSW bytes.

System action: GCS halts by loading a disabled waitstate PSW. Execution of the command is terminated.

User response: Re-IPL GCS and reenter the commandthat failed. If the problem persists, contact your systemsupport personnel.

GCT020E • GCT030T


GCT032T Supervisor error {1|2|3|4|5}. Re-IPLsysname

Explanation: This message will be issued with anerror number between 1 and 5.

Error Explanation

1 A GETMAIN error has been detected duringGCS supervisor internal processing. The errorprobably occurred because there wasinsufficient free storage to allocate systemcontrol blocks.

2 A FREEMAIN error was detected during GCSsupervisor processing. The error probablyoccurred because an authorized program hasdestroyed system pointers or other vitalinformation needed for storage management.

3 GCS was unable to get storage to extend asave area for a critical processor.

4 GCS was unable to release a save areaextension for a critical processor.

5 A QUERY LOCK command has been issued,and the machine that holds the lock wasinvalid. The invalid virtual machine IDindicates that the lock is held by a nonexistentvirtual machine.

System action: All five errors cause the ‘system name’supervisor to be terminated. The virtual machine isreset.

User response: If error 1 or 3 has occurred, define alarger virtual machine and re-IPL GCS. If the problempersists, notify your system support personnel.

If error 2 has occurred, make sure the problem programis not altering system storage. If the problem persists,notify your system support personnel.

If error 4 has occurred, notify your system supportpersonnel.

If error 5 has occurred, re-IPL GCS and retry theoperations that preceded the failure. Contact yoursystem support personnel.

GCT053E File ‘fn ft fm’ not found

Explanation: The specified file was not found on theaccessed disk(s). Either the file does not reside on thisfile mode, the file identifier was misspelled, orincomplete identification was provided to cause theappropriate file mode to be searched.

For a description of the file identification required byeach command and the search procedure used, refer toz/VM: Group Control System.


User response: Find or create the desired file. Ensure

that the disk on which the file resides is accessed.Correct and reissue the command.

GCT054E Incomplete fileid specified

Explanation: You must specify the file name and filetype in order for the command to be executed. Inaddition, for some commands you must specify the filemode.


User response: Check the description of thecommand, correct the command line, and reissue thecommand.

GCT062E Invalid character ‘char’ in fileid ‘fn ft’

Explanation: The character specified was invalid inthe file ID in which it appeared.


User response: Check the description of the commandformat and reissue the command.

GCT100E Missing the system name operand

Explanation: You must specify a saved system namewhen you invoke the GROUP exec from a line modeterminal. This operand was missing from the exec callas issued.

System action: RC=24. The command terminates.

User response: Reissue ‘GROUP’ followed by thesystem name.

GCT101E Invalid information specified for highcommon field

Explanation: The start of HCOMMON storage definedin the GROUP exec is not greater than 16Mb or amultiple of 1Mb.

System action: None

User response: Correct the information aboutSHCOMMON/EHCOMMON.

GCT103E User environment specification invalid

Explanation: The user environment must be specifiedas YES or NO.

System action: Prompt the user for valid input.

User response: Reply with YES or NO to the question.

GCT032T • GCT103E


GCT104R Enter selection number 1, 2, 3, or 4

Explanation: The selection number identifies thescreen to be displayed or updated.


User response: Type one of these numbers on thecommand line and press the ENTER key.

GCT105E System name not specified

Explanation: No system name was entered on thePrimary Option Menu after invoking the GROUP exec.


User response: Enter the system name on the PrimaryOption Menu.

GCT106E Maximum number of Virtual Machinesmissing or invalid

Explanation: The maximum number of virtualmachines that can join this group must be specified.The number of group members must be in the range 1to 65,535. Only digits 0-9 are valid.


User response: Specify the maximum number ofvirtual machines that can join this group.

GCT107E Trace table location specification invalid

Explanation: An invalid response was entered.



GCT108E Restricted group specification invalid

Explanation: This message indicates the input to theGROUP EXEC was invalid.



GCT109E System ‘sysname’ has not been defined toCP with the VMGROUP attribute

Explanation: When the named saved system wasdefined to the control program, it was not assigned theVMGROUP attribute.

System action: No action is taken on the GROUPexec.

User response: Redefine your GCS named savedsystem to the Control Program with the VMGROUPattribute.

GCT109I System ‘sysname’ was defined to CP withthe VMGROUP attribute

Explanation: The system named in the message hasbeen defined to CP with the VMGROUP attribute.



GCT110I All saved segment names on this pageare valid

Explanation: The saved segment name(s) indicatedhave been defined to the Control Program.



GCT111I You are now editing your ‘fileid’ file

Explanation: The ‘GROUP’ exec has been invokedfrom a line mode terminal.



GCT112E Undefined PFKEY/PAKEY

Explanation: You have pressed a PFkey or PAkey thathas no function assigned to it.



GCT113I The number of VM userids processed isnnnnn

Explanation: ‘nnnnn’ is the total number of virtualmachine user IDs in the ‘system name GROUP’ fileauthorized to (1) execute programs in virtualsupervisor state and (2) have access to all GCSfunctions.



GCT114E No VM userids have been specified

Explanation: No user IDs have been designated asauthorized VM user IDs. Authorized VM user IDs haveauthority to run programs in virtual supervisor stateand have access to all GCS functions.



GCT104R • GCT114E


GCT115I This is the {first|last} page for thisscreen

Explanation: This is an information message sent ifyou are on the first or the last page of a GROUP EXECmenu.



GCT116E The number of invalid userids on thispage is nn

Explanation: At least one user ID entered on thisscreen is not a valid logon.


User response: Correct the user ID(s) that are in error.

GCT117I All userids on this page have beenverified as valid

Explanation: All user IDs have been verified as validuser IDs.



GCT118E Select disk address in the range of 001through FFFF

Explanation: System disk address or system diskextension address is not in the valid range.


User response: Correct the disk address in error.

GCT119E Select trace table size in the range of 4Kthrough 16384K

Explanation: The entry for the trace table size isinvalid.


User response: Correct the trace table size.

GCT120I ‘userid’ is a valid Authorized VM userid

Explanation: The user ID named in the message is avalid user ID and is also an entry in the AuthorizedVM user IDs list.



GCT121I ‘userid’ is a valid userid

Explanation: The user ID entered as the recoverymachine or the user ID entered to receive dumps is avalid userid.



GCT122E ‘userid’ is not a valid userid

Explanation: The user ID must be valid in order toreceive dumps of common storage or be designated asthe recovery machine.


User response: Correct the user ID(s) in error.

GCT123I No userid has been specified to receivedumps

Explanation: Since no dumpid has been specified, thedumps of storage will default to the virtual machineoperator.



GCT124E No userid has been specified as therecovery machine

Explanation: You must identify a user ID as therecovery machine.


User response: Designate the recovery machine userID.

GCT125I The number of saved segment namesprocessed is nnnnn

Explanation: ‘nnnnn’ is the total number of savedsegment links that the system will attempt to link whenthis GCS group is IPLed. The saved segment lines aredefined in the group configuration file.



GCT126E No saved segment names have beenspecified

Explanation: No saved segments have been identifiedfor automatic linkage when this GCS group is IPLed.



GCT115I • GCT126E


GCT127E The number of invalid saved segmentnames on this page is nn

Explanation: At least one saved segment nameentered on the screen is not defined in the system.


User response: Correct the saved segment name(s)that are in error.

GCT128E There are nn overlapping valid segmentnames on all pages

Explanation: If nn is greater than zero, there areoverlapping segment names. The overlapping segmentnames on the viewed page are highlighted with arrows.Use PF10 on all pages to determine all overlappingsegment names.


User response: Use the QUERY NSS MAP commandto locate and correct the overlap error for the flaggedsegments.

GCT129T No virtual console attached. Re-IPLsysname.

Explanation: You have DETACHed your virtualconsole.

System action: The GCS system halts by issuing theCP command SYSTEM RESET.

User response: Define a virtual console with the CPDEFINE command, and re-IPL the named system.

GCT130T Virtual console not ready. Re-IPLsysname.

Explanation: Your virtual console is in a NOTREADYstate.


User response: Ready your virtual console with theCP READY command, and re-IPL the named system.

GCT132E Segment segname was not loaded. Thesegment does not exist or is restricted inthe directory

Explanation: The segment named in the message hasnot been defined or has been defined as restricted inthe CP directory.

System action: If the message occurs duringinitialization, then the segment is not linked to thevirtual machine and the system continues processing.

If the failure occurred while starting VSAM, the taskthat was in control at the time of the error is endedabnormally.

User response: Contact the system programmer, whowill generate the segment, supply a different segmentname, or add a NAMESAVE statement to yourdirectory entry.

GCT133E Paging I/O error for segment ‘segname’

Explanation: CP has encountered a PAGING I/O errorwhile attempting to read the segment name from adirect access storage device containing the segment.

System action: The segment is not linked to thevirtual machine. The system continues processing.

User response: If the problem persists after you re-IPLthe virtual machine, notify system support personnel.

GCT134I sysname available common storage isnnnnn KB BELOW and nnnnn KBABOVE the 16MB line

Explanation: This message is an output of the QUERYCOMMON command. The message specifies howmuch free common storage is available for GETMAINrequests above/below the 16 megabyte line.

System action: The system continues processing. Ifthere is not enough free common storage available forGETMAIN requests, problems may occur after thesystem is saved and subsequently IPLed.

User response: Check the system build documentationto make sure that you have the available free commonstorage that you need for this system.

GCT135T Group allocation exceeded for system‘sysname’

Explanation: The maximum number of virtualmachines that can join the group associated with thenamed system has been exceeded.


User response: Contact the system programmer. Themaximum number of virtual machines that can join thegroup is specified when the named system is built.

GCT136T Recovery machine ‘userid’ is not IPLed.System ‘sysname’ cannot be initialized.

Explanation: The recovery virtual machine for thisgroup has not been IPLed, or the GCS system has beenregenerated.


User response: Contact the system programmer. Therecovery machine for the group must IPL the namedsystem before other members of the group can IPL it. Ifthe system has been regenerated, all the machines in

GCT127E • GCT136T


the virtual machine group must re-IPL the GCS savedsegments.

GCT137I Generated at date time

Explanation: IPL informational message to display thecurrent date and time of the IPL that took place.



GCT138T This release of GCS requires a level ofCP which supports the year 2000.

Explanation: You attempted to IPL a GCS operatingsystem that requires a CP level that has year 2000support.

System action: Execution stops.

User response: Contact your system programmer.

GCT139T nnnnnnnn bytes needed for requestedtrace table size exceeds availablecommon free storage of mmmmmmmmbytes

Explanation: The trace table is allocated in freecommon storage. This message is displayed if the sizeof the trace table (displayed as ‘nnnnnnnn’ bytes)exceeds available free common storage (displayed as‘mmmmmmmm’ bytes).


User response: Make sure that you specified the righttrace table size. If the trace table size is correct youmust increase the size of available free commonstorage.

GCT140T sysname supervisor has terminatedbecause of an unrecoverable error.Virtual machine has been reset.

Explanation: The supervisor has encountered an errorfor which recovery may not be possible.

System action: The named system (sysname) uses CPmessages to display this message on both the user‘sand the system operator‘s consoles. The virtualmachine is dumped. The CP command ‘SYSTEMRESET’ is issued for this virtual machine, which causesa disabled wait PSW to be loaded.

User response: Re-IPL the named system (sysname onthe user ID for the virtual machine that RESET. If thefailure persists on subsequent IPLs, notify the systemprogrammer or the IBM Support Center for assistance.

GCT141S Recovery machine ‘userid’ for sysnamehas abnormally terminated

Explanation: The virtual machine that was designatedas the recovery machine has somehow been reset.

System action: The supervisor of the named systemuses CP messages to display this message on both theuser‘s and the system operator’s console. Thesupervisor will terminate, issuing message 140T, andthe virtual machine will be dumped.

User response: Have system support personnel re-IPLthe recovery machine, then re-IPL your virtual machine.

GCT142T Storage needed for Storage Managementexceeds available common free storage.Define more common storage.

Explanation: Storage management could not findenough common storage for its control blocks.


User response: Increase the size of common storage.

GCT143T Storage needed for Storage Managementexceeds available private free storage.Define more private storage.

Explanation: Storage management could not findenough private storage for its control blocks.


User response: Increase the size of private storage.

GCT144E Segment ‘segment’ not found|loaded,rc=‘nnn’

Explanation: An error occurred while the ControlProgram was processing a request from GCS to find orload a segment. Return code ‘nnn’ is returned by CP.

System action: The segment is not linked to thevirtual machine. The system continues processing.

User response: Contact the system programmer.

GCT145T Virtual machine size too small to savehigh common area.

Explanation: The high common area allocated in thegroup exec is not enough to save all the necessarycontrol blocks in it.

System action: The command is terminated.

User response: Correct the SHCOMMON size.


GCT146T Machine check encountered. MCIC:“machine check interrupt code”

Explanation: A machine check was encountered whichis not a channel report word type.

System action: The machine check is ignored and GCScontinues normal operation.


GCT147W Machine is in 370 mode; storage above16MB will be ignored.

Explanation: This is a 370 virtual machine so the sizewill be forced to 16 MB.



GCT148T Virtual machine mode different thanrecovery machine. Virtual machine hasbeen reset.

Explanation: All virtual machines in a GROUP musthave the same architecture mode; either System/370™

(370) or Extended Architecture (XA or ESA).

System action: Virtual machine is reset.

User response: Issue the CP SET command to changethe machine mode to agree with the recovery machineand reIPL.

GCT200S Console cannot be initialized - Re-IPLsysname

Explanation: The console cannot be opened for thenamed system (sysname) due to an I/O error.

System action: All virtual machines that have IPLedthe named system (sysname) will be reset.

User response: Re-IPL the named system (sysname) onthe user ID for the virtual machine that RESET.

GCT201S Permanent console error - Re-IPLsysname

Explanation: A permanent console error occurredwhile attempting to do I/O to the console.

System action: All virtual machines that have IPLedthe named system (sysname) will be reset.

User response: Re-IPL the named system (sysname) onthe user ID for the virtual machine that RESET.

GCT202I GCS

Explanation: GCS is the active operating system inyour virtual machine.


User response: None is necessary.

GCT203I Ready (nnnnn);

Explanation: The system has completed the commandthat was entered, but the command may not have beencompleted successfully. A return code from thecommand appears in the ‘nnnnn’ portion of themessage. Error or information messages with additionalinformation about the problem may have preceded thismessage. The system is ready for further input.


User response: Check the handling of the return codeand reissue the command if necessary. For moreinformation, refer to z/VM: CP Commands and UtilitiesReference.

GCT204S Recovery task abended

Explanation: An unrecoverable error occurred in therecovery task.

System action: All virtual machines for the entiregroup are terminated.

User response: Re-IPL the system on the user ID forthe virtual machine that RESET.

GCT205E Unknown CP/GCS command

Explanation: A command was transmitted to GCS orto CP but was not recognized.

System action: No action is taken; system status is notchanged.


GCT206E Reply not accepted, ID not specified

Explanation: A REPLY command was entered withoutan identification number.

System action: The REPLY command is ignored.

User response: Reissue the REPLY command with acorrect ID number specified.

GCT207E Reply not accepted, ID number not 00 to99

Explanation: A REPLY command was enteredspecifying an id not in the range of 00 - 99.



GCT146T • GCT207E


GCT208I Reply xx not outstanding

Explanation: A REPLY command was entered, butthere is no outstanding reply request with theidentification xx. Either the message request hasalready been answered, the message reply identificationxx is incorrect, or a reply was not being requested.

System action: The REPLY xx command is ignored.

User response: If the reply identification wasincorrect, correct and reissue the command.

GCT209E Reply xx not accepted, reply too long forrequestor

Explanation: A REPLY command was entered and thereply text was too long for the user‘s buffer. A REPLYtext can not be more than 119 characters long.


User response: Correct and reissue the REPLYcommand.

GCT210E Reply not accepted, invalid ECB address

Explanation: The WTOR to which the REPLYcommand is responding contains an invalid(inaccessible) ECB address in the parameter list.

System action: The WTOR issuer is abended. Theabend code is E23; the reason code is 1300.

User response: Make sure that parameter listaddresses are within the range of your storage. Formore information, see “GCS Abend Codes” on page 11.

GCT211E Reply not accepted, invalid reply bufferaddress

Explanation: The WTOR to which the REPLYcommand is responding contains an invalid(inaccessible) reply buffer address in the parameter list.

System action: The WTOR issuer is abended. Theabend code is D23; the reason code is 1300.

User response: Make sure that parameter listaddresses are within the range of your storage. Formore information, see “GCS Abend Codes” on page 11.

GCT212E Member cannot be loaded, commandnot defined RC=nn

Explanation: A LOADCMD command was entered,but an error occurred and one of the following returncodes was set:

Code Meaning

1 A LOADCMD already exists for the requestedname.

4 Module is marked “not executable.” Themodule is not loaded; the command is not

defined. To determine why the “notexecutable” flag was set, examine theinformation provided by the linkage editor atthe time the module was created. The moduleis not suitable to be used as a commandmodule.

10 Module is an overlay structure. The module isnot loaded; the command is not defined. If thisprogram is to be used as a command module,it must be restructured so that it does notrequire overlays.

12 Module is marked “only loadable.” Themodule is not loaded; the command is notdefined. This module is not suitable to be usedas a command module.

14 The command name specified is a GCSimmediate command or an abbreviation forone. A nucleus extension will not be created.

24 Too many or extraneous operands werespecified.

28 The specified member cannot be found.

32 No member name was specified.

36 A permanent I/O error was detected when thesystem attempted to search the directory.

40 Insufficient virtual storage was available forreading directory entry for this module.

41 There was not enough free storage to buildnucleus control blocks representing thecommand.

System action: Execution of the command isterminated. The command name is not defined to thesystem.

User response: Check return code reason. If user error,correct the problem if possible and reissue theLOADCMD command.

GCT213I Reply xx cancelled

Explanation: The program that issued a WTORrequest with the reply identifier ‘xx’ has abnormallyterminated. The reply that the program asked for istherefore no longer needed.



GCT214I No replies outstanding

Explanation: A QUERY REPLY command was entered,and there are no outstanding reply requests.



GCT208I • GCT214I


GCT215I The following replies are outstanding:

Explanation: A QUERY REPLY command was enteredcausing REPLY id numbers and texts to be listed.


User response: The REPLY command may be enteredwith a REPLY id and text in response to one of theoutstanding replies.

GCT216I GROUP ID = sysname, Users: Current =nnnnn, Maximum = mmmmm

Explanation: A QUERY GROUP command wasentered causing the system to provide the followinginformation:

sysname -the supervisor name of the group you arerunning under.

nnnnn -the current number of users in the group.

mmmmm -the maximum number of users allowed forthat group.



GCT217E The common lock is free

Explanation: The QUERY LOCK command wasentered, and the common lock is not held by anymachine.



GCT218I The common lock is held by userid

Explanation: The QUERY LOCK command wasentered, and the common lock is held by the user IDnamed in the message.



GCT219E PARM field contains more than 100characters

Explanation: The OSRUN command was issued witha parameter field of more than 100 characters.Parameters passed with the OSRUN command may notbe more than 100 characters in length.


User response: Reduce the parameter field to amaximum of 100 characters and reissue the OSRUNcommand.

GCT220E Unable to open file ‘fn’

Explanation: The system was unable to OPEN the fileidentified in the message.

System action: Dependent upon the module identifiedin the message prefix:

Prefix Action

GCTGLBThe system could not find the LOADLIBspecified in the GLOBAL command.Previously specified LOADLIBs are nullified.A return code of 28 is issued.

GCTLOSThe task that issued the OPEN endsabnormally with an abend code of 806 and areason code of 8. The abnormal end occursbecause the file directory could not be read, orwas read incorrectly.

User response: Re-IPL GCS. Make sure the filefilename LOADLIB exists, and try the operation again. Ifthe failure persists, contact your system programmer.

GCT221S More than nnn libraries specified

Explanation: No more than 63 load libraries may bespecified with a GLOBAL command.

System action: RC=88. Execution of the command isterminated, and any previous library list is cleared.

User response: Combine some libraries to reduce thenumber of libraries required for this terminal session.

GCT222E File ‘fn ft fm’ contains invalid recordformats

Explanation: The load library file named in themessage did not have ‘LIBPDS’ as the first sixcharacters in its header record. GCS can support onlyLIBPDS-format load libraries.

System action: RC=32. The load library named in themessage is not GLOBALed, and the system continueson to process the next LOADLIB in the GLOBALcommand, if any more LOADLIBS have been specified.

User response: Check the format of the LOADLIBnamed in the message, and convert it to LIBPDS formatif possible.

GCT223S Error ‘nn’ reading file ‘fileid’ from disk

Explanation: An I/O error occurred while READingfrom a disk.


Prefix Action

GCT215I • GCT223S


GCTGLBThe failure occurred while processing aGLOBAL command. Previously specified loadlibraries are nullified, and the command issuesa return code of 100.

GCTLOSThe task currently in control ends abnormallywith abend code 806 and reason code 8.

User response: Refer to the error code descriptionsbelow to find the correct message and possible cause ofthe error.

ALL DEVICES

Code Meaning

254 BSAM was called with an unposted ECBspecified.

DISK INPUT

Code Meaning

1 The file was not found.

2 The virtual storage area was not within thelimits of the virtual machine.

3 A permanent disk error occurred. This mayoccur if you link to and access another user'sdisk and try to read a file that was altered byits owner after you issued the ACCESScommand. Reissue the ACCESS command andtry to read the file again.

5 The number of items was zero.

7 The fixed/variable flag in FST entry was not For V.

8 The given storage area was smaller than theactual size of the item read. (This is arecoverable error: the number of bytes readcorresponds to the size of the buffer.)

11 The number of items is greater than 1 for avariable-length file.

12 An unexpected end of file occurred (the itemnumber specified exceeds the number of itemsin the file).

13 A variable-length file has an invaliddisplacement in the active file table.

25 Insufficient virtual storage is available.

26 Requested item number is negative, or theitem number plus the number of items exceedsfile system capacity.

If the problem cannot be resolved, contact your systemprogrammer or the IBM Support Center for assistance.

GCT224E Member ‘membername’ not found inlibrary

Explanation: The member name specified in theOSRUN command just issued could not be found dueto one of the following:

v None of the load libraries identified in the GLOBALcommand contained this member name; or,

v No load libraries were specified in the GLOBALcommand; or,

v No GLOBAL command was issued.

System action: The OSRUN command fails, and thetask abends with abend code 806 and reason code 4.

User response: Check the GLOBAL command to makesure that the needed libraries have been GLOBALed.Reissue the GLOBAL command if necessary and thenreissue the OSRUN command.

GCT225I HX Complete

Explanation: The HX command has completedprocessing.

System action: All active programs and commands inthe virtual machine have been terminated. Allcommands not yet executed have been purged.

User response: Enter new commands for execution.

GCT226E Application ‘name’ failed - System abendxxxx-yyyy

Explanation: The application program named in themessage, or a subtask of the program, failed with thespecified abend code (‘xxxx’) and reason code (‘yyyy’).

System action: The program or subtask has beenterminated. A dump may have been taken.

User response: For an explanation of the abend andreason code, see “GCS Abend Codes” on page 11.

GCT227E Application ‘name’ failed - User abendxxxx-0000

Explanation: The application program named in themessage, or a subtask of the program or command,failed with the specified completion code (‘xxxx’).

System action: The program or subtask has beenterminated. A dump may have been taken.

User response: Refer to application for definition ofcompletion code.

GCT228E Subtask of ‘name’ failed - System abendxxxx-yyyy

Explanation: A subtask of the program or commandfailed with the specified abend code (‘xxxx’) and reasoncode (‘yyyy’).

GCT224E • GCT228E


System action: The subtask has been terminated. Adump may have been taken.


GCT229E Subtask of ‘name’ failed - User abendxxxx-0000

Explanation: A subtask of the program or commandfailed with the specified completion code (‘xxxx’).

System action: The subtask has been terminated. Adump may have been taken.


GCT230E Command ‘command’ failed - Systemabend xxxx-yyyy

Explanation: The command named in the messagefailed with the specified abend code (‘xxxx’) and reasoncode (‘yyyy’).

System action: The command has been terminated. Adump may have been taken.


GCT231E Command ‘command’ failed - User abendxxxx-0000

Explanation: The command named in the messagefailed with the specified completion code (‘xxx’).

System action: The command has been terminated. Adump may have been taken.


GCT232E Abend xxx-yyyy occurred during abendESTAE processing

Explanation: An ESTAE exit routine failed, causing anabend.

System action: The failing exit is bypassed, and anyother exits are given control. No dump is taken.

User response: The condition of your virtual machinemay cause further failures; contact your systemprogrammer.

GCT233E Abend xxx-yyyy occurred during abendTASKEXIT processing

Explanation: A TASKEXIT exit failed, causing anabend.

System action: The failing exit is bypassed, and anyother exits are given control. No dump is taken for anyof these failures.


GCT234E Abend xxx-yyyy occurred during abendResource Manager processing

Explanation: The failure occurred while attempting torelease a task resource, such as GETMAINed storage oran open data set.

System action:

1. If the failure occurred during Resource Managerprocessing for a subtask of the failing task,termination will continue for the failing task.

2. If the failure occurred during Resource Managerprocessing for the failing task, or occurred duringABEND processing itself, the task is set asnondispatchable, and termination of that task ishalted.

No dump is taken for either of these failures.


GCT235E Abend xxx-yyyy occurred during abendinternal processing

Explanation: The ABEND itself failed.

System action: No dump is taken.


GCT236E Ending apostrophe is missing

Explanation: You did not include a closing apostrophein the parameter you passed in an OSRUN command.

System action: The OSRUN command terminates;system status remains unchanged.

User response: You can (1) reissue the command,adding a closing apostrophe to the parameter field, or(2) reissue the command, omitting the apostrophes,provided that there are no spaces or special charactersin the parameter you wish to pass.

GCT237E Command ended without detachingsubtasks

Explanation: A command or program ended normallybut without DETACHing those subtasks it created thatwere not ATTACHed with JSTCB=YES specified.

System action: The remaining subtasks areDETACHed.

User response: The program should be modified toDETACH all subtasks before ending.


GCT238I Ready;

Explanation: The system has performed the actionrequested by the user, or by an error message orinformation message appearing before this readymessage.



GCT239I No entry points are currently loaded inthis Virtual Machine

Explanation: The system has attempted to find allentry points loaded by the system and could not findany.



GCT240I No entry points were loaded by theLOADCMD command

Explanation: The system has attempted to find allentry points loaded by the LOADCMD command andcould not find any.



GCT243S Parameter list delimiter missing

Explanation: Tokenized plist is either missingdelimiter double word “FF” at the end or is too long(longer than 1K bytes).

System action: No action is taken on the command.The system status is not changed.

User response: The user program needs to have thedelimiter of double word “FF” at the end of the plistpassed to the command processing module.

GCT244I ‘userid’ is now the virtual machinereceiving dumps

Explanation: The user displayed will receive anydumps taken by the system.

System action: GCS processing continues normally.

User response: Verify that the user identification iscorrect.

GCT245I ‘userid’ can now IPL as an authorizedvirtual machine

Explanation: The user displayed will be added to thelist of authorized users in this GCS group. When theuser next IPLs into the group, the virtual machine willhave authorized status.



GCT246I ‘userid’ can no longer IPL as anauthorized virtual machine

Explanation: The user displayed will be deleted fromthe list of authorized users in this GCS group. Whenthe user next IPLs into the group, the virtual machinewill not have authorized status.



GCT247I The trace table is now being maintainedin ‘location’ storage.

Explanation: The GCS system will now place tracetable entries in storage (COMMON or PRIVATE) asindicated by the message. Previous entries are stillavailable in the other location.


User response: Verify that the location is correct.

GCT248I No users are currently authorized

Explanation: No users are currently in the authorizedlist for this GCS group.


User response: Verify that the list is correct.

GCT249E The recovery machine ‘userid’ must beauthorized

Explanation: An attempt was made to change theauthorization of the GCS recovery machine. Theauthorization has not been changed.


User response: Verify that the correct useridentification was given.

GCT250I User exit returned to GCS in accessregister mode. GCS will return to theuser in primary space mode.

Explanation: A user exit returned to the GCSsupervisor in access register mode.

System action: GCS switches to primary space modeand processing continues normally.

User response: The user exit should be changed toreturn to GCS in primary space mode.

GCT238I • GCT250I


GCT300S Control Program error indication ‘nnn’

Explanation: An unexpected error occurred while theControl Program was processing a request from GCS tofind or load a saved segment. Return code ‘nnn’ is fromDIAGNOSE X'64'. For more information, refer to z/VM:CP Programming Services.

System action: The task that was in control at the timeof the error ends abnormally with an abend code of036.

User response: Contact the installation's systemprogrammer for assistance.

GCT301E Invalid device ‘devname’

Explanation: The device specified is invalid.


User response: Reissue the command, specifying avalid device name.

GCT302E Parameter missing after DDNAME

Explanation: A parameter that is required by thecommand was not specified. For the FILEDEFcommand, a device name or DUMMY or CLEAR mustbe specified after the ddname. For the DLBL command,a disk mode or CLEAR must be specified after theddname.



GCT303I No user defined {FILEDEF|DLBL}'s ineffect

Explanation: A list of all FILEDEFs or DLBLs in effectwas requested, and no FILEDEFs or DLBLs have beendefined.

System action: No further action occurs; the commandis terminated.


GCT304I Invalid CLEAR request

Explanation: A CLEAR request was entered for a filedefinition that does not exist. No action was taken onthe command.


User response: Correct the file definition specified inthe CLEAR request.

GCT305I DDNAME ‘ddname’ not found. CLEARnot executed.

Explanation: A DLBL CLEAR command was enteredbut the ddname specified in the message was notfound.

System action: No action is taken on the command.

User response: Reissue the command with the correct‘ddname’ if ‘ddname’ was entered incorrectly.

GCT306S Input error ‘nnn’ on ‘ddname’

Explanation: If the prefix on the message is:

GCTSCTGCS issued this message because an inputerror was encountered by one of the following:

v An OS CLOSE macro

v An OS CHECK

v GET macro when a SYNADAF (erroranalysis) routine had not been specified bythe user.

GCTSERThis message was built by the simulationroutine for the SYNADAF (error analysis)macro. It was issued by a user SYNADroutine.

GCTXCPAn irrecoverable error occurred while readingfrom the disk named in the message. The errorcode may be one of the following:

Code Meaning

2 A unit exception occurred.

3 A record with an incorrect length wasdetected.

13 A permanent I/O error occurred. Thedisk is full.

Note: For message prefixes GCTSCT and GCTSER theerror code in the message identifies the specific error.For further information, look up the error code in theUser Response section below.

System action: If the message prefix is ‘GCTSCT’ or‘GCTSER,’ the current task ends abnormally with anabend code of 001. If the prefix is ‘GCTXCP,’ the taskends abnormally with an abend code of 038.

User response: Refer to the error code descriptionsbelow (for GCTSCT and GCTSER messages only) tofind the correct message and possible cause of the error.

ALL DEVICES

Code Meaning


GCT300S • GCT306S


DISK INPUT

Code Meaning

1 The file was not found.

2 The virtual storage area was not within thelimits of the virtual machine.

3 A permanent disk error occurred. This mayoccur if you link to and access another user'sdisk and try to read a file that was altered byits owner after you issued the ACCESScommand. Reissue the ACCESS command andtry to read the file again.

5 The number of items was zero.

7 The fixed/variable flag in FST entry was not For V.

8 The given storage area was smaller than theactual size of the item read. (This is arecoverable error: the number of bytes readcorresponds to the size of the buffer.)


12 An unexpected end of file occurred (the itemnumber specified exceeds the number of itemsin the file).

13 A variable-length file has an invaliddisplacement in the active file table.


26 Requested item number is negative, or theitem number plus the number of items exceedsfile system capacity.

CARD READER

Code Meaning

2 Intervention required. The virtual reader is ina NOTREADY condition or is SPOOLed withthe NOEOF option.

3 I/O operation was unsuccessful; accompaniedby message 029S or 030S.

5 The number of bytes read was less than thenumber of bytes requested.

8 The given storage area was smaller than theactual size of the item read. (This is arecoverable error; the number of bytescorresponding to the size of the buffer havebeen read.)

12 End of file.

100 No virtual reader defined at address X'00C';accompanied by message 28.

108 Device is not open.

112 Device is busy.

Note: All errors except 8 (above) cause execution of thecommand to terminate. Error 8 is valid if reading thefirst portion of a large record into a small buffer.

GCT307S Output error ‘nnn’ on ‘ddname’

Explanation: If the prefix on the message number is‘GCTSCT,’ GCS issued this message because anOUTPUT error was encountered (1) by an OS CLOSEmacro, or (2) by an OS CHECK or PUT macro when aSYNADAF (error analysis) routine had not beenspecified by the user. The error code in the messageidentifies the specific error. For further information,look up the error code in the table in the ‘UserResponse’ section below.

If the message prefix is ‘GCTSER,’ this message wasbuilt by the simulation routine for the SYNADAF (erroranalysis) macro; it was issued by a user SYNADroutine. The error code in the message identifies thespecific error. For further information, look up the errorcode in the table in the ‘User Response’ section below.

If the prefix is ‘GCTXCP,’ then an unrecoverable erroroccurred while writing to the disk named in themessage. The error code may be one of the following:

Code Meaning

2 A unit exception occurred.

3 A record with an incorrect length wasdetected.

13 A permanent I/O error occurred.

System action: The current task is terminatedabnormally with an abend code of 001 if the message isfrom module GCTSCT or GCTSER. The current task isterminated abnormally with an abend code of 038 if themessage is from module GCTXCP.

User response: Look up the error code in the tablebelow (for ‘GCTSCT’ and ‘GCTSER’ messages only) tofind the correct message and possible cause of the error.

ALL DEVICES

Code Meaning


DISK OUTPUT

Code Meaning

2 The virtual storage address is zero.

4 The first character mode was invalid.

5 The second character mode was invalid.

7 An attempt was made to skip over anunwritten variable-length item.

8 The number of bytes was not specified.

11 The fixed/variable flag was not F or V.

GCT307S


12 The disk is either not accessed or it aread-only disk.

13 The disk is full.

14 The number of bytes to be written is notintegrally divisible by the number of recordsto be written.

15 The length of this item is not the same as theprevious item.

16 The fixed/variable flag is not the same as thatof the previous record.

17 A variable-length item is greater than 65,535bytes.


20 An invalid character was detected in the filename.

21 An invalid character was detected in the filetype.

22 Virtual storage capacity has been exceeded.


26 Requested item number is negative, or itemnumber plus number of items exceeds filesystem capacity.

PRINTER

Code Meaning

1 The buffer size is too large.

2 Channel 12 was sensed (virtual 3211-typeprinters only).

3 Channel 9 was sensed (virtual 3211-typeprinters only).

4 Intervention required. The device is in aNOTREADY condition. Accompanied bymessage 346S.

5 I/O operation was unsuccessful. Accompaniedby message 029S or 030S.

100 No virtual printer defined at address X‘00E’.Accompanied by message 028S.

CARD PUNCH

Code Meaning

2 Intervention required. The virtual punch is ina NOTREADY condition. Accompanied bymessage 346S.

3 I/O operation was unsuccessful. Accompaniedby message 029S or 030S.

100 No virtual punch defined at address X‘00D’.Accompanied by message 028S.

108 Device is not open.

112 Device is busy.

GCT308E OPEN error ‘nn’ on ‘ddname’

Explanation: An error occurred during an OS OPEN.

System action: The task ends abnormally with anabend code of 013. The DCBOFLGS OPEN bit is notturned on and the DCB is not initialized.

User response: Using the error code table below andthe ddname displayed in the message, check theassociated FILEDEF command and DCB macro forinvalid or missing DCB options.

Code Meaning

1 Invalid DSORG specified. Only PS issupported.

2 A default FILEDEF for the ‘ddname’ displayedin the message was issued. The defaultFILEDEF failed.

3 RECFM does not agree with the format of theexisting file. One RECFM is F and the other isV.

4 No LRECL OR BLKSIZE value was specifiedin the DCB or FCB, and the file does not exist.

5 (1) The DCB BLKSIZE is not a correct multipleof the DCB LRECL, or (2) the DCB specifieswriting blocked output, but only unblockedrecords are permitted on the I/O device (i.e.reader).

6 (1) RECFM is fixed and LRECL does not agreewith the record length of the existing file, or(2) RECFM is variable length and LRECL isnot 4 bytes greater than the record length ofthe existing file, or (3) BLKSIZE is not amultiple of LRECL.

11 I/O option ‘UPDATE’ is invalid for a filefound on a read-only extension. Output filewith DISP = MOD means update, so it maynot exist on a read-only extension.

13 There is insufficient storage available toprocess the OPEN macro instruction.

15 The OPEN macro instruction was issued for afile allocated to a virtual unit record devicethat has not been defined. Either define thedevice, or allocate the file to a different device.

16 The OPEN macro instruction was issued for afile allocated to a virtual unit record devicethat already has an open file on it. Make surethat the first file is closed before the second isopened, or allocate the file to a differentdevice.

GCT308E


17 Invalid OPEN option specified. Valid options:INPUT, OUTPUT, and UPDAT. DISP isignored.

18 An invalid device was specified. I/O issupported for disk, dummy, printer, punch,and reader.

19 INPUT or UPDAT option was specified, butthe DCB did not specify a MACRF of GET orREAD.

20 OUTPUT option was specified, but the DCBdid not specify a MACRF of PUT or WRITE.

21 (1) The LRECL value was greater than themaximum allowed, which is 32,760 bytes forfixed-length logical records, or 32,752 bytes + 4bytes for the record descriptor word (RDW)for variable-length records, or (2) LRECL=Xwas specified.

22 (1) The BLKSIZE value was greater than themaximum allowed (32,760 bytes forfixed-length logical records; 32,752 bytes + 4bytes for the block descriptor word (BDW) forvariable-length records), or (2) The BLKSIZEvalue was less than the minimum value forvariable-length logical records (8 bytes).

80 Only CMS formatted disk I/O is supported.OS or DOS formatted disk I/O is notsupported.

GCT308W OPEN error ‘nn’ on ‘ddname’

Explanation: An error occurred during an OS OPEN.

System action: The DCBOFLGS OPEN bit is notturned on and the DCB is not initialized.

User response: Using the error code table below andthe ddname displayed in the message, check theassociated FILEDEF command and DCB macro forinvalid or missing DCB options.

Code Meaning

12 The OUTPUT option was specified, but thedisk is not accessed as a read/write disk.

23 The INPUT option was specified, but theassociated file does not exist.

GCT309E CLOSE error ‘nn’ on ‘ddname’

Explanation: An error occurred during an OS CLOSE.

System action: The task ends abnormally with anabend code of 014.

User response: Check the error code and ddnamedisplayed in the message with the table below, andmake the appropriate changes.

Code Meaning

1 The unit record device that the file wasallocated to was not opened.

3 There is insufficient storage available toprocess the CLOSE macro instruction.

4 An invalid device was specified. I/O issupported for disk, dummy, printer, punch,and reader.

GCT310R Enter data set name:

Explanation: A DLBL command was entered with the? or DSN ? operand. The command requires that aVSAM data set name be entered.

System action: The command waits for a response.

User response: Use the REPLY command to supplythe requested information.

GCT311E Invalid data set name

Explanation: An invalid VSAM data set name wasspecified in the DLBL command line.

System action: RC=24. No action is taken on thecommand and system status is not changed.

User response: Reissue the DLBL command with avalid data set name.

GCT312R Enter volume specifications:

Explanation: The system expects you to enter VSAMdata set volume specifications because you specifiedthe MULT option of the DLBL command.

System action: Execution of the command is delayeduntil you respond to the specification request. If a nullline is the first response, an error message(GCTDLB021E) is displayed and the DLBL commandhas no effect. Otherwise, a null response after one ormore lines of data signifies the end of thespecifications.

User response: Enter data set volume specificationsusing the REPLY command. The data may be enteredon one line separated by commas, or may be enteredon separate lines. The final comma at the end of theline is optional and may be omitted. The data enteredis the file mode for each disk. Do not repeat the filemode specified in the command line.

GCT313E Invalid ddname ‘ddname’

Explanation: The ddname specified in the DLBLcommand is invalid.


User response: Reissue the DLBL command with avalid ddname. The ddname may not be more than 7characters long.


GCT314I Maximum number of disk entriesrecorded

Explanation: The DLBL command just enteredspecified the maximum number of disks allowed for amultivolume VSAM data set.

System action: Execution of the command isterminated; the data set definition is stored.


GCT315E Catalog DDNAME ‘ddname’ not found

Explanation: The user catalog ‘ddname’ referenced bythe CAT option has not been defined by a previousDLBL command.

System action: Execution of the command isterminated. The definition does not take effect.

User response: Either:

1. Reissue the command specifying the CAT optionwith a previously defined ddname; or

2. Issue a DLBL command for the user catalogddname and then reissue the DLBL command forthe data set you have defined.

GCT316E mode disk is in CMS format; Invalid forVSAM data set

Explanation: The DLBL command issued includes theDSN operand. This indicates the data set is in VSAMformat, but the disk identified in the DLBL command isin CMS format. References to the disk in the DLBLcommand include not only the disk mode in thecommand line, but also the mode in the MULTspecifications.

System action: The command or program isterminated with no change to the DLBL definitions ineffect. If the message prefix was GCTVIP, the task isterminated with an abend code of 37.

User response: Reissue the ACCESS and DLBLcommands using a disk formatted for use with VSAMdata sets.

GCT317I Job catalog DLBL cleared

Explanation: The DLBL for the job catalog has beencleared and is no longer active.

System action: If the job catalog is cleared, all otherdefinitions flagged as using the job catalog are nolonger flagged as such. This message can be the resultof a DLBL * CLEAR or DLBL IJSYSUC CLEAR.


GCT318I Master catalog DLBL cleared

Explanation: The DLBL for the master catalog hasbeen cleared and is no longer active.

System action: The message can be the result of aDLBL * CLEAR or DLBL IJSYSCT CLEAR.


GCT319S Unexpected error code nn on vdev

Explanation: An error occurred during EXCPprocessing for a VSAM data set. The error codeindicates the type of error that occurred.

System action: Execution of the current task isterminated with an abend code of 039.

User response: Check the error code displayed in themessage with the table below, and make theappropriate changes.

Code Meaning

5 No Active Disk Table (ADT) was found.

8 The disk is in neither OS nor DOS format.

GCT320E Error during filedef clear processing,DCB(s) not closed.

Explanation: A “FILEDEF ‘DD’ CLEAR” or “FILEDEF* CLEAR” was issued before the corresponding DCB(s)was closed.

System action: RC=40. For “FILEDEF ‘DD’ CLEAR”the command terminates and the system status is notchanged. If the “FILEDEF * CLEAR” was issued, thenall non-permanent FILEDEF entries with closed DCB'swill be cleared.

User response: Issue a QUERY FILEDEF command todisplay all FILEDEFs in effect. Close the associatedDCB(s) and reissue the command.

GCT321E Saved system name ‘sysname’ invalid.Only GCSVSAM or GCSBAM isallowed.

Explanation: An attempt was made, using the SETcommand, to change a SYSNAME that is not supportedby GCS. The BAM (GCSBAM) and VSAM (GCSVSAM)saved segments are the only saved segments that canbe manipulated via the SET command.


User response: Reissue the command using GCSBAMor GCSVSAM as the SYSNAME.

GCT314I • GCT321E


GCT322E New system name missing after name

Explanation: SET SYSNAME was issued for GCSBAMor GCSVSAM but no new system name was specified.


User response: Reissue the command specifying anew system name.

GCT323E Parameter missing on command

Explanation: SET SYSNAME was issued without anyother parameters.


User response: Reissue the command specifying allrequired parameters.

GCT325E Number of VSAM exit routines hasexceeded maximum of 128. Unable tocontinue.

Explanation: The number of exit routines for VSAMdata sets (both active and inactive) has exceeded themaximum of 128 allowed for this virtual machine.

System action: The active task is terminated with anabend code of 03A.

User response: Reduce the number of exit routines forVSAM data sets and re-execute the program.

GCT326E OPEN error on ‘ddname’: Possiblevolume error. See VSE/VSAMdocumentation for OPEN error codecode.

Explanation: The call to VSE/VSAM results in anerror code indicating that a problem could exist withthe volume on which the file resides.

System action: The current task ends abnormally withan abend code of 035.

User response: Consult the VSE/VSAMdocumentation, correct the error, and re-execute theprogram.

GCT327E OPEN error on ‘ddname’: Possible userprogramming error. See VSE/VSAMdocumentation for OPEN error code code

Explanation: The call to VSE/VSAM results in anerror code indicating that an error in your programmay have caused an error in processing.


User response: You may have issued an ACCESScommand after a DLBL command, in which case you

must reissue the DLBL command. Otherwise, consultthe VSE/VSAM documentation, correct the error, andre-execute the program.

GCT329E OPEN error on ‘ddname’: Possible catalogerror. See VSE/VSAM documentationfor OPEN error code code.

Explanation: The call to VSE/VSAM results in anerror code indicating that an error exists in thespecified catalog.



GCT330E OPEN error on ‘ddname’: Possible systemerror. See VSE/VSAM documentationfor OPEN error code code.

Explanation: The call to VSE/VSAM results in anerror code indicating that there is a serious error inGCS support of VSAM.



GCT331E CLOSE error on ‘ddname’: Possible userprogramming error. See VSE/VSAMdocumentation for CLOSE error codecode.




GCT332E CLOSE error on ‘ddname’: Possiblesystem error. See VSE/VSAMdocumentation for CLOSE error codecode.

Explanation: The call to VSE/VSAM results in anerror code indicating that there is a serious error inGCS support of VSAM.


User response: Consult the VSE/VSAM

GCT322E • GCT332E


documentation, correct the error, and re-execute theprogram.

GCT333E Error in request macro processing:Possible user programming error. SeeVSE/VSAM error code code. Return codecode.




GCT334E Error in request macro processing:Possible system error. See VSE/VSAMerror code code. Return code code.

Explanation: The call to VSE/VSAM results in anerror code indicating that there is a serious error inGCS VSAM support.



GCT335S Internal error during VSAM processing:name1 name2 function(s) not supported

Explanation: An internal error was detected in theGCS code that supports VSAM.


User response: Contact IBM support personnel.

GCT336S Internal error during VSAM processing:Illegal use of SVC 11




GCT337S Internal error during VSAM processing:Unsupported SVC svc (Hex xx) calledfrom vstor




GCT338S Internal error during VSAM processing:Invalid form of SVC svc (Hex xx) calledfrom vstor


System action: The current task ends abnormally witha abend code of 039.


GCT339S Internal error during VSAM processing:Unsupported function function of SVCsvc (Hex xx) called from vstor




GCT340S Internal error during VSAM processing:Unsupported form of name macro




GCT341S Internal error during VSAM processing:Phase name not found




GCT342S Internal error during VSAM processing:Unexpected error code ‘nn’ on vdev



User response: Check the error code with the tablebelow to determine the error, and contact IBM supportpersonnel.

Code Meaning

1 No CCW address in CCB

GCT333E • GCT342S


2 Device is unassigned

3 Device is unsupported

4 Invalid CCW

7 No console CCW

9 Track condition check encountered

GCT343S Internal error during VSAM processing:Invalid device class devclass for devtype


System action: The current task ends abnormally witha abend code of 039.


GCT344I VSAM IDUMP taken date time

Explanation: VSE/VSAM has initiated a dump for apotential problem situation.

System action: A dump is taken and processingcontinues.

User response: Consult VSE/VSAM manuals forinformation relative to IDUMPs.

GCT345E No option specified

Explanation: The indicated option was entered in anincomplete form on the DLBL command.


User response: Reissue the command specifying therequired data for the option.

GCT346S Intervention required on device vdev

Explanation: The specified device cannot perform therequested I/O operation because it is in a NOTREADYcondition.

System action: If the user‘s SYNAD exit was specifiedin the DCB, it will be executed. Otherwise, message306S or 307S is issued and the task is abnormallyterminated with abend code 001.

User response: READY the specified device.

GCT347R Enter response:

Explanation: VSE/VSAM is waiting for a responsefrom the terminal operator.

System action: The requesting task waits for aresponse.

User response: VSE/VSAM indicated the nature of therequested data in a previous message. Use the REPLYcommand to provide the requested data.

GCT348E Open error nn

Explanation: An error occurred during OS OPENmacro processing. A ddname is not specified because ofthe nature of the error.

System action: The task is terminated abnormallywith an abend code of 013.

User response: Check the error code displayed in themessage, and make the appropriate changes.

Code Meaning

14 An address that was specified by the user wasinvalid. Or, the DEB address in the DCB wasinvalid.

GCT349E Close error ‘nn’

Explanation: An error occurred during an OS CLOSE.A ddname is not specified because of the nature of theerror.

System action: The task ends abnormally with anabend code of 014.

User response: Check the error code displayed in themessage in the table below, and make the appropriatechanges.

Code Meaning

2 (1) A CLOSE macro instruction was issued,and an address that was specified by the userwas invalid (possibly the DCB address); or

(2) the DEB address in the DCB is invalid. Thiscan occur if the DCB DEB address ismaliciously changed, or if two tasks aresharing the same DCB, and the task that closesthe DCB is not the task that opened the DCB.

GCT350S Internal error during VTAM processing:Module ‘module’ not found.

Explanation: The module that handles VTAM ControlBlock Manipulation requests could not be found.

System action: The current task is ended abnormallywith an abend code of 036.

User response: VTAM is not installed on your system,or it has not been installed correctly. Contact yoursystem support personnel.

GCT351E System name not changed. VSAMalready initialized.

Explanation: The VSAM system names cannot bechanged because VSAM has already been initialized. Atleast one VSAM macro has been issued since the lastIPL, and VSAM may be in use. VSAM system names

GCT343S • GCT351E


can be changed only before VSAM is initialized.

System action: Execution of the SET command isterminated. System status is unchanged.

User response: If you wish to change the systemnames for VSAM, re-IPL GCS and issue the SETcommand before starting any VSAM programs.

GCT352E Invalid DDNAME specified

Explanation: A 'FILEDEF ' was issued with an invalidDDNAME. Either that DDNAME is being used byanother task and the 'NOCHANGE ' option was notspecified, or a DCB is already open using the FCB withthat DDNAME and the 'NOCHANGE ' option was notspecified.

System action: RC = 24

User response: Either change the DDNAME given inthe 'FILEDEF ' command, or reissue the 'FILEDEF 'command with the 'NOCHANGE ' option.

GCT353S The VSAM/BAM segment can notoverlap the top of the virtual machine

Explanation: When the GCS GROUP exec was run,your virtual machine was not specified as a user ofVSAM. Thus storage was not reserved for yourmachine at IPL time. Since you tried to use GCSVSAM, GCS tried to obtain storage for you, but yourvirtual machine size was defined so that storage couldnot be obtained.

System action: Task will abend.

User response: Case 1. If you are using theVSAM/BAM segments defined in the GROUP EXEC tobe used by your GCS group, (default is CMSBAM andCMSVSAM), all you need to do is re-IPL, storage forthese segments will automatically be reserved for you.

Case 2. If you are using your own VSAM/BAMsegments as declared by the SET function, redefineyour virtual machine size to be less then the startingaddress of both the segments and then re-IPL.

GCT354S Storage can not be reserved for yourversion of the VSAM/BAM segment asrequested by the set command

Explanation: Your version of the BAM/VSAMsegments as declared by the SET function could nothave storage reserved for it inside your virtualmachine. The storage was already in use.

System action: Task abends.

User response: Redefine your virtual machine size tobe less then the starting address of both the segmentsand then re-IPL.

GCT355S Storage has not been reserved for yourvirtual machine for the BAM or VSAMsegment by the GROUP exec.

Explanation: Your machine was not listed as amachine requiring storage to be reserved for it for theVSAM and BAM segments.

System action: Task will abend.

User response: Re-IPL. Storage for these segments willbe automatically reserved for you. However, storagewill not be reserved for segments specified by the SETcommand.

GCT356I The VSAM segment was not builtcorrectly or could not be found

Explanation: The VSAM segment that you defined inthe GCS GROUP exec does not exist or it was not builtas part of a compact segment space.

System action: IPL will continue, but storage will notbe reserved for the VSAM segment and VSAM will notbe available for use.

User response: If you need to run a VSAM job, youwill need to build a "compact" segment spacecontaining the VSAM segment and re-IPL.

GCT360I Dumplock = ‘setting’

Explanation: This message is given in response to theGCS QUERY DUMPLOCK command. It indicated thestate of the dumplock. The ‘setting’ may be ON or OFF.



GCT361I Dump = ‘setting’

Explanation: This message is given in response to theGCS QUERY DUMP command. It indicated the state ofthe dump facility. The ‘setting’ may be ON, OFF, orDEFAULT.



GCT362I Dump Suppressed

Explanation: Dumps are suppressed via the SETDUMP OFF command.

System action: GCS processing continues.



GCT363E Dump suppressed via SET DUMP OFFcommand

Explanation: A requested GDUMP was not takenbecause dumps are suppressed via the SET DUMP OFFcommand.

System action: GDUMP ends with a return code of 20.

User response: Issue the SET DUMP ON commandthen reissue the GDUMP.

GCT364I IPOLL = ‘setting’

Explanation: This message is given in response to theGCS QUERY IPOLL command. It indicated if the IUCVIPOLL subfunction is being used for this virtualmachine. ‘setting’ may be ON or OFF.



GCT365I Address of ‘variable’ is ‘address’

Explanation: This message returns the address of theGCS module or table requested.



GCT400T Program Exception code occurred at vstorin system routine routine. Re-IPLsysname.

Explanation: The specified hardware exceptionoccurred in a GCS system routine.

System action: The GCS system halts. Execution of thecommand is terminated.

User response: Contact your system supportpersonnel, or re-IPL the names system and try theoperation again.

GCT401I Directory error encountered duringinitialization of the IUCV environment

Explanation: An IUCV error occurred while thesystem was trying to initialize the virtual machine‘sIUCV environment. No IUCV functions can beperformed. The most likely cause for this error messageis that CP was unable to read the virtual machinedirectory.


User response: Have the system checked for hardwareerrors.

GCT402I An IUCV GETMAIN error occurredwhile trying to obtain storage forsysname IUCV initialization

Explanation: The virtual machine‘s IUCV environmentcould not be initialized because of a GETMAIN failure.No IUCV functions can be performed.


User response: Determine the cause of the GETMAINfailure and re-IPL the named system.

GCT403I An IUCV CONNECT error occurredwhile trying to connect to CP SignalServices. IPRCODE = xx.

Explanation: The system was unable to set up acommunications path to CP Signal Services. A nonzerovalue was returned in the IPRCODE field of the IUCVCONNECT parameter list.


User response: Look up the IPRCODE specified in themessage in the IUCV return codes table in z/VM: CPProgramming Services. Then correct the problem andre-IPL the system.

GCT404E Retry will be attempted in 15 seconds;PROP is not active in Virtual Machineuserid

Explanation: The PMX encountered an IUCV errorwhen attempting to connect to the virtual machine withthe specified user ID. This message is always precededby message 405E, which indicates the type of IUCVerror encountered. The PMX performs this RETRYoperation up to 10 times, or until the connection issuccessfully established.

System action: The PMX waits 15 seconds and thentries to establish the IUCV connection again. ThisRETRY process is repeated up to 10 times, or until anIUCV connection is established. If all 10 attempts fail,the PMX terminates.

User response: Wait for 15 seconds and see if the nextattempt fails, or terminate the PMX and restart itspecifying the user ID of the virtual machine runningthe programmable operator facility.

GCT405E An IUCV error occurred while trying toconnect to PROP virtual machine.IUCVCOM return code = code

Explanation: Sent when the PMX cannot get an IUCVconnection with the programmable operator.

System action: The program terminates.

User response: Use the specified code to determinethe problem and retry.

GCT363E • GCT405E


GCT406E PMX has abended and will now take adump and wait for NCCF termination.Abend code = xxx

Explanation: Indicates that an abend occurred in thePMX.

System action: The PMX enters a dormant state,waiting for NetView or NCCF to terminate.

User response: Use the specified code along with thedump to determine the problem.

GCT407E PROP has terminated or abended. Thecommand is not accepted.

Explanation: Sent when the NetView or NCCFoperator tries to issue a programmable operatorcommand after the programmable operator has beenterminated due to “STOP” or abend; or, theprogrammable operator has QUIESCEd the path fortermination cleanup.

System action: The operation is not performed.

User response: Notify the appropriate personnel.

GCT408E PMX has not been started. Thecommand is not accepted.

Explanation: Sent when the NetView or NCCFoperator tries to issue a programmable operatorcommand but the PMX was never invoked.


User response: Notify the appropriate personnel.NetView or NCCF must be CLOSEd and the PMXinvoked for a network management operator tocommunicate with the programmable operator.

GCT409E An IUCV error occurred while trying toSEND to PROP virtual machine. Thecommand is not accepted. IUCVCOMreturn code = nnnn

Explanation: Sent when a NetView or NCCF operatorhas issued a programmable operator command but itcannot be sent to the programmable operator via IUCVbecause the message limit on the path has beenexceeded.


User response: Try the operation again and/or notifythe appropriate personnel of the condition.

GCT410I PROP has resumed activity

Explanation: Sent to the NetView or NCCF logicaloperator, if any, when it is determined that theprogrammable operator has been restarted after anabend.



GCT411I PROP has abended

Explanation: Sent to the NetView or NCCF logicaloperator, if any, when it is determined that theprogrammable operator has abended and cannot acceptcommands.



GCT412I PROP has stopped

Explanation: Sent to the NetView or NCCF logicaloperator, if any, when it is determined that theprogrammable operator has been stopped and cannotaccept commands.



GCT413I PMX has terminated

Explanation: Sent to the NetView or NCCF logicaloperator, if any, and to the GCS console when the PMXterminates.



GCT414E Disk ‘vdev’ not properly formatted forACCESS

Explanation: The disk being ACCESSed has other thana 512, 1KB, 2KB or 4KB block size.

System action: RC=16. Execution of the command isterminated.

User response: Reformat the disk using the FORMATcommand under CMS, specifying a BLOCKSIZE of 512,1KB, 2KB, or 4KB. Then re-IPL GCS and reissue theACCESS command.

GCT415E Invalid device address ‘vdev’

Explanation: The device address was not specifiedcorrectly, or the device was not accessed.


User response: Check the device address and reissuethe command.

Note: A valid address is any address within the rangeX'001' through X'FFF'.

GCT406E • GCT415E


GCT416E No device specified

Explanation: The command requires that you specifya device address or mode letter.


User response: Reissue the command, specifying avalid device address or mode letter.

GCT418E Insufficient free storage available. Thecommand is not accepted.

Explanation: Sent to the GCS console or to therequesting NetView or NCCF operator when the PMXcannot obtain the storage required for buffers andcontrol blocks.



GCT419E PMX has abended. The command is notaccepted.

Explanation: Sent when a NetView or NCCF operatortries to issue a programmable operator command butthe PMX has abended.



GCT420T File system error detected. Virtualaddress ‘vdev’. Reason code ‘nn’

Explanation: An error detected indicates the GCS filesystem may be disoriented with respect to the disk thathas the virtual address ‘vdev’. ‘nn’ is a code indicatingthe nature of the error. It may be one of the following:

Code Meaning

1 No active-disk-table block was found wheremode-letter was supplied. The error wasdetected in module GCTDIO.

3 Three problems could have produced thiserror code:

v An error was detected in trying to readfrom or write on a disk. Probably the diskwas detached (with the use of the DETACHcommand) without being released first (withthe use of the RELEASE command), or thedisk is an unsupported device.

v A deallocation was attempted on anonallocated disk block.

v A read/write operation was attempted to adisk block number zero.

4 One of the following occurred:

v The cylinder number is not within the rangeof user‘s disk.

v A deallocation was attempted on anonallocated disk block.

5 The cylinder number received by the ControlProgram is not in the user‘s range, or anattempt was made to access file record zero.

6 An attempt was made to write on a read-onlydisk.

8 Three explanations are possible:

v A channel programming error occurred.

v A deallocation was attempted on a blockoutside the range of the disk structure.

v A read/write operation was attempted witha byte count of zero.

13 An I/O error occurred during a read/writeoperation to an FB-512 device.

18 A parameter list (plist) error was encounteredduring a truncate operation.

19 A storage error occurred during a truncateoperation.

1C The file or ADT for a truncate operation wasnot found.

24 The file to be truncated was located on a R/Odisk.

25 A storage error occurred during a read/writeoperation.

28 An error occurred in module GCTFNS duringa truncate operation.

2C Inconsistent V-Format pointers detected duringa truncate operation.

41 No free block is available for allocation. Youcan recover files from this disk if you access itas read-only under CMS and copy the desiredfiles to another disk.

42 A parameter list error occurred.

45 The cylinder number received by the ControlProgram is not in the user‘s range, or anattempt was made to access file record zero.

System action: The system enters a disabled waitstate. The user file directory is not updated.

User response: Re-IPL GCS and then reissue thecommand if data on the pack is still good. Contact yoursystem support personnel if the problem persists.

GCT421S Disk ‘mode (vdev)’ is full

Explanation: No more disk space is available on theminidisk identified in the message.

System action: RC=13. The last attempted write to thedisk is terminated, and the task that attempted the

GCT416E • GCT421S


write is terminated. The system will attempt to CLOSEany OPEN files belonging to that task.

User response: IPL CMS and try to create more diskspace by deleting unneeded files. Then re-IPL GCS andrun the program again. For more information onresolving disk space problems, refer to z/VM: CMSUser's Guide.

GCT422E ‘vdev’ already accessed as Read/Write‘mode’ disk

Explanation: You are trying to access the specifieddevice in read-only mode, but you have alreadyaccessed it in read/write mode. You cannot have a diskaccessed as both read-only and read/write, because theread-only file directory would not reflect any updatesyou made until the next time you accessed the disk.


User response: If you wish to access the specifieddevice in read-only mode, first release the disk byissuing the RELEASE command and then reissue theACCESS command.

GCT423I mode (vdev) {R/O|R/W} [-OS|-DOS]

Explanation: The disk identified in the message hasbeen accessed in read-only mode or in read/writemode, as indicated. An ‘-OS’ or ‘-DOS’ at the end of themessage means that the disk is OS or DOS formatted. Ifthe ‘-OS’ or ‘-DOS’ do not appear, then the disk is inCMS format.

Note: A read/write OS or DOS disk can be written ononly by VSAM.



GCT424I ‘vdev mode’ released

Explanation: The specified device was previouslyaccessed as a read/write disk with the mode letterindicated in the message. This device has now beenreleased since the user has accessed the same device asa read/write disk with a different mode letter.



GCT425I ‘vdev’ replaces ‘mode (vdev)’ [-OS|-DOS]

Explanation: The disk being accessed replaces a diskpreviously accessed as the same mode letter. The diskbeing replaced is released, but it is not detached.



GCT426I ‘vdev’ also = ‘mode’ [-OS|-DOS] disk

Explanation: The disk identified in the message is alsoaccessed as the ‘mode’ disk. If an ‘-OS’ or ‘-DOS’appears at the end of the message, the disk isformatted as an OS or DOS disk. If ‘-OS’ or ‘-DOS’ donot appear, then the disk is formatted as a CMS disk.



GCT427S ‘mode (vdev)’ device error

Explanation: An error is encountered when trying toaccess the disk. This is because it is an unsupporteddevice, or an I/O error occurred while reading in themaster file directory from the device. The device inerror may contain more than the maximum 32767cylinders that CMS/GCS supports.

System action: RC=100. Execution of the command isterminated. The system status remains the same unlessanother disk was replaced by this access, as indicatedby message GCTACC425I.

User response: If this is the first time you used thisdisk, use the FORMAT command under CMS to formatit, and then reissue the command under GCS. If theproblem persists, contact your system supportpersonnel.

GCT428S ‘mode (vdev)’ not attached

Explanation: The specified device is not attached tothe virtual machine.


Prefix Action

GCTACCThe execution of the ACCESS command thatwas issued is halted. The system statusremains the same unless another disk wasreplaced by this access, as indicated bymessage GCTACC425I. The return code is 100.

GCTGRPYour A-disk is detached. This could havehappened while you were running theGROUP EXEC, or even before you invoked theGROUP EXEC. As a result, the exec cannotcreate the GROUP EXEC file for your GCSsystem. The exec will continue running toallow you to LINK your A-disk from thecommand line.

User response: To complete an ACCESS operation, usethe CP LINK command to attach the missing disk toyour virtual machine, or ask the system operator toattach the disk to your machine. Then reissue theACCESS command.

GCT422E • GCT428S


To finish running the GROUP EXEC, LINK your A-diskfrom the command line. You can then finish runningthe exec in the normal way.

GCT429E File ‘fn ft fm’ not found. Disk ‘mode(vdev)’ will not be accessed.

Explanation:

v The files requested were not on the specified disk.

v If the disk you are trying to access contains no filesand you are trying to access it as a read-only disk,then your disk access has failed.

If another disk was already accessed as mode ‘fm’, it isreleased.

System action: RC=28. Execution of the command isterminated. System status is not changed.

User response: Check to see that the file ID isspecified correctly, and reissue the command.

GCT430W OS disk - Fileid specified is ignored

Explanation: The OS or DOS disk identified in theACCESS command just issued has been accessed, butthe file ID provided in the command is not applicableand has been ignored.

System action: RC=4. Execution of the commandcontinues.


GCT431T SEVER external interrupt has occurredon the Signal Services Path, Re-IPLsysname.

Explanation: An IUCV External Interrupt hasoccurred. This interrupt was a SEVER on the SignalServices Path.

System action: The GCS system halts by loading adisabled wait state PSW. Execution of the command isterminated.

User response: Re-IPL the named system. Contactyour system support personnel if further failures occur.

GCT432T Program exception code occurred at vstorwhile no task active, Re-IPL sysname

Explanation: The specified hardware exceptionoccurred in a GCS system routine.

System action: The GCS system halts by loading adisabled wait state PSW. Execution of the command isterminated.

User response: Contact your system supportpersonnel or re-IPL the named system.

GCT433S The GCS system's IUCV general exitreceived control

Explanation: The general exit established for the GCSsystem's IUCV connections has received control. Thereare no functions supported by this exit.

System action: The system ignores the incorrect IUCVusage that caused the general exit to receive control.

User response: If this message persists, contact yoursystem programmer to determine why the GCS generalIUCV exit is getting control.

GCT434S IUCVINI SET for GCS failed withreturn code nnn. Cannot continue IPL.

Explanation: A non-zero return code was receivedduring GCS IPL when trying to establish GCS as anIUCV user. The nnn is the return code that GCSreturns.

System action: The GCS IPL is terminated.

User response: Contact your system programmer todetermine why the IUCVINI SET failed.

GCT449E Error 22 running fn ft, line nn: Invalidcharacter string

Explanation: A character string scanned withOPTIONS ETMODE in effect contains one of thefollowing:

v Unmatched shift-out (SO) and shift-in (SI) controlcharacters.

v An odd number of bytes between the shift-out (SO)and shift-in (SI) characters.


User response: Correct the incorrect character string inthe EXEC file.

GCT450E Error 5 running fn ft, line nn: Machinestorage exhausted

Explanation: While attempting to process a program,the language processor was unable to get the spaceneeded for its work areas and variables. This may haveoccurred because a program that invoked the languageprocessor has already used up most of the availablestorage itself.


User response: Run the exec or macro on its own.More free storage may be obtained by releasing a disk(to recover the space used for the file directory).Alternatively, re-IPL GCS after defining a larger virtualstorage size for the virtual machine.


GCT451E Error 3 running fn ft, line nn: Program isunreadable

Explanation: The REXX program could not be readfrom the minidisk. This problem almost always occurswhen you are attempting to execute an exec orprogram from someone’s minidisk for which you haveread-only access, while someone with read-write accessto that minidisk has altered the program so that it nolonger exists in the same place on the minidisk.


User response: Reaccess the minidisk on which theprogram (such as, an exec) resides.

GCT452E Error 4 running fn ft, line nn: Programinterrupted

Explanation: The system interrupted execution of yourREXX program. Certain utility modules may force thisinterruption if they detect a disastrous error condition.


User response: Look for a problem with a utilitymodule called in your exec or macro.

GCT453E Error 6 running fn ft, line nn: Unmatched“/*” or quote

Explanation: The language processor reached the endof the file (or the end of data in an INTERPRETstatement) without finding the ending “*/” for acomment or quote for a literal string.


User response: Edit the exec and add the closing “*/”or quote. You can also insert a TRACE Scan statementat the top of your program and rerun it. The resultingoutput should show where the error exists.

GCT454E Error 7 running fn ft, line nn: WHEN orOTHERWISE expected

Explanation: The language processor expects a seriesof WHENs and an OTHERWISE within a SELECTstatement. This message is issued when any otherinstruction is found or if all WHEN expressions arefound to be false and an OTHERWISE is not present.The error is often caused by forgetting the DO andEND instructions around the list of instructionsfollowing a WHEN. For example:

WRONG RIGHT

Select SelectWhen a=b then When a=b then DOSay 'A equals B' Say 'A equals B'exit exitOtherwise nop endend Otherwise nop

end


User response: Make the necessary corrections.

GCT455E Error 8 running fn ft, line nn:Unexpected THEN or ELSE

Explanation: The language processor has found aTHEN or an ELSE that does not match a correspondingIF clause. This situation is often caused by using anincorrect DO-END in the THEN part of a complexIF-THEN-ELSE construction. For example:

WRONG RIGHT

If a=b then do; If a=b then do;Say EQUALS Say EQUALSexit exit

else endSay NOT EQUALS else

Say NOT EQUALS



GCT456E Error 9 running fn ft, line nn:Unexpected WHEN or OTHERWISE

Explanation: The language processor has found aWHEN or OTHERWISE instruction outside of aSELECT construction. You may have accidentallyenclosed the instruction in a DO END construction byleaving off an END instruction, or you may have triedto branch to it with a SIGNAL statement (which cannotwork because the SELECT is then terminated).



GCT457E Error 10 running fn ft, line nn:Unexpected or unmatched END

Explanation: The language processor has found moreENDs in your program than DOs or SELECTs, or theENDs were placed so they did not match the DOs orSELECTs.

This message can be caused if you try to signal into themiddle of a loop. In this case, the END will beunexpected because the previous DO will not havebeen executed. Remember, also, that SIGNALterminates any current loops, so it cannot be used totransfer control from one place inside a loop to another.

This message can also be caused if you place an ENDimmediately after a THEN or ELSE construction.


User response: Make the necessary corrections. Youcan use TRACE Scan to show the structure of theprogram, making it easier to find your error. Puttingthe name of the control variable on ENDs that closerepetitive loops can also help locate this kind of error.

GCT451E • GCT457E


GCT458E Error 11 running fn ft, line nn: Controlstack full

Explanation: This message is issued if you exceed thelimit of 250 levels of nesting of control structures(DO-END, IF-THEN-ELSE, and so on).

This message could be caused by a loopingINTERPRET instruction, such as:

line='INTERPRET line'INTERPRET line

These lines would loop until they exceeded the nestinglevel limit and this message would be issued. Similarly,a recursive subroutine that does not terminate correctlycould loop until it causes this message.



GCT459E Error 12 running fn ft, line nn: Clausetoo long

Explanation: You have exceeded the limit for thelength of the internal representation of a clause. Theactual limit is the amount of storage that can beobtained on a single request.

If the cause of this message is not obvious to you, itmay be due to a missing quote that has caused anumber of lines to be included in one long string. Inthis case, the error probably occurred at the start of thedata included in the clause traceback (flagged by +++on the console).

The internal representation of a clause does not includecomments or multiple blanks that are outside of strings.Note also that any symbol (name) or string gains twocharacters in length in the internal representation.



GCT460E Error 13 running fn ft, line nn: Invalidcharacter in program

Explanation: The language processor found an invalidcharacter outside of a literal (quoted) string. Validcharacters are:Alphanumeric

A-Z a-z 0-9Name Characters

@ # $ ¢ . ? ! _Special Characters

& * ( ) - + = \ ¬ ' " ; : < , > / |

If surrounded by X'0E' (shift-out) and X'0F' (shift-in),and if ETMODE is on, the following are also validcharacters:

X'41' - X'FE' (DBCS Characters)

Some causes of this error are:

1. Using accented and other language-specificcharacters in symbols.

2. Using DBCS characters without ETMODE in effect.



GCT461E Error 14 running fn ft, line nn:Incomplete DO/SELECT/IF

Explanation: The language processor has reached theend of the file (or end of data for an INTERPRETinstruction) and has found there is a DO or SELECTwithout a matching END, or an IF that is not followedby a THEN clause.


User response: Make the necessary corrections. Youcan use TRACE Scan to show the structure of theprogram, making it easier to find where the missingEND or THEN should be. Putting the name of thecontrol variable on ENDs that close repetitive loops canalso help locate this kind of error.

GCT462E Error 15 running fn ft, line nn: Invalidhexadecimal or binary string

Explanation: For the language processor, thehexadecimal or binary string cannot have leading ortrailing blanks and can have imbedded blanks at byteboundaries only. The following are all validhexadecimal strings:

'13'x'A3C2 1C34'x'1DE8'x

You may have mistyped one of the digits, for exampletyping a letter o instead of a 0. This message can alsobe caused if you follow a string by the 1-charactersymbol X (the name of the variable X), when the stringis not intended to be taken as a hexadecimal or binaryspecification. In this case, use the explicit concatenationoperator (||) to concatenate the string to the value ofthe symbol.



GCT463E Error 16 running fn ft, line nn: Label notfound

Explanation: The language processor could not findthe label specified by a SIGNAL instruction or a labelmatching an enabled condition when the corresponding(trapped) event occurred. You may have mistyped thelabel or forgotten to include it.

System action: Execution stops. The name of themissing label is included in the error traceback.

GCT458E • GCT463E



GCT464E Error 21 running fn ft, line nn: Invaliddata on end of clause

Explanation: You have followed a clause, such asSELECT or NOP, by some data other than a comment.



GCT465E Error 17 running fn ft, line nn:Unexpected PROCEDURE

Explanation: The language processor encountered aPROCEDURE instruction in an incorrect position. Thiscould occur because no internal routines are active,because a PROCEDURE instruction has already beenencountered in the internal routine, or because thePROCEDURE instruction was not the first instructionexecuted after the CALL or function invocation. Thiserror can be caused by “dropping through” to aninternal routine, rather than invoking it with a CALL ora function call.



GCT466E Error 26 running fn ft, line nn: Invalidwhole number

Explanation: The language processor found anexpression in the NUMERIC instruction, a parsingpositional pattern, or the right-hand term of theexponentiation (**) operator that did not evaluate to awhole number, or was greater than the limit, for theseuses, of 999999999.

This message can also be issued if the return codepassed back from an EXIT or RETURN instruction(when a REXX program is called as a command) is nota whole number or will not fit in a general register.This error may be due to mistyping the name of asymbol so that it is not the name of a variable in theexpression on any of these statements. This might betrue, for example, if you entered EXIT CR instead ofEXIT RC.



GCT467E Error 27 running fn ft, line nn: InvalidDO syntax

Explanation: The language processor found a syntaxerror in the DO instruction. You might have used BY,TO, FOR, WHILE, OR UNTIL twice, or used a WHILEand an UNTIL.



GCT468E Error 30 running fn ft, line nn: Name orString > 250 characters

Explanation: The language processor found a variableor a literal (quoted) string that is longer than the limit.

The limit for names is 250 characters, following anysubstitutions. A possible cause of this error is the use ofa period (.) in a name, causing an unexpectedsubstitution.

The limit for a literal string is 250 characters. This errorcan be caused by leaving off an ending quote (orputting a single quote in a string) because severalclauses can be included in the string. For example, thestring 'don't' should be written as 'don't' or “don't”.



GCT469E Error 31 running fn ft, line nn: Namestarts with number or “.”

Explanation: The language processor found a symbolwhose name begins with a number or a period (.). TheREXX language rules do not allow you to assign avalue to a symbol whose name begins with a numberor a period because you could then redefine numericconstants, and that would be catastrophic.


User response: Rename the variable correctly. It is bestto start a variable name with an alphabetic character,but some other characters are allowed.

GCT470E Error 34 running fn ft, line nn: Logicalvalue not 0 or 1

Explanation: The language processor found anexpression in an IF, WHEN, DO WHILE, or DO UNTILphrase that did not result in a 0 or 1. Any valueoperated on by a logical operator (¬, \, |, &, or &&)must result in a 0 or 1. For example, the phrase “Ifresult then exit rc” will fail if result has a value otherthan 0 or 1. Thus, the phrase would be better written asIf result¬=0 then exit rc.



GCT471E Error 35 running fn ft, line nn: Invalidexpression

Explanation: The language processor found agrammatical error in an expression. This could bebecause:

v You ended an expression with an operator.

v You specified, in an expression, two operators next toone another with nothing in between them.

v You did not specify an expression when one wasrequired.

GCT464E • GCT471E


v You did not specify a right parenthesis when onewas required.

v You used special characters (such as operators) in anintended character expression without enclosingthem in quotes.

An example of the last case is that LISTFILE * * *should be written as LISTFILE ’* * *’ (if LISTFILE isnot a variable) or even as ’LISTFILE * * *’.



GCT472E Error 36 running fn ft, line nn:Unmatched “(” in expression

Explanation: The language processor found anunmatched parenthesis within an expression. You willget this message if you include a single parenthesis in acommand without enclosing it in quotes. For example,COPY A B C A B D (REP should be written as COPY A BC A B D '('REP.



GCT473E Error 37 running fn ft, line nn:Unexpected “,” or “)”

Explanation: The language processor found a comma(,) outside a routine invocation or too many rightparentheses in an expression. You will get this messageif you include a comma in a character expressionwithout enclosing it in quotes. For example, theinstruction:

Say Enter A, B, or C

should be written as:Say 'Enter A, B, or C'



GCT474E Error 39 running fn ft, line nn:Evaluation stack overflow

Explanation: The language processor was not able toevaluate the expression because it is too complex(many nested parentheses, functions, and so on).


User response: Break up the expressions by assigningsubexpressions to temporary variables.

GCT475E Error 40 running fn ft, line nn: Incorrectcall to routine

Explanation: The language processor encountered anincorrectly used call to a routine. Some possible causesare:

v You passed incorrect data (arguments) to the built-inor external routine (this depends on the actualroutine). If a routine returns a nonzero return code,the language processor issues this message andpasses back its return code of 20040.

v You passed too many arguments to the built-in,external, or internal routine.

v The module invoked was not compatible with thelanguage processor.

If you were not trying to invoke a routine, you mayhave a symbol or a string adjacent to a “(” when youmeant it to be separated by a space or an operator. Thiscauses it to be seen as a function call. For example,TIME(4+5) should probably be written as TIME*(4+5).



GCT476E Error 41 running fn ft, line nn: Badarithmetic conversion

Explanation: The language processor found a term inan arithmetic expression that was not a valid numberor that had an exponent outside the allowed range of-999999999 to +999999999.

You may have mistyped a variable name, or includedan arithmetic operator in a character expressionwithout putting it in quotes. For example, thecommand MSG * Hi! should be written as 'MSG * Hi!',otherwise the language processor will try to multiply“MSG” by “Hi!”.



GCT477E Error 42 running fn ft, line nn:Arithmetic overflow/underflow

Explanation: The language processor encountered aresult of an arithmetic operation that required anexponent greater than the limit of 9 digits (more than999999999 or less than -999999999).

This error can occur during evaluation of an expression(often as a result of trying to divide a number by 0), orduring the stepping of a DO loop control variable.




GCT478E Error 43 running fn ft, line nn: Routinenot found

Explanation: The language processor was unable tofind a routine called in your program. You invoked afunction within an expression or in a subroutineinvoked by CALL, but the specified label is not in theprogram, or is not the name of a built-in function, andGCS is unable to locate it externally.

The simplest, and probably most common, cause of thiserror is mistyping the name. Another possibility maybe that one of the standard function packages is notavailable.

If you were not trying to invoke a routine, you mayhave put a symbol or string adjacent to a “(” when youmeant it to be separated by a space or operator. Thelanguage processor would see that as a functioninvocation. For example, the string 3(4+5) should bewritten as 3*(4+5).



GCT479E Error 44 running fn ft, line nn: Functiondid not return data

Explanation: The language processor invoked anexternal routine within an expression. The routineseemed to end without error, but it did not return datafor use in the expression.



GCT480E Error 45 running fn ft, line nn: No dataspecified on function RETURN

Explanation: A REXX program has been called as afunction, but an attempt is being made to return (by aRETURN; instruction) without passing back any data.Similarly, an internal routine, called as a function, mustend with a RETURN statement specifying anexpression.



GCT481E Error 49 running fn ft, line nn: Languageprocessor failure

Explanation: The language processor carries outnumerous internal self-consistency checks. It issues thismessage if it encounters a severe error.


User response: Report any occurrence of this messageto your IBM representative.

GCT482E Error 19 running fn ft, line nn: String orsymbol expected

Explanation: The language processor expected asymbol following the CALL or SIGNAL instructions,but none was found. You may have omitted the stringor symbol, or you may have inserted a special character(such as a parenthesis) in it.



GCT483E Error 20 running fn ft, line nn: Symbolexpected

Explanation: The language processor either expected asymbol following the CALL ON, CALL OFF, END,ITERATE, LEAVE, NUMERIC, PARSE, PROCEDURE,SIGNAL ON, or SIGNAL OFF keywords or expected alist of symbols following the DROP, UPPER, orPROCEDURE (with EXPOSE option) keywords. Eitherthere was no symbol when one was required or someother characters were found.



GCT484E Error 24 running fn ft, line nn: InvalidTRACE request

Explanation: The language processor issues thismessage when:

v The action specified on a TRACE instruction, or theargument to the built-in TRACE function, starts witha letter that does not match any valid alphabeticcharacter options. The valid options are A, C, E, F, I,L, N, O, R, or S.

v An attempt is made to request TRACE Scan wheninside any control construction or while in interactivedebug.

v In interactive trace, you enter a number that is not awhole number.



GCT485E Error 25 running fn ft, line nn: Invalidsub-keyword found

Explanation: The language processor expected aparticular sub-keyword at this position in aninstruction and something else was found. Forexample, the NUMERIC instruction must be followedby the sub-keyword DIGITS, FUZZ, or FORM. IfNUMERIC is followed by anything else, this message isissued.



GCT478E • GCT485E


GCT486E Error 28 running fn ft, line nn: InvalidLEAVE or ITERATE

Explanation: The language processor encountered anincorrect LEAVE or ITERATE instruction. Theinstruction was incorrect because of one of thefollowing:

v No loop is active.

v The name specified on the instruction does notmatch the control variable of any active loop.

Note that internal routine calls and the INTERPRETinstruction protect DO loops by making them inactive.Therefore, for example, a LEAVE instruction in asubroutine cannot affect a DO loop in the callingroutine.

You can cause this message to be issued if you use theSIGNAL instruction to transfer control within or into aloop. A SIGNAL instruction terminates all active loops,and any ITERATE or LEAVE instruction issued thenwould cause this message to be issued.



GCT487E Error 29 running fn ft, line nn:Environment name too long

Explanation: The language processor encountered anenvironment name specified on an ADDRESSinstruction that is longer than the limit of 8 characters.


User response: Specify the environment namecorrectly.

GCT488E Error 33 running fn ft, line nn: Invalidexpression result

Explanation: The language processor encountered anexpression result that is incorrect in its particularcontext. The result may be incorrect in one of thefollowing:

v ADDRESS VALUE expression

v NUMERIC DIGITS expression

v NUMERIC FORM VALUE expression

v NUMERIC FUZZ expression

v OPTIONS expression

v SIGNAL VALUE expression

v TRACE VALUE expression.

(FUZZ must be smaller than DIGITS.)



GCT489E Error 38 running fn ft, line nn: Invalidtemplate or pattern

Explanation: The language processor found anincorrect special character, for example %, within aparsing template, or the syntax of a variable triggerwas incorrect (no symbol was found after a leftparenthesis). This message is also issued if the WITHsub-keyword is omitted in a PARSE VALUE instruction.



GCT490E Error 48 running fn ft, line nn: Failure insystem service

Explanation: The language processor halts executionof the program because some system service, such asuser input or output or manipulation of the consolestack, has failed to work correctly.


User response: Ensure your input is correct and yourprogram is working correctly. If the problem persists,notify your system support personnel.

GCT491E Error 18 running fn ft, line nn: THENexpected

Explanation: All REXX IF and WHEN clauses must befollowed by a THEN clause. Another clause was foundbefore a THEN statement was found.


User response: Insert a THEN clause between the IFor WHEN clause and the following clause.

GCT492E Error 32 running fn ft, line nn: Invaliduse of stem

Explanation: The REXX program attempted to changethe value of a symbol that is a stem. (A stem is thatpart of a symbol up to the first period. You use a stemwhen you want to affect all variables beginning withthat stem.) This may be in the UPPER instructionwhere the action in this case is unknown, and thereforein error.


User response: Change the program so that it doesnot attempt to change the value of a stem.

GCT493E Error 1 running fn ft: No filenamespecified

Explanation: The EXEC command requires that youspecify the name of the EXEC that you wish to execute.


GCT486E • GCT493E


User response: Reissue the command and specify thefile name.

GCT494E Error 2 running fn ft: File not found

Explanation: The specified file was not found on theaccessed disks. This message can be issued when youtry to invoke an EXEC from within another EXEC.


User response: Access the disk where the file existsand reissue the command, or enter the correct name ofthe EXEC if you entered it incorrectly.

GCT495R Enter input for EXEC ‘execname’:

Explanation: ‘execname’ is the EXEC name. Thelanguage processor recognized a request for terminalinput. In most cases, this message will have beenpreceded by an informational message from the EXEC.

System action: The task executing the request issuspended until a REPLY command is issued.

User response: Use the REPLY command to supplythe required information.

GCT496R Enter DEBUG input for EXEC ‘execname’:

Explanation: ‘execname’ is the EXEC name. The EXECis being executed in DEBUG mode. The EXEC awaitsthe next user input.

System action: The task executing the request issuspended until a REPLY command is issued.

User response: Use the REPLY command to supplythe required information.

GCT497T Insufficient storage for EXEC interpreter

Explanation: There is insufficient storage for thelanguage processor to initialize itself.

System action: Execution is terminated at the point ofthe error.

User response: Redefine storage and reissue thecommand.

GCT500I Unable to locate ‘type’ extraction routine‘routine’

Explanation: The GCS extraction routine was unableto locate the ‘type’ extraction routine ‘routine’.

System action: Processing continues, and a problemreport will be created by the GCS extraction routine.

User response: Contact the system programmer todetermine why the routine could not be found.

GCT501I UNABLE TO LOCATE ‘type’DUMPSCAN ROUTINE ‘routine’

Explanation: The GCS DUMPSCAN routine wasunable to locate the ‘type’ DUMPSCAN routine ‘routine’

System action: Return to DUMPSCAN routine with areturn code of 8, which causes the message HCS270I tobe displayed.

User response: Contact the system programmer todetermine why the routine could not be found.

GCT502I TASKID nnnnn NOT FOUND

Explanation: One of the DUMPSCAN subcommands(TACTIVE, TLOADL, TSAB) has been issued with ataskid that was not in the task’s active program list ortaskid table.

System action: Return to DUMPSCAN routine with areturn code of 0, which causes the ready message to bedisplayed.

User response: Reissue the command with the correcttask ID.

GCT503I NO IUCV PATH TABLE

Explanation: The IUCV DUMPSCAN subcommandwas entered and the number of entries in the IUCVpath table was zero.



GCT504I PAGE vstor NOT FOUND IN DUMP

Explanation: The virtual address identified in themessage was not found in the dump. This means it wasnot dumped at the time the dump was taken.



GCT505I TASKID nnnnn INVALID

Explanation: One of the DUMPSCAN subcommands(TACTIVE, TLOADL, TSAB) has been issued with ataskid that is invalid. (Taskid must be from 0 tox‘FFFF’)


User response: Reissue the command with a validtaskid.


GCT506I UNABLE TO READ DUMPINFORMATION RECORD

Explanation: The GCS EXTRACTION routine wasunable to read the dump information record.

System action: DVF will prompt the user to enter allinformation for the problem report.

User response: Supply information in answer to theprompts that appear on the screen.

GCT507E Trace formatting routine ‘routine’ notfound

Explanation: Trace formatting could not locate thenamed routine.

System action: The record is displayed or printed inhexadecimal notation with no formatting done.

User response: Install the required TEXT file on anaccessed CMS disk and then re-execute the program.

GCT508I The following record was partially lost:

Explanation: TRSOURCE lost the last part of thisrecord.

System action: The first portion of the record isdisplayed in hexadecimal notation (unformatted).


GCT509I ETRACE set ON for event-type(s)

Explanation: This is the normal reply when externaltracing for the specified event has been enabled for thevirtual machine.



GCT510I ETRACE set ON for event-type(s) forGROUP

Explanation: This is the normal reply from anETRACE command that was issued to set externaltracing on for an event-type for the whole group.

System action: Exits are scheduled on all virtualmachines in the group to set ETRACE on for theevent-type named in the message.


GCT511I ETRACE set OFF for event-type(s)

Explanation: This is the normal reply when externaltracing for the specified event has been disabled for thevirtual machine.



GCT512I ETRACE set OFF for event-type(s) forGROUP

Explanation: This is the normal reply from anETRACE command that was issued to set externaltracing off for an event-type for the whole group.

System action: Exits are scheduled on all virtualmachines in the group to set ETRACE off for theevent-type named in the message.


GCT513E ETRACE GROUP option is in effect forevent-type(s)

Explanation: An attempt was made by anunauthorized user to disable external tracing while theGROUP option was in effect. The GROUP optionoverrides the command.

System action: Command terminates with no actiontaken.

User response: Use the QUERY ETRACE command tofind the event types which are in effect for the group.Then reissue the command without the event typeswhich were in effect for the group.

GCT514I All external trace events are disabled

Explanation: No external tracing is being done in thisvirtual machine.



GCT515I External trace is enabled for event-type(s)

Explanation: External tracing for the specified eventtype has been enabled for this virtual machine.



GCT516I External trace is enabled for event-type(s)for GROUP

Explanation: External tracing for the specified eventtype was enabled for this virtual machine by theGROUP operand of ETRACE.



GCT517I ITRACE set ON for event-types(s)

Explanation: This is the normal reply when theITRACE command is issued to enable ITRACE.

System action: ITRACE is enabled for the issuingvirtual machine.

GCT506I • GCT517I



GCT518I ITRACE set ON for event-type(s) forGROUP

Explanation: This is the normal reply when anauthorized user issues the ITRACE GROUP command.

System action: Exits are scheduled on all virtualmachines in the group to enable ITRACE.


GCT519I ITRACE set OFF for event-type(s)

Explanation: This is the normal reply when theITRACE has been disabled for the issuing virtualmachine.

System action: ITRACE is disabled for the issuingvirtual machine.


GCT520I ITRACE set OFF for event-type(s) forGROUP

Explanation: This is the normal reply when anauthorized user has issued the ITRACE END GROUPcommand, turning off ITRACE in all virtual machinesin the group.

System action: ITRACE is disabled for all virtualmachines in the group.


GCT521E ITRACE GROUP option is in effect forevent-type(s)

Explanation: An unauthorized user attempted todisable ITRACE while the ITRACE GROUP option wasin effect. The GROUP option overrides the command.

System action: Command terminates with no actiontaken. ITRACE remains in effect for the group.

User response: Use the QUERY ITRACE command tofind the event types which are in effect for the group.Then reissue the command without the event typeswhich were in effect for the group.

GCT522I Internal trace is enabled for event-type(s)

Explanation: ITRACE is enabled for this virtualmachine.



GCT523I Internal trace is enabled for event-type(s)for GROUP

Explanation: ITRACE is enabled for this virtualmachine by the GROUP operand.



GCT524I All internal trace events are disabled

Explanation: ITRACE is disabled for this virtualmachine.



GCT525E Userid is missing or invalid

Explanation: The TO operand was specified, but theuser ID was either left out or is invalid. The user IDcannot be longer than eight characters.

System action: Command terminates with no dumptaken.

User response: Reissue the command specifying avalid user ID.

GCT526E Userid ‘userid’ is not in CP directory

Explanation: The dump request was passed to CP, butthe receiving user ID, whether specified or defaulted,was not found in the CP directory.


User response: Reissue the command specifying avalid user ID.

GCT527E Invalid range

Explanation: One of the following conditions wasencountered:

1. Hexloc1 greater than hexloc2.

2. Invalid modifier - only ‘-’, ‘.’, and ‘:’ are valid.

3. Invalid bytecount.

4. Address specified which is out of the range of thevirtual machine‘s storage.

5. Range specified is not a valid hexadecimal number.

6. The dump request involved only areas whichrequire authorization to dump, but the receiver wasnot on the list of authorized users specified at GCSbuild time. Or the dump request involved onlyareas which require authorization to dump andDSS‘s but the receiver was not authorized and noDSS‘s exist.


GCT518I • GCT527E


User response: Reissue the command specifying avalid range.

GCT528I Dump complete

Explanation: A dump was taken. If the receiver is anauthorized user, the dump contains the whole virtualmachine and any discontiguous shared segments.Otherwise the dump contains all key 14 storage(storage belonging to non-privileged applications) andany other storage that is not fetch-protected.

System action: In the case of machine termination, thetermination continues. In the case of SYSTEMRESTART, control returns to the virtual machine at thepoint where it was interrupted to issue the CP SYSTEMRESTART command.


GCT529E Partial dump taken

Explanation: The dump was only partially completedfor one of the following reasons:

1. CP experienced an I/O error when attempting tobring a page to be dumped.

2. DSS specified, but no DSSs found.

3. The dump request involved some protected storage,but the receiver was not on the list of authorizedusers specified at GCS build time.

System action: Command terminates with a partialdump taken.

User response:

1. If the dump failed because of a CP I/O error,reissue the command. If the problem persists,contact the system programmer.

2. If the dump failed because no DSS was found, nouser action is required.

3. If the dump failed because the receiving user IDwas unauthorized, reissue the command specifyingan authorized receiver.

GCT530E Dump failed

Explanation: An error occurred while attempting todump the virtual machine.

System action: In the case of machine termination, thetermination continues with no dump taken. In the caseof SYSTEM RESTART, control returns to the virtualmachine at the point it was interrupted to enter thecommand, and no dump is taken.

User response:

1. Find out from the installation system programmer ifthe system is currently experiencing any spoolproblems. If it is, try the dump again after theproblem is fixed.

2. Also find out from the installation systemprogrammer if the user ID designated at GCS buildtime as the dump receiver is in the CP directory. Ifit is not, you cannot dump via SYSTEM RESTARTuntil this is corrected.

GCT531E Dump failed: Spooling error

Explanation: CP ran out of spool space.


User response: Reissue the command when spoolspace is available.

GCT532E Dump failed: I/O error

Explanation: CP encountered an I/O error whileattempting to bring in the parameter list or the dumpaddress list passed by the GCS supervisor.

System action: The command terminates with nodump taken.

User response: Reissue the command. If the failurepersists, contact the system programmer.

GCT533I VIRTUAL MACHINE LOAD LIST ISEMPTY

Explanation: The GCS DUMPSCAN subcommandVMLOADL was entered and the pointer to NUCCBLKSis zero.

System action: Return to the DUMPSCAN routinewith return code zero, which causes a ready message tobe displayed.


GCT534I TASK STORAGE ANCHOR BLOCKPTR IS ZERO

Explanation: The GCS DUMPSCAN subcommandTSAB was entered and the pointer to the task storageanchor block is zero.



GCT535I NUCON EXTENSION PTR IS ZERO.CAN'T FIND TASK LOAD LIST

Explanation: The GCS DUMPSCAN subcommandTLOADL was entered and the pointer to NUCONEXTENSION is zero.


GCT528I • GCT535I



GCT536I TASKID TABLE PTR IS ZERO. CAN'TFIND TASK LOAD LIST

Explanation: The GCS DUMPSCAN subcommandTLOADL was entered and the pointer to TASKIDTABLE is zero.



GCT537I TASK BLOCK PTR IS ZERO. CAN'TFIND TASK LOAD LIST

Explanation: The GCS DUMPSCAN subcommandTLOADL was entered and the pointer to TASK BLOCKis zero.



GCT538I TASK LOAD LIST PTR IS ZERO

Explanation: The GCS DUMPSCAN subcommandTLOADL was entered and the pointer to the TASK loadlist is zero.



GCT539I NUCON EXTENSION PTR IS ZERO.CAN'T FIND TASK STORAGEANCHOR BLOCK

Explanation: The GCS DUMPSCAN subcommandTSAB was entered and the pointer to NUCONEXTENSION is zero.



GCT540I TASKID TABLE PTR IS ZERO. CAN'TFIND TASK STORAGE ANCHORBLOCK

Explanation: The GCS DUMPSCAN subcommandTSAB was entered and the pointer to TASKID TABLE iszero.



GCT541I TASK BLOCK PTR IS ZERO. CAN'TFIND TASK STORAGE ANCHORBLOCK

Explanation: The GCS DUMPSCAN subcommandTSAB was entered and the pointer to TASK BLOCK iszero.



GCT542I NUCON EXTENSION PTR IS ZERO.CAN'T FIND IUCV PATH TABLE

Explanation: The GCS DUMPSCAN subcommandIUCV was entered and the pointer to NUCONEXTENSION is zero.



GCT543I IUCV ANCHOR BLOCK PTR IS ZERO.CAN'T FIND IUCV PATH TABLE

Explanation: The GCS DUMPSCAN subcommandIUCV was entered and the pointer to IUCV STORAGEANCHOR BLOCK is zero.



GCT544I IUCV PATH TABLE PTR IS ZERO

Explanation: The GCS DUMPSCAN subcommandIUCV was entered and the pointer to PATH TABLE iszero.



GCT545I NUCON EXTENSION PTR IS ZERO.CAN'T FIND STATE BLOCK

Explanation: The GCS DUMPSCAN subcommandTACTIVE was entered and the pointer to NUCONEXTENSION is zero.


GCT536I • GCT545I



GCT546I TASK BLOCK PTR IS ZERO. CAN'TFIND STATE BLOCK

Explanation: The GCS DUMPSCAN subcommandTACTIVE was entered and the pointer to TASK BLOCKis zero.



GCT547I STATE BLOCK PTR IS ZERO

Explanation: The GCS DUMPSCAN subcommandTACTIVE was entered and the pointer to STATEBLOCK is zero.



GCT548I TASKID TABLE PTR IS ZERO. CAN'TFIND STATE BLOCK

Explanation: The GCS DUMPSCAN subcommandTACTIVE was entered and the pointer to TASKIDTABLE is zero.



GCT549E productname control block formattingroutine routine not found

Explanation: The control block formatting routine forthe indicated product name is not on the user‘saccessed disk.

System action: Processing is terminated.

User response: Get the indicated routine‘s text deckon an accessed disk and reissue the DUMPPRTcommand.

GCT550R Do you wish to format productnamecontrol blocks? Reply YES or NO.

Explanation: Enter YES if you want to format controlblocks for the indicated product name; enter NO if youwant an unformatted dump only.

System action: Control will be passed to theappropriate formatting routine.

User response: Enter YES or NO at your terminal.

GCT551I External trace buffering has beeninitialized.

Explanation: ETRACE has been enabled whileTRSOURCE is in BLOCK mode. External trace pointsare collected in a GCS buffer in private storage beforebeing sent to CP. ETRACE may have been issued fromyour virtual machine or from another virtual machinein the GCS group with the GROUP option specified.

System action: Processing continues

User response: None

GCT552I All ETRACE support has been disabledand the buffer has been flushed.

Explanation: An ETRACE END has been issued or allexternal trace points have been turned off for thisvirtual machine while tracing was being done inBLOCK mode. All trace points have been sent to CP forprocessing. ETRACE END may have been issued fromyou virtual machine or from another virtual machine inthe GCS group with the GROUP option specified.


User response: None

GCT553I TRSOURCE has been changed toEVENT mode and external trace recordsmay have been lost.

Explanation: TRSOURCE was changed from BLOCKmode to EVENT mode without first disabling ETRACE.Any external trace points collected in the trace bufferare lost.

System action: All external tracing has been disabled.

User response: ETRACE must be reissued by thisvirtual machine or an authorized machine in the groupwith the GROUP option specified to reactivate externaltracing. Ensure that the TRSOURCE is enabled in thecorrect mode first.

GCT554I TRSOURCE has been disabled andexternal trace records may have beenlost.

Explanation: TRSOURCE was disabled without firstissuing an ETRACE END. Any external trace pointscollected in the trace buffer are lost.




GCT555I External tracing has been initialized inEVENT mode.

Explanation: ETRACE has been enabled whileTRSOURCE is in EVENT mode. External trace pointswill be sent directly to CP as they are generated inGCS.


User response: None

GCT556E TRSOURCE must be enabled beforeusing ETRACE.

Explanation: The GCS command ETRACE has beenissued before the CP TRSOURCE command was issued.

System action: All external tracing is left disabled.


GCT557E Trace buffer not processed. RC = 16from TRSOURCE. Records may havebeen lost.

Explanation: GCS tried to flush the trace buffer andCP was unable to handle it.


User response: Check the CP references onTRSOURCE before trying to reinitialize external tracing.

GCT558I TRSOURCE has been disabled. It mustbe enabled before external tracing canbe enabled.

Explanation: An ETRACE command was issued fromanother virtual machine for the entire group and thismachine tried to initialize external tracing and foundthat TRSOURCE was disabled.



GCT559E Insufficient storage in your virtualmachine to set up group trace buffering.

Explanation: An ETRACE command was issued fromthis machine or from an authorized machine with thegroup option specified and TRSOURCE was enabled inBLOCK mode. In the process of initializing for tracebuffer, insufficient storage was available.


System may terminate at any time due to insufficientstorage.

User response: Re-IPL after first setting your virtualmachine size larger to allow for an increase in privatestorage which will enable your trace buffering to beinitialized.

GCT560I Re-issue ETRACE to activate externaltracing. The TRSOURCE mode has beenchanged.

Explanation: The system detected that the TRSOURCEmode has been changed.



GCT561I GTRACE records greater than 256 bytesmust be processed by TRSOURCE inblock mode and GCS tracing set toETRACE GTRACE.

Explanation: This message is issued as a warning. Itwill be issued again when a GTRACE record greaterthan 256 bytes is generated without using block mode.


User response: Issue the appropriate TRSOURCEcommand to handle GTRACE records greater than 256bytes.

GCT621E The variations of this message areexplained below.

— Bad Plist: Device and lines argumentsare required

Explanation: The first two EXECIO command lineoperands are always required.

System action: RC=24. Execution is stops.

User response: Check the command syntax.

— Bad Plist: Disk argument argument ismissing

Explanation: The missing argument is FILENAME orFILETYPE. These are required arguments when DISKRor DISKW operations are specified.


User response: Issue the command again with themissing disk argument.

GCT555I • —


— Bad Plist: Disk filemode required forDISKW

Explanation: The file mode operand is required for aDISKW operation. The DISKW operation might causewriting to a disk that the user has write access to.


User response: Check the command syntax

— Bad Plist: File format specified (recfm)does not agree with existing file format(recfm)

Explanation: The record format of a record to bewritten into an existing file is inconsistent with that file.


User response: Check the record format specifiedagainst that of the file.

— Bad Plist: File lrecl specified (lrecl) doesnot agree with existing file lrecl (lrecl)

Explanation: The logical record length of a record tobe written into an existing file is inconsistent with thatfile.


User response: Check the logical record length againstthat of the file.

— Bad Plist: Input file fileid does not exist

Explanation: The indicated file cannot be found.


User response: Check to make sure that the file ID hasbeen entered correctly.

— Bad Plist: Invalid character in fileidentifier

Explanation: The specified file ID contains a characterthat is not valid for the GCS file system.


User response: Check the description of the commandformat and issue the command again using validcharacters.

— Bad Plist: Invalid DEVICE argument(argument)

Explanation: The valid values for the DEVICEargument are: CP, CARD, DISKR, DISKW, PUNCH,PRINT, and EMSG.



— Bad Plist: Invalid EXEC variable name

Explanation: Using the EXECIO command, themaximum length of a variable name for the VAR orSTEM option was exceeded. The maximum for the VARoption is 250 characters. The maximum for the STEMoption is 240 bytes.


User response: Use a shorter length variable name.

— Bad Plist: Invalid mode mode

Explanation: More than two characters were specifiedfor the file mode.



— Bad Plist: Invalid positional argument(argument)

Explanation: More than the maximum number ofpositional arguments (that is, arguments before the leftparenthesis marking the start of the options) werespecified. The number of positional arguments alloweddepends on the second operand (DISKR, and so on) onthe command line.

This message is likely the result of the left parenthesisoption delimiter missing from the command statement.


User response: Check to make sure that you havespecified the correct positional arguments and that youhave not omitted the parenthesis.

— Bad Plist: Invalid record format (recfm) --Must be either F or V

Explanation: For a DISKW operation, if the recordformat (recfm) is specified, it must be either fixed (F) orvariable (V). Variable is the default value.



— Bad Plist: Invalid record lengthargument (lrecl)

Explanation: For a DISKW operation, if the logicalrecord length (lrecl) is specified, the value must begreater than zero.



—


— Bad Plist: Invalid value (value) fornumber of lines

Explanation: The number of lines specified to beprocessed must be either a non-negative integer or anasterisk (*).


User response: Check the value specified for thenumber of lines to be processed.

— Bad Plist: Invalid value (value) for diskfile line number

Explanation: The line number specified is negative ora non-numeric value.



— Bad Plist: Missing DEVICE argument

Explanation: The EXECIO command requires aDEVICE argument.



— Bad Plist: Option option can only beexecuted from a REXX EXEC

Explanation: The VAR or STEM option was used, butthe EXECIO command was not invoked from within aREXX exec. The VAR and STEM options require the useof EXECCOMM which requires that a REXX exec beactive in the same task that issued the EXECIOcommand.


User response: Invoke the command again from aREXX exec.

— Bad Plist: option option is not valid withoption option

Explanation: Two mutually exclusive options werespecified. For example, only one input selection optionis allowed; therefore, if both a LOCATE and a FINDoption are specified, this message will be issued.


User response: Check the syntax of the command.

— Bad Plist: option option not valid withoperation operation

Explanation: The indicated option cannot be specifiedwith the indicated operation. For example, the FINISoption is not valid if PRINT is specified as the secondoperand in the command statement.



— Bad Plist: STRING option withLINES=* is valid only for CP operation

Explanation: The string option with lines=* is validonly for a CP operation.



— Bad Plist: Unknown option name (name)

Explanation: The indicated option name is notrecognized by EXECIO.


User response: Check to make sure that you have notmisspelled an option name.

— Bad Plist: Value (value) not valid foroption option

Explanation: A not valid value was specified for theindicated option. For example, if “Case 3” is used in acall to EXECIO, the message will read “... Value (3) notvalid for CASE option.”



— Bad Plist: Value missing after optionoption

Explanation: A value was not specified after theindicated option, yet one is required. For example, theMARGINS option requires that two values follow it. Ifone or both of these is missing, the message is issued.



— Bad Plist: VAR option with LINES > 1 isinvalid

Explanation: The EXECIO command was issued withthe VAR option and the number of lines specified wasgreater than one.


User response: Either change the lines operand to 1 oruse the STEM option.

GCT622E Insufficient free storage for EXECIO

Explanation: Insufficient storage was available forEXECIO to execute the requested function. The requestfunction is not performed.

— • GCT622E


System action: RC=41. Execution halts.

User response: More free storage may be obtained byreleasing a disk (to recover the space used for the filedirectory). Alternatively, re-ipl GCS after defining alarger virtual storage size for the virtual machine.

GCT632E I/O error in EXECIO; rc=‘nnnn’ from‘operation’ operation

Explanation: The specified error return code wasobtained by EXECIO when the indicated operation wasinvoked. EXECIO will not continue, but returns theerror return code to its caller. The EXECIO operationmay have partially completed before the error occurred.

System action: RC=‘nnnn’, where nnnn is the returncode from the command specified in the message text.

For example EXECIO return code 2008, signifies aninvalid variable name from the EXECCOMM operation.

User response: For more information on the returncodes, refer to the EXECIO command in z/VM: GroupControl System.

GCT900I z/VM Version n Release n, Service leveln

Explanation: This is an informational message. Therelease indicates the release level currently applied toyour z/VM system. The Service Level n indicates theservice level currently applied to your z/VM system.



GCT901E Error 46 running fn ft, line nn: Invalidvariable reference

Explanation: Within an ARG, DROP, PARSE, PULL, orPROCEDURE instruction, the syntax of a variablereference (a variable whose value is to be used,indicated by its name being enclosed in parentheses) isincorrect. The right parenthesis that shouldimmediately follow the variable name may be missing.



GCT902E Error 47 running fn ft, line nn:Unexpected label

Explanation: A label, being used incorrectly, wasencountered in the expression being evaluated for anINTERPRET instruction or in an expression enteredduring interactive debug.


User response: Do not use a label in theseexpressions.

GCT903E Error 23 running fn ft, line nn: InvalidSBCS/DBCS mixed string.

Explanation: A character string that has unmatchedSO-SI (Shift-Out - Shift-In) pairs (such as an SO withoutan SI), or an odd number of bytes between the SO-SIcharacters was processed with OPTIONS EXMODE ineffect.


User response: Correct the incorrect character string.

GCT920E GCSTOKEN parameter list (plist) doesnot start with 'GCSTOKEN'

Explanation: The GCSTOKEN plist does not start withGCSTOKEN. The address of the plist points to astorage location that does not contain the string'GCSTOKEN' in the first eight bytes. The GCSTOKENfunction requested was not performed.

System action: RC=38. GCS processing continuesnormally.

User response: Ensure the program using theGCSTOKEN macro has not overlaid any part of theparameter list before invoking the GCSTOKENfunction. When using the execute format of theGCSTOKEN macro, be sure the address of theparameter list is correctly loaded into the registerspecified that contains the address of the plist.

GCT921E GCSTOKEN function requested was notCREATE, RETRIEVE, or DELETE

Explanation: The GCSTOKEN parameter list does notcontain a valid function indicator. The GCSTOKENfunction requested was not performed.


User response: Ensure the program using theGCSTOKEN macro has not overlaid any part of theparameter list before invoking the GCSTOKENfunction. When using the execute format of theGCSTOKEN macro, be sure the function is specified oneither the EXECUTE, LIST, or LIST ADDRESS form ofthe macro.

GCT922E GCSTOKEN LEVEL specified was notCOMMON, PRIVATE, or TASK

Explanation: The GCSTOKEN parameter list does notcontain a valid LEVEL. The GCSTOKEN functionrequested was not performed.


User response: Ensure the program using theGCSTOKEN macro has not overlaid any part of the

GCT632E • GCT922E


parameter list before invoking the GCSTOKENfunction.

GCT923E Problem state programs can only issue{CREATE|DELETE} with LEVEL=TASK

Explanation: An unauthorized program attempted toissue GCSTOKEN CREATE or DELETE specifying aLEVEL other than TASK. The GCSTOKEN functionrequested was not performed.


User response: Ensure the program using theGCSTOKEN macro is in the proper state to issue theCREATE or DELETE at the LEVEL specified.

GCT925E Names cannot begin with {'GCT'|X'00'};{CREATE|DELETE} failed

Explanation: The GCSTOKEN CREATE or DELETEfunction was invoked with a NAME that begins withthe characters indicated. The GCSTOKEN functionrequested was not performed.


User response: Alter the NAME of the Name/Tokenpair so it does not start with the reserved charactersGCT or X'00'. Try the CREATE again.

GCT926S Insufficient free storage available forGCSTOKEN CREATE function withLEVEL={COMMON|PRIVATE|TASK}

Explanation: The GCSTOKEN CREATE function wasinvoked, but the system does does not have enoughavailable free storage to satisfy the request. TheGCSTOKEN function requested was not performed.


System programmer response: If the LEVEL indicatedin the message is COMMON and you have highcommon storage capabilities, define a larger commonstorage area using the GROUP EXEC, rebuild GCS, andre-IPL.

User response: If the LEVEL indicated in the messageis PRIVATE or TASK, define a larger virtual storagesize for the virtual machine and re-IPL GCS. If theLEVEL indicated in the message is COMMON, see thesystem programmer response.

GCT928E Only the virtual machine that created aName/Token pair can DELETE it withLEVEL=COMMON

Explanation: The GCSTOKEN DELETE function wasinvoked with LEVEL = COMMON, but the VM user IDof the creator of the pair does not match the VM user

ID of the user attempting to DELETE the pair. Forcommon level Name/Token pairs, only the virtualmachine that created the pair can delete it. TheGCSTOKEN function requested was not performed.


User response: None. You may want to verify theNAME specified is correct.


TSAF Messages

ATS001I Initialization is complete. The servicelevel is ssss

Explanation: This message is issued when allpermanent TSAF tasks have been started and TSAF isready for normal operation. The service level of thecode running is ssss.

System action: TSAF is running normally. It willperform its communications functions, as well asdynamic link and collection monitoring. You can entercommands.

Operator response: You can now enter TSAFcommands.

ATS002T Parameter parameter is a duplicate or isnot valid

Explanation: The argument, parameter, was passed as aparameter on invocation of RUNTSAF. The argument iseither invalid or it duplicates a previous argument.TSAF takes any numeric value to be the number of 1Kinternal trace blocks. If you provide two numericvalues, TSAF considers the second a duplicate, even ifits value is not the same as the first.

System action: TSAF will terminate with return code12.

Operator response: Check the TSAF invocation, andrestart TSAF with valid parameters.

ATS003I Termination is in progress

Explanation: TSAF has accepted a STOP command.

System action: TSAF will terminate with return code0.


ATS004E Parameter parameter is not valid

Explanation: You entered a parameter on a TSAFcommand that TSAF does not recognize.

System action: TSAF ignores the command and isready for another.


ATS005E A required parameter is missing

Explanation: A required parameter is missing from theinput command.

System action: TSAF ignores the command and isready for another command.

Operator response: Enter the correct command.

ATS006I TSAF link statistics and sessionaccounting records will be generated

Explanation: The TSAF virtual machine directorycontains the account option.

System action: TSAF will pass accounting records toCP.

Operator response: No action is required. However, ifyou do not want TSAF accounting records, notify thesystem administrator so they can delete the accountoption from the TSAF directory entry.

ATS007I No TSAF link statistics or sessionaccounting records will be generated

Explanation: The TSAF virtual machine directory doesnot contain the account option.


Operator response: No action is required. If, however,you want accounting records, notify the systemadministrator to add the account option to the TSAFdirectory entry.

ATS009E cmd is not a valid TSAF command

Explanation: You entered a command at the TSAFvirtual console that TSAF does not recognize.

System action: TSAF ignores the command and isready for another.


ATS010I External trace started

Explanation: TSAF processed a SET ETRACE ONcommand.

System action: CMS will write external trace recordsuntil it receives a SET ETRACE OFF command.


ATS011I External trace ended

Explanation: TSAF processed a SET ETRACE OFFcommand.

System action: External trace records will not bewritten until a SET ETRACE ON is issued.


ATS013I Trace area size is nnnK

Explanation: TSAF has obtained an internal traceblock of the size specified by nnn. This size may beeither:

ATS001I • ATS013I


v The default value (40K)

v The value specified as an input argument to TSAF,rounded up to a 4K multiple, if necessary.



ATS017I Abend code ccc at aaaaaa

Explanation: TSAF terminated abnormally, and CMSgave control to the TSAF abend exit routine. TSAF getsthe abend code, ccc, and the failure address, aaaaaa,from the PSW at the time the abend in the abend workarea (DMSABW) occurred.

System action: ATSCAB will display this and otherproblem determination messages at the terminal. ThenATSCAB will take a VMDUMP of the entire TSAFvirtual machine, and issue a Load Program Status Word(LPSW) instruction (assuming that CONCEAL is ON)to cause CP to re-IPL the CMS system that the virtualmachine is using.

Operator response: Save this information and contactyour service representative.

ATS018I Program old PSW is psw

Explanation: TSAF terminated abnormally, and CMSgave control to the TSAF abend exit routine. The psw isthe PSW at the time the abend in the abend work area(DMSABW) occurred. This message usually followsmessage ATS017I.

System action: See message ATS017I.


ATS019I Abend modifier is aaaaaaaaaa

Explanation: TSAF terminated abnormally, and CMSgave control to the TSAF abend exit routine. Themodule that invoked the abend set the abend modifierfield (CGM_REPORT) to aaaaaaaaaa. This isalphanumeric information. The abend code and theabend modifier, together, identify the failure point. Thismessage normally follows message ATS018I.



ATS021I Failure at offset nnnn in modulemmmmmm dated yy.ddd

Explanation: TSAF did a program check or issued anabend nnnn bytes into module mmmmmm. The yy.ddd isthe year and day the module was compiled. ATSCABdetermines the module name and compilation datefrom the eye-catcher by assuming register 11 or 12 isthe base register.


Operator response: Keep problem information andcontact your service representative.

ATS022I Called from offset nnnn in modulemmmmmm dated yy.ddd

Explanation: An instruction nnnn bytes into modulemmmmmm called the module in which the abendoccurred. The yy.ddd is the year and day mmmmmmwas compiled.

If the save area contains a non-zero backward pointer,TSAF issues this message after message 021I. TSAFextracts the name and compilation date of the callingmodule from the eye-catcher.



ATS023I VMDUMP ATSCABn mm/dd/yy hh:mm:sstaken

Explanation: A VMDUMP of the entire TSAF virtualmachine has been taken. TSAF specified “ATSCABmm/dd/yy hh:mm:ss” as the *dumpid operand on theVMDUMP command. On the message identifier:

n = 1 if the dump was invoked during the first entryto the abend exit

n = 2 if the dump was invoked after ATSCAB2 wasentered

mm/dd/yyis the current date

hh:mm:ssis the current time.



ATS024W Link linkunit has not been added

Explanation: The link specified on either the SETETRACE LINK command or the ETRACE LINKoperand of the RUNTSAF command, has not beenadded to the TSAF virtual machine.

System action: The command and link informationare accepted and stored. When the link is added to theTSAF virtual machine and the TSAF Link Definitiontable is built, external data tracing will occur for thespecified link.

Operator response: Determine whether the link unitwas entered correctly on the SET ETRACE LINKcommand. If not, reissue the command with the correctlink unit.


ATS025W User userid has no APPC/VM connectionto TSAF

Explanation: The virtual machine with the user IDspecified on either the SET ETRACE USERID commandor the ETRACE USERID operand of the RUNTSAFcommand, has not established an APPC/VM paththrough the TSAF virtual machine.

System action: The command and user ID informationare accepted and stored. When some APPC/VM pathactivity occurs for the user ID, external tracing willoccur for that user ID.

Operator response: Determine whether the user idwas entered correctly on the SET ETRACE USERIDcommand. If not, reissue the command with the correctuser ID.

ATS075E NON-NUMERIC COUNT CHARACTER- RETRY

Explanation: The count field has non-numericcharacters.



ATS076E FORMATTED DATA ENTRY EXCEEDSMAXIMUM SIZE

Explanation: You used either a SCROLL or TRACEsubcommand with the FORMAT option, but withoutthe FOR count option, to display a trace entry that istoo big to fit on the screen.

System action: CP truncates the displayed entry andterminates the subcommand.

User response: View the entry, by doing the following:

1. Note the address of the entry.

2. Issue a TRACE subcommand with the FROM andFOR count options.

ATS077E CONFLICTING OPERAND - operand

Explanation: This message occurs when:

v The same option is specified twice in the samecommand, or

v The function required by the given option isincompatible with a previously specified operand.


User response: Reissue the command with theoperands correctly specified.

ATS078E OPERAND MISSING OR INVALID

Explanation: One of the following commands causedan error:

v TRACE subcommand (from module ATSZTR)

– You specified the SCROLL operand before aTRACE subcommand established a previouslocation.

– You specified the FOR operand with no countvalue or an invalid value.

– You specified the FROM operand with no fromlocvalue or an invalid value.

– You used an unknown operand or invalidabbreviation.

v FDISPLAY subcommand (from module ATSZTD)

– You did not specify parameters on thesubcommand.

– The LINKCTL operand has no parameters.

– You specified an unknown operand or invalidabbreviation.


User response: Reissue the command with a validoperand.

ATS079I TRACE TABLE POINTERS INVALID:START = start END = endCURRENT = current

Explanation: While trying to display TSAF trace tableentries, it was found that the TSAF trace table pointersin the dump are invalid. Possible causes of the errorare:

v The trace table start address is greater than the tracetable end address.

v The current trace table address is outside of the tracetable.

v The trace table is not an integer number of pages.

v A “FROM” location was not specified and the tracetable pointers are invalid.

v A page needed for trace table wrapping is missingfrom the dump.

v The data at the end of the table is not a valid traceentry.

System action: If you specified a “FROM” location,then the processing of the subcommand will continueat the “FROM” location. The display will not wrap atthe trace table start position, and will stop when one ofthe following occurs:

v The specified count (or default count, if count wasnot specified) has been reached.

v The address of the next trace entry to display is lessthan or equal to zero.

v The address of the next trace entry to display isbeyond the end of the dump.

ATS025W • ATS079I


If you did not specify a “FROM” location then thesubcommand terminates.

User response: If you did not specify a “FROM”location, determine the location of the trace table, andreissue the TRACE command with a “FROM” locationspecified. If you did specify a “FROM” location, ignorethe message.

ATS080I “FROM” LOCATION OUTSIDE OFTRACE TABLE RANGE: fromloc START= start END = endCURRENT = current

Explanation: The “FROM” location that you specifiedon the TRACE subcommand points to a locationoutside of the trace table, while the trace table pointersappear to be valid.

The CURRENT trace table pointer is adjusted to pointto the start of the last entry entered in the trace table.The END trace table pointer is adjusted to the start ofthe entry nearest the bottom of the trace table. You mayuse any of the displayed pointer values to return to thetrace table.

You can start outside of the trace table and scroll intothe trace table. In this case, trace table wrapping willnot occur unless you restore wrapping by issuing aTRACE without a FROM operand, or specify a“FROM” location within the trace table.


User response: Verify the “FROM” location specifiedon the TRACE subcommand, and the trace tablepointers.

v If the “FROM” location is incorrect, reissue theTRACE subcommand with the correct “FROM”location.

v If the trace table pointers are incorrect and the“FROM” location is correct, ignore the message.

ATS081E “FROM” LOCATION NOT A VALIDTRACE ENTRY: fromloc

Explanation: The “FROM” location that you specifiedon the TRACE subcommand does not point to thebeginning of a valid trace entry.


User response: Respond to the message that follows(ATSZTS092I or ATSZTS093I).

ATS082E INVALID TRACE ENTRY FOUND ATaddr

Explanation: The data at location addr is not a validTSAF trace entry.


User response: Respond to the message that follows

(ATSZTS092I or ATSZTS093I).

ATS083E REQUIRED RESOURCES NOTAVAILABLE

Explanation: An error occurred while getting workbuffers to process the TRACE subcommand.



ATS084I PAGE xxxxxxxx NOT FOUND INDUMP

Explanation: It was determined that the address wasto be on a page that does not exist in the dump. Eitherthe TRACE subcommand (module ATSZTS) or theFDISPLAY subcommand (module ATSZTD) may issuethis message.

System action: The subcommand will ignore this pageand continue processing if possible.


ATS085E INVALID TRACE ENTRY FOUND INTRACE FILE

Explanation: The current TRACE entry beingformatted is not a valid TSAF trace entry. This could becaused if part of the entry was not collected in theTRACE file.

System action: The system displays the entry in dumpformat without any formatting.


ATS086E NO TRACE ENTRIES FOUND - addr

Explanation: The TRACE subcommand did not findany trace entries at the specified address. This is causedby all or a portion of a trace entry being on a page thatis not present in the dump.


User response: Enter a TRACE subcommand with the“FROM” option to return to the trace table.

ATS087E ATTEMPT TO GO BEYOND STORAGEBOUNDARY

Explanation: You tried to scroll beyond the dumpstorage boundaries.

System action: Subcommand terminates withoutdisplaying any trace entries.

User response: Enter a TRACE subcommand withouta SCROLL option.


ATS088E UNABLE TO LOCATE TRACE TABLEPOINTERS

Explanation: One of the following occurred:

v IPCS could not find the pointers in the load map, orthe map may be missing or invalid.

v The pointers are on a page that is not present in thedump.

System action: Subcommand terminates and tracetable wrapping is disabled.

User response: Enter a TRACE subcommand with the“FROM” option.

ATS089E UNABLE TO LOCATE GLOBALCONTROL BLOCK (ATSCGM)

Explanation: IPCS did not find the global controlblock, ATSCGM. The map may be missing or invalid.


User response: Use IPCSMAP to append a valid TSAFload map to the dump, and reissue the FDISPLAYsubcommand.

ATS090E UNABLE TO UPDATE THE DUMPWITH THE ABEND PSW ANDREGISTER DATA

Explanation: While extracting information from thedump, the TSAF extraction routine detected an error.This error prevented the routine from updating thedump with the PSW and the register information savedwhen TSAF detected the abend. One of the followingcaused the error:

v A load map was not appended to the dump (shownby an earlier message).

v The IPCS SVC 199 subcodes did not functionproperly.

System action: The system stops extracting data fromthe dump. The system will prompt you for anyinformation that it could not extract from the dump.

User response: Do not rely on the following:

v The register information displayed when you use theregister-related subcommands of DUMPSCAN

v The abend PSW and register information displayedwhen you print the dump using the PRTDUMPfacility

v The information in the symptom record.

If possible, determine the location of the following todebug the problem:

v The abend PSW in the dump

v Register information in the dump (if it exists).

You can find the abend PSW and registers by invokingDUMPSCAN to view the file.

If the TSAF and CMS load maps were not appended tothe dump then locate the appropriate TSAF and CMSload maps and invoke the IPCSMAP subcommand toappend the load maps to the dump.

Once valid load maps have been appended to thedump, use the MAPN subcommand to locate thepointer to the abend PSW and register data. If thecomment on the dump (displayed through theDUMPID subcommand) began with:

ATSCAB1locate the PABNWA field

ATSCAB2locate the PABNWA2 field.

The appropriate field contains the fullword address ofthe TSAF ABEND work area. The first 16 fullwords ofthe abend work area contain the general purposeregisters. Following the registers is the abend PSW.

ATS091E DATA FIELD OVERLAPS TRAILERRECORD

Explanation: While using the FORMAT option, IPCSfound that a trace entry has a data field length greaterthan the room for that data field. For example, a datafield may contain a length value of five bytes, but onlyfour bytes are available before the start of the trailerrecord. A storage overlay of the trace table could causethis.

System action: The system displays the data field upto the overlap and displays this message. The systemwill display the names of any defined data fields that itdid not process, along with this message:

EXPECTED DATA NOT IN TRACE ENTRY

Processing continues.

User response: Use the DISPLAY subcommand tocheck the actual contents of the trace entry.

ATS092I TRACE ENTRY SEARCH STOPPED ATaddr1 TO SEARCH TO LOWER DUMPADDRESSES, TRY ADDRESSaddr2TO SEARCH TO HIGHER DUMPADDRESSES, TRY {ADDRESSaddr3 | “SCROLL”}

Explanation: This message or message ATSZTS093Iwill follow message ATSZTS081E and ATSZTS082E. Aninvalid entry was found. There are no valid entriesbetween the invalid entry address specified in messageATSZTS081E or ATSZTS082E and the search endaddress.


User response: To continue looking for a trace entry,do one of the following:

ATS088E • ATS092I


v Issue the TRACE subcommand with FROM usingaddr2 or addr3.

v Issue the TRACE subcommand with the SCROLLoperand, depending on the information in themessage and the direction you wish to search.

Note: When searching toward the lower dumpaddresses by specifying FROM, the search proceedsfrom the FROM location toward the higher dumpaddresses. Therefore, the first entry found may not bethe entry with the highest address. To view all of thevalid entries that may be present, display the possiblevalid entry, and scroll downward until an invalid traceentry is reached.

ATS093I POSSIBLE TRACE ENTRY AT addr USETHE “FROM” OPERAND TODISPLAY THE ENTRY

Explanation: This message or message ATSZTS092Iwill follow message ATSZTS081E and ATSZTS082E. Aninvalid entry was found, but a possible valid entry wasfound at the address in the message.


User response: Issue a TRACE subcommand with theaddress as the FROM location and a FOR count of 1 todisplay the entry.

ATS094I THE POINTER TO THE SPECIFIEDSTRUCTURE IS ZERO

Explanation: While trying to locate the requested datastructure, the FDISPLAY processing modules detected apointer that contained the value of zero. A zeroedpointer value indicates one of the following:

v The data structure has not been defined.

v The pointer was overlayed.

System action: The subcommand terminates.

User response: Use the DISPLAY and LOCATEsubcommands to try to locate and display the datastructure.

ATS095I THE LINK WAS NOT FOUND IN THELINK-TYPE TABLE

Explanation: You requested a link-type (for example,CTCA) on the FDIPSLAY LINKCTL subcommand.However, TSAF could not find the entry related to thelink-type in the link-type table. The link-type tabledefinition is necessary to process the FDISPLAYLINKCTL subcommand.


User response: Use the DISPLAY and LOCATEsubcommands to locate and display the data structurethat the FDISPLAY subcommand could not display.

ATS096I THE DATA STRUCTURE IS EMPTY

Explanation: The FDISPLAY subcommand detectedthat there are no entries defined in the data structurethat FDISPLAY was to display.



ATS300T Error during HNDIUCV SET, returncode = nnnn

Explanation: TSAF was unable to issue an HNDIUCVSET CMS function during initialization. The nnnn is theHNDIUCV return code.

System action: TSAF will terminate with abend codeATS300.

User response: Restart TSAF. If this message appearsagain, contact your system programmer or servicerepresentative.

ATS302T Cannot connect to *CRM, it is already inuse

Explanation: TSAF was unable to connect to theCollection Resource Management (*CRM) systemservice because it was already in use by another virtualmachine.


Operator response: Determine which virtual machineshould be connected to the *CRM port, and takeappropriate action.

ATS303T Cannot connect to *CRM, not authorized

Explanation: The TSAF virtual machine was unable toconnect to the Collection Resource Management(*CRM) system service because it was not authorized inthe z/VM user directory.


Operator response: Make sure you are running TSAFunder the correct user ID. If it is the correct user ID,report the problem to your system programmer. Youmust check the TSAF virtual machine directory for thecorrect IUCV authorization (that is, it must have an“IUCV *CRM” entry).

ATS304T Error during CMSIUCV CONNECT to*CRM, return code = nnnn

Explanation: TSAF was unable to issue a CMSIUCVCONNECT CMS function during initialization. Thennnn is the CMSIUCV return code.


ATS093I • ATS304T


Operator response: Restart TSAF. If this messageappears again, contact your system programmer orservice representative. Use the CMSIUCV return codeto determine what you should do.

ATS305W MAXCONN is nnnnn but TSAF willenforce a maximum of nnnnn inaccordance with the virtual storage size[nnnnnK]

Explanation: The MAXCONN and the virtual storagesize specified for the TSAF virtual machine are inconflict. TSAF will run with a reduced maximumnumber of connections, which is computed from thevirtual storage size. The computation assumes aminimum size of 6MB for the TSAF virtual machine, atwhich size it allows for support of 128 paths. One morepath is allowed for each 4KB available over the 6MBminimum size. This does not guarantee that thisnumber of paths can be supported (that still dependson how heavily used each path is), it is an indicationthat almost certainly no more paths than the specifiednumber can be supported.

System action: TSAF continues running but will onlyaccept connections up to the second number specifiedin the message.

User response: Decrease the MAXCONN valuespecified in the TSAF virtual machine directory entryor increase the TSAF virtual storage size.

ATS310T Target RECEIVE of PIP indicates badTSAF

Explanation: The TSAF machine failed to provide forPIP data. The PIP data that the target-side TSAF sentwas incorrect and could not be received by the target,or, TSAF mishandled the PIP data which caused anerror in transferring the data to the target. If the PIPdata is incorrect, the last point at which it is known tobe correct is when the source-side TSAF received thedata.

System action: TSAF abends. See message 017I.

Operator response: Contact the appropriate systempersonnel and provide the dump.

ATS350I User userid connect to resource is severed;pathid nnnnn exceeds the connectionlimit determined by TSAF

Explanation: TSAF is enforcing the connection limitstated in previous message ATS305W. TSAF hasdetermined that this number of paths cannot besupported with the amount of virtual storage given tothe TSAF virtual machine.

System action: The connection is severed with anIPCODE value of X'0610' and TSAF operationcontinues.

User response: Notify the appropriate systems

personnel for your enterprise. You may be successful ifyou retry your application at a later time, but this isdependent on the usage level of TSAF at the time.

ATS511W Completion time expired whileattempting a JOIN

Explanation: This TSAF virtual machine was unable tojoin a collection within the expected time. This happenswhen several TSAFs are trying to join each other at thesame time or when there has been a sharp increase inload coincident with the attempt to join. It can alsohappen because of a collection partition that thecollection has not yet detected.

System action: The TSAF virtual machine will reset itscollection management structures and try again to joinan appropriate collection.

Operator response: No action is necessary. However,if this happens repeatedly, it may be because there aretoo many systems trying to join the collection (morethan eight systems). Display the collection table at theagent node (the node that this one is trying to join) todetermine the current collection size. If the collectionalready has the maximum number of nodes, then deletethe link from this node to the agent to preventunnecessary repetitions of the attempt to join.

ATS513I Attempting JOIN with node nodeid asthe agent

Explanation: This TSAF virtual machine is trying tojoin a collection by sending a request-to-join message tonode nodeid. If nodeid is not busy (already engaged in ajoin) it will become the agent for this TSAF virtualmachine in the join protocol.

System action: A request-to-join message is sent tonodeid.


ATS514W JOIN aborted because of I-message fromnode nodeid

Explanation: Something changed at another TSAFvirtual machine in the collection after the join protocolwas started here. This is a normal occurrence whenseveral TSAF virtual machines are involved.

System action: The TSAF virtual machine will reset itscollection management structures and try again to joinan appropriate collection.


ATS515I Join in progress for node nodeid. Agentis agnode.

Explanation: This TSAF collection has begun joinprocessing for node nodeid. Node agnode is responsiblefor executing this join. This message is sent to the TSAF

ATS305W • ATS515I


virtual console for each member of the TSAF collection.

System action: This TSAF virtual machine adds nodeidto its collection table and schedules the first joinsynchronization. If this TSAF virtual machine is theindicated agent node, it also sends the nodeid thecurrent collection management structures.


ATS516I Node nodeid cannot join, maximumcollection size has been reached

Explanation: The collection that nodeid is trying to joinis at its maximum allowable size.

System action: Node nodeid is not allowed to join. Thejoin protocol is aborted.

Operator response: Delete the links between nodenodeid and the current collection to prevent unnecessaryattempts to join.

ATS518I RESET: collection now has size 1

Explanation: The TSAF virtual machine reset itscollection management structures to show it as the onlymember of its collection. This is a normal occurrencefollowing an unsuccessful attempt to join a collection. Itis also one of the stages of initialization. No sessionsare interrupted by the reset action. However, newconnections cannot be made to remote resources untiltheir collection has been joined.

System action: The TSAF virtual machine will nowtry to join an appropriate collection by issuinghandshake messages on all available links.


ATS520I Synchronization is now NORMAL

Explanation: The logical clocks of the collection aresynchronized. This action takes place periodically andat the completion of the join protocol. These messageswill be sent to the operator consoles of all members ofthe collection, including the joiner.

System action: The system adjusts the logical clocks tomaintain synchronization.


ATS521I Collection is roughly synchronized

Explanation: This is the first synchronization event ofthe join protocol. The joining node sets its logical clockas close as possible to the clocks of the collection it isjoining. The other nodes send the synchronizationmessages that will allow it to do this. These messageswill be sent to the operator consoles of all members ofthe collection, including the joiner.

System action: If this TSAF virtual machine is acurrent member of the collection, it sends a

synchronization message to the joiner. If this TSAFvirtual machine is the joiner, it has receivedsynchronization messages from a majority of thecollection, and can now set its logical clock.


ATS530E Authentication check failed on messagefrom node nodeid Message type: mtype.

Explanation: Node nodeid sent an atomic broadcastmessage, of type mtype, that did not pass TSAF'sauthentication tests.

System action: The system ignores the message.

Operator response: This output can be correlated withthe output from the QUERY STATus command todetermine what node, if any, failed to authenticate themessage.

ATS531E Timeliness check failed on messagefrom node nodeid. Function=cc, Currenttime=curtime, Origin time=origtime,Performance time=perftime

Explanation: An atomic broadcast message from nodenodeid did not pass the timeliness tests. This happensafter an unsuccessful attempt to join. However, if ithappens frequently, node nodeid may be experiencingsome trouble.

System action: The system ignores the message.

Operator response: No action is necessary. However,if many nodes show this message referring to nodenodeid more than once, and the problem does notcorrect itself within a few minutes, restart the TSAFvirtual machine on node nodeid.

ATS540I Node nodeid deleted from collection

Explanation: The node nodeid has been deleted fromthe collection table of each node in the collection. Thishappens after a detected partition; the collectionmanagement structures of nodeid no longer agree withthe rest of the collection or are not available becausenodeid stopped communicating. If nodeid is stillcommunicating, no sessions are broken. As long as allcomponents are still working correctly, the systemrepairs the problem by the join protocol.

System action: Node nodeid is removed from thecollection table. The system attempts to rejoin the nodeusing handshake messages.


ATS545I Join rejected by node nodeid

Explanation: The TSAF virtual machine attempted tojoin a TSAF collection. However, the indicated noderejected this attempt.

ATS516I • ATS545I


System action: The TSAF virtual machine will attemptto join the TSAF collection later.


ATS546I Quiesce broadcasts issued by nodeid

Explanation: Node nodeid has started to process a joinrequest. The TSAF virtual console for each member ofthe TSAF collection will receive this message.

System action: The TSAF collection prepares to add anode to the collection and starts join processing asrequested by node nodeid.


ATS547I Quiesce broadcasts issued by nodeidtimed out

Explanation: The join request started by node nodeiddid not complete. The time period allotted for joinprocessing has expired.

System action: The TSAF virtual machine returns tonormal operation.


ATS600S Message with invalid frame typereceived: frame-type

Explanation: The routing group has received a framewith a frame-type value that it is not prepared tohandle.

System action: The system discards the message andcontinues processing.

Operator response: Contact your system programmeror service representative.

ATS601E Frame discarded. Hop-Count limitreached.

Explanation: Upon receiving a frame to forward toanother node, the routing group found that the frameexceeds the forwarding limit.

System action: The system discards the frame andcontinues processing.


ATS602E Incompatible release or service leveldetected on link linkunit

Explanation: The TSAF virtual machines attempting tocommunicate through link linkunit are incompatible.

System action: The link linkunit is deleted from theATSLINKS file and you will get message 713I. Furthercommunication on the link is prevented until theproblem is fixed.

Operator response: Contact your system programmer.

ATS603E Duplicate node nodeid detected on linklinkunit

Explanation: A node with the node ID nodeid isalready in the TSAF collection.

System action: The link linkunit is deleted from theATSLINKS file and you will get message 713I. Furthercommunication on the link is prevented until theproblem is fixed.

Operator response: Contact your system administratorso that he can assign a new and unique node ID to thenode indicated in the message.

ATS604E Incompatible release or service leveldetected on logical link to LAN nodenodeid on link logical_linkunit

Explanation: The TSAF virtual machines attempting tocommunicate through logical link logical_linkunit areincompatible.

System action: The logical link logical_linkunit isdeleted from the ATSLINKS file, and you will getmessage ATS713I. Further communication on the logicallink is prevented until the problem is fixed.


ATS605E Duplicate node nodeid detected onlogical link to LAN node LAN_nodeid onlink logical_linkunit

Explanation: A node with the node ID nodeid isalready in the TSAF collection.

System action: The logical link logical_linkunit isdeleted from the ATSLINKS file and you will getmessage ATS713I. Further communication on the logicallink is prevented until the problem is fixed.

Operator response: Contact your system administratorso that he can assign a new and unique node ID to thenode indicated in the message.

ATS700E Link-Definition table overflow, unableto add the new link linkunit

Explanation: To add the new link, the system mustexpand the Link-Definition table, but there is notenough storage available to do so.

System action: The system does not accept thedefined link.

Operator response: Deleting one or more unneededlinks may allow a new one to be added. This conditionindicates that the virtual machine is severely short ofvirtual storage. Whatever is freed by the DELETE LINKcommand(s) may be exhausted by other TSAF storagerequirements before the ADD LINK command can be

ATS546I • ATS700E


issued again. Contact your system programmer tocorrect this shortage.

ATS701E Driver rejected the new link linkunit

Explanation: The link driver could not complete theaddition of the new link. See the message issued beforethis for the reason.

System action: The system does not add the specifiedlink.

Operator response: Take action according to thepreceding message.

ATS702E Link unit address vdev is not valid

Explanation: The specified virtual device address isnot defined for the virtual machine or is not a validdevice address, that is, it is not a one, two, or threedigit hexadecimal number.


Operator response: Correct the command andresubmit it, or have the virtual device attached to thisvirtual machine as the specified unit address.

ATS703E Link linkunit is not a supported linktype

Explanation: The device at the specified virtual unitaddress does not have the required characteristics for aCTCA link.


Operator response: Check that the correct device isattached to the virtual machine, correct the command ifnecessary, and re-enter the command.

ATS704E Record number nnnnnnnn in ATSLINKSFILE is not valid

Explanation: The record does not have a correctlyspecified virtual unit address.

System action: The system does not add the linkcorresponding to the record.

Operator response: Examine the ATSLINKS FILE.Correct the record that is in error.

ATS705I Link linkunit went down

Explanation: The link group cannot get a responsefrom the other end of this link. The link device mayhave a malfunction (in this case, you may havereceived other messages). Other reasons that you mayget this message are that a processor went down orthat the TSAF virtual machine at the other end of thelink went down.

System action: The system will try to use the linklater.

Operator response: Examine the link state and have itfixed if you discover any malfunctions. If there is noproblem with the link itself, check on the status of theneighboring system.

ATS706W Received an interrupt on unit vdev,which is not in the link table

Explanation: An unexpected interrupt was receivedfrom the specified virtual device. The link device mayhave a malfunction.

System action: The system ignores the interrupt.

Operator response: You do not need to take actionunless the condition persists. If the condition doespersist, notify your system programmer or servicerepresentative.

ATS707I Link linkunit came up

Explanation: The link group got a response from theother end of this link.

System action: The system will use the new link.


ATS708E An attempt to reset link vdev has failed

Explanation: The driver tried to run a channelprogram to reset the link device, but the channelprogram did not complete as expected.

System action: The system will try to use the linklater.

Operator response: Check the hardware unitsassociated with the link. If you do not find a problem,contact your system programmer or servicerepresentative.

ATS710E Unable to allocate control block for linklinkunit

Explanation: To add the new link the system mustallocate a link control block, but there is not enoughstorage available to do so.


Operator response: Deleting one or more unneededlinks may allow a new one to be added. This conditionindicates that the virtual machine is severely short ofvirtual storage. Whatever is freed by the DELETE LINKcommand(s) may be exhausted by other TSAF storagerequirements before the ADD LINK command can beissued again. Contact your system programmer tocorrect this shortage.


ATS711E Unable to allocate I/O buffer for thelink linkunit

Explanation: The attempt to add the link failed.


Operator response: Deleting an unneeded link toallow a new one to be added would not work in thiscase. This condition indicates that the virtual machineis severely short of virtual storage. Contact your systemprogrammer to correct this shortage.

ATS712E Link unit address vdev is a duplicate

Explanation: A link that uses this virtual unit addresshas already been added.

System action: The system does not add the link.

Operator response: Delete the other link, or correctthe command and re-enter it.

ATS713I Link linkunit deleted

Explanation: The link that you specified has beendeleted.

System action: The system deletes the link.

Operator response: None

ATS714E Link symbolic destination name symdestis a duplicate

Explanation: A link that uses this symbolic destinationname already exists.


Operator response: Delete the existing link or retrythe ADD LINK command with another symbolicdestination name.

ATS715E Failed to add the definition of linklinkunit to ATSLINKS FILE A1. Returncode from FSWRITE was nnnn

Explanation: The system could not modify thedefinition file, ATSLINKS FILE, as specified by theADD LINK command.

System action: The system continues operation andwill use the defined link, despite the error. However,TSAF will not automatically use the link the next timeTSAF starts.

Operator response: Contact your system programmer.You will have to add the new link's definition manuallyto ATSLINKS FILE A1.

ATS716E Driver rejected the request to delete linklinkunit

Explanation: An internal TSAF or CMS error occurred,which prevented TSAF from an active link.

System action: The system does not accept the deleterequest.

Operator response: Retry the command. If the retrydoes not work, inform the system programmer. Thelink's definition can later be manually deleted from thefile ATSLINKS FILE. If a non-APPC link must beremoved immediately, detach it from the virtualmachine. If an APPC link must be deleted immediately,you must stop TSAF (issue STOP TSAF) at the nextconvenient time. When you stop TSAF for either typeof link, edit the ATSLINKS FILE to remove the link,and restart TSAF.

ATS717E Unable to retrieve sense bits from unitvdev, CSW is csw

Explanation: Following an I/O error, the link drivertried to issue a Sense I/O channel command to the linkdevice. However, the link driver did not get theexpected sense bits.

System action: The system continues operation, butthe TSAF virtual machines may partition the collectionsince the link may not be usable.


ATS718E Severe I/O error on unit vdev, CSW iscsw

Explanation: The link drive encountered a severe I/Oerror on the specified virtual device. The systemdisplays the Channel Status Word, indicating the error.

System action: The system continues operation, butthe TSAF virtual machines may partition the collectionsince the link may not be usable.


ATS719W ATSLINKS FILE not found

Explanation: The file that TSAF uses to permanentlyrecord link definitions does not exist on the virtualmachine's A-disk.

System action: The system continues operation, butno link definitions exist.

Operator response: If this is not an expectedcondition, contact your system programmer. The TSAFvirtual machine may be missing the appropriate LINKSand ACCESSES.

ATS711E • ATS719W


ATS720E Failed to delete the definition of linklinkunit from ATSLINKS FILE A1.Return code from FSREAD was nnnn

Explanation: While trying to do a deletion, a readerror occurred on the file that TSAF uses topermanently record link definitions.

System action: The system continues operation. Thesystem will not use the defined link, despite the error.

Operator response: Contact your system programmer.You must eventually delete the file or perform somesort of file recovery such as restore from a backup.

ATS721E Failed to delete the definition of linklinkunit from ATSLINKS FILE A1.Return code from FSWRITE was nnnn

Explanation: While trying to do a deletion, a writeerror occurred on the file that TSAF uses topermanently record link definitions.

System action: The system continues operation. Thesystem will not use the defined link, despite the error.

Operator response: Contact your system programmer.You must eventually delete the file or perform somesort of file recovery, such as restore from a backup.

ATS722I No links are defined

Explanation: This is a response to the TSAF QUERYLINK command.



ATS723E Link linkunit not found

Explanation: This is a response to a TSAF QUERY orDELETE LINK command.


Operator response: Retry the appropriate TSAFcommand and specify another link.

ATS724I Link linkunit added

Explanation: This is a response to the TSAF ADDLINK command.

System action: The system will now try to use thislink.


ATS725E vdev is not a valid device address forlink type linktype

Explanation: You specified an invalid device addressin the ADD LINK command. The subchannel portion of

the first address must be in the range of X'00' throughX'F8'.

System action: The defined link is not accepted.

User response: Reenter the command with the correctdevice address. If the problem continues, contact yoursystem programmer or system administrator.

ATS726E Link-Definition table expansion failed,unable to add logical link for LAN linkvdev

Explanation: Due to lack of storage, recordinginformation about a node on the Local Area Network(LAN) that connects TSAF failed.

System action: Communication with the specifiednode is not possible.

User response: You must provide the TSAF virtualmachine with more storage and restart it now or whenlocal operating procedures indicate. Otherwise, contactyour system programmer or system administrator.

ATS727E Unit vdev is not a valid device for linktype linktype

Explanation: One of the four addresses for Ethernet**LAN (ELAN) or Token Ring LAN (TLAN) subsystemlinks is not a 3088 type of device and/or does notreturn device-specific data indicating that the device isa 9221 LAN subsystem, or the consecutive virtualdevice addresses do not map to consecutive realaddresses.

System action: The link is not accepted.

User response: Reenter the command with the correctdevice address. Make sure the correct device is attachedto the TSAF virtual machine and there is not an errorin the TSAF VM directory entry or in the system I/Odefinition. Otherwise, contact your system programmeror system administrator.

ATS730E Unit linkunit DIAGNOSE X'98' error,return code rc

Explanation: The link driver could not completeinitialization for the indicated link.


User response: Fix the problem as indicated by thereturn code. For more information about DIAGNOSEX'98' return codes, refer to z/VM: CP ProgrammingServices.

ATS735I Logical link to LAN node LANaddr onlink vdev went down

Explanation: The logical link created by TSAF cannotreceive a response from the other TSAF node on theLAN. The link device may have a malfunction (in this

ATS720E • ATS735I


case, you may have received other messages). You canalso get this message if a processor went down or theTSAF virtual machine at the other end of the link wentdown.

System action: The system retries the link every 65-90seconds.

User response: Examine the link state and have itfixed if you discover any malfunctions. If there is noproblem with the link itself, check the status of theneighboring system.

ATS737I Logical link to LAN node LANaddr onlink vdev came up

Explanation: The logical link created by TSAF cannotreceive a response from the other TSAF node on theLAN.

System action: The system uses the new link.


ATS738E Unable to identify resource resid toCMS. HNDIUCV SET function failed.R15 = xxxx

Explanation: TSAF was unable to identify the resourcename to CMS.

System action: TSAF communications across APPClinks will not work.

Operator response: Use the R15 return code todetermine why the HNDIUCV SET function failed andcorrect the problem. Stop TSAF (issue STOP TSAF) andrestart TSAF (issue RUNTSAF) at the next convenienttime. If the problem continues, contact your systemprogrammer or system administrator.

ATS739E APPCVM macro failed on link symdest.IPSENDOP = xx, IPAUDIT = xx

Explanation: TSAF was unable to process data acrossan APPC link.

System action: The appropriate APPC link will bebrought down. TSAF will attempt to bring the linkback up the next time it monitors the status of the link.

User response: Use the return codes to determine whythe APPCVM macro failed and correct the problem. Ifthe problem continues, contact your systemadministrator or system programmer.

ATS740E CMSIUCV ACCEPT function failed onlink symdest. R15 = xxxx

Explanation: TSAF was unable to establishcommunications on an APPC link.


User response: Use the R15 return code to determinewhy the CMSIUCV ACCEPT function failed and correctthe problem. If the problem continues, contact yoursystem programmer or system administrator.

ATS741E APPCVM RECEIVE function failed onlink symdest. IPRCODE = xx

Explanation: TSAF was unable to receive data acrossan APPC link.

System action: The appropriate APPC link will bebrought down. TSAF will attempt to bring up the linkthe next time it monitors the status of the link.

User response: Use the IPRCODE return code todetermine why the APPCVM RECEIVE function failedand correct the problem. If the problem continues,contact your system programmer or systemadministrator.

ATS742E CMSIUCV CONNECT function failedon link symdest. R15 = xx

Explanation: TSAF was unable to establishcommunications on an APPC link.


User response: Use the R15 return code to determinewhy the CMSIUCV CONNECT function failed andcorrect the problem. If the problem continues, contactyour system programmer or system administrator.

ATS743E APPCVM SENDDATA function failedon link symdest. IPRCODE = xx

Explanation: TSAF was unable to send data on anAPPC link.


User response: Use the IPRCODE return code todetermine why the APPC SENDDATA function failedand correct the problem. If the problem continues,contact your system programmer or systemadministrator.

ATS744E Invalid transaction program name tpn1specified in the CMS communicationsdirectory for link symdest. Thetransaction program name must be tpn2

Explanation: The transaction program name specifiedin the CMS communications directory on the TSAFvirtual machine's user level directory is invalid for thespecified link.

System action: The appropriate APPC link will not beadded.

ATS737I • ATS744E


Operator response: Replace the invalid transactionprogram name with the correct transaction programname specified in the error message. Retry the ADDLINK command. If the problem continues, contact yoursystem programmer or system administrator.

ATS745E The gateway name gatelu and target LUname targetlu combination for linksymdest is a duplicate

Explanation: The gateway name and target LU namecombination is already defined for an existing APPClink.

System action: The appropriate APPC link will not beadded.

Operator response: Replace the gateway name andtarget LU name combination specified in the CMScommunications directory on the TSAF virtual machine.Retry the command. If the problem continues, contactyour system programmer or system administrator.

ATS746E APPCVM SENDDATA function failedon link symdest. IPCODE = xx,IPWHATRC = xx

Explanation: TSAF was unable to send data on aAPPC link.


User response: Use the return codes to determine whythe APPC SENDDATA function failed and correct theproblem. If the problem continues, contact your systemprogrammer or system administrator.

ATS747E APPCVM RECEIVE function failed onan APPC link. IPRCODE = xx

Explanation: TSAF was unable to receive data whiletrying to establish an APPC link.

System action: The appropriate APPC link will not bebrought up. TSAF will attempt to bring up the link thenext time it monitors the status of the link.

Operator response: Use the IPRCODE to determinewhy the APPCVM RECEIVE function failed and correctthe problem. If the problem continues, contact yoursystem programmer or system administrator.

ATS748E APPCVM macro failed on link symdest.IPSENDOP = xx, IPWHATRC = xx

Explanation: TSAF was unable to process data on anAPPC link.


User response: Use the return codes to determine whythe APPCVM macro failed and correct the problem. Ifthe problem continues, contact your systemprogrammer or system administrator.

ATS794I Sense bits are ‘xx’X

Explanation: An I/O error on the link caused the linkdriver to do a Sense I/O to the device.

System action: The system will try the I/O again later.


ATS795I Retry limit exceeded on unit vdev

Explanation: An I/O error occurred on the device andthe I/O was retried without success.

System action: The system will try the I/O again later.


ATS796I Bad I/O completion on unit vdev, CSWis csw

Explanation: The link driver did not get the expectedresult.

System action: The system will try another I/Ooperation some time later.


ATS797I Unit-check indicated on unit vdev

Explanation: The CSW indicated a unit check on thespecified device.

System action: The system will try another I/Ooperation later.


ATS798W Unexpected CSW (csw) for unit vdev

Explanation: The specified CSW was not expected asa result of the last I/O operation.



ATS799I Unit vdev is not operational

Explanation: You will get this message in response toone of the following:

v The TSAF ADD LINK command

v Any time that TSAF receives a not operationalindication on an I/O operation to the specifiedvirtual device.


ATS745E • ATS799I


Operator response: Check to see that the device isproperly connected to the system. If all connections arecorrect and the system programmer verifies that the CPsystem generation is correct, then the device needs tobe repaired.

ATS888T Unable to obtain storage for structure

Explanation: The TSAF module that issued themessage has issued a request to CMS to get storage forthe specified structure, structure. CMS diagnosed anerror on the request. The problem may have occurredbecause the TSAF virtual machine had insufficientvirtual storage.

System action: TSAF will abend with code ATS888.

Operator response: Provide more storage for theTSAF virtual machine, and restart TSAF. If it failsagain, contact your system programmer or servicerepresentative.

ATS890T Unable to release storage for structure

Explanation: The TSAF module that issued themessage has issued a request to return to CMS thestorage for the specified structure. CMS diagnosed anerror on that request.


Operator response: Keep the problem information andcontact your system programmer or servicerepresentative.

ATS999T TSAF system error.

Explanation: The TSAF module that issued thismessage encountered a condition that should not haveoccurred




VMSES/E MessagesVMSES/E issues messages with two different prefixes; VMF and ITN. For messageexplanations, system actions, and suggested user responses, refer to “VMF002E -VMF1490E,” “VMF1507E - VMF3064I” on page 175, and “ITN2000E - ITN2050E”on page 259.

VMF002E - VMF1490E

VMF002E messages

Explanation: The variations of this message are:

v File fn ft not found

v Update file fn ft not found

v Control file fn ft not found

v Product parameter file fn ft not found

v Part handler fn ft not found

v User exit fn ft not found

v Build list fn ft not found

v PTF part list fn ft not found

v Part fn ft of PTF ptfnum not found

v Apply list fn ft not found

v Message log fn ft not found

v Product exec fn ft not found

v Software Inventory file fn ft not found

v Envelope fn ft not found

v Product processing exit fn ft not found

v Language function fn ft not found

v Product parts file fn ft not found

v Parts catalog fn ft fm not found

The specified file is required by the procedure beingrun but does not exist on the appropriate set of disks.The set of disks being searched depends on the file.

System action: RC = 8 or 28.

On a return code of 8, the command processingcontinues bypassing the failing sub-function. On areturn code of 28, the command processing stops dueto the file not found condition.

User response: Determine why the file was not found.Possible reasons include:

v The required disks were not accessed.

v The required file was inadvertently erased.

v An incorrect file was specified.

v If the message was issued for an apply list, VMFRECmay not have been run prior to VMFAPPLY. In thiscase, the apply list that is being searched for has notbeen loaded to disk yet.

If the correct file can be located, ensure that it is on thecorrect disk and the disk is accessed. Then retry theprocedure.

VMF002W Tailored part fn ft not found

Explanation: During migration the specified file couldnot be found on any accessed disks. The tailored partwas not migrated to the new product.

System action: RC = 4. Command processingcontinues.

User response: If the tailored file is located, migratethe tailored file manually to its target disk. If the filewas not found, then the tailorings will have to bemanually added to the new file.

VMF003E Invalid option option

Explanation: The specified option is invalid. This mayhave been caused by one of the following:

v It may have been misspelled.

v If the option is truncatable, it may have beentruncated improperly.

v It may conflict with another option in the commandline.

v It may be invalid with a command parameter.

System action: RC=24.

Command processing is terminated. The system statusremains the same.


VMF017E Invalid device [address vdev | typedevtype]

Explanation: If the first variation appears then eitherthe device address was not specified correctly or thedevice was not accessed. If the second variationappears then the device type entered is not a supporteddevice type.


Command processing stops because of the externalerror.

User response: Check the specified device addressand reissue the command. The valid device addressesfor z/VM are:

v 0001 through 1FFF for a System/370 mode virtualmachine

v 0001 through FFFF for a 370-XA or XC mode virtualmachine

VMF002E • VMF017E


If the device type is invalid, rerun the command with avalid device type.

VMF056E File fn ft fm contains invalid recordformat

Explanation: The specified file is being used by thePatch facility and the file has entries which are notvalid. Possible causes are:

v No loader was specified in the build list

v An entry in the CNTRL file was not valid

v The Patch update file has missing or incorrectstatements

System action: RC = 12.

Command processing stops because of the internalerror.

User response: Review the description of the PatchFacility and the syntax of Patch Update files, build listsand CNTRL files. Make any necessary corrections andreissue the command.

VMF066E [option1 and option2 are conflictingoptions | Conflicting option option withoperand operand]

Explanation: The specified options are conflicting.This may have been caused by one of the following:

v The specified options are mutually exclusive andmust not be specified in the same command.

v It may be in conflict with a command operandparameter.

System action: RC=24. Command processing stopsbecause of the command syntax error.

User response: Enter the command again after theconflicting option has been removed.

VMF071E ERASE * * fm|* not allowed

Explanation: You cannot erase all files on all accessedfile modes using the ERASE command. You can enterasterisks for the file name and file type, but you mustspecify the file mode letter and number.

System action: RC=24. Command executionterminates. The system status remains the same.

User response: To erase all files on a minidisk, enterthe FORMAT command. For both minidisks and SFSdirectories, you can erase all files by using the ACCESScommand with the ERASE option. (All files on the diskor directory are erased the first time you write a newfile on the disk or directory.)

VMF104E Error nnn reading file fn ft fm [from diskor directory] [RC = rc from command]

Explanation: An irrecoverable error occurred whilereading the file from a disk or an SFS directory.Internally, the FSREAD macro reads the file. The nnn isthe return code from FSREAD and indicates the natureof the error. For FSREAD return code definitions, referto z/VM: CMS Macros and Functions Reference.

System action: RC=100. Command processing stopsbecause of the external error.

User response: If you can determine the problem fromthe Explanation, remedy the condition and enter thecommand again. If not, retry the command. If theproblem persists, call your system support personnel.

The problem may be that the in-core directory for theminidisk that contains the file being loaded does notmatch the actual directory. The real disk directory mayhave been changed since the disk was last accessed, orif on the system disk, the saved system may need to besaved again.

For error code 09, enter an FSCLOSE macro for the file.If a permanent disk read error occurs (code 3), it maybe the result of the user having detached a virtual diskwithout releasing it. Not realizing that the disk is nolonger part of the virtual machine, CMS assumes thatthe disk is still active, and encounters an error when ittries to read or write the file.

VMF113E Printer 00E not attached

Explanation: The specified device is not attached tothe virtual machine.


User response: Use the CP command DEFINE toattach the device to your virtual machine.

VMF130E Member name not found in library libfnlibft libfm

Explanation: The member specified was not found inthe temporary macro library libfn libft libfm that wascreated. The member name specified in the message isneeded to generate the CP load exec. The label name inthe macro may be different than the macro file name.

System action: RC=28. Processing terminates becausethe member was not found in the library.

User response: Change the label name to be the sameas the macro file name and enter the command again.

VMF156E {FROM|Record} nnn not found--[the]file [fn ft fm] has only nnn records.

Explanation: The FROM option was given in thecommand line or set up by the DEFAULTS command

VMF056E • VMF156E


to specify the starting record of the copying operation,but the specified input file does not contain that manyrecords.


User response: Enter the command again, specifying avalid starting record.

VMF283E The name saved segment could not befound; condition code cc, return code rcfrom FINDSYS

Explanation: This error was caused by one of thefollowing reasons:

v The FINDSYS function (DIAGNOSE code X'64') didnot find the specified saved segment.

v If the condition code is 2 and the return code is 44,the saved segment has not been defined on a CPDEFSEG and CP SAVESEG command.

For a complete description of the FINDSYS functionand its return codes, refer to z/VM: CP ProgrammingServices.

System action: RC=128. Execution of the commandterminates.

User response: Respond according to why themessage was generated.

The return code is related to a DIAGNOSE X'64' errorfollowing invocation by the FINDSYS command. Formore information about DIAGNOSE X'64', refer toz/VM: CP Programming Services.

VMF337E Saved segment name name is longerthan eight characters

Explanation: The name of a saved segment cannot bemore than eight characters long.

System action: RC=24. Command processing stops.

User response: Start the command with a valid savedsegment name.

VMF386E Missing operand(s)

Explanation: One or more operands were missing onthe invocation of the previously issued command.


User response: Reissue the command with the correctsyntax.

VMF387E Missing value_type for operand operand

Explanation: The value_type is missing for theindicated operand. The possible variations forvalue_type that can appear in the message text are:

v alphanumeric string

v application identifier

v character [string]

v device address

v directory id

v execname

v exectype

v filemode[[, filepoolid,] or directory id]

v filename

v filepoolid

v filetype

v [hexadecimal] number

v [negative|positive] integer

v value


User response: Enter the command again with thecorrect syntax.

VMF389E Invalid operand_type: operand

Explanation: The indicated operand is not valid for theoperand_type. The possible variations for operand_typethat can appear in the message text are:




v compname

v device address

v directory id

v execname

v exectype


v filename

v filepoolid

v filetype


v namedef


v operand

v REXX [stem] variable

v tag

v PTF/APAR number

System action: RC=24. Command processing stopsbecause of the syntax error.

VMF283E • VMF389E



VMF390E Invalid value_type value for operandoperand

Explanation: The value_type value is not valid for theindicated operand. The possible variations forvalue_type that can appear in the message text are:




v device address

v directory id

v execname

v exectype


v filename

v filepoolid

v filetype


v namedef



v tag

v value



VMF391E Unexpected operand(s): operands

Explanation: The operand(s) operands should notappear where they do on the invocation of thiscommand.



VMF392E Missing option option

Explanation: A required option was missing on theissued command. Required options are based on theother operands and options specified.



VMF393E Missing value_type for option option

Explanation: The value_type is missing for theindicated option. The possible variations for value_typethat can appear in the message text are:




v device address

v directory id

v execname

v exectype


v filename

v filepoolid

v filetype


v namedef

v [negative|positive]integer


v tag

v value



VMF394E Invalid option: option

Explanation: The option given on the invocation ofthis command is not valid.



VMF395E Invalid {value_type value|tag_name stringstring_name} for option option

Explanation: One of the following was not valid forthe indicated option:

v The value entered for the value_type indicated; thepossible variations for value_type that can appear inthe message text are:

– alphanumeric string

– application identifier

– character [string]

– device address

– directory id

– execname

– exectype

– filemode[[, filepoolid,] or directory id]

VMF390E • VMF395E


– filename

– filepoolid

– filetype

– [hexadecimal] number

– namedef

– [negative|positive] integer

– REXX [stem] variable

– tag

– value

v The string_name entered relating to the tag_nameindicated.

System action: RC=24. Command processing stopsdue to the command syntax error.


VMF448E Country code code not in VMFNLSLANGLIST

Explanation: The source file name specified on theVMFNLS command contains a country code (code) thatis not in the VMFNLS LANGLIST file. The countrycode is the 7th and 8th characters of the source filename.


User response: Rerun VMFNLS with a source filewhich contains a valid country code.

VMF622E Insufficient storage for VMFRDTBL

Explanation: Insufficient storage was available forVMFRDTBL.


User response: Correct the problem and restart theprocedure.

VMF622W Insufficient free storage for VMFRDTBLbuffer; processing continues

Explanation: Insufficient storage was available forVMFRDTBL to create a buffer containing informationfor the input file. The requested buffer size, or the sizeof the file, was too large in terms of the available freestorage.

System action: RC=4. Command processing continues.No buffer is created, and processing continues readingthe input file from the disk. The buffer size is set to 0so future invocations of VMFRDTBL will not cause thiswarning to be displayed.


VMF633E Too many tags wereencountered--maximum is 64 per line

Explanation: While searching the input file, an entrywas encountered that contained more than 64 tags(overflowing the internal tag tables of the VMFRDTBLcommand). This record was not processed correctly byVMFRDTBL.


User response: Ensure the entries in your input file donot have more than 64 tags, then enter the commandagain.

VMF633W Returned values were truncated

Explanation: The values returned were too long andwere truncated.

System action: RC=88. The values are truncated.


VMF634E No value to search for was specified

Explanation: The VMFRDTBL command was enteredwithout a search value (a tag with a value).


User response: Enter the command again with at leastone tag with a value to indicate what VMFRDTBLshould search for.

VMF635I No entries were found that matchedyour search criteria

Explanation: VMFSIM was unable to locate an entrythat matches the search criteria specified on thecommand line.

System action: RC=32. Processing completes.


VMF1015E EXECIO error reading file fn ft fm fromdisk

Explanation: There was an I/O error reading theindicated file.

System action: RC=100. Command execution stops.

User response: If the disk is read-only, ensure it hasnot been modified since the last access, and tryaccessing the disk again. For more information aboutthe EXECIO command, refer to z/VM: CMS Commandsand Utilities Reference.


VMF1016E EXECIO error writing file fn ft fm ondisk

Explanation: There was an I/O error writing theindicated file.


User response: Correct the problem and start thecommand again. For more information about theEXECIO command, refer to z/VM: CMS Commands andUtilities Reference.

VMF1032I The following products were selected:

Explanation: You pressed the PF5 EXECUTE key onthe DIRECGEN panel and the list of selected productsis displayed.

System action: Command execution continues.

User response: Review the list to make sure youselected the correct products.

VMF1034E Invalid product specification codeprodspec; correct your input and runINSTFPP again for all selected products

Explanation: You passed an invalid productspecification code as a parameter to INSTFPP. Aproduct specification code is seven to nine characterslong and is a combination of the product number andthe feature identification code. If there is no featureidentification code for this product, then the productspecification code must be exactly seven characterslong. You can leave a blank between the productnumber and the feature identification code.

System action: RC = 24. Command execution stops.

User response: Invoke the command with a validproduct specification code. Refer to the FEATURE$PRODUCTS file, Program Directory, or Memo to Usersto obtain the valid product specification code.

VMF1035W prodnum must be entered with a featureidentification code; prodnum idcode wasfound on the tape

Explanation: The product prodnum has features. Eachfeature has its own feature identification code. Youmust specify both the product number and the idcodetogether on the command line.


User response: Invoke the command with validproduct specification codes.

VMF1036I Memo to Users, fn ft, has been printed

Explanation: The Memo to Users for the optionalfeature being processed has been spooled to the virtualprinter.


User response: Retrieve the printed file from the realprinter if the appropriate spooling options are in effect.

VMF1037W The following selected product numberswere not found on the tape: prodnums

Explanation: One or more of the products specified onthe command line or selected from the panel is not onthe tape at virtual address 181. The wrong tape mightbe mounted, or you did not correctly enter the productspecification codes on the command line.

System action: RC = 85. Command executioncontinues.

User response: Make sure the correct tape is mounted,and invoke the command with the correct parameters.

VMF1038E Error printing fn ft fm; return code rcfrom the CMS PRINT command

Explanation: The PRINT command with the CCoption failed while trying to print the Memo to Users.


User response: Correct the problem and invoke thecommand again. For more information about thePRINT command, refer to z/VM: CMS Commands andUtilities Reference.

VMF1039E Terminal is in line mode, so theINSTFPP user assistance panel cannotbe displayed; INSTFPP arguments mustbe entered on the command line

Explanation: You must invoke INSTFPP withparameters and/or options if the terminal is in linemode, even if you want all the default options.


User response: Invoke the command with parametersand/or options.

VMF1041E Error {scanning|forwarding} tape vdev;return code rc from the CMS VMFPLC2command

Explanation: An error occurred while forward spacingor scanning the tape. There is either a hardwareproblem or a tape error. The tape position is unknown.


User response: Make sure your hardware is workingproperly and you have the correct tape mounted. Then,

VMF1016E • VMF1041E


invoke the command again. If the problem persists,contact your IBM Customer Service Representative ifyou suspect a hardware problem or contact the IBMSupport Center if you suspect a problem with the tapeitself.

VMF1042E Device at virtual address vdev does notexist

Explanation: One of the following occurred:v You invoked SERVICE with a tape address that is not

attached to MAINT.v You invoked INSTFPP without specifying the real

address of the stacked program product tape.

System action: RC = 40 or 100. Command executionstops.

User response: Attach the tape unit to MAINT as vdevor invoke INSTFPP specifying the real address of thetape unit.

VMF1043E A Product Identifier file is missing onthe tape

Explanation: INSTFPP did not find a required file onthe tape. The tape might have been incorrectlypositioned during the installation process.

System action: RC =87. Command execution stops.

User response: Make sure the correct tape is mountedand rewound, and invoke the command again. If theproblem persists, contact the IBM Support Center.

VMF1044R Press <ENTER> to continue or type inany character before pressing <ENTER>to return to the panel:

Explanation: A list of products selected on theDIRECGEN panels has been displayed after pressingthe PF5 EXECUTE key. Execution can continue or thepanel can be redisplayed.

System action: The system waits for a response.

User response: After reviewing the product list foraccuracy, respond to the prompt accordingly.

VMF1045E Error defining temporary work minidiskvdev; return code rc from the CPDEFINE command

Explanation: The CP DEFINE command failed withreturn code rc. If RC = 91, there might be insufficienttemporary disk space available on the system.


User response: Correct the problem and invoke thecommand again. For more information about theDEFINE command, refer to z/VM: CMS Commands andUtilities Reference.

VMF1046I Virtual device vdev1 has been redefinedto vdev2

Explanation: The virtual device at vdev1 has beenmoved to another virtual address, either to avoiddetaching the original virtual device or because aparticular virtual address is needed for the commandto continue.

System action: The virtual address of the device isredefined. Command execution continues.

User response: No user action is required.

VMF1047I Starting to process Program Productprodnum idcode...

Explanation: INSTFPP has started to process prodnumidcode.

System action: INSTFPP processes the productaccording to the options specified.


VMF1049E Product numbers may not be specifiedwith the option option

Explanation: You cannot enter product numbers onthe command line with the option option.


User response: Invoke the command with correctparameters and options.

VMF1050E There were no Program Products foundon the tape

Explanation: The tape is correctly mounted and inVMFPLC2 format, but it is not a stacked programproduct tape for use with INSTFPP.


User response: Mount the correct tape and invoke thecommand again.

VMF1051I Now updating the PROD LEVEL file....

Explanation: INSTFPP updates the PROD LEVEL filewith history information after installing an optionalfeature program product.

System action: The PROD LEVEL file on eitherMAINT's 319 minidisk or the user's 191 minidisk (if theuser does not have access to MAINT's 319 minidisk) isupdated with information about the version, release,modification, and service level of the installed product.Further installation requirements are briefly detailed.The return code is recorded if a severe error occurredduring installation exec processing.



VMF1052R Do you wish to install this product now(yes or no)?

Explanation: INSTFPP displays this prompt if theoptions Install and Prompt are active (specified on thecommand line, from the user data entry panel, or bydefault).

System action: INSTFPP waits for a response.

User response: If you respond YES, the productinstallation exec is called to install the product, and theMemo to Users is printed if the Memo option is ineffect. If you respond NO, INSTFPP bypasses thisproduct, and processing continues with the nextproduct on the tape.

VMF1053R Do you wish to print the Memo to Usersnow (yes or no)?

Explanation: INSTFPP displays this prompt if theoptions NOInstall and Prompt are active (specified onthe command line or from the user data entry panel).

System action: INSTFPP waits for a response.

User response: If you respond YES, the Memo toUsers is printed. Otherwise, processing continues withthe next product on the tape. The product is notinstalled in either case.

VMF1054I Now formatting temporary workdiskvdev as fm...

Explanation: A temporary minidisk is being preparedfor the installation process to use. The formattingprocess can take some time.

System action: The minidisk is formatted. Commandexecution continues.


VMF1056I Installation EXEC failed...

Explanation: An installation exec called by INSTFPPexited with a return code other than 0, 777, or 888.Product installation was not completed.

System action: INSTFPP continues processing with thenext product on the tape.

User response: Once INSTFPP finishes processing,look at the PROD LEVEL file on MAINT's 319 minidiskto determine the return code from the failed installationexec, or look at the console file in the virtual reader.Correct the problem and invoke the command again.

VMF1057I Leaving INSTFPP EXEC...

Explanation: INSTFPP has finished processing.

System action: INSTFPP restores the environment(accessed disks, spool file characteristics) to its previousstate and exits.


VMF1058E A valid real tape address must beentered

Explanation: The tape unit address specified on theINSTFPP data entry panel is not a valid device address.A valid device address consists of three or fourconsecutive hexadecimal digits (0-F).

System action: The cursor moves to the field needingcorrection. The system waits for user input from thedata entry panel.

User response: Obtain the real address of the tapeunit that has the stacked product tape mounted. Thecommand CP QUERY TAPE can be helpful. Type thereal address on the data entry panel and press ENTER.

VMF1059E Reply must be “Y” or “N”

Explanation: Only Y (for YES) and N (for NO) arevalid entries in the field.


User response: Type either Y or N in the appropriatefield and press ENTER.

VMF1060E Option must be 1, 2 or 3

Explanation: Only 1, 2, and 3 are valid processingoptions.


User response: Type a 1, 2, or 3 in the appropriatefield and press ENTER.

VMF1061E Device at real address rdev does notexist

Explanation: The device address you entered on theINSTFPP data entry panel is not the real address of anydevice. You might have entered a virtual addressinstead of a real address.


User response: Obtain the real address of the tapeunit on which the stacked product tape is mounted.The command CP QUERY TAPE can be helpful. Typethe real address on the data entry panel and pressENTER.

VMF1052R • VMF1061E


VMF1062E Device at real address rdev is not a tapeunit

Explanation: The device address you entered on theINSTFPP data entry panel is not the real address of atape unit. You might have entered a virtual addressinstead of a real address.


User response: Obtain the real address of the tapeunit that has the stacked product tape mounted. Thecommand CP QUERY TAPE can be helpful. Enter thereal address on the data entry panel and press ENTER.

VMF1063E Error attaching device rdev as vdev

Explanation: The device at real address rdev could notbe attached as virtual address vdev. Make sure thedevice is not attached to another user and MAINT hasuser privilege class A or B.


(In panel mode), the cursor moves to the field needingcorrection. The system waits for user input from thedata entry panel.

(In line mode), command execution stops.

User response: (In panel mode), try to correct theproblem using the panel command line to enterCP/CMS commands. Continue processing the panel orpress PF3 to QUIT.

(In line mode), correct the problem and invoke thecommand again.

For more information about the CP ATTACHcommand, refer to z/VM: CP Commands and UtilitiesReference.

VMF1064E Error rewinding tape; return code rcfrom the CP REWIND command

Explanation: The device at virtual address 181 mightnot be a tape unit or there might be a hardware tapeunit error.




User response: (In panel mode), try to correct theproblem using the panel command line to enterCP/CMS commands. Continue processing the panel orpress PF3 to QUIT.

(In line mode), correct the problem and invoke thecommand again.

For more information about the CP REWINDcommand, refer to z/VM: CP Commands and UtilitiesReference.

VMF1065E Rewind not performed; device vdev notready

Explanation: The tape unit is attached as vdev, but theCP REWIND command returned the response REWINDNOT PERFORMED. Possible explanations are: the tapeis not mounted properly, the tape is not ready, or thetape is still rewinding from a previous CP REWINDvdev.




User response: Make sure the tape unit is operatingcorrectly and the tape is mounted properly.

(In panel mode), make sure the tape is ready and pressENTER to reprocess the panel or press PF3 to QUIT.

(In line mode), make sure the tape is ready and invokethe command again.

VMF1066E Return code rc from ACCESS vdev mode

Explanation: The access of a minidisk needed forcommand execution failed.


User response: Ensure all required minidisks areattached and invoke the command again. For moreinformation about the ACCESS command, refer toz/VM: CMS Commands and Utilities Reference.

VMF1067E Return code rc from the CMS XEDITcommand

Explanation: A nonzero return code was returnedfrom the XEDIT command.

System action: Execution of the command isterminated. The system status remains the same.

User response: Check the return code explanation onthe XEDIT command. Make sure you are authorized touse the file and that the file is not locked.

VMF1068E Error copying Memo to Users to useridvaddr fm disk: Return code rc from theCMS COPYFILE command

Explanation: The COPYFILE command failed with thespecified return code.


User response: Ensure the disk cited in the message is



linked in read-write mode and has sufficient DASDspace. Enter the command again. For more informationabout the COPYFILE command, refer to z/VM: CMSCommands and Utilities Reference.

VMF1069E Error formatting temporary workminidisk vdev; return code rc from theCMS FORMAT command

Explanation: The FORMAT command failed withreturn code rc.


User response: Correct the problem and enter thecommand again. For more information about theFORMAT command, refer to z/VM: CMS Commands andUtilities Reference.

VMF1070I Creating appid PSUPLAN file at servicelevel servlev for component compname inPPF ppfname.

Explanation: A file called appid PSUPLAN is createdthat contains:

v The messages that VMFPSU issued

v The PTFs that are on the PSU media, but not on thesystem

v The PTFs on the system that would have to bereapplied

v Any PTFs excluded from the list of PTFs to beapplied from the PSU media

v Any parts with local modifications that would beaffected by PTFs from the Product Service Upgrade(PSU) media; these local modifications will have tobe reprocessed. (The PTFs from the PSU that affectthe part are listed.)

Note: A value of ‘????’ under any header in thePSUPLAN file means the data could not be collecteddue to an error. Refer to the error messages issued.

System action: The existing PSUPLAN for thisproduct is overwritten. Command processing continues.

User response: Review the appid PSUPLAN file on theA-disk to help you choose a service receive method:Preapplied-Prebuilt or PTFs Only.

VMF1071I There are num PTFs on theRecommended Service Upgrade forPRODID prodid that are not currentlyapplied.

Explanation: VMFPSU compares the PTFs on theProduct Service Upgrade media to the PTFs currentlyapplied on your system for the PPF and componentbeing processed. The number of PTFs that arepreapplied on the Recommended Service Upgrade andare not currently applied to your system is displayed inthe message.


User response: Review the appid PSUPLAN file on theA-disk to see the PTFs and their APARs.

VMF1072I There are num PTFs currently applied toPRODID prodid that need to bereapplied.

Explanation: VMFPSU compares the PTFs currentlyapplied to the product against the PTFs on the ProductService Upgrade media for the PPF and componentbeing processed. The number of PTFs that are currentlyapplied, but are not on the service upgrade, isdisplayed in the message. These PTFs would have to bereapplied if Preapplied-Prebuilt service is used.


User response: Review the appid PSUPLAN file on theA-disk to see the PTFs and their APARs.

VMF1073I There are num parts with localmodifications that need to bereprocessed.

Explanation: VMFPSU compares the parts that havelocal modifications to the PTFs that will be appliedfrom the Product Service Upgrade media for the PPFand component being processed. The number of partsaffected by PTFs from the service upgrade is displayedin the message.


User response: Review the appid PSUPLAN file on theA-disk to see the parts and their local modificationsthat were affected.

VMF1074I messages


v The Recommended Service Upgrade should not beinstalled because there are excluded PTFs. If any ofthe Program Temporary Fixes (PTFs) to be appliedfrom the Product Service Upgrade (PSU) media areexcluded, you should not proceed with theinstallation. This is because the Preapplied-Prebuiltservice has not excluded them.

v There are no PTFs on the Recommended ServiceUpgrade to be applied for PRODID prodid.Continue with the next product. There were noPTFs on the PSU media that were not alreadyapplied to the specified product. Continuing with thenext product is the recommendation.

System action: RC=0, 1, or 2. Command processingcontinues.

RC Reason

0 Output file ‘appid PSUPLAN A’ is successfullybuilt. Evaluate the contents of the file.

VMF1069E • VMF1074I


1 There are no PTFs to be applied from the PSUmedia for the product specified.

2 The Recommended Service Upgrade (RSU)should not be installed.

User response: Review the appid PSUPLAN file on theA-disk.

VMF1075I There is no service on theRecommended Service Upgrade forPRODID prodid. Continue with the nextproduct.

Explanation: The Product Service Upgrade mediadoes not contain any PTFs for the product beingprocessed.


User response: Continue with the next product to beserviced, if there is one.

VMF1076I There are num PTFs to be excluded fromthe Recommended Service Upgrade.

Explanation: VMFPSU compares the user and IBMexclude lists with the list of PTFs that would beapplied from the Product Service Upgrade media forthe PPF and component being processed. The numberof PTFs from the exclude lists that were found in thelist of PTFs to be applied are displayed in the message.


User response: Review the appid PSUPLAN file on theA-disk to see the excluded PTFs.

VMF1077I Comparing tables appid VVT$PSU$ pvfmand appid updtid updfm

Explanation: VMFPSU uses the two VVT tablesspecified to determine the PTFs to be applied from thePSU media and the PTFs to be reapplied.

Note: This message is issued only if the appid updtidfile is found on the APPLY disks.



VMF1078I Select data file appid $SELECT wascreated or updated to force the rebuildof local modifications.

Explanation: VMFPSU adds all parts that have localmodifications to the specified select data file. All objectsthat contain these parts will automatically be rebuiltwhen the next VMFBLD command is entered.



VMF1090E Conflicting AUX structures for mfn mftand afn aft. AUX file afn aft found [on{vdev|dirid} (fm)] but no correspondingAUX file found for mfn mft

Explanation: The specified file names should have thesame AUX file types. If one of the files has an existingAUX file, but the other file does not, then we have anerror condition.

System action: RC=28. Command processingterminates because there is a missing AUX file fromone of the specified files.

User response: Delete the existing AUX file, or createan AUX file for the file that has one missing.

VMF1091E The current level (mlvl) of mfn mft doesnot match the current level (llvl) of lfn lft

Explanation: VMFBLD uses the version vector tablesto determine the correct level of the CP load list to useduring build processing. Because the CP load list isgenerated from the macro, they both should have thesame service levels. If a mismatch occurs, thenVMFBLD may pick up the wrong CP load list.

System action: RC=100. Command processingterminates because the current level of the files do notmatch.

User response: Enter VMFSIM GETLVL with theHISTORY option for the files identified in the message.This will show the service history and the difference inlevels. Enter the GENCPBLS command again with theLOGMOD option to correct the mismatch.

VMF1200E No {SERVICE | RESTART} record wasfound for product {prodid | restart} intable sysid {SYSSUF | SYSREST}.

Explanation: A record for the specified product couldnot be found in the specified table. If the specified tableis the SYSSUF table, the specified product is notinstalled and therefore cannot be serviced usingVMFSUFIN. If the specified table is the SYSREST table,there is no interrupted VMFSUFIN or SERVICE installto restart for the specified product.

System action: RC = 100. Processing is terminated.

User response: Ensure the correct product was enteredon the VMFSUFIN command. If not, re-enter thecommand correctly. If using the SERVICE command,ensure that a restart is required. If not, enter theSERVICE command without the RESTART operand. Ifan installed product is not in the SYSSUF table, use theVMFSUFTB command to update the table, and thenre-enter the command.


VMF1200I No SERVICE record was found forproduct prodid in table sysid SYSSUF

Explanation: The ALL products operand was specifiedon the VMFSUFIN command, and a record for thespecified product could not be found in the SYSSUFtable. The specified product is not installed, andtherefore, it cannot be serviced using VMFSUFIN.

System action: RC=0. Processing continues with thenext product.

User response: If the specified product is installed,use the VMFSUFTB command to update the SYSSUFtable, and then enter the VMFSUFIN command againusing the PRODID operand instead of the ALLoperand.

VMF1201E A restart record was found for {productprodid|package package_name} in tablesysid SYSREST. The interruptedinvocation of VMFSUFIN must becompleted before a new one for {acommon product|the same package} canbe started.

Explanation: VMFSUFIN cannot install a servicepackage if the SYSREST table contains a checkpoint orlocal modification restart record for one of the productsspecified on the VMFSUFIN command or if theSYSREST table contains any restart record for thespecified package.


User response: Complete the interrupted invocation ofVMFSUFIN by re-entering the VMFSUFIN commandwith the restart option. After the restarted invocationcompletes successfully, re-enter the original command.If you do not want to complete the interruptedinvocation, you must delete the restart record from theVM SYSREST table using the VMFSIM MODIFYcommand, and then re-enter the original command.

VMF1202E The checkpoint restart data for packagepackage_name in table sysid SYSREST isnot valid. The restart {productprodid|step step_name} is not in the{product|step} list for this{package|product}.

Explanation: VMFSUFIN cannot restart theinterrupted invocation due to the invalid data in thecheckpoint restart record.


User response: If possible, correct the checkpointrestart record using the VMFSIM MODIFY command,and re-enter the VMFSUFIN command. Otherwise, theinterrupted invocation of VMFSUFIN cannot becompleted. Contact your IBM Support Center aboutthis problem.

VMF1203E No service envelope name or tapeaddress was specified.

Explanation: The VMFSUFIN command was invokedwithout the RSUENV, CORENV, RSUTAPE orCORTAPE options specified.


User response: Enter the command with the correctoptions.

VMF1204W Unable to copy file fn $PPF from theA-disk to the Software Inventory Disk(D-disk).

Explanation: The VMFSUFIN command could notcopy the specified $PPF file to the Software InventoryDisk.

System action: RC = 4. Processing continues.

User response: Correct the problem, and then copythe specified $PPF file from the A-disk to the SoftwareInventory Disk, and erase it from the A-disk.

VMF1205E messages


v A {RSU|COR Bucket} service envelope name wasspecified on two calls using the same KEY option

v A RSU service envelope name and a COR Bucketservice envelope name were both specified with theKEY option

The VMFSUFIN command was invoked twice using thesame KEY option, and either the RSUENV or theCORENV option was used on both invocations. Or, theVMFSUFIN command was invoked with the KEY,RSUENV and CORENV options on the sameinvocation. The only valid way to use the KEY optionis with two invocations of VMFSUFIN. One with theRSUENV option, one with the CORENV option, andeach with the same KEY data.


User response: Enter the command with the correctoptions, or contact your IBM Support Center about thisproblem.

VMF1206I Service was not {installed|built} forproduct prodid because{{:INSTALL|:BUILD} was not set to YESin the VM SYSSUF table|localmodifications or customized partsneeding rework have been identified for{this|a preceding} product}

Explanation: The automated service and migrationprocedures use the :INSTALL tag from the VM SYSSUFtable to determine whether to install service for aproduct and use the :BUILD tag to determine whether

VMF1200I • VMF1206I


to execute the build steps when installing service ormigrating.

Also, SERVICE and MIGRATE will not execute thebuild steps for a product once a local modification orcustomized part needing rework has been detected forany product.


User response: If prodid is a product that comesdisabled and you have a license for it, make sure thatyou have followed the product's installationinstructions for enablement. Following a product'sinstallation instructions will update the appropriatetags in the VM SYSSUF table and perform the bypassedbuild steps.

In order to complete the build steps after a localmodification or customized part has been identified,you must complete the rework, update the VMSYSLMOD table, and restart the SERVICE or MIGRATEcommand. The VMFUPDAT SYSLMOD command canbe used to update the VM SYSLMOD table.

VMF1207I messages


v There is no service for product prodid onCORrective service envelope fn

v There is no service for product prodid on the{RSU|COR} tape

An RSU envelope is being installed, and there is noservice for this product in the CORrective serviceenvelope received with the RSU. Or, service is beinginstalled from tape, and there is no service for thisproduct on the tape.

System action: If an RSU envelope is being installed,the receive and apply steps for CORrective service forthe product are skipped, and the installation of the RSUcontinues. If tape service is being installed, the productis skip, and service installation continues with the nextproduct.


VMF1208I File fn ft fm was empty and thereforewas not created

Explanation: VMSES/E attempted to create fn ft fm,but the file was empty. If the file previously existed, itwas erased.

For file SUF OUT A, this condition can only occur ifyou have set the :INCLUDE tag to NO in the VMSYSSUF table for all of the products installed on yoursystem.



VMF1209W Service was not installed for productprodid because the RSU contains PTFsthat are excluded

Explanation: An RSU is being installed by theVMFSUFIN EXEC, and one or more of the PTFs on theRSU were found in an exclude list for this product.VMFSUFIN cannot exclude PTFs from an RSU.

System action: RC=4. The RSU installation isterminated for this product, and the installationcontinues for any other products specified.

User response: If the PTFs in the exclude list do notneed to be excluded, remove them from the list, andre-enter the VMFSUFIN command for the product.

VMF1210I The COR Bucket for this RSU, fn DOC,is Text-Only

Explanation: The CORrective service bucket for theRSU being installed is Text-Only, and therefore has noPTFs to install.


User response: Read the documentation in file, fnDOC, and respond accordingly.

VMF1211I A {Checkpoint|Key|Initial|LocalModification} Restart Record has beencreated for package package in theSystem-Level Restart Table

Explanation: A restart record was created for thespecified package. If service is being installed from aservice envelope, package is the file name of theenvelope. If service is being installed from a servicetape, package has the form dfn.dft.prodid, where dfn is thefile name and dft is the file type of the tape descriptorfile, and prodid is the product identifier of the firstproduct on the tape. Explanations for the specificrestart types are as follows:

CheckpointA VMFSUFIN command failed while installingservice, and a checkpoint record was created.This record contains the information needed torestart the interrupted invocation ofVMFSUFIN. The process is restarted byissuing the VMFSUFIN command for one ofthe products specified on the originalcommand and specifying the RESTART option.VMFSUFIN will begin at the service step thatoriginally failed and complete the serviceinstallation using the data stored in the restartrecord. While a checkpoint restart recordexists, VMFSUFIN can only install service fora product listed in that record, or from thepackage listed in that record, by restartingfrom that record.

Key A VMFSUFIN command was issued with the



KEY option, but there was no record in theRestart table with the specified key. So a keyrecord was created. This record contains thedata that was specified on the VMFSUFINcommand. VMFSUFIN does not install thespecified service until a second VMFSUFINcommand is issued with the same key. At thattime, service will be installed using the dataspecified on the command and the data in therestart record. Even though a key restartrecord exists, VMFSUFIN can only installservice from the package listed in that recordif the same key is specified. The ServiceUpdate Facility uses this function to ship anRSU and its COR bucket separately, butinstalls them together.

Initial A VMFSUFIN command failed beforebeginning to install service, and an initialrecord was created. This record contains theinformation needed to restart VMFSUFIN. Theprocess is restarted by issuing the VMFSUFINcommand for one of the products specified onthe original command and specifying theRESTART option. VMFSUFIN will restart fromthe beginning and complete the serviceinstallation using the data stored in the restartrecord. Even though an initial restart recordexists, VMFSUFIN can only install servicefrom the package listed in that record byrestarting from that record.

Local ModificationA VMFSUFIN command did not completebuild processing while installing servicebecause local modifications requiring reworkwere encountered. A local modification recordwas created. This record contains theinformation needed to restart the VMFSUFINcommand and complete the build processingafter the identified local modifications arereworked. The process is restarted by issuingthe VMFSUFIN command for one of theproducts specified on the original commandand specifying the RESTART option.VMFSUFIN will begin at the build step of thefirst product for which a local modificationwas found and complete the build steps forthe service installation using the data stored inthe restart record. While a local modificationrestart record exists, VMFSUFIN can installservice only for a product listed in that record,or from the package listed in that record, byrestarting from that record.

System action: Processing completes.


VMF1212E A restart was requested for a service{tape|envelope}, but the interruptedinvocation of VMFSUFIN was for aservice {envelope|tape}

Explanation: The VMFSUFIN command was invokedwith the RESTART option, and there was a mismatchbetween the type of service indicated on the commandand the type of service indicated in the restart record inthe SYSREST table.


User response: If you wish to restart the interruptedinvocation of VMFSUFIN, enter the command with theappropriate options. If the interrupted invocation wasfor a service tape, you must use the RSUTAPE or theCORTAPE option. If the interrupted invocation was fora service envelope, VMFSUFIN will restart using theservice envelopes specified in the restart record; noneof the RSU or COR options should be used. If you wishto install service from a tape or envelope other than theone that was interrupted, you must first eithercomplete the interrupted invocation of VMFSUFIN ordelete the restart record from the SYSREST table.

VMF1213E A restart was requested for tape packagepackage name, but the interruptedinvocation of VMFSUFIN was for tapepackage package name

Explanation: The VMFSUFIN command was invokedwith the RESTART option and either the RSUTAPE orCORTAPE option was specified. The restart record inthe SYSREST table for the specified product contains apackage name that does not match the specified tape.


User response: If you wish to restart the interruptedinvocation of VMFSUFIN, enter the command with theRSUTAPE or CORTAPE option, and mount the sametape that was originally used. If you wish to installservice from a different tape, you must first eithercomplete the interrupted invocation of VMFSUFIN ordelete the restart record from the SYSREST table.

VMF1214I {RSU|COR} tape number required ontape address

Explanation: The specified tape is needed on thespecified tape device. The tape number correlates to theaddresses specified on the command (for example, ifRSUTAPE 181.182.183 was specified, the tape mountedon 182 would be referred to as RSU tape 2).


User response: If the specified tape is alreadymounted on the specified tape device, no action isrequired. If the tape is not mounted, mount it on thespecified device.


VMF1215E The number of {tapes|envelopes}specified does not match the number of{tapes|envelope} volumes defined bythe descriptor file

Explanation: The number of tapes or envelopesspecified on the SERVICE or VMFSUFIN command isless than or greater than the number of volumesspecified in the descriptor file found on the first tape orenvelope.

System action: RC=24. Processing terminates.

User response: Enter the SERVICE or VMFSUFINcommand again specifying the correct number of tapesor envelopes and mount the correct tapes or specify thecorrect envelopes.

VMF1216E File fn ft fm exists; The previous,interrupted SERVICE command instancemust be completed by invoking theSERVICE command with the RESTARToperand

Explanation: The SERVICE command, as specified,cannot complete the intended operation because one ormore restart records exist in the SERVICE $RESTARTfile (and perhaps also in the VM SYSREST file).


User response: First, complete the interrupted instanceof the SERVICE command by issuing the SERVICEcommand with the RESTART operand included. Afterthat command instance completes successfully, theSERVICE command instance that produced this errormessage can then be run.

VMF1217I There are no products to put intoproduction.

Explanation: The PUT2PROD EXEC was invoked withthe ALL operand and there are no products ready to beput into production. The systemid $PRODS file containsthe products that have been serviced and are ready tobe put into production.


User response: Check to make sure the correctmaintenance user ID was used. The maintenance userID must match the release level of the system.

VMF1218W Product product cannot be put intoproduction because it {has no records inthe systemid $PRODS file | is not foundin the SYSSUF table}.

Explanation: There are no entries in the $PRODS filefor the requested product on the system wherePUT2PROD is being executed, or the requested productis not in the VM SYSSUF table.

System action: RC = 4. Processing completes withwarning.

User response: Check to make sure the correctcomponent was entered on the PUT2PROD command,and that the correct maintenance user ID was used. Themaintenance user ID must match the release level ofthe system.

VMF1219E RACF cannot be put into productionbecause the userid userid is logged on.

Explanation: RACF cannot be put into production ifthe RACF server userid, RACFVM or equivalent, islogged on.

System action: RC = 100. Processing terminates.

User response: Rerun the PUT2PROD EXEC with theRACF test or backup server userid, RACMAINT orequivalent, active.

VMF1220W The RACF database templates must beupdated. Follow the instructions in theRACF Security Server SystemProgrammer's Guide.

Explanation: The IRRTEMP2 TEXT file has beenserviced, which requires the RACF database templatesto be updated. This update cannot be accomplishedwhile RACF is running.


User response: Consult z/VM: RACF Security ServerSystem Programmer's Guide for instructions about usingthe RACFCONV EXEC (and, the IRRMIN00 utility) toupdate the RACF database templates.

VMF1221W messages


v The CP Stand-Alone Dump utility must be rebuilt.Follow the instructions in the z/VM CP Planningand Administration book

v The CP Stand-Alone Program Loader must bewritten to the IPL device. Follow the instructions inthe z/VM System Operation book

For the CP Stand-Alone Dump utility, the utility hasbeen serviced and must be rebuilt. This rebuild willresult in a disabled wait state, and therefore cannot bedone by the SERVICE EXEC.

For the CP Stand-Alone Program Loader, theStand-Alone Loader Creation Utility (SALIPL) has beenserviced. Because of this, the Stand-Alone Loader(SAPL) must be re-written to the IPL device.


User response: To rebuild the Stand-Alone Dumputility, follow the instructions in z/VM: CP Planning and

VMF1215E • VMF1221W


|||||

||||

||||||

Administration. To write the Stand-Alone Loader to theIPL device, follow the instructions in z/VM: SystemOperation.

VMF1222E {Tape on vdev | Envelope fn} is not inVMSES/E format

Explanation: The specified tape or envelope is not aVMSES/E preventive or corrective service tape orenvelope.


User response: Enter the command again with thecorrect service tape or envelope.

VMF1223E The SERVICE console file {could not beidentified | could not be successfullyprocessed | does not contain expectedcontent}. The SERVICE EXEC cannotcontinue.

Explanation: An error was encountered whileprocessing or recovering the program console file. Theconsole file might no longer reside in the virtual reader,or it might not contain the correct content. Because theSERVICE command relies on console-based information(messages and other data) to complete the requestedservice action, it cannot successfully continue or restart.

System action: Command execution stops.

User response: Review accompanying messages formore information. If the reason for this error is notapparent, save any existing problem information andcontact the IBM Support Center for assistance.

VMF1224E The command command cannot run withCMS in full-screen mode

Explanation: Your system is in CMS full-screen mode.The specified command cannot run in this mode.

System action: RC = 100. Command processing stops.

User response: Set full-screen mode OFF and reissuethe command.

VMF1225I Product status:Service Level:levelProduction Level: level

Explanation: The service level and the productionlevels of each system for the specified product aredisplayed.



VMF1226I Product {PTF ptfnum|APAR aparnum (PTFptfnum)} status:status date timestatus datetime

Explanation: The status with date and time is displayedfor the specified PTF or APAR.



VMF1227I {ptfnum|aparnum} is not received orapplied [to product].

Explanation: The specified PTF or APAR has not beenreceived or applied. If a product is specified, only thatproduct was checked.



VMF1228W command failed for ppfname compname.This product will be skipped andprocessing will continue.

Explanation: The specified command failed for one ofthe multiple products that were being processed. Thefailing product will be skipped.


User response: Determine the reason for the failure,make any necessary corrections, and reprocess thefailing product.

VMF1229I No service was found for ppfnamecompname.

Explanation: The VMFBTMAP command did not findany received PFTs for the specified product.



VMF1230W A service bitmap cannot be producedfor compname because it was not foundin the SYSSUF table.

Explanation: A service bitmap can only be producedfor products installed on your VM system.


User response: Check if compname is the validcomponent name of an installed product. If it is not,reenter the VMFBTMAP command with the validcomponent name. If it is, run the VMFSUFTB commandto update the SYSSUF table and reenter theVMFBTMAP command.


VMF1231I Copying files from disk1 to disk2.

Explanation: Files are being copied from the firstspecified disk to the second specified disk.



VMF1232W There is no nucleus to build forprodname

Explanation: The product specified in the SERVICEcommand does not have a nucleus defined in the :BLDsection of its product parameter file (PPF).


User response: Reissue the SERVICE commandspecifying a product that has a nucleus defined in itsPPF.

VMF1233I The following products have been {putinto production | serviced}. [Recycle theappropriate servers.]compname compname ...

Explanation: Products or components that have beenserviced or placed into production are listed. Anyserver virtual machines associated with the products orcomponents that have been placed into productionmust be recycled in order to pick up the new servicelevel of production code.

System action: RC=0. Command processingcompletes.

User response: Recycle the appropriate server virtualmachines.

VMF1234E Variable var cannot be found in the:.DCL section of component compname infn PPF.

Explanation: A variable name found in the :P2Psection of the specified PPF file was not defined in the:DCL section of the PPF.


User response: Add the missing variable to the :DCLsection of the PPF, or correct the variable name in the:P2P section of the PPF.

VMF1235E The command command cannot run withthe system in repair mode

Explanation: Your system is IPLed in repair mode.The specified command cannot run in this mode.


User response: Re-IPL without the REPAIR parameter,and then reissue the command.

VMF1236E An error has prevented {receiving |processing} the console file {to | on} theA-disk. After the cause for this error hasbeen resolved, restart the SERVICEcommand.

Explanation: The SERVICE command encountered anerror while receiving a console spool file from thevirtual reader, or while processing a disk-resident filethat contains console information. Insufficient freeA-disk space is a likely cause for such an error.

System action: Command processing stops.

User response: Consult the messages that precededthis message for details about the error (or errors)encountered. Correct any problems, and then issue theSERVICE RESTART command (qualified with anyspecific operands cited by message VMF2310W, if thismessage was issued).

VMF1237I SERVICE RESTART has successfullyprocessed the SERVICE console file.Prior messages that cite consoleprocessing errors can be ignored.

Explanation: The SERVICE command has recoveredfrom a previous error that occurred while processingthe program console file. The console file has beensuccessfully received, or recovered from a saved(perhaps temporary) disk-resident file.



VMF1238E The command command cannot run on asystem that is a member of an SSIcluster.

Explanation: Your system is a member of an SSIcluster. The specified command cannot run on thissystem.


User response: Reissue the command on a system thatis not a member of an SSI cluster.

VMF1239I messages


v CP was serviced. Shutdown and re-IPL the systemto use the new service.

v CMS was serviced. Re-IPL CMS in all virtualmachines running CMS to use the new service.

The CP component or the CMS component (or both, ifboth variations of this message were received) wasserviced, and that service has been placed intoproduction. For the CP component, the system must beshutdown and re-IPLed to begin using the new servicelevel of production code. For the CMS component, all



virtual machines running CMS must re-IPL CMS tobegin using the new service level of production code.

System action: Command processing completes.

User response: For the CP component, shutdown andre-IPL the system. For the CMS component, re-IPL CMSin all virtual machines running CMS either by 1)invoking the IPL CMS command to IPL the CMS NSS;or 2) invoking the IPL 190 command to IPL CMS fromthe CMS system disk; or 3) logging off and loggingback on the virtual machine.

Note: If both CP and CMS were serviced, taking actionfor only the CP component is sufficient, becauseshutting down and re-IPLing the system will cause allCMS users to be recycled.

VMF1240E command cannot be used by user IDuserID on system sysname because theacquired Software Inventory Disk doesnot match the z/VM release (vrm) of thissystem

Explanation: The user ID listed in the message hasinvoked the named command on the listed z/VMsystem. This command cannot be used for its intendedpurpose on this system, because the z/VM release ofthe system differs from that of the Software Inventory(disks and SFS directories) associated with the givenuser ID.


User response: Log off of the current user ID and logon with the maintenance user ID that is appropriate forthe subject system. Run the named command whilelogged on as this maintenance user ID.

VMF1241E Segment segname cannot be builtbecause it is in use by these user IDs:userid_list[The segment is also in use by CPsystem event and sample monitoring]

Explanation: The indicated monitor saved segment isactively being used by one or more user IDs (listed inthe message). Because this segment is in active use, itcannot be built at this time.

Use of the segment by the CP system (listed as user ID"SYSTEM") is noted by additional message text, whenappropriate.


User response: The monitor saved segment needs tobe rebuilt only when the definition for it has beenaltered (such as to increase the segment size). BecausePUT2PROD has been invoked specifically to build justthis segment, it is likely that PUT2PROD was invokedto account for changes to the segment definition.

Take appropriate action for each listed user ID to

discontinue its use of the named segment. Such actionmight require logging off the subject virtual machine,or instead, quiescing the services that it provides. Whennecessary, CP system event or sample monitoring canbe stopped by use of the CP MONITOR STOPcommand.

If the subject segment is in use by the CP system (listedas user ID "SYSTEM") for event or sample monitoring,this activity also must be stopped before the segmentcan be built.

After the segment has been successfully built, takeappropriate action to resume its use by the listed userIDs.

For more information about the monitor segment andits use, see z/VM: Performance Toolkit Guide and z/VM:Performance.

VMF1241W Segment segname cannot be builtbecause it is in use by these user IDs:userid_list[The segment is also in use by CPsystem event and sample monitoring]

Explanation: The indicated monitor saved segment isactively being used by one or more user IDs (listed inthe message). Because this segment is in active use, itcannot be built at this time.

Use of the segment by the CP system (listed as user ID"SYSTEM") is noted by additional message text, whenappropriate.

System action: RC=4. Command processing continues.

User response: The monitor saved segment needs tobe rebuilt only when the definition for it has beenaltered (such as to increase the segment size). However,when PUT2PROD is used to build ALL segments, orthe monitor segment is named along with othersegments that are to be built, an attempt will be madeto build the monitor segment. If no definition changeshave been made with respect to the monitor segment,this warning condition likely can be dismissed.

If monitor segment definition changes have been made,then take appropriate action for each listed user ID todiscontinue its use of the named segment. Such actionmight require logging off the subject virtual machine,or instead, quiescing the services that it provides. Whennecessary, CP system event or sample monitoring canbe stopped by use of the CP MONITOR STOPcommand.

If the subject segment is in use by the CP system (listedas user ID "SYSTEM") for event or sample monitoring,this activity also must be stopped before the segmentcan be built.

After the segment has been successfully built, takeappropriate action to resume its use by the listed userIDs.

For more information about the monitor segment and



its use, see z/VM: Performance Toolkit Guide and z/VM:Performance.

VMF1242I File fn ft fm exists; Content is:

Explanation: The content of the indicated file isproduced after this message, to aid with any diagnosticefforts.



VMF1300E No local AUX entry was found in fnCNTRL fm

Explanation: The specified control file does notcontain a local level, and therefore a local modificationcannot be created for the component that uses thiscontrol file.



VMF1301R messages


v Local modification modid is being created for{replacement | update} part fn ft.

Enter (0) to quit; (1) to continue [(2) to create adummy or unchanged part].

If you choose to continue, you will be put into anXEDIT session. Make your changes and then enterFILE.

v Local modification modid is being reworked for{replacement | update} part fn ft, and there is noIBM service level or lower VVT level for the part.

Enter (0) to quit; (1) to continue.

If you choose to continue, you will be put into anXEDIT session. Make your changes and then enterFILE.

v Local modification modid is being reworked forreplacement part fn ft, and there is {IBM service forthe part | no IBM service level for the part, butthere is a levelid level}.


If you choose to continue, you will be put into anXEDIT session.

The top screen will be the local modification torework. The bottom screen will be the {IBM service| levelid level} part fn ft2. Compare the levels anddetermine how to include any {service | lowerlevel} changes in the local modification.

Make any necessary changes to the localmodification in the top screen, and then enter FILEfor each screen.

v Local modification modid is being reworked forupdate part fn ft, and there is {IBM service for thepart | no IBM service level for the part, but there isa levelid level}.


If you choose to continue, you will be put into asplit screen XEDIT session.

The top screen will be the part with the localmodification update applied. The bottom screenwill be the {IBM service | levelid level} update fn ft2only. Make sure that the logic of the localmodification is compatible with the {service |lower level update}.


v Local modification modid is being reworked forupdate part fn ft, but the local modification updatewill no longer apply, probably due to sequenceerrors.


If you choose to continue, you will be put into asplit screen XEDIT session.

The top screen will be the part without the localmodification update applied. The bottom screenwill be the local update only. Recreate the localmodification in the top screen by moving codefrom the update in the bottom screen to the topscreen in such away to make it compatible.


v Local modification modid for {replacement | update}part fn ft will be {created from | replaced by} partinfn inft.


A local modification is being created or reworked foran update maintained part or for a replacementmaintained part. This message is asking if you want tocontinue processing the local modification.

System action: RC=0 or 99.

User response: Enter 0, 1, or 2 as follows:

0 If you want to halt LOCALMOD processing,enter 0. Processing stops with a return code of99 and nothing is created or changed.

1 If you want to create or rework localmodification, fn ft2, enter 1. If you haveprovided the local modification in file infn inft,it is used to create or replace fn ft2. If youhave not provided infn inft, you are put intoan XEDIT session to create or rework the localmodification. A split screen XEDIT sessionmay be provided to assist you with reworkingthe local modification. Make your changes and

VMF1242I • VMF1301R


||

|||

|

|

enter FILE for each XEDIT session provided. Ifa split screen is displayed, make changes inthe top screen only.

2 If you want to create a dummy update or anunchanged replacement part, enter 2.

VMF1302E LOCALMOD processing terminated dueto a QUIT response

Explanation: The user either responded QUIT to aLOCALMOD message or QUIT out of the LOCALMODXEDIT session.



VMF1303R While creating or reworking a localmodification for component part fn ft, theLocalmod Restart file indicated that partfn ft2 was saved from a previousunsuccessful invocation of theLOCALMOD command. [The savedpart, however, could not be found].Enter (0) to quit; (1) to delete the restartrecord and continue[; (2) to continueusing the saved part].

Explanation: A local modification is being created orreworked, but a restart record was found for the part.This message asks if you want to restart with the localmodification that was found or continue as specified onthe LOCALMOD command. If the part was not found,you cannot restart.




1 If you want to delete the saved localmodification for the specified part andcontinue processing your LOCALMODcommand, enter 1.

2 If you want to restart the creating orreworking of the saved local modification,enter 2.

VMF1304R The REXX compiler EXEC, fn, was notfound. You may quit, continue withoutcompiling the part, or supply the filename of the compiler EXEC if it is notfn. Enter (0) to quit; (1) to continuewithout compiling; (fn) to supply thefile name of the compiler exec.

Explanation: A local modification to a compiled REXXpart is being created, but the REXX compiler EXEC wasnot found. This message asks if you want a

non-compiled REXX part to be created in place of thecompiled part, of if you want to use a differentcompiler EXEC.


User response: Enter 0, 1, or fn as follows:


1 If you want to create a non-compiled REXXpart to replace the compiled one, enter 1.

fn If you want to use a different REXX compilerEXEC, enter the file name of the EXEC.

VMF1305E Part type pft is not supported by theLOCALMOD command [for productcompname].

Explanation: A local modification cannot be createdby the LOCALMOD command for a part with thespecified file type. If the product is specified, thisrestriction does not apply to all products.


User response: Local modifications for this part canonly be created using manual procedures.

VMF1306E Part fn ft2 has no local modification torework.

Explanation: You entered the REWORK option on theLOCALMOD command, but the specified part has nolocal modifications.



VMF1307E Modid modid1 was specified, but modidmodid2 is the highest modid for part fnft. Only the highest local modificationfor a part can be reworked.

Explanation: You entered the REWORK and MODIDoptions on the LOCALMOD command, but thespecified modid is not the highest local modification forthe specified part. The LOCALMOD command canonly rework the highest local modification for a part.



VMF1308E A local modification cannot be createdfor part fn ft at VVT level levelid1because a local modification alreadyexists at higher VVT level levelid2.

Explanation: You entered the VVTFT option on theLOCALMOD command, but the specified part alreadyhas a local modification in a version vector table that is



at a higher level than the specified version vector. Alocal modification can only be created by a VVT levelat or above all existing local modifications.



VMF1309I Your changes to the local modificationfn ft have been saved and a restartrecord has been created.

Explanation: The LOCALMOD command did notcomplete successfully, and any changes that you mayhave entered have not been applied but have beensaved. If you reenter the LOCALMOD command withthe same part, you will be given the option to restartwith your saved changes.


User response: To restart with your saved changed,reenter the LOCALMOD command and respondappropriately to the VMF1303R message.

VMF1310I The status of local modification modidfor prodid part pfn pft in version vectorvvtft has been updated to REWORKEDin the SYSLMOD table.

Explanation: The LOCALMOD command has beensuccessfully used to rework the specified localmodification, and the SYSLMOD table has beenupdated to reflect this.



VMF1311R From the following list choose a releasefrom which to migrate:release Enter (0) toquit; (release) to continue.

Explanation: You did not specify the from-release onthe MIGRATE command. This message lists the validrelease(s) and asks you to choose one.


User response: Enter 0 or release as follows:

0 If you want to halt MIGRATE processing,enter 0. Processing stops with a return code of99 and nothing is migrated.

release If you want to continue MIGRATE, enterrelease.

VMF1312E MIGRATE processing terminated due toa QUIT response.

Explanation: The user responded QUIT to aMIGRATE message.

System action: RC= 99. Command processing stops.


VMF1313E A MIGRATE $RESTART file was foundfor release vrm. {This is not a validrelease from which to migrate | Releasevrm was specified on the MIGRATEcommand}.

Explanation: A MIGRATE restart file was found thatwas for either an invalid release or a release other thanthe one specified on the MIGRATE command.


User response: If you specified the wrong release onthe MIGRATE command, re-issue the command withthe release found in the restart file. Otherwise, contactthe IBM Support Center.

VMF1314E File VM MIGLvrm was not found. TheMIGLINK command has not been runsuccessfully for release vrm.

Explanation: The specified file which is produced bythe MIGLINK command was not found. Either theMIGLINK command was not successfully run or thewrong release was specified on the MIGRATEcommand.


User response: Issue the MIGLINK command on thefirst-level system, and re-issue the MIGRATE commandwith the correct release on the second-level system. Ifthe problem persists, contact the IBM Support Center.

VMF1315E The VM MIGLvrm table does notcontain {dcllabel disk | PPF} data forproduct prodid.

Explanation: The specified file which is produced bythe MIGLINK command does not contain the specifieddata.


User response: Re-issue the MIGLINK command onthe first-level system, and re-issue the MIGRATEcommand on the second-level system. If the problempersists, contact the IBM Support Center.

VMF1316I Product prodid (compname) will not bemigrated because it {has a status ofDISABLED|is not installed} on the oldsystem

Explanation: A product can only be migrated if it isinstalled and it is enabled on the old system. Since thisproduct was not specified on the MIGRATE command,this message is informational only.

System action: RC= 0. Command processingcontinues.




VMF1316W Product prodid (compname) will not bemigrated because it {has a status ofDISABLED|is not installed} on the oldsystem

Explanation: The product specified on the MIGRATEcommand was either not installed or disabled on theold system.


User response: Re-issue the MIGRATE commandspecifying a product that is installed and enabled.

VMF1317W messages


v Disk dcllabel could not be migrated for productprodid (compname) because it was not found byMIGLINK in release vrm.

v Part fn ft could not be migrated for product prodid(compname) because disk dcllabel was not found byMIGLINK in release vrm.

The specified disk is not defined in the PPF in thespecified release, and the MIGLINK command couldnot determine the equivalent disk.


User response: The specified disk or part must bemigrated manually.

VMF1318E messages


v MIGRATE cannot continue. A SERVICE restartrecord for productprodid was found, which couldnot have been created by MIGRATE.

v MIGRATE cannot continue. A SERVICE restartrecord for product prodid was found, but MIGRATEis attempting to restart with product prodid2.

v MIGRATE cannot continue. A SERVICE restartrecord was found, but the first product, prodid, to beprocessed by MIGRATE is not restarting at theBUILD step.

The MIGRATE command cannot successfully run theSERVICE command because of the SERVICE restart filethat was found. There are three possible scenarios:

v The SERVICE restart record is a type that could nothave been created by the MIGRATE commandcalling the SERVICE command. The SERVICEcommand has been unsuccessfully invoked prior tothis invocation of the MIGRATE command.

v The first product to be processed by the MIGRATEcommand does not match the product to be restarted

by the SERVICE command. This mismatch wouldcause the SERVICE command to fail when called byMIGRATE.

v The first product to be processed by the MIGRATEcommand is either not restarting or is restarting at astep other than BUILD. In either case, the BUILDstep would call the SERVICE command without theRESTART operand, and the SERVICE commandwould fail due to the RESTART file.


User response: For the first scenario, you mustcomplete the unsuccessful invocation of the SERVICEcommand before running MIGRATE. See the SERVICE$MSGLOG for information on the failure and how torestart SERVICE.

For the other two scenarios, you are probably trying torun MIGRATE for a product other than the one thatfailed on your previous invocation of MIGRATE. If thisis the case, you must correct the problems found by theprevious invocation and re-issue the MIGRATEcommand with the operands previously used. See theMIGRATE $MSGLOG for this information. Thesescenarios could also be caused by an unsuccessfulinvocation of the SERVICE command. If this is the caseyou must, like for the first scenario, complete theunsuccessful invocation.

If the problem persists, contact the IBM Support Center.

VMF1319I messages


v Disk dcllabel migrated, old {owner address|dirname}migrated to new {owner address|dirname}

v Part fn ft migrated, fn ft on {old|new} {owneraddress|dirname} copied to fn ft on new {owneraddress|dirname} [because the part was notcustomized on the old system]

v PTF ptfnum migrated

v Local modification modid for part fn ft migrated

The specified migration was successful.



VMF1319W Disk dcllabel migrated, old {owneraddress|dirname} migrated to new {owneraddress|dirname}.

Explanation: The specified migration was successful,but the disk definitions for the two releases were notidentical. This is not an error.


User response: There is no action required unless you

VMF1316W • VMF1319W


are using a PPF override that contains DCL diskdefinition changes for this product. There is a postmigration step that handles PPF override migration.

VMF1320W Migrate restart file, MIGRATE$RESTART A, has been updated due to{errors | customized parts}. {Correct theerrors | Rework the customized parts},and restart MIGRATE by reissuing thesame command. DO NOT issue theSERVICE RESTART command.

Explanation: The MIGRATE command did notcomplete successfully due to errors or customizedparts. The restart file was updated to enable therestarting of the MIGRATE command.


User response: Based on the preceding messages,either correct the errors or rework the customizedparts, and then reissue the MIGRATE command. Donot restart the SERVICE command.

VMF1321E Product prodid (compname) in this releasecannot be migrated from release vrm.

Explanation: The product specified cannot bemigrated from the release specified.

System action: RC= 100. Processing is terminated.

User response: Re-issue the MIGRATE commandspecifying a product that can be migrated form thespecified release.

VMF1322E MIGRATE can only run with thefollowing userids logged on: userid list.The following other userids were foundlogged on: userid list.

Explanation: User IDs that cannot be logged on whenthe MIGRATE command is issued were found.

System action: RC=100. Processing is terminated.

User response: Re-IPL with NOAUTOLOG and restartMIGRATE.

VMF1323W Compname part fn ft could not bemigrated to the dcllabel ({owneraddress|dirname}) disk. It should bemigrated manually.

Explanation: The specified part could not be migrated.

System action: RC= 4. Processing continues.

User response: Migrate the part to your new systemmanually.

VMF1324R You entered input as the component tomigrate, but this appears to be therelease from which you wish to migrate.Enter (0) to quit; (1) to continuewith input as the component name;(compname) to specify thecomponent name, ALL, or BASE,and use input as the from-release.

Explanation: You entered the MIGRATE commandwith a valid from-release as the first and only operand.This operand should be the component you wish tomigrate. You probably omitted the first operand andonly entered the second. This message asks if you wantto continue using this operand as the component tomigrate, or if you want to specify a component nameand use the operand as the from-release.

System action: RC=0 or 99

User response: Enter 0, 1, or compname as follows:.

0 If you want to halt MIGRATE processing,enter 0. Processing stops with a return code of99 and nothing is migrated.

1 If you want to continue migration processingwith the operand entered on the command asthe component, enter 1.

compnameIf you want to specify a different first operandand use the operand entered on the commandas the from-release, enter a component name,ALL, or BASE.

VMF1325E Modid modid is already in use byproduct compname

Explanation: The specified product contains a file witha file type ending in the specified modificationidentifier. The modification identifier might already bein use.


User response: Reissue the LOCALMOD commandwith a different modification identifier.

VMF1326E The specified modid modid does notmatch the restart modid modid2

Explanation: The LOCALMOD command was issuedwith a modification identifier that does not match themodification identifier found in the restart file.


User response: Reissue the LOCALMOD commandwith the correct, previously entered modificationidentifier.


VMF1327E Command command failed whileoperating on target

Explanation: The specified command failed whileoperating on the specified target.


User response: Review the console log and anyVMSES/E $MSGLOG files for related error messages,and then see the appropriate documentation for thefailing command.

Correct the problem and issue the command again.

VMF1400R Mount next tape and press <ENTER> tocontinue or type in any character beforepressing <ENTER> to quit:

Explanation: The program waits for the user to mountthe next tape required and press <ENTER> when thetape is ready. If the user enters any character then theprogram exits.

System action: The system waits for a response.

User response: Press <ENTER> after the next tape ismounted if you wish to continue or enter any characterto exit.

VMF1413E Invalid format recfm lrecl for file fn ft fm

Explanation: The indicated file does not have thecorrect format. Most likely the directory file specified isnot of RECFM = F and LRECL = 80.

This error may occur if the user has modified the file orthere are multiple copies of the file on the system.



User response: Ensure that the correct file is beingspecified to the command. If the indicated file has beenmodified then ensure that the file is corrected toconform to the proper format. If the files have not beenmodified, report the problem to the IBM SupportCenter.

VMF1419E Unable to LINK to {userid vdev|userid1vdev1} [since userid2 has disk linked R/Was vdev2]

Explanation: The program cannot LINK to theindicated disk, either due to some error or becausesomeone else has the disk accessed R/W.


User response: Check the $VMFINS $MSGLOG filefor more information on the problem. You may have torelease and detach the minidisk from another user.

Ensure the directory being modified by VMFRMT is thesame as the directory that is online on the system,either VMUSERS or as specified to VMFRMT.

If the $VMFINS $MSGLOG file has message 1412indicating the LINK command returned with returncode=15 (maximum number of password attempts wasexceeded), the user must first logoff and log back onbefore continuing.

VMF1420E R/W version of fn ft fm not found

Explanation: The indicated file cannot be found as aR/W file.



User response: Check the $VMFINS $MSGLOG filefor more information on the problem. You may have tore-access the disk in R/W mode or re-link and re-accessthe disk in R/W mode.

VMF1421E Unable to CREATE an EXCLUSIVE R/WLOCK for file fn ft fm [because userid hasfile locked with a locktype lock]

Explanation: An EXCLUSIVE R/W LOCK cannot becreated for the indicated file because of an error orbecause someone else has some type of lock (locktype)on the file that is in an SFS directory.


User response: See $VMFINS $MSGLOG file for moreinformation on the problem. You may have to getanother user to delete the LOCK that is on theindicated file or wait until the user is finished with thefile.

VMF1431I userid minidisk vdev moved - {all filescopied|contents not moved since theminidisk is not in CMS format|no filesto copy}

Explanation: The indicated user's minidisk wasmoved and all files were copied to the new disk, nofiles existed to copy, or no files were copied because theoriginal disk was not in CMS format. The disk may bea DOS formatted disk or a RECOMP area on disk.



VMF1443R Return code rc returned accessing useridaddr as fm The probable cause is anunformatted disk Enter 0 to exit or 1 toformat the disk

VMF1327E • VMF1443R


Explanation: The process requires a response from theuser.

System action: Command processing stops withRC=500 if your response is 0. Otherwise, the specifieddisk is formatted and processing continues.

User response: Enter zero (0) to quit or one (1) toformat the disk and let the processing continue.

VMF1444I Directory fn ft fm contains restrictedpasswords The online directory willhave thepasswords changed to NOLOGwhen it is placed on-line

Explanation: Users with restricted passwords willhave their passwords changed to NOLOG.


User response: You should change the final directory'spasswords for the users with restricted user IDs andput this directory online to avoid locking out user IDs.

VMF1484E filepool is not a valid filepool; RC = rc

Explanation: This file pool ID does not exist in theshared file system.

System action: RC = 100. Command processing stopsbecause of the external error.

User response: Determine the correct file pool ID andmodify the control file to reflect the correction, thenretry. If the problem continues, contact the IBM SupportCenter.

VMF1485E You are not an administrator for filepoolfilepoolid. Administrative authority isrequired to perform this process

Explanation: You must be granted administrativeprivileges from a Shared File System administratoruserid for this file pool before resource managementfunctions can be performed on the file pool.


Command processing stops due to the external error.

User response: Issue the command from a SFSadministrator userid or have administrative privilegesgranted to your userid for this file pool before retrying.

VMF1486E The variations of this message areexplained below.

Explanation:

v Filepool filepool is not operational; program cannotcontinue. The command you are running requiresthat the filepool cited in the message be in operation.However, this file pool is not running or is notavailable.

v Filepool filepool is not operational; continuing asdirected by option setting. The command in userequires the file pool cited in the message to beoperational. This file pool is not running or is notavailable, which normally prevents further commandprocessing. However, the option cited in the message(and, specified in a VMFINS DEFAULTS file) hasbeen used as an override and has caused the systemto continue operations despite this problem.

System action: For the first variation, RC = 100.Command processing stops.

For the second variation, command processingcontinues.

User response: For the first variation, determine whythe file pool server for the indicated file pool is notrunning. After correcting any problems, restart theapplicable server in multiple-user mode (using theFILESERV START command). If the file pool server isrunning, ensure that the PPF variable that identifies thesubject file pool in the VMSESE PROFILE is correct.

For the second variation, Upon completion of thecurrent command or task, confirm that all results arecorrect. If any command errors resulted due to a filepool not being available, ensure the appropriate filepool sever is running before trying the command again.In addition, ensure that the setting established by thesubject command option is such that file pool operationchecking and error control are performed by default.

VMF1487I userid is not authorized to connect to filepool filepool. Access todata in file pool filepool is presumed tonot be required.

Explanation: The command you are running hasattempted to connect to the file pool indicated in themessage. However, the user ID issuing the commandlacks the necessary authorization to connect to this filepool.


User response: In most instances, no action isrequired. It is presumed that data in the given file poolis not required for the successful use of this command.If access to this data is necessary, the user ID issuingthe command must be enrolled in this file pool, withappropriate directory and file authorizations thengranted.

VMF1488I The option option has been set tooverride filepool operation checks

Explanation: The option cited in the message (andspecified in a VMFINS DEFAULTS file) has been usedto alter how system-related file pool operation checkingis performed. As a result, processing performed by thecommand in use has also been altered.




User response: Upon completion of the currentcommand or task, determine whether continued use ofthe indicated option and setting is necessary. If nolonger required, alter the setting for this option suchthat file pool operation checking and error control arerestored to the default setting.

VMF1490E Content error detected for file: fileid

Explanation: One or more statement or definitionerrors have been identified within the file cited in themessage.


User response: Refer to accompanying messages fordetails about the specific error or errors that have beenidentified. After making the appropriate corrections inthe subject file, reissue the command.


VMF1507E - VMF3064I

VMF1507E The DASD volume volid, address address,containing the CP directory space is notlinked in R/W mode

Explanation: The DASD volume containing the CPdirectory space (DRCT) is accessed R/O. The volumelabel and address are obtained from the DIRECTstatement in the CP directory.


User response: Ensure the DASD volume containingthe CP directory space is available in R/W mode beforerunning again. Performing a QUERY LINKS against thedisk CUU will list any other user IDs that have R/Wlinks to the disk.

VMF1808E fn1 is an override in fn2 $PPF. Thisoverride points to fn3 $PPF. The productparameter file fn3 $PPF cannot belocated

Explanation: You are using nested override files, andone of the override files in the override chain cannot befound.


Command processing stops because of the file notfound condition.

User response: Ensure that all the files in the overridechain are product parameter files on one of theaccessed disks.

VMF1810R Enter a component name or zero (0) toquit

Explanation: The procedure needs a component nameto carry out its function.


If you enter 0, command processing stops with a returncode of 500. If you enter a component name, commandprocessing continues.

User response: Enter a component name listed in themessage preceding this message, or enter quit.

VMF1817E The updtid update ID is not in the fn ftfile

Explanation: The specified update identifier must bean update file or AUX file listed in the specified controlfile.


Command processing stops because of thefile-not-found condition.

User response: Specify a valid update identifier andreissue the command.

VMF1821E There are not enough filemodesavailable to complete the commandcommand. [None of the disks ordirectories will be accessed|Use ofRETAIN caused some modes to beskipped to maintain access order]

Explanation: Access to the required minidisk ordirectory failed because no file modes were available.

System action: RC=12. Command processing stopsbecause of the internal error.

User response: Reduce the number of minidisks ordirectories listed as required in the :MDA section of theproduct parameter file. Adjust the RETAIN modeseither in the product parameter file or on the options tothe VMFSETUP command.

VMF1822E No file mode within the range range isavailable for use

Explanation: An unused CMS file mode, within therange cited in the message, is required for commandprocessing. However, no file mode within this range isavailable.


User response: Review your current use of file accessmodes and release at least one file mode from withinthe indicated range for use by the given command.Then, try the command again.

VMF1823E File mode filemode is not available foruse

Explanation: The CMS file mode cited in the messageis required for command processing. However, this filemode already is in use.


User response: Review your current use of theindicated file access mode. If the accessed resource(minidisk or SFS directory) is not required in order touse the given command, release that resource.Alternately, access the resource using a different filemode. Then, try the command again.

VMF1824E A file mode that {precedes | follows}file mode filemode (within the set list1)cannot be acquired (file modes list2 areexempt from use)

Explanation: A CMS file mode cited in the message isrequired for command processing. The set of file modesin list1 is comprised of in-use file modes, while those inlist2 are restricted from consideration for use(regardless of whether these file modes currently are inuse).




User response: The conditions that resulted in thismessage being issued are not expected. Save anyexisting problem information and contact the IBMSupport Center for assistance.

VMF1832W Text deck fn ft is included in thebuildlist_name build list currently beingprocessed but the text deck cannot befound

Explanation: A text deck listed in the build list to beincluded in the build cannot be found on an accessedminidisk or directory.

System action: RC=28. Command processingcontinues.

User response: Verify the correct minidisks anddirectories are listed in the component section of theproduct parameter file. Ensure this deck wasintentionally removed from the access order.

VMF1836E This program requires disk_namevirtual_device to be accessed [as R/W][because it is a target of {SoftwareInventory files|tape files|build lists}|sothat user directory fn ft can be modified]

Explanation: The specified target must be accessed asindicated in the message. The target may be defined asa minidisk, SFS directory, or file mode.

System action: RC=36. Command processing stopsbecause the target is not available.

User response: Access the specified target as indicatedand rerun the command. If using VMFSETUP (eitherdirectly or by using the SETUP option), make sure thetarget is specified properly in the product parameterfile.

VMF1838E File mode fm is not accessed [with statusstatus]

Explanation: An expected minidisk or SFS directory isnot accessed using the CMS file mode indicated in themessage. Or, the minidisk or SFS directory accessedusing the indicated file mode does not have theread-only (R/O) or read-write (R/W) status required bythe command in use.


User response: Ensure the appropriate minidisk orSFS directory is accessed using the indicated file mode.If specific read-only or read/write status is required,ensure this status has been established before thesubject command is used again.

VMF1850E Build list bldlist is flagged to bebypassed in the :BLD section of productparameter file fn PPF (compnamecompname)

Explanation: The specified record in the productparameter file contained a bypass flag (a ‘-’ appendedto the front of it). The build list was not processed.


User response: To process the build list or productprocessing exit, remove the bypass flag and reissue thecommand.

VMF1851E messages


v (n of m) Cannot process fn ft because requisitebldlist object have not been satisfied

v (n of m) Cannot process fn ft because objectdeletions have not been satisfied

v (n of m) Cannot process fn ft because part handlerparthandler cannot be found

v (n of m) parthandler completed with return code rc.Some objects were not built

Objects in the given build list were not built for thespecified reason.


Command processing continues bypassing the failingsub-function.

User response: Correct the problem that is preventingthe object(s) from being built, and reissue thecommand. An object cannot be built unless all of itsbuild requisites have been built and a part handler canbe called to build it.

VMF1851I messages


v (n of m) parthandler processing tapefile

v (n of m) parthandler processing fn ft fm, target isstring {vdev|dirid} (mode)

v Executing the product processing exit fn

v (n of m) Build list fn1 has a build requisite forobject object in build list fn2, but fn2 has beenflagged to be bypassed

v Processing user exit fn to set up

v Processing user exit fn to clean up

v Processing product exec fn

v Reading build lists

v Cannot process fn ft because it is flagged to bebypassed

v (n of m) parthandler completed with return code rc

VMF1832W • VMF1851I


These messages notify you when major steps in theprocedure are being performed, or of relevantinformation related to the procedure.



VMF1852I Volume n of m of {COR|INS|PUT}{TAPE|ENVELOPE} tapenum [created onday month year]

Explanation: This message identifies the tape orenvelope being processed.



VMF1853W Serviced part fn ft was not found in anybuild list. A MANUAL buildrequirement will be created.

Explanation: The VMFBLD STATUS functionencountered a serviced part that could not be found inany build list. This implies that the part must beprocessed using manual procedures. Therefore aMANUAL build requirement is established by creatinga record in the SRVBLDS table. A part may also beassigned a status of MANUAL due to one of thefollowing error situations.

v A PTF or a local modification introduced a new partwithout adding the part to a build list.

v A PTF or a local modification inadvertentlyintroduced a new part by not matching the file nameand file type abbreviation data on the:PARTID tag inthe build list.

v A local modification incorrectly added a select data($SELECT) file entry for the part.

System action: RC=4 Processing continues.

User response: Do the manual processing and use theVMFUPDAT command or the VMFSIM MODIFYcommand to update the status in the SRVBLDS table toBUILT. If the MANUAL status was caused by an error,correct the error if it was caused by a localmodification. If the error was caused by a PTF, reportthe error to the IBM Support Center.

VMF1860E compname is an invalid component namefor the product parameter file fn $PPF

Explanation: The base component name given was notfound on the :COMPLST tag in the file fn $PPF.



User response: Verify that the file name of the productparameter file is correct for the component namespecified.

VMF1860I compname is an invalid component namefor the product parameter file fn $PPF

Explanation: The base component name given was notfound on the :COMPLST tag in the file fn $PPF.

System action: RC=0. Command processing continuesby issuing a prompt for the correct component name.

User response: When prompted for the componentname, respond by entering one of the componentnames listed by the prompt or enter quit.

VMF1861E The prodid service exec completed withreturn code rc. Some service may havebeen received

Explanation: The prodid is serviced with a productexec (prodid EXEC). The product exec was run andfailed with the specified return code.


User response: Follow the instructions in the product'sservice documentation.

VMF1861I The prodid service exec completed withreturn code rc[. The service may havebeen received previously]

Explanation: The prodid is serviced with a productexec (prodid EXEC). The product exec was run andcompleted with the specified return code.



VMF1861W The prodid service exec completed withreturn code rc. Service has been receivedand a build may be required

Explanation: The prodid is serviced with a productexec (prodid EXEC). The product exec was run andcompleted with the specified return code.


User response: Follow the instructions in the product'sservice documentation.

VMF1863W Service has been received on the S-disk.

Explanation: Files have been loaded to the systemdisk.


Command processing continues.

User response: The system minidisk needs to bere-IPLed, or the CMS segment may need to be resaved.


VMF1867E The build list fn ft fm does not contain avalid loader name

Explanation: Unless specified with the LOADERoption, the loader invoked for the build of thecomponent being processed is determined by the loadercard specified in the build list identified in the :BLD.section of the product parameter file. The build listdoes not contain a loader that is valid.



User response: Check the build list and correct or addthe loader entry and rerun the command. Or, rerun theprocedure by using the LOADER option and a validloader name.

VMF1868W messages


v Auxfile fn ft contains PTF ptfnum but textdeck fn ftcould not be located. Search will continue with thelevel ID from the control file. In determining thefile type of a textdeck using the AUX and control filestructure, an AUXFILE has been found that containsa valid PTF or local tracking number. A textdeck filetype formed with this number and prefix cannot belocated using the current access order. This mayresult in a build being done with a lower leveltextdeck.

v The control file fn CNTRL indicates that part fn2 ft2should exist but it cannot be located. Searching willcontinue at the next level. In determining the filetype of a textdeck using the AUX and control filestructure, the following occurred:

1. An update or AUX file was specified in thecontrol file.

2. The update or AUX file exists on an accesseddisk.

3. A part with a filetype of the prefix concatenatedwith the LEVELID could not be located.

This condition may also exist if the update specifiedin the control file contains a prefix, but the next AUXlevel points to an AUXFILE that does not contain avalid PTF number. In this case, a search is madeusing the LEVELID from the control file, which maycause the message to be issued as described above.

System action: RC=8. In each case, the procedurecontinues to process the control file searching for atextdeck file type.

User response: In each case, investigate the accessorder to determine if the textdeck identified in themessage can be located. If it can be located, either thedisk should be added in the PPF, or the textdeckshould be copied to a disk that is listed in the PPF. If

the deck cannot be located, then the module should bereassembled.

VMF1870S Choose the component to be processedfrom the list below:

Explanation: A procedure has been requested, but acomponent name was not specified. The namesdisplayed are taken from the :COMPLST tag and:OVERLST tags in the product parameter file.

System action: Command processing continues.Message 1810R will follow.


VMF1872W {COR|INS} is not a fully supportedoption for product prodid. The{TAPE|ENVELOPE} has been positionedto the beginning of the product's firstfile

Explanation: The product specified on the VMFRECcommand is not packaged in VMSES/E format andmust be processed using the product's servicedocumentation.



User response: Follow the instructions in the product'sservice documentation to load the product's service.

VMF1889E The fn ft file contains invalid data onthe tag record

Explanation: The syntax of the specified file is invalid.



User response: Correct the syntax of the file and rerunthe procedure.


Explanation:

v The product parameter file fn $PPF is invalid. tag1is missing or out of order. A required record cannotbe found in the product parameter file.

v override is an override in fn1 $PPF. This overridepoints to override tag tag in fn2 $PPF which isalready in the override chain. The use of nestedoverride files is incorrect.

v The product parameter file fn $PPF is invalid. tag isan invalid tag. A tag that is not valid has been foundin the product parameter file.

v The product parameter file fn $PPF is invalid.keyword is an invalid override keyword for tag. A



keyword that is not a valid override keyword for theindicated tag has been found in the productparameter file.

v The product parameter file fn $PPF is invalid.Override control records are not valid for theoverride keyword keyword found on the tag tag. Theoverride control records are not valid for theindicated override keyword found on the tag shown.


User response:

v Check the tag that is mentioned as missing in themessage. It may not begin with a colon (:) or endwith a period (.), and therefore is not considered avalid tag. Or, the tag may be out of order in relationto another tag.

v Check the nesting of override files in your productparameter files.

v Investigate why the tag is considered not valid. Itmay not begin with a colon (:) or end with a period(.), and therefore is not considered a valid tag.

v Investigate why the keyword is considered not valid.For more information about the tag and possibleoverride keywords, refer to z/VM: VMSES/EIntroduction and Reference.

v Investigate why the override control records areconsidered not valid for this tag. For moreinformation about the tag and possible overridekeywords, refer to z/VM: VMSES/E Introduction andReference.

VMF1893E A :COMPLST tag was found in the filefn $PPF which appears to be an overridefile

Explanation: The :COMPLST tag is only valid in abase product parameter file.



User response: Correct the product parameter file andreissue the command.

VMF1895E tag1 tag found {after|before} tag2 tag infn $PPF

Explanation: A tag was not in the proper place in theproduct parameter file.


User response: Correct the product parameter file andenter the command again.

VMF1896E Component missing off overridecomponent tag tag1

Explanation: The component could not be found inthe override file.



VMF1897E {Error reading file fn ft fm|A problemoccurred reading file fn ft while functionfunction was executing}

Explanation: A file required by the procedure cannotbe read.

System action: The procedure exits with RC=100.

User response: Correct the problem with the file andretry the procedure. Possible problems are not enoughstorage or bad file pointers.

For VMFBDMOD, examine the loadlist file and makesure all the load blocks are in the correct format and allthe required tags are present. Examine anyaccompanying error message and refer to the userresponse for that message for further assistance. Correctthe loadlist and enter the VMFBLD command again.

VMF1898E A record cannot be written to file fn ftfm

Explanation: A problem has been encountered addinga record to a file.


User response: Correct the problem with the minidiskor directory and retry the procedure. The minidisk orfile space being full could cause this error.

VMF1901E Missing keyword keyword1 for keyword2option

Explanation: Only one keyword was entered. Youmust enter both keyword1 and keyword2.


User response: Check the command syntax and enterthe command again.

VMF1902E Keywords out of order: keyword2 mustfollow keyword1

Explanation: The second keyword (Keyword2) wasfound before the first keyword (Keyword1). Keyword1must be entered first.


User response: Check the command syntax and enterthe command again.


VMF1905E The access of {vdev|dirid} failed with areturn code of rc.

Explanation: VMFSETUP was not able to perform anaccess that was listed in the product parameter file. Theminidisk or directory may not have been linked orformatted prior to running VMFSETUP.

System action: RC=12. Processing stops because of theinternal error.

User response: Ensure the access was not needed. If iswas needed, make the minidisk or directory accessible,and enter the command again.

VMF1906E Unable to access disk vdev R/O becauseno files were found. Disk vdev is notaccessed

Explanation: A read-only link to the indicated diskhas been specified or requested, but the disk is emptyand therefore cannot be accessed read-only.


Command processing continues, bypassing the failingsub-function.

User response: Subsequent VMSES/E operations mayfail because not all required disks have been accessed.Read/write authority should be obtained to thespecified disk, or ensure that it contains at least oneCMS file.

VMF1906W Unable to access disk vdev R/O becauseno files were found. Disk vdev is {notaccessed | now accessed R/W}

Explanation: A read-only link to the indicated diskhas been specified or requested, but the disk is emptyand therefore cannot be accessed read-only. If theVMFSETUP LINKRR option has been used, the disk isnot accessed, whereas for the VMFSETUP LINK option,the disk is accessed R/W.


Command processing continues, bypassing the failingsub-function.

User response: Subsequent VMSES/E operationsmight fail because all required disks might not havebeen accessed. If the indicated disk is required for otheroperations, ensure that it contains at least one CMS file.

VMF1907I {Assembling|Generating{commands|messages} for} fn

Explanation: ASSEMBLE, HASM, HLASM, GENCMD,or GENMSG is about to be run for the specified file.



VMF1908E Error {assembling|generating{commands|messages} for{ fn. Returncode was rc

Explanation: ASSEMBLE, HASM, HLASM, GENCMD,or GENMSG failed when processing the specified file.

System action: RC=8. Command processing continuesbypassing the failing subfunction.

User response: Investigate why the specifiedcommand failed. Correct the problem and enter thecommand again.

VMF1909I fn ft {created|updated|moved} {on|to}your character-disk

Explanation: This message is issued to alert you of thecreation or modification of the specified file.



VMF1910E No filepool is currently assigned

Explanation: A file pool is not currently assigned.



User response: Check your shared file systemdirectories.

VMF1911E Invalid CSECT name csect-name for ICScard in fn ft

Explanation: The include control section card has aninvalid CSECT name specified.



User response: Correct the ICS card and restart theprocedure.

VMF1912E VER card missing in fn ft

Explanation: A VER card was missing, and the patchcannot be performed.



User response: Add a VER card and restart theprocedure.




Explanation:

v Tag tag is not present in fn ft

v Tag tag data data is not valid in fn ft

v Tag tag data is missing for object obj in fn ft

v Tag tag data data is not valid for object obj in fn ft

v Tag tag data is missing in fn ft

v Data {tag | data} is not valid in fn ft

The syntax of the specified file is not valid.



User response: Correct the syntax and rerun theprocedure.

VMF1935I Object object in the fn ft build list wassuccessfully built

Explanation: This is an information only message toidentify the successful build of an object.


User response: This information is placed in the logfor informational purposes only.

VMF1937I Merge of string started

Explanation: The contents of the specified string ofdisks will be merged or promoted. The merge is basedon the following algorithm: Starting from the mostaccepted pair of disks, the contents of the less acceptedone of the pair are copied to the more accepted oneusing COPYFILE with the OLDDATE and REPLACEoptions. The contents of the less accepted one are thenerased. The procedure is repeated for each pair of disksin the string. The string is defined in the minidiskassignment (MDA) section of the product parameterfile.



VMF1938I Merging string {vdev1|dirid1} to{vdev2|dirid2}

Explanation: The contents of the first minidisk ordirectory will be copied to the second minidisk ordirectory. The copy is done using COPYFILE with theOLDDATE and REPLACE options. Once the copy iscomplete, the contents of the first minidisk or directoryare erased.



VMF1939I Merge of string completed

Explanation: The contents of the specified string havebeen merged successfully.



VMF1944E Update file fn ft fm contains anunsupported statement type, type, for thepatch facility

Explanation: The update file identified in the messageis a patch update that contains a statement other thanNAME (Name for CSECT), ICS (Included controlsection), VER (verify), REP (replace), or comments.Only these statement types are allowed in patch updatefiles.


User response: While creating the update file, youmay have incorrectly typed the update statements. Ifso, correct the statements and retry the procedure.Incorrect update files can generate a bad nucleus.Therefore the update file should be corrected.

VMF1949I PTF ptfnum for product ppfname hasalready been applied

Explanation: The specified PTF was listed in the applylist but has previously been applied.



VMF1953W filename was interrupted the last time itwas run. filename $MSGLOG has beenrestored from the saved history file fn ft

Explanation: While a VMSES/E procedure is running,the cumulative message log is saved with a file type of$OLDLOG so the $MSGLOG for the current procedurecan be built. When the procedure is finished, the$OLDLOG is appended to the $MSGLOG, and the$OLDLOG is erased. If a $OLDLOG is found at thebeginning of a VMSES/E procedure, it indicates aprevious procedure did not complete normally. The$OLDLOG is then appended to $MSGLOG as it shouldhave been at the conclusion of the previous procedure.



VMF1954I messages


v Locating tag1 tag in file fn $PPF on disk fm.Processing of an override has begun by locating theoverride in the chain.



v Applying override override1 from file fn $PPF. Theoverride has been located and is in the process ofbeing applied.



VMF1955E Override override1 in fn $PPF containsword1. Word1 is not a valid control word

Explanation: A record that begins with ‘./’ was found,but it was not a valid control record. Valid controlrecords are ./INSERT, ./DELETE and ./END.


Command processing stops due to the internal error.


VMF1956E An ./INSERT control record has beenencountered without a corresponding./END control record in overrideoverride1 from fn $PPF

Explanation: The ./END record is required to closethe Insert Block.



User response: Correct the override in the productparameter file and reissue the command.

VMF1957E cntrlrec has been located in an invalidlocation in override override from fn$PPF

Explanation: The ./INSERT and ./DELETE controlrecords can only be located in updateable sections of aproduct parameter file. Updateable sections include:DCL, :MDA, :RECINS, :RECSER, :BLD, and :DABBV.


User response: Correct the override in the productparameter file and enter the command again.

VMF1958W messages


v symbol1 symbol has been found on a ./DELETEcontrol record in file fn ft but the symbol cannot belocated in tag1 section.

The record that was supposed to be deleted was notfound. No delete was performed.

v symbol1 symbol has been found on a ./INSERTcontrol record in file fn ft but the symbol cannot belocated. The insert will be at the end of the tag1section in the file fn2 ft2.

The symbol used to identify where the insert is totake place can not be found. The information will beinserted at the end of the section indicated in themessage.


User response: If the action taken is not satisfactory,correct the override in the product parameter file andenter the command again.

VMF1965E messages


v Command command failed with RC=rc

v Command command failed with RC=rc whileoperating upon file fn ft [on {vdev|dirid} (fm)]

v Command command failed with RC=rc when issuedwith argument(s): args

v Command command failed with RC=rc whileprocessing object obj

v Command command failed with RC=rc whileprocessing object obj; It was operating upon file fnft [on {vdev|dirid} (fm)]

v Command command failed with RC=rc whileprocessing object obj; It was issued withargument(s): args

v Command command (issued in server userid) failedwith RC=rc

v Command command (issued in server userid) failedwith RC=rc when issued with argument(s): args

The specified command failed.

System action: RC = 100. Command processing stopsbecause of the error associated with the listedcommand.

User response: Review the console log and anyVMSES/E $MSGLOG files for any additional relatederror messages, and then refer to the appropriatedocumentation for the failing command. Correct theproblem, and enter the applicable VMSES/E commandagain.

VMF1966W messages


v Command command ended with RC=rc

v Command command ended with RC=rc whileoperating upon file fn ft [on {vdev|dirid} (fm)]

v Command command ended with RC=rc when issuedwith argument(s): args

v Command command ended with RC=rc whileprocessing object obj



v Command command ended with RC=rc whileprocessing object obj; It was operating upon file fnft [on {vdev|dirid} (fm)]

v Command command ended with RC=rc whileprocessing object obj; It was issued withargument(s): args

v Command command (issued in server userid) endedwith RC=rc

v Command command (issued in server userid) endedwith RC=rc when issued with argument(s): args

The specified command completed with warnings.



User response: Refer to the documentation for thecommand cited by the message. Determine if there is aproblem, take corrective action if necessary, and reissuethe applicable VMSES/E command.

VMF1967E messages


v Command command did not complete successfully

v Command command did not complete successfully;Expected response not obtained

v Command command did not complete successfully;Expected response value not obtained

The indicated command did not complete as expected,or, it did not produce a response or result that wasexpected.


User response: Review the console log for anyadditional related error messages, and then refer to theappropriate documentation for the failing command.Correct the problem, and enter the original commandagain.

VMF2000I Objects in segment build list fn ft havebeen built or deleted. Any segmentsusing this build list will have to berebuilt.

Explanation: The specified build list contains objectsthat have been built or deleted. If a saved segment usesthe build information in this build list, the savedsegment will have to be rebuilt to incorporate thechanges.


User response: If the changes to the rebuilt objectsnecessitate any changes to the definition of the savedsegment that uses the specified build list, make thosechanges. If the saved segment is a member of asegment space, complete any necessary changes to theother members. If any member of a segment space is

changed, all the members must be rebuilt. Enter theVMFBLD command with the name of the system savedsegment build list that contains all of the savedsegments that need to be rebuilt.

VMF2001E This userid does not have the requiredprivilege class to issue command(s):cmds

Explanation: The function attempted to issue thespecified commands on your behalf, but your user IDdoes not have the required privilege class.


User response: Have your user ID modified to includethe privilege class necessary to issue the specifiedcommands, or switch to another user ID that alreadyhas the privilege. Then invoke the function again.

VMF2002I A DEFSEG command will be issued forn segment(s).

Explanation: The SEGDATA file definitions for thesaved segments to be built have been verified. ADEFSEG will now be issued for each saved segment todefine the saved segment to CP.

System action: The system issues the DEFSEGcommands.


VMF2003W The fn ft fm file has been changed andmust be moved to the mode disk.

Explanation: The specified file has been changed andmust be moved to the specified disk.

System action: RC=4. Processing continues.

User response: Copy the file to the specified file mode(replacing any existing version on that file mode). Youcan then erase the file from the file mode where it wasmodified. If the specified disk is the S-disk, you mustalso enter SAMPNSS CMS to define the CMS savedsystem. Then re-IPL the S-disk with the PARMSAVESYS CMS option to update the S-disk shareddirectory. If the specified file is SYSTEM SEGID, thenlogical segments were changed on the system. Copy theupdated SYSTEM SEGID file to the test system disk(490) and the S-disk. Failure to do so causes theupdated SYSTEM SEGID to be overlaid by an oldercopy when placing CMS service into production in afuture service session. If these are critical segments,update the S-disk before you IPL or before new userslog on.

VMF2004I No logical segments can be built.

Explanation: An error has occurred that prevents anyfurther building of saved segments that are composedof logical saved segments. Saved segments that do not



contain logical saved segments will be built.

System action: Processing continues if there are savedsegments that do not contain logical saved segments;otherwise, processing stops.

User response: After processing ends, look at theprevious error messages in the message log ($VMFBLD$MSGLOG) to determine why logical saved segmentscould not be built. Also look at the messages issued bythe SEGGEN command, which are located in thephysical and logical segment map files (file typesPSEGMAP and LSEGMAP). The most likely cause ofthe error is that the target disk is full. Correct theproblem and reenter the VMFBLD command.

VMF2005W The load function for segment segnamewas specified as 'UNKNOWN'. Thesegment has been defined but cannot bebuilt by VMFBLD.

Explanation: The load function for the specified savedsegment is defined as 'UNKNOWN' in the SEGDATAfile. VMFBLD has issued a DEFSEG command to definethe saved segment, but cannot build it.

System action: RC=4. Processing continues with thenext saved segment.

User response: After processing ends, invoke thenecessary procedures to load and save the savedsegment. Note that the saved segment has already beendefined and should not be redefined.

VMF2006E Build list bldlist in component compnameof ppfname PPF could not be processedbecause its status was neither BUILTnor DELETED.

Explanation: Information in the specified build list isneeded to build an object. However, the build listcannot be used because its status indicates that it mightcontain parts that have not yet been built or deleted.

System action: RC=12. Syntax checking continues, butno saved segments are built or deleted.

User response: To set the correct status for the buildlist, start VMFBLD with the PPF, component, and buildlist names specified in the message, in addition to theAll and SETUP options. Then enter the originalVMFBLD command again to build the segments,specifying the SETUP option to reaccess the requireddisks.

VMF2007E There is no entry for segment segname infn ft.

Explanation: The specified saved segment cannot beprocessed because there is no information about it inthe specified file.

System action: RC=100. Syntax checking continues

with the next saved segment, but no saved segmentsare built or deleted.

User response: If the specified file is the SEGDATAfile, use the VMFSGMAP EXEC to add informationabout the saved segment to the file. Then reenter theVMFBLD command.

VMF2008E The build status status of build listbldlist in component compname of ppfnamePPF conflicts with the build status ofother parts of segment segname.

Explanation: The BLDPARMS statement for this savedsegment indicates that it is composed of several parts.The build status ('BUILT' or 'DELETED') of each ofthese parts must be the same. However, the status ofthe specified build list is not the same as the status ofother parts of the saved segment. Note that the buildstatus of a build list is taken from its productservice-level build status table. The status of any othertype of part specified on the BLDPARMS statement is'BUILT'.


Syntax checking continues, but no saved segments arebuilt or deleted.

User response: After processing ends, correct theinformation for the saved segment. To modify theBLDPARMS statement, use the VMFSGMAP EXEC. Tomodify the product service-level build status table, usethe VMFSIM EXEC. Then reenter the VMFBLDcommand.

VMF2009E A {build list bldlist|:BLDPARMS tag}that is used in building segment segnamecontains a load function loadfunc thatconflicts with the type of segment,{SEG|PSEG}.

Explanation: There is a mismatch between thespecified saved segment's type, as defined on the TYPEfield of the definition in the SEGDATA file, and theload function for the saved segment, as defined in thespecified product saved segment build list or on theBLDPARMS field of the definition in the SEGDATA file.If the type is 'PSEG', then each load function must befor a logical saved segment. If the type is 'SEG', thenthe load function cannot include a logical savedsegment.

System action: RC=100. Syntax checking continues,but no saved segments are built or deleted.

User response: After processing ends, correct theinformation for the saved segment. To modify the TYPEand BLDPARMS fields of the saved segment definitionrecord in the SEGDATA file, use the VMFSGMAPEXEC. Then reenter the VMFBLD command.


VMF2010I messages


v Processing has terminated due to an error. Noobjects have been built or deleted.

v Processing has terminated due to an error.Segments may have been purged but no segmentshave been built.

This message indicates whether any saved segmentsmight have been deleted before VMFBLD processingwas stopped due to an error. No saved segments havebeen built.

System action: The system waits for the next request.

User response: Look at the previous error messages inthe message log ($VMFBLD $MSGLOG) to determinewhat the errors were. If necessary, use the VMFSGMAPEXEC to modify saved segment definitions. Thenreenter the VMFBLD command.

VMF2011E Cannot use build list bldlist incomponent compname of ppfname PPF

Explanation: The specified build list could not beused, possibly because the product parameter file,component, or build list could not be found or was notvalid.

System action: RC=12. Syntax checking continues, butno saved segments are built or deleted.

User response: After processing ends, look at theprevious error messages in the message log ($VMFBLD$MSGLOG) to determine the cause of the error. Ifnecessary, use the VMFSGMAP EXEC to modify savedsegment definitions. Then reenter the VMFBLDcommand.

VMF2012E Storage in range addr1-addr2 for segnamein use.

Explanation: The saved segment segname spansaddr1-addr2, but the storage in that address range isalready in use.

System action: RC=100. The saved segment is notbuilt. Processing continues with the next savedsegment.

User response: After VMFBLD processing completes,determine what might have reserved storage in thatrange and release the storage if possible. If releasingthe storage is not possible, re-IPL with the CLEARoperand to clear storage. Then reenter the VMFBLDcommand.

VMF2013I Accessing disk or directory{vdev|dirname} as mode

Explanation: The disk or directory has been accessedat the specified mode.


User response: None

VMF2014E Objects objname1 and objname2 haveconflicting build status for segmentsegname.

Explanation: VMFBLD has identified multiple objectsthat require the same saved segment (the first part ofthe object name) to be built or deleted. However, theobjects do not have the same build status. The status ofone is 'DELETE', but the other is not. If one of theobjects has a build status of 'DELETE', then all theobjects must have that status.

System action: RC=100. Syntax checking continues forthe rest of the saved segments to be built, but no savedsegments are built or deleted.

User response: After processing ends, look at theservice-level build status table (whose file name isidentified in the PPF specified on the VMFBLDcommand) to determine which of this saved segment'sobjects have a build status of 'DELETE' and which donot. Note that VMFBLD assigns 'DELETE' status to anobject if it is in the build status table but is not in thebuild list. Change the status for the incorrect objects orremove them from the build status table. Then reenterthe VMFBLD command.

VMF2015E Members in the following space(s)cannot be built: spacename...

Explanation: The listed segment spaces have membersin common to be built. However, the members cannotbe built because the internal structure of one or more ofthe segment spaces is not complete. This may bebecause segment spaces or members have been purgedusing the PURGE NSS command without theASSOCIATES operand.

System action: RC=100. Processing continues forsaved segments that are not members of any of thelisted segment spaces.

User response: After processing ends, look at theprevious error messages in the message log ($VMFBLD$MSGLOG) to determine which segment spaces areincomplete. Use this information to resolve theproblem, probably by purging the incomplete segmentspaces using the PURGE NSS command with theASSOCIATES operand. Then reenter the VMFBLDcommand.

VMF2010I • VMF2015E


VMF2016E Segment segname cannot be built inspace spacename because its rangeoverlaps the range of an existingmember, membername.

Explanation: The range of the segment to be builtoverlaps the range of an unchanged segment already inthe segment space. A segment space cannot containoverlapping members. The specified existing membercould be in the skeleton segment space, if one exists.Or, it could be in the active segment space and not inthe skeleton segment space, because the member wouldthen be copied to the skeleton space when the changedsegment is built.

System action: RC=100 Processing continues buildingchanged segments that are not members of thespecified space or of any other space connected to thisspace. Two spaces are connected if they have at leastone member in common.

User response: After processing ends, useVMFSGMAP EXEC to view the existing and changedmembers of the specfied space and to modify theranges as necessary to avoid overlaps. Then start theVMFBLD command to build the segments that werenot built.

VMF2017W Saved systems cannot be added,changed, or deleted by VMFSGMAP

Explanation: Saved systems are not defined in thesystem saved segment build list or the SEGDATA file.Even though VMFSGMAP displays saved systemscurrently defined on the system, the information issupplied for planning purposes only. You cannot useVMFSGMAP to add, change or delete saved systems.


User response: Any changes to saved systems must bedone outside of VMFSGMAP.

VMF2018E The default language, langid, must beactive in order to build segments

Explanation: The default language langid indicated inthis message was not set. It must be set to buildsegments using VMFBLD.


User response: Enter the SET LANGUAGE commandspecifying the default language langid indicated in thiserror message, and then enter the PUT2PROD orVMFBLD command again.

VMF2024W One or more segments defined above2G are not displayed

Explanation: The VMFSGMAP command does notsupport segments that are defined above the 2 GB line,and the VMFSGMAP panel will not display thesesegments.



VMF2025I No segments found in{ERROR|SEGDATA}

Explanation: VMFSGMAP found no segments in errorin response to the VIEW ERROR subcommand or nosegments in the SEGDATA file in response to the VIEWSEGDATA subcommand.



VMF2026I QNSS

Explanation: The VMFSGMAP Query NSS Mapwindow displays the current definitions for a segmentor segment space. The output is in the same format asthe output returned by the CP QUERY NSS MAPcommand.



VMF2027W Members in segment space spacenamecannot be adjusted

Explanation: VMFSGMAP has tried to change theranges of the members of the specified segment spaceso that the ranges do not overlap. However, this hasnot been successful, due to conflicts with other savedsegments or due to a lack of storage.


User response: The members of the specified segmentspace cannot be built with overlapping ranges. UsingVMFSGMAP, either move the members manually toeliminate the overlaps or remove some members fromthe segment space.

VMF2028W PPF contains multiple segment buildlists.

Explanation: The product parameter file specified onthe VMFSGMAP command contains other build lists inaddition to the one specified on the VMFSGMAPcommand. The saved segment definitions displayed byVMFSGMAP depend on the build list.


User response: Make sure that the build list youspecified on the VMFSGMAP command is the one youwant to use.



VMF2029I Segment name required on OBJNAMEfield

Explanation: A saved segment name must be specifiedon the OBJNAME field when adding a new definition.The name must be different from the names of all theother saved segments and segment spaces on thissystem.


User response: Enter a unique saved segment nameon the OBJNAME field.

VMF2030I No overlapping members found

Explanation: There are no members with overlappingranges in the segment space.



VMF2031E Overlapping members found

Explanation: There are members with overlappingranges in the segment space. A segment space cannotbe built with overlapping members.

System action: Definition records for the overlappingmembers are added to the display.

User response: Use the Adjust Member function(PF11) to automatically adjust member ranges toeliminate the overlaps, or manually adjust the ranges ofthe overlapping members.

VMF2032I System and SEGDATA definitions arethe same for segment segname

Explanation: The storage ranges, page descriptorcodes, and segment space names defined in theSEGDATA file for the specified saved segment matchthe values defined on the system.



VMF2033I System and SEGDATA definitions areNOT the same for segment segname

Explanation: The storage ranges, page descriptorcodes, or segment space names defined in theSEGDATA file for the specified saved segment do notmatch the values defined on the system. If the savedsegment is rebuilt, it will be moved to the rangesdefined in the SEGDATA file, or it will added orremoved from segment spaces as defined in theSEGDATA file.


User response: Correct the storage ranges or segmentspace values in the SEGDATA definition if you do not

want the saved segment moved when it is rebuilt.

VMF2034I Building segment map

Explanation: VMFSGMAP is using information in theSEGDATA file and on the system to build a segmentmap.



VMF2035R Segment data has been changed. Enter(1) if you want to {exit withoutsaving|cancel} the changes or (0) tocontinue processing

Explanation: You have made changes to the segmentdata that will be lost if you exit the map or cancel thechanges.


User response: If you do not want to keep thechanges made during this session, enter ‘1’ to cancel orexit the map. It you want to continue processing andremain in the current panel, enter ‘0’.

VMF2036I No default segment data found

Explanation: You have requested that default savedsegment data be used. However, either the PRODPARTfile with this data could not be located or the file didnot contain the default data.


User response: Correct the PRODPART file name andcomponent name on the PRODID field, if it is incorrect.Otherwise, use the product documentation to enter thenecessary information for the saved segment definition.

VMF2037W One or more segment definitions inerror

Explanation: There are saved segment definitions inthe SEGDATA file that contain information that is notvalid, or there are currently segments defined on thesystem that are in error. The segments that are found inerror are identified in the segment map with a statuscode of E. Changes to the segment map can be saved inthis condition, but the saved segments in error willprobably not be built successfully.


User response: Before using VMFBLD to build asaved segment, ensure it is correctly defined in theSEGDATA file.

Continue viewing and changing the segment map.

To view only the segment definitions in error, enter thefollowing subcommand on the command line:

VIEW ERROR

VMF2029I • VMF2037W


v If a member saved segment is defined on the system,but does not have an associated segment space, thefollowing record is appended to the end of the map:

E segname MEM

v If a segment space is defined on the system, but hasno members, the following record is appended to theend of the map:

E segname SPA NOMEMBERS

v To see the system definition for a saved segment,press PF2 or PF14 to run “Chk Obj.”

v To purge a system data file causing an error, enter:

#cp purge nss spoolid

Note: If purging a segment space, be sure to specifythe ASSOCIATES operand on the PURGE NSScommand.

v To see the SEGDATA definition for a saved segment,press PF4 or PF16 from the Segment Map panel.Errors are highlighted on the Change SegmentDefinition panel. Correct the errors and return to themap by pressing PF5 or PF17.

VMF2038E messages


v Invalid data, data, on field field

v Missing data on field field

The specified field contains incorrect data or is missingrequired data. The saved segment definition will not beaccepted with this condition.


User response: Depending on the text of the message,correct the data or supply the missing data on thespecified field.

VMF2039W Userid not authorized to issue QUERYNSS. Segments defined on system notmapped

Explanation: VMFSGMAP issued the QUERY NSScommand to get information about saved segments andsaved systems defined on the system, but your user IDdoes not have the CP privilege class required to usethis command. The displayed segment map containsonly saved segments defined in the SEGDATA file.


User response: If you need to view and modify thecurrent system saved segment information, you musthave your user ID updated to give you the CPprivilege required to issue the QUERY NSS command,or switch to a user ID that already has that privilege.

VMF2040I Segment segname not defined inSEGDATA file

Explanation: The specified saved segment does notexist in the SEGBLIST SEGDATA file.


User response: Check the SEGBLIST SEGDATA file. Ifthe saved segment is not found, the segment can bebuilt using VMFSGMAP.

VMF2040W Segment segname not defined on {system| in SEGDATA file}

Explanation: The specified saved segment belongs to aproduct that is not installed on this system or thespecified saved segment is not found in the SEGDATAfile.


User response: Insure that the segment name wasspecified correctly.

VMF2041I Segment space spacename not defined.All segments mapped

Explanation: The specified segment space does notexist on the current system or in the SEGDATA file, soa definition for this segment space cannot be displayed.

System action: All the saved segments and segmentspaces defined on the system are added to the segmentmap. The system waits for the next request.


VMF2042I Fields in error must be corrected

Explanation: The highlighted fields contain incorrectdata. The saved segment definition will not be accepteduntil the fields are corrected.


User response: Correct the highlighted fields.

VMF2043E Duplicate segment and segment spacename name specified

Explanation: The specified name is already in use,either as the name of a segment space or as the nameof a saved segment. Each segment space name or savedsegment name must be unique.


User response: Change the name of the existing ornew segment space or saved segment to a name notalready in use.


VMF2044W messages


v Segment name segname already defined. Currentsegment definition will be replaced. The specifiedsaved segment name is already defined in theSEGDATA file. The existing definition in theSEGDATA file will be replaced by the new data fromthe panel.

v Segment name new_segname already defined inADD Object Panel. OBJNAME reset to old_segname.The new saved segment name you tried to define isalready in use in another definition on the panel.

System action: For the first variation, the system waitsfor the next request.

For the second variation, the duplicate name is restoredto the original name. The system waits for the nextrequest.

User response: For the first variation, if you do notwant to replace the existing definition in the SEGDATAfile, change the name in the OBJNAME field.

For the second variation, if you need to change thename of the saved segment, select a name not used forany other saved segment or segment space.

VMF2045W Duplicate segment space namesspacename specified.

Explanation: The specified segment space name hasbeen included multiple times on the SPACE field. Asaved segment cannot be a member of the samesegment space more than once.


User response: Correct the duplicate name if it shouldbe the name of a different segment space. Otherwise,remove the duplicate name.

VMF2046I Segment {segname|space spacename} hasbeen deleted

Explanation: You may receive this message whileworking in the segment map or after invoking theVMFBLD EXEC to build saved segments:

v If you receive this message while working in thesegment map, the specified saved segment orsegment space has been marked for deletion in theSEGDATA file. A 'DELETED' record is displayed atthe end of the map. The storage range that itoccupied can be used for other saved segments. Anymember of a deleted segment space is also deleted ifit is not a member of another segment space. Thesaved segment or segment space marked for deletionis not actually deleted from the current system untilVMFBLD is invoked.

v If you receive this message after invoking VMFBLD,the specified saved segment has been purged fromthe current system.

System action: If you receive this message whileworking in the segment map, the system waits for thenext request. If you receive this message after invokingVMFBLD, processing continues with the next savedsegment.


VMF2047I HELP for the VMFSGMAP EXECSegment Definition panel OBJNAMEfield

Explanation: This message provides theuser-requested HELP panel for the OBJNAME field onthe Segment Definition panel generated by theVMFSGMAP EXEC. It is displayed in HELP only.

For a description of the VMFSGMAP EXEC, refer toz/VM: VMSES/E Introduction and Reference.



VMF2048I HELP for the VMFSGMAP EXECSegment Definition panel DEFPARMSfield

Explanation: This message provides theuser-requested HELP panel for the DEFPARMS field onthe Segment Definition panel generated by theVMFSGMAP EXEC. It is displayed in HELP only.




VMF2049I HELP for the VMFSGMAP EXECSegment Definition panel SPACE field

Explanation: This message provides theuser-requested HELP panel for the SPACE field on theSegment Definition panel generated by theVMFSGMAP EXEC. It is displayed in HELP only.




VMF2050I HELP for the VMFSGMAP EXECSegment Definition panel TYPE field

Explanation: This message provides theuser-requested HELP panel for the TYPE field on theSegment Definition panel generated by theVMFSGMAP EXEC. It is displayed in HELP only.






VMF2051I HELP for the VMFSGMAP EXECSegment Definition panel OBJDESCfield

Explanation: This message provides theuser-requested HELP panel for the OBJDESC field onthe Segment Definition panel generated by theVMFSGMAP EXEC. It is displayed in HELP only.




VMF2052I HELP for the VMFSGMAP EXECSegment Definition panel OBJINFOfield

Explanation: This message provides theuser-requested HELP panel for the OBJINFO field onthe Segment Definition panel generated by theVMFSGMAP EXEC. It is displayed in HELP only.




VMF2053I HELP for the VMFSGMAP EXECSegment Definition panel GT_16MBfield

Explanation: This message provides theuser-requested HELP panel for the GT_16MB field onthe Segment Definition panel generated by theVMFSGMAP EXEC. It is displayed in HELP only.




VMF2054I HELP for the VMFSGMAP EXECSegment Definition panel DISKS field

Explanation: This message provides theuser-requested HELP panel for the DISKS field on theSegment Definition panel generated by theVMFSGMAP EXEC. It is displayed in HELP only.




VMF2055I HELP for the VMFSGMAP EXECSegment Definition panel SEGREQfield

Explanation: This message provides theuser-requested HELP panel for the SEGREQ field onthe Segment Definition panel generated by theVMFSGMAP EXEC. It is displayed in HELP only.




VMF2056I HELP for the VMFSGMAP EXECSegment Definition panel PRODIDfield

Explanation: This message provides theuser-requested HELP panel for the PRODID field onthe Segment Definition panel generated by theVMFSGMAP EXEC. It is displayed in HELP only.




VMF2057I HELP for the VMFSGMAP EXECSegment Definition panel BLDPARMSfield

Explanation: This message provides theuser-requested HELP panel for the BLDPARMS field onthe Segment Definition panel generated by theVMFSGMAP EXEC. It is displayed in HELP only.




VMF2058I HELP for the VMFSGMAP EXECSegment Map panel

Explanation: This message provides theuser-requested HELP panel for the Segment Map panelgenerated by the VMFSGMAP EXEC. It is displayed inHELP only.





VMF2059I HELP for the VMFSGMAP EXECSegment Definition panel

Explanation: This message provides theuser-requested HELP panel for the Segment Definitionpanel generated by the VMFSGMAP EXEC. It isdisplayed in HELP only.




VMF2060E The target string {vdev|dirid} must beenlarged by at least n cylinders beforemerging

Explanation: The requested merge did not take placebecause one of the targets is not large enough. Thetarget minidisk or directory must be able to hold all ofthe files from the source minidisk or directory, plus allof the files on the target minidisk or directory that arenot on the source.

System action: RC = 12. Command processing stopsbecause of the internal error.

User response: No files were moved so no clean up isnecessary. Enlarge the target minidisk or directory bythe required number of cylinders to accommodate thefiles from the source minidisk or directory.

VMF2063I Merge not required from {vdev1|dirid1}to {vdev2|dirid2} for string because{vdev1|dirid1} is empty

Explanation: If the source minidisk or directory of amerge is empty, there is no need to merge it.

System action: Command processing continues withother merges (if any).


VMF2065I string {vdev|dirid} was n percent fullbefore merging and m percent full aftermerging

Explanation: This message indicates how much spaceis left over after the merge and may help you in yourresource planning.



VMF2066E A previous {VMFAPPLY|VMFREM} didnot complete as indicated by theexistence of appid{$APRCVRY|$RMRCVRY} on the stringstring. Run {VMFAPPLY|VMFREM}before running command

Explanation: The last run of VMFAPPLY or VMFREMdid not complete as indicated by the presence of arecovery file on the string mentioned.


User response: Enter VMFAPPLY or VMFREM againfor the ppf and compname that correspond to the abovenoted appid. Then enter the command again.

VMF2068E No merge occurred because string{vdev|dirid} is your S-disk

Explanation: A system disk cannot be included in amerge.


User response: Remove the system disk from thestring and reissue the command.

VMF2069E messages


v Tape file tapefile is listed more than once in the{:RECINS|:RECSER} section of product parameterfile fn PPF (compname compname). The first token ofrecords in the :RECINS and :RECSER sections of theproduct parameter file is a tape file name. The tapefiles in these sections can only be listed once. To loadthe same tape file twice requires two invocations ofVMFREC.

v Build list bldlist is listed more than once in the:BLD section of product parameter file fn PPF(compname compname). The first token of records inthe :BLD section of the product parameter file is abuild list name. The build lists in this section canonly be listed once. To build the same build list twicerequires either two invocations of VMFBLD or twocopies of the build list with different file names.

v Minidisk disk is listed more than once on the stringstring in the :MDA section of product parameterfile fn PPF (compname compname). The first token ofrecords in the :MDA section of the productparameter file is the string name. Minidisks anddirectories can only be listed once per string.

v Directory dirid is listed more than once on the stringstring in the :MDA section of product parameterfile fn PPF (compname compname). The first token ofrecords in the :MDA section of the productparameter file is the string name. Minidisks anddirectories can only be listed once per string.

v String string is listed more than once on the :P2Psection of product parameter file fn PPF (compnamecompname). The first token of records in the :P2Psection of the product parameter file is the stringvalue for a test build minidisk or SFS directory.Minidisks and SFS directories can only be listedonce.





User response: Correct the specified section of theproduct parameter file and reissue the command.

VMF2070E messages


v Invalid string name string in the :MDA section ofproduct parameter file fn PPF (compnamecompname)

v String string is not in the :MDA section of productparameter file fn PPF (compname compname)

v String string is missing values in the :MDA sectionof product parameter file fn PPF (compnamecompname)

v Invalid tape file tapefile in the {:RECINS|:RECSER}section of product parameter file fn PPF (compnamecompname)

v Tape file tapefile is not in the {:RECINS|:RECSER}section of product parameter file fn PPF (compnamecompname)

v Invalid build list bldlist in the :BLD section ofproduct parameter file fn PPF (compnamecompname)

v Invalid target [string] for tape file tapefile in the{:RECINS|:RECSER} section of product parameterfile fn PPF (compname compname)

v Invalid part handler [parthandler] for tape file tapefilein the {:RECINS|:RECSER} section of productparameter file fn PPF (compname compname)

v Invalid target [string] for build list bldlist in the:BLD section of product parameter file fn PPF(compname compname)

v Invalid part handler [parthandler] for build list bldlistin the :BLD section of product parameter file fn PPF(compname compname)

v Invalid option option in the :P2P section of theproduct parameter file fn PPF (compnamecompname)

A string, tape file, build list, or part handler (or anassociated value) was specified improperly. Stringnames, tape files, build lists, and part handlers must allbe valid CMS file names. In addition, string namesmust begin with one of the seven defined string types(TASK, LOCAL, APPLY, DELTA, BASE, BUILD, orSYSTEM). Also, build lists cannot be namedUNKNOWN.

Strings are defined in the :MDA section of the productparameter file and are referenced as targets in the :BLD,:RECINS, and :RECSER sections and A target stringmust correspond to a string defined in the :MDAsection.

Tape files are defined in the :RECINS and :RECSERsections of the product parameter file and referenced inthe product contents directory on the tape or envelope,on the VMFREC command line, and on the:PROCOPTS tags in the :PARTS section of thePRODPART file. Tape file definitions must include apart handler and a target specification.

Build lists are defined in the :BLD section of theproduct parameter file and referenced in SoftwareInventory files and on the command lines of severalVMSES/E commands (for example, VMFBLD andVMFQOBJ). Build list definitions must include a parthandler and a target specification.

Options in the :P2P section of the specified PPF mustbe valid options for this section.


User response: Correct the string, tape file,optionbuild list, or part handler specification and enterthe command again. If the error is in the PRODPARTfile shipped by IBM, contact the IBM Support Centerabout this problem.

VMF2070W Build list bldlist is not in the :BLDsection of product parameter file fn PPF(compname compname)

Explanation: A build list that is located in the bldidSRVBLDS file for the component being built is notdefined in the :BLD section of the product parameterfile.

System action: RC=4. The build list is bypassed andprocessing continues.

User response: Correct the build list specification andenter the command again. If this build list wasintentionally removed from the PPF by an override,this message can be ignored.

VMF2071E Invalid device address or directory id,{vdev|dirid}, on the string string in the:MDA section of product parameter filefn PPF (compname compname)

Explanation: You have specified an minidisk ordirectory that is not valid. A minidisk address specifiedin the product parameter file (PPF) must be ahexadecimal number of no more than 4 characters inlength. A directory specified in the PPF must be fullyqualified. A fully qualified directory identifier is in theform filepoolid:userid.qualifier (qualifier can be multiplesubdirectory identifiers, that is, A.B.C).


User response: Correct the minidisk or directoryspecification in the PPF and reissue the command.


VMF2072E string cannot list {vdev|dirid} as sourceand target

Explanation: As defined in the product parameter file,the specified minidisk or directory would be both thesource and the target for the same merge.



VMF2073E You specified n pair(s) of minidisks ordirectories to be merged for string, butonly m pair(s) are defined in the :MDAsection of product parameter file fn PPF(compname compname)

Explanation: You have specified a number of levels onthe command line which is greater than the number oflevels defined in the :MDA section of the productparameter file. There must be at least 1 pair ofminidisks or directories defined in the productparameter file.



User response: Specify a valid number of pairs on thecommand line or define valid pairs in the productparameter file and reissue the command.

VMF2074E Level fn ft of part fn ft [in object object]in build list fn ft is missing

Explanation: The specified level of a part could not befound. This part is required to build this object, so theobject will not be built.

If the missing level shown contains a base file type (ie.fta00000), then VMSES/E was unable to find the baselevel of the part. The base level of a part has twopossible forms: the first has the base file type and canreside on any disk, the second has the real (executable)file type and must reside on a BASE disk. VMSES/Eissues this message if neither form of the base level canbe found.

System action: RC = 28. Command processing stopsfor the specified object.

User response: Determine why the specified file ismissing. If this is an acceptable condition, the IGNOREpart option may be specified on the :OPTIONS tag forthe part in the object definition for the specified object.

VMF2074I Part fn ft [in object object] in build list fnft will be ignored

Explanation: There is no defined level for thespecified part, but the IGNORE part option was

specified so the part will be ignored and the buildingof the object will continue. If all parts within an objectare ignored, the object will receive a status of BUILT,even though the entire object will be ignored.




VMF2075E messages


v The file type abbreviation ftabbrev could not betranslated to a real file type

v The file type abbreviation ftabbrev could not betranslated to a base file type

v The base file type could not be determined becausethe part was not serviced and a file typeabbreviation was not specified

The VM SYSABRVT table, in conjunction with the:DABBV section of the PPF, contains information thatallows an abbreviation for a file type to be translated toeither a real file type or base file type. This translationhas failed.


Command processing stops because of the not foundcondition.

User response: Check the VM SYSABRVT table for theabbreviation and ensure you have built the latest levelof the abbreviation table. When using VMFSIM and thiserror occurs:

v Verify the file type abbreviation used on thecommand invocation.

v If a file type abbreviation was not specified on theVMFSIM invocation and the part was not serviced,specify a file type abbreviation.

If the abbreviation is still not found, contact your IBMsupport center.

VMF2076I messages


v Copying filename filetype on address (filemode) totofilename tofiletype tofilemode for input to the loader

v Copying filename filetype on address (filemode) totofilename tofiletype tofilemode

One of the following occurred:

v If the file that is being copied to is $$$TLL$$ EXEC,the FASTPATH option was selected, and the buildlist, filename filetype, is being copied prior to invokingthe loader. The loader uses a build list named$$$TLL$$ EXEC as input. VMFBDNUC is copyingthe build list to $$$TLL$$ EXEC A, and the loader



may issue messages referring to $$$TLL$$ EXEC.These loader messages are actually referring to thefilename filetype build list.

v If the file being copied from is $$$TLL$$ EXEC,VMFBDNUC is copying the temporary build listcreated for the loader to the file name above. Thiscan be left on your disk and used later with theFASTPATH option.

v The file filename filetype address (filemode) was copiedto tofilename tofiletype tofilemode and used as atemporary work file.



VMF2080I The contents of fn ft fm follow: data

Explanation: This message is used to display thecontents of a file.



VMF2100E messages


v The apply of PTF ptfnum1 failed due to problemswith PTF ptfnum2.

v PTF ptfnum1 could not be applied because ptfnum2has not been received.

v PTF ptfnum1 is a corequisite of PTF ptfnum2 whichis already applied. This is an inconsistent state.

PTF ptfnum1 was specified in the Apply List and couldnot be applied for the specified reason.

System action: RC = 8. Processing of this PTFterminates. Processing continues with the next PTF inthe Apply List. All messages up to message 2115 relateto this failure.

User response: Review the $VMFAPP $MSGLOG todetermine which PTFs were not applied and the reasonfor each failure. Contact the IBM Support Center todetermine what should be done to correct the problem.

VMF2101I PTF ptfnum has been validatedsuccessfully

Explanation: The specified PTF has passedVMFAPPLY validation. If the VMFAPPLY commandcompletes successfully, the Software Inventory will beupdated to include this PTF.



VMF2102I n of m PTFs processed

Explanation: The first number indicates the number ofPTFs that have been processed. The second number isthe total number of PTFs which require processing.This message indicates the progress of the VMFAPPLYcommand. This message is issued after processing1/10, 2/10, .... of the PTFs in the Apply list. Thismessage does not appear in the $VMFAPP $MSGLOG.



VMF2103I The variations of this message areexplained below.

Explanation:

v The Software Inventory has been updated on theaddr (fm) disk. The command entered has completedsuccessfully. The maintenance level of the productspecified in the input product parameter file hasbeen updated on the specified disk.

v The Software Inventory has not been updated. TheSoftware Inventory has not been updated. This couldoccur if the command was entered with a test orplan option.



VMF2103E The Software Inventory must berecovered

Explanation: The command that was entered failed,and the Software Inventory files have been partiallyupdated and must be recovered. The data needed forrecovery is stored in temporary files.


User response: Determine the cause of the failure byexamining the messages issued previously. Make thenecessary corrections, and enter the command again.Respond to message VMF2114R to recover the SoftwareInventory and complete the interrupted command.

VMF2103W The Software Inventory has not beenupdated

Explanation: The entered command failed and theSoftware Inventory files have not been updated.


User response: Determine the cause of the failure byexamining the messages issued previously. Make thenecessary corrections and enter the command again.


VMF2104I PTF ptfnum contains user information.Review the :UMEMO section in fileptfnum $PTFPART.

Explanation: User information was provided with PTFptfnum. This information exists in the section identifiedby the :UMEMO tag in the ptfnum $PTFPART file.


User response: If the PTF was applied using theSERVICE command, use the VMFUPDAT SYSMEMOcommand to review the memo contents. Otherwise, useXEDIT to review the user information in the ptfnum$PTFPART file.

VMF2105I message

Explanation: This message is a summary of the resultsof the VMFAPPLY command. message is one of thefollowing:

v VMFAPPLY processing has completedSUCCESSFULLY. The fn Apply List contains n1PTFs. n2 PTFs were already applied. n3 PTFsapplied successfully. n4 PTFs were included. n5were excluded or require excluded PTFs. n6 PTFsfailed.

v VMFAPPLY processing has completedUNSUCCESSFULLY. The fn Apply List contains n1PTFs. n2 PTFs were already applied. n3 PTFspassed validation. n4 PTFs were included andpassed validation. n5 were excluded or requireexcluded PTFs. n6 PTFs failed.

v VMFAPPLY has terminated due to an error. The fnApply List contains n1 PTFs. n2 PTFs were alreadyapplied. n3 PTFs passed validation. n4 PTFs wereincluded and passed validation. n5 were excludedor require excluded PTFs. n6 PTFs failed.

v VMFAPPLY processing has completed withWARNINGS. The fn Apply List contains n1 PTFs.n2 PTFs were already applied. n3 PTFs appliedsuccessfully. n4 PTFs were included. n5 wereexcluded or require excluded PTFs. n6 PTFs failed.

N1 is the number of PTFs which are in the specifiedApply List.

N2 is the number of PTFs which are in the specifiedApply List and had an apply status of "APPLIED" or"SUPED" in the Apply Status table prior to theinvocation of the VMFAPPLY command.

N3 is the number of PTFs which are in the specifiedApply List and were processed successfully.

N4 is the number of PTFs which are not in thespecified Apply List, however are required, and wereprocessed successfully.

N5 is the number of PTFs which are in the specifiedApply List, however were not applied because the PTFswere in an Exclude list or required PTFs which are inan Exclude List.

N6 is the number of PTFs which are in the specifiedApply List and failed.



VMF2106I The fn Apply List contains n PTFs thatneed to be applied and m PTFs that arealready applied

Explanation: This message is a summary messageindicating the amount of processing that will be done.

N is the number of PTFs which are in the specifiedApply List and require processing. This number doesnot reflect duplicate entries.

M is the number of PTFs which are in the specifiedApply List and had an apply status of APPLIED orSUPED in the Apply Status table prior to theinvocation of the VMFAPPLY command.



VMF2107I n parts are missing

Explanation: After processing all the PTFs specified inthe Apply list, the highest PTF version of all partsassociated with the PTFs in the Apply list must exist.This message is a summary message and is issued ifany parts are missing.


User response: Review the $VMFAPP $MSGLOG.Message VMF002E is issued for every missing part.Copy the missing parts to the DELTA string and reissuethe VMFAPPLY command with the initial parameters.

VMF2108I n parts failed self-documentinginformation validation

Explanation: The CKSDI option was selected. Theself-documenting information in the highest appliedversion of all parts containing self-documentinginformation is compared to the version vector table.This message is a summary message and is issued ifany mismatches are identified.


User response: Review the $VMFAPP $MSGLOG.Message VMF2117E provides detail information oneach mismatch.



VMF2109I VMFAPPLY will automatically correctthe problem identified by message2122E by including the missing PTFs inthe current Apply list.

Explanation: VMFAPPLY has attempted to correct theproblem described by message 2122E. If VMFAPPLYcompletes successfully with no other error messages,the problem has been corrected.



VMF2109R VMFAPPLY will automatically correctthe problem identified by message2122E by including the missing PTFs inthe current Apply list. Enter (1) tocontinue; (0) to quit.

Explanation: The set of PTFs applied on the lower(earlier) maintenance level is not a subset of the PTFson the highest (latest) level. The architecture of theservice database requires this hierarchy to bemaintained, otherwise incorrect Auxiliary files mayexist. VMFAPPLY will automatically correct thisproblem by applying the missing PTFs to the higherlevel.

This problem can occur if multiple levels of APPLYdisks are maintained (for example, :MDA entry in PPF= APPLY 2A6 2A4 2A2) and service is applied to anintermediate level (for example, 2A4) while serviceexists at a higher level (for example, 2A6).

System action: RC = 0 or 500. Command processingstops with a return code of 500 if you enter 0.Command processing continues if you enter 1.

User response: Respond to the prompt be entering a 0or 1.

VMF2110I PTF ptfnum is an included PTF and hasbeen applied successfully.

Explanation: The specified PTF is not in the apply list,however is required by a PTF in the apply list, and haspassed VMFAPPLY validation. If the VMFAPPLYcommand completes successfully, the softwareinventory will be updated to include this PTF.



VMF2111E PTF ptfnum is in the fn Exclude List andis already applied. This PTF cannot beexcluded

Explanation: The fn Exclude List includes PTF ptfnum.However, this PTF has a status of APPLIED in theapply status table. Exclude Processing can only excludePTFs that are not applied.


User response: There are two options:

v Remove the PTF from the specified Exclude List.

v Use the VMFREM command to un-apply thespecified excluded PTF.

VMF2112W PTF ptfnum1 has a requisite-type requisitefor PTF ptfnum2 in product prodid(product description).

Explanation: The ptfnum1 has an out-of-componentrequisite for ptfnum2 in the product specified by prodid.The product description is obtained from theout-of-component products PRODPART file.

The valid requisite types are:

PREREQThe ptfnum1 requires ptfnum2, but ptfnum2does not require ptfnum1.

COREQThe ptfnum1 and ptfnum2 require each other.

IFREQ The ptfnum1 requires ptfnum2 if product prodidis installed. The ptfnum2 does not requireptfnum1.


User response: Verify that the required PTF isinstalled on the specified product by using theSERVICE command with the STATUS operand.

VMF2113E An error was detected while updatingthe version information for part fnftabbrev in PTF ptfnum for reason = nn

Explanation: When processing a PTF duringVMFAPPLY or VMFREM, the version vector is updatedbased on information in the $PTFPART file. Aninconsistency between the version vector and the$PTFPART file was detected.

System action: RC = 8. Processing of the specified PTFterminates. VMFAPPLY continues processing with thenext PTF in the apply list. VMFREM terminatesprocessing.

User response:

Code Meaning

1 The $PTFPART file indicates the part is notsupported with AUX files. This is notconsistent with the information in the versionvector table or on the :APARS tag in the$PTFPART file.

2 The :APARS tag is missing in the $PTFPARTfile.

3 The $PTFPART file indicates the part is



supported with source updates. This is notconsistent with the information in the versionvector table.

4 The :APARS in the $PTFPART file containsincorrect data.

5 The APAR history specified on the :APARS tagin the $PTFPART file does not match theversion vector table.

6 This PTF contains a new APAR without acorresponding update file.

This error is caused by incorrect information in the$PTFPART file for this PTF or a prior PTF.

VMF2114R The prior invocation of{VMFAPPLY|VMFREM} abnormallyterminated during “critical processing”.{VMFAPPLY|VMFREM} willautomatically recover from this situationby completing the interrupted{VMFAPPLY|VMFREM} invocationusing data saved in temporary files.Enter (0) to quit; (1) to complete theprior {VMFAPPLY|VMFREM}invocation.

Explanation: VMFAPPLY or VMFREM wasinterrupted during “critical processing.” This messageis asking if you want VMFAPPLY or VMFREM toautomatically recover from this situation.

“Critical processing” is the step in VMFAPPLY orVMFREM when the Software Inventory is updated andAUX files are generated.

System action: RC = 0 or 500. If you enter 0,command processing stops with a return code of 500. Ifyou enter 1, command processing continues.

User response: You should enter 1 to recover theSoftware Inventory and complete the prior invocationof VMFAPPLY or VMFREM. However, if you choose tonot complete the prior invocation of VMFAPPLY orVMFREM, you must clean up manually.

For VMFAPPLY this is done by erasing the contents ofthe disk that contains the file appid $APPCVRY. Thisdisk must be the highest APPLY disk that containsservice. This disk should be empty (an empty highestAPPLY disk is recommended prior to usingVMFAPPLY). So the files erased are related to the priorinvocation of VMFAPPLY only. If this disk was notempty prior to the interrupted VMFAPPLY (multipleVMFAPPLY invocations were issued without usingVMFMRDSK), then the earlier invocations ofVMFAPPLY related to the pre-existing files must bererun.

For VMFREM, this is done by restoring the backups foreach disk that contains the file appid $RMRCVRY.

If you are unable to recover, contact the IBM SupportCenter for assistance.

VMF2115I Validating {PTF ptfnum|segmentsegname}.

Explanation: This message is issued at the start ofprocessing for each PTF in the Apply List or for eachsaved segment to be deleted or built.



VMF2116W The apply of PTF ptfnum1 failed becausePTF ptfnum2 is in the fn Exclude list.

Explanation: PTF ptfnum1 was specified in the ApplyList, but it could not be applied because it was in the fnExclude list or it requires a PTF in the Exclude list.

System action: RC = 4. Processing of this PTFterminates and processing continues with the PTF inthe Apply List.


VMF2117E The self-documenting information in fnft does not match the version vectortable.

Explanation: Some PTF numbered parts containservice history information in the part itself. Thissupport is determined by the presence of the SDIkeyword on the PROCOPTS tag in the $PTFPART file.If the CKSDI option was specified in the $PPF or onthe VMFAPPLY command invocation, then thisinformation is compared to the version vector table.This comparison determined that the information doesnot match.


Validation of the remaining parts continues.

User response: Determine the cause of the mismatch.Message 2121W contains the part history and theversion vector entry. The number of entries must beequal. The comparison is based on the following rules:

1. The part entry matches exactly the third value inthe version vector entry.

2. Characters 2-6 of the part entry match characters 3-7of the first value in the version vector entry.

The cause of this error is one of the following:

1. IBM shipped an incorrect part.

2. An incorrect assembly was done for the part.


VMF2118I Starting {VMFAPPLY|VMFREM}recovery

Explanation: The prior invocation of VMFAPPLY orVMFREM for the product identified in the PPFspecified on the command abnormally terminatedduring “critical processing.” Automatic recovery fromthis situation is starting.

Critical processing is the step in VMFAPPLY orVMFREM where the software inventory is updated andAUX files are generated. Interruption of the processmay result in a software inventory with inconsistentinformation. This state is identified by the presence ofthe file appid $APPCVRY or $RMRCVRY on the APPLYor DELTA string.

System action: The automatic recovery proceduresstart.

User response: Check for message VMF2119I.

VMF2119I {VMFAPPLY|VMFREM} recovery hascompleted successfully

Explanation: The prior invocation of VMFAPPLY orVMFREM for the product identified in the $PPFspecified on the command abnormally terminatedduring “critical processing.” Automatic recovery fromthis situation was successful.


User response: The invocation of the VMFAPPLY orVMFREM command that initiated the recoveryprocedures is ignored. If this was a re-invocation of theinterrupted command, no further action is required.The recovery procedures completed the originalcommand. If this invocation of VMFAPPLY orVMFREM is new, enter the command again.

VMF2120W Part fn ftabbrev has service at level level1[on the {vdev|dirname} (fm) disk] whichis a higher level than level2 [on the{vdev|dirname} (fm) disk]. Thehigher-level service may need to bereworked or removed

Explanation: VMFAPPLY or VMFREM found entriesin the level1 version vector table that are at a higherlevel in the control file than level2.


User response: Message 2121I, which follows, containsthe version vector entry for fn ftabbrev at localmodification level level1. You must investigate whetherthis local modification level conflicts with the service inlevel level2. You may need to rework or remove thelocal modification at the higher level.

VMF2121I diagnostic data

Explanation: This message displays diagnosticinformation associated with the preceding errormessage.


User response: Review the accompanying message.

VMF2122E The set of PTFs in the Apply StatusTable (fn1 SRVAPPS) on the addr disk(filemode fm1) is not a subset of thePTFs in the highest level Apply Statustable on the addr2 disk (filemode fm2).This is an inconsistent state.

Explanation: The set of PTFs applied on the lower(earlier) maintenance level is not a subset of the PTFson the highest (latest) level. The architecture of theservice database requires this hierarchy to bemaintained, otherwise incorrect Auxiliary files mayexist.


Processing terminates.

User response: You can correct this problem byapplying the missing PTFs to the higher level. WhenVMFAPPLY is issued while this situation exists it willautomatically apply the missing PTFs to the higherlevel.

The details of the problem can be displayed using thefollowing command: “VMFSIM COMPTBL fn1SRVAPPS fm1 fn2 SRVAPPS fm2 TDATA :PTF”

This problem can occur if multiple levels of APPLYdisks are maintained (for example, :MDA entry in PPF= APPLY 2A6 2A4 2A2) and service is applied to anintermediate level (for example, 2A4) while serviceexists at a higher level (for example, 2A6).

VMF2123W Part fn ft of PTF ptfno must be created

Explanation: Part fn ft, which is part of PTF ptfno, wasnot found. This part is maintained with updates andmust be created.


User response: This part can be generated usingVMFASM, VMFHASM, or EXECUPDT. The generationtool used depends on the type of part. Text parts useVMFASM or VMFHASM. EXECs and XEDIT parts useEXECUPDT. For text parts, any MACLIBs affected byservice must be built prior to using the generationtools. After the part generation tool is complete theresulting part must be copied to the DELTA string andthe file type must be ft.



VMF2124W The fn Apply List is empty

Explanation: The fn Apply list does not contain anyPTFs. There is no processing required in VMFAPPLY.

System action: RC = 4. Processing completes.


VMF2125I messages


v VMFREM processing completed successfully

v VMFREM processing completed successfully withwarnings

v VMFREM processing completed with the TESToption

v VMFREM processing terminated due to an error

v VMFREM processing terminated due to a QUITresponse to a prompt

v VMFREM processing terminated due to a severeerror

This is an informational message informing you whenthe VMFREM command has completed processing.


User response: If a severe error has occurred, theSoftware Inventory files have been partially updatedand must be recovered. Determine the cause of thefailure by examining the messages issued previously.Make the necessary corrections, and enter thecommand again. VMFREM will attempt to recover theSoftware Inventory and complete the prior invocationof VMFREM.

VMF2126I messages


v PTF ptfnum is a dependent PTF and has passedun-apply validation

v PTF ptfnum has passed {un-apply|un-receive|commit} validation

v Service level {vdev|dirname} (fm) has passed removevalidation

v MOD modid is a dependent MOD and has passedremove validation

v MOD modid has passed remove validation


v The specified PTF has passed validation by theun-apply, un-receive, or commit function ofVMFREM. If the VMFREM command completessuccessfully, this PTF will be un-applied, un-received,or committed as specified.

v The specified service level has passed validation bythe remove function of VMFREM. If the VMFREMcommand completes successfully, this service levelwill be removed.

v The specified MOD has passed validation by theremove local modification function of VMFREM. Ifthe VMFREM command completes successfully, thisMOD will be removed.



VMF2127I messages


v PTF ptfnum cannot be removed because it has notbeen {received|applied}

v Service level {vdev|dirname} (fm) cannot be removedbecause it has no applied PTFs

v MOD modid cannot be removed because it has notbeen applied


v The specified PTF could not be removed because itwas not received.

v The specified PTF could not be removed because itwas not applied and the UNRECEIVE option wasnot specified.

v The specified service level could not be removedbecause it contained no applied PTFs.

v The specified MOD could not be removed because itwas not applied.



VMF2128E messages


v The un-apply of PTF ptfnum1 failed due toproblems with PTF ptfnum2

v The un-apply of PTF ptfnum1 failed due toproblems un-applying PTF ptfnum2 from servicelevel {vdev|dirname} (fm)

v The {un-receive|commit} of PTF ptfnum failed

v The removal of service level {vdev|dirname} (fm)failed due to problems with PTF ptfnum

v The removal of MOD modid1 failed due toproblems with MOD modid2


v PTF ptfnum1 was specified on the VMFREMcommand and could not be un-applied due to afailure un-applying PTF ptfnum2. If ptfnum1 andptfnum2 are not the same PTF, then PTF ptfnum2 wasbeing un-applied because it is a dependent of PTFptfnum1.

VMF2124W • VMF2128E


v PTF ptfnum1 was specified on the VMFREMcommand and could not be un-applied due to afailure when un-applying PTF ptfnum2 from servicelevel {vdev|dirname} (fm), which is not the highestservice level.

v PTF ptfnum was specified on the VMFREM commandand could not be {un-received|committed} due to aprocessing failure.

v Service level {vdev|dirname} (fm) was specified to beremoved by the VMFREM command and could notbe removed due to a failure when un-applying PTFptfnum.

v MOD modid1 was specified on the VMFREMcommand and could not be removed due to a failurewhen removing MOD modid2. If modid1 and modid2are not the same MOD, then MOD modid2 was beingremoved because it is a dependent of MOD modid1.

System action: Processing terminates.

User response: Review the $VMFREM $MSGLOG todetermine which PTFs or MODs failed and the reasonfor each failure. Contact the IBM Support Center todetermine what should be done to correct the problem.


Explanation:

v The following PTFs {were un-applied|passedun-apply validation}: L1

v The following PTFs {were un-applied but|passedun-apply validation but would} remain superseded:L2

v The following PTFs {were un-received|passedun-receive validation}: L3

v The following PTFs {were committed|passedcommit validation}: L4

v The following service levels {were removed|passedremove validation}: L5

v The following parts {were erased|passed erasevalidation}: L6

v The following MODs {were removed|passedremove validation}: L7

v The following MOD parts {were removed|passedremove validation} from the indicated versionvectors: L8

v The following local AUX files were updated: L9

This message is a summary of the results of theVMFREM command.

L1 A list of PTFs that were un-applied or thatwould be un-applied if VMFREM completedsuccessfully with the RUN option.

L2 A list of PTFs that were un-applied or thatwould be un-applied if VMFREM completed

successfully with the RUN option, but retainedor would retain a status of SUPED in theSRVAPPS table.

L3 A list of PTFs that were un-received or thatwould be un-received if VMFREM completedsuccessfully with the RUN option.

L4 A list of PTFs that were committed or thatwould be committed if VMFREM completedsuccessfully with the RUN option.

L5 A list of service levels that were removed orthat would be removed if VMFREM completedsuccessfully with the RUN option.

L6 A list of parts that were erased or that wouldbe erased if VMFREM completed successfullywith the RUN option.

L7 A list of MODs that were removed or thatwould be removed if VMFREM completedsuccessfully with the RUN option.

L8 A list of MOD parts that were removed fromthe indicated version vectors or that would beremoved from the indicated version vectors ifVMFREM completed successfully with theRUN option.

L9 A list of local AUX files that were updated.

Parts that passed validation are listed as file name andfile type. Parts that were erased are listed as file name,file type, and file mode. If the file mode is displayed asa dash, the part was not found and was assumed to bepreviously erased. This is not an error condition.



VMF2130W VMFREM has encountered thefollowing missing parts whileattempting to {un-apply PTFs|removeservice levels|remove MODs}: fn ft1 [orfn ft2 on a base disk]

Explanation: While un-applying PTFs, removingservice levels, or removing local modifications,VMFREM detected that the highest service level of oneor more parts is missing. If the missing part is aserviced level of the part, it is displayed as fn ft1. If themissing part is the base level of the part, it is displayedin its two possible forms: as fn ft1 with the base filetype and as fn ft2 with the real file type, which mustreside on a base disk.

System action: RC = 4. Message VMF2131R is issuedfor each missing part.

User response: Respond to message VMF2131R.


VMF2131R VMFREM can continue {un-applyingPTFs|removing service levels|removingMODs}, but missing part fn ft1 [or fn ft2on a base disk] {will have to be restoredbefore running VMFBLD|may beneeded to rework remaining MODs}[unless the part is bypassed by notadding it to the select data file]. Enter(0) to quit; (1) to continue[; (2) to bypass the part].

Explanation: VMFREM has detected that the highestservice level of a part that may be required byVMFBLD or may be needed to rework localmodifications is missing. This message is asking if youwant to continue VMFREM processing. You will onlybe offered the bypass response for missing base levelparts needed by VMFBLD.

System action: RC=0 or 500. If you enter 0, commandprocessing stops with a return code of 500 and nothingis updated. If you enter 1, command processingcontinues. If you enter 2, command processingcontinues, but the part is not added to the select data($SELECT) file.


0 If you want to halt VMFREM processing dueto the missing part. The system will beunchanged.

1 If you intend to restore the missing part oryou do not need it for rework and want tocontinue VMFREM processing. If you do notrestore a missing part that is needed byVMFBLD prior to running VMFBLD, buildprocessing will fail. You can restore a missingpart in one of the following ways:

v You can retrieve it from a product, serviceor backup tape.

v If the part is source maintained, you cangenerate it by using VMFHLASM orVMFEXUPD.

2 If you do not intend to restore the missingpart and want to continue VMFREMprocessing. The missing part will not be addedto the select data file. Therefore, any objectsthat contain that part will not be automaticallyrebuilt and will remain at the level thatcontains the removed service. VMFBLD canfail even with the bypass option if an objectthat contains the missing part is forced to berebuilt. This can occur if another part in theobject is added to the select data file byVMFAPPLY or VMFREM, or if VMFBLDmarks the object to be built due to a buildrequisite or the use of the ALL option.

The 2 response should be used if the missingpart never existed. This would occur if a newwildcard part was added by the removed

service. It is not possible for VMFREM todetect new wildcard parts. The only way todetermine if a wildcard part is new is to checkthe original install tapes for the part. If you donot find the part on the install tapes, then it isnew. In this case the object built from the partwill remain on its BUILD disk. If you wish to,you can remove the object using VMFERASE.

The 2 response could also be useful when abase level of a part was not shipped, as in thecase of HELP files. Leaving a HELP file at thelevel of the removed service might be a betteralternative to restoring the base level from theinstall tapes.

VMF2132W The following parts are missing: fn ft1[or fn ft2 on a base disk] {{They must|IfVMFREM had successfully completedwith the RUN option, they would needto} be restored before runningVMFBLD|They may be needed torework MODs}.

Explanation: This is a summary message describingone of the following:

v You received message VMF2131R for one or moremissing parts, and you responded to continue.

v You were running in TEST mode and VMFREMdetected that the highest service level of one or moreparts would be missing if VMFREM processingcompleted.


User response: If you were not running in TEST modeand processing completed successfully, you mustrestore a missing part that is need by VMFBLD beforerunning VMFBLD.

You can restore a missing part in one of the followingways:

v You can retrieve it from a product, service, or backuptape.

v If the part is source maintained, you can generate itby using VMFHLASM or VMFEXUPD.

VMF2133W The following parts were bypassed: fnftabbrev {They were not|If VMFREMhad successfully completed with theRUN option, they would not have been}added to the select data file andtherefore any object containing them{will not be|would not have been}automatically rebuilt when VMFBLD{is|was} run.

Explanation: This is a summary message listing partswhose highest level, the base level, could not be foundby VMFREM after remove processing. These parts willnot be added to the select data file because you choseto bypass them in response to message VMF2131R.

VMF2131R • VMF2133W


Objects that contain these parts will not be rebuilt byVMFBLD. They will remain at the level that containsthe removed service.



VMF2134E Issue the VMFAPPLY command toautomatically correct the problemidentified by message VMF2122E

Explanation: The set of PTFs applied on the lower(earlier) maintenance level is not a subset of the PTFson the highest (latest) level. The architecture of theservice database requires this hierarchy to bemaintained. Otherwise incorrect Auxiliary files mayexist. VMFAPPLY can automatically correct thisproblem by applying the missing PTFs to the higherlevel.


User response: Enter the VMFAPPLY command usingthe same PPF file name and component name that youused on the VMFREM command. When you receivemessage 2109R, respond to continue in order to allowVMFAPPLY to correct the problem. After VMFAPPLYhas corrected the problem, rerun the VMFREMcommand.

VMF2135I {Any|If VMFREM had successfullycompleted with the RUN option, any}product which has a requisite to one ofthe un-applied PTFs {should|wouldneed to} be removed. Any PTF, inanother product, whichhas a requisite to one of theun-applied PTFs also {should |would need to} be removed.

Explanation: This message will always follow messageVMF2129I “The following PTFs were un-applied:” or“The following PTFs passed un-apply validation:”

If an installed product, component or PTF has anout-of-component requisite to an un-applied PTF, itshould be removed.


User response: VMSES/E does not maintain any crossreference data on out-of-component requisitesTherefore, it is a manual task for you to determine ifanything should be removed.

Product requisites to out-of-component PTFs can befound in the $VMFINS $MSGLOG, the VM SYSREQTtable, the PRODPART files, or the productdocumentation. When you install a product, messageVMF2806W will identify any out-of-componentrequisites. If you have an installed product that has arequisite to an un-applied PTF, you should either usethe VMFINS DELETE command to remove the productor reapply the PTF.

PTF requisites to out-of-component PTFs can be foundin the $VMFAPP $MSGLOG, the SRVREQT tables, the$PTFPART files, and the RSU memos. When you applya PTF, message VMF2112I will identify anyout-of-component requisites. If you have an appliedPTF that has an out-of-component requisite to anun-applied PTF, you should use the VMFREMcommand to un-apply the PTF.

VMF2136I The following PTFs will be un-receivedbecause they were committed and arenow being un-applied: ptfnum

Explanation: If a committed PTF is un-applied, it willautomatically be un-received also. This is necessarybecause some or all of the parts of a committed PTFhave been erased. If the PTF were not un-received, itcould be reapplied and VMFAPPLY would fail for themissing parts.



VMF2137E VMFREM recovery has failed for Applyidentifier appid [on {vdev|dirid} (fm)].

Explanation: VMFREM was interrupted during“critical processing” and recovery has failed.

“Critical processing” is the step in VMFREM when theSoftware Inventory is updated and AUX files aregenerated.

System action: Processing is terminated.

User response: You can attempt to correct any errorsthat were encountered and rerun VMFREM to retryrecovery. If you cannot correct the errors or if recoverycontinues to fail, you must clean up manually.

Manual recovery is done by restoring the backups foreach disk that contains the file appid $RMRCVRY.

If you are unable to recover, contact the IBM SupportCenter for assistance.

VMF2138W PTF ptfnum could not be un-receivedbecause it contains the following buildlists: fn ft VMFBLD {must|would needto} be run before un-receiving PTFptfnum

Explanation: When a build list is serviced, VMFBLDrequires both the highest and the previous highest levelof the build list in order to successfully complete itsstatus function. When a PTF that contains a build list isun-applied, the PTF level of the build list becomes theprevious highest level. If the un-applied PTF was alsoun-received, the build list that is needed by VMFBLDwould be erased. Therefore, when a PTF that contains abuild list is un-applied, VMFBLD must be successfullyrun before that PTF can be un-received.




User response: If you want to un-receive PTF ptfnum,run the VMFBLD command with the STATUS option,and then run the VMFREM command for the PTF withthe UNRECEIVE option.

VMF2139I PTF ptfnum cannot be committedbecause it has not been received

Explanation: Only PTFs that have been received andapplied can be committed.



VMF2139W PTF ptfnum cannot be committedbecause it has not been applied

Explanation: Only PTFs that have been received andapplied can be committed. If a PTF that has not beenapplied were committed, VMFAPPLY could fail formissing parts.


User response: If you are attempting to commit PTFptfnum, in order to erase its parts, you can accomplishthe same result by un-receiving it using the VMFREMcommand.

VMF2140W PTF ptfnum will be committed, but noparts can be erased

Explanation: PTF ptfnum is eligible to be committed,but none of its parts are eligible to be erased. Each ofits parts is either the highest level of the particular part,a build list that is needed by VMFBLD, or an update.



VMF2141W No PTFs were selected to be committed

Explanation: This message is issued when theVMFREM command is specified with the ALL operandand the COMMIT option, and no PTFs are selected tobe committed. PTFs are selected based on the APPLIEDor SUPED operand. If the APPLIED operand isspecified, all PTFs with the status APPLIED or SUPEDAPPLIED are selected. If the SUPED operand isspecified, all PTFs with the status SUPED APPLIED areselected. No PTFs met the specified criteria.



VMF2142W The following parts could not be erasedby commit processing because they are{currently the highest level of thepart|build lists that are needed byVMFBLD}: fn ft

Explanation: While committing PTFs, VMFREM couldnot erase all of the parts in the committed PTFs. Thehighest level of a part cannot be erased becauseVMFBLD might need that part to perform the buildfunction. A build list that appears in the unprocessedsection of the select data file cannot be erased becauseVMFBLD needs that part to perform the statusfunction.



VMF2143E VMFREM was requested to remove nservice levels, but only m APPLY disksare defined in the :MDA section ofproduct parameter file fn PPF(compname compname)

Explanation: You have specified a number of servicelevels on the command line that is greater than thenumber of APPLY disks defined in the :MDA section ofthe product parameter file.


User response: Enter the VMFREM command againwith a valid number of service levels.

VMF2144I Removed PTFs have been added toexclude list fn ft fm

Explanation: All PTFs that were un-applied orun-received by VMFREM were added to the specifiedexclude list.


User response: If you wish to apply one of theremoved PTFs, you will need to remove it from theexclude list.

VMF2144W Removed PTFs could not be added toexclude list fn ft fm.

Explanation: The specified exclude list could not beupdated by VMFREM.


User response: You should manually add theun-applied and un-received PTFs to the exclude list orremove them from the apply list.


VMF2145I The following parts could not be erasedby unreceive processing because theyare build lists that are needed byVMFBLDfn ft

Explanation: While removing local modifications,VMFREM could not erase all of the parts because oneor more of the parts is a build list.

A build list that appears in the unprocessed section ofthe select data file cannot be erased because VMFBLDrequires that part to perform the status function.



VMF2150E The {TAPE|ENVELOPE} is not in the{service|installation} format expected byVMSES/E. The format of the{TAPE|ENVELOPE} is format.

Explanation: VMSES/E can process envelopes andtapes in either installation or service format. The formator contents of the tape or envelope being processeddoes not match the format specified in the VMSES/Ecommand entered to process it. This is either the wrongtape or envelope, the wrong command was entered toprocess it, or the tape or envelope was not createdcorrectly.

System action: RC = 12. You are prompted to mountthe correct tape, identify the correct envelope, or to exitfrom this command.

User response:

v If this is the wrong tape or envelope, then mount thecorrect tape or identify the correct envelope, andcontinue processing.

v If you entered the wrong command for this type oftape or envelope, enter 0 to Exit, and enter thecorrect command.

If you are processing an RSU the correct command touse is VMFINS.

If you are processing CORrective service the correctcommand to use is VMFREC.

v If the correct tape or envelope was used and thecorrect command was used then the tape or envelopeis probably faulty. Enter 0 to exit, and then re-orderthe tape or envelope or contact the IBM SupportCenter.

VMF2151E The number (tapenum1) of the currentTAPE does not match the number(tapenum2) of the previous TAPE

Explanation: The tape currently mounted is not one ofthe volumes from the set of tapes being processed.

System action: RC = 12. You will be prompted tomount the correct tape.

User response: Respond to the prompt.

VMF2152E The descriptor file (fn ft) on the currentTAPE {does not match the previousTAPE|contains invalid records}

Explanation: It has already been determined that thetape mounted is a volume from the set of tapes beingprocessed, but the descriptor files do not match. Or,there are records that are not valid in the descriptorfile. The tape was built incorrectly.


User response: Contact the IBM Support Center toreport the problem and order a new tape.

VMF2153E The time stamp (timestamp) on thecurrent TAPE does not match the timestamp (timestamp) on the previous TAPE

Explanation: The tape currently mounted is not one ofthe volumes from the set of tapes being processed.

System action: RC = 12. You will be prompted tomount the correct tape.


VMF2154E There are no files for {prodid|ppfnamecompname} on this {TAPE|ENVELOPE}

Explanation: The product/component that youspecified could not be found on the current tape orenvelope.


User response: Ensure that you specified the correctproduct/component. You can issue VMFREC orVMFINS with the INFO function to get a list of theproducts/components on the tape or envelope.

VMF2155I Files for {prodid|ppfname compname}{begin|continue} on volume n

Explanation: This message identifies the correct tapeto mount.

System action: You will be prompted to mount thecorrect volume.


VMF2156E There are only n header file(s) forppfname

Explanation: You specified an invalid header filenumber.



User response: Reissue the command using a validheader file number.



VMF2157E The product contents directory (fn ft) onthe current TAPE does not match theprevious TAPE

Explanation: It has already been determined that thetape mounted is a volume from the set of tapes beingprocessed, but the product contents directories do notmatch. The tape was built incorrectly.



VMF2158R messages


v Mount correct volume and enter one (1) to continueor zero (0) to quit

v Enter correct envelope name or zero (0) to quit

A new tape volume must be mounted, or a newenvelope name must be specified,


If you enter 0, command processing stops with a returncode of 500. If you enter 1 and are using tapes,command processing continues. If you are usingenvelopes, specify the new envelope name.

User response: Refer to the previous message todetermine which tape volume to mount or whichenvelope name to enter

VMF2159I messages


v {Loading|Loaded} n part(s) to [string] {vdev|dirid}(fm)

v Loading fn ft to [string] {vdev|dirid} (fm)

The specified files will be loaded from the tape orenvelope.



VMF2160I There are n tape files for {prodid|ppfnamecompname} on volume m

Explanation: This message identifies which productsare present on the tape (all volumes) or envelope beingprocessed.


User response: You can use this information to planwhich products/components you are going to install orservice.

VMF2162E The component name (compname1) onthe command line does not match thecomponent name (compname2) in productparameter file fn ft

Explanation: You have entered the wrong componentname.

System action: RC=12. Command processing stopsdue to the internal error.

User response: Use the specified product parameterfile to identify the correct component name and enterthe command again.

VMF2170E fn ft is not a format n build list

Explanation: Each VMFBLD part handler processes acertain build list format. When the build list specifiedfor a part handler is not in the correct format, the parthandler cannot process it. The message identifies thebuild list format that the part handler requires.



User response: Correct the syntax of the build list orproduct parameter file, and reissue the command.

VMF2172E messages


v An invalid entry was found on line n of build listfn ft.

v An invalid entry was found on line n of build listfn ft. A tag tag may be missing

v An invalid entry was found on line n of build listfn ft. Valid tags in this position are: tags

v An invalid entry was found on line n of build listfn ft. There is extraneous data on a tag tag

v An invalid entry was found on line n of build listfn ft. The tag tag must appear on a new line

The specified build list was found to be in error on thegiven line number. If a specific tag is missing, it islisted in the message. If only a specific set of tags arepermitted on this line, the complete set of valid tags isprovided. Each build list tag must begin on a new lineand must consist of a beginning colon, the tag name,and an ending period. For example:

:PARTID.


User response: Correct the syntax of the build list,and enter the command again.



VMF2173I messages


v Executing build exec fn

v Executing verification exec fn

v No verification exec found for this product

Some products provide build or verification execs orboth. If the product being processed provides them,this message indicates when either is run. Otherwise,this message indicates that no verification exec wasprovided.

Explanation:



VMF2177E The FASTPATH option was specified forthe fn build list, but the fn $NUCEXECfile could not be found on any accesseddisk

Explanation: The FASTPATH option requires that abuild list named fn $NUCEXEC be available. This is thefile that contains resolved build list entries so thatfurther processing can be bypassed.



User response: Find, rename or create the appropriateload list and reissue the command; or, rerun theprocedure without specifying the FASTPATH option.

VMF2178I Object objname cannot be rebuilt because{it is not serviced|no parts were found}

Explanation: The object specified to be built containsan asterisk (*) as the file name in the :PARTID entry inthe build list. If the VMFBLD ALL option wasspecified, the object could only be built if it wereserviced. If the VMFBLD WILD option was specified,the object could only be built if matching serviced orbase parts were found. It is not known what parts arerequired to build this object. Because the base level ofthis object must already exist, the object will be given astatus of BUILT.


User response: This message is for information only.

VMF2179I There are no build requirementsmatching your request at this time. Noobjects will be built

Explanation: The SERVICED option was specified, butnone of the selected objects were serviced, so no objectswere built.


User response: This message is for information only. Ifyou wish to build an object regardless of its servicestatus, use the ALL option. However, one case whenthe ALL option still will not build the object is whenthe object contains an asterisk (*) as a :PARTID entry inthe build list, and that object has never been serviced.

VMF2180I messages


v There are n build requirements remaining

v Build Requirements:

Bldlist Object Statusbldlist object status [Partids]

The service-level build status table contains the list ofbuild requirements. On each invocation of VMFBLD,this message is issued just prior to completion to notifyyou of any remaining build requirements. The secondformat of this message identifies each of theserequirements, but is only included in the build messagelog ($VMFBLD $MSGLOG). Use VMFVIEW to view themessage log for these details. You can also useVMFQOBJ to query the status (and other details) of aspecific object. Objects that are serviced within abypassed build list are not considered buildrequirements.

There is a special object with a build list name ofUNKNOWN and an object name of BLDLIST for anyserviceable parts that are not included in any object.These parts are assigned a status of MANUAL becausethey must be processed manually. The parts are listedin the second format of this message. A part may alsobe assigned a status of MANUAL due to one of thefollowing error situations.

v A PTF or a local modification introduced a new partwithout adding the part to a build list.

v A PTF or a local modification inadvertentlyintroduced a new part by not matching the file nameand file type abbreviation data on the :PARTID tag inthe build list.

v A local modification incorrectly added a select data($SELECT) file entry for the part.


User response: If there are any build requirements,follow the service procedures to build the affectedobjects. If there are any parts with a status ofMANUAL, perform the manual processing, or correctthe error if caused by a local modification, or report theerror to the IBM Support Center if caused by a PTF.Use the VMFUPDAT command or the VMFSIMMODIFY command to update the status to BUILT. Formore information on how to use the VMFSIM MODIFYcommand to update the status, refer to z/VM: VMSES/EIntroduction and Reference.



VMF2181E The primary Apply identifier (appid) onthe :APPID tag in product parameter filefn2 PPF (compname compname) mustappear as an Apply identifier on the:LASTAPP tag in Build Status table fn1SRVBLDS

Explanation: The apply identifier defines the name ofthe select data file. It is specified in both the productparameter file and the Build Status table. The firstapply identifier in the product parameter must appearin the Build Status table.


User response: Correct the :APPID tag in the productparameter file or the :LASTAPP tag in the Build Statustable and enter the command again.

VMF2182I messages


v Identifying new build requirements

v New build requirements identified

v No new build requirements identified

Each time VMFBLD is invoked it identifies any newbuild requirements. A build requirement exists for anobject if any of the following criteria are met:

v any of the parts included in it are serviced

v its definition is serviced in the build list

v it is specified on the VMFBLD command line withthe ALL option

v it has a build requisite for another object that meetsany of these criteria.

When new build requirements are identified, they arelisted in the service-level build status table. Regardlessof whether new build requirements are found or not,this message is issued to notify you when this portionof VMFBLD processing begins and completes.



VMF2183E prodid can only be received withthe{PPF|PROD} operand because it issupported by a product {exec|parameterfile}

Explanation: The keyword operand (either PPF orPROD) does not match the type of support providedfor the specified product. The tape or envelope definesthe type of support in the 7th character of the programlevel file (sometimes referred to as the CRLLNNF file).If this character is ‘1’, a product parameter file is used.If it is ‘0’ or blank, a product exec is used.



User response: Reissue the command with the correctoperand.

VMF2184E This program requires a string disk

Explanation: At least 1 disk in the specified string isrequired because it is a target of the Software Inventoryfiles.


Command processing stops because of the target notavailable condition.

User response: Correct the :MDA section of theproduct parameter file and reissue the command.

VMF2185R The following source product parameterfiles have been serviced: fn $PPF Whensource product parameter files areserviced, all product parameter filesbuilt from them must be recompiledusing VMFPPF before VMFBLD can berun. Enter zero (0) to have the latestlevels of the source product parameterfiles copied to your A-disk and exitVMFBLD so you can recompile yourproduct parameter files with VMFPPFEnter one (1) to continue only if youhave already recompiled your productparameter files with VMFPPF

Explanation: The :BLD section of the productparameter file contains the master list of build lists.When the product parameter source file is serviced, thismaster list can change making it necessary to update itprior to running VMFBLD.


If you enter 0, the latest level of the product parametersource file is copied to your A-disk and then commandprocessing stops with a return code of 500. If you enter1, command processing continues.

User response: If you have not rebuilt your productparameter file, you must do so now.

VMF2186W There are no message blocks in fn$MSGLOG [for{RECID|APPID|BLDID}{prodid|appid|bldid}]

Explanation: When VMFVIEW is invoked, it searchesthe specified log for the appropriate blocks of messagesto be displayed. This message is issued when:

v There are no valid message blocks in the log.

v There are no valid message blocks that match thesearch criteria from the product parameter file (ifspecified).



For Install, Receive, and Merge the RECID is the searchkey. For Apply, the APPID is the search key, and forBuild, the BLDID is the search key.

System action: RC = 4. No log is displayed.

User response: If using a product parameter file,investigate why the identifier from the productparameter file does not match the identifier from themessage log. To view the entire message log, issueVMFVIEW with the ALL option and no productparameter file.

VMF2187E Syntax error on line n of VMFVIEW$PROFILE

Explanation: The VMFVIEW$ PROFILE is not valid.



User response: Correct the syntax of VMFVIEW$PROFILE and reissue the command.

VMF2188I Building fn ft1 on string {vdev|dirid} (fm)from level ft2

Explanation: The specified file will be built at thegiven level.



VMF2189I Updating Requisite table prodidSRVREQT, Description table prodidSRVDESCT and Receive Status tableprodid SRVRECS with n PTFs from tapeidentifier

Explanation: The tape or envelope contains PTF thatwere not previously received or committed to yoursystem. These PTFs have been received and will nowbe added to your Software Inventory.



VMF2190E messages.


v Missing file type abbreviations for build list fn ft inproduct parameter file ppfname PPF (compnamecompname)

v Invalid file type abbreviation ftabbrev for build listfn ft in product parameter file ppfname PPF(compname compname)

v Missing file type abbreviations for part partfn inobject object in build list fn ft

v Invalid file type abbreviation ftabbrev for part partfnin object object in build list fn ft

Serviceable parts are uniquely identified by their filename and file type abbreviation. For format 1 buildlists, the file type abbreviations are specified in the:BLD section of the product parameter file. For format 2and 3 build lists, they are specified on :PARTID tagswithin the build lists. At least one file type abbreviationmust be specified for each part. More than one file typeabbreviation may be specified if the part has more thanone version. File type abbreviations are listed in thesystem abbreviation table (VM SYSABRVT) and in the:DABBV section of the product parameter file.

Some build part handlers allow only certain file typeabbreviations. For example, the VMFBDMLB parthandler only allows file type abbreviations thattranslate into the real file types MACRO and COPY,and the VMFBDTLB part handler only allows parts filetype abbreviations that translate into the real file typeTEXT.

If the part is serviced strictly by updates (i.e. noreplacement parts are shipped), the file typeabbreviation is actually the full file type of the sourcepart. If the NOGETLVL part option is specified for thepart, the file type abbreviation is actually the real filetype of part to be included in the object. When theNOGETLVL part option is specified, only one file typemay be specified.

System action: RC = 12. Command processing stopsdue to the internal error.

User response: Correct the syntax of the productparameter file or build list, and reissue the command.

VMF2191W Message number nnnn was not found; itwas issued from routine in applicationapplid

Explanation: The message requested could not befound in the specified repository.



User response: Verify the command and reissue it.

VMF2192E The component name (compname) islisted in tape descriptor file fn1 ft1 butdoes not appear in product contentsdirectory fn2 ft2

Explanation: The tape descriptor file lists all of theproducts and components on the current tape orenvelope. The product contents directory lists all of thecomponents for the specified products. If these 2 filesdo not match, the tape was built incorrectly.




VMF2193I Appending new {Apply|Exclude} list fn{$APPLIST|$EXCLIST} to the existinglist on string {vdev|dirid} (fm)

Explanation: When the APPEND option of VMFRECis used the existing Apply and Exclude lists on thetarget disk (if present) are appended to the new onesthat are received from the current tape or envelope.This feature is useful when receiving multiple servicetapes, because it allows you to receive all of the tapesand perform a single apply step.



VMF2195I command

Explanation: The complete command syntax of thecommand issued is echoed into the $MSGLOG.


User response: Review the $MSGLOG.

VMF2196W The FASTPATH option will be ignoredbecause fn $NUCEXEC fm containsentries for patched text decks

Explanation: The FASTPATH option was specifiedindicating that the loader should use the text deckentries from the previous nucleus build. Thisinformation is contained in the load list fn $NUCEXEC.One or more of the text files in this load list wereserviced using the patch facility. Patched text decks arecreated temporarily during VMFBLD processing, anddo not exist on subsequent VMFBLD invocations. TheFASTPATH option must be ignored to allow the loadlist and any patched text decks to be created.



VMF2197I An entry that was not valid was foundin a prior level of build list build_list.All objects in the latest level of thisbuild list, filename filetype, will be built

Explanation: When a build list is serviced, VMFBLDcompares the latest level to the previous level of thebuild list to determine if object definitions havechanged. If an object definition changes, that objectmust be built. This comparison could not be donebecause an error was found in the prior level of thebuild list. We must build all objects in the latest level ofthe build list because we are unable to determinewhich object definitions have changed.



VMF2198E The {ASTEM|STEM} {operand|option}is only valid when issued from an exec

Explanation: Stems can only exist in an execenvironment. The command was issued with no activeexec environment.



VMF2199E messages


v Object object in build list fn ft cannot be builtbecause part fn ft on disk|directory (pfm) may not beat the correct level

v The object created by build list fn ft cannot be builtbecause part fn ft on disk|directory (pfm) may not beat the correct level

VMFSIM GETLVL has indicated that the base level ofthe specified part is the level required to build thelisted object. This base level part was found, but not onthe BASE string. Since it was not on the BASE string, itis not known whether this is indeed the correct baselevel part and therefore cannot be used.


Command processing continues with the next object.

User response: Ensure you have the correct accessorder. If the file indicated is indeed the correct baselevel part, it should be moved to the BASE string usingVMFCOPY. Otherwise, this file should be erased orrenamed.

VMF2200E var is an invalid variable in the :DCLsection of the product parameter file fnft

Explanation: A variable was found that does notbegin with a ‘&’.


User response: Correct the product parameter file thatcontains the variable name given and enter thecommand again. The name of the product parameterfile given in the message is the temporary productparameter file created as a result of runningVMFOVER. If that file is created using override files,the variable definition you are looking for may be in afile with a file name other than the one given in themessage.



VMF2201E An undefined variable var was found inthe product parameter file fn ft

Explanation: A variable was found in the productparameter file that was not defined in the DCL sectionof the product parameter file.


User response: Define the variable in the :DCL sectionof the product parameter file and enter the commandagain.

VMF2202E Invalid syntax was used to definevariable var1 in the product parameterfile fn ft

Explanation: A variable was not defined correctly inthe DCL section of the product parameter file.



VMF2203E The file SETUP $LINKS which containsany LINKS issued by VMFSETUP wasnot found. No DETACH commands wereissued

Explanation: The file SETUP $LINKS is required asinput to VMFSETUP for the DETACH function. The fileis erased for each logon session.



User response: If the file does not exist it is becauseVMFSETUP has not been called for this logon session.No user action is required.

VMF2204I Linking owner owner_vdev [as link_vdev]with link mode mode

Explanation: The minidisk cited in the message isbeing linked to, as indicated.



VMF2205I Minidisk|Directory Assignments:messages

Explanation: This message identifies the current accessorder.String Mode Stat Vdev Label (OwnerID Odev : Cyl/%Used)

-or- SFS Directory Namestring mode stat vdev label {(ownerID odev : nnnn/pp) | sfs-dir}

string is the name of a symbolic disk string, asdefined in a product parameter file (PPF). If

this field is left blank, the minidisk or SharedFile System (SFS) directory cited is part of thesame string as the previously-listed minidiskor directory. If this field is filled with dashes,the minidisk or directory is not part of anydefined disk string.

mode is the file mode letter at which the minidisk ordirectory is accessed. If this field is filled withdashes, the minidisk or directory is notaccessed.

stat is the status of the minidisk or directory: R/O(read-only) or R/W (read/write). If this field isfilled with dashes, the minidisk or directory isnot accessed.

vdev is the virtual device number of a minidisk, or'DIR', if the entry is an SFS directory. If thedirectory has the directory control(DIRCONTROL) attribute, 'DIRC' is displayedinstead of 'DIR'.

label is the label assigned to a formatted CMS disk.If the entry is an OS or DOS disk, this is thevolume label.

ownerID odev : nnnn/ppis additional disk information that is providedwith minidisk entries only, where:

ownerIDidentifies the user ID that owns thelisted disk.

odev is the owner's virtual device numberfor this disk.

nnnn is the number of cylinders availableon the disk.

pp is the percentage of disk blocks inuse.

sfs-dir is the complete name of an SFS directory.



VMF2206W Modes A, B, C, and D are reserved forVMSES/E. The minidisks or directoryIDs at these modes should not bespecified in the PPF. This conflict existsfor minidisk or directory ID {disk|dirid}(filemode) specified in product parameterfile ppfname PPF

Explanation: Minidisks or directory IDs used byVMSES/E are specified in the product parameter file.


User response: The VMSES/E Test Build or Build diskmust be accessed as the B-disk. Mode D is reserved forthe System Software Inventory. The disks accessed as Aand C are work disks. Minidisks or directory IDs at



these modes should not appear in the :MDA section ofthe product parameter file.

VMF2207I Copying part fn ft on disk|directory (fm)to the A-disk

Explanation: VMFSIM GETLVL has indicated that thebase level of the specified part is the level required.However, a file with the same name exists on a higheraccess disk|directory than the BASE string. Since wedo not know what level this other part is at, the file onthe BASE disk will be copied to the A-disk to ensurethat this version will be used.



User response: Ensure you have the correct accessorder and issue VMFSETUP if not. Examine the fileslisted and determine why they are on a disk that isaccessed ahead of the BASE string. If they are not basefiles they should be erased or renamed. If they are thecorrect base files, use VMFCOPY to move them to theBASE string if need be.

VMF2208I Parts had to be copied to the A-disk. Donot use the FASTPATH option forsubsequent nucleus builds with buildlist fn ft

Explanation: VMFSIM GETLVL indicated that the baselevel of one or more parts was required in generatingthe nucleus. To prevent the loader from using files withthe same specifications that were not on the base string,the base files were temporarily placed on the A-disk. Ifthe FASTPATH option were selected, however, thisoperation would not take place and incorrect levels ofparts might be used in generating the nucleus.



User response: Ensure you have the correct accessorder and issue VMFSETUP if not. Examine the fileslisted and determine why they are on a disk that isaccessed ahead of the BASE string. If they are not basefiles they should be erased or renamed. If they are thecorrect base files, use VMFCOPY to move them to theBASE string if need be.

VMF2209E The FASTPATH option cannot be usedbecause the existing load list fn ftconflicts with NUCTARG nuctarg

Explanation: The existing load list was created duringa previous invocation of VMFBLD, and is being useddue to the selection of the FASTPATH option. Theloader control card in this file, however, is in conflictwith the nucleus target location specified on theNUCTARG option. If NUCTARG MODULE isspecified, the value in this record must beHCPLODNC. If any other value is specified on the

NUCTARG option, the value in this record must beHCPGENUC.


Processing terminates.

User response: If the NUCTARG value requested iscorrect, invoke VMFBLD without specifying theFASTPATH option. This will cause a new load list to begenerated with the correct loader control card. If youdo wish to use the FASTPATH option, eliminate theimplementation of the NUCTARG option or change itto match the existing load list as described above.

VMF2210E messages


v Invalid part name [fn] on :PARTID tag in object objin build list fn ft

v Invalid part name [fn] on line n in build list fn ft

v Invalid part type [ft] on line n in build list fn ft

There is an invalid or missing part name (or type)specified at the given location in the build list.

In format 1 build lists, part names and part types mustbe valid CMS file names and file types.

In format 2 and 3 build lists, the :PARTID tag mustcontain either a valid CMS file name or an asterisk (*)if it appears in a wildcard object. Wildcard objects areonly valid in format 2 build lists. In VM/ESA Version 1Release 2 the file name of a wildcard object must be anequal sign (=).


User response: Correct the syntax of the build list,and reissue the command.

VMF2211E messages


v Invalid object name object on :OBJNAME tag inbuild list fn ft

v Invalid requisite object name object on :GBLDREQtag in build list fn ft

v Invalid requisite object name object on :BLDREQtag in object object in build list fn ft

v Invalid requisite object name object for build list fnft in :BLD section of product parameter file fn2 PPF(compname compname)

There is an invalid object name specified at the givenlocation in the build list or product parameter file.

The only valid object name for format 1 build lists isBLDLIST. In format 2 build lists, the object name is acombination of the object file name and the object file



type joined by a period (for example, filename.filetype).The object file name can be any valid CMS file name,except BLDLIST or an equal sign (=) for a wildcardobject. The object file type can be any valid CMS filetype. The VMFBDMOD part handler requires the objectfile type to be MODULE. In format 3 build lists, theobject name is the member name in a library. The objectname can be any valid CMS file name, exceptBLDLIST.

Format 2 build lists do not include the object file typein products packaged for VMSES/E levels prior toVM/ESA Version 1 Release 2.



VMF2212E messages


v Invalid requisite build list name bldlist on:GBLDREQ tag in build list fn ft

v Invalid requisite build list name bldlist on:BLDREQ tag in object object in build list fn ft

v Invalid requisite build list name [bldlist] for buildlist fn ft in :BLD section of product parameter filefn2 PPF (compname compname)

v Invalid build list name bldlist in :BLD section ofproduct parameter file fn2 PPF (compnamecompname)

There is an invalid build list name specified at thegiven location in the build list or product parameterfile. A build list name can be any valid CMS file nameother than UNKNOWN.




VMF2213E A :EOBJNAME tag is missing for objectobject in build list fn ft

Explanation: In a format 2 or 3 build list, each objectmust end with a :EOBJNAME tag.




VMF2214E messages


v Missing :PARTID tags {for object object } in buildlist fn ft

v Multiple :PARTID tags {for object object } in buildlist fn ft

v There are no parts specified in build list fn ft

v Multiple object tags specified in build list fn ft

In general, objects in format 2 and 3 build lists mayhave zero or more :PARTID tags per object block. Manypart handlers further restrict this by requiring at leastone :PARTID tag per object block and/or limiting eachobject block to only one :PARTID tag. All format 1 parthandlers require at least one part to be specified in thebuild list.

Wildcard objects in format 2 build lists must containexactly one :PARTID tag.

A build list to build a Callable Services Library maycontain exactly one :OBJECT tag.




VMF2215E messages


v Missing value for build list option option for buildlist fn ft

v Missing value for object parameter parm for objectobject in build list fn ft

v Missing value for part option option for object objectin build list fn ft

v Invalid build list option option for build list fn ft

v Invalid object parameter parm for object object inbuild list fn ft

v Invalid part option option for object object in buildlist fn ft

v Invalid value value for build list option option forbuild list fn ft

v Invalid value value for object parameter parm forobject object in build list fn ft

v Invalid value value for part option option for objectobject in build list fn ft

v Missing keyword keyword for object parameter parmfor object object in build list fn ft

v Invalid library parameter parm in build list fn ft

v Missing value for library parameter parm in buildlist fn ft



v Invalid value value for library parameter parm forbuild list fn ft

The given parameter or option is not valid for thespecified part handler, or a required keyword for anobject parameter has not been supplied.

Build list options can be specified after the parenthesesin records in the :BLD section of the product parameterfile and after the object specification on the VMFBLDcommand invocation. Build list options are generallyoperands or options (or both) of the primitives used tobuild objects.

Object parameters are specified after the object nameon the :OBJNAME tag in format 2 and 3 build lists.Object parameters are generally operands or options (orboth) of the primitives used to build objects.

Library parameters are specified after the library nameon the :LIBNAME tag in format 3 build lists. Libraryparameters are used to specify optional methods ofbuilding a library.

In format 1 build lists, part options are specified afterthe parentheses on each part record. In format 2 and 3build lists, part options are specified on :OPTIONS tagswithin object blocks. Part options are generally optionsof the primitives used to build objects. Part options alsoinclude the capability to specify language specific parts.


User response: Correct the syntax of the build list,product parameter file, or VMFBLD commandinvocation, and enter the command again.

VMF2216E Invalid library {name|type}{libname|libtype} on the{:GLOBAL|:GGLOBAL} tag [in objectobject] in build list fn ft

Explanation: There is an invalid library type specifiedat the given location in the build list. The valid librarytypes are CSLLIB, DOSLIB, LOADLIB, MACLIB, andTXTLIB.




VMF2217I messages


v library_name library_type will be rebuilt because noexisting version can be found

v library_name library_type will be rebuilt because allmembers must be rebuilt

v library_name library_type will be rebuilt in order todelete members

v library_name library_type will be rebuilt becauserequired_filename required_filetype cannot be found

The subject library will be generated using informationin the build list because of the reason specified. Onlysome libraries must be generated when objects(members) need to be deleted (for example, MACLIBs).



VMF2218I messages


v libname libtype is now empty and will be erasedfrom string {vdev|dirid} (fm)

v libname libtype is now empty. fn ft will be erasedfrom string {vdev|dirid} (fm)


v The last member was deleted from the specifiedlibrary.

v An attempt was made to generate the library, but nomembers were specified in the build list.


The specified library or file is erased from the targetdisk.


VMF2219I Processing object object

Explanation: The specified object has been selected forprocessing by the part handler.



VMF2220I Updating service history member forlibname libtype

Explanation: The library member containing theservice history for this entity is being created orupdated and will be included within the library.





VMF2221W Build requisite rbfn.reqobject for [objectobject] in build list fn does not exist

Explanation: The specified object has a requisite for anobject which is not defined in any build list. Therequisite may have been specified improperly, or it mayhave been deleted without removing the pointer to it.




VMF2222E messages


v Object object is defined more than once in build listfn ft

v Object object is not defined in build list fn ft

Objects must be unique within a build list. If an objectis specified more than once, the first version of thismessage is issued.

If an object is identified as belonging to a build list andit does not, the second version of this message isissued.

The reserved object name BLDLIST is used to representthe build list as an entity. This is the only valid namethat can be used to reference the single object createdby a format 1 build list.




VMF2223E Control file ctlfn contains the followinginvalid record: invalid_record

Explanation: The specified record is not a validcomment record, AUX record, or MACs record.



User response: Correct the syntax of the control file,and reissue the command.

VMF2224E messages


v The language translation by langfunc failed for fnftabbrev

v The language translation by langfunc failed for fnftabbrev because the language code language_code isnot defined

v The language translation by langfunc failed for fnftabbrev because the resulting file type abbreviationlfta is not a valid file specification

v The language translation by langfunc failed for fnftabbrev because the resulting file name lfn is not avalid file specification

v The language translation by langfunc failed for fnftabbrev because no result was returned

The language function langfunc was called for theserviceable part fn ftabbrev, and this functionencountered problems.

System action: RC = 12. Command processing stopsbecause of the failure.

User response: The language functions are calledduring VMFBLD processing for all serviceable partsthat are language sensitive. The LANG option in format1 build lists and the LANGFUNC option in format 2and 3 build lists identify the language sensitive parts.Check the build lists that contain fn ftabbrev. Use theVMFQOBJ command to identify these build lists.

VMF2225E A requisite loop has been detectedprocessing {object|PTF} {object|ptfnum}[in build list fn ft]

Explanation: The specified object or PTF, or one of itsrequisites, is identifying the specified object or PTF asits requisite. This is not a valid state.



User response: Correct the build or PTF requisites,and reissue the command.

VMF2226E messages


v Output stem OUTLIST. from part handler fn wasnot initialized properly

v Invalid object name object in record n of outputstem OUTLIST. from part handler fn

v Invalid object status status in record n of outputstem OUTLIST. from part handler fn

When VMFBLD part handlers change the status of anobject, the new status is communicated to VMFBLD ina stem named OUTLIST. This message indicates thatVMFBLD has found the contents of this stem to beinvalid when returned from the specified part handler.The results of the part handler are not recorded in theservice-level build status table.


Command processing continues bypassing the failingsub-function.



User response: Correct the code in the specified parthandler, and reissue the command.

VMF2227W Object object in build list bldlist cannotbe deleted because its file specificationsare unknown

Explanation: The definition of the specified object hasbeen removed from its build list. When this occurs, thecorresponding object should be erased from yoursystem. Because of one of the following two reasons,the object could not be erased:

v The object is a wildcard object. Wildcard objectscontain wildcard parts (parts whose names aredefined as asterisks). Wildcard objects by definitioncannot be deleted because a complete list of theobjects included in the object definition is notavailable.

v The version tag in the PPF indicates that objectdeletion is not supported for this object. Objectdeletion is not supported by the VMFBDCOM parthandler for products packaged for VMSES/E levelsprior to VM/ESA Version 1 Release 2.

The object is flagged as DELETED in the service-levelbuild status table even though the object may still existon your system.



VMF2228E messages


v Part handler fn is not supported beyond VM/ESA1.1.1

v Part handler fn is not supported until VM/ESA 1.2.0

v Part handler fn is not supported until VM/ESA 1.2.1

v Part handler fn with option option is not supporteduntil VM/ESA 2.1.0

v Part handler fn is supported on only z/VM n.n.n orlater

A part handler was invoked with function that is eithernot supported by the level of VMSES/E indicated onthe :VERSION tag in the PPF or by the current level ofCMS.

System action: RC=12. Command processing stopsdue to the internal error.

User response:

v If you created your own PPF, check the :VERSIONtag, and update it if necessary.

v Make sure the level of VMSES/E matches the levelof CMS running on your system.

v If the levels of VMSES/E and CMS match, and thePPF was shipped from IBM, contact the IBM SupportCenter.

VMF2229I messages


v Library search order changed for object object:

libtype libnames

v Library search order restored by program:

libtype libnames

The CMS library environment has been changed by theprogram currently executing, or restored to the valuesset upon entry to this program. The library types andnames are identified on subsequent lines as necessary.



VMF2230E messages


v Invalid option (valid options listed above)

v Invalid selection (valid selections listed above)

v Conflicting options

v Invalid option. Valid options are NOSetup orSETup

The option or selection entered was not a valid value.


User response: Enter a valid value.

VMF2231I messages


v PPF file name must be entered

v Component name must be entered

v Setup must be specified

v System name must be entered

v PTF/APAR number must be entered

v Build list/Object/Part file name must be entered

v Table file name/file type must be entered

A value for the listed field(s) must be entered tocontinue processing.


User response: Enter a value for the listed field.


VMF2232E messages


v Only num item(s) may be selected

v Only one field may be specified

As indicated, the number of fields or items that can beselected is limited.


User response: Select only one field or the maximumnumber of items indicated.

VMF2233E messages


v No component names found in ppfname ppftype disk(ppfmode).

The specified product parameter file (PPF) does nothave any :COMPLST or :OVERLST tags, or nocomponents are specified on the tags.

v Component name compname not found in PPFppfname ppftype ppfmode (disk_address).

The component name specified on the command wasnot found in the product parameter file (PPF)specified.

System action: RC = 12 or 100. Command processingterminates because there are no components to process.

User response: Correct the file, or specify a file thatcontains one or more of the tags with components.

VMF2233I messages


v PPF ppfname PPF fm not found

v Component name compname not found in PPFppfname PPF fm

v No PPFs found

v No component name found in PPF ppfname PPF fm

v Table filename filetype not found. Query cancelled

v Invalid system value. Table system SYSABRVT notfound

The item specified did not exist on any accessed disk.


User response: Enter a valid PPF file name,component name, or table name.

VMF2234E Invalid [PTF | APAR] syntax. Prefixmust be alphabetic, suffix must be allnumeric

Explanation: The PTF/APAR number entered was notin the correct format.


User response: Enter a valid PTF/APAR.

VMF2234I [PTF ptfnum | APAR aparnum] has notbeen received.

Explanation: The PTF/APAR number entered did notexist.


User response: Enter a valid PTF/APAR.

VMF2235E Object [object | file type objft] is not avalid CMS file name

Explanation: The value for the item specified was nota valid CMS file name.


User response: Enter a valid CMS file name for theitem.

VMF2236I messages


v Build list bldlist not found

v Part/abbrev partfn partfta not found in build listbldlist

v Object object not found in build list bldlist

v Object object not found in any build list

v Part partfn not found in object object

v Part partfn with abbrev partfta was not found

v Part partfn not found in any object

v Object object not found with part partfn partfta

v Object object not found with part abbrev partfta

v Abbrev partfta not found in object object

The item specified was not found.


User response: Enter an existing value.

VMF2237I File type [abbreviation fileabbv | filetype]not found in abbreviation table

Explanation: The file abbreviation specified was notfound.


User response: Enter an existing value.

VMF2238I Query output saved to file filenamefiletype

Explanation: The query results were successfullysaved.





VMF2239E Invalid value specified. Setup may onlybe YES or NO

Explanation: The specified value for setup wasinvalid. Only YES or NO is valid.


User response: Enter YES or NO.

VMF2239I messages


v Setup was not performed. Query results may beinvalid

v Setup did not complete successfully. Query resultsmay be invalid

Setup was not done. The environment may not includenecessary tables.


User response: Change the setup value if a setup isrequired.

VMF2240E There are no {PTFs/APARs|parts|component names}specified in fn ft fm

Explanation: No PTFs, APARs, parts, or componentnames were found in file fn ft fm.


User response: Re-enter the command with theappropriate PTFs, APARs, parts, or component nameslisted in the specified file.

VMF2240I messages


v There are no common tags. The comparison cannotbe performed

v There are no build lists specified in ppffn PPF ppffm

v There are no objects specified in build list bldlist

v There are no parts specified in object object in buildlist bldlist

v There are no parts specified in build list bldlist

The requested data does not exist.



VMF2241I There is no help for this panel

Explanation: Help does not exist for the panelspecified.


User response: None

VMF2242E messages


v Invalid input. Data cannot contain a blank

v Invalid input. Valid special characters are '$#@_-+:'

v Invalid input. An '*' is not valid for this field

v Invalid input: data

The specified input contained characters that were notvalid.


User response: Enter a valid value for the item.

VMF2243E No generation routine was specified forobject object in build list fn ft

Explanation: The module issuing this messagerequires that the name of the EXEC to be used togenerate this object be supplied as an object parameter.This information is provided using the GENPARMSand EGENPARMS keywords. This information may besupplied for all objects in a build list by using the:GOBJPARM tag, or for a specific object by providing iton an :OBJNAME tag following the object name. Sincethe object cannot be generated without thisinformation, it is given a status of ERROR andprocessing continues with the next object.


Command processing continues bypassing the failingobject.

User response: Correct the syntax of the build list andreissue the command.

VMF2244E None of the generation routinesspecified for object object in build list fnft can be located

Explanation: If VMFHLASM or VMFHASM arespecified as the generation routine for an object,VMFBDGEN will ensure that the required CMSfunction is available prior to issuing the command. If itis not available and no additional generation routinewas supplied, the object cannot be built.


Command processing continues bypassing the failingobject.

User response: Check the CMS access order to



determine why the required function could not befound. Correct the build list to use an appropriategeneration routine that is available.

VMF2245I The following command was issued togenerate object object in build list fn ft:command

Explanation: This is the actual command that wasissued to generate the object specified. This messagewill only be placed in the message log if one exists, andwill not appear at the terminal.



VMF2246W Object object in build list fn ft will notbe built because no required parts werefound.

Explanation: No parts were found for the specifiedobject. This could be due to one of the followingreasons:

v the object contains no parts.

v none of the parts were found and build processingwas instructed to ignore missing parts.

At least one part is required to build the object, so theobject cannot be built.

System action: RC=4. This object is not built. Buildprocessing continues with the next object.


VMF2247I fn ft will remain on {vdev|dirid} (fm)

Explanation: A library or file could not be erased orcould not be copied from the current location to thetarget location. It remains at the location specified inthe message. This message is usually used inconjunction with other messages issued by the routinethat detected the condition.


User response: Determine if this file needs to beerased or moved to the target location. Use VMFCOPYto copy the file to the target location. Use VMFERASEto erase the file from the specified location.

VMF2248E :PARTID. tag found after :OPTIONS.value tag in build list fn ft

Explanation: A :PARTID. tag is not allowed followinga :OPTION. tag for an ALIAS or TXTLIB in a CallableServices Library build list. Reasons for this extra:PARTID. tag might be simply that it was includedincorrectly or that an :OPTIONS. tag is missing.



VMF2249W The RETAIN option was specified formode filemode. Minidisk or directory iddirid (filemode) is not accessed in theorder specified by product parameterfile ppfname PPF

Explanation: VMFSETUP was entered with theRETAIN option. The address at the retained mode isalso in the :MDA section, and has changed the CMSaccess order specified by the :MDA section.


User response: The resulting access order may resultin problems. If so, the situation must be corrected.

Possible causes for this situation are:

v Prior to invoking the service tools, an address that isidentified in the PPF was left at a mode that isRETAINED. In this case, RELEASE the retainedmode and enter the VMFSETUP command again.

v The RETAIN function is useful when you want tokeep your local tools disks accessed while usingVMFSETUP. This situation occurs if the addresses ofthe local tools disks conflict with the addresses in thePPF. In this case, change one of the addresses.

v In special situations it may be desirable to changethe CMS access order. If the RETAIN option is usedfor this purpose, it should be done with caution.

VMF2250W The following compname objects havebeen built on string {vdev|dirid} (fm) andshould be copied to your workstation:list

Explanation: The listed workstation objects belongingto the specified product have been updated on thespecified disk.


User response: If you installed this product to aworkstation, replace the corresponding workstationfiles with the updated versions. See the appropriateproduct documentation for the download procedures.

VMF2251I Number of valid service content recordsidentified in file mapfile_ID : nnn

Explanation: The indicated load module map file(mapfile_ID : nnn) was processed to identify applicableservice content (APAR numbers, PTF numbers, andlocal modification identifiers) for inclusion within itsassociated object (a nucleus load module). Uponcompletion of this process, the number of serviceinformation records (possibly zero) cited by thismessage, are identified.





VMF2252I Service content has been included inobject module_file.

Explanation: The build process for the indicatednucleus object (module_file) included — within thissame object — pertinent service update information, inthe form of applicable APAR numbers, PTF numbers,and local modification identifiers. One or more updatesfor this object were identified, with the relevant servicecontent incorporated within that object.



VMF2253E Service content has not been included inobject module_file.

Explanation: The build process for the indicatednucleus object (module_file) attempted to include —within this same object — pertinent service updateinformation, in the form of applicable APAR numbers,PTF numbers, and local modification identifiers.However, one or more significant errors (cited byaccompanying messages) were encountered which haveprevented the inclusion of this information. Althoughthe newly built nucleus is complete with respect toapplied service, embedded information about thatservice is not present.


User response: Refer to accompanying messages todetermine what problems exist, and review theappropriate documentation to identify what actions arenecessary to resolve them. When all problems havebeen resolved, try building the given object again.Alternately, if the lack of object-embedded serviceinformation is acceptable, the newly built nucleus canbe used in its current form.

VMF2253W Service content has not been included inobject module_file.

Explanation: The build process for the indicatednucleus object (module_file) attempted to include —within this same object — pertinent service updateinformation, in the form of applicable APAR numbers,PTF numbers, and local modification identifiers. Eitherno updates for this object were identified, or one ormore errors (cited by accompanying messages) wereencountered which have prevented the inclusion of thisinformation. Although the newly built nucleus iscomplete with respect to applied service, embeddedinformation about that service is not present.


User response: Refer to the accompanying messagesto determine what problems exist, and review theappropriate documentation to identify what actions arenecessary to resolve them. When all problems have

been resolved, try building the given object again.Alternately, if the lack of object-embedded serviceinformation is acceptable, the newly built nucleus canbe used in its current form.

VMF2254W File mapfile_ID contains unrecognizedservice content.Data for these text files has beenignored:text_fn info

Explanation: While processing the indicated loadmodule map file (mapfile_ID) to identify applicableservice content (APAR numbers, PTF numbers, andlocal modification identifiers) for inclusion within itsassociated object (a nucleus load module), theinformation acquired for one or more text parts(indicated in the message) was found to be in a formnot recognized by the system. Information for the listedparts is ignored, and is not included in any resultingnucleus load module.


User response: Review the accompanying messagesfor more information. If the reason for this error is notapparent, save any existing problem information — acopy of the MAP file that pertains to the affected object(nucleus load module), as well as the message log andconsole files associated with this build attempt — andcontact your IBM Support Center personnel forassistance.

VMF2255W File mapfile_ID contains unrecognizedservice content that cannot bemapped to an applicable APAR value inVVT file file_IDThe acquired data that follows has beenignored:update_info

Explanation: While processing the indicated loadmodule map file (mapfile_ID) to identify applicableservice content (APAR numbers, PTF numbers, andlocal modification identifiers) for inclusion within itsassociated object (a nucleus load module), the serviceinformation associated with one or more text updatescould not be mapped to a corresponding APAR valuefrom the listed VVT file (file_ID). Pertinent updateinformation associated with this problem is indicated inthe message. Because a proper VVT APAR value couldnot be acquired for the affected updates, thisinformation is ignored, and is not included in anyresulting nucleus load module.


User response: Review the accompanying messagesfor more information. If the reason for this error is notapparent, save any existing problem information — acopy of the MAP file that pertains to the affected object(nucleus load module), as well as the message log andconsole files associated with this build attempt — and



contact your the IBM Support Center personnel forassistance.

VMF2256W File mapfile_ID contains unexpectedservice contentData for these text files has beenincluded as local modification data:update_info

Explanation: While processing the indicated loadmodule map file (mapfile_ID) to identify applicableservice content (APAR numbers, PTF numbers, andlocal modification identifiers) for inclusion within itsassociated object (a nucleus load module), serviceinformation associated with one or more text updateswas identified, but was not expected to be present.Because the data encountered represents a valid AUXupdate file type, this information is included in anyresulting nucleus load module, but is considered to bea local modification.


User response: Review the accompanying messagesfor more information. The reported unexpected contentcould be present due to the inclusion of third-party(vendor) updates, or perhaps from the use of acircumventive service update. If the reason for thiswarning is not apparent, save any existing probleminformation — a copy of the MAP file that pertains tothe affected object (nucleus load module), as well as themessage log and console files associated with this buildattempt — and contact your the IBM Support Centerpersonnel for assistance.

VMF2271E The CP SET PRODUCT command failedfor product prodid

Explanation: A CP SET PRODUCT command,executed by the SERVICE or PUT2PROD EXEC, failed.The CP SET PRODUCT command was issued inresponse to a VMFINS ENABLE or VMFINS DISABLEcommand.

System action: RC=100. Command processingterminates.

User response: Correct the problem that caused theCP SET PRODUCT command to fail and then rerun theSERVICE or PUT2PROD EXEC. The most likely causeof the CP SET PRODUCT failure is that the user ID didnot have the correct privilege class to execute thecommand.

VMF2300E fn EXEC must be run on a terminal withat least 22 lines and 80 columns

Explanation: The specified command requires aterminal with at least 22 lines and 80 columns.


User response: Rerun the command on the requiredterminal.

VMF2301W messages


v Invalid data data entered for data_description

v Invalid data data entered for 'Component Name'field

v Invalid data data entered for 'PPF name' field

v Invalid data data entered for 'Modid' field

v Invalid data data entered for 'Compname' field

The data entered on the panel is invalid.


User response: Enter valid data on the panel for thedescribed field, and continue.

VMF2302E Error displaying help file fn

Explanation: The specified help file could not bedisplayed.

System action: RC = 8. Panel processing continues.


VMF2303W Undefined PFKey

Explanation: An undefined PF key was pressed.



VMF2304E The Software Inventory Disk (disk) mustbe accessed as fm [with R/W status]

Explanation: The Software Inventory Disk is either notaccessed as the specified file mode or is accessed inread-only mode.


User response: If the message mentions read-write(R/W) status as being required for the SoftwareInventory disk, link this minidisk such that writecapability is established, and then access it using theindicated file mode. Otherwise, ensure the SoftwareInventory disk is accessed at this file mode. Then,re-enter the command.

VMF2305E File SERVICE $RESTART A was notfound

Explanation: The SERVICE EXEC restart file was notfound.


User response: The SERVICE EXEC cannot berestarted. Issue the SERVICE EXEC without using theRESTART operand.


VMF2306W The VMFSUFTB key is not valid afterany data changes

Explanation: The VMFSUFTB key is valid only beforeany data is entered on the Update SYSSUF Table Panel.



VMF2307E PPF for component compname not foundin VM SYSSUF table

Explanation: In the system-level service update facilitytable (VM SYSSUF), either the indicated componentwas not found or a product parameter file for thecomponent was not found.


User response: Confirm that the correct VM SYSSUFtable is available and that the VM SYSSUF table contenthas not been corrupted.

VMF2307W PPF ppffn not found in SYSSUF table

Explanation: The PPF file name that you selected tobe changed in the SYSSUF table was not found in anyrecords.




Explanation:

v Part fn ft has a local modification modid in versionvector vvtft which must be reworked prior tobuilding product prodid.

v Part fn ft which was customized using localmodification modid in version vector vvtft has beenmigrated. It must be reworked prior to buildingproduct prodid.

v Part fn1 ft1 which was customized by beingchanged in place, cannot be migrated to the newdcllabel ({owner address|dirname}) disk. It has beencopied to the A-disk as fn2 ft2. The customizationof this part must be reworked prior to buildingproduct prodid.

v Part fn1 ft1 which was customized by being copiedand changed, has been migrated to the dcllabel({owner address|dirname}) disk as fn2 ft2. Thecustomization of this part must be reworked priorto building product prodid. [See the product exitmessage log exitfn $MSGLOG for reworkinformation.]

v Part fn ft which may have been customized bybeing copied and changed, cannot be migrated tothe dcllabel ({owner address|dirname}) disk because itsfileid is not resolved. The customization of this

part must be reworked prior to building productprodid. [See the product exit message log exitfn$MSGLOG for rework information.]

v Part fn ft may have been customized by beingcopied and changed, but its fileid is not resolved. Ifit was customized, it will be migrated to the ({owneraddress|dirname}) disk [when product prodid2 ismigrated]. The customization of this part must bereworked prior to building product prodid1.

A local modification or customized part requiringrework was encountered while installing service orduring migration, and a record was written to the VMSYSLMOD table. VMFBLD cannot be run, by theVMFSUFIN, SERVICE, or MIGRATE commands, untilthe local modification has been reworked.


User response: Rework the local modification orcustomized part, and update the VM SYSLMOD tableto indicate that the rework is complete. TheVMFUPDAT SYSLMOD command may be used toupdate the VM SYSLMOD table. If no rework isneeded, just update the VM SYSLMOD table to indicatethat the rework is complete.

To rework customized parts:

v If the part was migrated, you must incorporate anychanges found in the uncustomized part on the newrelease into the migrated part. If so specified, there isinformation in the product exit message log to assistyou with the rework. In this case the migrated partmay need to be renamed as well as reworked.

v If a changed in place part was not migrated, youmust incorporate your customizations from the partthat was copied to the A-disk into the part on thenew release.

v If a copied and changed part was not migratedbecause of an unresolved fileid, there may beinformation in the product exit message log to assistyou with the rework. You must determine the file IDof the customized part on the old release andmigrate that part to the new release.

v If a copied and changed part with an unresolved fileID was migrated, you must determine the fileid ofthe customized part on the new release andincorporate any changes found in the uncustomizedpart. If the part is migrated by another product, youcannot complete the rework until that product ismigrated.

There are instances when certain file IDs cannot beresolved by the system, such as when the subject parthas been introduced through product service updates,but the pertinent service has not been applied to thesystem from which the migration is being performed.Such files likely exist on the new system only, and thusmight not require that action be taken to migrate orrework the customization of those parts based onreceipt of this message.



VMF2308W messages


v Part fn ft has a local modification modid in versionvector vvtft which must be reworked prior tobuilding product prodid.

v Part fn ft which was customized using localmodification modid in version vector vvtft has beenmigrated. It must be reworked prior to buildingproduct prodid.

v Part fn1 ft1 which was customized by beingchanged in place, cannot be migrated to the newdcllabel ({owner address|dirname}) disk. It has beencopied to the A-disk as fn2 ft2. The customizationof this part must be reworked prior to buildingproduct prodid.

v Part fn1 ft1 which was customized by being copiedand changed, has been migrated to the dcllabel({owner address|dirname}) disk as fn2 ft2. Thecustomization of this part must be reworked priorto building product prodid. [See the product exitmessage log exitfn $MSGLOG for reworkinformation.]

v Part fn ft which may have been customized bybeing copied and changed, cannot be migrated tothe dcllabel ({owner address|dirname}) disk because itsfileid is not resolved. The customization of thispart must be reworked prior to building productprodid. [See the product exit message log exitfn$MSGLOG for rework information.]

v Part fn ft may have been customized by beingcopied and changed, but its fileid is not resolved. Ifit was customized, it {has been|will be} migrated tothe ({owner address|dirname}) disk [when productprodid2 is migrated]. The customization of this partmust be reworked prior to building product prodid1.

A local modification or customized part requiringrework was found in the VM SYSLMOD table.VMFBLD will not be run for this product, or anyfurther products, for this invocation of the VMFSUFIN,SERVICE, or MIGRATE command.


User response: Rework the local modification orcustomized part, and update the VM SYSLMOD tableto indicate that the rework is complete. TheVMFUPDAT SYSLMOD command may be used toupdate the VM SYSLMOD table. If no rework isneeded, just update the VM SYSLMOD table to indicatethat the rework is complete.

To rework customized parts:

v If the part was migrated, you must incorporate anychanges found in the uncustomized part on the newrelease into the migrated part. If so specified, there isinformation in the product exit message log to assistyou with the rework. In this case the migrated partmay need to be renamed as well as reworked.

v If a changed in place part was not migrated, youmust incorporate your customizations from the partthat was copied to the A-disk into the part on thenew release.

v If a copied and changed part was not migratedbecause of an unresolved fileid, there may beinformation in the product exit message log to assistyou with the rework. You must determine the file IDof the customized part on the old release andmigrate that part to the new release.

v If a copied and changed part with an unresolved fileID was migrated, you must determine the fileid ofthe customized part on the new release andincorporate any changes found in the uncustomizedpart. If the part is migrated by another product, youcannot complete the rework until that product ismigrated.

There are instances when certain file IDs cannot beresolved by the system, such as when the subject parthas been introduced through product service updates,but the pertinent service has not been applied to thesystem from which the migration is being performed.Such files likely exist on the new system only, and thusmight not require that action be taken to migrate orrework the customization of those parts based onreceipt of this message.

VMF2309I There are no local modifications [formodid modid|for compname compname]that require rework

Explanation: There are no records in the VMSYSLMOD table that match your selection..



VMF2310W Service restart file, SERVICE $RESTARTA, has been created due to {errors|localmodifications}. {Correct theerrors|rework the modifications}, andrestart SERVICE using the followingcommand: command

Explanation: The SERVICE command did notcomplete successfully due to errors or localmodifications. A restart file was created to enable therestarting of the SERVICE command.


User response: Based on the preceding messages,either correct the errors or rework the localmodifications, and then issue the SERVICE RESTARTcommand specified in this message.



VMF2311I There are no parts with a MANUALstatus for compname

Explanation: The specified product, component, orfeature has no parts with a status of MANUAL in itsService-Level Build Status Table.



VMF2312I There are no active service restartrecords.

Explanation: Neither the System-Level Restart Tablenor the SERVICE $RESTART file were found.



VMF2313I There are no memos to display.

Explanation: There are no records in the VMSYSMEMO table with the DISPLAY status.

System action: RC = 0. Command processingcompletes.


VMF2404E Duplicate tables entered. No comparisonwill be done

Explanation: VMFSIM COMPTBL was invoked withtwo identical table specifications. No comparison isnecessary, so none will be done.

System action: RC = 24. Command processing stopsbecause of the command syntax error.

User response: If you have two tables to compare,reissue the VMFSIM command specifying the propertable specifications.

VMF2406E Missing TDATA keyword in { FILE fn ftfm | STEM stemid }

Explanation: A syntax error occurred in the input fileor stem identified in the message. The file or stem didnot start with the keyword TDATA.

System action: RC = 12. Command processing stopsbecause of the syntax error.

User response: Add the TDATA keyword to the file orstem, and reissue the VMFSIM or VMFQOBJ command.

VMF2407E Input STEM stemid is not initializedproperly

Explanation: A syntax error exists in the STEMspecified on the VMFSIM or VMFQOBJ command. Thestem count in stemid.0 must contain a positive number.


User response: Check the VMFSIM or VMFQOBJcommand syntax for the usage of the STEM operand,and reissue the command.

VMF2408E Tag missing at start of TDATA statementtdata

Explanation: A syntax error exists in the TDATAstatement identified in the message. A tag must followthe keyword TDATA. Tags must begin with a colon (:).


User response: Add the appropriate tag to the TDATAstatement, and reissue the VMFSIM or VMFQOBJcommand.

VMF2409I File fn ft will be created on {vdev|dirid}(fm)

Explanation: The specified AUX file will be created byGENCPBLS.



VMF2423E { FILE fn1 ft1 fm1 | STEM stemid }contains an incorrect file specification:fn2 ft2 fm2

Explanation: The input files and stems for theVMFSIM CHKLVL, GETLVL, INIT, and VMFERASELIST function contain lists of files:

VMFSIM CHKLVLThe file specifications are made up of a filename and optionally a file type abbreviation.

VMFSIM GETLVLThe file specifications are made up of a filename and optionally a file type abbreviation.

VMFSIM INITThe file specifications each include a file name,file type, and optionally a file mode. The filetypes must all be the same and can only beeither $PTFPART or PRODPART. These filetypes must also be consistent with the rest ofthe VMFSIM INIT command line. If theservice-level Software Inventory is beinginitialized, the file types must be $PTFPART. Ifthe system-level Software Inventory is beinginitialized, the file types must be PRODPART.

VMFERASE LISTThe file specifications are made up of a filename and file type. A file mode can bespecified, but is ignored. The list of files can



be in CMS EXEC format (with or without theleading &1 and &2) or in SIMDATA format.

The file identified in the message is incorrect, and wasnot processed.

System action: RC = 8. Command processingcontinues and bypasses the incorrect file specification.For VMFERASE, no files will be erased.

User response: Correct the file specification and enterthe VMFSIM or VMFERASE command again.

VMF2426E No valid input in {FILE fn ft fm|STEMstemid}

Explanation: The input files and stems for theVMFSIM CHKLVL, GETLVL, INIT, and VMFERASELIST function contain lists of files: .

VMFSIM CHKLVLThe file specifications are made up of a filename and optionally a file type abbreviation.

VMFSIM GETLVLThe file specifications are made up of a filename and optionally a file type abbreviation.

VMFSIM INITThe file specifications each include a file name,file type, and optionally a file mode. The filetypes must all be the same and can only beeither $PTFPART or PRODPART. These filetypes must also be consistent with the rest ofthe VMFSIM INIT command line. If theservice-level Software Inventory is beinginitialized, the file types must be $PTFPART. Ifthe system-level Software Inventory is beinginitialized, the file types must be PRODPART.

VMFERASE LISTThe file specifications are made up of a filename and file type. A file mode can bespecified, but is ignored. The list of files canbe in CMS EXEC format (with or without theleading &1 and &2) or in SIMDATA format.

No valid files were listed, and none were processed.


User response: Correct the file specifications and enterthe VMFSIM or VMFERASE command again.

VMF2441I ptfnum $PTFPART fm is for PRODIDprodid. It will not be processed

Explanation: VMFSIM INIT has encountered a$PTFPART file that is not for the product/componentbeing processed. The data contained in this file willNOT be added to the tables being processed. Thiscondition may occur if:

v An incorrect table name was entered on the VMFSIMcommand.

v The ptfnum $PTFPART file was for anotherproduct/component.



User response: If an incorrect table name was enteredon the command, reissue the command with the correcttable name. If the $PTFPART file was for anotherproduct/component, reissue the VMFSIM INIT functionfor PRODID identified in the message.

VMF2442E STEM variable stemid not definedcorrectly, stemvar contains invalid data.

Explanation: While processing STEM or ASTEM inputVMFSIM found invalid data or the variable has notbeen set correctly.


Command processing stops because of invalid STEMinput.

User response: Correct the format of the STEMvariable and reissue the VMFSIM command.

VMF2443E Invalid tag tagname found in tabletableid.

Explanation: VMFSIM has found a syntax error in thetable identified in the message.


Command processing stops for table identified in themessage.

User response: Modify the tag and/or data identifiedin the message using the VMFSIM MODIFY functionand re-run the procedure.

Note: VMFSIM MODIFY function does not supporttables that have a file type of $PTFPART, PRODPARTor $PPFTEMP. For more information on correctingsyntax errors within these tables, refer to z/VM:Installation Guide and z/VM: Service Guide.

VMF2444E Data type error found in TDATAstatement tdata. Data on tag tag containsinvalid datatype, baddata

Explanation: VMFSIM has found a data type error inthe TDATA statement entered on the command.


Command processing stops for this TDATA statementdue to syntax error.

User response: Correct the tag and/or data identifiedin the message and reissue the command.


VMF2445E Duplicate tags tag found in TDATAstatement tdata. TDATA statement willnot be processed.

Explanation: While processing the tags and dataentered on the VMFSIM MODIFY or LOGMODcommand, VMFSIM found tag(s) that were repeated inthe TDATA statement. This TDATA statement will notbe processed by VMFSIM.


Command processing stops for this TDATA statementbecause of syntax error in statement.

User response: If the name of a tag was misspelled,correct the spelling and reissue the VMFSIM command.Otherwise, delete the duplicate tags from the TDATAstatement.

VMF2445I Duplicate tags tag found in TDATAstatement tdata for table tableid. Theywill be ignored

Explanation: While processing the tags and dataentered on the VMFSIM command, VMFSIM foundtag(s) that were repeated in the TDATA statement.These tags and any data following these tags isignored.


Command processing continues ignoring theextraneous data.

User response: If the name of a tag was misspelledcorrect the spelling and reissue the VMFSIM command.

VMF2446I Tags tagnames in TDATA statement tdataare not defined [for table tablename].They will be ignored.

Explanation: While processing the tags and dataentered on the VMFSIM or VMFQOBJ command, aTDATA statement was encountered with an invalid tag.For VMFSIM, the table being processed is alsoidentified. These tags, and any data following thesetags, are ignored.


Command processing continues ignoring theextraneous data.

User response: If the name(s) of a tag(s) is misspelled,correct the spelling and reissue the command. ForVMFSIM, if the wrong table was specified, reissueVMFSIM with the correct table.

Note: To get a list of the tags defined for a SoftwareInventory table, issue VMFSIM QUERY tblname tbltype.

VMF2447E Required tag tag not found in TDATAstatement tdata for table tabletype.TDATA statement will not be processed

Explanation: While processing the tags and dataentered on the VMFSIM MODIFY or LOGMODcommand, VMFSIM found that a required tag wasmissing from the TDATA statement. This TDATAstatement will not be processed by VMFSIM.


Command processing stops for this TDATA statementbecause of syntax error in statement.

User response: If the name of a tag was misspelled,correct the spelling and reissue the VMFSIM command.Otherwise, add the required tag and data to theTDATA statement and reissue the VMFSIM command.

VMF2448E Table tableid1 has a key tag keytag1, tabletableid2 has a key tag keytag2. Tablescannot be compared.

Explanation: VMFSIM COMPTBL requires that thetables that are being compared contain the same keydefinitions. Example: the SRVAPPS and SRVRECStables both contain the same key definition, :PTF. Thesetables can be compared using VMFSIM COMPTBL.SRVAPPS and SRVDESC contain different keydefinitions, :PTF for SRVAPPS and :APARNUM. forSRVDESC, these tables cannot be compared usingVMFSIM COMPTBL.


Command processing stops because of incompatibletable definitions.


VMF2449E fn ft fm will not be processed

Explanation: VMFSIM INIT found a syntax error in a$PTFPART or PRODPART file. This file will not beprocessed by VMFSIM INIT.


Command processing stops for this file due to syntaxerror. VMFSIM will continue processing any remaining$PTFPART or PRODPART files.

User response: Report the problem to the IBMsupport center.

VMF2450I Entry tdata-statement not found

Explanation: VMFSIM MODIFY or LOGMOD function(when specified with the delete option) will issue thismessage if the data specified on the key tag in thetdata-statement cannot be located in the table beingmodified. This tdata-statement will not be processed.

System action: RC = 2. Command processing



continues with any additional TDATA statements toprocess.

User response: If the data on the key tag was notcorrect, correct the data and reissue the VMFSIMcommand.

VMF2453I Table tableid1 is a subset of table tableid2

Explanation: VMFSIM COMPTBL could not find anyentries in tableid1 that are not contained in tableid2.



VMF2457E Syntax error found in table tableid.Duplicate tag tags found

Explanation: The specified tag appears more thanonce in the specified table. This is not permitted in thistable.


User response: Correct the table and restart theprocedure.

VMF2458E messages


v Data Type error found in table tableid. Data on tagtag1 required by tag tag2 contains invalid datatype,baddata

v Data Type error found in table tableid. Data on tagtag2 contains invalid datatype, baddata

The data specified on the tag defined for table tableid isnot valid. The tag tag2 identifies the field in the tablethat owns the tag in error.


Command processing stops for table identified inmessage.

User response: Correct the data identified in themessage using the VMFSIM MODIFY function andre-run the procedure.

Note: VMFSIM MODIFY function does not supporttables that have a file type of $PTFPART, PRODPARTor $PPFTEMP. For more information on correcting datatype errors in these tables, refer to z/VM: InstallationGuide and z/VM: Service Guide.

VMF2459E Syntax error found in table tableid.Required tag tag1 [required by tag tag2]was not found.

Explanation: A tag required in the table tableid wasnot found following the second tag (tag2) identified inthe message. If the second tag (tag2) is not contained in

the message then the tag that was missing is a key tagin the table.


Command processing stops for the table identified inthe message.

User response: Add the required tag identified in themessage using the VMFSIM MODIFY function andre-run the procedure.

Note: VMFSIM MODIFY function does not supporttables that have a file type of $PTFPART, PRODPARTor $PPFTEMP. For more information on correctingsyntax errors in these tables, refer to z/VM: InstallationGuide and z/VM: Service Guide.

VMF2460W No valid tags found in TDATAstatement tdata [for table tableid]

Explanation: While processing the tags and dataentered on the VMFSIM or VMFQOBJ command, aTDATA statement was encountered with no valid tags.For VMFSIM, the table being processed is alsoidentified.


Command processing continues with next TDATAstatement.

User response: If the name(s) of a tag(s) weremisspelled, correct the spelling and reissue thecommand. For VMFSIM, if the wrong table is specified,reissue VMFSIM with the correct table.

Note: To get a list of the tags defined for a SoftwareInventory table, issue VMFSIM QUERY tblname tbltype.

VMF2461I Unknown {datatype | fieldtype} definedfor tag tag in table definition tabletype

Explanation: VMFSIM was unable to perform datatype or field type checking for the tag identified in themessage. An unknown data type of field typedefinition was found in the table definition file for thetable file type identified in the message.

System action: RC = 2. Command processingcompletes without performing data type or field typechecking for the tag identified in the message.

User response: Verify that the correct level of theVMFTBDEF EXEC and VMFSIM EXEC are accessed.Also verify that any user-defined table definitions arebeing processed by VMFSIM.

VMF2462I Table tableid1 is empty, it will be erased

Explanation: VMFSIM MODIFY or LOGMOD functionwith the delete option specified has deleted all tags anddata from the table identified in the message. The tablewill be erased.



System action: Command processing completed.


VMF2465E AUX filetype auxft for file fn was notfound in control file fn CNTRL fm

Explanation: VMFSIM CHKLVL function could notfind the AUX filetype specified on the AUXFT option inthe control file for the file identified in the message.



User response: Check the following conditions:

v If the control file contains preferred AUX files theAUXFT specified on the command may have beenignored for this file.

v The control file does not contain an entry for theAUX file.

v The AUX filetype entered on the command wasincorrect.

After correcting the error, reissue VMFSIM CHKLVL forthe file identified in the message.

VMF2465W AUX filetype auxft for file fn was notfound in control file fn CNTRL fm

Explanation: VMFSIM CHKLVL function could notfind the AUX filetype specified on the AUXFT option inthe control file for the file identified in the message.




v If the control file contains preferred AUX files theAUXFT specified on the command may have beenignored for this file.

v The control file does not contain an entry for theAUX file.

v The AUX filetype entered on the command wasincorrect.

After correcting the error, reissue VMFSIM CHKLVL forthe file identified in the message.

VMF2468E messages


v Mismatch, file fn ft not found in VVT vfn vft vfm.Aux file afn aft afm contains updates

v Mismatch, VVT file vfn vft not found on a LOCALor APPLY disk. Aux file afn aft afm contains updatesfor file fn ft

A mismatch of levels occurred. The part file fn ft is notfound in VVT vfn vft vfm. But, the Aux file afn aft afmcontains updates.


Command processing continues with next part.

User response: Check to ensure the following:

v All required disks were accessed.

v Disk search order is correct.

v The AUX file type entered on the command wascorrect.

v The correct control file was entered on the command.

After correcting any setup errors reissue VMFSIMCHKLVL for the file identified in the message. If nosetup errors were found, refer to z/VM: Service Guidefor details on how to generate an AUX file from theversion vector table.

VMF2468W Mismatch, file fn ft not found in VVT fnft fm. Aux file fn ft fm contains updates

Explanation: A mismatch of levels occurred. The partfile fn ft is not found in VVT fn ft fm. But, the Aux filefn ft fm contains updates.









VMF2469E Mismatch, Aux file fn ft fm not found.File fn ft in version vector table fn ft fmcontains updates

Explanation: A mismatch of levels occurred. Aux filefn ft fm not found. But, the Part file fn ft in VersionVector table fn ft fm contains updates.



User response: Check the following:








VMF2469W Mismatch, Aux file fn ft fm not found.File fn ft in version vector table fn ft fmcontains updates

Explanation: A mismatch of levels occurred. Aux filefn ft fm not found. But, the Part file fn ft in VersionVector table fn ft fm contains updates.



User response: Check the following:






VMF2471E Mismatch between AUX file fn auxftauxfm for file fn ft in version vectorvvtname vvtft vvtfm

Explanation: VMFSIM CHKLVL function found amismatch in the entries found in the AUX file levelspecified in the message that corresponds to the VVTidentified.








After correcting any setup errors, re-run VMFSIMCHKLVL for the file identified in the message. If nosetup errors were found, refer to z/VM: Service Guidefor details on how to generate an AUX file from theversion vector table.

VMF2471W Mismatch between AUX file fn auxftauxfm for file fn ft in version vectorvvtname vvtft vvtfm

Explanation: VMFSIM CHKLVL function found amismatch in the entries found in the AUX file levelspecified in the message that corresponds to the VVTidentified.








After correcting any setup errors, run VMFSIMCHKLVL again for the file identified in the message. Ifno setup errors were found, refer to z/VM: Service Guidefor details on how to generate an AUX file from theversion vector table.

VMF2472I VVT and AUX levels match for fn ft

Explanation: VMFSIM CHKLVL completed processingof the VVT and AUX levels for the file identified in themessage.



VMF2473I No AUX files or VVT entries found forfn ft

Explanation: VMFSIM CHKLVL could not locate anyAUX files or VVT files and/or VVT entries for the partidentified in the message. This means the part hasnever been serviced.



VMF2474E AUX files fn AUX* * found for fn but nocorresponding VVT entries were found.

Explanation: VMFSIM found one or more AUX filescontaining service for the part identified in themessage, but no VVT entries were found. This is anerror condition. All service to a part should beidentified in a VVT. VMFAPPLY may have failed orlocal modification has not been entered into the VVTfor the component.

System action: RC = 12. Command processing stopsfor the part identified in the message. VMFSIM will



continue processing any remaining parts entered on thecommand.

User response: For details on correcting mismatchesbetween AUX and VVT tables, refer to z/VM: ServiceGuide.

VMF2475I VVT file fn ft found on the vaddr (mode)disk is not defined on a LOCAL orAPPLY disk. It will be ignored

Explanation: A VVT file (fn ft) was found on a diskthat was not identified in the PPF as a LOCAL orAPPLY disk. Only VVT files defined on LOCAL orAPPLY disk are processed by VMSES.


Command processing continues with part beingprocessed.


v all required disks were accessed

v disk search order is correct

v the correct PPF file was entered on the command


VMF2480I Results for tdata-statement

Explanation: VMFSIM QUERY completed processingof the TDATA statement identified in the message.

Note: This message is only displayed if the outputoption for VMFSIM QUERY is TYPE.



VMF2481W No entries match search arguments tdata[in table tableid]

Explanation: For VMFSIM QUERY and VMFSIMCOMPTBL, no entries that matched the searcharguments specified could be found in the table beingprocessed. For VMFQOBJ, no objects that match thesearch arguments specified could be found.


Command processing continues with the next TDATAstatement.

User response: If the search arguments were enteredincorrectly, reissue the command with the correctsearch arguments.

VMF2485E fn ft is not supported by AUX files

Explanation: VMFSIM CHKLVL determined that thefile identified in the message is not supported by AUXfiles. No VVT to AUX check will be performed.VMFSIM GETLVL was issued with the AUX option andit determined that the file identified in the message isnot supported by AUX files. No AUX level searchingwill be performed.



User response: If the function being run is GETLVL,reissue VMFSIM GETLVL using the VVT option for thefile identified in the message.

VMF2486W fn not found in any VVT files identifiedin control file fn1 ft1 fm1 File fn ft inVersion

Explanation: VMFSIM could not find any VVT levelsidentified in control file fn1 ft1 fm1 that contained thefile specified in the message. No serviced levels couldbe found for the file.

System action: RC = 4. Command processing stops forthis file. VMFSIM will continue processing anyremaining files that were entered on the command.

User response: Validate the following:

v The correct disks and access order was being used.

v The correct CNTRL file was entered on thecommand.

v The correct VVT file name was entered on thecommand.

v The file entered on the command has been serviced.

If one of the conditions above is true, reissue thecommand for the file that failed. If the message stilloccurs, refer to z/VM: Service Guide for instructions oncorrecting AUX file and VVT mismatches.

VMF2487I No {VVT | AUX} levels found for file fnft

Explanation: The VMFSIM GETLVL function couldnot find any VVT or AUX levels identified in thecontrol file for the file identified in the message. Thiscould be due to one of the following conditions:

v fn ft has never been serviced.

v Disk access order is not correct.

v Service to fn ft has not been applied by VMFAPPLY.



User response: If the file has been serviced, check theapply status of the PTFs that contained service for thefile. If they have not been applied, refer to z/VM:Installation Guide for details on how to apply PTFs. If



they have been applied, refer to z/VM: Service Guide fordetails on how to re-apply PTFs to update the VVTand/or AUX files.

VMF2490E Table type tabletype is not supported byVMFSIM (function)

Explanation: VMFSIM function specified on thecommand does not support the type of table that wasentered.


Command processing stops.

User response: Reissue the command with the correcttable type specified.

VMF2500E Requisite error, missing requisite{ptfnum1 for PTF ptfnum2|prodid1 forPRODID prodid2}

Explanation: One of these conditions occurred:

v The VMFSIM command SRVREQ or SRVDEP couldnot find the requisite PTF ptfnum1 that is required byPTF ptfnum2 in the SRVREQT table for thecomponent. Additional requisites maybe required bythe missing PTF.

v The VMFSIM command SYSREQ or SYSDEP couldnot find the requisite PRODID prodid1 that isrequired by product prodid2 in the SYSREQT systeminventory table for product requisites. Additionalrequisites maybe required by the missing PRODID.

System action: RC=12. Command processingcontinues searching for any additional requisites or thenext PTF or PRODID to process.


v The correct search order has been established.

v The correct tables were entered on the command.

If none of the above conditions are true, refer to z/VM:Service Guide for procedures to follow for missingrequisites.

VMF2501E Requisite error, PTF ptfnum has a statusof SUPED. No superseding PTF(s) werefound

Explanation: VMFSIM could not find a PTF in theSRVREQT for the component that superseded the PTFidentified in the message. A PTF should not have astatus of SUPED unless a superseding PTF is APPLIED.Additional requisites may be required by the missingPTF.


Command processing continues searching for anyadditional requisites and/or the next PTF to process.


v The correct search order has been established

v The correct tables were entered on the command

If none of the above conditions are true, refer to z/VM:Service Guide for procedures to follow for status errors.

VMF2502W PTF ptfnum not found in requisite tablefn ft fm

Explanation: VMFSIM could not locate the PTFnumber entered on the command in the requisite tableidentified in the message.


Command processing stops for this PTF. VMFSIM willcontinue processing any remaining PTFs that wereentered on the command.

User response: Validate the following:

v The correct disks and access order was being used

v The correct requisite table was entered on thecommand

v The correct PTF number was entered on thecommand

If one of the conditions above is true then correct theproblem and reissue the command for the PTF thatfailed. If the message still occurs, order the PTF fromthe IBM Support Center.

VMF2503E PTF ptfnum has a status of APPLIED buthas requisites that have not beenapplied.

Explanation: VMFSIM found a PTF that has a statusof APPLIED but has one or more requisites identifiedin the SRVREQT for the component that are notAPPLIED. A PTF should not have a status of APPLIEDunless all required requisites are APPLIED or SUPED.


Command processing continues searching for anyadditional requisites and/or the next PTF to process.


v The correct search order has been established

v The correct tables were entered on the command

If none of the above conditions are true runVMFAPPLY with an apply list containing the PTF(s)that are not applied. This will correct the status of thePTF(s) in error.

VMF2504W PRODID prodid1 has a DREQ of prodid2but it has been superseded by prodid3.PRODID prodid1 will not run withprodid3.

Explanation: The specified product has a DREQ of a



product that has been superseded. This may or maynot be an error.



VMF2505W PRODID prodid1 has a NPRE of prodid2that has been applied. PRODID prodid1will not run with prodid2.

Explanation: The specified product has an NPRE of aproduct that has been applied. This indicates that thespecified product cannot be applied because it conflictswith its NPRE.



VMF2506E The query of the software inventory filefn ft fm failed with a code nn

Explanation: The VMFRDTBL routine failed whilereading the software inventory file fn ft fm. The nn codeindicates the failing condition.



User response:

Code Meaning

24 The invocation of VMFRDTBL was invalid.

32 No entries matched the search criteria

88 A returned tag or value was truncated, or thenumber of tags exceeded the internal buffersize. Increase the size of your virtual machine.

89 EXECCOMM failed. Increase the size of yourvirtual machine.

90 VMFRDTBL was not loaded as a nucleusextension.

91 There was insufficient storage. Increase thesize of your virtual machine.

100 An error occurred reading the file.

VMF2507I fn ft created on your fm-disk [from partifn ift ifm] for use in a [non-]VMSES/Eenvironment

Explanation: ASSEMBLE, HASM, HLASM, GENCMD,GENMSG, EXECUPDT, or COPYFILE completedsuccessfully, and the output file has been placed onyour fm-disk. The PPF option is used for VMSES/Eenvironments. The CTL option is used fornon-VMSES/E environments. The PPF option or the

CTL option is determined from the operands enteredon the command line.



VMF2507W The version vector vfn vft was not foundon the LOCAL or APPLY strings, butAUX files with the file type aft exist onthese disks

Explanation: The version vector tables are used byVMFSIM GETLVL to determine the file type of thelatest version of a part. The vfn vft version vector tablewas not found on the LOCAL or APPLY disk strings,but AUX files with the corresponding file type aft werefound. AUX files are created from the information inthe version vector tables, causing an inconsistent state.The information in the AUX files is not used.


User response: Two possible causes of this problemare:

v Local modifications were done, but the VMFSIMLOGMOD command was not used to add theinformation to the local version vector tables.VMFSIM LOGMOD can be used now to correct thisproblem.

v Extraneous AUX files with the file type aft were lefton the APPLY or LOCAL disk strings. Removingthese files will correct this problem.

VMF2508W messages


v AUX file fileID exists for part fn ft, but an entry forthis part does not exist in a ft1 version vector tableon the LOCAL or APPLY disks string.

v AUX file fileID exists for part fn ft, but a vvtfnversion vector table does not exist on the LOCAL orAPPLY disk string. The valid file names for thevvtfnversion version vector table are: vvtfns

A local modification was not logged in the local versionvector table.

System action: RC = 4. VMFSIM GETLVL continuesprocessing in compatibility mode where the AUX filesare used instead of the version vector tables todetermine the file type of the latest version of the part.

User response: VMFSIM LOGMOD should be used tocreate an entry in a local version vector table for thepart. The file type of the part must be renamed toreflect the local tracking number used. The file name ofthe local version vector table must match a value onthe :APPID tag in the product parameter file (PPF) andthe local version vector table must be on the LOCALstring.


VMF2509I messages


v The version vector table fn1 ft1 fm1 will be updatedfor the part fn2 ft2 [using the information in AUXfile fn3 ft3]

v AUX file fn3 ft3 not found. Entry for part fn2 ft2will be deleted from version vector table fn1 ft1 fm1

v AUX file fn3 ft3 does not contain any updates.:MOD data for part fn2 ft2 will be deleted fromversion vector table fn1 ft1 fm1

The LOGMOD option was selected and the localmodification will be automatically logged in theversion vector tables. The LOGMOD optionautomatically logs information into the version vectortable based on the information in the AUX files orinformation supplied to the VMFREPL command. TheAUX file fn3 ft3 was compared to the correspondingversion vector table and a mismatch was detected. Theinformation from the AUX file was used to replace theexisting version vector entry.

System action: RC = 0. The specified version vector isupdated.


VMF2510W No LOCAL disks defined. TheLOGMOD option is ignored.

Explanation: LOGMOD option processing is bypassedif a LOCAL disk cannot be found.



VMF2511I The highest {level of IBM service|localmodification} for part fn ft is {ft|NONE}

Explanation: The QUERY option of the VMFREPLcommand was specified. The highest level of IBMservice or local modification is returned.



VMF2512E The specified version vector file type ftis not defined as a local version vectortype in control file fn CNTRL.

Explanation: The VVTFT option of the LOCALMODcommand was specified with a file type that is notdefined in the control file. A local modification can onlybe created for a version vector level that is defined inthe control file.


User response: Enter the LOCALMOD command witha valid VVTFT or allow the command to use the

default local version vector level.

VMF2512W The specified version vector file type ftis not defined as a local version vectortype in control file fn CNTRL

Explanation: The VVTFT option of the VMFREPLcommand was specified with a file type that is notdefined in the control file. The specified version vectortable will be updated as requested.


User response: Ensure that the specified file type iscorrect. VMFBLD will only use version vector tablesthat are defined in the control file when determiningthe highest level of parts.

VMF2513I Part pfn was {found|not found} in loadlist lfn1 lft1. It will be assembled usingcontrol file cfn.

Explanation: The VMFHLASM DUAL option wasselected and the specified part was assembled using theindicated control file based on the contents of theindicated load lists. If the part was found in a load list,it is a nucleus part and was therefore assembled usingthe control file that corresponds to the load list. If thepart was not found in either load list, it is not anucleus part and therefore was assemble using theprimary control file.



VMF2514W Part fn ft will be used due to missingversion vector table entry

Explanation: Because a local modification was notlogged in the local version vector table, VMFSIMGETLVL (in compatibility mode) has identified thelisted part as the latest version to be used for thecurrent operation.


User response: VMFSIM LOGMOD should be used tocreate an entry in a local version vector table for thesubject part. This action will ensure that the correctlevel of this part is used when objects that include thispart are built.

VMF2600E messages


v There are no products to be built for productidentifier

v There are no products to be deleted for productidentifier

v There are no products to be installed for productidentifier



v There are no products to be migrated to productidentifier

v There are no products to be replaced by productidentifier

v There are no products to be installed on the{TAPE|ENVELOPE}

v There are no products to be replaced by productson the {TAPE|ENVELOPE}

v There are no products to be migrated to productson the {TAPE|ENVELOPE}

v There are no products to be enabled for productidentifier

v There are no products to be disabled for productidentifier

A major processing step is to be performed, but itcannot be performed because a valid target of thefunction could not be found.


User response: Determine if the input was specifiedproperly. If not rerun the command with the correctinput.

VMF2600I There are no memos to be printed

Explanation: The MEMO option was specified, butthere are no memos to be printed.



VMF2601R messages


v Do you want to delete product identifier? Enter 0(No), 1 (Yes) or 2 (Exit)

v Do you want to migrate old product identifier to newproduct identifier? Enter 0 (No), 1 (Yes) or 2 (Exit)

v Do you want to replace old product identifier withnew product identifier? Enter 0 (No), 1 (Yes) or 2 (Exit)

v Do you want to print memo memo identifier? Enter 0(No), 1 (Yes) or 2 (Exit)

v Do you want to create an override for productidentifier? Enter 0 (No), 1 (Yes) or 2 (Exit)

A major processing step will be performed.

System action: Command processing continues basedon your response. If you answer “No”, the processingcontinues with the next step. If you answer “Yes”, theprocessing step is performed. If you answer “Exit”, thecommand terminates with RC=500.

User response: Enter the number that correspondswith your choice.

VMF2602R messages


v The following components can be built for productidentifier. Enter the number of your choice

v The following components can be deleted forproduct identifier. Enter the number of your choice

v The following components can be installed forproduct identifier. Enter the number of your choice

v The following components can be migrated toproduct identifier. Enter the number of your choice

v The following components can be replaced byproduct identifier. Enter the number of your choice

v The following memos are available to be printed.Enter the numbers of your choices separated byblanks

v The following components can be compiled forsource ppf. Enter the numbers of your choicesseparated by blanks

v The following components can be enabled forproduct identifier. Enter the number of your choice

v The following components can be disabled forproduct identifier. Enter the number of your choice

A major processing step is to be performed, but thereare multiple choices of how to proceed. Your optionsmight include bypassing this processing step andimmediately exiting this command.

System action: Command processing continues basedon your response. If you choose to bypass thisprocessing step, the processing continues with the nextstep. If you choose to exit, the command terminateswith RC=500. For any other choice, the processing stepis performed with your choice.

User response: Enter the number or numbers thatcorrespond with your choice.

VMF2603I messages


v Building product product identifier

v Deleting product product identifier

v Installing product product identifier

v Migrating product old product identifier to new productidentifier

v Replacing product old product identifier with newproduct identifier

v Enabling product product identifier

v Disabling product product identifier

v Processing product product identifier

v Getting build status for product product identifier

v Planning for the deletion of product productidentifier



v Planning for the installation of product productidentifier

v Planning for the migration of product old productidentifier to new product identifier

v Planning for the replacement of product old productidentifier with new product identifier

v Product built

v Product deleted

v Product installed

v Product migrated

v Product replaced

v Product enabled in VMSES/E, CP processingrequired

v Product disabled in VMSES/E, CP processingrequired

This message indicates when major processing steps arebeing performed.


User response: If 'CP processing required' is indicated,refer to previously issued messages, and respondaccordingly.

VMF2604E messages


v Product product identifier cannot be processedbecause the packaging format cannot bedetermined. Either the product's PRODPART file orINSTFPP Program Level file (Iponum 0vrmnn) isrequired.

v Product product identifier cannot be built because ithas not been received

v Product product identifier cannot be deleted becauseit has not been received

v Product product identifier cannot be processedbecause its requisites are not satisfied

v Product product identifier cannot be deleted becausethere are products which depend on it

v Product product identifier cannot be deleted becauseit is not in VMSES format

v Product product identifier cannot be installed withthe REPLACE option because it is not in VMSESformat

v Product product identifier cannot be migrated tobecause it is not in VMSES format

v Product product identifier cannot be installed becauseit is not on the installation media

v Product product identifier cannot be processedbecause of problems with the product parameterfiles

v Product product identifier cannot be planned forbecause it is in INSTFPP format

A major processing step is to be performed, but itcannot be completed for the specified reason.

System action: RC = 8. Command processingcontinues, bypassing the failing sub-function.


VMF2604W messages


v Product product identifier cannot be processedbecause its requisites are not satisfied

v No product parameter file override was created forproduct product identifier

The first format of this message indicates that certainrequisite problems exist with the product beinginstalled. These problems can be ignored duringinstallation, but must be satisfied before the productcan be built.

The second format of this message indicates that noproduct parameter file override was created, eventhough you requested that one be created. This may bebecause you decided to exit from the Make OverridePanel without creating an override.



VMF2605R How would you like to proceed? Enterthe number of your choice:(0) Bypassthis product[(1) Install this productwithout its requisites][(1) Process thisproduct with the existing PPF]({1|2})Exit

Explanation: A problem was encountered processingthe product, and you must decide how to proceed.Your choices include bypassing the product,immediately exiting this command, and, in certaincases, ignoring the problem and continuing to processthe product.

System action: Command processing continues basedon your response. If you choose to bypass this product,the processing continues with the next step. If youchoose to exit, the command terminates with RC=500.Otherwise, processing continues.

User response: Enter the number for the action youwish to take.

VMF2607E fn is reserved for use by VMSES/E

Explanation: The specified VMSES/E exec is notintended for external use.


User response: Determine which VMSES/E command



provides the desired function.

VMF2608W messages


v Product prodid is not participating in productenablement

v There are no products participating in productenablement

The product that was specified does not have anyenablement state or status in the CP system norVMSES/E.

System action: RC = 4. Processing completes. No newenablement report is generated.


VMF2680E Module name HCPMM3 is a reservedmemory marker for HCPMDLATMACRO but is included in a macro filethat is used to build the Load List.

Explanation: The HCPMM3 memory marker is usedto mark the end of the CP load list. HCPMM3 cannotbe defined in an alternate xxxMDLAT macro.

System action: RC = 100. Command processingterminates.

User response: Remove the HCPMM3 memorymarker from the appropriate xxxMDLAT macro andrerun GENCPBLS.

VMF2701E Product prodid packaging format is notknown by VMFINS

Explanation: The product specified is not packaged ina format recognized by VMFINS and cannot beinstalled by VMFINS.



User response: Manual installation of the specifiedproduct is required. For more information on how tomanually install the specified product, refer to z/VM:Installation Guide

VMF2704E messages


v You chose {ADD|NORESOURCE} but you are notenrolled in the filepoolid filepool

v You chose {NORESOURCE} but you do not haveenough space in the filepoolid filepool

The process you are running requires you to beenrolled in the filepoolid file pool and have spaceavailable to you in the file pool. You either were not

enrolled in the file pool, or there was not enough spaceallocated to your user ID to perform the task you weredoing. Because you chose the specified options, youcould not be enrolled in the file pool or more file poolspace could not be made available to your user ID.

System action: Processing stops with RC = 100.

User response: Ensure you are enrolled in the filepool with a sufficient amount of space, and restart theprocess.

VMF2705R The current description for this productis: description Enter a new description orpress ENTER to use the currentdescription

Explanation: When you create product parameter fileoverrides, you are given the opportunity to provide anew description of the product.

System action: System waits for a response.

User response: Enter a new description for theproduct, or press the ENTER key to use the existingdescription.

VMF2707R Have the resources already beengenerated for product product identifier?Enter 0 (No) or 1 (Yes)

Explanation: Products packaged in INSTFPP formatdo not have resources generated automatically byVMFINS processing. These must be generated externalto VMFINS.

System action: System displays a prompt.

User response: Respond to the prompt. If theresources have been generated, you can continueprocessing. If the resources have not been generated,the process will terminate and you must generate theresources for the product and rerun the command.

VMF2713I Attempt to save shared file system{authorizations|aliases} for fn ft diridfailed with RC rc

Explanation: The process tried and failed to saveauthorizations or aliases for the specified fileid.



User response: When processing ends, eithermanually grant the appropriate authorizations ormanually create the appropriate aliases.

VMF2714W Migration of prodid|ppfname compname isterminating

Explanation: Migration processing for the indicatedproduct is terminating because you chose to quit.






VMF2715I messages


v Tailored part fn1 ft1 fm1 (vaddr1|dirid1) saved as fn2ft2 fm2 (vaddr2|dirid2). The specified tailored part hasbeen saved in the migration save area with the newpart name. The new part name will be processedduring the migration Restore Tailorings phase.

v Authorizations saved for fn1 ft1 dirid. Shared Fileauthorizations have been saved for the specified part.These file authorizations will be restored during themigration Restore Tailorings phase.

v Aliases saved for fn1 ft1 dirid. Shared File aliaseshave been saved for the specified part. These filealiases will be restored during the migration RestoreTailorings phase.



VMF2716I messages


v The following files can be erased from vaddr

v The following files may exist on your system. Theycan be erased

The list of files following this message indicate the filesthat the product you are working with loaded to thedisk that was linked as the specified virtual address.



VMF2721E Compname compname is not valid

Explanation: You entered an invalid component onthe command line for the product you are workingwith.


User response: A list of valid components will bedisplayed. Choose the component you wish to processand enter the correct number.


Explanation: This message indicates when varioussteps of the product deletion process have completed.

v Product files have been deleted

v Product resources have been deleted



VMF2726I Prodid prodid has been deleted

Explanation: All of the product code and resources forthe product have been removed from the system.



VMF2733E Error reading tape or envelope

Explanation: An error occurred while attempting toread a product tape or envelope.



User response: Review any preceding messages,correct the problem, and reissue the command.

VMF2735E Did not locate product {prodid|ppfnamecompname} on this {TAPE|ENVELOPE}

Explanation: The product/component that youspecified could not be found on the current tape orenvelope, or the tape was positioned past the specifiedproduct when VMFINS began processing this product.This may occur if you process more than one productat a time and you change the order in which theproducts are processed from that of the tape.

System action: The user is asked to mount the correcttape.

User response: If the product is on the tape that iscurrently mounted, then enter 1 to continue. If theproduct is not on the tape, then mount the correct tapeand enter 1 to continue.

VMF2737E messages


v Tape does not contain a table of contents

v Process all products on the tape or issue INSTFPPspecifying each product identifier

The action you requested requires the tape containingthe table of contents to be mounted. This tape does notcontain the table of contents. If the second part of themessage appears, you can process all the products onthe tape by specifying each product identifier as inputto the INSTFPP command.

System action: Processing stops with RC=100.

User response: Mount the tape that contains the tableof contents or specify each individual product identifierand restart the process.


VMF2738I No files to erase from fm for productprodid

Explanation: No files will be erased from the specifiedmode due to one of two reasons:

v There is no VMSES PARTCAT file on that mode.

v The VMSES PARTCAT file contains no entries for thespecified product.


User response: If the mode or the product identifier isincorrect, enter the command again with the correctvalue.

VMF2739I messages


v Erasing files from {vdev|dirid}

v Listing files on {vdev|dirid}

v No files to erase from {vdev|dirid}

v No files to list on {vdev|dirid}

One of the formats of this message is issued for eachminidisk or directory that may contain product codefor a product that is to be deleted. The set of minidisksor directories is obtained from the :MDA section of thePPF. All strings listed in the :MDA section areprocessed except for LOCAL, TASK and SYSTEMstrings. When the PLAN option is being used, the filesthat make up the product code on each disk are onlylisted. When the NOPLAN option is being used, thefiles are actually erased.



VMF2740E messages


v There is not enough physical space in filepoolfilepoolid at storage group storage_group to meet therequirements of the product you are installing. Thefollowing minidisks will be added to the serveridserver machine, but will not be made available tothe filepool. You need to manually add these disksto the filepool, and start the process again. The listis as follows: The product you are installing loadsfiles into the filepoolid filepool, but the filepool doesnot have enough physical space in the indicatedstorage group to meet this product's requirement.The Resource Management tool has added theappropriate number of minidisks to the servermachine, serverid, but you need to make theseminidisks available to the filepool.

v Filepool filepoolid on node nodeid requires that youadd at least nn 4K block(s) of space to storagegroup storage_group to satisfy the current request.The filepool is not owned on the current node.

Therefore, automatic directory updates cannot bemade to add space. The message gives the nodename where the minidisk resources are defined forthe indicated filepool. Use the QUERY RESOURCEcommand on the indicated node to determine theserver ID that owns these minidisks. On this othersystem, update the directory with the requiredminidisk additions for this server ID and place itonline. Then, make these minidisks available to thefilepool at the indicated storage group.

System action: RC=36. Processing terminates.

User response: If necessary, make these disks availableto the indicated system and to the filepool, and restartthe process.

VMF2742E There are multiple :TARGET. sectionsfor userid vaddr with conflicting options

Explanation: The :RMT. section of the PRODPART filehas multiple :TARGET. sections for this user's minidisk.Some of the options within these two sections conflict.



User response: There is an error in the PRODPARTfile shipped by IBM. This is not a user-tailorable file.Contact the IBM Support Center about this problem.

VMF2743I {Original|Temporary} CP directoryplaced online

Explanation: Either a temporary CP directory wasplaced on-line during processing, and now the originalCP Directory is placed back on-line or a temporary CPdirectory is placed on-line during processing so theprocess can link to certain minidisks.



VMF2744E Error placing {original|temporary} CPdirectory online

Explanation: An error has occurred trying to place aCP Directory on line.



User response: Check the associated message todetermine the return code for the DIRECT |DIRECTXA command. Research the problem that theexec is having with the DIRECT | DIRECTXAcommand and try to resolve it. If you cannot resolvethe problem, contact the IBM Support Center.



VMF2746E This product needs blksize blocks onuserid vaddr, but there was not enoughcontiguous space available.

Explanation: Resource management was trying toallocate the specified number of blocks of space for thisuserid's minidisk, but could not find enoughcontiguous free space to do so.



User response: You need to create a contiguous spacelarge enough to contain this minidisk.

VMF2753E Invalid entry data on line linenum in filefn ft

Explanation: An error was found on the specified lineof the file.


User response: If the error is in the VMFRMTEXTENTS, correct the error and enter the commandagain. If the error is in the $DASD$ CONSTS, thencontact the IBM Support Center.

VMF2758E Multiple section_name sections for useriduserid in prodid PRODPART

Explanation: The PRODPART file for this product hasmultiple copies of the specified section, but only one ofthese sections is allowed.



User response: There is an error in the PRODPARTfile shipped by IBM. This is not a user tailorable file.Contact the IBM Support Center about this problem.

VMF2759I messages


v userid vaddr minidisk could not be deleted becauseit is formatted format_type1

v userid vaddr minidisk could not be deleted becauseit is RECOMPed

v userid vaddr minidisk could not be deleted becausethere are still files on it

v The SFS Directory dirname could not be deleted

v The SFS Directory dirname was not deleted becausethere are still files or subdirectories associated withit

The userid, SFS directory, or minidisk could not bedeleted for the specified reason.



User response: Resource management (VMFRMT) wastrying to delete the SFS directory, or minidisk, butcould not for the specified reason. You may want todetermine why it couldn't be deleted, and delete itmanually if it is no longer needed.

VMF2760I messages


v Descriptive_name (modname) processing started

v Descriptive_name (modname) processing completed[stepname|successfully|unsuccessfully|withwarnings]

v Descriptive_name (modname) processing started for[ppfname compname|product prodid]

v Descriptive_name (modname) processing completed[stepname|successfully|unsuccessfully|withwarnings] for [ppfname compname|product prodid]

v Descriptive_name (modname) processing incompletedue to local modifications or customized parts

v Descriptive_name (modname) processing previouslycompleted for product prodid (compname)

v Descriptive_name (modname) processing compname step

Informational message informing you when thedescriptive_name has started and completed processing.


User response: If incomplete due to localmodifications, rework the local modifications, updatethe VM SYSLMOD table to indicate that the localmodifications have been reworked, and restart thecommand. The VMFUPDAT SYSLMOD command maybe used to update the VM SYSLMOD table.


Explanation:

v The userid userid is no longer needed by thisproduct. It has not been deleted from the CPdirectory, but you may want to delete it

v The following lines were added to the userid userid,but are no longer needed by this product. Theyhave not been deleted from the CP directory, butyou may want to do so.

The userid or the lines that were added to the useridare not needed by this product anymore. They were notdeleted from the CP directory, but you may want to doso.





User response: Resource management (VMFRMT) wastrying to delete the userid, but could not for thespecified reason. You may want to manually delete it ifit is no longer needed.

VMF2763I This file represents a higher level ofservice

Explanation: The preceding message identified a PTFfile that could not be located. This PTF file represents alevel of service that is higher than the service containedon the tape.


User response: You need to determine why this PTFfile could not be found. If this service is still required,then you need to reapply this PTF.

VMF2763W PTF ptfnum must be reconciled, but itspart list fn ft is missing

Explanation: The specified PTF was applied to theprevious level of the product being installed, but is notyet included in the new level that you are installing. Ifyou do not reapply this PTF you may back-level theservice level of this product. In order to reapply thisPTF you must reorder it, because its part list is missing.



User response: If this PTF is required on your system,reorder the PTF and apply it to the new level of theproduct.

VMF2767I messages


v Reading fn ft fm for additional options

v Reading fn ft fm for list of {products | objects |PTFs | APARs | components | localmods} toprocess

These messages notify you when the system accessescertain files for additional information.



VMF2768W The STORE command can only be usedfor tailorable files

Explanation: An attempt was made to use the STOREcommand while Xediting a nontailorable file.



User response: The STORE command can only beused while Xediting a tailorable file.

VMF2769W No lines marked with CUT or CUTC

Explanation: An attempt was made to use thePASTE/PLACE prefix command without marking anytext to be moved with a CUT or CUTC prefix tag.



User response: Enter a CUT or CUTC tag in the prefixarea before entering the PASTE/PLACE prefixcommand.

VMF2770I There are some PTF's that need to bere-applied. The PTF's can be located inthe file fn $APPLIST A

Explanation: The service reconciliation processing hasidentified some PTF's that may need to be re-applied.


User response: Look at the $APPLIST file anddetermine which if any PTFs need to be reapplied tothe product.

VMF2771E The CP SET PRODUCT command failedfor product prodid

Explanation: A CP SET PRODUCT command that wasissued in response to a VMFINS ENABLE command ora VMFINS DISABLE command, that was executed bythe SERVICE EXEC, failed.

System action: RC=100. Command processingterminates.

User response: Correct the problem that caused theCP SET PRODUCT command to fail and then rerun theSERVICE EXEC. The most likely cause of the CP SETPRODUCT failure is that the user ID did not have thecorrect privilege class to execute the command. TheSERVICE EXEC can be run only on MAINT or anequivalent userid.

VMF2771I The CP SET PRODUCT commandcompleted successfully for productprodid

Explanation: A CP SET PRODUCT command wassuccessfully issued in response to a VMFINS ENABLEcommand, a VMFINS DISABLE command, or aVMFINS INSTALL, MIGRATE or DELETE commandwith the ENABLE or DISABLE option.




VMF2771W The CP SET PRODUCT commandcompleted with return code rc forproduct prodid

Explanation: A CP SET PRODUCT command that wasissued in response to a VMFINS ENABLE command, aVMFINS DISABLE command, or a VMFINS INSTALL,MIGRATE or DELETE command with the ENABLE orDISABLE option failed. VMSES/E will build an execcontaining the CP SET PRODUCT command. MessageVMF2772I is issued when the exec is created.


User response: Correct the problem that caused theCP SET PRODUCT command to fail, and then run theexec that contains the command. The most likely causeof the CP SET PRODUCT failure is that the user ID didnot have the correct privilege class to execute thecommand.

VMF2772I File fn ft created on your fm-diskcontains the {CP SET PRODUCTcommand|system configurationPRODUCT statement} for product prodid

Explanation: File fn ft fm was created in response to aVMFINS ENABLE command, a VMFINS DISABLEcommand, or a VMFINS INSTALL, MIGRATE orDELETE command with the ENABLE or DISABLEoption.


User response: If the file contains the systemconfiguration PRODUCT statement, add the statementto your system configuration file at this time so the CPenablement state will be retained over the next IPL.This new PRODUCT statement should be placed afterany current PRODUCT statements in the systemconfiguration file.

If the file contains the CP SET PRODUCT command, itwas created because the CP SET PRODUCT commandfailed. Correct the cause of the failure, and invoke thefile. A fn EXEC was created if it did not already exist orif it did exist on the A-disk and was created byVMFINS; otherwise a fn $$EXEC$$ was created. Inorder to run the $$EXEC$$ file you will need to renameit with a file name of your choice and a file type ofEXEC.

VMF2773E File fn ft could not be created on yourfm-disk. This file would have containedthe {CP SET PRODUCTcommand|system configurationPRODUCT statement} for product prodid.

Explanation: VMSES/E attempted to create fn ft fm inresponse to a VMFINS ENABLE command, a VMFINSDISABLE command, or a VMFINS INSTALL,

MIGRATE or DELETE command with the ENABLE orDISABLE option.

System action: RC = 8. Processing terminates for thisproduct.

User response: Correct the cause of the failure. Themost likely cause of the failure would be a full diskcondition.

If a VMFINS ENABLE or DISABLE command wasrunning, re-enter it.

If a VMFINS INSTALL, MIGRATE, or DELETEcommand was running with the ENABLE or DISABLEoption, the main function of the command (install,migrate, or delete) completed successfully, and only theenable or disable function failed. In this case enter aVMFINS ENABLE or DISABLE command for thefailing product after correcting the failure.

VMF2774I The system configuration PRODUCTstatement for product prodid wassuccessfully copied from file fn ft tosystem configuration file fn ft on useridaddr.

Explanation: A system configuration PRODUCTstatement, that was created by a VMFINS ENABLEcommand or a VMFINS DISABLE command that wasexecuted by the SERVICE EXEC, was copied to thesystem configuration file.



VMF2775I Full volume minidisks are used byppfname compname (product prodid). Theowners and descriptions are: userid -description You need to {add|delete}these full volume minidisks

Explanation: The product you are working withrequires fullpack minidisks. If you are installing thisproduct, you need to add these fullpack minidisks tothe CP directory. If you are deleting this product, youmay want to delete these fullpack minidisks from theCP directory.


User response: Manually add or delete the fullpackminidisk definitions.

VMF2776E messages


v System name systemid does not match a systemname in the [system configuration | VM SYSPINV]file

v The following system names do not match a systemname in the [system configuration | VM SYSPINV]file: systemid_list



For the VMFUPDAT command, a system name wasspecified which does not match any system name inthe system configuration file. For the SERVICE orPUT2PROD command, a system name was found inthe system configuration file that does not exist in thesystem-level Product Inventory file, VM SYSPINV, or asystem name was found in the VM SYSPINV file thatdoes not exist in the system configuration file.Depending on your system environment, you canreceive more than one instance of this message.

System action: Command processing ends.

User response: For the VMFUPDAT command, enterthe command again, specifying a system name that isin the system configuration file. For the SERVICE orPUT2PROD command, verify that the system names inthe system configuration file and the VM SYSPINV fileare correct.

In an SSI cluster, use the QUERY SSI command todetermine the valid system names in the cluster. On anon-SSI z/VM system, use the QUERY USERIDcommand to determine the system name.

To change a system name in the system configurationfile, refer to the SYSTEM_IDENTIFIER statement inz/VM: CP Planning and Administration. To change asystem name in the VM SYSPINV file, use thiscommand: VMFUPDAT SYSPINV SYSTEM new_systemidold_systemid.

VMF2780E {var1|tag|value} is not a valid {var2,found within|tag within|value for tagwithin} the section section in the prodidPRODPART

Explanation: The resource management processingfound an error in the PRODPART file. Either a variable,a tag, or a tag value is not valid in the specifiedsection.



User response: There is an error in the PRODPARTfile shipped by IBM. This is not a user-tailorable file.Contact your IBM Support Center about this problem.

VMF2781E User userid does not have an associatedaddress with the SEPARATED tag in theTARGET section of prodid PRODPART

Explanation: While processing a SEPARATED tag inthe TARGET section, a userid was found which did nothave an address. Values for the SEPARATED tag comein pairs of userid and address.



User response: There is an error in the PRODPARTfile shipped by IBM. This is not a user-tailorable file.Contact the IBM Support Center about this problem.

VMF2782E tag1 is an unexpected tag found beforetag2 in the section section in prodidPRODPART

Explanation: The tag tag1 has appeared out of orderin the section section of the PRODPART file.




VMF2783E Unable to locate tag tag in section sectionin prodid PRODPART

Explanation: The tag was not located before reachingthe end of the section section in the specifiedPRODPART file. This tag is a section ending tag.




VMF2785E Required tag tag missing from :TARGETsection in prodid PRODPART

Explanation: The tag tag is required but cannot belocated in the :TARGET section in the specifiedPRODPART file




VMF2786E Variable var referenced in the sectionsection in the prodid PRODPART {cannotbe found|must match up to a LINK [orDIR] statement|has a parm value ofvalue that is not valid} in the :DCLsection in ppfname PPF

Explanation: A Variable tag found in the sectionsection of the PRODPART file was not defined orimproperly defined in the :DCL section of the PPF file.





User response: Determine what caused the indicatedproblem in the PPF and PRODPART files. The errormay have occurred during customization of theproduct parameter file override file. If it did, correct theoverride file and rerun the command. If the error is inthe PRODPART file shipped by IBM, contact the IBMSupport Center. The PRODPART file is not a usertailorable file.

VMF2790R Do you wish to continue? Enter 1 (YES)or 0 (NO).



Command processing either continues with a returncode of 0 or stops with a return code of 500 based onyour response to the prompt.

User response: Enter one (1) to continue or zero (0) toquit.

VMF2791R Enter 0 (No) or 1 (Yes) [ or 2 (Exit)]


System action: Command processing continues if yourresponse is 0 or 1, otherwise the processing stops withRC = 500.

User response: Enter zero (0) to skip this product, one(1) to process the product, or two (2) to quit.

VMF2793E A free virtual device address is notavailable

Explanation: An attempt to find a free virtual deviceaddress failed.



User response: After processing ends, detach a virtualdevice address. Prepare the system for a restart byfollowing the restart guidelines.

VMF2794I Now creating override for productproduct identifier

Explanation: Normal processing is continuing.



VMF2795E The virtual machine storage is not largeenough [to build segment segname].

Explanation: Either:

v There was not enough available free storage tocontinue running, or

v There was not enough available free storage to buildthe specified saved segment.


For the first case, command processing stops because ofthe external error.

For the second case, syntax checking continues, but nosaved segment is built.

User response: For the first case, after processingends, define a larger virtual machine storage size.Prepare the system for a restart by following the restartguidelines.

For the second case, after processing ends, define alarger virtual machine storage size. Re-IPL CMS. Thenenter the VMFBLD command again to build the savedsegment.

VMF2795W The virtual machine storage is not largeenough to build segment segname.

Explanation: The process determined there was notenough available free storage to build the specifiedsaved segment.

System action: RC=4 Command processing continues.

User response: After processing ends, define a largervirtual machine storage size, if that is required to buildthe saved segment. Re-IPL CMS, if necessary. Thenbuild the saved segment.

VMF2796I Completed creating override for productproduct identifier. Overrides for othercomponents in PPF ppfname will now becreated.

Explanation: A PPF override has been created for theproduct being installed or migrated. Overrides to anyother components in the original PPF will now becreated incorporating the appropriate changes.



VMF2805I messages


v Product product identifier passed requisite checking

v No other products depend on product productidentifier

If you are installing a product, this message indicatesthat all requisites for the specified product are satisfied.

VMF2790R • VMF2805I


If you are deleting a product, this message indicatesthat there are no other products on the system thatdepend upon the specified product.


User response: None

VMF2806W messages


v The following requisites for product productidentifier are not satisfied:

v The following products depend on product productidentifier. They must also be removed if this productis deleted from the system:


v The product failed requisite checking and cannot beprocessed. This relates to install requisites and areflagged in this message as type PREREQUISITE.

v A product does not have run time requisitessatisified and processing continues if all installrequisites are met. These missing requisites areflagged in the message as type REQUISITE.

v There are products on the system that depend uponthe product you are trying to delete.

Before a product is installed a requisite check isperformed. This will determine if there are otherproducts that need to be installed prior to installing orrunning this product. Also, it will determine if there areproducts installed on the system that preclude youfrom installing this product.

Before a product is deleted a dependency check isperformed to determine if there are other products onthe system that depend upon the product you aredeleting.




VMF2811E messages


v Error occurred when trying to set a stem variable

v STEM option is only valid when the command isissued from either a REXX or EXEC-2 exec

If the first variation appears, then VMFRDTBL couldnot set the stem variable, this could be caused by a lackof free storage.

If the second variation appears, then there is noEXECCOM interface established in which to return theSTEM. The most obvious causes are:

v the STEM option was used with a command lineinvocation of VMFRDTBL.

v the exec where the STEM option was used with aninvocation of VMFRDTBL is not a REXX or EXEC-2exec.

v if the calling program was not an exec, then theextended parameter list (EPLIST) was not properlydefined.


Command processing terminates.

User response: Correct the situation and reissue thecommand.

VMF2818I Your version of the file fn ft is beingcopied to {userid address|filepool directory}without editing because the new IBMfile has not changed

Explanation: IBM has not changed the file whichcorresponds to the tailored customer file. The customerfile will replace the corresponding IBM file loaded fromtape.

System action: Command processing continues. Yourtailored version of the file replaces the correspondingnew IBM file loaded from tape.


VMF2819W The variations of this message areexplained below.

Explanation:

v Attempt to restore shared file system read|writeauthorization on fn ft directory for userid useridfailed with RC= rc

v Attempt to recreate shared file system alias on basefile fn1 ft1 directory1 for alias fn2 ft2 directory2 failedwith RC= rc

v An attempt to restore a previously saved shared filesystem authorization failed.

v An attempt to recreate a previously saved shared filesystem alias failed.



User response: When processing ends, eithermanually grant the appropriate authorization ormanually create the appropriate alias.

VMF2820E A valid file mode letter must bespecified

Explanation: A nonalphabetic file mode letter wasentered.


User response: Enter a valid file mode letter. An



asterisk (*) or blank will not be accepted.

VMF2821I Build (VMFBLD) must be executed afterreapplying the specified PTFs

Explanation: PTFs have been applied to the oldproduct which have not been applied to the newproduct. To prevent back-leveling of the product thePTFs listed must be reapplied before executingVMFBLD.


User response: Read the $VMFINS $MSGLOG whenprocessing completes to see which PTFs need to bereapplied. APPLY the PTFs and run VMFBLD torebuild the product.

VMF2822I Product ppfname compid migratedsuccessfully

Explanation: The indicated product was migratedwithout any errors.




Explanation:

v Build of product prodid compid completedunsuccessfully

v routine encountered errors in the prodid

v Product prodid compid was not built because theSTATUS option was used

The product identified in the message was not built.The product either did not build successfully becausethere was an error during the build, or the STATUSoption was entered and only information wasrequested.

System action: RC=100 or RC=0.


User response: If an error occurred during the buildprocessing, then you need to look at the other errormessages that were displayed to determine why theerror occurred. Fix the problem and start the processagain.

If the build was not done because the STATUS optionwas entered, then you need to determine theappropriate build option to use and start the processagain.

VMF2824R Enter the file name, type, and mode ofthe CP directory in the format fn ft fm

Explanation: The CP directory file is needed by theprocess.


User response: Specify the file name, file type and filemode of your CP directory file. The CP directory filemust reside on a R/W accessed minidisk or SFSdirectory. You must specify a valid file mode.

VMF2825E The userid userid needed by themigration was not found

Explanation: An attempt to link a minidisk failedbecause the userid was not found in the CP directory.



User response: Check for the existence of the userid inyour CP directory when processing ends.

If the userid exists, check the component levelinventory files for the cause. If the userid does not existin the inventory files, contact your IBM servicerepresentative.

Correct the situation that caused the failure. Prepare thesystem for a restart by following the migration restartguidelines.

VMF2826I ppfname compname has not been receivedon the system, but there is at least onecopy of product prodid on the system.The SYSAPPS table will be updated forthis PPF and build processing willcontinue.

Explanation: None.



VMF2828W userid vaddr was created but needs to beformat_type formatted. You need tomanually format the disk.

Explanation: The resource manager (VMFRMT) wasable to add the specified disk that the product required,but was not able to format the disk.


Command processing continues, but you need tomanually format the disk.

User response: Format the disk and restart theprocess.


VMF2830E userid vaddr cannot be grown. It wasoriginally format_type1 formatted. Thisproduct needs it format_type2 formatted

Explanation: The resource manager (VMFRMT) istrying to increase the size of the specified minidisk.However, the minidisk was previously formatteddifferently than the new format requirement. Thus, theminidisk could not be grown.


User response: You need to determine why theexisting disk is formatted as specified. If it is no longerneeded, you can delete it. Otherwise, you may want tochange the address of the old minidisk so the new onecan be added. Enter the command again.

VMF2831E This product needs blksize blocks ondisk userid addr. This disk cannot begrown because it is RECOMPed

Explanation: VMFRMT is trying to increase the size ofthis minidisk. However, the disk that exists isRECOMPed and cannot be grown.


User response: You need to determine why the oldminidisk was RECOMPed. If it is no longer needed inthis format, you can delete the minidisk and start theprocess again. Otherwise, you may want to change theaddress of the existing minidisk.

VMF2832E packname was entered as a valid pack infile fn ft, but it is not CP OWNED orSYSTEM OWNED, so cannot be used

Explanation: The DASD volume packname is listed inthe file fn ft as one that the Resource Manager(VMFRMT) can use for adding minidisks. However,this DASD volume is not CP or SYSTEM owned, soVMFRMT cannot use it.



User response: Either remove the line from the file sothat VMFRMT does not try to use it, or make the packCP or SYSTEM owned. Reissue the command.

VMF2832W messages


v Entry entry in VMFRMT EXTENTS fm will not beused because volid is not a valid volume identifier

v Entry entry in VMFRMT EXTENTS fm will not beused because model is not a valid DASD model

v Entry entry in VMFRMT EXTENTS fm will not beused because n is not a valid starting extent for thisDASD model

v Entry entry in VMFRMT EXTENTS fm will not beused because n is not a valid size for this DASDmodel

v Entry entry in VMFRMT EXTENTS fm will not beused because volume volid was already defined as adifferent DASD model

v Entry entry in VMFRMT EXTENTS fm will not beused because volume volid is not attached or is notCP OWNED or CP SYSTEM. You may not have theproper user class

The VMFRMT EXTENTS file contains all of the spaceavailable for the VMSES/E resource manager to use inallocating DASD space for products being installed. Thespecified entry is not valid. Therefore, no space will beallocated from it. Other entries in the file will still beprocessed.


User response: If there is not enough space availablefor the product you are installing, correct the entry oradd additional entries to the VMFRMT EXTENTS file.Instructions for updating the file are included at thetop of the file.

VMF2833E messages


v routine encountered errors in the CP directory, fn ftfm, specified as input

v routine encountered errors in the prodid PRODPARTdirectory information added to the CP directory

An error was encountered either in the original CPdirectory that was specified as input or in the CPdirectory information obtained from the specifiedPRODPART file.



User response: If the error occurred in the original CPdirectory, then correct the error and start the processagain.

If the PRODPART file was in error, then contact theIBM Support Center about this problem.

VMF2834I message

Explanation: message is the following:

**************************************************************** PLEASE NOTE, VERY IMPORTANT!!**************************************************************** If a message indicating that command processing** has completed is not displayed or if the



** command command fails, to recover, place the** CP directory fn ft fm on-line with the** command command**************************************************************

A temporary CP directory is placed on line, and theoriginal CP directory will be put back on line whenprocessing is complete. If something happens to thesystem before the original CP directory is placed online you need to put the original CP directory back online.


User response: If the message does not appear, putthe original CP directory on line as specified in thismessage. Otherwise, no response is required.


Explanation:

v Shared File System resources will not be allocatedbecause the filepoolid filepool is unavailable orunknown

v Shared File System resources will not be allocatedbecause there is not enough free space in thefilepoolid filepool

The Shared File System resources were not allocated.Either the file pool is unavailable or unknown or thereis not enough free space available in the file pool.

System action: RC = 100. Command processing stopsbecause of the external error. The Shared File Systemresources were not allocated.

User response: Fix the problems and continue theprocess. If you are unable to resolve the problems,contact the IBM Support Center.

VMF2837I The product you are installing requiresthe userid userid, but one already exists.The new CP directory control statementshave been commented out in the CPdirectory, you will need to modify thisuserid.

Explanation: The product needs the specified userid,but that userid already exists. The new useridstatements were commented. Before running thisproduct you will need to modify this userid's CPdirectory statements.


User response: You may want to look at the useridstatements that were commented out and update theold userid statements accordingly.

VMF2842E Products entered must be inppfname-compname pairs

Explanation: The products were not entered asppfname component name pairs. Each ppfname enteredmust have a component name associated with it.


Command processing stops due to the commandsyntax error.

User response: Ensure that all products entered on thecommand line have a ppfname and a component nameand then reissue the command.

VMF2848E No temporary space is available.

Explanation: The virtual device has not been definedin the virtual machine configuration because thetemporary space requested is not available. Temporaryspace is considered not available if:

v No space has been allocated by the installation fortemporary use

v The number of cylinders (or blocks if FB-512 device)requested cannot be satisfied from the availablespace remaining.



User response: Reissue the command. If there istemporary space allocated, you may have to wait untilthere is enough temporary space available tosuccessfully complete the command. If there is notemporary space allocated by the installation, contactyour system support personnel.

VMF2849E Invalid virtual address

Explanation: Incorrect virtual address has been used.



User response: Ensure that you are using a validvirtual address. Correct this problem and re-run theprogram.

VMF2850W The file fn ft already exists on the diskspecified

Explanation: The filename and filetype supplied bythe user already exists on the minidisk specified on thedata entry panel.


Data panel is redisplayed and processing continues.

User response: Modify the file name and/or file typeon the data entry panel and reissue the command.


VMF2851R messages


v Type a new fileid, fn ft fm, and press ENTER

v Type a new filename for the product parameter fileoverride and press ENTER

The first variation may appear during a MigrationRestore Tailorings step. You have asked to save atailored file and one already exists with the same fileid.The second variation appears when you are creating auser override to a product parameter file. The windowthat appears is asking what you want to call this newoverride file.


User response: Enter a new file id or file name andpress ENTER.

VMF2854I messages


v (0) Return to edit session without saving anychanges made this session

v (1) Return to edit session saving all changes madethis session

v (2) File IBM version with changes and continuemigration processing

v (2) Send IBM version with changes to reader andreturn to edit session

v (3) File your version with changes and continuemigration processing

v (3) Send your version with changes to reader andreturn to edit session

v (4) Copy IBM version with changes to filemode fmand return to edit session

v (5) Copy your version with changes to filemode fmand return to edit session

These are the choices available when exiting the “splitscreen” editing facility of the migration process. Thefiles you are editing are tailorable files needed by theproduct being migrated. The migration process needsto dispose of the files being edited and offers this list ofactions.


User response: Choose one of the options.

VMF2855I messages


v (0) Return to view session

v (1) Erase the saved version and continue migrationprocessing

v (1) Send the saved version to reader and continuemigration processing

v (2) Copy the saved version to filemode fm andcontinue migration processing

These are the choices available when exiting the browseediting facility of the migration process. The files youare browsing are tailorable files no longer needed bythe product being migrated. The migration processneeds to dispose of the files being browsed and offersthis list of actions.


User response: Select one of the options.

VMF2856I Shared File authorizations and aliasesmay be lost for the following files:

Explanation: If you are not the owner of the SFS fileslisted, any file authorizations and aliases may not beable to be saved and restored by the migration process.

System action: A list of the affected files is displayedand you are prompted to continue or quit.

User response: Determine whether processing shouldcontinue.

VMF2857E Fileid fn ft is not valid as a tailored part

Explanation: File identifiers for a tailored part (TPARTon the PRODID file), must be explicitly defined. Nowildcarding is allowed on a :PARTS tag containing theTPART keyword.




VMF2858R messages


v Choose an option and enter the correspondingnumber

v Choose the copy to replace and enter thecorresponding number

v Choose the copy to delete and enter thecorresponding number

v Choose the copy from which to migrate and enterthe corresponding number

v Choose the copy you wish to save and enter thecorresponding number

v Choose the copy you wish to override and enter thecorresponding number

The process has given you a set of choices, and you arenow being asked to choose one.

System action: System waits for response.

VMF2851R • VMF2858R


User response: Choose an option and press ENTER.

VMF2860I processtype processing started on useriduserid. Planning for action of prodidcompid

Explanation: The indicated processing has started andidentification of the user ID the processing is beingdone from is provided. The type of planning beingdone for the specified product is also identified. Thisinformation is logged in the header of the PLANINFOfile.



VMF2862I messages


v The following memos are available for productprodid

v The following components are available forproduct prodid

v The following copies are available for productprodid

v The following copies exist for the producttailorable file fn ft

v The following is a list of $PPF files that can beoverridden for product prodid

Information message showing what is available tochoose from.



VMF2865W messages


v The file $UPDATE $PARTCAT A has been created.This is a list of files which could not be entered inVMSES PARTCAT files.VMFCOPY called VMFSIM MODIFY. VMFSIMMODIFY attempted to place part entries in theappropriate VMSES PARTCAT files. One or more ofthese entries could not be entered successfully. Thefailing entries have been listed in a file, $UPDATE$PARTCAT, on your A disk.

v The file $UPDATE $PARTCAT A has been updated.This is a list of files which could not be entered inVMSES PARTCAT files.VMFCOPY called VMFSIM MODIFY. VMFSIMMODIFY attempted to place part entries in theappropriate VMSES PARTCAT files. One or more ofthese entries could not be entered successfully. Thefailing entries have been added to an existing file,$UPDATE $PARTCAT, on your A disk.



VMF2866I messages


v VMSES PARTCAT will not be copied. It is onlyvalid for the disk or directory it was created on. Anattempt was made to copy the parts catalog, VMSESPARTCAT, from one disk or directory to another.Parts catalogs are valid only for the disk or directorythey are created and updated on. Therefore, the fileVMSES PARTCAT should not be copied to any otherdisk or directory.

v VMSES PARTCAT fm will not be erased unlessVMFERASE deletes all the records from it. Anattempt was made to erase VMSES PARTCAT fromthe specified mode by including it directly in theinput to VMFERASE. Parts catalogs are managed bythe system, so the request to erase VMSES PARTCATwill be ignored. However, if VMFERASE deletes allthe records in a parts catalog, the file will beautomatically erased.

System action: Command processing continues withthe other files to copy or erase.


VMF2867W messages


v No files will be copied. The source file name andfile type of VMSES PARTCAT was used as input tothe VMFCOPY command. Parts catalogs are validonly for the disk or directory they are created andupdated on. Therefore, the file VMSES PARTCATwill not be copied.

v There are no parts cataloged in VMSES PARTCATfm for product prodid that match the file identifier fnft. No files will be copied. Command VMFCOPYdid not copy any files to the target location for oneof these reasons:

– The specified source files are not cataloged in fileVMSES PARTCAT fm.

– The :PRODID. tag does not match the productidentifier specified by the SPRODID option.

System action: RC=4. Command processing continues.No files are copied. The system status remains thesame.


VMF2869I File VMSES PARTCAT has catalogentries for product prodid that do notexist on {vdev|dirid (fm)}

Explanation: The VMFCOPY command found catalog



entries in file VMSES PARTCAT fm for product prodid,but the files do not exist on the disk or directory. Themissing files may or may not match the filespecification entered when the VMFCOPY commandwas started.


User response: Review file VMSES PARTCAT on thespecified disk or directory. Determine if there is aproblem and take corrective action if necessary.

VMF2870I The following files will now beprocessed

Explanation: The Restore Tailorings phase of themigration process is going to process tailored filesusing the split screen editor and/or browse screenviewing facilities.

System action: A list of tailored files is displayed andyou are prompted to continue or quit.

User response: Determine whether processing shouldcontinue.

VMF2871W Part fn ft cannot be added to the VMSESPARTCAT because its file name or filetype contains a colon

Explanation: VMFCOPY could not update the VMSESPARTCAT file for the specified part because a colon isnot a supported character for data in a VMSES/E table.


User response: If you want the specified part to becataloged, you must rename it without using the coloncharacter.

VMF2886I Disk fm {vdev|dirid} is full. Attemptingto increase the size.

Explanation: Copying a file to the disk has caused thea disk full condition. An internal process is called toincrease the disk size.



VMF2890I Object objname not {built | deleted}.prodid1 superseded by higher releaselevel product ID prodid2

Explanation: The specified object was not built or notdeleted because the product being serviced issuperseded by a higher release level product.


User response: Subsequent messages VMF2891Wand/or VMF2891I provide additional information onwhat action, if any, needs to be taken. MessageVMF2891W specifies a corresponding APAR or local

modification for the higher release level product thatneeds to be applied to obtain an updated object or todelete the object. If message VMF2891W specifies anAPAR, service should not be placed into production(that is, PUT2PROD should not be run) until that APARhas been applied to the higher release level product. Ifmessage VMF2891W specifies a local modification, themodification should be assessed, and applied, ifappropriate, before the PUT2PROD command is used.For message VMF2891I, the corresponding APAR isincluded in the base of the higher release level product,so no additional action is needed.

VMF2891I APAR aparnum is included in the basehigher release level prodid%compname

Explanation: Previous message VMF2890I indicatedthat an object was not built or not deleted because theproduct being serviced is superseded by a higherrelease level product. The specified APAR is includedin the base of the higher release level product.



VMF2891W {APAR aparnum | Local modificationmodid} needs to be applied on higherrelease level prodid%compname

Explanation: Previous message VMF2890I indicatedthat an object was not built or not deleted because theproduct being serviced is superseded by a higherrelease level product. The APAR or local modification(or both, if appropriate) specified by this messageneeds to be applied to the specified higher release levelproduct to obtain an updated object or to delete theobject.


User response: If an APAR number is specified, log onto the maintenance user ID corresponding to thehighest release level in the SSI cluster. To determine ifthe APAR is already applied, issue the commandSERVICE prodid%compname STATUS aparnum, whereprodid%compname is the specified higher release leveland aparnum is the specified APAR. If the APAR isapplied, no further action is needed. If it is not applied,apply the specified APAR on the higher release level toobtain an updated object.

If a local modification ID is specified and the localmodification applies to the higher release level, log onto the maintenance user ID corresponding to thehighest release level in the SSI cluster. To determine ifthe local modification was already applied, issue thecommand VMFINFO ppfname compname (SETUP. On the"Serviceable Parts/Usable Forms Query Panel," enterthe object name given in previous message VMF2890Iand select "Service level of part(s)." If the localmodification was already applied, no further action isneeded. If it was not applied, apply the specified local



modification on the higher release level to obtain anupdated object.

VMF2899W SMAPI utility utility has been servicedand needs to be restarted

Explanation: Files associated with the specifiedSMAPI utility have been serviced and updated on theMAINTxxx 400 minidisk. Because these utility serversare part of the larger SMAPI environment, theSERVICE EXEC cannot automatically restart thespecified server.


User response: Restart the specified SMAPI utilityserver, either individually or by restarting the entireSMAPI environment.

VMF2900I Data on field field is valid

Explanation: You asked for help on a field that is notin error.



VMF2901E messages


v No data was entered on the input field

v {vdev|dirid|userid|filepoolid} is not valid input data

Incorrect data was entered on a field. The data could beincorrect for one of several reasons.

1. No data was entered on an input field.

2. A minidisk address was specified incorrectly. Validaddresses are hexadecimal numbers from 0 to FFFF.

3. A restricted logon userid, userid, was entered.

4. The filepoolid filepoolid specified is not a validfilepoolid.

5. The userid userid contains characters that are notvalid.


Command processing stops because of the commandsyntax error.

User response: Correct the entry at the cursorposition.

VMF2902E The SFS directory identifier dirid is notvalid

Explanation: The directory identifier entered on aninput field is not a valid directory identifier. Thepossible causes are:

1. no sub-directory identifier was entered,

2. the directory identifier entered has more than eightsub-directories,

3. the filepoolid entered was not VMSYS,

4. a sub-directory name is longer than 16 characters,

5. the first character of a sub-directory was notalphabetic,

6. or there is a non-alphanumeric in the sub-directoryname.



User response: Correct the entry at the current cursorposition.

VMF2903W Cursor is not on a valid data field

Explanation: You have attempted to execute afunction on a data field that does not support thatfunction.



User response: Move the cursor to a field thatsupports the function.

VMF2904E Unsupported function key function-key

Explanation: The user pressed an unsupportedfunction key.



User response: Try another function key.

VMF2906I Type Return to exit from CMS subset ...

Explanation: The user entered CMS subset commandon the command line.


User response: Type Return and press ENTER toreturn to the panel.

VMF2907E The DCL section of the productparameter file fn ft is empty

Explanation: There are no entries in the :DCL sectionof this product parameter file.





VMF2909W You cannot change this field. This is anold setup

Explanation: You have attempted to change a productparameter file field in an existing file.

System action: Command processing continues


VMF2910W This field is in conflict with productppfname compname (prodid prodid)

Explanation: The contents of a product parameter filefield conflicts with a field in the specified productparameter file.


User response: Determine why the fields conflict anddecide if the field needs to be changed.

VMF2911W The entries in this file are in conflictwith another copy. Do you want tocontinue saving this file?

Explanation: You asked to save an override file yetthe resulting PPF will conflict with entries in anotherPPF.


User response: Either continue to save the overridefile or correct the fields that conflict with the other PPF.

VMF2912I Product parameter file override filesaved as fn ft fm

Explanation: User saved a product parameter fileoverride file.



VMF2913E The file ‘fileid’ is already assigned toanother override file in the systeminventory. Input another fileid

Explanation: You attempted to save a file that hasalready been used to define a level of a product.


Command processing stops because of the file notfound condition.

User response: Enter a new fileid.

VMF2917R Do you want to use the defaults for thisproduct? Enter 0 (No), 1 (Yes) or 2 (Exit)

Explanation: The current PPF file does not containany errors or warnings. You may use the currentsettings to install this product.


User response: Enter the number that correspondswith your choice.

VMF2918R File fn ft fm already exists. Do you wantto replace this file?

Explanation: You attempted to file an override withthe same name as an existing override file.


User response: Enter one of the options: Yes or No.

VMF2924E No default file name specified. Use‘Save As...’ to save this file

Explanation: The user tried to save a productparameter file override file in an existing file. However,no existing file could be found.



User response: Use the Save As function to save thisfile.

VMF2926E Selection number is not valid

Explanation: You have entered a selection number fora function that cannot be performed because of errors.Data entered on the data entry lines of the panel maybe in error or the fileid specified during a Savefunction cannot be found.


User response: You can do one of the following:

1. Correct the errors in the data or specify a validfileid and reselect the number selection.

2. Enter a different selection number.

VMF2927E Error found in data. Data cannot besaved

Explanation: You have tried to save the data on thepanel, but because of errors in the data, the file cannotbe saved.

System action: System displays a window and waitsfor a response.

User response: Correct the problems and reissue thecommand.

VMF2930E You cannot use the fileid of the baseproduct parameter file

Explanation: The user tried to overwrite the baseproduct parameter file with the override file.

System action: RC=24. Command processing stops



because of the command syntax error.

User response: Enter another file name.

VMF2931I There are no conflicts

Explanation: You asked to see any minidisk ordirectory conflicts and no conflicts exist.



VMF2935E Toggling is not valid for this field

Explanation: You tried to change a minidisk addressto a SFS directory identifier. However, the minidiskaddress cannot be changed. Its address is not a variablein the product parameter file.




VMF2936I command command processing is inprogress, which might require severalseconds (or minutes) to complete

Explanation: The command indicated in this messagewas issued. Based on the amount or type of data thathas to be processed, the time required for thiscommand to complete can range from several secondsto several minutes. During this period, no messages aredisplayed on the console.



VMF2999I text

Explanation: Contextual information, with variablecontent, is provided by this message for diagnosticpurposes. Such messages are produced only whenprogram diagnostic functions have been activated.



VMF3001E R/W access not established for resource:{resource | fm}

Explanation: The indicated minidisk or SFS directoryresource could not be accessed with read/write status,or such status is not in effect for the resource accessedat the indicated file mode. No files can be copied tothis resource.

System action: As dictated by the command andoptions in use, command processing continues to theextent possible; otherwise, command processing stops.

System programmer response: Determine why theindicated resource cannot be acquired with read/writestatus. For minidisk resources, this condition can arisewhen another user ID has established a READ/WRITElink to the subject minidisk. For SFS directories, theuser ID running this command may lack WRITEauthority for the subject directory. Once you establishwrite access for the indicated resource, try thecommand again.

VMF3002E Cannot locate file: file_ID

Explanation: The listed file was not found at theindicated file mode. This file must be available forreference by the command in use to identify variousresources, files or file attributes that pertain to theoperation of this command.


System programmer response: Access the minidisk orSFS directory where this file resides, or determine whythe listed file is not present at the indicated file mode.For PRODUTL command use, also verify that thecorrect file name has been specified for the ctlg_nameoperand of the PRODUTL command. Then, try thecommand again.

VMF3003E No file mode is available to accessresource: resource

Explanation: All CMS file access mode letters arecurrently in use. At least one such file mode letter mustbe available to perform an access of the indicatedminidisk or SFS directory resource.


System programmer response: Review your currentuse of file access modes and release at least one filemode for the subject command in use. Then, try thecommand again.

VMF3005E messages


v Invocation error; PPF file name not specified

v Invocation error; Component name not specified

v Invocation error; Catalog name not specified

v Invocation error; Catalog section not specified

v Invocation error; Operand(s) not recognized: text

A required command operand has been omitted or anextraneous operand has been supplied.


System programmer response: Review the operandsused with your command and ensure that all required(and supported) operands are specified when you nextissue the command. Consult the PRODUTL commanddocumentation in z/VM: VMSES/E Introduction and



Reference for more information about operands thatpertain to this command.

VMF3009E :DCL. variable name 'name' cannot beresolved or is not valid

Explanation: An attempt to resolve the indicatedVMSES/E variable name to its corresponding value, asdefined within the variable declaration (:DCL.) sectionof the PPF file referenced by the command, was notsuccessful.


System programmer response: Review the relevantPPF file to determine why the indicated variable namecannot be resolved. For example, a misspelling of thevariable name in a catalog file entry, or removal of a:DCL. definition in the PPF file (via a PPF override)might cause this problem. Also, verify that entrieswithin the pertinent CATALOG file are correct. Correctany problems, then try the command again.

VMF3010E Variable name 'name' is not valid

Explanation: A CATALOG file record error has beendetected. A source or target variable name wasexpected, but such a value was not present.


System programmer response: Refer to accompanyingmessage VMFxxx3015 for information about the specificentry that is in error. Review the CATALOG file that isin use for syntax or other errors. Correct any problems,then try the command again.

VMF3011E Unexpected error rc reading file 'file_ID'

Explanation: An error occurred while attempting toread the indicated file.


System programmer response: Verify access to thelisted file, and that the file can be read. For moreinformation about the '<' PIPE stage return code rccited in the message, see z/VM: CMS Pipelines User'sGuide and Reference. Correct the problem, then try thecommand again.

VMF3013W No entries are available for processing

Explanation: The designated CATALOG file does notcontain any entries that identify files to be processed bythe PRODUTL command, or the designated sectioncontains no such entries.


System programmer response: Verify that the correctCATALOG file name and section name have been

specified as part of the command. If correct, review thecontent of the relevant catalog file and section, andensure that the entries present exist in proper form;that is, the entries are neither all commentary data norall marked with the entry-bypass operator (a hyphen).Also, verify that a corresponding end tag is present forthe designated catalog section. Correct any problems,then try the command again.


Explanation:

VMF3015E Error detected while processing {catalog| exclusion} entry:

VMF3015E entry_text

A syntax or other error condition has been identifiedwhile processing the indicated catalog file entry.


System programmer response: Refer to theaccompanying message VMFxxx3010 or VMFxxx3025for detailed information about why the indicated entryis in error. Correct this problem, then try the commandagain.

VMF3017E Option 'text' is not recognized or is notvalid

Explanation: A command option has been specifiedthat is not supported.


System programmer response: Review the optionsused with your command and ensure that onlysupported options are specified when you next issuethe command. Consult the PRODUTL commanddocumentation in z/VM: VMSES/E Introduction andReference for more information about options thatpertain to this command.


Explanation:

VMF3020W Error appending saved message log(file1_ID)

VMF3020W to current message log (file2_ID);

VMF3020W command completed with RC = rc

When the command in use runs, the cumulativemessage log is saved with a file type of $SAVELOG sothe $MSGLOG file for the current invocation can becreated. These log files are then consolidated by thecommand as it completes. However, the COPYFILEcommand used for this purpose failed with the



indicated return code. The $MSGLOG and the$SAVELOG files are not consolidated, and remain asdistinct files.


System programmer response: A probable cause forthis message is a lack of sufficient storage space for theminidisk or directory at which the indicated log filesreside. For more information about the COPYFILEreturn code cited in the message, see z/VM: CMSCommands and Utilities Reference.

Upon command completion, it might be necessary toreview the contents of each log file and manuallyconsolidate them. You can consolidate the log file byappending the contents of the $SAVELOG file to theend of $MSGLOG file, and then deleting the$SAVELOG file.

VMF3025E Incorrect number of operands detected

Explanation: A syntax error has been identified whileprocessing the indicated catalog file entry.


System programmer response: For information aboutthe specific entry that is in error, refer to accompanyingmessage VMFxxx3015. Review the CATALOG file thatis in use for possible syntax or other errors. Correct anyerrors, then try the command again.

VMF3026W File entry has been bypassed

Explanation: Processing for a catalog file entry hasended prematurely due to a problem associated withthat entry.


System programmer response: For information aboutthe specific entry that has been bypassed, as well as thereason for this action, refer to accompanying messages.Correct any problems, then try the command again.


Explanation:

VMF3027E Error renaming existing log file'file1_ID';

VMF3027E command command completed with RC= rc

When the command in use runs, the cumulativemessage log is saved with a file type of $SAVELOG sothe $MSGLOG file for the current invocation can becreated. These log files are then consolidated by the

command as it completes. However, the RENAMEcommand used to save the cumulative message logfailed with the indicated return code.


System programmer response: A probable cause forthis error is the presence of an existing $SAVELOG filethat remains from a prior command invocation that didnot complete normally. For more information about theRENAME return code cited in the message, see z/VM:CMS Commands and Utilities Reference.

Review the contents of each log file and manuallyconsolidate them. Consolidate the log file by appendingthe contents of the $SAVELOG file to the end of$MSGLOG file, and then deleting the $SAVELOG file.

VMF3028E PPF :DCL. information not found forcomponent ID 'comp_ID'

Explanation: The PPF file referenced by the commanddoes not contain any records in the variable declaration(:DCL.) section associated with the listed componentID.


System programmer response: Review the relevantPPF file to determine the cause for this problem. Forthe PRODUTL command, verify that the component IDoperand specified for your command is correct. Ifnecessary, review the relevant PPF file to determine thecause for this problem. Correct any errors, then try thecommand again.

VMF3029W Write access not verified for resource:resource

Explanation: The indicated resource was not acquiredand accessed with a CMS file mode. Thus, writecapability for this resource could not be confirmed.


System programmer response: This message is issuedonly for test mode processing and is intended to makeyou aware of a condition that might have bearing onproblems that occur later.


Explanation:

VMF3033W Error(s) encountered restoringaccess/search order;

VMF3033W Original search order may not havebeen fully restored

Because the PRODUTL command alters the CMS searchorder during its operation, information about accessedresources is saved at command invocation. Thisinformation is then used to restore the original search



order upon command completion. However, one ormore problems occurred when restoration of theoriginal search order was attempted.


System programmer response: Review accompanyingmessages for information about problems associatedwith the handling of specific resources. You can use thePRODUTL command TRACE option to obtain detailedinformation about such problems. If this problempersists, contact the IBM support center for assistance.


Explanation:

VMF3035W command was interrupted the last timeit was run;

VMF3035W file1_ID has been restored from thesaved message log:

VMF3035W file2_ID

When the command in use runs, the cumulativemessage log is saved with a file type of $SAVELOG sothe $MSGLOG file for the current invocation can becreated. These log files are then consolidated by thecommand as it completes. Locating a $SAVELOG fileduring command initialization indicates a previousinvocation did not complete normally. Thus, thecommand attempts to consolidate the message log filesby appending the $SAVELOG file to the $MSGLOG file(as it should have been at the conclusion of theprevious invocation).


System programmer response: This message is issuedto make you aware that unexpected results wereproduced the last time this command was run. It mightbe necessary to take future action if other problemsarise with management of the cumulative message logthat corresponds to the subject command.

VMF3036W Copy not performed for "source" file'file_ID'

Explanation: The indicated file could not be copied tothe intended destination.


System programmer response: Refer to accompanyingmessages for information about why the indicated filecould not be copied. Correct any problems, then try thecommand again.

VMF3038I command command completed with RC= rc

Explanation: The command cited in the messagecompleted with the indicated return code. In mostinstances, this message is used to report warning or

error conditions associated with a specific command.However, it might also be issued for informationalpurposes, as when command tracing is performed.


System programmer response: Refer to accompanyingmessages to determine if a problem exists and whetheraction to resolve such a problem is appropriate.

VMF3041E PPF :PRODID. information not foundfor component 'compname'

Explanation: Within the designated PPF file, thedefinition of the indicated component does not includea required product identifier (:PRODID.) record.


System programmer response: Verify that the correctcomponent name has been specified as part of thecommand. Alternatively, review the content of therelevant PPF file and any PPF file overrides todetermine the cause for this error. Correct anyproblems, then try the command again. If necessary,contact the IBM support center for assistance.

VMF3042W messages


v VMF3042W Reason: Cannot verify existence of file'file_ID'

v VMF3042W Reason: Comparison of "source" and"target" files failed

v VMF3042W Reason: "Source" and "target" filedifferences detected

v VMF3042I Reason: "Target" file does not differ from"source" file

v VMF3042W Reason: File 'file_ID' does not exist

One of these messages is issued in conjunction withmessage VMFxxx3044 to explain why the copyoperation for a given file is bypassed.


System programmer response: Refer to accompanyingmessages to determine if a problem exists and whetheraction to resolve such a problem is appropriate. Ifnecessary, consult the PRODUTL commanddocumentation in z/VM: VMSES/E Introduction andReference for more information and review the entries inthe subject catalog file section.

VMF3043W File file_ID (resource) has been updated;its content should be reviewed forchanges that might affect your use ofthe production copy of this file

Explanation: The content of the indicated sample file,located on the listed resource, has been updated byservice that has been installed on the system. The



changes to this file are associated with functionalchanges to one or more program components that havelikewise been affected by service.


System programmer response: Upon completion ofthe command, review the content of the indicated fileand determine whether the changes that have beenintroduced affect your use of any customized,production-use counterpart to this file. For moreinformation, consult the descriptions of these changesdescribed in the relevant APAR or other servicedocumentation.

In some instances, it might help to compare theupdated file with its base-level counterpart, so you canidentify specific changes that might not be apparent ina customized, production-use file.

VMF3044W {Copy | Comparison} {will be} bypassedfor "source" file 'file_ID' (resource)

Explanation: Processing of the indicated file, locatedon the listed resource, ended prematurely due to aproblem associated with this file, or with an existing,production-use counterpart. The subject file either isnot copied to the production build minidisk, or is notcompared with its production counterpart, as indicatedby the message.


System programmer response: Refer to accompanyingmessages to determine if a problem exists and whetheraction to resolve such a problem is appropriate. Ifnecessary, consult the PRODUTL commanddocumentation in z/VM: VMSES/E Introduction andReference for more information and review the entries inthe subject catalog file section.


Explanation:

VMF3046E Options (options) specified for "source"

VMF3046E file 'file_ID' are not valid;

VMF3046E Differing option delimiters have beenspecified

The catalog entry that corresponds to the indicated fileincludes multiple file processing options. These optionshave been separated using both of the available optiondelimiters: the slash (/) and the period (.). The use ofboth these delimiters for a given entry is not permitted.


System programmer response: Review the CATALOGfile entry that corresponds to the indicated file, thenmodify the entry so only one of the available optiondelimiters is used to separate each processing option. Ifnecessary, consult the PRODUTL command

documentation in z/VM: VMSES/E Introduction andReference for more information. After your changes arecomplete, try the command again.


Explanation:

VMF3047W Error erasing previous log file 'file_ID';

VMF3047W command command completed with RC= rc

When the command in use runs, the cumulativemessage log is saved with a file type of $SAVELOG sothe $MSGLOG file for the current invocation can becreated. These log files are then consolidated by thecommand as it completes. However, the ERASEcommand for this purpose failed with the indicatedreturn code. The $MSGLOG and the $SAVELOG filesare not consolidated and remain as distinct files.


System programmer response: A probable cause forthis error is the presence of an existing $SAVELOG filethat remains from a prior command invocation that didnot complete normally. If necessary, for moreinformation about the ERASE return code cited in themessage, see z/VM: CMS Commands and UtilitiesReference.

Upon command completion, it might be necessary toreview the contents of each log file and manuallyconsolidate them. You can consolidate the log file byappending the contents of the $SAVELOG file to theend of $MSGLOG file, and then deleting the$SAVELOG file.

VMF3048E Option (option) specified for "source" file'file_ID' is not valid; message

Explanation: message can be one of the following:

v VMF3048E Associated file name is not a wildcard(*)

v VMF3048E No exclude section has been identified

v VMF3048E Exclude section 'name' reference isrecursive

v VMF3048E Exclude section 'name' not found orcontains no entries

v VMF3048E Option is not recognized or is notsupported

v VMF3048E Options cannot be specified as part of afile type

The catalog entry that corresponds to the listed fileincludes a file processing option. However, this optionhas either been incorrectly specified or refers to a fileexclude section that cannot be used for the reasonindicated.




System programmer response: Review the subjectCATALOG file, as well as any pertinent file entries, toidentify specific corrections that are needed to resolvethe problem. If necessary, consult the PRODUTLcommand documentation in z/VM: VMSES/EIntroduction and Reference for more information. Afteryour changes are complete, try the command again.

VMF3052W Unexpected {exclusion | wildcard} entryencountered: entry_text

Explanation: An entry of the indicated type is presentin the catalog file section that is being processed. Suchentries are permitted only within certain catalog filesections, not this one. The indicated entry is ignored.


System programmer response: Review the subjectCATALOG file, as well as any pertinent file entries, toidentify specific corrections that are needed to resolvethe problem. If necessary, consult the PRODUTLcommand documentation in z/VM: VMSES/EIntroduction and Reference for more information. Afteryour changes are complete, try the command again.

VMF3054I messages


v VMF3054I Files successfully processed: number

v VMF3054E Files not processed due to errors: number

This message reports the number of files that have beensuccessfully processed for a given wildcard catalog fileentry, or the number of such files for which processingerrors were encountered.

System action: If file processing errors are not severe,command processing continues.

System programmer response: When an errorcondition is reported, this message is accompanied bymessage VMF055, which provides:

v A summary of individual return codes and relevantcommand and file information

v Specific VMSES/E VMFCOPY command messagesand results for the files for which errors wereencountered.

Use the information provided by these messages toresolve any problems before using the PRODUTLcommand again.

VMF3055I VMFCOPY command error summaryfollows. Options used for all commands:VMFCOPY options

Explanation: This message provides summaryinformation about errors encountered for one or moreof the files processed by the PRODUTL command. The

following example shows the general format of theoutput:

rc : VMFCOPY file_ID1 file_ID2rc : VMFCOPY file_ID1 file_ID2...VMF3055I VMSES/E VMFCOPY commanderror information followsVMSES/E message identifier and textVMSES/E message identifier and text...

The VMFCOPY command options used for processingall such files are indicated first, followed by a list of thefiles for which errors were encountered. For each itemlisted, the relevant VMFCOPY error return code iscited, followed by the affected source file file_ID1 andits counterpart destination file, file_ID2. The messagesproduced by the VMSES/E VMFCOPY command forthe affected files are listed in summary form at the endof this message.


System programmer response: Use the informationprovided by this message to determine why theindicated files could not be copied to their intendeddestinations. If necessary, consult the appropriatecommand documentation for more information.Resolve any problems, then try the PRODUTLcommand again.

VMF3057W Null exclude section detected for option(option) specified for file file_ID

Explanation: The catalog file entry that corresponds tothe indicated file includes an exclusion option for whichno catalog section name has been specified.


System programmer response: Review the CATALOGfile entry that corresponds to the indicated file, thenmodify the entry to include an appropriate catalogsection name. If necessary, consult the PRODUTLcommand documentation in z/VM: VMSES/EIntroduction and Reference for more information. Afteryour changes are complete, try the command again.

VMF3060W Cannot verify existence of file 'file_ID'

Explanation: The listed file was not found at theindicated file mode, or a problem occurred indetermining whether such a file exists. A resourceintended as the target for a file copy operation haspreviously been determined to be unavailable. Themessage is reported for each processed catalog entryfor which a file is destined for that resource.


System programmer response: This message is issuedonly for test mode processing. The message confirmsthat the catalog entry associated with the indicated filehas been processed to the extent possible.


VMF3061E Option option cannot be used when a'type' catalog section is processed

Explanation: Use of the option listed in the messageconflicts with the type of catalog section that is to beprocessed by the PRODUTL command. For certaincatalog section types, some command processingoptions are restricted from use because their effect oncommand actions or results conflicts with the nature ofthe files listed within the indicated catalog section.


System programmer response: Confirm that thecatalog section name and all options specified for thePRODUTL command are correct. If necessary, reviewthe PRODUTL command documentation that describesthe CATALOG file and its structure in z/VM: VMSES/EIntroduction and Reference. Correct any problems, thenretry the command.

VMF3063I File comparisons performed:comp_countPaired file differencesidentified: diff_countSource files notavailable for comparison:unavailable_count

Explanation: This message summarizes filecomparison results obtained for source and target filesthat pertain to the catalog section that has beenprocessed. The following counter values are displayed:

v comp_count: The total number of file comparisonsperformed.

v diff_count: The number of paired files (that is, asource file and its target counterpart) for which adifference in content was identified.

v unavail_count: The number of source files not presentin the “source” resource for which a comparisonwith a corresponding target file was not possible.


System programmer response: If non-zero diff_countand unavail_count values were reported, review theaccompanying messages for more information aboutthe files that pertain to the counter value of interest,and take appropriate actions to resolve any problems.

VMF3064I Catalog entries / files to be processed:count

Explanation: This message displays the number ofentries identified for processing. Depending on theformat of the entries in the subject catalog section, thenumber reported might not reflect the total number offiles that will be processed by the command.


System programmer response: None.



ITN2000E - ITN2050E

ITN2000E messages


v Additional input operands are required for theinvocation of this command.

v Unexpected data found after the closingparenthesis: command_line_data

Either an incorrect number of operands were specifiedon the command, or unexpected data was found afterthe closing parenthesis on the command.

User response: Update the command and resubmit it.Check the command syntax for additional information.

ITN2000I date time message_number The ITNVTSTRprogram has begun processing withcommand: command

Explanation: This is the initialization messageindicating that the ITNVTSTR program wassuccessfully initialized.

User response: No action required.

ITN2001I messages


v Unbundle process starting on date at time for orderorder_number

v Unbundle process ending on date at time

v date time Order order_number file package_filenameunpackaged file filename to target_disk/directory

These messages address the actual start and ending ofthe unbundling process.


ITN2002I messages


v Delete process starting on date at time

v Delete process ending on date at time

v date time File filename deleted fromtarget_disk/directory

v There are no requests for file deletion

These messages mark the start and ending of the file(ENVELOPE and PACKAGE) delete process.


ITN2003I messages


v The ITNVTSTR program was unsuccessful

v The ITNVTSTR program was unsuccessful fororder order_number

v The ITNVTSTR program was successful

v The ITNVTSTR program was successful for orderorder_number

These messages represent the concluding message forITNVTSTR EXEC with regard to successful processingof a specific order.

User response: If the order was processedunsuccessfully, then the user should investigate thecause of the failure.

ITN2004I The following messages were issued:----------------------------------------------------

Explanation: This message is placed in the NOTIFYfile to delimit the message section.


ITN2005I Letter for order_format order order_numberfollows:------------------------------------------------------

Explanation: This message is used in the NOTIFY fileand marks the start of the CUSTDOC data (orderinformation).


ITN2006I messages


v Archive process starting on date at time for orderorder_number

v Archive process ending on date at time

v date time Order order_number file filename archived totarget_disk/directory

These messages mark the start and ending of thearchive process.


ITN2006W Archive will not be performed, since itmaps to the A-disk

Explanation: Either an ITN PROFILE file or acommand override is requesting archiving of thecurrent order file, but the archive target is the user'scurrent A-disk. This is not allowed.

User response: Several actions can be taken by theuser:

v Change the A-disk.

v Turn off archiving.

v Retarget the archiving.

ITN2000E • ITN2006W


ITN2007I messages


v Install process starting on date at time for orderorder_number

v Install process ending on date at time

v date time Order order_number file package_filenameinstalled

These messages address the actual start and ending ofthe install process.


ITN2007W messages


v Install process ending on date at time with warnings

v date time Order order_number file package_filenameinstalled with warnings

The install process has completed with warnings fromat least one of the called VMSES/E commands.

User response: Review the console log and theVMSES/E message logs for the warning condition.

ITN2008E messages


v An error was encountered installing orderorder_number, Rc = return_code

v Install was not performed for order order_numberbecause no service envelope files were found

Either an error condition was returned from one of thecalled VMSES/E commands or there was no serviceenvelope to install.

User response: If an error was encountered installingthe order, review the console log and the VMSES/Emessage logs for the error condition. Correct the error,and restart the install process by entering theVMFSUFIN command for the failing product with theRESTART option. If no service envelope was found,contact your IBM Service Representative for assistance.

ITN2010E messages


v Option option was given an invalid value of (value)

v An invalid option (option) was found

An ITN PROFILE file or a command option wasspecified with an invalid value, or an incorrect optionwas specified.

User response: Change the option or its value andresubmit the command.

ITN2011E messages


v An error occurred in PIPE pipe_name while readingthe user profile filename, Rc = return_code

v An error occurred in PIPE pipe_name, Rc =return_code

A Pipeline command with the specified name failedwith the indicated return code possibly when trying toread the indicated file.

User response: Contact your IBM ServiceRepresentative with the issued message information.

ITN2011W An error occurred in PIPE pipe_name, Rc= return_code

Explanation: A Pipeline command with the specifiedname failed with the indicated return code.

User response: No user action is required, since this isjust a warning of a failure for a noncritical command.

ITN2012E Problems were encountered accessingdirectory directory as mode access_mode{FORCERO|FORCERW}, Rc = return_code

Explanation: The indicated directory could not beaccessed.

User response: Contact your system programmer forcorrective action. The most probable cause is that spaceor authorization was not set up correctly for theindicated directory.

ITN2013E Problems were encountered accessingminidisk minidisk_address as modeaccess_mode, Rc = return_code

Explanation: An error occurred when trying to accessthe indicated minidisk. The access return code is alsosupplied.

User response: With the message information, attemptto perform error determination and correction. Ifsuccessful, re-issue the command; otherwise, contactyour system programmer for further assistance.

ITN2014E messages


v A LINK attempt for minidisk_owner minidisk_addressas link_address link_mode failed, Rc = return_code

v A LINK and ACCESS attempt for minidisk_ownerminidisk_address failed

The indicated minidisk could not be properly linkedand accessed.

User response: Contact your system programmer to

ITN2007I • ITN2014E


ensure that minidisk definitions and authorizationshave been correctly set up.

ITN2015E [No free modes are available to performan ACCESS | No free addresses werefound in the range x'100' to x'5FF']

Explanation: All available access modes or diskaddresses (in the range X'100' to X'5FF') are in use.

User response: Free up additional modes or addresses(in the required range); then retry the command.

ITN2016E messages


v COPYFILE error was encountered copying filefrom_filename to to_filename, Rc = return_code

v COPYFILE error was encountered copying filefrom_filename starting at record starting_index fornumber_of_records to to_filename, Rc = return_code

A COPYFILE error has occurred when copying all or apart of the indicated file from one file to another.

User response: Ensure that there is sufficient space onthe target disk to copy the file. Also, ensure that youare authorized to write to the target disk.

ITN2017I Delete of file filename was not done,since it was not found

Explanation: An erase of the indicated file wasrequested, but the file was not found. Processingcontinues.


ITN2017W ERASE error was encountered erasingfile filename, Rc = return_code

Explanation: An expected file was not found whentrying to erase it. A warning message is issued andprocessing continues.


ITN2018E messages


v A {DETERSE|TERSE} (UNPACK encountered anerror with file filename, Rc = return_code

v Package unbundling requires a DETERSEMODULE or a TERSE MODULE, neither can befound

Either the DETERSE and TERSE modules are notavailable or an error occurred when attempting to runone of them.

User response: Ensure that the DETERSE module orthe TERSE module is available. Also ensure that there

is sufficient space on the target disk to unbundle thepackage. If problems have been encountered whenrunning DETERSE or TERSE, contact your IBM ServiceRepresentative for additional assistance.

ITN2019W A SENDFILE error was encounteredtrying to send file filename to user_target,Rc = return_code

Explanation: A SENDFILE error occurred in trying tosend the indicated file to the indicated user. The returncode from this attempt is also displayed.

User response: From the message information,attempt to correct the problem. If the problem can notbe corrected, contact your IBM Service Representative.Because this message is a warning, it does notrepresent a serious processing problem. The real erroris the probable loss of the NOTIFY file for this order.

ITN2020E messages


v File filename cannot be found, Rc = return_code

v Error occurred reading file filename, Rc = return_code

v No comment records were found in file filename,these contain the processing control information

A problem was encountered when attempting to accessand read the indicated ENVELOPE file.

User response: An apparent problem has occurred inthe ordering process. Ensure that the ENVELOPE file isstored on the A-disk and is in a readable format. If theproblem cannot be corrected, contact your IBM ServiceRepresentative for further assistance.

ITN2021E messages


v Control section section_name in file envelope_filenamemust start with this keyword, followed bysecond_keyword

v Control section section_name in file envelope_filenamemust end with this keyword, followed bysecond_keyword

v Control record or section_name is missing in fileenvelope_filename

v Control records or sections names are missing infile envelope_filename

v Control record or section_name was found a secondtime in file envelope_filename

v No data was found between the section_name controlrecords in file envelope_filename

v Control record name is missing data after thekeyword in file envelope_filename

v Control record OPSYS has a value value that isdifferent than VM in file envelope_filename

ITN2015E • ITN2021E


v Control record name is missing in fileenvelope_filename

v Control record name has a value value but value isexpected in file envelope_filename

v Control record name has a value of value but apositive whole number was expected in fileenvelope_filename

v Control record VMFPLCD_FMT has a value of YESindicating that a filetype value of SERVLINK andnot filetype was expected for record NAME in fileenvelope_filename

v A filename and filetype (2 values) are expected on aNAME record in file envelope_filename

v Record VMFPLCD_FMT had an invalid value ofvalue specified in file envelope_filename, valid valuesare "YES NO"

An error exists in the structure of this order'sENVELOPE file.

User response: Contact your IBM ServiceRepresentative for correction and retransmission of theorder.

ITN2022I The ITNVTSTR EXEC at levelhost_tool_level does not match the levelthat the order was packaged atpackaging_level as specified in fileenvelope_filename

Explanation: A mismatch exists between the currentlevel of the VMSES/E ITNVTSTR EXEC and thepackaging level of the transmitted files. Processingcontinues.

User response: It is very likely that no action willneed to be taken. If processing should fail, it mayrequire upgrading the level of the packaged files, thetool, or both.

ITN2023E A mismatch exists in the number ofpackaged files as reported in fileenvelope_filename on the FILECNT record(filecnt_value) and the number of FILEsections (file_sections_found)

Explanation: The number of FILE sections in theENVELOPE file does not match the expected numberof files as provided on the FILECNT record in thissame file.

User response: Contact your IBM ServiceRepresentative to provide corrective action. Either orboth of the ENVELOPE and PACKAGE files are inerror.

ITN2024E The package_filename package filecontains number_of records, but onlynumber of these records are referenced inthe FILE section in file envelope_filename

Explanation: A mismatch exists in the number ofrecords that exist in the PACKAGE file and thosereferenced by the ENVELOPE file. They need to matchexactly.

User response: Contact your IBM ServiceRepresentative to provide corrective action. Either theENVELOPE file or the PACKAGE file, or both files, arein error.

ITN2025E The START record with a value ofrecord_index for FILE packaged_filenamedoes not point to the next packagerecord of running_record_index in fileenvelope_filename

Explanation: The ENVELOPE file contains informationon the packaged files in the corresponding PACKAGEfile. In this ENVELOPE file, each of the packaged filesmust have a START index. This value is compared tothe end of the previous packaged file to ensure therecords are contiguous; otherwise, this error situation isflagged.

User response: Contact your IBM ServiceRepresentative to provide corrective action. Either theENVELOPE file or the PACKAGE file, or both files, arein error.

ITN2026E The RECORDS record with a value ofnumber_of_records for FILEpackaged_filename in file envelope_filenameresults in an index that is larger thanthe package file

Explanation: The ENVELOPE file contains informationon one of the packaged files with regards to thenumber of records that it contains. This data whencoupled with the starting index of the packaged filewould exceed the size of the PACKAGE file.

User response: Contact your IBM ServiceRepresentative to provide corrective action. Either orboth of the ENVELOPE and PACKAGE files are inerror.

ITN2027E When option option_name is YES, thenoption second_option_name must bespecified

Explanation: The presence of the first option with thevalue of YES requires that the second option also bespecified.

User response: Either modify the processing PROFILEor supply a command option that changes the value ofthe first option or provides a value for the secondoption.


ITN2050E messages


v Error encountered in message processing

v The message repository could not be initialized

v An invocation message could not be issued

Either the ITNUME message repository could not befound or a requested message could not be issued fromthe repository.

User response: It is possible that the ITNUMEmessage repository text file does not exist or has beencorrupted, or that the specific message does not exist. Ifthis is the case, you can attempt to rebuild the text filefrom the source repository (REPOS) file. If the text filecannot be rebuilt, contact your IBM ServiceRepresentative for further assistance.

ITN2050E



Notices

This information was developed for products and services offered in the US. Thismaterial might be available from IBM in other languages. However, you may berequired to own a copy of the product or product version in that language in orderto access it.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

For license inquiries regarding double-byte character set (DBCS) information,contact the IBM Intellectual Property Department in your country or sendinquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer ofexpress or implied warranties in certain transactions, therefore, this statement maynot apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided forconvenience only and do not in any manner serve as an endorsement of those


websites. The materials at those websites are not part of the materials for this IBMproduct and use of those websites is at your own risk.

IBM may use or distribute any of the information you provide in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

The performance data and client examples cited are presented for illustrativepurposes only. Actual performance results may vary depending on specificconfigurations and operating conditions.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

Statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

This information may contain examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to actual people or business enterprises is entirelycoincidental.

COPYRIGHT LICENSE:

This information may contain sample application programs in source language,which illustrate programming techniques on various operating platforms. You maycopy, modify, and distribute these sample programs in any form without paymentto IBM, for the purposes of developing, using, marketing or distributingapplication programs conforming to the application programming interface for theoperating platform for which the sample programs are written. These exampleshave not been thoroughly tested under all conditions. IBM, therefore, cannotguarantee or imply reliability, serviceability, or function of these programs. The


sample programs are provided “AS IS”, without warranty of any kind. IBM shallnot be liable for any damages arising out of your use of the sample programs.

Programming Interface InformationThis publication primarily documents information that is NOT intended to be usedas Programming Interfaces of z/VM.

This publication also documents intended Programming Interfaces that allow thecustomer to write programs to obtain the services of z/VM. This information isidentified where it occurs, either by an introductory statement to a chapter orsection or by the following marking:

▌PI▐

<...Programming Interface information...>

▌PI end▐

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the web at IBM copyright andtrademark information - United States (www.ibm.com/legal/us/en/copytrade.shtml).

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Terms and Conditions for Product DocumentationPermissions for the use of these publications are granted subject to the followingterms and conditions.

Applicability

These terms and conditions are in addition to any terms of use for the IBMwebsite.

Personal Use

You may reproduce these publications for your personal, noncommercial useprovided that all proprietary notices are preserved. You may not distribute, displayor make derivative work of these publications, or any portion thereof, without theexpress consent of IBM.

Commercial Use

You may reproduce, distribute and display these publications solely within yourenterprise provided that all proprietary notices are preserved. You may not makederivative works of these publications, or reproduce, distribute or display thesepublications or any portion thereof outside your enterprise, without the expressconsent of IBM.

Notices 267

http://www.ibm.com/legal/us/en/copytrade.shtml

http://www.ibm.com/legal/us/en/copytrade.shtml

Rights

Except as expressly granted in this permission, no other permissions, licenses orrights are granted, either express or implied, to the publications or anyinformation, data, software or other intellectual property contained therein.

IBM reserves the right to withdraw the permissions granted herein whenever, in itsdiscretion, the use of the publications is detrimental to its interest or, asdetermined by IBM, the above instructions are not being properly followed.

You may not download, export or re-export this information except in fullcompliance with all applicable laws and regulations, including all United Statesexport laws and regulations.

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESEPUBLICATIONS. THE PUBLICATIONS ARE PROVIDED “AS-IS” AND WITHOUTWARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDINGBUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY,NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.

IBM Online Privacy StatementIBM Software products, including software as a service solutions, (“SoftwareOfferings”) may use cookies or other technologies to collect product usageinformation, to help improve the end user experience, to tailor interactions withthe end user, or for other purposes. In many cases no personally identifiableinformation is collected by the Software Offerings. Some of our Software Offeringscan help enable you to collect personally identifiable information. If this SoftwareOffering uses cookies to collect personally identifiable information, specificinformation about this offering’s use of cookies is set forth below.

This Software Offering does not use cookies or other technologies to collectpersonally identifiable information.

If the configurations deployed for this Software Offering provide you as customerthe ability to collect personally identifiable information from end users via cookiesand other technologies, you should seek your own legal advice about any lawsapplicable to such data collection, including any requirements for notice andconsent.

For more information about the use of various technologies, including cookies, forthese purposes, see IBM Online Privacy Statement Highlights athttp://www.ibm.com/privacy and the IBM Online Privacy Statement athttp://www.ibm.com/privacy/details in the section entitled “Cookies, WebBeacons and Other Technologies”, and the IBM Software Products andSoftware-as-a-Service Privacy Statement at http://www.ibm.com/software/info/product-privacy.


http://www.ibm.com/privacy

http://www.ibm.com/privacy/details

http://www.ibm.com/software/info/product-privacy

http://www.ibm.com/software/info/product-privacy

Glossary

For a list of z/VM terms and their definitions, see z/VM: Glossary.

The z/VM glossary is also available through the online z/VM HELP Facility, ifHELP files are installed on your z/VM system. For example, to display thedefinition of the term “dedicated device”, issue the following HELP command:help glossary dedicated device

While you are in the glossary help file, you can do additional searches:v To display the definition of a new term, type a new HELP command on the

command line:help glossary newterm

This command opens a new help file inside the previous help file. You canrepeat this process many times. The status area in the lower right corner of thescreen shows how many help files you have open. To close the current file, pressthe Quit key (PF3/F3). To exit from the HELP Facility, press the Return key(PF4/F4).

v To search for a word, phrase, or character string, type it on the command lineand press the Clocate key (PF5/F5). To find other occurrences, press the keymultiple times.The Clocate function searches from the current location to the end of the file. Itdoes not wrap. To search the whole file, press the Top key (PF2/F2) to go to thetop of the file before using Clocate.



Bibliography

This topic lists the publications in the z/VMlibrary. For abstracts of the z/VM publications,see z/VM: General Information, GC24-6193.

Where to Get z/VM InformationThe current z/VM product documentation isavailable in IBM Knowledge Center - z/VM(www.ibm.com/support/knowledgecenter/SSB27U).

You can download the z/VM publications in PDFformat from IBM Publications Center(www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss).

z/VM Base LibraryOverviewv z/VM: License Information, GC24-6200v z/VM: General Information, GC24-6193v z/VM: Glossary, GC24-6195

Installation, Migration, and Servicev z/VM: Installation Guide, GC24-6246v z/VM: Migration Guide, GC24-6201v z/VM: Service Guide, GC24-6247v z/VM: VMSES/E Introduction and Reference,

GC24-6243

Planning and Administrationv z/VM: CMS File Pool Planning, Administration,

and Operation, SC24-6167v z/VM: CMS Planning and Administration,

SC24-6171v z/VM: Connectivity, SC24-6174v z/VM: CP Planning and Administration,

SC24-6178v z/VM: Enabling z/VM for OpenStack (Support for

OpenStack Newton Release), SC24-6253v z/VM: Getting Started with Linux on z Systems,

SC24-6194v z/VM: Group Control System, SC24-6196v z/VM: I/O Configuration, SC24-6198v z/VM: Running Guest Operating Systems,

SC24-6228

v z/VM: Saved Segments Planning andAdministration, SC24-6229

v z/VM: Secure Configuration Guide, SC24-6230v z/VM: TCP/IP LDAP Administration Guide,

SC24-6236v z/VM: TCP/IP Planning and Customization,

SC24-6238v z/OS and z/VM: Hardware Configuration Manager

User's Guide, SC34-2670

Customization and Tuningv z/VM: CP Exit Customization, SC24-6176v z/VM: Performance, SC24-6208

Operation and Usev z/VM: CMS Commands and Utilities Reference,

SC24-6166v z/VM: CMS Primer, SC24-6172v z/VM: CMS User's Guide, SC24-6173v z/VM: CP Commands and Utilities Reference,

SC24-6175v z/VM: System Operation, SC24-6233v z/VM: TCP/IP User's Guide, SC24-6240v z/VM: Virtual Machine Operation, SC24-6241v z/VM: XEDIT Commands and Macros Reference,

SC24-6244v z/VM: XEDIT User's Guide, SC24-6245

Application Programmingv z/VM: CMS Application Development Guide,

SC24-6162v z/VM: CMS Application Development Guide for

Assembler, SC24-6163v z/VM: CMS Application Multitasking, SC24-6164v z/VM: CMS Callable Services Reference, SC24-6165v z/VM: CMS Macros and Functions Reference,

SC24-6168v z/VM: CMS Pipelines User's Guide and Reference,

SC24-6252v z/VM: CP Programming Services, SC24-6179v z/VM: CPI Communications User's Guide,

SC24-6180v z/VM: Enterprise Systems Architecture/Extended

Configuration Principles of Operation, SC24-6192


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

http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss

v z/VM: Language Environment User's Guide,SC24-6199

v z/VM: OpenExtensions Advanced ApplicationProgramming Tools, SC24-6202

v z/VM: OpenExtensions Callable Services Reference,SC24-6203

v z/VM: OpenExtensions Commands Reference,SC24-6204

v z/VM: OpenExtensions POSIX ConformanceDocument, GC24-6205

v z/VM: OpenExtensions User's Guide, SC24-6206v z/VM: Program Management Binder for CMS,

SC24-6211v z/VM: Reusable Server Kernel Programmer's Guide

and Reference, SC24-6220v z/VM: REXX/VM Reference, SC24-6221v z/VM: REXX/VM User's Guide, SC24-6222v z/VM: Systems Management Application

Programming, SC24-6234v z/VM: TCP/IP Programmer's Reference, SC24-6239v Common Programming Interface Communications

Reference, SC26-4399v Common Programming Interface Resource Recovery

Reference, SC31-6821v z/OS: IBM Tivoli Directory Server Plug-in

Reference for z/OS, SA76-0169v z/OS: Language Environment Concepts Guide,

SA38-0687v z/OS: Language Environment Debugging Guide,

GA32-0908v z/OS: Language Environment Programming Guide,

SA38-0682v z/OS: Language Environment Programming

Reference, SA38-0683v z/OS: Language Environment Run-Time Messages,

SA38-0686v z/OS: Language Environment Writing

Interlanguage Communication Applications,SA38-0684

v z/OS MVS Program Management: AdvancedFacilities, SA23-1392

v z/OS MVS Program Management: User's Guideand Reference, SA23-1393

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

GC24-6161v z/VM: CP Messages and Codes, GC24-6177v z/VM: Diagnosis Guide, GC24-6187

v z/VM: Dump Viewing Facility, GC24-6191v z/VM: Other Components Messages and Codes,

GC24-6207v z/VM: TCP/IP Diagnosis Guide, GC24-6235v z/VM: TCP/IP Messages and Codes, GC24-6237v z/VM: VM Dump Tool, GC24-6242v z/OS and z/VM: Hardware Configuration

Definition Messages, SC34-2668

z/VM Facilities and FeaturesData Facility Storage ManagementSubsystem for VMv z/VM: DFSMS/VM Customization, SC24-6181v z/VM: DFSMS/VM Diagnosis Guide, GC24-6182v z/VM: DFSMS/VM Messages and Codes,

GC24-6183v z/VM: DFSMS/VM Planning Guide, SC24-6184v z/VM: DFSMS/VM Removable Media Services,

SC24-6185v z/VM: DFSMS/VM Storage Administration,

SC24-6186

Directory Maintenance Facility for z/VMv z/VM: Directory Maintenance Facility Commands

Reference, SC24-6188v z/VM: Directory Maintenance Facility Messages,

GC24-6189v z/VM: Directory Maintenance Facility Tailoring

and Administration Guide, SC24-6190

Open Systems Adapterv Open Systems Adapter-Express Customer's Guide

and Reference, SA22-7935v Open Systems Adapter-Express Integrated Console

Controller User's Guide, SC27-9003v Open Systems Adapter-Express Integrated Console

Controller 3215 Support, SA23-2247v Open Systems Adapter/Support Facility on the

Hardware Management Console, SC14-7580

Performance Toolkit for VMv z/VM: Performance Toolkit Guide, SC24-6209v z/VM: Performance Toolkit Reference, SC24-6210

RACF® Security Server for z/VMv z/VM: RACF Security Server Auditor's Guide,

SC24-6212v z/VM: RACF Security Server Command Language

Reference, SC24-6213


v z/VM: RACF Security Server Diagnosis Guide,GC24-6214

v z/VM: RACF Security Server General User'sGuide, SC24-6215

v z/VM: RACF Security Server Macros andInterfaces, SC24-6216

v z/VM: RACF Security Server Messages and Codes,GC24-6217

v z/VM: RACF Security Server SecurityAdministrator's Guide, SC24-6218

v z/VM: RACF Security Server System Programmer'sGuide, SC24-6219

v z/VM: Security Server RACROUTE MacroReference, SC24-6231

Remote Spooling CommunicationsSubsystem Networking for z/VMv z/VM: RSCS Networking Diagnosis, GC24-6223v z/VM: RSCS Networking Exit Customization,

SC24-6224v z/VM: RSCS Networking Messages and Codes,

GC24-6225

v z/VM: RSCS Networking Operation and Use,SC24-6226

v z/VM: RSCS Networking Planning andConfiguration, SC24-6227

v z/OS: Network Job Entry (NJE) Formats andProtocols, SA32-0988

Prerequisite ProductsDevice Support Facilitiesv Device Support Facilities: User's Guide and

Reference, GC35-0033

Environmental Record Editing andPrinting Programv Environmental Record Editing and Printing

Program (EREP): Reference, GC35-0152v Environmental Record Editing and Printing

Program (EREP): User's Guide, GC35-0151

Bibliography 273


IBM®

Product Number: 5741-A07

Printed in USA

GC24-6207-05