CA FAVER™ VSAM Data
Protection
Message Reference Guide
r4.5
This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to
as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This
Documentation is proprietary information of CA and may not be copied, transferred, reproduced, disclosed, modified or
duplicated, in whole or in part, without the prior written consent of CA.
If you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make
available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with
that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.
The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable
license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to
certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or 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 YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE,
DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST
INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE
POSSIBILITY OF SUCH LOSS OR DAMAGE.
The use of any software product referenced in the Documentation is governed by the applicable license agreement and such
license agreement is not modified in any way by the terms of this notice.
The manufacturer of this Documentation is CA.
Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions
set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or
their successors.
Copyright © 2011 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to
their respective companies.
CA Technologies Product References
This document references the following CA Technologies products:
■
CA Disk™ Backup and Restore (CA Disk)
■
CA Extend™/DASD VSAM Compression (CA EXTEND/DASD)
■
CA FAVER™ VSAM Data Protection (CA FAVER)
■
CA VSAMAid™ VSAM Tools (CA VSAMAID)
Contact CA Technologies
Contact CA Support
For your convenience, CA Technologies provides one site where you can access the
information that you need for your Home Office, Small Business, and Enterprise CA
Technologies products. At http://ca.com/support, you can access the following
resources:
■
Online and telephone contact information for technical assistance and customer
services
■
Information about user communities and forums
■
Product and documentation downloads
■
CA Support policies and guidelines
■
Other helpful resources appropriate for your product
Providing Feedback About Product Documentation
If you have comments or questions about CA Technologies product documentation, you
can send a message to [email protected].
To provide feedback about CA Technologies product documentation, complete our
short customer survey which is available on the CA Support website at
http://ca.com/docs.
Contents
Chapter 1: Introduction
7
Chapter 2: Messages
9
GV Messages ................................................................................................................................................................ 9
GVA Messages ............................................................................................................................................................ 62
GVCAT Messages ........................................................................................................................................................ 70
IC Messages ................................................................................................................................................................ 75
Chapter 3: Condition Codes and User Abends
79
CA FAVER Condition Codes ........................................................................................................................................ 79
CA FAVER User Abends .............................................................................................................................................. 80
Contents 5
Chapter 1: Introduction
This guide contains messages, return codes, and abend codes issued by CA FAVER. The
messages are listed alphanumerically and the return codes and abend codes are listed
numerically. The one-letter code at the end of each message gives you additional
information. Following are the one-letter codes used in this guide:
E
Indicates that an error has occurred and processing terminates with a return code
of 16 if ABEND=NO is set, or a user abend equal to the install parameter ABCODE if
ABEND=YES is set.
I
Indicates an informational message that does not affect normal operation. This
message indicates values read from control statements, determined from the
environment, or calculated by the program.
W
Indicates that something has gone wrong (warning), but it is not serious enough to
stop processing. The value assumed by CA FAVER may not be causing the expected
execution. You should examine these messages and correct the problems.
Chapter 1: Introduction 7
Chapter 2: Messages
This section lists the messages issued by CA FAVER.
This section contains the following topics:
GV Messages (see page 9)
GVA Messages (see page 62)
GVCAT Messages (see page 70)
IC Messages (see page 75)
GV Messages
GV008
VERIFY(Y/N) RESTORE - entryname
Reason:
entryname: Name of cluster or alternate index to be restored.
RVER has been specified on the RESTORE card, requesting that the operator be notified
that a cluster is to be restored. A Y reply allows the RESTORE to continue; a reply of N
bypasses the restore of this cluster and proceeds to the next.
GV010
SYNTAX ERROR MARKED BY 'X'
GV010
UNKNOWN INPUT
Reason:
A parameter is specified incorrectly. An X will appear immediately below the incorrect
parameter. This error is typically caused by a misspelled or incomplete parameter.
Chapter 2: Messages 9
GV Messages
GV011
ddname DD STATEMENT MISSING
Reason:
ddname: A ddname specified in a parameter.
The ddname used in a CAT=, TAPE=, MERGIN=, FVROUT=, or OUTDD= statement is
missing.
GV011
MISSING parameter
Reason:
parameter: Name of the missing parameter.
The indicated control statement type is required but was not found in the input data.
GV012
ERROR IN CATDEF=
Reason:
The catalog data set name does not follow the equal sign (=), is too long, or is not
followed by a proper delimiter. The password does not immediately follow the slash (/),
is too long, or is not enclosed in quotation marks when required.
GV013
ERROR IN FVRIN=
Reason:
Nothing follows the equal sign (=); a parameter is misspelled; or a ddname is too long or
separated with an improper delimiter.
GV014
ERROR IN VOLUME=
Reason:
Nothing follows the equal sign (=), a volser is too long or not separated by a comma (,),
or expected continuation of the card was not found.
10 Message Reference Guide
GV Messages
GV015
ERROR IN CLUSTER NAME
Reason:
Entryname is too long or does not follow the equal sign (=); a parameter is misspelled or
too long, or expected continuation was not received. A generic name is used with
DEFINED or REUSE.
GV017
ERROR IN AMS INPUT
Reason:
An invalid cluster component is specified, a blank card, or balanced parentheses were
found.
GV019
PREMATURE EOF ON INPUT
Reason:
EOF on SYSIN was encountered before adequate statements to begin execution were
read.
GV021
DUPLICATE CLUSTER NAMES
Reason:
This cluster has already been specified on a previous cluster name card.
Chapter 2: Messages 11
GV Messages
GV031
OUTDD
GV051
VOLUME action ERROR volser
Reason:
action: The word "EXPORT" if using CA FAVER. The word "COLLECT" if using CA VSAMAID
without CA FAVER.
volser: The volume used in a VOLUME= statement.
A volume could not be allocated or the VVDS could not be opened. Exporting or
collecting continues with the next volume.
GV052
ALIAS NOT FOUND - alias
Reason:
alias: High level qualifier of a cluster name.
An alias could not be found in the master catalog. The user catalog this cluster is in
cannot be found. This, and the other cluster with the same alias, are not exported.
GV053
NAME NOT FOUND IN CATALOG - entryname
Reason:
entryname: Cluster or alternate index name.
An entry specified on a CL= statement was not found in the catalog. The name is
misspelled, the entry does not exist, or the name is not that of a cluster or alternate
index.
12 Message Reference Guide
GV Messages
GV054
NO MATCH ON GENERIC ENTRY - entryname
Reason:
entryname: Generic entryname
No data sets were found matching the generic entryname specified on a CL= statement.
The generic entryname is specified incorrectly or there are no data sets matching the
generic entryname.
GV057
CLUSTER NOT PROCESSED - entryname
Reason:
entryname: Cluster or alternate index not found.
The cluster identified by entryname was specified on a cluster name card but was not
found. It was to be restored, excluded, compared, or have AMS input, but it was not on
the input file.
Or the cluster was empty, and REMP was not specified on the RESTORE card.
GV059
DDNAME NOT FOUND - ddname
Reason:
ddname: ddname not found.
The ddname specified in a CAT=, TAPE=, FVRIN= or cluster name parameter was not
found. CA FAVER terminates.
Also, a CA FAVER DD card (SNAPDD, FVRVOLS, FVRCLDD) may not have been included. If
the DD card is required, CA FAVER terminates. Otherwise, the CA message is issued and
execution continues.
GV061
ERROR IN AMS CLUSTER NAME
Reason:
In the AMS input for this cluster, the cluster name is specified incorrectly. RESTORE
bypasses this cluster and continues to the next. See "Define Cluster" in the IDCAMS
manual for the proper syntax.
Chapter 2: Messages 13
GV Messages
GV062
ERROR IN AMS MASTER PW USING OLD PW
Reason:
In the AMS input for this cluster, the master password is specified incorrectly. RESTORE
uses the password, if any, from the input file. See "Define Cluster" in the IDCAMS
manual for the proper syntax.
GV102
CLUSTER PRIMED
Reason:
The cluster was primed. CA FAVER will prime clusters that, when exported, had all
records deleted. The practice of priming a cluster is often used to allow a cluster to be
open for update when it actually has no records in it.
GV103
UNABLE TO USE SNAP RC= rc
Reason:
rc: SNAP macro return code.
CA FAVER attempted to use the SNAPDD data set but was unsuccessful. The return code
from the SNAP macro is documented in the Supervisor Services and Macro Instructions
manual. If the return code is FF, this is a CA FAVER supplied value and indicates that
SNAP was to be used, but the SNAPDD DD card was not found.
GV104
OPEN FOR OUTPUT
Reason:
This cluster is currently open for output by another task or the open indicator flag in the
catalog was left on due because of a system crash. EXO (EXport Open) was specified and
the cluster is exported.
GV104
OPEN FOR OUTPUT WHEN EXPORTED
Reason:
This cluster was exported with the EXO option in effect. See EXO for an explanation of
its use.
14 Message Reference Guide
GV Messages
GV105
EMPTY CLUSTER action DEFINITION
Reason:
action: The word "EXPORTING" if using CA FAVER. The word "COLLECTING" if using CA
VSAMAID without CA FAVER.
The cluster has no data in it, but its catalog definition is exported or collected and a
subsequent restore will redefine it.
GV105
EMPTY CLUSTER RESTORING DEFINITION
Reason:
Specify REMP on the RESTORE card to redefine an empty cluster.
GV106
OPEN FOR OUTPUT, NO EXO, NOT action
Reason:
action: The word "EXPORTED" if using CA FAVER. The word "COLLECTED" if using CA
VSAMAID without CA FAVER.
This cluster is currently open for output by another task or the open indicator flag in the
catalog was left on because of a system crash. EXO was not specified and the cluster is
not exported. Export or collection continues with the next cluster.
GV107
CI SPLIT IN PROGRESS
Reason:
The busy flag in a control interval definition field is on, indicating a control interval split
has not completed. If this occurs when the cluster is open and being used, the backup
file will not match the input exactly because update activity has not been quiesced.
When the cluster is closed and this message is issued, a CI or CA split did not complete,
and the cluster is damaged.
Chapter 2: Messages 15
GV Messages
GV108
RECORD COUNTS DISAGREE CATALOG= nnn
Reason:
The record count maintained during export does not agree with the record total
(records inserted for a RRDS) field from the catalog. This is an informational message
only. The counts maintained in the catalog are only valid when a close successfully
completes for the cluster. The purpose of this message is to indicate that this cluster
was not properly closed at some point in time.
GV109
WARNING - RECORD SIZE GREATER THAN DEFINED MAXIMUM RECORD SIZE
RECORD SIZE FOUND = xxxxx
DEFINED MAX RECORD SIZE = xxxxx
Reason:
The record size is greater than the defined maximum record size. CA FAVER can EXPORT
the cluster. Upon RESTORE, you need to add an AMS override to change the MAXRECSZ
to the size indicated in the error message, in order for the file to redefine and RESTORE
properly. This condition can occur when CI-level processing has been used on the file.
GV110
DELETED CLUSTER NOT CARRIED FORWARD - entryname
Reason:
entryname: Cluster or alternate index name.
NOCARRY was specified for a merge function. The cluster in the message was deleted
since the last merge/export, and it is not carried forward on the export file.
GV111
CONDITION CODE SET TO nnn
Reason:
nnn: New highest condition code value.
The highest condition code for the job has been reset by a previous error message.
16 Message Reference Guide
GV Messages
GV112
NOT UPDATED SINCE LAST action - DROPPED - entryname
Reason:
action: The word "EXPORT" if using CA FAVER. The word "COLLECT" if using CA VSAMAID
without CA FAVER.
entryname: Cluster name.
DROP was specified for a merge function. The cluster in the message has not been
updated since the last merge/export or collection and it is not written to the output.
GV113
INDEX FULL - CA SPLIT REQUIRED
Reason:
An index control interval was filled with keys before the data control area was filled with
records; the index CI size is too small. After each PUT, RESTORE will print this message if
the RPL error code is 16, indicating that the index is full.
GV115
DATA SET MIGRATED - HAS BEEN SUCCESSFULLY RECALLED FOR EXPORT - dsn
Reason:
User had requested that VSAM files that were migrated by HSM/ABR to be exported.
This is an informational message to say the data set has been successfully recalled
before exporting.
GV116
OUTDD AND CILEVEL ARE MUTUALLY EXCLUSIVE, OBJECT NOT WRITTEN TO OUTDD
Reason:
The client has specified the OUTDD to get a sequential "flat" file copy of the cluster, but
the client has requested the CILEVEL processing parameter for GVEXPORT. When
CILEVEL is requested, ESDS clusters are processed at the control interval level. Logical
data records are not processed, so it is impossible to create the output necessary for
OUTDD. This file cluster is not copied to OUTDD, but processing continues.
Chapter 2: Messages 17
GV Messages
GV117
NODATA IN EFFECT, NO DATA WRITTEN
Reason:
Informational. The EXPORT parameter NODATA was specified. The definition of the
cluster associated with this message was written to the export output, but no cluster
data has been written.
GV118
NOAIX IN EFFECT, NO DATA WRITTEN
Reason:
Informational. The EXPORT parameter NOAIX was specified. The definition of alternate
indexes and any paths associated with this message have been written to the export
output, but no alternate index data has been written.
GV120
DEFAULTS: parm1, parm2...parmn
Reason:
Informational. The GVPARMS utility can be used to assign many default parameter
settings. This message is issued at the beginning of export processing to display the
defaults in effect, since they may differ from the documented defaults.
GV121
DEFAULTS: parm1, parm2...parmn
Reason:
Informational. The GVPARMS utility can be used to assign many default parameter
settings. This message is issued at the beginning of restore processing to display the
defaults in effect, since they may differ from the documented defaults.
GV130
DDNAME ddname, EXPORTING TO DSN=dsn VOL=volser
Reason:
Informational. This message is issued when a new export output data set is opened. It
identifies the data set name to which the export is being written. It also includes the
initial volume serial number of the output data set. See the GV131 message also.
18 Message Reference Guide
GV Messages
GV131
DDNAME ddname, EXPORT COMPLETE TO DSN=dsn VOL=volser,...,volser
Reason:
Informational. This message is issued when a new export output data set is closed. It
identifies the data set name to which the export was written. It also includes all the
volume serial numbers of the output data set. This message can be paired to message
GV130 that was issued earlier in the export process.
GV132
FAVER SYSTEM DEFAULTS MODULE (FVDFAULT) NOT FOUND
Reason:
Warning. The CA FAVER system defaults are maintained in the FVDFAULT load module.
This module is created and maintained by the GVPARMS utility. This message indicates
the module cannot be loaded from the STEPLIB or the LINKLIST. Processing continues
with the documented defaults, however, some subsequent processing may require the
presence of this module. In that case, a failure occurs later in processing.
Action:
Run the GVPARMS utility to create a new FVDFAULT module. Running GVPARMS with
the one control statement "RESET" causes an FVDFAULT module to be built that reflects
the documented defaults.
GV133
RECALL PROCESSING REQUESTED, BUT STORAGE ENVIRONMENT CANNOT BE
DETERMINED
Reason:
Error. The client has requested RECALL processing by using the RECALL, HSM, DMS, or
ABR export parameters. RECALL processing requires the FVDFAULT module to be
available. See the GV132 message issued previously in this same execution of
GVEXPORT.
Chapter 2: Messages 19
GV Messages
GV134
FAVER SYSTEM DEFAULTS MODULE (FVDFAULT) IS REQUIRED FOR RECALL
PROCESSING
Reason:
Error. The client has requested RECALL processing by using the RECALL, HSM, DMS, or
ABR export parameters. RECALL processing requires the FVDFAULT module to be
available. See the GV132 message issued previously in this same execution of
GVEXPORT.
GV135
RECALL CANNOT BE PERFORMED WHEN SGMR=NONE
Reason:
Warning. The client has requested RECALL processing by using the RECALL, HSM, DMS,
or ABR export parameters. The current system defaults settings indicated SMGR=NONE.
Recall processing is not possible. Processing continues. Either the RECALL parameter
should be removed from the GVEXPORT control statements or the GVPARMS utility
should be used to define the desired storage manager.
GV136
EXPECTED CONTROL STATEMENT CONTINUATION NOT RECEIVED
Reason:
Error. While examining control statements, an incomplete parameter was encountered.
Processing terminates.
GV137
NO CONTROL STATEMENTS PRESENT, NO UPDATE WILL BE ATTEMPTED
Reason:
Informational. The GVPARMS utility was run with no control statements at all. This has
the effect of displaying the current CA FAVER system defaults without updating them in
any way. This message ensures the client that no updates are attempted.
GV138
CONTROL STATEMENT PROCESSING BEGINS
Reason:
Informational. The GVPARMS utility has input to process and attempts to update the CA
FAVER system defaults if no errors are detected.
20 Message Reference Guide
GV Messages
GV139
CONTROL STATEMENT PROCESSING COMPLETE, n ERRORS DETECTED
Reason:
Informational. GVPARMS has processed all control statements. n can be a number or
the word "NO". If errors are detected, no update is attempted. Even if errors have been
detected, processing continues to the analysis phase.
GV140
PARAMETER keyword MUST BE IN THE RANGE OF n to nnnn
Reason:
Error. Where keyword is one of GVPARMS control parameters that have a range of
numeric values. n is the minimum and nnnn is the maximum value of the range.
GV141
DUPLICATE PARAMETER
Reason:
Error. The identified keyword has already been specified in a previous control
statement. It cannot be specified again.
GV142
MUTUALLY EXCLUSIVE WITH parm1
Reason:
Error. The identified keyword cannot be specified with another keyword that has
already been encountered. parm1 is the previous keyword with which the current
keyword conflicts.
GV143
ANALYZING FAVER SYSTEM DEFAULTS
Reason:
Informational. After all control statements have been processed, GVPARMS analyzes the
resulting system default settings to see if any new settings may be introducing a conflict
with other settings that have not been changed in this execution. This message signals
the beginning of the analysis phase.
Chapter 2: Messages 21
GV Messages
GV144
OBSERVATION: notes
Reason:
Informational. During the analysis phase, GVPARMS may produce observation messages
the client may find helpful. Changing a default setting may require changes to the
export or restore job streams. These observations are intended to prevent problems in
export and restore processing.
GV145
CONFLICT IN PARAMETERS: parm1, parm2
Reason:
Error. During the analysis phase, two defaults have been set that are mutually exclusive
with one another. This can arise when one of these parameters was changed during the
execution of GVPARMS, while the other retains its value by virtue of not being updated.
GV146
ASSIGNED VALUE EXCEEDS MAX LENGTH OF n
Reason:
Error. Certain GVPARMS parameters can be assigned text values. The text is too long.
GV147
SUBSCRIPT EXCEEDS MAX VALUE OF n
Reason:
Error. Certain GVPARMS parameters, such as SMGRDDN, are subscripted to create
arrays of values. The array is limited in size. n defined the maximum value of the
subscript.
GV148
EXPECTED SUBSCRIPT VALUE OF n
Reason:
Error. When defining subscripted parameters to GVPARMS, the values must be assigned
starting with subscript value of 1. For example, to specify "SMGRDDN(2)=DD2", one
must first specify "SMGRDDN(1)=DD1" in a given execution of GVPARMS.
22 Message Reference Guide
GV Messages
GV149
ANALYSIS OF FAVER SYSTEM DEFAULTS COMPLETE, n ERRORS DETECTED
Reason:
Informational. GVPARMS has analyzed the system defaults. n can be a number or the
word "NO". If errors are detected, no update is to be attempted. Even if errors have
been detected, processing continues to the reporting phase.
GV150
DETAILED REPORT OF FAVER SYSTEM DEFAULTS FOLLOWS
Reason:
Informational. This signals the beginning of the reporting phase. All of the CA FAVER
system default settings are displayed on the following page. This report is produced
even if errors have been detected.
GV154
WARNING - SMGRDSN(n)=dsn - locate_failure
Reason:
Informational. As part of the analysis phase, the SMGRDSN array elements are verified
against the system catalog. If the value assigned to a SMGRDSN array element is not
found in the system catalog, this message is issued. dsn is the value assigned to the nth
SMGRDSN entry and locate_failure may be one of the following:
- DATA SET NOT FOUND IN CATALOG
- CATALOG LOCATE FAILED RC=rc
where rc is an unexpected and unanticipated return code from catalog management.
GV155
WARNINGS DETECTED DURING PROCESSING – UPDATE PROCEEDING
Reason:
Informational. All control statements have been processed and all analysis has been
completed. No errors have been detected, but warning messages have been issued.
Processing continues to the update phase. The warnings may indicate problems will
arise during export or restore processing using the current system default settings.
Review the output carefully to determine whether or not the warnings may actually
cause a problem.
Chapter 2: Messages 23
GV Messages
GV156
ERRORS DETECTED DURING PROCESSING
Reason:
Informational. All control statements have been processed and all analysis has been
completed. Either control statement errors or analysis errors have been detected. The
update phase is skipped. Review the output, correct the error conditions, and attempt
the update again.
GV157
FAVER SYSTEM DEFAULTS UPDATED FAILED - RC=n
Reason:
GVPARMS attempted to update the CA FAVER system defaults module, FVDFAULT, but
an error occurred. Review the messages immediately preceding this message for more
details.
GV158
FAVER SYSTEM DEFAULTS NOT UPDATED
Reason:
Informational. GVPARMS has not attempted to update the CA FAVER system defaults
module, FVDFAULT. This is a result of providing no control statements. This execution of
GVPARMS has provided a display of the current CA FAVER system default settings, but
has not changed them in any way.
GV159
FAVER SYSTEM DEFAULTS SUCCESSFULLY UPDATED
Reason:
Informational. GVPARMS has accepted all control statements. All analysis tests were
applied and no errors were detected. The CA FAVER system defaults module, FVDFAULT,
has been updated with the new system default settings.
24 Message Reference Guide
GV Messages
GV160
INSUFFICIENT STORAGE FOR BUFFERS, INCREASE REGION SIZE
Reason:
Error. GVPARMS has accepted the all control statements. All analysis tests were applied
and no errors were detected. GVPARMS attempted to update the CA FAVER system
defaults module, FVDFAULT, but insufficient main storage was available to accomplish
the update process. The update has been abandoned. Increase the region size and try
the update again.
GV161
FAVER SYSTEM DEFAULTS COULD NOT BE SAVED
Reason:
Error. GVPARMS has accepted the all control statements. All analysis tests were applied
and no errors were detected. GVPARMS attempted to update the CA FAVER system
defaults module, FVDFAULT, but an error occurred during the update process. The
update has been abandoned. Review the GV167 message that follows this message for a
more detailed explanation of the error condition.
GV167
ERROR OCCURRED WHILE UPDATING SYSLIB, FAILING FUNCTION: binder_function
RET=return_code RSN=reason_code
Reason:
Error. This message accompanies GV161 to provide a more detailed explanation of the
failure that occurred. GVPARMS uses the DFSMS Binder API to update the FVDFAULT
module in the library defined by the SYSLIB DD statement. The return_code and
reason_code values represent the return code and the reason code from the DFSMS
Binder function that failed. binder_function can be any one of the following:
GETBUF
Acquire buffers - The GV160 message will precede this message.
STARTD
Start a dialog with the Binder.
CREATEW
Create a "workmod".
PUTD(E)
Put ESD data into the "workmod".
Chapter 2: Messages 25
GV Messages
PUTD(T)
Put TEXT data into the "workmod".
PUTD(I)
Put IDR data into the "workmod".
PUTD(F)
Conclusion of the put sequence.
SAVEW
Save the "workmod" in SYSLIB. This is the most likely function to fail. The most
common causes of this failure are:
1.
The user is not authorized to update the SYSLIB data set.
2.
The SYSLIB data set is on a volume that is accessed as "read-only"
3.
The SYSLIB data set is full with no secondary allocation or needs to be
compressed
DELETEW
Delete the "workmod".
ENDD
End the Binder dialog.
FREEBUF
Free the buffers
A detailed explanation of the return and reason codes from the DFSMS Binder and their
meanings, see the IBM publication DFSMS/MVS Program Management in the section
titled "Using the Binder Application Programming Interface".
In all likelihood, GV168 followed by a sequence of GV169 messages will follow this
message. Review them carefully.
GV168
MESSAGES FROM DFSMS BINDER FOLLOW IN GV169 MESSAGES
Reason:
Informational. GVPARMS has accepted the all control statements. All analysis tests were
applied and no errors were detected. GVPARMS attempted to update the CA FAVER
system defaults module, FVDFAULT, but an error occurred during the update process.
GVPARMS uses the DFSMS Binder API to update the FVDFAULT module in the library
defined by the SYSLIB DD statement. The binder has generated messages that are
displayed in the GV169 messages that follow this message.
26 Message Reference Guide
GV Messages
GV169
BINDER: binder message
Reason:
Binder message is a message generated by the DFSMS Binder. The explanation of these
messages can be found in the IBM publication OS/390 VnRn MVS System Messages.
GV199
NO OBJECTS HAVE BEEN processtype
Reason:
After completing the search operations, no data sets matched the selection criteria. If
processtype is EXPORTED, then all EXPORT operations have been completed, but no
data was written to the FVROUT0 or FVROUT1 data sets. If processtype is SELECTED,
then all COLLECT operations have completed, but no data was written to the VSAMAID
TRENDS file.
GV200
USER EXIT NOT ALLOWED FOR SAVECOMP FILE
Reason:
Files that are exported with SAVECOMP option are stored in a specialformat using
DFSMSdss. CA FAVER terminates.
Correct the input and rerun.
GV201
COMPARE NOT ALLOWED FOR SAVECOMP FILE
Reason:
Files that are exported with SAVECOMP option are stored in a special format using
DFSMSdss. CA FAVER terminates.
Correct the input and rerun.
Chapter 2: Messages 27
GV Messages
GV202
THIS IS NOT A SAVECOMP ELIGIBLE FILE
Reason:
The SAVECOMP parameter was specified but the file is not an extended hardware
compressed VSAM file.
None. This is an informational message.
GV203
MERGE NOT ALLOWED FOR SAVECOMP FILE
Reason:
Files that are exported with SAVECOMP option are stored in a special format using
DFSMSdss. CA FAVER terminates.
Correct the input and rerun.
GV204
RETURN CODE nnnn FROM DFSMSDSS REFER TO DSSMSGDD
Reason:
DFSMSdss encountered a problem and cannot continue processing. CA FAVER
terminates.
Refer to DSSMSGDD for further information.
GV205
OUTPUT WRITTEN BY DFSMSDSS
Reason:
DFSMSdss is being used to write the output file.
GV206
INPUT READ BY DFSMSDSS
Reason:
DFSMSdss is being used to read the input file.
28 Message Reference Guide
GV Messages
GV207
DSSMSGDD NOT FOUND
Reason:
Files that are exported/restored with SAVECOMP option require a //DSSMSGDD DD
statement in the JCL. CA FAVER terminates.
Add the //DSSMSGDD DD statement to the JCL and rerun.
GV300
UNABLE TO OPEN CATALOG
Reason:
The catalog identified in previous messages could not be opened. EXPORT continues
with the next catalog.
GV301
ERROR READING CATALOG OR VVDS
Reason:
An error occurred while reading a catalog or VVDS identified in previous messages.
EXPORT continues with the next catalog.
GV302
UNABLE TO OPEN ENTRY - entryname
Reason:
entryname: Cluster or alternate index name.
A cluster or alternate index could not be opened. Preceding messages give the precise
reasons for the open failure.
GV303
ERROR READING CLUSTER
Reason:
A GV903 or GV905 message precedes this message and describes the problem
encountered with the cluster or alternate index. The fact that this cluster is partially
exported should be considered when restoring it.
Chapter 2: Messages 29
GV Messages
GV304
CATALOG TIME STAMP BACK LEVELED
Reason:
During a merge operation, the time stamp for a cluster is less in the catalog than in the
merge input file. The catalog time stamp should remain equal to the copy if no update
activity has occurred. If update activity has occurred, the catalog time stamp should be
higher. When the catalog time stamp is less, the update level of the merge in file cannot
be accurately determined. Export/merge continues with the next catalog.
GV305
ERROR READING MERGIN
Reason:
An error has occurred while reading the MERGIN file. The job is terminated.
GV306
ERROR OPENING mcds FILE - R15=cc RC=rc
Reason:
When trying to open the MCDS (user had requested the export of files that were
migrated by HSM with the RECALL parameter) an error occurred. mcds is the DD name
of the data set being opened. An explanation of the error is in the VSAM Programmer's
Guide with rc under the appropriate type (OPEN) and cc.
GV307
VSAM CBMM ERROR DOING function - R15=cc RC=rc
Reason:
An error occurred when trying to do a VSAM macro. function is either SHOWCB or
MODCB. Return codes are documented in the VSAM Programmer's Guide with rc under
the appropriate type (either SHOWCB or MODCB) and cc.
GV308
VSAM REQUEST ERROR READING mcds FILE - R15=cc RC=rc
Reason:
An error occurred when trying to read the MCDS file (user had requested the export of
files that were migrated by HSM with the RECALL parameter). mcds is the DD name of
the data set being read. Return codes are documented in the VSAM Programmer's
Guide with rc under the GET macro and cc.
30 Message Reference Guide
GV Messages
GV309
NO ENTRY FOUND FOR DATA SET IN MCDS - REPORTED MIGRATED IN CATALOG - dsn
Reason:
When trying to determine if a migrated file was originally VSAM (reading the MCDS),
there was no entry for this particular data set.
GV310
PREVIOUS ERROR OPENING MCDS - CANNOT RECALL - dsn
Reason:
A previous attempt to open the MCDS failed. See preceding GV306 message for the
reason the MCDS could not be opened.
GV320
EXPECTED DD NOT FOUND, DDNAME=ddname
Reason:
Error. The RECALL parameter was specified for EXPORT processing. GVEXPORT required
access to a CA Disk (DMS) storage manager data set. A GVPARMS entry for
SMGRDDN(n)=ddname was recorded in the FVDFAULT module. Since the corresponding
SMGRDSN(n) indicated no data set name, the DD named ddname is expected to be
present in the GVEXPORT JCL. Processing continues, but the CA Disk interface is marked
as disabled, so RECALL processing is not possible.
GV321
DYNAMIC ALLOCATION FAILED FOR dsn
Reason:
Error. The RECALL parameter was specified for EXPORT processing. GVEXPORT required
access to a CA Disk (DMS) storage manager data set. A GVPARMS entry for
SMGRDSN(n)=dsn was recorded in the FVDFAULT module. GVEXPORT attempted to
dynamically allocate this data set, but the allocation failed. Processing continues, but
the CA Disk interface is marked as disabled, so RECALL processing is not possible.
Chapter 2: Messages 31
GV Messages
GV322
DISK SYSTEM INTERFACE MODULE NOT FOUND
Reason:
Error. The RECALL parameter was specified for EXPORT processing. GVEXPORT required
access to the CA Disk (DMS) storage manager interface module, but the module was not
found. The interface module named "MI", was not in the STEPLIB or the system link list.
Either add the CA Disk product load library to the system link list, or concatenate it to
the STEPLIB out of which GVEXPORT is being executed. Processing continues, but the CA
Disk interface is marked as disabled, so RECALL processing is not possible.
GV323
DATASET HAS BEEN ARCHIVED, NOT BEING EXPORTED - dsn
Reason:
Informational. The NORECALL parameter was specified for EXPORT processing.
GVEXPORT identified the data set dsn as having been archived by the CA Disk (DMS)
storage manager. If RECALL was in effect, further analysis would have been performed
on this data set. If it represents a VSAM cluster, it would have been recalled for EXPORT
processing.
GV324
ARCHIVED FILE WAS RECALLED BUT WAS NOT VSAM - DOES NOT MATCH FILES ENTRY dsn
Reason:
Informational. The RECALL parameter was specified for EXPORT processing. GVEXPORT
retrieved information from CA Disk (DMS) concerning the data set dsn. It appeared to be
a VSAM cluster and was recalled for EXPORT processing. After it was recalled, the
system catalog records revealed that it was not a VSAM cluster. Processing continues.
GV325
NO ENTRY FOUND FOR DATASET IN FILES; REPORTED ARCHIVED IN CATALOG - dsn
Reason:
Informational. The RECALL parameter was specified for EXPORT processing. GVEXPORT
attempted to retrieve information from CA Disk (DMS) concerning the data set dsn. It
appeared to be archived by CA Disk, but no information was found in the CA Disk FILES
data set. Processing continues.
32 Message Reference Guide
GV Messages
GV326
PREVIOUS ERROR INTERFACING TO DISK - CANNOT RECALL dsn
Reason:
Error. The RECALL parameter was specified for EXPORT processing. A previous attempt
to access the CA Disk storage manager failed and the interface was marked as disabled.
RECALL analysis is not possible for the data set named dsn. Processing continues, but
the CA Disk interface remains marked as disabled, so RECALL processing is not possible.
GV327
DISK SUBTASK FAILURE - failure
Reason:
Error. The RECALL parameter was specified for EXPORT processing. An archived file was
encountered and an attempt was made to query the CA Disk FILES data set to determine
whether the archived file was VSAM. The CA Disk interface subtask unexpectedly failed.
failure can be one of the following:
■
ABEND Sxxx - A system abend occurred.
■
ABEND Snnnn - A CA Disk user abend occurred.
■
TERMINATED CC=nnnn - The CA Disk interface module encountered an unexpected
condition and terminated with an abend. nnnn is the condition code.
■
ATTACH FAILED RC=nn - The initial attempt to ATTACH the subtask failed. nn is the
ATTACH return code.
Action:
Processing continues, but the CA Disk interface is marked as disabled, so RECALL
processing is not possible.
GV501
SMS SUBSYSTEM IS NOT AVAILABLE
Reason:
Error. GVEXPORT required access to the DFSMS subsystem, but SMS was not available.
The SMS subsystem is either down or improperly defined. Processing terminates.
Chapter 2: Messages 33
GV Messages
GV502
STORAGE GROUP stgroup WAS NOT FOUND
Reason:
Error. The client specified STGROUP=stgroup in the GVEXPORT input control statements,
but the storage group named stgroup was not found in the current SMS configuration.
Processing terminates.
GV503
STORAGE GROUP stgroup CONTAINS NO VOLUMES
Reason:
Error. The client specified STGROUP=stgroup in the GVEXPORT input control statements.
The storage group named stgroup was found in the current SMS configuration, but it
had no volumes associated with it. Processing terminates.
GV504
STORAGE GROUP stgroup HAS NO VOLUME ELIGIBLE FOR USE ON THIS SYSTEM
Reason:
Error. The client specified STGROUP=stgroup in the GVEXPORT input control statements.
The storage group named stgroup was found in the current SMS configuration, but it
had no volumes that were eligible for use. Either its SMS system status or its OS/390
system status disqualified every volume. Processing terminates.
GV505
INSUFFICIENT STORAGE FOR SMS TO RETURN DATA, INCREASE REGION SIZE
Reason:
Error. GVEXPORT required access to the DFSMS subsystem, but SMS was not able to
return the requested information because there was not enough main storage. Increase
the region size and attempt to run GVEXPORT again. Processing terminates.
34 Message Reference Guide
GV Messages
GV506
STORAGE GROUP stgroup CANNOT BE USED – reason
Reason:
Error. The client specified STGROUP=stgroup in the GVEXPORT input control statements.
The storage group named stgroup was found in the current SMS configuration, but it
was not eligible for use. The storage group type must be "POOL". The SMS system status
must be ENABLE, QUINEW, or DISNEW. Either its SMS system status or its storage group
type disqualified it.
reason can be:
STATUS=status or
TYPE=nondisktype
status can be NOTCON, QUIALL, or DISALL.
nondisktype can be VIO, DUMMY, OBJECT, OBJBACK, or TAPE.
Processing terminates.
GV507
ERROR OCCURRED CALLING SMS SUBSYSTEM, FAILING FUNCTION: function RET=rc
RSN=rsn
Reason:
Error. GVEXPORT required access to the DFSMS subsystem, but SMS was not able to
return the requested information. function can be SUBSYS_CALL, GET_STGROUP, or
GET_VOLLIST. rc is the return code and rsn is the reason code. This message is not
expected to be seen by the client. Processing terminates.
GV510
nnn INELIGIBLE VOLUMES FROM STORAGE GROUP stgroup FOLLOW IN GV511
MESSAGES
Reason:
Informational. The client specified STGROUP=stgroup in the GVEXPORT input control
statements. The storage group named stgroup was found in the current SMS
configuration, but one or more of the volumes in that group are not eligible for use. nnn
is the number of ineligible volumes. The complete list of disqualified volumes will follow
in one or more GV511 messages. Processing continues.
Chapter 2: Messages 35
GV Messages
GV511
VOLS - volume(smsstat,osstat) volume(smsstat,osstat) ...
Reason:
Informational. This message always follows a GV510 message to provide details on the
SMS volumes that are not processed in the requested storage group. As each volume
was examined, either its SMS system status or its OS/390 system status disqualified it.
Each volume is displayed with its SMS system status and its OS/390 system status.
volume is an ineligible disk volume. smsstat is the SMS status of this volume. osstat is
the OS/390 status of this volume. Processing continues.
GV512
ALL VOLUMES IN STORAGE GROUP stgroup ARE ELIGIBLE FOR PROCESSING
Reason:
Informational. The client specified STGROUP=stgroup in the GVEXPORT input control
statements. The storage group named stgroup was found in the current SMS
configuration and all of the volumes in that group are eligible for use. When this
message is produced, neither the GV510 message nor the GV511 message is generated.
Processing continues.
GV513
nnn VOLUMES INCLUDED FROM STORAGE GROUP stgroup FOLLOW IN GV514
MESSAGES
Reason:
Informational. The client specified STGROUP=stgroup in the GVEXPORT input control
statements. The storage group named stgroup was found in the current SMS
configuration and at least one volume in that group is eligible for use. nnn is the number
of eligible volumes. The complete list of selected volumes will follow in one or more
GV514 messages. Processing continues.
GV514
VOLS - volume volume ...
Reason:
Informational. This message always follows a GV513 message to provide details on the
SMS volumes that are processed in the requested storage group. volume is an eligible
disk volume. Processing continues.
36 Message Reference Guide
GV Messages
GV600I
NO MATCHING CMPPRM ENTRY FOUND - NO COMPRESSION DATA COPIED TO
BACKUP.
Reason:
CMPPRM does not contain an entry for this data set. Either this data set is
uncompressed or some one deleted the CMPPRM entry. CA FAVER backed up the data
set but was unable to backup any compression data. If this data set is uncompressed, no
action is required. If this data set is compressed, recreate or restore your CMPPRM
entry.
GV601E
INVALID CMPPRM RECORD SIZE, CLUSTER NOT BACKED UP.
Reason:
There is a CMPPRM entry for this data set; however, the record length in the CMPPRM
entry does not match the record length in the data set. CA FAVER is unable to back up
this data set. This message accompanies message GV603E.
GV602E
INTERNAL ERROR. NON-ZERO TOKEN PASSED TO INIT FUNCTION.
Reason:
The caller passed an invalid parameter list to the CA FAVER - CA EXTEND/DASD interface
initialization routine. Call CA Technical Support for help.
GV603E
*** MAKE SURE THAT cmpprm data set name IS NOT CORRUPTED.
Reason:
This message accompanies GV601E. The message text contains the name of the
CMPPRM data set that contains the invalid record size. CA FAVER is unable to back up
this data set. Check the CMPPRM data set named in the message text. It is possible that
a user or a user program updated the CMPPRM entry. After you have restored
CMPPRM, the data set can be exported.
Chapter 2: Messages 37
GV Messages
GV604I
NO EXTEND/DASD DATA IN BACKUP. MATCHING CLUSTER ENTRY FOUND IN CMPPRM.
REMOVAL MAY BE NECESSARY.
Reason:
CMPPRM contains an entry for this data set, but CA FAVER found no compression data
on the EXPORT copy. Either the EXPORT data set is uncompressed, or you created it
before the CA FAVER - CA EXTEND/DASD interface existed. The CA FAVER RESTORE
function did not alter or delete the CMPPRM entry. If the data set is uncompressed,
delete or rename the CMPPRM entry so that you can access your data.
GV605E
COULD NOT RESTORE COMPRESSION TABLE. RESTORE BYPASSED FOR THIS CLUSTER.
Reason:
CA FAVER could not restore the compression table associated with the data set. The CA
FAVER message that accompanies this message lists the name of the data set. CA FAVER
cannot access or restore the data without this table. This problem is usually the result of
an X37 ABEND (that is, CMPTBL data set out of space). It can also happen if the CA
EXTEND/DASD global parameters are set incorrectly.
GV606E
MATCHING CMPPRM ENTRY FOUND, BUT type TABLE compression table name NOT
FOUND IN CMPTBL
Reason:
The CMPPRM entry for this data set contains a compression table name. The
compression table name type (either current or desired) is shown in the message text.
However, the compression table is not a member of CMPTBL. CA FAVER exported the
data set and issued a return code of 4. The backup copy is in compressed format but is
unusable without the compression table.
GV607I
NO EXTEND/DASD DATA ON BACKUP OR IN CMPPRM - ASSUMING DECOMPRESSED
BACKUP.
Reason:
CA FAVER was unable to find any CA EXTEND/DASD data on the backup copy or in the
CMPPRM data set. CA FAVER restored the data set as a normal uncompressed data set
and issued a return code of zero.
38 Message Reference Guide
GV Messages
GV608I
CMPPRM AND CMPTBL ENTRIES SUCCESSFULLY RESTORED FROM BACKUP
Reason:
CA FAVER successfully restored both the CMPPRM and CMPTBL entry for the current
data set.
GV609I
type TABLE compression table name ACQUIRED
Reason:
CA FAVER EXPORT successfully accessed the compression table named in the message
text. The compression table type (either current or desired) is also displayed. CA FAVER
copied this compression table to the backup data set.
GV610I
CLUSTER EXISTS IN CMPPRM, BUT IS NOT COMPRESSED.
Reason:
CMPPRM contains an entry for the data set listed in the preceding CA FAVER message.
The compression table name is either *MONITOR or *NONE. CA FAVER this data set as a
normal uncompressed data set (for example, it backed up the data set with no
compression information).
GV611E
COULD NOT RESTORE CMPPRM ENTRY. RESTORE BYPASSED FOR THIS CLUSTER.
Reason:
An error occurred when CA FAVER attempted to write the CMPPRM entry. CA FAVER
issued one of the following return codes.
4
The data set is uncompressed, so CA FAVER was able to restore it.
8
The data set is compressed, so CA FAVER was unable to restore it.
Chapter 2: Messages 39
GV Messages
Find the source of the CMPPRM error. If CMPPRM is out of space, see the CA
EXTEND/DASD VSAM Compression System Reference Guide for information on
increasing its space allocation.
If CA EXTEND/DASD is accessing the wrong CMPPRM data set or no CMPPRM data set,
check the data set names in the CA EXTEND/DASD setup parameters. See the CA
EXTEND/DASD VSAM Compression System Reference Guide for more information. In
addition, check the system catalog entry for the CMPPRM data set. Correct the error
and try again.
GV612I
COMPRESSION TABLE HAS NOT CHANGED SINCE BACKUP
Reason:
CA FAVER did not restore compression data from the backup copy because the data is
unchanged.
GV613I
DESIRED TABLE UPDATED TO MATCH CURRENT TABLE
Reason:
CA FAVER restored the data set and updated the desired compression table name so
that it matches the current compression table name. CA FAVER takes this action when
the backup copy of the data set is in compressed format but the desired compression
table name is *MONITOR or *NONE.
GV620
DATA IS COMPRESSED, EXTEND/DASD NOT IN SYSTEM THEREFORE FAVER WILL NOT
RESTORE DATA.
Reason:
Upon restoring, CA FAVER determined that the data on the backup file has the CA
EXTEND/DASD cipher and control information and that the data is compressed. Since CA
EXTEND/DASD is not in the system, CA FAVER does not restore the data since there is no
way to access the data in uncompressed format.
GV621
EXTEND/DASD INFORMATION ON TAPE BUT DATA NOT COMPRESSED - RESTORING.
Reason:
The CA EXTEND/DASD cipher and control information is on the backup file, but the data
itself is not compressed. This is just a warning. The data is restored.
40 Message Reference Guide
GV Messages
GV702
FAVER2/VSE INPUT DATA SET DETECTED
Reason:
The FAVER2 parameter was not specified, but the current reload has been directed to
an export copy that appears to have been made by FAVER2/VSE. The FAVER2 interface
has been activated automatically.
GV703
FAVER2/VSE TRANSPARENCY ACTIVE
Reason:
The FAVER2 transparency has been activated. The exported data set is expected to be in
FAVER2 format. If the transparency has been activated automatically, this message is
preceded by GV702. Otherwise, the transparency has been activated explicitly.
GV750
ERROR OPENING, GVOPEN RC=n,MEANING:explanation
Reason:
The FAVER export title could not be processed. The values of n and the corresponding
explanation are as follows:
16
CANNOT OPEN FVRFILE - Either the DD statement is missing or it defines a file that
is inconsistent with a FAVER export file format.
17
CANNOT OPEN DDNAME=ddname - The PARM=ddname option was used, but the
file whose DD name is ddname is either missing or is inconsistent with a FAVER
export file format.
18
CANNOT FIND CLUSTER=dataset - The entire FAVER export file was scanned, but
the data set named dataset was not found.
other
UNKNOWN - An unexpected return code was passed back from GVOPEN. This
information will be useful to CA Support in problem determination.
Chapter 2: Messages 41
GV Messages
GV751
Reason:
An unexpected error occurred reading the FAVER export file. The values of n and the
corresponding explanation are as follows:
19
PREMATURE END OF FILE - GVREAD encountered physical end of file when more
records were expected. A common cause of this would be not providing the
complete set of volumes on a multivolume FAVER export data set.
other
UNKNOWN - An unexpected return code was passed back from GVREAD. This
information will be useful to CA Support in problem determination.
GV800
EXTEND/DASD VSE COMPRESSION TYPE x DETECTED, DATA WILL BEDECOMPRESSED
Reason:
The input file has been compressed by CA Extend/DASD for VSE. The compression type
is designated by the value of "x". The reload process will decompress this file so that the
improved compression techniques of CA Extend/DASD for MVS may be employed.
GV801
CANNOT DECOMPRESS DATA SET EXPORTED USING CILEVEL
Reason:
The FAVER/VSE transparency is currently active. The data set to be reloaded was
compressed, but was also exported in CILEVEL. This is not currently supported.
Action:
Contact CA FAVER support for assistance in getting this data set restored.
42 Message Reference Guide
GV Messages
GV802
EXTEND/DASD/VSE DECOMPRESS FAILED, RECORD=n TYPE=x RC=rc - TERMINATING
Reason:
During a reload operation while decompressing a data set that was compressed by CA
Extend/DASD for VSE, an unexpected error condition arose. "n" is the current logical
record number with the file. "x" is the compression technique employed. "rc" is the
return code passed back from the VSE decompression routines.
Action:
If the file being reloaded was not created by CA FAVER for VSE or FAVER2 for VSE,
remove the XTNDCHK parameter and try the reload again. If this fails, the file may be
corrupted. CA support will help determine how to recover this file.
GV803
IDCAMS ERROR - RESTORE BYPASSED
Reason:
During the IDCAMS DEFINE CLUSTER portion of an auto-define an IDCAMS error was
detected. The IDCAMS output should be examined for any errors caused by AMS input
supplied by the user. If CA FAVER generated the erroneous parms, report the problem.
Normally, RESTORE continues with the next cluster, but if ESTOP was specified on the
RESTORE card, execution will terminate.
GV804
ALLOCATION ERROR - RESTORE BYPASSED
Reason:
Dynamic allocation for a sequential data set failed.
GV805
CANNOT DECOMPRESS VSE SYSTEM COMPRESSED DATA SET - RESTORE BYPASSED
Reason:
This data set has been compressed by VSE system compression and was Exported by
FAVER2. OS/390 and z/OS system compression is not compatible with VSE system data
compression. This data set cannot be decompressed in an MVS environment.
Chapter 2: Messages 43
GV Messages
GV806
CANNOT DECOMPRESS VSE TYPE X'xx' COMPRESSED DATA SET - RESTORE BYPASSED
Reason:
The FAVER/VSE transparency is currently active. The data set to be reloaded is
compressed, but this particular compression technique is not recognized. The
compression technique is identified by X'xx'. The data set cannot be restored.
Action:
Informational.
GV807
INSUFFICIENT REGION SIZE TO PROCESS COMPRESSED DATA SET - RESTORE BYPASSED
Reason:
Decompression requires an internal decompression buffer. The attempt to acquire this
buffer failed because there was not enough storage left in the region.
Action:
Increase REGION size and try the restore again.
GV808
UNABLE TO OPEN DD - ddname
Reason:
ddname: The file that cannot be opened.
The input data set indicated by ddname could not be opened.
GV809
DYNAMIC ALLOCATION FAILURE RC= xxxx SEE JOB LOG
Reason:
xxxx: Error reason code, documented in OS/390 SPL: Job Management.
A data set could not be allocated. An interpretation and reason for the error is displayed
in the JES job log as an IKJ prefix message. The IKJ message and its explanation in the
OS/390 message manual will provide adequate documentation to fix the problem.
44 Message Reference Guide
GV Messages
GV810
REMP NOT SPECIFIED, EMPTY DATA SET SKIPPED - DSN=cluster
Reason:
A cluster matching the client's specifications was found on the FAVER export data set.
Since REMP was not specified for the RESTORE operation, this cluster is skipped. This is
not counted as an unsuccessful restore.
Action:
To cause this cluster to be defined in the system where the RESTORE command is
processed, add the REMP parameter to the RESTORE command.
GV811
WARNING: EXTEND/DASD/VSE SHOWS COMPRESSION OFFSET OF x, USING y BASED
ON reason
Reason:
The values of reason can be:
■
KEY OFFSET AND LENGTH
■
XTNDOFF OVERRIDE
If "KEY OFFSET AND LENGTH" appears, this indicates a rare problem has been
encountered. This is a case where a cluster has been put under Extend/DASD/VSE
control and then later had its key length or key offset changed without updating the
control information in the Extend/DASD/VSE Control File. The data set is correctly
compressed, but the "offset to compression" value is recorded incorrectly. Since
FAVER/VSE and FAVER2 for VSE acquire this information from the Extend/DASD/VSE
Control File, the value of "hp3.x" reflects the original settings. Extend/DASE/VSE adapts
to this by detecting the correct starting point. This message indicates that CA FAVER is
adapting to the change in key length or key offset.
If "hp2.XTNDOFF OVERRIDE" appears, the XTNDOFF=y input parameter has been
specified to override the original setting.
Action:
If this message is followed by a GV813 message, then the value of "y" is correct.
If this message is followed by a GV812 message, compare the number of records that
appeared to be uncompressed in the GV812 message with the total record count
reloaded. If the number of records in the GV812 message matches the record count,
then there is a problem. Map the input tape with GVMAP using PARM-PRINT and
contact CA support for assistance in getting this file restored.
Chapter 2: Messages 45
GV Messages
GV812
WARNING: n RECORDS DID NOT APPEAR TO BE COMPRESSED
Reason:
The input file was originally exported from a VSE system by either FAVER/VSE or
FAVER2/VSE in compressed format. FAVER decompressed the data during the restore
process so it may be compressed by MVS services. Some or all records encountered
during the restore operation did not appear to be in compressed format.
Action:
If the number "n" represents a small percentage of the total records restored, there is
most likely no problem. Extend/DASD/VSE tolerates uncompressed records within the
compressed file. This situation can happen if the VSAM file was updated while
Extend/DASD/VSE was not active.
If the number "n" represents the entire file, there is a problem. Check to see if this
message is preceded with GV811. Map the input tape with GVMAP using PARM-PRINT
and contact CA support for assistance in getting this file restored. With the assistance of
CA support, use the XTNDOFF=parameter to set the correct offset to compression.
GV813
ALL RECORDS PROCESSED CONTAINED EXPECTED EXTEND/DASD/VSE COMPRESSION
PREFIX
Reason:
The input file was originally exported from a VSE system by either FAVER/VSE or
FAVER2/VSE in compressed format. FAVER decompressed the data during the restore
process so it may be compressed by MVS services. This message confirms that all
records were decompressed successfully.
GV898
EXIT LINKAGE ERROR - nn
Reason:
nn Error code:
01 Insert is the only valid return code after end of file.
02 Invalid return code.
46 Message Reference Guide
GV Messages
03 Modify or insert, no record length or address returned.
04 Insert is not allowed for an RRDS.
A RESTORE user exit error was detected. Following messages identify SNAP dumps for
the exit, the parameter list, and the current record.
GV899
ABEND ..sss... IN FAVER
Reason:
sss: The system abend code.
The CA FAVER STAE exit routine was entered due to an abend. Messages identifying
SNAP dumps for CA FAVER storage, GETMAINed areas, I/O areas, user exit storage, and
the STAE work area follow. The dump of the STAE work area contains PSW and general
register contents at the time of the abend. Its format is as follows:
Bytes
0
4
8
16
24
- 3
- 7
- 15
- 23
- end
=
=
=
=
=
Exit parameter list address.
Abend code.
PSW at time of abend.
Last problem program PSW.
Registers 0-15 at time of abend.
GV901
VSAM type ERROR R15=cc RC=rc AT addr
Reason:
type: OPEN -- An open macro was issued.
REQUEST -- SYNAD/LERAD entered for GET, PUT, or CLOSE
GMST -- GENCB, MODCB, SHOWCB, or TESTCB macro.
cc: The contents of register 15 in hex.
rc: The VSAM return code in decimal.
addr: The address within CA FAVER where the macro was issued.
An error occurred during execution of a VSAM macro. An explanation of the error is in
the VSAM Programmer's Guide, with rc under the appropriate type and cc.
Chapter 2: Messages 47
GV Messages
Where applicable, messages identifying SNAP dumps of the ACB, RPL, and the record
key follow.
When GV901 occurs during RESTORE, CA FAVER normally continues with the next
cluster. However, if ESTOP is specified on the RESTORE card, CA FAVER terminates. The
return codes should be examined for codes indicating missing DD cards, out of space
conditions, or sequence errors when keys are changed in a user exit.
GV902
I/O ERROR - ddname SYNADAF message
Reason:
ddname: Input file with the error.
message: SYNADAF message.
The SYNADAF macro is issued and its message buffer is printed.
GV903
EXCP ERROR READING component
Reason:
component: INDEX or DATA.
The ECB (Event Control Block) used to wait for the completion of an EXCP (EXecute
Channel Program) SVC indicates an error termination. Following the message is a
formatted dump of the IOB (Input Output Block) and the channel program. The IOB and
ECB are documented in the SPL: Debugging Handbook. Channel programs are
documented in the DFSMSdfp Advanced Services.
GV904
ACCESS DENIED - entryname
Reason:
entryname: Cluster or alternate index name.
A user written security exit will not allow a cluster to be read.
48 Message Reference Guide
GV Messages
GV905
VSAM STRUCTURE ERROR - error description
CORRUPT RDF
rdf error type AT LOCATION address
hex dump of rdf
Reason:
INVALID RDF PAIR -- Sometimes two RDFs are required to describe a record, and the
flags that pair them together are not correct.
SEGMENT OUT OF SEQUENCE -- The segments (first, intermediate, last) of a spanned
record were not found in the proper order.
UPDATE NUMBER INCORRECT -- The update number carried with each segment of a
spanned record does not match the update number in another segment of the same
record.
UNKNOWN RDF -- The flags telling what type of information is in the RDF are invalid.
RECORD COUNT INVALID -- A count type RDF has a count of zero.
LENGTH ERROR -- A length type RDF is zero or greater than will fit.
Chapter 2: Messages 49
GV Messages
GV906
COMPARE reason
INPUT RECORD - INPT=recadr,reclen ,BLOCK=blknbr
DISK RECORD - DISK=recadr,reclen, RECORD=recnbr
INPT SLOT=islot DISK SLOT=dslot
INPUT RECORD FOLLOWS
dump of record
DISK RECORD FOLLOWS
dump of record
Reason:
A COMPARE command has found a discrepancy between the file on disk and the backup
file. The disk file may have been updated since the EXPORT command was performed. If
you are sure that the file has not changed, contact CA FAVER support immediately for
assistance.
Action:
Reason why the files do not compare can be:
INPT EOF
Ran out of input data while more data exists in compare file
LENGTH
The length of the input and compare records does not match
CONTENT
The data records do not match
SLOT NUM
The corresponding slot numbers do not match
DISK EOF
Ran out of compare file data while more data exists in input file
recadr
Address of the record in memory
reclen
Length of the record in memory
blknbr
Block number on the input tape where the occur was encountered
50 Message Reference Guide
GV Messages
recnbr
Logical record number within the compare file where the error was encountered.
If the error reason is SLOT NUM, then the slot number will also appear in this message.
islot
Slot number from the input tape
dslot
Slot number in the compare file
GV907
INPUT LOGICAL ERROR -x BLOCK=9999999
CL=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Reason:
While restoring a data set, an unexpected condition was encountered. The error code
describes the problem more precisely.
x is the error code:
1
Block sequence error
2
Incorrectly spanned record
3
Spanned record length inconsistent with block length
4
Total block count does not match block count in trailer record
5
RDW in error
6
Wrong length record
This is most likely the result of processing a multivolume input tape data set where
either the tape volumes have been given to GVRESTOR in the wrong order or a tape
volume has been omitted from the list.
Chapter 2: Messages 51
GV Messages
GV908
COMPRESSION ERROR - type
ERROR CODE=xxxxxxxx REASON CODE=xxxxxxxx
Reason:
During an EXPORT operation, a data set compressed with DFSMS compression services
was encountered. GVEXPORT was attempting to decompress the data when the error
occurred.
type can be:
INITIALIZING
Failure occurred during open processing
DECOMPRESSING
Failure occurred while attempting to decompress data
TERMINATING
Failure occurred during close processing
REBLOCKING
Failure occurred when attempting to add a decompressed to the current internal CI
The error code and reason code are from DFSMS compression services.
GV909
clname PARTIALLY EXPORTED
Reason:
During the RESTORE process, GVRESTOR unexpectedly came to end of file on the input
tape. Either the EXPORT job that created this tape failed before it completed the
EXPORT or the export copy was written to multiple tape volumes and not all of those
volumes were given to GVRESTOR.
GV910
DFSMS COMPRESSION SERVICE NOT AVAILABLE
Reason:
The file being exported is compressed. The DFSMS compression services are required to
decompress it. Since they are currently not available, this file cannot be exported.
Action:
When the DFSMS compression services are started, run this export again.
52 Message Reference Guide
GV Messages
GV911
FILE TYPE=NON-CI-FORMAT NOT SUPPORTED. DSN=datasetname-RESTORE BYPASSED
Reason:
The data set named is a VSE library that has been exported with FAVER2. This type of
data set cannot be restored into an OS/390 or z/OS environment.
GV912
EXCP ERROR READING component
GV912
BLKSIZE MIN=minblk MAX=maxblk
GV912
LRECL MIN=minirecl MAX=maxlrecl
GV912
MAX RECORDS PER BLOCK=recs
Reason:
When GVRESTOR reloads a sequential data set indicated as TYPE=SD, it performs a
record analysis of the logical blocks processed from the track image input. The primary
purpose of this analysis is to validate the exported data. When plain sequential data sets
are exported by FAVER2.VSE, there are situations where the correct record format is not
available. Without this information, CA FAVER must reload the data set as RECFM=U.
The information listed in this message is designed to help you determine the correct
record format.
minblk
is the size of the smallest block encountered
maxblk
is the size of the largest block encountered
minlrecl
is the size of the smallest record encountered
Chapter 2: Messages 53
GV Messages
maxlrecl
is the size of the largest records encountered
recs
is the largest number of records found in any one block.
Also see message GV913.
GV913
RECFM=U DATA SET CONFORMS TO RECFM=recfm FORMATTING WITH n RECORDS
Reason:
When plain sequential data sets are exported by FAVER2/VSE, there are situations
where the correct record format is not available. Without this information, CA FAVER
must load the data set as RECFM=U/ When GVRESTOR reloads a sequential data set
indicated as TYPE=SD and RECFM=U, it performs a record analysis of the logical blocks
processed from the track image input. If every block appears to have a valid block
descriptor word (BDW) and every record appears to have a valid record descriptor word
(RDW), this message is issued. recfm can be V or VB. n is the number of records in the
file if it were processed as a variable length record file. The normal record count, which
follows this message will reflect the block count since RECFM=U records are blocks.
If you want to access the reloaded file as a variable length record file, include:
DCB=(BLKSIZE=maxblk,LRECL=maxlrecl,RECFM=VB)
in the JCL when accessing it. The JCL specifications will override the attributes stored on
the disk label (Format 1 DSCB). The values of "maxblk" and "maxlrecl" can be taken
directly out of the GV912 message.
GV914
DATA IS INCONSISTENT WITH RECORD FORMAT
Reason:
When GVRESTOR reloads a sequential data set indicated as TYPE=SD, it performs a
record analysis of the logical blocks processed from the track image input. The primary
purpose of this analysis is to validate the exported data.
For RECFM=V or RECFM=VB data sets, the block descriptor word (BDW) or record
descriptor word (RDW) do not correctly describe the records or blocks in the file. If you
attempt to access this file as a variable length record file, the application will fail.
For RECFM=F or RECFM=FB data sets, a block has been encountered that is not an even
multiple of LRECL. If you attempt to access this data set as a fixed length record file, the
application will fail.
54 Message Reference Guide
GV Messages
GV918
FAVER2 TRANSPARENCY REQUIRES LARGE BLOCK INTERFACE (lbi), TERMINATING
Reason:
GVRESTOR is attempting to reload data through the FAVER2 transparency. The
transparency module requires the Large Block Interface (LBI) services to read the VSE
tape's 64Kblocks. The current system does not have the LBI service available.
LBI is available on OS/390 2.10 and later systems, including all levels of z/OS. If this
operating system supports LBI, ensure the service has been activated.
GV919
alloc_text
Reason:
When allocating sequential files in preparation for reload, GVRESTOR logs out the
allocation values in a series of GV919 messages.
Action:
This is informational only.
GV920
GETMAIN ERROR
Reason:
Insufficient storage exists in the address space to continue processing.
Action:
Increase the REGION value on the JOB or EXEC JCL statement and run this job again.
GV921
INPUT NOT GVEXPORT FORMAT
Reason:
The input tape is expected to be in FAVER EXPORT format. The most common mistake is
attempting to reload a cluster from a REPRO format tape.
Chapter 2: Messages 55
GV Messages
GV922
DYNAMIC ALLOCATION FAILED RC=xx INFO=xxxxxxxx
GV922 dynalloc messages
Reason:
FAVER was attempting to create a sequential data set for the current RESTOR. The
allocation failed. RC is the return code from dynamic allocation and INFO is the
combination error and information codes from dynamic allocation. If there are any
other messages generated by dynamic allocation, they will immediately follow, with
each message prefixed by GV922.
GV923
QSAM OPEN ERROR, DDNAME=xxxxxxxx
Reason:
The current file being reloaded is a sequential file, rather than a VSAM file. The OPEN
was unsuccessful. The reload is aborted.
Action:
Review the console log for additional messages concerning this file.
GV924
DATA SET PRIMED
Reason:
The sequential file has been allocated and primed. No data was reloaded into this file.
This was performed as a result of requesting PRIME for this restore operation.
GV925
RECORD LENGTH xxxxx EXCEEDS MAXIMUM OF yyyyy
Reason:
During the reload of a sequential file, a record was encountered that exceeded the
maximum allowable record length. xxxxx is the length of the record to be written. yyyyy
is the LRECL value for this data set.
56 Message Reference Guide
GV Messages
GV926
QSAM CLOSE ERROR, DDNAME=xxxxxxxx, TERMINATING
Reason:
After a restore operation for a sequential file has terminated the CLOSE failed.
Action:
Review the console log for any other messages related to this data set.
GV927
RECORD LENGTH xxxxxx DOES NOT MATCH FIXED LRECL OF yyyyy, TERMINATING
Reason:
During the reload of a fixed length record sequential file, a record was encountered
whose length did not match the record length. xxxxx is the length of the record to be
written. yyyyy is the LRECL value for this data set.
GV928
FAVER FILE FORMAT ERROR - reason
xxxxxxxxxxxx
Reason:
The input file from a VSE FAVER 2 system has unexpected or unknown contents. The
type of error is explained in one of the following reasons:
UNKNOWN SEGMENT
The tape record format is variable blocked spanned. The segment indicator in the
segment descriptor word is invalid.
FIRST SEGMENT ORDER
A first segment does not follow a last segment.
INTERMEDIATE SEGMENT ORDER
An intermediate segment does not follow a first or intermediate segment.
LAST SEGMENT ORDER
A last segment does not follow a first or intermediate segment.
Chapter 2: Messages 57
GV Messages
UNKNOWN HEADER TYPE
Each block has a header that describes the data in the block. This one does not
match a valid type.
UNKNOWN RECORD TYPE
Each block also includes a record identifier. This one does not match a known type.
xxxxxxxxxxxx is a hex dump of the beginning of the block where the error was
encountered.
GV929
SKIPPING HEADER - reason
Reason:
Certain FAVER2 VSE record types are not supported by FAVER2 transparency, the
header records are bypassed. This is an informational message the type of header
skipped is described by reason:
COMPRESSION HEADER
A record containing information about hardware compression of a cluster is
skipped.
DSCB HEADER
A record containing information about a direct access file is skipped.
GV930
FAVER2 TRANSPARENCY REQUIRES SYSTEM DETERMINED BLOCK SIZE AT LEAST 64K
(PARMLIB DEVSUPxx)
Reason:
The FAVER2 Transparency uses the Large Block Interface (LBI) which is available on
OS/390 2.10 and all levels of z/OS and subsequent operating systems. The current
environment does not allow a minimum of 64K as a block size.
Action:
If you are at the proper operating system level, examine the DEVSUPxx member of
SYS1.PARMLIB to ensure the TAPEBLKSZLIM value is set to 64K or higher.
58 Message Reference Guide
GV Messages
GV931
OUTDD=ddname HAS ALREADY BEEN PREVIOUSLY SPECIFIED, DDNAME MUST BE
UNIQUE
Reason:
A given DD may be used for OUTDD processing by only one cluster. If OUTDD processing
is desired for multiple clusters, each cluster must be directed to a separate DD
statement.
GV932
OUTDD PROCESSING IS NOT SUPPORTED WITH A GENERIC CLUSTER SELECTION
Reason:
The associated cluster selection specifies generic selection characters that may resolve
to multiple clusters. Since OUTDD processing requires a unique OUTDD for each
separate cluster, specifying OUTDD in this context is not allowed.
If you need to perform OUTDD processing on multiple clusters, specify each cluster on a
separate cluster selection statement with the OUTDD parameter designating different
DD names on each one.
GV933
INPUT SUBTASK ERROR - RC=
Reason:
The input subtask of the Move/Copy operation failed to initialize properly, and
execution was terminated.
GV934
OUTPUT SUBTASK ERROR - RC=
Reason:
The output subtask of the Move/Copy operation failed to initialize properly, and
execution was terminated.
Chapter 2: Messages 59
GV Messages
GV935
Unable to obtain ENQ for DSN dataset name.
Reason:
During a Move operation, the ENQ failed on the input data set, and has been bypassed
for processing. Usually, MOVE continues with the next cluster, but if ESTOP is specified
then the execution will terminate.
GV936
Rename table not initialized, dataset bypassed.
Reason:
During a Move operation, the rename table failed to initialize, and the data set has been
bypassed for processing.
CORRUPT CIDF.
CI STARTS AT LOCATION address CIDF CONTENTS xxxx
hex dump of rdf
Reason:
The contents of a CIDF do not correctly describe length or location of the free space in
the CI. The CIDF contains a software end-of-file, but the current RBA is less than
high-used RBA; in other words, the end-of-file is out of place.
INDEX IN A LOOP
Reason:
The pointer chain that connects sequence set index records together forms a loop. Any
attempt to read the cluster sequentially will cause that program to go into a loop.
INDEX PREMATURE EOF
DIRECT LAST INDEX CI RBA = rba SEQUENTIAL LAST INDEX RBA = rba
Reason:
The end of file for this cluster when following the index from highest level to sequence
set and when following the sequence set chain pointers does not occur at the same CI.
Direct processing can proceed normally; however, sequential processing will not find all
records in the file.
60 Message Reference Guide
GV Messages
DATA RBA NOT FOUND
INDEX RBA NOT FOUND
RBA = rba
Reason:
The RBA to read a data or index CI could not be found in the RBA/DASD EXTENT table.
KEYS OUT OF SEQUENCE
LAST KEY IN SEQUENCE - key
KEY OUT OF SEQUENCE - key
Reason:
The keys of adjacent records in a KSDS were not in ascending sequence.
GV999
license_msg - prod_name
Reason:
The License Management Program (LMP) has detected a problem when determining the
license status of this product. The license_ msg may be one of the following:
■
PRODUCT EXPIRES SOON - This product is currently licensed, but the license expires
in less than 30 days.
■
PRODUCT HAS EXPIRED - No current license for this product could be found.
■
ENVIRONMENTAL ERROR - The LMP system could not make a license
determination. Review the console log for additional information concerning this
failure.
■
CAIRIM HAS NOT BEEN RUN - The LMP system has not been initialized yet. Make
sure CAIRIM is included in the operating system startup commands.
■
INTERNAL ERROR - The LMP system has experienced an unrecoverable error.
Review the console log for additional information concerning this failure.
The prod_name text identifies the ISM product to which this message pertains.
Chapter 2: Messages 61
GVA Messages
GVA Messages
GVA001E
REQUEST MACRO ERROR CODE(DECIMAL) = xx
Reason:
A VSAM request issued by GVBLDIX failed. The xx field displays the FEEDBACK from the
RPL.
Action:
Check FEEDBACK code; see the VSAM Administration: Macro Instruction Reference
Guide for more information.
GVA003E
GENCB/MODCB/SHOWCB/TESTCB ERROR
Reason:
The GVA003E error message originates in opening either the base or the alternate index
object. GVBLDIX was unable to generate an ACB or an RPL, and then was unable to
execute a MODCB, SHOWCB, or TESTCB in an attempt to gather more information.
Action:
The problem may be insufficient virtual storage; try increasing the REGION parameter.
Check the JCL, making sure the cluster names are spelled correctly. Also make sure the
correct CATALOG has been specified if you have not set up an alias.
GVA004E
INPUT IS NOT A BASE CLUSTER
Reason:
A search of the catalog record found that the cluster specified on the BASE DD is not a
base cluster.
Action:
Most likely the VSAM object is something other than a base cluster. Perform a LISTCAT
for more information.
62 Message Reference Guide
GVA Messages
GVA006E
OUTPUT IS NOT AN AIX
Reason:
The object specified on the AIX DD is not an alternate index.
Action:
Specify an alternate index on the AIX DD. For more information, perform a LISTCAT.
GVA007E
BASE DD NOT FOUND
Reason:
The required BASE DD was not found in your jobstream.
Action:
Specify a DD with the DNAME BASE. This DD must describe the base cluster.
GVA008E
GETMAIN FAILED
Reason:
A GETMAIN macro failed, possibly due to insufficient virtual storage.
Action:
Increase the REGION parameter.
GVA010W
AIX POINTER OVERFLOW, AIX KEY FOLLOWS:
Reason:
This warning occurs when you have specified a nonunique alternate index and there is
insufficient space within an AIX record to contain all the prime pointers for a particular
alternate key. All the records in the base cluster are not represented by the alternate
index.
Action:
To ensure the maximum room for prime pointers, do not specify a record size and make
sure the control area size is 1 cylinder (that is, use CYLINDER allocation).
Chapter 2: Messages 63
GVA Messages
GVA011E
GVCAT FAILED
Reason:
GVCAT is a catalog interface routine used to gather information on the alternate index.
GVCAT was unable to obtain information on the alternate index specified on the AIX DD.
Action:
Make sure you have proper security to access the catalog. It is possible that the catalog
is corrupt, so run a DIAGNOSE on it. Also run a listcat on the catalog and the alternate
index.
GVA012E
GVCAT NODE ERROR
Reason:
GVCAT builds a node for each alternate index defined for the cluster specified on the
BASE DD. Each node contains information about an alternate index, but for some reason
a node was incomplete.
Action:
This may be a catalog problem. Run IDCAMS DIAGNOSE.
GVA013W
NONUNIQUE AIX KEY, RECORD NOT WRITTEN TO aix.name
GVA013W
AIX KEY FOLLOWS:
...Hex dump of key... *...Character dump of key...*
64 Message Reference Guide
GVA Messages
GVA014W
PRIME KEY FOLLOWS:
Hex dump of key *...Character dump of key
Reason:
The alternate index was defined as UNIQUE, and a nonunique record was encountered.
This record is not written to the alternate index. Instead, the alternate key and the
prime key are written to SYSPRINT.
Action:
None.
GVA015W
PRIME RBA FOLLOWS: ...record RBA...
Reason:
This message follows the GVA014W message if the cluster is an ESDS. The RBA (relative
byte address) of the record is printed.
Action:
None.
GVA016E
DYNAMIC ALLOCATION ERROR R15 = xxx, yyyy
Reason:
A problem was encountered in allocating or unallocating an alternate index. xxx is the
return code from DYNALLOC, and yyyy is the error code from +4 into S99RB.
Action:
Please see the IBM System Macros and Facilities Volume 1 (pages 1-266).
Chapter 2: Messages 65
GVA Messages
GVA017I
BASE RECORDS IN = a AIX RECORDS OUT = b WRITTEN TO aix.name
Reason:
In this informational message, a is the number of records input to sort (for the current
AIX, see GVA018I), and b is the number of records written to the alternate index.
Action:
None. Informational only.
GVA018I
*** BEGIN PROCESSING aix.name
Reason:
In this informational message, aix.name is the alternate index currently being processed.
All messages following this message pertain to this alternate index, until message
GVA019I is displayed.
Action:
None.
GVA018I
*** END PROCESSING aix.name
Reason:
In this informational message, aix.name is the alternate index that has just been
successfully built.
Action:
None.
66 Message Reference Guide
GVA Messages
GVA031W
AIX KEY DOES NOT EXIST IN BASE RECORD
Reason:
This warning occurs when the defined alternate index key (+ offset) into the base record
runs over the end or does not exist in the base record. The alternate key as defined does
not exist in the base record, so an alternate index record cannot be built.
Action:
Check the definition of the alternate index; make sure the key offset and length are
correct.
GVA020E
DROP KEY PARAMETER ERROR
Reason:
This error message indicates either an 'X' (hex) or a 'C' (character) has been omitted.
Action:
It is necessary to specify the type of drop key (that is, DROP=X, or DROP=C).
GVA021E
SYNTAX ERROR MARKED BY 'X'
Reason:
A parameter has been incorrectly specified. An X appears immediately below the
parameter in error.
Action:
Most likely the error was caused by a misspelled or incomplete parameter. Ensure that
the parameters are correct.
Chapter 2: Messages 67
GVA Messages
GVA032E
DISCONTIGUOUS KEY LENGTH ERROR - CURRENT AIX IS
Reason:
This error message indicates that the sum of the discontiguous keys specified does not
equal the length of the aix key from the catalog.
Action:
Check the definition of the alternate index, making sure the key length matches the sum
of the discontiguous key lengths.
GVA033E
DROP KEY LENGTH NOT EQUAL TO AIX KEY LENGTH Reason:
This error message indicates that the drop key length as specified on the DROP= sub
parameter does not equal the aix key length from the catalog.
Action:
Check the definition of the alternate index, making sure the key length matches the
length of the DROP= key parameter.
GVA034I
AIX RECORD OVERFLOW COUNT =
Reason:
This informational message indicates the aix record could not contain all of the base
record pointers. A decimal integer count of the number of dropped pointers is
displayed.
Action:
None.
68 Message Reference Guide
GVA Messages
GVA035W
NONUNIQUE KEY LIMIT REACHED, CURRENT AIX IS
GVA035W
AIX KEY FOLLOWS
Reason:
This warning message indicates the limit on the number of base pointers that will fit into
an aix record has been reached. The remaining base pointers are dropped. The aix key is
printed following the GVA035W message.
Action:
None.
GVA037W
AIX FOUND IN CATALOG BUT NOT SELECTED. AIX NOT BUILT. Reason:
This warning message indicates that an alternate index was found in the catalog but was
not specified in the control statements. The alternate is not built since there is not an
AIX= selecting it.
Action:
None.
GVA040E
xxxx DD NOT FOUND
Reason:
This error indicates that the ddname passed to GVPATH was not found (where xxxx =
BASE or AIX).
Action:
Ensure that the ddname passed to GVPATH exists in your JCL. Check to make sure the
parameter list is properly specified.
Chapter 2: Messages 69
GVCAT Messages
GVA041E
PARAMETER ERROR - UNKNOWN OPERATION
Reason:
The flag field does not contain either a 4 (OPEN), an 8 (READ) or a 12 (CLOSE). This error
occurs only on GVPATH calls.
Action:
Make sure the parameter list is properly specified.
GVCAT Messages
GVCAT.100
AMDSB LEN TOO SMALL = value of ctgflln
Reason:
The GVCAT procedure encountered an invalid CTGFLLN value. Most likely a user
program overwrote storage used by CA EXTEND/DASD.
Action:
Check user programs and other software for subscripts out of bounds, base registers not
set properly, and other causes of overwritten storage.
If you find none of these, or if correcting them does not help, see the dump procedures
in the CA EXTEND/DASD VSAM Compression System Reference Guide.
GVCAT.120
C#BASASC PAST END
Reason:
The GVCAT procedure encountered an internal error in the base cluster association list.
Most likely a user program overwrote storage used by CA EXTEND/DASD.
Action:
Check user programs and other software for subscripts out of bounds, base registers not
set properly, and other causes of overwritten storage.
If you find none of these, or if correcting them does not help, see the dump procedures
in the CA EXTEND/DASD VSAM Compression System Reference Guide.
70 Message Reference Guide
GVCAT Messages
GVCAT.140
C#AIXASC PAST END
Reason:
The GVCAT procedure encountered an error in the CTGFL association list. Most likely a
user program overwrote storage used by CA EXTEND/DASD.
Action:
Check user programs and other software for subscripts out of bounds, base registers not
set properly, and other causes of overwritten storage.
If you find none of these, or if correcting them does not help, see the dump procedures
in the CA EXTEND/DASD VSAM Compression System Reference Guide.
GVCAT.160
NO DATA COMP FOR AIX
Reason:
The GVCAT procedure could not find a data component associated with an alternate
index. This is possibly a catalog error, but most likely a user program overwrote storage
used by CA EXTEND/DASD.
Action:
Use IDCAMS LISTCAT on the base cluster and on each alternate index to ensure that the
catalog contains an entry for the data component of each alternate index. If such is the
case, then check user programs and other software for subscripts out of bounds, base
registers not set properly, and other causes of overwritten storage. If you find none of
these, or if correcting them does not help, see the dump procedures in the CA
EXTEND/DASD VSAM Compression System Reference Guide.
Chapter 2: Messages 71
GVCAT Messages
GVCAT.180
AMDSB LEN TOO SMALL
Reason:
The GVCAT procedure encountered an invalid CTGFLLN value. Most likely a user
program overwrote storage used by CA EXTEND/DASD.
Action:
Check user programs and other software for subscripts out of bounds, base registers not
set properly, and other causes of overwritten storage.
If you find none of these, or if correcting them does not help, see the dump procedures
in the CA EXTEND/DASD VSAM Compression System Reference Guide.
GVCAT.200
BAD CTG CHAIN
Reason:
The GVCAT procedure could not find needed catalog entries. This is possibly a catalog
error, but most likely a user program overwrote storage used by CA EXTEND/DASD.
Action:
Use IDCAMS LISTCAT on the base cluster and on each alternate index to ensure that all
necessary catalog entries exist. If such is the case, then check user programs and other
software for subscripts out of bounds, base registers not set properly, and other causes
of overwritten storage.
If you find none of these, or if correcting them does not help, see the dump procedures
in the CA EXTEND/DASD VSAM Compression System Reference Guide.
72 Message Reference Guide
GVCAT Messages
GVCAT.220
C#AS PAST END
Reason:
The GVCAT procedure encountered an error in an internal association list. Most likely a
user program overwrote storage used by CA EXTEND/DASD.
Action:
Check user programs and other software for subscripts out of bounds, base registers not
set properly, and other causes of overwritten storage.
If you find none of these, or if correcting them does not help, see the dump procedures
in the CA EXTEND/DASD VSAM Compression System Reference Guide.
GVCAT.240
ENTRY NOT FOUND IN CATALOG. DSN= data set name
Reason:
The specified data set is not cataloged.
Action:
If this message occurs while the MIEXAM job is running, use the CA EXTEND/DASD ISPF
panels to check the spelling of the DSNAME. Then re-submit the MIEXAM job.
If this message occurs while the Analyzer is running, the data set is not in the specified
catalog. Ensure that you specified both the data set name and the catalog name
correctly. Correct the error and resubmit the job.
If this message occurs at some other time, most likely a user program overwrote storage
used by CA EXTEND/DASD. Check user programs and other software for subscripts out
of bounds, base registers not set properly, and other causes of overwritten storage.
If you find none of these, or if correcting them does not help, see the dump procedures
in the CA EXTEND/DASD VSAM Compression System Reference Guide.
Chapter 2: Messages 73
GVCAT Messages
GVCAT.260
ERROR IN CATALOG LOCATE
DSN= data set name
RC = return code
REASON = reason code
FDBK = fdbk code
SEE IBM MSG IDC3009I
Reason:
The OS/390 catalog LOCATE function encountered an error.
Action:
See IBM's documentation for OS/390 message IDC3009I.
GVCAT.280
LOC RET LEN=0 OR INFO=FF
Reason:
While using the OS/390 locate service, the GVCAT procedure encountered an error.
Most likely a user program overwrote storage used by CA EXTEND/DASD.
Action:
Check user programs and other software for subscripts out of bounds, base registers not
set properly, and other causes of overwritten storage.
If you find none of these, or if correcting them does not help, see the dump procedures
in the CA EXTEND/DASD VSAM Compression System Reference Guide.
74 Message Reference Guide
IC Messages
IC Messages
IC211
DYNAMIC ALLOCATION FAILED - SEE JOB LOG - VOL=volser UNIT=name X'xxxx'
Reason:
volser: Volume being allocated.
name: Unit name used for allocation.
X'xxxx' Error reason code, documented in OS/390 SPL: Job Management.
A volume could not be allocated. An interpretation and reason for the error is displayed
in the JES job log as an IKJ prefix message. The IKJ message and its explanation in the
OS/390 message manual will provide adequate documentation to fix the problem.
IC212
PREVIOUS DISK OPEN ERROR VOL=volser
Reason:
volser: Volume being allocated and opened.
A previous attempt to allocate and open this volume failed. See a preceding IC211
message for the reason this volume could not be opened or allocated.
IC213
DD STATEMENT MISSING FOR VOLUME volser
Reason:
volser: Desired volume (VS1 only.) A DD statement was not supplied for this volume.
See JCL requirements in the CA FAVER VSAM Data Protection User Guide.
Chapter 2: Messages 75
IC Messages
IC230
data setname NOT FOUND ON volser
Reason:
data setname: Catalog or VVDS.
volser: Volume where above was expected to be found.
The VVDS (DSN= SYS1.VVDS.Vvolser) could not be found in the VTOC of this pack. Or, a
catalog which locate or read JFCB indicates is on this pack could not be found in the
VTOC.
IC231
data setname READ ERROR=nnn
Reason:
data setname: Catalog or VVDS being read.
nnn: Type of error encountered:
■
12 RBA not found.
■
13 EXCP error.
■
14 Spanned record error.
■
15 Corrupt CIDF.
■
16 Corrupt RDF.
An error was encountered when reading a catalog or VVDS. The usual cause is a corrupt
record in the catalog or VVDS. An IDCAMS DIAGNOSE or LISTCAT ALL will help in
determining the cause of the error.
IC232
INVALID FIELD IN data setname TRACE=nnn
Reason:
data setname: Name of catalog or VVDS being opened.
nnn: Internal trace point that marks the point of the error.
When gathering data from the self-describing records of a catalog or VVDS an invalid
field was encountered. For an ICF catalog or a VVDS, execute the IDCAMS DIAGNOSE
function to find the cause of the error. For a VSAM catalog, a LISTCAT ALL may provide
additional information.
76 Message Reference Guide
IC Messages
IC233
DATA SET HAS BEEN MIGRATED, NOT BEING EXPORTED - dsn
Reason:
This cluster was requested for export. At time of export, the cluster had been archived
by HSM. Therefore, it is not in VSAM format, nor will it be exported by CA FAVER since
there is no HSM parameter card.
IC234
MIGRATED FILE WAS RECALLED BUT WAS NOT VSAM - DOES NOTMATCH MCDS ENTRY
- dsn
Reason:
This cluster was requested for export even if it had been migrated. According to the
MCDS, this file was originally VSAM therefore it was recalled. Upon checking the catalog
after recall, the file turned out not to be a VSAM file. This does not match the MCDS.
IC235
DYNAMIC ALLOCATION ERROR WHILE TRYING TO ALLOCATE MIGRATED FILE - dsn
Reason:
This cluster was requested for export even if it had been migrated. When trying to
dynamically allocate the file (to have the file recalled) there was an error. Check the
return codes for the specific reason of the error.
IC236
catalog dsn - READ ERROR = rc
Reason:
When trying to read the catalog after a requested cluster had been recalled (HSM
parameter set), there was a read error. The usual cause is a corrupt record in the
catalog. An IDCAMS DIAGNOSE or LISTCAT ALL will help in determining the cause of the
error.
IC237
REQUESTED DATA SET NOT VSAM - dsn
Reason:
This cluster was specifically asked for by a CL= card in the EXPORT job but was not a
VSAM file.
Chapter 2: Messages 77
IC Messages
IC240
name MACRO ERROR DDNAME=ddname RETURN CODE=nnn
Reason:
name: The system macro instruction returning the error.
ddname: The DD statement used by the macro.
nnn: Macro error return code in decimal.
An error return code was passed by a system macro instruction. The meanings of the
return codes and the corrective actions can be found in the SPL: Data Management,
Supervisor Services and Macro Instructions, or Data Management Services manuals.
IC241
data setname LOCATE FAILED RETURN CODE=nnn
Reason:
data setname: Catalog name.
nnn: Locate macro return code in decimal.
The locate function failed when used to find the volume and device type of a catalog.
The meanings of the return codes and the corrective actions can be found in the Data
Management Services manual.
78 Message Reference Guide
Chapter 3: Condition Codes and User
Abends
This chapter lists the return codes and abend codes issued by CA FAVER.
This section contains the following topics:
CA FAVER Condition Codes (see page 79)
CA FAVER User Abends (see page 80)
CA FAVER Condition Codes
At normal termination, CA FAVER issues the following condition codes:
0
Indicates normal completion.
2
Indicates that all clusters were exported but the SAVECOMP parameter had been
specified and at least one cluster exported was not hardware compressed.
4
Indicates that all clusters were exported or restored. SYSOUT should be checked for
informational messages describing conditions encountered on some clusters.
8
Indicates that not all clusters were exported, restored, or compared. Messages in
the listing describe the reasons.
16
Indicates that no clusters were restored or exported. Also, an error was detected in
a user exit.
Chapter 3: Condition Codes and User Abends 79
CA FAVER User Abends
CA FAVER User Abends
At abnormal termination, CA FAVER issues the following user abend codes:
001
Indicates that CA FAVER is abending due to an unrecoverable error.
002
Indicates that the user, using the ESTOP parameter, requested GVRESTOR abend
rather than skip a cluster and continue to the next one. If ESTOP was not specified,
GVRESTOR would have continued and terminated with a condition code of 8.
003
Indicates that PARM=DUMP has requested an abend with a dump.
009
Indicates that the user, using the ESTOP parameter, requested GVEXPORT abend
rather than skip a cluster and continue to the next one. If ESTOP was not specified,
GVEXPORT would have continued and terminated with a condition code of 8.
80 Message Reference Guide