Messages Guide Version 2 - IBM Supportpublib.boulder.ibm.com/tividd/td/reporter/repm1mst/en_US/...1...

ReporterMessages GuideVersion 2.0

ReporterMessages GuideVersion 2.0

TME 10 Reporter Messages Guide (March 1997)Copyright NoticeCopyright 1991, 1997 by Tivoli Systems, an IBM Company, including this documentation and allsoftware. All rights reserved. May only be used pursuant to a Tivoli Systems Software LicenseAgreement or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of thispublication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated intoany computer language, in any form or by any means, electronic, mechanical, magnetic, optical,chemical, manual, or otherwise, without prior written permission of Tivoli Systems. The document is notintended for production and is furnished “as is” without warranty of any kind. All warranties on thisdocument are hereby disclaimed including the warranties of merchantability and fitness for aparticular purpose.

Note to U.S. Government Users–Documentation related to restricted rights–Use, duplication, ordisclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.

Trademarks

The following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, IBM,NetView, Tivoli Management Environment, and TME 10.

Other company, product, and service names mentioned in this document are trademarks or registeredtrademarks of their respective manufacturers. These company, product, and service names might bedenoted by a double asterisk (**) at their first occurrence in this publication.

Notice

References in this publication to Tivoli Systems or IBM products, programs, or services do not implythat they will be available in all countries in which Tivoli Systems or IBM operates. Any reference tothese products, programs, or services is not intended to imply that only Tivoli Systems or IBM products,programs, or services can be used. Subject to Tivoli System's or IBM's valid intellectual property orother legally protectable right, any functionally equivalent product, program, or service can be usedinstead of the referenced product, program, or service. The evaluation and verification of operation inconjunction with other products, except those expressly designated by Tivoli Systems or IBM, are theresponsibility of the user.

Patents may be pending.

Version 2.0iv

Messages GuidePreface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

Understanding TME 10 Reporter MessagesIdentifying a Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Part of Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Message Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2Types of Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Finding Out What to Do with a Message . . . . . . . . . . . . . . . . . . . . . . 1-3

TME 10 Reporter MessagesPRADM Administration Messages . . . . . . . . . . . . . . . . . . . . . . . . . .2-2PRCOL Log Collector Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40PRCOM Common Messages . . . . . . . . . . . . . . . . . . . . . . . . . . .2-128PRDSP Report Generation Messages . . . . . . . . . . . . . . . . . . . . . 2-134PRGTH Data Gathering Messages . . . . . . . . . . . . . . . . . . . . . . . 2-145PRGUI Report Generation and Handling Messages—Graphical

Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-160PRINS Installation Messages . . . . . . . . . . . . . . . . . . . . . . . . . . .2-166PRREP Report Handling Messages . . . . . . . . . . . . . . . . . . . . . . . 2-191ZCCAFC Common Messages . . . . . . . . . . . . . . . . . . . . . . . . . .2-200ZCCDBC Database Interface Messages . . . . . . . . . . . . . . . . . . . . 2-201ZCCPRM Parameter File Messages . . . . . . . . . . . . . . . . . . . . . . 2-214ZCCRSS Communication Messages . . . . . . . . . . . . . . . . . . . . . .2-219ZCCTED Table Editor Messages . . . . . . . . . . . . . . . . . . . . . . . . 2-229ZCCUIC Common GUI Messages . . . . . . . . . . . . . . . . . . . . . . . . 2-231ZCCUTI Common Messages . . . . . . . . . . . . . . . . . . . . . . . . . . .2-232

Bibliography

TME 10 Reporter: Messages Guide v

AIX Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Bib-1DB2 for AIX Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bib-2ORACLE Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Bib-2NetView for AIX Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bib-3SYBASE Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Bib-3Systems Monitor for AIX Books . . . . . . . . . . . . . . . . . . . . . . . . . . Bib-3XRT/graph Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Bib-3

Glossary

Version 2.0vi

Preface

PrefaceThe TME 10 Reporter Messages Guidehelps TME 10 Reporter usersidentify and solve product problems indicated by TME 10 Reportermessages.

The guide provides explanations to all TME 10 Reporter messages.

Who Should Read This GuideThis guide is for TME 10 Reporter users who get TME 10 Reportermessages.

Related DocumentsFollowing is a list of documents related to TME 10 Reporter:

TME 10 Reporter Installation and Administration, SH19-4119

TME 10 Reporter Log Collector Guide and Reference, SH19-4121

TME 10 Reporter Reporting Dialog Guide, SH19-4120

TME 10 Reporter User's Reference, SH19-4122

The “Bibliography” on page Bib-1 lists other books that can behelpful when using TME 10 Reporter.

What This Guide ContainsUse this guide to find out what a specific TME 10 Reporter messagemeans and what to do about it.

■ “Understanding TME 10 Reporter Messages” on page 1-1 givesyou general information on the TME 10 Reporter messages.

■ “TME 10 Reporter Messages” on page 2-1 explains you eachspecific TME 10 Reporter message.

TME 10 Reporter: Messages Guide vii

Preface

Typeface ConventionsThis guide uses several typeface conventions for special terms andactions. These conventions have the following meaning:

Bold Identifies file names, commands, and flags.

Italics Identifies parameters whose actual names or values are tobe supplied by the user.

This guide may include icons in the left margin. These icons providecontext for the discussion in the text for performing a step within aprocedure. For example, if you start a procedure by double-clickingon a task icon, that icon appears in the left margin to the first step. Ifthe fourth step of the procedure instructs you to open another icon,that icon appears in the left margin next to the fourth step.

Contacting Customer SupportWe are very interested in hearing from you about your experiencewith the products and documentation in the Tivoli ManagementEnvironment. We welcome your suggestions for improvements.

If you encounter difficulties in any TME 10 product, please contactyour customer support representative. To assist you, the TME 10Framework includes the wsupport command. This command promptsyou for problem information, which can be E-mailed to your supportprovider or saved to a text file. You can then print the saved file, andfax the resulting TME Problem Report form to your support provider.See the TME 10 Framework Reference Manual for additionalinformation about the wsupport command.

If you have comments or suggestions about the TME 10documentation, please send E-mail to [email protected].

Version 2.0viii

Un

derstan

din

g R

epo

rter Messag

es

1 Understanding TME 10 ReporterMessages

This chapter explains how to read TME 10 Reporter (hereafter alsoreferred to as Reporter) messages. It tells you how to use themessages you get from Reporter and where to look for anexplanation.

Identifying a MessageTo help you identify Reporter messages easily, the message IDs areall structured the same way. This example illustrates how to identifyReporter messages:

PRADM123I

PR it is the message prefix

ADM identifies the part of the product

123 identifies the serial number of the message

I identifies the type of the message

Part of ProductReporter has several groups of messages, corresponding to thedifferent parts of the product:

ADM component installation and activation, data collection,SMIT

TME 10 Reporter: Messages Guide 1-1

Understanding Reporter Messages

COL log collector

COM common messages shared by different programs

DSP report generation

GTH data gathering

GUI report generation and handling, graphical interface

INS installation

MIG migration

REP report handling

AFC common messages shared by different programs

DBC database interface

PRM parameter file access

RSS manager—agent communication

TED table editor

UIC common GUI messages

UTI common messages shared by different programs

Message NumberThe serial number of Reporter messages range from 001 to 999 andare unique within each part of the product.

Types of MessagesReporter displays six different types of messages:

I Information messages provide feedback about somethinghappening in the product or system that might be important. Thesemessages also guide you while you are requesting specific actionfrom Reporter.

Q Query messages indicate that user input is expected.

Version 2.01-2

Un

derstan

din

g R

epo

rter Messag

es

Understanding Reporter Messages

W Warning messages call your attention to an exception conditionthat is not necessarily an error and does not require immediateaction.

E Error messages indicate that an action cannot be completed dueto user or system error. Error messages always require userresponse.

S Severe error messages are issued by the log collector andindicate that the log collector has stopped.

T Termination messages are issued by the log collector andindicate an abnormal termination of the log collector.

Finding Out What to Do with a MessageInformation messages just tell you what is going on. You do not haveto respond to them.

Query messages require user input before the program will continue.

Warning messages call your attention to an exception condition.Using these messages, you will have to decide whether they indicatean error or not.

Error messages, Severe messages, and Termination messagesmust besolved before you can go on working with Reporter. That means youhave to follow the instructions given under User response before theoperation can continue.

To find out what to do with a specific message, see “TME 10Reporter Messages” on page 2-1.


Version 2.01-4

Rep

orter M

essages

2TME 10 Reporter Messages

This chapter lists and explains Reporter messages. The messages arelisted in numeric order in these sections:

PRADM component installation and activation, data collection,SMIT

PRCOL log collector

PRCOM common messages shared by different programs

PRDSP report generation

PRGTH data gathering

PRGUI report generation and handling, graphical interface

PRINS installation

PRREP report handling

ZCCAFC common messages shared by different programs

ZCCDBC database interface

ZCCPRM parameter file access

ZCCRSS manager—agent communication

ZCCTED table editor

ZCCUTI common messages shared by different programs


PRADM Administration MessagesThis section lists PRADM messages. They appear when you arerunning data collection, when you activate Reporter, and when youare using SMIT.

PRADM001E program was stopped. The node node does notexist.

Explanation: You specified a node that does not exist.

System action: The program stops and control is returned to theoperating system.

User response: Specify an existing node or use SMIT to define anew one and rerun the command. To see a list of available nodes,select the List button in SMIT.

PRADM002E program was stopped. The node group nodegroup does not exist.

Explanation: You specified a node group that does not exist.


User response: Specify an existing node group or use SMIT todefine a new one and rerun the command. To see a list of availablenode groups, select the List button in SMIT.

Version 2.02-2

Rep

orter M

essages

PRADM003E program was stopped. The log log does not exist.

Explanation: You specified a log that does not exist.


User response: Specify an existing log or issue the log collectorcommand prlogcol to define a new one and rerun the command. Tosee a list of available logs, select the List button in SMIT.

PRADM004E program was stopped. The component componentdoes not exist.

Explanation: You specified a component that does not exist.


User response: Specify an existing component or issue thecommand pradmcomp to define a new one and rerun the command.To see a list of available components, select the List button in SMIT.

PRADM005I program: The log or component name on thenode node is already active.

Explanation: The named log or component is not activated becauseit is already active.

System action: Processing continues normally.

User response: If the log or component already that is active is theone you need, no action is required.


PRADM006I program: The log or component name on thenode node is not active.

Explanation: The named log or component is not deactivatedbecause it is already inactive.


User response: If the log or component already that is inactive isthe one you need, no action is required.

PRADM007E program: The file file does not exist.

Explanation: The named log file does not exist on the node.

System action: The log file is not transferred nor data is collected.

User response: Ensure that the gathering program on the agent isactive. If the log type (the second part of the file name) is perf ordisk, then run the prpsperfd command on the agent to check that theprperfd daemon is still running. If it is not, examine the file/var/perfrep/node-name.prperfd.errorlog for a description of theprperfd daemon. If it is another log type, first check that it shouldrun, using the command crontab -l on the agent. Also refer to/var/perfrep/node-name.prgather.log for any error messages.

PRADM008E program: The transfer of the file file was notsuccessful.

Explanation: An error prevented the file from being transferredfrom the agent to the manager. Previous messages give additionaldetail on the cause of the error.

System action: The error is bypassed and processing continues.

User response: Ensure that the rshsrv daemon is running on theagent and verify that the communication is set up as a trusted host.

Version 2.02-4

Rep

orter M

essages

See also the preceding messages generated by rshcli. Note thatrshsrv must be started by root. Verify the communication with thecommand /usr/lpp/perfrep/bin/rshcli -h node hostname.

PRADM009I program: The log log for the date date wastransferred and collected on the nodes: nodes.

Explanation: The log file was transferred to the manager andcollected in the database.


User response: None.

PRADM011E program: Node group and node name are bothspecified.

Explanation: Conflicting input; node group and node name cannotbe specified at the same time.


User response: Specify either the node name or group.

PRADM012E program: The argument argument is notsupported for the flag -o.

Explanation: The named argument is not supported for the namedflag.


User response: Rerun the command using the correct argument. Ifyou do not know which argument to use, look in the


/usr/lpp/perfrep/prdbaccess or /usr/lpp/prdbcalender files. Searchfor the appropriate option in the file and see which variables it uses.

PRADM013E program: The installation was not successful.The program program ended with the return coderc.

Explanation: The installation of a component failed. The programthat The program that detected the problem gives a return code thatcan be used for problem determination in conjunction with errormessages issued previously.


User response: Use the log produced by the installation program todetermine the cause of the problem. The log is in the /var/perfrepdirectory and is named prinstcomponent_name.log. It traces theinstallation process and shows where the error occurred. Beforererunning the installation, ensure that you can connect to thedatabase. Note that after any installation failure, you must uninstallthe component before reinstalling.

PRADM014E program: The component component cannot beinstalled because its install status is Y.

Explanation: You cannot install a component that is alreadyinstalled (install status = Y).


User response: No action is required, but if the component shouldbe reinstalled for any reason you must uninstall it before installingagain.

Version 2.02-6

Rep

orter M

essages

PRADM015E program: The uninstall was not successful. Theprogram program ended with the return code rc.

Explanation: The uninstallation of a component failed. Theprogram that detected the problem gives a return code that can beused for problem determination in conjunction with error messagesissued previously.


User response: Use the log produced by the uninstallation programto determine the cause of the problem. The log is in the /var/perfrepdirectory and is named prdeinstcomponent_name.log. It traces theinstallation process and shows where the error occurred. Beforererunning the uninstallation ensure that you can connect to thedatabase.

PRADM016E program: The component component cannot beuninstalled because its install status is N.

Explanation: You cannot uninstall a component that is alreadyuninstalled (install status = N).




PRADM017Q Press Enter to exit, or type any nonblankcharacter to display the log file file.

Explanation: You can view the log file on the screen by pressingEnter. The log file is in the /var/perfrep directory or in your homedirectory.

System action: The program waits for input.

User response: Enter input as required.

PRADM018Q Type the dbms password for user ID. It will notbe displayed.

Explanation: During some database transactions the Reporteradministrator must log on to the database. These are examples ofsuch transactions: set up database, install component, and uninstallcomponent.

System action: The program waits for input.

User response: Type the password.

For... The password is...

DB2 The AIX password for the AIX user ID that correspondsto the table prefix

ORACLE The ORACLE password of the ORACLE user ID thatcorresponds to the table prefix. If the current user ID isthe same as the table prefix, no password is required. Thisuser ID has to be authorized by operating system.

SYBASE The SYBASE password of the SYBASE user ID thatcorresponds to the table prefix.

Version 2.02-8

Rep

orter M

essages

PRADM019I program: The component component wasuninstalled successfully.

Explanation: All parts of the component are uninstalled. Allreports, data tables, and log collector definitions are removed.



PRADM020E program: An error occurred when running thecommand command on the node node.

Explanation: The remote command issued for the named nodefailed. If the command involves multiple nodes, processing continueswith the next node. This message is followed by another messagegiving additional information on the type of error.

System action: If the command involves multiple nodes, processingcontinues with the next node; in other cases control is returned to theoperating system.

User response: Use the additional message to perform problemdetermination before reissuing the command. In addition, ensure thatthe rshsrv daemon is running on the agent and verify that thecommunication is set up as a trusted host. Note that rshsrv must bestarted by the root user. Verify the communication with thecommand: /usr/lpp/perfrep/bin/rshcli -h node hostname. Alsoexamine any additional error messages from the remote command forfurther analysis.


PRADM021I program: The log log is activated on the nodenode.

Explanation: The activate command issued against the named nodewas successful. Log files are created on the node.



PRADM022I program: The log log is deactivated on the nodenode.

Explanation: The deactivate command issued for the node wassuccessful. Log files will no longer be created on the node.



PRADM023I Node, NodeGroup, Log and Component canhave the keyword 'All'.

Explanation: This message is preceded by message PRCOM001Ewhich describes the syntax of the command.


User response: Specify the keyword All for nodes, node groups,logs, components, when the action is required on all of them.

Version 2.02-10

Rep

orter M

essages

PRADM026I program: The log log for the date date wastransferred from nodes: nodes.

Explanation: The log files were transferred from the named nodesto the manager.



PRADM027I program: The log log for the date date wascollected for node(s): nodes.

Explanation: The log files were collected in the database.



PRADM028I program: Nothing was processed on node node.

Explanation: Activation or deactivation has failed for the nodes.This message is followed by other messages that give additionalinformation on the type of error.

System action: The error is bypassed and processing continues.

User response: Use all the messages to perform problemdetermination and take the appropriate action.


PRADM030I program: The component component issuccessfully installed.

Explanation: All reports, data tables, and log collector definitionshave been created. The component can now be activated on nodes,data collection can be started, and reports can be displayed.



PRADM031E program: The uninstallation program for thecomponent component is not found.

Explanation: An attempt was made to uninstall a component butthe uninstallation program for this component was not found. Eitheryou do not have access to the database or the named program doesnot exist.


User response: Ensure that you have access to the database and thatthe program is defined.

PRADM032E program: The installation program for thecomponent component is not found.

Explanation: An attempt was made to install a component but theinstallation program for this component was not found. Either you donot have access to the database or the named program does not exist.


User response: Ensure that you have access to the database and thatthe program is defined.

Version 2.02-12

Rep

orter M

essages

PRADM033I The system is uninstalling the componentcomponent, please wait.

Explanation: The component is being uninstalled and no action isrequired on the user's part.



PRADM034Q Press Enter to exit.

Explanation: The program will end when you press the Enter key.

System action: The system waits for your input.


PRADM036E No action performed on the componentcomponent because it is not installed.

Explanation: The action you are trying to perform requires that thecomponent.


User response: Ensure that the correct syntax for the componentwas entered, or install the component before you issue this commandagain. You can list all components and their status using SMIT (issuesmit perfrep.inst.comp.ls on the command line).


PRADM042E The parameter parameter in the section sectionis not updated.

Explanation: The command zccparmset failed. This messagefollows another message that described the cause of the error.

System action: The request is ignored and processing continues.

User response: Ensure that you have write access to the parameterfile. The parameter file is set by the environment variableZCCPARM, by default /etc/perfrep/perfrep.cfg. In addition, use thepreceding message to perform problem determination

PRADM043E The requested parameter in the parameter filecannot be updated on the node node.

Explanation: An attempt was made to update a parameter that isnot applicable to the node. This parameter can only be updated on amanager node.



PRADM044E program: The buffer size of n bytes is incorrect.

Explanation: An invalid value was entered for the log collectorbuffer size (in bytes).


User response: Specify the buffer size with a numeric value andrerun the command.

Version 2.02-14

Rep

orter M

essages

PRADM045I program: No node is specified.

Explanation: The keyword All for all nodes is specified but nonodes exist, so no task is performed.

System action: The command is not run.

User response: Create nodes using SMIT and rerun the command.

PRADM046E program: You cannot write to the directorydirectory.

Explanation: You do not have write permission to the directorywhere the log files are stored on the agent node.


User response: Ensure you have write permission to this directory.

PRADM047W program: The log type type is not supported onthe platform platform.

Explanation: HP and Sun do not support all provided logs. Therequested log type is not supported.

System action: The log is not activated on the HP or Sun node.



PRADM050E The update definition for the table table is notdisplayed.

Explanation: The update definition for the table cannot bedisplayed because there is no update definition defined for this table.

System action: No update definition is listed and control is returnedto the operating system.

User response: If you need and update definition for the table seethe Log Collector Guide and Referenceto add update definitions.

PRADM052E The table table is not a Reporter data table.

Explanation: The named table name is not recognized as a Reporterdata table.

System action: The request is not processed and control is returnedto the operating system.

User response: Enter input as required. Valid table names are listedin SMIT. To see them, issue smit perfrep.op.table.ls on thecommand line.

PRADM053E The report report does not exist.

Explanation: The specified report name does not exist.


User response: Enter input as required. Valid values are listed inSMIT. To see them, issue smit perfrep.rep.ls on the command line.

Version 2.02-16

Rep

orter M

essages

PRADM054E program: Cannot write to the log file file.

Explanation: You do not have write permission to the installationor uninstallation log file.

System action: The component is not installed or uninstalled.

User response: Ensure that you have write access to the directoryspecified by the logPath parameter before rerunning this program. Bydefault this is the /var/perfrep directory. This command is normallyrun by the Reporter administrator, default user ID perfrep. This userID should be part of the UNIX group adm. The adm group shouldhave write access to the logPath directory (/var/perfrep ). If anotheruser has run this program, the installation or uninstallation log, forexample /var/perfrep/prinstsample.log, could already exist. If this isthe case, delete the file or make sure that the current user ID haswrite access to this file.

PRADM056E program: The argument argument for the flag -ois incorrect (return code=rc).

Explanation: You specified an invalid argument for the named flag.


User response: The return code is returned from a command usedby the argument in the script. Most likely it comes from a failure of azccdbcmd call (return codes: 1, 2, 101 - 199). If this is the case,check your database access and rerun the command.


PRADM057I The log deactivation completed successfully.

Explanation: The log is deactivated on the requested node.

System action: The log will no longer be created on this node.


PRADM058I Running pradmcoll -d -c program -n All. Pleasewait.

Explanation: The pradmcoll program is running to deactivate thenamed component on all nodes.



PRADM059I Installing the component component, please wait.

Explanation: The component is being installed.



PRADM070I The component component has active logs on thenodes nodes.

Explanation: An attempt was made to remove log collector/reportsdefinitions from the database but the named component is active onthe nodes. If you continue the uninstallation of the component, datacollection will be stopped and all collected data will be deleted.


Version 2.02-18

Rep

orter M

essages

User response: You could either stop the uninstallation process orcontinue the uninstallation and have the component deactivated on allnodes.

PRADM071Q Press Enter to exit, or type any nonblankcharacter to continue the deinstallation anddeactivate the logs.

Explanation: You can choose whether to continue uninstallation.


User response: To stop the uninstallation and keep everythingunchanged, press Enter. If you type a nonblank character, theuninstallation will continue and the component will be deactivated onall nodes.

PRADM075I The size information is not available.

Explanation: The size information cannot be displayed because it isnot available in the SYBASE database.

System action: Size information is not displayed and processingcontinues normally.


PRADM076I Loading the table editor.

Explanation: The table editor program is loading the table. Bigtables require some time to be loaded.




