BrightStor CA-Dynam for VSE Message Guide

BrightStorCA-Dynam for VSE

Message Guide 7.0 SP3

D00014-1E

This documentation and related computer software program (hereinafter referred to as the “Documentation”) is for the end user’s informational purposes only and is subject to change or withdrawal by Computer Associates International, Inc. (“CA”) at any time.

This documentation may not be copied, transferred, reproduced, disclosed or duplicated, in whole or in part, without the prior written consent of CA. This documentation is proprietary information of CA and protected by the copyright laws of the United States and international treaties.

Notwithstanding the foregoing, licensed users may print a reasonable number of copies of this documentation for their own internal use, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the confidentiality provisions of the license for the software are permitted to have access to such copies.

This right to print copies is limited to the period during which the license for the product remains in full force and effect. Should the license terminate for any reason, it shall be the user’s responsibility to return to CA the reproduced copies or to certify to CA that same have been destroyed.

To the extent permitted by applicable law, CA provides this documentation “as is” without warranty of any kind, including without limitation, any implied warranties of merchantability, fitness for a particular purpose or noninfringement. In no event will CA be liable to the end user or any third party for any loss or damage, direct or indirect, from the use of this documentation, including without limitation, lost profits, business interruption, goodwill, or lost data, even if CA is expressly advised of such loss or damage.

The use of any product referenced in this documentation and this documentation is governed by the end user’s applicable license agreement.

The manufacturer of this documentation is Computer Associates International, Inc.

Provided with “Restricted Rights” as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-19(c)(1) and (2) or DFARS Section 252.227-7013(c)(1)(ii) or applicable successor provisions.

2003 Computer Associates International, Inc.

All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Contents

Chapter 1: Introduction Message Code Suffixes ........................................................................ 1-1 Return Codes from Batch Utilities .............................................................. 1-2 Related Publications .......................................................................... 1-2 IBM Publications ............................................................................. 1-3

Chapter 2: Messages CADA Prefixed Messages ..................................................................... 2-1 CADC Prefixed Messages .................................................................... 2-31 CADD Prefixed Messages ................................................................... 2-128 CADE Prefixed Messages.................................................................... 2-183 CADF Prefixed Messages.................................................................... 2-220 CADT Prefixed Messages.................................................................... 2-236 CADU Prefixed Messages ................................................................... 2-346 CADV Prefixed Messages ................................................................... 2-368 CASP Prefixed Messages .................................................................... 2-390 CATA Prefixed Messages.................................................................... 2-406

Chapter 3: Return Codes CAD Return Codes ........................................................................... 3-1

VTOC Return Codes ...................................................................... 3-1 CA-Dynam/T Return Codes ................................................................... 3-3 Catalog Management Return Codes ............................................................ 3-5 CICS Abend Codes .......................................................................... 3-10 IUCV Function Codes ........................................................................ 3-11 Task Manager Return Codes .................................................................. 3-11

Contents iii

Event Codes ................................................................................. 3-12 CA-Dynam/D Event Codes ............................................................... 3-12 CA-Dynam/FI Event Codes ............................................................... 3-12 CA-Dynam/T Event Codes................................................................ 3-13

iv CA-Dynam Message Guide

Chapter

1 Introduction

This guide explains the error messages, abend codes, and return codes for all BrightStor CA-Dynam for VSE products: CA-Dynam/D, CA-Dynam/FI and CA-Dynam/T.

Message Code Suffixes The messages are listed by alphabetically by prefix and then numerically by message number. Each message has a one-letter suffix giving you additional information:

The Suffix Means

A You must perform a specific action before continuing.

D You must make a decision before continuing. (You must reply to this message.)

E An error has occurred.

I This message is for information only.

P The currently running task has stopped. An operator command is required.

S An error has occurred. A return code is set.

T An error has occurred. The task is terminated.

W Warning message. Something has gone wrong, but it is not serious enough to stop processing.

Introduction 1–1

Return Codes from Batch Utilities

Return Codes from Batch Utilities For installations using VSE Version 2 or higher, all batch utilities supplied with CA-Dynam pass a return code to the operating system when processing is complete (EOJ). The return code reflects the most serious message to have been issued while a particular utility was running.

The following table lists the return code associated with each of the one-letter message code suffixes described earlier:

For Code The return code passed is

A N/A

D N/A

E 8

I 0

P N/A

S 12

T 16

W 4

Note: N/A means not applicable. A return code based on this message has no meaning.

Related Publications The following publications relate to CA-Dynam VSE and are available from Computer Associates:

Name Operating System

CA-Dynam/T DYNVM Extension Administrator Guide

VSE

CA-Dynam/T DYNVM Extension Operator Guide VSE

CA-Dynam/T DYNVM Extension Systems Programmer Guide

VSE

CA-EARL Reference Guide VSE

CA-CIS documentation set VSE

1–2 CA-Dynam Message Guide

IBM Publications

Introduction 1–3

IBM Publications Reference the following IBM publications for definitions of terminology and background on the basic IBM VSE system conventions required to use CA-Dynam:

■ VSE/AF, System Control Statements

■ VSE/AF, Maintain System History Program Reference

■ VSE/AF, System Management Guide

■ VSE/AF, Data Management Concepts

■ VSE/AF, Application Programming: Macro Reference

■ Device Support Facilities, User's Guide And Reference

■ VSE/ESA Macro User Guide

■ VSE/ESA Administration Guide

■ VSE/ESA Data Management Concepts

■ VSE/ESA Guide to System Functions

■ VSE/ESA Messages and Codes

■ VSE/ESA Operators Guide

■ VSE/ESA System Control Statements

■ VSE/ESA System Macro Reference

■ VSE/ESA System Macro Users Guide

■ VSE/VSAM Programmer's Reference

■ Using VSE/VSAM Commands and Macros

Chapter

2 Messages

CADA Prefixed Messages

CADA000E — ERROR IN AUDTUTIL COMMAND. MESSAGE NUMBER IS nnnn.

Reason:

The utility program command parser has found an error in the command being processed.

Action:

Correct the error in the command and resubmit.

CADA100E — ERROR HAS OCCURRED RTC=nn FC=nn

Reason:

An unexpected return code has been issued by the Catalog Management component. The function code and return codes are Catalog Management codes, and indicate a problem in access of the catalog or audit files.

Action:

Inspect the return code for 'normal' conditions such as insufficient storage. If the problem does not appear to be of this nature, document the problem and contact Computer Associates. See "Catalog Management Return Codes" for more information.

CADA101E — INVALID AUDIT TRAIL FILE FORMAT. PLEASE INITIALIZE.

Reason:

The audit trail file must be initialized before it can be processed, or else the system cannot access the audit trail file.

Messages 2–1


Action:

Execute the AUDTUTIL program with the DATASET INITIALIZE function to initialize the audit file. Also see message CADA114.

CADA102I — AUDIT TRAIL FILE IS nn PERCENT FULL

Reason:

This message is issued when the file becomes 10, 20, 30, and 40% full.

Action:

No action required.

CADA103W — AUDIT TRAIL FILE IS nn PERCENT FULL. PLEASE BACKUP.

Reason:

This message is issued when the file becomes 50, 60, 70, 80, and 90% full.

Action:

Execute the AUDTUTIL program with the BACKUP function to save the contents of the audit file onto tape; the file will be cleared automatically.

CADA104E — AUDIT TRAIL DATASET ON LAST CONTROL INTERVAL. RUN BACKUP IMMEDIATELY.

Reason:

Audit trail logging will cease when this track becomes full.

Action:

Execute the AUDTUTIL program with the BACKUP function immediately. (See message CADA103W.)



CADA105W — AUDIT TRAIL FILE IS FULL. LOGGING STOPPED.

Reason:

All audit trail logging has stopped.

Action:

Execute the AUDTUTIL program with the BACKUP function immediately. (See message CADA104E.)

CADA106I — AUDTUTIL WILL BE CANCELED DUE TO 'E' LEVEL ERROR

Reason:

An AUDTUTIL command terminated with an 'E' level diagnostic error.

Action:

Correct the error in the command and resubmit.

CADA107I — AUDTUTIL WILL BE CANCELED DUE TO OPERATOR REQUEST

Reason:

Operator entered 'CANCEL' as reply to an AUDTUTIL message.

Action:

No action required.

CADA108D — ENTER AUDTUTIL COMMAND

Reason:

The utility program has been executed from the console and is ready to read command statements from there.

Action:

Enter the utility program command statement.

Messages 2–3


CADA110I — AUDIT TRAIL PROCESSING IS COMPLETE

Reason:

The AUDTUTIL program has completed its processing.

Action:

No action required.

CADA111E — ERRORS HAVE BEEN FOUND DURING AUDIT TRAIL PROCESSING

Reason:

Errors were encountered during the execution of the AUDTUTIL program.

Action:

Correct errors found and resubmit job.

CADA112E — FUNCTION SUPPRESSED DUE TO ERRORS ON PREVIOUS CONTROL CARDS

Reason:

The current function has been suppressed due to error(s) encountered on previous command statements. The audit utility stops processing when an error occurs, and then flushes the remainder of the IJSYSIN file.

Action:

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

CADA113E — INSUFFICIENT STORAGE FOR AUDIT TRAIL UTILITY EXECUTION

Reason:

The AUDTUTIL utility program requires a size of approximately 100K.

Action:

Increase the partition size.



CADA114E — INVALID OR MISSING LABEL INFORMATION FOR THE AUDIT TRAIL DATA SET

Reason:

The label for the audit trail file (CAIAUDT) is either

■ not defined in the system standard, partition standard or user label area, or

■ not assigned correctly.

Action:

Assign the logical unit on the EXTENT statement to the disk volume on which the audit trail file resides.

CADA115E — DISK ERROR OCCURRED WHILE READING AUDIT TRAIL DATA SET RC=nnnn CSW=nnnn

Reason:

The audit trail file wasn't initialized. It cannot be processed.

Action:

Use the DATASET INITIALIZE function of the AUDTUTIL program. See "Catalog Management Return Codes" for more information.

CADA116W — AUDIT TRAIL FILE IS EMPTY

Reason:

You are attempting to generate a report from an empty audit trail file.

Action:

Wait until audit information is logged before generating an audit report.

CADA117E — INVALID TAPE LOGICAL UNIT - xxxxxx

Reason:

The logical unit defined for the tape to be processed by AUDTUTIL is invalid.

Action:

Correct the condition and resubmit the job.

Messages 2–5


CADA118E — INVALID TAPE FORMAT - BAD TAPE RECORDS FOUND

Reason:

The AUDTUTIL program found invalid tape records while attempting to read the tape created by the BACKUP command.

Action:

Ensure that the correct input tape file is being processed.

CADA119I — AUDIT TRAIL DATASET IS BEING LOCKED

Reason:

The user has 'locked' the audit trail file. (See the DATASET and BACKUP commands of AUDTUTIL.)

Action:

No action required.

CADA120I — AUDIT TRAIL DATASET LOCK HAS BEEN RELEASED

Reason:

The 'lock' on the audit file has been released. (See message CADA119I).

Action:

No action required.

CADA121I — AUDIT LOGGING IS BEING STOPPED

Reason:

Audit recording has been stopped.

Action:

No action required. Informational.



CADA122I — AUDIT LOGGING HAS BEEN RESTARTED

Reason:

If audit logging was stopped because the audit data set was filling up, the BACKUP function restarts audit trail logging.

Action:

No action required.

CADA123E — REPORT COMMAND NOT GIVEN - INVALID COMMAND SEQUENCE

Reason:

A SELECT, INPUT, TITLE, or GENERATE command was given without a prior REPORT command.

Action:

Insert a REPORT command and resubmit.

CADA124E — FUNCTION NOT SUPPORTED FOR THIS PACKAGE

Reason:

The function requested in the utility command is not supported for the systems currently installed.

Action:

Review the documentation for the products currently installed and active in this system. Correct the command, and resubmit.

CADA125E — ERROR WHILE READING AUDIT TRAIL DATA SET - RC=nnnn

Reason:

An error has occurred while reading the audit trail data set. The most likely cause is either an I/O error, or the overwriting of the audit data set by another file.

Messages 2–7


Action:

Determine the cause of the error by looking at the VTOC listings and EREP reports for the DASD volume. If the cause of the error cannot be determined, contact Computer Associates for assistance. See "Catalog Management Return Codes" for more information.

CADA126I — AUDIT TRAIL DATA SET 'UNCONDITIONALLY' RELEASED

Reason:

The data set UNLOCK function has been used to force the dequeue of the audit data set.

Action:


CADA127E — PHASE 'xxxxxxxx' NOT FOUND

Reason:

The audit trail utility has attempted to load the named phase but it was not found in the core image library.

Action:

Review the CA-Dynam installation LNKEDT SYSLST output to assure that no errors occurred. If necessary, reinstall the product beginning with the original distribution tape.

CADA128E — ERROR OCCURRED WRITING RECORD TO HISTORY TAPE - RC=nnnn

Reason:

An I/O error occurred while writing a record to the backup tape.

Action:

Rerun the backup using another tape volume and/or tape drive. See "Catalog Management Return Codes" for more information.



CADA129E — NO CA-DYNAM PRODUCTS INSTALLED, CANNOT CONTINUE

Reason:

The audit component requires at least one CA-Dynam product to be installed in order to function.

Action:

Review documentation for the products which should be installed and determine why they are not.

CADA130E — ERROR OCCURRED WHILE RELEASING THE AUDIT TRAIL DATA SET

Reason:

An I/O error occurred while the enqueue/dequeue record for the audit data set was being dequeued.

Action:

The audit data set must be unlocked and reinitialized.

CADA131E — ERROR OCCURRED WHILE OPENING THE AUDIT TRAIL HISTORY TAPE FOR xxxxxxxx -- RC=nnnn

Reason:

An error was encountered while the audit history tape was being opened. It could have been an I/O or a logical open error.

Action:

Verify the assignment, label and command parameters for the audit history tape data set. If the error persists, use another tape and/or tape drive. See "Catalog Management Return Codes" for more information.

CADA132E — ERROR OCCURRED WHILE CLOSING THE AUDIT TRAIL HISTORY TAPE FOR 'xxxxxxxx' -- RC=nnnn

Reason:

An error was encountered while the audit history tape was being closed. It could have been an I/O or a logical close error.

Messages 2–9


Action:

Verify the assignment, label and command parameters for the audit history tape data set. If the error persists, use another tape and/or tape drive. See "Catalog Management Return Codes" for more information.

CADA133E — ERROR OCCURRED WHILE READING THE AUDIT TRAIL HISTORY TAPE RC=nnnn

Reason:

An I/O error occurred while reading the audit trail history tape.

Action:

Clean the tape and drive and try again. If the problem persists, the tape may be irrecoverably damaged. See "Catalog Management Return Codes" for more information.

CADA150E — UNEXPECTED END OF DATA ON INPUT FILE. (CONTINUATION CARD EXPECTED)

Reason:

The AUDTUTIL program expected to encounter a continuation statement and instead encountered an end-of-file condition.

Action:

Recheck the commands submitted to the AUDTUTIL program and ensure all required commands and operands are supplied.

CADA151E — TOO MANY CONTINUATION STATEMENTS

Reason:

A maximum of seven (7) continuation statements are allowed by AUDTUTIL.

Action:

Correct and resubmit.



CADA152E — UNRECOGNIZABLE COMMAND

Reason:

AUDTUTIL found an invalid command.

Action:

See the AUDTUTIL command descriptions in the User Guide.

CADA153E — REQUIRED OPERAND(S) OMITTED

Reason:

A required operand has been omitted for the command being processed.

Action:

See the specific command description in the User Guide.

CADA154E — INVALID KEYWORD OPERAND

Reason:

There is an invalid keyword specified for the command being processed.

Action:


CADA155E — UNRECOGNIZABLE KEYWORD OPERAND

Reason:

There is an unrecognizable keyword operand.

Action:

Correct the command error and resubmit.

Messages 2–11


CADA156E — TOO MANY POSITIONAL OPERANDS

Reason:

There are too many operands on the command being processed.

Action:


CADA157E — TOO MANY REPEATS OF KEYWORD OPERAND

Reason:

There are too many repeats of a keyword operand.

Action:


CADA158E — TOO MANY SUBOPERANDS

Reason:

Too many suboperands were supplied in a list enclosed in parentheses.

Action:


CADA159E — SYNTAX ERROR - UNPAIRED PARENTHESES

Reason:

A parenthesis is missing for the command processed.

Action:




CADA160E — SYNTAX ERROR - UNPAIRED APOSTROPHES

Reason:

An apostrophe is missing for the command processed.

Action:


CADA161E — SYNTAX ERROR - INVALID SEPARATOR

Reason:

There is an invalid separator for the command processed. (Blanks must be used.)

Action:


CADA162E — INVALID NUMERIC VALUE

Reason:

AUDTUTIL did not find a numeric value for the operand processed.

Action:


CADA163E — VALUE TOO LONG - TRUNCATED

Reason:

A supplied character string or keyword is too long and has been truncated.

Action:


Messages 2–13


CADA164E — VALUE IS TOO LONG

Reason:

A supplied character string or keyword is too long. Truncation is not performed.

Action:


CADA165E — INVALID OR UNRECOGNIZABLE VALUE

Reason:

A supplied keyword is not valid.

Action:


CADA166E — STRING MUST BE IN APOSTROPHES

Reason:

The string is not enclosed in apostrophes, but should be.

Action:


CADA167E — STRING MUST NOT BE IN APOSTROPHES

Reason:

The string is in apostrophes, but should not be.

Action:




CADA200I — AUDIT TRAIL INITIALIZATION HAS BEGUN

Reason:

The DATASET INITIALIZE function of AUDTUTIL has started.

Action:

No action required.

CADA201I — AUDIT TRAIL DATA SET INITIALIZATION SUCCESSFULLY COMPLETED

Reason:

Information can now be logged to the data set.

Action:

No action required.

CADA202E — DISK FORMAT ERROR FOUND DURING DATA SET INITIALIZATION. (DISK MAY NOT BE PROPERLY INITIALIZED)

Reason:

Unrecoverable disk I/O errors have occurred during data set initialization.

Action:

Check for hardware DASD problems.

CADA203E — AUDIT TRAIL DATA SET INITIALIZATION TERMINATED DUE TO ERRORS

Reason:

The DATASET INITIALIZE command has failed. The exact nature of the error encountered will have been indicated in a previous error message.

Action:


Messages 2–15


CADA204I — AUDIT TRAIL DATA SET STATUS REPORT FOLLOWS

Reason:

The DATASET function has been executed.

Action:

No action required.

CADA205I — AUDIT TRAIL DATA SET STATUS ALTERATION BEGINNING

Reason:

The DATASET LOCK or UNLOCK function of AUDTUTIL has been started.

Action:

No action required.

CADA206I — AUDIT TRAIL DATA SET STATUS ALTERATION IS COMPLETE.

Reason:

The DATASET LOCK or UNLOCK function of AUDTUTIL has completed successfully.

Action:

No action required.

CADA207W — DISK FORMAT ERROR FOUND DURING DATA SET STATUS ALTERATION. (DISK MAY NOT BE PROPERLY INITIALIZED)

Reason:

An unexpected disk error has occurred. The disk may not be properly initialized.

Action:

Verify formatting of the disk area on which the data set lies.



CADA208E — DATA SET PROCESSING TERMINATED DUE TO ERRORS

Reason:

The DATASET LOCK or UNLOCK function was terminated due to an error. The exact nature of the error condition will have been indicated in a previous error message.

Action:

Correct and resubmit immediately. Audit trail support will cause jobs to be placed in a controlled loop until the data set is unlocked.

CADA209E — AUDIT TRAIL DATA SET 'DEQUEUE' ERROR - RC=nnnn

Reason:

An internal error has been encountered in processing the audit trail data set.

Action:

Collect documentation and contact Computer Associates for assistance. See "Catalog Management Return Codes" for more information.

CADA300E — GENERATE COMMAND NOT GIVEN

Reason:

AUDTUTIL did not find a GENERATE command. This command is required in order to generate a report.

Action:

Insert GENERATE command into the job stream.

CADA301W — NO FIELDS COMMAND(S) GIVEN

Reason:

AUDTUTIL found no FIELDS command(s) and a user-defined report was specified.

Action:

Insert necessary FIELDS command into the job stream.

Messages 2–17


CADA302W — NO RECORDS SELECTED FOR PROCESSING

Reason:

AUDTUTIL found no records to be selected for the specified REPORT function.

Action:

No action required.

CADA303E — REPORT NAME 'xxxxxxxx' IS UNDEFINED

Reason:

The report specified is not a valid predefined report.

Action:

Specify a valid report name or provide user-defined report specifications.

CADA304E — FIELD NAME 'xxxxxxxx' IS UNDEFINED

Reason:

Either the specified field name is not valid, or a syntax error has occurred in the FIELDS statement.

Action:


CADA305E — RECORD CLASS 'xxxxxxxx' IS UNDEFINED

Reason:

The specified record-selection class, specified on the SELECT command, is invalid.

Action:




CADA306W — REPORT LINES ARE TOO LONG - TRUNCATING

Reason:

Fields specified using the FIELDS command overflow print column 121.

Action:

No action required. The report is truncated at column 121.

CADA307W — TOO MANY REPORT TITLE LINES DEFINED

Reason:

A maximum of seven (7) titles (both page and field) may be defined.

Action:

No action required. Extra title lines are ignored.

CADA308W — TITLE LINES ARE TOO LONG - TRUNCATING

Reason:

Title lines exceed 121 characters.

Action:

No action required. The execution continues, but lines are truncated.

CADA309W — TITLE LINES PRECEDE LINE BEGIN - TRUNCATING

Reason:

Field titles were specified with a position of '-nn', which would place the title before print column 1.

Action:

No action required. The job proceeds.

Messages 2–19


CADA310E — REPORT FUNCTION NOT SUPPORTED FOR 'xxxxxxxx'

Reason:

The report function requested is not supported for the product name.

Action:

Review documentation for the product, correct the input command, and resubmit.

CADA400I — AUDIT TRAIL DATA SET BACKUP IS BEGINNING

Reason:

The BACKUP function has begun.

Action:

No action required.

CADA401I — AUDIT TRAIL BACKUP HISTORY TAPE HAS BEEN SUCCESSFULLY CREATED

Reason:

The audit trail BACKUP to tape is complete. Further BACKUP processing remains to be done. Even if the job cancels (due to a disk error, for example), the history tape is valid and current once this message is issued.

Action:

No action required.

CADA402I — AUDIT TRAIL DATA SET IS BEING RESET TO CLEARED STATUS

Reason:

The BACKUP function has begun to clear the audit trail data set.

Action:

No action required.



CADA403I — AUDIT TRAIL DATA SET BACKUP HAS BEEN SUCCESSFULLY COMPLETED

Reason:

All BACKUP processing has successfully completed.

Action:

No action required.

CADA404E — DISK FORMAT ERROR FOUND DURING DATA SET CLEAR OPERATION - RC=nnnn CSW=nnnn

Reason:

An unexpected disk error has occurred. The disk may not be properly initialized.

Action:

Verify formatting of the disk area on which the data set lies. See "Catalog Management Return Codes" for more information.

CADA405E — AUDIT TRAIL DATA SET BACKUP TERMINATED DUE TO ERRORS

Reason:

An error has occurred during the BACKUP function. The nature of the error will have been explained in a previous error message.

Action:

Correct and resubmit. :lblbox.Caution The audit trail data set may be left in a LOCKED status. The data set should be UNLOCKED immediately so that normal processing may continue. :elblbox.

CADA406E — DISP=KEEP AND ADD FUNCTION ARE MUTUALLY EXCLUSIVE

Reason:

The ADD function was used with DISP=KEEP. It is not allowed.

Action:


Messages 2–21


CADA407E — ERROR WRITING AUDIT TRAIL BACKUP ENTRY --RC=nnnn

Reason:

An I/O error occurred while writing the backup tape.

Action:

Use another tape and/or tape drive. See "Catalog Management Return Codes" for more information.

CADA408D — AUDIT TRAIL DATA SET RESERVED BY ANOTHER PARTITION

Reason:

The audit trail is currently enqueued from another partition or system. Processing cannot continue until it is freed.

Action:

If the problem persists, check if another program is using the audit trail.

If no such program is running, the audit trail data set may be permanently enqueued due to an abend of another user. In this case the data set unlock command may be used to force dequeue.

You can reply RETRY to this message to retry accessing the audit data set.

Respond RELEASE after verifying that the data set may be unlocked in order to unlock the data set.

CADA409E — ERROR OCCURRED WHILE UPDATING AUDIT TRAIL CONTROL RECORD

Reason:

An I/O error occurred while the audit trail control record was being updated.

Action:

If the problem persists, reinitialize the audit trail.



CADA410I — AUDIT TRAIL HISTORY TAPE NOT CREATED -- NO ENTRIES WERE FOUND IN THE AUDIT TRAIL DATA SET

Reason:

The BACKUP function has been attempted, but there are no entries to be backed up.

Action:

Wait until there are entries before attempting the BACKUP function.

CADA411E — NUMBER ENTRIES BACKED UP (nnnnnnnn) DOESN'T MATCH NUMBER IN AUDIT TRAIL DATA SET

Reason:

The number of entries written to the backup tape does not match the number of entries known to be in the Catalog. This indicates a probable I/O error reading the audit data set.

Action:

If the error persists, move the audit data set to another extent.

CADA500E — INVALID PARAMETER SPECIFIED ON CATALOG PARAMETER CARD

Reason:

The catalog command contains one or more invalid parameters.

Action:

Correct the catalog command and resubmit.

CADA501I — CATALOG RECOVERY BEGINNING, USING DATE = xxxxxxxx, TIME = xxxxxxxx

Reason:

Recovery of the Catalog is beginning. The date and time shown represent the point from which recovery is being performed.

Action:

No action required. Informational only.

Messages 2–23


CADA504I — CATALOG RECOVERY HAS COMPLETED SUCCESSFULLY

Reason:

Catalog recovery has successfully completed.

Action:

No action required. Informational only.

CADA505E — CATALOG RECOVERY HAS TERMINATED DUE TO ERRORS

Reason:

An error has occurred during catalog recovery. The function is terminated.

Action:

Refer to the previous message issued for the cause of the error. Correct the error and resubmit.

CADA506E — RE=nnnn VAL2=nnnn VAL3=nnnn VAL4=nnnn

Reason:

Catalog recovery has terminated with errors.

Action:

Press the ENTER/EOB key to continue.

CADA600E — ERROR HAS OCCURRED RTC=nnnn FC=nnnn

Reason:

An internal error has been detected. The message issued previous to this one documents the cause of the error. This message documents the internal function and return codes.

Action:

No action required. Informational. See "Catalog Management Return Codes" for more information.



CADA601E — SUFFICIENT STORAGE IS NOT AVAILABLE

Reason:

There is insufficient storage available.

Action:

Review the partition and system GETVIS storage available and make necessary corrections to provide more if the problem recurs.

CADA602E — AUDIT FILE NOT DEFINED

Reason:

The audit data set is not accessible.

Action:

Either generate AUDIT=NO, or take steps to make the audit dataset accessible and initialize it.

CADA603E — AUDIT FILE UNAVAILABLE DUE TO PRIOR ENQUEUE

Reason:

The audit file is enqueued from another partition or system.

Action:

Check if the audit data set is in use by another task. If it is not, the catalog lockout may be freed by use of the AUDTUTIL data set unlock function.

CADA604E — AUDIT FILE IS FULL

Reason:

The audit data set is full.

Action:

Backup and clear the audit data set. You may have to increase its size.

Messages 2–25


CADA605E — PHYSICAL I/O ERROR HAS OCCURRED CSW xxxx

Reason:

A physical I/O error has occurred during audit access. The integrity of the audit data set may be in doubt.

Action:

Backup and initialize the audit data set as soon as possible.

CADA606E — SEQUENTIAL END-OF-FILE

Reason:

An internal error is detected. The text indicates the specific error found. Another message will indicate the actual function experiencing the error. The function will terminate.

Action:

Collect diagnostic information, and contact Computer Associates for assistance in resolving the problem.

CADA607E — INVALID FUNCTION

Reason:


Action:


CADA608E — INVALID BUFFER ADDRESS

Reason:




Action:


CADA609E — INVALID BUFFER LENGTH

Reason:


Action:


CADA610E — EXCEED CONTROL INTERVAL SIZE

Reason:


Action:


CADA611E — INVALID SHARE OPTIONS

Reason:


Action:


Messages 2–27


CADA612E — AUDIT FILE NOT INITIALIZED

Reason:


Action:


CADA613E — RECORD TRUNCATED

Reason:


Action:


CADA614E — NO STORAGE FOR FUNCTION

Reason:


Action:


CADA615E — ENQUEUE ERROR

Reason:




Action:


CADA616E — DEQUEUE ERROR

Reason:


Action:


CADA617E — SAVER ERROR

Reason:


Action:


CADA618E — GETAREA ERROR

Reason:


Action:


Messages 2–29


CADA619E — FREEAREA ERROR

Reason:


Action:


CADA620E — OBTAIN ERROR

Reason:


Action:


CADA621E — MESSAGE ERROR

Reason:


Action:



CADC Prefixed Messages


CADC001I — WAITING FOR CATALOG ENQUEUE. DDNAME=ddname OWNER=(cpuid,job|vmid, step|cms command)

Reason:

The task has requested access to the Catalog or CAIAUDIT file, but it is currently in use from another partition or system.

Action:

If the Catalog is enqueued for batch processing, the situation is normal. The access request will be retried until the Catalog is dequeued. If the Catalog is not enqueued for batch processing, the access request will be repeated every 5 seconds, up to 255 times. The requesting task waits. If unsuccessful, the CADC005D message will be issued. Jobs which require the Catalog may not be run while the Catalog is being backed up.

If no such job is running, or if the job which enqueued the Catalog has cancelled, it is likely that a catalog lockout condition exists. To free the Catalog, proceed as follows:

If data set is from and DDNAME=

(default)

Use this command

CA-Dynam DYNBARCH

DYNBCAT

CAICATL

CAIAUDT

BDYNUTL ARCDEQ

BDYNUTL DEQUEUE

DYNCAT DEQUEUE

AUDTUTIL DATASET UNLOCK

CA-Top Secret CAISAFE

CAISAFS

CAISAFL

CASECAT DEQUEUE

CA-Scheduler alone CAIJMST

CAIJTRK

CAITSTG

CAIJDCM

FORCEDEQ (refer to the CA-Scheduler Systems Programmer Guide)

CA-Scheduler with CA-DRIVER

CAIJDRV FORCEDEQ (refer to the CA-Scheduler Systems Programmer Guide)

Messages 2–31


If data set is from and DDNAME= Use this command

(default)

CA-DRIVER alone CAIJDRV -FORCEDEQ (refer to the CA-Scheduler Systems Programmer Guide)

CADC002I — CATALOG ENQUEUE OBTAINED. PROCESSING CONTINUES. DDNAME=ddname

Reason:

The task has obtained access to the Catalog or CAIAUDIT file.

Action:

None.

CADC003I — ENQUEUED FOR BATCH PROCESSING. DDNAME=ddname.

Reason:

The Catalog or CAIAUDIT file has been enqueued for processing from a batch program. It remains enqueued, not allowing access by other partitions or systems until the batch processing is complete. The Catalog is enqueued in this fashion by the BACKUP and SCRATCH functions.

The batch program which owns the Catalog continues. Any other program attempting to use the Catalog will be placed in a wait state until the batch program enqueue is released.

Action:

None.

CADC004I — CATALOG DEQUEUED. DDNAME=ddname.

Reason:

The Catalog file has been dequeued from batch processing. Any other programs awaiting catalog availability will proceed.

Action:

None.



CADC005D — ENQUEUE FAILURE DDNAME=ddname

Reason:

Catalog Management has retried accessing the Catalog, but has not been able to obtain enqueue. The Catalog is owned by the task noted in the CADC001 message. The system will wait for an operator response.

Action:

Investigate the cause of the enqueue failure. If the task that owns the Catalog is performing a batch catalog utility function, such as BACKUP or DEFINE, the failure may be normal. In this event, the function which owns the Catalog should be allowed to complete. Enter one of the following responses:

RETRY Retry the ENQUEUE process

EOB Retry the ENQUEUE process

STOP Stop the partition while investigating, or to allow the job which owns the Catalog to continue and finish (a job STOPped in this manner may be restarted at any time using the CASTART command).

CANCEL Cancel the partition requesting the Catalog

If the task which owns the Catalog appears to have canceled with the Catalog enqueued, or is in an unending loop or wait, refer to the table shown under message CADC001I and proceed accordingly.

CADC006W — WRAP-AROUND HAS OCCURRED DDNAME=ddname

Reason:

All of the reserved continuous free space in the Catalog has been used. Processing will continue, but performance will be degraded as Catalog Management will be searching for available free space records, as required. When all of the available free space is used, the task abends.

Action:

Perform BACKUP/RESTORE REORG at the earliest opportunity to collect all free space records at the end of the Catalog. If you receive the message for the HELP file, you may choose to delete and allocate it with a larger space specification. The adapter needs to be recycled if the HELP file is deleted and reallocated.

Note: If you should receive the message for the CAISAFS file, either initialize the file (and rerun CASESESN if applicable) or increase the extents.

Messages 2–33


CADC007W — RESERVED INDEX AREA FULL

Reason:

The pre-allocated index extension area in the Catalog has been filled.

Action:

Perform BACKUP/RESTORE REORG and increase the Catalog size at the earliest opportunity.

CADC008I — AUTOMATIC CLOSE SUCCESSFUL DDNAME=xxxxxxx

Reason:

The task that owned the catalog-managed file identified by DDNAME= has abended, but the Catalog was successfully closed during the recovery process.

Action:

None.

CADC009I — AUTOMATIC CLOSE FAILED DDNAME=xxxxxxx

Reason:

The task that owned the catalog-managed file identified by DDNAME= has abended. An attempt was made to dequeue the Catalog during recovery but it failed. This could be a result of some situations (such as insufficient storage) that cannot be directly dealt with.

Action:

None. However, if the CADC005D message should appear later, it might then be necessary to run the DYNCAT DEQUEUE function. If this message occurs frequently, contact Computer Associates Technical Support.

CADC010W — CAJRNL2 OPERATION FAILED

Reason:

The journal file could not be located.

Action:

Reinitialize the journal and run the catalog backup.



CADC020E — RECOVERY CAN NOT BE PERFORMED AGAINST A REORGANIZED CATALOG.

Reason:

Physical recovery depends on the RBA addresses of the control intervals not changing from those recorded in the journal file. A reorganizing restore changes these RBAs.

Action:

Rerun the restore without the reorganize option, and then rerun recovery.

CADC022E — JOURNAL RECORDS NOT BEING PROCESSED IN DATE/TIME SEQUENCE.

Reason:

Journal records must be processed in ascending date/time sequence. The likely cause of this is multiple journal tape files being read out of sequence. The Catalog is not in a usable state after this message is issued. Before running anything that depends on the Catalog this situation must be resolved.

Action:

Ensure that the journal tape files are processed in sequence. If this does not solve the problem contact Computer Associates Technical Support.

CADC023E — ONLY PHYSICAL TYPE JOURNAL RECORDS CAN BE PROCESSED.

Reason:

Only journal records produced by the physical journal feature of Catalog Management can be processed. The Catalog may not be in a usable state after this message is issued. Before running anything that depends on the Catalog this situation must be resolved.

Action:

Contact Computer Associates Technical Support.

CADC024E — CCR RECORD NOT FOUND AT RBA ZERO.

Reason:

The Catalog control record could not be located at RBA zero of the Catalog. The Catalog is not in a usable state after this message is issued. Before running anything that depends on the Catalog, this situation must be resolved.

Messages 2–35


Action:

Ensure the prior non-reorganizing restore completed successfully. If this is the case re-run both the restore and recovery, otherwise contact Computer Associates Technical Support.

CADC025E — JOURNAL OUT OF SYNC WITH CATALOG.

Reason:

The Catalog start of session record was not preceded by a beginning sync point record. The Catalog may not be in a usable state after this message is issued. Before running anything that depends on the Catalog, this situation must be resolved.

Action:


CADC026E — CACNPHY0 ERROR. PPLECD=x'eeeeeeee' R0=x'rrrr' DISP=x'dddd'

Reason:

An error occurred in the Catalog Management I/O module. The error code is 'eeeeeeee'. The register zero value at the time of the error is 'rrrr'. The error occurred at displacement 'dddd' in program CACUJCR0. The Catalog may not be in a usable state after this message is issued. Before running anything that depends on the Catalog, this situation must be resolved.

Action:


CADC028E — AUDIT/E ERROR. ATPLRTCD=x'eeeeeeee' R0=x'rrrr' DISP=x'dddd'

Reason:

An error occurred in the journal management I/O module. The error code is 'eeeeeeee'. The register zero value at the time of the error is 'rrrr'. The error occurred at displacement 'dddd' in program CACUJRC0. The Catalog may not be in a usable state after this message is issued. Before running anything that depends on the Catalog, this situation must be resolved.

Action:




CADC029I — JOURNAL TAPE VOLUME vvvvvv 1ST RECORD DATE dddddd TIME tttttttt

Reason:

This message is issued for the 1st record on each journal backup tape read. The tape volume vvvvvv, the journal records creation date dddddd, and time tttttttt is displayed.

Action:

None.

CADC030E — 1st AUDIT RECORD TIMESTAMP SHOULD PRECEDE LAST BACKUP TIMESTAMP. REPLY GO/CANCEL.

Reason:

The message indicates that the backup was done prior to the initialization of the journal data set.

Action:

Reply GO if this is an acceptable condition, otherwise reply CANCEL.

CADC031E — SYNCPOINT RECORD SEQUENCE ERROR. DISP=x'dddd' REASON=x'rr'

Reason:

A journal syncpoint sequence error has occurred. This error occurred at displacement dddd in CACUJCR0. The reason code is rr.

x'01' - The syncpoint record is a unknown type. x'02' - The ending syncpoint record is missing. x'03' - A beginning syncpoint record was expected. x'04' - An ending syncpoint record was expected.

The Catalog may not be in a usable state after this message is issued. Before running anything that depends on the Catalog, this situation must be resolved.

Action:


Messages 2–37


CADC032E — SYNCPOINT FLUSH RECORD ENCOUNTERED. REMAINDER OF JOURNAL RECORDS WILL BE IGNORED.

Reason:

The syncpoint flush record is created when the Catalog application determines that the data set and the journal are no longer in sync. All journal records that follow the syncpoint flush record will be ignored.

The Catalog Management may not be in a usable state after this message is issued. Before running anything that depends on the Catalog, this situation must be resolved.

Action:


CADC100E — ERROR HAS OCCURRED RTC=nnnn FCN=nnnn

Reason:

An unexpected return code has been issued by the Catalog Management service. The function code and return codes are Catalog Management codes, and indicate a problem in accessing the Catalog or CAIAUDIT files.

Action:

Inspect the return code for 'normal' conditions such as insufficient storage. See "Catalog Management Return Codes" later in this chapter for more information. If the problem does not appear to be of this nature, document the problem and contact Computer Associates Technical Support.

CADC101E — SUFFICIENT STORAGE IS NOT AVAILABLE FOR FUNCTION

Reason:

There is not enough storage for the function.

Action:

Review the partition and system GETVIS storage available and make necessary corrections to provide more if the problem recurs.



CADC102E — NO LABEL INFORMATION FOR ddname DATA SET

CADC102E — INVALID LABEL INFORMATION FOR ddname DATA SET

CADC102E — SYSNNN LOGICAL UNIT NOT ASSIGNED

Reason:

The Catalog could not be accessed for the reason noted in the message.

Action:

Correct the error and retry the job.

CADC103E — CATALOG IS UNAVAILABLE DUE TO PRIOR ENQUEUE

Reason:

The Catalog is enqueued from another partition or system.

Action:

Check if the Catalog is legitimately in use by another task. If it is not, refer to the table shown under message CADC001I and proceed accordingly.

CADC104E — CATALOG IS FULL

Reason:

The Catalog is full.

Action:

Back up the Catalog and RESTORE/REORG it to a larger extent. The situation may be temporarily eased by running the DYNCAT SCRATCH function.

CADC105E — PHYSICAL I/O ERROR HAS OCCURRED CSW xxxxxxxx

Reason:

A physical I/O error has occurred during Catalog access. The integrity of the Catalog is in doubt.

Messages 2–39


Action:

Check the integrity of the Catalog by running the DYNCAT BACKUP function. If necessary, the Catalog may have to be rebuilt.

CADC106E — INVALID ADDRESS OF RELATIVE BYTE ADDRESS

Reason:


Action:

Collect as much diagnostic information as possible, and contact Computer Associates Technical Support.

CADC107E — INVALID ADDRESS OF NEXT PARAMETER LIST

Reason:


Action:


CADC108E — INVALID BUFFER ADDRESS SPECIFIED

Reason:


Action:




CADC109E — INVALID BUFFER LENGTH

Reason:


Action:


CADC110E — INVALID KEY LENGTH

Reason:


Action:


CADC111E — INVALID RECORD SIZE

Reason:


Action:


CADC112E — INVALID VOLUME SEQUENCE NUMBER

Reason:


Messages 2–41


Action:


CADC113E — INVALID FILE SEQUENCE NUMBER

Reason:


Action:


CADC114E — INVALID VERSION NUMBER

Reason:


Action:


CADC115E — INVALID VAULT IDENTIFIER

Reason:


Action:




CADC116E — INVALID CATALOG OPTIONS SPECIFIED

Reason:


Action:


CADC117E — INVALID CATALOG FUNCTION COMBINATIONS

Reason:


Action:


CADC118E — INVALID CATALOG COMBINATION TABLE

Reason:


Action:


CADC119E — INVALID FUNCTION CODE

Reason:


Messages 2–43


Action:


CADC120E — INVALID ADDRESS OF CACB

Reason:


Action:


CADC121E — NO RECORD FOUND AT SPECIFIED ADDRESS

Reason:


Action:


CADC122E — INVALID GET NEXT NO PREVIOUS GET OR ADD

Reason:


Action:




CADC123E — LOGICAL END-OF-FILE

Reason:


Action:


CADC124E — INVALID RECORD IDENTIFIER

Reason:


Action:


CADC125E — INVALID ADDRESS OF DATA SET NAME

Reason:


Action:


CADC126E — A LINK TO THIS RECORD ALREADY EXISTS

Reason:


Messages 2–45


Action:


CADC127E — DUPLICATE RECORD

Reason:


Action:


CADC128E — INVALID DATA SET NAME

Reason:


Action:


CADC129E — BUFFER IS TOO SHORT FOR THIS RECORD

Reason:


Action:




CADC130E — GENERATION GAP

Reason:


Action:


CADC131E — ERROR DURING OBTAIN FUNCTION

Reason:


Action:


CADC132E — INVALID DATA SET INDEX RECORD

Reason:


Action:


CADC133E — PREMATURE END-OF-CHAIN

Reason:


Messages 2–47


Action:


CADC134E — SPECIFIED FILE SEQUENCE IS NOT FOUND

Reason:


Action:


CADC135E — NO MATCHING VOLUME FOUND

Reason:


Action:


CADC136E — INVALID VOLUME INDEX RECORD

Reason:


Action:




CADC137E — PREMATURE END-OF-CHAIN

Reason:


Action:


CADC138E — BAD RETURN CODE FROM AUDIT EXIT

Reason:


Action:


CADC139E — INVALID ADDRESS OF VOLUME SERIAL

Reason:


Action:


CADC140E — INVALID ADDRESS OF BUF1

Reason:


Messages 2–49


Action:


CADC141E — INVALID ADDRESS OF BUF2

Reason:


Action:


CADC142E — INVALID ADDRESS OF CAB

Reason:


Action:


CADC143E — INVALID DEVICE ADDRESS FOR ddname

Reason:


Action:




CADC144E — INVALID DEVICE TYPE FOR ddname

Reason:


Action:


CADC145E — INVALID CONTROL INTERVAL SIZE FOR ddname

Reason:


Action:


CADC146E — INVALID EXTENT LIMITS FOR ddname

Reason:


Action:


CADC147E — RECORD IS OUTSIDE EXTENT FOR ddname

Reason:


Messages 2–51


Action:


CADC148E — NO FREE STORAGE AVAILABLE

Reason:


Action:


CADC149E — INVALID FUNCTION CODE

Reason:


Action:


CADC150E — INVALID ADDRESS OF EXIT LIST

Reason:


Action:




CADC151E — INVALID ADDRESS OF WORKAREA

Reason:


Action:


CADC152E — INVALID ADDRESS OF CATALOG PARAMETER LIST

Reason:


Action:


CADC153E — INVALID CATALOG CONTROL RECORD

Reason:


Action:


CADC154E — RBA OUTSIDE FORMAT

Reason:


Messages 2–53


Action:


CADC155E — SAVER ERROR

Reason:


Action:


CADC156E — INVALID INDEX RBA

Reason:


Action:


CADC157E — INVALID INDEX DISPLACEMENT

Reason:


Action:




CADC158E — INVALID INDEX NUMBER

Reason:


Action:

Collect as much diagnostic information as possible, and and contact Computer Associates Technical Support.

CADC190W — CAIAUDIT IS NOT ACTIVE - NO LOGGING IS BEING DONE

Reason:

CAIAUDIT=YES was genned in the DYNAM macro and the interface module to the CAIAUDIT file has detected that this component is not active. The message will be issued once every 50 attempts to write to this file.

Action:

Processing will continue. The event will not be logged to the CAIAUDIT file. Please check your DYNAM macro to insure that the desired value is coded for this parameter. Check startup procedures if CAIAUDIT support is desired.

CADC191W — UNKNOWN CAIAUDIT EVENT - PRODUCT=c CLASS=nn CODE=nnnn

Reason:

The interface to the CAIAUDIT file has detected a product, class, or code that it cannot translate to a CAIAUDIT code.

Action:

Processing will continue. The event will be logged with an event code of UNDOCUMENTED. Please contact Computer Associates Technical Support so that it can be determined whether or not the event should be logged to the CAIAUDIT file.

Messages 2–55


CADC192W — INVALID PRODUCT DYNAM/x

Reason:

The interface to the CAIAUDIT file has detected a product that it cannot identify.

Action:

Processing will continue. The event will not be logged. Please contact Computer Associates Technical Support so that it can be determined whether or not the product should be logged to the CAIAUDIT file.

CADC193W — CAIAUDIT ERROR - R/C=x'nnnnnnnn'

Reason:

CAIAUDIT has returned an error to the DYNAM interface program.

Action:

Processing will continue. An explanation of the return codes is as follows:

X'00000011' ACVT not in SVA

X'00000012' Logger task not active-rec placed in queue

X'00000013' Invalid product/event code

X'00000014' Message queue is not allocated

X'00000017' Logger task not active-rec not placed in queue

CADC194W — INVALID PRODUCT/EVENT CODE - PRODUCT=cccc,EVENT=cccc

Reason:

CAIAUDIT does not recognize the product/event passed in the audit record.

Action:

Processing will continue. The product and event are shown. Verify that the product and event codes are valid.



CADC198E — ERROR HAS OCCURRED RTC=nnnn FCN=xxxxxxxx

Reason:

An unexpected return code has been issued by the Catalog Management service. The function code and return codes are Catalog Management codes, and indicate a problem in accessing the Catalog or CAIAUDIT files.

Action:

Inspect the return code for 'normal' conditions such as insufficient storage. See "Catalog Management Return Codes" for more information. If the problem does not appear to be of this nature, document the problem and contact Computer Associates Technical Support.

CADC199E — UNEXPECTED ERROR-SEND DUMP TO COMPUTER ASSOCIATES

Reason:

An unexpected internal error is detected. The function will terminate with a dump.

Action:

Send dump, JCL and console log to Computer Associates.

CADC201E — INVALID RECORD ID. ID EXPECTED=xxx, ID ENCOUNTERED=xxx

Reason:

During the Catalog backup function, an invalid catalog record ID was encountered. The type of record expected at the location and the type of record found is indicated. The integrity of the Catalog is suspect.

Action:

When the backup has completed, rebuild the Catalog. The error condition may be cleared by:

■ Performing a RESTORE REORG function using the backup tape created, or

■ Restoring the previous backup tape and performing catalog recovery using the CAIAUDIT data set.

If the RESTORE REORG function is used, any information contained in the Catalog record in error will be lost.

Messages 2–57


CADC202I — DSN=data-set-name, VERSION=nnnnnn, VOLSER=xxxxxx, RBA=nnnnnnnn

Reason:

During CAIAUDIT recovery, an error was found with the component records of the data set, version, and volume noted. The information is provided to aid in verifying the accuracy of the Catalog information about the data set. The CAIAUDIT recovery proceeds.

Action:

Check the accuracy of the information for the specified data set.

CADC203E — CATALOG ERROR OCCURRED. F/C=nnnn R/C=nnnnnnnn

Reason:

During CAIAUDIT recovery, a physical error was detected. The CAIAUDIT recovery proceeds.

Action:

Recover the Catalog. Either the backup tape just created may be used to perform a RESTORE REORG function, or a previous backup tape may be used in conjunction with the CAIAUDIT Catalog recovery procedure. See "Catalog Management Return Codes" for more information.

CADC204E — UNRECOVERABLE CATALOG ERROR

Reason:

During the Catalog backup function, a severe error was encountered in the Catalog, CAICATL. The function is terminated.

Action:

Recover the Catalog from a previous backup tape because the tape being created is incomplete and may not be used.

To recover the Catalog, restore the previous backup tape using the RESTORE function of DYNCAT, and bring it up-to-date by using either:

■ The CAIAUDIT recovery feature, or

■ DYNCAT manual maintenance if the CAIAUDIT feature is not installed.



CADC205E — INVALID RECORD DISPLACEMENT. PLEASE RE-SPECIFY

Reason:

An invalid RBA was entered, most likely with non-hexadecimal digits, or too large a displacement.

Action:

Correct the input and reenter.

CADC206I — xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Reason:

The CACNUTIL +nnnn command was issued. This message displays 16 bytes of data found in the Catalog at the specified displacement.

Action:

None.

CADC207E — VERIFICATION ERROR

Reason:

There is an error in verification.

Action:

None. Informational.

CADC208E — INVALID COMMAND

Reason:

There is an invalid command.

Action:

Correct the command and resubmit.

Messages 2–59


CADC209W — COMMAND OUT OF SEQUENCE

Reason:

A REP= command was entered without a preceding +nnnn or VER= command to CACNUTIL.

Action:

Correct the command and resubmit.

CADC210W — DATASET NOT ACCESSIBLE

Reason:

The desired data set (Catalog or CAIAUDIT file) cannot be located. This is probably a JCL error.

Action:

Correct the desired data set and resubmit.

CADC211I — xxx FOUND AT RBA=nnnnnnnn

Reason:

A DSN= or VOL= command to display the RBA of the corresponding DBR or VBR was issued.

Action:

None.

CADC212D — ENTER CATALOG SHARE OPTION

Reason:

This is issued during RESTORE REORG if the Catalog share option is being changed from SHARE=YES or SHARE=VSELOCK to something else.

Action:

Respond YES or NO or VSELOCK to set the desired share option.



CADC213E — AUDIT ERROR OCCURRED. F/C=nnn R/C=nnnnnnnn

Reason:

This is issued by a DYNCAT function if an CAIAUDIT error occurs during processing. The CAIAUDIT function and return codes are displayed.

Action:

Review the CAIAUDIT return codes to determine if the error is 'normal', and if so, correct the condition. If not, collect documentation and contact Computer Associates Technical Support. See "Catalog Management Return Codes" in the "Codes" chapter for more information.

CADC214E — INVALID MULTIFILE SET

Reason:

This is issued by the DYNCAT SCRATCH function if an incomplete multi-file set is encountered. The CADC202I message will be issued to document the data set name and volume with the error.

Action:

Use the DYNCAT BACKUP function to validate the contents of the Catalog, and contact Computer Associates Technical Support.

CADC215E — INVALID FUNCTION F/C=nnnnn

Reason:

There is an invalid function code in the CAIAUDIT record. This is an internal error.

Action:


CADC216E — INVALID REPLACE, RECORD id=nnnnn

Reason:

During an AUDIT CATALOG RECOVERY an internal request to replace a record has been issued, but the record ID can not be found.

Messages 2–61


Action:


CADC352W — RECORD NOT FOUND

Reason:

The record being displayed does not exist for this CPUID.

Action:

Check the CPUID to ensure it is correct, or add this record to the file.

CADC411D — REALLY RESTORE THE CATALOG?

Reason:

The RESTORE command has been submitted, and DYNCAT is verifying the function before starting.

Action:

Respond YES in order to restore the Catalog. Any other response will cause DYNCAT to abort the function.

CADC421D — REALLY INITIALIZE|DEQUEUE THE CATALOG?

Reason:

The INITIAL or DEQUEUE function has been requested and DYNCAT is verifying that the files are to be initialized or dequeued as appropriate.

Action:

Respond YES if the Catalog is to be initialized or dequeued. Any other response will abort the function.



CADC422I — CATALOG IS BEING INITIALIZED

Reason:

A response of YES was entered to message CADC421D.

Action:

None.

CADC424I — DYNAM RESTORE

Reason:

The DYNCAT RESTORE function is in progress.

Action:

None.

CADC426I — DYNAM BACKUP

Reason:

The DYNCAT BACKUP function is in progress.

Action:


CADC431E — INVALID RESPONSE

Reason:

An invalid response was entered for message CADC411D or CADC421D.

Action:

Enter a valid response.

Messages 2–63


CADC500E — module ERROR: OFFSET=address : FUNCTION=name : FC=nnnnnnnn RC=nnnnnnnn

Reason:

An unexpected error has occurred in the named module. This message is often followed by an additional message describing the error (such as CADC512W).

Action:

If additional messages are not provided, contact Computer Associates Technical Support.

CADC501W — OMS M:ACC DATA SET filename IS ACCESSIBLE, BUT CA-DYNAM/TLMS (CA-TLMSII) IS NOT ACTIVE ON OS SYSTEM

Reason:

The CAIMACC data set is accessible, but CA-Dynam/TLMS is not active.

Action:

Activate CA-Dynam/TLMS on your shared MVS system.

CADC502D — OMS M:ACC DATA SET filename NOT ACCESSIBLE,

CADC502D — LOGGING OPERATIONS TO OS SYSTEM SUSPENDED

CADC502D — RECREATE THE OS TAPE VOLUME MASTER FILE WHEN CA-DYNAM/TLMS (CA-TLMSII) IS ACTIVE

CADC502D — ENTER EOB/END/ENTER TO CONTINUE

Reason:

Logging cannot be performed to the CAIMACC data set. Logging is suspended, which means that the CAICATL and the Volume Master File will not be synchronized. The CAICATL will be correct.

Action:

Run the appropriate jobs to synchronize the VMF and CAICATL once CA-Dynam/TLMS is operational.



CADC503E — NO LABEL INFORMATION FOR OMS M:ACC filename

Reason:

The DLBL and EXTENT for CAIMACC cannot be located.

Action:

Contact your Systems Programmer for assistance.

CADC504E — INVALID LABEL INFORMATION FOR OMS M:ACC filename

Reason:

The DLBL and EXTENT are invalid.

Action:


CADC505E — NO FORMAT 1 RECORD FOUND OMS M:ACC filename

Reason:

No VTOC entry has been found for the MQF.

Action:

Contact your Systems Programmer for assistance. The MQF must be formatted using the proper CA-Dynam/TLMS (CA-TLMS II) utility before it can be used.

CADC506E — IMPROPER ASSIGNMENT OMS M:ACC filename SYSnnn=cuu

Reason:

The logical unit assignment for the MQF is incorrect.

Action:


Messages 2–65


CADC507E — INVALID FORMAT FOR OMS M:ACC filename SYSnnn=cuu

Reason:

The MQF is found, but the format is invalid.

Action:

Contact your Systems Programmer for assistance. It will probably be necessary to reinitialize the M:ACC MQF using the proper CA-Dynam/TLMS (CA-TLMS II) utility.

CADC508E — INVALID FULL CONDITION OMS M:ACC filename SYSnnn=cuu

Reason:

The MQF has remained full too long.

Action:

Contact your Systems Programmer for assistance. It will probably be necessary to reinitialize the M:ACC MQF using the proper CA-Dynam/TLMS (CA-TLMS II) utility and synchronize the CAICATL to the VMF.

CADC509E — ENQUEUE FAILURE OMS M:ACC filename SYSnnn=cuu

Reason:

CA-Dynam cannot obtain an enqueue on the MQF.

Action:

Contact your Systems Programmer for assistance. It will probably be necessary to reinitialize the M:ACC MQF using the proper CA-Dynam/TLMS (CA-TLMS II) utility, and synchronize the CAICATL to the VMF.



CADC512W — XSYSTEM PATH pathid NOT ACCESSIBLE

CADC512W — LOGGING OPERATIONS TO PATH pathid SUSPENDED

CADC512W — RESYNCHRONIZATION OF THE CORRESPONDING CATALOGS MAY BE REQUIRED

CADC512W — ENTER END/EOB/ENTER TO CONTINUE

Reason:

The named pathid could not be updated with the information required to keep an associated tape management system in synchronization. This message is often preceded by a message between CADC513W and CADC519W, describing the exact nature of the problem.

Action:

Correct the problem as described in the preceding message, then execute the appropriate jobs to synchronize the tape management systems.

CADC513W — NO LABEL INFORMATION FOR XSYSTEM PATH pathid

Reason:

Either the disk referenced by the FILEDEF cannot be accessed or the FILEDEF for the named pathid is missing.

Action:

Correct the DYNLINK EXEC.

CADC514W — INVALID LABEL INFORMATION FOR XSYSTEM PATH pathid

Reason:


Action:


Messages 2–67


CADC515W — NO FORMAT 1 RECORD FOUND FOR XSYSTEM PATH pathid

Reason:

Either the disk referenced by the FILEDEF cannot be accessed or the VTOC of the accessed disk does not contain the DSN as specified in the FILEDEF command.

Action:

Ensure that the FILEDEF DSN correctly matches the VTOC entry. If there is no VTOC entry for the specified file then use the CAICATDK utility program to create one.

CADC516W — IMPROPER ASSIGNMENT FOR XSYSTEM PATH pathid

Reason:


Action:


CADC517W — INVALID FORMAT ON XSYSTEM PATH pathid

Reason:

The specified pathid was located, but the format of the file is invalid.

Action:

Initialize the path using the DYNCAT MACC INITIAL DDNAME=pathid control statement.

CADC518W — INVALID FULL CONDITION ON XSYSTEM PATH pathid

Reason:

The specified pathid could not be updated because of a file full condition. The current update is lost. The receiving system has remained inactive for too long a period.

Action:

The RWAIT of the receiving system should be decreased.



CADC519W — ENQUEUE FAILURE ON XSYSTEM PATH pathid

Reason:

The specified pathid could not be updated because of a file enqueue condition. The current update is lost.

Action:

Dequeue the specified pathid using the DYNCAT MACC DEQUEUE DDNAME=pathid command.

CADC520I — TRANSACTION FOR VOL=volser RECEIVED: PATH=pathid : NODE=nodeid STATUS=status

Reason:

A transaction for the specified volser has been read from the specified pathid. The node which sent the volume update has changed the volume's status to that reported in the message. The status reported may be:

(INPUT) DSN=data set name

(OUTPUT) DSN=data set name

(MAINT) TYPE=ACTIVE

(MAINT) TYPE=SCRATCH

Action:

None, this is an informational message produced when the PATH LOG ON pathid RECEIVE command had been issued.

CADC521I — VERIFY RECEIVE: PATH=pathid1 : FOR=pathid2 : TIME=hh:mm:ss

VERIFY SEND: PATH=pathid1 : FOR=pathid2 : TIME=hh:mm:ss

Reason:

A special path verification record has been processed by this CPU. Normally if a path has been 'idle' for too long a period, a verify transaction would be sent along this node's send path, specifying its receive path as the target. If the verify transaction is then received, both paths have been verified as active, and both nodes are assumed to be communicating.

Action:

None, this is an informational message produced when the PATH LOG ON pathid VERIFY command had been issued.

Messages 2–69


CADC522E — VERIFY ERROR: SEND PATH=pathid1 : RECEIVE PATH=pathid2 : TIME SENT=hh:mm:ss

Reason:

A special path verification record had previously been sent by this CPU, but it has not been received on the corresponding path within the specified time limit. This indicates that an error exists in either of the two paths or communicating nodes.

Action:

Ensure that the nodes are active. If active, then check for a prior CADC500E message in the console log.

CADC523E — PLIST IN ERROR=address hex-data

Reason:

This message is produced after a CADC500E message and provides additional information regarding an XSYSTEM function error.

Action:

None. This is produced when the PATH LOG ON pathid PLIST command is issued.

CADC524E — REGISTERS IN ERROR=register-savearea

Reason:

This message is produced after a CADC500E message and provides additional information regarding an XSYSTEM function error.

Action:

None. This is produced when the PATH LOG ON pathid PLIST command is issued.

CADC525E — PATH pathid1 IS FULL: VRFY FOR: pathid2 COULD NOT BE SENT

Reason:

A special path verification record could not be sent on pathid1 because of a FILE FULL condition.



Action:

Ensure that the nodes are active. If active, then check for a prior CADC500E message in the console log.

CADC526E — STATUS CONFLICT DETECTED: VOL=volser : RECEIVE PATH=pathid RECEIVE DSN=data set name1 : CATALOG DSN=data set name2

Reason:

A transaction for the specified volume was received on the specified pathid, but conflicts could not be updated in this node's CA-Dynam Catalog. The two tape volume catalogs require synchronization.

Action:

Execute the appropriate jobs to synchronize the tape management systems.

CADC527I — PATH pathid PROCESSED: UPDATES=nn : CONFLICTS=nn : ERRORS=nn RC=retcode

Reason:

The specified path has been processed (emptied of any transactions). The total number of volume records read which resulted in an update to this node's catalog, as well as the total number of detected conflicts and errors, are reported. The return code is the current return code for this iteration of the path.

Return Code Internal Meaning

0 NO ERROR ENCOUNTERED

4 VERIFY SENT ON CORRESPONDING SEND PATH

8 VOLUME CONFLICT DETECTED

12 A VERIFY ERROR WAS DETECTED ON THIS PATH

24 SEND PATH IS FULL (VERIFY COULD NOT BE SENT)

28 AN INTERNAL LOGIC ERROR WAS DETECTED

32 A SYSTEM ADAPTER ERROR OCCURRED

36 NO STORAGE AVAILABLE

Messages 2–71


Action:

None, this is an informational message produced when the PATH LOG ON pathid SUMMARY command is issued.

CADC530D — UNABLE TO OBTAIN ENQUEUE DDNAME=pathid : REPLY RETRY OR CANCEL

Reason:

The specified pathid could not be updated because of a file enqueue condition. The current update is still pending.

Action:

Dequeue the specified pathid using the DYNCAT MACC DEQUEUE DDNAME=pathid command and then reply RETRY.

CADC531I — XSYSTEM FILE pathid IS nn PERCENT FULL

Reason:

A record has been written to the specified XSYSTEM path to log a volume status change, causing the specified file threshold to be reached.

Action:

If this message is produced several times, for increasing threshold limits, the corresponding system is not receiving.



CADC539E — XSYSTEM (CATAXSS0) TASK TERMINATED AT OFFSET=address : reason

Reason:

An attempt was made to start the XSYSTEM task, but a serious error prevented task initialization. The reasons given may be one of the following:

NO STORAGE AVAILABLE ERROR PERFORMING OBTAIN ERROR MANIPULATING DATE XSYSTEM PATH TABLE NOT FOUND A CORRESPONDING SEND PATH WAS NOT LOCATED RECEIVE (TO) PATHS NOT DEFINED FOR THIS CPUID XSYSTEM NODE TABLE NOT FOUND ENQUEUE FAILURE ON CRITICAL RESOURCE DTPARMS NOT LOCATED CASAGENA NOT LOCATED ERROR PERFORMING SAVER ERROR IN WAIT PROCESSING

Action:

Correct the error and then re-initialize CA-Dynam/T or enter the PATH RESTART command.

CADC540I — RECEIVE PATH=pathid (nodeid) ADDR=address

LAST EXEC=hh:mm:ss LAST REC=hh:mm:ss

NUM REC=nn ERRS=nn : RC=retcode : STATUS=status

Reason:

This message is issued in response to a PATH QUERY command and gives the status for a receive path controlled by this CPU. The nodeid is the nodeid of the CPU sending transactions on this path. The return code is the highest return code recorded for this path. The status will display whether the path is currently enabled, and whether any traces or logs are pending for this path.

Action:

None.

Messages 2–73


CADC541I — SEND PATH=pathid STATUS=status

Reason:

This message is issued in response to a PATH QUERY command and gives the status for a send path controlled by this CPU.

Action:

None.

CADC542E — SPECIFIED PATH(S) NOT DEFINED

Reason:

This message is issued in response to a PATH QUERY pathid command for which a matching pathid (controlled by this CPU) was not found.

Action:

Correct the pathid and reissue the command.

CADC543E — XSYSTEM (CATAXSS0) TASK ALREADY INITIATED

CADC543E — XSYSTEM (CATAXSS0) TASK NOT INITIATED

CADC543E — XSYSTEM (CATAXSS0) TASK HAS ABENDED

Reason:

Refer to the reason that corresponds with your message.

Message Reason

INITIATED Message issued in response to a PATH RESTART command when there is already an XSYSTEM task present in the system.

NOT INITIATED Message issued in response to a PATH QUERY command where there are no receive paths controlled by this CPU.

ABENDED Message issued in response to a PATH command when a prior abend has occurred in the XSYSTEM task. The XSYSTEM task is no longer present.



Action:

Refer to the action that corresponds with your message.

INITIATED None. Only one XSYSTEM task may be present in the service machine.

NOT INITIATED None. This message indicates that there were no XSYSTEM paths with the 'TO' option specifying this CPUID.

ABENDED Execute the PATH RESTART command.

CADC543I — XSYSTEM (CATAXSS0) TASK INITIATED

Reason:

This message is issued during XSYSTEM task startup. The name of the XSYSTEM task is CATAXSS0 (using the Task Manager TCB Q command).

Action:

None.

CADC544I — RECEIVE PATH pathid (nodeid) DISABLED

RECEIVE PATH pathid (nodeid) ENABLED

Reason:

This message is issued in response to a PATH ENABLE or PATH QUERY command for one or more RECEIVE pathids. A separate message will appear for each RECEIVE pathid specified in the query.

Action:

None.

Messages 2–75


CADC545I — TRACE STARTED FOR RECEIVE PATH pathid (nodeid)

CADC545I — TRACE ENDED FOR RECEIVE PATH pathid (nodeid)

CADC545I — LOG STARTED FOR RECEIVE PATH pathid (nodeid)

CADC545I — LOG ENDED FOR RECEIVE PATH pathid (nodeid)

Reason:

This message is issued in response to a PATH TRACE or PATH LOG command for one or more RECEIVE pathids. A separate message will appear for each RECEIVE pathid specified in the query.

Action:

None.

CADC546I — CASAVMF0 (SEND PATH) TRACE STARTED

CASAVMF0 (SEND PATH) TRACE ENDED

Reason:

This message is issued in response to a PATH TRACE command for SEND paths. A separate message will appear for each SEND pathid.

Action:

None.

CADC550I — ENTER TDYNSYNC COMMAND

Reason:

TDYNSYNC was executed through the system console.

Action:

Enter a TDYNSYNC command.



CADC551E — CATALOG ERROR DISP=DDDD F/C=FFFF R/C=RRRR

Reason:

An unexpected error occurred while accessing the Catalog. The job is terminated with a dump.

Action:

Retain the console log, SYSLST output, and dumps for the Systems Programmer to aid in problem determination. If the error persists, take a DYNCAT BACKUP of the Catalog file before beginning any other error correction measures. See "Catalog Management Return Codes" for more information.

CADC552E — CA-DYNAM CONTROL PHASE CANNOT BE LOCATED

Reason:

An unexpected error occurred while trying to access the CA-Dynam product control phase. The job will be terminated by a dump.

Action:


CADC553E — INSUFFICIENT STORAGE AVAILABLE TO CONTINUE

Reason:

There is not enough storage for TDYNSYNC to continue. The job will be terminated.

Action:


Messages 2–77


CADC554E — TDYNSYNC CONTROL STATEMENT INVALID

Reason:

The operation code or a parameter on the control statement is invalid. If TDYNSYNC was executed through the system console, you will be prompted to enter the next TDYNSYNC command; otherwise the job will be terminated.

Action:

Correct the control statement and reexecute the function.

CADC555E — ERROR OPENING DTFNAME R15=xx

Reason:

The OPEN failed for the specified DTFNAME. R15 contains the return code. The job will be terminated with a dump.

Action:

See the System Adapter return codes for further information or action. If a solution cannot be determined, then retain the console log, SYSLST output, and dumps for the Systems Programmer to aid in problem determination. If the error persists, take a DYNCAT BACKUP of the Catalog file before beginning any other error correction measures. See "Catalog Management Return Codes" in the "Codes" chapter for more information.

CADC556E — VOLUME VOLSER, PROBLEM REASON=r

Reason:

An unexpected error occurred while processing the volser contained in the message. The job will continue.

Action:




CADC557E — DYNAM/T CONTROL PHASE CAN'T BE LOCATED

Reason:

An unexpected error occurred while trying to access the CA-Dynam/T product control phase. The job will terminate with a dump.

Action:


CADC558E — XSYSTEM CONTROL PHASE CAN'T BE LOCATED

Reason:

An unexpected error occurred while trying to access the CA-Dynam/T XSYSTEM control phase. The job will terminate with a dump.

Action:


CADC559E — ERROR LOADING PHASE UTILSLT0 R15=xx. R15 CONTAINS THE RETURN CODE

Reason:

An unexpected error occurred while trying to load phase UTILSLT0. The job will terminate with a dump.

Action:


Messages 2–79


CADC560E — UNEXPECTED ERROR UTILSLT0 R15=xx SSLERRCS=xx. R15 CONTAINS THE RETURN CODE.

Reason:

SSLERRCS contains the specific return code as determined by UTILSLT0. The job will terminate with a dump.

Action:


CADC561E — OBTAIN FUNCTION FAILED

Reason:

Unexpected error was returned by the system adapter OBTAIN function. The job will terminate with a dump.

Action:


CADC562E — SRAM ERROR OCCURRED R15=xx. R15 CONTAINS THE RETURN CODE

Reason:

Unexpected error was returned by a CA-SRAM function. The job will terminate with a dump.

Action:




CADC601E — SYNTAX ERROR

Reason:

The command processed contains a syntax error.

Action:

Correct the command and press Enter.

CADC602E — INVALID COMMAND

Reason:

The command processed is not valid.

Action:

Enter a valid command and press Enter.

CADC603E — INVALID OPERAND

Reason:

The operand processed is not valid.

Action:

Enter a valid operand and press Enter.

CADC604E — INVALID SHORTFORM COMMAND

Reason:

The short command is not defined to the system.

Action:

Enter a valid short command and press Enter.

Messages 2–81


CADC605E — INVALID RELATION

Reason:

The specified relational operator is not valid.

Action:

Enter a valid relational operator.

CADC606E — INVALID DATA SPECIFIED

Reason:

The fields with invalid data are displayed in high intensity.

Action:

Correct the field(s) in error.

CADC607I — RECORD SUCCESSFULLY UPDATED

Reason:

The record has been successfully updated.

Action:

None.

CADC608E — OPERAND nn IS INVALID

Reason:

Operand nn is not valid.

Action:

Enter a valid operand and press Enter.

CADC609I — TAPE VOLSER NOT FOUND

Reason:

The volser of the tape you requested cannot be found.



Action:

Enter a valid volser and press Enter.

CADC610I — TOP OF FILE

Reason:

The top of the display has been reached.

Action:

None.

CADC611I — END OF FILE

Reason:

The end of the display has been reached.

Action:

None.

CADC612I — TOP/END OF FILE

Reason:

The top of the display has been reached, and there are no more records to display.

Action:

None.

CADC613I — DATA SET NOT FOUND

Reason:

The data set name processed is not valid.

Action:

Enter a valid data set name and press Enter.

Messages 2–83


CADC614I — DATA SET VERSION NOT FOUND

Reason:

The data set version you requested was not found.

Action:

Enter a different version number and press Enter.

CADC616E — UPDATE FAILED - OPTION RECORD UPDATED SINCE LAST BEING READ

Reason:

The CAICUI record has been updated since the CUI online transaction was entered.

Action:

EXIT the CUI transaction and reestablish a new CUI session.

CADC621E — DELETE FAILED

Reason:

The data set has not been deleted.

Action:

Verify that the data set is still in the CA-Dynam catalog and retry. If the problem persists, contact Computer Associates Technical Support.

CADC622E — INSUFFICIENT PARTITION GETVIS TO PERFORM CATALOG I/O

Reason:

Catalog Management functions require partition GETVIS.

Action:

Increase the partition GETVIS allocation for Catalog Management. If the problem persists, contact Computer Associates Technical Support.



CADC623E — CA-DYNAM CATALOG NOT FOUND

Reason:

CA-Dynam could not find the catalog.

Action:

Verify that the DTF name for the catalog matches the information contained in your standard labels. Also, check to make sure that the catalog is permanently assigned in the partition.

CADC624E — CA-DYNAM CATALOG I/O ERR xxxx

Reason:

CA-Dynam could not perform the requested function.

Action:


CADC625E — CA VSE SYSTEM ADAPTER UNAVAILABLE

Reason:

The System Adapter is not active.

Action:

Activate the System Adapter.

CADC626E — SERVICE NUCLEUS ERROR xxxx

Reason:

The service nucleus was not able to process the function xxxx.

Action:

Check the other error messages to determine the problem and retry the function call. If the problem persists, contact Computer Associates Technical Support.

Messages 2–85


CADC630E — UPDATE FAILED

Reason:

The update cannot be processed at this time because an invalid object name or invalid data was entered.

Action:

Correct the invalid data and retry the function call.

CADC631E — CPUID/CLASS OR PARTITION MUST BE FOLLOWED BY A COMMA OR BLANK

Reason:

The programs parsing routine expects cpu-id and class to be one character, and partition id's to be two characters, followed by either a comma or a blank.

Action:

Correct the error and press Enter.

CADC632E — VALID CPU-ID's ARE A-Z and 0-9

Reason:

A cpu-id was entered that is not in specified ranges.

Action:


CADC633E — VALID CLASSES ARE C,D,E AND G-Z

Reason:

A class parameter was entered that is not a valid class as indicated in the message.

Action:




CADC634E — RECORD LENGTH EXCEEDS MAXIMUM SIZE

Reason:

An attempt was made to add a record to the CAICUI VSAM database that exceeded the maximum size allowed.

Action:

Contacts Computer Associates technical support

CADC635E — STARTING LUB CANNOT EXCEED ENDING LUB

Reason:

A lub range was entered with a starting lub number that was greater than the ending lub number entered for that lub pair.

Action:


CADC636E — VOLSER MUST BE 6 NON-BLANK CHARACTERS

Reason:

A volser was entered that contained blank characters.

Action:


CADC650I — CA-DYNAM FUNCTION INITIALIZATION IN PROGRESS

Reason:

The CA-Dynam online initialization has commenced.

Action:

None.

Messages 2–87


CADC651I — CA-DYNAM FUNCTION INITIALIZATION COMPLETE

Reason:

The CA-Dynam initialization process has successfully completed.

Action:

None.

CADC652E — CAICUI XFCS IS NOT ACTIVE

Reason:

The XFCS subtask was not properly activated.

Action:

Refer to the previous return code and error messages to determine the probable cause and correct the condition. If the problem persists, contact Computer Associates Technical Support.

CADC653E — CA-DYNAM CAYDUTLO FUNCTION ATTACH FAILED

Reason:

The CAYDUTLO function was not successfully attached.

Action:

Refer to the previous return code and error messages to determine the probable cause and correct the conditions that caused the attach to fail.

CADC654E — CA-DYNAM CAYDSERV FUNCTION ATTACH FAILED

Reason:

The CAYDSERV function was not successfully attached.

Action:

Refer to the previous return code and error messages to determine the probable cause and correct the conditions that caused the attach to fail.



CADC655E — CA-DYNAM FUNCTION INITIALIZATION FAILED

Reason:

The CA-Dynam initialization failed.

Action:

Refer to the previous return code and error messages to determine the probable cause and retry the initialization process. If the problem persists, contact Computer Associates Technical Support.

CADC670I — CA-DYNAM FUNCTION SHUTDOWN IN PROGRESS

Reason:

The CA-Dynam shut down has begun.

Action:

None.

CADC671I — CA-DYNAM FUNCTION SHUTDOWN COMPLETE

Reason:

The CA-Dynam shut down process was successful.

Action:

None.

CADC672I — CA-DYNAM FUNCTION SHUTDOWN FAILED

Reason:

The CA-Dynam shut down abended.

Action:

Refer to the previous return code and error messages to determine the problem, and and rerun the job. If the problem persists, contact Computer Associates Technical Support.

Messages 2–89


CADC681E — CAICUI DATA SET NOT AVAILABLE

Reason:

The CAICUI option data set is not available.

Action:

Verify that the system meets installation requirements.

CADC682E — WARNING --- READ-ONLY DATA SET

Reason:

The CAICUI option data set is not available for update.

Action:

Check your security authorization or whether the system meets installation requirements.

CADC683E — WARNING --- INCORE OPTION RECORD UPDATE FAILED

Reason:

The requested option record was not found in the system shared virtual area.

Action:

Verify that the system has been successfully initialized.

CADC685W — RECORD SUCCESSFULLY UPDATED - WARNING -- AUDIT LOG FAILED

Reason:

A record update completed successfully, but attempts to log the update as a CAICUI event failed.

Action:

Make sure that CAIAUDIT was successfully initialized. If the problem persists, contact Computer Associates Technical Support.



CADC686E — WARNING --- INCORE OPTION RECORD NOT FOUND

Reason:

The requested option record was not found in the system's shared virtual area.

Action:

Make sure the system was successfully initialized. If the problem persists, contact Computer Associates Technical Support.

CADC687E — WARNING --- AUDIT LOG EVENT FAILED

Reason:

An unsuccessful attempt has been made to have CAIAUDIT log a CAIAUDIT event.

Action:

Make sure that CAIAUDIT was successfully initialized. If the problem persists, contact Computer Associates Technical Support.

CADC688E — PHASE NOT FOUND - xxxxxxxx

Reason:

A phase was unable to be located in the library search chain.

Action:

Check the library search chain for the sublibrary containing the phase name in the message.

CADC689W — RECORD ALREADY EXISTS, PRESS PF9 TO REWRITE, CLEAR TO CANCEL

Reason:

User has requested that a given record is to be copied as a different record with a new key. The key of the new record it is to be copied as already exists on the file.

Action:

If you want to REPLACE the old, existing record - Press PF9 If you DO NOT - Press CLEAR to cancel this request

Messages 2–91


CADC690E — UNABLE TO COPY RECORD TO CUI DATABASE

Reason:

An error occurred trying to copy a record

Action:

Check that the vsam database is available and able to be written to.

CADC691I — RECORD SUCCESSFULLY ADDED

Reason:

The record has been successfully added.

Action:

None.

CADC692I — RECORD SUCCESSFULLY DELETED

Reason:

The requested record was deleted from the file

Action:

None

CADC693E — UNABLE TO DELETE RECORD FROM CUI DATABASE

Reason:

An error occurred trying to delete a record

Action:

Check that the vsam database is available and able to be written to.



CADC694E — DELETE FOR SYSTEM DEFAULT RECORD IS NOT ALLOWED

Reason:

User was trying to delete a System Default record (cpuid=*) and this action is not permitted.

Action:

None

CADC800D — ENTER DYNCAT COMMAND

Reason:

The DYNCAT program has been initiated from the console and the program is requesting control statement input.

Action:

Enter a valid control statement.

CADC801E — CONTROL STATEMENT ERROR HAS OCCURRED *SEE PRINTER*

Reason:

An error has been detected with a control statement.

Action:

From the printer listing, determine the error. Correct it and rerun the catalog function.

CADC802E — CONTROL STATEMENT INVALID, STATEMENT BYPASSED

Reason:

One or more of the parameters in the control statement are not valid.

Action:


Messages 2–93


CADC803E — INSUFFICIENT AREA IN CATALOG FILE, STATEMENT BYPASSED

Reason:

There is no more room in the Catalog to catalog additional files.

Action:

Use the BACKUP function to dump the Catalog to tape. Restore it to larger EXTENTs with the RESTORE REORG function. Reexecute the function.

CADC804E — DATA SET NAME ALREADY IN CATALOG, STATEMENT BYPASSED

Reason:

The data set being cataloged already exists in the Catalog.

Action:

If the proper data set is already cataloged, this statement can be ignored. If the wrong data set name was specified in the control statement, correct it and reexecute the function.

CADC805E — DATA SET NAME NOT IN CATALOG, STATEMENT BYPASSED

Reason:

An operation is being specified for a data set that does not exist in the Catalog.

Action:


CADC806E — SPECIFIED VERSION OR VOLUME SERIAL IS NOT FOUND

Reason:

The version number specified is not defined in the Catalog for this data set. If this message occurs during:

■ DYNCAT ADD APPEND, you may be attempting to append a volume to an open/not closed version.

■ DYNCAT DELETE, you may be trying to delete a volume which is a protected open/not closed version, or one which has been previously deleted.



Action:


CADC807E — nnn PARAMETER IN CONTROL STATEMENT INVALID, STATEMENT BYPASSED

Reason:

The specified parameter in the control statement is invalid.

Action:


CADC808E — SYSTEM NUMBER INVALID, STATEMENT BYPASSED

Reason:

The logical unit number specified is invalid.

Action:

Correct the statement and restart.

CADC809E — UNIT IS DEVICED DOWN, STATEMENT BYPASSED

Reason:

The INT or INTR command has been issued to a tape drive which is currently VARYed offline.

Action:

Either enter the &VARY. online command to the tape drive in question and then rerun DYNCAT or specify a different tape drive.

CADC810E — INVALID DEVICE TYPE, STATEMENT BYPASSED

Reason:

The cuu specified in the INT or INTR command is not the channel and unit number of a tape drive.

Action:

Correct the control statement and resubmit.

Messages 2–95


CADC811E — TAPE UNIT UNAVAILABLE, STATEMENT BYPASSED

Reason:

The channel and unit address specified in the INT or INTR command is not currently available for use in this partition.

Action:

Resubmit the command, specifying a different tape drive.

CADC812E — CA-DYNAM/T CONTROL PHASE NOT PRESENT

Reason:

CATAGENA, the CA-Dynam/T control phase, is not present.

Action:

Contact the Systems Programmer for assistance. The control phrase must be assembled, cataloged to the system core image library, and then loaded before the product may be made active.

CADC814E — volser ALREADY IN FILE AS 'data-set-name'

volser ALREADY IN FILE AS EXTERNALLY OWNED

volser ALREADY IN FILE AS SCRATCH

Reason:

The first form of the message is issued if an attempt is made to add or initialize a volume serial number which is already associated with an active data set.

The second form is issued if an attempt is made to add a volume serial number which is already in the Catalog and is owned by another product.

The third form is issued if an attempt is made to reinitialize a tape which is already in the file as a SCRATCH tape, that is, potentially creating two physical volumes with the same number.

Action:

No response is permitted to the first and second forms of the message.

In response to the third message, verify the reel number to be added. If the volume is a scratch tape which is to be reinitialized, reply 'ACCEPT'.



CADC815E — VOLUME NO xxxxxx ALREADY IN FILE, STATEMENT BYPASSED

Reason:

The user is attempting to add a duplicate reel number, which is not allowed.

This message will also result if one and two are true, or three or four is true:

1. The INT function is being performed the mounted volume is already a controlled volume

2. The user has responded with something other than "ACCEPT" to a CADT010D or CADC814E message

3. The volume is externally owned

Action:

None. The statement is ignored.

CADC816E — PRIOR FILE (PF) NOT IN CATALOG, STATEMENT BYPASSED

Reason:

The prior file name specified when cataloging a multi-file data set is not in the catalog file.

Action:

None.

CADC817E — PRIOR FILE (PF) IS NOT THE LAST FILE OF A MULTI-FILE VOLUME - STATEMENT BYPASSED

Reason:

The prior file name specified in a multi-file catalog statement is not the last one for the multi-file set. Multi-file sets must be cataloged in sequence.

Action:

None.

Messages 2–97


CADC818E — VOLUME xxxxxx NOT A SCRATCH TAPE OR NOT IN CATALOG

Reason:

The volume serial number specified in the DELETE or INT(R) statement is not a scratch tape, or not in the catalog file, or is externally owned.

Action:

None.

CADC819E — INVALID FUNCTION FOR MULTI-FILE VOLUME

Reason:

This operation is not valid for other than the first file of a multi-file volume or set of volumes.

Action:

None.

CADC820E — INVALID ADD APPEND STATEMENT

Reason:

You cannot add tape volumes to a disk version, or disk volumes to a tape version. The only valid options with APPEND are DISK and VERSION.

Action:

Check the ADD statement. You must code 'DISK' if appending to a disk version or 'TAPE' is assumed. Check the version in the Catalog to see what type it is. Correct the statement and resubmit.

CADC821I — cuu volser INITIALIZED

Reason:

The specified volume serial number has been initialized on the indicated tape drive.

Action:

None.



CADC822I — DYNCAT BEGIN

Reason:

The DYNCAT program has been executed from SYSRDR.

Action:

None.

CADC823I — DYNCAT END

Reason:

The DYNCAT program is ending.

Action:

None.

CADC824E — VAULT LOCATION NOT ALPHA, STATEMENT BYPASSED

Reason:

The VAULT parameter of the DYNCAT control statement contains an invalid vault ID. Only the alphabetic characters A through Z are valid.

Action:

Correct the parameter and rerun.

CADC825I — DATA SET HAS VAULT CONTROL DSN=data-set-name.

Reason:

A data set with vault control is being deleted.

Action:

None. The operation is completed; however, it is the user's responsibility to return the necessary volumes to the main tape library (Vault A). Note that no TDYNVLT MOVEMENT reports will be produced.

Messages 2–99


CADC826I — VAULT-CONTROLLED DSN=data-set-name, VLT=vault

Reason:

A version with vault control in a vault other than "A" is being deleted.

Action:

None. The operation is completed; however, it is the user's responsibility to return the necessary volumes to the main tape library (Vault A). Note that no TDYNVLT MOVEMENT reports will be produced.

CADC827E — INVALID FUNCTION FOR WORK DATA SET

Reason:

The object data set is a work data set, and the indicated function cannot be performed. A work data set is not allowed to be defined with retention information (NGEN, RETAIN, PEDCYC).

Action:

None. The statement is bypassed.

CADC828E — DATASET NAME DOES NOT CONFORM TO OS NAMING CONVENTIONS

Reason:

An attempt was made to add a data set name to the Catalog, but the data set name does not conform to VSAM or OS/MVS naming conventions.

Action:

Correct the data set name and resubmit.

CADC829E — INVALID DSN FOR MF=AUTO OR MF=RESET

Reason:

A DEFINE or ALTER function is being performed on an AMF data set, but the required three asterisks (***) were not found in the DSN. The statement is bypassed.

Action:

Supply the DSN with the three asterisks in the correct positions.



CADC830E — INVALID DSN OR EXTOWNER

Reason:

The DSN in an ADD statement for an externally owned volume must be less than or equal to 17 characters. EXTOWNER may only be 0-9, A-Z, and must be a valid NODEID as defined by the XSYSTEM macro. No ADD options may be used when defining an externally owned volume.

Action:

Correct the DSN and rerun the DYNCAT command.

CADC831E — VOLUME STATUS INVALID FOR SCRATCH

Reason:

The SCR function is being performed on a tape that is an active data set. This function can be performed only on tapes in L, T, D, O, or S status.

Action:

None.

CADC832E — FUNCTION INVALID - DATA SET LOCKED

Reason:

An ALTER function is being performed, and either the data set is locked for output or version one is locked for input.

Action:

In order to perform the ALTER function, the data set must first be unlocked.

CADC833E — DATA SET NOT MF=AUTO DSN

Reason:

The ALTER function is being performed with an MF parameter, but this data set name was not cataloged as MF=AUTO.

Action:

Correct the data set name or delete and recatalog it with MF=AUTO.

Messages 2–101


CADC834E — OVERFLOW ON MF=AUTO DATA SET

Reason:

An ALTER 'DSN', MF=NEW statement is being processed, but the maximum number of data sets already exists for this AMF set of DSNs.

Action:

Manual maintenance must be performed to remove some of the AMF data sets from the catalog file.

CADC835E — VOLSER xxxxxx INVALID, STATEMENT BYPASSED

Reason:

The volume serial number for this INT or INTR function is not valid because either it

■ Does not contain at least one character greater than zero,

■ Contains special characters, or

■ If the installation option was chosen, is not numeric.

Action:

Correct the volume serial number and reprocess the command.

CADC836E — PHYSICAL I/O ERROR OCCURRED CSW=xxxxxxxx

Reason:

An I/O error has occurred. The CSW status is displayed.

Action:

None.



CADC837E — INSUFFICIENT STORAGE

Reason:

Insufficient storage has been reserved for the processing of the command.

Action:

Rerun the job, reserving additional program and/or partition and system GETVIS storage.

CADC838E — CATALOG IS FULL

Reason:

The Catalog is full.

Action:

Either the DYNCAT SCRATCH function or, for temporary relief, the DYNCAT BACKUP and RESTORE REORG may be run to free additional areas in the Catalog.

If the problem persists, the catalog extents must be enlarged and the Catalog must be backed up, reinitialized, and restored to enlarge it.

CADC839E — ADDING OUT OF SEQUENCE FOR A MULTI-FILE DATASET

Reason:

An ADD command which would result in a file being added out of sequence has been entered for a member of a multi-file data set. ADD commands must be processed in order by file sequence for multi-file data sets.

Action:

Correct the sequence of the ADD commands and resubmit.

CADC840E — PASSWORD IS INVALID OR MISSING, STATEMENT BYPASSED

Reason:

An attempt has been made to process a password-protected data set, but the password submitted is either incorrect or has been omitted.

Messages 2–103


Action:

Provide the correct password and resubmit.

CADC841E — DSN IS NOT DEFINED AS A TAPE DATASET

Reason:

An attempt has been made to process a data set which exists in the Catalog as a non-tape data set using the CA-Dynam/T tape data set utility. The data set is not eligible for processing.

Action:


CADC842E — INVALID UNIT STATUS

CADC842E — FILE PROTECT

CADC842E — INTR REQ'D

CADC842E — DRIVE IS NOT READY

CADC842E — SEVEN TRACK TAPE

Reason:

An error has been detected while attempting to access the tape drive. The message text indicates the specific cause of the error.

Action:

Correct the condition which caused the error, or select another tape drive and resubmit the command.

CADC843E — cuu INVALID DENSITY

Reason:

Either the tape drive indicated is not capable of writing the desired density, or the specified density is not valid.



Action:

Choose another tape drive or another density.

CADC844E — UNEXPECTED RETURN CODE FROM CATALOG

Reason:

An internal Catalog Management error has been detected.

Action:

Collect as much documentation as possible. If the problem persists, it may be cleared by IPLing the system and performing a DYNCAT BACKUP and RESTORE REORG on the Catalog.

CADC845E — volser IS NOT IN THE CATALOG AS data-set-name.

Reason:

The indicated volume serial number is not in the Catalog as the indicated DSN. The error was detected during the scratch function.

Action:

Review the data set name and volume serial number listings. Perform manual maintenance to correct the problem or correct the control statement and resubmit.

CADC847E — NO AMF DATA SET OR VERSIONS TO RENAME, STATEMENT BYPASSED

Reason:

This is from the RENAME request. The data set name is not in the Catalog. There is no data set or version in the Catalog to rename. To use the MF=RESET function, there must be at least one automatic multi-file (AMF) data set. The statement is bypassed.

Action:

Correct the input and resubmit.

Messages 2–105


CADC848E — INVALID LOGICAL UNIT SPECIFIED

Reason:

There is an invalid logical unit specified. The logical unit specified must be in the range SYS000-SYS254.

Action:


CADC849E — INVALID OPTION CODE SPECIFIED

Reason:

TAPEOPT or DISKOPT contains an invalid value.

Action:

See the User Guide for valid values. Correct the input and resubmit.

CADC850E — INVALID RANGE SPECIFIED

Reason:

A numeric value specified in a parameter is invalid. Most likely the BLKSZ, LRECL or NEXTGEN value is invalid. For BLKSZ or LRECL, 1 to 32767 is valid; for NEXTGEN, 1 to 99 is valid.

Action:


CADC851E — MISSING A REQUIRED PARAMETER

Reason:

A required parameter is missing. The ALLOC parameter requires at least a primary allocation amount to be specified. An absolute extent (PRIME, etc.) also requires secondary allocation to be specified.

Action:




CADC852E — DELETION NOT PERFORMED

Reason:

The requested deletion was not performed.

Action:


CADC853E — INVALID NGEN SPECIFIED

Reason:

An invalid NGEN was specified. The NGEN parameter may be only 1-98 for disk data sets and 1-255 for tape data sets.

Action:


CADC854E — NUMBER OF SECONDARY ALLOCATIONS CANNOT BE SPECIFIED WITH AN ABSOLUTE EXTENT

Reason:

You cannot specify the number of secondary allocations with an absolute extent.

Action:


CADC855E — EXTENT TYPE OR NUMBER IS NOT VALID FOR THIS DATASET

Reason:

The extent type or number is not valid for this data set.

Action:


Messages 2–107


CADC856E — GENERATION IS STILL ACTIVE, ALTER NOT PERFORMED

Reason:

Disk data set generation alteration cannot be performed if the ALTER would result in duplication of generation numbers in the VTOC.

Action:

Use DYNUTIL to delete the conflicting version from disk, and use the DYNCAT DELETE function to delete the conflicting catalog version.

CADC857E — INVALID GDSID SPECIFIED

Reason:

There is an invalid GDSID. Valid disk generation data sets range from 1-99.

Action:


CADC858E — SKNAME ALREADY IN CATALOG, STATEMENT BYPASSED

Reason:

The SKNAME is already in the Catalog.

Action:


CADC859E — SKNAME IS NOT IN CATALOG, STATEMENT BYPASSED

Reason:

The SKNAME is not in the Catalog.

Action:




CADC860E — FIELDS PARAMETER IS INCORRECT, STATEMENT BYPASSED

Reason:

The FIELDS parameter is not correct.

Action:

See the User Guide for valid format. Correct the input and resubmit.

CADC861E — NO FIELDS PARAMETER GIVEN, STATEMENT BYPASSED

Reason:

The FIELDS parameter is required for SKNAME.

Action:


CADC862E — RECFM MUST HAVE A VALUE OF V OR F FOR A SORT KEY DEFINITION

Reason:

Use V or F for RECFM for sort key definition.

Action:

See the User Guide for SKR definitions. Correct the input and resubmit.

CADC863E — CANNOT ALTER FORMAT WITHOUT SPECIFYING FIELDS PARAMETER

Reason:

FIELDS parameter was not specified.

Action:


Messages 2–109


CADC864E — NO DEFAULT FORMAT OR SPECIFIC FORMAT WAS SPECIFIED

Reason:

No specific or default format was specified.

Action:


CADC865E — NO SORTING SEQUENCE SPECIFIED

Reason:

Sort sequence is required.

Action:


CADC866E — A FIELD LENGTH IN FIELDS PARAMETER IS INVALID

Reason:

A field length in FIELDS parameter is invalid.

Action:


CADC867E — RELEASE CAN ONLY BE SPECIFIED FOR A WORK DATASET

Reason:

RELEASE can only be specified for a work data set.

Action:




CADC868E — FIELDS CAN ONLY BE SPECIFIED WHEN DEFINING OR ALTERING A SORT KEY RECORD

Reason:

FIELDS can only be specified when defining or altering a sort key record.

Action:


CADC869E — MUST SPECIFY EXTENT SEQUENCE NUMBER

Reason:

You did not specify an extent sequence number.

Action:


CADC871E — GDSID MUST BE SPECIFIED

Reason:

You did not specify GDSID.

Action:


CADC872 — INVALID VAULT SLOT NUMBER SPECIFIED

Reason:

The first slot number is greater than or equal to the second slot number.

Action:


Messages 2–111


CADC873 — VAULT SLOT NUMBER ALREADY EXISTS

Reason:

An attempt has been made to define a slot number which already exists.

Action:


CADC874 — VAULT SLOT NUMBER NOT FOUND

Reason:

An attempt has been made to delete a slot number which does not exist.

Action:


CADC875 — CANNOT SPECIFY SLOTS FOR VAULT A

Reason:

You cannot specify slots for vault A.

Action:


CADC876 — INVALID PARAMETERS FOR A MF DSN

Reason:

AUTOSCR, ROTATE and NOLABEL are invalid TAPEOPT parameters for a multi-file data set.

Action:




CADC877 — INVALID VOLUME STATUS FOR SCRATCH-YES/NO PARAMETER

Reason:

The ALTER command for a volser was issued with the SCRATCH operand, and the volser either was not in scratch status or was active and connected to a data set.

Action:


CADC878 — MACC ERROR HAS OCCURRED - FUNCTION=xxxx RTC=nnn

Reason:

An unexpected error was received while accessing the CAIMACC communication file.

Action:

Contact Computer Associates Technical Support. See "Catalog Management Return Codes" for more information.

CADC879I — NO SUBSTITUTIONS ARE MADE FOR PARTITION- OR CPU-INDEPENDENT DSNS

Reason:

A data set name was coded with CPU- or partition-independent characters.

Action:

None.

CADC881E — VERSION IS IN A PERMANENT VAULT - MUST SPECIFY PERMVLT=YES TO DELETE

Reason:

An attempt to delete a version with PERM=YES specified.

Action:

To delete the version, specify PERMVLT=YES on the DELETE command.

Messages 2–113


CADC882E — ADDING VERSION OUT OF SEQUENCE

Reason:

An attempt was made to add a version to a data set which would leave a gap in the version number sequence.

Action:


CADC883W — SYSTEM ADAPTER ERROR OCCURRED FN=........,R/C=nnnnnnnn

Reason:

A Dyncat DELETE with the PURGE operand returned an error from a SYSTEM ADAPTER function.

Action:

Note the function name and return codes. Contact Computer Associates Technical Support with this information for further assistance.

CADC884W — UNABLE TO DELETE DISK FILE DSN=dsn

Reason:

A Dyncat DELETE with the PURGE operand was unable to delete a version from a disk volume. This message will follow the CADC883W message above.

Action:

Check the function name and return codes from the CADC883W message which proceeds it. Contact Computer Associates if more information is needed.

CADC885W — DISK FILE NOT FOUND, VOL=volser,DSN=dsn

Reason:

A Dyncat DELETE with the PURGE operand was unable to locate and scratch a file on disk. The catalog version records pointed to a disk volume as the location of the actual disk file but the VTOC scratch function was unable to find it.



Action:

Run a VTOC report to see if the file is on that disk pack. This could happen if a file has been scratched from a disk volume BEFORE a Dyncat DELETE with PURGE has been run or if a file has been moved by a utility program that did not update the catalog with the new location.

CADC886W — cuu INVALID DENSITY

CADC886W — cuu INVALID DEVICE TYPE

CADC886W — cuu DEVICED DOWN

CADC886W — cuu UNAVAILABLE

Reason:

This message specifies one of the following problems with the device requested:

■ The device is not available

■ The device is not capable of writing the desired density

■ The specified density is not valid

Action:

Choose another tape drive or another density.

CADC887D — ENTER 'RETRY', 'NEXT', or 'END'

Reason:

One of the problems reported in message CADC886W (device availablity or compatiblity with density specified associated with initialization of multiple tape drives) has occurred.

Action:

Enter RETRY to start the function again, NEXT to try initializing the next drive in the list, or END to cancel the function.

Messages 2–115


CADC888E — EXTERNAL SECURITY VIOLATION DSN=dsn

Reason:

External security (like CA-Top Secret) is installed and active, and a request for a DYNCAT command has been issued which violates defined security restrictions. The job will be canceled.

Action:

Either resubmit the job with an ID statement for an authorized user, or contact the Security Administrator.

CADC890D — ENTER DYNCOPY COMMAND

Reason:

The DYNCOPY program has been initiated from the console and the program is requesting control statement input.

Action:

Enter the appropriate command.

CADC891I — PARAMETER CARD=

Reason:

The parameter card listed in the message has been processed.

Action:

None.

CADC892E — PARAMETER CARD ERROR

Reason:

There was an error with the parameter card displayed in message CADC891I.

Action:

Reissue the command with appropriate parameter specified.



CADC893I — BLOCKS READ nnnnn RECORDS READ nnnnnn RECORDS PRINTED nnnnn

Reason:

Indicates the number of blocks and records read and the number of records printed by DYNCOPY.

Action:

None.

CADC894E — DYNCOPY ERROR - FUNCTION=

Reason:

An error has occurred during DYNCOPY processing

Action:


CADC895E — NO LABEL FOUND FOR DTFNAME=

Reason:

A valid TLBL or DLBL is missing for either the input or output file.

Action:

Reenter DYNCOPY with an appropriate DTFname or supply an appropriate TLBL or DLBL..

CADC896E — NO RECFM SPECIFIED

Reason:

The RECFM parameter is required on selective copies.

Action:

Reissue the command with a RECFM parameter specified.

Messages 2–117


CADC897I — TOTAL BLOCKS COPIED nnnnn

Reason:

This is an informational message indicating the number of blocks copied on a DYNCOPY command.

Action:

None.

CADC898E — DUMP AND SEL BOTH SPECIFIED

Reason:

DUMP and SEL parameters cannot be specified together on the same DYNCOPY command.

Action:

Reissue the command with only one of these parameters.

CADC899E — BLKSIZE/LRECL INVALID OR MISSING

Reason:

An incorrect block or logical record size was entered or none was specified on the DYNCOPY utility.

Action:

Reissue the command with a correct BLKSIZE or LRECL value.

CADC900 — UNEXPECTED END OF FILE ON INPUT

Reason:

DYNCAT expected to encounter a continuation statement and instead encountered an end-of-file condition.

Action:

Check the commands submitted to the DYNCAT program and ensure that all required commands and operands are supplied.



CADC901 — TOO MANY CONTINUATION STATEMENTS

Reason:

A maximum of ten continuation statements is allowed by DYNCAT.

Action:


CADC902 — UNRECOGNIZABLE COMMAND

Reason:

DYNCAT found an invalid command.

Action:

See the DYNCAT command descriptions in the User Guide.

CADC903 — REQUIRED OPERAND(S) OMITTED

Reason:

A required operand has been omitted.

Action:

Refer to the specific command description in the CA-Dynam User Guide.

CADC904 — INVALID KEYWORD OPERAND

Reason:

DYNCAT found an invalid keyword specified for the command being processed.

Action:


Messages 2–119


CADC905 — UNRECOGNIZABLE KEYWORD OPERAND

Reason:

There is an unrecognizable keyword operand.

Action:


CADC906 — TOO MANY REPEATS OF KEYWORD OPERAND

Reason:

There are too many repeats of a keyword operand.

Action:


CADC907 — TOO MANY POSITIONAL OPERANDS

Reason:

DYNCAT found too many operands on the command being processed.

Action:


CADC908 — TOO MANY SUBOPERANDS

Reason:

Too many sub operands were supplied in a list enclosed in parentheses.

Action:




CADC909 — SYNTAX ERROR - UNPAIRED PARENTHESES

Reason:

A parenthesis is missing for the command being processed.

Action:


CADC910 — SYNTAX ERROR - UNPAIRED APOSTROPHES

Reason:

An apostrophe is missing for the command being processed.

Action:


CADC911 — INVALID SEPARATOR ENCOUNTERED

Reason:

DYNCAT found an invalid separator for the command being processed. Blanks must be used.

Action:


CADC912 — STRING MUST BE IN APOSTROPHES

Reason:

The string must be in apostrophes.

Action:


Messages 2–121


CADC913 — STRING CANNOT BE IN APOSTROPHES

Reason:

The string cannot be in apostrophes.

Action:


CADC914 — INVALID NUMERIC VALUE

Reason:

DYNCAT did not find a numeric value for the operand being processed.

Action:


CADC915 — INVALID OR UNRECOGNIZABLE VALUE

Reason:

A supplied keyword is invalid.

Action:


CADC916 — VALUE IS TOO LONG

Reason:

A supplied character string or keyword is too long.

Action:




CADC917 — VALUE TOO LONG - TRUNCATED

Reason:

A supplied character string or keyword is too long and has been truncated.

Action:


CADC950I — LABEL DSN=' '

Reason:

A TLBL or DLBL with CA-Dynam options, within the data set name, was encountered by the CA-Dynam Job Exit. The data set name specified is the full DSN prior to the stripping out of options.

Action:

None.

CADC951E — UNABLE TO LOAD/LOCATE xxxxxxxx

Reason:

Phase xxxxxxxx of the CA-Dynam Job Exit could not be found or loaded.

Action:

Check LIBDEFs for the partition in which the job was run to insure that the CA-Dynam library is accessible.

CADC952E — GETVIS HAS FAILED

Reason:

Issued by CADCPSTA during post-initialization for CA-Dynam products. A request for storage from System, Dynamic or Partition GETVIS failed.

Action:

Ensure GETVIS storage is available for allocation and reinitialize the CA-Dynam product(s). If the problem recurs save output and contact Computer Associates Technical Support.

Messages 2–123


CADC953E — LOAD FOR PRODUCT CVT PHASE CADCPCVT FAILED.

Reason:

Issued by CADCPSTA during post-initialization for CA-Dynam products. The load for the CA-Dynam Product Communication Vector Table phase failed.

Action:

Ensure that the library containing this phase (included with the product on the installation library) is in the LIBDEF search chain at CASAUTIL execution and reinitialize.

CADC954E — CAISLA CONNECT FAILED, R/C=X'xx'.

Reason:

Issued by CADCPSTA during post-initialization for CA-Dynam products. An attempt to connect to the Computer Associates Symbolic Label Interface failed.

Action:

Retain output and contact Computer Associates Technical Support.

CADC955E — LABEL OPTION CHAIN CORRUPTION DETECTED.

Reason:

Issued by CASALOPA during label option processing for CA-Dynam products. A label option chain corruption error has been detected. This error may occur due to corruption of label option storage in System GETVIS by another program.

Action:

Attempt to identify the circumstances under which the problem occurs with regard to CA-Dynam activity and other recent or concurrent system activity. Obtain a dump of the partition and System GETVIS and contact Computer Associates Technical Support.

CADC956E — ESA FACILITIES FAILURE

Reason:

The product was unable to locate the modules required to support the requested function under VSE/ESA.



Action:

Check the LIBDEFs. If problem persists contact Computer Associates for assistance.

CADC957E — CA-DYNAM/C POST-INITIALIZATION FAILURE F/C=nnnn R/C=nnnn

Reason:

Post-initialization has detected a severe error and will be prematurely terminated. The impact on CA-Dynam processing will vary depending on the error.

Action:

Correct the error and re-IPL.

Function Code Meaning and action to be taken

1 Unable to locate the DYNCOMM information block. Check CAICUI label in standard labels. Initialize the CAICUI dataset for PROD(DYNAMCOM) and re-IPL if the CAICUI label in standard labels is correct.

The return code (R/C) is the System Adapter return code returned in register 15.

CADC958E — DYNPARM ERROR HAS OCCURRED. R/C=nnnn FN=xxxxxxxx

Reason:

The DYNPARM function to get the table generated by the DYNAM option record encountered an error. Consult the System Adapter function and return codes.

Action:


CADC959W — xxxxxxx OPTION RECORD NOT FOUND

Reason:

The DYNPARM function was unable to locate the option record indicated in the message.

Messages 2–125


Action:

Run CACCDBU0 to initialize the appropriate product record on the CUI VSAM file.

CADC960E — LMP FACILITIES UNAVAILABLE

Reason:

The LMP key for one of the Dynam family of products has expired.

Action:

Contact Computer Associates Technical Support to arrange for a new key.

CADC961E — INSUFFICIENT PARTITION STORAGE

Reason:

There is not enough partition getvis for the Dynam VTAPE Job Exit to process the VTAPE command.

Action:

The VTAPE command is passed unmodified to job control.

Make sure there is sufficient partition getvis available to process the VTAPE command.

CADC962E — DATASET NAME NOT FOUND OR INVALID

Reason:

The DSN= parameter was specified on the VTAPE command but the data set name is either invalid or not in the catalog.

Action:

The VTAPE command is passed to job control unmodified. Specify the correct data set name.



CADC963E — VERSION NOT FOUND OR DOES NOT CONTAIN VTAPE INFORMATION

Reason:

The DSN= parameter was specified on the VTAPE command but the specified version does not exist or is not a VTAPE version.

Action:

The VTAPE command is passed to job control unmodified. Specify the correct version.

CADC964E — INVALID VTAPE COMMAND

Reason:

The DSN= parameter was specified on the VTAPE command and one or more of the following conditions was encountered:

UNIT= was not specified

FILE= was specified

LOC= was specified

Action:

The VTAPE command is passed to job control unmodified. Specify a correct VTAPE command.

CADC965E — VTAPE PROCESSING ERROR - DISP=XXXX R/C=XX

Reason:

An internal error was detected by the Dynam VTAPE Job Exit during VTAPE processing.

Action:

The VTAPE command is passed to job control unmodified.

Collect as much diagnostic information as possible and contact Computer Associates Technical Support.

Messages 2–127

CADD Prefixed Messages


CADD001I — ASSIGNED FILE=xxxxxxx SYSnnn=cuu volid

Reason:

The CA-Dynam/D AVR routines have located the correct disk device and have made a temporary assignment to the device address.

Action:

None.

CADD002I — ALLOCATED FILE=xxxxxxx SYSnnn=cuu volid IX=aa/bbbb/cccc(G#nn)

Reason:

Dynamic space allocation has occurred. If the DASD volume has a VTOC index, extent information is preceded by IX; if not, by X. G# is the generation number for generation data sets.

Action:

None.

CADD003I — AUTO-DELETE VOL=volser FILE=xxxxxxx FILE-ID=file-id (G#nn)

Reason:

CA-Dynam/D has deleted one of the following:

■ a file from a VTOC (because either the 'D' or 'X' option code was specified on the user's DLBL card) or

■ a back-level generation (G#nn)

Action:

None.



CADD004A — FILE xxxxxxxxx NOT FOUND, ALL AVAILABLE VOLUMES SEARCHED

CADD004A — FILE xxxxxxxxx NOT FOUND, POOL vvvvvv SEARCHED

CADD004A — FILE xxxxxxxxx NOT FOUND, ALL GENERIC VOLUMES vvvvvv SEARCHED

CADD004A — FILE xxxxxxxxx NOT FOUND, VOLUME vvvvvv SEARCHED

Reason:

CA-Dynam/D was unable to locate the specified input file after searching the volume(s) or pool displayed in the message. Note that if DASDAVR was generated at installation, only the devices specified by DASDAVR are searched.

Action:

Enter one of the following:

BYPASS exit and transfer control to VSE.

CANCEL cancel the job

STOP place the partition in the wait state until a CASTART command is issued by the VSE operator

V=vvvvvv search this volume for the file

SEARCH=ALL search all available volumes for the file

'dsname' search the volume for this new or corrected data set.

CADD005E — NO MATCHING INPUT EXTENT FILE=xxxxxxx SYSnnn=cuu volid

Reason:

The designated input file was found; however, CA-Dynam/D could not locate a matching extent sequence number for this file. The job is canceled.

Action:

Correct the extent sequence number and resubmit.

Messages 2–129


CADD007E — DATA SET/VERSION IS LOCKED FILE=xxxxxxx SYSnnn=cuu volid

Reason:

An attempt was made to OPEN a locked data set as an OUTPUT, or a locked version as an INPUT. The job is canceled.

Action:

Resolve the LOCK condition through catalog maintenance and resubmit.

CADD008A — VOLUME vvvvvv NOT AVAILABLE FILE=xxxxxxxx

Reason:

The CA-Dynam/D AVR routines were unable to locate the volume specified in the EXTENT statement.

Action:


CANCEL to cancel the job

STOP to place the partition in the wait state until a CASTART command is issued by the VSE operator

NEWPAC to mount a new disk pack (Mount the correct disk pack and type 'NEWPAC' at the operator's console. CA-Dynam/D will find volume automatically.)

V=volser to cause CA-Dynam/D to override the original volume serial number (pool or generic) with the specified value



CADD009D — DATA SET ALREADY ENQUEUED FILE=xxxxxxx SYSnnn=cuu volid

Reason:

Action:



The program has attempted to open a file which has been enqueued.

STOP to place the partition in the wait state until a CASTART command is issued by the VSE operator

RETRY to reobtain the Enqueue

CADD010W — INSUFFICIENT DISK SPACE FILE=xxxxxxx SYSnnn=cuu volid (ntrks)

Reason:

CA-Dynam/D was unable to allocate a contiguous area of disk space to satisfy the user's allocation request.

Action:

None. Message CADD021A will be issued after this message.

CADD011I — VOLUME xxxxxx - QUIESCED

CADD011I — VOLUME xxxxxx - OFFLINE

CADD011I — VOLUME xxxxxx - ONLINE

CADD011I — VOLUME ****** - ONLINE

Reason:

The DD STATUS command was issued and CA-Dynam found the listed volume to be temporarily bypassing DASD processing. 'ONLINE' indicates that the specified volume is not offine or quiesced. '******' indicates that a DD STATUS ALL command was issued and no volumes are currently quiesced or offline.

Messages 2–131


Action:

None.

CADD012W — CATALOG FILE-ID NOT FOUND FILE=xxxxxxx

Reason:

You tried to access a file from the Catalog but the file cannot be found.

Action:

Make sure that the correct Catalog is assigned. A display of the files in the Catalog can be obtained by executing the DYNCAT utility program. Check that the file ID on the DLBL statement matches exactly the file ID in the Catalog.

CADD013E — CATALOG DATA SET FULL FILE=xxxxxxx

Reason:

There is insufficient space to add a file to the Catalog.

Action:

Use the DYNCAT BACKUP and RESTORE or RESTORE REORG functions to recreate the Catalog data set with a larger extent area. If catalog free space fragmentation has occurred, use a BACKUP/RESTORE REORG to reorganize the Catalog without making it larger.

CADD014W — CATLG. ERR. R/C=xxxxxxxx FILE=xxxxxxx

Reason:

The Catalog management component has passed an error return code to CA-Dynam/D. The condition is usually caused by insufficient partition GETVIS. See "Catalog Management Return Codes" for more information.

Action:

Recreate the catalog data set. Contact the operations manager to check possible errors on the channel.



CADD015I — CATALOG REQUEST IGNORED FILE=xxxxxxx

Reason:

The catalog request was not successful. The most likely causes are:

■ a lack of sufficient GETVIS storage to process the catalog request

■ temporary catalog errors

■ enqueueing of the Catalog

The program will continue to process.

Action:

Identify and correct the cause of the message and resubmit the job if necessary.

CADD016E — PASSWORD VIOLATION FILE=xxxxxxx

Reason:

You are attempting to open a file which has a password associated with it, and the SYSPARM password supplied does not match the password in the Catalog.

Action:

Check the password defined when cataloging the file.

CADD017A — DUPLICATE CATALOG ENTRY FILE =xxxxxxx

Reason:

You are attempting to catalog a file which already exists in the Catalog.

Action:

Use DELETE to delete the original entry and add the new entry to the catalog. Use IGNORE to ignore the catalog request and continue to process the job.

CADD019A — ENTER PASSWORD FILE=xxxxxxx

Reason:

You are attempting to open a file which has a password defined in the Catalog.

Messages 2–133


Action:

Enter a matching password in order to continue processing. If an incorrect password is supplied, then message CADD016E will appear.

CADD020E — EXTENT VOLSER MISSING FILE=xxxxxxx SYSnnn=cuu volid

Reason:

You attempted to catalog a file, and the volume serial number was not supplied on the EXTENT statement.

Action:

Add the volume serial number to the EXTENT statement and rerun the job.

CADD021A — data-set-name (ntrks) CRE= dd mmm yyyy EXP=dd mmm yyyy MAX=nnnnnnnn

CADD021A — *** NO UNEXPIRED FILE(S) FOUND *** MAX=nnnnnnnn TRACKS/BLOCKS

CADD021A — *** END OF VTOC REACHED, WRAP-AROUND WILL OCCUR ***

Reason:

CA-Dynam/D was unable to allocate a contiguous area of disk space to satisfy the user's allocation request. The next unexpired file in the VTOC, its number of tracks, creation date (CRE=), and expiration date (EXP=) are displayed. Also displayed is the size of the largest contiguous free space on the volume (MAX=). This value is continuously updated through the recovery process. As files are deleted, if the deleted file was contiguous with the largest piece of free space, or was itself larger than the largest piece, the value will increase. By comparing this value with the amount of space required for the file being allocated, the operator can predict when sufficient space has become available. Files with an expiration date greater than or equal to the MANDTE parameter value in the CA-Dynam/D option record are not displayed during recovery. After the last unexpired file ID in the VTOC is displayed, CA-Dynam/D issues the last form of the message, returns to the beginning of the VTOC and displays the first unexpired file it finds.



Action:

Use the following commands.

Enter this To

CANCEL cancel job immediately

nnnn retry to allocate this number of tracks (CA-Dynam/D searches for the first volume defined in the 'pool' if a pool volume is used.)

DELETE delete from the VTOC the last file displayed on SYSLOG (The MAX value will be incremented if it was affected by the deletion of the file.)

BYPASS or B display on SYSLOG the next file in the VTOC

RETRY cause CA-Dynam/D to try to reallocate the space originally requested on the same volume

NEWPAC select the next generic or pool volume when using cross- volume allocation or pool management. This option is not valid for sequential work files.

V=volser

or V=*

cause CA-Dynam/D to allocate disk space on the specified disk volume (real or pool). If you use V=*, all volumes defined in the PUB table are searched. This option is not valid for sequential work files.

STOP place partition into wait state until the operator restarts the job.

EOB/END cause CA-Dynam/D to RETRY allocation.

MAX cause CA-Dynam/D to use the largest available piece of free space for the allocation. (This value appears in the MAX= field of this message. If the value is zero, the CADD021A message is reissued.)

BLDINDEX cause CA-Dynam/D to rebuild and remap the VTOC index, deleting all expired files automatically. (If the volume does not contain a VTOC index, the CADD021A message will be reissued.)

TAPE cause CA-Dynam/D to attempt to invoke CA-Dynam/FI to change the DTF in the program from disk to tape. Only valid if the complete CA-Dynam system (CA-Dynam/T, CA-Dynam/D, and CA-Dynam/FI) is installed and active, and only for the initial allocation of a sequential disk data file which is catalog-controlled. See "Controlling File Independence" in the User Guide for details.

Messages 2–135


If you enter an invalid response, the CADD021A message is redisplayed on the console.

Note: For DTFSD TYPEFILE=WORK, a reply of NEWPAC or V= is considered invalid. IBM requires that all extents reside on the same volume.

CADD022I — RELEASED nnnn TRACKS FILE=xxxxxxx VOL=xxxxxx

Reason:

Sequential disk (SD) or ISAM truncation has occurred.

Action:

None.

CADD024E — NO FREE LUBS AVAILABLE

Reason:

CA-Dynam/D, in trying to perform dynamic LUB allocation, was unable to find any LUB entries available. If issued for a multivolume Direct Access (DA) file, there may not have been a consecutive series of available LUB entries long enough for all the volumes used by the file.

Action:

Unassign one or more logical units which are not needed and rerun the job.

CADD025E — ILLEGAL SYSFIL OVERRIDE FILE=SYSnnn

Reason:

One of two things may have happened:

■ The CA-Dynam/D AVR routine is attempting to override an assignment for a library-type file or a system file (SYSLST, SYSLNK, SYSPCH) which has been opened previously in the job.

■ You have attempted to override the assignment of SYSIN.

Action:

None.



CADD026A — WRITE INHIBITED FILE=xxxxxxx SYSnnn=cuu volser

Reason:

Either the write inhibit switch is set on the disk device being accessed, or under VM/370 the disk device is linked in read-only (R/O) mode.

Action:


Enter this To


RETRY access the disk volume again

STOP have the partition STOPped (CASTART must be used to restart.)

NEWPAC to bypass the disk in favor of the next pack to be searched

V=volser to search the indicated volume (real or pool) instead of the current volume

CADD027E — VTOC ERROR SYSnnn=cuu volser F/C=nnnn R/C=nnnnnnnn nnnn

Reason:

An unexpected return code was received while reading or writing a VTOC. The job will be canceled.

Action:

Verify that there have been no hardware errors on the disk. Attempt to run either the DYNPRINT VTOC Report or LVTOC program to scan the VTOC. If the problem is replicated, the VTOC trace program may be used to collect documentation.

CADD028I — ACCESSED FILE=xxxxxxx SYSnnn=cuu volid IX=aa/bbbb/cccc (G#nn)

Reason:

A dynamic extent has been defined for a file and the file has been opened as input. CA-Dynam/D scans the VTOC for the appropriate extent information. If the DASD volume contains a VTOC index, the extent information will be preceded by IX; if not, it will be preceded by X.

Messages 2–137


Action:

None.

CADD029W — SD INPUT IGNORED FILE=xxxxxxx SYSnnn=IGN

Reason:

CA-Dynam/D has attempted to open a disk file as input and has found that it is assigned as 'IGN'. This is a warning. When COBOL programs read an input ignored file, they may appear to loop.

Action:

None.

CADD030W — FILE NOT CREATED USING THE CATALOG FILE=xxxxxxx

Reason:

A file is being accessed as input, using the Catalog, but it was not created as a catalog-controlled file.

Action:

None.

CADD031E — GENERATION OPTCODE ERR FILE=xxxxxxx SYSnnn=cuu volid

Reason:

A particular generation has been called, but cannot be determined.

For an input file, either

■ the 'G' optcode value is not numeric,

■ the matching data set is not defined in the Catalog as a generation-type data set, or

■ the label has both a DLBL and EXTENT statement.

For an output file, an attempt is being made to create a file using the G# or G- option, and the label record as submitted has no extent.



Action:

For input, verify that the DLBL for this file has no EXTENT (catalog-controlled). Verify that the data set is defined in the Catalog as a generation data set (using DYNCAT 'LISTCAT' command).

For output, verify that both the DLBL and EXTENT are present.

CADD033E — DATA IN GENERATION LABEL FILE=xxxxxxx SYSnnn=cuu volid

Reason:

CA-Dynam/D has detected characters in positions 41-44 of the file ID and this is not allowed for generation data sets. The job is canceled.

Action:

Rename the data set, limiting the file ID to 40 characters. CA-Dynam/D updates positions 41-44 of the file ID with the generation number.

CADD034W — NO LABEL FOUND FOR DTFNAME

Reason:

CA-Dynam/D could not find a valid DLBL/EXTENT statement in the label area for the above DTFNAME.

Action:

Correct the JCL and resubmit.

CADD036A — PERMANENT FILE FILE=xxxxxxx SYSnnn=cuu volid

Reason:

CA-Dynam/D has detected an equal file ID condition when attempting to allocate a permanent file.

Action:


Enter this To

CANCEL cancel the job immediately

DELETE delete the existing permanent file and allocate the file to be created

Messages 2–139


Enter this To

REWRITE rewrite the existing file using its existing extent limits (The number of tracks requested in job control will be ignored as the existing extent information will be used.)

IGNORE indicate that you don't want to delete the file found (allowed only after the permanent file is already allocated and CA-Dynam/D is searching for other possible equal file IDs on subsequent disk volumes defined in a 'pool')

CADD037A — ASSIGNMENT OVERRIDE FILE=xxxxxxx SYSnnn=cuu volid

Reason:

CA-Dynam/D is changing an existing assignment and not dynamically finding an available logical unit.

Action:


Enter this To


SYSnnn override logical unit with the specified SYSnnn

IGNORE allow the assignment to be changed

DYNLUB use dynamic LUB allocation to find a new logical unit

CADD038E — DYNAMIC ASSIGN ERROR FILE=xxxxxxx R/C=nn

Reason:

An unexpected error was received from the ASSGN function.

Action:

Collect the diagnostic information and contact Computer Associates.



CADD039W — VTOC IS FULL FILE=xxxxxxx SYSnnn=cuu volid

Reason:

CA-Dynam/D attempted to add a file entry to the VTOC and found the VTOC to be full.

Action:

If a real volume serial number was specified, CA-Dynam/D enters 'RECOVERY' and you can delete files which are not needed. Otherwise, the job will be canceled by the IBM open processing routines.

CADD042W — INSUFFICIENT STORAGE CA-Dynam/D PROCESSING BYPASSED

Reason:

CA-Dynam/D could not find sufficient partition GETVIS storage.

Action:

Define additional GETVIS storage.

CADD044A — MISSING INPUT EXTENT FILE=xxxxxxx EXTENT SEQUENCE NUMBER nnn

Reason:

CA-Dynam/D could not locate one or more of the data set's extents in the VTOC of the specified volume. This message is only issued if the filetype is DA or if the DDOPTION record has been coded with MODON=10.

Action:

Ensure that all extent statements are using the proper sequence numbers and that all required extents are in the VTOC.

Enter this To


STOP put the partition in which the job is executing into the wait state. (The CASTART command should be used to subsequently restart the partition.)

NEWPAC mount a new disk pack (Mount the correct disk pack and type 'NEWPAC' at the operator's console. CA-Dynam/D will find volume automatically.)

Messages 2–141


Enter this To

V=volser cause CA-Dynam/D to override the original volume serial number (pool or generic) with the specified value

CADD045W — INCORRECT DYNAM/D CONTROL PHASE FORMAT.

Reason:

CA-Dynam/D has been installed and activated, but the DYNAMD option record has not been initialized at the current level.

Action:

The DYNAMD option record must be initialized properly in the CAICUI database. Review the option record documentation in the Systems Programmer Guide. This message may also indicate option record or storage corruption. For assistance contact Computer Associates.

CADD046W — LABEL PROCESSING ERROR - F/C=nnnn R/C=nnnn

Reason:

An unexpected return code was received while processing disk label (DLBL) information. CA-Dynam/D processing will be bypassed.

Action:

If the problem recurs, collect diagnostic information, including a label trace, and contact Computer Associates.

CADD047E — INVALID ALLOCATION BY LOGICAL RECORD FILE=xxxxxxx

Reason:

An output DASD file controlled through the Catalog is being opened. The Catalog specifies that the file is to be allocated by a number of logical records, but the logical record size cannot be determined by CA-Dynam/D, and the Catalog does not specify the default LRECL and block sizes.

Action:

Update the catalog definition for the data set to include the logical record length and block size, and rerun the job.



CADD049I — INELIGIBLE VOLUME FILE=xxxxxxx SYSnnn=cuu volser

Reason:

An attempt was made to allocate DASD space on a volume which is not eligible to contain the extent. The volume already contains previous extents of the file but does not contain the extent just prior to the one currently being allocated.

Action:

If a real volume serial number was specified for the file, insufficient space recovery will be invoked. If a pool volume serial was specified, allocation is attempted on the next volume defined in the pool. If no other volume in the pool contains sufficient free space, insufficient space recovery will be invoked.

CADD050E — UNEXPECTED ERROR F/C=nnnn R/C=nnnn F/N=xxxxxxxx

Reason:

Unexpected return codes have been received from adapter functions. The function code, return code and function name are reported.

Action:

Collect diagnostic information and contact Computer Associates.

CADD051W — INVALID RESPONSE, NOT PRIMARY ALLOCATION, FILE=xxxxxxxx

Reason:

A response of 'TAPE' has been made to an insufficient space message, and the request to modify the open from disk to tape cannot be honored. The reason for denying the request is noted in the text of the message. See the chapter on Controlling File Independence for restrictions for operator dynamic file switching.

Action:

Either cancel the job, or continue with normal processing of recovery from insufficient space. The file cannot be placed on tape.

Messages 2–143


CADD053W — INVALID RESPONSE, UNSUPPORTED DTF TYPE, FILE=xxxxxxx

Reason:


Action:


CADD059W — INVALID RESPONSE, FILE ALREADY OPEN, FILE=xxxxxxx

Reason:


Action:


CADD060W — INVALID RESPONSE, NOT SUPPORTED ON CA-SORT ALLOCATION, FILE=xxxxxxx

Reason:


Action:




CADD064E — EXTERNAL SECURITY VIOLATION FILE=dtfname

Reason:

External security is installed and active, and a request for OPEN of a data set has been issued which would violate defined security restrictions. The partition issuing the OPEN is not running as a logged-on external security user authorized to access the file. The job will be canceled.

Action:

Either resubmit the job with an ID statement for an authorized user or contact the Security Administrator.

CADD065I — VOLUME vvvvvv CANNOT BE LOCATED

Reason:

This message is issued if the volume given in the V= response cannot be located.

Action:

Respond with an existing volser, or see the message displayed prior to this message for other available responses.

CADD066I — AUTO-DELETE OF TEMPORARY DATA-SET(S) IN PROGRESS

Reason:

Whenever CA-Dynam/D deletes temporary data sets this message appears. This deletion results if temporary data sets were used within a job. Deletion of temporary data sets will be invoked when a /& or a // JOB JCL statement is encountered.

Action:


CADD067W — TOO MANY CHARACTERS FOR TEMPORARY DATA SET NAME FILE=xxxxxxx

Reason:

CA-Dynam/D has found a temporary data set name with more than eight characters specified. The remaining characters will be truncated.

Messages 2–145


Action:

A possibility of duplicate data set names exists. Correct Job Control and resubmit.

CADD068A — NO VOLUMES IN POOL vvvvvv AVAILABLE

Reason:

CA-Dynam/D is not able to locate any real volume in the pool specified in the EXTENT statement or, if Catalog controlled, specified in the Catalog allocation information. Note that if DASDAVR was generated at installation, only the devices specified by DASDAVR are searched.

Action:



STOP to put the partition in which the job is executing into the wait state

V=vvvvvv to search this volume for the file

NEWPAC to mount or define a new disk pack, and type NEWPAC at the operator's console. CA-Dynam/D will find the volume automatically.

CADD069A — INVALID REPLY - ENTER VALID REPLY

Reason:

The response to the message displayed before this message was not correct.

Action:

Respond with a valid reply.



CADD070W — USER CLOSE EXIT xxxxxxxx NOT FOUND

CADD070W — USER LABEL EXIT xxxxxxxx NOT FOUND

CADD070W — USER MESSAGE EXIT xxxxxxxx NOT FOUND

CADD070W — USER OPEN EXIT xxxxxxxx NOT FOUND

CADD070W — USER REPLY EXIT xxxxxxxx NOT FOUND

Reason:

CA-Dynam/D was unable to locate the named phase in any of the chained sublibraries.

Action:

Perform a LISTDIR for the affected sublibraries and then do one of the following:

■ correct the phase name in the CA-Dynam/D option record; then either refresh the option record or perform an IPL,

■ or, add the missing library to the LIBDEF search chain.

CADD071E — INSUFFICIENT GETVIS FOR USER EXIT PROCESSING

Reason:

CA-Dynam/D could not find sufficient partition GETVIS storage for the User Exit Block.

Action:

Define additional GETVIS storage.

CADD072E — FILE=xxxxxx NO ALLOCATION INFORMATION IN CATALOG FOR xxxxxxxxxxxxxxxxxx

Reason:

A disk data set was defined to the Catalog without allocation information and there is no definition in the CA-Dynam/D option record for default allocation or, if the file is input, for automatic secondary allocation.

Messages 2–147


Action:

Define allocation information for the data set in the Catalog, define default allocation in the CA-Dynam/D option record, or define secondary allocation in the CA-Dynam/D option record.

CADD073E — NO EXTENT SPECIFIED FOR TEMPORARY DATA SET NAME FILE=xxxxxx

Reason:

No EXTENT statement was supplied by a temporary data set and there is no definition in the CA-Dynam/D option record for default allocation or, if the file is input, for automatic secondary allocation.

Action:

Supply an EXTENT statement, define default allocation in the CA-Dynam/D option record, or define secondary allocation in the CA-Dynam/D option record.

CADD074E — CANCELLED - NO MORE AVAIL. EXT. - FILE=.......'

Reason:

CA-Dynam/D did not have enough extents available to write the entire file. Either not enough extents were defined for ASA processing or the number of secondary extents defined in the catalog was not sufficient.

Action:

If this is a catalog controlled file, increase the number of secondary allocations or increase the size of each allocation using the DYNCAT alter statement or through the CUI DYNT online screens. If it is an ASA file, increase the ASA values to allow for a larger file using the CUI online CA-Dynam/D Options screens or by altering this system option with CACCDBU0.

CADD100W — CA-Dynam/D POST-INITIALIZATION ERROR F/C=nnnn R/C=nnnn

Reason:

Post-initialization has detected an error that is not serious enough to terminate processing. Consult the table below to determine the possible effect on your system.

Action:

None or, if you determine the impact on your processing is serious enough, correct the error and re-ipl.



Function Code

Meaning and Action to be taken

1 Unable to locate DDDTFEX, the CA-Dynam/D DTF exclusion list. Run CACCDBU0 with parameters that will cause the CAICUI file to be initialized with CA-Dynam/D's records.

2 Unable to locate DDLUBEX, the CA-Dynam/D LUB exclusion list. Run CACCDBU0 with parameters that will cause the CAICUI file to be initialized with CA-Dynam/D's records.


CADD101E — CA-Dynam/D POST-INITIALIZATION FAILURE F/C=nnnn R/C=nnnn

Reason:

Post-initialization has detected an severe error and will be prematurely terminated. The impact on CA-Dynam/D processing will vary depending on the error.

Action:


Function Code


0 Unable to locate CA-Dynam/D, the CA-Dynam/D System Option Record. Run CACCDBU0 with parameters to define DDOPTIONS.

1 Product CA-Dynam/D is not active. Check startup procedure, libdefs etc.


CADD201 — INVALID CONTROL CARD.

Reason:

The DYNCATCV program control card is either missing or invalid. If the control card was supplied, this message is preceded by the CADD205I message, which lists the statement on both the console and printer.

Messages 2–149


Action:

Review the control statement for errors in either the positional parameters (backup or restore) or the keyword parameters of the restore option. If the message CADD205I was not issued, the required control statement was not supplied through the SYSIPT device.

CADD202 — DATASETS PROCESSED=nnnn

Reason:

The number of data set definitions read from the old Catalog for a backup execution, or the number of data sets added to the new Catalog for a restore execution are reported.

Action:

None.

CADD203 — CATALOG ERROR R/C=nnnn data-set-name

Reason:

An error has been detected while accessing the Catalog file. The return code (R/C=) is a Catalog Management return code. The data set name of the file entry is included in the message text.

Action:

Ignore many noncritical errors. The most common of these errors is return code 086C which indicates that a duplicate data set name is already in the Catalog. If the reason for the error cannot be determined, contact Computer Associates for assistance.

CADD204 — CATALOG IS FULL

Reason:

The CA-Dynam Catalog file is full.



Action:

If the catalog file already contains production data set definitions, back up the catalog file to tape using the DYNCAT utility program, reload the catalog label information specifying a larger extent area, restore the catalog backup tape to the new area, and restart the conversion. Any data sets which were successfully added to the new Catalog before it became full will be reported as duplicates. If the catalog file did not contain active data set information, simply provide a larger extent area and restart the conversion program.

CADD205I — --- input control statement ---

Reason:

The control statement read by the DYNCATCV program is provided.

Action:

None.

CADD331E — PARTITION ID MISSING OR INVALID

Reason:

A CATRACE command has been entered with an invalid or missing partition ID.

Action:

Enter a valid partition ID and resubmit.

CADD332E — CUU/SYSNNN MISSING OR INVALID

Reason:

A CATRACE command has been entered with an invalid or missing cuu or SYSnnn number.

Action:

Enter a valid cuu or SYSnnn number and resubmit.

CADD333E — INVALID STARTING EXTENT NUMBER SPECIFIED

Reason:

A CATRACE command has been entered with an invalid starting extent number.

Messages 2–151


Action:

Enter an extent number between 0 and 255, and resubmit.

CADD334E — DTFNAME MISSING OR INVALID

Reason:

A CATRACE command has been entered with an missing or invalid dtfname.

Action:

Specify a valid dtfname and resubmit.

CADD335E — TAPE CUU SELECTED IS NOT OPERATIONAL

Reason:

A CATRACE command has been entered with a cuu belonging to a tape unit whose status is unavailable.

Action:

Make sure a tape unit is attached and ready before entering the CATRACE command.

CADD336E — SPECIFIED PRODUCT IS NOT ACTIVE OR NOT AVAILABLE

Reason:

A CATRACE command has been entered for a product that is inactive, or has not been initialized.

Action:

Make sure the correct product code is entered for the CATRACE command, and that the product has successfully initialized and is currently active.

CADD401E — UNRECOGNIZED OPERATION CODE

Reason:

DYNOPEN command code is in error.



Action:


CADD402E — INVALID KEYWORD OPERAND

Reason:

One of the DYNOPEN operands is invalid (FILE, UNIT, ETC.).

Action:


CADD403E — INVALID FIELD

Reason:

One of the DYNOPEN user-supplied operand values is invalid.

Action:


CADD404E — FILENAME IS MISSING

Reason:

A DYNOPEN 'OPEN' command has been entered without a filename specified.

Action:


CADD420D — ENTER NUMBER OF OUTPUT RECORDS

Reason:

An output file is being created by DYNTEST.

Action:

Either enter number of output records or enter CANCEL.

Messages 2–153


CADD421E — INVALID OR NO UPSI SPECIFIED

Reason:

Either no UPSI or an invalid UPSI is specified.

Action:

None. The job is canceled.

CADD422E — INVALID RECORD NUMBER SPECIFIED

Reason:

There is a nonnumeric value specified for record number.

Action:

If the job is run from the console, the operator is prompted for the record number; otherwise the job is canceled.

CADD423I — SD WORK FILE HAS BEEN CREATED

Reason:

DYNTEST has created an SD work file.

Action:


CADD424I — NUMBER OF RECORDS READ

Reason:

DYNTEST has completed reading an input file.

Action:


CADD425I — NUMBER OF RECORDS WRITTEN

Reason:

DYNTEST has completed writing an output file.



Action:


CADD426E — INSUFFICIENT DISK SPACE FOR FILE

Reason:

There is insufficient disk space for the file.

Action:

Review JCL for changes which may be necessary.

CADD427E — ISAM ERROR ENCOUNTERED RTC=nn

Reason:

An ISAM error has been encountered.

Action:


CADD428E — DA ERROR ENCOUNTERED RTC=nn

Reason:

A DA error has been encountered.

Action:


CADD500E — INSUFFICIENT STORAGE AVAILABLE TO EXECUTE DYNUTIL

Reason:

The DYNUTIL program requires a minimum partition size of 64K and should not be executed with 'SIZE=AUTO'.

Action:

Increase the size of the partition to a minimum of 64K bytes.

Messages 2–155


CADD501E — UNEXPECTED END OF DATA ON INPUT FILE. (CONTINUATION CARD EXPECTED)

Reason:

DYNUTIL expected a continuation card and instead encountered end of data.

Action:

Insert continuation card and resubmit the job.

CADD502E — TOO MANY CONTINUATION STATEMENTS

Reason:

More than the maximum number of continuation cards was encountered.

Action:

Limit the number of continuation cards to four.

CADD503E — UNRECOGNIZABLE COMMAND

Reason:

DYNUTIL was unable to recognize or validate the command entered.

Action:

Check valid DYNUTIL commands and resubmit.

CADD504E — REQUIRED OPERAND(S) OMITTED

Reason:

DYNUTIL could not find one of the required operands for the command processed.

Action:

Check required operands and correct the error.

CADD505E — INVALID KEYWORD OPERAND

Reason:

A keyword operand was used incorrectly.



Action:

Correct error and resubmit.

CADD506E — UNRECOGNIZABLE KEYWORD OPERAND

Reason:

An operand which was not understood by DYNUTIL was found.

Action:

Correct error and resubmit.

CADD507E — TOO MANY POSITIONAL OPERANDS

Reason:

DYNUTIL found too many operands specified in the OPEN, CLOSE, or TAPE command option list.

Action:

Ensure that each option within parentheses is specified once only and that all operands are separated by at least one blank.

CADD508E — TOO MANY REPEATS OF KEYWORD OPERAND

Reason:

DYNUTIL found a keyword requested or duplicated for the same command.

Action:


CADD509E — TOO MANY SUBOPERANDS

Reason:

More than the allowable number of options were specified within parentheses on the OPEN or CLOSE command.

Action:


Messages 2–157


CADD510E — SYNTAX ERROR - UNPAIRED PARENTHESES

Reason:

A pair of parentheses must surround the options specified. DYNUTIL found only one parenthesis.

Action:


CADD511E — SYNTAX ERROR - UNPAIRED APOSTROPHES

Reason:

DYNUTIL found only one apostrophe for the file ID; the file ID must be surrounded by a pair of apostrophes.

Action:


CADD512E — SYNTAX ERROR - INVALID SEPARATOR

Reason:

DYNUTIL found a separator other than a blank between operands.

Action:


CADD513E — INVALID NUMERIC VALUE

Reason:

The year and/or number of days specified on the DUMP/RESTORE command has an invalid value (EXPIRE operand). The maximum number of days is 366.

Action:




CADD514W — VALUE IS TOO LONG - TRUNCATED

Reason:

DYNUTIL found a volume serial number specified with more than six characters.

Action:


CADD515E — VALUE IS TOO LONG

Reason:

One of the operands exceeds its maximum length.

Action:


CADD516E — INVALID OR UNRECOGNIZABLE VALUE

Reason:

An invalid value has been specified for one of the operands.

Action:


CADD517E — STRING MUST BE IN APOSTROPHES

Reason:

The file ID operand is not enclosed within apostrophes.

Action:


CADD518E — STRING CANNOT BE IN APOSTROPHES

Reason:

Apostrophes were found around an operand other than the file ID.

Messages 2–159


Action:


CADD519W — VOL=/POOL= HAS BEEN SPECIFIED WITH CATALOG, VOL/POOL IGNORED

Reason:

DYNUTIL CATALOG and VOL= or POOL= are mutually exclusive. VOL=/POOL= has been ignored.

Action:

Correct and resubmit if necessary.

CADD520E — POOL KEYWORD IS ILLEGAL-DYNTABS TABLE IS NOT ACTIVE

Reason:

DYNUTIL encountered a POOL keyword and found that the COMPOOL table is not loaded into system GETVIS.

Action:

Load the COMPOOL table into system GETVIS using CUI or CACCDBU0, or change POOL= to VOL= if a real volser is specified.

CADD521E — UNACCEPTABLE VALUE HAS BEEN SPECIFIED FOR POOL VOLUME SERIAL NUMBER

Reason:

A 6-character pool volume serial number was expected and not found. In addition, asterisks are not permitted as part of the pool volume serial number.

Action:

See the DYNPOOL option record for further details.

CADD522E — SPECIFIED POOL VOLUME SERIAL NUMBER CANNOT BE FOUND FOR THIS PARTITION IN THE DYNTABS TABLE

Reason:

The pool volume serial number is specified with a partition ID, and the pool serial number is not defined in the COMPOOL table.



Action:

See the COMPOOL option record for further details.

CADD523E — ONE OR MORE ARGUMENTS ILLEGAL WITH THIS FUNCTION

Reason:

Illegal operands were found for the specified command.

Action:


CADD524E — VOL= OR POOL= HAS NOT BEEN SPECIFIED

Reason:

When a file ID is specified, then either VOL= or POOL= must also be specified.

Action:


CADD525E — VOL= AND POOL= CANNOT BE SPECIFIED TOGETHER

Reason:

It is invalid to specify VOL= and POOL= together.

Action:


CADD526E — ILLEGAL VOL=/POOL= OR BAD FILE-ID

Reason:

VOL= or POOL= is invalid with the requested function. A file ID contains illegal characters for the requested function.

Action:


Messages 2–161


CADD527E — OPEN REJECTED - TAPE FILE IS ALREADY OPEN

Reason:

You are trying to OPEN a file which has already been opened by a previous OPEN or DUMP command.

Action:

Insert a CLOSE command for the file.

CADD528E — CLOSE REJECTED - TAPE FILE IS NOT OPENED

Reason:

You are trying to close a file which is not currently OPEN.

Action:

Check the logical sequence of the commands submitted.

CADD529E — LOGICAL UNIT IS NOT ASSIGNED TO A TAPE

Reason:

The tape file isn't assigned to the default logical unit or the specified logical unit (OPEN command).

Action:

Make a logical assignment for tape file and resubmit job.

CADD530W — CLOSE FILENAME DOES NOT MATCH CURRENTLY OPENED TAPE FILE

Reason:

The CLOSE filename doesn't match the filename specified on the previous OPEN command.

Action:




CADD531E — WRONG TAPE STATUS, CURRENTLY AS OUTPUT

Reason:

The tape file was opened as output, and a RESTORE function was issued.

Action:

Close the tape and then open it for input before the RESTORE function is performed.

CADD532E — WRONG TAPE STATUS, CURRENTLY AS INPUT

Reason:

The tape file was opened as input, and a DUMP function was issued.

Action:

Close the tape and then open it for output before the DUMP function is performed.

CADD533E — WRONG TAPE STATUS, LOGICAL UNIT IS OPEN

Reason:

An attempt to reposition a tape device that has already been opened for either input or output has occurred.

Action:

None.

CADD534E — INVALID EXPIRATION HAS BEEN SPECIFIED

Reason:

The expiration date specified is not in the format yy/ddd.

Action:

Correct date and resubmit.

Messages 2–163


CADD535E — INVALID PROGRAMMER LOGICAL UNIT

Reason:

The logical unit specified on the command line is not within the range of valid programmer logical units for the active partition.

Action:

Specify a logical unit which is valid for the execution partition.

CADD536A — VOLUME NOT ONLINE, PLEASE MOUNT volser

Reason:

The specified disk volume could not be found by the DYNUTIL program. This message is issued in conjunction with CADD561A.

Action:

The operator should mount the specified volume and reply EOB/END/ENTER to continue processing. To cancel the job, reply CANCEL.

CADD537E — UNSUPPORTED DASD DEVICE ENCOUNTERED DURING PROCESSING

Reason:

DYNUTIL can support the following DASD device types: 2311, 2314, 3310, 3330 (mod I and II), 3340, 3350, 3370, 3375, 3380, 3390.

Action:

Verify DASD device type being used.

CADD538E — INSUFFICIENT STORAGE TO EXECUTE REQUESTED FUNCTION

Reason:

DYNUTIL is unable to locate sufficient buffer space to perform the requested function.

Action:

Increase partition size and resubmit the job.



CADD539E — NO DATA SET(S) FOUND TO PROCESS

Reason:

DYNUTIL could not locate the requested file ID(s).

Action:

For DUMP function, run DYNPRINT VTOC display in order to check the existing file IDs in the VTOC. For REORG function, run DYNUTIL LISTTAPE to verify the existence and order of the file on the tape.

CADD540I — CATALOG CONVERSION FOR fileid COMPLETED

Reason:

CONVERT has been specified as part of the DYNUTIL REORG command and the conversion has successfully completed.

Action:


CADD541E — UNEXPECTED DASD I/O ERROR, CCB='xxx,.....,xxx' CCW=xxxx,.....,xxxx SEEK=xxxxxxxx

Reason:

DYNUTIL encountered a DASD I/O error in processing the disk volume specified.

Action:

Check for DASD hardware problems.

Messages 2–165


CADD542I — DUMPING 'file-id' tttt, VOL=xxxxxx, VOLSEQ=nn, TAPE VOLSER=nnnnnn, TAPE VOLSEQ=nn

CADD542I — RESTORING 'file-id' tttt, VOL=xxxxxx, VOLSEQ=nn, DUMPED AT (date,time)

CADD542I — REORGANIZING 'file-id' tttt, VOL=xxxxxx, VOLSEQ=nn, DUMPED AT (date,time)

CADD542I — REORGANIZING 'file-id' AS 'new-file-id' ww, VOL=xxxxxx, VOLSEQ=nn

CADD542I — ALTERING 'file-id' VOL=xxxxxx, VOLSEQ=nn, EXTENTS=mm

CADD542I — DELETING 'file-id' VOL=xxxxxx, VOLSEQ=nn, EXTENTS=mm

CADD542I — RESTORING 'file-id' tttt, VOL=xxxxxx, VOLSEQ=nn

Reason:

DYNUTIL is performing the indicated function. 'tttt' represents the number of tracks or blocks; 'ww' represents the type of file (SD, DA, ISAM, VSAM, or DAM).

Action:

None.

CADD543I — VOLUME=xxxxxxx,VOLSEQ=nn,ttttt,SEQ=nn LOWER-LIMIT=ccc-hh UPPER-LIMIT=ccc-hh

Reason:

DYNUTIL is processing the disk volume and extent specified.

Action:

None.



CADD544E — FILE-ID NOT FOUND

Reason:

The file-id which satisfies the specified parameters could not be found on the requested disk volume(s).

Action:

Execute DYNVTOC to produce a VTOC file ID display of the volume.

CADD544W — FILE-ID NOT FOUND (DYNUTIL DELETE FUNCTION ONLY)

Reason:

The file-id which satisfies the specified parameters could not be found on the requested disk volume(s).

Action:

Execute DYNPRINT VTOC Report to produce a VTOC file ID display of the volume.

Note: The DYNUTIL DELETE function will issue this as a warning message.

CADD545E — ONE OR MORE EXTENTS/VOLUMES MISSING FOR FILE-ID 'file-id'

Reason:

DYNUTIL, in attempting to locate multiple extents for the file, detected a missing disk volume.

Action:

Execute DYNPRINT VTOC Report to locate all of the extents for the specified file ID.

CADD546E — DUPLICATE COPIES OF THE SAME FILE HAVE BEEN FOUND 'file-id'

Reason:

DYNUTIL found duplicate copies of the same file ID.

Action:

Delete one of the file IDs and resubmit the job.

Messages 2–167


CADD547E — MIXED DASD TYPES ENCOUNTERED DURING PROCESSING

Reason:

In processing a multiple extent file, DYNUTIL found two extents for the file on different DASD device types.

Action:

Recreate file with all extents on the same DASD device type.

CADD548E — DUPLICATE FILE-ID FOUND ON VOLUME=xxxxxx 'file-id'

Reason:

In performing the RESTORE or in a DISPLAY function, more than one file ID was found in the pool. DYNUTIL found an equal file ID in the VTOC.

Action:

Delete the file before performing the RESTORE, or specify the REPLACE operand on the RESTORE command. In a DISPLAY function, use the EXTENT or PBN operands.

CADD549E — FILE-ID OVERLAPS VTOC

Reason:

The file ID to be restored overlaps the VTOC of the disk volume specified.

Action:

Check the disk volume specified on the RESTORE command.

CADD550E — FILE-ID TO BE RESTORED OVERLAPS 'file-id'

Reason:

An overlap condition occurs when restoring the specified file ID to disk.

Action:

Delete or move to another extent area the file which overlaps in order to successfully perform the RESTORE.



CADD551E — NO SPACE IN VTOC TO ADD 'file-id'

Reason:

The VTOC file for the specified disk volume is full.

Action:

Delete entries from the VTOC before performing the RESTORE.

CADD552E — DUMP/RESTORE FUNCTIONS ARE NOT SUPPORTED

Reason:

The CA-Dynam/D system was generated without DUMP/RESTORE support.

Action:

Specify DYNUTIL=YES in CA-Dynam/D option record.

CADD553E — INPUT TAPE IS NOT A FULL VOLUME DUMP

Reason:

The user specified to DYNUTIL to restore an entire volume and the input tape does not contain full volume dump for the specified volume.

Action:

Locate the correct input tape and resubmit the job.

CADD554E — SPECIFIED FILE-ID IS NOT ON THE INPUT TAPE

Reason:

The file-id which satisfies the specified parameters could not be located on the input tape during a RESTORE function.

Action:

Verify that the input tape being processed is correct.

Messages 2–169


CADD555W — REORGANIZATION IGNORED FOR 'dsname' BECAUSE

THE FILE IS NOT SEQUENTIAL

CISIZE CANNOT BE DETERMINED FROM THE ORIGINAL FORMAT-1

THE FILE TO REORG IS INCOMPLETE

GDS= SPECIFIED AND CATALOG OMITTED

THE VERSION IS NOT CURRENT

NEWDSN= ERRONEOUSLY SPECIFIED

THE VERSION TO REPLACE IS NOT CURRENT

GDS=NEW INVALID FOR GENERIC REORGANIZATION

GDS=REPLACE IS SPECIFIED AND NEWDSN= OMITTED

FILE IS FOUND IN THE CATALOG WHILE NONCATAL IS SPECIFIED

FILE CANNOT BE FOUND IN THE CATALOG WHILE CATALOG IS SPECIFIED

DATASET NAME SPECIFIED BY NEWDSN= IS NOT FOUND IN THE CATALOG

NONCATAL IS SPECIFIED AND THE DATASET NAME SPECIFIED BY NEWDSN= IS FOUND IN THE CATALOG

THIS IS NOT A GENERATION DATASET

THE DATASET CONTROL BLOCK (DSCB) ON THE TAPE IS INVALID

SPECIFIED VOLUME OR POOL CANNOT BE FOUND



THE DASD TYPE TO RESTORE TO IS NOT SUPPORTED

Reason:

Reorganization was ignored for any of the reasons in these messages.

Action:

None.

CADD556E — INSUFFICIENT USRLABEL TRACK AREA TO GENERATE LABELS

Reason:

There is not enough space on the USRLABEL area to build the required CA-Dynam/D label records to control the reorganization request. The REORG function is terminated.

Action:

Rerun the job without unnecessary DLBL/EXTENT or TLBL statements.

CADD557E — DASD DEVICE TYPE DISAGREES WITH RESTORE FILE

Reason:

The disk device type to be used in the restore operation does not agree with the type of disk from which the file was originally dumped.

Action:

If you are changing DASD types you must use the REORG command; otherwise, ensure that you RESTORE to the same DASD type from which the file was originally dumped.

CADD558E — UNEXPECTED/UNRECOGNIZABLE RECORD FOUND ON INPUT TAPE

Reason:

Either one or more control blocks necessary to restore the file were not found on the input tape, or an unrecognizable record was found.

Action:

Ensure that the tapes are read in their proper volume sequence and that a subsequent volume is the proper tape.

Messages 2–171


CADD559E — PREMATURE EOF ON INPUT TAPE VOLUME

Reason:

An end-of-file condition has occurred during a file restore.

Action:

Ensure that the tapes are read in their proper volume sequence and that a subsequent volume is the proper tape.

CADD560E — CATALOG CONVERSION FOR 'FILE-ID' REJECTED

Reason:

Convert option of DYNUTIL REORG was specified, but the file-id cannot be found in the Catalog or is not a current version. REORG continues.

Action:

Make sure dump tape is current.

CADD561A — REPLY CANCEL OR (EOB/END) AFTER VOLUME IS MOUNTED

Reason:

Issued in conjunction with message CADD536A. The operator may either continue processing or cancel the function.

Action:

A reply of EOB/END/ENTER will continue processing. A reply of CANCEL will cancel the job.

CADD562E — FUNCTION ABNORMALLY TERMINATED, RETURN CODE=nnn

Reason:

The function concurrently being processed has been terminated due to errors. Note that the return code has no significance in the current version. It is used internally to determine the severity of the error and will have additional uses in future versions.

Action:

None.



CADD563I — END OF DYNUTIL PROCESSING

Reason:

The DYNUTIL program has completed all of its processing.

Action:

None.

CADD564E — END OF FILE/EXTENT ENCOUNTERED BEFORE STARTING RECORD

Reason:

An end of file/extent has been encountered before starting a record.

Action:

Investigate to assure that the DASD location is known.

CADD565W — WARNING!! HOME ADDRESS DOES NOT CORRESPOND TO ACTUAL DISK ADDR

Reason:

The home address field of the track does not equal the actual disk address. This may be caused by a defective/alternate track.

Action:

Investigate to assure that the DASD device is not 'corrupt.'

CADD566A — filename IS SPECIFIED AS A DATA-SECURED FILE

Reason:

A request has been made to DELETE or ALTER for the file 'filename' which is currently a data-secured file.

Action:

Use the following responses.

Respond To

IGNORE perform the specified action while ignoring the file status

BYPASS skip this file (continue with generic scan)

Messages 2–173


Respond To

CANCEL cancel this command and continue with the next DYNUTIL command

CADD567A — filename IS SPECIFIED AS A PERMANENT FILE

Reason:

A request has been made to DELETE or ALTER for the file 'filename' which has an expiration date greater than the AUTODTE parameter of the CA-Dynam/D option record.

Action:

Respond as follows.

Respond To

IGNORE perform the specified action ignoring the file status

BYPASS skip this file (continue with generic scan)

CANCEL cancel this command and continue with the next DYNUTIL command

CADD568E — INVALID CHARACTER SET SPECIFIED

Reason:

An invalid character set has been specified for the CHARSET= operand of the DYNUTIL DISPLAY command.

Action:

Correct the CHARSET= specification. Specify either 48, 60, or ALL for the CHARSET= operand.

CADD569E — CONFLICTING OPTIONS SPECIFIED

Reason:

The options specified on the current DYNUTIL command cannot be used together.



Action:

Remove the conflicting option and reexecute the command. The options which may not be specified together are:

Not together In this command

VTOC and 'FILE-ID' DISPLAY

PERM, RETAIN, EXPDATE ALTER

DSFON and DSFOFF ALTER

CADD570E — UNEXPECTED VTOC ERROR F/C=nn R/C=nn

Reason:

Error return from VTOC.

Action:

Obtain diagnostics and contact Computer Associates.

CADD571E — CANNOT ALTER, NEW FILE-ID ALREADY PRESENT

Reason:

You have attempted to use DYNUTIL to change a file ID in a VTOC already containing a file with the same file ID.

Action:

Use DYNPRINT VTOC Report to display the files already present to resolve the conflict.

CADD572E — LABEL I/O ERROR F/C=nn R/C=nn

Reason:

DYNUTIL has received a bad return code from the label processor.

Action:

Use LSERV to determine the cause of the error and correct.

Messages 2–175


CADD573E — CATALOG FILE-ID NOT FOUND

Reason:

DYNUTIL cannot locate the requested file in the Catalog.

Action:

Use DYNCAT LISTCAT to locate the file in question and determine the cause of the error, and correct.

CADD574E — CATALOG 'ddname' CANNOT BE LOCATED OR ACCESSED.

Reason:

The indicated file cannot be located by Catalog Management.

Action:

Check logical unit assignment, labels etc. to determine the cause of the error.

CADD575E — CATALOG ERROR OCCURRED F/C=xx R/C=xxxxxxxx

Reason:

An unexpected return code has been received from the Catalog Management component. The function code and return codes are Catalog Management codes, and they indicate a problem in access of either the catalog or audit file.

Action:

Inspect the return code for 'normal' errors such as insufficient storage. BACKUP the Catalog immediately if the problem does not appear to be of this type, and contact Computer Associates for assistance.

CADD576W — WARNING POSSIBLE MISSING EXTENTS FOR FILE-ID 'file-id'

Reason:

DYNUTIL, while processing a full-volume dump has found a file which might have extents on another volume.

Action:

Run DYNPRINT VTOC Report to verify the locations of all extents for the file.



CADD577W — 'volser' NOT MOUNTED FOR CATALOG DSN='file-id'

Reason:

DYNUTIL, while processing a dump with the CATALOG option, has found a file with extents on a volume which is not mounted.

Action:

Run DYNPRINT VTOC Report to verify the locations of all extents for the file, and run DYNUTIL again with all volumes mounted.

CADD578E — FILE LABEL 'label' NOT FOUND

Reason:

DYNUTIL could not locate the specified label record.

Action:

Correct JCL and resubmit the job.

CADD579E — UNSUPPORTED OPERATING SYSTEM

Reason:

The operating system is an unsupported one.

Action:

Contact Computer Associates for more information on supported systems.

CADD580E — SYSTEM ADAPTER NOT ACTIVE - PROCESSING TERMINATED

Reason:


Action:

Activate the CA-Dynam system before running DYNUTIL.

Messages 2–177


CADD581E — INDEXED VTOC ERROR OCCURRED F/C=xx R/C=xxxxxxxx

Reason:

An unexpected return code has been received during DYNUTIL VTOC processing from the VTOC access component. The function code and return codes are VTOC codes, and indicate a problem in accessing the VTOC or VTOC index.

Action:

Inspect the return code for 'normal' errors such as insufficient storage. (See Indexed VTOC return codes at the end of the message section of this manual.) If the problem does not appear to be of this nature, document the problem and contact Computer Associates.

Verify the contents and format of the VTOC and VTOC Index of the volume on the device indicated by running an LVTOC and DYNPRINT VTOC for the volume with indexed VTOC support active, then again with it deactivated, and compare the two. If the problem is reproducible, run the VTOC trace.

CADD582E — SYSTEM ADAPTER ERROR OCCURRED.

FUNCTION=xxxxxxxx F/C=xxxx R/C=xxxxxxxx xxxxxxxx

Reason:

An unexpected return code has been received during the System Adapter processing from the component identified as FUNCTION=. The function code, if given, is the function requested by DYNUTIL from the System Adapter. The return code (and, in some cases, the extended error code) are what the System Adapter component returned to DYNUTIL.

Action:

Inspect the return code for 'normal' errors such as insufficient storage. (See System Adapter return codes in the CA-CIS Message Guide.) If the problem does not appear to be of this nature, document the problem and contact Computer Associates.



CADD583E — VOLUME volser IS READ-ONLY, FUNCTION CANNOT BE PERFORMED

Reason:

The indicated volume is in read-only mode, and a DELETE, ALTER or RESTORE has been issued.

Action:

Make the disk write-accessible.

CADD587W — DUMP IGNORED FOR filename

Reason:

The specified file contains user labels which are not supported by DYNUTIL.

Action:

None.

CADD589E — BLOCKSIZE ERROR

Reason:

The blocksize of the logical record to restore is larger than the blocksize calculated by DYNUTIL initialization.

Action:

If the device type to restore to is FBA, this problem can be solved by specifying a larger CISIZE in the DLBL statement.

CADD591I — REORGANIZATION SUCCESSFULLY COMPLETED

Reason:

The REORG completed and the end-of-file marker was written.

Action:

None.

Messages 2–179


CADD592I — REORGANIZATION COMPLETED WITHOUT END OF FILE

Reason:

This message is issued when an extent of a multivolume file has been reorganized successfully. The end-of-file marker was not written because the entire file has not been successfully reorganized, only this particular extent.

Action:

None.

CADD593E — UNEXPECTED TAPE I/O ERROR WHILE REORGANIZATION IN PROGRESS

Reason:

An I/O error was returned reading the backup tape after a file reorganization has been initiated. DYNUTIL will close the file but it MAY NOT BE A COMPLETE FILE.

Action:

Restore the file with DYNITUL RESTORE function and repeat the BACKUP and REORG for this file.

CADD594E — UNEXPECTED TAPE I/O ERROR

Reason:

An I/O error was returned reading the backup tape during initialization of the REORG function.

Action:

REORG for the file receiving the I/O error will have been bypassed. Use DYNUTIL RESTORE function to restore the file and repeat the BACKUP and REORG for this file.

CADD595W — filename EXTENTS ARE NOT ALL ON VOLUME volid

Reason:

All extents for the file 'filename' do not reside on the indicated volume. The ALTER function will not change this file. The DELETE function will not delete this file/extent.



Action:

There are two methods for updating this file. First, to update all extents of the file on all volumes, use the CATALOG parameter. Second, to force update of this incomplete file, use the PARTIAL parameter. The use of CATALOG is preferred because it maintains the same data for all extents of this file.

CADD596I — FIRST MESSAGE WITH HIGHEST SEVERITY (CADD----)

Reason:

The message number indicated was the first message issued at the highest nonzero severity level encountered during this execution of DYNUTIL. This message can only occur in installations using VSE Release 2 and above.

Action:

None.

CADD597W — ACCESS DENIED BY EXTERNAL SECURITY FOR filename

Reason:

Access to the indicated file id has been denied by external security. The indicated file is bypassed and the security violation logged.

Action:

Contact the Security Administrator at your installation to arrange access to this file.

CADD598W — PURGE IS ONLY VALID WITH CATALOG, PURGE IGNORED

Reason:

A DYNUTIL DELETE command was entered with the PURGE operand but without the CATALOG operand.

Action:

Processing continues. PURGE is ignored and the catalog is not updated.

Messages 2–181


CADD996I — --------- user text --------

Reason:

An input data set is opened and the user has defined an open input message in the CA-Dynam Catalog.

Action:

None.

CADD997I — --------- user text --------

Reason:

An output data set is opened and the user has defined an open output message in the CA-Dynam Catalog.

Action:

None.

CADD998I — --------- user text --------

Reason:

An input data set is closed and the user has defined a close input message in the CA-Dynam Catalog.

Action:

None.

CADD999I — --------- user text --------

Reason:

An output data set is closed and the user has defined a close output message in the CA-Dynam Catalog.

Action:

None.


CADE Prefixed Messages


CADE601E — DATA-SET NAME TOO LONG FILE=filename

Reason:

The file-id is longer than 41 characters, and 3 extra characters are needed for the CA-Dynam/D partition- and CPU-id prefix. This message is issued by the CA-SYSTEM/MANAGER JCL Processor at job control time.

Action:

Use a shorter file-id.

CADE602E — DTFNAME NOT FOUND OR TOO LONG

Reason:

The DLBL lacks a valid filename field. This may be caused by misplacement of a comma. This message is issued by the CA-SYSTEM/MANAGER JCL Processor at job control time.

Action:

Correct the DLBL.

CADE603E — ALLOCATION BY NUMBER OF RECORDS INVALID FILE=filename

Reason:

The NRECS= parameter was used where it is not permitted, or it was not accompanied by LRECL= and BLKSIZE= parameters. This message is issued by the CA-SYSTEM/MANAGER JCL Processor at job control time.

Action:

Correct the DLBL. (Note that all three of these parameters must be on the first line of a continued DLBL statement.)

CADE604E — ERROR LABEL INTERFACE FILENAME=filename F/C=ffffffff R/C=rrrrrrrr

Reason:

A Label Interface error occurred processing the DLBL for the cited filename. The meanings of the F/C and R/C fields can be found in the this guide.

Messages 2–183


This message is issued by the CA-SYSTEM/MANAGER JCL Processor at job control time.

Action:

Contact Computer Associates for assistance.

CADE605E — BLOCKSIZE NOT A MULTIPLE OF RECORDSIZE FILE=filename

Reason:

The BLKSIZE= and LRECL= parameters were incorrectly used. This message is issued by the CA-SYSTEM/MANAGER JCL Processor at job control time.

Action:

Correct the DLBL.

CADE606E — ERROR OCCURRED SYSTEM ADAPTER FUNCTION function F/C=ffffffff R/C=rrrrrrrr

Reason:

A call to the cited System Adapter component failed. The meanings of the F/C and R/C fields can be found in this guide.


Action:

Contact Computer Associates.

CADE607E — CATALOG MANAGEMENT ERROR OCCURRED DDNAME=filename F/C=ffffffff R/C=rrrrrrrr

Reason:

A call to Catalog Management for the cited file name failed. The meanings of the F/C and R/C fields can be found in this guide.


Action:




CADE608E — CADJSMS0 ABEND CODE=cc

Reason:

An irrecoverable program error occurred in the CA-SYSTEM/MANAGER JCL Processor. This message is issued by the CA-SYSTEM/MANAGER JCL Processor at job control time.

Action:


CADE609E — CONFLICTING PARAMETERS DDNAME=filename

Reason:

The DLBL parameters supplied are mutually incompatible. This message is issued by the CA-SYSTEM/MANAGER JCL Processor at job control time.

Action:

See the "CA-Dynam/D For Former CA-SPACE/MANAGER Users" section of the CA-SYSTEM/MANAGER To CA-Dynam Conversion Guide, and your CA-SYSTEM/MANAGER documentation for information on correcting the DLBL.

CADE610E — file-id NOT FOUND IN THE DYNAM CATALOG

Reason:

The parameters supplied require that the file has been already cataloged. This message is issued by the CA-SYSTEM/MANAGER JCL Processor at job control time.

Action:

See the "CA-Dynam/D For Former CA-SPACE/MANAGER Users" section of the CA-SYSTEM/MANAGER To CA-Dynam Conversion Guide to learn which situations require precataloging. Correct the DLBL or define the file using the DYNCAT DEFINE function.

Messages 2–185


CADE611E — NO ROOM FOR DYNAM/D OPTIONS IN DATASET NAME file-id

Reason:

The CA-SYSTEM/MANAGER JCL Processor translates certain DLBL parameters of CA-SPACE/MANAGER to CA-Dynam/D file-id options; if the file-id is too long then it and the translated options cannot all be fitted into 44 characters. This message is issued by the CA-SYSTEM/MANAGER JCL Processor at job control time.

Action:

Either choose a shorter file-id or define this one to the catalog with some of the options so that they do not need to be supplied in the DLBL.

CADE612E — INVALID S/M DLBL PARAMETER

Reason:

A parameter unknown to CA-SYSTEM/MANAGER has been supplied. Perhaps a keyword was misspelled. This message is issued by the CA-SYSTEM/MANAGER JCL Processor at job control time.

Action:

Correct the DLBL.

CADE613W — SYSNUMBER INVALID OR NOT SUPPORTED

Reason:

A logical unit which does not conform to the rules for a programmer logical unit (SYSnnn), or whose logical unit number is outside your system's LUB table, was supplied. This message is issued by the CA-SYSTEM/MANAGER JCL Processor at job control time.

Action:

Change the logical unit, or omit it.



CADE614E — TRACKS= NRECS= or FB= NOT SPECIFIED

Reason:

A file-id which is not cataloged, or for which there is no catalog Allocation Control Record entry, was referenced. But there was no allocation information in the DLBL. This message is issued by the CA-SYSTEM/MANAGER JCL Processor at job control time.

Action:

Add the allocation information to the DLBL.

CADE615W — INVALID SPACE/MANAGER CONTINUATION DLBL STATEMENT

Reason:

Syntax rules for continuation DLBLs were not followed, or a parameter required to be on the initial statement was used on a continuation statement instead. This message is issued by the CA-SYSTEM/MANAGER JCL Processor at job control time.

Action:

Correct the DLBL.

CADE616W — PRE-OPEN WAS NOT SUCCESSFUL

Reason:

The pre-open failed for a file for which SYSnnn was used. This message is issued by the CA-SYSTEM/MANAGER JCL Processor at job control time.

Action:

The message will usually be accompanied by a CA-Dynam/D message which will make it possible to find the error and correct the DLBL.

CADE617E — INVALID ALLOCATION - DTFNAME=ccccccc

Reason:

Disk space referencing was used for an allocation amount which resulted in the System Manager Simulation Job Exit being unable to calculate a valid allocation quantity. Possible causes are: Either no version record, or no allocation control record, exists in the catalog; An allocation using dtfname-nn resulted in a zero or negative amount; more than two decimal places were used (dtfname*n.nnn).

Messages 2–187


Action:

Correct the error and rerun the job.

CADE700I — CA-CATALOG CONVERSION UTIL START dd-mmm-yyyy AT hh.mm.ss

Reason:

This message signals the start of CATCONV and documents the date/time. It is issued by the CATCONV main phase, once per run, at the start.

Action:

None.

CADE701I — READING COMMANDS FROM READER

Reason:

This message signals that CATCONV is being run as a batch job. It is issued by the CATCONV main phase, once per batch run, at the start.

Action:

None.

CADE702I — COMMAND FROM READER: .... text ....

Reason:

This message documents the command given. It is issued by the CATCONV main phase, once for each SYSIPT command read.

Action:

None.

CADE703I — REL. r.v ** CA-Dynam REL. r.v ddddpplll

Reason:

This message indicates which of the CATCONV and CA-Dynam release numbers and the CA-Dynam genlevel are in use. It is issued by the CATCONV main phase, once per run, at the start.



Action:

Report this information to Computer Associates if problems occur.

CADE704I — READING COMMANDS FROM CONSOLE

Reason:

Either CATCONV is being run from the console, or it was run in batch, but reader EOF was reached without a valid command being read. This message is issued by the CATCONV main phase, once, at the start of interactive processing.

Action:

None.

CADE705D — PLEASE ENTER COMMAND OR NOTHING TO END JOB

Reason:

CATCONV wants you to enter a command. This message is issued by CATCONV main phase whenever a console command is wanted.

Action:

Enter a command, or if you want to end the job, enter a nullstring.

CADE706I — COMMAND FROM CONSOLE: .... text ....

Reason:

This message documents the command entered. It is issued by the CATCONV main phase, once for each console command entered.

Action:

None.

Messages 2–189


CADE707W — COMMAND INVALID OR UNKNOWN

Reason:

This message is issued by the CATCONV main phase after any invalid command.

Action:

Consult the CA-SYSTEM/MANAGER To CA-Dynam Conversion Guide and reenter the command correctly.

CADE708I — CATALOG filename BEING ENQUEUED

Reason:

This message documents CATCONV's attempt to enqueue the CA-Dynam Catalog. It is issued by the CATCONV main phase, once, at the start of processing the first command which requires catalog I/O.

Action:

None.

CADE709E — CATALOG filename NOT ENQUEUED, JOB ENDING

Reason:

This message is probably due to a hardware error if processing a new catalog, or possibly the result of another partition or system "holding" the catalog. It is issued by the CATCONV main phase, after finding that the catalog cannot be enqueued.

Action:

Try to release the catalog using DYNCAT DEQUEUE. If this does not work, reinitialize the catalog with a different track allocation.



CADE710I — CATALOG filename ENQUEUED SUCCESSFULLY

Reason:

CATCONV was able to enqueue the catalog. This message is issued by the CATCONV main phase, once per run, after having enqueued the catalog.

Action:

None.

CADE711I — CONVERSION PHASE progname STARTING

Reason:

The conversion phase was loaded successfully and is being linked to by CATCONV. This message is issued by the CATCONV main phase prior to passing control to each conversion phase requested.

Action:

None.

CADE712I — CONVERSION PHASE progname COMPLETED

Reason:

The conversion phase has completed successfully. This message is issued by the CATCONV main phase after receiving control back from each conversion phase requested.

Action:

None.

CADE713I — CATALOG filename DEQUEUED

Reason:

The catalog has been released by CATCONV. This message is issued by the CATCONV main phase, once, at end of the run.

Action:

None.

Messages 2–191


CADE714I — CA-CATALOG CONVERSION UTILITY END

Reason:

This message documents the end of the CATCONV run. It is issued by the CATCONV main phase, once, at end of the run.

Action:

None.

CADE715W — READER EOF, NO VALID COMMANDS

Reason:

All SYSIPT commands that were read are in error. This message is issued by the CATCONV main phase, once, during batch run at SYSIPT EOF, if SYSIPT contained no valid commands.

Action:

Enter the commands through the console, when prompted for them.

CADE716I — STARTING .... text ....

Reason:

This message documents the start of a logical processing phase. It is issued by logical processing routines in the conversion phases.

The following texts are used by the CA-TAPE/MANAGER Catalog conversion phases (CACUTMCA and CACUVMCA):

STARTING TAPE VOLUME RANGE PROCESSING STARTING TAPE VOLUME TABLE PROCESSING STARTING FILE DEFINITION PROCESSING STARTING GENERATION DEFINITION PROCESSING STARTING MULTIFILE SET LINKING

The following text is used by the CA-TAPE/MANAGER long file-id punching phases (CACUTPRA and CACUVPRA):

STARTING SCANNING TAPE FOR LONG FILE-IDS

The following texts are used by the CA-TAPE/MANAGER file renaming phase (CACUTFRA):

STARTING SORTING CADJTFR0 FOR DUPLICATES STARTING RENAMING FILES IN DYNAM CATALOG STARTING BACKING OUT FILE RENAMES



The following text is used by the CA-SPACE/MANAGER volid listing phases (CACUSLDA and CACUULDA):

STARTING SCAN OF INPUT TAPE

The following text is used by the CA-SPACE/MANAGER Catalog conversion phases (CACUSMCA and CACUUMCA):

STARTING FILE DEFINITION PROCESSING

The following text is used by the CA-SPACE/MANAGER VTOC conversion phase (CACUSVCA) and CA-SPACE/MANAGER VTOC restore phase (CACUSVRA):

STARTING PROCESSING INPUT TAPE RECORDS

Action:

None.

CADE717I — FINISHED .... text ......... nnnn items processed

Reason:

This message documents the completion of a logical processing phase and informs you of the number of items processed. It is issued by logical processing routines in the conversion phases. If one of these messages is not issued, it means that the function was suppressed or the count was zero.

The following texts are used by the CA-TAPE/MANAGER Catalog conversion phases (CACUTMCA and CACUVMCA):

FINISHED TAPE VOLUME RANGE PROC. nnnn RANGES FROM INPUT FINISHED nnnn RANGES DEFINED FINISHED TAPE VOLUME TABLE PROC. nnnn VOLSERS DEFINED FINISHED FILE DEFINITION PROC. nnnn FILES DEFINED FINISHED GENERATION DEFINITION nnnn GENS DEFINED FINISHED MULTIFILE SET LINKING nnnn M/F SETS LINKED

The following text is used by the CA-TAPE/MANAGER long file-id punching phases (CACUTPRA and CACUVPRA):

FINISHED SCANNING TAPE nnnn FILE-IDS PUNCHED

The following texts are used by the CA-TAPE/MANAGER file renaming phase (CACUTFRA):

FINISHED SORTING CADJTFR0 nnnn ENTRIES IN TABLE FINISHED nnnn DUP. NEW NAMES FINISHED RENAMING FILES nnnn FILES RENAMED OK FINISHED nnnn NEW NAMES REJ. FINISHED nnnn FILES NOT FOUND FINISHED BACKING OUT RENAMES nnnn BACKED OUT OK FINISHED nnnn OLD NAMES REJ. FINISHED nnnn NEW NAMES MISSING

Messages 2–193


FINISHED TAPE FILE RENAME ATTEMPT 0 FILES RENAMED FINISHED FILE RENAMING OK nnnn FILES RENAMED

The following text is used by the CA-SPACE/MANAGER volid listing phases (CACUSLDA and CACUULDA):

FINISHED SCAN OF INPUT TAPE nnnn DISK VOLIDS FOUND

The following texts are used by the CA-SPACE/MANAGER Catalog conversion phases (CACUSMCA and CACUUMCA):

FINISHED FILE DEFINITION PROC. nnnn FILES DEFINED FINISHED nnnn VSAM DEFINED FINISHED nnnn VSAM NOT DEF'D FINISHED nnnn OTHER NOT DEF'D FINISHED nnnn DYN. VERS. DEF'D FINISHED nnnn ALLOCS. DEFINED FINISHED WRITING VTOC CONV. FILE nnnn RECORDS WRITTEN

The following texts are used by the CA-SPACE/MANAGER VTOC conversion phase (CACUSVCA) and CA-SPACE/MANAGER VTOC restore phase (CACUSVRA):

FINISHED PROCESSING INPUT TAPE nnnn RECORDS READ FINISHED nnnn INVALID RECORDS FINISHED nnnn DSNS MOD. ALL OK FINISHED nnnn DSNS UNCH. ALL OK FINISHED nnnn DSNS PARTLY MOD. FINISHED nnnn DSNS ALL MISSING FINISHED nnnn ENTRIES PROCESSED FINISHED nnnn ENTRIES CHANGED FINISHED nnnn ENTRIES UNCHANGED FINISHED nnnn ENTRIES MISSING FINISHED nnnn VOL OFFLINE ENT. FINISHED nnnn 2-NAME ENTRIES

Action:

Check the counts for reasonableness.

Note that for a CA-SPACE/MANAGER Catalog conversion, the number of allocations defined will exceed the number of file-ids defined by the number of secondary extents owned by static files, less the number of retained dynamic files for which no allocation information was available. The total number of files read from input is the sum of FILES DEFINED, VSAM NOT DEFINED, and OTHER NOT DEFINED (VSAM DEFINED is included in FILES DEFINED).

For the 'RENAME TAPEMAN FILES' command, the issuance of messages for 'OLD NAMES REJECTED' or 'MISSING NEW NAMES' at the end of the 'BACKING OUT RENAMES' logical phase will be accompanied by message CADE787A. This implies that you need to rerun the CA-TAPE/MANAGER Catalog conversion before rerunning the 'RENAME TM FILES' command. If errors persist, contact Computer Associates.



CADE718E — ........ text ...........

Reason:

An error condition has been encountered indicating corruption of the source catalog or VTOCs, or failure to follow instructions. See the "CA-SPACE/MANAGER Catalog Corruption" section of the CA-SYSTEM/MANAGER To CA-Dynam Conversion Guide, where the texts are explained.

This message is issued by the CA-SPACE/MANAGER Catalog phases (CACUSMCA and CACUUMCA) and VTOC conversion/restore phases (CACUSVCA and CACUSVRA).

Action:

Correct the error, if possible, in the old catalog/VTOCs, and rerun the conversion. If necessary, contact Computer Associates for assistance.

CADE719W — ........ text ...........

Reason:

A condition which may produce an undesirable result has been encountered. See the section entitled "CA-SPACE/MANAGER Catalog Corruption" found in the CA-SYSTEM/MANAGER To CA-Dynam Conversion Guide for an explanation of the texts.

This message is issued by the CA-SPACE/MANAGER Catalog conversion phases (CACUSMCA and CACUUMCA) and VTOC conversion/restore phases (CACUSVCA and CACUSVRA).

Action:

Take corrective action if you want a different result. If necessary, rerun the conversion. Contact Computer Associates for assistance.

CADE720D — ........ text ...........

Reason:

A condition has been encountered for which a self-explanatory message has been supplied. This message is issued by various CATCONV phases.

Action:

Reply as instructed in the message.

Messages 2–195


CADE722I — LOGICAL EOF FROM CATALOG filename

Reason:

This message indicates that an EOF was found during sequential reading of the catalog. This message is issued by various CATCONV phases.

Action:

None.

CADE723W — TAPES IN PENDING STATUS - TREATED AS NON-PENDING

Reason:

At least one of the tapes in the input was in pending status, probably due to a failure to run SPLISTF with the UPDATE option immediately prior to running CACUSMB2. This message is issued by the CA-TAPE/MANAGER Catalog conversion phases (CACUTMCA and CACUVMCA) in the end-of-program summary.

Action:

Rerun the whole conversion making sure to follow the instructions exactly.

CADE725W — DELETED GENERATIONS ENCOUNTERED - IGNORED

Reason:

At least one input generation was in deleted status. This message is issued by the CA-TAPE/MANAGER Catalog conversion phases (CACUTMCA and CACUVMCA), and CA-SPACE/MANAGER Catalog conversion phases (CACUSMCA and CACUUMCA) in the end-of-program summary.

Action:

CACUTMCA and CACUVMCA issue message CADE738W for each deleted generation. Check the output for these messages and determine if you want to take corrective action.

CACUSMCA and CACUUMCA issue message CADE719W for each deleted generation of a dynamic file, but only if you use MSGLEVEL 4. Messages CADE719W are issued for each deleted static file if you run with the NODSTAT option, but can be suppressed by using MSGLEVEL 1.



CADE726W — FILES WITHOUT ACTIVE VERSIONS - DEFINED ANYWAY

Reason:

At least one input record was for a file which was defined, but had no active versions. In the cases of CACUSMCA and CACUUMCA, the "DEFINED ANYWAY" applies to those dynamic files without active versions which were retained in the catalog by using the INCDGdel and/or INCDKdel options.

This message is issued by the CA-TAPE/MANAGER Catalog conversion phases (CACUTMCA and CACUVMCA), and CA-SPACE/MANAGER Catalog conversion phases (CACUSMCA and CACUUMCA), in the end-of-program summary.

Action:

None.

CADE727W — VAULT MOVE SPECS FOR MORE THAN 100 GENS - DISCARDED

Reason:

At least one file had a vault rotation scheme involving more than 100 versions. CATCONV has truncated the scheme at 100 volumes; all active versions in excess of 100 will return to the default location (normally location A, the data center).

This message is issued by the CA-TAPE/MANAGER Catalog conversion phases (CACUTMCA and CACUVMCA) in the end-of-program summary.

Action:

None.

CADE728E — INPUT NOT CORRECTLY SORTED - STOPPING LOGICAL PHASE

Reason:

This message probably results from a failure to run SPSTART immediately before running CACUSMB2. (See the "Dumping Your CA-SYSTEM/MANAGER Catalog" section of the CA-SYSTEM/MANAGER To CA-Dynam Conversion Guide.)

It is issued by the CA-TAPE/MANAGER Catalog conversion phases (CACUTMCA and CACUVMCA) and the CA-SPACE/MANAGER Catalog conversion phases (CACUSMCA and CACUUMCA) if out-of-order input is encountered.

Messages 2–197


Action:

Rerun the whole conversion making sure to follow the instructions exactly.

CADE729E — CONVERSION PHASE progname NOT AVAILABLE

Reason:

The load failed for the conversion phase required for the last command accepted by CATCONV. You may have accidentally used a command which is accepted but for which the conversion phase was not included in your product tape. This message is issued by the CATCONV main phase.

Action:

If the command is documented in this manual, be sure you installed the phase correctly, and that the required load library is available.

CADE730I — LINKED FILE nnnnn: file-id

Reason:

The named file-id has been linked into a multifile set as the nth member. This message is issued by the CA-TAPE/MANAGER Catalog conversion phases (CACUTMCA and CACUVMCA).

Action:

Examine the series of all these messages and be sure that what you intended has been done. If not, either rerun the conversion with the NOMFlink option or contact Computer Associates for advice on how to modify the links.

CADE731I — END OF MULTIFILE SET

Reason:

CATCONV completed the linking of a multifile set. This message is issued by the CA-TAPE/MANAGER Catalog conversion phases (CACUTMCA and CACUVMCA).

Action:

None.



CADE732E — ACTIVE TAPE, NO CONNECTED FILE: volser

Reason:

The input catalog contained an entry for an active tape but there was no corresponding file entry in the catalog. Note that CATCONV has made this volume a SCRATCH tape in the CA-Dynam Catalog. This message is issued by the CA-TAPE/MANAGER Catalog conversion phases (CACUTMCA and CACUVMCA).

Action:

Try to determine what is on the tape and, if necessary, add the files to the CA-Dynam Catalog with the DYNCAT ADD command. (This will cause the tape to be given ACTIVE status.) You may have intentionally deleted the file; check the CADE738W message texts issued during the conversion.

CADE733E — SCRATCH MADE ACTIVE, HAS CONNECTED FILES: volser

Reason:

The input catalog contained an entry for a scratch tape for which there was a corresponding entry for an active file. This message is issued by the CA-TAPE/MANAGER Catalog conversion phases (CACUTMCA and CACUVMCA).

Action:

None. CATCONV has changed the tape's status to active. If in doubt, check the tape to see if the file really is still on it.

CADE734E — TAPE DUPLICATE REFERENCE: volser

Reason:

The input catalog contained more than one file entry, each of which is pointing to the same position on one tape. This message is issued by the CA-TAPE/MANAGER Catalog conversion phases (CACUTMCA and CACUVMCA).

Action:

Determine which of the files is actually on the tape (use the trial CA-Dynam/T SCRATCH run output to find the file-ids), correct the catalog by deleting all the files involved, and then add the correct ones back in.

Messages 2–199


CADE735I — TIME NOW: hh.mm.ss ON dd-mmm-yyyy

Reason:

This message documents the duration of conversion phase processing. It is issued by the CATCONV main phase after the return from a conversion phase.

Action:

None.

CADE736I — nnnn NOW PROCESSED ....

Reason:

CATCONV has just finished processing another set of items in the logical phase currently in progress. The increment varies; it is usually 500 or 100. This message is issued by the CATCONV conversion phases.

Action:

None.

CADE737W — NO ACTIVE VERSIONS: file-id

Reason:

CATCONV has determined that the named fileid has no active versions. This message is issued by the CA-TAPE/MANAGER Catalog conversion phases (CACUTMCA and CACUVMCA). Its issuance and meaning are affected by the NOINact option.

Running without NOINact, the file has been defined despite having no active versions. The message is suppressed at MSGlevel 1 or lower.

Running with NOINact, the file has not been defined and the message only appears at MSGlevel 3 or higher.

Action:

None.



CADE738W — message: gen# file-id

Reason:

This message is issued by the CA-TAPE/MANAGER Catalog conversion phases (CACUTMCA and CACUVMCA). Refer to the reason that corresponds with the contents of your "message".

Content Reason

DELETED The named (absolute) version of this file was flagged in the source (old) catalog as being deleted. CATCONV will ignore this version. You may get message CADE732E for the tape(s) this version was on. If you get this message you will also get message CADE725W once, at the end of the run.

NO VSN The named (absolute) version of this file is on an undefined tape. The tape is identified in message CADE753E which follows.

M/F ERR The named (absolute) version of this file is part of a multifile set, some of whose members have been deleted. Also see the accompanying message CADE754W.

O'FLOW The named (absolute) version of this file resides on more than 33 tape volumes; only the first 33 are registered by CATCONV. This is explained in an immediately following message CADE718E.

Action:

None, except for NO VSN; see message CADE753E.

CADE739I — PARSED OK TO HERE ------------------+

Reason:

The command parser found a keyword which was not valid in the context as interpreted to that point. The "+" will be either immediately before or immediately after the invalid keyword (depending on the type of error). This message is issued by the CATCONV main phase, command parser routine after repeating the invalid or unrecognized command.

Action:

See the "Conversion Steps" chapter of the CA-SYSTEM/MANAGER To CA-Dynam Conversion Guide to determine what is wrong with the command, and enter the correct command when prompted. If you cannot find any error, contact Computer Associates.

Messages 2–201


CADE740E — REQUIRED PRODUCT COMPONENT CA-Dynam/x NOT ACTIVE/NOT INSTALLED

Reason:

The conversion requested in the input command requires you to have a CA-Dynam component installed which you do not have installed or is not active; "x" can be "D" or "T". This message is issued by the CATCONV main phase before passing control to a conversion phase.

Action:

Check that you have performed the installation steps correctly and that your IPL has brought up CA-Dynam correctly. Be sure you have entered the correct command for the conversion you want to perform.

CADE741I — MESSAGES FOR FILE: file-id

Reason:

This message identifies the file-id for which the following error or warning message(s) were issued. It is issued by many of the conversion phases only once for a given file-id.

Action:

None.

CADE742I — TYPE: abcdef NGENS: nnnn ABSGEN: nnnn RELGEN: nnnn

Reason:

This message identifies the version for which the following error or warning message(s) were issued. The various items in this message are explained in the section entitled "CA-Dynam/D For Former CA-SPACE/MANAGER Users" found in the CA-SYSTEM/MANAGER To CA-Dynam Conversion Guide.

The message is issued by the CA-SPACE/MANAGER Catalog conversion phases (CACUSMCA and CACUUMCA), never more than once for a given version of a given file.

Action:

None.



CADE743W — VOLID vvvvvv: .... text ....

Reason:

This message informs you of an irregularity encountered processing an extent or VTOC entry belonging to a file on the named disk pack. (The file in question is identified by preceding messages CADE741I and/or CADE742I.) It may be followed by an error or warning message giving more detailed information.

As used in end-of-run summaries, it gives some concise information about the whole pack.

The message is issued by the CA-SPACE/MANAGER Catalog conversion phases (CACUSMCA and CACUUMCA) and CA-SPACE/MANAGER VTOC conversion/restore phases (CACUSVCA and CACUSVRA), only once for a given file-id/volid combination. It is also issued by all CA-SPACE/MANAGER conversion phases during the end-of-run summary.

Action:

See the "CA-Dynam/D For Former CA-SPACE/MANAGER Users" section of the CA-SYSTEM/MANAGER To CA-Dynam Conversion Guide for actions appropriate to various texts.

CADE744W — NO POOLS DEFINED BUT "NOPOOL" OPTION NOT INVOKED

Reason:

Either no CASATABA phase was created to define your DASD pools, or something you are not aware of went wrong (assembler error, link-edited to wrong library, etc.), but the "NOPOOL" option was not invoked.

This message is issued by the CATCONV main phase service routine which builds a pool-real volid cross-reference table used by some disk management conversion phases.

Action:

None (see explanation of CADE745D, which is always issued together with this message).

Messages 2–203


CADE745D — ENTER ANY REPLY TO GO ON W/ "NOPOOL", "A" TO ABORT

Reason:

Message CADE744W has been issued, and CATCONV needs a response to proceed. This message is issued by the CATCONV main phase service routine which builds a pool-real volid cross-reference table used by some disk management conversion phases.

Action:

If you forgot to use the NOPOOL option, enter EOB. If you want to use DASD pooling enter "A", and then see the "Conversion Steps" chapter of the CA-SYSTEM/MANAGER To CA-Dynam Conversion Guide to learn how to create a pooling table (if you haven't already done so). If you already created a pooling table, find out why it was not accessible to CATCONV and correct the error.

CADE746E — REQUIRED PHASE/TABLE progname NOT FOUND

Reason:

Either a required phase was not created, or something you are not aware of went wrong (assembler error, link-edited to wrong library, etc.) This message is issued by various routines which operate on user-generated tables.

Action:

Determine why the phase is not accessible, correct the error, and resubmit the job.

CADE747E — CADJVCB0 TABLE HAS DIFFERENT FBA DEV. FACTORS

Reason:

The factor values which were supplied for FBA devices in the CADJVCB0 table are not all the same; that is, the factors not equal to 1. This message is issued by the CA-SPACE/MANAGER Catalog conversion phases (CACUSMCA and CACUUMCA).

Action:

Examine the assembly listing of the CADJVCB0 table, find and correct the error, and resubmit the job.



CADE748W — IGNORING INVALID FILE-ID IN INPUT, FIRST 4 CHARS ARE (HEX) xxxxxxxx

Reason:

An invalid file-id (usually low-values) was found in the input file. This message will be issued for any file-id whose first character has a hex value lower than x'40' (space). It is issued by the CA-SPACE/MANAGER Catalog conversion phases (CACUSMCA and CACUUMCA) and CA-TAPE/MANAGER Catalog conversion phases (CACUTMCA and CACUVMCA).

Action:

None.

CADE749W — IGNORING COMMAND AS COMMENT

Reason:

The last command line received began with an asterisk (*). This message is issued by the CATCONV main phase command processor.

Action:

None.

CADE750W — NO MORE NON-INTERACTIVE MESSAGES ON CONSOLE

Reason:

A NOCONsol command has been given; all messages will still be issued to the printer. This message is issued by the CATCONV main phase command processor.

Action:

None.

CADE751D — ENTER CORRECTED COMMAND OR NOTHING TO CONTINUE READING

Reason:

A command line read from the reader was in error. This message is issued by the CATCONV main phase command processor.

Messages 2–205


Action:

Find the cause of the error and enter a corrected command line, or enter EOB to continue reading.

Reenter the incorrect line from the beginning, omitting or correcting the incorrect keyword. This facility will not work correctly if the error was found in a continuation line in the input; in such cases you are advised to cancel and resubmit the job, or, if the incorrect command was the only one in the input, enter EOB until the message CADE715W is issued, after which you can reenter the command in interactive mode.

If the line in error was continued, the correction must also be continued; if the line in error was not continued, the correction must not be continued. If correction within these limitations is not possible, you must proceed as above.

CADE752E — >>> VOLID TABLE OVERFLOW - PREMATURE TERMINATION <<<

Reason:

The input referenced many more volids than are online, so the program ran out of space to record processing information about the volids. (The space allocated is sufficient for 20 volids plus twice the number that are online.)

This message is issued by the CA-SPACE/MANAGER Catalog conversion phases (CACUSMCA and CACUUMCA) and VTOC conversion/restore phases (CACUSVCA and CACUSVRA).

Action:

For the CA-SPACE/MANAGER Catalog conversion, reinitialize the catalog (or RESTORE it if you are converting an existing catalog), and resubmit the conversion job having either added the:

■ LIST SM VOLIDS command prior to the CONVERT SM CATALOG command, or

■ NVOLid nnn option to the CONVERT SM CAT command, with nnn at least as large as the number reported by LIST SM VOLIDS.

For the CA-SPACE/MANAGER VTOC conversion, you may back out the incomplete conversion by using the RESTORE SM VTOCS command, but this is not necessary. Then restart the VTOC conversion after adding the NVOLid nnn option with nnn at least as large as the number of volids reported as being affected in the catalog conversion end-of-run summary.



CADE753E — VSN vvvvvv REFERENCED, WAS NEVER DEFINED

Reason:

A file was encountered on the named tape, but the tape volume serial was never defined in the CA-Dynam Catalog. Most likely, overuse of the MINVsn or MAXVsn options prevented the volser from being defined.

This message is issued by the CA-TAPE/MANAGER Catalog conversion phases (CACUTMCA and CACUVMCA).

Action:

Reinitialize the catalog (or RESTORE it if you are converting into an existing catalog) and resubmit the conversion job having ensured that all volsers named in these messages are included in the range MINVsn to MAXVsn.

If the problem is not related to the MINVsn/MAXVsn options, contact Computer Associates for advice.

CADE754W — PRIOR FILE IN SET MISSING - VOL. SEQ. # MAY BE WRONG

Reason:

A file, part of a multifile set, was encountered but one or more of the preceding files in the same set have been deleted from the catalog. As a result, the volume sequence number for the file within the set may be computed incorrectly.

This message is issued by the CA-TAPE/MANAGER Catalog conversion phases (CACUTMCA and CACUVMCA).

Action:

None. The possible error in the volume sequence number should have no effect on the accessibility of the file for input.

CADE755D — PLEASE ENTER COMMAND CONTINUATION

Reason:

The last command line entered from the console had a continuation character (-) at the end. CATCONV now needs the continuation line to complete processing of the command. This message is issued by the CATCONV main phase command processor.

Messages 2–207


Action:

Continue entering options appropriate to the command. If you have changed your mind and have no more options, enter EOB.

CADE756D — REALLY INITIALIZE CATALOG ddname (YES/NO)?

Reason:

The INITIAL/INITCAT command that was issued must be confirmed or canceled. At this point, it is advisable that you verify the name of the catalog. This message is issued by the CATCONV main phase catalog initialization routine.

Action:

Enter YES if you want the initialization to be carried out, NO if you do not.

CADE757E — INVALID RESPONSE, PLEASE RE-ENTER

Reason:

A prompt requiring a limited choice of responses was issued and the response given was not among the choices offered. The prompt will be repeated. This message is issued by any CATCONV routine.

Action:

None.

CADE758I — CATALOG ddname IS BEING INITIALIZED

Reason:

The INITIAL/INITCAT command was issued and confirmed with a YES response to CADE756D. Initialization is now in progress. This message is issued by the CATCONV main phase catalog initialization routine.

Action:

None.



CADE759I — ----------------------

Reason:

This message makes the output easier to read. It is issued by various conversion phases which issue more than one line of messages per file or group of files.

Action:

None.

CADE760E — ALL OF THESE FILES SAME NEW NAME: new file-id

Reason:

The same new name was used for more than one old file-id when the TMRENAME option records, which were assembled into the CADJTFR0 table, were edited. The relevant old file-ids are those mentioned in CADE741I messages starting after the last CADE759 message issued before this one.

This message is issued by the CA-TAPE/MANAGER file rename phase (CACUTFRA).

Action:

Use this output to guide you in reediting the option records prior to reassembling the CADJTFR0 table.

CADE761E — FILE NOT FOUND IN CATALOG

Reason:

The file named in the immediately preceding message CADE741I, which has a TMRENAME entry in the CADJTFR0 table, was not found in the CA-Dynam Catalog. You may have accidentally changed the OLD= parameter in the TMRENAME option record, or you may have run the CA-TAPE/MANAGER Catalog conversion using the NOINACT option, but punched the TMRENAME option records without using NOINACT.

This message is issued by the CA-TAPE/MANAGER file rename phase (CACUTFRA).

Action:

Determine the cause of the discrepancy, reedit the TMRENAME option records, reassemble and relink the CADJTFR0 table, and retry the 'RENAME TM FILES' command.

Messages 2–209


CADE762E — NEW NAME ALREADY IN CATALOG: new name

Reason:

For the file named in the immediately preceding CADE741I message, the TMRENAME option record NEW= parameter duplicates a file-id already present in the CA-Dynam Catalog. The duplicate new name is given in this message. The already-existing file may be either a disk or a tape file; you may or may not want to retain it in the CA-Dynam Catalog. This message is issued by the CA-TAPE/MANAGER file rename phase (CACUTFRA).

Action:

Determine the cause of the duplication, and either delete the already-existing file, or reedit the TMRENAME option record and reassemble and relink the CADJTFR0 table. Then retry the 'RENAME TM FILES' command.

CADE763A — ===> CORRECT, RE-ASSEMBLE, AND RE-LINK CADJTFR0 TABLE

Reason:

Error conditions as specified in the preceding messages CADE760E, CADE761E, and CADE762E have been encountered during the run (see SYSLST output). This message is issued by the CA-TAPE/MANAGER file rename phase (CACUTFRA) once, at end-of-run, if errors have been detected.

Action:

Determine the causes of the errors, take the appropriate action for your situation, and retry the 'RENAME TM FILES' command.

CADE764E — ADJACENT MIN- OR MAXVSN VALUES: uuuuuu AND vvvvvv

Reason:

Two MINVSN values without an intervening MAXVSN value, or vice versa, have been given for one range. This message is issued by the CA-TAPE/MANAGER Rel. 5.x catalog conversion phase (CACUVMCA) during the initial volume range processing.

Action:

Correct the command and retry it.



CADE765E — CONVERSION PHASE TERMINATING DUE TO PARAMETER ERRORS

Reason:

In the command, errors were present which could only be detected after the start of conversion phase processing. Case-specific messages will have been issued. This message is issued by any conversion phase that processes parameters beyond what is done by the CATCONV main phase command parsing processor.

Action:


CADE766I — VOLUME RANGE DEFINED: uuuuuu THROUGH vvvvvv

Reason:

This message documents the ranges that are being defined as a result of existing ranges interacting with MINVSN/MAXVSN parameters supplied in the command. It is issued by the CA-TAPE/MANAGER Rel. 5.x catalog conversion phase (CACUVMCA) at the end of initial volume range processing.

Action:

None.

CADE767D — ===> REWINDING TAPE FOR SECOND PASS; ENTER ANY RESPONSE WHEN READY

Reason:

This message tells you what is happening. By waiting until the rewind is complete before responding, you avoid having to respond to OPEN error messages. It is issued by any conversion phase that does more than one pass on the input tape.

Action:

Wait until the tape finishes rewinding and enter any response.

Messages 2–211


CADE768W — FILE(S) WITH MORE THAN 33 VOLUMES - EXCESS DISCARDED

Reason:

This message calls your attention to the occurrence, at least once, of this error. Specific instances are documented by messages CADE738W giving the absolute generation number and file-id, with the text "O'FLOW", and message CADE718E with an explanatory text. The message is issued by the CA-TAPE/MANAGER Rel. 5.x catalog conversion phase (CACUVMCA) at end of the generation definition logical phase.

Action:

Find the files in the CA-TAPE/MANAGER Catalog and add the volsers after the first thirty-three volumes using DYNCAT ADD or the DYNT transaction.

CADE769E — MIN- or MAXVSN VALUE NOT IN ANY RANGE, IGNORED: vvvvvv

Reason:

A MINVSN or MAXVSN value in the command was not found to be in any range defined in the CA-TAPE/MANAGER Catalog. This message is issued by the CA-TAPE/MANAGER Rel. 5.x catalog conversion phase (CACUVMCA) at the end of the volume range processing logical phase.

Action:


CADE780A — IJSYSBK SHOULD BE ALLOCATED TO progname OUTPUT TAPE

Reason:

This message documents the expected source of the input. It is issued by the CATCONV main phase service routines which open input tapes, once, prior to opening any tape.

Action:

If in doubt that the correct tape will be read, end the job when the prompt is given.



CADE781I — progname RUN DATE/TIME STAMP: mm/dd/yy hh:mm

Reason:

This message documents the time stamp from the precursor program run. It is issued by the CATCONV main phase service routines which open input tapes, once after opening and once prior to closing any tape.

Action:

Check the date and time when examining the output, especially if there seem to be inconsistencies.

CADE782A — ===> INPUT IRREGULARITIES AFFECTING CONVERSION ACCURACY

Reason:

This message is always issued together with CADE783A. One or more conditions possibly requiring a rerun have been detected. It is issued by the CATCONV main phase on return from any conversion phase which has encountered invalid input data.

Action:

Examine the output carefully, especially any E-type messages that were issued. Check the CA-SYSTEM/MANAGER To CA-Dynam Conversion Guide to decide how serious the errors are. If necessary, rerun the whole conversion from start to finish after taking indicated corrective actions. If problems persist, contact Computer Associates.

CADE783A — ===> PLEASE REREAD INSTRUCTIONS, IF NECESSARY DO RERUN

Reason:

This message is always issued together with CADE782A. One or more conditions possibly requiring a rerun have been detected. The message is issued by the CATCONV main phase on return from any conversion phase which has encountered invalid input data.

Action:

See the "Action" for CADE782A.

Messages 2–213


CADE784D — ===> AWAITING ANY REPLY TO CONTINUE, "A" TO ABORT

Reason:

Confirmation is wanted to ensure that everything is correct up to this point. This message is issued by various CATCONV main phase service routines.

Action:

Enter nullstring if you think everything is OK, otherwise enter "A" to abort the run and save some waiting time.

CADE785E — ===> IRREGULARITIES IN INPUT, POSSIBLE SOURCE CATALOG CORRUPTION

Reason:

There were inconsistencies in the input pointing to corruption of the source catalog. This message is issued by the CATCONV main phase, on return from any conversion phase which processes input from a source catalog.

Action:

Examine the various messages that were issued in specific instances and decide what you have to do. Corrective action on the converted catalog may be possible. But you may have to go back to the original environment, correct the errors in the old catalog, and then rerun the conversion. You may want to contact Computer Associates for advice.

CADE786E — dtfname: WRONG TAPE MOUNTED, CREATED BY progname

Reason:

During OPEN processing, the service routine checks the tape file header record to see if the precursor program name agrees with that given in the preceding message CADE780A. If not, this message is issued and processing of the CATCONV command is terminated.

This message is issued by the CATCONV main phase service subroutines which read input tapes, at OPEN time, if the wrong tape is mounted.

Action:

If necessary (multiple-command job), cancel the CATCONV run. Then rerun being sure to mount the correct input tape. You may have to change the CATCONV command if, for example, it appears that you are converting CA-SYSTEM/MANAGER Rel. 5 (CACUSMB2/CACUSMCA named as precursor in message CADE780A, but the tape was actually created by CACUUMB2/CACUUMCA).



CADE787A — ===> PROGRAM LOGIC ERRORS FOR COMMAND, JOB TERMINATING

Reason:

During conversion phase processing, noncritical logic errors were detected. There will have been other messages issued which indicate what sort of errors occurred. See the documentation for these messages find out how serious the errors are.

This message is issued by the CATCONV main phase on return from a conversion phase.

Action:

Using the documentation for the accompanying messages as a guide, try to take corrective action. If logic errors persist, contact Computer Associates.

CADE789W — DIAGNOSTIC DUMP PRODUCED

Reason:

An unexpected condition has arisen, but it did not cause a critical error. This message is issued by the CATCONV main phase once (conditionally), at the end of the run.

Action:

Contact Computer Associates for advice. Depending on the information in the dump, your conversion may or may not have been successful. Examine all output with extra care.

CADE790E — INTERNAL .... type .... ERROR HAS OCCURRED

Reason:

An unexpected condition has arisen, causing a critical error. The "type" text can be one of the following:

■ SYSTEM ADAPTER

■ PROGRAM LOGIC

■ CATALOG MNGMT.

■ CA SERVICE RTN

This message is issued by the CATCONV main phase on an abnormal return from any conversion phase.

Messages 2–215


Action:


CADE791E — SNAP DUMP REQUESTED BY progname

Reason:

The named program has requested the dump. This message is issued by the CATCONV main phase on an abnormal return from any conversion phase.

Action:


CADE792E — CAUSE: .... text ....

Reason:

The condition described in the message has arisen. This message is issued by the CATCONV main phase on an abnormal return from any conversion phase, if the programmer has provided an explanatory text.

Action:


CADE793E — PLEASE KEEP DUMP(S), CALL COMPUTER ASSOCIATES FOR HELP

Reason:

A critical error has occurred and/or a diagnostic dump has been issued. This message is issued by the CATCONV main phase, at end-of-job if any diagnostic or abend dump has been issued.

Action:




CADE794E — CATALOG: filename ** ACCESS F/C=nnnn, R/C=nn, E/C=nn

Reason:

Catalog Management has returned the named R/C and E/C on a call using the named F/C. This message is issued by the CATCONV main phase at the end-of-job if the run has been abnormally terminated due to a Catalog Management error.

Action:

Contact Computer Associates unless the codes are R/C=08, E/C=64, in which case you should try creating a larger CA-Dynam Catalog and rerunning CATCONV.

CADE801E — STEP xxxxxxxx NOT FOUND

Reason:

GOTO Step processing is in effect and the label for the indicated step name was not found.

Action:

Correct the JCL and resubmit the job.

CADE802I — HOLD PARAMETER IGNORED ON THE FOLLOWING CARD:

Reason:

The HOLD parameter was specified on a STEP card. HOLD processing is not supported by the CA-Dynam Job Exit.

Action:

None.

CADE803E — SUBSTITUTION CANNOT BE PERFORMED FOR THE FOLLOWING STATEMENT:

Reason:

Variable substitution is being used for the indicated statements but the resulting card length after substitution is greater than 71 characters.

Messages 2–217


Action:

The JCL statement is passed unsubstituted to job control. Correct the JCL statement so the fully substituted length of the card is less than 72 characters.

CADE804E — INVALID SET= IN THE FOLLOWING STEP CARD:

Reason:

SET= was specified on a STEP card but the resulting value is incorrect. The value must be between 10 and 99.

Action:

Correct the SET= parameter on the STEP card.

CADE805I — DATE XX/XX/XX,CLOCK HH/MM/SS

Reason:

This is an informational message that displays the date and time when a STEP card is processed.

Action:

None.

CADE806E — INSUFFICIENT PARTITION STORAGE

Reason:

There is not enough partition getvis for the CA-Dynam Job Exit to process JCL/Manager JCL.

Action:

The JCL statement is passed unmodified to job control. Ensure there is sufficient partition getvis available to process JCL/Manager JCL.



CADE807E — INVALID CP COMMAND

Reason:

Either an invalid or disabled CP command has been issued.

Action:

The JCL statement is ignored. Either remove the CP command from the JCL or enable it.

CADE808E — POWER IS NOT RUNNING

Reason:

A PWR card is encountered but POWER is not active.

Action:

The JCL statement is ignored.

CADE809E — NO RESPONSE FROM POWER WITHIN 2 MIN

Reason:

A request was made to POWER by the CA-Dynam Job Exit but a response has not been received back for at least 2 minutes.

Action:

The JCL statement is passed to IBM.

CADE810E — ERROR IN XPCC COMMUNICATION, FUNC=*****,RC=********

Reason:

There was an error trying to communicate with POWER during the processing of a PWR card. The failing function and return code are specified in the message.

Action:

The JCL statement is passed to IBM. Collect as much diagnostic information as possible and contact Computer Associates Technical Support.

Messages 2–219

CADF Prefixed Messages

CADE811I — power_card

Reason:

Whenever a PWR card is encountered it is printed out.

Action:

None.

CADE812I — OK

Reason:

A PWR card has been successfully processed.

Action:

None.


CADF001E — PHASE 'CAFNIOCA' NOT FOUND

Reason:

CA-Dynam/FI cannot find phase CAFNIOCA.

Action:

Review installation procedures and rerun.

CADF002E — INSUFFICIENT GETVIS STORAGE.FILE=dtfname

Reason:

CA-Dynam/FI could not obtain the storage necessary for processing.

Action:

Either increase the partition size or decrease the SIZE value used to execute the program.



CADF003E — INVALID BLOCK-SIZE FILE=filename

Reason:

A block size value which is inconsistent with the program logical record length was specified.

Action:

Specify a block size which is consistent with the program logical record length. Note that the block size must be an even multiple of the record length for fixed-length records and equal to the record length for undefined records. For variable-length records the block size value must be greater than the record length value.

CADF004E — TAPE DTF EXTENSION ERROR - FORCED ABEND

Reason:

CA-Dynam/FI detected a tape DTF extension that does not conform to the known formats.

Action:

Gather storage dump and related documentation and contact Computer Associates immediately.

CADF007W — INSUFFICIENT GETVIS AVAILABLE FOR CA-DYNAM/FI.

Reason:

CA-Dynam/FI was unable to obtain virtual storage to construct essential control blocks. The OPEN request is allowed to continue, but CA-Dynam/FI processing is not possible. Processing will continue.

Action:

Reexecute the job-step with a SIZE parameter which will yield a larger GETVIS area.

CADF011W — CATALOG READ ERROR - CATALOG NOT UPDATED.FILE=filename

Reason:

The CA-Dynam Catalog could not be updated to reflect the current attributes of the file. Catalog Management has returned an error return code while accessing the Catalog.

Messages 2–221


Action:

Verify that the catalog entry for the file has not been deleted by another partition while the current job was running.

CADF012W — CATALOG WRITE ERROR - CATALOG NOT UPDATED. FILE=filename

Reason:

The CA-Dynam Catalog could not be updated to reflect the current attributes of the file. Catalog Management has indicated that an error occurred while writing the Catalog.

Action:

Verify that the catalog entry for the file has not been updated by another partition while the current job was running.

CADF013E — NO LOGICAL UNIT AVAILABLE FOR TAPE DTF. FILE=filename

Reason:

CA-Dynam/FI is generating a replacement DTFMT for a file, but no logical unit (LUB) is available. The original file table was probably DTFSD with no DEVADDR specified.

Action:

Add a logical unit to the catalog entry for the file, or add the operand SYSnnn to the TLBL statement.

CADF051E — UNEXPECTED ERROR F/C=nnnn R/C=nnnn F/N=xxxxxxxx

Reason:

Unexpected return codes have been received from the System Adapter functions. The function code (F/C), return code (R/C) and function name (F/N) are listed.

Action:

Collect the diagnostic information and contact Computer Associates.



CADF060E — VSAM LIOCS ERROR HAS OCCURRED. ERROR CODE=xxx (DECIMAL). FILE=filename.

Reason:

A VSAM LIOCS error has occurred.

Action:

See the IBM VSAM Messages and Codes manual for the VSAM error code given.

CADF061E — WRONG LENGTH RECORD FOUND, LENGTH=nnnnn(DECIMAL) FILE=filename

Reason:

CA-Dynam/FI detected a record length that was inconsistent with the attributes specified for the file. The value nnnnn shows the decimal record length of the record causing the error.

Action:

Ensure that the file attributes in the job agree with the original attributes used when the file was created. Correct any errors and reexecute the job-step.

CADF062E — ILLEGAL USE OF $$BDYF$X TRANSIENT.

Reason:

A CA-Dynam/FI logical transient has been invoked without storage blocks being initialized.

Action:

Ensure that no program other than those distributed by Computer Associates invokes CA-Dynam/FI transients.

CADF064I — ---- continued part of TLBL statement ---

Reason:

Continued TLBL statements containing only CA-Dynam/FI options are not recognized by JCL, so continuation cards will appear on SYSLST and/or SYSLOG.

Action:

None. The continuation statement is listed for documentation purposes.

Messages 2–223


CADF065E — SORTKEY NAME 'keyname' NOT FOUND IN CATALOG. FILE=filename

Reason:

SORTIN/SORTOUT=keyname was specified on a DLBL or TLBL statement, but the sort key record (SKR) was not found in the CA-Dynam Catalog.

Action:

Define the appropriate SKR catalog record, or specify the actual sort keys on the xLBL statement.

CADF066E — FORMAT NOT SUPPORTED BY SPECIFIED CA-SRAM

Reason:

A sort key string was specified for a Dynamic Sorting Task (SRAM) that included a field format not supported by CA-SRAM. The field formats presently supported are:

BI/B Positive Binary

CH/C Character

PD/P Packed Decimal

Action:

Ensure that sort key field formats are limited to those supported by CA-SRAM.

CADF067E — SORT KEY STRING GREATER THAN 256 CHARACTERS. FILE=filename

Reason:

A sort key string greater than 256 characters has been specified for a Dynamic Sorting Task. CA-SRAM restricts the length of this string to 256 characters.

Action:

Restructure the sort key string to be within the limit (including parentheses). If this is not possible, CA-SRAM cannot be used for the sorting task.



CADF068E — CA-SRAM SUPPORT NOT SPECIFIED FOR DYNAM/FI. FILE=filename

Reason:

A Dynamic Sorting Task was initiated with SORTIN/SORTOUT= on a DLBL or TLBL statement, but CA-SRAM support was not specified when CA-Dynam/FI was installed.

Action:

Change the CA-Dynam/FI Option Record specifying CA-SRAM (SRAM=YES). Be sure to link-edit the correct version of DYNFSRAM (see the Getting Started guide).

CADF069E — CDLOAD DIRECTORY FULL (DYNFSRAM). FILE=filename

Reason:

There were not enough slots in the CDLOAD Directory (Anchor Table) to load the CA-Dynam/FI CA-SRAM interface phase 'DYNFSRAM'.

Action:

Restructure the job into more steps, each requiring less 'CDLOAD' activity.

CADF071E — CA-SRAM NOT SUPPORTED FOR RECFM=U. FILE=filename

Reason:

CA-Dynam/FI does not support Dynamic Sorting for files with UNDEFINED record format. CA-SRAM expects a format of either FIXED or VARIABLE.

Action:

Do not use undefined record format.

CADF081W — CONCATENATION FOR OUTPUT DATASET IGNORED

Reason:

The data set for which the concatenation option is specified was opened for output.

Action:

Concatenation of output data sets is not supported.

Messages 2–225


CADF082W — CONCATENATION FOR UNSUPPORTED DTF IGNORED

Reason:

A dtftype other than DTFMT, DTFSD, DTFPH (some), or DTFCP was encountered at open with concatenation specified.

Action:

Dtftypes other than those specified above are not supported for concatenation processing.

CADF099D — dtfname SYSIPT:

Reason:

CA-Dynam/FI SYSLOG support for unit record files issues this prompting message for each SYSIPT read request.

Action:

Enter the data that the program expects for the file 'dtfname'.

CADF100W — CA-DYNAM/FI POST-INITIALIZATION ERROR F/C=nnnn R/C=nnnn

Reason:


Action:

None or, if you determine the impact on your processing is serious enough, correct the error and re-IPL.

Function Code


1 Unable to locate DFPROG, the CA-Dynam/FI program exception list. Run CACCDBU0 with parameters to define DFPROG.

2 Unable to locate DFEXCL, the CA-Dynam/FI program exclusion list. Run CACCDBU0 with parameters to define DFEXCL.




CADF101E — CA-DYNAM/FI POST-INITIALIZATION FAILURE F/C=nnnn R/C=nnnn

Reason:

Post-initialization has detected a severe error and will be prematurely terminated. The impact on CA-Dynam/FI processing will vary depending on the error.

Action:


Function Code


0 Unable to locate DYNAM/F, the CA-Dynam/FI System Option Record. Run CACCDBU0 with parameters to define DFOPTIONS.

1 Product CA-Dynam/FI is not active. Check startup procedure, LIBDEFs etc.


CADF132W — GETVIS FAILURE IN xxx RETURN CODE = rc

Reason:

A GETVIS return code has been sent. An error in one of the following phases (xxx) has occurred.

$BO VCKD open transient

$BC VCKD close transient

$BX VCKD service transient

MOD VCKD I/O module

Action:

Increase the amount of partition GETVIS available, and rerun.

Messages 2–227


CADF133E — FREEVIS FAILURE IN xxx RETURN CODE = rc

Reason:

A FREEVIS return code has been sent. An error in one of the following phases (xxx) has occurred.

$BO VCKD open transient

$BC VCKD close transient

$BX VCKD service transient

MOD VCKD I/O module

Action:

Consult the Supervisor and I/O option records reference for the cause of error.

CADF134W — LABEL RETURN CODE = rc FOR FILE = xxxxxxx

Reason:

A LABEL ACCESS METHOD return code has been issued for a file to be opened.

Action:

Consult the Supervisor and I/O option records reference for cause of error.

CADF135W — GETVCE RETURN CODE = rc FOR FILE = xxxxxxx

Reason:

A GETVCE MACRO return code has been issued for a file to be opened.

Action:

Consult the Supervisor and I/O option records reference for the cause of error.



CADF136I — FILE OPENED = xxxxxxx

Reason:

A DA file has been opened and assigned to an FBA device.

Action:

None.

CADF137I — FILE CLOSED = xxxxxxx

Reason:

A DA file has been closed.

Action:

None.

CADF140D — ENTER UTILITY CONTROL STATEMENTS

Reason:

VCKDCLDK has been executed from the console.

Action:

Enter the clear disk control statement. A null entry (EOB) will result in message CADF141.

CADF141E — INVALID CONTROL STATEMENT, JOB CANCELED

Reason:

The entered clear disk control statement was invalid.

Action:

Enter a valid clear disk control statement.

Messages 2–229


CADF142E — INVALID xxx PARAMETER, JOB CANCELED

Reason:

The xxx parameter of the control statement is invalid.

Action:

Enter a valid clear disk control statement.

CADF143E — NO FREE STORAGE AVAILABLE, JOB CANCELED

Reason:

GETVIS storage could not be obtained.

Action:

Increase the partition GETVIS size and rerun the job.

CADF147I — BACKUP IN PROGRESS

Reason:

Backup facility of VCKDBKRS starting.

Action:

None.

CADF148I — CLEAR DISK IN PROGRESS

Reason:

Clear disk facility of VCKDBKRS starting.

Action:

None.



CADF149I — RESTORE IN PROGRESS

Reason:

Restore facility of VCKDBKRS starting.

Action:

None.

CADF150D — ENTER BACKUP/RESTORE CONTROL STATEMENTS

Reason:

VCKDBKRS has been executed from the console.

Action:

Enter the backup/restore control statement. A null entry (EOB) will result in message CADF151.


Reason:

The entered control statement was invalid.

Action:


CADF152E — INVALID MAXSIZE PARAMETER, JOB CANCELED

Reason:

The MAXSIZE= parameter contained an error.

Action:


Messages 2–231


CADF153E — NO GETVIS STORAGE AVAILABLE, JOB CANCELED

Reason:

GETVIS storage could not be obtained.

Action:

Increase the partition GETVIS size and rerun the job.

CADF154E — NO MORE ROOM ON FBA EXTENT, JOB CANCELED

Reason:

The allocated number of FBA blocks was not large enough to contain the file.

Action:

Increase the allocation for the file.

CADF155E — TAPE NOT CREATED BY BACKUP, JOB CANCELED

Reason:

The input tape used in the restore phase is invalid.

Action:

Mount the proper tape volume and resubmit.

CADF156I — nnnnnnnnn DA RECORDS WRITTEN TO TAPE

Reason:

nnnnnnnnn records have been read from the CKD DA disk file and written to the backup tape.

Action:




CADF157I — nnnnnnnnn DA RECORDS READ FROM TAPE

Reason:

nnnnnnnnn records have been read from the backup tape and written to the FBA DA file.

Action:


CADF158I — CISIZE=nnnnn

Reason:

The size of the emulated CKD track is reported.

Action:

None.

CADF159I — LOGICAL RECORDS PER CI=nnnnn

Reason:

nnnnn logical records are contained in the control interval (emulated track).

Action:

None.

CADF160D — ENTER ANALYZER STATEMENT

Reason:

VCKDANAL has been executed from the console.

Action:

Enter the analyzer control statement. A null entry (EOB) will result in message CADF161.

Messages 2–233



Reason:

The entered control statement was invalid.

Action:

Enter a valid disk analyzer control statement.

CADF162E — INVALID MAXSIZE PARAMETER, JOB CANCELED

Reason:

The MAXSIZE = parameter contained an error.

Action:

Correct the parameter and resubmit.

CADF331E — PARTITION ID MISSING OR INVALID

Reason:

A CATRACE command has been entered with an invalid or missing partition ID.

Action:

Enter a valid partition ID and resubmit.

CADF332E — CUU/SYSNNN MISSING OR INVALID

Reason:

A CATRACE command has been entered with an invalid or missing cuu or SYSnnn number.

Action:

Enter a valid cuu or SYSnnn number and resubmit.



CADF333E — INVALID STARTING EXTENT NUMBER SPECIFIED

Reason:

A CATRACE command has been entered with an invalid starting extent number.

Action:

Enter an extent number between 0 and 255, and resubmit.

CADF334E — DTFNAME MISSING OR INVALID

Reason:

A CATRACE command has been entered with an missing or invalid dtfname.

Action:

Specify a valid dtfname and resubmit.

CADF335E — TAPE CUU SELECTED IS NOT OPERATIONAL

Reason:

A CATRACE command has been entered with a cuu belonging to a tape unit whose status is unavailable.

Action:

Make sure a tape unit is attached and ready before entering the CATRACE command.

CADF336E — SPECIFIED PRODUCT IS NOT ACTIVE OR NOT AVAILABLE

Reason:

A CATRACE command has been entered for a product that is inactive, or has not been initialized.

Action:

Make sure the correct product code is entered for the CATRACE command, and that the product has successfully initialized and is currently active.

Messages 2–235

CADT Prefixed Messages


CADT000I — -------user text-------

Reason:

A control statement was input to CASAUTIL when action log was specified.

Action:

None.

CADT001D — UNASSIGNED INPUT/OUTPUT TAPE dtfname SYSnnn

Reason:

An OPEN has been issued for a tape file (or unassigned DTFCP) that is not being controlled by CA-Dynam/T. Either the logical unit being used by this DTF is not assigned to a tape device, or end-of-volume has been reached for an uncontrolled tape file. The system is requesting that the operator enter the address of the tape drive to be used.

Action:

Perform one of the following actions:

Reply with To

cuumm enter the tape drive address to be used for the file, where mm is the optional density.

CANCEL cancel the job.

STATUS obtain a list (on the console) of all tape drives.

FREE

RUN cuu|ALL REW cuu|ALL FSF cuu,nnn BSF cuu,nnn FSR cuu,nnn BSR cuu,nnn

obtain a list (on the console) of all tape drives that are unassigned, in a ready status, and attached to this machine.

STOP place the partition in a wait state (use the CASTART command to restart the partition).

Note that any invalid response will result in this same message being issued again.



CADT002D — *INTERV-REQ* SYSnnn=cuu

CADT002D — UNAVAILABLE SYSnnn=cuu

CADT002D — FILE-PROTECT SYSnnn=cuu

CADT002D — *NOT LD PNT* SYSnnn=cuu

CADT002D — *NON COMPAT* SYSnnn=cuu

Reason:

The response made to one of the system MOUNT messages was a tape drive address; however, that tape drive is not eligible for use.

Message Reason

*INTERV-REQ* The tape drive is not ready.

UNAVAILABLE The tape drive is nonexistent, deviced down, or already assigned to another logical unit; or an I/O error occurred while reading the VOL1/HDR1 from the tape.

FILE-PROTECT The tape is file-protected and this is an output file.

*NOT LD PNT* This is not a multifile volume and the tape is not at load point.

*NON COMPAT* There is a noncompatible tape drive/density.

Action:

Refer to the prior message to which the response of cuu was originally entered. Respond to that message again.

Resply with To

REWIND rewind the tape. Even in this case, the original message will be reissued and must be responded to once again. This response, of course, may be the same cuu to which the response of 'REWIND' was entered in order to then use that tape.

UNLOAD to unload the tape

REL to release the logical unit assignment and allow another drive to be used.

Messages 2–237


Resply with To

FREE to obtain a list (on the console) of all tape drives that are unassigned, in a ready status, and attached to this machine.

CANCEL to cancel the job.

DYNLUB to release the logical unit assignment and dynamically allocate an available logical unit.

IGNORE to exit CA-Dynam/T processing. Since we are unable to read the volume label, we cannot control the tape. This response is only valid for the *NOT LD PNT* message.

CADT002I — *INTERV-REQ* SYSnnn=cuu

CADT002I — UNAVAILABLE SYSnnn=cuu

CADT002I — FILE-PR V=volser SYSnnn=cuu

CADT002I — *NOT LD PNT* SYSnnn=cuu

CADT002I — *NON COMPAT* SYSnnn=cuu

Reason:

The response made to one of the system MOUNT messages was a tape drive address; however, that tape drive is not eligible for use.

Message Reason


UNAVAILABLE The tape drive is nonexistent, deviced down, or already assigned to another logical unit; or an I/O error occurred while reading the VOL1/HDR1 from the tape.

FILE-PR The tape is file-protected and this is the output file volser and SYS number.


*NON COMPAT* There is a noncompatible tape drive/density.



Action:


CADT003W — VOLUME xxxxxx DYNAM/T CONTROLLED TAPE, MOUNT NON-DYNAM/T SCRATCH SYSnnn

Reason:

The file being created is not a CA-Dynam/T controlled data set; however, the tape mounted on the assigned drive (assigned through JCL or operator response) is a CA-Dynam/T controlled volume. When the system cannot access the catalog files, no controlled volume may be used for output. When the system has access to the catalog files, scratch tapes may be used for uncontrolled output files unless such action is prevented due to installation options.

Action:

Mount an uncontrolled volume on the assigned drive. If the logical unit was assigned in response to the CADT001 message, then that message will be reissued. Respond with another cuu if desired.

If the installation option to protect scratch tapes from uncontrolled use was chosen, then any tape with a volume serial number equal to one in the Catalog will be protected.

CADT004A — MOUNT VOLUME xxxxxx data-set-name SYSnnn JOB=jobname VAULT=(v,sssss)

Reason:

The data set in the mount message is being opened as input, but the system could not locate the above volume.

Action:

Mount the correct volume on an available tape drive.

CADT004D — MOUNT VOLUME xxxxxx data-set-name SYSnnn JOB=jobname VAULT=(v,sssss)

Reason:


Messages 2–239


Action:

Mount the correct volume on an available tape drive and reply END/ENTER or respond with one of the following:

Reply with To

cuu direct the system to a specific tape drive (only necessary to force override for this data set).

CANCEL cancel this job.


FREE obtain a list (on the console) of all tape drives that are unassigned, in a ready status, and attached to this machine.

RUN cuu|ALL

REW cuu|ALL

FSF cuu,nnn

BSF cuu,nnn

FSR cuu,nnn

BSR cuu,nnn

perform the indicated tape control operation to the drive indicated, if the drive is unassigned or owned by the partition issuing the message.

STOP place the partition in a wait state (awaiting a CASTART).

ALTER erase the label record currently in use and reopen the file to access the next sequentially submitted label record for this file.

RERUN scratch Version 1 of this data set and reopen the file to access what was the Version 2 as Version 1 (not valid for multifile data sets).

ACCEPT DSN=

'data-set-name'

[,VER=nnn|

,VOL=xxxxxx]

to reissue the OPEN and search for the indicated data set, version or volume instead of the one called for through JCL (valid only if ACCEPT=YES has been generated; may be used to ACCEPT multifile data sets).

DYNLUB release the logical unit assignment and dynamically allocate an available logical unit.

PREV reopen the file to access the next most current version (not valid for multifile data sets) Only valid if PREV=YES is specified in the CA-Dynam/T option record.



The responses ACCEPT, ALTER, RERUN and PREV are installation options, valid only if so indicated at installation time. Any invalid response will result in this same message being reissued. The CADT004 MOUNT message will always be issued for files that are assigned to tape drives at open time (not using AVR). This is so that any subsequent messages (CADT005 or CADT006 or CADT002) immediately following may refer to the information in the MOUNT message. The CADT004 MOUNT message with a volume serial number of six zeros (000000) indicates that the requested volume or version of the data set does not exist. The MOUNT message is issued in this fashion so that one of the optional responses may be used, if appropriate.

CADT004I — MOUNT VOLUME xxxxxx data-set-name SYSnnn JOB=jobname VAULT=(v,sssss)

Reason:


Action:


CADT005D — WRONG TAPE: VOL=xxxxxx HDR 1='data set name' SYSnnn=cuu

Reason:

The volume mounted on the assigned drive (through JCL or operator response) is not the correct requested volume. The volume and HDR1 information shown is taken from the tape.

Action:

Mount the requested volume (as per the CADT004 MOUNT message) and reply EOB, or reply with one of the following:

Reply with To

cuu direct the system to another tape drive (not valid if the logical unit was assigned at open time through JCL).


ALTER erase the label record currently in use and reopen the file in order to access the next sequentially submitted label record.


Messages 2–241


Reply with To

ACCEPT accept this volume as input (it should not be used with multifile data sets; use ACCEPT DSN=dsn, VER=nnn with message CADT004) instead.

RERUN SCRATCH Version 1 of the indicated data set and reopen the file in order to access what was Version 2 as Version 1.

NEWTAP reissue the open (dismount the volume, mount the desired one, and respond NEWTAP).

REL drop the assignment to this physical tape, and then have full AVRbe performed.


PREV

reopen the file to access the next most current version (not valid for multifile data sets) Only valid if PREV=YES is specified in the CA-Dynam/T option record.

The responses PREV, RERUN, ALTER and ACCEPT are installation options and not valid unless selected at installation time. Additionally, if allowed, the occurrence of these replies will always be reported on the EXCEPTION REPORT as well as the AUDIT reports if that option is chosen.

CADT006W — DSN='dsn' IN CATALOG IS NOT A TAPE DATA SET

Reason:

The data set name specified on the TLBL exists in the CA-Dynam Catalog as a disk or other type of data set. CA-Dynam/T requires unique data set names. The data set is treated as uncontrolled.

Action:

Refer the problem to the systems programmer for correction. The DYNCAT ALTER command may be used to change the data set in the Catalog to TAPE if necessary.

CADT007I — ***** LABEL dtfname SYSnnn=cuu volser ssss *data-set-name* WORK dtfname SYSnnn=cuu volser ssss *data-set-name*

Reason:

The indicated data set is being created on the named tape drive. If the data set is a work data set, then that will be indicated with the word WORK replacing the word LABEL. 'ssss' is the volume sequence number.



Action:

None.

CADT008A — MOUNT SCRATCH dtfname SYSnnn DSN=data-set-name OWNER=xx MODE=xx SIZE=xx JOB=jobname VOLID=xx

CADT008A — MOUNT SCRATCH dtfname ON cuu DSN=data-set-name OWNER=xx MODE=xx SIZE=xx JOB=jobname VOLID=xx

Reason:

A CA-Dynam/T controlled data set is being opened for output, but the system could not locate a controlled scratch tape. The second format of this message (ON cuu) will be issued when the logical unit was previously assigned. In this case, that tape drive must be used.

Action:

Mount a controlled scratch tape, with file protect ring, on an available tape drive.

CADT008D — MOUNT SCRATCH dtfname SYSnnn DSN=data-set-name OWNER=xx MODE=xx SIZE=xx JOB=jobname VOLID=xx

CADT008D — MOUNT SCRATCH dtfname ON cuu DSN=data-set-name OWNER=xx MODE=xx SIZE=xx JOB=jobname VOLID=xx

Reason:


Action:

Mount a controlled scratch tape, with file protect ring, on an available tape drive and reply EOB, or reply with one of the following:

Reply with To

cuumm direct the system to use a specific drive (invalid if logical unit was preassigned and necessary only to initialize a scratch "on the fly" or override mode or owner).

Messages 2–243


Reply with To





RUN cuu|ALL

REW cuu|ALL

FSF cuu,nnn

BSF cuu,nnn

FSR cuu,nnn

BSR cuu,nnn

perform the indicated tape control operation to the drive indicated or to all drives (valid for unassigned drives owned by the partition issuing the message.

SCRTCH, nnn cause CA-Dynam/T to display nnn SCRATCH volumes on the console. The default is ten volumes.

DISK cause CA-Dynam/T to attempt to invoke CA-Dynam/FI to change the DTF in the program from tape to disk (only valid if the complete CA-Dynam system (CA-Dynam/T, /D, and /FI) is installed and active, and only fr a MOUNT request for Volume 1 of a controlled tape data set. See the "Controlling File Independence" chapter of the User Guide.


When AVR is performed for output files (any time the logical unit is not preassigned), the system will check all tapes at load point with a file protect ring for the following:

■ Is it currently set at desired recording mode (if requested)?

■ Does data set owner match volume owner (if present)?

■ Does catalog owner ID match VOL1 owner ID (if checking)?

■ Does data set length match volume length (if specified)?

■ Does the volid match the first two characters of the volser (if specified)?

Any volumes that do not meet all required checks will be bypassed by the AVR routines. The operator may override some of these specifications by directing the system to a specific tape drive by responding with a cuu or cuumm.



CADT008I — MOUNT SCRATCH dtfname SYSnnn DSN=data-set-name OWNER=xx MODE=xx SIZE=xx JOB=jobname VOLID=xx

CADT008I — MOUNT SCRATCH dtfname ON cuu DSN=data-set-name OWNER=xx MODE=xx SIZE=xx JOB=jobname VOLID=xx

Reason:


Action:


CADT009D — VERIFY VOLUME NO=xxxxxx

Reason:

The system has been directed to use a specific tape (by operator response or JCL assign) and the tape mounted is not a CA-Dynam/T controlled volume. The volume mounted will be initialized as a controlled scratch tape with the volume serial number resulting from this message.

Action:

If this volume serial number is correct, reply EOB. This will cause the tape to be initialized with that number.

A 1- to 6-character volume serial number may also be entered if the number displayed is not correct. In this case, this message will be reissued with the operator-entered volume serial number for verification. If this message keeps reappearing each time a reply of EOB is made, it is an indication that the volume serial number in the message is not valid or that TAPEINT=NO is specified in the CA-Dynam/T option record, in which case the only valid replies are CANCEL or NEWTAP. The operator must reply with a valid volume serial number.

A response of CANCEL will cancel the job.

If the volume mounted is not the desired volume, dismount the volume, mount the correct volume and reply 'NEWTAP' to verify the new volume.

Messages 2–245


CADT010D — VOLSER xxxxxx ALREADY IN FILE AS data-set-name

CADT010D — VOLSER xxxxxx ALREADY IN FILE AS SCRATCH

CADT010D — VOLSER xxxxxx ALREADY IN FILE AS SCRATCH OWNER=xx, REQUESTED OWNER=xx

CADT010D — VOLSER xxxxxx ALREADY IN FILE AS SCRATCH VOLID=xx, REQUESTED VOLID=xx

Reason:

If an attempt is made to use a tape which contains an active data set as a SCRATCH tape, the first form of this message will be issued. No operator response is allowed, and if the drive was preassigned, the tape will be unloaded. A different volume must be used.

The second message is issued if an attempt is made to initialize a tape 'on the fly,' and the serial number on the tape matches one in the Catalog as a SCRATCH. This message will be issued as a warning that the potential exists for initializing a duplicate volume serial number. This may legitimately occur if the tape has never been written by CA-Dynam/T before, but the serial number has been added to the Catalog manually, or if a tape has been used outside the system, so that the internal CA-Dynam/T ID has been lost. In this case, the operator may respond 'ACCEPT' to reinitialize the tape.

The third message is issued if the tape selected by the operator is a SCRATCH, but the tape OWNER does not match the OWNER of the data set being opened. This message is issued to allow the operator to choose another tape, or respond 'ACCEPT' to reinitialize the tape to the OWNER of the data set.

The fourth message is issued if the volume identifier for the tape does not match the volid of the data set.

Action:

Type 'ACCEPT' to initialize the tape (and change the owner or volume identifier if necessary), or select another tape. Note that this response is only valid if the volume serial number in question is a tape in SCRATCH status.

Type EOB to cancel the job.



CADT011W — cuumm INVALID DENSITY

Reason:

A response of cuumm as printed in the message was made to a CADT008 MOUNT SCRATCH message. The tape drive (cuu) cannot write at the specified density (mm).

Action:

Respond to the MOUNT message again.

CADT012E — SYSLST/PCH ASSIGNED TO CA-DYNAM/T TAPE

Reason:

SYSPCH or SYSLST is being assigned to a drive on which a CA-Dynam/T controlled tape is mounted. CA-Dynam/T will not allow you to write on a controlled tape. The job is canceled to protect the tape, and the logical unit is left unassigned.

Action:

Mount a non-CA-Dynam/T tape and rerun the job.

CADT013W — xxxxx INVALID RESPONSE

Reason:

The response indicated in the message (xxxxx) is invalid.

Action:

Respond to the original message again.

CADT014E — DSN=data-set-name SERIAL NO.=xxxxxx LOCKED

Reason:

The program is trying to open a volume which has been LOCKED by the DYNCAT LOCK function.

Action:

None. The file must be unlocked before it can be accessed. CA-Dynam/T cancels the job.

Messages 2–247


CADT015I — cuu-pp-SYSnnn x cuu UA status volser file-id

Reason:

Status was requested by operator command. Each tape drive in the PUB table is listed with, if assigned, the owning partition (pp) and first logical unit found in that partition assigned to the drive.

To the right (x) of the logical unit maybe one of the following:

This Indicates

* additional assignments to this drive

STD stored standard assign

ALT alternate assign

Tape drives not assigned will show the STATUS of the drive as:

This Indicates

AVRLOCK tape drive has a lock issued against it

BUSY tape drive is busy

DOWN device is down

NOT CAP tape drive is not capable of reading the tape

NOT RDY tape drive is not ready

NOT AVBL tape drive is not accessible

NOT AVRABLE

tape drive unavailable, not in AVRTABLE (CMS)

RDY LP/F ready, load point, file protected

RDY LP/W ready, load point, not file protected

RDY NLPF ready, not load point, file protected

RDY NLPW ready, not load point, not file protected

Action:

None.



CADT016E — SYSPCH/LST xxxxxx ACTIVE FILE DSN= data-set-name

Reason:

SYSLST or SYSPCH was assigned to an active CA-Dynam/T volume.

Action:

The tape is unloaded, the logical unit is set to unassigned and the job is canceled in order to protect the tape. Rerun the job with another volume mounted.

CADT017D — *INTERV-REQ* SYSnnn=cuu

CADT017D — UNAVAILABLE SYSnnn=cuu

CADT017D — FILE-PR V=volser SYSnnn=cuu

CADT017D — NOT LOAD PNT SYSnnn=cuu

CADT017D — *NON COMPAT* SYSnnn=cuu

Reason:

The response made to one of the system MOUNT messages was a tape drive; however, that tape drive is not eligible for use.

Message Reason


UNAVAILABLE The tape drive is nonexistent, deviced down, or already assigned to another logical unit, or an I/O error occurred while reading the VOL1/HDR1 from the tape.

FILE-PR The tape is file-protected and this is the output file volser and SYS number..


*NON COMPAT* A noncompatible tape drive/density combination has been detected. The tape should be removed from the drive.

Messages 2–249


Action:

Refer back to the prior message to which the response of cuu was originally entered. Respond to that message again.

The operator may respond:

■ 'REWIND' and the system will rewind the tape. Even in this case, the original message will be reissued and must be responded to once again. This response, of course, may be the same cuu to which the response of 'REWIND' was entered in order to then use that tape.

■ 'UNLOAD' to unload the tape

■ 'REL' to release the logical unit assignment and allow another drive to be used.

■ 'FREE' to obtain a list (on the console) of all tape drives that are unassigned, in a ready status, and attached to this machine.

■ 'CANCEL' to cancel the job.

■ 'DYNLUB' to release the logical unit assignment and dynamically allocate an available logical unit.

■ 'IGNORE' to exit CA-Dynam/T processing. This response is only valid for *NOT LD PNT* message.

CADT018W — NO ROOM AVAILABLE IN CATALOG, TAPE nnnnnn DSN = 'dsn' NOT CATALOGED *** NOTE ***

Reason:

There is no room left in the CAICATL file to catalog the named data set.

Action:

Inform the operations supervisor or systems programmer immediately. The file size must be increased, and the CA-Dynam/T catalogs must be restored to the larger extents before any additional versions may be cataloged. As a temporary measure, the DYNCAT SCRATCH function may be run to free space immediately. Any volume for which this message appears must be manually ADDed to the data set referenced when space is made available.



CADT019W — CATALOG IS FULL -- PERFORM REORGANIZATION *** WARNING ***

Reason:

There is no more room left in the catalog file to accept any more tapes.

Action:

Refer to the operator action for CADT018. The file must be enlarged before any additional volumes may be added.

CADT020A — MOUNT VOLUME xxxxxx FOR FILE NO. xxx DSN='data-set-name' SYSnnn

Reason:

A file other than file one on a multifile volume is to be written, and the correct tape is not mounted.

Action:

Mount the correct tape on any available drive.

CADT020D — MOUNT VOLUME xxxxxx FOR FILE NO. xxx DSN='data-set-name' SYSnnn

Reason:


Action:

Mount the correct tape on any available drive and reply EOB. Other acceptable replies are:

Reply with To


cuu specify the drive on which the tape is mounted.

STATUS find an available tape drive.


STOP stop the partition (put in wait state) Use the CASTART command to restart the partition.

Messages 2–251


Reply with To

RUN cuu|ALL

REW cuu|ALL

FSF cuu,nnn

BSF cuu,nnn

FSR cuu,nnn

BSR cuu,nnn

perform the indicated tape control to the drive indicated, or all drives (These are valid if the drive is unassigned or owned by the partition issuing the message).

CADT020I — MOUNT VOLUME xxxxxx FOR FILE NO. xxx DSN='data-set-name' SYSnnn

Reason:


Action:


CADT021E — TAPE xxxxxx ALREADY HAS FILE NO. xxx ON IT

Reason:

The program is attempting to write a file on a multifile volume, and that file already exists on that volume.

Action:

In order to recreate a file on a multifile volume, first delete that version of the file from the Catalog using the DYNCAT DELETE VERSION command.

CADT022E — DSN = 'dsn' IS FILE NO. xxx, THERE ARE ONLY xxx FILES ON TAPE

Reason:

The program is trying to write a file on a multifile volume before the preceding file(s) have been written. This message also appears trying to read a file that has not been created on this volume. The system cancels the job.

Action:

For an output tape, files on a multifile volume must be created in sequence. For an input tape, mount the correct volume and resubmit.



CADT023I — DSN 'data-set-name' FILE NO. xxx BEING CREATED ON TAPE xxxxxx cuu.

Reason:

The data set is being created on tape.

Action:

None.

CADT024E — DSN = data-set-name CANNOT LOCATE PRIOR FILE

Reason:

The data set name that is the prior file for this data set could not be found in the Catalog. This should never occur.

Action:

The job is canceled. Contact Computer Associates for assistance if the cause cannot be determined.

CADT025W — TAPE xxxxxx WRONG OUTPUT TAPE FOR DSN=data-set-name

Reason:

A program is trying to write other than file one on a multifile volume. Either the operator replied cuu to the mount message CADT020 or the drive was preassigned, but the serial number of the tape mounted on that drive does not match the serial number of the prior file in the multi-file volume set.

Action:

The system rewinds and unloads the tape and scans the drives for the correct tape. If the correct tape is not found, the system issues the mount message CADT020 again. Respond to CADT020.

If the tape is found, normal processing continues, and no response is needed.

CADT026W — VOLSER xxxxxx NOT FOUND IN CATALOG ** ERROR **

Reason:

The system was attempting to update a volume record at close but could not locate that record. Most likely, the DTF has been corrupted.

Messages 2–253


Action:

Refer this problem to the systems programmer for correction. Contact Computer Associates for assistance if needed.

CADT027W — DYNAM/T TAPE xxxxxx NOT IN CATALOG

Reason:

The indicated volume is a CA-Dynam/T controlled tape (as per the HDR1 record), but the serial number is not in the catalog file. The tape is unloaded. Messages will also occur if catalog owner mismatch.

Action:

In order to use this tape, it must be reinitialized with DYNCAT in order to place the number in the catalog file.

CADT028I — RELEASED dtfname INPUT volser data-set-name

CADT028I — RELEASED dtfname OUTPUT volser data-set-name

Reason:

The indicated data set name was released at close as a result of the release option in the TLBL for this file. The indicated volume serial number is in scratch status and can be used for output now.

Action:

None.

CADT029E — SYSnnn INVALID LUB FOR dtfname

Reason:

The logical unit for the named file is not acceptable to the system. This will generally be a LUB that is not valid for this partition.

Action:

Inform the systems programmer of this occurrence.



CADT031I — *CLOSED* filename SYSnnn=cuu volser dsn B=blks

CADT031I — *EOV* filename SYSnnn=cuu volser dsn BLK=blks

CADT031I — *TEST* filename SYSnnn=cuu volser dsn BLK=blks

CADT031I — *LOCKED* filename SYSnnn=cuu volser dsn BLK=blks

Reason:

A controlled output file has been closed and the CA-Dynam/T catalog has been updated.

Message Issued

*CLOSED* when the program closed the file.

*EOV* at volume switch for output.

*TEST* at close for $TEST jobs.

*LOCKED* at close if the DSN was locked for output.

In the case of *TEST* and *LOCKED*, the data set is not updated -- only the volume record. 'blks' indicates the number of blocks written to the tape volume, available from the DTF.

Action:

None.

CADT032I — ASSIGNED filename SYSnnn=cuu volser volseq data-set-name

Reason:

CA-Dynam/T has located the correct input file.

Action:

None.

Messages 2–255


CADT033E — DSN 'data-set-name' MISSING

Reason:

During automatic multifile processing, the data set name indicated in the message was found to be missing, probably because it had already been deleted by the user with the DYNCAT DELETE function.

Action:

CA-Dynam/T must be informed which AMF DSN to use next, through the ALT function of DYNCAT.

CADT034E — DSN 'data-set-name' MAXIMUM FILES EXIST

Reason:

It was found during AMF processing that no more data sets can be created because the maximum of 999 already exists.

Action:

Manual maintenance must be performed to remove some of the AMF data sets from the catalog file.

CADT035E — DSN 'data-set-name' ALREADY EXISTS

Reason:

The named data set was to be created by AMF processing, but was found to already exist in the Catalog.

Action:

The named DSN must be removed from the catalog file with DYNCAT maintenance.

CADT036E — CATALOG FULL - CANNOT CREATE MF=AUTO DSN

Reason:

An automatic multifile DSN was opened as output, but no room is available in the catalog file to create a new data set record.



Action:

The CA-Dynam/T catalog file probably needs enlargement by use of the BACKUP and RESTORE/REORG function. A temporary solution would be to run the SCRATCH function to clear some space until the files can be enlarged.

CADT037E — DSN 'data-set-name' MFV CTL RCD MISSING

Reason:

A multifile control record is missing. A user program may have overwritten the catalog file.

Action:


CADT038W — NOT WORK dtfname INPUT/OUTPUT volser data-set-name

Reason:

A close has occurred for a controlled data set which is not a work data set, yet a 'RELEASE' ('R' or 04 OPTCODE) has been specified on the TLBL.

Action:

None required, but you should review the JCL to assure that 'RELEASE' has been specified for the correct data set.

CADT039W — ** OPENED OFF LD PT ** dtfname SYSnnn=cuu

Reason:

An uncontrolled file has been opened for output with NOREWIND specified, and the logical unit is preassigned to a tape which is not at load point. CA-Dynam/T cannot validate the use of the tape without destroying the positioning, so a warning is issued. The file is treated as uncontrolled. No audit information can be collected. The open proceeds.

Action:

Notify the systems programmer of this occurrence so that steps can be taken to bring the file under CA-Dynam/T control.

Messages 2–257


CADT040E — *** UNABLE TO ACCESS FILE dtfname *** RTC=nnnn

Reason:

NOTIFY and SECURE option was selected in order to display this message when any of the CA-Dynam files cannot be accessed.

Action:

The job is canceled. Contact Computer Associates for assistance if the cause cannot be determined.

CADT040W — *** UNABLE TO ACCESS FILE dtfname *** RTC=nnnn

Reason:

NOTIFY installation option was selected in order to display this message when any of the CA-Dynam files cannot be accessed.

Action:

Informational only. If the SECURITY option was selected, the job will be canceled. (POWER/VSE will never be canceled, nor will jobname 'DYNAM/T'.) See "Catalog Management Return Codes" for more information. The cause is most likely one of the following:

■ The named file has not been initialized for use.

■ The logical unit specified in the extent statement for the named file (SYS-number) is not assigned to the device upon which the file resides.

■ Label information for the named file cannot be located in any of the label areas.

■ Insufficient partition GETVIS is available.

CADT041E — DYNAMIC ASSIGN ERROR, RC= nnnn

Reason:

An unexpected error was received from the ASSGN function.

Action:

The problem may be fixed by increasing the EXTENT value on the IPL SYS statement. If the problem persists, contact Computer Associates. See "Catalog Management Return Codes" for more information.



CADT042E — INSUFFICIENT GETVIS STORAGE AVAILABLE TO PROCESS (xxxxxxxx)

Reason:

Insufficient GETVIS storage is available to process the file. CA-Dynam/T acquires storage dynamically from partition GETVIS. The GETVIS request failed. The job is canceled. For documentation purposes, the CA-Dynam module whose storage request failed is noted in the message.

Action:

Rerun the job with a smaller size parameter on the execute card to provide more partition GETVIS.

CADT043E — UNRECOVERABLE ERROR OCCURRED -- FUNCTION=function R/C=rc

Reason:

An unexpected and unrecoverable error has occurred while processing a file. This message is issued by CA-Dynam/T upon exit from the function. The function may be one of: OPEN-01, EOV, JOBCNTRL, CLOSE-01, CLOSE-02, CLOSE-03, SWAPPSW, or SAVER-CL. The job is canceled. The return code which indicates the nature of the error and the name of the function which experienced the error are produced for documentation purposes.

Action:

Retain the console log, SYSLST output, and any dumps which are produced for the systems programmer to assist in error resolution. If the problem recurs, contact the systems programmer for assistance. An IPL may clear the condition. See "Catalog Management Return Codes" for more information.

CADT044W — VOLUME xxxxxx IS OUTSIDE ALLOWABLE RANGE

Reason:

The volume serial number specified is outside the allowable range of numbers as established in the volser parameter of the CA-Dynam/T option record.

Action:

Select another volume serial number. If the range specified in the CA-Dynam/T option record is in error, refer the problem to the systems programmer for resolution.

Messages 2–259


CADT045D — VERIFY UNCONTROLLED USE OF VOLUME: volser, dtfname SYSnnn=cuu

Reason:

An uncontrolled tape file is being opened for output, and the tape on the specified drive is a CA-Dynam/T scratch tape.

Action:

Remove the CA-Dynam/T scratch tape and replace it with a non-CA-Dynam/T scratch, and (END/ENTER to verify the new tape, respond 'ACCEPT' to override CA-Dynam/T and allow the controlled scratch tape to be used, or respond 'FREE' to view a list of tape drives that are ready, unassigned and attached to this machine.

CADT047E — ERROR AT CLOSE/EOV dtfname SYSnnn=cuu volser data-set-name

Reason:

An error has been detected at CLOSE or End of Volume while attempting to update the catalog linkages for the named output volser and data set. This results from an operator error during AVR or OPEN, most commonly from the tape having been physically moved from the drive during OPEN processing, and mounted on another drive, and the first drive having been used by another volume.

Action:

Verify that the tapes referenced are accurate, and display the catalog for this data set and other concurrently created ones to resolve the problem.

CADT048I volser OWN=xx LEN=yy DENSITY=mm VOLID=cc

Reason:

A response of 'SCRTCH' was entered to a CADT008 mount scratch message. CA-Dynam/T lists ten scratch volumes from the Catalog so that a scratch can be located. The owner code (xx) is indicated if the volume is owned. 'OWN=**' indicates no owner. 'yy' is the length of the volume. '**' indicates no specified length. 'cc' is the volume identifier. The CADT008 mount message is repeated.

Action:

None.



CADT049E — FATAL CAM ERROR, xx/xxxxxx xxxx (xxxxxxxx/xxxx)

Reason:

An unexpected error has occurred while accessing the catalog. Catalog corruption may have occurred, but it is likely that the error is inconsequential. Since the catalog file is blocked and highly organized, an event such as an operator issuing a FLUSH command, or an emergency cancel, may have terminated CA-Dynam processing before catalog update was complete, resulting in one or more incomplete version records. The problem can be corrected by a BACKUP/RESTORE REORG/SCRATCH run. Other possibilities include an out-of-storage condition during catalog processing (insufficient available GETVIS), or even a catalog full condition while adding a new data set name or volume serial number inline. The job is terminated with a dump.

Action:

Retain the console log, SYSLST output, and dumps for the systems programmer to aid in problem determination. If the error persists, take a DYNCAT BACKUP of the catalog file before beginning any other error correction measures. See "Catalog Management Return Codes" for more information.

CADT050D — CATALOG ENQUEUE FAILURE - FILE 'ddname'

Reason:

Request for catalog enqueue has failed. The catalog is in use by another task.

Action:

Awaits operator response.

Reply with To

STOP cause the partition to be placed in a stopped state so that the catalog enqueue failure can be investigated and a 'DEQUEUE' function run in another partition if necessary (Once the enqueue failure has been cleared, the partition can be restarted by CASTART so that processing can continue).


(END/ENTER) retry the catalog enqueue request.

Messages 2–261


CADT062I — SENSE COMMAND CUU=cuu SNS=xxxxxxx

Reason:

SENSE operator command has been issued for a tape drive. The current sense status is returned.

Action:

None.

CADT063E — CANNOT ACTIVATE HOOK - INSUFFICIENT GETVIS STORAGE

Reason:

A user exit was to be entered by CA-Dynam/T, but sufficient GETVIS storage is not available for user exit processing.

Action:

Increase the amount of partition GETVIS which is available.

CADT064I — DSN='data-set-name' VER=nnn CREATE=mm/dd/yy VOL=volser SCRATCHED

Reason:

The CA-Dynam/T automatic scratch function has scratched the noted version, and the tape has been returned to scratch status.

Action:

None.

CADT065D — MOUNT VOLUME volser DSN='data-set-name' JOB=jobname FOR OUTPUT

Reason:

The data set has been specified for ROTATE support, and an output open request requires that the noted tape be mounted for output.

Action:

Mount the requested tape and EOB or enter 'FREE' to list tape drives in a ready status, unassigned, and attached to this machine.



CADT066D — WRONG TAPE: VOL=volser HDR1='dsn' SYSnnn=cuu CLOSED CIRCUIT

Reason:

The data set has been specified for ROTATE support, and an output open MOUNT request has been satisfied with the wrong tape.

Action:

Mount the requested tape and EOB.

CADT067W — INVALID RESPONSE, NOT SUPPORTED AT EOV

Reason:

A response of 'DISK' has been made to a MOUNT message, and the request to modify the open from tape to disk cannot be honored. See the section on operator device switching in the User Guide.

Action:

Either cancel the job, or continue with normal MOUNT processing. The file cannot be placed on disk.

CADT068W — INVALID RESPONSE, NOT SUPPORTED ON MULTIFILE VOLUMES

Reason:


Action:


CADT069W — INVALID RESPONSE, D/FI IS NOT ACTIVE OR FILE IS OUTPUT FROM CA-SORT

Reason:


Messages 2–263


Action:


CADT070W — INVALID RESPONSE, UNSUPPORTED DTF TYPE

Reason:


Action:


CADT071W — INVALID RESPONSE, D/FI SWITCH SUPPORT NOT GENERATED

Reason:

A response of 'DISK' has been made to a MOUNT message, and the request to modify the open from tape to disk cannot be honored. See the section on operator device switching in the CA-Dynam VSE User Guide (CA-Dynam/FI) restrictions.

Action:


CADT072W — INVALID RESPONSE, D/FI CATALOG SUPPORT NOT GENERATED

Reason:


Action:




CADT073W — INVALID RESPONSE, DSN NOT IN CATALOG

Reason:


Action:


CADT074W — INVALID RESPONSE, CATALOG NOT CODED 'FI'

Reason:


Action:


CADT075W — INVALID RESPONSE, 'NOFI' CODED ON DLBL OR TLBL

Reason:


Action:


Messages 2–265


CADT076W — INVALID RESPONSE, FILE ALREADY OPEN

Reason:


Action:


CADT077W — INVALID RESPONSE, NOT SUPPORTED ON CA-SORT ALLOCATION

Reason:


Action:


CADT078E — LABEL ERROR OCCURRED dtfname F/C=nn R/C=nn

Reason:

An error return code has been received from the LABEL function of the System Adapter.

Action:

Find the cause of the error and correct. See System Adapter Return Codes in the CA-CIS Message Guide for more information.

CADT079E — NO LUBS AVAILABLE dtfname

Reason:

The operator has requested a switch from disk to tape, and there are no free LUBS available to assign to the tape unit. The job will be canceled.



Action:

Rerun the job.

CADT079I — NO LUBS AVAILABLE dtfname

Reason:

No free LUBS are available for dynamic LUB allocation.

Action:

None.

CADT080E — EXTERNAL SECURITY VIOLATION FILE=xxxxxxxx

Reason:

External security is installed and active, and a request for OPEN of a data set has been issued which would violate defined security restrictions. The program issuing the OPEN is not running from a job which is logged on as an external security user authorized to access the file. The job will be canceled.

Action:

Either resubmit the job with an ID statement for an authorized user, or contact the Security Administrator.

CADT081W — LABEL FOR dtfname IS MISSING

Reason:

The indicated label cannot be found.

Action:

Include label and rerun the job.

CADT082E — DSN=data-set-name IS UNLABELED

Reason:

A CA-Dynam/T controlled data set marked as unlabeled is being opened and the DTF does not have FILABL=NO specified.

Messages 2–267


Action:

The job is canceled. Resolve the error and run the job again.

CADT083A — MOUNT SCRATCH dtfname SYSnnn DSN=data-set-name OWNER=xx MODE=xx SIZE=xx JOB=jobname VOLID=xx FOR UNLABELED PROCESSING

CADT083A — MOUNT SCRATCH dtfname ON cuu DSN=data-set-name OWNER=xx MODE=xx SIZE=xx JOB=jobname VOLID=xx FOR UNLABELED PROCESSING

Reason:

A CA-Dynam/T controlled data set is being opened for unlabeled output, but the system could not locate a controlled scratch tape. The second format of this message (ON cuu) will be issued when the logical unit was previously assigned. In this case, that drive must be used.

Action:


CADT083D — MOUNT SCRATCH dtfname SYSnnn DSN=data-set-name OWNER=xx MODE=xx SIZE=xx JOB=jobname VOLID=xx FOR UNLABELED PROCESSING

CADT083D — MOUNT SCRATCH dtfname ON cuu DSN=data-set-name OWNER=xx MODE=xx SIZE=xx JOB=jobname VOLID=xx FOR UNLABELED PROCESSING

Reason:

A CA-Dynam/T controlled data set is being opened for unlabeled output, but the system could not locate a controlled scratch tape. The second format of this message (ON cuu) will be issued when the logical unit was previously assigned. In this case, that drive must be used.

Action:


Reply with To

cuumm direct the system to use a specific drive (Invalid if the logical unit was preassigned and necessary only to initialize a scratch "on the fly" or override mode or owner).



Reply with To




STOP place the partition in a wait state (awaiting CASTART).

RUN cuu|ALL

REW cuu|ALL

FSF cuu,nnn

BSF cuu,nnn

FSR cuu,nnn

BSR cuu,nnn

perform the indicated tape control operation to the drive indicated or to all drives (valid for unassigned drives, or for drives owned by the partition issuing the message).

SCRTCH cause CA-Dynam/T to display ten SCRATCH volumes on the console.

DISK cause CA-Dynam/T to attempt to invoke CA-Dynam/FI to change the DTF in the program from tape to disk (only valid if the complete CA-Dynam system (CA-Dynam/T, /D, and /FI) is installed and active, and only for a MOUNT request for Volume 1 of a controlled tape data set. See the "Controlling File Independence" chapter of the User Guide.

DYNLUB to release the logical unit assignment and dynamically allocate an available logical unit.






■ Does volid match the first 2-digits of the volser (if specified)?


Messages 2–269


CADT084D — VERIFY VOLUME NO=xxxxxx FOR UNLABELED PROCESSING

Reason:

This message is issued whenever an unlabeled dsn (TAPEOPT=NOLABEL) is being opened for output to verify that the volume is to be used for unlabeled processing.

Action:

EOB causes CA-Dynam/T to use this tape. CANCEL cancels the job. If the volume mounted is not the desired volume, dismount the volume, mount the correct volume and reply NEWTAP to verify the new volume.

CADT085D — MOUNT VOLUME xxxxxx DSN=data-set-name SYSnnn MODE=xx JOB=jobname VAULT=(v,sssss) FOR UNLABELED PROCESSING

Reason:

The data set in the mount message is being opened for unlabeled input processing.

Note that AVR is not performed for unlabeled input tapes since no labels exist on the tape.

Action:

Reply with To

cuu or cuumm force use of the specific unit.

CANCEL cancel this job.

STATUS obtain a list of all tape drives (on the console).


RUN cuu|ALL

REW cuu|ALL

FSF cuu,nnn

BSF cuu,nnn

FSR cuu,nnn

BSR cuu,nnn

perform the indicated tape control operation to the drive indicated, if the drive is unassigned or owned by the partition issuing the message.

STOP place the partition in a wait state (awaiting a CASTART).



Reply with To

ALTER direct the system to erase the label record being used and reopen the file in order to access the next sequentially submitted label record for this file.

RERUN direct the system to scratch Version 1 of this data set and reopen the file in order to access what was Version 2 as Version 1 (not valid for multifile).

ACCEPT DSN=

'data-set-name'

(,VER=nnn|

,VOL=xxxxxx)

cause CA-Dynam/T to reissue the OPEN and search for the indicated data set, version or volume instead of the one called for through JCL (Valid only if ACCEPT=YES has been generated; may be used to ACCEPT multifile data sets).


PREV reopen the file to access the next most current version (not valid for multifile data sets) Only valid if PREV=YES is specified in the CA-Dynam/T option record.

CADT086D — VERIFY VOLUME NO=xxxxxx IS ON cuu FOR UNLABELED PROCESSING

Reason:

This message is issued whenever an unlabeled dsn (TAPEOPT=NOLABEL) is being opened for input to verify that the correct volume is mounted.

Action:

EOB causes CA-Dynam/T to use this tape.

CANCEL cancels the job.

If the volume mounted is not the desired volume, dismount the volume, mount the correct volume and reply NEWTAP to verify the new volume.

Messages 2–271


CADT087E — UNABLE TO CONTACT SERVER RTC=xx IUCVCODE=xx

Reason:

This message is issued whenever IUCV communication cannot be established.

Action:

None. Normal CA-Dynam/T processing continues, but no dynamic ATTACHing or DETACHing of drives is performed.

CADT088D — UNABLE TO HONOR DISP=disp FOR DSN=data-set-name

Reason:

A CA-Dynam/T controlled data set is being opened for output and the DISP parameter on the TLBL cannot be honored.

Possible reasons are:

■ DSN is multifile.

■ Version 1 does not exist and DISP=OLD is specified.

■ Version 1 was never closed or is unlabeled.

Action:

A reply of CANCEL will cancel the job.

A reply of EOB will process as normal output (DISP=NEW processing).

CADT089D — DISP=MOD ENCOUNTERED dtfname SYSnnn DSN=data-set-name

Reason:

A CA-Dynam/T controlled data set is being opened for output and DISP=MOD is specified on the TLBL.

Action:

Reply with NEW to create a new file.

Reply with OLD to extend the existing file.

Reply with CANCEL to cancel the job.



CADT090I — xxxxxxxx or blanks (IF REPLY IS EOB)

Reason:

A reply has been made on the CMS machine. It is mirrored on the VSE machine for logging/audit trail purposes (CMS Interface - VSE SLAVE MODE only).

Action:

None.

CADT091W — AUTOCAT REQUEST DENIED, DSN DOES NOT CONFORM TO VSAM NAMING CONVENTIONS, dtfname PROCESSED UNCONTROLLED

Reason:

CA-Dynam/T was instructed to automatically catalog a data set, but the data set name in the TLBL does not conform to VSAM or OS/MVS naming conventions.

Action:

CA-Dynam/T will process the DTF as uncontrolled. If automatic cataloging of the data set is required, correct the data set name.

CADT092W — STATUS IS QUESTIONABLE FOR VOLUME=volume

Reason:

An attempt was made to use a scratch tape for output processing, but the data set name in its HDR1 label disagrees with the last known data set name recorded in the Catalog for this volume.

Action:

Mount a different scratch tape.

CADT093E — VOLUME SCRATCHED BEFORE EOV dtfname SYSnnn volume dsn

CADT093E — VOLUME SCRATCHED BEFORE CLOSE dtfname SYSnnn volume dsn

Reason:

The volume was scratched before updating Catalog linkages for the named output volser and data set. The job is terminated with a dump.

Messages 2–273


Action:

Increase the number of hours in the CA-Dynam/T option record DELETEH and OPENH parameters.

CADT094E — ATTACH FOR XSYSTEM RECEIVE FAILED R/C=xx

Reason:

The attach for the cross-system receive task failed. 'xx' is the return code.

Action:

None. Processing continues. If this problem persists, contact Computer Associates.

CADT095I — ATTACH SUCCESSFUL FOR XSYSTEM RECEIVE TASK. LA=xxxxxx

Reason:

The cross-system receive task was successfully attached. 'xxxxxx' is the load address of the task.

Action:

None.

CADT100W — CA-DYNAM/T POST-INITIALIZATION ERROR F/C=nnnn R/C=nnnn

Reason:


Action:

None or, if you determine the impact on your processing is serious enough, correct the error and re-IPL.

Function Code

Meaning and Action to be Taken

10 XSYSTEM function is not available. The System Adapter was unable to locate certain needed phases. Check LIBDEFs at CASAUTIL execution.



Function Meaning and Action to be Taken Code

11 XSYSTEM function; unable to locate phase CATXSSO. Check LIBDEFs at CASAUTIL execution.

12 XSYSTEM function; unable to attach subtask.

13 IUCV function; unable to obtain system GETVIS storage for CA-Dynam/T's AVRTABLE.

14 IUCV function; phase CATAIUXA not found. Check LIBDEFs at CASAUTIL execution.

15 Unable to locate DTPOOL, the CA-Dynam/T pool tape list. Run CACCDBU0 with parameters to define DTPOOL.

16 Unable to locate DTLOCK, the CA-Dynam/T pool lock list. Run CACCDBU0 with parameters to define DTLOCK.

17 Unable to locate DTNODET, the CA-Dynam/T pool node list. Run CACCDBU0 with parameters to define DTNODET.

18 Unable to locate DTDTFEX, the CA-Dynam/T DTF exclusion list. Run CACCDBU0 with parameters to define DTDTFEX.

19 Unable to locate DTLUBEX, the CA-Dynam/T LUB exclusion list. Run CACCDBU0 with parameters to define DTLUBEX.

20 Unable to locate DTNODE, the CA-Dynam/T XSYSTEM node. Run CACCDBU0 with parameters to define DTNODE.

21 Unable to locate DTPATH, the CA-Dynam/T XSYSTEM path. Run CACCDBU0 with parameters to define DTPATH.

The return codes are either internal CA-Dynam/T return codes or from IBM functions. Contact Computer Associates if the above actions do not resolve the problem.

CADT101E — CA-DYNAM/T POST-INITIALIZATION FAILURE F/C=nnnn R/C=nnnn

Reason:

Post-initialization has detected a severe error and will prematurely terminate. The impact on CA-Dynam/T processing varies depending upon the error.

Messages 2–275


Action:


Function Code

Meaning

0 Unable to locate CA-Dynam/T Option Record. Check the CAICUI label in standard labels and LIBDEFs at CASAUTIL execution.

1 CA-Dynam/T product is not active. Check startup procedure, LIBDEFs, etc.

2 Unable to locate CA-Dynam/T, the CA-Dynam/T System Option Record. Run CACCDBU0 with parameters to define DTOPTIONS.

3 System Adapter saver function involving CA-Dynam/T control block 'DTPSTOR'. Probably lack of system GETVIS storage.

4,5,6 Problem with IBM phase $IJJTTOP. This will lead to difficulties with CA-Dynam/T EOV processing. Contact Computer Associates for assistance.

The return codes are either internal CA-Dynam/T return codes or from IBM functions. Contact Computer Associates if the above actions do not resolve the problem.

CADT102E — VOLUME=xxxxxx CONTAINS ACTIVE CA-ASM/ARCHIVE DATA

Reason:

An attempt was made to write on an active CA-ASM/ARCHIVE tape.

Action:

Mount a nonactive CA-ASM/ARCHIVE tape.

CADT103E — GETVIS FAILURE - UNABLE TO SEND DYNCLOSE COMMAND

Reason:

An attempt to acquire GETVIS storage failed during DYNCLOSE processing

Action:

None. Dynamically attached tape drive may not be detached by the DYNVM interface.



CADT104E — VTAPE SAVER ENTRY NOT FOUND

Reason:

An internal error is detected by CA-Dynam/T during VTAPE processing.

Action:

The job is cancelled. Collect as much diagnostic information as possible and contact Computer Associates Technical Support.

CADT202W — CONTROL STATEMENT INVALID, STATEMENT BYPASSED

Reason:

The operation code in the control card is not valid.

Action:

Correct the control card and rerun the job.

CADT208W — SYSTEM NUMBER INVALID, STATEMENT BYPASSED

Reason:

The logical unit number (SYSnnn) specified is invalid. For the TDYNASN 'ASSGN' function, the logical unit must be a programmer logical unit.

Action:

Correct the statement and restart.

CADT220I — NO MORE AVAILABLE DUMMY DEVICES

Reason:

The // ASSGN SYSnnn DUMMY function of TDYNASN has been executed, and there are no available dummy devices (7F0-7FF) to make the assignment.

Action:

None.

Messages 2–277


CADT226D — ENTER TDYNASN COMMAND

Reason:

TDYNASN is being executed from the console and, therefore, will read all commands from the console.

Action:

Enter any valid TDYNASN command or reply 'END' or 'EOB' to terminate TDYNASN.

CADT331E — TRACE NOT ACTIVATED. PARTITION ID OMITTED OR INVALID

Reason:

You must specify a partition ID as part of the CATRACE command.

Action:

Correct the command and then reissue the CATRACE.

CADT332E — TRACE NOT ACTIVATED. CUU SPECIFIED IS INVALID OR DOWN

Reason:

The device specified for cuu is in deviced-down status, or not a tape cuu, or unknown to the system.

Action:

Reenter the CATRACE command with a correct cuu.

CADT333E — UNABLE TO LOCATE/LOAD CATAPOFA

Reason:

The CA-Dynam/T POWER POFFLOAD subtask phase could not be found or loaded.

Action:

Check the current LIBDEF to make sure the CA-Dynam library is on the active chain.



CADT334E — UNABLE TO ATTACH SUBTASK CATAPOFA

Reason:

A problem occurred trying to attach the CA-Dynam/T POWER POFFLOAD processing subtask in the POWER partition.

Action:

None. The command is terminated. If the problem persists, contact Computer Associates for assistance.

CADT400D — ENTER COMMAND STRING

Reason:

The program TDYNUTL is being executed from the console typewriter or from SYSIPT without control statements.

Action:

Enter any valid TDYNUTL command. In order to terminate the program execution, enter EOB or a null response.

CADT403W — VOLUME SERIAL NUMBER NOT IN FILE

Reason:

A display function is being performed on a volume serial number, and there is no version record in the file for the data set that matches the volume serial number.

Action:

None. Processing continues. If the problem persists, contact Computer Associates for assistance.

CADT404I — DATA SET NAME NOT IN FILE

Reason:

A display function is being performed on a volume serial number, and the data set name in the VBR does not appear in the file.

Messages 2–279


Action:

None. Processing continues. If the problem persists, contact Computer Associates for assistance.

CADT405D — DISK DATASET

Reason:

A display function is being performed on a data set name which is in catalog as a disk data set.

Action:

Display any tape data set, or EOB.

CADT406I — SCRATCH TAPE

Reason:

A display on volume serial number is being performed, and the specified volume is a scratch tape. This can be a normal occurrence.

Action:

None. No error exists. The indicated volume is in scratch status.

CADT408I — ACTIVE - NODSN

Reason:

A display on a volume serial number is being performed and the specified volume is active but not attached to a data set. This can be a normal occurrence.

Action:

None. No error exists. The indicated volume is not in scratch status.

CADT414W — INVALID COMMAND STRING

Reason:

TDYNUTL has detected an invalid command or an invalid parameter in the input.



Action:

Correct the invalid input card and resubmit.

CADT415W — DATA SET NAME NOT FOUND IN CATALOG FILE

Reason:

TDYNUTL is performing a display function and cannot locate the data set record for the specified volume serial number.

Action:

None. Processing continues. If this problem persists, contact Computer Associates for assistance.

CADT420W — VERSION NOT IN FILE

Reason:

A 'PULL' card that specifies a 'VER =' parameter has been processed, but the specified version does not exist.

Action:

None. Processing continues. The parameter is ignored.

CADT425W — WRONG LENGTH RECORD ON SYSIN

Reason:

TDYNUTL has detected an incorrect record length on SYSIN.

Action:

None. The record is not processed.

CADT430W — CATALOG PASSWORD IS MISSING OR INVALID

Reason:

The Catalog password is missing or invalid.

Action:

Correct the catalog password on the list password command and resubmit.

Messages 2–281


CADT500E — STORAGE ALLOCATION FAILURE

Reason:

The System Adapter GETAREA function was unable to obtain sufficient GETVIS storage for its I/O buffer(s).

Action:

Processing will terminate. Increase partition size or reduce SIZE= parameter on // EXEC statement if applicable.

CADT501D — ENTER NUMBER OF INPUT FILES

Reason:

The multiple input files UPSI bit is on (X'80'), and TDYNCOPY is requesting the number of input files to process.

Action:

Enter a one- or two-digit number (from 1-99) indicating the number of input files.

CADT502W — ENTRY IS NOT NUMERIC OR INVALID

Reason:

Previous response was invalid or not numeric.

Action:

None. The original message is reissued.

CADT503D — ENTER LOGICAL RECORD LENGTH

Reason:

The reblocking function is indicated (UPSI X'04'), and TDYNCOPY is requesting the logical record length.

Action:

Enter a one- to five-digit number in the range 1 to 32767.



CADT504D — ENTER NEW BLOCKING FACTOR

Reason:

The reblocking function is indicated (UPSI X'04'), and TDYNCOPY is requesting a blocking factor to be applied to the new record size. The new block size will be this factor times the record length.

Action:

Respond with a one- to four-digit number in the range 1 to 9999.

CADT505W — NEW BLOCKSIZE OF nnnnn BYTES IS TOO LARGE

Reason:

The calculated block size specified in the message is greater than 32767 bytes.

Action:

None. Messages CADT503 and CADT504 will be reissued.

CADT506I — NEW BLOCKSIZE IS nnnnn BYTES

Reason:

The new block size is indicated.

Action:

None.

CADT507I — TDYNCOPY END

Reason:

Program execution is completed.

Action:

None.

Messages 2–283


CADT508W — INCOMPATIBLE UPSI SETTINGS

Reason:

Conflicting functions are indicated by the UPSI setting, such as UPSI X'48', multifile output and stacking.

Action:


CADT509I — BLOCK COUNT=nnnnnnn INPUT

Reason:

End-of-file has been detected, and the specified number of blocks were read from the input file.

Action:

None.

CADT510I — BLOCK COUNT=nnnnnnn OUTPUT

Reason:

An output file is being closed, and the specified number of blocks were written.

Action:

None.

CADT511I — CHECKPOINT RECORDS BYPASSED

Reason:

TDYNCOPY is either stacking or reblocking and encountered checkpoint records. They are ignored.

Action:

None.



CADT512W — INPUT BLOCKSIZE NOT MULTIPLE OF RECORD SIZE

Reason:

TDYNCOPY is performing the reblocking function and encountered an input block which is not evenly divisible by the record size specified in response to message CADT503.

Action:


CADT514W — FILES=NN STATEMENT INVALID OR MISSING

Reason:

The FILES=nn statement is invalid or missing.

Action:

Correct input and resubmit.

CADT515W — LRECL=nnnnn STATEMENT INVALID OR MISSING

Reason:

The LRECL=nnnnn statement is invalid or missing.

Action:


CADT516W — NRECS=nnnn STATEMENT INVALID OR MISSING

Reason:

The NRECS=nnnn statement is invalid or missing.

Action:


Messages 2–285


CADT517W — UIN=xxx INVALID, xxx MUST BE REW, RUN OR NOR

Reason:

The UIN specification is incorrect. It must be REW, RUN or NOR.

Action:


CADT518W — UOUT=xxx INVALID, xxx MUST BE REW, RUN OR NOR

Reason:

The UOUT specification is incorrect. It must be REW, RUN or NOR.

Action:


CADT519W — INVALID STATEMENT STARTING WITH ....

Reason:

There is an invalid statement.

Action:


CADT520D — ENTER NUMBER OF TEST PATTERNS OR EOB

Reason:

You must enter the number of test patterns.

Action:

Respond with either one digit indicating the number of dummy labels to be printed in order to obtain correct alignment, or EOB to continue processing if no test labels are desired.



CADT521W — INVALID OR NON-NUMERIC RESPONSE

Reason:

The previous reply was either not numeric or otherwise invalid.

Action:

None. The original request will be reissued.

CADT522D — ENTER STARTING NUMBER

Reason:

A starting number must be entered.

Action:

Respond with a one- to six-digit number indicating the first label to be printed, or enter EOJ.

CADT523D — ENTER ENDING NUMBER

Reason:

An ending number must be entered.

Action:

Respond with one- to six-digit number indicating the last label to be printed. A response of 'EOJ' is also permitted.

CADT524D — ENTER NUMBER OF LINES BETWEEN LABELS

Reason:

The number of lines between labels must be entered.

Action:

Respond with a 1-digit number indicating the number of blank lines to be skipped between numbers. If you are unsure, start with 5 and work from there, using the test pattern facility. Default value is 9. For the brown CA-Dynam/T labels, this number should be 9.

Messages 2–287


CADT525I — SET PRINTER FOR 8 LINES PER INCH

Reason:

This message is a reminder to print the labels at 8 LPI for easier readability.

Action:

None.

CADT526W — INVALID CONTROL STATEMENT

Reason:

An error has been detected while TDYNLBL was trying to process a command. If the program is executed from the console, TDYNLBL will prompt the operator; if executed from batch, the job is canceled.

Action:


CADT527W — INVALID BEGIN OR END PARAMETER

Reason:

If the program is executed from the console, TDYNLBL will prompt the operator. If it is executed from batch, the job is canceled.

Action:


CADT528W — INVALID TEST PARAMETER

Reason:


Action:




CADT529W — INVALID SKIP PARAMETER

Reason:


Action:


CADT530W — INVALID DIGITS PARAMETER

Reason:


Action:


CADT531D — ENTER LABEL PREFIX

Reason:

Label prefix must be entered.

Action:

Respond with a one- to six-character alphanumeric label prefix or EOB if no prefix is desired. 'EOJ' will end job.

CADT532D — ENTER NUMBER OF DIGITS

Reason:

The number of digits must be entered.

Action:

Respond with a 1-digit number (from 1 to 6) indicating the number of digits to be printed. Default is 6 minus length of prefix.

Messages 2–289


CADT533D — INVALID PREFIX AND DIGITS COMBINATION

Reason:

The prefix length added to the digits value can't exceed a maximum label length of six.

Action:

Specify lengths for the prefix and digits that when added together do not exceed 6 digits.

CADT534D — ENTER INCREMENT NUMBER

Reason:

An increment number can be entered.

Action:

Enter a one- to six-digit number; it will be added to each label number to determine the next label number to print. Or, respond EOB to increment by one (the default value) for sequential numbering of labels.

CADT535D — ENTER LENGTH OF TEST PATTERN

Reason:

The number of characters on the test patterns can be entered.

Action:

Enter a number from one to six; this will be the number of characters printed on each test pattern. Or, respond EOB to default to six characters.

CADT536E — TAPE I/O ERROR

Reason:

TDYNCOPY has received an I/O error trying to reposition the tape being copied.

Action:

Processing will continue but, depending on the tape position, may or may not complete successfully. Rerun the job with an // OPTION PARTDUMP statement and contact Computer Associates.



CADT537W — REBLOCKING HAS BEEN REQUESTED ON A NON FIXED FILE

Reason:

Reblocking has been requested for TDYNCOPY and the file is not a fixed or fixed blocked file

Action:

Processing will continue and TDYNCOPY will try to reblock the file. Successful completion will depend on the input blocksize and the reblocking parameters submitted.

CADT550I — TDYNRST BEGIN

Reason:

The program TDYNRST is being executed.

Action:

None.

CADT551D — ENTER TDYNRST PARAMETERS

Reason:

TDYNRST parameters must be entered.

Action:

Enter TDYNRST parameter to indicate which tape file is to be restarted and at what point. The following are valid parameters:

■ a 1- to 7-character DTFNAME

■ a 1- to 6-character volume serial number

■ a 1- to 4-character volume sequence number

■ an 'I' for input

■ an 'O' for output

Messages 2–291


CADT552W — PARAMETERS ARE INVALID

Reason:

The parameter entered was invalid.

Action:

Enter a valid parameter.

CADT553W — NO TLBL FOUND FOR *dtfname*

Reason:

No TLBL matching the dtfname provided in the parameter was found in the label area.

Action:

Verify that the dtfname entered corresponds exactly to the dtfname on the TLBL, and be sure that the TLBL was submitted before the execution of TDYNRST in the JCL, or that it exists on the PARSTD or STDLABEL track.

CADT554W — DSN *data set name* NOT IN CATALOG FILE

Reason:

The data set name specified on the TLBL being processed does not match an entry in the data set name catalog.

Action:

Verify that the TLBL being processed contains a data set name under CA-Dynam/T control.

CADT555W — TAPE xxxxxx IS DN *data set name*

Reason:

The tape volume specified is an active member of the data set indicated and is not available for restart. To be available for restart, a volume must be in 'OPEN' - NOT CLOSED' status.

Action:

Verify that the correct volume was specified.



CADT556E — UNEXPECTED LABEL ERROR HAS OCCURRED

Reason:

TDYNRST has received an error during a call to the IBM label interface.

Action:

Collect documentation and contact Computer Associates.

CADT557W — DSN REQUESTED IS MULTI-FILE

Reason:

The data set specified on the TLBL being processed is a member of the multifile data set. Multifile data sets are not eligible for restart using TDYNRST.

Action:

Verify that the correct dtfname was entered and that the data set specified is not multifile.

CADT558W — VOL xxxxxx NOT IN DN *data set name*

Reason:

For input files, the specified volume serial number is not a member of the data set indicated; for output files, the data set name under which the volume was last opened does not match the current data set name.

Action:

Verify that the correct volume serial number is specified for the data set being restarted.

CADT559W — VOL xxxxxx IS NOT VOL SEQ NO ssss

Reason:

The volume serial number specified does not match the volume sequence number (ssss) specified.

Action:

Verify that the volume sequence number entered for the volume being restarted is correct.

Messages 2–293


CADT560W — VOL xxxxxx IS IN STATUS x

Reason:

The volume specified is not in a valid status for TDYNRST; in order to be restarted, a volume must be in 'OPEN - NOT CLOSED' status.

Action:

Verify that the correct volume was specified.

CADT561I — FILE xxxxxxx LABEL HAS BEEN UPDATED

Reason:

The TLBL for the file specified has been successfully updated.

Action:

None.

CADT562W — VOL xxxxxx NOT IN CATALOG FILE

Reason:

The volume specified is not in the serial number file.

Action:

Verify that the serial number entered is correct.

CADT563I — TDYNRST END

Reason:

TDYNRST program has ended.

Action:

None.



CADT564W — DN *data-set-name* IS LOCKED

Reason:

Data set being restarted is locked.

Action:

Verify the status of the data set being restarted.

CADT565I — INPUT:

Reason:

TDYNRST has been executed with an UPSI 1 and will display each input card upon the console.

Action:

None.

CADT566E — CA-DYNAM/T IS NOT ACTIVE. JOB CANCELED.

Reason:

CA-Dynam isn't active.

Action:

None.

CADT567E — DTF IS EXCLUDED FROM CONTROLLED PROCESSING

Reason:

CA-Dynam/T maintains a list of dtfnames that are excluded from controlled processing. This feature is activated by coding a DTDTFEX option record with the DTFNAMEs to exclude from CA-Dynam/T processing.

Action:

None.

Messages 2–295


CADT570D — ENTER 'Y' FOR TDYNRST PARAMETERS

Reason:

A 'Y' for TDYNRST parameters must be entered.

Action:

Enter 'Y' for display of valid TDYNRST parameter format upon console; enter any other character or EOB/END to continue.

CADT571I — VALID FORMAT FOR TDYNRST PARAMETERS:

Reason:

A response of 'Y' to message CADT570 was issued.

Action:

None.

CADT572W — MIXED RECORD FORMATS NOT PERMITTED WITH STACKING

Reason:

You have requested TDYNCOPY to process multiple input tapes. These tapes are not all the same formats. For example, one tape is fixed block and another is variable format.

Action:

When MODON 10 is not ON, TDYNCOPY will be canceled. With MODON 10 ON, this message is only a warning. See TDYNCOPY section for more information.

CADT600I — TDYNVLT BEGIN

Reason:

TDYNVLT has begun.

Action:

None.



CADT602I — TDYNVLT CATALOG UPDATE BEGIN

Reason:

The CA-Dynam Catalog update has begun.

Action:

None.

CADT603I — TDYNVLT CATALOG UPDATE ENDED

Reason:

The CA-Dynam Catalog update has completed.

Action:

None.

CADT604I — TDYNVLT CATALOG DEQUEUED

Reason:

The CA-Dynam Catalog is dequeued.

Action:

None.

CADT605E — TDYNVLT NO STORAGE AVAILABLE FOR INITIALIZATION

Reason:

TDYNVLT cannot find enough partition GETVIS to process.

Action:

Increase partition GETVIS. Note that TDYNVLT should always run with a SIZE= parameter in the EXEC statement.

Messages 2–297


CADT606E — TDYNVLT UNEXP. ERROR

Reason:

An unexpected error has occurred.

Action:

Get the output produced by TDYNVLT when the unexpected error occurred and contact Computer Associates.

CADT607I — TDYNVLT REPORTS BEGIN

Reason:

Printing of the reports has been started.

Action:

None.

CADT608I — TDYNVLT REPORTS ENDED

Reason:

Printing of the reports has completed.

Action:

None.

CADT609I — TDYNVLT END

Reason:

This execution of TDYNVLT is complete.

Action:

None.



CADT610E — TDYNVLT VBR NOT FOUND DSN=dsn VOL=volser VRS=version

Reason:

Volume base record in the CA-Dynam Catalog cannot be found. There is catalog corruption. The volume is ignored and TDYNVLT continues processing. This will also be reported in the TDYNVLT exception report.

Action:

Perform a DYNCAT BACKUP/RESTORE REORG sequence. If the problem persists, contact Computer Associates.

CADT611E — TDYNVLT CATMAN ERROR OCCURRED FILE=WORK1 F/C=xxxx R/C=xxxxx

Reason:

An error was encountered while writing or reading the WORK1 TDYNVLT workfile. WORK1 uses Computer Associates catalog management to write and read.

Action:

Contact Computer Associates. See "Catalog Management Return Codes" for more information.

CADT612E — TDYNVLT CATALOG ERROR MOD=xx F/C=xxxx R/C=xxxx

Reason:

A CA-Dynam Catalog error was encountered.

Action:

Contact Computer Associates. See "Catalog Management Return Codes" for more information.

CADT613E — CAIEXTR ERROR - FUNCTION=xxxx R/C=xxxx

Reason:

EXTRACT was specified and an error was encountered processing CAIEXTR.

Action:

Make sure the labels and assignments are in place for the CAIEXTR file.

Messages 2–299


CADT615I — ENTER TDYNVLT COMMAND

Reason:

TDYNVLT has been executed from the console, and control card input is accepted from there.

Action:

Enter the TDYNVLT control statements. When all control statements have been entered, enter (EOB|END|ENTER) to start TDYNVLT processing. If no control statements are entered TDYNVLT will end without any processing.

CADT616I — INVALID TDYNVLT COMMAND, STATEMENT BYPASSED.

Reason:

An invalid TDYNVLT control card has been encountered.

Action:

Correct the control card and rerun.

CADT617W — nnnnnnn BLOCKS DROPPED DUE TO BLOCKS LESS THAN 12 BYTES.

Reason:

TDYNCOPY has encountered blocks of less than 12 bytes in length which have not been copied to the output tape

Action:

If input tape contains valid data blocks less than 12 bytes long, TDYNCOPY cannot be used to copy dataset



CADT625E — CATALOG MANAGEMENT ERROR - type

Reason:

An error was detected during TDYNCLEN. Refer to the reason that reason that corresponds to the message type.

Type Reason

LOGIC ERROR SEE RET CODE

An unexpected return code has been issued by the Catalog Management component.

PHYSICAL I/O ERROR

A physical I/O error has occurred during Catalog access. The integrity of the Catalog is in doubt.

INVALID CPL ADDRESS

An internal error was detected during Catalog access.

NONZERO REG 15 FROM CAT MGT

An unexpected error has occurred during Catalog access.

Action:

Refer to the action that corresponds to the message type.

Type Action

LOGIC ERROR SEE RET CODE

Inspect the Catalog Management return code given in message CADT626E. If the problem is not clear, collect diagnostic information and contact Computer Associates.

PHYSICAL I/O ERROR

Check the integrity of the Catalog by running the DYNCAT BACKUP command. If necessary, the Catalog may have to be rebuilt.

INVALID CPL ADDRESS

Collect diagnostic information and contact Computer Associates.

NONZERO REG 15 FROM CAT MGT

Inspect the Catalog Management return code given in message CADT626E. If the problem is not clear, collect the diagnostic information and contact Computer Associates.

Messages 2–301


CADT626E — ADAPTER RET CODE IS nnnn. DISPLACEMENT IN TDYNCLEN IS nnnn.

Reason:

This message may be issued by the System Adapter or Catalog Management if an unexpected condition is encountered while processing a request which should complete normally.

Action:

Inspect the return code and additional error messages, if present, for more information. Contact Computer Associates for further assistance if needed.

CADT627W — REQUIRED KEYWORD MISSING. (OPENS OR ERRORS)

Reason:

Required keyword is missing.

Action:


CADT628W — SPELLING ERROR ON CONTROL CARD

Reason:

There is a spelling error on a control card.

Action:


CADT629W — NUMERIC FIELD IS MORE THAN 3 DIGITS

Reason:

The numeric field is more than three digits.

Action:




CADT630W — THE "STATUS=" KEYWORD HAS INVALID OPERAND

Reason:

The STATUS= keyword has an invalid operand.

Action:


CADT631W — NUMERIC FIELD HAS NON-NUMERIC DATA

Reason:

The numeric field has nonnumeric data.

Action:


CADT650I — ENTER TDYNPULL COMMAND

Reason:

TDYNPULL was executed through the system console.

Action:

Enter a JCL statement. A null response is considered as the end of input.

CADT651E — CATALOG ERROR DISP=dddd F/C=ffff R/C=rrrr

Reason:

An unexpected error occurred while accessing the Catalog. The job will be terminated with a dump.

Action:


Messages 2–303


CADT652E — DYNAM CONTROL PHASE CAN NOT BE LOCATED.

Reason:

An unexpected error occurred while trying to access the CA-Dynam product control phase. The job will be terminated with a dump.

Action:


CADT653E — INSUFFICIENT STORAGE AVAILABLE TO CONTINUE.

Reason:

There is not enough storage for TDYNPULL to continue. The job will be terminated.

Action:


CADT654E — ERROR LOADING PHASE pppppppp R/C=xx.

Reason:

An unexpected error occurred while trying to load a phase. The job will terminate with a dump.

Action:




CADT655E — DYNAM/T CONTROL PHASE CAN'T BE LOCATED.

Reason:

An unexpected error occurred while trying to access the CA-Dynam/T product control phase. The job will terminate with a dump.

Action:


CADT656E — OBTAIN FUNCTION FAILED.

Reason:

An unexpected error was returned by the System Adapter OBTAIN function. The job will terminate with a dump.

Action:


CADT657E — AN ERROR OCCURRED ON A SRAM REQUEST=xx R/C=xx

Reason:

An unexpected error was returned by a SRAM function. The job will terminate with a dump.

Action:


Messages 2–305


CADT658E — TDYNPULT PHASE CONTAINS INVALID DATA.

Reason:

The pull-table phase, TDYNPULT, contains invalid data.

Action:

Ensure that the pull table assembled correctly, otherwise retain the console log, SYSLST output, and dumps for the systems programmer to aid in problem determination. If the error persists, take a DYNCAT BACKUP of the catalog file before beginning any other error correction measures. See "Catalog Management Return Codes" for more information.

CADT840E — *** UNABLE TO ACCESS FILE:ddname *** RTC=nn nn

Reason:


Action:

Informational only. If the SECURITY option was selected, the request will be canceled. Refer to Catalog Management return codes for explanation. Most likely, the cause is one of the following:


■ The filemode specified in the FILEDEF statement for the named file is not assigned to the device upon which the file resides.

■ A FILEDEF command has not been issued for the named file.

CADT840W — *** UNABLE TO ACCESS FILE:ddname *** RTC=nn nn

Reason:


Action:

Informational only. If the SECURITY option was selected, the request will be canceled. Refer to Catalog Management return codes for explanation. Most likely, the cause is one of the following:




■ The filemode specified in the FILEDEF statement for the named file is not assigned to the device upon which the file resides.

■ A FILEDEF command has not been issued for the named file.

CADT841D — DEVICE cuu IS NOT A FREE TAPE DEVICE

Reason:

The indicated device address was entered as a response to a CA-Dynam/T message, but the device is either not a tape device or the tape unit is not currently available for use.

Action:

Reply to the original message again.

CADT842I — cuu IS NOT A TAPE DEVICE OR NOT IN DTPOOL

Reason:

An operator tape drive status request has been issued and the named cuu is either not a tape device or the tape drive is not defined in the DTPOOL macro.

Action:

Correct the DTPOOL error and restart the system.

CADT843I — CONNECTION WITH VSE GUEST MAY HAVE BEEN SEVERED

Reason:

An IUCV error has been detected attempting to communicate with a VSE guest running CA-Dynam/T VSE.

Action:

Determine if a VSE guest running CA-Dynam/T VSE, communicating with CA-Dynam/T VM has been IPLed. If it has, this error and the CADT772E message previously issued can be ignored. If not, retain the console logs and contact Computer Associates for assistance.

Messages 2–307


CADT844W — VOLUME nnnnnn IS OUTSIDE ALLOWABLE RANGE

Reason:

The volume serial number specified is outside the allowable range of numbers as established in the volser parameter of the CA-Dynam/T macro.

Action:

Select another volume serial number. If the range specified in the CA-DynamT macro is in error, refer the problem to the systems programmer for resolution.

CADT845D — VERIFY UNCONTROLLED USE OF VOLUME: nnnnnn, ddname userid cuu

Reason:

An uncontrolled tape file is being opened for output, and the tape on the specified drive is a CA-Dynam/T scratch tape.

Action:

Remove the CA-Dynam/T scratch tape, and replace it with a non-CA-Dynam/T scratch and (EOB)/END/ENTER to verify the new tape. Or respond 'ACCEPT' to override CA-Dynam/T and the controlled scratch tape to be used.

CADT847E — ERROR AT CLOSE/EOV userid cuu volser data set name

Reason:

An error has been detected at CLOSE or End of Volume while attempting to update the catalog linkages for the named output volser and data set. This results from an operator error during AVR or OPEN, most commonly from the tape having been physically moved from the drive during OPEN processing, and mounted on another drive, and the first drive having been used by another volume.

Action:

Verify that the tapes referenced are accurate, and display the catalog for this data set and other concurrently created data sets to resolve the problem.



CADT848I — nnnnnn OWN=xx yy

Reason:

A response of 'SCRTCH' was entered to a CADT808 mount scratch message. CA-Dynam/T lists ten scratch volumes from the Catalog so that a scratch can be located. The owner code (xx) is indicated if the volume is owned. 'OWN=**' indicates no owner. 'yy' is the length of the volume. '**' indicates no specified length. The CADT808 mount message is repeated.

Action:

None.

CADT849E — FATAL CAM ERROR, xx/xxxxxx xxxx (xxxxxxxx/xxxx)

Reason:

An unexpected error has occurred while accessing the catalog. Catalog corruption may have occurred, but it is likely that the error is inconsequential. Since the catalog file is blocked and highly organized, an event such as an operator issuing a FLUSH command, or an emergency cancel, may have terminated CA-Dynam processing before catalog update was complete, resulting in one or more incomplete version records. The problem can be corrected by a BACKUP/RESTORE REORG/SCRATCH run. Other possibilities include an out-of-storage condition during catalog processing, or even a catalog full condition while adding a new data set name or volume serial number inline. The request is terminated.

Action:

Retain the console log, printer output, and dumps for the systems programmer to aid in problem determination. If the error persists, take a DYNCAT BACKUP of the catalog file before beginning any other error correction measures.

Messages 2–309


CADT850D — CATALOG ENQUEUE FAILURE - FILE 'ddname'

Reason:

Request for catalog enqueue has failed. The catalog is in use by another task.

Action:

Awaits operator response.

Reply with To

CANCEL cancel the request

(END/ENTER) retry the catalog enqueue request

CADT861I — LMS INITIALIZATION STARTED

Reason:

CA-Dynam/T has begun the initialization process with the Library Management Software service machine.

Action:

None.

CADT862I — mtc COMMAND CUU=cuu: command text

Reason:

An MTC operator command has been issued for a tape drive. The command text will give information about the command status. If the SENSE command is issued, the current sense status is returned.

Action:




CADT863E — CANNOT ACTIVATE HOOK -- INSUFFICIENT STORAGE

Reason:

No storage available at initialization time.

Action:

Increase storage size.

CADT864I — DSN='data set name' VER=nnn CREATE=mm/dd/yy VOL=volser SCRATCHED

Reason:

The CA-Dynam/T automatic scratch function has scratched the noted version, and the tape has been returned to scratch status.

Action:


CADT865A — MOUNT VOLUME volser DSN='data set name' USER=userid FOR OUTPUT

Reason:


Action:

Mount the requested tape.

CADT865D — MOUNT VOLUME volser DSN='data set name' USER=userid FOR OUTPUT

Reason:


Action:


Messages 2–311


CADT865I — MOUNT VOLUME volser DSN='data set name' USER=userid FOR OUTPUT

Reason:


Action:


CADT866D — WRONG TAPE: VOL=volser HDR1='dsn' cuu CLOSED CIRCUIT

Reason:

The data set has been specified for ROTATE support, and an output open MOUNT request has been satisfied with the wrong tape.

Action:


CADT867I — LMS INITIALIZATION COMPLETED

Reason:

CA-Dynam/T has completed the initialization process with the Library Management Software service machine.

Action:

None.

CADT868E — DEVICE ATTACH FAILURE userid cuu ** RC=nnn **

DEVICE DETACH FAILURE userid cuu ** RC=nnn **

DEVICE WAIT FAILURE userid cuu ** RC=nnn **

Reason:

An error occurred while attempting to attach, detach or detach/wait the noted tape device for the specified userid. The value nnn is the return code for the ATTACH and DETACH commands. Possible return code values are documented in the IBM VM/SP CP Command Reference Guide.



Action:

Determine the cause of the error and correct the condition. If the open request was issued using the SMSG Facility or if the request was issued by an alternate userid, check to see if the specified virtual address is already defined in the machine. Correct the error and reissue the request.

CADT869E — ACS ___________ REQUEST - REPLY AREA TOO SMALL, INCREASE TO ________

Reason:

Not enough storage was allocated to allow the Automated Cartridge Subsystem server to process a request.

Action:

Retain console logs and contact Computer Associates.

CADT870E — ACS ___________ REQUEST - INVALID DATA IN REQUEST BLOCK AT OFFSET ______

Reason:

A request passed to the Automated Cartridge Subsystem server contained invalid parameter specifications.

Action:


CADT871E — ACS ___________ REQUEST - UNRECOVERABLE ERROR

Reason:

An error occurred on a request to the Automated Cartridge Subsystem server. The request could not be processed.

Action:


Messages 2–313


CADT872E — ACS ___________ REQUEST - REQUEST FAILED, REASON CODE _______

Reason:

An error occurred on a request to the Automated Cartridge Subsystem server. The request could not be processed. The reason code is the error code returned by the Automated Cartridge Subsystem server.

Action:


CADT873 — NO CA/DYNAMT SCRATCH VOLUMES AVAILABLE IN AUTOMATED LIBRARY

Reason:

During AVR processing for a scratch volume, no suitable CA-Dynam/T scratch volumes could be found in the STK 4400 Automated Cartridge Subsystem, Memorex, LMS, or IBM 3494/3495 Tape Library.

Action:

Add CA-Dynam/T scratch volumes to the Tape Library.

CADT874I — _______ INITIALIZATION STARTED

Reason:

CA-Dynam/T has begun the initialization process with the STK 4400 Host Software Component (ACS) or IBM 3494/3495 Tape Library Server (IBM).

Action:

None.

CADT875I — _______ INITIALIZATION COMPLETED

Reason:

CA-Dynam/T has completed the initialization process with the STK 4400 Host Software Component (ACS) or IBM 3494/3495 Tape Library Server (IBM).

Action:

None.



CADT876I — _______ INTERFACE HAS BEEN DISCONNECTED - WILL BE RE-ESTABLISHED WHEN AVAILABLE

Reason:

The interface between CA-Dynam/T and the STK4400 Host Software Component (ACS) or IBM 3494/3495 Tape Library Server (IBM) has become disabled due to an IUCV error or shutdown/abend of the Subsystem server.

Action:

None, the interface will be re-enabled when available.

CADT877I — ACS ____ LSM __ ---- ______ SCRATCH VOLUMES

Reason:

A display of the number of scratch volumes contained in the Automated Cartridge Subsystem module. This reflects a count based on the Subsystem catalog, not the CA-Dynam/T scratch count. This message is given in response to a QUERY SCRATCH command.

Action:

None.

CADT880I — UNABLE TO CONNECT TO _______ SERVER - WILL ESTABLISH CONNECTION WHEN POSSIBLE

Reason:

On initialization of CA-Dynam/T, a connection to the STK 4400 (ACS) or IBM 3494/3495 (IBM) server could not be made. Connection will be established when available.

Action:

None.

CADT881E — LMS ___________ REQUEST - REQUEST FAILED, REASON CODE _______

Reason:

An error occurred on a request to the Library Management Software server machine. The request could not be processed. The reason code is the error code returned by the Library Management Software server machine.

Messages 2–315


Action:

Retain console logs and contact Computer Associates for assistance.

CADT882E — LMS ________ REQUEST - UNCOVERABLE ERROR

Reason:

An error occurred on a request to the Library Management Software server machine. The request could not be processed.

Action:

Retain console logs and contact Computer Associates for assistance.

CADT883A — MOUNT SCRATCH USER DDNAME DSN=data-set-name MODE REELSIZE

Reason:

A CA-Dynam/T controlled data set is being requested for a mount, but the system could not locate a controlled scratch tape.

Action:


CADT883D — MOUNT SCRATCH USER DDNAME DSN=data-set-name MODE REELSIZE

Reason:


Action:


Reply with To

cuumm direct the system to use a specific drive, where mm is the optional density.


CANCEL cancel the request and notify the requestor.



Reply with To

RUN cuu|ALL

REW cuu|ALL

FSF cuu,nnn

BSF cuu,nnn

FSR cuu,nnn

BSR cuu,nnn

perform the indicated tape control to one or all drives (valid if the drive is unassigned).

STACK place the request on the request queue and notify the requestor.







CADT883I — MOUNT SCRATCH USER DDNAME DSN=data-set-name MODE REELSIZE

Reason:


Action:


CADT884D — VERIFY VOLUME NO=xxxxxx FOR UNLABELED PROCESSING

Reason:

This message is issued whenever an unlabeled dsn (TAPEOPT=NOLABEL) is being opened for output to verify that the volume is to be used for unlabeled processing.

Messages 2–317


Action:

EOB causes CA-Dynam/T to use this tape. CANCEL cancels the request and notifies the requestor. If the volume mounted is not the desired volume, dismount the volume, mount the correct volume and reply NEWTAP to verify the new volume.

CADT885D — MOUNT VOLUME xxxxxx DSN=data-set-name MODE DDNAME USER=userid *UNLABELED*

Reason:

The data set in the mount message is being opened for unlabeled input processing.

Note that AVR is not performed for unlabeled input tapes since no labels exist on the tape.

Action:

Mount the correct volume on an available tape drive and reply with one of the following:

Reply with To

cuumm direct the system to use a specific drive, where mm the optional density.



RUN cuu|ALL

REW cuu|ALL

FSF cuu,nnn

BSF cuu,nnn

FSR cuu,nnn

BSR cuu,nnn


ALTER direct the system to erase the label record being used and reopen the file in order to access the next sequentially submitted label record for this file.

RERUN direct the system to scratch Version 1 of this data set and reopen the file in order to access what was Version 2 as Version 1 (not valid for multi-file).



Reply with To


ACCEPT DSN=

'data-set-name'

(,VER=nnn

|,VOL=xxxxxx)

cause CA-Dynam/T to reissue the OPEN and search for the indicated data set, version or volume instead of the one called for (valid only if ACCEPT=YES has been generated; may be used to ACCEPT multi-file data sets).

CADT886D — VERIFY VOLUME NO=xxxxxx IS ON cuu FOR UNLABELED PROCESSING

Reason:

This message is issued whenever an unlabeled dsn (TAPEOPT=NOLABEL) is being opened for input to verify that the correct volume is mounted.

Action:

EOB causes CA-Dynam/T to use this tape.

CANCEL cancels the request and notifies the requestor.

If the volume mounted is not the desired volume, dismount the volume, mount the correct volume and reply NEWTAP to verify the new volume.

CADT887W — VOLUME xxxxxx NOT IN CATALOG

Reason:

The volume requested in the DYNMOUNT command is not in the CA-Dynam/T catalog.

Action:

Reissue the DYNMOUNT command specifying the correct volser.

CADT888A — MOUNT VOLUME xxxxxx USER=userid DSN=data-set-name FOR OUTPUT

Reason:

A DYNMOUNT command has been issued, but AVR was unable to locate the requested volume on an available drive.

Messages 2–319


Action:

Mount the requested tape on an available drive.

CADT888D — MOUNT VOLUME xxxxxx USER=userid DSN=data-set-name FOR OUTPUT

Reason:


Action:

Perform one of the following actions:

Reply with To

cuumm direct the system to a specific tape drive, where mm is the optional density.

STATUS obtain a list of all tape drives (on the console)

CANCEL cancel the request and notify the requestor

RUN cuu|ALL

REW cuu|ALL

FSF cuu,nnn

BSF cuu,nnn

FSR cuu,nnn

BSR cuu,nnn



CADT888I — MOUNT VOLUME xxxxxx USER=userid DSN=data-set-name FOR OUTPUT

Reason:


Action:




CADT889D — WRONG TAPE: VOL=xxxxxx HDR 1='xxxxxx'

Reason:

The volume mounted on the assigned drive (through user request or operator action) in response to a DYNMOUNT request is not the requested volume. The volume and HDR1 information shown is taken from the tape.

Action:

Mount the requested volume (as per the CADT888 MOUNT message) and reply EOB, or reply with one of the following:

Reply with To

cuumm direct the system to use a specific tape drive, where mm is the optional density.


ACCEPT force the system to accept this volume as input. (It should not be used with multi-file data sets; use use ACCEPT DSN=dsn, VER=nnn with message CADT888 instead).

RERUN direct the system to SCRATCH Version 1 of the indicated data set and reopen the file in order to access what was Version 2 as Version 1.

NEWTAP cause the open to be reissued (Dismount the volume if it is not the desired one, mount the desired volume and respond NEWTAP).

CADT890W — DSN data-set-name IS INVALID FOR DYNMOUNT REQUEST

Reason:

The data set name is either too long, contains invalid characters, or the tape was not created by DYNMOUNT.

Action:

Reissue the DYNMOUNT request with a valid data-set-name.

CADT891W — USER userid NOT AUTHORIZED TO ACCESS VOLUME xxxxxx

Reason:

User has tried to mount a volume which is not owned by the requesting user.

Messages 2–321


Action:

Reissue the DYNMOUNT command with the correct volser.

CADT892W — INCORRECT DATA SET NAME SPECIFIED FOR VOLUME xxxxxx

Reason:

The specified dsn is not contained on the specified volser.

Action:

Reissue the DYNMOUNT command specifying the correct volser or dsn.

CADT893D — ERROR ON TAPE I/O AT LOCATION xxxxxxxx: CCW=nn CSW=nn

CADT893D — REPLY: CANCEL/IGNORE/RETRY

Reason:

An error occurred at the specified location, while tape labels were being written.

Action:

Enter CANCEL to end the function, IGNORE to ignore the error and continue processing, or RETRY to start the function again.

CADT894E — DRIVE cuu BYPASSED: ATTWAIT LIMIT EXCEEDED

Reason:

The status of the specified drive could not be verified after the ATTACH was issued. The time limit specified by the ATTWAIT command was exceeded.

Action:

Increase the time limit of the ATTWAIT command.



CADT895 — DIAG ERR: MOD=module OFFSET=address RC=rc REPLY=CP reply

CADT895 — LOGIC ERR: MOD=module OFFSET=address

Reason:

An unexpected CP reply was received in response to an internally issued CP command.

Action:

Contact Computer Associates' support personnel.

CADT896W — STATUS IS QUESTIONABLE FOR VOLUME=xxxxxx

Reason:

The HDR1 dataset name on the volume does not match what CA-Dynam/T has recorded for a dataset name. This is most likely due to CA-1 having recently used the volume and status has not yet been reflected in the CA-Dynam/T catalog.

Action:

Mount a new volume.

CADT897I — LMS INTERFACE HAS BEEN DISCONNECTED - WILL BE RE-ESTABLISHED WHEN AVAILABLE

Reason:

The interface between CA-Dynam/T and the Memorex 5400 Automated Tape Library has become disabled due to an IUCV error or shutdown/abend of the LMS server.

Action:

None, the interface will be re-enabled when available.

CADT898I — UNABLE TO CONNECT TO LMS SERVER - WILL ESTABLISH CONNECTION WHEN POSSIBLE

Reason:

On initialization of CA-Dynam/T, a connection to the Library Management Software server machine could not be made. Connection will be established when available.

Messages 2–323


Action:

None.

CADT899E — IBM ________ REQUEST FAILED, RC=__ REASON __________

Reason:

An IBM 3494/3495 request failed with the specified return and reason codes. The request was not processed.

Action:

Determine the cause of the problem from the DFSMS Removable Media Services Users Guide and Reference, using the Return and Reason Code. Contact Computer Associates if necessary.

CADT900 — ENTER TDYNCONx COMMAND

Reason:

This message is issued by the conversion programs TDYNCONV and TDYNCON1.

Action:

For more information, contact Computer Associates.

CADT901 — CONTROL STATEMENT ERROR HAS OCCURRED *SEE PRINTER*

Reason:


Action:


CADT902 — CONTROL STATEMENT INVALID, STATEMENT BYPASSED

Reason:




Action:


CADT903 — INSUFFICIENT AREA IN DN OR SN FILE, STATEMENT BYPASSED

Reason:


Action:


CADT904 — NO LABEL INFORMATION FOR IJSYSDN AND/OR IJSYSSN FILES

Reason:


Action:


CADT905 — TDYNCONx BEGIN

Reason:


Action:


CADT906 — TDYNCONx END FUNCTION xxxxxxxxxxxxx

Reason:


Messages 2–325


Action:


CADT911E DSN MAY BE ADDED AFTER THE LAST DSN ONLY

Reason:

An attempt was made to add a data set in the middle of a tape that has multiple data sets. A new data set can be added only at the end of the last data set on the tape.

Action:

Specify the last data set on the tape and retry the command.

CADT912E — YOU MUST SPECIFY EITHER 'INPUT' OR 'OUTPUT'

Reason:

The field contains a string which is neither INPUT nor OUTPUT.

Action:

Specify either INPUT or OUTPUT for the field.

CADT913E — CMSDOS IS NOT ACTIVE

Reason:

CMSDOS was found to be inactive. CMSDOS must be active to use the field.

Action:

Either SET DOS ON, or do not use the field.

CADT914I — CREATING 'CADYNAMT USERPROF A'

Reason:

When editing the CA-Dynam/T user profile, no default profile was found on any accessed disks, so one is created.

Action:

None. Informational message only.



CADT915I — USER PROFILE SAVED AS 'CADYNAMT USERPROF fm'

Reason:

The user profile was successfully saved onto the specified disk.

Action:


CADT916I — CREATING 'CADYNAMT SYSPROF A'

Reason:

When editing the CA-Dynam/T system profile, no default profile was found on any accessed disks, so one is created.

Action:


CADT917I — SYSTEM PROFILE SAVED AS 'CADYNAMT SYSPROF fm'

Reason:

The system profile was successfully saved onto the specified disk.

Action:


CADT918E — COULD NOT WRITE PROFILE. RETURN CODE IS nnnnnnnn

Reason:

An attempt to save the user or system profile was not successful. The return code indicates the cause.

Action:

Consult the IBM System Product Editor Command and Macro Reference for an explanation of the return code.

Messages 2–327


CADT919E — FILE 'DYNT MODULE' NOT FOUND

Reason:

An attempt was made to access the DYNT transaction, but the module could not be located in the search path.

Action:

Make certain that the module is available for use and try again.

CADT920I — PRESS PF2 TO SCRATCH TAPE volser, OR PF3 TO CANCEL

Reason:

A scratch request has been made. This is a confirmation message.

Action:

Press PF2 to perform the scratch or PF3 to prevent the scratch.

CADT921I — PLEASE PRESS ENTER TO SCRATCH DSN data set name

Reason:


Action:

Press ENTER to perform the scratch or an active PF key to prevent the scratch.

CADT922E — ATTACH REQUIRES A USERID AND A VADDR

Reason:

An attempt was made to attach a tape drive to a userid without specifying the user or the user's virtual device address.

Action:

Enter the required information into the proper field and attempt the operation again.



CADT923E — FIELD MAY NOT BE MODIFIED

Reason:

An attempt was made to modify tape drive information for an active tape drive.

Action:

Modify the userid or vaddr fields ONLY if the device is free and you are attempting to attach it to a specific userid.

CADT924E — TAPE DEVICE cuu MUST BE OFFLINE FOR VARY ON

Reason:

An attempt was made to VARY ON a tape drive that is already online.

Action:

None. You may only VARY ON tape drives that are offline.

CADT925E — TAPE DEVICE cuu MUST BE FREE FOR VARY OFF

Reason:

An attempt was made to VARY OFF a tape drive that is either attached to a userid or already offline.

Action:

If the tape drive is attached to a userid, detach it, then VARY OFF. Otherwise, do nothing; you may only VARY OFF tape drives that are online.

CADT926E — NON-QUEUED REQUEST MAY NOT BE UNSTACKED

Reason:

An attempt was made to unstack an item that is not queued.

Action:

None. You may only unstack queued items.

Messages 2–329


CADT927I — NO RECORDS FOUND

Reason:

No records were found.

Action:

None. This is informational only.

CADT928I — DSN 'data set name' DELETED.

Reason:

The indicated data set name has been successfully deleted.

Action:


CADT929I — TAPE 'tape name' DELETED.

Reason:

The indicated tape has been successfully deleted.

Action:


CADT930I — REQUEST WAITING ON SERVICE MACHINE.

Reason:

The request is waiting in the service machine for processing.

Action:




CADT931E — INVALID REQUEST FORMAT RECEIVED - USER=userid

Reason:

The user command entered is not compatible with the current release of CA-Dynam/T.

Action:

Make sure that the disk containing the user commands for the current release is properly accessed.

CADT932I — PRESS PF2 TO INITIATE YOUR REQUEST

Reason:

This message is issued in order to confirm your request.

Action:

Press PF2 to begin processing, or PF3 to cancel.

CADT933I — REQUEST SENT TO SERVICE MACHINE xxxxxxxx

Reason:

The request has been sent to the service machine indicated.

Action:


CADT934I — FILE BEING CREATED, PRESS PF2 TO CONFIRM OR PF3 TO CANCEL

Reason:

The indicated file will be created when you press PF2.

Action:

Press PF2 to create the file, or PF3 to cancel the request.

Messages 2–331


CADT935I — AVR - NO TAPES IN DTPOOL

Reason:

There are no tapes available in the DTPOOL upon which to perform Automatic Volume Recognition.

Action:

Check the DTPOOL.

CADT936I — PLEASE PRESS ENTER TO SCRATCH TAPE VOLSER

Reason:


Action:

Press ENTER to perform the scratch or an active PF key to prevent the scratch.

CADT936I — DYNLINK EXEC HAS BEEN SAVED ON THE xxx DISK AND YCLINK ON THE xxx.

Reason:

The DYNLINK and YCLINK EXECs have been saved properly on the disks indicated.

Action:


CADT937E — ERROR READING THE YCLINK EXEC FROM THE xxx DISK. RC=nnn

Reason:

The return code is from the CMS READ command.

Action:

Consult the appropriate CMS documentation for return code description.



CADT938E — ERROR LINKING OR ACCESSING THE xxx DISK OF xxxxxxxx. RC=nnn.

Reason:

The return code is from CP LINK or CMS ACCESS command.

Action:

Consult the appropriate CP or CMS documentation for return code description.

CADT939E — ERROR COPYING THE YCLINK EXEC TO THE xxx DISK. RC=nnn.

Reason:

The return code is from the CMS COPYFILE command.

Action:

Consult the appropriate CMS documentation for return code description.

CADT941I — PLEASE EXIT PANEL AND VERIFY PREVIOUS INSTALLATION STEPS.

Reason:

The current installation step has completed.

Action:

Press the PF3 or PF4 key to exit this screen.

CADT942I — PRESS PF3 TO EXIT SCREEN

Reason:

This step has completed.

Action:

Press the PF3 key to return to the previous screen.

Messages 2–333


CADT943I — PLEASE WAIT . . .

Reason:

The modules are being generated.

Action:


CADT944E — ERROR SAVING FILE 'filename filetype fm'. RC='nnnnnn'.

Reason:

The file indicated cannot be saved.

Action:

Check the return code and perform the appropriate action.

CADT945I — filename filetype fm SAVED SUCCESSFULLY.

Reason:

The file has been saved on the indicated disk.

Action:


CADT946I — PLEASE MAKE ANY CHANGES YOU DESIRE AND PRESS PF2 TO SAVE THEM.

Reason:

The options on this screen may be changed.

Action:

Edit the screen as you wish, then press the PF2 key to save the changes.



CADT947I — ACTION CONFIRMED

Reason:

The function has been correctly performed and the task is flagged as COMPLETE.

Action:


CADT948E — xxxxxxxx xxxxxxxx NOT FOUND. PLEASE CORRECT BEFORE CONTINUING.

Reason:

The indicated file cannot be found.

Action:

Check the file name, correct and retry.

CADT949I — PLEASE CORRECT THE PROBLEM BEFORE CONTINUING.

Reason:

A problem has been encountered.

Action:

Correct the problem and continue.

CADT950I — DIRECTORY ENTRY FOR SERVICE MACHINE BUILT. FILEID=filename filetype fm.

Reason:

A CMS file which contains the directory entry for the CA-Dynam/T service machine has been successfully created.

Action:


Messages 2–335


CADT951I — *** MODULE GENERATION COMPLETE ***

Reason:

The module has been successfully generated.

Action:


CADT952I — *** PROFILE GENERATION COMPLETE ***

Reason:

The profile has been successfully generated.

Action:


CADT953I — *** SYSTEM PROFILE INFORMATION IS NOT AVAILABLE ***

Reason:

An attempt was made to generate the CA-Dynam/T system profile, but the required information, from the prerequisite tasks, could not be found.

Action:

Execute (or reexecute) the previous system profile tasks.

CADT954I — *** ERROR SAVING SYSTEM PROFILE. RC = 'nnnnnn' ***

Reason:

The system profile could not be saved.

Action:




CADT955I — *** ERROR - 'filename filetype fm' NOT FOUND ***

Reason:

The indicated file could not be found on the indicated disk.

Action:

Make sure the correct minidisk is accessed and continue.

CADT956I — *** CONTROL TABLE GENERATION COMPLETE ***

Reason:

The control table has been successfully generated.

Action:

No action required.

CADT957I — *** ERROR SAVING PRODUCT CONTROL TABLE. RC = 'nnnnnn' ***

Reason:

The product control table could not be generated.

Action:


CADT958I — PLEASE PRESS ENTER TO START GENERATION OF DYNAM/T MODULES, OR CANCEL

Reason:

You must press the ENTER key to begin generating the CA-Dynam/T modules.

Action:

Press the ENTER key.

Messages 2–337


CADT959I — DYNAM/T MODULES BEING GENERATED ON MINIDISK 'nnn'.

Reason:

The CA-Dynam/T modules are being generated.

Action:


CADT960E — ERROR SAVING DIRECTORY FILE 'filename filetype fm'. RC='nnnnnn'.

Reason:

The directory file for the CA-Dynam/T service machine could not be saved.

Action:

Check that the appropriate CAIMAINT minidisk is accessed in read/write mode.

CADT961I — DIRECTORY ENTRY SAVED AS 'filename filetype fm'.

Reason:

The directory has been save under the filename indicated.

Action:


CADT962E — xxxxxxxxxxx DSN NOT AVAILABLE. PLEASE VERIFY DYNLINK EXEC.

Reason:

The indicated data set is not available.

Action:

Check the DYNLINK EXEC, correct and resubmit.



CADT963I — DYNAM/T SYSTEM PROFILE BEING GENERATED ON MINIDISK 'nnn'.

Reason:

The CA-Dynam/T system profile is being generated on the indicated minidisk.

Action:


CADT964I — TASK MANAGER SYSTEM PROFILE SUCCESSFULLY BUILT.

Reason:

The system profile for Task Manager has been successfully saved.

Action:


CADT965I — TASK MANAGER CP COMMAND FILE SUCCESSFULLY BUILT.

Reason:

The CP command file for Task Manager has been successfully saved.

Action:


CADT966I — TASK MANAGER CMS COMMAND FILE SUCCESSFULLY BUILT.

Reason:

The CMS command file for Task Manager has been successfully saved.

Action:


Messages 2–339


CADT967I — PLEASE PRESS THE PF2/14 KEY TO SEND FILES TO DYNAM/T SERVICE MACHINE.

Reason:

You must press the PF2 key to send the required files to the CA-Dynam/T service machine.

Action:

Press the PF2 key to continue.

CADT968I — FILES SENT TO USER ID 'xxxxxxxx'

Reason:

The required service machine startup files have been successfully sent to the indicated userid.

Action:


CADT969E — ERROR SENDING FILE 'filename filetype fm', RC=nnnn.

Reason:

The specified file, which is required for the initialization of the CA-Dynam/T service machine, could not be sent to the service machine's virtual reader.

Action:

Make sure the files are available and the CP directory entry for the service machine has been processed.

CADT970E — xxxxxxxxxxx CUU NOT AVAILABLE. PLEASE VERIFY DYNLINK EXEC.

Reason:

A CP LINK command could not be executed for the specified cuu.

Action:

Check the DYNLINK EXEC.



CADT971I — xxxxxxxxxxxxxxxxxxxxxx INITIALIZATION COMPLETE.

Reason:

The initialization for the indicated function has completed.

Action:


CADT972E — UNABLE TO LINK TO 'xxxxxxxx'. RETURN CODE IS 'nnnnnn'.

Reason:

A link could not be established with the minidisk indicated.

Action:

Check the return code, and the DYNLINK EXEC.

CADT973W — UNABLE TO VERIFY LINK TO 'xxxxxxxx'.

Reason:

The link could not be verified with the minidisk indicated.

Action:

Check the DYNLINK EXEC.

CADT974E — xxxxxxxx IS NOT A VALID LINK. RC = nnnn.

Reason:

The link established for the minidisk indicated is not valid.

Action:

Check the return code and the DYNLINK EXEC.

Messages 2–341


CADT975E — LINK COMMAND FOR CUU 'nnn' FOR DDNAME 'xxxxxxxx' IS MISSING.

Reason:

The CP LINK command is missing for the specified cuu and ddname.

Action:

Check the DYNLINK EXEC and correct the error.

CADT976E — ACCESS COMMAND FOR FILEMODE 'xx' FOR DDNAME 'xxxxxxxx' IS MISSING.

Reason:

The CP ACCESS command has not been specified for the noted filemode and ddname.

Action:

Check the DYNLINK EXEC and correct the error.

CADT977E — FILDEF FOR DDNAME 'xxxxxxxx' MUST BE SPECIFIED.

Reason:

A FILEDEF statement cannot be found for the DDNAME indicated, and one is required.

Action:

Specify a FILEDEF statement for the DDNAME.

CADT978E — xxxxxxxxx UTILITY FAILED. RC=nnnn.

Reason:

The indicated utility program has encountered an error and failed.

Action:




CADT979I — SYSTEM PROFILE HAS BEEN UPDATED. MAKE SURE TO RE-GENERATE THE SYSPROF.

Reason:

The changes you have made to the system profile have been properly saved. Be sure to re-generate the CA-Dynam/T system profile before continuing.

Action:


CADT980I — PRODUCT CONTROL TABLE CHANGES HAVE BEEN SAVED. PRESS PF3 TO EXIT.

Reason:

The changes you have made to the product control table have been properly saved.

Action:


CADT981E — INVALID xxxxxxxx COMMAND.

Reason:

The command specified is not a valid CA-Dynam/T command.

Action:

Consult the CA-Dynam/T User Guide and the CA-Dynam/T Operator Guide for valid commands and syntax.

CADT982I — PLEASE PRESS ENTER TO GENERATE THE PRODUCT CONTROL TABLE.

Reason:

You must press the ENTER key to begin the product control table generation.

Action:

Press the ENTER key.

Messages 2–343


CADT983E — xxxxxxxxxxxxxxxxxxxx MAY NOT HAVE BEEN PROPERLY FORMATTED.

Reason:

The minidisk on which the indicated data set resides has not been formatted correctly.

Action:

Check the minidisk and reformat, if necessary.

CADT984E — DUPLICATE TAPE DRIVE ADDRESS.

Reason:

You have specified the same tape drive address twice. The cursor will appear on the duplicate address.

Action:

Check the values and correct the problem.

CADT985I — PRODUCT CONTROL TABLE BEING GENERATED ON MINIDISK 'nnn'.

Reason:

The product control table is being generated on the indicated minidisk.

Action:


CADT986E — INVALID VOLSER RANGE.

Reason:

The volume serial number range specified is not valid.

Action:

Enter a new volser and try again.



CADT987E — DUPLICATE xxxxxxx COMMAND 'xxxxxxxx'

Reason:

The command indicated has been specified twice, but it need only be entered once.

Action:

Check the command, correct and retry.

CADT989W — AVR LOCKING (AVRLCK) FORCES MULTI-CPU ENVIRONMENT (MULTCPU=YES).

Reason:

You specified the AVRLCK option on the product control table. This message indicates that the MULTCPU option will be changed to YES.

Action:


CADT996I — --------- user text --------

Reason:

An input data set is opened and the user has defined an open input message in the CA-Dynam Catalog.

Action:

None.

CADT997I — --------- user text --------

Reason:

An output data set is opened and the user has defined an open output message in the CA-Dynam Catalog.

Action:

None.

Messages 2–345

CADU Prefixed Messages

CADT998I — --------- user text --------

Reason:

An input data set is closed and the user has defined a close input message in the CA-Dynam Catalog.

Action:

None.

CADT999I — --------- user text --------

Reason:

An output data set is closed and the user has defined a close output message in the CA-Dynam Catalog.

Action:

None.


CADU001E — DYNPRINT UNEXPECTED END OF INPUT ENCOUNTERED

Reason:

The input to the DYNPRINT command processor ended but the last command was not complete. This usually results from ending the command stream with a keyword and no accompanying value.

Action:


CADU002E — DYNPRINT EXPECTING A VALUE - ENCOUNTERED: xxxxxxxx

Reason:

The DYNPRINT command processor has just processed a keyword. This message usually results from putting two keywords together without an intervening value.



Action:


CADU003E — DYNPRINT UNEXPECTED VALUE: xxxxxxxx

Reason:

Whatever was input to the DYNPRINT command processor where the value was expected did not conform to the requirements. This can happen as a result of using special characters in an unquoted value.

Action:


CADU004E — DYNPRINT EXPECTING COMMAND VALUE - ENCOUNTERED: xxxxxxxx

Reason:

An invalid or unrecognized value in the input to the DYNPRINT command processor followed a command keyword other than ACCESS. Most often this is caused by specifying a report of the wrong category for the data source currently accessed.

Action:


CADU005E — DYNPRINT EXTRANEOUS KEYWORD: xxxxxxxx

Reason:

The DYNPRINT command processor has encountered a keyword which either is not supported for the report specified, or has already been given in the current command.

Action:


Messages 2–347


CADU006E — DYNPRINT VALUE TOO LONG: xxxxxxxx

Reason:

The value in the DYNPRINT command processor input is longer than the permitted maximum length for the current keyword.

Action:


CADU007E — DYNPRINT SYNTAX ERRORS DETECTED - RUN TERMINATED

Reason:

This is issued by the DYNPRINT command processor at the end of the input if any error conditions have been detected. The run is abended.

Action:


CADU008E — DYNPRINT EXPECTING START OF COMMAND - ENCOUNTERED: xxxxxxxx

Reason:

The first word found in the DYNPRINT command processor input, or found after a successfully interpreted ACCESS command, must be a keyword that initiates a new command. Any other word will cause this message to be issued.

Action:


CADU009I — DYNPRINT DETECTED NO SYNTAX ERRORS

Reason:

This is issued by the DYNPRINT command processor at the end of input if no errors have been found. It indicates that execution is proceeding.

Action:

None.



CADU010E — DYNPRINT EXPECTING ACCESS VALUE - ENCOUNTERED: xxxxxxxx

Reason:

The value in the DYNPRINT command processor input following the ACCESS keyword is not the name of a data source supported by DYNPRINT.

Action:


CADU011E — DYNPRINT EXPECTING VALID SELECT OPTION - ENCOUNTERED: xxxxxxxx

Reason:

One of the values following the SELECT keyword in the DYNPRINT command processor input is not valid for the report currently requested. See the individual report descriptions for the accepted SELECT options.

Action:


CADU012E — DYNPRINT EXPECTING NUMERIC VALUE - ENCOUNTERED: xxxxxxxx

Reason:

A non-numeric value was encountered in the DYNPRINT command processor input as the value for a keyword requiring a numeric value.

Action:


CADU013E — DYNPRINT ENCOUNTERED KEYWORDS NOT ALLOWED FOR THIS REPORT CLASS -

Reason:

The complete command has been processed by the DYNPRINT command processor, but it contained a keyword(s) invalid for the current report class. This message is always accompanied by an informational message listing the keywords not allowed for the current report class.

Action:


Messages 2–349


CADU014E — DYNPRINT ENCOUNTERED MUTUALLY EXCLUSIVE KEYWORDS: VER/GEN/GDG

Reason:

Only one of these three keywords is allowed in any one command.

Action:


CADU015I — VOL, FSQ, AND/OR MAXFILES

Reason:

This is issued with message CADU013E for DSN-based Catalog reports. These keywords are never allowed for this report class.

Action:


CADU016I — DSN, VSQ, VER, GEN, GDG, MAXVERS, MAXVOLS, AND/OR DVC

Reason:

This is issued with message CADU013E for volser-based Catalog reports. These keywords are never allowed for this report class.

Action:


CADU017I — GENERIC DSN (DSN WITH *)

Reason:

This is issued with message CADU013E for volser-based reports, whether using the Catalog or the VTOCs as a data source. Generic DSN access is not allowed for either of these report classes.

Action:




CADU018I — DSN, FSQ, VSQ, VER, GDG, GEN, PSW, MAXFILES, MAXVERS, MAXVOLS, DVC, CATNM, AND/OR CBUFN

Reason:

This is issued with message CADU013E for VTOC-based reports. None of these keywords are allowed for this report class.

Action:


CADU019E — DYNPRINT MORE THAN ONE SELECT OPTION WITH MAXLINES NOT SUPPORTED

Reason:

The DYNPRINT command processor may issue this message if you use MAXLINES with more than one SELECT option.

Action:


CADU020E — DYNPRINT EXPECTING VALID DVC VALUE - ENCOUNTERED: xxxxxxxx

Reason:

Whatever immediately followed the keyword DVC in the DYNPRINT command processor input stream is not one of the allowed values for this keyword. Valid values are listed in the general DYNPRINT description.

Action:


CADU021E — DYNPRINT EXPECTING VALID BANNER VALUE - ENCOUNTERED: xxxxxxxx

Reason:

Whatever immediately followed the keyword BANNER in the DYNPRINT command processor input stream is not one of the allowed values for this keyword. Valid values are listed in the general DYNPRINT description.

Action:


Messages 2–351


CADU022E — DYNPRINT EXPECTING VALID EDITEST VALUE - ENCOUNTERED: xxxxxxxx

Reason:

Whatever immediately followed the keyword EDITEST in the DYNPRINT command processor input stream is not one of the allowed values for this keyword. Valid values are listed in the general DYNPRINT description.

Action:


CADU023E — DYNPRINT EXPECTING VALID EROPT VALUE - ENCOUNTERED: xxxxxxxx

Reason:

Whatever immediately followed the keyword EROPT in the DYNPRINT command processor input stream is not one of the allowed values for this keyword. The valid values are listed in the general DYNPRINT description.

Action:


CADU050R — ENTER DYNPRINT INPUT:

Reason:

This message is issued by the DYNPRINT command processor when DYNPRINT is being run from an operator console and is expecting further input control statements.

Action:

Enter another statement or a continuation of the current statement. If your command stream is complete, enter EOB to close input processing and initiate report processing.



CADU060E — DYNPRINT NORMAL TERMINATION

Reason:

Issued by the DYNPRINT runtime manager DYNPLOAD at the end of a run in which no errors have occurred.

Action:

None.

CADU061E — ERROR OCCURRED LOADING DYNPLOAD - RETURN CODE xxxxxxxx ERROR CODE xxxxxxxx

Reason:

Issued by the DYNPRINT root phase at start of processing if an error occurs loading the runtime manager DYNPLOAD.

Action:

Check that DYNPLOAD is available in a library in the search chain. If necessary, contact Computer Associates for assistance.

CADU062E — SYSTEM ADAPTER FUNCTION xxxxxxxx

Reason:

Issued by the DYNPRINT runtime manager DYNPLOAD after a critical error involving the System Adapter, as part of the diagnostic procedure. Indicates which Adapter function had been invoked.

Action:

Try to diagnose and fix the problem. If necessary, contact Computer Associates for assistance.

CADU063E — UTILITY ADAPTER FUNCTION xxxxxxxx

Reason:

Issued by the DYNPRINT runtime manager DYNPLOAD after a critical error involving the Utility Adapter, as part of the diagnostic procedure. Indicates which Adapter function had been invoked.

Messages 2–353


Action:

Try to diagnose and fix the problem. If necessary, contact Computer Associates for assistance.

CADU064E — CSECT: xxxxxxxx OFFSET: xxxxxxxx

Reason:

Issued by the DYNPRINT runtime manager DYNPLOAD after a critical error, as part of the diagnostic procedure. Localizes the point where the error was detected.

Action:

Report this information to Computer Associates when calling in for assistance.

CADU065E — ABNORMAL TERMINATION - RETURN CODE = xxxx ERROR CODE = xxxx

Reason:

Issued by the DYNPRINT runtime manager DYNPLOAD after a critical error, as part of the diagnostic procedure. Documents the return and error codes encountered.

Action:

Use this information in any attempt to diagnose and fix the problem. The return and error codes for many functions are documented in the CA-Dynam manual. Report this information to Computer Associates when calling in for assistance.

CADU101E — S.A. DYNPARM ERROR RC xxxxxxxx DYNREAD RC xxxxxxxx

Reason:

Issued by CA-EARL report phases if the installation options phase generated by the DYNAM option record cannot be located. Perhaps CA-Dynam has not been started up.

Action:

Try to diagnose and fix the problem. If necessary contact Computer Associates for assistance.



CADU102E — DYNACC CATALOG POINTER MISSING RC xxxx EC xxxx EROFFS xxxxxx

Reason:

Issued by CA-EARL report phases after getting return code 14 back from DYNACC. Further data access for the current major item (file-id or volser) is aborted, but processing for the report continues. The interrupted pointer chains result from an abend occurring while a Catalog update is in progress. This is usually not a cause for concern as the version being cataloged is probably invalid as a result of the abend.

Action:

To determine which files are affected, rerun the report using the same DYNPRINT command, but adding the option EROPT=D. This provides detailed information in the form of snap dumps. Then you can:

■ correct a Catalog entry, using the DYNCAT commands ALTER and/or ADD

■ delete a Catalog entry, using the DYNCAT DELETE command

■ delete all erroneous Catalog entries by running DYNCAT BACKUP and RESTORE REORG.

If necessary contact Computer Associates for assistance. Be sure you have the snap dumps produced by the EROPT=D option available when you call.

CADU107E — S.A. DATEPROC ERROR FN nn RC nnnnnnnn

Reason:

Issued by CA-EARL report phases if an invocation of the System Adapter Date Processor function was unsuccessful. In the case of a custom report, reread the information in the PLIST copybook to be sure the reported function code is valid.

Action:


CADU109E — S.A. DDPARMS ERROR RC nnnnnnnn

Reason:

Issued by CA-EARL report phases if the CA-Dynam/D installation options phase created by the DYNAMD option record could not be found. Perhaps CA-Dynam/D is not installed.

Messages 2–355


Action:


CADU110E — S.A. DASDCALC ERROR RC nnnnnnnn SFRC nnnnnnnn

Reason:

Issued by CA-EARL report phases if an invocation of the System Adapter DASD Calculations function returned a nonzero code. If the problem is with a subfunction invoked by DASDCALC, the code in SFRC is what the subfunction returned.

Action:


CADU111E — S.A. OBTAIN ERROR RC nnnnnnnn

Reason:

Issued by CA-EARL report phases if an invocation of the System Adapter OBTAIN function returned a nonzero code.

Action:


CADU201E — DYNINFO DYNRQLEN BELOW MINIMUM

Reason:

A DYNPRINT CA-EARL report phase has invoked DYNACC, the Catalog access module, using a DYNINFO PLIST with too small a length in the field DYNRQLEN. The minimum length is documented in the portion of the manual relating to DYNACC.

Action:

Correct the length in the CA-EARL source. If a standard DYNPRINT report was being run, contact Computer Associates for further assistance.



CADU202E — DYNACC/DYNINFO VERSION MISMATCH

Reason:

A DYNPRINT CA-EARL report phase has invoked DYNACC, the Catalog access module, using a DYNINFO PLIST with the wrong version stamp for the DYNACC Service Module that was initially loaded. Can normally not occur unless the version stamp field in DYNINFO (DYNRQID) has been altered by the calling program.

Action:

Check the calling CA-EARL source for possible errors. If a standard DYNPRINT report was being run, contact Computer Associates for further assistance.

CADU203E — DYNINFO SENTINEL NOT FOUND

Reason:

A DYNPRINT CA-EARL report phase has invoked DYNACC, the Catalog access module, using a DYNINFO PLIST in which the first eight bytes are not equal to the string "DYNINFO". Can normally not occur unless this field in DYNINFO (DYNSTAMP) has been altered by the calling program.

Action:

Check the calling CA-EARL source for possible errors. Take note of the instructions in the CA-EARL version of DYNINFO. If a standard DYNPRINT report was being run, contact Computer Associates for further assistance.

CADU204E — PASSWORD IS INCORRECT

Reason:

A DYNPRINT CA-EARL report phase has invoked DYNACC, the Catalog access module, requesting information about a password-protected file, and supplying the wrong password for the file.

Action:

Correct the password in the invoking DYNPRINT command or in the EARL source if not running under DYNPRINT.

Messages 2–357


CADU205E — PHYSICAL I/O ERROR DURING CAT READ

Reason:

A DYNPRINT CA-EARL report phase has invoked DYNACC, the Catalog access module, and a physical I/O error reading the Catalog has occurred as a result.

Action:

Refer to DYNACC documentation to diagnose the problem. If necessary, contact Computer Associates for further assistance.

CADU206E — LOGICAL I/O ERROR DURING CAT READ

Reason:

A DYNPRINT CA-EARL report phase has invoked DYNACC, the Catalog access module, and a logical I/O error reading the Catalog has occurred as a result.

Action:


CADU207E — CATALOG IS INACCESSIBLE

Reason:

A DYNPRINT CA-EARL report phase has invoked DYNACC, the Catalog access module, and DYNACC is unable to access the Catalog. This is usually the result of a JCL problem. The DTFname used on the Catalog DLBL (and in the invoking DYNINFO PLIST) must not have been used to refer to a different catalog file any time since the last system IPL.

Action:


CADU208E — GETVIS DENIAL FOR BUFFERS

Reason:

A DYNPRINT CA-EARL report phase has invoked DYNACC, the Catalog access module, and DYNACC has encountered a short-on-storage condition when allocating buffers at Catalog OPEN time.



Action:

Refer to DYNACC documentation to diagnose the problem. Try running in a partition with a larger GETVIS segment, or reducing the number of buffers requested by using the CBUFN parameter. If necessary, contact Computer Associates for further assistance.

CADU209E — CATALOG SAVER MEMORY MGMT ERROR

Reason:

A DYNPRINT CA-EARL report phase has invoked DYNACC, the Catalog access module, and a DYNACC invocation of Catalog Management has encountered an error invoking the System Adapter SAVER function.

Action:


CADU210E — DYNACC LOGICAL ERROR

Reason:

A DYNPRINT CA-EARL report phase has invoked DYNACC, the Catalog access module, and an internal logic error has occurred in DYNACC.

Action:


CADU211E — GETVIS DENIAL FOR DYNAMIC STORAGE

Reason:

A DYNPRINT CA-EARL report phase has invoked DYNACC, the Catalog access module, and DYNACC has encountered a short-on-storage condition when allocating its dynamic working storage area.

Action:

Refer to DYNACC documentation to diagnose the problem. Try running in a partition with a larger GETVIS segment. If necessary, contact Computer Associates for further assistance.

Messages 2–359


CADU212E — UNABLE TO LOCATE CACUDAXO PHASE

Reason:

A DYNPRINT CA-EARL report phase has invoked DYNACC, the Catalog access module, and the DYNACC relocatable module was unable to load the DYNACC Service Module specified in the DYNINFO PLIST. This message is preceded by CADU220E, which names the specific service module sought.

Action:

Refer to documentation of message CADU220E to diagnose the problem. If issued by a standard DYNPRINT report function, contact Computer Associates for further assistance.

CADU213E — SAVE AREA FAILURE

Reason:

A DYNPRINT CA-EARL report phase has invoked DYNACC, the Catalog access module, and at some level of internal subroutine invocation DYNACC ran out of save areas.

Action:

Contact Computer Associates for further assistance.

CADU214E — SYNTAX ERROR IN CALL TO DYNACC

Reason:

A DYNPRINT CA-EARL report phase has invoked DYNACC, the Catalog access module, and a syntax error was detected in the passed DYNINFO PLIST. Most often the result of an invalid value in a packed field in the DYNREQST portion of DYNINFO. These fields must contain either a valid packed number or blanks. Can also result from passing blanks in DYNRQLEN, or from an unrecognized request code in DYNRQCD.

Action:

Refer to DYNACC documentation to diagnose the problem. Check the calling CA-EARL source for possible errors. If issued by a standard DYNPRINT report function, contact Computer Associates for further assistance.



CADU220E — UNABLE TO LOCATE DYNACC SERVICE MODULE xxxxxxxx R/C= xxxxxxxx

Reason:

A DYNPRINT CA-EARL report phase has invoked DYNACC, the Catalog access module, and the DYNACC relocatable module was unable to load the DYNACC Service Module specified in the DYNINFO PLIST.

Action:

Refer to DYNACC documentation to diagnose the problem. Be sure the phase name in the message corresponds to the service module you expect to be invoked. Check that the named phase is accessible in the active LIBDEF search chain. If issued by a standard DYNPRINT report function, contact Computer Associates for further assistance.


Reason:

A DYNPRINT CA-EARL report phase has invoked a System Adapter function through the DYNREAD interface, and there weren't enough save areas for all levels of internal subroutine calling invoked by the function.

Action:


CADU302E — UNKNOWN ADAPTER FUNCTION

Reason:

A DYNPRINT CA-EARL report phase has invoked a System Adapter function using the DYNREAD interface, and the Adapter nucleus didn't recognize the requested function, even though it was accepted by DYNREAD dispatching.

Action:

Check that the CA-Dynam and CA-CIS libraries are available and correctly defined and accessed through job control statements. If the problem persists, contact Computer Associates for assistance.

Messages 2–361


CADU303E — ADAPTER FUNCTION NOT INSTALLED

Reason:

A DYNPRINT CA-EARL report phase has invoked a System Adapter function through the DYNREAD interface, and the Adapter nucleus found that the function is not available.

Action:

Check that the CA-Dynam and CA-CIS libraries are available and correctly defined and accessed through job control statements. If the problem persists, contact Computer Associates for assistance.

CADU304E — ADAPTER STORAGE MANAGEMENT FAILURE

Reason:

A DYNPRINT CA-EARL report phase has invoked a System Adapter function through the DYNREAD interface, and the requested function has encountered a short-on-storage condition when trying to allocate a dynamic work area.

Action:

Try running in a partition with a larger GETVIS segment. If the problem persists, contact Computer Associates for assistance.

CADU305E — MAIN ADAPTER NOT AVAILABLE

Reason:

A DYNPRINT CA-EARL report phase has invoked a System Adapter function through the DYNREAD interface, and a failure has occurred locating the Main System Adapter.

Action:

Check that the CA-Dynam and CA-CIS libraries are available and correctly defined and accessed through job control statements. Be sure that CA-Dynam has been started up correctly. If the problem persists, contact Computer Associates for assistance.



CADU306E — ADAPTER SYSTEM LOADLIST NOT AVAILABLE

Reason:

A DYNPRINT CA-EARL report phase has invoked a System Adapter function through the DYNREAD interface, and the Main Adapter nucleus was unable to locate its Load List.

Action:

Check that the CA-Dynam and CA-CIS libraries are available and correctly defined and accessed through job control statements. Be sure that DYNAM has been started up correctly. If the problem persists, contact Computer Associates for assistance.

CADU401E — SRAM GOT UNKNOWN RETURN CODE

Reason:

A DYNPRINT CA-EARL report phase has invoked the DYNREAD SRAM (Sort Reentrant Access Method) interface for input data retrieval, and SRAM has returned a code unknown to DYNREAD.

Action:



Reason:

A DYNPRINT CA-EARL report phase has invoked the DYNREAD SRAM (Sort Reentrant Access Method) interface for input data retrieval, and SRAM has encountered a save area failure.

Action:


CADU403E — ADAPTER STORAGE MANAGEMENT FAILURE

Reason:

A DYNPRINT CA-EARL report phase has invoked the DYNREAD SRAM (Sort Reentrant Access Method) interface for input data retrieval, and SRAM has encountered a short-on-storage condition when trying to allocate buffers or dynamic working storage.

Messages 2–363


Action:

Try running in a partition with a larger GETVIS segment. If the problem persists, contact Computer Associates for assistance.

CADU404E — SRAM ALREADY INITIALIZED

Reason:

A DYNPRINT CA-EARL report phase has invoked the DYNREAD SRAM (Sort Reentrant Access Method) interface for input data retrieval, and when DYNREAD attempted to initialize SRAM the request was rejected.

Action:


CADU405E — SRAM NOT INITIALIZED

Reason:

A DYNPRINT CA-EARL report phase has invoked the DYNREAD SRAM (Sort Reentrant Access Method) interface for input data retrieval, and SRAM returned a code indicating that it had not ever been initialized.

Action:


CADU501E — VTOCINFO PLIST NOT FOUND OR INVALID

Reason:

A DYNPRINT CA-EARL report phase has invoked VTOCAC, the VTOC access module, using no VTOCINFO PLIST or an invalid one.

Action:

Refer to VTOCAC documentation, including the instructions in the EARL version of VTOCINFO, to diagnose the problem. Check the CA-EARL report source code for possible errors. If issued by a standard DYNPRINT report function, contact Computer Associates for further assistance.



CADU502E — INTERNAL LOGIC ERROR

Reason:

A DYNPRINT CA-EARL report phase has invoked VTOCAC, the VTOC access module, and an internal logic error has occurred in VTOCAC.

Action:


CADU503E — INVALID VTOC RECORD FORMAT TYPE

Reason:

A DYNPRINT CA-EARL report phase has invoked VTOCAC, the VTOC access module, and either 1) the record type requested in the VTOCAC PLIST was out of the acceptable range or 2) a record was read from the VTOC with an out-of-range record type. VTOCAC expects all VTOC records to have a type from 1 through 6.

Action:

Check the CA-EARL report source code for possible errors. Dump the VTOC and check for possible corruption there. If the problem persists, especially if the message is issued by a standard DYNPRINT report function, contact Computer Associates for further assistance.

CADU504E — INVALID VTOC RECORD LINK ADDRESS

Reason:

A DYNPRINT CA-EARL report phase has invoked VTOCAC, the VTOC access module, and VTOCAC has encountered a link pointer to an invalid location or one outside the VTOC extent.

Action:

Dump the VTOC and check for possible corruption there. If the problem persists, contact Computer Associates for further assistance.

Messages 2–365


CADU505E — INSUFFICIENT SAVE AREAS

Reason:

A DYNPRINT CA-EARL report phase has invoked VTOCAC, the VTOC access module, and there weren't enough save areas available for all levels of invoked internal subroutines.

Action:


CADU506E — UNEXPECTED SYSTEM ADAPTER ERROR

Reason:

A DYNPRINT CA-EARL report phase has invoked VTOCAC, the VTOC access module, which in turn has invoked a System Adapter function; the latter has encountered an unexpected error in a basic internal function (codes in the range 1-20).

Action:


CADU507E — UNEXPECTED FUNCTION ERROR

Reason:

A DYNPRINT CA-EARL report phase has invoked VTOCAC, the VTOC access module, which in turn has invoked a System Adapter function; the latter has encountered an unexpected error in a subsidiary function (codes higher than 20).

Action:


CADU508E — UNEXPECTED DASDAVR ERROR

Reason:

A DYNPRINT CA-EARL report phase has invoked VTOCAC, the VTOC access module, which in turn has invoked the System Adapter DASDAVR function; the latter has returned an unexpected code.



Action:


CADU509E — UNEXPECTED DYNLUB ERROR

Reason:

A DYNPRINT CA-EARL report phase has invoked VTOCAC, the VTOC access module, which in turn has invoked the System Adapter DYNLUB function; the latter has returned an unexpected code.

Action:


CADU510E — UNEXPECTED VTOC RETURN CODE

Reason:

A DYNPRINT CA-EARL report phase has invoked VTOCAC, the VTOC access module, which in turn has invoked the System Adapter IXVTOC function; the latter has returned an unexpected code.

Action:


CADU900E — EARL PROGRAM CALLED ABORT

Reason:

DYNREAD was called by an CA-EARL report phase with a function code of ABORT. DYNREAD interprets a function code of SPACES as a request to retrieve and process the DYNPRINT default data access request block (DYNPRQST). If none is present, DYNREAD sets a return code, sets the function code to ABORT, and returns. If the CA-EARL program calls DYNREAD again with a function of ABORT, this message will be issued.

Action:

Check the CA-EARL source for possible errors. Compare with the source code in one of the standard reports to see how they handle conditional retrieval of the DYNPRQST block. If issued by a standard DYNPRINT report function, contact Computer Associates for support.

Messages 2–367

CADV Prefixed Messages


CADV001E — SYS001 NOT ASSIGNED

Reason:

CA-Dynam/FastVTOC has been executed to display the VTOC on the device where SYS001 is assigned, and SYS001 has been found to be assigned incorrectly.

Action:

Correct the assignment for SYS001 and resubmit the job.

CADV002E — NO DASD DEVICES ASSIGNED

Reason:

CA-Dynam/FastVTOC has been executed to display the VTOC on all assigned DASD devices, and none are found assigned.

Action:

Assign DASD devices and resubmit the job.

CADV003E — INSUFFICIENT STORAGE FOR EXECUTION

Reason:

CA-Dynam/FastVTOC has been executed with insufficient partition GETVIS available to run.

Action:

Execute CA-Dynam/FastVTOC in a partition with SIZE=AUTO.

CADV004E — ERROR OCCURRED AT ADDRESS=xxxxxxxx RETURN CODE=xxxx

Reason:

CA-Dynam/FastVTOC has encountered an unexpected condition.

Action:

The address shown should be noted and documentation collected prior to calling Computer Associates.



CADV005E — INVALID CONTROL CARD

Reason:

CA-Dynam/FastVTOC has encountered an invalidly formatted control statement.

Action:

Correct the control statement in error and resubmit.

CADV006E — VOLUME/POOL CANNOT BE LOCATED

Reason:

One of the following may have occurred:

■ CA-Dynam/FastVTOC cannot locate a requested volume.

■ The COMPOOL option record is not present or does not contain the requested pool name.

■ There were no volumes mounted for the specified pool.

Action:

Correct the error and resubmit.

CADV007D — ENTER DYNVTOC CONTROL CARD

Action:

Reason:

Reason:

CA-Dynam/FastVTOC has been executed from the console.

Enter any valid CA-Dynam/FastVTOC control statement and (EOB/END).

CADV008W — UNEXPECTED FORMAT RECORD FOUND AT ADDRESS xx LINKED FROM xx

CA-Dynam/FastVTOC has encountered an unexpected VTOC record (Format 2-5) linked from another record. Both record addresses are displayed.

Messages 2–369


Action:

Use DITTO or DYNUTIL to display the records in the VTOC to determine the cause of the error. This indicates corruption of the VTOC.

CA-Dynam/FastVTOC has encountered an unexpected error return code from the System Adapter VTOC processor during VTOC OPEN.

Action:

Reason:

CADV009E — ERROR OCCURRED DURING VTOC OPEN CUU=cuu R/C=xxxx

Reason:

Action:

Document the problem and contact Computer Associates. Verify the contents and format of the VTOC of the volume on the device indicated, and check for I/O errors on the device in EREP. If you can replicate the error, run a VTOC trace and forward documentation to Computer Associates.

Reason:

An error was returned while trying to AVR a DASD volume.


CADV100E — SYSTEM ADAPTER IS NOT ACTIVE. PROCESSING TERMINATED.

CADV010E — AVRDASD ERROR OCCURRED F/C=xx

CAINTDK has been executed, but the System Adapter has not been initialized.

Action:

Execute CASAUTIL to activate CA-Dynam.



CADV101D — ENTER VTOC CONTROL CARD

Reason:

CAINTDK has been executed, but no control statement has been found on SYSIPT.

Action:

Enter valid CAINTDK control statement.

CADV102E — ERROR IN VTOC CONTROL CARD

Reason:

CAINTDK has been executed, but an error has been encountered in a control statement.

Action:

Correct the error and reenter.

CADV102D — ERROR IN VTOC CONTROL CARD RE-ENTER

Reason:

CAINTDK has been executed, but an error has been encountered in a control statement.

Action:

Correct the error and reenter.

CADV103D — ENTER VOL CONTROL CARD

Reason:

CAINTDK expects a VOL control statement, but none was entered.

Action:

Enter a valid CAINTDK VOL control statement.

Messages 2–371


CADV104E — ERROR IN VOL CONTROL CARD

Reason:

CAINTDK has been executed, but an error has been detected in the VOL control statement.

Action:


CADV104D — ERROR IN VOL CONTROL CARD RE-ENTER

Reason:

CAINTDK has been executed, but an error has been detected in the VOL control statement.

Action:


CADV105E — ERROR IN GETVCE R/C=rc

Reason:

CAINTDK has received an unexpected return code from the IBM GETVCE option record.

Action:

Consult the GETVCE return codes for the cause of the error.

CADV106E — DEVICE IS NOT AN FBA DASD

Reason:

CAINTDK has been executed, but the device to be initialized is not FBA.

Action:

Correct the JCL and resubmit.



CADV107E — DEVICE WAS NOT PREVIOUSLY FORMATTED

Reason:

CAINTDK has been executed, but the DASD device has not been formatted for use by INTDK previously.

Action:

Format the DASD device and place the VTOC where desired. CAINTDK is not needed.

CADV108E — VOLID READ=volser REQUESTED VOLID=volser

Reason:

CAINTDK has been executed, but the volume serial number of the assigned disk does not match that specified in the parameter statement.

Action:


CADV109E — NEW VTOC EXCEEDS DEVICE CAPACITY

Reason:

The starting PBN for the VTOC is too large for the number of format records requested.

Action:


CADV110E — GETVIS FAILURE R/C=rc

Reason:

CAINTDK has been executed, but an error return code has been issued from the IBM GETVIS option record.

Action:

Check the GETVIS return code, correct the error and resubmit.

Messages 2–373


CADV111E — INSUFFICIENT PARTITION GETVIS

Reason:

CAINTDK has been executed, but there is not sufficient partition GETVIS available for it to function.

Action:

Modify the SIZE parameter and resubmit.

CADV112E — VTOC CONTROL CARD MISSING

Reason:

CAINTDK has been executed, but no VTOC control statement has been submitted. The VTOC control statement is required.

Action:


CADV113E — ERROR DURING VTOC I/O F/C=nnn R/C=nnnnnnnn,nnnnnnnn

Reason:

An unexpected return code has been received during indexed VTOC processing from the VTOC access component. The function code and return codes are VTOC codes, and they indicate a problem in access of the VTOC itself.

Action:

Inspect the return code for 'normal' errors such as insufficient storage. (See "Indexed VTOC Return Codes".) If the problem does not appear to be of this nature, document the problem and contact Computer Associates.

CADV115E — UNEXPECTED ERROR OCCURRED. SAVE DUMP

Reason:

CAINTDK has been executed, and an internal logic error has been detected.

Action:

Report the problem to Computer Associates.



CADV116E — I/O ERROR OCCURRED. SAVE DUMP

Reason:

CAINTDK has been executed, and an I/O error on disk has been detected.

Action:

Consult EREP for the disk volume. If the problem is reproducible, report the problem to Computer Associates.

CADV117E — NEW VTOC OVERLAPS DSN=dsn

Reason:

CAINTDK has been executed, but the new VTOC specified overlaps an existing file.

Action:

Correct the JCL, or delete the file and resubmit.

CADV118E — VTOC IS FULL

Reason:

The extent for the new VTOC is too small.

Action:

Enlarge the extent for the new VTOC and resubmit.

CADV120E — I/O ERROR DURING WRITE OF NEW VOL1 RECORD. SAVE DUMP.

— I/O ERROR DURING WRITE OF NEW VTOC. SAVE DUMP.

Reason:

CAINTDK has been executed, but an I/O error has occurred during rewrite of the VOL1 or VTOC.

Action:

Consult EREP for further information. Contact Computer Associates if the problem persists.

Messages 2–375


CADV122I — NEW VTOC IS FORMATTED STARTING ADDRESS=address

— NUMCI=numci TOTAL FORMAT RECORDS=number-of-records

— ACTIVE FORMAT RECORDS=number-of-records

Reason:

Self-explanatory.

Action:

None.

CADV123E — ERROR DURING MODVCE R/C=rc

Reason:

CAINTDK has been executed, but an error return code has been received from the IBM MODVCE option record.

Action:

Consult documentation on the MODVCE option record for return codes. Correct error and resubmit.

CADV200E — SYSTEM ADAPTER ERROR OCCURRED F/C=nnn R/C=nn

Reason:

An unexpected return code has been received during VTOC processing from the System Adapter component. The function code and return codes are System Adapter codes, and indicate a problem there.

Action:

Document the problem and contact Computer Associates. Verify the contents and format of the VTOC and VTOC Index of the volume on the device indicated by running an LVTOC and CA-Dynam/FastVTOC for the volume with indexed VTOC support active, then again with it deactivated. Compare the two. If the problem is reproducible, a VTOC trace should be run.



CADV201E — INDEX ERROR OCCURRED F/C=nnn R/C=xxxxxxxx VOL=volser CUU=cuu

— INTERCEPT ERROR OCCURRED F/C=nnn R/C=xxxxxxxx VOL=volser CUU=cuu

Reason:

The first form of the message appears when an unexpected return code has been received during Indexed VTOC processing from the catalog management component. The function code and return codes are Catalog Management codes, and indicate a problem in access of the VTOC Index file.

The second form of this message is issued by the common VTOC handler intercept if an error is returned from Indexed VTOC. Inspect the return code for 'normal' errors such as insufficient storage. (See the return codes at the end of this guide.) If the problem does not appear to be of this nature, document the problem and contact Computer Associates.

Action:

Verify the contents and format of the VTOC and VTOC Index of the volume on the device indicated by running an LVTOC and CA-Dynam/FastVTOC for the volume with indexed VTOC support active, then again with it deactivated. Compare the two. If the problem is reproducible, a VTOC trace should be run.

CADV202E — VTOC ERROR OCCURRED F/C=nnn R/C=xxxxxxxx VOL=volser CUU=cuu

Reason:

An unexpected return code has been received during VTOC processing from the VTOC access component. The function code and return codes are VTOC codes, and they indicate a problem in access of the VTOC itself.

Action:

Inspect the return code for 'normal' errors such as insufficient storage. (See Indexed VTOC return codes at the end of this guide.) If the problem does not appear to be of this nature, document the problem and contact Computer Associates.


Messages 2–377


CADV203S — OVERLAP ON SPACE HOLDER VOL=volser, CUU=cuu JOB CANCELED

Reason:

An unexpected overlap condition has been detected by VTOC management between a file and space which has been allocated for use by CA-Dynam/D. This message indicates that the VTOC Index is not reliable, and should be rebuilt using the DYNCAT VTOC function. The overlap has been detected and the job cancelled to prevent damage to the VTOC itself -- which is intact.

Action:

Run the DYNCAT VTOC function to rebuild the VTOC index on the indicated volume.


CADV204I — BUILDINDEX IN PROGRESS FOR VOL=volser CUU=cuu

Reason:

This message appears when the VTOC index file on the indicated volume is being built. It will appear when the index is initially formatted by the DYNCAT VTOC command. In addition, it will appear for each volume which is found to contain a VTOC index when the VTOC is opened for the first time after an IPL, and at approximately 8:00 a.m. each morning. When the index is built, all expired files on the volume are automatically deleted. This message will also appear if the operator responds to the CADD021 message with BLDINDX.

Action:

None.

CADV205I — VTOC INDEX NOT ACCESSIBLE. NONINDEXED PROCESSING CONTINUES. VOL=volser CUU=cuu

Reason:

The index has been corrupted.

Action:

Run the DYNCAT VTOC function to rebuild the index on the volume.



CADV206W — VTOC INDEX NOT FOUND. VTOC FLAGGED AS NONINDEXED. VOL=volser CUU=cuu

Reason:

The format-1 record for the VTOC index is missing even though the volume is flagged as being indexed.

Action:

Run the DYNCAT VTOC function to put a new index on the volume.

CADV900E — ERROR HAS OCCURRED: RTNxx

Reason:

This message is issued by the VTOC processer to indicate the return code set for a particular internal error. It is issued in conjunction with the particular internal error message in the range CADV901E - CADV942E.

Action:

Collect diagnostic information and contact Computer Associates for assistance.

CADV901E — INVALID FUNCTION CODE

Reason:

An internal error was detected. Message CADV900E, issued in conjunction with this message, displays the error return code.

Action:


CADV902E — NO FREE STORAGE AVAILABLE

Reason:


Action:


Messages 2–379


CADV903E — INVALID ADDRESS OF DSN

Reason:


Action:


CADV904E — INVALID ADDRESS OF NEW DSN

Reason:


Action:


CADV905E — INVALID ADDRESS OF BUFFER

Reason:


Action:


CADV906E — GETAREA ERROR

Reason:


Action:




CADV907E — FREEAREA ERROR

Reason:


Action:


CADV908E — SAVER ERROR

Reason:


Action:


CADV909E — MESSAGE WRITER ERROR

Reason:


Action:


CADV910E — UNSUPPORTED DEVICE TYPE

Reason:


Action:


Messages 2–381


CADV911E — GETVCE ERROR

Reason:


Action:


CADV912E — INCONSISTENT INDEX

Reason:


Action:


CADV913E — DATASET NOT FOUND

Reason:


Action:


CADV914E — END OF VTOC ON SEQUENTIAL RETRIEVE

Reason:


Action:




CADV915E — VTOC FULL

Reason:


Action:


CADV916E — INSUFFICIENT SPACE

Reason:


Action:


CADV917E — ERROR OCCURRED IN CACNPHY0

Reason:


Action:


CADV918E — READ ONLY (WRITE INHIBIT)

Reason:


Action:


Messages 2–383


CADV919E — I/O ERROR READING VOL1 LABEL

Reason:


Action:


CADV920E — VOLUME NOT MOUNTED OR LUB UNASSIGNED

Reason:


Action:


CADV921E — I/O ERROR READING VTOC

Reason:


Action:


CADV922E — DUPLICATE NAME ON VOLUME

Reason:


Action:




CADV923E — VTOC FULL

Reason:


Action:


CADV924E — OVERLAP ON UNPROTECTED UNEXPIRED FILE

Reason:


Action:


CADV925E — OVERLAP ON PROTECTED UNEXPIRED FILE

Reason:


Action:


CADV926E — OVERLAP ON VTOC

Reason:


Action:


Messages 2–385


CADV927E — FORMAT-1 OR NEXT LABEL NOT FOUND

Reason:


Action:


CADV928E — INVALID READ OR WRITE ADDRESS

Reason:


Action:


CADV929E — OVERLAP ON PROTECTED EXPIRED FILE

Reason:


Action:


CADV930E — SECURITY VIOLATION

Reason:


Action:




CADV931E — INVALID VTOC SHARE OPTION

Reason:


Action:


CADV932E — EXTENTS OVERLAP AMONG THEMSELVES

Reason:


Action:


CADV933E — USER-SUPPLIED WORK AREA TOO SMALL

Reason:


Action:


CADV934E — FORMAT-4 LABEL NOT FOUND

Reason:


Action:


Messages 2–387


CADV935E — VOL1 LABEL NOT FOUND

Reason:


Action:


CADV936E — ASSGN PROCESSING FAILURE

Reason:


Action:


CADV937E — DATA CHECK I/O ERROR

Reason:


Action:


CADV938E — LABELS NOT ALL FORMAT-1 OR FORMAT-3

Reason:


Action:




CADV939E — LOCK INCONSISTENT WITH PREVIOUS LOCK

Reason:


Action:


CADV940E — LOCK WOULD RESULT IN A DEADLOCK

Reason:


Action:


CADV941E — DTL FORMAT ERROR

Reason:


Action:


CADV942E — UNRECOVERABLE I/O ERROR ON LOCK FILE

Reason:


Action:


Messages 2–389

CASP Prefixed Messages


CASP001E — SYNTAX ERROR

Reason:

The command processed contains a syntax error.

Action:

Correct the command and press the ENTER key.

CASP002E — INVALID COMMAND

Reason:

The command processed is not valid.

Action:

Enter a valid command and press the ENTER key.

CASP003E — INVALID OPERAND

Reason:

The operand processed is not valid.

Action:

Enter a valid operand and press the ENTER key.

CASP004E — INVALID SHORTFORM COMMAND

Reason:

The short command is not defined to the system.

Action:

Enter a valid short command and press the ENTER key.



CASP005E — INVALID RELATION

Reason:

The specified relational operator is not valid.

Action:

Enter a valid relational operator.

CASP006E — INVALID DATA SPECIFIED

Reason:

The fields with invalid data are displayed in high intensity.

Action:

Correct the field(s) in error.

CASP007I — RECORD SUCCESSFULLY UPDATED

Reason:

The record has been successfully updated.

Action:

None.

CASP008E — OPERAND nn IS INVALID

Reason:

Operand nn is not valid.

Action:

Enter a valid operand and press the ENTER key.

Messages 2–391


CASP010I — TOP OF FILE

Reason:

The top of the display has been reached.

Action:

None.

CASP011I — END OF FILE

Reason:

The end of the display has been reached.

Action:

None.

CASP012I — TOP/END OF FILE

Reason:

The top of the display has been reached and there are no more records to display.

Action:

None.

CASP013I — INVALID DASD POOL

Reason:

The pool name processed is not valid.

Action:

Enter a valid DASD pool name and press the ENTER key.



CASP014I — DASD VOLSER NOT FOUND

Reason:

The DASD volser processed is not valid.

Action:

Enter a valid volser and press the ENTER key.

CASP015I — RECORD NOT FOUND

Reason:

The selected record was not found.

Action:

None.

CASP016I — VSAM CATALOG NOT FOUND

Reason:

The VSAM USER catalog could not be found.

Action:

Check if the Master Catalog name matches your standard labels, and enter a valid catalog name and press ENTER.

CASP017I — VSAM DATA SET NOT FOUND

Reason:

The data set name processed is not valid.

Action:

Enter a valid data set name and press the ENTER key.

Messages 2–393


CASP018I — NO INFORMATION AVAILABLE

Reason:

No information is available for this request.

Action:

None.

CASP019E — VOLSER xxxxxx IS NOT AVAILABLE

Reason:

The volser where this catalog resides is not available.

Action:

Make this volser available for to VSE.

CASP020E — DELETE FAILED ID1AERR1 RETURN CODE = xxxx

Reason:

The DELETE you requested was not successful.

Action:

Copy the return code information and contact Computer Associates Technical Support.

CASP021E — DEFINE FAILED ID1AERR1 RETURN CODE = xxxx

Reason:

The DEFINE you requested was not successful.

Action:




CASP022I — DEFINE SUCCESSFUL

Reason:

The DEFINE you requested was successful.

Action:

None.

CASP023E — IDCAMS FAILED ID1AERR1 RETURN CODE = xxxx

Reason:

The function you requested was not successful.

Action:


CASP024E — UNABLE TO ACCESS INFORMATION R/C=xxxxxxxx

Reason:

An error occurred during catalog access processing. One of the following return codes may accompany the message:

64 Insufficient partition GETVIS.

66 SRAM open error.

Action:

Check return codes for possible corrections to the problem. If the problem persists, contact Computer Associates Technical Support.

CASP025E — CA VSE SYSTEM ADAPTER UNAVAILABLE

Reason:


Action:

Activate the System Adapter.

Messages 2–395


CASP026I — NO DATA SET WITHIN POOL BOUNDARIES

Reason:

No data sets have been found within the pool boundaries.

Action:

Run DYNVTOC and CAISERV, then check the COMPOOL option record definitions corresponding to the data sets found on the VTOC.

CASP030E — UPDATE FAILED

Reason:

The update cannot be processed at this time because an invalid object name or invalid data was entered.

Action:

Check any of the reasons above and retry the function call.

CASP050E — UNABLE TO ACCESS VTOC INFORMATION R/C=xxxxxxxx

Reason:

An error occurred during VTOC access processing. One of the following return codes may accompany the message:

-1 The volser you specified was not found.

-2 CICS abend.

64 Insufficient partition GETVIS.

65 Invalid VTOC assign.

66 SRAM open error.

67 VTOC open error.

68 Error during a VTOC read.

Action:

Check return codes for possible corrections to the problem. If the problem persists, contact Computer Associates Technical Support.



CASP100I — CA-DYNAM FUNCTION INITIALIZATION IN PROGRESS

Reason:

The CA-Dynam initialization process has started.

Action:

None.

CASP101I — CA-DYNAM FUNCTION INITIALIZATION COMPLETE

Reason:

The CA-Dynam initialization process has successfully completed.

Action:

None.

CASP102E — CAICUI XFCS IS NOT ACTIVE

Reason:

The XFCS subtask was not properly activated.

Action:

Refer to the messages that were previously issued, and correct the conditions. If the problem persists, contact Computer Associates Technical Support.

CASP103E — CA-DYNAM CASPUTLO FUNCTION ATTACH FAILED

Reason:

The CASPUTLO function was not successfully attached.

Action:

Refer to the messages that were previously issued, and correct the conditions that caused the attach to fail.

Messages 2–397


CASP104E — CA-DYNAM CAYDSERV FUNCTION ATTACH FAILED

Reason:

The CAYDSERV function was not successfully attached.

Action:

Refer to the messages that were previously issued, and correct the conditions that caused the attach to fail.

CASP105E — CA-DYNAM FUNCTION INITIALIZATION FAILED

Reason:

The CA-Dynam initialization failed.

Action:

Check the return code and error messages to determine the probable cause(s), and retry the initialization. If the problem persists, contact Computer Associates Technical Support.

CASP200I — CA-DYNAM FUNCTION SHUTDOWN IN PROGRESS

Reason:

The CA-Dynam shutdown process has started.

Action:

None.

CASP201I — CA-DYNAM FUNCTION SHUTDOWN COMPLETE

Reason:

The CA-Dynam shutdown process has successfully completed.

Action:

None.



CASP202I — CA-DYNAM FUNCTION SHUTDOWN FAILED

Reason:

The shutdown for the CA-Dynam system failed.

Action:

Check all the return codes and messages to determine the problem, and rerun the job. If the problem persists, contact Computer Associates Technical Support.

CASP500E — ENTER EITHER DTFNAME OR FILEID AND VOLSER

Reason:

Either a DTFname or a fileid AND volser must be entered to open the history file.

Action:

Enter the appropriate information to continue.

CASP502E — DETAIL SCREEN REQUIRES APAR OR PTF NUMBER AS INPUT

Reason:

An SPI D MSHPDET command was entered without the keyword operand NUM=nnnnnnn. The SPI-5110 MSHP Apar/Ptf DETAIL screen requires an APAR or PTF number to process.

Action:


Messages 2–399


CASP510E — CICS ERROR ON TEMPORARY STORAGE QUEUE R/C=nnnn

Reason:

CICS returned an error trying to read or write to a temporary storage queue.

Action:

Consult the appropriate CICS manual and the table below to determine the error and action.

R/C Type of Error Action

4 Queue ID error Contact Computer Associates

8 Invalid request Contact Computer Associates

0C Item error Contact Computer Associates

10 I/O error Contact Computer Associates

14 No space Check space allocation, and Contact Computer Associates

CASP511E — HISTORY FILE HAS NO INSTALLED PRODUCTS

Reason:

The history file was accessed and a search for APARS and/ or PTF's was instituted but no Install (i.e. component) records were found.

Action:

Check that the correct history file is being accessed. Execute an LSERV to check that the label in standard labels (if DTFname is used to access the file) points to the correct DLBL and EXTENT information. Run a MSHP RETRACE to see that components are installed in this file.

CASP512E — LABEL FOR DTFNAME NOT FOUND IN STANDARD LABELS

Reason:

A dtfname was entered on the selection screen but the required label was not in standard labels.

Action:

Execute an LSERV to check that the label is in standard labels.



CASP513E — HISTORY FILE NOT FOUND ON VOLUME

Reason:

A DSN and Volser was entered on the selection screen but a search of the VTOC on the volume entered failed to locate a matching DSN.

Action:

Verify that the DSN is correctly entered on screen. Execute a VTOC listing to verify that the history file is on that volume.

CASP514E — VOLSER NOT FOUND OR NOT AVAILABLE

Reason:

A DSN and Volser was entered on the selection screen but we were unable to locate or access that volume.

Action:

Verify that the volser is correct. Insure that the volume is available and accessible.

CASP520E — ERROR ACCESSING MSHP FILE R15=xxxxxxxx,R0=xxxxxxxx

Reason:

A call to open the history file was made and was not successful.

Action:

Consult the table below to determine the appropriate action

R15 Type of Error Explanation/Action

04 End-of-file An unexpected EOF condition was returned on a call to read a record in the history file. Contact Computer Associates.

08 Record not found

A call to retrieve a record was made and it could not be found. Check that correct history file is being accessed. Run MSHP RETRACE to verify existence of the desired record in this history file.

0C History file not found

Check labels, dsn, volser to insure that the history file you wish to process is correctly pointed to.

Messages 2–401


R15 Type of Error Explanation/Action

10 Invalid call to CASPMS1A

An invalid function code was passed to the program to read the history file. Contact Computer Associates

14 GETVIS error R0=GETVIS return code.

18 GETVCE error R0=GETVCE return code.

1C VTOC error R0=VTOC return code.

20 LABEL error R0=LABEL return code.

24 No volser or lub found in DLBL statement

A call by DTFname was made and the label in standard labels did not have either a volser or lub in it. Correct label or access by DSN and Volser.

28 I/O error R0=IORB status bytes.

2C RBA too high A call to CASPMS1A was made to retrieve a record and the RBA was higher than the highest RBA in the file. Contact Computer Associates

30 Not a history file

The program has determined that the file being accessed is not a history file. Check label information, DSN, Volser etc.

34 Work area has been overlayed

The internal work area used by CASPMS1A has been overlayed. Contact Computer Associates

38 EXTENT error R0=EXTENT return code.

CASP521E — RECORD NOT FOUND

Reason:

A call to retrieve a history file record was made and the record was not found.

Action:

Check that correct history file is being accessed. Run MSHP RETRACE to verify existence of the desired record in this history file.



CASP522E — MSHP ACCESS ERROR, xxxxxxxx,+xxxx

Reason:

A call to read the history file was made and returned an error. XXXXXXXX is the program name where the error was returned and +XXXX is the displacement into that program where the call failed.

Action:

Contact Computer Associates

CASP560E — DTFNAME IS REQUIRED FOR DETAIL DISPLAY

Reason:

An SPI D LABELDET command was entered which requires a dtfname as minimum input (the group defaults to system)

Action:


CASP561E — ENTER LABEL GROUP

Reason:

The Label Selection panel (CASP6000) requires the entry of a label group if no other selection criteria is entered. Acceptable groups are: System, Parstd, Classtd, User or * (for all groups).

Action:

Enter one of the above choices for label group.

CASP562E — LABEL ACCESS ERROR, cccccccc+nnnn, R0=nnnn,RF=nnnn

Reason:

A call to access the label file was made and was not successful. cccccccc is the module id that returned the error at +nnnn into the module. R0 is the contents of general register 0 which will contain the return code from the function being executed. RF is the contents of general register 15 which will contain the return code from CA's label subtask program (CASPLB1A).

Messages 2–403


Action:

Consult the table below of RF return codes to determine the appropriate action.

RF Type of Error Explanation/Action

04 End-of-file An unexpected EOF condition was returned on a call to read a record in the label file. Contact Computer Associates.

0C Invalid call to label subtask

A call to the label subtask had an invalid function code. Contact Computer Associates

10 Storage A call to allocate storage received a bad return code from the System Adapter Getarea function. R0 contains the return code.

14 Storage overlay Subtask work area was overlayed. There is a good possibility that this error will be accompanied by a CICS storage violation message. Take an AR dump of the CICS partition if no storage violation else take a DFHDUMP. Contact Computer Associates.

1C $IJBSLA A call to read the label file received an unacceptable return code from IBM's label phase. R0 contains the return code from $IJBSLA.

20 Update in progress

A return code from $IJBSLA indicated that the label area being accessed was in the process of being updated. Check that no job is running that accesses that subarea and try again.

28 GETPAEA The label subtask was trying to locate this CA-Dynam control block and could not. Contact Computer Associates

2C 30 Option blk not found Other option block errors

A call to locate the label option block for a Dtfname returned an error. R0 contains the return code from the System Adapter Labelopt function. Contact Computer Associates.

CASP563E — INVALID DATA FOR NON-VSE/ESA SYSTEM

Reason:

User entered data that is only valid on a VSE/ESA system such as CLASSTD or partition id that is neither BG nor begins with the letter 'F'.



Action:

Enter group or partition id that is consistent with the VSE system that you are running.

CASP564E — LABEL SUBAREA NOT FOUND

Reason:

User selected a group and partition (or Class on ESA) that has no labels currently in it.

Action:

Enter a subarea for which labels exist. If you believe label exist for this group verify with LSERV and contact Computer Associates.

CASP565E — LABEL NOT FOUND, DTF=ccccccc

Reason:

Specific selection criteria was entered that would normally result in one specific label being selected for either directory or detail display but no label was found with this dtfname in the subarea selected.

Action:

Verify with LSERV that the label exists in that subarea. If it does contact Computer Associates.

CASP566E — LABEL AREA UPDATE IN PROGRESS. DATA UNAVAILABLE OR OBSOLETE

Reason:

A search of a label subarea was undertaken and a return code from IBM's label handling phase indicated that this subarea was in the process of being updated resulting in no label being returned.

Action:

Insure that no job is running that updates that subarea before retrying or retry after a short wait.

Messages 2–405

CATA Prefixed Messages

CASP567E — INVALID LABEL GROUP

Reason:

An invalid label group was entered.

Action:

Enter a valid label group (S,P,C,U or *)


CATA001I — TASK MANAGER IS ACTIVE REL nn.n GEN xxxxxxxx

Reason:

During system initialization, the release and generation level of Task Manager are displayed for possible problem resolution.

Action:

No action required.

CATA002I — (c) - COMPUTER ASSOCIATES INTERNATIONAL,INC

Reason:

During system initialization, this copyright statement is displayed. The Task Manager is being executed.

Action:

No action required.

CATA003I — (userid) message

Reason:

A command was entered at the service virtual machine console or an SMSG was received from the noted userid. The entire message is displayed for reference.

Action:

No action required.



CATA004I — REPLY nnn CANCELLED

Reason:

The task waiting for a response to reply message number nnn, was canceled. The task is no longer active, and a response is not required. Any response to this message number is considered an error and is ignored. This is an internal function which is the result of the cancellation of a specific task or the purge of a product using the system PURGE command or normal/abnormal termination of a product.

Action:

No action required.

CATA005I — product LOADED AT address

Reason:

A product has been loaded into the specified address and has begun execution. The product is now considered active. This message is useful for dump analysis and problem resolution.

Action:

No action required.

CATA006E — OUTSTANDING REPLY nnn NOT FOUND

Reason:

An attempt has been made to respond to a reply that does not exist. The response is rejected and not processed.

Action:

Enter QUERY REPLY to display a list of outstanding replies. The reply message number and userid destination are displayed at the system console. Determine the proper reply message number and enter again.

Messages 2–407


CATA007E — command string CONTAINS AN INVALID TASK MANAGER COMMAND

command string IS A PRIVILEGED TASK MANAGER COMMAND

Reason:

The command string entered is not a valid Task Manager command or the command requires Task Manager Operator privilege. The command is ignored.

Action:

Examine the command entered. If it is a product command, precede the command with the proper product name.

CATA008I — command COMMAND COMPLETE, RC = nnn

Reason:

The command has been completed. The return code indicates the completion condition.

Action:

No action required.

CATA009I — NO OUTSTANDING REPLIES

Reason:

There are no outstanding replies, in response to a QUERY REPLY command.

Action:

No action required.

CATA010E — UNABLE TO PURGE product NOT ACTIVE OR DEFINED

Reason:

A PURGE command was entered for a product that was not active or defined in the product table. The purge request is ignored and not processed.

Action:

Enter QUERY ACTIVE to display a list of the active products. If necessary, enter the command again with the proper product name.



CATA011E — STORAGE RELEASE FAILURE FOR address AT call-location

Reason:

Dynamic storage may be corrupted, and consequently, results are unpredictable.

Action:

Terminate all active tasks as soon as possible, then enter the command, CAISTOP DUMP. Collect all relevant documentation and contact Computer Associates for technical assistance.

CATA012I — product IS NOT ACTIVE

Reason:

An attempt was made to send a command to a specific product, but the product is not active. The command is not processed.

Action:

Enter QUERY ACTIVE to determine what products are currently active. Verify that the product prefix used on the command was correct. Ask the System Support staff when the product will be available and enter the command again.

CATA013I — product IS ACTIVE AT xxxxxx REL release GEN generation

Reason:

QUERY ACTIVE was requested. All of the products currently active are listed with a description of the product, its release and its generation level for problem resolution.

Action:

No action required.

CATA015E — UNABLE TO LOAD product ... PRODUCT TERMINATED

Reason:

A product load has failed. The cause of the problem is usually displayed by a CMS message prior to this error message.

Messages 2–409


Action:

Review the system console for any CMS message which describes the load failure. Examine the Task Manager system profile GLOBAL statement to verify that the necessary TXTLIBs are properly defined. If necessary, enter the GLOBAL command to correct the TXTLIB search sequence. Enter a CMS ACCESS command if the TXTLIB resides on another user minidisk. Enter the product's LOAD command again.

CATA016E — TCB=xxxxxx product-name task-name

Reason:

This message is displayed in conjunction with message CATA011E, when a storage request failure occurs. It is used to identify the requesting task.

Action:

Save the system console for problem resolution.

CATA017E — NOT OWNED. OWNED BY TCB=xxxxxx product-name task-name request owner-tcb

Reason:

This message is displayed in conjunction with message CATA011E, when a storage failure occurs. It is used to identify the task that owns the storage which caused the failure.

Action:

Save the system console for problem resolution.

CATA018E — PRODUCT product ALREADY ACTIVE

Reason:

A LOAD command was entered for a product that was already active. The load request is ignored and not processed.

Action:

Enter QUERY ACTIVE to display a list of the active products. If necessary, enter the command again with the proper product name.



CATA020E — INSUFFICIENT STORAGE TO LOAD product

Reason:

The storage defined for the CA-Dynam/CMS service virtual machine is insufficient to support the product noted.

Action:

Enter CAISTOP to terminate the Task Manager. Define sufficient storage for the virtual machine to support the task. Examine the CMS cushion size entered on the parameter list and adjust if necessary.

CATA021I — userid IS PRIVILEGED FOR MSGNOH

Reason:

The proper VM privilege has been assigned to the Task Manager virtual machine userid for issuing MSGNOH commands in place of MSG commands for disconnected operator communications. This message is displayed during Task Manager initialization.

Action:

No action required.

CATA022I — STORAGE SIZE=s,sssK FREE=f,fffK

Reason:

This message is displayed as a response to a 'QUERY STORAGE' command request.

Action:

No action required.

CATA023I — TCB=xxxxxx queue-priority product task return dev/user/time

Reason:

The information is displayed for each task attached in the service machine in response to a TCB QUERY command.

Action:

No action required.

Messages 2–411


CATA040E — DISK function ERROR nnn ON filename filetype filemode AT address

Reason:

A disk I/O error has occurred on the file displayed. The I/O error code (nnn) identifies the CMS disk read or write error (refer to FSREAD and FSWRITE macro error conditions in the CMS Command and Macro Reference manual).

Action:

Determine that the disk device for that filemode is properly accessed.

CATA051W — CONFLICTING NODE ID node FOR SYSID userid AT node-id

Reason:

A STARTCTC command has been specified stating that this node should be communicating with the specified userid on the indicated node-id across this CTC. The CPU-ID is used in conjunction with the SYSTEM NETID file for determining the node-id in which the service machine is running. This message indicates that a potential problem exists, but the CTC link remains connected.

Action:

Verify that the destination userid, node-id and SYSTEM NETIF file are correct and that an incorrect TASKNODE statement has not been placed in the TASKMAN SYSPROF file of the destination. If the node-id is not correct, enter a STOPCTC command, followed by the correct STARTCTC command.

CATA090I — WARNING, STORAGE AVAILABLE IS CRITICALLY LOW

Reason:

The mixture of products and active tasks has drained the available Task Manager storage pool to a critical level. The products are not effected by this message. System performance may be affected by this condition.

Action:

Examine the virtual machine size and, if necessary, make adjustments before the next execution.



CATA091I — product TERMINATED

Reason:

The indicated product (task) has been terminated, either by a product command, a PURGE command, or by termination of the Task Manager itself.

Action:

No action required.

CATA096E — PROG EXC 0Cx HAS OCCURED AT address, product load-address task subtask displacement

Reason:

A program exception has occurred in a task operating under Task Manager. The task in error is canceled.

Action:

Contact Computer Associates for technical support relating, in full, the information displayed. A Task Manager dump will be spooled to the printer. Retain the dump and console log for problem determination and resolution.

CATA097E — FATAL ERROR HAS OCCURRED, RC = nnn

Reason:

The return code, nnn, is intended to assist Computer Associates' personnel in determining precisely and accurately the nature of the problem. This message normally appears in conjunction with another message which indicates precisely the nature and cause of the fatal error.

Action:

Contact Computer Associates for technical support. Ensure that the CA-Dynam/CMS service virtual machine console log is available and at hand.

CATA098E — TASK MANAGER REQUIRES 'ECMODE' SET...SYSTEM TERMINATED

Reason:

The environment of the virtual machine is not properly set for Task Manager execution. Task Manager multitasking operating system is terminated and control is reset to the normal CMS environment

Messages 2–413


Action:

Set ECMODE ON and execute Task Manager again.

CATA099I — TASK MANAGER TERMINATED

Reason:

Task Manager multitasking operating system is terminated and control is reset to the normal CMS environment.

Action:

Determine the cause of the system termination. If due to a critical error, make the appropriate corrections and begin Task Manager execution again.

CATA100I — CTCA ccuu NOT READY

Reason:

A QUERY NODE command was requested. This indicates that the channel-to-channel adapter (CTCA) was defined, but the destination userid has not finished the connection.

Action:

No action required.

CATA101I — CTCA ccuu CONNECT TO node

Reason:

A QUERY NODE command was requested. This message indicates that the channel-to-channel adapter (CTCA) connection is currently active.

Action:

No action required.



CATA102I — WRITE REQUEST THRESHOLD NUMBER nn

Reason:

A QUERY NODE command was requested.

Action:

No action required.

CATA103I — WRITE REQUEST LIMIT IN HUNDREDTHS SECONDS nnn

Reason:


Action:

No action required.

CATA104I — PERCENT MAXIMUM NUMBER OF WRITES OCCURRED nn

Reason:


Action:

No action required.

CATA105I — PERCENT MAXIMUM WAIT TIME OCCURRED nn

Reason:


Action:

No action required.

Messages 2–415


CATA106I — PERCENT BUFFER FULL OCCURRED nn

Reason:


Action:

No action required.

CATA107I — PERCENT NO BUFFER AVAILABLE OCCURRED nn

Reason:


Action:

No action required.


Chapter

3 Return Codes

CAD Return Codes Various messages produced by the system, especially those warning of unexpected or unusual conditions, contain function codes and return codes and other internal information which may be helpful in interpreting the cause of the condition. Each of the components of the system uses a scheme of function codes and return codes for internal communication. When a function completes, a return code which describes the end result of the function is passed. A return code of zero usually indicates successful completion. Return codes below are expressed in hexadecimal.

See the CA-CIS Message Guide for System Adapter return codes.

VTOC Return Codes

The return codes used by the VTOC access component fall into three categories:

■ Those specific to the VTOC nucleus (master return code X'18'),

■ Those returned to VTOC from the IBM VTOC handler ($IJJHCVH) (master return code X'1C'), and

■ Those returned to VTOC from Catalog Management (master return code X'20').

R/C Internal Meaning (and likely cause/action)

1804 INVALID FUNCTION CODE

1808 NO FREE STORAGE AVAILABLE

Insufficient partition GETVIS.

180C INVALID ADDRESS OF DSN

1810 INVALID ADDRESS OF NEW DSN

181C INVALID ADDRESS OF BUFFER

Return Codes 3–1

CAD Return Codes


1820 GETAREA ERROR OCCURRED

Insufficient partition GETVIS.

1824 FREEAREA ERROR OCCURRED

1828 SAVER ERROR OCCURRED

Insufficient system GETVIS.

182C MESSAGE WRITER ERROR

1830 UNSUPPORTED DEVICE TYPE

1834 GETVCE ERROR

Bad return code from GETVCE macro.

1838 INCONSISTENT INDEX

183C DATASET NOT FOUND

1840 END OF VTOC ON SEQ. RETRVE.

1844 VTOC FULL

VTOC extent is full; enlarge VTOC.

1848 INSUFFICIENT SPACE

VTOC extent is full; enlarge VTOC.

184C USER ABORTED VOLUME MAPPING

1850 READ ONLY (WRITE INHIBIT)

Volume is write inhibited.

1Cnn ERROR FROM $IJJHCVH

1C04 I/O ERROR READING VOL1 LABEL

1C08 VOLUME NOT MOUNTED OR LUB UNASSIGNED

1C0C I/O ERROR READING VTOC

1C10 DUPLICATE NAME ON VOLUME

1C14 VTOC FULL

1C1C OVERLAP ON UNPROTECTED UNEXPIRED FILE

1C20 OVERLAP ON PROTECTED UNEXPIRED FILE

1C24 OVERLAP ON VTOC

1C2C FORMAT-1 OR NEXT LABEL NOT FOUND

1C30 INVALID READ OR WRITE ADDRESS


CA-Dynam/T Return Codes


1C38 OVERLAP ON PROTECTED EXPIRED FILE

1C40 GETVIS FAILED

Insufficient partition GETVIS

1C44 SECURITY VIOLATION

1C4C INVALID VTOC SHARE OPTION

1C50 EXTENTS OVERLAP AMONG THEMSELVES

1C54 USER-SUPPLIED WORK AREA TOO SMALL

1C58 FORMAT-4 LABEL NOT FOUND

1C5C VOL1 LABEL NOT FOUND

1C60 JIB PROCESSING FAILURE

1C64 DATA CHECK I/O ERROR

1C6C LABELS NOT ALL FORMAT-1 OR FORMAT-3'S

1C70 LOCK INCONSISTENT WITH PREVIOUS LOCK

1C74 LOCK WOULD RESULT IN A DEADLOCK

1C78 DTL FORMAT ERROR

1C7C UNRECOVERABLE I/O ERROR ON LOCK FILE

20nn ERROR FROM CATALOG MANAGEMENT

The error code returned with a master return code of X'20' is the return code passed to the VTOC component by Catalog Management.


Return Code Description

'00' Processing successful (no errors).

04 CA-Dynam/T has not been generated into the System Adapter Modules.

24 Unrecognized command argument.

28 Unrecognized command option.

32 Invalid data set name.

36 Invalid ddname.

Return Codes 3–3



40 Invalid device address specified.

44 Invalid keyword parameter specified.

48 VMCF message rejected by service machine.

52 VMCF data transfer error.

56 System Adapter not available on accessed disk.

60 Volume not mounted (when NOMOUNT option specified).

64 CA-Dynam/T not active in service machine.

68 CA-Dynam/T control table not found in service machine.

72 TDCB not found in service machine (for DYNCLOSE commands).

76 Insufficient storage.

80 Device attach error.

84 Request canceled.

88 Device not available (using the RSV option).

92 Unauthorized request.

96 Device detach error.

100 DDNAME already in use (for DYNOPEN commands).

104 DASD DSN not in catalog (using the DISK option).

108 DASD version not in catalog (using the DISK option).

112 DASD volser not found (using the DISK option).

116 DASD data set not found in VTOC (using the DISK option).

120 Request cannot currently be canceled (DYNCANCL command).

124 TDCB not found for cancel (DYNCANCL command).

128 Request function is currently disabled.

132 CA-Dynam/T is currently quiesced.

136 Generic CA-Dynam/B tape returned.

140 Requested tape volume is already OPENed.

144 Request has been queued for later processing.

148 'WAIT nn' time limit expired.

152 System INCLUDE file I/O error.

156 System EXCLUDE file I/O error.


Catalog Management Return Codes


160 System OPERATOR file I/O error.

164 CA-DIRECTOR system interface error.

168 System service wait limit expired.

172 Error message passed to user.

176 Unknown return code received for service machine.

180 Invalid DYNRQA PLIST format (mixed modules).

184 Open or Mount request still pending completion.

Catalog Management Return Codes The Catalog Management subsystem is used for a variety of internal system functions as well as maintaining the data set catalogs, CAICATL and DYNBCAT. Auditing support also uses Catalog Management for some functions and may issue Catalog Management return codes. These consist of two bytes, a master return code, and a specific error code. Supplemental information may also be present, depending upon the particular message, but the first 2 bytes (hex) are most important. For example, each of the messages below has the same return code, X'080C', expressed in slightly different forms.

CADC100E ERROR HAS OCCURRED RTC=080C FC=003

CADC203E CATALOG ERROR OCCURRED. F/C=020A R/C=080C0000

CADT040W UNABLE TO ACCESS FILE CAICATL **** RTC=080C

CADT049S FATAL CAM ERROR, 08/0C0000 020A (DTOPENTR/11C)

The master return code 08 indicates that the error was experienced by the logical processing component. The specific error code 0C indicates a storage insufficiency (not enough main storage was available to satisfy a request during processing). Since main storage may become exhausted at any time if the virtual machine size parameter is not correct, the error may be reflected by any component, resulting in different messages. The return code will always be the same for the same Catalog Management failure.

Catalog Management return codes fall into two categories. If the master return code is X'08', the error occurred in the logical component. If it is X'0C', the error occurred in the physical component.

Return Codes 3–5


The return codes and their meanings are provided in the following table. If no User Action is indicated, the problem is most likely the result of storage corruption or a logic error. Collect diagnostic information and contact Computer Associates. The term 'catalog', as used below, applies to CAICATL, CAIAUDT, and DYNBCAT.

R/C Internal Meaning Likely Cause/User Action

'0804' INVALID ADDRESS OF CACB

'0808' INVALID FUNCTION CODE

'080C' NO FREE STORAGE AVAILABLE

Insufficient GETVIS available to process request. Increase partition GETVIS storage.

'0810' INVALID ADDRESS OF DSN

'0814' INVALID ADDRESS OF VOLSER

'0818' INVALID ADDRESS OF RBA

'081C' INVALID ADDRESS OF NEXTPL

'0820' INVALID ADDRESS OF BUFFER

'0824' INVALID BUFFER LENGTH

'0828' INVALID KEY LENGTH

'082C' INVALID LRECL

'0830' INVALID VOLUME SEQ. NO.

'0834' INVALID FILE SEQUENCE NO.

'0838' INVALID VERSION NUMBER

'083C' INVALID VAULT IDENTIFIER

'0840' INVALID CPL OPTIONS

'0844' INVALID CPL/FUNCT COMB.




'0848' INVALID COMB. TABLE

'084C' NO CATALOG TO ACCESS

JCL or user error. Check labels for catalog, FILEDEFs, logical unit assignments, and VTOC.

'0850' ENQUEUE FAILED DYNCAT DEQUEUE function required.

'0854' NO RECORD FOUND AT RBA

Possible catalog corruption. Check SHARE option for catalog; run BACKUP immediately.

'0858' NO PREVIOUS GET OR ADD

'085C' LOGICAL END-OF-FILE Record expected, but not found. Check catalog SHARE option; run BACKUP immediately.

'0860' INVALID RECORD ID Catalog has possibly been corrupted or not initialized. Check catalog SHARE option; run BACKUP immediately.

'0864' NO SPACE TO ADD RECORD

Catalog is full. Run BACKUP, enlarge extents and run RESTORE.

'0868' A LINK ALREADY EXISTS

'086C' DUPLICATE RECORD Possible catalog corruption. Check catalog SHARE option; run BACKUP immediately.

'0870' INVALID DATASET NAME

'0874' BUFFER TOO SHORT FOR REC.

Possible catalog corruption. Check catalog SHARE option; run BACKUP immediately.

'0878' GENERATION GAP

'087C' ERROR DURING OBTAIN FUNCT.

Bad return code from SVC 107.

'0880' INVALID DATASET INDEX REC.

'0884' PREMATURE END-OF-CHAIN

'0888' FILE SEQ. NOT FOUND Possible user error. Run SCRATCH.

'088C' NO MATCHING VOLUME FOUND

Return Codes 3–7



'0890' INVALID VOLUME INDEX REC.

'0894' PREMATURE END-OF-CHAIN

'0898' AUDIT ERROR OCCURRED

'089C' AUDIT EXIT GAVE BAD RTNCD

'08A0' INVALID CATALOG CNTRL REC.

User error likely. Check release level of system, assure that catalog has been initialized, and display catalog RBA 0. This return code will result if the logical unit used for the catalog is inadvertently assigned to the disk after the catalog has been initially located.

'08A4' RBA OUTSIDE FORMAT

Verify that there was not a concurrent update/delete of this record. This error may occur if the record was deleted or updated while simultaneously attempting to display.

'08A8' SAVER ERROR Error during attempt to add to or access SYSTEM GETVIS. Indicates insufficient SYSTEM GETVIS availability.

'08AC' INVALID INDEX RBA

'08B0' INVALID INDEX DISP

'08B4' INVALID INDEX NUMBER

Shown below are return codes issued by the Physical Access component:


'0C00' REAL PHYSICAL I/O ERRORS OCCURED. CHECK THE DATASET AND PACK FOR ERRORS. RESTORE FILES.

'0C04' INVALID ADDRESS OF RBA




'0C08' INVALID ADDRESS OF BUF1

'0C0C' INVALID ADDRESS OF BUF2

'0C10' INVALID ADDRESS OF CAB

'0C14' INVALID DEVICE ADDRESS

'0C18' INVALID DEVICE TYPE

'0C1C' INVALID CI SIZE

'0C20' INVALID EXTENT FOR CATALOG

Probable user error. Check labels, JCL, logical unit assignment, and VTOC. This return code will result if the logical unit used to access the catalog is inadvertently assigned UA or if the FILEDEF is missing.

'0C24' RBA IS OUTSIDE EXTENT

'0C28' NO FREE STORAGE AVAILABLE

'0C2C' INVALID FUNCTION CODE

'0C30' INVALID ADDR OF EXIT LIST

'0C34' INVALID ADDR OF WORK AREA

'0C38' GETVCE FAILED

Note: If code is not listed here, contact Computer Associates Technical Support.

Return Codes 3–9

CICS Abend Codes

CICS Abend Codes The following CICS ABEND codes may be received from the Computer Associates online interface.

Code Reason Action

CATR The online interface was initiated without a valid TRANSID code. Valid codes are currently DYNT, SCHD and SNTL.

Correct and retry.

CAPR The online interface was initiated but not all required programs were in the CICS PPT.

Consult the appropriate online interface documentation, correct the PPT and retry.

CAST There is insufficient CICS subpool storage to satisfy the online interface's storage request.

Increase the size of the CICS subpool and retry.

CALG An internal logic error has occurred.


CAXT An error was encountered during a CICS SETEXIT request.


CAAB The Catalog Access Subtask has abended.

Retrieve the dump produced on SYSLST and contact Computer Associates.

SN01 The length operand of the CICS exec link program (CASE071) is not connected.

Refer to the

CA-TOP SECRET/VSE Systems Programmer Guide for more information.


IUCV Function Codes

IUCV Function Codes

Code Reason

00 OPEN IUCV APPLID

04 CLOSE IUCV APPLID

08 CONNECT TO IUCV APPLICATION

0C ACCEPT IUCV APPLID

10 SEND BROADCAST MSGS TO IUCV APPLIDS

14 SEND MESSAGE TO IUCV APPLID

18 RECEIVE MESSAGE FROM IUCV APPLID

1C REPLY TO MESSAGE FROM APPLID

20 PURGE A MESSAGE SENT TO APPLID

24 REJECT MESSAGE FROM APPLID

28 SEVER A PATHID

2C QUIESCE A PATHID

30 RESUME A PATHID

34 TEST STATUS CONNECT REQUEST

38 TEST STATUS OF MESSAGE

3C LOCATE FIRST MSG (IPARML RETURNED)

40 LOCATE NEXT MSG (IPARML RETURNED)

44 INTERNAL FUNCTION-SET TRACE

48 UNUSED AT THIS TIME

4C UNUSED AT THIS TIME

Task Manager Return Codes The following return codes are produced by the Task-Manager:

000 Command processed successfully

004 Attempt to load an active product

008 Invalid Task Manager command

999 Invalid CP/CMS command

Return Codes 3–11

Event Codes

Event Codes The following pages list the event codes assigned to CA-Dynam products. The products and the codes are listed alphabetically.

CA-Dynam/D Event Codes BGDG Back level GDG deletion

CLOS Disk file closed

CNCL Job cancellations

EOV EVENT NOT FOUND

OPAL Operator reduced allocation

OPEN Disk file open

PDEL Permanent data set delete response

PSWD Incorrect password entered

RECD Space recovery delete response

UDOC Undocumented/Unknown audit event

UTIL DYNAM/D Utility command audit entry

VEQV V=volser response entered

CA-Dynam/FI Event Codes GENL DYNAM/FI accepted for processing

RBLK Invalid blocksize

RDEV Unsupported device in DTF

RDTF Unsupported DTF feature

RIGN Ignore option specified

RILU Invalid logical unit

RLBL Unsupported label type

RLRC Invalid logical recored length

RRFM Unsupported or invalid Recfm

UTIL DYNAM/T Utility command audit entry


Event Codes

CA-Dynam/T Event Codes ACPT ACCEPT response entered

ALTR ALTER response entered

CLOS Tape file closed

CNCL Job cancellations

EOV Tape file has gone to end of volume

FUNC D/T tape forced uncontrolled

NLDP Tape opened off Load Point

OPEN Tape file open

RELS RELEASE response entered

RRUN RERUN response entered

SCRT DYNCAT SCRATCH command

UADD DYNCAT ADD command

UALT DYNCAT ALTER command

UDEF DYNCAT DEFINE command

UDEL DYNCAT DELETE command

UDOC Undocumented/Unknown audit event

UTIL DYNAM/T Utility command audit entry

Return Codes 3–13