PS to ZLB - CA Support

PS to ZLB - CA Support
CA Database Management
Solutions for DB2 for z/OS
Message Reference Guide (PS to ZLB)
r15
Fourth Edition
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 may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without
the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed
by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing
your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and
CA.
Notwithstanding the foregoing, 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 ACF2™ for z/OS (CA ACF2)
■
CA Bind Analyzer™ for DB2 for z/OS (CA Bind Analyzer)
■
CA Compile/PRF
■
CA Database Analyzer™ for DB2 for z/OS (CA Database Analyzer for DB2)
■
CA Detector® for DB2 for z/OS (CA Detector)
■
CA Endevor® SCM Interface for DB2 for z/OS (CA Endevor SCM for DB2)
■
CA Fast Check® for DB2 for z/OS (CA Fast Check)
■
CA Fast Index® for DB2 for z/OS (CA Fast Index)
■
CA Fast Load for DB2 for z/OS (CA Fast Load)
■
CA Fast Recover™ for DB2 for z/OS (CA Fast Recover)
■
CA Fast Unload® for DB2 for z/OS (CA Fast Unload)
■
CA InfoRefiner® (CA InfoRefiner)
■
CA InfoTransport® (CA InfoTransport)
■
CA Insight™ Database Performance Monitor for DB2 for z/OS (CA Insight)
■
CA Index Expert™ for DB2 for z/OS (CA Index Expert)
■
CA Log Analyzer™ for DB2 for z/OS (CA Log Analyzer)
■
CA LogCompress™ for DB2 for z/OS (CA LogCompress)
■
CA Merge/Modify™ for DB2 for z/OS (CA Merge/Modify)
■
CA NSM Database Option for DB2 for z/OS (CA NSM Database Option)
■
CA Partition Expert™ for DB2 for z/OS (CA Partition Expert)
■
CA Plan Analyzer® for DB2 for z/OS (CA Plan Analyzer)
■
CA Quick Copy for DB2 for z/OS (CA Quick Copy)
■
CA Rapid Reorg® for DB2 for z/OS (CA Rapid Reorg)
■
CA RC/Compare™ for DB2 for z/OS (CA RC/Compare)
■
CA RC/Extract™ for DB2 for z/OS (CA RC/Extract)
■
CA RC/Migrator™ for DB2 for z/OS (CA RC/Migrator)
■
CA RC/Query® for DB2 for z/OS (CA RC/Query)
■
CA RC/Secure™ for DB2 for z/OS (CA RC/Secure)
■
CA RC/Update™ for DB2 for z/OS (CA RC/Update)
■
CA Recovery Analyzer™ for DB2 for z/OS (CA Recovery Analyzer)
■
CA Report Facility for IMS, CICS, and TSO (CA Report Facility)
■
CA Service Desk
■
CA SQL-Ease® for DB2 for z/OS (CA SQL-Ease)
■
CA Subsystem Analyzer for DB2 for z/OS (CA Subsystem Analyzer)
Contact CA Technologies
Contact CA Support
For your convenience, CA Technologies provides one site where you can access the
information you need for your Home Office, Small Business, and Enterprise CA
Technologies products. At http://ca.com/support, you can access the following:
■
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]
If you would like 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.
Documentation Changes
The following documentation updates have been made in the fourth edition of this
document:
■
Precompiler Return Codes (see page 39)—Updated return code 0 to indicate that a
bind is necessary. Added return code 1. Removed return code 2.
■
CA RC/Query Return Codes (see page 55)—Updated return code 56 to indicate that
a data set member is missing.
■
PSA Messages (see page 113)—Added or revised the following message: PSA0815.
■
PUT Messages (see page 533)—Added or revised the following messages: PUT0017I
and PUT0095W.
■
PTUIX Messages (see page 529)—Added or revised the following message:
PTUIX10E.
■
RM Messages (see page 1071)—Added or revised the following message: RM522E.
■
RMA Messages (see page 1249)—Added or revised the following messages:
RMA914W and RMA914W.
■
RU Messages (see page 1853)—Added or revised the following messages: RU676I
and RU677I.
■
SQ Messages (see page 2083)—Added or revised the following message: SQ152E.
■
TGR Messages (see page 2264)—Added or revised the following messages:
TGRTRC001I, TGRTRC003I, TGRTRC004I, TGRTRC005I, TGRTRC006I, TGRTRC007I,
TGRTRC008I, TGRTRC009I, TGRTRC010I, TGRTRC011I, TGRTRC012I, TGRTRC013I,
TGRTRC014I, TGRTRC015I, and TGRTRC016I.
The following documentation updates have been made in the third edition of this
document:
■
PUT Messages (see page 533)—Added or revised the following messages:
PUT0506I.
■
QI Messages (see page 734)—Changed QI171E to QI171W
■
RAE Messages (see page 815)—Added or revised the following messages:
RAE00937, RAE00938, RAE00939, and RAE00940.
■
RO Messages (see page 1343)—Added or revised the following messages: RO199E,
RO267E, RO269E, RO280E, RO428E, RO655I, RO657E, RO658E, and RO659E.
■
RS Messages (see page 1718)—Added the following message: RS575W.
■
SQ Messages (see page 2083)—Added the following message: SQ166E.
■
TGR Messages (see page 2264)—Added the following messages: TGRIBS003E and
TGRIBS004E.
The following documentation updates have been made in the second edition of this
document:
■
PUT Messages (see page 533)—Added or revised the following messages:
PUT9808E.
■
QI Messages (see page 734)—Changed QI172E to QI172W.
■
RMA Messages (see page 1249)—Added the following messages: RMA889E.
■
RO Messages (see page 1343)—Added or revised the following messages: RO063E
and RO066E.
The following documentation updates have been made since the last release of this
documentation:
■
CA Database Analyzer for DB2 Return Codes (see page 45)—Updated the SQL error
condition for return code 04.
■
Utilities Index Compression Service Return and Reason Codes (see page 60)—Added
new topic.
■
Utilities Index Compression Size Service Return and Reason Codes (see
page 61)—Added new topic.
■
PSA Messages (see page 113)—Added the following messages: PSA0362, PSA0367,
PSA0368, and PSA0369.
■
PTT Messages (see page 460)—Added or revised the following messages: PTT0710,
PTT0711, PTT0712, and PTT1073E.
■
PUT Messages (see page 533)—Added or revised the following messages:
PUT0136I, PUT2200E, PUT2201E, PUT2202E, PUT2203E, PUT2542I, PUT3037E,
PUT3043E, PUT4428W, PUT6210E, and PUT6242E.
■
RAE Messages (see page 815)—Added or revised the following messages:
RAE00085.
■
RAG Messages (see page 854)—Revised the following message: RAG030I.
■
RM Messages (see page 1071)—Added the following messages: RM632W, RM700I,
RM701I, RM702I, RM703E, RM706E, RM707W, RM709E, RM710E, RM711I,
RM712E, RM715E, RM716E, RM717I, RM718I, RM720E, RM721E, RM722E,
RM723E, RM724E, RM725E, RM726E, RM727I, RM729E, RM731E, RM732E,
RM733E, RM734E, RM735E, RM736E, RM737E, RM738E, RM739E, RM740E,
RM741E, RM742E, RM743E, RM744E, RM745E, RM746E, RM747E, RM748E,
RM749E, RM760E, RM761E, RM762E, RM763E, RM764E, RM765E, RM766E,
RM767E, RM768E, RM769E, RM770E, RM771E, RM772E, RM773E, RM774E,
RM775E, RM776E, RM777E, RM778E, and RM779E.
■
RMA Messages (see page 1249)—Added the following messages: RMA593W,
RMA817E, RMA849W, RMA885E, and RMA887E; changed message number
RMA817I to RMA860I.
■
RO Messages (see page 1343)—Added or revised the following messages: RO064E,
RO190I, RO192I, RO245I, RO272I, RO374E, RO378I, RO379I, RO488I, RO651E
through RO653E, RO748E, RO793E through RO805E.
■
RS Messages (see page 1718)—Revised the following message: RS035E.
■
RU Messages (see page 1853)—Added the following messages: RU676I, RU677I,
and RU678E.
■
RX Messages (see page 1994)—Added the following message: RX072E.
■
SQ Messages (see page 2083)—Added or revised the following messages: SQ015W,
SQ155W through SQ160W.
■
TGR Messages (see page 2264)—Added or revised the following messages:
TGRCKE001E, TGRCKE002E, TGRFLA012E, and TGRIBY017E.
Contents
Chapter 1: Introduction
13
Message Format ......................................................................................................................................................... 13
Variables ..................................................................................................................................................................... 13
Suffixes ....................................................................................................................................................................... 13
Message Levels........................................................................................................................................................... 13
DSNTIAR Format for SQLCODE +445 .......................................................................................................................... 14
z/OS and TSO Messages ............................................................................................................................................. 14
Audit Error Messages ................................................................................................................................................. 15
User Abends ............................................................................................................................................................... 15
CA InfoTransport System Messages ........................................................................................................................... 15
CA Insight Message Formats ...................................................................................................................................... 15
ISPF Session ......................................................................................................................................................... 16
Data Collector and PC Owner.............................................................................................................................. 16
IMOD Messages .................................................................................................................................................. 16
VTAM User Interface ........................................................................................................................................... 17
Message Codes........................................................................................................................................................... 17
Batch Processor Return Codes ............................................................................................................................ 18
IBM Return Codes ............................................................................................................................................... 18
Media Manager Return Codes ............................................................................................................................ 18
CA InfoRefiner Return Codes .............................................................................................................................. 20
CA Report Facility Return Codes ......................................................................................................................... 21
PTLDRIVM Product Driver Return Codes............................................................................................................. 21
RC/Alter Return Codes ........................................................................................................................................ 23
Snapshot General Services .................................................................................................................................. 23
Thread Termination\Dynamic DSNZPARM Return and Reason Codes ............................................................... 37
CA Bind Analyzer Return Codes .......................................................................................................................... 38
CA Insight Return Codes ...................................................................................................................................... 41
CA Database Analyzer for DB2 Return Codes...................................................................................................... 45
CA Detector Return Codes .................................................................................................................................. 46
CA Fast Check Return Codes ............................................................................................................................... 47
CA Fast Recover Return Codes ............................................................................................................................ 47
CA Log Analyzer Return Codes ............................................................................................................................ 48
CA Plan Analyzer Return Codes ........................................................................................................................... 49
CA Quick Copy Return Codes .............................................................................................................................. 49
CA Rapid Reorg Return Codes ............................................................................................................................. 54
CA RC/Migrator Return Codes ............................................................................................................................ 54
CA RC/Query Return Codes ................................................................................................................................. 55
Contents 9
CA RC/Secure Return Codes ................................................................................................................................ 58
CA SQL-Ease Return Codes .................................................................................................................................. 59
Utilities Index Compression Service Return and Reason Codes .......................................................................... 60
Utilities Index Compression Size Service Return and Reason Codes .................................................................. 61
Utilities Restart/Retry Return and Reason Codes ............................................................................................... 62
Chapter 2: PS to PTUIX
65
PS Messages ............................................................................................................................................................... 65
PSA Messages ........................................................................................................................................................... 113
PT Messages ............................................................................................................................................................. 149
PTD Messages .......................................................................................................................................................... 320
PTEX Messages ......................................................................................................................................................... 339
PTFL Messages ......................................................................................................................................................... 343
PTGET Messages....................................................................................................................................................... 345
PTGL Messages ......................................................................................................................................................... 345
PTI Messages ............................................................................................................................................................ 399
PTRR Messages......................................................................................................................................................... 403
PTT Messages ........................................................................................................................................................... 460
PTUIX Messages ....................................................................................................................................................... 529
Chapter 3: PUT to QRFM
533
PUT Messages .......................................................................................................................................................... 533
PXA Messages .......................................................................................................................................................... 665
PXM Messages ......................................................................................................................................................... 690
QI Messages ............................................................................................................................................................. 734
QRFM Messages ....................................................................................................................................................... 767
Chapter 4: RAE to RAW
815
RAE Messages........................................................................................................................................................... 815
RAG Messages .......................................................................................................................................................... 854
RAI Messages ........................................................................................................................................................... 862
RAP Messages .......................................................................................................................................................... 864
RAQ Messages .......................................................................................................................................................... 960
RAU Messages .......................................................................................................................................................... 974
RAW Messages ......................................................................................................................................................... 978
Chapter 5: RCM to RIV
985
RCM Messages ......................................................................................................................................................... 985
RCMHC Messages ................................................................................................................................................... 1021
10 Message Reference Guide (PS to ZLB)
RCX Messages......................................................................................................................................................... 1022
RG Messages .......................................................................................................................................................... 1031
RI Messages ............................................................................................................................................................ 1041
RIV Messages ......................................................................................................................................................... 1063
Chapter 6: RM to RO
1071
RM Messages ......................................................................................................................................................... 1071
RMA Messages ....................................................................................................................................................... 1249
RO Messages .......................................................................................................................................................... 1343
Chapter 7: RQ to RX
1685
RQ Messages .......................................................................................................................................................... 1685
RS Messages ........................................................................................................................................................... 1718
RU Messages .......................................................................................................................................................... 1853
RX Messages ........................................................................................................................................................... 1994
Chapter 8: SA to TT
2041
SA Messages ........................................................................................................................................................... 2041
SD Messages........................................................................................................................................................... 2079
SDM Messages ....................................................................................................................................................... 2081
SQ Messages .......................................................................................................................................................... 2083
SQL Messages ......................................................................................................................................................... 2137
SRSL Messages ....................................................................................................................................................... 2257
TGHC Messages ...................................................................................................................................................... 2262
TGR Messages ........................................................................................................................................................ 2264
TT Messages ........................................................................................................................................................... 2454
Chapter 9: U to ZLB
2469
U Messages ............................................................................................................................................................ 2469
UDC Messages ........................................................................................................................................................ 2471
UNLD Messages ...................................................................................................................................................... 2481
UOFB Messages ...................................................................................................................................................... 2506
UOFC Messages ...................................................................................................................................................... 2510
UOFL Messages ...................................................................................................................................................... 2511
UOFR Messages ...................................................................................................................................................... 2515
UOFU Messages ..................................................................................................................................................... 2519
UOGL Messages...................................................................................................................................................... 2523
UOQC Messages ..................................................................................................................................................... 2533
UORR Messages ..................................................................................................................................................... 2537
Contents 11
UTG Messages ........................................................................................................................................................ 2544
WNG Messages ...................................................................................................................................................... 2545
XD Messages .......................................................................................................................................................... 2545
XG Messages .......................................................................................................................................................... 2619
xnt Messages .......................................................................................................................................................... 2651
ZLB Messages ......................................................................................................................................................... 2834
12 Message Reference Guide (PS to ZLB)
Chapter 1: Introduction
This guide lists and describes the product and component messages for the CA Database
Management Solutions for DB2 for z/OS.
Message Format
Within the chapters, the messages are listed alphabetically, and then by message
number. For example, message PTGL123 comes before PTGL124. After each message is
an explanation and, if appropriate, suggestions on what to do.
Variables
Some of the messages use variables, which appear in all lowercase or are indicated by
the ampersand (&) sign. Variables are replaced by actual values when the error message
displays online. For example, &return and column-name in the following sample
messages indicate that the value is a variable. In the message that you see, an actual
return code and column name would be shown:
PFI0031E Invalid Return Code from PTAZLBLD - Return Code: '&return.'
RU527I UNPROTECT COMPLETE FOR column-name.
Suffixes
Some of the messages use three- or four-digit suffixes, which appear in all uppercase
after the message text. These suffixes are used by CA for diagnostic purposes and are
for internal use only.
Message Levels
To help users determine the severity of a problem, we use a one-letter code at the end
of the message number, such as the E in RU010E. The letter at the end of a message is
used to represent one of the following values.
■
I indicates an informational message
■
W indicates a warning message
■
E indicates an error message
Chapter 1: Introduction 13
DSNTIAR Format for SQLCODE +445
DSNTIAR Format for SQLCODE +445
The standard DSNTIAR formatted error message for an SQLCODE +445 looks like this:
DSNT404I SQLCODE = 445, WARNING: VALUE HAS BEEN TRUNCATED
DSNT418I SQLSTATE = 01004 SQLSTATE RETURN CODE
DSNT416I SQLERRD = 0 0 0 -1 0 0 SQL DIAGNOSTIC INFORMATION
DSNT416I SQLERRD = X'00000000' X'00000000' X'00000000'
X'FFFFFFFF' X'00000000' X'00000000' SQL DIAGNOSTIC
INFORMATION
DSNT417I SQLWARN0-5 = W,W,,,, SQL WARNINGS
DSNT417I SQLWARN6-A = ,,,, SQL WARNINGS
When a product has activated the SQL Truncation Translation feature the SQLCODE is
modified to be a value of +445. To further aid in diagnosing the problem as having been
simulated, the SQLCA field SQLERRM is modified so that the following message is
generated:
DSNT404I SQLCODE = 445, WARNING: VALUE *SQLCODE +0 -> +445* HAS BEEN TRUNCATED
DSNT418I SQLSTATE = 01004 SQLSTATE RETURN CODE
DSNT416I SQLERRD = 0 0 0 -1 0 0 SQL DIAGNOSTIC INFORMATION
DSNT416I SQLERRD = X'00000000' X'00000000' X'00000000'
X'FFFFFFFF' X'00000000' X'00000000' SQL DIAGNOSTIC
INFORMATION
DSNT417I SQLWARN0-5 = W,W,,,, SQL WARNINGS
DSNT417I SQLWARN6-A = ,,,, SQL WARNINGS
z/OS and TSO Messages
Some error messages are preceded by a z/OS or TSO error message. To display these
messages, specify the following from any command line or ISPF panel:
TSO PROFILE WTPMSG
14 Message Reference Guide (PS to ZLB)
Audit Error Messages
Audit Error Messages
The audit error messages start with prefix ERR.
An identifier is provided only for documentation and is not displayed within the error
message. The ERRx identifier is included so that you can easily report which message is
causing problems.
x
Represents the error message number.
Information in parentheses ( ) in a message is included to clarify the meaning of the
message and is not displayed in the actual message.
User Abends
On occasion, an internal error in a program may cause a user abend such as the
following:
U0299
This is not an error message but a user abend. If you receive a user abend, save the
dump information.
CA InfoTransport System Messages
System messages are displayed on the z/OS, the target machine, or both, depending on
whether you or CA InfoTransport moves the data to the target machine and executes
the server component.
CA Insight Message Formats
The following CA Insight components generate specific message formats:
■
ISPF session messages
■
Data collector and PC owner messages
■
IMOD messages
■
VTAM user interface messages
Chapter 1: Introduction 15
CA Insight Message Formats
ISPF Session
ISPF session messages occur online within the TSO or VTAM sessions and appear directly
above the command line.
As the explanations and related actions for these messages are available online (by
pressing PF1), they are not described in this guide.
All ISPF session messages have the format DBG55nnnx, where n is an integer (0-9) and x
is I, W, or E as described in Message Levels.
Note: ISPF error messages are stored in the CDBAMAPS library. Online error messages
are stored in members whose names begin with DBG55. Members contain the text and
help for ten messages. For example, DBG55078E is in CDBAMAPS(DBG5507), which
contains messages DBG55070E through DBG55079E. You can use the ISPF BROWSE
function to see the help for a particular message.
Data Collector and PC Owner
The Data Collector and PC Owner issue messages during initialization, while executing,
and during termination. These messages will appear as job log (WTO) messages and/or
in the output destination you have specified for the log files for these programs. If CA
Insight is running under Xmanager, the data collector messages will be written to the
IDLGssid file, where ssid is the DB2 subsystem ID, and the PC owner messages will be
written to the IDB2PCLG file. If the data collector and PC owner are not running under
Xmanager, the messages for each are written to the DBGPRINT file.
Most messages have the format DBGccnnnx ssid hh:mm:ss, where n or c is an integer
(0-9) and x is I, W, or E as described in Message Levels.
■
For Data Collector messages, ssid identifies the DB2 subsystem (it will be blank if
the subsystem is not yet known).
■
For PC owner messages, ssid identifies the Xmanager ID if running under Xmanager
or the PC subsystem ID (PCSSID). If not running under Xmanager, the ssid hh:mm:ss
portion of the messages will not be shown in the messages in this guide, but the
message ID and text will be shown instead.
IMOD Messages
The Global Subsystem (GSS) issues CA Insight-specific messages for IMODs. These
messages are self-explanatory and are therefore not documented. They appear in the
ISRV log.
16 Message Reference Guide (PS to ZLB)
Message Codes
Messages with the format:
■
IMHnnnI are informational.
■
IMHnnnW are issued when subsystem control blocks do not exist for the specified
DB2 subsystem. Check the names coded in the DB2SSID member in the source
library.
■
IMHnnnE are issued when program logic errors are detected. Report these
messages to CA Support.
VTAM User Interface
VTAM User Interface messages appear on the z/OS operating system in the format
DBG51nnnx, where n is an integer (0-9) and x is I (informational), W (warning), or E
(error).
Message Codes
The messages can contain reason, return, condition, and information codes for the
products and components as follows:
■
Reason codes provide more information about why the error was generated.
■
Return codes describe the processing that occurred (execution completed,
terminated, and so on) within the product or component. The following return
codes are issued routinely for the products and components:
0
Indicates processing completed successfully.
4
Indicates processing completed successfully but conditions were detected
during processing that caused warning messages to be generated.
8+
Indicates errors occurred during processing. Processing usually terminates and
cannot be completed until the errors are corrected.
■
Condition codes are returned at termination and are explained by messages written
to the message log output file.
■
Info codes (&info) provide diagnostic information used by CA Support for problem
analysis and determination.
Chapter 1: Introduction 17
Message Codes
Batch Processor Return Codes
The following return codes apply to all Batch Processor commands:
Note: Any non-zero return code is accompanied by a Batch Processor warning or error
message. A return code is generated based on the outcome of each statement.
0
Indicates processing completed successfully.
4
Indicates processing completed successfully but conditions were detected during
processing that resulted in the generation of warning messages.
8
Indicates processing errors have occurred. These conditions will affect subsequent
processing (for example, job steps might be skipped).
For Batch Processor, this return code indicates a fatal error for any SQL statement
that returns a non-zero SQLCODE (except +100) and invalid Batch Processor
commands. For some commands, the return code can be lower.
12
Indicates processing did not complete successfully and has stopped. The error must
be corrected before processing continues.
16
Indicates processing did not complete successfully due to a severe error and has
stopped. The error must be corrected before processing continues.
IBM Return Codes
When a CA utility invokes an IBM utility and the IBM utility fails, a return code may be
issued that is different than the return code that may have been issued from the CA
utility. When this occurs, a return code of 8 is issued by the CA utility to indicate that the
job failed. View the job output to find the IBM return code and resolve the error.
Media Manager Return Codes
The following return codes apply to Media Manager:
4
Indicates END OF FILE reached.
8
Indicates a GETMAIN failure.
18 Message Reference Guide (PS to ZLB)
Message Codes
12
Indicates that a LOCATE failed.
16
Indicates no data set match on generic mask.
20
Indicates a data set allocation error.
24
Indicates an open/connect error.
28
Indicates a close/disconnect error.
32
Indicates an I/O error.
36
Indicates that CHECK was issued before a GET.
40
Indicates that no MMIO blocks are available.
44
Indicates that a data set was opened with UBUF=YES.
48
Indicates that Media Manager was unable to extend the data set.
52
Indicates a user-supplied buffer size > 180*4 KB.
56
Indicates that the DIRECT requested page was not found in the current data set.
60
Indicates that a multi-page DIRECT request is not valid.
64
Indicates that a DIRECT requested page is beyond the current data set.
68
Indicates that a POINT request is invalid after the first PUT SEQUENTIAL.
72
Indicates a DEVTYPE macro error.
Chapter 1: Introduction 19
Message Codes
76
Indicates a TRKCALC macro error.
80
Indicates that the CA size is not an integral number of tracks.
84
Indicates that SVC26 failed for LISTCAT.
88
Indicates that SVC26 failed for ADDVOL.
92
Indicates that SVC26 failed for REMOVEVOL.
96
Indicates an invalid MMGR control block for [email protected]
100
Indicates a PAGESIZE error: PGSIZE <> CISIZE & CISIZE <> 4K.
104
Indicates an IEANTCR service error.
108
Indicates an IEANTRT service error.
CA InfoRefiner Return Codes
The following return codes can be generated for CA InfoRefiner:
0
Indicates processing completed successfully.
4
Indicates processing completed successfully but conditions were detected during
processing that resulted in the generation of warning messages. These conditions
do not affect subsequent processing.
8
Indicates processing errors have occurred. These conditions will affect subsequent
processing (for example, job steps might be skipped).
12
Indicates processing did not complete successfully and has stopped. The error must
be corrected before processing continues.
20 Message Reference Guide (PS to ZLB)
Message Codes
16
Indicates processing did not complete successfully due to a severe error and has
stopped. The error must be corrected before processing continues.
20
Indicates processing did not complete successfully due to a system error. The error
must be corrected before processing continues.
CA Report Facility Return Codes
The following return codes can be generated by CA Report Facility when running batch
reports:
0
Indicates processing completed successfully.
4
Indicates processing completed successfully but conditions were detected during
processing that resulted in the generation of warning messages.
8
Indicates errors have occurred during processing.
PTLDRIVM Product Driver Return Codes
The following return codes apply to the PTLDRIVM product driver:
0
Indicates processing completed successfully.
8
Indicates the program is not licensed or licensing cannot be verified.
12
Indicates an error occurred opening PTILIB.
24
Indicates a link failure.
68
Indicates a GETMAIN error.
120
Indicates no parameters passed.
Chapter 1: Introduction 21
Message Codes
128 and 130
Indicates an internal error.
131
Indicates the requested PLAN is not defined in PLANSxx.
133
Indicates the requested SSID is not defined in SETUPxx.
137
Indicates an invalid plan name.
138
Indicates the specified plan was not found.
139
Indicates an invalid output plan number or different from the input plan
140
Indicates the LOAD failed.
141
Indicates the DECP call failed.
142
Indicates the TASKLIB call failed.
143
Indicates the DEFAULTS call failed.
202
Indicates a GETMAIN failure for parmlib DCB.
203
Indicates a CCB address was not passed.
206
Indicates an invalid FREE request.
208
Indicates an unsupported API request.
211
Indicates an error opening parmlib.
212
Indicates the parmlib DD was not found.
22 Message Reference Guide (PS to ZLB)
Message Codes
213
Indicates the Batch Processor call failed.
214
Indicates Invalid parameters.
RC/Alter Return Codes
The following are RC/Alter analysis return codes:
0
Indicates processing completed successfully.
4
Indicates processing completed successfully but warnings were detected in the DDL
during processing.
8
Indicates DDL errors have occurred.
12
Indicates SQL errors have occurred.
16
Indicates miscellaneous errors have occurred.
Snapshot General Services
Snapshot General Services has one abend code (U2780) and multiple return codes for
the following modules:
■
TGAAPI
■
TGABMAN
■
TGAFDISP
■
TGALMAN
■
TGAMMGR
■
TGASCHED
■
TGASMAN
Chapter 1: Introduction 23
Message Codes
TGAAPI Return Codes
The following return codes apply to module TGAAPI:
01001001
(#TIGER macro version > max supported)
Indicates that the version of the interface used by a utility, such as CA Quick Copy, is
at a higher level than the Snapshot General Services subsystem. This can occur if
maintenance is applied that changes the interface, but the Snapshot General
Services subsystem is not re-initialized.
Reinitialize the subsystem to correct.
01001002
Indicates the RESMGR ADD failed.
01001003
Indicates the Server Module ENQ failed.
01001004
Indicates #TIGER issuer is not authorized.
01001005
Indicates an unrecognized RC from function dispatcher.
01001006
Indicates the Server Module DEQ failed.
01001007
Indicates the RESMGR DELETE failed.
01001008
Indicates the RC is not 0. Bringing up special ESTAEX.
01001009
Indicates the RC is not 0. Bringing down special ESTAEX.
0100100A
Indicates the requested subsystem (//TGR$xxxx DD DUMMY or //TGRSUBSY DD
SUBSYSxxxx in a job) was not found and is not active.
xxxx
Identifies the Snapshot General Services subsystem.
Initialize the requested subsystem or remove the DD statement to use the master
Snapshot General Services subsystem.
24 Message Reference Guide (PS to ZLB)
Message Codes
0100100B
Caller's release is not equal to Snapshot General Services subsystem release.
Indicates that the release of a utility, such as CA Quick Copy, that calls Snapshot
General Services is not the same as the release of the Snapshot General Services
subsystem. For example, this occurs if the r11.5 release of CA Quick Copy is used to
call the r11 release of Snapshot General Services. Cross-release calls to Snapshot
General Services are not supported.
Make sure that the requested Snapshot General Services subsystem and the calling
utility are from the same release.
TGABMAN Return Codes
The following return codes apply to module TGABMAN:
01005001
Indicates the block size is not a multiple of 4 KB.
01005002
Indicates TTWA storage exhausted.
01005004
Indicates TBAV not found in owning TPBE's list in DeAbstract routine.
01005005
Indicates TBEA's elem count exhausted before queue in DeAbstract routine.
01005006
Indicates TBEA's queue exhausted before elem count in DeAbstract routine.
01005007
Indicates an invalid Buffer Queue in MoveSubQueue routine.
01005008
Indicates an invalid Queue Element Count (Target) in MoveSubQueue routine.
01005009
Indicates an invalid Queue Element Count (Source) in MoveSubQueue routine.
0100500A
Indicates invalid number of unabstracted buffers in GetBufferQ routine.
Chapter 1: Introduction 25
Message Codes
TGAFDISP Return Codes
The following return codes apply to module TGAFDISP:
01004001
Indicates TTWA's stack storage has been exhausted.
01004002
Indicates SWAREQ for JFCB failed in OPEN-Read-Sequential function.
01004003
Indicates SWAREQ returned unexpected block ID in OPEN-Read-Sequential function.
01004004
Indicates no filled buffers and no I/O running in Read-Plain function.
01004005
Indicates no filled buffers after WAIT was called in Read-Plain function.
01004006
Indicates an abstracted buffer count greater than 2**31 in Read-Plain function.
01004007
Indicates no abstracted buffers when some expected in Read-Plain function.
01004008
Indicates could not find TQAV with an associated TTOB in Read-Plain function.
01004009
Indicates argument TBEA failed TQAV eyecatcher check in Put-Anchor-Plain
function.
0100400A
Indicates TBAV not found in owning TPBE's list in Put-Anchor-Plain function.
0100400B
Indicates TBEA's element count exhausted before queue in Put-Anchor-Plain
function.
0100400C
Indicates TBEA's queue exhausted before element count in Put-Anchor-Plain
function.
0100400D
Indicates I/O Scheduler failed to flush all TQQEs in Close-Thread function.
0100400E
Indicates TTCE is not on TFCB's list in Close-Thread function.
26 Message Reference Guide (PS to ZLB)
Message Codes
0100400F
Indicates TFCB is not on TLVT's list in Close-Thread function.
01004010
Indicates ENQ for SYSZTIOT failed in EnqTiot routine.
01004011
Indicates SYSZTIOT ENQ not previously issued in DeqTiot routine.
01004012
Indicates DEQ for SYSZTIOT failed in DeqTiot routine.
01004013
Indicates SVC-26 using DSName failed in MapVsam routine.
01004014
Indicates SVC-26 failed to return Catalog's ACB address in MapVsam routine.
01004015
Indicates SVC-26 failed to return Entry Type in MapVsam routine.
01004016
Indicates SVC-26 returned other than Cluster or Data in MapVsam routine.
01004017
Indicates SVC-26 failed to return NAMEDS data in MapVsam routine.
01004018
Indicates SVC-26 Cluster returned has no Data association in MapVsam routine.
01004019
Indicates SVC-26 using Data Component address failed in MapVsam routine.
0100401A
Indicates SVC-26 returned unexpected DSATRO data length in MapVsam routine.
0100401B
Indicates SVC-26 returned unexpected AMDCIREC data length in MapVsam routine.
0100401C
Indicates SVC-26 returned unexpected NAMEDS data length in MapVsam routine.
0100401D
Indicates SVC-26 returned multiple volinfo pointers in MapVsam routine.
0100401E
Indicates SVC-26 returned inconsistent extent data length in MapVsam routine.
Chapter 1: Introduction 27
Message Codes
0100401F
Indicates SWAREQ for JFCBX failed in MapPhysSeq routine.
01004020
Indicates SWAREQ returned unexpected block ID in MapPhysSeq routine.
01004021
Indicates OBTAIN-SEARCH failed in MapDASD routine.
01004022
Indicates DEVTYPE failed in MapDASD routine.
01004023
Indicates TRKCALC failed in MapDASD routine.
01004024
Indicates OBTAIN-SEEK failed in MapDASD routine.
01004025
Indicates SVC99 allocation failed in DynAlloc routine.
01004026
Indicates SVC99 failed to return DDNAME in DynAlloc routine.
01004027
Indicates SVC99 unallocation failed in DynAlloc routine.
01004028
Indicates other task awaiting lock in CloseThread function.
0100402A
Indicates UCB is unavailable in OpenRead or OpenWriteSeq function.
0100402B
Device is VIO (Virtual I/O) in OpenRead or OpenWriteSeq function.
0100402B
Indicates system does not support UCB services in FindUCB routine.
0100402E
Indicates UCBLOCK failed in FindUCB routine.
28 Message Reference Guide (PS to ZLB)
Message Codes
TGALMAN Return Codes
The following return codes apply to module TGALMAN:
01002001
Indicates TCB matched but RB did not, on lock obtain.
01002004
Indicates Lock is not held, on lock release.
01002005
Indicates TCB does not own lock, on lock release.
01002006
Indicates RB does not own lock, on lock release.
01002009
Indicates TTWA exhausted, no room for savearea.
TGAMMGR Return Codes
The following return codes apply to module TGAMMGR:
01007001
Indicates a Media Manger error occurred.
01007002
Indicates TMMI not complete after return from SUSPEND/CALLDISP.
01007003
Indicates an invalid calling sequence.
01007004
Indicates next TMMI not found on pending queue.
TGASCHED Return Codes
The following return codes apply to module TGASCHED:
01006001
Indicates TTWA storage exhausted.
01006002
Indicates block size is not a multiple of 4 KB.
01006004
Indicates output file not sequential.
Chapter 1: Introduction 29
Message Codes
01006005
Indicates input file not sequential.
01006006
Indicates the output file is not tape.
01006007
Indicates the number of abstracted buffers > 2**31.
01006008
Indicates TTCE's current disk addr < extent in SizeSeqChunk routine.
01006009
Indicates TTCE's current disk addr > extent in SizeSeqChunk routine.
0100600A
Indicates blocks-to-end-of-extent <= 0 in SizeSeqChunk routine.
0100600B
Indicates an unexpected non-zero '@Next in TTOX in IoDriver routine.
0100600C
Indicates inconsistent IOPIDs across IOSBs in IoDriver routine.
0100600D
Indicates SYSEVENT DONTSWAP failed in IoDriver routine.
0100600E
Indicates LRA for channel program start failed in VsSeqEckdIn routine.
0100600F
Indicates LRA for chanprog start failed (tape) in TapeAlgnOut routine.
01006010
Indicates media manager Put Sequential failed in MediaMgr routine.
01006011
Indicates an unexpected return code from media manager in MediaMgr routine.
01006013
Indicates LRA for TIC address failed in GetExtTcppCcw routine.
01006014
Indicates LRA for TIC address failed in GetExtTcppArg routine.
01006015
Indicates LRA for argument's address failed in BuildDx routine.
30 Message Reference Guide (PS to ZLB)
Message Codes
01006016
Indicates LRA for argument's address failed in BuildLr routine.
01006017
Indicates LRA for argument's address failed in BuildNop routine.
01006018
Indicates TPBEs exhausted before count in BuildRckd1 routine.
01006019
Indicates LRA for argument's address failed in BuildRckd1 routine.
0100601A
Indicates LRA for argument's address failed in BuildRckd1 routine.
0100601B
Indicates LRA for argument's address failed in BuildRckd1 routine.
0100601C
Indicates LRA for argument's address failed in BuildRckd1 routine.
0100601D
Indicates LRA for argument's address failed in BuildRckd1 routine.
0100601E
Indicates no I/O is pending to wait on in Wait routine.
0100601F
Indicates I/O not completed after wait in Suspend routine.
01006020
Indicates abnormal I/O completion in Complete routine.
01006021
Indicates no TTWA room for IEASMFEX savearea in Complete routine.
01006022
Indicates IEFSMFEX's RC not "0" or "4" in Complete routine.
01006024
Indicates ending "CCHH" not as expected in Complete routine.
01006025
Indicates ending "R" not as expected in Complete routine.
01006026
Indicates SYSEVENT DONTSWAP failed in Local Initialization routine.
Chapter 1: Introduction 31
Message Codes
01006027
Indicates SYSEVENT OKSWAP failed in Local Initialization routine.
01006028
Indicates invalid logical block length in BuildAlignedWrite routine.
01006029
Indicates logical block not page aligned in BuildAlignedWrite routine.
0100602A
Indicates LRA for logical buffer failed in BuildAlignedWrite routine.
0100602B
Indicates LRA for full block IDAW area failed in BuildAlignedWrite routine.
0100602C
Indicates LRA for short block IDAW area failed in BuildAlignedWrite routine.
0100602D
Indicates block count > four billion in BuildAlignedWrite routine.
0100602E
Indicates physical blocksize exceeded in SizeOutChunk routine.
0100602F
Indicates block count > four billion in SizeOutChunk routine.
01006030
Indicates expected predecessor TLBE not found in SizeOutChunk routine.
01006031
Indicates more than four billion TLBEs in loop in SizeOutChunk routine.
01006032
Indicates nothing on output queue after split in SizeOutChunk routine.
01006033
Indicates TQQE marking split point not found in SizeOutChunk routine.
01006034
Indicates more than four billion TQQEs in SizeOutChunk routine.
01006035
Indicates elements left on output queue < one in SizeOutChunk routine.
01006039
Indicates TTOX failed validation in I/O Driver Exit.
32 Message Reference Guide (PS to ZLB)
Message Codes
0100603A
Indicates TTOX failed validation in I/O Driver Exit.
0100603B
Indicates TTOX failed validation in I/O Driver Exit.
0100603C
Indicates unrecoverable error in Dev/Chan Stat during tape output.
0100603D
Indicates ambiguous overall ending status during tape output.
0100603E
Indicates ending CCW address less than zero during tape output.
0100603F
Indicates CCW did not use IDAWs during tape output.
01006040
Indicates first IDAW's addr not reverse-translated during tape output.
01006041
Indicates link from IDAW area .NE. ending CCW during tape output.
01006042
Indicates TLBEs incomplete for block written during tape output.
01006043
Indicates unexpected TQQE queue end (TQAV search) during tape output.
01006044
Indicates unexpected TQQE queue end (easy split) during tape output.
01006045
Indicates TLBE BCT-counter register wrapped during tape output.
01006046
Indicates residual TLBE queue size < zero during tape output.
01006047
Indicates TQQE BCT-counter register wrapped during tape output.
01006048
Indicates an unexpected null pointer to last comp TQQE during tape output.
01006049
Indicates completed TQQE queue size .LE. zero during tape output.
Chapter 1: Introduction 33
Message Codes
0100604A
Indicates blocks written TLBE BCT-counter wrapped during tape output.
0100604B
Indicates new VOLSER .NE. preallocated TVDEs during tape output.
0100604C
Indicates LRA for argument's address failed during tape input.
0100604D
Indicates LRA for argument's address failed during tape input.
0100604E
Indicates LRA for argument's address failed during tape input.
0100604F
Indicates LRA for argument's address failed during tape input.
TGASMAN Return Codes
The following return codes apply to module TGASMAN:
01003001
Indicates requested amount > pallet maximum in ObtainCtl routine.
01003002
Indicates requested amount > pallet maximum in ObtainCtlBelow routine.
01003003
Indicates requested amount > pallet maximum in ObtainObj routine.
01003004
Indicates number requested not positive in ObtainObjMult routine.
01003005
Indicates negative remaining bytes in free parcel in ObtainObjMult routine.
01003006
Indicates negative remaining parcels to be gotten in ObtainObjMult routine.
01003007
Indicates request amount > pallet maximum in ObtainObjMult routine.
01003008
Indicates number requested not positive in ObtainBfsePage or ObtainBfseMultPage
routine.
34 Message Reference Guide (PS to ZLB)
Message Codes
01003009
Indicates negative remaining bytes in free parcel in ObtainBfsePage or
ObtainBfseMultPage routine.
0100300A
Indicates negative remaining parcels to be gotten in ObtainBfsePage or
ObtainBfseMultPage routine.
0100300B
Indicates request amount > pallet maximum in ObtainBfsePage or
ObtainBfseMultPage routine.
0100300C
Indicates overlapping parcels detected in ReleaseObjList routine.
0100300D
Indicates overlapping parcels detected in ReleaseObjList routine.
0100300E
Indicates overlapping parcels detected in ReleaseObjList routine.
0100300F
Indicates overlapping parcels detected in ReleaseObjList routine.
01003010
Indicates overlapping parcels detected in ReleaseObjList routine.
01003011
Indicates overlapping parcels detected in ReleaseObjList routine.
01003012
Indicates overlapping parcels detected in ReleaseObjList routine.
01003013
Indicates overlapping parcels detected in ReleaseObjList routine.
01003014
Indicates overlapping parcels detected in ReleaseObjList routine.
01003015
Indicates pallet not found for parcel's address in ReleaseObjList routine.
01003016
Indicates overlapping parcels detected in ReleaseObjList routine.
01003017
Indicates overlapping parcels detected in ReleaseObjList routine.
Chapter 1: Introduction 35
Message Codes
01003018
Indicates overlapping parcels detected in ReleaseObjList routine.
01003019
Indicates overlapping parcels detected in ReleaseObjList routine.
0100301A
Indicates FPD's parcel length > pallet length in ReleaseObjList routine.
0100301B
Indicates TTWA stack space exhausted in Entry Keep routine.
0100301C
Indicates pallet not found for released parcel in ComRelease routine.
0100301D
Indicates released and free parcels have same address in ComRelease routine.
0100301E
Indicates overlapping parcels in ComRelease routine.
0100301F
Indicates overlapping parcels in ComRelease routine.
01003020
Indicates argument TSPD not found on TOPQ in FreeObjPal routine.
01003021
Indicates argument TSPD not empty in FreeObjPal routine.
01003022
Indicates free parcel size .NE. pallet size in FreeObjPal routine.
01003023
Indicates Page Extent Table exhausted in FreeObjPal routine.
01003024
Indicates Invalid Page Status Map entry in FreeObjPal routine.
01003025
Indicates Page Services Area exhausted in PageFix routine.
01003026
Indicates Page Services Area exhausted in PageUnFix routine.
01003027
Indicates pallet not found for parcel in PrepFixList routine.
36 Message Reference Guide (PS to ZLB)
Message Codes
01003028
Indicates Page Extent Table exhausted in PrepFixList routine.
01003029
Indicates Parcel page is already marked "fixed".
0100302A
Indicates requested amount > pallet maximum in ObtainSqa routine.
0100302B
Indicates corrupted TSPD or queue linkage in DeInitialize routine.
0100302C
Indicates STORAGE RELEASE failed in DeInitialize routine.
0100302D
Indicates queue elements disagree with count in DeInitialize routine.
0100302E
Indicates count disagrees with queue elements in DeInitialize routine.
01003031
Indicates an invalid function.
Thread Termination\Dynamic DSNZPARM Return and Reason Codes
The following return codes apply when terminating threads in batch:
0
Indicates processing completed successfully.
4
Indicates one or more threads was not terminated.
8
Indicates no qualifying threads could be found, therefore no threads were
terminated.
12
Indicates no SYSIN DD card was present or there was an error in the control card.
No threads were terminated.
Chapter 1: Introduction 37
Message Codes
The following return and reason codes are provided when a thread termination fails.
These codes are listed in the log record for the termination attempt.
■
For return code 4, the following reason codes are generated:
1
Indicates the thread is invalid. The thread may have already terminated or the
thread's task control block (TCB) may have changed.
2
Indicates DB2 termination was specified but the thread was not executing
within DB2.
3
Indicates the thread originated from a system address space. Threads that
originate from a system address space are not terminated.
4
Indicates the address space where the thread was executing was already
terminating.
5
Indicates the thread's TCB was already terminating.
6
Indicates DB2 termination was specified but a DB2 termination had already
been requested.
7
Indicates the thread was not terminated because a DB2 termination was
specified but the DB2 termination failed.
10
Indicates you requested to kill a distributed thread. That feature is not
supported for this version of DB2.
■
For return code 8, reason code 8 indicates a z/OS termination was specified but the
termination attempt failed.
■
For return code 12, reason code 9 indicates access to the thread was denied by the
external security system.
CA Bind Analyzer Return Codes
The following components generate return codes for CA Bind Analyzer:
■
Precompiler
■
Binder
38 Message Reference Guide (PS to ZLB)
Message Codes
■
DBRM Compare Facility
■
Catalog Compare Facility
■
DBRM Rebuild
Precompiler Return Codes
A return code is issued indicating the status of the DBRM compare. Unique return code
values indicate when a bind is necessary. By default, the precompiler sets 0 (execution
successful) or 4 (execution successful, but caused warning messages). However, the 0
and 4 values do not tell you when a bind is necessary.
Two unique values (1 and 3) indicate when binds are not necessary. The values of 0 and
4 are still set, but indicate when binds are necessary.
The following list contains the return codes for the Precompile step:
0
Indicates processing completed successfully. A bind is necessary.
1
Indicates processing completed successfully. A bind is not necessary.
3
Indicates processing completed successfully but conditions were detected during
processing that resulted in the generation of warning messages. A bind is not
necessary.
4
Indicates processing completed successfully but conditions were detected during
processing that resulted in the generation of warning messages. A bind is necessary.
16
Indicates that an error occurred opening PTILIB DD or accessing CDBADBRM.
If IBM precompile errors are encountered, appropriate return code values are returned
directly from DB2.
Binder Return Codes
Following are the return codes for the BIND step:
0
Indicates processing completed successfully.
4
Indicates a PARM error. The default value is used.
Chapter 1: Introduction 39
Message Codes
8
Indicates fatal parameter error or data set allocation error (UTILITY CHECRC error).
12
Indicates error accessing BPIIPT DD or PTIDBRMO (invalid resynch data).
16
Indicates the product expired, a fatal I/O error occurred, unable to call the Batch
Processor, or unable to open PTILIB.
Note: If the Batch Processor encounters errors, those return code values are
returned directly from the Batch Processor.
DBRM Compare Facility Return Codes
The following lists the return codes for the DBRM Compare Facility:
0
Indicates processing completed successfully.
4
Indicates one or both of the CDBADBRM libraries contained no members to
compare. No reports are generated if this return code is received.
8
Indicates one or more of the parameters passed in the PARM= field contains an
error. Processing continues, but the incorrect parameters are set to their defaults
and no bind or copy statements are generated.
16
Indicates bad file open.
68
Indicates insufficient storage.
Catalog Compare Facility Return Codes
The following lists the return codes for the Catalog Compare Facility:
0
Indicates processing completed successfully.
4
Indicates the selection criteria for the CDBADBRM library created an empty list;
therefore, no reports are generated.
40 Message Reference Guide (PS to ZLB)
Message Codes
8
Indicates one or more of the parameters passed in the PARM field contains an
error. Processing continues, but the incorrect parameters are set to their defaults
and no bind or copy statements are generated.
16
Indicates bad file open.
68
Indicates insufficient storage.
DBRM Rebuild Return Codes
The following lists the return codes for the DBRM Rebuild:
0
Indicates processing completed successfully.
4
Indicates DBRM not rebuilt. No action taken.
8
Indicates one or more of the parameters passed in the PARM= field contains an
error. Processing continues, but the incorrect parameters are set to their defaults.
16
Indicates bad file open.
68
Indicates insufficient storage.
CA Insight Return Codes
The following components generate return codes for CA Insight:
■
Batch report writer
■
Batch user interface
■
Data collector
■
PC owner routine
Chapter 1: Introduction 41
Message Codes
Batch Report Writer Return Codes
A condition code is returned at termination. Normally a code of zero is returned even
though the Batch Report Writer may have terminated due to some error condition. The
error condition would be explained by messages written to the message log output file
(DBGPRINT DD). Several conditions may have caused termination without producing
error messages. These conditions are indicated by non-zero codes.
The condition codes returned are:
0
Indicates the program terminated normally or for some error condition indicated by
messages in the message log output file (DBGPRINT DD).
12
Indicates error message issued, no report generated
36
Indicates the message log output file (DBGPRINT DD) or DBGIN DD statement
missing.
44
Indicates an ABEND occurred but was intercepted by the ESTAE exit routine.
52
Indicates an error was encountered while processing the startup parameters. Check
the message log output file (DBGPRINT DD) for error messages.
99
Indicates the product code has expired or is invalid.
Batch User Interface Return Codes
A condition code is returned at termination. Normally a code of zero is returned even
though the Batch User Interface may have terminated due to some error condition. The
error condition would be explained by messages written to the message log output file
(DBGPRINT DD).
0
Indicates processing completed successfully.
>0
Indicates processing was not successful.
42 Message Reference Guide (PS to ZLB)
Message Codes
Data Collector Return Codes
The Data Collector returns a condition code every time it is terminated. Normally, it
returns a code of zero even if the Data Collector terminated for an error condition. The
error condition is then explained by messages written to the message log output file.
However, any one of several conditions may cause the Data Collector to terminate
without producing error messages. These conditions are indicated by non-zero codes. In
these cases, the condition codes returned are as follows:
0
Indicates the program terminated. An error, which may have caused the
termination, is indicated by a message on the message log output file.
32
Indicates an error occurred processing parameters specified in the PARM field of
the EXEC statement.
36
Indicates the message log output file or DBGIN DD statement is missing.
44
Indicates an ABEND occurred but was intercepted by the ESTAE exit routine.
52
Indicates an error was encountered while processing the startup parameters. Check
the message log output file for error messages.
99
Indicates your product code has expired or is invalid.
PC Owner Routine Return Codes
A condition code is returned by the program at termination. Most of the conditions
producing a non-zero code will also produce a message on the message log output file.
Each code specifies a fairly unique condition, so if the message log output file has been
put to a throwaway output class, the cause of the termination should be apparent from
the codes. The codes produced are:
0
Indicates the program terminated normally without errors.
4
Indicates no virtual storage available for a GETMAIN, or a module not found for a
BLDL.
Chapter 1: Introduction 43
Message Codes
8
Indicates no real storage page available for a SQA GETMAIN request, or an I/O error
occurred in a PDS directory for a BLDL.
12
Indicates a GETMAIN error occurred obtaining SQA storage for the PC number
table.
16
Indicates the LOAD failed for the module containing the CMS routine.
20
Indicates an error occurred when the ETCRE macro was executed.
24
Indicates an ENQUEUE error was encountered when the ENQ was issued for an
internal enqueue.
32
Indicates an error occurred processing the input parameters.
36
Indicates the Message log output file DD statement missing.
44
Indicates an ABEND occurred but was intercepted by the ESTAE exit routine.
48
Indicates the CMS Owner program was already started when an attempt was made
to start the program.
52
Indicates an error was encountered when the GQSCAN macro was issued.
60
Indicates an error occurred when the ETCON macro was issued.
64
Indicates a GETMAIN error occurred obtaining storage for a program control block.
68
Indicates an error occurred obtaining storage for a SSCVT.
44 Message Reference Guide (PS to ZLB)
Message Codes
72
Indicates the system LX value could not be obtained.
76
Indicates that the system is configured with ALLOWUSERKEYCSA(NO) and
KEY8CSA=YES is specified in the PC task parameters. You cannot specify
KEY8CSA=YES on a system defined with ALLOWUSERKEYCSA(NO). You must specify
KEY8CSA=NO or change the system setting to ALLOWUSERKEYCSA(YES).
CA Database Analyzer for DB2 Return Codes
The following return codes apply to CA Database Analyzer for DB2:
04
Indicates one of the following conditions has occurred:
■
Audit failure. The AUDIT_ERROR parmlib parameter lets you override the
return code value of 4 when the following audit errors occur: All, 24, 36, or 37.
■
When MAINT=F is specified and the Activation indicator is not equal to I, the
MAINT=F request will be ignored and Auto-Stats Deletion will not execute (It
will perform the same as MAINT=N). Message RD03001W is issued.
■
Tablespace was BYPASSED because it contained no tables.
■
No action JCL generated other than a fill member. Check setting of
NO_ACTJCL_RC parmlib parameter.
■
SQL error occurred logging an audit error to PTLOG_MAIN_1500 or
PTLOG_RDAMSG table; processing will continue.
■
SPACEMAP scan was selected for an extract that has the Auto-Catalog Update
(ACU) feature selected. ACU is bypassed.
08
Indicates one of the following conditions has occurred:
■
SQL error in reports.
■
PTIRPT DD card missing.
■
STOP entered for console prompt, or an internal error forced processing to
stop prematurely.
■
INCOMPLETE message for any object.
■
SQL error storing stats.
12
Indicates the PTIIPT DD has no cards or is invalid.
Chapter 1: Introduction 45
Message Codes
16
Indicates one of the following conditions has occurred:
■
Program not licensed, or unable to verify license.
■
STEPLIB not authorized.
■
Error processing volume data.
■
Fatal error in subtask (collection, stats storing); usually failed getmain.
■
LOAD failure for a load module RALxxxx.
■
Getmain failure (Program could not allocate needed storage) for an internal
control block. Increase REGION size or make extract smaller.
■
Error connecting to stats SSID, or opening RDPSxxxx plan (used in action JCL
generation for condition action SQL).
■
SSID not found in SETUP parmlib member (SSID in first control card in column
18).
■
CATALIAS not found in SETUP member for SSID (same as above).
■
DB2 connection failure during catalog update.
■
Other fatal errors.
CA Detector Return Codes
The following return codes apply when the batch reporting facility uses CA Detector:
0
Indicates processing completed successfully.
4
Indicates no data was found matching report criteria. An empty report has been
generated.
8
Indicates warning messages have been issued and the report has been generated.
Note: Review warning messages and reports to ensure that the report contains all
of the requested data.
12
Indicates error messages have been issued. The report has not been generated.
If you encounter return codes of 4 or 8, you might also receive partial output. Review
the WTO messages to determine the validity of the information.
46 Message Reference Guide (PS to ZLB)
Message Codes
CA Fast Check Return Codes
One of the following return codes displays after each CA Fast Check job execution:
0
Indicates processing completed successfully. No errors were detected.
4
Indicates errors have been detected in the tablespace or index. Review the output
messages for more information. Possible errors include:
■
Child rows have no corresponding parent rows
■
Index entries have no corresponding data rows
■
Data rows have no corresponding index entries
8
Indicates problems occurred during the check processing that must be investigated
and resolved. See the error messages in the job output for a description of the error
encountered. Possible errors include:
■
Syntax errors in the job stream
■
Data set allocation failed
■
SORT ran out of work space
16
Indicates errors have occurred. See the CA Fast Check XMESSAGE written for futher
details of the error.
68
Indicates insufficient storage.
CA Fast Recover Return Codes
One of the following return codes displays after each CA Fast Recover job execution:
0
Indicates the recovery and associated tasks all completed successfully.
4
Indicates the recovery completed successfully, but a warning flag has been set. Look
at the job output messages for warnings, such as (but not limited to) one of the
following:
■
Copy pending flag set
■
No indexes found for INDEX ALL recovery
Chapter 1: Introduction 47
Message Codes
■
A TOCOPY image copy is SHRLEVEL CHANGE
■
Unused candidate volumes could not be removed after the recovery
■
Quick Copy failed for a tablespace
■
Indexes were put into recover pending after a tablespace recovery
8 (and higher)
Indicates problems occurred during the recovery. They must be investigated and
resolved before the recovery is considered complete. Error messages in the job
output describe the error encountered. Examples of failures are:
■
Data set ran out of space
■
Data set DELETE/DEFINE failed
■
SORT ran out of space
■
An image copy was missing
■
An archive log data set was missing
CA Log Analyzer Return Codes
The apply program issues return codes indicating the status of the apply. The following
lists the return codes for the Log Apply:
0
Indicates processing completed successfully.
4
Indicates SQL errors have occurred and the input file is empty. Warning messages
issued.
8
Indicates table not found and discard limits have been exceeded. Processing
terminated.
16
Indicates a fatal error. Processing terminated.
48 Message Reference Guide (PS to ZLB)
Message Codes
CA Plan Analyzer Return Codes
The following lists the CA Plan Analyzer return codes:
0
Indicates processing completed successfully.
4
Indicates processing completed successfully but conditions were detected during
processing that resulted in the generation of warning messages.
8
Indicates a processing error has occurred.
12
Indicates the HVERSION conversion limit has been exceeded.
16
Indicates a Batch Processor error has occurred.
32
Indicates a parameter list error.
68
Indicates a GETMAIN error.
99
Indicates an SQL error.
CA Quick Copy Return Codes
The following information documents the CA Quick Copy API reason codes and their
descriptions:
0
Indicates processing completed successfully.
2
Indicates the copy completed with PREVIEW OPTION or a catalog error (Not
Cataloged 2).
4
Indicates the copy completed with warnings. Warning level messages are
generated.
Chapter 1: Introduction 49
Message Codes
8
Indicates the copy encountered errors. Copy job was terminated before
completion. Error messages are generated that identify the problem.
16
Indicates the copy encountered severe errors. Copy job was terminated before
completion. Error messages are generated that identify the problem.
20
Indicates an invalid API Control block (#COPY) address.
21
Indicates an invalid API function identifier (#COFUNC).
22
Indicates a Getmain Error detected in API module UTLQC#1.
23
Indicates a parser (UTLQCPSE) ATTACH error.
24
Indicates a UTLQC#2 LOAD error.
25
Indicates the API INLINE ATTACH Termination ECB has been posted early. This could
indicate that a syntax error has been detected in the PQC parser (UTAQCPSE) or an
error has occurred in the first stage of PQC driver processing. Other errors that
could occur are a system abend or a user abend.
26
Indicates a CA Quick Copy Parser or Driver error.
27
Indicates the CA Quick Copy API initialization (#COPY INIT) has not been invoked or
an error has occurred during API initialization.
28
Indicates an invalid Page Size specified for INLINE processing.
29
Indicates an invalid API internal (#COPYI) Control Block address.
30
Indicates an invalid QCPX (#[email protected]) Control Block address.
50 Message Reference Guide (PS to ZLB)
Message Codes
31
Indicates a write error has been detected by a CA Quick Copy writer task during API
INLINE processing.
32
Indicates an invalid ECB contents when trying to compare and swap the PQC INLINE
Reader ECB (#[email protected]).
33
Indicates an INLINE writer task abend has occurred.
34
Indicates the STIMERM function cannot be performed.
35
Indicates a CA Quick Copy error has occurred (PQC ECB posted).
36
Indicates a zero RAMTS address (#[email protected]) has been passed.
37
Indicates a zero RAMIX address (#[email protected]) has been passed.
38
Indicates an invalid RAMTS (TS_ID) header ID.
39
Indicates an invalid RAMIX (IX_ID) header ID.
40
Indicates a zero GLEB address (#[email protected]) has been passed.
41
Indicates an invalid GLEB identifier (GLEB_ID).
42
Indicates the PQC API does not support the copy of IBM databases.
43
During a #COPY INIT call the [email protected] parameter was specified but a previous
#COPY PREINIT call had not been issued.
44
Indicates an error was detected during #COPY PREINIT processing.
Chapter 1: Introduction 51
Message Codes
45
Indicates the ATTACH termination ECB used for PQC PREINIT processing has been
posted early. This could be due to an error encountered in the PQC parser.
46
Indicates an invalid VCAT specified.
47
Indicates an invalid INSTANCE NODE specified.
48
Indicates an invalid PARTITION NODE specified.
49
Indicates the CA Quick Copy API does not support more than one object in a list.
50
Indicates an invalid SYNTAX option specified.
51
Indicates an invalid RESTART option specified.
52
Indicates an invalid DB2AUTH option specified.
53
Indicates an invalid ENQ option specified.
54
Indicates an invalid MSG option specified.
55
Indicates an invalid ETM option specified.
56
Indicates an invalid TERMTYP option specified.
57
Indicates an invalid COPYBUF option specified.
58
Indicates an invalid IDCMENQ option specified.
59
Indicates an invalid ALTSPCE option specified.
52 Message Reference Guide (PS to ZLB)
Message Codes
60
Indicates an invalid API control block (#COPY) address.
61
Indicates a UTLQC#1 LOAD error.
62
Indicates the UTLQC#2 address (#[email protected]) =zero.
63
Indicates an invalid environment (standard call) for #COPY CALL (INLINE).
64
Indicates an invalid environment for #COPY SRPOST. The required environment
must be standard copy ATTACH.
65
Indicates SYSCOPY Registration ECB has already been posted.
67
Indicates an invalid environment for #COPY SRILINE.
68
Indicates an invalid SRIREG option specified.
69
Indicates an invalid SRITYPE option specified.
70
Indicates an invalid SHRLVL option specified.
71
Indicates an invalid SUPACSS option specified.
72
Indicates an invalid CPYFLGS option specified.
80
Warning, #COPY INIT bypassed (in PREINIT Mode).
100
Indicates the CA Quick Copy API does not support SNAPSHOTACCESS YES.
103
Indicates the CA Quick Copy API does not support concurrent copies.
Chapter 1: Introduction 53
Message Codes
CA Rapid Reorg Return Codes
One of the following return codes displays after each CA Rapid Reorg job execution:
0-4
Indicates all objects are fine.
8
Indicates a failure occurred during the unload phase. No objects were reorganized.
The original source VSAM data sets were restarted and the restart record has been
deleted. If DATA-AVAILABLE HIGH was used, the target VSAM data set (.B001) was
deleted. The original objects are exactly the same as they were before the job
started. See the messages output with the job for more information.
10
Indicates all data sets were reloaded but a subfunction such as QUICKCOPY or
PDASTATS failed. The restart record was deleted and the job is not restartable. See
the messages output with the job for more information.
11
Indicates a -STOP was issued but the object remained in -STOP PENDING status for
an extended length of time. Check the value of STOP-LIMIT to determine how long
to wait before terminating processing.
12
Indicates a failure occurred during the reload. The job is restartable for
DATA-AVAILABLE NORMAL or for DATA-AVAILABLE HIGH with RESTART-ONERROR
YES. If RESTART-ONERROR NO was specified (with DATA-AVAILABLE HIGH), the
target data set and restart record were deleted. The job must be rerun from the
beginning. See the messages output with the job for more information.
16
Indicates a failure occurred during the reload and the job is not restartable. The
tablespace, index, or both need to be recovered. The reorg job is not restartable.
See the messages output with the job for more information.
CA RC/Migrator Return Codes
The following are CA RC/Migrator analysis return codes. Return codes greater than 4
stop execution.
0
Indicates processing completed successfully.
4
Indicates processing completed successfully but conditions were detected during
processing that resulted in the generation of warning messages. Warning in DDL.
54 Message Reference Guide (PS to ZLB)
Message Codes
8
Indicates an error occurred in the DDL.
12
Indicates an SQL error has occurred.
16
Indicates miscellaneous errors have occurred.
68
Indicates a GETMAIN error has occurred.
CA RC/Query Return Codes
The following codes are CA RC/Query analysis return codes:
0
Indicates processing completed successfully.
22
Indicates the SSN not specified.
23
Indicates the VAR value or TABLE parameter is missing.
24
N/A
25
Indicates an unsupported column type has been specified.
26
N/A
27
Indicates a TBCREATE or TBOPEN error.
28
N/A
29
Indicates TBTOP failed.
30
Indicates an error occurred while initializing DB2 (for example, invalid plan).
Chapter 1: Introduction 55
Message Codes
31
N/A
32
Indicates the subsystem ID is not specified.
33-36
N/A
37
Indicates a failure to open a DB2 table.
39
Indicates unknown parameters.
40
Indicates data set and SQL string specified.
41
Indicates data set or SQL string required.
42
N/A
43
N/A
44
Indicates DWNPW value missing.
45
Indicates SQLID value missing.
46
Indicates DSNVS or DSNPW specified without SQLDSN.
47
Indicates the COMMIT value is not = YES or NO.
48
Indicates an LMINIT problem.
49
N/A
50
Indicates an LMOPEN problem.
56 Message Reference Guide (PS to ZLB)
Message Codes
51
Indicates the data set is not partitioned but a member is specified.
52
Indicates the data set partitioned by member not specified.
53
Indicates the data set is in use.
54
Indicates the SQL string is too long.
55
N/A
56
Indicates the data set member does not exist.
57
Indicates an unknown data set error.
58
N/A
59
N/A
60
Indicates -KEY value missing or not = '1'.
61
N/A
62
N/A
63
Indicates the DB2 table has too many columns.
64
Indicates the ROWS value missing or not numeric.
Chapter 1: Introduction 57
Message Codes
CA RC/Secure Return Codes
The following are possible CA RC/Secure return codes:
0
Indicates processing completed successfully.
4
Indicates one of the following errors has occurred:
■
No authorizations to grant or revoke.
■
Not authorized for DB2ID or department.
12
Indicates one of the following errors has occurred:
■
OPEN if CA Program Lib failed.
■
Invalid parameter passed to SQL processor.
■
Access not allowed for user ID.
16
Indicates the BLDL failed.
20
Indicates the product license expired.
24
Indicates an invalid parameter passed to #MAIN.
28
Could not load module.
32
Indicates one of the following:
■
ATTACH to #DRIV failed.
■
CONNECT to DB2 failed.
■
Not APF authorized.
36
Indicates an execution proc error.
48
OPEN of APLFILE failed.
58 Message Reference Guide (PS to ZLB)
Message Codes
68
Indicates a GETMAIN error.
99
Indicates an SQL error in tree build.
CA SQL-Ease Return Codes
The following components generate return codes for CA SQL-Ease:
■
Enhanced explain
■
Enhanced explain exceptions
■
Highest value
Enhanced Explain Return Codes
The Enhanced Explain feature passes a single return code to the batch processor. This
code is the highest code of the following:
■
The severity codes set through the Expert System Rules reports
■
The Enhanced Explain exception return codes
Enhanced Explain Exceptions Return Codes
You can specify the return codes for three different types of Enhanced Explain
exceptions. These return codes give you immediate feedback on your EXPLAIN
processing.
The following list describes the Enhanced Explain exception return codes:
EXPLRC1
There are no SQL statements for Enhanced Explain to process.
EXPLRC2
SQL errors occurred during the EXPLAIN.
EXPLRC3
General errors occurred during Enhanced Explain processing.
These user-defined return codes are defined in the parmlib at installation. You can set
the codes to any number between 0 and 4095. The default is 0.
Chapter 1: Introduction 59
Message Codes
Highest Value Return Code Issued
CA SQL-Ease considers the following codes before issuing the return code for an SQL
statement.
■
The Expert System Rules report severity codes
■
The Enhanced Explain exception return codes
After reviewing these codes, CA SQL-Ease returns the highest value. It is important to
keep this in mind when setting your return and severity code values.
Utilities Index Compression Service Return and Reason Codes
The following return and reason codes can be generated when CA utilities invoke the
Index Compression Service:
10
Indicates that the compression service failed.
This return code can be accompanied by the following reason codes, which describe
the specific failure that was detected:
C8
Indicates that the DB2 index compression service failed to compress an index
page.
CC
Indicates that the internal LCMOD service failed during initialization.
D0
Indicates that the internal LCMOD service failed to load the DB2 index
compression service.
D4
Indicates that the internal LCMOD service failed while terminating the DB2
index compression service.
D8
Indicates that the internal LCMOD service failed during IXD initialization
processing.
DC
Indicates that the internal LCMOD service failed during IXD initialization
processing.
60 Message Reference Guide (PS to ZLB)
Message Codes
E0
Indicates that the internal LCMOD service failed during IXD termination
processing.
E4
Indicates that the DB2 IXD build service failed.
64
Indicates that the LOAD for the CSLCPINX compression service manager failed.
68
Indicates an invalid request to the CSLCPINX compression service manager.
Utilities Index Compression Size Service Return and Reason Codes
The following return and reason codes can be generated when CA utilities invoke the
Index Compression Size Service:
08
Indicates that an error occurred during the service call.
This return code can be accompanied by the following reason codes, which describe
the specific error encountered:
14
Indicates that a storage obtain failed.
15
Indicates that a call to UTA$SD for current version definitions failed.
16
Indicates that an unknown key version was encountered.
0C
Indicates that the request could not be processed because the processing context is
incomplete or invalid.
This return code can be accompanied by the following reason codes, which describe
the specific error encountered:
01
Indicates that the parameter list is not recognized.
02
Indicates that the request code is not recognized.
03
Indicates that the parameter list version is not supported.
Chapter 1: Introduction 61
Message Codes
04
Indicates that the current service call cannot be processed because the service
has not yet been initialized.
05
Indicates an invalid GLEB control block.
06
Indicates an invalid RAMIX control block.
07
Indicates an invalid index page.
08
Indicates an invalid header page.
09
Indicates an invalid directory page.
0A
Indicates an invalid key number.
0B
Indicates that a key number is out of range.
10
Indicates that the Index Compression Size API is not available.
Utilities Restart/Retry Return and Reason Codes
The following return codes can be generated when multiple CA utilities try to use the
same restart rows:
0
Indicates processing completed successfully. Results expected.
4
Indicates processing completed successfully but conditions were detected during
processing that resulted in the generation of warning messages.Unexpected results
have occurred.
8
Indicates processing errors have occurred. These conditions will affect subsequent
processing (for example, job steps might be skipped). The function fails.
62 Message Reference Guide (PS to ZLB)
Message Codes
The following reason codes can be generated when two or more CA utilities try to use
the same restart rows:
. 81 (X'00000051')
Indicates an unknown type of error.
. 82 (x'00000052')
Indicates GETMAIN failed.
. 83 (x'00000053')
Indicates FREEMAIN failed.
. 84 (x'00000054')
Indicates BUILD UTILID failed.
. 85 (x'00000055')
Indicates BUILD AUTHID failed.
. 86 (x'00000056')
Indicates an invalid utility name has been passed.
. 87 (x'00000057')
Indicates the SSID is not found in SSCT51-Unknown type of error.
. 88 (x'00000058')
Indicates a validation error.
. 89 (x'00000059')
Indicates an SQL error.
. 90 (x'0000005A')
Indicates SQL not found.
. 91 (x'0000005B')
Indicates no dynamic SQL passed.
. 92 (x'0000005C')
Indicates SHRLV is not E, R, or U.
. 93 (x'0000005D')
Indicates the statement level enqueue failed.
Chapter 1: Introduction 63
Chapter 2: PS to PTUIX
PS Messages
Messages with the PS prefix are generated from the Statistics Manager component of
CA Plan Analyzer.
PS000I
WELCOME TO STATISTICS MANAGER V1.0, PRESS PF1/13 FOR HELP.
Reason:
Statistics Manager welcome message.
Action:
Be sure to fill in profile information before using the product. You can do this by
selecting option P from the Products Main Menu.
PS002E
INVALID VALUE. VALID VALUES ARE Y - YES AND N - NO.
Reason:
You have entered an invalid option for the tablespace PCTFREE Statistics Manager
profile variable.
Action:
Valid values are as follows:
■
Y-Propagate Statistics using the tablespace PCTFREE value.
■
N-Do not use the tablespace PCTFREE value in calculating statistics.
Chapter 2: PS to PTUIX 65
PS Messages
PS003E
INVALID VALUE. VALID VALUES ARE Y - YES AND N - NO.
Reason:
You have entered an invalid option for the tablespace FREEPAGE Statistics Manager
profile variable.
Action:
Valid values are as follows:
■
Y-Propagate Statistics using the tablespace FREEPAGE value.
■
N-Do not use the tablespace FREEPAGE value in calculating statistics.
PS004E
INVALID VALUE. VALID VALUES ARE Y - YES AND N - NO.
Reason:
You have entered an invalid option for the tablespace SEGSIZE Statistics Manager profile
variable.
Action:
Valid values are as follows:
■
Y-Propagate Statistics using the tablespace SEGSIZE value.
■
N-Do not use the tablespace SEGSIZE value in calculating statistics.
PS005E
INVALID VALUE. VALID VALUES ARE Y - YES AND N - NO.
Reason:
You have entered an invalid option for the tablespace SEGSIZE Statistics Manager profile
variable.
Action:
Valid values are as follows:
■
Y-Propagate Statistics using the tablespace SEGSIZE value.
■
N-Do not use the tablespace SEGSIZE value in calculating statistics.
66 Message Reference Guide (PS to ZLB)
PS Messages
PS006E
INVALID VALUE. VALID VALUES ARE Y - YES AND N - NO.
Reason:
You have entered an invalid option for Statistics Manager profile variables.
Action:
Valid values are as follows:
■
Y-Propagate Statistics using the tablespace SEGSIZE value.
■
N-Do not use the tablespace SEGSIZE value in calculating statistics.
PS007E
INVALID VALUE. VALID VALUES ARE Y - YES AND N - NO.
Reason:
You have entered an invalid option for Statistics Manager profile variables.
Action:
Valid values are as follows:
■
Y-Propagate Statistics using the tablespace SEGSIZE value.
■
N-Do not use the tablespace SEGSIZE value in calculating statistics.
PS008E
INVALID VALUE. VALID VALUES ARE Y - YES AND N - NO.
Reason:
You have entered an invalid option for Statistics Manager profile variables.
Action:
Valid values are as follows:
■
Y-Propagate Statistics using the tablespace SEGSIZE value.
■
N-Do not use the tablespace SEGSIZE value in calculating statistics.
Chapter 2: PS to PTUIX 67
PS Messages
PS009E
INVALID VALUE. VALID VALUES ARE 01 - 99.
Reason:
You have entered an invalid option for Statistics Manager profile variables.
Action:
Valid values are as follows:
■
Y-Propagate Statistics using the tablespace SEGSIZE value.
■
N-Do not use the tablespace SEGSIZE value in calculating statistics.
PS010E
AN UNEXPECTED INTERNAL ERROR CONDITION HAS OCCURRED. PRESS HELP.
Reason:
Statistics Manager encountered an internal processing condition that was unexpected
or undesirable, or both. You should report this error to Technical Support. There might
be some diagnostics information that you should save (by screen prints or by writing it
down exactly as shown) and give to Technical Support.
Action:
For assistance, contact CA Support at http://ca.com/support.
PS011E
INSUFFICIENT VIRTUAL STORAGE TO CONTINUE. PRESS HELP FOR MORE INFO.
Reason:
Statistics Manager could not obtain enough virtual storage to continue processing your
request.
Action:
Possible solutions to this condition are as follows:
■
Exit any split screen sessions that might be in effect.
■
Increase the region size of your TSO LOGON procedure. We recommend a region
size of between 2048 to 3072 KB.
68 Message Reference Guide (PS to ZLB)
PS Messages
PS012E
YOU HAVE ENTERED AN INVALID COMMAND. PRESS HELP FOR MORE INFO.
Reason:
You have entered an invalid command in the command line for the panel.
Action:
Enter ? in the command line to get a list of available Statistics Manager commands valid
for this panel, global Statistics Manager commands, inter-product commands, and
scrolling commands (if applicable).
PS013E
RC= return-code , RCODE= reason-code message
Reason:
Statistics Manager was unable to successfully establish a thread to the specified DB2
subsystem using the Call Attachment Facility (CAF). The information in the message is
the information that DB2 has returned to the CAF component.
Action:
Use the information in the message text to resolve the problem.
PS014E
UNABLE TO LOAD PTLSSP LOAD MODULE.
Reason:
Statistics Manager could not load the PTLSSP load module. This module controls all
processing for the Extended Query Facility (EQF). Do not attempt to use any EQF
functions while this condition exists.
Action:
Ensure that the PTILIB DD is allocated, and that the PTLSSP module is contained in one
of the load libraries defined by this DD.
Chapter 2: PS to PTUIX 69
PS Messages
PS015E
ERROR OCCURRED IN CSECT &PSERPGM , STATEMENT &PSERSTM .
Reason:
An SQL ERROR occurred.
Action:
The message contains the name of the program that issued the SQL, along with the
statement number.
PS016E
YOU MAY ONLY SELECT ("S") ONE COMMAND.
Reason:
You have selected more than one line command to be processed for this line. You can
select only one line command to be processed.
Action:
Remove all but one S that you have entered and press Enter.
PS017E
INVALID LINE COMMAND. VALID COMMANDS ARE (S,?).
Reason:
You have entered an invalid line command.
Action:
Valid line commands are as follows:
■
S-Select this command for processing.
■
?-Display additional help about this line command.
70 Message Reference Guide (PS to ZLB)
PS Messages
PS018E
YOU MAY NOT INTERMIX "S" AND "?" LINE COMMANDS.
Reason:
You have entered a combination of S and ? line commands. You cannot intermix these
commands.
Action:
As an alternative, first select all the line you want to view help for with the ? line
command. After viewing all the help panels you selected, select the one command you
want to execute for this line with an S and press Enter.
PS019E
AN UNEXPECTED SQL ERROR HAS OCCURRED.
Reason:
An error was encountered while processing an SQL request for the current function.
Prior to receiving this error message, you should have been shown the SQL ERROR panel
(PTSQLET), which described the error condition.
Action:
As that panel noted, this error might not necessarily be a problem with Statistics
Manager. The error might have been caused by entering incorrect data, not holding
required authorization, or a problem with your DB2 system.
To insure the integrity of Statistics Manager processing, return to the Statistics Manager
main menu before retrying this function. If you attempt to complete the current
function without returning to the main menu, you could encounter further errors as
data expected from the SQL request might not be present or might be incomplete.
PS020E
INVALID COMMAND FOR CREATE LINE. ONLY (C) IS VALID ON THIS LINE.
Reason:
You have entered an invalid command was entered on the create line.
Action:
The only valid command is C.
Chapter 2: PS to PTUIX 71
PS Messages
PS021E
INVALID COMMAND FOR OBJECT LINES. VALID COMMANDS ARE (U, D).
Reason:
You have entered an invalid object line command.
Action:
Valid commands are U and D.
PS022E
YOU ARE NOT AUTHORIZED TO UPDATE OR DELETE THIS STRATEGY.
Reason:
You are attempting to update a strategy that cannot be updated by public.
Action:
Choose another strategy or create a new one.
PS023E
A STRATEGY NAME MUST BE ENTERED.
Reason:
You are attempting to create a strategy without specifying a strategy name.
Action:
You must enter a strategy name.
PS024E
A VALID STRATEGY TYPE MUST BE ENTERED. VALID VALUES ARE M AND U.
Reason:
You are attempting to create a strategy without a valid strategy type.
Action:
Valid types are as follows:
■
M-Migration Strategy
■
U-Update Strategy
72 Message Reference Guide (PS to ZLB)
PS Messages
PS025E
A VALID SHARE OPTION MUST BE ENTERED. VALID VALUES ARE (Y,N,U).
Reason:
You are attempting to create a strategy without a valid share option.
Action:
Valid share options are as follows:
■
U-All users can execute and update the strategy.
■
Y-All users can execute the strategy.
■
N-Only the creator can execute and update the strategy.
PS026E
THIS STRATEGY NAME ALREADY EXISTS. PLEASE CHOOSE A DIFFERENT NAME.
Reason:
You are attempting to create a strategy using a strategy name that already exists.
Action:
Choose a different strategy name.
PS027E
EMBEDDED BLANKS ARE NOT ALLOWED IN THIS FIELD.
Reason:
You entered a field with embedded blanks. Statistics Manager requires that field
contains no embedded blanks.
Action:
Reenter the field in question.
PS028I
STRATEGY DELETED.
Reason:
Statistics Manager successfully deleted the strategy.
Action:
None.
Chapter 2: PS to PTUIX 73
PS Messages
PS030E
LOG ENTRY IS NOT IN DELETE OR ROLLBACK PENDING STATUS.
Your attempt to execute a log entry was incorrect. The Execute function for the
Statistics Log is valid only on those entries that are in Delete or Rollback Pending status.
PS031E
LOG ENTRY STATUS REQUIRES ACTION. DELETE LINE COMMAND IGNORED.
Reason:
Your attempt to delete a log entry was invalid because the Log entry is in Delete or
Rollback Pending status.
Action:
To delete this entry first perform the Log Entry Execution.
PS032E
INVALID LINE COMMAND FOR LOG ENTRIES. VALID VALUES ARE (D,E,H,I).
Reason:
You entered an invalid line command or a Log Entry.
Action:
Valid line commands are as follows:
■
D-Delete Log Entry.
■
E-Execute Log Entry. This command functions only for entries in Delete or Rollback
Pending status (DP or RP).
■
H-This command provides help on status and action codes.
■
I-This command provides detail information on a log entry.
PS033E
LOG EXECUTION FAILED. CONTACT CUSTOMER SUPPORT FOR ASSISTANCE.
Reason:
PSM encountered an error while processing the current function.
Action:
As that panel noted, this error might not necessarily be a problem with Statistics
Manager. The error might have been caused by entering incorrect data, not holding
required authorization, or a problem with your DB2 system.
74 Message Reference Guide (PS to ZLB)
PS Messages
PS034E
UNABLE TO BUILD COLUMN SCREEN LIST. PRESS HELP FOR MORE.
Reason:
PSM was unable to retrieve column information from the DB2 catalog due to an SQL
error. An informational screen describing the SQL error should already have been
displayed.
Action:
The error might have been due to a deadlock condition within DB2.
PS035E
VALID LINE CMDS ARE: F, R, S, U, X, and Z.
Reason:
You have entered an invalid CATALOG UPDATE line command.
Action:
Valid line commands for tablespaces (object TYPE of TS) are as follows:
■
F-Force user-entered new catalog statistics values to become the old catalog
statistics values.
■
R-Reset user-entered catalog statistics back to their current DB2 catalog values.
■
S-Shrink the display of tablespace/column information to remove object detail.
■
U-Explode the display of information to include object detail and the current
settings of DB2 catalog statistics. The exploded display includes prompts, letting you
update the catalog statistic values.
■
X-Propagate the user entered multiplier to all dependent objects. This command
treats the table cardinality as a multiplier for all dependent objects.
■
Z-Set all statistics values (Old and New) to zero.
Chapter 2: PS to PTUIX 75
PS Messages
PS036E
VALID LINE CMDS ARE: C, F, R, S, U, and Z.
Reason:
You have entered an invalid CATALOG UPDATE line command.
Action:
Valid line commands for indexes (object TYPE IX) are as follows:
■
C-View a list of the index-key's columns. The column list lets you view/update
column statistics.
■
F-Force user-entered new catalog statistics values to become the old catalog
statistics values.
■
R-Reset user-entered statistics back to their current DB2 catalog values. This
command also resets any updated column statistics.
■
S-Shrink the display of object information to remove object detail.
■
U-Explode the display of object information to include object detail and current DB2
catalog values. The exploded display includes prompts, letting you update the
catalog statistic values.
■
Z-Set all statistics values (Old and New) to zero.
PS037E
SPECIFIED VALUE MUST BE A NUMBER LESS THAN 2,147,483,648.
Reason:
You have entered an invalid value at one of the Catalog Update statistics prompts. The
statistic you are trying to update requires an integer value in the range of -1 to
2,147,483,647. Your cursor has been positioned on the value that is in error.
Action:
Correct the value and press Enter.
76 Message Reference Guide (PS to ZLB)
PS Messages
PS038E
SPECIFIED VALUE MUST BE A NUMBER LESS THAN 32,768.
Reason:
You have entered an invalid value at one of the Catalog Update statistics prompts. The
statistic you are trying to update requires an integer value in the range of -1 to 32,767.
Your cursor has been positioned on the value that is in error.
Action:
Correct the value and press Enter.
PS039E
INVALID HEX CHARACTER. VALID CHARS ARE: 0 - 9, A - F. PF1 FOR MORE.
Reason:
You have entered an invalid hex character at the HIGH2KEY or LOW2KEY column
statistics prompts. Each of these prompts has two input areas:
The top line is for character data.
The bottom two lines are for hexadecimal data and should be used to enter the
hexadecimal representation of characters that have no representation on your
keyboard.
Action:
Valid hexadecimal characters are as follows: A thru F and 0 thru 9. Your cursor has been
positioned on the invalid character. Enter a valid hex character and press enter or use
the R (Reset) line command to restore the column's statistics to there current DB2
catalog values.
PS040E
CARDINALITY VALUE NOT SPECIFIED.
Reason:
You have not entered a cardinality (or multiplier) for doing statistics propagation.
Action:
When using the P or X line commands, you must specify a new cardinality for the table
you want to work on.
Chapter 2: PS to PTUIX 77
PS Messages
PS041E
VALID LINE CMDS ARE: C, F, P, R, S, U, X, and Z.
Reason:
You have entered an invalid CATALOG UPDATE line command.
Action:
Valid line commands for tables (object TYPE TB) are as follows:
■
C-View a list of the table's columns. The column list lets you view/update column
statistics.
■
F-Force user-entered new catalog statistics values to become the old catalog
statistics values.
■
P-Propagate the user entered cardinality to all dependent objects.
■
R-Reset user-entered statistics back to their current DB2 catalog values. This
command also resets any updated column statistics.
■
S-Shrink the display of object information to remove object detail.
■
U-Explode the display of object information to include object detail and current DB2
catalog values. The exploded display includes prompts, letting you update the
catalog statistic values.
■
X-Propagate the user entered multiplier to all dependent objects. This command
treats the table cardinality as a multiplier for all dependent objects.
■
Z-Set all statistics values (Old and New) to zero.
PS042E
INVALID STATUS FOR EXECUTE FUNCTION. COMMAND IGNORED.
Reason:
You have attempted to issue the Execute command on a Log entry that was not in a
Delete Pending (DP) or Rollback Pending (RP) status.
PS043E
INVALID STATUS FOR DELETE FUNCTION. COMMAND IGNORED.
Reason:
You have attempted to delete a Log Entry that has a Delete Pending (DP) or Rollback
Pending (RP) status.
Action:
Use the execute command.
78 Message Reference Guide (PS to ZLB)
PS Messages
PS044E
VALID LINE COMMANDS ARE: D, E, H, I.
Reason:
You have entered an invalid Log entry line command.
Action:
Valid types are as follows:
■
D-Delete a Log Entry
■
E-Execute a Log Entry with Status Pending Codes
■
H-Display help for Log entry Status and Action Codes
■
I-Display Log Entry Detail Information
PS045E
EXECUTE COMMAND FAILED.
Reason:
The execution of a Log Entry failed.
PS046E
INVALID OBJECT TYPE. VALID TYPES ARE: K, CK, P, CP, T, CT, S, CS.
Reason:
You have entered an invalid object type code.
Action:
Valid types are as follows:
■
K-Autobuild Package
■
CK-Catalog Package
■
P-Autobuild Plan
■
CP-Catalog Plan
■
S-Autobuild Tablespace
■
CS-Catalog Tablespace
■
T-Autobuild Table
■
CT-Catalog Table
Chapter 2: PS to PTUIX 79
PS Messages
PS047E
YOU MUST ENTER A PLAN NAME, PACKAGE NAME, OR A TABLE CREATOR.
Reason:
You have not entered information in a required field.
Action:
Enter the required information and rerun the job.
PS048E
A COLLECTION ID OR A TABLE NAME MUST BE ENTERED.
Reason:
You have not entered information in a required field.
Action:
Enter the required information and rerun the job.
PS049E
THIS FIELD CONTAINS INVALID INFORMATION FOR THE OBJECT TYPE.
Reason:
You have entered incorrect information in a non-required field.
Action:
Enter the required information and rerun the job.
PS050E
OBJECT EDIT ERROR.
Reason:
You have entered incorrect information in a non-required field.
Action:
Enter the required information and rerun the job.
80 Message Reference Guide (PS to ZLB)
PS Messages
PS051W
THE ATTN KEY WAS PRESSED. THE REPORT MAY BE INCOMPLETE.
Reason:
Statistics Manager was generating a report or selection list when you pressed the ATTN
key to cancel the generation. Because the report was canceled during generation, the
report might not be complete.
Action:
This is a warning message. No action is required.
PS052E
NO DATA WAS FOUND MATCHING SELECTION CRITERIA.
Reason:
Statistics Manager could not find any data for the criteria selected for your request.
Confirm that you specified the correct DB2 subsystem ID. Also, check the spelling for
accuracy.
Action:
If you are unsure of the problem, you might want to use an asterisk (*) to designate all
for a comprehensive search for the data requested.
PS053E
THE ONLY VALID LINE COMMAND IS (S). BLANKS REMOVE ENTRY FROM QUEUE.
Reason:
You entered a line command other than S (for Select) on a Selected Queue screen. An S
is pre-marked next to each entry that has been selected for processing.
Action:
Replace the line command with an S to keep the entry in the queue. When you do not
want Statistics Manager to process the entry, blank out the line command for that entry
and press Enter.
Chapter 2: PS to PTUIX 81
PS Messages
PS054E
YOU HAVE ENTERED AN INVALID COMMAND. PRESS HELP FOR MORE INFO.
Reason:
You have entered an invalid command in the command line for the panel. The command
line is typically preceded by COMMAND ===> or by OPTION ===>.
Action:
Enter ? in the command line to get a list of available Statistics Manager commands valid
for this panel, global Statistics Manager commands, CA's inter-product commands, and
scrolling commands (if applicable).
PS055E
INVALID MASK TYPE. PRESS HELP FOR MORE INFO.
Reason:
You have entered an invalid mask type.
Action:
Valid types are as follows:
■
TBC-Table Creator Name Mask
■
TBN-Table Name Mask
■
TSD-Tablespace Database Name Mask
■
TSN-Tablespace Name Mask
■
IXC-Index Creator Name Mask
■
IXN-Index Name Mask
PS056E
A SOURCE MASK MUST BE ENTERED. PRESS HELP FOR MORE INFO.
Reason:
You have not entered a source mask. A source mask is required.
Action:
Specify a source mask. Access online help if you require more information.
82 Message Reference Guide (PS to ZLB)
PS Messages
PS057E
A TARGET MASK MUST BE ENTERED. PRESS HELP FOR MORE INFO.
Reason:
You have not entered a target mask. A target mask is required.
Action:
Specify a target mask. Access online help if you require more information.
PS058E
INVALID SSID.
Reason:
You have entered an invalid subsystem ID.
Action:
Specify a valid subsystem ID.
PS059E
INVALID MASK RELATION. VALID VALUES ARE 1, M.
Reason:
You have not entered a valid Mask relationship.
Action:
Valid values are as follows:
■
1-Mask is used as a one-to-one relationship
■
M-Mask is used as a one-to-many relationship
PS060E
CREATE ONLY VALID ON CREATE LINE.
Reason:
You have attempted to create a new Mask entry from a line other than the create line.
Chapter 2: PS to PTUIX 83
PS Messages
PS061E
INVALID LINE COMMAND. VALID COMMANDS ARE D, T, U.
Reason:
You have entered an invalid line on a Mask entry.
Action:
Valid commands are as follows:
■
D-Delete a Mask entry
■
T-Template an entry
■
U-Update an etnry
PS062E
INVALID ROLLBACK OPTION. VALID OPTIONS ARE C, R.
Reason:
You have entered an invalid line Rollback option.
Action:
Valid options are as follows:
■
C-Commit Catalog Updates
■
R-Commit Catalog Update but gather Rollback statistics
PS063E
INVALID SSID SPECIFIED.
Reason:
You have entered an invalid DB2 Subsystem Id (SSID).
Action:
Enter ? for a selection list.
84 Message Reference Guide (PS to ZLB)
PS Messages
PS064E
INVALID LOCATION SPECIFIED.
Reason:
You have entered an invalid DB2 Subsystem Location.
Action:
Enter ? for a selection list or enter LOCAL.
PS065E
INVALID MASKING OPTION SPECIFIED. PRESS PF1 FOR HELP.
Reason:
You have specified an invalid masking option.
Action:
Valid values are as follows:
■
Y-Apply Masks
■
N-Do Not Apply Masks
PS066E
INVALID DB2 SUBSYSTEM ID (SSID) AND LOCATION COMBINATION.
Reason:
You have specified an invalid SSID.
Action:
Enter ? for a selection list of valid DB2 subsystems.
Chapter 2: PS to PTUIX 85
PS Messages
PS067E
INVALID STRATEGY COMMAND. VALID VALUES ARE B, D, E, I, L, M, O, U.
Reason:
You have entered an invalid line command.
Action:
Valid values are as follows:
■
B-Browse a strategy definition
■
D-Delete a strategy
■
E-Execute a strategy
■
I-Information report
■
L-List all versions for this strategy
■
M-Edit strategy masks
■
O-Edit strategy DB2 objects
■
U-Update a strategy definition
PS068E
NO CATALOG STATISTICS HAVE BEEN EXTRACTED. PRESS PF1 FOR HELP.
Reason:
You are trying to edit statistics, but no statistics have been extracted.
Action:
Use the Object editor to define objects that you would like to extract statistics for and
initialize Catalog Extraction.
PS069E
INVALID ROLLBACK OPTION SPECIFIED. PRESS PF1 FOR HELP.
Reason:
You have specified an invalid rollback option.
Action:
Valid values are as follows:
■
C-Commit Statistics
■
R-Rollback Statistics
86 Message Reference Guide (PS to ZLB)
PS Messages
PS070I
CATALOG STATISTICS UPDATE COMPLETE.
Reason:
Statistics Manager Catalog Statistics Update completed successfully.
Action:
None.
PS071I
CATALOG STATISTICS ROLLBACK COMPLETE.
Reason:
Statistics Manager Catalog Statistics Rollback completed successfully.
Action:
None.
PS072E
CATALOG STATISTICS ROLLBACK UNSUCCESSFUL.
Reason:
An invalid Catalog Update finished abnormally.
PS073E
CATALOG STATISTICS ROLLBACK UNSUCCESSFUL.
Reason:
An invalid Catalog Rollback finished abnormally.
PS074E
INVALID LOCATION SPECIFIED. STRATEGY CREATION UNSUCCESSFUL.
Reason:
An invalid Catalog Rollback finished abnormally.
Chapter 2: PS to PTUIX 87
PS Messages
PS075E
NO STATISTICS WHERE FOUND FOR THE OBJECTS SPECIFIED.
Reason:
The Statistics Extraction routine did not find any tables for the objects that were
specified.
PS076E
YOU MUST ENTER A JOB CARD.
Reason:
You did not specify a job card for batch execution.
Action:
Specify a job card and rerun the job.
PS077E
YOU MUST ENTER A SYSOUT CLASS.
Reason:
You did not specify a SYSOUT class for batch execution.
Action:
Specify a SYSOUT class and rerun the job.
PS078E
INVALID VALUE. VALID VALUES ARE M AND U.
Reason:
An invalid statistics execution function has been specified.
Action:
Valid values are as follows:
■
M-Perform migration of catalog statistics
■
U-Perform update of catalog statistics
88 Message Reference Guide (PS to ZLB)
PS Messages
PS079E
INVALID STRATEGY COMMAND. VALID VALUES ARE B AND S.
Reason:
You have specified an invalid line command.
Action:
Valid values are as follows:
■
B-Browse a statistics strategy
■
S-Select a statistics strategy
PS080E
You have entered an invalid value for a statistics multiplier. This field must contain a
numeric value.
Reason:
You specified a non-numeric value for the statistics multiplier.
Action:
Enter a numeric value for the statistics multiplier.
PS090E
INVALID STATISTICS EXECUTION FUNCTION. VALID VALUES ARE A AND U.
Reason:
You have entered an invalid statistics execution function.
Action:
Valid values are as follows:
■
A-Perform statistics analysis
■
E-Perform statistics extraction
■
M-Perform statistics migration
■
U-Perform statistics update
Chapter 2: PS to PTUIX 89
PS Messages
PS091E
INVALID STATISTICS EXECUTION REPORT. VALID VALUES ARE N, S, AND L.
Reason:
You have entered an invalid statistics report option.
Action:
Valid values are as follows:
■
L-Produce long reports.
■
S-Produce short reports.
■
N-Do not produce reports.
PS092E
INVALID EXECUTION MODE. VALID VALUES ARE B, I AND O.
Reason:
You have entered an invalid statistics execution mode.
Action:
Valid values are as follows:
■
B-Perform multiple executions in batch.
■
I-Perform execution in batch.
■
O-Perform execution online.
PS093E
INVALID STATISTICS CALCULATION OPTION. VALID VALUES ARE Y AND N.
Reason:
You have entered an invalid statistics calculation option.
Action:
Valid values are as follows:
■
Y-Recalculate Statistics.
■
N-Do not recalculate statistics.
90 Message Reference Guide (PS to ZLB)
PS Messages
PS094E
INVALID STATISTICS SAVE OPTION. VALID VALUES ARE Y AND N.
Reason:
You have entered an invalid statistics save option.
Action:
Valid values are as follows:
■
Y-Save extracted statistics from extraction or migration
■
N-Do not save statistics
PS095I
INVALID STRATEGY NAME. PRESS HELP FOR MORE INFORMATION.
Reason:
You have entered an invalid strategy name. Strategy names cannot begin with special
characters such as #.
Action:
Press HELP to obtain more information about this informational message.
PS096I
BATCH CARDS GENERATED.
Reason:
This message informs you that the batch cards were generated.
Action:
None.
PS097E
INVALID LOCATION SPECIFIED. PRESS PF1 FOR HELP.
Reason:
You have entered an invalid DB2 location. This error could be caused because DDF is not
currently running.
Action:
Specify a valid location. If you need further help, press PF1 (Help) for more information.
Chapter 2: PS to PTUIX 91
PS Messages
PS098E
INVALID OVERRIDE OPTION SPECIFIED. VALID VALUES ARE Y AND N.
Reason:
You have entered an invalid statistics calculation override option.
Action:
Valid values are as follows:
■
Y-Override multiplier values.
■
N-Do not override multiplier values.
PS099I
CALCULATIONS VARIABLES HAVE BEEN SAVED.
Reason:
This message informs you that calculation variables have been saved.
Action:
None.
PS100I
SELECTED OBJECTS HAVE BEEN QUEUED, ENTER (S)HRINK TO VIEW THE QUEUE.
Reason:
This informational message indicates that selections have been queued.
Action:
None.
PS101I
STATISTICS STRATEGY HAS BEEN SAVED.
Reason:
This informational message indicates that the statistics strategy has been saved.
Action:
None.
92 Message Reference Guide (PS to ZLB)
PS Messages
PS102E
NO OBJECTS HAVE BEEN SPECIFIED. EXECUTION CANCELED.
Reason:
The execution function cannot be performed because you have not defined objects for
the purpose of extracting statistics.
Action:
You must define objects prior to performing statistical functions.
PS103E
NO OBJECTS HAVE BEEN SPECIFIED. EXTRACTION CANCELED.
Reason:
The extraction function cannot be performed because you have not defined objects for
the purpose of extracting statistics.
Action:
You must define objects prior to performing an extraction.
PS104E
NO OBJECTS HAVE BEEN SPECIFIED. ANALYSIS CANCELED.
Reason:
The analysis function cannot be performed because you have not defined objects for
the purpose of extracting statistics.
Action:
You must define objects prior to performing analysis.
PS105E
NO OBJECTS HAVE BEEN DEFINED. STRATEGY NOT SAVED.
Reason:
A strategy definition is incomplete because you have not defined objects.
Action:
You must define objects for a strategy to be complete.
Chapter 2: PS to PTUIX 93
PS Messages
PS106E
VALID LINE CMDS ARE: F, R, S, U, and Z.
Reason:
You have entered an invalid CATALOG UPDATE line command.
Action:
Valid line commands for columns are as follows:
■
F-Force user-entered new catalog statistics values to become the old catalog
statistics values.
■
R-Reset user-entered catalog statistics back to their current DB2 catalog values.
■
S-Shrink the display of tablespace/column information to remove object detail.
■
U-Explode the display of information to include object detail and the current
settings of DB2 catalog statistics. The exploded display includes prompts, letting you
update the catalog statistic values.
■
Z-Set all statistics values (Old and New) to zero.
PS107W
SOME OR ALL THE OBJECTS HAVE NO STATISTICS. DEFAULT VALUES USED.
Reason:
Statistics Manager encountered objects that RUNSTATS had not been run against or
where zeros were encountered in key calculation fields. Default values were
substituted.
Action:
This is a warning message. No action is required.
94 Message Reference Guide (PS to ZLB)
PS Messages
PS108E
INVALID EXTRACTION SCOPE. VALID VALUES ARE F)ULL OR P)ARTIAL.
Reason:
You have entered an invalid extraction scope.
Action:
Valid entries for this field are as follows:
■
F-Full Extraction. This indicates PSM should extract all catalog statistics. Use this
option when you want manipulation of statistical values.
■
P-Partial Extraction. PSM extracts only statistics necessary for catalog update. This
option increases performance; you should use it when no modification of catalog
statistics is required.
PS109E
COMMAND NOT VALID WITH PARTIAL EXTRACTION.
Reason:
You have attempted to perform full statistical modifications or entered invalid execution
options on a strategy defined with a partial extraction scope. Partial extractions provide
limited execution and statistic modification ability.
Action:
When you want full PSM capabilities, set the extraction scope to Full.
PS110E
INVALID CALCULATION OPTION FOR PARTIAL EXTRACT. VALID VALUES ARE N.
Reason:
You have attempted to perform statistical calculations on a strategy defined with a
partial extraction scope. Partial extractions provide limited execution and statistic
modification ability.
Action:
When you want full PSM capabilities, set the extraction scope to Full.
Chapter 2: PS to PTUIX 95
PS Messages
PS111E
ENTERED VALUE CANNOT BE REPRESENTED AS A FLOATING POINT NUMBER.
Reason:
You have attempted to perform statistical calculations on a strategy defined with a
partial extraction scope. Partial extractions provide limited execution and statistic
modification ability.
Action:
When you want full PSM capabilities, set the extraction scope to Full.
PS112E
INVALID VALUE. VALID VALUES ARE Y - YES AND N - NO.
Reason:
You have entered an invalid option for Statistics Manager existing masks.
Action:
Valid values for this variable are as follows:
■
Y-Use previously created masks.
■
N-Do not use previously created masks.
PS113E
INVALID EXECUTION FUNCTION. VALID VALUES ARE I,IX OR L.
Reason:
You have entered an invalid execution value.
Action:
Valid values are as follows:
■
I-Import
■
IX-Import/Export
■
L-Load
96 Message Reference Guide (PS to ZLB)
PS Messages
PS114E
INVALID FUNCTION. VALID VALUE FOR STRATEGY CREATION/UPDATE IS S.
Reason:
You have entered an invalid function.
Action:
The only valid value is S.
PS115E
INVALID VALUE. CREATOR/DB NAME MUST BE BLANK FOR THIS MASK TYPE.
Reason:
You have entered a value for the Creator/DB Name field.
Action:
For the selected mask type, any value in this field is invalid.
PS116E
INVALID VALUE. IX/TB/TS NAME MUST BE BLANK FOR THIS MASK TYPE.
Reason:
You have entered a value for the IX/TB/TS Name field.
Action:
For the selected mask type, any value for this field is invalid.
PS117E
IX/TB/TS NAME REQUIRED FOR THIS MASK TYPE.
Reason:
You have not entered the required index, table, or tablespace name required for this
mask type.
Action:
For mask types TB, TBN, IX, IXN, TS, and TSN, you must complete the IX/TB/TS Name
field.
Chapter 2: PS to PTUIX 97
PS Messages
PS118E
CREATOR/DB NAME REQUIRED FOR THIS MASK TYPE.
Reason:
You have not entered the required index creator, table creator, or database name for
this mask type.
Action:
For mask types TB, TBC, IX, IXC, TS, and TSD, you must complete the Creator/DB Name
field.
PS119E
EXPORT SSID AND LOCATION REQUIRED FOR FUNCTIONS: IS, IX, AND X.
Reason:
You have not specified a value for the Export SSID and Location fields.
Action:
These fields are required for the IS, IX, or X functions.
PS120E
IMPORT SSID AND LOCATION REQUIRED FOR FUNCTIONS: I AND IX.
Reason:
You have not specified a value for the Export SSID and Location fields.
Action:
These fields are required for the I and IX functions.
PS121E
INVALID COLUMN GROWTH %. MUST BE NUMERIC.
Reason:
You have entered an invalid value for the Column Growth % field.
Action:
This field value must be a valid numeric value.
98 Message Reference Guide (PS to ZLB)
PS Messages
PS122I
THE BATCH PROCESSOR INPUT HAS BEEN WRITTEN TO THE BATCH MODE DATASET.
Reason:
This message indicates that the batch processor input has been written to the batch
mode data set.
Action:
None.
PS123E
UNABLE TO LOAD PTLSQLDP LOAD MODULE.
Reason:
Statistics Manager could not load the PTLSQLDP load module.
Action:
Ensure that the PTILIB DD is allocated and that the PTLSQLDP module is contained in
one of the load libraries defined by this DD.
PS124I
STRATEGY VERSION DELETED.
Reason:
This message indicates that the strategy version was deleted.
Action:
None.
Chapter 2: PS to PTUIX 99
PS Messages
PS125E
INVALID FUNCTION. VALID VALUES ARE A,I,U OR X.
Reason:
You have entered an invalid execution function for a strategy version.
Action:
Valid values are as follows:
■
A-Analysis
■
I-Import
■
L-Load
■
U-Unload
■
X-Export
PS126E
CLUSTERRATIO MUST BE LESS THAN OR EQUAL TO 100.
Reason:
You have entered an invalid value for CLUSTERRATIO.
Action:
Valid values are less than or equal to 100.
PS127E
ROLLBACK FUNCTION WAS NOT COMPLETED. NO STATISTICAL DATA COLLECTED.
Reason:
You tried to export and roll back a strategy/version that did not complete. No statistical
data was collected and saved, and no execution on the strategy/version is possible.
PS128E
INVALID FUNCTION. EXPORT VERSION MAY NOT BE EDITED.
Reason:
You have attempted to edit an export strategy version.
Action:
You cannot edit export strategy versions.
100 Message Reference Guide (PS to ZLB)
PS Messages
PS129E
INVALID TS NAME. TS NAME CANNOT BE GREATER THAN 8 BYTES LONG.
Reason:
You have entered an invalid value for tablespace name.
Action:
The tablespace name cannot be greater than 8 bytes in length.
PS130E
INVALID STRATEGY VERSION COMMAND. VALID VALUES ARE: B,D,E,I,R,S.
Reason:
You have entered an invalid line command.
Action:
Valid values are as follows:
■
B-Browse a strategy version definition
■
D-Delete a version
■
E-Execute a version
■
I-Information report
■
R-Statistics reports
■
S-Edit strategy statistics
PS131E
INVALID VALUE. VALID VALUES ARE Y - YES AND N - NO.
Reason:
You have specified an invalid reporting option.
Action:
Valid values are as follows:
■
Y-Report on the corresponding table.
■
N-Do not report on the corresponding table.
Chapter 2: PS to PTUIX 101
PS Messages
PS132E
VALID LINE CMDS ARE: S AND U.
Reason:
You have entered an invalid catalog update line command for an object of type TBS.
Action:
Valid line commands are as follows:
■
S-Shrink the display of object information to remove object detail.
■
U-Explode the display of object information to include object detail and current DB2
catalog values.
PS133E
VALID LINE CMDS ARE: S AND U.
Reason:
You have entered an invalid catalog update line command for an object of type IXS.
Action:
Valid line commands are as follows:
■
S-Shrink the display of object information to remove object detail.
■
U-Explode the display of object information to include object detail and current DB2
catalog values. The exploded display includes prompts, letting you update the
catalog statistic values.
PS134E
UNLOAD MUST BE A VERSION IMPORT OR IMPORT/EXPORT STATISTICS.
Reason:
You attempted to perform the UNLOAD function on a Statistics Strategy.
Action:
The UNLOAD function is valid only for statistics strategy versions.
102 Message Reference Guide (PS to ZLB)
PS Messages
PS135E
INVALID PRIMARY SPACE ALLOCATION. MUST BE NUMERIC.
Reason:
You have specified an invalid primary space allocation value for a new data set.
Action:
The primary space allocation value must be numeric and cannot exceed five digits.
PS136E
INVALID SECONDARY SPACE ALLOCATION. MUST BE NUMERIC.
Reason:
You have specified an invalid secondary space allocation value for a new data set.
Action:
The secondary space allocation value must be numeric and cannot exceed five digits.
PS137E
INVALID DIRECTORY BLOCK ALLOCATION. MUST BE NUMERIC.
Reason:
You have specified an invalid directory block space allocation value for a new data set.
Action:
The directory block space allocation value must be numeric and cannot exceed five
digits.
PS138E
INVALID ALLOCATION TYPE. MUST BE: CYL, TRK, OR BLK.
Reason:
You have entered an invalid value for the Space Allocation Type.
Action:
Valid values are as follows:
■
CYL-Cylinders
■
TRK-Tracks
■
BLK-Blocks
Chapter 2: PS to PTUIX 103
PS Messages
PS139E
PROPAGATION COULD NOT BE CALCULATED. MISSING PARTITION STATISTICS.
Reason:
Propagation calculations could not be completed because missing partition statistics are
missing.
Action:
To solve this problem, run RUNSTATS on the objects and attempt propagation again.
PS140E
INVALID DATASET ALLOCATION. PLEASE CHECK DSN VALUES AND TRY AGAIN.
Reason:
You have specified an invalid data set allocation value, which prevents a successful
UNLOAD.
Action:
Verify the data set allocation values and try again.
PS141E
INVALID DATASET. PLEASE USE THE MEMBER NAME FIELD TO SPECIFY A MEMBER.
Reason:
You have specified an invalid data set name.
Action:
When you want to specify a member name, use the Member Name field.
104 Message Reference Guide (PS to ZLB)
PS Messages
PS142E
INVALID VALUE. VALID VALUES ARE D - DETAIL, O - OLD, N - NEW.
Reason:
You have specified an invalid line command.
Action:
Valid values are as follows:
■
D-Detail
■
O-Old
■
N-New
PS143E
INVALID DATASET. DATASET NAME IS A REQUIRED FIELD.
Reason:
You have not specified a data set name or have specified an invalid data set name.
Action:
To correct this error, specify a valid data set name and try again.
PS144E
INVALID STRATEGY VERSION COMMAND. VALID VALUES ARE: B,D,E,I,M,R,S.
Reason:
You specified an invalid line command.
Action:
Valid values are as follows:
■
B-Browse a strategy or version
■
D-Delete a strategy or version
■
E-Execute a strategy or version
■
I-Information report
■
M-Edit strategy or version masks
■
R-Report on a strategy or version
Chapter 2: PS to PTUIX 105
PS Messages
PS145I
SELECT A MEMBER TO LOAD FROM.
Reason:
This message is a request that you select a member from which to load.
Action:
Select a member name for the Load utility.
PS146E
INVALID EXECUTION FUNCTION. VALID VALUES ARE X OR U.
Reason:
You specified an invalid value in the Strategy/Version Execution Function field.
Action:
Valid values are as follows:
■
U-UNLOAD strategy or version statistics to file.
■
X-Export strategy or version statistics.
PS147E
INVALID EXECUTION FUNCTION. VALID VALUES ARE X OR IX.
Reason:
You specified an invalid value in the Strategy/Version Execution Function field.
Action:
Valid values are as follows:
■
IX-Import/export strategy or version statistics
■
X-Export strategy or version statistics.
106 Message Reference Guide (PS to ZLB)
PS Messages
PS148E
CLUSTERRATIOF RANGE MUST BE BETWEEN 0 AND 1.
Reason:
You entered an invalid value for CLUSTERRATIOF.
Action:
Valid values are between 0 and 1.
PS149E
NACTIVE RANGE MUST BE GREATER THAN OR EQUAL TO 0.
Reason:
You specified an invalid NACTIVE value.
Action:
NACTIVE must be greater than or equal to zero.
PS150E
INVALID DATASET. LOAD DATASET MUST EXIST.
Reason:
You have specified an invalid data set name.
Action:
Specify a valid data set name for the Load utility.
PS151E
INVALID MEMBER NAME. LOAD MEMBER NAME MUST EXIST.
Reason:
You specified an invalid member name.
Action:
Specify the name of an existing member of the selected data set for the Load utility.
Chapter 2: PS to PTUIX 107
PS Messages
PS152E
INVALID EXECUTION FUNCTION. VALID VALUES ARE I AND IX.
Reason:
You specified an invalid value for the Strategy/Version Execution Function field.
Action:
Valid values are as follows:
■
I-Import Strategy statistics
■
IX-Import/Export Strategy statistics
PS153W
UNLOAD MEMBER EXIST AND WILL BE OVER WRITTEN.
Reason:
You selected to unload statistics to a partitioned data set member that already exists. If
you continue, the existing member is overwritten.
Action:
This is a warning message. No action is required.
PS154I
UNLOAD MEMBER DOES NOT EXIST AND WILL BE CREATED.
Reason:
This message indicates that you specified an unload member that does not currently
exist. The member will be created.
Action:
None.
PS155E
DATASET HAS AN INVALID DSORG. SELECT A NEW DATASET NAME.
Reason:
You specified a data set with an invalid DSORG (data set organization).
Action:
The data set must be a valid PDS (partitioned data set).
108 Message Reference Guide (PS to ZLB)
PS Messages
PS156E
A VALID MEMBER NAME MUST BE SPECIFIED FOR PARTITIONED DATASET.
Reason:
You have not specified a member name for the selected PDS (partitioned data set).
Action:
A member name is required.
PS157E
A MEMBER NAME SPECIFIED FOR SEQUENTIAL DATASET IS INVALID.
Reason:
Indicates that you have specified a member name for a sequential data set.
Action:
Choose a PDS (Partitioned DataSet) or a sequential data set without the member name
specified.
PS158E
DATASET HAS AN INVALID LRECL. SELECT A NEW DATASET NAME.
Reason:
You specified an invalid data set. The data set must have a DSORG (data set
organization) of PO (partitioned organization) or PS (physical sequential). The data set
must also be fixed block (FB) with a logical record length (LRECL) of 80 bytes.
Action:
Verify that the data set fits the above criteria.
PS159E
DATASET NAME IS INVALID. PLEASE SUPPLY A VALID DATASET NAME.
Reason:
You specified an invalid data set name.
Action:
Specify a valid DSN. Verify that the data set name is valid and retry the function.
Chapter 2: PS to PTUIX 109
PS Messages
PS160E
UNABLE TO LOAD PZL#STDR LOAD MODULE.
Reason:
Statistics Manager could not load the PZL#STDR load module.
Action:
Ensure that the PTILIB DD is allocated, and that the PZL#STDR module is contained in
one of the load libraries defined by this DD.
PS161E
INVALID VALUE. VALID VALUES ARE Y - YES, N - NO, OR U - UPDATE.
Reason:
You entered an invalid option for Update Reporting Options.
Action:
Valid values are as follows:
■
Y-Run execution with the current report options.
■
N-Do not run execution with the current report options.
■
U-Update the report options.
PS162E
INVALID VALUE FOR FIELD. VALID VALUES ARE Y - YES OR N - NO.
Reason:
You entered an invalid option for Update Calculation Options.
Action:
Valid values are as follows:
■
Y-Update the current calculation options.
■
N-Do not update the current calculation options.
110 Message Reference Guide (PS to ZLB)
PS Messages
PS163E
INVALID VALUE FOR FIELD. VALID VALUES ARE Y - YES OR N - NO.
Reason:
You entered an invalid option for Update Execution Options.
Action:
Valid values are as follows:
■
Y-Update the current execution options.
■
N-Do not update the current execution options.
PS164E
INVALID FUNCTION. MASKS ARE ONLY UPDATEABLE FOR IMPORT OR LOAD.
Reason:
You have entered an invalid function for the strategy version line command.
Action:
Strategy masks are only updateable for Import or Load strategy versions.
PS165W
Valid number has to be positive. Default values used.
Reason:
You have entered negative number or 0 for CARDF for propagate a value based on the
cardinality. PSM used the default value for CARDF.
Action:
This is a warning message only. No further action is required.
Chapter 2: PS to PTUIX 111
PS Messages
PS166E
Invalid REPORT parameter.
Reason:
An invalid parameter was specified on the REPORT command.
Action:
Use the following valid syntax for this command:
■
REPORT-Save the report configuration.
■
REPORT RESET-Reset the report configuration.
PS167I
Report configuration saved.
Reason:
The report configuration has been saved. The report will use this configuration
automatically the next time it is invoked.
Action:
No further action required.
PS168W
Report reset to default configuration.
Reason:
The report configuration has been reset. The report will use the default configuration
the next time it is invoked.
Action:
No further action required.
PS169W
The REPORT command is not supported on this panel.
Reason:
The REPORT command is not supported on this panel.
Action:
No further action required.
112 Message Reference Guide (PS to ZLB)
PSA Messages
PSA Messages
Messages with the PSA prefix are generated from CA Subsystem Analyzer.
PSA0100
SSANALZE INIT IN PROGRESS DB2=ssid.
Reason:
CA Subsystem Analyzer collection initialization is in progress for a selected DB2
subsystem.
CA Subsystem Analyzer collection executes within the Xmanager address space. The
message text includes the DB2 subsystem identifier for which the CA Subsystem
Analyzer collector is being started.
Action:
This message is informational and is written to the Xmanager joblog as well as to the
MVS SYSLOG.
PSA0101
SSANALZE INIT COMPLETE FOR DB2=ssid.
Reason:
CA Subsystem Analyzer collection initialization completed successfully for a selected
DB2 subsystem.
CA Subsystem Analyzer collection executes within the Xmanager address space. The
message text includes the DB2 subsystem identifier for which the CA Subsystem
Analyzer collector is being started.
Action:
This message is informational and is written to the Xmanager joblog as well as to the
MVS SYSLOG.
Chapter 2: PS to PTUIX 113
PSA Messages
PSA0102
SUBSYSTEM ANALYZER ALREADY ACTIVE FOR DB2=ssid.
Reason:
A start CA Subsystem Analyzer request has been received by the Xmanager address
space. However, initialization failed because CA Subsystem Analyzer collection is already
active for the selected DB2 subsystem.
Only one CA Subsystem Analyzer collector can be active per DB2 subsystem. You cannot
have multiple CA Subsystem Analyzer collectors for a single DB2 subsystem.
Action:
Ensure you have only one collection active for the selected DB2 subsystem.
PSA0103
SSANAYZE TERM IN PROGRESS FOR DB2=ssid.
Reason:
CA Subsystem Analyzer collection termination is in progress for a selected DB2
subsystem.
CA Subsystem Analyzer collection executes within the Xmanager address space. The
message text includes the DB2 subsystem identifier for which the CA Subsystem
Analyzer collector is being terminated.
Action:
This message is informational and is written to the Xmanager joblog as well as the MVS
SYSLOG.
PSA0104
SUBSYSTEM ANALYZER TERM COMPLETE FOR DB2=ssid.
Reason:
CA Subsystem Analyzer collection has been successfully terminated for a selected DB2
subsystem.
CA Subsystem Analyzer collection executes within the Xmanager address space. The
message text includes the DB2 subsystem identifier for which the CA Subsystem
Analyzer collector has terminated.
Action:
This message is informational and is written to the Xmanager joblog as well as the MVS
SYSLOG.
114 Message Reference Guide (PS to ZLB)
PSA Messages
PSA0105
SSANALZE ABEND RECURSION DETECTED FOR DB2=ssid.
Reason:
CA Subsystem Analyzer has detected abend activity while in the process of processing
an abend. Collection is terminated due to the failure.
Action:
None.
PSA0106
SSANALZE SUSPENDED FOR DB2 INIT OF DB2=ssid.
Reason:
Collection initialization has suspended waiting for DB2 initialization to be completed.
This message is issued when CA Subsystem Analyzer collection is started using MVS
modify command and AUTO=YES is specified.
Action:
None.
PSA0107
SSANALZE INIT FAILED/CDMID=mmmm LOCATE FAILED.
Reason:
CA Subsystem Analyzer collection initialization was unsuccessful. During collection
initialization, validation/locate logic has failed.
Action:
None.
Chapter 2: PS to PTUIX 115
PSA Messages
PSA0108
SSANALZE COLLECTION TIME LIMIT HAS EXPIRED DB2=ssid.
Reason:
CA Subsystem Analyzer collection has determined that the time limit specified when
collection was started has expired. When provided, a time limit causes collection to
terminate when the time limit has been reached.
Action:
This message is informational only. Collection termination is processed subsequent to
this message being received.
PSA0109
SSANALZE INIT HAS FAILED [email protected]@@@
Reason:
CA Subsystem Analyzer collection initialization for the subsystem identified has failed.
Action:
See previous messages for the reason of the failure.
PSA0110
SSANALZE INIT OF I/O ANALYSIS ERROR, [email protected]@@@
Reason:
CA Subsystem Analyzer collection initialization process for the subsystem identified
incurred an error while setting up the I/O analysis process. Collection initialization
continues, but problems may occur later during the collection process.
Action:
None.
116 Message Reference Guide (PS to ZLB)
PSA Messages
PSA0111
SSANALZE [email protected]@@ INIT IN PROGRESS [email protected]@@@
Reason:
CA Subsystem Analyzer collection initialization is in progress for the collection identifier
(CID) specified.
Action:
None.
PSA0112
SSANALZE [email protected]@@ INIT COMPLETE [email protected]@@@
Reason:
CA Subsystem Analyzer collection initialization is complete for the collection identifier
(CID) specified.
Action:
None.
PSA0113
SSANALZE [email protected]@@ TERM IN PROGRESS [email protected]@@@
Reason:
CA Subsystem Analyzer collection termination is in progress for the collection identifier
(CID) specified.
Action:
None.
PSA0114
SSANALZE [email protected]@@ TERM COMPLETE [email protected]@@@
Reason:
CA Subsystem Analyzer collection termination is complete for the collection identifier
(CID) specified.
Action:
None.
Chapter 2: PS to PTUIX 117
PSA Messages
PSA0115
SSANALZE CID-CVA INIT IN PROGRESS
Reason:
CA Subsystem Analyzer collection initialization is in progress for the volume analysis
process.
Action:
None.
PSA0116
SSANALZE CID=CVA INIT COMPLETE
Reason:
CA Subsystem Analyzer collection initialization is complete for the volume analysis
process.
Action:
None.
PSA0117
SSANALZE CID=CVA TERM IN PROGRESS
Reason:
CA Subsystem Analyzer collection termination is in progress for the volume analysis
process.
Action:
None.
PSA0118
SSANALZE CID=CVA TERM COMPLETE
Reason:
CA Subsystem Analyzer collection termination is complete for the volume analysis
process.
Action:
None.
118 Message Reference Guide (PS to ZLB)
PSA Messages
PSA0120
ERROR RETRIEVING GROUP BUFFER POOL STATS FOR @@@@@@@@, [email protected]@@@
[email protected]@@@@@@@
Reason:
CA Subsystem Analyzer collection process received an error attempting to retrieve
information regarding the specified group buffer pool structure in the coupling facility.
The return and reason code supplied are returned from the IXLMG macro provided by
IBM.
Action:
None.
PSA0121
ERROR RETRIEVING GROUP BUFFER POOL STATS FOR @@@@@@@@,
[email protected]@@@
Reason:
CA Subsystem Analyzer collection process received an error attempting to retrieve
information regarding the specified group buffer pool structure in the coupling facility.
The data area specified was not located.
PSA0122
ABEND=abend-code MODULE=name OFFSET=abend-offset DB2=version
Reason:
Collection has failed due to abnormal termination. CA Subsystem Analyzer error
handling recovery logic has recovered from the abend and collection has been disabled.
Action:
View the joblog or MVS Syslog for additional error WTO messages.
For assistance, contact CA Support at http://ca.com/support.
Chapter 2: PS to PTUIX 119
PSA Messages
PSA0125
SSA INITIALIZATION FAILED. PSACOExx VERIFICATION FAILED
Reason:
CA Subsystem Analyzer collection initialization failed. Possible reasons might be a
conflict with OEM product or mixed level of PSA modules.
Action:
For assistance, contact CA Support at http://ca.com/support.
PSA0170
SSANALZE COLLECTION INTERVAL END TIME=hh:mm INTERVAL=hh:mm DB2=xxxx
VCAT=xxxxxxxx.xxxxxxxx DATASTORE=xxxxxxxx
Reason:
Collection interval is complete and externalization is active.
Valid message parameters include the following:
■
TIME-End time of the collection interval.
■
INTERVAL-Duration of the collection interval.
■
DB2-SSID of the DB2 subsystem for which this collection is active.
■
VCAT-High-level qualifier of the data store used to externalize collection data.
■
DATASTORE-Name of the data store being used to externalize collection data.
Action:
None.
120 Message Reference Guide (PS to ZLB)
PSA Messages
PSA0171
SSANALYZE COLLECTION INTERVAL END FORCED DUE TO XMANAGER STORAGE
SHORTAGE, DB2=ssid
Reason:
The Xmanager has encountered a storage shortage. The message identifies the DB2
subsystem related to this collector. The current collection interval is terminated and the
interval data is externalized if externalization was specified at collection start. This
message is in response to Xmanager message PXM0372.
Action:
None.
Note: To determine if any action is required, see the PXM0372 message.
PSA0200
SSANALZE COLLECTION MODIFY IN PROGRESS.
Reason:
A MVS modify request has been received for CA Subsystem Analyzer collection.
Action:
This message is informational. It indicates the request was received and is about to be
processed. The modify command is processed and additional messages are issued by
the modify request process routine.
PSA0201
SSANALZE MODIFY FAILED/COLLECTION ACTIVE OR PENDING.
Reason:
A modify request to start CA Subsystem Analyzer collection was ignored because
collection for the DB2 SSID was already active or was pending for the DB2 subsystem to
become active.
Action:
Terminate CA Subsystem Analyzer collection before issuing the start modify request if
collection is already active or wait for the DB2 subsystem to become active.
Chapter 2: PS to PTUIX 121
PSA Messages
PSA0202
SSANALZE MODIFY FAILED/ASYNCH ABEND INCURRED.
Reason:
The CA Subsystem Analyzer collection modify request has failed because an abend was
incurred while the request was being processed.
PSA0203
SSANALZE MODIFY FAILED/COLLECTION NOT ACTIVE.
Reason:
A modify request to CA Subsystem Analyzer collection has failed because collection for
the DB2 SSID was not active.
Action:
Collection for the SSID must be active for the modify request to be processed.
PSA0204
SSANALZE MODIFY FAILED/INVALID KEYWORD LOCATED.
Reason:
The CA Subsystem Analyzer collection modify request has failed because an invalid
keyword was located.
Action:
Correct the modify command text and reissue the modify command.
PSA0205
SSANALZE MODIFY FAILED/KEYWORD NOT FOUND KEY=keyword.
Reason:
The CA Subsystem Analyzer collection modify request has failed because an invalid
keyword was located.
Action:
Correct the modify command text and reissue the modify command.
122 Message Reference Guide (PS to ZLB)
PSA Messages
PSA0207
SSANALZE MODIFY FAILED/DATALEN ERROR KEY=keyword.
Reason:
The message text indicates that the modify command text contained a keyword
operand value with an invalid length. The failing keyword is provided in the message
text.
Action:
Correct the keyword operand and reissue the modify request.
PSA0208
SSANALZE MODIFY FAILED/DATA OUT OF RANGE KEY=keyword.
Reason:
The message text indicates that the modify command text contained a keyword
operand value that was out of range and therefore invalid. The failing keyword is
provided in the message text.
Action:
Correct the keyword operand and reissue the modify request.
PSA0209
SSANALZE MODIFY FAILED/DATA IS INVALID KEY=keyword.
Reason:
The message text indicates that the modify command text contained a keyword
operand value that was determined to be invalid. The failing keyword is provided in the
message text.
Action:
Correct the keyword operand and reissue the modify request.
Chapter 2: PS to PTUIX 123
PSA Messages
PSA0210
SSANALZE MODIFY FAILED DUE TO ERROR.
Reason:
The message text indicates that the modify command failed and was not executed due
to one or more errors. Additional messages have been issued indicating the reason for
failure.
Action:
Correct the modify command text and reissue the request.
PSA0211
SSANALZE MODIFY FAILED/DATASTORE DOES NOT EXIST.
Reason:
The message text indicates that the modify command failed because the data store
name in the modify command text does not exist.
Action:
Correct the modify command data store name and reissue the request.
PSA0212
SSANALZE MODIFY FAILED/CONTROL FILE NOT FOUND.
Reason:
The message text indicates that the modify command failed. This message is issued
when CA Subsystem Analyzer collection modify command processing has failed due to
problems locating control file information.
Action:
Verify the control file in use is correct.
For assistance, contact CA Support at http://ca.com/support.
124 Message Reference Guide (PS to ZLB)
PSA Messages
PSA0213
SSANALZE MODIFY FAILED/CONTROL FILE ALLOC ERROR.
Reason:
The message text indicates that the modify command failed because a control file
allocation error was incurred. An additional message relating to the allocation error
should have been issued.
Action:
Verify the control file in use is correct.
PSA0215
SSANALZE MODIFY FAILED/CONTROL FILE OPEN ERROR.
Reason:
The message text indicates that the modify command failed due to a control file open
error. An additional message relating to the open error should have been issued.
Action:
Verify the control file in use is correct.
PSA0216
SSANALZE MODIFY FAILED/CONTROL FILE IS FULL.
Reason:
The message text indicates that the modify command failed because the control file is
full.
The control file needs to be reallocated to a larger size.
Action:
To reallocate the control file:
1.
Create a new control file using a different control file name.
2.
Use IDCAMS repro to copy the old control file contents to the new control file.
3.
Rename the old control file to a new (backup) name.
4.
Rename the new control file to the previous control file name.
5.
Terminate and restart the Xmanager address space.
Chapter 2: PS to PTUIX 125
PSA Messages
PSA0217
SSANALZE MODIFY FAILED/CONTROL FILE WRITE ERROR.
Reason:
The message text indicates that the modify command failed due to a control file write
error. An additional message relating to the write error should have been issued.
Action:
Verify that the control file in use is correct.
PSA0218
DATASTORE INIT CONTROL FILE UPDATE FAILED DUE TO ERROR: errorid.
Reason:
The message text indicates that the modify command failed due to a control file update
error. An additional message relating to the update error should have been issued.
Action:
Verify that the control file in use is correct.
PSA0219
SSANALZE DATASTORE=dstname INIT COMPLETE DB2=ssid.
Reason:
Indicates CA Subsystem Analyzer collection has successfully performed initialization of
the data store for collection use.
Action:
This message is informational only. It is followed by additional messages related to
collection initialization.
PSA0220
SANALZE VOLUME ANALYSIS Q/LOOP DETECTED VOL=xxxxxx
Reason:
This message is issued if more than 1000 I-O requests are found queued off of a single
volume.
Action:
None.
126 Message Reference Guide (PS to ZLB)
PSA Messages
PSA0222
Volume Analysis Q/Loop Detected.
Reason:
This message is issued if the CA Subsystem Analyzer volume activity monitor detects a
single DASD volume with more then 500 queued I/O requests. Requests in excess of 500
are not included in the CA Subsystem Analyzer volume statistics.
Action:
If you receive this message repeatedly, contact Technical Support.
PSA0230
CONTROL FILE DATASET NAME IS INVALID OR NOT FOUND
Reason:
The control file data set name contained in member SACFPARM within the Xmanager
CDBAPXMP data set does not exist (or the name is invalid). The control file is created
when the program is installed.
Action:
Browse the CDBAPXMP data set contained in the Xmanager started task JCL. Determine
whether the data set name contained within the member is valid. If the data set has
been deleted, attempt to restore the data set if possible.
PSA0231
SSANALZE CONTROL FILE ALLOCATE FAILED RC=rc
Reason:
Dynamic allocation of the control file data set failed. The message text includes the
SVC99 error reason code.
Action:
Look up the reason for the allocation failure in the IBM Application Development Guide:
Authorized Assembler Language Programs (System Macros and Facilities for MVS/XA)
manual.
Chapter 2: PS to PTUIX 127
PSA Messages
PSA0233
CONTROL FILE OPEN FAILED
Reason:
MVS OPEN processing for the control file failed. The control file is created when the
program is installed. Member SACFPARM in the Xmanager CDBAPXMP data set contains
the control file data set name in use.
Action:
Check the Xmanager job log and MVS SYSLOG for additional error messages regarding
the error. A message indicating the MVS OPEN error should have been issued using
WTO.
PSA0234
ERROR UPDATING SSANALZE CONTROL FILE, DELETE NOT PROCESSED
Reason:
An error occurred during an attempt to update the control file.
PSA0235
SSANALZE CONTROL FILE UPDATE FAILED, DATASET FULL
Reason:
The requested operation failed because the control file is full.
Action:
For information about creating and copying the control file, see the product
documentation.
PSA0236
SSANALZE CONTROL FILE UPDATE FAILED DUE TO VSAM ERROR
Reason:
An error occurred during an attempt to update the control file.
128 Message Reference Guide (PS to ZLB)
PSA Messages
PSA0237
DATASTORE datastore name IN USE, DELETE NOT PROCESSED
Reason:
A delete request failed because the datastore is in use by an active collection.
Action:
None.
PSA0238
DATASTORE datastore name IN USE
Reason:
A copy request failed because the target datastore is in use by an active collection.
Action:
None.
PSA0239
DATASTORE datastore name FOR SSID ssid NOT FOUND
Reason:
The specified datastore could not be found in the control file. An invalid datastore name
might have been specified, or the datastore might have been deleted.
Action:
Choose a datastore name from names available on the datastore display screens, and
then retry the operation.
PSA0300
INTERVAL CONTROL ERROR RPLREQ=X'aa' RPLRTNCD='aa' RPLERRCD=X'aa' DSID=nn
DB2=ssid.
Reason:
Indicates collection externalization to the data store has incurred a interval control
VSAM error.
Chapter 2: PS to PTUIX 129
PSA Messages
PSA0301
INSERT ERROR, RPLREQ=X'rplreq', RPLRTNCD=X'rplrtncd', RPLERRCD=X'rplerrcd',
DB2=ssid.
Reason:
A VSAM write error was incurred during CA Subsystem Analyzer collection
externalization processing. The message text includes the VSAM request type, return
code, error code, and DB2 subsystem ID.
Action:
Attempt to understand and resolve the problem based on information provided in the
message.
PSA0302
DATASTORE DATASET IS FULL DSID=nn DB2=ssid.
Reason:
This message is issued when a data store data set becomes full and the data set could
not be extended. When this message occurs, collection remains active, but
externalization to the data store data set is suspended.
The message identifies the data store data set ID that is full.
Action:
Create a new data store with increased space. Terminate collection and restart it with
the new data store name. You can still reference the old data store data, but if it is no
longer needed, delete the old data store.
PSA0303
CONTROL GET ERROR RPLREQ=X'aa' RPLRTNCD=X'aa' RPLERRCD=X'aa' DSID=nn
DB2=ssid.
Reason:
Indicates that collection externalization to the data store has incurred a VSAM GET error
while reading data store control information.
130 Message Reference Guide (PS to ZLB)
PSA Messages
PSA0304
INTERVAL GET ERROR RPLREQ=X'aa' RPLRTNCD=X'aa' RPLERRCD=X'aa' DSID=nn
DB2=ssid.
Reason:
Indicates that collection externalization to the data store has incurred a VSAM GET error
while reading data store interval information.
PSA0305
UPDATE ERROR RPLREQ=X'aa' RPLRTNCD=X'aa' RPLERRCD=X'aa' DSID=nn DB2=ssid.
Reason:
Indicates that collection externalization to the data store has incurred a VSAM
PUT/UPDATE error while updating data store data records.
PSA0306
INTERVAL UPDATE ERROR RPLREQ=X'aa' RPLRTNCD=X'aa' RPLERRCD=X'aa' DSID=nn
DB2=ssid.
Reason:
Indicates that collection externalization to the data store has incurred a VSAM
PUT/UPDATE error while updating interval information.
PSA0307
SSANALZE ALLOCATE FAILED S99ERROR=X'aaaa' S99INFO=X'aaaa' DSID=nn DB2=ssid.
Reason:
Indicates that an allocation error has been incurred on one of the data store data sets.
The message ID contains the data store data set identifier that incurred the error.
Action:
Attempt to determine the cause of the allocation failure.
Chapter 2: PS to PTUIX 131
PSA Messages
PSA0308
SSANALZE OPEN FAILED RC=X'aa' ACBERFLG=X'aa'DSID=nn DB2=ssid.
Reason:
This message indicates that an open error has been incurred on one of the data store
data sets. The message ID contains the data store data set identifier that incurred the
open error.
Action:
Attempt to determine the cause of the open error.
PSA0309
SSANALZE ALLOC FAILED DATASTORE DATASET DOES NOT EXIST DSID=nn DB2=ssid.
Reason:
Indicates that a data store data set owned by the data store does not exist. This may
indicate the data set was deleted outside of CA Subsystem Analyzer. Verify the proper
data store name is being used.
Action:
Determine if the data set can be restored. If you are unable to locate the data set, you
must create a new data store.
PSA0311
DATASTORE VALIDATION FAILED/VERSION vv.vv INCOMPATIBLE WITH SSANALZE
VERSION IN USE.
Reason:
The data store specified for use is incompatible with the version of CA Subsystem
Analyzer being executed.
Action:
The data store may only be used with a compatible version of CA Subsystem Analyzer. If
you have just installed a new level of CA Subsystem Analyzer, you must create and use a
new data store with the new version.
132 Message Reference Guide (PS to ZLB)
PSA Messages
PSA0312
DATASTORE REQUEST FAILED RPLREQ=X'aa' RPLRTNCD=X'aa' RPLERRCD=X'aa'.
Reason:
A request to access the data store has failed due to a VSAM related error.
Action:
Try the request again.
PSA0313
DATASTORE READ OPEN ERROR, RC=X'rc' ACBERFLG=X'aa'.
Reason:
A request to open a data store data set has failed due to a MVS OPEN error on the data
set.
Action:
Try the request again.
PSA0315
DB2 SUBSYSTEM ssid IS INVALID OR NOT ACTIVE.
Reason:
The subsystem associated with the SSID specified in the SYSIN input parameters to the
batch reporting facility is invalid or not currently active.
Action:
Ensure that the SSID value is correct in the SYSIN and that the subsystem is active and
rerun the job.
PSA0316
DATASTORE DSN IS UNAVAILABLE, DSN=dsname.
Reason:
The data store specified in the SYSIN input parameters to the CA Subsystem Analyzer
batch reporting facility is unavailable.
Chapter 2: PS to PTUIX 133
PSA Messages
PSA0317
DATASTORE DSN IS INVALID, DSN=dsname.
Reason:
The data store name specified in the SYSIN input parameters to the CA Subsystem
Analyzer batch reporting facility is invalid.
Action:
Check the input information with the data store information located on the CA
Subsystem Analyzer Datastore Display for the specified SSID. Be sure to check the VCAT
(or HLVL) for the data store.
PSA0318
DATASTORE DSN ALLOCATION FAILED, DSN=dsname.
Reason:
The CA Subsystem Analyzer batch reporting facility has failed to allocate the data store
data set.
Action:
Attempt to resolve the allocation failure. Examine the WTO messages received to help
determine the cause of the failure.
PSA0319
DATASTORE DSN IS EMPTY, DSN=dsname.
Reason:
The data store specified in the SYSIN input parameters to the CA Subsystem Analyzer
batch reporting facility is empty.
Action:
Check the input information with the data store information located on the CA
Subsystem Analyzer Datastore Display for the specified SSID. Be sure to check the VCAT
(or HLVL) for the data store.
134 Message Reference Guide (PS to ZLB)
PSA Messages
PSA0320
AUTHORIZATION FAILED FOR PLAN=planname.
Reason:
The user running the batch reporting job does not have the authority to access the CA
Subsystem Analyzer plans that read the data store.
Action:
Ensure that the USERID has access to the plan.
PSA0321
OPEN FAILED FOR SYSREC DATASET, UNLOAD BYPASSED.
Reason:
The batch reporting facility is unable to open the SYSREC data set that will contain the
unload data store information.
Action:
Check your JCL to verify that you have specified a valid SYSREC DD card as requested in
the batch reporting facility documentation.
PSA0322
OPEN FAILED FOR SYSREC DATASET, BAD LRECL, UNLOAD BYPASSED.
Reason:
The batch reporting facility is unable to open the SYSREC data set because of an invalid
LRECL.
Action:
Check your JCL to verify that you have specified a valid LRECL for the SYSREC data set.
PSA0323
INVALID VALUE FOR parameter PARAMETER, USING DEFAULT.
Reason:
You specified an invalid value for the parameter identified in the message. The default
value will be used.
Action:
Ensure that the value has been entered correctly and rerun batch reporting if necessary.
Chapter 2: PS to PTUIX 135
PSA Messages
PSA0324
UNSUPPORTED REPORT FILTER FOR THIS REPORT, FILTER WILL BE IGNORED,
FILTER=filter.
Reason:
You specified an unsupported report filter for this report.
Action:
Ensure that the filter is spelled correctly and that it is a supported filter for this report.
Rerun batch reporting if necessary.
PSA0330
XMANID INVALID ON EXEC PARM
Reason:
You specified an invalid Xmanager ID on the EXEC statement when invoking CA
Subsystem Analyzer batch reporting.
Action:
Ensure that the XMANID is four numeric characters.
PSA0331
WARNING, NO DATA FOR SELECTION CRITERIA.
Reason:
There is no data for the selection criteria.
Action:
Ensure that the data store contains collection data.
PSA0332
OPEN FAILED FOR SYSPRINT DATASET.
Reason:
The batch reporting facility is unable to open the SYSPRINT data set that will contain the
batch reporting facility output.
Action:
Check your JCL to verify that you have specified a valid SYSPRINT DD card as requested
in the batch reporting facility documentation.
136 Message Reference Guide (PS to ZLB)
PSA Messages
PSA0333
OPEN FAILED FOR SYSPRINT DATASET, INVALID LRECL.
Reason:
The batch reporting facility is unable to open the SYSPRINT data set because of an
invalid LRECL.
Action:
Check your JCL to verify that you have specified a valid LRECL for the SYSPRINT data set.
PSA0334
OPEN FAILED FOR dataset_type DATASET.
Reason:
The batch reporting facility is unable to open the SYSIN or the SYSOUT data set for batch
reporting as identified in the error message.
Action:
Check your JCL to verify that you have specified a valid DD card as requested in the
batch reporting facility documentation.
PSA0335
UNRECOGNIZED INPUT PARAMETER SPECIFIED, PARAMETER WILL BE IGNORED,
PARAMETER=parameter
Reason:
The batch reporting facility encountered an unrecognized parameter in the SYSIN cards.
The parameter will be ignored.
Action:
Check the input card and see the batch reporting facility documentation to determine
valid input information. Correct the SYSIN information and rerun the facility.
Chapter 2: PS to PTUIX 137
PSA Messages
PSA0337
UNSUPORTED SORT COLUMN SPECIFIED, USING DEFAULT, COLUMN=column.
Reason:
The batch reporting facility encountered an unsupported sort column and will use the
default sort column.
Action:
Check the input card and see the batch reporting facility documentation to determine
valid input information. Correct the SYSIN information and rerun the facility.
PSA0338
UNRECOGNIZED CONTENT VALUE WILL BE IGNORED, CONTENT =value.
Reason:
The batch reporting facility encountered an unrecognized content value in the SYSIN
cards.
Action:
Check the input card and see the batch reporting facility documentation to determine
valid input information. Correct the SYSIN information and rerun the facility.
PSA0339
UNSUPORTED FORMAT TYPE SPECIFIED, USING DEFAULT, FORMAT=type.
Reason:
The batch reporting facility encountered an unsupported format type and will use the
default type of SUMMARY.
Action:
Check the input card and see the batch reporting facility documentation to determine
valid input information. Correct the SYSIN information and rerun the facility.
138 Message Reference Guide (PS to ZLB)
PSA Messages
PSA0340
UNSUPORTED REPORT NAME SPECIFIED, REPORT=name.
Reason:
The batch reporting facility encountered an unsupported report name.
Action:
Check the input card and see the batch reporting facility documentation to determine
valid input information. Correct the SYSIN information and rerun the facility.
PSA0341
SSANALZE DATASTORE NAME NOT FOUND IN INPUT CARD PARAMETERS.
Reason:
The batch reporting facility did not find a data store name in the input cards.
Action:
Check the input cards and see the batch reporting facility documentation to determine
valid input information. Correct the SYSIN information and rerun the facility.
PSA0342
DB2 SUBSYSTEM ID NOT FOUND IN INPUT CARD PARAMETERS.
Reason:
The batch reporting facility did not find a DB2 subsystem ID in the input cards.
Action:
Check the input cards and see the batch reporting facility documentation to determine
valid input information. Correct the SYSIN information and rerun the facility.
PSA0343
XMANAGER IS NOT ACTIVE.
Reason:
The Xmanager associated with the XMANID specified in the batch reporting facility is
not currently active. The batch reporting facility requires the Xmanager started task to
be active to access the data store.
Action:
Start the Xmanager started task and rerun the facility.
Chapter 2: PS to PTUIX 139
PSA Messages
PSA0344
INTERNAL PROCESSING ERROR, SSWA NOT SET.
Reason:
The batch reporting facility encountered an internal error.
PSA0345
UNSUPORTED COLUMN IN SORT INPUT CARD FOR THIS REPORT, USING DEFAULT,
COLUMN=column.
Reason:
The batch reporting facility encountered an unsupported column specified as the sort
column for this report and will use the default sort column.
Action:
Check the input card and see the batch reporting facility documentation to determine
valid input information. Correct the SYSIN information and rerun the facility.
PSA0346
INVALID type FILTER - filter
Reason:
The batch reporting facility encountered an invalid DATE or TIME report selection filter
in the SYSIN cards. See the batch reporting facility documentation to determine valid
TIME or DATE filter formats.
Action:
Correct the SYSIN card and rerun the facility.
PSA0347
CONTINUED CONTROL CARD EXCEEDS MAXIMUM NUMBER OF CHARACTERS parameter.
Reason:
The batch reporting facility encountered a report parameter that exceeded the
maximum number of continuations. A report parameter may be continued onto a total
maximum of 100 input records.
Action:
Correct the SYSIN information and rerun the facility.
140 Message Reference Guide (PS to ZLB)
PSA Messages
PSA0360
COMPRESSION DICTIONARY name LOAD FAILED, R0=xxxxxxxx R15=xxxxxxxx
Reason:
The load of the CA Subsystem Analyzer compression dictionary failed during collection
initialization. The collection initialization is terminated. The message contains the name
of the compression dictionary load module and the register contents from the failing
load.
Action:
For assistance, contact CA Support at http://ca.com/support.
PSA0361
EXPANSION DICTIONARY name LOAD FAILED, R0=xxxxxxxx R15=xxxxxxxx
Reason:
The load of the CA Subsystem Analyzer expansion dictionary failed during collection
initialization or during a user request to view collection data. The collection initialization
or user request is terminated. The message contains the name of the expansion
dictionary load module and the register contents from the failing load.
Action:
For assistance, contact CA Support at http://ca.com/support.
PSA0362
ERROR UPDATING DATASTORE CONTROL INFORMATION
[email protected]@@@@@@@@@ [email protected]@ [email protected]@@@
Reason:
Collection externalization to the data store incurred a VSAM UPDATE error while
updating the data store control record.
Action:
If you cannot determine the cause of the failure, contact CA Support.
Chapter 2: PS to PTUIX 141
PSA Messages
PSA0367
ERROR UPDATING DATASTORE INTERVAL RECORD [email protected]@ [email protected]@@@
Reason:
Collection externalization to the data store incurred a VSAM UPDATE error while
updating the data store interval information.
Action:
If you cannot determine the cause of the failure, contact CA Support.
PSA0368
ERROR READING DATASTORE CONTROL INFORMATION DSID [email protected]@ [email protected]@@@
Reason:
Data store validation failed. The SSID of the data store does not match the CA
Subsystem Analyzer SSID in use.
Action:
If you cannot determine the cause of the failure, contact CA Support.
PSA0369
ERROR READING DATASTORE INTERVAL RECORD [email protected]@ [email protected]@@@
Reason:
Collection externalization to the data store incurred a VSAM GET error while reading
data store interval information.
Action:
If you cannot determine the cause of the failure, contact CA Support.
PSA0601
DB2 SSID IS INVALID OR NOT ACTIVE
Reason:
An offline request was made to create a CA Subsystem Analyzer data store for an
inactive or invalid DB2 subsystem.
Action:
Correct the SSID control card in the data store create request or start the DB2
subsystem for which the data store is being created.
142 Message Reference Guide (PS to ZLB)
PSA Messages
PSA0602
XMANAGER IS NOT ACTIVE; REQUEST IGNORED
Reason:
An offline request was made to create a CA Subsystem Analyzer data store for an
inactive or invalid XMANAGER task.
Action:
Start the XMANAGER task or correct the XMANID control Card in the data store create
request.
PSA0603
REQ FAILED; ABEND INCURRED; RECOVERY SUCCESSFUL
Reason:
An offline request was made to create a CA Subsystem Analyzer data store. The create
data store request failed with an abend.
Action:
Examine the associated messages to determine the cause of the failure.
PSA0634
OPEN FAILED FOR @@@@@@ DATASET
Reason:
An offline request was made to create a CA Subsystem Analyzer data store. The request
failed because DATASET @@@@@@ could not be accessed.
Action:
Examine the associated messages to determine the cause of the failure.
Chapter 2: PS to PTUIX 143
PSA Messages
PSA0640
DATASTORE NAME ALREADY EXISTS; SPECIFY UNIQUE NAME
Reason:
An offline request was made to create a CA Subsystem Analyzer data store that already
exists.
Action:
Use the current data store, as is, or change the DST (data store) or VCAT control cards in
the request to create a new data store.
PSA0644
DATASTORE INIT FAILED; ERROR RELATED WTO ISSUED
Reason:
An offline request was made to create a CA Subsystem Analyzer data store that failed.
Action:
This message directs the user to view the information in the Joblog to gather additional
information on the reason the data store initialization failed.
PSA0651
CONTROL FILE HAS NOT BEEN INITIALIZED
Reason:
Indicates an error during batch datastore utility execution, PSADSALC. This error can
occur when the SACFPARM member within high-level.CDBAPXMP contains a CDSN
specification but the actual PSA control file VSAM data set was not allocated as
expected. Other possible reasons may be that the SACFPARM member does not exist in
high-level.CDBAPXMP or it exists but does not contain a valid CDSN entry or is blank or
empty.
Action:
Review and correct your settings.
144 Message Reference Guide (PS to ZLB)
PSA Messages
PSA0700
ALLOC FAILED ID=dsnid S99INFO=X'aaaa' S99ERROR=X'aaaa'.
Reason:
A data set dynamic allocation request has failed. The message text includes an internal
data set identifier that describes the data set incurring the error, the SVC99 information,
and error data contents.
Action:
Attempt to resolve the allocation message.
PSA0701
DEALLOC FAILED ID=dsnid S99INFO=X'aaaa' S99ERROR=X'aaaa'.
Reason:
A data set dynamic deallocation request has failed. Message text includes an internal
data set identifier that describes the data set incurring the error, the SVC99 information,
and error data contents.
Action:
Attempt to resolve the deallocation message.
PSA0702
OPEN FAILED ID=dsnid RC=X''rc'' ACBERFLG=X'aa'.
Reason:
A data set OPEN request has failed. Message text includes an internal data set identifier
that describes the data set incurring the OPEN error, the OPEN return code, and ACB
error flag contents.
Action:
Attempt to resolve the OPEN error.
Chapter 2: PS to PTUIX 145
PSA Messages
PSA0703
PUT FAILED ID=dsnid RPLRTN=X'aa' RPLERR=X'aa'.
Reason:
A data set PUT request has failed. Message text includes an internal data set identifier
that describes the data set incurring the PUT error, the RPL return code, and RPL error
flag contents.
Action:
Attempt to resolve the PUT error.
PSA0704
SSANALZE CONTROL FILE INIT HAS FAILED.
Reason:
Initialization of the CA Subsystem Analyzer control file during Xmanager initialization has
failed. During Xmanager initialization, CA Subsystem Analyzer exit processing derives
the control file name to be used from the Xmanager CDBAPXMP data set, member
name SACFPARM. Indicates there was a problem locating the member name or the
member contents were invalid. The member is placed into the CDBAPXMP data set
when the control file is created during the installation process.
Action:
Verify the CDBAPXMP Xmanager data set contains the SACFPARM member. Examine its
contents. Terminate and restart the Xmanager address space.
For assistance, contact CA Support at http://ca.com/support.
PSA0705
CONTROL FILE WRITE ERROR RPLREQ=X'aa' RPLRTNCD=X'aa' RPLERRCD=X'aa'.
Reason:
Indicates a VSAM write error was incurred on the control file. Message contains the
VSAM RPL diagnostic data at the time of error.
146 Message Reference Guide (PS to ZLB)
PSA Messages
PSA0806
SSANALZE CTHREAD FAILED/PLAN NOT FOUND OR NOT AUTHORIZED DB2=ssid
Reason:
A DB2 thread could not be created for the task that locates the DB2 table name based
on the DB2 object ID, the required plan was not defined to the DB2 subsystem, or the
user ID for the XMANAGER started task was not authorized to execute the plan. This
message identifies the DB2 subsystem for which the CA Subsystem Analyzer collector is
being started.
Action:
Verify that the CA Subsystem Analyzer primary plan is available and that the
authorization is correct. The planname is specified in the issuance of the $START (SSA)
with the PLAN(xxxxxxxx) parameter or in the PLANSxx parmlib member. Verify that the
user ID for the XMANAGER started task is authorized to execute the CA Subsystem
Analyzer primary plan.
PSA0807
SSANALZE CTHREAD FAILED/PLAN NOT AUTHORIZED DB2=ssid.
ssid = The DB2 subsystem for which a collection start has been requested.
Reason:
A DB2 thread could not be created for the task which locates the DB2 table name based
on the DB2 object ID, due to authorization.
Action:
Ensure that the user ID for the XMANAGER started task is authorized to execute the CA
Subsystem Analyzer primary plan.
PSA0808
MSGTXT='TABLE LOCFAIL SQLCODE=xxx DB=xxxxxxxx TS=xxxxxxxx TBID=xxxx DB2=ssid
Reason:
Indicates that a request to locate the Creator and Tablename for table TBID failed with
an unexpected SQLCODE.
Action:
This message may be due to maintenance or a new installation with the CA Subsystem
Analyzer plan PSAAxxx not rebound in the DB2 subsystem that is being monitored by CA
Subsystem Analyzer.
For assistance, contact Technical Support at http://ca.com/support.
Chapter 2: PS to PTUIX 147
PSA Messages
PSA0811
SSANALZE CTHREAD FAILED/DB2 IS TERMING DB2=ssid
Reason:
A DB2 thread could not be created for the task that locates the DB2 table name based
on the DB2 object ID because the DB2 subsystem is terminating. This message identifies
the DB2 subsystem for which the CA Subsystem Analyzer collector is being started.
Action:
Restart the CA Subsystem Analyzer collector once the DB2 subsystem is started.
PSA0815
SSANALZE SDUMP CAPTURE COMPLETE DB2 DP2E RETURN CODE 00 REASON 00
Reason:
SSANALYZE collection failed due to abnormal termination. Error handling recovery logic
has recovered from the abend. SSANALYZE collection has been disabled.
Action:
View the joblog or z/OS syslog for additional error WTO messages.
PSA0820
TABLE LOCFAIL SQLCODE=-805. REASON xx DB=xxxxxxxx TS=xxxxxxxx TBID=xxxx
DB2=xxxxx".
Reason:
Indicates that a request to locate the Creator and Tablename for table TBID failed with
an -805 SQLCODE.
Action:
This message may be due to maintenance or a new installation with the Subsystem
Analyzer plan PSAAxxx not rebound in the DB2 subsystem being monitored by
Subsystem Analyzer.
PSA1020
COLLECTION STATUS PROPIGATION FAILED - reason.
Reason:
Indicates that an attempt to communicate active collection status to the Xmanager
sysplex group members failed. reason is the reason for the failure.
148 Message Reference Guide (PS to ZLB)
PT Messages
PSA1021
COLLECTION STATUS PROPIGATION RESUMED.
Reason:
Indicates that CA Subsystem Analyzer resumed communication of active collection
status to the Xmanager sysplex group members.
Action:
None.
PSA1022
REQUEST HAS FAILED. CROSS SYSTEM ERROR.
Reason:
Indicates that CA Subsystem Analyzer request has failed due to a Xmanager cross
systems communication error.
PT Messages
Messages with the PT prefix are generated from general facilities used by several
products, including: CA Data Compressor, CA Fast Check, CA Fast Index, CA Fast Load, CA
Fast Recover, CA Fast Unload, CA LogCompress, CA Merge/Modify, CA Partition Expert,
CA Quick Copy, and CA Rapid Reorg.
PT000E
NOT ENOUGH MEMORY TO CONTINUE PROCESSING, APPLICATION TERMINATED.
Reason:
CA products require more memory to continue processing.
Action:
Increase your region size.
Chapter 2: PS to PTUIX 149
PT Messages
PT001E
INVALID COMMAND.
Reason:
You have entered an invalid command.
Action:
You can enter a question mark (?) from any screen's command line to display a list of
valid commands. Entering another question mark next to the command in question will
give you syntax information.
PT002E
TOO MANY OPERANDS.
Reason:
You have specified a valid scrolling command, but have specified too many operands. If
you are specifying a column name that includes a space, you must enclose the name in
single quotation marks so that the scrolling routine knows that the column name is the
whole string.
Action:
You can enter a question mark (?) to get a list of valid commands. Entering another
question mark next to the command in question will give you syntax information.
PT003E
PUT STRING IN QUOTES.
Reason:
The input character parameter needs to be enclosed in quotes.
Action:
Enclose the string in quotes and try again.
PT004E
NO OPERANDS ALLOWED.
Reason:
No operands are allowed for the command you have entered. The MELT command is an
example of commands that do not allow operands. This is because MELT pertains to all
columns, not a specified column.
150 Message Reference Guide (PS to ZLB)
PT Messages
PT005E
REQUIRED OPERAND MISSING.
Reason:
You must include one of the partitions selected by the utility you are attempting to
terminate using PART(n). The PART(n) requirement prevents global deletes since rows
can be in the table for the same database or tablespace but different partitions.
Action:
Specify PART(0) for a non-partitioned object. PART(0) signifies that ALL of the partitions
have been selected or that NO partitions have been selected.
PT006E
REQUEST NOT SUPPORTED BY APPLICATION.
Reason:
The requested function is not supported by the current application.
Action:
See the product documentation for information on supported functions.
PT007E
SAME DELIMITER MUST BE USED FOR END OF STRING.
Action:
Use the same delimiter for the beginning and ending delimiter. For example, use single
quotation marks.
PT008E
COLUMN NAME NOT FOUND.
Reason:
You have entered a scrolling command that requires a column name and the column
you have specified cannot be found on the current scrollable list.
Action:
Ensure that you have entered the column name correctly. If the column name contains
spaces, you must enclose the column name in single quotation marks.
Chapter 2: PS to PTUIX 151
PT Messages
PT009E
COLUMN NAME NOT UNIQUE.
Reason:
You have entered a scrolling command that requires a column name and the column
you have specified cannot be uniquely identified by the string you have entered. For
example, if there are two columns, COL1A and COL2A, you could not use the string COL
to represent column because the name would not be unique and the product would
not know which column to use.
Action:
You must specify enough of the name to make it unique, for example, COL1 and COL2.
PT010E
COLUMN ALREADY FROZEN.
Reason:
You have entered the FREEZE command on a column that is already frozen.
Action:
To unfreeze a single column, use the UNfreeze command. To unfreeze all frozen
columns, use the MELT command.
PT011E
REQUEST NOT SUPPORTED FOR THIS COLUMN.
Reason:
You have specified a scrolling command for a column that does not support this
command. For example, object selection lists do not support the UNfreeze command for
the object name column.
PT012E
COLUMN NOT FROZEN.
Reason:
You have entered the UNfreeze command for a column that is not frozen or have
entered to MELT command when no columns are frozen.
152 Message Reference Guide (PS to ZLB)
PT Messages
PT013E
INVALID SORT OPERAND.
Reason:
An invalid SORT operand has been entered.
PT014W
ALREADY AT TOP.
Reason:
You have requested to scroll UP, but the scrollable list is already at the top.
PT015W
ALREADY AT LEFT.
Reason:
You have requested to scroll LEFT, but the scrollable list is already all the way to the left.
PT016W
ALREADY AT RIGHT.
Reason:
You have requested to scroll RIGHT, but the scrollable list is already all the way to the
right.
PT017E
NOT ENOUGH ROOM TO FREEZE COLUMN.
Reason:
The FREEZE command locks a column's place on the display. You can freeze as many
columns that can fit on the screen. You cannot freeze a column if there is no room on
the screen (because other columns are frozen). PT017E displays when you request to
freeze a column and there is no room to display it.
Action:
You must UNfreeze columnS to make room for the column you want to freeze.
Chapter 2: PS to PTUIX 153
PT Messages
PT018E
COLUMN NOT LARGE ENOUGH TO CONTAIN STRING.
Reason:
You have entered the FIND command with a string that is longer than the specified
column's length. For example, you have entered FIND 'A234567' NAME and NAME's
length is 4.
Action:
You can correct the string and search again, or do a global search by removing the
column name.
PT019I
BOTTOM OF DATA REACHED.
Reason:
You have entered the FIND command, and the scrolling routine reached the bottom of
the data without finding the string. You can try the search again from the top of the list.
PT020E
NOT ENOUGH UNFROZEN SCREEN TO DISPLAY COLUMN.
Reason:
You have entered the FIND command for a column that is not currently displayed. This
column cannot be displayed because the frozen columns are taking up too much of the
screen.
PT021W
ENTER A FIND COMMAND.
Reason:
The RFIND command was entered without a previous FIND command.
PT022I
STRING FOUND.
Reason:
You have entered the FIND command and it was successful. The cursor moves to the
first character of the string you searched for.
154 Message Reference Guide (PS to ZLB)
PT Messages
PT023W
STRING string NOT FOUND.
Reason:
You have entered the FIND command and the search has not been successful. You may
have typed the string incorrectly. If the string is correct, try the search again from the
beginning of the scrollable list.
PT024W
STRING FOUND BUT NOT VISIBLE ON SCREEN.
Reason:
You have entered the FIND command and the search has been successful. However, the
string was found in a column that is not currently displayed. This column cannot be
displayed because the frozen columns are taking up too much of the screen.
PT025W
ALREADY POSITIONED AT FIRST ITEM.
Reason:
You pressed PF7 to scroll to the previous item, but the first item is already displayed.
Action:
Use PF10 to scroll to the top of the item.
PT026W
ALREADY POSITIONED AT LAST ITEM.
Reason:
You pressed PF8 to scroll to the next item, but the last item is already displayed.
Action:
Use PF11 to scroll to the bottom of the item.
Chapter 2: PS to PTUIX 155
PT Messages
PT027W
ALREADY AT TOP OF ITEM.
Reason:
You pressed PF10 to scroll to the top of the item, but the item was already at the top.
Action:
Use PF7 to scroll to the previous item.
PT028W
ALREADY AT BOTTOM OF ITEM.
Reason:
You pressed PF11 to scroll to the bottom of the item, but the item was already at the
bottom.
Action:
Use PF8 to scroll to the next item.
PT029I
USE PF10/11 FOR UP/DOWN WITHIN DATA ITEM.
Reason:
Some scrollable lists, such as RC/QUERY Detail reports have data items that are larger
than a single screen can display. For such lists, you use PF7/8 to scroll through the list,
from item to item.
Action:
Use PF10/11 to scroll within the item. For example, if there are two Table Detail reports,
one for table DEPT and one for table EMP, you would use PF7/8 to scroll within the
Table Detail report for DEPT or EMP. Use the PF10/11 to scroll within the DEPT report or
within the EMP report.
156 Message Reference Guide (PS to ZLB)
PT Messages
PT030E
INVALID COMMAND HAS BEEN ENTERED, PLEASE CORRECT.
Reason:
You have entered an invalid command.
Action:
You can enter a question mark (?) from any screen's command line to display a list of
valid commands.
PT031E
SUM OF COLUMN SIZES EXCEEDS MAXIMUM ROWSIZE, PLEASE CORRECT.
Reason:
The sum of the lengths of the columns you have specified exceeds 4056 bytes, the
maximum rowsize (for a 4K page).
Action:
You must change the lengths of the columns so that the sum does not exceed 4056.
PT032E
ENTER "S", A VALID RC/QUERY OPTION, OR "?" FOR RC/QUERY MENU.
Reason:
You have entered an invalid selection option on an object selection list.
Action:
Enter "S" to select the object for the current function, or enter a valid RC/QUERY report
option. For a list of valid RC/QUERY report options, enter a question mark (?) in the
selection field.
PT033E
NOT ENOUGH MEMORY TO CONTINUE PROCESSING.
Reason:
CA products require more memory to continue processing.
Action:
Increase the region size.
Chapter 2: PS to PTUIX 157
PT Messages
PT034E
SOME TYPE CONVERSIONS WERE INVALID AND HAVE BEEN RESET.
Reason:
Some column type conversions are invalid. The data type has been reset to its original
type.
PT035I
LIMIT VALUES ASSOCIATED WITH MODIFIED KEY COLUMNS MUST BE RESPECIFIED.
Reason:
The data type of a key column has changed. Limit keys must be changed to reflect the
new data types.
PT036I
A PRIMARY KEY DOES NOT CURRENTLY EXIST FOR THIS TABLE.
Reason:
A primary key column has not been specified for this table.
Action:
Specify a primary key column.
PT037I
THERE ARE NO COLUMNS IN THIS TABLE.
Reason:
Currently, there are no columns defined for this table.
Action:
You must define columns for the table.
158 Message Reference Guide (PS to ZLB)
PT Messages
PT038I
THERE ARE NO COLUMNS IN THIS TABLE.
Reason:
Currently, there are no columns defined for this table. You requested to insert a column
into the primary key. There are no columns to insert; all columns in the table are already
defined as part of the primary key.
Action:
You must define columns for the table.
PT039E
UNABLE TO RESOLVE EQF EXTERNAL REFERENCE, ERROR FOUND IN: PTATALF2.
Reason:
The stored query (EQF) module could not be found.
Action:
Check for module PTLSSP in the library allocated to PTILIB, the library that contains the
CA products.
PT040I
QPRINT REQUEST COMPLETED.
Reason:
Your QPRINT request was completed. This message is for information only and does not
indicate a problem.
PT041E
QPRINT REQUEST FAILED.
Reason:
Due to environmental problems, your QPRINT request has failed.
Action:
Check your Print Parameters Profile and retry.
Chapter 2: PS to PTUIX 159
PT Messages
PT042I
PPRINT REQUEST COMPLETED.
Reason:
Your PPRINT request was completed. This message is for information only and does not
indicate a problem.
PT043E
PPRINT REQUEST FAILED.
Reason:
Due to environmental problems, your PPRINT request has failed.
Action:
Check your Print Parameters Profile and retry.
PT044W
COLUMN ALREADY EXCLUDED.
Reason:
You requested to EXCLUDE a column that is already excluded. The column will remain
excluded.
PT045E
CANNOT EXCLUDE FROZEN COLUMN.
Reason:
You have entered the EXCLUDE command for a column that is frozen.
Action:
Use the UNfreeze command to unfreeze a specific column or the MELT command to
unfreeze all frozen columns. Some scrollable lists have columns that are frozen by
default and may not be unfrozen. For example, object names on object selection lists
are frozen by default and may not be unfrozen. You cannot use the EXCLUDE command
on these columns.
160 Message Reference Guide (PS to ZLB)
PT Messages
PT046W
COLUMN ALREADY SHOWING.
Reason:
You have entered the SHOW command for a column that has not been EXCLUDED. The
SHOW command brings back to the display columns that were hidden using the
EXCLUDE command.
PT047E
DYNAMIC ALLOCATION ERROR, RC = code, RSN = reason, INFO = info.
Reason:
Dynamic Allocation has failed for the data set name that you specified for the current
function. The message provides you with the DYNALLOC return code, INFO code, and
ERROR code. This allows you to locate the problem in the appropriate IBM macro
manual.
PT048E
PRINT FILE OPEN ERROR.
Reason:
An output file open error has been encountered.
Action:
Check your Print Parameters Profile and retry.
PT049E
DYNAMIC DE-ALLOCATION ERROR RC = code, RSN = reason, INFO = info.
Reason:
Dynamic Allocation has failed for the data set name that you specified for the current
function. The message provides you with the DYNALLOC return code, INFO code, and
ERROR code. This allows you to locate the problem in the appropriate IBM macro
manual.
Chapter 2: PS to PTUIX 161
PT Messages
PT050W
SQL PAGE NOT PRINTED; PRINT LINE SIZE NOT LARGE ENOUGH.
Reason:
The SQL page was not printed because the line size is too small. Increase the line size in
your Print Parameters Profile and retry.
PT051W
SQL PAGE NOT PRINTED; NOT ENOUGH STORAGE FOR REQUEST.
Reason:
The SQL page was not printed because not enough storage could be found. Increase
your region size and try again.
PT052W
NO COLUMNS EXCLUDED.
Reason:
You entered the SHOW command and no columns were :excluded. This does not
indicate a problem.
PT053E
REQUEST FAILED DUE TO BAD PARMS - CALL CUSTOMER SUPPORT.
Reason:
The request has failed due to internal errors.
PT054W
VALID PRINT PARMS REQUIRED TO PRINT.
Action:
In order to use the QPRINT or PPRINT commands, you must complete your Print
Parameters Profile. The Print Parameters Profile screen displays so that you can
complete or correct your profile. When you have completed your profile, press PF3
(END) to return to the previous screen and complete your print request.
162 Message Reference Guide (PS to ZLB)
PT Messages
PT055W
QPRINT REQUEST CANCELED.
Reason:
The QPRINT request was canceled by the user. This message is for information only and
does not indicate a problem.
PT056W
PPRINT REQUEST CANCELED.
Reason:
The PPRINT request was canceled by the user. This message is for information only and
does not indicate a problem.
PT058E
ONLINE EXECUTION COMPLETED.
Reason:
The current online function has completed execution. This message is for information
only.
PT059E
BATCH JOB SUBMITTED.
Reason:
Your batch job request was successfully submitted to JES for execution.
PT060E
INVALID PARMS PASSED TO PTADSNQ.
Reason:
An internal error has occurred.
Chapter 2: PS to PTUIX 163
PT Messages
PT061I
DATASET ALREADY ALLOCATED. PLEASE SPECIFY A DIFFERENT DATASET.
Reason:
The output data set specified already exists.
Action:
Specify another data set name.
PT062E
DATASET NAME CANNOT BE ENQUED. GRS RESOURCE LIMIT EXCEEDED.
Reason:
GRS returned a return code indicating that the ENQ/RESERVE request has exceeded a
threshold value for the system.
Action:
Contact your MVS Systems Programmer.
PT063E
ENQ FOR DATASET NAME FAILED.
Reason:
MVS ENQUE for the system has failed for the specified data set.
Action:
Contact your MVS Systems Programmer.
PT064E
CHANGE OF DBCS CHARACTERS CAUSED OVERLAY OF UNVIEWABLE CHARACTERS.
Reason:
Due to display corrections, addition characters needed to be inserted in the DBCS string.
You have overlaid one or more of these characters. This would increase the size of the
original data. The input data is ignored.
164 Message Reference Guide (PS to ZLB)
PT Messages
PT065I
BATCH PROCESSOR JCL HAS BEEN WRITTEN TO THE REQUESTED DATASET.
Reason:
Your batch job was successfully written to the specified data set.
PT066E
BATCH PROCESSOR FILE DE-ALLOCATED FAILURE.
Reason:
Due to environmental conditions, the Batch Processor file deallocation has failed.
Action:
Contact your MVS Systems Programmer.
PT067E
BATCH PROCESSOR FILE OPEN FAILURE.
Reason:
Due to environmental conditions, the Batch Processor file open has failed.
Action:
Contact your MVS Systems Programmer.
PT068E
BATCH PROCESSOR FILE ALLOCATION FAILURE.
Reason:
Due to environmental conditions, the Batch Processor file allocation has failed.
Action:
Contact your MVS Systems Programmer.
PT069E
INTERNAL PARAMETER LIST ERROR.
Reason:
An internal error has occurred.
Chapter 2: PS to PTUIX 165
PT Messages
PT070E
PHYSICAL I/O ERROR WHILE PROCESSING MEMBER SELECTION.
Reason:
A physical I/O error has occurred while reading the directory of a PDS.
Action:
Check the validity of the data set.
PT071E
OPEN FAILURE WHILE PROCESSING MEMBER SELECTION.
Reason:
The data set cannot be opened to get the member selection list.
Action:
Check the validity of the data set.
PT072E
UNABLE TO DYNAMICALLY ALLOCATE THE REQUESTED DATASET.
Reason:
Due to environmental conditions, the requested data set allocation has failed.
Action:
Contact your MVS Systems Programmer.
PT073E
SHORTAGE OF MEMORY ENCOUNTERED WHILE PROCESSING MEMBER SELECTION.
Reason:
While processing member selection, a shortage of memory was encountered.
Action:
Increase the region size.
166 Message Reference Guide (PS to ZLB)
PT Messages
PT074E
FAILURE DURING TASK I/O TABLE PROCESSING DURING MEMBER SELECTION.
Reason:
An internal error occurred while processing a member selection list.
PT075E
MEMBER SELECTION HAS BEEN ENDED WITHOUT SELECTING A MEMBER.
Reason:
You entered selection criteria in the member name field to display a member selection
list, then you exited from the member selection list screen without selecting a member.
Action:
You must specify a member name if you are using a PDS. You can redisplay the selection
list or specify a member name.
PT076E
THE MEMBER YOU HAVE SELECTED DOES NOT EXIST.
Reason:
The model JCL Member was not found in the specified library.
Action:
Enter an asterisk (*) for a listing of the members contained in the selected library.
PT077E
OUTPUT MEMBER EXISTS, AND YOU HAVE CHOSEN NOT TO REPLACE IT.
Reason:
You have specified an existing PDS member name and have specified (N)o for the
Replace Existing Member prompt.
Action:
You must specify a new member name or change the Replace Existing prompt to (Y)es.
Chapter 2: PS to PTUIX 167
PT Messages
PT078E
DYNAMIC ALLOC. FAILED FOR BP INPUT FILE, RET CODE = return-code.
Reason:
Dynamic Allocation has failed for the data set name that you specified for the current
function.
PT079E
UNABLE TO OPEN FILE.
Reason:
The specified data set could not be opened.
Action:
Check the data set's validity and your authorizations on the data set.
PT080E
FILE CANNOT CONTAIN ANY .COMMANDS FOR ONLINE PROCESSING.
Reason:
Batch Processor commands (those that begin with a period) cannot be executed online.
The data set contains Batch Processor commands and so must be executed in batch
mode.
PT081I
SELECT A MEMBER TO USE.
Reason:
The Member Selection list screen displays so that you can select a PDS member to use
for your Batch Processor input. The PDS name is taken from the screen.
Action:
Enter "S" next to the member you want to use.
168 Message Reference Guide (PS to ZLB)
PT Messages
PT082I
SELECT A MEMBER TO CONTAIN YOUR BATCH PROCESSOR JCL.
Reason:
The Member Selection list screen displays so that you can select a PDS member to use
for your Batch Processor JCL data set. The PDS name is taken from the screen.
Action:
Enter "S" next to the member you want to use.
PT083E
UNABLE TO ALLOCATE TEMPORARY DATASET FOR BATCH PROCESSOR OPTIONS.
Reason:
Due to environmental conditions, the Batch Processor file allocation has failed.
Action:
Contact your MVS Systems Programmer.
PT084E
UNABLE TO OPEN THE TEMPORARY DATASET FOR BATCH PROCESSOR OPTIONS.
Reason:
Due to environmental conditions, the Batch Processor file open has failed.
Action:
Contact your MVS Systems Programmer.
PT085I
SEARCH FOR ">ERROR" IN OUTPUT TO LOCATE ERRORS FOUND IN PROCESSING.
Reason:
Errors were found in processing.
Action:
To locate the errors, do a FIND '>ERROR'.
Chapter 2: PS to PTUIX 169
PT Messages
PT086E
NOT ENOUGH MEMORY TO PROCESS.
Reason:
More memory is needed to continue processing.
Action:
Increase the region size.
PT087E
UNABLE TO LINK BATCH PROCESSOR MODULE.
Reason:
The Batch Processor was unable to successfully LINK to one of its main subservice
modules. This can be caused by not having the product library DDNAME allocated
properly. The DDNAME that should be allocated is PTILIB and that library contains the
subroutine services needed.
PT088I
THE MEMBER YOU ATTEMPTED TO BROWSE IS EMPTY.
Reason:
The member you attempted to browse contains no data.
PT089I
NO OBJECTS MATCH SELECTION CRITERIA.
Reason:
No objects match the selection criteria you have entered.
Action:
Check your object types and selection criteria carefully. You can enter asterisks in the
Object Name or Creator prompts to list ALL.
170 Message Reference Guide (PS to ZLB)
PT Messages
PT090E
ENTER 1 "S" TO SELECT, OR ENTER A VALID RC/QUERY REPORT OPTION.
Reason:
More than one selection has been made, or the line command was not a valid
RC/QUERY report option for the type of DB2 object to be selected.
Action:
Enter only one "S" to select. Or, enter a valid RC/QUERY report option.
PT091E
JOB NAME INVALID OR NO NAME SPECIFIED.
Reason:
The JOB name on the JOB card does not exist or it is invalid.
Action:
Ensure that there are no blanks between the // and the JOB name and that a JOB name
has been specified.
PT093E
STORED QUERY NOT FOUND, CANNOT BE EDITED.
Reason:
You have specified a stored EQF query that cannot be found.
Action:
You can enter "S" in the Where field without a query name to display a list of stored
queries.
Chapter 2: PS to PTUIX 171
PT Messages
PT094I
DEFAULT STORED QUERY USED.
Reason:
The requested report has a default stored query attached to it. This query, whose name
displays in the Where field, was used to display the report.
Action:
If you want to display the report without using the default query, you must edit the
query and change the Default value to "N". You can also specify a different query for the
report.
PT095E
STORED QUERY NOT FOUND AND NO DEFAULT EXISTS.
Reason:
The stored query name does not exist for the requested report. No default query exists
for report. The report was displayed without using an extended query.
PT096E
NOT ENOUGH STORAGE TO PROCESS STORED QUERIES.
Reason:
There was not enough available storage to process the requested queries.
Action:
Increase your region size and try again.
PT097E
WHERE FIELD ==> VALID OPTIONS ARE (Y), (S), (N).
Reason:
You have entered an invalid option for the Where field.
Action:
Valid options are as follows: N, Y, and S.
172 Message Reference Guide (PS to ZLB)
PT Messages
PT098E
AN SQL ERROR HAS BEEN DETECTED IN YOUR SELECTION.
Reason:
The selection criteria has caused an SQL error.
Action:
Review the SQL error and correct the problem.
PT099I
SELECTED COLUMNS HAVE BEEN QUEUED, ENTER "(S)HRINK" TO VIEW QUEUE.
Reason:
You have selected columns.
Action:
You can continue to select columns or enter the SHRINK command to view only selected
columns.
PT100I
SELECTED VOLUMES HAVE BEEN QUEUED, ENTER "(S)HRINK" TO VIEW QUEUE.
Reason:
You have selected volumes.
Action:
You can continue to select volumes or enter the SHRINK command to view only selected
volumes.
PT101E
YOU MUST ENTER A LIMIT KEY CONSTANT FOR AT LEAST THE FIRST KEY COLUMN.
Reason:
A partitioned index space must have key constants defined for at least the first key
column.
Action:
If you try to PF3 or CANCEL from the Limit Keys screens without defining any key
constants, you will get this message. Define the limit key constants for the first column.
Chapter 2: PS to PTUIX 173
PT Messages
PT102E
LIMITS MUST BE CONTIGUOUS, INTERVENING KEYS COLUMNS MAY NOT BE BLANK.
Reason:
A partitioned index space must have key constants defined for all partitions.
Action:
If you try to PF3 or CANCEL from the Limit Keys screens without defining any key
constants, you will get this message. Define the limit key constants for the partitions.
PT103I
SELECTED USERIDS HAVE BEEN QUEUED, ENTER "(S)HRINK" TO VIEW QUEUE.
Reason:
You have selected user IDs.
Action:
You can continue to select user IDs or enter the SHRINK command to view only selected
user IDs.
PT104I
REQUESTED ROW LIMIT HAS BEEN REACHED.
Reason:
The row limit you requested has been reached. This message is for information only and
does not indicate a problem.
PT105E
NOT ENOUGH MEMORY TO CONTINUE PROCESSING, REQUEST TERMINATED.
Reason:
Your request has been terminated due to insufficient memory.
Action:
Increase the region size.
174 Message Reference Guide (PS to ZLB)
PT Messages
PT106I
REQUEST HAS BEEN CANCELED.
Reason:
The user has canceled a request. This message is for information only.
PT107E
AN SQL ERROR HAS BEEN ENCOUNTERED, REQUEST TERMINATED.
Reason:
An SQL error has been encountered.
Action:
Review the SQL error message and correct the SQL error.
PT108I
SQL STATEMENT RESULT TABLE IS EMPTY.
Reason:
The SQL statement returned no rows.
PT109E
INVALID PRIMARY COMMAND HAS BEEN ENTERED, PLEASE CORRECT.
Reason:
You have entered an invalid primary command.
Action:
You can enter a question mark (?) from any screen's command line to display a list of
valid commands.
PT110I
YOU ARE EDITING YOUR BATCH PROCESSOR INPUT FILE.
Reason:
You specified (Y)es for the Edit Input Dataset prompt and the input data set displays.
This is an information message reminding you that the data set you are editing is your
Batch Processor input data set.
Chapter 2: PS to PTUIX 175
PT Messages
PT111E
YOU MUST SPECIFY A VCAT NAME BEFORE REQUESTING VSAM DEFINITIONS.
Reason:
You entered the "V" line command to perform VSAM definitions for an index space or
table space without specifying the VCAT name.
Action:
Enter the VCAT name and try again.
PT112I
AT LEAST ONE VOLUME MUST BE SPECIFIED FOR CLUSTER DEFINITION.
Reason:
At least one volume must be specified when defining VSAM clusters.
Action:
Specify a volume.
PT113E
DO NOT SELECT AND ENTER RC/QUERY OPTIONS AT THE SAME TIME.
Reason:
This screen does not allow you to select items and enter RC/QUERY report options.
Action:
Enter S to select the object for the current function or enter a valid RC/QUERY report
option. For a list of valid RC/QUERY report options, enter a question mark (?) in the
selection field.
PT114E
LINK TO RC/QUERY HAS FAILED.
Reason:
An internal error has occurred while trying to invoke RC/QUERY.
Action:
Check the region size.
176 Message Reference Guide (PS to ZLB)
PT Messages
PT115E
COMMAND IS INVALID.
Reason:
You have entered an invalid command.
Action:
You can enter a question mark (?) from any screen's command line to display a list of
valid commands.
PT116E
ERROR ENCOUNTERED FROM SCROLLING ROUTINE - PTASCROL.
Reason:
An internal error has been encountered by the scrolling routine.
PT117E
LIST ALREADY FILTERED; ENTER "S" OR "V" TO RETRIEVE FULL LIST
Reason:
An illogical request has been made to filter a volume or stogroup list to show only those
volumes or stogroups on which the requested space may be allocated, when such a
filtered list is already being displayed.
Action:
To display a filtered volume list when a filtered stogroup list is being displayed, enter F.
To display a filtered stogroup list when a filtered volume list is being displayed, enter G.
PT118E
INVALID OPTION OR OBJECT ENTERED.
Reason:
An invalid object or option was specified to serve as an argument to create a list of
space strategies.
Action:
Specify a valid option. Valid options are as follows: S (Space strategies only); C (Catalog
entries only, i.e., only real tablespaces and indexes); and * (Union of S and C options.
Valid object types are TS (tablespace), IX (Index), and * (both types of objects).
Chapter 2: PS to PTUIX 177
PT Messages
PT119E
INVALID EQF SPECIFICATION ENTERED. USE N, S, OR Y.
Reason:
An invalid options was used in an attempt to use the Extended Query Facility.
Action:
Specify a valid option. Valid options are as follows: N (No EQF to be used), S (Produce a
selection list to choose from using the mask value entered as the EQF name to filter the
list), and Y (Use a temporary EQF rather than a stored query).
PT120E
PROMPT CODE IS INVALID.
Reason:
The selection code you have entered is invalid.
Action:
Enter a valid selection code.
PT121E
CONNECTION NAME IN ERROR.
Action:
See the description for DB2 reason code 00F30022 in the IBM DB2 Messages and Codes
manual.
PT121E
MAXIMUM DB2 CONNECTION REACHED.
Action:
See the description for DB2 reason code 00F30055 in the IBM DB2 Messages and Codes
manual.
178 Message Reference Guide (PS to ZLB)
PT Messages
PT121E
LOAD OF MODULES DSNALI FAILED - MODULE NOT FOUND.
Reason:
The module DSNALI not found in standard search sequence for load modules.
Action:
Ensure that this module is available in the library in part of the standard search
sequence so a load module works.
PT121E
DB2 REQUEST ALREADY ACTIVE.
Action:
See the description for DB2 reason code 00F30050 in the IBM DB2 Messages and Codes
manual.
PT121E
INVALID FRB RALE/QUAL COMBINATION.
Action:
See the description for DB2 reason code 00F30015 in the IBM DB2 Messages and Codes
manual.
PT121E
PARAMETER COUNT IN ERROR.
Action:
See the description for DB2 reason code 00F30021 in the IBM DB2 Messages and Codes
manual.
PT121E
COMMIT REQUEST INVALID.
Action:
See the description for DB2 reason code 00F30046 in the IBM DB2 Messages and Codes
manual.
Chapter 2: PS to PTUIX 179
PT Messages
PT121E
RELEASE MISMATCH BETWEEN SYSTEM ID AND DB2 LOAD LIBRARY.
Reason:
The DB2 subsystem ID specified does not run under the same release of DB2 as the
version of DB2 you are currently running.
Action:
Specify a DB2 subsystem ID that runs under the same release of DB2 that you are
currently running.
PT121E
CORRELATION ID IN ERROR.
Action:
See the description for DB2 reason code 00F30038 in the IBM DB2 Messages and Codes
manual.
PT121E
FRBRALE VALUE IN ERROR.
Action:
See the description for DB2 reason code 00F30016 in the IBM DB2 Messages and Codes
manual.
PT121E
CURRENT LEVEL ERROR.
Action:
See the description for DB2 reason code 00F30053 in the IBM DB2 Messages and Codes
manual.
PT121E
DB2 IS STOPPING TERMINATION ECB MAY NOT BE POSTED.
Action:
See the description for DB2 reason code 00F30025 in the IBM DB2 Messages and Codes
manual.
180 Message Reference Guide (PS to ZLB)
PT Messages
PT121E
INDOUBT RESOLUTION PARAMETER IN ERROR.
Action:
See the description for DB2 reason code 00F30032 in the IBM DB2 Messages and Codes
manual.
PT121E
DB2 STARTUP ECB IS IN ERROR.
Action:
See the description for DB2 reason code 00F30008 in the IBM DB2 Messages and Codes
manual.
PT121E
DB2 SYSTEM NOT OPERATIONAL.
Action:
See the description for DB2 reason code 00F30002 in the IBM DB2 Messages and Codes
manual.
PT121E
COMMUNICATION BLOCK PASSED IS INVALID - PTABDBC.
Reason:
An internal error has occurred.
PT121E
GETMAIN FAILED IN MODULE - PTABDBC.
Reason:
A GETMAIN failed due to lack of memory.
Action:
Increase your region size.
Chapter 2: PS to PTUIX 181
PT Messages
PT121E
PLAN NAME IS UNAUTHORIZED.
Action:
See the description for DB2 reason code 00F30034 in the IBM DB2 Messages and Codes
manual.
PT121E
PLAN NAME SPECIFIED WAS NOT FOUND IN THIS DB2 SUBSYSTEM.
Action:
See the description for DB2 reason code 00F30040 in the IBM DB2 Messages and Codes
manual.
PT121E
DB2 SYSTEM NOT OPERATIONAL - STARTUP ECB OVERLAYS PRIOR.
Action:
See the description for DB2 reason code 00F30012 in the IBM DB2 Messages and Codes
manual.
PT121E
CALLERS PASID NOT EQUAL TO HASHID.
Action:
See the description for DB2 reason code 00F30019 in the IBM DB2 Messages and Codes
manual.
PT121E
FRBQUAL VALUE IN ERROR.
Action:
See the description for DB2 reason code 00F30017 in the IBM DB2 Messages and Codes
manual.
182 Message Reference Guide (PS to ZLB)
PT Messages
PT121E
DEAK AND WORK OUTSTANDING SYNC OR ABORT REQUIRED.
Action:
See the description for DB2 reason code 00F30043 in the IBM DB2 Messages and Codes
manual.
PT121E
TCB ALREADY CONNECTED.
Action:
See the description for DB2 reason code 00F30049 in the IBM DB2 Messages and Codes
manual.
PT121E
REQUESTED TERMINATION ECB IS A DUPLICATE.
Action:
See the description for DB2 reason code 00F30009 in the IBM DB2 Messages and Codes
manual.
PT121E
CANCELED TERMINATION ECB COULD NOT BE FOUND.
Action:
See the description for DB2 reason code 00F30010 in the IBM DB2 Messages and Codes
manual.
PT121E
ADDRESS SPACE CONNECTED WITH DIFFERENT NAME OR TYPE.
Action:
See the description for DB2 reason code 00F30024 in the IBM DB2 Messages and Codes
manual.
Chapter 2: PS to PTUIX 183
PT Messages
PT121E
ABEND ACCESSING NETWORK ID.
Action:
See the description for DB2 reason code 00F30048 in the IBM DB2 Messages and Codes
manual.
PT121E
CONNECTION LEVEL NOT SPECIFIED AT CURRENT LEVEL.
Action:
See the description for DB2 reason code 00F30054 in the IBM DB2 Messages and Codes
manual.
PT121E
USER NOT AUTHORIZED TO DB2.
Action:
See the description for DB2 reason code 00F30013 in the IBM DB2 Messages and Codes
manual.
PT121E
CONNECTION TYPE PARAMETER ERROR.
Action:
See the description for DB2 reason code 00F30007 in the IBM DB2 Messages and Codes
manual.
PT121E
RESTRICTED ACCESS MODE.
Action:
See the description for DB2 reason code 00F30056 in the IBM DB2 Messages and Codes
manual.
184 Message Reference Guide (PS to ZLB)
PT Messages
PT121E
General Notes.
Reason:
PT121E is a trap for DB2 abend reason codes pertaining to subsystems. These messages
indicate a problem with DB2, not a problem with the product. The text displayed with
message PT121E varies, depending on the particular reason code returned by DB2. The
messages are listed alphabetically. For each message, the number of the DB2 reason
code is also listed.
Action:
See the reason code descriptions in the IBM DB2 Messages and Codes manual for more
information.
PT121E
PLAN NAME IS IN ERROR.
Action:
See the description for DB2 reason code 00F30033 in the IBM DB2 Messages and Codes
manual.
PT121E
WEIGHTING FACTOR IS INVALID.
Action:
See the description for DB2 reason code 00F30027 in the IBM DB2 Messages and Codes
manual.
PT121E
DB2 SYSTEM NOT OPERATIONAL - STARTUP ECB NOT ACCEPTED.
Action:
See the description for DB2 reason code 00F30011 in the IBM DB2 Messages and Codes
manual.
Chapter 2: PS to PTUIX 185
PT Messages
PT121E
COMMIT OPTION PARAMETER ERROR.
Action:
See the description for DB2 reason code 00F30020 in the IBM DB2 Messages and Codes
manual.
PT121E
TCB NOT CONNECTED TO DB2.
Action:
See the description for DB2 reason code 00F30018 in the IBM DB2 Messages and Codes
manual.
PT121E
TERMINATION ECB PARM ERROR.
Action:
See the description for DB2 reason code 00F30005 in the IBM DB2 Messages and Codes
manual.
PT121E
DB2 SYSTEM ID NAME IS INVALID.
Action:
See the description for DB2 reason code 00F30006 in the IBM DB2 Messages and Codes
manual.
PT121E
FRB VALUE INVALID.
Action:
See the description for DB2 reason code 00F30026 in the IBM DB2 Messages and Codes
manual.
186 Message Reference Guide (PS to ZLB)
PT Messages
PT121E
GENERAL DB2 CONNECTION ERROR.
Action:
See the description for DB2 reason code 00F30000 in the IBM DB2 Messages and Codes
manual.
PT122E
PROCESS REQUEST CANCELED - NO COMMAND TO PROCESS.
Action:
The current request has been canceled by the user and there is no command to process.
This message is informational only and does not indicate a problem.
PT123E
VALID COMMANDS ARE "END" OR "=X".
Reason:
You have entered an invalid command.
Action:
Specify a valid command. Valid commands are END and =X. You can display a list of valid
commands from any screen by entering a question mark (?).
PT124E
IFI FAILED - RETURN CODE = code REASON CODE = code.
Reason:
DB2 IFI failed. Use the displayed Return and Reason Codes from DSNWLI (IFI Interface)
to diagnose the problem.
Action:
See the IBM DB2 Messages and Codes manual for code information.
PT125W
DOWN REQUEST IGNORED ALREADY AT BOTTOM.
Reason:
You have requested to scroll DOWN (PF8) when the bottom of the scrollable list is
already displayed.
Chapter 2: PS to PTUIX 187
PT Messages
PT126W
TOP REQUEST IGNORED ALREADY AT TOP.
Reason:
You have requested to scroll UP (PF7) when the top of the scrollable list is already
displayed.
PT127W
VALID SELECTION CODES ARE "S", "E", OR "D".
Reason:
You have entered an invalid selection code.
Action:
Specify a valid selection code. Valid codes are as follows: S, E, and D.
PT128W
NO LOCATIONS WERE FOUND IN THE LOCATION TABLE.
Reason:
A location was specified and no locations were found for DB2 DDF.
PT129E
VALID SELECT CODE IS "S".
Reason:
The only valid selection code is "S" (select). You entered another selection code.
Action:
Change your code to "S" and try again.
188 Message Reference Guide (PS to ZLB)
PT Messages
PT140E
UNABLE TO OPEN PTILIB DDNAME.
Reason:
The PTILIB DDNAME could not be opened. This data set is used by the CA products to
access load modules for internal processing. Without this data set, processing cannot
continue and has been terminated.
Action:
Check to see why PTILIB is not allocated. It should be allocated in the CLIST that
allocates the CA product libraries.
PT141E
RC=code, RCODE = codes.
Reason:
An error occurred while trying to establish a thread to the specified DB2 subsystem via
the DB2 Call Attach Facility (CAF). PTEDRTNC represents the return code issued by DB2
and PREDRSNC is the last four bytes of the CAF reason code.
PT142E
INVALID COMMAND ENTERED. PRESS HELP FOR MORE INFORMATION.
Reason:
The command you have entered is invalid.
Action:
You can display a list of valid commands from any screen by entering a question mark
(?).
PT143E
LENGTH SPECIFIED MUST BE NUMERIC. PRESS HELP FOR MORE INFORMATION.
Reason:
The DSNCHAR command is used to change the displayed length of the Dataset-Name
column on the Execution Display panel.
Action:
Using the DSNCHAR command, you can vary the viewable length of the data set name
anywhere from 3 to 53 characters. If you want to entirely omit the data set name, enter
a length of 0.
Chapter 2: PS to PTUIX 189
PT Messages
PT144E
VALID BPID COLUMN WIDTHS ARE 0, OR ANY NUMBER FROM 4 TO 53.
Reason:
The BPIDCHAR command is used to change the displayed width of the BPID column on
the Execution Display panel.
Action:
Using the BPIDCHAR command, you may vary the viewable length of the BPID anywhere
from 4 to 53 characters. If you wish to entirely omit the BPID column from the display,
enter a width of 0. If you have frozen any columns, there must be room left on the
screen for the width that you have requested. If you have frozen columns and wish to
enlarge the BPID column, you may have to Unfreeze a column or Melt all columns to
make room for the expansion.
PT145E
INVALID SELECTION CODE. ENTER D, DD, E, B OR S. PF1 FOR MORE INFO.
Reason:
The selection code you have entered is invalid.
Action:
Specify a valid selection code. Valid selection codes are as follows: D, DD, E, B, and S.
PT146E
INCOMPLETE BLOCK DELETE COMMAND ENTERED. PRESS HELP FOR MORE
INFORMATION.
Reason:
The block DELETE command must have a pair of "DD'S -- one on the first entry you want
deleted, and one on the last entry you want deleted. You entered only one "DD".
PT147E
number ROW(S) WERE DELETED FROM THE LOG (XI, SC ROWS
BYPASSED).pteddxim=xi,sc.
Reason:
This message specifies how many rows were deleted from the log. If displayed, the "XI,
SC rows bypassed" portion of this message indicates that you attempted to delete 1 or
more sync or analysis type records that were generated by a currently executing job.
You cannot delete such sync or analysis type records.
190 Message Reference Guide (PS to ZLB)
PT Messages
PT148E
INVALID COMMAND ENTERED. PRESS HELP FOR MORE INFO.
Reason:
You have entered an invalid command.
Action:
You can enter a question mark (?) from any screen's command line to display a list of
valid commands.
PT149E
THE TIME INTERVAL MUST BE NUMERIC. PRESS HELP FOR MORE INFO.
Reason:
The CYCLE command will cause the Execution Display to periodically, automatically
refresh the displayed data. You can control the frequency with which the log data is
refreshed by specifying a time interval with the CYCLE command. The time interval
specified represents the number of seconds paused between each refresh of the data.
The time interval can be any number between 5 and 999.
PT150E
THE TIME INTERVAL MUST NOT BE LESS THAN 5. PRESS HELP FOR MORE INFO.
Reason:
The CYCLE command will cause the Execution Display to periodically, automatically
refresh the displayed data. You can control the frequency with which the log data is
refreshed by specifying a time interval with the CYCLE command. The time interval
specified represents the number of seconds paused between each refresh of the data.
The time interval can be any number between 5 and 999.
PT151E
SAVED DISPLAY FORMAT NOT FOUND. PRESS HELP FOR MORE INFORMATION.
Reason:
Your ISPF profile does not contain a "display format." A display format is saved in the
data set allocated to DDNAME ISPPROF (in member name RCPROF) when the SAVEF
command is issued. Your profile will not contain a display format if the SAVEF command
has never been issued, or if it was issued with a different data set allocated to the
ISPPROF DDNAME.
Chapter 2: PS to PTUIX 191
PT Messages
PT152
*** interval SECOND CYCLE IN PROCESS, PRESS PA1 TO EXIT ****.
Reason:
You entered the Execution Display CYCLE command. The screen will be refreshed every
interval number of seconds.
PT153
DISPLAY FORMAT HAS BEEN SAVED.
Reason:
Your display format has been successfully saved. A display format is saved in the data
set allocated to DDNAME ISPPROF (in member name RCPROF) when the SAVEF
command is issued.
PT154E
THIS COLUMN NAME HAS ALREADY BEEN SPECIFIED. PRESS HELP FOR MORE INFO.
Reason:
You have entered an invalid SORT command. Your sort command is in error because it
contains multiple references to a single column. Each individual column name may only
be specified once in a sort command. The cursor has been positioned on the column
name that is in error.
PT155E
UNABLE TO LOCATE PTILIB DCB. ERROR ENCOUNTERED IN PTISCROL.
Reason:
The PTILIB allocation could not be found.
Action:
Check to see if PTILIB is allocated correctly.
192 Message Reference Guide (PS to ZLB)
PT Messages
PT156E
LOAD FAILURE. ERROR DETECTED BY MODULE PTAEDMAN.
Reason:
The products were unable to load a module.
Action:
Check the region size.
PT157E
INVALID COMMAND ENTERED. PRESS HELP FOR MORE INFORMATION.
Reason:
You have entered an invalid command.
Action:
You can enter a question mark (?) from any screen's command line to display a list of
valid commands.
PT160E
VALID LINE COMMANDS ARE "S" SELECT, "D" DELETE, "U" UNDELETE.
Reason:
You have entered an invalid line command.
Action:
Specify a valid line command. Valid line commands are as follows: S, D, and U.
PT161E
SELF REFERENCING RELATION, INSERTION OF PARENT TABLE COLS NOT ALLOWED.
Reason:
You tried to use the "I" command in the Column Information section of the Foreign Key
Detail screen to insert a parent table column into the foreign key and into the child
table. Because the child and parent tables are the same table, inserting a column into
the table does not make sense.
Action:
Use the "I" (Insert) command in the Foreign Key part of the screen to insert the column
into the foreign key only (and not the table).
Chapter 2: PS to PTUIX 193
PT Messages
PT162E
SOME PRIMARY KEY COLUMN DEFINITIONS HAVE BEEN SET TO "NOT NULL".
Reason:
You tried to change a primary key column definition to NULL=Y. Primary key columns
must be defined as NOT NULL.
PT163E
INVALID TYPE CONVERSIONS RESET; PRIMARY KEY COLUMNS SET TO NOT NULL.
Reason:
You tried to change a primary key column's type to an invalid value and its NULL
definition to NULL=Y. Primary key columns must be defined as NOT NULL. The type and
NULL definitions have been reset.
PT164I
CURRENT SQLID HAS BEEN SET TO authid. ENTER HELP FOR MORE INFORMATION.
Reason:
Your SET CURRENT SQLID request has been satisfied, and all CA DB2 connections will be
made with the SQLID until you request that a different one be used. This SQLID has been
saved in the ISPF PROFILE variable pool, which will allow us to maintain this value
between sessions for you.
PT165I
ALL OF THE COLUMNS IN THIS TABLE ARE CURRENTLY IN THE FOREIGN KEY.
Reason:
You requested to insert a column into the foreign key. There are no columns to insert;
all columns in the table are already defined as part of the foreign key.
PT166E
INVALID PTMALTER LIST DETECTED BY MODULE PTATALT.
Reason:
An internal error has occurred in the PTMALTER structure.
194 Message Reference Guide (PS to ZLB)
PT Messages
PT167E
INVALID COMMAND, ENTER A "?" TO VIEW A LIST OF VALID COMMANDS.
Reason:
You have entered an invalid command.
Action:
You can enter a question mark (?) from any screen's command line to display a list of
valid commands.
PT169I
ENTER ONE OF THE VALID EXECUTION MODES. PRESS HELP FOR MORE INFO.
Reason:
You must enter a valid execution mode.
Action:
Valid execution modes are O and B.
PT170E
YOU ALREADY HAVE AN ACTIVE RC/UPDATE SESSION. PRESS HELP FOR INFO.
Reason:
You attempted to jump to a product you are already using. You must exit the product
you are currently in to get back to the product you want.
PT171E
LINK TO PROCESS PRIMARY COMMAND HAS FAILED. PRESS HELP FOR MORE INFO.
Reason:
The product was unable to successfully LINK to its primary command processing
module. This can be caused by not having the product library DDNAME allocated
properly. The DDNAME that should be allocated is PTILIB and that library contains the
service modules.
Chapter 2: PS to PTUIX 195
PT Messages
PT172E
YOU ALREADY HAVE AN ACTIVE RC/QUERY SESSION. PRESS HELP FOR INFO.
Reason:
You attempted to jump to a product you are already using. You must exit the product
you are currently in to get back to the product you want.
PT173E
#LINK HAS FAILED. PRESS HELP FOR MORE INFO.
Reason:
A LINK macro within the current product has failed. This could be due to improper
allocation of the product library.
Action:
Check to be sure that the product library is allocated to the DDNAME PTILIB.
PT174E
ONLY ONE COMMAND MAY BE SELECTED. PRESS HELP FOR MORE INFO.
Reason:
You have entered "S" next to more than one command on the Global Commands
screen.
Action:
The "S" option executes the command, so you can enter "S" for only one command at a
time. Select only one command to execute and try again.
PT175E
"S" AND "?" COMMANDS CANNOT BE INTERMIXED. PRESS HELP FOR MORE INFO.
Action:
You can enter one "S" to execute a single command or enter one or more question
marks (?) to get help on multiple commands. You cannot enter "S" and "?" at the same
time. Correct your selections and try again.
196 Message Reference Guide (PS to ZLB)
PT Messages
PT176E
YOU HAVE ENTERED AN INVALID LINE COMMAND. PRESS HELP FOR MORE INFO.
Reason:
You have entered a line command other than "S" or "?", the only valid line commands.
Action:
"S" executes the command. "?" displays help on the command. Enter a valid line
command and start again.
PT177I
HELP IS NOT AVAILABLE FOR THE global COMMAND.
Reason:
You entered a question mark to get help on a global command and help is not available.
The name of the global command displays in the message.
PT178E
YOU ALREADY HAVE AN ACTIVE DB2C SESSION. PRESS HELP FOR INFO.
Reason:
You attempted to jump to a product you are already using.
Action:
You must exit the product you are currently in to get back to the product you want.
PT179E
YOU ALREADY HAVE AN ACTIVE PDA/UTIL SESSION. PRESS HELP FOR INFO.
Reason:
You attempted to jump to a product you are already using.
Action:
You must exit the product you are currently in to get back to the product you want.
Chapter 2: PS to PTUIX 197
PT Messages
PT180E
YOU ALREADY HAVE AN ACTIVE RC/SQL SESSION. PRESS HELP FOR INFO.
Reason:
You attempted to jump to a product you are already using.
Action:
You must exit the product you are currently in to get back to the product you want.
PT181E
THE SPECIFIED OPERANDS ARE INVALID FOR THE COMMANDS YOU HAVE ENTERED.
Reason:
You have specified a valid command, but have specified invalid operands.
Action:
You can enter a question mark (?) to get a list of valid commands. Entering another
question mark next to the command in question will give you syntax information.
PT182E
YOU HAVE ENTERED TOO MANY OPERANDS FOR THIS COMMAND.
Reason:
You have specified a valid command, but have specified too many operands.
Action:
You can enter a question mark (?) to get a list of valid commands. Entering another
question mark next to the command in question will give you syntax information.
PT183E
YOU ALREADY HAVE AN ACTIVE RC/MIGRATOR SESSION. PRESS HELP FOR INFO.
Reason:
You attempted to jump to a product you are already using.
Action:
You must exit the product you are currently in to get back to the product you want.
198 Message Reference Guide (PS to ZLB)
PT Messages
PT184E
YOU ALREADY HAVE AN ACTIVE RC/SECURE SESSION. PRESS HELP FOR INFO.
Reason:
You attempted to jump to a product you are already using.
Action:
You must exit the product you are currently in to get back to the product you want.
PT185E
YOU MUST OWN PDA OR RC/QUERY TO USE PDA JUMPING COMMANDS.
Reason:
Interproduct Interface requires you to have a license for the product you want to access.
You attempted to access RC/QUERY or PDA (or one of their functions) without having
the proper license.
PT186E
YOU MUST OWN PDA, PPA, OR RC/Q TO USE THE DB2 COMMAND PROCESSOR.
Reason:
Interproduct Interface requires you to have a license for the product you want to access.
You attempted to access the DB2 Command Processor without having the proper
license. You must have a license for CA Database Analyzer for DB2, CA Plan Analyzer, or
CA RC/Query.
PT187E
THE DB2 COMMAND PROCESSOR MAY ONLY BE USED IN DB2 V2.1 OR HIGHER.
Reason:
You tried to use the DB2 Command Processor while running a version of DB2 that is
earlier than V2.1. To use the DB2 Command Processor, you must be running DB2 V2.1 or
higher.
Chapter 2: PS to PTUIX 199
PT Messages
PT188E
YOU ALREADY HAVE AN ACTIVE COMPRESS SESSION. PRESS HELP FOR INFO.
Reason:
You attempted to jump to a product you are already using.
Action:
You must exit the product you are currently in to get back to the product you want.
PT189E
THE LOAD OF PTLDBSYS FAILED. PRESS HELP FOR INFO.
Reason:
The load for module PTLDBSYS failed. This module is used to retrieve the plan name that
should be used. As part of the installation procedure, this load module should have
been created.
PT190E
UNABLE TO LOAD PRODUCTS PARAMETER BLOCK. PF1 FOR HELP.
Reason:
An attempt to LOAD the products parameter block has failed. This parameter block was
being loaded in order to obtain any user defined DB2 Object Definition Defaults. The
failure of this LOAD can be caused by not having the product library DDNAME allocated
properly. The DDNAME that should be allocated is PTILIB and that library contains the
subroutine services.
PT191E
RC=code, RCODE=codes, messages.
Reason:
An attempt to establish a thread to the DB2 subsystem via the Call Attach Facility (CAF)
has failed. The information in the message is the information that DB2 has returned to
the CA CAF component.
200 Message Reference Guide (PS to ZLB)
PT Messages
PT192I
DB2 OBJECT CREATION DEFAULTS DO NOT EXIST FOR USERID user.
Reason:
DB2 object creation defaults do not exist for the specified user ID and no masked ID
matches.
Action:
You can retrieve defaults for another ID (or mask) and save them for the specified ID or
you can create new defaults for the specified user ID.
PT193E
YOU MAY NOT SPECIFY BOTH VCAT AND STOGROUP INFORMATION. PF1 FOR HELP.
Reason:
You have attempted to specify both VCAT and STOGROUP information.
Action:
You may specify one or the other, but not both. If you want to define and manage the
VSAM data sets used by DB2 yourself, specify a default VCAT NAME. If you prefer to let
DB2 define and manage the VSAM data sets, specify stogroup information.
PT194E
PRIMARY QUANTITY MUST BE NUMERIC. PF1 FOR HELP.
Reason:
You have specified an invalid primary quantity value. The primary quantity specified
must be a number less than 4194394. The number specified is the number of kilobytes
DB2 will use as the primary space allocation for the DB2-defined VSAM data sets.
PT195E
SECONDARY QUANTITY MUST BE NUMERIC. PF1 FOR HELP.
Reason:
You have specified an invalid secondary quantity value. The secondary quantity
specified must be a number less than 131068. The number specified is the number of
kilobytes DB2 will use as the secondary space allocation for the DB2-defined VSAM data
sets.
Chapter 2: PS to PTUIX 201
PT Messages
PT196E
FREE PAGE MUST BE A NUMBER BETWEEN 0 AND 255. PF1 FOR HELP.
Reason:
You have specified an invalid FREEPAGE value. The value specified must be a number in
the range of 0 - 255. This value specifies how often DB2 is to leave a page of freespace
when the tablespace or index is loaded or reorganized.
PT197E
PCTFREE MUST BE NUMERIC. PF1 FOR HELP.
Reason:
You have specified an invalid PCTFREE value. The value specified must be a number in
the range of 0 - 99. This value specifies what percentage of each page is to be left as free
space when the tablespace or index is loaded or reorganized.
PT198E
INVALID BUFFERPOOL. PF1 FOR HELP.
Reason:
You have specified an invalid buffer pool. For tablespaces, the bufferpool specified must
be one of the following: BP0, BP1, BP2, or BP32K. For indexes, the bufferpool specified
must be one of the following: BP0, BP1, or BP2.
PT199E
CLOSE MUST "YES" OR "NO". PF1 FOR HELP.
Reason:
You have specified an invalid CLOSE value. The CLOSE value must be YES or NO. The
value specified here indicates to DB2 whether to close the data setS which support the
tablespace or index when the object is not being used.
PT200E
DYNALLOC FAILURE, RTN = code, INFO = info, ERROR = error.
Reason:
Dynamic Allocation has failed for the data set name that you specified for the current
function. The message provides you with the DYNALLOC return code, INFO code, and
ERROR code. This allows you to locate the problem in the appropriate IBM macro
manual.
202 Message Reference Guide (PS to ZLB)
PT Messages
PT201E
THE SPECIFIED DATASET DOES NOT EXIST. PRESS HELP FOR INFO.
Reason:
Dynamic Allocation has failed for the data set name that you specified for the current
function. The DYNALLOC function has returned an ERROR code indicating that the
specified data set does not exist. The message provides you with the DYNALLOC return
code, INFO code, and ERROR code to allow you to locate the problem in the appropriate
IBM macro manual.
PT202E
GETMAIN FAILURE, DUE TO INSUFFICIENT VIRTUAL STORAGE.
Reason:
A Getmain was attempted and failed because there was not enough available storage or
memory.
Action:
Increase the region size.
PT203E
PARTITIONED TABLESPACE CANNOT BE SEGMENTED.
Reason:
This message appears when you try to segment a partitioned tablespace.
PT204E
NOT ENOUGH SPACE FOR THIS BPID WIDTH. PRESS HELP FOR MORE INFO.
Reason:
The BPIDCHAR command is used to change the displayed width of the BPID column on
the Execution Display panel.
Action:
Using the BPIDCHAR command, you may vary the viewable length of the BPID anywhere
from 4 to 53 characters. If you wish to entirely omit the BPID column from the display,
enter a width of 0. If you have frozen any columns, there must be room left on the
screen for the width that you have requested. If you have frozen columns and wish to
enlarge the BPID column, you may have to Unfreeze a column or Melt all columns to
make room for the expansion.
Chapter 2: PS to PTUIX 203
PT Messages
PT205I
ONLY THE FIRST SIX VOLUMES WILL BE USED FOR THE VSAM DEFINE.
Reason:
You have selected more than six volumes. Only the first six shown in the list will be used.
The volumes after the sixth one will be ignored.
PT206I
VOLUMES HAVE ALREADY BEEN SELECTED. ENTER SHRINK TO VIEW.
Reason:
You have requested the Space Locator and have already specified volumes to use for the
VSAM Defines.
Action:
Enter SHRINK to view the selected volumes.
PT207I
VSAM DELETE/DEFINES WILL BE GENERATED USING THE SELECTED VOLUMES.
Reason:
This message is not used.
PT208I
ENTER A VCAT NAME OR PRESS ENTER FOR A SELECTION LIST.
Reason:
The Space Calculator/Locator was originally entered with a STOGROUP. A volume
selection was made, which forces the user to select a VCAT.
PT210I
YOU MAY SELECT UP TO number VOLUMES. PF1 FOR HELP.
Reason:
There is currently enough room in the set of defaults you are editing to add additional
volumes to the default stogroup volume list.
204 Message Reference Guide (PS to ZLB)
PT Messages
PT211E
PARTITIONED MUST BE "YES" OR "NO". PF1 FOR HELP.
Reason:
You have specified an invalid PARTITIONED value. Valid values for the PARTITIONED
prompt are YES and NO. Any other value is invalid. The value specifies whether or not
the tablespaces or indexes will be defined as partitioned.
PT212E
SEGSIZE MUST BE A MULTIPLE OF 4 LESS THAN OR EQUAL TO 64. PF1 FOR HELP.
Reason:
You have specified an invalid SEGSIZE. The SEGSIZE value must be a number less than or
equal to 64 that is a multiple of 4, for example, 0, 4, 8, 12, 16, . . .64.
PT213E
INVALID LOCKSIZE SPECIFIED. PF1 FOR HELP.
Reason:
You have specified an invalid LOCKSIZE parameter.
Action:
Specify a valid parameter value. Valid values are ANY, PAGE, TABLESPACE, and TABLE.
PT214E
INVALID AUDIT VALUE SPECIFIED. PF1 FOR HELP.
Reason:
You have specified an invalid AUDIT value. You must have DB2 V2.1 to better to use
table auditing.
Action:
Specify a valide value. Valid values are NONE, ALL, and CHANGES.
Chapter 2: PS to PTUIX 205
PT Messages
PT215E
INVALID COLUMN NULL INDICATOR SPECIFIED. PF1 FOR HELP.
Reason:
This indicates that you have specified an invalid default COLUMN NULL INDICATOR.
Action:
Specify a valid value. Valid values are Y and N.
PT216E
INVALID COLUMN DATA TYPE VALID SPECIFIED. PF1 FOR HELP.
Reason:
You have specified an invalid data type. Valid data types are CHAR, VARCHAR, LONG
VARCHAR, INTEGER, SMALLINT, REAL, FLOAT, GRAPHIC, VARGRAPHIC, LONG
VARGRAPHIC, DATE, TIME, TIMESTAMP, and DECIMAL.
PT217E
INVALID UNIQUE VALUE SPECIFIED. PF1 FOR HELP.
Reason:
You have specified an invalid UNIQUE value.
Action:
Specify a valid value. Valid values are YES and NO.
PT218E
INVALID CLUSTER VALUE SPECIFIED. PF1 FOR HELP.
Reason:
You have specified an invalid CLUSTER value.
Action:
Specify a valid value. Valid values are YES and NO.
206 Message Reference Guide (PS to ZLB)
PT Messages
PT219E
INVALID SUBPAGE VALUE SPECIFIED. PF1, FOR HELP.
Reason:
You have specified an invalid default SUBPAGE value.
Action:
Specify a valid value. Valid values are as follows: 0, 1, 2, 4, 8, 16.
PT220E
INVALID VIEW CHECK OPTION SPECIFIED. PF1 FOR HELP.
Reason:
You have specified an invalid CHECK OPTION.
Action:
Specify a valid value. Valid values are Y and N.
PT221I
Defaults not available for USERID &USERID.; shown here are IBM's defaults.
Reason:
An object definition default is not available for your user ID because of one of the
following conditions:
■
No definition is defined (that is, a search for a definition saved under your TSOID, or
saved under a MASKID that matches your TSOID, returned no results).
■
The definition is not accessible, due to a connection, plan, or SQL error.
A temporary definition is used, instead, that is populated with a set of predetermined
default settings consistent with the DB2 defaults used by IBM. These predetermined
defaults are used when creating new objects (and for other functions, such as inserting
columns for a table and inserting partitions for a tablespace or index).
Note: The APPLY DEFAULTS command is not allowed when a temporary definition is in
use.
Action:
No action is required.
Chapter 2: PS to PTUIX 207
PT Messages
PT222I
DEFAULTS FOR USERID authid TAKEN FROM groupid MASKID.
Reason:
There are currently no DB2 object definition defaults defined for your user ID. The
defaults displayed on the previous panel were taken from a masked ID (Group ID) that
matches the first n characters of your TSO ID.
PT223E
THE SPECIFIED USERID IS NOT A VALID TSOID OR MASKID. PF1 FOR HELP.
Reason:
You have attempted to save a set of defaults for an ID that is not a valid TSO ID or
masked ID. Valid TSO IDs must begin with an alphabetic or national character (i.e., A
through Z, or @, #, $). The remaining characters must be alphanumeric (i.e., A through
Z, 0 through 9). A valid masked ID follows the same rules except that it can end with an
asterisk (*). The single character * is also a valid mask.
PT224I
USER DEFAULTS HAVE BEEN SAVED.
Reason:
The user defaults displayed on the Object Definition Defaults screen have been saved
because you entered the "S" (Save) action code. This message is for information only.
PT225I
YOU MAY NOT SELECT MORE THAN ONE ITEM. PF1 FOR HELP.
Reason:
You have attempted to select multiple sets of defaults for retrieval.
Action:
You can select only one. Correct your error by removing the "S" selection character from
all but one of the listed defaults.
208 Message Reference Guide (PS to ZLB)
PT Messages
PT226E
ENTER AN "S" TO SELECT AN ITEM. PF1 FOR HELP.
Reason:
You have entered an invalid selection code.
Action:
“S” is the only valid selection code.
PT227I
REQUESTED ITEM(S) HAVE BEEN DELETED.
Reason:
An attempt to delete defaults saved under the specified user ID was successful.
PT228E
DFLTS DO NOT EXIST FOR user_id DELETE REQUEST FAILED. PF1 FOR HELP.
Reason:
An attempt to delete defaults saved under the specified user ID has failed due to a
not-found condition.
PT229E
UNABLE TO LOAD REQUESTED SERVICE MODULE. PF1 FOR HELP.
Reason:
An attempt to LOAD subservice module has failed. This can be caused by not having the
product library DDNAME allocated properly. The DDNAME that should be allocated is
PTILIB and that library contains the subroutine services.
PT234E
You have entered an invalid value for the Batch Processor RESTART option.
Reason:
Valid options are N, Y, and O.
Chapter 2: PS to PTUIX 209
PT Messages
PT235E
YOU ALREADY HAVE AN ACTIVE BP SESSION. PRESS HELP FOR MORE INFO.
Reason:
You attempted to jump to a product you are already using.
Action:
You must exit the product you are currently in to get back to the product you want.
PT236E
MEMBER SPECIFIED IN BOTH DATASET AND MEMBER FIELDS.
Reason:
You can specify a PDA member name in the Data set Name field or the Member field,
but not both.
Action:
Correct this problem by specifying a member name in only one of these fields.
PT237I
YOU ARE EDITING YOUR BATCH PROCESSOR MODEL JCL MEMBER.
Reason:
You have requested to edit your model JCL member and the member has been
displayed. This message is for your information only and does not indicate an error.
PT238E
INVALID SYMBOLIC: symbolic FOUND IN MODEL JCL MEMBER.
Reason:
The symbolic variable whose name displays in the message is not valid.
Action:
See the product documentation for information on symbolic variable syntax. Correct the
symbolic variable in the model member and try again.
210 Message Reference Guide (PS to ZLB)
PT Messages
PT239E
DYNAMIC ALLOCATION FAILURE FOR MODEL JCL DATASET.
Reason:
Dynamic Allocation has failed for the model JCL data set. The message provides you with
the DYNALLOC return code, INFO code, and ERROR code. This allows you to locate the
problem in the appropriate IBM macro manual.
PT240E
INVALID LRECL FOR DATASET - MUST BE 80.
Reason:
The data set you have specified for your data set has a record length other than 80.
Model JCL data sets must have an LRECL of 80.
PT241E
OPEN FAILURE FOR DATASET.
Reason:
Your data set could not be opened.
PT242I
ENTER VALUES FOR MODEL JCL SYMBOLICS. "H" COMMAND TURNS HEADER ON/OFF.
Reason:
This message is for information only and does not indicate a problem. The Symbolic
Variable Replacement screen enables you to replace symbolic variables with the actual
values that will be used in the JCL. Enter values for all symbolics that are not
automatically replaced. You can use the HEADER command to toggle the top portion of
the screen on and off. This enlarges display area for the symbolic variables and model
JCL.
PT243E
VALID LINE COMMANDS ARE "D" - DELETE AND "C" - CLEAR. HELP FOR INFO.
Reason:
You have entered an invalid line command on the Model JCL screen.
Action:
Specify a valid command. Valid commands are D and C.
Chapter 2: PS to PTUIX 211
PT Messages
PT244I
ENTER BATCH PROCESSOR INPUT DATA SET NAME.
Reason:
This message is for information only and does not indicate a problem.
Action:
You must enter the name of the data set you want to process through the Batch
Processor in the Input Data Set Name field. For a PDS you can enter selection criteria in
the Member field to display a list of members.
PT245I
ENTER MODEL JCL DATA SET AND MEMBER NAMES.
Reason:
This message is for information only and does not indicate a problem.
Action:
You must enter the name of the PDS that contains your model JCL member. You can
enter selection criteria in the Member field to display a list of members.
PT246I
SELECT A MEMBER TO USE FOR YOUR BATCH PROCESSOR INPUT DATASET.
Reason:
A member selection list displays so that you can choose a member for your Batch
Processor Input Data set.
Action:
Enter "S" next to the member you want to use or enter CANCEL to return to the Batch
Processor screen without selecting a member.
212 Message Reference Guide (PS to ZLB)
PT Messages
PT247I
SELECT A MEMBER TO USE FOR YOUR MODEL JCL DATASET.
Reason:
A member selection list displays so that you can choose a member for your Batch
Processor Model JCL.
Action:
Enter "S" next to the member you want to use or enter CANCEL to return to the Batch
Processor screen without selecting a member.
PT248I
YOU ARE EDITING YOUR MODEL JCL MEMBER.
Reason:
You have requested to edit your model JCL member and the member has been
displayed. This message is for your information only and does not indicate an error.
PT249I
ONE OR MORE SYMBOLIC REPLACEMENT VALUES HAVE BEEN LEFT BLANK.
Reason:
You have left the Symbolic Variable Replacement screen without specifying values for
one or more symbolic variables. This message displays because blanks will be
substituted for the variable. This could cause errors when the job is submitted for
execution.
PT250E
UNABLE TO LOAD PRODUCTS PARAMETER BLOCK. PF1 FOR HELP.
Reason:
An attempt LOAD the products parameter block has failed. This parameter block was
being loaded in order to obtain the product's DB2 plan name. The failure of this LOAD
can be caused by not having the product library DDNAME allocated properly. The
DDNAME that should be allocated is PTILIB and that library contains the subroutine
services.
Chapter 2: PS to PTUIX 213
PT Messages
PT252E
MODEL JCL DATASET MUST BE PARTITIONED.
Reason:
A sequential data set has been specified instead of a partitioned data set. Model JCL
must be partitioned.
PT253I
NO SYMBOLIC VARIABLES FOUND IN MODEL JCL.
Reason:
Informs you that the Symbolic Variable Replacement screen will not display because
there are no symbolic variables in the model JCL.
PT254E
MEMBER OR SEQUENTIAL DATASET IN USE. ENTER HELP FOR MORE INFO.
Reason:
The requested member or sequential data set is currently unavailable. You or another
user may be editing the member or sequential data set.
Action:
Try requesting the member at another time.
PT257E
INVALID RECFM FOR DATASET - MUST BE FIXED.
Reason:
The data set you have specified has a variable record format. Your data set must have a
fixed record format.
PT258E
INVALID RECFM FOR JCL OUTPUT DATASET - MUST BE FIXED.
Reason:
The data set you have specified for the JCL output has a variable record format. JCL
output data sets must have a fixed record format.
214 Message Reference Guide (PS to ZLB)
PT Messages
PT259E
INVALID LRECL FOR JCL OUTPUT DATASET - MUST BE 80.
Reason:
The data set you have specified for the JCL output has an invalid record length. JCL
output data sets must have a record length of 80.
PT260E
YOU ALREADY HAVE AN ACTIVE PIPELINE SESSION. PRESS HELP FOR INFO.
Reason:
You attempted to jump to a product you are already using.
Action:
You must exit the product you are currently in to get back to the product you want.
PT261I
YOU ARE EDITING YOUR MODEL JCL MEMBER.
Reason:
Informs you that you are editing your model JCL member. This message is for
information only and does not indicate a problem.
PT262E
JCL OUTPUT FILE ALLOCATION FAILURE.
Reason:
Due to environmental conditions, the JCL output file allocation has failed.
Action:
Contact your MVS Systems Programmer.
Chapter 2: PS to PTUIX 215
PT Messages
PT263E
JCL OUTPUT FILE OPEN FAILURE.
Reason:
Due to environmental conditions, the JCL output file open has failed.
Action:
Contact your MVS Systems Programmer.
PT264I
JCL HAS BEEN SUBMITTED TO JES.
Reason:
The JCL has been submitted to JES as you requested. This message is for information
only and does not indicate a problem.
PT265I
JCL HAS BEEN WRITTEN TO THE REQUESTED DATASET.
Reason:
The JCL has been written to the data set that you specified. This message is for
information only and does not indicate a problem.
PT266I
SELECT A MEMBER TO CONTAIN YOUR JCL.
Action:
Select a member from the Member Selection List to contain your JCL.
PT267E
INVALID SYMBOLIC: symbolic FOUND IN MODEL JCL MEMBER.
Reason:
The symbolic listed in the message is invalid.
216 Message Reference Guide (PS to ZLB)
PT Messages
PT268E
INVALID OPTION ENTERED. ENTER ONE OF THE OPTIONS LISTED ON THE PANEL.
Reason:
You have entered an invalid option.
Action:
Enter one of the options listed on the panel.
PT269E
THE ATTACHED VERSION OF DB2 DOES NOT SUPPORT REMOTE LOCATIONS.
Reason:
The attached version of DB2 is earlier than V2.2 and does not support remote locations.
You cannot specify a location other than LOCAL.
PT270E
DB2 SUBSYSTEM ID NOT FOUND IN PARMLIB. PRESS HELP FOR MORE INFO.
Reason:
The specified DB2 subsystem ID could not be located in the SETUP member of
high-level.CDBAPARM. This member is created at install time. It should contain an entry
for each DB2 subsystem that you intend to access via CA products.
Action:
Check that the DB2 subsystem ID has not been misspelled. If the subsystem ID is correct,
contact your System Administrator and request that the subsystem to be added to the
member.
Chapter 2: PS to PTUIX 217
PT Messages
PT271E
UNABLE TO ALLOCATE NECESSARY DB2 SOFTWARE LIBRARIES. PF1 FOR HELP.
Reason:
An attempt to allocate DB2 software libraries has failed. The products ALLOCATE and
OPEN the DB2 libraries for use as a TASKLIB. This allows the products to connect to
different versions of DB2 without requiring the user to change any of their allocations.
The names of the necessary DB2 software libraries are retrieved from the parmlib. This
member is created by your installation at install time.
Action:
Check with your System Administrator that the name of the DB2 software library has
not been misspelled in the member.
PT272E
INTERNAL ERROR. PTLDCB INVOKED WITH INVALID PARMS. PF1 FOR HELP.
Reason:
An internal error has been detected by the software.
PT273E
UNABLE TO OPEN NECESSARY DB2 SOFTWARE LIBRARIES. PF1 FOR HELP.
Reason:
An attempt to open necessary DB2 software libraries has failed. The products ALLOCATE
and OPEN the DB2 libraries for use as a TASKLIB. This allows the products to connect to
different versions of DB2 without requiring the user to change any of their allocations.
The names of the necessary DB2 software libraries are retrieved from the parmlib. This
member is created by your installation at install time.
218 Message Reference Guide (PS to ZLB)
PT Messages
PT274E
GETMAIN FAILURE. INSUFFICIENT VIRTUAL STORAGE TO CONTINUE PROCESSING.
Reason:
An attempt to obtain additional virtual storage (via the GETMAIN service) has failed. As
a result, processing could not be completed.
Action:
Possible solutions to this problem are as follows:
■
Exit any split screen sessions that may be in effect.
■
Increase the region size of your TSO LOGON procedure. We recommend a region
size between 2048 to 3072 KB.
PT275E
UNABLE TO ALLOCATE/OPEN OR DEALLOCATE/CLOSE DB2 SOFTWARE LIBRARIES.
Reason:
An attempt to allocate or open necessary DB2 software libraries has failed. The
products ALLOCATE and OPEN the DB2 libraries for use as a TASKLIB. This allows the
products to connect to different versions of DB2 without requiring the user to change
any of their allocations. The names of the necessary DB2 software libraries are retrieved
from the parmlib. This member is created by your installation at install time.
Action:
Check with your System Administrator that the name of the DB2 software library has
not been misspelled in the member.
PT276E
USE OF THE SPECIFIED COMMAND REQUIRES A LICENSE FOR COMPUTER ASSOCIATES
UTILITIES.
Reason:
The requested command is not available. The DISPLAY CA and TERMINATE CA primary
commands are available only if your installation has a license for CA Utilities.
Chapter 2: PS to PTUIX 219
PT Messages
PT277E
USE OF THE SPECIFIED COMMAND REQUIRES A LICENSE FOR SQL-EASE.
Reason:
The requested command is not available. The following primary commands are available
only if your installation has a license for CA SQL-Ease:
■
SYNTAX-Verifies the syntactical correctness of your SQL statements.
■
PRED-Determines the indexability/sargability of SQL predicates.
■
STAND-Reformats SQL statements into a standard form.
PT278I
REQUESTED FUNCTION TERMINATED BY ATTENTION.
Reason:
Informs you that you pressed the ATTENTION INTERRUPT key. As a result, processing of
your request has been terminated.
PT279E
REQUESTED FUNCTION HAS ABENDED. ABEND: abend, REASON CODE: number.
Reason:
Indicates that the requested function has abended. If you are unable to determine the
cause of the abend, report this message and the abend and reason code to Technical
Support.
Action:
For assistance, contact CA Support at http://ca.com/support.
PT280E
TSO SERVICE FACILITY ERROR. RETCODE: ret_code, RSNCODE: number.
Reason:
An attempt to invoke the TSO Service Facility has failed. The return code and reason
code listed in the error message are from the TSO Service Facility.
Action:
Make a note of the return and reason code information.
220 Message Reference Guide (PS to ZLB)
PT Messages
PT280E
TSO SERVICE FACILITY ERROR. RETCODE: 14, RSNCODE: 30.
Reason:
This specific PT280 message indicates that the PTLTSRB module needs to be in an
authorized library.
Action:
Refer to the Products Installation Guide for details.
PT281E
TSO SERVICE FACILITY INVOKED FROM A NON-TSO ENVIRONMENT.
Reason:
Indicates that an attempt has been made to invoke the TSO Service Facility in a non-TSO
environment.
PT282E
UNABLE TO LOCATE MODULE PTLTSRB. PRESS HELP FOR MORE INFO.
Reason:
The TSO Service Facility (IKJEFTSR) was unable to find load module PTLTSRB. As a result,
the requested function cannot be performed online. CA products use the TSO Service
Facility to perform certain authorized functions in an online TSO environment. For
example, it is in this way that the Batch Processor executes the .AUTH command in an
online TSO environment. Execution of such authorized functions via the TSO Service
Facility requires that PTLTSRB is added to an APF authorized LINKLIST or STEPLIB library
and the SYS1.PARMLIB member IKJTSO00 must be updated as described in the
Installation Guide. If the PTLTSRB has not been added to an APF authorized LINKLIST or
STEPLIB library, then the requested function must be performed in Batch Mode.
PT283E
ONLINE EXECUTION NOT ALLOWED. SYS1.PARMLIB(IKJTS000) MUST BE UPDATED.
Reason:
An attempt to perform an authorized function via the TSO Service Facility has failed. CA
products can only use the TSO Service Facility if SYS1.PARMLIB member IKJTS000 is
updated as described in the Installation Guide. CA products use the TSO Service Facility
to perform certain authorized functions in an online TSO environment. For example, it is
in this way that the Batch Processor executes the .AUTH command in an online TSO
environment.
Chapter 2: PS to PTUIX 221
PT Messages
PT284E
PTLTSRB COULD NOT BE FOUND IN AN APF AUTHORIZED LIBRARY.
Reason:
The TSO Service Facility (IKJEFTSR) was unable to find load module PTLTSRB in an APF
authorized library. As a result, the requested function cannot be performed online. CA
products use the TSO Service Facility to perform certain authorized functions in an
online TSO environment. For example, it is in this way that the Batch Processor performs
online authorization switching via the .AUTH command. Execution of such authorized
functions via the TSO Service Facility requires that PTLTSRB is added to an APF
authorized LINKLIST or STEPLIB library. If the PTLTSRB has not been added to an APT
authorized LINKLIST or STEPLIB library, then the requested function must be performed
in Batch Mode.
PT285E
REQUESTED FUNCTION REQUIRES PTILIB DATASETS TO BE APF AUTHORIZED.
Reason:
The requested function cannot be performed without APF authorization. All of the data
setS allocated to the PTILIB DDNAME must be APF authorized libraries. The load library
should be allocated to the PTILIB DDNAME.
Action:
We recommend that you make this load library an APF authorized library.
PT286E
AN INTERNAL ERROR HAS OCCURRED. PRESS HELP (PF1) FOR MORE INFORMATION.
Reason:
This is internal error message indicates that a product encountered an internal
processing condition that was unexpected or undesirable, or both.
Action:
This error should be reported to Technical Support. Give Technical Support the
diagnostic information that accompanies the error message.
222 Message Reference Guide (PS to ZLB)
PT Messages
PT287E
RESERVED FOR LOGGING ERRORS TO ISPF LOG.
Reason:
This is internal error message indicates that a product encountered an internal
processing condition that was unexpected or undesirable, or both.
Action:
Report this error to Technical Support and provide the diagnostic information that
accompanies the error message.
PT288E
YOU ALREADY HAVE AN ACTIVE PLAN ANALYZER SESSION. PRESS HELP FOR INFO.
Reason:
You have attempted to jump to a product that you are already using.
Action:
You must exit the product you are currently in to get back to your existing product
session.
PT289E
THE ATTACHED VERSION OF DB2 DOES NOT SUPPORT DDF. PF1 FOR HELP.
Reason:
Your SQL statement references a remote location. The attached version of DB2 does not
support the Distributed Data Facility (DDF). DDF is only supported by DB2 V2.2 and
above.
PT290E
DATASET NAME MUST BE FILLED IN.
Reason:
You cannot continue without specifying a partitioned data set name.
Chapter 2: PS to PTUIX 223
PT Messages
PT291E
INVALID CHARACTERS IN DATASET NAME.
Reason:
Dataset names can contain only letters, numbers, $, @, and #. A data set name cannot
start with a number.
PT292E
DUPLICATE MEMBERS SPECIFIED.
Reason:
The member you specified already exists in this data set.
Action:
Specify another member name.
PT293E
NO MEMBER SPECIFIED AFTER PAREN.
Reason:
You put an opening parenthesis at the end of the data set name, but you did not specify
a member.
Action:
Remove the opening parenthesis or specify a member and close the parenthesis.
PT294E
MEMBER NAME IS TOO LONG.
Reason:
The member name you specified is too long. Dataset member names can only be 8
characters long.
Action:
Enter a shorter member name.
224 Message Reference Guide (PS to ZLB)
PT Messages
PT295E
DATASET NAME IS TOO LONG.
Reason:
The data set name you specified is too long.
Action:
Enter a shorter data set name.
PT296E
MEMBER NAME IS INVALID
Reason:
The member name you specified is invalid. A member name can contain only letters,
numbers $, @, or #. It cannot start with a number.
Action:
Enter a valid member name, or leave the field blank to access the member selection list.
PT297E
A QUALIFIER IN THE DATASET NAME IS INVALID.
Reason:
A qualifier in the data set name that you specified is invalid. Qualifiers can only contain
letters, numbers, $, @, or #. They cannot start with numbers.
Action:
Correct the data set qualifier and try again.
PT298E
UNABLE TO ALLOCATE DATASET.
Reason:
The data set specified cannot be allocated. If the partitioned data set is being used in
another process, you cannot use it here.
Action:
Specify a different data set name.
Chapter 2: PS to PTUIX 225
PT Messages
PT299E
MEMBER SPECIFIED FOR NON-PARTITIONED DATASET.
Reason:
The member you specified belongs to a non-partitioned data set. You must specify a
member of a partitioned data set.
Action:
Enter a different data set name and member name.
PT300E
UNABLE TO OPEN THE REQUESTED DATASET.
Reason:
You have requested a data set that cannot be opened.
Action:
Check to make sure the data set and member names are valid and that the data set is
not already in use.
PT301E
OUTPUT MEMBER EXISTS AND "REPLACE = NO" WAS SPECIFIED.
Reason:
CA products cannot use the output member specified because it already exists.
Action:
You must specify a different output member, or else change the REPLACE field to "YES".
PT302I
SELECT A MEMBER FOR PROCESSING.
Reason:
You have specified a partitioned data set without specifying a member name.
Action:
Select a member from the displayed member selection list to continue.
226 Message Reference Guide (PS to ZLB)
PT Messages
PT303I
NO MEMBER WAS SELECTED FOR PROCESSING.
Reason:
You did not select a member from the member selection list, so processing was
canceled.
Action:
You can enter a member name in the member field, or return to the member selection
list again.
PT304E
THE INPUT MEMBER SPECIFIED DOES NOT EXIST.
Reason:
The specified member does not exist in the data set specified.
Action:
Check the member name, or use the member selection list to select a member. (To
access the member selection list, leave the member field blank, or enter a wildcard
pattern.)
PT305E
"REPLACE = NO" WAS SPECIFIED WITHOUT SPECIFYING AN OUTPUT MEMBER.
Reason:
CA products do not have a member to use for output, since you set the REPLACE field to
"NO" and left the MEMBER field blank.
Action:
Change the REPLACE field to "YES" or enter a member name in the MEMBER field.
Chapter 2: PS to PTUIX 227
PT Messages
PT306E
ONLY ONE MEMBER MAY BE SELECTED.
Reason:
You tried to select multiple members from the selection list. Only one member can be
selected at a time.
Action:
Blank out the 'S' next to all members except one.
PT307E
VALID OPTIONS ARE S (SELECT), B (BROWSE) AND E (EDIT).
Reason:
The only line commands you can enter next to a member name are S, B or E.
Action:
Enter one of these commands to continue.
PT308E
YOU MUST ENTER A MODEL ID FOR CREATION.
Action:
Enter a name for the new model ID you are creating (templating). The model ID name
field is in the header.
PT309E
EMBEDDED BLANKS INVALID IN MODEL ID.
Reason:
You cannot have embedded blanks in a model ID name.
Action:
Remove the blanks.
228 Message Reference Guide (PS to ZLB)
PT Messages
PT310E
INVALID CHARACTERS IN MODEL ID.
Reason:
The only characters you can use in a model ID name are letters, numbers, $ @ and #. A
model ID name cannot start with a number.
PT311E
YOU MUST ENTER A VALID SHARE OPTION (Y,N,U).
Reason:
The Share option must be set to one of the following values: Y, N, or U.
PT312E
YOU HAVE ENTERED AN INVALID LINE COMMAND. PRESS HELP FOR INFORMATION.
Reason:
The line command you entered is not valid.
Action:
Use one of the following commands: B, T, U, or D.
PT313E
YOU HAVE ENTERED A RESTRICTED LINE COMMAND. PRESS HELP FOR INFORMATION.
Reason:
Some line commands can only be used on models that reside in the user library. U
(update) and D (delete) are restricted commands. They can only be used on model IDs
that have a share option of "U" or that you created. You can use B (browse) and T
(template) on any model ID listed.
Chapter 2: PS to PTUIX 229
PT Messages
PT314E
YOU HAVE ENTERED AN INVALID GENERAL MODEL SERVICES COMMAND.
Reason:
The command you entered at the COMMAND prompt is not available in Model Services.
Type '?' at the COMMAND prompt to get a list of valid commands. In addition to those,
the following commands are valid:
■
CANCEL
■
END
■
EXIT
■
HEADER
■
MAIN
■
=X
PT315E
DUPLICATE MODEL ID, PLEASE SPECIFY ANOTHER.
Reason:
The model ID you specified already exists.
Action:
Enter a new name for the model ID being created.
PT316E
MODEL ID DOES NOT EXIST.
Reason:
The model ID you specified does not exist.
Action:
You must enter an existing model ID name, except when you are templating a new
model ID. Use "*" to generate a selection list of existing model IDs.
PT317E
MODEL ID IS NOT SHAREABLE.
Reason:
This model ID and its members can only be updated by its creator.
230 Message Reference Guide (PS to ZLB)
PT Messages
PT318E
SUPPLY A NEW MODEL ID FOR YOUR TEMPLATED MODEL.
Reason:
You indicated that you wanted to template a new model ID, but you did not enter a new
model ID name.
Action:
Enter the new MODEL ID name.
PT319E
YOU HAVE ENTERED AN INVALID LINE COMMAND. PRESS HELP FOR INFORMATION.
Reason:
The line command you entered is not valid.
Action:
The following commands are valid: I, D, R, X, S, B, and E.
PT320E
YOU MUST ENTER A UTILITY NAME.
Action:
Before Model Services can process your command, you must enter a utility name in the
line being worked with.
PT321E
EMBEDDED BLANKS INVALID IN UTILITY NAME.
Reason:
Utility names cannot have blanks in them.
Action:
Replace the blanks with "_" or remove them completely.
Chapter 2: PS to PTUIX 231
PT Messages
PT322E
INVALID CHARACTERS IN UTILITY NAME.
Reason:
The only characters you can use in a utility name are letters, numbers, $ @ _ and #. A
utility name can not start with a number.
PT323E
YOU MUST ENTER A VALID OBJECT TYPE.
Reason:
The object type you entered is not valid. Valid types are as follows:
■
SG
■
V
■
DB
■
A
■
TS
■
S
■
T
■
P
■
I
■
PK
PT324E
UNABLE TO ALLOCATE THE MODEL MEMBER.
Reason:
The model member you specified cannot be allocated. If the partitioned data set is
being used in another current process, you cannot use it here.
232 Message Reference Guide (PS to ZLB)
PT Messages
PT325E
THE MODEL DATASET IS NOT PARTITIONED.
Reason:
The model data set must be a partitioned data set.
Action:
Enter the name of a partitioned data set.
PT326E
UNABLE TO OPEN THE MODEL MEMBER.
Reason:
The model member you specified cannot be opened.
PT327E
DUPLICATE UTILITY, PLEASE SPECIFY ANOTHER.
Reason:
The utility you specified already exists in this model ID for the type of object you
specified.
Action:
Enter a new utility name.
PT328E
YOU HAVE ENTERED AN INVALID LINE COMMAND. PRESS HELP FOR INFORMATION.
Reason:
The line command you entered is not valid on this screen. The following commands are
valid only when you have edit authority in a member: I, D, or R.
There are no line commands you can use when you do not have edit authority.
PT329E
YOU MUST ENTER A SYMBOL NAME.
Reason:
A symbol name must be included when you insert a new symbol.
Chapter 2: PS to PTUIX 233
PT Messages
PT330E
EMBEDDED BLANKS INVALID IN SYMBOL NAME.
Reason:
Symbol names cannot have blanks in them.
Action:
Remove the blanks in symbol names.
PT331E
INVALID CHARACTERS IN SYMBOL NAME.
Reason:
The only characters you can use in a symbol name are letters, numbers, $ @ and #. A
symbol name cannot start with a number.
PT332E
DUPLICATE SYMBOL NAME, PLEASE SPECIFY ANOTHER.
Reason:
You specified a symbol name already used in this model member.
Action:
Enter a different name.
PT333E
YOU HAVE USED A RESTRICTED LINE COMMAND.
Reason:
R (Repeat) and D (Delete) are only valid on user defined symbols.
234 Message Reference Guide (PS to ZLB)
PT Messages
PT334I
MODEL SUBSTITUTION PERFORMED.
Reason:
This message tells you that changes to the data you made have been saved in the Model
ID. Model substitution is performed when you press Enter with no line commands.
Action:
To avert Model substitution, press END (PF3) immediately after making changes to the
data using line commands.
PT335I
MODEL SUBSTITUTION AVERTED.
Reason:
This message tells you that changes to the data you made have NOT been saved in the
Model ID.
Action:
To perform a Model substitution, press Enter with no line commands. If you press END
(PF3) immediately after making changes to the data using line commands, the
substitution is averted.
PT336E
YOU HAVE USED A RESTRICTED LINE COMMAND.
Reason:
E (Edit), R(Repeat) and I(Insert) can only be used on model members that you own, or
that are shareable.
PT337E
YOU MUST ENTER A MEMBER NAME.
Reason:
A member name must be specified before the requested action can be completed.
Chapter 2: PS to PTUIX 235
PT Messages
PT338E
EMBEDDED BLANKS INVALID IN MEMBER NAME.
Reason:
Member names cannot have blanks in them.
Action:
Remove blanks in member names.
PT339E
INVALID CHARACTERS IN MEMBER NAME.
Reason:
The only characters you can use in a model member name are letters, numbers, $ @
and #. A model member name cannot start with a number.
PT340E
YOU MAY ONLY SELECT ONE LOCATION.
Reason:
To select a location, enter "S" next to the appropriate location ID. Only one location may
be selected.
PT341E
YOU MUST ENTER A USER LIBRARY BEFORE EDITING A MODEL MEMBER.
Reason:
You tried to used the E(edit) line command for a Model ID that uses only the INSTALL
LIB.
Action:
You must specify a USER LIB before editing the member.
PT342E
SELECT OPTION MUST BE D, S, T, OR Z. PRESS HELP FOR MORE INFORMATION.
Reason:
There are only four select options (line commands) which are valid on this screen. They
are as follows: D, S, T, and Z.
236 Message Reference Guide (PS to ZLB)
PT Messages
PT343E
MAP NUMBER MUST BE NUMERIC. PRESS HELP FOR MORE INFORMATION.
Reason:
The MAP number must correspond to a source column number (SRC#) to be valid.
PT344E
MAP NUMBER IS OUT OF RANGE. PRESS HELP FOR MORE INFORMATION.
Reason:
The MAP number must correspond to a source column number (SRC#) to be valid.
Action:
Check the source column to which you want to map this target column and try again.
PT345E
MULTIPLE TARGET COLS MAPPED TO SAME SOURCE COL. PRESS HELP FOR
INFORMATION.
Reason:
There must be a one-to-one correspondence in the target column to source column
mapping. The SRC# you entered has already been used for another target column.
PT346E
INVALID MODEL ID REPLACED WITH DEFAULT.
Reason:
The model ID you entered was invalid. The system has replaced it with @DEFAULT.
PT347E
INVALID COLUMN TYPE CONVERSION. PRESS HELP FOR MORE INFORMATION.
Reason:
You have specified an invalid column type conversion.
Chapter 2: PS to PTUIX 237
PT Messages
PT348E
NO LIST EXISTS TO REDISPLAY. PRESS HELP FOR MORE INFORMATION.
Reason:
The Drop Impact option was not set to Y, or no Drop Impact list was returned. In case,
there is no list which can be displayed in response to the IMPACT command.
Action:
Enter RO from the Drop Object selection list screen to get an options screen on which
the Drop Impact display options may be reset.
PT349I
rqtab HAS rqcnt ROW(S).
PT350I
VALID VALUES FOR DEVICE TYPE ARE 3350,3375,3380, OR 3390.
Reason:
You have entered an invalid value in the Device Type field. The value entered in this field
represents the DASD device type. Valid values are 3350, 3375, 3380 or 3390.
Action:
To correct this problem, enter a valid value in the Device Type field and press Enter.
PT351I
PAGE SIZE MUST BE 4K OR 32K.
Reason:
You have entered an invalid value in the Page Size field. The value in this field represents
the page size in the tablespace. Valid values are 4k or 32k.
Action:
To correct this problem, enter a valid value in the Page Size field and press Enter.
238 Message Reference Guide (PS to ZLB)
PT Messages
PT352I
FREEPAGE MUST BE NUMERIC. VALID VALUES ARE BETWEEN 0 AND 255.
Reason:
You have entered an invalid value in the Freepage field. The value of this field
represents how often to leave a free page in a table during a table load or a table reorg.
Valid values are any number between 0 and 255, inclusive.
Action:
To correct this problem, enter a valid value in the Freepage field and press Enter.
PT353I
PCTFREE MUST BE NUMERIC. VALID VALUES ARE BETWEEN 0 AND 99.
Reason:
You have entered an invalid value in the Pctfree field. The value of this field represents
what percent of each page is left free during a table load or a table reorg. Valid values
are any number between 0 and 99, inclusive.
Action:
To correct this problem, enter a valid value in the Pctfree field and press Enter.
PT354I
SECQTY PCT MUST BE NUMERIC.
Reason:
You have entered an invalid value in the Secqty Pct field. The value of this field
represents the secondary quantity percent, which is used to determine the secondary
quantity by taking a percent of the primary quantity. Valid values are any number
between 0 and 99, inclusive.
Action:
To correct this problem, enter a valid value in the Secqty Pct field and press Enter.
Chapter 2: PS to PTUIX 239
PT Messages
PT355I
SEG SIZE MUST BE NUMERIC AND A MULTIPLE OF 4 LESS THAN 64. PF1 FOR MORE
INFORMATION.
Reason:
You have entered an invalid value in the Seg Size field. The value entered in this field
represents the table space segment size. Valid values are multiples of 4, from 0 to 64.
For example, 0, 4, 8, 12...64 are valid values.
Action:
To correct this problem, enter a valid value in the Seg Size field and press Enter.
PT356I
VALID VALUES FOR QTY TYPE ARE ROW, TRK, AND CYL.
Reason:
You have entered an invalid value in the Qty Type field. The value of this field tell you
what is being measured in the quantity field. Valid values are ROW, TRK, or CYL.
Action:
To correct this problem, enter a valid value in the Qty Type field and press Enter.
PT357I
VALID VALUES FOR VOLUME ARE N, S, OR V.
Reason:
You have entered an invalid value in the Volume field. Volume is used to access the
Space Locator function of the Space Calculator.
Valid values are: N, S, and V.
Action:
To correct this problem, enter a valid value in the Volume field and press Enter.
240 Message Reference Guide (PS to ZLB)
PT Messages
PT358E
QUANTITY MUST BE NUMERIC. PRESS PF1 FOR MORE INFORMATION.
Reason:
Character data has been entered for the Quantity.
Action:
Enter a number for Quantity. The Quantity refers to the Quantity Type field (from the
Control Parameters section). The number indicates the number of units for the specified
Quantity Type (row, track, or cylinder).
PT359I
ENTER "TOTALS" COMMAND TO VIEW CALCULATED SPACE STATISTICS. PRESS PF1 FOR
HELP.
Reason:
Informs you that the total DASD space requirements for your table space have been
calculated.
Action:
To view the calculated space statistics, enter "T" or "TOTALS" in the Space Calculation
screen's command line. Press Enter. The calculated totals appear at the bottom of your
screen. To remove the totals from the screen, enter "T" or "TOTALS" again in the
command line. The (T)OTALS command works as a toggle. The displayed totals are
recalculated each time you change the input information.
PT360E
INVALID LINE COMMAND. ENTER D, E, I OR R. PRESS HELP FOR MORE INFORMATION.
Reason:
An invalid line command has been entered at the Space Calculation screen.
Action:
Enter one of these commands: D, E, I or R.
PT361E
ROW LENGTH MUST BE NUMERIC.
Reason:
Character data has been entered for the Row Length. Enter a number. The Row Length
is your estimate of how long each row can be.
Chapter 2: PS to PTUIX 241
PT Messages
PT362I
THE SEGSIZE HAS BEEN RESET TO NEAREST MULTIPLE OF 4 LESS THAN 68.
Reason:
Informs you that the specified table space segment size was invalid. The segment size
has been reset to the nearest multiple of 4 which is less than 68.
PT363I
THE FREEPAGE VALUE HAS BEEN RESET TO THE MAXIMUM VALUE OF 255.
Reason:
Informs you that the Freepage field has been set to 255. This is done when you enter a
value larger than 255, which is the maximum value for Freepage.
PT364I
THE AVG DUPLICATES VALUE HAS BEEN RESET TO THE MAXIMUM VALUE OF 255.
Reason:
You have selected to use the Index Space Calculation feature. This message occurs when
you enter a value greater than 255 in the Avg Duplicates field. When you press Enter,
the maximum value (255) is automatically inserted as the average number of duplicate
indexes.
Action:
Enter a lower number than 255 or keep the value at 255.
PT365E
YOU ALREADY HAVE AN ACTIVE COMPILE/QQF SESSION. PRESS HELP FOR MORE
INFORMATION.
Reason:
You attempted to jump to a product you are already using.
Action:
You must exit the product you are currently in to get back to the product you want.
242 Message Reference Guide (PS to ZLB)
PT Messages
PT366E
UNABLE TO LOAD DSNHDECP. IBM DEFAULTS WILL BE USED.
Reason:
A LOAD request for the DB2 DSNHDECP module has failed. The products load the
DSNHDECP module to determine the release level of the attached DB2 subsystem.
DSNHDECP will be loaded from the DB2 software libraries specified in the parmlib.
Action:
Verify that libraries named in the SETUP member of CDBAPARM are correct.
PT366I
SELECTED COL(S) WIDTH EXCEEDS SCREEN WIDTH, BYTE SCROLLING IN EFFECT.
Reason:
Indicates that the horizontal scrolling mode has been switched from column scrolling
(the default) to byte scrolling. When byte scrolling is in effect, a column's data may be
split across screens so that only a portion of the data is visible. Data will be scrolled
LEFT/RIGHT by bytes, rather than by column. Byte scrolling has been turned on because
the width of one or more of the columns selected in your query exceeds the width of
the screen. These columns would not be visible in scroll by column mode.
PT367I
PLEASE CHOOSE AN OPTION FROM THE LIST SHOWN.
Action:
You must select at least one option from the list shown.
PT368I
SQL STATEMENT LENGTH EXCEEDS 32K. TREE COMMAND BYPASSED.
Reason:
Your installation password module contains a product password that will expire soon.
Action:
Execute the PASSWORD command for more detailed information on product and CPU
passwords.
Chapter 2: PS to PTUIX 243
PT Messages
PT369E
THE MODEL SERVICES TABLE IS EMPTY. PRESS HELP FOR MORE INFORMATION.
Reason:
Your installation does not have the Model Services DB2 Table properly loaded for this
subsystem.
Action:
Refer to the Installation Guide for more information.
PT370W
AT LEAST 1 CA-DB2 PRODUCT KEY EXPIRES IN THE NEXT 30 DAYS.
Reason:
Your installation is using an over ride password to allow entry to your purchased
products. That password will expire within the next 30 days.
Action:
A valid product key is required to continue using the products. Contact Technical
Support for more information.
PT371I
A TRIALED PRODUCT PASSWORD WILL EXPIRE ON date.
Reason:
Your installation password module contains a product password that will expire soon.
Action:
Execute the PASSWORD command for more detailed information on product and CPU
passwords.
PT372I
SELECTED COL(S) WIDTH EXCEEDS SCREEN WIDTH, BYTE SCROLLING IN EFFECT.
Reason:
The horizontal scrolling mode has been switched from column scrolling (the default) to
byte scrolling. When byte scrolling is in effect, a column's data may be split across
screens so that only a portion of the data is visible. Data will be scrolled left/right by
bytes rather than by column. Byte scrolling has been turned on because the width of
one or more of the columns selected in your query exceeds the width of the screen.
These columns would not be visible in scroll by column mode.
244 Message Reference Guide (PS to ZLB)
PT Messages
PT373E
INVALID DATA CAPTURE VALUE SPECIFIED. PF1 FOR HELP.
Reason:
The value specified for the DATA CAPTURE field is invalid. Valid values for this prompt
are as follows: NONE and CHANGES.
PT374E
AN OVERLAY OF DBCS CHARACTERS WOULD CAUSE TRUNCATION OF DATA.
Reason:
An overlay of DBCS data would cause data truncation. The characters overlaid included
some SO SI characters that were inserted so that the data could be properly displayed.
These SO SI characters are not part of the actual data, so if they are overtyped by SBCS
characters the resulting string becomes longer than the original string.
Action:
Correct the overtype or blank out some trailing characters at the end of the string so
that resulting string may fit into the original string.
PT375E
MODEL MEMBER SPECIFIED IS EMPTY.
Reason:
The model member specified contained no lines.
Action:
Specify a model member that contains lines.
PT377
YOU ALREADY HAVE AN ACTIVE PGF SESSION. PRESS PF1 FOR MORE INFORMATION.
Reason:
Indicates that you have attempted to jump to a product that you are already using.
Action:
You must exit the product you are currently in to get back to the product you want.
Chapter 2: PS to PTUIX 245
PT Messages
PT379
YOU ALREADY HAVE AN ACTIVE PKG SESSION. PRESS PF1 FOR MORE INFORMATION.
Reason:
Indicates that you have attempted to jump to a product that you are already using.
Action:
You must exit the product you are currently in to get back to the product you want.
PT380E
DESTINATION LENGTH ERROR
Reason:
The value specified in the Destination field has an incorrect length. The value may be a
field of up to eight characters followed by a comma and then another field of up to eight
characters or one eight character field.
PT381E
YOU ALREADY HAVE AN ACTIVE PRA SESSION. PRESS PF1 FOR MORE INFORMATION.
Reason:
You attempted to jump to a product you are already using.
Action:
You must exit the product you are currently in to get back to the product you want.
PT382E
UNABLE TO ESTABLISH BROWSE SESSION ON REQUESTED DATASET.
Reason:
The BROWSE session for the data set you requested was not able to be established. The
most common reasons for failure are NEW or MOD data set dispositions, or empty data
set.
PT383E
VALID SELECTION CODES ARE B-BROWSE OR E-EDIT.
Reason:
You have entered an invalid line command. The only line commands you can enter on
this screen are B (browse) or E (edit).
246 Message Reference Guide (PS to ZLB)
PT Messages
PT384E
AN INCOMPLETE QUOTED OR APOSTROPHIZED STRING HAS BEEN ENCOUNTERED.
Reason:
An incomplete character string constant or delimited SQL identifier was detected while
parsing your SQL statement. A closing quote or apostrophe is missing.
Action:
Carefully read through your SQL statement making sure all delimited SQL identifiers and
character string constants are terminated with a quote or an apostrophe. If necessary,
use the FIND command to locate the opening quote or apostrophe.
PT385E
AN INCOMPLETE HOST VARIABLE HAS BEEN ENCOUNTERED.
Reason:
An incomplete host variable was detected while parsing your SQL statement. Host
variable names are preceded by a colon (:). CA SQL-Ease has detected a colon that is not
followed by a host variable name.
Action:
Delete the colon, or add a host-variable name immediately after the colon. If necessary,
use the fine command to locate the colons in your SQL statement.
PT386E
AN INCOMPLETE HEX CONSTANT HAS BEEN ENCOUNTERED.
Reason:
An incomplete hexadecimal string constant was detected while parsing your SQL
statement. A closing quote or apostrophe is missing. A valid hex string constant consists
of an X followed by an even number of hexadecimal digits delimited by string delimiters.
An example of a valid hex string constant is: X'F0F1F2.
Action:
Carefully read through your SQL statement making sure all string constants are
terminated with a quote or an apostrophe. If necessary, use the FIND command to
locate the opening quote or apostrophe.
Chapter 2: PS to PTUIX 247
PT Messages
PT387E
AN INCOMPLETE OR INVALID GRAPHIC OR DBCS STRING HAS BEEN DETECTED.
Reason:
An incomplete or invalid graphic string constant was detected while parsing your SQL
statement.
In a PL/I program, the format of a graphic string is <'****'G>. Where < represents the
shift out character X'0E'; > represents the shift in character X'0F"; * represents a valid
Double Byte character; ' represents the DBCS string delimiter X'427D'; and G represents
the DBCS character X'42C7.
In all other contexts, a graphic string must be specified in one of the following two
formats: G'<****>' or N'<****>'. Where < represents the shift out character X'0E'; >
represents the shift in character X'0E'; * represents a valid Double Byte character; and '
represents the EBCDIC string delimiter X'7D'.
This error could also be an indication that your SQL statement contains an incomplete
DBCS string (i.e. a string that begins with a SHIFT OUT, X'0E', but is not terminated with a
SHIFT IN, X'0F').
PT388E
YOU ALREADY HAVE AN ACTIVE VIS SESSION. PRESS PF1 FOR MORE INFORMATION.
Reason:
You attempted to jump to a product you are already using.
Action:
You must exit the product you are currently in to get back to the product you want.
PT389E
YOU ALREADY HAVE AN ACTIVE PQO SESSION. PRESS PF1 FOR MORE INFORMATION.
Reason:
You attempted to jump to a product you are already using.
Action:
You must exit the product you are currently in to get back to the product you want.
248 Message Reference Guide (PS to ZLB)
PT Messages
PT390W
MESSAGES ISSUED DURING PARMLIB PROCESSING, ENTER STATUS FOR DETAILS.
Reason:
A non-serious error has occurred during parmlib processing. The STATUS command
should be entered to see what has occurred. the STATUS command will display each
CDBAPARM member processed along with status messages.
PT391E
ERRORS OCCURRED DURING PARMLIB PROCESSING.
Reason:
A serious error has occurred during parmlib processing. The STATUS command should
be entered to see what has occurred. The STATUS command will display each
CDBAPARM member processed along with status messages. The problem must be
corrected before rerunning.
PT393E
ACM: acm ACMID: acmid.
Reason:
This informational message displays the current ACMID and if ACM is ON or OFF.
PT394I
CURRENT SQLID: sqlid.
Reason:
This informational message displays the current SQLID.
PT395I
QFILE REQUEST COMPLETED.
Reason:
Your QFILE request was completed.
Chapter 2: PS to PTUIX 249
PT Messages
PT396E
QFILE REQUESTED FAILED.
Reason:
Your QFILE request has failed due to environmental problems.
Action:
Check your Print Parameters Profile and retry the QFILE request.
PT397I
PFILE REQUESTED COMPLETED.
Reason:
Your PFILE request was completed.
PT398E
PFILE REQUEST FAILED.
Reason:
Your PFILE request has failed due to environmental problems.
Action:
Check your Print Parameters Profile and retry the PFILE request.
PT399
DETECTOR SESSION IS ALREADY ACTIVE, PRESS PF1 FOR MORE INFORMATION.
Reason:
You have attempted to jump to a product that you are already using.
Action:
You must exit the product you are currently in to get back to the product you desire.
250 Message Reference Guide (PS to ZLB)
PT Messages
PT400E
DYNAMIC ALLOCATION ERROR, RC=code;RSN=code;INFO=code.
Reason:
The Dynamic Allocation has failed for the data set name that you specified for the
current function. The message provides you with the DYNALLOC return code, INFO code,
and ERROR code. This allows you to locate the problem in the appropriate IBM macro
manual.
PT401E
REPORT FILE OPEN ERROR.
Reason:
An output file open error has been encountered.
Action:
Check your Print Parameters Profile and retry.
PT402E
DYNAMIC DE-ALLOCATIONS ERROR, RC=code;RSN=code;INFO=code.
Reason:
The Dynamic Allocation has failed for the data set name that you specified for the
current function. The message provides you with the DYNALLOC return code, INFO code,
and ERROR code. This allows you to locate the problem in the appropriate IBM macro
manual.
PT403I
QFILE REQUEST CANCELED.
Reason:
Your QFILE request was canceled.
PT404I
PFILE REQUEST CANCELED.
Reason:
Your PFILE request was canceled.
Chapter 2: PS to PTUIX 251
PT Messages
PT405E
REQUESTED OBJECT NOT FOUND.
Reason:
The object you specified was not found.
PT406E
SELECTION REQUIRED.
Action:
You must enter S to select one or more of the available options.
PT407E
UNABLE TO COMPLETE PROCESSING FOR DISPLAYED INPUT.
Reason:
The Batch Processor input encountered an error before being able to process the
displayed input.
Action:
Correct the error and resubmit.
PT408E
YOU ALREADY HAVE AN ACTIVE PLA SESSION. PRESS PF1 FOR MORE INFORMATION.
Reason:
You have attempted to jump to a product that you are already using.
Action:
You must exit the product you are currently in to get back to the product you desire.
PT409I
YOU ALREADY HAVE AN ACTIVE PDN SESSION. PRESS PF1 FOR MORE INFORMATION.
Reason:
You have attempted to jump to a product that you are already using.
Action:
You must exit the product you are currently in to get back to the product you desire.
252 Message Reference Guide (PS to ZLB)
PT Messages
PT410E
ENTER DB2 OR EXT (EXTERNAL) FOR THE COMPRESSION TYPE.
Reason:
The compression type entered was invalid. The following options are valid:
■
DB2
■
EXT
PT411E
ENTER 127 OR 255 FOR THE MAXIMUM NUMBER OF ROWS PER PAGE.
Reason:
The value for the maximum number of rows per page was invalid. Valid values are as
follows: 127 and 255.
PT412E
VARIABLE RECORD LENGTH OUTPUT IS NOT SUPPORTED.
Reason:
A variable length record output file cannot be used with this command. Only a fixed
length record may be used.
PT413E
INVALID VALUE FOR LOCKMAX PARAMETER. PRESS PF1 FOR HELP.
Reason:
You have specified an invalid number for the LOCKMAX parameter. Valid values are
numbers from 0 through 2,147,483,647, or SYSTEM. A value of zero indicates no
threshold for escalating the locks. An integer value indicates that when the indicated
number of locks has been reached, the locks will be escalated. A value of SYSTEM
indicates that the LOCKMAX threshold value has been set during the installation of DB2.
PT414E
INVALID VALUE FOR INDEX TYPE. PRESS PF1 FOR HELP.
Reason:
You have specified an invalid value for the index type. Valid values are 1, 2, or a space,
which is treated as a 1. If the LOCKSIZE attribute of the tablespace in which the table to
be indexed exists is ROW, index type must be 2. Otherwise, type is accepted.
Chapter 2: PS to PTUIX 253
PT Messages
PT415E
BLANK BPID. UNABLE TO COMPLY WITH YOUR REQUEST. HELP FOR INFO.
Reason:
You requested to EDIT, BROWSE or re-SUBMIT the DDL of a job whose BPID is blank.
Jobs with blank BPIDs cannot be edited, browsed or re-submitted for execution because
it is not possible to identify and locate the job's DDL without a valid BPID.
PT416E
UNRECOGNIZABLE BPID TYPE PREVENTS REQUESTED ACTION. HELP FOR INFO.
Reason:
You requested to EDIT, BROWSE or re-SUBMIT the DDL of a job whose BPID contains an
unrecognizable format. In order for the Execution Display Facility to identify and locate
the job's DDL, the BPID must be in one of the following recognizable formats:
datasetname
Specifies the sequential data set in which the job's DDL resides.
datasetname-member
Specifies that the job's DDL is a member in the partitioned data set data set name.
creator-strategy-user-timestamp
Specifies that the job's DDL is managed by RC/MIGRATOR in a DB2 table.
Note: The dashes (-) are required delimiters. The number of dashes in the BPID
determines the presumed format of the BPID and where the Execution Display Facility is
to look for the job's DDL (i.e., a sequential file, partitioned data set or an
product-managed DB2 table).
254 Message Reference Guide (PS to ZLB)
PT Messages
PT417E
INVALID BPID PREVENTS REQUESTED ACTION. HELP FOR INFO.
Reason:
You requested to EDIT, BROWSE or re-SUBMIT the DDL of a job whose BPID is in a
recognizable format, but contains invalid data or fields. In order for the Execution
Display Facility to identify and locate the job's DDL, the BPID must have valid data in
each field (if more than one field, each is separated by a dash (-)), as follows:
datasetname
Specifies the sequential data set. data setname may not exceed 44 characters.
datasetname-member
Specifies the partitioned data set. data setname may not exceed 44 characters.
member must be 1 to 8 characters.
creator-strategy-user-timestamp
Specifies the CA RC/Migrator managed DB2 table output. Creator, strategy, and
user must each be 1 to 8 characters. timestamp must be 16 characters.
PT418I
DSNCHAR COMMAND IS OBSOLETE. USE BPIDCHAR INSTEAD. HELP FOR INFO.
Reason:
The DSNCHAR command is no longer supported and has been replaced with the
BPIDCHAR command.
Action:
Use the BPIDCHAR command in order to modify the width of the BPID column on the
Execution Display.
PT420E
Requested model &mod1 not found
Reason:
The specified model name cannot be found in the current model library.
Action:
Verify that you have entered the model name correctly, and that the model member
exists in the model library.
Chapter 2: PS to PTUIX 255
PT Messages
PT421E
ERROR: '#INCLUDE i-model' in model e-model not found
Reason:
The application encountered a not-found condition while attempting to read the
PTIMODEL dataset for the i-model model member. The missing member is referenced in
an #INCLUDE directive from the e-model model member, which is currently being
processed.
Action:
Do the following:
■
Check the PTIMODEL allocation. The PTIMODEL DD does not support
concatenation.
■
Verify that the i-model model name is not misspelled on the #INCLUDE statement
within the e-model model.
■
Verify that the i-model model exists in the model library data set.
PT422E
Model &mod2 recursively included model &mod1
Reason:
Model &mod2 contains an #INCLUDE &mod1 statement where model &mod1 and
&mod2 are the same model. This cannot be processed because it would result in an
infinite loop of inclusion.
Action:
Remove the self reference.
PT423E
Requested model &mod1 cannot be accessed
Reason:
An error occurred while accessing the named model. This is not the normal "not found"
error, and usually indicates a corrupted data set.
Action:
Examine the data set, verify the integrity of the model, and then retry your request.
256 Message Reference Guide (PS to ZLB)
PT Messages
PT424E
Model &mod1 has invalid #INCLUDE statement
Reason:
The specified model includes a syntactically invalid #INCLUDE statement.
Action:
Check the &mod1 model and verify that the name following the #INCLUDE statement
meets the following criteria:
■
It is separated by at least one blank.
■
It is a valid PDS member name (1–8 characters in length).
■
It terminates before column 72.
PT425E
Model &MOD1 has invalid #SET statement syntax:
%VARNAME = MYVALUE has to follow the #SET. Press
HELP while this message is displayed for general
#SET information.
Reason:
The specified model contains a syntactically invalid #SET statement.
Action:
Correct the syntax and try again. The following #SET syntax is valid:
#SET %VARNAME = MYVALUE
PT426E
Model &MOD1 has invalid #SET statement syntax:
Length of %VARNAME in last #SET displayed must be
between 1 and 8 characters. Press HELP while this
message is displayed for general #SET information.
Reason:
The specified model contains a syntactically invalid #SET statement.
Action:
Correct the syntax and try again. The following #SET syntax is valid:
#SET %VARNAME = MYVALUE
Chapter 2: PS to PTUIX 257
PT Messages
PT427E
Model &MOD1 has invalid #SET statement syntax:
Equal sign missing in the last #SET displayed.
Press HELP while this message is displayed for
general #SET information.
Reason:
The specified model contains a syntactically invalid #SET statement.
Action:
Correct the syntax and try again. The following #SET syntax is valid:
#SET %VARNAME = MYVALUE
PT428E
Your model JCL contains an invalid #SET statement.
Overriding existing automatic symbolics is not allowed.
Remove #SET for the %&MOD1 symbolic. Press HELP while
this message is displayed for general #SET information.
Reason:
The application detected an attempt to override an automatic symbolic (such as
%DBNAME) or a system automatic symbolic (such as %PTILIBx).
Action:
Rename the #SET variable, verify that the variable name does not conflict with
automatic symbolics or system automatic symbolics, and try again.
PT500E
AN ERROR OCCURRED WHILE ATTEMPTING TO ALLOCATE STORAGE.
Reason:
An error has occurred while attempting to allocate storage. The region size for your TSO
session may be too small.
Action:
Attempt to increase the size.
258 Message Reference Guide (PS to ZLB)
PT Messages
PT501E
AN ERROR OCCURRED DURING THE DB2 SSID/LOCATION SELECTION PROCESS.
Reason:
An error has occurred while processing the DB2 SSID/Location selection process.
Action:
Verify with the product installer that all data sets required to execute products are
allocated and that you have read authority for those data sets.
PT502E
SSID/LOCATION WAS NOT SELECTED. ENTER SSID/LOCATION OR ? FOR LIST.
Reason:
An SSID/Location was not selected during the DB2 SSID/Location selection process.
Action:
Specify a valid SSID/Location or enter a question mark (?) for a selection list.
Chapter 2: PS to PTUIX 259
PT Messages
PT503I to PT518I
PT503I THE REQUESTED COMMAND REQUIRES AN RC/UPDATE LICENSE.
PT504I SELECT A MEMBER TO COMPLETE THE COPY COMMAND.
PT505I SELECT A MEMBER TO COMPLETE THE CREATE COMMAND.
PT506I SELECT A MEMBER TO COMPLETE THE REPLACE COMMAND.
PT507I THE DCREATE COMMAND WILL NOT REPLACE A MEMBER THAT EXISTS.
PT508I DCOPY COMMAND PROCESSED SUCCESSFULLY.
PT509I DCREATE COMMAND PROCESSED SUCCESSFULLY.
PT510I DREPLACE COMMAND PROCESSED SUCCESSFULLY.
PT511I AN "A" OR "B" LINE COMMAND IS REQUIRED FOR THE DCOPY COMMAND.
PT512I AN "M", "C", A SET OF "MM" OR "CC" COMMANDS IS NEEDED FOR THE
COMMAND.
PT513E DATASET NAME ENTERED WAS INVALID, CORRECT AND RETRY.
PT514E THE MEMBER MUST EXIST FOR THE DREPLACE COMMAND.
PT515I THE DCREATE COMMAND MUST BE APPLIED TO A PARTITIONED DATASET.
PT516I PLEASE SPECIFY A NEW MEMBER FOR THE PARTITIONED DATASET.
PT517E AN ERROR HAS OCCURRED DURING YOUR LOG MAINT SESSION.
PT518I UTILITY utilexl EXCLUDED, UTILITY utilexla ACTIVATED
Reason:
Indicates that since the utility utilexl was excluded, its mutually exclusive utility utilexla
was activated for this model. The program requires certain utility functions to be
available during analysis. These functions included Bind, Check Data, Image Copy, Load,
Rebind, Reorg, Runstats and Unload.
To support the CA Utilities, one of the following pairs of mutually exclusive utilities must
be active:
■
To perform an image copy, IBM's COPY or QCOPY (CA Quick Copy).
To load a table, IBM's LOAD or FLOAD (CA Fast Load).
■
To reorg a tablespace, IBM's REORG or RREORG (CA Rapid Reorg).
■
To unload, a table UNLOAD or FLUNLD (CA Fast Unload).
260 Message Reference Guide (PS to ZLB)
PT Messages
PT519E
EXCLUDE FAILED FOR utilexl, UTILITY utilexla NOT FOUND
Reason:
The utilexl utility you tried to exclude cannot be excluded, because its mutually exclusive
utility utilexla cannot be found in this model member.
For more information, see the PT518I message.
PT520I
UTILITY utilexl ACTIVATED, UTILITY utilexla EXCLUDED
Reason:
This information message indicates that since the utility utilexl was activated, its
mutually exclusive utility utilexla has been excluded for this model.
For more information, see the PT518I message.
Chapter 2: PS to PTUIX 261
PT Messages
PT521I to PT537I
PT521I UTILITY utilexl EXCLUDED.
PT522I UTILITY utilexl ACTIVATED.
PT523E UTILITY utilexl CANNOT BE DELETED.
PT524I MODEL MEMBER utilexl CANNOT BE EDITED.
PT525E EDIT FAILED, MEMBER utilexl IN USE.
PT526I MODEL MEMBER utilexl SAVED.
PT531I THE DEFAULT VALUES HAVE BEEN DELETED.
PT532I THE DEFAULT VALUES HAVE BEEN UPDATED.
PT533E PLEASE ENTER A NEW USERID AND DESCRIPTION FOR THE TEMPLATED
DEFAULTS.
PT534I THE DEFAULT VALUES HAVE BEEN SAVED.
PT535I AN SQL ERROR WAS ENCOUNTERED. THE DEFAULT VALUES WERE NOT SAVED.
PT536E THIS USERID ALREADY EXISTS. PLEASE ENTER A DIFFERENT USERID.
PT537I THE DEFAULTS FLAG IN THE PARMLIB IS SET TO ''NO''.
Reason:
This informational message notifies you that the DEFAULTS setting in the SETUP
member of CDBAPARM is set to NO.
Action:
In order to use the global defaults that are modified by the GLOBAL DEFAULTS facility,
you must set this indicator to YES
262 Message Reference Guide (PS to ZLB)
PT Messages
PT538I
THE COLUMNS BELOW REFLECT PREVIOUS ACTIONS ON THE TABLES.
Reason:
Indicates that at least one of the tables in the VIEW SELECT clause has had its definition
altered.
For RC/UPDATE, you have created a table in batch mode during the current session. You
have created or altered a table in your current strategy session.
Action:
None.
PT539I
THE PARMLIB DEFAULTS MAY NOT BE UPDATED.
Reason:
Indicates that the parmlib defaults may not be updated using this facility.
Action:
If you need to update these defaults, you must changes the DEFAULTS member of
CDBAPARM.
PT540E
YOU HAVE AN ACTIVE OBJECT TRACKER SESSION. PRESS HELP FOR INFO.
Reason:
You attempted to jump to a product you are already using.
Action:
You must exit the product you are currently in to get back to the product you want.
PT541E
DATASET HAS AN UNDEFINED RECORD FORMAT. PRESS HELP FOR INFO.
Reason:
The member you have specified for an edit has a record format that is undefined (i.e.
RECFM=U). Files with an undefined record format are not able to be edited, they may
only be browsed or selected.
Chapter 2: PS to PTUIX 263
PT Messages
PT542E
YOU HAVE ENTERED TOO MANY PARAMETERS. PRESS HELP FOR INFO.
Reason:
You have entered too many parameters for a Select or Edit.
Action:
Ensure that the only parameter you entered is the member name.
PT543E
NO MEMBER SPECIFIED. PRESS HELP FOR INFO.
Reason:
You must specify a member for a Select or Edit command.
PT544E
MEMBER SELECTED DOES NOT EXIST. PRESS HELP FOR INFO.
Reason:
The member you specified for a Select command does not exist in this data set.
PT545E
YOU HAVE AN ACTIVE QUERY ANALYZER SESSION. PRESS HELP FOR INFO.
PT546E
YOU HAVE AN ACTIVE DEPENDENCY ANALYZER SESSION. PRESS HELP.
Reason:
Indicates that you have attempted to jump to a product that you are already using.
Action:
You must exit the product you are currently in to get back to the product you desire.
264 Message Reference Guide (PS to ZLB)
PT Messages
PT547E
INVALID COMMAND, VALID COMMANDS ARE CT OR CI.
Reason:
Indicates you have entered an invalid command.
Action:
Enter CT or CI.
PT550E
ALL ENTRIES MUST BE FILLED IN TO CREATE A SPACE STRATEGY.
Reason:
Information is missing on the strategy creation line for the Space Calculator. You must
specify the strategy name (8 characters), creator name (8 characters), strategy type (TS
or IX), database name (8 characters), and the tablespace or indexspace name (8
characters).
PT551E
ERROR ATTEMPTING TO SAVE STRATEGY - STRATEGY NOT SAVED.
Reason:
An error occurred while saving the strategy. The strategy was not saved.
This error typically occurs when you are attempting to save a strategy using a name that
already exists. If this is the case, this message is preceded by an SQL -803 error message.
Another possible cause is that an I/O error occurred during the save attempt.
PT552I
STRATEGY DATA SAVED SUCCESSFULLY.
Reason:
Indicates that no errors were encountered while saving the strategy.
Chapter 2: PS to PTUIX 265
PT Messages
PT553E
ERROR FETCHING STRATEGY.
Reason:
An I/O or catalog fetch error occurred. This problem may be caused by DB2 locks on an
object your strategy needs, by an Alternate Catalog Mapping profile, by an I/O error, or
by corrupted data.
PT554E
ATTEMPT TO SAVE DUPLICATE STRATEGY - STRATEGY ALREADY EXISTS.
Reason:
You changed one or more fields on the Strategy Save screen, resulting in an attempt to
save a duplicate strategy. Update or Save is permitted for the original data on the
Strategy Save Screen, but if the displayed data is modified, a Save is assumed. The
attempt to save the data under the modified key resulted in an SQL -803 error.
PT555E
NO MATCHING STRATEGY SELECTED FOR COMPARISON.
Reason:
You specified only a single item for comparison or you specified an odd number of items
for comparison.
PT556E
MISMATCHED OBJECT TYPES - CANNOT BE COMPARED.
Reason:
You are trying to compare dissimilar objects. For instance, you may be trying to compare
a tablespace with an index. You can compare only like objects (tablespaces with
tablespaces and indexes with indexes).
PT557E
ERROR DURING COMPARISON DATA RETRIEVE - COMPARISON ABORTED.
Reason:
An I/O or catalog fetch error occurred during comparison data retrieve. This problem
may be caused by DB2 locks on an object your strategy needs, by an Alternate Catalog
Mapping profile, by an I/O error, or by corrupted data.
266 Message Reference Guide (PS to ZLB)
PT Messages
PT558E
INVALID DATA DETECTED DURING RECALCULATION PROCESS.
Reason:
An I/O or catalog fetch error occurred during the recalculation process. The problem
may be caused by DB2 locks on an object your strategy needs, by an Alternate Catalog
Mapping profile, by an I/O error, or by corrupted data.
PT559E
SHAREOPTION PROHIBITS UPDATE.
Reason:
An attempt was made to update a strategy created by another SQLID which is not
defined as updatable. Only shareoption 'U' strategies belonging to other IDs may be
updated.
PT560E
DO NOT USE VOLUME INFORMATION FOR SMS ALLOCATIONS.
Reason:
You specified volume information for an allocation managed by SMS. SMS data set
placement is controlled entirely by SMS, based on MANAGEMENTCLASS,
STORAGECLASS, and DATACLASS parameters established by your storage administrator,
and cannot be modified.
Action:
See your local systems programmer or storage administrator for more information on
your installation's use of SMS.
PT561E
EQF NOT AVAILABLE FOR SQL UNION STATEMENTS. PRESS PF1 FOR HELP.
Reason:
You attempted to invoke the Extended Query Facility (EQF) when the SQL that was to be
executed took the form of a UNION or UNION ALL statement. EQF does not support
such SQL statements, and any modification of the prepared statement causes an SQL
error during the attempt to execute it.
Chapter 2: PS to PTUIX 267
PT Messages
PT562E
YOU ALREADY HAVE AN ACTIVE SPACE CALCULATOR SESSION. PF1 FOR HELP.
Reason:
You attempted to jump to a space calculator session when you already have one active.
PT563E
STOGROUP/VOLUME ALLOCATIONS NOT PERMITTED FOR SMS. PF1 FOR HELP.
Reason:
You attempted to allocate user-defined VSAM data sets under SMS control using
STOGROUP or volume allocation. SMS data set placement is controlled entirely by SMS
based on MANAGEMENTCLASS, STORAGECLASS, and DATACLASS parameters
established by your storage administrator, and cannot be modified.
Action:
See your local systems programmer or storage administrator for more information on
your installation's usage of SMS.
PT564E
STRATEGY NAMES CANNOT BEGIN WITH A BLANK. PRESS PF1 FOR HELP.
Reason:
You attempted to update or save a strategy name containing one or more leading
blanks. Strategy names must begin with an alphabetic character (A-Z) or with $, @, or #.
PT565E
THE LOG MAINTENANCE PLAN NAME WAS NOT FOUND. PRESS PF1 FOR HELP.
Reason:
The plan name for the Log Maintenance Facility was not found in the PLANS parmlib.
Action:
Check with the installer of the products to be sure that the plans member contains the
proper value for PLMPLANS.
268 Message Reference Guide (PS to ZLB)
PT Messages
PT566E
ERROR FETCHING SPREADSHEET CALCULATION DATA. PRESS PF1 FOR HELP.
Reason:
An I/O or catalog fetch error occurred during the process of fetching spreadsheet
calculation data. The problem may be caused by DB2 locks on an object your strategy
needs, by an Alternate Catalog Mapping profile, by an I/O error, or by corrupted data.
PT567E
MISMATCHED OBJECTS SELECTED FOR SPREADSHEET. PRESS PF1 FOR HELP.
Reason:
You selected both index and tablespace objects for an invocation of the Space
Calculation spreadsheet. All objects selected for a spreadsheet session must be of the
same type.
PT568E
ERROR OCCURRED FETCHING DATA FOR EDIT. PRESS PF1 FOR HELP.
Reason:
An error occurred during an attempt to fetch data for a space strategy edit session. The
problem may be caused by DB2 locks on an object your strategy needs, by an Alternate
Catalog Mapping profile, by an I/O error, or by corrupted data.
PT569E
COMPARE/SPREADSHEET NOT SUPPORTED FOR PARTITIONED OBJECTS.
Reason:
You attempted to select a partitioned index or tablespace for a comparison or a
spreadsheet. The Space Calculator does not support such a use of a partitioned object at
this time. Only space strategies, non-partitioned indexes, and simple or segmented
tablespaces may be used as input to a comparison or spreadsheet
PT570E
ALL FIELDS MUST BE FILLED IN. PRESS PF1 FOR HELP.
Reason:
You attempted to save a space strategy with an incomplete or invalid key field. All the
key fields must be filled in for the save to be processed. Blanks are allowed for the
database name and space name, but not for the creator name, strategy name, or the
shareoption.
Chapter 2: PS to PTUIX 269
PT Messages
PT571I
STRATEGY SAVE CANCELED BY REQUEST. NO DATA WAS UPDATED.
Reason:
Indicates that a strategy save was canceled. The original strategy remains unchanged,
and no new strategy has been created.
PT572I
STRATEGY EXISTS AND WILL BE UPDATED IF CONFIRMED WITH ENTER.
Reason:
Indicates that a strategy with the same key as the one displayed on the save screen
already exists. If none of the fields on the save screen are changed, the existing strategy
will be updated. If any of the fields are updated, an attempt will be made to save the
strategy as a new strategy. If another strategy with that same key already exists also, an
SQL error will be encountered.
PT573E
STRATEGY NOT DELETED; ONLY CREATOR MAY DELETE.
Reason:
You are attempting to delete a strategy which was not created by your user ID or your
current SQLID. If you used a different SQLID to create a strategy, you can issue the SET
CURRENT SQLID command to set your SQLID to the strategy creator ID, and deletion will
then be accepted.
PT574E
PRINTLINESIZE AND LINESPERPAGE MUST BE VALID FOR Q/PFILE CMDS.
Reason:
You must complete your PRINTLINE SIZE and the LINES PER PAGE profile variables in
order to use the QFILE or PFILE commands. The Print Parameters Profile screen displays
so that you can complete or correct your profile.
Action:
When you have completed your profile, press PF3 (END) to return to the previous
screen and complete your print request.
270 Message Reference Guide (PS to ZLB)
PT Messages
PT575E
INVALID SIZE ENTERED. PRESS HELP FOR MORE INFO.
Reason:
You entered an invalid value for the SIZE option. This option is used to select the sources
that are to be used for space calculations. The available sources are as follows:
■
P-Use PDA statistics. This requires that PDA be installed on the subsystem.
■
R-Use Runstats. If this option is selected, Runstats should be kept up to date to
avoid B37 abend when running utilities.
■
I-Use Idcams catalog information for space calculations.
If no space statistics are available (for example if the data set has been migrated), a
default size of 10 cylinders will be used.
PT576I
JOB jobname(job_id) WAS SUBMITTED TO JES. PRESS PF1 FOR HELP.
Reason:
Indicates that a batch job with jobname and job_id was submitted to JES for processing.
PT577I
no_of_jobs JOBS WERE SUBMITTED TO JES. FIRST WAS jobname(job_id).
Reason:
Indicates that no_of_jobs batch jobs have been submitted to JES for processing and that
the first job submitted was jobname with job ID of job_id.
PT578I
MODEL SERVICES @DEFAULT MODEL ID IS NOT INSTALLED ON THIS SUBSYSTEM.
Chapter 2: PS to PTUIX 271
PT Messages
PT579I
VALID UNLOAD MODE OPTIONS ARE "A", "U", OR "N"'.
Reason:
This informational message describes the valid options for the unload mode on the
Batch Processor panel. The following options are valid:
■
A- All Batch Processor input is to be executed.
■
U -The section of input containing Unload statements is to be omitted.
■
N-Only the section of input containing Unload statements is to be executed.
This option is intended for use with Batch Processor streams which were created.
PT580I
VALID RESTART OPTIONS ARE "O", “OD”, "N", “Y”, “YD”, number, numberD, or name.
Reason:
This informational message describes the valid options for specifying the RESTART to be
used by the Batch Processor. The following options are valid:
■
O
■
OD
■
N
■
Y
■
YD
■
number
■
numberD
■
name
PT581I
Valid Options are "Y"es or "N"o.
Reason:
A value other than Y or N was entered.
Action:
Enter Y or N.
272 Message Reference Guide (PS to ZLB)
PT Messages
PT582I
ENTER A VALID OUTPUT CLASS.
PT583I
ENTER A VALID JES FORM ID. THIS FIELD IS OPTIONAL.
PT584I
ENTER A VALID JES DESTINATION. THIS FIELD IS OPTIONAL.
PT585E
Option "U"pdate not valid when current is "N"o.
Reason:
The current value for Audit List Dest is N (No), which specifies to not generate an audit
trail. You cannot specify the U option (to update the current setting) when the field is
already set to N.
Action:
Choose one of the following options:
D
Specifies a ddname or data set name in which to save audit output.
P
Prints the audit output.
N
Does not generate an audit output listing.
Chapter 2: PS to PTUIX 273
PT Messages
PT586I
Valid Options are "P"rint, "D"ata set, "N"o or "U"pdate.
Reason:
You need to specify a valid option for the Audit List Dest field (to determine whether
Batch Processor should generate an audit trail list).
Action:
Choose one of the following options:
D
Specifies a ddname or data set name in which to save audit output.
P
Prints the audit output.
N
Does not generate an audit output listing.
U
Updates the current setting. This option is valid only if Print Setting or Dataset
Setting is displayed below the field.
PT587E
YOU HAVE ENTERED MORE DATA THAN THE COLUMN CAN HOLD.
PT588I
DEFAULT VALUES ARE NOT ALLOWED FOR NOT NULL UNIQUE COLUMNS.
PT589E
THIS DECIMAL NUMBER IS INVALID BASED ON THE COLUMN DEFINITION.
PT590E
YOU HAVE ENTERED AN INVALID FLOATING-POINT NUMBER.
Reason:
The floating-point number you entered is invalid. Valid floating-point constants consist
of two numbers separated by an E. The first number can include a sign and a decimal
point, whereas the second number can include only a sign. The number of characters in
the constant cannot be greater than 30. The number of the digits cannot be greater
than 17 in the first number and two in the second. The range of a floating-point number
is approximately +/-7.2E+75 to +/-5.4E-79.
274 Message Reference Guide (PS to ZLB)
PT Messages
PT597I
VALID VALUES ARE "Y"ES OR "N"O. PRESS HELP FOR INFO.
Reason:
This message describes the valid options for specifying the CONTINUE IF LOAD
DISCARDS on the Batch Processor panel. The following options are valid: Y and N.
PT598I
VALID VALUES ARE "Y"ES OR "N"O. PRESS HELP FOR INFO.
Reason:
This message describes the valid options for specifying the CONTINUE IF SQL ERROR on
the Batch Processor panel. The following options are valid: Y and N.
PT599I
VALID VALUES ARE "W"RAP OR "T"RUNCATE. PRESS HELP FOR INFO.
Reason:
This message describes the valid options for specifying the WRAP/TRUNCATE OPTION
on the Batch Processor panel. The following options are valid: W, and T.
PT600E
COMPRESSION RATIO MUST BE NUMERIC.
Reason:
The compression ratio entered is invalid. A valid number is a two-digit number
representing the percentage by which the data in a tablespace is expected to be
reduced as a result of using data compression. It does not matter whether the data
compression is performed by IBM hardware, DB2 itself, or a third party vendor's
compression software.
PT601I
ENTER S, L, OR N. PRESS PF1 FOR HELP.
Action:
Enter one of these valid commands: S, L, or N.
Chapter 2: PS to PTUIX 275
PT Messages
PT602E
ENTER "NONE" OR "CHANGES" FOR DATA CAPTURE.
Reason:
An invalid value has been entered in the Data Capture field. Valid values are as follows:
■
NONE
■
CHANGES
PT603I
DATA SET NOT CATALOGUED - LISTCAT CANCELED.
Reason:
The data set name built for the LISTCAT command is not catalogued. No information is
available about this data set name; therefore the LISTCAT was not produced.
PT604I
DEFAULT VALUES NOT SAVED. NO USERID WAS SUPPLIED.
PT605I
ONLY 255 TABLES MAY BE CONTAINED IN ONE TABLESPACE.
Reason:
You have attempted to include more than 255 tables in a space calculation. Since a
tablespace cannot contain more than 255 tables, this would produce invalid results if it
were attempted. Therefore, the table list has been limited to 255 entries, and the excess
Repeat/Insert commands have been discarded.
PT606E
INVALID COLUMN TYPE OR LENGTH FOR SQLID OR USERID DEFAULT.
Reason:
You have attempted to create a default of SQLID or USERID for a column which is not a
character or varchar column or is not at least 8 bytes in length.
Action:
Consider redefining the column to be of a valid type and length or using a different
default.
276 Message Reference Guide (PS to ZLB)
PT Messages
PT608E
NO MORE THAN ONE OPTION CAN BE SELECTED.
Reason:
More than one option has been selected.
Action:
Select only one option and try again.
PT610E
AN UNEXPECTED INTERNAL ERROR CONDITION HAS OCCURRED. PRESS HELP.
Reason:
An internal processing condition has occurred that was unexpected, undesirable, or
both.
Action:
Report this error to Technical Support. On this message panel, some diagnostic
information might appear. This information should be saved (by screen prints or by
writing it down EXACTLY as shown) and given to Technical Support.
PT611E
INSUFFICIENT VIRTUAL STORAGE TO CONTINUE. PRESS HELP FOR MORE INFO.
Reason:
The product could not obtain enough virtual storage to continue processing your
request.
Action:
Possible solutions to this condition are as follows:
■
Exit any split screen sessions that might be in effect
■
Increase the region size of your TSO LOGON procedure. We recommend a region
size of between 2048 and 3072 KB.
Chapter 2: PS to PTUIX 277
PT Messages
PT612E
AN UNEXPECTED ERROR OCCURRED IN PROCESSING EQF - EQF NOT USED.
Reason:
An error was encountered while processing an Extended Query Facility (EQF) request.
The EQF query will not be used to process your request as it cannot rely on the accuracy
of the query's extension.
PT613E
COLUMN TYPE MUST BE NOT NULL WITH DEFAULT TO SET DEFAULT VALUE.
Reason:
You have attempted to set up a default value for a column that is NOT NULL, NOT NULL
UNIQUE, or not nullable.
Action:
Change the column null indicator to D and you may then enter the default editor.
PT630I
THE CURRENT SSID IS sys.
Reason:
The SHOWSSID command has displayed the current SSID.
PT631E
YOU ALREADY HAVE AN ACTIVE PXF SESSION. PRESS HELP FOR INFO.
Reason:
You have attempted to jump to a product that you are already using.
Action:
You must exit the product you are currently in to get back to the product you desire.
278 Message Reference Guide (PS to ZLB)
PT Messages
PT632I
YOUR ALLOCATION HAS REACHED THE DB2 CEILING OF 4194304.
Reason:
Your space calculation has reached or exceeded the DB2 maximum primary space
allocation of 4,194,304 1K blocks. DB2 will not honor requests for more space than this,
so the Space Calculator will not generate such requests.
Action:
See the IBM DB2 Administration Guide for further details on allocating space for
tablespaces or indexspaces.
PT633I
DB2 DEFAULT VALUES USED FOR PRIQTY AND/OR SECQTY.
Reason:
Indicates that you did not enter or calculate a value for PRIQTY and SECQTY and that the
DB2 default value will be substituted if you do not enter such values before you
complete your processing of the object.
PT634E
CONSTRAINTS MUST BE THE SAME FOR mkey1 AND mkey2.
Reason:
Indicates that you are attempting to create different delete rules that reference the
same column in the parent table. Constraints that reference the same table must use
the same delete rule. One or both of the constraints must be changed to satisfy this DB2
rule.
PT635I
SPACE INFORMATION FOR UNDERLYING VSAM DATASET UNAVAILABLE.
Reason:
This message is an RC/OBJECT message indicating that you are templating or altering a
tablespace or indexspace for which the underlying VSAM data sets have been deleted or
migrated. The message will also be displayed the first time you display the VSAM
definition screen while creating a new tablespace or indexspace. Space information is
not available from the operating system until the underlying VSAM data setS is/are
recalled from migrated status, or given an explicit space allocation on the VSAM
definition screen. Any explicit space allocation given will be accepted and used.
Chapter 2: PS to PTUIX 279
PT Messages
PT636E
VALID LINE COMMANDS ARE S, B AND E. PRESS HELP FOR MORE INFORMATION.
Reason:
Indicates that you have entered an invalid line command.
Action:
Enter S to enter a series of screens that guide you through the parm entries, enter E to
enter an edit session on the member, or enter B to enter a browse session on the
member.
PT637E
PARMLIB READER ERRORS. TYPE STATUS FOR MORE INFORMATION.
Reason:
Indicates that the parmlib editor could not be entered because the parmlib member
could not be read.
PT638E
INVALID LRECL/BLKSIZE/RECFM COMBINATION. PF1 FOR HELP.
Reason:
Indicates that you are attempting to allocate and open for output a data set with
inconsistent or incompatible attributes.
For example, the blocksize may not be an integral multiple of the logical record length
for an F, FB, or FBA record format, or the blocksize minus four might not be larger than
the logical record length for a Vxx record format data set. You must correct the
attributes before the data set can be allocated.
PT639W
ONE OR MORE COLUMNS HAS LENGTH OF ZERO. DDL WILL NOT WORK.
Reason:
Indicates that you have specified a column length of zero for one or more of your table's
columns. This is invalid and will cause an SQL error if you attempt to create or alter your
table without correcting the zero lengths.
280 Message Reference Guide (PS to ZLB)
PT Messages
PT640E
YOU DO NOT HAVE RACF AUTHORITY TO UPDATE PARMLIB.
Reason:
Indicates that an RACF error has occurred. There is a problem processing RACF or you do
not have authority to update CDBAPARM. Return code and reason code refer to return
codes for RACROUTE verify request.
PT641E
A SINGLE PARMLIB DATASET NAME COULD NOT BE DETERMINED.
Reason:
Indicates that there is more than one data set allocated to PTIPARM, and a single data
set name for the parmlib cannot be determined.
PT642E
THE PTIPARM DDNAME COULD NOT BE FOUND. ACCESS DENIED.
Reason:
Indicates that the PTIPARM ddname was not allocated.
Chapter 2: PS to PTUIX 281
PT Messages
PT643E
INVALID OPTIONS SPECIFIED. PRESS HELP FOR MORE INFORMATION.
Reason:
Indicates that you have entered an invalid option.
Action:
Make sure you separate all options by a comma.
Valid format: (opt1, opt2, opt3) where opt1 can be one of the following:
■
Y-May run Online
■
W-May run Online/Issue Warning
■
B-Force to run in Batch
Opt2 can be one of the following:
■
Y-May run without ACM
■
N-Force ACM ON
Opt 3 can be one of the following:
■
Y-May run Online (Catalog List)
■
W-May run Online/Issue Warning (Cat list)
■
C-Cancel run Online (Catalog List)
282 Message Reference Guide (PS to ZLB)
PT Messages
PT644E
INVALID OPTIONS SPECIFIED. PRESS HELP FOR MORE INFORMATION.
Reason:
Indicates that you have entered an invalid option.
Action:
Make sure you separate all options by a comma.
Valid format: (opt1,opt2) where opt1 can be one of the following:
■
Y-May run Online (Generate)
■
W-May run Online/Issue Warning (Generate)
■
C-Cancel run Online (Generate)
opt2 can be one of the following:
■
Y-May run Online (Execute)
■
W-May run Online/Issue Warning (Execute)
■
B-Force to run in Batch (Execute)
PT645I
INFORMATION FOR DB2 SUBSYSTEM sys-id ENTERED, ENTER NEXT SUBSYSTEM.
Reason:
Information for the SECURE member of CDBAPARM has been entered for DB2
subsystem sys-id.
Action:
Do one of the following:
■
Enter information for the next DB2 subsystem to be entered into the SECURE
member, placing a Y or N for the additional subsystems question and then press
enter.
■
Enter N for additional subsystems and press enter to go into edit on the SECURE
member.
■
Enter PF3/End to go into edit on the SECURE member.
Chapter 2: PS to PTUIX 283
PT Messages
PT646I
INFORMATION FOR DB2 SUBSYSTEM sys-id ENTERED, ENTER NEXT SUBSYSTEM.
Reason:
Information for the MIGRATOR member of CDBAPARM has been entered for DB2
subsystem sys-id.
Action:
Do one of the following:
Enter information for the next DB2 subsystem to be entered into the SECURE member,
placing a Y or N for the additional subsystems question and then press enter.
■
Enter N for additional subsystems and press enter to go into edit on the SECURE
member.
■
Enter PF3/End to go into edit on the SECURE member.
PT647I
INFORMATION FOR DICTIONARY ID dict ENTERED.
Reason:
Information for the PIPELINE parmlib member has been entered for Dictionary ID dict.
Action:
Do one of the following:
■
Enter information for the next dictionary ID to be entered into the PIPELINE
member, placing a Y or N for the Multiple Dictionary ID's questions and then press
enter.
■
Enter N for Multiple Dictionary ID's and press enter to go into edit on the PIPELINE
member.
■
Enter PF3/End to go into edit on the PIPELINE member.
284 Message Reference Guide (PS to ZLB)
PT Messages
PT648I
INFORMATION FOR DB2 SUBSYSTEM sys-id ENTERED.
Reason:
Information for the SECURE member of CDBAPARM has been entered for DB2
subsystem sys-id.
Action:
Do one of the following:
■
Enter information for the next DB2 subsystem to be entered into the SECURE
member, placing a Y or N for the additional subsystems question and then press
enter.
■
Enter N for additional subsystems and press enter to go into edit on the SECURE
member.
■
Enter PF3/End to go into edit on the SECURE member.
PT649E
SYNTAX OF RCSADM(S) ENTRIES WAS INCORRECT, ENCRYPTION WAS BYPASSED.
Reason:
The syntax of the RCSADMS was incorrect and encryption had to be bypassed.
Action:
Correct the syntax and retry.
PT650E
UNABLE TO ALLOCATE OR FREE THE TEMP FILE FOR JCL CREATION.
Reason:
The temporary data set used to hold the output of the file tailoring was unable to be
allocated or freed.
Action:
Ensure that you do not have any data sets allocated to the ISPFILE ddname.
Chapter 2: PS to PTUIX 285
PT Messages
PT651E
THE JCL FILE COULD NOT BE EDITED.
Reason:
The temporary data set used to hold the output of the file tailoring was unable to be
edited.
Action:
Ensure that you do not have any data sets allocated to the ISPFILE ddname.
PT652E
ERRORS HAVE OCCURRED PROCESSING THE PARMLIB LOAD MODULE JCL.
Reason:
While trying to process the JCL that creates the load module for the parmlib members,
an error occurred.
Action:
Check to be sure you can create data sets on the volume specified in your profile.
PT653E
INVALID PRINT PROFILE PARAMETERS. CHECK YOUR GLOBAL PROFILE.
Reason:
While trying to process the Q/PPRINT command, the print processor found invalid print
profile parameters.
Action:
Check the global profile print parameters for valid values. Common errors are a print
line size greater than 255 and unspecified print class.
PT654E
INVALID PARM OPTION(S) SPECIFIED. SEE MESSAGE(S) BELOW.
Reason:
Indicates that you have saved the PDA parm member with invalid parm options. The
STATUS panel displays with messages indicating which parm options are invalid. PF3 will
take you back into edit to make the corrections. Without making the corrections the
invalid parm options will be saved and the next time you enter the product PDA, default
values will be used (where applicable) for the parms that have invalid values.
286 Message Reference Guide (PS to ZLB)
PT Messages
PT656E
ENTER ONE OF THE LISTED VALUES.
Reason:
Indicates that you have entered an invalid value in the CA Recovery Analyzer parmlib.
Action:
Enter one of the values that is listed.
PT657E
DATASET NOT PHYSICAL OR PARTITIONED ORGANIZATION.
Reason:
Indicates that the data set you have specified for the output has an invalid organization.
The data set must be partitioned or sequential.
PT658E
VALID LINE COMMAND IS S. B AND E ARE RESERVED FOR PARMLIB MEMBERS.
Reason:
Indicates that when entering a command in the Create a Parmlib Load Module option in
the Edit Parmlib Members screen, you can only enter S. B and E can only be entered in
the parmlib member options.
PT659E
odsn COULD NOT BE BROWSED.
Reason:
Indicates that the data set odsn could not to be browsed.
Action:
You should make sure the data set exists. If it exists, check to see if it is being held with
an exclusive lock.
Chapter 2: PS to PTUIX 287
PT Messages
PT660E
odsn COULD NOT BE EDITED.
Reason:
Indicates that the data set odsn was unable to be edited.
Action:
You should make sure the data set exists. If it exists, check to see if it is being held with
an exclusive lock.
PT661E
FIELDPROC SPECIFIED FOR INVALID COLUMN TYPE. PF1 FOR HELP.
Reason:
Indicates that you have specified a fieldproc for a column that is not a short string
column (CHAR, VARCHAR, GRAPHIC, or VARGRAPHIC), or has a non-null default value
(i.e. does not have a null code of 'Y' on this screen). Fieldprocs are allowed only on
columns with both of these attributes.
PT662E
NO PARM HAS BEEN ENTERED FOR THE PARMLIB FACILITY. PF1 FOR HELP.
Reason:
Indicates that the PLANS parmlib member does not contain an entry for the parmlib
editing facility.
Action:
Check the PLANS member for a fourth plan in the General section. If none exists, enter
Quick Install to refresh the plans parmlib member and rebind the general plans.
PT663I
YOU CANNOT RETURN TO THE PREVIOUS SCREEN FROM THE FIRST SCREEN.
Reason:
Indicates that you cannot use the BACK Command or press PF3 from a product's first
edit parmlib member screen to return to the previous screen. This is only an option
from the screens following the first screen.
288 Message Reference Guide (PS to ZLB)
PT Messages
PT664I
INVALID VALUE. YOU MUST ENTER A VALID VALUE TO CONTINUE.
Reason:
Indicates that you have entered an invalid value.
Action:
You must enter one of the valid values to continue.
PT665I
YOU CANNOT RETURN TO THE PREVIOUS SCREEN FROM THIS SCREEN.
Reason:
Indicates that you cannot use the BACK Command or press PF3 from this screen.
PT666I
YOU SHOULD NOT ENTER INFORMATION FOR THE SAME SSID TWICE.
Reason:
Indicates that when editing the Migrator parmlib, you cannot enter information for the
same SSID twice.
PT667I
YOU SHOULD NOT ENTER INFORMATION FOR THE SAME DICTID TWICE.
Reason:
Indicates that when editing the Pipeline parmlib, you cannot enter information for the
same Dictionary ID twice.
PT668I
REGISTER COPY MUST BE YES WHEN MODIFY BITS IS YES.
Reason:
Indicates that when editing the CA Recovery Analyzer parmlib, the field Register Copy
must be set to YES if the field Modify Bits is set to YES.
Chapter 2: PS to PTUIX 289
PT Messages
PT669E
YOU ALREADY HAVE AN ACTIVE PRI SESSION. PRESS PF1 FOR MORE INFORMATION.
Reason:
You attempted to jump to a product you are already using. You must exit the product
you are currently in to get back to the product you want.
PT670E
THE MAIN PRF MODULE COULD NOT BE FOUND.
PT671I
DATASETS HAVE BEEN RECALLED/MIGRATED.
PT672E
HRECALL/HMIGRATE FAILED WITH RETURN CODE return_code.
PT680E
THE DATASET NAME AT THE CURSOR COULD NOT BE FOUND.
PT682E
UNABLE TO ALLOCATE fixvrtzn.
PT683E
UNABLE TO ALLOCATE fixvrdzn.
PT684E
UNABLE TO OPEN fixvrtzn.
PT685E
UNABLE TO OPEN fixvrdzn.
PT686E
UNABLE TO DEALLOCATE fixvrtzn.
PT687E
UNABLE TO DEALLOCATE fixvrdzn.
290 Message Reference Guide (PS to ZLB)
PT Messages
PT688I
SECONDARY IDS NOT USED. PRESS HELP FOR INFO. RC = return_code
Reason:
Secondary IDs for the function you are performing could not be determined for the
reason given.
Action:
If you have not set up secondary IDs for authorization you do not need them and may
ignore this message. However, if you require the secondary IDs for proper access, report
this error to your administrator.
PT691E
INVALID PRIMARY COMMAND HAS BEEN ENTERED. ENTER ? FOR A VALID LIST.
Reason:
You have entered an invalid primary command.
Action:
To see a list of the valid primary commands, enter '?' on the command line. Valid
primary commands can be selected from this list.
PT692E
AN UNEXPECTED INTERNAL ERROR HAS OCCURRED. PRESS HELP.
Reason:
A condition has occurred within Alternate Catalog Mapping shadow table creation that
was not expected to happen and cannot be handled correctly.
Action:
Press PF1 for help information.
Chapter 2: PS to PTUIX 291
PT Messages
PT693E
UNABLE TO ALLOCATE odsn.
Reason:
The data set listed was unable to be allocated.
Action:
Ensure that the data set exists. If it exists, check to see if it is being held with an
exclusive lock.
PT694E
UNABLE TO DEALLOCATE odsn.
Reason:
The data set listed was not able to be deallocated.
PT695I
ENTER SUBMIT TO EXECUTE THE JOB.
Action:
Enter SUBMIT to execute the job. Wait for the execution of this job to complete before
executing the next step.
PT696E
FILE odsn COULD NOT BE EDITED.
Reason:
The data set listed was unable to be edited.
Action:
Ensure that the data set exists. If it exists, check to see if it is being held with an
exclusive lock.
292 Message Reference Guide (PS to ZLB)
PT Messages
PT697E
IDCAMS LISCAT LEVEL (sys) NOT FOUND.
Reason:
The data set odsn was unable to be allocated.
Action:
Ensure the data set exists. If it exists, check to see if it is being held with an exclusive
lock.
PT700W
CONVERTING FROM TYPE 2 TO TYPE 1 CAN CAUSE ERRORS.
Reason:
Converting an index from Type 2 to Type 1 can cause problems if the tablespace
containing the table on which the index is built was created with row level locking. If this
is the case, the conversion will fail and an SQL error will be returned. If you are sure row
level locking does not exist in the table's tablespace, the conversion should take place
without causing any problem.
PT701I
ANALYZER SESSION IS ALREADY ACTIVE, PRESS PF1 FOR MORE INFORMATION.
Reason:
You have attempted to jump to a product that you are already using.
Action:
To access that product, you must exit the product you are currently in.
PT710I
ENTER A VALID RC/M STRATEGY NAME.
Action:
Enter the name of the strategy name associated with this input table.
PT711I
ENTER THE CREATOR OF THE RC/M STRATEGY.
Action:
Enter the user ID that created the strategy.
Chapter 2: PS to PTUIX 293
PT Messages
PT712I
ENTER THE USER ID OF THE RC/M ANALYSIS.
Action:
Enter the user ID that analyzed the strategy.
PT713I
ENTER THE DATE OF THE RC/M ANALYSIS.
Action:
Enter the date on which the analysis was run.
PT714I
ENTER THE TIME OF THE RC/M ANALYSIS.
Action:
Enter the time at which with analysis was run.
PT715I
INPUT DDL CANNOT BE FOUND OR NO LONGER EXISTS.
The RC/M managed DDL or Recovery analysis output you have specified to be used as
input to the Batch Processor no longer exists or could be found.
PT716I
INVALID LINE COMMAND.
Reason:
You have entered an invalid command.
Action:
You can enter a question mark (?) in any command line to display a list of valid
commands.
294 Message Reference Guide (PS to ZLB)
PT Messages
PT717E
INVALID COLUMN DEFAULT IND. SPECIFIED. PRESS HELP FOR INFO.
Reason:
This indicates that you have specified an invalid default COLUMN DEFAULT INDICATOR.
Valid values are as follows:
■
C
■
N
■
S
■
U
■
Y
■
blank
PT718I
COLUMN NULL INDICATOR ''D'' HAS BEEN CONVERTED. PRESS HELP FOR INFO.
Reason:
This message is informing you that the Object Definition Defaults for this ID had the
default COLUMN NULL INDICATOR set to D, which is no longer supported. It was
translated to an equivalent specification using the COLUMN NULL INDICATOR and the
new COLUMN DEFAULT IND. fields.
Note: Valid values for the COLUMN NULL INDICATOR are Y or N.
Action:
In future when you want to specify NOT NULL WITH DEFAULT, do so by specifying a
COLUMN NULL INDICATOR value of N and a COLUMN DEFAULT IND. value of Y (the N
and D columns, respectively, on the Table Alt or Table Create screens). This is equivalent
to specifying the old D COLUMN NULL INDICATOR. This is the translation that has been
done automatically for you. To prevent this message from appearing in the future, go to
Object Definition Defaults (if you are not already there) and save the current defaults by
specifying an Action of S. The COLUMN NULL INDICATOR and COLUMN DEFAULT IND.
fields are already filled in, so there is nothing else that you need to do on the screen.
Chapter 2: PS to PTUIX 295
PT Messages
PT719E
COLUMN NULL INDICATOR OF ''D'' IS NO LONGER SUPPORTED. HELP FOR INFO.
Reason:
This message is informing you that a COLUMN NULL INDICATOR value of D is no longer
supported. Valid values are as follows: Y or N.
Action:
If you wish to specify NOT NULL WITH DEFAULT, as you may have done in an older
release of the product which supported the D value, you may still do so by specifying a
COLUMN NULL INDICATOR value of N and a COLUMN DEFAULT value of Y. This
combination is equivalent to specifying the old D COLUMN NULL INDICATOR.
PT720I
COLUMN NULL INDICATOR ''D'' HAS BEEN TRANSLATED. HELP FOR INFO.
Reason:
This message is informing you that you entered a Column Null Indicator of D (in the N
column) on the Table Alter or Table Create screens, and this value is no longer
supported. However, it was translated to an equivalent specification using the Column
Null Indicator and the new Column Default Indicator (the N and D columns,
respectively). Valid Column Null Indicators are now: Y or N.
Action:
In the future, when you wish to specify NOT NULL WITH DEFAULT, you may do so by
specifying a Column Null Indicator of N and a Column Default Indicator of Y, which is
equivalent to specifying the old D Column Null Indicator.
PT721E
COLUMN NULL AND COLUMN DEFAULT INDICATORS MAY NOT BOTH BE ''N''.
Reason:
You specified a value of N for both the Column Null and Column Default Indicators, and
this combination is not valid. Specifying N for both the Column Null and Column Default
Indicators is equivalent to indicating that both the NOT NULL and DEFAULT NULL clauses
be used in your create and/or alter DDL; however, these two clauses are mutually
exclusive and may not be specified together.
296 Message Reference Guide (PS to ZLB)
PT Messages
PT722W
OBJ DEF DEFAULTS INCOMPATIBLE WITH V3.1 OBJ: USING STANDARD DEFAULTS.
Reason:
The Object Definition Defaults for your userid are incompatible with the object that you
are creating or altering, because the defaults are for a later version of DB2. Standard
defaults that are compatible with the object's current version of DB2 will be used
instead.
PT723I
OBJECT'S OLD COLUMN NULL INDICATOR OF ''D'' HAS BEEN TRANSLATED.
Reason:
The object's old Column Null Indicator of D, which showed in the N column on the Table
Alter or Table Create screens in earlier releases of the product, is no longer supported. It
has been translated to an equivalent specification using the Column Null Indicator and
the new Column Default Indicator (the N and D columns, respectively). Valid Column
Null Indicators are now: Y or N.
Action:
In the future, when you wish to specify NOT NULL WITH DEFAULT, you may do so by
specifying a Column Null Indicator of N and a Column Default Indicator of Y, which is
equivalent to specifying the old D Column Null Indicator.
PT725E
Valid assembler names are ASMA90 AND IEV90.
Action:
You must enter one of the valid assembler names to ensure a correct assembler was
used to build the JCL.
PT743E
MODULE module_name IS NOT AN APF AUTHORIZED LIBRARY MODULE
Reason:
The named module is invoking PTLTSRB from a non-APF authorized library. The request
is terminated.
Chapter 2: PS to PTUIX 297
PT Messages
PT752E
PTLTSRB CSVQUERY SERVICE ERROR RC: return_code RSN: reason_code
Reason:
An internal error has occurred in module PTLTSRB.
PT753E
PTLTSRB ENTERED VIA UN-AUTHORIZED PATH: RC: return_code RSN: reason_code
Reason:
An unexpected calling sequence has been detected.
PT756W
One or more truncated objects have been suppressed.
Reason:
The CA DB2 product you are using has encountered one or more retrieved rows that
contain one or more columns whose values were truncated. These rows have been
suppressed from the panel that you are viewing.
The truncation most likely has occurred as a result of a DB2 object that has been defined
exploiting long value functionality present starting in DB2 V8. The product you are using
is not fully long value exploitive, so the object was suppressed from the report.
PT757W
One or more truncated objects are present.
Reason:
The CA DB2 product you are using has encountered one or more rows that were
retrieved that contained one or more columns whose values were truncated. These
rows have been suppressed from the panel that you are viewing.
The truncation typically occurs due to a DB2 object that has been defined exploiting
long value functionality present starting in DB2 V8. The product you are using is not fully
long value exploitive, so one or more values associated with the object has a truncated
value, and whose full value you cannot see.
PT758E
PTLTSRB - module_name not in AUTH table: RC: return_code RSN: reason_code
Reason:
PTLTSRB has been requested to link to an unauthorized program.
298 Message Reference Guide (PS to ZLB)
PT Messages
PT759E
PTLTSRB invoked NON-authorized: RC: return_code RSN: reason_code
Reason:
PTLTSRB has been invoked non-authorized.
Action:
Ensure that PTLTSRB was linked AC(1).
PT77054E
Cannot Connect to DB2:
Reason:
Connection to the subsystem specified in the message was not successful and execution
terminates.
Action:
Ensure the subsystem-ID is valid and active. Ensure DSNREXX modules delivered by IBM
exist and have been bound for the specific subsystem.
PT77092E
MSGFILE missing in JCL - terminating execution
Reason:
The MSGFILE DD statement could not be found in the JCL.
Action:
Ensure that MSGFILE is allocated in the JCL. It can be allocated to SYSOUT or it can be a
sequential file with RECL=133 and fixed blocked.
PT77400I
No PLAN_TABLES to convert
Reason:
This is an informational message indicating no PLAN_TABLES were found in the specified
DB2 subsystem, even though the input parameter specifies that this explain type should
be converted.
Chapter 2: PS to PTUIX 299
PT Messages
PT77401I
No DSN_STATEMNT_TABLEs to convert
Reason:
This is an informational message indicating no DSN_STATEMNT_TABLES were found in
the specified DB2 subsystem, even though the input parameter specifies that this
explain table type should be converted.
PT77402I
No DSN_FUNCTION_TABLEs to convert
Reason:
This is an informational message indicating no DSN_FUNCTION_TABLES were found in
the specified DB2 subsystem, even though the input parameter specifies that this
explain table type should be converted.
PT77403E
RBPFILE missing in JCL-terminating execution
Reason:
The RBPFILE DD statement could not be found in the JCL.
Action:
Ensure that RBPFILE is allocated in the JCL. This JCL is created using the EC option under
the Value Pack component on the Main Menu. The data set attributes are as follows:
DCB=(LRECL=80,RECFM=FB,BLKSIZE=6160).
Use the EC option on the main menu to generate the JCL.
PT77404E
EXPPARM DD is empty - terminating execution
Reason:
The data set allocated to EXPPARM DD in the JCL is empty.
This data set is created when using the EC option from the Value Pack component on
the main menu.
Action:
Use this option to re-enter the parameters before submitting the JCL.
300 Message Reference Guide (PS to ZLB)
PT Messages
PT77405E
First input variable must be DB2ID (ssid)
Reason:
The first parameter in the data set allocated to EXPPARM DD must be DB2ID (ssid),
where ssid is the subsystem-id in which explain tables are going to be converted.
PT77406E
Invalid syntax for DB2ID parameter
Reason:
The DB2ID parameter in the data set allocated to EXPPARM DD in the JCL is invalid.
The first parameter in the data set allocated to EXPPARM DD must be DB2ID (ssid),
where ssid is the subsystem-id in which explain tables are going to be converted.
PT77407I
Connecting to DB2: db2_subsystem
Reason:
This is an informational message indicating the DB2 subsystem which the batch job is
connecting to in order to convert explain tables.
PT77408E
EXPPARM DD missing PLAN_TABLE_CONV parameter
Reason:
The PLAN_TABLE_CONV parameter in the data set allocated to EXPPARM DD in the JCL
is missing.
The second parameter in the data set allocated to EXPPARM DD must be
PLAN_TABLE_CONV (x), where x is Y (PLAN_TABLEs are to be converted) or N
(PLAN_TABLES are not to be converted). This data set is created using the EC option
under the Value Pack component from the main menu.
Chapter 2: PS to PTUIX 301
PT Messages
PT77409E
Invalid syntax for PLAN_TABLE_CONV parameter
Reason:
The PLAN_TABLE_CONV parameter in the data set allocated to EXPPARM DD in the JCL
is invalid.
The second parameter in the data set allocated to EXPPARM DD must be
PLAN_TABLE_CONV (x), where x is Y (PLAN_TABLES are to be converted) or N
(PLAN_TABLES are not to be converted). This data set is created using the EC option
under the Value Pack component from the main menu.
PT77410E
EXPPARM DD missing DSN_STATEMNT_CONV parameter
Reason:
The DSN_STATEMNT_CONV parameter in the data set allocated to EXPPARM DD in the
JCL is missing.
The third parameter in the data set allocated to EXPPARM DD must be
DSN_STATEMNT_CONV (x), where x is Y (DSN_STATEMNT_CONV is to be converted) or
N (DSN_STATEMNT_CONV is not to be converted). This data set is created using the EC
option under the Value Pack component from the main menu.
PT77411E
Invalid syntax for DSN_STATEMNT_CONV parameter
Reason:
The DSN_STATEMNT_CONV parameter in the data set allocated to EXPPARM DD in the
JCL is invalid.
The third parameter in the data set allocated to EXPPARM DD must be
DSN_STATEMNT_CONV (x), where x is Y (DSN_STATEMNT_CONV is to be converted) or
N (DSN_STATEMNT_CONV is not to be converted). This data set is created using the EC
option under the Value Pack component from the main menu.
302 Message Reference Guide (PS to ZLB)
PT Messages
PT77412E
EXPPARM DD missing DSN_FUNCTION_CONV parameter
Reason:
The DSN_FUNCTION_CONV parameter in the data set allocated to EXPPARM DD in the
JCL is missing.
The third parameter in the data set allocated to EXPPARM DD must be
DSN_FUNCTION_CONV (x), where x is Y (DSN_FUNCTION_CONV is to be converted) or N
(DSN_FUNCTION_CONV is not to be converted). This data set is created using the EC
option under the Value Pack component from the main menu.
PT77413E
Invalid syntax for DSN_FUNCTION_CONV parameter
Reason:
The DSN_FUNCTION_CONV parameter in the data set allocated to EXPPARM DD in the
JCL is invalid.
The fourth parameter in the data set allocated to EXPPARM DD must be
DSN_FUNCTION_CONV (x), where x is Y (DSN_FUNCTION_CONV is to be converted) or N
(DSN_FUNCTION_CONV is not to be converted). This data set is created using the EC
option under the Value Pack component from the main menu.
PT77414E
DB2 error for CURSOR C8 get Explain tables
Reason:
An unpredictable error occurred trying to access the DB2 catalog to retrieve information
for the explain tables to be converted.
Action:
Check the job output; it includes information about the SQLCODE and the reason for the
display of this message.
PT77415I
No tables found to convert:
Reason:
This is an informational message indicating that no explain tables of the type listed were
found on the DB2 subsystem.
Chapter 2: PS to PTUIX 303
PT Messages
PT77416I
No new columns for:
Reason:
This is an informational message indicating that the table listed will have no ALTER
TABLE statements generated because the table already has the format matching the
master table used as the skeleton.
PT77417I
Table will get new columns:
Reason:
This is an informational message indicating that the table listed will have ALTER TABLE
ADD COLUMNs generated.
PT77418W
Invalid table - ROLLBACK created:
Reason:
The table listed in this message cannot be converted using ALTER TABLE ALTER
COLUMN. A ROLLBACK statement was generated after the ALTER TABLE statements.
This message is preceded with at least one additional message detailing the reason for
the ALTER STATEMENTs to be invalid.
PT77419W
Mismatch column sequence
Reason:
This is a warning message indicating an explain table was found in the DB2 catalog in
which the column sequence does not match the standard explain table or a colum is
missing.
The table listed on the output cannot be conhverted using ALTER statements. You will
have to convert it manually to match DB2 V8 format.
304 Message Reference Guide (PS to ZLB)
PT Messages
PT77420W
column number
Reason:
This is a warning message specifying the column for the table specified in message
PT77419W that does not match the standard format.
The table listed on the output cannot be converted using ALTER statements. You will
have to convert it manually to match DB2 V8 format.
PT77421E
DB2 error CURSOR C8 GET table details
Reason:
An unpredictable error occurred trying to access the DB2 catalog to retrieve information
for the explain tables to be converted.
Action:
Please check the job output, which includes information about the SQLCODE and the
reason that this message displayed.
PT77422I
Table will get columns altered:
Reason:
This is an informational message indicating that the table listed will have columns
altered to match the most current format.
PT77423W
The ALTER statements will fail for the following table
Reason:
This message is accompanied by PT77434W and PT77424W and describes the database
and tablespace being referred to in these messages.
These three messages warn you that the specified tablespace has to be altered to use a
bigger buffer pool in order for the ALTER TABLE ALTER COLUMN statements to be
executable. The reason is the rowlength for a table residing in this tablespace will
increase beyond what the current allocated buffer pool can hold.
Before the ALTER statements generated can be executed, this tablespace must be
dropped and created with a bigger buffer pool.
Chapter 2: PS to PTUIX 305
PT Messages
PT77424W
Unless the tablespace is allocated to a bigger BP
Reason:
This message is accompanied by PT77423W and PT77434W and describes the database
and tablespace being referred to in these messages.
These three messages warn you that the specified tablespace has to be altered to use a
bigger buffer pool for the ALTER TABLE ALTER COLUMN statements to be executable.
The reason is the rowlength for a table residing in this tablespace will increase beyond
what the current allocated buffer pool can hold.
Before the ALTER statements generated can be executed, this tablespace must be
dropped and created with a bigger buffer pool.
PT77425E
EXPPARM DD missing ALL_CREATORS parameter
Reason:
The ALL_CREATORS parameter in the data set allocated to EXPPARM DD in the JCL is
missing.
The fifth parameter in the data set allocated to EXPPARM DD must be ALL_CREATORS
(x), where x is Y or N depending on whether all the explain tables found (based on
PLAN_TABLE_CONV, DSN_STATEMNT_CONV and DSN_FUNCTION_CONV parameters)
are going to be converted or only for a specific CREATOR. This data set is created using
the EC option under the Value Pack component from the main menu.
PT77426E
Invalid syntax for ALL_CREATORS parameter
Reason:
The ALL_CREATORS parameter in the data set allocated to EXPPARM DD in the JCL is
invalid.
The fifth parameter in the data set allocated to EXPPARM DD must be ALL_CREATORS
(x), where x is Y or N depending on whether all the explain tables found (based on
PLAN_TABLE_CONV, DSN_STATEMNT_CONV and DSN_FUNCTION_CONV parameters)
are going to be converted or only for a specific CREATOR. This data set is created using
the EC option under the Value Pack component from the main menu.
306 Message Reference Guide (PS to ZLB)
PT Messages
PT77427E
EXPPARM DD missing CONVERT_CREATOR parameter
Reason:
The CONVERT_CREATORS parameter in the data set allocated to EXPPARM DD in the JCL
is missing.
The sixth parameter in the data set allocated to EXPPARM DD must be ALL_CREATORS
(x), where x is Y or N depending on whether all the explain tables found (based on
PLAN_TABLE_CONV, DSN_STATEMNT_CONV and DSN_FUNCTION_CONV parameters)
are going to be converted or only for a specific CREATOR. This data set is created using
the EC option under the Value Pack component from the main menu.
PT77428E
Invalid syntax for CONVERT_CREATOR parameter
Reason:
The CONVERT_CREATORS parameter in the data set allocated to EXPPARM DD in the JCL
is invalid.
The sixth parameter in the data set allocated to EXPPARM DD must be ALL_CREATORS
(x), where x is Y or N depending on whether all the explain tables found (based on
PLAN_TABLE_CONV, DSN_STATEMNT_CONV and DSN_FUNCTION_CONV parameters)
are going to be converted or only for a specific CREATOR. This data set is created using
the EC option under the Value Pack component from the main menu.
Chapter 2: PS to PTUIX 307
PT Messages
PT77429E
EXPPARM DD missing DB2_CREATOR parameter
Reason:
The DB2_CREATOR parameter in the data set allocated to EXPPARM DD in the JCL is
missing.
The seventh parameter in the data set allocated to EXPPARM DD must be
DB2_CREATOR (base-creator), where base-creator is the creator of the three explain
tables having the most recent changes for the specific DB2 version. These tables are
typically created as part of the DB2 install or upgrade.
The explain tables are as follows:
■
PLAN_TABLE
■
DSN_STATEMNT_TABLE
■
DSN_FUNCTION_TABLE
This parameter is used to find the definition of these tables, which are then used to
convert existing tables to have the same look. The data set holding this parameter is
created using the EC option under the Value Pack component from the main menu.
PT77430E
Invalid syntax for DB2_CREATOR parameter
Reason:
The DB2_CREATOR parameter in the data set allocated to EXPPARM DD in the JCL is
missing.
The seventh parameter in the data set allocated to EXPPARM DD must be
DB2_CREATOR (base-creator), where base-creator is the creator of the three explain
tables having the most recent changes for the specific DB2 version. These tables are
typically created as part of the DB2 install or upgrade.
The explain tables are as follows:
■
PLAN_TABLE
■
DSN_STATEMNT_TABLE
■
DSN_FUNCTION_TABLE
This parameter is used to find the definition of these tables, which then are used to
convert existing tables to have the same look. The data set holding this parameter is
created using the EC option under the Value Pack component from the main menu.
308 Message Reference Guide (PS to ZLB)
PT Messages
PT77431E
Valid values for PLAN_TABLE_CONV is Y or N
Reason:
The PLAN_TABLE_CONV parameter in the data set allocated to EXPPARM DD in the JCL
is invalid. The only valid values are Y or N.
The second parameter in the data set allocated to EXPPARM DD must be
PLAN_TABLE_CONV (x), where x is Y or N depending on whether PLAN_TABLEs are going
to be converted. This data set is created using the EC option under the Value Pack
component from the main menu.
PT77432E
Valid values for DSN_STATEMNT_CONV is Y or N
Reason:
The DSN_STATEMNT_CONV parameter in the data set allocated to EXPPARM DD in the
JCL is invalid. Valid values are Y or N.
The third parameter in the data set allocated to EXPPARM DD must be
DSN_STATEMNT_CONV (x), where x is Y or N depending on whether
DSN_STATEMNT_TABLEs are going to be converted. This data set is created using the EC
option under the Value Pack component from the main menu.
PT77433E
Valid values for DSN_FUNCTION_CONV is Y or N
Reason:
The DSN_FUNCTION_CONV parameter in the data set allocated to EXPPARM DD in the
JCL is invalid. Valid values are Y or N.
The fourth parameter in the data set allocated to EXPPARM DD must be
DSN_FUNCTION_CONV (x), where x is Y or N depending on whether
DSN_FUNCTION_TABLEs are going to be converted. This data set is created using the EC
option under the Value Pack component from the main menu.
Chapter 2: PS to PTUIX 309
PT Messages
PT77434W
DB.TS = databasename.tablespacename
Reason:
This message is accompanied by PT77423W and PT77424W and describes the database
and tablespace being referred to in these messages.
These three messages warn you that the specified tablespace has to be altered to use a
bigger buffer pool for the ALTER TABLE ALTER COLUMN statements to be executable.
The reason is the rowlength for a table residing in this tablespace will increase beyond
what the current allocated buffer pool can hold.
Before the ALTER statements generated can be executed, this tablespace must be
dropped and created with a bigger buffer pool.
PT77435E
Valid values for ALL_CREATORS is Y or N
Reason:
The ALL_CREATORS parameter in the data set allocated to EXPPARM DD in the JCL is
invalid. Valid values are Y or N.
The fifth parameter in the data set allocated to EXPPARM DD must be ALL_CREATORS
(x), where x is Y or N depending on whether all the explain tables found (based on
PLAN_TABLE_CONV, DSN_STATEMNT_CONV and DSN_FUNCTION_CONV parameters)
are going to be converted or only for a specific CREATOR. This data set is created using
the EC option under the Value Pack component from the main menu.
310 Message Reference Guide (PS to ZLB)
PT Messages
PT77436E
Specify an existing creator for explain tables.
Reason:
The DB2_CREATOR parameter in the data set allocated to EXPPARM DD in the JCL is
invalid. The creator specified in the parenthesis must be an existing creator for the
explain tables having the most current format
The seventh parameter in the data set allocated to EXPPARM DD must be
DB2_CREATOR (base-creator), where base-creator is the creator of the three explain
tables having the most recent changes for the specific DB2 version. These tables are
typically created as part of the DB2 install or upgrade.
The explain tables are as follows:
■
PLAN_TABLE
■
DSN_STATEMNT_TABLE
■
DSN_FUNCTION_TABLE
This parameter is used to find the definition of these tables, which then are used to
convert existing tables to have the same look. The data set holding this parameter is
created using the EC option under the Value Pack component from the main menu.
PT77437E
All explain tables are set to not to be converted.
Reason:
All the following three parameters in the data set allocated to EXPPARM DD in the JCL
are set to N :
■
PLAN_TABLE_CONV
■
DSN_STATEMNT_CONV
■
DSN_FUNCTION_CONV
Action:
At least one of the parameters must be set to Y; otherwise there are no tables to check
for conversion to the most current definition.
Chapter 2: PS to PTUIX 311
PT Messages
PT77438E
Creator must be specified for CONVERT_CREATOR
Reason:
ALL_CREATORS (N) has been specified in the data set allocated to EXPPARM DD in the
JCL, but the content of CONVERT_CREATOR parameter is empty.
ALL_CREATORS (N) is specified, meaning not all the existing explain tables in the DB2
subsystem are going to be converted. This means a CREATOR must be specified in the
CONVERT_CREATOR parameter to illustrate WHICH explain table creator must be
converted.
PT77439E
DB2 error for CURSOR C9 checking bufferpool
Reason:
An unpredictable error occurred trying to access the DB2 catalog to retrieve information
about the currently allocated bufferpool for the explain table being converted to the
most current format.
Action:
Please check the job output, which holds information about the SQLCODE and the
reason that this message displayed.
PT77440E
DB2 error for CURSOR C7 get DB2 Master table
Reason:
An unpredictable error occurred trying to access the DB2 catalog to retrieve information
for the master explain tables to be used as the skeleton for the conversion.
Action:
Please check the job output, which holds information about the SQLCODE and the
reason that this message displayed.
312 Message Reference Guide (PS to ZLB)
PT Messages
PT77441E
Alter not possible - existing column bigger:
Reason:
The column listed in this message for the specific table is larger than the corresponding
column from the explain table to which it is being compared.
The generated ALTER TABLE ALTER COLUMN statement cannot be executed because
DB2 ALTER does not allow a column to be decreased in size. SQL comment symbols will
be placed for the generated ALTER statement and a ROLLBACK statement will be
generated.
PT77442E
Table does not have minimum number of columns:
Reason:
The explain table listed in this message has fewer columns than the minimum
requirement described in the IBM documentation.
The minimum number of columns for the explain tables as described in the IBM DB2
documentation are as follows:
■
For the PLAN_TABLE, the minimum number of columns is 25
■
For the DSN_STATEMNT_TABLE, the minimum number of columns is 11
■
For the DSN_FUNCTION_TABLE, the minimum number of columns is 15
Because you must define these columns as NOT NULL, you cannot use alter statements
to add them to the table. Any ALTER statements generated to this table are proceeded
with a ROLLBACK, but processing continues.
PT77443E
Table has too many columns compared to master:
Reason:
The explain table listed in this message has more columns compared to the master
specified by the DB2_CREATOR parameter in the data set allocated to EXPPARM.
Any ALTER statements generated for this table are proceeded with a ROLLBACK
statements, because the table will be invalid for explain if the ALTER's were carried out.
Processing continues.
Chapter 2: PS to PTUIX 313
PT Messages
PT77444E
EXPPARM DD missing DB2VERSION parameter
Reason:
The DB2VERSION parameter in the data set allocated to EXPPARM DD in the JCL is
missing.
The eigth parameter in the data set allocated to EXPPARM DD must be DB2VERSION (x),
where x is a DB2 version number (currently only V8 is supported). This parameter
describes to which DB2 version the explain tables are being converted to. This data set is
created using the EC option under the Value Pack component from the main menu.
PT77444W
Error reading parmlib
Reason:
The parmlib data set could not be found allocated to PTIPARM in the JCL. Execution will
terminate.
Action:
Ensure PTIPARM has the correct high-level.CDBAPARM allocated.
PT77445E
Invalid syntax for DB2VERSION parameter
Reason:
The DB2VERSION parameter in the data set allocated to EXPPARM DD in the JCL is
invalid.
The eigth parameter in the data set allocated to EXPPARM DD must be DB2VERSION (x),
where x is a DB2 version number (currently only V8 is supported). This parameter
describes to which DB2 version the explain tables are being converted to. This data set is
created using the EC option under the Value Pack component from the main menu.
314 Message Reference Guide (PS to ZLB)
PT Messages
PT77446E
Currently only DB2 V8 conversion supported.
Reason:
An invalid value was specified for DB2VERSION parameter in the data set allocated to
EXPPARM DD in the JCL
Currently the only valid parameter is (08). This parameter describes to which DB2
version the explain tables are being converted. This data set is created using the EC
option under the Value Pack component from the main menu.
PT800E
An internal error occurred. Error information:
servname,00,servtype,calladdr,statcode,reason01,reason02
Reason:
An internal error has occurred. Error information follows:
servname
Specifies the name of the service routine that failed.
servtype
Specifies the type of service provided by the service routine.
calladdr
Specifies the address in hexadecimal of the instruction that follows the call to the
service routine.
statcode
Specifies the status code in hexadecimal of the service routine.
reason01
Specifies the primary reason code in hexadecimal.
reason02
Specifies the secondary reason code in hexadecimal.
This message is issued when a service routine fails and provides information of interest
to CA Technical Support. A dump is also generated if a SYSUDUMP or SYSMDUMP data
set is provided.
Chapter 2: PS to PTUIX 315
PT Messages
PT804E
MAKETAB facility is not available on DB2 Version 10.
Reason:
The MAKETAB facility is not available for creating alternate catalog mapping (ACM)
shadow tables and indexes and loading the shadow tables on DB2 10.
Action:
Create and upload the shadow tables outside of the MAKETAB facility.
PT860E
Requested Object Not Found. If ACM = Y, system catalog accessed.
Reason:
The object you specified was not found. If ACM is in use, note that the
LBIND/LREBIND/LFREE command does not support ACM. The system catalog may not
contain the object.
PT864E
Enter a value for the replaceable parameter
Reason:
Indicates that a runtime value is needed for a replaceable parameter in an extended
selection or data query WHERE condition. A maximum number of up to 255 characters
may be entered. You can view the extended selection or data query by entering the SQL
primary command.
PT865E
Invalid row limit entered - must be blank or 1-99999999.
Reason:
The Row Limit value entered is not valid.
Row Limit can be blank or a number from 1 to 99999999. If blank, no row limit is used.
316 Message Reference Guide (PS to ZLB)
PT Messages
PT870E
Batch Processor has completed with errors.
Reason:
The PT870E message informs you that although the Batch Processor has completed,
errors were present.
Action:
Review the JESYSMSG output for additional error messages which may be present.
PT880E
Invalid characters in data set name. The data set name must include only national
characters (A-Z, 0-9, @, #, $). Be sure you have not entered the name in quotes or
specified a member name.
Reason:
Indicates that invalid characters have been specified in the Batch Processor audit file
data set field.
Action:
The following rules must be used when specifying the data set name:
■
Use only national characters (A-Z, 0-9, @, #, $)
■
Do not enclose in quotes or include a member name
Correct the data set name and retry the request.
PT881I
Batch processor request is cancelled.
Reason:
Indicates that the Batch Processor request was cancelled.
Action:
None. This message is informational.
Chapter 2: PS to PTUIX 317
PT Messages
PT882W
Jump command is ignored from this panel.
Reason:
Indicates that a jump command was entered; however, it is not valid on the panel
where it was entered. This can occur on a popup window where you are specifying
additional information about a request.
Action:
Specify Enter or Cancel instead of jump.
PT883E
Only one of DDNAME and data set name can be specified.
Reason:
Indicates that a ddname and a data set name were specified in the Batch Processor
interface on the Audit List Data Set Options panel. Only one of the choices (ddname or
data set name) is supported.
Action:
Remove one of the two fields and retry the request.
PT884E
One of DDNAME or data set name must be specified. Enter either the DDNAME or the
name of an existing, cataloged data set.
Reason:
Indicates that the ddname and data set name field are empty on the Batch Processor
interface Audit List Data Set Options panel. One of these values is required.
Action:
Specify only one of the two fields and retry the request.
318 Message Reference Guide (PS to ZLB)
PT Messages
PT885E
The DDNAME specified is an invalid name.
Reason:
Indicates that the ddname specified on the Batch Processor interface Audit List
Data Set Options panel is invalid. The ddname must be one- to eight- national characters
(A-Z, 0-9, @, # and $).
Action:
Correct the ddname and retry the request.
PT886E
The data set name specified is an invalid name.
Reason:
Indicates that the format of the data set name specified on the Batch Processor
interface Audit List Data Set Options panel is invalid. The following rules must be
followed:
■
The name must be one- to -eight national characters (A-Z, 0-9, @, #, $) and can
include periods (.).
■
The maximum length is 44 characters.
■
The name must not be enclosed within apostrophes and must not include a
member name.
Action:
Correct the data set name and retry the request.
PT887E
Enter a cataloged data set name.
Reason:
Indicates that the specified data set name is not cataloged. The data set must be
cataloged for proper function.
Action:
Change the data set name to a cataloged data set name and retry the request.
Chapter 2: PS to PTUIX 319
PTD Messages
PT888W
Quotes have been removed from the data set name.
Reason:
Indicates that the specified data set name was enclosed in quotes. Quotes are not
permitted in Batch Processor audit file data set names. The Batch Processor removed
the quotes from the data set name.
Action:
Verify that the resulting data set is the correct data set for this request.
PT889W
Data set name has been changed.
Reason:
Indicates that the specified data set name was changed.
Action:
This is typically a result of the data set name not identifying a cataloged data set and
then the user changing the name to that of a cataloged data set.
PTD Messages
Messages with the PTD prefix are generated from CA Data Compressor.
PTDA003I
DATA COMPRESSOR DYNAMIC-ALTER CONTROL CARD PARSING STARTED
Reason:
The utility is parsing the DYNAMIC-ALTER syntax.
PTDA004E
DATA COMPRESSOR AUTHORIZATION FAILED - CONTACT CA SUPPORT
Reason:
Your site may not have a current license.
Action:
For assistance, contact CA Support at http://ca.com/support.
320 Message Reference Guide (PS to ZLB)
PTD Messages
PTDA005E
"CHANGEDATA/NOCHANGEDATA/RECOVERY" MUST BE LAST KEYWORD
Reason:
The DYNAMIC-ALTER syntax to add a transparent compression routine must end with
NOCHANGEDATA or RECOVERY.
PTDA006E
"TABLE" KEYWORD ONLY VALID AFTER "DYNAMIC-ALTER"
Reason:
The DYNAMIC ALTER keyword must be followed by TABLE and a table name.
PTDA007E
TABLE NAME MISSING CREATOR NAME, OR CREATOR NAME TOO LONG
Action:
You must specify a table name, in the form creator.tablename, after the TABLE keyword.
The creator can be up to 8 characters long.
PTDA008E
TABLE NAME TOO LONG
Reason:
A DB2 table name can be up to 18 characters long.
Action:
Check the control cards.
PTDA009E
"EDITPROC" KEYWORD VALID ONLY AFTER TABLE NAME
Reason:
The EDITPROC keyword must follow the table name specification.
Chapter 2: PS to PTUIX 321
PTD Messages
PTDA010E
"ADD" KEYWORD VALID ONLY AFTER "EDITPROC" KEYWORD
Reason:
The ADD keyword can only be placed following the EDITPROC keyword.
PTDA011E
INVALID EDITPROC NAME AFTER "ADD" KEYWORD
Action:
You must specify the name of a transparent compression routine after the ADD
keyword. You cannot specify a non-transparent edit procedure in a dynamic alter.
PTDA012E
TABLE NAME MISSING AFTER "TABLE" KEYWORD
Action:
You must specify a table name, in the form creator.tablename, after the TABLE keyword.
The creator can be up to 8 characters long.
PTDA013E
EDITPROC NAME MISSING AFTER "ADD" KEYWORD
Action:
You must specify the name of a transparent compression routine after the ADD
keyword.
PTDA014E
"FROM" KEYWORD VALID ONLY AFTER "EDITPROC" KEYWORD
Reason:
The FROM keyword can only be specified immediately after the EDITPROC keyword.
322 Message Reference Guide (PS to ZLB)
PTD Messages
PTDA015E
INVALID EDITPROC NAME AFTER "FROM" KEYWORD
Reason:
The old edit procedure specified immediately after the FROM keyword must be a
transparent edit procedure.
Action:
If you want to switch from a non-transparent edit procedure, you must drop the edit
procedure using a standard ALTER TABLE command.
PTDA016E
EDITPROC NAME MISSING AFTER "FROM" KEYWORD
Action:
You must specify the current edit procedure that you want to switch from, immediately
after the FROM keyword.
PTDA017E
"TO" KEYWORD VALID ONLY AFTER "FROM" CLAUSE
Reason:
You cannot specify TO unless you have specified FROM.
PTDA018E
INVALID EDITPROC NAME AFTER "TO" KEYWORD
Reason:
The new edit procedure specified immediately after the TO keyword must be a
transparent edit procedure.
Action:
If you want to switch to a non-transparent edit procedure, you must alter the edit
procedure using a standard ALTER TABLE command
Chapter 2: PS to PTUIX 323
PTD Messages
PTDA019E
EDITPROC NAME MISSING AFTER "TO" KEYWORD
Reason:
You must specify the edit procedure that you want to switch to, immediately after the
TO keyword.
PTDA025E
"TABLE" KEYWORD MISSING AFTER "DYNAMIC-ALTER" KEYWORD
Reason:
You must specify the TABLE keyword immediately after DYNAMIC-ALTER.
PTDA026E
DYNAMIC-ALTER STATEMENT INCOMPLETE - EXPECTED "EDITPROC" OR "ADD"
Reason:
To add a transparent compression routine to a table, you must include the EDITPROC
keyword after the table specification in the control cards.
Action:
To add a column to a table that has a transparent edit procedure, you must include the
ADD keyword.
PTDA027E
DYNAMIC-ALTER STATEMENT INCOMPLETE - EXPECTED "ADD", "DROP", OR "FROM"
Reason:
You have specified a transparent edit routine after the EDITPROC keyword without
specifying ADD, DROP, or FROM.
PTDA028E
DYNAMIC-ALTER STATEMENT INCOMPLETE - EXPECTED "TO" KEYWORD
Reason:
You have specified that you want to change from an old edit procedure to a new one,
but you did not include the TO keyword in the syntax.
324 Message Reference Guide (PS to ZLB)
PTD Messages
PTDA029E
STATEMENT INCOMPLETE - EXPECTED "CHANGEDATA/NOCHANGEDATA" KEYWORD
Reason:
When you are adding a transparent edit procedure, you must include the
NOCHANGEDATA keyword after specifying the edit procedure. The CHANGEDATA
option is not available at this time.
PTDA043E
"DROP" KEYWORD VALID ONLY AFTER "EDITPROC" KEYWORD
Reason:
If you want to drop a transparent edit procedure from a table, you must specify DROP
immediately after the EDITPROC keyword.
PTDA044E
INVALID EDITPROC NAME AFTER "DROP" KEYWORD
Reason:
You can only drop transparent edit procedures using the dynamic alter syntax.
Action:
Use the DB2 TABLE ALTER syntax to drop a non-transparent edit procedure from a table.
PTDA045E
EDITPROC NAME MISSING AFTER "DROP" KEYWORD
Reason:
You must specify the name of the transparent edit procedure that you want to drop
from the table, immediately following the DROP keyword.
PTDA046E
"CHANGEDATA" NOT SUPPORTED FOR "DROP" - "DROP" IS ONLY FOR RECOVERY
Reason:
You must specify RECOVERY after you specify DROP edit procedure.
Chapter 2: PS to PTUIX 325
PTD Messages
PTDA047E
DATA-TYPE ALLOWED ONLY AFTER "ADD" KEYWORD
Reason:
You must specify the column name and data type of the column to be added to a table
with a transparent edit procedure only after the ADD keyword.
PTDA048E
DATA-TYPE PRECISION/LENGTH MISSING
Reason:
The data type you have specified did not include the required precision or length
parameter.
PTDA049E
INVALID DATA-TYPE PRECISION/LENGTH
Reason:
The data type you have specified did not include a valid precision or length parameter.
PTDA050E
CLOSING PARENTHESIS MISSING
Reason:
You have unbalanced parentheses in the control cards.
PTDA051E
WORD "PRECISION" MISSING AFTER WORD "DOUBLE"
Reason:
To specify a column of double precision, you must specify DOUBLE PRECISION.
326 Message Reference Guide (PS to ZLB)
PTD Messages
PTDA052E
WORD "VARCHAR" OR "VARGRAPHIC" MISSING AFTER WORD "LONG"
Reason:
You must specify what kind of long data the column is.
Action:
Specify LONG VARCHAR or LONG VARGRAPHIC.
PTDA053E
"FOR" KEYWORD INVALID IN THIS POSITION
Reason:
The FOR keyword must follow the column name and data type.
PTDA054E
"SBCS", "MIXED", OR "BIT" KEYWORD VALID ONLY AFTER "FOR" KEYWORD
Reason:
FOR DATA specifications must follow the ADD column data-type specification, and take
the following form: FOR SBCS/MIXED/BIT DATA.
PTDA055E
"DATA" KEYWORD ONLY VALID AFTER "FOR SBCS/MIXED/BIT" CLAUSE
Reason:
FOR DATA specifications must follow the ADD column data-type specification, and take
the following form: FOR SBCS/MIXED/BIT DATA.
PTDA056E
"NOT" KEYWORD INVALID IN THIS POSITION
Reason:
NOT can only be included as part of the NOT NULL WITH DEFAULT specification. This
specification should be at the end of the syntax.
Chapter 2: PS to PTUIX 327
PTD Messages
PTDA057E
"NULL" KEYWORD MISSING AFTER "NOT" KEYWORD. NULL must be included as part of
the NOT NULL WITH DEFAULT specification.
Reason:
This specification should be at the end of the syntax.
PTDA058E
"WITH" KEYWORD MISSING AFTER "NOT NULL" CLAUSE. WITH DEFAULT must be
included as part of the NOT NULL WITH DEFAULT specification.
Reason:
This specification should be at the end of the syntax.
PTDA059E
"DEFAULT" KEYWORD MISSING AFTER "NOT NULL WITH" CLAUSE. DEFAULT must be
included as part of the NOT NULL WITH DEFAULT specification.
Reason:
This specification should be at the end of the syntax.
PTDA060E
STATEMENT INCOMPLETE - EXPECTED DATA-TYPE FOR COLUMN
Reason:
When you are specifying a column to add to a table with a transparent edit procedure,
you must specify the data-type immediately after the column name.
PTDA061E
STATEMENT INCOMPLETE - EXPECTED REST OF "FOR SBCS/MIXED/BIT" CLAUSE
Reason:
To specify a data format, you must include the entire FOR DATA statement.
328 Message Reference Guide (PS to ZLB)
PTD Messages
PTDA062E
STATEMENT INCOMPLETE - EXPECTED REST OF "NOT NULL WITH DEFAULT"
Reason:
To specify not null with default, you must include the entire NOT NULL WITH DEFAULT
statement.
PTDA063E
"RECOVERY" KEYWORD NOT VALID WITH "ADD" OPERATION
Reason:
You can only specify RECOVERY with FROM xx TO yy or DROP xx syntax.
PTDA064
"NOCHANGEDATA" KEYWORD NOT VALID WITH "FROM-TO" OPERATION
Reason:
You can only specify the NOCHANGEDATA keyword with ADD xx syntax.
PTDA065E
"CHANGEDATA" KEYWORD NOT VALID WITH "DROP" OPERATION
Reason:
The CHANGEDATA keyword is not in use at this time.
PTDA066E
"NOCHANGEDATA" KEYWORD NOT VALID WITH "DROP" OPERATION
Reason:
You can only specify the NOCHANGEDATA keyword with ADD xx syntax.
PTDA067E
"CUSTOMEDITPROC" KEYWORD VALID ONLY AFTER TABLE NAME
Reason:
You must specify a table name immediately after the DYNAMIC-ALTER keyword.
Chapter 2: PS to PTUIX 329
PTD Messages
PTDA068E
WORD "CUSTOMEDITPROC" MISSING AFTER WORD "WITH"
Reason:
You must follow the word WITH with CUSTOMEDITPROC in DYNAMIC-ALTER syntax.
PTDA069E
WORD "WITH" KEYWORD ONLY VALID AFTER TABLE NAME
Reason:
You must specify a table name immediately after the DYNAMIC-ALTER keyword.
PTDA070E
DYNAMIC-ALTER STATEMENT INCOMPLETE - EXPECTED "CUSTOMEDITPROC"
Reason:
You must include the CUSTOMEDITPROC keyword in the DYNAMIC-ALTER syntax if you
are adding any transparent edit procedure other than the transparent edit procedures
that are provided.
PTDA071E
DYNAMIC-ALTER STATEMENT INCOMPLETE - EXPECTED "ADD"
Reason:
The WITH CUSTOMEDITPROC clause is used only when you are adding a new column to
a table that uses a customized transparent edit procedure.
PTDA099T
"CHANGEDATA" KEYWORD NOT SUPPORTED YET IN THIS RELEASE
Reason:
The CHANGEDATA keyword is not in use at this time.
PTDA101
OPERATION ON SYSTEM DATABASE IS NOT SUPPORTED
Reason:
You cannot add transparent edit procedures or new columns to tables in the system
database.
330 Message Reference Guide (PS to ZLB)
PTD Messages
PTDA257
DYNAMIC-ALTER PROCESSING STARTED date
Reason:
Indicates that the alter processing has begun.
PTDA287
DYNAMIC-ALTER PROCESSING COMPLETE
Reason:
Indicates that the utility has completed the dynamic alter.
PTDA288
DYNAMIC-ALTER PROCESSING TERMINATED DUE TO ERROR(S) - SEE MESSAGES ABOVE
Reason:
The dynamic alter job encountered errors that caused the process to stop.
PTDA301E
TABLE ALREADY HAS EDITPROC
Reason:
You have specified that you want to add a transparent edit procedure to a table that
already has an edit procedure.
Action:
You must drop the existing edit procedure before you can add a new one.
If it is a transparent edit procedure, you can use the FROM TO syntax.
PTDA302E
ADD WITH NOCHANGEDATA REQUIRES A TRANSPARENT EDITPROC
Reason:
You must specify a transparent edit procedure following the ADD keyword, and follow it
with NOCHANGEDATA.
Chapter 2: PS to PTUIX 331
PTD Messages
PTDA304W
WARNING: EDITPROC DROP IS ONLY FOR RECOVER OR UNDO PURPOSES
Reason:
DROP edit procedure should only be used to recover to a previous point in time or for
other "undo" purposes.
Action:
Do not use it to remove the edit procedure permanently.
PTDA305E
EDITPROC FROM AND TO CANNOT BE SAME NAME
Reason:
When you specify FROM xx TO yy, you cannot specify the same edit procedure for the
FROM and the TO edit procedures.
PTDA306W
WARNING: EDITPROC FROM/TO WITH RECOVERY IS ONLY FOR RECOVERY
Reason:
FROM xx TO yy should only be used to recover to a previous point in time or for other
"undo" purposes.
Action:
Do not use it to change the edit procedure permanently.
PTDA307E
TABLE DOES NOT HAVE AN EDITPROC - USE DB2 ALTER TABLE
Reason:
You have tried to add a column to a table using DYNAMIC-ALTER, but the table does not
have an edit procedure.
Action:
Use the standard DB2 ALTER TABLE syntax to add the column.
332 Message Reference Guide (PS to ZLB)
PTD Messages
PTDA308E
ERROR ENABLING CATALOG UPDATE
Reason:
Dynamic alter was not able to update the DB2 system catalog.
PTDA309E
UTMDAAED GETMAIN FAILURE
Reason:
Dynamic alter encountered an internal error.
PTDA310E
ERROR PREPARING INITIAL DDL
Reason:
Dynamic alter encountered an internal error.
PTDA311E
ERROR EXECUTING INITIAL DDL
Reason:
Dynamic alter encountered an internal error.
PTDA312E
ERROR PREPARING STEP 2 DDL
Reason:
Dynamic alter encountered an internal error.
PTDA313E
ERROR EXECUTING STEP 2 DDL
Reason:
Dynamic alter encountered an internal error.
Chapter 2: PS to PTUIX 333
PTD Messages
PTDA316E
ERROR PREPARING ALTER DDL
Reason:
Dynamic alter encountered an internal error.
PTDA317E
ERROR EXECUTING ALTER DDL
Reason:
Dynamic alter encountered an internal error.
PTDA318E
ERROR PREPARING CATALOG SQL
Reason:
Dynamic alter encountered an internal error.
PTDA319E
ERROR EXECUTING CATALOG SQL
Reason:
Dynamic alter encountered an internal error.
PTDA320E
ERROR RESETTING CATALOG UPDATE
Reason:
Dynamic alter encountered an internal error.
PTDA321E
ADD COLUMN REQUIRES A TRANSPARENT EDITPROC
Reason:
You have tried to add a column to a table using DYNAMIC-ALTER, but the table does not
have a transparent edit procedure.
334 Message Reference Guide (PS to ZLB)
PTD Messages
PTDA322E
TABLE RECLENGTH EXCEEDS MAX ALLOWED FOR TABLE WITH AN EDITPROC
Reason:
You cannot add an edit procedure to the table you specified because its row length
exceeds the maximum allowed by DB2 for tables with edit procedures.
PTDA323I
TABLE USES A TRANSPARENT EDITPROC
Reason:
The table you specified has a transparent edit procedure.
PTDA324I
TABLE WILL USE A TRANSPARENT EDITPROC
Reason:
The table you specified will use a transparent edit procedure.
PTDA325I
EDITPROC ADDED TO TABLE
Reason:
The edit procedure has been successfully added to the table.
PTDA326I
EDITPROC DROPPED FROM TABLE
Reason:
The edit procedure you specified has been successfully dropped from the table.
Chapter 2: PS to PTUIX 335
PTD Messages
PTDA327W
TABLE WILL REQUIRE RECOVERY OR PAGE CHANGES
Reason:
The data in the table is not currently in a usable format.
Action:
After the edit procedure is dropped from the table, load the table with valid data.
PTDA328I
EDITPROC CHANGED FOR TABLE tblname
Reason:
The edit procedure has been changed as specified for the table named in the message.
PTDA329E
TABLE WITH A LONG COLUMN CANNOT BE ALTERED
Reason:
The alteration you requested cannot be made because the table has a long column.
PTDA330W
DEFINITION CHANGE OF TABLE MAY REQUIRE
Action:
See the following message.
PTDA331W
... SIMILAR CHANGE ON READ-ONLY SYSTEMS
Reason:
If the table being altered is an owner table, the read-only tables might need to be
altered also.
336 Message Reference Guide (PS to ZLB)
PTD Messages
PTDA332W
... (SQLCODE=+738)
Reason:
Messages PTDA330W and PTDA331W precede this message.
PTDA334E
ERROR EXECUTING ALTER TABLESPACE DDL
Reason:
Dynamic alter encountered an internal error.
PTDA335I
TABLESPACE ENABLED FOR 255 ROWS PER PAGE
Reason:
This is an informational message informing you that the 127 row restriction has been
removed.
PTDA336I
TABLESPACE PREVIOUSLY ENABLED FOR 255 ROWS PER PAGE
Reason:
This is an informational message informing you that this tablespace has already had its
127 row restriction removed.
PTDA337E
ERROR PREPARING ALTER TABLESPACE DDL
Reason:
Dynamic alter encountered an internal error.
PTDA398E
UNKNOWN FUNCTION IN UTADAAED
Reason:
Dynamic alter encountered an internal error.
Chapter 2: PS to PTUIX 337
PTD Messages
PTDA399E
CALL CUSTOMER SUPPORT
Reason:
Dynamic alter encountered an internal error.
PTDA999
DYNAMIC-ALTER INTERNAL ERROR - CALL Customer Support
Reason:
Dynamic alter encountered an internal error.
Action:
For assistance, contact CA Support at http://ca.com/support.
PTDC001
PTIIPT DDNAME MISSING OR FAILED OPEN
Reason:
The PTIIPT ddname is missing or failed to open.
Action:
Check that the PTIIPT ddname is allocated to a valid and available input data set (names
of compression routines).
PTDC002
STORAGE ACQUISITION FAILED
Reason:
Not enough storage is available.
Action:
Increase your region size by entering a larger value for the JCL REGION= parameter.
338 Message Reference Guide (PS to ZLB)
PTEX Messages
PTDC003
PTILIB DDNAME MISSING OR FAILED OPEN
Reason:
The PTILIB ddname could not be opened or found. This data set is used by the CA
products to access load modules for internal processing. Without this data set,
processing cannot continue and has been terminated.
Action:
Check that the PTILIB ddname is allocated to the CA product libraries.
PTDC004
PRODUCT IS NOT AUTHORIZED TO EXECUTE ON THIS SYSTEM
Reason:
Authorization to use the product has not been assigned for the specified DB2
subsystem.
Action:
Define the appropriate authorization.
PTDC005
PTILOAD DDNAME MISSING OR FAILED OPEN
Reason:
The PTILOAD ddname could not be opened or found.
Action:
Check that the PTILOAD ddname is allocated to a valid and available input data set
(control cards).
PTEX Messages
Messages with the PTEX prefix are generated from general facilities used by several
products, including: CA Data Compressor, CA Fast Check, CA Fast Index, CA Fast Load, CA
Fast Recover, CA Fast Unload, CA LogCompress, CA Merge/Modify, CA Partition Expert,
CA Quick Copy, and CA Rapid Reorg.
Chapter 2: PS to PTUIX 339
PTEX Messages
PTEX001
UTILITY DATASET DEB ERROR. RETURN CODE: rc
Reason:
The process which allows Utility data sets to occupy two extents has encountered a data
set that occupies just one extent. This message can occur under rare circumstances. It is
not generally necessary to have the UTIL data set set at two extents.
Action:
A temporary resolution would be to define the Utility data set as one track for the
primary and secondary allocations, and then run the initialization program.
PTEX002
THE [email protected] COULD NOT BE FOUND FOR VOLSER: volser
Reason:
The UCB, an MVS control block for the device, could not be found for the specified
volume serial.
PTEX003
THE DEVICE TYPE OF THE DATASET IS NOT SUPPORTED
Reason:
CA DB2 utilities do not support the device type specified for the data set. The currently
supported devices are as follows: 3350, 3380, 3390, and 34xx.
Action:
If an error occurs with a supported device, contact Technical Support.
PTEX005
READ FAILED
Reason:
A read I/O operation was unsuccessful.
Action:
Examine other messages issued during the job to help determine the source of the
problem. To diagnose the problem, the entire job is required, including all system and
CA messages.
340 Message Reference Guide (PS to ZLB)
PTEX Messages
PTEX006
STORAGE ACQUISITION FAILED
Reason:
The CA DB2 utility was unable to acquire the amount of storage necessary for the
current task.
Action:
Specify a larger REGION size and rerun or restart the job.
PTEX007
UTIL DATASET FAILED ALLOCATION
Reason:
EXCP processing dynamically allocates a temporary data set used to facilitate its
processing. This allocation failed.
Action:
Inspect the JES Log for the job and the JES messages for the job step for indications of
failure. Also ensure that the generic unit name SYSALLDA, installed by default in MVS, is
valid in your environment.
PTEX008
DATASET IS BEING ALLOCATED
Reason:
Indicates that an object has been migrated. The job will appear to be in a Wait State
while the data set is being recalled.
Action:
If this job is running for benchmark results, rerun it to achieve an accurate benchmark.
Chapter 2: PS to PTUIX 341
PTEX Messages
PTEX009
BUILD EXNODES FAILED. POSSIBLE LISTCAT ERROR.
Reason:
The CA DB2 utility was unable to perform a LISTCAT on a data set. This might be due to
the data set being migrated, among other reasons.
Action:
Rerun the job with ALLMSGS.
PTEX010
UTLEXCPE LINK FAILED. NOTIFY COMPUTER ASSOCIATES.
Reason:
The UTLEXCPE link has failed. This module prints diagnostic information in the event of
an error. If this message displays, an underlying problem occurred which caused an
attempt to print diagnostics. However, that attempt failed.
Action:
Ensure that UTLEXCPE is in the STEPLIB and resubmit the job to obtain the diagnostic
information for use by Technical Support.
PTEX011
DIRECT ACCESS NOT ALLOWED FOR TAPE DEVICES
Reason:
Direct access methods cannot be used to read or write data to tape (cartridge) devices.
You must use sequential access.
Action:
See the product's documentation to ensure that the ddnames you specified are correct.
342 Message Reference Guide (PS to ZLB)
PTFL Messages
PTEX012
OPEN FAILED FOR ddname
Reason:
An attempt to open the data set associated with ddname failed.
Action:
To determine that data set name, find the ddname in the JES messages for the job step.
The data set name accompanies ddname in the messages.
PTEX013
UNABLE TO LOAD PTLSVC99
Reason:
The load module PTLSVC99 was not loaded.
Action:
To determine the cause of the failure, examine the JES Log for the job and the JES
messages for the job step. Also, inspect the STEPLIB concatenation.
PTEX019I
SYS1.DUMPXX IS CREATED FOR RIO COMPONENT
Reason:
Indicates that an error has been detected in one of the RIO modules. An SVC dump has
been captured.
Action:
Save this dump and for assistance, contact Technical Support.
PTFL Messages
This section details messages that contain the PTFL prefix.
Chapter 2: PS to PTUIX 343
PTFL Messages
PTFL131
DISCARD DETAIL LIST
Reason:
This message marks the beginning of the discarded records report.
Action:
None.
PTFL135
COLUMN ENDS OUTSIDE INPUT
PTFL135 COLUMN STARTS OUTSIDE INPUT
PTFL135 DATA FIELD NOT NUMERIC
PTFL135 DATA FIELD TOO LARGE
PTFL135 DATA NOT IN PARTITION KEY SEQ
PTFL135 DATA VALUE TOO LARGE
PTFL135 DATE FIELD INVALID
PTFL135 DATE / TIME EXIT REJECTED
PTFL135 DUPLICATE INDEX KEY
PTFL135 FAILED CONDITIONAL CHECK
PTFL135 FAILED CONVERSION SERVICE
PTFL135 FAILED CHECK CONSTRAINT
PTFL135 FAILED FIELDPROC CONVERSION
PTFL135 FAILED OBID CHECK
PTFL135 FAILED "PARTITION" KEY
PTFL135 FAILED REFERENTIAL INTEGRITY
PTFL135 FAILED RI & CHECK CONSTRAINT
PTFL135 FAILED VALIDPROC CHECK
PTFL135 FLOAT FIELD CONVERSION ERROR
PTFL135 INPUT FILE CONVERSION ERROR
PTFL135 INVALID DATA FOUND
PTFL135 INVALID GRAPHICS STRING
PTFL135 INDEX KEY OUT OF SEQUENCE
PTFL135 LARGE TS LIMITKEY EXCEEDED
PTFL135 LOB CONVERSION FAILURE
PTFL135 PARTITION SIZE LIMIT EXCEEDED
PTFL135 PARTITIONS IN MULTIPLE INDDNS
PTFL135 TABLE ALTERED-UNLOAD SKIPPED
PTFL135 TIME FIELD INVALID
PTFL135 VARCHAR TOO BIG FOR DATA FIELD
Reason:
Indicates the reason the record was discarded.
344 Message Reference Guide (PS to ZLB)
PTGET Messages
PTGET Messages
Messages with the PTGET prefix are WTO messages that are generated from general
facilities used by CA Fast Load and CA Rapid Reorg.
PTGET02E
[email protected] <addrget> Get Error <rsncode>
Reason:
An error occurred while the utility was trying to perform an index page get.
The message variables are as follows:
■
<addrget>—Hex address of the UTMGETP block
■
<rsncode>—Hex reason code return by DB2
The utility retries the task. If all the retries fail, then the index page get task quits, a
message is issued stating that the task failed, and the job ends with a return code of 16.
Action:
No action is required if the retries are successful. However, if you consistently get these
messages, consider increasing the index's buffer pool or running the load when the
system is less busy.
PTGL Messages
Messages with the PTGL prefix are generated from general facilities used by several
products, including: CA Data Compressor, CA Fast Check, CA Fast Index, CA Fast Load, CA
Fast Recover, CA Fast Unload, CA LogCompress, CA Merge/Modify, CA Partition Expert,
CA Quick Copy, and CA Rapid Reorg.
PTGL000
CA-DB2 UTILITIES PROCESS STARTED
Reason:
This is an informational message. It is printed when CA Fast Unload begins processing.
Action:
None.
Chapter 2: PS to PTUIX 345
PTGL Messages
PTGL001
SYSIN ddname MISSING OR FAILED TO OPEN
Reason:
Indicates that the tablespace specified in the message is not in the correct state (RO,
RW, UT, STOP, UTRO, UTRW, or copy pending) for the utility to operate on it.
PTGL004
STATUS CHECK FOR DATABASE: dbname
TABLESPACE: tsname
FAILED
Reason:
The tablespace named in this error message has an invalid status for making an image
copy. For Quick Copy to make an image copy, the tablespace must be in one of the
following states: RW, RO, copy pending, UTIL, or STOP. If the object is not in one of the
above statuses, this error message displays.
Action:
To see the status of the object being copied, include the ALLMSGS keyword in the Quick
Copy syntax.
PTGL005
various messages
Reason:
These messages indicate that an error was encountered during data set access.
Action:
Check to be sure the data sets referenced for the table data are correct; and that proper
DB2 authorities have been granted.
PTGL006
INITIALIZATION COMPLETE
Reason:
Indicates that initialization has completed successfully.
346 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL007
PROCESSING TERMINATED DUE TO "CHECK" OPTION
Reason:
Processing has terminated because you have specified CHECK for the RESTART option.
This option enables you to check the syntax for errors without executing the job.
Action:
Change the RESTART option and resubmit the job.
PTGL008
USER LACKS REQUIRED DB2 AUTHORITIES
Reason:
You lack the DB2 authorities required to execute this CA DB2 utility. You must have one
of the following authorities:
■
SYSADM
■
DBADM or DBCNTL authorities for the database containing the tablespace or
indexspace to be reorganized, loaded, unloaded, or copies
■
Specific DB2 authorities for the utility in question
PTGL009
PARM FIELD ON EXECUTION CARD IS FORMATTED INCORRECTLY
Reason:
The PARM field on the EXEC card is not formatted correctly.
PTGL010
USERID PROCESSED: authid
- AUTHORIZATION ID PROCESSED
Reason:
Indicates the user ID and secondary authorization ID specified has been successfully
processed.
Chapter 2: PS to PTUIX 347
PTGL Messages
PTGL010
PTIIPT DDNAME MISSING OR FAILED OPEN
Reason:
The PTIIPT ddname is missing from your job or the DD could not be opened.
Action:
Check your job to make sure PTIIPT is included. If it is, check the DD.
PTGL010
SYSIN DDNAME MISSING OR FAILED OPEN
Reason:
The SYSIN (input) ddname is missing from your job or the DD could not be opened.
Action:
Check your job to make sure PTIIPT is included. If it is, check the DD.
PTGL011
STORAGE ACQUISITION FAILED - module_name
Reason:
Not enough storage is available. One possible problem is many discarded records during
a reorg or load.
Action:
Try increasing your region size or reducing the number of I/O buffers.
PTGL012
PTILIB DDNAME MISSING OR FAILED OPEN
Reason:
You have not included a PTILIB (CA Products) ddname in your job or the DD specified
could not be opened.
348 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL012
SIMPLE TABLESPACES LARGER THAN 2.2 GIGABYTES
Reason:
Indicates that the utility was not able to process a simple tablespace because it was
larger than 2.2 gigabytes.
PTGL013
PRODUCT IS NOT AUTHORIZED TO EXECUTE ON THIS SYSTEM
Reason:
The product executing has expired or is not authorized to run on the requested CPU.
Action:
Contact your sales representative or for assistance.
PTGL013
REGION SIZE BELOW bytes BYTES
Reason:
This message lists the region size (in bytes) available to the job.
PTGL013
CPU PASSWORD HAS EXPIRED. CONTACT CA.
Reason:
Your site may not have a current CPU password.
PTGL014
CAF ERROR: error message
Reason:
A Call Attach Facility error has occurred. The message text listed in this message varies
depending on the error encountered. The errors usually occur when problems are
encountered with connecting, opening plans, closing plans, and disconnecting.
Action:
Check the IBM DB2 Messages and Codes book to determine the error.
Chapter 2: PS to PTUIX 349
PTGL Messages
PTGL015
SYSTABLES UPDATE FAILED SQLCODE: code
Reason:
The update of SYSIBM.SYSTABLES failed for the reason given by the SQL error code.
PTGL015
SYSCOPY UPDATE FAILED => SQLCODE: code or SYSCOPY UPDATE FAILED => SQLCODE:
code
**ATTEMPTING RETRY **
Reason:
An attempted insert, delete, or update to SYSIBM.SYSCOPY failed. Another DB2 task
might have had a lock on SYSIBM.SYSCOPY.
The first form of the message is received on the last attempt to update
SYSIBM.SYSCOPY.
If this is the only PTGL015 message you receive, increase the value of the installation
parameter RESTART-RETRY so that the update will be attempted more than once if it
fails with an SQL error code of -911 or -913.
The second form of the message is generated for each unsuccessful attempt to update
SYSIBM.SYSCOPY when the update will be attempted again.
PTGL015
SYSCOPY UPDATE FAILED SQLCODE: code
Reason:
The ICTYPE column SYSIBM.SYSCOPY could not be updated to record that a REORG
LOG(NO) was performed.
PTGL015
DYNAMIC SQL SELECT FAILED FOR PREPARE => SQLCODE=code
Reason:
An attempted SQL SELECT statement failed, resulting in the listed SQLCODE.
Action:
See the IBM DB2 Messages and Codes manual for more information on this code.
350 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL016
CATALOG ACCESS SQL ERROR = > SQLCODE: - sql_error
Reason:
The displayed SQL error message was encountered when trying to access the DB2
catalog.
PTGL017
TABLESPACE IN STOP PENDING MODE - UTILITY WILL RETRY
Reason:
The specified tablespace is in Stop Pending mode, or the tablespace has been stopped
but the buffers have not yet been externalized and all locks have not yet been released.
The utility will retry.
PTGL017
SECONDARY AUTHORIZATION IS INVALID FOR THIS USER
Reason:
The authorization ID specified in the AUTHORIZATION-ID parameter is not valid for the
user who submitted the job.
PTGL018
[TABLESPACE | INDEXSPACE] name FAILED TO [STOP | START]
Reason:
The utility was not able to stop or start the tablespace or indexspace successfully. The
job will end with a return code of 8.
PTGL018
VALID RESPONSES ARE (Y)ES OR (N)O
Reason:
Valid responses are Y(es) or (N)o and you have specified an invalid response.
Chapter 2: PS to PTUIX 351
PTGL Messages
PTGL019
ELAPSED TIME: time
Reason:
The elapsed time for the Utility phase displays. This is an informational message.
PTGL020
[INDEX | INDEXSPACE | TABLESPACE] FAILED [DE/ALLOC] RC- returncode
REASON- reasoncode INFO- infocode DSN => datasetname DDN => ddname
Reason:
Dynamic allocation/deallocation of the data set has failed. The return code, reason
code, info code, data set name, and ddname are listed.
Action:
See the IBM DB2 Messages and Codes manual to determine the reason for the
allocation or deallocation failure.
PTGL021
INDEX/INDEXSPACE/TABLESPACE DATASET FAILED OPEN
Reason:
Due to environmental conditions, the data set deallocation has failed. Contact your MVS
Systems Programmer.VIO+ users: You might need to bypass VIO+ to open the
tablespace successfully.
Action:
Include the VIOCTL DD control card in the job. See the VIO+ documentation for more
information about this control card.
Note: You cannot delete/define the data sets immediately before execution.
If you have just performed a delete/define, load an empty data set using IBM Load, and
then the job will work fine.
In the future, use the space definition feature to redefine you data sets.
352 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL021
TABLESPACE FAILED "OPEN" OR "CLOSE"
RTN=>returncode RCODE=>reasoncode MOD=>module DSN=>datasetname
DDN=>ddname
Reason:
The open or close of the tablespace data set has failed in the module indicated. The
return code, data set name, and ddname are listed.
Action:
See the IBM DB2 Messages and Codes manual to determine the reason for the
allocation or deallocation failure.
PTGL021
INDEXSPACE DATASET FAILED OPEN
Reason:
Due to environmental conditions, the indexspace data set open has failed.
Action:
Contact your MVS systems programmer.
PTGL021
INDEX DATASET FAILED OPEN
Reason:
Due to environmental conditions, the data set open has failed. Contact your MVS
Systems Programmer.VIO+ users: You might need to bypass VIO+ to open the
indexspace successfully.
Action:
Include the VIOCTL DD control card in the job. See the VIO+ documentation for more
information about this control card.
PTGL022
ACB / RPL GENERATION ERROR
Reason:
An error has occurred in generating an ACB or RPL macro.
Chapter 2: PS to PTUIX 353
PTGL Messages
PTGL023
THE DB2 DATASET OPERATIONAL "STATE" IS NOT IN PROPER MODE
Reason:
Indicates that the indexspace or tablespace is not in a status required for the CA DB2
utilities to run against them. An IBM utility may be executing against them object.
Action:
Let the IBM utility complete, or use the DB2 -DISPLAY command to determine the state
of the object, and correct the data set startup mode. Then restart the utility in question.
PTGL023
THE DB2 DATASET OPERATIONAL "STATE" IS state, FROM A PREVIOUS UTILITY
Reason:
Indicates that the indexspace or tablespace is not in a status required for the CA DB2
utilities to run against the object. The current state of the object is specified in the
message.
Action:
An IBM utility might be executing against the object; if so, let the utility complete or
cancel it with the -TERM command.
If the state is UTUT, but no utility is running against the object, you can issue a START
command with ACCESS(FORCE) and then retry the utility.
354 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL024
VSAM "GET"/"PUT" ROUTINE FAILED - RTN => returncode RCODE => reasoncode
Reason:
An error has occurred trying to read or write to a VSAM page. If the error occurred
during a "put", an additional line gives the ddname of the file for which the write error
occurred.
Action:
The VSAM Return and Reason Codes are provided to help you resolve the problem. The
Return and Reason Codes are documented in VSAM Macro Return and Reason Codes
section of the DFSMS/MVS Macro Instructions for Data Sets manual, or the Macro
Instruction Return Codes and Reason Codes section of the MVS/DFP Macro Instructions
for VSAM Data Sets manual.
Locate the accompanying IEC070 or IEC161 messages. These messages, with their return
codes, and their explanation from the IBM DB2 Messages and Codes manual will help
you resolve the problem.
PTGL025
INDEXSPACE DATASET FAILED ALLOCATION
Reason:
Due to environmental conditions, the indexspace data set allocation has failed.
Action:
Contact your MVS systems programmer.
PTGL026
INDEXSPACE DATASET FAILED OPEN
Reason:
Due to environmental conditions, the indexspace data set open has failed.
Action:
Contact your MVS systems programmer.
Chapter 2: PS to PTUIX 355
PTGL Messages
PTGL030
UNABLE TO LOAD EXIT
Reason:
The utility is unable to load one of the user exit routines specified in the control cards.
PTGL030
USER EXIT NOT FOUND
Reason:
The specified user exit was not found.
Action:
Check to make sure that you have specified the correct exit name and that the exit
resides in a library allocated to STEPLIB.
PTGL060
DATASET ALTER (ADD) - INCOMPLETE.
Indicates that SMS, or another system storage manager overrode your volume
specification.
PTGL061
DATASET LISTCAT FAILED - datasetname
or
DATASET DEFINE FAILED - datasetname
Reason:
The LISTCAT or DEFINE has failed for the specified data set.
Action:
Check to be sure you have spelled the data set name correctly.
Check for system messages in the job output. If no messages, attempt to perform a
LISTCAT ENT ('data set name') ALL command using the same ID that executed the job.
This may show a message indicating the reason the LISTCAT command failed.
356 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL062
DATASET ALTER (REMOVE) INCOMPLETE
Reason:
Indicates that SMS, or another system storage manager overrode your volume
specification.
PTGL063
ALLOCATION COMPLETE FOR => name
Reason:
Indicates that the space redefinition you requested has been successfully completed.
PTGL070
FAILURE OCCURRED DURING DATASET STATUS SETTING
Reason:
An internal routine that resets the check, copy, and recover pending flags encountered
an error, and the status of the tablespace is in doubt.
Action:
Restart the tablespace with -START ACCESS(FORCE).
If the tablespace has any referential relations, run the DB2 CHECK utility. Take an image
copy to be sure the tablespace is recoverable.
PTGL071
IMAGECOPY REQUIRED FOR TABLESPACE
Reason:
A CA DB2 utility was executed against a tablespace without an image copy being taken
during the execution.
Action:
Take an image copy of the tablespace.
Chapter 2: PS to PTUIX 357
PTGL Messages
PTGL072
flagtype PENDING FLAG(S) COULD NOT BE status BECAUSE reason
Reason:
This informational message further explains the condition that message PTGL070
reports. The message variables are as follows:
■
flagtype-ALLP (all pending), CHKP (check pending), COPY (copy pending), RECP
(recover pending), or UTUT (utility utility)
■
status-DISABLED (set Status flag off) or ENABLED (set Status flag on)
■
reason-OBJECT IN RW STATUS or VALIDATION FAILED
PTGL073
TABLESPACE CHECKSUM PROCESSING FINISHED [successfully|unsuccessfully]
Reason:
This message tells you the whether tablespace checksum processing finished
successfully or unsuccessfully.
Action:
If the checksum processing was unsuccessful, you should check the other messages to
determine the status of your tablespace.
PTGL080
UPDATING CATALOG QUANTITIES FAILED - NO RESTART FOR FUNCTION
Reason:
The Utility failed to update the Catalog columns for PQTY and SQTY for the tablespace
and / or indexspaces. This portion of the job cannot be restarted. The Catalog quantities
(PQTY and SQTY) must be updated manually using the DB2 ALTER command.
PTGL081
UPDATING CATALOG STATISTICS FAILED - NO RESTART FOR FUNCTION
Reason:
The Utility failed to update the Catalog statistics. This portion of the job cannot be
restarted.
Action:
If you want the Catalog statistics updated, run RUNSTATS or PDA.
358 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL082
UPDATING SYSCOPY FAILED - NO RESTART FOR FUNCTION
Reason:
The Utility failed to update SYSIBM.SYSCOPY with image copy information. This portion
of the job cannot be restarted.
Action:
Take an image copy to be sure that the tablespace is recoverable.
PTGL083
QUICKCOPY FUNCTION FAILED - UTILITY CAN BE RESTARTED
Reason:
The Utility failed to complete making an image copy.
Action:
Use RESTART or RESTART(PHASE) to restart the utility. The image copy will be
completed.
PTGL084
CHECK PENDING FLAGS NOT SET - NO RESTART FOR FUNCTION
Reason:
The utility failed to set the check pending flags. This portion of the job cannot be
restarted.
Action:
Run the CHECK Utility to be sure that referential relations have not be violated.
Chapter 2: PS to PTUIX 359
PTGL Messages
PTGL085
DISCARD PROCESSING DID NOT COMPLETE - NO RESTART FOR FUNCTION
Reason:
The load failed to process all the discard records. This portion of the job cannot be
restarted.
Action:
If you want to see the discarded records, run the batch discard program.
If you have accidentally deleted the SYSERR data set, you can rerun the job with
OUTPUT-CONTROL ALL and UNLOAD PAUSE. This will rebuild the SYSERR data set
without actually reloading the records.
PTGL086
DATASETS HAVE BEEN LOADED SUCCESSFULLY
Reason:
Informs you that the tablespace and/or indexspace that the utility has been working
with have been loaded successfully.
Action:
You can start the spaces without any recovery procedures. Look at the other messages
to see if any portion of the job failed. For example, statistics may not have been
updated.
PTGL087
NO RESTART FROM THIS POINT
Reason:
None of the functions performed after this message is issued can be restarted. If a
function fails, you must perform that function manually.
Action:
See the messages that follow this message for indications on whether functions have
failed.
360 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL088
QUICKCOPY FUNCTION FAILED - INLINE COPIES CANNOT BE RESTARTED
Reason:
The image copy portion of the job failed. It cannot be restarted because the image copy
is written concurrently with other utility operations. The tablespace will be placed in
copy pending status.
Action:
Take an image copy to be sure that the tablespace is recoverable.
PTGL089
ALL DATASETS DID NOT LOAD SUCCESSFULLY - UTILITY CAN BE RESTARTED
Reason:
See the previous error messages for this job to determine the problem the utility
encountered. After you correct the problems, the job can be restarted using RESTART or
RESTART(PHASE).
PTGL090
PDA AND STATISTICS UPDATE -BYPASSED-DUE TO RESTART
Reason:
PDA statistics processing was bypassed because of a restart.
PTGL090
UNLOAD PROCESS UNLOADED ALL ROWS BUT AN UNKNOWN PAGE TYPE WAS
FOUND. SEE MESSAGE PTRR040 ABOVE FOR PAGES FOUND FLAGGED AS UNKNOWN.
SEE UTILITIES ERROR MANUAL FOR COMPLETE DESCRIPTION OF ERROR. JOB MAY
HAVE TO BE RESTARTED TO COMPLETE RELOAD PHASE.
Reason:
Indicates that the utility encountered at least one page of unknown page type.
The PTRR040 error message description in this manual provides a complete description
of steps to take to restart the job.
Chapter 2: PS to PTUIX 361
PTGL Messages
PTGL091
INDEX => creator indexname <= FAILED CHECKSUM PROCESSING
Reason:
The specified index has failed the checksum processing. Depending on the state of the
index and the job, you might be able to restart the job.
PTGL091
SWITCHING TO STANDARD VERSION - SYSTEM IS NOT ESA
Reason:
Although the job specified to use an Extended Reorg, the system on which the job is
running does not meet all the requirements. You must have ESA to perform an Extended
Reorg.
PTGL092
CATALOG SCAN ERROR - OPEN FAILED
Reason:
An open failure occurred on the DB2 Catalog data sets.
Action:
See associated JES messages.
PTGL092
HIPERSPACE NOT SUPPORTED - SETTING TO DATASPACE ONLY
Reason:
Extended Reorg processing will use dataspace but not hiperspace because your system
does not support hiperspace, or enough extended storage was not available.
PTGL092
HIPERSPACE NOT SUPPORTED - SETTING TO DATASPACE ONLY
Reason:
Your CPU does not support hiperspaces. Dataspaces will be used.
362 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL092
HIPERSPACE NOT SUPPORTED - SETTING TO DATASPACE ONLY
Reason:
Your CPU does not support hiperspaces. Dataspaces will be used.
PTGL093
HIPERSPACE - "MOVEPAGE" NOT SUPPORTED
Reason:
Indicates that the hiperspace move page option is not supported.
PTGL093
CATALOG SCAN ERROR - GET FAILED
Reason:
A get failure occurred on the DB2 Catalog data sets.
Action:
See associated JES messages.
PTGL094
CATALOG SCAN ERROR - GETMAIN FAILED
Reason:
Not enough region is specified or available to complete the DB2 Catalog scan.
PTGL095
TABLESPACE PLACED IN CHECK PENDING dbname tsname part
Reason:
The tablespace named in this message has been placed into check pending status in
DB2. A DB2 Check Data Utility must be executed against the tablespace before it can be
used.
Chapter 2: PS to PTUIX 363
PTGL Messages
PTGL096
START FAILED FOR CHK PENDING PROCESS:
Reason:
The utility stopped the tablespace to set the check pending flag. It could not start it.
PTGL097
SYSTABLES UPDATED FOR: creator table
Action:
The DB2 SYSIBM.SYSTABLES statistical columns have been updated for the table named
in the message.
PTGL098
THE TOTAL OF ALL CLUSTERED INDEX ROWS DOESN'T MATCH TABLESPACE COUNTS
Reason:
Not all rows are indexed correctly or there are too many index entries.
Action:
You must recreate or recover the index.
PTGL099
INDEX CHECKSUM PROCESSING FINISHED [successfully|unsuccessfully]
Reason:
This message tells you the whether index checksum processing finished successfully or
unsuccessfully.
Action:
If the checksum processing was unsuccessful, you should check the other messages to
determine the status of your index.
364 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL100
parmlibfield parmlibvalue [*]
Reason:
This informational message appears in the PTIIMSG file once for each two parmlib
options, showing the current parmlib values in two-column format. An asterisk (*) is
shown next to each parmlib option that might have been overridden in your utility job.
Action:
Check your job input to determine the values actually used in the job.
PTGL101
SYNTAX ERROR ON OR NEAR LOCATION location
Reason:
A syntax error was found on or near the location specified.
PTGL102
DUPLICATE KEYWORD ON OR NEAR LOCATION location
Reason:
A duplicate keyword was found on or near the location specified.
Action:
Remove the duplicate.
PTGL102
INVALID KEYWORD ON OR NEAR LOCATION location
Reason:
A syntax keyword error was found on or near the location specified.
Chapter 2: PS to PTUIX 365
PTGL Messages
PTGL103
DUPLICATE KEYWORD ON OR NEAR LOCATION location
Reason:
A duplicate keyword was found on or near the location specified.
Action:
Remove the duplicate.
PTGL104
DATABASE / TABLESPACE NAME FORMAT ERROR
Reason:
An error was encountered in the database or tablespace name format.
Action:
Correct the name and resubmit.
PTGL105
INDEXNAME FORMAT ERROR
Reason:
An error was encountered in the database or index name format.
Action:
Correct the name and resubmit.
PTGL106
PARTITION FORMAT ERROR
Reason:
An error was encountered in the index partition name format.
Action:
Correct the name and resubmit.
366 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL106
DATA FIELD MUST BE NUMERIC
Reason:
The specified data field is non-numeric and must be numeric.
PTGL107
OBID FORMAT ERROR
Reason:
The OBID was specified incorrectly in the INTO TABLE clause.
Action:
Recheck the Utility syntax and resubmit the job.
PTGL107
PARTITION MUST BE (ALL) OR NUMERIC
Reason:
The partition name must be ALL or a number that indicates the specific partition
number.
PTGL108
TABLE NAME FORMAT ERROR
Reason:
An error was encountered in the table name format.
Action:
Correct the name and resubmit.
PTGL109
"CALC" NOT VALID FOR TABLESPACE-INDEX OR TABLE-INDEX REQUESTS
Reason:
The CALC parameter is not valid for TABLESPACE-INDEX or TABLE-INDEX reorganizations.
Action:
Remove the CALC keyword.
Chapter 2: PS to PTUIX 367
PTGL Messages
PTGL110
INDIVIDUAL PARTITIONS NOT VALID FOR TABLESPACE-INDEX OR TABLE-INDEX
Reason:
You have specified individual partitions while using the TABLESPACE-INDEX or
TABLE-INDEX keywords.
Action:
If you want to reorganize individual indexspace partitions, you must use the INDEX
keyword.
PTGL111
STORAGE ACQUISITION FAILED [ - module]
Reason:
Not enough storage is available.
Action:
Try increasing your region size.
If present, module indicates where the error occurred.
PTGL112
DB2 CATALOG TABLES MAY NOT BE PROCESSED
Reason:
The DB2 system (catalog) objects cannot be processed by the product.
Action:
Do not select DB2 system objects.
PTGL113
PASSWORD AUTHORIZATION FAILED, CONTACT CA
Reason:
Your site may not have a current password.
368 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL113
ONLINE REORG AUTHORIZATION FAILED, CONTACT CA
Reason:
Your site may not have a current license for the utility.
PTGL114
QUICK COPY AUTHORIZATION FAILED, CONTACT CA
Reason:
Your site may not have a current CA Quick Copy license.
PTGL115
PARSING FUNCTION COMPLETED SUCCESSFULLY
Reason:
The command syntax has been parsed. Any errors have been pointed out with
messages.
If you specified the CHECK restart option, processing stops. Otherwise, processing
continues.
PTGL116
UTILITY KEYWORD MISSING
Reason:
A required utility keyword is missing.
PTGL117
MAXTASKS NOT NUMERIC OR > 9999
Reason:
You have specified an invalid value for MAXTASKS. A numeric value less than 9999 must
be specified.
Chapter 2: PS to PTUIX 369
PTGL Messages
PTGL118
QUICK COPY OPTIONS IGNORED FOR INDEX REORGS OR FASTSCAN FUNCTIONS
Reason:
You have specified QUICK COPY for an index reorganization or a FastScan. The option is
ignored.
PTGL119
DATA FIELD MUST BE NUMERIC OR IN CALCULATION FORMAT
Reason:
The specified data field must be a numeric value or a space calculation.
PTGL120
CALCULATION FORMULA IS INVALID
Reason:
The specified space calculation is invalid.
PTGL121
PDA AUTHORIZATION FAILED, CONTACT CA
Reason:
An internal error has occurred.
Action:
For assistance, contact CA Support at http://ca.com/support.
PTGL122
WARNING - KEYWORD NOT SUPPORTED
Reason:
Indicates that one of the non-supported keywords (such as STARTUP-ACCESS, QUIESCE,
or PAGE-SIZE for example) was included in the job control card. Processing will continue
with the next control card.
370 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL123
"INTO TABLE" KEYWORD REQUIRED FOR FASTLOAD UTILITY.
Reason:
You must include the INTO TABLE clause of the syntax. This clause specifies the table to
be loaded.
PTGL124
FASTLOAD AUTHORIZATION FAILED - Contact Customer Support for assistance
Reason:
Your site may not have a current license.
Action:
For assistance, contact CA Support at http://ca.com/support.
PTGL125
MAXTASKS CANNOT BE GREATER THAN 99.
Reason:
You have specified a value greater than 99 for Max Tasks. 99 is the maximum value
accepted.
PTGL125
PARSING FUNCTION FAILED
Reason:
The utility was not able to parse the control cards successfully.
Action:
Check the job output for error messages that describe syntax errors.
PTGL126
SORTFLAG SPECIFIED IS NOT SUPPORTED IN THIS RELEASE - SEE MANUAL
Reason:
The SORTFLAG you have specified is not valid in the current release of the CA DB2
utilities. (It may be from an earlier release.)
Chapter 2: PS to PTUIX 371
PTGL Messages
PTGL127
IGNORE-ERROR FORMAT ERROR
Reason:
The IGNORE-ERROR parameter was specified in an invalid format.
Action:
Use the following format:IGNORE-ERROR 1,2,16.
PTGL130
"UNLOAD PAUSE" VALID ONLY FOR "ALL" TYPE LOADS
Reason:
You have specified UNLOAD PAUSE on a BUILD type load, but UNLOAD PAUSE is valid
only when the load type is ALL.
PTGL131
RECOVERY IN-PROGRESS
Reason:
Indicates that the CA DB2 utility has begun the Restart Recovery phase of the job.
PTGL131
INDEX REBUILD UNSUCCESSFUL - INDEX(ES) MUST BE RECOVERED
Reason:
Indicates that due to a reorg failure during the reload phase, some non-clustering
indexes must be recovered.
Action:
See message(s) PTRR044 to identify the indexes needed recovery. Job processing has
terminated.
PTGL132
RECOVERY COMPLETE
Reason:
Indicates that the CA DB2 utility has completed the Restart Recovery phase of the job.
372 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL134
SPECIFIED DDNAME MUST BE SIX CHARACTERS OR LESS or "INDDN" DDNAME MUST
BE SIX CHARACTERS OR LESS
Reason:
The ddname specified for the INDDN, WORKDDN, or UNLDDN keyword must be six or
fewer characters, because the seventh and eighth characters are used for increment
numbers.
PTGL141
ONLY 'NO' IS SUPPORTED FOR LOG
Reason:
LOG YES is not supported but will apply LOG NO.
Action:
If you must use LOG YES with your load or reorg, use the IBM LOAD or REORG utility.
PTGL142
ONLY 'NO' IS SUPPORTED FOR ENFORCE
Reason:
ENFORCE CONSTRAINTS is not supported.
Action:
If you must use ENFORCE CONSTRAINTS with your load, use the IBM LOAD utility.
The utility does not support the ENFORCE parameter but will allow ENFORCE NO.
PTGL144
FIELD SPECIFICATIONS ARE ONLY VALID ON FIRST INTO CLAUSE
Reason:
Any column definitions must be defined in the first INTO TABLE clause. You can only
have one column definition set, and it will apply to all INTO TABLE tablename PART
sequences. Any subsequent field specifications (column definitions) are ignored.
Chapter 2: PS to PTUIX 373
PTGL Messages
PTGL145
UNLOAD-ACCESS OPTION INVALID - MUST BE "RO" OR "STOP"
Reason:
You have specified an invalid option for the UNLOAD-ACCESS keyword in your job. The
option must be RO (read-only) or STOP, to specify whether the object will be available in
READ-ONLY status during the unload phase.
PTGL146
sort-program DETECTED AS THE SORT PROGRAM
Reason:
This informational message identifies the sort program that the CA DB2 utility has
detected. The possible sort-program values are CA-SORT, DFSORT, and SYNCSORT.
PTGL147
$ORTPARM: VSCORE = nnnK, VSCORET = mmmK
Reason:
This informational message for SYNCSORT users lists the sort parameter values used
with dynamic allocation of the $ORTPARM DD data set. The VSCORE value is taken from
the parmlib parameter SORT-APPLSIZE value. For the VSCORET parameter, the SORTSIZE
value from the job (or the value of the parmlib parameter SORT-SORTSIZE) is used.
PTGL170
DATASET DID NOT LOAD SUCCESSFULLY. RESTART IS REQUIRED.
Reason:
An error occurred while loading your data sets.
Action:
Check for other error or sort messages.
374 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL200
INVALID WHERE CLAUSE CONSTRUCTED
Reason:
You have specified an invalid WHERE clause for your SELECT or DELETE statement.
Action:
Check the SQL syntax.
PTGL201
CONSTANT VALUE IS INVALID
Reason:
The constant you have specified for your SELECT or DELETE statement is invalid.
Action:
Check the SQL syntax.
PTGL202
COMPARISON OPERATOR IS UNKNOWN
Reason:
The comparison operator you have specified for your SELECT or DELETE statement is
invalid.
Action:
Check the SQL syntax.
PTGL203
CURRENT DATE SYNTAX IS INCORRECT
Reason:
The CURRENT DATE syntax in the control cards is invalid.
Chapter 2: PS to PTUIX 375
PTGL Messages
PTGL204
TABLE NAME FOR ROW-SELECTION NOT FOUND IN THIS TABLESPACE
Reason:
The specified table was not found in the specified tablespace.
Action:
Check the table name. (If the creator is not specified, it defaults to the job submitter.)
If it is correct, try quiesceing the tablespace and resubmitting the job.
PTGL204
TABLE NAME FOR ROW-SELECTION NOT FOUND IN THIS TABLESPACE
Reason:
You have specified a table that is not in the tablespace being reorganized. The table
name is specified in the row selection portion of the job.
Action:
Correct the JCL and resubmit the job.
PTGL205
COLUMN - column name WAS NOT FOUND IN TABLE SELECTED
Reason:
The specified column was not found in the selected table. Check the SELECT or DELETE
statement to make sure you have specified the correct information.
Action:
Check the table and column names. (If the table creator is not specified, it defaults to
the job submitter.)
PTGL206
COLUMN - column NUMERIC FIELD GREATER THAN 15 BYTES
Reason:
You have specified a numeric constant for the specified column that is greater than the
limit, 15 bytes.
Action:
Check the value to make sure the correct number is entered.
376 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL207
COLUMN - column IS COMPARING AGAINST A NON-NUMERIC FIELD
Reason:
You have specified a non-numeric constant for the specified column, which is a numeric
field.
Action:
Check the column's definition and respecify the constant.
PTGL208
COLUMN - column HAS AN UNSUPPORTED DATA TYPE
Reason:
You have specified a column in a SELECT or DELETE clause that contains an unsupported
data type. FLOAT, GRAPHIC, and LONGVAR columns are not supported for row
selection/deletion. This message is also issued if you attempt to specify INITIAL for an
invalid column type.
PTGL209
COLUMN colnam STARTING / ENDING POSITION INVALID
Reason:
The starting or ending position for the column specified in the error message is invalid
or inconsistent with the column definition.
PTGL210
POSITIONAL VALUE MUST COMPARE AGAINST CHARACTER DATA OR HEX DATA
Reason:
The field specification for a positionally-defined column is invalid.
PTGL211
COLUMN colnam IS NOT NULL DEFINED COLUMN
Reason:
The column named in the message is defined as NOT NULL, but you have tried to set it
to NULL. (Using NULLIF, for example.)
Chapter 2: PS to PTUIX 377
PTGL Messages
PTGL212
COLUMN: colname CONTAINS INVALID HEX DATA
Reason:
The specified column contains invalid hexadecimal data. A valid hexadecimal number
consists of an even number of digits, 0-9 or A-F.
PTGL216
NUMERIC LITERAL NOT VALID
Reason:
Embedded Structured Query Language (ESQL) does not support numeric literals. Only
character strings, hex strings, and graphic strings are supported.
Action:
Specify the value as a hex string and resubmit the job.
PTGL217
FAILURE BUILDING UTILITY ID
Reason:
CA Fast Unload attempted to build a utility ID but failed. CA Fast Unload builds a default
utility ID from the user ID and job name if the user does not provide an override utility
ID.
Either or both of the possible utility ID generation processes have failed.
Action:
Correct the override utility ID or determine what is causing the failure in the generation
of the default utility ID, and resubmit the job.
PTGL300
RESTART LOG SQL ERROR => SQLCODE-311
Reason:
The specified SQL error occurred on the Restart table.
Action:
Specify that the Restart table is to use 32K pages instead of 4K and restart the job.
378 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL300
SUBSYSTEM NOT FOUND IN JES TABLE
Reason:
The DB2 subsystem ID requested is not found in the JES tables that contain available
DB2 subsystem IDs.
PTGL301
INTERNAL DB2 BLOCKS DO NOT MATCH
Reason:
The DB2 subsystem ID requested is not found in the JES tables that contain available
DB2 subsystem IDs or an internal error was found in the JES tables.
PTGL301
UNABLE TO RETRY SELECT
Reason:
An attempted RETRY SELECT statement failed. The SELECT is attempted ten times.
PTGL302
APPLICATION LACKS MVS APF AUTHORIZATION
Reason:
Certain CA DB2 utility applications must be installed in MVS authorized libraries.
PTGL302
DB2 CATALOG TABLE "SYSCOPY" UPDATED WITH REORG LOG(NO)
Reason:
You specified the Update SYSCOPY option. The ICTYPE column of SYSIBM.SYSCOPY has
been updated with “W” to record that a reorganization with LOG(NO) was performed.
PTGL303
DB2 CATALOG TABLE "SYSCOPY" UPDATED WITH IMAGE COPY
Reason:
You specified the "Y" to register the image copy. The ICTYPE column of SYSIBM.SYSCOPY
has been updated with “F” to record that a full image copy was performed.
Chapter 2: PS to PTUIX 379
PTGL Messages
PTGL304
APPLICATION LACKS MVS AUTHORIZATION FOR SYSCOPY UPDATE
Reason:
The program is not being executed from an APF authorized library, therefore it does not
have the necessary authorities for execution.
PTGL305
DB2 CATALOG TABLE SYSTABLEPART UPDATED WITH NEW QUANTITIES
Reason:
The catalog statistics have been updated in the SYSIBM.SYSTABLEPART table.
PTGL305
ANOTHER Computer Associates DB2 utility IS CURRENTLY EXECUTING/ACTIVE ON THIS
TABLESPACE
Reason:
Another CA DB2 utility is currently executing against the specified tablespace. The
current utility request cannot be processed until the other utility has completed
executing.
PTGL306
DB2 CATALOG TABLE "SYSCOPY" UPDATED WITH LOAD REPLACE LOG(NO)
Reason:
The DB2 catalog table SYSIBM.SYSCOPY will be updated with the value "S" to indicate
that a LOAD Utility with the REPLACE LOG(NO) option was executed against the
specified object.
PTGL306
SYSTABLEPART UPDATE FAILED => SQLCODE: code
Reason:
The CA DB2 utility was not able to update the catalog statistics in
SYSIBM.SYSTABLEPART.
Action:
Check the SQL return code to determine the reason for the update failure.
380 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL307
DB2 CATALOG TABLE "SYSCOPY" UPDATED WITH LOAD LOG(NO)
Reason:
The DB2 catalog table SYSIBM.SYSCOPY will be updated with the value "Y" to indicate
that a LOAD Utility with the LOG(NO) option was executed against the specified object.
PTGL308
ERROR OCCURRED DURING SYSLGRNG SCAN. RERUN WITH ABEND-TASK
Reason:
An error occurred when the CA DB2 utility was scanning SYSLGRNG.
Action:
Rerun the job with ABEND-TASK.
PTGL311
ANOTHER Computer Associates DB2 utility IS CURRENTLY ACTIVE ON THIS OBJECT
Reason:
Indicates that the object or partition on which you want to run a utility is in use by
another CA DB2 utility.
Action:
Wait until the other utility job has finished.
PTGL320
INITIALIZATION OF DB2 ENVIRONMENT FAILED
Reason:
An attempt to set up the utility environment has failed.
PTGL321
INITIALIZATION OF LOGRBA FAILED
Reason:
An attempt to set up the utility environment has failed.
Chapter 2: PS to PTUIX 381
PTGL Messages
PTGL330
PARMLIB ENTRY - COPY-BUFFERS IS INVALID
Reason:
The value for the COPY_BUFFERS parameter in the UTIL member of
high-level.CDBAPARM must be an integer between 0 and 999.
PTGL331
PARMLIB ENTRY - SORT-APPLSIZE IS INVALID
Reason:
The value for the SORT-APPLSIZE parameter in the UTIL member of
high-level.CDBAPARM must be of the form nnnnK.
PTGL332
PARMLIB ENTRY - NONLEAF-PCTFREE IS INVALID
Reason:
The value for the NONLEAF-PCTFREE parameter in the UTIL member of
high-level.CDBAPARM must be LEAF or an integer between 0 and 99.
PTGL333
PARMLIB ENTRY - VSAM-BUFFERS IS INVALID
Reason:
The value for the VSAM-BUFFERS parameter in the UTIL member of
high-level.CDBAPARM must be an integer between 0 and 999.
PTGL334
PARMLIB ENTRY - IO-BUFFERS IS INVALID
Reason:
The value for the IO-BUFFERS parameter in the UTIL member of high-level.CDBAPARM
must be an integer between 0 and 999.
382 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL335
PARMLIB ENTRY - MAXTASKS IS INVALID
Reason:
The value for the MAXTASKS parameter in the UTIL member of high-level.CDBAPARM
must be an integer between 1 and 9.
PTGL336
PARMLIB ENTRY - SORTFLAG IS INVALID
Reason:
The value for the SORTFLAG parameter in the UTIL member of high-level.CDBAPARM
must be ALL, NONE, or CRITICAL.
PTGL337
PARMLIB ENTRY - SORT-SORTNUM IS INVALID
Reason:
The value for the SORT-SORTNUM parameter in the UTIL member of
high-level.CDBAPARM must be an integer between 0 and 999.
PTGL338
PARMLIB ENTRY - COPY-TASKS IS INVALID
Reason:
The value for the COPY-TASKS parameter in the UTIL member of high-level.CDBAPARM
must be an integer between 0 and 999.
PTGL339
PARMLIB ENTRY - SMS-VOLUMES IS INVALID
Reason:
The value for the SMS-VOLUMES parameter in the UTIL member of
high-level.CDBAPARM must be an integer between 0 and 99.
Chapter 2: PS to PTUIX 383
PTGL Messages
PTGL340
PARMLIB - COLCARD INVALID
Reason:
The value you specified for the COLCARD parameter in the UTIL member of
high-level.CDBAPARM is not valid.
Action:
You must specify INDEXED or ALL.
PTGL343
PARMLIB ENTRY - DISCARD-ERROR IS INVALID
Reason:
The value for the DISCARD-ERROR parameter in the UTIL member of
high-level.CDBAPARM must be NONE, ABEND, or RCxx (where xx is a number from 5 to
50).
PTGL347
PARMLIB ENTRY - INPUT-BUFFERS IS INVALID
Reason:
The value you specified for input buffers is incorrect.
Action:
Specify an integer that indicates the number of buffers to be used when reading data
from SYSREC and SYSUT1.
PTGL350
STATS-OPTIONS: INVALID OPTION
Reason:
The option you specified in the STATS-OPTIONS keyword is not valid.
Action:
You must specify COLCARD-INDEXED or COLCARD-ALL.
384 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL351
PARMLIB ENTRY - PAGE-FRAMES xxxx
Reason:
You have exceeded the maximum value permitted for the PAGE-FRAMES parmlib entry,
which is 70. The variables in the message (denoted by xxxx) indicate one of the
following:
■
IS INVALID-The PAGE-FRAMES value you specified is too large.
■
SET TO 70-The utility has set the PAGE-FRAMES value to 70 so that processing can
proceed.
PTGL353
PARMLIB ENTRY - STOP-LIMIT IS INVALID
Reason:
The value for the STOP-LIMIT parameter in the UTIL member of high-level.CDBAPARM
must be a five-digit integer (maximum value 99999). The default value is 1.
PTGL354
PARMLIB ENTRY - UPDATE-CATSTATS IS INVALID
Reason:
The value for the UPDATE-CATSTATS parameter in the UTIL member of
high-level.CDBAPARM must be YES or NO.
PTGL400
RESTART LOG SQL ERROR = > SQLCODE: sql_code
Reason:
The utility encountered a problem when it attempted to restart the job.
Action:
Ensure the restart table has not been tampered with.
Chapter 2: PS to PTUIX 385
PTGL Messages
PTGL400
RESTART LOG SQL ERROR = > SQLCODE: - sqlcode
Reason:
An SQL error was encountered querying the record log. The SQL error code has been
provided to help you solve the problem.
Action:
See the IBM DB2 Messages and Codes manual for detailed SQL error code information.
PTGL401
RESTART LOG RECORD CREATED - UTILITY ID => util_id
Reason:
This informational message is issued at the beginning of a non-restart utility job. It gives
you the Utility ID of the job (the submitter's user ID if not explicitly stated on the EXEC
card) and informs you that a row has been entered in the CA RESTART table for the job.
This makes the reorganization job restartable.
PTGL402
RESTART LOG DELETED
Reason:
Indicates that the restart row in the CA RESTART table for the job has been deleted. The
job is no longer restartable. The restart log is deleted at the end of a successful job
execution.
PTGL403
RESTART ROW NOT FOUND - TASK IS NOT RESTARTABLE
Reason:
This informational message tells you that no row has been found in the CA RESTART
table for the task, and so it is not restartable.
Action:
You must restart the job from the beginning.
386 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL404
INVALID RESTART PARAMETER
Reason:
You have specified an invalid restart parameter. Valid parameters are as follows:
■
RESTART
■
RESTART(PHASE)
■
RESTART(BYPASS)
■
CHECK
PTGL405
RESTART PROCESSING ACTIVE - DATA OBJECT RESTARTING WITH LAST PHASE
Action:
Restart processing has begun. The data object is being processed in the last phase.
PTGL406
DATA OBJECT IN RESTART MODE - USER BYPASSED RESTART STARTING UNLOAD
Action:
Restart processing has begun. The data object is being processed in the last phase.
PTGL406
RESTART TABLE ERROR - GLRS_DATA TOO SMALL
Reason:
The RESTART Table column GLRS_DATA is too small.
Action:
You must resize the GLRS_DATA column in the Utilities RESTART table. Edit the PUTDDL
member in high-level.CDBASRC using SDM (Software Delivery Manager). Change the
length of the GLRS_DATA column.
Chapter 2: PS to PTUIX 387
PTGL Messages
PTGL407
DATA OBJECT IN RESTART MODE - RESTART PARAMETER REQUIRED
Reason:
This message tells you that a row has been found in the RESTART table for the task, and
so you must include a restart parameter on the EXEC card of your utility job to restart it.
PTGL408
RESTART(TERM) NOT VALID FOR THIS UTILITY
Reason:
The RESTART(TERM) parameter cannot be specified for the utility being executed.
Possible restart values are RESTART, RESTART(PHASE), or RESTART(BYPASS).
PTGL408
DATA OBJECT IN RESTART MODE - ACTION PARAMETER MISMATCH
Reason:
You tried to reorganize an index whose tablespace is in restart mode or tried to perform
a FastScan on a tablespace in restart mode.
Action:
You must complete the reorganization before any other Reorg utilities can be executed
against the objects.
PTGL409
DATA OBJECT IN RESTART MODE - UTILITY MISMATCH
Reason:
The object being processed has been logged as having a utility job already started on it.
The previous utility job is not the same as the currently requested utility job.
PTGL410
RESTART PROCESSING ACTIVE - OBJECT RESTARTING WITH LAST CHECK POINT
Reason:
The request to restart the utility has been processed and the utility is being restarted at
the last checkpoint.
388 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL411
OBJECT RESTARTING WITH FIRST PHASE
Reason:
The restarted utility job is restarting with the first processing phase.
PTGL411
DATA OBJECT IN RESTART MODE - USER BYPASSED RESTART. STARTING COPY
Reason:
The specified object was in restart mode, but a restart was not requested by the user.
An image copy is being performed on the object.
PTGL411
OBJECT RESTARTING WITH FIRST PHASE
Action:
Restart processing has begun. The data object is being processed in the first phase.
PTGL411
OBJECT RESTARTING WITH FIRST PHASE
Reason:
The restarted utility job is restarting with the first processing phase.
PTGL412
RESTART TABLE DOESN'T MATCH INPUT
Reason:
The row for the utility job in the RESTART Table does not match the information for the
current job. Another utility job is running against the same objects, or the objects
specified do not match the previous execution of the utility.
Chapter 2: PS to PTUIX 389
PTGL Messages
PTGL412
RESTART TABLE DOESN'T MATCH INPUT
Reason:
The row for the utility job in the RESTART Table does not match the information for the
current job. Another utility job is running against the same objects, or the objects
specified do not match the previous execution of the Utility.
PTGL412
RESTART TABLE DOESN'T MATCH INPUT
Reason:
Indicates that an internal error with the RESTART table has been detected.
PTGL415
DATA OBJECT IN RESTART MODE - UTILITY MISMATCH
Reason:
The object is in Restart mode for another CA DB2 utility.
When the other utility has released the object, you can run your job.
PTGL415
OBJECT IN USE BY ANOTHER Computer Associates DB2 utility
Reason:
The object cannot be accessed because it is in use by another CA DB2 utility. As a result,
more than one Utility is attempting to access the same RESTART table row.
Action:
Check for a stopped utility in the RESTART table.
390 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL417
UNABLE TO RUN UPDATE UTILITIES CONCURRENTLY-SEE MESSAGE PTGL430
Reason:
Two update-mode utilities are attempting to run against the same DB2 tablespace, but
this is not allowed.
Action:
See message PTGL430 for information about which utility has a lock on the tablespace.
PTGL418
UNKNOWN UTILITY TYPE
Reason:
An unknown utility type has been encountered. Examples of utility types include:
REORG-TS, FASTLOAD, FASTBLD, COPY, UNLOAD, RECOVER.
PTGL420I
RESTART ROW FOUND FOR utility AND PARTITIONS: partitionlist
Reason:
Indicates for which utility and for which partitions (if applicable) a RESTART row was
found.
PTGL421S
utility RESTARTED WITH INVALID DSNUM PARAMETER. RESTART USING DSNUM
PARAMETER WITH SAME PARTITIONS AS RESTART ROW.
Reason:
The specified utility has been restarted with an invalid DSNUM parameter or an
incorrect partition list.
The job must be corrected to indicate the same partitions as the restart row to
successfully process the restart.
PTGL425S
RESTART ROW FOR UNKNOWN PRODUCT
Reason:
Indicates that a RESTART row for an unknown product has been found in the RESTART
table.
Chapter 2: PS to PTUIX 391
PTGL Messages
PTGL430
TABLESPACE PART: nnn UID: user_id utility_type LK:lock UTILITY ID: util_id
Reason:
This error message gives you the partition number (nnn) and the Utility ID (util_id) for
the tablespace utility job. The utility_type indicates the type of utility job: REORG-TS,
FASTLOAD, FASTBLD, COPY, UNLOAD, RECOVER, or OTHER. The lock value is EXCL
(exclusive) or RO (read only). If you receive this message, it means you tried to do one of
the following:
■
Restart a job with a different Utility ID,
■
Run a job with no restart parm when a restart row is found, or
■
Run a different utility
The utility terminates with a non-zero return code, leaving the restart row intact.
Note: There are times that this message is issued as a warning message and the job
finishes ok with a condition code of 0. In this case, there are multiple utilities
referencing (and possibly updating) the NPIs simultaneously (as long as they are using
different partitions). In this case, PTGL430 message is issued simply as a warning, and is
a non-error situation.
PTGL431
IXSP: indexname PART: nnn UID: user_id utility_type LK:lock UTILITY ID: util_id
Reason:
This error message gives you the index name (indexname), the partition number (nnn),
and the Utility ID (util_id) for the indexspace utility job. The utility_type indicates the
type of Utility job: REORG-IX, FASTLOAD, FASTBLD, COPY, UNLOAD, RECOVER, or
OTHER. The lock value is EXCL (exclusive) or RO (read only). If you receive this message,
it means you tried to do one of the following:
■
Restart a job with a different Utility ID,
■
Run a job with no restart parm when a restart row is found, or
■
Run a different utility
The utility terminates with a non-zero return code, leaving the restart row intact.
Note: There are times that this message is issued as a warning message and the job
finishes ok with a condition code of 0. In this case, there are multiple utilities
referencing (and possibly updating) the NPIs simultaneously (as long as they are using
different partitions). In this case, PTGL431 message is issued simply as a warning, and is
a non-error situation.
392 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL435
CATALOG ERROR DURING HEADER PAGE BUILD
Reason:
A CA DB2 utility encountered an error in the system catalog while attempting to build a
header page.
PTGL498
ENQ OF TS(IX): xxxxxxxx.xxxxxxxx ON PART: xxx FAILED
Reason:
Indicates that another CA DB2 utility is using the tablespace or index partition specified
in the message.
PTGL499
DEADLOCK ENCOUNTERED TRYING TO ACCESS RESTART TABLE. RETRYING ACCESS.
Reason:
Indicates that the utility was not able to update the RESTART table. It will retry as many
times as were specified in the RESTART-RETRY parm of the UTIL member of
high-level.CDBASRC.
PTGL500
STOGROUP SQL ERROR = > SQLCODE: code
Reason:
The Utility received the SQL error listed in this message when it tried to select a
stogroup through DB2.
PTGL500
PDA PROCESSING COMPLETE
Reason:
PDA statistics processing has completed.
Chapter 2: PS to PTUIX 393
PTGL Messages
PTGL501
STOGROUP CONTAINS NO PHYSICAL VOLUMES
Reason:
Indicates that the volumes specified in the storage group aren't found.
Action:
Correct the storage group to contain volumes that exist in your system.
PTGL501
PDA PROCESS - CATALOG SEARCH FAILED dataset_name
Reason:
The specified data set could not be found in the master catalog.
PTGL502
CATALOG UPDATE NOT PROCESSED DUE TO SINGLE PARTITION PROCESSIN.
Reason:
Catalog statistics are not calculated when only a single partition of a partitioned
tablespace is loaded or reorganized.
Action:
Run PDASTATS or RUNSTATS after the partition has been processed by the utility.
PTGL503
CATALOG UPDATE NOT PROCESSED DUE TO RESUME YES PROCESSING
Reason:
Catalog statistics are not calculated when RESUME YES is specified.
Action:
Run PDASTATS or RUNSTATS after the partition has been processed by the utility.
394 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL504
DSNXKAL (CATALOG ACCESS LOCATOR) FAILURE RC=rtn REAS=rsn
Reason:
The DB2 DSNXKAL module (Catalog Access Package) returned the specified internal
reason code and return code, both of which very according to the error.
PTGL601
DICTIONARY ERROR DURING:
Reason:
The utility encountered an error while using the compression dictionary.
PTGL602
VARIOUS DICTIONARY VALIDATION ERRORS
Reason:
The utility encountered an error while validating the dictionary.
PTGL603
for non-partitioned tablespaces: KEEPDICTIONARY SPECIFIED BUT COMPRESSION OFF
for partitioned tablespaces:
KEEPDICTIONARY SPECIFIED BUT COMPRESSION OFF, PART xxx
Reason:
Indicates that the tablespace (and partition, if applicable) being loaded or reorganized
does not have compression turned on, but the job specified KEEPDICTIONARY. The
keyword will be ignored. No dictionary action will be taken.
PTGL603
DDNAME EXCEEDED 8 CHARACTERS MAX LENGTH
Reason:
Indicates the ddname identified has exceeded the maximum length of eight characters.
The job terminates with a return code of 8 or greater.
Action:
Check that the ddname(s) are eight characters or less and rerun the job.
Chapter 2: PS to PTUIX 395
PTGL Messages
PTGL604
COMPRESSION DICTIONARY DOES NOT EXIST FOR TABLESPACE
Reason:
This warning indicates that the job specified KEEPDICTIONARY, but no compression
dictionary existed for the tablespace. A dictionary will be built. The utility will compress
all the records as well as the records being loaded.
PTGL605
COMPRESSION DICTIONARY DOES NOT EXIST FOR TABLESPACE PART xxx
Reason:
This warning indicates that the job specified KEEPDICTIONARY, but no compression
dictionary existed for indicated partition. A dictionary will be built. The utility will
compress all the records and the records being loaded.
PTGL606
PREFORMATTING ERROR - message
Reason:
Indicates that the preformatting routine did not complete successfully.
Action:
Check the message and see if you can determine the problem.
PTGL607
BUILD/KEEPDICTIONARY INVALID WITH RESTART
Reason:
You have specified the OUTPUT-CONTROL BUILD and KEEPDICTIONARY keywords, which
are invalid with a restart. The utility will override the KEEPDICTIONARY keyword and
rebuild the dictionary.
396 Message Reference Guide (PS to ZLB)
PTGL Messages
PTGL700
PTGL700 - DBD BUILD ERROR.
Reason:
There was an error attempting to build a copy of a DBD. An SVC dump with the title
'PTGL700 - DBD BUILD ERROR' was captured.
Action:
Supply Technical Support with the SVC dump information.
PTGL800
ddname DDNAME CANNOT BE DEFINED AS "DUMMY" or "SYSOUT"
Reason:
The DD named in this error cannot be defined as DUMMY.
PTGL800
ddname DDNAME CANNOT BE DEFINED AS "MOD.
Reason:
The DD named in this error cannot be defined as MOD.
Action:
Set the disposition to NEW, OLD or SHR.
PTGL800
SYSPRINT DD STATEMENT NO LONGER SUPPORTED. SYSPRINT is no longer a valid DD
name.
Action:
Use PTIMSG to specify the DD to contain the output messages instead.
PTGL801
ddname DDNAME CANNOT BE DEFINED AS "DUMMY" OR "SYSOUT"
Reason:
The DD named in this error cannot be defined as DUMMY.
Chapter 2: PS to PTUIX 397
PTGL Messages
PTGL810
QUIESCE FAILED ON OPEN TO SYSIN
Reason:
The utility was not able to quiesce before beginning the actual utility work.
PTGL811
QUIESCE FAILED ON OPEN TO SYSPRINT
Reason:
The utility was not able to quiesce before beginning the actual utility work.
PTGL815
QUIESCE UPDATE FAILED. => SQLCODE: code
Reason:
An attempted quiesce failed for the reason indicated by the SQL error code displayed in
this message.
PTGL820
ddname DDNAME FAILED ALLOCATION
Reason:
Indicates that the indicated ddname could not be allocated.
Action:
See any other messages produced at this time and check your JCL.
PTGL900
WARNING - MVS SAF ROUTER NOT ACTIVE
Reason:
This warning message indicates that the MVS SAF router is not active. Processing of the
job continues.
398 Message Reference Guide (PS to ZLB)
PTI Messages
PTGL913
SAF RACROUTE FAILED - SAFRC = X'aaaa', RC=X'bbbb', RS=X'cccccccc'
Reason:
Indicates that a SAF RACROUTE has failed. The values indicated are as follows: aaaa is
the SAF return code, bbbb is the RACF/MVS security product return code, and cccccccc is
the RACF/MVS security product reason code. Job processing terminates.
Action:
Contact your MVS security adminstrator for assistance in resolving this error.
PTGL920
WARNING - RACF/MVS SECURITY NOT ACTIVE
Reason:
This warning message indicates that MVS security is not currently active. Processing of
the job continues.
PTI Messages
Messages with the PTI prefix are generated from CA Service Desk.
PTI800I
Service Desk request CR:crnum opened for this ABEND
Reason:
An abend occurred in a DB2 tools program called by the driver, PTLDRIVM, and SDI(YES)
was specified in parmlib. CA Service Desk opened an issue for the abend, where crnum is
the call request number of the issue.
Action:
None.
Module: PTARECOV
Chapter 2: PS to PTUIX 399
PTI Messages
PTI801E
Service Desk request could not be opened
Reason:
An abend occurred in a DB2 tools program called by the driver, PTLDRIVM, and SDI(YES)
was specified in parmlib. PTLDRIVM was unable to open an issue for the ABEND in CA
Service Desk.
Action:
Refer to the PTI802I message.
Module: PTARECOV
PTI802I
CSDEREQ return codes: R15 = r15, R0 = r0, R1 = r1
Reason:
PTLDRIVM encountered an error while trying to open an issue for an abend in CA
Service Desk.
r15
Indicates the value of R15 returned by the CSDEREQ macro. The r15 value can be 4,
8, 12, 16, 20, 24, or 28.
If r15 is 4, the r0 value is one of the following:
1
Indicates a USD request was not opened because of MINTIME.
2
Indicates a USD request was not opened because of MAXCOUNT.
3
Indicates a USD request was not opened because the interface for this
particular product is currently disabled.
If r15 is 8, the r0 value is one of the following:
0
Indicates the CAISDI/els interface module, CSDEOPRQ, was not found.
1
Indicates the CAISDI/els interface was found, but the interface has not been
initialized. (The Event Control Structure was not found in this environment.)
400 Message Reference Guide (PS to ZLB)
PTI Messages
2
Indicates the CAISDI/els interface module was found and the Event Control
Structure was found, but this product is not defined to the interface. The
CAISDI/els startup control member, ELSSTART, does not contain a DEFINE
command for this product.
3
Indicates the CAISDI/els interface module was found, the Event Control
Structure was found, this product is defined to the interface, but this particular
event was not found. There was no event member for this product in the
CAI.CDBAEVNT library for this event.
4
Indicates the CA Common Services SOAP API module, CAS0PCLI, was not found.
If r15 is 12, the r0 value is one of the following:
0
Identifies the CAISDI/soap API return code.
1
Identifies the CAISDI/soap detailed return code.
If r15 is 16, the call to the CA Common Services SOAP API module (CASOPCLI) failed.
■
The r0 value is the CAISDI/soap API return code.
■
The r1 value is the CAISDI/soap API detailed return code.
If r15 is 20, the r0 value is one of the following:
1
Indicates the Event Parameter List is invalid: Eye catcher is missing.
2
Indicates the Event Parameter List is invalid: Length is inconsistent with the
parameters.
3
Indicates the Event Parameter List is invalid: Product name or event name is
missing.
4
Indicates the CA Service Desk request ticket was opened, but the request
number was not found in response packet. This should not occur, but it could
happen if the format of the XML reply packet was changed or if the XML packet
was incorrectly altered somewhere in the network path.
Chapter 2: PS to PTUIX 401
PTI Messages
5
Indicates there was an error creating summary text. r1 is the return code from
EDIT. This should not occur, but could if the Event Control Structure has been
corrupted (overlaid).
6
Indicates there was an error creating description text. r1 is the return code
from EDIT. This should not occur, but could if the Event Control Structure has
been corrupted (overlaid).
7
Indicates there was an error generating XML. This should not occur, but it could
happen if the CSDEOPRQ module itself was partially corrupted.
If r15 is 24, the R0 value is one of the following:
0
Indicates the CAISDI/els interface module (CSDEOPRQ) was not found.
4
Indicates an invalid attempt to update the Event Control Structure. This should
not occur, but could the Event Control Structure has been corrupted (overlaid).
5
Indicates the Product Event Table update was aborted because the table entry
was below the table boundary. This should not occur, but could if the Event
Control Structure has been corrupted (overlaid).
6
Indicates the Product Event Table update was aborted because the table entry
was above the table boundary. This should not occur, but could if the Event
Control Structure has been corrupted (overlaid).
8
Indicates the PC routine that updates the Product Event Table has been
removed. This should not occur, but could if the Event Control Structure has
been corrupted (overlaid).
If r15 is 28, the CAISDI/els interface module (CSDEOPRQ) has abended. The r1 value
is the abend code given to the ESTAEX routine. This should not occur, but could if
the Event Control Structure has been corrupted (overlaid), or if a calling program
has passed an invalid parameter. An invalid parameter would most likely cause a
S0C4 ABEND.
r0
Indicates the value of R0 returned by the CSDEREQ macro.
r1
Indicates the value of R1 returned by the CSDEREQ macro.
402 Message Reference Guide (PS to ZLB)
PTRR Messages
Action:
See reason description.
Module: PTARECOV
PTRR Messages
Messages with the PTRR prefix are generated from CA Rapid Reorg.
PTRR0094E
EXCP ERROR MESSAGE
Action:
For assistance, contact CA Support at http://ca.com/support.
PTRR016
REORG UNLOAD PROCESSING STARTED
Reason:
The Unload phase of processing has started.
PTRR016
REORG INDEX PROCESSING STARTED
Reason:
Reorg Index processing has begun.
PTRR016
REORG PROCESS STARTED - STANDARD VERSION
Reason:
The utility has started execution. The standard mode is executing.
PTRR017
REORG PROCESS STARTED - EXTENDED VERSION
Reason:
The utility has started execution. The extended mode is executing.
Chapter 2: PS to PTUIX 403
PTRR Messages
PTRR017
PROCESSING CANCELED - TABLESPACE HAS NO INDEXES
Reason:
A REORG TABLESPACE-INDEX was specified and there are no indexes associated with the
specified tablespace.
PTRR018
STOPPING TABLESPACE
Reason:
The tablespace is being stopped for the reorganization or load.
PTRR019
REORG PROCESSING COMPLETE
Reason:
Processing is complete.
PTRR020
STARTING TABLESPACE
Reason:
The tablespace is being started.
PTRR020
PROCESSING TABLESPACE STARTUP ACCESS MODE
Reason:
The tablespace is being restarted in the specified mode.
PTRR021
REGION SIZE BELOW =
Reason:
This informational message explains that your region size is below the region size
required because of specified options.
404 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR021
WORK DATASET FAILED TO OPEN - SEE JES MESSAGES FOR EXPLANATION
Reason:
The work data set could not be opened.
Action:
See the associated JES messages.
PTRR021
THE NUMBER OF SYSUT1(X) IS NOT SUFFICIENT FOR THE NUMBER OF SYSREC(X)
Action:
You must define as many SYSUT1s as SYSRECs.
PTRR022
REORG PROCESSING FAILED - START TABLESPACE IGNORED
Reason:
The utility processing has failed. The tablespace remains in STOP mode.
PTRR022
STARTUP ACCESS FOR DATASET FAILED - NO RESTART FOR THIS FUNCTION
Reason:
The utility was unable to start the data set.
Action:
See previous messages in your job output to determine the job status.
PTRR023
REORG UNLOAD PROCESSING COMPLETE
Reason:
Reorg unload processing has been completed.
Chapter 2: PS to PTUIX 405
PTRR Messages
PTRR023
REORG UNLOAD PROCESSING INCOMPLETE
Reason:
An aspect of the Reorg unload processing did not complete successfully.
Action:
See the other messages in this job for information about which tasks failed.
PTRR024
REORG PROCESSING COMPLETE
Reason:
Processing has completed.
PTRR024
STORAGE ACQUISITION FAILED FOR IO-BUFFERS - RESET BUFFERS
Action:
Increase the region size or lower the number of buffers for this job.
PTRR024
DISCARD DATASET FAILED TO OPEN - SEE JES MESSAGES FOR EXPLANATION
Reason:
The discard data set could not be opened.
Action:
See the associated JES messages.
PTRR024
REORG INDEX PROCESSING COMPLETE
Reason:
The Index phase of processing has finished.
406 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR025
UNLDDN DDNAME NOT FOUND
Reason:
The UNLDDN specified in the parameter must be the same as the ddname in the JCL.
PTRR026
WORKDDN DDNAME NOT FOUND
Reason:
The WORKDDN specified in the parameter must be the same as the ddname in the JCL.
PTRR027
REORG RELOAD PROCESSING STARTED
Reason:
The utility has started reloading the tablespace data.
PTRR027
REORG RELOAD PROCESSING STARTED
Action:
Reload processing has begun.
PTRR028
REORG RELOAD PROCESSING COMPLETE RCODE: returncode
Reason:
Reload processing has ended. The message also lists the return code.
PTRR028
REORG RELOAD PROCESSING INCOMPLETE
Reason:
Reload processing did not complete successfully.
Action:
See the other messages in the job output to determine which task(s) failed.
Chapter 2: PS to PTUIX 407
PTRR Messages
PTRR029
INDEX REBUILD TASKS SET TO : integer
Reason:
Indicates the number of rebuild tasks used in the job. If you do not specify
REBUILD-INDEX, it will be set to zero.
PTRR029
MAX SORTS SET TO: num
Reason:
Based on parameters and environments, the maximum number of sorts has been set to
num.
PTRR030
INDEX TASK PROCESSING ABENDED CONTACT Computer Associates
Action:
For assistance, contact CA Support at http://ca.com/support.
PTRR031
INDEX/TABLESPACE TASK PROCESSING ABENDED - CONTACT Customer Support
GROUP
Action:
For assistance, contact CA Support at http://ca.com/support.
PTRR032
IO-BUFFERS SET TO: size
Reason:
Based on parameters and environments, the number of IO-BUFFERS has been set to
num.
408 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR032
UNLOAD/RELOAD PROCESSING TERMINATED DUE TO REGION SIZE
Reason:
Unload or reload processing has been terminated due to an insufficient region size.
Action:
Increase the region size and restart the job.
PTRR033
THE NUMBER OF SYSUT1(X) MUST EQUAL THE NUMBER OF INDEXES
Reason:
Based on the parameters and environment, the number of SYSUT1 DDs must be equal
to the number of indexes.
PTRR033
SYSREC DATASET DOES NOT MATCH TABLESPACE TO BE PROCESSED
Reason:
Indicates that the work data sets do not match the tablespace being reorganized.
Action:
Check the UNLDDN to make sure the correct data sets are specified. A restart of a job
could be using a UNLDDN data set from a different job.
PTRR033
RELOAD PROCESS HALTED DUE TO KEYWORD “UNLOAD PAUSE”
Reason:
You specified the UNLOAD PAUSE keyword, which stops the reorganization after phase
1.
PTRR033
WITH MULTIPLE SYSUT1(X) MAXTASKS NEEDS TO BE SET WORKDDN COUNT
Reason:
MAXTASKS must equal the number of SYSUT1 data sets, if you are using more than one
SYSUT1.
Chapter 2: PS to PTUIX 409
PTRR Messages
PTRR034
IO-BUFFERS REDUCED BY HALF DUE TO REGION CONSTRAINT
Reason:
The number of I/O buffers had to be decreased by half because of the region size.
Action:
Increase the region size to avoid this problem.
PTRR034
REGION IS INSUFFICIENT FOR THE NUMBER OF IO DEVICES / SORTS
Reason:
Based on the environment, the region size must be increased and/or the number of
SYSRECs, SYSUT1s, or sorts must be decreased.
PTRR035
TABLESPACE FAILED CHECKSUM PROCESSING PHASE #1 - RECOVER TABLESPACE
Reason:
The checksum test comparing unloaded and reloaded data failed.
Action:
Check to see if the correct SYSREC data sets were specified (after a restart), or if there
was a hardware failure on the SYSREC device.
PTRR035
THE NUMBER OF MAXTASKS MUST EQUAL THE NUMBER OF INDEXES
Reason:
Based on the environment, the number for MAXTASKS must be equal to the number of
indexes.
PTRR036
ROWS UNLOADED: num - ROWS RELOADED num
Reason:
Indicates the number of rows unloaded from and reloaded into the tablespace.
410 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR037
SPACE UNLOADED: num - SPACE RELOADED num
Reason:
Indicates the checksum results for space unloaded and reloaded.
PTRR038
MAXTASKS TOO SMALL TO HANDLE REQUEST
Reason:
The value specified for MAXTASKS is not adequate for the number of SYSUT1s specified,
or the number of sorts required.
PTRR038
STARTING TABLESPACE RECHECK PROCESSING
Reason:
Recheck processing has begun.
PTRR039
TABLESPACE FAILED CHECKSUM PROCESSING PHASE #2 - RECOVERY TABLESPACE
Reason:
The checksum test failed.
Action:
Recover the tablespace.
PTRR039
ANOTHER ONLINE REORG IS CURRENTLY EXECUTING ON THIS TABLESPACE/INDEX
Reason:
Another job is currently executing on the specified tablespace or indexspace.
Action:
If desired, you can resubmit this job after the currently executing job is completed.
Chapter 2: PS to PTUIX 411
PTRR Messages
PTRR040
TABLESPACE RECHECK PROCESSING COMPLETED
Reason:
This message marks the end of the RECHECK processing.
PTRR040
UNKNOWN PAGE TYPE FOUND AT PAGE => pagenum
Reason:
The page type found at the page specified is of an unknown type. The page may be
broken, empty, or undefined. The page number is returned by the utility as a decimal
number.
Action:
If you receive a return code of 6 with this message, use one of the following methods to
determine the best recovery procedure:
1.
If there is an index on the tables in the tablespace, run a Select Count (*) for each
table in the tablespace being reorganized. If the count is the same as the output
rows, restart the job using a RESTART(PHASE).
Note: The tablespace will be stopped when the job ends. If you want to verify row
counts using a Select, you must start the tablespace in at least READ ONLY mode.
After you do the select, stop the tablespace again.
2.
Use PDA to do a PDA Display of the page. If it is not a broken page, restart the job
using a RESTART(PHASE).
3.
Use DSN1PRNT to print the page. If it is an empty page, restart the job using a
phased restart.
Note: DSN1PRNT requires you to specify the page number in hexadecimal format.
Since the utility returns the number in decimal format, you must translate it to hex
before running DSN1PRNT.
Alternately, you can run DSN1COPY with the CHECK option.
If the page is broken or the counts do not match, correct the pages in error and
restart the job from the beginning with a RESTART(BYPASS).
412 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR041
EDITPROC APPLICATION FAILED
Reason:
The edit procedure for the table has failed.
Action:
If you are reorganizing a table that uses an EDITPROC, the library containing the
EDITPROC must be specified in the STEPLIB DD.
If this is not the problem, verify that the edit procedure is functioning correctly.
PTRR042
RECORD FOUND GREATER THAN 32K - PAGE: pgnum PART: partnum
Reason:
The record found on the specified page is greater than 32K, the maximum record length.
This probably indicates a bad page.
PTRR043
STATUS: YY.DDD HH:MM:SS DATAID: NNN - ROW COUNT:......x
Reason:
The total row count for the partition displays if you specify the DISPLAY-STATUS
keyword in the JCL. The current date (julian) and time are denoted by YY.DDD
HH:MM:SS.
PTRR043
STATUS: PARTITION: partnum ROW COUNT: num
Reason:
The total row count for the partition displays if you specify the DISPLAY-STATUS
keyword.
PTRR044
INDEX xxxxxxxx.xxxxxxxx MUST BE RECOVERED
Reason:
Indicates that the specified non-clustering index must be recovered. Job processing has
terminated.
Chapter 2: PS to PTUIX 413
PTRR Messages
PTRR050
KEY ENTRY NOT FOUND IN INDEX
Reason:
A value has been found in a row that has no corresponding value in the index. This
probably indicates a bad index.
PTRR051
OBJECT IS NOT PARTITIONED
Reason:
You have specified a partition number for this object and the object is not partitioned.
Action:
Check the object definition and change the syntax.
PTRR052
INDEX SELECTED DOES NOT EXIST ON THIS SYSTEM
Reason:
The index selected does not exist on the specified DB2 subsystem.
PTRR053
TABLE SELECTED DOES NOT EXIST ON THIS SYSTEM
Reason:
The table selected does not exist on the specified DB2 subsystem.
PTRR057
PARTITIONED TABLESPACE CONTAINS NO PARTITIONED INDEXES - IE (EMPTY)
Reason:
A partitioned tablespace has been found with no partitioned indexes or partitioned
indexes that have no data.
414 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR058
USER CANCELED PROCESS THRU EXIT
Reason:
The reorganization job was canceled due to a user exit.
PTRR059
NUMBER OF PAGES EXCEEDS MAXIMUM ALLOWED FOR PARTITION
Reason:
The maximum size allowed for a partition depends on the number of partitions:
■
1 -16 partitions-4 gigabytes
■
17 - 32 partitions-2 gigabytes
■
33 - 64 partitions-1 gigabyte
PTRR060
TABLE - tablename
Reason:
Indicates the table name.
PTRR060
FASTLOAD INPUT DOES NOT MATCH PARTITION SELECTED FOR REORG
Reason:
Indicates that you are using FASTLOAD-DDN, and the data set contains data from a
partition other then the one which you are attempting to reorg. Processing has
terminated.
Action:
Resubmit the job specifying the same paritition from which the data originated.
Chapter 2: PS to PTUIX 415
PTRR Messages
PTRR060
TABLESPACE: tsname ALLOCATION FAILED
Reason:
Allocation has failed for the specified tablespace.
Action:
Check to see if the tablespace exists. Also, make sure you have the proper authorities to
allocate, read from, and write to the tablespace.
PTRR061
INDEX: indexname LISTCAT FAILED
Reason:
The utility had a problem trying to do a LISTCAT on the index data set. This might be due
to the data set being migrated, among other reasons.
PTRR062
VCAT DEFINED DATASET dsn MUST BE REALLOCATED PRIOR TO RESTART
Reason:
Allocation has failed for the specified VCAT-defined data set. You must perform a
manual define of the object before attempting to restart. This message appears only if
the object to be allocated is VCAT defined.
PTRR062
ALLOCATION FAILED FOR => dsn
Reason:
Allocation has failed for the specified data set.
Action:
Check to see if the data set exists. Also, make sure you have the proper authorities to
allocate, read from, and write to the data set.
416 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR062
INDEX: indexname REDEFINITION FAILED
Reason:
The redefinition of the index data set failed.
Action:
Check for system messages in the job output for the cause of the error. Some causes of
failure are as follows: space not available, authorization lacking to delete or define the
data set, or volume not mounted.
PTRR062
TABLESPACE: tsname REDEFINITION FAILED
Reason:
The redefinition of the tablespace data set failed.
Action:
Check for system messages in the job output for the cause of the error. Some causes of
failure are as follows: space not available, authorization lacking to delete or define the
data set, or volume not mounted
PTRR063
INDEX: indexname REDEFINITION COMPLETE
Reason:
The redefinition of the tablespace data set was successful.
PTRR063
ALLOCATION COMPLETE FOR => dsn
Reason:
The specified data set has been successfully allocated.
PTRR063
TABLESPACE: tsname REDEFINITION COMPLETE
Reason:
The redefinition of the tablespace data set was successful.
Chapter 2: PS to PTUIX 417
PTRR Messages
PTRR063
INDEX: indexname OPENED FOR REBUILD
Reason:
The utility has opened the specified index for a rebuild.
PTRR063
ALLOCATION COMPLETE FOR tablespace_name
Reason:
The utility was able to successfully allocate space for the tablespace named in the
message.
PTRR065
TABLESPACE: tsname SMS FAILED RECALLING DATASET
Reason:
The specified tablespace could not be recalled.
PTRR065
INDEX: indexname ADD VOLUME FAILED
Reason:
The utility was not able to add the candidate volume(s) for the index data set named in
the error message.
Action:
Check to see if the volume exists.
PTRR065 TABLESPACE: tsname ADD VOLUME FAILED
The utility was not able to add the candidate volume(s) for the tablespace data set
named in the error message.
Check to see if the volume exists.
418 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR066
dsname - DATASET FAILED OPEN
Reason:
Due to environmental conditions, the specified data set failed open.
Action:
Contact your MVS Systems Programmer.
PTRR067
WORKDDN => ddname - DOESNT MATCH TABLESPACE TO BE RELOADED
Reason:
Indicates that the WORKDDN data sets (SYSRECs) do not match the tablespace being
reloaded.
Action:
Check the WORKDDN to make sure the correct data sets are specified. A restart of a job
could be using a WORKDDN data set from a different job.
PTRR067
OUTDDN => out-ddname - DOESNT MATCH TABLESPACE TO BE RELOADED
Reason:
Indicates that the OUTDDN data sets (SYSRECs) do not match the tablespace being
reloaded.
Action:
Check the OUTDDN to make sure the correct data sets are specified. A restart of a job
could be using a OUTDDN data set from a different job.
PTRR068
TABLE ENTRY NO LONGER FOUND - LOAD CANCELED
Reason:
This error indicates that the object being reloaded was not located. Ensure that the
table still exists. This can occur when if the object was dropped during unload pause and
then the job was restarted.
Chapter 2: PS to PTUIX 419
PTRR Messages
PTRR069
WORKDDN => ddname CONTAINS A INDEX RECORD WITHOUT A HEADER
Reason:
An internal inconsistency has been detected in the indicated data set.
PTRR069
WORKDDN => ddname DOESNT MATCH INDEX TO BE RELOADED
Reason:
Indicates that the WORKDDN data sets (SYSUT1s) do not match the index being
reloaded.
Action:
Check the WORKDDN to make sure the correct data sets are specified. A restart of a job
could be using a WORKDDN data set from a different job.
PTRR070
VSAM CONTROL BLOCK FAILED VERIFICATION
Reason:
An integrity check of the VSAM control block has failed.
PTRR071
THE DISCARD I/O PROCESSOR ABENDED
Reason:
An internal error has occurred.
PTRR072
THE OPEN/CLOSE PROCESSOR ABENDED
Action:
For assistance, contact CA Support at http://ca.com/support.
420 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR072
TABLESPACE: tsname ACQUIRING DSP WORKAREA
Reason:
The specified tablespace is acquiring dataspace workarea.
PTRR072
TABLESPACE: tsname OPENED FOR RELOAD
Reason:
Reload processing has begun for the specified tablespace.
PTRR073
TABLESPACE: tsname RELOAD: n ROWS
Reason:
The number of tablespace rows in tables that were selected to be reloaded.
PTRR074
TABLESPACE: tsname RPL ERROR RCODE: returncode REAS: reasoncode
Action:
Refer to the return code and reason code for more information.
PTRR074
INDEX: indexname RPL ERROR: error-code
Action:
For assistance, contact CA Support at http://ca.com/support.
PTRR075
INDEX: object EXCEEDED ALL AVAILABLE EXTENDS OR NEEDS ADDITIONAL VOLUMES
Reason:
Indicates that additional space is needed to process the indicated index or tablespace.
Chapter 2: PS to PTUIX 421
PTRR Messages
PTRR076
INDEX: indexname ALLOCATION FAILED
Reason:
Allocation has failed for the specified index.
Action:
Check to see if the index exists. Also, make sure you have the proper authorities to
allocate, read from, and write to the index.
PTRR077
A TABLESPACE UNLOAD TASK HAS FAILED - NO RELOAD TASKS ARE EXECUTING. THE
REORG PROCESS WILL BE STOPPED AND ALL DATASETS RESTARTED
Reason:
Indicates that the utility failed in the tablespace unload task and no reload tasks are
executing.
Action:
See the preceding messages for more information about the task failure.
PTRR077
A TABLESPACE UNLOAD TASK HAS FAILED - NO RELOAD TASKS ARE EXECUTING. ALL
REMAINING UNLOAD TASKS WILL BE CANCELED
Reason:
Indicates that utility failed in the tablespace unload task and no reload tasks are
executing.
Action:
See the preceding messages for more information about the task failure.
422 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR077
A TABLESPACE UNLOAD TASK HAS FAILED - RELOAD TASKS ARE EXECUTING. THE
REORG PROCESS WILL CONTINUE UNTIL ALL RELOAD TASKS HAVE COMPLETED
Reason:
Indicates that the utility failed in the tablespace unload task but continued executing
reload tasks for the other partitions.
Action:
See the preceding messages for more information about the task failure.
PTRR077
A TABLESPACE UNLOAD TASK HAS FAILED - RELOAD TASKS ARE EXECUTING. REORG
MAY NEED TO BE RESTARTED OR RECOVERED BEFORE ACCESSING DATASETS
Reason:
Indicates that the utility failed in the tablespace unload task but continued executing
reload tasks.
Action:
See the preceding messages for more information about the task failure.
PTRR078
A TABLESPACE UNLOAD TASK HAS FAILED
Reason:
For assistance, contact CA Support at http://ca.com/support.
PTRR079
INDEX UPDATE PROCESSING WAS INCOMPLETE
Reason:
An aspect of the reorg index update processing did not complete successfully.
Action:
See the other messages in this job for information about which tasks failed.
Chapter 2: PS to PTUIX 423
PTRR Messages
PTRR079
MAX DATASPACE PAGE FRAMES USED: pages
Reason:
This message displays the maximum number of page frames.
PTRR080
TABLESPACE: creator.tablespacename.part RENAME COMPLETE
Reason:
For DATA-AVAILABLE HIGH processing of the specified tablespace, the renaming of the
temporary VSAM data sets has been completed successfully.
PTRR081
INDEX : creator.indexname.part RENAME COMPLETE
Reason:
For DATA-AVAILABLE HIGH processing of the specified index, the renaming of the
temporary VSAM data sets has been completed successfully.
PTRR081
FINAL REORG ANALYSIS
Reason:
This message provides a comprehensive summary of the reorganization job. Each
tablespace partition and index or index partition that was reorganized is identified as
COMPLETED or FAILED - RECOVER REQUIRED.
If the utility indicates that recovery is required, that object needs to be recovered. If
only one partition is listed as requiring recovery, only that partition needs to be
recovered. If NO RECOVER is indicated, processing did not complete but recovery is not
necessary.
424 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR082
STARTUP PROCESSING FAILED THE REORG PROCESS WILL BE STOPPED AND ALL
DATASETS RESTARTED or ALL REMAINING UNLOAD TASKS WILL BE CANCELED
Reason:
Startup processing has failed.
Action:
See other messages issued during execution for further information.
PTRR082
SYSREC OBID X'nnnn' NOT FOUND IN CATALOG
Reason:
In this message, 'nnnn' refers to the OBID found in the SYSREC file. An error occurred in
one of the JCL Reorg steps. No reference to the specified obid was found in the system
catalog
Action:
Verify that each of the SYSREC and SYSUT1 data sets within each step has a different
name.
PTRR083
INDEX REBUILD PROCESSING WAS INCOMPLETE. REORG PROCESSING WILL THEN
TERMINATE AND ALL DATASETS RESTARTED
Reason:
Index rebuild processing has failed.
Action:
See the summary in message PTRR081 for a complete description of the state of the
indexes.
Chapter 2: PS to PTUIX 425
PTRR Messages
PTRR083
INDEX REBUILD PROCESSING WAS INCOMPLETE. SOME INDEXES MAY NEED TO BE
RESTARTED OR RECOVERED BEFORE ACCESSING
Reason:
Index rebuild processing has failed.
Action:
See the summary in message PTRR081 for a complete description of the state of the
indexes.
PTRR083
INDEX REBUILD PROCESSING WAS INCOMPLETE. INDEX REBUILD PROCESSING STILL
ACTIVE AND WILL BE ALLOWED TO COMPLETE
Reason:
Index rebuild processing has failed.
Action:
See the summary in message PTRR081 for a complete description of the state of the
indexes.
PTRR084
WORKDDN DRIVER FOR NCI KEYS FAILED
Reason:
The update task for a non-clustering index failed.
PTRR084
WORKDDN DRIVER FOR NCI UPDATE FAILED
Reason:
The update task for a non-clustering index failed.
PTRR085
THE STRIP INDEX PROCESSOR ABENDED
Action:
For assistance, contact CA Support at http://ca.com/support.
426 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR085
INDEX: indexname DID NOT REBUILD - INDEX OK
Reason:
Indicates the utility is unable to rebuild the specified index.
PTRR086
INDEX: indexname FAILED - REBUILD - AUTORECV
Reason:
Indicates that processing for the indicated index failed during the reload. The utility will
automatically attempt to recover the index.
Action:
See other messages issued during execution for more information.
PTRR086
A TABLESPACE UNLOAD/RELOAD TASK HAS FAILED - EXECUTION CANCELLED
THE REORG PROCESS WILL BE STOPPED AND ALL DATASETS RESTARTED
Reason:
A DATA-AVAILABLE HIGH reorg job has failed during the unload phase. Because none of
the reloads have yet been started, the reorg job is terminated and the original VSAM
data sets have been restarted. The restart records have been deleted.
The tablespace is exactly as it was before the reorg was started.
The job is not restartable, but it can be rerun from the beginning.
PTRR087
INDEX: indexname SWITCHING TO SORT
Reason:
The specified index is being sent directly to the sort task.
PTRR088
INDEX: indexname FAILED DURING RENAME
Reason:
The utility failed to rename the specified index.
Chapter 2: PS to PTUIX 427
PTRR Messages
PTRR089
INDEX : user.indexspace.001 TARGET DSN MISSING or
TABLESPACE: database.tablespace.001
TARGET DSN MISSING
Reason:
You forgot to define the B00x data sets for the specified object before running your
DATA-AVAILABLE HIGH reorg. Because the object is user-defined (not stogroup-defined)
with SPACE-DEFN NO, the utility cannot define the B00x data sets for you.
Action:
Define the target data sets and rerun the job.
PTRR090
THE REORG MAIN TASK MANAGER ABENDED. SEE THE FINAL ANALYSIS MESSAGE FOR
ANY RECOVERY CONDITIONS.
Reason:
The reorg main task manager job has abended.
Action:
See the final analysis message (PTRR081) for any recovery conditions.
PTRR091
TABLESPACE: tsname APPLICATION ABEND - RELOAD
Reason:
Indicates that the application abended during the reload of the indicated tablespace.
This might be because of an abend or a trapped reason.
Action:
See other messages issued during execution for more information.
428 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR092
"PART" STATEMENT CONTAINS AN INVALID PARTITION VALUE
Reason:
You have specified a partition that does not exist for the tablespace or index being
reorganized.
Action:
Check the index definition and JCL.
PTRR094
UTLEXCP ERR RC X'00000058' REAS X'00000000'
Reason:
RIO returned with an error condition but did not format an error message. The return
code (RC) and reason code (REAS) are specified in the message.
PTRR100
INDEX KEYS LOADED ........... num
Reason:
The index keys have been reloaded.
PTRR100
USER CANCELED PROCESS THRU EXIT
Reason:
The reorganization job was canceled due to a user exit.
PTRR101
INDEX: indexname HSP FAILURE: RSN=error-code
Reason:
A hiperspace error has been detected.
Chapter 2: PS to PTUIX 429
PTRR Messages
PTRR101
TABLESPACE: tsname HSP FAILURE: RSN=error-code
Reason:
A hiperspace error has been detected.
PTRR101
LEAF PAGES .................. num
Reason:
The number of leaf pages loaded.
PTRR102
NONLEAF PAGES ............... num
Reason:
The number of nonleaf pages loaded.
PTRR103
INDEX LEVELS ................ num
Reason:
The number of index levels after the load.
PTRR104
TOTAL PAGES ACTIVE .......... num
Reason:
The number of total active pages after the load.
PTRR105
INDEX: indexname HSP=hsp-pages DSP=dsp-pages
Reason:
This informational message gives the amount of hiperspace (HSP) and dataspace (DSP)
used. Both values are given in 4K pages.
430 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR105
INDEX indexname HAS BEEN RELOADED:
Reason:
The index name being loaded.
PTRR106
NUMBER OF VSAM PUT WAITS .... num
Reason:
The number of VSAM PUT WAITS.
PTRR106
INDEX: indexname UNLOAD: num ROWS
Reason:
The number of rows indicated in the message have been unloaded from the named
index.
PTRR107
INDEX: indexname OPENED FOR UNLOAD
Reason:
The index named in the message has been opened. It will be unloaded next.
PTRR107
INDEX KEYS UPDATED .......... num
Reason:
The number of index keys that were updated.
PTRR108
INDEX PAGES MODIFIED ........ num
Reason:
The number of index pages that were modified.
Chapter 2: PS to PTUIX 431
PTRR Messages
PTRR109
INDEX: indexname HSP DIAG: RC=error-code RSN=error-code
Reason:
An internal diagnostic condition has been detected.
PTRR109
INDEX: indexname HSP FAILED: RTN=routine RSN=error-code
Reason:
An internal diagnostic condition has been detected.
PTRR110
TABLESPACE ROWS LOADED ...... num
Reason:
The number of tablespace rows that were loaded.
PTRR111
TABLESPACE PAGES WRITTEN .... num
Reason:
The number of tablespace pages written.
PTRR112
ROWS LOADED ..... num
Reason:
The number of rows loaded.
PTRR113
PAGES LOADED .... num
Reason:
The number of pages loaded for the table named in message PTRR115.
432 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR114
TABLESPACE: tsnam
Reason:
The tablespace name.
PTRR115
TABLE: tablenam
Reason:
The name of the table being loaded.
PTRR116
tablespace type TYPE
Reason:
This informational message displays the type of tablespace (Simple, Segmented,
Partitioned) being processed.
PTRR117
pagesize PAGE SIZE
Reason:
This informational message displays the page size.
PTRR118
num NUMBER OF PARTS
Reason:
This informational message displays the number of partitions.
PTRR119
num SEGMENT SIZE
Reason:
This informational message displays the segment size.
Chapter 2: PS to PTUIX 433
PTRR Messages
PTRR120
TABLESPACE ROWS PROCESSED num
Reason:
This informational message displays the number of rows processed.
PTRR121
TABLESPACE PAGES READ ....... num
Reason:
The number of tablespace pages read.
PTRR122
TABLESPACE DROPPED ROWS ..... num
Reason:
The number of dropped rows for the tablespace.
PTRR123
TABLESPACE DROPPED SPACE .... num
Reason:
The amount of dropped space for the tablespace.
PTRR124
TABLESPACE DELETED ROWS.... num
Reason:
The number of rows deleted due to ROW-PROCESSING.
PTRR125
TABLESPACE DELETED SPACE .... num
Reason:
The amount of deleted space.
434 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR126
TABLESPACE PAGES IO WAIT .... num
Reason:
The tablespace pages I/O wait.
PTRR127
TABLESPACE RELOCATED ROWS ... num
Reason:
The number of relocated rows in the tablespace.
PTRR127
SYSREC PAGES WRITTEN ........ num
Reason:
The number of SYSREC pages written.
PTRR128
SYSREC PAGES IO WAIT .......... num
Reason:
The SYSREC pages I/O WAIT.
PTRR128
TABLESPACE RELOCATED RESET .. num
Reason:
The number of rows reset to their original page.
PTRR129
SYSUT1 PAGES WRITTEN ........ num
Reason:
The number of SYSUT1 pages written.
Chapter 2: PS to PTUIX 435
PTRR Messages
PTRR130
SYSUT1 PAGES IO WAIT ........ num
Reason:
The SYSUT1 pages I/O wait.
PTRR131
TABLESPACE REORG PAGES REQ .. num
Reason:
The number of pages required for the tablespace reorganization.
PTRR132
ROWS PROCESSED .. num
Reason:
The number of rows processed.
PTRR132
ROWS SELECTED ... num
Reason:
The number of rows selected due to ROW-PROCESSING.
PTRR133
TABLESPACE: tsnam
Reason:
The tablespace name.
PTRR134
TABLE: tablenam
Reason:
The table name.
436 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR140
INDEXSPACE: idxnam
Reason:
The indexspace name.
PTRR141
INDEX ROWS UNLOADED ......... num
Reason:
The number of index rows unloaded.
PTRR142
INDEXSPACE PAGES READ ....... num
Reason:
The number of indexspace pages read.
PTRR143
INDEXSPACE PAGES IO WAIT .... num
Reason:
The indexspace pages I/O wait.
PTRR160
DICTIONARY: [KEPT | BUILT], ENTRIES..................entries
Reason:
Indicates whether the compression dictionary has been built or kept during
compression. It also gives the number of dictionary index entries. The entries number is
512, 1024, 2048, 4096, or 8192.
Note: Messages PTRR160 - PTRR168 always appear together to give data compression
statistics. See the accompanying message descriptions for more information.
Chapter 2: PS to PTUIX 437
PTRR Messages
PTRR161
PAGES....................pages [(xx PAGES RESERVED)]
Reason:
This message gives the number of data pages used by the compression dictionary. The
number of pages reserved for the dictionary is also listed, if it is different from the
number of pages used.
PTRR162
KB WITHOUT COMPRESSION.................noncompbytes
Reason:
This message gives the total number of uncompressed kilobytes (KB=1024 bytes) for the
loaded or reorganized data, rounded up to the nearest KB. This number is for the data
only, after any edit procedures are applied; it does not include any row or page
overhead.
PTRR163
KB WITH COMPRESSION.................compbytes
Reason:
This message gives the total number of compressed kilobytes (KB=1024 bytes) for the
loaded or reorganized data, rounded up to the nearest KB. This number is for the data
only; it does not include any row or page overhead.
PTRR164
PCT BYTES SAVED.......................pctsaved
Reason:
This message gives the percentage of bytes saved for the loaded or reorganized data as
a result of the compression.
PTRR165
PCT ROWS COMPRESSED..................pctrowcompt
Reason:
This message gives the percentage of all the rows loaded or reorganized that were
compressed. Rows whose length changed because of an edit procedure but were not
compressed are counted as uncompressed. This is different from DB2's DSNU244I
message
438 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR166
PAGES W/O COMPRESSION................noncomppages
Reason:
This message gives the estimated number of DB2 pages required by the uncompressed
data rows that were loaded or reorganized. This estimate includes space required for
page and row overhead, PCTFREE, FREEPAGE, header pages, one spacemap page. The
number is rounded up to the next integer.
PTRR167
PAGES WITH COMPRESSION................comppages
Reason:
This message gives the estimated number of DB2 pages required by the compressed
data rows that were loaded or reorganized. This estimate includes space required for
dictionary pages, page and row overhead, PCTFREE, FREEPAGE, header pages, one
spacemap page. The number is rounded up to the next integer. It is possible that
comppages could be larger than the value noncomppages in message PTRR166, due to
the data dicitonary.
PTRR168
PCT DB2 PAGES SAVED................pctpagessaved
Reason:
This message gives an estimate of the percentage of DB2 pages saved by compressing
the loaded or reorganized data. If the comppages of message PTRR167 is larger than the
noncomppages of message PTRR167, pctpagessaved is a negative number, indicating
the compressed data and data dictionary require more space than the uncompressed
data.
PTRR200
INPUT DRIVERS SET TO: integer
Reason:
Indicates the number of unload tasks that have been allocated.
Chapter 2: PS to PTUIX 439
PTRR Messages
PTRR201
OUTDDN DEVICES SET TO: integer
Reason:
The number of OUTDDN devices available to write the SYSREC data sets to is indicated
by this message.
PTRR202
INDEX UPDATE TASKS SET TO: integer
Reason:
Indicates the number of update tasks. The utility uses the smaller of the value set in
UPDATE-TASKS and the number of non-clustering indexes (plus the number of partitions
in the clustering index, if RECLUSTER YES is specified).
PTRR203
WORKDDN DEVICES SET TO: integer
Reason:
Indicates the number of work data sets used in the job.
PTRR204
STRIP INDEX TASKS SET TO : 000
Reason:
Indicates the number of strip index tasks that have been allocated.
PTRR207
TABLESPACE: tsname OPENED FOR UNLOAD
Reason:
The specified tablespace has been opened for unload.
PTRR208
TABLESPACE: tsname UNLOAD: n ROWS SELECT: n ROWS
Reason:
This message specifies the number of rows unloaded and selected from the named
tablespace.
440 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR212
DATA FIELD MUST BE (Y)ES OR (N)O
Reason:
The field specified in the error must be set to YES or NO.
PTRR214
TABLESPACE,INDEX,TABLESPACE-INDEX, OR TABLE-INDEX KEYWORD MISSING
Reason:
You must specify the type of object you will be reorganizing by specifying an object
keyword. Valid object keywords are TABLESPACE INDEX TABLESPACE-INDEX
TABLE-INDEX
PTRR215
DATA FIELD NOT VALID OR > 999999999
Reason:
A required data filed is missing or is not a numeric value less than 999,999,999.
Action:
Check the syntax.
PTRR215
DATA FIELD NOT VALID OR > 9999
Reason:
A required data field is missing or is not a numeric value less than 9999.
Action:
Check the syntax.
Chapter 2: PS to PTUIX 441
PTRR Messages
PTRR218
SPACE-DEFN ENTRIES TO PARTITIONS DO NOT MATCH
Reason:
The space definition calculations you have specified do not correspond to the number of
partitions in the tablespace or indexspace.
Action:
Check the syntax of the space definition.
PTRR219
SORTSIZE/SORTLIMIT MUST BE IN FORMAT OF 1K OR 1M
Reason:
The SORTSIZE must be in the format of MAX, 1K, or 1M.
SORT-LIMIT, an installation parameter, must also be in the same format.
PTRR220
SELECT / DELETE STATEMENT EXCEEDS 800 CHARACTERS
Reason:
Your SELECT or DELETE statement exceeds 800 characters.
PTRR221
EXIT PROCESSING NOT ALLOWED FOR TYPE 1 REORG
Reason:
You have specified an exit for a type 1 reorg, which is not allowed.
PTRR222
DISPLAY-STATUS NOT NUMERIC OR > 99,999,999,999
Reason:
You have specified an invalid value for DISPLAY-STATUS. Valid values are numerics less
than 99,999,999,999.
442 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR223
STATEMENT MUST BEGIN WITH SELECT OR DELETE
Reason:
The ROW-PROCESSING statement is not in the correct format. It must begin with SELECT
or DELETE.
PTRR224
NO TABLE NAME FOUND
Reason:
No table name was found in your SELECT or DELETE statement.
Action:
Check the SQL.
PTRR225
NO "WHERE" KEYWORD FOUND
Reason:
No WHERE keyword was found in your SELECT or DELETE statement.
Action:
Check the SQL.
PTRR226
BASIC "WHERE" CLAUSE STRUCTURE ERROR
Reason:
The WHERE clause of the job syntax contains errors. Its structure should be WHERE
column_name operator constant.
Chapter 2: PS to PTUIX 443
PTRR Messages
PTRR226
WHEN/NULLIF/DEFAULTIF STRUCTURE INVALID
Reason:
The WHEN, NULLIF, or DEFAULTIF clause is not in the correct format.
Action:
See the documentation of the utility you are using for details on the correct syntax.
PTRR227
COLUMN NAME IS INVALID
Reason:
The specified column name is invalid.
PTRR228
ENDING LOCATION MUST GREATER / EQUAL TO STARTING LOCATION
Reason:
You have specified starting and ending locations for a field and have specified an ending
location less than the starting location. You must specify an ending location equal to or
greater than the starting location.
PTRR229
POSITION FIELD SYNTAX ERROR
Reason:
The POSITION portion of the INTO clause has a syntax error.
PTRR230
DATATYPE IS INVALID
Reason:
The data type specified in the line indicated is not valid.
444 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR231
DATATYPE LENGTH IS INVALID
Reason:
The length specified is not valid for the data type specified.
PTRR232
BASIC STRUCTURE ERROR
Reason:
The line indicated in this message contains a syntax error.
PTRR233
INITIAL (X) MAY HAVE NO OTHER PARMS
Reason:
You have included an extraneous parameter in the INITIAL clause.
PTRR234
INITIAL (X) STRUCTURE ERROR
Reason:
The INITIAL clause indicated in this message contains an error.
PTRR235
NULLIF/DEFAULTIF STRUCTURE ERROR
Reason:
The NULLIF or DEFAULTIF clause is not in the correct format.
Action:
See the documentation of the utility you are using for details on the correct syntax.
Chapter 2: PS to PTUIX 445
PTRR Messages
PTRR238
RESTART FOR QUICKCPY FOUND, RESTART INVALID, CONTROL CARDS CHANGED
Reason:
This job cannot be restarted because the control cards specifying the utility options
have been modified since the original execution of the job.
Action:
Remove the restart parameter or restore the options to their previous settings before
resubmitting the job.
PTRR238
INVALID ROW LENGTH FOR TABLE
Reason:
An invalid row length was specified for the table.
PTRR239
FASTLOAD INPUT TABLE DOES NOT EXIST IN REORG TABLESPACE
Reason:
The table you specified to unload in the syntax was not found in the tablespace selected
for reorg.
Action:
Check the table and tablespace names.
PTRR240
SEGMENTED TABLESPACE SQL SELECT PROCESSING COMPLETED RC=>xx
Reason:
Indicates that the utility has successfully completed the SELECT processing to select an
arbitrary row of data from the tables in the tablespace prior to setting the copy pending
flag. Any time a segmented tablespace is being reorganized, the utility performs this SQL
SELECT processing to update the DBD and ensure that the tablespace data is
synchronized.
446 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR240
TABLESPACE LOAD FOR DDNAME => ddname - ABENDED
Action:
For assistance, contact CA Support at http://ca.com/support.
PTRR241
PREVIOUS EXECUTION WAS CANCELLED. BYPASS SYSREC WAS SELECTED. EXAMINE
PREVIOUS EXECUTION TO DETERMINE WHAT OBJECTS REQUIRE RECOVERY.
Reason:
Because BYPASS-SYSREC was selected in the original run of this job, a restart is not
possible.
Action:
Look at the output messages from the previous run to determine which objects had not
completed the reorganization and might need to be recovered.
PTRR241
INDEX LOAD FOR DDNAME => ddname - ABENDED
Action:
For assistance, contact CA Support at http://ca.com/support.
PTRR242
INDEX: indexname REDEFINITION COMPLETE
Reason:
The utility has finished redefining the specified index.
PTRR242
INDEX: indexname OPENED FOR REBUILD
Reason:
The specified index has been opened for rebuild.
Chapter 2: PS to PTUIX 447
PTRR Messages
PTRR242
INDEX: indexname OPENED FOR STRIP
Reason:
The specified index has been opened to strip the index keys out.
PTRR242
INDEX: indexname OPENED FOR UPDATE
Reason:
The specified index has been opened for update.
PTRR243
INDEX: indexname RELOAD: n KEYS
Reason:
The utility has reloaded the number of keys specified into the index indicated.
PTRR244
INDEX: indexname UPDATE: n KEYS
Reason:
The utility has updated the number of keys specified in the index indicated.
PTRR244
INDEX: indexname STRIP: n KEYS
Reason:
The utility has stripped out the number of keys specified from the index indicated.
PTRR245
TABLESPACE tname n ROWS
Reason:
Indicates the number of rows unloaded for the named tablespace during standard
execution.
448 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR246
COPY DATA PROCESS ENDED - RETURN CODE rtn
Reason:
Processing has abendeed. Review the return code information.
PTRR246
COPY DATA PROCESS ABENDED - CODE rtn
Reason:
Processing has abendeed.
Action:
Review the return code information.
PTRR288
INDEX database.indexspace SWITCH TO SORT (TYP 2 DUP)
Reason:
REBUILD-INDEX NO is specified but there is a non clustering type 2 index that is not
unique.
Action:
Rebuild the index to place the RIDs in the correct order.
PTRR300
THE NUMBER OF WORKDDNS MUST BE AT LEAST => num
Reason:
Indicates the number of WORKDDNs required.
Action:
Define the number of WORKDDNs specified in your job.
Chapter 2: PS to PTUIX 449
PTRR Messages
PTRR301
THE NUMBER OF OUTDDN(X) CANNOT BE ZERO
Reason:
The only time you can omit OUTDDN data sets (SYSREC) is when you specify
BYPASS-SYSREC, RECLUSTER YES SORTDATA YES.
BYPASS-SYSREC can only be executed with SORTDATA YES. If the tablespace has no
clustering index, the utility automatically converts the job to SORTDATA NO RECLUSTER
NO, which cannot be BYPASS-SYSREC. Therefore, the job requires OUTDDN data set(s).
PTRR302
THE NUMBER OF WORKDDN(X) CANNOT BE ZERO
Reason:
The number of WORKDDNs data sets (SYSUT1) cannot be zero. Change the number of
OUTDDNs in your job.
Action:
If you have specified BYPASS-SYSUT1, but the tablespace has non-clustering indexes,
you must define one WORKDDN.
PTRR303
DISCARD TO OUTPUT DATASET NOT POSSIBLE DURING THIS RESTART
Reason:
Indicates that discard processing is not available during this restart because a tablespace
was partially unloaded before the job failed.
PTRR304
EXTENDED VERSION WAS SWITCHED TO STANDARD VERSION
Reason:
Your Extended Mode reorg job has been switched to the Standard Mode, because not
all requirements for running Extended Mode were met.
PTRR305
THE NUMBER OF OUTDDNS EXCEEDED MAX - SET TO 16
Reason:
User specified too many DDs. The utility has set the number of OUTDDNs to 16.
450 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR306
THE NUMBER OF WORKDDNS EXCEEDED MAX - SET TO 17
Reason:
User specified too many DDs. The utility has set the number of WORKDDNs to 17.
PTRR307
FASTLOAD INPUT USAGE - NUMBER OF OUTDDNS SET TO 1
Reason:
User specified too many DDs. The utility has set the number of OUTDDNs to 1.
PTRR310
DATA AVAILABILITY SET TO => [HIGH | NORMAL]
Reason:
The DATA-AVAILABLE keyword or parmlib parameter value is given (HIGH or NORMAL).
PTRR311
RESTART TABLE TOO SMALL FOR TABLESPACE
Reason:
The tablespace is too large for the restart table.
Action:
Make the restart table a 32 KB table.
PTRR320
DATASET HAS BEEN msg
Reason:
Indicates that the specified action was taken on the named data set. The variable “msg”
indicates one of the following:
■
ROLLED BACK TO-Because an error occurred during the reorg, the data sets were
rolled back to their original names.
■
RENAMED TO-The reorg was successful, so the data sets were renamed.
Chapter 2: PS to PTUIX 451
PTRR Messages
PTRR321
IDCAMS ERROR RENAMING dsn TO dsn
Reason:
An IDCAMS error occurred during the renaming of the indicated data set.
PTRR322
IDCAMS ERROR OCCURRED WHILE ROLLING BACK DATASET RENAMES
DATASET dsn COULD NOT BE RENAMED BACK TO dsn
AND WILL HAVE TO BE RENAMED MANUALLY
THE TABLESPACE WILL BE LEFT IN STOPPED STATUS
Reason:
An IDCAMS error occurred during the rolling back of the indicated data set. Additional
information is provided so that you know which data set to rename manually.
PTRR323
STARTING DATASET RENAME PROCESS
Reason:
The utility has begun to rename the data sets it used for the reorg.
PTRR324
DATASET RENAME PROCESS HAS COMPLETED SUCCESSFULLY
Reason:
The specified process completed as expected.
PTRR325
DATASET RENAME ROLLBACK WAS SUCCESSFUL
Reason:
The rollback of the data set names completed successfully.
PTRR326
DATASET RENAME ROLLBACK WAS INCOMPLETE
Reason:
The rollback of the data set names did not complete.
452 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR327
DATASET RENAME PROCESS HAS FAILED
Reason:
The renaming of the data sets has failed.
PTRR328
DATASET RENAME ROLLBACK COMMENCING
Reason:
Because the renaming process failed, the utility will roll back the names of the data sets.
PTRR329
DATASET ARRAY HAS OVERFLOWED
Reason:
An internal error occurred.
PTRR330
PLEASE CONTACT Customer Support
Reason:
A companion message to the previous messages.
Action:
For assistance, contact CA Support at http://ca.com/support.
PTRR332
xxxxx HAS BEEN DELETED
Reason:
The specified data set has been deleted.
PTRR333
IDCAMS DELETE FAILED FOR DATASET
Reason:
The IDCAMS delete operation failed for the specified data set.
Chapter 2: PS to PTUIX 453
PTRR Messages
PTRR335
STARTING DATASET DELETE PROCESSING
Reason:
The utility is beginning to delete data sets.
PTRR336
DATASET DELETE PROCESSING HAS COMPLETED SUCCESSFULLY
Reason:
The utility was able to delete the data sets that it used as part of the reorganization
process.
PTRR337
DATASET DELETE PROCESSING HAS COMPLETED WITH ERRORS
Reason:
Errors occurred during the deletion process, but the utility completed the process.
PTRR400
WORK DATASET => ddname FAILED xxxxx, RC=> X'nnnnn' MOD =>RROPN
Reason:
The listed macro failed on the specified sequential data set. The message also procides
the return code value, denoted by nnnnn, that is returned in register 15 after the Open
or Close macro is issued. RROPN is the CSECT of the module that encountered the error.
The xxxxx in the error message can be one of the following:
■
OPEN-The Open macro failed.
■
CLOSE-The Close macro failed.
■
MOD-The Modify macro failed.
454 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR901
rrrr/cccc/mmmm/aaaa/ssss/pppp.
Reason:
The variables in the message indicate the following:
■
rrrr-The requested number of frames
■
cccc-The current total number of frames allocated
■
mmmm-The maximum number of frames allocated in this step
■
aaaa-The number of free frames that are available in the system
■
ssss-The total number of frames in the entire system
■
pppp-The value of EXTENDED-PAGE-FRAMES in high-level.CDBAPARM
PTRR901
INDEX EXCEEDS 2 GIGS
Reason:
This informational message informs you that you have exceeded the limit for a
partitioned index. Processing will continue.
PTRR901
INDEX: indexname BLKS REQ EXCEEDS PARMLIB
Reason:
The dataspace required for the specified index exceeded the limit specified in the UTIL
member of high-level.CDBAPARM. You should increase the limit and run the job again.
PTRR910
DSP REQUIRES: number BLKS =>xxxxx
Reason:
The dataspace requires the specified number of 4K blocks. The message indicates that
one of the following errors (denoted by xxxxx above) occurred:
■
BLKS REQ EXCEED PAGESYS-The number of blocks required for the operation
exceeded the paging limit.
■
DSP REASON CODE ERROR-An unexpected reason code was encountered while
attempting to create the dataspace.
Chapter 2: PS to PTUIX 455
PTRR Messages
■
DSP EXCEEDS SMF MAXIMUM-Creation of the dataspace would violate installation
criteria. See the IEFUSI Installation Exit section in IBM's MVS/ESA SP Installation
Exits. Check with your system programmer for local restrictions on the creation and
use of dataspaces.
■
DSP EXCEEDS ALL RESOURCES-This is an environment error where the system
cannot create additional dataspaces because of a shortage of resources. Retry the
job one or more times during a period of lower system usage. If the problem
persisits, consult your system programmer, who might be able to tune the system
so that resources will not become depleted.
■
DSP NAME NOT UNIQUE-This is a program error where the specified dataspace
name is not unique within the address space.
■
DSP NAME EXCEEDS NAME LIMIT-This is an environment error where the system's
set of generated names for dataspaces and hiperspaces has been temporarily
depleted. Retry the job one or more times during a period of lower system usage. If
the problem persisits, consult your system programmer, who might be able to tune
the system so that more names are available for use.
■
DSP INDEX EXCEEDS 2 GIGABYTES-The index is too large to be processed.
PTRR910
REQUEST number/CUR TOT number/JOB MAX number/AVAIL number/MAXIMUM
number/PCT number
Reason:
This is an informational message. The word number in the message above refers to 4K
blocks, except for the PCT number, which refers to the percentage of dataspace being
used.
PTRR911
THIS ERROR PREVENTS INDEX UPDATE PROCESSING FROM COMPLETING
Reason:
The utility encountered an error that prevented it from updating the index.
PTRR911
PRR WILL AUTOMATICALLY REBUILD INDEX(ES) THAT DID NOT COMPLETE
Reason:
This message is a companion to the previous message. When the utility encounters an
error that prevents it from updating the index, it rebuilds the indexes automatically.
456 Message Reference Guide (PS to ZLB)
PTRR Messages
PTRR912
INDEX: indexname FAILED UPD-AUTORECV
Reason:
The task for the specified index did not complete successfully. Autorecovery is being
invoked to read the index from the tablespace and recreate it.
PTRR913
UPDATE CROSS-REFERENCE TABLE SIZE: HSP=hspsize DSP=dspsize
Reason:
The amount of hiperspace and dataspace used, in 4K pages, by the cross-reference
table. The cross-reference table is where the utility keeps track of the RIDs for updating
the index entries.
PTRR914
INDEX: indexname CHECKSUM ERROR
Reason:
A checksum error occurred on the specified index.
PTRR914
INDEX: indexname EXPECTED:
Reason:
This message clarifies the previous message by indicating the number of rows that the
specified index expected.
PTRR915
rrrr/cccc/mmmm/aaaa/ssss/pppp
Reason:
The variables in the message indicate the following:
■
rrrr-The requested number of frames.
■
cccc-The current total number of frames allocated.
■
mmmm-The maximum number of frames allocated in this step.
■
aaaa-The number of free frames that are available in the system.
Chapter 2: PS to PTUIX 457
PTRR Messages
■
ssss-The total number of frames in the entire system.
■
pppp-The value of EXTENDED-PAGE-FRAMES in high-level.CDBAPARM.
PTRR915
INDEX: indexname xxxx OR TABLESPACE tsname xxxx
Reason:
If you are reorganizing an index, you might receive the first message. If you are
reorganizing a tablespace, you might receive the second message. Indicates that one of
the following errors (denoted by xxxxx above) occurred while the utility was processing
the specified index or tablespace:
■
HSP - EXCEEDS SMF MAXIMUM-Creation of the hiperspace would violate
installation criteria. See the IEFUSI Installation Exit section in IBM's MVS/ESA SP
Installation Exits. Check with your system programmer for local restrictions on the
creation and use of dataspaces.
■
DSP - EXCEEDS SMF MAXIMUM-See above entry for a description of this message.
■
HSP - NAME NOT UNIQUE-This is a program error where the specified hiperspace
name is not unique within the address space.
■
DSP - NAME NOT UNIQUE-This is a program error where the specified dataspace
name is not unique within the address space.
■
HSP - NAME EXCEEDS NAME LIMIT-This is an environment error where the system's
set of generated names for dataspaces and hiperspaces has been temporarily
depleted. Retry the job one or more times during a period of lower system usage. If
the problem persisits, consult your system programmer, who might be able to tune
the system so that more names are available for use.
■
DSP - NAME EXCEEDS NAME LIMIT-See above entry for a description of this
message.
■
HSP - EXCEEDS ALL RESOURCES-This is an environment error where the system
cannot create additional dataspaces because of a shortage of resources. Retry the
job one or more times during a period of lower system usage. If the problem
persisits, consult your system programmer, who might be able to tune the system
so that resources will not become depleted.
■
DSP - EXCEEDS ALL RESOURCES-See above entry for a description of this message.
■
HSP- REASON CODE ERROR-An unexpected return code was encountered while
attempting to create a hiperspace.
■
DSP - REASON CODE ERROR-An unexpected return code was encountered while
attempting to create a dataspace.
■
HSP - NO EXPANDED STORAGE-There is no room in expanded storage to perform
processing.
■
DSP EXCEEDS USER MAXIMUM-Request exceeded EXTENDED-DSP parmlib option.
458 Message Reference Guide (PS to ZLB)
PTRR Messages
■
HSP EXCEEDS USER MAXIMUM-Request exceeded EXTENDED-HIPER parmlib option.
■
DSP EXCEEDS PAGE SYSTEM-Request would have exceeded the paging limit. See the
EXTENDED-PAGE-FRAMES parmlib option.
■
NON INDEX PAGE FOUND-An unexpected page was found, which was not a leaf
page, non-leaf page, header or spacemap page.
PTRR915
PROCEEDING WITH DSP REQUEST
Reason:
This message appears if the utility fails to obtain the entire hiperspace. It then proceeds
with the request for dataspace.
PTRR920
TABLESPACE: creator.tablespacename.part ACQUIRING HSP WORKAREA
Reason:
The utility is obtaining the dataspace workarea for the specified tablespace.
PTRR920
TABLESPACE: creator.tablespacename.part ACQUIRING DSP WORKAREA
Reason:
The utility is obtaining the dataspace workarea for the specified tablespace.
PTRR920
TABLESPACE: tablespace xxxx or INDEXSPACE: indexspace xxxx
Reason:
Depending on your situation, you might receive one of the messages or the other. The
variables in the message indicate one of the following:
■
PAGING SYSTEM EXHAUSTED-The requested operation exceeded the paging limit.
■
ALL WORKAREA EXHAUSTED-The requested operation exceeded the available
workspace.
■
ACQUIRING HSP WORKAREA-The utility is acquiring hiperspace workarea.
■
ACQUIRING DSP WORKAREA-The utility is acquiring dataspace workarea.
Chapter 2: PS to PTUIX 459
PTT Messages
PTRR920
TABLESPACE: creator.tablespacename.part
PAGING SYSTEM EXHAUSTED
Reason:
The utility was obtaining the hiperspace workarea for the specified tablespace;
however, there is not enough hiperspace available.
PTRR920
TABLESPACE: creator.tablespacename.part ALL WORKAREA EXHAUSTED
Reason:
The utility was obtaining the hiperspace workarea, the dataspace workarea, or both for
the specified tablespace; however, the utility has reached the maximum allowed due to
user-specified maximums or system-specified maximums.
PTRR922
TABLESPACE: creator.tablespacename.part ......num1/......num2/num3
Reason:
None.
PTRR930
TABLESPACE: tsname ACQUIRING HSP WORKAREA
Reason:
The specified tablespace is acquiring hiperspace workarea.
PTRR987
BAD PARAMETER PASSAGE - RRUE2
Reason:
An internal error has occurred due to a bad parameter being passed to module
UTARRUE2.
PTT Messages
Messages with the PTT prefix are generated from Thread Termination\Dynamic
DSNZPARM.
460 Message Reference Guide (PS to ZLB)
PTT Messages
PTT0001
THREAD TERM USER=user_ID, TYPE=requested_information ON date AT time,
DB2=subsystem, TOKEN=token_ID
Reason:
Messages PTT0001, PTT0002, PTT0003, and PTT0004 appear together to provide the
result of a thread termination request issued by the thread monitor. PTT0001 contains
the user ID associated with the Xmanager under which the thread monitor is running
and the type of termination requested: D for soft termination, M for hard termination,
or W for a warning. Also provided are the date and time of the termination request, the
DB2 subsystem ID, and the token ID of the thread selected for termination processing.
Action:
None.
PTT0002
DB2=subsystem, TOKEN=token_ID, CORR=correlation_ID, AUTH=authorization_ID,
OPID=original_authorization_ID, PLAN=plan_name, CONN=connection_ID
Reason:
Messages PTT0001, PTT0002, PTT0003, and PTT0004 appear together to provide the
result of a thread termination request issued by the thread monitor. PTT0002 contains
the DB2 subsystem ID, the token ID of the thread selected for termination processing,
the correlation ID, the authorization ID, the original authorization ID, the plan name,
and the connection ID.
Action:
None.
PTT0003
DB2=subsystem, TOKEN=token_ID, CONNTP=connection_type, JOB=job_name,
ASID=address_space_ID, PROFILE GROUP=termination_profile_group_name
Reason:
Messages PTT0001, PTT0002, PTT0003, and PTT0004 appear together to provide the
result of a thread termination request issued by the thread monitor. PTT0003 contains
the DB2 subsystem ID, the token ID of the thread selected for termination processing,
the connection type, the job name, the home address space ID, and the name of the
termination profile group that contains the termination profile that the thread matched.
Action:
None.
Chapter 2: PS to PTUIX 461
PTT Messages
PTT0004
DB2=subsystem, TOKEN=token_ID, result_of_request
Reason:
Messages PTT0001, PTT0002, PTT0003, and PTT0004 appear together to provide the
result of a thread termination request issued by the thread monitor. PTT0004 contains
the DB2 subsystem ID, the token ID of the thread selected for termination processing,
and the result of the thread termination request: "THREAD MONITOR WARNING,"
"THREAD TERMINATION SUCCESSFUL," or "THREAD TERMINATION FAILED, RETURN
CODE=return_code, REASON=reason."
Action:
None.
More Information:
Thread Termination\Dynamic DSNZPARM Return and Reason Codes (see page 37)
PTT0005
message text
Reason:
A request to connect to or create a thread to DB2 has failed. The message text informs
you of why the request has failed.
Action:
Your specific response is determined by the message text.
PTT010
ACCESS DENIED.
Reason:
Your installation's external security system (for example, CA ACF2, CA Top Secret, or
IBM RACF) has denied access to this resource.
Action:
None.
462 Message Reference Guide (PS to ZLB)
PTT Messages
PTT0100
THREAD MONITORING INIT IN PROGRESS [email protected]@@@
Reason:
The thread monitor has been started.
Action:
None.
PTT0101
THREAD MONITORING INIT COMPLETE FOR [email protected]@@@
Reason:
The thread monitor has completed initialization with no fatal error.
Action:
None.
PTT0102
THREAD MONITORING TERM IN PROGRESS FOR [email protected]@@@
Reason:
The thread monitor has begun termination processing.
Action:
None.
PTT0103
THREAD MONITORING TERM COMPLETE FOR [email protected]@@@
Reason:
The thread monitor termination processing is complete.
Action:
None.
Chapter 2: PS to PTUIX 463
PTT Messages
PTT0105
THREAD MONITOR PARMLIB PROCESSING START [email protected]@@@
Reason:
The thread monitor has begun processing profiles for the designated DB2 subsystem.
Action:
None.
PTT0106
THREAD MONITOR PARMLIB PROCESSING END [email protected]@@@
Reason:
The thread monitor has completed processing profiles for the designated DB2
subsystem.
Action:
None.
PTT0107
THREAD MONITOR PARMLIB PROCESSING-ERROR PROCESSING SSID MEMBER
[email protected]@@@
Reason:
The thread monitor detected an error in the format of the designated SSID record in the
SSIDxmid parmlib member.
Action:
Check for manual changes to the card.
PTT0108
NO PROFILE GROUPS W/ SSID ssid WILL BE USED DURING MONITORING INIT; IT IS NOT
DEFINED TO THE OS.
Reason:
The thread monitor will not initialize monitoring for the given subsystem ID because it
has determined that the subsystem ID is not defined to the operating system.
Action:
None.
464 Message Reference Guide (PS to ZLB)
PTT Messages
PTT0109
NO PROFILE GROUPS W/ SSID ssid WILL BE USED DURING MONITORING INIT. ssid IS
ON A REMOTE LPAR.
Reason:
The thread monitor won't initialize monitoring for the given SSID because it has
determined that the SSID is on a remote LPAR.
Action:
None.
PTT0110
THREAD MONITOR PARMLIB PROCESSING-PROCESSING ENDED FOR [email protected]@@@
Reason:
The thread monitor parmlib has finished processing for the designated DB2 subsystem.
Action:
None.
PTT0111
THREAD MONITOR PARMLIB PROCESSING-ERROR PROCESSING PROFILE
@@@@@@@@
Reason:
The thread monitor has found a profile with no selection criteria.
Action:
Change the profile to specify selection criteria.
PTT0112
THREAD MONITOR INVALID TERMINATION TYPE @@@@ PROFILE @@@@@@@@
Reason:
The thread monitor has found an invalid termination type in the designated profile. The
thread will not be terminated, and warnings will not be issued.
Action:
None.
Chapter 2: PS to PTUIX 465
PTT Messages
PTT0113
THREAD MONITOR PARMLIB PROCESSING-ERROR-GROUP @@@@@@@@ NOT
FOUND IN TTGROUPS
Reason:
The thread monitor has found a reference to a group which does not exist.
Action:
None.
PTT0114
THREAD MONITOR PARMLIB PROCESSING-ERROR PROCESSING GROUP MEMBER
@@@@@@@@
Reason:
The thread monitor has detected an invalid format for a record in the designated group
member.
Action:
None.
PTT0115
THREAD MONITOR PARMLIB PROCESSING-PROCESSING ENDED FOR GROUP MEMBER
@@@@@@@@
Reason:
The thread monitor has completed processing the designated group.
Action:
None.
PTT0116
THREAD MONITOR PARMLIB SSID @@@@ BYPASSED, ALREADY BEING MONITORED
Reason:
The thread monitor has determined that the designated subsystem is being monitored
by another monitor.
Action:
None.
466 Message Reference Guide (PS to ZLB)
PTT Messages
PTT0117
THREAD MONITOR PARMLIB PROCESSING-INVALID DATA IN PROFILE @@@@@@@@
Reason:
The thread monitor has detected invalid data in the designated profile parmlib member.
Action:
None.
PTT0118
THREAD MONITOR STARTUP COMPLETED
Reason:
The thread monitor has completed startup.
Action:
None.
PTT0119
THREAD MONITOR STARTUP FAILED
Reason:
The thread monitor attach failed.
Action:
None.
PTT0120
THREAD MONITOR SHUTDOWN COMPLETED
Reason:
The thread monitor task has been successfully detached.
Action:
None.
Chapter 2: PS to PTUIX 467
PTT Messages
PTT0121
THREAD MONITOR NON NUMERIC WARNING COUNTS, MULTIPLE WARNINGS NOT
SUPRESSED [email protected]@@@
Reason:
The thread monitor has found invalid data needed to acquire storage for suppressing
multiple warnings. Multiple warnings will be permitted.
Action:
None.
PTT0150
THREAD TERMINATOR MONITOR TASK ABEND FOR [email protected]@@@
Reason:
The thread monitor retry routine has detected recursive or fatal abends.
Action:
None.
PTT0153
THREAD TERMINATOR MPROFILE = profile name LOCATE FAILED
Reason:
The data set associated with the profile specified during monitor startup request does
not exist.
Action:
Check the profile specified at monitor startup and the data set associated with it to be
sure that the profile still exists. Correct any errors and restart the monitor.
PTT0154
THREAD TERMINATOR MPROFILE = profile name ALLOC FAILED
Reason:
Allocation of the monitor profile data set failed. Use the profile display screens to verify
the profiles available.
Action:
Correct any errors and restart the monitor.
468 Message Reference Guide (PS to ZLB)
PTT Messages
PTT0155
THREAD TERMINATOR MPROFILE = profile name DATASET IS EMPTY
Reason:
The monitor profile specified for the monitor startup is empty.
Action:
Use the monitor profile screens to modify the profile and restart the monitor.
PTT0156
THREAD TERMINATOR MPROFILE = profile name VALIDATION FAILED
Reason:
An error occurred during processing of the monitor profile data set.
Action:
See the Xmanager job log for additional error messages.
PTT0157
THREAD TERMINATOR MPROFILE = profile name REQUEST = xmanager routine request
HAS FAILED
Reason:
A request to the Xmanager started task abended.
Action:
Make sure the Xmanager started task is active.
PTT0158
THREAD TERMINATOR MPROFILE= profile name LOCATE FAILED; ID = ssid
Reason:
Required information was not found in the monitor profile.
Action:
Delete and recreate the monitor profile and then restart the monitor.
Chapter 2: PS to PTUIX 469
PTT Messages
PTT0159
THREAD TERMINATOR MPROFILE profile name READ ERROR ID = ssid
Reason:
Required information was not found in the monitor profile.
Action:
Delete and recreate the monitor profile and then restart the monitor.
PTT0200
INPUT RECORD SYNTAX ERROR - SEE TTREPORT.
Reason:
An error was detected in a control card for the batch processor. Details of the error will
be found in the Batch Error Report that is written to the data set named by the
TTREPORT DD statement in the Batch JCL.
Your response will be determined by the details in the Batch Error Report.
PTT0201
XMANAGER NOT AVAILABLE.
Reason:
The specified or defaulted version of Xmanager is not currently running. The program
requires the services of Xmanager.
Action:
Start Xmanager.
PTT0202
UNABLE TO OPEN OUTPUT FILE.
Reason:
The batch processor was unable to successfully open the file pointed to by the
TTREPORT DD statement in the batch JCL.
Action:
There will probably be other error messages from MVS indicating what the problem is.
Correct the error and resubmit.
470 Message Reference Guide (PS to ZLB)
PTT Messages
PTT0203
UNABLE TO OPEN INPUT FILE.
Reason:
The batch processor was unable to successfully open the file pointed to by the SYSIN DD
statement in the batch JCL.
Action:
There will probably be other error messages from MVS indicating what the problem is.
Correct the error and resubmit.
PTT0204
SPECIFIED DB2 SUBSYSTEM NOT AVAILABLE.
Reason:
You requested termination of threads running in the DB2 subsystem specified on the
control card for the batch processor. That subsystem is not running on this processor.
Action:
None.
PTT0205
ABEND DETECTED IN XMANAGER.
Reason:
An ABEND occurred in the Xmanager address space. Error recovery routines trapped the
abend and produced this message.
PTT0206
AUTHORIZATION FAILED; SEE PTT0005 MESSAGE.
Reason:
You have not been granted access to the feature you requested.
Action:
For more information, see PTT0005 message.
Chapter 2: PS to PTUIX 471
PTT Messages
PTT0218
TTREPORT FILE COULD NOT BE OPENED.
Reason:
The batch processor was unable to successfully open the file pointed to by the
TTREPORT DD statement in the batch JCL.
Action:
There will probably be other error messages from MVS indicating what the problem is.
Correct the error and resubmit.
PTT0220
THREAD TERMINATOR MODIFY IN PROGRESS
Reason:
This is an informational message indicating that a monitor modify request has been
received and is being processed.
Action:
None.
PTT0221
THREAD TERMINATOR MODIFY FAILED/ALREADY ACTIVE
Reason:
A modify request to start the monitor was ignored due to the monitor already being
active.
Action:
Terminate the monitor before issuing the start modify request if the monitor needs to
be restarted.
PTT0222
THREAD TERMINATOR MODIFY FAILED DUE TO ERROR
Action:
Modify command processing has failed.
View the Xmanager job log for additional messages related to this message.
472 Message Reference Guide (PS to ZLB)
PTT Messages
PTT0224
THREAD TERMINATOR MODIFY FAILED/SSID INVALID OR NOT ACTIVE
Reason:
The monitor modify request has failed due to invalid DB2 SSID specified or not being
active on the MVS system where the modify command was issued.
Action:
Determine the cause of the message and reissue the modify command.
PTT0226
THREAD TERMINATOR MODIFY FAILED/ASYNCH ABEND INCURRED
Reason:
The monitor modify request has failed due to an abend that occurred while the request
was being processed.
PTT0227
THREAD TERMINATOR MODIFY FAILED/INVALID KEYWORD LOCATED
Reason:
The collection modify request has failed due to an invalid keyword being located.
Action:
Correct the modify command text and reissue the modify command.
PTT0228
THREAD TERMINATOR MODIFY FAILED/KEYWORD NOT FOUND KEY=keyword
Reason:
The modify request has failed due to a required keyword not being located in the
modify command text.
Action:
Correct the modify command text and reissue the modify command.
Chapter 2: PS to PTUIX 473
PTT Messages
PTT0229
THREAD TERMINATOR MODIFY FAILED/DATALEN ERROR KEY=keyword
Reason:
The message text indicates modify command text contained a keyword operand value
with an invalid length specified. The failing keyword is provided in the message text.
Action:
Correct the keyword operand and reissue the modify request.
PTT0230
THREAD TERMINATOR MODIFY FAILED/DATA IS INVALID KEY=keyword
Reason:
The message text indicates modify command text contained a keyword operand value
that was determined to be invalid. The failing keyword is provided in the message text.
Action:
Correct the keyword operand and reissue the modify request.
PTT0231
THREAD TERMINATOR MODIFY FAILED/PROFILE=profile name NOT FOUND
Reason:
This message is issued when a modify command contains a termination profile name
which is invalid.
Action:
Correct the termination profile name specified and reissue the modify command.
PTT0232
THREAD TERMINATOR MODIFY FAILED/CONTROL FILE NOT FOUND
Reason:
Modify command processing has failed due to inability to locate the control file data set
name.
Action:
Verify that the data set name in member TTCFPARM contained in Xmanager CDBAPXMP
data set reflects a valid control file data set name.
474 Message Reference Guide (PS to ZLB)
PTT Messages
PTT0233
THREAD TERMINATOR MODIFY FAILED/CONTROL FILE ALLOC FAILED
Reason:
Modify command processing has failed due to problems allocating the control file.
Action:
Attempt to determine the reason for the failure.
PTT0234
THREAD TERMINATOR MODIFY FAILED/CONTROL FILE ACCESS ERROR
Reason:
Modify command processing has failed due to access restrictions opening the control
file. The Xmanager address space must have read and write access to the control file.
Action:
Determine if any additional messages exist on the Xmanager job log that may be related
to this failure.
PTT0235
THREAD TERMINATOR MODIFY FAILED/CONTROL FILE OPEN ERROR
Reason:
Collection modify command processing has failed due to problem opening the control
file.
Action:
Determine if any additional messages exist on the Xmanager job log that may be related
to this failure.
PTT0236
THREAD TERMINATOR MODIFY FAILED/CONTROL FILE IS FULL
Reason:
Collection modify command processing has failed due to the control file being full.
Action:
See the product documentation for information on creating and copying the control file.
Chapter 2: PS to PTUIX 475
PTT Messages
PTT0237
THREAD TERMINATOR MODIFY FAILED/CONTROL FILE WRITE ERROR
Reason:
Collection modify command processing has failed due to a write error while writing to
the control file.
PTT0238
THREAD TERMINATOR MODIFY FAILED/MONITOR NOT ACTIVE
Reason:
A modify request to monitor has failed due to monitor not being active. The monitor
must be active for the modify request to be processed.
PTT0239
THREAD TERMINATOR MODIFY FAILED/MONITOR SHUTDOWN FAILED
Reason:
A modify stop the thread monitor has failed because of an error.
Action:
Determine if any additional messages exist on the Xmanager job log that may be related
to this failure.
PTT0240
THREAD TERMINATOR MODIFY FAILED/SCHEDULER NOT ACTIVE
Reason:
You attempted to issue a command to refresh the schedules controlled by the scheduler
task, but the scheduler is currently inactive. The scheduler must be active in order to
refresh the scheduled commands.
Action:
Start the scheduler and reissue the modify command, if needed.
476 Message Reference Guide (PS to ZLB)
PTT Messages
PTT0330
CONTROL FILE DATASET NAME IS INVALID OR NOT FOUND
Reason:
The control file data set name contained in member TTCFPARM within the Xmanager
CDBAPXMP data set does not exist (or the name is invalid). The control file is created
when the program is installed.
Action:
Browse the CDBAPXMP data set contained in the Xmanager started task JCL. Determine
whether the data set name contained within the member is valid. If the data set has
been deleted, attempt to restore the data set if possible.
PTT0331
CONTROL FILE ALLOCATE FAILED RC=rc
Reason:
Dynamic allocation of the control file data set failed. The message text includes the
SVC99 error reason code.
Action:
Look up the reason for the allocation failure in the IBM Application Development Guide:
Authorized Assembler Language Programs (System Macros and Facilities for MVS/XA)
manual.
PTT0333
CONTROL FILE OPEN FAILED
Reason:
MVS OPEN processing for the control file failed. The control file is created when the
program is installed. Member TTCFPARM in the Xmanager CDBAPXMP data set contains
the control file data set name in use.
Action:
Check the Xmanager job log and MVS SYSLOG for additional error messages regarding
the error. A message indicating the MVS OPEN error should have been issued using
WTO.
Chapter 2: PS to PTUIX 477
PTT Messages
PTT0334
ERROR UPDATING CONTROL FILE, DELETE NOT PROCESSED
Reason:
An error occurred during an attempt to update the control file.
PTT0335
CONTROL FILE UPDATE FAILED, DATASET FULL
Reason:
The requested operation failed because the control file is full.
Action:
For information about creating and copying the control file, see the product
documentation.
PTT0336
CONTROL FILE UPDATE FAILED DUE TO VSAM ERROR
Reason:
An error occurred during an attempt to update the control file.
PTT0337
SYSIN PARAMETER=parameter ERROR: error
Reason:
An error was encountered during processing of a SYSIN parameter.
Action:
Correct the indicated error, and then retry the operation.
478 Message Reference Guide (PS to ZLB)
PTT Messages
PTT0400
LOGGING INITIALIZATION IN PROGRESS XMID=xmanid.
Reason:
Indicates that Xmanager initialization has begun the process of initializing the logging
process in the indicated Xmanager address space.
Action:
None.
PTT0401
LOGGING INITIALIZATION COMPLETE FOR XMID=xmanid.
Reason:
Indicates that Xmanager initialization has successfully completed the process of
initializing the logging process in the indicated Xmanager address space.
Action:
None.
PTT0402
LOGGING TERMINATION IN PROGRESS FOR XMID=xmanid.
Reason:
The logging process has been directed to shut down. The process has begun in the
indicated Xmanager address space.
Action:
None.
PTT0403
LOGGING TERMINATION COMPLETE FOR XMID=xmanid.
Reason:
The logging process has completed its shut down process in the indicated Xmanager
address space.
Action:
None.
Chapter 2: PS to PTUIX 479
PTT Messages
PTT0404
xmanid LOG INIT FAILED-PTT GLOBAL AREA NOT FOUND.
Reason:
Indicates that the logging initialization process was not set up correctly.
Action:
Look for a failure in the PTTXE3CC exit routine. The variable data in this message is the
Xmanager ID.
PTT0405
message text.
Reason:
This is a general purpose message.
PTT0406
xmanid LOG INIT FAILED-NO MSW$COMM ELEMENT FOUND.
Reason:
Indicates a failure of the Xmanager initialization or a shortage of MSW$COMM elements
in the indicated Xmanager address space.
Action:
None.
PTT0407
MONITOR STARTUP NOT REQUESTED ID=xmanid
Reason:
Indicates that the monitor task was not requested to be started during initialization via
the RUNM parameter in the PTTSTART member of the high-level.CDBAPXMP data set.
Action:
None.
480 Message Reference Guide (PS to ZLB)
PTT Messages
PTT0408
PTTLOG DDNAME NOT FOUND, LOGGING UNAVAILABLE.
Reason:
The logging process was unable to open the file pointed to by the PTTLOG DD statement
in the Xmanager JCL. The program can continue, but nothing can be logged.
Action:
Determine the nature of the error, correct, and then shut down and restart the
Xmanager address space.
PTT0602
ERROR PROCESSING PTTSTART MEMBER OF PXMPARM ID=xmanid
Reason:
During initialization thread terminator reads the PTTSTART member and parses the data
in the file. However, one or more parsing errors occurred.
Action:
Refer to prior error messages for the exact cause of the parsing error. Correct the error
and restart the XMANAGER task. Refer to the comments in the PTTSTART member and
the Product documentation for details on the contents of the PTTSTART member.
PTT0603
DYNAMIC ALLOCATION ERROR DDNAME=ddname, ERROR=svc99error,
INFO=svc99info
Reason:
A dynamic allocation error has occurred.
Action:
Attempt to dynamically allocate a data set failed. Attempt to determine the reason for
the SVC99 return code information.
Ensure that the data set is specified correctly in the parmlib file, that the data set exists,
and that it is available for use.
Chapter 2: PS to PTUIX 481
PTT Messages
PTT0605
IFI CANCEL REQ FAILED RC=rc, REASON=reason ID=db2ssid
Reason:
An error occurred in the call attach facility while attempting to cancel a DB2 thread via
the IFI interface using the DB2 -CANCEL THREAD command. The DB2 Return and Reason
Codes are given.
Action:
Look up the DB2 reason code in the IBM DB2 Messages and Codes manual to determine
why the CANCEL THREAD command failed. Follow the problem determination for the
reason code.
PTT0606
THREAD TERMINATOR LOGGING ON SYSOUT ID=xmanid
Reason:
This is an informational message indicating that you have requested to have the PTTLOG
allocated to SYSOUT and the SYSOUT DD is already allocated.
Action:
None.
PTT0607
FAILURE RETRIEVING PTTLOG DSN, ID=xmanid
Reason:
When attempting to allocate the PTTLOG data set, it was determined that the PTTLOG
was already allocated to a different data set. Processing terminates.
Action:
Specify the correct data set in the PTTLOG DD of the Xmanager JCL or remove the
PTTLOG DD and let Xmanager dynamically allocate the log file.
482 Message Reference Guide (PS to ZLB)
PTT Messages
PTT0608
LOG TO BE ALLOCATED TO SYSOUT CLASS class ID=xmanid
Reason:
This is an informational message indicating that the PTTLOG will be dynamically
allocated with the SYSOUT class indicated.
Action:
None.
PTT0609
LOG SYSOUT ALLOCATION FAILED, ID=xmanid
Reason:
When attempting to allocate the PTTLOG data set to the SYSOUT class indicated in
message PTT0608, the allocation failed.
Action:
Ensure that the SYSOUT class specified in the PTT0608 message is a valid SYSOUT class.
Correct the class value in the CDBAPXMP data set member and restart the Xmanager
task.
PTT0610
ERROR PROCESSING PTTAUTH MEMBER OF PXMPARM ID=xmanid
Reason:
During initialization thread terminator reads the PTTAUTH member and parses the data
in the file. However, one or more parsing errors occurred.
Action:
Refer to prior error messages for the exact cause of the parsing error. Correct the error
and restart the XMANAGER task. Refer to the comments in the PTTAUTH member and
the Product documentation for details on the contents of the PTTAUTH member.
Chapter 2: PS to PTUIX 483
PTT Messages
PTT0611
BAD LIST ITEM BYPASSED FOR group: item
Reason:
While parsing the user command groups (USRGRPx) in the PTTAUTH member, an invalid
list value was encountered. The invalid list value will be ignored and processing will
continue.
Action:
Note that Thread Termination\Dynamic DSNZPARM commands are specified in this list
and not user security groups. Refer to the comments in the PTTAUTH member and the
product documentation for details on specifying valid commands to include in the
USRGRPx lists in the PTTAUTH member. Correct the invalid item and restart the
XMANAGER task, if necessary.
PTT0612
LOG TO BE ALLOCATED TO DATASET dsname ID=xmid
Reason:
Indicates the Thread Terminator log will be written to the data set identified by dsname.
The data set should be predefined as a sequential fixed block (FB) data set with an
LRECL of 154. If the PTTLOG DD is not defined in the Xmanager JCL, the data set will be
dynamically allocated during startup.
PTT0620
QUALIFYING THREADS EXCEED MAXIMUM, FIRST 1000 RETURNED, ID=db2
Reason:
The maximum number of threads that Thread Termination\Dynamic DSNZPARM will
collect to use in holding a lock on a particular resource is 1000. There are more than
1000 DB2 threads holding lock on the resource in question.
Action:
If you wish to cancel all threads holding locks, issue the cancel request multiple times.
484 Message Reference Guide (PS to ZLB)
PTT Messages
PTT0700
DB2 CAF TASK ABEND abendcode ENCOUNTERED, ID=ssid
Reason:
An abend occurred in the call attach facility while attempting to cancel a DB2 thread via
the IFI interface using the DB2 -CANCEL THREAD command.
Action:
Refer to prior error messages and the abend code to determine a possible cause for the
abend.
PTT0710
SCREEN INIT NAME/TOKEN request FAILED RC=rc
Reason:
A MVS name token services request failed. The message identifies the failing request
and return code.
Action:
Contact CA Support.
PTT0711
SCREEN INIT PTILIB DCB OPEN FAILED
Reason:
An attempt to open the PTILIB DD during Xmanager initialization failed.
Action:
Examine the Xmanager JCL and verify that the PTILIB DD statement is present and
references the CA Database Management Solutions for DB2 for z/OS load library at the
correct release level.
If you cannot determine the cause of the failure, contact CA Support for assistance.
Chapter 2: PS to PTUIX 485
PTT Messages
PTT0712
SCREEN INIT table-name TABLE LOAD FAILED, R1=xxxxxxxx R15=xxxxxxxx
Action:
An attempt to load a required module during Xmanager initialization failed. The R1
value contains the LOAD return code and the R15 value represents the MVS abend code
related to the failing load.
Reason:
Determine the meaning of the LOAD abend code using the IBM z/OS MVS System Codes
guide. Examine the Xmanager JCL and verify that the PTILIB DD statement is present and
references the CA Database Management Solutions for DB2 for z/OS load library at the
correct release level.
If you cannot determine the cause of the failure, contact CA Support.
PTT0721
THREAD TERMINATOR CONTROL FILE INITIALIZATION FAILED
Reason:
One or more control file parameters in the TTCFPARM member of the CDBAPARM data
set is invalid.
Action:
Refer to prior parsing error messages for the TTCFPARM member to determine which
parameters are invalid. Correct the invalid parameters and retry.
PTT0725
THREAD TERMINATOR CONTROL FILE WRITE ERROR RPLREQ=X''rplreq''
RPLRTNCD=X''rplrtncd' RPLERRCD=X''rplerrcd''
Reason:
Indicates that monitor has incurred a write error while attempting to access the control
file. The message contains VSAM request and error information.
486 Message Reference Guide (PS to ZLB)
PTT Messages
PTT0726
THREAD TERMINATOR CONTROL FILE ALLOC FAILED, DDNAME=ddname
S99INFO=X''s99info'' S99ERROR=X''s99error''
Reason:
This message is issued as a result of control file allocation error being incurred by
monitor.
Action:
Attempt to determine the reason for the SVC99 return code information.
PTT0727
THREAD TERMINATOR CONTROL FILE DEALLOC FAILED,DDNAME=ddname
S99INFO=X''s99info'' S99ERROR=X''s99error''
Reason:
A control file deallocation error was incurred by the monitor.
Action:
Attempt to determine the reason for the SVC99 return code information.
PTT0728
THREAD TERMINATOR CONTROL FILE OPEN FAILED RC=X''rc'' ACBERFLG=X''acberflg''
Reason:
This message is issued as a result of control file open error being incurred by monitor.
Action:
Attempt to determine the reason for the open return code information.
PTT0729
THREAD TERMINATOR CONTROL FILE PUT ERROR, RPLRTNCD=X''rplrtncd''
RPLERRCD=X''rplerrcd''
Reason:
A control file put error has been incurred by monitor.
Chapter 2: PS to PTUIX 487
PTT Messages
PTT0730
INPUT THREAD MONITOR PROFILE VERSION VV.R IS NOT A SUPPORTED VERSION'
Reason:
The input thread monitor profile is not supported by this release.
Action:
Resubmit the job using a release that supports the version of the profile.
PTT1000E
UNKNOWN MESSAGE NUMBER SENT TO THE MESSAGE ROUTINE: message number
Reason:
The message processing routine was passed a message number for which there is no
message defined. This is most likely an internal logic error.
Action:
Ensure that all code modules are at the same maintenance level.
PTT1001E
ERROR OPENING xxxxxxxx DATA SET, PROCESSING TERMINATED.
Reason:
An error was encountered trying to open a required data set.
Action:
Allocate the data set.
PTT1002E
'xxxxxxxx' IS AN UNRECOGNIZED COMMAND.
Reason:
An invalid command was detected.
Action:
Correct the invalid command.
488 Message Reference Guide (PS to ZLB)
PTT Messages
PTT1003E
INVALID OPERAND, 'xxxxxxxx', ENCOUNTERED (LINE line #, COL column #).
Reason:
An invalid or unknown operand was detected on the specified line number at the
specified column number.
Action:
Correct the operand.
PTT1004E
VALUE EXPECTED FOR OPERAND, 'xxxxxxxx', BUT NONE WAS FOUND (LINE line #, COL
column #).
Reason:
A value was required by the specified operand on the specified line number at the
specified column number.
Action:
Specify a valid value for the operand.
PTT1005E
DUPLICATE OPERAND, 'xxxxxxxx', ENCOUNTERED (LINE line #, COL column #).
Reason:
Duplicate operand detected.
Action:
Eliminate the redundant operand.
PTT1006E
VALUE FOR OPERAND 'xxxxxxxx' EXCEEDS MAXIMIUM LENGTH OF length (LINE line #,
COL column #).
Reason:
The value you specified for an operand exceeds the maximum length.
Action:
Correct the value for the specified operand.
Chapter 2: PS to PTUIX 489
PTT Messages
PTT1007E
VALUE FOR OPERAND 'xxxxxxxx' NEEDS TO BE AT LEAST length CHARS LONG (LINE line
#, COL column #).
Reason:
The value you specified for an operand is not long enough to be valid.
Action:
Correct the value for the specified operand.
PTT1008E
INVALID NUMERIC VALUE SPECIFIED FOR OPERAND 'xxxxxxxx' (LINE line #, COL
column #).
Reason:
An invalid numeric value was specified for the specified operand.
Action:
Ensure that the value specified for the specified operand is a valid numerical digit. Note
that some values do not allow for percent, plus, and minus signs.
PTT1009E
VALUE FOR OPERAND 'xxxxxxxx' IS LESS THAN THE MINIMUM VALUE minimum
number (LINE line #, COL column #).
Reason:
The value specified for the specified operand is below the minimum value, minimum
number, allowed.
Action:
Change the number value for the specified operand so that it is at or above the required
minimum allowed.
490 Message Reference Guide (PS to ZLB)
PTT Messages
PTT1010E
VALUE FOR OPERAND 'xxxxxxxx' EXCEEDS THE MAXIMUM VALUE maximum number
(LINE line #, COL column #).
Reason:
The value specified for the specified operand is above the maximum value allowed.
Action:
Change the number value for the specified operand so that it is at or below the required
maximum allowed.
PTT1011W
CLOSING PARENTHESIS MISSING FOR OPERAND VALUE (LINE line #, COL column #).
CONTINUING WITH ASSUMED END OF VALUE.
Reason:
The value for the specified operand was specified with an open parenthesis, but the
closing parenthesis is missing.
Action:
The command parser assumes a closing parenthesis and continues processing. Add the
closing parenthesis to avoid this warning message.
PTT1012E
REQUIRED OPERAND, 'xxxxxxxx', IS MISSING WITH NO ASSUMABLE DEFAULT VALUE.
Reason:
A required operand was not specified.
Action:
Add the operand specified in this message to the command statement.
Chapter 2: PS to PTUIX 491
PTT Messages
PTT1013E
SUBSYSTEM 'DB2 subsystem name' IS NOT AN ACTIVE DB2 SUBSYSTEM.
Reason:
You requested an action be taken for subsystem DB2 subsystem name, but the DB2
subsystem is not active or is not fully initialized.
Action:
Start the DB2 subsystem or wait until the subsystem is active to issue the command.
PTT1014E
SUBSYSTEM 'DB2 subsystem name' IS NOT AN MVS DEFINED SUBSYSTEM.
Reason:
You requested an action be taken for subsystem DB2 subsystem name, but the
subsystem specified is not defined to the local MVS system.
Action:
Correct the DB2 subsystem name and try again.
PTT1015E
SUBSYSTEM 'DB2 subsystem name' IS NOT AT A SUPPORTED RELEASEOF DB2
(RELEASE=DB2 release).
Reason:
You requested an action be taken for subsystem DB2 subsystem name, but the DB2
subsystem is at an unsupported release level.
Action:
Consult the installation documentation for supported releases of DB2.
PTT1016E
SUBSYSTEM 'subsystem name' IS NOT A DB2 SUBSYSTEM.
Reason:
You requested an action be taken for subsystem subsystem name, but the subsystem is
not a valid DB2 subsystem.
Action:
Correct the DB2 subsystem name and try again.
492 Message Reference Guide (PS to ZLB)
PTT Messages
PTT1017E
NO QUALIFYING THREAD FOUND FOR CANCEL REQUEST.
Reason:
You requested to cancel a DB2 thread, but no threads were found with matching
qualification data. The qualification data has been mistyped, or the thread no longer
exists.
Action:
Correct the qualification data if it was mistyped.
PTT1018E
ERROR UPDATING ACTIVE LOGS. FUNCTION='function ID', RC=return code-reason code
Reason:
You requested to add or delete an active log data set, but an error occurred while trying
to process function, function ID. The return code and reason code indicate the nature
of the error.
Action:
If possible, evaluate the Return and Reason Codes and try to correct the problem. For
example, the function may have been an allocate and the return and reason code would
indicate why allocation failed.
PTT1019E
ABEND abend code-reason code OCCURED WHILE UPDATING ACTIVE LOGS
(FUNCTION='function ID').
Reason:
An abend occurred while trying to add or delete an active log data set. Recovery
completed to ensure integrity. The abend code indicates the value in the SDWACMPC
field and the reason code the value in the SDWACRC field.
Action:
Obtain the dump output and contact Technical Support.
Chapter 2: PS to PTUIX 493
PTT Messages
PTT1020E
LOGIC ERROR TRYING TO UPDATE ACTIVE LOGS. FUNCTION='function ID', RC=return
code-reason code
Reason:
An internal logic error was detected while trying to add or delete an active log data set.
PTT1021W
BUFFER POOL IS NOT CURRENTLY ALLOCATED BY DB2. WILL SET MINIMUM BUFFERS
TO size.
Reason:
You requested to change the size of a buffer pool that is not currently allocated. The
minimum pool size will be set to the value you requested so that when DB2 does
allocate the buffer pool, it will be of the desired size.
Action:
None.
PTT1022W
BUFFER POOL WILL NOT BE UPDATED BECAUSE CURRENT SIZE EQUALS REQUESTED
SIZE.
Reason:
You requested to change the size of a buffer pool, but the buffer pool is already at the
desired size.
Action:
None.
PTT1023E
AT LEAST ONE OF 'PLAN', 'CONN', 'CORR', OR 'AUTH' MUST BE SPECIFIED FOR CANCEL.
Reason:
You requested to cancel a DB2 thread, but have not specified any qualification data.
Action:
Specify one or more of the qualification operands and retry.
494 Message Reference Guide (PS to ZLB)
PTT Messages
PTT1024E
INTERNAL ERROR: REQUEST CODE request code value (command) NOT FOUND IN
REQUEST PROCESSOR'S TABLE.
Reason:
The command processor has built a request block with an unknown request code value.
This is most likely an internal logic error.
Action:
Ensure that all modules are at the same release level.
PTT1025W
command REQUEST NOT PROCESSED BECAUSE NEW VALUE EQUALS OLD VALUE.
Reason:
The action request identified by command was bypassed because the requested value
and the current value are the same.
Action:
None.
PTT1026I
command REQUEST WAS SUCCESSFULLY PROCESSED.
Reason:
The requested action has completed successfully.
Action:
None.
Chapter 2: PS to PTUIX 495
PTT Messages
PTT1027E
CANNOT SET MAXIMUM BUFFER POOL BUFFERS LESS THAN THE CURRENT NUMBER
OF BUFFERS ALLOCATED (current buffers allocated).
Reason:
For a DB2 V2R3 subsystem, you requested to set the buffer pool maximum size value
below the current minimum value.
Action:
Set the maximum value to the minimum value, or change the minimum value before
changing the maximum value.
PTT1028E
COULD NOT EXPAND BP TO MAX REQUESTED - EITHER NO DBM1 STORAGE OR AT
MAX BUFFERS (DB2 RC=return code).
Reason:
You requested to increase the size of a DB2 V2R3 buffer pool, but there was not enough
virtual storage in DB2's DBM1 address space to satisfy the request or the requested
amount would have exceeded the maximum amount of buffers allowed. The return
code is the return code from DB2's add buffer pool buffer routine. Normally, the
maximum number of buffers will be adjusted to accommodate the request, but if the
current number of buffers exceeds the target value (that is, a previous buffer decrease
was requested but DB2 has not yet released all the buffers) then the current plus the
amount requested can exceed the current maximum.
Action:
Request a smaller increase of the buffer pool, increase the size of the DBM1's extended
private region when DB2 is restarted, or increase the BPMAX value.
PTT1031I
CANCEL REQUEST ISSUED FOR THREAD: PLAN=plan name CONN=connection name
CORR=correlation ID AUTH=authorization ID.
Reason:
A cancel request has been issued for the thread identified by plan name, connection
name, correlation ID, and authorization ID.
Action:
None.
496 Message Reference Guide (PS to ZLB)
PTT Messages
PTT1032E
command ACTION NOT SUPPORTED IN DB2 RELEASE DB2 release.
Reason:
The action you requested is not supported in DB2 release DB2 release. The command is
not valid for the DB2 release, or one or more of the command parameters makes it
invalid for the release indicated.
Action:
Do not attempt to change a value that is not supported by a given release of DB2.
PTT1033E
CANNOT UPDATE command VALUE BECAUSE THE DISTRIBUTED DATA FACILITY IS NOT
INSTALLED FOR SUBSYSTEM DB2 subsystem.
Reason:
You requested to update a value relating to the distributed data facility (DDF), but DDF
is not installed on DB2 subsystem.
Action:
Do not attempt to change a DDF value when DDF is not installed.
PTT1034E
CONFLICTING OR DUPLICATE OPERAND ENCOUNTERED (LINE line #, COL column #).
Reason:
The specified operand is a duplicate or is not compatible with another operand that has
been specified.
Action:
Correct the syntax and try again.
PTT1035E
REQUIRED KEYWORD IS MISSING WITH NO ASSUMABLE DEFAULT VALUE.
Reason:
A required keyword is missing.
Action:
Correct the syntax and try again.
Chapter 2: PS to PTUIX 497
PTT Messages
PTT1036I
INPUT: input record
Reason:
This message replicates the input cards.
Action:
None.
PTT1037E
UNABLE TO LOAD ORIGINAL COPY OF DB2 ZPARM MODULE INTO MSTR ADDRESS
SPACE. LOAD R1=register 1 value, R15=register 15 value.
Reason:
In order to obtain the original ZPARM values, an original copy of the ZPARM module
must be loaded into DB2's MSTR address space. However, the load request failed. The
register 1 and 15 values returned from the LOAD macro are shown.
Action:
Analyze the contents of R1 and R15 to determine the cause of the load failure and
correct if possible.
PTT1038I
ATTEMPTING TO (RE)INITIALIZE SCHEDULES.
Reason:
This message is issued by the scheduler during initialization and when a request to
refresh the list of schedules is received.
Action:
None.
498 Message Reference Guide (PS to ZLB)
PTT Messages
PTT1039I
SCHEDULE COMMAND: input schedule command text
Reason:
During scheduler (re)initialization, input commands are read in from the scheduler input
data set and are echoed to output with this message.
Action:
None.
PTT1040W
(RE)INITIALIZATION OF SCHEDULES WAS UNSUCCESSFUL.
Reason:
During scheduler (re)initialization, one or more input statements were found to have
syntax errors. The current list of schedules, if any, remain in effect.
Action:
Correct the syntax errors and refresh the list of schedules.
PTT1041I
(RE)INITIALIZATION OF SCHEDULES WAS SUCCESSFUL.
Reason:
The scheduler has just finished (re)initialization. Any schedule commands that are
defined to be active for the current time will now be executed.
Action:
None.
PTT1042E
COMMAND EXCEEDS MAXIMUM LENGTH.
Reason:
The schedule command identified in preceding messages is too long.
Action:
Reformat the schedule command so that it fits on fewer lines.
Chapter 2: PS to PTUIX 499
PTT Messages
PTT1043E
UNIDENTIFIED KEYWORD FOUND STARTING WITH 'string'.
Reason:
During schedule command syntax check, an unknown keyword or operand was
encountered starting with the characters identified in string.
Action:
Correct the statement syntax and retry.
PTT1044E
NO VALID DAYS WERE SPECIFIED.
Reason:
No days were specified in a DAYS parameter of the SCHEDULE command.
Action:
Specify one or more days that the command should execute on in the DAYS parameter.
PTT1045E
REQUIRED KEYWORD MISSING.
Reason:
A required keyword or operand is missing from the SCHEDULE command.
Action:
Ensure that all required parameters are specified and try again.
PTT1046E
SCHEDULE FROM TIME IS NOT LESS THAN TO TIME.
Reason:
The TO time on the SCHEDULE command must be later than the FROM time specified.
To span a time over midnight, you need to specify two separate commands.
Action:
Correct the time values in the FROM and TO fields and try again.
500 Message Reference Guide (PS to ZLB)
PTT Messages
PTT1047E
DUPLICATE KEYWORD "keyword" ENCOUNTERED.
Reason:
The keyword or operand, keyword, was found more than once in the SCHEDULE
command.
Action:
Eliminate the duplicate keyword or operand and try again.
PTT1048E
"COMMAND" KEYWORD MISSING.
Reason:
The COMMAND operand is missing from the SCHEDULE command.
The schedule command requires that the COMMAND operand be specified.
PTT1049E
SYNTAX ERROR IN "operand" PHRASE AT OR NEAR "string".
Reason:
The value for the SCHEDULE command operand, operand, is invalid. The command
parser detected the error near the data identified by string.
Reason:
Correct the syntax error and retry.
PTT1050E
TIME EXCEEDS 24:00.
Reason:
The TIME operand in the SCHEDULE command cannot exceed midnight (24:00).
Reason:
Correct the TIME operand and retry.
Chapter 2: PS to PTUIX 501
PTT Messages
PTT1051E
ENDING QUOTE IS MISSING.
Reason:
The ending quote on the text string for the COMMAND operand of the SCHEDULE
command is missing. Ensure the command string in the COMMAND operand in
enclosed in quotes.
Action:
Correct the syntax error and retry.
PTT1052E
"COMMAND" EXCEEDS MAXIMUM LENGTH OF 80 CHARACTERS.
Reason:
The command text in the COMMAND operand of the SCHEDULE command cannot
exceed 80 characters.
Action:
Eliminate excessive blanks in the command text so that the text string is less than 80
characters.
PTT1053I
THE FOLLOWING SCHEDULED COMMAND EXECUTED AT time ON date FROM system.
Reason:
The scheduler detected that a scheduled command needed to be executed. The current
date, time, and requesting system displays for reference.
Action:
None.
PTT1054I
command text
Reason:
This message identifies the command that is being executed by the scheduler.
Action:
None.
502 Message Reference Guide (PS to ZLB)
PTT Messages
PTT1055I
DB2 OR SCHEDULER RESTART DETECTED.
Reason:
The scheduler detected that the DB2 subsystem or the scheduler was restarted. It will
proceed to execute any commands that are valid for the current time.
Action:
None.
PTT1056I
THE FOLLOWING THREAD WILL BE CANCELLED: PLAN=plan name CONN=connection
name CORR=correlation ID AUTH=authorization ID.
Reason:
This message identifies a thread that is going to be terminated in order to honor a free
pageset request. The PLAN, CONN, CORR and AUTH identify the specific thread.
Action:
None.
PTT1057I
PAGESET SUCCESSFULLY FREED.
Reason:
Indicates that all users, if any, of a particular pageset were successfully purged in order
to free the requested pageset.
Action:
None.
Chapter 2: PS to PTUIX 503
PTT Messages
PTT1058I
PAGESET IS NOT ALLOCATED TO DB2.
Reason:
A request was received to free a pageset of all lock holders. The pageset was not
currently allocated to DB2, or the pageset has been freed of all users and the pageset
has since been successfully stopped and is now not currently allocated to DB2. This is
normal message.
Action:
None.
PTT1059E
INTERNAL ERROR: IRLM SUBSYSTEM NOT FOUND.
Reason:
The request processor was unable to locate the IRLM subsystem. This is due to internal
logic error or a system problem.
PTT1060E
CANCEL WAIT TIME EXCEEDED. PAGESET NOT FREED.
Reason:
A request to free a pageset could not be honored because one or more threads would
not terminate. This could be due to a long running thread performing backout or high
activity occurring on a reusable thread.
Action:
Cancel the user by other means, such as canceling a batch job, and retry.
PTT1061I
DB2 messages
Reason:
The requested action resulted in a DB2 command being executed in order to satisfy the
request. The resulting DB2 messages are displayed with this message. The DB2
command is identified in a prior message.
Action:
None.
504 Message Reference Guide (PS to ZLB)
PTT Messages
PTT1062E
ERROR PROCESSING DB2 COMMAND CALL. DB2 RETURN CODE return code REASON
CODE reason code.
Reason:
A requested action resulted in a DB2 command being executed in order to satisfy the
request. However, an error occurred trying to execute the command. The DB2 return
code and reason code are specified.
Action:
Refer to DB2 Messages and Codes manual and follow the action specified for the reason
code.
PTT1063I
EXECUTING DB2 COMMAND: DB2 command text
Reason:
The requested action resulted in a DB2 command being executed in order to satisfy the
request. The text of the command that will be issued is identified in this message.
Action:
None.
PTT1064E
BPID DOES NOT CONTAIN A VALID VALUE (BP0-BP49, BP32K-BP32K9).
Reason:
The BPID operand does not contains a valid value. The BPID should be from BP0 to
BP49, and BP32K to BP32K9.
Action:
Correct the BPID operand and retry.
Chapter 2: PS to PTUIX 505
PTT Messages
PTT1065E
ABEND abend code-reason code OCCURRED WHILE PROCESSING EXIT REFRESH
FUNCTION "function ID".
Reason:
An abend was encountered while trying to refresh a DB2 user exit. The abend and
reason code are given. A system dump is requested.
Action:
If the dump is the result of a user abend (such as a security 913 abend), then correct the
problem and retry.
PTT1066E
ERROR OCCURRED TRYING TO LOAD USER EXIT. LOAD R15=LOAD register 15 value
R0=LOAD register 0 value.
Reason:
An error occurred trying to load the user exit from the library specified. Registers 0 and
15 from the LOAD function are displayed. Register 15 normally indicates a return code,
and register 0 indicates the type of abend.
Action:
Identify the abend from register 0 and correct the causing problem if possible.
PTT1067E
ERROR OCCURRED TRYING TO OPEN USER EXIT LOAD LIBRARY. OPEN RC=OPEN return
code value.
Reason:
An error occurred trying to open the user exit load library.
Action:
Ensure the library is a valid load library and that the DB2 address spaces have proper
authority to access the library.
506 Message Reference Guide (PS to ZLB)
PTT Messages
PTT1068E
ERROR OCCURRED TRYING TO ALLOCATE USER EXIT LIBRARY. ALLOC R15=dynamic
allocation return code R0=dynamic allocation reason code.
Reason:
An error occurred trying to allocate the load library specified.
Action:
Ensure that the library specified is valid and is available for allocation to the DB2 address
spaces. Refer to the dynamic allocation Return and Reason Codes for details.
PTT1069E
GENERAL ERROR TRYING TO PERFORM EXIT REFRESH FUNCTION "function ID".
INTERNAL RC=return code.
Reason:
An internal error occurred trying to replace a user exit routine. The internal function ID
and return code is given.
PTT1070E
INTERNAL ERROR ENCOUNTERED. ERROR NUMBER=internal error ID.
Reason:
A general internal error occurred trying to process a request.
PTT1071I
LOG DATA SET SUCCESSFULLY ADDED.
Reason:
The ADDLOG command was successfully processed.
Action:
None.
Chapter 2: PS to PTUIX 507
PTT Messages
PTT1072I
LOG DATA SET SUCCESSFULLY DELETED.
Reason:
The DELLOG command was successfully processed.
Action:
None.
PTT1073E
EDMPOOL SIZE CHANGE FAILED REASON CODE 00000002
Reason:
A Thread Termination\Dynamic DSNZPARM internal control block could not be located.
Action:
Contact CA Support.
PTT1073E
EDMPOOL SIZE CHANGE FAILED REASON CODE 00000006
Reason:
An internal error occurred while processing the EDMPOOL size change request.
Action:
Contact CA Support.
PTT1074I
EXIT ROUTINE SUCCESSFULLY REPLACED.
Reason:
The requested exit was successfully replaced in DB2.
Action:
None.
508 Message Reference Guide (PS to ZLB)
PTT Messages
PTT1075E
CONINUATION LINE NOT FOUND.
Reason:
An input line contained the continuation character, but a continuation line was not
found.
Action:
Remove the continuation character if it is not needed. Otherwise, finish the statement
and retry.
PTT1076W
SET COMMAND NOT SPECIFIED. STATEMENT BYPASSED.
Reason:
A SET command was encountered but no other data was found. The empty SET
statement will be bypassed.
Action:
Remove the empty SET statement to avoid a warning message.
PTT1077E
PRODUCT CODE NOT SPECIFIED.
Reason:
No product code has been specified in a PRODCODE parameter of a DEFAULTS
statement. A product code is required for processing to continue.
Action:
Ensure that a valid product code is specified on a DEFAULTS statement and retry.
Chapter 2: PS to PTUIX 509
PTT Messages
PTT1078I
command REQUEST WAS SUCCESSFULLY PROCESSED. OLD VALUE = old character data,
NEW VALUE = new character data.
Reason:
The command, command, was processed successfully. The prior value is identified by
old character data and the new value is indicated by new character data.
Action:
None.
PTT1079I
command REQUEST WAS SUCCESSFULLY PROCESSED. OLD VALUE = old number value,
NEW VALUE = new number value.
Reason:
The command, command, was processed successfully. The prior value is identified by
old number value and the new value is indicated by new number value.
Action:
None.
PTT1080W
VALUE FOR PREVIOUS REQUEST WAS RESET TO THE MINIMUM ALLOWED REQUESTED VALUE WAS BELOW THE DB2 MINIMUM.
Reason:
The value requested would have been below the minimum allowed by DB2. Therefore,
the value was processed at the DB2 minimum. This is normally a result of a delta or
percent type change request which cannot be detected at syntax check time.
Action:
None. The value has been set to the minimum.
510 Message Reference Guide (PS to ZLB)
PTT Messages
PTT1081W
VALUE FOR PREVIOUS REQUEST WAS RESET TO THE MAXIMUM ALLOWED REQUESTED VALUE WAS ABOVE THE DB2 MAXIMUM.
Reason:
The value requested would have been above the maximum allowed by DB2. Therefore,
the value was processed at the DB2 maximum. This is normally a result of a delta or
percent type change request which cannot be detected at syntax check time.
Action:
None. The value has been set to the maximum.
PTT1082E
BP0 SIZE SPECIFIED IS BELOW THE DB2 MINIMUM.
Reason:
The value requested for BP0 is below the minimum allowed. BP0 requires at least a set
number (number depends on the DB2 release) of buffers.
Action:
Correct the buffer pool size value for BP0 and retry.
PTT1083E
THE SIZE SPECIFIED FOR A NON-4K BUFFER POOL IS ABOVE THE DB2 MAXIMUM.
Reason:
The value requested for a non-4 KB buffer pool is above the maximum allowed. Non-4
KB buffer pools cannot have as many buffers as 4 KB buffer pools.
Action:
Correct the buffer pool size value for the non-4 KB buffer pool and retry.
Chapter 2: PS to PTUIX 511
PTT Messages
PTT1084E
INCORRECT PREFETCH VALUE SPECIFIED FOR A NON-4K BUFFER POOL.
Reason:
The prefetch value requested for a non-4K buffer pool is invalid. It should be 0, 2 or 4
for a 32 KB buffer pool; 2, 4 or 8 for a 16 KB buffer pool; or 4, 8 or 16 for a 8 KB buffer
pool.
Action:
Correct the prefetch value and retry.
PTT1085E
INCORRECT PREFETCH VALUE SPECIFIED FOR A 4K BUFFER POOL. VALUE SHOULD BE 8,
16, 32, or 64.
Reason:
The prefetch value requested for a 4K buffer pool is invalid. It should be 8, 16, 32, or 64.
64 is valid for DB2 V8 and above.
Action:
Correct the prefetch value and retry.
PTT1086E
COULD NOT CHANGE THE PREFETCH VALUE FOR BUFFER POOL buffer pool name
BECAUSE IT IS NOT ALLOCATED.'
Reason:
The request to change the prefetch value for a buffer pool could not be honored
because the buffer pool is not currently allocated.
Action:
Wait until DB2 allocates the buffer pool (or request data from a pageset that uses the
buffer pool) and retry.
512 Message Reference Guide (PS to ZLB)
PTT Messages
PTT1087E
DDCS ESCAPE CHARACTER SPECIFIED, "escape character", IS NOT A VALID SPECIAL
CHARACTER.
Reason:
The escape character is not valid. It can be any non-alphanumeric value except the
percent sign ( ) or an underscore (_) character. A value of X will internally be interpreted
as a blank.
Action:
Change the escape character to a valid value and retry.
PTT1089E
COULD NOT ADD ACTIVE LOG DATA SET BECAUSE IT HAS ALREADY BEEN ADDED.
Reason:
You requested to add an active log data set, but the active log data set is already
available for DB2 to use.
Action:
Allocate a new log data set using a different name than the ones already in use by DB2
and retry.
PTT1090E
COULD NOT DELETE ACTIVE LOG DATA SET BECAUSE IT DOES NOT EXIST.
Reason:
You requested to delete an active log data set, but the data set specified is not allocated
or used by DB2.
Action:
Reason:
Change the data set name to one that is in use by DB2 and retry.
Chapter 2: PS to PTUIX 513
PTT Messages
PTT1091E
CANNOT ADD COPY 2 DATA SET IN A SINGLE LOG SYSTEM.
Reason:
You requested to add a copy 2 data set, but the DB2 subsystem is using single logging.
Action:
If you intended to add the data set to log copy 1, then change the copy parameter.
Otherwise, you'll have to restart DB2 with dual logging to add a copy 2 data set.
PTT1092E
CANNOT ADD ACTIVE LOG BECAUSE MAXIMUM NUMBER OF LOGS HAS BEEN
REACHED.
Reason:
You requested to add an active log data set, but the maximum number of logs has
already been reached.
If you need more active log space, you can delete some of the existing logs, reallocate
them with more space, then add them back.
PTT1093E
DATE LENGTH IS NOT VALID (0, 10-254).
Reason:
You requested to change the current local date length, but specified and invalid value.
Action:
Change the value to be 0 or in the range of 10 to 254.
PTT1094E
TIME LENGTH IS NOT VALID (0, 8-254).
Reason:
You requested to change the current local time length, but specified and invalid value.
Action:
Change the value to be 0 or in the range of 8 to 254.
514 Message Reference Guide (PS to ZLB)
PTT Messages
PTT1095E
INVALID RESTART VALUE SPECIFIED.
Reason:
You specified an invalid option on the RESTART parameter of the FREE pageset
command.
Action:
Change the value to be NONE, UT, RO, RW or FORCE.
PTT1096E
CANNOT DELETE THE CURRENT ACTIVE LOG DATASET.
Reason:
You requested to delete the current log data set, but you are not allowed to delete the
current log data set.
Action:
Request to delete another non-current active log data set, or switch the current log
through the ARCHIVE LOG DB2 command and retry.
PTT1097E
CANNOT DELETE A FULL ACTIVE LOG DATASET THAT HAS NOT BEEN OFFLOADED
WITHOUT THE FORCE OPTION.
Reason:
You requested to delete an active log data set that has not been offloaded yet.
Action:
Wait until the log data set has been offloaded, or use the FORCE option on the DELLOG
command to force delete the log data set.
Chapter 2: PS to PTUIX 515
PTT Messages
PTT1098I
THE FOLLOWING COMMAND EXECUTED AT time ON date BY USER user JOB jobname
SYSTEM system id FOR db2 subsystem.
Reason:
This message informs you that an online user has issued a command request on the
date and time identified. The system ID identifies the LPAR/sy/stem from which the
request originated. The text of the command and command results should follow this
message.
Action:n
None.
PTT1100W
BUFFER POOL CANNOT DROP BELOW ORIGINAL MINIMUM VALUE. SIZE HAS BEEN
RESET TO ORIGINAL MINIMUM.
You requested to resize a 2.3 buffer pool below its original minimum value which is not
allowed. The buffer pool has been resized to the original minimum value.
ActioReason:
None.
PTT1104E
ABEND OCCURRED PROCESSING REQUEST.
RC=abend code-reason code
Reason:
An abend occurred trying to process your request. The abend completion code and
reason code are given.
A dump was taken to the system dump data set if available.
516 Message Reference Guide (PS to ZLB)
PTT Messages
PTT1105E
ABEND OCCURRED PROCESSING SCHEDULES.
ABEND RC=abend code - reason code.
RETRY x OF y.
Reason:
An abend occurred in the scheduler. The retry count has not been exceeded so the
scheduler will recover and continue processing. The abend completion code and reason
code are given.
PTT1106E
COULD NOT FREE EDM POOL TO FULL AMOUNT BECAUSE NOT ENOUGH FREE PAGES
IN EDM POOL.
Reason:
You requested to reduce the size of the EDM pool, but there were not free enough
pages in the EDM pool to honor the request to the full amount. All available free pages
have been deleted.
Action:
You may request to reduce the size of the EDM pool after more DB2 activity has caused
additional free pages to become available.
PTT1107E
COULD NOT FREE EDM POOL TO FULL AMOUNT DUE TO LACK OF FREE EDMP
CONTROL BLOCKS.
Reason:
In order to reduce the size of the EDM pool, there must be a sufficient number of free
EDMP control blocks available in DB2's pool of EDMP control blocks. If the pool of free
EDMP control blocks becomes exhausted, then no more pages can be freed. Some
pages were able to be freed, but not enough to fulfill the request. The number of pages
freed will be indicated in another message.
Action:
Retry the request after more EDM pool activity has taken place. If new objects are
added or deleted from the EDM pool, DB2 may add or free up some EDMP control
blocks.
Chapter 2: PS to PTUIX 517
PTT Messages
PTT1108E
COULD NOT FREE EDM POOL PAGES BECAUSE THERE ARE NO FREE PAGES IN THE EDM
POOL.
Reason:
You requested to reduce the size of the EDM pool, but there were no free pages in the
EDM pool to honor the request.
Action:
You may request to reduce the size of the EDM pool after more DB2 activity has caused
enough free pages to become available.
PTT1109E
COULD NOT EXPAND EDM POOL DUE TO LACK OF PRIVATE AREA STORAGE IN DBM1
ADDRESS SPACE.
Reason:
You requested to increase the size of the EDM pool, but there was not enough virtual
storage in the DBM1 address space to honor the request.
Action:
You can request to increase the size by a smaller amount. Otherwise, you will have to
restart DB2 with a larger region size.
PTT1110E
COULD NOT EXPAND EDM POOL DUE TO NO FREE EDMP CONTROL BLOCKS BEING
AVAILABLE.
Reason:
In order to increase the size of the EDM pool, there must be a sufficient number of free
EDMP control blocks available in DB2's pool of EDMP control blocks. If the pool of free
EDMP control blocks becomes exhausted, then you cannot add any more pages.
Action:
Retry the request after more EDM pool activity has taken place. If new objects are
added or deleted from the EDM pool, DB2 may add or free up some EDMP control
blocks.
518 Message Reference Guide (PS to ZLB)
PTT Messages
PTT1111E
COULD NOT FREE EDM POOL PAGES DUE TO NO FREE EDMP CONTROL BLOCKS BEING
AVAILABLE.
Reason:
In order to reduce the size of the EDM pool, there must be a sufficient number of free
EDMP control blocks available in DB2's pool of EDMP control blocks. If the pool of free
EDMP control blocks becomes exhausted, then you cannot free any pages.
Action:
Retry the request after more EDM pool activity has taken place. If new objects are
added or deleted from the EDM pool, DB2 may add or free up some EDMP control
blocks.
PTT1113E
STORED PROCEDURE TIMEOUT VALUE IS NOT VALID (NOLIMIT, 5-1800)
Reason:
You requested to change the current stored procedure timeout value, but an invalid
value was specified.
Action:
Change the value to be 0 or in the range of 5 to 1800 (or specify NOLIMIT).
PTT1114W
STDSQL VALUE OF YES IS NOT VALID FOR DB2 V2 OR V3. STDSQL OF 86 USED INSTEAD.
Reason:
You requested to change the default standard SQL value to YES, which is not valid for
DB2 V2 or DB2 V3. A value of 86 has been substituted instead.
For DB2 V2 and V3, use 86 instead of YES.
Chapter 2: PS to PTUIX 519
PTT Messages
PTT1116E
BPID DOES NOT CONTAIN A VALID VALUE (BP0-BP49).
Reason:
The BPID operand does not contains a valid value. The BPID should be from BP0 to
BP49.
Action:
Correct the BPID operand and retry.
PTT1117E
YOU CANNOT CHANGE THE CHECKPOINT FREQUENCY TYPE USING AN OFFSET VALUE.
Reason:
You have requested to change the checkpoint frequency from minutes to a number of
log records or vise versa, and you requested the change be an offset of a percentage
change from the current value which is not allowed.
Action:
When changing the checkpoint frequency type, use a specific value and do not use a
percentage or offset value.
PTT1118E
THERE IS INSUFFICIENT VIRTUAL STORAGE IN THE DB2 MSTR ADDRESS SPACE TO
CHANGE THE OUTBUFF SIZE AS REQUESTED.
Reason:
You have requested to change the active log output buffer size, but there is not enough
virtual storage in the DB2 MSTR address space to obtain the new buffer area.
Action:
Try requesting a smaller buffer area.
520 Message Reference Guide (PS to ZLB)
PTT Messages
PTT1119I
ACCESS CONTROL AUTH EXIT INITIALIZATION INVOKED: RC=xxxxxxxx, EXPLRC1=xx,
EXPLRC2=xxxxxxxx (EXIT ENABLED).
Reason:
You have requested to refresh the access control authorization exit and it has been
successfully refreshed and the exit is currently enabled. The following return codes are
from the exit routine when invoked for initialization: RC is the contents of R15 after the
exit returned control (in hex), EXPLRC1 is the contents of the exit parameter list return
code field (in decimal), and EXPLRC2 is the contents of the exit parameter list reason
code field (in hex).
Action:
None.
PTT1120W
ACCESS CONTROL AUTH EXIT INITIALIZATION INVOKED: RC=xxxxxxxx, EXPLRC1=xx,
EXPLRC2=xxxxxxxx (EXIT DISABLED).
You have requested to refresh the access control authorization exit and it has been
successfully refreshed, but the exit is currently disabled due to the return codes during
exit initialization. The following return codes included in this message are from the exit
routine when invoked for initialization: RC is the contents of R15 after the exit returned
control (in hex), EXPLRC1 is the contents of the exit parameter list return code field (in
decimal), and EXPLRC2 is the contents of the exit parameter list reason code field (in
hex).
Action:
If you did not intend for the exit to be disabled. You need to check the return codes
from the exit routine and modify the routine as needed so that a return code of zero is
returned.
PTT1121I
DB2 RESTART DETECTED FOR xxxx.
Reason:
The scheduler has detected a restart of the identified DB2 subsystem and will process
any scheduled changed for that subsystem.
Action:
None.
Chapter 2: PS to PTUIX 521
PTT Messages
PTT1122E
SCHEDULER IS NOT ACTIVE.
Reason:
You have requested to perform some function that requires the scheduler to be active,
but the scheduler is currently stopped.
Action:
If the scheduler should be active, use the user interface panels or the Xmanager modify
command to start the scheduler.
PTT1123E
SCHEDULER IS ALREADY ACTIVE.
Reason:
You have requested to start the scheduler, but the scheduler is already active.
Action:
If you need to refresh the current set of schedules, then use the schedule refresh
option. Optionally, you may stop and restart the scheduler.
PTT1124I
SCHEDULER TERMINATED.
Reason:
A stop request was received by the scheduler, and the scheduler has successfully
terminated.
Action:
None.
PTT1125I
ALLOCATING SCHEDULE DATA SET xxxxx.
Reason:
The scheduler is attempting to dynamically allocate the identified data set in order to
initialize or refresh the schedules.
Action:
None.
522 Message Reference Guide (PS to ZLB)
PTT Messages
PTT1126E
SCHEDULE DATA SET ALLOCATION FAILED. R15="routine rc" DYNAMIC ALLOC
RC=return code - reason code.
Reason:
The scheduler was unsuccessful in attempting to dynamically allocate the data set
identified in message PTT1125I.
Action:
Ensure that the data set name is correct and that it is available for allocation to the
Xmanager address space. Refer to the dynamic allocation return code and reason code
as to why the allocation failed.
PTT1127E
XMANAGER ADDRESS SPACE IS NOT ACTIVE.
Reason:
An attempt to connect to and use a service requiring the Xmanager address space failed
because the Xmanager is not active.
Action:
Ensure that the Xmanager address space is started and running without any errors. If
so, ensure that the Xmanager ID is defined correctly in the PTIPARM data set.
PTT1128E
XMANAGER REQUEST FAILED WITH ABEND. RECOVERY SUCCESSFUL.
Reason:
An attempt to connect to and use a service requiring the Xmanager address space failed
due to an abend.
Action:
Collect all output from the Xmanager address space and the user interface, if applicable.
If the abend is not correctable, contact Technical Support.
Chapter 2: PS to PTUIX 523
PTT Messages
PTT1129E
UNAUTHORIZED REQUEST. EXTERNAL SECURITY CHECK FAILED.
Reason:
You attempted to perform a function for which you are not authorized. External
security check was attempted, but failed.
Action:
If you need to perform the function requested, contact your product administrator for
access. The product administrator will need to authorize your ID for access to the
requested function via external security. Refer to the product documentation for details
on using external security.
PTT1130E
UNAUTHORIZED REQUEST. PLAN SECURITY CHECK FAILED FOR PLAN plan name
RC=return code - reason code.
Reason:
You attempted to perform a function for which you are not authorized. Internal plan
security checking was attempted, but failed.
Action:
If you need to perform the function requested, contact your product administrator for
access. The product administrator will need to authorize your ID for access to the plan
name specified. Refer to the product documentation for details on using plan security.
The DB2 return code and reason code are given to identify the reason for failure.
PTT1131E
THREAD TERMINATOR READPARM FAILURE FOR PARMLIB MEMBER PTT
Reason:
You attempted to perform a function that requires information from the PTIPARM
parmlib data set. The requested action failed because the data set is not allocated,
contains invalid data, or member PTT is not present.
Action:
Ensure that the correct parmlib data set is allocated and that it contains valid members
including a valid PTT member.
Note: For more information about the parmlib data sets, see the product installation
documentation.
524 Message Reference Guide (PS to ZLB)
PTT Messages
PTT1132I
BATCH PROCESSING COMPLETE MAX RC=return code.
Reason:
Batch processing of commands has completed with a maximum return code as
indicated.
Action:
None.
PTT1133I
BATCH INVOCATION EXECUTED AT time ON date BY USER user JOB job SYSTEM system
ID.
Reason:
This message lets you know that a batch interface has been started on the date and
time identified. The system ID identifies the system on which the batch job is executing.
The text of any commands to be processed and the command results should follow this
message.
Action:
None.
PTT1134E
COMMAND NOT AUTHORIZED TO BE EXECUTED FROM A CONSOLE
Reason:
An MVS console modify command was issued to execute a SET statement from the
console. However, the SET statement command has not been authorized to be
executed from a console.
Action:
If you need to issue the SET statement command from the console, you need to update
the CONSOLE parameter of the PTTAUTH member in the XMANAGER parmlib data set.
See the product documentation for details on setting up and issuing SET statement
commands from the console.
Chapter 2: PS to PTUIX 525
PTT Messages
PTT1137E
ERROR CHANGING EDMPOOL SIZE. FUNCTION='function ID', RC=return
code-reason code
Reason:
You requested to change the EDM pool size, but an error occurred while trying to
process function function ID. The return code and reason code indicate the nature of the
error.
PTT1138E
ABEND abend code-reason code OCCURED WHILE CHANGING EDMPOOL SIZE
(FUNCTION='function ID')
Reason:
An abend occurred while trying to change the size of the EDM pool. Recovery was
attempted to ensure integrity. The abend code indicates the value in the SDWACMPC
field and the reason code the value in the SDWACRC field.
Action:
Obtain the dump output and contact Technical Support.
PTT1139I
COMMAND command id EXECUTING ON REMOTE SUBSYSTEM db2 subsystem id
SYSTEM system id FROM SYSTEM remote system id.
Reason:
This message indicates that a request from remote system id is executing on system id
for DB2 subsystem db2 subsystem id. The command being processed is identified by
command id.
This message is issued for a request to process a command for a DB2 subsystem that
resides on a system other than the system from which the command was requested.
Reason:
None.
526 Message Reference Guide (PS to ZLB)
PTT Messages
PTT1140E
REMOTELY SCHEDULED COMMANDS ARE NOT SUPPORTED.
Reason:
This message indicates that a scheduled command was requested for a remote DB2
subsystem. This is not supported.
Action:
Instead of trying to have a scheduled command for a remote subsystem, add the
command to the set of scheduled commands on the system for which the DB2
subsystem resides. This will ensure that scheduled commands are executed if the DB2
subsystem is restarted.
PTT1141E
ERROR CONVERTING DATA TO UNICODE. CSMCHRCV RC=return codereason code.
Reason:
During an attempt to convert the input data to unicode, an error was returned from
CA's unicode conversion service (CSMCHRCV). A return code and reason code (in
decimal) are returned from the service.
Action:
Collect the complete set of returned output messages, and then contact Technical
Support.
PTT1142E
DB2 CAF ERROR: "error description"
Reason:
Indicates that a Call Attach facility error has occurred. The error description portion of
the message is replaced with a brief description of the error.
Action:
Review the content of the error message and take corrective actions to eliminate the
problem.
Chapter 2: PS to PTUIX 527
PTT Messages
PTT1143E
REQUESTED ZPARM VALUE IS NOT SUPPORTED FOR DB2 RELEASE release.
Reason:
Indicates that the value requested for the ZPARM is not allowed for the "release" of DB2
indicated in the message text. Refer to the online help or User Guide for a list of valid
values for the release specified.
Action:
Specify a value that is valid for the release of DB2. If the requested value is valid by DB2
standards, but is not supported by dynamic ZPARM update, contact CA technical
support to see if it is possible for dynamic ZPARM update to support the desired value.
PTT1144E
THREAD TERMINATOR MAKECOMM ERROR
Reason:
Indicates that an error has occurred in the initialization of a Thread Terminator API. This
is most likely an install related error.
Action:
Verify that the correct CA DB2 products libraries are specified, parmlib, loadlib, and so
on as described in the product installation documentation.
PTT1145E
THREAD TERMINATOR PRODUCT NODE NOT FOUND
Reason:
Indicates that an error has occurred in the initialization of a Thread Terminator API. This
is most likely an install related error.
Action:
Verify that the correct CA DB2 products libraries are specified, parmlib, loadlib, and so
on as described in the product installation documentation.
For assistance, contact CA Support at http://ca.com/support.
528 Message Reference Guide (PS to ZLB)
PTUIX Messages
PTT1146E
SCHEDULER MODIFY REQUEST "req id." COULD NOT BE AUTHORIZED, DEFAULT SDB2
PARM NOT SUPPLIED.
Reason:
An error occurred attempting to authorize a request to manage the Thread Terminator
scheduler.
Action:
Verify that a default subsystem ID has been supplied in the SDB2 parameter of the
PTTAUTH member in the high-level.CDBAPXMP library. This subsystem ID is used to
authorize Manager Scheduler modify requests.
Note: For more information about setting up and managing schedules, see the Thread
Termination\Dynamic DSNZPARM User Guide.
PTUIX Messages
Messages with the PTUIX prefix are WTO messages that are generated from general
facilities used by CA Fast Load and CA Rapid Reorg.
Chapter 2: PS to PTUIX 529
PTUIX Messages
PTUIX10E
[email protected] <stgaddr> xID <IDvalues> Error getting RID size
Reason:
The utility could not find the RID size for an index because it could not find the DBD for
the associated database. This error can happen when the DBD is being rebuilt or the
index is stopped. This message can also indicate an internal error. Processing continues
with a default RID size.
This message provides the following information:
Stgaddr
Indicates the hex address of ECSA storage for PI communication.
Example: 16BE0000
IDvalues
Provides hex values (DBID, OBID, PSID, key length, and RID length) that identify the
index.
Example: 0318,0010,0011,0077,0005
Action:
If the job ends with a return code 4 or less, run a CHECK INDEX job to verify that the
index is correct.
If the return code is greater than 4, follow standard recovery procedures to recover the
index.
If the errors continue, save the output listing and DB2 MSTR log and contact CA Support.
530 Message Reference Guide (PS to ZLB)
PTUIX Messages
PTUIX24W
[email protected] <addr> xID <obj ids> Index update error, Retrying <rsncode>
Reason:
An error occurred while the utility was trying to perform index inserts or deletes.
The message variables are as follows:
■
<addr>—Hex address of the ECSA block
■
<obj ids>—Group of hex values for the index object
Example: 0573,000A,000B,0006,0004
■
–
0573 = DBID
–
000A = OBID
–
000B = PSID
–
0006 = Key length
–
0004 = RID length
<rsncode>—Hex reason code return by DB2
The utility retries the update. If all the retries fail, then the index update task quits, a
message is issued stating that the update failed, and the job ends with a return code of
16.
Action:
No action is required if the retries are successful. However, if you consistently get these
messages, consider increasing the index's buffer pool or running the load when the
system is less busy.
PTUIX44W
[email protected] <addr> SDUMP RC: <returncode>
Reason:
An SDUMP (SVC DUMP) was requested. If the <returncode> value is blank or missing,
then the SVC DUMP was successful and a dump was written to one of the system dump
data sets. If a <returncode> value is present, it is the hex value returned from the
SDUMP macro.
Action:
Check the documentation for SDUMP to determine what the return code means.
Common return codes are '00000208' (another dump in progress) and '00000408'
(dump suppressed).
Chapter 2: PS to PTUIX 531
PTUIX Messages
PTUIX46E
[email protected] <addr> Enter ESTAEX <address>
Reason:
An ABEND occurred while the processor was executing the PI update code. The ABEND
is trapped and a return and reason code are returned. If you specified MSG-DUMP (*PI),
an SDUMP is requested. If you did not specify MSG-DUMP (*PI), this message is the only
indication that an ABEND occurred.
Action:
If a dump was taken, save it. Also save the job output and the DB2 MSTR message log,
then contact Technical Support for assistance.
PTUIX48E
[email protected] <addr> Task was canceled.
Reason:
The job was canceled by the user or by an automated process.
Action:
No action is required. This message verifies that the PI update code detected the cancel
and is ending in a normal manner.
PTUIX50E
[email protected] <addr> Quit requested.
Reason:
A task has ended and all PI tasks are now signaled to end.
Action:
No action is required. This message verifies that the PI code is ending in a normal
manner. It is accompanied by another message which indicates that a task has failed or
quit.
532 Message Reference Guide (PS to ZLB)
Chapter 3: PUT to QRFM
PUT Messages
Messages with the PUT prefix are generated from general facilities used by several
products, including: CA InfoRefiner, CA Data Compressor, CA Fast Check, CA Fast Index,
CA Fast Load, CA Fast Recover, CA Fast Unload, CA LogCompress, CA Merge/Modify, CA
Partition Expert, CA Quick Copy, and CA Rapid Reorg.
PUT0000I
CA-DB2 Utilities Version &versION Started
Reason:
This is an informational message that let you know that the CA DB2 utilities have
started, as well as the stating the current utilities version number.
PUT0001E
SYSIN DDNAME missing or failed OPEN
Reason:
The DD name specified in the SYSIN failed open.
Action:
Check the spelling of the name.
PUT0002E
Critical error message DDNAME missing
Reason:
There is a DD statement missing from the job.
Chapter 3: PUT to QRFM 533
PUT Messages
PUT0003E
PTILIB DDNAME missing or failed OPEN
Reason:
The PTILIB DD name is missing from the job.
Action:
Correct the job and resubmit.
PUT0004W
Status check for Database: &dbNAME Tablespace: &tsname failed
Reason:
The tablespace named in this error message has an invalid status.
Action:
To see the status of the object being copied, include the ALLMSGS keyword in the
syntax.
PUT0005E
No Tables found in Tablespace
PUT0005E - &MSG
PUT0005E - CBLD initialization error
Reason:
Your request to run a utility against a table cannot be completed since there are no
tables in the selected tablespace.
PUT0005W
No Tables found in Tablespace, REORG will continue
Reason:
The REORG continues despite no tables being found in the tablespace being REORGED.
Action:
No further action is required.
534 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0006I
Initialization Complete - dd mmm yyyy hh:mm:ss
Reason:
This message indicates that the initialization is complete.
dd
Specifies current day.
mmm
Specifies current month.
yyyy
Specifies current year.
hh
Specifies current hour.
mm
Specifies current minutes.
ss
Specifies current seconds.
Action:
None.
PUT0007E
Processing Terminated due to CHECK option
Reason:
Utility processing has been terminated.
PUT0008E
Module DSNHDECP not found
Action:
For assistance, contact CA Support at http://ca.com/support.
Chapter 3: PUT to QRFM 535
PUT Messages
PUT0009E
PARM field on Execution Card is formatted incorrectly
Reason:
The PARM field on the EXEC card is not formatted correctly.
PUT0010E
SUMMARY message DDNAME is missing
Reason:
The ddname that supplies the summary messages is missing from your job.
PUT0011E
Storage Acquisition Failed in module &module
Reason:
Not enough storage is available. One possible problem is many discarded records during
a reorg or load.
Action:
Try increasing your region size or reducing the number of I/O buffers.
PUT0012E
SVC 99 Error Return Code: &rc
S99ERROR: &ERR
PUT0012e - S99INFO: &INF
DDNAME: &ddname
Module: &module
Reason:
The message text includes the SVC99 reason code as well as the DD name where the
error occurred.
Action:
Attempt to determine the cause of the error.
536 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0013W
Warning: utility being executed is not purchased
Reason:
This message appears during install if you have not purchased the CA Fast Utilities. No
additional messages are written to the Job Log and no LMP violation is logged. This
warning message can be ignored if it occurs during install.
However, if attempts are made to use the CA (at is not purchased) after install,
messages are then written to the JOB LOG and an LMP violation is logged.
PUT0014E
CAF Error: &CAFMSG
Reason:
The product's attempt to use the DB2 Call Attach Facility has failed.
Action:
Contact your system administrator to investigate the error indicated by the message
text. This message usually indicates that the product has not been installed correctly.
PUT0015E
SYSTABLES Update Failed with SQLCODE -&SQLRC
PUT0015E - SYSTABLESPACE Update Failed with SQLCODE -&SQLRC
Reason:
The update of SYSTABLES or SYSTABLESPACE failed for the reason given by the SQL error
code.
PUT0016E
Catalog Access SQL Error, SQLCODE -&SQLRC
Reason:
The displayed SQL error message was encountered when trying to access the DB2
catalog. The SQL error code supplies the reason for the failure.
Chapter 3: PUT to QRFM 537
PUT Messages
PUT0017I
Tablespace in STOP PENDING Mode - Utility will Retry
Reason:
The utility encountered a tablespace that requires further processing. The tablespace is
in stop pending (STOPP) mode, or it is stopped but the buffers are not yet externalized
and the locks are not yet released.
Action:
No action is required. The utility retries to process the tablespace.
PUT0018I
Invoking Utility &UTIL - Statement Number: &STEP
Reason:
Indicates invoked utility and step number of the utility statement in a multi step job.
Action:
None.
538 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0019I
Elapsed Time: hh:mm:ss - dd mmm yyyy hh:mm:ss
Reason:
This message displays the elapsed time for the Utility phase.
dd
Specifies current day.
mmm
Specifies current month.
yyyy
Specifies current year.
hh
Specifies current hour.
mm
Specifies current minutes.
ss
Specifies current seconds.
Action:
None.
PUT0020E
Tablespace Dataset failed Allocation
PUT0020E - Tablespace Dataset failed Allocation: &dsn
PUT0020E - Return Code: &rc
Reason Code: &rsn
Info Code: &info
Module: &module
Reason:
Dynamic allocation/deallocation of the data set has failed. The return code, reason
code, info code, data set name, and ddname are listed. Reason:
Action:
See the IBM DB2 Messages and Codes manual to determine the reason for the
allocation or deallocation failure.
Chapter 3: PUT to QRFM 539
PUT Messages
PUT0021E
VSAM dataset OPEN Failure
Reason:
Due to environmental conditions, the data set could not open or data set deallocation
has failed.
Action:
Contact your MVS Systems Programmer.
PUT0022E
ACB/RPL Generation Error in module &module
Reason:
An error has occurred in generating an ACB or RPL macro.
PUT0023E
VSAM GET error in module &module
Reason:
The utility encountered a VSAM GET error when it was reading a tablespace data set.
Action:
Look up the return code and reason code in the IBM VSAM Systems Macros manual.
PUT0024E
SPACEMAP Page is not valid
Reason:
Because it the spacemap page is not valid, the utility terminates processing.
PUT0025E
VSAM PUT error in module &module
Reason:
The utility encountered a VSAM PUT error in the module named in this message.
540 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0026E
The Operational State for this DB2 Dataset is &STAT which is invalid for this Utility
Reason:
The operational state named in this message is due to the running of a previous utility
on the data set.
PUT0026E
The Operational State for this DB2 Dataset is &STAT which is invalid for this Utility
Reason:
The operational state named in this message in invalid for the utility you are running.
PUT0028W
LOCKS / CLAIMS prevent acquisition of control for utility processing
Waiting for LOCKS / CLAIMS to be released
Reason:
The utility cannot stop or quiesce the object because a lock or claim on the tablespace
or index has not been released. Processing continues.
PUT0029E
LOCKS / CLAIMS prevent utility from proceeding
Reason:
Processing cannot continue because there is a lock or claim on the object that the utility
is trying to stop or quiesce.
Chapter 3: PUT to QRFM 541
PUT Messages
PUT0030E
IFI failed, Return Code: &rc
Reason Code: &reas
Reason:
DB2 IFI failed.
Action:
Use the displayed return and reason codes from DSNWLI (IFI Interface) to diagnose the
problem.
Note: For code information, see the IBM DB2 Messages and Codes manual.
PUT0031E
Initialization of DB2 Environment Failed
Reason:
An attempt to set up the utility environment has failed.
PUT0032E
Invalid RESTART Parameter
Reason:
The parameter you have supplied with RESTART is invalid.
PUT0033E
PARMLIB entry &MSGWTO is invalid
Reason:
The value for the specified parameter in the UTIL parmlib member is invalid.
PUT0034I
Application lacks MVS APF Authorization
Reason:
The program is not being executed from an APF authorized library; therefore, it does
not have the necessary authorities for execution.
542 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0035E
An error occurred determining the RO Share status for the Tablespace
Reason:
An error occurred when the utility was attempting to determine the READ ONLY share
status for the tablespace indicated in the message.
PUT0036E
Catalog error during Header Page Build
Reason:
The utility encountered an error in the system catalog while attempting to build a
header page.
PUT0037E
RESTART TABLE ACCESS ERROR - SQL ERROR CODE: sql_return_code INTERNAL
FUNCTION CODE: function_code
Reason:
The utility could not access the RESTART table. The error message gives an SQL return
code and internal function code that explains the reason for the error.
PUT0038W
Invalid PART number from DISPLAY prevents processing to continue - Retrying
DISPLAY
Reason:
The utility cannot stop the tablespace because an invalid PART number was returned
from the DISPLAY. This message is a warning. Processing continues.
PUT0039E
Invalid PART number from DISPLAY prevents processing from continuing
Reason:
The utility cannot continue processing because an invalid PART number was returned
from the DISPLAY.
Chapter 3: PUT to QRFM 543
PUT Messages
PUT0040E
Restart Table Retry Failure - either Retries Exhausted or Retries not valid for this
Function
Reason:
Either the maximum number of retries have been reached or retry attempts are not
valid for this SQL function.
Action:
See message PUT0037E.
PUT0041I
PDASTATS &VER. Processing Starting
Reason:
PDASTATS processing has started for the specified version.
Action:
None.
PUT0042I
QUIESCE &VER. Processing Starting
Reason:
Quiesce processing has started for the specified version.
Action:
None.
544 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0043I
DB2 SSID: &SSID., DB2 Ver: &DV..&DR.
- MVS Ver: &MVS., &DFSMS Ver: &V..&R..&M.
- &TY. Tablespace CCSIDS: (&CS.,&CM.,&CD.) This appears when running PDASTATS
Utility.
Reason:
The PDASTATS or QUIESCE utility is running on the identified subsystem, DB2, MVS, and
DFSMS versions. For PDASTATS, the tablespace CCSIDs are also shown.
Action:
None.
PUT0048E
Error initializing UNICODE Conversion Services in CSECT &MODULE - RC = &RC
Reason:
CA utility code was unable to initialize UNICODE Conversion Services.
PUT0049W
Deadlock encountered trying to Access the History Table. Retrying Access
Reason:
Indicates that the utility was not able to update the HISTORY table.
PUT0050I
History LOG Record created - UTILITY ID: &UTILID
Reason:
This is an informational message that lets you know that a history log record has been
created.
Action:
No further action is required.
PUT0051E
STOGROUP &NAME contains no physical volumes
Reason:
The STOGROUP named in this message does not contain any physical volumes.
Chapter 3: PUT to QRFM 545
PUT Messages
PUT0052E
No STOGROUPS found
Action:
The utility could not find any storage groups. Check if the tablespace can allocate more
space or if there are no more volumes in the storage group. If you are not using
VOLUMES ('*') in the STOGROUP, you can REMOVE volumes and then ADD them again.
PUT0053W
History LOG SYSIN data was truncated at 1600 bytes.
Reason:
A history record was received that is larger than the PUT_CMD_TEXT column of the CA
history table. The record was truncated and saved.
Action:
None.
PUT0054E
&CAPMSG
Return Code: &rc
Reason Code: &reas
Module: &module
Reason:
An error occurred in the module named in this message. The return code and reason
code provide explain the reason for the error.
PUT0055E
History LOG SQL error, SQLCODE: -&SQLCD
Reason:
The utility encountered an error with the history log. The SQL error code provided in this
message explains the reason for the error.
546 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0056E
Object is not Partitioned
Reason:
You have specified a partition number for this object and the object is not partitioned.
Action:
Check the object definition and change the utility syntax.
PUT0057E
Partitioned Tablespace contains no Partitioning Index
ie (Empty)
Reason:
The partitioned tablespace you specified does not contain a partitioning index.
Action:
Create a partitioned index on the table and then rerun the job.
PUT0058E
Selected Index does not exist on this System
Reason:
The index you specified in the utility syntax was not found on the subsystem the job is
being executed on.
Action:
Check the name of the index.
PUT0059E
Selected Table does not exist on this System
Reason:
The table you specified in the utility syntax was not found on the subsystem the job is
being executed on.
Action:
Check the name of the table.
Chapter 3: PUT to QRFM 547
PUT Messages
PUT0060E
Unexpected Conversion Services Error in CSECT &MODULE
Return Code &RC, Reason Code &RS
Reason:
An unexpected failure occurred in UNICODE Conversion Services.
Action:
The probable return codes, reason codes, and their respective reason and required
action are as follows:
Return
Code
Reason
Code
Reason
Action
4
6
A non-convertable
Identify and correct the control
character was in the control card character.
cards.
4
7
An incomplete character
was found in the control
cards.
Identify and correct the control
card character.
8
*
Internal error.
Contact Technical Support.
12
1
z/OS conversion
environment is not set up.
Contact your systems group.
12
2
z/OS conversion services
are not available
Contact your systems group.
16
*
Internal system error.
Contact Technical Support.
32
4
Insufficient storage is
available.
Adjust the REGION allotted to
the job and resubmit.
32
8
Insufficient CSA storage is
available.
Contact your systems group.
32
12
Virtual memory error.
Contact your systems group.
32
16
Internal program storage
error.
Contact Technical Support.
If the code is not listed or you are unable to resolve the problem, contact Technical
Support.
548 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0061E
Dataset RECALL failed for &dsn
Reason:
RECALL has failed for the specified data set. The data set was not able to be recalled.
Action:
Attempt to recall manually and restart.
PUT0062E
VSAM Extended Addressability not supported for &dsn
Reason:
VSAM extended addressability is not supported for the specified data set.
Action:
Do not attempt to use VSAM extended addressability for the data set in question.
PUT0062W
An EA Dataset:&dsn is defined with no &smsclass specified
Reason:
An EXTENDED-FUNCTION or EXTENDED-ADDRESS VSAM data set is being defined
without one or more of the following SMS classes because NO is specified in the parmlib
member:
■
SMS-DATACLASS
■
SMS-STORCLASS
■
SMS-MGMTCLASS
Action:
If no ACS rules preclude the use of these SMS classes, set the defaults to YES or NO,
depending on what classes cannot be specified for the user who is submitting the reorg.
Chapter 3: PUT to QRFM 549
PUT Messages
PUT0063E
VSAM Extended Function not supported for &dsn
Reason:
VSAM extended function is not supported for the specified data set.
Action:
Do not attempt to use VSAM extended function for the data set in question.
PUT0070E
Failure occurred during Dataset STATUS Setting
Reason:
The data set status could not be set.
PUT0072E
&flag Pending Flag(s) could not be DISABLED because &MSGTXT
Reason:
The flag name provided in this message could not be disabled. The reason for this is
given in the error message.
PUT0092E
Syntax Error on or near location &LOC
Reason:
A syntax error occurred on or near column number &LOC in the error message.
Action:
Correct the statement syntax.
PUT0093E
STOGROUP &STONAME exceeds 133 volumes
Reason:
The storage group named in this message exceeds the maximum number of volumes
allowed.
550 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0094E
Catalog Scan Error - GETMAIN failed
Reason:
A getmain was attempted and failed because there was not enough available storage or
memory.
Action:
The region size should be increased.
PUT0095W
Tablespace placed in CHECK PENDING: &dbTSNAME
Reason:
The specified tablespace is in check pending (CHKP) mode due to potential referential
integrity or table check constraints. Processing continues even if the tablespace has
constraint violations.
This message is issued with return code 4.
Action:
After the job finishes processing, use CA Fast Check to run a FASTCHECK DATA control
statement against the tablespace. CA Fast Check detects and reports violations of
referential and table check constraints. You can then correct the violations.
Note: For more information about using FASTCHECK DATA and correcting constraint
errors, see the CA Fast Check User Guide.
PUT0096E
START failed for CHECK PENDING process: &dbTSNAME
Reason:
The START for the check pending process failed for the tablespace named in this
message.
Chapter 3: PUT to QRFM 551
PUT Messages
PUT0097E
SYSTABLES updated for: &tbname
PUT0097I - SYSTABLES updated for: &tbname
Reason:
SYSTABLES has been updated for the table named in this message.
Action:
This message is informational only. No further action is required.
PUT0098E
SYSTABLESPACE updated for: &dbTSNAME
PUT0098I - SYSTABLESPACE updated for: &dbTSNAME
Reason:
SYSTABLESPACE has been updated for the tablespace named in this message.
Action:
This message is informational only. No further action is required.
PUT0099E
Duplicate keyword on or near location &LOC
Reason:
A keyword on or near the column number &LOC has already been specified.
Action:
Correct the syntax, deleting one instance of the keyword and resubmit the job.
PUT0100I
Utilities V&ver PARMLIB Options in effect for &PROD
PUT0100I &parmOPT
PUT0100I - * = PARMLIB Override Possible
Reason:
The parmlib options named in this message are in effect for the utility.
Action:
This message is informational only. No further action is required.
552 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0101E
Invalid keyword on or near location &LOC
Reason:
Indicates that you have specified an invalid keyword on or near the specified location.
Action:
Correct the syntax and resubmit the job.
PUT0103E
FIRST RECORD IS NOT A UTILITY KEYWORD
Reason:
The parser requires that utility control statements begin with a utility statement.
Action:
Ensure that the SYSIN control statements for all utility jobs start with a utility statement.
PUT0104E
Database/Tablespace Name format error
Reason:
The utility encountered a format error with the database/tablespace.
Action:
Verify the database/tablespace name.
PUT0105E
Index Name format error
Reason:
The utility encountered a format error with the index name.
Action:
Verify the name of the index.
Chapter 3: PUT to QRFM 553
PUT Messages
PUT0106E
PARTITION FORMAT ERROR
Reason:
The utility encountered a partition format error. Too many partitions specified in the
syntax.
DB2 releases before V8 allow no more than 254. DB2 V8 allows 4096.
Action:
Verify the number of partitions is correct for the DB2 release you are running and fix the
formatting as needed.
PUT0107E
Partition must be ALL or numeric
Reason:
The partition number value must be a valid integer or ALL.
Action:
Correct the partition number value and resubmit the job.
PUT0108E
Table Name format error
Reason:
An error was encountered in the table name format.
Action:
Correct the table name and resubmit the job.
PUT0110E
Individual Partitions not valid for TABLESPACE-INDEX or TABLE-INDEX
Reason:
The PART keyword has been specified for TABLESPACE-INDEX or TABLE-INDEX.
Action:
Remove the PART keyword from the syntax.
554 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0111E
Storage Acquisition failed - Detected in module &MODULE
Reason:
Not enough storage is available. This could be a result of too many discarded records
during REORG or LOAD.
Action:
Increase your region size or reduce the number of I/O buffers.
PUT0113I
Expanding LISTDEF &LDE. &TYPE. Entries
Reason:
Indicates the expansion of the listdef entries.
Action:
None.
PUT0114E
No &TYPE. entries for LISTDEF &LDE.
Reason:
No tablespace entries for in the list.
Action:
Review the LISTDEF entries.
PUT0115I
PDASTATS Processing Ended - Return Code - &RC
Reason:
The PDASTATS processing ended with the specified return code.
Action:
None.
Chapter 3: PUT to QRFM 555
PUT Messages
PUT0116I
QUIESCE Processing Ended - Return Code - &RC
Reason:
The utility QUIESCE processing ended with the specified return code.
Action:
None.
PUT0117I
LISTDEF Processing Ended - Return Code - &RC
Reason:
The utility LISTDEF processing ended with the specified return code.
Action:
None.
PUT0119E
LISTDEF Processing Terminated
Reason:
LISTDEF processing encountered errors that caused the termination of the utility.
Action:
Review the job output to determine the reason for LISTDEF process termination.
PUT0120E
Unable to expand Listdef &LDF. Objects
Reason:
Indicates that the utility was unable to expand the LIST.
Action:
Determine if the LIST is unavailable.
556 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0121E
PDA Authorization Failed Contact Tech Support
Reason:
Your site may not have a current CA Database Analyzer for DB2 license.
Action:
For assistance, contact CA Support at http://ca.com/support.
PUT0121W
Dataset in use - Delete failed
Reason:
This is a warning message stating that a data set is in use. The DELETE failed.
PUT0122W
Dataset in use - Attempting RETRY
Reason:
This is a warning message stating that a data set is in use. A retry is attempted.
PUT0123E
Unable to QUIESCE Object(s)
Reason:
The utility was unable to QUIESCE the objects.
Action:
Review the job output to determine the reason for the QUIESCE failure.
PUT0124I
Listdef &LDE. includes &TYPE. &DB..&TS.
Reason:
This is an informational message that indicates the included List entry.
Action:
None.
Chapter 3: PUT to QRFM 557
PUT Messages
PUT0125I
Resolving LISTDEF &LDF. FROM DDNAME &DDN.
Reason:
Indicates that the utility is attempting to resolve the list name from the specified
LISTDEF ddname.
Action:
None.
PUT0126I
Returning from Resolving LISTDEF &LDF. FROM DDNAME &DDN
Reason:
Indicates the return of the utility from resolving the list name from the specified LISTDEF
ddname.
Action:
None.
PUT0127I
Listdef &LDF. contains &CNT. Objects
Reason:
Specifies the number of objects included in the list.
Action:
None.
PUT0128I
Listdef &LDF found in SYSIN
Reason:
A duplicate LISTDEF name was found in the SYSIN.
Action:
LISTDEF processing does not allow duplicate list names. Remove the duplicate and
resubmit.
558 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0128W
SORTNUM too high for SORT package - Value reset to maximum
Reason:
The value specified for SORTNUM is higher than the maximum value allowed by your
sort package. The SORTNUM has been reset to the maximum value allowed.
Action:
None.
PUT0129E
Recursion Error - Listdef &LDF Refers to itself
Reason:
The LISTDEF name refers to itself.
Action:
Correct the syntax and resubmit the job.
PUT0130E
Listdef &LDF. not found in SYSIN or DDNAME &DDN
Reason:
The list name specified is not found in the SYSIN or LISTDEF ddname.
Action:
Make sure the specified list name has been created.
PUT0131I
Error Converting &FR. SYSIN to &TO.
Return Code:&RC., Reason Code:&RS. Parsing Continues.
Reason:
Indicates that a conversion error occurred when converting from one CCSID to another.
Action:
None.
Chapter 3: PUT to QRFM 559
PUT Messages
PUT0132E
Error Initializing MVS Conversion Services
for converting UNICODE CCSID 1208 to EBCDIC CCSID 37
Return Code:&RC., Reason Code:&RS.
Reason:
An error occurred initializing the MVS conversion services for converting Unicode SYSIN
to EBCDIC.
Action:
Contact your system administrator.
PUT0133E
Invalid STARTUP-ACCESS parameter specified
Reason:
An invalid value has been specified for STARTUP-ACCESS.
Action:
Ensure STARTUP-ACCESS is one of the following: RESET, RW, RO, FORCE, or STOP.
PUT0134I
SYSIN detected as UNICODE UTF-8 (CCSID 1208)
Reason:
The SYSIN is in Unicode format.
Action:
None.
PUT0135E
LISTDEF Internal Buffer Exhausted
Reason:
The utility encountered an internal buffer overrun during LISTDEF processing.
Action:
For assistance, contact CA Support at http://ca.com/support.
560 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0136I
Primary restart rows deleted
Reason:
The restart row was deleted from the primary restart table. This row is deleted
automatically when a job completes successfully because the restart row is no longer
needed.
This message can also be issued when job processing terminates with an error,
depending on the error type.
Action:
If the job completed successfully, no action is required. If the job terminated with an
error, other messages are issued to indicate the cause of the error. For more
information, see those messages.
PUT0137W
TERM utility failed. User may need to terminate utility &UTIL
Reason:
Utility failed to terminate.
Action:
Issue the following command manually:
TERM UTIL
PUT0138I
FOLLOWING COMMAND ISSUED AT dd mmm yyyy hh:mm:ss
Reason:
This message is issued if ALLMSGS YES is specified. See the command following this
message for more information.
dd
Identifies the day of the month.
mmm
Identifies the month.
yyyy
Identifies the year.
Chapter 3: PUT to QRFM 561
PUT Messages
hh:mm:ss
Identifies the time in hours (hh), minutes (mm), and seconds (ss).
Action:
None. This message is informational only.
PUT0141E
LISTDEF/LISTDEFDD not valid with AUTO-RESTART NO
Reason:
AUTO-RESTART YES must be specified in the UTIL parmlib member when the CA utility
syntax includes LISTDEF, an OPTIONS LISTDEFDD override, or LIST.
Action:
Change AUTO-RESTART to YES in the UTIL parmlib member and resubmit the job.
PUT0147I
$ORTPARM: VSCORE: &VSCORE.K VSCORET: &VSCORET.K
Reason:
This informational message for SYNCSORT users lists the sort parameter values used
with dynamic allocation of the $ORTPARM DD data set. The VSCORE value is taken from
the parmlib parameter SORT-APPLSIZE value. For the VSCORET parameter, the SORTSIZE
value from the job (or the value of the parmlib parameter SORT-SORTSIZE) is used.
PUT0148E
DBD build error
Reason:
There was an error attempting to build a copy of a DBD. An SVC dump with the title
'PTGL700 - DBD BUILD ERROR' was captured.
PUT0149E
DBD OBDRU area missing
Reason:
There is an error in the DBD.
562 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0150E
Error(s) found for Tablespace &parm
PUT0150E - Error(s) found for Tablespace &parmA Partition &parmB
Reason:
Errors have been found in the process of auditing tablespace tablespace-name.
Subsequent error messages indicate the nature of the errors.
PUT0151E
Error(s) found for page &parm
Reason:
Errors have been found. The page number is the actual hexadecimal representation of
the page number as found in the PGNUMBER field of the page.
PUT0152E
Invalid data: &parm
Reason:
The invalid data detected by the audit process is printed in this message. The data is
printed in its hexadecimal form and varies in length depending on the nature of the
error. The preceding message or messages describe the nature of the error.
Action:
See the explanation of the preceding message for a description of the data printed in
this message.
PUT0155E
Partition number for page is invalid. Partition number is out of range.
Reason:
The partition number encoded in the PGNUMBER field of the page is not valid for the
tablespace. The partition number occupies a variable number of bits in the PGNUMBER
field, as described in DB2 Diagnosis and Reference. The bit configuration found
exceeded the maximum partition number as indicated in SYSIBM.SYSTABLESPACE. The
data printed in the succeeding PUT0152E message is the three byte PGNUMBER field.
Chapter 3: PUT to QRFM 563
PUT Messages
PUT0156E
I/O Error Flag is on in flag byte of page
Reason:
The flag bit indicating an I/O error for the page is on in the PGCOMB byte of the page.
The data printed in the succeeding PUT0152E message is the one byte PGCOMB field.
PUT0157E
Inconsistent Data Flag is on in flag byte of page
Reason:
The flag bit indicating an I/O error for the page is on in the PGFLAGS byte of the page.
The data printed in the succeeding PUT0152E message is the one byte PGFLAGS field.
PUT0158E
Page Header does not match page trailer
Reason:
The flag bit in the PGCOMB field did not match the trailer byte for the page. The data
printed in the succeeding PUT0152E message is the one byte PGFLAGS field.
PUT0159E
Invalid page type
Reason:
The page type encoded in the PGFLAGS field is invalid. The data printed in the
succeeding PUT0152E message is the one byte PGFLAGS field.
PUT0160E
DBID in Header Page does not match DBID in SYSTABLESPACE
Reason:
The DBID found in the HPGDBID field of the header page for the tablespace did not
match the SYSIBM.SYSTABLESPACE value for the DBID. The data printed in the
succeeding PUT0152E message is the two byte HPGDBID field.
564 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0161E
PSID in Header Page does not match PSID in SYSTABLESPACE
Reason:
The PSID found in the HPGPSID field of the header page for the tablespace did not
match the SYSIBM.SYSTABLESPACE value for the PSID. The data printed in the
succeeding PUT0152E message is the two byte HPGPSID field.
PUT0162E
OBID in Header Page does not match OBID of Table in the Tablespace
Reason:
The OBID found in the HPGROID field of the header page for the tablespace did not
match the SYSIBM.SYSTABLESPACE value for the OBID. The data printed in the
succeeding PUT0152E message is the two byte HPGROID field. This message occurs
when there is exactly one table in the tablespace as indicated by HPGTBLC.
PUT0163E
OBID in Header Page does not match OBID of Tablespace
Reason:
The OBID found in the header page for the tablespace did not match the
SYSIBM.SYSTABLESPACE value for the OBID.
Action:
Reorg the tablespace to correct the problem and run the job again.
Until the tablespace can be reorged, setting the AUDIT level to 0 in your CA Quick Copy
syntax will allow the job to finish.
PUT0170E
The number of SPACEMAP entries is invalid
Reason:
The value for the maximum number of spacemap entries for the spacemap, as found in
the FOSMNENT field, was not the correct value for the tablespace. This value is
dependent on the tablespace type, page size, and so on, as documented in DB2
Diagnosis and Reference. The data printed in the succeeding PUT0152E message is the
four byte FOSMNENT field.
Chapter 3: PUT to QRFM 565
PUT Messages
PUT0171E
Last Used Entry in Non-Segmented SPACEMAP exceeds maximum
Reason:
The value for the last used spacemap entry, as found in the FOSMLENT, was greater
than the maximum number of spacemap entries, as found in the FOSMNENT field. The
data printed in the succeeding PUT0152E message is the four byte FOSMLENT field.
PUT0172E
Segment Size in page does not match DB2 Catalog
Reason:
The segment size, as found in the SEGSIZE field of the spacemap page, did not match the
value found in SYSIBM.SYSTABLESPACE. The data printed in the succeeding PUT0152E
message is the two byte SEGSIZE field.
PUT0173E
SEGNUM is not correct for the SEGSIZE and PAGE SIZE
Reason:
The number of segment entries for a spacemap, as found in the SEGNUM field of the
spacemap page, did not correspond to the value for the segment size and page size, as
documented in DB2 Diagnosis and Reference. The data printed in the succeeding
PUT0152E message is the one byte PGFLAGS field.
PUT0174E
SEGFREE is invalid. It must be less than SEGNUM
Reason:
The number of free segments in the range covered by the spacemap, as found in the
SEGFREE field of the spacemap, was greater than the maximum number of segments
covered by the spacemap, as found in the SEGNUM field of the spacemap. The data
printed in the succeeding PUT0152E message is the two byte SEGFREE field.
566 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0175E
SEGFREE is invalid. It does not match number of free segments found.
Reason:
The number of free segments tabulated in the SEGFREE field does not match the
number of free segments as determined by tallying up the segments indicated as free
on the segment chains for the spacemap. The data printed in the succeeding PUT0152E
message is the two byte SEGFREE field.
PUT0176E
SEGENT is invalid. It must be less than SEGNUM
Reason:
The value for the lowest possible free segment entry, as found in the SEGENT field of
the spacemap, is greater than the maximum number of segments for the spacemap
page, as indicated in the SEGNUM field. The data printed in the succeeding PUT0152E
message is the two byte SEGENT field.
PUT0177E
SEGMENT is on multiple segment chains
Reason:
A segment was found on more than one segment chain of the spacemap. The data
printed in the succeeding PUT0152E message is the four byte segment number field, as
found in the last chain it was detected on.
PUT0178E
First Segment is on multiple segment chains
Reason:
The first segment in a chain was found on multiple segment chains in the spacemap. The
data printed in the succeeding PUT0152E message is the four byte segment number.
PUT0179E
Segment table ID does not match any Table within the Tablespace
Reason:
The OBID of the segment owner, as indicated by the SEGOBID field of the segment
entry, is not an OBID found in the DB2 catalog for this tablespace. The data printed in
the succeeding PUT0152E message is the two byte SEGOBID field.
Chapter 3: PUT to QRFM 567
PUT Messages
PUT0180E
- All segments in a chain do not have ths same OBID
Reason:
A segment chain with segments owned by more than one OBID was found for the
spacemap. All segments in a chain must belong to the same OBID. The data printed in
the succeeding PUT0152E message is the four byte segment number of the first
segment of the chain.
PUT0181E
- Segment is not on a segment chain
Reason:
A segment was found which did not exist on a segment chain. All segments must be
found on exactly one chain. The data printed in the succeeding PUT0152E message is
the four byte segment number of the first segment of the chain.
PUT0185E
- The number of Anchor Points in data page should be zero
Reason:
The PGNANCH field of a data page was found to contain a non-zero value. The data
printed in the succeeding PUT0152E message is the one byte PGNANCH field.
PUT0186E
- Offset to contiguous free space is too large
Reason:
The value indicating the offset in the data page to the largest contiguous free space, as
found in the PGFREEP field, exceeds the maximum offset allowable. The PGFREEP value
must be less than the last used MAPID. The data printed in the succeeding PUT0152E
message is the two byte PGFREEP field.
PUT0187E
- Offset to large hole is too large
Reason:
The value indicating the offset in the data page to the large hole, as found in the
PGHOLE1 field, exceeds the maximum offset allowable. The PGHOLE1 value must be less
than the last used MAPID. The data printed in the succeeding PUT0152E message is the
two byte PGHOLE1 field.
568 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0188E
- Field on large hole chain is not a large hole
Reason:
The large hole chain for the data page, indicating available free space areas 5 bytes or
longer in length, contains an element which is not a large hole. The data printed in the
succeeding PUT0152E message is the four byte offset of the invalid record in the page.
PUT0189E
- MAPID on free MAPID chain is not a free MAPID
Reason:
A MAPID on the free MAPID chain is not marked as a free MAPID. The data printed in
the succeeding PUT0152E message is the two byte MAPID field of the MAPID containing
the invalid pointer.
PUT0190E
- MAPID on free MAPID chain is greater than 25
Reason:
A MAPID on the free RID chain is greater than the maximum allowable value for a RID.
The data printed in the succeeding PUT0152E message is the two byte MAPID field of
the MAPID containing the invalid pointer.
PUT0191E
- OBID in data row does not match OBID
of a Table within the Tablespace
Reason:
A row in the data page contains an OBID which is not found in the DB2 catalog for this
tablespace. The data printed in the succeeding PUT0152E message is the 6 byte record
header.
PUT0192E
- Row points to a MAPID but the MAPID
does not point back to the row
Reason:
A data page row contains a MAPID pointer which does not contain the offset of the data
page row. The data printed in the succeeding PUT0152E message is the 6 byte record
header.
Chapter 3: PUT to QRFM 569
PUT Messages
PUT0193E
- Unknown record type found
Reason:
A data page record was found to contain an invalid type indicator. Valid types include
normal record, overflow record, pointer record, large hole, and small hole.
The data printed in the succeeding PUT0152E message is the 6 byte record header.
PUT0194E
- SPACEMAP MODBIT is off and data page MODBIT is on
Reason:
A data page modify bit was found to be turned on in the PGFLAGS byte, but the
corresponding spacemap bit is not on. This will cause subsequent updates to the data
page to be missed in an incremental copy. The data printed in the succeeding PUT0152E
message is the one byte PGFLAGS field.
PUT0195E
- SPACEMAP MODBIT is on and data page MODBIT is off
Reason:
A data page modify bit was found to be turned off in the PGFLAGS byte, but the
corresponding spacemap bit is on. This will cause subsequent incremental copies to
include unnecessary pages. The data printed in the succeeding PUT0152E message is the
one byte PGFLAGS field.
PUT0196E
- Pointer record does not point to an overflow row
Reason:
A pointer record in a data page was found for which no corresponding overflow record
was found. The data printed in the succeeding PUT0152E message is the RID of the
pointer record
570 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0197E
- Overflow row does not have a pointer record
which points to it.
Reason:
An overflow record in a data page was found for which no corresponding pointer record
was found. The data printed in the succeeding PUT0152E message is the RID of the
overflow record.
PUT0198E
- Invalid record found in data page
Reason:
During a data page scan for a Level 2 Audit, a record was found that did not match any
documented DB2 record type. The data printed in the succeeding PUT0152E message is
the 6 byte record header.
PUT0199E
Incorrect PGFREE on the data page
Reason:
There is an incorrect PGFREE on the data page.
PUT0200E
MAPID ON FREE ID MAP CHAIN IS BROKEN.
Free ID MAP chain is broken. A MAPID on the free IDMAP chain does not contain the
valid last free MAPID.
Reason:
A MAPID on the free IDMAP chain does not contain the valid last free MAPID.
Chapter 3: PUT to QRFM 571
PUT Messages
PUT0201E
MAPID not found for Overflow Versioned Row
Reason:
The utility was performing AUDIT 1 or AUDIT 2 processing for a universal tablespace that
contains versioned pages. However, the utility encountered an error when it attempted
to identify the MAPID of an overflow row. Processing stops.
Action:
This is an internal error. Contact CA Technical Support.
PUT0205E
INVALID VALUE FOR $SYNC, MUST BE 3 DIGITS, 000 999
Reason:
You have specified an invalid value for $SYNC. The value must be a three-digit number
between 000 and 999.
PUT0206E
INVALID UTILITY NAME name
Reason:
The utility name is incorrect. Check the spelling.
PUT0207E
FAILURE BUILDING UTILITY ID
Reason:
The utility ID of the job could not be built.
PUT0208E
LOAD FAILURE FOR name
Reason:
The object named in this message could not be loaded. Check the output for additional
messages to decipher the cause of the problem.
572 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0209E
ERROR ON name
MSG: message RETURN CODE: return_code
REASON CODE: reason_code
Action:
Verify the DB2 subsystem is properly defined in the SETUPxx member of CDBAPARM. If
this is under Data Sharing, all members and the group attach name must be properly
defined. Also verify consistency between ENVDEF, PTISYSxx and SETUPxx to verify the
correct parmlib members are being utilized as expected. The STATUS command from
the DB2 Products Main Menu may assist with verifying the expected parmlib members
are being utilized.
PUT0210W
INPUT FILE EMPTY, RETURN CODE: 4
Reason:
Since the input file was empty, this warning message results.
Action:
Check the input file.
PUT0220E
Keyword TEMPLATE requires a Template-Name
Reason:
The TEMPLATE keyword must be followed by a template name.
Action:
See the IBM documentation for valid TEMPLATE syntax.
PUT0221E
&KEYWORD value exceeds max length of &LENGTH characters
Reason:
The value for the named keyword exceeds the allowed maximum length.
Action:
See the IBM documentation for valid TEMPLATE syntax.
Chapter 3: PUT to QRFM 573
PUT Messages
PUT0222E
Invalid DISP parm, DISP requires 3 positional parameters
enclosed within parenthesis
Reason:
The DISP parameter must specify all three parameters (status, normal termination, and
abnormal termination).
Action:
See the IBM documentation for valid TEMPLATE syntax.
PUT0223E
Invalid keyword for Template encountered
Reason:
An invalid keyword was specified for the TEMPLATE control statement.
Action:
See the IBM documentation for valid TEMPLATE syntax.
PUT0224E
Keyword &KEYWORD requires an integer value
Reason:
The named keyword requires an integer value.
Action:
See the IBM documentation for valid TEMPLATE syntax.
PUT0225E
Invalid &KEYWORD value specified
Reason:
The value that was specified for the named keyword is not valid.
Action:
See the IBM documentation for valid TEMPLATE syntax.
574 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0226E
Invalid RECFM value, valid values are F,V,FB,VB
Reason:
The RECFM keyword was specified with an invalid value.
Action:
Specify a valid value for RECFM (F, V, FB, or VB) and resubmit the job.
PUT0227E
Keyword &KEYWORD requires a value
Reason:
A value was not specified for the named keyword.
Action:
See the IBM documentation for valid TEMPLATE syntax.
PUT0228E
Unbalanced parenthesis for keyword &KEYWORD.
Reason:
The syntax for the named keyword is missing a parenthesis.
Action:
Correct the syntax and resubmit the job.
PUT0229E
zero token length returned from UTMTOKEN FUNCTION=GET
Reason:
This is an internal error.
Action:
Contact Technical Support for assistance.
Chapter 3: PUT to QRFM 575
PUT Messages
PUT0230E
Error processing UNIT keyword, EDTINFO macro RC = &RC.
Reason:
This is an internal error that is encountered when the EDTINFO macro is executed.
Action:
Contact Technical Support for assistance.
PUT0231E
Number of Volumes specified exceeds max of 255
Reason:
The VOLUMES keyword requires that the list of volumes be enclosed within parentheses
and be limited to 255 volumes.
Action:
Correct your VOLUMES syntax and resubmit the job.
PUT0232E
Duplicate template &TEMPLATE found in &TEMPLDD
Reason:
More than one template control statement has been defined using the same template
name.
Action:
See the IBM documentation for valid TEMPLATE syntax.
PUT0233E
Expecting keyword 'TEMPLATE', found ' &KEYWORD '
Reason:
When you submit a job that processes a template data set, the first keyword in the data
set or member must be TEMPLATE.
Action:
See the IBM documentation for valid TEMPLATE syntax.
576 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0234I
SYSTEMPL DD found in JCL, processing SYSTEMPL dataset
Reason:
This informational message indicates that default template DD SYSTEMPL is being
processed because it was defined in the JCL.
Action:
No action required.
PUT0235E
Error encountered reading Template DD &DDNAME
Reason:
An error was encountered when attempting to read the data set defined for a template
DD. The job output may contain other error messages that identify the problem.
Action:
Examine the JCL and verify that a valid data set or member name was specified.
PUT0236E
INTERNAL ERROR: UTA#SYM: ERROR FROM ASASYMBM, RC= &RC.
Reason:
This is an internal error.
Action:
Contact Technical Support for assistance.
PUT0237E
INTERNAL ERROR: UTA#SYM: ERROR FROM TIME MACRO, RC= &RC.
Reason:
This is an internal error.
Action:
Contact Technical Support for assistance.
Chapter 3: PUT to QRFM 577
PUT Messages
PUT0238E
INTERNAL ERROR: Unknown Utility NAME for UTILNAME Symbolic
Reason:
This is an internal error. The &UTILNAME variable was specified in the DSN expression,
but no utility name was available.
Action:
Contact Technical Support for assistance.
PUT0239E
TemplateDD &TEMPLDD contains invalid input : ' &KEYWORD '
Reason:
Invalid data was encountered when processing a TEMPLATE control statement.
Action:
See the IBM documentation for valid TEMPLATE syntax.
PUT0240E
TemplateName ' &TEMPLATE ' Not Found within Active list
Reason:
A template name in a utility statement was not found for the current active template
data set.
Action:
Identify the correct template DD in the OPTIONS control statement and resubmit the
job, or provide the TEMPLATE control statement in the SYSIN for the template name
used by the utility.
PUT0241E
Keyword &KEYWORD must be specified
Reason:
The named keyword must be specified for TEMPLATE.
Action:
See the IBM documentation for valid TEMPLATE syntax.
578 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0242E
BatchSubsytem requires LRECL and RECFM
Reason:
The SUBSYSname keyword requires the LRECL and RECFM keywords.
Action:
See the IBM documentation for valid TEMPLATE syntax.
PUT0243E
Batchpipe Subsystem not specified, LRECL and RECFM ignored
Reason:
The LRECL and RECFM keywords are valid only with SUBSYS.
Action:
Either remove LRECL and RECFM from your syntax or insert SUBSYS, and resubmit the
job.
PUT0244E
RETPD and EXPDL are mutually exclusive
Reason:
The RETPD (retention period) and EXPDL (expiration date) keywords are mutually
exclusive.
Action:
Specify only one of these keywords in your syntax and resubmit the job.
PUT0245I
VOLCNT defaulting to 95
Reason:
This informational message indicates that a TAPE device type was specified without a
VOLCNT keyword. VOLCNT therefore defaults to 95.
Action:
No action required.
Chapter 3: PUT to QRFM 579
PUT Messages
PUT0245E
Missing DDNAME, unable to locate UCB for Tape Stacking
Reason:
This is an internal error. Processing terminates.
Action:
Contact CA Technical Support for assistance.
PUT0246E
Number of VOLUMES specified cannot exceed VOLCNT
Reason:
Both VOLUMES and VOLCNT were specified for TEMPLATE. The number of volumes
specified for the VOLUMES keyword cannot exceed the value of VOLCNT.
Action:
See the IBM documentation for valid TEMPLATE syntax.
PUT0247E
Keyword &KEYWORD Not valid with TAPE
Reason:
If a device type of TAPE is specified, you cannot specify keywords that apply to DASD
devices.
Action:
See the IBM documentation for valid TEMPLATE syntax.
PUT0248E
Invalid MEMBER or GDG value
Reason:
This is an internal error. Processing terminates.
Action:
Contact CA Technical Support for assistance.
580 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0249E
Internal Error: UTA#SYM: invalid length for Input Pattern
or Output Target Area
Reason:
This is an internal error. An invalid length was specified for a control block area.
Action:
Contact Technical Support for assistance.
PUT0250E
invalid character string &CHAR found in DSN expression
Reason:
An invalid string of characters, identified by &CHAR, was encountered in the DSN
expression.
Action:
All symbolics must be preceded by an ampersand (&) and end with a period. If the DSN
expression contains special characters, the expression must be enclosed within single
quotes.
PUT0251I
Retry of Dynamic DASD space Allocation in progress for:
&dsname
Reason:
The utility is trying again to dynamically allocate DASD space with altered primary and
secondary quantities.
Action:
No action is required. Processing continues.
Chapter 3: PUT to QRFM 581
PUT Messages
PUT0252I
Retry of Dynamic DASD space Allocation successful for:
&dsname
Reason:
The utility has successfully performed the dynamic allocation of DASD space with
altered primary and secondary quantities.
Action:
No action is required. Processing continues.
PUT0253I
Retry of Dynamic DASD space Allocation unsuccessful for:
&dsname
Reason:
The utility is unable to dynamically allocate DASD space with altered primary and
secondary quantities. This error is usually due to an invalid data set name.
Action:
Refer to the WTO messages in the job output to identify the generated data set name
that was not allocated.
PUT0254E
ERROR ALLOCATING DATA SET:
DSN=&dsname
SVC99 CODE=&reason
Reason:
SVC 99 returned an error during TEMPLATE data set dynamic allocation. The code
identifies the SVC 99 error. The failure is usually due to an invalid data set name.
Action:
Refer to the WTO messages in the job output to identify the generated data set name
that was not allocated.
582 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0256E
ERROR UNALLOCATING DATA SET:
DD=&DDNAME , DSN=&DSNAME
SVC99 CODE=&REASON
Reason:
This is an internal error. Processing terminates.
Action:
Contact CA Technical Support for assistance.
PUT0257E
Internal Error: Invalid Dataset Name for DYNALLOC
Reason:
This is an internal error. Processing terminates.
Action:
Contact CA Technical Support for assistance.
PUT0258E
Internal Error: Invalid DDNAME for DYNALLOC
Reason:
This is an internal error. Processing terminates.
Action:
Contact CA Technical Support for assistance.
PUT0259E
Internal Error: Invalid DATACLAS, STORCLAS or MGMTCLAS
for DYNALLOC
Reason:
This is an internal error. Processing terminates.
Action:
Contact CA Technical Support for assistance.
Chapter 3: PUT to QRFM 583
PUT Messages
PUT0260E
Internal Error: Invalid MODELDCB for DYNALLOC
Reason:
This is an internal error. Processing terminates.
Action:
Contact CA Technical Support for assistance.
PUT0261E
Internal Error: Invalid UNIT value for DYNALLOC
Reason:
This is an internal error. Processing terminates.
Action:
Contact CA Technical Support for assistance.
PUT0262E
Internal Error: Invalid RETPD value for DYNALLOC
Reason:
This is an internal error. Processing terminates.
Action:
Contact CA Technical Support for assistance.
PUT0263E
Internal Error: Invalid DISP, NDISP or CDISP for DYNALLOC
Reason:
This is an internal error. Processing terminates.
Action:
Contact CA Technical Support for assistance.
584 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0264E
Internal Error: Invalid or Missing DDNAME for UNALLOC
Reason:
This is an internal error. Processing terminates.
Action:
Contact CA Technical Support for assistance.
PUT0265E
Internal Error: Invalid or Missing DSNAME for UNALLOC
Reason:
This is an internal error. Processing terminates.
Action:
Contact CA Technical Support for assistance.
PUT0266E
Internal Error: DSAB not found for DYNALLOC Tape Stacking
Reason:
This is an internal error. Processing terminates.
Action:
Contact CA Technical Support for assistance.
PUT0278E
Dynamic Allocation: Invalid PARMLIB Keyword &KEYW
&X detected processing directive &D
Reason:
The indicated parmlib keyword is invalid.
Action:
Verify the parmlib settings.
Chapter 3: PUT to QRFM 585
PUT Messages
PUT0289I
Dynamic Allocation: Reading PARMLIB Member &M
Reason:
Indicates an error reading the parmlib member named in this error.
Action:
None.
PUT0293E
Dynamic Allocation: Invalid Directive &D
Reason:
Indicates a dynamic allocation error.
Action:
Verify the settings in the PRR member of high-level.CDBAPARM as well as the RID,
SYSDISC, SYSREC, and SYSUT1 keyword specifications.
PUT0295E
Dynamic Allocation: Error Reading PARMLIB Member
Reason:
Indicates a dynamic allocation error reading the parmlib member.
Action:
Verify the spelling.
PUT0296I
TABLE Processing: Reading PARMLIB Member &M
Reason:
The utility is reading the specified parmlib member to process a table that is required
for the job.
Action:
No action is necessary.
586 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0297E
TABLE Processing: Error Reading PARMLIB Member
Reason:
An internal error occurred when the utility attempted to read a parmlib member to
process a table. Processing stops.
Action:
Determine which parmlib member the utility was attempting to read by viewing the
PUT0296I message that preceded this message. Verify whether the parmlib member
exists, and then contact CA Technical Support for assistance.
PUT0298E
TABLE Processing: Invalid PARMLIB Keyword &KEYW
detected processing directive &D
Reason:
The utility attempted to read a parmlib member to process a table, but it encountered
an invalid keyword. &D identifies the major keyword. &KEYW identifies the minor
keyword parameter that caused the error. Processing stops.
Action:
Determine which parmlib member contains the invalid keyword by viewing the
PUT0296I message that preceded this message. Correct the specified keyword and
resubmit the job.
PUT0300E
SUBSYSTEM NOT FOUND IN JES TABLE
Reason:
You have specified an invalid subsystem name.
Action:
Verify the subsystem information and resubmit the job.
PUT0301E
INTERNAL DB2 BLOCK DOES NOT MATCH
Reason:
The requested DB2 subsystem ID is not found in the JES tables that contain available
DB2 subsystem IDs or an internal error was found in the JES tables.
Chapter 3: PUT to QRFM 587
PUT Messages
PUT0302E
TABLE Processing: Invalid Directive &D
Reason:
The utility attempted to read a parmlib member to process a table, but it encountered
an invalid major keyword. &D identifies the keyword that caused the error. Processing
stops.
Action:
Determine which parmlib member contains the invalid keyword by viewing the
PUT0296I message that preceded this message. Correct the specified keyword and
resubmit the job.
PUT0303E
TABLE Processing: Invalid PARMLIB Symbolic starting with
&SYM detected processing directive &D
and processing keyword &KEY
Reason:
The utility attempted to read a parmlib member to process a table, but it encountered
an invalid symbolic. &D identifies the major keyword. &KEYW identifies the minor
keyword parameter. &SYM identifies the symbolic that caused the error. Processing
stops.
Action:
Determine which parmlib member contains the invalid symbolic by viewing the
PUT0296I message that preceded this message. Correct the specified symbolic and
resubmit the job.
PUT0304E
APPLICATION LACKS MVS APF AUTHORIZATION
Reason:
The program is not being executed from an APF authorized library; therefore, it does
not have the necessary authorities for execution.
588 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0305I
DB2 CATALOG TABLE SYSTABLEPART UPDATED WITH NEW QUANTITIES
Reason:
The SYSTABLEPART column of the DB2 catalog has been updated with new quantities.
This message is informational only. No further action is required.
PUT0306E
SYSTABLEPART UPDATE FAILED WITH SQLCODE: -sql_code
Reason:
The update of the SYSTABLEPART column of the DB2 catalog failed.
Action:
Look up the SQL code in IBM DB2 Messages and Codes to determine the cause of the
error.
PUT0307E
TOO MANY ROWS UPDATED, CHANGES TO SYSTABLEPART ROLLED BACK
Reason:
Since too many rows in were updated the changes to the SYSTABLEPART column of
the DB2 catalog were rolled back. No updates were made.
PUT0308E
SYSSEQUENCES UPDATE FAILED WITH SQLCODE: -sql_code
Reason:
The update of the SYSSEQUENCES column of the DB2 catalog failed. Look up the SQL
code in IBM DB2 Messages and Codes to determine the cause of the error
PUT0310E
UNABLE TO START TABLESPACE
Reason:
The utility was unable to start the tablespace. A partition might be in read-only mode.
Chapter 3: PUT to QRFM 589
PUT Messages
PUT0311E
UNABLE TO RETRY SELECT
Reason:
An attempted RETRY SELECT statement failed.
PUT0312E
UNABLE TO STOP TABLESPACE
Reason:
The utility cannot stop the tablespace named in the message.
PUT0313E
SQLD/SQLVAR AREA NOT SET BY DB2
Reason:
DB2 could not set the SQLD/SQLVAR area.
PUT0315E
UNABLE TO START INDEXSPACE
Reason:
The utility was not able to START the indexspace.
Action:
Check the mode of the index as well as its partitions.
PUT0316E
UNABLE TO STOP INDEXSPACE
Reason:
The utility was not able to STOP the indexspace.
Action:
Check the mode of the index as well as its partitions.
590 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0317E
DYNAMIC SQL SELECT FAILED FOR action WITH SQLCODE -sql_code
Reason:
An attempted SQL SELECT statement failed, resulting in the listed SQLCODE.
Action:
See the IBM DB2 Messages and Codes manual for more information on this code.
PUT0318E
DB2 SSID NOT ACTIVE
Reason:
The DB2 subsystem is not currently active.
PUT0319E
DB2 SSID NOT VALID
Reason:
You have supplied an invalid DB2 subsystem name.
Action:
Verify the name of the DB2 SSID.
PUT0320E
ASCII CONVERSION NOT SUPPORTED FOR THIS RELEASE
Reason:
The release of the product you are using does not support ASCII conversion.
Chapter 3: PUT to QRFM 591
PUT Messages
PUT0321E
TRANSLATION PROCEDURE procedure NOT SUPPORTED FOR THIS RELEASE
Reason:
The release of the product you are using does not support the translation procedure
that you have attempted.
PUT0322W
CCSID ccsid number ATTEMPTING DATA TRAN
Reason:
This is a warning message letting you know that a data transport is being attempted for
the CCSID number given in the message.
Action:
As this is warning message, no further action is required.
PUT0323I
Information for CCSID &CCSID to &NUMB conversion
(Type &TYPE.,&IBM.,&PROC.) found in SYSIBM.SYSSTRINGS
Reason:
The CCSID given in this message was found in SYSIBM.SYSTRINGS.
Action:
This message is informational only. No further action is required.
PUT0324W
CCSID ccsid number NOT FOUND IN DATA TRANSPORT
Reason:
You have entered an invalid CCSID.
592 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0325E
STATIC SQL SELECT FAILED FOR type WITH SQLCODE sql_code
Reason:
An attempted SQL SELECT statement failed, resulting in the listed SQLCODE.
Action:
See the IBM DB2 Messages and Codes manual for more information on this code.
PUT0326E
TRANSLATION PROCEDURE procedure NOT FOUND
Reason:
The utility could not find the function you are requesting.
PUT0327E
TRANSLATION PROCEDURE FAILED
Reason:
The translation function failed.
PUT0328E
EBCDIC TO ASCII CONVERSION CCSIDS CANNOT BE FOUND ABENDING
Action:
Verify the CCSIDs and resubmit the job.
PUT0328I
EBCDIC TO ASCII CONVERSION DEFAULT CCSIDS CANNOT BE FOUND DSNDDECP
VALUES: MIXED:
X'mixed.' EBCDIC CCSIDS: X'sbcs' ASCII
CCSIDS: X'asbcs'
Action:
Verify the CCSIDs and resubmit the job.
Chapter 3: PUT to QRFM 593
PUT Messages
PUT0329E
EBCDIC TO ASCII CONVERSION CCSIDS CANNOT BE FOUND ABENDING DSNDDECP
VALUES: EBCDIC CCSID: X'sbcs' ASCII
CCSID: X'asbcs' MIXED:
X'mixed.'
Action:
Verify the CCSIDs and resubmit the job.
PUT0330W
- DSNHDECP module not consistent with DB2 Catalog
Discrepancy noted for &LABEL
Reason:
The parameter specified in DSNHDECP module is not consistent with that originally
specified in the tablespace definition.
PUT0331I
- &USER Transproc &TRANS Loaded
Action:
None.
PUT0333W
- Conversion Services Routine Failure attempting to convert
data from CCSID &from to &to
Return code: &rc., Reason Code: &rsn
Reason:
There was an error in the data conversion.
PUT0334I
- Conversion Services Routine Found: CCSID &from - &to
Action:
None.
594 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0350I
PDA PROCESSING COMPLETE
Reason:
Processing has completed.
Action:
This message is informational only. No further action is required.
PUT0351E
PDA PROCESS: CATALOG SEARCH FAILED FOR DATASET dataset_name
Reason:
The search for the data set failed.
Action:
Verify the spelling of the data set and resubmit the job.
PUT0352W
CATALOG UPDATE NOT PROCESSED DUE TO SINGLE PART PROCESSING
Reason:
The DB2 catalog could not be updated. This message is a warning. Processing
continues.
PUT0353W
CATALOG UPDATE NOT PROCESSED DUE TO RESUME YES PROCESSING
Reason:
The DB2 catalog could not be updated. This message is a warning. Processing
continues.
PUT0354E
DAS PRODUCT HAS NOT BEEN INSTALLED
Reason:
The product could not be installed.
Chapter 3: PUT to QRFM 595
PUT Messages
PUT0354W
product PRODUCT HAS NOT BEEN INSTALLED
Reason:
The product named in this message could not be installed.
PUT0355E
PDA PRODUCT OWNERSHIP FLAG COULD NOT BE SET
Reason:
The ownership flag cold not be set.
PUT0356W
CA utilities currently do not fully support statistics for Indexes with a value of 'P' or 'D'
in the INDEXTYPE column of SYSINDEXES.
Therefore, some statistics for these indexes will not be collected. All statistics not
related to these types of indexes will still be collected and the appropriate tables
updated.
Reason:
CA utilities currently do not fully support collection of statistics for indexes with a value
of P or D in the INDEXTYPE column in SYSINDEXES. Some statistics for these indexes will
not be collected.
Action:
No action is required. All statistics not related to these types of indexes will be collected
and appropriate catalog tables will be updated.
596 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0357E
TABLE Processing: Max &KEY name length exceeded
detected processing keyword &KEYW
while processing directive &D
Reason:
The utility attempted to read a parmlib member to process a table, but it encountered a
keyword value that exceeded the maximum length. This may occur if the value for the
tablespace, table, or index name contains one or more symbolics that causes the name
to exceed the maximum length when the symbolic is resolved. &KEY identifies the
object type (tablespace, table, or index). &D identifies the major keyword and &KEYW
identifies the minor keyword parameter that caused the error. Processing stops.
Action:
Determine which parmlib member contains the invalid keyword value by viewing the
PUT0296I message that preceded this message. Correct the specified keyword value so
that it does not exceed the maximum length. Tablespace names can be eight bytes long.
Table and index names can be 128 bytes long. After you have corrected the keyword
value, resubmit the job.
PUT0501E
PUT0501E - Display buffer pool &BP failed.
Return Code:&RC Reason Code:&REAS Module:&MODULE
Reason:
The display buffer pool command failed with the return and reason codes from DB2. If a
connection could not be established, then the return and reason codes were set by the
interface (PTLBDBC).
Action:
Save the job output and contact Technical Support for assistance.
PUT0502I
Max display buffer pool lines reached.
Skipping future writes.
Reason:
The PUT0505I messages will not print because the number of lines printed has exceeded
an internal limit.
Action:
No action is required.
Chapter 3: PUT to QRFM 597
PUT Messages
PUT0503I
BP:&BP busy:&PER.% (&TOT.,&USE.,&UPD.)
Reason:
The buffer pool (&BP) had a percent busy (&PER) that exceeded the threshold
(calculated using the formula &UPD * 100 / &TOT). You must specify ALLMSGS to
activate this message. The message is written to PTIIMSG if allocated, otherwise it is
written to PTIMSG.
Action:
Processing waits two seconds and then tries again.
PUT0504E
cap_message RETURN CODE: return_code
REASON CODE: reason_code
MODULE: module
Reason:
The message provides you with the return code, and reason code.
Action:
See the IBM DB2 Messages and Codes for more information.
PUT0505I
> &MSG
> &MSG
Reason:
An error occurred during results processing because the output of the display buffer
pool command is in a different format. This message shows the output of that
command.
Action:
Save the job output and the '-DISPLAY BUFFERPOOL (BP0)' output, and contact Technical
Support for assistance.
598 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0506I
Retrying PI mode index delete/insert.
Key Retry #&NUM1 of #&NUM2 Buffer Retry #&NUM3 of #&NUM4 for PSID &PSID
Reason- &REASON Key/RID = &RID
Reason:
The utility attempted to delete or insert a key in a nonpartitioned index but the buffer
pool was too busy for too long. The DB2 connection has terminated and a longer wait
interval has been entered.
This message provides the following information:
Key Retry
Indicates how many key retries have been attempted and the maximum number of
attempts (for example, #0003 of #0020). Each time this message is issued, the
&NUM1 value increments to indicate processing progress.
Buffer Retry
Indicates how many buffer retries have been attempted and the maximum number
of attempts (for example, #0005 of #02000). Each time this message is issued, the
&NUM3 value increments to indicate processing progress.
PSID
Indicates the PSID of the index being processed.
Reason
Identifies the reason for the retry (for example, "Check Point").
Key/RID
Identifies the KEY RID being updated.
Action:
Processing continues after the wait interval has elapsed. If the error reoccurs, this
message is reissued and the values increase to indicate processing progress.
PUT0507I
Bufferpool busy, retrying get page.
Reason:
The utility was attempting to retrieve an index page from the DB2 buffer pool but the
buffer pool was too busy for too long. The DB2 connection has terminated and a longer
wait interval has been entered.
Action:
Processing continues after the wait interval has elapsed.
Chapter 3: PUT to QRFM 599
PUT Messages
PUT0508I
Get checkpoint for index &IDX is &CNT keys.
Reason:
This informational message appears when the utility is processing partition
independence (PI) index updates. IDX is the PSID and OBID for the index, in hex (for
example, 0008-0009). CNT is the number of get requests that are processed before the
connection is freed and the buffer pool usage is checked.
Action:
No action is required. Processing continues.
PUT0509I
Update checkpoint for index &IDX is &CNT buffers.
BufSz &BS, #Buf &BNUM, Keyl &KEY &MSG
Reason:
This informational message appears when the utility is processing partition
independence (PI) index updates.
■
IDX is the PSID and OBID for the index, in hex (for example, 0008-0009).
■
CNT is the number of buffers of keys that are processed before the connection is
freed and buffer pool usage is checked.
■
BS is the size of one buffer, rounded based on key length and full 4 KB blocks.
■
BNUM is the number of buffers.
■
KEY is the key length plus six bytes of overhead per key.
■
MSG is the buffer pool name.
Action:
No action is required. Processing continues.
PUT0513E
SAF RACROUTE Failed - SAFRC=X'xxxx', RC=X'xxxx', RS=X'xxxxxxxx'
Action:
Refer to the RACROUTE REQUEST=AUTH return and reason codes in the z/OS Security
Server RACROUTE Macro Reference for information to correct this error.
600 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0535E
RDJFCB Error DDNAME: ddname
Reason:
An attempt to validate access to data sets through the specified ddname failed because
the RDJFCB macro call failed. This message is preceded by static or dynamic definition
error messages for the ddname.
Action:
Search the product and JES logs for error messages related to the specified ddname to
identify the root of the problem.
PUT0600E
INDEX: index_name FAILED CHECKSUM PROCESSING
Reason:
The checksum test comparing unloaded and reloaded data failed.
Action:
Check to see if the correct SYSREC data sets were specified (after a restart), or if there
was a hardware failure on the SYSREC device.
PUT0605E
DDNAME ddname NOT FOUND
Action:
Verify the name of the DD names in the JCL and resubmit the job.
PUT0608E
TOTAL OF ALL CLUSTERED INDEX ROWS DOESN'T MATCH TS COUNTS
Reason:
Not all rows are indexed correctly or there are too many index entries.
Action:
You must recreate or recover the index.
Chapter 3: PUT to QRFM 601
PUT Messages
PUT0609E
INDEX CHECKSUM PROCESSING FINISHED UNSUCCESSFULLY
Reason:
The checksum test failed.
Action:
Recover the index.
PUT0609I
INDEX CHECKSUM PROCESSING FINISHED SUCCESSFULLY
Reason:
Informs you that tablespace check sum processing finished successfully.
Action:
None.
PUT0610E
RESTART TABLE &rctype Error; RC = &rc , RSN = &rsn
Reason:
A restart error has occurred.
Action:
Review the return and reason codes to determine the cause of the error. For more
information, see "Return Codes" in the chapter "Introduction."
602 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0611E
Restart Row Utility &util1 , Stmt# &stmt does not match Utility &util2 of SYSIN
Reason:
A Restart statement record was found in the restart table for the specified statement
number from the Restart parm ( RESTART(nnn,parm) ) however, the utilities do not
match.
This error can occur when the syntax has been changed or another job with the same
utility-ID matches an existing statement record in the Restart Table.
Action:
The message identifies the Utility that failed. Use that information to determine what
action to perform for the job that failed:
Restart the failed job.
Determine if a RESTART(TERM) can be executed to remove the restart rows.
PUT0612E
Statement Number &STMT1 of Restart parm does not match Statement Number
&STMT2 of Restart record.
Reason:
A Restart Statement Record was found in the Restart Table but the statement number in
the restart record is not the same as the restart number in the restart parm.
Action:
The failed job can be automatically restarted with the RESTART parm if no statement
number is specified. Otherwise, specify the correct statement number on the RESTART
parm or determine if the failed job can be terminated to remove the restart rows from
the restart table.
PUT0615I
Restart Statement Record found for Stmt# &STMT Utility &UTIL
Reason:
This is an informational message indicating that a Statement Restart record was found
in the RESTART TABLE. The message identifies the STATEMENT NUMBER and UTILITY.
Action:
None.
Chapter 3: PUT to QRFM 603
PUT Messages
PUT0700E
SQL ERROR MESSAGE PROCESSING FAILED SQL ERROR CODE = code.
Reason:
An SQL error has occurred.
Action:
See the IBM DB2 Messages and Codes for more information.
PUT0701E
AN SQL ERROR HAS OCCURRED:
Action:
See the IBM DB2 Messages and Codes for more information.
PUT0703E
LINK FOR LOAD MODULE PTLDBZCH FAILED. CONTACT CUSTOMER SUPPORT FOR
ASSISTANCE.
Reason:
Indicates that the utility load of module PTLDBZCH has failed.
Action:
For assistance, contact CA Support at http://ca.com/support.
PUT0704E
INTERNAL DB2 BLOCKS DO NOT MATCH.
Reason:
The utility encountered an internal error.
604 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0705E
LOAD FOR LOAD MODULE [email protected] FAILED. CONTACT CUSTOMER SUPPORT FOR
ASSISTANCE.
Reason:
Indicates that the utility load of module [email protected] has failed.
Action:
For assistance, contact CA Support at http://ca.com/support.
PUT0706E
DEFINE NO Dataset already allocated:
Reason:
This would occur if a load was attempted on a tablespace created DEFINE NO or if one
of the associated indexes were created DEFINE NO. If there is a DEFINE NO object, the
dataset must not exist.
PUT0707E
Unable to complete REPAIR DBD - Must repair DBD
Use the following syntax:
REPAIR DBD REBUILD DATABASE &DBNAME
Reason:
A REPAIR is required to modify the object allocation following the creation of the VSAM
data set for an object that was originally created as DEFINE NO.
Action:
Specify REPAIR DBD REBUILD DATABASE for the database identified in the message text.
PUT0708E
Catalog update failed while creating DEFINE NO dataset:
&DSN
Reason:
An attempt to allocate the data set for an object created as DEFINE NO failed due to a
catalog error.
Action:
Recreate the object without DEFINE NO. The default setting for allocation of VSAM data
sets should be evaluated.
Chapter 3: PUT to QRFM 605
PUT Messages
PUT0709I
REPAIR Utility Failed - REORG Utility will Retry
Reason:
This message occurs during FASTSWITCH YES processing for CA Rapid Reorg with
DATA-AVAILABLE HIGH and CRITICAL when the IBM DB REPAIR utility initially fails and
reorg reissues the utility.
Action:
This is an informational message. No action is required.
PUT0800I
UPDATING CATALOG TABLE SYSINDEXPART WITH NEW QUANTITIES FOR: INDEX:
index_name
Reason:
The SYSINDEXPART column of the DB2 catalog has been updated with new values for
the index named in this message. This message is informational only. No further action
is required.
PUT0802E
SYSINDEXPART UPDATE FAILED WITH SQLCODE -sql_code
Reason:
The update to SYSINDEXPART failed. The message provides you with the SQLCODE. See
the IBM DB2 Messages and Codes for more information.
PUT0830E
PARMLIB ENTRY COPY-BUFFERS IS INVALID
Reason:
The COPY-BUFFERS option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
606 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0831E
PARMLIB ENTRY SORT-APPLSIZE IS INVALID
Reason:
The SORT-APPLSIZE option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
PUT0832E
PARMLIB ENTRY NONLEAF-PCTFREE IS INVALID
Reason:
The NONLEAF-PCTFREE option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
PUT0833E
PARMLIB ENTRY VSAM-BUFFERS IS INVALID
Reason:
The VSAM-BUFFERS option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
PUT0834E
PARMLIB ENTRY IO-BUFFERS IS INVALID
Reason:
The IO-BUFFERS option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
Chapter 3: PUT to QRFM 607
PUT Messages
PUT0835E
PARMLIB ENTRY MAXTASKS IS INVALID
Reason:
The MAXTASKS option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
PUT0836E
PARMLIB ENTRY SORT-FLAG IS INVALID
Reason:
The SORT-FLAG option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
PUT0837E
PARMLIB ENTRY SORT-SORTNUM IS INVALID
Reason:
The SORT-SORTNUM option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
PUT0838E
PARMLIB ENTRY COPY-TASKS IS INVALID
Reason:
The COPY-TASKS option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
608 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0839E
PARMLIB ENTRY SMS-VOLUMES IS INVALID
Reason:
The SMS-VOLUMES option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
PUT0840E
PARMLIB ENTRY COLCARD IS INVALID
Reason:
The COLCARD option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
PUT0841E
PARMLIB ENTRY UNLOAD-TASKS IS INVALID
Reason:
The UNLOAD-TASKS option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
PUT0843E
PARMLIB entry DISCARD-ERROR IS INVALID.
Valid options are: NONE, ABEND, RCxx.
where xx is a number from 5 and 50.
Reason:
The DISCARD-ERROR option is invalid for the utility you are using.
Action:
Remove the keyword or select a valid option and resubmit the job.
Chapter 3: PUT to QRFM 609
PUT Messages
PUT0844E
PARMLIB ENTRY REBUILD-TASKS IS INVALID
Reason:
The REBUILD-TASKS option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
PUT0845E
PARMLIB ENTRY UPDATE-TASKS IS INVALID
Reason:
The UPDATE-TASKS option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
PUT0846E
PARMLIB ENTRY STRIP-TASKS IS INVALID
Reason:
The STRIP-TASKS option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
PUT0847E
PARMLIB ENTRY INPUT-BUFFERS IS INVALID
Reason:
The INPUT-BUFFERS option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
610 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0848E
PARMLIB ENTRY UPDATE-BUFFERS IS INVALID
Reason:
The UPDATE-BUFFERS option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
PUT0849E
PARMLIB ENTRY STRIP-BUFFERS IS INVALID
Reason:
The STRIP-BUFFERS option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
PUT0850E
PARMLIB ENTRY SORT-FILSZMAX IS INVALID
Reason:
The SORT-FILSZMAX option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
Chapter 3: PUT to QRFM 611
PUT Messages
PUT0851E
- PARMLIB entry PAGE-FRAMES is invalid
Reason:
You have exceeded the maximum value permitted for the PAGE-FRAMES parmlib entry,
which is 70. The variables in the message (denoted by xxxx) indicate one of the
following:
■
IS INVALID-The PAGE-FRAMES value you specified is too large.
■
SET TO 70-The utility has set the PAGE-FRAMES value to 70 so that processing can
proceed.
■
PUT0851W PARMLIB ENTRY PAGE-FRAMES SET TO 70
■
PAGE-FRAMES have been set to 70. This message is a warning only. No further
action is required.
PUT0852E
PARMLIB ENTRY DATA-AVAILABLE IS INVALID
Reason:
The DATA-AVAILABLE option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
PUT0853E
PARMLIB ENTRY STOP-LIMIT IS INVALID
Reason:
The STOP-LIMIT option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
612 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0854E
PARMLIB ENTRY UPDATE-CATSTATS IS INVALID
Reason:
The UPDATE-CATSTATS option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
PUT0855E
PARMLIB ENTRY IXBUFFER-SIZE IS INVALID
Reason:
The IXBUFFER-SIZE option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
PUT0856E
PARMLIB ENTRY CENTURY20 IS INVALID
Reason:
The CENTURY20 option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
PUT0857E
PARMLIB ENTRY IXCHECK-SIZE IS INVALID
Reason:
The IXCHECK-SIZE option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
Chapter 3: PUT to QRFM 613
PUT Messages
PUT0858E
PARMLIB ENTRY SYSCOPY IS INVALID
Reason:
The SYSCOPY option is invalid for the utility you are using.
Action:
Remove the keyword and resubmit the job.
PUT0861E
PARMLIB entry RC-NO-OBJECTS-SELECTED is invalid
Reason:
An invalid value was specified for RC-NO-OBJECTS-SELECTED.
Action:
Specify a valid value for RC-NO-OBJECTS-SELECTED. Valid values are 0004–4095.
PUT0862E
PARMLIB entry RC-OBJS-AUTO-EXCLUDED is invalid
Reason:
An invalid value was specified for RC-OBJS-AUTO-EXCLUDED.
Action:
Specify a valid value for RC-OBJS-AUTO-EXCLUDED. Valid values are 0000–0004.
PUT0863E
PARMLIB entry GDG-LIMIT is invalid
Reason:
An invalid value has been specified for GDG-LIMIT.
Action:
Specify a valid value for GDG-LIMIT. Valid values are 1–255.
614 Message Reference Guide (PS to ZLB)
PUT Messages
PUT0870E
PARMLIB entry SORT-HIPERMAX is invalid
Reason:
The value specified for the SORT-HIPERMAX parameter in the UTIL parmlib member is
not an acceptable value for SORT.
Action:
Specify a valid hyperspace sort size for the SORT-HIPERMAX. See your sort manual for
acceptable values or specify NONE.
PUT0871E
PARMLIB entry SORT-MOSIZE is invalid
Reason:
The value specified for the SORT-MOSIZE parameter in the UTIL parmlib member is not
an acceptable value for SORT.
Action:
Specify a valid value for SORT-MOSIZE. Acceptable values are 0-9999, 0-100%, MAX, or
NONE.
PUT0910E
'utl' FAILED ON OPEN TO 'ddn'
Reason:
The failure to open the DDNAME (SYSIN, TASKLIB, or SYSPRINT) prevented the utility
from functioning.
PUT0912E
DB2 xxxxxxxx Utility ABENDED - ECB: xxxxxxxx
Reason:
The utility identified by DB2 xxxxxxxx was not able to complete successfully. After a call
to the DB2 DSNUTILB, the ECB is posted with one of the following abend codes:
'40xxx000' for system abends or '40000xxx' for user abends (xxx is the abend code). ECB
can also be '40xxxxxx', where xxxxxx is the low order 24 bits of register 15 at
termination.
Chapter 3: PUT to QRFM 615
PUT Messages
PUT0915E
QUIESCE UPDATE FAILED WITH SQLCODE -sql_code
Action:
An attempted quiesce failed for the reason indicated by the SQL error code displayed in
this message. See the IBM DB2 Messages and Codes for more information.
PUT0920E
DDNAME ddname FAILED ALLOCATION
Reason:
Indicates that the indicated ddname could not be allocated.
Action:
See any other messages produced at this time and check your JCL.
PUT0950E
DATASET HAS MORE THAN 133 VOLUMES, SPACE DEFINITION CANCELLED
Reason:
The utility could not perform space definition because the data set has more than 133
volumes.
PUT2021E
DATASET IN USE DELETE FAILED DETECTED IN MODULE module
Reason:
Because the data set is in use, a DELETE failed in the specified module.
PUT2021W
DATASET IN USE ATTEMPTING RETRY DETECTED IN MODULE module
Reason:
Since the data set is in use, a RETRY is being attempted in the specified module. This
message is a warning. Processing continues.
616 Message Reference Guide (PS to ZLB)
PUT Messages
PUT2060E
INDEX: index_name
ALLOCATION FAILED RETURN CODE: return_code
REASON CODE: reason_code
INFO CODE: info_code DETECTED IN MODULE module
Reason:
Allocation failed for the index named in this message. The message provides you with
the return code, and reason code.
Action:
See the IBM DB2 Messages and Codes for more information.
PUT2061E
LISTCAT FAILED FOR INDEX index_name DETECTED IN MODULE module
Reason:
The LISTCAT has failed for the specified index. Check to be sure you have spelled the
index name correctly. Check to see if the index exists. Also make sure you have the
proper authorities to allocate, read from, and write to the index. Also check for system
messages in the job output. If there are no messages, attempt to perform a LISTCAT ENT
('index name') ALL command using the same ID that executed the job. This might display
a message indicating the reason the LISTCAT command failed.
PUT2062E
REDEFINITION FAILED FOR INDEX index_name DETECTED IN MODULE module VCAT
DEFINED DATASET dataset_name MUST BE REALLOCATED PRIOR TO RESTART
Reason:
The redefinition failed for the index named in this message. A VCAT data set with the
name given in this message must be reallocated prior to RESTART.
Action:
Check for system messages in the job output for the cause of the error. Some causes of
failure are: space not available, authorization lacking to delete or define the data set, or
volume not mounted.
Chapter 3: PUT to QRFM 617
PUT Messages
PUT2063I
INDEX :index_name REDEFINITION COMPLETE
Reason:
The redefinition of the index named in this message is complete.
Action:
This message is informational only. No further action is required.
PUT2064E
DATASET RECALL FAILED FOR INDEX index_name DETECTED IN MODULE module
Reason:
A data set recall for the index named in this message has failed.
Action:
Check the spelling of the index and resubmit the job.
PUT2065W
IDCAMS ADDVOL FAILED FOR INDEX index_name DETECTED IN MODULE module
Reason:
A IDCAMS ADDVOLUME for the index named in this message has failed.
Action:
Check the spelling of the index and resubmit the job.
PUT2066W
INVALID CALCULATION FORMULA FOR field VALUE RESET
Reason:
You have supplied an invalid calculation formula for the field named in this message.
The value was reset to its prior value.
Action:
This message is a warning. Processing continues.
618 Message Reference Guide (PS to ZLB)
PUT Messages
PUT2069E
TARGET DATASET NAME MISSING FOR INDEX index_name
RETURN CODE: return_code
REASON CODE: reason_code
INFO CODE: info_code DETECTED IN MODULE module
Reason:
The target data set name is missing for the index named in this message. The message
provides you with the return code, and reason code. See the IBM DB2 Messages and
Codes for more information.
PUT2089E
INDEX: ixname TARGET DSN MISSING IN MODULE: module RC => rc REASON => reas
INFO => info
Reason:
The B00x data sets for the specified object must be defined before running the
DATA-AVAILABLE HIGH reorg. Because the object is user-defined, (not
subgroup-defined) with SPACE-DEFN NO, the utility cannot define the B00x data sets
for the user.
Action:
Define the target data sets and rerun the job.
PUT2100E
MMGR PUT ROUTINE FAILED
RETURN CODE: Xreturn_code
REASON CODE: Xreason_code DDNAME: ddname MODULE: module_name
Reason:
The specified Media Manager function failed within the indicated module. Most likely,
you need to allocate more space for the data set. The task control block, return code,
reason code, buffer, and data set name are provided.
Action:
See the IBM DB2 Messages and Codes manual to review any accompanying IBM related
messages given with this error message.
Chapter 3: PUT to QRFM 619
PUT Messages
PUT2101E
CSECT module ABENDED X'estaeid' ESTAE INTERCEPTED
Reason:
The utility has encountered an internal error.
PUT2102E
INDEX :dataset_name MAXIMUM DATASETS EXCEEDED
Reason:
The maximum number of data sets allowed for the index named in this message has
been exceeded.
PUT2103I
INDEX :dataset_name OPENED FOR REBUILD
Reason:
The index data set named in this message has been opened for REBUILD.
Action:
This message is informational only. No further action is required.
PUT2104E
NUMBER OF PAGES EXCEEDS MAXIMUM ALLOWED FOR IX PART part
Reason:
The maximum number of pages allowed for the index partition has been exceeded.
PUT2105I
INDEX :index_name RELOAD row_count KEYS
Reason:
This index named in this message has reloaded the number of keys also given in this
message.
Action:
This message is informational only. No further action is required.
620 Message Reference Guide (PS to ZLB)
PUT Messages
PUT2106E
ERROR CLOSING DATASET RETURN CODE return_code, REASON CODE reason_code
DATASET: dataset_name MODULE:
module
Reason:
The data set could not be closed. The message provides you with the return code, and
reason code (as well as the data set and module names). See the IBM DB2 Messages
and Codes for more information.
PUT2107E
ERROR WRITING DATASET RETURN CODE return_code, REASON CODE reason_code
DATASET: dataset_name MODULE:
module
Reason:
The data set could not written. The message provides you with the return code, and
reason code (as well as the data set and module names). See the IBM DB2 Messages
and Codes for more information.
PUT2108E
ERROR READING DATASET RETURN CODE return_code, REASON CODE reason_code
DATASET: dataset_name MODULE:
module
Reason:
The data set could not be read. The message provides you with the return code, and
reason code (as well as the data set and module names). See the IBM DB2 Messages
and Codes for more information.
PUT2109E
TABLESPACE DATASET FAILED ALLOCATION DATASET: dataset_name
MODULE:
module
Reason:
The tablespace data set could not be allocated.
Chapter 3: PUT to QRFM 621
PUT Messages
PUT2110E
ERROR OPENING DATASET RETURN CODE return_code, REASON CODE reason_code
DATASET: dataset_name MODULE:
module
Reason:
The data set could not be opened. The message provides you with the return code, and
reason code (as well as the data set and module names). See the IBM DB2 Messages
and Codes for more information.
PUT2111I
TCB: tcb *TRACE* dataset_name TCB: tcb *TRACE* MODULE: module PG#: page I_PG#:
&int_page
Reason:
This is an informational message that gives the TCB (task control block) , trace data set
name, trace module as well as page numbers. No further action is required.
PUT2200E
Error Initializing Index Compression Size Service
Return Code &rtn., Reason Code &rsn
Module: &module
Reason:
The Index Compression Size Service failed to initialize properly. Processing terminates.
The module name issuing this message is identified by &module. The return code (&rtn)
and reason code (&rsn) indicate the specific failure. This message can indicate
insufficient region size or improperly applied maintenance or storage overlays.
Action:
For return code 08 with reason code 14, increase the region size.
For all other return and reason codes, contact CA Support for assistance.
More information:
Utilities Index Compression Size Service Return and Reason Codes (see page 61)
622 Message Reference Guide (PS to ZLB)
PUT Messages
PUT2201E
Error Initializing Index Compression Service
Return Code &rtn., Reason Code &rsn
Module: &module
Reason:
The Index Compression Service failed to initialize properly. Processing terminates. The
module name issuing this message is identified by &module. The return code (&rtn) and
reason code (&rsn) indicate the specific failure. This message can indicate a missing
service module, improperly applied maintenance or storage overlays, or a storage
shortage.
Action:
For return code 20, increase the region size or reduce the MAXSORTS value in the utility
job and then resubmit the job.
For return code 64, verify that the STEPLIB contains the CSLCPINX service module.
For all other return and reason codes, contact CA Support for assistance.
More information:
Utilities Index Compression Service Return and Reason Codes (see page 60)
PUT2202E
Error Compressing Index Page &page
Return Code &rtn., Reason Code &rsn
Module: &module
Reason:
The Index Compression Service failed to compress properly. Processing terminates. The
page number being compressed is &page. The module name issuing this message is
identified by &module. The return code (&rtn) and reason code (&rsn) indicate the
specific failure. This message can indicate improperly applied maintenance or storage
overlays.
Action:
Contact CA Support for assistance.
More information:
Utilities Index Compression Service Return and Reason Codes (see page 60)
Chapter 3: PUT to QRFM 623
PUT Messages
PUT2203E
Error Calculating Size of Index Page &page
Return Code &rtn., Reason Code &rsn
Module: &module
Reason:
The Index Compression Size Service failed to calculate the index page size properly.
Processing terminates. The page number being processed is &page. The module name
issuing this message is identified by &module. The return code (&rtn) and reason code
(&rsn) indicate the specific failure. This message can indicate improperly applied
maintenance or storage overlays.
Action:
Contact CA Support for assistance.
More information:
Utilities Index Compression Size Service Return and Reason Codes (see page 61)
PUT2310E
Index &CR..&IX..&PT. Invalid Index Directory
Reason:
A corrupt index directory page was found (index directory header eyecatch XD
mismatch).
Action:
Recover the indexspace identified in the message.
PUT2311E
Index &CR..&IX..&PT.
Read Error when attempting to access the Index Directory
Reason:
An error occurred while attempting to read an index directory page using IBM Media
Manager.
Action:
You may need to recover the indexspace identified in the message. Contact CA technical
support for assistance.
624 Message Reference Guide (PS to ZLB)
PUT Messages
PUT2312I
*TRACE* &CALL. TCB: &TCB. Enter: &ENTER.
Reason:
This informational message only appears with CA DEBUG options when specified under
the direction of CA technical support.
Action:
No action required.
PUT2410I
Index MMGR Calls Elapsed Time hh:mm:ss:ttt:mmm.
Reason:
Indicates the amount of time required to process the calls to MEDIA MANAGER in MSG
PUT2411I.
The time format is as follows:
■
hh (Hours)
■
mm (Minutes)
■
ss (Seconds)
■
ttt (Thousanths)
■
mmm (Millionths)
Action:
None.
PUT2411I
Index: ixname
Total MMGR Calls: ............nnn
Reason:
Indicates the number of calls made to MEDIA MANAGER to process the INDEX during
the reorganization. ixname refers to the index name and nnn identifies the number of
calls made.
Action:
None.
Chapter 3: PUT to QRFM 625
PUT Messages
PUT2500I
Real Time Statistics tables update processing beginning
Reason:
Indicates the beginning of the process of updating DB2 Real Time Statistics. Updates
only occur on DB2 V7 and up systems whose Real Time Statistics tables have been
defined.
PUT2501I
Real Time Statistics tables update processing complete
Reason:
Indicates the end of the process of updating the DB2 Real Time Statistics.
PUT2542I
TABLESPACE:&tsname Opened for Rebuild - &module
Reason:
The OPEN for the data set specified by the ddname was successful.
Action:
None.
PUT3002E
Restart table initialization error RC: &RC Reason: &REAS
Reason:
A restart error has occurred.
Action:
Review the return and reason codes to determine the cause of the error. For more
information, see "Return Codes" in the chapter "Introduction."
626 Message Reference Guide (PS to ZLB)
PUT Messages
PUT3003I
UTILID
= &UTILID CHECKSUM = &CSUM
UTYPE
= &UTYPE
USERID = &USERID
TIME ACCESSED = &TIMEA
STATUS
= &ACTFLG
The following variations of this message may appear, depending on whether DISPLAY CA
or DISPLAY CA UTIL (active utilities) is requested:
UTILID
= &UTILID STATEMENT = &STM
UTYPE
= &UTYPE
USERID = &USERID
STATEMENT TIME = &TIMEA
STATUS
= &ACTFLG
The following may also appear:
UTILITY TIME = &TIMEA CHECKSUM = &CSUM
JOBNAME
= &JOBNM
PHASE
= &PHASE
DATABASE: &DBNAME OBJECT: &OBJNAME &PRTI &PRT
&ROWI &ROWS STATUS: &STAT
Reason:
This is an informational message. The symbolics have the following values:
■
&UTILID—utility ID
■
&STM—statement number in syntax
■
&UTYPE—utility type (UNLOAD, REORG, and so on)
■
&USERID—user ID that submitted the job
■
&TIMEA—current time of utility
■
&ACTFLG—utility status (ACTIVE or INACTIVE)
■
&CSUM—CHECKSUM value (unique number based on utility syntax and objects that
identifies a specific utility)
■
&JOBNM—job name
■
&PHASE—current or last phase of utility (ALLOCATION, UNLOAD, RELOAD, and so
on)
■
&DBNAME—database name
■
&OBJNAME—tablespace or indexspace pageset name
■
&PRTI—PART or blank if no partition number
■
&PRT—partition number or blank if no partition number
Chapter 3: PUT to QRFM 627
PUT Messages
■
&ROWI—ROWS or blank if not row oriented processing utility
■
&ROWS—last count of rows processed or blank if not row oriented
■
&STAT—status of specific object (UNLOADED, LOADED, RECOVER NEEDED, and so
on)
Action:
Review these informational messages to verify that the utility is executing properly.
Check utility and object status, row counts, and so on. Verify for possible restart of the
utility. If the utility is inactive, this information helps identify whether to restart the
utility. If no restart is desired and no object recovery is needed, you can clean up the
restart rows by either resubmitting the utility job with RESTART(BYPASS) specified in the
EXEC parameter of the JCL, or by resubmitting the utility job with RESTART(TERM),
which terminates the utility and deletes the restart rows. (Some utilities may also reset
the object status; see the RESET-STATUS keyword in the UTIL parmlib member.)
Optionally, you can issue a TERM CA command to clean up restart rows only.
PUT3008E
Invalid Command
Reason:
When using wildcarding with the TERM CA command, at least one database,
spacename, utility-id, or userid must specify filtering criteria. By design, wildcarding will
not allow for the termination of all utilities with a single command.
PUT3037E
Tablespace &DB..&TS.&PT. Exceeds Maximum Datasets.
Reason:
The specified tablespace has exceeded the maximum allowable data set size.
Action:
Create more available space by reorging the tablespace or recreating it with a larger
data set size.
628 Message Reference Guide (PS to ZLB)
PUT Messages
PUT3043E
TABLESPACE:&tsname LOB Insert Error - &module
Internal Reason Code: &reason
Key: &key
RID: &rid
MAPID: &mapid
Reason:
The utility encountered a LOB insert error.
Action:
Refer to the reason code for additional information to help determine the error.
PUT4300E
SUBSYSTEM NOT FOUND IN JES TABLE
Reason:
The DB2 subsystem ID requested is not found in the JES tables that contain available
DB2 subsystem IDs. Verify the spelling.
PUT4301E
INTERNAL DB2 BLOCK DOES NOT MATCH
Reason:
The DB2 subsystem ID requested is not found in the JES tables that contain available
DB2 subsystem IDs or an internal error was found in the JES tables.
PUT4302I
DB2 CATALOG TABLE SYSCOPY UPDATED WITH REORG LOG(NO)
Reason:
The SYSCOPY table in the DB2 catalog has been updated with REORG LOG(NO). This
message is informational only. No further action is required.
PUT4303I
DB2 CATALOG TABLE SYSCOPY UPDATED WITH IMAGECOPY
Reason:
The SYSCOPY table in the DB2 catalog has been updated with IMAGECOPY. This message
is informational only. No further action is required.
Chapter 3: PUT to QRFM 629
PUT Messages
PUT4304E
APPLICATION LACKS MVS APF AUTHORIZATION
Reason:
Certain CA DB2 utility applications must be installed in MVS authorized libraries.
PUT4305E
PTADBZCH Internal Error - Storage Address Invalid (RC 20)
Reason:
An internal error occurred while trying obtain authority to update the DB2 catalog
(probably for SYSCOPY access).
Action:
Contact CA technical support for assistance.
PUT4306I
DB2 CATALOG TABLE SYSCOPY UPDATED WITH LOAD REPLACE LOG(NO)
Reason:
The SYSCOPY table in the DB2 catalog has been updated with REPLACE LOG(NO). This
message is informational only. No further action is required.
PUT4307I
DB2 CATALOG TABLE SYSCOPY UPDATED WITH LOAD LOG(NO)
Reason:
The SYSCOPY table in the DB2 catalog has been updated with LOAD LOG(NO).
Action:
None.
630 Message Reference Guide (PS to ZLB)
PUT Messages
PUT4308I
Index :INDEX [creator.]{idxname}.node SYSCOPY W Row Written
Reason:
When the UPDATE-SYSCOPY parameter is included in a REORG INDEX INDEX
[creator.]{idxname}, this message indicates that a ROW was written to the DB2 Catalog
Table "SYSCOPY".
Action:
You can use the information provided in this message for recovery in case of a job
failure. The node is a unique numeric identifier for the Index. For example, .0001. The W
in the message is an indicator in the DB2 Catalog Table "SYSCOPY" that a REORG is
running.
PUT4309I
Tablespace &DB..&TS..&PT.
DB2 Catalog SYSCOPY inserted with ICTYPE '&ICTYPE.' - &TYPE.
Reason:
A row was inserted into the DB2 SYSCOPY table to register this utility's actions in the
DB2 catalog. &ICTYPE indicates the action performed by the utility (X = REORG LOG YES,
W = REORG LOG NO, Y = LOAD LOG NO, S = LOAD LOG REPLACE NO).
Action:
Verify that the proper utility registration was performed.
PUT4315W
UPDATE FAILED WITH SQLCODE -sql_code
** ATTEMPTING RETRY **
Reason:
The update failed but a RETRY is being attempted. See the IBM DB2 Messages and
Codes for more information on the SQLCODE.
Action:
None.
Chapter 3: PUT to QRFM 631
PUT Messages
PUT4321E
INITIALIZATION OF LOGRBA FAILED
Reason:
An attempt to set up the utility environment has failed.
PUT4322I
Checkpoint Member:x'memb' Range:x'low.rba.lrsn'/x'hi.rba.lrsn'
For the checkpoint being used
Reason:
Provides checkpoint member information for the checkpoint being used:
x'memb' or x'0000'
Specifies the hexidecimal member number in a data sharing or non-data sharing
environment, respectively.
x'low.rba.lrsn'/x'hi.rba.lrsn'
Specifies the low and high RBA or LRSN (log record sequence number) of the
checkpoint being used.
Action:
This is an informational message.
PUT4323I
PSK Member:x'memb' dbname.tsname.part x'rba.lrsn'
For the page set checkpoint found in the checkpoint range
Reason:
For the table being unloaded:
x'memb' or x'0000'
Specifies the hexidecimal member number in a data sharing or non-data sharing
environment, respectively.
dbname
Specifies the database name.
632 Message Reference Guide (PS to ZLB)
PUT Messages
tsname
Specifies the tablespace name.
part
Specifies the partition number relative to zero. This is c'0000' if the table is not
partitioned.
Action:
This is an informational message.
PUT4324I
Log Reader called with Range:x'low.rba.lrsn'/x'hi.rba.lrsn'
For the DB2 log range for all objects being unloaded
Reason:
For all objects being unload:
x'low.rba.lrsn'/x'hi.rba.lrsn'
Specifies the low and high RBA or LRSN (log record sequence number) for all objects
being unloaded.
These values are used when reading the active and archive DB2 logs for all members in a
data sharing environment.
Action:
This is an informational message.
PUT4325I
All DB2 subsystems have stale checkpoints
Buffer pool lookup skipped
Reason:
All DB2 checkpoints are older than 38 hours.
Action:
This is an informational message.
Chapter 3: PUT to QRFM 633
PUT Messages
PUT4326I
Log Range Member:x'0003' Range:x'000D0E60F77A'/x'C6235D4C1D7C'
Reason:
Provides log range member information for the log range being used:
x’memb’ or x'0000'
Specifies the hexadecimal member number in a data sharing or non-data sharing
environment, respectively.
x’low.rba.lrsn’ / x 'hi.rba.lrsn'
Specifies the low RBA and low LRSN to be used for the member.
Action:
None.
PUT4400I
INDEX KEYS LOADED .............value
Reason:
The value given in this message indicates the number of index keys that have been
loaded. This message is informational only. No further action is required.
PUT4400I
INDEX KEYS INSERTED ...........value
Reason:
The value given in this message indicates the number of index keys that have been
inserted. This message is informational only. No further action is required.
PUT4400I
INDEX KEYS DELETED ............value
Reason:
The value given in this message indicates the number of index keys that have been
deleted. This message is informational only. No further action is required.
634 Message Reference Guide (PS to ZLB)
PUT Messages
PUT4401I
LEAF PAGES ....................value
Reason:
The value given in this message indicates the number of leaf pages that exist. This
message is informational only. No further action is required.
PUT4402I
NONLEAF PAGES .................value
Reason:
The value given in this message indicates the number of nonleaf pages that exist. This
message is informational only. No further action is required.
PUT4403I
INDEX LEVELS ..................value
Reason:
The value given in this message indicates the number of index levels that exist. This
message is informational only. No further action is required.
PUT4404I
TOTAL PAGES ACTIVE ............value
Reason:
The value given in this message indicates the number of total active pages that exist.
This message is informational only. No further action is required.
PUT4405I
INDEX: index_name
Reason:
The message gives the name of an index. This message is informational only. No further
action is required.
Chapter 3: PUT to QRFM 635
PUT Messages
PUT4420E
TABLESPACE DATASET FAILED ALLOCATION DATASET WAS MIGRATED RETURN CODE:
return_code
REASON CODE: reason_code
INFO CODE: info_code
Reason:
The tablespace data set could not be allocated. The message provides you with the
return code, and reason code. See the IBM DB2 Messages and Codes for more
information.
PUT4423I
ALLOCATION COMPLETE FOR dataset_name
Reason:
The data set named in this message has been allocated successfully. This message is
informational only. No further action is required.
PUT4425E
INDEX dataset_name FAILED ALLOCATION
Reason:
The index data set could not be allocated.
PUT4426E
RETURN CODE: return_code
REASON CODE: reason_code
INFO CODE: info_code
Reason:
The message provides you with the return code, and reason code. See the IBM DB2
Messages and Codes for more information.
636 Message Reference Guide (PS to ZLB)
PUT Messages
PUT4427E
INDEXSPACE FAILED OPEN RETURN CODE: return_code
REASON CODE: return_code
MODULE: module
Reason:
An indexspace failed open. The message provides you with the return code, and reason
code. See the IBM DB2 Messages and Codes for more information.
PUT4428W
SPACE-DEFN overrides failed
DSN: &dsn
Reason:
The overrides you specified for SPACE-DEFN have failed.
Action:
Correct the syntax and resubmit the job.
PUT5000E
CATALOG ACCESS PACKAGE INITIALIZATION HAS FAILED. PLEASE CONTACT CUSTOMER
SUPPORT FOR ASSISTANCE.
Action:
For assistance, contact CA Support at http://ca.com/support.
PUT5001E
CATALOG ACCESS PACKAGE OPEN HAS FAILED. PLEASE CONTACT CUSTOMER SUPPORT
FOR ASSISTANCE.
Action:
For assistance, contact CA Support at http://ca.com/support.
Chapter 3: PUT to QRFM 637
PUT Messages
PUT5002E
CATALOG ACCESS PACKAGE FETCH FOR type HAS FAILED. PLEASE CONTACT
CUSTOMER SUPPORT FOR ASSISTANCE.
Action:
For assistance, contact CA Support at http://ca.com/support.
PUT5003E
THE field HAS CHANGED FOR type 'name1..name2.' SINCE THE START OF THIS UTILITY.
Reason:
The field named in this message has changed since the utility started.
PUT5004E
A NEW field HAS BEEN ADDED TO type 'name1..name2.' SINCE THE START OF THIS
UTILITY.
Reason:
The field named in this message has been added since the utility started.
PUT5005E
AN SQL ERROR HAS OCCURRED IN CSECT 'csect':
Reason:
Indicates that the utility has encountered an unexpected SQL error in its processing. The
location of the SQL error is listed.
PUT5006E
AN ERROR HAS OCCURRED TRYING TO FORMAT THE SQL ERROR.
Reason:
An error has occurred trying to format the SQL error.
PUT5007E
ANOTHER UTILITY HAS BEEN RUN SINCE THE START OF THIS UTILITY.
Reason:
Another utility has been run since the start of this utility.
638 Message Reference Guide (PS to ZLB)
PUT Messages
PUT5008E
UNEXPECTED ERROR IN SVC 26
Action:
An unexpected error has occurred in SVC 26.
PUT5009I
num CANDIDATE VOLUMES WERE SUCCESSFULLY ADDED TO DATASET dataset_name.
Reason:
The value given in this message indicates the number of candidate volumes that were
successfully added to the data set named in the message.
Action:
This message is informational only. No further action is required.
PUT5010I
num CANDIDATE VOLUMES WERE SUCCESSFULLY REMOVED FROM DATASET
dataset_name.
Reason:
The value given in this message indicates the number of candidate volumes that were
successfully removed from the data set named in the message.
Action:
This message is informational only. No further action is required.
PUT5012I
THE FOLLOWING DATASET DOES NOT EXIST: dataset_name.
Reason:
The data set named in this message does not exist. This message is informational only.
No further action is required.
Chapter 3: PUT to QRFM 639
PUT Messages
PUT5500E
Invalid Syntax found when parsing &WHERE Clause
Reason:
There is invalid syntax in the &WHERE clause.
Action:
Verify the &WHERE clause and resubmit.
PUT5501E
&WHERE Clause: Constant Value is Invalid
Reason:
There is a constant in the &WHERE clause that is invalid.
Action:
Verify the constant in the &WHERE clause and resubmit.
PUT5502E
&WHERE Clause: Comparison Operator is Unknown
Reason:
There is a comparison operator in the &WHERE clause that is invalid.
Action:
Verify the comparison operator in the &WHERE clause and resubmit.
PUT5503E
&WHERE Clause: Current Date Syntax is Incorrect
Reason:
There is an invalid current date syntax in the &WHERE clause.
Action:
Verify the current date syntax in the &WHERE clause and resubmit.
640 Message Reference Guide (PS to ZLB)
PUT Messages
PUT5504E
TABLE NAME FOR ROW-SELECTION NOT FOUND IN THIS TABLESPACE
Reason:
You have specified a row-selection for a table that cannot be found. Check the spelling
of the table name and resubmit the job.
PUT5505E
COLUMN: column_name WAS NOT FOUND IN SELECTED TABLE
Reason:
The column name given in this message was not found in the selected table. Check the
spelling of the column name and resubmit the job.
PUT5506E
COLUMN: column_name NUMERIC FIELD GREATER THAN 15 BYTES
Reason:
The column name given in this message is a numeric field greater than 15 bytes. Correct
the name and resubmit the job.
PUT5507E
COLUMN: column_name IS COMPARING AGAINST A NON-NUMERIC FIELD
Reason:
You have specified a column name that is numeric and cannot be compared against a
non-numeric field.
PUT5508E
COLUMN: column_name HAS AN UNSUPPORTED DATA TYPE
Reason:
The column name given in this message has an unsupported data type. Verify the data
in the column and resubmit the job.
Chapter 3: PUT to QRFM 641
PUT Messages
PUT5509E
COLUMN: column_name STARTING/ENDING POSITION INVALID
Reason:
The column name given in this message has an invalid starting or ending position.
PUT5511E
COLUMN: column_name IS NOT NULL DEFINED COLUMN
Reason:
The column name given in this message is not a NULL column.
PUT5513W
COMPARE VALUE EXCEEDS MAXIMUM ALLOWABLE POSITIVE VALUE FOR A SMALLINT
Reason:
You have attempted a compare value that exceeds the maximum allowed for a
SMALLINT.
PUT5514W
COMPARE VALUE EXCEEDS THE MAXIMUM ALLOWABLE NEGATIVE VALUE FOR A
SMALLINT
Reason:
You have attempted a compare value that exceeds the maximum allowed negative
value for a SMALLINT.
PUT5515W
COMPARE VALUE EXCEEDS THE MAXIMUM ALLOWABLE NEGATIVE VALUE FOR AN
INTEGER
Reason:
You have attempted a compare value that exceeds the maximum allowed negative
value for a INTEGER.
642 Message Reference Guide (PS to ZLB)
PUT Messages
PUT5516W
COMPARE VALUE EXCEEDS THE MAXIMUM ALLOWABLE POSITIVE VALUE FOR AN
INTEGER
Reason:
You have attempted a compare value that exceeds the maximum allowed positive value
for a INTEGER.
PUT5517E
COLUMN: column_name COMPARISON TIMESTAMP SYNTAX IS INVALID
Reason:
The column name given in this message cannot be compared to a TIMESTAMP.
PUT5518E
&WHERE Clause: Date Function not Valid
Reason:
There is a date function in the &WHERE clause that is invalid.
Action:
Verify the date function in the &WHERE clause and resubmit.
PUT5519E
&WHERE Clause: Numeric Literal not Valid
Reason:
There is a numeric literal in the &WHERE clause that is invalid.
Action:
Verify the numeric literal in the &WHERE clause and resubmit.
PUT6000E
RID X'rid' WAS NOT FOUND IN INDEX creator.name. PLEASE CONTACT CUSTOMER
SUPPORT FOR ASSISTANCE. KEY DATA WAS:
Action:
For assistance, contact CA Support at http://ca.com/support.
Chapter 3: PUT to QRFM 643
PUT Messages
PUT6000E
RID X'rid' COULD NOT BE LOCATED IN DATASET. PLEASE CONTACT CUSTOMER
SUPPORT FOR ASSISTANCE.
Action:
For assistance, contact CA Support at http://ca.com/support.
PUT6001E
LOAD FAILED FOR EDITPROC 'module.'
Reason:
The load of the ediproc named in this message failed.
PUT6002E
BAD FUNCTION REQUEST TO PROGRAM [email protected] WHILE PROCESSING INDEX
creator.name. PLEASE CONTACT CUSTOMER SUPPORT FOR ASSISTANCE.
Action:
For assistance, contact CA Support at http://ca.com/support.
PUT6003E
OPEN FAILED FOR UTILDS DDNAME ddname.
WHILE PROCESSING INDEX creator.name.
Reason:
The DDNAME could not be opened.
Action:
Check the spelling of the DDNAME.
PUT6004E
UTAGLDEB FAILED WITH RETURN CODE: 'return_code.' WHILE PROCESSING INDEX
creator.name.
Reason:
The UTAGLDEB failed with the return code given in this message.
644 Message Reference Guide (PS to ZLB)
PUT Messages
PUT6005E
type EXCP ERROR WHILE PROCESSING INDEX creator.name. PLEASE CONTACT
CUSTOMER SUPPORT FOR ASSISTANCE.
Action:
For assistance, contact CA Support at http://ca.com/support.
PUT6006E
THE PAGE NUMBER READ X'read' DOES NOT MATCH THE EXPECTED PAGE NUMBER
X'&EXPECTED.' WHILE PROCESSING INDEX creator.name. PLEASE CONTACT
CUSTOMER SUPPORT
Action:
For assistance, contact CA Support at http://ca.com/support.
PUT6007E
PAGE NUMBER BEING READ WHILE PROCESSING INDEX creator.name. IS NOT IN THE
TABLESPACE PLEASE CONTACT CUSTOMER SUPPORT FOR ASSISTANCE.
Reason:
Processing error.
Action:
For assistance, contact CA Support at http://ca.com/support.
PUT6008E
INVALID RBA ENCOUNTERED WHILE PROCESSING INDEX creator.name. PLEASE
CONTACT CUSTOMER SUPPORT FOR ASSISTANCE.
Reason:
Processing error.
Action:
For assistance, contact CA Support at http://ca.com/support.
Chapter 3: PUT to QRFM 645
PUT Messages
PUT6009E
BAD NEW PAGE NUMBER ENCOUNTERED WHILE PROCESSING INDEX creator.name.
PLEASE CONTACT CUSTOMER SUPPORT FOR ASSISTANCE.
Reason:
Processing error.
Action:
For assistance, contact CA Support at http://ca.com/support.
PUT6010E
BAD SPACEMAP EXTEND WHILE PROCESSING INDEX creator.name. PLEASE CONTACT
CUSTOMER SUPPORT FOR ASSISTANCE.
Action:
For assistance, contact CA Support at http://ca.com/support.
PUT6011E
type ERROR AGAINST VSAM DATASET
'data_set.' RETURN CODE: return_code., REASON CODE: reason_code
Reason:
The message provides you with the return code, and reason code. See the IBM DB2
Messages and Codes for more information.
PUT6012E
ALLOCATE FAILED FOR DATASET 'data_set.' RETURN CODE: return_code., REASON
CODE: reason_code
Reason:
The message provides you with the return code, and reason code. See the IBM DB2
Messages and Codes manual for more information.
PUT6013E
PREFORMAT FAILED: message
Reason:
The PREFORMAT failed due to the reason given in this message.
646 Message Reference Guide (PS to ZLB)
PUT Messages
PUT6014E
ALLOCATE FAILED FOR UTILDS DATASET CHECK UTIL PARMLIB MEMBER
Reason:
The UTILDS data set failed allocated. Check the UTIL parmlib member.
PUT6015E
ATTACH FOR MODULE module FAILED
Reason:
The ATTACH for the module named in this message failed.
PUT6016E
ZL TREE IS MISSING.
Reason:
ZL tree is missing.
PUT6017E
ROW HARDWARE COMPRESSION FAILED.
Reason:
Row hardware compression failed.
PUT6018E
CALL TO EDITPROC FAILED.
Reason:
Editproc call failed.
PUT6019E
AN INDEX SUBTASK HAS ABENDED.
Reason:
An index subtask has abended.
Chapter 3: PUT to QRFM 647
PUT Messages
PUT6020E
INDEX INSERT KEY WITH RID X'rid' IS A DUPLICATE. PLEASE CONTACT CUSTOMER
SUPPORT FOR ASSISTANCE.
Action:
For assistance, contact CA Support at http://ca.com/support.
PUT6021E
THE AMOUNT OF FREE SPACE IN INDEX PAGE X'page' CALCULATED DURING GARBAGE
COLLECTION WAS LESS THAN THE AMOUNT SPECIFIED IN THE PAGE HEADER.
Reason:
Processing error.
PUT6022E
DUPLICATE KEYS FOUND WHILE SPLITTING A NON-LEAF PAGE. PLEASE CONTACT
CUSTOMER SUPPORT FOR ASSISTANCE.
Action:
For assistance, contact CA Support at http://ca.com/support.
PUT6023E
A BAD INDEX PROCESS REQUEST TYPE WAS FOUND. PLEASE CONTACT CUSTOMER
SUPPORT FOR ASSISTANCE.
Action:
For assistance, contact CA Support at http://ca.com/support.
PUT6024E
STORAGE ACQUISITION HAS FAILED. PLEASE TRY INCREASING REGION SIZE. IF THIS
FAILS, CONTACT CUSTOMER SUPPORT FOR ASSISTANCE. THE GETMAIN FAILED IN
CSECT 'csect'
Action:
Try increasing the region size in your JCL.
For assistance, contact CA Support at http://ca.com/support.
648 Message Reference Guide (PS to ZLB)
PUT Messages
PUT6025W
UNABLE TO ADJUST VSAM VOLUME EXTENT QUANTITY FOR DATASET data_set.
Reason:
Processing error.
PUT6026E
UNKNOWN CALL TYPE, PLEASE CALL CUSTOMER SUPPORT
Action:
For assistance, contact CA Support at http://ca.com/support.
PUT6027E
UNUSABLE UCB TYPE ENCOUNTERED WHILE PROCESSING INDEX creator.name. PLEASE
CALL CUSTOMER SUPPORT
Action:
For assistance, contact CA Support at http://ca.com/support.
PUT6028E
INVALID DATATYPE, PLEASE CALL CUSTOMER SUPPORT
Action:
For assistance, contact CA Support at http://ca.com/support.
PUT6029E
RID X'rid' WAS NOT FOUND IN INDEX creator.name. FOUND RID X'&BADRID.'
INSTEAD.
PLEASE CONTACT CUSTOMER SUPPORT FOR ASSISTANCE. MODULE INFO CODE WAS
X'info.'.
KEY DATA WAS:
Reason:
Processing error.
Action:
For assistance, contact CA Support at http://ca.com/support.
Chapter 3: PUT to QRFM 649
PUT Messages
PUT6030E
RID X'rid' WAS NOT FOUND IN INDEX creator.name. PLEASE CONTACT CUSTOMER
SUPPORT FOR ASSISTANCE.
MODULE INFO CODE WAS X'info_code.'.
KEY DATA WAS:
Reason:
Processing error.
Action:
For assistance, contact CA Support at http://ca.com/support.
PUT6031E
ATTEMPTING TO OBTAIN PAGE X'00000000' DURING INSERT PROCESS FOR INDEX
creator.name. PLEASE CONTACT CUSTOMER SUPPORT FOR ASSISTANCE. RID X'rid'
MODULE INFO CODE WAS X'info_code.'
KEY DATA WAS:
Reason:
Processing error.
Action:
For assistance, contact CA Support at http://ca.com/support.
PUT6100E
I/O ERROR DURING function RETURN CODE: return_code.,REASON CODE: reason_code
FOR dataset_name
DETECTED IN CSECT csect
Reason:
The message provides you with the return code, and reason code. See the IBM DB2
Messages and Codes for more information.
Action:
For assistance, contact CA Support at http://ca.com/support.
650 Message Reference Guide (PS to ZLB)
PUT Messages
PUT6101E
INVALID PAGE page_number DETECTED IN CSECT csect Previous page: previous_page
DSN: dataset_name
Reason:
The utility detected a nonleaf data page while reading the next leaf page in logical
sequence from an index object. Processing stops.
Action:
Save the dump output and the console output, and examine them to determine the
cause of the problem. If the same pages are repeatedly reported from this program,
other DB2 utilities, or SQL accesses to the same object, you may have a corrupt index.
PUT6103E
Unable to load DB2 service module
Func=&function, Service: &service, &subservice
RC=&rc, RSN=&rsn, INFO=&info
Detected in &module
Reason:
The utility cannot access a DB2 service module that is required to process the current
database component. Processing stops.
This message provides the following information:
&function
Indicates the function that was taking place when the error occurred (INIT, LOAD, or
TERM).
&service
Indicates the primary service area in which the error occurred. This area may be a
module name or a functional area such as INDEX.
&subservice
Indicates the specific service. The service may be a CSECT name or a functional
name such as COMP for compression or DECOMP for decompression.
Chapter 3: PUT to QRFM 651
PUT Messages
&rc, &rsn, &info
Indicate the return code, reason code, and information code from the CSALCMOD
service routine.
&module
Indicates the name of the program issuing this message.
Action:
Verify that the IBM DB2 load library is in the STEPLIB or link list concatenation, and then
resubmit the job.
PUT6104E
Decompression of index leaf page failed
RC=&rc, Page=&pagenbr
Detected in &module
Reason:
The DB2 decompression service failed when it was called to decompress the index leaf
page for a compressed index. Processing stops.
This message provides the following information:
&rc
Indicates the decompression service return code.
&pagenbr
Indicates the index leaf page number being decompressed.
&module
Indicates the name of the program issuing this message.
Action:
The index leaf page may be corrupted. View the subsequent messages to identify the
affected tablespace, and then rebuild the index.
PUT6201E
INVALID PAGE page_number DETECTED IN CSECT csect INDEX: creator.name
Reason:
Processing error.
652 Message Reference Guide (PS to ZLB)
PUT Messages
PUT6202E
ERROR OPENING INDEX creator.name
DETECTED IN CSECT csect
PROVIDE THE MESSAGES AND SNAP DUMP TO CUSTOMER SUPPORT
Reason:
Processing error.
Action:
For assistance, contact CA Support at http://ca.com/support.
PUT6203E
ERROR READING INDEX creator.name DETECTED IN CSECT csect PAGE#: page_number
RETURN CODE: return_code
REASON CODE: reason_code PROVIDE THE MESSAGES AND SNAP DUMP TO
CUSTOMER SUPPORT
Reason:
Processing error.
Action:
For assistance, contact CA Support at http://ca.com/support.
Chapter 3: PUT to QRFM 653
PUT Messages
PUT6203I
Error Reading Index CREATOR.SPACE Detected in CSECT MODNAME Attempting
Retry Based on STOP-LIMIT Value.
Where:
- CREATOR is the DB2 space creator's ID.
- SPACE is the index space name.
- MODNAME is the name of the module that detected the error.
Reason:
This message displays when a utility cannot communicate with DB2.
Action:
The utility waits a specified amount of time and tries again. If communication cannot be
established, this message is repeated. This iterative process continues until
communication with DB2 is established or until the number of retries reached the value
of STOP-LIMIT.
PUT6204E
Index &CR..&IX..&PT. GETDIR Error
Expected Page: &EX., Max_Page of Dataset: &MX.
MMGR Return Code: &RTN., Reason Code: &RSN.
Reason:
An IBM Media Manager error occurred while trying to obtain the index page identified
in the message.
Action:
Contact CA technical support for assistance.
PUT6205E
Index &CR..&IX..&PT. PUTSEQ Error
Expected Page: &EX., HURBA: &HU.
MMGR Return Code: &RTN., Reason Code: &RSN.
Reason:
An IBM Media Manager error occurred while trying to write the index page identified in
the message.
Action:
Contact CA technical support for assistance.
654 Message Reference Guide (PS to ZLB)
PUT Messages
PUT6206E
Index &CR..&IX..&PT. PUTCHUNK Error
MMGR Return Code: &RTN., Reason Code: &RSN.
Reason:
An IBM Media Manager error occurred while using EXCP to write a group of index pages
for the index identified in the message.
Action:
Contact CA technical support for assistance.
PUT6207E
HEADER PAGE VALIDATION ERROR DETECTED EXPECTED HPGOBID VALUE:
expected_value READ HPGOBID VALUE:
read_value
Reason:
Processing error.
PUT6208E
Index &CR..&IX..&PT. CHECK Error
MMGR Return Code: &RTN., Reason Code: &RSN.
Reason:
An IBM Media Manager error occurred while checking whether I/O was completed for a
group of index pages for the index identified in the message.
Action:
Contact CA technical support for assistance.
PUT6209E
Index &CR..&IX..&PT. OPEN Error
MMGR Return Code: &RTN., Reason Code: &RSN.
Reason:
An IBM Media Manager error occurred while trying to open the index identified in the
message.
Action:
Contact CA technical support for assistance.
Chapter 3: PUT to QRFM 655
PUT Messages
PUT6210E
Error reading LOB
Internal Error code: &ERRCODE
Reason:
An internal error occurred while the utility was reading a LOB.
Action:
Save the job output and dump (if any) and contact CA Support for assistance.
PUT6242E
VSAM GET routine failed - Return Code: &rtn
Reason Code: &rcode Module: &module
VSAM PUT routine failed - Return Code: &rtn
Reason Code: &rc DDNAME: &ddn Module: &module
MMGR &FUNCTION routine failed in module &module
TCB: &tcb Buffer Address: &buffer
Return Code: &rtn Reason Code: &rcode
DSN: &dsn
Reason:
The first two instances of this message indicate that an error occurred trying to write to
a VSAM page. The module name for which the write error occurred is provided.
This message also occurs when the specified Media Manager function failed within the
indicated module. Most likely, you need to allocate more space for the data set. The
task control block, return code, reason code, buffer, and data set name are provided.
See the IBM DB2 Messages and Codes manual to review any accompanying IBM related
messages given with this error message.
VSAM Return and Reason Codes are documented in VSAM Macro Return and Reason
Codes section of the DFSMS/MVS Macro Instructions for Data Sets manual, or the Macro
Instruction Return Codes and Reason Codes section of the MVS/DFP Macro Instructions
for VSAM Data Sets manual.
Action:
See IBM DB2 Messages and Codes to help you resolve the Media Manager problem.
Locate any accompanying IEC070I or IEC161I messages. These messages, with their
return codes and their explanation from the IBM DB2 Messages and Codes manual, will
also help resolve the problem.
656 Message Reference Guide (PS to ZLB)
PUT Messages
PUT6300E
Storage Acquisition has failed.
The GETMAIN failed in CSECT '&GETCSECT'
Please try increasing REGION Size.
Reason:
The specified REGION size is insufficient for the utility options requested. Processing
stops.
Action:
Increase the region size for this step or change the utility options so that less memory is
requested.
PUT6301E
LOAD for load module [email protected] failed in CSECT '&GETCSECT'
Reason:
An internal error occurred when the utility attempted to load the specified module. This
error may be due to insufficient region size or an authorization failure. Processing stops.
Action:
Increase the region size specified in the JOB statement for this job. Also review the user
authorizations that are required to run this utility. Authorizations are documented in the
user guides for each utility. Then resubmit the job. If the error persists, contact CA
Technical Support for assistance.
Chapter 3: PUT to QRFM 657
PUT Messages
PUT6302E
ENQUEUE failed for IBM mapping table in CSECT '&GETCSECT'
Reason:
The utility attempted to enqueue the mapping table because it is needed by multiple
concurrent jobs. However, an internal error occurred in the specified CSECT. Processing
stops.
Action:
Contact CA Technical Support for assistance and provide the name of the CSECT.
You can use either of the following workarounds to eliminate the need for an enqueue
and process your jobs:
■
When running jobs that require a mapping table, run only one job at a time. Do not
run them concurrently.
■
Do not use serialization when running jobs that require a mapping table. This lets
the utility create and use multiple mapping tables, instead of requiring it to create
and use a single mapping table.
PUT6303E
DEQUEUE failed for IBM mapping table in CSECT '&GETCSECT'
Reason:
The utility attempted to dequeue a mapping table that is needed by multiple concurrent
jobs. However, an internal error occurred in the specified CSECT. Processing stops.
Action:
Contact CA Technical Support for assistance and provide the name of the CSECT.
You can use either of the following workarounds to eliminate the need for a dequeue
and process your jobs:
■
When running jobs that require a mapping table, run only one job at a time. Do not
run them concurrently.
■
Do not use serialization when running jobs that require a mapping table. This lets
the utility create and use multiple mapping tables, instead of requiring it to create
and use a single mapping table.
658 Message Reference Guide (PS to ZLB)
PUT Messages
PUT6304E
SQL &STMT failed with SQLCODE &CODE in CSECT '&GETCSECT'
Reason:
An SQL error occurred when the utility attempted to process the specified SQL
statement in the specified CSECT. Processing stops.
Action:
Look up the SQL code in IBM DB2 Messages and Codes to determine the cause of the
error.
PUT6305I
Mapping table &MAP in use - waiting for another
CA REORG DATA-AVAILABLE CRITICAL job to release it
Reason:
Another CA Rapid Reorg job is currently using the specified mapping table. Your job
cannot process until the mapping table is available.
Action:
No action is required. When the other CA Rapid Reorg job completes, your job will
process. If your job requires immediate processing, you can cancel it, specify a different
mapping table by using the MAPPINGTABLE keyword, and then resubmit the job.
If you frequently encounter this message, consider configuring your PORM parmlib
member to create multiple mapping tables so that you can process multiple CA Rapid
Reorg online jobs concurrently.
For more information about mapping tables, the MAPPINGTABLE keyword, and the
PORM parmlib member, see the CA Rapid Reorg User Guide.
PUT7001E
DYNAMIC ALLOCATION PARSING ERROR HAS OCCURRED IN MODULE module
Reason:
Dynamic allocation has failed.
Chapter 3: PUT to QRFM 659
PUT Messages
PUT7002E
DYNAMIC ALLOCATION
UNKNOWN PARMLIB KEYWORD: keyword
Reason:
The keyword specified in this message is an unknown option.
Action:
Remove the keyword and resubmit the job.
PUT7002I
VALID KEYWORDS: DSN, DISP, NDISP, CDISP AND STORCLASS DETECTED IN MODULE
module
Action:
This message is informational only. No further action is required.
PUT7003E
DYNAMIC ALLOCATION: SYMBOL symbol IS INVALID
Reason:
The symbol given in this error message is invalid for dynamic allocation.
Action:
Remove the symbol and resubmit the job.
PUT7004E
DYNAMIC ALLOCATION: INVALID DATASET NAME NODE: node
Reason:
The name node given in this message in invalid for dynamic allocation.
Action:
Remove the node and resubmit the job.
660 Message Reference Guide (PS to ZLB)
PUT Messages
PUT7005E
DYNAMIC ALLOCATION: INVALID DATASET NAME LENGTH DETECTED IN MODULE
module
Reason:
The length of the data set name is invalid.
PUT7005I
DSN: dataset_name
Reason:
This message is informational only. No further action is required.
PUT7006E
DYNAMIC ALLOCATION: INVALID DISP: data_set DETECTED IN MODULE module
Reason:
The DISP data set named in this message is invalid for dynamic allocation.
PUT7007E
DYNAMIC ALLOCATION: INVALID DATASET NAME: dataset_name DETECTED IN
MODULE module
Reason:
The data set name given in this message is invalid for dynamic allocation.
PUT7008E
DYNAMIC ALLOCATION: PROCESS FAILED FOR module DETECTED IN MODULE module
Reason:
Dynamic allocation failed. The module name is given.
PUT7009I
DYNAMIC ALLOCATION HAS SUCCESSFULLY COMPLETED ISSUED FROM module
Reason:
This message is informational only. No further action is required.
Chapter 3: PUT to QRFM 661
PUT Messages
PUT7010E
DYNAMIC ALLOCATION: ERROR IN PARMLIB PROCESSING RETURN CODE: return_code
Reason:
Dynamic allocation failed. The return code is given.
PUT7010E
DYNAMIC ALLOCATION: ERROR IN SVC 99 DETECTED IN MODULE module
Reason:
Dynamic allocation failed. The module name is given.
PUT7015I
dataset_name message DEALLOCATED
MODULE: module
Reason:
This message is informational only. No further action is required.
PUT7016E
TAPE THRESHOLD PARAMETER IS INVALID DETECTED IN MODULE module
Reason:
The value specified for the TAPE THRESHOLD parameter is invalid in the module given in
this message. Correct the parameter and resubmit the job.
PUT7017E
TAPE EXPIRATION DATE IS INVALID DETECTED IN MODULE module
Action:
Change the TAPE EXPIRATION DATE value and resubmit the job.
PUT7018E
TAPE RETENTION PERIOD IS INVALID DETECTED IN MODULE module
Action:
Change the TAPE RETENTION PERIOD value and resubmit the job.
662 Message Reference Guide (PS to ZLB)
PUT Messages
PUT7019E
TAPE VOLUME COUNT IS INVALID DETECTED IN MODULE module
Action:
Change the TAPE VOLUME COUNT value and resubmit the job.
PUT7020W
SPACE-OVER PARAMETER SUPERCEEDS THRESHOLD PARAMETER DETECTED IN
MODULE module
Action:
Check the values for SPACE-OVER and the THRESHOLD PARAMETER.
PUT7021E
EXPDT AND RETPD ARE MUTUALLY EXCLUSIVE DETECTED IN MODULE module
Reason:
You cannot specify EXPDT and RETPD. Remove one or the other and resubmit the job.
PUT7022E
PCTSPACE PARAMETER IS INVALID DETECTED IN MODULE module
Action:
Change the PCTSPACE value and resubmit the job
PUT9800E
INDEX INSERT FAILED WITH RETURN CODE: return_code
Reason:
The index insert failed. The message provides you with the return code. See the IBM
DB2 Messages and Codes for more information
Chapter 3: PUT to QRFM 663
PUT Messages
PUT9801E
AN ATTEMPT TO INSERT A KEY INTO A UNIQUE INDEX FAILED BECAUSE THE KEY WAS
FOUND TO BE A DUPLICATE OF ONE THAT WAS INSERTED INTO A DIFFERENT
PARTITION WHILE THIS UTILITY WAS RUNNING. THE TABLESPACE AND INDEX
PARTITIONS AND ALL NON-CLUSTERING INDEXES MUST BE RECOVERED.
Action:
Check to see if the key is a duplicate or if you have inserted it into a different partition
while the utility was running. Recover the tablespace and all non-clustering indexes.
PUT9808E
[email protected] Index Space Map error has occurred at page: &pppppppp
IPSNENTS+IPSLUSED: &nnnnuuuu IPSNFREE+IPSFFREE: &ooooffff
Reason:
During a reorganization, the utility encountered an index space map page that was
encoded as being full when that same page was also encoded with available entries. For
this page, the value in IPSNENTS was equal to the value in IPSFFREE, which indicates that
the page is fully populated. However, the IPSNFREE value is greater than zero, which
indicates that the page has more entries that can be used. Processing stops.
This message provides the following information:
&pppppppp
Identifies the index space map page number.
&nnnnuuuu
Provides the following information:
nnnn
Shows the IPSNENTS value for the number of pages covered by this space map
page.
uuuu
Shows the IPSLUSED value for the index of the last used entry.
664 Message Reference Guide (PS to ZLB)
PXA Messages
&ooooffff
Identifies the following information:
oooo
Shows the IPSNFREE value for the number of free entries,
ffff
Shows the IPSFFREE value for the index of the first unused entry.
Action:
Save the job output and contact CA Support.
Note: No recovery is necessary because the reorganization did not complete.
PUT9999I
- MESSAGE PROCESSOR DID NOT FIND MESSAGE ID &id
RELINK THE EXTERNALIZED MESSAGE TEXT OR CONTACT CA-CUSTOMER SUPPORT
Reason:
The indicated message ID is not a valid error message.
Action:
Relink the externalized message text to a valid message ID.
PXA Messages
Messages with the PXA prefix are generated from CA Partition Expert.
PXA0001
KEYWORD IS INVALID - keyword
Reason:
The specified keyword is incorrect.
Action:
Correct the syntax and resubmit the job.
Chapter 3: PUT to QRFM 665
PXA Messages
PXA0002
REPARTITIONING TYPE IS INVALID OR INCOMPATIBLE WITH
SINGLE-PARTITION-NUMBER tt
Reason:
The combination of keywords and values selected for TYPE and associated parameters is
incorrect. The error was discovered in a step after this original error was discovered. The
probable error is an incorrect restart (the wrong step was restarted after an error).
Action:
Review all jobs/steps involved and correct the problem.
PXA0003
SPECIFIED VARIABLE EITHER NOT DEFINED OR INCORRECT LENGTH - value
Action:
Correct the value for the keyword and resubmit the job.
PXA0004
SYNTAX OR LENGTH ERROR - FORMAT IS: KEYWORD VARIABLE
Reason:
While parsing the input statement an error was discovered and parsing stopped. The
format of a statement is one keyword followed by the associated variable. Minimum
and maximum lengths exist for the keywords and variables. Variable entries not within
the limits will fail with this message.
Action:
Correct the syntax and resubmit the job.
PXA0006
INCORRECT OPTIONS CHOSEN FOR TYPE, ROLL-DIRECTION, AND/OR ROLL-METHOD
Reason:
The combination of keywords and values selected is incorrect.
666 Message Reference Guide (PS to ZLB)
PXA Messages
PXA0007
REQUIRED KEYWORD IS MISSING - keyword
Reason:
The required keyword was not found in the input stream.
PXA0008
SINGLE-PARTITION-NUMBER NOT VALID WITH SPECIFIED TYPE
Action:
See the product documentation for the correct TYPE parameters. Correct the syntax and
restart the job.
PXA0010
ERROR SQL CODE xxxxx REFERENCING SYSDBASE OBJECTS FOR CREATOR.TABLE
ccccccc.tttttttttt ON ssid
Reason:
A SQL error occurred terminating the program.
Action:
Review the SQL code in the DB2 Messages and Codes manual to determine the cause of
the failure. Correct the problem or, if the SQL return code is -911, consider running the
job when less catalog contention is occurring.
PXA0011
CREATOR.TABLE ccccccc.tttttttttt IS NOT DEFINED AS A BASE TABLE ON ssid
Reason:
The specified table is not a base table on the subsystem indicated.
Action:
If the table is a view, change the name to the base table name. Correct the problem and
resubmit the job.
Chapter 3: PUT to QRFM 667
PXA Messages
PXA0012
ERROR - CREATOR.TABLE ccccccc.tttttttttt IS NOT A PARTITIONED TABLE ON ssid
Reason:
The specified table is not a partitioned table on the subsystem indicated. The utility only
works on partitioned tables.
Action:
Correct the problem and resubmit the job.
PXA0013
A COLUMN TYPE IN THE ROW CANNOT BE CONVERTED.
Reason:
The row contained a column type which cannot be converted to DB2 external format.
PXA0015
PARSING FOR PARTITION EXPERT STARTED. ONE KEYWORD WITH ONE VARIABLE PER
STATEMENT IS REQUIRED.
Reason:
Parsing the input statements has started. Only one keyword and one variable per
statement is valid.
PXA0016
PARSING FOR PARTITION EXPERT ENDED SUCCESSFULLY
Reason:
Parsing the input statements has ended successfully.
PXA0017
PARSING FOR PARTITION EXPERT ENDED UNSUCCESSFULLY
Reason:
Parsing the input statements has ended unsuccessfully. Other messages appear prior to
this message indicating the error(s).
Action:
Correct the input and restart the job.
668 Message Reference Guide (PS to ZLB)
PXA Messages
PXA0019
SMOOTHING IS ONLY VALID FOR TYPE MULTIPLE
Reason:
The type specified in JOB 1 must be MULTIPLE. Attempting to smooth using the
incorrect type is not allowed.
PXA0020
CAF ERROR RETURN CODE= rrrrrrr REASON CODE= rrrrrrrr, PARMS ffffffffff ssss
pppppppp
Reason:
An error was encountered attempting to attach to DB2 using the call attach (CAF). The
Return and Reason Codes indicate the IBM failure information. The parameters indicate
the CAF function code, the DB2 subsystem, and the plan name involved.
Action:
Correct the problem and restart the job in the failing step.
PXA0021
PARTITION EXPERT HAS EXPIRED ON ssid
Reason:
The product has expired on the subsystem ID indicated.
PXA0022
PARTITION EXPERT STEP CANNOT BE EXECUTED. RETURN CODE= rrrrrrr ON ssid
Reason:
An error was encountered on the DB2 subsystem indicated.
Action:
Refer to the return code for more information.
Chapter 3: PUT to QRFM 669
PXA Messages
PXA0023
PARTITION VALUE IS INVALID - RETURN CODE = x
Reason:
The partition value is invalid. Return codes are as follows:
■
1-Zero or an invalid hex value supplied.
■
2-Value higher than the number of partitions.
■
3-Invalid alpha value - ALL is expected.
■
4-Partitions must be supplied in ascending order.
■
5-Invalid order for partition values. ALL must proceed all partition numbers.
PXA0024
DECIMAL NUMBER IS EITHER INVALID OR ZERO
Action:
Correct the value to a valid decimal number.
PXA0025
INDEX HOT SPOT FOUND
Reason:
The utility has detected that the index leaf pages are no longer clustered for the current
key range.
PXA0026
TABLE HOT SPOT FOUND
Reason:
The utility has detected the table rows are no longer clustered in the order of the
partition index.
670 Message Reference Guide (PS to ZLB)
PXA Messages
PXA0032
ERROR - LIMIT KEY UPDATE/CONVERSION FAILED, REASON CODE = xxx
Reason:
The error is generated attempting to update the CA RC/Migrator data set with new limit
keys. Reason codes are as follows:
■
001-An unexpected end of file condition occurred on the P42 data set. Probable
cause may be that a P42 DD DUMMY data set was found
■
002-The cluster key work found in the CA RC/Migrator file before a create
statement.
■
003-Column names for the index found after the cluster statement
■
004-Column names for the index found after the cluster statement
■
005-The number of columns do not match between the Map data set update during
the unload step and the CA RC/Migrator data set. Correct the mismatch.
■
006-A parenthesis was found in the CA RC/Migrator data set before all the expected
columns were processed
■
007-An unexpected end of file condition occurred on the P42
■
008-An unexpected end of file condition occurred on the P42 data set. Probable
cause may be P42 DD DUMMY data set
■
009-CA Partition Expert expected to be positioned before the cluster statement in
the CA RC/Migrator file.
■
010-CA Partition Expert expected to be positioned after the cluster statement in the
CA RC/Migrator file.
■
011-An incorrect parenthesis was found in the values statement of the CA
RC/Migrator file.
■
012-Conversion failed trying to convert a column from the internal format to
external format. Probable cause is non-supported data type.
■
013-The converted external columns do not fit on the CA RC/Migrator statement.
Probable solution is to specify the dummy key on the statement in column 1 or
reduce the number of columns in the partitioning index. Remember the maximum
length is 40 bytes for a partitioning index.
■
014-The CA Partition Expert map data set created by Job 1 cannot be used.
Probable causes include Job 1 not run, incorrect symbolic references, or the map
data set is not usable
■
015-The number of partitions specified in the Q88 data set create in job 20 do not
match the RC/Migrator specified number of partitions. Correct the mismatch.
■
017-The order by column(s) could not be found using CA Fast Unload. Probable
causes follow.
Chapter 3: PUT to QRFM 671
PXA Messages
The CA Fast Unload step has more than one select statement with different order by
statements. The columns in the order by do not match exactly the columns in the select
that is, SELECT * is invalid as the first select statement.
CA Partition Expert processes the CA RC/Migrator data set and assumes the following:
one column name definitions per statement; the direction if specified appears on the
same statement as the column name; cluster on a statement by itself; expect values on
a statement by itself; expect all the index column values for a partition on one
statement; expect all the supplied external limit keys values to fit on one statement per
partition.
PXA0040
ERROR - xxxxxxxxxxxx ppp OF TABLE cccccccc ttttttttt OLD LIMIT KEY NOT EQUAL TO
DB2 CATALOG ON
ssid
Reason:
The old limit key for SYSIBM.SYSINDEXPART or SYSIBM.SYSTABLEPART partition ppp of
the table specified on the subsystem indicated appears incorrect. The PLQ old limit key
is not equal to the value in the DB2 catalog. Possible causes are: running the job for the
wrong DB2 subsystem, or the old limit key was edited erroneously by the user. The old
limit key values are never to be changed by the user.
Action:
Correct the limit key in error and restart the job in the failing step.
PXA0041
ERROR - xxxxxxxxxxxx ppp OF TABLE cccccccc ttttttttt NEW LIMIT KEY VALUE AND
LENGTH PROBLEM ON ssid
Reason:
The limit key for SYSIBM.SYSINDEXPART or SYSIBM.SYSTABLEPART partition of the table
specified on the subsystem indicated is incorrect. The PLQ limit key appears to have
increased in length, but the length field does not reflect the increase. Correct the length
field in the PLQ data set for the specified partition or shorten the limit key.
Action:
Correct the limit key in error and restart the job in the failing step.
672 Message Reference Guide (PS to ZLB)
PXA Messages
PXA0042
LIMIT KEY CHANGES SYSTABLEPART=xxx SYSINDEXPART=xxx ON ssid
Reason:
Specifies the number of limit keys changed for SYSIBM.SYSINDEXPART and
SYSIBM.SYSTABLEPART. The two counts must be equal or else the updates are rolled
back.
PXA0043
THE NUMBER OF SYSTABLEPART AND SYSINDEXPART CHANGES MUST BE EQUAL AND
APPROXIMATE xxx ON ssid
Reason:
Specifies an error occurred. The number of limit keys changed for
SYSIBM.SYSINDEXPART and SYSIBM.SYSTABLEPART must be equal and the updates were
rolled back.
Action:
Correct the PLQ limit key(s) in error and restart the job.
PXA0044
ERROR MODULE mmmmmmmm RETURN CODE rrrr REASON CODE cccccccc ON ssid
Reason:
Indicates an error was discovered processing the request. If the module is DSNALI, a DB2
connection failure occurred. If the module is PXAREP64, a problem occurred attempting
to read the PLQ data set.
Action:
Correct the problem and restart the job.
Chapter 3: PUT to QRFM 673
PXA Messages
PXA0045
ERROR - xxxxxxxxxxxx ppp OF TABLE cccccccc ttttttttt USER SUPPLIED OLD AND NEW
LIMIT KEYS ARE EQUAL ON ssid
Reason:
The new limit key for SYSIBM.SYSINDEXPART or SYSIBM.SYSTABLEPART partition ppp of
the table specified on the subsystem indicated is the same as the old limit key. The PLQ
new limit key does not appear to be edited. Edit the PLQ data set new partition limit key
in question. Old and new limit keys can be equal when the TYPE is MULTIPLE only.
Action:
Correct the limit key in error and restart the job in the failing step.
PXA0050
ERROR - ZERO LENGTH KEY FOUND FOR PARTITION pppp FOR ssid
Reason:
The PLQ data set contains a zero key for the specified partition. This suggests a user
error during the limit key editing.
Action:
Correct the limit key in error and restart the job in the failing step.
PXA0052
INDEX LIMIT KEY FOR PARTITION pppp MUST BE LESS THAN pppp ON ssid
Reason:
The keys for SYSIBM.SYSINDEXPART must be ascending. The PLQ data set contains a key
for the specified partition that is not ascending. This suggests a user error during the
limit key editing.
Action:
Correct the limit key in error and restart the job in the failing step.
674 Message Reference Guide (PS to ZLB)
PXA Messages
PXA0053
LIMIT KEY FOR PARTITION pppp AND pppp MAY BE INCORRECT - REVIEW THE VALUES
ON ssid
Reason:
The keys for SYSIBM.SYSINDEXPART must be ascending. The PLQ data set contains a key
for the specified partition that is not ascending. The keys are equal for the for the
common length, for example, the length of the shorter key, but the lowest order
partition key length is less than the high key length. It is assumed this is an error
because the shorter key is normally padded with X'FF' making it higher. This suggests an
error during the limit key editing.
Action:
Correct the limit key in error and restart the job in the failing step.
PXA0055
SET UP TO CONVERT LIMIT KEY TO INTERNAL FORMAT FAILED. RETURN CODE xxx
Reason:
The message is generated by PXAREP30. The return codes are as follows:
■
004-No partition number parameter passed to the routine.
■
008-No partitions were processed and the PLQ data set was not updated.
■
016-Non numeric partition number passed as a parameter.
■
020-Problem with the parameter value passed to the routine. The value may not
exist, be greater than 4 digits, or the partition number is greater than the total
number of partitions.
■
024-Problem obtaining and formatting the PLQ information in the PLQ data set.
■
034-Cannot find Map data set for the specified table.
PXA0056
PROBLEM OCCURRED ATTEMPTING TO GENERATE FAST UNLOAD/LOAD STATEMENTS.
RETURN CODE xxx
Reason:
The message is generated by module PXAREP31 and the return codes are as follows:
■
004-No statements generated.
■
024-Problem obtaining and formatting the PLQ information in the PLQ data set.
■
034-Cannot find Map data set for the specified table.
Chapter 3: PUT to QRFM 675
PXA Messages
PXA0060
DYNAMIC ALLOCATION ERROR - REGISTER 5 HAS S99RB ADDRESS. R6 AND R7 HAVE
FIRST 8 BYTES OF S99RB
Reason:
Dynamic allocation, SVC 99, is documented in the MVS/ESA Systems Programming
Library: Application Development Guide. Common errors are the user is not authorized
to read or update the specified data set, or the data set for the roll function is still
allocated by DB2 even though it has been stopped.
PXA0061
DYNAMIC DEALLOCATION ERROR - REGISTER 5 HAS S99RB ADDRESS. R6 AND R7 HAVE
FIRST 8 BYTES OF S99RB
Reason:
Dynamic allocation, SVC 99, is documented in the MVS/ESA Systems Programming
Library: Application Development Guide.
PXA0061
DYNAMIC DEALLOCATION ERROR - REGISTER 5 HAS S99RB ADDRESS. R6 AND R7 HAVE
FIRST 8 BYTES OF S99RB
Reason:
Dynamic allocation, SVC 99, is documented in the MVS/ESA Systems Programming
Library: Application Development Guide.
PXA0070
CLONE PARTITIONED TABLE MUST EXIST IN THE SAME SUBSYSTEM, DATA BASE, WITH
THE SAME LENGTH INDEX NAME
Reason:
The clone partitioned table must reside in the same data base as the original table. Also
the index name for the clone partition index must be the same length as the original
partitioned index.
676 Message Reference Guide (PS to ZLB)
PXA Messages
PXA0071
UNABLE TO FIND VCAT FOR SUBSYSTEM ssss VERIFY JOB WAS RUN ON THE CORRECT
MVS SYSTEM AND DB2 SUBSYSTEM IS PRESENT
Reason:
The job may not have been run on the MVS subsystem that you intended. Verify where
the job was run.
PXA0072
AN UNEXPECTED ERROR OCCURRED. SUBMIT A FULL IBM SYSUDUMP TO CUSTOMER
SUPPORT
Action:
For assistance, contact CA Support at http://ca.com/support.
PXA0073
PARTITION nnn SELECT STATEMENT yyy TOTAL ROWS ANALYZED zzzz
Reason:
This message is generated by the PXAREPE4 exit to CA Fast Unload to indicate the
partition number (nnn), the select statement(yyy), and all the rows analyzed (zzz) for the
select statement.
PXA0074
PARTITION nnn
SELECT STATEMENTy
TOTAL ROWS SELECTED
zzzz
Reason:
This message is generated by the PXAREPE4 exit to CA Fast Unload to indicate the
partition number (nnn), the select statement(yyy), and how many rows were selected
(zzz). The difference between the rows analyzed in message 73 and rows selected in
message 74 indicates the number of rows rejected.
Chapter 3: PUT to QRFM 677
PXA Messages
PXA0075
UNLOAD STATEMENTS
NOT GENERATED - PROBABLE CAUSE IS/ARE PLQ LIMIT KEYS
Action:
This message is generated by module PXAREP31. Check the PLQ limit keys to see if the
values look valid.
PXA0076
PARTITION xxx SELECTION STATEMENT yyy
FAILED. RETURN CODE ccc
Reason:
The message is reserved and the return codes are as follows:
■
004-No statements generated.
■
024-Problem obtaining and formatting the PLQ information in the PLQ data set.
■
034-Cannot find Map data set for the specified table.
PXA0077
ERROR PROCESSING MAP DATASET VERSES FAST UNLOAD COLUMN INFORMATION
Reason:
Modules PXAREPE2 and PXAREPF4 generate the message. The message indicates a
problem between the information obtained in the first CA Partition Expert job and
column information specified to CA Fast Unload.
PXA0078
ERROR AN UNEXPECTED END OF FILE OCCURRED
Reason:
Modules PXAREPF1 and PXAREP42 generate the message. The message indicates a Q88
or PLR data set problem causing the premature end of file.
678 Message Reference Guide (PS to ZLB)
PXA Messages
PXA0079
ERROR OCCCURRED TRYING TO LOAD A MODULE
Reason:
Module PXAREPF4 generates the message.
Action:
Verify the correct CA production load library is in the JOBLIB or STEPLIB for the step.
PXA0100
PARTITION part DSN dsname DATE date TIME xxx SSID ssss
Reason:
The partition number, data set name, date, time and SSID are given in this message.
PXA0101
num % INDEX FULL
Reason:
The percentage full for the index partition. Full is determined by taking the highest RBA
containing index entries and dividing by the maximum RBA allowed for the partition.
PXA0102
num % TABLE FULL
Reason:
The percentage full for the table space partition. Full is determined by taking the highest
RBA containing rows of data and dividing by the maximum RBA allowed for the
partition.
PXA0103
num NUMBER OF TABLE PAGES OVER SPECIFIED %
Reason:
The number of table pages exceeding the percentage full that you specified for the
partition is given in this message.
Chapter 3: PUT to QRFM 679
PXA Messages
PXA0104
num NUMBER OF INDEX PAGES OVER SPECIFIED %
Reason:
The number of index pages exceeding the percentage full that you specified for the
partition is given in this message.
PXA0105
num TABLE CLUSTER RATIO
Reason:
The table cluster ratio is returned. The ratio is based on the table rows being in the
partitioning index clustering sequence. A ratio of 100% says the data rows are in the
same sequence as the partitioning index.
PXA0106
num INDEX CLUSTER RATIO
Reason:
The index cluster ratio is returned. The ratio is based on the distance from one leaf page
to the next higher key index page. A ratio below 92% indicates the index is becoming
disorganized and may need reorganization.
PXA0107
xxx INDEX HIGH PAGE NUMBER - HEX
Reason:
The highest index leaf page found page number is given.
PXA0108
row_num ROW
HIGH PAGE NUMBER - HEX
The highest table space row page number is given.
680 Message Reference Guide (PS to ZLB)
PXA Messages
PXA0109
XXX TOTAL NUMBER OF UNIQUE INDEX KEYS
Reason:
The total number of unique index keys is given.
PXA0111
xxx TOTAL NUMBER OF VALID RIDS
Reason:
The total number of rids is given. This value includes valid and pseudo deleted rids.
PXA0113
TOTAL NUMBER OF PSEUDO DELETED RIDS
Reason:
The total number of pseudo deleted rids is given. Pseudo deleted rids occupy space but
do not point at a data row.
PXA0114
TOTAL NUMBER OF UNCOMMITTED RIDS
Reason:
The total number of uncommitted rids is given.
PXA0115
TOTAL NUMBER OF DELETED INDEX KEYS
Reason:
The total number of index keys deleted is given. This can occur if all the rids are pseudo
deleted for a given index key.
PXA0116
TOTAL NUMBER OF RID CHAINS
Reason:
The total number of RID chains is given. Rid chains occur if space does not exist when a
new rid is added for an existing non-unique index key.
Chapter 3: PUT to QRFM 681
PXA Messages
PXA0117
xxx ROWS TO BE MOVED TO PARTITION part_num, CONSIDER USING PARTITION LOAD
RESUME
Reason:
Rows in the current partition are to be moved to a new partition. The user needs to
unload the current partition and then load xxx rows into the new partition. LOAD
RESUME can be used add rows to a partition.
Action:
See message PXA0118 for information on reloading a current partition.
PXA0118
ROWS TO BE REMOVED FROM PARTITION part_num, CONSIDER USING PARTITION
LOAD REPLACE
Reason:
Some rows in the current partition are being moved to another partition (see message
PXA0117). The current partition needs to be unloaded and then the existing rows must
be reloaded using LOAD REPLACE to clean up the deleted rows and index entries in the
partition.
PXA0119
NEW LIMITKEY REQUIRED PARTITION
Reason:
The utility has determined a new limit key is required for the partition based on the
selection criteria. If the user has specified MODIFY-PLQ-LIMIT-KEY(YES), the limit key for
the partition is automatically updated in the PLQ data set.
PXA0120
YOU NEED TO UNLOAD ALL THE ROWS IN PARTITION nnn BEFORE RUNNING THE JOB
TO MODIFY THE DB2 CATALOG
Reason:
This informational message informs the user to make sure to unload all the data in a
specific partition before modifying the DB2 catalog.
682 Message Reference Guide (PS to ZLB)
PXA Messages
PXA0121
xxxxxxxxx TOTAL NUMBER OF VALID RIDS IDEAL FOR PART pppp
Reason:
This message reports the ideal number of rids (data rows) for the specified part to meet
the users specifications.
PXA0122
xxxxxxxxx TOTAL NUMBER OF VALID RIDS CHOSEN FOR PART pppp
Reason:
The message reports the chosen number of rids (data rows) for the specified part to
meet the users specifications. The chosen number of rids normally will not match the
ideal number of rids. Items such as duplicate keys may cause variances. The
specifications of row range, total row percentage, and partial key length will also
contribute to variances.
PXA0123
ERROR - CORRECT TOTAL ROW
PERCENTAGE VALUES SPECIFIED
Reason:
The total row percentage value was over 100%, or 100% of the rids were allocated but
partitions were still remaining, or all the partitions were processed but not 100% of the
rids were assigned.
Chapter 3: PUT to QRFM 683
PXA Messages
PXA0124
ERROR - ROW RANGE, NEW PARTITION VALUE, AND PERCENT VALUE ARE
INCOMPATIBLE
Reason:
While trying to process the summary records, (P88), the utility encountered a problem.
The major cause may be the row range value is too large to be able to satisfy the
request. As a rule of thumb the row range should specify a row range of 10% of the total
number of rows. If the number of partitions or the total row percentage cause some
partitions to have less than 10% of the rows, the row range must be lowered.
The utility cannot complete the requested repartitioning because of the values specified
for the parameters specified.
Action:
Possible solutions include selecting a row range equal to or smaller than the percentage
value whether specified or defaulted. For example having a table of 100000 rows going
into 100 partitions would require a row range value of 10000 or less. If a percent size of
.5 was specified for a partition, a row range of 500 might be required.
PXA0126
THE LIMIT KEYS IN THE PLQ dataset FOR THIS PARTITON ANALYSIS WERE UPDATED
Reason:
The selection criteria specified to MODIFY-PLQ-LIMIT-KEY(YES) and the utility has
updated the PLQ limit key for this partition.
PXA0127
THE LIMIT KEYS IN THE PLQ dataset FOR THIS PARTITON ANALYSIS WERE NOT
UPDATED
Reason:
The user did not specify selection criteria to update the PLQ limit key.
PXA0128
TOTAL NUMBER OF DUPLICATE INDEX KEYS
Reason:
Indicates the number of duplicate index keys, or partial keys discovered.
684 Message Reference Guide (PS to ZLB)
PXA Messages
PXA0129
TBLP-KEY=
*** KEY CAUSING EXCEPTION OR RANGE
Reason:
The table part key value displays for the range or exceptional condition just triggered.
Normally, this message is issued because the TABLE-ROW-RANGE value has been
reached.
PXA0130
INDP-KEY= *** KEY CAUSING EXCEPTION OR RANGE
Reason:
The index part key value, displays for the range or exceptional condition just triggered.
Normally, this message is issued because the TABLE-ROW-RANGE value has been
reached.
PXA0135
SPECIFICATIONS DO NOT ALLOW ROWS TO BE REMOVED OFF THE FRONT
Reason:
During the automatic smoothing process, the utility determined it could not move rows
off the front of the partition. Common causes of the problem are as follows:
■
not running JOB 21 for all partitions in the tablespace.
■
running JOB 21 with a too large value for the TABLE-ROW-RANGE.
■
moving rows in multiple partitions in conflicting directions.
■
specifying PROHIBIT -ROW-ADDITIONS YES for critical partitions at the beginning of
the tablespace.
PXA0136
SPECIFICATIONS DO NOT ALLOW ROWS TO BE REMOVED OFF THE BACK
Reason:
During the automatic smoothing process, the utility determined it could not move rows
off the back of the partition. Common causes of the problem are as follows:
■
not running JOB 21 for all partitions in the tablespace.
■
running JOB 21 with a too large value for the TABLE-ROW-RANGE.
Chapter 3: PUT to QRFM 685
PXA Messages
■
moving rows in multiple partitions in conflicting directions.
■
specifying PROHIBIT -ROW-ADDITIONS YES for critical partitions at the end of the
tablespace.
PXA0137
PLEASE REVIEW THE UTILITY UNLOAD AND LOAD GUIDELINES IN THE PPX
DOCUMENTATION BEFORE PROCEEDING
Reason:
Automatic smoothing output many indicate to change the limit keys for one or many
partitions. You should review the recommendations and then unload and reload the
involved partitions. It is possible for a partition to loose and gain rows. Partitions loosing
rows need to be reloaded first, followed by partitions loosing and gaining row in the
order of row movement, followed by partitions gaining rows.
PXA0139
DISTIBUTION REPORT TRIGGERED BY SPECIFIED EVENT
Reason:
A distribution report follows the message. The most common event is the last key found
for a partition and the user selected DISTRIBUTION-REPORT LAST.
PXA0140
KEY - VALID RIDS
Reason:
For one key, within the key range, the maximum number of valid rids found.
PXA0141
KEY - TOTAL RIDS
Reason:
For one key, within the key range, the maximum number of rids found.
PXA0142
KEY - PSEUDO DELETED RIDS
Reason:
For one key, within the key range, the maximum number of pseudo deleted rids found.
686 Message Reference Guide (PS to ZLB)
PXA Messages
PXA0143
KEY - UNCOMMITTED RIDS
Reason:
For one key, within the key range, the maximum number of uncommitted rids found.
PXA0144
KEY - NUMBER OF RID CHAINS
Reason:
For one key, within the key range, the maximum number of rid chains found.
PXA0145
ROW RANGE RECORD
Reason:
Indicates a range summary record follows because a row range boundary was crossed.
PXA0146
INDEX RANGE RECORD
Reason:
Indicates a range summary record follows because an index range boundary was
crossed.
PXA0147
LAST KEY FOUND
Reason:
Indicates a range summary record follows because the last index key was found and
processed.
PXA0148
DISTIBUTION REPORT TRIGGERED BY INDEX VALUE
Reason:
The distribution report which follows was triggered by and index value.
Chapter 3: PUT to QRFM 687
PXA Messages
PXA0149
DISTIBUTION REPORT TRIGGERED BY TABLE ROW VALUE
Reason:
The distribution report which follows was triggered by and table row value.
PXA0150
FRONT HIT INDEX
Reason:
Indicates a range summary follows because an index count was reached.
PXA0151
FRONT HIT ROW
Reason:
Indicates a range summary follows because a table row count was reached.
PXA0152
BACK HIT INDEX
Reason:
Indicates a range summary follows because an index count was reached.
PXA0153
BACK HIT ROW
Indicates a range summary follows because a table row count was reached.
PXA0155
CONSIDER REORGANIZING THE INDEX FOR PARTITION part
Reason:
The utility has determined the partitioning index clustering ratio is not optimal.
If index entries are inserted frequently, or the index is used for some degree of
sequential processing, or major plans have non-matching index scans, reorganizing the
index will improve performance.
688 Message Reference Guide (PS to ZLB)
PXA Messages
PXA0156
CONSIDER REORGANIZING THE TABLE FOR PARTITION part
Reason:
The utility has determined the partition data clustering ratio compared to the
partitioning index is not optimal.
If the table is accessed for some degree of sequential processing, reorganizing the
tablespace partition will improve performance.
PXA0157
CONSIDER REPARTITIONING BECAUSE OF PARTITION part
The utility has determined the indicated partition needs to be repartitioned based on
the user specified selection criteria.
PXA0160
DISTRIBUTION OF FREE SPACE ON EACH LEAF SUBPAGE
Reason:
The bucket value indicates the value of free space which is equal to or less than the
actual value. The occurrences indicate the number of pages which satisfy the first
occurrence of the bucket the count is associated.
PXA0161
DISTRIBUTION OF PAGE DISTANCE BETWEEN LEAF PAGES
Reason:
The bucket value indicates the value of page difference between leaf pages which is
equal to or less than the actual value. The occurrences indicate the number of pages
which satisfy the first occurrence of the bucket the count is associated.
PXA0162
DISTRIBUTION OF PAGE DISTANCE BETWEEN ROW RIDS
Reason:
The bucket value indicates the value of page difference between consecutive data rows
which is equal to or less than the actual value. The occurrences indicate the number of
pages which satisfy the first occurrence of the bucket the count is associated.
Chapter 3: PUT to QRFM 689
PXM Messages
PXA0163
DISTRIBUTION OF NUMBER OF RIDS PER KEY
Reason:
The bucket value indicates the value of page difference between leaf pages which is
equal to or less than the actual value. The occurrences indicate the number of pages
which satisfy the first occurrence of the bucket the count is associated.
PXA0164
DISTRIBUTION OF NUMBER OF VALID RIDS PER KEY
Reason:
The bucket value indicates the value of the number of rids per index key which is equal
to or less than the actual value. The occurrences indicate the number of pages which
satisfy the first occurrence of the bucket the count is associated.
PXA0165
DISTRIBUTION OF NUMBER OF PSEUDO DELETED RIDS PER KEY
Reason:
The bucket value indicates the value of pseudo deleted rids per key which is equal to or
less than the actual value. The occurrences indicate the number of pages which satisfy
the first occurrence of the bucket the count is associated.
PXA0166
BUCKET OCCURRENCES
Reason:
The bucket value indicates the value of the category being reported (see messages
PXA0160-PXA0165). The occurrences indicate the number of pages which satisfy the
first occurrence of the bucket the count is associated.
PXM Messages
Messages with the PXM prefix are generated from Xmanager.
690 Message Reference Guide (PS to ZLB)
PXM Messages
PXM0100
XMANAGER Rrr.rr INIT IN PROGRESS XMID=id.
Reason:
Xmanager initialization is in progress. The message text provides the Xmanager release
in the message text. The XMID is the XMANID of the Xmanager started procedure. If the
XMANID on the started procedure is set to 0000, this message will specify the version
number of the release.
This message is informational only.
PXM0101
XMANAGER Rrr.rr INITIALIZATION COMPLETE XMID=id.
Reason:
Xmanager initialization has been successfully completed. Once you have received this
message, Xmanager is available to process requests from the requester address spaces.
This message is informational only.
PXM0102
CA/XMANAGER IS ALREADY ACTIVE XMID=id.
Reason:
You attempted to start a session of Xmanager, but Xmanager is already active on this
system. Only a single Xmanager address space per release of Xmanager is allowed per
MVS system. The Xmanager start request is aborted.
This message is informational only.
PXM0103
CA/XMANAGER STOP IN PROGRESS XMID=id.
Reason:
Termination processing for Xmanager has begun as the result of an Xmanager stop
request (P PTXMAN or STOP PTXMAN). The Xmanager address space is in the process of
terminating.
This message is informational only.
Chapter 3: PUT to QRFM 691
PXM Messages
PXM0104
XMANAGER TERMINATION CLEANUP COMPLETE XMID=id.
Reason:
Necessary termination cleanup efforts have been performed successfully by Xmanager
termination processing. The Xmanager address space has terminated.
This message is informational only.
PXM0105
CA/XMANAGER MODIFY IN PROGRESS XMID=id.
Reason:
Xmanager has received an MVS command using the MVS MODIFY command. Xmanager
acknowledges the receipt of the MODIFY command. MODIFY-related processing is in
progress.
This message is informational only.
PXM0106
MODIFY UNSUCCESSFUL, MODIFY TEXT IS INVALID.
Reason:
An MVS MODIFY command has been sent to the Xmanager address space, but the
command was invalid. As a result, MODIFY processing for the command is terminated.
Action:
Correct the command text and reissue the MVS MODIFY command.
PXM0107
MODIFY TEXT = modify command text.
Reason:
This message displays the contents of a MODIFY command received by Xmanager. It lets
you review Xmanager MODIFY text in case errors are encountered during MODIFY
command processing.
This message is informational only.
692 Message Reference Guide (PS to ZLB)
PXM Messages
PXM0108
FOLLOWING DB2 SUBSYSTEMS WERE LOCATED.
Reason:
Xmanager has received an F PTXMAN,LISTDB2 modify command request. This is the
initial message sent to the MVS SYSLOG as a result of the modify request.
This message is informational only.
PXM0109
XMANAGER MODIFY PROCESSING COMPLETE.
Reason:
Xmanager has completed processing all modify requests. Xmanager modify processing
has terminated because there are no outstanding modify requests.
This message is informational only.
PXM0110
DB2 SSID=ssid STAT=ssssssss CMD=cccccccc V=vvv DSPG=gggggggg GATT=aaaa.
Reason:
This message is issued for each DB2 subsystem located on the MVS system as a result of
an Xmanager, MVS modify, LISTDB2 command. Each message describes a single DB2
subsystem located on the MVS system. Message variables include the DB2 subsystem
identifier, and the DB2 subsystem status (active, inactive, and so on), DB2 subsystem
recognition character, DB2 version if the DB2 SSID is active, and the member and group
attach names if the DB2 subsystem is a member of a data sharing group.
Action:
None.
PXM0111
XMANAGER DISPLAY WORKLOAD IN PROGRESS.
Reason:
An Xmanager DISPLAY modify command is being processed.
Action:
None. This message is followed by additional messages that describe the existing
workload currently active in the Xmanager address space.
Chapter 3: PUT to QRFM 693
PXM Messages
PXM0112
XMANAGER CURRENTLY HAS NO WORKLOAD.
Reason:
Xmanager has received an Xmanager DISPLAY modify request. However, no active
collections are currently active in the Xmanager address space.
Action:
None.
PXM0113
DETECTOR IS ACTIVE FOR DB2=ssid.
Reason:
As a result of an Xmanager DISPLAY modify request, this message indicates that
collection is active for the DB2 subsystem identified in the message text.
Action:
None.
PXM0114
XMANAGER TERMINATED, MVS/ESA REQUIRED.
Reason:
An attempt was made to start Xmanager on an MVS system that is not running
MVS/ESA. Xmanager requires MVS/SP 3.1 or higher. Xmanager does not support
pre-MVS/SP 3.1 versions.
Action:
None.
PXM0115
XMANAGER TERMINATED, NOT APF AUTHORIZED.
Reason:
Xmanager requires APF authorization. All data sets specified on the Xmanager STEPLIB
DDNAME must be APF authorized.
APF authorize the necessary data sets and restart Xmanager.
694 Message Reference Guide (PS to ZLB)
PXM Messages
PXM0116
MVS CANCEL COMMAND HAS BEEN DETECTED XMID=id.
Reason:
An MVS CANCEL command has been issued for the Xmanager address space. As a result,
termination of the Xmanager address space is in progress.
This message is informational only.
PXM0117
XMANAGER TERMINATION COMPLETE XMID=id.
Reason:
The Xmanager address space has terminated. Control returns to MVS as a result of
termination processing.
This message is informational only.
PXM0118
XMANAGER pppppppp PARM IS INVALID/XMANAGER TERMINATED.
Reason:
An invalid parameter or value was passed in the PARM= operand when Xmanager was
started. See the product documentation, which details the Xmanager execution
parameters and their allowable values.
Action:
Correct the Xmanager execution parameters and restart Xmanager.
PXM0119
SEND MESSAGE ERROR/MESSAGE PID=pid MID=mid NOT LOCATED.
Reason:
This message is issued due to Xmanager send message request being driven for a
message ID, which was not located.
Chapter 3: PUT to QRFM 695
PXM Messages
PXM0121
XMANAGER AUTHID = authid.
Reason:
This message is returned by Xmanager as a result of processing a LISTAUTH modify
command. Output returned displays the MVS authorization identifier, which is in use by
the Xmanager address space.
This message is informational only.
PXM0122
XMANAGER AUTHID IS NULL.
Reason:
This message is returned by Xmanager as a result of processing a LISTAUTH modify
command. Output returned indicates there is currently no MVS authorization identifier
in use by the Xmanager address space.
This message is informational only.
PXM0123
TMANAGER IS ACTIVE FOR DB2=ssid.
Reason:
Xmanager has received a DISPLAY modify command. The Trace Manager (TMANAGER)
component is currently active for the selected DB2 subsystem identified in the message
text.
This message is informational only.
PXM0124
XMANAGER SDUMP HAS BEEN ISSUED.
Reason:
Indicates the Xmanager address space has requested a SVC dump. Evaluate why the
dump was generated.
696 Message Reference Guide (PS to ZLB)
PXM Messages
PXM0125
XMANAGER SDUMP CAPTURE COMPLETE.
Reason:
Indicates the Xmanager address space has completed the capture of a requested a SVC
dump. Evaluate why the dump was generated.
PXM0126
SSANALZE IS ACTIVE FOR DB2=ssid.
Reason:
As a result of an Xmanager DISPLAY modify request, this message indicates that
Subsystem Analyzer collection is active for the DB2 subsystem identified in the message
text.
This message is informational only.
PXM0127
DB2 AGENT IS ACTIVE FOR DB2=ssid
Reason:
As a result of an Xmanager DISPLAY modify request, this message indicates that the DB2
agent collection is active for the DB2 subsystem identified in the message text.
Action:
None.
PXM0128
CA-INSIGHT IS ACTIVE FOR DB2=ssid
Reason:
As a result of an Xmanager DISPLAY modify request, this message indicates that the
CA-Insight collection is active for the DB2 subsystem identified in the message text.
This message is informational only.
Chapter 3: PUT to QRFM 697
PXM Messages
PXM0133
TMANAGE2 IS ACTIVE FOR DB2 = ssid.
Reason:
Xmanager has received a DISPLAY modify command. The Pending Trace Manager
(TMANAGER2) component is currently active for the DB2 subsystem identified in the
message text.
This message is informational only.
PXM0200
XMANAGER DETECTED TERM IN PROGRESS DB2=ssid.
Reason:
Xmanager has detected DB2 termination in progress for a selected DB2 subsystem.
Xmanager tracks the startup and termination of all DB2 subsystems located on the MVS
system.
This message is informational only. It does not indicate any actions being performed by
Xmanager as a result of DB2 subsystem termination.
PXM0201
XMANAGER DETECTED TERM COMPLETE DB2=ssid.
Reason:
Xmanager has detected DB2 termination completion for a selected DB2 subsystem.
Xmanager tracks the startup and termination of all DB2 subsystems located on the MVS
system.
This message is informational only. It does not indicate any actions being performed by
Xmanager as a result of DB2 subsystem termination.
PXM0202
XMANAGER DETECTED INIT IN PROGRESS FOR DB2=ssid.
Reason:
Xmanager has detected DB2 startup in progress for a selected DB2 subsystem.
Xmanager tracks the startup and termination of all DB2 subsystems located on the MVS
system.
This message is informational only. It does not indicate any actions being performed by
Xmanager as a result of DB2 subsystem startup.
698 Message Reference Guide (PS to ZLB)
PXM Messages
PXM0203
XMANAGER DETECTED INIT COMPLETE DB2=ssid.
Reason:
Collection initialization completed successfully for selected DB2 subsystem. Collection
executes within the Xmanager address space. The message text includes the DB2
subsystem identifier for which the collector is being started.
This message is informational and is written to the Xmanager job log as well as to the
MVS SYSLOG. None.
PXM0314
TASK TERMINATION TIME LIMIT WAS EXCEEDED
Reason:
XMANAGER has terminated a task prior to its completion because the task termination
time limit has expired. If the terminated task was a collection task, the data from the
last collection interval may not have been stored.
Action:
Use the TERMWAIT XMANAGER start-up parameter to increase the time allowed for the
sub-task to terminate. The default value for TERMWAIT is TERMWAIT(1), or 1 minute.
PXM0315
RACROUTE VERIFY FAILED SAFRC=safrc RC=returncode RS=reasoncode
USER=userid PLAN=planname
Reason:
A RACROUTE TYPE=VERIFY macro issued during DB2 plan authorization validation failed
for the indicated userid and product plan.
When SAFRC=0008 and RC=001C then the validation failed because the user access was
revoked by the security system. The meaning of other Return and Reason Codes can be
found in the SecureWay Security Server External Security Interface (RACROUTE) Macro
Reference.
If the message is issued for an unauthorized user then no action is required.
Chapter 3: PUT to QRFM 699
PXM Messages
PXM0320
RUN MODIFY FAILED/MEMBER NAME INVALID.
Reason:
The RUN modify command request has failed due to the member name specified on the
RUN command being invalid.
Action:
Correct the member name and reissue the request.
PXM0321
RUN MODIFY FAILED/MEMBER NOT FOUND IN PARMLIB.
Reason:
The RUN modify command has failed due to the member name specified in the
command text not being located in the Xmanager CDBAPXMP data set.
Action:
Correct the error and reissue the modify request.
PXM0322
RUN MODIFY FAILED, VALID COMMAND NOT FOUND IN pxmparm member.
Reason:
The RUN modify command has failed due to the member name being empty in the
Xmanager CDBAPXMP data set.
Action:
Correct the member contents and reissue the modify command.
PXM0323
RUN MODIFY PROCESSING COMPLETE.
Reason:
The RUN modify command has completed processing.
This message is informational and indicates RUN modify command processing is being
exited.
700 Message Reference Guide (PS to ZLB)
PXM Messages
PXM0324
XMANAGER pxmparm member AUTOCMD PROCESSING IN PROGRESS.
Reason:
Indicates that Xmanager is in the process of automatically issuing the commands in the
member of the Xmanager parmlib specified by the INIT execution parameter. This is
done whenever Xmanager is started.
Action:
None.
PXM0325
XMANAGER pxmparm member AUTOCMD PROCESSING COMPLETE.
Reason:
Indicates that Xmanager has completed processing the commands in the member of the
Xmanager parmlib specified by the INIT execution parameter. These commands are
automatically issued whenever Xmanager is started.
Action:
None.
PXM0326
XMANAGER pxmparm member AUTOCMD MEMBER NOT FOUND.
Reason:
The member of the Xmanager parmlib specified by the INIT execution parameter does
not exist. Xmanager auto command processing is bypassed. This message is suppressed
for the default auto command member XMANINIT.
Action:
Specify the correct auto command member name for the INIT execution parameter.
Chapter 3: PUT to QRFM 701
PXM Messages
PXM0327
COMMAND ________________________... IS TOO LONGCOMMAND NOT PROCESSED
Reason:
Indicates a request to execute the command in the text was invalid because the
command string was too long. The first 24 characters in the command string are
included in the message.
Action:
Shorten the command string by putting multiple parameters on a control card line.
PXM0370
CA/XMANAGER SHUTDOWN IN PROGRESS XMID=id.
Reason:
Xmanager termination is in progress. XMID is the XMANID of the Xmanager started
procedure. If the XMANID on the started procedure is set to 0000 this message will
specify the version number of the release.
Action:
None.
PXM0371
XMANAGER REGION IN USE CLOSE TO REGION LIMIT FOR region
Reason:
The Xmanager is going to be shut down because almost all of the private storage that
was allocated for the Xmanager task has been consumed. The region values that may
appear are LPVT, which stands for low private, and EPVT, which stands for extended
private.
Action:
Specify a larger REGION size in the Xmanager JCL.
702 Message Reference Guide (PS to ZLB)
PXM Messages
PXM0372
XMANAGER REGION IN USE HAS REACHED SHORTAGE THRESHOLD FOR type
Reason:
The Xmanager has encountered a storage shortage for the specified type of memory.
Action:
Contact your system administrator.
For type 'EPVT' increase the value specified on the REGION parameter on the EXEC
statement of the Xmanager task or reduce the Xmanager CUSHION parameter high
value.
For type 'MOBJ' increase the value specified on the MEMLIMIT parameter on the EXEC
statement of the Xmanager task or reduce the Xmanager CUSH64 parameter high value.
Note: For the MEMLIMIT and REGION parameters, see the MVS JCL Reference. For the
CUSHION and CUSH46 parameters, see the General Facilities Reference Guide.
PXM0373
XMANAGER REGION type STORAGE SHORTAGE RELIEVED
Reason:
A private storage shortage in the XMANAGER has been relieved for the specified type of
memory. This message indicates that an earlier shortage identified by a PXM0372
message has ended.
Action:
None.
PXM0400
XMANAGER PRODINIT PROCESSING ENTERED.
Reason:
This message is issued during normal startup processing of Xmanager. It indicates
product initialization processing is being entered.
Action:
None.
Chapter 3: PUT to QRFM 703
PXM Messages
PXM0401
XMANAGER PRODINIT PROCESSING ENDED.
Reason:
This message is issued during normal startup processing of Xmanager. It indicates
product initialization processing is being exited.
Action:
None.
PXM0402
XMANAGER PRODINIT COMPLETE FOR PID=pid.
Reason:
This message informs that Xmanager has entered product initialization processing for
the specified product identifier.
Action:
None.
PXM0403
XMANAGER PRODINIT FAILED PID=pid LMOD=lmod.
Reason:
Indicates Xmanager product initialization has failed for the specified product identifier
and load module.
PXM0404
XMANAGER PRODINIT PTILIB OPEN HAS FAILED.
Reason:
Message is issued due to inability to OPEN the Xmanager PTILIB data set during
Xmanager product initialization processing.
Action:
Determine if MVS authorization failure messages have also been issued in relation to
the error.
704 Message Reference Guide (PS to ZLB)
PXM Messages
PXM0405
XMANAGER PRODINIT FAILED/PXMPVTCC NOT LOCATED.
Reason:
Xmanager product initialization processing has failed.
PXM0406
XMANAGER PRODINIT FAILED/BLDL ERROR.
Reason:
Xmanager product initialization processing has failed.
PXM0410
XMANAGER MSLOGGER INIT ENTERED XMID=id.
Reason:
This message informs that Xmanager has entered message log task initialization
processing for the specified Xmanager identifier.
Action:
None.
PXM0411
XMANAGER MSLOGGER INIT COMPLETE XMID=id.
Reason:
This message informs that Xmanager has completed message log task initialization
processing for the specified Xmanager identifier.
Action:
None.
Chapter 3: PUT to QRFM 705
PXM Messages
PXM0412
XMANAGER MSLOGGER TERM IN PROGRESS FOR XMID=id.
Reason:
This message informs that Xmanager has entered message log task termination
processing for the specified Xmanager identifier.
Action:
None.
PXM0413
XMANAGER MSLOGGER TERM COMPLETE XMID=id.
Reason:
This message informs that Xmanager has completed message log task termination
processing for the specified Xmanager identifier.
Action:
None.
PXM0414
ddname DDNAME NOT FOUND, MSLOGGER UNAVAILABLE.
Reason:
This message informs that Xmanager message log task initialization failed because the
message log DD statement was not present in the Xmanager JCL procedure.
Action:
Add the DD statement to the Xmanager JCL procedure and restart the Xmanager.
PXM0501
CROUTER REQUEST FAILED / REQUEST ID INVALID.
Reason:
An Xmanager asynchronous request has failed due to invalid request identifier being
received.
706 Message Reference Guide (PS to ZLB)
PXM Messages
PXM0502
PARMLIB READ ERROR/BLDL HAS FAILED.
Reason:
Xmanager has been requested to read a member from the Xmanager parmlib (can be a
read as part of an update request). The parmlib processing failed due to an error while
issuing a BLDL macro. This is not a member not found error, since this condition is
handled by the parmlib processor.
Action:
Check the parmlib settings.
PXM0503
PARMLIB READ ERROR/FIND HAS FAILED.
Reason:
Xmanager has been requested to read a member from the Xmanager parmlib (can be a
read as part of an update request). The parmlib processing failed due to an error while
issuing a FIND macro. This should not be a member not found error, since this condition
is handled by the parmlib processor during the BLDL step.
Action:
Check the parmlib settings.
PXM0504
PARMLIB READ ERROR/BLOCK DESC EXTEND FAILED.
Reason:
Xmanager has been requested to read a member from the Xmanager parmlib (can be a
read as part of an update request). The parmlib processing function which tracks data
blocks in the parmlib member encountered an error.
Action:
This is most likely a software problem. It is possible to avoid this problem by reblocking
the parmlib using a larger block size to reduce the number of blocks. Note that the
Xmanager started task must be shut down and restarted to accomplish this.
Chapter 3: PUT to QRFM 707
PXM Messages
PXM0505
PARMLIB READ ERROR/BLOCK LENGTH OF ZERO.
Reason:
Xmanager has been requested to read a member from the Xmanager parmlib (can be a
read as part of an update request). The parmlib processing failed due to an error while
issuing a READ macro. A block was found with a record length of zero.
Action:
Fix the problem and retry.
PXM0510
PARMLIB WRITE ERROR/OPEN FAILED.
Reason:
Xmanager has been requested to write a member to the Xmanager parmlib as part of an
add or update request.
The parmlib processing failed due to an error while issuing an OPEN macro. This WTO
may be preceded by MVS abend messages, which indicates the specific open error.
PXM0511
PARMLIB WRITE ERROR/STOW FAILED.
Reason:
An error was incurred by Xmanager while attempting a STOW request to the CDBAPXMP
data set.
PXM0520
PARMLIB DELETE ERROR/OPEN FAILED.
Reason:
An error was incurred by Xmanager while attempting to OPEN the CDBAPXMP data set.
Action:
Verify that Xmanager has read/write access to the CDBAPXMP data set.
708 Message Reference Guide (PS to ZLB)
PXM Messages
PXM0521
PARMLIB DELETE ERROR/FIND FAILED.
Reason:
An error was incurred by Xmanager while attempting to delete a CDBAPXMP data set
member.
PXM0522
PARMLIB DELETE ERROR/STOW FAILED.
Reason:
An error was incurred by Xmanager while attempting to delete a CDBAPXMP data set
member.
PXM0600
XMAN CONNECT HAS NOT BEEN ESTABLISHED.
Reason:
This message is issued as a result of a product request which has failed due preceding
error incurred during Xmanager connect logic.
PXM0601
PXMDBM TERMINATING / MAX RETRYS REACHED.
Reason:
A critical component of the Xmanager address space has terminated abnormally.
Termination is in progress because numerous recoverable abends have occurred.
PXM0602
PXMZGV TERMINATING / MAX RETRYS REACHED.
Reason:
A critical component of the Xmanager address space has terminated abnormally.
Termination is in progress because numerous recoverable abends have occurred.
Chapter 3: PUT to QRFM 709
PXM Messages
PXM0602
PXMZGV TERMINATING / MAX RETRYS REACHED.
Reason:
A critical component of the Xmanager address space has terminated abnormally.
Termination is in progress because numerous recoverable abends have occurred.
PXM0605
XMANAGER EXITCNTL ENTERED EXID=exid.
Reason:
This message is issued when Xmanager is started. It indicated Xmanager product exit
processing has been entered for the related exit identifier.
Action:
None.
PXM0606
XMANAGER EXITCNTL COMPLETE XMID=id.
Reason:
This message is issued when Xmanager is started. It indicates Xmanager product exit
processing has been completed for all product exits existing at the specified Xmanager
identifier.
Action:
None.
PXM0607
XMANAGER EXITCNTL EXID=exid ENTERED PID=pid.
Reason:
Indicates Xmanager is passing control to a product exit. The message is issued when
Xmanager is started. Message text includes the exit identifier as well as the product
identifier for which the exit is being driven.
Action:
None.
710 Message Reference Guide (PS to ZLB)
PXM Messages
PXM0608
XMANAGER EXITCNTL EXID=exid COMPLETE PID=pid.
Reason:
Indicates Xmanager has completed the product exit. The message is issued when
Xmanager is started. Message text includes the exit identifier as well as the product
identifier for which the exit is being driven.
Action:
None. This message is informational only and issued as a result of normal Xmanager
startup processing.
PXM0609
XMANAGER EXITCNTL RECOVERY RETRY SUCCESSFUL.
Reason:
Indicates a failure has occurred during Xmanager initialization within product exit
processing.
PXM0610
XMANAGER EXITCNTL PTILIB ACCESS HAS FAILED.
Reason:
A failure occurred during Xmanager initialization while attempting to read the Xmanager
PTILIB ddname data set(s). Xmanager requires MVS READ access to the PTILIB data sets.
PXM0611
XMANAGER EXITCNTL PTILIB OPEN HAS FAILED.
Reason:
A failure occurred during Xmanager initialization while attempting to OPEN the
Xmanager PTILIB ddname data set(s). Xmanager requires MVS READ access to the PTILIB
data sets.
PXM0612
XMANAGER EXITCNTL ABEND RECURSION DETECTED.
Reason:
This message is issued as a result of Xmanager initialization failing while within product
exit related processing.
Chapter 3: PUT to QRFM 711
PXM Messages
PXM0613
XMANAGER EXITCNTL ABEND PERCOLATION INCURRED.
Reason:
This message is issued as a result of Xmanager initialization failing while within product
exit related processing.
PXM0614
XMANAGER EXITCNTL RECOVERY RETRY DRIVEN.
Reason:
This message is issued as a result of Xmanager initialization failing while within product
exit related processing.
PXM0800
ABEND INCURRED/RETRY IN PROGRESS.
Reason:
Indicates an Xmanager product related request has resulted in an abend being incurred.
Other product related messages may have been issued in relation to the failure.
Action:
Locate all messages issued.
PXM0801
ABEND INCURRED/RETRY SUCCESSFUL.
Reason:
Indicates an Xmanager product related request has resulted in an abend; recovery
termination processing has successfully retried the error incurred. Other product related
messages may have been issued in relation to the failure.
Action:
Locate all messages issued.
712 Message Reference Guide (PS to ZLB)
PXM Messages
PXM0802
RETRY RECURSION DETECTED/TERMINATION FORCED.
Reason:
Indicates an Xmanager product related request has resulted in an abend. While the
abend was being retried abend recursion was detected. This resulted in the error being
percolated. Other product related messages may have been issued in relation to the
failure.
Action:
Locate all messages issued.
PXM0803
MAX ABENDS REACHED/RETRY PROCESSING BYPASSED.
Indicates an Xmanager product related request has resulted in an abend. While the
abend was being processed it was determined that several previous abends have
occurred. As a result of an internal abend limit being reached recovery retry processing
was aborted and the error was percolated. Other product related messages may have
been issued in relation to the failure.
Action:
Locate all messages issued.
PXM0810
CA/XMANAGER RECOVERY IN PROGRESS.
Reason:
The Xmanager recovery manager has intercepted a program abend in the Xmanager
started procedure.
PXM0811
PSW: abend-psw LMOD: module-name OFFSET: module-offset ABEND: abend-code.
Reason:
This message follows message PXM0810 and provides additional information about the
intercepted program abend.
Chapter 3: PUT to QRFM 713
PXM Messages
PXM0812
GPRS nn-nn
rrrrrrrr rrrrrrrr rrrrrrrr rrrrrrrr.
Reason:
This message follows message PXM0810 and provides additional information about the
intercepted program abend.
PXM0813
CA/XMANAGER Rvv.vv DUMP LOC: module+offset ABEND: abend-code PSW:
abend-psw.
Reason:
The Xmanager recovery manager has taken a diagnostic dump as a result of intercepting
a program abend in the Xmanager started procedure. The message provides
information about the intercepted program abend.
PXM0814
SVCDUMP INVOKED RC=returncode RSN=reasoncode.
Reason:
This message follows message PXM0813 and provides additional information about the
diagnostic dump.
PXM4400
XMANAGER PLEXCNTL INIT SYSPLEX=sysplex MVS=mvs XMID=id.
Reason:
This message informs that Xmanager has started sysplex communication task
initialization for the specified Xmanager identifier.
Action:
None.
714 Message Reference Guide (PS to ZLB)
PXM Messages
PXM4401
XMANAGER PLEXCNTL INIT COMPLETE XMID=id.
Reason:
This message informs that Xmanager has completed sysplex communication task
initialization for the specified Xmanager identifier.
Action:
None.
PXM4402
XMANAGER ALREADY ACTIVE SYSPLEX=sysplex MVS=mvs.
Reason:
This message informs that Xmanager sysplex communication task has initialization has
terminated because of a duplicate Xmanager identifier.
Action:
Give each Xmanager on the same MVS system a unique value for the XMANID
parameter and restart the Xmanager.
PXM4403
XMANAGER PLEXCNTL TERM IN PROGRESS XMID=id.
Reason:
This message informs that Xmanager has started sysplex communication task
termination for the specified Xmanager identifier.
Action:
None.
PXM4404
XMANAGER PLEXCNTL TERM COMPLETE XMID=id.
Reason:
This message informs that Xmanager has completed sysplex communication task
termination for the specified Xmanager identifier.
Action:
None.
Chapter 3: PUT to QRFM 715
PXM Messages
PXM4405
XMANAGER PLEXCNTL ABEND RECURSION INCURRED.
Reason:
This message informs that the Xmanager sysplex communication task has terminated
due to an abend.
PXM4406
XMANAGER XMANPLEX IS NOT ACTIVE.
Reason:
The Xmanager sysplex communications task is not active.
Action:
Insure that the XSYS(Y) execution parameter is specified and restart the Xmanager.
PXM4500
XMANAGER SEND=send type FAILED RC=returncode RS=reason RID=requestid
SYS=mvs.
Reason:
An Xmanager sysplex communication request failed.
PXM4502
XMANAGER SEND=send type FAILED MEMBER NOT ACTIVE RID=request id SYS=mvs.
Reason:
An Xmanager sysplex communication request failed because the Xmanager was not
active on the indicated MVS system.
PXM4503
XMANAGER SEND REQUEST TIMEOUT INCURRED RID=requested.
Reason:
An Xmanager sysplex communication request failed because a response was not
received within the number of seconds specified by the Xmanager TIMEOUT parameter.
The request may succeed on retry.
Action:
If the problem persists try increasing the value of the Xmanager TIMEOUT parameter.
716 Message Reference Guide (PS to ZLB)
PXM Messages
PXM4510
MSVR1 INVALID MSGCNTL SEEN.
Reason:
An internal error occurred processing an Xmanager sysplex communication request.
PXM4511
MSVR2 INVALID MSGCNTL SEEN.
Reason:
An internal error occurred processing an Xmanager sysplex communication request.=
PXM4512
RECEIVE POST FAILED.
Reason:
An internal error occurred processing an Xmanager sysplex communication request.
PXM4513
ZMV01 INVALID MSGCNTL SEEN.
Reason:
An internal error occurred processing an Xmanager sysplex communication request.
PXM4514
NPST INVALID MSGCNTL SEEN.
Reason:
An internal error occurred processing an Xmanager sysplex communication request.
PXM4515
NOTIFY RESPONSE POST ERROR.
Reason:
An internal error occurred processing an Xmanager sysplex communication request.
Chapter 3: PUT to QRFM 717
PXM Messages
PXM4520
MSGEXIT PARMDATA FAILED.
Reason:
An internal error occurred processing an Xmanager sysplex communication request.
PXM4521
MSGEXIT MEMBER LOCATE FAILED.
Reason:
An internal error occurred processing an Xmanager sysplex communication request.
PXM4522
MSGEXIT RECEIVE REQUEST FAILED.
Reason:
An internal error occurred processing an Xmanager sysplex communication request.
PXM4523
MSGEXIT RECEIVE SEGMENT FAILED.
Reason:
An Xmanager sysplex communication request failed.
PXM4524
MSGEXIT RECEIVE RESPONSE FAILED.
Reason:
An Xmanager sysplex communication request failed.
PXM4525
MSGEXIT ALESERV ADD FAILED.
Reason:
An Xmanager sysplex communication request failed.
718 Message Reference Guide (PS to ZLB)
PXM Messages
PXM4526
MSGEXIT ALESERV DELETE FAILED.
Reason:
An Xmanager sysplex communication request failed.
PXM4527
NTFYRESP BYPASSED/REQUESTOR TERMED.
Reason:
An Xmanager sysplex communication request failed.
PXM4528
MSGEXIT INITIALIZATION IS INCOMPLETE.
Reason:
Indicates an attempt to process a cross-system message request occurred before the
message request service initialization was completed.
Action:
None.
PXM4530
WORK SERVER DISPATCH FAILED.
Reason:
An internal error occurred processing an Xmanager sysplex communication request.
PXM45304
XMANPLEX IS NOT ACTIVE ON THIS XMANAGER.
Reason:
The Xmanager sysplex communications task is not active.
Action:
Insure that the XSYS(Y) execution parameter is specified and restart the Xmanager.
Chapter 3: PUT to QRFM 719
PXM Messages
PXM45307
SYSPLEX INTERVAL PROPAGATION FAILED - RC rc.
Reason:
Propagation of the Xmanager sysplex interval to the other Xmanager group members
failed. Rc is the failure reason code.
PXM4531
WORK SERVER DETACH ENTERED.
Reason:
An Xmanager sysplex communication server task is being terminated.
Action:
None.
PXM4532
WORK SERVER DETACH COMPLETE.
Reason:
An Xmanager sysplex communication server task termination is complete.
Action:
None.
PXM4533
MONTASK DETACH ENTERED.
Reason:
The Xmanager sysplex communication server monitor task is being terminated.
Action:
None.
720 Message Reference Guide (PS to ZLB)
PXM Messages
PXM4534
MONITOR DETACH COMPLETE.
Reason:
The Xmanager sysplex communication server monitor task termination is complete.
Action:
None.
PXM4540
WSERVE MONTASK TERMINATE WORK DRIVEN.
Reason:
The Xmanager sysplex communication server monitor task terminated a work server
task.
PXM4541
WSERVE MONTASK TERMINATE FAILED.
Reason:
The Xmanager sysplex communication server monitor task failed in an attempt to
terminate a work server task.
PXM4550
WORK SERVER ABEND RETRY SUCCESS.
Reason:
An Xmanager sysplex communication server task incurred an abend.
PXM4551
REQUEST DEFINITION LOCATE FAILED.
Reason:
An internal error occurred processing an Xmanager sysplex communication request.
Chapter 3: PUT to QRFM 721
PXM Messages
PXM4552
REQUEST LOAD FAILED.
Reason:
An internal error occurred processing an Xmanager sysplex communication request.
PXM4553
WORK SERVER ABEND RETRY NOT ALLOWED.
Reason:
An Xmanager sysplex communication server task incurred an abend.
PXM4554
WORK SERVER ABEND RETRY ATTEMPTED.
Reason:
An Xmanager sysplex communication server task incurred an abend.
PXM4600
XMANAGER PLEXMSRV INIT ENTERED XMID=id.
Reason:
This message informs that Xmanager has started sysplex communication task message
server initialization for the specified Xmanager identifier.
Action:
None.
PXM4601
XMANAGER PLEXMSRV INIT COMPLETE XMID=id.
Reason:
This message informs that Xmanager has completed sysplex communication task
message server initialization for the specified Xmanager identifier.
Action:
None.
722 Message Reference Guide (PS to ZLB)
PXM Messages
PXM4602
XMANAGER PLEXMSRV TERM IN PROGRESS XMID=id.
Reason:
This message informs that Xmanager has started sysplex communication task message
server termination for the specified Xmanager identifier.
Action:
None.
PXM4603
XMANAGER PLEXMSRV TERM COMPLETE XMID=id.
Reason:
This message informs that Xmanager has completed sysplex communication task
message server termination for the specified Xmanager identifier.
Action:
None.
PXM4604
XMANAGER MSGSERV ABEND RECURSION XMID=id.
Reason:
The Xmanager sysplex communication message server task incurred an abend for the
specified Xmanager identifier.
PXM4629
SXMSRV NOTIFY RESPONSE SEND FAILED.
Reason:
An internal error occurred processing an Xmanager sysplex communication request.
Chapter 3: PUT to QRFM 723
PXM Messages
PXM4630
SXMSRV NOTIFY RESPONSE FAILED DUE TO INSUFFICIENT Storage
Reason:
Xmanager failed to complete the request due to insufficient storage of the requestor.
Action:
Increase the region size of your TSO or batch job.
PXM4700
XMANAGER PLEXCNTL CINIT COMPLETE RC=return/reason.
Reason:
This message displays the IXCCREAT Return and Reason Codes from Xmanager sysplex
communication task initialization.
Action:
None.
PXM4702
XMANAGER PLEXCNTL MEM=membername
STAT=status.
Reason:
This message is issued during Xmanager initialization. Membername is the name of an
Xmanager that is a member of the same sysplex group and status is the current member
status.
Action:
None.
724 Message Reference Guide (PS to ZLB)
PXM Messages
PXM4704
XMANAGER PLEXGRPX GRP=groupname MEM=membername.
Reason:
This message is issued when an Xmanager joins or leaves the Xmanager sysplex group.
Groupname is the name of the Xmanager sysplex group. Membername is the member
name of the Xmanager that has joined or left the group.
Action:
None.
PXM4705
XMANAGER PLEXGRPX NEW=nn OLD=nn TYPE=nn.
Reason:
This message is issued when an Xmanager joins or leaves the Xmanager sysplex group.
Action:
None.
PXM4706
XMANAGER PLEXGRPX GRPEXIT VALIDATION FAILED.
Reason:
An internal error occurred during an Xmanager sysplex group processing.
PXM4707
XMANAGER PLEXCNTL JINIT COMPLETE RC=return/reason.
Reason:
This message displays the IXCJOIN Return and Reason Codes from Xmanager sysplex
communication task initialization.
Action:
None.
Chapter 3: PUT to QRFM 725
PXM Messages
PXM4708
XMANAGER PLEXCNTL LTERM COMPLETE RC=return/reason.
Reason:
This message displays the IXCLEAVE return and reason codes from Xmanager sysplex
communication task termination.
Action:
None.
PXM4709
XMANAGER PLEXCNTL QUERY FAILED RC=return/reason.
Reason:
An attempt to determine the status of an Xmanager sysplex group member failed. This
message displays the Return and Reason Codes from the failed IXCQUERY.
PXM4710
XMANAGER PLEXCNTL=groupname MEM=membername.
Reason:
This message is issued during Xmanager sysplex communication task initialization.
Groupname is the name of the Xmanager sysplex group. Membername is the Xmanager
group member name.
Action:
None.
PXM4720
ROUTINE routine FAILED FOR DB2 ssid REASON reason.
Reason:
A cross system communication error occurred attempting to execute a request service
routine for the indicated DB2 subsystem. Reason describes the failure reason. The
requesting Xmanager issues this message.
726 Message Reference Guide (PS to ZLB)
PXM Messages
PXM4721
ROUTINE routine FAILED FOR DB2 ssid REASON reason.
Reason:
A cross system communication error occurred attempting to execute a request service
routine for the indicated DB2 subsystem. Reason describes the failure reason. The
responding Xmanager issues this message.
PXM4800
XMANAGER PLEXRSRV INIT ENTERED XMID=id.
Reason:
This message informs that Xmanager has started sysplex communication task message
receiver initialization for the specified Xmanager identifier.
Action:
None.
PXM4801
XMANAGER PLEXRSRV INIT COMPLETE XMID=id.
Reason:
This message informs that Xmanager has completed sysplex communication task
message receiver initialization for the specified Xmanager identifier.
Action:
None.
PXM4802
XMANAGER PLEXRSRV TERM IN PROGRESS XMID=id.
Reason:
This message informs that Xmanager has started sysplex communication task message
receiver termination for the specified Xmanager identifier.
Action:
None.
Chapter 3: PUT to QRFM 727
PXM Messages
PXM4803
XMANAGER PLEXRSRV TERM COMPLETE XMID=id.
Reason:
This message informs that Xmanager has completed sysplex communication task
message receiver termination for the specified Xmanager identifier.
Action:
None.
PXM4804
XMANAGER PLEXRSRV ABEND RECURSION XMID=id.
Reason:
The Xmanager sysplex communication message receiver task incurred an abend for the
specified Xmanager identifier.
PXM4805
XMANAGER REQID=requestid LMOD=loadmodule NOT FOUND.
Reason:
An internal error occurred processing an Xmanager sysplex communication request.
PXM5100
XMANAGER PLEXWSRV INIT ENTERED XMID=id.
Reason:
This message informs that an Xmanager sysplex communication server task has started
initialization for the specified Xmanager identifier.
Action:
None.
728 Message Reference Guide (PS to ZLB)
PXM Messages
PXM5101
XMANAGER PLEXWSRV INIT COMPLETE XMID=id.
Reason:
This message informs that an Xmanager sysplex communication server task has
completed initialization for the specified Xmanager identifier.
Action:
None.
PXM5102
XMANAGER PLEXWSRV/servno TERM IN PROGRESS XMID=id.
Reason:
This message informs that an Xmanager sysplex communication server task has started
termination for the specified Xmanager identifier. Servno is the service task identifier.
Action:
None.
PXM5102
XMANAGER PLEXWMON TERM IN PROGRESS XMID=id.
Reason:
This message informs that the Xmanager sysplex communication server monitor task
has started termination for the specified Xmanager identifier.
Action:
None.
PXM5103
XMANAGER PLEXWSRV/servno TERM COMPLETE XMID=id.
Reason:
This message informs that an Xmanager sysplex communication server task has
completed termination for the specified Xmanager identifier. Servno is the service task
identifier.
Action:
None.
Chapter 3: PUT to QRFM 729
PXM Messages
PXM5103
XMANAGER PLEXWMON TERM COMPLETE XMID=id.
Reason:
This message informs that the Xmanager sysplex communication server monitor task
has completed termination for the specified Xmanager identifier.
Action:
None.
PXM5104
XMANAGER PLEXWMON ABEND RECURSION XMID=id.
Reason:
The Xmanager sysplex communication server monitor task incurred an abend for the
specified Xmanager identifier.
PXM5104
XMANAGER PLEXWSRV/servno ABEND RECURSION XMID=id.
Reason:
An Xmanager sysplex communication server receiver task incurred an abend for the
specified Xmanager identifier. Servno is the service task identifier.
PXM5200
XMANAGER PLEXWMON INIT ENTERED XMID=id.
Reason:
This message informs that the Xmanager sysplex communication server monitor task
has started initialization for the specified Xmanager identifier.
Action:
None.
730 Message Reference Guide (PS to ZLB)
PXM Messages
PXM5201
XMANAGER PLEXWMON INIT COMPLETE XMID=id.
Reason:
This message informs that the Xmanager sysplex communication server monitor task
has completed initialization for the specified Xmanager identifier.
Action:
None.
PXM5300
XMANAGER XAQTABLE FAILED/RQT BLDL ERROR.
Reason:
An internal error occurred initializing the Xmanager sysplex communications
environment.
PXM5301
XMANAGER XAQTABLE PTILIB OPEN FAILED.
Reason:
Message is issued due to inability to OPEN the Xmanager PTILIB data set during
Xmanager sysplex communication initialization processing. Determine if MVS
authorization failure messages have also been issued in relation to the error.
PXM5308
SYSPLEX INTERVAL IS hh:mm.
Reason:
This message displays the current setting of the Xmanager sysplex interval following a
PLEXINTV MVS MODIFY command.
Action:
None.
Chapter 3: PUT to QRFM 731
PXM Messages
PXM5309
SYSPLEX INTERVAL SET
TO hh:mm.
Reason:
This message displays the new setting of the Xmanager sysplex interval following a
PLEXINTV MVS MODIFY command.
Action:
None.
PXM5310
SYSPLEX INTERVAL MODIFY FAILED/COMMAND TEXT INVALID.
Reason:
An PLEXINTV MVS MODIFY command has been sent to the Xmanager address space, but
the command was invalid. As a result, MODIFY processing for the command is
terminated.
Action:
Correct the command text and reissue the MVS MODIFY command.
PXM5311
SYSPLEX INTERVAL SET TO hh:mm FROM SYSTEM mvs
Reason:
This message displays the new setting of the Xmanager sysplex interval following a
PLEXINTV MVS MODIFY command.
Action:
None.
732 Message Reference Guide (PS to ZLB)
PXM Messages
PXM5313
SYSPLEX INTERVAL IS ALREADY hh:mm.
Reason:
A PLEXINTV MVS MODIFY command to set a new sysplex interval specifies the same
time value as the currently set sysplex interval.
Action:
None. The sysplex interval value is not changed.
PXM5320
CROSS SYSTEM COMMUNICATION TASK STARTED
Reason:
A START(XSYS) modify command to restart the Xmanager cross system communication
task completed successfully.
Action:
None.
PXM5321
CROSS SYSTEM COMMUNICATION TASK ATTACH FAILED, RC=rc
Reason:
A START(XSYS) modify command to restart the Xmanager cross system communication
failed with attach reason code rc.
PXM5322
CROSS SYSTEM COMMUNICATION TASK ALREADY ACTIVE
Reason:
A START(XSYS) modify command to restart the Xmanager cross system communication
task was ignored because the communication task was already active.
Action:
None.
Chapter 3: PUT to QRFM 733
QI Messages
PXM5601
PXMDBX TERMINATING / MAX RETRYS REACHED.
Reason:
A critical component of the Xmanager address space has terminated abnormally.
Termination is in progress because numerous recoverable abends have occurred.
QI Messages
Messages with the QI prefix are generated from post-installation processing.
QI012I
INFORMATION FOR DB2 SUBSYSTEM subsystem ENTERED, ENTER NEXT SUBSYSTEM.
Reason:
Information for the PIPELINE parmlib member has been entered for Dictionary ID
dictionary.
Action:
You must do one of the following:
■
Enter information for the next dictionary ID to be entered into the PIPELINE
member, placing a Y or N for the Multiple Dictionary ID's question and then press
Enter.
■
Enter N for Multiple Dictionary ID's and press Enter to go into edit on the PIPELINE
member.
■
Enter F3 (End) to go into edit on the PIPELINE member.
QI013AI
INFORMATION FOR DB2 SUBSYSTEM subsystem ENTERED.
Reason:
Information for the SECURE parmlib member has been entered for DB2 subsystem
subsystem.
734 Message Reference Guide (PS to ZLB)
QI Messages
QI013I
INFORMATION FOR DB2 SUBSYSTEM subsystem ENTERED, ENTER NEXT SUBSYSTEM.
Reason:
Information for the SECURE parmlib member has been entered for the specified DB2
subsystem.
Action:
You must now do one of the following:
■
Enter information for the next DB2 subsystem to be entered into the SECURE
member, placing a Y or N for the additional subsystems question and then press
Enter.
■
Enter N for additional subsystems and press Enter to go into edit on the SECURE
member.
■
Enter F3 (END) to go into edit on the SECURE member.
QI014E
UNABLE TO ALLOCATE highlvl..LOADLIB TO TASKLIB.
Reason:
The high-level..CDBALOAD data set (formerly high-level..LOADLIB) could not be
allocated to the TASKLIB DD.
Action:
Make sure the data set exits, and if it exits check to see if it is being held with an
exclusive lock.
QI015E
SYNTAX OF RCSADM(S) ENTRIES WAS INCORRECT, ENCRYPTION WAS BYPASSED.
Reason:
The syntax of the RCSADM(s) was incorrect and encryption has to be bypassed.
Action:
Correct an retry.
Chapter 3: PUT to QRFM 735
QI Messages
QI016I
INFORMATION FOR DB2 SUBYSTEM subsystem ENTERED, ENTER NEXT SUBSYSTEM.
Reason:
Information for the MIGRATOR parmlib member has been entered for the specified DB2
subsystem.
Action:
You must now do one of the following:
■
Enter information for the next DB2 subsystem to be entered into the MIGRATOR
member, placing a Y or N for the additional subsystems question and then press
Enter.
■
Enter N for additional subsystems and press Enter to go into edit on the MIGRATOR
member.
■
Enter F3 (END) to go into edit on the MIGRATOR member.
QI016I
INFORMATION FOR DB2 SUBYSTEM subsystem ENTERED.
Reason:
Information for the MIGRATOR parmlib member has been entered for the specified DB2
subsystem.
QI017E
RC=return-code, RCODE=reason-code message.
Reason:
Post Install was unable to successfully establish a thread to the specified DB2 subsystem
using the Call Attachment Facility (CAF). The information in the message is the
information that DB2 has returned to the CA CAF component.
QI018E
UNABLE TO ALLOCATE dataset.
Reason:
The specified data set was unable to be allocated. Make sure the data set exits. If it
exits, check to see if it is being held with an exclusive lock.
736 Message Reference Guide (PS to ZLB)
QI Messages
QI019E
UNABLE TO DEALLOCATE dataset.
Reason:
The specified data set was not able to be unallocated.
QI020E
COMPARE REPORT FILE dataset COULD NOT BE BROWSED.
Reason:
The Object Compare Report data set could not be browsed. If you have not performed
the object comparison, this data set does not exist yet.
Action:
If you have performed the comparison, check to be sure the data set exists and that it is
not being held with an exclusive lock.
QI021E
ANALYSIS OUTPUT FILE dataset COULD NOT BE EDITED.
Reason:
The Object Compare Report data set could not be edited. If you have not performed the
object comparison, this data set does not exist yet.
Action:
If you have performed the comparison, check to be sure the data set exists and that it is
not being held with an exclusive lock.
QI022I
DATASET 'highlvl..CLIST.suffix' IS NOW CUSTOMIZED.
Reason:
The customization of the command list library is now complete. The selected highlevel
has been replaced in the members that appeared as they were customized.
Chapter 3: PUT to QRFM 737
QI Messages
QI023E
DATASET 'highlvl..CLIST.suffix' DOES NOT EXIST.
Reason:
The command list library data set was not found.
Action:
Check the output from your unload job to be sure that no errors occurred on the
creation of this library.
QI023E
DATASET 'highlvl..CLIST.suffix' DOES NOT EXIST.
Reason:
The model library data set was not found.
Action:
Check the output from your unload job to be sure that no errors occurred on the
creation of this library.
QI024I
DATASET 'highlvl..MODEL.suffix' IS NOW CUSTOMIZED.
Reason:
The customization of the model library is now complete. The STEPLIB, USERLIB, DB2
libraries, CDBAPARM, and CDBAXMSG library symbols have been replaced by the names
of the permanent library data sets.
QI025I
MAKE ANY CHANGES. PF3 OR END TO SAVE. CANCEL TO EXIT WITHOUT SAVING.
Action:
If you want to make changes to the variable initialization CLIST make them now and
press F3 (End) to save.
QI026E
DATASET dataset NOT FOUND.
Reason:
The specified data set could not be found.
738 Message Reference Guide (PS to ZLB)
QI Messages
QI026I
PLEASE ENTER NEXT LIBRARY OR PF3 (END) TO QUIT.
Reason:
Enter the name of the next data set that you wish to modify.
QI028E
FILE dataset COULD NOT BE EDITED.
Reason:
The specified data set was unable to be edited.
Action:
Make sure the data set exists. If it exists, check to see if it is being held with an exclusive
lock.
QI029I
YOU ARE USING ALL THE FILES CREATED DURING THE INSTALL.
Reason:
The Post Install Cleanup step attempts to delete data sets that are not needed by the
products that you have selected. However, you have selected a mix of products where
all the libraries that have been created are needed by a product.
QI030E
START/END DATE MUST BE GREATER THAN 0100 AND LESS THAN 1232.
Reason:
The START/END date must be greater than 0100 and less than 1232 because these
entries represent month dates. They must correspond to dates that actually exist.
QI031E
START DATE MUST BE LESS THAN END DATE.
Reason:
You cannot specify an ending date that is less than the date you specified as the begin
date.
Chapter 3: PUT to QRFM 739
QI Messages
QI032E
START DAY MUST BE LESS THAN END DAY.
Reason:
You cannot specify an ending day that is less than the day you specified as the begin
day.
QI033E
START/END TIME MUST BE LESS THAN 2401.
Reason:
The START/END time must be less than 2401 because these entries represent hours and
minutes within a 24 hour day. The entry here must correspond to times that actually
exist.
QI034E
START TIME MUST BE BEFORE END TIME.
Reason:
You cannot specify an ending time that is less than the time you specified as the begin
time.
QI035E
UNABLE TO ALLOCATE dataset.
Reason:
The specified data set was unable to be allocated.
Action:
Make sure the data set exists. If it exists check to see if it is being held with an exclusive
lock.
740 Message Reference Guide (PS to ZLB)
QI Messages
QI036E
UNABLE TO OPEN dataset.
Reason:
The specified data set was unable to be opened.
Action:
Make sure the data set exists. If it exists check to see if it is being held with an exclusive
lock.
QI037E
UNABLE TO RENAME PGF LOAD MODULE.
Reason:
The PGF load module could not be renamed.
Action:
Make sure the data set exists, and if it exists check to see if it is being held with an
exclusive lock.
QI038E
UNABLE TO CLOSE dataset.
Reason:
The specified data set was unable to be closed.
Action:
Make sure the data set still exists. If it has not been deleted, make sure it is not held
with an exclusive lock.
QI039E
UNABLE TO FREE dataset.
Reason:
The specified data set was unable to be freed.
Action:
Make sure the data set still exists. If it has not been deleted, make sure it is not held
with an exclusive lock.
Chapter 3: PUT to QRFM 741
QI Messages
QI040I
THIS STEP NOT NECESSARY BASED ON PRODUCTS SELECTED FOR INSTALL.
Reason:
The step you have selected is not necessary because the products you have selected do
not require the items created by this step.
QI041I
ENTER NEXT PASSWORD/CPU ID, OR PF3 TO END.
Action:
Enter each CPU and product password that has been provided for you. After typing in
each password press Enter. When you have entered all the passwords, press F3 (END) to
exit the entry process. If you feel at some point that you have made a mistake, keep
entering passwords and you will be able to check all that you have entered before
committing the passwords to the products.
QI042I
PRF INITIALIZATION SUCCESSFUL.
Reason:
The Report Facility has been properly initialized.
QI043I
PRF INITIALIZATION NOT SUCCESSFUL.
Reason:
The Report Facility has not been properly initialized.
QI044I
THIS STEP NOT NECESSARY SINCE COMPUTER ASSOCIATES WAS NOT PREVIOUSLY
INSTALLED.
Reason:
If you have not installed a previous tape or you are not copying information from a
previous tape, this step does not need to be performed.
742 Message Reference Guide (PS to ZLB)
QI Messages
QI045E
AT LEAST ONE TABLE DEFINITION LIBRARY MUST BE ENTERED.
Reason:
At least one table definition library must be specified for the Pipeline product to
function properly.
QI046E
AT LEAST ONE MAPPING ROUTINE LIBRARY MUST BE ENTERED.
Reason:
At least one mapping routine library must be specified for the Pipeline product to
function properly.
QI047E
subsystem NOT FOUND IN PIPELINE PARMLIB MEMBER.
Reason:
The DB2 subsystem you have specified was not previously specified in the Pipeline
parmlib member.
Action:
Correct the subsystem specification or go back and add the subsystem to the Pipeline
parmlib member.
QI048E
OWNER CARD NOT FOUND IN PIPELINE PARMLIB MEMBER FOR subsystem.
Reason:
The owner card you have specified was not previously specified in the Pipeline parmlib
member.
Action:
Correct the owner card or go back and add the owner card to the Pipeline parmlib
member.
Chapter 3: PUT to QRFM 743
QI Messages
QI049I
THE OBJECT CREATION MUST BE SUBMITTED IN BATCH MODE.
Action:
You must submit the object creation job in batch to allow the DB2 authorized functions
to execute. If you have your temporary libraries APF authorized, you may run the object
creation online.
QI050I
ENTER SUBMIT TO EXECUTE THE JOB AND EXIT QI TO AVOID DSN CONTENTION.
Action:
Enter SUBMIT to execute the job. After you have submitted this job, you should exit
Post Install to avoid data set contention on the data sets that you have currently
allocated.
QI051I
RC/M MASK SET CUSTOMIZATION COMPLETED SUCCESSFULLY.
Reason:
Indicates that the mask set customization step has been completed successfully.
QI052I
RC/M @DEFAULT MASK SET ALREADY EXISTS. INSTALL HAS BEEN AVERTED.
Reason:
Indicates that the @DEFAULT mask set already exists. This part of the install does not
need to be completed.
QI053I
YOU MUST SPECIFY A CREATOR FOR THE @DEFAULT MASK SET.
Reason:
Indicates that you must enter a creator ID for the @DEFAULT Automapping Mask set.
744 Message Reference Guide (PS to ZLB)
QI Messages
QI054I
RC/M CUSTOMIZATION CONNECTION ERROR. PLEASE CHECK SUBSYSTEM AND PLAN.
Reason:
Indicates that there was a DB2 subsystem connection error during customization. Make
sure that the correct subsystem was specified in the SETUP parmlib member and the
plan was bound successfully.
QI055I
FAST UNLOAD MUST BE USED WHEN SELECTING FAST LOAD.
Reason:
Indicates that you must also select the CA Fast Unload utility when you select the CA
Fast Load utility during Model Services customization.
QI056I
YOU HAVE SPECIFIED AN INVALID CUSTOMIZATION VALUE. PLEASE REENTER.
Reason:
You have entered an invalid value for selection. Valid values are Y for yes or N for no.
QI057I
REVIEW THE DDL FOR THE PROPER CREATOR NAME. CANCEL IF INCORRECT.
Action:
Review the DDL to ensure that each set of objects have the correct owner ID, that was
specified in the PIPELINE parmlib member, for each data dictionary. Enter CANCEL if the
DDL is incorrect.
QI058E
CANNOT GET EXCLUSIVE CONTROL ON dataset.
Reason:
The data set must be allocated with exclusive control to rename a PGF load module.
Action:
Check to see if the data set exists and make sure no other users have an queues on the
data set.
Chapter 3: PUT to QRFM 745
QI Messages
QI059I
NO PPA TABLE UPGRADING IS REQUIRED FOR THE SPECIFIED VERSION.
Reason:
Indicates that it is not necessary for you to run the PPA Load step of PPA customization
for your current version of PPA. All the objects within the PPA tables are current and do
not require upgrading.
QI060I
THIS STEP IS NOT REQUIRED FOR PRODUCTS SELECTED.
Reason:
Because you did not select Object Tracker or Query Analyzer, you do not need to
execute the step that you have selected.
QI061E
INVALID OPTIONS SPECIFIED. PRESS HELP FOR MORE INFO.
Reason:
Indicates that you have entered an invalid option.
Action:
Make sure you separate all options by a comma.
Valid format: (opt1,opt2,opt3)
■
Y-May run Online
■
W-May run Online/Issue Warning
■
B-Force to run in Batch
■
Y-May run without ACM
■
N-Force ACM ON
■
Y-May run Online (Catalog List)
■
W-May run Online/Issue Warning (Cat list)
■
C-Cancel run Online (Catalog List)
746 Message Reference Guide (PS to ZLB)
QI Messages
QI062E
INVALID OPTIONS SPECIFIED. PRESS HELP FOR MORE INFO.
Reason:
Indicates that you have entered an invalid option.
Action:
Make sure you separate all options by a comma.
Valid format: (opt1,opt2)
■
Y-May run Online
■
W-May run Online/Issue Warning
■
B-Force to run in Batch
■
Y-May run Detail
■
N-Force Summary option
QI063E
INVALID OPTIONS SPECIFIED. PRESS HELP FOR MORE INFO.
Reason:
Indicates that you have entered an invalid option.
Action:
Make sure you separate all options by a comma.
Valid format: (opt1,opt2)
■
Y-May run Online (Generate)
■
W-May run Online/Issue Warning (Generate)
■
C-Cancel run Online (Generate)
■
Y-May run Online (Execute)
■
W-May run Online/Issue Warning (Execute)
■
B-Force to run in Batch (Execute)
Chapter 3: PUT to QRFM 747
QI Messages
QI064E
AN ERROR HAS OCCURRED IN THE PIPELINE DDL CREATION PROCESS.
Reason:
The Pipeline product requires modifications to its DDL member to allow multiple
dictionaries to be defined. This error indicates that an error occurred while trying to
replicate the DDL for all dictionary IDs that were entered for the current DB2 subsystem.
Common causes for this error include the PIPEDDL member being missing, another user
holding the PIPEDDLO member exclusively or another user holding the entire CDBASRC
library with an exclusive lock.
QI065E
AN ERROR WAS FOUND IN THE PIPELINE MEMBER. PRESS PF1 FOR MORE INFO.
Reason:
The Pipeline object comparison feature reads the Pipeline parmlib member. Indicates
that an error occurred while processing the Pipeline parmlib member. Common causes
for this error include a missing PIPEDDL member, another user holding the PIPEDDLO
member exclusively or another user holding the entire CDBASRC library with an
exclusive lock. Also check the PIPELINE parmlib member for format errors or missing
subsystems.
QI066I
IF YOU HAVE SUBMITTED THE COPY JOB, PRESS PF1 FOR INSTRUCTIONS.
Reason:
The copy job you just submitted may copy members into new extents in the CA libraries.
So Post Install can access these new extents, after the copy job is complete you must
exit and reenter Post Install. This will assure the proper execution of the rest of your
installation.
QI067E
AN ERROR WAS FOUND IN THE ALOGDEL MEMBER. PRESS PF1 FOR MORE INFO.
Reason:
Indicates that an error occurred in the Edit Parmlib Member step while processing the
ALOGDEL parmlib member. Make sure the ALOGDEL parmlib member exists and has no
non-numeric entries. Where there are unusable entries, defaults of zero have been
used.
748 Message Reference Guide (PS to ZLB)
QI Messages
QI068E
AN ERROR WAS FOUND IN THE PDA MEMBER. TYPE STATUS FOR MORE INFO.
Reason:
Indicates that an error occurred in the Edit Parmlib Member step while processing the
PDA parmlib member. Check the PDA parmlib member for format errors or missing
subsystems. You can enter STATUS at the command line to get more information on the
PDA parmlib member.
QI069E
AN ERROR WAS FOUND IN THE RCEDIT MEMBER. TYPE STATUS FOR MORE INFO.
Reason:
Indicates an error occurred in the Edit Parmlib Member step while processing the
RCEDIT parmlib member. Check the RCEDIT parmlib member for format errors or
missing subsystems. You can enter STATUS at the command line to get more
information on the RCEDIT parmlib member.
QI070E
AN ERROR WAS FOUND IN THE PPA MEMBER. TYPE STATUS FOR MORE INFO.
Reason:
Indicates an error occurred in the Edit Parmlib Member step while processing the PPA
parmlib member. Check the PPA parmlib member for format errors or missing
subsystems. You can enter STATUS at the command line to get more information on the
PPA parmlib member.
QI071E
AN ERROR WAS FOUND IN THE SQE MEMBER. TYPE STATUS FOR MORE INFO.
Reason:
Indicates an error occurred in the Edit Parmlib Member step while processing the SQE
parmlib member. Check the SQE parmlib member for format errors or missing
subsystems. You can enter STATUS at the command line to get more information on the
SQE parmlib member.
Chapter 3: PUT to QRFM 749
QI Messages
QI171W
PLAN NOT FOUND FOR PLAN NAME = planname
Reason:
A plan named planname is listed in the new PLANSxx parmlib member (PTIPARMN DD)
but plan planname has not been bound. The Copy Plan Authorizations task will skip all
authorizations for planname.
Action:
Follow these steps:
1.
Prepare and execute the Bind Product Plans and Packages DB2 customization task.
2.
Resubmit the Copy Plan Authorizations job.
QI072E
AN ERROR WAS FOUND IN THE BATPROC MEMBER. TYPE STATUS FOR MORE INFO.
Reason:
Indicates an error occurred in the Edit Parmlib Member step while processing the
BATPROC parmlib member. Check the BATPROC parmlib member for format errors or
missing subsystems. You can enter STATUS at the command line to get more
information on the BATPROC parmlib member.
QI073E
AN ERROR WAS FOUND IN THE PQA MEMBER. TYPE STATUS FOR MORE INFO.
Reason:
Indicates an error occurred in the Edit Parmlib Member step while processing the PQA
parmlib member. Check the PQA parmlib member for format errors or missing
subsystems. You can enter STATUS at the command line to get more information on the
PQA parmlib member.
QI074E
AN ERROR WAS FOUND IN THE UTIL MEMBER. TYPE STATUS FOR MORE INFO.
Reason:
Indicates an error occurred in the Edit Parmlib Member step while processing the UTIL
parmlib member. Check the UTIL parmlib member for format errors or missing
subsystems. You can enter STATUS at the command line to get more information on the
UTIL parmlib member.
750 Message Reference Guide (PS to ZLB)
QI Messages
QI075E
AN ERROR WAS FOUND IN THE SECURE MEMBER. TYPE STATUS FOR MORE INFO.
Reason:
Indicates an error occurred in the Edit Parmlib Member step while processing the
SECURE parmlib member. Check the SECURE parmlib member for format errors or
missing subsystems. You can enter STATUS at the command line to get more
information on the SECURE parmlib member.
QI076E
AN ERROR WAS FOUND IN THE SETUP MEMBER. TYPE STATUS FOR MORE INFO.
Reason:
Indicates an error occurred in the Edit Parmlib Member step while processing the SETUP
parmlib member. Check the SETUP parmlib member for format errors or missing
subsystems. You can enter STATUS at the command line to get more information on the
SETUP parmlib member.
QI077E
AN ERROR WAS FOUND IN THE PIPELINE MEMBER. PRESS PF1 FOR MORE INFO.
Reason:
Indicates an error occurred in the Edit Parmlib Member step while processing the
PIPELINE parmlib member. Make sure the PIPELINE parmlib member exists and contains
the following cards: SRCLIB, DICTID, DICTSSID, OWNER, TABLEPDS, MAPLIB, and
DICTPLNS. Check that the first two cards are SRCLIB and DICTID and that there is only
one SRCLIB card for the parmlib member.
QI078E
NO MEMBERS SELECTED TO BE COPIED. PRESS PF1 FOR HELP.
Reason:
Indicates that there were no Security Exits or member names selected to be copied.
Action:
Check to see that you entered a 'Y' in any of the Copy EXIT## entries or that you have
specified a member name in the Member name entries.
Chapter 3: PUT to QRFM 751
QI Messages
QI079E
AN ERROR OCCURRED ALLOCATING dataset.
Reason:
An error occurred while attempting to allocate the control file for a copy of the Pipeline
dictionary bind cards.
Action:
Check to see if the data set file exists and if there are any locks on it.
QI080E
UNABLE TO COPY DICBINDO FROM dataset.
Reason:
The DICBINDO member could not be copied during a Pipeline bind.
Action:
Make sure the data set exists. If it exists, check to see if it is being held with an exclusive
lock.
QI081I
LOAD MODULE PTIPGFT HAD PREVIOUSLY BEEN RENAMED DSQUEGV1.
Reason:
This informational messages indicates that the renaming of the load module PTIPGFT to
DSQUEGV1 had already been done prior to the current execution of PGF customization.
QI082E
BOTH LOAD MODULES PTIPGFT AND DSQUEGV1 ARE MISSING.
Reason:
An attempt was made to rename the load module PTIPGFT to DSQUEGV1. Because
neither load module could be found, the attempt to rename was aborted.
Action:
Check to see that the modules have been properly copied and that they have not been
deleted.
752 Message Reference Guide (PS to ZLB)
QI Messages
QI083I
LOAD MODULE PTIPGFT HAS BEEN RENAMED DSQUEGV1.
Reason:
The PGF customization step has renamed load module PTIPGFT to DSQUEGV1. This
allows QMF to load the CA Governor rather than the IBM governor when the CA load
libraries are concatenated before the IBM QMF load libraries.
QI084E
VALID LINE COMMANDS ARE (U, S, B OR M). PRESS HELP FOR MORE INFO.
Reason:
You have entered an invalid line command.
Action:
The following are valid line commands. If you leave the field blank, the product will not
be installed.
■
U-Unselect a product for installation.
■
S-Install the product and its maintenance.
■
B-Install the base product.
■
M-Apply maintenance to the product.
QI085E
DB2 SUBSYSTEM NOT ENTERED IN DB2 SUBSYSTEM PARAMETERS. HELP FOR MORE.
Reason:
You have entered a DB2 subsystem ID that does not correspond to the ID entered in the
DB2 Subsystem Parameters screen of the Enter Installation Information step. If you wish
to perform tasks on the subsystem you have selected, return to the DB2 Subsystem
Parameters screen and enter the proper information.
QI086I
NO PREVIOUS TAPE VOLSER SELECTED.
Reason:
You have not entered a previous tape VOLSER for the tape last used to install PDA. The
VOLSER entered here is not necessarily the same as the last tape installed. It might also
be valid not to enter a VOLSER if PDA has not been previously installed. If PDA has not
been previously installed, you should not be executing this step. See your installation
manual for more instructions.
Chapter 3: PUT to QRFM 753
QI Messages
QI087E
AN ERROR WAS FOUND IN THE PDT MEMBER. TYPE STATUS FOR MORE INFO.
Reason:
The PDT Edit Parmlib feature requires the reading of the PDT parmlib member. Indicates
that an error occurred while processing the PDT parmlib member.
Action:
Check the PDT parmlib member for format errors.
QI088I
REVIEW THIS MEMBER FOR CORRECTNESS AND COPY TO A PROCEDURE LIB.
Reason:
After reviewing the PTXMAN procedure, you should copy the procedure from
high-level.CDBASAMP to a systems procedure library where procedures that start tasks
are normally kept.
QI089E
THE ATTEMPT TO AUTOSIZE HAS ENCOUNTERED AN ERROR.
Reason:
The autosize routine has encountered an error. A common error is not properly
specifying the VCAT information in the DB2 Subsystem Information screen in the Enter
Installation Information step. Other possible errors include the inability to access the
IDCAMS program from this address space and not having the DDF objects created in the
catalog.
Although the autosizing routine has experienced an error, it has attempted to provide as
much information as possible. You might be able to use the size values that it did
generate.
Action:
Review the size values and continue or attempt to rectify the error.
QI090E
QICPRF CLIST HAS FAILED. PLEASE CHECK THE CLIST FOR ERRORS.
Reason:
The CLIST could not allocate DB2 and COBOL libraries.
754 Message Reference Guide (PS to ZLB)
QI Messages
QI091I
NO PARMLIB MEMBERS FOUND IN THE PREVIOUS VERSION PARMLIB.
Reason:
No parmlib members were found in your previous version of the products.
QI092E
THE PROPER QI MAINT. HAS NOT BEEN INSTALLED. PRESS HELP.
Reason:
You have selected a target VOLSER that does not match the install maintenance that has
been unloaded. Be sure you have unloaded the install maintenance by executing the
UNLOADM step of the $AQIUSER job. If you have executed this step, be sure that the
proper tape has been unloaded and that the job did not have errors.
Action:
You must unload the install maintenance prior to attempting to unload any product
maintenance.
QI093E
THE LEVEL MEMBER OF THE CONTROL DATASET COULD NOT BE FOUND.
Reason:
The LEVEL member in the *.CDBASAMP data set is missing. This member is required to
run Post Install.
QI094E
UTILITY WORK DATASET ALREADY ALLOCATED. ENTER CANCEL TO EXIT.
Reason:
The Utility Work Dataset has already been allocated. If you already installed the CA
Utilities for DB2 or CA Log Analyzer, you do not have to run the format job.
Chapter 3: PUT to QRFM 755
QI Messages
QI095E
DB2 LOAD LIBRARY &db2LLIB IS NOT CATALOGED.
Reason:
The DB2 load library requested is not cataloged and is unable to be allocated.
Action:
Specify the proper name for this library.
QI096E
DB2 EXIT LIBRARY &db2ELIB IS NOT CATALOGED.
Reason:
The DB2 exit library requested is not cataloged and is unable to be allocated.
Action:
Specify the proper name for this library.
QI097E
MIGRATION NOT NEEDED FOR TAPES AFTER THE P303 SERIES.
Reason:
This message is generated during CA Dependency Analyzer customization.
QI098E
UNABLE TO OPEN &ODSN.
Reason:
This message is generated during SMP/E processing. A *.CDBASAMP (IVOLSER) member
or the SMP/E PTF VSAM control data set could not be allocated.
QI099E
UNABLE TO READ &ODSN.
Reason:
This message is generated during SMP/E processing.
756 Message Reference Guide (PS to ZLB)
QI Messages
QI100E
THIS FIX HAS ALREADY BEEN ACCEPTED. PRESS HELP FOR MORE INFO.
Reason:
This SMP/E fix has already been accepted. It cannot be accepted again.
QI101E
YOU HAVE NOT SELECTED ANY FIXES FOR THIS MAINT. SESSION. PRESS HELP.
Reason:
You have not selected any fixes.
QI102E
VALID LINE COMMANDS ARE (S OR U). PRESS HELP FOR MORE INFO.
Reason:
You have entered an invalid line command. Valid line commands are S or U only.
QI103E
UNABLE TO ALLOCATE &ODSN.
Reason:
The data set &ODSN was unable to be allocated. Make sure the data set exists. If it
exists, check to see if it is being held with an exclusive lock. You may continue with your
SMPE install, but the status of the fixes listed on this screen may be in error.
QI104E
SSID MUST BE SPECIFIED FOR A NEW SUBSYSTEM ENTRY.
Action:
You must specify an SSID for a new subsystem entry.
QI105E
“D” IS NOT A VALID ENTRY FOR A NEW SUBSYSTEM ENTRY.
Reason:
You have entered an invalid line command. You cannot enter D for a new subsystem
entry.
Chapter 3: PUT to QRFM 757
QI Messages
QI106E
VALID LINE COMMANDS ARE (S OR D). PRESS HELP FOR MORE INFO.
Reason:
You have entered an invalid line command.
Action:
Enter S to select a SSID, enter D to delete a SSID or leave the field blank.
QI107E
ONLY B ALLOWED FOR SMP/E INSTALL. PRESS HELP FOR MORE INFO.
Reason:
You have entered an invalid line command. For the SMP/E install, you may only enter a
B to install the base product. Maintenance may only be applied in an SMP/E install by
applying PTFs and ZAPs.
QI108I
INFORMATION FOR DICTIONARY ID &PIPDID ENTERED.
Reason:
Information for the dictionary ID has been accepted.
QI109E
YOU SHOULD NOT ENTER INFORMATION FOR THE SAME DICTID TWICE.
Reason:
The DICTID information has already been entered. It cannot be entered again.
QI110E
AT LEAST ONE STRLIB DATASET MUST BE ENTERED.
Reason:
You have not entered a DB2 STRLIB data set. At least one DB2 STRLIB data set must be
entered.
758 Message Reference Guide (PS to ZLB)
QI Messages
QI111E
AT LEAST ONE UPSLIB DATASET MUST BE ENTERED.
Reason:
You have not entered a UPSLIB data set. At least one UPSLIB data set must be entered.
QI112E
AT LEAST ONE UPLLIB DATASET MUST BE ENTERED.
Reason:
You have not entered a UPLLIB data set. At least one UPLLIB Dataset must be entered.
QI113E
ONE OR MORE SELECTED FIXES HAVE NOT BEEN RECEIVED.
Reason:
Indicates one or more of the selected fixes was not found in your SMP/E data sets. For
these fixes, the status area will be blank.
QI113I
The SPFALLOC command is not required and is no longer supported.
Reason:
The SPFALLOC command is no longer required to allocate file tailoring temporary work
files. The work files are allocated automatically.
Action:
None.
QI114E
ONE OR MORE SELECTED FIXES HAVE NOT BEEN APPLIED.
Reason:
Indicates a problem with applying one or more of the selected fixes.
Chapter 3: PUT to QRFM 759
QI Messages
QI114I
The SPFFREE command is not required and is no longer supported.
Reason:
The SPFFREE command is no longer required or supported for freeing file tailoring
temporary work files. The work files must remain allocated for the remainder of your
ISPF session.
Action:
None.
QI115W
SMP/E FIX STATUS CHECKING TURNED ON
Reason:
Indicates that fix status checking will be performed when you select Apply or Accept
options. If a possible SMP/E violation is detected, you will receive an information
message.
Action:
To turn off fix status checking, enter SMPSCOFF in the command line.
QI116W
SMP/E STATUS CHECKING TURNED OFF
Reason:
Indicates that fix status checking will not be performed when you select Apply or Accept
options. You will not be notified of possible SMP/E violations.
Action:
To turn on fix status checking, enter SMPSCOFF in the command line.
QI117E
ONE OR MORE FIXES HAVE ALREADY BEEN RECEIVED.
Reason:
One or more of the fixes you selected to receive have already been received. Fixes with
a status of REC (received) are eligible only to be Applied.
760 Message Reference Guide (PS to ZLB)
QI Messages
QI118E
ONE OR MORE FIXES HAVE ALREADY BEEN APPLIED.
Reason:
One or more of the fixes you have selected to apply have already been applied. Fixes
with a status of APP (applied) are eligible only to be Accepted.
QI119E
ONE OR MORE FIXES HAVE ALREADY BEEN ACCEPTED.
Reason:
One or more of the fixes you have selected to accept have already been Accepted.
QI121E
SMP/E REQUIRES LAST ZONE NAME QUALIFIER TO BE .CSI.
Reason:
The SMP/E Zone data set names must end in .CSI.
QI122E
SMP/E SUPERCEDED (SUP) FIXES CANNOT BE SELECTED.
Reason:
Fixes with a status of SUP (superceded) are eligible only to be Accepted.
QI123E
FIX MUST BE IN REC STATUS TO BE ELIBIBLE FOR APPLY SELECT.
Reason:
Fixes cannot be applied until they have a status of REC (received).
QI124E
FIX MUST BE IN REC/APP STATUS TO ELIGIBLE FOR ACCEPT SELECT.
Reason:
Fix can be selected for accept processing when status is REC or APP.
Chapter 3: PUT to QRFM 761
QI Messages
QI168
WORK DATASETS ISPWRK1 THROUGH ISPWRK4 HAVE BEEN ALLOCATED
Reason:
This message indicates that temporary ISPF work datasets needed for JCL file tailoring
have been allocated successfully.
Action:
None.
QI169
Datasets ISPWRK1 through ISPWRK4 have been freed.
Reason:
This messages indicates that temporary ISPF work datasets needed for JCL file tailoring
have been freed successfully.
Action:
None.
QI170
THERE WAS A PROBLEM ALLOCATING THE FOUR ISPWRK DATASETS
Reason:
This message indicates that one or more of the four ISPWRK1 – ISPWRK4 temporary
datasets were not allocated successfully. These temporary datasets are used as ISPF
work space for file tailoring of JCL file. It is possible that the JCL files may be tailored
successfully despite this message.
Action:
If the the tailoring is not successful (a B37 error may be encountered), then try changing
the work file unit using INS main menu option 0 followed by option 4.
762 Message Reference Guide (PS to ZLB)
QI Messages
QI171W
PLAN NOT FOUND FOR PLAN NAME = planname
Reason:
A plan named planname is listed in the new PLANSxx parmlib member (PTIPARMN DD)
but plan planname has not been bound. The Copy Plan Authorizations task will skip all
authorizations for planname.
Action:
Follow these steps:
1.
Prepare and execute the Bind Product Plans and Packages DB2 customization task.
2.
Resubmit the Copy Plan Authorizations job.
QI172W
userid LACKS GRANT PRIVILEGE FOR PLAN planname
Reason:
The Copy Plan Authorizations task has encountered a user/grantor who had the
privilege to GRANT EXECUTE on the old version of a plan but who does not have the
privilege to GRANT EXECUTE on the new version of the plan. The task skips all
authorizations from userid on planname.
The Copy Plan Authorizations task assumes that the grantors of the execute privilege for
the plans of the prior release also have the privilege to GRANT EXECUTE for the plans of
the new release. The privilege to GRANT EXECUTE for a plan of the new release can be
held in one or more of the following ways:
■
userid has EXECUTE privilege on plan planname with GRANT option.
■
userid has SYSADM authority.
■
userid is the owner of plan planname
This warning message is issued when the grantor does not have the GRANT EXECUTE
privilege for the new plan in any of the ways described.
Chapter 3: PUT to QRFM 763
QI Messages
Action:
Complete these steps:
1.
A user with SYSADM authority should do one of the following:
■
Give userid the privilege to grant execute on planname with this SQL
command:
GRANT EXECUTE ON PLAN planname TO userid WITH GRANT OPTION;
■
Give userid SYSADM authority with the SQL command:
GRANT SYSADM TO userid;
2.
Resubmit the Copy Plan Authorizations job.
QI300
ENTER COMMAND
Reason:
Select fixes before pressing Enter key.
QI301
INVALID COMMAND ENTERED.
Reason:
This command is not valid. For information on valid commands, enter a question mark
(?) in the command field.
QI302
INVALID CSI DATASET NAME.
Reason:
You have entered an invalid CSI data set name.
QI303
CSI DATASET NAME TOO LONG.
Reason:
This error is issued if the SMP/E data set name is larger than 44 characters.
764 Message Reference Guide (PS to ZLB)
QI Messages
QI304
INVALID RESPONSE, SPECIFY YES OR NO.
Reason:
Yes and No are the only valid responses.
QI308
DATASET NAME error reason
Reason:
An error was encountered processing the CDBASKL1 data set. The name of the
CDBASKL1 data set appears in the message. The error reason is one of the following:
■
DATASET NOT FOUND
■
ERROR PROCESSING REQUESTED DATASET
■
PROTECTED DATASET
■
VOLUME NOT ON SYSTEM
■
UNAVAILABLE DATASET
■
INVALID DATASET NAME
QI309
There are no Rebind Id members in the DBRMCNTL dataset
Reason:
There are NO rebind id members listed in the member selection list for panel INSSBND1
because the CDBASKL1 data set (formerly DBRMCNTL) is empty.
QI310
Enter one of the following options: ALLS, ALLU or PROCESS
Action:
Enter a valid primary command of ALLS, ALLU or PROCESS.
QI311
Enter one of the listed options
Action:
Enter one of the available options listed on panel INSMBIND.
Chapter 3: PUT to QRFM 765
QI Messages
QI313E
SSIDVER parameter in SETUP?? is incorrect for subsystem SSID
Reason:
The version specified in the SETUP?? member parameter SSIDVER is not an acceptable
DB2 version.
QI314E
SSIDMODE parameter in SETUP?? is incorrect for subsystem SSID
Reason:
The mode for the DB2 subsystem is missing or not one of the following acceptable
values for V8 and above subsystems:
■
CM (compatibility mode)
■
ENFM (enabling new function mode)
■
NFM (new function mode)
QI317
A MINIMUM OF ONE ENTRY IS REQUIRED WITHIN PERMANENT DASD FILES.
Reason:
This message indicates that a field value is missing in the INSALLOC screen.
Action:
When completing the fields in the INSALLOC screen, if there are no SMS classes entered,
then you must enter at least the device type field for permanent files.
QI318
THE DEVICE TYPE IS REQUIRED ALONG WITH THE VOLUME SERIAL
Reason:
This message indicated that device type is missing.
Action:
When specifying allocations parameters for permanent DASD datasets, if you specify a
volume serial, then you must also specify a device type.
766 Message Reference Guide (PS to ZLB)
QRFM Messages
QRFM Messages
Messages with the QRFM prefix are generated from CA Compile/PRF.
QRFM001I
FUNCTION COMPLETED SUCCESSFULLY.
Reason:
The function or action that you requested has been completed successfully.
Action:
None.
QRFM002S
PRODUCT FAILED ACQUIRING number BYTES OF STORAGE.
Reason:
A GETMAIN request was made by the product for the number of bytes indicated by
number. The request could not be satisfied by the system. The storage could not be
acquired and the product cannot continue with the requested function.
Action:
Try again after other storage in the system has been freed (for example, when other
users have finished their work). If there are no conflicting tasks or users, contact your
system administrator to determine whether your task can be allotted more storage.
QRFM003S
PRODUCT FAILED RELEASING STORAGE AT address.
Reason:
The product has issued a FREEMAIN request for storage at the address indicated by
address. The system could not grant this request. The storage has not been freed. The
product may continue to work, but this condition usually indicates that a severe error
has occurred.
Action:
If a severe error has occurred, terminate the current session and inform your system
administrator.
Chapter 3: PUT to QRFM 767
QRFM Messages
QRFM004S
PRODUCT INVOKED WITH INVALID PARAMETER LIST.
Reason:
The product has been invoked with an invalid parameter list, which prevents it from
operating correctly.
Action:
Contact your system administrator to correct this condition.
QRFM005S
PRODUCT SCREEN FILE COULD NOT BE OPENED OR CLOSED.
Reason:
The product screen file could not be opened or closed. This file contains the screen
definitions required to operate the product successfully. The file has been corrupted or
the product has not been installed correctly.
Action:
Contact your system administrator to ensure that the product is installed correctly.
QRFM006S
CAF ERROR: RETURN=return_code; REASON=reason_code; FUNCTION=function.
Reason:
The product's attempt to use the DB2 Call Attach Facility has failed. The message
indicates the Return and Reason Codes issued by DB2 as well as the function that was
being processed when the failure occurred. The program cannot execute unless the CAF
requests are successful. When SQLCA information is available, the SQL Error screen also
displays to further describe the failure.
Action:
Contact your system administrator to investigate the error indicated by the message
text. This message usually indicates that the product has not been installed correctly.
768 Message Reference Guide (PS to ZLB)
QRFM Messages
QRFM007S
INT ERROR: RETURN=return_code; REASON=reason_code; MODULE=module.
Reason:
The product has failed for an unexpected internal reason. The return code, reason code
and module indicate the location in the product where the failure occurred. The
requested function cannot be satisfied.
Action:
Contact CA with a description of the failure scenario and the message text.
QRFM008E
INVALID COMMAND: COMMAND IS NOT DEFINED FOR THIS SCREEN.
Reason:
The indicated command is not supported for the current screen or in the current
context. For example, you may be attempting to use a scroll command on a screen that
is not scrollable.
Action:
Use a command that is supported by this screen. You may use the COMMANDS
command to see a list of the commands that are supported.
QRFM009E
INVALID SELECTION.
Reason:
The selection you have made is not valid.
Action:
Use a selection that is listed in the selection list next to the selection field.
Chapter 3: PUT to QRFM 769
QRFM Messages
QRFM010E
INVALID FUNCTION KEY.
Reason:
The function key that you have hit is not defined to the current screen.
Action:
Use a function key that is defined to the current screen. A partial list of defined keys
displays at the bottom of the screen. To obtain a complete list of the key definitions for
the current screen, use the KEYS command.
QRFM011E
TOO MANY ARGUMENTS SPECIFIED FOR COMMAND.
Reason:
You have entered more arguments in the command field of the current screen for the
desired command than that command supports.
Action:
Correct the argument list in the command field and retry. You can obtain a full
description of the command by entering the COMMANDS command and selecting the
desired command from the presented list.
QRFM012E
INVALID COMMAND: COMMAND IS NOT SUPPORTED BY COMPILE/PRF.
Reason:
The command that you have indicated is not defined to the product. The request cannot
be processed. This message can also be generated when using an invalid command
name as an argument to the HELP command. For example, you may have requested
help for the XYZ command by entering “HELP XYZ” in the command field.
Action:
Correct the name of the command and retry. To obtain a list of the commands defined
to the product, use the COMMANDS command or specify the HELP command while the
cursor is positioned in the command field.
770 Message Reference Guide (PS to ZLB)
QRFM Messages
QRFM013E
AMBIGUOUS COMMAND.
Reason:
The command abbreviation that you have indicated is ambiguous. More than one
command defined to the product has this abbreviation. The request cannot be
processed. For example, you may have entered “R” when both the RIGHT and RUN
commands are supported. Or you may have used the HELP command with an
ambiguous command name as an argument, such as “HELP R”.
Action:
Enter more characters to identify the command uniquely. Use the COMMANDS
command to obtain a list of all commands that are defined to the product.
QRFM014E
INVALID ARGUMENT SPECIFIED FOR COMMAND.
Reason:
An argument that you have supplied for the indicated command is not valid. For
example, the command may require the entry of a numeric argument, but you have
entered a non-numeric value.
Action:
Change the argument to the required value and retry. To obtain detailed information
about the syntax of the particular command, use the COMMANDS command and select
the desired command from the presented list.
QRFM015E
INVALID MESSAGE NUMBER. SPECIFY A MESSAGE NUMBER OF 1 TO 3 DIGITS.
Reason:
You have entered an invalid message number. Valid message numbers are in the range,
1 to 999. You must enter the number of a message that is currently defined.
Action:
Correct your input to use a 1- to 3-digit number that identifies a message and retry.
Chapter 3: PUT to QRFM 771
QRFM Messages
QRFM016I
VERTICAL SCROLL INTERVAL IS scroll_amt scroll_type.
Reason:
This message appears when the vertical scroll interval is changed and when you request
it with the use of the question mark (“?”) as an argument for a vertical scroll command.
The scroll interval is the number of lines indicated by scroll_amt and may be further
described by scroll_type, which indicates the type of scrolling currently in effect. Each
time you use a vertical scroll command, such as UP or DOWN, the display will be
adjusted by this interval.
Action:
None.
QRFM017W
CANNOT SCROLL UP. ALREADY AT TOP OF LIST.
Reason:
You have used a vertical scroll command (such as UP), but the display is already
positioned at the top of the list. There is no further data above the currently displayed
items.
Action:
If you meant to scroll the display in a different direction, use the appropriate command
such as DOWN, LEFT, or RIGHT.
QRFM018W
CANNOT SCROLL DOWN. ALREADY AT BOTTOM OF LIST.
Reason:
You have used a vertical scroll command (such as DOWN), but the display is already
positioned at the bottom of the list. There is no further data below the currently
displayed items.
Action:
If you meant to scroll the display in a different direction, use the appropriate command
(such as UP, LEFT, or RIGHT).
772 Message Reference Guide (PS to ZLB)
QRFM Messages
QRFM019W
CANNOT VIEW PREVIOUS PAGE. THIS IS THE FIRST PAGE IN THE LIST.
Reason:
You have requested the display of the previous page or screen, but there is no such
page. You are already viewing the first available page.
Action:
If you meant to view a later page, use the NEXT command.
QRFM020W
CANNOT VIEW NEXT PAGE. THIS IS THE LAST PAGE IN THE LIST.
Reason:
You have requested the display of the next page or screen, but there is no such page.
You are already viewing the last available page.
Action:
If you meant to view a previous page, use the PREVIOUS command.
QRFM021E
REQUEST COULD NOT BE COMPLETED DUE TO SQL ERROR.
Reason:
The action being taken could not be completed because it required the successful
execution of an SQL statement by DB2. The SQL request did not complete successfully.
In most cases, the SQL Error Help screen displays detailed information about the SQL
error.
Action:
If the error occurred due to a temporary system problem, you may be able to retry your
request now or after waiting until the problem clears up. If the error is more severe, you
should contact your system administrator with detailed information describing the
actions you are taking and the SQL error that is being generated.
Chapter 3: PUT to QRFM 773
QRFM Messages
QRFM022I
RECORD(S) RETRIEVED SUCCESSFULLY.
Reason:
The specified record, or records, have been retrieved successfully.
Action:
None.
QRFM023I
RECORD(S) CREATED SUCCESSFULLY.
Reason:
The specified record, or records, have been created successfully. The new values have
been saved.
Action:
None.
QRFM024I
RECORD(S) UPDATED SUCCESSFULLY.
Reason:
The specified record, or records, have been updated successfully. The new values have
been saved.
Action:
None.
QRFM025I
RECORD(S) DELETED SUCCESSFULLY.
Reason:
The specified record, or records, have been deleted successfully.
Action:
None.
774 Message Reference Guide (PS to ZLB)
QRFM Messages
QRFM026W
RECORD NOT FOUND.
Reason:
The specified record was not found. You have requested access to a record that does
not exist. The record cannot be retrieved, updated or deleted.
Action:
Ensure that the identifying information for the desired record is correct. You may have
mistyped this information. If this information is correct, you might need to recreate the
record. If you are not sure of this information, you may be able to use wildcard criteria
to invoke a list of records from which the desired record can be selected.
QRFM027W
RECORD ALREADY EXISTS.
Reason:
The specified record already exists. It cannot be created again.
Action:
Ensure that the identifying information for the desired record is correct. You may have
mistyped this information. If this information is correct, you might need to delete or
update the existing record. If you are unsure of this information, you may be able to use
wildcard criteria to invoke a list of records where information about existing records can
be determined.
QRFM028I
KEY SETTINGS RESET TO DEFAULT VALUES SUCCESSFULLY.
Reason:
The indicated function key settings have been reset to their default values.
Action:
None.
Chapter 3: PUT to QRFM 775
QRFM Messages
QRFM029I
KEY SETTINGS RECORDED SUCCESSFULLY.
Reason:
The indicated function key settings have been recorded successfully. These settings will
now be in effect for the current screen until you change them or reset them to their
default values with the RESET command.
Action:
None.
QRFM030E
REQUIRED INFORMATION IS MISSING.
Reason:
You have not entered the information that is required to fulfill your request. The cursor
is positioned to the required field.
Action:
Enter the appropriate value.
QRFM031E
INVALID NUMERIC ENTRY.
Reason:
The indicated value is not a valid numeric entry. A valid numeric entry must be made to
process your request. The cursor is positioned to the field that is in error.
Action:
Enter a valid numeric value.
776 Message Reference Guide (PS to ZLB)
QRFM Messages
QRFM032E
INVALID DATE FORMAT SPECIFIED.
Reason:
The indicated entry does not indicate a valid date format. A valid entry must be made to
process your request. The cursor is positioned to the field that is in error.
Action:
Enter a valid date format. Valid entries are:
■
ISO (International). Example: CCYY-MM-DD
■
USA (United States). Example: MM-DD-CCYY
■
STD (Standard). Example: YY/MM/DD
■
EUR (European). Example: DD MM CCYY
■
XS (Extended-Short). Example: DD Mon CCYY (restricted to report output)
■
XL (Extended-Long). Example: Month DD, CCYY (restricted to report output)
QRFM033E
TSO COMMAND FAILED RC=return_code, RS=reason_code, AB=abend_code.
Reason:
The requested TSO command did not complete successfully. The return code, reason
code, and abend code that were returned from the system are included in the message
text to assist you in determining why the command failed. This is not a product related
problem. The product only passes the requested command to your operating system.
Action:
Use a valid command that is supported in your system or contact your system
administrator to investigate the reason your system cannot process the requested
command.
Chapter 3: PUT to QRFM 777
QRFM Messages
QRFM034E
"DSN" COMMAND INVALID IN COMPILE/PRF.
Reason:
The DSN command cannot be processed. It would attempt to establish a connection to
DB2 for the DSN Command Processor. However, the program is already connected to
DB2 using the Call Attach Facility. These connections are not compatible.
Action:
Use a valid command that is supported by your system.
QRFM035E
INVALID VALUE SPECIFIED.
Reason:
You have entered an invalid value. The cursor is positioned at the field that is in error. A
valid value is required. You can use the HELP command to obtain help for the field when
the cursor is positioned in the field. A list of valid entries will be provided in the help
information.
Action:
Enter a valid value.
QRFM036E
INVALID ENTRY: USE "Y" OR "N".
Reason:
You have entered an invalid conditional indicator.
QRFM037I
SOURCE CODE GENERATED SUCCESSFULLY.
Reason:
The source code has been generated successfully for the new program.
Action:
None.
778 Message Reference Guide (PS to ZLB)
QRFM Messages
QRFM038I
PLEASE SET HOST VARIABLE TYPES AND DEFAULT VALUES.
Reason:
Review the current list of host variables and update their types and values. The variable
types determine the type of host variable that will be used in the generated source code
and the logic that manipulates the variable. The value will be used as the default value
in the generated source code when an override value is not specified at the time of
execution.
Action:
When the list is correct, press Enter to generate the program. Use the END command to
cancel the request to generate the program. Update and finalize the list.
Note: This message is informational and does not indicate an error.
QRFM039S
DSNHDECP NOT ACCESSIBLE. DB2 INSTALL PARMS CANNOT BE DETERMINED.
Reason:
The DSNHDECP module cannot be loaded. This is a data-only module that is created
during installation of DB2 and contains information about the installation. The
information is required to operate correctly. It describes the type of character set being
used, the size of decimal data fields, the delimiter recognized in SQL statements, and
other things that may be important to the product.
Action:
Ensure that the module is defined and accessible to the current region so that it may be
dynamically loaded.
Chapter 3: PUT to QRFM 779
QRFM Messages
QRFM040E
INVALID DATASET NAME: UNBALANCED QUOTES.
Reason:
You have entered a data set name with unbalanced quotes. The quotes are used to
indicate whether the entered data set name is fully qualified and are used at the
beginning and end of the data set name if present. If one quote is entered, the matching
quote must also be entered, as in the following examples:
'CREATOR.QUALIFIER.QUALIFIER'
'CREATOR.QUALIFIER.QUALIFIER(MEMBER)'
Action:
Enter a fully qualified data set name with balanced quotes, or enter an unqualified data
set name without any quotes.
QRFM041E
INVALID DATASET NAME: INVALID CHARACTER USED.
Reason:
You have used an invalid character in the data set name. Qualifiers, as well as member
names, must be composed of the following types of characters:
■
Alphabetic
■
Numeric
■
National (In the U.S., these are @, #, and $.)
Further, the first character of a qualifier or member name cannot be numeric and
spaces cannot be embedded in the name.
Action:
Enter a data set name that uses valid characters.
780 Message Reference Guide (PS to ZLB)
QRFM Messages
QRFM042E
INVALID DATASET NAME: INVALID LENGTH OF NAME, QUALIFIER OR MEMBER.
Reason:
You have entered a data set name containing a qualifier or member name whose length
is not valid. Names must consist of 1 to 8 characters. Qualifiers are separated by
periods. A member name is delimited by parentheses. Further, the true data set name
(excluding the member specification) cannot exceed 44 characters.
Action:
Enter a data set name with valid qualifiers (and member name, if applicable).
QRFM043E
INVALID DATASET NAME: A MEMBER NAME CANNOT BE USED IN THIS CONTEXT.
Reason:
You have included a member name in the data set specification. The program does not
accept the inclusion of a member name in this context. The member name is indicated
by the use of parentheses.
Action:
Enter a data set name without specifying a member.
QRFM044S
FILE ACCESS FAILED: RETURN=return_code; REASON=reason_code; FUNC=abend_code.
Reason:
The attempted file access has failed for an unexpected or unusual reason. The return
code and reason code are the codes returned by the file manager subtask. The function
indicates the type of processing being done by the file manager subtask.
Action:
Double-check any parameters that you have supplied to the product regarding this file
access request. It may be that a parameter was specified incorrectly. Verify that the
parameters are valid for your installation and that they are compatible with each other.
If you are attempting to use existing objects, ensure that these do exist and are
accessible, as you have presumed. If the specifications appear to be correct, the product
may not be installed correctly.
Finally, your installation may have other security software that is interfering with or
preventing the desired access. Check this.
Chapter 3: PUT to QRFM 781
QRFM Messages
QRFM045W
END OF FILE REACHED. RECORD NOT FOUND.
Reason:
You have read past the end of the current file. There are no more records to retrieve.
Action:
Continue processing the previously retrieved records as desired, but do not attempt to
read any more records from the current file.
QRFM046E
FILE ACCESS FAILED: SUBTASK COULD NOT ACQUIRE NECESSARY STORAGE.
Reason:
You have attempted to access a file, and this access requires the acquisition of
additional storage. There was not enough storage available to process the request.
Action:
Retry after other storage has been freed by other users. If there is no other storage that
can be freed, contact the system administrator to obtain a larger allocation where to
operate the product.
QRFM047E
FILE ACCESS FAILED: LRECL DOES NOT MATCH BLKSIZE FOR BLOCK DATASET.
Reason:
You have requested access to a blocked data set where the logical record length (LRECL)
must match the block size (BLKSIZE). However, the specified LRECL does not match the
BLKSIZE. The request cannot be processed.
Action:
Alter the record length or blocking specifications to make the two compatible, then
retry your request.
782 Message Reference Guide (PS to ZLB)
QRFM Messages
QRFM048E
FILE ACCESS FAILED: INVALID LABELLING METHOD SPECIFIED.
Reason:
You have specified an invalid labeling method for a data set. The data set cannot be
accessed with such a specification. Valid LABEL values are NL, SL, BLP, or blank.
Action:
Use a valid label specification and retry your request.
QRFM049E
FILE ACCESS FAILED: INVALID FILE STATUS SPECIFIED.
Reason:
You have specified an invalid file status for a data set. The data set cannot be accessed
with such a specification. Valid STATUS values are SHR, OLD, MOD, and NEW.
Action:
Use a valid status and retry your request.
QRFM050E
FILE ACCESS FAILED: INVALID FILE FORMAT SPECIFIED.
Reason:
You have specified an invalid file format for a data set. The data set cannot be accessed
with such a specification. Valid FORMAT values are F, FB, V, and VB.
Action:
Use a valid format and retry your request.
QRFM053S
INSTALLATION ERROR: PIEFILM MODULE IS NOT AVAILABLE AS REQUIRED.
Reason:
The program has determined that the PIEFILM load module has not been installed
correctly. This prevents any data set access.
Action:
Contact your system administrator to have the product installed correctly.
Chapter 3: PUT to QRFM 783
QRFM Messages
QRFM054E
FILE ACCESS FAILED: SPECIFIED UNIT IS NOT AVAILABLE.
Reason:
You have requested access to a data set on a unit that is not currently available. This
unit must be available to satisfy the request. For example, you may be attempting to
access a tape that has not been mounted and made available to the system.
Action:
Check your unit specification. You may have indicated the wrong unit. If the unit is
correct, contact your data center to determine when and how the unit may be made
available and retry your request when it is.
QRFM055E
FILE ACCESS FAILED: SPECIFIED VOLUME DOES NOT EXIST.
Reason:
You have requested access to a data set on a volume that does not exist. This volume
must exist to satisfy the request.
Action:
Correct your volume specification to indicate a volume that is defined to your system.
QRFM056E
FILE ACCESS FAILED: SPECIFIED UNIT DOES NOT EXIST.
Reason:
You have requested access to a data set on a unit that does not exist. This unit must
exist to satisfy the request.
Action:
Correct your unit specification to indicate a unit that is defined to your system.
784 Message Reference Guide (PS to ZLB)
QRFM Messages
QRFM057E
FILE ACCESS FAILED: REMOTE DESTINATION IS NOT DEFINED TO JES.
Reason:
You have requested access to a remote destination that is not defined to your job entry
system (JES). It must be defined to process your request.
Action:
Correct your destination specification to indicate a destination that is defined to your
job entry system.
QRFM058E
FILE ACCESS FAILED: ACF2 VIOLATION OCCURRED WHILE ACCESSING DATASET.
Reason:
You have requested access to a data set that is protected by CA ACF2. This is a security
system that has been installed in your system to prevent access to certain data sets. The
request cannot be processed.
Action:
If you should have access to the indicated data set, have the CA ACF2 security in your
system changed to allow such access. If you have indicated the desired data set
incorrectly, change your specifications and retry.
QRFM059E
FILE ACCESS FAILED: INVALID DATASET NAME SPECIFIED.
Reason:
The name of the data set that you have specified is not valid. A valid data set name is
composed of qualifiers that are each 1 to 8 characters in length. The total length of the
data set name cannot exceed 44 characters. Each qualifier must begin with an
alphabetic or national character. The other characters may be alphabetic, national, or
numeric.
Action:
Correct the name of the data set and retry.
Chapter 3: PUT to QRFM 785
QRFM Messages
QRFM060E
FILE ACCESS FAILED: INVALID FILE DISPOSITION SPECIFIED.
Reason:
You have specified an invalid file disposition for a data set. The data set cannot be
accessed with such a specification. Valid DISP values are as follows:
■
C or CATALOG
■
K or KEEP
■
D or DELETE
Action:
Use a valid disposition and retry your request.
QRFM061E
FILE ACCESS FAILED: DATASET CURRENTLY BEING USED BY ANOTHER USER.
Reason:
The data set that you wish to access is not available right now. It is being accessed by
another user, application, or job. Your request cannot be processed until the data set is
available.
Action:
Wait for the data set to be freed by the other user and retry.
QRFM062W
OBJECT BEING CHANGED BY A PRF USER AND IS NOT AVAILABLE.
Reason:
The designated CA Report Facility object (query, form, or procedure) is currently being
altered by a CA Report Facility user. The program cannot use this object until the
changes have been saved and the object's definition is complete.
Action:
Wait for the CA Report Facility user to complete the changes or use a different object.
786 Message Reference Guide (PS to ZLB)
QRFM Messages
QRFM063W
OBJECT IS NOT DEFINED TO PRF.
Reason:
The designated object (query, form, or procedure) is not defined to CA Report Facility.
The program can only process existing objects.
Action:
Check your input. It may be that you have used the wrong name to identify the desired
object. If this is the correct object name, have a CA Report Facility user create the object
before you attempt to use it.
QRFM064E
INVALID OBJECT DEFINITION.
Reason:
The object (query, form, or procedure) definition is not valid. It may be that the output
from the Export Facility has been altered and is no longer valid or that multiple object
definitions exist in a single data set. The program expects a single object definition. For
queries, the SQL syntax must be included. In other words, the object definition must
also be complete and usable. It may be that you have exported an object whose
definition has not yet been completed and is not executable.
Action:
Use a valid object definition.
QRFM065E
UNSUPPORTED VERSION OF PRF.
Reason:
You have indicated a version of CA Report Facility that is not supported. This can arise if
you are using object definitions that were exported from a version of CA Report Facility
that is not supported.
Action:
Use a supported version. This is specified in the region profile.
Chapter 3: PUT to QRFM 787
QRFM Messages
QRFM066E
UNSUPPORTED FORM TYPE.
Reason:
You have indicated a type of form that is not supported. This can arise if you are using
object definitions that were exported outside of the program. Access to unsupported
form types is automatically prevented. Column and Tabulation forms are supported.
Action:
Use a supported form type.
QRFM067E
QUERY AND FORM DEFINITIONS ARE NOT COMPATIBLE.
Reason:
You have supplied query and form definitions that are not compatible. This can arise if
you attempt to use a form that is not defined for the indicated query or that is not
synchronized with the query (which may occur if changes have been made to the query
that have not been incorporated into the form). The program requires the use of query
and form definitions that are compatible with each other.
Action:
Use compatible query and form definitions.
QRFM068E
FILE ACCESS FAILED: DATASET DOES NOT EXIST.
Reason:
You have specified a data set that does not exist. The data set must exist to process your
request successfully. Data sets may be specified as qualified or unqualified.
For qualified, a full data set name is specified in quotes (for example,
'userid.QRF.COBOL'). For unqualified, a partial data set name is specified without
quotes, to which Compile/PRF will append your user ID (for example, QRF.COBOL).
Use the name of an existing data set.
788 Message Reference Guide (PS to ZLB)
QRFM Messages
QRFM069E
FILE ACCESS FAILED: MEMBER DOES NOT EXIST.
Reason:
You have specified a member that does not exist in the designated data set. The
member must exist to process your request successfully. The member name is entered
as the last qualifier in the data set name and is enclosed in parentheses. For example, to
indicate the member, ABC, in the data set, 'userid.QRF.COBOL', enter:
'userid.QRF.COBOL(ABC)'
Use the name of an existing member.
QRFM070E
INVALID DATASET NAME: DATASET NAME CANNOT EXCEED 42 CHARACTERS.
Reason:
You have entered a data set name that uses more than 42 characters. The program can
only process data set names that have 42 or fewer characters in their name.
Action:
Enter a valid data set name that uses 42 or fewer characters.
QRFM071E
MODEL CONTAINS INVALID STATEMENTS AND IS NOT USABLE.
Reason:
The model being processed contains statements that render it unusable. This is usually
caused by attempting to use the wrong model or model library or indicates that the
model has been altered. For example, a COBOL program model may become unusable if
a substitution variable is moved to, or introduced at, the end of a line. When the model
is processed, the substitution value may cause the generated line to exceed the
maximum allowable size.
Action:
Ensure use of the correct model library and member. Make sure that the model has not
been altered in such a way as to make it unusable.
Chapter 3: PUT to QRFM 789
QRFM Messages
QRFM072E
QUERY USES TOO MANY HOST VARIABLES.
Reason:
The query uses too many host variables. The program enforces the CA Report Facility
limit of 50 replaceable parameters in a query. Therefore, a query can only use 50
distinct host variables. This does not prevent the reference to a single host variable
multiple times.
Action:
Alter the query to use no more than 50 different host variables.
QRFM073E
INVALID PROGRAM NAME: CANNOT USE "QRF" AT START OF NAME.
Reason:
You have entered a program name that uses QRF as the first three characters. This is not
allowed, as programs of this name are reserved for use by the actual product.
Action:
Enter a valid program name that does not start with QRF.
QRFM074E
UNSUPPORTED QUERY TYPE.
Reason:
You have indicated a type of query that is not supported. This can arise if you are using
object definitions that were exported outside of the program. When using the program
to obtain the object definitions, access to unsupported query types is automatically
prevented. DB2 queries are supported. File queries are not supported.
Action:
Use a query type that is supported.
790 Message Reference Guide (PS to ZLB)
QRFM Messages
QRFM075E
INVALID TIME FORMAT SPECIFIED.
Reason:
The indicated entry does not indicate a valid time format. A valid entry must be made to
process your request. The cursor is positioned to the field that is in error.
Action:
Enter a valid time format. Valid entries are:
■
ISO (International). Example: HH.MM.SS.
■
USA (United States). Example: HH:MM xM
■
JIS (Japenese). Example: HH:MM:SS
QRFM076E
CONFLICTING ADV COMPILER OPTIONS SPECIFIED.
Reason:
You have specified an ADV COBOL compiler option that conflicts with your requested
use of the Advance feature. You have turned off the Advance feature and included the
ADV compiler option or you have turned on the Advance feature and included the
NOADV compiler option. If ADV compiler option is used, it must be kept in sync with the
Advance feature. Note that the ADV/NOADV compiler option does not necessarily need
to be included in the Compile Options depending on defaults for your installation.
Action:
Use an ADV compiler option that agrees with the requested usage of the Advance
feature (which is also specified in the user profile) or remove the ADV compiler option
specification to use the default for your installation (which also must agree with the
requested use of Advance).
QRFM077I
JOB job_name(job_number) SUBMITTED.
Reason:
A job has been submitted for batch execution to fulfill your request. The name and
number of the job are job_name and job_number, respectively.
Action:
None.
Chapter 3: PUT to QRFM 791
QRFM Messages
QRFM078W
JOB CARDS ARE NOT RECORDED FOR YOUR ID.
Reason:
The program has determined that you have not defined any job cards for your ID. Valid
job cards are usually required to complete the process that you are about to initiate. For
example, when submitting a batch program for background execution, the job built will
require valid job cards when it is submitted to JES. This may be acceptable if you intend
to save the job in a data set and then edit it before submission or if valid job cards have
been added to the model JCL.
Action:
If you must define job cards, use the global JOBCARDS command.
QRFM079E
UNSUPPORTED OBJECT TYPE.
Reason:
You have indicated a type of object that is not supported. The program supports QUERY
and FORM objects. It does not support PROC objects. When designating the type of
object, you may use any truncated abbreviation of that object type (such as QU to
indicate a query or F to indicate a form).
Action:
Use an object type that is supported.
QRFM080I
JOB CREATED AND SAVED SUCCESSFULLY.
Reason:
A job has been created for batch execution of the specified program and has been
successfully saved in the designated data set. When submitted to JES, this job will cause
the batch program to be executed.
Action:
None.
792 Message Reference Guide (PS to ZLB)
QRFM Messages
QRFM081W
REQUEST HAS BEEN CANCELLED.
Reason:
The request that was being processed has been canceled. This has been done in
response to your command.
Action:
If you wish to initiate the request again, you may do so.
QRFM082E
FILE ACCESS FAILED: MEMBER MUST BE SPECIFIED FOR A PDS.
Reason:
You have indicated a partitioned data set (PDS) without specifying a member. To access
a PDS, the name of the desired member must also be specified. The member name is
entered as the last qualifier in the data set name and is enclosed in parentheses. For
example, to indicate the member, ABC, in the data set, 'PDCHIP.QRF.COBOL', enter:
'PDCHIP.QRF.COBOL(ABC)'
Action:
Specify the name of the desired member.
QRFM083E
FILE ACCESS FAILED: DATASET IS NOT A PDS.
Reason:
You have specified a data set that is not a partitioned data set (PDS). You must enter the
name of a data set that is partitioned.
Action:
Enter the name of a partitioned data set.
Chapter 3: PUT to QRFM 793
QRFM Messages
QRFM084I
MODULE REGISTERED SUCCESSFULLY.
Reason:
Your request to register the current module has been completed successfully. The
module can now be executed using the execution facilities for batch or online programs
(as appropriate).
Action:
None.
QRFM085E
INVALID OBJECT NAME.
Reason:
The object name you have specified is not valid. Object names identify an object by
using a two-part name in the form of creator.name where creator is optional and
defaults to your user ID if it is not specified. Parts of the name must conform to DB2
naming standards for ordinary identifiers, where creator is a short identifier and name is
a long identifier.
Action:
Enter a valid object name.
QRFM086E
ONLY "I" IS ALLOWED IN THE PRIMARY LINE COMMAND FIELD.
Reason:
You have entered an invalid value in the primary line command field. Only I can be used
in this field, indicating that a new line is to be inserted in the list before the first line
displays on the screen. The primary line command field is the line command field that
appears before the start of the displayed list. All other lines in the list have a command
field where all available action codes can be used.
Action:
Enter I if you want to insert a new line at the top of the list. Enter other selection codes
on the line to which the action is to be applied.
794 Message Reference Guide (PS to ZLB)
QRFM Messages
QRFM087E
INVALID VARIABLE NAME.
Reason:
The variable name you have specified is not valid. Variable names must:
■
Consist of 1 to 8 characters without embedded spaces
■
Start with an alphabetic character
■
Consist entirely of alphabetic and numeric characters
Action:
Enter a valid variable name.
QRFM088I
PLEASE SPECIFY OVERRIDE VALUES FOR HOST VARIABLES.
Reason:
Override values for host variables are needed.
Action:
Supply override specifications for the host variables that are used by the current
program. If any default settings were registered, those settings are displayed and can be
changed. You may add overrides by inserting new records in the list. When the list is
correct, press Enter to submit the program. Use the END command to cancel the
request to submit the program. Update and finalize the list.
This message is informational and does not indicate an error.
Chapter 3: PUT to QRFM 795
QRFM Messages
QRFM089E
INVALID VARIABLE TYPE.
Reason:
The variable type you have entered is not valid. Valid types are entered in the form of
cpp for alphanumeric and integer variables and in the form of cpp,ss for other variables,
where:
c
Indicates the category of data.
pp
Indicates the precision of the data.
ss
Indicates the scale of the data (does not apply to alpha or integer data).
Action:
Enter a valid variable type such as “A20,” “P9,2”, or “H3.”
QRFM090E
FORM EXCEEDS MAXIMUM DEPTH SUPPORTED BY ONLINE PROGRAMS.
Reason:
The specified form requires a minimum page depth that exceeds the maximum depth
that is supported for online programs. The standard browse facility that is used by
online programs generated only supports pages that do not exceed 22 lines in depth.
This form needs more than 22 lines and cannot be generated. For example, the page
header, column headings, break headers, and page footers require 22 or more lines,
leaving no room for data to be displayed by the online program.
Action:
Alter the form or use a different form so that 22 or fewer lines are needed.
QRFM091I
PROGRAM RUN SUCCESSFULLY.
Reason:
The specified program has been successfully executed.
Action:
None.
796 Message Reference Guide (PS to ZLB)
QRFM Messages
QRFM092E
COMPILE/PRF INVOKED WITH INVALID TRANSACTION.
Reason:
The program, or one of its secondary programs, has been invoked with an invalid
transaction. You can only invoke the program with the primary driver transaction, QRF,
that is supplied with the product. You cannot access the secondary programs by
invoking their own transactions. For example, you cannot invoke the QRFM transaction
from top-level CICS. This error can also arise after running a generated program that has
been altered and no longer uses the proper protocol for returning control.
Action:
See the product documentation for details about the structure of programs generated
for execution in CICS. Use the transaction named QRF to invoke the product.
QRFM093E
YOU ARE NOT AUTHORIZED TO USE THAT TRANSACTION.
Reason:
You have attempted to use a transaction for which you are not authorized.
Authorization is determined by CICS and maintained by the CICS administrator. This
error can occur when attempting to run a generated program that is properly defined to
CICS but is restricted to other users.
Action:
Use a transaction for which you are authorized or contact your CICS administrator to
obtain the necessary authorization.
Chapter 3: PUT to QRFM 797
QRFM Messages
QRFM094E
TRANSACTION IS NOT DEFINED TO CICS.
Reason:
The transaction is not defined to CICS and cannot be invoked. It cannot be used until it
has been defined. Transactions are defined in the Program Control Table or the CICS
System Definition (starting with CICS Version 3).
This error occurs when attempting to run a generated program that has not been
defined to your CICS region. Be sure to define and install the proper definitions before
attempting to run the program. See the product manual for details about defining and
installing resources for generated programs.
Action:
Correct the name of the transaction if you have entered it incorrectly; or have the
transaction definition added to the PCT or CSD in your region.
QRFM095E
INVALID TRANSACTION NAME: CANNOT USE "QRF" AT START OF NAME.
Reason:
You have entered a transaction name that uses QRF as the first three characters. This is
not allowed, as transactions of this name are reserved for use by the actual product.
Action:
Enter a valid transaction name that does not start with QRF.
QRFM096W
VALID CPU PASSWORD HAS NOT BEEN DEFINED TO TRIAL CONTROL SYSTEM.
Reason:
The CA Trial Control System has determined that a valid password for the current CPU
has not been defined in the password module that was created when the product was
installed. This may be due to an upgrade that has occurred since the product was
installed. You are required to register your CPU with CA to use the product. You will be
supplied a valid password that can be incorporated in your password module. You may
use the CPUID command to see a list of the registered CPUs.
Action:
Obtain a valid password and record it in the password module.
798 Message Reference Guide (PS to ZLB)
QRFM Messages
QRFM097E
VALID PRODUCT PASSWORD HAS NOT BEEN DEFINED TO TRIAL CONTROL SYSTEM.
Reason:
The CA Trial Control System has determined that a valid password has not been
recorded. You cannot use the product. You must register your copy of the product with
CA to obtain a valid password. This password must then be recorded in the password
module that is generated during the product installation process. You may use the
PASSWORD command to see the list of recorded passwords.
Action:
Obtain a valid password and include it in the password module.
QRFM098E
COMPILE/PRF HAS NOT BEEN PURCHASED.
Reason:
The CA Trial Control System has determined that the product has not been purchased.
The function you have requested can only be processed after the product has been
purchased. You must purchase your copy of the product with CA. This password must
then be recorded in the password module that is generated during the product
installation process. You may use the PASSWORD command to see the list of recorded
passwords.
Action:
Obtain a valid password and include it in the password module.
Chapter 3: PUT to QRFM 799
QRFM Messages
QRFM099E
INVALID LINE COMMAND: OPTION IS NOT SUPPORTED BY COMPILE/PRF.
Reason:
The line command that you have indicated is not defined to the product. The request
cannot be processed. Sample line commands that can be used in some options fields
include the following:
■
D (delete current line)
■
I (insert new line after current line)
■
R (repeat current line)
■
S (select the record on the current line)
Action:
Correct the name of the command and retry. To obtain a list of the supported
commands, use the HELP command while the cursor is positioned in the option field.
QRFM100E
LIST IS FULL AND CANNOT BE EXPANDED.
Reason:
The maximum number of entries are already defined in the current list. New entries
cannot be created in the list until the size of the list is reduced.
Action:
Do not attempt to insert new entries. If a new entry is required, you must also remove
an existing entry with a D (Delete) line command.
QRFM101I
LIST EXPANDED SUCCESSFULLY.
Reason:
The current list has been expanded successfully. The new entries have been created as
requested.
Action:
Normally, you should update the new entries to their desired values.
800 Message Reference Guide (PS to ZLB)
QRFM Messages
QRFM102I
PLEASE CONVERT REPLACEABLE PARMS TO HOST VARIABLES.
Reason:
Replaceable parms must be converted to host variables.
Action:
Review the SQL and replace any occurrences of CA Report Facility replaceable
parameters with host variables. Replaceable parameters are identified by the
ampersand character (&) and are not valid in static SQL. They must be replaced with
literals, constants, column names, or host variables as desired. To retain the flexibility of
the replaceable parameters , use host variables. These may use the same name.
Therefore, you need only change the ampersands to colons (:), which indicate a host
variable in static SQL. Convert dynamic SQL to static SQL by converting parms with host
variables.
This message is informational and does not indicate an error. No action is required.
QRFM103E
HOST VARIABLE VALUE EXCEEDS MAXIMUM LENGTH.
Reason:
The length of the value specified for a host variable exceeds the maximum allowable
length. When generating programs, the value must fit in the generated source code
lines and is limited to 51 characters. This is sufficient for all numeric and most
alphanumeric fields. Remember that the value, as recorded in the source code, will be
longer than the specified value if the specified value contains quotation marks that
match those used by the compiler. The program automatically duplicates such
quotation marks to assure proper compilation of the source code.
Action:
Reduce the length of the specified value of the host variable.
Chapter 3: PUT to QRFM 801
QRFM Messages
QRFM104I
PLEASE DEFINE HOST VARIABLES.
Reason:
Supply definitions of any host variables that are used in the program that is being
registered.
Note: This message is informational and does not indicate an error.
Action:
Specify each variable's type and the default value that is to be used when the program is
executed. You may add records to the list with the insert line command. When the list is
correct, press Enter to submit the program. Use the END command to cancel the
request to submit the program. Update and finalize the list.
QRFM105W
NO ITEMS FOUND THAT MATCH SEARCH CRITERIA.
Reason:
No items match the specified search criteria. The list is empty. This condition usually
occurs because you have specified search criteria that do not identify the desired
item(s). It can also occur if the desired item no longer exists.
Action:
Change the search criteria to be more general (by using wildcards).
QRFM106I
PLEASE SELECT DESIRED ITEM.
Reason:
You have been presented a list of items. You are expected to select the desired item
using the S line command. If the desired item is not listed, you may cancel the selection
process by using the END command. If the list is dynamic, you may change its contents
by entering new search criteria.
Action:
Use the S line command to select the desired item and press Enter.
802 Message Reference Guide (PS to ZLB)
QRFM Messages
QRFM107E
EITHER CHANGE THE LIST CRITERIA OR CHANGE AN OBJECT: CANNOT DO BOTH.
Reason:
The object criteria was changed and an object was selected from the list. Only one
operation can be done at a time.
Action:
If the object selected should be processed, unselect it, reenter original search criteria,
then select the object. If the criteria should be changed, unselect the object, then
change the criteria to generate a new list.
QRFM108E
INVALID QUERY: DECIMAL DATA EXCEEDS MAXIMUM COBOL PRECISION.
Reason:
The query cannot be used because it uses decimal data with a precision that exceeds
the maximum supported by COBOL. The maximum decimal precision supported by VS
COBOL II is 18. This typically occurs when the query selects a decimal data column with a
precision of more than 18. DB2 supports a maximum decimal precision of 31. This can
also occur when the query selects an expression or function that generates a decimal
result, regardless of the precision of each argument.
Action:
See the IBM DB2 SQL Reference manual for details regarding the DEC15 and DEC31
options. Convert the query to use DEC15 decimal data.
QRFM109E
UNSUPPORTED VERSION OF DB2.
Reason:
You are using an unsupported version of DB2. The program determines the version of
DB2 by loading and interrogating the DSNHDECP data-only load module that was
created during the installation of your DB2 subsystem. The version that was recorded in
this module indicates an unsupported version of DB2.
Action:
Use a supported version of DB2.
Chapter 3: PUT to QRFM 803
QRFM Messages
QRFM110E
ATTACHMENT FACILITY IS NOT SUPPORTED IN THE INDICATED ENVIRONMENT.
Reason:
You have indicated an attachment facility that is not valid for the indicated
environment. CICS programs must use the CICS Attachment Facility. Batch and TSO
programs must use the Call or TSO Attachment Facility.
Action:
Indicate an attachment facility that is supported for the indicated environment.
QRFM111E
TSO ATTACH PROGRAMS CANNOT BE EXECUTED FROM WITHIN COMPILE/PRF.
Reason:
You have requested the execution of a program that uses the TSO Attachment Facility
for DB2 services. The program uses the Call Attachment Facility. Therefore, the DSN
Command Processor is not active and the requested program cannot be executed.
Action:
Select a program that uses the Call Attachment Facility. To run a TSO Attach program,
you must execute it outside of the program.
QRFM112I
PARAMETERS HAVE BEEN SET TO REGISTERED VALUES.
Reason:
The execution parameters that are displayed on the current screen have been set with
the registered values for the specified program. You may now use these values or
change them before proceeding.
Action:
Change any parameters as desired and press Enter to process the request.
804 Message Reference Guide (PS to ZLB)
QRFM Messages
QRFM113W
MODULE IS NOT REGISTERED.
Reason:
The designated module is not registered. A module must be registered before its
registration record can be used.
Action:
Check your input. It may be that you have used the wrong name to identify the desired
module.
QRFM114E
INVALID PROGRAM.
Reason:
You have requested the execution of a program that cannot be used. The program has
attempted to invoke the program, but cannot do so. This is usually due to the use of the
incorrect program name. Check the name and ensure that the program has been fully
prepared for execution. It may be that you have generated source code for the program
but have not compiled and linked the program into an executable load module. Finally,
it may be the case that the load module has been prepared correctly but is not is a
library that has been allocated.
Action:
Specify a program that is executable and available. If you are unsure of the program
name and it is registered, you may use the registered module field to access the
registration list and obtain the name of the desired program.
QRFM115E
FILE ACCESS FAILED: INSUFFICIENT SPACE IN DATASET.
Reason:
The data set where you are attempting to store data does not have enough space to
accommodate all the output. If the data set uses secondary extents, the maximum
number of extents have probably already been used. Otherwise, the data set probably
lacks enough primary space to accommodate the output. You might have to compress
the data set or allocate it more space. Your request cannot be processed until sufficient
space is available for all the generated output.
Action:
Increase the amount of space that is available in the data set and retry.
Chapter 3: PUT to QRFM 805
QRFM Messages
QRFM116E
FILE ACCESS FAILED: DD IS ALREADY ALLOCATED.
Reason:
You have requested the allocation of a DD name that is already allocated. The DD must
be freed before it can be reallocated.
Action:
Free the specified DD and retry.
QRFM117E
FILE ACCESS FAILED: INSUFFICIENT SPACE FOR NEW DATASET.
Reason:
You have requested the creation of a new data set, but there is not enough space to
create that data set. This is usually due to a volume being full or nearly full.
Action:
Increase the amount of space available on the indicated volume(s) or reduce the
amount of space that is to be allocated to the new data set.
QRFM118E
USER IS NOT IDENTIFIED TO CICS
Reason:
The user that is attempting to access the program has not signed onto CICS. The
program requires users to identify themselves to use the correct profile and to assure
that the correct authorizations are used.
Action:
Sign onto CICS. This can be done with a standard signon transaction such as CESN.
806 Message Reference Guide (PS to ZLB)
QRFM Messages
QRFM119E
USER NOT AUTHORIZED FOR REQUESTED FUNCTION
Reason:
You have attempted to perform a function for which you are not enabled. Check your
user profile for the authorities you have been granted.
Action:
Check with your System Administrator if the function attempted should be processed.
QRFM120E
INVALID ENTRY: USE "U" OR "M"
Reason:
You have entered an invalid conditional indicator.
Action:
You must enter a valid indicator that will determine whether the condition will be met.
Enter a valid indicator:
■
U (uppercase)
■
M (mixed case)
QRFM121E
INVALID OPTION FOR VERSION/RELEASE OF PRF.
Reason:
The option specified cannot be processed due to the limitations of the version/release
of CA Report Facility specified. To remain consistent with the specified version/release
of CA Report Facility, the correct option has been entered.
Action:
A valid option has already been entered for you. You may also want to verify that the
specified version/release of CA Report Facility is the correct version/release for the
region being executed.
Chapter 3: PUT to QRFM 807
QRFM Messages
QRFM122E
SPECIFIED PAGE DEPTH DOES NOT CONTAIN ENOUGH LINES FOR USER TEXT
Reason:
You have attempted to generate a program for a form which does not fit on a single
page. Because of any of the freeform areas (headers, footers, break headers, break
footers) and their defined depths and inability to split the area between pages, the form
cannot be generated into a valid program without looping.
Action:
Increase the page depth on the batch program screen, or change any of the freeform
area definitions to fit on the defined page depth.
QRFM123I
CONVERT SUCCESSFUL; PRESS ENTER TO CONTINUE.
Reason:
The CONVERT command was entered and all the replaceable parameters were changed
to host variables.
Action:
Press the ENTER key to continue.
QRFM401W
NO RECORDS SATISFY THE QUERY CONDITIONS
Reason:
There were no records returned by the query that was executed. There is no data to
process.
Action:
Check the conditions used by the query to assure the proper results, if you believe that
data records should be returned.
Note: This message is used only by generated programs
808 Message Reference Guide (PS to ZLB)
QRFM Messages
QRFM402E
PROGRAM INVOKED WITH INVALID PARAMETER LIST
Reason:
You have attempted to invoke a program without supplying a parameter list in the
required form. The program cannot be executed.
Action:
Change the parameter list to the required form.
Note: This message is used only by generated programs
QRFM403E
DSNALI FAILED: FUNC=ffffffffffff; RTN=99999999; RSN=xxxxxxxx
Reason:
The DB2 attachment function indicated in this message has failed. The return code
(99999999) and the reason code in hexadecimal form are reported and can be
referenced in the DB2 Messages and Codes manual.
Action:
Determine the cause of the DB2 failure and correct the cause.
Note: This message is used only by generated programs
QRFM404E
PROGRAM INVOKED WITH INVALID DB2 ATTACHMENT PARAMETERS
Reason:
You have attempted to invoke a program without supplying the required DB2
attachment parameters. The program cannot be executed.
Action:
Supply the required parameters as documented in the program.
Note: This message is used only by generated programs
Chapter 3: PUT to QRFM 809
QRFM Messages
QRFM405E
AN SQL ERROR HAS OCCURRED. SQLCODE = -999.
Reason:
An SQL error has occurred. The SQLCODE that was returned from DB2 is also reported.
The program cannot continue to execute. The SQLCODE can be translated using the DB2
Messages and Codes manual.
Action:
Determine and correct the DB2 problem.
Note: This message is used only by generated programs
QRFM406E
HOST VARIABLE VALUE EXCEEDS MAXIMUM ALLOWABLE SCALE
Reason:
The value cannot be assigned to the host variable because it exceeds the maximum
allowable scale of the variable. This applies to decimal data and indicates that the
number of digits following the decimal point exceeds the limit that is indicated by the
variable type.
Action:
Reduce the number of digits following the decimal point.
Note: This message is used only by generated programs
QRFM407E
UNABLE TO PROCESS SPF FUNCTION: ffffffff
Reason:
The SPF function identified in this message cannot be processed. The program cannot
continue to execute.
Action:
Ensure the SPF environment has been established correctly to support the program.
Note: This message is used only by generated programs
810 Message Reference Guide (PS to ZLB)
QRFM Messages
QRFM408E
UNABLE TO INVOKE SUPPLEMENTARY PROGRAM: pppppppp. COND=-999999999.
Reason:
The required program pppppppp which is distributed as a supplementary program,
cannot be invoked. The program cannot continue to execute. The CICS condition code
that identifies the problem is also reported.
Action:
Prepare and supply the supplementary program.
QRFM409E
PROGRAM INVOKED WITH INVALID COMMAREA
Reason:
You have attempted to invoke a program without supplying a commarea in the required
form. The program cannot be executed.
Action:
Change the commarea to the required form.
QRFM410I
PROGRAM COMPLETED SUCCESSFULLY
Reason:
The program has completed successfully.
Action:
This message is informational only. Continue as desired.
Chapter 3: PUT to QRFM 811
QRFM Messages
QRFM411E
HOST VARIABLE OVERRIDES ARE NOT SPECIFIED IN VALID FORMAT
Reason:
The host variable overrides supplied to the program are not specified in the valid
format. Overrides must be specified in the following form:
nnnnnnnn = vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
nnnnnnnn
Indicates the variable name and appears in column 1.
=
Indicates the equality sign and appears in column 9
vvv…
Indicates the override value and appears in column 10.
Action:
Correct the override specifications.
QRFM412E
DYNAMIC STORAGE COULD NOT BE ACQUIRED
Reason:
An attempt has been made to acquire dynamic storage that is required by the program.
The request could not be satisfied. The program cannot continue to execute.
Action:
Run the program in a larger region or change the conditions used by the query to reduce
the amount of data that needs to be processed.
QRFM413E
DYNAMIC STORAGE COULD NOT BE RELEASED
Reason:
An attempt has been made to release dynamic storage that was acquired by the
program. The request could not be satisfied. The program cannot continue to execute.
Action:
Correct the cause of the failure and rerun the program.
812 Message Reference Guide (PS to ZLB)
QRFM Messages
QRFM414E
HOST VARIABLE VALUE CONTAINS AN INVALID CHARACTER
Reason:
The value cannot be assigned to the host variable because it contains an invalid
character. This usually indicates the use of a non-numeric character (other than a sign or
decimal point) for numeric data.
Action:
Change the value to use only valid characters.
QRFM415E
HOST VARIABLE VALUE EXCEEDS MAXIMUM ALLOWABLE PRECISION
Reason:
The value cannot be assigned to the host variable because it exceeds the maximum
allowable precision of the variable. For character data, this indicates that there are too
many characters. For numeric data, this indicates that there are too many digits.
Action:
Reduce the number of characters used in the value.
QUI27I
ENTER SUBMIT TO EXECUTE THE JOB.
Action:
Enter SUBMIT to execute the job. Wait for the execution of this job to complete before
executing the next step.
Chapter 3: PUT to QRFM 813
Chapter 4: RAE to RAW
RAE Messages
Messages with the RAE prefix are generated from CA Database Analyzer for DB2 and CA
Recovery Analyzer.
RAE00001
RECOVERY ANALYZER IS NOT LICENSED FOR THIS CPU. CONTACT CUSTOMER SUPPORT
FOR ASSISTANCE.
Reason:
You need a license to run this product.
RAE00003
GENERATION INCOMPLETE DUE TO EDIT ERRORS.
Reason:
An error was detected during batch analysis. CA Recovery Analyzer will not build the JCL
because the PRA parmlib field OVERRIDE_ERRORS is set to N.
Action:
None.
RAE00004
INVALID OVERRIDE INDICATOR IN THE PRA PARMLIB.
Reason:
If an error is detected during batch analysis, CA Recovery Analyzer checks the override
indicator. It was determined to be invalid. Processing is aborted.
Action:
Verify the setting of the override indicator in the PRA parmlib.
Chapter 4: RAE to RAW 815
RAE Messages
RAE00005
LENGTH OF RECORD MISMATCH ERROR WHILE PROCESSING ZPARMS.
Reason:
A DB2 level consistency check failed while reading the BSDS. The BSDS is invalid.
RAE00006
GET FAILURE DURING A BSDS READ IN ZPARM PROCESSING.
Reason:
MVS detected a read error while CA Recovery Analyzer was examining the BSDS.
RAE00007
BSDS FILE OPEN FAILURE DURING ZPARM PROCESSING.
Reason:
CA Recovery Analyzer could not open the BSDS.
Action:
For assistance, contact CA Support at http://ca.com/support.
RAE00008
A GENERATE CONTROL BLOCK REQUEST FAILED PROCESSING ZPARMS.
Reason:
Internal initialization processing necessary to read the BSDS failed.
RAE00009
THE ALLOCATION OF THE BSDS DURING ZPARM PROCESSING FAILED. Reason:
#1=Reason:1, Reason: #2=Reason:2.
Reason:
The attempt to allocate the BSDS to the session failed. The MVS dynamic allocation
error reasons are displayed.
816 Message Reference Guide (PS to ZLB)
RAE Messages
RAE00010
I/O ERROR WHILE READING THE MASTER CATALOG.
Reason:
While scanning the MVS master catalog, an I/O error occurred.
RAE00011
I/O ERROR WHILE READING THE USER CATALOG.
Reason:
While scanning an MVS user catalog, an I/O error occurred.
RAE00012
COULD NOT CONNECT TO THE DESIRED DB2 SUBSYSTEM.
Reason:
The batch process could not make the connection to the desired DB2 subsystem.
RAE00013
ERROR ATTEMPTING TO DISCONNECT FROM THE DB2 SUBSYSTEM.
Reason:
The attempt to break the connection to the desired DB2 subsystem failed.
RAE00014
PROGRAM pgmname ABNORMALLY TERMINATING.
Reason:
The indicated program encountered a condition that prevents further processing from
continuing.
RAE00015
FILE TAILOR ALREADY IN PROGRESS.
Reason:
An internal sequencing error occurred in Batch Processor/JCL generation.
Chapter 4: RAE to RAW 817
RAE Messages
RAE00016
FILE TAILOR OUTPUT FILE IS NOT ALLOCATED.
Reason:
An internal sequencing error occurred in Batch Processor/JCL generation.
RAE00017
FILE TAILOR OUTPUT FILE IS IN USE.
Reason:
The data set requested to be loaded with the CA Recovery Analyzer generated JCL is
allocated by another job or user in the MVS system.
Action:
Verify availability of the output data set.
RAE00018
FILE TAILOR OPEN SEVERE ERROR.
Reason:
The data set requested to be loaded with the CA Recovery Analyzer generated JCL could
not be opened.
Action:
Verify availability of the output data set.
RAE00019
FILE TAILOR INCLUDE - MEMBER DOES NOT EXIST. SKELETON MEMBER: member.
Reason:
An internal error occurred in CA Recovery Analyzer batch processing.
Action:
For assistance, contact CA Support at http://ca.com/support.
818 Message Reference Guide (PS to ZLB)
RAE Messages
RAE00020
FILE TAILOR INCLUDE - MEMBER IN USE. SKELETON MEMBER: member.
Reason:
An internal error occurred in CA Recovery Analyzer batch processing.
Action:
For assistance, contact CA Support at http://ca.com/support.
RAE00021
FILE TAILOR INCLUDE - DATA TRUNCATION. SKELETON MEMBER: member.
Reason:
An internal error occurred in CA Recovery Analyzer batch processing. A generated JCL
line may have exceeded the maximum length of 72 characters and was therefore
truncated on the right side.
RAE00022
FILE TAILOR INCLUDE - SEVERE ERROR. SKELETON MEMBER: member.
Reason:
An internal error occurred in CA Recovery Analyzer batch processing.
Action:
For assistance, contact CA Support at http://ca.com/support.
RAE00023
FILE TAILOR CLOSE - FILE IS NOT OPEN.
Reason:
An internal error occurred in CA Recovery Analyzer batch processing.
Action:
For assistance, contact CA Support at http://ca.com/support.
Chapter 4: RAE to RAW 819
RAE Messages
RAE00024
FILE TAILOR CLOSE - FILE IS IN USE.
Reason:
An internal error occurred in CA Recovery Analyzer batch processing.
Action:
Verify availability of the output data set.
For assistance, contact CA Support at http://ca.com/support.
RAE00025
FILE TAILOR CLOSE - FILE IS NOT ALLOCATED.
Reason:
An internal error occurred in CA Recovery Analyzer batch processing.
RAE00026
FILE TAILOR CLOSE - SEVERE ERROR.
Reason:
An internal error occurred in CA Recovery Analyzer batch processing.
RAE00027
DB2 SUBSYSTEM PARAMETER REQUIRED - PROGRAM ABORTING.
Reason:
The desired DB2 subsystem parameter on the JCL execution card was not specified.
Execution was aborted.
Action:
Enter the desired DB2 subsystem in the execution card or rebuild the JCL.
RAE00028
LINE LIMIT OF 10 EXCEEDED ON COMMAND.
Reason:
The number of lines in the current command being processed by the batch command
processor exceeded the limit of 10.
820 Message Reference Guide (PS to ZLB)
RAE Messages
RAE00029
INVALID SQLCODE EXECUTING DYNAMIC COMMAND. SQLCODE=abendsc.
Reason:
The batch command processor received an invalid return code from the current DB2
subsystem.
RAE00030
DB2 CONNECT FAILED TO SUBSYSTEM: ssid.
Reason:
The batch process could not connect to the desired DB2 subsystem.
RAE00031
DB2 OPEN FAILED TO SUBSYSTEM ssid PLAN planname.
Reason:
The CA Recovery Analyzer plan used by batch processing could not be opened to the
desired DB2 subsystem.
Action:
Verify plan availability.
RAE00032
RETURN CODE retcode1 - Reason: CODE retcode2 message.
Reason:
This message displays additional diagnostic information available for certain error
conditions.
RAE00033
PROGRAM PRA#ARCH ABNORMALLY TERMINATING.
Reason:
An abnormal condition occurred in the batch disaster recovery archive log processing
program.
Chapter 4: RAE to RAW 821
RAE Messages
RAE00034
MAX NBR OF LOGS COPY IS NOT NUMERIC - CORRECT AND RESUBMIT.
Reason:
The CA Recovery Analyzer profile variable that contains the maximum number of
archive logs to back up was not valid.
Action:
Verify the contents of the CA Recovery Analyzer profile.
RAE00035
MATCHING LOGDSN NODE NOT FOUND FOR DATASET datasetname.
Reason:
CA Recovery Analyzer tried to copy a secondary archive log DSN that does not exist.
Action:
Verify the existence of the secondary archive log DSN.
RAE00038
PRA#ARCH - GETMAIN FAILURE ON SSID NODE.
Reason:
An internal error occurred in the CA Recovery Analyzer disaster recovery archive log
process.
RAE00039
PRA#ARCH - GETMAIN FAILURE ON ARCHIVE LOG NODE.
Reason:
An internal error occurred in the CA Recovery Analyzer disaster recovery archive log
process.
RAE00040
PROGRAM PRA#CHKP IS ABNORMALLY TERMINATING.
Reason:
An abnormal condition occurred in the batch disaster recovery checkpoint processing
program.
822 Message Reference Guide (PS to ZLB)
RAE Messages
RAE00041
PRA#CHKP - COULD NOT OPEN CHECKPOINT FILE FOR INPUT.
Reason:
The CA Recovery Analyzer checkpoint program could not open the checkpoint file.
Action:
Verify the availability of the PRA parmlib checkpoint restart file.
RAE00042
PRA#CHKP - OPEN FAILURE ON OPENING THE BSDS FILE.
Reason:
The CA Recovery Analyzer checkpoint program could not open the BSDS file.
Action:
Verify the availability of the BSDS.
RAE00043
PRA#CHKP - COULD NOT OPEN CHECKPOINT FILE FOR OUTPUT.
Reason:
The CA Recovery Analyzer checkpoint program could not open the checkpoint file to
update the contents.
Action:
Verify the availability of the PRA parmlib checkpoint restart file.
RAE00044
* * * * SYNAD EXIT INFORMATION * * * *
synmess1
synmess2
INPUT BUFFER ADDRESS IS synbufad
LENGTH OF READ WAS synlngth
Reason:
This message displays additional information under certain abnormal circumstances.
Chapter 4: RAE to RAW 823
RAE Messages
RAE00045
PRA#CMDS - BAD RETURN CODE FROM DB2 ON EXECUTED COMMAND - ABORTING.
Reason:
A STOP or START command issued to DB2 from the CA Recovery Analyzer batch
command processor was not successful.
Action:
Verify that the DB2 subsystem is available.
RAE00046
PRA#CMDS - STOP DATABASE/TABLESPACE WAIT TIME HAS EXCEEDED THE PRA
PARMLIB LIMIT - TRY AGAIN LATER.
Reason:
A STOP command was issued against a tablespace multiple times, but the space never
came out of stop pending status.
Action:
Verify availability of the tablespace, increase the Wait Time In Seconds After Stop and
Number of Times to Retry the Stop fields in the PRA parmlib.
RAE00047
PRA#CMDS - SYSPRINT DD STATEMENT MISSING - SYNAD EXIT ABORTED.
Reason:
CA Recovery Analyzer attempted to write additional diagnostic information, but the
SYSPRINT DD output card was missing.
Action:
Verify that the SYSPRINT DD statement is present.
RAE00048
PRA#DATA - I/O ERROR OR NO DATA IN DD PRA#DATA.
Reason:
Batch analysis detected an empty input stream for the PRA#DATA parameters.
Action:
Verify the presence of the PRA#DATA instream parameters.
824 Message Reference Guide (PS to ZLB)
RAE Messages
RAE00049
PROGRAM PRA#DCAT ABNORMALLY TERMINATING.
Reason:
An abnormal condition occurred in the batch disaster recovery DB2 catalog recreation
processing program.
RAE00050
PRA#DCAT - GETMAIN FAILURE ON SSID NODE.
Reason:
An internal error occurred in the disaster recovery DB2 catalog recreation processing
program.
RAE00051
PRA#DSNJ - GETMAIN FAILURE ON DATASET NODE.
Reason:
An internal error occurred in the batch disaster recovery “other data set” processing
program.
RAE00052
PROGRAM PRA#DSNJ ABNORMALLY TERMINATING.
Reason:
An abnormal condition occurred in the batch disaster recovery “other data set”
processing program.
Chapter 4: RAE to RAW 825
RAE Messages
RAE00053
INVALID PARM - SHOULD BE A DB2 SUBSYSTEM, A COMMA, THE NUMBER OF LOAD
FILES TO WRITE TO, AND WHETHER OR NOT TO USE SQL ACCESS FOR RETRIEVING THE
DB2 CATALOG INFORMATION. ABORTING.
Reason:
The parm passed to the step was invalid. The generated JCL should contain the following
after the EP= program name: a one- to four-character DB2 subsystem name, a comma, a
one- to two-digit number of tasks to use, another comma, and a Y or N to specify
whether to use SQL access to retrieve DB2 catalog information.
Action:
Verify the presence of the parameter.
RAE00054
INVALID PARM - THE MAXIMUM NUMBER OF TASKS PARAMETER IS MISSING.
ABORTING.
Reason:
The parameter that specifies the number of catalog tasks to use is missing from the
execution card.
Action:
Verify the presence of the parameter.
RAE00055
INVALID PARM - INVALID CHARACTER IN THE NUMBER OF TASKS TO ATTACH.
ABORTING.
Reason:
The parameter that specifies the number of catalog tasks to use contains a non-numeric
character and cannot be interpreted.
Action:
Verify the validity of the parameter.
826 Message Reference Guide (PS to ZLB)
RAE Messages
RAE00056
INVALID PARM - NUMBER OF TASKS TO ATTACH PARAMETER NOT IN THE RANGE OF
1-25. ABORTING.
Reason:
The parameter that specifies the number of catalog tasks to use is outside the range of 1
to 25. Too many tasks will result in MVS catalog request errors.
Action:
Verify the validity of the parameter.
RAE00057
INVALID RETURN CODE UNLOADING SYSTEM CATALOG. CHECK PTIMSG DD AND
ST01MSG DD FOR ADDITIONAL MESSAGES.
Reason:
An internal error was encountered reading the DB2 catalog.
Action:
Check PTIMSG DD and ST01MSG DD for additional messages.
RAE00058
INVALID COMPARE BETWEEN SYSINDEXES AND SYSTABLEPART.
Reason:
An internal error was encountered within the CA Recovery Analyzer VTOC table load
process.
RAE00059
PRA#FULD - GETMAIN FAILURE LOADING READ ONLY SHARE DATABASE.
Reason:
An internal error occurred in the batch DB2 catalog unload processing program.
RAE00060
PRA#FULD - GETMAIN FAILURE LOADING ELIMINATE DATABASE.
Reason:
An internal error occurred in the batch DB2 catalog unload processing program.
Chapter 4: RAE to RAW 827
RAE Messages
RAE00061
INVALID RETURN CODE FROM SORT. ABORTING.
Reason:
The sort program encountered an error.
RAE00062
PRA#ICFA - VALID PARM VALUES FOR THE SMS INDICATOR ARE 'Y' AND 'N.'
ABORTING.
Reason:
The MVS ICF catalog scan program detected an invalid parameter value for the SMS
scan YES/NO switch.
Action:
Verify the validity of the parameter on the execution card.
RAE00063
PRA#ICFA - PARM FORMAT INVALID. SHOULD BE A 1-4 CHARACTER SUBSYSTEM ID, A
COMMA, AND A Y/N SMS INDICATOR. ABORTING.
Reason:
The parm passed to the step was invalid. The generated JCL should contain the following
after the EP= program name: a one- to four-character DB2 subsystem name, a comma,
and a single character for the SMS check YES/NO flag.
Action:
Verify the presence of the parameter.
RAE00064
PRA#ICFL - NOT ENOUGH STORAGE FOR LOADtasknumber DCB. ABORTING.
Reason:
The MVS ICF catalog scan program could not acquire enough storage to continue
processing.
Action:
Reduce the number of tasks used in the unload process.
828 Message Reference Guide (PS to ZLB)
RAE Messages
RAE00065
PRA#ICFL - NOT ENOUGH STORAGE FOR THE EODAD= ROUTINE FOR LOADtasknumber.
ABORTING.
Reason:
The MVS ICF catalog scan program could not acquire enough storage to continue
processing.
Action:
Reduce the number of tasks used in the unload process.
RAE00066
PRA#ICFL - NOT ENOUGH STORAGE FOR FINDtasknumber DCB. ABORTING.
Reason:
The MVS ICF catalog scan program could not acquire enough storage to continue
processing.
Action:
Reduce the number of tasks used in the unload process.
RAE00067
PRA#ICFL - NOT ENOUGH STORAGE FOR ERRRtasknumber DCB. ABORTING.
Reason:
The MVS ICF catalog scan program could not acquire enough storage to continue
processing.
Action:
Reduce the number of tasks used in the unload process.
Chapter 4: RAE to RAW 829
RAE Messages
RAE00068
PRA#ICFL - NOT ENOUGH STORAGE FOR THE GET/PUT ROUTINES IN TASK
#tasknumber. ABORTING.
Reason:
The MVS ICF catalog scan program could not acquire enough storage to continue
processing.
Action:
Reduce the number of tasks used in the unload process.
RAE00069
PRA#ICFL - NOT ENOUGH STORAGE FOR THE PRA#LOAD RECORD IN TASK
#tasknumber. ABORTING.
Reason:
The MVS ICF catalog scan program could not acquire enough storage to continue
processing.
Action:
Reduce the number of tasks used in the unload process.
RAE00070
PRA#ICFL - NOT ENOUGH STORAGE FOR THE PRAROUT RECORD IN TASK #tasknumber.
ABORTING.
Reason:
The MVS ICF catalog scan program could not acquire enough storage to continue
processing.
Action:
Reduce the number of tasks used in the unload process.
830 Message Reference Guide (PS to ZLB)
RAE Messages
RAE00071
PRA#ICFL - NOT ENOUGH STORAGE FOR THE LOCATE ERROR RECORD IN TASK
#tasknumber. ABORTING.
Reason:
The MVS ICF catalog scan program could not acquire enough storage to continue
processing.
Action:
Reduce the number of tasks used in the unload process.
RAE00072
PRA#ICFL - NOT ENOUGH STORAGE FOR THE QSAM SAVE AREA IN TASK #tasknumber.
ABORTING.
Reason:
The MVS ICF catalog scan program could not acquire enough storage to continue
processing.
Action:
Reduce the number of tasks used in the unload process.
RAE00073
PRA#MAIN - DRIVER PROGRAM IS TO BE RUN IN BATCH MODE ONLY.
Reason:
The CA Recovery Analyzer batch services driver program was somehow executed
outside of JCL.
RAE00074
PRA#MAIN - INVALID RETURN CODE FROM RSPINIT.
Reason:
An internal error occurred in the CA Recovery Analyzer batch services driver
initialization code.
Chapter 4: RAE to RAW 831
RAE Messages
RAE00075
PRA#MAIN - 'RECOVERY POINT (R)' SPECIFIED, BUT THE 'RECOVER RBA ()' VALUE IS
NOT PRESENT.
Reason:
An illogical condition arose where a recovery point was specified as TO RBA, but the RBA
to recover to was missing.
Action:
Verify that the RBA parameters are set correctly on the global or individual options on
the strategy.
RAE00076
PRA#MAIN - STRATEGY DOES NOT HAVE A VALID JOBCARD. PROGRAM ABORTING
UNTIL JOBCARD SUPPLIED.
Reason:
The JCL lines entered on the strategy global options were invalid or missing.
Action:
Verify the validity of the JCL lines on the strategy global options screen.
RAE00077
PRA#QUIE - STRATEGY CREATOR/NAME IS INCOMPLETE. ABORTING.
Reason:
The strategy name and/or creator name specified in the PRA#DATA input stream to the
batch services driver was incomplete.
Action:
Verify the presence of both fields.
RAE00078
PRA#QUIE - INTERNAL ERROR RETRIEVING STRATEGY. ABORTING.
Reason:
The program could not find the strategy saved in DB2.
Action:
Regenerate the batch job to analyze the strategy with an existing strategy.
832 Message Reference Guide (PS to ZLB)
RAE Messages
RAE00079
PRA#QUIE - INTERNAL ERROR - NO QUIESCE POINT FOUND FOR SPACE. ABORTING.
Reason:
The strategy calls for a tablespace to be recovered to a selected quiesce point, but that
point does not exist.
RAE00080
MAXIMUM SUBSYSTEM PARM LENGTH IS 4 CHARACTERS.
Reason:
The program detected an invalid DB2 subsystem parm.
Action:
Verify the validity of the DB2 subsystem parm on the execution card.
RAE00081
PRA#REFT - INVALID PARM VALUE GIVEN.
Reason:
The program received an invalid parm from the JCL execution card.
Action:
Verify the validity of the DB2 subsystem parm.
RAE00082
PRA#REPT - MAXIMUM SUBSYSTEM PARM LENGTH IS 4 CHARACTERS.
Reason:
The program detected a DB2 subsystem parm that exceeded four characters. The
subsystem ID can only be one to four characters.
Action:
Verify the validity of the DB2 subsystem parm.
Chapter 4: RAE to RAW 833
RAE Messages
RAE00083
PRA#REPT - INVALID PARM VALUE GIVEN.
Reason:
The program received an invalid parameter from the JCL execution card.
Action:
Verify the validity of the DB2 subsystem parameter.
RAE00084
PRA#REPT - INVALID RETURN CODE FROM SORT1. ABORTING.
Reason:
While organizing the first report for output, an unexpected return code was received
from the sort program.
RAE00085
PRA#REPT - Invalid return code X'rc' from SORT2.
The Locate Failure... Report cannot be created.
See PRA#SRT2 listing for sort messages that describe the error.
Reason:
While organizing data for the Locate Failure Table/Index Spaces Report, CA Recovery
Analyzer received an unexpected return code from the sort program. Processing
continues, but this report is not created.
Note: PRA#REPT is the job step that the PRA#LOAD batch job uses to produce error
reports. For more information about PRA#LOAD, see the CA Recovery Analyzer User
Guide.
Action:
See the PRA#SRT2 listing for additional messages regarding this sort error. Your
PRA#LOAD job specifies the DD name where this listing is written.
RAE00086
PRA#REPT - INVALID RETURN CODE FROM SORT3. ABORTING.
Reason:
While organizing the third report for output, an unexpected return code was received
from the sort program.
834 Message Reference Guide (PS to ZLB)
RAE Messages
RAE00087
INVALID SQLCODE ON SELECT OF PTI.PTRA_VTOC_0200. SQLCODE IS sqlcode.
Reason:
The program attempted to read the PRA#LOAD VTOC table for data. The request failed.
Action:
Verify the availability of the DB2 subsystem.
RAE00088
INVALID SQLCODE DELETING PRA#LOAD TIMESTAMP. SQLCODE IS sqlcode.
Reason:
The PRA#LOAD job attempted to update the timestamp displayed on the CA Recovery
Analyzer primary options panel, but the attempt failed.
Action:
Verify availability of the DB2 subsystem.
RAE00089
INVALID SQLCODE INSERTING PRA#LOAD TIMESTAMP. SQLCODE IS sqlcode.
Reason:
The PRA#LOAD job attempted to update the timestamp displayed on the CA Recovery
Analyzer primary options panel, but the attempt failed.
Action:
Verify availability of the DB2 subsystem .
RAE00090
PROGRAM PRA#RPRB ABNORMALLY TERMINATING.
Reason:
The program detected an illogical condition and is aborting.
Chapter 4: RAE to RAW 835
RAE Messages
RAE00091
PRA#RPRB - NO RP/RB ICBACKUP TYPES EXIST IN SYSIBM.SYSCOPY.
Reason:
The CA Recovery Analyzer disaster recovery image copy backup program detected no
recovery site-type image copies in the SYSCOPY DB2 database.
Action:
Verify that the image copies taken for the desired tablespaces were marked as
“recovery site.”
RAE00092
PRA#RPRB - GETMAIN FAILURE CHECKING FOR DUPLICATE VOLUME ON STOGRP.
Reason:
The program could not acquire the necessary storage to continue processing.
RAE00093
PRA#UCAT - PROGRAM ABNORMALLY TERMINATING.
Reason:
The program detected an illogical condition and is now aborting.
RAE00094
PRA#UCAT - ERROR ALLOCATING ISPWRK1 WORK FILE DD.
Reason:
The program attempted to allocate a file for use in building the user catalog restore JCL.
The attempt failed.
RAE00095
PRA#UCAT - INVALID RETURN CODE FOR MVS CATALOG SCAN.
Reason:
The attempt to locate all the user catalogs on the current MVS complex failed.
Action:
Increase the PRA parmlib value CATALOG_BUFFER_SIZE.
836 Message Reference Guide (PS to ZLB)
RAE Messages
RAE00096
PRA#VOLS - DYNAMIC ALLOCATION OF THE SORT OUTPUT FILE FAILED.
Reason:
The program attempted to allocate a work file to sort the results of the volume scan.
The attempt failed.
RAE00097
PRA#VOLS - DYNAMIC ALLOCATION OF THE SORT INPUT FILE FAILED.
Reason:
The program attempted to allocate a work file to sort the results of the volume scan.
The attempt failed.
RAE00098
PRA#VOLS - THE PRAREPRT DD IS MISSING FROM THE JOB STEP.
Reason:
The DD used to hold the resulting volume scan report was not present in the JCL.
Action:
Verify the presence of the DD in the JCL.
RAE00099
PRA#VOLS - THE PRAREPRT DD COULD NOT BE OPENED.
Reason:
The DD used to hold the resulting volume scan report could not be opened.
Action:
Verify the presence of the DD in the JCL.
RAE00100
PRA#VOLS - INVALID RETURN CODE RETURNED FROM THE ICF SCAN. RETURN CODE
FROM SCAN=rcode.
Reason:
The internal scan used to find all the data sets on the selected volume in all the MVS
complex's catalogs failed.
Chapter 4: RAE to RAW 837
RAE Messages
RAE00101
PRA#VOLS - OPEN OF THE SORT OUTPUT FILE FAILED IN THE FILL ROUTINE.
Reason:
The program attempted to open the sort work file, but failed.
RAE00102
PRA#VOLS - INVALID RETURN CODE FROM SORT1. ABORTING.
Reason:
An unexpected return code was received from the sort program in building the data set
list.
RAE00103
PRA#VOLS - OPEN OF THE SORT1 FILE FOR INPUT FAILED.
Reason:
The program could not open the sort work file for input to write the report.
RAE00104
PRA#XLAT - FIRST RECORD IN GROUP FROM INPUT FILE IS NOT A HEADER RECORD.
Reason:
The input tablespace or tablespace backup contained an unknown format first record.
Action:
Verify the validity of the input tablespace or tablespace backup.
RAE00105
PRA#XLAT - AN ERROR OCCURRED READING THE OS TYPE INPUT FILE.
Reason:
After determining that the input tablespace was a non-VSAM file, a read attempt failed.
Action:
Verify the validity of the input tablespace backup.
838 Message Reference Guide (PS to ZLB)
RAE Messages
RAE00106
PRA#XLAT - AN ERROR OCCURRED READING THE VSAM TYPE INPUT FILE.
Reason:
After determining that the input tablespace was a VSAM file, a read attempt failed.
Action:
Verify the validity of the input tablespace.
RAE00107
PRA#XLAT - CANNOT DETERMINE PROPER OBJECT ID FROM INPUT FILE.
Reason:
The translate program determined that there were multiple OBIDs within the input file
with VARCHAR type fields. The translate program can no longer correlate old OBIDs to
the new OBIDs. Automatic translation not possible.
RAE00108
PRA#XLAT - MULTIPLE OBIDS HAVE THE SAME LENGTH. CANNOT CORRELATE.
Reason:
The translate program determined that at least two OBIDs within the input file had
identical length rows. The translate program can no longer correlate old OBIDs to the
new OBIDs. Automatic translation not possible.
RAE00109
PRA#XLAT - SELECTED DATABASE/TABLESPACE NO LONGER EXISTS IN DB2.
Reason:
The translate program checked the DB2 catalog for the specified tablespace to
determine the new DBIDs and PGIDs, but the space was not found.
Action:
Verify that the space exists in the DB2 subsystem.
Chapter 4: RAE to RAW 839
RAE Messages
RAE00110
PRA#XLAT - SELECTED TABLE NO LONGER EXISTS IN DB2.
Reason:
The translate program checked the DB2 catalog for the specified table to obtain the new
OBID, but the table was not found.
Action:
Verify that the table exists in the DB2 subsystem.
RAE00111
PRA#XLAT - THE NUMBER OF OBIDS IN THE INPUT FILE DOES NOT MATCH THE
NUMBER OF OBIDS FOR THE TABLE IN THE DB2 CATALOG.
Reason:
The translate program found a different number of OBIDs in the input file than on the
DB2 catalog for the tablespace.
Action:
Verify that the input file is consistent with the specified database or tablespace.
RAE00112
PRA#XLAT - COULD NOT FIND A MATCHING RECORD LENGTH OBID IN THE DB2
CATALOG.
Reason:
While scanning the DB2 catalog looking for the new OBID for a table, a matching row
length OBID could not be found.
Action:
Verify that the input file is consistent with the specified database or tablespace.
RAE00113
PRA#XLAT - AN OBID FROM THE DB2 CATALOG COULD NOT BE MATCHED.
Reason:
An extra OBID was detected for the new definition of the tablespace in the DB2 catalog.
Action:
Verify that the input file is consistent with the specified database or tablespace.
840 Message Reference Guide (PS to ZLB)
RAE Messages
RAE00114
PRA#XLAT - AN OBID EXISTED IN THE INPUT FILE THAT WAS NOT FOUND WITHIN
SYSIBM.SYSTABLES.
Reason:
An extra OBID was detected from the input file that could not be matched to a table in
the DB2 catalog.
Action:
Verify that the input file is consistent with the specified database or tablespace.
RAE00115
PRA#XLAT - INVALID RETURN CODE FROM THE DSN1COPY PROGRAM. CHECK
DSN1COPY MESSAGES FOR EXPLANATION.
Reason:
After building the control cards necessary to do the image copy translation, the
DSN1COPY program was called and returned an unexpected return code.
Action:
Verify that the control cards and parameter string were built properly by examining the
output.
RAE00116
PRA#CHKP - DYNAMIC ALLOCATION OF THE CHECKPOINT RESTART FILE ABENDED IN
MVS. POSSIBLE SECURITY VIOLATION.
Reason:
The allocation of the PRA parmlib checkpoint restart file caused an MVS abend.
Action:
Verify the availability of the PRA parmlib checkpoint restart file.
Chapter 4: RAE to RAW 841
RAE Messages
RAE00117
PRA#CHKP - DYNAMIC ALLOCATION OF THE CHECKPOINT RESTART FILE FAILED.
Reason:
The allocation of the PRA parmlib checkpoint restart file was not successful.
Action:
Verify the availability of the PRA parmlib checkpoint restart file.
RAE00118
PRA#CHKP - OPENING OF THE CHECKPOINT RESTART FILE FOR INPUT ABENDED IN
MVS. POSSIBLE SECURITY VIOLATION.
Reason:
When the program attempted to access the PRA parmlib checkpoint restart file, an MVS
abend occurred.
Action:
Verify the availability of the PRA parmlib checkpoint restart file.
RAE00119
PRA#CHKP - OPENING OF THE CHECKPOINT RESTART FILE FOR OUTPUT ABENDED IN
MVS. POSSIBLE SECURITY VIOLATION.
Reason:
When the program attempted to write to the PRA parmlib checkpoint restart file, an
MVS abend occurred.
Action:
Verify the availability of the PRA parmlib checkpoint restart.
RAE00121
PRA#ARCL - NO ARCHIVE LOGS WERE FOUND IN THE BSDS FOR SUBSYSTEM ssid.
ABORTING.
Reason:
Before issuing the DB2 ARCHIVE LOG command, the DB2 BSDS contained no other
archive logs. This is an illogical condition.
842 Message Reference Guide (PS to ZLB)
RAE Messages
RAE00122
PRA#ARCL - INVALID RETURN CODE FROM DYNAMIC COMMAND PROCESSOR.
Reason:
The attempt to issue the DB2 ARCHIVE LOG command was not successful.
Action:
Verify the availability of the DB2 subsystem.
RAE00123
PROGRAM PRA#ARCL ABNORMALLY TERMINATING.
Reason:
The program detected an illogical condition and is aborting.
RAE00124
THE BSDS READER CANNOT FIND THE SPECIFIED SUBSYSTEM IN SETUP.
Reason:
The subsystem parameter passed to the batch program was not found in the CA SETUP
parmlib member.
RAE00125
PRA#VVDS - GETMAIN FAILURE ON VVDS NODE.
Reason:
A GETMAIN request to MVS could not be satisfied.
RAE00126
PRA#XLAT - COMPRESSION IS INVOLVED WITH THIS SPACE WHICH MAKES
AUTOMATIC DETERMINATION OF THE NEW OBIDS IMPOSSIBLE.
Reason:
CA Recovery Analyzer cannot automatically determine the new OBID because DB2
compression has been used on the space.
Chapter 4: RAE to RAW 843
RAE Messages
RAE00128
THE ALLOCATION OF ARCHIVE LOG #1 FAILED. CHECK THE ERROR REPORT FOR
DETAILS.
Reason:
The local site archive log #1 cannot be located.
Action:
Check the CA Recovery Analyzer error log (PRAERRPT DD) to determine why the archive
log cannot be found.
RAE00129
THE ALLOCATION OF ARCHIVE LOG #2 FAILED. CHECK THE ERROR REPORT FOR
DETAILS.
Reason:
The local site archive log #2 cannot be located.
Action:
Check the CA Recovery Analyzer error log (PRAERRPT DD) to determine why the archive
log cannot be found.
RAE00130
THE ALLOCATION OF THE INPUT ARCHIVE LOG FAILED. CHECK THE ERROR REPORT FOR
DETAILS.
Reason:
The input archive log cannot be opened.
Action:
Check the CA Recovery Analyzer error log (PRAERRPT DD) to determine why the archive
log cannot be opened.
844 Message Reference Guide (PS to ZLB)
RAE Messages
RAE00135
WHILE PROCESSING A SEGMENTED TABLESPACE IMAGE COPY, MORE THAN 1 OBID
WAS FOUND TO HAVE NO DATA ROWS. CANNOT CORELLATE.
Reason:
Two blank tables were found in the image copy. When this is the case, CA Recovery
Analyzer cannot determine which OBID is associated with which blank table in the
image copy.
Action:
Manual entry of the OBIDs is required.
RAE00136
PROGRAM PRA#TAPE ABNORMALLY TERMINATING.
Reason:
An abnormal condition occurred which required processing to stop.
Action:
See prior message in the output of the job.
RAE00137
A ERROR OCCURRED ALLOCATING THE ZPARM LIBRARY OR THE ZPARM
LIBRARY/MEMBER.
Reason:
The ZPARM library/member in the setup member for this DB2 subsystem could not be
allocated for processing.
Action:
Verify the existence of the data set and member name.
RAE00138
AN ERROR OCCURRED RETRIEVING THE ACTIVE LOGS FROM THE ZPARM
LIBRARY/MEMBER.
Reason:
No active log entries were found in the current BSDS specified in the SETUP member for
the current DB2 subsystem.
Chapter 4: RAE to RAW 845
RAE Messages
RAE00139
PRA#PSYS - INVALID PARM VALUE GIVEN.
Reason:
The parm given to the program is a one to four character DB2 subsystem ID.
Action:
Correct and resubmit.
RAE00140
PRA#UCAT - THE MASTER CATALOG COULD NOT BE ACCESSED.
Reason:
When attempting to access the master catalog specified in the PRA parmlib, an error
occurred which prevented the action.
RAE00141
PRA#UCAT - INSUFFICIENT STORAGE DURING PROCESSING.
Reason:
The region size is not sufficient or the PRA parmlib entry for the CATALOG BUFFER SIZE
is too small.
Action:
Enter a larger value on the first screen of the PRA parmlib (PTPEPRA1) and retry.
RAE00143
PRA#ICFA - ONE OF THE PRA#LOAD CATALOG SUBTASKS RETURNED A NON-ZERO
CODE. ABORTING.
Reason:
During the PRA#LOAD job, one of the 25 subtasks abended.
846 Message Reference Guide (PS to ZLB)
RAE Messages
RAE00144
PROGRAM PRA#CHEK IS ABNORMALLY TERMINATING.
Reason:
The program that forces a checkpoint abended because the wait time or number of
waits allowed was exceeded while waiting for the checkpoint record to be written.
Action:
Determine why the checkpoint record has not been written.
RAE00145
PRL#CHECK - THE NUMBER OF WAITS FOR THE COMPLETION OF THE CHECKPOINT
PROCESS HAS BEEN EXCEEDED. PROGRAM ABORTING.
Reason:
The program that forces a checkpoint abended because the wait time or number of
waits allowed was exceeded while waiting for the checkpoint record to be written.
Action:
Determine why the checkpoint record has not been written.
RAE00146
PRA#CALC - INVALID PARM VALUE GIVEN.
Reason:
The parameter value does not conform to the format expected by the PRA#CALC
program.
Action:
Check the parameter value.
RAE00147
ONE OR MORE DATASETS ALLOCATED IN THE PTILIB DD LACK APF AUTHORIZATION.
CHECK WITH YOUR SYSTEMS PROGRAMMER TO DETERMINE THE AUTHORIZATION OF
ALL DATASETS IN THE PTILIB DD.
Chapter 4: RAE to RAW 847
RAE Messages
RAE00148
THE USERID IN SYSADM FIELD FOR GIVEN SUBSYSTEM IN THE CA PARMLIB IS NOT
AUTHORIZED TO ISSUE A -DISPLAY GROUP COMMAND. PLEASE HAVE YOUR CA
ADMINISTRATOR CHECK THE VALIDITY OF THE USER ID SUPPLIED IN THE SYSADM
FIELD FOR THE GIVEN SUBYSTEM.
Reason:
An attempt was made to determine if the given DB2 SSID is a member of a data sharing
group. A -DISPLAY GROUP command is entered under the SYSADM user ID in the CA
SETUP parmlib member for the given subsystem. The user entered in this field is not
authorized for the following command.
Action:
Have your CA administrator check the validity in the SYSADM field for subsystem ssid in
the CA SETUP parmlib member.
RAE00150
PRA#ACTU - INVALID PARM VALUE GIVEN.
Reason:
The program received an invalid parm.
Action:
Verify the validity of the DB2 subsystem parm.
RAE00152
LOAD failed for DSNZPARM member.
Action:
Perform the following steps:
1.
In each of the SETUP members, add the SDSNEXIT ahead of the SDSNLOAD in the
LOADLIBS parameter for each subsystem.
LOADLIBS (xxxxxx.SDSNEXIT
xxxxxx.SDSNLOAD)
2.
Check the suffix referenced in the ENVDEF parmlib member.
848 Message Reference Guide (PS to ZLB)
RAE Messages
RAE00154
PRA#DALC - Error in RDJFCB Archive Log Copy 1
Reason:
A non-zero return code was returned by a RDJFCB macro used to find the volser of the
newly created copy of an archive log.
Action:
No action required. This message will be followed by further messages.
RAE00155
PRA#DALC - Error in RDJFCB Archive Log Copy 2
Reason:
A non-zero return code was returned by a RDJFCB macro used to find the volser of the
newly created copy of an archive log.
Action:
No action required. This message will be followed by further messages.
RAE00161
ERROR OCCURRED DURING -DISPLAY GROUP COMMAND.
CHECK THE JESMSGLG OF BATCH JOB OR TSO ACCOUNT FOR MORE INFORMATION.
Reason:
An error occurred when CA Recovery Analyzer issued a -DISPLAY GROUP command to
DB2. The most common reason for a failure is lack of security.
Action:
Verify that the SYSADM() value in the SETUP parmlib member matches a install SYSADM
as defined in the DB2 zParms. Correct and rerun the job. For all other errors, contact
Technical Support.
Chapter 4: RAE to RAW 849
RAE Messages
RAE00418
OVERRIDE_ERRORS parmlib setting of Y will be ignored:
The JCL generated may be unexecutable and therefore
will not be created.
Reason:
CA Recovery Analyzer detected severe errors while analyzing a strategy. The generated
JCL would contain unexecutable syntax for the COPY, RECOVER/REBUILD, or CHECK
utilities, therefore analysis stops. CA Recovery Analyzer does not generate any JCL, even
if the parmlib is set to OVERRIDE_ERRORS Y or if you select a manual override on the
Selected Recovery Point Error panel.
Action:
Correct the syntax problems that are causing the severe errors and rerun the analysis. If
you are using batch processing, you can determine the cause of the errors by viewing
the PRAERRPT report (included in the job output). If you are processing online, you can
view the PRA Selected Recovery Point Error panel, which appears automatically when
errors are detected.
RAE00937
Unknown Object Type Csect: &DBGCSCT at Offset: &DBGOFST for
Object: &DBGOBJ Object Type: &DBGOBJT Return Code: &DBGRET
Reason:
CA Recovery Analyzer retrieved an unknown DB2 object type from the system catalog in
the listed CSECT at the specified offset. The message identifies the object, object type,
and return code.
Action:
This error is for internal use. Contact CA Support and provide the information displayed
in this message.
850 Message Reference Guide (PS to ZLB)
RAE Messages
RAE00938
Storage Obtain failed in Csect: &DBGCSCT at Offset: &DBGOFST
Object: &DBGOBJ Length: &DBGR0 Address: &DBGR1 Return Code: &DBGRET
Reason:
CA Recovery Analyzer attempted to acquire storage but it failed in the listed CSECT at
the specified offset. The message identifies the object for which the storage was
requested, its length, and the return code.
Action:
This error is for internal use. Contact CA Support and provide the information displayed
in this message.
RAE00939
Storage Release failed in Csect: &DBGCSCT at Offset: &DBGOFST
Object: &DBGOBJ Length: &DBGR0 Address: &DBGR1 Return Code: &DBGRET
Reason:
CA Recovery Analyzer attempted to free storage but it failed in the listed CSECT at the
specified offset. The message identifies the object, its length, its address, and the return
code.
Action:
This error is for internal use. Contact CA Support and provide the information displayed
in this message.
RAE00940
SQL Error incurred in Csect: &DBGCSCT at Offset: &DBGOFST
Object: &DBGOBJ
Object Type: &DBGOBJT
SQL Error: &DBGR1 Return Code: &DBGRET
Reason:
CA Recovery Analyzer encountered an SQL error in the listed CSECT at the specified
offset. The message identifies the object CA Recovery Analyzer attempted to retrieve,
the object type, the SQL error, and the return code.
Action:
This error is for internal use. Contact CA Support and provide the information displayed
in this message.
Chapter 4: RAE to RAW 851
RAE Messages
RAE09001
Internal Recovery Analyzer error.
Archive Log Volume Count (ARCHIVE_LOG_NVOL) = 0.
Reason:
An internal error occurred.
Action:
A dump may be produced for this error. Contact your systems group to gather the
information from the dump.
RAE000E
VALID OPTIONS: (D)ELETE OR (S)ELECT
Reason:
An invalid option has been selected.
Action:
Choose D for Delete or S for Select.
RAE001E
DELETION REQUEST - CANCELLED - USER NOT EQUAL TO SUBMITTER.
Reason:
Your delete request has been cancelled because the user ID is not the same as the
submitter ID.
RAE002E
DB2 DATASET NOT FOUND.
Reason:
Errors have been encountered while processing DB2 data set information for your
selected object. Object information was found for the selected object within the
catalog, but it is incomplete or contradictory. The DB2 object information may appear to
be in error if DB2 has not totally written its buffers to disk since the object was created
or updated. Remember, the program accesses the actual VSAM data set directly instead
of using DB2.
852 Message Reference Guide (PS to ZLB)
RAE Messages
RAE003E
UNABLE TO ACCESS DB2 CATALOG
Reason:
Indicates that the DB2 Catalog has not been found. You received this error because the
OPEN failed on the VSAM data set which contains the index on SYSIBM.SYSTABLESPACE.
The VSAM catalog high level qualifier per DB2 subsystem is specified in CATALIAS of the
SETUP parmlib member. Check that the VSAM catalog level qualifier is correct for the
DB2 subsystem you are using. This error can also occur if a READ fails for this same
VSAM data set.
RAE004E
YOU ALREADY HAVE AN ACTIVE DB2 SESSION.
Reason:
You have attempted to jump to a product that you are already using.
Action:
You must exit the product you are currently in to get back to the product you want.
RAE005E
YOU ALREADY HAVE AN ACTIVE RC/UPDATE SESSION.
Reason:
You have attempted to jump to CA RC/Update when you are already using the product.
Action:
You must exit the product you are currently in to get back to CA RC/Update.
RAE006E
YOU ALREADY HAVE AN ACTIVE RC/QUERY SESSION.
Reason:
You have attempted to jump to CA RC/Query when you are already using the product.
Action:
You must exit the product you are currently in to get back to CA RC/Query.
Chapter 4: RAE to RAW 853
RAG Messages
RAE007E
YOU ALREADY HAVE AN ACTIVE RC/MIGRATOR SESSION.
Reason:
You have attempted to jump to the product when you are already using the product.
Action:
You must exit the product you are currently in to get back to CA RC/Migrator.
RAE008E
YOU ALREADY HAVE AN ACTIVE RC/SECURE SESSION.
Reason:
You have attempted to jump to CA RC/Secure when you are already using the product.
Action:
You must exit the product you are currently in to get back to CA RC/Secure.
RAE009E
THE SPECIFIED OPERANDS ARE INVALID FOR THE COMMAND YOU HAVE ENTERED.
Action:
Enter a ? on the command line to receive a listing of valid commands. From this
command list, enter a ? next to the desired command to receive help. Or, enter an S to
execute the command.
RAG Messages
Messages with the RAG prefix are generated from CA Database Analyzer for DB2.
RAG000E
SQL ERROR HAS BEEN ENCOUNTERED.
Reason:
See the IBM DB2 Message and Codes reference manual for information on the given
SQL error.
854 Message Reference Guide (PS to ZLB)
RAG Messages
RAG002I
PROCESS REQUEST CANCELLED.
Reason:
Your CANCEL command successfully terminated the process.
RAG003I
DOWN REQUEST IGNORED - ALREADY AT BOTTOM OF PAGE.
Reason:
You are attempting to scroll past the end of the data. Your cursor down request will be
ignored.
RAG004I
UP REQUEST IGNORED - ALREADY AT TOP OF PAGE.
Reason:
You are attempting to scroll up past the top of the data. Your cursor up request will be
ignored.
RAG005E
STORAGE ACQUISITION REQUEST FAILED - APPLICATION CANCELLED.
Reason:
Your Storage Acquisition Request cannot be fulfilled due to storage limitations
(GETMAIN failure). This function may succeed when the system is less stressed.
RAG006E
APPLICATION FAILED DURING OPEN PROCESSING OF PTILIB.
Reason:
The application cancelled due to an error in the OPEN processing of PTILIB.
Action:
Check that the libraries concatenated under PTILIB are the libraries that contain the CA
load modules.
Chapter 4: RAE to RAW 855
RAG Messages
RAG007E
APPLICATION FAILED DURING LOAD PROCESSING.
Reason:
The application cancelled due to a problem encountered while attempting to LOAD a
module.
Action:
Check that the libraries concatenated under PTILIB contain all load modules.
RAG008E
QUERY SELECTION OPTION MUST BE (N), (S), OR (Y).
Reason:
An invalid query option has been selected. Choose N for Do Not Execute EQF, S for
Select a Query for Execution, or Y for Add a New Query or Edit an Existing Query.
RAG009E
QUERY SUBSYSTEM FAILED DURING error, return, Reason:.
Reason:
Initialization, processing, or termination failed while processing an extended query
function in the Query Facility or in the report procedures.
Action:
Check the validity of the EQF member in question by exploding that EQF member while
in report procedures.
RAG010I
DEFAULT QUERY PROCESS DURING SQL SELECTION.
Reason:
This message lets you know that a default EQF has been set up for the current query and
it was used to produce the current report.
856 Message Reference Guide (PS to ZLB)
RAG Messages
RAG011W
INVALID F KEY PROCESS KEY.
Reason:
An invalid F key request has been made. Valid F keys are: END, RETURN, UP, DOWN, or
Enter.
RAG012E
THE SYNTAX IS INCORRECT OR THE COMMAND IS NOT KNOWN.
Reason:
An invalid syntax or command has been entered. Enter a ? in the command line for a
listing of valid commands.
RAG013I
DETAILED SELECTION REQUEST PROCESSING ==> PLEASE STANDBY.
Reason:
The program is processing your selections. Your selections will be displayed immediately
after processing.
RAG014I
USER NOT AUTHORIZED TO USE PRODUCT - SEE AUTHORIZATIONS.
Reason:
Authorization to use the product has not been assigned. Use CA's Authorization Facility
to check and to grant authorization.
RAG016E
THIS SSID NOT SPECIFIED IN PTIPARM(SETUP).
Reason:
The SSID selected does not have an entry in the SETUP member of the library allocated
to the PTIPARM DD. This DD is usually allocated to the CA parmlib.
RAG017E
ERROR IN MODEL JOB CARD MEMBER - ENTER CANCEL AND CHECK SYMBOLICS.
The model job card member is invalid. Check your model job card, especially check for
invalid symbolics. Enter CAN or CANCEL to exit the panel RDA.ESMN.
Chapter 4: RAE to RAW 857
RAG Messages
RAG018I
PLEASE SELECT A PRE UTILITY MODEL.
Reason:
Indicates that the selection list displays to allow the selection of a PRE model. This
model will be placed (without symbolic substitution) as the first utility step of the job
stream.
RAG019I
PLEASE SELECT A POST UTILITY MODEL.
Reason:
Indicates that the selection list displays to allow the selection of a POST model. This
model will be placed (without symbolic substitution) as the last utility step of the job
stream.
RAG020I
LINK MACRO FAILED FOR PTLBMOD. CHECK PTILIB FOR THIS MODULE.
Reason:
The program attempted to use the LINK macro to access load module PTLBMOD, but the
LINK failed. You may also receive a terminal message (CSV003, and so on) with the
return code and reason code explaining the failure in more detail.
Action:
If you did not, issue a TSO PROFILE command and check that WTPMSG and MSGID are
on. If the messages are not enabled, issue a TSO PROFILE WTPMSG MSGID to allow
terminal messages. Repeat the sequence of steps leading up to the failure.
With the return code and reason code you can then find the cause of the problem. Most
likely causes are PTILIB does not include the load module, or your region is not large
enough.
RAG021E
DELETE REQUEST FAILED FOR LOAD MODULE lmod
Reason:
Indicates that a delete request has failed for a loaded module.
Action:
Notify Technical Support with the name of the load module that appears in the
message, as well as any other relevant documentation.
858 Message Reference Guide (PS to ZLB)
RAG Messages
RAG022I
PREVIEW Action: JCL BYPASSED - FILL MEMBER CREATED
Reason:
Indicates that the program has bypassed the preview action JCL option because the
action JCL was created with only a fill member.
RAG023I
PREVIEW Action: JCL BYPASSED - FATAL ERROR ENCOUNTERED
Reason:
Indicates that the program has bypassed the preview action JCL option because a fatal
error was encountered and no JCL was created.
RAG024E
PACKAGE/PLAN SYMBOLIC PROCESSING FAILED. CALL CA.
Reason:
Indicates that the processing to resolve a package or plan symbolic failed. Try to
generate the same JCL using an Extract. The PTIMSG may have more details for this
error if it happens there.
RAG025E
PACKAGE/PLAN SYMBOLIC PROCESSING FAILED. DEADLOCK OCCURED.
Reason:
Indicates that the processing to resolve a package or plan symbolic incurred a dead lock.
Plan symbolic processing accesses SYSPLANDEP. Package symbolic processing accesses
SYSPACKDEP and if versioning is requested in the parmlib member then also
SYSPACKAGE.
Action:
This is an operational error and can be alleviated by rerunning Utility Manager when
these resources are available. Call Technical Support if this does not seem to be the
situation. Try to generate the same JCL using an Extract. The PTIMSG may have more
details for this error if it happens there.
Chapter 4: RAE to RAW 859
RAG Messages
RAG026E
1 STEP AND X STEPS OPTIONS CANNOT BE MIXED. PRESS HELP FOR DETAILS.
Reason:
There are two types of DU Utility Codes. When using type:
■
1 STEP-One step will be generated for the tablespace or for all partitions flagged as
SELECTED during Action: Condition processing. Valid choices for this option are: RR,
FL, FU, FI, and FC.
■
x STEPS-One step will be generated for the tablespace or for each partition flagged
as SELECTED during Action: Condition processing. Valid choices for this option are:
QC, CX, RX, LX, UX, FR, MC, MM, and PC.
An Extract Procedure can only have one of these types of DU Utility Codes tied to it, not
both.
Mixing DU ONESTEP and XSTEPS Utility Codes is not currently supported.
RAG027E
1 STEP and X STEPS options cannot be mixed. Press HELP for details.
Reason:
Message RAG027E indicates that the SQLID and the Default Procedure Creator were
reset to your TSO USERID. It would have been a security violation to allow the user to
use an invalid SQLID for the procedure creator. For this error to occur, these conditions
must be true:
■
A DB2 SET CURRENT SQLID = 'xxxxxxxx' must have failed. An SQL error panel would
have been displayed.
■
The user profile must be set to SQLID for the Proc. Creator ==> value OR the user
profile must be set to PARMLIB for the Proc. Creator ==> value and the keyword in
the PARMLIB1.(Database Analyzer) member must be DEF_PROC_CREATOR (SQLID).
Action:
Verify the setting of the SQLID. A new SQLID can be set with the global command SET
SQLID xxxxxxxx.
860 Message Reference Guide (PS to ZLB)
RAG Messages
RAG028E
DU Symbolic variable in a NON-DU Util Code. Press HELP for details.
Reason:
RAG028E appears when a problem was found processing the action procedure
symbolics.
DU symbolics variables can be used only in models set for DU action utility code. In
others words, normal use of those symbolic variables is dedicated to CA Utilities JCL
generation. DU symbolic variables can be used for utility codes you can access using DU
panel (RAPUBDU): QC, CX, RR, RX,PC, MM, MC, FU, UX, FR, FL, LX, FI, and FC. Some DU
symbolics can be used only for a given CA Utility Product. Any other uses will NOT be
supported.
Action:
To correct this problem, update the Model by removing ALL DU symbolic variables in it.
By doing this, all action Procedures and related Extract Procedures will be executable
again. Since no tables must be updated, it is easiest to edit the Model using ISPF
function(3.4). The other solution is to call your local sales representative to purchase
related CA Utility Products.
RAG029I
Virtual storage shortage detected. PDA may have been able to recover. Press HELP for
details.
Reason:
Message RAG029I indicates that the program detected a shortage of virtual storage
below the 16M line. Above the 16M line extended storage will be used when possible.
Potentially, a storage abend could still occur after this if not enough above the line
storage was available. If possible, logon to TSO using a larger region size to get more
below the line storage. If storage abends continue, process less objects in the Utility
Extract.
Action:
For virtual storage related information, see Virtual Storage in the on-line glossary by
choosing option T from the main menu.
Chapter 4: RAE to RAW 861
RAI Messages
RAG030I
VIRTUAL STORAGE SHORTAGE DETECTED
Reason:
Indicates that the program detected a shortage of virtual storage above the 16M line.
The program displays data retrieved up to the point of shortage detection.
Action:
To avoid this situation, use Automatic Statistics Maintenance (option 3;1 from the main
menu) or Log Maintenance (option E;W from CA main menu) to purge old rows from log
tables PTLOG_MAIN_1500 and PTLOG_RDAMSG.
RAG031I
INVALID JOB CARD DETECTED IN JOB CARD MODEL. UNPREDICTABLE RESULTS MAY
OCCUR.
Reason:
Indicates that the program detected that the first statement in the JOB card model is
not a valid JOB card. The program requires a valid JOB card to correctly generate
executable action JCL, or unpredictable results may occur in the generated action JCL.
For example, certain automatic symbolics, like %LABL and %REFR may not be correctly
resolved. Edit the JOB card model and provide a valid JOB card. For an example of a valid
JOB card see sample model MJJOBCD.
Note: The generated JCL may contain a JCL comment following the first card found from
the JOB card model indicating an invalid JOB card was detected. This comment card will
have a reason code representing what was found to be incorrect. The possible reason
codes and descriptions are as follows:
■
Card does not start with // in column 1
■
First digit of job name (column 3) is invalid (eg, &JCLC )
■
Job name exceeds the maximum length of 8 digits
■
' JOB ' was not found-end of card reached
■
First non-blank after job name is not 'JOB '
■
Specified JOB card model was returned empty from Model Services.
RAI Messages
Messages with the RAI prefix are generated from CA Recovery Analyzer.
862 Message Reference Guide (PS to ZLB)
RAI Messages
RAI00001
PRA#ARCH - JOB GENERATING CHANGE INVENTORY LOG JOB STREAM.
Reason:
The disaster recovery archive log backup program has successfully backed up all the logs
it needs and is now generating the change inventory log job.
Action:
None.
RAI00002
PRA#ARCH - JOB GENERATING CANCEL CONDITIONAL RESTART STREAM.
Reason:
The disaster recovery archive log backup program has successfully generated the
inventory log job and is now generating the cancel conditional restart job.
Action:
None.
RAI00003
PRA#ARCL - SHOULD RECOVERY ANALYZER WAIT FOR THE ARCHIVE LOG PROCESS FOR
SSID ssid TO COMPLETE (Y/N)?
Reason:
The [email protected] job that backs up the local DB2 catalog and generates other recovery JCL
issues an -ARCHIVE LOG command. The [email protected] job then goes into a wait state until
the log has been archived.
Action:
If you respond to this WTO with an N, the [email protected] job does not go into a wait state. If
you respond with a Y, or do not respond at all, the [email protected] job goes into a wait state
until the log has been archived. Responding to this message with an N lets you continue
other CA Recovery Analyzer processing without waiting for the log to be archived.
Chapter 4: RAE to RAW 863
RAP Messages
RAI00004
PRA#ARCL - INVALID RESPONSE. SHOULD PRA WAIT FOR THE ARCHIVE LOG PROCESS
ON DB2 ssid TO COMPLETE (Y/N)?
Reason:
You entered an invalid response to this message.
Action:
Enter Y or N to indicate whether you want CA Recovery Analyzer to wait for the archive
log process to complete on the specified subsystem. For more information, see the
explanation for message RAI00003.
RAI00005
PRA#ARCL - DETECTED THE COMPLETION OF THE ARCHIVE LOG PROCESS ON DB2
SUBSYSTEM ssid.
Reason:
This message informs you that CA Recovery Analyzer has completed archiving the log.
Action:
None.
RAP Messages
Messages with the RAP prefix are generated from CA Database Analyzer for DB2.
RAP000E
PROCEDURE NAME REQUIRED.
Reason:
A procedure name has not been entered, or an invalid procedure name has been
entered.
Action:
Enter a valid procedure name.
864 Message Reference Guide (PS to ZLB)
RAP Messages
RAP001E
COPY PROCEDURE NOT FOUND; ENTER (*) FOR SELECTION LIST.
Reason:
The procedure you specified cannot be located.
Action:
Check the typing for typographical errors. If the spelling is correct, enter an asterisk (*)
in the Procedure Name field for a listing of all procedures.
RAP002E
PROCEDURE DESCRIPTION REQUIRED.
Reason:
The Procedure Description has been omitted.
Action:
Enter a Procedure Description.
RAP003E
AT LEAST ONE EXTRACT OPTION MUST BE SELECTED.
Reason:
This message appears when you are attempting to create a procedure and no objects
have been selected.
Action:
Enter selection criteria to get a list of objects from which a selection may be made.
RAP004E
CREATOR ID REQUIRED.
Reason:
The Creator ID has been omitted. Include the required Creator ID to continue.
Chapter 4: RAE to RAW 865
RAP Messages
RAP005E
PROCEDURE DB2 SYSTEM ID REQUIRED.
Reason:
The Procedure DB2 System ID has been omitted.
Action:
Enter this ID in the DB2 SYSID field to continue.
RAP006I
SELECTED PROCEDURE FOUND - CURRENCY SET.
Reason:
This message informs you that the selected procedure was found.
RAP007I
COPY PROCEDURE FOUND - CURRENCY SET.
Reason:
This message informs you that the copy procedure was found.
RAP008E
COPY PROCEDURE SPECIFIED IS NOT SHAREABLE.
Reason:
You have selected a non-shareable procedure (Share Option set to N). This procedure
can be used only by the creator.
RAP009E
SHARE OPTION MUST BE (Y)ES, (N)O, OR (U)PDATE.
Reason:
An invalid Share Option has been entered.
Action:
Select one of the three valid options: Y for Yes, N for No, or U for Update.
866 Message Reference Guide (PS to ZLB)
RAP Messages
RAP010E
UPDATE INVALID - USER NOT OWNER OR PROCEDURE NOT UPDATEABLE.
Reason:
This message appears when a procedure whose Share Option is not updateable (Share
Option set to N or Y) is selected by a user who is not the creator of the procedure. The
procedure may be updated only by the creator.
RAP011E
OPTIONS: E(XPLODE) OR D(ELETE).
Reason:
An invalid option has been entered. Valid options are E for Explode or D for Delete.
RAP012E
DELETION INVALID - USER NOT OWNER OR PROCEDURE NOT SHAREABLE.
There has been an attempt to delete a procedure whose Share Option has been set to
N. Only the creator can delete the procedure.
RAP013I
EXTRACT ENTRIES PROCESSED SUCCESSFULLY.
Reason:
This message lets you know that the DB2 objects you selected for extract have been
correctly processed.
RAP014W
OPTIONS: S(ELECT) OR E(XPLODE).
Reason:
An invalid option has been selected.
Action:
To correct this, choose one of these options: S for Select or E for Explode.
Chapter 4: RAE to RAW 867
RAP Messages
RAP015I
proctype PROCEDURE storproc - Action:.
Reason:
This variable message confirms that an action, execution, extract, or report procedure
has been deleted or created.
RAP016E
DATA FIELD REQUIRED.
Reason:
A required data field has been left blank. Your cursor will jump to the data field that
needs a value.
Action:
Enter an appropriate value in the data field to correct this.
RAP017E
OPTIONS: E(XPLODE), U(PDATE), D(ELETE), OR L(IST EXEC).
Reason:
An invalid option has been selected.
Action:
Select one of the following options:
■
E-Explode.
■
U-Update.
■
D-Delete.
■
L-List Execution.
RAP018E
OPTIONS: C(REATE).
Reason:
An invalid option has been selected.
Action:
Enter C for Create as a valid option.
868 Message Reference Guide (PS to ZLB)
RAP Messages
RAP019E
OPTIONS: E(XP), U(PD), S(UB), D(ELETE), A(CTION), L(IST), C(OPY)An invalid option has
been selected.
Reason:
You can correct this error by selecting one of the following options:
■
E-Explode.
■
U-Update.
■
A-Action:.
■
D-Delete.
■
S-Submit.
■
L-List Execution.
■
C-Copy.
RAP020I
EXTRACTING ONLY THRU DATABASES.
Reason:
This informs you that only a list of databases will display.
RAP021I
EXTRACTING ONLY THRU TABLE SPACES.
Reason:
This informs you that only a list of table spaces will display.
RAP022I
EXTRAction: ONLY THRU TABLES.
Reason:
This informs you that only a list of tables will display.
Chapter 4: RAE to RAW 869
RAP Messages
RAP023E
OPTIONS: A(UTO-BUILD) OR S(ELECTION).
Reason:
An invalid option has been entered.
Action:
For the correct option, choose A for Auto-build or S for Selection.
RAP024E
DB2 OBJECT SELECTED CAN ONLY BE "A" - AUTOBUILD.
Reason:
The option S for Selection was chosen for a DB2 object that can only use the option A
for Autobuild.
Action:
Select A.
RAP025E
LOWER INDEX/TABLESPACE PARTITIONS CAN ONLY BE "S" - SELECTED.
Action:
Option A for Autobuild was selected for Lower Index/Tablespace partitions. Clear this by
choosing S for Selected.
RAP026E
LOWER LEVELS OF AN "AUTOBUILD", MUST NOT BE SELECTED.
Reason:
An object already included in an Autobuild has been selected.
Action:
Do not select the lower levels of an Autobuild.
870 Message Reference Guide (PS to ZLB)
RAP Messages
RAP027W
OPTION (E)XPLODE VALID ONLY FOR "ALL" EXTRACTS.
Reason:
The EXPLODE option is available only for objects with a level of ALL. You entered this
command for an object whose level is SEL. The object's level displays in the LVL column
of the list.
RAP028E
COPY PROCEDURE SPECIFIED RESIDES IN DIFFERENT DB2 SYSTEM.
Reason:
The copy procedure specified refers to a different DB2 subsystem from the one you are
currently connected to. You cannot copy a procedure that refers to a different DB2
subsystem because the objects will probably not exist on the current subsystem.
RAP029E
OPTIONS: E(XPLODE), U(PDATE), D(ELETE), S(UBMIT), C(OPY)An invalid option has
been selected.
Action:
You can correct this error by selecting one of the following options:
■
E-Explode.
■
U-Update.
■
D-Delete.
■
S-Submit.
■
C-Copy.
RAP030E
EXECUTION PROCEDURES REQUIRE AT LEAST ONE EXTRACT.
Reason:
You must select at least one extract procedure or one report procedure to successfully
create an execution procedure.
Action:
Enter an asterisk (*) in the procedure name field for a listing of procedures. Select from
the listing.
Chapter 4: RAE to RAW 871
RAP Messages
RAP031E
RESTORE OPERATION REQUIRES DATASET PARAMETER IN CLIST.
Reason:
The program attempts to restore statistics but the specified model library and model
member do not contain the name of the data set which was used in the statistics
backup. The default model member is%MSRTRST for Batch and%MCRTRST for Online.
DATASET is the parameter within the model member that is not being found.
RAP032E
VALID ENTRIES ARE (Y)ES OR (N)O.
Reason:
This message is in response to an invalid entry.
Action:
Choose one of these valid entries: Y for Yes or N for No.
RAP033E
PRINT CLASS SPECIFICATION REQUIRED.
Action:
Enter a valid print class to continue.
RAP034E
EXECUTION REQUIRES VALID MODEL JCL.
Reason:
An invalid model JCL has been entered.
Action:
Check the model JCL for spelling errors. See the product documentation more
information on model JCL.
RAP035E
DATABASE CONTAINS NO TABLESPACES.
Reason:
There are no tablespaces within the specified database. The database will be bypassed.
872 Message Reference Guide (PS to ZLB)
RAP Messages
RAP036E
CODE SPECIFIED WITHOUT PROCESSING - RE-PROCESS OR LOSE CODE.
Reason:
This error appears if a utility code that contains user symbolics has been entered
without its accompanying symbolics filled in the Symbolic Replacement panel. If the
symbolics are not entered, then the utility code will not remain part of the extract or
utility procedure.
RAP037I
EXTRAction: CURRENTLY CONTAINS NO ENTRIES.
Reason:
Informs you that no objects have been selected.
Action:
Select DB2 objects if you would like to perform extraction procedures.
RAP038E
TOTAL LENGTH OF PARAMETERS AND REPLACEMENTS EXCEEDS LIMIT.
Reason:
This message displays when the number of bytes required to store the information
regarding a specific utility or action procedure is greater than 1800 bytes. Information
types that cannot exceed 1800 bytes include: Model Library Name, Conditional action
Information, Immediate Message Information, Utility Codes, and User Supplied
Symbolics associated with each one.
Chapter 4: RAE to RAW 873
RAP Messages
RAP039E
STORED Action: DOESN'T MATCH CURRENT MODEL.
Reason:
This message appears when a model member's number of user-specified symbolics has
changed since the last update of the action procedure. Therefore, this message displays
when you are updating an action procedure. One of the existing utility codes will be
referencing the model member. Every utility code that is affected will be marked as
invalid. Also, a parameter of U will be placed next to those utility codes to force an
update of the utility code symbolics.
Action:
Press Enter to display the symbolic replacement screen for the affected utility codes.
Enter values for the new symbolics.
RAP040E
DATASET FAILED ON dtype - RETCODE => derr.
Reason:
The ISPF library access service call failed.
Action:
Check that all specified libraries are correct.
RAP041E
ZERRLM. The ISPF library access service (LMxxxxx) call failed.
Action:
Check that all specified libraries are correct.
RAP042E
VALID OPTIONS: (A)CTION OR (E)XPLODE.
Reason:
In invalid option has been selected.
Action:
Choose A for action or E for Explode.
874 Message Reference Guide (PS to ZLB)
RAP Messages
RAP043E
DATA FIELD REQUIRES NUMERIC ENTRY.
Reason:
Character data has been entered in a numeric field.
Action:
To correct this, enter a numeric.
RAP044E
DELETION REQUEST DENIED - PROCEDURE CONNECTED TO EXECUTION PROC.
Reason:
This message appears when you try to delete an extract or report procedure that is
contained in an execution procedure.
Action:
You must first delete the extract or report procedure from the execution procedure(s)
before you can delete the extract or report procedure. You can also delete the entire
execution procedure.
RAP045E
VALID OPTIONS: (Q)UERY, (G)RAPH, (F)ORECAST, OR (T)REND ANALYSIS.
Reason:
An invalid option has been selected.
Action:
Choose Q for Query, G for Graph, F for Forecast, or T for Trend Analysis.
RAP046E
EXECUTION TYPE SELECTED CONTAINS NO ENTRIES.
Reason:
The execution procedure contains no extract or reporting procedures.
Chapter 4: RAE to RAW 875
RAP Messages
RAP047E
VALID OPTIONS: SUBMIT TO (D)ATASET, (J)ES, OR (P) PREVIEW.
Reason:
An invalid option has been selected.
Action:
Correct this by selecting D for Dataset, J for JES, or P for Preview.
RAP048I
JOB SUBMITTED TO OUTPUT DESTINATION.
Reason:
Informs you that the job submitted was successfully sent to a data set or to JES.
RAP049E
VALUE MUST BE EITHER # OR %.
An invalid value has been entered for the type of change requested. Valid values are #
for the actual numeric change or % for the percentage change.
RAP050E
VALID CMDS: (SUB)MIT, (EXP)LODE, (CAN)CEL, MAIN, EXIT, OR ?.
Reason:
An invalid command has been entered.
Action:
Select one of these valid commands: SUB, EXP, CAN, MAIN, EXIT, or ?. Enter a ? in the
command line for a listing of valid commands.
RAP051E
READ-AHEAD BUFFERS MUST BE A MINIMUM OF FOUR (4).
Reason:
The READ-AHEAD buffers are less than 4.
Action:
Specify a minimum of 4 in the BUFFERS field to correct this.
876 Message Reference Guide (PS to ZLB)
RAP Messages
RAP052E
VALID CMDS: (SUB)MIT, (EXP)LODE, (CAN)CEL, (SA)VE, MAIN, ?.
Reason:
An invalid command has been entered.
Action:
Select one of these valid commands: SUB, EXP, CAN, SA, MAIN, or ? for a command list.
RAP053E
VALID CMDS: (EXP)LODE, CANCEL, MAIN, OR ?.
Reason:
An invalid command has been entered.
Action:
Select one of these valid commands: EXP, CANCEL, MAIN, or ?. Enter a ? to display a list
of valid commands.
RAP054E
VALID CMDS: MAIN OR ? FOR COMMAND LIST.
Reason:
An invalid command has been entered.
Action:
Select MAIN to return to the Main Menu or ? to display a listing of valid commands.
RAP055E
VALID CMDS: CANCEL, MAIN, EXIT, END, OR ? FOR COMMAND LIST.
Reason:
An invalid command has been entered.
Action:
Correct this by selecting one of these valid commands: CANCEL, MAIN, EXIT, or END.
Enter a ? to display a list of valid commands.
Chapter 4: RAE to RAW 877
RAP Messages
RAP056E
VALID OPTIONS: (U)PDATE, (E)XPLODE, OR (D)ELETE.
Reason:
An invalid option has been selected.
Action:
Choose one of these valid options: U for Update, E for Explode, or D for Delete.
RAP057E
DATASET REQUIRED.
Reason:
An invalid data set name has been entered.
Action:
Correct this by entering a valid data set name in the field where the cursor is positioned.
RAP058E
MODEL JCL/OUTPUT DESTINATION DATASETS MUST BE PARTITIONED.
Reason:
A sequential data set has been specified instead of a partitioned data set. Model JCL and
output destination data sets must be partitioned.
RAP059E
MODEL JCL - MEMBER NOT FOUND; ENTER * FOR SELECTION LIST.
Reason:
The model JCL Member was not found in the specified library.
Action:
Enter an asterisk (*) for a listing of the members contained in the selected library.
RAP060E
INVALID UTILITY CODE.
Reason:
An invalid utility code has been entered. Valid utility codes are listed on your screen.
878 Message Reference Guide (PS to ZLB)
RAP Messages
RAP061E
VALID CODES: (U)PDATE, (E)XPLODE, OR (N)O UPDATE.
Reason:
An invalid code has been entered.
Action:
Choose one of these three valid codes as your selection: U for Update, E for Explode, or
N for No Update
RAP062E
PARM FIELD ENTRY INVALID FOR NON-SELECTED CODE
RAP063E
TSO USER ID REQUIRED WITH OPTION SPECIFIED YES.
Reason:
This message displays if the TSO User is YES and the TSO ID is not specified.
Action:
Specify the TSO ID or set TSO User to NO.
RAP064E
CONDITIONAL FIELD REQUIRED IF OPTION SELECTED
RAP065E
VALID ENTRIES: (O)NLINE OR (B)ATCH.
Reason:
An invalid option has been entered.
Action:
Select one of these two valid options: O for Online or B for Batch.
Chapter 4: RAE to RAW 879
RAP Messages
RAP066E
VALID CODES: (E)XPLODE.
Reason:
An invalid code has been chosen.
Action:
Enter E for Explode.
RAP067E
DUPLICATE PROCEDURE.
Reason:
You are attempting to save a procedure whose name already exists.
Action:
You must specify a unique procedure name.
RAP068E
ROUTING AND DESCRIPTOR CODES MUST BE BETWEEN 01 AND 12.
Reason:
An invalid WTOR code has been entered.
Action:
Enter a Routing or Descriptor code that is between the numbers 01 and 12.
RAP069E
VALID OPTIONS: (Y)ES, (N)O OR (E)XPLODE.
Reason:
An invalid option has been entered.
Action:
Correct this by selecting one of these three options: Y for Yes, N for No, or E for Explode.
880 Message Reference Guide (PS to ZLB)
RAP Messages
RAP070E
UNPROCESSED EXTRACT ITEMS, EITHER CANCEL REQUEST OR SUBMIT.
Reason:
This message displays if you select objects in Statistics Maintenance or the Utility
Manager and then try to exit without first submitting the Statistics Maintenance
backup/restore or submitting the utility request. As a solution, CANCEL the request or
SUBMIT the request.
RAP071E
MODEL JCL CONTAINS AN INVALID VARIABLE.
Reason:
The model JCL contains an invalid variable.
Action:
See the product documentation for a list of valid symbolic variables. Then, correct the
model JCL variable.
RAP072I
MODEL JCL CONTAINS NO SYMBOLIC REPLACEMENTS.
Reason:
Informs you that the Symbolic Variable Replacement screen will not display because
there are no symbolic variables in the model JCL.
RAP073E
IMMEDIATE MESSAGE MUST BE "N" SINCE THE Action: IS NON CONDITIONAL.
Reason:
The action must have at least one condition specified to request immediate messages.
Action:
To specify a conditional action, place a Y in the Conditional action field.
Chapter 4: RAE to RAW 881
RAP Messages
RAP074E
OPTIONS: E(XPLODE), U(PDATE), D(ELETE), S(ELECT), L(IST EXTRACTS).
Reason:
An invalid option has been selected.
Action:
Select one of the following valid options:
■
E-Explode.
■
U-Update.
■
D-Delete.
■
S-Select.
■
L-List Extracts.
RAP075E
OPTIONS: E(XPLODE), S(ELECT), O(BJECT), C(CREATE).
Reason:
An invalid option has been selected.
Action:
Select one of the following valid options:
■
E-Explode.
■
S-Select.
■
O-Object.
■
C-Create.
RAP076E
Action: PROCEDURE storproc - NO LONGER AVAILABLE - ROLLBACK ISSUED.
Reason:
The action procedure associated with the current procedure has been deleted or
changed. Your changes are rolled back.
Action:
Check the status of the action procedure.
882 Message Reference Guide (PS to ZLB)
RAP Messages
RAP077E
OPTIONS: E(XPLODE), U(PDATE), D(ELETE), L(IST EXTRACTS), C(OPY).
Reason:
An invalid option has been selected.
Action:
You can correct this error by selecting one of the following options:
■
E-Explode.
■
U-Update.
■
D-Delete.
■
L-List Extracts.
■
C-Copy.
RAP078E
OPTIONS: E(XPLODE), S(ELECT), Y(CREATE).
Reason:
An invalid option has been selected.
Action:
Select one of the following valid options:
■
E-Explode.
■
S-Select.
■
Y-Yes, Create.
RAP079E
VALID OPTIONS: (S)ELECT.
Reason:
An invalid option has been selected. The valid option available is S for Select.
Chapter 4: RAE to RAW 883
RAP Messages
RAP080E
A REFERENCE INTEGRITY ERROR EXISTS BETWEEN OBJECTS AND Action:S.
Reason:
The specified action cannot be executed without violating referential integrity.
Action:
Check referential integrity between objects and actions.
RAP081I
UNPROCESSED MODIFIED PAGES EXIST - EITHER PROCESS PAGES OR CANCEL.
Reason:
Informs you that unprocessed modified pages exist. You must CANCEL the changes or
process them by entering the PROCESS command.
Action:
See the product documentation for more information on Data Change Techniques.
RAP082I
VALUE IS OUTSIDE OF VALID RANGE
RAP083E
RNEXT, RBACK, RFIRST, forMAT, OR DNEXT NOT VALID IN NON DATA PAGE.
Reason:
The commands RNEXT, RBACK, RFIRST, forMAT, or DNEXT have been used on non-data
pages. Non-data pages include header, space map, and root pages.
RAP084E
FORMAT COMMAND REQUIRES PROPER ROW POSITIONING.
Reason:
You will see this message when you are not positioned at the beginning of a row and the
FORMAT command is issued. Use RNEXT, RFIRST, or DNEXT for valid row positioning.
884 Message Reference Guide (PS to ZLB)
RAP Messages
RAP085E
OPTIONS: D(ELETE).
Reason:
An invalid option has been selected.
Action:
Choose D for Delete as the valid option.
RAP086E
OPTIONS: A(CTIONS), D(ELETE), OR E(XPLODE).
Reason:
An invalid option has been selected.
Action:
Select one of the following valid options:
■
A-Action.
■
D-Delete.
■
E-Explode.
RAP087E
CATALOG UPDATE MAY BE EXECUTED ONLY IN VERSION 2 OF DB2.
Reason:
You have attempted to execute CATALOG Update using Version 1.3 or lower of DB2.
CATALOG Update may be executed with Version 2 or higher.
Chapter 4: RAE to RAW 885
RAP Messages
RAP088E
OPTIONS: S(ELECT), E(XPLODE), OR U(PDATE).
Reason:
An invalid option has been selected.
Action:
You can correct this error by selecting one of the following options:
■
S-Select.
■
E-Explode.
■
U-Update.
RAP089E
OPTIONS: E(XPLODE), S(UBMIT), D(ELETE), U(PDATE), L(IST), C(OPY).
Reason:
An invalid option has been selected.
Action:
Select one of the following valid options:
■
E-Explode.
■
S-Submit.
■
D-Delete.
■
U-Update.
■
L-List.
■
C-Copy.
RAP090E
VALID ENTRIES: (P)REVIEW OUTPUT OR (B)ATCH.
Reason:
You will receive this error message for invalid entries.
Action:
Select one of these two valid entries: P for Preview output or B for Batch.
886 Message Reference Guide (PS to ZLB)
RAP Messages
RAP091E
CATALIAS PARAMETER INVALID FOR THIS SSID IN PTIPARM(SETUP).
Reason:
The CATALIAS parameter is invalid or missing for this SSID. The parameters are specified
in the SETUP member of the data sets allocated to the PTIPARM DD. This is usually the
CA parmlib.
RAP092E
MJSTATS NOT FOUND IN MODEL LIBRARY OR IT CONTAINS INVALID SYMBOLICS.
Reason:
This message means MJSTATS was not found in the specified Model Library or MJSTATS
contains invalid symbolics. This model contains JCL for executing procedures in batch
mode.
Action:
Check if MJSTATS exists in the specified model library and that it contains no invalid
symbolics. See the product documentation for more information on model JCL and
symbolic variables.
RAP093E
ROW NUMBER ENTERED IS LARGER THAN MAXIMUM ROWS ON PAGE.
Reason:
The row ID entered is larger than the total number of rows for that page.
Action:
Enter a lower row ID.
RAP094E
AUDIT FACILITY COMPLETED.
Reason:
Informs you that your AUDIT command successfully audited your page.
Chapter 4: RAE to RAW 887
RAP Messages
RAP095E
DISPLACEMENT ENTERED IS LARGER THAN PAGE SIZE.
Reason:
The value entered in the Displacement field is larger than the page size.
Action:
Lower the Displacement value to correct this.
RAP096E
MODEL LIBRARY NOT FOUND OR FAILED OPEN.
Reason:
The model JCL library and member was not found.
Action:
Confirm the spelling and the access authorities to correct this.
RAP097E
VALID OPTIONS: (S) - TRANSFER TO PAGE DISPLAY.
Reason:
An invalid option has been selected.
Action:
Select the valid option: S for Transfer to PAGE Display.
RAP098I
DETAILED DELETION REQUEST PROCESSING ==> PLEASE STANDBY.
Reason:
Informs you that the deletes you requested are processing.
Action:
Wait until the deletion process is complete.
888 Message Reference Guide (PS to ZLB)
RAP Messages
RAP099E
VALID CMDS: (CAN)CEL, MAIN, EXIT, (PROC)ESS OR ? FOR LIST OF CMDS.
Reason:
An invalid command has been entered.
Action:
Choose one of these five valid commands: CAN, MAIN, EXIT, PROC, or ?.
RAP101E
VALID OPTIONS: (A)LL, (I)NDEX OR (N)ONE.
Reason:
An invalid option has been selected.
Action:
Choose one of these valid options: A for All, I for Index, or N for None.
RAP102E
FREQUENCY PERIOD AND PURGE LIMIT MUST BE GREATER THAN ZERO.
Reason:
The values entered in the Frequency Period or Purge Stats Older Than fields are less
than zero.
Action:
Enter values greater than zero in those fields.
RAP103I
AUTO-STATISTICS PROFILE RECORD UPDATED.
Reason:
Informs you that the changes you have made to the Auto-Statistics Profile are saved.
Note: Your editing changes will be saved only if the Auto-Statistics activation is ON.
Chapter 4: RAE to RAW 889
RAP Messages
RAP104I
Action: LIST SELECTION DISALLOWED - PDA NOT INSTALLED.
Reason:
Informs you that your action procedure selection for the Utility Manager will be ignored.
You will be able to use the action procedure as soon as the program is installed.
RAP105E
MODEL MEMBER MISSING OR EMPTY
Reason:
Your model member was not found, it contained no data.
Action:
Ensure the following:
■
Ensure that the model library exists.
■
Ensure that the model member is on the library.
■
Ensure that the member is not blank and contains at least one non-model control
card to be used as a _VJC.
Enter a MASK ('*') for the member name to get a list of members. You will then be able
to browse or edit model.
RAP106E
VALID OPTIONS: (D)ATASET, (J)ES, (B)OTH OR (P)REVIEW
Reason:
Indicates that an invalid option has been selected.
Action:
Correct this by selecting any of the following options:
■
D-Dataset.
■
J-JES.
■
B-Both.
■
P-Preview.
890 Message Reference Guide (PS to ZLB)
RAP Messages
RAP107E
VALID OPTIONS: (N)ONE OR (U)PDATE.
Reason:
An invalid option has been entered.
Action:
Select one of these two valid options: N for None or U for Update.
RAP108E
DELETION REQUESTS ARE ONLY ALLOWED IN LOCAL FRAME.
Reason:
Your deletion request refers to an invalid DB2 subsystem ID.
Action:
Confirm the DB2 subsystem ID.
RAP109E
ENTER EITHER APPLICATION PLAN OR CATALOG OBJECT NOT BOTH.
Reason:
This message appears when you try to process application plans and DB2 objects at the
same time.
Action:
You must choose which of these two you want to process first.
RAP110E
NO OBJECTS WERE FOUND.
Reason:
You will see this message when no DB2 objects can be found for the selection criteria
entered. The DB2 object may not be found if DB2 has not written its buffers to disk since
the object was created. Remember, the program accesses the actual VSAM data set
directly instead of using DB2.
Chapter 4: RAE to RAW 891
RAP Messages
RAP111E
MODEL LIBRARY MUST BE SPECIFIED.
Reason:
You must specify the library that contains the model JCL.
RAP112E
NEW VALUE NUMBER CANNOT BE LARGER THAN 2,147,483,647.
Reason:
This message displays by CATALOG Update when a new value larger than 2,147,483,647
is entered.
RAP113E
QUALIFYING CONDITION MUST BE SPECIFIED.
Reason:
This message displays if a conditional action is selected and a condition is not specified.
Action:
Specify a condition or unselect the conditional action. You may specify a condition by
beginning with a comparison operator (for example, > 90).
RAP114E
EXPLODE IS INVALID BECAUSE IMMEDIATE MESSAGE DOES NOT EXIST.
Reason:
This message occurs when you try to explode an immediate message that does not
exist.
Action:
To create an immediate message, enter Y in the Immediate Messages field.
892 Message Reference Guide (PS to ZLB)
RAP Messages
RAP115E
VALID CODES: (Y) MEMBER SPECIFIED, (U)PDATE OR (E)XPLODE.
Reason:
An invalid code has been entered.
Action:
Select one of these valid codes: Y for Member Specified, U for Update, or E for Explode.
RAP116I
Action: PROCEDURE SUCCESSFULLY COPIED.
Reason:
Informs you that the action procedure was found and copied.
RAP117E
ENTER MODEL NAME OR CANCEL.
Action:
Enter the model name or CANCEL processing.
RAP118E
VALID Action:S: ENTER, CANCEL, OR ? FOR COMMAND LIST.
Reason:
An invalid command has been entered.
Action:
Select one of these commands: ENTER, CANCEL, or ?.
RAP119E
A MESSAGE DESTINATION WAS NOT CHOSEN.
Reason:
A message has been sent without a specified destination.
Action:
Specify the message destination to correct this.
Chapter 4: RAE to RAW 893
RAP Messages
RAP120E
NO MODEL WAS CHOSEN.
Reason:
A model has not been chosen.
Action:
Specify the name of the model JCL member.
RAP121E
Action: PROCEDURE WAS NOT CREATED; INFORMATION WAS NEVER ENTERED.
Reason:
You will see this message after attempting to create an action procedure when the
Enter key was not pressed before exiting action procedure services. Pressing Enter is
required for the procedure information to be accepted and processed. The action
procedure was not saved.
RAP122E
DEFAULT SHARE OPTION OF "N" SET; OTHER VALID VALUES: "U" AND "Y".
Reason:
This message lets you know that the default share option is N for Nonshareable. You can
change this value with one of these other valid values: U for Updateable or Y for Yes for
shareable.
RAP123E
PARM OPTION IS NOT VALID SINCE NO UTILITY CODE WAS CHOSEN.
Reason:
The Parm option is invalid because a utility code was not chosen.
Action:
Choose a utility code.
894 Message Reference Guide (PS to ZLB)
RAP Messages
RAP124I
ANY REQUESTED DELETES ARE PERMANENT; CANCEL WILL NOT AFFECT THEM.
Reason:
You will receive this message when you access the Log Display Facility. Informs you that
CANCEL is not available to "undo" any requested deletes.
RAP125I
CATALOG UPDATE IS NOT SUPPORTED FOR DB2 VERSIONS 1.3 AND BELOW.
Reason:
Informs you that you are operating under DB2 V1.3 or lower and that you attempted to
update the catalog by entering catalog update or by specifying catalog update as an
option of an extract or of an action. Updating the catalog is not allowed because DB2
V1.3 and below do not allow the statistical values in the catalog tables to be updated.
RAP126I
FORMAT IS NOT SUPPORTED FOR CATALOG TABLESPACES.
Reason:
This message appears when you attempt to format a row that belongs to a catalog
tablespace. Any kind of row manipulation is not allowed on catalog tablespaces.
Statistics cannot be gathered at the column level or the FORMAT command may not be
used to format a row.
RAP127E
AT LEAST ONE PROCESS OPTION MUST BE SELECTED.
Reason:
You will see this message when you have not specified that extracts, reports, or actions
are to be processed.
Action:
Set one of these options to Y or exit the panel.
Chapter 4: RAE to RAW 895
RAP Messages
RAP128E
LOCATION CHANGED TO LOCAL DUE TO DB2 VERSION < 2.2.
Reason:
The Location ID that is specified is not LOCAL and the DB2 version is not at least 2.2. The
Location ID has been changed to LOCAL because DB2 versions earlier than V2.2 do not
support Distributed Data Facility (DDF).
RAP129E
MAXIMUM NUMBER OF PROCEDURES WHICH MAY BE CHOSEN IS 20.
Reason:
More than 254 report procedures have been chosen for a single utility code of PR. An A
has been entered next to the report procedures to select them.
Action:
If you want to choose more than 254 report procedures, use another PR utility code in
the action.
RAP130E
VALID OPTIONS: (A)CTION, (E)XPLODE, (D)ELETE, (U)PDATE, OR (L)IST.
Reason:
An invalid option has been selected.
Action:
Choose one of these five valid options:
■
E-Explode
■
D-Delete
■
L-List
■
A-Action.
■
U-Update
896 Message Reference Guide (PS to ZLB)
RAP Messages
RAP131I
Action: TIES TO OBJECTS WILL BE SEVERED - CAN TO CANCEL.
Reason:
This message appears when you have changed an extract object selection and the
following conditions apply:
■
The extract contained at least one object that was SELected, and this object had at
least one Action: tied to it, and you have specified A for AUTOBUILD for the
database or tablespace that the object belongs to.
■
Because the Action: was tied to the individual object, the Action: tie will now be
severed. This will be true for all objects in the database or tablespace selected as
AUTOBUILD that had actions tied to them.
RAP132E
LOCATION NOT FOUND FOR CURRENT SSID IN PTIPARM(SETUP).
Reason:
The current location is not LOCAL and the location name is not found for the current
SSID in the SETUP member of the data set allocated to the PTIPARM DD. This is usually
the CA parmlib.
RAP133E
LOCSSID MISSING FOR THIS LOCATION/SSID ENTRY IN PTIPARM(SETUP).
Reason:
The LOCSSID parameter is missing for the LOCATION subentry in the SSID entry. This is
specified in the SETUP member of the data set allocated to the PTIPARM DD. This is
usually the CA parmlib.
RAP134E
OPEN OF TABLESPACE SYSPLAN FAILED.
Reason:
This message appears when the PLANS or PLANAME symbolics are being processed and
the open of the catalog tablespace SYSPLAN failed.
Chapter 4: RAE to RAW 897
RAP Messages
RAP135E
MEMBER IN USE BY ANOTHER USER.
Reason:
The member you specified to contain the JCL is already in use.
Action:
Select another member or a different data set.
RAP136E
OPEN OF TABLESPACE SYSDBASE FAILED.
Reason:
This message appears when the TSSET symbolic is being processed and the open of the
catalog tablespace SYSDBASE failed.
RAP137E
ERROR OCCURRED PROCESSING TABLESPACE SET LIST.
Reason:
This message appears when the TSSET symbolic is being processed and an error
OCCURRED processing one of the tablespaces in the tablespace set list. The object in the
tablespace set list could not be found in the catalog.
RAP138E
VALID OPTIONS: (P)REVIEW, (D)ATASET, OR (J)ES SUBMISSION.
Reason:
An invalid option has been selected.
Action:
Correct this by selecting D for Dataset, J for JES submission, or P for preview. If preview
is selected, the data will be displayed under ISPF Edit. The user may modify the data;
any changes will be saved.
898 Message Reference Guide (PS to ZLB)
RAP Messages
RAP139E
EXPLODE OPTION NOT VALID FOR THIS REPORT.
Reason:
The EXPLODE option is not valid for this report type. This report is generated without
using SQL. Therefore, there is no SQL to explode.
RAP140E
SELECT ONLY ONE OPTION.
Reason:
More than one option has been selected. Select only one of the available options Reorg,
Fastscan, or Index Build, by entering S (Select) or U (Update) by the option.
Action:
To unselect an option, blank out the S or U.
RAP141E
ONE OPTION MUST BE SELECTED.
Reason:
No options have been selected.
Action:
Select at least one of the options.
RAP142E
VALID OPTIONS: (S)ELECT OR (U)PDATE.
Reason:
An invalid option has been selected. The valid options are S to select and U to update.
RAP143E
VALID OPTIONS: (S)ELECT.
Reason:
An invalid option has been selected. The valid option is S to select.
Chapter 4: RAE to RAW 899
RAP Messages
RAP144E
VALID OPTIONS: 1, 2, OR 3.
Reason:
An invalid option has been selected. The valid options are 1, 2, or 3.
RAP145E
EACH NUMBER (1, 2, OR 3) MAY ONLY BE USED ONCE.
Reason:
An option has been specified more than once. The valid options are 1, 2, and 3. Each
option may only be used once.
RAP146E
REGION MUST BE IN THE FORMAT OF 99999M OR 99999K.
Reason:
The Batch Region Size has not been specified in the correct format. The correct format is
99999M or 99999K, where K is kilobytes and M is meg.
RAP147E
DEVICE TYPE MUST BE 3350, 3380, OR 3390.
Reason:
The work data set device type is incorrectly specified. The valid values are 3350, 3380,
and 3390.
RAP148E
VALID ENTRIES FOR LOG TYPE ARE M, A, OR B.
Reason:
You will receive error message RAP when you have entered a value for Log Type that is
not valid. Valid values are M, A, or B:
■
M-User Messages only
■
A-Audit Errors only
■
B-Both types
900 Message Reference Guide (PS to ZLB)
RAP Messages
RAP149E
ONE OR MORE FIELDS MUST BE BLANKED OUT ABOVE OR BELOW (OR).
Reason:
This message appears when too many different types of DB2 objects have been entered
to be search on. Data should not be entered both above and below the OR.
RAP150E
MODEL LIBRARY NOT FOUND.
Reason:
This message appears when the Model Library is not found by dynamic allocation SVC99
routines.
Action:
Confirm that the library name is accurately spelled, that the library exists, and that the
library is catalogued.
RAP151E
VALID ENTRIES ARE: (R)EGULAR, (F)AST, (S)PACEMAP SCAN OR (N)O.
Reason:
This error message appears for invalid entries.
Action:
Choose on of the following entries:
■
R-Regular. All statistics will be collected and all audits will be done.
■
F-Fast scan only. All statistics will be collected and only those audits which are not
time intensive will be performed; no overflow pointers will be verified. If there is an
edit procedure, it will not be invoked. Therefore, F will provide the biggest savings
for tablespaces with edit procedures.
■
S-Spacemap scan only. Statistics will be collected and audits will be done on the
spacemap pages only. Any statistic which cannot be calculated from the spacemap
page will not be collected, and audits on non-spacemap pages will not be
performed. Only spacemap pages are read. Catalog update is bypassed if only
spacemap statistics are collected.
■
N-No.
Chapter 4: RAE to RAW 901
RAP Messages
RAP152E
VALID OPTION IS (D)ELETE OR (E)XPLODE.
Reason:
An invalid option has been entered. The only available options are D for Delete or E for
Explode.
RAP153E
VALID OPTIONS ARE: (D)IV OR (V)SAM.
Reason:
An invalid option has been entered. The valid options are D for DIV or V for VSAM.
RAP154E
VALID OPTIONS ARE: (R)ESTART, (B)YPASS, (C)HECK, (P)HASE.
Reason:
You will receive error message RAP154E when an invalid option has been entered. The
valid options are R for Restart, B for Bypass, C for Check Syntax, or P for Phase.
RAP155E
YOUR TSO PROFILE HAS NOPREFIX, MUST USE QUOTES ON ALL DSNAMES.
Reason:
Your TSO profile prefix option is set to NOPREFIX. One or more of the data set names in
the panel is not fully qualified with quotes, so the program cannot fully qualify the data
set name.
Action:
Use quotes on all data set names or set your TSO profile prefix to your user ID or to
some other valid value.
902 Message Reference Guide (PS to ZLB)
RAP Messages
RAP156E
VALID OPTIONS: (A)UTO-BUILD, (S)ELECTION, (T) ALL TBLS, (I) ALL IXS.
Reason:
An invalid option has been selected.
Action:
For the correct option you may choose any of the following:
■
A-Auto-build. A may be used next to databases, tablespaces, and the first partition
of a table or an index.
■
S-Select. S may be used next to any object.
■
T-All Tables. T may be used next to a database or tablespace.
■
I-All Indexes. I may be used next to a database or tablespace.
RAP157E
VALID OPTIONS: (A)UTO-BUILD, (S)ELECTION.
Reason:
An invalid option has been selected.
Action:
For the correct option you may choose any of the following:
■
A-Auto-build. A may be used next to databases, tablespaces, and the first partition
of a table or an index.
■
S-Selection. S may be used next to any object.
Chapter 4: RAE to RAW 903
RAP Messages
RAP158E
VALID OPTIONS: (A)UTO-BUILD, (T) ALL TABLES.
Reason:
An invalid option has been selected.
Action:
For the correct option you may choose any of the following:
■
A-Auto-build.
■
T-All Tables.
You cannot use I to select all indexes if indexes were not requested as part of the
selection list. To request indexes as part of the selection list, exit from the current
selection list. The Utility Build screen appears. Specify an index name or wild card in the
selection list parameters from this screen to indicate that indexes should be a part of
the selection list.
RAP159E
REPORT TYPE NOT SELECTED (ABOVE), CANNOT SELECT QUERY.
Reason:
A query has been selected for a Graph, Trend, or Forecast report, but the sub-report has
not been selected.
Action:
Select the report that is to be presented before selecting the query.
RAP160E
POSSIBLE INVALID TABLE/INDEX NAME - BLANKS NOT SUPPORTED.
Action:
Check the line the cursor is positioned on for a blank name. If a blank name is a true
table/index name, these names are not supported. If the detail line should have some
other name, contact Technical Support with the following info:
■
Screen prints showing the database, tablespace, table, creator, and index if
applicable.
■
Verification that the table/index name that should appear is not all blanks.
904 Message Reference Guide (PS to ZLB)
RAP Messages
RAP161E
VALID OPTIONS: (A)UTO-BUILD, (T)ABLES, (I)NDEXES.
Reason:
An invalid option has been selected.
Action:
For the correct option you may choose any of the following:
■
A-Auto-build. Includes all objects (for example, tablespaces, tables, indexes) in the
database.
■
T-Tables. Includes all tables in the database.
■
I-Indexes. Includes all indexes in the database.
RAP162E
VALID OPTIONS: (A)UTO-BUILD, (T)ABLES, (I)NDEXES, (E)XCLUDE.
Reason:
An invalid option has been selected.
Action:
For the correct option you may choose:
■
A-Auto-build. Includes all tables and indexes in the tablespace.
■
T-Tables. Includes all tables in the tablespace.
■
I-Indexes. Includes all indexes in the tablespace.
■
E-Exclude. Excludes all tables and indexes in the tablespace.
Chapter 4: RAE to RAW 905
RAP Messages
RAP163E
VALID OPTIONS: (A)UTO-BUILD, (S)ELECT, (E)XCLUDE.
Reason:
An invalid option has been selected.
Action:
For the correct option, choose from the following:
■
A-(Auto-build) For a table, A includes all table partitions and all indexes. For an
index, A includes all index partitions.
■
S-(Select) Includes the table only or the index only. No other partitions are included.
■
E-(Exclude) Exclude the table only or the index only. If on partition 001, E excludes
all partitions else it excludes only the partition excluded.
RAP164E
VALID OPTIONS: (S)ELECT, (E)XCLUDE.
Reason:
An invalid option has been selected.
Reason:
For lower level table and index partitions, the options you may choose are the following:
■
S-Select. Include this partition only.
■
E-Exclude. Exclude this partition only.
906 Message Reference Guide (PS to ZLB)
RAP Messages
RAP165E
OBJECT ALREADY INCLUDED OR EXCLUDED.
Reason:
This message appears when an option has been entered to include (A, T, I, or S) or
exclude (E) an object that has already been included or excluded.
With a group of objects, you can include all objects (A option), just tables (T option), or
just indexes (I option).
If a group has been included this way, you can exclude specific objects from the included
group. Thus, you can include objects in a database (A next to the database) except for a
certain tablespace (E next to the tablespace). Then, in that excluded tablespace, you can
include a particular index (A or S by the index).
When a group of objects has been included, a subordinate object cannot be included.
For instance, if a database has an A option, a tablespace in the database cannot have
the T option because all tables in the database are already included with the A option
next to the database. Similarly, if a group is excluded with the E option, a subordinate
group cannot be excluded again.
For databases:
■
A-Includes tablespaces, tables, and indexes in the database.
■
T-Includes all tables in the database.
■
I-Includes all indexes in the database.
For tablespaces:
■
A-Includes all tables and indexes in the tablespace.
■
T-Includes all tables in the tablespace.
■
I-Includes all indexes in the tablespace.
■
E-Excludes all tables and indexes in the tablespace.
For Table (1st Part):
■
A-Includes table (all partitions) and indexes in the table.
■
S-Includes this table (this partition only).
■
E-Excludes the index (all partitions).
For Index (1st Part)
■
A-Includes the index (all partitions).
■
S-Includes this index (this partition only).
■
E-Excludes this index (all partitions).
Table (Low Parts)
■
S-Includes this partition only.
Chapter 4: RAE to RAW 907
RAP Messages
■
E-Excludes this partition only.
Index (Low Parts)
■
S-Includes this partition only.
■
E-Excludes this partition only.
RAP166E
VALID OPTIONS: (E)XPLODE. CONDITION OPTIONS MAY NOT BE CHANGED.
Reason:
You have attempted to select a new action condition or change a selection for an action
condition. You entered the action condition display using explode and therefore, no
changes are allowed. The option will be reset to what it was before you altered it.
Action:
You may (E)xplode any condition. When you exit the Explode display, the option will be
reset to its original value.
RAP167E
VALID OPTIONS: (E)XPLODE, (S)ELECT, (C)ROSS CONDITION SELECTION.
Reason:
An invalid option has been entered. Valid options are as follows:
■
E-Explode. This will cause the SQL, which is used to accomplish the conditional test,
to be displayed.
■
S-Select. This will select the condition so that it is used as a test to determine if the
Action: should be generated. If several conditions are selected, the Action: is
generated if any of the conditions are true.
■
C-Cross condition selection. If C is entered next to an index (IX) type of SQL
statement, the index statistics will be used to determine if tablespace utilities are to
be generated. Each index (in the extract) that is on a table, which is in the
tablespace, will be used to determine if the Action: should be generated for the
tablespace. For each test, each index's information will be used to set symbolic
variables. As soon as an index satisfies the condition, no further indexes will be
tested, and the Action: will be generated for the tablespace.
For tables within the extract only the table's indexes will be used for the conditional
test. If the C is placed next to a tablespace (TS) type of SQL statement the tablespace
statistics will be used to determine if index utilities are to be generated.
908 Message Reference Guide (PS to ZLB)
RAP Messages
RAP168E
ENTER SPECIFIC VOLUME NAME AT VOLUME PROMPT.
Reason:
The RAP168E error message indicates that you must enter a valid volume name for the
Database prompt.
RAP169E
UR NOT VALID IN UTILITY MANAGER.
Reason:
This utility code (UR) is not valid in the utility manager.
RAP170E
VALID OPTIONS: (H)ELP FOR AUDIT ERROR.
Reason:
An invalid option has been selected.
Action:
You can use H for Help on an audit error that displays.
RAP171W
HELP FOR AUDIT ERROR IS NOT AVAILABLE.
Reason:
Indicates that the help for the audit error is not available. Help for audit errors is only
available to audit errors produced by version 2.0 and higher.
Chapter 4: RAE to RAW 909
RAP Messages
RAP172E
ACCESS VALUES: AUTO, DIV, VSAM, A/EXCP, D/EXCP, or V/EXCP
Reason:
The Access Value lets you control how DB2 objects are read. This value is used when you
submit an Extract Procedure.
Valid values are as follows:
■
AUTO-PDS will use VSAM reads only if an object is not a linear VSAM data set.
Otherwise, the DIV macro is used. Enter AUTO if you are unsure if your VSAM data
sets are linear or non-linear. However, it will cost more in overhead to check if the
data sets are linear or non-linear. AUTO is the default.
■
DIV-The Data In Virtual (DIV) macro will be used to read DB2 objects. The DIV macro
can read linear data sets only. However, you will be unable to read any non-linear
data sets. Use the DIV macro if you know the data sets are linear and the VSAM
option is not available to you.
■
VSAM-VSAM reads will be used. VSAM reads can offer performance advantages
over the DIV macro, especially when reading large tablespaces.
■
A/EXCP, D/EXCP, V/EXCP-EXCP versions of the above options cause EXecute
Channel Program (EXCP) access to be used whenever possible (currently, Regular
and Fastscan tablespace collections.) EXCP can offer performance advantages over
DIV and VSAM. Use EXCP_READ_ACCESS parmlib option to use this feature at a
'site' level without recreating the Extract JCL.
RAP173E
VOLUME SPACE MUST BE Y OR N.
Reason:
The only acceptable values for the Volume Space parameter are Y or N. The default is Y.
RAP174E
ABEND VALUE MUST BE NO OR YES.
Reason:
The only acceptable values for the Abend parameter are No or Yes. The default is No.
Note: You should only use Yes if you are instructed to do so by Technical Support.
910 Message Reference Guide (PS to ZLB)
RAP Messages
RAP175E
CYLINDERS MUST BE A VALUE FROM 1 TO 99.
Reason:
The space value entered in the Primary Cylinders or Secondary Cylinders parameter is
invalid.
Action:
Enter a value from 1 to 99. The default is 1.
RAP176E
PR IS NOT VALID FROM UTILITY MANAGER.
Reason:
PR is not valid from within Utility Manager.
Action:
Enter a valid utility code.
RAP177E
ALLOCATION ERROR.
Reason:
An error was encountered trying to allocate the data set. The message has already been
displayed by the operating system.
RAP178E
WILD CARDS NOT ALLOWED IN DIRECT SECTION.
Reason:
Direct processing requires a complete name with no wildcard characters.
Chapter 4: RAE to RAW 911
RAP Messages
RAP179E
UCB SCAN ERROR - VOLUME NOT FOUND.
Reason:
Volume name not found in scan of UCBs.
Action:
Verify the name; if it is a valid name, gather documentation showing there is a volume
mounted with this name.
RAP180E
YOU MUST ENTER RFIRST, RNEXT, OR RBACK COMMAND PRIOR TO FORMAT.
Action:
FORMAT command requires row positioning; enter RFIRST, RBACK, or RNEXT to
establish row position, then enter FORMAT.
RAP181E
ORDER FIELD MUST BE NUMERIC. VALUE WILL BE RIGHT JUSTIFIED.
Reason:
The ORD field must be all numeric. The value entered will be automatically right
justified.
This field specifies the order that the Actions are to be executed.
Action:
Enter numbers in the ORD field to number the Actions. If you add an Action after
ordering existing Actions, the new Action: is numbered one higher than the previously
highest numbered Action.
RAP182E
VALID VALUES ARE 'AND' OR 'OR'.
Action:
Enter AND to use the and connector between conditions, or OR to use the or connector.
AND implies that all conditions selected must be true, while OR implies that at least one
condition selected must be true.
912 Message Reference Guide (PS to ZLB)
RAP Messages
RAP183E
VALID VALUES ARE Y(ES) OR N(O).
Action:
Enter Y(ES) to cause all tied Actions for the old extract to be tied to the new extract as
well. Enter N(O) to prevent this.
RAP184E
COPY Action:S = Y REQUIRES COPY PROCEDURE NAME.
Reason:
When Copy Actions is Y, you must enter a name or '*' in the Copy Procedure field.
Actions cannot be copied unless the extract is copied as well.
RAP185E
EPAGE IS AN INVALID PAGE NUMBER. FIELD MUST BE NUMERIC.
Reason:
The PAGE field must be all numeric. This field specifies the page you wish to retrieve.
The page value must be overtyped to specify the desired page. For table-spaces, RID
values may be optionally input. When only the page value is entered, the beginning of
the specified page displays.
RAP186E
EROW IS AN INVALID ROW NUMBER. FIELD MUST BE NUMERIC.
Reason:
The RID field must be all numeric. This optional field specifies the row number to locate
on the page specified in the PAGE field.
RAP187E
OBJECT SSID IS REQUIRED FOR REPORT PROCEDURE.
Reason:
Object SSID is used to connect to DB2 when procedure is run and therefore is required
when defining procedure.
Chapter 4: RAE to RAW 913
RAP Messages
RAP188E
MUST SELECT A DATABASE OR INDEX.
Reason:
One of these two fields must have a value specified: DATABASE or INDEXSPACE. Supply
one or the other.
RAP189E
Action: PROCEDURE WAS NOT UPDATED; INFORMATION WAS NEVER ENTERED.
Reason:
Error message RAP189E displays after attempting to update an existing action
procedure and the Enter key was not depressed before exiting action procedure
services. Enter is required for the procedure information to be accepted and processed.
Any action procedure updates were not saved.
RAP190E
CANNOT FORMAT ROW - ROW IS DROPPED, OR CURRENT ROW NOT ESTABLISHED.
Reason:
FORMAT command requires current row positioning to be established before entering
command (RFIRST, RNEXT, RBACK). Also, it is not possible to format a dropped row.
RAP191E
PAGE IS UNFORMATTED, AUDIT BYPASSED.
Reason:
Cannot audit an unformatted page. Audit process was bypassed.
RAP192E
QC CODE IS INVALID IN UTILITY MANAGER.
Reason:
QC code is not supported in Utility Manager; enter another code.
914 Message Reference Guide (PS to ZLB)
RAP Messages
RAP193E
HEX CHARACTERS EXCEEDED IN PAGE FIELD; MAXIMUM IS 6.
Reason:
The PAGE field must contain 1 to 6 valid hex digits (0-9, A-F) when the page number is
preceded by an 'X'.
RAP194E
PAGE NUMBER CONTAINS INVALID HEX DIGITS. MUST BE 0-9, A-F.
Reason:
The PAGE field must contain 1 to 6 valid hex digits (0-9, A-F) when the page number is
preceded by an 'X'.
RAP195E
epage IS AN INVALID PAGE NUMBER.
Reason:
The PAGE field must contain 1 to 6 valid hex digits (0-9, A-F) when the page number is
preceded by an 'X'.
RAP196E
RID FIELD CONTAINS INVALID HEX DIGITS. MUST BE 0-9, A-F.
Reason:
The RID field must contain 1 to 2 valid hex digits (0-9, A-F) when the RID is preceded by
an 'X'. This optional field specifies the row number to locate on the page specified in the
PAGE field.
RAP197E
erow IS AN INVALID RID VALUE.
Reason:
The RID field must contain 1 to 2 valid hex digits (0-9, A-F) when the RID is preceded by
an 'X'. This optional field specifies the row number to locate on the page specified in the
PAGE field.
Chapter 4: RAE to RAW 915
RAP Messages
RAP198E
NOT LICENSED FOR QUICK COPY, QC Action: CODE NOT VALID.
Reason:
QC code is not valid because you are not licensed to run CA Quick Copy.
RAP199E
INVALID VALUE - USE 3350, 3380, OR 3390.
Reason:
Must use one of these values: 3350, 3380, or 3390.
RAP200E
VALID VALUES ARE R, B, C, OR A.
Reason:
Must use one of these values: R for Restart, B for Bypass Restart, C for Check Syntax, or
A for Auto Restart (blank is also valid, for no restart parm).
RAP201E
VALID VALUES ARE A(ND), O(R), N(O), OR E(XPLODE).
Reason:
Valid values are A for AND, O for OR, N for NO, or E for EXPLODE.
RAP202E
VALID VALUES ARE A(ND), O(R), N(O), U(PDATE), OR E(XPLODE).
Reason:
Valid values are A for AND, O for OR, N for NO, U for Update, or E for EXPLODE.
RAP203W
EXPLODE PROCESSING - ANY CHANGES WILL BE IGNORED.
Reason:
The action displays due to an EXPLODE request. Though the screen will allow changes,
any changes made will be ignored.
916 Message Reference Guide (PS to ZLB)
RAP Messages
RAP204E
VALID OPTIONS: (A)UTO-BUILD, (T)ABLES.
Reason:
At the Database level, the following options are allowed:
■
A-Autobuild. Includes all objects (for example, Tablespaces, Tables, Indexes) in the
Database.
■
T-Tables. Includes all Tables in the Database.
The message was displayed because an invalid option was entered. To correct the error,
blank out the option (put a space in the option field) or enter one of the options above.
RAP205E
VALID OPTIONS: (A)UTOBUILD, (T)ABLES, (E)XCLUDE.
Reason:
At the Tablespace level, the following options are allowed:
■
A-Autobuild. Includes all Tables and Indexes in the Tablespace.
■
T-Tables. Includes all Tables in the Tablespace.
■
E-Exclude. Excludes all Tables and Indexes in the Tablespace.
The message was displayed because an invalid option was entered. To correct this error,
blank out the option or enter one of the options above.
RAP206E
INVALID MEMBER NAME, CORRECT AND PRESS ENTER.
Reason:
Member name as entered is not valid and cannot be saved.
Action:
Enter a valid name before saving.
RAP207E
ENTER E(XPLODE), U(PDATE), OR Y(ES).
Action:
Enter E for Explode (no updates), U for Update, or Y for Yes (only prompt for symbolics if
one or more user symbolics are found in model).
Chapter 4: RAE to RAW 917
RAP Messages
RAP208E
VALID VALUES ARE BLANK (MEANING NOT SELECTED), OR 1-3599.
Action:
Enter blank to indicate you are not selecting this suboption. Enter a number from 1 to
3599 to indicate you are selecting this option and to specify the number of action jobs
you are requesting. This option specifies the number of jobs to generate, regardless of
the number of steps generated. Empty jobs use the MJUTLFIL model (or the model
specified on the panel). All steps pertaining to a given object are kept within the same
job, so the number of steps per job will not always be exactly equal.
Note: This option is mutually exclusive with the NUMBER OF STEPS PER JOB and NEW
JOB FOR EVERY OBJECT options. Choose one and only one of these options.
RAP209E
VALID VALUES ARE BLANK (MEANING NOT SELECTED), OR 1-200.
Action:
Enter blank to indicate you are not selecting this suboption. Enter a number from 1 to
200 to indicate you are selecting this option, and to specify the number of steps per job
you are requesting. This number is used as a guide for generating JCL; all steps
pertaining to a given object will be kept within the same job, so the actual number of
steps in each resulting job may not match exactly with this value; however, it should
never be less than this value.
Note: This option is mutually exclusive with the NUMBER OF JOBS and NEW JOB FOR
EVERY OBJECT options. Choose one and only one of these options.
RAP210E
VALID VALUES FOR ONE JOB PER OBJECT ARE Y(ES), OR N(O).
Action:
Enter blank or N to indicate you are not selecting this suboption. Enter Y to indicate you
are selecting this option. This option indicates that you want a new job for every object,
regardless of the number of JCL steps generated for the object.
Note: This option is mutually exclusive with the NUMBER OF STEPS PER JOB and
NUMBER OF JOBS options. Choose one and only one of these options.
918 Message Reference Guide (PS to ZLB)
RAP Messages
RAP211E
VALID VALUES FOR ONE MEMBER PER JOB ARE Y(ES), OR N(O).
Action:
Enter blank or N to indicate you are not selecting this option. Enter Y to indicate you are
selecting this option. This option indicates that you want a new PDS member for every
job. The member name is determined in one of the following ways:
■
If you specify an action JCL member name on the submit panel, that name is
determined by the number of jobs. If <10 jobs, one rightmost character is replaced
(0-9); if <100 jobs, two rightmost characters replaced (00-99); if <1000 jobs, three
rightmost characters replaced (000-999); else four rightmost characters are
replaced (0000-9999). For this reason, it is good practice to make the first four, five,
or six characters of the member name as unique as possible to reduce confusion.
■
If you do not specify an action JCL member name on the submit panel, the program
generates as many names as needed using the same format as before
(AMMDDxxxx) where MMDD is the month and day, and xxxx is a number from 0001
to 9999. This is the recommended method.
RAP212E
SPECIFY ONLY ONE OF: NUMBER OF JOBS OR NUMBER OF STEPS PER JOB.
Reason:
Only one of these values may be specified: NUMBER OF JOBS or NUMBER OF STEPS PER
JOB. Each of these determines how JCL is generated, but the logic used is different since
the number of jobs is unknown as the JCL is being built.
If multiple extracts are tied to an Execution Procedure and if all the extracts do not have
matching values for these parms, only one of these values is used: The highest NUMBER
OF STEPS PER JOB value is used if requested by at least one extract, OR, the highest
NUMBER OF JOBS value will be used.
A message is written to PTIMSG indicating which options are used.
RAP213E
VALID VALUES FOR ONE STEP PER UTILITY ARE Y(ES) OR N(O).
Action:
Specify ONE STEP PER UTILITY when you DON'T want utilities generated one after
another in the same JCL step, that is, REORG and RUNSTATS in the same step. When the
default is taken, or when specifying N, the program will attempt to put similar utilities
within the same JCL step.
Chapter 4: RAE to RAW 919
RAP Messages
RAP214E
THE ONLY VALID OPTIONS FOR UTILITY HISTORY REPORTS IS D (DETAIL) AND L (LATEST
1-9)
Reason:
An invalid option was selected for a Utility History report. The only valid options are D
(Detail) and L (Latest 1-9).
RAP215E
PF3 NOT ALLOWED WITH INVALID Action: CODES; CORRECT OR CANCEL
Reason:
Error message RAP215E indicates that at least one action code's stored model symbolics
do not match the current version of the model in the model library.
Action:
You must update the action code (by pressing enter) or cancel out of the update with
the CANCEL top line command.
RAP216E
LOAD FAILED FOR PTLBMOD, LOOK IN PTILIB FOR THIS MODULE.
Reason:
PTLBMOD could not be loaded using the z/OS LOAD macro. Common causes are:
module not in PTILIB, or region not available (use at least 4M, 6-8M is recommended).
RAP217E
REGION SIZE MUST BE GREATER THAN REGION REQUIRED.
Reason:
The batch region size specified is too small for the options which have been specified.
Action:
Increase the region size or decrease the options specified.
920 Message Reference Guide (PS to ZLB)
RAP Messages
RAP218E
MEMBER NAME NOT ALLOWED IN DSN FIELD, USE MEM FIELD.
Reason:
You have specified a member name in both the MEM field and the DSN field. This is not
allowed.
Action:
Remove the member name from the DSN field, and use only the MEM field for action
member names.
RAP219E
NUMBER OF STEPS PER JOB NOT VALID WITH ONE JOB PER OBJECT.
Reason:
Only one of NUMBER OF STEPS PER JOB and ONE JOB PER OBJECT may be requested.
This is because ONE JOB PER OBJECT automatically determines when a new step is
generated.
Action:
Choose the NUMBER OF JOBS option when using ONE JOB PER OBJECT (can be set to 1 if
so desired).
RAP220I
ENTER A LOCATION OR SSID AT THE APPROPRIATE PROMPT.
Reason:
This message appears when neither the LOCATION nor the SYSID fields have a valid
value on the panel. One and only one of these must be supplied.
Action:
Supply a location (to copy to a remote sysid) or a sysid (to copy to a local sysid).
Chapter 4: RAE to RAW 921
RAP Messages
RAP221I
ONLY ONE OF LOCATION AND SSID IS ALLOWED - BLANK OUT ONE OF THESE.
Reason:
This information message appears when both the LOCATION and the SYSID fields have a
valid value on the panel. One and only one of these fields must be supplied.
Action:
Supply a location (to copy to a remote sysid) or a sysid (to copy to a local sysid).
RAP222I
VALUE FOR COPY Action:S MUST BE Y(ES) OR N(O).
Reason:
An invalid value was entered for the COPY ACTIONS field. Valid values are Y for Yes or N
for No.
COPY ACTIONS requests that, as part of the process of copying the extract procedure
and its connections to action Procedures, you want to also copy the action Procedures
themselves.
RAP223I
CANNOT COPY REPORT PROCEDURES WITH EQFS.
Reason:
You have requested the copy of a report procedure that uses at least one Extended
Query Facility (EQF). EQFs cannot be copied because the possibility exists that the EQF is
not defined on the other subsystem.
RAP224I
proctype PROCEDURE "storproc" COPIED TO lsys.
Reason:
Indicates the completion of the copy.
922 Message Reference Guide (PS to ZLB)
RAP Messages
RAP225I
OPTIONAL CONDITION TABLES FOUND: actbl1 actbl2 actbl3.
Reason:
Indicates which condition tables were found in PTILIB. RAAACTB is required, but
RAAACTB1, RAAACTB2, and RAAACTB3 are optional. All tables in PTILIB are always
loaded.
If RAAACTB1, RAAACTB2, or RAAACTB3 are not found, you may receive terminal
message CSV003 indicating that one or more tables were not found. The program will
continue processing the existing tables normally.
Action:
To eliminate these terminal messages, you can assemble the RAAACTB2 and RAAACTB3
tables.
If duplicate Actions exist within the same table or different tables, only the first
occurrence of the condition will be used.
RAP226I
ONE OR MORE Action: CONDITIONS NOT FOUND IN TABLE - INVALID.
Reason:
The action procedure is invalid because it contains one or more action conditions that
do not exist in the current version of the action condition tables (RAAACTB1/2/3).
Action:
Locate the correct versions of RAAACTB, RAAACTB1, RAAACTB2, and RAAACTB3, or
update the procedure to select existing action conditions.
RAP227I
STATS MAINTENANCE IN PROGRESS, ACCESS IS BROWSE ONLY.
Reason:
The Statistics Maintenance Profile is being used by an Extract for Stats Maintenance. To
prevent losing changes, updates are not allowed until processing is completed.
Chapter 4: RAE to RAW 923
RAP Messages
RAP228I
CONDITION MUST BE N(O), A(ND), OR O(R).
Reason:
An invalid option has been selected.
Reason:
Select one of the following valid options:
■
N-No.
■
A-And (only valid when at least one Action: condition is selected.)
■
O-Or (only valid when at least one Action: condition is selected).
RAP229I
IMMEDIATE MESSAGES MUST BE Y(ES) OR N(O).
Reason:
An invalid option has been selected. Valid values are N for no, or Y for yes. Y is valid only
for conditional Actions.
RAP230I
N IS THE ONLY VALID VALUE BECAUSE NO CONDITIONS ARE DEFINED.
Reason:
Indicates that N is the only valid value for the Conditions field because no conditions are
defined for the current action.
Action:
You can enter an A or O to supply action conditions, or enter N to continue processing
without action conditions.
924 Message Reference Guide (PS to ZLB)
RAP Messages
RAP231I
COPY NOT ALLOWED WHILE UPDATINGEXISTING EXECUTION PROCEDURE.
Reason:
You cannot use the copy function while updating an existing Execution Procedure. The
copy function can only be used while creating a new Execution Procedure.
Action:
To delete Extract/Report ties from an existing Execution Procedure, enter EXPLODE D in
the command line. To add Extracts/Reports, enter the names and creators in the
PROCEDURE NAME and CREATOR fields and select them on the next screen.
RAP232I
COPY NOT ALLOWED AFTER ONE SUCCESSFUL COPY ALREADY DONE.
Reason:
You have attempted to use the copy function after having performed a successful copy.
The copy function can only be used once when you build a new procedure.
RAP233E
OPTIONS: S(TANDARD), Q(UICK)
RAP234E
INCOMPLETE OPTIONS SPECIFIED. PRESS HELP FOR INFO.
Reason:
You have selected an option that requires further processing.
Action:
Press Enter to process the options, remove the option by changing it to an N, or enter
CANCEL on the command line and press Enter to exit the panel without saving any
changes.
Chapter 4: RAE to RAW 925
RAP Messages
RAP235E
PROBLEM ENCOUNTERED PROCESSING Action: MODEL. UPDATE Action: PROC.
Reason:
The program encountered a problem when processing the action Procedure symbolic
variables. The program stores user symbolics and their values in the action Procedure
table row.
Some of the problems which may have been encountered are as follows:
The model library may no longer exist.
■
The model member may no longer exist.
■
Symbolics have been added to the model but do not have any values associated
with them.
Action:
To correct this problem, update the action Procedure with the correct information.
RAP236E
NO ROOM TO INSERT - THE MAXIMUM OF 10 CODES ARE ALREADY SPECIFIED.
Reason:
This message appears when an attempt is made to insert a blank action code line., and
there are already 10 action codes specified. A maximum of 10 action codes can be
specified.
926 Message Reference Guide (PS to ZLB)
RAP Messages
RAP237E
INVALID PARM(S) SPECIFIED. PRESS HELP FOR INFO.
Reason:
This message appears when an invalid parm was detected. Valid parms are as follows:
■
D-Delete the code from the Action: list. All remaining codes are moved up one line.
■
I-Insert an empty code at the cursor. The code on this line and all codes after this
line are moved down one line.
■
C-Copy the code to the destination line indicated by an A or B.
■
M-Move the code to the destination line indicated by an A or B.
■
A-Copy/Move the code after this line. All codes after the copied line are moved
down one line.
■
B-Copy/Move the code before this line. The code on this line and all codes after this
line are moved down one line.
■
R-Repeat the code. All codes after the repeated line are moved down one line.
RAP238E
INVALID PARM(S) SPECIFIED. PRESS HELP FOR INFO.
Reason:
This message appears when an invalid parm was detected. Valid parms are as follows:
■
E-Explode the Action: list.
■
N-Do not update the Action: line.
■
D-Delete the code from the Action: list. All remaining codes are moved up one line.
■
I-Insert an empty code at the cursor. The code on this line and all codes after this
line are moved down one line.
■
C-Copy the code to the destination line indicated by an A or B.
■
M-Move the code to the destination line indicated by an A or B.
■
A-Copy/Move the code after this line. All codes after the copied line are moved
down one line.
■
B-Copy/Move the code before this line. The code on this line and all codes after this
line are moved down one line.
■
R-Repeat the code. All codes after the repeated line are moved down one line.
Chapter 4: RAE to RAW 927
RAP Messages
RAP239E
CAN SPECIFY ONLY 1 (C)OPY/(M)OVE AND (A)FTER/(B)EFORE, OR (R)EPEAT
Reason:
This message appears when more than one Copy/Move, After/Before, and/or Repeat
parm was entered. Only one Copy/Move and corresponding After/Before or -Repeat
parm can be entered at one time.
Action:
Delete all but one Copy/Move and associated After/Before or Repeat parm.
RAP240I
COPY/MOVE IS PENDING
Reason:
This message appears when you entered a Copy/Move parm without the corresponding
After/Before parm or an After/Before parm without the corresponding Copy/Move
parm.
Action:
Enter the appropriate parm.
RAP241I
CHANGE THE INSERTED CODE TO A VALID UTILITY CODE
Reason:
This message appears after you insert a new line into the action Procedure list.
Action:
Update the utility code with a valid utility code from those listed on the Build action
Procedure screen.
928 Message Reference Guide (PS to ZLB)
RAP Messages
RAP242E
AN ACTION CODE OF PR MUST BE THE LAST ACTION CODE IN A PROCEDURE
Reason:
This message appears when you specify a PR action code and it is not the last action
code in the action procedure. When specified, a PR action code must be the last action
code in the action Procedure.
Action:
Use the Move option to move the PR action code to the last entry in the list prior to
saving the action procedure again. Otherwise, delete the PR action code by using the
Delete option.
RAP243I
CREATING A NEW PROCEDURE - ENTER QUERY SELECTION LIST PARAMETERS
Reason:
This message displays when you are attempting to create a new procedure.
Action:
Enter selection criteria to get a list of objects you can select from.
RAP244E
NOT LICENSED FOR ONLINE REORG, UR Action: CODE NOT VALID
Reason:
UR code is not valid because you are not licensed to run the product.
RAP245E
** WARNING ** ALLT AND COLSTATS=I. PRESS HELP FOR INFO
RAP246E
OBJECT SSID "obss" NOT SPECIFIED IN PTIPARM(SETUP)
Chapter 4: RAE to RAW 929
RAP Messages
RAP247E
NON-ZERO RETRUN CODE ENCOUNTERED PROCESSING Action: LIBRARY
Reason:
The program has received a non-zero return code from General Model Services while
trying to write out the generated action JCL to the specified action library.
Action:
You should ensure this library is a PDS with available space including the directory.
RAP248E
ORDER FIELD MUST BE NUMERIC. VALUE WILL BE RIGHT JUSTIFIED.
Reason:
The ORDER field must be all numeric. The value entered will be automatically right
justified.
This field specifies the relative order that the Extract and Report Procedures are to be
executed.
Action:
Enter numbers in the ORDER field to resequence|renumber the procedures. If you
change the order of any of the procedures, all procedures are resequenced according to
your specified relative order, then renumbered, that is, each procedure is given a new
relative order number once the procedures are resequenced.
RAP249I
THE PROCEDURES HAVE BEEN RESEQUENCED AND RENUMBERED.
Reason:
Appears after you change the ordering of a procedure. All procedures in the list are
resequenced according to the values you entered. All procedures in the list are then
renumbered.
RAP250E
INTERNAL ERROR: MATCHING DETAIL LINE|EBPB ENTRY NOT FOUND
Reason:
An internal error has occurred. Reordering of Extract|Report Procedures within an
Execution Procedure was performed. The program was attempting to reorder the
resequenced procedures within control blocks prior to saving the Execution Procedure.
However, a match of a detail line with a control block entry was not made.
930 Message Reference Guide (PS to ZLB)
RAP Messages
RAP252E
OBJECT TYPE IS INCOMPATIBLE WITH CURRENT EXTRACT OBJECTS
Reason:
The object type selected is incompatible with the current extract objects. Extracts built
with stogroups or volumes are not compatible with other objects.
RAP253E
INVALID WILD CARD SELECTION COMBINATION. PRESS PF1 FOR DETAILS.
Reason:
The selection criteria entered is an invalid execution time wild card (%%) input value.
Execution time wild cards are only available for Database, Tablespace and Tablespace
Creator combinations. This combination of criteria can be efficiently processed with
data from SYSTABLESPACE only. The execution time wild card characters (%%) must
appear as the last two characters of the object name. %% can be used by itself.
If an execution time wild card (%%) is specified, Table, Index, and all Creator fields
except Tablespace Creator must be blank.
A single wild card (%) is similar to a DB2 wild card and is used to define static selection
criteria. A double wild card (%%) is used to define selection criteria for objects that will
be selected at execution time. Single and double wild carded input fields cannot be
combined or mixed.
As an example, in environments such as SAP(tm), the selection criteria could be as little
as: Database => %% Tablespace => %% TSCreator => SAP%%
RAP254E
OBJECT TYPE IS INVALID
Reason:
The object type entered is invalid.
Action:
Choose one of these five valid options:
■
PK for package
■
PL for plan (without packages)
■
PP for plan (with packages)
■
ST for stogroup
■
VL for volume
Chapter 4: RAE to RAW 931
RAP Messages
RAP255E
VALID ENTRY IS: (Y)ES. PRESS HELP FOR INFO
Reason:
Appears when COLCARD field has been set to "Y" for SYSCOLUMNS and
HIGH2KEY/LOW2KEY have been set "N". The program will require that the
HIGH2KEY/LOW2KEY fields are also set to "Y" based on the importance that the IBM
puts on their correlation to COLCARD. The IBM DB2 Administration Guide describes it as
follows:
LOW2KEY and HIGH2KEY. If the COLCARD value is not '-1', the column is assumed to
have statistics, as previously mentioned. It is also assumed that the LOW2KEY and
HIGH2KEY values are accurate. They are used in filter factor calculations, as they appear
in the catalog."
RAP256E
RLOC COMMAND IS ONLY VALID WITH TYPE 2 INDEXES
Reason:
Indicates an RLOC command was attempted when the index was not a type 2. RLOC is
not possible with