PRADM078E program: You are not authorized to updatestatistics in the data dictionary data dictionary.

Explanation: You have to be a database administrator to update thestatistics in the data dictionary.

System action: The data dictionary statistics are not updated andprocessing continues.

User response: Request authorization from the systemadministrator.

PRADM079E program: No query file was found for the reportreport.

Explanation: No query file is found for the report.


User response: Add a query file to this report by using thereporting dialog or the Modify report definition dialog of SMIT (entersmit perfrep.rep.mod on the command line).

PRADM090E program: The query file file was not found inany of the following directories directories.

Explanation: The query file cannot be found in any directoryspecified by the repPath parameter.


User response: Choose one of the following actions:

■ Locate the query file and move the file to a directory in therepPath parameter.

Version 2.02-20

Rep

orter M

essages

■ Add the directory to the repPath parameter.

■ Update the report definition using the reporting dialog or SMIT(enter smit perfrep.rep.mod on the command line).

PRADM091I The accounting group (node group) node groupdoes not exist.

Explanation: An attempt was made to add a node to a node groupthat does not exist. Every node must be associated with a node groupfor accounting purposes.


User response: Select List and, from the list, select a node group touse as an accounting group. If no suitable node group exists, createone before you continue.

PRADM092I The node node is added.

Explanation: This is a confirmation that the node was successfullyadded.



PRADM093I The node group node group is added.

Explanation: This is a confirmation that the node group wassuccessfully added.




PRADM094I The node node is added to the node group nodegroup.

Explanation: This is a confirmation that the node was successfullyadded to the node group.



PRADM095I The node node is removed from the node groupnode group.

Explanation: This is a confirmation that the node was successfullyremoved from the node group.



PRADM096I The node node is updated.

Explanation: This is a confirmation that the node was successfullyupdated.



Version 2.02-22

Rep

orter M

essages

PRADM097E You are not authorized to update the systemtables tables.

Explanation: Only the Reporter administrator can insert, update,and delete system tables.


User response: Request this type of operation to the Reporteradministrator.

PRADM098I The node group node group is updated.

Explanation: This is a confirmation that the node group wassuccessfully updated.



PRADM099I The node group node group is deleted.

Explanation: This is a confirmation that the node group wassuccessfully deleted.




PRADM110E The node group node group cannot be deleted.

Explanation: The node group cannot be deleted because it containsone or more nodes.


User response: A node group can be removed only if no nodesexist in the group. Before deleting node group, use SMIT to removeall nodes from the node group (enter smitperfrep.nodes.remfromgrp on the command line).

PRADM112E The node group node group was not deletedbecause it is the accounting group for the nodesnodes.

Explanation: The node group you are trying to delete is used as theaccounting group for a number of nodes. You must modify the nodesbefore you delete the named node group.

System action: The request is not processed and control is returnedto the operating system. You must modify the nodes before youdelete the %s node group.

User response: Use SMIT to modify the nodes listed that have thenode group as accounting group. Enter smit perfrep.nodes.modnodeon the command line. Update the field accounting group to a nodegroup that you are not going to delete.

Version 2.02-24

Rep

orter M

essages

PRADM114I The following components are active on thenodes in the node group node group:

Explanation: This message is followed by a list of activecomponents.



PRADM115I The following logs are active on the nodes in thenode group node group:

Explanation: This message is followed by a list of active logs.



PRADM116I Loading the reporting dialog.

Explanation: Waiting for the reporting dialog program to be loaded.



PRADM117I The node node is deleted.

Explanation: The node was successfully deleted.




PRADM118E The node node is not part of the node groupnode group.

Explanation: The node is not deleted because it does not belong tothe group of nodes that you specified.


User response: Select List to get a list of all nodes that are part ofthe node group before requesting this command again.

PRADM119E A node already exists with the name node,domain name domain name, or IP address IPaddress.

Explanation: The node was not added because the node name,domain name, and IP address fields are already defined.


User response: Use values that are unique. Select List to get a listof all existing node names, domain names, and IP addresses.

PRADM120I Creating tables and log collector definitions.

Explanation: The request to create data tables for the component isin progress.



Version 2.02-26

Rep

orter M

essages

PRADM121I Creating report definitions.

Explanation: The request to create report definitions for thecomponent is in progress.



PRADM122I Updating component information.

Explanation: The request to update component information duringinstallation is in progress.



PRADM123I Deleting tables and log collector definitions.

Explanation: The request to delete tables and log collectordefinitions for the component is in progress.



PRADM124I Deleting report definitions.

Explanation: The request to delete report definitions for thecomponent is in progress.




PRADM125I Updating component information.

Explanation: The request to update component information duringinstallation is in progress.



PRADM127E program: Connection to database was notsuccessful.

Explanation: The program zccdbcmd did not connect to thedatabase.


User response: Ensure that the DBMS environment variables andthe dbSetup parameter are correct before rerunning the command. ThedbSetup parameter must refer to a file containing the DBMSenvironment variables. See the files prdb2profile , oraenv, orprsybprofile in the directory /etc/perfrep for the environmentvariables that need to be set.

PRADM130E The name of the node group is to be unique.

Explanation: The node group was not added because it alreadyexists.


User response: Use names that are unique. Select List to get a listof all existing node names before rerunning the command.

Version 2.02-28

Rep

orter M

essages

PRADM134E The calendar object day - day period day perioddoes not exist.

Explanation: An attempt was made to delete the day period, but itdoes not exist in the database.


User response: Select List to get a list of existing periods beforererunning the command.

PRADM135I The calendar object day - day period day period isupdated.

Explanation: The day period was updated.



PRADM136I The calendar object day - day period day period isdeleted.

Explanation: The day period was deleted.




PRADM137I The calendar object day - day period day period isadded.

Explanation: The day period was added.



PRADM141E The time time is not in the correct format.

Explanation: The time is not in the correct format; the correctformat is hh.mm.ss (00.00.00 - 23.59.59).


User response: Enter the time in the correct format.

PRADM143Q Press Enter to exit, or type any nonblankcharacter to delete the day type.

Explanation: Days of week, day periods, and special days will bedeleted after confirmation.

System action: The system waits for input.


Version 2.02-30

Rep

orter M

essages

PRADM144E The day type was not deleted because the filefile was not accessed.

Explanation: The day type was not deleted because you do nothave write access to the file.

System action: The request is not processed.

User response: Request authorization from the system administratorbefore running the command again.

PRADM145E The component was not uninstalled because alog deactivation was not successful.

Explanation: An error occurred during the deactivation process.Preceding messages give additional information on the error.

System action: The component is not uninstalled and control isreturned to the operating system.

User response: Use the information given in the precedingmessages to perform problem determination.

PRADM146I Checking the component component, please wait.

Explanation: Current status of the component component is checkedbefore the activation or deactivation continues.




PRADM147I The node node cannot be deleted because it hasactive logs.

Explanation: An attempt was made to delete a node that has activelogs.


User response: Use SMIT to deactivate the logs for the node beforedeleting the node (enter smit perfrep.inst.deact.log.node on thecommand line).

PRADM149I The day type day type does not exist.

Explanation: An attempt was made to list a day type that does notexist.



PRADM150E The day period day type, start time is not addedbecause it already exists.

Explanation: An attempt was made to add a day period but italready exists in the database.



Version 2.02-32

Rep

orter M

essages

PRADM151I The day type day type does not exist.

Explanation: An operation was requested on a day type but it doesnot exist in the database.

System action: The program stops.

User response: Enter valid data before rerunning this commandagain.

PRADM152I The day day of the week is added.

Explanation: The day was added to the data base.



PRADM153E The day day of the week was not added becauseit already exists.

Explanation: An attempt was made to add a day that already existsin the database.



PRADM154I The day type day type is added.

Explanation: The day type was added to the database.




PRADM155E The day type day type was not added because italready exists.

Explanation: An attempt was made to add a day type that alreadyexists in the database.



PRADM156I The special day day is added.

Explanation: The special day was added to the database.



PRADM157E The special day day was not added because italready exists.

Explanation: An attempt was made to add a special day thatalready exists in the database.



Version 2.02-34

Rep

orter M

essages

PRADM159I The day day of the week does not exist.

Explanation: An operation was requested on a day of week thatdoes not exist in the database.


User response: Enter valid data before running this command again.

PRADM160I The day type day type is used in the followingdays of the week:

Explanation: An operation was requested on selected days of aweek. This is the header displayed for those day types.



PRADM161I The day type day type is used in the followingday periods:

Explanation: An operation was requested on selected day periods.This is the header displayed for those day periods.




PRADM162I The day type day type is used in the followingspecial days:

Explanation: An operation was requested on selected day types.This is the header displayed for those day types.



PRADM163I The day type day type is not deleted.

Explanation: The day type is not deleted because the request wascanceled.



PRADM164I The day type day type is deleted.

Explanation: You requested to delete the day type.



PRADM165I The special day day does not exist.

Explanation: An operation was requested on a special day that doesnot exist in the database.



Version 2.02-36

Rep

orter M

essages

PRADM166I The special day day is deleted.

Explanation: You asked to delete a special day.



PRADM167I The day type day type is not defined.

Explanation: An operation was requested on a day type that doesnot exist in the database.



PRADM168I The day day of the week is updated.

Explanation: The named day of the week is updated.



PRADM169I The day type day type is updated.

Explanation: The named day type is updated.




PRADM170I The special day day is updated.

Explanation: The named special day is updated.



PRADM171E The operation cannot be performed on the nodenode.

Explanation: The requested operation cannot be performed on thenode because the parameters entered are only applicable to agentnodes.



PRADM172E The DynaText books cannot be found in thepath path.

Explanation: The documentation package is not installed or theparameter bookPath is set to the wrong directory.


User response: Install the documentation package or correct theparameter bookPath.

Version 2.02-38

Rep

orter M

essages

PRADM178E program: The query file file is not qualified by afull path name.

Explanation: The report cannot be edited because the query filemust be specified with a full path name.


User response: Specify a full path name for the report to be editedin the query field of the report definition.

PRADM181I The day day of the week is deleted.

Explanation: The named day of the week is deleted.




PRCOL Log Collector MessagesThis section lists the PRCOL messages. They are displayed when thelog collector is running.

PRCOL003I

Explanation: This message is used to insert a blank line betweenother messages. (For an example, see Figure 1 on page 2-126.)

PRCOL007S text is not a valid variable definition.

Explanation: text is supplied as a parameter to the log collector. Itis supposed to define a log collector variable. However, text is not avalid variable definition.

System action: The log collector stops without processing anystatements.

User response: Refer to Reporter Log Collector Guide andReference for a description of how to invoke the log collector.Correct the parameter.

Version 2.02-40

Rep

orter M

essages

PRCOL011E Information about update update in system tablesystem table is damaged. Restore the updatedefinition.

Explanation: The contents of the system table system table aredamaged, perhaps because something other than the log collector wasused to update the table. The damaged information is a part of thedefinition of the update update. The definition cannot be used.

System action: The log collector stops processing the currentstatement and continues with the next.

User response: Execute the DROP UPDATE and DEFINEUPDATE statements for the update update to restore the definition.

PRCOL012E Information about record record in system tablesystem table is damaged. Restore the recorddefinition.

Explanation: The contents of the system table system table aredamaged, perhaps because something other than the log collector wasused to update the table. The damaged information is a part of thedefinition of the record record. The definition cannot be used.


User response: Execute the DROP RECORD and DEFINERECORD statements for the record record to restore the definition.


PRCOL015E The update update is not at the current level.Redefine it using the current version of logcollector.

Explanation: The update definition was stored using an olderversion of the log collector, and was not migrated to the current level.It cannot be used with the current version of the log collector.


User response: Execute the DROP UPDATE and DEFINEUPDATE statements for the update update to restore the definition.Alternatively, run the migration program.

PRCOL021E The file file could not be opened.

Explanation: The log collector cannot open the file file.


User response: Ensure that the file exists and can be opened.

PRCOL024E Permanent I/O error encountered after nrecords in file file.

Explanation: The log collector encountered an I/O error after nrecords in the file file.


User response: Check the output for more messages about the error.Study the cause of the error and act accordingly.

Version 2.02-42

Rep

orter M

essages

PRCOL031E The statement "text" is not recognized.

Explanation: The text appears in a place where a statement name isexpected. However, it is not the name of any statement of the logcollector language.


User response: Check the syntax diagram in Reporter Log CollectorGuide and Referenceand correct the statement. Notice that thedifferent clauses of the statement must be written in the order shownin the diagram. Notice also that the error might be located muchearlier in the input than the token text. A large portion of inputextending past the error might still conform to the syntax. Themessage identifies the point where the input no longer matches thesyntax.

PRCOL032E The variable variable does not exist.

Explanation: The input text contains a variable marker &variable,but the variable variable is not defined.


User response: Specify a value for the variable at the invocation ofthe log collector, or by executing the SET statement. Notice that allvariables are dropped at the end of the log collector run.


PRCOL033E The expression or condition starting with text istoo long or too complex.

Explanation: Either the text of the expression or condition, or itsinternal representation is longer than 2000 characters.


User response: Try to simplify the expression or condition. Is itpart of an update definition? Then you can break out parts of theexpression and put them in the LET clause.

PRCOL034E "text" is not a valid variable marker.

Explanation: The text begins with an ampersand, but is not a validvariable marker. A variable marker consists of an ampersand (&)followed by an identifier.


User response: Correct the variable marker.

PRCOL035E An invalid field format "text" is specified forfield field.

Explanation: text was specified as the field format for the fieldfield, but it does not identify any field format known to the logcollector.


User response: Refer to Reporter Log Collector Guide andReference for a list of valid field formats.

Version 2.02-44

Rep

orter M

essages

PRCOL036E The offset of the field field is undefined. Offsetmust be specified when the previous field format isCHAR(*).

Explanation: The offset of field has been omitted. The offset cannotbe determined because the previous field has the format CHAR(*),and no field can follow a field with that format.


User response: Add an offset specification for the field.

PRCOL037E The format specified for the field field conflictswith the length of the field.

Explanation: A given format can only be specified for fields ofcertain lengths. For example:

■ DATE(YYMMDD) can only be specified for a 6-byte field.

■ EXTERNAL FLOAT can only be specified for a field no longerthan 32 bytes.

■ CHAR(*) can only be specified for a varying-length field (afield with LENGTH *).


User response: Refer to Reporter Log Collector Guide andReference for information about the lengths allowed for different fieldformats. Ensure that the format agrees with the length specification.


PRCOL038E "text" is not a valid integer constant.

Explanation: The token text looks like an integer constant, but isnot a valid integer constant (for example, its value is outside therange of integers).


User response: Correct the constant.

PRCOL039E "text" is not a valid floating-point constant.

Explanation: The token text looks like a floating-point constant, butis not a valid floating-point constant (for example: the exponent isincomplete or is outside the allowed range).


User response: Correct the constant.

PRCOL040E Syntax error: unexpected text "" (two quotationmarks) is found.

Explanation: Two consecutive quotations marks were found wherethey are not allowed by the syntax. Consecutive quotation marks areallowed only within a delimited identifier, string constant, orcomment.


User response: Correct the error.

Version 2.02-46

Rep

orter M

essages

PRCOL041E Syntax error: unexpected text "text" is found.

Explanation: The token text was found where it is not allowed bythe syntax.


User response: Check the syntax diagram in Reporter Log CollectorGuide and Referenceand correct the statement. Notice that differentclauses of the statement must be written in the order shown in thediagram. Notice also that the error might be located much earlier inthe input than the token text. A large portion of input extending pastthe error might still conform to the syntax. The message identifies thepoint where the input no longer matches the syntax.

PRCOL042E Syntax error: unexpected text "text1" is foundafter "text2".

Explanation: The token text2, which conforms to the syntax, wasfollowed by the token text1. The syntax does not allow this sequence.


User response: Check the syntax diagram in Reporter Log CollectorGuide and Referenceand correct the statement. Notice that differentclauses of the statement must be written in the order shown in thediagram. Notice also that the error might be located much earlier inthe input than the token text1. A large portion of input extending pastthe error might still conform to the syntax. The message identifies thepoint where the input no longer matches the syntax.


PRCOL043E Syntax error: "text1" found where text2 isexpected.

Explanation: The token text1 was found where it is not allowed bythe syntax. The text2 states what the syntax allows in place of text1.



PRCOL044E Syntax error: "text1" found after "text2", wheretext3 is expected.

Explanation: The token text1 was found followingtext2, where it isnot allowed by the syntax. The text3 states what the syntax allows inplace of text1.



Version 2.02-48

Rep

orter M

essages

PRCOL045E The identifier starting with text is too long. Themaximum length is 18 bytes.

Explanation: An identifier cannot exceed 18 bytes. The length of adelimited identifier ("identifier") does not include the enclosingquotation marks.


User response: Change the identifier.

PRCOL046E The string starting with text is too long. Themaximum length is 254 bytes.

Explanation: The string specified by a constant cannot exceed 254bytes.


User response: Change the string.

PRCOL047E The delimited identifier starting with text is notterminated.

