ibm tivoli advanced backup and recovery for z/os:...

IBM Tivoli Advanced Backup and Recovery for z/OS

Messages

Version 2 Release 1

GC23-9731-00IBM Confidential

��

Note:

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

This edition applies to Version 2 Release 1 of IBM Advanced Backup and Recovery for z/OS(product number

5698–B17) and to all subsequent releases and modifications until otherwise indicated in new editions.

© Copyright Rocket Software Inc., 1998, 2008

IBM Confidential

Contents

About this guide . . . . . . . . . . . . . . . . . . . . . . . . v

Intended audience for this guide . . . . . . . . . . . . . . . . . . . v

Publications . . . . . . . . . . . . . . . . . . . . . . . . . . v

Accessing publications online . . . . . . . . . . . . . . . . . . . v

Ordering publications . . . . . . . . . . . . . . . . . . . . . . vi

Accessing terminology online . . . . . . . . . . . . . . . . . . . . vi

Tivoli technical training . . . . . . . . . . . . . . . . . . . . . . vi

Support information . . . . . . . . . . . . . . . . . . . . . . . vii

Conventions used in this publication . . . . . . . . . . . . . . . . . vii

Typeface conventions . . . . . . . . . . . . . . . . . . . . . vii

Chapter 1. Advanced Backup and Recovery for z/OS Messages . . . . . . 1

Chapter 2. Advanced Backup and Recovery for z/OS Messages (BKM9) . . 3

Chapter 3. Advanced Backup and Recovery for z/OS Messages (BKMA) . . 9

Chapter 4. Advanced Backup and Recovery for z/OS Messages (BKMB) 71

Chapter 5. Advanced Backup and Recovery for z/OS Messages (BKMC) 103

Chapter 6. Advanced Backup and Recovery for z/OS Messages (BKMD) 113

Chapter 7. Advanced Backup and Recovery for z/OS Messages (BKME) 115

Chapter 8. Advanced Backup and Recovery for z/OS Messages (BKMF) 119

Chapter 9. Advanced Backup and Recovery for z/OS Messages (BKMG) 121

Chapter 10. Advanced Backup and Recovery for z/OS Messages (BKMH) 123

Chapter 11. Advanced Backup and Recovery for z/OS Messages (BKMI) 143

Chapter 12. Advanced Backup and Recovery for z/OS Messages (BKMJ) 157

Chapter 13. Advanced Backup and Recovery for z/OS Messages (BKMK) 163

Chapter 14. Advanced Backup and Recovery for z/OS Messages (BKML) 217

Chapter 15. Advanced Backup and Recovery for z/OS Messages (BKMM) 219

Chapter 16. Advanced Backup and Recovery for z/OS Messages (BKMP) 225

Chapter 17. Advanced Backup and Recovery for z/OS Messages (BKMS) 243

Chapter 18. Advanced Backup and Recovery for z/OS Messages (BKMV) 251

Support information . . . . . . . . . . . . . . . . . . . . . . 261

Using IBM Support Assistant . . . . . . . . . . . . . . . . . . . 261

Obtaining fixes . . . . . . . . . . . . . . . . . . . . . . . . 261

Contacting IBM Software Support . . . . . . . . . . . . . . . . . 262

Determining the business impact . . . . . . . . . . . . . . . . . 263

Describing problems and gathering information . . . . . . . . . . . 263

IBM Confidential

iii

Submitting problems . . . . . . . . . . . . . . . . . . . . . 263

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . 266

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

IBM Confidential

iv IBM Tivoli Advanced Backup and Recovery for z/OS: Messages

About this guide

This book provides message descriptions for IBM Tivoli Advanced Backup and

Recovery for z/OS.

Intended audience for this guide

This book is intended for those persons responsible for installing, configuring and

using IBM Tivoli Advanced Backup and Recovery for z/OS and assumes working

knowledge of:

v The z/OS® operating system

v The Microsoft® Windows® operating system

Publications

The following publications are included in the Advanced Backup and Recovery for

z/OS product library:

v IBM Tivoli Advanced Backup and Recovery for z/OS Program Directory,

GI11-8886

Provides hardware and software prerequisites and instructions for the Advanced

Backup and Recovery for z/OS SMP/E installation.

v IBM Tivoli Advanced Backup and Recovery for z/OS User's Guide, SC23-9730

Provides instructions for using Advanced Backup and Recovery for z/OS.

v IBM Tivoli Advanced Backup and Recovery for z/OS Monitoring Agent Planning

and Configuration Guide, SC23-9732

Provides instructions for planning, installing, and configuring Advanced Backup

and Recovery for z/OS. This publication includes the following types of

information:

– Information and worksheets to help you plan your configuration

– A list of prerequisite steps to complete before configuring the product

– Instructions for configuring the monitoring server and monitoring agent on a

z/OS system

– Instructions for installing and setting up the distributed components of the

product

– Information about using system variables and batch processing to expand a

configuration across the enterprise

– Security considerations and advice

v IBM Tivoli Advanced Backup and Recovery for z/OS Monitoring Agent User's

Guide, SC23-9733

Provides instructions for using Advanced Backup and Recovery for z/OS to

monitor z/OS system and sysplex resources, and product-specific monitoring

scenarios.

v IBM Tivoli Advanced Backup and Recovery for z/OS Messages, GC23-9731

Lists and explains Advanced Backup and Recovery for z/OS messages.

Accessing publications online

IBM® posts publications for this and all other Tivoli® products, as they become

available and whenever they are updated, to the Tivoli Information Center Web site

at http://www.ibm.com/software/tivoli/library/.

IBM Confidential

v

http://www.ibm.com/software/tivoli/library/

In the Tivoli Information Center window, click Tivoli product manuals. Click the

letter that matches the first letter of your product name to access your product

library. For example, click M to access the IBM Tivoli Monitoring library or click O

to access the IBM Tivoli OMEGAMON® library.

Note: If you print PDF documents on other than letter-sized paper, set the option in

the File > Print window that allows Adobe® Reader to print letter-sized

pages on your local paper.

Reading CCR2 online

IBM publishes CCR2™, a useful monthly e-newsletter for the System z™ and

zSeries® software community. You can find the latest issue of CCR2 at

http://www-306.ibm.com/software/tivoli/features/ccr2/info.html.

Ordering publications

You can order many Tivoli publications online at the following Web site:

http://www.elink.ibmlink.ibm.com/public/applications/ publications/cgibin/pbi.cgi.

You can also order by telephone by calling one of these numbers:

v In the United States: 800-879-2755

v In Canada: 800-426-4968

In other countries, contact your software account representative to order Tivoli

publications. To locate the telephone number of your local representative, perform

the following steps:

1. Go to http://www.elink.ibmlink.ibm.com/public/applications/ publications/cgibin/pbi.cgi.

2. Select your country from the list and click Go.

3. Click About this site in the main panel to see an information page that includes

the telephone number of your local representative.

Accessing terminology online

The Tivoli Software Glossary includes definitions for many of the technical terms

related to Tivoli software. The Tivoli Software Glossary is available at the following

Tivoli software library Web site:

http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm

The IBM Terminology Web site consolidates the terminology from IBM product

libraries in one convenient location. You can access the Terminology Web site at the

following Web address:

http://www-306.ibm.com/software/globalization/terminology

Tivoli technical training

For Tivoli technical training information, refer to the following IBM Tivoli Education

Web site:

http://www.ibm.com/software/tivoli/education

IBM Confidential

vi IBM Tivoli Advanced Backup and Recovery for z/OS: Messages

http://www-306.ibm.com/software/tivoli/features/ccr2/info.html

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi



http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm

http://www-306.ibm.com/software/globalization/terminology

http://www.ibm.com/software/tivoli/education

Support information

If you have a problem with your IBM software, you want to resolve it quickly. IBM

provides the following ways for you to obtain the support you need:

v IBM Support Assistant: You can search across a large collection of known

problems and workarounds, Technotes, and other information at

http://www.ibm.com/software/support/isa.

v Obtaining fixes: You can locate the latest fixes that are already available for your

product.

v Contacting IBM Software Support: If you still cannot solve your problem, and you

need to work with someone from IBM, you can use a variety of ways to contact

IBM Software Support.

For more information about resolving problems, see “Support information” on page

261.

Conventions used in this publication

This guide uses several conventions for special terms and actions and for operating

system-dependent commands and paths.

Typeface conventions

This guide uses the following typeface conventions:

Bold

v Lowercase commands and mixed case commands that are otherwise

difficult to distinguish from surrounding text

v Interface controls (check boxes, push buttons, radio buttons, spin

buttons, fields, folders, icons, list boxes, items inside list boxes,

multicolumn lists, containers, menu choices, menu names, tabs, property

sheets), labels (such as Tip: and Operating system considerations)

v Keywords and parameters in text

Italic

v Words defined in text

v Emphasis of words (words as words)

v New terms in text (except in a definition list)

v Variables and values you must provide

Monospace

v Examples and code examples

v File names, programming keywords, and other elements that are difficult

to distinguish from surrounding text

v Message text and prompts addressed to the user

v Text that the user must type

v Values for arguments or command options

IBM Confidential

About this guide vii

http://www-306.ibm.com/software/support/isa

IBM Confidential

viii IBM Tivoli Advanced Backup and Recovery for z/OS: Messages

Chapter 1. Advanced Backup and Recovery for z/OS

Messages

Use the information in these messages to help you diagnose and solve Advanced

Backup and Recovery for z/OS problems.

Message format

Advanced Backup and Recovery for z/OS messages adhere to the following format:

BKMinnnnx

Where:

BKM Indicates that the message was issued by Advanced Backup and Recovery

for z/OS

i Indicates the message identifier

nnn Indicates the message identification number

x Indicates the severity of the message:

A Indicates that operator intervention is required before processing

can continue.

E Indicates that an error occurred, which might or might not require

operator intervention.

I Indicates that the message is informational only.

W Indicates that the message is a warning to alert you to a possible

error condition.

Each message also includes the following information:

Explanation:

The Explanation section explains what the message text means, why it

occurred, and what its variables represent.

User response:

The User response section describes whether a response is necessary,

what the appropriate response is, and how the response will affect the

system or program.

IBM Confidential

1

IBM Confidential

2 IBM Tivoli Advanced Backup and Recovery for z/OS: Messages


Messages (BKM9)

BKM99801E Control display save error

Explanation:

Error saving table values.

User response:

Try the panel option again. If the problem persists

contact Technical Support.

BKM99802E Control display restore error

Explanation:

Error restoring table values.

User response:



BKM99803E Table for this application in use

Explanation:

The table to display is currently in use.

User response:



BKM99804E Table create error

Explanation:

The table could not be created.

User response:



BKM99805W DUPL table found

Explanation:

Duplicate table found - processing continues.

User response:

If the warning persists contact Technical Support.

BKM99806I TBEND on open failed

Explanation:

The table could not be closed before recreating.

User response:

If the problem persists contact Technical Support.

BKM99807W TBTOP failed

Explanation:

The table could not be positioned at the top.

User response:

If the problem persists contact Technical Support.

BKM99808W Table add error

Explanation:

An error occurred adding table entry.

User response:

Try the panel option again. If the problem persists,


BKM99809E TBADD failed - RC > 8

Explanation:

An error occurred adding table entry.

User response:



BKM99810E TBPUT failed

Explanation:

An error occurred putting table entry.

User response:

Try the panel option again. If the problem persists,


BKM99811E TBGET failed

Explanation:

An error occurred getting table entry.

User response:



BKM99815E TBVCLEAR failed

Explanation:

The table variables were not cleared.

User response:



BKM99816E TBDELETE failed

Explanation:

The table was not deleted.

User response:



BKM99820E LMINIT DATAID not created

Explanation:

The LMINIT routine could not create DATAID.

IBM Confidential

3

User response:



BKM99821E LMINIT failed

Explanation:

LMINIT routine failed.

User response:



BKM99822E LMOPEN failed

Explanation:

LMOPEN routine failed.

User response:



BKM99823E LMCLOSE failed.

Explanation:

LMCLOSE routine failed.

User response:



BKM99824E LMFREE failed

Explanation:

LMFREE routine failed.

User response:



BKM99825E ENDREQ failed, contact technical

support

Explanation:

ENDREQ failed to close JCL properly therefore a job

number is not returned and the job is not submitted.

User response:

Logoff TSO which should cause the INTRDR DD to

close and submit the JCL. If it does not, submit then

rerun the routine and submit the JCL using the

BUILD/VIEW JCL option. Contact Technical Support.

BKM99849E Getnext error, SI27 failed

Explanation:

SI27 failed when getting a record.

User response:



BKM99849E Getnext error, SI27 failed

Explanation:

SI27 failed when getting a record.

User response:



BKM99851E Put error, SI27 failed RC=

Explanation:

SI27 failed when putting a record.

User response:



BKM99852E End error, SI27 failed RC=

Explanation:

SI27 failed when closing the table.

User response:



BKM99853E Create error, SI27 failed RC=

Explanation:

SI27 failed when creating the table.

User response:



BKM99854E Point error, SI27 failed RC=

Explanation:

SI27 failed when pointing to a record in the table.

User response:



BKM99855E Error add refind option

Explanation:

An error occurred while enabling the refind option.

User response:



BKM99860E Date calculation error

Explanation:

SI19 failed to calculate the date correctly.

User response:



BKM99821E • BKM99860E IBM Confidential


BKM99901E Parm check failed

Explanation:

The parms passed to a subsequent program were

invalid.

User response:



BKM99902E No parms passed

Explanation:

The subsequent program requires parms to be passed.

User response:



BKM99903E Parm # invalid

Explanation:

The parm passed to a subsequent program is invalid.

User response:



BKM99904E Error creating panel variables

Explanation:

During panel display the proper variables could not be

created.

User response:



BKM99905E Error during data retrieval

Explanation:

An error was encountered retrieving input data.

User response:



BKM99906E Panel display error (panel)

Explanation:

The panel identified could not be displayed.

User response:



BKM99907E Error defining variable pool #

Explanation:

Variable pool # could not be created.

User response:



BKM99910E Error opening database

Explanation:

An error occurred when opening the database.

User response:



BKM99911E Error closing database

Explanation:

An error occurred when closing the database.

User response:



BKM99912E Error during VREAD

Explanation:

An error occurred when reading the database.

User response:



BKM99913E Error during VRDNEXT

Explanation:

An error occurred when reading the next record in the

database.

User response:



BKM99914E Error during VREADUPD

Explanation:

An error occurred when reading for update in the

database.

User response:



BKM99915E Error during VPOINTF

Explanation:

An error occurred when pointing to a record in the

database.

User response:



BKM99916E Error during VPOINTB

Explanation:

An error occurred when pointing to a record in the

database.

User response:

BKM99901E • BKM99916EIBM Confidential

Chapter 2. Advanced Backup and Recovery for z/OS Messages (BKM9) 5



BKM99917E Error during VDELETE

Explanation:

An error occurred when deleting a record from the

database.

User response:



BKM99918E Error calling BKM01VV1 tttttttt Function:

function R15=nnnn R0=nnnnnnnn ID=lllll

MOD=mmmm

Explanation:

A problem occurred using a dataspace. tttttttt is the

name of the internal table. lllll is the location where the

error occurred. Processing terminates.

User response:

Call Technical Support.

BKM99920E Error writing to database

Explanation:

An error occurred when writing a record to the

database.

User response:



BKM99921E Write failed, no space in database

Explanation:


database.

User response:

Check database size, verify space is available and try

option again. If the problem persists contact Technical

Support.

BKM99922E Write failed, duplicate record found

Explanation:


database.

User response:



BKM99923E Error rewriting to database

Explanation:

An error occurred when rewriting a record to the

database.

User response:



BKM99930E Error allocating DSN

Explanation:

An error occurred when allocating an internal data set.

User response:



BKM99931E Error freeing DSN

Explanation:

An error occurred when freeing an internal data set.

User response:



BKM99932E Error allocating SYSOUT

Explanation:

An error occurred when allocating SYSOUT DD.

User response:

Try submitting again. If the problem persists contact

Technical Support.

BKM99933E Error closing JCL

Explanation:

During a submit, the created JCL output file could not

be closed.

User response:

Try submitting again. If the problem persists contact

Technical Support.

BKM99940E INI parm not found: section/parm

Explanation:

Required INI parm not found.

User response:

Check INI for section or parm specified. Correct the

problem and try again. If the problem persists contact

Technical Support.

BKM99941E INIGET FAILED: section/parm

Explanation:

Error getting INI parm.

User response:

Check INI for section or parm specified. Correct the

problem and try again. If the problem persists contact

Technical Support.

BKM99917E • BKM99941E IBM Confidential


BKM99942E INI parm length invalid: section/parm

(char expected)

Explanation:

INI parm length invalid.

User response:

Check INI for section or parm specified and shown

length. Correct problem and try again. If the problem

persists contact Technical Support.

BKM99943E Invalid BADBKUPRC INI value -

contains non-numeric values from

PROCESS_OPTIONS_ISPF/QUICK_RESTORE_BADBKUPRC

Explanation:

The value specified in a INI member in the PARMLIB is

invalid. The value was specified in the

PROCESS_OPTIONS_ISPF section for the parameter

QUICK_RESTORE_BADBKUPRC.

User response:

Correct the value to be in the numeric range of 0 - 9999

and try the restore again.

BKM99950E ZIP FAILURE: message

Explanation:

An error occurred as described in the message.

User response:



BKM99960E Error during FREEMAIN of SMS

interface

Explanation:

An error occurred interfacing with SMS.

User response:



BKM99961E Error during VPOINTF

Explanation:

An error occurred when pointing to record in database.

User response:

Retry the application. If the problem persists contact

Technical Support.

BKM99962E Error during VRDNEXT

Explanation:

An error occurred when reading the next record in

database.

User response:


Technical Support.

BKM99963E VSAM error, VREWRITE

Explanation:

An error occurred when trying to update a record in the

database.

User response:


Technical Support.

BKM99964E Error opening database

Explanation:

An error occurred when opening the database.

User response:


Technical Support.

BKM99970E Inventory data set does not support

compression

Explanation:

The Inventory Data Set (IDS) stores records in a

compressed format but the IDS indicates compressed

records are not supported.

User response:

Run the DBINIT function against the IDS to convert it to

support compressed records.

BKM99971E If inventory data set is for BRM release

0601 or later, run the IDS conversion

utility.

Explanation:

See BRM9970E.

User response:

See BRM9970E.

BKM99972E xxxxxxxx function terminated

Explanation:

This message relates to BKM9970E. The function,

xxxxxxxx, was terminated due to the problem detected

as indicated in the message BKM9970E.

User response:

See BKM9970E.

BKM99973E Failed to find equivalent utility

program. JFLT Record Entry = ″entry

from JFLT record″.

Explanation:

This message is issued during the building of the Batch

Intercept File (BIF). It gets issued when a JFLT record

(from the IDS) contains a utility program name that does

not have an alternate. The name is used internally to

know how to track jobs of a certain program name. This

could happen if a utility name has been renamed in a

mainframe environment and it has not been registered

BKM99942E • BKM99973EIBM Confidential

Chapter 2. Advanced Backup and Recovery for z/OS Messages (BKM9) 7

as an a different name. For example, if IEBGENER has

been renamed to MYGENER, that needs to registered

so batch intercept processing knows what to do when

MYGENER is encountered.

User response:

If the utility has an alternate name and is not registered,

register it by going into this product’s ISPF interface and

going into the top menu item called ″ADMIN″ and

register the alternate name of the utility. Once done,

rebuild the BIF and see if the error message goes away.

if it doesn’t, copy the error message issued and contact

technical support. Be sure to provide the error message.

IBM Confidential



Messages (BKMA)

BKMA12129E DADSMFTK not active

Explanation:

DAD is not active on this image.

User response:

DADSMFTK must be active on the image running the

DADFLUSH STEP. Check for other log messages.

BKMA0101E Obtain common storage failed

Explanation:

An unrecoverable error occurred during processing.

User response:


BKMA0102E Unable to find ARCWCTL in CDE

Explanation:


User response:


BKMA0103E No module found to change

Explanation:


User response:


BKMA0104I Retrying serialization for xxxx

Explanation:

ABARS attempted to acquire a shared ENQ for

resource xxxx and failed. The ENQ will be retried every

30 seconds. The number of times the retry should be

attempted is specified by token ENQ_FAIL_RETRYS =

n in section BACKUP_OPTIONS in the INI.

User response:

None.

BKMA1901E Aggregate construct not found

Explanation:

This aggregate is not defined to SMS.

User response:

Define the aggregate using ISMF, activate a new

configuration and retry the job.

BKMA0198I Processing continues without tracking

Explanation:


User response:

The ABARS function continues but tracking will fail. The

activity log may be loaded after the event has

completed.

BKMA0299E Product internal error

Explanation:


User response:

Processing for the ABARS stops. Call Technical

Support.

BKMA0301W SWARES failed: CCOFF parm ignored

Explanation:

An internal error occurred during ABACKUP processing

when attempting to determine the output file type (.D. or

.I). Processing continues but the request to turn off CC

processing (if used) will be ignored.

User response:

If the problem continues, call Technical Support for

assistance.

BKMA403W Concurrent copy initialization failed

for: nnnn terminate the backup? (Y/N)

Explanation:

Error during concurrent copy initialization for data set

nnnn.

User response:

Respond to the WTOR with Y to terminate the

aggregate backup or N to continue without concurrent

copy.

BKMA404E Invalid reply to message

Explanation:

Invalid reply to message BKMA0403W.

User response:

Respond to the WTOR with Y or N.

BKMA0499E Error returned from IRXJCL

Explanation:


User response:


BKMA0501E Function FAIL. RC = nnnnnnnn

Explanation:

IBM Confidential

9

The function (ENQ or DEQ failed with the reported

return code.

User response:

Note the return code and press Enter. If the return code

= 18, see accompanying message BKMA0502E.

Otherwise follow the instructions on the panel.

BKMA0502E Environmental error. You have reached

the limit for the number of concurrent

resource requests. Retry the request

one or more times. If the problem

persists, ask your system programmer

to tune the system so that the limit is

no longer exceeded.

Explanation:

Self explanatory.

User response:

Specified in message.

BKMA0601W Aggregate not found in ISMF:

xxxxxxxx default values will be used

Explanation:

Aggregate xxxxxxxx was not found in ISMF but was

found in the IDS so default values will be used: Retain

Backup Versions value will be set to 1.

User response:

Verify the aggregate in the message exists in the IDS

but not in ISMF. If aggregate no longer exists then

aggregate in the IDS should be deleted.

BKMA0701E EXEC parm value is invalid

Explanation:

The value in the EXEC parm is not valid.

User response:

Determine the reason for the open failure and retry job.

BKMA0702E OPEN ERROR: ddname

Explanation:

An open error occurred for the ddname indicated.

User response:


BKMA0703E Unknown command

Explanation:

The SYSIN command listed just prior to this message

contains an invalid command. Valid commands are

ABACKUP and ARECOVER.

User response:

Correct the syntax error and resubmit the job.

BKMA0704E SYSIN file empty

Explanation:

The SYSIN file contains no commands.

User response:

Correct the error and resubmit the job.

BKMA0705E Expected continuation not found:

Explanation:

The SYSIN file contains a syntax error.

User response:

Correct the error and resubmit the job.

BKMA0706E HSM is in debug mode

Explanation:

HSM was found to be in debug mode. While in this

mode, no data movement will be done.

User response:

Use SETSYS to set HSM to NODEBUG and retry the

job.

BKMA0707E Error while trying to extract HSM data

Explanation:

HSM was either not active or HSM control blocks were

not constructed as expected.

User response:

Check job log for additional messages. If HSM was not

active start it and retry the job. If reason cannot be

determined, call Technical Support.

BKMA0708E Error retrieving INVDB

Explanation:

An error occurred obtaining the INVDB name thru

JFCB.

User response:

Try running batch process again. If the problem

persists, call Technical Support.

BKMA0709W RACROUTE error

Explanation:

An error occurred obtaining RACF® Information for the

Inventory Data Set.

User response:

The process will continue although the warning is

displayed. Please call Technical Support and provide

the details of the displayed message.

BKMA0502E • BKMA0709W IBM Confidential


BKMA0710E CATSCRUB function not licensed on

this CPU

Explanation:

The current INI does not contain a valid product license

key for CATSCRUB.

User response:

Modify the current product license key to include

CATSCRUB function. If you do not have a valid product

key please contact Technical Support.

BKMA0711I CATSCRUB processing completed

highest return code is xx

Explanation:

The processing completed and the highest return code

is displayed.

User response:

None.

BKMA0717E Unknown command in command

starting on line 0 command : x

Explanation:

x is an invalid command.

User response:

Correct the command syntax and retry.

BKMA0718I List of commands until invalid

command

Explanation:

List of commands scanned prior to finding an error

follows.

User response:

None.

BKMA0799E Load of TSOENV; failed return code =

xx

Explanation:


User response:


BKMA0801E (Un)allocation failed: xxxxx

Explanation:

Dynamic allocation failed for the file specified.

User response:

Fix the problem, if it is a customer issue and retry the

job. If it is not or the problem persists, call Technical

Support.

BKMA0803E Non-zero return from HSEND command

Explanation:

A non-zero return code was returned from the TSO

HSEND command.

User response:

Check sysout and system log to determine the source

of problem. If unable to determine the cause of the

problem or if the problem persists, call Technical

Support.

BKMA0804E No HSM ABACKUP started task found

for : xxxxxxxx

Explanation:

HSEND ABACKUP WAIT command produced a return

code of zero but ABR determined that HSM never got

control.

User response:

Check sysout for any previous messages. Check

system log for messages. If still unable to determine the

reason for the failure, issue the HSEND command from

ISPF option 6 to see if any messages are returned by

HSEND that ABR was unable to trap. If the reason for

the error still cannot be determined, call Technical

Support for assistance.

BKMA0805E ABARS function failed in HSM.

Explanation:

The task determined that an error occurred in the HSM

secondary address space.

User response:

Check the system log for ″BKM″ error messages. Call

Technical Support for help in resolving the error if

necessary.

BKMA0806E No activity log found for this task.

Explanation:

Unable to find an activity log for this task.

User response:

Check for any messages preceding this one. If unable

to determine the reason for this error, call Technical


BKMA0807E Error calling xxxxxxxx R15=nnnn ID=lllll

Explanation:

A problem occurred calling an internal utility program.

xxxxxxxx is the program name. lllll is the location where

the error occurred. Processing terminates.

User response:

Contact Technical Support. Have available the listing

that contains this message and the parmlib member that

controls execution.

BKMA0710E • BKMA0807EIBM Confidential

Chapter 3. Advanced Backup and Recovery for z/OS Messages (BKMA) 11

BKMA0808E Open failed for: xxxxx

Explanation:


User response:


BKMA0809E Severe error when attempting to

retrieve INI data - Section: xxxx Token :

yyyy

Explanation:

An unrecoverable error occurred while attempting to

retrieve required information from the INI member of

parmlib.

User response:

Processing terminates. Fix the problem in member INI

of parmlib and retry. If unable to determine the reason

for the failure, Contact Technical Support. Have

available the listing that contains this message and the

parmlib member.

BKMA0810W INI options missing or invalid:

retrieve INI DATA - Section: xxx Token :

yyy

Explanation:

The INI data for section xxx token yyy is invalid.

User response:

Processing continues using defaults. If defaults are not

acceptable, correct the INI data and resubmit the job.

BKMA0811W Errors while deleting event from IDS.

Explanation:

Errors occurred while trying to delete records for the

verify phase of a VEREXE command.

User response:

Processing continues. There may be unnecessary

records left in the IDS.

BKMA0901E Error calling BKM01VV1 tttttttt Function:


Explanation:




User response:



controls execution.

BKMA0902W INI token value invalid - Using

default: xxxx

Explanation:

In section ABARS_RC_OVERRIDES, token xxxx has an

invalid value.

User response:

Processing continues however the return code may not

be what was expected. To eliminate these messages,

correct the INI token value.

BKMA0903I INI return code override applied for:

xxxxx

Explanation:

Message ID xxxxx was found in section

ABARS_RC_OVERRIDE of the INI. The return code

specified there will be applied.

User response:

None. Processing continues.

BKMA0904E Activity log is not for an ABACKUP

Explanation:

An attempt was made to load an activity log that was

not for an ABACKUP. This function is valid only for

ABACKUP logs.

User response:

Processing terminates. Specify a valid activity log and

rerun the job.


Explanation:


User response:



BKMA0906E Invalid activity log: msgid data

Explanation:

Found unexpected data in the activity log.

User response:

This is most likely an internal error. Contact Technical

Support. Have available the listing that contains this

message and the parmlib member that controls

execution.

BKMA0907E Attempt was made to write a duplicate

xxx to the IDS

Explanation:

Attempted to write a record of type xxx to the IDS that

was already there.

User response:

BKMA0808E • BKMA0907E IBM Confidential


The most likely causes are a corrupted database or an

internal error. Contact Technical Support. Have available

the listing that contains this message and the parmlib

member that controls execution.

BKMA0908E CFILE record already in IDS

Explanation:

When attempting to add a ″CFILE″ record to the IDS, a

record with the same key was found to already exist.

The probable reasons are either the wrong IDS was

specified in the JCL or EXPIREBV was done and the

events for HSM are still recorded in the IDS.

User response:

If the wrong IDS was specified, correct the JCL and

rerun the job or load the activity log. If the problem is

due to EXPIREBV, delete the aggregate from the IDS

and either rerun the job or load the activity log.

BKMA0909E Attempt to correct duplicate CFILE

failed

Explanation:

After finding a duplicate ″CFILE″ record in the IDS, an

attempt was made to correct the error. The attempt

failed.

User response:

If the wrong IDS was specified, correct the JCL and

rerun the job or Load the activity log. If the problem is

due to EXPIREBV, delete the aggregate from the IDS

and either rerun the job or load the activity log.

BKMA0911I Sequential write failed, switching to

standard write

Explanation:

When inserting records into the IDS sequentially the

action failed due to invalid data order.

User response:

Program will switch modes from sequential write mode

to standard write mode and continue processing.

However as part of this message the previous data set

key and the current data set key will be displayed and

should be sent to Technical Support.

BKMA0912E Rewrite from sequential to standard

failed

Explanation:

The switch was made from sequential write to standard

write and the standard write failed.

User response:

Contact Technical Support.

BKMA0913E Sequential write error

Explanation:

A sequential write was issued when writing data set

records to the IDS with a VSWRITE error other than

RC=8 and RSNCODE=12.

User response:


BKMA0914E Activity log truncated

Explanation:

Some of the end of the Activity Log is missing.

User response:

Repair the Activity Log and rerun the LOADACT. If the

problem persists, contact Technical Support and give

them this message and the activity log.

BKMA0915E Storage obtain error : return code = xx

ID=x

Explanation:

Error obtaining storage necessary for event.

User response:

Processing terminates. Save error message and


BKMA0917W Error converting log date: JDATE

found in log - jdate

Explanation:

Error converting the Julian date (jdate) to Gregorian

date.

User response:

Processing continues. Log date is set to job start date.

BKMA0996I aggname: number of data sets

processed = nnnnnnnn

Explanation:

The number of data sets processed for aggname.

User response:

None.


Explanation:




User response:



controls execution. .



BKMA10002E SKIPDS allocation failed for: xxxxxx

Explanation:

Dynamic allocation failed for data set xxxxxx the reason

specified.

User response:

Fix the problem, if it is a customer issue, and retry the

job. If it is not or the problem persists, contact Technical

Support.

BKMA10003E SKIPDS unallocation failed for:

xxxxxx

Explanation:

Dynamic unallocation failed for data set xxxxxx the

reason specified.

User response:



Support.

BKMA10007E CONFLI allocation failed for: xxxxxx

Explanation:


specified.

User response:



Support.

BKMA10008E CONFLI unallocation failed for:

xxxxxx

Explanation:

Dynamic unallocation failed for data set xxxxxx the

reason specified.

User response:



Support.

BKMA1001E Duplicate event record in IDS

Explanation:

This event is already in the IDS. Most probable cause is

a corrupted IDS.

User response:


BKMA10101E Error calling BKMA1VV1 ttttttt

function: function R15=nnnn

R0=nnnnnnnn ID=lllll

Explanation:




User response:



controls execution of BKM.

BKMA10201I Invalid INCLUDE or EXCLUDE

parameter.

Explanation:

A DSN or mask in the INCLUDE(...) parameter is

invalid. Check length or for invalid masking characters.

User response:

Fix the error and retry the job.

BKMA10202I xxxxx : not selected by INCLUDE(...)

Explanation:

DSN xxxxx was backed up by the event being

recovered but did not match any data set or mask in the

INCLUDE(...) parameter.

User response:

None.

BKMA10203I xxxxxx : excluded by EXCLUDE(...)

Explanation:

DSN xxxxxx was backed up by the event being

recovered but was excluded from recovery by a data set

name or mask in the EXCLUDE(...) parameter.

User response:

None.

BKMA10204I xxxxxx : file type not one of selected

types

Explanation:


recovered but was excluded from recovery because it’s

file type (Prim, ML1, ML2, or UTAPE) was not one of

the ones specified in the control statement.

User response:

None.

BKMA10205I xxxxxx : not an active member of a

GDG base

Explanation:


recovered but was not a active member of the GDG

base when the most recent, incremental version being

recovered was backed up.

User response:

None.

BKMA10002E • BKMA10205I IBM Confidential


BKMA10206W No GDG base record found in IDS

for: xxxxx

Explanation:


recovered but no GDGB record was found in the IDS.

The GDGB record is used to recover the GDS’s in the

correct order.

User response:

The GDS is included in the recovery, but the GDG

should be checked after the recovery to insure that it is

correct.

BKMA10207W Error calling BKMA1VV1 ttttttt

Function: function R15=nnnn


Explanation:




User response:




BKMA10208W Unknown file type found in IDS :

xxxxx

Explanation:

File type xxxxx was the file type found in IDS for the

following ″NOT SELECTED″ data set. This most likely

due to corrupted data.

User response:

Contact Technical Support for help in resolving this

error.

BKMA10209I xxxxxx : not selected -

GDGGEN0ONLY was specified

Explanation:

DSN xxxxxx was backed up but was not selected for

recover because it was not the +0 generation when this

GDG family was backed up.

User response:

None.

BKMA10302E (Un)allocation failed for: xxxxx

Explanation:


specified.

User response:



Support.

BKMA10304E Open failed for: xxxxx

Explanation:

An open error occurred for the file indicated.

User response:


BKMA10305I No data sets recovered from this

cycle/gen

Explanation:

After processing all INCLUDE / EXCLUDE parameters

all data sets backed up by this event were excluded

from recovery.

User response:

If this is not what was intended, correct the control

statements and retry the job.

BKMA10306E Odd number of levels specified for

RECOVERNEWNAMELEVEL.

Explanation:

The RECOVERNEWNAMELEVEL parameter was

incorrectly coded The OLDprefix NEWprefix must be in

even numbered pairs.

User response:

Correct the control statements and retry the job.

BKMA10307E More than 30 levels specified for


Explanation:

ABARS allows only 30 RECOVERNEWNAMELEVEL

pairs.

User response:


BKMA10308E Duplicate old hlqs listed in

RECOVERNEWNAMELEVEL

Explanation:

An old high level qualifier may be listed in the

RECOVERNEWNAMELEVEL only once.

User response:


BKMA1030E RECOVERNEWNAMEALL would result

in an attempt to rename more than one

data set to the same name.

Explanation:

This usually occurs when a recover is being done for

data sets with multiple high level qualifiers that have

common lower level qualifiers.

User response:

Correct the error and retry the job.

BKMA10206W • BKMA1030EIBM Confidential





Explanation:




User response:






yyyy

Explanation:



parmlib.

User response:





parmlib member.

BKMA10501I A non-BKM function found

Explanation:

An ABARS function was determined to be non-BKM

controlled.

User response:

None.

BKMA10502E Allocation failed for DD: SKIPDS

Explanation:

Dynamic allocation of the data set to be used by the

ARCSKEXT failed.

User response:

Processing stops. Fix the problem and retry the job.

BKMA10503E Open error for DD: SKIPDS

Explanation:

Open failed for the data set to be used by the

ARCSKEXT

User response:


BKMA10504W Un-allocation failed for DD: SKIPDS

Explanation:

Dynamic unallocation of the data set to be used by the

ARCSKEXT failed.

User response:

Processing continues. Report the error to Technical

Support.

BKMA10505W Unable to locate related HSM MWE

reason continuing without BKM

tracking

Explanation:

HSM has no or more than one ABRCB for this ASID.

BKM, after several retries, was unable to determine

which MWE was related to the event being processed in

the address space. This is usually due to HSM being to

busy maintain it’s control blocks in a timely manner.

User response:

Processing continues but BKM treats the event as if it is

a ″native″ command and BKM tracking is not done. If

this was a BMR function, the batch job will abend with a

U999 and message BKMA0804E will be issued. The job

may either be rerun or the activity log may be loaded

using the LOADACT command.

BKMA10506E SI027 put error

Explanation:


User response:


BKMA10507E Sub-task event block not found

Explanation:


User response:


BKMA10701E DSN parm not passed

Explanation:

DATASET parm expected and was not passed.

User response:

Pass the DATASET parm and try again. If the problem


BKMA10702E No SPACE format passed

Explanation:

A SPACE parm was expected and was not passed.

User response:

Supply a SPACE parm and try again. If the problem


BKMA10703E SPACE format passed invalid

Explanation:

The SPACE parm passed was invalid.

User response:



Correct the SPACE parm and try again. If the problem


BKMA10704E No backup event records found

Explanation:

While counting the generations of backup event files

none were found in the database.

User response:

Try executing again. If the problem persists, contact

Technical Support.

BKMA10705E Error reading backup event records

Explanation:

While trying to gather backup event data an error

occurred.

User response:


Technical Support.

BKMA10706E No data set detail records found

Explanation:

While searching the data sets for overlaps no data set

detail records (DSND) were found in the database.

User response:


Technical Support.

BKMA10707E Error reading datas et detail records

Explanation:

While trying to read the data set detail records and error

occurred

User response:


Technical Support.

BKMA10708E Invalid data set name passed

Explanation:

A data set name/mask passed to search for contains

invalid masking characters.

User response:


Technical Support.

BKMA10709E Backlevel data set already contains

data

Explanation:

When initializing the backlevel VSAM DSN, data was

found in the data set.

User response:

Delete the backlevel DSN and try again. If the problem


BKMA10801I No overlaps: aggname

Explanation:

No overlaps were found for event name or mask

passed.

User response:

None.

BKMA10802E No EVENT parm passed

Explanation:

An EVENT parm was expected and was not passed.

User response:

Pass an EVENT parm and try executing again. If the

problem persists contact Technical Support.

BKMA10803E No GEN parm passed

Explanation:

A GEN parm was expected and was not passed.

User response:

Pass a GEN parm and try executing again. If the



Explanation:

A SPACE parm was expected and was not passed.

User response:




Explanation:

SPACE parm passed was invalid.

User response:



BKMA10806E No backup events records found

Explanation:

When reading the database for backup event records

none were found.

User response:

Try again. If the problem persists, contact Technical

Support.

BKMA10807E Error reading backup event records

Explanation:


an error occurred

User response:


Support.



BKMA10808E No data set detail records found

Explanation:



User response:


Technical Support.

BKMA10809E Error reading data set detail records

Explanation:

While trying to read the data set detail records an error

occurred.

User response:


Technical Support.

BKMA10810E Invalid data set name passed

Explanation:


invalid masking characters

User response:


Technical Support.

BKMA10811E Bad FROM generation passed

Explanation:

A generation number from 0 to -9999 was not passed

User response:

Pass a generation number between 0 and -9999. If the

problem persists, contact Technical Support.

BKMA10812E Bad TO generation passed

Explanation:

A generation number from 0 to -9999 was not passed.

User response:



BKMA10813I Logical aggregate not found

Explanation:

A logical aggregate name was passed but does not

exist.

User response:

Enter a valid logical aggregate name and try again. If

the problem persists contact Technical Support.

BKMA10814W Current aggregate limit = 75

Explanation:

Up to 75 Aggregates from a logical aggregate are

reported. If a logical aggregate contains more than 75

aggregates then only the first 75 are reported.

User response:

None.

BKMA10815E Backlevel data set already contains

data

Explanation:

When initializing the backlevel VSAM DSN, data was

found in the data set.

User response:



BKMA10901E Syntax errors in command

Explanation:

The SYSIN command listed above contains syntax

errors. See messages prior to this one. Valid commands

are ABACKUP and ARECOVER

User response:

Correct the syntax errors and resubmit the job.

BKMA10902E Required keyword missing -

xxxxxxxxxxx

Explanation:

The SYSIN command listed above is missing required

keywords.

User response:


BKMA11001E (Un) allocation failed: xxxxx

Explanation:


User response:



Support.

BKMA11002E Open error: xxxxx

Explanation:


User response:





Explanation:


User response:



BKMA11101E Un-balanced /* - */ pair.

Explanation:

When parsing the selection data set, a syntactical error

was found.

User response:


BKMA11102E Un-balanced parenthesis.

Explanation:


was found.

User response:


BKMA11103E Empty selection data set(s).

Explanation:

When parsing the selection data set, it was found that

the selection data sets were empty.

User response:

This could be due to misplaced comment characters.



Explanation:


User response:


BKMA11105E Error calling xxxxxxxx R15=nnnn

Explanation:




User response:




BKMA11106E Unexpected end of file processing

compressed selection data set

Explanation:

An internal processing error has occurred.

User response:




Explanation:

An internal processing error as occurred.

User response:



Explanation:


User response:


BKMA11202E Error deleting old SDSL record

Explanation:

An error occurred when attempting to delete an old

SDSL record in preparation for writing a new one.

User response:

If the problem persists and the cause cannot be

determined, contact Technical Support.

BKMA11203E Duplicate record zipping activity log

Explanation:

This is probably due to IDS contamination.

User response:


BKMA11301I Full rename mode: EXECUTE | FILE

Explanation:

Display of the full rename mode requested. FILE

specifies that a file of ALTER/NEWNAME IDCAMS

statements is to be written. EXECUTE specifies that a

file is to be created and that IDCAMS is to be

dynamically invoked.

User response:

None.

BKMA11302I Full rename output dsname: dsname

Explanation:

dsname is the name of the data set into which the

ALTER/NEWNAME IDCAMS statements are written.

User response:

None.

BKMA11003E • BKMA11302IIBM Confidential


BKMA11303I Rename data set disposition :

DELETE | KEEP

Explanation:

Disposition of the output data set.

User response:

None.

BKMA11304E Open error: ddname

Explanation:


User response:

Determine the reason for the open failure and retry the

job.

BKMA11305E Too many old/new mask pairs in

FULLRENAME PARM

Explanation:

More than 30 old/new mask pairs were specified in the

FULLRENAMEMASKS parameter.

User response:

Fix the error and rerun the job.

BKMA11306E Odd number old/new masks in

FULLRENAME PARM

Explanation:

Old/new masks in the FULLRENAMEMASKS parameter

must be entered in pairs.

User response:


BKMA11307E Duplicate old masks in

FULLRENAME PARM

Explanation:

An ″Old″ mask occurred more than once in the old/new

mask pairs in the FULLRENAMEMASKS parameter.

User response:


BKMA11308E (Un)allocation failed: xxxx

Explanation:


User response:



Support.

BKMA11310E IDCAMS ended with non-zero return

code

Explanation:

During full rename processing, IDCAMS returned a

non-zero return code.

User response:

Check the IDCAMS output for the problem.

BKMA11312E Syntax errors in IDCAMS ALTER

commands

Explanation:

At least one syntax error was generated when building

the control statements for full rename. The IDCAMS

alters were not done.

User response:

This error is usually caused when trying to add or

remove nodes during rename. Check old/new mask

pairs for errors. Rename was not attempted.

BKMA1313EE New name mask is ambiguous

Explanation:

The use of wildcards in the new name mask is more

limited than in the old name mask. Only one ″**″

wildcard may be used. Partial qualifiers such as ″.*A*.″

or ″.*ABC.″ may not be used.

User response:

Fix the errors and retry the job.

BKMA11314E IDCAMS rename not done - errors or

warnings found

Explanation:

The mode was ″EXEC″ but problems were encountered

while resolving the new names.

User response:

Check the messages, fix the problems and retry. If the

file disposition was ″KEEP″, you may edit the file,

correct any problems, then use the file for input to

IDCAMS.

BKMA11315E CSI routine failed : xxxxx

Explanation:

CSI routine failed for reason xxxxx.

User response:


BKMA11316E Unable to find GDG attributes : xxxxx

Explanation:

Full rename was unable to find the GDG base attributes

it needs to define a new GDG base.

User response:

BKMA11303I • BKMA11316E IBM Confidential


If unable to determine the reason for this failure, contact

Technical Support.




Explanation:




User response:




BKMA11318E xxxx : data set already cataloged on

system

Explanation:

A new GDG base name resolved to the name of a data

set that is already cataloged on this system.

User response:

GDG is not renamed. Processing continues.


retrieve INI data - Section: xxx Token :

yyy

Explanation:


User response:





yyyy

Explanation:



parmlib.

User response:





parmlib member.

BKMA11401E Error returned for BKMA1FD0 - xxxx

Explanation:

Error occurred processing old/new filters.

User response:


BKMA11402E New name mask resulted in duplicate

data set names :xxx

Explanation:

New name mask would cause more than one data set

to be renamed to the same name.

User response:


BKMA11403E Rename error: data set is a GDG

generation

Explanation:

An attempt was made to rename an active member of a

generation data group and the INI token

RENAME_GDGS was set to N.

User response:

Filter out this data set and set the INI token to Y and

retry. If the file was kept, it may be used for input to

IDCAMS. No ALTER statements were written for this

data set.




Explanation:




User response:




BKMA11501E Rename mask is invalid: xxx

Explanation:

The new name mask indicated by xxx is invalid.

User response:


BKMA11599E Rename mask is invalid: xxx

Explanation:

The new name mask indicated by xxx is invalid.

User response:


BKMA11601E Aggregate name not a node of

dsname

Explanation:

At least one node of the full rename output data set

must be the aggregate name.

User response:



Change the data set name to include the aggregate

name and rerun the job. You may use the variable

&AGGNAME and BKM will insert the aggregate name

into the dsname.

BKMA1602E INI token OUTPUTRENAMEDSN is

invalid

Explanation:

The INI value does not adhere to coding rules.

User response:

Correct the error and try again.

BKMA12715E Message queue open failed.

Explanation:

Correctable error.

User response:

See other error messages.

BKMA12031E DAD command request not

recognized

Explanation:

An internal error has occurred.

User response:


BKMA12080E Error fetching //SISPARM info,

R15=xx

Explanation:

During the first phase of DADSMFTK startup,

DADSMFTK was unable to process the information from

the //SISPARM JCL statement.

User response:


BKMA12090E Error fetching ″LOG″ token. R15=xx

Explanation:


DADSMFTK was unable to process the LOG token from


User response:

Determine the error in the ″LOG″ token, and restart

DADSMFTK.

BKMA12091E Error with value of ″LOG″ token.

Explanation:


DADSMFTK processed the LOG token from the

//SISPARM JCL statement, but found a error in the

value.

User response:


DADSMFTK.

BKMA12092E Error with len value of ″LOG″ token.

Explanation:




value. It should be a DSN, which has a maximum length

of 44 characters.

User response:


DADSMFTK.

BKMA12093E Cannot determine this DADSMFTKs

SYSLOG

Explanation:



//SISPARM JCL statement, but was unable to determine

the name of its LOG DSN.

User response:


DADSMFTK.

BKMA12096E Allocation of //DADLOG failed:

R15=xx,INFO=ddddddddd

Explanation:



//SISPARM JCL statement, but MVS™ declared the DSN

invalid.

User response:


DADSMFTK.

BKMA12097E LOG DSN value is null

Explanation:

During DADSMFTK startup, DADSMFTK determined

that the LOG DSN was ″null″ meaning that it was

invalid during INI value processing, or, was never

specified in the INI values. This value is described in

the ″DADSMFTK_OPTIONS″ section of the //SISPARM

member.

User response:


DADSMFTK.

BKMA12115W U83 exit not active for SYSID.

Explanation:

DADSMFTK is not running or a problem was

encountered installing the U83 exit.

User response:

BKMA1602E • BKMA12115W IBM Confidential


The application may be missing information from this

SYSID. Whether this is critical is up to the application

analyst.

BKMA12116W DAD database update task not

active for SYSID.

Explanation:

The task which writes SMF records to the database is

not active for this SYSID.

User response:



analyst. Unless the update task was terminated on

purpose, check the console log for update task error

messages. If the update task was stopped because of

errors, the message ASP01010E abnormal termination

of DAD9254S will appear in the log along with other

messages identifying the precise reason for the

abnormal termination.

BKMA12117W DAD database update task is doing

no work for SYSID

Explanation:


active but is not writing records to the database.

User response:

If the image is not frozen (other jobs are processing),

check for other messages from the read task

(DAD9254S) that might indicate the nature of the

problem. APPLEND will continue processing, but the

application may be missing information from this SYSID.

Whether this is critical is up to the application analyst.

BKMA12118W No response from DAD database

update task for SYSID

Explanation:

The task which writes SMF records to the database

does not respond when told to flush SMF records.

User response:


check for other messages from the update task

(DAD9254S) that might indicate the nature of the




BKMA12119E Application not found in DAD

database.

Explanation:

An application master record for the application named

in the APPLEND parm cannot be found.

User response:

Check that the applname in the parm is correct or that

the application has indeed been created.

BKMA12120I APPLEND started for application.

Explanation:

Informational only.

User response:

None.

BKMA12121I Cycle number increased for

application.

Explanation:

The DAD cycle number for this cycle’s worth of SMF

records has been increased by one.

User response:

None required.

BKMA12122I Buffer flush requested for application.

Explanation:

A signal has been sent to each image requesting that

the SMF record buffers be flushed.

User response:

None required.

BKMA12123I Buffer flush acknowledge for

application.

Explanation:

Images acknowledge request for buffer flush.

User response:

None required.

BKMA12124I Buffer flush satisfied for application.

Explanation:

Buffers successfully flushed.

User response:

None required.

BKMA12128E Free of ddname DADMSGQ failed

Explanation:

SVC99 failure.

User response:

Note SVC99 failure code. If not solvable contact

Technical Support.

BKMA12129E DADSMFTK not active

Explanation:


User response:

DADSMFTK must be active on the image running the

DADFLUSH step. Check for other log messages.



BKMA12130E NAMETOKEN fetch failed.

Explanation:

Fetch of name/token pair failed.

User response:


BKMA12131E Failure allocating ddname DADMSGQ

to data set.

Explanation:

SVC99 FAILURE.

User response:

See SVC99 reason code. Problem is likely user

solvable.

BKMA12132E DAD msg queue not formatted

correctly. Expected DADMSG in 1st 16

slots.

Explanation:

Message queue not formatted.

User response:

Check that JCL member DADMQBLD has been run.

BKMA12300E Exit area exists..must unload first

Explanation:

Correctable error.

User response:

Stop the DADSMFTK task using STOPALL and restart

using AUTOSTART.

BKMA12301E Cannot open EXITLIB

Explanation:

Correctable error.

User response:

Make sure the DSN is correct for each load library in

the INI parmlib member.

BKMA12302E X-CSA storage not available

Explanation:

Correctable error.

User response:

Increase the region size of the DADSMFTK job.

BKMA12303I X-CSA located at: nnnnnnnn length:

nnnnnnnn

Explanation:

Informational message.

User response:

None.

BKMA12304E Unable to load primary exit. Load

RC=nnn reason=xx

Explanation:

U83 exit load error.

User response:

Pease report this message with the error text issued to

Technical Support.

BKMA12305E Name token creation failed. IEANTCR

RC=nn

Explanation:

Internal error.

User response:

Please report this message with the error text issued to

Technical Support.

BKMA12306E X-CSA built and identified

Explanation:


User response:

None.

BKMA12307E Unable to load secondary exit. Load

RC=nn

Explanation:


User response:


Technical Support.

BKMA12308I Secondary exit loaded successfully

Explanation:


User response:

None.

BKMA12309E Exit area does not exist

Explanation:


User response:


Technical Support.

BKMA12310E Unable to free X-CSA. Freemain

RC=nn

Explanation:

Internal error.

User response:


Technical Support.



BKMA12311I Exit area removed

Explanation:


User response:

None.

BKMA12312E Cannot remove exit with dataspace

active

Explanation:

Correctable error.

User response:

Stop the DADSMFTK task using the STOPALL

command.

BKMA12313E Cannot turn on exit without

dataspace active

Explanation:

Correctable error.

User response:


command and restart using the AUTOSTART command.

BKMA12314E Secondary exit already active

Explanation:

Correctable error.

User response:



BKMA12315I Secondary exit active

Explanation:


User response:

None.

BKMA12316E Secondary exit not active

Explanation:

Correctable error.

User response:



BKMA12317I Secondary exit deactivated

Explanation:


User response:

None.

BKMA12318I Secondary exit data space VSAM

subtask active exists running

Explanation:


User response:

None.

BKMA12319I Cannot load new secondary exit while

existing exit is turned on

Explanation:

Correctable error.

User response:



BKMA12320I Secondary exit reloaded successfully

Explanation:


User response:

None.

BKMA12321E SMF xxxxxxxxxxx complete for:

xxxxxxxxxxxxxxxx

Explanation:


User response:

None.

BKMA12322E SMF dynamic exit facility xxxxxx

RC=nn reason=xxxx

Explanation:

Internal error.

User response:


Technical Support.

BKMA12326E Cannot xxxxxx exit; no exits defined

to MVS

Explanation:

Correctable error.

User response:

See other messages that may explain the reason for

this error.

BKMA12327I There were xxxx exits deleted than

installed

Explanation:

Correctable error.

User response:

BKMA12311I • BKMA12327IIBM Confidential



this error.

BKMA12338E Token ″LOAD ″ DSN xxxxxxxxxxxx

request failed; r15=nn SVC 99 data:

xxxxxxxx

Explanation:

Internal error.

User response:


Technical Support.

BKMA12339E ddname xxxxxxxxxxxxxxx request

failed; r15=nn SVC 99 data: xxxxxxxx

Explanation:

Internal error.

User response:


Technical Support.

BKMA12342E DADESTAE load module query failed.

RC=nn

Explanation:

Internal error.

User response:


Technical Support.

BKMA12343E Unable to load DADESATE/secondary exit. Load RC=nnn

reason=nn

Explanation:

Internal error.

User response:


Technical Support.

BKMA12344E Error on initial open of DAD

database

Explanation:

Correctable error.

User response:


this error.

BKMA12400E Unable to make non swapable.

SYSEVENT RC=nn

Explanation:

Internal error.

User response:


Technical Support.

BKMA12401E Unable to xxxxxxx dataspace.

DSPSERV RC=xx

Explanation:

Correctable error.

User response:

See the IBM MVS Auth Assm Services Reference

ALE-DYN for a discussion of DSPSERV errors.

BKMA12402E Unable to xxxxxxx ALET. ALESERV

RC=xx

Explanation:

Correctable error.

User response:

See theIBM MVS Auth Assm Services Reference

ALE-DYN for a discussion of ALET errors.

BKMA12403E Dataspace BUF count origin size

created z,zzz,zzz xxxxxxxx z,zzz,zzzk

Explanation:


User response:

None.

BKMA12404I Data space removed

Explanation:


User response:

None.

BKMA12405E Must install exit before manipulating

dataspace

Explanation:

Correctable error.

User response:

Wrong sequence of operator commands. The exit must

be installed first.

BKMA12406E Dataspace already exists

Explanation:

Correctable error.

User response:

You must delete the current dataspace before you can

recreate it.



BKMA12407E Data space does not exist

Explanation:


User response:

None.

BKMA12408E Cannot delete data space with exit

turned on

Explanation:

Correctable error.

User response:

If you want to delete the dataspace, the U83 exit must

be turned off.

BKMA12409I Buffer value not valid, using default

Explanation:


User response:

None.

BKMA12410I Buffer value excessive. Using 32MB

of buffers

Explanation:


User response:

None.

BKMA12411I Internal dataspace ID is bad; resetting

internal ID

Explanation:


User response:

None.

BKMA12520E Read DAD database subtask exists.

Explanation:

Correctable error.

User response:



BKMA12521E Read DAD database subtask failed to

start. RC=nn

Explanation:

Internal error.

User response:


Technical Support.

BKMA12522I Read DAD database subtask started;

using xxxxxxxxxxxxxxxxxxx

Explanation:


User response:

None.

BKMA12523E Must load exit area before starting

subtask

Explanation:

Correctable error.

User response:



BKMA12524E Internal dataspace ID is bad. Need

valid ID.

Explanation:

Internal error.

User response:


Technical Support.

BKMA12525E Must create dataspace before

starting subtask

Explanation:

Correctable error.

User response:



BKMA12530E Read DAD database subtask does

not exist.

Explanation:

Unexpected event but shut down show proceed

normally.

User response:

None.

BKMA12531E Read DAD database subtask not

responding.

Explanation:

Unexpected event but shut down should proceed

normally.

User response:

None.



BKMA12532I Read DAD database subtask stopped.

Explanation:


User response:

None.

BKMA12533E Read DAD database subtask

destroyed.

Explanation:

No response from task, so the task was removed.

User response:

None.

BKMA12539E DAD DSN value is null

Explanation:

No value for DAD database DSN.

User response:

Update INI with valid DAD database DSN.

BKMA12540E Update DAD database subtask

exists.

Explanation:

Correctable error.

User response:



BKMA12541E Update DAD database subtask failed

to start. RC=nn

Explanation:

Internal error.

User response:


Technical Support.

BKMA12542I Update DAD database subtask

started; using xxxxxxxxxxxxxxxxxxx

Explanation:


User response:

None.

BKMA12543E Must load exit area before starting

subtask

Explanation:

Correctable error.

User response:

Stop the DADSMFTK task using STOPALL command

and restart using AUTOSTART command.

BKMA12544E Internal dataspace ID is bad. Need

valid ID.

Explanation:

Internal error.

User response:


Technical Support.

BKMA12545E Must create dataspace before

starting subtask

Explanation:

Correctable error.

User response:



BKMA12550E Update DAD database subtask does

not exist.

Explanation:


normally.

User response:

None.

BKMA12551E Update DAD database subtask not

responding.

Explanation:


normally.

User response:

None.

BKMA12552I Update DAD database subtask

stopped.

Explanation:


User response:

None.

BKMA12553E Update DAD database subtask

destroyed.

Explanation:

No response from task, so task removed.

User response:

None.



BKMA12560E DAD monitor command subtask not

responding.

Explanation:


normally.

User response:

None.

BKMA12561I DAD monitor command subtask

stopped.

Explanation:


User response:

None.

BKMA12562E DAD monitor command subtask

destroyed.

Explanation:


User response:

None.


exists.

Explanation:

Correctable error.

User response:




failed to start. RC=nn

Explanation:

Internal error.

User response:


Technical Support.

BKMA12565E Overflow export subtask exists.

Explanation:

Correctable error.

User response:



BKMA12566E Overflow export subtask not

responding.

Explanation:


normally.

User response:

None.

BKMA12567I Overflow export subtask stopped.

Explanation:


User response:

None.

BKM12568E Overflow export subtask destroyed.

Explanation:


User response:

None.

BKMA12569E Overflow export subtask does not

exist.

Explanation:


normally.

User response:

None.

BKMA12570E Overflow export subtask failed to

start. RC=nn

Explanation:

Internal error.

User response:


Technical Support.

BKMA12571E Overflow import subtask exists.

Explanation:

Correctable error.

User response:



BKMA12572E Overflow import subtask not

responding.

Explanation:


normally.

User response:

None.



BKMA12573I Overflow import subtask stopped.

Explanation:


User response:

None.

BKMA12574E Overflow import subtask destroyed.

Explanation:


User response:

None.

BKMA12575E Overflow import subtask does not

exist.

Explanation:


normally.

User response:

None.

BKMA12576E Overflow import subtask failed to

start. RC=nn

Explanation:

Internal error.

User response:


Technical Support.

BKMA12577I Overflow import subtask started.

Explanation:


User response:

None.

BKMA12578I Overflow export subtask started.

Explanation:


User response:

None required.

BKMA12579I DAD monitor command subtask

started.

Explanation:


User response:

None required.

BKMA12600E Shut down complete

Explanation:


User response:

None required.

BKMA12601E Errors occurred during shut down.

Explanation:

Unexpected events caused shut down errors.

User response:

See other messages.

BKMA12602E Autostart complete

Explanation:


User response:

None required.

BKMA12603E Errors occurred during autostart.

Explanation:

Unexpected events caused autostart to fail.

User response:

See other messages.

BKMA12610I Error xxxxxxxxxxxx info from

//SISPARM. R15=nnnn

Explanation:

Correctable error.

User response:

Incorrect or missing data in INI. Correct errors and

restart the DADSMFTK task.

BKMA12612E Overflow dsn not found for SYSID

Explanation:

Correctable error.

User response:

Incorrect or missing data in INI. Each SYSID must have

its own overflow data set.

BKMA12613E Too many overflow file allocation

parms. Size limit is 123 bytes.

Explanation:

Correctable error.

User response:

Reduce the allocation parms in the

OVERFLOW_PARMS token.



BKMA12614E Substitution error on INI variables.

Output less than 92 bytes.

Explanation:

Internal error.

User response:


Technical Support.

BKMA12615E Syntax error for OVERFLOW_DSN

parm xxxxxxxxxxxxxxxx

Explanation:

Correctable error.

User response:

Correct errors in OVERFLOW_PARMS.

BKMA12701E Unexpected return code (nn) from

xxx IEANT xx

Explanation:

Internal error.

User response:


Technical Support.

BKMA12704E QEDIT nonzero return code. xxxxxxxx

RC=nn

Explanation:

Internal error.

User response:


Technical Support.

BKMA12705E Cannot get message system lock

Explanation:

Internal error.

User response:


Technical Support.

BKMA12706E Cannot execute unauthorized

Explanation:

Correctable error.

User response:

The DADSMFTK module must be in an authorized

library.

BKMA12707E Another DADSMFTK is executing. It

was started yyyy/mm/dd at hh:ss:mm

Explanation:

Correctable error.

User response:

Only one DADSMFTK task can run on an image.

BKMA12712E DADSMFTK: build &SYSDATC

&SYSTIME

Explanation:


User response:

None required.

BKMA12715E Message queue open failed.

Explanation:

Correctable error.

User response:


BKMA12715E Message queue allocate failed.

Explanation:

Correctable error.

User response:

See other allocate error messages.

BKMA12718E All DAD slots filled in message

queue

Explanation:

Correctable error.

User response:

The DADSMFTK task can be started on a maximum of

16 images. Make sure that SYSIDS no longer in use

are deleted from the message queue dataset.

BKMA12719E Message queue data set not

formatted

Explanation:

Correctable error.

User response:

The message queue setup job DEF#MSGQ must run

successfully before the DADSMFTK job can be started.

BKMA12720E Message queue deallocate failed.

Explanation:

Correctable error.

User response:


BKMA12721E Overflow allocate failed.

Explanation:

Correctable error.

User response:




BKMA12722E Overflow deallocate failed.

Explanation:

Correctable error.

User response:


BKMA12725E xxxxxxxxxxxxxxxxxxxxxxxxx

xxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxx

Explanation:

Correctable error.

User response:

This message gives the details of an allocate error.

Correct the error and restart DAD.

BKMA12727E Overflow open failed.

Explanation:

Correctable error.

User response:


BKMA12728E Startup failed due to parmlib INI

error

Explanation:

Internal error.

User response:


Technical Support.

BKMA12729E INI token not found. Token

=xxxxxxxxxxxxxxxxxxxx

Explanation:

Correctable error.

User response:

Review INI. The token name may have been changed

or a line may have been deleted.

BKMA12730E INI fetch of token failed RC= nnn

Token = xxxxxxxxxxxxxxxxx

Explanation:

Correctable error.

User response:

Review INI for token and token value syntax errors.

BKMA12731E Cannot find matching SYSID for

token:xxxxxxxxxxxxxxxxxxxx

Explanation:

Correctable error.

User response:

Review INI. The correct values are listed by SYSID.

BKMA12732E Token syntax error token =

xxxxxxxxxxxxxxxxx

Explanation:

Correctable error.

User response:

Review INI. The token value is not in the format

expected.

BKMA12733E dsn longer than 44 characters token

= xxxxxxxxxxxxxxxx

Explanation:

Correctable error.

User response:

Review INI. The token value should be a dsn.

BKMA12734E Log dsn not valid

Explanation:

Correctable error.

User response:

Review INI. The value for the log token must be a valid

dsn.

BKMA12736E Message log allocate failed.

Explanation:

Correctable error.

User response:


BKMA12737E Message log deallocate failed.

Explanation:

Correctable error.

User response:


BKMA12901E Unexpected return code (nn) from

xxx IEANT xx

Explanation:

Internal error.

User response:


Technical Support.

BKMA12904E Abnormal termination of DADDBUPD

Explanation:

DAD update task did not shut down normally.

User response:

This is critical error. Other error messages should give

more details of the problem. Please report these

messages with the text issued to Technical Support.




Explanation:


User response:



BKMA13002E (Un)allocation failed - xxxxx

Explanation:

Dynamic allocation failed for the reason specified.

User response:



Support.

BKMA13003E Error calling nnnnnnnn RC=rrrrr

Explanation:


nnnnnnnn is the program name. Processing terminates.

User response:



controls execution.


Explanation:


User response:


BKMA13006W Allocation failed - retry: dsn

Explanation:

Allocation of SDS data set failed. Will wait for a while

and retry.

User response:

None.

BKMA13009W PDS member in use - retry: dsn

Explanation:

Attempt to obtain exclusive use of the PDS member for

update failed. Wait for a while and retry.

User response:

None.

BKMA13010E Unable to get exclusive control of

the SDS: dsn

Explanation:

Attempt to obtain exclusive use of the PDS to open for

update failed after repeated retries.

User response:


job. If it is not, or the problem persists, call Technical

Support.

BKMA13012E SDSB records not found in IDS

Explanation:

While attempting to restore the selection data set to it’s

original contents, the original selection data set that had

been saved into the IDS could not be found. The SDS

must be restored to its original status manually.

User response:

Processing terminates. Fix the SDS and retry the

backup. If assistance is needed, call Technical Support.


Explanation:


User response:




Explanation:


User response:



Support.


Explanation:


User response:


BKMA1306W SDS allocation failed - retry

Explanation:

Allocation of SDS failed, will wait 1 minute and retry.

User response:

Free the selection data set.

BKMA13201E Unexpected return code nnn from

uuu IEANTPP

Explanation:

During any phase of processing, the MVS Name Token

processing modules returned a code of nnn. The token

being manipulated is for the uuu phase (either CSA or

HAT processes). The specific IEANT module reporting is

pp which would be IEANTRT, IEANTDL, or IEANTCR.

User response:

Report this error to Technical Support.



BKMA13202E Allocate of overflow data set failed

Explanation:

The allocation of the overflow data set failed.

User response:

Look for other messages that will give details about the

the allocation failure.

BKMA13203E Open of overflow data set failed.

Explanation:

The open of the overflow data set failed.

User response:

Look for MVS system messages that will give details

about the open failure. If the cause still cannot be

determined, report this error to Technical Support.

BKMA13204W Overflow dataset is not available

Explanation:

The overflow dataset is in use by the import task.

User response:

None required.

BKMA13205E Deallocate of overflow data set

failed.

Explanation:

The deallocation of the overflow data set failed.

User response:


the deallocation failure. The DAD shutdown will

continue.

BKMA13206W Overflow dataset is full. SMF data

may be lost.

Explanation:

Since the overflow data set is full, SMF data that cannot

be added to the dataspace buffers will be lost.

User response:

None required.

BKMA13207E DAD status update failed.

Explanation:

An update to the message queue data set failed.

User response:



xxxxxxxxxxxxxxxxxxxxxxxxxxx xxxx

Explanation:

Allocate and deallocate messages.

User response:

These messages should give details about the failure.

BKMA13209I Waiting for overflow

Explanation:

Module is trying to get access to the overflow data set.

User response:

None required.

BKMA13301E Unexpected return code (nnn) from

uuu IEANTPP

Explanation:






User response:


BKMA13302E Allocate of overflow data set failed

Explanation:


User response:


the allocation failure.

BKMA13303E Open of overflow data set failed.

Explanation:


User response:




BKMA13305E Deallocate of overflow dataset failed.

Explanation:


User response:


the deallocation failure. The DAD shutdown will

continue.

BKMA13307E Output open of overflow data set

failed.

Explanation:

All the overflow records have been reloaded to the

buffers, but an open for output needs to be done to

empty the overflow data set.

User response:






BKMA13308E Overflow export stop failed.

Explanation:

When the overflow data set is full the export task is

terminated, the import tasks stops and restarts the

export task.

User response:

If there are no MVS system messages that point to the

cause of the stop or start task failure, try stopping and

starting the export task via the DAD monitor. if this fails,

report this error to Technical Support.

BKMA13309E Overflow export start failed.

Explanation:



export task.

User response:



starting the export task via the DAD monitor. If this fails,


BKMA13310E DAD status update failed.

Explanation:


User response:



xxxxxxxxxxxxxxxxxxxxxxxxxxx xxxx

Explanation:


User response:


BKMA13312I Waiting for overflow

Explanation:


User response:

None required.

BKMA13313I Overflow records reloaded nnnnn

Explanation:

Number of overflow records reloaded to dataspace

buffers.

User response:

None required.

BKMA13401E DSN parm not passed

Explanation:


User response:

Pass DATASET parm and try again. If the problem

persists, contact Technical Support.


Explanation:


User response:




Explanation:


User response:



BKMA13404E FROM date invalid

Explanation:

From date passed was not a valid date or mask.

User response:

Pass a date in the format MM/DD/YYYY or

YYYY/MM/DD. If problem persists contact Technical

Support.

BKMA13405E TO date invalid

Explanation:

To date passed was not a valid date or mask.

User response:



Support.


Explanation:

SPACE parm was expected and was not passed.

User response:




Explanation:


User response:





BKMA13408E Number of days missing/invalid

Explanation:

DATE was passed with an invalid mask of *-nnn where

nnn is a number between 0 and 999.

User response:

Correct the nnn value to be between 0 and 999. If the


BKM13409E Error running date calc routine

Explanation:

Date routine ended abnormally.

User response:


Support.


Explanation:


none were found.

User response:


Support. Also determine if backup events actually exist.

BKMA13411E Error reading backup event

Explanation:


an error occurred.

User response:


Support.

BKMA13412E No dataset detail records found

Explanation:

When reading the database for data set detail records

no data set detail records were found.

User response:


Support. Also check to make sure data set detail

records do exist in the database by selecting a backup

event with N to display a data set list.

BKMA13413E Error reading dataset detail records

Explanation:


an error occurred.

User response:


Support.

BKMA13414E Invalid dataset name passed

Explanation:

Data set name passed contains invalid character.

User response:

Correct the data set name and try again. If the problem


BKMA13415E FROM time invalid

Explanation:

From time passed was not a valid time.

User response:

Pass a time in the format HHMM. If the problem


BKMA13416E TO time invalid

Explanation:

To time passed was not a valid time.

User response:



BKMA13501E EVENT parm not passed

Explanation:

EVENT parm expected and was not passed.

User response:

Pass EVENT parm and try again. If the problem



Explanation:


User response:




Explanation:


User response:




Explanation:


User response:



Support.




Explanation:


User response:



Support.


Explanation:


User response:




Explanation:


User response:




Explanation:



User response:



BKMA13509E Error running date calc routine

Explanation:


User response:


Support.


Explanation:


none were found.

User response:



BKMA13511E Error reading backup event

Explanation:


an error occurred.

User response:


Support.

BKMA13512E No event detail records found

Explanation:



User response:





BKMA13513E Error reading event detail records

Explanation:


an error occurred.

User response:


Support.

BKMA13514E Invalid event name passed

Explanation:


User response:




Explanation:


exist.

User response:



BKMA13516W Current aggregate limit = 75

Explanation:

Up to 75 aggregates from a logical aggregate are



User response:

None

BKMA13601E EVENT parm not passed

Explanation:


User response:






Explanation:


User response:




Explanation:


User response:




Explanation:


User response:



Support.


Explanation:


User response:



Support.


Explanation:


exist.

User response:




Explanation:



User response:



BKMA13609E Error running date calc routine

Explanation:


User response:


Support.

BKM13610E No backup events records found

Explanation:


none were found.

User response:



BKM13611E Error reading backup event

Explanation:


an error occurred.

User response:


Support.

BKM13614E Invalid event name passed

Explanation:


User response:



BKMA13615W Currrent aggregate limit= 75

Explanation:




User response:

None

BKMA13701E PGM NAME parm required

Explanation:

No program name was passed to BKMBMAIN in the

JCL.

User response:

Correct the JCL and try again. If the problem persists,




BKMA13702E Authorization failed RC = nnnnnnnn

Explanation:

Backup & Recovery Manager must be run from an

authorized library.

User response:

Authorize the Advanced Backup and Recovery Manager

library and do not concatenate any non-authorized

libraries in the JOBLIB or STEPLIB concatenation.

BKMA13703E Failed load of: module-name LOAD

RC: nnnnnnnn

Explanation:

An error occurred loading module-name.

User response:

Determine that all appropriate load libraries (including

the one containing module-name) are specified as

LOADn parameters in PARMLIB(INI)

BKMA13704E SI27 point fail, RC = nnnnnnnn

Explanation:


User response:


BKMA13705E SI27 GETN fail, RC = nnnnnnnn

Explanation:


User response:


BKMA13801E DAD failure - U83 exit has abended

Explanation:

The U83 EXIT has abended, and the DADESTAE

module will try to shut it down.

User response:


Technical Support.

BKMA13802I U83 exit dormant

Explanation:

The U83 EXIT abended, and the EXIT has been shut

down.

User response:

None required.

BKMA13901E Parm check failed

Explanation:

Parameters passed for aggregate update where invalid.

User response:

Verify parameters are correct and submit JCL again.

BKMA13902E AGG parm not passed

Explanation:

AGG parameter not specified or is invalid.

User response:

Verify AGG parameter is correct and submit JCL again.

BKMA13903E Bad backup GEN passed

Explanation:

BACKUP_GEN_GRPS_TO_RETAIN value not between

1 and 9999.

User response:

Correct the parameter and submit JCL again.

BKMA13904E Bad recovery GEN passed

Explanation:

RECOVERY_GEN_TO_RETAIN value not between 1

and 9999.

User response:


BKMA13905E Error getting SMS info

Explanation:

Call to SMS failed.

User response:


Support.

BKMA13907E Bad mask specified

Explanation:

AGG parameter contains an incorrect mask.

User response:


BKMA13909E Error opening BKM database

Explanation:

An error occurred opening the BKM database.

User response:


Support.

BKMA13910E Error during VREADUPD

Explanation:

An error occurred perform while trying to read a record.

User response:


Support.



BKMA13911E Error closing BKM database

Explanation:

An error occurred closing the BKM database.

User response:


Support.

BKMA13912E Aggregate has been added to BKM

Explanation:

Based on the aggregate name or mask specified, the

Aggregate was found in SMS but not BKM so it was

added.

User response:

None required.

BKMA13913E Error writing to BKM database

Explanation:

An error occurred writing to the BKM database.

User response:


Support.

BKMA13914E WRITE failed, duplicate record found

Explanation:

An attempt was made to add a record that already

existed.

User response:

Try again. If the problem persist contact Technical

Support.

BKMA13915E WRITE failed, no space in database

Explanation:

An attempt was made to write a record but the

database is full.

User response:

Increase the size of the BKM database and try again.

BKMA13917I Aggregate has been updated in BKM

Explanation:


Aggregate was found in BKM and updated.

User response:

None Required.

BKMA13918E Error in override switches: xxxxx

Explanation:

Override switches contain invalid combinations

User response:

Fix the error and retry.

BKMA13919E error initializing AGM record

Explanation:

An attempt was made to initialize the aggregate master

record and failed.

User response:

Try again. If the problem persist contact Technical

Support.

BKMA13920E ISFM version must be 9999 or

NOLIMIT for aggregate

Explanation:

Aggregate option was set to INCR(Y|N) and aggregate

found matching name or mask was not identified in

SMS with a backup retain value of 9999 or NOLIMIT.

User response:

None required.

BKMA13921I Aggregate has been added to BKM

Explanation:

An aggregate was not found in the BKM database but

was added with the values specified.

User response:

None required.

BKMA13922I Aggregate has been updated in BKM

Explanation:

An aggregate was found in the BKM Database and was

updated with the values specified.

User response:

None required.

BKMA13923E INCR parm invalid - Incremental not

licensed

Explanation:

INCR parm is invalid since Incremental is not licensed.

User response:

None required.

BKMA1401E Report type passed invalid

Explanation:

Invalid report type passed.

User response:

Correct the report type and try again. If the problem


BKMA14101E APPL parm not passed

Explanation:

From program to program the APPL name was not

passed.

User response:



Try running the report again. If the problem persists,


BKMA14103E No records found for APPL specified

Explanation:

No data sets were found for the backup-end application

name specified.

User response:

Verify that the backup-end process ran successfully

then try running this report again. If the problem


BKMA14104E Tape volser not found

Explanation:

The tape volser for the output data set was not found to

be cataloged.

User response:



BKMA14105E Internal error occurred

Explanation:

The report failed due to an internal error.

User response:



BKMA14106E No tape sub-system found

Explanation:

When gathering tape information on a data set no tape

subsystem was found.

User response:



BKMA14107E Undefined RC value from MSTPSSFU

Explanation:

When gathering tape information on a data set an

unknown error occurred running the tape-management

interface.

User response:

Try running report again. If the problem persists, contact

Technical Support.

BKMA14108EE TLMSVMP DD not allocated -

skipping location check

Explanation:

The TLMS Tape System was detected and the

TLMSVMP DD was not found in the executing JCL.

User response:

Add the TLMSVMP DD to the JCL point to the TLMS

database and run report again. If the problem persists,


BKMA14109E TLMSVMF is NULLFILE - skipping

location check

Explanation:

The TLMS Tape System was detected but the data set

identified on the TLMSVMF DD was NULLFILE.

User response:

Specify the name of the TLMS database on the

TLMSVMF DD and run report again. If the problem


BKMA14401E APPL parm not passed

Explanation:

APPL parm expected and was not passed.

User response:

Pass APPL parm and try again. If the problem persists


BKMA14402E Bad cycle passed

Explanation:

A cycle number from 0 to 9999 was not passed.

User response:

Pass a cycle number between 0 and 9999. If the


BKMA14403E No records found for APPL specified

Explanation:

Using the application specified, no records were found.

User response:

Verify that the application specified has DSR records

available and try again. If the problem persists, contact

Technical Support.

BKMA14501E No APPL parm passed

Explanation:

An APPL parm was expected and was not passed.

User response:

Pass an APPL parm and try executing again. If the


BKMA14502E No application records found

Explanation:

When reading the database for application records none

were found.

User response:






Explanation:


User response:


BKMA1602E Error returned from BKM01PP1

Explanation:

An internal processing error occurred.

User response:




Explanation:

An internal processing error occurred.

User response:


BKMA1604E No datasets included by selection data

set(s)

Explanation:

After processing all include/exclude parms, no data sets

were left in the include list.

User response:

Change the selection data set so that at least one data

set will be included in the backup and retry the job.

BKMA1605E Error calling BKM01VV1 table name

table processing R15=rr hhhhhhhh

hhhhhhhhh, ID=nnnn

Explanation:

There are numerous sorted tables for processing. An

error occurred while processing one of the tables.

User response:

If the two hex displays contain 00000008 xx0005xx

(where ″xx″ are insignificant digits) check with the

installation’s system programmer and the IEFUSI exits.

This is a result of limitations on dataspace creation

enforced by the exit. Depending on the command and

options within the command, there can be more than 20

dataspaces in use at a time. For all other codes,


BKMA1606E Dsn or mask exceeds 44 bytes: xxxxx

Explanation:

DSN or mask exceeds maximum length of 44 bytes.

Possible reason may be no blank before a ″+″

continuation character.

User response:

Processing ends. Correct the error and retry the job. If

the problem persists, call Technical Support.

BKMA1607E Aggregate master record not found in

IDS

Explanation:

The aggregate master was not found. Check to make

sure the aggregate name was spelled correctly. It could

also be due to a corrupted IDS.

User response:

Determine the cause of the problem and retry the job. If


BKMA1608I alias-name: changed to TRUENAME:

truename

Explanation:

A non-VSAM alias name was found in the selection data

set, either as a discrete name or as a result of a filter.

ABARS can not handle Alias names. The Alias name is

changed to the truename in the modified selection data

set.

User response:


BKMA1609E Selection data set error : xxxx

Explanation:

Error xxxx was found in the selection data set.

User response:



Explanation:


User response:




Explanation:


User response:



Support.


Explanation:


User response:




BKMA1705E No data sets included by selection

data sets

Explanation:

After processing the selection data sets, there were no

data sets to go into the INCLUDE parameter of the

rebuilt selection data set. HSM requires at least one

INCLUDE.

User response:

Fix the problem and retry the job.

BKMA1706W Allocation failed - retry: dsn

Explanation:

Allocation of selection data set failed. Will wait for a

while and retry.

User response:

None.



Explanation:




User response:



controls execution.

BKMA1708I xxxx: serialization failed - retry

Explanation:

Attempt to obtain ARCDSN ENQ for data set xxxx

failed.

User response:

None. Will wait 30 seconds and retry ENQ.

BKMA1709W PDS member in use - retry: dsn

Explanation:

Attempt to obtain exclusive use of the PDS member for

update failed. Wait for a while and retry.

User response:

None. Will wait 30 seconds and retry.

BKMA1710E Unable to get exclusive control of the

SDS: dsn

Explanation:

Attempt to obtain exclusive use of the PDS to open for

update failed after repeated retries.

User response:



Support.


Explanation:


User response:


BKMA1802E Error calling xxxxxxxx RC= rr

Explanation:

This is an internal error.

User response:



Explanation:


User response:



Explanation:


User response:



BKMA1902E (Un)allocation failed: file-name

Explanation:


User response:



Support.


Explanation:


User response:


BKMA1904E Error calling xxxxxxxx R15=nnnn

Explanation:


xxxxxxxx is the program name. Processing terminates.

User response:



controls execution.



BKMA1905E Duplicate record zipping instruction

data set

Explanation:


User response:


BKMA2000I Created token name: token

Explanation:

Informational only and is intended to be used during

problem determination if necessary.

User response:

None.

BKMA2001E BKMCVT control block not where

expected

Explanation:


User response:


BKMA2002E Name token create failed: nnnnn

Explanation:


User response:



Explanation:


nnnnnn is the program name. Processing terminates.

User response:



controls execution.

BKMA2201E SYSEVENT TRANSWAP failed

Explanation:

An attempt to make the address space non-swappable

failed.

User response:


BKMA2301E PGSER failed - SVC table

Explanation:


User response:


BKMA2302E PGSER failed - SVC routine

Explanation:


User response:


BKMA2303E TCB not found where expected

Explanation:


User response:


BKMA2401E TCB not found where expected

Explanation:


User response:


BKMA2402E PGSER failed - SVC table

Explanation:


User response:


BKMA2403E PGSER failed - SVC routine

Explanation:


User response:


BKMA2701I Recovering xxxxxxxx using CFILE

yyyyyy

Explanation:

ABARS is starting an ARECOVER for aggregate

xxxxxxxx under ABR management. It will be using the

ABARS ″C″ file yyyyyy.

User response:

None.

BKMA2702I ABACKUP starting for aggregate

xxxxxxxx

Explanation:

ABARS is starting an ABACKUP for aggregate xxxxxxxx

under ABR management.

User response:

None.

BKMA1905E • BKMA2702I IBM Confidential


BKMA2703E Invalid control block construct

Explanation:


User response:


BKMA2799E BKMWFTCH ended with errors

Explanation:


User response:


BKMA2901E SDS must be passed for check parm

Explanation:

Internal program error. Parm expected was not passed.

User response:

Try again. If the problem persists contact Technical

Support.

BKMA2902E AGG/SDS or AGG/EVENT must be

passed

Explanation:

Internal program error. Parm expected was not passed.

User response:


Support.

BKMA2903E Error allocating SDS

Explanation:

SDS to unzip was not allocated.

User response:

Check to see that the data set in question is cataloged.

If so try again. If the problem persists, contact Technical

Support.

BKMA2904E Error freeing SDS

Explanation:

SDS was allocated for decompress and could not be

deallocated.

User response:



Support.

BKMA2905W SDS allocation failed - retry

Explanation:

Allocation of SDS failed. Will wait 1 minute and retry.

User response:

None.

BKMA2906I SDS not currently converted

Explanation:

SDS not in converted status.

User response:

None.

BKMA2907E Compressed SDS not found

Explanation:

SDS was not found in the database to decompress.

User response:



Support.

BKMA2909I SDS successfully deconverted

Explanation:

SDS was rebuilt to original form.

User response:

None.

BKMA3101E BKMAGINT failed

Explanation:

This is probably an internal error.

User response:


BKMA3102E INCREMENTAL invalid for this

aggregate

Explanation:

This aggregate has not been specified as an

INCREMENTAL aggregate.

User response:

If the INCREMENTAL request was valid, use interactive

panel to mark this aggregate as being for incremental

backups.


IDS.

Explanation:




User response:





BKMA3201W xxxxxxxx: excluded-later backup

found in aggregate: yyyyyyyy

Explanation:

xxxxxxxx will not be recovered by this ARECOVER. The

PREVENT_BACKLEVEL parm was coded and the most

recent backup was found in aggregate yyyyyyyy.

User response:

Verify this is correct and what is desired. If not, recover

the data set from the desired aggregate without the

PREVENT_BACKLEVEL parameter.



Explanation:




User response:



controls execution.

BKMA3301E Error writing to database

Explanation:

An error was encountered while writing the CFILE name

to the database.

User response:


BKMA3302E Duplicate CFILE found after delete

Explanation:

A duplicate CFILE was found and the owning event was

deleted. But when attempting to write the CFILE,

another duplicate CFILE was found.

User response:


BKMA3303E Write failed, no space in database

Explanation:

When attempting to write the CFILE name, the

database was full.

User response:


BKMA3304E Error writing to database

Explanation:

An error was encountered when writing the CFILE name

to the database.

User response:


BKMA3310E Duplicate CFILE used by different

aggregate

Explanation:

CFILE is owned by another application and the event

could not be deleted.

User response:


BKMA3311E Duplicate CFILE not found

Explanation:

A duplicate CFILE was detected but when confirming

the CFILE duplicate, it no longer existed.

User response:


BKMA3350E Delete of duplicate CFILE failed

Explanation:

An error was encountered when deleting the event from

the IDS.

User response:


BKMA3390E Error during VOPEN

Explanation:

An error was encountered when opening the IDS.

User response:


BKMA3391E Error during VREAD

Explanation:

An error was encountered when reading the IDS.

User response:


BKMA3399E Error during VCLOSE

Explanation:

An error was encountered when closing the IDS.

User response:




Explanation:




User response:



controls execution.

BKMA3201W • BKMA3401E IBM Confidential



Explanation:



User response:



controls execution.


Explanation:


User response:



Explanation:


User response:



Explanation:



User response:



controls execution.

BKMA3503E Error calling BKM01VV1 ttttttt Function:


Explanation:




User response:



controls execution.


Explanation:


User response:



BKMA3602W SDS allocation failed - retry: xxxxx

Explanation:

Allocation of SDS failed. Will wait 1 min. and retry.

User response:

None.


Explanation:


User response:



Support.


Explanation:


User response:


BKMA3605E Error calling nnnnnnnn R15=nnnn

Explanation:



User response:



controls execution.

BKMA3606E Duplicate record zipping restart SDS

Explanation:


User response:



Explanation:


User response:



BKMA3702W SDS allocation failed - retry: xxxxx

Explanation:

Allocation of SDS failed. Will wait 1 minute and retry.

User response:

None.

BKMA3402E • BKMA3702WIBM Confidential



Explanation:


User response:



Support.


Explanation:


User response:



Explanation:



User response:



controls execution.

BKMA3706E Duplicate record zipping restart SDS

Explanation:


User response:


BKMA3801E VSAM error - xxxxxx

Explanation:

A VSAM error occurred processing the HSM BCDS.

Where xxxxxx is the macro.

User response:

If the problem persists, call Technical Support.

BKMA3802E xxxxxxxx un-allocation failed - reason

Explanation:


User response:



Support.

BKMA3803E xxxxxxxx allocation failed - reason

Explanation:


User response:



Support.

BKMA3804W ABR record not found in BCDS.

Explanation:

A search of the HSM BCDSs found no ABR record for

this ABACKUP.

User response:

This is an indication that the ABACKUP may not have

been successful. Check for error messages to

determine the problem. If the ABACKUP was not

successful, fix the errors and retry.

BKMA3805I ABR record found in BCDS.

Explanation:

A search of the HSM BCDSs found a ABR record for

this ABACKUP.

User response:

None. Informational only.

BKMA3806W xxxxxxxx allocation failed - retry.

Explanation:


User response:

Will retry allocation up to 5 times before giving up.

BKMA3899E Internal error

Explanation:


User response:




Explanation:




User response:



controls execution.



yyyy

Explanation:



parmlib.



User response:





parmlib member.



yyyy

Explanation:

The INI data for section xxxx token yyyy is invalid.

User response:





Explanation:




User response:



controls execution.


Explanation:


User response:




Explanation:




User response:



controls execution.



Explanation:




User response:



controls execution.


Explanation:




User response:



controls execution.


xxxxxxxxxxx

Explanation:


keywords.

User response:



Explanation:




User response:


BKMA4703W Aggregate master record not found in

IDS.

Explanation:




User response:

Processing continues. No SDSL to SDS conversion is

done for this aggregate.

BKMA4704W Aggregate not using SDSL

Explanation:

The aggregate master record indicates that the

aggregate is not using SDSL.

User response:

Processing continues. No SDSL to SDS conversion is

done for this aggregate.

BKMA4002W • BKMA4704WIBM Confidential


BKMA4901E Invalid aggregate name: xxxxxxxx

Explanation:

This aggregate name does not meet syntactical rules.

User response:

The job fails. Fix the problem and rerun.

BKMA4902E More than 99 aggregates names

specified in this command.

Explanation:

Only 99 events can be processed by a single command.

User response:

The job fails. Submit multiple commands or jobs in

process events in excess of 99.

BKMA4903E Error returned for BKM01FSB - xxxx

Explanation:


User response:


BKMA5001E No backup for this gen/copyset found

Explanation:

No backup event was found in the IDS for the

requested generation numeric and copyset.

User response:




Explanation:




User response:



controls execution.

BKMA5003E Syntax error in command

Explanation:

The command statement is incorrect.

User response:


BKMA5004E Keyword contains invalid parameter(s):

xxx

Explanation:

Keyword xxx is incorrect.

User response:


BKMA5005E Required keyword missing: xxx

Explanation:

Keyword xxx is missing.

User response:


BKMA5006E Mutually exclusive keywords: xxx | yyy

Explanation:

Keywords xxx and yyy are mutually exclusive.

User response:


BKMA5007E XMIT specified but CFILE is not

cataloged:

Explanation:

When XMIT is specified, ARECOVER searches the

catalog for the control and data files. If XMIT is not

specified, an ARECOVER command with the VOLUME()

and UNIT() parameters will be built.

User response:

Either catalog the C, D, O, and I files or remove the

XMIT parameter and retry the job.



yyyy

Explanation:



parmlib.

User response:





parmlib member.

BKMA5009E INI options missing or invalid: retrieve

INI data - Section: xxx Token : yyy

Explanation:


User response:



BKMA5010E Allocation failed for nnn

Explanation:

Dynamic allocation failed for the file identified.

User response:





Support.

BKMA5011E Open error: xxxx

Explanation:


User response:


BKMA5012E VEREXE not valid for native mode

Explanation:

VEREXE is valid only for controlled events.

User response:

Specify either VER or EXE and retry job.


Explanation:


HSEND command.

User response:




Support.

BKMA5014I Member xxx was added / replaced in

PDS yyy

Explanation:

A native mode HSEND command was built and placed

or replaced in PDS yyy

User response:

None.


Explanation:




User response:



controls execution.

BKMA5401W Delete of expired backup events

failed.

Explanation:

An error occurred when attempting to delete events in

excess of the retain versions specified.

User response:


BKMA5402I EXPIREBV issued : xxxx

Explanation:

EXPIREBV command xxxx was issued to HSM.

User response:

None.

BKMA5403W Retain versions invalid default to

9999 : xxxx

Explanation:

Number of retain versions obtained from the IDS (xxxx)

was invalid. Defaulted to 9999.

User response:

Set a valid retain limit in the IDS. If the problem




Explanation:




User response:



controls execution.

BKMA5500I Backup task dispatched for: xxxxxxxx

Explanation:

A backup task has been dispatched for aggregate

xxxxxxxx.

User response:

None.

BKMA5501I Backup task ended | successfully |

with warning exceptions | with error

exceptions | for: xxxxxxxx RC= rrrr

Explanation:

A backup task has ended with status rrrr. Return codes

are for internal use and are used for debugging

purposes when there is a problem.

User response:

If an exception was reported and the cause cannot be

determined from other sources or related messages,

contact Technical Support for assistance.

BKMA5502E Error occurred during attach

Explanation:


User response:




BKMA5503E Error in override switches: xxxxx

Explanation:

Override switches contain invalid combinations.

User response:



Explanation:




User response:

Correct the syntax error(s) and resubmit the job.

BKMA5505E No aggregates specified for ABACKUP

Explanation:

The SYSIN command listed above does not specify any

aggregates to backup.

User response:


BKMA5506E Mutually exclusive keywords xxxxxxxx

yyyyyyyy

Explanation:

The SYSIN command listed above contains mutually

exclusive keywords.

User response:



xxxxxxxxxxx

Explanation:


keywords.

User response:


BKMA5508E Keyword xxxxxx contains invalid

parameter(s)

Explanation:

The keyword indicated in the message contains invalid

or misspelled parameters.

User response:


BKMA5509E Authorization failed, for use of

incremental backup

Explanation:

Authorization to use the incremental backup feature

failed.

User response:

See other messages with specific reasons why

authorization failed. Verify parmlib INI tokens in the

PRODUCT_SECURITY section are set to values

supplied by Technical Support. If these appear correct

call Technical Support.



yyyy

Explanation:



parmlib.

User response:





parmlib member.



Explanation:


User response:




Explanation:


User response:


BKMA5601E DSN or mask exceeds 44 bytes: xxxxx

Explanation:

DSN or mask exceeds maximum length of 44 bytes.

Possible reason is no blank before a ″+″ continuation

character.

User response:

Processing ends. Correct the error and retry the job. If


BKMA5602E Open failed for :xxxxx

Explanation:

An open error occurred for xxxxx.

User response:




BKMA5603E Un-balanced /* - */ pair.

Explanation:


was found.

User response:


BKMA5604E Un-balanced parenthesis.

Explanation:


was found.

User response:


BKMA5605E Empty selection data set(s)

Explanation:

When parsing the selection data sets, the selection data

sets were found to be empty.

User response:



BKMA5899E BKMWDATA not where expected

Explanation:


User response:


BKMA5901E Duplicate event record in IDS

Explanation:

This event is already in the IDS. Most probable cause is

a corrupted IDS.

User response:




Explanation:




User response:



controls execution.

BKMA6002E Activity log is not for an ABACKUP

execution

Explanation:

Attempt was made to load an activity log that was not

for an ABACKUP. This function is valid only for

ABACKUP logs.

User response:

Processing terminates. Specify a valid activity log and

rerun the job.

BKMA6003E Invalid activity log: msgid data

Explanation:

Found unexpected data in the activity log.

User response:

This is most likely an internal error. Contact Technical



execution.

BKMA6004E RECOVERNEWNAMEALL(...) error:

xxxxxx

Explanation:

When resolving a restore data set with new name, an

error was found for data set xxxxxx. Check for any

errors found in the ARECOVER activity log.

User response:

Determine the reason for the error, if any, fix any

problems, and retry the job.

BKMA6005W Message ARC6291I was issued by

ABARS

Explanation:

ARC6291I message indicates that at least one data set

will not be renamed as requested.

User response:

Determine the reason for the message, take appropriate

action and retry the job.

BKMA6006W : dsname : migrated VSAM data set

will not be renamed by full rename.

Explanation:

VSAM data set is migrated. Migrated VSAM data sets

are not supported by full rename.

User response:

Recall the migrated VSAM data set before backup or

build and submit a separate IDCAMS job to rename the

VSAM data sets that failed.



BKMA6007W dsname : catalog search bypassed as

per INI option RENAME.

Explanation:

Token

BYPASS_CATALOG_LOOKUP_DURING_ARECOVER

in section :RECOVERY_OPTIONS was set to ″Y″. After

ARECOVER statistics for the data sets recovered not

collected.

User response:

None required.

BKMA6008I Sequential write failed, switching to

standard write

Explanation:

When inserting records into the IDS sequentially the


User response:




Explanation:




User response:



controls execution.


Explanation:


User response:



Explanation:


User response:


BKMA6201W Delete of expired backup events

failed.

Explanation:

An error occurred when attempting to delete events in

excess of the retain versions specified.

User response:




Explanation:




User response:



controls execution.


Explanation:


User response:



Explanation:


nnnnnn is the program name. lllll is the location where


User response:



controls execution.

BKMA6303E Duplicate record zipping restart data

set

Explanation:


User response:


BKMA6402E (Un)allocation failed:xxxxx

Explanation:


User response:



Support.


Explanation:


User response:


BKMA6007W • BKMA6403E IBM Confidential




Explanation:




User response:



controls execution.


Explanation:




User response:



controls execution.

BKMA6501W Incremental backup requested but a

good base version was not found -

mode changed to base.

Explanation:

An incremental backup was requested but no

proceeding BASE version was found. A BASE version is

required.

User response:

The backup mode is changed to BASE and processing

continues.

BKMA6502E Incremental backup requested but

related base was not a successful

backup

Explanation:

An incremental backup was requested but the related

BASE version backup failed (no ABARS backup was

created).

User response:

Change this backup to a base version and check return

codes to ensure it is successful. The next incremental

should then process successfully.



Explanation:




User response:



controls execution.

BKMA6601E Unable to access the DAD database

Explanation:

When attempting to read the DAD, the task was unable

to get control.

User response:

Determine the reason for the contention and retry.

BKMA6603E DAD file is empty

Explanation:

The DAD file has no entries. All data sets will be backed

up.

User response:

None if the DAD data set is a new data set. If not,

check to make sure the DAD stared task is running.

BKMA6604I Excluded by DAD

Explanation:

During an incremental backup, the DAD data set

indicated that the data set had not been changed since

last backed up by this aggregate.

User response:

None if the DAD data set is a new data set. If not,

check to make sure the DAD stared task is running.



Explanation:




User response:



controls execution.

BKMA6606W All ″INCLUDE″ datasets have been

excluded or no new/changed datasets

found

Explanation:

After processing the data sets, and checking the DAD

for changed data sets, there were no data sets left to be

placed in the INCLUDE parameter of the rebuilt

selection data sets. HSM requires at least one.

User response:

If this was unexpected, fix the problem and retry the job.




Explanation:




User response:



controls execution.



Explanation:




User response:



controls execution.

BKMA6702E Unknown DAD construct error

Explanation:


User response:


BKMA6703E Updated DAD records exceeds max len

:xxxx

Explanation:

The DAD record for data set xxxx, after update,

exceeds the maximum record length specified when the

DAD was allocated.

User response:

Processing terminates. Rebuild the DAD with a larger

maximum record length. (see DAD instructions)

BKMA6801E No aggregates specified for

ARECOVER

Explanation:

The ARECOVER command listed above does not

specify any aggregates to recover.

User response:


BKMA6802E Syntax error in AGGREGATE keyword

Explanation:

The AGGREGATE keyword is incorrect.

User response:


BKMA6803E Error occurred during attach

Explanation:


User response:


BKMA6804I ARECOVER task dispatched for:

xxxxxxxx

Explanation:

A recover task has been dispatched for aggregate

xxxxxxxx. It will run concurrently with other aggregates

recoveries specified on the current ARECOVER

command.

User response:

None.

BKMA6805I Native ARECOVER initiated for:

xxxxxxxx

Explanation:

A ″native″ ARECOVER task has been started for

xxxxxxxx. It will run concurrently with other aggregate

recoveries specified on the current ARECOVER

command.

User response:

None.



yyyy

Explanation:



parmlib.

User response:





parmlib member.



Explanation:


User response:





BKMA6808I Recover ended sssss for aaaaaaaa

Explanation:

ARECOVER task has ended for aggregate aaaaaaaa

with a status of sssss

User response:

If other than successful, check the SYSOUT for

aaaaaaaa.

BKMA6809E Dispatch ECB list error

Explanation:


User response:


BKMA6901E Deleted old Conflict data set - dsn

Explanation:

A previous recovery, with DATASETCONFLICT, was run

and there were conflicts. This created a Conflicts data

set. This time, DATASETCONFLICT was non-blank so

the old Conflict data set has been deleted.

User response:

None.

BKMA6901E Deleted old Conflict data set - dsn

Explanation:

A previous recovery, with DATASETCONFLICT, was run,

and there were conflicts. This created a Conflicts data

set. This time, DATASETCONFLICT was non-blank so

the old Conflicts data set has been deleted.

User response:

None.


Explanation:




User response:


BKMA6903E Mutually exclusive keywords: xxxxxxxx

| yyyyyyyy

Explanation:

The SYSIN command listed above contains mutually

exclusive keywords.

User response:


BKMA6904E Required keyword missing: xxxxxxxxxxx

Explanation:


keywords.

User response:


BKMA6905E Keyword contains invalid parameter(s):

xxxxxx

Explanation:

The keyword indicated in the message contains invalid

or misspelled parameters.

User response:


BKMA6906E No backup for this cycle / gen /

copyset found

Explanation:

The relative generation specified in the ARECOVER

command was not found in the IDS.

User response:


BKMA6908W Invalid backup skipped

Explanation:

During an ARECOVER, the backup event found in the

IDS in the specified incr:base range was for a failed

backup.

User response:

The backup event is skipped and processing continues.

To avoid this message, use the interactive panels to

delete these events prior to the ARECOVER request.

BKMA6909W No eligible datasets found for

ARECOVER

Explanation:

During ARECOVER, found no data sets to be restored

in this backup event. It is possible that all data sets on

this backup were excluded by the filters in the control

statement. If this is an incremental ARECOVER, it is

possible that all backups for this generation are either

excluded by filters or are to be recovered from a more

recent backup.

User response:

Processing continues.

BKMA6910E Restart and/or Conflict data set(s) exist

- NORESTART specified

Explanation:

a Restart data set, Conflict data set or both exists for an

event to be recovered but the NORESTART parameter

was specified.

BKMA6808I • BKMA6910EIBM Confidential


User response:

If this is a valid restart, remove the NORESTART

keyword from the control statement. If not, delete all

restart and conflict data sets related to the ARECOVER

and retry the job.

BKMA6911E (un)allocation failed: xxxxxxxx

Explanation:

Dynamic allocation or unallocation failed for xxxxxxxx

User response:



Support.


Explanation:


User response:

Determine the reason for the open failure and retry the

job.

BKMA6913E XMIT specified but CFILE is not

cataloged: xxxxxx

Explanation:

When XMIT is specified, ARECOVER searches the

catalog for the control and data files. If XMIT is not

specified, we will build the ARECOVER command with

the VOLUME() and UNIT() parameters.

User response:

Either catalog the C, D, O, and I files or remove the

XMIT parameter and retry the job.

BKMA6915E Full rename requested but

ALLOWFULLRENAME disallowed

Explanation:

Full rename is disallowed by INI (see section

:RECOVER_OPTIONS, token ALLOWFULLRENAME).

User response:

Either change the to value ″Y″ or remove the full

rename request from the control statement, and rerun

the job.

BKMA6923W PROCESS_OPTIONS/SYSOUT_CLASS

missing or value is invalid

Explanation:

In the parmlib member INI, in section

PROCESS_OPTIONS, the parameter SYSOUT_CLASS

was not found or the value was invalid.

User response:

Processing continues. A default of ″*″ will be used.



Explanation:




User response:



controls execution.



yyyy

Explanation:



parmlib.

User response:




available listing that contains this message and the

parmlib member.



Explanation:


User response:



BKMA6929E Error during attach

Explanation:


User response:




BKMA7001E (un)allocation failed: xxxxxxxx

Explanation:

Dynamic allocation or unallocation failed for xxxxxxxx

User response:



Support.




Explanation:


HSEND command.

User response:




Support.

BKMA7004E No HSM ARECOVER started task found

for : xxxxxxxx

Explanation:

HSEND ARECOVER WAIT command returned with a

return code of zero but determined that HSM never got

control.

User response:

Check sysout for any previous messages. Check

system log for messages. If still unable to determine the

reason for the failure, issue the HSEND from ISPF

option 6 to see if any messages are returned by

HSEND that ABR was unable to trap. If the reason for

the error still cannot be determined, call Technical


BKMA7005E ABARS function failed in HSM.

Explanation:

The task determined that an error occurred in the HSM

secondary address space.

User response:

Check the system log for ″BKM″ error messages. Call

Technical Support for help in resolving the error if

necessary.

BKMA7008E No activity log found for this task.

Explanation:

Unable to find an activity log for this task.

User response:

Check for any messages preceding this one. If unable

to determine the reason for this error, call Technical


BKMA7202E Input SI027 table error

Explanation:


User response:


BKMA7203E Unknown backup type

Explanation:


User response:




Explanation:




User response:



controls execution.

BKMA7301E BKMWDATA not found where expected

Explanation:


User response:


BKMA7401E Required keyword missing or in error:

xxxxxx

Explanation:

Keyword xxxxxx is either missing or contains a syntax

error.

User response:


BKMA7402W Backup already in IDS: xxxxxx

Explanation:

The backup being loaded is already in the IDS. xxxxxx

is the event id of the backup already in the IDS.

User response:

If this is a problem, fix the error and retry the job.

BKMA7403E Allocation failed for: xxxx

Explanation:


User response:



Support.



BKMA7404I Activity log successfully loaded into

IDS.

Explanation:

(Informational message.)

User response:

None.

BKMA7405W Activity log is for a verify mode

event. Not loaded.

Explanation:

It was determined that the activity log was for a Verify

event. LOADACT will load only EXECUTE mode events.

User response:

Processing stops for this command and continues with

the next command.

BKMA7406E Un-allocation failed for : xxxx

Explanation:


User response:



Support.

BKMA7407E Unable to determine log type

Explanation:

Unable to determine if the activity log was for

ABACKUP or ARECOVER.

User response:

Processing terminates. The most likely cause is the

event failed and the messages required are missing. If

unable to determine the cause, call Technical Support.



Explanation:




User response:



controls execution.

BKMA7491E Required CFILE for the backup event

not found

Explanation:

The CFILE record for the backup event to be recovered

was not found in the IDS.

User response:


BKMA7492E The backup event record not found in

IDS.

Explanation:

The backup event record for the backup event to be

recovered was not found in the IDS.

User response:


BKMA7493E Storage obtain for BKMCVT failed in

IDS.

Explanation:

GETMAIN failed.

User response:

Increase the region size. If the problem persists, call

Technical Support.


Explanation:




User response:


BKMA8102E Error calling nnnnnnnn R15=nnnn ID=lllll

Explanation:




User response:



controls execution.



Explanation:




User response:



controls execution.

BKMA8105E (un)allocation failed: xxxxx

Explanation:


User response:





Support.



yyy

Explanation:


User response:





yyyy

Explanation:



parmlib.

User response:



for the failure, contact Technical Support. Have available


member.

BKMA8202W Aggregate construct not found: xxxx

Explanation:


User response:

If this is valid aggregate, define it using ISMF, activate a

new configuration.

BKMA8203E Invalid aggregate | mgmtclas name:

xxxx

Explanation:

The aggregate or management class xxxx is invalid.

User response:


BKMA8204W Specific aggregate not found in IDS:

xxxx

Explanation:

The aggregate name xxxx was not found.

User response:


BKMA8205E Related aggregate not in IDS :xxxx

Explanation:

An aggregate related to logical aggregate xxxx was not

found.

User response:




Explanation:




User response:



controls execution.

BKMA8207E Error returned from BKM01FSB - xxxx

Explanation:


User response:



Explanation:


User response:



Explanation:




User response:



controls execution.


Explanation:


User response:






Explanation:




User response:



controls execution.


Explanation:




User response:



controls execution.

BKMA8502E Unknown record type:xxxxx

Explanation:

This is an internal error. xxxxx is the key of the problem

record.

User response:


BKMA8503E IDS empty

Explanation:

The object IDS is an empty file.

User response:

Check to see if the correct IDS was specified. Fix the

error and retry the job.



Explanation:




User response:



controls execution.


Explanation:

a VSAM error occurred processing the HSM BCDS.


User response:



Explanation:


User response:



Support.

BKMA8603E xxxxxxxx allocation failed - reason

Explanation:


User response:



Support.

BKMA8604W ABR record not found in BCDS

Explanation:

A search of the HSM BCDS(s) found no ABR record for

the backup event being recovered. This could be

because an EXPIREBV expired this event.

User response:

None if this is not a problem.


Explanation:


User response:



Explanation:




User response:



controls execution.



Explanation:




User response:





controls execution.

BKMA8705E xxxxxxxx (un-)allocation failed

Explanation:


User response:



Support.



yyy

Explanation:


User response:





yyyy

Explanation:



parmlib.

User response:





member.


Explanation:


User response:


BKMA8802E SI040 Open error

Explanation:


User response:




Explanation:




User response:



controls execution.



Explanation:




User response:



controls execution.


Explanation:




User response:



controls execution.

BKMA8903E ESEQ record not found

Explanation:

A required records was not found in the IDS. This is

either an internal error or a corrupted database.

User response:

Processing terminates. Call Technical Support.


Explanation:


User response:


BKMA9002E Unknown record type:xxxxx

Explanation:


User response:






Explanation:




User response:



controls execution.


Explanation:


User response:



Explanation:


User response:


BKMA9202E Invalid aggregate name:xxxxxxxx

Explanation:

This aggregate name does not meet syntactical rules,

User response:

Job fails. Fix the problem and rerun.

BKMA9203E Specific aggregate not in input

file:xxxxxxxx

Explanation:

This fully qualified aggregate name was not found in the

input file.

User response:

Job continues.

BKMA9204E Related aggregate not in input

file:xxxxxxxxyyyyyyyy

Explanation:

Aggregate yyyyyyyy that is related to logical aggregate

xxxxxxxx was not found in the unloaded flat file.

User response:

Job fails. Fix the problem and rerun.



Explanation:




User response:



controls execution.

BKMA9207E Error returned for BKM01FSB - xxxx

Explanation:


User response:


BKMA9300E Error parsing parmlib INI member

Explanation:

A syntax error occurred while parsing the parmlib INI

member.

User response:

See accompanying messages for the specific syntax

error. Change the INI member and try again.

BKMA9301E ALLOC DD DIR failed

Explanation:

An error occurred attempting to allocate the DD name

DIR to the load libraries specified by the LOADn tokens

in the parmlib INI member.

User response:

See accompanying message for the specific allocation

error.

BKMA9302E BLDLTASK attach failed

Explanation:

An error occurred attempting to attach BLDLTASK.

User response:

Check that BLDLTASK is in the LOAD1 library.

BKMA9303E VPUT of MSVECTOR failed

Explanation:

ISPF VPUT service failed.

User response:


BKMA9304E LIBDEF ISPPLIB failed

Explanation:

Failure occurred issuing ISPF LIBDEF for ISPPLIB

using library names from INI tokens ISPPLIBn.

User response:

Check library names specified by tokens ISPPLIB1-nn

specified by the INSTALLATION_DATASETS section of

the parmlib INI member.



BKMA9305E LIBDEF ISPMLIB failed

Explanation:

Failure occurred issuing ISPF LIBDEF for ISPMLIB


User response:




BKMA9306E LIBDEF ISPTLIB failed

Explanation:

Failure occurred issuing ISPF LIBDEF for ISPTLIB


User response:




BKMA9307E LIBDEF ISPLLIB failed

Explanation:

Failure occurred issuing ISPF LIBDEF for ISPLLIB using

library names from INI tokens LOADn.

User response:

Check library names specified by tokens LOAD1-nn



BKMA9308E INVENTORY_DATASET token not found

Explanation:

The INVENTORY_DATASET token was not found in the

PRODUCT_DATASETS section of the parmlib INI

member.

User response:

Check parmlib INI member for the correct section and

token names.

BKMA9303E INIGET of INVENTORY_DATASET

failed, RC: nnn

Explanation:

Internal error.

User response:


BKMA9310E ALLOC of IDS failed

Explanation:

Failure attempting to allocate ddname IDS to the data

set specified by the INI token INVENTORY_DATASET.

User response:

Accompanying message should specify allocation error

reason. Check allocation error message and status of

data set specified by the INVENTORY_DATASET token.

BKMA9311E ABR_TITLE1 token not found

Explanation:

The ABR_TITLE1 token was not found in the

PRODUCT_INFO section of the parmlib INI.

User response:


token names.

BKMA9312E INIGET of ABR_TITLE1 failed, RC: nnn

Explanation:

Internal error.

User response:


BKMA9313E VPUT of ABR_TITLE1 FAILED, RC: nnn

Explanation:


User response:



Explanation:



User response:


token names.

BKMA9315E INIGET of ABR_TITLE2 FAILED, RC:

nnn

Explanation:

Internal error.

User response:



Explanation:



User response:


token names.


Explanation:

Internal error.

User response:




BKMA9318E VGET of ISPTUTEP failed, RC: nnn

Explanation:

Internal error.

User response:


BKMA9319E Authorization failed, RC: nnn

Explanation:

Authorization to use the product failed.

User response:

See other messages with specific reasons why

authorization failed. Verify parmlib INI tokens in the

PRODUCT_SECURITY section are set to values

supplied. If you received your authorization codes via

Lotus Notes®, verify the blanks are X`40` and not X`41`.

If all appears correct, call Technical Support.

BKMA9320E Error freeing IDS

Explanation:

Error issuing FREE for ddname IDS

User response:

See accompanying error message with SVC99 reason.

If the issue cannot be resolved from error message, call

Technical Support.

BKMA9321E UNDO LIBDEF ISPLLIB failed, RC: nnn

Explanation:

Error trying to remove LIBDEF for ISPLLIB.

User response:


BKMA9322E UNDO LIBDEF ISPMLIB failed, RC: nnn

Explanation:

Error trying to remove LIBDEF for ISPMLIB.

User response:


BKMA9323E UNDO LIBDEF ISPTLIB failed, RC: nnn

Explanation:

Error trying to remove LIBDEF for ISPTLIB.

User response:


BKMA9324E UNDO LIBDEF ISPPLIB failed, RC: nnn

Explanation:

Error trying to remove LIBDEF for ISPPLIB.

User response:


BKMA9325E Error freeing DIR

Explanation:

Error issuing FREE for ddname DIR

User response:

See accompanying error message with SVC99 reason.

If issue cannot be resolved from error message, call

Technical Support.

BKMA9326E SI027 GETDIR failed, RC nnn

Explanation:

Error retrieving in-memory token value.

User response:

Internal error. Call Technical Support.

BKMA9400E VPUT of MSVECTOR failed, RC: nnn

Explanation:


User response:


BKMA9401E VPUT of ISPTUTEP failed, RC: nnn

Explanation:


User response:



Explanation:



User response:


token names.


Explanation:

Internal error.

User response:


BKMA9404E VPUT of GENTITL1 failed, RC: nnn

Explanation:


User response:





Explanation:



User response:


token names.


Explanation:

Internal error.

User response:



Explanation:


User response:



Explanation:



User response:


token names.


Explanation:

Internal error.

User response:



Explanation:


User response:



Explanation:

A VSAM error occurred processing the HSM BCDS.


User response:



Explanation:


User response:



xxxxxxxxxxx

Explanation:


keywords.

User response:


BKMA9505E xxxxxxxx allocation failed

Explanation:


User response:



Support.

BKMA9506I ACTLOG not found inCATALOG: xxxxxx

Explanation:

An attempt was made to copy the activity log to the

IDS, but the associated activity log was no longer

cataloged

User response:



Explanation:


User response:



Support.


Explanation:




User response:

Correct the syntax error(s) and resubmit the job.



BKMA9510I Aggregate construct not

found:xxxxxxxx

Explanation:


User response:

No events for this aggregate will be migrated to the IDS.


BKMA9511I Input not sorted.

Explanation:

The input is not in the expected sequence. Verify that

the sort step ran successfully.

User response:

Job fails. Fix the problem and rerun the job.

BKMA9514E Record already in IDS: xxxxxxxx

Explanation:

The record was already in the IDS. This could be due to

a restart of the job.

User response:



Explanation:


User response:



Explanation:


User response:

Determine the reason for the open failure and rerun the

job.

BKMA9602E Entry parm record type invalid

Explanation:


User response:


BKMA9603E SDSL not found in IDS for

aggregate:xxxxxxxx

Explanation:

The SDSL control could not be found in the IDS.

User response:

If the control has not been created, use the ISPF panels

to create and save the SDSL control and rerun the job.

BKMA9604E Group filter not found in IDS:xxxxxxxx

Explanation:

The SDSL control referenced a group filter name that

does not exist in the IDS.

User response:

If the group name has not been misspelled, it may not

have been created. If this is the case, use the ISPF

panels to create and save the group and rerun the job.

BKMA9605E module-name LOAD FAIL, RC=return

Explanation:


User response:



LOADn parameters in PARMLIB(INI).

BKMA9606E Error retrieving SDSL/GFLT from IDS

ID: xxxx

Explanation:


User response:


BKMA9701E Retrieve filter failed si35errmsg

Explanation:

An error occurred retrieving filters.

User response:

Check the si35errmsg for additional information. If this is

not sufficient to solve the problem, call Technical

Support.

BKMA9702E Retrieve group filter failed si35errmsg

Explanation:

An error occurred retrieving Group filters.

User response:

Check the si35errmsg for additional information. If this is

not sufficient to solve the problem, call Technical

Support.

BKMA9703E Error storing filter. RC=return

Explanation:

An error occurred storing a filter in a temporary table.

User response:




BKMA9711E module-name load fail, RC=return

Explanation:


User response:



LOADn parameters in PARMLIB(INI)

BKMA9712E Filter exceeds maximum length:

partial-filter

Explanation:

A filter exceeded the maximum length of 4096 bytes.

The beginning of the filter is printed as an aid in finding

the offending filter.

User response:

Separate the filter into multiple filters.


Explanation:


User response:



IDS

Explanation:




User response:



BKMA9802E (Un)allocation failed for xxxx

Explanation:

Dynamic allocation failed for file xxxxxx.

User response:

See preceding messages to determine the reason for

the failure. Fix the problem, if it is a customer issue, and

retry the job. If it is not or the problem persists, call

Technical Support.

BKMA9804E Open failed for xxxxx

Explanation:

An open error occurred for file xxxxx.

User response:


BKMA9806E No valid candidates found

Explanation:

No valid candidate data sets were found in the input.

User response:

Review other error messages and the SDS or SDSL

input to determine source of problem.



Explanation:




User response:



controls execution.


Explanation:




User response:



controls execution.

BKMA9809E nnnnn : DSTYPE xxx is invalid

Explanation:

An internal filtering error occurred.

User response:



controls execution.

BKMA9810E Unknown filter, type=y Filter=yyyyyy

Explanation:

An internal filtering error occurred.

User response:



controls execution.



yyyy

Explanation:



parmlib.



User response:





member.

BKMA9812E Filter skipped - xxxxx inappropriate for

DSN=nnnn yyyyy - fffff

Explanation:

A filter xxxxx with the scope of yyyy is being applied to

a DSN (nnnn) that does not possess that attribute , e.g.

REFDT for a GDGBASE.

User response:

Processing terminates. Fix the problem in the SDSL

code and retry. If unable to determine the reason for the

failure, contact Technical Support. Have available the

listing that contains this message.

BKMA9813E Volume(...) OR STORAGEGROUP(...) in

SDSL invalid

Explanation:

CANDIDATES statement in SDSL is incorrect.

User response:

Correct the error and retry.

BKMA9814E UCBSCAN error return code: rrrr

reason code: nnnn

Explanation:

Internal error.

User response:


BKMA9815W Volume not mounted: xxxxxx

Explanation:

A volser requested by a SDSL candidate statement was

not mounted on the system.

User response:


BKMA9816E UCBLOOK error return code: rrrr

Reason code: nnnn

Explanation:

Internal error.

User response:


BKMA9817E Error calling IDGCSP00 RC= rrrr

Explanation:

Internal error.

User response:


BKMA9818E Unable to obtain SMS storage group

construct for: nnn

Explanation:

SMS construct was not found for storage group nnn.

User response:

Probably misspelled. Correct the error and retry.

BKMA9819E Error attempting to obtain SMS storage

groups RC= rrrr

Explanation:

Internal error.

User response:


BKMA9820E Error attempting to obtain SMS volume

construct(s) for storage group nnnn

RC= rrrr

Explanation:

Internal error.

User response:


BKMA9821I INI return code override applied for:

msgid STORAGE GROUP nnnn RC= rrrr

Explanation:

Message ID xxxxx was found in section

ABARS_RC_OVERRIDE of the INI. The return code

specified there will be applied.

User response:


BKMA9896I Number of data sets selected =

nnnnnnnn

Explanation:

The number of data sets selected for processing.

User response:

None.

BKMA9897E No data sets included by selection

data sets

Explanation:

No valid data sets were found in the input.

User response:

Review other error messages and the SDS or SDSL

input to determine source of problem.




Messages (BKMB)

BKMB0002E SKIPDS allocation failed for: xxxxxx

Explanation:

Dynamic allocation failed for data set xxxxxx for the

reason specified.

User response:



Support.

BKMB0003E SKIPDS unallocation failed for: xxxxxx

Explanation:

Dynamic unallocation failed for data set xxxxxx for the

reason specified.

User response:



Support.

BKMB0007E CONFLI allocation failed for: xxxxxx

Explanation:

Dynamic allocation failed for data set xxxxxx for the

reason specified.

User response:



Support.

BKMB0008E CONFLI unallocation failed for: xxxxxx

Explanation:

Dynamic unallocation failed for data set xxxxxx for the

reason specified.

User response:



Support.

BKMB0101E Error calling BKM01VV1 ttttttt Function:


Explanation:




User response:



controls execution.

BKMB0201I Invalid INCLUDE or EXCLUDE

parameter.

Explanation:

A DSN or mask in the INCLUDE(...) parameter is

invalid. Check length or for invalid masking characters.

User response:


BKMB0202I xxxxx : not selected by INCLUDE(...)

Explanation:

DSN xxxxx was backed up by the event being

recovered but did not match any data set or mask in the

INCLUDE(...) parameter.

User response:

None.

BKMB0203I xxxxxx : excluded by EXCLUDE(...)

Explanation:


recovered but was excluded from recovery by a data set

name or mask in the EXCLUDE(...) parameter.

User response:

None.

BKMB0204I xxxxxx : file type not one of selected

types

Explanation:


recovered but was excluded from recovery because its

file type (Primary, ML1, ML2, or UTAPE) was not one of

the ones specified in the control statement.

User response:

None.

BKMB0205I xxxxxx : not an active member of a

GDG base

Explanation:


recovered but was not a active member of the GDG

base when the most recent, incremental version being

recovered was backed up.

User response:

None.

BKMB0206W No GDG base record found in IDS

for: xxxxxx

Explanation:

IBM Confidential

71


recovered but no GDGB record was found in the IDS.

The GDGB record is used to recover the GDS’s in the

correct order.

User response:

The GDS is included in the recovery, but the GDG

should be checked after the recovery to insure that it is

correct.

BKMB0207W Error calling BKM01VV1 tttttttt



Explanation:




User response:



controls execution.

BKMB0208W Unknown file type found in IDS :

xxxxx

Explanation:

File type xxxxx was the file type found in IDS for the

following ″NOT SELECTED″ data set. This most likely

due to corrupted data.

User response:

Contact Technical Support for help in resolving this

error.

BKMB0209I xxxxxx : not selected - GDGGEN0ONLY

was specified

Explanation:

DSN xxxxxx was backed up but was not selected for

recover because it was not the +0 generation when this

GDG family was backed up.

User response:

None.

BKMB0302E (Un)allocation failed for: xxxxx

Explanation:


specified.

User response:



Support.

BKMB0304E Open failed for: xxxxx

Explanation:

An open error occurred for the file indicated.

User response:


BKMB0305I No datasets recovered from this

cycle/gen

Explanation:

After processing all INCLUDE / EXCLUDE parameters

all data sets backed up by this event were excluded

from recovery.

User response:

If this is not what was intended, correct the control

statements and retry the job.

BKMB0306E Odd number of levels specified for


Explanation:

The RECOVERNEWNAMELEVEL parameter was

incorrectly coded The OLDprefix NEWprefix must be in

even numbered pairs.

User response:


BKMB0307E More than 30 levels specified for


Explanation:

ABARS allows only 30 RECOVERNEWNAMELEVEL

pairs.

User response:


BKMB0308E Duplicate old HLQs listed in

RECOVERNEWNAMELEVEL

Explanation:

An old high level qualifier may be listed in the

RECOVERNEWNAMELEVEL only once.

User response:


BKMB0309E RECOVERNEWNAMEALL would result

in an attempt to rename more than one

data set to the same name.

Explanation:

This usually occurs when a recover is being done for

data sets with multiple high level qualifiers that have

common lower level qualifiers.

User response:


BKMB0207W • BKMB0309E IBM Confidential


BKMB0310E Error calling BKM01VV1 tttttttt Function:


Explanation:




User response:



controls execution.

BKMB0311E Severe error when attempting to


yyyy

Explanation:



parmlib.

User response:





member.

BKMB0499E Internal error

Explanation:


User response:


BKMB0501I A non-ABR function found

Explanation:

An ABARS function was determined to be non-ABR

controlled.

User response:

None.

BKMB0502E Allocation failed for DD: SKIPDS

Explanation:

Dynamic allocation of the data set to be used by the

HSM ARCSKEXT exit failed.

User response:


BKMB0503E Open error for DD: SKIPDS

Explanation:

Open failed for the data set to be used by the HSM

ARCSKEXT

User response:


BKMB0504W Un-allocation failed for DD: SKIPDS

Explanation:

Dynamic unallocation of the data set to be used by the

HSM ARCSKEXT exit failed.

User response:

Processing continues. Report the error to Technical

Support.

BKMB0505W Unable to locate related HSM MWE

reason continuing without ABR

tracking

Explanation:

HSM has no or more than one ABRCB for this ASID.

After several retries, unable to determine which MWE

was related to the event being processed in the address

space. This is usually due to HSM being to busy

maintain its control blocks in a timely manner.

User response:

Processing continues but treats the event as if it is a

″native″ command and tracking is not done. If this was

a BKM function, the batch job will abend with a U999

and message BKMA0804E will be issued. The job may

either be rerun or the activity log may be loaded using

the LOADACT command.

BKMB0506E SI027 PUT error

Explanation:


User response:


BKMB0507E Sub-task event block not found

Explanation:


User response:


BKMB0701E DSN parm not passed

Explanation:


User response:



BKMB0702E No SPACE format passed

Explanation:


User response:



BKMB0310E • BKMB0702EIBM Confidential


BKMB0703E SPACE format passed invalid

Explanation:


User response:



BKMB0704E No backup event records found

Explanation:

While counting the generations of backup event files

none were found in the database.

User response:


Technical Support.

BKMB0705E Error reading backup event records

Explanation:

While trying to gather backup event data an error

occurred.

User response:


Technical Support.

BKMB0706E No data set detail records found

Explanation:



User response:


Technical Support.

BKMB0707E Error reading data set detail records

Explanation:


occurred.

User response:


Technical Support.

BKMB0708E Invalid data set name passed

Explanation:



User response:


Technical Support.

BKMB0709E Backlevel data set already contains

data

Explanation:

When initializing the backlevel VSAM data set, it was

found not to be empty.

User response:



BKMB0801I No overlaps: aggname

Explanation:

No overlaps were found for event name or mask

passed.

User response:

None.

BKMB0802E No EVENT parm passed

Explanation:

An EVENT parm was expected and was not passed.

User response:

Pass an EVENT parm and try executing again. If the


BKMB0803E No GEN parm passed

Explanation:

A GEN parm was expected and was not passed.

User response:

Pass a GEN parm and try executing again. If the



Explanation:


User response:




Explanation:


User response:



BKMB0806E No backup events records found

Explanation:


none were found.

User response:

BKMB0703E • BKMB0806E IBM Confidential





Explanation:


an error occurred.

User response:


Support.


Explanation:



User response:


Technical Support.


Explanation:


occurred

User response:


Technical Support.


Explanation:



User response:


Technical Support.

BKMB0811E Bad FROM generation passed

Explanation:


User response:



BKMB0812E Bad TO generation passed

Explanation:


User response:



BKMB0813I Logical aggregate not found

Explanation:


exist.

User response:


the problem persists, contact Technical Support.

BKMB0814W Current aggregate limit = 75

Explanation:




User response:

None.

BKMB0815E Backlevel data set already contains

data

Explanation:

When initializing the backlevel VSAM data set, it was

found not to be empty.

User response:



BKMB0901E Syntax errors in command

Explanation:




User response:


BKMB0902E Required keyword missing -

xxxxxxxxxxx

Explanation:


keywords.

User response:


BKMB1001E (Un) allocation failed:xxxxx

Explanation:


User response:



Support.



BKMB1002E Open error: xxxxx

Explanation:


User response:


BKMB1003E Aggregate construct not found

Explanation:


User response:



BKMB1101E Un-balanced /* - */ pair.

Explanation:


was found.

User response:


BKMB1102E Un-balanced parenthesis.

Explanation:


was found.

User response:


BKMB1103E Empty selection data set(s).

Explanation:

When parsing the selection data set(s), the selection

data set(s) were found to be empty.

User response:




Explanation:


User response:


BKMB1105E Error calling xxxxxxxx R15=nnnn

Explanation:




User response:



controls execution.

BKMB1106E Unexpected end of file processing


Explanation:

An internal processing error as occurred.

User response:



Explanation:


User response:


BKMB1202E Error deleting old SDSL record

Explanation:

An error occurred when attempting to delete an old

SDSL record in preparation for writing a new one.

User response:

If the problem persists, and the cause cannot be

determined, call Technical Support.

BKMB1203E Duplicate record zipping activity log

Explanation:


User response:


BKMB1301I Full RENAME mode: EXECUTE | FILE

Explanation:

Display of the full rename mode requested. FILE

specifies that a file of ALTER/NEWNAME IDCAMS

statements is to be written. EXECUTE specifies that a

file is to be created AND that IDCAMS is to be

dynamically invoked.

User response:

None.

BKMB1302I FULL RENAME output dsname: dsname

Explanation:

dsname is the name of the data set into which the

ALTER/NEWNAME IDCAMS statements are written.

User response:

None.

BKMB1303I RENAME data set disposition :

DELETE | KEEP

Explanation:

Disposition of the output data set.

User response:

None.

BKMB1002E • BKMB1303I IBM Confidential


BKMB1304E Open error: ddname

Explanation:


User response:


BKMB1305E Too many old/new mask pairs in

FULLRENAME parm

Explanation:

More than 30 old/new mask pairs was specified in the

FULLRENAMEMASKS parameter.

User response:


BKMB1306E Odd number old/new masks in

FULLRENAME parm

Explanation:

Old/new masks in the FULLRENAMEMASKS parameter

must be entered in pairs.

User response:


BKMB1307E Duplicate old masks in FULLRENAME

parm

Explanation:

An ″Old″ mask occurred more than once in the old/new

mask pairs in the FULLRENAMEMASKS parameter.

User response:


BKMB1308E (Un)allocation failed: xxxx

Explanation:


User response:



Support.

BKMB1310E IDCAMS ended with non-zero return

code

Explanation:

During full rename processing, IDCAMS returned a non

zero return code.

User response:

Check the IDCAMS output for the problem.

BKMB1312E Syntax errors in IDCAMS ALTER

commands

Explanation:

At least one syntax error was generated when building

the control statements for full rename. The IDCAMS

alters were not done.

User response:

Usually caused when trying to add or remove nodes

during rename. Check old/new mask pairs for errors.

Rename was not attempted.

BKMB1313EE New name mask is ambiguous

Explanation:

The use of wild cards in the new name mask is more

limited than in the old name mask. Only one ″**″ wild

card may be used. Partial qualifiers such as ″.*A*.″ or

″.*ABC.″ may not be used.

User response:

Fix the errors and retry the job.

BKMB1314E IDCAMS RENAME not done - errors or

warnings found

Explanation:

The mode was ″EXEC″ but problems were encountered

while resolving the new names.

User response:

Check the messages, fix the problems and retry. If the

file disposition was ″KEEP″, you may edit the file,

correct any problems, then use the file for input to

IDCAMS.

BKMB1315E CSI routine failed :xxxxx

Explanation:

CSI routine failed for reason xxxxx.

User response:


BKMB1316E Unable to find GDG attributes :xxxxx

Explanation:

Full rename was unable to find the GDG base attributes

it needs to define a new GDG base.

User response:

if unable to determine the reason for this failure, call

Technical Support.



Explanation:






User response:



controls execution.

BKMB1318E xxxx: data set already cataloged on

system

Explanation:

A new GDG base name resolved to the name of a data

set that is already cataloged on this system.

User response:

GDG is not renamed. Processing continues.

BKMB1319W INI options missing or invalid:


yyy

Explanation:


User response:



BKMB1320E Severe error when attempting to


yyyy

Explanation:



parmlib.

User response:





member.

BKMB1401E Error returned for BKMA1FD0 - xxxx

Explanation:

An error occurred processing old/new filters.

User response:


BKMB1402E New name mask resulted in duplicate

data set names :xxx

Explanation:

New name mask would cause more than one data set

to be renamed to the same name.

User response:


BKMB1403E Rename error: data set is a GDG

generation

Explanation:

An attempt to rename an active member of a generation

data group and the INI token RENAME_GDGS was set

to N.

User response:

Filter out this data set, set the INI token to Y and retry.

If the file was kept, it may be used for input to IDCAMS.

No ALTER statements were written for this data set.



Explanation:




User response:



controls execution.

BKMB1501E RENAME mask is invalid: xxx

Explanation:

New name mask indicated by xxx is invalid.

User response:


BKMB1599E RENAME mask is invalid: xxx

Explanation:


User response:


BKMB1601E Aggregate name is not a node of

dsname

Explanation:

At least one node of the full rename output data set

must be the aggregate name.

User response:

Change the data set name to include the aggregate

name and rerun the job. You may use the variable

&AGGNAME and the aggregate name will be inserted

into the dsname.

BKMB1602E INI token OUTPUTRENAMEDSN is

invalid

Explanation:

The INI value does not adhere to coding rules.

User response:

Correct the error and try again.





Explanation:




User response:



Explanation:


xxxxxxxx is the program name.

User response:



controls execution.

BKMB1703E BAEV record not found in IDS: xxx

Explanation:

Required IDS record is missing. Possible IDS

corruption.

User response:




Explanation:




User response:



Explanation:



User response:



controls execution.


Explanation:


corruption.

User response:


BKMB2031E DAD command request not recognized

Explanation:

An internal error has occurred.

User response:


BKMB2080E Error fetching //SISPARM info, R15=xx

Explanation:


DADSMFTK was unable to process the information from


User response:


BKMB2090E Error fetching ″LOG″ token. R15=xx

Explanation:


DADSMFTK was unable to process the LOG token from


User response:


DADSMFTK.

BKMB2091E Error with value of ″LOG″ token.

Explanation:




value.

User response:


DADSMFTK.

BKMB2092E Error with len value of ″LOG″ token.

Explanation:




value. It should be a DSN, which has a maximum length

of 44 characters.

User response:


DADSMFTK.

BKMB2093E Cannot determine this DADSMFTKs

SYSLOG

Explanation:



//SISPARM JCL statement, but was unable to determine

the name of its LOG DSN.



User response:


DADSMFTK.

BKMB2096E Allocation of //DADLOG failed: R15=xx,

INFO=ddddddddd

Explanation:



//SISPARM JCL statement, but MVS declared the DSN

invalid.

User response:


DADSMFTK.

BKMB2097E LOG DSN value is null

Explanation:

During DADSMFTK startup, DADSMFTK determined

that the LOG DSN was ″null″ meaning that it was

invalid during INI value processing, or, was never

specified in the INI values. This value is described in

the ″DADSMFTK_OPTIONS″ section of the //SISPARM

member.

User response:


DADSMFTK.

BKMB2115W U83 exit not active for SYSID.

Explanation:

DADSMFTK is not running or a problem was


User response:



analyst.

BKMB2116W DAD database update task not active

for SYSID.

Explanation:



User response:






errors, the message ASP01010E abnormal termination

of DAD9254S will appear in the log along with other

messages identifying the precise reason for the

abnormal termination.

BKMB2117W DAD database update task is doing

no work for SYSID

Explanation:



User response:


check for other messages from the read task

(DAD9254S). That might indicate the nature of the



whether this is critical is up to the application analyst.

BKMB2118W No response from DAD database

update task for SYSID

Explanation:

The task which writes SMF records to the database


User response:



(DAD9254S) That might indicate the nature of the




BKMB2119E Application not found in DAD

database.

Explanation:



User response:

Check that the applname in the parm is correct or that

the application has indeed been created.

BKMB2120I APPLEND started for application.

Explanation:

Informational only.

User response:

None.

BKMB2121I Cycle number increased for

application.

Explanation:

The DAD cycle number for this cycle’s worth of SMF


User response:

None required.



BKMB2122I Buffer flush requested for application.

Explanation:



User response:

None required.

BKMB2123I Buffer flush acknowledge for

application.

Explanation:


User response:

None required.

BKMB2124I Buffer flush satisfied for application.

Explanation:


User response:

None required.

BKMB2128E Free of ddname DADMSGQ failed

Explanation:

SVC99 failure.

User response:

Note SVC99 failure code. If not solvable, contact

Technical Support.

BKMB2129E BKMSTSKD not active

Explanation:


User response:

BKMSTSKD must be active on the image running the


BKMB2130E NAMETOKEN fetch failed.

Explanation:


User response:


BKMB2131E Failure allocating ddname DADMSGQ

to data set.

Explanation:

SVC99 FAILURE.

User response:

See SVC99 reason code. The problem is likely user

solvable.

BKMB2132E DAD msg queue no formatted

correctly. Expected DADMSG in 1st 16

slots.

Explanation:


User response:

Check that JCL member DADMQBLD has been run.

BKMB2300E Exit area exists..must unload first

Explanation:

Correctable error.

User response:

Stop the DADSMFTK task using STOPALL and restart

using AUTOSTART.

BKMB2301E Cannot open EXITLIB

Explanation:

Correctable error.

User response:

Make sure the DSN is correct for each load library in

the INI parmlib member.

BKMB2302E X-CSA storage not available

Explanation:

Correctable error.

User response:

Increase the region size of the DADSMFTK job.

BKMB2303I X-CSA located at: nnnnnnnn length:

nnnnnnnn

Explanation:


User response:

None.

BKMB2304E Unable to load primary exit. Load

RC=nnn reason=xx

Explanation:


User response:


Technical Support.

BKMB2305E Name token creation failed. IEANTCR

RC=nn

Explanation:

Internal error.

User response:


Technical Support.

BKMB2122I • BKMB2305EIBM Confidential


BKMB2306E X-CSA built and identified

Explanation:


User response:

None.

BKMB2307E Unable to load secondary exit. Load

RC=nn

Explanation:


User response:


Technical Support.

BKMB2308I Secondary exit loaded successfully

Explanation:


User response:

None.

BKMB2309E Exit area does not exist

Explanation:


User response:


Technical Support.

BKMB2310E Unable to free X-CSA. FREEMAIN

RC=nn

Explanation:

Internal error.

User response:


Technical Support.

BKMB2311I Exit area removed

Explanation:


User response:

None.

BKMB2312E Cannot remove exit with dataspace

active

Explanation:

Correctable error.

User response:


command.

BKMB2313E Cannot turn on exit without dataspace

active

Explanation:

Correctable error.

User response:



BKMB2314E Secondary exit already active

Explanation:

Correctable error.

User response:



BKMB2315I Secondary exit active

Explanation:


User response:

None.

BKMB2316E Secondary exit not active

Explanation:

Correctable error.

User response:



BKMB2317I Secondary exit deactivated

Explanation:


User response:

None.

BKMB2318I Secondary exit active data space

exists VSAM subtask running

Explanation:


User response:

None.

BKMB2319I Cannot load new secondary exit while

existing exit is turned on

Explanation:

Correctable error.

User response:





BKMB2320I Secondary exit reloaded successfully

Explanation:


User response:

None.

BKMB2321E SMF xxxxxxxxxxx complete for:

xxxxxxxxxxxxxxxx

Explanation:


User response:

None.

BKMB2322E SMF dynamic exit facility xxxxxx RC=nn

reason=xxxx

Explanation:

Internal error.

User response:


Technical Support.

BKMB2326E Cannot xxxxxx exit; no exits defined to

MVS

Explanation:

Correctable error.

User response:


this error.

BKMB2327I There were xxxx exits deleted than

installed

Explanation:

Correctable error.

User response:


this error.

BKMB2338E Token ″LOAD ″ DSN xxxxxxxxxxxx

request failed; R15=nn SVC 99 data:

xxxxxxxx

Explanation:

Internal error.

User response:


Technical Support.

BKMB2339E ddname xxxxxxxxxxxxxxx request failed;

R15=nn SVC 99 data: xxxxxxxx

Explanation:

Internal error.

User response:


Technical Support.

BKMB2340E DAD DSN xxxxxxxxxxxx request failed;

R15=nn SVC 99 data: xxxxxxxx

Explanation:

Correctable error.

User response:

Ensure the DAD data set name has been entered in INI

and the name is spelled correctly.

BKMB2342E DADESTAE load module query failed.

RC=nn

Explanation:

Internal error.

User response:


Technical Support.

BKMB2343E Unable to load DADESATE/SECONDARY exit. Load RC=nnn

reason=nn

Explanation:

Internal error.

User response:


Technical Support.

BKMB2344E Error on initial open of DAD database

Explanation:

Correctable error.

User response:


this error.

BKMB2400E Unable to make non swapable.

SYSEVENT RC=nn

Explanation:

Internal error.

User response:


Technical Support.

BKMB2320I • BKMB2400EIBM Confidential


BKMB2401E Unable to xxxxxxx dataspace.

DSPSERV RC=xx

Explanation:

Correctable error.

User response:


ALE-DYN for a discussion of DSPSERV errors.

BKMB2402E Unable to xxxxxxx ALET. ALESERV

RC=xx

Explanation:

Correctable error.

User response:


ALE-DYN for a discussion of ALET errors.

BKMB2403E Dataspace created buf count z,zzz,zzz

origin xxxxxxxx size z,zzz,zzzk

Explanation:


User response:

None.

BKMB2404I Data space removed

Explanation:


User response:

None.

BKMB2405E Must install exit before manipulating

dataspace

Explanation:

Correctable error.

User response:


be installed first.

BKMB2406E Dataspace already exists

Explanation:

Correctable error.

User response:


recreate it.

BKMB2407E Data space does not exist

Explanation:


User response:

None.

BKMB2408E Cannot delete data space with exit

turned on

Explanation:

Correctable error.

User response:


be turned off.

BKMB2409I Buffer value not valid, using default

Explanation:


User response:

None.

BKMB2410I Buffer value excessive. Using 32MB of

buffers

Explanation:


User response:

None.

BKMB2411I Internal dataspace ID is bad; resetting

internal ID

Explanation:


User response:

None.

BKMB2520E Read DAD database subtask exists.

Explanation:

Correctable error.

User response:



BKMB2521E Read DAD database subtask failed to

start. RC=nn

Explanation:

Internal error.

User response:


Technical Support.

BKMB2522I Read DAD database subtask started;


Explanation:


User response:

None.



BKMB2523E Must load exit area before starting

subtask

Explanation:

Correctable error.

User response:



BKMB2524E Internal dataspace ID is bad. Need

valid ID.

Explanation:

Internal error.

User response:


Technical Support.

BKMB2525E Must create dataspace before starting

subtask

Explanation:

Correctable error.

User response:



BKMB2530E Read DAD database subtask does not

exist.

Explanation:


normally.

User response:

None.

BKMB2531E Read DAD database subtask not

responding.

Explanation:


normally.

User response:

None.

BKMB2532I Read DAD database subtask stopped.

Explanation:


User response:

None.

BKMB2533E Read DAD database subtask

destroyed.

Explanation:


User response:

None.

BKMB2539E DAD DSN value is null

Explanation:

No value for DAD database DSN.

User response:

Update INI with valid DAD database DSN.

BKMB2540E Update DAD database subtask exists.

Explanation:

Correctable error.

User response:



BKMB2541E Update DAD database subtask failed to

start. RC=nn

Explanation:

Internal error.

User response:


Technical Support.

BKMB2542I Update DAD database subtask started;


Explanation:


User response:

None.

BKMB2543E Must load exit area before starting

subtask

Explanation:

Correctable error.

User response:



BKMB2544E Internal dataspace ID is bad. Need

valid ID.

Explanation:

Internal error.

User response:


Technical Support.



BKMB2545E Must create dataspace before starting

subtask

Explanation:

Correctable error.

User response:



BKMB2550E Update DAD database subtask does

not exist.

Explanation:


normally.

User response:

None.

BKMB2551E Update DAD database subtask not

responding.

Explanation:


normally.

User response:

None.

BKMB2552I Update DAD database subtask

stopped.

Explanation:


User response:

None.

BKMB2553E Update DAD database subtask

destroyed.

Explanation:


User response:

None.

BKMB2560E DAD monitor command subtask not

responding.

Explanation:


normally.

User response:

None.

BKMB2561I DAD monitor command subtask

stopped.

Explanation:


User response:

None.

BKMB2562E DAD monitor command subtask

destroyed.

Explanation:


User response:

None.

BKMB2563E DAD monitor command subtask exists.

Explanation:

Correctable error.

User response:



BKMB2564E DAD monitor command subtask failed

to start. RC=nn

Explanation:

Internal error.

User response:


Technical Support.

BKMB2565E Overflow export subtask exists.

Explanation:

Correctable error.

User response:



BKMB2566E Overflow export subtask not

responding.

Explanation:


normally.

User response:

None.

BKMB2567I Overflow export subtask stopped.

Explanation:


User response:

None.



BKM2568E Overflow export subtask destroyed.

Explanation:


User response:

None.

BKMB2569E Overflow export subtask does not

exist.

Explanation:


normally.

User response:

None.

BKMB2570E Overflow export subtask failed to start.

RC=nn

Explanation:

Internal error.

User response:


Technical Support.

BKMB2571E Overflow import subtask exists.

Explanation:

Correctable error.

User response:



BKMB2572E Overflow import subtask not

responding.

Explanation:


normally.

User response:

None.

BKMB2573I Overflow import subtask stopped.

Explanation:

Informational message

User response:

None.

BKMB2574E Overflow import subtask destroyed.

Explanation:


User response:

None.

BKMB2575E Overflow import subtask does not

exist.

Explanation:


normally.

User response:

None.

BKMB2576E Overflow import subtask failed to start.

RC=nn

Explanation:

Internal error.

User response:


Technical Support.

BKMB2577I Overflow import subtask started.

Explanation:


User response:

None.

BKMB2578I Overflow export subtask started.

Explanation:


User response:

None.

BKMB2579I DAD monitor command subtask

started.

Explanation:


User response:

None.

BKMB2600E Shut down complete

Explanation:


User response:

None.

BKMB2601E Errors occurred during shut down.

Explanation:

Unexpected events caused shut down errors.

User response:

See other messages.

BKM2568E • BKMB2601EIBM Confidential


BKMB2602E Autostart complete

Explanation:


User response:

None.

BKMB2603E Errors occurred during autostart.

Explanation:

Unexpected events caused autostart to fail.

User response:

See other messages.

BKMB2610I Error xxxxxxxxxxxx info from

//SISPARM. R15=nnnn

Explanation:

Correctable error.

User response:

Incorrect or missing data in INI. Correct errors and

restart the DADSMFTK task.

BKMB2612E Overflow DSN not found for SYSID

Explanation:

Correctable error.

User response:

Incorrect or missing data in INI. Each SYSID must have

its own overflow data set.

BKMB2613E Too many overflow file allocation


Explanation:

Correctable error.

User response:

Reduce the allocation parms in the

OVERFLOW_PARMS token.

BKMB2614E Substitution error on INI VARIABLES.

Output less than 92 bytes.

Explanation:

Internal error.

User response:


Technical Support.

BKMB2615E Syntax error for OVERFLOW_DSN

PARM xxxxxxxxxxxxxxxx

Explanation:

Correctable error.

User response:

Correct errors in OVERFLOW_PARMS.

BKMB2701E Unexpected return code (nn) from xxx

IEANT xx

Explanation:

Internal error.

User response:


Technical Support.

BKMB2704E QEDIT nonzero return code. xxxxxxxx

RC=nn

Explanation:

Internal error.

User response:


Technical Support.

BKMB2705E Cannot get message system lock

Explanation:

Internal error.

User response:


Technical Support.

BKMB2706E Cannot execute unauthorized

Explanation:

Correctable error.

User response:

The DADSMFTK module must be in an authorized

library.

BKMB2707E Another DADSMFTK is executing. It

was started yyyy/mm/dd at hh:ss:mm

Explanation:

Correctable error.

User response:

Only one DADSMFTK task can run on an image.

BKMB2712E DADSMFTK: build &SYSDATC

&SYSTIME

Explanation:


User response:

None required.

BKMB2715E Message queue open failed.

Explanation:

Correctable error.

User response:




BKMB2715E Message queue allocate failed.

Explanation:

Correctable error.

User response:


BKMB2718E All DAD slots filled in message queue

Explanation:

Correctable error.

User response:

The DADSMFTK task can be started on a maximum of

16 images. Make sure that SYSIDS no longer in use

are deleted from the message queue data set.

BKMB2719E Message queue data set not formatted

Explanation:

Correctable error.

User response:

The message queue setup job DEF#MSGQ must run

successfully before DADSMFTK job can be started.

BKMB2720E Message queue deallocate failed.

Explanation:

Correctable error.

User response:


BKMB2721E Overflow allocate failed.

Explanation:

Correctable error.

User response:


BKMB2722E Overflow deallocate failed.

Explanation:

Correctable error.

User response:


BKMB2725E xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Explanation:

Correctable error.

User response:

This message gives the details of an allocate error.

Correct the error and restart DAD.

BKMB2727E Overflow open failed.

Explanation:

Correctable error.

User response:


BKMB2728E Startup failed due to parmlib INI error

Explanation:

Internal error.

User response:


Technical Support.

BKMB2729E INI token not found. Token =

xxxxxxxxxxxxxxxx

Explanation:

Correctable error.

User response:

Review INI. The token name may have been changed

or a line may have been deleted.

BKMB2730E INI fetch of token failed RC= nnn token

= xxxxxxxxxxxxxxxxx

Explanation:

Correctable error.

User response:

Review INI for token and token value syntax errors.

BKMB2731E Cannot find matching SYSID for token:

xxxxxxxxxxxxxxxx

Explanation:

Correctable error.

User response:

Review INI. The correct values are listed by SYSID.

BKMB2732E Token syntax error token =

xxxxxxxxxxxxxxxxx

Explanation:

Correctable error.

User response:

Review INI. The token value is not in the format

expected.

BKMB2733E Dsn longer than 44 characters token =

xxxxxxxxxxxxxxxx

Explanation:

Correctable error.

User response:

Review INI. The token value should be a DSN.



BKMB2734E Log DSN not valid

Explanation:

Correctable error.

User response:

Review INI. The value for the log token must be a valid

DSN.

BKMB2736E Message log allocate failed.

Explanation:

Correctable error.

User response:


BKMB2737E Message log deallocate failed.

Explanation:

Correctable error.

User response:


BKMB2901E Unexpected return code (nn) from xxx

IEANT xx

Explanation:

Internal error.

User response:


Technical Support.

BKMB2904E Abnormal termination of DADDBUPD

Explanation:

DAD update task did not shut down normally.

User response:

This is critical error. Other error messages should give

more details of the problem. Please report these

messages with the text issued to Technical Support.

BKMB3201E Unexpected return code (nnn) from uuu

IEANTPP

Explanation:






User response:


BKMB3202E Allocate of overflow data set failed

Explanation:


User response:


allocation failure.

BKMB3203E Open of overflow data set failed.

Explanation:


User response:




BKMB3204W Overflow data set is not available

Explanation:

The overflow data set is in use by the import task.

User response:

None required.

BKMB3205E Deallocate of overflow data set failed.

Explanation:


User response:


deallocation failure. The DAD shutdown will continue.

BKMB3206W Overflow data set is full. SMF data

may be lost.

Explanation:

Since the overflow data set is full, SMF data that cannot

be added to the dataspace buffers will be lost.

User response:

None required.

BKMB3207E DAD status update failed.

Explanation:


User response:


BKMB3208E xxxxxxxxxxxxxxxxxxxxxxxxxxx


Explanation:


User response:




BKMB3209I Waiting for overflow

Explanation:


User response:

None required.

BKMB3301E Unexpected return code (nnn) from uuu

IEANTPP

Explanation:






User response:


BKMB3302E Allocate of overflow data set failed

Explanation:


User response:


allocation failure.

BKMB3303E Open of overflow data set failed.

Explanation:


User response:




BKMB3305E Deallocate of overflow data set failed.

Explanation:


User response:


deallocation failure. The DAD shutdown will continue.

BKMB3307E Output open of overflow data set

failed.

Explanation:

All the overflow records have been reloaded to the

buffers, but an open for output needs to be done to

empty the overflow data set.

User response:




BKMB3308E Overflow export stop failed.

Explanation:



export task.

User response:





BKMB3309E Overflow export start failed.

Explanation:



export task.

User response:





BKMB3310E DAD status update failed.

Explanation:


User response:


BKMB3311E xxxxxxxxxxxxxxxxxxxxxxxxxxxx

xxxxxxxxxxxxxxxxxxxxxxxxxxxx

Explanation:


User response:


BKMB3312I Waiting for overflow

Explanation:


User response:

None required.

BKMB3313I Overflow records reloaded nnnnn

Explanation:

Number of overflow records reloaded to dataspace

buffers.

User response:

None required.

BKMB3209I • BKMB3313IIBM Confidential


BKMB3401E DSN parm not passed

Explanation:


User response:




Explanation:


User response:




Explanation:


User response:



BKMB3404E FROM date invalid

Explanation:


User response:


YYYY/MM/DD. If the problem persists, contact Technical

Support.

BKMB3405E TO date invalid

Explanation:


User response:



Support.


Explanation:


User response:




Explanation:


User response:



BKMB3408E Number of days missing/invalid

Explanation:



User response:



BKM3409E Error running date calc routine

Explanation:


User response:


Support.


Explanation:


none were found.

User response:




Explanation:


an error occurred

User response:


Support.


Explanation:


no data set detail records were found

User response:






Explanation:


an error occurred

User response:


Support.




Explanation:


User response:



BKMB3415E FROM time invalid

Explanation:

FROM time passed was not a valid time.

User response:



BKMB3416E TO time invalid

Explanation:

TO time passed was not a valid time.

User response:



BKMB3501E EVENT parm not passed

Explanation:


User response:




Explanation:


User response:




Explanation:


User response:




Explanation:


User response:



Support.


Explanation:


User response:



Support.

BKMB3506E No space format passed

Explanation:


User response:




Explanation:


User response:




Explanation:



User response:



BKMB3509E Error running date calc routine

Explanation:


User response:


Support.


Explanation:

When reading the database for backup event records,

none were found.

User response:




Explanation:


an error occurred.

User response:




Support.

BKMB3512E No event detail records found

Explanation:



User response:





BKMB3513E Error reading event detail records

Explanation:


an error occurred.

User response:


Support.

BKMB3514E Invalid event name passed

Explanation:


User response:




Explanation:


exist.

User response:




Explanation:




User response:

None.

BKMB3601E EVENT parm not passed

Explanation:


User response:




Explanation:


User response:




Explanation:


User response:




Explanation:


User response:



Support.


Explanation:


User response:



Support.


Explanation:


exist.

User response:




Explanation:



User response:





BKMB3609E Error running date calc routine

Explanation:


User response:


Support.

BKM3610E No backup events records found

Explanation:

When reading the database for backup event records,

none were found.

User response:



BKM3611E Error reading backup event records

Explanation:


an error occurred.

User response:


Support.

BKM3614E Invalid event name passed

Explanation:


User response:




Explanation:




User response:

None.

BKMB3701E PGM name parm required

Explanation:

No program name was passed to BKMBMAIN in the

JCL.

User response:

Correct the JCL and try again. If the problem persists,


BKMB3702E Authorization failed RC = nnnnnnnn

Explanation:

ABARS Manager must be run from an authorized

library.

User response:

Authorize the ABARS Manager library and do not

concatenate any non-authorized libraries in the JOBLIB

or STEPLIB concatenation.

BKMB3703E Failed load of: module-name Load RC:

nnnnnnnn

Explanation:


User response:




BKMB3704E SI27 point fail, RC = nnnnnnnn

Explanation:


User response:


BKMB3705E SI27 GETN fail, RC = nnnnnnnn

Explanation:


User response:


BKMB3801E DAD failure - U83 exit has abended

Explanation:

The U83 exit has abended, and the DADESTAE module

will try to shut it down.

User response:


Technical Support.

BKMB3802I U83 exit dormant

Explanation:

The U83 EXIT abended, and the EXIT has been shut

down.

User response:

None.

BKMB3901E Parm check failed

Explanation:

Parameters passed for aggregate update where invalid.

User response:

Verify parameters are correct and submit JCL again.



BKMB3902E AGG parm not passed

Explanation:

AGG parameter not specified or is invalid.

User response:


BKMB3903E Bad backup gen passed

Explanation:

BACKUP_GEN_GRPS_TO_RETAIN value not between

1 and 9999.

User response:


BKMB3904E Bad recovery gen passed

Explanation:

RECOVERY_GEN_TO_RETAIN value not between 1

and 9999.

User response:


BKMB3905E Error getting SMS info

Explanation:

CALL to SMS failed.

User response:


Support.

BKMB3907E Bad mask specified

Explanation:

AGG parameter contains an incorrect mask.

User response:


BKMB3909E Error opening IDS

Explanation:

An error occurred opening the IDS.

User response:


Support.

BKMB3910E Error during VREADUPD

Explanation:

An error occurred perform while trying to read a record.

User response:


Support.

BKMB3911E Error closing IDS

Explanation:

An error occurred closing the IDS.

User response:


Support.

BKMB3912E Aggregate has been added

Explanation:


aggregate was found in SMS but not in the IDS so it

was added.

User response:

None.

BKMB3913E Error writing to IDS

Explanation:

An error occurred writing to the IDS.

User response:


Support.

BKMB3914E WRITE failed, duplicate record found

Explanation:

An attempt was made to add a record that already

existed.

User response:


Support.

BKMB3915E WRITE failed, no space in database

Explanation:

An attempt was made to write a record but the

database is full.

User response:

Increase the size of the IDS and try again.

BKMB3917I Aggregate has been updated in IDS

Explanation:


aggregate was found in the IDS and updated.

User response:

None.

BKMB3918E Error in override switches: xxxxx

Explanation:

Override switches contain invalid combinations.

User response:




BKMB3919E Error initializing AGM record

Explanation:

An attempt was made to initialize the aggregate master

record and failed.

User response:


Support.

BKMB3920E ISFM version must be 9999 or NOLIMIT

for aggregate

Explanation:

Aggregate option was set to INCR(Y|N) and aggregate

found matching name or mask was not identified in

SMS with a backup retain value of 9999 or NOLIMIT

User response:

None.

BKMB3921I Aggregate has been added to IDS

Explanation:

Aggregate was not found in the IDS but was added with

the values specified.

User response:

None.

BKMB3922I Aggregate has been updated in IDS

Explanation:

Aggregate was found in the IDS and was updated with

the values specified.

User response:

None.

BKMB3923E INCR parm invalid - incremental not

licensed

Explanation:

INCR parm is invalid since Incremental is not licensed.

User response:

None required.

BKMB4101E APPL parm not passed

Explanation:

From program to program the APPL name was not

passed.

User response:



BKMB4103E No records found for APPL specified

Explanation:

No data sets were found for the Backup-end application

name specified.

User response:

Verify that the Backup-end process ran successfully

then try running this report again. If the problem


BKMB4104E Tape VOLSER not found

Explanation:

The tape VOLSER for the output data set was not

found to be cataloged.

User response:



BKMB4105E Internal error occurred

Explanation:

The report failed due to an internal error.

User response:



BKMB4106E No tape sub-system found

Explanation:

When gathering tape information on a data set no tape

sub-system was found.

User response:



BKMB4107E Undefined RC value from MSTPSSFU

Explanation:

When gathering tape information on a data set an

unknown error occurred running the tape-management

interface.

User response:



BKMB4108E TLMSVMP DD not allocated - skipping

location check

Explanation:

The TLMS Tape System was detected and the

TLMSVMP DD was not found in the executing JCL.

User response:

Add the TLMSVMP DD to the JCL point to the TLMS

database and run report again. If the problem persists,




BKMB4109E TLMSVMF is NULLFILE - skipping

location check

Explanation:

The TLMS Tape System was detected but the data set

identified on the TLMSVMF DD was NULLFILE.

User response:

Specify the name of the TLMS database on the

TLMSVMF DD and run report again. If the problem


BKMB4401E APPL parm not passed

Explanation:

APPL parm expected and was not passed.

User response:

Pass APPL parm and try again. If the problem persists,


BKMB4402E Bad cycle passed

Explanation:

A cycle number from 0 to 9999 was not passed.

User response:

Pass a cycle number between 0 and 9999. If the


BKMB4403E No records found for APPL specified

Explanation:

Using the application specified, no records were found.

User response:

Verify that the application specified has DSR records

available and try again. If the problem persists, contact

Technical Support.

BKMB4501E No APPL parm passed

Explanation:

An APPL parm was expected and was not passed.

User response:

Pass an APPL parm and try executing again. If the


BKMB4502E No application records found

Explanation:

When reading the database for application records,

none were found.

User response:





Explanation:




User response:



Explanation:



User response:



controls execution.


Explanation:


corruption.

User response:




Explanation:




User response:



Explanation:



User response:



controls execution.


Explanation:


corruption.

User response:




BKMBRR00E Missing ddname: xxxxxxxx

Explanation:

BKM01BRR requires DDNames QSAM and VSAM.

QSAM is for the backed-up data, VSAM is the object

being backed-up.

User response:

Ensure the JCL matches the documentation.

BKMBRR01E SVC99 failed for ddname: xxxxxxxx

Explanation:

BKM01BRR issues SVC99 to determine the STATUS

and DISPOSITION of the input and output objects.

SVC99 failed.

User response:


BKMBRR02E Invalid status for ddname: xxxxxxxx

Explanation:

BKM01BRR requires specific DISP=(xxx,xxx) DD

sub-parameter values. The VSAM DD must have

DISP=SHR, the QSAM DD must be one of the

following: DISP=(NEW,CATLG),DISP=(OLD,PASS), or

DISP=(OLD,KEEP,KEEP). You can implicitly or explicitly

code these values.

User response:

Ensure the JCL matches the documentation.

BKMBRR03E IGGCSI00 non-zero RC. Processing:

xxxxx.xxxx.xxxx

Explanation:

BKM01BRR uses the Catalog Search Interface to

determine the attributes of the VSAM object. A failure

occurred in CSI.

User response:


BKMBRR04E IGGCSI00 no entries / associations

found. Processing: xxx

Explanation:

BKM01BRR uses the Catalog Search Interface to

determine the attributes of the VSAM object. Either the

VSAM object was not cataloged, or did not have any

components - Index or Data.

User response:

Ensure the JCL specifies a valid dsname for the VSAM

object.

BKMBRR05E VSAM object not REUSE:

xxxxx.xxxx.xxxx

Explanation:

BKM01BRR requires that the VSAM object have an

attribute of REUSE.

User response:

Use the IDCAMS ALTER command to modify the

object’s attributes to REUSE. This may not be done if

the object uses keyranges or has an associated

alternate index. This will now comply with the

documentation.

BKMBRR06E VSAM object not SHR(2 3):

xxxxx.xxxx.xxxx

Explanation:


attribute of Shareoptions(2 3) - multiple read, single

update.

User response:

Use the IDCAMS ALTER command to modify the

object’s share option attribute. This must be performed

at the component level; change both Index and Data

components to the same value. This will now comply

with the documentation.

BKMBRR07E VSAM object not KSDS:

xxxxx.xxxx.xxxx

Explanation:


attribute of Indexed.

User response:

Ensure that the JCL specifies a valid VSAM KSDS to be

processed. This will now comply with the

documentation.

BKMBRR08E Invalid job-step parameter: xxxxxxxx

Explanation:

BKM01BRR requires that the job-step parameter in the

JCL specify one of the following values: REORG (the

default if no parameter is specified), BACKUP or

RELOAD.

User response:


processed. This will now comply with the

documentation.

BKMBRR09E Open error for ddname: xxxxxxxx

Explanation:

BKM01BRR attempted to open the specific ddname, but

failed.

User response:


BKMBRR10E Empty object: xxxxx.xxxx.xxxx

Explanation:

BKM01BRR requires that the input VSAM object have

at least one record.

User response:

BKMBRR00E • BKMBRR10EIBM Confidential



processed.

BKMBRR11E GET failure: xxxxx.xxxx.xxxx

Explanation:

BKM01BRR attempted to read a record from the

specific DSName, but failed.

User response:


BKMBRR12I Secondary allocation or new volume

required. Duplicate key created in

alternate index. Write buffer suggested.

Sequence set record capacity

exceeded. No buffer writes performed.

Control interval split indicator detected

mark buffer invalid.

Explanation:

These are informational messages that might be

displayed during the reload.

User response:

They are all informational.

BKMBRR13E RPL active for other request.DSN:

xxxxx.xxxx.xxxx

Explanation:

A logic error occurred causing the RPL to be referenced

concurrently during the reload.

User response:


BKMBRR14E PUT logical error DSN:

xxxxx.xxxx.xxxx

Explanation:

When attempting to write a record back to the VSAM

object a logical error occurred.

User response:


BKMBRR15E PUT physical error. DSN:

xxxxx.xxxx.xxxx

Explanation:

The put failed to write the record to the VSAM object, a

physical error occurred.

User response:


BKMBRR16E ENQ failed: enq_minor_name

Explanation:

BKM01BRR attempts to lock the VSAM file to be

prevent concurrent access by update users. The ENQ

request failed.

User response:


BKMBRR17E Error processing parmlib INI member.

Explanation:

BKM01BRR uses the INI member to provide information

about the ″Lock DSN″. This lock file is used to prevent

access to the VSAM object in the event of a reorg

failure. Validate the entries in the SI040_VALUES

section against the documentation.

User response:


BKMBRR18E Error parsing INI data.

Explanation:

BKM01BRR uses the INI member to provide information

about the ″Lock DSN″. This lock file is used to prevent

access to the VSAM object in the event of a reorg

failure. Validate the entries in the SI040_VALUES

section against the documentation.

User response:


BKMBRR19E Lock DSN free / allocation failed:

xxxx.xxxx.xxxx

Explanation:

BKM01BRR will, at the start of a REORG process, free

the ″Lock DSN″ with a DISP=(OLD,DELETE)

specification, and then allocate the data set. On

successful conclusion, the ″Lock DSN″ is deleted.

These processes use SVC99. There was a failure.

User response:


BKMBRR20I Backup/reorg starting

Explanation:

The date and timestamp at which the backup process

started.

User response:

None required.

BKMBRR21I Backup completed. Records: nnnn

Explanation:

The number of records read by the backup process.

User response:

None required.

BKMBRR22I Reload starting

Explanation:

The date and timestamps at which the reload process

started.

BKMBRR11E • BKMBRR22I IBM Confidential


User response:

None required.

BKMBRR23I Reload/reorg completed. records: nnnn

Explanation:

The date and timestamps at which the reload process

completed.

User response:

None required.

BKMBRR24E INI token not found

Explanation:

BKM01BRR requires that the input INI file have a

section SI040_VALUES. This section was not found.

User response:

Specify the correct INI file.

BKMBRR25E Invalid RECFM for QSAM file

Explanation:

BKM01BRR requires that the QSAM (flat) file have a

RECFM attribute indicating either F(ixed) or V(ariable).

A RECFM value of U(ndefined) is invalid.

User response:

Specify a RECFM value of VBS or FBS, as appropriate.

BKMBRR26E LOCKDSN and VSAM DSNAME are

the same

Explanation:

BKM01BRR found that the LOCKDSN parameter in the

INI specifies the data set that is being processed.

User response:

Specify a different LOCKDSN and retry.

BKMBRR27I BKM01BRR maintenance level

Explanation:

Informational data on the version of this module.

User response:

Provide to Technical Support if asked.

BKMBRR23I • BKMBRR27IIBM Confidential


IBM Confidential



Messages (BKMC)

BKMCA101E No INIT function received.

Explanation:


User response:


BKMCA102E INIT function received without

intervening term

Explanation:


User response:


BKMCA103E Unknown function: xxxx

Explanation:


User response:


BKMCA104E Error calling BKM01VV1 xxxx R15=rc

R0=rea ID=nn

Explanation:


User response:


BKMCA105E MLA value found greater than 4

Explanation:


User response:


BKMCA106E Mask failed evaluation check: xxxx

Explanation:

Mask xxxx is invalid.

User response:

Fix the error and retry the function.

BKMCA107E CSI failed when calling for master

catalog name

Explanation:


User response:


BKMCA108E Mask failed evaluation check: xxxx -

yyyyy

Explanation:

Mask xxxx is invalid for reason yyyyy

User response:


BKMCA109E Un-allocation failed for:cccc

Explanation:

Un-allocation failed for catalog cccc.

User response:

Determine the reason for and fix the problem, Retry the

function.

BKMCA110E Allocation failed for: cccc

Explanation:

Allocation failed for catalog cccc.

User response:

Determine the reason for the allocation failure and retry.

BKMCA111E UCBLOOK error for: vvvv - Return

code: rc Reason code: rsn

Explanation:


User response:


BKMCA112E Volume not mounted: vvvv DSN: nnn

Devtype: ttt

Explanation:

A catalog entry specified that a data set was cataloged

to a volume, vvvv, that was not mounted for data set

name nnn on device type ttt.

User response:

Mount the volume, uncatalog the data set, or re-specify

the selection masks. Retry the function.

BKMCA113E IOSCAPU ERROR FOR: vvvv - Return

code: rc Reason code: rsn

Explanation:


User response:


BKMCA114E nnnn : VOLSER=vvvv

RC=rrr,REAS=sss,DESC=zzzz

IBM Confidential

103

Explanation:

An error occurred when trying to access the VVDS on

volume vvvv for data set nnnn . rrr = Returncode. sss =

Reason code. zzzz = description when available.

User response:

If unable to determine the cause of the error or to fix it,


BKMCA115E UCBPIN error for: vvvv - Return code:

rc Reason code: rsn

Explanation:


User response:


BKMCA116E CVAF ERROR: Return code: rc Status

code: sc Volume: vvvv ID=nn Prev

Func:ffff

Explanation:


User response:


BKMCA117E Error obtaining VTOC data from vvvv :

nnnn

Explanation:

An error occurred when trying to access the VTOC on

volume vvvv for data set nnnn.

User response:



BKMCA118E HSM MCVT not found

Explanation:

An error occurred when trying to access the HSM

control blocks. The most probable cause is HSM has

not been started.

User response:



BKMCA119E HSM data extract ended with errors

Explanation:



not been started.

User response:



BKMCA120E MIgrated data set not found in MCDS:

nnnn

Explanation:

The catalog indicated that data set nnnn was migrated,

but no entry was found in the HSM MCDS.

User response:



BKMCA121W No catalog entries found for mask(s)

Explanation:

No catalog entries were found for any of the masks

passed to BKM01VE1.

User response:

If this result was not expected, try to determine the

reason for the problem and retry the function. If help is

needed, contact Technical Support for assistance.

BKMCA122E Associated entry not found in catalog

- nnnn

Explanation:

A non-VSAM alias entry with an association of nnnn

was not found in the catalog. The most probable cause

is an orphaned catalog entry.

User response:

Determine the reason for and fix the problem. Retry the

function. If help is needed, contact Technical Support for

assistance.

BKMCA123E Unexpected catalog record construct

- association cell not where expected

Explanation:

Catalog entry for entry mentioned above is invalid.

User response:



assistance.

BKMCA124E Type ″J″ record with no matching ″B″

record: nnnn

Explanation:

Catalog entry nnnn is an extension record for a catalog

record that does not exist.

User response:



assistance.

BKMCA115E • BKMCA124E IBM Confidential


BKMCA125E Error reading self describing record

from catalog: nnnn

Explanation:


User response:


BKMCA126E Received a ″GET″ Request before

receiving a mask

Explanation:


User response:


BKMCA127E Input control block is not compatible

Explanation:


User response:


BKMCA129E HSM is not active - unable to retrieve

requested data

Explanation:

HSM must be active for MCDS data to be retrieved.

User response:

Start HSM and retry the function.

BKMCA130I Allocation failed for: nnnn - Will not be

used for search

Explanation:

Unable to allocate catalog nnnn. No entries that may

reside in this catalog will be retrieved.

User response:

Informational only. Processing continues.

BKMCA131E Volume not mounted: vvvv DSN=nnn

Devtype: ttt

Explanation:


to a volume, vvvv, that was not mounted for DSN nnn

on device type ttt.

User response:



BKMCA132E No MCDS data set with valid

key-range found

Explanation:

An attempt was made to find a data set name in the

HSM MCDS but no MCDS found in the HSM address

space had a key range that would accommodate the

data set name.

User response:

Processing continues. No MCDS data will be included

for this data set.

BKMCA133E No MCDS DSN(s) found in HSM

address space

Explanation:

An attempt was made to find a the data set names of

the MCDSs allocated to HSM. The attempt failed.

User response:


for this data set.

BKMCA134W Error calling BKMHSM RC=RC

Explanation:


User response:

Processing continues. No MCDS data will be included.

If the reason for the failure cannot be determined,


BKMCA135E nnnn : VOLSER=vvvvvv - VVDS not

open

Explanation:

A previous OPEN failed for the VVDS on volume vvvvvv

failed.

User response:

Processing continues. No VVDS related data is returned

for data set nnnn.

BKMCA136W Invalid DSN found :

xxxxxxxxxxxxxxxxxxx

Explanation:

The catalog contained an invalid data set name. The

first BKMCA136W shows the data set name in

character format. The next three BKMCA136W show

the name in hex.

User response:

Fix the catalog and retry the function.

BKMCA137W Open failed for: nnnn - Will not be

used for search

Explanation:

Unable to open catalog nnnn. No entries that might


User response:


BKMCA125E • BKMCA137WIBM Confidential


BKMCA138E Cluster not found for TRUENAME in

catalog -

Explanation:

An error has been detected in your catalog. A VSAM

true name record was found without an associated

cluster entry.

User response:

Informational only. Processing continues. Evaluate

catalog entries for the identified data set.

BKMCA139I Retrying error obtaining ??????? FOR

DSN - ucat

Explanation:

An error occurred when trying to access the VTOC,

VVDS, or MCB information for a data set. This message

will occur if the catalog is incorrect. This message may

occur if the data set is being migrated so that the

catalog is temporarily out of date.

User response:

No action required for this message unless subsequent

errors BKMCA117E, BKMCAx20E, or BKMCAx14E

occur. See action for these messages.

BKMCSM01I BKM01CSM Maintenance Level (rev id

date)

Explanation:

Shows revision number, fix ID and fix date of

BKM01CSM.

User response:

None.

BKMCSM09E Migration keywords kw1 requires

keyword kw2

Explanation:

If you specify xxx-MIGRATION-TAPE you must also

specify the corresponding xxx-MIGRATION-DASD.

If you specify xxx-MIGRATION-DASD you must also

specify the corresponding xxx-MIGRATION-TAPE.

Valid GDS-MIGRATION* variations:

1. Explicit GDS-MIGRATED, specify only

GDS-MIGRATED

2. Implicit GDS-MIGRATED, specify no GDS migrated

keywords so the INI values for GDS migration are

used.

3. GDS migrated by migrated type, specify

GDS-MIGRATED-DASD and DS-MIGRATED-TAPE

Valid NONVSAM-MIGRATION* variations:

1. Explicit NONVSAM-MIGRATED, specify only

NONVSAM-MIGRATED.

2. Implicit NONVSAM-MIGRATED, specify no

NONVSAM migrated keywords so the INI

NONVSAM migration are used.

3. NONVSAM migrated by migrated type, specify

NONVSAM-MIGRATED-DASD with

NONVSAM-MIGRATED-TAPE

Valid VSAMSPERE-MIGRATION* variations:

1. Explicit VSAMSPERE-MIGRATED, specify only

VSAMSPERE-MIGRATED

2. Implicit VSAMSPERE-MIGRATED, specify no

VSAMSPERE migrated keywords so the INI

VSAMSPERE migration are used.

3. VSAMSPERE migrated by migrated type, specify

VSAMSPERE-MIGRATED-DASD and

VSAMSPERE-MIGRATED-TAPE.

User response:

Edit the CATSCRUB command and rerun.

BKMCSM10E Invalid to use migration keyword kw1

with kw2

Explanation:

where: | kw1 | kw2

| GDS-MIGRATED-DASD | GDS-MIGRATED

| GDS-MIGRATED-TAPE | GDS-MIGRATED

| NONVSAM-MIGRATED-DASD | NONVSAM-MIGRATED

| NONVSAM-MIGRATED-TAPE | NONVSAM-MIGRATED

| VSAMSPHERE-MIGRATED-DASD |

VSAMSPHERE-MIGRATED

| VSAMSPHERE-MIGRATED-TAPE |

VSAMSPHERE-MIGRATED

Use of the xxx-MIGRATION-DASD or

xxx-MIGRATION-TAPE keywords, makes the

corresponding xxx-MIGRATION keyword invalid.

Valid GDS-MIGRATION* variations:

1. Explicit GDS-MIGRATED, specify only

GDS-MIGRATED.

2. Implicit GDS-MIGRATED, specify no GDS migrated

keywords so the INI values for GDS migration are

used.

3. GDS migrated by migrated type, specify

GDS-MIGRATED-DASD and DS-MIGRATED-TAPE.

Valid NONVSAM-MIGRATION* variations:

1. Explicit NONVSAM-MIGRATED, specify only

NONVSAM-MIGRATED.

BKMCA138E • BKMCSM10E IBM Confidential


2. Implicit NONVSAM-MIGRATED, specify no

NONVSAM migrated keywords so the INI

NONVSAM migration are used.

3. NONVSAM migrated by migrated type, specify

NONVSAM-MIGRATED-DASD with

NONVSAM-MIGRATED-TAPE

Valid VSAMSPERE-MIGRATION* variations:

1. Explicit VSAMSPERE-MIGRATED, specify only

VSAMSPERE-MIGRATED.

2. Implicit VSAMSPERE-MIGRATED, specify no

VSAMSPERE migrated keywords so the INI

VSAMSPERE migration are used.

3. VSAMSPERE migrated by migrated type, specify

VSAMSPERE-MIGRATED-DASD and

VSAMSPERE-MIGRATED-TAPE.

User response:

Remove the keywords that you do not need and rerun.

BKMCSM11E Keyword kw1 invalid unless used

with keyword kw2

Explanation:

The EXCLUDE- keywords must be used with the non-

excluded keyword. Examples:

Table 1.

Keyword invalid

unless Keyword is specified

EXCLUDE-MATCH-VOLSER

MATCH-VOLSER

EXCLUDE-KEEP-TAPE

KEEP-TAPE

EXCLUDE-KEEP-VOLSER

KEEP-VOLSER

EXCLUDE-KEEP-DSN

KEEP-DSN

User response:

Revise the CATSCRUB command and rerun.

BKMCSM12E Severe error when attempting to

retrieve INI data - section: CATSCRUB

token: token name

Explanation:

Unable to find CATSRUB entry in CATINI.

User response:

Check CATINI and make sure CATSCRUB TOKEN is

correct.

BKMCSM13E INI token value is invalid - section:

CATSCRUB_OPTIONS token: token

name

Explanation:

CATSCRUB INI token value is invalid.

User response:

Correct and restart.

BKMCSM14E INI section/token missing or invalid -

section: CATSCRUB_OPTION token:

name

Explanation:

CATSCRUB INI SECTION/TOKEN missing or invalid.

User response:

Correct and restart.

BKMCSM21E Keyword kwd has mutually exclusive

keywords kwds.

Explanation:

CATSCRUB COMMAND contains invalid parm for 1 of

the 3 parm token names (DISP, RC(n), PROC).

DELETE or KEEP can be specified but not both.

CONTINUE or END can be specified but not both.

User response:

Correct the CATSCRUB COMMAND parm in error and

restart.

BKMCSM22E RC value not in numeric or not in

range of 0 to 4095.

Explanation:

CATSCRUB COMMAND contains invalid RC parm

value. The value must be numeric and in the range of 0

to 4095.

User response:


restart.

BKMCSM92E Error in the input command.

Explanation:

The CATSCRUB command is invalid as shown by prior

messages.

User response:


restart.

BKMCSM93E Error setting up the parser.

Explanation:

CATSCRUB command is unable to continue because of

an internal error.

User response:

Report error to Technical Support.

BKMCSM11E • BKMCSM93EIBM Confidential


BKMCSM97E Mask for keyword x more than 6

characters, starting with y. (or) Mask

for keyword x more than 44 characters,

starting with y.

Explanation:

The named keyword contains one or more strings, the

identified string is too long for a data set (44) or a

volume (6).

User response:

Correct CATSCRUB COMMAND parm in error and

restart.

BKMCSM99E Invalid mask for xxx found yyy

Explanation:

The named keyword contains one or more strings, the

identified string is not a valid mask.

User response:


restart.

BKMCSS01I Maintenance level

(REV=??,PMR=????????,

REVDATE=??/??/????)

Explanation:

Describes the version of the BKM01CSS module.

User response:

None required. Provide value if asked by Technical

Support.

BKMCSS02E CSI failed when calling for master

catalog name

Explanation:


User response:


BKMCSS03E Error calling CSI - MOD ID

Explanation:


User response:


BKMCSS04E (aaa) bbb failed filter: ccc dddd (or)

(aaa) bbb failed filter: ccc DSN=dddd

Explanation:

CATSCRUB has determined that a value ccc retrieved

from the master catalog is invalid. If the value is a

volume name, the DSN= value will indicate the name of

the data set with the problem. Otherwise, the data set

name is invalid.

User response:

The message indicates that you have a catalog entry

that is in error. Depending on your CATSCRUB

parameters, CATSCRUB may have deleted the data set

so that no other action is required. If CATSCRUB did

not delete the data set, you should remove the problem

data set, although CATSCRUB continued processing

normally.

BKMCSS06I DSN excluded by EXCLUDE-BCS

keyword, will not be processed.

Explanation:

The identified catalog will not be processed because of

an EXCLUDE-BCS mask.

User response:

None.

BKMCSS08E Deallocate failed for: cccc

Explanation:

Un allocation failed for catalog cccc.

User response:

Determine the reason for and fix the problem, Retry the

function.

BKMCSS09E Allocation failed for:cccc

Explanation:

Allocation failed for catalog cccc. Highest Return code

150.

User response:

Add Usercat cccc to the EXCLUDE-BCS list and retry.

BKMCSS10E UCBSCAN error; return code=rc

reason code=rsn

Explanation:


User response:


BKMCSS11E Error calling IGDCSP00 for VOLSER

volser - RC = rc ID=nn while seeking

VTOC information for data set xxxxx

UCB dump:

Explanation:

An error occurred while retrieving the VTOC for a

volume. A hex dump of the UCB is printed.

User response:

v RC = 4 Error accessing one or more data sets.

Check status of the volume. CATSCRUB will continue

per message BKMCSS34E.

v RC= 8 Error accessing VTOC. The volume identified

was found online but the VTOC was not of the

correct format. This can occur on VM/CMS volumes

that are online to MVS. Check status of data set and

BKMCSM97E • BKMCSS11E IBM Confidential


the volume. If the volume is a VM/CMS volume, the

catalog entry is incorrect and the volume should not

be online to MVS. CATSCRUB will continue per

message BKMCSS34E.

v RC = 12 Error accessing VVDS - Either the VVDS is

missing from the volume or a VVR or NVR record

could not be found in the VVDS. Take corrective

action. CATSCRUB will continue per message

BKMCSS34E.

v RC = 16 Getmain/Freemain error. This condition

should not occur. Internal error. Contact Technical

Support.

v RC = 32 Parm list error. This condition should not

occur. Internal error. Contact Technical Support.

v RC = 320 Can’t acquire enough memory. USE

REGION=0M on the EXEC PGM= JCL statement and

rerun CATSCRUB.

BKMCSS12E Error calling BKM01VV1 xxxx R15=rc

R0=rea ID=nn

Explanation:


User response:


BKMCSS13I xxxx : entry deleted - yyyy

Explanation:

If a data set is in the catalog but not found on the

volume specified in catalog being scrubbed, then the

data set (xxxx) is deleted for the reason (yyyy).

User response:

Verify that the data set (xxxx) was deleted for the

reason (yyyy) specified.

BKMCSS14W data set name : keyword option :

RC=nn

Explanation:

This message appears when RC for keyword option set

= 4 and the DISP value is ’KEEP’. If a data set is in the

catalog but a volume is not in the VOLUME ONLINE list

this message will be displayed. The volume is excluded

from the VOLUME ONLINE list by actually not being

online, not being in the MATCHVOLSER list if present,

or by being in the EXCLUDEMATCHVOLSER list if

present.

User response:

Determine what action you wish to take for this

anomaly.

BKMCSS15E data set name : CATSCRUB keyword

option : RC=nn

Explanation:

This message appears when RC for keyword option set

> 4.

User response:

Determine what action you wish to take for this anomaly

BKMCSS16I data set name : ASSOC NON-VSAM

ALIAS DELETED - reason

Explanation:

This non-VSAM alias has been deleted due to DELETE

in NONVSAM_ALIAS_NO_REALNAME specification.

User response:

None.

BKMCSS18I data set name : Path entry deleted -

reason

Explanation:

This VSAM entry has been deleted due to DELETE in

one of the VSAM-SPHERE keywords.

User response:

None.

BKMCSS19I data set name : TRUENAME entry

deleted - reason

Explanation:

This VSAM entry has been deleted due to DELETE in

one of the VSAM-SPHERE keywords.

User response:

None. Informational message.

BKMCSS20E GDG base name : catalog sharing

error

Explanation:

This error occurs if the record to rebuild has changed

since it was last read.

User response:

Stop sharing of catalog and restart.

BKM21I data set name : GDS entry deleted -

reason

Explanation:

This GDS entry has been deleted due to DELETE in

one of the GDS- keywords.

User response:

None.

BKM22I data set name : GDG base deleted -

reason

Explanation:

This GDG base entry has been deleted due to a

DELETE in the GDGBASE-NO-ACTIVE-GENS keyword.

User response:

None. Informational message.

BKMCSS12E • BKM22IIBM Confidential


BKMCSS23I CATSCRUB processing prematurely

terminated due to ’END’ request on xxx

Explanation:

The named keyword specified END for the anomaly

found.

User response:

None.

BKMCSS24E Error opening catalog. RC: 16 -

catalog catame

Explanation:

This error occurs while trying to open catalog for read

next.

User response:

Determine cause of error and fix or add catalog name to

EXCLUDE_BCS keyword string.

BKMCSS25E Error opening catalog for update. RC:

16 - CATALOG catname

Explanation:

This error occurs while trying to open catalog for

update.

User response:

Determine cause of error and fix or add catalog name to

EXCLUDE_BCS keyword string.

BKMCSS27E No catalogs meet specifications for

CATSCRUB

Explanation:

The BCS keyword did not specify a mask for an existing

catalog.

User response:

Change the BCS keyword so that the mask or DSN

matches one or more catalogs.

BKMCSS28I No processing needed for this catalog.

Explanation:

Either the catalog is empty or there are no conditions in

the catalog that meet the CATSCRUB command string.

User response:

Verify that the informational message is correct.

BKMCSS29W BCS not in master catalog - ignored

bcs mask|bcs name

Explanation:

The bcs mask|bcs name is not in master catalog.

User response:

Verify that the bcs mask|bcs name is what was intended

and possibly re-run.

BKMCSS30I Expected record not found - ignored:

xxx record key.

Explanation:

A record was being read for update but was not found.

User response:


BKMCSS31E Error rebuilding GDG sphere: key.

Explanation:

A GDG Sphere record read but was not found.

User response:

Processing continues. Report this to Technical Support.

BKMCSS32I List of MATCH-VOLSER volumes

minus EXCLUDE-MATCH-VOLSER

Explanation:

This information is provided to help you validate your

MATCH-VOLSER and EXCLUDE-MATCH-VOLSER

selection.

User response:

None.

BKMCSS33W MATCH-VOLSER volumes minus

EXCLUDE-MATCH-VOLSER volumes

yields no VOLUMEs.

Explanation:

Using these keywords and the disk volumes online

leave no match volumes. The purpose of CATSCRUB is

to delete all catalog entries for data sets that are not on

the matched volumes CATSCRUB will now delete all

items in the catalogs that you have specified -

depending on your anomaly keywords.

User response:

None.

BKMCSS34E VOLUME volser - no VTOC found,

continuing.

Explanation:

CATSCRUB could not retrieve the VTOC from the

named volume. A volume can have no VTOC, when:

1. The volume is a VM/CMS mini-volume that is

errantly varied online to the Z/OS system.

2. The volume has been initialized but has no VTOC

create.

User response:

CATSCRUB logs this error and continues.

BKMCSS23I • BKMCSS34E IBM Confidential


BKMCSS35I Retry after error reading catalog, key=

xxx

Explanation:

CATSCRUB received a retriable error while reading the

current catalog sequentially.

User response:

CATSCRUB logs this message and continues.

BKMCSS99E name : catalog record error - reason

Explanation:

GDG or ALIAS catalog record error.

User response:

Fix reported problem and proceed.

BKMCSS35I • BKMCSS99EIBM Confidential


IBM Confidential



Messages (BKMD)

BKMDYN01I [message text]

Explanation:

where message text is one of the following:

Syntax error in value of xxxxxx -n

Illegal character in input text

BKM01PSN not available

IEFDB476 not available

Unknown request type

Function complete. RC=0

DSN failed RACF test

Not enough text units -

Critical keyword missing: xxxxx

SVC 99 (F) failure. R15: xx error: xxxx info: xxxx

Indicates BKM01DYN failed during a dynamic allocation

function.

User response:

Report this error and associated product errors to

Technical Support.

IBM Confidential

113

IBM Confidential



Messages (BKME)

BKMERR00I Object access failure, ddname: ddn

Explanation:

These messages are issued when the Catalog Fast

Reader, Catalog Keyed Updater, or VVDS Handler

encounter an error.

User response:

Depends on other messages. Generally, these

messages are designed to be self explanatory, and are

used by staff for extended debugging. Please contact

Technical Support.

BKMERR01I VVDS access failure, ddname: ddn

Explanation:



encounter an error.

User response:




Technical Support.

BKMERR02I DSN: usercat name

Explanation:

User Catalog cannot be accessed.

User response:

Follow the Programmer Response for message IEC161I

found in JESYSMSGs or eliminate the usercat from the

selection list.

BKMERR03I No DD allocation found

Explanation:



encounter an error.

User response:




Technical Support.

BKMERR04I Failing module Function: ##,description

Explanation:



encounter an error.

User response:




Technical Support.

BKMERR05I Previous module function: ##,description

Explanation:



encounter an error.

User response:




Technical Support.

BKMERR06I Program CSECT: csect

Explanation:



encounter an error.

User response:




Technical Support.

BKMERR08I statement error ID: listingID#

Explanation:



encounter an error.

User response:




Technical Support.

BKMERR09I statement ASM listing line #: line#

Explanation:



encounter an error.

User response:




Technical Support.

IBM Confidential

115

BKMERR10I R15 = ##, description

Explanation:



encounter an error.

User response:




Technical Support.

BKMERR12I module ASM listing line #: line

Explanation:



encounter an error.

User response:




Technical Support.

BKMERR14I Processor R15: r15

Explanation:



encounter an error.

User response:




Technical Support.

BKMERR15I Processor reason code: nnn

Explanation:

This is the decimal value of the failure reason code.

Usually this is followed by message BKMERR20I

containing text explanation of the reason code. If a text

explanation is not available, BKMERR18I is issued, ″NO

DESCRIPTION FOR REASON CODE″.

User response:

If message BKMERR18I follows BKMERR15I and the

error is determined by OPEN, CLOSE or VSAM (as

indicated by message BKMERR19I), additional

information about the reason code can be obtained by

consulting z/OS V1R9.0 DFSMS™ Macro Instructions for

Data Sets.

BKMERR16I SVC99 error code:

Explanation:



encounter an error.

User response:




Technical Support.

BKMERR17I SVC99 information code:

Explanation:



encounter an error.

User response:




Technical Support.

BKMERR18I No description for reason code

Explanation:



encounter an error.

User response:




Technical Support.

BKMERR19I Error determined by:

Explanation:



encounter an error.

User response:




Technical Support.

BKMERR20I description

Explanation:



encounter an error.

User response:




Technical Support.

BKMERR10I • BKMERR20I IBM Confidential


BKMERR21I ** implicit OPEN

Explanation:



encounter an error.

User response:




Technical Support.

BKMERR22I ** implicit CLOSE

Explanation:



encounter an error.

User response:




Technical Support.

BKMERR23I ** Implicit reposition

Explanation:



encounter an error.

User response:




Technical Support.

BKMERR24I OPEN classification:

Explanation:



encounter an error.

User response:




Technical Support.

BKMERR25I Calling parm LRECL:

Explanation:



encounter an error.

User response:




Technical Support.

BKMERR26I Calling parm KEYLEN:

Explanation:



encounter an error.

User response:




Technical Support.

BKMERR27I LRECL:

Explanation:



encounter an error.

User response:




Technical Support.

BKMERR28I CI RBA requested:

Explanation:



encounter an error.

User response:




Technical Support.

BKMERR29I VVR/NVR key requested:

Explanation:



encounter an error.

User response:




Technical Support.

BKMERR30I Record type requested:

Explanation:

BKMERR21I • BKMERR30IIBM Confidential

Chapter 7. Advanced Backup and Recovery for z/OS Messages (BKME) 117



encounter an error.

User response:




Technical Support.

BKMERR31I VVR keyrange qualifier requested:

Explanation:



encounter an error.

User response:




Technical Support.

BKMERR31I IBM Confidential



Messages (BKMF)

BKMF0000I Tracking suspended - Jobname:nnn

Step name:sss.

Explanation:

Tracking will not be done for jobname nnn step sss.

See sysout for the reason.

User response:

None.

BKMF3501E BKMSTSKA not running

Explanation:

BKMSTSKA must be active on the image submitting this

job.

User response:

Start BKMSTSKA or determine why it may have failed.

BKMF3502E Allocate of message queue failed.

Explanation:

SVC99 failure.

User response:

From the included SVC99 return code, determine why

the allocate failed.

BKMF3503E Cannot open message queue.

Explanation:

BDAM open failure.

User response:

Check attributes of message queue. Ensure JCL

member DEF#MSGQ was run.

BKMF3504E Free of message queue failed.

Explanation:

SVC99 failure.

User response:

From the included SVC99 return code determine why

the free failed.

BKMF3507I Message queue refresh sent: SYSID.

Explanation:

The message sent after the system identified by sysid

has updated that a refresh of the BIF is needed.

User response:

None - verify in the SDSF log that the refresh

completed.

BKMF3601E Error returned for BKM01FD1 - xxxx

Explanation:

An error occurred processing old/new filters.

User response:


BKMF3602I DSN-name : no matching ″old″ filter.

Explanation:

No ″OLD″ rename filter matched this data set name.

The data set will not be restored with a new name.

User response:

Processing proceeds.

BKMF3603E New mask : rename mask is invalid.

Explanation:


User response:


BKMF3604E New-mask : new name greater than 44

bytes.

Explanation:

The new data set name built as a result of the ″new″

rename filter exceeds the 44 byte maximum length.

User response:


BKMF3701E Error calling BKM01VV1 tttttttt Function:


Explanation:




User response:


BKMF3702E Error calling xxxxxxxx R15=nnnn

Explanation:



User response:

Call Technical Support. Have available the listing that

contains this message and the parmlib member that

controls execution.

BKMF3703W No backups selected for restore.

Explanation:

IBM Confidential

119

No backups matching the selection criterion used were

found.

User response:

If not correct, correct the command and retry.



Explanation:




User response:

Processing terminates.


Explanation:



User response:

Call Technical Support. Have available the listing that

contains this message and the parmlib member that

controls execution.

BKM3806E Invalid parm: ppppp

Explanation:

Command parm ppppp is invalid.

User response:

Correct the syntax errors and restart the job.

BKMF3807E Mutually exclusive parameters: xxxxx

Explanation:

Command parms xxxxx are mutually exclusive.

User response:


BKMF3808E Required parm missing: xxxxx

Explanation:

A required parm is missing.

User response:


BKMF3809E Unknown parm.

Explanation:

The command statement listed above contains an

invalid parm.

User response:


BKMF3811E Unknown command.

Explanation:


invalid command.

User response:




Explanation:




User response:


BKMF5101E xxxxxxxx Missing: Tracking not

supported.

Explanation:

Required DD statement missing. It is required for

tracking.

User response:

Processing proceeds without tracking.


Explanation:



User response:



controls execution.

BKMF5103E OPEN error: ddname

Explanation:

An OPEN error occurred for the ddname indicated.

User response:


BKMF3801E • BKMF5103E IBM Confidential



Messages (BKMG)

BKMG3101E (Un)allocation failed: xxxxx.

Explanation:


User response:


job. If it is not a customer problem or the problem


BKMG3102E OPEN error: ddname

Explanation:


User response:


BKMG3103E Error calling xxxxxxxx R15=nnnn

Explanation:

A problem occurred calling an internal utility program


User response:



controls execution.

BKMG3104E TCB not found where expected.

Explanation:


User response:


BKMG3107E Error calling BRM01VV1 tttttttt Function:

function R15=nnnn R0=nnnnnnn ID=lllll

Explanation:




User response:


BKMG3109E Severe error when attempting to

retrieve INI data–section:ssss token:tttt

Explanation:


User response:


BKMG3110E INI section/token missing or

invalid–section: sssss token:tttt

Explanation:

Token tttt of section sssss in the INI is incorrect.

User response:


BKMG3113E Name/Token xxxxx not found.

Explanation:

The most likely cause for this error is that BKMSTSKA

is not started.

User response:

Start BKMSTSKA and retry. If the problem persists, call

Technical Support.

BKMG3114E Name/Token xxxxx invalid.

Explanation:


User response:


BKMG3116W No supported function found.

Explanation:

None of the commands found in SYSIN were supported.

User response:


BKMG8101E (Un)allocation failed:xxxxx

Explanation:


User response:



Support.

BKMG8102E OPEN error: ddname.

Explanation:


User response:


BKMG8103E Error calling xxxxxxxx R15=nnnn

Explanation:



User response:

IBM Confidential

121



controls execution.

BKMG8104E Error calling BKM01VV1 ttttttt

Function:function R15=nnnn


Explanation:




User response:


BKMG8108E nnnnn: not found in HSM BCDS.

Explanation:

Backup for nnnnn copy not found in HSM BCDS after

ARCINBAK.

User response:

Processing proceeds but IDS data is incomplete.

BKMG8113E Name/Token xxxxx not found.

Explanation:


is not started.

User response:


Technical Support.

BKMG8114E Name/Token xxxxx invalid.

Explanation:


User response:


BKMG8502E INI section/token missing or invalid -

Section: sssss Token: tttt

Explanation:


User response:

Fix the problem in the INI and retry.

BKMG8503E Allocation failed: file.

Explanation:


User response:



Support.

BKMG8504E OPEN failed: ddname

Explanation:


User response:

Determine the reason for the OPEN failure and retry the

job.

BKMG8505E LOAD failed for pgmname. RC: rr

Reason: ss

Explanation:


User response:


BKMG8511E OPEN failed: ddname.

Explanation:

An OPEN error occurred for the DDNAME indicated.

User response:

Determine the reason for the OPEN failure and retry

job.

BKMG8104E • BKMG8511E IBM Confidential



Messages (BKMH)

BKMH0001E Invalid function code:xxxxx

Explanation:


User response:


BKMH0001I Invalid function code:xxxxx

Explanation:


User response:


BKMH0002E Error calling xxxxxxxx RC=nnnn

Explanation:



User response:



controls execution.

BKMH0003E Unable to locate INI file.

Explanation:

Access to the INI data set is required. Most likely cause

is a JCL DD statement missing.

User response:

Correct the error and retry.

BKMH0004E (Un)allocation failed: xxxxxx

Explanation:


User response:



Support.

BKMH0005E Authorization failed.

Explanation:

Authorization to use this feature failed.

User response:

Verify parmlib INI tokens in the PRODUCT_SECURITY

section are set to values supplied by support. If these

appear correct call Technical Support.

BKMH0100I BKMSTSKA: build &SYSDATC

&SYSTIME

Explanation:

Date and time program BKMSTSKA was assembled

and linked.

User response:

None.

BKMH0101E Cannot load support module

PGMNAME.

Explanation:

Unable to load PGMNAME.

User response:

Most probably cause is the program is not in the

execution loadlib concatenation. Check the JCL. If

unable to determine the cause, call Technical Support.

BKMH0102E Severe error when attempting to

retrieve INI data - section: ssss token :

tttt

Explanation:


User response:


BKMH0103E INI section/token missing or invalid -

section: ssssss token: tttt

Explanation:

Token tttt of section ssssss in the INI is incorrect.

User response:

Fix the problem in the INI and retry.

BKMH0104E Abended with no SDWA.

Explanation:

Job abended. Retry was not possible.

User response:


BKMH0105E Allocation failed: file.

Explanation:


User response:



Support.

BKMH0106E Cannot execute; unauthorized.

Explanation:

IBM Confidential

123

An attempt was made to execute BKMSTSKA from an

APF unauthorized load library.

User response:

Authorize the load library or move to an authorized

library and retry the job.

BKMH0107E BKMSTSKA already active on this

system.

Explanation:

BKMSTSKA is already active on this system.

User response:

None.

BKMH0108E Unexpected return code from pgmname

RC: returncode.

Explanation:

Bad return code from program. This is an internal error.

User response:


BKMH0109E BKMSTSKA command request not

recognized.

Explanation:

The modify command is invalid.

User response:

Retry.

BKMH0110E System completion code xxx.

Explanation:

ABEND occurred in started task.

User response:

Job terminates.

BKMH0111E OPEN failed: ddname

Explanation:


User response:


job.

BKMH0112E All slots filled in message queue.

Explanation:

A limit of 16 processors can participate in a single

message queue.

User response:

Limit the number of CPUs to 16. If the 16 limit is not the

problem, make sure the file is formatted. If still unable to

determine the problem, call Technical Support.

BKMH0113E Flat copy subtask is not responding.

Explanation:

An attempt was made to communicate with the flat copy

subtask but there was no response.

User response:


BKMH0114E Monitor command subtask is not

active.

Explanation:

STOPMON was not done because the monitor was not

active.

User response:

None.

BKMH0115E Flat copy subtask is not active.

Explanation:

An attempt was made to stop the flat copy task but the

task was not active.

User response:


BKMH0116E Monitor command subtask is not

responding.

Explanation:

An attempt was made to communicate with the monitor

but there was no response.

User response:


BKMH0117I Monitor command subtask stopped.

Explanation:

Monitor task has been deactivated.

User response:

None.

BKMH0118E Monitor command subtask already

active.

Explanation:

Attempt was made to start the monitor task but it was

already active.

User response:

None.

BKMH0119I Monitor command subtask started.

Explanation:

Monitor subtask is now active.

User response:

None.

BKMH0107E • BKMH0119I IBM Confidential


BKMH0121E Data space services function cccccc

failed RC:

Explanation:


User response:


BKMH0123E User response: aaaaa exit is not

loaded.

Explanation:

Action against exit was not taken because the exit was

not loaded.

User response:

None.

BKMH0128I Task-CSA loaded at: aaaa length: llll

Explanation:

For debugging purposes only.

User response:

None.

BKMH0129I Task-CSA loaded and identified.

Explanation:

For debugging purposes only.

User response:

None.

BKMH0130E Exit area already exists...must unload

first.

Explanation:

LOAD was not successful.

User response:

None.

BKMH0131E Task-CSA storage not available.

Explanation:

GETMAIN for CSA storage above the line failed.

User response:

Increase region size and retry.

BKMH0132E Unable to free task-CSA storage RC:

Explanation:


User response:


BKMH0133I Exit area removed.

Explanation:

IEFUSI exit has been removed.

User response:

None.

BKMH0134E pgmname load failed. RC:rr REASON:

ss

Explanation:


User response:


BKMH0135E CSVDYNAM facility nnnn RC:rr

REASON:ss

Explanation:


User response:


BKMH0136E Un-allocation failed: file.

Explanation:

Dynamic unallocation failed for the reason specified.

User response:



Support.

BKMH0137E Cannot xxxxxx exit. No exits defined to

MVS.

Explanation:


User response:


BKMH0138I Job table dataspace deleted.

Explanation:

Informational.

User response:

None.

BKMH0139I SMF xxxxx complete for yyyyy.

Explanation:

Informational.

User response:

None.

BKMH0121E • BKMH0139IIBM Confidential


BKMH0140E No xxxxxx exit defined to MVS.

Explanation:

IEUFSI exit not turned on in SMF parms.

User response:

Fix SMF parms and try again.

BKMH0141I Secondary exit loaded successfully.

Explanation:

Informational.

User response:

None.

BKMH0142E There were more/less exits deleted

than installed.

Explanation:

This is probably an internal error.

User response:


BKMH0143E Secondary exit already active.

Explanation:

TURNON was not done because the exit is already

active.

User response:

None.

BKMH0146I Secondary exit active.

Explanation:

Informational.

User response:

None.

BKMH0147I Secondary exit deactivated.

Explanation:

Informational.

User response:

None.

BKMH0148E Secondary not active.

Explanation:

TURNOFF was not done because the exit was not

active.

User response:

None.

BKMH0149I Job table refreshed.

Explanation:

A new copy of the job table is now in use.

User response:

None.

BKMH0150E Cannot load new secondary exit while

existing exit is turned on.

Explanation:

NEWSECONDARY was not done.

User response:

Unload the existing exit and retry.

BKMH0151I Secondary exit reloaded successfully.

Explanation:

Informational.

User response:

None.

BKMH0154I Errors occurred during shut down.

Explanation:

Errors were encountered during shut down.

User response:

Review messages and contact Technical Support for

additional information.

BKMH0155I Shut down complete.

Explanation:

Informational.

User response:

None.

BKMH0156I AUTOSTART complete.

Explanation:

Informational.

User response:

None.

BKMH0157I Errors occurred during AUTOSTART.

Explanation:

Errors were encountered during AUTOSTART.

User response:

Review messages and contact Technical Support for

additional information.

BKMH0140E • BKMH0157I IBM Confidential


BKMH0158E Flat copy subtask already active.

Explanation:

An attempt was made to start the FLATCOPY task, but

it was already active.

User response:

None.

BKMH0159I FLATCOPY subtask started.

Explanation:

FLATCOPY task is now active. This task finds files that

have been ″spun-out″ from intercepted backup utilities

and updates and copies the records to the IDS.

User response:

None.

BKMH0160I FLATCOPY command subtask stopped.

Explanation:

FLATCOPY task has been deactivated.

User response:

None.

BKMH0161I Shut down due to ABEND.

Explanation:

BKMSTSKA ended due to an ABEND.

User response:

Look for the reason in the previous messages. If unable

to determine the reason or fix the problem, call

Technical Support.

BKMH0162I Task structure shut down.

Explanation:

Informational only. Normal part of BKMSTSKA shut

down.

User response:

None.

BKMH0163I Waiting for command.

Explanation:

Informational only. Operator commands can now be

entered.

User response:

None.

BKMH0164I Task cleanup in progress.

Explanation:

Informational only. Started shutdown cleanup

processing.

User response:

None.

BKMH0165I FLATCOPY stopping – this could take

a minute.

Explanation:

Informational only. Started flat copy task shut down.

User response:

None.

BKMH0166I FLATCOPY busy - waiting for current

copy to finish.

Explanation:

Informational only. Started flat copy task shut down, but

a copy of a flat file is currently in progress.

User response:

None.

BKMH0167E Primary vector table not found.

Explanation:


User response:


BKMH0168E Secondary vector table not found.

Explanation:


User response:


BKMH0169E Active R.M. table not found

Explanation:


User response:


BKMH0201E (Un)allocation failed: file.

Explanation:


User response:



Support.

BKMH0202E Record not found: xxxxx

Explanation:

Record xxxxx was expected in the JOBFLAT file but

was not found. This is an internal error.

User response:


BKMH0158E • BKMH0202EIBM Confidential


BKMH0205E Job names exceeded dataspace

capacity.

Explanation:


User response:


BKMH0206E Bad table pointer in dataspace.

Explanation:


User response:


BKMH0208E Error releasing job table storage.

Explanation:


User response:


BKMH0209E Error obtaining job table storage.

Explanation:


User response:


BKMH0210E Function xxxxx failed. RC: rrrr

Explanation:


User response:


BKMH0301E BKMMQBLD: increase space, not room

for 256 4096 byte blocks in primary

extent.

Explanation:

MQBLD failed.

User response:

Increase primary space in JCL and retry.

BKMH0501E BKMUSISE: BKM01FD1 addr zero.

Explanation:


User response:


BKMH0502E BKMUSISE: task CSA addr zero.

Explanation:


User response:


BKMH0503E BKMUSISE: >>>> BKMCSATK not

found

Explanation:


User response:


BKMH0504E BKMUSISE: ESTAE addr zero.

Explanation:

This is an internal problem.

User response:


BKMH0505E BKMUSISE: ESTAE not established.

Explanation:


User response:


BKMH0506E BKMUSISE: TCB not found where

expected.

Explanation:


User response:


BKMH0507E BKMUSISE: TCT not found where

expected.

Explanation:


User response:


BKMH0508E BKMUSISE: JCT not found where

expected.

Explanation:


User response:


BKMH0205E • BKMH0508E IBM Confidential


BKMH0509E BKMUSISE: SCT not found where

expected.

Explanation:


User response:


BKMH0510E BKMUSISE: Job table not found.

Explanation:


User response:


BKMH0511I BKMUSISE: job step sss program: ppp

intercepted.

Explanation:

This is an informational message. Step sss, program

ppp has been intercepted and will track it in the IDS as

a backup event.

User response:

None.

BKMH0512E BKMUSISE: dataspace ALET not valid.

Explanation:


User response:


BKMH0513E BKMUSISE: BIF has not been loaded.

Explanation:

The BIF data has not been loaded.

User response:

Use ISPF to build the BIF data set and refresh the BIF

table.

BKMH0514I BKMUSISE: job step: stepname

included | excluded by filter filter.

Explanation:

This is an informational message. Job step stepname

was either included or excluded by filter from the BIF

table.

User response:

None.

BKMH0601E USI exit has abended.

Explanation:


User response:


BKMH0602I USI exit dormant.

Explanation:

USI exit is inactive.

User response:

None.

BKMH0603I No retry allowed.

Explanation:

Informational.

User response:

None.

BKMH0604I Retry routine abended.

Explanation:

Informational.

User response:

None.

BKMH0605I The system was unable to take a

dump: xxxxx RC=Xrrrrr

REASON=Xnnnnn

Explanation:

Informational.

User response:

None.

BKMH0701E BKMTTIME: BKMSTSKA CSA name

token not found.

Explanation:


User response:


BKMH0702E Abended with no SDWA.

Explanation:

Job abended. Retry was not possible.

User response:


BKMH0703E System completion code xxx.

Explanation:

ABEND occurred in CBTI code.

User response:

Processing terminates without tracking.



BKMH1001E Error calling xxxxxxxx R15=nnnn ID=lllll

Explanation:

A problem occurred calling an internal utility program..



User response:



controls execution.

BKMH1002E BKMUSISE: TCB not found where

expected.

Explanation:


User response:


BKMH1201E SYSOUT intercept routine abended.

Tracking will not be done for this job

step.

Explanation:


User response:

Processing proceeds without tracking. Please notify

technical support. Include dump when opening a

problem report.

BKMH1213E ABENDED with no SDWA ABENDED -

PSW not available ABEND during

BKM12100 processing.

Explanation:

Job abended.

User response:


BKMH1301E Error calling BKM01VV1 tttttttt function:


Explanation:



error occurred.

User response:


BKMH0139I SMF xxxxx complete for yyyyy.

Explanation:

Informational.

System action:

User response:

None.

BKMH1501E Unrecoverable error encountered - flat

file copy task shutting down.

Explanation:

An error has occurred. There will be no more attempts

to copy flat files to the IDS.

User response:

Stop the flatfile copier, fix the problem, and start the

copier again.

BKMH1502E HSM not active but is required to

process flat files - will try again later.

Explanation:

HSM is required to process flat files, but was not up.

The process will wait for a while and try again.

User response:

If HSM is up and this message continues to be issued,

stop the flat copy task (F ???,STOPFC) and call

Technical Support.


retrieve INI data - SECTION: ssss

TOKEN : tttt

Explanation:


User response:



SECTION: sssss TOKEN : tttt

Explanation:


User response:

Fix the problem in INI and retry.

BKMH1505E Allocation failed: file.

Explanation:


User response:



Support.

BKMH1506E Unallocation failed: file.

Explanation:

Dynamic unallocation failed for the file specified.

User response:



Support.



BKMH1507W Will try allocation again after a short

wait.

Explanation:

An allocation failed - see message above.

User response:

None.

BKMH1508E Error calling BKM01HSM RC=rc.

Explanation:


User response:

Copy of flat files is suspended. Call Technical Support.

BKMH1701E (Un)allocation failed: xxxxx

Explanation:


User response:


BKMH1702E Open error: ddname.

Explanation:


User response:


BKMH1703E Error calling xxxxxxxx RC=nnnn

Explanation:



the error occurred.

User response:


BKMH1704I Volume being dumped: xxxxxx

Explanation:

DUMP FULL of volser xxxxxx has been intercepted.

User response:

None

BKMH1705E UCBLOOK error for: vvvvvv return

code: rrrr reason code: nnnn

Explanation:

If volser vvvvvv is mounted, this is an internal error.

User response:


BKMH1706E Volume not mounted: vvvvvv DSN=nnnn

DEVTYPE: type CODE:nnnnn

Explanation:

If volser vvvvvv is mounted, this in an internal error.

User response:


BKMH1707E ERROR calling BKM01VV1 ttttttt

FUNCTION: function R15=nnnn


Explanation:



error occurred.

User response:


BKMH1708E DDNAME not found in TIOT: ddname.

Explanation:

The ddname coded in the DFDSS control statement

was not in the JCL.

User response:




TOKEN : tttt

Explanation:


User response:



SECTION: sssss TOKEN : tttt

Explanation:


User response:


BKMH1711E Unable to determine object volser.

Explanation:

Unable to find the volser being dumped.

User response:


BKMH1712E OUTDDNAME parm not found in

SYSIN.

Explanation:

Unable to find required SYSIN parm.

User response:

BKMH1507W • BKMH1712EIBM Confidential



BKMH1713E Name/token xxxxx not found.

Explanation:


is not started.

User response:


Technical Support.

BKMH1714E Name/token xxx invalid.

Explanation:


User response:


BKMH1716W No supported function found.

Explanation:


User response:


BKMH1717E Only one INDY parm supported.

Explanation:

More than one parameter was listed in the INDY parm.

User response:


BKMH1718E TCB not found where expected.

Explanation:


User response:


BKMH1801E Error calling BKM01VV1 xxxx R15=rc

R0=rea ID=nn.

Explanation:


User response:

Call Technical Report.

BKMH1802E Error calling xxxxxxxx R15=nnnn.

Explanation:



User response:



controls execution.


Explanation:


User response:



Support.

BKMH1804W Token

CHANGED_DATASET_TRACKING in

section CBTI_PROCESS_OPTIONS is

invalid - defaulted to N.

Explanation:

Token in INI is incorrect.

User response:


BKMH1805E OPEN error: ddname.

Explanation:


User response:


BKMH1806E DAD started task not active.

Explanation:

An attempt to update the DAD database failed. DAD not

up.

User response:

Processing proceeds without changed data set tracking.

BKMH1807E DAD update failed - Invalid PC number

encountered. Invalid ALET for DAD. An

ABEND occurred. Lock could not be

obtained.

Explanation:

Attempt to update the DAD database failed.

User response:

Processing proceeds without changed data set tracking.


retrieve INI data - Section: sssss Token:

tttt.

Explanation:


User response:





Section: sssss Token: tttt.

Explanation:


User response:



Explanation:


User response:


BKMH1902E OPEN error: ddname

Explanation:


User response:



Explanation:




User response:



Explanation:


User response:


BKMH1907E Error calling BKM01VV1 tttttt Function:


Explanation:




User response:

Processing proceeds without tracking. Contact Technical



execution.


Explanation:

The ddname coded in the IDCAMS control statement

was not in the JCL.

User response:



retrieve INI DATA - Section: ssss Token

: tttt

Explanation:


User response:



Section: sssss Token: tttt.

Explanation:


User response:


BKMH1912E Neither INFILE nor INDATATSET found

in command.

Explanation:

Required parms missing.

User response:



Explanation:


is not started.

User response:


Technical Support.

BKMH1914E Name/token xxxxx invalid.

Explanation:


User response:


BKMH1915E Neither OUTFILE nor OUTDATASET

found in command.

Explanation:


User response:


BKMH1916W No supported function found in

SYSIN.

Explanation:

CBTI found no supported commands in SYSIN.

User response:

BKMH1810E • BKMH1916WIBM Confidential



BKMH1917E Input was a member of a PDS.

Explanation:

Backup of a PDS member is not supported.

User response:


BKMH1918E Entry name missing.

Explanation:


User response:


BKMH1919E Selective keywords found.

Explanation:

IDCAMS REPRO / EXPORT with selective keywords is

no supported as a backup.

User response:


BKMH1920E Input was concatenated data sets.

Explanation:

Backup of concatenated data sets is not supported.

User response:


BKMH1921W AIX backup not supported.

Explanation:

Backup of AIX® is not supported. Only backups of entire

clusters are supported.

User response:


BKMH2001E Free of ddname DADMSGQ failed.

Explanation:

SVC99 failure.

User response:

Note SVC99 failure code and contact Technical Support.

BKMH2002E Error calling xxxxxxxxx RC=nnnn

Explanation:



User response:



controls execution.

BKMH2003E BKMDADMT not active.

Explanation:


User response:

BKMDADMT must be active on the image running the


BKMH2004E Failure allocating DDNAME DADMSGQ

to dataset.

Explanation:

SVC99 failure.

User response:

See SVC99 reason code. The problem is likely user

solvable.

BKMH2005E MSG queue no formatted correctly.

Expected DADMSG in 1st 16 slots.

Explanation:


User response:

Verify that JCL member DEF#MSGQ has been run.

BKMH2006I Waiting in BKMDADFL flush queue.

Explanation:

A FLUSH is already in progress. Only one can run at a

time.

User response:

None. Will retry until available.

BKMH2007I Waiting for access to MSGQUEUE.

Explanation:

MSGQUEUE is in use by another task.

User response:

None. Will retry until available.


Explanation:


User response:


BKMH2302E OPEN failed: ddname.

Explanation:


User response:





Explanation:




User response:


BKMH2307E Error calling BKM01VV1 tttttttt Function:


Explanation:




User response:




execution.

BKMH2308E DDNAME not found in TIOT: ddname

Explanation:

ddname coded in the FDR control statement was not in

the JCL.

User response:




TOKEN : tttt

Explanation:


User response:



Section: sssss Token : tttt

Explanation:


User response:


BKMH2312E Input data set is a PDS member - not

supported.

Explanation:

Only entire data sets are supported.

User response:



Explanation:


is not started.

User response:


Technical Support.


Explanation:


User response:


BKMH2316W Non-supported function found in

SYSIN.

Explanation:

Only GENERATE commands are supported.

User response:


BKMH2317E Input was concatenated data sets - not

supported.

Explanation:


User response:



Explanation:


User response:



Explanation:


User response:



Explanation:



the error occurred.

User response:





Explanation:


User response:


BKMH2407E Error calling BKM01VV1 ttttttt Function:


Explanation:




User response:




execution.

BKMH2408E DDNAME not found in TIOT:ddname.

Explanation:

The ddname coded in the FDR control statement was

not in the JCL.

User response:



retrieve INI DATA - Section: ssss Token

: tttt

Explanation:


User response:




Explanation:


User response:



Explanation:


is not started.

User response:


Technical Support.


Explanation:


User response:


BKMH2415I DSN: PDS compress not tracked.

Explanation:

A PDS compress was found in an intercepted step.

User response:



SYSIN.

Explanation:


User response:


BKMH2417I DSN: reason.

Explanation:

An IEBCOPY function for DSN not tracked because of

reason.

User response:


BKMH2501E Unallocation failed: xxxxx

Explanation:


User response:



Support.

BKMH2502E Error calling xxxxxxxx R15=nnnn

Explanation:



User response:



controls execution.

BKMH2503W UCBLOOK error for: vvvvvv return

code: rrrr reason code: nnnn

Explanation:


User response:


BKMH2404E • BKMH2503W IBM Confidential


BKMH2504W Volume not mounted: vvvvvv

DSN=nnnnn devtype: type code: nnnnn

Explanation:


User response:


BKMH2505E OPEN failed: ddname.

Explanation:


User response:


job.

BKMH2505W OPEN failed: ddname.

Explanation:


User response:


job.

BKMH2506W DUMPVTOC data set not available -

xxxx

Explanation:

A DUMPVTOC data set for a HSM AUTODUMP was

unavailable. No data set details will be available for this

dump in the IDS.

User response:


BKMH2507E ESEQ record not found.

Explanation:

A required records was not found in the IDS. This is

either an internal error or a corrupted database.

User response:

Processing terminates. Call Technical Support.

BKMH2508E Error calling BKM01VV1 ttttttt



Explanation:




User response:




execution.

BKMH2601E (Un)allocation failed: xxxx

Explanation:

Dynamic allocation failed for the specified file.

User response:

Processing continues without tracking.

BKMH2602E OPEN error : ddname.

Explanation:


User response:



Explanation:




User response:


BKMH2607E Error calling BKM01VV1 tttttttt Function:


Explanation:




User response:




execution.


Explanation:


not in the JCL.

User response:



retrieve INI data - Section: ssss Token :

tttt

Explanation:


User response:


BKMH2504W • BKMH2609EIBM Confidential




Explanation:


User response:


BKMH2612E Input data set is a PDS member - not

supported.

Explanation:

Input is a member of a PDS. Only entire data set

backups are tracked.

User response:



Explanation:


is not started.

User response:


Technical Support.


Explanation:


User response:


BKMH2615E Input was concatenated datasets - not

supported.

Explanation:


User response:



Explanation:


User response:



Support.


Explanation:


User response:


job.

BKMH3203E Error calling xxxxxxxx R15=nnnn

Explanation:



User response:



controls execution.


Explanation:


User response:


BKMH3205E UCBLOOK error for: vvvvvv Return

code: rrrr Reason code: nnnn

Explanation:


User response:


BKMH3206E Volume not mounted: vvvvvv DSN=nnnn

devtype :typeN CODE: nnn

Explanation:


User response:


BKMH3207E Error calling BKM01VV1 tttttt Function:


Explanation:



error occurred.

User response:



Explanation:

The ddname coded in the DFDSS control statement

was not in the JCL.

User response:




tttt

Explanation:




User response:




Explanation:


User response:

Fix the problem in INI and retry.


Explanation:


is not started.

User response:


Technical Support.


Explanation:


User response:


BKMH3220E xxxx: message does not adhere to

restrictions.

Explanation:

The SYSOUT message was not what was expected.

User response:


BKMH3221E SYSPRINT incomplete: FDR007

message missing.

Explanation:

The SYSOUT message expected was not found.

User response:


BKMH3221W FDRCPK command did not include a

dump.

Explanation:

Only backups are tracked. FDRCPK without the

DUMP=YES option is not a backup.

User response:



retrieve INI data – Section : ssss Token

: tttt

Explanation:


User response:




Explanation:


User response:



Explanation:


User response:



Support.

BKMH3304E OPEN error: file.

Explanation:


User response:


BKMH3305I nnnnn Being copied to IDS. Copy

successful. Copy failed.

Explanation:

Informational only.

User response:

None.



Explanation:



error occurred.

User response:


BKMH3307E Will try allocation again after a short

wait.

Explanation:

An allocation failed - see message above.

User response:



None.

BKMH3308W Version record missing or invalid.

Explanation:

A file whose name matches the filter for flat files

contains either no or an invalid version record.

User response:

The file is not copied. Processing continues. To stop

continually trying to process the problem data set, either

delete the file or rename it. F???,STOPFC.

BKMH3309I Sequential write failed, switching to

standard write.

Explanation:

When inserting records into the IDS sequentially, the


User response:



However, as part of this message, the previous data set

key and the current data set key will be displayed and

should be sent to Technical Support.

BKMH3310E Error calling CSI - MOD ID:xxxx Return

code:xxxx Reason: xxxx R15: xxxx

Catalog: catname

Explanation:

Errors were found in at least one of the data set entries

returned from this catalog.

User response:

Processing continues. Check output for accuracy.

BKMH3311E Failure in catalog search interface

routine:xxxx reason: xxxx R15: xxxx

catalog: catname

Explanation:

CSI called failed.

User response:

Processing terminates. Save diagnostic data and call

Technical Support.

BKMH3312E Reason code 0186 indicates the

catalog is locked.

Explanation:

Catalog has apparently been locked.

User response:

Processing terminates. Unlock the catalog and retry.

BKMH3313E More problem data sets than can be

tracked. Flat file copy shutting down.

Explanation:

Encountered more than 1000 data sets with the data

set prefix specified in INI that either do not have a valid

version record or contain invalid data.

User response:

The flat file copy task is shut down. Either rename the

problem datasets or delete them and restart the flat file

copy task. F ??,STARTFC

BKMH3314E Invalid data set or contained invalid

data.

Explanation:

Unable to process a data set whose name matched the

data set prefix specified in INI. The data set either did

not have a valid version record or contained invalid

data.

User response:

The file is not copied. Either rename or delete the

problem data set. If the reason cannot be determined,




Explanation:



error occurred.

User response:




Explanation:



error occurred.

User response:


BKMH3602E nnnn:reason

Explanation:

The data set cannot be tracked for the reason specified.

User response:


BKMH3603W nnnn: The output data set type is

invalid for a backup.

Explanation:

The data set type cannot be used for a recover.

BKMH3308W • BKMH3603W IBM Confidential


User response:

The data set name is changed to

INVALID.OUTPUT.DS.TYPE.??? where ??? is the

original data set type (JES, NULLFILE, TEMPFILE).


Explanation:


User response:



Explanation:


User response:



Explanation:



the error occurred.

User response:


BKMH3707E Error calling BKM01VV1 ttttttt



Explanation:



error occurred.

User response:




execution.


Explanation:


not in the JCL.

User response:



Explanation:


is not started.

User response:


Technical Support.


Explanation:


User response:



SYSIN

Explanation:

Found no supported commands in SYSIN.

User response:


BKMH3701E • BKMH3716WIBM Confidential


IBM Confidential



Messages (BKMI)

BKMI0002E OPEN error: ddname.

Explanation:


User response:


BKMI0003E Error calling xxxxxxxx R15=nnnn

Explanation:



User response:



controls execution.

BKMI0004E Invalid command syntax:

Explanation:

The command listed above contains syntax errors. See

messages prior to this one.

User response:


BKMI0005E ccccc command is required before the

first RESTORE command.

Explanation:

Command cccccc is a required command.

User response:


BKMI0006E Invalid parm: ppppp

Explanation:


User response:


BKMI0007E Mutually exclusive parameters: xxxxx

Explanation:

Command parms xxxxx are mutually exclusive.

User response:


BKMI0008E Required parm missing: xxxxxx

Explanation:

A required parm is missing.

User response:


BKMI0009E Unknown parm.

Explanation:


invalid parm.

User response:


BKMI0010E Internal error: rrrr

Explanation:

This is an internal logic error.

User response:


BKMI0011E Unknown command.

Explanation:


invalid command.

User response:


BKMI0012E Required DD statement missing: ddn.

Explanation:

DD statement ddn is missing – required.

User response:


BKMI0013E (Un)allocation failed: xxxxx

Explanation:


User response:



Support.

BKMI0014E Severe error when attempting to

retrieve INI data - Section: ssss Token

:tttt

Explanation:


User response:


BKMI0015E INI section/token missing or invalid -

Section: sssss Token :tttt

IBM Confidential

143

Explanation:


User response:


BKMI0016E Started task must be active to run a

restore.

Explanation:

An attempt was made to initiate a restore via ISPF and

the started task was not active.

User response:


Technical Support.

BKMI0017E Name/token xxx invalid.

Explanation:


User response:


BKMI0101E Error calling BKM01VV1 tttttt Function:


Explanation:




User response:



Explanation:



User response:



controls execution.

BKMI0103W No backups selected for restore.

Explanation:

No backups matching the selection criterion were found.

User response:

If not correct, correct command and retry.

BKMI0105E jobname rc rid jobname rundate runtime

step# task# utiltype: BAEV NOT FOUND.

Explanation:

Required IDS record was missing. Possible IDS

corruption.

User response:

No restore JCL will be built. Call Technical Support.

BKMI0105I jobname rc rid jobname rundate runtime


Explanation:


corruption.

User response:


BKMI0105W jobname rc rid jobname rundate runtime


Explanation:


corruption.

User response:


BKMI0106E jobname rc rid jobname rundate runtime:

failed RC check.

Explanation:

The backup job could not be processed because the

job’s return code is higher than was allowed by the

RESTORE command.

Note: The default BADKUPRC is 8.

User response:

No restore JCL will be built.

BKMI0106I jobname rc rid jobname rundate runtime:

failed RC check.

Explanation:



RESTORE command.


User response:


BKMI0106W jobname rc rid jobname rundate runtime:

failed RC check.

Explanation:



RESTORE command.


User response:


BKMI0016E • BKMI0106W IBM Confidential


BKMI0107I data set rc rid jobname rundate runtime

step task util : SELECTED

Explanation:

This backup event for data set has been selected for

processing.

User response:


BKMI0108E jobname: requested cycle not found.

Explanation:

Job cycle requested was not found for jobname.

User response:


BKMI0108I jobname: requested cycle not found.

Explanation:


User response:


BKMI0108W jobname: requested cycle not found.

Explanation:


User response:


BKMI0110W data set rc rid jobname rundate runtime

step task util : OVERLAP - SKIPPED

Explanation:

A more recent backup of data set was found. No restore

JCL will be build for this copy.

User response:


BKMI0201E Error calling BKM01VV1 ttttttt Function:


Explanation:




User response:



Explanation:


found.

User response:

If incorrect, correct command and retry.

BKMI0204E dsname : Requested gen not found.

Explanation:

Backup generation requested for dsname was not

found.

User response:


BKMI0204I dsname : Requested gen not found.

Explanation:


found.

User response:


BKMI0204W dsname : Requested gen not found.

Explanation:


found.

User response:


BKMI0205E data set rc rid jobname rundate runtime

step task util : Failed RC check

Explanation:

The selected backup event for data set could not be

processed because the event’s return code is higher

than was allowed by the RESTORE command.

Note: The default BADBKUPRC is 8.

User response:




Explanation:





User response:




Explanation:





BKMI0107I • BKMI0205WIBM Confidential


User response:



step task util : Selected

Explanation:


processing.

User response:



step task util : PHY backup - rejected

Explanation:

The requested generation for this data set was a

physical backup but include physical dumps was NO.

User response:


BKMI0301E Error calling BKM01VV1 tttttttt



Explanation:




User response:



Explanation:



User response:



controls execution.


Explanation:


found.

User response:


BKMI0304E volser: requested gen not found.

Explanation:

Backup generation requested for volser was not found.

User response:


BKMI0304E volser: requested gen not found.

Explanation:


User response:


BKMI0304W volser: requested gen not found.

Explanation:


User response:


BKMI0305E volser rc rid jobname rundate runtime

step# task# utiltype : Event record not

found in IDS

Explanation:


corruption.

User response:


BKMI0305I volser rc rid jobname rundate runtime


found in IDS

Explanation:


corruption.

User response:


BKMI0305W volser rc rid jobname rundate runtime


found in IDS

Explanation:


corruption.

User response:




Explanation:

The selected backup event for VOLSER could not be




User response:


BKMI0206I • BKMI0306E IBM Confidential




Explanation:





User response:




Explanation:





User response:




Explanation:


processing.

User response:


BKMI0401E Error calling BKM01VV1 xxxx r15=rc

r0=rea id=nn

Explanation:


User response:


BKMI0402E Error calling xxxxxxxx Rc=nnnn rrrr

Explanation:


xxxxxxxx is the program name for reason rrrr.

User response:



controls execution.


Explanation:


found.

User response:


BKMI0404E Error found un-zipping ASPB IDS

record - rrrr

Explanation:


User response:


BKMI0405E data set rc rid jobname rundate runtime

step task util : Backup no longer valid

Explanation:

The backup event selected to do restores is not in the

IDS.

User response:




Explanation:


IDS.

User response:




Explanation:


IDS.

User response:



step# task# utiltype : IDS record not

found

Explanation:


corruption.

User response:




found

Explanation:


corruption.

User response:


BKMI0306I • BKMI0406IIBM Confidential




found

Explanation:


corruption.

User response:



step# task# utiltype : Backup is

physical. Backup is HSM INCR.

Explanation:

The backup selected for restore is not a selected type.

It cannot be used because either the INI or the

command specified that this type of dump was not to be

used.

User response:





Explanation:




used.

User response:





Explanation:




used.

User response:


BKMI0412E dsn - No backup copy selected for

restore

Explanation:

No backup could be found that matched the input

criterion used.

User response:


BKMI0412I dsn - No backup copy selected for

restore

Explanation:


criterion used.

User response:


BKMI0412W dsn - No backup copy selected for

restore

Explanation:


criterion used.

User response:


BKMI0413E jobname rc rid jobname rundate runtime :

Failed RC check

Explanation:



RESTORE command.


User response:


BKMI0413I jobname rc rid jobname rundate runtime :

Failed RC check

Explanation:



RESTORE command.


User response:


BKMI0413W jobname rc rid jobname rundate runtime :

Failed RC check

Explanation:



RESTORE command.


User response:


BKMI0406W • BKMI0413W IBM Confidential




Explanation:

Data sets backup event xxx be processed.

User response:


BKMI0501E Error calling BKM01VV1 ttttttt Function:


Explanation:




User response:



Explanation:



User response:



controls execution.

BKMI0503W Requested backup copy not available -

xxxx

Explanation:

The backup copy for event xxxx was not available. The

backup copy is not in the IDS, the COPY(?) is

improperly coded, or the OUTCODE did not match the

filters specified.

User response:

Processing continues. No restore JCL is built for this

event.

BKMI0506E Expected record not found in IDS: xxx

Explanation:


corruption.

User response:


BKMI0507E Severe error when attempting to


tttt

Explanation:


User response:


BKMI0508E INI section/token missing or invalid -


Explanation:


User response:



Explanation:


User response:



Support.

BKMI0510E Internal error: unknown utility type - ids

rec key

Explanation:


User response:




Explanation:




User response:


BKMI0602E Internal error: unknown command - xxx

Explanation:


User response:


BKMI0603E Incompatible variable type - xxx

Explanation:

The SETx skel command is invalid. Variables are of

different types (numeric or character).

User response:

Correct skeleton and retry.

BKMI0604E Internal error: unknown record type -

xxx

Explanation:


User response:


BKMI0414I • BKMI0604EIBM Confidential


BKMI0605E Internal error: unknown utility type - ids

rec key

Explanation:


User response:



Explanation:


User response:



Support.


Explanation:



User response:



controls execution.

BKMI0704E OPEN error: ddname

Explanation:


User response:


BKMI0705E Syntax error in skeleton statement xxxx

Explanation:

The skeleton statement above is invalid for reason xxx.

User response:

Correct the statement and retry.

BKMI0706E IF- ENDIF statements not evenly

paired.

Explanation:

IF - ENDIF must be in pairs.

User response:

Correct the skeleton and retry.

BKMI0707E LOOP - ENDLOOP statements not

evenly paired.

Explanation:

LOOP - ENDLOOP must be in pairs.

User response:


BKMI0708E )ELSE with no preceding )IF.

Explanation:

Preceding )IF is required to use )ELSE.

User response:


BKMI0709E )ENDIF with no preceding )IF

Explanation:

IF - ENDIF must be in pairs.

User response:


BKMI0710E )ENDLOOP with no preceding )LOOP.

Explanation:

LOOP - ENDLOOP must be in pairs.

User response:


BKMI0711E Unknown skeleton command.

Explanation:

Probable spelling error.

User response:


BKMI0712E Undeclared variable: xxx

Explanation:

An attempt to use a variable that has not been

declared. Use )SETN to declare the variable before

using it in the skeleton.

User response:


BKMI0801E Error calling BKM01VV1 ttttttt



Explanation:




User response:


BKMI0802E Undeclared variable: xxx

Explanation:

An attempt to use a variable that has not been

declared. Use )SETn to declare the variable before

using it in the skeleton.

User response:


BKMI0605E • BKMI0802E IBM Confidential


BKMI0803E Variable value is NULL - xx

Explanation:

An attempt to use a variable that was declared but no

value was ever assigned. Not all variables are set for

every type of data set. Make sure the variable has not

been misused.

User response:

If help is needed to resolve this problem, call Technical

Support.

BKMI0804E Constructed JCL statement extends

past column 71.

Explanation:

Variable substitution used in the constructed statement

resulted in the maximum length being exceeded.

User response:


BKMI0805E Math would result in a negative value.

Explanation:

)SETN statement misused. Negative values are invalid.

User response:

Correct skeleton and retry.

BKMI0806E ))LOOP - )ENDLOOP string error.

Explanation:

Nested loop is coded improperly.

User response:


BKMI0807E Loop control count variable not

numeric.

Explanation:

Loop control variable is the wrong type.

User response:



function R15=nnnn R0=nnnnnnnn ID=llllll

Explanation:




User response:


BKMI1002E BAEV record not found in IDS: xxx

Explanation:


corruption.

User response:


BKMI1005W dsn : previous restore built for this

data set.

Explanation:

The DSN is being recovered in a previous step. If this is

a selective data set restore, the data set will not be

included in this step.

Note: If this is a full volume recover, the data set will

be recovered. This could cause the data set to

be regressed.

User response:



Explanation:



User response:



controls execution.

BKMI1P01E Error parsing INI, #(xxx) reason

(yyyyyyyyyyyyyyyyyyyyyyy)

Explanation:

INI parser found invalid INI text. When you get a

parsing error, first check that columns 73-80 are blanks.

These columns are not included int he text that is

parsed. Often this results in an error that is hard to see.

User response:

Edit your INI, fix the problem indicated, and resubmit.

BKMI1P02I Line (xxxx) Text (yyyyyyyyy

yyyyyyyyyyyyyyyyyyyyyyyyyy

yyyyyyyyyyyyyyyyy)

Explanation:

This message displays the line number and text of the

INI input line that was found to be in error. See

preceding BKMI1P01E message.

Note: For future compatability of the INI, please ensure

that columns 73-80 are blank.

User response:

Edit your INI, fix the problems indicated, and resubmit.

BKMI0803E • BKMI1P02IIBM Confidential


BKMI1P03W Remove non-blank text in columns

73-80 TEXT(xxxxxx)

Explanation:

This message warns that text found in columns 73-80 of

the INI input line might be in error. See preceding

BKMI1P01E message.



User response:

Edit your INI, fix the problems inidicated, and resubmit.

BKMI1P04E Additional information (xx

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)

Explanation:

This message provides additional information

concerning the INI input line that was found to be in

error. See preceding BKMI1P01E message.



User response:

Edit your INI, fix the problem indicated, and resubmit.

BKMIK101E BKM01IKB LOAD fail, RC =

Explanation:


User response:

Confirm BKM01IKB is in your STEPLIB concatenation. If

it is, contact Technical Support.

BKMIK102E BKM01MSG load fail, RC = ___

Explanation:


User response:

Confirm that BKM01MSG is in your STEPLIB

concatenation. if it is, contact Technical Support.

BKMIK103E IKJEFTSR fail return code = ___

reason code = ___ ABEND code = ___

Explanation:

An error occurred calling a module through IKJEFTSR.

rc is the return code from IKJEFTSR.rc2 is the return

code from the called program abend is the abend that

occurred.

User response:

1. Confirm that all of your libraries in the STEPLIB

concatenation are APF authorized.

2. Confirm that BKM01IKB is in the AUTHTSF

NAMES list in the IKJTSO__ member of

SYS1.PARMLIB.

If all of the above are true, contact Technical Support.

BKMIK104E Authorized program not in authorized

lib

Explanation:

You are running an authorized program but it is not in

an authorized library.

User response:

Confirm that all of the libraries in your STEPLIB


BKMIK201E BKM01IKB load fail, RC = ___

Explanation:


User response:

Confirm that BKM01IKB is in your STEPLIB


BKMIK202E BKM01MSG load fail, RC = ___

Explanation:


User response:

Confirm that BKM01MSG is in your STEPLIB


BKMIK203E IKJEFTSR fail return code = ___

reason code = ___ ABEND code = ___

Explanation:

An error occurred calling a module through IKJEFTSR.

rc is the return code from IKJEFTSR.rc2 is the return

code from the called program abend is the abend that

occurred.

User response:

1. Confirm that all of your libraries in the STEPLIB


2. Confirm that BKM01IKB is in the AUTHTSF

NAMES list in the IKJTSO__ member of

SYS1.PARMLIB.

BKMIK204E Authorized program not in authorized

lib

Explanation:

You are running an authorized program but it is not in

an authorized library.

User response:

Confirm that all of the libraries in your STEPLIB


BKMI1P03W • BKMIK204E IBM Confidential


BKMINI01E R2 does not point to valid vector table

Explanation:

No parameters passed to BKM01PLD.

User response:


BKMINI02E BKM01INI, VAR KEY LEN not 1-25

Explanation:


User response:


BKMINI03E BKM01INI, 2nd parm, no VL BIT

Explanation:


User response:


BKMINI04E BKM01VS1 GETDIR RC nnnnnnnn

Explanation:


User response:


BKMINI05E VAR token REC shorter than KEY

Explanation:


User response:


BKMINI06E Token value longer than PARM3

Explanation:


User response:


BKMINI07E RECLEN not from 1 TO 4081

Explanation:


User response:


BKMINI08E VARPUT, BKM01VS1 PUT failed

Explanation:


User response:


BKMINI09E BKM01VS1 END failed

Explanation:


User response:


BKMINP00I BKM01INP starting (REV=nn,

PMR=xxxxxxx, FIXDATE=xxxxxxxx

Explanation:

Message shows current version of the module.

User response:

None.

BKMINP01E Error parsing PARMLIB INI# member

on line n error parsing PARMLIB INI

member on line n

Explanation:

An error was found when parsing an INI member.

User response:

Look for subsequent messages and repair the

PARMLIB(xxxINI) or PARMLIB(xxxINI#) member as

indicated.

BKMINP02E Unmatched */ found Continued

statement at end of file

Explanation:

An end-comment (*/) was found for which there was no

begin-comment (/*).

User response:

Remove the end-comment or insert a begin-comment in

the appropriate location.

BKMINP05E Token name longer than 72

Explanation:

A Token name longer than 72 bytes was found on the

specified line.

User response:

Reduce the length of the token to 72 or less.

BKMINP06E Expected = after token name

Explanation:

An equal sign (=) was not found after the token name.

User response:

Insert an equal sign (=) between the token and its

value.

BKMINI01E • BKMINP06EIBM Confidential


BKMINP07E Expected = after token name

Explanation:


User response:


value.

BKMINP08E Found non-Notes token before 1st

section name

Explanation:

A Token was found before any Section was specified.

Only the Notes token is allowed before a section name.

Remember: Notes is provided for the customer and no

product code can access the Notes value.

User response:

Ensure that the first non-comment line and non-Notes

token is a Section name.

BKMINP09E Duplicate section/token found section

token

Explanation:

A token cannot be defined twice for the same section.

User response:

Remove the redundant token and retry.

BKMINP10E File function fail, RC = nnnnnnnn

Explanation:


User response:


BKMINP11E OPEN failure, DD ddname DD INI OPEN

failure DD SYSPRINT OPEN failure DD

UPDATE OPEN failure DD tracedd

OPEN failure

Explanation:


User response:


BKMINP12E Expected parm value or record, found

function

Explanation:


User response:


BKMINP14E Error parsing MSCINI

Explanation:

INIMERGE failed to parse the MSCINI input because it

could not find the INIMERGE_SECTION values.

User response:

Use the INI# member distributed and retry. If assistance

is needed contact Technical Support.

BKMINP15W Columns 73-80 not blank on line

Explanation:

INI parser detected characters in columns 73-80.

Technical Support has found many INI errors occur

because the person editing the INI cannot see text in

columns 73-80.

User response:

Edit INI to ensure columns 73-80 are blank.

BKMINP21E Sysplex name more than 8 characters

Explanation:

The sysplex value on an INI section statement is invalid

because it is too long.

User response:

Repair the section name and retry.

BKMINP22E System name more than 8 characters

Explanation:



User response:


BKMINP31E Section name longer than 72

Explanation:

The section name is limited in size.

User response:


BKMINP32E Invalid section name

Explanation:

The section name can have alphanumeric characters in

addition to a period, dash, underscore or slash.

User response:


BKMINP33E Period(″.″) found in INI# section

Explanation:

A period character in the section name is valid in the

customer INI for denoting sysplex and system names

but is not valid in the distributed INI#.

User response:

BKMINP07E • BKMINP33E IBM Confidential



BKMINP34E Qualified INIMERGE_VALUES in INI

Qualified PRODUCT_INFO in INI

Explanation:

These sections cannot be qualified by sysplex or

system name.

User response:


BKMINP35E Two INIMERGE_VALUES sections

found

Explanation:

The INIMERGE_VALUES may only appear once in the

INI.

User response:


BKMINP36E Qualified section after generic

Explanation:

A section was found with sysplex or system

qualifications but it follows the same section without

such qualification. This section can never be accessed

and is invalid.

User response:


BKMINP37E Duplicate qualified section Duplicate

unqualified section found

Explanation:

Two section names match exactly, then are either:

1. Both unqualified

2. Both specify the same SYSPLEX and system

names.

Section names must be unique.

User response:


BKMINP38E Trailing period on section statement

Explanation:

A section statement has one of the following formats:

:sectionname.sysplexname.systemname

:sectionname.sysplexname

:sectionname..systemname

User response:


BKMINP39E INI# columns 73-80 are not blank, line

nnnn

Explanation:

Historically, placing text in columns 73-80 makes

debugging errors in the INI difficult.

User response:


BKMINP39W INI columns 73-80 are not blank, line

nnnn

Explanation:


debugging errors in the INI difficult.

User response:


BKMINP40E Right of INI#’’S section not blank

Explanation:

INI#’s section statement must be all blanks after section

name to facilitate customers entering SYSPLEX or

system names.

User response:


BKMINP41I Nothing copied

Explanation:

The customer INI had no special sections to copy.

User response:

None.

BKMINP42I Nothing delete

Explanation:

No INI parameters were deleted.

User response:

None.

BKMINP50I Input: input line

Explanation:

A previously noted error occurred on the line shown.

User response:

See prior error message.

BKMINP51E Token non-NOTES before 1st section

Explanation:

NOTES is the only token allowed before the first section

statement.

User response:

Repair the INI and resubmit.

BKMINP34E • BKMINP51EIBM Confidential


BKMINP52E Token NOTES found in INI#

Explanation:

NOTES is only allowed in the customer INI#.

User response:


BKMINP53E Error parsing MSCINI (INI#), See job

log error parsing the customer INI, see

job log

Explanation:

INIMERGE used the INI parser to validate the INI but

the INI parser was unsuccessful.

User response:

For INI#, contact Technical Support.

BKMINP71E Section in INI# but not INI:

Explanation:

INI view cannot find section in INI that was found in the

INI#.

User response:


BKMINP72I All INI# sections found in INI

Explanation:

All of the INI# sections were found in the INI.

User response:

None.

BKMINP73E Error in SYSPARM

Explanation:

BKM01INV SYSPARM is incorrect. Valid forms are:

SYSPARM= for current SYSPLEX and SYS name

SYSPARM=’’ for current SYSPLEX and SYS name

SYSPARM=’,’ for current SYSPLEX and SYS name

SYSPARM=’plexname,sysname’

User response:

Correct the SYSPARM on your execute statement and

resubmit.

BKMINS01E BKM01VV1 END failure, RC = nnnnnnnn

Explanation:


User response:


BKMINS02E Passed section length invalid length

Explanation:


User response:


BKMINS03E Passed token length invalid length

Explanation:


User response:


BKMINS04E INIGET 3RD parm, no VL BIT

Explanation:


User response:


BKMINS05E INI token REC shorter than KEY

section/token section/token

Explanation:


User response:


BKMINS06E Token value longer than receiving

parm section/token token token value

value

Explanation:


User response:


BKMINS07E Bad REG 2 PTR to vector table

Explanation:


User response:


BKMINP52E • BKMINS07E IBM Confidential



Messages (BKMJ)

BKMJ0101E Application specified not found in

database.

Explanation:

The application name entered was not an application

name that exists in the database.

User response:

Verify that the application name exists and correct the

application name on the BKUPEND command to match.

BKMJ0103E No backup found expected RC 0/4/8

Explanation:

The NO-BKUP-FOUND-RC keyword has a value

specified that is not 0, 4, or 8.

User response:

Correct the specified return code to 0, 4, or 8.

BKMJ0104E Changed since last backup expected

RC 0/4/8

Explanation:

The CHANGED-SINCE-LAST-BKUP-RC keyword has a

value specified that is not 0, 4, or 8

User response:


BKMJ0106W No critical DSNS found for APPL

specified.

Explanation:

No critical data sets were found for the application

name specified.

User response:

None.

BKMJ0108W ASPB with matching cycle not delete

Explanation:

An error occurred deleting a BKUPEND that contained a

cycle number matching the current BKUPEND cycle

number.

User response:

None. An additional BKUPEND will be displayed with

the same cycle number as the current one.

BKMJ0109W A BKUPEND for the current application

and cycle was found and will be

replaced.

Explanation:

A BKUPEND was executed for an application and cycle

that already had a previous BKUPEND performed. The

previous BKUPEND was replaced.

User response:

None.

BKMJ0110E DSN not defined to JCL - required

Explanation:

BKUPEND requires the database to be specified in the

JCL using the DD ACDIDB. This message is produced if

the Automated Critical Data Identification Application

Data Inventory has not been defined to the JCL.

User response:

Verify that the ACDIDB DD has been defined and that

the database has been specified on that DD.

BKMJ0120E No APPLEND record found to

determine cycle number.

Explanation:

BKUPEND retrieves the latest (most recent) cycle

number from the ASPDBAPE record for the application

requested. It did not find the record.

User response:

Verify that the application requested is correct. Verify

that an APPLEND run has been performed for the

application.



Explanation:




User response:



application.



Explanation:




User response:



application.

IBM Confidential

157

BKMJ0123E Error updating the ASPDBAPE record.

BKUPEND run terminated.

Explanation:

BKUPEND retrieves the latest (most recent)

ASPDBAPE (APPLEND) record from the data base to

update it with the BKUPEND date and time. Putting this

record back into the database failed. The BKUPEND

run is terminated.

User response:

This probably means some there is some kind of issue

with the database (hardware error, database full, and so

on). Verify that there is not physical problem with the

database and retry the application. If the problem


BKMJ0201E No BKUPEND for APPL specified.

Explanation:

The application specified on the BKUPEND report was

not found in the IDS.

User response:

None.

BKMJ0202E Bad cycle passed.

Explanation:

CYCLE number passed was not a valid number

between 0 and 9999.

User response:

Correct the cycle number and run the report again.

BKMJ0203E No backup found expected RC 0/4/8

Explanation:

The NO-BKUP-FOUND-RC keyword has a value

specified that is not 0, 4, or 8.

User response:


BKMJ0204E Changed since last backup expected

RC 0/4/8.

Explanation:

The CHANGED-SINCE-LAST-BKUP-RC keyword has a

value specified that is not 0, 4, or 8.

User response:

Correct the specified Return code to 0, 4, or 8.

BKMJ0210E BKUPEND found critical DSN(s) with

no backup.

Explanation:

The BKUPEND summary report found critical data sets

with no backup found in IDS.

User response:

None.

BKMJ0210I BKUPEND found critical DSN(s) with

no backup.

Explanation:



User response:

None.

BKMJ0210W BKUPEND found critical DSN(s) with

no backup.

Explanation:



User response:

None.

BKMJ0211E BKUPEND found DSN(s) changed

since last tracked BKP

Explanation:

The BKUPEND summary report found data sets

changed since the last tracked backup.

Note: This requires the DAD to be running to determine

if data sets have changed.

User response:

None.

BKMJ0211I BKUPEND found DSN(s) changed


Explanation:





User response:

None.

BKMJ0211W BKUPEND found DSN(s) changed


Explanation:





User response:

None.

BKMJ0123E • BKMJ0211W IBM Confidential


BKMJ0212E Bad backups were found with RC>=xx

Explanation:

xx is a value passed on the BAD-BKUP-RC parameter

for determining what BKUPEND should identify as a

bad backup. This message will be produced if a backup

was found at BKUPEND time that ended with a return

code greater than, or equal to, the number specified.

User response:

None.

BKMJ0313I Looking in catalog: catname

Explanation:

Catalog catname is being searched.

User response:

None.

BKMJ0314I Total data sets found: nnn

Explanation:

nnn is the total number of data sets found with no

backup.

User response:

None.

BKMJ0401E Error calling BKM01VV1 tttttttt Function:


Explanation:




User response:


BKMJ0402E Error calling xxxxxxxx R15=nnnn

Explanation:


xxxxxxx is the program name.

User response:



controls execution.

BKMJ0404W Data set record: xxx Expected event

record not found: yyy

Explanation:

Required IDS record yyy for data set record xxx was

missing. Possible IDS corruption.

User response:

Processing continues, but you should report the

problem to Technical Support.

BKMJ0502E Error calling xxxxxxxx R15=nnnn

Explanation:



User response:


BKMJ0504E Expected event record not found: xxx

Explanation:


corruption.

User response:


BKMJ0504W Data set record: xxx Expected event

record not found: yyy

Explanation:

Required IDS record yyy for data set record xxx was

missing. Possible IDS corruption.

User response:

Processing continues, but you should report the

problem to Technical Support.

BKMJ0513E ABENDed with no SDWA. ABENDed -

PSW not available. ABEND during

BKM12100 processing.

Explanation:

Job ABENDed.

User response:


BKMJCL00I Processing member xxxxxxx.

Completed member xxxxxxx. STOWing

alias xxxxxxx. ttr xxxxxx.

Explanation:

Message shows JCL members processed.

User response:

None.

BKMJCL01I PDS has alias xxxxxxx of xxxxxxx. PDS

has member

Explanation:

Program has found member name in directory.

User response:

None.

BKMJ0212E • BKMJCL01IIBM Confidential


BKMJCL02E Open failed for JCLIN/JCLOUT

/JCLDIR/SYSPRINT/operation FAILED

FOR ddname

Explanation:

The operation failed for the specified DD statement.

User response:

If operation is OPEN, make sure the JCL contains a DD

card for ddname. Otherwise, contact Technical Support.

BKMJCL02I Open failed for JCLIN. Open failed for

JCLOUT. Open failed for JCLDIR. Open

failed for SYSPRINT. operation FAILED

FOR ddname.

Explanation:

The operation failed for the specified DD statement.

User response:

If operation is OPEN, make sure the JCL contains a DD

card for ddname. Otherwise, contact Technical Support.

BKMJCL03E Errors found reading INI.

Explanation:

The JOB log shows the errors detected in the INI.

User response:

Correct the INI.

BKMJCL04E Element error. Procname too long.

Explanation:

The specified element had the specified error.

User response:

Correct the error.

BKMJCL05E Unknown JCL type.

Explanation:

A line of JCL was found that could not be scanned.

User response:


BKMJCL06E Expecting PARM: xxxx in section: xxxx

Explanation:

A parameter of a proc wasn’t defined in the INI within

the section specified.

User response:


BKMJCL07E Error on line: nnnn text:

xxxxxxxxxxxxxxxxxxxxxxxxxx

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Explanation:

The specified line number with displayed text is

incorrect.

User response:


BKMJCL08W ALIAS has no member xxxxxxxx; will

create member xxxxxxxx.

Explanation:

A broken alias has been found. This typically occurs

with a PDS (not a PDSE) when a member has an alias

and the member has been edited and saved. The

member and the alias relationship is broken so that

there are now two separate members–modeling what

occurs with the ISPF editor.

User response:

None.

BKMJCL10I Maintenance: BKMJCL07E: text:

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Explanation:

Specified line number with displayed text is incorrect.

User response:


BKMJCL11I BKM01JCL processing ended

successfully.

Explanation:

All JCL was processed with no errors.

User response:

None.

BKMJCL20I (text) found - JCL record.

Explanation:

Indicates a target JCL component to be changed.

User response:

None required.

BKMJCL21I (text) delete - JCL record.

Explanation:

Indicates a JCL record to be deleted.

User response:

None required.

BKMJCL22I (text) insert - JCL record.

Explanation:

Indicates a JCL record to be added.

User response:

None required.

BKMJCL02E • BKMJCL22I IBM Confidential


BKMJCL30I Using JCL_PROC_PARMS section.

Explanation:

Indicates the INI section that will be used to drive the

JCL customization. This name varies by function and

version.

User response:

None required.

BKMJCL31E Processing ended with errors.

REASON :JCL_PROC_PARM not in INI.

Explanation:

The section named JCL_PROC_PARMS must exist in

your INI, based on the function and version.

User response:


BKMJCL99E Internal errors.

Explanation:

An unrecoverable internal error occurred.

User response:

Correct the JCL error.

BKMJCL30I • BKMJCL99EIBM Confidential


IBM Confidential



Messages (BKMK)

BKMK0101E APPLNAME parameter missing

Explanation:

The program was not passed a parameter.

User response:


Technical Support.

BKMK0102E APPLNAME parameter too long invalid

3rd parm

Explanation:

Internal error with parameters.

User response:


Technical Support.

BKMK0103E Database rewrite error RC=

Explanation:

Error rewriting a record.

User response:


Technical Support.

BKMK0104E Bad return code from AMPCTLOC

close

Explanation:

Internal error.

User response:


Technical Support.

BKMK0105E Bad return from AMPCTLOC

Explanation:

Internal error.

User response:


Technical Support.

BKMK0106E Bad return from AMPCTLOC READ

Explanation:

Internal error.

User response:


Technical Support.

BKMK0107E AEF record not found

Explanation:

Filter record not found.

User response:

Check the filter display (universal, global, and local)

panels before contacting Technical Support.

BKMK0108E Database read error RC=

Explanation:

VSAM READ error.

User response:


Technical Support.

BKMK0109E AMPGETGN call failed

Explanation:

Failure attempting to retrieve GDG catalog information.

User response:


Technical Support.

BKMK0110E No usable GDG info

Explanation:

Catalog retrieval should have returned GDG info.

User response:


Technical Support.

BKMK0111E AMPGETGN returned too much

Explanation:

Catalog retrieval returned more than expected.

User response:


Technical Support.

BKMK0112E Database open error RC=

Explanation:

Error opening database.

User response:


Technical Support.

BKMK0113E Database CLOSE error RC=

Explanation:

Error closing database.

User response:

IBM Confidential

163


Technical Support.

BKMK0114E Database SEQ READ error RC=

Explanation:

Error reading database.

User response:


Technical Support.

BKMK0115E Application master record not found

Explanation:

Application master record not found.

User response:

From the main menu, look for the application in the ’list

applications’ option before contacting technical support.

BKMK0116E Database READ error RC=

Explanation:


User response:


Technical Support.

BKMK0117E Application APV record not found

Explanation:

The APV record, created/changed via the application

setup panel, is missing.

User response:

Entering and leaving the application setup panel will

verify or create the APV record. Contact Technical

Support if this does not correct the problem.

BKMK0118E Start record key not found

Explanation:

VSAM start forward key not found.

User response:


Technical Support.

BKMK0119E Database start error RC=

Explanation:

VSAM start forward failed.

User response:


Technical Support.

BKMK0120E Call to AMPLOCAT failed

Explanation:

Catalog lookup routine failed.

User response:


Technical Support.

BKMK0121E AMPGETGN call failed see other

messages

Explanation:

Catalog GDG lookup routine failed.

User response:


Technical Support.

BKMK0122E BKMFLTLD load failed RC:

Explanation:

Filter load program failed.

User response:


Technical Support.

BKMK0123E Bad return code from BKMFLTSR input

DSN to BKMPFLTR:

Explanation:

Filter search routine failed.

User response:


Technical Support.

BKMK0124E Filter scope from BKMFLTSR incorrect

Explanation:

Filter search routine returned invalid filter scope.

User response:


Technical Support.

BKMK0125E Filter error in BKMPFLTR

Explanation:

Internal error.

User response:


Technical Support.

BKMK0126E Incorrect filter type from BKMFLTSR

Explanation:

Internal error.

User response:


Technical Support.

BKMK0114E • BKMK0126E IBM Confidential


BKMK0127E BKMFLTLD del failed RC:

Explanation:

Internal error.

User response:


Technical Support.

BKMK0128E DSR record not passed to BKMPPREP

Explanation:

Internal error.

User response:


Technical Support.

BKMK0129E Call to BKMPPREP failed call

BKMPPREP RC: nnnnnnnn BKMPPREP

parm: ’DSR key’

Explanation:

Internal error.

User response:


Technical Support.

BKMK0130E Database insert error RC=

Explanation:

VSAM error inserting a record.

User response:


Technical Support.

BKMK0131E Database rewrite error RC=

Explanation:

VSAM error rewriting a record.

User response:


Technical Support.

BKMK0132E DSR record not found

Explanation:

Expected DSR record not found.

User response:


Technical Support.

BKMK0132E BKM01VSI error RC=

Explanation:

Internal error.

User response:


Technical Support.

BKMK0135E Invalid rel DSN

Explanation:

Invalid GDG relative DSN.

User response:


Technical Support.

BKMK0136E ACS compare failed: DSN compared:

ARG compared:

Explanation:

ACS DSN to ARG comparison failed.

User response:


Technical Support.

BKMK0137E BKMCATEX format error

Explanation:

Internal error.

User response:


Technical Support.

BKMK0138E BKMCATEX INIT error

Explanation:

Internal error.

User response:


Technical Support.

BKMK0140E BKMCATEX sendmask error

Explanation:

Catalog lookup module received unexpected data.

User response:


Technical Support.

BKMK0141E BKMCATEX GET error

Explanation:

Internal error.

User response:


Technical Support.

BKMK0142E INI GET error. RC =

Explanation:

Error retrieving information for INI parmlib member.

User response:

See other errors for explanation of the problem.

BKMK0127E • BKMK0142EIBM Confidential


BKMK0143W SPACE_MANAGEMENT token error

Explanation:

Missing or incorrect syntax for space management

token.

User response:

See other errors for explanation of the problem.

BKMK0144E Missing space management token data

Explanation:


token.

User response:

Add space management token information or correct

syntax.

BKMK0145E Space management data not valid

Explanation:


token.

User response:


syntax.

BKMK0146W MCDS_ERROR_RC token error

Explanation:

Missing or incorrect syntax for MCDS_ERROR_RC

token.

User response:


syntax.

BKMK0147E MCDS return code data not valid

Explanation:

Missing or incorrect syntax for MCDS_ERROR_RC

token.

User response:

Add MCDS return code token information or correct

syntax.

BKMK0148E DSR rec table readnext failed. RC =

nnn

Explanation:

Internal error.

User response:


Technical Support.

BKMK0149E DSR rec table point failed. RC = nnn

Explanation:

Internal error.

User response:


Technical Support.

BKMK0150E DSR rec table write failed. RC = nnn

Explanation:

Internal error.

User response:


Technical Support.

BKMK0151E DSR rec table rewrite failed. RC = nnn

Explanation:

Internal error.

User response:


Technical Support.

BKMK0152E DSR rec table read failed. RC = nnn

Explanation:

Internal error.

User response:


Technical Support.

BKMK0153E DSR rec table read failed. RC = nnn

Explanation:

Internal error.

User response:


Technical Support.

BKMK0201E APPLNAME parameter missing

Explanation:

Internal error.

User response:


Technical Support.

BKMK0202E APPLNAME parameter too long

Explanation:

Internal error.

User response:


Technical Support.

BKMK0143W • BKMK0202E IBM Confidential


BKMK0203W SDS built but not valid for ABARS

Explanation:

A selection data set has been created, but it is unlikely

it is usable.

User response:

Review the selection data set. Also, look for other error

messages that might explain the problem.

BKMK0204E Selection data set not built

Explanation:

A selection data set could not be built because of major

errors.

User response:

Look for other error messages that will give more

information.

BKMK0205E Selection data set sort failed

Explanation:

The sort did not complete successfully.

User response:

Look for other error messages that will give more

information.

BKMK0206E No include data sets for backup

Explanation:

There must be at least one include data set in the

selection data set.

User response:

No data gathered for this application or all data sets

have been excluded by the evaluation process.

BKMK0213E Database read error RC=xxx

Explanation:

Internal error.

User response:


Technical Support.

BKMK0215E Database seq read error RC=xxx

Explanation:

Internal error.

User response:


Technical Support.

BKMK0224E INCLUDE has wrong evaluation status

xxxxxxxx

Explanation:

Internal error.

User response:


Technical Support.

BKMK0225E Verify selection DSN missing xxxxxxxx

Explanation:

Selection data set name is invalid or not provided.

User response:

Make sure a verify data set name has been provided.

BKMK0225E ALLOCATE has wrong evaluation

status xxxxxxxx

Explanation:

Internal error.

User response:


Technical Support.

BKMK0226E Invalid verify selection data set name

xxxxxxxx

Explanation:

Selection data set name is invalid.

User response:

Make sure a verify data set name has been specified

correctly.

BKMK0226E ACCOMPANY has wrong evaluation

status xxxxxxxx

Explanation:

Internal error.

User response:


Technical Support.

BKMK0227E DATE CONVERSION ROUTINE ERROR

Explanation:

Internal error.

User response:


Technical Support.

BKMK0228E DB action type incorrect

Explanation:

Internal error.

User response:


Technical Support.

BKMK0203W • BKMK0228EIBM Confidential


BKMK0228E EXCLUDE has wrong evaluation status

xxxxxxxx DSN:

Explanation:

Internal error.

User response:


Technical Support.

BKMK0229E SI040DC0 call error RC=xxx

Explanation:

Internal error.

User response:


Technical Support.

BKMK0229E Unknown status type xxxxxxxx DSN:

Explanation:

Internal error.

User response:


Technical Support.

BKMK0230W No DSR records in database

Explanation:

RSP has not collected any SMF or UJI data.

User response:

RSP must be collecting data before a selection data set

can be created.

BKMK0231E No DSR records for selected appl

Explanation:

RSP has not collected any SMF or UJI data for the

application.

User response:

RSP must be collecting data for an application before a

selection data set can be created.

BKMK0232E Start record key not found

Explanation:

Internal error.

User response:


Technical Support.

BKMK0233E Sel ds allocation failed xxxxxxxxxxxx

xxxxxxxxxxxxxxxxxxxxxxx

Explanation:

Selection data set allocation failed.

User response:

The reason for the failure should be a part of the

message.

BKMK0233E E35 Sel DS allocation failed. E35 00001

E SVC99 Allocate R15=xx; Error=xxx;

Info=xxx DDname=SELECTDD

Explanation:

SVC99 failure for selection dataset.

User response:



BKMK0234E Database rewrite error RC=xxx

Explanation:

Internal error.

User response:


Technical Support.

BKMK0235E Database start error RC=xxx

Explanation:

Internal error.

User response:

Please report this message, with the error text issued,

to Technical Support.

BKMK0236E Application not found xxxxxxxx.

Explanation:

Internal error.

User response:



BKMK0301E No parm passed.

Explanation:

No parameters passed to BKMAPLEN from the EXEC

statement.

User response:

BKMAPLEN requires at least the ’APPL’ parameter.

BKMK0302E Parm syntax error.

Explanation:

Syntax of BKMAPLEN parameters is incorrect.

User response:

Check manual or sample BKMAPLEN member in JCL

library.



BKMK0303E Internal error processing BKMAPLEN

parameters.

Explanation:

Internal error.

User response:


BKMK0304I Update/Noupdate no longer valid -

ignored.

Explanation:

Obsolete parameter.

User response:

Remove obsolete parm to eliminate this message.

BKMK0305E SELREBUILD/NOSELREBUILD mutually

exclusive.

Explanation:

Mutually exclusive parameters.

User response:

Select one or the other.

BKMK0306I NUPDATE is not valid, SELREBUILD

OK.

Explanation:

NOUPDATE is obsolete; SELREBUILD recognized.

User response:

Remove NOUPDATE parm to eliminate this message.

BKMK0307E CYCLEINC/CYCLENOINC mutually

exclusive.

Explanation:

Mutually exclusive parameters.

User response:

Select one or the other.

BKMK0310E Auto delete failed for application.

Explanation:

Deletion of previous cycle’s data failed.

User response:

Should have messages from BKMDSDDE. If not

solvable, call Technical Support.

BKMK0311I Successful selection build.

Explanation:

Selection data set build without errors.

User response:

None; informational message.

BKMK0312W Selection dataset build with errors.

Explanation:

The selection data set will likely cause backup failures.

User response:

From other messages determine the cause of the error.

Examine the SDS for cause of problem, possibility all

data sets excluded by filters.

BKMK0313E Errors prevented selection dataset

build.

Explanation:

Another error stopped the build process.

User response:

From other messages, determine the cause of error. If

not correctable, call Technical Support.

BKMK0314W Selection data set build not

requested

Explanation:

Caused by BKMAPLEN parm.

User response:

None unless SDS desired.

BKMK0315W U83 exit not active for SYSID.

Explanation:

BKMSTSKR is not running or a problem was


User response:

The application might be missing information from this


analyst.

BKMK0316W Database update task not active for

SYSID.

Explanation:



System action:

User response:






errors, the message BKM01010E ABNORMAL

TERMINATION OF RSP9254S will appear in the log

along with other messages identifying the precise

reason for the abnormal termination.

BKMK0303E • BKMK0316WIBM Confidential


BKMK0317W Database update task is doing no

work for SYSID.

Explanation:



User response:



(RSP9254S) that might indicate the nature of the

problem. BKMAPLEN will continue processing, but the



BKMK0318W No response from database update

task for SYSID.

Explanation:

The task which writes the SMF records to the database


User response:



(BKMRUPDT) that might indicate the nature of the

problem. BKMAPLEN will continue processing, but the

application might b e missing information from this


analyst.

BKMK0319E Application not found in database.

Explanation:



User response:

Check that the APPLNAME in the parm is correct or

that the application has indeed been created.

BKMK0320I APPLEND started for application.

Explanation:

APPLEND processing started.

User response:

None; informational only.

BKMK0321I Cycle number increased for

application.

Explanation:

The RSP cycle number for this cycle’s worth of SMF


User response:


BKMK0322I Buffer flush requested for application.

Explanation:



User response:


BKMK0323I Buffer flush acknowledge for

application.

Explanation:


User response:


BKMK0324I Buffer flush satisfied for application

Explanation:


User response:


BKMK0325I Auto delete successful for application.

Explanation:

Previous cycles of DSD records successfully deleted.

User response:


BKMK0326I DSD to DSR conversion for

application.

Explanation:

RSP records merged with JCL records to create new

set of DSR records.

User response:

None.

BKMK0327E DSR evaluation not completed.

Explanation:

An error occurred evaluating the DSR records.

User response:


BKMK0328E Free of DDNAME RSPMSGQ failed.

Explanation:

SVC99 failure.

User response:

Note SVC99 failure code. If not solvable, contact

Technical Support.



BKMK0329E BKMSTSKR not active.

Explanation:

BKMSTSKR is not active on this image.

User response:

BKMSTSKR must be active on the image running the

APPLEND step. Check for other log messages.

BKMK0330E NAMETOKEN fetch failed.

Explanation:


User response:


BKMK0331E Failure allocating DDNAME RSPMSGQ

to data set.

Explanation:

SVC99 failure.

User response:

See SVC99 reason code. Problem is likely user

solvable.

BKMK0332E RSP msg queue not formatted

correctly. Expected RSPMSG in 1st 16

slots.

Explanation:


User response:

Check that JCL member BKMMQBLD has been run.

BKMK0336W Error fetching

SDS_FLTR_OVERRIDES_CAT,

R15=nnnnn

Explanation:

An error occurred reading parmlib member INI. The

token is SDS_FLTR_OVERRIDES_CAT. The default

value of ’N’ will be used for selection data set build.

User response:

Check that the INI token is correctly specified.

BKMK0337W Invalid length

SDS_FLTR_OVERRIDES_CAT,

LEN=nnnnn

Explanation:

The length specified for the token in PARMLIB member

INI is invalid. The token is

SDS_FLTR_OVERRIDES_CAT. The default value of ’N’

will be used for selection data set build.

User response:

Check that the INI token is correctly specified.

BKMK0338E DSR load to database failed.

Explanation:

An error occurred while loading the DSR records.

User response:


BKMK0338I DSR load to database completed

successfully.

Explanation:

DSR records were successfully loaded.

User response:

None; informational message.

BKMK0401E HDR1 record not in jobflat file.

Explanation:

Bad JOBFLAT file.

User response:

Check if job flat build (RSPBLDJB) ran successfully. If it

completed with no errors, report this message, with the

error text issued, to Technical Support.


Explanation:

Bad JOBFLAT file.

User response:


completed with no errors, report this message, with the

error text issued, to Technical Support.


Explanation:

Bad JOBFLAT file.

User response:


completed with no errors, report this message with the

error text issued to Technical Support.

BKMK0404I RSP job table loading into area 1.

Explanation:


User response:

None.

BKMK00405I RSP job table loading into area 21

Explanation:


User response:

None.

BKMK0329E • BKMK00405IIBM Confidential



Explanation:

Bad JOBFLAT file.

User response:





Explanation:

Bad JOBFLAT file.

User response:




BKMK0408E Jobflat record count invalid.

Explanation:

Bad JOBFLAT file.

User response:




BKMK0409E Job names exceed dataspace table.

Explanation:

Data space is not large enough to hold job table.

User response:



BKMK0410I Job names table will hold: nnnnnnnn

Explanation:


User response:

None.

BKMK0411I Job name count in jobflat file:nnnnnnnn

Explanation:


User response:

None.

BKMK0412E Bad table ptr in dataspace.

Explanation:

Data space area has been corrupted.

User response:



BKMK0500E Exit area exists. Must unload first.

Explanation:

U83 exit already exists.

User response:

If you want to recreate it, you must unload the exit first.

BKMK0501E Cannot open EXITLIB.

Explanation:

A problem with the load libraries defined in the INI

parmlib member.

User response:

Make sure the dataset name is correct for each load

library in the INI parmlib member.

BKMK0502E C X-CSA storage not available

Explanation:

Insufficient virtual storage.

User response:


Technical Support.

BKMK0503I X-CSA located at: nnnnnnnn Length:

nnnnnnnn

Explanation:


User response:

None.

BKMK0504E Unable to load primary exit. Load RC=

Explanation:

Problem loading exit programs.

User response:



BKMK0505E Name token creation failed. IEANTCR

RC=

Explanation:

Internal error.

User response:



BKMK0506I X-CSA built and identified.

Explanation:


User response:

None.

BKMK0406E • BKMK0506I IBM Confidential


BKMK0507E Unable to load primary exit. LOAD

RC=xxx REASON=

Explanation:

Internal error.

User response:



BKMK0508I Secondary exit loaded successfully.

Explanation:


User response:

None.

BKMK0509E Exit area does not exist.

Explanation:

Unload failed because exit area does not exist.

User response:

None.

BKMK0510E Unable to free X-CSA. FREEMAIN RC=

Explanation:

Internal error.

User response:



BKMK0511E Exit area removed.

Explanation:


User response:

None.

BKMK0512E Cannot remove exit with dataspace

active.

Explanation:

Correctable error.

User response:

The dataspace buffer area must be removed before the

U83 exit is removed.

BKMK0513E Cannot turn on exit without dataspace

active.

Explanation:

Correctable error.

User response:

The dataspace buffer area must be created before the

U83 exit is turned on.

BKMK0514E Secondary exit already active.

Explanation:


User response:

Start up failed because the task is already active.

BKMK0515E Secondary exit active.

Explanation:


User response:

None.

BKMK0516E Secondary exit not active.

Explanation:


User response:

None.

BKMK0517E Secondary exit deactivated.

Explanation:


User response:

None.

BKMK0518I Secondary exit Active/Dormant; Data

space Exists/Does not exist; VSAM

subtask.

Explanation:


User response:

None.

BKMK0519E Cannot load new secondary exit while

existing exit is turned on.

Explanation:

Correctable error.

User response:

Turn off secondary exit before attempting to load a new

one.

BKMK0520I Secondary exit reloaded successfully.

Explanation:


User response:

None.



BKMK0521I SMF xxxxxxxxxxxx complete for:

U83ExitName.

Explanation:


User response:

None.

BKMK0522I SMF dynamic exit facility xxxxxxx

RC=xx REASON=

Explanation:


User response:

None.

BKMK0523I SMF separation complete.

Explanation:


User response:

None.

BKMK0524E Unable to separate from SMF. RC=xx

Reason=xxxx

Explanation:

Internal error.

User response:



BKMK0526E Cannot xxxxxxxx exit; no exits defined

to MVS.

Explanation:

Internal error.

User response:



BKMK0527I There were more/less exits deleted

than installed.

Explanation:


User response:

None.

BKMK0528E Job name table not created.

Explanation:

Internal error.

User response:



BKMK0538E Token LOAD x DSN xxxxxxxxxxxx

request failed; R15=xx SVC99

Data:xxxxxxxx

Explanation:

Internal error.

User response:



BKMK0539E ddname xxxxxxxxxxxx Request failed;

R15=xx SVC99 Data:

Explanation:

Internal error.

User response:



BKMK0540E BKM01FS0 LOAD module query failed.

RC=xx.

Explanation:

Internal error.

User response:



BKMK0541E Unable to load BKM01FS0/secondary

exit. Load RC=xxx Reason=

Explanation:

Internal error.

User response:



BKMK0600E Unable to make non swapable

sysevent RC=xx

Explanation:

Internal error.

User response:



BKMK0601E Unable to xxxxxxxx dataspace.

DSPSERV RC=xx

Explanation:

Internal error.

User response:



BKMK0521I • BKMK0601E IBM Confidential


BKMK0602E Unable to xxxxxxxx ALET. ALESERV

RC=xx

Explanation:

Internal error.

User response:



BKMK0603I Dataspace created Buf count z,zzz,zzz

Origin xxxxxxxx Size z,zzz,zzzk

Explanation:


User response:

None.

BKMK0604I Data space removed.

Explanation:


User response:

None.

BKMK0605E Must install exit before manipulating

dataspace.

Explanation:

Correctable error.

User response:


be installed first.

BKMK0606E Dataspace already exists.

Explanation:

Correctable error.

User response:


recreate it.

BKMK0607E Data space does not exist.

Explanation:


User response:

None.

BKMK0608E Cannot delete data space with exit

turned on.

Explanation:

Correctable error.

User response:


be turned off.

BKMK0609I Buffer value not valid, using default.

Explanation:


User response:

None.

BKMK0610I Buffer value excessive. Using 32MB of

buffers.

Explanation:


User response:

None.

BKMK0611I Internal dataspace ID is bad; resetting

internal ID.

Explanation:


User response:

None.

BKMK0612E Dataspace create for job table failed.

Explanation:

Internal error.

User response:



BKMK0613E Dataspace delete for job table failed.

Explanation:

Internal error.

User response:



BKMK0614E Dataspace create for FLT table failed.

Explanation:

Internal error.

User response:



BKMK0720I VSAM subtask exists.

Explanation:


User response:

None.



BKMK0721E VSAM subtask failed to start. RC=xx

Explanation:

Internal error.

User response:



BKMK0722I VSAM subtask started; using

Explanation:


User response:

None.

BKMK0723E Must load exit area before starting

subtask.

Explanation:

Correctable error.

User response:

The U83 must be loaded before the database update

task can be started.

BKMK0724E Internal dataspace ID is bad. Need

valid ID.

Explanation:

Correctable error.

User response:

Unload U83 exit. Load it again. Try to start database

subtask. If the same message is received, report this

message with the error text issued to Technical Support.

BKMK0725E Must create dataspace before starting

subtask.

Explanation:

Correctable error.

User response:

The RSP tasks must be started in the correct order.

Review the documentation and try again.

BKMK0730E VSAM subtask does not exist.

Explanation:

Correctable error.

User response:

The KILL command was issued, but the database

update task is not running. Check for a task ABEND. If

there is no ABEND, the task was stopped previously.

BKMK0731E VSAM subtask not responding.

Explanation:


User response:

Use KILL command to stop the task.

BKMK0732I VSAM subtask stopped.

Explanation:


User response:

None.

BKMK0733I VSAM subtask destroyed.

Explanation:


User response:

None.

BKMK0739E RSP monitor command subtask exists.

Explanation:

Correctable error.

User response:

Stop the BKMSTSKR task using STOPALL command


BKMK0740W RSP monitor command subtask not

responding.

Explanation:


normally.

User response:

None.

BKMK0741I RSP monitor command subtask

stopped.

Explanation:


User response:

None.


destroyed.

Explanation:


User response:

None.



BKMK0743E RSP monitor command subtask does

not exist.

Explanation:

Internal error.

User response:



BKMK0744E RSP monitor command subtask failed

to start.RC=nn.

Explanation:

Internal error.

User response:



BKMK0745E Overflow export subtask exists.

Explanation:

Correctable error.

User response:



BKMK0746W Overflow export subtask not

responding.

Explanation:


normally.

User response:

None.

BKMK0747I Overflow export subtask stopped.

Explanation:


User response:

None.

BKMK0748E Overflow export subtask destroyed.

Explanation:


User response:

None.

BKMK0749I Overflow export subtask does not

exist.

Explanation:

Unexpected event but shut down show proceed

normally.

User response:

None.

BKMK0750E Overflow export subtask failed to start.

RC=nn

Explanation:

Internal error.

User response:



BKMK0751E Overflow import subtask exists.

Explanation:

Correctable error.

User response:



BKMK0752I Overflow import subtask not

responding.

Explanation:


normally.

User response:

None.

BKMK0753I Overflow import subtask stopped.

Explanation:


User response:

None.

BKMK00754E Overflow import subtask destroyed.

Explanation:


User response:

None.

BKMK0755I Overflow import subtask does not

exist.

Explanation:


normally.

User response:

None.

BKMK0756E Overflow import subtask failed to

start.RC=nn

Explanation:

Internal error.

User response:





BKMK0757I Overflow import subtask started.

Explanation:


User response:

None.

BKMK0758I Overflow export subtask started.

Explanation:


User response:

None.


started.

Explanation:


User response:

None.

BKMK0800E Shut down complete.

Explanation:


User response:

None.

BKMK0801E Errors occurred during shut down.

Explanation:


User response:

None. Any errors should be corrected with RSP is

restarted.

BKMK0802E Autostart complete.

Explanation:


User response:

None.

BKMK0803E Errors occurred during autostart.

Explanation:


User response:

Please refer to previous error messages from RSP

tasks.

BKMK0810E Error retrievingxxxxxxxxxxxxxxxx info

from //INI. R15= xxxx

Explanation:

Incorrect variable format.

User response:

Check AUTOSTART variable in INI. Ensure that ’ (*)’

follows variable value. At least one space must be

inserted before the ’(*)’.

BKMK0811E BKMSTSKR initialization

valuesxxxxxxxxxxxxxxxx

Explanation:

Internal error.

User response:



BKMK0812E Overflow DSN not found for SYSID

xxxx

Explanation:

No overflow file in INI for SYSID.

User response:

Put overflow DSN in the INI for this SYSID. Every

image that is running RSP must have its own overflow

data set.

BKMK0813E Too many overflow file allocation


Explanation:

Correctable error.

User response:

Remove unnecessary allocation parameters. LRECL,

DSORG and RECFM do not need to be defined.

BKMK0814E Substitution error on INI

variablesxxxxxxxxxxxxxxxx

Explanation:

Internal error.

User response:



BKMK0815E Syntax error for INI

parmxxxxxxxxxxxxxxxx

Explanation:

Correctable error.

User response:

Review documentation for correct parm syntax.



BKMK0901E Unexpected return code (xx) from xxx

IEANT

Explanation:

Internal error.

User response:



BKMK0903I ADR: xxxxxxxx Date: xxxxxxxx Time:

xxxxxxxx

Explanation:


User response:

None.

BKMK0904E QEDIT nonzero return

code.xxxxxxxxRC=xx.

Explanation:

Internal error.

User response:



BKMK0905E Cannot get message system lock.

Explanation:

Internal error.

User response:



BKMK0906E RSP cannot execute unauthorized.

Explanation:

Correctable error.

User response:

The load modules must reside in an authorized library.

BKMK0907E Another BKMRSMFT is executing. It

was started YYYY/MM/DD HH.MM.SS

Explanation:

Correctable error.

User response:

Two RSP tasks cannot be executing on the same

image. One RSP must be stopped before another one

can be started.

BKMK0908E //EXEC..PARM=″DATA IGNORED.

Explanation:

Correctable error.

User response:

RSP was started with bad parm data. Stop RSP.

Correct the data, and restart RSP.

BKMK0909E ″TEST″ operand must be 3 characters.

Explanation:

Correctable error.

User response:

Fix test name. Stop and restart RSP.

BKMK0910I TEST(xxx) accepted.

Explanation:


User response:

None.

BKMK0911I Secondary BKMRSMFT responding;

ID=xxx

Explanation:


User response:

None.

BKMK0912I BKMRSMFT: build &SYSDATC

&SYSTIME

Explanation:


User response:

None.

BKMK0913E ″SYSID″ operand must be 1-4

characters, using system SMF ID of

xxxx

Explanation:

Correctable error.

User response:

RSP was started with bad parm data. Stop RSP.

Correct the data, and restart RSP.

BKMK0914I SYSID(xxxx) accepted.

Explanation:


User response:

None.

BKMK0915E Message queue allocate failed.

Explanation:

Correctable error.

User response:

See message BKMK0925E for further details. Correct

the error and restart RSP.



BKMK0916E Message queue open failed.

Explanation:

Correctable error.

User response:

Look for MVS system messages for the cause of the

open failure. Correct the error and restart RSP.

BKMK0918E All RSP slots filled in message queue.

Explanation:

Correctable error.

User response:

Unused SYSIDS must be removed from the

MSGQUEUE file. Please contact Technical Support for

further instructions.

BKMK0919E Message queue data set not formatted.

Explanation:

Correctable error.

User response:

The member BKMMQBLD in the JCL library must be

executed to format the message queue data set.

BKMK0920E Message queue deallocate failed.

Explanation:

Correctable error.

User response:

See message BKMK0925E for further details.

BKMK0921E Overflow allocate failed.

Explanation:

Correctable error.

User response:

See message BKMK0925E for further details. Correct

the error and restart RSP.

BKMK0922E Overflow deallocate failed.

Explanation:

Correctable error.

User response:

See message BKMK0925E for further details.

BKMK0923E Overflow open failed.

Explanation:

Correctable error.

User response:

Look for MVS system messages for the cause of the

open failure. Correct the error and restart RSP.

BKMK0924I No MVS exit selected for use by RSP.

Explanation:


User response:

RSP will not process any data from a U83 or a UJI exit

because of user request.

BKMK0925E xxxxxxxxxxxxxxxxxxxxxxxxx

xxxxxxxxxxxxxxxxxxxxxxxx

Explanation:

Correctable error.

User response:

This message gives the details of the allocate error.

Correct the error and restart RSP.

BKMK1001E Unexpected return code (xx) from

IEANT xx.

Explanation:

Internal error.

User response:



BKMK1002E Cannot get message system lock.

Explanation:

Internal error.

User response:



BKMK1003E SI040DC0 interface disabled.

Explanation:

Internal error.

User response:



BKMK1005E Application cycle table is too large.

Explanation:

Internal error.

User response:



BKMK1006E Invalid filter type for APPxxxxxxxx filter

dataxxxxxxxxxx.

Explanation:

Internal error.

User response:





BKMK1007E Application missing in APV cycle

tablexxxxxxxx.

Explanation:

The application is in the job table, but not in the

database.

User response:

After deleting applications from the database, the job

RSPJRFSH must be run to update the job table.

BKMK1008E Call to ASPFLTLD failed.

Explanation:

Internal error.

User response:



BKMK1009E Call to RSPGETJB failed.

Explanation:

Internal error.

User response:



BKMK1010E Abnormal termination of BKMRUPDT

Explanation:

The database update task has shut down because of a

major error.

User response:


problem, then report to Technical Support.

BKMK1011I Unexpected SMF record type in

dataspace.

Explanation:

Bad data is in the SMF record data space.

User response:

The database update task continues to process after

dropping the bad record, but report incident to Technical

Support.

BKMK1012I More than 1023 applications for job

xxxxxxxx excess applications ignored.

Explanation:

There is a limit of 1024 applications for a job.

User response:

The most probable cause is that the job table has been

set up incorrectly. Report to Technical Support.

BKMK1014E Data base error, xxx record not found.

Explanation:

Internal error.

User response:



BKMK1015E Message queue allocate failed.

Explanation:

Internal error.

User response:



BKMK1016E Message queue open failed.

Explanation:

Internal error.

User response:



BKMK01017E Message queue deallocate failed.

Explanation:

Internal error.

User response:



BKMK1018I Waiting for access to msgqueue RSP

records.

Explanation:

Resource contention without other tasks.

User response:

Database update tasks continue proceessing, but this is

a potential problem. Please report this message with the


BKMK1101E Parm length invalid, found: nn.

Explanation:

The program was passed an invalid parameter.

User response:



BKMK1102E Parm byte 9 not R or S: xx

Explanation:


User response:





BKMK1103E RSP UJI error collecting JCL data:

error information from RSP UJI exit.

Explanation:

An error occurred while the RSP UJI exit was

processing a job for this application. The selection data

set was built, but might be missing JCL information.

User response:



BKMK1106E Application APV record not found.

Explanation:



User response:




BKMK1111E First 77 bytes of buffer: record key

Explanation:

Unanticipated VSAM I/O error.

User response:

Please report this message with any other related error

messages to Technical Support.

BKMK1112I BKMEVALA merging data set detail

records for APPL: applname.

BKMEVALA merging JCL records from

cycle: n. BKMEVALA merging SMF

records from cycle: n. BKMEVALA

merging RSP records from cycle: n.

BKMEVALA merging RSP records

through cycle: n. BKMEVALA JCL

detail records used: n. BKMEVALA JCL

detail records ignored: n. BKMEVALA

RSP detail records used: n.

BKMEVALA RSP detail records

ignored: n. BKMEVALA SMF detail

records used: n. BKMEVALA SMF

detail records ignored: n.

Explanation:

During the build of a selection data set, data set detail

records are merged from JCL, batch SMF, and RSP

SMF. These messages display the cycles to be included

and counts of records used. SMF refers to batch SMF

collection. RSP refers to SMF collection via the RSP

real-time collection system.

User response:

If statistics reveal undesired records being used, check

the setup option for RSP cycles to be included and

check when building the SDS from ISPF whether SMF

records are to be used from RSP or batch SMF scan.

BKMK1113E DSR REC table WRITE error. RC=nnnn

Explanation:

Internal error.

User response:



BKMK1301E Parm length not 9.

Explanation:

Internal error.

User response:


Technical Support.

BKMK1302E Invalid parm byte 9.

Explanation:

Internal error.

User response:


Technical Support.

BKMK1303E DB open error. RC=

Explanation:

Error opening the database.

User response:


Technical Support.

BKMK1304E DB close error. RC=

Explanation:

Error closing the database.

User response:


Technical Support.

BKMK1305E Application control record not found.

Explanation:



User response:




BKMK1306E DB read error. RC=

Explanation:


User response:


Technical Support.



BKMK1307E Start record key not found.

Explanation:

Internal error.

User response:


Technical Support.

BKMK1308E DB start error. RC=

Explanation:

Internal error.

User response:


Technical Support.

BKMK1309E SI040DC0 DEL error RC=

Explanation:

Error deleting a record.

User response:


Technical Support.

BKMK1310E SI040DC0 error RC=

Explanation:

Internal error.

User response:


Technical Support.

BKMK1311I Deleting DSD records for APPL:

Current cycle:nnnnnnnnn Number of

cycles to retain nnnn Deleting cycles

less than: nnnnnnnnnn DSD records

deleted: nnnnnnnnnn DSD records

retained:nnnnnnnnnn

Explanation:

Informational messages detailing the deletion of data

set detail records.

User response:

None.

BKMK1501E Invalid parm.

Explanation:

Internal error.

User response:


Technical Support.

BKMK1502E Data dict SI27 table create failed

RC=nnnn

Explanation:

Internal error.

User response:


Technical Support.

BKMK1503E Return code not zero, see other

messages.

Explanation:


User response:

Please see accompanying messages, which should

explain the problem.

BKMK1504W Error fetching INI token

SDS_STOP_SHARE

Explanation:

Internal error.

User response:

Although the job may run to completion, please report

this message with the error text issued to Technical

Support.

BKMK1505W Token SDS_STOP_SHARE not valid.

Explanation:

Internal error.

User response:

Although the job might run to completion, please report


Support.

BKMK1506W Error fetching INI token

SDS_FLTR_OVERRIDES_CAT.

Explanation:

Internal error.

User response:



Support.

BKMK1507W Token SDS_FLTR_OVERRIDES_CAT

not valid.

Explanation:

Internal error.

User response:



Support.



BKMK1508E INI build failed. See other messages.

Explanation:


User response:

Please see accompanying messages, which should

explain the problem.

BKMK2001E Unable to open files.

Explanation:

The program was unable to open a required file.


User response:

Please report this message to Technical Support. The

JES SYSOUT for the job should indicate the missing

DDNAME.

BKMK2002W Invalid data found: Field=fffffff

Event#=nnnn Invalid data: hexadecimal

data *Character data*

Explanation:

Invalid data was found in the ZEKE database. The field,

fffffff, will be ’JOB NAME’, ’APPLICATION’, ’GROUP ID’,

or ’EVENT NAME’. The event#, nnnn, is the event

number in ZEKE. The invalid data is printed in

hexadecimal and character format. Processing

continues.

User response:

The field with invalid data should be corrected in ZEKE,

in order to fully use job collection.

BKMK2003W Event has been skipped.

Explanation:

This message follows BKMK2002W if the field with

invalid data was the jobname. A valid jobname is

required. Processing continues.

User response:

Correct the ZEKE event displayed in message

BKMK2002W.

BKMK2004W Field replaced with spaces.

Explanation:

This message follows BKMK2002W if the field with

invalid data was the ZEKE application, ZEKE

GROUPID, or ZEKE event name. If the job collection

criteria uses the invalid field, the job will not be

selected. Processing continues.

User response:

Correct the ZEKE event displayed in message

BKMK2002W.

BKMK2005W Unable to print data, R15=nnnn

Explanation:

An error occurred trying to print the invalid data field.

nnnn is the return code from the formatting routine,

SI017DC1. Processing continues.

User response:

Please notify Technical Support if this warning is issued.

BKMK2006W Error terminating SI017, R15=nnnn

Explanation:

An error occurred trying to ’clean-up’ the formatting

routine, SI017DC1. nnnn is the return code from the

formatting routine. Processing continues.

User response:

Please notify Technical Support if this warning is issued.

BKMK2301E Unable to open files.

Explanation:


User response:



DDNAME.

BKMK2302E Invalid parameter: errortext.

Explanation:

The parameter passed to the program was incorrect.

User response:

Please report this message with the error text to

Technical Support.

BKMK2303E Problem with predecessor for

EVENTNAME.

Explanation:

The predecessor for EVENTNAME had an incorrect

length.

User response:

Please report this message to Technical Support. Have

the ZEKEIN file available for problem determination.

BKMK2304E Error from SI024 errortext.

Explanation:

The filter routine SI024 detected an error.

User response:

Please report this message with the ’ERROR TEXT’ to

Technical Support. Have the ZEKEIN file available for

problem determination.



BKMK2305E No jobs selected for application

application name.

Explanation:

No jobs matched the specified selections.

User response:

Check that the ’JOB’, ’ENAME’, ’ZAPL’, and ’GROUP’

entries specified for the application are correct. If further

assistance is required, contact Technical Support.

BKMK2306E Error fetching //SISPARM info.

Explanation:

The internal call to SI030DC0 to read parmlib member

INI failed. R15 is the return code from SI030DC0.

User response:

Check that DD //SISPARM in the JCL is pointing to the

correct product parmlib data set name and member INI.

For further assistance, contact Technical Support.

BKMK2307W Error fetching token, R15: nnnn;

Default for

JOBCOLL_ZEKE_ABNORMAL_JOBS

will be used.

Explanation:

A problem occurred retrieving token

JOBCOLL_ZEKE_ABNORMAL_JOBS. The default of N

will be used.

User response:

None required.

BKMK2308W Value for token,

JOBCOLL_ZEKE_ABNORMAL_JOBS is

invalid; default will be used.

Explanation:

The value specified for the token is incorrect. The

default of N will be used.

User response:

None required, unless Y was desired.

BKMK2309I Abnormal job events will be included.

Explanation:

The value specified for token

JOBCOLL_ZEKE_ABNORMAL_JOBS was ’Y’.

Abnormal job events will be included during ZEKE job

collection.

User response:

None.

BKMK2310I Number of job events included: nnnnn

Explanation:

The number of job events found in ZEKE that match the

specified collection criteria. This might not reflect the

actual number of jobs saved in the database; a jobname

can be duplicated in ZEKE.

User response:

None.

BKMK2311I Zeke selection for application

APPLICATION: ZEKE application

name(s) EVENT: ZEKE event name(s)

GROUP: ZEKE group name(s) JOB:

ZEKE job name(s).

Explanation:

The ZEKE selection criteria specified for the application.

User response:

None.

BKMK2312E No job collection criteria found for

application: appl

Explanation:

No ZEKE selection criteria were found for the

application.

User response:

Use the ISPF job collection panel for ZEKE to specify

selection criteria for the application.

BKMK2313E Unknown ZEKE criteria found for

application: appl

Explanation:

An unknown criteria type was found for the application.

User response:

Use the ISPF job collection panel for ZEKE to correct

the selection criteria for the application.

BKMK2401E Record too large.

Explanation:

Internal error.

User response:



BKMK2402E Duplicate record.

Explanation:

Internal error.

User response:






Explanation:


User response:

Please report this message, with the error text, to

Technical Support.

BKMK2502E Error from SI024 errortext.

Explanation:

The filter routine SI024 detected an error.

User response:


Technical Support.

BKMK2503E ISPF error RC: nnnn errortext

Explanation:

An error occurred during ISPF processing.

User response:



BKMK2601E Invalid parameter: errortext

Explanation:


User response:


Technical Support.

BKMK2602E Unable to open file.

Explanation:

The program was unable to open the edit file.

User response:

Please report this message to Technical Support.

BKMK2701E JOBCOLL_ZEKE_JCLLIB missing or

DSNAME specified is not valid.

Explanation:

Token JOBCOLL_ZEKE_JCLLIB was not found in the

INI or the data set name was invalid.

User response:

Correct the specification of JOBCOLL_ZEKE_JCLLIB.

BKMK2702E Nonzero RC from BKMJOBZJ for

JCLLIB/ZEKEUTL. RC=rc

Explanation:

An error occurred attempting to select the ZEKE JCLLIB

or ZEKEUTL procedure.

User response:

If unable to determine the reason for the error, contact

Technical Support.

BKMK2703E ZEKEOUTP in :JCL_DEFAULTS

missing or no DSNAME specified.

Explanation:

Token ZEKEOUTP was not found in section

:JCL_DEFAULTS of INI or no data set name was

specified.

User response:

Correct the specification of ZEKEOUTP.

BKMK2704E ZEKEOUTF in :JCL_DEFAULTS

missing or no DSNAME specified.

Explanation:

Token ZEKEOUTF was not found in section

:JCL_DEFAULTS of INI or no data set name was

specified.

User response:

Correct the specification of ZEKEOUTF.

BKMK2801E Unable to open files; check SYSOUT.

Explanation:


User response:



DDNAME.

BKMK2802E Internal sort failed.

Explanation:

The internal sort of the jobs had an error.

User response:


available the entire batch job output.

BKMK2803E VSAM error; function.

Explanation:

An error occurred processing the database.

User response:


BKMK2805E Error from SI024;RC=nnnn

Explanation:

The string filter routine, SI024DC2, detected an error.

User response:


Message BKMK2806E will also be issued.



BKMK2806E String is STRING_TEXT Mask is

MASK_TEXT.

Explanation:


User response:


Message BKMK2805E will also be issued.

BKMK2807E Error fetching //SISPARM info

Explanation:



User response:




BKMK2808E Error obtaining INI value for

section=:ACDI, Token=token

Explanation:

The check for a token in INI failed.

User response:




BKMK2809E Error in INI value for section=:ACDI,

Token=token, Value=val

Explanation:

The value for a token in INI is invalid.

User response:

Correct the INI token value.

BKMK2810I Job filtering is disabled for application.

Explanation:

The setup option for the application indicates filters

should not be applied during job collection.

User response:

None required.

BKMK2811I Job filtering is enabled, but no job

filters exist for application.

Explanation:

The setup option for the application indicates filters

should be applied during job collection, but no job filters

have been specified.

User response:

None required.

BKMK2812I The following jobs excluded

–INCL_JOB filters exist and do not

include jobs.

Explanation:

The jobs listed were not matched to the specified

INCL_JOB filters.

User response:

None required.

BKMK2813I jobname job excluded by EXCL_JOB

filter filter.

Explanation:

The job, jobname, matched the specified EXCL_JOB

filter, filter, and has been excluded, or,the job’s

predecessor was excluded.

User response:

None required.

BKMK2814I All jobs were excluded by filtering.

Explanation:

The INCL_JOB, EXCL_JOB filters eliminated all the

jobs.

User response:

The jobs excluded by filters will be listed. Change the

filters so the jobs for the application are not excluded.

BKMK2815I Dependent jobs will be excluded if the

predecessor job is excluded.

Explanation:

The INI token value indicated that the exclusion of a

predecessor should exclude its successors.

User response:

None.

BKMK2816I Dependent jobs will not be excluded if

the predecessor job is excluded.

Explanation:

The INI token value indicated that the exclusion of a

predecessor should not affect its successors.

User response:

None.

BKMK2817E SI027DC0 error; R15=nnnn

R0=nnnnnnnn Function=func

Table=tblname

Explanation:

An error occurred accessing a data space.

User response:


that contains this message.



BKMK2818I The following INCLUDE job filters will

be used: INCLUDE_JOB_FILTERS

Explanation:

INCL_JOB filters were found for the application and will

be applied.

User response:

None.

BKMK2819I The following EXCLUDE job filters will

be used: EXCLUDE_JOB_FILTERS

Explanation:

EXCL_JOB filters were found for the application and will

be applied.

User response:

None.


Explanation:


User response:

Check that the JCL has not been incorrectly modified.

BKMK2903E Internal sort failed.

Explanation:

The internal sort of the jobs had an error.

User response:

If unable to resolve the sort problem, contact Technical

Support. Have available all job output.


Explanation:


INI failed. R15 IS the return code from SI030DC0.

User response:




BKMK2908E Error obtaining INI value for

section=section, Token=token

Explanation:


User response:




BKMK2909E Error in INI value for token=token,

Value=value

Explanation:


User response:


BKMK2910I Duplicated jobname. First occurrence:

jobname collection info Other

occurrence: jobname collection info

Explanation:

A jobname was found multiple times.

User response:

None required.

BKMK2911I Data for first job replacing second.

Explanation:

Jobname in message BKMK2910I was duplicated. The

collection info for the first occurrence of the jobname is

replacing subsequent occurrences. Predecessor and

successor information for the subsequent occurrence

will be maintained, but will be associated with the first

occurrence.

User response:

None required.

BKMK2912I Job: jobname1 collection info is

predecessor and successor to job:

jobname2

Explanation:

A loop was detected. JOBNAME1 is a predecessor and

a successor to JOBNAME2.

User response:

None required.

BKMK2913I First job being used as predecessor.

Explanation:

JOBNAME1, message BKMK2912I, is a predecessor

and a successor to JOBNAME2. JOBNAME1 will be

used as the predecessor.

User response:

None required.


R0=nnnnnnnn Function=func

Table=tblname

Explanation:


User response:






Explanation:


User response:



DDNAME.

BKMK3002E No jobs found in input file.

Explanation:

No jobs were detected in the input file.

User response:

Check that the JCL has not been incorrectly modified. If

unable to determine the cause of the error, contact

Technical Support.

BKMK3003E VSAM error: errortext

Explanation:

An error occurred processing a database.

User response:

Check the associated MSC041NNE messages. If

unable to determine the cause of the error, contact

Technical Support.

BKMK3004E Parameter error; errortext.

Explanation:

An error occurred with the parameter passed to the

program.

User response:




Explanation:



User response:




BKMK3501E BKMRSMFT not running.

Explanation:

RSP must be active on the image submitting this job.

User response:

Start RSP or determine why it might have failed.

BKMK3502E ALLOCATE of RSP message queue

failed.

Explanation:

SVC99 failure.

User response:



BKMK3503E Cannot open message queue.

Explanation:

BDAM open failure.

User response:

Check attributes of RSP message queue. Ensure JCL

member BKMMQBLD was run.

BKMK3504E Free of RSP message queue failed.

Explanation:

SVC99 failure.

User response:

From the included SVC99 return code, determine why

the free failed.

BKMK3601E Increase space, not room for 48 4096

byte blocks in primary extent.

Explanation:

Space value in DD RSPMSGQ is too small.

User response:

Change JCL and resubmit BKMMQBLD.


IEANT xx

Explanation:

Internal error.

User response:



BKMK3802E Allocate of overflow data set failed.

Explanation:

The overflow data set could not be allocated.

User response:

Look for other messages that should specify the nature

of the problem.

BKMK3803E Open of overflow data set failed.

Explanation:

The overflow data set could not be opened.

User response:


of the problem.



BKMK3804W Overflow data set is not available.

Explanation:

The overflow data set is in use by import task

RSPOVFIM.

User response:

None.

BKMK3805E Deallocate of overflow data set failed.

Explanation:

The overflow data set could not be deallocated.

User response:


of the problem.

BKMK3806W Overflow data set is full. SMF data

may be lost.

Explanation:

None.

User response:

If BKMRUPDT was stopped to reorganize the database,

the overflow file size needs to be increased or the reorg

time decreased.

BKMK3807E RSP status update failed.

Explanation:

Internal error.

User response:



BKMK3808E Various detailed allocate and

deallocate error messages.

Explanation:

Allocate and deallocate detail messages.

User response:

If possible fix errors and rerun; otherwise, report this

message with the error text to Technical Support.

BKMK3809I Waiting for overflow

Explanation:

Informational message. Overflow being used by other

modules.

User response:

None.

BKMK3810I Overflow data set load started.

Explanation:

Informational message. Records are being moved from

buffers to the overflow data set.

User response:

None.

BKMK3811I Overflow data set load finished.

Explanation:

Informational message. All the records in the buffers

have been moved to the overflow data set.

User response:

None.


IEANT xx.

Explanation:

Internal error.

User response:



BKMK3902E Allocate of overflow data set failed.

Explanation:

The overflow data set could not be allocated.

User response:


of the problem.

BKMK3903E Open of overflow data set failed.

Explanation:


User response:


of the problem.

BKMK3905E Deallocate of overflow data set failed.

Explanation:

The overflow data set could not be deallocated.

User response:


of the problem.

BKMK3907E Output open of overflow data set

failed.

Explanation:


User response:


of the problem.



BKMK3908E Overflow export stop failed.

Explanation:

Internal error.

User response:


Technical Support.

BKMK3909E Overflow export start failed.

Explanation:

Internal error.

User response:



BKMK3910E RSP status update failed.

Explanation:

Internal error.

User response:





Explanation:


User response:



BKMK3912I Waiting for overflow.

Explanation:


User response:

None.

BKMK3913I Overflow records reloaded nnnnn

Explanation:


User response:

None.

BKMK4101E Subtask name must be CMD, EXP, IMP,

DJC, or UPD.

Explanation:

Internal error.

User response:



BKMK4102E Subtask status must be A or S.

Explanation:

Internal error.

User response:



BKMK4103E RSP main task not active.

Explanation:

Internal error.

User response:



BKMK4104E MSGQUEUE allocation failed.

Explanation:

The MSGQUEUE data set could not be allocated.

User response:


of the problem.

BKMK4105I Waiting for access to MSGQUEUE.

Explanation:


User response:

None.

BKMK4106E MSGQUEUE open failed.

Explanation:

The MSGQUEUE data set could not be opened.

User response:


of the problem.

BKMK4107E MSGQUEUE free failed.

Explanation:


User response:


of the problem.

BKMK4108E Subtask function must be C, E, or S.

Explanation:

Internal error.

User response:





BKMK4201E MSGQUEUE allocate failed.

Explanation:

The MSGQUEUE data set could not be allocated.

User response:


of the problem.

BKMK4202E MSGQUEUE open failed.

Explanation:


User response:


of the problem.

BKMK4203E MSGQUEUE free failed.

Explanation:

The MSGQUEUE data set could not be freed.

User response:


of the problem.

BKMK4204I Waiting for access to RSP records.

Explanation:


User response:

None.

BKMK4301E Invalid filter table process request.

Explanation:

Internal error.

User response:



BKMK4302E Invalid filter table scope type.

Explanation:

Internal error.

User response:



BKMK4303E Invalid filter table applname

Explanation:

Internal error.

User response:



BKMK4304E Filter table too large for storage area.

Explanation:

Internal error.

User response:



BKMK4401E No parameters passed.

Explanation:

Internal error.

User response:


BKMK4402E Insufficient parameters.

Explanation:

Internal error.

User response:


BKMK4403E APV record not found.

Explanation:

The application’s APV record was not found in the

database.

User response:


BKMK4410E Point forward, reread DSDKEY.

Explanation:

Internal error repositioning in the database.

User response:


BKMK4411E READNEXT, reread DSDKEY

Explanation:

Internal error repositioning in the database.

User response:


BKMK4420I New relative generations skipped in

job: jobname Base GDG: basegdgname

Explanation:

Processing of relative GDS numbers from RSP JCL

detected missing numbers. For example, (+2) was

found, but (+1) was not.

User response:

Not required.



BKMK4421W Positive GDS calculated for:

basegdgname.

Explanation:


resulted in a + relative number. The DSR record is not

written.

User response:

Please notify Technical Support if this occurs.

BKMK4422W Over 999 generations found for:

basegdgname Relative entries skipped.

Explanation:


detected over 999 new generations. The relative entries

for this GDG will not be written. Processing continues

with the next GDG base.

User response:

It might be necessary to schedule BKMAPLEN for the

application more frequently or to exclude this GDG.

BKMK4701I CTL record written to database.

Explanation:

The initial record has been successfully added to the

database.

User response:

None required.

BKMK4702I CTL record already in database.

Explanation:

The initial record already existed in the database.

User response:

None required.

BKMK4801E No parameters supplied.

Explanation:

Internal error.

User response:


BKMK4802E Parm1 invalid length.

Explanation:

Internal error.

User response:


BKMK4803E Parm1 invalid value.

Explanation:

Internal error.

User response:


BKMK4804E PARM2 invalid length.

Explanation:

Internal error.

User response:


BKMK4805E Parm2 invalid value.

Explanation:

Internal error.

User response:


BKMK4806E Parm3 invalid length.

Explanation:

Internal error.

User response:


BKMK4807W Update has already completed.

Explanation:

A conversion job was being run. The database indicates

that the specified conversion has already been

completed.

User response:

None required.

BKMK4808E Conversion record not found.

Explanation:

An attempt was made to update the status of a

database conversion. The record for that conversion

was not in the database.

User response:


BKMK5001E SI024DC1 ADDR zero.

Explanation:

The address for the filter routine, SI024DC1, was zero.

No JCL DSD records will be collected.

User response:

Notify Technical Support if this error occurs.

BKMK5002E U83 ADDR zero.

Explanation:

The address for the RSP IEFU83 exit routine was zero.

No JCL DSD records will be collected.

User response:


BKMK4421W • BKMK5002EIBM Confidential


BKMK5003E ESTAE ADDR zero.

Explanation:

The address for RSPUJIES, the ESTAE routine, was

zero. No JCL DSD records will be collected.

User response:


BKMK5004E ESTAE not established.

Explanation:

The request to establish an ESTAE failed. No JCL DSD

records will be collected.

User response:


BKMK5005E Bad RC from filter routine.

Explanation:

The return code from SI024DC1 was greater than 4.

The current job might not have any JCL DSD records

collected.

User response:


BKMK5006E RSP_STATUS indicates not available.

Explanation:

The RSP dataspace indicates no space is available to

record the current DJC information. The information for

that JCL DSD record will be lost.

User response:


BKMK5101E RSP failure–UJI exit has ABENDed.

Explanation:

The UJI exit has ABENDed, and the RSPUJIES module

will try to shut it down.

User response:

Notify Technical Support if this message occurs. Please

have all the ABEND information available.

BKMK5102E U83 exit dormant.

Explanation:

The UJI exit ABENDed, and the exit has been shut

down.

User response:

None.

BKMK5103E RSPUJISE ABEND occurred with no

SDWA available.

Explanation:

An ABEND occurred in RSPUJISE, the RSP IEFUJI

exit. No ABEND information is available.

User response:

Notify Technical Support if this message occurs.

BKMK5104E Retry routine ABENDed.

Explanation:


exit. In the recovery process another ABEND has

occurred.

User response:



BKMK5105E No retry allowed.

Explanation:


exit. The recovery process cannot be completed.

User response:



BKMK5201E SYSIN data error.

Explanation:

Internal error.

User response:



BKMK5202E SYSIN data parsing error.

Explanation:

Internal error.

User response:



BKMK5203E Invalid character in SYSIN data after

keywordxxxxxxxxxx.

Explanation:

Unexpected data in SYSIN DD.

User response:



BKMK5204E Next keyword longer than 16

characters. Previous

keyword:xxxxxxxxxx

Explanation:


User response:





BKMK5205E Invalid syntax. Keyword:xxxxxxxxx.

Explanation:


User response:



BKMK5206E Invalid syntax. Data:xxxxxxxxxx

Keyword:xxxxxxxxxxx

Explanation:


User response:



BKMK5207E No APPL keyword or APPL not first

keyword.

Explanation:


User response:



BKMK5208E Optional keyword invalid.xxxxxxxxxx

Explanation:


User response:



BKMK5209E APPLNAME xxxxxxxx not in database.

Explanation:

APPLNAME is not valid.

User response:

Correct APPLNAME and rerun job.

BKMK5210E Keyword xxxxxxxxxx appears more than

once.

Explanation:


User response:



BKMK5212E Start job xxxxxxxx not in job table.

Explanation:

START job is not valid.

User response:

Correct START job name or add START job to job table

and rerun job.

BKMK5213E More than 8 START jobs.

Explanation:

There is a maximum of 8 START jobs allowed.

User response:

Remove extra START jobs and rerun job.

BKMK5214E END job xxxxxxxx not in job table.

Explanation:

END job is not valid.

User response:

Correct END job name or add END job to job table and

rerun job.

BKMK5215E More than 8 END jobs.

Explanation:

There is a maximum of 8 END jobs allowed.

User response:

Remove extra END jobs and rerun job.

BKMK5216E Error retrieving job flat file name from

INI.

Explanation:

Internal error.

User response:



BKMK5217E Dataspace create failed for job table.

Explanation:

Internal error.

User response:



BKMK5218E Job table load failed.

Explanation:

Internal error.

User response:



BKMK5219E Invalid date or time for keyword

xxxxxxxxxx.

Explanation:

Time data or date data for keyword is invalid.

User response:

Change the data to a correct date (YYYYDDD) or a

correct time (HH.MM) as appropriate.



BKMK5220E End date is not greater than start date.

Explanation:

End date must be greater than start date.

User response:

Change end date to greater than start date or remove

end date.

BKMK5221E STARTTIME keyword must be used

with STARTDATE keyword. ENDTIME

keyword must be used with ENDDATE

keyword.

Explanation:

The STARTTIME keyword is used without the

STARTDATE keyword, or the ENDTIME keyword is

used without the ENDDATE keyword.

User response:

If you want to use start time or end time you must use

STARTDATE or ENDDATE.

BKMK5223E Dataspace delete failed for job table.

Explanation:

Dataspace delete failed for job table.

User response:



BKMK5224E Duplicate APPLNAMEs not allowed in

xxxxxxxx.

Explanation:

An application can only appear once in the SYSIN DD.

User response:

Remove any duplicate application names.

BKMK5225E APPL data table update failed

forxxxxxxxx.

Explanation:

Internal error.

User response:



BKMK5226E APPL data table read failed.

Explanation:

Internal error.

User response:



BKMK5227E APPL data table point failed.

Explanation:

Internal error.

User response:



BKMK5230E Open failed for SMF data set.

Explanation:

Internal error.

User response:



BKMK5231E Call to BKMFLTLD failed.

Explanation:

Internal error.

User response:



BKMK5232E Invalid filter type for APPxxxxxxxx filter

data xxxxxxxxxx

Explanation:

Internal error.

User response:



BKMK5233I Application statisticsxxxxxxxx

Explanation:

Heading for following statistics for SMF file data

captured and processed for this application.

User response:

None; informational.

BKMK5234I xxxxxxxxxxxxxxxxxxxxxxxxxx

xxxxxxxxxxxxxxxxxxxx

Explanation:

SMF file statistics.

User response:


BKMK5235I Spanned record dropped.

Explanation:

Spanned records cannot be processed.

User response:




BKMK5236I SMF record larger than 4096 bytes.

Explanation:

Records larger than 4K cannot be processed.

User response:


BKMK5301E Parm length invalid, found: nnnnnnnn

Explanation:

Length of parm is invalid. The parm cannot be longer

than 9 characters.

User response:

Correct parm and rerun job.

BKMK5302E DSR REC table point failed. RC=nnn.

Explanation:

Internal error.

User response:



BKMK5303E DSR REC READNEXT failed. RC=nnn

Explanation:

Internal error.

User response:



BKMK5401E LOADLIB open failed.

Explanation:

The open of the LOAD library failed.

User response:



BKMK5402E Load failed. Module=xxxxxxxx

Explanation:

Load of the above module failed.

User response:



BKMK5403E DSR REC SI27 table create failed. RC=

Explanation:

Creation of a dataspace table failed.

User response:



BKMK5404E Invalid parm, length zero.

Explanation:


User response:



BKMK5405E Invalid parm, too big.

Explanation:


User response:



BKMK5406E Invalid parm length, not 9.

Explanation:


User response:



BKMK5407E Parm byte 9 not R or S

Explanation:


User response:



BKMK5408E BKMEVALA failed. See other

messages.

Explanation:

Non zero return code from module BKMEVALA.

User response:

Look for other messages that might explain the

problem.

BKMK5409E BKMEVALB failed. See other

messages.

Explanation:

Non zero return code from module BKMEVALB.

User response:


problem.

BKMK5410E BKMDSRLD failed. See other

messages.

Explanation:

Non zero return code from module BKMDSRLD.

User response:

BKMK5236I • BKMK5410EIBM Confidential



problem.

ASP05501E Cannot register database. R15=nnnn;

SI040DC0 response

block=/xxxx/xxxx/xxxx/.

Explanation:

The OPEN of the database failed.

User response:




Explanation:

Internal error.

User response:



BKMK5503E Cannot get working storage for

database.

Explanation:

Internal error.

User response:



BKMK5504E Application xxxxxxxx not in database;

unable to proceed.

Explanation:

Application not found.

User response:

Application name might be misspelled. Correct and try

again.

BKMK5505E Unexpected return code during

application/generic read/direct

read/delete R15=NNNN; SI040DC0

Response block /xxxx/xxxx/xxxx/.

Explanation:

Database I/O failure.

User response:



BKMK5506I Removed from

database:xxxxxxxxxxxxxxxx

Explanation:

Application removed from database.

User response:

None.

BKMK5507I Start of DSR removal for

applicationxxxxxxxx

Explanation:

DSR delete beginning.

User response:

None.

BKMK5508I End of DSR removal for application

xxxxxxxx DSRs removed: nnnnnnnn

Explanation:

DSR delete finished.

User response:

None.

BKMK5509I Database not available. Retrying...

Explanation:

Cannot get exclusive use of database.

User response:

None.

BKMK5510I Application xxxxxxxx verified;

proceeding with request.

Explanation:

Application found.

User response:

None.

BKMK5511I End of delete (TYPE(DSR)..). Total

applications processed: nnnnnnnnnn

Total DSRs removed:nnnnnnnnnn

Explanation:

Application delete statistics.

User response:

None.

BKMK5513I Start rename of applicationxxxxxxxx

Explanation:

DB rename beginning.

User response:

None.

BKMK5514I End rename of application xxxxxxxx.

Explanation:

DB rename end.

User response:

None.

ASP05501E • BKMK5514I IBM Confidential


BKMK5520I VSAM interface: file not available. Will

retry.

Explanation:

Cannot get exclusive use of database.

User response:

None.

BKMK5597E Required keyword missing: xxxxxxxxxx

Explanation:

Required keyword missing or misspelled.

User response:

Correct syntax and rerun.

BKMK5598E Errors during command read.

Explanation:

Required keyword missing or misspelled.

User response:

Correct syntax and rerun.

BKMK5599I End of file on SYSIN.

Explanation:

End of input data.

User response:

None.

BKMK5602I New application: xxxxxxxx copied from

applicaton xxxxxxxx

Explanation:

New application created using information from another

application.

User response:

None.

BKMK5603E No target applications for copy.

Explanation:

Syntax error after applications keyword.

User response:

There must be at least two applications after the

application keyword. The first application is the source

application and all other applications are target

applications.

BKMK5604E Source applicaton: xxxxxxxx APV

record not found.

Explanation:

Valid source application is not in the database.

User response:

You must choose another application to copy.

BKMK5605E Source application: xxxxxxxx APL

record not found.

Explanation:

Valid source application is not in the database.

User response:

You must choose another application to copy.

BKMK5606E Target application: xxxxxxxx APV

record exists.

Explanation:

Target application already exists in database.

User response:

You cannot use this application as a target application.

BKMK5607E Target application: xxxxxxxx APL record

exists.

Explanation:

Target application already exists in the database.

User response:

You cannot use this application as a target application.

BKMK5701E No filter action requested.

Explanation:

No keywords in input stream.

User response:

Review filter syntax documentation, correct the errors,

and rerun.

BKMK5702E One of the keywords REPLACE,

ADD_LAST, or ADD_FIRST, required.

Explanation:

A required keyword is missing.

User response:

Review filter syntax documentation, correct the error,

and rerurn.

BKMK5703E Keywords RETENTION,

RETENTION_DSN, RETENTION_DDN,

and RETENTION_DEL are mutually

exclusive.

Explanation:

Only one of the above keywords can be used with the

filters command.

User response:


and rerurn.



BKMK5704E Keywords EVALUATION,

EVALUATION_DSN, EVALUATION_DDN,

AND EVALUATION_DEL are mutually

exclusive.

Explanation:

Only one of the above keywords can be used with the

filters command.

User response:


and rerurn.

BKMK5705E Only application, universal, or global

keywords are valid with overview.

Explanation:

Invalid syntax.

User response:


and rerurn.

BKMK5706E Application: xxxxxxxx not in database.

Explanation:

Application name is invalid.

User response:

Add the application to the database or choose another

application.

BKMK5707E Allocate failed for DSN: xxxxx

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Explanation:

Allocate failed.

User response:

Review detail messages in BKMK5708E.



Explanation:


User response:

If possible, fix the errors and rerun; otherwise, report

this message with the error text to Technical Support.

BKMK5709E Deallocate failed for DSN: xxxxxx

xxxxxxxxxxxxxxxxxxxxxxxxxxxx

Explanation:

Deallocate failed.

User response:



BKMK5710E Open of filter work data set failed.

Explanation:

Non-recoverable error.

User response:


Technical Support.

BKMK5711E Only one filter type keyword is allowed

in the filters command.

Explanation:

Filter types RETENTION, EVALUATION, and

EXTERNAL cannot be mixed in FILTERS command.

User response:

Review FILTER syntax documentation, correct the

errors, and rerun.

BKMK5712E Open of retention filter data set failed.

Explanation:


User response:


Technical Support.

BKMK5713E No data set filters.

Explanation:

Input data set or DDNAME has no data.

User response:

At least one filter must be included in the filter data set.

BKMK5714E Invalid filter: xxxxxxxxxxxxxxxxxxxx

Explanation:

Syntax error message from ACSFILTER routine.

User response:

Error message BKMK5716E will show filter that is in

error. Review FILTER syntax documentation, correct the

errors, and rerun.

BKMK5715E DSN is longer than 44 bytes:

xxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxx

Explanation:

Invalid DSN filter.

User response:


and rerun.

BKMK5716I FILTER: xxxxxxxxxxxxxxxxxxxx


Explanation:

Filter in error.

User response:



See error message BKMK5714E.

BKMK5717E xxxxxxxxxxxxxxxxxxxxxxx filter too

long–truncated.

Explanation:

Filter type exceeded maximum length.

User response:


and rerun.

BKMK5718E Keywordxxxxxxxx_DEL value must be

ALL, DSN, VOL, JOB, UNIT, or SYSID.

Explanation:

Value for all keywords with _DEL suffix must be one of

above values.

User response:


and rerun.

BKMK5719E Only one type of global filter can be

updated at a time.

Explanation:

When updating global filters types DSN, VOL, JOB,

UNIT and SYSID cannot be mixed. Each type must be

processed separately.

User response:


and rerun.

BKMK5720E Point backward found no filter record

forxxxxxxxxxx.

Explanation:


User response:


Technical Support.

BKMK5721E Old filter count is zero.

Explanation:


User response:


Technical Support.

BKMK5722E Duplicate key. Filter type:xxxxxxxxxx

Filter

value:xxxxxxxxxxxxxxxxxxxxxxxxxxxx

Explanation:


User response:


Technical Support.

BKMK5723E Global filter type is only allowed for

local (application) filters.

Explanation:

Global filters are not allowed in universal filters.

User response:


and rerun.

BKMK5724E Invalid generation data set

specification.

Explanation:

Relative number greater than 255 or non-numeric.

User response:


and rerun.

BKMK5725E Keywords REPLACE, ADD_FIRST, and

ADD_LAST are mutually exclusive.

Explanation:

Only one of the above keywords can be used with

FILTERS command.

User response:


and rerun.

BKMK5726E Invalid character in DSN: xxxxxxxxx

xxxxxxxxxxxxxxxxxxxxxx

Explanation:

DSN FILTER syntax error.

User response:

Review FILTER syntax documentation, correct the

errors, and rerun.

BKMK5801I Control-M job collection for application

APPL completed; return code=NNN.

Explanation:

Job collection for the indicated application has

completed.

User response:

None required if the return code is less than or equal to

four (4). If the return code is greater than four (4), check

other messages.


Explanation:


User response:





DDNAME.

BKMK5803E Invalid parameter: ERRORTEXT.

Explanation:

The program was given an invalid parameter.

User response:


available the listing containing this message.

BKMK5804E No data found in report file.

Explanation:

The report file from CONTROL-M did not contain the

expected job names.

User response:


available the listing containing this message. The report

file from the CONTROL-M step will also be required.

BKMK5901E Invalid parm, length zero.

Explanation:


User response:


Technical Support.

BKMK5902E Invalid parm, larger than 11 bytes.

Explanation:


User response:


Technical Support.

BKMK5903E Filter request type not E, J, O, or R.

Explanation:


User response:


Technical Support.

BKMK5904E Allocate failed for temporary filter data

set.

Explanation:

Allocate failed.

User response:


ASP05905E Deallocate failed for temporary filter

dataset.

Explanation:

Deallocate failed.

User response:

Review detailed messages in BKMK5908E.

BKMK5906E ISP services error:xxxxxxxx

Explanation:


User response:

Report this message with the error text to Technical

Support.



Explanation:


User response:



BKMK5909E Filter load error. See other error

messages.

Explanation:


User response:


Support.

BKMK5910E XYXIN data set open error.

Explanation:


User response:


Support.

BKMK5911E Allocate failed for XYXIN DDNAME.

Explanation:

Allocate failed.

User response:


BKMK5912E Deallocate failed for XYXIN DDNAME.

Explanation:

Deallocate failed.

User response:




BKMK5913E Allocate failed for SYSPRINT DDNAME.

Explanation:

Allocate failed.

User response:


BKMK5914E Deallocate failed for SYSPRINT

DDNAME.

Explanation:

Deallocate failed.

User response:


BKMK5915E Columns 72 through 80 must be

spaces.

Explanation:

Syntax error.

User response:

Correct the errors and try again.

BKMK6001I CA7 job collection for application

APPL completed; Return code=nnn

Explanation:

Job collection for the indicated application has

completed.

User response:

None required if the return code is less than or equal to

four (4). If the return code is greater than four (4), check

other messages.


Explanation:


User response:



DDNAME.


Explanation:


User response:



BKMK6004E No data found in report file.

Explanation:

No job names were collected from the CA7 report.

User response:


available the listing containing this message. The report

file from the CA7 will also be required.


Explanation:


User response:



DDNAME.

BKMK6103E Invalid parameter: ERRORTEXT

Explanation:


User response:



BKMK6107E Error fetching //INI info.

Explanation:


INI failed. R15 IS the return code from SI030DC0.

User response:

Check that DD //INI in the JCL is pointing to the correct

product parmlib data set name and member INI. For

further assistance, contact Technical Support.

BKMK6117E BKM01VV1 error; R15=nnnn

R0=nnnnnnnn Function=xxxx

Table=xxxxxxxxxxxxxxxx

Explanation:


User response:



BKMK6202E xxxxxx failed.

Explanation:

A VSAM function for the database failed. xxxxxx is the

failing function.

User response:


BKMK6203W No APV records found.

Explanation:

No APV records were found in the database.

User response:

None.



BKMK6204W RSP xxx record delete failed.

Explanation:

The call to BKMDSDDE to delete records was not

successful. XXX is the type of DSD record being

deleted - SMF or JCL.

User response:

Check the messages from BKMDSDDE for the reason

for the failure.

BKMK6310E No SYSIN.

Explanation:

No control statements were found from the //SYSIN DD

statement.

User response:

Specify the desired SYSIN parameters.

BKMK6311E SI027 error, xxxxxx; R15=nnnn

Explanation:

An error occurred accessing a data space table. xxxxxx

is the failing function. nnnn is the return code from

SI027DC0.

User response:


BKMK6312E No APV records found.

Explanation:

No APV records were found in the database.


User response:

Check that the //ASAPDB DD statement is pointing to

the correct data set name.

BKMK6314E VSAM error, xxxxxx

Explanation:


failing function.

User response:


BKMK6315E Required keyword missing.

Explanation:

The function keyword, DSD, was missing.

User response:

Specify a keyword.

BKMK6316E Invalid application length.

Explanation:

An application name or mask is longer than eight

characters.

User response:

Correct the application specification.

BKMK6317E Invalid application name.

Explanation:

An application name or mask is invalid.

User response:

Correct the application specification.

BKMK6318E Invalid date; format is YYYYDDD.

Explanation:

The date entered for keyword DATE is invalid.

User response:

Correct the DATE specification.

BKMK6320W Duplicate application; ignored

aaaaaaa

Explanation:

A duplicate application, aaaaaaa, was found in SYSIN.


User response:

None.

BKMK6321W No match for application aaaaaaa.

Explanation:

No match was found for specified application, aaaaaaa.


User response:

None.

BKMK6401I Application deleted: applname

Explanation:

Application applname has been deleted.

User response:

None.

BKMK6402I Records deleted: n,nnn,nnn

Explanation:

The delete of an application caused n,nnn,nnn records

to be deleted from the database.

User response:

None.

BKMK6403I No records deleted.

Explanation:

The application specified for deletion did not have any

records in the database.

User response:

None, unless the application name specified was

incorrect.

BKMK6204W • BKMK6403I IBM Confidential


BKMK06404I Data set deleted: DSN of application

entries PDS

Explanation:

The application’s entries PDS has been deleted.

User response:

None.

BKMK6405I Application entry deleted fromxxxxxxxx.

Explanation:

The application’s entry has been deleted from a

PDS.xxxxxxxx is the dsname of the PDS.

User response:

None.

BKMK6406I Application entries PDS not

deleted;xxxxxxxx

Explanation:

The application’s entries PDS,xxxxxxxx, could not be

allocated and was not deleted.

User response:

None.

BKMK6410E Parm is required.

Explanation:

No parameter was given to the program.

User response:

For batch execution, verify that ″APPL=APPLNAME″

has been correctly specified on the EXEC statement for

the execution of BKMDELAP. For online execution,


BKMK6411E Parm length invalid.

Explanation:

The length of the parameter is invalid.

User response:

For batch execution, verify that ″APPL=APPLNAME″

has been correctly specified on the EXEC statement for

the execution of BKMDELAP. For online execution,


BKMK6412E Module xxxxxxxx not found.

Explanation:

A necessary program was not found.

User response:

For batch execution, verify that the STEPLIB(s) specify

the correct product load libraries. For online execution,



Explanation:

An error occurred trying to access the INI member of

parmlib.

User response:

For batch execution, verify that DD //SISPARM points to

the correct product parmlib, member INI. For online

execution, contact Technical Support.

BKMK6414E VSAM error, xxxxxx

Explanation:


failing function.

User response:


BKMK6415E Application not found.

Explanation:

The APL record for the application being deleted was

not found in the database.

User response:


BKMK6416E Record read was:

Explanation:

The APL record for the application being deleted was

not found in the database.

User response:


BKMK6417E Unable to open xxxxxxxx file.

Explanation:

The program was unable to open a file.

User response:


BKMK6421W LMC record not found.

Explanation:

The LMC record was not found in the database.

User response:

None.

BKMK6422W xxxxxxxx entry not deleted.

Explanation:

The application entry was not deleted from either the

auditing or notebook PDS.

User response:

None.

BKMK06404I • BKMK6422WIBM Confidential


BKMK6601E RSP failure–U83 exit has ABENDed.

Explanation:

The U83 exit has ABENDed, and the RSPESTAE

module will try to shut it down.

User response:



BKMK6602I U83 exit dormant.

Explanation:

The U83 exit ABENDed, and the exit has been shut

down.

User response:

None.

BKMK6801E Parameter error; error text.

Explanation:

Internal error; the parameter list passed to the program

is incorrect.

User response:


BKMK6802E Error retrieving token; section: section

token: token.

Explanation:

An error occurred attempting to retrieve a token from

the INI.

User response:


BKMK6803E Invalid token value; token: token value:

specified value.

Explanation:

The value specified for the token is invalid.

User response:

Correct the value of the token.

BKMK6804E ISPF error; R15:nnnn error text

Explanation:

An error occurred using the ISPF functions.

User response:

If you are unable to determine the reason for the failure,


BKMK7201I TWS application selection completed,

Application=application name Return

code=nnn

Explanation:


User response:

None.


Explanation:


User response:



DDNAME.


Explanation:


User response:



BKMK7205E No entries matched TWS application

names/masks specified.

Explanation:

No TWS application names were found in the TWS

extract report to match those specified for the

application.

User response:

Check that the TWS application names were specified

correctly to the database.


Explanation:


parmlib.

User response:

Verify that DD //SISPARM points to the correct product

parmlib, member INI.

BKMK7208E Error from SI024: String:string

Mask:mask Error:errortext

Explanation:


User response:


available the listing containing the message.

BKMK7209E No TWS applications found for

application in database.

Explanation:

No TWS application names were found for the

application.

User response:

Use online job collection panels to specify TWS

application names/masks for the application.



BKMK7210I Following names/masks will be

checked: TWS application name/mask

Explanation:

The listed TWS application names or masks were found

in the application’s JCZ records. Those names will be

used in checking the TWS application report.

User response:

None.

BKMK7301I Job collection completed for application

name return code=nnn

Explanation:


User response:

None.


Explanation:


User response:



DDNAME.


Explanation:


User response:



BKMK7304E No jobs found in report file.

Explanation:

No jobs were selected from the TWS report.

User response:

Check that the TWS extraction was successful.

BKMK7309E Error in INI value for section=section,

token=token, value=value.

Explanation:


User response:


BKMK7310E SI027DC0 error: R15=nnnn

R0=nnnnnnnn function=func,

table=tblname

Explanation:


User response:



BKMK7311E Error parsing report record:’PRINT OF

RECORD’

Explanation:

An error occurred trying to determine the valid date for

the TWS application from the TWS report.

User response:



BKMK7312I Date format MMDDYY will be checked;

date format YYMMDD will be checked;

date format DDMMYY will be checked.

Explanation:

Based on the INI token value, the TWS report will be

checked using the indicated format.

User response:

None.

BKMK7314E No applications within date range.

Explanation:

Using the date format from the INI token, no TWS

applications were found that were within the valid range.

User response:

Check that the INI token correctly indicates the date

format being used for TWS at your installation.

BKMK7401I Invalid parameter: ERRORTEXT

Explanation:

Internal error passing parameters.

User response:

Contact Technical Support. Have available a screen

print that contains this message.

BKMK7403E ISPF error RC:NNNN ERROR_TEXT

Explanation:


User response:

If unable to determine the reason for the ISPF failure,

contact Technical Support. Have available a screen print


BKMK7404E DDNAME missing: ddname

Explanation:


User response:






Explanation:

Internal error opening work file.

User response:



BKMK7503E Invalid parameter: ERROR_TEXT

Explanation:


User response:



BKMK7504E DDNAME missing: ddname.

Explanation:


User response:



BKMK7505E Invalid record type: BADTYPE

Explanation:

An unrecognized JCZ record type was returned.

User response:



BKMK7601I Conversion completed; return

code=nnn

Explanation:


User response:

None.

BKMK7602I JBC records read: nnnnnnnnn

Explanation:

Informational message indicating the number of JBC

application records found in the database.

User response:

None.

BKMK7603I JBC records converted: nnnnnnnn

Explanation:

Informational message indicating the number of JBC

application records converted for TWS job collection.

User response:

None.

BKMK7604W Unable to convert JBC for

application: application.

Explanation:

The program was unable to parse the JBC for the

indicated application. The JBC record will be printed.

The conversion will continue with the next Automated

Critical Data Identification application.

User response:

Do an online job collection for the indicated application.

The TWS application names/masks will need to be

specified since the conversion program could not obtain

them from the JBC.

BKMK7606E VSAM error,xxxxxxxx

Explanation:

A VSAM function for the database failed. xxxxxxxx is

the failing function.

User response:



Explanation:


parmlib.

User response:




Explanation:


User response:



BKMK7702E Error from SI024 CURRENT_MASK

Explanation:


User response:


available a screen print that contains this message.

BKMK7703E ISPF error RC: nnnn ERROR_TEXT

Explanation:


User response:






BKMK7704E DDNAME missing: ddname

Explanation:


User response:




Explanation:


User response:




Explanation:


User response:



BKMK7901I Job collection started YYYY/MM/DD

HH:MM:SS; Application: application.

Explanation:


User response:

None.

BKMK7902I Records written to APLJOBS:nnnnnnnn

Explanation:


User response:

None.

BKMK7903I Job collection completed YYYY/MM/DD

HH:MM:SS; Return code=nnn

Explanation:


User response:

None if the return code is 0. If the return code is not 0,

check for other messages which indicate the reason for

the non-zero return code.

BKMK7904E Unable to open file: ddname

Explanation:


User response:

If unable to determine the problem, contact Technical

Support. Have the entire job output available.

BKMK7905E Invalid record type: badtype

Explanation:

An unrecognized JCZ record type was returned.

User response:


containing this message.


Explanation:


User response:




Explanation:


parmlib.

User response:



BKMK7908E No selection criteria found in the

database for application applname.

Explanation:

No ESP selection criteria was found for this application.

User response:

Enter ESP selection criteria for the application through

the online job collection panels.

BKMK7909I Criteria to be used for application

applname

Explanation:

Information message indicating the ESP criteria which

will be used for this application.

User response:

None.

BKMK7910I ESPJOBS Heading information; Date:

YYYY/MM/DD Time: HH:MM:SS

Explanation:

Informational message indicating the ESPJOBS extract

file heading.

User response:

None.



BKMK7911E No records matched selection criteria.

Explanation:

No ESP entries matched the selection criteria specified

for the application.

User response:

Verify that ESPJOBS is pointing to the correct extraction

file for the application.

BKMK7912E Unexpected version in ESPJOBS

header: VER#

Explanation:

An unexpected version was found in the ESPJOBS file

header.

User response:



BKMK7913E Unexpected end-of-file for ESPJOBS.

Explanation:

End of file was hit prematurely for ESPJOBS.

User response:



BKMK7914E Error parsing record; field:

FIELDDESCRIPTION

Explanation:

The program could not parse an ESP data field. The

entire ESP record with the problem is printed.

User response:



BKMK7915E Error from filter routine.

Explanation:

The ACS filter routine failed. An error message from the

routine is printed.

User response:



BKMK7917W Error calling SI017DC1, R15= nnnn

Explanation:

An error occurred trying to print a record containing

invalid data.

User response:



BKMK8001I SADGEN extraction started

YYYY/MM/DD HH:MM:SS

Explanation:


User response:

None.

BKMK8003I SADGEN extraction completed

YYYY/MM/DD HH:MM:SS; return

code=nnn.

Explanation:


User response:

None if the return code is 0. If the return code is not 0,

check for other messages which indicate the reason for

the non-zero return code.

BKMK8004E Unable to open file: ddname.

Explanation:


User response:

If unable to determine the problem, contact Technical

Support. Have the entire job output available.


R0=nnnnnnnn function=func

table=tblname

Explanation:


User response:



BKMK8011E Error parsing record.

Explanation:

The program could not parse an ESP data record. The

entire ESP record with the problem is printed.

User response:

Verify that ESPSADGN is pointing to the correct ESP

SADGEN file.

BKMK8017W Error calling SI017DC1, R15= nnnn

Explanation:

An error occurred trying to print a record containing

invalid data.

User response:



BKMK7911E • BKMK8017W IBM Confidential


BKMK8020I Records read from ESPSADGN:

nnnnnnnnn

Explanation:


User response:

None.

BKMK8021I Records written to ESPJOBS:

nnnnnnnn

Explanation:


User response:

None.


Explanation:


User response:



BKMK8104E DDNAME missing: ddname.

Explanation:


User response:



BKMK8105E ISPF error RC:nnnn ERROR_TEXT.

Explanation:


User response:





Explanation:


parmlib.

User response:



BKMK8108E Error obtaining INI value for Section=

section, Token= token.

Explanation:


User response:




BKMK8109E Error in INI value for Section=section,

Token=token, Problem=explanation.

Explanation:


User response:


BKMK8110E Invalid attributes for DSN=dsn

Problem: description.

Explanation:

The attributes for the DSN specified in ESPJOBS are

invalid.

User response:

Specify a different data set for use as the ESPJOBS

file.

BKMK8116W Deallocation for extract file failed,

DDNAME: ddname

Explanation:

Deallocation of the file failed. SVC99 messages will be

issued.

User response:

If unable to determine the reason for the failure, contact

Technical Support. Have available the screen print

(online) or the batch job with the messages.

BKMK8201E Invalid parm, length less than 3.

Explanation:

Internal errors passing parameters.

User response:



BKMK8202E Invalid parm, larger than 6.

Explanation:


User response:



BKMK8203E Error fetchingxxxxxxxxxxxxxxxxxx

RC=nnnn

Explanation:

Internal error fetching INI# token.

User response:





BKMK8206E ISP variable define failed.

Explanation:

Internal ISP error.

User response:



BKMK8207E ISPF call failed forxxxxxxxx.

Explanation:

Internal ISP error.

User response:



BKMK8208E Application name not found:xxxxxxxx

Explanation:

Internal error.

User response:



BKMK8209E Invalid parm, not OLDAPL or NEWAPL.

Explanation:


User response:



BKMK8303E Error fetchingxxxxxxxxxxxxxxxx

RC=nnnn

Explanation:


User response:




Explanation:

Internal ISP error.

User response:




Explanation:

Internal ISP error.

User response:




Explanation:

Internal error.

User response:



BKMK8311E Allocate failed for SKJNEKH DDNAME.

Explanation:

Allocation error.

User response:

This error might be correctable. Review detail messages

BKMK8320E.

BKMK8312E Deallocate failed for SKJNEKH

DDNAME

Explanation:

Deallocation error.

User response:


BKMK8320E.

BKMK8313E Allocate failed for SYSOUT DDNAME.

Explanation:

Allocation error.

User response:


BKMK8320E.

BKMK8314E Deallocate failed for SYSOUT

DDNAME.

Explanation:

Deallocation error.

User response:


BKMK8320E.

BKMK8315E Allocate failed for SORTMSG DDNAME.

Explanation:

Allocation error.

User response:


BKMK8320E.

BKMK8316E Deallocate failed for SORTMSG

DDNAME.

Explanation:

Deallocation error.

User response:




BKMK8320E.



Explanation:


User response:



BKMK8401E Invalid parm, length less than 3.

Explanation:


User response:



BKMK8402E Invalid parm, larger than 8.

Explanation:


User response:



BKMK8403E Error fetchingxxxxxxxxxxxxxxxxxx

RC=nnnn

Explanation:


User response:




Explanation:

Internal ISP error.

User response:




Explanation:

Internal ISP error.

User response:




Explanation:

Internal error.

User response:



BKMK8409E JCL library not valid.

Explanation:

Internal error.

User response:



BKMK8410E Parmlib token not valid.

Explanation:

Internal error.

User response:



BKMK8411E Allocate failed for ddnamexxxxxxxx

Explanation:

Allocation error.

User response:


BKMK8421E.

BKMK8412E Deallocate failed for ddnamexxxxxxxx.

Explanation:

Deallocation error.

User response:


BKMK8412E.

BKMK8417E Database token not valid.

Explanation:

Internal error.

User response:



BKMK8420E OPEN for temp JCL data set failed.

Explanation:

Internal error.

User response:







Explanation:


User response:



BKMK8501E ISP define errors.

Explanation:

Internal ISP error.

User response:



BKMK8507E ISP services error:xxxxxxxx

Explanation:

Internal ISP error.

User response:



BKMK8508E Global filter lookup failed.

Explanation:

Error reading global filter records in the database.

User response:



BKMK8601E Access request invalid.

Explanation:

User does not have access authority.

User response:

Proper access authority is needed to view or edit global

and universal filters.


Explanation:

Internal ISP error.

User response:




Explanation:

Internal ISP error.

User response:



BKMK8701E Incorrect data in passed parm.

Explanation:

Internal error.

User response:


Technical Support.

BKMK8702E INI token not found.

Token=xxxxxxxxxxxxxxxx

Explanation:

Correctable error.

User response:

Check the INI member for missing tokens, tokens

spelled incorrectly, or tokens in the wrong section.

BKMK8703E INI fetch of token failed. RC= nnnn

Token=xxxxxxxxxxxxxxxx

Explanation:

Correctable error.

User response:

Check the INI member. The token variable should be

the correct format. The token variable should be the

correct length. If a token variable is extended over more

than one line, make sure the line continuation character

(+) is used.

BKMK8704E ISP variable define failed. RC= nnnn

Explanation:

Internal error.

User response:


Technical Support.

BKMK8705E VPUT failed for

variablexxxxxxxxxxxxxxxx RC= nnnn

Explanation:

Internal error.

User response:


Technical Support.

BKMK8706E BRM01LIC LOAD failed.

Explanation:

Internal error.

User response:


Technical Support.



BKMK8708E Product code not found.

Explanation:

Correctable error.

User response:

If you have been issued a product license, then check

to make sure the code was entered correctly. If the

code format is correct then contact Technical Support.

BKMK8802E OPEN error RC=nnn

Explanation:

OPEN failed for database.

User response:



BKMK8803E CLOSE error RC=nnn

Explanation:

CLOSE failed for database.

User response:



BKMK8804E Update in progress.

Explanation:

Internal error.

User response:



BKMK8805E READNEXT failed RC=nnn.

Explanation:

Database I/O failed.

User response:



BKMK8806E READ failed RC=nnn

Explanation:


User response:



BKMK8807E STARTFWD failed RC=nnn.

Explanation:


User response:



BKMK8901E Open of pre-staged job list data set

failed.

Explanation:

OPEN failed for pre-staged data set.

User response:

Correctable error. Ensure the data set name is correct

and not in use.

BKMK8902E OPEN of converted job list data set

failed.

Explanation:

Open failed for job list data set.

User response:

Contact Technical Support with the error text.

BKMK8903E jobname greater than 8 characters,

jobname:xxxxxxxx

Explanation:

Invalid jobname in pre-staged data set.

User response:

Correctable error. Message BKMK8911I will show the

record number that is in error.

BKMK8904E Invalid jobname character: x

Explanation:


User response:



BKMK8905E Invalid jobname:xxxxxxxxx

Explanation:

Invalid JOBNAME in pre-staged data set.

User response:



BKMK8906E Continuation character (+) must be

preceded by a space.

Explanation:

Syntax error in pre-staged data set.

User response:



BKMK8907E Continuation character (+) invalid

before STRUC keyword.

Explanation:

Syntax error in pre-staged dataset.

User response:






Explanation:

Application name missing or greater than 8 characters.

User response:

Correctable error.

BKMK8909E Mask character (*) cannot be first or

only character of JOBNAME.

Explanation:


User response:



BKMK8910E Mask character (*) must be last

character.

Explanation:


User response:



BKMK8911I Job records read: nnnn.

Explanation:

This informational message shows the number of job

records read. If the job finished with a condition code of

zero, this is the input record total. Otherwise, this is the

number of records read when the error occurred.

User response:

None.

BKMK9001E OPEN of JOBTRAC job list data set

failed.

Explanation:

OPEN failed for JOBTRAC input data set.

User response:

Correctable error. Make sure the data set name is

correct and not in use.

BKMK9002E OPEN of converted job list data set

failed.

Explanation:

OPEN failed for output job list data set.

User response:


BKMK9003E OPEN of selected job list data set

failed.

Explanation:

OPEN failed for the job selection list data set.

User response:


BKMK9005E Invalid jobname:xxxxxxxxx

Explanation:


User response:



BKMK9006I Job records read: nnnn

Explanation:

This informational message shows the number of job

records read. If the job finished with a condition code of

zero, this is the input record total. Otherwise this is the

number of records read when the error occurred.

User response:

None.


Explanation:

Application name missing or greater than 8 characters.

User response:

Correctable error.




Messages (BKML)

BKMLIC01E No valid AUTHCODE= or LICENSES= in

INI

Explanation:

During program start, the product licensing values were

found to be in error.

User response:

Compare the //INI member’s ″:Product_security″ section

entries with those sent by Technical Support. If the

contents agree, character for character, contact

Technical Support. Have available the listing that

contains this message and the INI parmlib member.

BKMLIC02E AUTHCODE length not 12

Explanation:

During program start, the authorization code value was


User response:




Technical Support.. Have available the listing that


BKMLIC03W Authorization - days remaining: nnnn,

RC=4 Authorization - days remaining:

nnnn, RC=0

Explanation:

Your license for this product will no longer be valid after

the number of days shown. This product will function

normally until the license expires although the minimum

return code may be 4.

The RC=4 indicates that either

EXPIRATION_WARNING_RC was not specified in the

INI or the value was 4, meaning the calling program

was warned of this message, setting the minimal JOB

step return code to 4.

The RC=0 indicates that EXPIRATION_WARNING_RC

= 0 was specified in the INI, meaning the calling

program received a return code zero.

EXPIRATION_WARNING_RC = 0 allows those sites

who need a return code zero even with a warning

message so subsequent steps of batch JOBs will

execute correctly based on the return code.

User response:

If you are trialing this product, your evaluation period

will end soon as agreed by your trial agreement.

Contact you sales representative for further information.

If you have purchased a license for this product, you

need to contact Technical Support for an extension of

your license in accordance with your contact.

BKMLIC04E Error fetching EXPIRATION_DATE

Explanation:

During program start, the expiration date value was


User response:






BKMLIC05E EXPIRATION_DATE length not 6

Explanation:

During program start, the expiration date value was


User response:






BKMLIC06E Error fetching a CPUID

Explanation:

During program start, the CPUID value was found to be

in error.

User response:



contents character for character, contact Technical


message and the INI parmlib member.

BKMLIC07E A CPUID length was not 16

Explanation:

During program start, the CPUID value was found to be

in error.

User response:






BKMLIC08E License is too short.

Explanation:

IBM Confidential

217

During program start, one of the LICENSES= values

was found to be in error.

User response:






BKMLIC84E EXPIRATION_WARNING_DAYS invalid.

Explanation:

During program start, the

EXPIRATION_WARNING_DAYS value of the

:PRODUCT_SECURITY INI section was found to not

specify a number between 0 and 9999.

User response:

Change value and resubmit.

BKMLIC85E EXPIRATION_WARNING_RC not 0 or 4

Explanation:

During program start, the EXPIRATION_WARNING_RC

value of the :PRODUCT_SECURITY INI section was

found to not specify 0 or 4.

User response:

Change value and resubmit.

BKMLIC84E • BKMLIC85E IBM Confidential



Messages (BKMM)

BKMMER00I BKM01MER starting (REV=nn,

PMR=xxxxxxx, fixdate=xxxxxxxx

Explanation:

Message shows current version of the module.

User response:

None.

BKMMER01E Error parsing PARMLIB INI# member.

Error parsing PARMLIB INI member on

line n.

Explanation:

An error was found in when parsing an INI member.

User response:

Look for subsequent messages repair the PARMLIB(INI)

or PARMLIB(INI#) member as indicated.

BKMMER02E Umatched */ Continued statement at

end of file

Explanation:

An end-comment (*/) was found for which there was no

begin-comment (/*).

User response:

Remove the end-comment or insert a begin-comment in

the appropriate location.

BKMMER05E Token name longer than 72

Explanation:

A Token or Section name longer than 72 bytes was

found on the specified line.

User response:

Reduce the length of the token to 72 or less.

BKMMER06E Expected = after token name

Explanation:


User response:


value.

BKMMER07E Expected = after token name

Explanation:


User response:


value.

BKMMER08E Found non-NOTES token before 1st

section name

Explanation:

A Token was found before any Section was specified.

Only the ″Notes’ Token is allowed before a section

name Reminder, Notes is provided for the customer and

no product code can access the Notes value.

User response:

Ensure that the first non-comment line and non-Notes

token is a Section name.

BKMMER09E Duplicate Section/Token found

section token

Explanation:

A token can not be defined twice for the same section.

User response:

Remove the redundant token and retry.

BKMMER10E file-function fail, RC = nnnnnnnn

Explanation:


User response:


BKMMER11E Open failure, DD ddname/ DD INI

OPEN FAILURE/ DD SYSPRINT open

failure/DD UPDATE open failure/ DD

TRACEDD open failure

Explanation:


User response:


BKMMER12E Expected parm value or record,

found function

Explanation:


User response:


BKMMER14E Error parsing MSCINI

Explanation:

MSCINI INIMERGE failed to parse the MSCINI input

because it could not find the INIMERGE_SECTION

values.

User response:

IBM Confidential

219

Use the INI# member distributed by Technical Support

and retry. If you need help with this contact Technical

Support.

BKMMER15W Columns 73-80 not blank on line

Explanation:

INI parser detected characters in columns 73-80.

Technical Support has found that many INI errors occur

because the person editing the INI doesn’t see text in

columns 73-80.

User response:

Edit PARMLIB member INI so that columns 73-80 are

blank.

BKMMER21E System name more than 8 characters

Explanation:



User response:


BKMMER22E System name more than 8 characters

Explanation:

The system value on an INI section statement is invalid


User response:


BKMMER31E Section name longer than 72

Explanation:

The section name is limited in size.

User response:


BKMMER32E Invalid section name

Explanation:

The section name can have alphanumeric characters in

addition to a period, dash, underscore, or slash.

User response:


BKMMER33E Period(″.″) found in INI# section

Explanation:

A period character in the section name is valid in a

customer INI for denoting sysplex and system names

but is not valid in the distributed INI#.

User response:


BKMMER34E Qualified INIMERGE_VALUES in INI

Qualified PRODUCT_INFO in INI

Explanation:

These sections cannot be qualified by sysplex and

system name.

User response:


BKMMER35E Two INIMERGE_VALUES sections

found

Explanation:

The INIMERGE_VALUES may only appear once in INI.

User response:


BKMMER36E Qualified section after generic

Explanation:

A section was found with sysplex or system

qualifications but it follows the same section without

such qualification. This section can never be accessed

and is invalid.

User response:


BKMMER37E Duplicate unqualified section found

Explanation:

Two section names match exactly, then are either:

1. both unqualified

2. both specify the same Sysplex and system names.

Section names must be unique.

User response:


BKMMER38E Trailing period on section statement

Explanation:

A section statement has one of the following formats:

:sectionname.sysplexname.systemname

:sectionname.sysplexname

:sectionname..systemname

User response:


BKMMER39E INI# columns 73-80 are not blank, line

nnnn

Explanation:


debugging errors in INI difficult.

BKMMER15W • BKMMER39E IBM Confidential


User response:


BKMMER39W INI columns 73-80 are not blank, line

nnnn

Explanation:


debugging errors in INI difficult.

User response:


BKMMER40E Right of INI#’’s section not blank

Explanation:

INI#’s section statement must be all blanks after section

name to facilitate customers entering sysplex or system

names.

User response:


BKMMER41I Nothing copied

Explanation:

The customer INI had no special sections to copy.

User response:

None.

BKMMER42I Nothing to delete

Explanation:

No INI parameters were deleted.

User response:

None.

BKMMER50I INPUT: input line

Explanation:

A previously noted error occurred on the line shown.

User response:

See prior error message.

BKMMER51E Token non-NOTES before 1st section

Explanation:

NOTES is the only token allowed before the first section

statement.

User response:


BKMMER52E Token NOTES found in INI#

Explanation:

NOTES is only allowed in the customer INI.

User response:


BKMMER53E Error parsing MSCINI (INI#), see JOB

Log/Error parsing the customer INI,

see JOB Log

Explanation:

INIMERGE used the INI parser to validate the INI but

the INI parser was unsuccessful.

User response:

For INI#, Contact Technical Support. For the customer

INI, repair ABR INI based on the messages in the JOB

log and resubmit.

BKMMER71E Section in INI# but not INI:

Explanation:

INI view cannot find section in INI that was found the

INI#.

User response:


BKMMER72I All INI# sections found in INI

Explanation:

All of the INI# sections were found in INI.

User response:

None.

BKMMER73E Error in SYSPARM

Explanation:

Valid forms are:

SYSPARM= for current SYSPLEX and SYS name

SYSPARM=’’ for current SYSPLEX and SYS name

SYSPARM=’,’ for current SYSPLEX and SYS name

SYSPARM=’plexname,sysname’

User response:

Correct the SYSPARM on your execute statement and

resubmit.

BKMML111E Bad input character in license

xxxxxxxxxxxxxx

Explanation:

The displayed license or product code is invalid for a

variety of reasons:

v Authorization - invalid chars in authcode — invalid

chars in authcode

v Authorization - product expired — product expired

v Authorization - invalid juldate — invalid juldate

v Authorization - julian date does not match — julian

date does not match

v Authorization - cpu timed out — cpu timed out

v Authorization - product expired — product expired

BKMMER39W • BKMML111EIBM Confidential


User response:

Contact Technical Support concerning your licenses and

provide the text from the message.

BKMML112E Authorization - CPUID limit value is

zero or inconsistent for CPUID:

xxxx/Authorization - CPUID sequence

value is duplicated or too large for

CPUID: xxxx/Authorization - CPUID

parity is invalid for CPUID: xxxx.

Explanation:

An error was found in the CPUID values.

User response:



BKMML113E Authorization - product mismatch

Explanation:

Product code provided is not for this product.

User response:



BKMML114E Authorization - not licensed on this

CPU/Authorization - CPU S/N =

xxxxxxxxxxxx

Explanation:

A license was not found for this CPU.

User response:

Call Technical Support concerning your licenses and


BKMML115E Authorization - invalid chars in

FEATURE-1/Authorization - seq

mismatch in FEATURE-1

Explanation:

A license wasn’t found for this CPU.

User response:

Call Technical Support about your licenses and provide

the text from the message.

BKMML116E Authorization - validation failed

Explanation:

This product cannot be used because of licensing

problems displayed in prior messages.

User response:



BKMML134E Invalid block check of license

xxxxxxxxxxxxxx

Explanation:

The displayed license is not consistent.

User response:



BKMMOD01I Starting (rev=xxx,ptf=xxx,fixdate=xxx)

Explanation:

Indicates BKM01MOD is starting and its version.

User response:

Informational only.

BKMMOD02I DIFF option requires SYSUT2

Explanation:

DIFF compares loadlibs SYSUT1 and SYSUT2.

User response:

Correct JCL or execution parameter.

BKMMOD02I Terminating

Explanation:

Indicates BKM01MOD is terminating.

User response:

Informational only.

BKMMOD03E Unable to open SYSUT1

Explanation:

SYSUT1 is a required DD statement.

User response:

Correct JCL or execution parameter.

BKMMOD04E A duplicate PMR found module

Explanation:

The same PMR number was used twice in the same

module.

User response:

Informational only.

BKMMOD05E No PMR data available for ’SYSUT1

xxxxxxxx’ No PMR data available for

’SYSUT2 xxxxxxxx’

Explanation:

The load module has an EHDR, not

MSCHDR/MSCPMR macros.

User response:

Informational only.

BKMML112E • BKMMOD05E IBM Confidential


BKMMOD06E No Header data available for

’SYSUT1 xxxxxxxx’ No Header data

available for ’SYSUT2 xxxxxxxx’

Explanation:

The load module does not have MSCHDR/MSCPMR or

EHDR macros.

User response:

Informational only.

BKMMOD30E Fatal error in BKM01VV1

TABLE(table) FUNC(func) RC(rc)

Explanation:

An error occurred using an BKM01VV1 table.

User response:


BKMMOD91E Error READ_PDSE ERROR -

terminating

Explanation:

An error occurred reading a PDSE (not a PDS).

User response:


BKMMOD92E Error READ_PDS error - terminating

Explanation:

An error occurred reading a PDSE (not a PDS).

User response:


BKMMSL01E PGM NAME parm required

Explanation:

No program name was passed to BKM01MSL.

User response:


BKMMSL02E PGM NAME parm required

Explanation:

No program name was passed to BKM01MSL.

User response:


BKMMSL03E Second parm from SELECT

CMD/PGM not 10 bytes LEN =

nnnnnnnn MSVECTOR = vector-data

Explanation:


User response:


BKMMSL04E R2 not pointing to MSVECTBL

Explanation:


User response:


BKMMSL05E R2 does not point to valid vector

table R2 ADDRESS(DEC): nnnnnnnnnn

Explanation:


User response:


BKMMSL06E LOAD OF PGM FAILED module-name

Explanation:


User response:




BKMMSL07E DELETE OF PGM FAILED

module-name

Explanation:

An error occurred deleting module-name.

User response:


BKMMSL08E LOAD OF PGM FAILED module-name

Explanation:


User response:




BKMMSL09E DELETE OF PGM FAILED

module-name

Explanation:

An error occurred deleting module-name.

User response:


BKMMOD06E • BKMMSL09EIBM Confidential


IBM Confidential



Messages (BKMP)

BKMP1079E //SYSPRINT failed to OPEN

Explanation:

A critical JCL DD card could not be opened.

User response:


BKMP1080E Error fetching //SISPARM info, R15=

RC

Explanation:

During the first phase of BKM00001 startup, BKM00001

was unable to process the information from the

//SISPARM JCL statement.

User response:


BKMP1081E Error fetching AUTHCODE

Explanation:

During the second phase of BKM00001 startup,

BKM00001 was unable to fetch the AUTHCODE token

from the ALB_PRODUCT_SECURITY section of the

//SISPARM member.

User response:

Determine the error in the ″AUTHCODE″ token, and

restart BKM00001.

BKMP1082E AUTHCODE length not 12

Explanation:


BKM00001 fetched the AUTHCODE token from the

ALB_PRODUCT_SECURITY section, but it wasn’t 12

bytes long.

User response:

Determine the error in the ″AUTHCODE″ token, and

restart BKM00001.

BKMP1083E Error fetching EXPIRATION_DATE

Explanation:


BKM00001 was unable to fetch the JULDATE token

from the ALB_PRODUCT_SECURITY section of the

//SISPARM member.

User response:

Determine the error in the ″JULDATE″ token, and

restart BKM00001.

BKMP1084E EXPIRATION_DATE length not 6

Explanation:


BKM00001 fetched the JULDATE token from the

ALB_PRODUCT_SECURITY section, but it was not 6

bytes long.

User response:

Determine the error in the ″JULDATE″ token, and

restart BKM00001.

BKMP1085E Error fetching a CPUID

Explanation:


BKM00001 was unable to fetch a CPUID token from the

ALB_PRODUCT_SECURITY section of the //SISPARM

member.

User response:

Determine the error in the ″CPUID″ token, and restart

BKM00001.

BKMP1089E Product code mismatch

Explanation:

During product license checking, the product code,

embedded in the AUTHCODE value did not specify the

ALB family of products.

User response:

Ensure the AUTHCODE value specified is for the ALB

family of products. If they appear correct, call Technical

Support.

BKMP1094E Cannot load support module

″BKMA1MSG″ Cannot load support

module ″BKMA1DTC″

Explanation:

One or more support programs are missing from the

executable library.

User response:

Locate these programs in another product, or call

Technical Support.

BKMP1096E Allocation of //SYSPRINT failed:

R15=12,INFO=123456789

Explanation:

A critical JCL DD card could not be allocated.

User response:


BKMP1104I System variable xxxxxx converted to

yyyyyy used by ddddddd

Explanation:

IBM Confidential

225

A system variable, xxxxxx, was detected as the

VOLSER of a non-VSAM data set, dddddddd. Using

MVS’s symbol resolution service, the VOLSER was

changed to yyyyyy.

User response:

Ensure this substitution is correct for the system in

which the ABACKUP will be executed. At worst, the size

for the data set will be incorrect and the eventual load

balancing effect of BKM00002 may be compromised.

BKMP1105W Cannot determine value for system

variable xxxxxx used by ddddddddd

Explanation:

A system variable, xxxxxx, was detected as the

VOLSER of a non-VSAM data set. BKM00001 was not

able to resolve the variable. The data set will be placed

in the //SYSUT2 output file but the size will be listed as

0K.

User response:

Ensure this substitution is correct for the system in

which the ABACKUP will be executed.

BKMP1106E Selection DSN/MEMBER greater than

54 bytes ddddddddddd

Explanation:

A selection data set name found in an SELDSN

parameter was longer than 44 characters for a

non-member name DSN, or was longer than 54

characters for a member name DSN.

User response:

Fix the DSN name that is longer than 44/54 characters.

BKMP1107E Selection data set not LRECL=80,

RECFM=FB

Explanation:

During phase I processing of a selection data set, it was

found to be other than a LRECL 80, fixed length file.

User response:

Check that the specified SDS is really a SDS, which

has specific requirements set forth by HSM’s ABARS.

BKMP1108E Rejected:Cannot enlarge SVC26

workarea

Explanation:

During phase III processing of a selection data set, the

retry logic within BKM00001 attempted multiple

expansions of a catalog workarea. As the new

workarea(s) was not large enough, it can be assumed

that the program’s above 16MB region size was too

small to process the number of data sets chosen during

initial selection for a masked value.

User response:

Check values within IEFUSI for a limit of above 16MB

GETMAIN requests. Check the program’s region size.

Restrict the masked values for data set selection for the

INCLUDE, ACCOMPANY, and ALLOCATE keywords.

(″Restrict″ means place the first wildcard character

further to the right within a DSN mask. For example,

INCLUDE(A*.**) might be a list for millions of files, while

INCLUDE(AB*.**) may be hundreds of thousands, thus

within the reach of the region of BKM00001.)

BKMP1109W DSN not in catalog on line nnn

dddddddddddddddd

Explanation:

On line nnn of a selection data set, the specified file

was not in the catalog.

User response:

Determine why the file was in the SDS but did not exist.

BKMP1110E Rejected: Catalog access failure xxx

R15=RC Error Code=ec DSN=ddd

Explanation:

Catalog management returned a bizarre value to

BKM00001.

User response:

Check the message IDC3009 in the appropriate IBM

book for return code ″RC″ and reason code ″ec″. If the

problem cannot be resolved from the IDC3009 text,


BKMP1111E Critical catalog info missing on line

nnn ddddddddddddd

Explanation:

One or more critical catalog entries are missing for the

DSN or mask specified on line nnn. This would imply

that faulty data passed through the catalog

management interface.

User response:

Execute IDCAMS’s EXAMINE, DIAGNOSE ICFCAT and

DIAGNOSE VVDS commands for the catalog and

volume(s) of the file listed. Take action as needed.

BKMP1112W Catlg entry neither VSAM nor

non-VSAM on line nnn ddddddddddd

Explanation:

On line nnn a file name that was not a catalog, was not

part of a VSAM sphere, or was not a non-VSAM data

set was returned from catalog management.

User response:

Execute an IDCAMS LISTCAT ENT(...)ALL command

against this file name. Ensure that it is part of a VSAM

Sphere, a non VSAM data set, or a catalog. If it is one

of the above contact Technical Support or eliminate it

from the selection data set.

BKMP1105W • BKMP1112W IBM Confidential


BKMP1113W FMT1 DSCB obtain failed on line nnn

ddddddddddddddd

Explanation:

On line nnn the BKM00001 equivalent of a IEC143

S-213-04. A catalogued data set no longer is on disk, or

at least the designated disk.

User response:

Execute an IDCAMS DELETE DSN NOSCRATCH to

synchronize the catalog to the disk.

BKMP1114W FMT3 DSCB obtain failed on line nnn

ddddddddddddddd

Explanation:

On line nnn the BKM00001 equivalent of a IEC143

S-213-04. A catalogued data set no longer is on disk, or

at least the designated disk.

User response:

Execute an IDCAMS DELETE DSN NOSCRATCH to

synchronize the catalog to the disk.

BKMP1115W Error during GDG conversion on line

nnn dddddddd

Explanation:

On line nnn BKM00001 tried to convert a GDG looking

name to an absolute generation number. The

conversion failed.

User response:

Contact Technical Support for assistance.

BKMP1116E Must have DISTRIBUTE, INPUT, and

OUTPUT keyword

Explanation:

Three keywords are required for input to BKM00001.

User response:

If they all appear to be in the input stream, check for

continuation markers after each input record.

BKMP1117E Must have an ″AGGR″ and/or

″SELDSN″ keyword

Explanation:

Within the OUTPUT and INPUT parameters, there must

be a SELDSN or a AGGR parameter.

User response:

If they all appear to be in the input stream, check for

continuation markers after each input record.

BKMP1118E Aggregate name greater than 8 bytes

aaaaaaaa

Explanation:

An aggregate name found inside an AGGR parameter

was longer than 8 characters.

User response:

Fix the aggregate name that is longer than 8 characters.

BKMP1119E Must have a BY_COUNT or

BY_TOTAL_KB keyword

Explanation:

Within the DISTRIBUTE parameter, there must be a

BY_COUNT or a BY_TOTAL_KB parameter. If they all

appear check for continuation markers after each input

record.

User response:

Add the desired value to the DISTRIBUTE parameter.

BKMP1120E AGGNAME rejected by SMS aaaaaaaa

Explanation:

The decoded aggregate name was rejected by SMS.

User response:

Fix the spelling of the aggregate name.

BKMP1121E Selection DSN > 44 or MEMBER > 8

Explanation:

A selection data set name appeared to have a member

name. During parsing of the two values, either the DSN

was longer than 44 bytes or the member name was

longer than 8 bytes.

User response:

Fix the data set or member name.

BKMP1123E Invalid selection data set content on

line nnn

Explanation:

During decoding of a selection data set, one or more

errors were found. This message will be accompanied

by another message or series of messages.

User response:

Fix the errors.

BKMP1124E Unbalanced parenthesis in selection

data set on line nnn

Explanation:

During decoding of a selection data set, one or more

errors were found. This message will be accompanied

by another message or series of messages.

User response:

Fix the errors.

BKMP1125E DSN/Keyword string to long on line

nnn

Explanation:

On line nnn during decoding of a selection data set, a

DSN or selection data set keyword was longer than 50

bytes.

BKMP1113W • BKMP1125EIBM Confidential


User response:

Fix the error.

BKMP1126E Unexpected right paren on line nnn

Explanation:

On line nnn during decoding of a selection data set, a

″)″ was found before it was expected.

User response:

Fix the error.

BKMP1128E Missing ″(″ after keyword on line nnn

Explanation:

On line nnn a selection data set keyword (INCLUDE,

EXCLUDE, ...) was detected but was not followed by a

″(″.

User response:

Fix the error.

BKMP1129E Bad keyword on line nnn

Explanation:

On line nnn an invalid keyword was detected.

User response:

Fix the error.

BKMP1132E Bad GDG name on line nnn

Explanation:

On line nnn a GDG name with more than 4 characters

within the parenthesis was detected.

User response:

Fix the error.

BKMP1133E Missing ″)″ on line nnn

Explanation:

On line ″xx,xxx″ a ″)″ was missing.

User response:

Fix the error.

BKMP1134E DSN greater than 44 bytes on line nnn

Explanation:

On line nnn a data set name greater than 44 characters

was detected.

User response:

Fix the errors.

BKMP1135E DSNMASK greater than 50 bytes on

line nnn

Explanation:

On line nnn a masked data set name greater than 50

characters was detected.

User response:

Fix the errors.

BKMP1136E DSNMASK contains bad data on line

nnn

Explanation:

On line nnn a masked data set name contained

characters other than the valid data set name

characters and mask characters.

User response:

Fix the errors.

BKMP1137E Too many masks on line nnn

Explanation:

While decoding a series of selection data sets within

one aggregate (using an AGGR parameter) or during

decoding of a single selection data set (using an

SELDSN parameter) BKM00001 encountered more than

1 MB of INCLUDE data set names and masks; more

than 1 MB of EXCLUDE data set names and masks;

more than 100 KB of ACCOMPANY data set names and

masks; more than 100 KB of ALLOCATE data set

names and masks; more than 100 KB of

ACCOMPANYEXCLUDE data set names and masks; or

more than 100 KB of ALLOCATEEXCLUDE data set

names and masks.

User response:

Code fewer masks and data set names. If this large

number of data set names and masks are needed,


BKMP1138E ACS compare failed: xxxxxxxxxx

xxxxxxxxxxxxxxxxxxxxxx DSN compared:

xxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxx

ARG compared: xxxxxxxxxx


Explanation:

ACS compared failed for reason described.

User response:

Fix incorrect data set name or mask or fix incorrect filter

in the selection data set.

BKMP1139E BKM01CA1 GET error xxxxxxxxxxxxxxx


Explanation:

Catalog lookup failed for a data set. The data set that

caused the error was placed in the first output selection

data set.

User response:

If the user wants the data sets that had errors placed in

the correct selection data sets, then the catalog must be

corrected and loadbalancer must be rerun.

BKMP1126E • BKMP1139E IBM Confidential


BKMP1141E Too many INCLUDE keywords on line

nnn

Explanation:

On line nnn of a selection data set a duplicate keyword

was detected.

User response:

Remove the duplicate keyword.

BKMP1142E Too many ACCOMPANY keywords on

line nnn

Explanation:


was detected.

User response:


BKMP1143E Too many ALLOCATE keywords on line

nnn

Explanation:


was detected.

User response:


BKMP1144E Too many EXCLUDE keywords on line

nnn

Explanation:


was detected.

User response:


BKMP1145E Too many ACCOMPANYEXCLUDE

keywords on line nnn

Explanation:


was detected.

User response:


BKMP1146E Too many ALLOCATEEXCLUDE

keywords on line nnn

Explanation:

On line ″nnn″ of a selection data set a duplicate

keyword was detected.

User response:


BKMP1149E BKM01CA1 sendmask error xxxxxxxxx

xxxxxxxxxxxxxxxxxxxxxxxxx

Explanation:

Internal error. Not correctable.

User response:


BKMP1151I Starting processing for aggregate:

aaaaaaaa

Explanation:

The input aggregate appearing after this message is

being processed.

User response:

None.

BKMP1152I End of processing for aggregate:

aaaaaaaa

Explanation:

The input aggregate appearing after this message has

finished processing.

User response:

None.

BKMP1175I Relative generation used on line nnn

dddddddddddddd

Explanation:

During phase III processing of a selection data set, a

relative generation was converted to an absolute

generation number.

User response:

None.

BKMP1180I BKM00001 execution complete. Return

code is RC

Explanation:

The processing of BKM00001 is complete.

User response:

None.

BKMP1181I Selection data set being opened:

ddddddddddd

Explanation:

The input selection data set appearing after this

message is being opened during phase I of SDS

processing.

User response:

None.

BKMP1141E • BKMP1181IIBM Confidential


BKMP1182E Primary GETMAIN failure; Increase

region

Explanation:

BKM00001 could not obtain an adequate sized work

area, RC 12 accompanies this message.

User response:

Increase region size.

BKMP1183W Unable to completely free storage;

retrying

Explanation:

The cause of this message is bizarre -- storage can be

freed once obtained. In the unlikely event that

BKM00001 is unable to free storage, it issues this

message and continues.

User response:

Although the program continues, it is so odd that

Technical Support should be contacted.

BKMP1184W Conflicting CAT info; unable to calc

size dddddddddddddd

Explanation:

While processing a VSAM file, the control interval size

was less than 512 bytes or greater than 32,768 bytes.

As these are the limits set by IBM, it suggests that

something is wrong with the VVDS on the volume

where this file resides.

User response:

Execute the IDCAMS DIAGNOSE command and

proceed accordingly.

BKMP1185W Unknown device; TRKS instead of KB

ddddddddddddddd

Explanation:

BKM00001 could not determine if the data set was on

3380 or 3390 storage. The value in kilobytes is actually

the number of tracks occupied by the file. ″ddd...″ is the

DSN.

User response:

None.

BKMP1186I End of Keyword/DSN/DSN-MASK scan

Explanation:

Phase II processing of a selection data set is complete.

User response:

None.

BKMP1187I Useful data detected on line nnn tttt

Explanation:

During phase II processing of a selection data set, a

data set name or mask (tttt) found on line nnn of a

selection data set was detected and passed to phase III

processing.

User response:

None.

BKMP1188I ″ACCOMPANYEXCLUDE″ detected

Explanation:

During phase II processing of a selection data set, one

of the six allowable control statements was found.

User response:

None.

BKMP1189I ″ALLOCATEEXCLUDE″ detected

Explanation:



User response:

None.

BKMP1190I ″EXCLUDE″ detected

Explanation:



User response:

None.

BKMP1191I ″ALLOCATE″ detected

Explanation:



User response:

None.

BKMP1192I ″INCLUDE″ detected

Explanation:



User response:

None.

BKMP1193I ″ACCOMPANY″ detected

Explanation:



User response:

None.

BKMP1182E • BKMP1193I IBM Confidential


BKMP1194I Detected AR MODE -- correcting

Explanation:

While exiting a phase of BKM00001, it found itself in

access register mode instead of primary control mode,

which is very unusual.

User response:

None.

BKMP1195I Selection data set being closed:

dddddddddddddddddd

Explanation:

The input selection data set appearing after this

message is being closed during phase I of SDS

processing.

User response:

None.

BKMP1196E Cannot create access list entry. xxx

R15=RC R0=reason

Explanation:

BKM00001 uses two data spaces while processing

selection data sets. Each initial request is modest,

100KB, therefore the creation should always work. If it

fails, check if the installation has a limit (SMF exit

IEFUSI) for size of data spaces. According to the

OS/390® Installation Exits manual is far less than the

default maximum size.

aaaaaa is replaced by ″expand″ or ″create″, depending

on the function being performed.

xxx is replaced by an identifier depending on which data

space creation, expansion, or access list maintenance

failed.

rc and ″reason″ are the return code and reason code

values required to determine the actual cause of the

problem.

User response:

Check values within IEFUSI before contacting Technical


BKMP1197E Cannot aaaaaa dataspace. xxx R15=RC

R0=reason

Explanation:

BKM00001 uses two data spaces while processing

selection data sets. Each initial request is modest,

100KB, therefore the creation should always work. If it

fails, check if the installation has a limit (SMF exit

IEFUSI) for size of data spaces. According to the

OS/390 Installation Exits manual is far less than the

default maximum size.

aaaaaa is replaced by ″expand″ or ″create″, depending

on the function being performed.

xxx is replaced by an identifier depending on which data

space creation, expansion, or access list maintenance

failed.

rc and ″reason″ are the return code and reason code

values required to determine the actual cause of the

problem.

User response:

Check values within IEFUSI before contacting Technical


BKMP1198I BKM00001: Aggregate Load Balancing

- Build yyyymmdd hh.mm

Explanation:

Identifies the program execution date and time.

User response:

None.

BKMP1199E SVC99 fffffffff R15=rc Error code=ec

DSN=ddddddddd

Explanation:

Dynamic allocation or deallocation (ffffffff) for a selection

data set failed.

User response:

Ensure the selection data set is specified correctly. This

could be in the input control cards, or within the

aggregate definition inside SMS.

BKMP2079E //SYSPRINT failed to OPEN

Explanation:

A critical JCL DD card could not be opened.

User response:


BKMP2101E Record must be type 1, 2, 3, OR 4

Explanation:

The sequential file manipulation program placed

between BKM00001 and BKM00002 inserted a record

that was not in the correct format. The record is

displayed.

User response:

Fix the program.

BKMP2102E Corrupted numerics on control record

Explanation:

The type 1 control record was modified incorrectly by

the file manipulation program placed between

BKM00001 and BKM00002.

User response:

Fix the program.

BKMP1194I • BKMP2102EIBM Confidential


BKMP2103E Must have at least one output select

data set

Explanation:

After processing the type 1 OSEL and OAGG control

cards, there were no valid output data sets named.

Most likely, there will be messages prior to this one.

User response:

BKM00001 always produces the correct control records,

therefore it is probably the fault of the file manipulation

program placed between programs BKM00001 and

BKM00002. Fix the program.

BKMP2104E Cannot allocate dynamic work area

Explanation:

The region parameter is not large enough for the

number of output selection data sets.

User response:

BKM00001 always produces the correct control records,

therefore it is probably the fault of the file manipulation

program placed between programs BKM00001 and

BKM00002. Increase region size.

BKMP2105E Aggregate name does not exist in SMS

Explanation:

An aggregate name specified in BKM00001’s OUTPUT

AGGR parameter or inserted by the file manipulation

program between BKM00001 and BKM00002 was

incorrect.

User response:

Correct the name.

BKMP2106E ddname disappeared

Explanation:

A dynamically allocated data set disappeared in the last

few micro seconds.

User response:


BKMP2107E Cannot decipher the OSEL name

Explanation:

A selection data set name appeared to have a member

name. During parsing of the two values, either the data

set name was longer than 44 bytes or the member

name was longer than 8 bytes.

User response:

Fix the error.

BKMP2108E More SELDSNS/AGGS than expected

Explanation:

During user processing of the sequential file, type 1

OSEL or OAGG records were added by the file

manipulation program inserted between BKM00001 and

BKM00002 but the type BY record was not adjusted.

This is a warning, and processing continues.

User response:

None.

BKMP2109E Unidentified type 1 record

Explanation:

During user processing of the sequential file, the file


BKM00002 added an incorrect format type 1 record, or

modified an existing type 1 record incorrectly.

User response:

Fix the error.

BKMP2110E Unidentified record type

Explanation:

During user processing of the sequential file by the file


BKM00002, a record type was inserted that is

incompatible with the format of these two programs.

User response:

Fix the error.

BKMP2111W Found AGGNAME and SELNAME;

using AGGNAME

Explanation:

During either user processing of the sequential file by

the file manipulation program inserted between

BKM00001 and BKM00002 or normal processing of an

aggregate by BKM00001, both an aggregate name and

a selection data set name were added to a type 2

record. BKM00002 will use the aggregate name. This is

a warning: processing continues.

User response:

None.

BKMP2112E More than one type 1 trailer record

detected

Explanation:



BKM00002, the type 1 trailer record was duplicated.

User response:

Fix the error.

BKMP2113W Fewer OSEL/OAGG than expected,

continuing

Explanation:



BKM00002, several type 1 OAGG or OSEL records

were deleted, the values on type 1 OAGG or OSEL

BKMP2103E • BKMP2113W IBM Confidential


records were deleted and the values on the type 1 BY

record were not adjusted. This is a warning: processing

continues.

User response:

None.

BKMP2115W KBYTES corrupted; assuming 1KB

Explanation:



BKM00002, the type 2 data set record’s KB value was

corrupted. BKM00002 will assume the file size is 1 KB.

User response:

None.

BKMP2116W Cannot find suggested AGGNAME;

using distribution

Explanation:

During user processing of the file, an aggregate name

added to the record by the file manipulation program

inserted between BKM00001 and BKM00002, or added

by BKM00001 during normal processing, was not listed

in the type 1 OAGG records. Rather than rejecting the

record BKM00002 will choose an output selection data

set based on the DISTRIBUTE parameter.

User response:

None.

BKMP2117W Cannot find suggested SELNAME;

using distribution

Explanation:

During user processing of the file by the file


BKM00002, a selection data set name added to the

record was not listed in the type 1 OSEL records.

Rather than rejecting the record BKM00002 will choose

an output selection data set based on the DISTRIBUTE

parameter.

User response:

None.

BKMP2119W Skipping duplicate data set

Explanation:

BKM00002 determined this file appeared more than

once. This extra record will be rejected.

User response:

None.

BKMP2120E No ″1 by″ record detected

Explanation:

During user processing of the file by the file


BKM00002, the type 1 BY record was deleted.

User response:

Put it back.

BKMP2121E Type 1 trailer record missing

Explanation:



BKM00002, the type 1, 2, 3, or 4 trailer (9’s) record was

deleted.

User response:

Do not delete trailer records.


Explanation:




deleted.

User response:



Explanation:




deleted.

User response:



Explanation:




deleted.

User response:


BKMP2130E Non-zero return code from sort. Sort

RC is

Explanation:

The SORT utility program returned a non-zero return

code. As there are numerous causes for this, some

based on the SORT, and others based on BKM00002

logic, look for other messages that will explain why this

was non-zero.

User response:

Review other error messages from BKM00002, take

action as appropriate.

BKMP2115W • BKMP2130EIBM Confidential


BKMP2180I BKM00001 execution complete. Return

code is RC

Explanation:

The processing of BKM00001 is complete.

User response:

None.

BKMP2198I BKM00002: aggregate load balancing -

Build yyyymmdd hh.mm

Explanation:

Identifies the program execution date and time.

User response:

None.

BKMP2199E SVC99 fffffffff R15=rc error code =ec

xxxxxxxxxxxxx selection data set is

ddddddddddd

Explanation:

Dynamic allocation or deallocation (ffffffff) for a selection

data set failed. xxxxxxxxxxxxx indicates the source of

information for the selection data set name. OAGG

means the source was an aggregate while OSEL

means the source was the selection data set name as

specified in BKM00001.

User response:

Ensure the selection data set is specified correctly. This

could be in the input control cards, or within the

aggregate definition inside SMS. .

BKMPAR00I <variable message containing parser

tracing information>

Explanation:

Message produced when parser is in tracing mode.

User response:

None required.

BKMPAR01I which you specified as a keyword of

xxxx from line yyy

Explanation:

The message provides context for the error on a

previous line.

User response:

None required.

BKMPAR11E (1) <Literal not terminated before end

of line (2) <Literal not terminated

before end of input (3) <Literal not

terminated before end of line (4)

<Literal not terminated before end of

line

Explanation:

A literal was not properly terminated.

User response:

Correct the identified literal and resubmit.

BKMPAR11I Error on line ______ , processing

keyword _____

Explanation:

A literal was not properly terminated.

User response:

Correct the identified literal and resubmit.

BKMPAR12E 1) Error processing keyword -

keyword 2) Missing continuation

character after keyword - 3) Missing

continuation character after keyword -

Explanation:

Value for identified keyword was not specified.

User response:

Correct the identified keyword and resubmit.


keyword _____

Explanation:

Value for identified keyword was not specified.

User response:


BKMPAR13E (1) Simple keyword should have at

most one operand -

Explanation:

A right parenthesis must follow the identified keyword’s

parameters.

User response:



keyword _____

Explanation:

A right parenthesis must follow the identified keyword’s

parameters.

User response:


BKMPAR14E (1) Missing left parenthesis after

keyword- keyword(2) Missing left

parenthesis after keyword- keyword(3)

Missing left parenthesis after keyword-

keyword(4) Missing left parenthesis

after keyword- keyword(5) Missing left

parenthesis after - ITEM (6) Missing left

parenthesis after keyword - keyword (7)

Missing left parenthesis after keyword-

keyword(8) Missing left parenthesis

BKMP2180I • BKMPAR14E IBM Confidential


after keyword- keyword

Explanation:

A left parenthesis must follow the identified keyword or

value.

User response:



keyword _____

Explanation:

A left parenthesis must follow the identified keyword or

value.

User response:


BKMPAR15E (1) Found end of data, expected

parameter for - keyword (2) Found end

of data, expected parameter for -

keyword (3) Missing continuation

character ’ (4) Found end of data,

expected parameter for - keyword (5)

Missing left parenthesis after - ITEM (6)

Found end of data, expected parameter

for - keyword (7) End of data, expected

parameter for - keyword (8) End of data,

expected parameter for - keyword

Explanation:

Identified keyword is not closed properly.

User response:



keyword _____

Explanation:


User response:


BKMPAR16E (1) Left parenthesis not valid after -

keyword (2) Left parenthesis not valid

after - keyword (3) Left parenthesis not

valid after - keyword

Explanation:


User response:



keyword _____

Explanation:


User response:


BKMPAR17E (1) Missing continuation character

after - (2) Missing continuation

character after - (4) Missing

continuation character after - (5)

Missing continuation character after -

(6) Missing continuation character after

keyword - (7) Missing continuation

character

Explanation:


User response:



keyword _____

Explanation:


User response:


BKMPAR18E (1) Right parenthesis not valid after -

(2) Right parenthesis not valid after -

(3) Right parenthesis not valid after -

Explanation:


User response:



keyword _____

Explanation:


User response:


BKMPAR19I (1) Missing continuation missing

Explanation:

Keyword not completed before end of command.

User response:

Add a continuation character to the end of the line.

BKMPAR20E Expecting right parenthesis or

keyword for ___

Explanation:

This keyword’s operands are an ordered list of

keywords that end with a right parenthesis.

User response:


BKMPAR14I • BKMPAR20EIBM Confidential


BKMPAR21E (1) End of data while expecting ″*/″ (2)

End of data while expecting ″*/″ (3) End

of data while expecting ″*/″ (4) Found

end of data, expected expecting ″*/″ (5)

End of data while expecting ″*/″

Explanation:

A block comment was started on the indicated line but

was not terminated.

User response:

Correct the identified block comment and resubmit.

BKMPAR21I Error on line ___, comment block that

started on line ___

Explanation:

A block comment was started on the indicated line but

was not terminated.

User response:

Correct the identified block comment and resubmit.

BKM30E Missing ″=″ after keyword -

Explanation:



User response:



keyword _____

Explanation:



User response:


BKMPAR31E Missing ″=″ following keyword - _

Explanation:



User response:



keyword _____

Explanation:



User response:


BKMPAR32E Missing continuation - _

Explanation:

Continuation of line is expected and not found.

User response:



keyword _____

Explanation:


User response:


BKMPAR33E Missing continuation - _

Explanation:


User response:



keyword _____

Explanation:


User response:


BKMPAR34E Missing left parenthesis after =

Explanation:

Expecting ″Keyword=(″ but missing the left parenthesis.

User response:



keyword _____

Explanation:

Expecting ″Keyword=(″ but missing the left parenthesis.

User response:


BKMPAR35E Unknown keyword found- keyword

Explanation:

The language does not have this keyword.

User response:


BKMPAR21E • BKMPAR35E IBM Confidential



keyword _____

Explanation:

The language does not have this keyword.

User response:


BKMPAR36E Error with no prior /*, found -

Explanation:

″*/″ found without prior matching /*

User response:

Correct the identified comment block and resubmit.


keyword _____

Explanation:

″*/″ found without prior matching /*

User response:

Correct the identified comment block and resubmit.

BKMPAR37E Literal string exceeds limit of 1024

characters

Explanation:

Probable error with single and or double quotes.

User response:

Correct the quotes and resubmit.


keyword _____

Explanation:

Probable error with single and or double quotes.

User response:

Correct the quotes and resubmit.

BKMPAR51E Keyword should not be specified

twice - keyword

Explanation:

The input stream contains the indicated keyword twice.

Keywords can only occur once within a set of

parenthesis.

User response:

Correct the find the replicated keyword, remove one,

and resubmit.


keyword _____

Explanation:

The input stream contains the indicated keyword twice.

Keywords can only occur once within a set of

parenthesis.

User response:

Correct the find the replicated keyword, remove one,

and resubmit.

BKMPAR52E (1) Wrong number of reoccurring

parms for keyword - (2) Wrong number

of reoccurring parms for keyword -

Explanation:

The grammar requires that the parameters for the

identified keyword appear in groups of 2, 3, 4.

User response:

Correct the parameters for the identified keyword and

resubmit.


keyword _____

Explanation:

The grammar requires that the parameters for the

identified keyword appear in groups of 2, 3, 4.

User response:

Correct the parameters for the identified keyword and

resubmit.

BKMPAR53E Required parameter not specified for

keyword - keyword

Explanation:

The grammar requires that you specified the identified

keyword - it is a required keyword.

User response:

Add the keyword to the input and resubmit.


keyword _____

Explanation:

The grammar requires that you specified the identified

keyword - it is a required keyword.

User response:

Add the keyword to the input and resubmit.

BKMPAR54E Value specified is not valid for

keyword - keyword

Explanation:

Only a few valid values are permitted for the identified

keyword, you have not specified one of them.

User response:

Correct the parameter for the identified keyword and

resubmit.




keyword _____

Explanation:



User response:


resubmit.

BKMPAR55E One of a set of required keywords is

required, ex:

Explanation:

The syntax requires that you specify one of the

identified keywords but neither was found.

User response:

Add one of the keywords to your input and resubmit.


keyword _____

Explanation:

The syntax requires that you specify one of the

identified keywords but neither was found.

User response:

Add one of the keywords to your input and resubmit.

BKMPAR56E Only one of the follow keywords is

allowed - keyword

Explanation:

The syntax requires that you specify only one of the

identified keywords but both were found.

User response:

Remove one of the keywords from your input and

resubmit.


keyword _____

Explanation:

The syntax requires that you specify only one of the

identified keywords but both were found.

User response:

Remove one of the keywords from your input and

resubmit.

BKMPAR57E Value specified is not valid for

keyword - keyword

Explanation:



User response:


resubmit.


keyword _____

Explanation:



User response:


resubmit.

BKMPAR58E Value must be numeric for keyword -

keyword

Explanation:

The indicated keyword permits only numeric values

consisting of integers 0-9.

User response:


resubmit.


keyword _____

Explanation:

The indicated keyword permits only numeric values

consisting of integers 0-9.

User response:


resubmit.

BKMPAR59E An incorrect count of parameters for

keyword - keyword

Explanation:

You have exceeded the allowed number of parameters

for the identified keyword or have not specified enough

parameters.

User response:

Correct the parameters for the identified keyword.


keyword _____

Explanation:

You have exceeded the allowed number of parameters

for the identified keyword or have not specified enough

parameters.

User response:


BKMPAR60E Invalid HEX value.

Explanation:

Hexadecimal literals require:

1. Format of x’abcd’ or X’abcd’.

2. Have an even number of valid hex digits

0123456789abcdefABCDEF

BKMPAR54I • BKMPAR60E IBM Confidential


User response:



keyword _____

Explanation:

Hexadecimal literals require:

1. Format of x’abcd’ or X’abcd’.

2. Have an even number of valid hex digits

0123456789abcdefABCDEF

User response:


BKMPAR71E More right parentheses found than

left parentheses

Explanation:

While processing another error, the parser discovered

that there is not a matching set of left and right

parentheses.

User response:

Determine if prior error was caused by missing or extra

parenthesis.

BKMPAR72E More left parentheses found than

right parentheses

Explanation:

While processing another error, the parser discovered

that there is not a matching set of left and right

parentheses.

User response:

Determine if prior error was caused by missing or extra

parenthesis.

BKMPAR73E Unable to open input DDNAME xxx

Explanation:

DDNAME was missing or invalid.

User response:

Modify the jcl to include the DDNAME shown.

BKMPAR91E (1) Internal error, get_keyword found

id=zero (2) Internal error, get_keyword

found id=zero (3) Internal error,

get_keyword found invalid (4) Internal

error, unknown keyword type (5)

Internal error, PDITEM MUTEXCL not in

same DSECT (6) Internal error, PDITEM

count invalid (7) Internal error, PDITEM



count invalid (10) Internal error, file get

after end of input (11) Internal error,

get_keyword found invalid

Explanation:


User response:


BKMPAR92E No rules specified.

Explanation:

An error has occurred during parsing.

User response:


BKMPAR93E Bad grammar, optional positional

parms before keyword.

Explanation:

An error has occurred during parsing. Error should only

occur during grammar development.

User response:


BKMPAR94E Missing required positional

parameter.

Explanation:

A positional parameter has a required positional

parameter that was not specified.

User response:

Add the required positional parameter.

BKMPAR94E Missing required positional

parameter.

Explanation:

A positional parameter has a required positional

parameter that was not specified.

User response:

Add the required positional parameter.

BKMPAR98E (1) Kw_names properties not coded

grammar

Explanation:


User response:


BKMPAR99E

Explanation:


User response:

Read following messages for more information.



BKMPLD01E Subtask ABEND Recovery in

Progress.

Explanation:

Module Manager Subtask BKM01PLD has detected an

ABEND. The ABEND is being recovered. Refer to other

messages in the Syslog and Joblog to identify the

ABEND code.

User response:

Ensure that the product has been called correctly. If the

cause of the ABEND cannot be determined, contact

Technical Support.

BKMPLD02w LOAD Failed, PGM= ________

RC=___

Explanation:

Program module-name could not be loaded.

User response:




BKMPLD03W DELETE Failed, PGM= ________

RC=___

Explanation:

Program module-name could not be deleted.

User response:


BKMPLD04E R2 does not point to valid vector

table

Explanation:

Invalid parameters passed to BKM01PLD.

User response:


BKMPLD06W Load Library OPEN Failed, DD=

________ RC=___

Explanation:

DDNAME ddname could not be opened.

User response:

If ddname is one that can be specified in the JCL,

specify it, otherwise contact Technical Support.

BKMPLD07W Load Library CLOSE Failed, DD=

________ RC=___

Explanation:

DDNAME ddname could not be CLOSEd.

User response:


BKMPP100I text

Explanation:

Message produced when command input is read.

User response:

None required.

BKMPP101E Input file not open.

Explanation:

Message produced when command input is parsed.

User response:


BKMPP102E Input file LRECL invalid

Explanation:


This error typically occurs if SYSIN DD statement refers

to a data set with LRECL other than 80.

User response:

Correct the command input and resubmit.

BKMPP103E Blank record invalid here

Explanation:


User response:


BKMPP104E Expected continuation not found

Explanation:


User response:


BKMPP105W Input flushed

Explanation:

Message produced when command input is parsed and

a prior error has been detected.

User response:

Review the prior BKMPP1 error messages. Correct the

command input and resubmit.

BKMPP106E Unmatched parenthesis

Explanation:


User response:


BKMPLD01E • BKMPP106E IBM Confidential


BKMPP107E Paren nesting error

Explanation:


User response:


BKMPP108E Line buffer full

Explanation:


User response:


BKMPP109E String delimiters not balanced

Explanation:


Second quotation character not found.

User response:


BKMPP110E Input record buffer length invalid

Explanation:


User response:


BKMPP203E Blank input line invalid

Explanation:

The SYSIN input found a blank line when expecting a

continuation. The SYSIN text will be printed up to the

point of the error.

User response:

Correct the SYSIN input and resubmit.

BKMPP204E Expected continuation not found

Explanation:

The SYSIN input did not continue on an additional line

as expected. The SYSIN text will be printed up to the

point of the error.

User response:


BKMPP205E Input Flushed

Explanation:

Because of other errors already printed, the remainder

of the SYSIN will be ignored. The SYSIN text will be

printed up to the point of the error.

User response:


BKMPP206E Unmatched parenthesis

Explanation:

The end of the SYSIN was reached while expecting a

closing right parenthesis. The SYSIN text will be printed

up to the point of the error.

User response:


BKMPP207E Paren nesting error

Explanation:

More right parenthesis characters have been seen than

left parenthesis characters. The SYSIN text will be

printed up to the point of the error.

User response:


BKMPP208E Input buffer full

Explanation:

SYSIN buffer has been exceeded for the current

command. The SYSIN text will be printed up to the

point of the error.

User response:


BKMPP209E xxxxxx delimiters not balanced

Explanation:

Right quotes haven’t been found to match the left single

or double quotes for the string or hex quoted value. The

SYSIN text will be printed up to the point of the error.

User response:


BKMPSE20I Command ended

Explanation:



User response:

Review the prior BKMPSE error messages. Correct the


BKMPSE21E Keyword not found : text

Explanation:

Message produced when command input is parsed. The

displayed keyword is not valid for this command or

parent keyword.

User response:

Review the prior BKMPSE error messages. Correct the


BKMPP107E • BKMPSE21EIBM Confidential


BKMPSE22E Module not found: module-name

Explanation:


User response:


BKMPSE23E Operand not supported for: text

Explanation:


displayed keyword is not implemented.

User response:


BKMPSE24E Operand truncated for:

Explanation:


value specified for the displayed keyword is longer than

the keyword accepts.

User response:


BKMPSE25E Empty or missing parmlist

Explanation:



User response:


BKMPSE26W Command abandoned

Explanation:



User response:

Review the prior BKMPSE error messages.

BKMPSE28E Operand required for keyword:

keyword

Explanation:


displayed keyword requires a value.

User response:


BKMPSE29E Conflicting keywords specified with

keyword:

Explanation:


Two mutually exclusive keywords have been specified.

User response:


BKMPSE30E Multiple use of keyword not allowed

Explanation:


Two mutually exclusive keywords have been specified.

User response:


BKMPSE22E • BKMPSE30E IBM Confidential



Messages (BKMS)

BKMS1000I ssssss

Explanation:

This is a self explanatory informational message.

User response:

If explanation is necessary, contact Technical Support.

BKMS1001E Invalid ″BKMCXCOM″ control block

Explanation:


User response:


BKMS1002E ″GET″ function requested but there

was no active SENDMASK

Explanation:


User response:


BKMS1003E Expected ″DATA″ in ″WHAT_NEXT″

found %1

Explanation:


User response:


BKMS1004E R2 is not pointing to ″MSVECTBL″

Explanation:


User response:


BKMS1005E MLA value found greater than 4

Explanation:


User response:


BKMS1006W Error calling BKM01HSM RC=%1

Explanation:


User response:




BKMS1007E CSI failed when calling for %1

Explanation:


User response:


BKMS1008W No MCDS DSN(s) found in HSM

address space

Explanation:

An attempt was made to find the data set names of the

MCDS(s) allocated to HSM. The attempt failed.

User response:


for this data set.

BKMS1009I No catalog entries found for mask: %1

Explanation:

No entries were found in any of the catalogs searched

that matched mask %1.

User response:


BKMS1010E Filter validation failed string =″%1″

error = %2

Explanation:

Mask did not adhere to restrictions.

User response:

Fix the mask and retry.

BKMS1011E Error from filter routine DSN=%1

Filter=%2 Error=%3 %AD %LD

Explanation:

Invalid data set name %1 found in catalog.

User response:

Fix the catalog and retry.

BKMS1012E Error updating catalog table

Explanation:


User response:


BKMS1013E Unexpected return code from catalog

reader

Explanation:

IBM Confidential

243


User response:


BKMS1014W Dynamic allocation failed for catalog

%1 - Will not be used for search

Explanation:

Allocation failed for catalog named. The catalog will not

be used when searching for data sets that match the

masks.

User response:

If this is a problem, determine the cause and retry. If

unable to determine the cause, contact Technical

Support.

BKMS1015W Open failed for catalog %1 - Will not

be used for search

Explanation:

Allocation failed for catalog named. The catalog will not

be used when searching for data sets that match the

masks.

User response:

If this is a problem, determine the cause and retry. If

unable to determine the cause, contact Technical

Support.

BKMS1016E Error reading self describing record

from catalog - %1

Explanation:


User response:


BKMS1017W Associated entry not found in

catalog- %1 (%AD %LD )

Explanation:

This is an internal error. An associated entry with an

association of %1 was not found in the catalog. The

most probable cause is an orphaned catalog entry.

User response:


BKMS1018W Volume not mounted: VOL=%1

DSN=%2 (%AD %LD)

Explanation:

This is an internal error. A catalog entry specified that

data set %2 was cataloged to a volume, %1, but the

volume was not mounted on this system.

User response:

Processing continues without the volume statistics for

this data set on this volume.

BKMS1019W VVDS record not found VOL=%1

DSN=%2 (%AD %LD)

Explanation:

This is an internal error. A catalog entry specified that

data set %2 was cataloged to a volume,%1, but the

volume was not mounted on this system.

User response:

Processing continues without the volume statistics for

this data set on this volume.

BKMS1020W No MCDS was found with a valid

key-range: %1

Explanation:



space had a key-range that would accommodate the

data set name.

User response:


for this data set.

BKMS1021W Migrated data set not found in

MCDS:%1

Explanation:

The catalog indicated data set nnnn was migrated, but

no entry was found in the HSM MCDS.

User response:


for this data set.

BKMS1022W Error obtaining VTOC data:

VOL=%1DSN=%2 RETCODE=%3

REASON=%4 (%AD %LD)

Explanation:

An error occurred when attempting to access the VTOC

on volume %1 for data set %2.

User response:

Processing continues. No volume data will be included

for this data set.

BKMS1023E Invalid function call

Explanation:


User response:


BKMS1101E Abandoned data set on volume %1: %2

Explanation:

Uncataloged data set %2 was found on volume %1.

User response:

BKMS1014W • BKMS1101E IBM Confidential


Return code and processing are determined by the

backup options.

BKMS1102E Error from filter routine

DSN=%1FILTER=%2 ERROR=%3 (%AD

%LD)

Explanation:

The database is corrupted in a way that cannot be

corrected by the health checker.

User response:

Fix the catalog and retry.

BKMS1121E Database corrupted - need to unload /

reload (%AD %LD)

Explanation:

The database is corrupted in a way that cannot be

corrected by the health checker.

User response:

Unloaded IDS using UNLOADIDS and reloaded using

LOADIDS.

BKMS8000E Error calling BKM01VV1

Function=%1Table=%2 Retcode=%3

Reason=%4 (%AD %LD)

Explanation:

A problem occurred using a dataspace. %2 is the name

of the internal table. %5 is the location where the error

occurred.

User response:

Processing terminates. Contact Technical Support. Have


parmlib member that controls execution.

BKMS8001E Dynamic allocation failed for %1 %2

(%AD %LD)

Explanation:

Allocation failed for ddname|dsname name.

User response:


BKMS8002E Dynamic unallocation failed for %1 %2

Explanation:

Unallocation failed for ddname|dsname name.

User response:


BKMS8003E Unresolvable internal error - (%AD

%LD)

Explanation:


User response:


BKMS8004E Error using%1RETCODE=%2

REASON=%3

Explanation:

A problem occurred using module/macro %1.

User response:



controls execution.

BKMS8005E Severe error when attempting to

retrieve INI data - Section:%1 Token:

%2

Explanation:



parmlib.

User response:



for the failure, contact Technical Support and have


parmlib member.

BKMS8006E INI options missing or invalid. -

Section:%1 Token: %21 (%AD %LD)

Explanation:



parmlib.

User response:



for the failure, contact Technical Support and have


parmlib member.

BKMS8007E Error attempting to open ddname %1

(%AD %LD )1 (%AD %LD)

Explanation:

An open error occurred when attempting to open

ddname %1.

User response:

Processing terminates. Fix the problem and retry. If

unable to correct the problem, call Technical Support

and have available the listing that contains this

message.

BKMS8008E Required DD statement missing: %1

(%AD %LD)

Explanation:

A required DD statement is missing.

BKMS1102E • BKMS8008EIBM Confidential


User response:

Correct the JCL and retry.

BKMS8009I DD STATEMENT NOT FOUND:%1- %2

SKIPPED (%AD %LD)

Explanation:

An optional DD statement (%1) for function (%2) was

not found.

User response:

Processing continues, retry.

BKMS8010E Syntax error in exec parameter(s)

Explanation:

The parameters on the EXECUTE statement is invalid.

User response:

Correct the parameters and retry.

BKMS8011E ERROR FROM FILTER ROUTINE

DSN=%1FILTER=%2 ERROR=%3

Explanation:


User response:




message.

BKMS8012E SYSIN PARAMETER ERROR:%1

Explanation:

Control statement parameter %1 is invalid.

User response:




message.

BKMS8013W Volume not mounted: VOL=%1

Explanation:

Volume %1 was not mounted on this system.

User response:

Processing continues without this volume.

BKMS8014W Error calling CSI -

MODID=%1RETCODE=%2 REASON=%3

Catalog=%4

Explanation:

Errors were found in at least one of the data set entries

returned from this catalog.

User response:

Processing continues. Check output for accuracy.

BKMS8015E CSI call failed - Modid=%1 Retcode=%2

Reason=%3 Catalog=%4

Explanation:

Catalog Search Interface call failed.

User response:

Processing terminates. Save diagnostic data and call

Technical Support.

BKMS8016E Mutually exclusive keywords: %1 | %2

Explanation:

Mutually exclusive keywords were found in the

command SYSIN.

User response:

Processing terminates. Correct the error and retry or

call Technical Support.

BKMS8017E Failure reason text

Explanation:

Compress / uncompress of IDS record failed due to

failure reason.

User response:

This is an internal error, correct the error and retry.

Contact Technical Support and have available the listing

that contains this message and the parmlib member.

BKMS8018E Inventory database conversion has

already completed -

Modid=mmmmmmmm Retcode=nnnn

Conversion_Number=nnnn

Explanation:

An attempt was made to convert the Inventory Data Set,

but the conversion has already taken place.

MODID=name of program issuing the message.

Retcode= is the return code from the program.

Conversion_Number= is the identifier for the type of

conversion.

User response:

No action necessary, Inventory Data Set already

converted.

BKMS8019E Error occurred during VSKIP

processing.

Explanation:

A VREADUP was executed to retrieve a record from the

IDS. It was subsequently determined that the record did

not need updating and a VSKIP was issued to bypass

the update. An error occurred.

User response:

Contact Technical Support for help in determining the

seriousness of this error.

BKMS8009I • BKMS8019E IBM Confidential


BKMS8020E Error occurred updating the IDS during

conversion processing

Conversion_Number=nnnn

Explanation:

During Inventory Data Set conversion processing, an

error occurred updating the IDS. Conversion_Number=

is the identifier for the type of conversion process.

User response:

This type of error will usually have other error messages

accompanying it. Refer to those messages for further

clarification of the error and what to do about it. Contact

Technical support if more help is needed.

BKMS8021E Error occurred during VREWRITE

processing

Explanation:


Inventory Data Set.

User response:

Retry the application. If the problem persists, contact

Technical Support.

BKMS8022E Error occurred during VWRITE

processing. - MODID=mmmmmmmm

Explanation:


Inventory Data Set.

User response:

Retry the application. If the problem persists, contact

Technical Support.


processing - duplicate record -

MODID=mmmmmmm.

Explanation:

An error occurred when trying to write a record in the

Inventory Data Set but, unexpectedly, a duplicate record

was encountered.

User response:




processing - no space in the IDS. -

Modid=mmmmmmmm.

Explanation:

An error occurred when trying to write a record in the

Inventory Data Set but, there was no space left to hold

the record.

User response:

Follow the directions in the User Guide for adding space

to the Inventory Data Set and retry the function.

BKMS8025E Error, conversion record not found. -

Modid=mmmmmmmm

Explanation:

An attempt was made to update an Inventory Data Set

conversion record, but it was not found.

User response:

This occurs if a conversion process was done out of

order. Review the conversion process documentation

and if it was not performed in the correct order, re-do

the process. If it was done in order, contact Technical

Support for help in resolving this issue.

BKMS8026E VREADUPD error. -

MODID=mmmmmmmm

Explanation:

An attempt was made to read a record for updating

from the Inventory Data Set, the read failed.

User response:



BKMS8027E IDS open error. - Modid=mmmmmmmm

Explanation:

An attempt was made to open the Inventory Data Set

for processing.

User response:

Make sure the function is pointing to the Inventory Data

Set. If the function is pointing to a properly formatted

Inventory Data Set, make sure it is not being held

exclusive by some other application. Contact Technical

Support if more help is needed to resolve this issue.

BKMS8028E Parm check failed - more than nnnn

parms passed in -

MODID=mmmmmmmm

Explanation:

Program mmmmmmmm was being called by another

program but the calling program passed an incorrect

number of parameters.

User response:

Call the module with the correct number of parms. If the

program was called with the correct number of parms,

verify the link or call used the VL parameter that sets

the high order bit on the last parameter.

BKMS8029I Backup and Recovery Manager

Release 6.01 Inventory Data set

conversion process started:

Explanation:

Informative message indicating the conversion process

has started.

User response:

No action necessary.

BKMS8020E • BKMS8029IIBM Confidential


BKMS8030I Conversion number = nnnn

Explanation:

Informative message indicating the type of conversion

process occurring.

User response:


BKMS8031I Conversion description = ddd......ddd

Explanation:

Informative message providing a description of the

conversion process occurring.

User response:


BKMS8032I Conversion result = rrr...rrr

Explanation:

Informative message providing the results of the

conversion process. There are 3 possible results:

1. Successful

2. Previously completed successfully

3. Failed

User response:

No action necessary for results 1 & 2. If result 3 occurs,

contact Technical Support for help in determining the

cause of the failure.

BKMS8034W Unsupported or no tape management

sub-system

Explanation:

The tape sub-system is not RMM, CA-1, or TLMS. If

using TLMS the reason could be the inability to allocate

the TLMS data set or it is NULL.

User response:

Processing continues but no data set statistics can be

obtained.

BKMS8035W DSNAME VOLSER FILESEQ : reason

Explanation:

No entry was found in the tape management database

for dsname on volume/fileseq.

User response:

Processing continues but no data set statistics can be

obtained for this data set.

BKMS8036W Bad VTOC DSN encountered. DSN=

dsn , ON VOL= volser entry ignored,

processing continues

Explanation:

While scanning a DASD volume’s VTOC, a bad data set

name was encountered. The name does not conform to

data set naming standards. It is assumed then that this

a non-standard data set.

User response:

This is a warning message only meant to inform the

user of the bad data set on the volume. Processing

continues.

BKMS8037W Unable to process the VTOC on

VOL=volser. The error occurred using:

module name Retcode=nn Reason=nn.

The volume is ignored and processing

continues.

Explanation:

An error occurred attempting to access a DASD

volume’s VTOC. The module name plus a return code

and reason code for the failure is printed. The volume is

ignored and processing continues.

User response:

This is a warning message only meant to inform the

user of the software’s inability to access a volume’s

VTOC. Look at the VOLSER printed, it may be obvious

as to why it cannot be accessed. Failing this, try doing a

VTOC listing of the volume using ISPF. This also may

show an obvious reason as to why the volume cannot

be accessed. If it is possible to get a VTOC listing of

the volume, contact Technical Support for help with this

problem. Be sure to include the error messages plus a

VTOC listing of the volume.

BKMS8038E Required parameter missing: nnn

Explanation:

A require parameter is missing.

User response:

Processing terminates. Correct the syntax and retry.

BKMS8039E Aggregate construct not found: nnn

Explanation:


User response:

Processing terminates. Define the aggregate using

ISMF, activate a new configuration and retry the job.

BKMS8040I Volume dumped: nnn

Explanation:

This is an informational only message.

User response:

None.

BKMS8030I • BKMS8040I IBM Confidential


BKMS8041W No supported function found.

Explanation:

No supported function was found in the job step being

tracked.

User response:

Tracking is suspended.

BKMS8042E Message does not adhere to

restrictions: nnn

Explanation:

A SYSOUT message being parsed was not what was

expected.

User response:

Tracking is suspended.

BKMS8043E Unsupported backup - Reason: nnn

Explanation:

A backup could not be supported for reason nnn.

User response:

This backup will not be tracked.

BKMS8044E Authorization check failed

Explanation:

Authorization checking for this function failed.

User response:

If you are licensed for this function, Contact technical

support.

BKMS8045E Invalid parm: ppppp

Explanation:


User response:


BKMS8999I Message string

Explanation:

A self explanatory message.

User response:

None.

BKMS8041W • BKMS8999IIBM Confidential


IBM Confidential



Messages (BKMV)

BKMVE101E No INIT function received.

Explanation:


User response:


BKMVE102E INIT function received without

intervening term

Explanation:


User response:


BKMVE103E Unknown function: xxxx

Explanation:


User response:


BKMVE104E Error calling BKM01VV1 xxxx R15=rc

R0=rea ID=nn

Explanation:


User response:


BKMVE105E MLA value found greater than 4

Explanation:


User response:


BKMVE106E Mask failed evaluation check: xxxx

Explanation:


User response:


BKMVE107E CSI failed when calling for master

catalog name

Explanation:


User response:


BKMVE108E Mask failed evaluation check: xxxx -

yyyyy

Explanation:

Mask xxxx is invalid for reason yyyyy

User response:


BKMVE109E Un-allocation failed for: cccc

Explanation:

Un-allocation failed for catalog cccc.

User response:

Determine the reason for and fix the problem, retry the

function.

BKMVE110E Allocation failed for: cccc

Explanation:


User response:


BKMVE111E UCBLOOK error for: vvvv - return code:

rc reason code: rsn

Explanation:


User response:


BKMVE112E Volume not mounted: vvvv DSN: nnn

devtype: ttt

Explanation:



name nnn on device type ttt.

User response:



BKMVE113E IOSCAPU error for: vvvv - return code:

rc reason code: rsn

Explanation:


User response:


BKMVE114E nnnn : VOLSER=vvvv RC=rrr, Reas=sss,

Desc=zzzz

IBM Confidential

251

Explanation:


volume vvvv for data set nnnn . rrr = Return code. sss =

Reason code. zzzz = description when available.

User response:



BKMVE115E UCBPIN error for: vvvv - return code: rc

reason code: rsn

Explanation:


User response:


BKMVE116E CVAF error: Return code: rc Status

code: sc Volume: vvvv ID=nn Prev

func:ffff

Explanation:


User response:


BKMVE117E Error obtaining VTOC data from vvvv :

nnnn

Explanation:



User response:



BKMVE118E HSM MCVT not found

Explanation:



not been started.

User response:



BKMVE119E HSM data extract ended with errors

Explanation:



not been started.

User response:



BKMVE120E Migrated data set not found in MCDS:

nnnn

Explanation:



User response:



BKMVE121W No catalog entries found for mask(s)

Explanation:


passed to BKM01VE1.

User response:




BKMVE122E Associated entry not found in catalog -

nnnn

Explanation:




User response:



assistance.

BKMVE123E Unexpected catalog record construct -

association cell not where expected

Explanation:


User response:



assistance.

BKMVE124E Type ″J″ record with no matching ″B″

record: nnnn

Explanation:



User response:



assistance.

BKMVE115E • BKMVE124E IBM Confidential


BKMVE125E Error reading self describing record

from catalog: nnnn

Explanation:


User response:


BKMVE126E Received a ″GET″ request before

receiving a mask

Explanation:


User response:


BKMVE127E Input control block is not compatible

Explanation:


User response:


BKMVE129E HSM is not active - unable to retrieve

requested data

Explanation:


User response:


BKMVE130I Allocation failed for: nnnn - will not be

used for search

Explanation:



User response:


BKMVE131E Volume not mounted: vvvv DSN=nnn

Devtype: ttt

Explanation:


to a volume, vvvv, that was not mounted for DSN nnn

on device type ttt.

User response:



BKMVE132E No MCDS data set with valid key-range

found

Explanation:




data set name.

User response:


for this data set.

BKMVE133E NO MCDS DSN(s) found in HSM

address space

Explanation:

An attempt was made to find a the data set names of

the MCDSs allocated to HSM. The attempt failed.

User response:


for this data set.

BKMVE134W Error calling BKMHSM RC=rc

Explanation:


User response:




BKMVE135E nnnn : VOLSER=vvvvvv - VVDS not

open

Explanation:

A previous OPEN failed for the VVDS on volume vvvvvv

failed.

User response:


for data set nnnn.

BKMVE136W Invalid DSN found :

xxxxxxxxxxxxxxxxxxx

Explanation:


first BKMVE136W shows the data set name in character

format. The next three BKMVE136W show the name in

hex.

User response:


BKMVE137W Open failed for: nnnn - will not be

used for search

Explanation:

Unable to open catalog nnnn. No entries that might


User response:


BKMVE125E • BKMVE137WIBM Confidential


BKMVE138E Cluster not found for TRUENAME in

catalog -

Explanation:



cluster entry.

User response:



BKMVE139I Retrying error obtaining ??????? for

dsn - ucat

Explanation:






User response:


errors BKMVE117E, BKMVEx20E, or BKMVEx14E

occur. See action for these messages.

BKMVE201E No INIT function received.

Explanation:


User response:


BKMVE202E INIT function received without

intervening term

Explanation:


User response:


BKMVE203E Unknown function: xxxx

Explanation:


User response:


BKMVE204E Error calling BKM01VV1 xxxx R15=rc

R0=rea ID=nn

Explanation:


User response:


BKMVE205E MLA value found greater than 4

Explanation:


User response:


BKMVE206E Mask failed evaluation check: xxxx

Explanation:


User response:


BKMVE207E CSI failed when calling for master

catalog name

Explanation:


User response:


BKMVE208E Mask failed evaluation check: xxxx -

yyyyy

Explanation:

Mask xxxx is invalid for reason yyyyy.

User response:


BKMVE209E Un-allocation failed for: cccc

Explanation:

Un -allocation failed for catalog cccc.

User response:

Determine the reason for and fix the problem, retry the

function.

BKMVE210E Allocation failed for: cccc

Explanation:


User response:


BKMVE211E UCBLOOK error for: vvvv - return code:

rc reason code: rsn

Explanation:


User response:


BKMVE138E • BKMVE211E IBM Confidential



Devtype:ttt

Explanation:



nnn on device type ttt.

User response:



BKMVE213E IOSCAPU error for: vvvv - return code:

rc reason code: rsn

Explanation:


User response:


BKMVE214E VOLSER=vvvv

RC=rrr,REAS=sss,DESC=zzzz

Explanation:


volume vvvv for data set nnnn. rrr = Return code sss =

Reason code zzzz = Description when available.

User response:



BKMVE215E UCBPIN error for: vvvv - return code :rc

reason code: rsn

Explanation:


User response:


BKMVE216E CVAF error: return code: rc status

code: sc volume: vvvv ID=nn prev

func:ffff

Explanation:


User response:


BKMVE217E Error obtaining VTOC data from vvvv :

nnnn

Explanation:



User response:



BKMVE218E HSM MCVT not found

Explanation:



not been started.

User response:



BKMVE219E HSM data extract ended with errors

Explanation:



not been started.

User response:



BKMVE220E Migrated data set not found in MCDS:

nnnn

Explanation:



User response:



BKMVE221W No catalog entries found for mask(s)

Explanation:


passed to BKM01VE2.

User response:




BKMVE222E Associated entry not found in catalog -

nnnn

Explanation:




User response:



assistance.

BKMVE223E Unexpected catalog record construct -

association cell not where expected

Explanation:


BKMVE212E • BKMVE223EIBM Confidential


User response:



assistance.

BKMVE224E Type ″J″ record with no matching ″B″

record: nnnn

Explanation:



User response:



assistance.

BKMVE225E Error reading self describing record

from catalog: nnnn

Explanation:


User response:


BKMVE226E Received a ″GET″ request before

receiving a mask

Explanation:


User response:


BKMVE227E Input control block is not compatible

Explanation:


User response:


BKMVE229E HSM is not active - unable to retrieve

requested data

Explanation:


User response:


BKMVE230I Allocation failed for: nnnn - will not be

used for search

Explanation:



User response:



Devtype: ttt

Explanation:



nnn on device type ttt.

User response:



BKMVE232E No MCDS data set with valid key-range

found

Explanation:




data set name.

User response:


for this data set.

BKMVE233E No MCDS DSN(s) found in HSM

address space

Explanation:

An attempt was made to find the data set names of the

MCDS(s) allocated to HSM. The attempt failed.

User response:


for this data set.

BKMVE234W Error calling BKM01HSM RC=RC

Explanation:


User response:




BKMVE235E nnnn : VOLSER=vvvvvv - VVDS not

open

Explanation:

A previous OPEN failed for the VVDS on volume

vvvvvv.

User response:


for data set nnnn.

BKMVE236W Invalid DSN found :

xxxxxxxxxxxxxxxxxxx

Explanation:

BKMVE224E • BKMVE236W IBM Confidential



first BKMVE236W shows the data set name in character

format. The next three BKMVE236W show the name in

hex.

User response:


BKMVE237W Open failed for: nnnn - will not be

used for search

Explanation:

Unable to open catalog nnnn. No entries that may


User response:


BKMVE238E Cluster not found for truename in

catalog -

Explanation:



cluster entry.

User response:



BKMVE239I Retrying error obtaining ??????? For

dsn - ucat

Explanation:






User response:


errors BKMVE217E, BKMCA120E, BKMCA114E,

BKMCA220E, or BKMCA214E occur. See action for

these messages.

BKMVSE00E VSAM failure,ddname: ddname VSAM

DSN: data set name or no DD allocation

found

Explanation:

A VSAM failure occurred attempting to OPEN, access,

or CLOSE a VSAM data set used by a product via

product’s common VSAM I/O routine (BKM01VSI).

User response:

See additional messages. Although many errors could

be caused by internal errors, look for any messages

with ** USER CORRECTABLE **. These could include

problems such as insufficient region size, unable to

allocate extents, and so on.

Some errors could be the result of incorrectly defining a

data set. Compare values returned for catalog LRECL,

key length, and key offset to the specifications for the

data set as documented in the appropriate product

manual. LRECL and KEYLEN to be compared are those

supplied with messages BKMVSE21 and BKMVSE22,

not BKMVSE19 and BKMVSE20. If the error does not

appear to be user correctable, please include all

BKMVSEnn messages in documentation supplied to

Technical Support. Also supply the output from a

LISTCAT ENT(...) ALL for the failing data set.

BKMVSE01E Failing BKM01VSI function: nnn and

previous BKM01VSI function: nnn

Explanation:

Last and previous (if any) VSAM function performed.

User response:

This message is provided for debugging purposes.

However, other messages could indicate a user

correctable situation. Note that this is the last logical

request made by a product program. Because of implicit

OPENs and CLOSEs, see message BKMVSE13E to

determine the exact VSAM function last requested when

determining which set of documented return or reason

codes apply.

BKMVSE03E Program CSECT: csect name

Explanation:

CSECT name of failing program.

User response:

This message provided for debugging purposes.


correctable situation.

BKMVSE04E VWHEN error ID: id

Explanation:

Internally assigned ID of last VSAM I/O call.

User response:




BKMVSE05E VWHEN ASM listing line #: line

number

Explanation:

Source listing line number of last VSAM I/O call.

User response:




BKMVE237W • BKMVSE05EIBM Confidential


BKMVSE06E Message associated with BKM01VSI

register 15 value

Explanation:

Message associated with a non-VSAM error - that is, a

non-zero return code from BKM01VSI or a VSAM

OPEN, ACCESS, or CLOSE.

User response:

This message is provided for debugging purposes.


correctable situation. If last function is OPEN, and return

code is 16: RLS not available - no SMSVSAM server

this may be user correctable if the product parmlib

ABRINI member specified RLS for the data set and in

fact RLS is not supported on the image.

BKMVSE07E Message associated with VSAM

register 15 value

Explanation:

Message associated with VSAM register 15 value.

User response:

See message BKMVSE10 and BKMVSE11 for VSAM

reason code and description. If BKMVSE12 is produced

instead of BKMVSE11, see the manual for a description

of the reason code.

BKMVSE08E SVC99 error code: code

Explanation:

Error code from SVC99 - dynamic allocation.

User response:

Use this error code in conjunction with the SVC99

information code (BKMVSE09E) to determine the cause

of failure.

BKMVSE09E SVC99 information code: code

Explanation:

Error code from SVC99 - dynamic allocation.

User response:

Use this error code in conjunction with the SVC99

information code (BKMVSE08E) to determine the cause

of failure.

BKMVSE10E VSAM reason code: code

Explanation:

Reason code returned from VSAM OPEN, ACCESS or

CLOSE.

User response:

Use this error code in conjunction with the description

provided by message BKMVSE11E to determine the

cause of the failure. See additional comments for

BKMVSE11E.

BKMVSE11E VSAM reason code description

Explanation:

Abbreviated description for selected VSAM reason

codes.

User response:

The error handling module producing BKMVSEnn

messages includes many VSAM reason code

descriptions. Note that these messages are abbreviated

in comparison to the messages documented. For this

reason, users should also refer to the documentation for

the reason code displayed with message BKMVSE10.

Because documented reason codes are distinguished

by OPEN/CLOSE versus ACCESS, see message

BKMVSE13E for the last ACCESS attempted.

BKMVSE13E will indicate OP for OPEN, and CL for

CLOSE. Consider any other value as ACCESS. Note

especially any reason code descriptions with the string

** USER CORRECTABLE as these may be situations

correctable without support.

BKMVSE12E No description for reason code

Explanation:

Description for reason code not included in error

handling table.

User response:

Refer to the description of the reason code

(BKMVSE10E) for the last function requested

(BKMVSE13E) in the documentation.

BKMVSE13E VSAM ccode: code

Explanation:

This is a product value indicating the last VSAM request

issued.

User response:

This value is necessary if looking up the return and

reason codes in documentation. CCODE will be OP for

an OPEN and CL for a CLOSE. Consider any other

value as ACCESS.

BKMVSE14E BKM01VSI implicit open

Explanation:

Indicator that last program request required the data set

be re-opened.

User response:

Primarily for product debugging.

BKMVSE15E BKM01VSI implicit close

Explanation:

Indicator that a CLOSE was the result of one task losing

control to another.

User response:


BKMVSE06E • BKMVSE15E IBM Confidential


BKMVSE16E BKM01VSI implicit reposition

Explanation:

Indicator that the positioning had to be re-established as

a result of losing control to another task.

User response:


BKMVSE17E OPEN classification: value

Explanation:

Product internal value indicating intended use of the

data set.

User response:


BKMVSE18E Buffering technique: value

Explanation:

Product internal value indicating selected buffering

technique.

User response:


BKMVSE19E BKM01VSI parm LRECL: lrecl

Explanation:

Last LRECL set in BKM01VSI parm field.

User response:


BKMVSE20E BKM01VSI parm KEYLEN: key length

Explanation:

Last key length set in BKM01VSI parm field.

User response:


BKMVSE21E BKM01VSI catalog lrecl: lrecl

Explanation:

Max LRECL fetched from catalog at OPEN time.

User response:

This should be used to verify that the cluster as defined

matches the requirements for the data set as defined in

the product documentation.

BKMVSE22E BKM01VSI catalog keylen: key length

Explanation:

Key length fetched from catalog at OPEN time.

User response:




BKMVSE23E BKM01VSI catalog key offset: key

offset

Explanation:

Key offset fetched from catalog at OPEN time.

User response:




BKMVV136E INVALID LRECL: value

Explanation:

LRECL must be a positive integer.

User response:

Correct the LRECL value.

BKMVV137E Dataspace defined over 2 GB

Explanation:

Dataspaces are limited to 2 GB or 2097152 K. The

corresponding SI027_VALUES in INI are specified in K,

so the limit is 2097152.

User response:

Correct the SI027_Values section of INI.

BKMVV138E Error creating dataspace RC=xx reason

yyyyyyyy

Explanation:

BKM01VV1 attempted to create a dataspace. The error

indicates that the parameters were incorrect.

User response:


BKMVV139E Error extending dataspace RC=xx

reason yyyyyyyy

Explanation:

BKM01VV1 attempted to expand a dataspace. The error

indicates that the parameters were incorrect.

User response:


BKMVV140E Bad token: INITIAL_SIZE

Explanation:

Value specified is larger than the value allowed

(2097152).

User response:

Correct the INITIAL_SIZE value in INI.

BKMVSE16E • BKMVV140EIBM Confidential


BKMVV141E Bad token: MAXIMUM_SIZE

Explanation:


(2097152).

User response:

Correct the MAXIMUM_SIZE value in INI.

BKMVV142E Bad token:

MAXIMUM_DATASPACE_SIZE

Explanation:


(2097152).

User response:

Correct the MAXIMUM_DATASPACE_SIZE value in INI.

BKMVV141E • BKMVV142E IBM Confidential


Support information

If you have a problem with your IBM software, you want to resolve it quickly. This

section describes the following options for obtaining support for IBM software

products:

v “Using IBM Support Assistant”

v “Obtaining fixes”

v “Contacting IBM Software Support” on page 262

Using IBM Support Assistant

The IBM Support Assistant is a free, stand-alone application that you can install on

any workstation. You can then enhance the application by installing product-specific

plug-in modules for the IBM products you use.

The IBM Support Assistant saves you time searching product, support, and

educational resources. The IBM Support Assistant helps you gather support

information when you need to open a problem management record (PMR) or

Electronic Tracking Record (ETR), which you can then use to track the problem.

Tip

The Log and Trace Analyzer tool can help you prepare logs to submit with a

PMR.

The product-specific plug-in modules of the IBM Support Assistant provide you with

the following resources:

v Support links

v Education links

v Ability to submit problem management reports

For more information and to download the IBM Support Assistant, see

http://www.ibm.com/software/support/isa/.

Obtaining fixes

A product fix might be available to resolve your problem. To determine which fixes

are available for your Tivoli software product, follow these steps:

1. Go to the IBM Software Support Web site at http://www.ibm.com/software/support.

2. Under Select a brand and/or product, select Tivoli.

3. Under Select a product, select a product and click Go.

4. Under Download, click the name of a fix to read its description and, optionally,

to download it.

If there is no Download heading for your product, supply a search term, error

code, or APAR number in the field provided under Search Support (this

product), and click Search.

For more information about the types of fixes that are available, see the IBM

Software Support Handbook at http://techsupport.services.ibm.com/guides/handbook.html.

IBM Confidential

261

http://www-306.ibm.com/software/support/isa

http://www.ibm.com/software/support

http://www.ibm.com/software/support

http://techsupport.services.ibm.com/guides/handbook.html

http://techsupport.services.ibm.com/guides/handbook.html

Contacting IBM Software Support

IBM Software Support provides assistance with product defects. The easiest way to

obtain that assistance is to open a PMR or ETR directly from the IBM Support

Assistant (see “Using IBM Support Assistant” on page 261), and attach the logs you

prepare with the help of the Log and Trace Analyzer Tool.

Before contacting IBM Software Support, your company must have an active IBM

software maintenance contract, and you must be authorized to submit problems to

IBM. The type of software maintenance contract that you need depends on the type

of product you have:

v For IBM distributed software products (including, but not limited to, Tivoli, Lotus®,

and Rational® products, as well as DB2® and WebSphere® products that run on

Windows, or UNIX® operating systems), enroll in Passport Advantage® in one of

the following ways:

Online

Go to the Passport Advantage Web site at http://www-306.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm and click How

to Enroll.

By phone

For the phone number to call in your country, go to the IBM Software

Support Web site at http://techsupport.services.ibm.com/guides/contacts.html and click the name of your geographic region.

v For customers with Subscription and Support (S & S) contracts, go to the

Software Service Request Web site at https://techsupport.services.ibm.com/ssr/login.

v For customers with IBMLink™, CATIA, Linux®, S/390®, iSeries®, pSeries®,

zSeries, and other support agreements, go to the IBM Support Line Web site at

http://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006.

v For IBM eServer™ software products (including, but not limited to, DB2 and

WebSphere products that run in zSeries, pSeries, and iSeries environments), you

can purchase a software maintenance agreement by working directly with an IBM

sales representative or an IBM Business Partner. For more information about

support for eServer software products, go to the IBM Technical Support

Advantage Web site at http://www.ibm.com/servers/eserver/techsupport.html.

If you are not sure what type of software maintenance contract you need, call

1-800-IBMSERV (1-800-426-7378) in the United States. From other countries, go to

the contacts page of the IBM Software Support Handbook on the Web at

http://techsupport.services.ibm.com/guides/contacts.html and click the name of your

geographic region for phone numbers of people who provide support for your

location.

IBM Confidential


http://www-306.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm

http://www-306.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm

http://techsupport.services.ibm.com/guides/contacts.html


https://techsupport.services.ibm.com/ssr/login

https://techsupport.services.ibm.com/ssr/login

http://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006

http://www.ibm.com/servers/eserver/techsupport.html


If you prefer to contact IBM Software support without the help of the IBM Support

Assistant, complete the following steps:

1. “Determining the business impact”

2. “Describing problems and gathering information”

3. “Submitting problems”

Determining the business impact

When you report a problem to IBM, you are asked to supply a severity level.

Therefore, you need to understand and assess the business impact of the problem

that you are reporting. Use the following criteria:

Severity 1

The problem has a critical business impact. You are unable to use the

program, resulting in a critical impact on operations. This condition requires

an immediate solution.

Severity 2

The problem has a significant business impact. The program is usable, but

it is severely limited.

Severity 3

The problem has some business impact. The program is usable, but less

significant features (not critical to operations) are unavailable.

Severity 4

The problem has minimal business impact. The problem causes little impact

on operations, or a reasonable circumvention to the problem was

implemented.

Describing problems and gathering information

When describing a problem to IBM, be as specific as possible. Include all relevant

background information so that IBM Software Support specialists can help you

solve the problem efficiently. To save time, know the answers to these questions:

v What software versions were you running when the problem occurred?

v Do you have logs, traces, and messages that are related to the problem

symptoms? IBM Software Support is likely to ask for this information.

v Can you re-create the problem? If so, what steps were performed to re-create

the problem?

v Did you make any changes to the system? For example, did you make changes

to the hardware, operating system, networking software, and so on.

v Are you currently using a workaround for the problem? If so, be prepared to

explain the workaround when you report the problem.

Submitting problems

You can submit your problem to IBM Software Support in one of two ways:

Online

Click Submit and track problems on the IBM Software Support site at

http://www.ibm.com/software/support/probsub.html. Type your information

into the appropriate problem submission form.

By phone

For the phone number to call in your country, go to the contacts page of the

IBM Software Support Handbook at http://techsupport.services.ibm.com/guides/contacts.html and click the name of your geographic region.

IBM Confidential

Support information 263

http://www.ibm.com/software/support/probsub.html



If the problem you submit is for a software defect or for missing or inaccurate

documentation, IBM Software Support creates an Authorized Program Analysis

Report (APAR). The APAR describes the problem in detail. Whenever possible, IBM

Software Support provides a workaround that you can implement until the APAR is

resolved and a fix is delivered. IBM publishes resolved APARs on the Software

Support Web site daily, so that other users who experience the same problem can

benefit from the same resolution.

IBM Confidential


Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in

other countries. Consult your local IBM representative for information on the

products and services currently available in your area. Any reference to an IBM

product, program, or service is not intended to state or imply that only that IBM

product, program, or service may be used. Any functionally equivalent product,

program, or service that does not infringe any IBM intellectual property right may be

used instead. However, it is the user’s responsibility to evaluate and verify the

operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter

described in this document. The furnishing of this document does not give you any

license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk, NY 10504-1785

U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM

Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation Licensing

2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other country

where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS

MACHINES CORPORATION PROVIDES THIS PUBLICATION ″AS IS″ WITHOUT

WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT

NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,

MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states

do not allow disclaimer of express or implied warranties in certain transactions,

therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes be

incorporated in new editions of the publication. IBM may make improvements and/or

changes in the product(s) and/or the program(s) described in this publication at any

time without notice.

Any references in this information to non-IBM Web sites are provided for

convenience only and do not in any manner serve as an endorsement of those

Web sites. The materials at those Web sites are not part of the materials for this

IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes

appropriate without incurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those

products, their published announcements or other publicly available sources. IBM

has not tested those products and cannot confirm the accuracy of performance,

IBM Confidential

265

compatibility or any other claims related to non-IBM products. Questions on the

capabilities of non-IBM products should be addressed to the suppliers of those

products.

Trademarks

IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of

International Business Machines Corporation in the United States, other countries,

or both. These and other IBM trademarked terms are marked on their first

occurrence in this information with the appropriate symbol (® or

™), indicating US

registered or common law trademarks owned by IBM at the time this information

was published. Such trademarks may also be registered or common law trademarks

in other countries. A complete and current list of IBM trademarks is available on the

Web at http://www.ibm.com/legal/copytrade.shtml.

Adobe and all Adobe-based trademarks are either registered trademarks or

trademarks of Adobe Systems Incorporated in the United States, other countries, or

both.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation

in the Unites States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other

countries.

Other company, product, and service names may be trademarks or service marks

of others.

IBM Confidential


http://www.ibm.com/legal/copytrade.shtml

Index

AAdvanced Backup and Recovery for z/OS

audience, intended v

Bbooks

see publications v

Cconventions

abbreviations vii

typeface vii

customer supportSee Software Support

Eeducation 261

see Tivoli technical training vi

Ffix packs 261

Gglossary, accessing online vi

IIBM Redbooks 261

IBM Support Assistant 261

Mmanuals

see publications v

messagesoverview 1

Nnotices 265

Oonline publications v

Pprerequisites

experience v

knowledge v

problem determinationdescribing problems 263

determining business impact 263

submitting problems 263

problem resolution 261

publications v

accessing online v

ordering vi

RRedbooks, IBM 261

SSoftware Support 261

contacting 262

describing problems 263

determining business impact 263

submitting problems 263

support 261

support assistant 261

Tterminology vi

Tivoli Software Information Center v

Tivoli technical training vi

training, Tivoli technical vi

typeface conventions vii

IBM Confidential

267

IBM Confidential


��

Program Number: 5698–B17

IBM Confidential

Printed in USA

GC23-9731-00

ibm tivoli advanced backup and recovery for z/os:...

Documents