Security zSecure Version 2.1 · using the IBM® Security zSecure™ 2.1.1 products. It provides explanations for these messages and errors. The information in this guide that applies

Security zSecureVersion 2.1.1

Messages Guide

SC27-6549-00

��

NoteBefore using this information and the product it supports, read the information in “Notices” on page 473.

March 2015

This edition applies to version 2, release 1, modification 1 of IBM Security zSecure products and version 1, release11, modification 2 of IBM Security zSecure Manager for RACF z/VM (product number 5655-T13), and to allsubsequent releases and modifications until otherwise indicated in new editions.

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

Contents

About this publication . . . . . . . . vIntended audience . . . . . . . . . . . . vWhat this publication contains . . . . . . . . vAccess to publications and terminology . . . . . vRelated documentation. . . . . . . . . . . ixAccessibility . . . . . . . . . . . . . . xTechnical training. . . . . . . . . . . . . xSupport information . . . . . . . . . . . . xStatement of Good Security Practices . . . . . . x

Chapter 1. Introduction . . . . . . . . 1Release information . . . . . . . . . . . . 1Overview of the zSecure products . . . . . . . 1zSecure message types . . . . . . . . . . . 2

Chapter 2. CKF Messages . . . . . . . 5Messages from 0 to 99 . . . . . . . . . . . 5Messages from 100 to 199. . . . . . . . . . 16Messages from 200 to 299. . . . . . . . . . 26Messages from 300 to 399. . . . . . . . . . 34Messages from 400 to 599. . . . . . . . . . 42Messages from 700 to 799. . . . . . . . . . 49Messages from 800 to 899. . . . . . . . . . 51Messages from 900 to 999. . . . . . . . . . 51

Chapter 3. CKG messages . . . . . . 59Messages from 100 to 199. . . . . . . . . . 59Messages from 400 to 499. . . . . . . . . . 62Messages from 500 to 599. . . . . . . . . . 64Messages from 600 to 699. . . . . . . . . . 68Messages from 700 to 799. . . . . . . . . . 76Messages from 800 to 899. . . . . . . . . . 81Messages from 900 to 999. . . . . . . . . . 81

Chapter 4. CKN messages . . . . . . 89Messages from 0 to 99 . . . . . . . . . . . 89Messages from 100 to 199. . . . . . . . . . 99Messages from 200 to 299 . . . . . . . . . 109Messages from 600 to 899 . . . . . . . . . 111Messages from 900 to 999 . . . . . . . . . 112

Chapter 5. CKR messages . . . . . . 115Messages from 0 to 99 . . . . . . . . . . 115Messages from 100 to 199 . . . . . . . . . 127Messages from 200 to 299 . . . . . . . . . 138Messages from 300 to 399 . . . . . . . . . 148Messages from 400 to 499 . . . . . . . . . 159Messages from 500 to 599 . . . . . . . . . 169Messages from 600 to 699 . . . . . . . . . 180Messages from 700 to 799 . . . . . . . . . 190Messages from 800 to 899 . . . . . . . . . 196Messages from 900 to 999 . . . . . . . . . 198Messages from 1000 to 1099 . . . . . . . . 209Messages from 1100 to 1199 . . . . . . . . 218

Messages from 1200 to 1299 . . . . . . . . 227Messages from 1300 to 1399 . . . . . . . . 239Messages from 1400 to 1499 . . . . . . . . 249Messages from 1500 to 1599 . . . . . . . . 259Messages from 1600 to 1699 . . . . . . . . 263Messages from 1700 to 1799 . . . . . . . . 263Messages from 1800 to 1899 . . . . . . . . 272Messages from 1900 to 1999 . . . . . . . . 272Messages from 2200 to 2299 . . . . . . . . 280Messages from 2300 to 2399 . . . . . . . . 283Messages from 2400 to 2499 . . . . . . . . 295Messages from 2500 to 2599 . . . . . . . . 305Messages from 2600 to 2699 . . . . . . . . 309Messages from 2700 to 2799 . . . . . . . . 312Messages from 2800 to 2899 . . . . . . . . 312

Chapter 6. CKV messages . . . . . . 315Messages from 0 to 99 . . . . . . . . . . 315Messages from100 to 199 . . . . . . . . . 318Messages from 200 to 299 . . . . . . . . . 320Messages from 300 to 399 . . . . . . . . . 320Messages from 400 to 499 . . . . . . . . . 322Messages from 700 to 799 . . . . . . . . . 322Messages from 800 to 899 . . . . . . . . . 323

Chapter 7. CKX messages . . . . . . 325Messages from 0 to 99 . . . . . . . . . . 325Messages from 800 to 899 . . . . . . . . . 327Messages from 900 to 999 . . . . . . . . . 327

Chapter 8. CQT messages . . . . . . 331Messages from 0 to 99 . . . . . . . . . . 331Messages from 100 to 199 . . . . . . . . . 338Messages from 900 to 999 . . . . . . . . . 344

Chapter 9. C2P messages . . . . . . 347Messages from 0 to 999 (zSecure started task) . . 347Messages from 1000 to 1999 (Predefined RACFalerts) . . . . . . . . . . . . . . . . 381Messages from 2000 to 2999 (Predefined ACF2alerts) . . . . . . . . . . . . . . . . 389Messages from 4000 to 6999 (Installation definedalerts) . . . . . . . . . . . . . . . . 394

© Copyright IBM Corp. 1998, 2015 iii

Chapter 10. C2R messages . . . . . 395

Chapter 11. C2RU messages . . . . . 405

Chapter 12. C2RW messages. . . . . 411

Chapter 13. C2X messages . . . . . 413

Chapter 14. C4R messages . . . . . 425Messages from 0 to 399 . . . . . . . . . . 425Messages from 400 to 499 . . . . . . . . . 425Messages from 500 to 599 . . . . . . . . . 429Messages from 600 to 699 . . . . . . . . . 436Messages from 700 to 799 . . . . . . . . . 442Messages from 800 to 899 . . . . . . . . . 446Messages from 900 to 999 . . . . . . . . . 446

Chapter 15. BB messages . . . . . . 449

Chapter 16. B8R messages . . . . . 451

Chapter 17. ICH and IRR messages 463

Chapter 18. Other error messages . . 465C errors . . . . . . . . . . . . . . . 465

LC errors . . . . . . . . . . . . . . . 465EPR errors . . . . . . . . . . . . . . 465

Appendix. Support for problemsolving . . . . . . . . . . . . . . 467Searching knowledge bases . . . . . . . . . 467

Available technical resources . . . . . . . 467Searching with support tools . . . . . . . 467Searching tips . . . . . . . . . . . . 467

Obtaining fixes . . . . . . . . . . . . . 467Registering with IBM Software Support . . . . 468Receiving weekly support updates . . . . . . 468Contacting IBM Software Support . . . . . . 469

Determining the business impact . . . . . . 470Describing problems and gathering information 470Submitting problems . . . . . . . . . . 470

Notices . . . . . . . . . . . . . . 473Trademarks . . . . . . . . . . . . . . 475

Index . . . . . . . . . . . . . . . 477

iv Messages Guide

About this publication

This guide contains the messages and return codes that you might receive whenusing the IBM® Security zSecure™ 2.1.1 products. It provides explanations for thesemessages and errors. The information in this guide that applies to zSecureManager for RACF® z/VM® applies to version 1.11.2 of that product.

Intended audienceThis guide is intended for the system administrators responsible for managing andtroubleshooting the zSecure products. Readers must be familiar with the zSecureproduct concepts and commands.

What this publication containsThis guide includes the following information:v An introduction to the zSecure products and a description of what each product

doesv Lists of the messages and errors and their severity levelsv An explanation for each individual messagev Support information

Access to publications and terminologyThis section provides:v A list of publications in the “IBM Security zSecure Manager for RACF z/VM

library” and the “IBM Security zSecure library” on page vi.v Links to “Online publications” on page ix.v A link to the “IBM Terminology website” on page ix.

IBM Security zSecure Manager for RACF z/VM library

The following documents are available in the IBM Security zSecure Manager forRACF z/VM library:v IBM Security zSecure Manager for RACF z/VM Release Information

For each product release, the Release Information topics provide informationabout new features and enhancements, incompatibility warnings, anddocumentation update information. You can obtain the most current version ofthe Release Information at http://www.ibm.com/support/knowledgecenter/SSQQGJ_1.11.2/com.ibm.zsecurevm.doc_1.11.2/welcome.html.

v IBM Security zSecure Manager for RACF z/VM: Installation and Deployment Guide,SC27-4363

Provides information about installing, configuring, and deploying the product.v IBM Security zSecure Manager for RACF z/VM User Reference Manual, LC27-4364

Describes how to use the product interface and the RACF administration andaudit functions. The manual provides reference information for the CARLacommand language and the SELECT/LIST fields. It also providestroubleshooting resources and instructions for using the zSecure Collectcomponent. This publication is available only to licensed users.

© Copyright IBM Corp. 1998, 2015 v

v IBM Security zSecure CARLa Command Reference, LC27-6548Provides both general and advanced user reference information about theCARLa Auditing and Reporting Language (CARLa). CARLa is a programminglanguage that is used to create security administrative and audit reports withzSecure. The CARLa Command Reference also provides detailed information aboutthe NEWLIST fields for selecting data and creating zSecure reports. Thispublication is available only to licensed users.

v IBM Security zSecure Messages Guide, SC27-6549Provides a message reference for all IBM Security zSecure components. Thisguide describes the message types associated with each product or feature, andlists all IBM Security zSecure product messages and errors along with theirseverity levels sorted by message type. This guide also provides an explanationand any additional support information for each message.

v IBM Security zSecure Manager for RACF z/VM Documentation CD, LCD8-2726Supplies the IBM Security zSecure documentation, which contains the licensedand unlicensed product documentation. The IBM Security zSecure: DocumentationCD is available only to licensed users.