Explanation: A delimited identifier ("identifier") without an endingquotation mark (") was found.


User response: Add the quotation mark (") at the end of theidentifier.


PRCOL048E The string starting with text is not terminated.

Explanation: A string constant without an ending apostrophe (')was found.


User response: Add the apostrophe (') to the end of the stringconstant.

PRCOL049E An invalid character, hexadecimal cc, is found.

Explanation: This character is only allowed inside a string constant,delimited identifier, or comment. It was found outside theseconstructs.


User response: Refer to Reporter Log Collector Guide andReference for information which characters are allowed outside ofstring constants, delimited identifiers, and comments. Correct thecharacter.

PRCOL050E An invalid character, hexadecimal cc, is foundafter "text".

Explanation: This character is only allowed inside a string constant,delimited identifier, or comment. It was found outside theseconstructs, after the text text.


User response: Refer to Reporter Log Collector Guide andReference for information which characters are allowed outside of

Version 2.02-50

Rep

orter M

essages

string constants, delimited identifiers, and comments. Correct thecharacter.

PRCOL051E The preceding n message(s) refer to theexpression for name.

Explanation: This message helps you locate the errors indicated bythe messages issued before this message. If name is the nameappearing to the left of an equal sign in a LET, GROUP BY, or SETclause, the messages apply to the expression appearing to the right ofthat equal sign. If name is a language keyword such as WHERE orOFFSET, the messages apply to the expression following thatkeyword.


PRCOL052E The expression is too complex.

Explanation: An expression contains a nested structure of a depththat exceeds the capacity of the log collector. There are two kinds ofnested structures: the parentheses and the constructs involvingalternatives (the VALUE function and case expressions).

The nesting depth of parentheses at a given point is equal to thenumber of pairs of parentheses enclosing that point. The parenthesesinclude those that are a part of function calls with more than oneargument and the implicit parentheses inserted to enforce theprecedence of operations. For example, A*B+C*D has these implicitparentheses: (A*B)+(C*D).

The nesting depth of alternative structures at a given point is thenumber of nested VALUE calls and case expressions containing thatpoint, plus the number of preceding arguments within each VALUEcall, plus the number of preceding THEN clauses within each caseexpression.


This message indicates that one or both of these nesting depthsexceed the maximum that can be handled by the log collector.


User response: Use the subsequent message PRCOL051E toidentify the expression in error. If possible, define parts of theexpression separately, using LET. Otherwise, try to restructure theexpression to reduce the nesting depth. For example, change thesequence of operators and specify complex cases first, in caseexpressions.

PRCOL053E The name name is not defined.

Explanation: name is not among the names recognized in thecontext where it is used.

Note that different names might be recognized in different parts of astatement. For example, the only names recognized to the right of anequal sign in a SET clause of a DEFINE UPDATE statement are thenames of fields in the record (or columns in the table) that is thesource of the update and the names defined by means of a LETclause.


User response: Use the subsequent message PRCOL051E to locatethe expression that contains the name. Refer to Reporter LogCollector Guide and Referencefor information about the objects(such as fields or columns) that can be referenced at a specific part ofthe statement. Specify the name of one of these objects.

Version 2.02-52

Rep

orter M

essages

PRCOL054E The field field belongs to a section that cannot bereferenced in this context.

Explanation: The section containing the field field cannot bereferenced for one (or both) of these reasons:

■ The section is repeated, or is a subsection of a repeated section,and the present context does not identify a unique occurrence ofthat repeated section.

■ In a DEFINE RECORD statement, the section is referencedbefore it is defined.


User response: Use the subsequent message PRCOL051E toidentify the expression that contains the reference. Refer to ReporterLog Collector Guide and Referencefor exact rules. Restructure yourdefinition so that the required information is accessible.

PRCOL056E The name name specified as the argument ofSECTNUM is not a section name.

Explanation: The argument of SECTNUM must be a section name.


User response: Use the subsequent message PRCOL051E toidentify the expression that contains the invocation of SECTNUM.Ensure that the argument is a field name.


PRCOL057E The section section cannot be referenced in thiscontext.

Explanation: The section cannot be referenced for one (or both) ofthe following reasons:

■ The section is repeated, or is a subsection of a repeated section,and the present context does not identify a unique occurrence ofthat repeated section.

■ In a DEFINE RECORD statement, the section is referencedbefore it is defined.


User response: Use the subsequent message PRCOL051E toidentify the expression that contains the reference. Refer to ReporterLog Collector Guide and Referencefor exact rules. Restructure yourdefinition so that the required information is accessible.

PRCOL060E The name name is already defined.

Explanation: name is specified as the name of:

■ A LET expression

■ The timestamp or interval column in a DISTRIBUTE clause

■ The interval type, start time, end time, or status column in anAPPLY SCHEDULE clause

However, the same name has been used earlier in the same updatedefinition for one of these purposes.


User response: Ensure that all names introduced in the same updatedefinition are unique.

Version 2.02-54

Rep

orter M

essages

PRCOL061E The name name conflicts with a source fieldname.

Explanation: The name is specified as the name of:


■ The timestamp or interval column in a DISTRIBUTE clause

■ The interval type, start time, end time, or status column in anAPPLY SCHEDULE clause

However, name is also the name of a field in the record that is thesource of the update. You cannot use the name for the specifiedpurpose because it would cause ambiguity.


User response: Ensure that all names introduced in an updatedefinition are distinct from the names of fields in the source record.

PRCOL062E The name name conflicts with a source columnname.

Explanation: The name is specified as the name of:


■ The name of the timestamp or interval column in aDISTRIBUTE clause

■ The interval type, start time, end time, or status column in anAPPLY SCHEDULE clause.

However, name is also the name of a column in the table that is thesource of the update. You cannot use the name for the specifiedpurpose because it would cause ambiguity.



User response: Ensure that all names introduced in an updatedefinition are distinct from the names of columns in the source table.

PRCOL065E Argument number n of function is of incorrecttype.

Explanation: In an invocation of function, the data type of theindicated argument is not allowed for this argument.

If function is one of the arithmetic, string, or comparison operatorssuch as +, ||, or =, argument number 1 means the left-hand operand,and argument number 2 means the right-hand operand.

If function is prefix −, argument number 1 means the expressionfollowing the operator.


User response: Use the subsequent message PRCOL051E toidentify the expression that contains the invocation of the function.Refer to Reporter Log Collector Guide and Reference for informationon the allowed types of arguments for function and for rules on theuse of arithmetic, string, and comparison operators.

Ensure that the argument is of the required type. For example, use aconstant of a different type, redefine a field to yield a correct datatype, or apply a conversion function if suitable.

PRCOL066E The arguments of function have an incorrectcombination of types.

Explanation: In an invocation of function, each of the arguments byitself has a data type acceptable for that argument, but the actualcombination of data types of the arguments is not allowed.


Version 2.02-56

Rep

orter M

essages

User response: Use the subsequent message PRCOL051E toidentify the expression that contains the invocation of the function.Refer to Reporter Log Collector Guide and Reference for informationon the allowed types of arguments for function and for rules on theuse of arithmetic, string, and comparison operators.

Ensure that the arguments have an allowed combination of types. Forexample, use a constant of a different type, redefine a field to yield acorrect data type, or apply a conversion function if suitable.

PRCOL067E The arguments of VALUE are of different types.

Explanation: All arguments in an invocation of VALUE must be ofthe same type.


User response: Use the subsequent message PRCOL051E toidentify the expression that contains the invocation of the function.Ensure that all arguments are the same type. For example, use adifferent type of constant, redefine a field to yield a correct data type,or apply a conversion function if suitable.

PRCOL068E The values specified for different cases are ofdifferent types.

Explanation: In a case expression, all expressions following thekeywords THEN (and ELSE, if present) must specify the same typeof values.


User response: Use the subsequent message PRCOL051E toidentify the expression. Ensure that all expressions specify the sametype of values. For example, use a different type of constant, redefine


a field to yield a correct data type, or apply a conversion function ifsuitable.

PRCOL069E The value specified for case n is of incorrecttype.

Explanation: In a case expression, the expression that follows theTHEN keyword number n is not of a type allowed for the result of acase expression (for example, a labeled duration or a truth value.)

If the n is 1 greater than the number of THEN keywords in theexpression, it refers to the expression following the ELSE keyword.

(If the case expression contains nested case expressions, the keywordsTHEN and ELSE of these subexpressions are not included in the n.)


User response: Use the subsequent message PRCOL051E to locatethe expression. Ensure that the expression is of an allowed type.

PRCOL070E The keyword keyword, that identifies a labeledduration, follows a non-numeric expression.

Explanation: The keyword keyword is supposed to follow anexpression that specifies the number of time units identified by thekeyword. The expression must specify a numeric value (that is, avalue of type integer or floating-point).


User response: Use the subsequent message PRCOL051E to locatethe expression containing the keyword. Ensure that the expressionpreceding the keyword specifies a numeric value. For example, use aconstant of a different type, redefine a field to yield a correct datatype, or apply a conversion function if suitable.

Version 2.02-58

Rep

orter M

essages

PRCOL071E The lookup table table does not exist.

Explanation: A lookup expression is incorrect because the lookuptable (the table specified after the keyword IN) does not exist.


User response: Use the subsequent message PRCOL051E to locatethe expression. Ensure that the lookup table exists.

PRCOL072E The lookup table table does not have columncolumn.

Explanation: A lookup expression is incorrect because the lookuptable (the table specified after the keyword IN) does not contain thecolumn referenced in the expression.


User response: Use the subsequent message PRCOL051E to locatethe expression. Ensure that the lookup table has all the columnsreferenced in the expression.

PRCOL075E Argument number n of function has an incorrectvalue.

Explanation: In an invocation of function, the indicated argument isspecified by means of a constant or a combination of constants. Thevalue thus specified is not valid for this argument.

If function is one of the arithmetic, string, or comparison operatorssuch as +, ||, or =, argument number 1 means the left-hand operand,and argument number 2 means the right-hand operand.


If function is prefix −, argument number 1 means the expressionfollowing the operator.


User response: Use the subsequent message PRCOL051E toidentify the expression that contains the invocation of the function.Refer to Reporter Log Collector Guide and Reference for informationon the allowed values of arguments for function and for rules on theuse of arithmetic, string, and comparison operators.

Ensure that the argument has a correct value.

PRCOL076E The result of function is outside the range ofvalues of type type.

Explanation: The function is applied to argument(s) specified asconstants or combinations of constants. The result of function issupposed to be of typetype, but function applied to the specifiedvalues yields a value outside that type (for example, a value largerthan 2óñ−1 when the result is supposed to be an integer).


User response: Use the subsequent message PRCOL051E toidentify the expression that contains the invocation of the function.Ensure that you specify correct values.

PRCOL080E The value specified for keyword is not of typetype.

Explanation: The keyword is a language keyword such as OFFSETor LENGTH. The expression following this keyword must specify avalue of typetype, but the actual expression specifies a value ofanother type.

Version 2.02-60

Rep

orter M

essages


User response: Ensure that the expression specifies a value of therequired type. For example, use a constant of a different type,redefine a field to yield a correct data type, or apply a conversionfunction if suitable.

PRCOL081E The value specified for column column isincompatible with the column type.

Explanation: An update definition specifies a value to be assignedto column. The value is of a type that cannot be assigned to thecolumn. Note that an integer or a floating-point number can beassigned only to a column of the type integer, small integer,floating-point, or decimal. A character string can be assigned only toa column of the type character string, graphic string, date, time, ortimestamp. A date/time value can be assigned only to a column of thesame type, to a timestamp column, or to a character string column.


User response: Ensure that the value to be assigned has a data typethat is compatible with the type of the column.

PRCOL082E The column column is too short for the date/timevalue.

Explanation: A date/time value (a date, a time, or a timestamp) isassigned to the column column which is of the character string type.Before assignment, the value is converted to a character string. Adate value is converted to a string of 10 characters; a time value isconverted to a string of 8 characters; a timestamp value is convertedto a string of 26 characters. The column column is shorter than theresulting string, and the assignment cannot be performed. (Thedate/time strings are not truncated on assignment.)



User response: Ensure that the column can accommodate theconverted date/time value.

PRCOL095E The lookup condition has too many terms. Themaximum number is 15.

Explanation: A lookup expression specifies a condition that consistsof more than 15 terms connected with AND operators.


User response: Simplify the condition, or modify the lookupprocess, for example by restructuring the lookup table.

PRCOL100E The log log already exists.

Explanation: The log could not be defined because a log with thesame name already exists. Each log name must be unique.


User response: Change the log name or drop the old log definition.

PRCOL101E The log log does not exist.

Explanation: The log log is specified in a statement, but it does notexist.


User response: Correct the statement or define the log.

Version 2.02-62

Rep

orter M

essages

PRCOL102I The log log is defined.

Explanation: The log log has been defined successfully.

System action: Processing continues.

PRCOL103I The log log is altered.

Explanation: The log log has been altered successfully.


PRCOL104I The log log is dropped.

Explanation: The log log has been dropped successfully.


PRCOL105I The comment is stored for the log log.

Explanation: COMMENT ON LOG was successful for log.


PRCOL106E The name condition for the log log is invalid.

Explanation: One of the following conditions is not valid:

■ The FIRST RECORD or LAST RECORD condition forlog.

■ The WHERE condition specified on the COLLECT statementfor log



User response: Refer to Reporter Log Collector Guide andReference for information about valid conditions for DEFINE LOG orCOLLECT. Ensure that the correct condition is specified.

PRCOL107E The name of the log must not exceed 16 bytes.

Explanation: The maximum length of a log name is 16 bytes.


User response: Specify a name that is not longer than 16characters.

PRCOL121E The record record already exists.

Explanation: The record could not be defined because a record withthe same name already exists. Each record name must be unique.


User response: Change the record name or drop the old recorddefinition.

PRCOL122E The record record does not exist.

Explanation: The record record is specified in a statement, but itdoes not exist.


User response: Correct the statement or define the record.

Version 2.02-64

Rep

orter M

essages

PRCOL123E The record record does not contain the fieldfield.

Explanation: The field field of the record record is specified in astatement, but it does not exist.



PRCOL124E No records are defined for this log.

Explanation: No records are defined for this log.


User response: Either define the records or, if the incorrect log isspecified, correct the log name.

PRCOL125I The record record is defined.

Explanation: The record record has been defined successfully.


PRCOL126I The record record is altered.

Explanation: The record record has been altered successfully.



PRCOL127I The record record is dropped.

Explanation: The record record has been dropped successfully.


PRCOL128E All records in this log are defined without fields.The log cannot be processed.

Explanation: No record definitions containing fields exist for thislog.


User response: Perform DEFINE RECORD for the requiredrecords.

PRCOL129E A record name must not both start and end withan asterisk (*).

Explanation: A record name cannot both start and end with anasterisk (*).


User response: Specify a name that does not start and end with anasterisk.

Version 2.02-66

Rep

orter M

essages

PRCOL130I The comment is stored for the record record.

Explanation: COMMENT ON RECORD was successful forrecord.


PRCOL131I The comment is stored for the field field inrecord record.

Explanation: COMMENT ON FIELD was successful on field inrecord.


PRCOL132E There is no update or record procedure definedfor any record in this log. The log cannot beprocessed.

Explanation: Records are defined for the log to be collected, but noprocessing is defined for them. The processing of a record might bedefined in two ways:

■ By specifying the record as the source of an update definition

■ By specifying the record as input to a record procedure

No record in the log is used in this way.


User response: Ensure that some processing is defined for at leastone record type in the log.


PRCOL133E An error is found in the definition of recordrecord.

Explanation: This message identifies a record in error. A previousmessage identifies the error.



PRCOL135E The record record does not contain a sectionsection.

Explanation: The section section specified for record does notexist.


User response: Redefine the record or correct the section name.

PRCOL137E The section section in record record is notrepeated.

Explanation: This message is issued in one of the followingsituations:

■ A DEFINE UPDATE or ALTER UPDATE statement specifiesan update FROM record SECTIONsection.

■ A COLLECT statement encountered an update FROM recordSECTION section.

■ A LIST RECORD statement specifies RECORD recordSECTION section.

Version 2.02-68

Rep

orter M

essages

In each case, the SECTION clause indicates that the requestedoperation (update or listing) is to be repeated once for eachoccurrence of section section. This can be specified only for arepeated section section.


User response: Refer to Reporter Log Collector Guide andReference for an explanation of how repeated sections are processed.Decide which repeated section you want to process (if any). Note thatthe choice of the section determines which fields you can access.

PRCOL138E The section section is not previously defined inthe record record.

Explanation: This message is issued in one of the followingsituations:

■ A DEFINE RECORD statement for the record record defines asection IN SECTION section. The section section must bedefined earlier in the same statement.

■ An ALTER RECORD statement for the record record definesfields IN SECTION section or a section IN SECTION section.The record must already have the section section.


User response: For DEFINE RECORD, ensure that the section isdefined earlier in the same statement. For ALTER RECORD, ensurethat the record already has the section.


PRCOL139E The section section is already defined.

Explanation: The message is issued in one of the followingsituations:

■ A DEFINE RECORD statement specifies section as the name oftwo different sections.

■ An ALTER RECORD statement attempts to add a sectionsection to a record that already has a section with that name.


User response: Ensure that all sections within a record havedifferent names.

PRCOL140E Too many fields are specified for the record orthe log header.

Explanation: A maximum of 2000 fields can be specified in arecord or a log header.



PRCOL141E Too many sections are specified for the record.

Explanation: A maximum of 300 sections can be specified in arecord.



Version 2.02-70

Rep

orter M

essages

PRCOL142E The field field is already defined.

Explanation: The message is issued in one of the followingsituations:

■ A DEFINE RECORD statement specifies field as the name oftwo different fields in the record.

■ A DEFINE LOG statement specifies field as the name of twodifferent fields in the log header.

■ An ALTER RECORD statement attempts to add the field fieldto a record that already has a field with that name.

■ An ALTER LOG statement attempts to add the field field to alog header that already has a field with that name.


User response: Ensure that all fields within a record or a log headerhave different names.

PRCOL147E The record record is the source of the updateupdate.

Explanation: The definition of the record record contains an errorthat has been identified by one or more error messages. This messagefollows the error message(s) forrecord and explains why an error inthe record prevents the execution of a COLLECT statement: Therecord record is the source of the update update, and the target of theupdate is one of the tables specified in the INCLUDE clause of thestatement.

System action: Processing of the statement is terminated and thelog collector continues with the next.

User response: Correct the definition of the record record, orremove the table from the INCLUDE clause.


PRCOL148E The record record is used as input to recordprocedure procedure.

Explanation: The definition of the record record contains an errorthat has been identified by one or more error messages. This messagefollows the error message(s) for the recordrecord and explains whyan error in the record prevents execution of the current statement:The record record is used as input to the record procedure procedure,which is required for the execution of the statement.


User response: Correct the definition of the record record.

PRCOL150E The IDENTIFIED BY condition for the recordrecord is invalid.

Explanation: The condition specified as the IDENTIFIED BYcondition is not valid. This error message is preceded by one or moreerror messages identifying the error(s).



PRCOL151E An invalid condition or expression is specifiedfor section section of record record.

Explanation: One of the following items is not valid:

■ The condition specified as the PRESENT IF condition for thesection

■ The expression specified as the offset, length, or number ofoccurrences of the section

Version 2.02-72

Rep

orter M

essages

This message is preceded by one of more messages identifying theerror(s) and the condition or expression in error.



PRCOL152E The length of section section of record record isundefined: neither LENGTH nor any named fieldsare specified.

Explanation: If the length of a section is not specified explicitly bymeans of a LENGTH clause, it is determined by the fields containedin that section. It is then defined to be the minimum length thataccommodates all named fields. If no named fields are defined for thesection, the length cannot be determined.


User response: Ensure that the length is specified in one of the twoways. If you must define a section that extends to the end of thecontaining record or section, specify a large length by means of aLENGTH clause. Refer to Reporter Log Collector Guide andReference for exact rules about specifying length.

PRCOL153I The section subsection of record record is asection within section section, which has noLENGTH defined. The section section will have itslength defined by the length of its fields.

Explanation: This information message reminds the user that, in theabsence of an explicit length specification for the section section, thelength of the section will be determined by the named fields of thesection section, and not by the length of the subsection subsection.The length will be defined as the minimum length that accommodates


all named fields of section, and might be insufficient to accommodatethe subsection.


User response: Add a LENGTH clause for the section section, orensure that the total length of the fields of the containing section is atleast equal to the length of the subsection.

PRCOL154I The section section of record record has noOFFSET specified. Offset 0 is assumed.

Explanation: If the offset of a section is not specified explicitly bymeans of an OFFSET clause, the section is assumed to startimmediately after the end of a preceding section, identified accordingto the rules stated in Reporter Log Collector Guide and Reference. Ifthe preceding section does not exist, the section is assumed to start atoffset 0. This information message tells the user that this lastalternative was applied for the section section.


User response: Refer to Reporter Log Collector Guide andReference for exact rules about specifying length. Specify OFFSET ifoffset 0 is not what you intended.

PRCOL155E The section section of record record is specifiedto be a subsection of itself.

Explanation: The section section specifies IN SECTION section,which means that section is a subsection of itself. This is notpossible.


User response: Change the SECTION name or the IN SECTIONname.

Version 2.02-74

Rep

orter M

essages

PRCOL161E The record procedure procedure does not exist.

Explanation: The record procedure procedure is specified in astatement, but it is not defined to the log collector.


User response: Ensure that the procedure is defined.

PRCOL162E The log procedure procedure could not beloaded.

Explanation: The log procedure procedure is required for the log tobe processed, but it could not be loaded.


User response: Ensure that the procedure procedure is present inone of the directories listed in the default library path (LIBPATH).

PRCOL163I The comment is stored for record procedureprocedure.

Explanation: COMMENT ON RECORDPROC was successful forthe procedure procedure.



PRCOL164E The record procedure procedure already exists.

Explanation: The record procedure procedure, specified in DEFINERECORDPROC already exists.



PRCOL165I The record procedure procedure is defined.

Explanation: DEFINE RECORDPROC was successful for recordprocedure procedure.


PRCOL166I The record procedure procedure is dropped.

Explanation: DROP RECORDPROC was successful for recordprocedure procedure.


PRCOL167I The record procedure procedure is altered.

Explanation: ALTER RECORDPROC was successful for recordprocedure procedure.


Version 2.02-76

Rep

orter M

essages

PRCOL168E The record procedure procedure is involved in acircular process.

Explanation: The record procedure procedure is defined so that itsinput is derived, directly or indirectly, from its own output. Forexample, procedure is a procedure for record REC1 built by aprocedure PROC2 for a record REC2 built by the procedureprocedure. Such a circular process is not allowed.


User response: Check the definitions of the records built by therecord procedureprocedure, the record procedures for these records,and so on. Modify them so that the process is not circular.

PRCOL171E The record procedure procedure could not beloaded.

Explanation: The record procedure procedure is required for thespecified processing, but it could not be loaded.


User response: Ensure that the procedure procedure is present inone of the directories listed in the default library path (LIBPATH).


PRCOL172E The record record specified for record procedureprocedure does not exist.

Explanation: The DEFINE RECORDPROC statement for recordprocedure procedure specifies the record record in its FOR clause,but the record is not defined.



PRCOL174I Record number n is the last log record processed.

Explanation: This message is issued after a record procedure isterminated by an error.


PRCOL200E The update update already exists.

Explanation: The update could not be defined because an updatewith the same name already exists. Each update name must beunique.


User response: Change the update name or drop the old updatedefinition.

Version 2.02-78

Rep

orter M

essages

PRCOL201I The update update is defined.

Explanation: The update update has been defined successfully.


PRCOL202I The update update is dropped.

Explanation: The update update has been dropped successfully.


PRCOL203I The update update is altered.

Explanation: The update update has been altered successfully.


PRCOL204E The update update does not exist.

Explanation: The update update is specified in a statement, but itdoes not exist.


User response: Correct the statement or define the update.

PRCOL205I The comment is stored for update update.

Explanation: COMMENT ON UPDATE was successful onupdate.



PRCOL206E The update update is not defined.

Explanation: DEFINE UPDATE failed. A previous messageexplains the reason.



PRCOL210E The update does not specify the value of anycolumn.

Explanation: The update being defined does not have any of theclauses: GROUP BY, SET, or MERGE that define the contents ofthe target table.


User response: Ensure that the update contains at least one of theclauses GROUP BY, SET, or MERGE.

PRCOL211E The WHERE condition in update update isinvalid.

Explanation: The condition specified in the WHERE clause ofupdate is not valid. This message is preceded by one or moremessages identifying the error(s).



Version 2.02-80

Rep

orter M

essages

PRCOL212E The section section specified in update updatedoes not exist.

Explanation: The update is specified to be FROM SECTIONsection of a record. The section existed when the update was defined.However, the record must have been redefined afterwards, because itno longer contains the section section.


User response: Correct the update definition or add the section tothe record definition.

PRCOL213E The column column, specified as argumentnumber 2 of AVG or PERCENTILE, is notdefined by means of COUNT or SUM.

Explanation: Argument number 2 of the accumulation functionsAVG and PERCENTILE must be a column with a value defined inthe same update by means of the accumulation function COUNT orSUM.


User response: Correct the AVG or PERCENTILE to specifyanother column or change the accumulation function for column.


PRCOL214E The column column is defined by MERGE andcannot be changed to SET or GROUP BY.

Explanation: Columns specified in the MERGE clause of aDEFINE UPDATE statement cannot be changed to a SET or GROUPBY column in an ALTER UPDATE statement.


User response: If the column must be changed, drop and redefinethe update.

PRCOL215E The value of column column is specified morethan once.

Explanation: A column can be specified only once in an updatedefinition.


User response: Ensure that you specified the correct column name.

PRCOL216E Argument number 3 of PERCENTILE is not inthe range 1–99.

Explanation: Argument number 3 of the accumulation functionPERCENTILE must be an integer constant in the range 1–99.


User response: Change the integer value.

Version 2.02-82

Rep

orter M

essages

PRCOL217E The field field in DISTRIBUTE is not numeric.

Explanation: All fields or columns to be distributed must benumeric.


User response: Correct the DISTRIBUTE clause.

PRCOL218E In the expression for column column, theargument number 1 of function is not numeric.

Explanation: Argument number 1 of function (SUM, AVG, orPERCENTILE) must be numeric (that is, of the integer orfloating-point type). The error was found in the clause specifying thevalue of columncolumn.


User response: Change the expression used in the specification ofcolumn column.

PRCOL219E Different update definitions for the table tablespecify the value of column column in differentways.

Explanation: If different update definitions specify the value of thesame column, the value must be specified in the same way by alldefinitions: Either the column must be a GROUP BY column in alldefinitions, or all definitions must specify the value of the columnusing the same accumulation function. A subsequent message(PRCOL331E) identifies an update that does not follow this rule.



User response: Correct the accumulation function for column.

PRCOL220E Different update definitions for the table tablehave different GROUP BY columns.

Explanation: If different update definitions specify the contents ofthe same table, their GROUP BY columns must be the same. Asubsequent message (PRCOL331E) identifies an update that does notfollow this rule.


User response: Make the GROUP BY clauses of all updates TO thetable table identical.

PRCOL224E The MERGE and SET clauses of an updatedefinition are mutually exclusive.

Explanation: An ALTER UPDATE statement attempts to add aMERGE clause to an update definition that has a SET clause, or aSET clause to an update definition that has a MERGE clause.However, an update definition cannot have both.


User response: Remove the SET or the MERGE clause from theupdate definition before adding the other clause.

Version 2.02-84

Rep

orter M

essages

PRCOL225E The name name specified by keyword is alreadyused as the name of a field or column ofsource.

Explanation: The name name introduced bykeyword clause isidentical to the name of a field (or column) of the record (or table)source, which is the source of the update. You cannot use the namefor the specified purpose because it would cause ambiguity.


User response: Change the parameter.

PRCOL226E The name name specified inkeyword clause is nota field or column of source.

Explanation: The name name specified in the keyword clause isexpected to be the name of a field (or column) in the record (ortable) source, which is the source of the update. The record (or table)does not contain a field (or column) with this name.


User response: Correct the parameter to specify source fields orcolumns.

PRCOL227E The value of column has an incorrect length.

Explanation: The value of the expression assigned to column is ofan incorrect length. For example, in an update definition’s MERGEclause, the value of the expression specified for the interval typecolumn must have a length of 3.



User response: Correct the expression assigned to the columncolumn.

PRCOL228E The column column is not of type type.

Explanation: The assignment to column requires it to be of typetype, which it is not. For example, columns assigned AVG valuesmust be of the floating-point type.


User response: Change the column name, column type, oraccumulation function.

PRCOL229E The field field in DISTRIBUTE is specified morethan once.

Explanation: Each field to be distributed should be specified onlyonce.


User response: Change the definition so the field is defined onlyonce.

PRCOL230E The SECTION parameter cannot be used whenthe source of the update is a table.

Explanation: The SECTION parameter can be used only to identifya section of a record definition.



Version 2.02-86

Rep

orter M

essages

PRCOL231E The value of the column column of table table isspecified by more than one update using theaccumulation function PERCENTILE.

Explanation: If the value of a column is specified by means of theaccumulation function PERCENTILE, the value can be specified inonly one update definition.


User response: Remove the assignment to the column from allupdate definitions but one.

PRCOL232E The accumulation function PERCENTILEcannot be used when the source of the update is atable.

Explanation: The accumulation function PERCENTILE can only beused in an update where the source is a record.


User response: Consider an alternative way of computing theinformation you need, for example, counting values that exceed acertain threshold.


PRCOL233E The argument number n of APPLY SCHEDULEis of incorrect type.

Explanation: The correct type for argument 1 (interval type) ischaracter string. The correct type for argument 2 (interval start) andargument 3 (interval end) is timestamp.


User response: Ensure that the argument is of the required type.For example, use a different type of constant, redefine a field to yielda correct data type, or apply a conversion function if suitable.

PRCOL234E The column column cannot be used as agrouping column.

Explanation: A GROUP BY clause of an update definition specifiesthat the column column should hold a grouping value. The column iseither a decimal column, or a long string column.


User response: Redefine the column or specify another column.

PRCOL235E There is a circular update involving tables tablelist.

Explanation: Each table in the table list is updated from itself via acascaded update involving other tables in the table list. A tablecannot be updated from itself.


Version 2.02-88

Rep

orter M

essages

User response: Check update definitions involving the tables listedin the table list. You may have an old update definition that was notdropped. Correct the error.

PRCOL241E The table table does not exist.

Explanation: The operation failed because the specified table tabledoes not exist.



PRCOL242E The table table does not contain the columncolumn.

Explanation: The column column of table table is specified in astatement, but it does not exist.


User response: Change the update definition or change and recreatethe table.

PRCOL243E The control table table does not exist.

Explanation: The function DAYTYPE, PERIOD, or APPLYSCHEDULE could not be performed because the control table tableis missing.


User response: Contact the Reporter administrator. Refer toReporter Log Collector Guide and Referencefor an explanation.


PRCOL244E The column column of control table table ismissing or has an incorrect type.

Explanation: The function DAYTYPE, PERIOD, or APPLYSCHEDULE could not be performed because the column column incontrol table table either is not present or has an incorrect type.


User response: Contact the Reporter administrator. Refer toReporter Log Collector Guide and Referencefor an explanation.

PRCOL245W The length of string column column in the tabletable exceeds the length supported by the logcollector.

Explanation: The maximum length of a CHARACTER orVARCHAR column supported by the log collector is 254 bytes.

System action: The processing continues, but the following willhappen if the log collector reads data from the table:

■ When the log collector reads a string of more than 254 bytesfrom a CHARACTER or VARCHAR column, it truncates thestring to 254 bytes. This might result in damaging amultiple-byte character contained in the string.

User response: Ensure that this warning message does not indicatea problem that must be corrected.

Version 2.02-90

Rep

orter M

essages

PRCOL246E The table table is specified more than once in anINCLUDE or EXCLUDE clause.

Explanation: A table name can only appear once in the sameINCLUDE or EXCLUDE clause.



PRCOL247E The EXCLUDE clause did not exclude anytables.

Explanation: None of the tables specified by the EXCLUDE clauseis among the tables that would otherwise be selected for processing.


User response: Check the EXCLUDE clause. If the clause does notspecify the tables you want to exclude, correct it. If there are notables to be excluded, remove the clause.

PRCOL251E The SQL statement or condition is too long.

Explanation: An SQL statement in the log collector cannot belonger than 8000 bytes.




PRCOL300I operation started at timestamp.

Explanation: The operation (COLLECT, LIST RECORD,LOGSTAT, or PURGE) began processing at timestamp.


PRCOL301I operation ended at timestamp.

Explanation: The operation (COLLECT, LIST RECORD,LOGSTAT, or PURGE) completed processing at timestamp.


PRCOL302I Processing file.

Explanation: This message identifies the log file being processed.


PRCOL303E The log file has already been processed.

Explanation: The log file has already been collected. The logcollector uses the first 80 bytes of the first selected record to identifythe log. The file name is not used for identification.

System action: COLLECT terminates. Debug information will bedisplayed in standard error file. The log record number beingprocessed will be displayed as well as the first 80 bytes of the recordwhich caused the message.


Version 2.02-92

Rep

orter M

essages

PRCOL304W The log file is being reprocessed.

Explanation: The log file has already been collected but, becausethe REPROCESS parameter is specified on the COLLECT statement,the log is processed again.

System action: COLLECT starts from the beginning of the log.

User response: Ensure that the warning message does not indicate aproblem that must be corrected.

PRCOL305I The log file has been partly processed.

Explanation: The log file has been partly collected; the previousCOLLECT for this file was terminated before the entire log wasprocessed.

System action: The first n records (as identified bymessage PRCOL306I) are skipped, and COLLECT continuesprocessing the remaining records in the log file.

PRCOL306I The first n records are skipped.

Explanation: This is a continuation of message PRCOL305I. Seethat message.



PRCOL307E The value specified by the COMMIT AFTERclause is not valid.

Explanation: The COMMIT AFTER n RECORDS parameterspecified an invalid value. For example, a zero (0) is not allowed.

System action: COLLECT terminates.


PRCOL308I A database update started after n records due toa buffer-full condition.

Explanation: The collect buffer was full and a database update wasstarted.


PRCOL309I A database update started after n records.

Explanation: COMMIT AFTER n RECORDS was specified on theCOLLECT statement, and a multiple of n records have been read.


PRCOL310I A database update started after n records due toend of log.

Explanation: The end of the log file has been reached.


Version 2.02-94

Rep

orter M

essages

PRCOL311I A database update started after n records due tofile switch.

Explanation: This message is issued when the log being processedconsists of several concatenated files. The end of a file was reached,and the log collector started a database update before processing thenext concatenated file. After the database update completes, thestatistics for the file will be presented.


PRCOL313I The collect buffer was filled n times. Considerincreasing the collect buffer size.

Explanation: This message shows the number of times the collectbuffer was filled during processing of the log file.


User response: The collect time will increase considerably eachtime the collect buffer is filled. A larger collect buffer will decreasethe number of times the collect buffer is filled. Consider increasingthe value specified in the BUFFER SIZE parameter of the COLLECTstatement.

PRCOL315I Records read from the log or built by logprocedure:

Explanation: This message is followed by a table showing therecord types in the log being processed, or, if the log procedure wasused, the record types built by the log procedure. For each recordtype, the table shows the number of records of that type that wereactually found and processed. The table also shows the number ofunrecognized records, and the total number of records. The table is


built from messages PRCOL317I through PRCOL321I. For anexample of such a table, see Figure 1 on page 2-126.


PRCOL316I Records built by record procedures:

Explanation: This message is followed by a table showing therecord types built by record procedures. For each record type, thetable shows the number of records of that type that were found andprocessed. The table also shows the number of unrecognized records,and the total number of records. The table is built from messagesPRCOL317I through PRCOL321I. For an example of such a table,see Figure 1 on page 2-126.


PRCOL317I PRCOL318I PRCOL319I PRCOL320I PRCOL321I

Explanation: Messages PRCOL317I through PRCOL321I are usedto build the table that follows the messages PRCOL315I andPRCOL316I. See the explanation for those messages. For anexample, see Figure 1 on page 2-126.


Version 2.02-96

Rep

orter M

essages

PRCOL323I PRCOL324I PRCOL325I PRCOL326I PRCOL327I

Explanation: Messages PRCOL323I through PRCOL327I are usedto build a table that shows the number of rows inserted and updatedin the collect buffer and in the database tables. For an example, seeFigure 1 on page 2-126.

For more information on how to interpret collect messages, refer toReporter Installation and AdministrationandReporter Log CollectorGuide and Reference.


PRCOL328I Reading lookup table table: n rows, b bytes.

Explanation: The log collector is about to use the lookup tabletable. The entire table will be read into storage, where it is going tooccupy b bytes.


User response: Check if the size of the table looks reasonable. Arow and byte count of 0 may indicate that the contents of the tablewas lost. A very large row or byte count may explain problems withstorage, or degraded performance, in particular if a lookup expressionagainst the table uses pattern matching (the LIKE operator).


PRCOL330E The collect initialization failed.

Explanation: This message follows other message(s) explaining thecause of the failure.



PRCOL331E An error was found in update update.

Explanation: This message identifies an update in error. A previousmessage identifies the cause of the error.



PRCOL333I The record record has no fields and is not used.

Explanation: The record is excluded.

System action: Processing continues; COLLECT and LOGSTAToperations continue their execution.

User response: ALTER the record or DROP and redefine it.

Version 2.02-98

Rep

orter M

essages

PRCOL335E The processing terminated due to an error foundby log or record procedure procedure.

Explanation: The log or record procedure procedure returned witha request for termination of the processing of the log.



PRCOL336W n records or rows were skipped in updateupdate of table table due to a null GROUP BYvalue.

Explanation: A source record or row is skipped if any of thegrouping values for that row is null. A grouping value is thatspecified by the expression to the right of an equal sign in theGROUP BY clause. It might be null because the data in the sourcerecord or row that are used to compute the value are missing, orinvalid, or result in a computation error.


User response: The standard error file contains information thatidentifies the skipped records or rows. Examine these records or rowsto see if the content was indeed invalid, and if not, what informationwas lost. Consider redefining the update to prevent this kind ofproblem.


PRCOL337W For n records or rows in an update of tabletable, one or more values were set to null becauseof error.

Explanation: The following has happened for n source records orrows: A value (one or more) obtained from the row was to be used inthe update, for example as the argument of an accumulation function(but not as a grouping value). The value could not be evaluatedbecause the data in the record or row is invalid or resulted in acomputation error; a null value was used instead in the update.

Notice that the message does not signal the null values that resultfrom missing data. Such a null value is not considered an error.


User response: The standard error file contains information thatidentifies the first source record of each type (or the first row of eachsource table) included in the count. Examine these records or rows tosee if the content was indeed invalid, and if not, what informationwas lost. Consider redefining the update to prevent this kind ofproblem.

PRCOL338W The section section of record record was skippedn time(s) due to error in offset, length, or number.

Explanation: One or more occurrences of section section of recordcould not be located because the offset, length, or number attribute ofthe section could not be evaluated. The number n is the number ofunsuccessful attempts to locate an occurrence of the section, andmight be larger than the actual number of skipped occurrences (forexample, when several updates tried to locate the same occurrence).


Version 2.02-100

Rep

orter M

essages

PRCOL339E Processing terminated due to invalid return codereturn code returned by log or record procedureprocedure.

Explanation: The log or record procedure procedure returned withan invalid return code, which caused the processing of the log tostop.



PRCOL340W The name condition for the log is not satisfied.

Explanation: The name condition (FIRST RECORD or LASTRECORD), as coded in the DEFINE LOG statement, was not metwhen applied to the first or last record read from the log.



PRCOL341I The first-record timestamp is timestamp.

Explanation: A TIMESTAMP clause is specified in the logdefinition. The timestamp for the first record from the log file istimestamp.



PRCOL342I The last-record timestamp is timestamp.

Explanation: A TIMESTAMP clause is specified in the logdefinition. The timestamp for the last record from the log file istimestamp.


PRCOL343I The first-record timestamp is invalid.

Explanation: A TIMESTAMP clause is specified in the logdefinition. The timestamp for the first record selected from the logfile could not be evaluated because of absent or invalid data, orbecause of a calculation error.


User response: Check the data in the log file and make sure it isvalid. Check the TIMESTAMP expression in the log definition, andcorrect it if necessary.

PRCOL344I The last-record timestamp is invalid.

Explanation: A TIMESTAMP clause is specified in the logdefinition. The timestamp for the last record selected from the log filecould not be evaluated because of absent or invalid data, or becauseof a calculation error.


User response: Check the data in the log file and make sure it isvalid. Check the TIMESTAMP expression in the log definition, andcorrect it if necessary.

Version 2.02-102

Rep

orter M

essages

PRCOL345E The specified buffer size is n. The minimumallowed value is min.

Explanation: The minimum allowed buffer size on COLLECT andLIST RECORD is min.


User response: Specify a larger buffer size.

PRCOL346W n records or rows were skipped in updateupdate, table table due to invalid arguments ofDISTRIBUTE.

Explanation: A source record or row is skipped if one or morearguments of DISTRIBUTE are invalid, for example:

■ The START, END, or BY expression cannot be evaluatedbecause of missing data, invalid data, or computation errors.

■ The START time is later than the END time.

■ The BY value is not a multiple of 60.


User response: The standard error file contains information thatidentifies the record or row that caused the error. Check theDISTRIBUTE clause against the contents of the record or row andcorrect the cause of the error.


PRCOL347W n records or rows were skipped in updateupdate, table table due to invalid arguments ofMERGE.

Explanation: A source record or a row of a source table is skippedif one or more arguments of MERGE are invalid, for example:

■ The argument cannot be evaluated because of missing data,invalid data, or computation errors.

■ The interval type code (argument 1) is not one of the allowedinterval type codes.

■ The interval start time (argument 2) is later than the interval endtime (argument 3).

■ The quiet interval (argument 4) is negative.


User response: The standard error file contains information thatidentifies the record or row that caused the error. Check the MERGEclause against the contents of the record or row and correct the causeof the error.

PRCOL348W COLLECT initialization resulted in no tablesselected for processing.

Explanation: No tables were selected for COLLECT processing.


User response: Investigate the reason for failure of the COLLECTstatement to select tables for processing. Is the EXCLUDE parameterpresent? If so, check its content. Correct the error.

Version 2.02-104

Rep

orter M

essages

PRCOL349W Data values in table table were changed to nullin n columns due to overflow.

Explanation: An overflow is a situation during the execution of aCOLLECT, LIST RECORD, or RECALCULATE statement when theresult of an accumulation function exceeds the capacity of the columnsupposed to receive it. In the case of COLLECT andRECALCULATE, the column is a column in the target table, and itscapacity is determined by the SQL data type of the column. In thecase of LIST RECORD, the column is a part of the output list, andits capacity is determined by the type of expression defining it.

According to the options defined for the statement, the processingwas to continue in case of an overflow. Every time an overflowoccurred, the current value of the accumulation function wasdiscarded, the column was reset to null, and the accumulationcontinued starting from null. If the column appeared as argumentnumber 2 of an AVG or PERCENTILE function in the same update,the current value of that AVG or PERCENTILE was similarlydiscarded and reinitialized. All discarded values were written to thestandard error file, together with the identification of the column andthe currently processed record or row.

The columns of the table table were reinitialized in this way n timesduring the execution of the statement.


User response: Refer to the standard error file for exact informationon what has happened. Check if the overflow was caused by anincorrectly defined argument of the accumulation function. Examinethe source record or row to see if the overflow was caused by invaliddata. If the statement is COLLECT, consider redefining the targettable to give the column a higher capacity (integer instead of smallinteger, floating-point instead of integer, and a higher precision for adecimal column). If the statement is LIST RECORD, considermodifying the argument of the accumulation function to change thetype of result from integer to floating-point. (The RECALCULATE


statement is always terminated by an overflow, so that this messagecan never be issued for it.)

PRCOL350E Overflow occurred in column column of tabletable.

Explanation: The value of column column was to be computed by aCOLLECT, LIST RECORD, or RECALCULATE statement. Thevalue of column column is specified by means of an accumulationfunction with a numeric result. The result exceeds the capacity of thecolumn. This situation is called an overflow.

In the case of COLLECT and RECALCULATE, the column is acolumn in the target table, and its capacity is determined by the SQLdata type of the column. In the case of LIST RECORD, the columnis a part of the output list, and its capacity is determined by the typeof expression defining it.


User response: Check if the overflow was caused by an incorrectlydefined argument of the accumulation function. Examine the sourcerecord or row to see if the overflow was caused by invalid data.Examine the data specified by RECALCULATE. If the statement isCOLLECT or RECALCULATE, consider redefining the target tableto give the column a higher capacity (integer instead of small integer,floating-point instead of integer, and a higher precision for a decimalcolumn). If the statement is LIST RECORD, consider modifying theargument of the accumulation function to change the type of theresult from integer to floating-point (if it is not alreadyfloating-point). If the statement is COLLECT or LIST RECORD,consider specifying ON OVERFLOW CONTINUE.

Version 2.02-106

Rep

orter M

essages

PRCOL351E The COLLECT processing is terminated by anoverflow.

Explanation: An overflow is the situation when the result of anaccumulation function becomes too large to be stored in the specifiedcolumn.

The COLLECT statement specified (explicitly or by default) that theprocessing is to stop in case of overflow. This message is precededby message PRCOL350E that provides further details.

System action: The processing is stopped and the database updatesare rolled back to the most recent commit point. The log collectorcontinues with the next.

User response: See explanation and user response for messagePRCOL350E.

PRCOL353E n records or rows were skipped in updateupdate, table table due to invalid arguments ofAPPLY SCHEDULE.

Explanation: A source record or row is skipped if one or morearguments of APPLY SCHEDULE are invalid, for example, theinterval start time is greater than the interval end time.


User response: The standard error file contains information thatidentifies the record or row that caused the error. Check the APPLYSCHEDULE clause against the contents of the record or row andcorrect the cause of the error.


PRCOL355E No updates or valid records are defined for thetables in the INCLUDE list.

Explanation: The COLLECT statement was not executed becauseno valid updates exist for the tables specified in the INCLUDEclause, or the updates exist, but their source records do not exist orare invalid.


User response: Ensure that the included tables have valid updateand record definitions.

PRCOL361E The column number n, specified in ORDER BYclause, does not exist.

Explanation: n is higher than the number of columns to be listed.



PRCOL362E The column column, specified in ORDER BYclause, does not exist.

Explanation: column does not appear as the specification of acolumn to be listed.


User response: Correct the error. Specify the column number if thecolumn specification is not a single field name.

Version 2.02-108

Rep

orter M

essages

PRCOL363E The record record does not belong to the samelog as the record in the previous list specification.

Explanation: If several record types are listed in the sameprocessing of the log, all record types must belong to the same log.



PRCOL364E The list file file is used in a previous listspecification.

Explanation: Two list specifications specified the same output file.Each listed record type must be written to its own output file; theycannot be mixed.



PRCOL365E The number of columns to be listed exceeds theallowed maximum.

Explanation: No more than 120 columns can be listed at the sametime. This maximum is decreased by 1 for each AVG andPERCENTILE column.


User response: Correct the error. You can list the same record typeto another output file in the same processing of the log.


PRCOL366E The LIST RECORD statement requires aGROUP BY clause.

Explanation: If the columns to be listed are specified both with andwithout accumulation functions, a GROUP BY clause is required.The GROUP BY clause must then contain exactly those columns thathave no accumulation function.



PRCOL367E The GROUP BY item number n is not a columnspecification.

Explanation: The item number n of the GROUP BY clause is notpresent among the column specifications in the FIELDS clause. Thus,no grouping can be done on that column.



PRCOL368E The column specification number n is notpresent in GROUP BY clause.

Explanation: The GROUP BY clause specifies that grouping shouldbe done. Column number n is not specified to be a grouping column(it is not present in the GROUP BY clause). The column has noaccumulation function specified and cannot be accumulated.


Version 2.02-110

Rep

orter M

essages

User response: Add the column expression to the GROUP BYarguments or specify an accumulation function for the column.

PRCOL369I The column number n is specified more thanonce in ORDER BY.

Explanation: The ORDER BY clause contains the same expressiontwice. This duplication has no effect on the list processing.


PRCOL370E An error was found in the WHERE clause of thelist specification of record record.

Explanation: Either the WHERE condition is not a condition, or aprevious message explains the cause of the error.



PRCOL371E An error was found during initialization of LISTRECORD record.

Explanation: This message indicates that an error was found in thelist specification for record. A previous error message explains thecause of the error.




PRCOL372E Argument number n of the FIELDS clause is nota valid expression.

Explanation: The argument might be a condition. Or a previousmessage identifies the cause.



PRCOL377W The LIST RECORD processing is interrupteddue to a buffer-full condition.

Explanation: The list output was buffered due to a GROUP BY orORDER BY clause in the list specification. The buffer filled upbefore the input log processing was finished. The buffered rows werewritten to the output file(s), and the processing was ended.

System action: Processing continues for the rows read before thebuffer-full condition.

User response: Rerun LIST RECORD with a larger buffer.

PRCOL378E The LIST RECORD processing is terminated byan overflow.

Explanation: An overflow is the situation when the result of anaccumulation function becomes too large to be stored in the specifiedcolumn.

The LIST RECORD statement specified (explicitly or by default) thatthe processing is to stop in case of overflow. This message ispreceded by message PRCOL350E that provides further details.


Version 2.02-112

Rep

orter M

essages


PRCOL380I n records read from the input log.

Explanation: This message, issued at the end of a LIST RECORDoperation, indicates the quantity of records read from the input log.


PRCOL381I n records written to the file file.

Explanation: This message, issued at the end of a LIST RECORDoperation, indicates the quantity of records written to the named file.


PRCOL401E An invalid SQL condition is specified for table.

Explanation: The SQL condition specified in the WHERE clause ofDEFINE PURGE or RECALCULATE for the table table is not valid.



PRCOL402E The SQL condition exceeds 254 bytes.

Explanation: The SQL condition specified in the WHERE clause ofDEFINE PURGE or RECALCULATE for the table cannot exceed254 bytes.




PRCOL403I The purge condition for table is added.

Explanation: The purge condition for table was successfully added.


PRCOL404I PRCOL405I PRCOL406I

Explanation: Messages PRCOL404I through PRCOL406I are usedto build a table that shows the number of rows deleted from differenttables during a purge process. For an example of such a table, seeFigure 2 on page 2-126.


PRCOL407W Purging data from table with the purgecondition condition was not successful.

Explanation: Check the output for an SQL message that explainsthe reason.



Version 2.02-114

Rep

orter M

essages

PRCOL408I No purge condition exists for the table table.

Explanation: DROP PURGE FROM was not performed ontablebecause no purge condition existed.


PRCOL409I The purge condition for table is dropped.

Explanation: DROP PURGE FROM was successful for table.


PRCOL410I The purge condition for table is altered.

Explanation: DEFINE PURGE was successful fortable.


PRCOL415E There are no tables to be purged.

Explanation: The PURGE statement failed because there were noincluded tables that had a purge condition defined.




PRCOL441E An incorrect number of values is specified in theINSERT clause.

Explanation: If the INSERT clause of the RECALCULATEstatement does not specify any column names, the number of valuesspecified by the clause must be equal to the number of columns inthe table. If the INSERT clause specifies one or more column names,the number of values must be the same as the number of columnnames.


User response: Ensure that the number of values is equal to thenumber of columns in the table, or to the number of specified columnnames.

PRCOL442E An error occurred during initialization ofRECALCULATE.

Explanation: An error occurred during initialization ofRECALCULATE. Message PRCOL442E might be issued inconjunction with other messages that describe the cause of the errorand explain why processing was interrupted.


User response: Check the output for messages issued before thismessage for more information on why the processing was interrupted.Correct the error.

Version 2.02-116

Rep

orter M

essages

PRCOL443E The INSERT clause specifies only the values ofGROUP BY columns. The table already contains arow with these values.

Explanation: The RECALCULATE statement is applied to a tablethat is the target of one or more update definitions. The INSERTclause of the statement specifies values for only those columns thatare used as GROUP BY columns in these updates. The table alreadycontains a row with these values.

System action: The table is not updated. The log collector stopsprocessing the current statement and continues with the next.

User response: Depending on what you intend to achieve, alter theclause to specify values of non-key columns, or specify acombination of key values that is not present in the table.

PRCOL444E The INSERT clause does not specify values of allGROUP BY columns.

Explanation: The RECALCULATE statement is applied to a tablethat is the target of one or more update definitions. The INSERTclause of the statement does not specify values for all columns thatare used as GROUP BY columns in these updates.


User response: Specify values of all GROUP BY columns.


PRCOL445I PRCOL446I PRCOL447I

Explanation: Messages PRCOL445I through PRCOL447I are usedto build a table that shows the number of rows updated, deleted from,and inserted by a RECALCULATE statement. For an example ofsuch a table, see Figure 3 on page 2-127.


PRCOL448E The RECALCULATE statement is terminatedby an overflow.

Explanation: An overflow is the situation when the result of anaccumulation function becomes too large to be stored in the specifiedcolumn. This message is preceded by message PRCOL350E thatprovides further details.



PRCOL449E The INSERT clause specifies null value for oneor more GROUP BY columns.

Explanation: The RECALCULATE statement is applied to a tablethat is the target of one or more update definitions. The INSERTclause of the statement specifies a null value for a column that isused as a GROUP BY column in these updates.


Version 2.02-118

Rep

orter M

essages

User response: Check the INSERT clause. Ensure that all valuesspecified for GROUP BY columns are non-null.

PRCOL450E The table table is specified more than once.

Explanation: The table table appears more than once in the list oftables to be recalculated.


User response: Correct the statement and rerun RECALCULATE.

PRCOL451E The table table is not based on any of thespecified tables.

Explanation: The table table appears in the list of tables to berecalculated. It should have an update definition from another table inthe list, or from the table specified in the clause that follows the list.No such update definition exists.


User response: Correct the statement and rerun RECALCULATE.

PRCOL452E The UPDATE clause specifies null value for oneor more GROUP BY columns.

Explanation: The RECALCULATE statement is applied to a tablethat is the target of one or more update definitions. The UPDATEclause of the statement specifies a null value for a column that isused as a GROUP BY column in these updates.



User response: Check the UPDATE clause. Ensure that all valuesspecified for GROUP BY columns are non-null.

PRCOL461E The ALTER statement was not processed.

Explanation: A previous message explains why the processingstopped.



PRCOL462E FIELDS definition is not allowed here.

Explanation: The FIELDS clause is not allowed in the section partof an ALTER RECORD statement.



PRCOL800T The log collector run terminated abnormally.The standard error file contains detailedinformation.

Explanation: The log collector detected a situation that should notoccur, such as an unexpected return code from SQL, or an invalidvalue of some internal data.

System action: The log collector terminates its run with return code102. Any uncommitted changes to the database are rolled back.Detailed information about the problem is written to the standarderror file.

Version 2.02-120

Rep

orter M

essages

User response: Use the information written to the standard outputand standard error files to establish the reason for termination. Thetermination may be caused by a program error in your log or recordprocedure or in the log collector. If you suspect an error in the logcollector, save the contents of the standard error file, and note asmuch detail as possible of what you were doing when the erroroccurred. Report the error to IBM.

PRCOL801T The log collector run is terminated because ofexcessive load on the system (SIGDANGER).

Explanation: The log collector run was terminated because of anexcessive load on the system.

System action: The log collector terminates its run with return code100. Any uncommitted changes to the database are rolled back.

User response: Stop other applications at your system that requirelarge amounts of storage. When they have terminated, run your logcollector job again.

PRCOL850I Operation successfully completed.

Explanation: A database operation was successfully executed.


PRCOL851W Operation completed. No data found.

Explanation: A database operation was completed with anindication that no data was retrieved, updated, or inserted. Theoperation was either execution of an SQL statement that yousubmitted using the log collector statement SQL, or an operationrequested by the log collector to perform a part of its work.


System action: If the message is about your SQL statement, the logcollector continues with the next statement. If the message is aboutan operation requested by the log collector, the action depends onwhat this result means for the work being done: the log collector mayissue additional messages; it may continue processing, or stopprocessing the current statement, or terminate all processing.

User response: If the message is about your SQL statement, ensurethat this warning message does not indicate a problem that must becorrected. If the message is about an operation requested by the logcollector, and there are additional messages, take the action describedas user response for these messages.

PRCOL852W sql message

Explanation: A database operation resulted in a warning messagesql message from the database manager. The operation was eitherexecution of an SQL statement that you submitted using the logcollector statement SQL, or an operation requested by the logcollector to perform a part of its work.


User response: Refer to your database manual for explanation ofthe message. If the message is about your SQL statement, ensure thatthis warning message does not indicate a problem that must becorrected. If the message is about an operation requested by the logcollector, and there are additional messages, take the action describedas user response for these messages.

Version 2.02-122

Rep

orter M

essages

PRCOL853W Operation completed with a warning.SQLSTATE is sqlstate. CLI return code is cli code.

Explanation: A database operation resulted in an warning from thedatabase interface, but no message is available. The operation waseither execution of an SQL statement that you submitted using thelog collector statement SQL, or an operation requested by the logcollector to perform a part of its work.


User response: Refer to your database manual for explanation ofSQLSTATE. If the message is about your SQL statement, ensure thatthis warning message does not indicate a problem that must becorrected. If the message is about an operation requested by the logcollector, and there are additional messages, take the action describedas user response for these messages.

If SQLSTATE is blank, and you do not see any obvious reason forthe message, note the cli code, save the contents of the standard errorfile, and note as much detail as possible of what you were doingwhen the error occurred. Report the error to IBM.

PRCOL854E sql message

Explanation: A database operation resulted in an error messagesqlmessage from the database manager. The operation was eitherexecution of an SQL statement that you submitted using the logcollector statement SQL, or an operation requested by the logcollector to perform a part of its work.



User response: Refer to your database manual for explanation ofthe message. If the message is about your SQL statement, correct theerror. If the message is about an operation requested by the logcollector, and there are additional messages, take the action describedas user response for these messages.

PRCOL855E Operation completed with an error. SQLSTATEis sqlstate. CLI return code is cli code.

Explanation: A database operation resulted in an error indicationfrom the database interface, but no message is available. Theoperation was either execution of an SQL statement that yousubmitted using the log collector statement SQL, or an operationrequested by the log collector to perform a part of its work.


User response: Refer to your database manual for explanation ofSQLSTATE. If the message is about your SQL statement, correct theerror. If the message is about an operation requested by the logcollector, and there are additional messages, take the action describedas user response for these messages.

If SQLSTATE is blank, and you do not see any obvious reason forthe message, note the cli code, save the contents of the standard errorfile, and note as much detail as possible of what you were doingwhen the error occurred. Report the error to IBM.

Version 2.02-124

Rep

orter M

essages

PRCOL870E Unexpected return code received from database.

Explanation: The log collector received an unexpected return codewhen attempting to execute a database operation.

System action: The message is preceded by one of the messagesPRCOL851W, PRCOL852W, PRCOL853W, PRCOL854E, orPRCOL855E, containing information obtained from the databasemanager. Detailed information about the attempted database operationis written to the standard error file. The message is followed bymessage PRCOL800T and the log collector terminates its operation.

User response: Use the information written to the standard outputand standard error files to establish the reason for termination. Thetermination may be caused by a program error. If you suspect anerror in the log collector, save the contents of the standard error file,and note as much detail as possible of what you were doing when theerror occurred. Report the error to IBM.

PRCOL871S Cannot connect to database manager.

Explanation: The log collector could not connect to the databasemanager. The message is preceded by one of the messagesPRCOL854E or PRCOL855E, containing information returned by thedatabase manager in response to the request for connection.

System action: The log collector is not run.

User response: Refer to your database manual for explanation ofthe information provided by the message PRCOL854E orPRCOL855E. Establish the cause of the failure to connect andremove it.


PRCOL3ððI Collect started at 1997-ð5-15-1ð.27.14.

PRCOL3ð2I Processing log/merge1.

PRCOL3ð4W The log file is being reprocessed.

PRCOL31ðI A database update started after 9 records due to end of log.

PRCOL328I Reading lookup table PERFREP.CAL_SPECIAL_DAY: ð rows, ð bytes.

PRCOL328I Reading lookup table PERFREP.CAL_DAY_OF_WEEK: 14 rows, 42ð bytes.

PRCOL328I Reading lookup table PERFREP.CAL_DAY_PERIOD: 12 rows, 648 bytes.

PRCOLðð3I

PRCOL315I Records read from the log or built by log procedure:

PRCOL317I Record name | Number

PRCOL318I -------------------|----------

PRCOL319I RES_DATA_A | 5

PRCOL319I RES_DATA_B | 1

PRCOL319I RES_DATA_C | 3

PRCOL318I -------------------|----------

PRCOL321I Total | 9

PRCOLðð3I

PRCOL323I -------Buffer------ ------Database-----

PRCOL324I Table name | Inserts Updates Inserts Updates

PRCOL325I ----------------------------|----------------------------------------

PRCOL326I PERFREP .AVAIL_BY_SHIFT | 2 12 2 ð

PRCOL326I PERFREP .AVAIL_STATUS | 13 11 13 ð

PRCOL325I ----------------------------|----------------------------------------

PRCOL327I Total | 15 23 15 ð

PRCOLðð3I

PRCOL3ð1I Collect ended at 1997-ð5-15-1ð.27.17.

Figure 1. An example of messages generated by a COLLECT statement. It illustrates the use ofmessages PRCOL317I through PRCOL327I.

PRCOL3ððI Purge started at 1997-ð5-15-15.39.58.

PRCOL4ð4I Table name | Deletes

PRCOL4ð5I ---------------------------|---------

PRCOL4ð6I PERFREP .STATS_D | 1

PRCOL4ð6I PERFREP .STATS_H | 3

PRCOL3ð1I Purge ended at 1997-ð5-15-15.39.59.

Figure 2. An example of messages generated by a PURGE statement. It illustrates the use of messagesPRCOL404I through PRCOL406I.

Version 2.02-126

Rep

orter M

essages

PRCOL445I Table name | Updates Deletes Inserts

PRCOL446I ----------------------------|------------------------------

PRCOL447I PERFREP .STATS_H | ð ð 1

PRCOL447I PERFREP .STATS_D | 1 ð ð

Figure 3. An example of messages generated by a RECALCULATE statement. It illustrates the use ofmessages PRCOL445I through PRCOL447I.


PRCOM Common MessagesThis section lists PRCOM messages. They are common messagesshared by many programs.

PRCOM001E Usage: command arguments

Explanation: You specified an incorrect syntax of the command.


User response: Correct the syntax and rerun the command.

PRCOM002E program: The file or directory name was notaccessed.

Explanation: The named file or directory does not exist or youcannot access it.


User response: Ensure that the file or directory exists and you canaccess it and try again.

Version 2.02-128

Rep

orter M

essages

PRCOM003E program: The file file was not saved.

Explanation: The named file was not saved because no more spaceis available in the file system.


User response: Extend the file system or delete unnecessary filesfrom that file system and try again.

PRCOM004E program: The command command ended withreturn code rc.

Explanation: The named command was not successful. See thefollowing messages for further information.


User response: See the following messages for further action.

PRCOM005I The command command is being processed.

Explanation: The request is being processed.




PRCOM006E program: The parameter parameter does notexist in the parameter file.

Explanation: The named parameter was not retrieved from theparameter file.


User response: Add the parameter and value in the parameter file.The syntax is parameter = value.

PRCOM007I Select List to see the valid values.

Explanation: This message follows other messages. It gives youfurther information on the action to take.

System action: The system waits for user input.

User response: Select a value from the list and try again.

PRCOM008I program: The default value value is used.

Explanation: This message follows another message. It gives youfurther information.



Version 2.02-130

Rep

orter M

essages

PRCOM009I program: Messages from the command command:

Explanation: This message is followed by other messages issuedfor the named command.



PRCOM010E program: zccdbcmd did not execute the SQLstatement statement in database. The return code isrc.

Explanation: The system did not access to the database. See theprevious messages for further information.


User response: See the previous message for further action.

PRCOM011E program: The directory directory specified bythe parameter parameter does not exist.

Explanation: The named directory does not exist or you cannotaccess it.


User response: Use SMIT to correct the directory name in theparameter file or ensure you have access to the named directory andtry again.


PRCOM012W program: Cannot write to the directorydirectory specified by the parameter parameter.

Explanation: You do not have write permission to the nameddirectory.


User response: Use SMIT to correct the file name in the parameterfile or ensure you have write permission to the named directory andtry again.

PRCOM013E Cannot write to the file file.

Explanation: You do not have write permission to the named file.


User response: Ensure you have write permission to the file and tryagain.

PRCOM014W Cannot write to the file file.

Explanation: You do not have write permission to the named file.

System action: The current operation is not performed butprocessing continues normally.


Version 2.02-132

Rep

orter M

essages

PRCOM015E Cannot find the file or directory name.

Explanation: The named file or directory does not exist or youcannot read it.


User response: Correct the file name or ensure you have readpermission to it.

PRCOM016W Cannot find the file or directory name.

Explanation: The named file or directory does not exist or youcannot read it.




PRDSP Report Generation MessagesThis section lists PRDSP messages. They appear when you are usingthe graphical interface to display reports.

PRDSP001E No values were specified for the following fields:fields

Explanation: You did not specify any values for the named fields.

System action: No report is generated.

User response: Specify the values required for the fields listed inthe message.

PRDSP002E Specify a print command.

Explanation: You did not specify any print command.

System action: The report is not printed.

User response: Specify a print command.

PRDSP003E Specify the name of the file where to save thedata.

Explanation: You did not specify a file where to save the report.

System action: The report is not saved.

User response: Specify a file name.

Version 2.02-134

Rep

orter M

essages

PRDSP004E Cannot open the file file.

Explanation: The program did not open the file where you want tostore the report.


User response: Ensure that you have write permission to the file.

PRDSP005E Cannot save the tabular report to the file file.

Explanation: The program did not save the report to the named file.


User response: Ensure that the file system is not full.

PRDSP006E Cannot save the graphical report to thePostScript file file. The XRT/graph message ismessage.

Explanation: The program did not save the report to the named file.The XRT/graph message gives further indication about the problem.


User response: See the XRT/graph message for further action.

PRDSP007E Cannot save the graphical report to theXRT/graph file file. The XRT/graph message ismessage.

Explanation: The program did not save the report to the named file.The XRT/graph message gives further indication about the problem.




PRDSP008E n columns are selected. Across computationrequires exactly three columns.

Explanation: You defined a report using across computation, whichrequires that exactly 3 columns are included in the select statement.


User response: Either change the select statement in the reportdefinition to include exactly 3 columns, or do not use acrosscomputation.

PRDSP009E The column column must be numeric for acrosscomputation.

Explanation: You defined a report using across computation, whichrequires the third column to be numeric.


User response: Either change the select statement in the reportdefinition to have the third column as nonnumeric, or do not useacross computation.

PRDSP010W The column column must be numeric. Thecolumn is ignored.

Explanation: You chose to view in graphical mode a report that hasa nonnumeric value for the named column. That column is ignored,because in a graphical report only the first column can benonnumeric.

System action: The named column is not displayed.

Version 2.02-136

Rep

orter M

essages

User response: To display the named column, view the report intabular mode.

PRDSP011E There are no available values for the field field.

Explanation: No data is stored in the database for the named field.

System action: No list of values is shown.

User response: The table from which the report extracts data isempty. See the section about working with report definitions in theReporting Dialog Guide.

PRDSP012E Select a value.

Explanation: You did not select any value from the list.

System action: The list is still displayed.

User response: Either select a value or select CANCEL to cancelthe list.

PRDSP013E The minimum or maximum value value isincorrect.

Explanation: You entered a value that is not numeric.

System action: The graphical report is not modified.

User response: Specify a numeric value.


PRDSP014E The minimum value n1 must be less than themaximum value n2.

Explanation: You specified a minimum value that is not lower thanthe corresponding maximum value.

System action: The graphical report is not modified.

User response: Specify valid values.

PRDSP016E Specify the paper width, height, and margin.

Explanation: You did not set all the required values in thePrint/Save Graphical Data window.

System action: The report is not printed or saved.

User response: Enter the required values.

PRDSP017E The value value is incorrect for paper width,height, and/or margin.

Explanation: You set an incorrect value in the Print/Save GraphicalData window.


User response: Specify valid values.

Version 2.02-138

Rep

orter M

essages

PRDSP018E Cannot multiply n1 and n2. The result is toolarge.

Explanation: The program did not perform the conversion fromcentimeters to inches or from inches to centimeters. One of the valuesspecified is too large.

System action: The conversion is not performed.

User response: Specify a smaller value.

PRDSP019E Invalid SELECT statement: statement.

Explanation: The named SELECT statement in the query file is notcorrect.

System action: The report is not generated.

User response: Modify the SELECT statement in the query file andtry again.

PRDSP020E There is no SELECT statement in the query file:file.

Explanation: The named query file does not contain a SELECTstatement.


User response: Modify the query file and try again.


PRDSP021E The SELECT statement does not end with asemicolon in the file file.

Explanation: The SELECT statement does not end with asemicolon in the named file.



PRDSP022E There is extra text text after the SELECTstatement.

Explanation: A query file must contain exactly one SELECTstatement, which cannot be followed by other statements.



PRDSP023E The variable name name is invalid.

Explanation: The named variable in the query file contains blanksand/or quote characters.



Version 2.02-140

Rep

orter M

essages

PRDSP024W The values you entered in the dialog are notsaved. They will not be used in subsequentsessions.

Explanation: You entered values that the program did not save. Thevalues will not be available in subsequent sessions. Defaults will beused.


User response: Ensure that the parameter Save State Path is set to adirectory for which you have write permission and that there isenough space in the file system.

PRDSP025I Started printing the tabular report using the printcommand command.

Explanation: A tabular report is scheduled for printing.



PRDSP026I Started printing the graphical report using theprint command command.

Explanation: A graphical report is scheduled for printing.




PRDSP027I The tabular report is saved to the file file.

Explanation: The tabular report is saved to the named file.



PRDSP028I The graphical report is saved in XRT/graphformat to the file file.

Explanation: The graphical report is saved in XRT/graph format tothe named file.



PRDSP029I The graphical report is saved in PostScriptformat to the file file.

Explanation: The graphical report is saved in PostScript format tothe named file.



Version 2.02-142

Rep

orter M

essages

PRDSP030Q Do you want to save the graphical options forthe report definition definition to the file file?

Explanation: You are asked to confirm to save the graphicaloptions for the named report to the named file.

System action: The system waits for your input.

User response: Select Yes to save the graphical options to thenamed file, otherwise select No.

PRDSP031W The extracted report has only n columns.

Explanation: The number of columns extracted from the database isless than two.


User response: Ensure that the SELECT statement in the query filefor the report has at least two columns.

PRDSP033E Cannot create a PostScript file where to storedata.

Explanation: A PostScript file was not created.


User response: Ensure you have write permission to the currentdirectory and that the file system is not full.


PRDSP034E Cannot write to the PostScript file file.

Explanation: No data was written to the named PostScript file.


User response: Ensure you have write permission to the currentdirectory and that the file system is not full.

PRDSP035E XRT/graph cannot write to the PostScript filefile. The XRT/graph message is message.

Explanation: XRT/graph did not write any data in the namedPostScript file. The XRT/graph message gives further indicationabout the problem.



Version 2.02-144

Rep

orter M

essages

PRGTH Data Gathering MessagesThis section lists PRGTH messages. They appear when data is beinggathered on the agents.

PRGTH001E program: An error occurred when thesubroutine subroutine was called.

Explanation: An internal error on a subroutine call occurred.


User response: Contact your IBM/Tivoli representative.

PRGTH002E program: An error occurred when the commandcommand was executed.

Explanation: An internal error on a command call occurred.


User response: See the previous messages for further action.

PRGTH003E program: Cannot write the record in the log filefile. The subroutine fputs() was not successful.

Explanation: The subroutine fputs() was not successful, probablybecause the file system is full.



User response: Check the size of the file system where the log filesare located by using the command df file. If the file system is full,extend it or delete unnecessary files, and then rerun the command.

PRGTH004E program: An error occurred on the commandcommand while processing the record record.

Explanation: An internal error occurred when creating a log filerecord.



PRGTH005E program: An error occurred. Cannot write therecord record to the log file.

Explanation: An internal error occurred when creating a log filerecord.


User response: See the previous messages for further action, orcontact your IBM/Tivoli representative.

PRGTH006E program: Incorrect date date was specified.

Explanation: The date you specified is incorrect.


User response: See the following message for further action.

Version 2.02-146

Rep

orter M

essages

PRGTH007W program: Disk gathering is not supported on HPand Sun.

Explanation: The disk log in the performance component is notgathered on the specified node.

System action: If only disk gathering is requested, the operation isnot performed. If the Performance component was specified, only theperf gathering is started.


PRGTH008E program: Incorrect time time was specified.

Explanation: The time you specified in the parameter file is invalid.


User response: Use SMIT to set the right value for the fieldPerformance Log Gathering Interval (from 1 to 86 400 seconds),Performance Log Gathering Counter (from 1 to 24 800 seconds), orDisk Log Gathering Interval (from 1 to 1 440 minutes).

PRGTH009W program: Internal error when processing outputfrom the command command.

Explanation: An internal error occurred while creating a record inthe log file.




PRGTH010E program: Cannot allocate storage using theinternal routine routine.

Explanation: Additional memory is not allocated.


User response: Ensure that the running processes do not require toomuch memory and try again.

PRGTH011E The daemon daemon is stopped by the signalsignal.

Explanation: A signal was sent to stop a daemon.


User response: Restart the daemon. If the same error occurs again,contact your IBM/Tivoli representative.

PRGTH012I program: The date format must be yymmdd.

Explanation: The date was specified in the wrong format.

System action: No date is returned.

User response: Enter the date in the form yymmdd, whereyy is theyear,mm is the month, anddd is the day. If the error was generatedby one of the programs provided with the product, contact yourIBM/Tivoli representative.

Version 2.02-148

Rep

orter M

essages

PRGTH014E program: There is not enough space on the filesystem file system.

Explanation: The free space on the file system where the log filesare located is less than the value set for the parameter Free Space inLog File Directory in the parameter file.


User response: Make more free space available on the file system(either by extending the file system or deleting unnecessary files) oruse SMIT to change the value set for the parameter Free Space inLog File Directory. Then issue the command prgather again.

PRGTH015I program: Gathering for the log file log completedsuccessfully.

Explanation: The log file for the named log was created.



PRGTH016E program: Cannot retrieve the last recordtimestamp from the previous processing.

Explanation: The control file with the timestamp of the lastprocessed record is corrupted. This message can occur for NetViewor Systems Monitor gathering.

System action: See the following message for further information.

User response: Contact your IBM/ representative.


PRGTH017E program: The command command was notsuccessful. The log file log is not created.

Explanation: Gathering for the named log was not successful. Thelog file will not be transferred to and collected on the manager.

System action: The named log file is not created.


PRGTH018I program: The following processes are running forthe daemon daemon:

Explanation: This message is followed by a list of processes thatare running for the named daemon.



PRGTH019E program: The daemon daemon is not running.

Explanation: The named daemon is not running.


User response: If the Performance component is active on the agentnode, start the daemon by issuing the command practperfd .

Version 2.02-150

Rep

orter M

essages

PRGTH020E program: The daemon daemon is alreadyrunning.

Explanation: The daemon is already running.



PRGTH021I program: To start the daemon, first stop it byissuing the command command.

Explanation: To restart a running daemon you have to stop it first,by using the named command.


Explanation: Run the named command to stop the daemon. Youcan then restart it.

PRGTH022I program: Processing: record.

Explanation: This message is for tracing purposes.




PRGTH024I program: No poll interval is specified. The defaultvalue (n seconds) is used.

Explanation: The default value n seconds is used, because the pollinterval is not specified in the parameter file.

System action: Processing continues using the default poll interval.

User response: Use SMIT to set another value for the poll intervalin the parameter file and issue the command again.

PRGTH025I program: Additional memory cannot be allocated.



User response: See the following messages for further action.

PRGTH026I program: Total number of Systems Monitorrecords read: n.




Version 2.02-152

Rep

orter M

essages

PRGTH027I program: Number of valid Systems Monitorrecords read: n.




PRGTH028W program: The last timestamp cannot be saved.

Explanation: The timestamp of the last record is older than thetimestamp from the previous processing.

System action: The timestamp for the last processed record is notsaved. The next time Systems Monitor gathering is performed, thesame records that were just processed will be gathered again.

User response: Check if the file sysmond.col contains incorrecttimestamps. If it does, remove them manually or contact your IBMrepresentative.

PRGTH029E program: An error occurred when the parameterfile was read.

Explanation: The parameters in the parameter file cannot beaccessed.


User response: Ensure that you have read permission to theparameter file, which is /etc/perfrep/perfrep.cfg by default.


PRGTH030E program: The file file cannot be created.

Explanation: The gathering of the file is not performed, becauseyou do not have the required permissions to the directory.


User response: Ensure that you have write permission to thedirectory where the log files are created, which is /var/perfrep bydefault.

PRGTH031E program: The node name cannot be returned.

Explanation: An internal error occurred.


User response: Contact your IBM representative.

PRGTH032I program: Total number of subtype subtype logrecords written: n.




Version 2.02-154

Rep

orter M

essages

PRGTH035W program: The user ID user ID in the pacct file isincorrect.

Explanation: An internal error occurred while parsing the file/var/adm/acct/nite/opacct.

System action: This record is not processed. The program continuesnormally.

User response: Check for error messages about the runacctcommand in the /var/adm/acct/nite/accterr file.

PRGTH036W program: The group ID group ID in the pacctfile is incorrect.

Explanation: An internal error occurred while parsing the file/var/adm/acct/nite/opacct.

System action: The record is not processed. The program continuesnormally.

User response: Check if error messages were stored about therunacct command in the file /var/adm/acct/nite/accterr.

PRGTH037E program: The day n is incorrect. log gathering isnot performed.

Explanation: The Configuration date is not valid. It must be anumber between 1 and 31, or a list of numbers separated by blanks.

System action: Configuration gathering is not performed.

User response: Specify a valid number and issue the commandagain.


PRGTH039E program: Systems Monitor user data gatheringwas not successful.

Explanation: The gathering of user data from Systems Monitor wasnot performed.



PRGTH040E program: Systems Monitor Token-ring gatheringwas not successful.

Explanation: The gathering of Token-ring data from SystemsMonitor was not performed.



PRGTH041E program: Systems Monitor response timegathering was not successful.

Explanation: The gathering of response time data from SystemsMonitor was not performed.



Version 2.02-156

Rep

orter M

essages

PRGTH043I program: Configuration data is not created.

Explanation: The days on which the gathering of Configurationdata is scheduled are specified with the parameter Configuration Datein the parameter file. Gathering is not scheduled on the current day.

System action: No Configuration data is created.

User response: Use SMIT to modify the parameter ConfigurationDate in order to change the days on which gathering configurationdata. Then deactivate and activate the Configuration componentagain.

PRGTH044I program: Configuration data will be created onlythe days n of every month.

Explanation: The gatehring of configuration data is scheduled onlyon the named days of the month.



PRGTH045E program: A parsing error occurred whenprocessing the log file file.

Explanation: An internal error occurred while creating a log filerecord.


User response: Contact your IBM representative.


PRGTH047E program: The log log is already scheduled.

Explanation: You tried to activate a log on a node where it isalready active.

System action: Processing continues and control is returned to theoperating system.

User response: Use SMIT to check which logs are active on thenode. Ensure that the logs listed are the same as those shown by thecommands prgather (in the cron table) and prpsperfd.

PRGTH048E program: The log log is not scheduled.

Explanation: You tried to deactivate a log on a node where it isalready inactive.


User response: Use SMIT to check which logs are active on thenode. Ensure that the logs listed are the same as those shown by thecommands prgather (in the cron table) and prpsperfd.

PRGTH049E program: Systems Monitor Ethernet gatheringwas not successful.

Explanation: The gathering of the Ethernet data from the SystemsMonitor was not successful.



Version 2.02-158

Rep

orter M

essages

PRGTH051E program: The parameter parameter must benumeric.

Explanation: The named parameter must be numeric.


User response: Use SMIT to specify a numeric parameter and issuethe command again.

PRGTH052E program: Insufficient authority to stop theprocesses.

Explanation: The processes are not stopped.


User response: Ensure you have the authority required to stop theprocesses and issue the command again.


PRGUI Report Generation and HandlingMessages—Graphical Interface

This section lists PRGUI messages. They appear when you are usingthe graphical interface to generate and handle reports.

PRGUI001E LibGui error: the subroutine subroutine was notsuccessful.

Explanation: An internal error in a subroutine occurred.


User response: If the error persists, contact your IBM/Tivolirepresentative.

PRGUI002E A group template with the name name alreadyexists.

Explanation: You specified a name that is not unique.

System action: The group template is not created. Processingcontinues normally.

User response: Specify a unique name.

Version 2.02-160

Rep

orter M

essages

PRGUI003E A report template with the name name alreadyexists.

Explanation: You specified a name that is not unique.

System action: The report template is not created. Processingcontinues normally.

User response: Specify a unique name.

PRGUI004E Cannot write to the file file.

Explanation: You do not have the permission required to write tothe named file.

System action: The file is not created. Processing continuesnormally.

User response: Ensure that you have the permission required towrite to the file.

PRGUI006E The file file does not exist.

Explanation: A query file or a graphical options file that wasspecified for a report template definition does not exist.

System action: The report or report template is not created orupdated.

User response: Specify the name of an existing file.


PRGUI008Q The query file was modified. Are you sure youwant to cancel the changes?

Explanation: You selected to quit from the editor program. If youdo, your changes to the query file will be cancelled.

System action: If you select Yes, you exit the editor program andthe changes made are not saved. If you select No, you can continueediting the file.

User response: Select Yes to cancel the changes or No to continue.

PRGUI009E Your user ID is not returned by the system. Thefield field is not updated.

Explanation: An internal error occurred while the system wasreturning the user ID. The named field is not updated.



PRGUI010E Cannot create the dialog window.


System action: The window is not displayed. Processing continuesnormally.


Version 2.02-162

Rep

orter M

essages

PRGUI011E Cannot display the dialog window.


System action: The window is not displayed. Processing continuesnormally.


PRGUI012Q The query file file is used also by another reportdefinition. Are you sure you want to edit the file?

Explanation: You have to confirm whether you want to edit thenamed query file.

System action: If you select Yes, the editor program is started. Ifyou select No, the editor program is not called.

User response: Select Yes to continue or No to exit the program.

PRGUI013E Enter a value for the field field.

Explanation: A required field in a dialog is to be assigned a value.

System action: The requested operation is not performed.Processing continues normally.

User response: Enter the required value and try again.


PRGUI014E Cannot find a value for the parameter parameterin the parameter file.

Explanation: The system did not find any value for the namedparameter.


User response: Use SMIT to specify the missing value in theparameter file.

PRGUI016I No object matching the searching criteria wasfound.

Explanation: The program did not find any objects that you weresearching for.



PRGUI017I The file old file was successfully copied to new file.

Explanation: The query file is copied to the named new file. TheQuery File field is updated with the new file name.


User response: To use the named new file as the current query file,select OK or Apply in the Show/Modify Report Definition window.

Version 2.02-164

Rep

orter M

essages

PRGUI018E Cannot start the help.

Explanation: The help cannot be started.


User response: Ensure that the manager images are installedcorrectly.

PRGUI019E Your environment is not configured to useReporter.

Explanation: Your environment is not configured for Reporter.




PRINS Installation MessagesThis section lists PRINS messages. They appear when you installReporter.

PRINS001E program: The database setup was not successful.The program ended with the return code rc.

Explanation: An error occurred during the creation or initializationof the Reporter system tables. The database setup may havecompleted partially.


User response: Refer to the log file /var/perfrep/prsetupdb.log tohave more information about the error. Before issuing the programprsetupdb again, you can delete all tables by running the programprdroptables

PRINS002I Creating Reporter system tables, using prefix astable prefix.

Explanation: Reporter system tables are being created.



Version 2.02-166

Rep

orter M

essages

PRINS003W program: Unable to write to the log file file.

Explanation: The program prsetupdb did not direct its output tothe named log file.

System action: The output is directed to the screen.


PRINS006I program: The file system file system is alreadydefined.

Explanation: The named file system already exists, probably from aprevious installation of Reporter. No file system is created.



PRINS007I program: The file system file system will bemounted.

Explanation: The named file system exists but is not mounted. Itwill be mounted.




PRINS009I program: Messages will be spooled to the log filefile.

Explanation: The program prsetupdb directs its output to thenamed log file.


User response: See the log file /var/perfrep/prsetupdb.log afterthe program is run. If prsetupdb.log is located on your homedirectory, ensure you have write permission to the /var/perfrepdirectory. The Reporter administrator needs write permission to thisdirectory.

PRINS010I Initiating Reporter system tables for prefix.

Explanation: The new Reporter system tables are being initiated.



PRINS011I DBMS..................: dbms

Explanation: The Data Base Management System parameter is setto the value shown.


User response: Ensure that the value is correct. Only DB2,ORACLE, and SYBASE are valid values.

Version 2.02-168

Rep

orter M

essages

PRINS012I Table space...........: table space

Explanation: The table space is set to the value shown.


User response: Ensure that the value is correct.

PRINS013I Table prefix..........: prefix

Explanation: The table prefix is set to the value shown.



PRINS014I User group............: group

Explanation: The database group for Reporter users is set to thevalue shown.



PRINS015I Administrator group...: group

Explanation: The database group for Reporter administrator is setthe value shown.




PRINS016I The following values will be used:

Explanation: This message is followed by a list of the parametervalues.


User response: Ensure that the values are correct.

PRINS017Q Press Enter to continue, or type any nonblankcharacter to modify the values.

Explanation: This message follows a list of values that you canmodify.

System action: If you press Enter, processing continues normally. Ifyou type a nonblank character, you can modify the values.

User response: Press Enter to continue and use the values listed, ortype a nonblank character to modify those values.

PRINS018Q Type a new value or press Enter to accept thevalue shown.

Explanation: The value that was set is shown in brackets. You canaccept or modify it.


User response: Press Enter to accept the value shown. Otherwise,type a new value.

Version 2.02-170

Rep

orter M

essages

PRINS019Q DBMS (dbms):

Explanation: Data Base Management System is set to the valueshown in brackets.


User response: Ensure that the value shown is correct. Press Enterto accept it, or type a new value. Only DB2, ORACLE, andSYBASE are correct values.

PRINS020Q Table space (table space):

Explanation: The table space is set to the value shown in brackets.


User response: Ensure that the value shown is correct. Press Enterto accept it, or type the name of a table space defined in your DataBase Management System.

PRINS021Q Table prefix (prefix):

Explanation: The table prefix is set to the value shown in brackets.


User response: Ensure that the value shown is correct. Press Enterto accept it, or type the name of a table prefix defined in your DataBase Management System.


PRINS022Q User group (group):

Explanation: The database group for Reporter users is set to thevalue shown in brackets.


User response: Ensure that the value shown is correct. Press Enterto accept it, or type the name of a database group defined in yourData Base Management System.

PRINS023Q Administrator group (group):

Explanation: The database group for Reporter administrator is setto the value shown in brackets.


User response: Ensure that the value shown is correct. Press Enterto accept it, or type the name of a database group defined in yourData Base Management System.

PRINS025Q Press Enter to continue, or type any nonblankcharacter to exit.

Explanation: This message follows a list of parameters to be usedduring the database setup.

System action: If you press Enter, processing continues normally. Ifyou type a nonblank character, the program stops and control isreturned to the operating system.

User response: Ensure that the values are correct. Press Enter tocontinue or any nonblank character to exit the program.

Version 2.02-172

Rep

orter M

essages

PRINS026I Inserting calendar data.

Explanation: The default calendar is being added.



PRINS027I The database is successfully setup.

Explanation: The Reporter database is now ready.



PRINS028I Inserting report templates.

Explanation: Default report templates are being added.



PRINS030E The table prefix prefix exceeds maximum lengthof eight characters.

Explanation: You specified a value for the table prefix that exceedsthe maximum length of eight characters.


User response: Specify a table prefix with a name of maximumeight characters.


PRINS031I No tables are created.

Explanation: The setup of the Reporter database was notsuccessful.


User response: See the previous message from the Data BaseManagement System for further action.

PRINS032E program: An error occurred when creating thefile system file system.

Explanation: The named file system was not created.

System action: The command is not run.

User response: See previous messages for further action. Thenamed program must be run by the user root.

PRINS033E dbms is not a supported database system. Validvalues are DB2, ORACLE, or SYBASE.

Explanation: The Data Base Management System you specified isnot supported by Reporter.


User response: Valid values are DB2, ORACLE, or SYBASE.Enter the one that you are using. Ensure you have also thecorresponding Reporter database package (perfrep_db2, perfrep_ora,or perfrep_syb) installed.

Version 2.02-174

Rep

orter M

essages

PRINS034E You have not installed a Reporter databasepackage.

Explanation: To use the database setup program a Reporterdatabase package must be installed.


User response: Install a Reporter database package and issue thecommand again. The available packages are perfrep_db2, perfrep_ora,or perfrep_syb.

PRINS037E A symbolic link for the dbms shared library is notset correctly.

Explanation: Each supported Data Base Management System hasits own shared library. The symbolic link libPrDb.a must refer to thecorrect library.


User response: Logon as root and issue the command ln -s -f/usr/lpp/perfrep/lib/libPrDB2.a /usr/lpp/perfrep/lib/libPrDb.a .Replace libPrDB2.a with libPrOra.a , if you are using ORACLE, orlibPrSyb.a if you are using SYBASE.

PRINS038I Logon as root.

Explanation: You issued a command that can be executed only bythe user root.


User response: Logon as root and issue the command again.


PRINS039I Issue the command: ln -s -f/usr/lpp/perfrep/lib/libPr dbms.a/usr/lpp/perfrep/lib/libPrDb.a

Explanation: Each supported Data Base Management System hasits own shared library. The symbolic link libPrDb.a must refer tothe correct library.


User response: Logon as root and issue the command shown. Thecorrect shared libraries are libPrDB2.a if you are running DB2,libPrOra.a if you are running ORACLE, or libPrSyb.a if you arerunning SYBASE.

PRINS041E The Reporter system tables creation was notsuccessful. The program ended with the returncode rc.

Explanation: The program did not create the Reporter systemtables. The system tables may have been created partially.


User response: Refer to the log file /var/perfrep/prsetupdb.log tohave more information about the error. Before issuing the programprsetupdb again, you can delete all tables by running the programprdroptables.

Version 2.02-176

Rep

orter M

essages

PRINS042E The grant of privileges on Reporter system tablesfailed. The program ended with the return code rc.

Explanation: The program did not grant access to the Reportersystem tables. Access may have been granted partially.



PRINS043E Comments to the Reporter system tables were notadded. The program ended with the return coderc.

Explanation: The program did not add comments on the Reportersystem tables. Comments may have been partially added.




PRINS044W The Reporter administrator, user ID, is not amember of the AIX adm group. After thisprogram is run, logon as root and add user ID toadm.

Explanation: The Reporter administrator must be a member of theAIX adm group to execute commands.


User response: Add the Reporter administrator to the AIX admgroup after prsetupdb is run.

PRINS047Q Press Enter to continue, or type any nonblankcharacter to exit.

Explanation: This message follows a list of parameters to be usedduring the database setup.

System action: If you press Enter, processing continues normally. Ifyou type a nonblank character, the program stops and control isreturned to the operating system.

User response: Ensure that the values are correct. Press Enter tocontinue or type a nonblank character to exit the program.

PRINS048E program: user ID did not connect to dbms. Checkthe user ID authority.

Explanation: The user cannot connect to the named database.


User response: Ensure that the environment variables for thedatabase are correctly set. Those variables are documented in

Version 2.02-178

Rep

orter M

essages

/etc/perfrep/dbprofile, where dbprofile is prdb2profile , oraenv, orprsybprofile .

Explanation: The user does not have the database authority requiredto perform the requested operation.


User response: Grant authority authority as system administrator tothe named user ID.

PRINS052E You did not install the Reporter databasepackage for dbms. Install the perfrep_user IDpackage before continuing.

Explanation: To run the database setup program prsetupdb thedatabase package must be installed.


User response: Install the perfrep_dbms package and rerun theprogram.

PRINS054E program: Environment variables for dbms are notset correctly. Press Enter to exit, or type anynonblank character to set the variables by runningthe file file.

Explanation: The parameter Database Environment Variables Filemust be set to a file containing the environment variables for thedatabase.

System action: If you type a nonblank character, processingcontinues normally. If you press Enter, the program stops and controlis returned to the operating system.


User response: If you have set the parameter Database EnvironmentVariables File correctly, continue by typing a nonblank character,otherwise press Enter to exit the program.

PRINS056E program: Failed to source the dbsetup file. Verifythat the file is correct and rerun the programprogram.

Explanation: The file that contains the environment variables forthe database contains an error.


User response: Correct the file and rerun the program.

PRINS057E program: The environment variable variable is notset and the parameter Database EnvironmentVariables File is not defined.

Explanation: To run Reporter the parameter Database EnvironmentVariables File is requested.


User response: Set the parameter Database Environment VariablesFile to a file containing the environment variables for the databaseand rerun the program.

Version 2.02-180

Rep

orter M

essages

PRINS058Q Enter the name of a file that sets the databasedbms environment variables, including environmentvariables, or press Enter to exit the programprogram.

Explanation: The parameter Database Environment Variables Filemust be set to a file containing the environment variables for thedatabase.

System action: If you enter the name of a file, processingcontinues. If you press Enter, the program stops and control isreturned to the operating system.

User response: Enter the name of a file containing the environmentvariables, or press Enter to exit the program, set the parameter andenvironment variables, and rerun the program.

PRINS061I A sample file, /etc/perfrep/file, is shipped withReporter. Edit this sample file before using it.

Explanation: The named file, containing database environmentvariables, is shipped with Reporter for you to edit.

System action: See the previous message for further information.

User response: Edit the sample file to meet your requirements.

PRINS063E program: The role role does not exist in dbms.Press Enter to exit, or type any nonblankcharacter to create the role.

Explanation: The named role does not exist in dbms.

System action: If you press Enter, the program stops and control isreturned to the operating system. If you type a nonblank character,you can continue by creating the role.


User response: Press Enter to exit the program, or type a nonblankcharacter to create the role.

PRINS065I You need database administration authority.

Explanation: Database administration authority is required toperform the operation you requested. See the previous message forfurther action.


User response: Logon with a user ID that has databaseadministration authority and issue the command again.

PRINS066E program: The group group does not exist in dbms.

Explanation: The named group does not exist in dbms.



PRINS067I Press Enter to exit, or type any nonblankcharacter to create the group.

Explanation: A group does not exist.

System action: If you press Enter, the program stops and control isreturned to the operating system. If you type a nonblank character,you can continue by creating the group.

User response: Press Enter to exit the program, or type a nonblankcharacter to create the group.

Version 2.02-182

Rep

orter M

essages

PRINS068E program: The AIX group group does not exist.Logon as root and use SMIT to create the group.

Explanation: The named AIX group defined in the parameter filedoes not exist.


User response: Create the AIX group or set the parameter UserGroup or Administrator Group to an existing AIX group.

PRINS071I Run the procedure sp_addgroup group in isql.

Explanation: The named group is to be added.


User response: Issue the command isql, then add the group to thedatabase by using the named procedure.

PRINS072E program: The user ID user ID does not exist inoperating system/dbms.

Explanation: The named user ID is not defined in the namedoperating system or database.




PRINS073I Press Enter to exit, or type any nonblankcharacter to create the user ID in the database.

Explanation: A user ID does not exist in the database.

System action: If you press Enter, the program stops and control isreturned to the operating system. If you type a nonblank character,you can continue by creating the user ID in the database.

User response: Press Enter to exit the program, or type a nonblankcharacter to create the user ID in the database.

PRINS075I Logon as root and use SMIT to create the user IDuser ID.

Explanation: The named user ID, specified by the parameter TablePrefix, does not exist.


User response: Create the user ID or use SMIT to set the parameterTable Prefix to an existing user ID.

PRINS077E program: The user ID user ID does notcorrespond to the table prefix prefix. Change theAIX user ID to prefix, or change the table prefix touser ID.

Explanation: The table prefix specified by the parameter TablePrefix must be the same as your user ID, when you use SYBASE.


User response: Either change the AIX user ID to prefix or changethe table prefix to user ID.

Version 2.02-184

Rep

orter M

essages

PRINS080I Issue isql as system administrator and add theuser ID user ID by issuing sp_adduser prefix, prefix,role

Explanation: The named user ID must be defined in the database,when you use SYBASE.


User response: Issue the command isql and add the user ID.

PRINS082I A dbms password is required for the user ID userID.

Explanation: A database password is required to access thedatabase.



PRINS083I The password will be stored in the file file.

Explanation: The password will be stored in a file that only youcan access.




PRINS084I In ORACLE you can have operating systemauthorized user IDs that do not require passwords.

Explanation: In ORACLE you can setup the environment so thatthe password is not required to access the database.



PRINS086I Press Enter to set the password, or type anynonblank character to exit.

Explanation: In ORACLE you can setup the environment so thatthe password is not required to access the database.

System action: If you press Enter, you can set the password. If youtype a nonblank character, the program stops and control is returnedto the operating system.

User response: Press Enter to set a password. Type a nonblankcharacter to exit the program and define the user ID to beauthenticated by the operating system. In this way, no password isrequired for the user ID to access the database.

PRINS088I This program verifies that your databasemanagement system and database user are setupcorrectly, and creates the Reporter system tables.

Explanation: This message describes what the program prsetupdbis used for.



Version 2.02-186

Rep

orter M

essages

PRINS090I One or more Reporter system tables for prefixalready exist.

Explanation: The Reporter system tables to be created alreadyexist.



PRINS091Q Press Enter to exit, or type any nonblankcharacter to continue by deleting the existingtables.

Explanation: You can exit the program or continue by deleting theReporter system tables. If you continue, any data stored in the tableswill not be saved.

System action: If you press Enter, the program stops and control isreturned to the operating system. If you enter a nonblank character,the processing continues by deleting the existing tables.

User response: Press Enter to exit the program. Type a nonblankcharacter to continue and delete the system tables. Then the tableswill be recreated but the data stored so far will not be saved.

PRINS093I Reporter system tables for prefix will be deleted.

Explanation: All the Reporter system tables with the named prefixwill be deleted.




PRINS094I Deleting Reporter system tables that use prefix astable prefix.

Explanation: All the Reporter system tables with the named prefixare being deleted.



PRINS095E program: The table deletion was not successful.The program ended with the return code rc.

Explanation: The Reporter system tables were not deleted. Thereturn code was rc.


User response: Ensure that you have database administrationauthority and rerun the program.

PRINS096I The Reporter system tables were successfullydeleted.

Explanation: The Reporter system tables were successfully deleted.



Version 2.02-188

Rep

orter M

essages

PRINS097E The creation of the triggers for the Reportersystem tables was not successful. The programended with the return code rc.

Explanation: The program did not create the triggers for theReporter system tables. Some of the triggers may have been created.


User response: Refer to the log file /var/perfrep/prsetupdb.log tohave more information about the error. Before issuing the programprsetupdb, you can delete all tables and triggers by running theprogram prdroptables.

PRINS101I program: You are connected to the database name.

Explanation: You are successfully connected to the nameddatabase.



PRINS102Q Press Enter to continue, or type any nonblankcharacter to display the log file file.

Explanation: All messages are stored in the named file, which youcan always refer to for tracking purposes.

System action: If you press Enter, the program stops and control isreturned to the operating system. If you type a nonblank character,the log file is displayed.

User response: Press Enter to continue. Type a nonblank characterto display the log file.


PRINS103I program: Creating directory as a directory.

Explanation: The named directory is being created.



PRINS104I program: The directory directory already exists.

Explanation: The named directory already exists.



PRINS105I A prefixed ORACLE user name has to be typedlike OPS\\\$PR.

Explanation: If you use ORACLE and the user name is prefixed,follow the naming convention shown in the message, where PR is theuser ID.



Version 2.02-190

Rep

orter M

essages

PRREP Report Handling MessagesThis section lists PRREP messages. They appear when you aredisplaying reports from the command line or in batch.

PRREP001E You cannot connect to the database: Databasemessage: message General code: code, DBMS code:code

Explanation: The program did not connect to the database.

System action: Application dependent. The program stops or thecurrent operation is not performed but processing continues.

User response: Ensure that the parameter Table Prefix in theparameter file is set correctly, your database is configured correctly,and the database server is running.

PRREP002E You cannot disconnect from the database:Database message: message General code: code,DBMS code: code

Explanation: The program did not disconnect from the database.


User response: If the problem persists, contact your IBM/Tivolirepresentative.


PRREP003E You cannot use the database: DBMS message:message General code: code, Native code: codeSQL statement: statement

Explanation: The program did not execute a database operation.


User response: Ensure that the database is configured correctly. Ifthis message is displayed while generating a report, ensure that thequery file for that report is correct.

PRREP005E The report definition definition is not found.

Explanation: A report definition is not found.


User response: Use SMIT or the command prreplist to list thereport definitions that are available. Add any report definition that ismissing. For predefined reports, verify that the component to whichthe report definition belongs is installed.

PRREP006E A report definition with the name name alreadyexists.

Explanation: You used a name that is not unique.


User response: Specify a unique name and try again.

Version 2.02-192

Rep

orter M

essages

PRREP007E The report group group is not found.

Explanation: A report group is not found.


User response: Use SMIT or the command prrglist to list thereport groups that are available. Add any report group that is missing.For predefined report groups, ensure that the component to which thereport group belongs is installed.

PRREP008E A report group with the name name alreadyexists.

Explanation: You used a name that is not unique.


User response: Specify a unique name and try again.

PRREP009E The report group group cannot be deletedbecause it contains the following report definitions:definitions.

Explanation: The report group is not removed.


User response: Remove the report definitions that refer to the groupand try again.


PRREP010Q The report group group contains reportdefinitions. Do you want to delete the group andall its report definitions?

Explanation: You have to confirm whether you want to remove thenamed report group.


User response: Select Yes to delete the report group and its reportdefinitions, otherwise select No.

PRREP011E Do not specify more than n characters for thevalue value for the column column.

Explanation: You specified a value too long to be stored in thedatabase.

System action: The value is not stored. Processing continuesnormally.

User response: Enter a valid value and try again.

PRREP012E Do not specify more than n characters for thevalue value.

Explanation: You specified a value too long to be stored in thedatabase.


User response: Specify a valid value and try again.

Version 2.02-194

Rep

orter M

essages

PRREP013E The character character is not allowed in thevalue value for the column column.

Explanation: You specified a value containing one or more invalidcharacters.



PRREP014E The value value contains the invalid charactercharacter.

Explanation: You specified a value containing one or more invalidcharacters.



PRREP015Q Do you want to remove the following reportgroups: groups?

Explanation: You have to confirm whether you want to remove thenamed report groups.


User response: Select Yes to remove the report groups, otherwiseselect No.


PRREP016Q Do you want to modify the following reportgroups: groups?

Explanation: You have to confirm whether you want to modify thenamed report groups.


User response: Select Yes to modify the report groups, otherwiseselect No.

PRREP017Q Do you want to remove the following reportdefinitions: definitions ?

Explanation: You have to confirm whether you want to remove thenamed report definitions.


User response: To remove the report definitions select Yes,otherwise select No.

PRREP018Q Do you want to modify the following reportdefinitions: definitions?

Explanation: You have to confirm whether you want to modify thenamed report definitions.


User response: To modify the report definitions select Yes,otherwise select No.

Version 2.02-196

Rep

orter M

essages

PRREP019W No report groups matching the searchingcriteria groups are found.

Explanation: The program did not find any report groups that youwere searching for.



PRREP020W No report groups are found.

Explanation: The command prrglist did not list any report groups.



PRREP021W No report definitions matching the searchingcriteria reports are found.

Explanation: The program did not find any report definitions thatyou were searching for.




PRREP022W No report definitions are found.

Explanation: The command prreplist did not list any reportdefinitions.



PRREP023I The report group group is added.

Explanation: The named report group was added.



PRREP024I The report group group is modified.

Explanation: The named report group was modified.



PRREP025I The report group group is removed.

Explanation: The named report group was removed.



Version 2.02-198

Rep

orter M

essages

PRREP026I The report definition definition is added.

Explanation: The named report definition was added.



PRREP027I The report definition definition is modified.

Explanation: The named report definition was modified.



PRREP028I The report definition definition is removed.

Explanation: The named report definition was removed.




ZCCAFC Common MessagesThis section lists ZCCAFC messages. They are common messagesshared by different programs.

ZCCAFC001E Specify a nonblank value for the argumentargument.

Explanation: The named argument requires a nonblank value.


User response: Specify a nonblank value and try again.

ZCCAFC002E The argument argument contains a charactercharacter.

Explanation: The argument contains the named character, which isnot valid.



ZCCAFC003I name version.release.modlevel

Explanation: This message is displayed to show the program name,version, release, and modification level.



Version 2.02-200

Rep

orter M

essages

ZCCDBC Database Interface MessagesThis section lists ZCCDBC messages. They appear when you areusing the database interface.

ZCCDBC000I Usage:

Explanation: This message is followed by the correct syntax of acommand.



ZCCDBC001I n rows are retrieved.

Explanation: The program processed a SELECT statement andreturned n rows from the database table.



ZCCDBC002I n rows are affected.

Explanation: The program processed a DELETE, INSERT, orUPDATE statement and n rows were deleted, inserted, or updated inthe database table.




ZCCDBC003I The command ran successfully.

Explanation: The program processed an SQL statement other thanSELECT, INSERT, UPDATE, and DELETE.



ZCCDBC004W The formatting flags (-a,-b,-j,-l,-o,-w,-z) willnot be used.

Explanation: You specified one or more of the flags used foroutput formatting. Those flags are meaningful only when processing aSELECT statement. The flags are ignored.



ZCCDBC005E message

Explanation: This message is from the database managementsystem. For an explanation, refer to your database documentation.


User response: For further action refer to the databasedocumentation.

ZCCDBC006E The first flag for the command must be-d,-i,-s,-u, or -r.

Explanation: One of the following flags is to be specified first:

Version 2.02-202

Rep

orter M

essages

-d for DELETE

-i for INSERT

-s for SELECT

-u for UPDATE

-r for an arbitrary SQL statement


User response: Specify one of the named flags as the first flag andrerun the command.

ZCCDBC007E The name name under which the commandwas issued is not recognized.




ZCCDBC008E The flag -flag is not valid.

Explanation: The named flag is not supported by the command.


User response: Correct the syntax and rerun the command. For adescription of the valid syntax, enter man zccdbcmd or zccdbcmdwithout flags.


ZCCDBC009E Do not specify any argument for the flag -flag.

Explanation: The named flag is to be specified without arguments.



ZCCDBC010E Specify the flag -flag.

Explanation: The named flag is required together with the otherflags you specified.



ZCCDBC011E Specify either the flag -flag1 or -flag2.

Explanation: Only one of the named flags can be specified at atime.



Version 2.02-204

Rep

orter M

essages

ZCCDBC012E Specify an argument for the flag -flag.

Explanation: The named flag requires an argument.



ZCCDBC013E Specify only one argument for the flag -flag.

Explanation: For the named flag you cannot specify more than oneargument.



ZCCDBC014E The number of columns specified for the flag-c and the number of values specified for the flag-v must be equal.

Explanation: The flag -c specifies the table columns and the flag -vspecifies the values for those columns. The number of columns andvalues must match.


User response: Specify matching values for the named flags andrerun the command.


ZCCDBC015E The argument argument for the flag -flag isincorrect.

Explanation: You specified an incorrect argument for the namedflag.



ZCCDBC016E Specify a flag after the character character.

Explanation: The flag prefix (-) requires a flag.



ZCCDBC017E The command syntax is incorrect.

Explanation: You specified a command with an incorrect syntax.



Version 2.02-206

Rep

orter M

essages

ZCCDBC019E Specify a column number between 1 and n forthe flag -flag.

Explanation: The argument must be a number in the indicatedrange.



ZCCDBC020E The justification value for the flag -flag isincorrect.

Explanation: The value specified for the justification is incorrect.


User response: Correct the syntax and rerun the command. For adescription of valid syntax, enter man zccdbcmd or zccdbcmdwithout flags.

ZCCDBC021E The width value for the flag -flag is incorrect.

Explanation: The value specified for the width is incorrect.




ZCCDBC022E The width value for the flag -flag is incorrectfor column n. It must be a positive integer.

Explanation: The value specified for the width is incorrect.



ZCCDBC023E The title value for the flag -flag is incorrect.

Explanation: The value specified for the title is incorrect.



ZCCDBC024E The SQL statement is incorrect or missing.

Explanation: The SQL statement is incorrect or was not specified.


User response: Correct the SQL statement and rerun the command.

Version 2.02-208

Rep

orter M

essages

ZCCDBC026E Specify the flag -flag only once.

Explanation: The named flag can be specified only once.



ZCCDBC027E The argument argument for the flag -flag isincorrect. It must be a positive integer.

Explanation: You specified an incorrect argument for the namedflag.



ZCCDBC028E The format value for the flag -flag is incorrect.

Explanation: The value specified for the format is incorrect.




ZCCDBC029E Cannot connect to the database.

Explanation: The system did not connect to the database.


User response: Ensure that the database is running, you haveauthority to connect to the database, and the environment isconfigured correctly (including the environment variables required bythe database).

ZCCDBC030E Enclose macro arguments in parentheses.

Explanation: The list of arguments for a macro must always beenclosed between parentheses, even if that list does not contain anyvalue.



ZCCDBC031E The macro argument is incorrect.

Explanation: You specified an invalid macro argument.



Version 2.02-210

Rep

orter M

essages

ZCCDBC032E Too few macro arguments are specified.

Explanation: One or more arguments for a macro are missing.



ZCCDBC033E Too many macro arguments are specified.

Explanation: You specified too many macro arguments.



ZCCDBC034E An error occurred when processing macros.

Explanation: An internal error occurred when macros whereprocessed.




ZCCDBC035E The third argument for the DTEQ, DTLT,DTGT, DTLE, or DTGE macro is missing orinvalid. It must be D, T, or DT.

Explanation: Each of the macros for datetime comparison (DTEQ,DTLT, DTGT, DTLE, and DTGE) must have three arguments. Thefirst two arguments specify the datetime values that are to becompared (for example two table columns). The third argumentindicates which parts of the first two arguments are to be used in thecomparison. Specifying D means that only the date parts arecompared, T that only the time parts are compared, and DT meansthat both the date and time parts are compared.


User response: Correct the command syntax and rerun thecommand.

ZCCDBC036E The argument specified for the DTLIT2ITmacro is incorrect. The correct syntax is:[YY]YY-MM-DD]HH[:MI[:SS]]]

Explanation: The argument specified for the named macro mustfollow the syntax displayed in the message.


User response: Correct the syntax and rerun the command. For adescription of the valid syntax, enter man zccdbcmd.

Version 2.02-212

Rep

orter M

essages

ZCCDBC037E The argument specified for the NTLIT2ITmacro is incorrect.

Explanation: You specified an incorrect argument for the namedmacro.



ZCCDBC038E The third argument for the DTADD orDTSUB macro is incorrect. Specify D for days.

Explanation: You specified an incorrect argument for the namedmacro, only D is valid.




ZCCPRM Parameter File MessagesThis section lists ZCCPRM messages. They appear when theparameter file is being used.

ZCCPRM001W The environment variable variable is not set.Default values will be used.

Explanation: The program did not find any parameter file to use,because the environment variable ZCCPARM is not set. The programruns using the default values.


User response: To use values different from the defaults, set theenvironment variable ZCCPARM to a parameter file or issue thecommand again specifying -f /etc/perfrep/perfrep.cfg.

ZCCPRM002E The environment variable variable is not set.

Explanation: The program did not find any parameter file to use.


User response: Set the environment variable ZCCPARM to aparameter file, or issue the command again specifying -f/etc/perfrep/perfrep.cfg.

Version 2.02-214

Rep

orter M

essages

ZCCPRM003W Cannot open the parameter file file. Defaultvalues will be used.

Explanation: The parameter file specified by the environmentvariable ZCCPARM cannot be opened. The program runs using thedefault values.


User response: To use values different from the defaults, take oneof the following actions:

■ Ensure that you have read permission to the named file■ Use the default parameter file /etc/perfrep/perfrep.cfg■ Set the environment variable ZCCPARM to a parameter file for

which you have read permission

ZCCPRM004E Cannot open the parameter file file.

Explanation: The named parameter file cannot be opened.






ZCCPRM005W Cannot read any values in the parameter filefile. Default values will be used.

Explanation: The named parameter file is not valid. The parameterfile is empty or the syntax is incorrect The program runs using thedefault value.





ZCCPRM006E Cannot read any values in the parameter filefile.

Explanation: The named parameter file is not valid. The parameterfile is empty or the syntax is incorrect


User response: To use values different from the defaults, set theenvironment variable ZCCPARM to a valid parameter file.

ZCCPRM007W Cannot retrieve a value for the parametersection::parameter. Using default value value.

Explanation: The program did not retrieve any value for the namedparameter in the named section of the parameter file. The programruns using the default value.


Version 2.02-216

Rep

orter M

essages

User response: To use a value different from the default, add theparameter and value in the parameter file. The syntax is parameter =value.

ZCCPRM008E Cannot retrieve a value for the parametersection::parameter.

Explanation: The program did not retrieve any value for the namedparameter in the named section of the parameter file.

System action: Application dependent. The program stops or theoperation is not performed but processing continues normally.

User response: To use a value different form the default, add thevariable and value in the parameter file. The syntax is parameter =value.

ZCCPRM009E The update of the parameter file file was notsuccessful.

Explanation: The program did not update the named parameter file.

System action: Application dependent. The program stops or theoperation is not performed but processing continues.

User response: Ensure that you have write permission to the namedparameter file and the file system is not full.


ZCCPRM010W The backup of the parameter file file to thefile backup file was not successful.

Explanation: The program did not create a backup copy of thenamed parameter file. The parameter file has been updated.


User response: Ensure that you have write permission to the namedparameter file and the file system is not full.

ZCCPRM011E Reached maximum number n of nestedparameter files (include statements).

Explanation: You specified too many nested parameter files or aparameter file nests another file that was previously nested.


User response: Ensure that a circular nesting is not generated.

Version 2.02-218

Rep

orter M

essages

ZCCRSS Communication MessagesThis section lists ZCCRSS messages. They appear duringmanager—agent communication.

ZCCRSS001E Cannot read the local file file.

Explanation: The communication program did not read the namedlocal file. The file transfer is not performed.

System action: Application dependent. The program stops or thecurrent operation is not performed but processing continues normally.

User response: Ensure that the file exists and you have readpermission to it.

ZCCRSS002E An error occurred while reading a file.

Explanation: An internal error occurred during the file transfer. Thefile transfer is not performed.


User response: Ensure that the file system to which the localdirectory belongs is mounted and the local file exists.


ZCCRSS003E Cannot write to the file file on the agent node.

Explanation: The communication program did not write to thenamed remote file. The file transfer is not performed.


User response: Ensure that you have write permission to the remotefile.

ZCCRSS004E The file transfer was not successful. The returncode is rc.



User response: See the error messages written to syslog on theagent node for further action.

ZCCRSS005E Cannot write to the local file file.

Explanation: The communication program did not write to thenamed local file. The file transfer is not performed.


User response: Ensure that you have write permission to the namedfile.

Version 2.02-220

Rep

orter M

essages

ZCCRSS006E An error occurred while writing to a file.



User response: Ensure that the file system to which the localdirectory belongs is mounted and is not full.

ZCCRSS007E Cannot read the file file on the agent node.

Explanation: The communication program did not read the remotefile. The file transfer is not performed.



ZCCRSS008E Error (errno=n). Cannot write to the file file onthe manager node.

Explanation: The communication program did not write to thenamed local file. The file transfer is not performed.


User response: Ensure that you have write permission to the localfile.


ZCCRSS009E Error (errno=n). An error occurred whilewriting to a file.



User response: Ensure that the file system to which the remotedirectory belongs is mounted and is not full.

ZCCRSS010E Error (errno=n). Cannot read the remote filefile.

Explanation: The communication program did not read the remotefile. The file transfer is not performed.



ZCCRSS011E Error (errno=n). An error occurred whilereading a file.



User response: Ensure that the file system to which the remotedirectory belongs is mounted and the remote file exists.

Version 2.02-222

Rep

orter M

essages

ZCCRSS012E Error calling the subroutine subroutine(),errno=n.

Explanation: The named subroutine was not successful. This errormay be caused by trying to start the program rshsrv when it wasalready running.


User response: If the subroutine is bind(), ensure that the programrshsrv is already running. If it is not, contact your IBM/Tivolirepresentative.

ZCCRSS013E The node node is unknown.

Explanation: You specified an unknown node name.


User response: Specify a valid node name or IP address and rerunthe command.

ZCCRSS014E The service name name or the protocol name(tcp) is not specified.

Explanation: The communication programs did not find the servicename or the protocol name.

System action: The daemon rshsrv is not started or the programrshcli stopped.

User response: Add the entry prrsh n/tcp (where n is the portnumber) to the file /etc/services or the NIS database and issue thecommand again.


ZCCRSS015E No node name was specified.


System action: The operation is not performed. Processingcontinues normally.

User response: Try the operation again. If the error persists,contact your IBM/Tivoli representative.

ZCCRSS016E Cannot connect to the node node.

Explanation: The communication program did not connect to thenamed agent node.


User response: Ensure that the port number specified by the servicename in the file /etc/services or the NIS database is the same on boththe manager and agent nodes.

ZCCRSS017E Unsuccessful remote execution in interactivemode (errno=n).

Explanation: An internal error occurred while executing aforeground command.


User response: See the error messages written to syslog for furtheraction.

Version 2.02-224

Rep

orter M

essages

ZCCRSS018E Unsuccessful remote execution in batch mode(errno=n).

Explanation: An internal error occurred while executing abackground command.


User response: See the error messages written to syslog for furtheraction.

ZCCRSS019E Authentication check was not successful.

Explanation: An internal error occurred while a request wasprocessed.


User response: Ensure that the file /.rhosts on the agent nodespecifies the correct trusted hosts.

ZCCRSS020E The system subroutine subroutine() was notsuccessful (errno=n).

Explanation: An internal error occurred in the named subroutine.


User response: See the man page about the subroutine for furtheraction.


ZCCRSS021E Unknown request n.

Explanation: An internal error occurred while a request wasprocessed.



ZCCRSS022E The daemon rshsrv must be run by the userroot.

Explanation: Only the user root can run the named program.



ZCCRSS023E An internal error occurred when initializing thedaemon.

Explanation: The communication program was not initialized.


User response: The system may be overloaded. Ensure that thereare not too many running processes and rerun the command. If theproblem persists, contact your IBM/Tivoli representative.

Version 2.02-226

Rep

orter M

essages

ZCCRSS024E The file descriptor n is not open.

Explanation: The communication program was not initialized.



ZCCRSS025E The flag -h must be specified as the firstparameter.

Explanation: You ran the communication program withoutspecifying the flag -h as the first parameter.


User response: Issue the command again using the correct syntax,as follows: rshcli -h node -s { cmd | file1 file2 | -t file1 file2 }

ZCCRSS026E The command is too long (max length is n).

Explanation: You specified a command that exceeds the maximumlength.




ZCCRSS027E Unexpected argument argument.

Explanation: You ran the communication program specifying aninvalid argument.



ZCCRSS028E Missing argument for the flag -flag.

Explanation: You ran the communication program withoutspecifying an argument for the named flag.



Version 2.02-228

Rep

orter M

essages

ZCCTED Table Editor MessagesThis section lists ZCCTED messages. They appear when you areusing the table editor.

ZCCTED001I Usage: program [X-Windows flags] flagstablename

Explanation: This message is displayed to show the correctcommand syntax. The program accepts the standard X-Windows. Atable name is required.



ZCCTED002E Cannot connect to the database.

Explanation: The system did not connect to the database.


User response: Ensure that the database is running, you haveauthority to connect to the database, and the environment isconfigured correctly (including environment variables required by thedatabase).


ZCCTED003E Cannot display the table table.

Explanation: The table was not retrieved from the database.


User response: Ensure that the table exists in the database and youhave authority to access the database.

Version 2.02-230

Rep

orter M

essages

ZCCUIC Common GUI MessagesThis section lists ZCCUIC messages. They appear when you arerunning window based programs.

ZCCUIC001E There is no help available for the windowwindow.

Explanation: The help for the named window was not found.

System action: No help is displayed. Processing continuesnormally.


ZCCUIC002E No help volume volume was found in any of thefollowing directories: directories

Explanation: The named help volume was not found.

System action: No help is displayed. Processing continuesnormally.

User response: Use SMIT to set the parameter Help Path to thecorrect value.


ZCCUTI Common MessagesThis section lists ZCCUTI messages. They are common messagesshared by different programs.

ZCCUTI001E The subroutine subroutine() was not successful(errno=n).

Explanation: An internal error occurred in the named subroutine.


User response: For further action, see the man page for thesubroutine.

ZCCUTI002E The process ID process ID did not write numberbytes to the pipe pipe (errno=n).

Explanation: An internal error occurred while the system waswriting to the named pipe.


User response: For further action, see the man page for the systemsubroutine write() .

Version 2.02-232

Rep

orter M

essages

ZCCUTI003E The process ID process ID did not read numberbytes from the pipe pipe (errno=n).

Explanation: An internal error occurred while the system wasreading from the named pipe.


User response: For further action, see the man page for the systemsubroutine read().

ZCCUTI004E An unexpected EOF occurred when the processID process ID was reading n bytes from the pipepipe.

Explanation: The named process did not read all the data itrequired from the named pipe.



ZCCUTI005E System resources are not sufficient. Theprogram is being stopped.

Explanation: The system resources are not sufficient and the signalSIGDANGER was sent to all programs that take a lot of memory.




ZCCUTI006E The flag -flag is required.

Explanation: The named flag must be specified.


User response: Specify the required flag and rerun the command.

ZCCUTI007E flag: The flag is ambiguous. Possible matchesare matches.

Explanation: You specified a flag abbreviation that has more thanone match.


User response: Specify a flag abbreviation that has only one match.

ZCCUTI008E flag: Specify the flag -flag only once.

Explanation: The named flag can be specified only once.



Version 2.02-234

Rep

orter M

essages

ZCCUTI009E argument1: Specify the valid argumentargument2 for the flag -flag only once.

Explanation: You specified an argument that must be specified onlyonce.



ZCCUTI010E flag2: The flags -flag1 and -flag2 are mutuallyexclusive.

Explanation: You specified two flags that cannot be used at thesame time.


User response: Specify only one of the named flags and rerun thecommand.

ZCCUTI011E argument: Only the argument argument is validfor the flag -flag.

Explanation: Only the named argument is valid for the named flag.


User response: Specify the correct argument and rerun thecommand.


ZCCUTI012E Specify the argument argument for the flag-flag.

Explanation: You specified the named flag without its requiredargument.



ZCCUTI013E argument1: Specify the argument argument2only once.

Explanation: You specified an argument that can be specified onlyonce.



ZCCUTI014E argument1: The value of the argumentargument2 is invalid.

Explanation: You specified an invalid argument.


User response: Specify a valid argument and rerun the command.

Version 2.02-236

Rep

orter M

essages

ZCCUTI015E Specify the argument argument.

Explanation: The named positional argument is required.


User response: Specify the required argument and rerun thecommand.

ZCCUTI016E The following arguments were not recognized:arguments

Explanation: You specified the named invalid arguments.



ZCCUTI017I Usage: command argument

Explanation: You specified an incorrect syntax of the command.


System action: Correct the syntax and rerun the command.


ZCCUTI018E The file file does not exist.

Explanation: You specified a file that does not exist.


User response: Specify an existing file.

ZCCUTI019E Cannot find the file file in any of the followingdirectories: directories

Explanation: The named file cannot be found.


User response: Specify an existing file.

ZCCUTI020E Cannot read the file file.

Explanation: The program did not read the named file.



Version 2.02-238

Rep

orter M

essages

ZCCUTI021E Cannot read the file file in any of the followingdirectories: directories

Explanation: The program did not read the named file.



ZCCUTI022E Cannot write to the file file.

Explanation: The program did not write to the named file.


User response: Ensure that the file exists and you have writepermission to it.

ZCCUTI023E Cannot write to the file file in any of thefollowing directories: directories

Explanation: The program did not write to the named file.


User response: Ensure that the file exists and you have writepermission to it.


ZCCUTI024E Cannot execute the program program.

Explanation: One of the exec routines did not execute the namedprogram.


User response: Ensure that the named program exists and isexecutable.

ZCCUTI025E Cannot find the program program in any of thefollowing directories: directories

Explanation: One of the exec routines did not execute the namedprogram.



ZCCUTI026E Cannot access the file file in mode n.

Explanation: The named file cannot be accessed in the specifiedmode. For further information, see the file /usr/include/sys/access.h.


User response: Ensure that the named file can be accessed in therequested mode.

Version 2.02-240

Rep

orter M

essages

ZCCUTI027E Cannot access the file file in mode n in any ofthe following directories: directories

Explanation: The named file cannot be accessed in the specifiedmode. For further information, see the file /usr/include/sys/access.h.


User response: Ensure that the named file can be accessed in therequested mode.

ZCCUTI028E Cannot open the file file in mode n.

Explanation: The named file cannot be opened in the specifiedmode.


User response: Ensure that the named file can be accessed in therequested mode. For further information, see the file/usr/include/sys/access.h.

ZCCUTI029E Cannot open the file file in mode n in any of thefollowing directories: directories

Explanation: The named file cannot be opened in the specifiedmode.


User response: Ensure that the named file can be accessed in therequested mode. For further information, see the file/usr/include/sys/access.h.


ZCCUTI030E Additional memory cannot be allocated.Stopping program with core dump.




ZCCUTI031E The node node is unknown.

Explanation: The system did not retrieve information about thenamed node.


User response: Specify an existing node and try again.

ZCCUTI032E The service service/protocol is not specified.

Explanation: The named service was not found in the file/etc/services or the NIS database.

System action: The server is not started or the client does notconnect to the server.

User response: Add the named service to the file /etc/services or tothe NIS database.

Version 2.02-242

Rep

orter M

essages

ZCCUTI033E The socket was not created (errno=n).

Explanation: An internal error occurred while the system wascreating a socket.


User response: For further action, check the error number in theman page for the system subroutine socket().

ZCCUTI034E The system subroutine bind() was not successful(errno=n).

Explanation: An internal error occurred while the system wassetting the named option for the socket.


User response: For further action, check the error number in theman page for the system subroutine bind().

ZCCUTI035E The system did not set the optionSO_REUSEADDR for socket (errno=n).

Explanation: An internal error occurred while the system wassetting the named option.


User response: For further action, check the error number in theman page for the system subroutine setsockopt().


ZCCUTI036E The system subroutine listen() was notsuccessful (errno=n).

Explanation: An internal error occurred while the system wasexecuting the named subroutine.


User response: For further action, check the error number in theman page for the system subroutine listen().

ZCCUTI037E Cannot connect to the port port on the nodenode (errno=n).

Explanation: An internal error occurred while the system wasconnecting to the named node.


User response: For further action, check the error number in theman page for the system subroutine connect().

ZCCUTI038E The system subroutine select() was notsuccessful (errno=n).

Explanation: An internal error occurred while the system waschecking the status of multiple file descriptors.


User response: For further action, check the error number in theman page for the system subroutine select().

Version 2.02-244

Rep

orter M

essages

ZCCUTI039E The system subroutine fork() was not successful(errno=n).

Explanation: An internal error occurred while the system wascreating a new process.


User response: For further action, check the error number in theman page for the system subroutine fork() .

ZCCUTI040E The system subroutine pipe() was not successful(errno=n).

Explanation: An internal error occurred while the system wascreating an interprocess channel.


User response: For further action, check the error number in theman page for the system subroutine pipe().

ZCCUTI041E The system subroutine waitpid() was notsuccessful for the child process ID process ID(errno=n).

Explanation: An internal error occurred while the system waswaiting for a child process to stop.


User response: For further action, check the error number in theman page for the system subroutine wait().


ZCCUTI042E The system did not read number bytes from thefile descriptor fd (errno=n).

Explanation: An internal error occurred while the system wasreading from an interprocess channel or a socket.


User response: For further action, check the error number in theman page for the system subroutine read().

ZCCUTI043E The system did not write number bytes to thefile descriptor fd (errno=n).

Explanation: An internal error occurred while the system waswriting to an interprocess channel or a socket.


User response: For further action, check the error number in theman page for the system subroutine write() .

ZCCUTI044E The system subroutine accept() was notsuccessful (errno=n) for the socket socket.

Explanation: An internal error occurred while the system waswaiting for a client to connect to the named socket.


User response: For further action, check the error number in theman page for the system subroutine accept().

Version 2.02-246

Rep

orter M

essages

ZCCUTI045E The system cannot send the signal signal to theprocess ID process ID (errno=n).

Explanation: An internal error occurred while the system wassending the named signal to the named child socket.


User response: For further action, check the error number in theman page for the system subroutine kill() .

ZCCUTI046E The system cannot send a packet of numberbytes via the udp socket socket (errno=n).

Explanation: An internal error occurred while the system wassending a packet.


User response: For further action, check the error number in theman page for the system subroutine sendto().

ZCCUTI047E The system cannot receive a packet of numberbytes via the udp socket socket (errno=n).

Explanation: An internal error occurred while the system wasreceiving a packet.


User response: For further action, check the error number in theman page for the system subroutine recvfrom().


ZCCUTI048E Cannot start the program program.

Explanation: One of the exec routines did not start the namedprogram.



Version 2.02-248

Bibliography

This bibliography lists all publications mentioned in this book as well asother relevant publications.

AIX BooksAIX Version 4.1 Commands Reference (all volumes), SBOF-1851

AIX Version 4.1 Communications Programming Concepts, SC23-2610

AIX Version 4.1 Files Reference, SC23-2512

AIX Versions 3.2 and 4.1 Performance Tuning Guide, SC23-2365

AIX Version 4.1 Quick Reference, SC23-2529

AIX Version 4.1 System Management Guide: Communications andNetworks, SC23-2526

AIX Version 4.1 System Management Guide: Operating System andDevices, SC23-2525

AIX Version 4.1 System User’s Guide: Communications and Networks,SC23-2545

AIX Version 4.1 System User’s Guide: Operating System and Devices,SC23-2544

AIX Documentation Overview, SC23-2456

AIX Hypertext Information Base Library, SC23-2163

AIX Planning for Your System Installation, GC23-2407

AIX Quick Reference, SC23-2401

AIX System Overview, GC23-2406

TME 10 Reporter: Messages Guide Bib-1

Bibliography

AIXwindows Environment/6000 Version 1.2 AIXwindows andAIXwindows Desktop User’s Guide, GC23-2432

AIX Version 3 Commands Reference, GBOF-1802

AIX Version 3 Communication Concepts and Procedures, GBOF-1524

AIX Version 3 Editing Concepts and Procedures, GC23-2212

AIX Version 3 Files Reference, GC23-2200

AIX Version 3 System Management Guide, SC23-2457

AIX Version 3 System User’s Guide, GC23-2377

AIX Version 3 Text Formatting Reference, SC23-2453

AIX Version 3 Topic Index and Glossary, GC23-2201

AIX Version 3.2 Performance Monitoring and Tuning Guide, SC23-2365

DB2 for AIX BooksDB2 for AIX 2.1, Administration Guide, S20H-4580

DB2 for AIX 2.1, Command Reference, S20H-4645

DB2 for AIX 2.1, SQL Reference, S20H-4665

DATABASE 2 AIX/6000, Administration Guide, SC09-1571

DATABASE 2 AIX/6000, Command Reference, SC09-1575

DATABASE 2 AIX/6000, SQL Reference, SC09-1574

ORACLE BooksORACLE7 for AIX-Based Systems Installation & Configuration Guide,Part No. A11366-2

ORACLE7 Server Administrator’s Guide and Reference, Part No.6694-70

ORACLE7 Server SQL Language Reference Manual, Part No. 778-70

SQL*Plus User’s Guide and Reference, Part No. 5142-31-1192

Version 2.0Bib-2

Bibliography

NetView for AIX BooksNetView (4.1) for AIX Programmer’s Guide, SC31-8164

NetView (4.1) for AIX Programmer’s Reference, SC31-8165

NetView for AIX Programmer’s Guide, SC31-6238

NetView for AIX Programmer’s Reference, SC31-6239

SYBASE BooksSYBASE SQL Server Reference Manual, 32401-01-1000

SYBASE SQL Server System Administration Guide, 32500-01-1000

SYBASE SQL Server Transact-SQL User’s Guide, 32300-01-1000

Systems Monitor for AIX BooksSystems Monitor (2.2) for AIX User’s Guide, SC31-8173

Systems Monitor for AIX User’s Guide, SC31-7150

Systems Monitor for HP-UX User’s Guide, SC31-7146

Systems Monitor for Sun Solaris User’s Guide, SC31-7148

XRT/graph BooksXRT/graph for Motif, Widget Programmer’s Guide and ReferenceManual, Version 2.3

TME 10 Reporter: Messages Guide Bib-3

Version 2.0Bib-4

Glossary

This glossary defines TME 10 Reporter terms.

A

administration . A TME 10 Reporter task that includes maintaining thedatabase, updating installation-dependent information, and ensuring theaccuracy of data collected.

agent. In TME 10 Reporter, a set of programs running on a network nodethat gather data about the node and write the data to log files. Agents cangather data by issuing UNIX commands, and by reading files such as UNIXaccounting files and files produced by other programs (such as NetView andSystems Monitor). Agents are controlled by the manager.

C

calendar. The calendar defines day types and divides days into periods. Itis used during collect and reporting.

collect. See log collector.

component. Separately installable definitions that enable TME 10 Reporterto collect and report on data for a particular systems management purpose.

TME 10 Reporter: Messages Guide Gloss-1

D

daemon. A long-running agent program that periodically gathers data byissuing commands. The daemon writes the data to a log file.

database. In TME 10 Reporter, a set of relational database tables thatincludes data tables, lookup tables, and system tables.

data collection. In TME 10 Reporter, a process that consists of two stages.Firstly, the transfer of log files from one or more nodes containing an agentto the node containing the manager. Secondly, the running of the logcollector (see log collector).

data table. In TME 10 Reporter, a table in the database that contains datasummarized from log files. Data may be summarized, for example, by hour,day, or month. The data is used to create reports.

G

gather. A process performed by agents in which performance data isentered into log files. The log files are located in the same nodes as theagents.

graphical options file. A file that specifies the default display format for agraphical report.

I

input data source. A file from which the agent gathers the data that itwrites to log files.

K

key columns. The columns of a database table that together constitute thekey.

Version 2.0Gloss-2

L

log. The log file type. Examples of logs are conf, perf, and netview. Eachlog can contain certain predefined types of records. Each record has apredefined format and contains specific data.

log collector. A TME 10 Reporter program that processes log files tocreate records in data tables (referred to as collect), and provides otherTME 10 Reporter services.

log collector language. Statements used to supply definitions to and invokeservices of the log collector.

log definition. The description of a log used by the log collector.

log file. Any file that contains data in a predefined format that can becollected into data tables by the log collector.

log procedure. A program that is used to process all record types in certainlog files.

lookup expression. An expression that specifies how a value is obtainedfrom a lookup table.

lookup table. A table in the database that contains user-providedinformation that is used for grouping, translation, or substitution duringcollect or reporting.

M

manager. In TME 10 Reporter, a set of programs that are installed on onenode in the network, and which use the services of one or more agents. Itprovides all user interfaces and functions for administration and reporting.

MIB . Management information base.

N

node. In TME 10 Reporter, a workstation within the network on which amanager and/or agent is installed.

node group. A number of nodes that are grouped together according touser-defined criteria.


P

parameter. A named item in the parameter file, with a value associatedwith it.

parameter file. A file that contains values for parameters that controlcertain TME 10 Reporter actions.

primary key . See key columns.

purge condition. The rules that specify which data is deleted from datatables on a regular basis.

Q

query file. A file that contains an SQL SELECT statement, and optionally,additional commands that specify the contents and format of a report.

R

record definition. The description of log file records used by the logcollector, including detailed record format descriptions.

record procedure. A program that is called to process some types of logrecords.

record type. The classification of records in a log file.

report definition . In TME 10 Reporter, the object used to create anddisplay reports. It defines the data to be used in the creation of a report andthe structure and layout of the report.

report group. A collection of TME 10 Reporter reports that can bereferred to by a single name.

retention period. The period of time a TME 10 Reporter data table retainsdata before purging it.

Version 2.0Gloss-4

S

SMIT . Systems Management Interface Tool. A menu system forconfiguring AIX computers. In TME 10 Reporter, SMIT provides a set ofwindows for use by the manager.

SNMP. Simple Network Management Protocol. A protocol running abovethe User Datagram Protocol (UDP) used to exchange network managementinformation.

source. In an update definition, the record or table that contains the dataused to update a data table.

system table. A database table that contains information for controllingTME 10 Reporter functions and operation.

T

table definition. The description of a table used to create the table in thedatabase.

target. In an update definition, the data table in which TME 10 Reporterstores data from the source record or table.

U

update definition. Instructions for entering data into a database table froma record or from another database table. Used by the log collector.

user-supplied information. All of the information that is added to the logfile data to create reports. This information can include data such as calendarinformation, node definitions, and information in lookup tables.

V

view. An alternative representation of data from one or more tables. Aview can include all or some of the columns contained in the table on whichit is defined.


SH19-4233-ð1

Date post:	16-Mar-2018
Category:	Documents
Upload:	vodung
View:	222 times
Download:	0 times