v Program Directory for IBM Security zSecure Manager for RACF z/VM, GI11-7865The Program Directory for IBM Security zSecure Manager for RACF z/VM isintended for the systems programmer responsible for installing, configuring, anddeploying the product. It contains information about the materials andprocedures associated with installing the software. The Program Directory isprovided with the product tape. You can also download the latest copy from theIBM Knowledge Center available at http://www.ibm.com/support/knowledgecenter/SSQQGJ_1.11.2/com.ibm.zsecurevm.doc_1.11.2/welcome.html.

IBM Security zSecure library

The following documents are available online in the IBM Security zSecure library:v IBM Security zSecure Release information

For each product release, the release information topics provide informationabout new features and enhancements, incompatibility warnings, anddocumentation update information for the IBM Security zSecure products. Youcan obtain the most current version of the release information athttp://www.ibm.com/support/knowledgecenter/SS2RWS_2.1.1/com.ibm.zsecure.doc_2.1.1/welcome.html.

v IBM Security zSecure CARLa-Driven Components Installation and Deployment Guide,SC27-5638Provides information about installing and configuring the following IBMSecurity zSecure components:– IBM Security zSecure Admin– IBM Security zSecure Audit for RACF, CA-ACF2, and CA-Top Secret– IBM Security zSecure Alert for RACF and ACF2– IBM Security zSecure Visual for RACF– IBM Security zSecure Adapters for QRadar SIEM for RACF, CA-ACF2, and

CA-Top Secretv IBM Security zSecure Admin and Audit for RACF Getting Started, GI13-2324

Provides a hands-on guide introducing IBM Security zSecure Admin and IBMSecurity zSecure Audit product features and user instructions for performingstandard tasks and procedures. This manual is intended to help new users

vi Messages Guide

http://www.ibm.com/support/knowledgecenter/SS2RWS_2.1.1/com.ibm.zsecure.doc_2.1.1/welcome.htmlhttp://www.ibm.com/support/knowledgecenter/SS2RWS_2.1.1/com.ibm.zsecure.doc_2.1.1/welcome.html

develop both a working knowledge of the basic IBM Security zSecure Adminand Audit for RACF system functionality and the ability to explore the otherproduct features that are available.

v IBM Security zSecure Admin and Audit for RACF User Reference Manual, LC27-5639Describes the product features for IBM Security zSecure Admin and IBMSecurity zSecure Audit. Includes user instructions to run the features from ISPFpanels, RACF administration and audit user documentation with both generaland advanced user reference material for the CARLa command language andthe SELECT/LIST fields. This manual also provides troubleshooting resourcesand instructions for installing the zSecure Collect for z/OS component. Thispublication is only available to licensed users.

v IBM Security zSecure Audit for ACF2 Getting Started, GI13-2325Describes the IBM Security zSecure Audit for ACF2 product features andprovides user instructions for performing standard tasks and procedures such asanalyzing Logon IDs, Rules, and Global System Options, and running reports.The manual also includes a list of common terms for those not familiar withACF2 terminology.

v IBM Security zSecure Audit for ACF2 User Reference Manual, LC27-5640Explains how to use IBM Security zSecure Audit for ACF2 for mainframesecurity and monitoring. For new users, the guide provides an overview andconceptual information about using ACF2 and accessing functionality from theISPF panels. For advanced users, the manual provides detailed referenceinformation including message and return code lists, troubleshooting tips,information about using zSecure Collect for z/OS, and details about userinterface setup. This publication is only available to licensed users.

v IBM Security zSecure Audit for Top Secret User Reference Manual, LC27-5641Describes the IBM Security zSecure Audit for Top Secret product features andprovides user instructions for performing standard tasks and procedures.

v IBM Security zSecure CARLa Command Reference, LC27-6533Provides both general and advanced user reference information about theCARLa Auditing and Reporting Language (CARLa). CARLa is a programminglanguage that is used to create security administrative and audit reports withzSecure. The CARLa Command Reference also provides detailed information aboutthe NEWLIST fields for selecting data and creating zSecure reports. Thispublication is available only to licensed users.

v IBM Security zSecure Alert User Reference Manual, SC27-5642Explains how to configure, use, and troubleshoot IBM Security zSecure Alert, areal-time monitor for z/OS® systems protected with the Security Server (RACF)or CA-ACF2.

v IBM Security zSecure Command Verifier User Guide, SC27-5648Explains how to install and use IBM Security zSecure Command Verifier toprotect RACF mainframe security by enforcing RACF policies as RACFcommands are entered.

v IBM Security zSecure CICS Toolkit User Guide, SC27-5649Explains how to install and use IBM Security zSecure CICS Toolkit to provideRACF administration capabilities from the CICS® environment.

v IBM Security zSecure Messages Guide, SC27-5643Provides a message reference for all IBM Security zSecure components. Thisguide describes the message types associated with each product or feature, andlists all IBM Security zSecure product messages and errors along with their

About this publication vii

severity levels sorted by message type. This guide also provides an explanationand any additional support information for each message.

v IBM Security zSecure Quick Reference, SC27-5646This booklet summarizes the commands and parameters for the following IBMSecurity zSecure Suite components: Admin, Audit, Alert, Collect, and CommandVerifier. Obsolete commands are omitted.

v IBM Security zSecure Visual Client Manual, SC27-5647Explains how to set up and use the IBM Security zSecure Visual Client toperform RACF administrative tasks from the Windows-based GUI.

v IBM Security zSecure Documentation CD, LCD8-2726Supplies the IBM Security zSecure documentation, which contains the licensedand unlicensed product documentation. The IBM Security zSecure: DocumentationCD is available only to licensed users.

v Program Directory for IBM Security zSecure Suite: CARLa-driven components,GI13-2277This program directory is intended for the system programmer responsible forprogram installation and maintenance. It contains information concerning thematerial and procedures associated with the installation of IBM Security zSecureCARLa-Driven Components: Admin, Audit, Visual, Alert, and the IBM SecurityzSecure Adapters for QRadar SIEM. Program directories are provided with theproduct tapes. You can also download the latest copy from the IBM SecurityzSecure documentation website at http://www.ibm.com/support/knowledgecenter/SS2RWS_2.1.1/com.ibm.zsecure.doc_2.1.1/welcome.html.

v Program Directory for IBM Security zSecure CICS Toolkit, GI13-2282This program directory is intended for the system programmer responsible forprogram installation and maintenance. It contains information concerning thematerial and procedures associated with the installation of IBM Security zSecureCICS Toolkit. Program directories are provided with the product tapes. You canalso download the latest copy from the IBM Security zSecure documentationwebsite at http://www.ibm.com/support/knowledgecenter/SS2RWS_2.1.1/com.ibm.zsecure.doc_2.1.1/welcome.html.

v Program Directory for IBM Security zSecure Command Verifier, GI13-2284This program directory is intended for the system programmer responsible forprogram installation and maintenance. It contains information concerning thematerial and procedures associated with the installation of IBM Security zSecureCommand Verifier. Program directories are provided with the product tapes. Youcan also download the latest copy from the IBM Security zSecure documentationwebsite at http://www.ibm.com/support/knowledgecenter/SS2RWS_2.1.1/com.ibm.zsecure.doc_2.1.1/welcome.html.

v Program Directory for IBM Security zSecure Admin RACF-Offline, GI13-2278This program directory is intended for the system programmer responsible forprogram installation and maintenance. It contains information concerning thematerial and procedures associated with the installation of the IBM SecurityzSecure Admin RACF-Offline component of IBM Security zSecure Admin.Program directories are provided with the product tapes. You can also downloadthe latest copy from the IBM Security zSecure documentation website athttp://www.ibm.com/support/knowledgecenter/SS2RWS_2.1.1/com.ibm.zsecure.doc_2.1.1/welcome.html.

viii Messages Guide

http://www.ibm.com/support/knowledgecenter/SS2RWS_2.1.1/com.ibm.zsecure.doc_2.1.1/welcome.htmlhttp://www.ibm.com/support/knowledgecenter/SS2RWS_2.1.1/com.ibm.zsecure.doc_2.1.1/welcome.htmlhttp://www.ibm.com/support/knowledgecenter/SS2RWS_2.1.1/com.ibm.zsecure.doc_2.1.1/welcome.htmlhttp://www.ibm.com/support/knowledgecenter/SS2RWS_2.1.1/com.ibm.zsecure.doc_2.1.1/welcome.htmlhttp://www.ibm.com/support/knowledgecenter/SS2RWS_2.1.1/com.ibm.zsecure.doc_2.1.1/welcome.htmlhttp://www.ibm.com/support/knowledgecenter/SS2RWS_2.1.1/com.ibm.zsecure.doc_2.1.1/welcome.htmlhttp://www.ibm.com/support/knowledgecenter/SS2RWS_2.1.1/com.ibm.zsecure.doc_2.1.1/welcome.htmlhttp://www.ibm.com/support/knowledgecenter/SS2RWS_2.1.1/com.ibm.zsecure.doc_2.1.1/welcome.html

Online publications

IBM posts product publications when the product is released and when thepublications are updated at the following locations:

IBM Security zSecure Manager for RACF z/VM libraryThe product documentation site (http://www.ibm.com/support/knowledgecenter/SSQQGJ_1.11.2/com.ibm.zsecurevm.doc_1.11.2/welcome.html) displays the welcome page and navigation for the library.

IBM Security zSecure libraryThe product documentation site (http://www.ibm.com/support/knowledgecenter/SS2RWS_2.1.1/com.ibm.zsecure.doc_2.1.1/welcome.html)displays the welcome page and navigation for the library.

IBM Security Systems Documentation CentralIBM Security Systems Documentation Central provides an alphabetical listof all IBM Security Systems product libraries and links to the onlinedocumentation for specific versions of each product.

IBM Publications CenterThe IBM Publications Center site (http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss) offers customized search functionsto help you find all the IBM publications you need.

IBM Terminology website

The IBM Terminology website consolidates terminology for product libraries in onelocation. You can access the Terminology website at http://www.ibm.com/software/globalization/terminology.

Related documentationIf you are using IBM Security zSecure products in a RACF environment, you canfind more information about RACF and the types of events that can be reportedusing zSecure Admin and Audit in several IBM manuals. For information aboutthe RACF commands, and the implications of the various keywords, see the RACFCommand Language Reference and the RACF Security Administrator's Guide. You canfind information about the various types of events that are recorded by RACF inthe RACF Auditor's Guide. To access manuals in the z/OS online library, seehttp://www.ibm.com/systems/z/os/zos/bkserv/.

Table 1. z/OS manuals in z/OS online library

Manual Title Order Number

z/OS Security Server RACF Command Language Reference SA23-2292

z/OS Security Server RACF Security Administrator's Guide SA23-2289

z/OS Security Server RACF Auditor's Guide SA23-2290

z/OS Security Server RACF System Programmer's Guide SA23-2287

z/OS MVS System Commands SA23-2292

z/OS Communications Server IP Configuration Reference SC27-3651

z/Architecture® Principles of Operation SA22–7832

You can find more information about ACF2 and the types of events that can bereported using zSecure Audit for ACF2 in the CA-ACF2 documentation.

About this publication ix

http://www.ibm.com/support/knowledgecenter/SS2RWS_2.1.1/com.ibm.zsecure.doc_2.1.1/welcome.htmlhttp://www.ibm.com/support/knowledgecenter/SS2RWS_2.1.1/com.ibm.zsecure.doc_2.1.1/welcome.htmlhttps://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/IBM%20Security%20Systems%20Documentation%20Central/page/Welcomehttp://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wsshttp://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wsshttp://www.ibm.com/software/globalization/terminologyhttp://www.ibm.com/software/globalization/terminology

For information about Top Secret, see the CA-Top Secret for z/OS documentation.

For information about z/VM, see the IBM Knowledge Center athttp://www.ibm.com/support/knowledgecenter/SSB27U/welcome. Also seehttp://www.vm.ibm.com/library for more information about z/VM.

Table 2. Further information about RACF administration, auditing, programming, andcommands for z/VM

Manual Order Number

z/VM RACF Security Server Command Language Reference SC24-6213

z/VM RACF Security Server Security Administrator's Guide SC24-6218

z/VM RACF Security Server Auditor's Guide SC24-6212

z/VM RACF Security Server System Programmer's Guide SC24-6219

ISPF Quick Start Guide for VM V2R3 GI13-3554

For information about incompatibilities, see the Incompatibility section underRelease Information on the documentation website for your product at:v For z/OS: http://www.ibm.com/support/knowledgecenter/SS2RWS_2.1.1/

com.ibm.zsecure.doc_2.1.1/welcome.htmlv For z/VM: http://www.ibm.com/support/knowledgecenter/SSQQGJ_1.11.2/

com.ibm.zsecurevm.doc_1.11.2/welcome.html

AccessibilityAccessibility features help users with a physical disability, such as restrictedmobility or limited vision, to use software products successfully. With this product,you can use assistive technologies to hear and navigate the interface. You can alsouse the keyboard instead of the mouse to operate all features of the graphical userinterface.

Technical trainingFor technical training information, see the following IBM Education website athttp://www.ibm.com/software/tivoli/education.

Support informationIBM Support provides assistance with code-related problems and routine, shortduration installation or usage questions. You can directly access the IBM SoftwareSupport site at http://www.ibm.com/software/support/probsub.html.

Statement of Good Security PracticesIT system security involves protecting systems and information throughprevention, detection and response to improper access from within and outsideyour enterprise. Improper access can result in information being altered, destroyed,misappropriated or misused or can result in damage to or misuse of your systems,including for use in attacks on others. No IT system or product should beconsidered completely secure and no single product, service or security measurecan be completely effective in preventing improper use or access. IBM systems,products and services are designed to be part of a comprehensive securityapproach, which will necessarily involve additional operational procedures, andmay require other systems, products or services to be most effective. IBM DOES

x Messages Guide

http://www.ibm.com/support/knowledgecenter/SSB27U/welcomehttp://www.vm.ibm.com/libraryhttp://www.ibm.com/support/knowledgecenter/SS2RWS_2.1.1/com.ibm.zsecure.doc_2.1.1/welcome.htmlhttp://www.ibm.com/support/knowledgecenter/SS2RWS_2.1.1/com.ibm.zsecure.doc_2.1.1/welcome.htmlhttp://www.ibm.com/support/knowledgecenter/SSQQGJ_1.11.2/com.ibm.zsecure.doc_1.11.2/welcome.htmlhttp://www.ibm.com/support/knowledgecenter/SSQQGJ_1.11.2/com.ibm.zsecure.doc_1.11.2/welcome.htmlhttp://www.ibm.com/software/tivoli/educationhttp://www.ibm.com/software/support/probsub.html

NOT WARRANT THAT ANY SYSTEMS, PRODUCTS OR SERVICES AREIMMUNE FROM, OR WILL MAKE YOUR ENTERPRISE IMMUNE FROM, THEMALICIOUS OR ILLEGAL CONDUCT OF ANY PARTY.

About this publication xi

xii Messages Guide

Chapter 1. Introduction

The IBM Security zSecure suite is a collection of products that improve theefficiency and maintainability of the mainframe security environment. Theseproducts can be used alone or in conjunction with the other zSecure products. Themain products are zSecure Admin and zSecure Audit. The IBM Security zSecureproducts provide security, monitoring, auditing and alerting functionality on boththe z/OS and z/VM platforms.

zSecure messages are usually categorized by a three-character prefix to identify theassociated programs or components. For example, the CKF prefix identifiesmessages issued by the zSecure Collect for z/OS component, and CKG messagesare issued by the CKGRACF program. This guide is organized by message prefixesthat are associated with their programs or components.

The following sections provide release information for zSecure 2.1.1 and zSecureManager for RACF z/VM1.11.2, an overview of the zSecure products, and thetypes of messages that can be generated.

Release informationThe zSecure Release information topics include details on new features andenhancements, incompatibility warnings, and documentation update information.

You can download the latest version of the release information for IBM SecurityzSecure 2.1.1 at: http://www.ibm.com/support/knowledgecenter/SS2RWS_2.1.1/com.ibm.zsecure.doc_2.1.1/welcome.html.

You can download the latest version of the release information for zSecureManager for RACF z/VM 1.11.2 at: http://www.ibm.com/support/knowledgecenter/SSQQGJ_1.11.2/com.ibm.zsecurevm.doc_1.11.2/welcome.html.

Overview of the zSecure productsThe IBM Security zSecure suite includes the following products.

zSecure AdminProvides a user-friendly layer in the form of an ISPF interface on top ofRACF which enables security administration, user management andcompliance management on the mainframe. It allows you to enter andprocess administrative commands more quickly, generate custom reports,and thoroughly clean up databases. Additionally, zSecure Admin providesadministration authority in a more granular fashion so that users are onlygranted the specific amount of administration authority required for theirjob.

zSecure AuditCompliance and audit solution that enables you to automatically analyzeand report on security events and detect security exposures. It providesstandard and customized reports that warn of policy exceptions orviolations. This component is available for RACF, ACF2, and Top Secret.

zSecure AlertMainframe audit solution that enables you to detect and report security

© Copyright IBM Corp. 1998, 2015 1

common-zsecure_symbols.dita#common-zsecure_symbols/info_center_welcome_urlcommon-zsecure_symbols.dita#common-zsecure_symbols/info_center_welcome_urlcommon-zsecure_symbols.dita#common-zsecure_symbols/vm_info_center_welcome_urlcommon-zsecure_symbols.dita#common-zsecure_symbols/vm_info_center_welcome_url

events and exposures on z/OS, DB2®, UNIX, RACF, ACF2, and Top Secret.IBM Security zSecure Alert is a real-time monitor, issuing alerts forsecurity-related system events at the time they occur.

zSecure Command VerifierMainframe policy enforcement solution adds granular controls for RACF tohelp prevent errors and noncompliant commands. This product runs in thebackground to verify your RACF commands against company policies andprocedures. If the command does not comply with the policy, it is blockedor fixed. It can run independently from the other zSecure components.

zSecure VisualzSecure Visual client is a Windows-based graphical user interface for RACFadministration. Using the Visual Server product establishes a secureconnection directly with RACF to enable decentralized administration froma Windows environment.

zSecure CICS ToolkitThis component enables you to do most RACF administration from a CICSenvironment instead of TSO.

zSecure Adapters for QRadar SIEMThis component enables you to collect mainframe security data and send itto the IBM Security QRadar® SIEM product to get an enterprise-wide view.

zSecure Manager for RACF z/VMThis product simplifies the process of managing mainframe security andenables you to quickly identify and fix problems in RACF on z/VM. Itautomates recurring and time-consuming security tasks.

zSecure message typeszSecure messages are categorized by an alphanumeric prefix. Each prefix refers tothe zSecure product function which the messages in that category are associatedwith. The following table lists the available zSecure message prefixes, their relatedfunctions, and the products that can display these messages:

Table 3. zSecure product messages

MessagePrefix Function Product Reference

CKF zSecure Collect for z/OS(CKFCOLL)

IBM Security zSecure Admin,IBM Security zSecure Audit,IBM Security zSecure Alert,IBM Security zSecure Adaptersfor QRadar SIEM

Chapter 2, “CKFMessages,” on page 5

CKG CKGRACF program IBM Security zSecure Admin,IBM Security zSecure Visual

Chapter 3, “CKGmessages,” on page59,

CKN zSecure Server (networknode)

IBM Security zSecure Admin,IBM Security zSecure Audit,IBM Security zSecure Visual

Chapter 4, “CKNmessages,” on page89

2 Messages Guide

Table 3. zSecure product messages (continued)


CKR CKRCARLA program IBM Security zSecure Admin,IBM Security zSecure Audit,IBM Security zSecure Visual,IBM Security zSecure Alert,IBM Security zSecure Managerfor RACF z/VM, IBM SecurityzSecure Adapters for QRadarSIEM

Chapter 5, “CKRmessages,” on page115

CKV zSecure Collect forz/VM (CKVCOLL)

IBM Security zSecure Managerfor RACF z/VM

Chapter 6, “CKVmessages,” on page315

CKX TSO execution utilityprogram CKX orzSecure CommandExecution Utility

IBM Security zSecure Admin,IBM Security zSecure Managerfor RACF z/VM

Chapter 7, “CKXmessages,” on page325

CQT Module CQTPMSGE IBM Security zSecure CICSToolkit

Chapter 8, “CQTmessages,” on page331

C2P zSecure Alert addressspace, Predefined RACFalert, Predefined ACF2alert, Installation definedalert, or zSecure RACFAccess Monitor

IBM Security zSecure Alert orIBM Security zSecure Admin

Chapter 9, “C2Pmessages,” on page347

C2R NLS table processorC2RIMENU, XSLTstylesheet, or theinstallationcustomization REXXexec C2REUPDR

IBM Security zSecure Chapter 10, “C2Rmessages,” on page395

C2RU User interface IBM Security zSecure VisualClient

Chapter 11, “C2RUmessages,” on page405

C2RW IBM Security zSecure VisualServer

Chapter 12, “C2RWmessages,” on page411

C2X zSecure RACF ExitActivator componentC2XACTV

IBM Security zSecure Admin,IBM Security zSecure Audit,IBM Security zSecure Alert

Chapter 13, “C2Xmessages,” on page413

C4R IBM Security zSecureCommand Verifier

Chapter 14, “C4Rmessages,” on page425

BB BBRACF component IBM Security zSecure Visual Chapter 15, “BBmessages,” on page449

B8R Security zSecure AdminRACF-Offline functions

IBM Security zSecure Admin Chapter 16, “B8Rmessages,” on page451

ICH andIRR

RACF Chapter 17, “ICH andIRR messages,” onpage 463

Chapter 1. Introduction 3

Table 3. zSecure product messages (continued)


C IBM Security zSecure VisualClient

Chapter 18, “Othererror messages,” onpage 465

LC Communication layerbetween the client userinterface and thec2ragent component

IBM Security zSecure VisualClient


EPR Communication layerbetween the c2ragentcomponent and theserver. Found also in thelog-files called cesys andceaud in the directory:ApplicationDirectory\Servers\ServerName.Files cesys0..cesys9 andceaud..ceaud9 areprevious log-files.

IBM Security zSecure VisualClient


The following chapters of this guide provide a listing of each message prefix alongwith a detailed explanation and possible solutions.

4 Messages Guide

Chapter 2. CKF Messages

zSecure Collect is a component of these products:v zSecure Adminv zSecure Auditv zSecure Alertv zSecure Adapters for QRadar SIEMv zSecure Manager for RACF z/VMzSecure Collect gathers system data and stores that data in CKFREEZE data sets. Itissues messages with the CKF prefix for the z/OS products and the CKV prefix forthe z/VM product. For example, if you are using zSecure Admin and Audit youmight see message number of CKF970I. The same message issued by zSecureManager for RACF z/VM has the number CKV970I. zSecure Collect messages forall products are documented. zSecure Collect messages shared between the z/OSand z/VM platforms are documented in this section. zSecure Collect messagesspecific to the z/VM product are documented in Chapter 6, “CKV messages,” onpage 315.

Each message number has the form CKFnnnI or CKVnnnI where nnn is themessage number. In addition to the message identifier, the program also issues aseverity code. This code is derived from the program completion code thatindicates the highest severity code encountered.

Note: The return code from the program is normally set to the maximum value ofthe return codes from any messages. If NOWARNINGRC is coded, the 04 returncode from the program is reset to 00.

The severity code can contain any of the following values:

00 Normal message, giving status or summary information.

04 Unusual condition found that may or may not result in missinginformation.

08 Unusual condition found that causes information that was requested to bemissing. Subsequent processing may be impacted.

12 Unexpected condition during zSecure Collect processing.

16 Syntax error in command input or entitlement problem.

24 Internal error or other unexpected and unsupported condition in zSecureCollect detected.

28 Internal error or other unexpected and unsupported condition in zSecureCollect detected. A user abend will be issued to protect your system andforce a dump.

In the rest of this section, all error messages are listed with an explanation andpossible actions to take. Messages are included in subsections, grouped by thehundred message-numbers. To locate documentation for a specific message, searchthis documentation for the message number, CKF970I or CKV970I, for example.

Messages from 0 to 99

© Copyright IBM Corp. 1998, 2015 5

CKF000I Control block name omitted, because ofreason

Explanation: This message is issued if the programfails to find an OS control block. This is not necessarilya problem, rather it notes the absence of someinformation which might have been useful, but whichmay not be available in your OS version at all. Thename of the control block is given by name, the controlblock ID. The exact nature of the failure is given byreason, which may be:

invalid block IDThe control block ID is not found in its properplace.

protection exceptionA protection exception occurred during thewalk through the pointer chain leading to thecontrol block.

invalid lengthA protection exception occurred during accessto the last-to-be-used byte of the control block.

nil pointerThe pointer to the control block was found tocontain binary zeros.

This message may very well occur after conversion to anew release of the OS. The resulting CKFREEZE filemay still be usable for your purposes.

Problems indicated with missing control block namesinclude the following:

STGS RMF™ is not active

EDT device type information not retrieved

IODN LCU and device number table missing (alsoRMF)

IOCH Channel information missing (also RMF)

LPBT Logical Path Block Table missing (SRM SP4)

RCVT No RACF in system

SSVT This may be seen if RMM is not active

Severity: 04

CKF001I No generic unit name for devclass unitdev devtype devtype

Explanation: This message indicates that your OScould not give a generic unit name for the device onaddress dev, and the device type (given as 8 hex digits)is also not available in the hardcoded device table inzSecure Collect. The device class is devclass. This is nota problem; it just warns you to expect question marksin the unit name fields.

Severity: 04

CKF002I LOCATE return code rc on type data setdatasetname

Explanation: This message indicates that the data setdatasetname (which is supposed to be a type data set)could not be found by the LOCATE service of MVS™.The return code returned by the service is rc. Thevolume will be left blank or zero in the CKFREEZE file.

Severity: 04

CKF003I DEVTYPE RC nonzero for unit dev

Explanation: The DEVTYPE SVC used to collectinformation on unit dev returned a nonzero return code.This may cause the device type record in theCKFREEZE file to be unusable.

Severity: 04

CKF004I Closed PDSE dev volume dsname readdecnum bytes in decnum members

Explanation: This informational message indicates theamount of data read from the indicated PDSE. It isissued only if the INFO option was selected.

Severity: 00

CKF005I Please ignore CMD rejects

Explanation: This message is displayed on theoperator console to warn the operator that no actionshould be taken on the burst of IOS000I or IEA000Imessages specifying a CMD reject on 3350 DASDdevices. It is removed immediately after the programhas finished processing the 3350 range of devices. It isdisplayed during authorized operation only.

CKF006I CVAFDIR type error, R15=rc,CVSTAT=code on device dev volumevolume

Explanation: During access to the VTOC index, theCVAFDIR type (READ or RLSE) service returned anonzero return code rc accompanied by CVAF returncode code. See the appropriate IBM manual for themeaning of these codes. If the type of access wasREAD, the VTOC was read completely without takinginto account the used DSCB map in the VTOC index.

Severity: 12

CKF007I Task is not APF authorized - onlynon-protected information can becollected

Explanation: This message alerts you to the fact thatthe program could not obtain authorization. Foradditional information, see the section Authorized orunauthorized? in the zSecure Collect documentation

CKF000I • CKF007I

6 Messages Guide

available in the user reference manual for your zSecureproduct.

Severity: 00

CKF008I Number of DASD devices interrogated:nn

Explanation: This message gives the number ofdevices that have been allocated and interrogated.

Severity: 00

CKF009I Number of DSCB entries copied: nn

Explanation: This message gives the number of DataSet Control Blocks copied from VTOCs to theCKFREEZE file. It is somewhat larger than the numberof data sets on the interrogated devices, because someextents are described in separate DSCBs for the samedata set. Note that only used DSCBs are copied.

Severity: 00

CKF010I Number of VVDS datasets processed: nn

Explanation: This message gives the number of VVDSdata sets for which an OPEN was attempted. Generally,this number is smaller than the number of DASDdevices interrogated, because not every volume needsto have a VVDS.

Severity: 00

CKF011I Number of NVR/VVR entries copied: nn

Explanation: This messages gives the number of VVRs(VSAM volume records) and NVRs (non-VSAM volumerecords) copied to the CKFREEZE file. The number ofVVRs is roughly two times the number of VSAM datasets on the processed volumes. NVRs are associatedwith SMS managed non-VSAM data sets.

Severity: 00

CKF012I Non-4K block size for VVDS notsupported - volume volume

Explanation: This message indicates a VVDS wasencountered on volume volume with a block size otherthan 4KB. This is not supported by this release ofzSecure Collect. The VVDS has a 4KB block size if ithas been made automatically on 3330/3350/3380/3390DASD with at least DFP 1.0 through DFP 3.3. If youencounter this message, then the VVDS information forthe specified volume will not be read, and you willonly see component names mentioned in the VTOC,not the cluster names.

Severity: 12

CKF014I DASD Device dev online but not ready

Explanation: This message indicates the devicenumber dev was included in the configuration becauseit was online, but could not be interrogated because itwas not ready. Instead of scheduling an I/O request,zSecure Collect has skipped the device. This may resultin incomplete information for your purpose.

Severity: 04

CKF015I SYSEVENT DONTSWAP failed, returncode hex rc

Explanation: This message indicates that zSecureCollect failed to make itself nonswappable. As a result,no authorized I/Os can be scheduled and no cache sizeinformation and device level cache disablementinformation will be collected for 3880 devices. Neitherwill guaranteed device path I/O be used to eliminateWAITs.

Severity: 08

CKF016I Unsupported control block level hexnumfor volume dsname

Explanation: This message indicates that a controlblock of an unsupported layout was returned byDirectory Entry Services for the indicated PDSE. Ifcontrol block is "DESB", checksum and IDR processingare skipped for the remainder of the PDSE; if it is"SMDE", processing is skipped for a single memberonly.

Severity: 08

CKF017I Path ch to type device dev volume notoperational

Explanation: This message indicates that the installedphysical channel (pre-XA) or channel path (XA) ch tothe selected online and ready device number dev withvolume serial volume was not operational. If this is notyour normal working configuration, then you aremeasuring a reduced configuration with a highercontention than normal. Alternatively this may point atrunning MVS/370 under VM.

Severity: 04

CKF018I parameter Parameter invalid in non-XAsystem.

Explanation: The parameter specified is not applicableto pre-XA systems.

Severity: 12

CKF008I • CKF018I

Chapter 2. CKF Messages 7

CKF019I BFLHFCHN invalid for type device devvolser; VTOC processing skipped

Explanation: The forward chain pointer of next bufferlist (BFLHFCHN) is not valid; i.e. no (more) VTOCinformation could be obtained for device dev.

Severity: 12

CKF020I Path information not gotten forunsupported device type type, device devvolume

Explanation: This message indicates that yourequested configuration information for a device typetype, which is not currently supported by zSecureCollect. Requests for support for other DASD typesthan 3350, 3380, 3390, and compatibles should bedirected to IBM Software Support.

Severity: 08

CKF021I Storage director IDs unavailable for typedevice dev volume because unauthorized

Explanation: This message indicates that physicalstorage director IDs for device number dev with volumeserial volume can only be extracted by authorizedprograms because its device type is type. The result ismissing storage director information which mayprevent an automatic deduction of the configuration.

Severity: 08

CKF022I Storage director ID not returned by IOSfor path ch to type device dev volume

Explanation: This message indicates that the IOSversion you have fails to return the complete senseinformation needed to find the storage director ID. Thefailure occurred on path ch to device number dev withvolume serial volume. The device type is type. Thismessage is issued for only one path, because zSecureCollect assumes the same failure will occur on theother paths to the device, and does not attempt I/O onthese paths.

Severity: 08

CKF023I String controller ID not returned by IOSfor path ch to type device dev volume

Explanation: This message indicates that the controllerID was not found in its proper place. This message isnot issued if the storage director ID is also missing.Currently no software level is known which omits onlycontroller information. Because of redundancy ofinformation, you will probably not notice any effect onthe reports.

Severity: 08

CKF024I Path information still incomplete afterbs tries on type device dev volume:missing at least path ch

Explanation: This message indicates that after bs trieszSecure Collect still did not succeed in scheduling I/Oalong all paths to a device. This message only occurs ifyou specified or implied WAIT=NO and PATH=YES.The resulting CKFREEZE information will beincomplete.

Severity: 08

CKF025I Path information still incomplete afterbn bs-try bursts on type device devvolume: missing at least path ch

Explanation: This message indicates that after bnbursts of bs tries with a 0.5 second WAIT intervalbetween the bursts, zSecure Collect still did not succeedin scheduling I/O along all paths to a device. This mayhappen on very busy shared DASD systems and onvery empty pre-XA systems that do not have channelrotation. The number of bursts, burst size, andinter-burst wait time can be adjusted by the appropriateBURSTxxxx parameters.

Severity: 08

CKF026I Unexpected IOS return code rc hex,CSW status hhhh sense ssss on path ch tocccc/mm for type/mm device dev volume

Explanation: This message indicates an unexpectederror during EXCP processing. The IOS return codesare documented in the IBM debugging handbooks(IOB/IOSB) and in the appropriate DFP manuals. Thecccc/mm and type/mm are the control unit type / modeland unit type / model, respectively, as returned by theSenseId CCW. The resulting CKFREEZE file willprobably be incomplete.

Severity: 12

CKF026I Unexpected IOS return code rc hex,CSW status hhhh sense ssss on path ch to3350 device dev volume

Explanation: This message indicates an unexpectederror during EXCP processing. The IOS return codesare documented in the IBM debugging handbooks(IOB/IOSB) and in the appropriate DFP manuals. Theresulting CKFREEZE file will probably be incomplete.

Severity: 12

CKF027I Invalid DSCB FMTID=X'xx' on typedevice dev volser CCHHR=0000000000DSN=dsname

Explanation: The VTOC for the indicated volumecontained an invalid DSCB, with format X'xx'. The onlyvalid types are X'F0' .. X'F6'. The DSCB record is

CKF019I • CKF027I

8 Messages Guide

included in the CKFREEZE file, but will not used. Thedsname reported is the data set name field (key area) ofthe DSCB in error. This has no consequences for MVS ifthe DSCB is not in use according to the space map.

Severity: 04

CKF028I SVC 99 RC=n DAIRFAIL code xxxx xxxxon dev volser

Explanation: The device/volser may be absent. Thismessage will be followed by an IKJ-message on theproblem. The error occurred in dynamic allocation orunallocation of a VTOC or data set for device dev. Thismessage has continuation lines detailing the individualtext units contents after SVC 99 (DYNALLOC)completion.

Severity: 08

CKF029I DASD Device dev online, but notmounted

Explanation: Device dev was not mounted public,storage or private, zSecure Collect does not attempt toallocate the VTOC and VVDS data sets.

Severity: 04

CKF030I OPEN abend xxx-rc on device devvolume volser for dsname

Explanation: The data set named dsname could not beopened for input on device dev. The VTOC is indicatedwith ** VTOC volser **. If the error occurs for a VTOC,both the VTOC and the VVDS for the volume will bemissing. If the error occurs for a VVDS, the VTOCinformation has been read properly. For informationabout the common abend codes, see the zSecure Collectdocumentation in the user reference manual for yourzSecure product.

Severity: 08

CKF031I CKFCOLL runs on sid with osname oslevelDFSMS release JES2 release CPU modelmodel

CKF031I site-specific identification string running onwhere CPU-id CPUid

CKF031I Last record written: ID=hh, contents starthexstring

Explanation: zSecure Collect abended while runningon the indicated system (SMF id) and operating systemrelease levels, under the focus and Products ids shown,on the CPU indicated, after writing the indicated record(this line is omitted if no records had been written yet).

Severity: 00

CKF032I Number of record(s) truncated: nn

Explanation: This message indicates that records weretruncated on output. You might try increasing therecord length, if problems arise. However, for mostpurposes the information needed is located at thebeginning of the BCS records, and these truncatedrecords therefore do not usually present a problem.

Severity: 08

CKF033I Module IGG019X1 missing, noconfiguration info for 3350 devicespossible

Explanation: This message indicates that theappendage IGG019X1 could not be found.

Severity: 08

CKF034I [ Before MONITOR interval ] CKFCOLLused ss.t CPU seconds, ss elapsedseconds, and collected m.kkk MB (m.kkkMB/s)Written rectotal records to ddname volumedsnameRegion requested r,rrrKB, grantedg,ggg+g,gggKB max used in jobstepu,uuu+u,uuuuKB

Explanation: This message details the TCB time usedas well as the wall clock time. In addition, the amountof data collected (written to the CKFREEZE file) issummarized as well as the effective data rate. Theeffective data rate will be misleadingly low ifCHECK=Y was specified, since that is a data reductionfunction. If MONITOR has been requested, then thismessage is issued twice, once before the monitoringstarts, and once at the end of the program. Themessage at the end of the program also shows theregion requested, granted, and used, both below andabove the 16MB line.

Severity: 00

CKF035I Number of PDS directories processed:nn

Explanation: This messages gives the number of PDS(Partition Data Set) directories copied to the CKFREEZEfile.

Severity: 00

CKF036I Information omitted for devn volser, SAFREAD access required on FACILITYSTGADMIN.IFG.READVTOC.volser ifnon-APF

Explanation: This message indicates that an attempt toread the VTOC resulted in an system abend 300, reasoncode 6, which means that name hiding was active, andyou were not allowed to read the VTOC. In a RACF

CKF028I • CKF036I


system, name hiding is activated with the commandSETROPTS MLNAMES. If name hiding is active, a SAFresource check is done against the resource nameindicated.

Severity: 04

CKF037I Unexpected abend condition dev devnvolser during action

Explanation: This message indicates that an abendoccurred during EXCP for a channel programattempting to perform the action indicated. ContactIBM Software Support if this message occurs to see ifthis can be prevented.

Severity: 12

CKF038I Unexpected abend during allocate of dsn

Explanation: This message indicates a failure toallocate (and possibly perform an automatic recall of) aVSAM cluster. An abend was encountered. The clusterwill be skipped. If you think the program should havesucceeded, contact IBM Software Support.

Severity: 08

CKF039I Running OS version DFSMS version JESnversion VTAM version secp version RMFversion TSO version HSM version [ underVM/version release ]

Explanation: This message indicates release levels orstatus of the software that zSecure Collect extractsinformation from. Instead of a version number, thekeyword inactive, active, or unknown may be present toindicate respectively that the product is installed butnot active, active but release could not be obtained, orcontrol blocks present but of unsupported layout. secpis the detected security product, it can be RACF, ACF2,or TSS.

Severity: 00

CKF040I Unexpected abend during LISTCAT ofdsn

Explanation: This message indicates a failure to locatea VSAM cluster name in the catalog; an abend wasencountered. The cluster will be skipped. If you thinkthe program should have found it, contact IBMSoftware Support.

Severity: 08

CKF041I Number of catalogs processed: nn

Explanation: This message gives the number of ICFand HSM catalogs for which an OPEN was attempted.

Severity: 00

CKF042I Number of BCS records copied: nn

Explanation: This messages gives the number of BCS(Basic Catalog Structure) records copied to theCKFREEZE file.

Severity: 00

CKF043I VVDS information not collected,catalogs cannot be dumped fast

Explanation: This message is issued if the VVDS datasets could not be accessed, but catalog processing wasrequested. zSecure Collect requires VVDS access todump catalogs.

Severity: 00

CKF044I Name of master catalog not found inCAXWA. Abend 913-0C may result forunconnected catalogs

Explanation: This message indicates that the mastercatalog name or volume serial could not be determined.Consequently, it is impossible to determine whichcatalogs are connected. zSecure Collect will try to openall catalogs it encounters on the disks processed. Thiswill result in abend 913-0C for each unconnectedcatalog.

Severity: 12

CKF045I Master catalog volume volume notselected. Abend 913-0C may result forunconnected catalogs

Explanation: This message indicates that the mastercatalog was not found on any of the disk volumesprocessed. Hence no user catalog connector informationis accumulated by zSecure Collect. zSecure Collect willtry to open all catalogs it encounters on the disksprocessed. This will result in abend 913-0C for eachunconnected catalog.

Severity: 08

CKF046I Slowdown mode invoked becausenoimbed and multi-volume index fordsname

Explanation: This message indicates that normalVSAM processing was selected for this cluster becauseit has a multi-volume index component that is neededbecause of NOIMBED.

Severity: 00

CKF037I • CKF046I

10 Messages Guide

CKF047I Data collection started on date time fornode nodename sysname sysname sid smfidnetid netid on a manufacturer typemodelmodel [ MVSCP conguration id xx ] [logical partition LPARname ] [ virtualmachine userid ] [ at sysid ] [ sysplexname ]

Explanation: This message indicates the timestampmarking the start of data collection. It can be used tofind the proper zSecure Collect SYSPRINT output whenpresented with a specific CKFREEZE file. In addition,the various system identifiers are listed: the JES2 nodename, the GRS system name, the SMF id, the VTAM®

netid, and the processor type. The processorspecifications are those returned by the CSRSI service.On older machines where that service is not yetavailable the type is the internal hexadecimalrepresentation (devtype/model); for VM systems thereal model byte is displayed if running APF authorized,otherwise it is FF. On the second line, optionalconfiguration information may be present to indicatethe MVSCP configuration id, the Logical Partitionname, the VM virtual machine user ID, the VM systemID (as would be displayed in the lower right cornerunder CMS), and the SYSPLEX name.

Severity: 00

CKF048I ACB OPEN failed for type dev volsercomponentname rc=nn, code=nn clusterclustername

Explanation: This message indicates a failure to openthe VSAM data set indicated and gives the return codeand reason code. The type can be BCS for an ICFcatalog, MCD for HSM MCDS, BCD for HSM BCDS,and RMM for the DFSMS RMM control data set. ACBOPENs for ICF catalogs are attempted only if thecatalog has been defined with NOIMBED, if it hasmore than 16 extents on a pre-DFP V3 system, or if therun is unauthorized in a pre-DFP V3 system.

Severity: 08

CKF049I Internal error CKFCCHH RC=16

Explanation: Contact IBM Software Support.

Severity: 24

CKF050I TTT Conversion fails on reltrkDEBNMEXT=nnn on dev volser

Explanation: This message indicates a failure toconvert the indicated relative track number to anabsolute cylinder and head address. The requestedtrack will not be read. Generally this means that theinternal structure of a data set was not understoodproperly, for example, because of a new version of thesoftware maintaining that data set. Contact IBMSoftware Support.

Severity: 08

CKF051I EXCP failed on ddname, RC=hh,IOBSEEK=address device dev volser

Explanation: This message indicates an unexpectedI/O failure on the indicated device and address. Thereturn code is the EXCP return code in hex.

Severity: 12

CKF051I (ECKD) EXCP failed on ddname, AddressCKFB: address, rc nnx,CSW=hhhhhhhhhhhhhh, IOBSEEK=addressdevice dev volser

Explanation: This message indicates an unexpectedECKD™ I/O failure on the indicated device andaddress. The return code is the EXCP return code inhex.

Severity: 12

CKF051I Multiple track read EXCP failed onddname, Number of reads hhhh, AddressCKFB: address, rc nnx,CSW=hhhhhhhhhhhhhh, IOBSEEK=addressdevice dev volser

Explanation: This message indicates an unexpectedmultitrack read I/O failure on the indicated device andaddress. The return code is the EXCP return code inhex.

Severity: 12

CKF052I Slowdown mode invoked becausenoimbed and index on volume forcatname

Explanation: This message indicates that the requestedICF, HSM, or RMM catalog dump will be tried withVSAM, because the faster EXCP mode does not supportNOIMBED with the index on a different volume thanthe data component.

Severity: 00

CKF053I Slowdown mode invoked because notAPF-authorized, data set volume catname

Explanation: This message indicates that the requestedcatalog dump will be tried with VSAM, because thefaster EXCP mode requires APF authorization that isnot present. ALTER authority is required to read ICFcatalogs without APF authorization on DFP systemsbelow version 3. For DFP version 3 APF authorizationis required to read ICF catalogs anyway and messageCKF064I will be issued. READ authority is needed toread HSM catalogs.

Severity: 00

CKF047I • CKF053I


CKF054I Data set catname CA at rel track ttmissing nn CIs in sequence set record

Explanation: This message indicates that the numberof CIs described by the index sequence set record wasnot the number of CIs per CA. If the error message isreproducible, perform EXAMINE on the data set. If nostrange things are found, contact IBM SoftwareSupport.

Severity: 00

CKF055I ACB OPEN type abend xxx-nn(explanation) for dev volume componentnameof catalogname

Explanation: This message indicates an abend duringan attempt to open the ICF, RMM, or HSM catalogindicated.

Severity: 08

CKF056I Slowdown mode invoked because moreextents than EXCP supports (abend013-E4) for vol cluster

Explanation: The maximum number of extentssupported by an EXCP OPEN depends on the DFSMSrelease. This is reflected in the job log as an abend013-E4 (or in older releases, 213-20). The CKF030Imessage is suppressed in this case. The abend isintercepted, and slowdown mode is invoked for thisrelease.

Severity: 00

CKF057I type abend xxx-nn (explanation) on devvolser dsname

Explanation: A nonrecoverable abend occurredopening data set dsname for input on device dev. If theerror occurs for a VTOC, the VTOC and all data sets onthe volume will be missing. If the error occurs for aVVDS, the VTOC information has been read properly.For information on the common abend codes, see thezSecure Collect documentation in the user referencemanual for your zSecure product.

Severity: 08

CKF058I Unexpected physical record lengthdecnum in imbedded SSR with indexblksize decnum for catname

Explanation: This message indicates that a physicalrecord (i.e. block) was read from the imbedded indextrack with a block size different from the block sizeindicated in the information in the VVR. Results will beunpredictable.

Severity: 12

CKF059I NOIMBED not supported, data setcatname on volser skipped

Explanation: This message indicates that for somereason the index was not read successfully.Consequently, the NOIMBED data set cannot beprocessed.

Severity: 08

CKF060I VVDS space map extension at RBAhexnum ignored - expecting hexnum

Explanation: zSecure Collect expects the space mapchain to occur in order in the VVDS.

Severity: 12

CKF061I VVDS can only be accessed with APFauthorization

Explanation: In DFP V3 systems, APF authorization isrequired to read the VVDS.

Severity: 04

CKF062I Connected catalog catname not found onvolumes processed

Explanation: The master catalog processed contained aconnector entry for catalog catname. However, thecatalog was not found on the volumes processed.Catalog information may be incomplete.

Severity: 08

CKF063I Unexpected error: Master cat BCS notfound on mastercat volume. Abend913-0C may occur

Explanation: This message indicates that for somereason the master catalog was not found on the volumeit was supposed to reside on. Consequently, it cannotbe determined whether user catalogs are connected ornot. Abend 913-0C results from trying to open anunconnected catalog if bypass-password processing isnot being used.

Severity: 08

CKF064I Catalog cannot be dumped without APFauthorization - catname

Explanation: On a DFP version 3 or higher system,APF authorization is required to dump ICF catalogs.

Severity: 08

CKF054I • CKF064I

12 Messages Guide

CKF065I Slowdown mode invoked becauseprimary data VVR not obtained fordatacomponent

Explanation: To read VSAM data sets in EXCP mode,zSecure Collect needs the VSAM Volume Record (VVR)residing in the VVDS. This message is issued if theVVR of the data component was not encountered.

Severity: 00

CKF066I Slowdown mode invoked becausenoimbed and primary index VVR notobtained for datacomponent

Explanation: To read VSAM data sets with theNOIMBED attribute in EXCP mode, zSecure Collectneeds the VSAM Volume Record (VVR) of the indexresiding in the VVDS. This message is issued if theVVR of the index component was not encountered.

Severity: 00

CKF067I Data set datacomponent error at CI num inCA at rel trk nnn type key

Explanation: Where key is the current record key (adata set name), and type can be one of the followingerror types:

last segment missing - record skipped

For a spanned record, the last segment was not foundin the control area. The record will not be copied toCKFREEZE.

orphan inner segment skipped

A spanned record intermediate segment wasencountered, but the first segment for the record wasnot found in the control area. The segment will bediscarded.

updated during copy

A spanned record was encountered, but the segmentsdid not have the same update count. This can happenif the record was updated between read instructions tothe control area. The record may appear garbled in theCKFREEZE file.

orphan last segment skipped

The last segment of a spanned record was encountered,but the first segment for the record was not found inthe control area. The segment will be discarded.

Severity: 04

CKF068I Cat rlen=xxxx (RDF=xxxxxx) at CI offsetxxxx > used CI xxxxxx of CA at reltrknnnnn in datacomponent

Explanation: The record length field in a catalog

record (rlen) points beyond the end of the used bytes ina control interval.

Severity: 08

CKF069I Slowdown mode invoked formulti-volume cluster dsname

Explanation: This message indicates that normalVSAM processing was selected for this cluster becauseit has a multi-volume data component.

Severity: 00

CKF070I type abend xxx-nn (explanation) on devvolume dataset

Explanation: This message indicates a nonrecoverableabend occurred during OPEN of the indicated PDS(E).For information about the common abend codes, seethe zSecure Collect documentation in the user referencemanual for your zSecure product.

Severity: 08

CKF071I Internal error IOBEXCP DEBNMEXT=0

Explanation: This message indicates an unexpectedcondition; I/O was being attempted against an emptydata set. Contact IBM Software Support. The message issuppressible.

Severity: 24

CKF072I Unexpected IOCINFO return code rcreason code rr (decimal)

Explanation: This message indicates that the IOCINFOservice issued an unexpected return code. Results areunpredictable.

Severity: 08

CKF073I Dynamic configuration change occurred,UCB scan restarted - file may containduplicate records

Explanation: This message indicates that theUCBSCAN service indicated a configuration changewhile scanning all UCBs. The scan will be restarted, butthis may make the CKFREEZE file unusable if yourapplication does not support duplicate information. Inthis case, you will have to rerun zSecure Collect.

Severity: 04

CKF074I Unexpected UCBSCAN return code rcreason code rr (decimal)

Explanation: This message indicates that theUCBSCAN service issued an unexpected return code.

Severity: 12

CKF065I • CKF074I


CKF075I Unexpected EDTINFO return code rcreason code rr (decimal) for dev volumedevtype devtype

Explanation: This message indicates that theEDTINFO service issued an unexpected return codewhile trying to obtain the generic device type for adevice. The field will be filled with a default value.

Severity: 04

CKF076I Unexpected UCBSCAN return code rcreason code rr (decimal) on dev volume

Explanation: This message indicates that theUCBSCAN service issued an unexpected return codewhen trying to obtain the last path used mask.

Severity: 12

CKF077I Unexpected UCBSCAN return code rcreason code rr (decimal) on dev volume

Explanation: This message indicates that theUCBSCAN service issued an unexpected return codewhile trying to pin and obtain the address of a UCB.The intended authorized I/O function will not beperformed.

Severity: 12

CKF078I Unexpected UCBPIN UNPIN rc rcreason code rr (decimal) on dev volume

Explanation: This message indicates that the UCBPINservice issued an unexpected return code while tryingto unpin an UCB after an authorized I/O operation.

Severity: 12

CKF080I Unexpected IXCQUERY return code rcreason code rr (decimal)

Explanation: This message indicates that theIXCQUERY service issued an unexpected return code.The XCF sysplex record will be missing from the file.

Severity: 04

CKF081I Unexpected IXCQUERY return code rcreason code rr (decimal)

Explanation: This message indicates that theIXCQUERY service issued an unexpected return code.The XCF sysplex record will be missing from the file.

Severity: 04

CKF082I Unexpected IXCQUERY type abendxxx-nn (explanation)

Explanation: This message indicates that theIXCQUERY service abended. The XCF sysplex recordwill be missing from the file.

Severity: 04

CKF083I Extent size discrepancy sizeDEBNMTRK=num on dev volser

Explanation: There is an unexpected difference in thelow order two bytes of the number of tracks in anextent. The software uses DEBNMTRK (which may betoo small). Contact IBM Software Support.

Severity: 20

CKF084I Internal error CKFCCHH RC=20 on devvolser

Explanation: Contact IBM Software Support.

Severity: 24

CKF085I TTT conversion result CCC HHHH cccchhhh not in extent cccc hhhh - cccc hhhhfor reltrk on dev volser Extent nn rangecccc hhhh - cccc hhhh start reltrk size trks

Explanation: This message indicates a failure toconvert the indicated relative track number to anabsolute cylinder and head address. The requestedtrack will not be read. Generally this means that theinternal structure of a data set was not understoodproperly, for example, because of a new version of thesoftware maintaining that data set. Contact IBMSoftware Support.

Severity: 08

CKF086I Member mem rel trk trk Rrec not in devvolser dsn size trks trk

Explanation: This message indicates that a PDSdirectory entry points to a member start (relative trackand record number) beyond the end of the data set. Apossible cause might be that the data set was truncatedduring a copy or restore operation.

Severity: 04

CKF087I Missing EOF in member mem rel trk trkRrec in dev volser dsn size trks trk

Explanation: This message indicates that the lastmember physically present in a partitioned data setwas truncated before it's End Of File marker. Themember starts at the indicated relative track and recordnumber. A possible cause might be that the data setwas truncated during a copy or restore operation.There will be no checksum for this member.

CKF075I • CKF087I

14 Messages Guide

Severity: 04

CKF088I Missing n out of total members in devvolser dsn size trks trk

Explanation: This message indicates that a PartitionedData Set directory referred to members not physicallypresent in the data set. A possible cause might be thatthe data set was truncated during a copy or restoreoperation.

Severity: 04

CKF089I Unexpected DMS subfile name name atrecord nnn of DMSU volume datasetname

Explanation: The data set indicated by the DMSUNL=keyword contains an unknown subfile name. The dataset is not read any further.

Severity: 08

CKF090I type abend xxx-nn (explanation) on devvolume dataset

Explanation: This message indicates a nonrecoverableabend occurred during OPEN of the indicated TMC.For information on the common abend codes, see thezSecure Collect documentation in the user referencemanual for your zSecure product.

Severity: 08

CKF091I TRKCALC for dsname gives RC=nndecimal

Explanation: The calculation of the number of blocksper track for the TMC, VMF or ACF failed with theindicated return code. As a consequence, no blocks willbe read.

Severity: 08

CKF092I Opened type dev volume dataset, numby/bl num bl/tr num rc/bl num trk

Explanation: This message indicates that the type dataset (TMC for CA1, VMF for CA-TLMS, or ABR forFDR/ABR) has just been opened, and shows thecharacteristics used for reading the TMC/VMF. It isissued only if the INFO option was specified.

Severity: 00

CKF093I Unexpected block length nnn at rel tracknnn Rnn of type vol dataset

Explanation: This message indicates that a track readcontained an unexpected block size. The remainder ofthe track is skipped. The current relative track numberand physical record number are shown in decimal. Thetype can be TMC, VMF, or ABR.

Severity: 08

CKF093I Unexpected block prefix "ttttttt" at reltrack nnn Rnn of ABR vol dataset

Explanation: This message indicates that an ABR trackread contained an unexpected block prefix. The currentrelative track number and physical record number areshown in decimal.

Severity: 08

CKF094I Closed type dev volume dataset, read nnntracks, copied nnn type and nnnn DSNBrecords

Explanation: This informational message indicates thatthe TMC/VMF/ABR data set was closed and showsthe number of volume and data set records that werecopied to CKFREEZE. It is issued only if the INFOoption was specified.

Severity: 00

CKF095I Unsupported type blocksize nnn lreclnnn for volume dataset

Explanation: For type equal to TMC this messageindicates that the indicated data set had a record size(lrecl) different from 200 and 340 (CA1 5.0). For typeequal to VMF this message indicates that the recordsize was different from 500. For type equal to ABR thisindicates that the block size was smaller than 32 bytes.

Severity: 08

CKF096I type abend xxx-nn (explanation) on typedev volume dataset

Explanation: This message indicates a nonrecoverableabend occurred during OPEN of the indicated type dataset (DMSU for DMSUNL, PDSE for PDS/E directory, orPDSM for DMS AUTHLIB). For information on thecommon abend codes, see the zSecure Collectdocumentation in the user reference manual for yourzSecure product.

Severity: 08

CKF097I Opened type dev volume dataset, blksznnnn, lrecl nnnn lasttrk nnnnn

Explanation: This message indicates that the indicatedtype data set (DMSU for DMSUNL, PDSE for PDS/Edirectory, or PDSM for DMS AUTHLIB) has just beenopened, and shows the block size, record length, andlast relative track number (decimal). It is issued only ifthe INFO option was specified.

Severity: 00

CKF088I • CKF097I


CKF098I Unexpected record length n at recordnnn of DMSU volume dataset

Explanation: A record length smaller than 9 wasencountered, this is not supported for a DMS unload(each record is expected to start with the 8 byte subfilename). The remainder of the data set will be skipped.

Severity: 08

CKF099I Closed type dev volume dataset read nnnrecords, copied nnn DSNINDEX and

nnnn RACFENCD records

Explanation: This informational message indicates thatthe DMStype data set (DMSU for DMSUNL, PDSE forPDS/E directory, or PDSM for DMS AUTHLIB) wasclosed and shows the number of records read as wellas the number of data set and RACF profile recordsthat were copied to CKFREEZE. It is issued only if theINFO option was specified.

Severity: 00

Messages from 100 to 199

CKF100I Missing PDS directory end in dev vol dsn

Explanation: This message indicates that a data setthat was supposed to have a Partitioned Data Setorganization did not have a proper PDS directory (i.e.ending in a record with a key of high values). Possiblecauses are that the data set is not a PDS at all, or thatthe data set was truncated before the end of the PDSdirectory by a failed copy or restore operation.

Severity: 08

CKF101I Unexpected return code nn dec duringLISTCAT of dsn

Explanation: This message indicates a failure to locatea VSAM cluster name in the catalog. The cluster will beskipped. If you think the program should have foundit, contact IBM Software Support.

Severity: 08

CKF102I type catname on volume BLK decnum CISZdecnum, CASZ decnum byte, num CI/CA,num bl/CA, numtr/CA, nn bl/trk, nn bl/CI

Explanation: This informational message gives thecontrol interval size, the number of bytes, blocks, andtracks in a control area, and the number of blocks pertrack and blocks per control intervals for the specifiedtype VSAM data set (BCS for catalog, MCD for HSMmigration Control Data set, BCD for HSM BackupControl Data set, RMM for DFSMS RMM control dataset) immediately before it is opened. It is issued only ifthe INFO option is selected.

Severity: 00

CKF103I No imbed - index indexname on volumeBLK decnum CISZ decnum

Explanation: This message indicates that the indexcomponent about to be opened has the NOIMBEDattribute, which makes it necessary to process theindex. The message indicates the index component dataset name, as well as the physical block size and CI size.It is issued only if the INFO option is selected.

Severity: 00

CKF104I Closed IX dev volume catname indexincore decnum bytes - indexname

Explanation: This informational message summarizesthe number of bytes that were read from the catalogindex component prior to closing. It is issued only ifthe INFO option was selected.

Severity: 00

CKF105I Opened type dev volser catname size numtrk datacomponent

Explanation: This informational message contains thenumber of tracks in the data component of the typedata set (see CKF102I) that has just been openedsuccessfully. It is issued only if the INFO option wasselected.

Severity: 00

CKF106I Master catalog is catname

Explanation: This informational message indicates thename of the master catalog. It is issued only if theINFO option was selected.

Severity: 00

CKF107I Opened ACB dev volume clustercomponent dsname

Explanation: This informational message indicates thesuccessful opening of the ACB for the indicated VSAMdata set. It is issued only if the INFO option wasselected.

Severity: 00

CKF108I Closed ACB dev volume cluster readdecnum, copied decnum recordsdatacomponent

Explanation: This informational message shows thenumber of records read and copied from the indicated

CKF098I • CKF108I

16 Messages Guide

VSAM data set. It is issued only if the INFO optionwas selected.

Severity: 00

CKF109I Opened dsntype dev volume dsname [ allocsize nn trk ]

Explanation: This informational message indicates thesuccessful opening of the PDS(E) indicated, and, for aPDS, the size of the data set in tracks. It is issued onlyif the INFO option was selected.

Severity: 00

CKF110I Closed PDS dev volume dsname readdecnum trks, copied decnum dir blks,scanned decnum byte in decnum members

Explanation: This informational message indicates thenumber of directory tracks and blocks read from theindicated PDS. It is issued only if the INFO option wasselected.

Severity: 00

CKF111I Scheduler allocated decnum I/Oexecutors

Explanation: This informational message shows theamount of parallelism introduced by the PARALLELparameter or its default. It is issued only if theREPORT or INFO option was selected or defaulted.

Severity: 00

CKF112I Opened VTOC dev volume size decnumtracks

Explanation: This informational message indicates thesuccessful opening of the VTOC for the indicatedvolume. It is issued only if the INFO option wasselected.

Severity: 00

CKF113I Closed VTOC dev volume read numtracks, copied decnum DSCBs

Explanation: This informational message summarizesthe number of tracks and records that were read fromthe VTOC prior to closing. It is issued only if the INFOoption was selected.

Severity: 00

CKF114I Opened SYS1.VVDS.Vvolume sizedecnum tracks, nnn blk/trk

Explanation: This informational message indicates thesuccessful opening of the indicated VVDS and thenumber of 4KB blocks per track. It is issued only if theINFO option was selected.

Severity: 00

CKF115I Closed SYS1.VVDS.Vvolume read numtracks, copied decnum NVR/VVRs

Explanation: This informational message summarizesthe number of tracks and records that were read fromthe VVDS prior to closing. It is issued only if the INFOoption was selected.

Severity: 00

CKF116I Closed type dev volume catname read numtrks, num records, copied decnum/decnumnon/spanned records

Explanation: This informational message summarizesthe number of tracks and records (both non-spannedand spanned) that were read and copied from the datacomponent of the type data set (see CKF102I) prior toclosing. It is issued only if the INFO option wasselected.

Severity: 00

CKF117I CP response truncated for command"command": response

Explanation: This message indicates that the responseto the specified CP command issued while runningunder VM did not fit into the return area. The first 5lines of the response are displayed. As a result,information collected by the command may be missingfrom the CKFREEZE file.

Severity: 12

CKF118I CP return code nn on command"command": response

Explanation: This message indicates the nonzeroreturn code returned by CP on the specified commandissued while running under VM. As a result,information collected by the command will be missingfrom the CKFREEZE file.

Severity: 12

CKF119I Q Vnnnn returns data for nnnn -possibly unsupported VM release

Explanation: While running an XA release of MVSunder VM, the QUERY VIRTUAL command issued byzSecure Collect unexpectedly returned informationfrom a different device. The information is notprocessed.

Severity: 12

CKF109I • CKF119I


CKF120I Unexpected IOS rc xx x, CSW stat xxxxsns xxxx id cccc/mm dddd/mm v/r=vv/rrdev dev volser during CCWname

Explanation: This message indicates a failed I/Ooperation of the type CCWname on the indicateddevice. The Channel Status Word and the first 2 bytesof the sense code are shown in hexadecimal, togetherwith the hexadecimal controller type cccc and modelmm and device type dddd and model mm, as returnedby the Sense Id, and the Virtual and Physical controllertype returned by the ReadDeviceCharacteristics. Thelatter are needed to determine the exact device typeand mode of 3990 models and RAMAC devices. Checkfor a possible hardware defect. More diagnosticinformation might be available in a directly subsequentmessage CKF144I.

Severity: 08

CKF121I Unexpected nil name pointer in product

Explanation: This message has two forms. the firstshows the name of a pointer that was unexpectedlyfound to be zero during access to a control block chainwith cross memory services in an address space for thespecified product (HSM, JES2, JES3, RMM, TLMS).

Severity: 04

CKF121I Unexpected null ASID for product

Explanation: The second form of this message showsthat the Address Space Id was unexpectedly found tobe zero during access to a control block chain withcross memory services in an address space for thespecified product (HSM, JES2, JES3, RMM, TLMS).

Severity: 04

CKF122I Number of TAPE devices interrogated:nnn

Explanation: This message, shown if TAPE=YES wasspecified or implied, shows the number of tape devicesthat were interrogated.

Severity: 00

CKF123I Q V mmm query for device nnnn returnsdata for nnnn - possibly unsupportedVM release

Explanation: While running a non-XA release of MVSunder VM, the QUERY VIRTUAL command issued byzSecure Collect to the VM device number mmm onbehalf of the nnnn device number in MVS,unexpectedly returned information from a differentdevice. The information is not processed.

Severity: 12

CKF124I Non-SMS system

Explanation: This informational message is issued toindicate that the SMS subsystem is not defined on thesystem.

Severity: 00

CKF125I SMS is inactive

Explanation: This informational message is issued toindicate that the SMS subsystem is defined, butinactive. No SMS information will be present in theCKFREEZE file.

Severity: 04

CKF126I SMS IEFSSREQ RC=nn (decimal) forrequest SSSA1TYP=nn (decimal)

Explanation: This message indicates the failure of aSMS subsystem request. The requested SMSinformation will be missing from the CKFREEZE file.

Severity: 08

CKF127I SMS return code SSOBRETN=nn(decimal) reason code SSSARSN=nnn(decimal) for request SSSA1TYP=nn(decimal)

Explanation: This message indicates the failure of aSMS information request. The requested SMSinformation will be missing from the CKFREEZE file.

Severity: 08

CKF128I SMS returned reason codeSSSARSN=nnn (decimal) and messagesfor request SSSA1TYP=nn (decimal):messages

Explanation: This message indicates the possiblefailure of a SMS information request. Informational orerror messages returned by SMS follow this message.The requested SMS information may be missing fromthe CKFREEZE file.

Severity: 04

CKF129I Unexpected SMS call type abend xxx-nn(explanation) for request SSSA1TYP=nn(decimal)

Explanation: This message indicates the abend issuedduring a SMS information request. The requested SMSinformation will be missing from the CKFREEZE file.

Severity: 08

CKF120I • CKF129I

18 Messages Guide

CKF130I SMS type name configuration description

Explanation: This informational message indicates thatthe complex of type type and name name has SMSactive and shows the comment (description) field of theactive configuration.

Severity: 00

CKF131I LCU selection not possible

Explanation: This message indicates that a LCUselection was given but no LCU information could befound in the system. The run is aborted. Possiblereasons include: RMF was not active, running under aVM system, or an unsupported RMF release.

Severity: 12

CKF132I Tape management system CA1 v.r.nl

Explanation: This message indicates that CA1 wasfound to be active on the system, and shows the releasein the form version.release.newsletter

Severity: 00

CKF133I FOCUS must precede parametersselecting additional information to becollected

Explanation: This message is issued if FOCUS was notthe first parameter, and you specified a parameter thatis not allowed under each focus before the FOCUSparameter. Move the FOCUS parameter in front.

Severity: 12

CKF134I Command not valid in current FOCUS -name

Explanation: This message indicates that a feature wasrequested that is invalid under the current focuscombination. You can look up the command name inthe index and read the restrictions.

Severity: 12

CKF135I site-specific identification string Runs onwhere CPU-id, source file ddname volserdsn

Explanation: This message shows the site-specificidentification string, CPU-id, and relevant productnumbers and names.

Severity: 00

CKF136I CLOSE abend xxx-rc on device devvolume volser for dsname

Explanation: The data set named dsname could not beclosed on device dev. The VTOC is indicated with** VTOC volser **. For information on the commonabend codes, see the zSecure Collect documentation inthe user reference manual for your zSecure product.

Severity: 08

CKF137I ACB CLOSE failed for type dev volumedatacomp rc=nn code=code cluster dsname

Explanation: The VSAM data set data componentdatacomp could not be closed. See the appropriate DFPmanual for the meaning of the codes.

Severity: 08

CKF138I GET RPL type dev volume datacomponentrc=nn reason=nnnn after nnnn records

Explanation: This messages indicates an unexpectedreturn code and reason code (in decimal) from theVSAM GET macro after the indicated number ofrecords.

Severity: 08

CKF139I TRKCALC for SYS1.VVDS.Vvolumegives RC=nn decimal

Explanation: The calculation of the number of blocksper track for the VVDS failed with the indicated returncode. As a consequence, the space map will not be usedand all tracks of the VVDS will be read.

Severity: 08

CKF140I Number of RACFENCD records copied:nnnn

Explanation: This message indicates the number ofrecords copied from the RACFENCD subfiles of DMSDMSFILES and unloaded DMSFILES data sets. TheRACFENCD subfile gives the relation between data setnames of archived or backed-up data sets and thecorresponding RACF profiles with an encoded name.

Severity: 00

CKF141I Number of DSNINDEX records copied:nnnn

Explanation: This message indicates the number ofrecords copied from the RACFENCD subfiles of DMSDMSFILES and unloaded DMSFILES data sets. Itincludes all archived and backed-

Documents

Security zSecure Version 2.1 · using the IBM® Security zSecure™ 2.1.1 products. It provides explanations for these messages and errors. The information in this guide that applies