74 Error Messages

74.1 General Error Messages

74.1.1 Internal consistency error: description

  • Explanation

    This message indicates a fatal corruption of user memory.

  • User Action

    Re-installation of this product may correct the problem, if it does not, submit an SPR.

  • 74.1.2 Modifing Class/Subclasses disabled

  • Explanation

    Modifing classes and subclasses is disabled after MERG data is read.

  • User Action

    This is currently a restriction for the capacity planner. Exit the capacity planner, restart and then add the new classes and subclasses (optional) before reading MERG data.

  • 74.1.3 Error opening file name

  • Explanation

    The specified file could not be opened.

  • User Action

    Ensure that the file exists and that the protections are properly set.

  • 74.1.4 Error reading filename

  • Explanation

    Error reading from filename

  • User Action

    Check the file protections for the file and the file access for the directory.

  • 74.1.5 Error writing filename

  • Explanation

    Error writing to filename

  • User Action

    Check the file protections for the file and the file access for the directory.

  • 74.1.6 No context sensitive help available for this component

  • Explanation

    Context sensitive help for this area of the screen does not exist.

  • User Action

    Select another area on the window.

  • 74.1.7 Cannot find label name

  • Explanation

    The capacity planner's message system depends on labels to find the appropriate message in the bookreader file. This message occurs when a label can not be found in the ECP_LABELS.MSG file.

  • User Action

    Submit an SPR.

  • 74.1.8 Cannot allocate n bytes

  • Explanation

    This is a FATAL error indicating memory could not be allocated.

  • User Action

    On OpenVMS systems, increase the PGFLQUO limit for the current user process. If the problem persists, submit an SPR.

    On Digital UNIX systems, submit a SPR.

  • 74.1.9 Cannot re-allocate n bytes

  • Explanation

    This is a FATAL error indicating memory could not be re- allocated.

  • User Action

    On OpenVMS systems, increase the PGFLQUO limit for the current user process. If the problem persists, submit an SPR.

    On Digital UNIX systems, submit a SPR.

  • 74.2 Data Collector Interface Error Messages

    74.2.1 Data collection has been submitted

  • Explanation

    The event trace data collection job has been submitted to a batch queue.

  • User Action

    None.

  • 74.2.2 Submit data collection to batch for node nodename

  • Explanation

    The event trace data collection job has been submitted to a batch queue for the specified node.

  • User Action

    None.

  • 74.2.3 Data Collector is not installed

  • Explanation

    The data collector was not found on the system.

  • User Action

    Install Event Monitor Data collector. Refer to the PerfCap Performance Data Collector Installation Guide Version 2.0 for OpenVMS VAX. Refer to the PerfCap Capacity Planner Installation Guide Version 2.0 for OpenVMS AXP.

  • 74.3 Data Integrator Error Messages

    74.3.1 Data Integrator is not installed

  • Explanation

    The Data Integrator is not installed.

  • User Action

    Install the Data Integrator component of the capacity planner. See the PerfCap Capacity Planner Installation Guide for OpenVMS or UNIX systems for details.

  • 74.3.2 Reset Data Integrator options to defaults

  • Explanation

    The data integrator options across all nodes have been reset to the default options, which are displayed on the Main Data Integrator window.

  • User Action

    None

  • 74.3.3 Invalid time range

  • Explanation

    The end time is earlier than the begin time.

  • User Action

    Change the selected times so that the end time is later than the begin time.

  • 74.3.4 No data found in specified time interval

  • Explanation

    No data was found in the specified interval.

  • User Action

    Make sure that the PSDC$DATABASE logical is defined to the directory where .CPD files reside.

  • 74.4 Workload Analyzer Messages

    74.4.1 Enter the class or subclass name

  • Explanation

    This option requires that a name be specified.

  • User Action

    Enter a name in the Current Class or the Current Subclass field before selecting either the Define or Delete options.

  • 74.4.2 No nodes defined

  • Explanation

    This operation requires that at least one node be defined.

  • User Action

    Read in MERG data file or interactivly define a node.

  • 74.4.3 Node name not found

  • Explanation

    User specifed node was not found in list of known nodes.

  • User Action

    Check correctness of nodename.

  • 74.4.4 name already exists

  • Explanation

    The user specifed device was found in list of known devices.

    Newly added devices must have unique names.

  • User Action

    Enter a unique name.

  • 74.4.5 Object name already exists

  • Explanation

    An object (such as a class, subclass, or node) with the specified name already exists. Newly added objects require unique names.

  • User Action

    Enter a unique name.

  • 74.4.6 Service time can not be less than the minumum for the disk

  • Explanation

    Service time can not be less than the average rotational latency time.

  • User Action

    Increase value of disk service time.

  • 74.4.7 variable name must be type

  • Explanation

    Illegal value for customization variable.

  • User Action

    Change the entered type (integer, string, or float) for variable.

  • 74.4.8 Invalid number found in database database file

  • Explanation

    The specifed database file has been incorrectly edited or has been corrupted.

  • User Action

    See the PerfCap Capacity Planner Reference Guide for the correct format of the .DBA file or re-install the product to restore the .DBA default values.

  • 74.4.9 device type tag not found in database database

  • Explanation

    The device was not found in the database. It is possible that the device is new and was not included in the database file.

  • User Action

    Edit the database file to include the new device. See the PerfCap Capacity Planner Reference Guide for the correct format of the .DBA file.

  • 74.4.10 Duplicate name name found in database database

  • Explanation

    The specified database file has been incorrectly edited or has been corrupted.

  • User Action

    The specified .DBA file must be edited to restored to a valid format. See the PerfCap Capacity Planner Reference Guide for the correct format of the .DBA file.

  • 74.4.11 Tag must be defined first in database name

  • Explanation

    The specifed database file has been incorrectly edited or has been corrupted.

  • User Action

    The specified .DBA file must be edited to restored to a valid format. See the PerfCap Capacity Planner Reference Guide for the correct format of the .DBA file.

  • 74.4.12 Default adapter type not found

  • Explanation

    Default adapter type not found in the CPU database.

  • User Action

    See the PerfCap Capacity Planner Reference Guide for the correct format of the .DBA file.

  • 74.4.13 Class name is unknown

  • Explanation

    The class name tag in the .CLAS file has no corresponding class definition.

  • User Action

    If the class definitions have been modifed since the last session, the restore option is no longer valid. Re-read each MERG file.

  • 74.4.14 Cannot expand number of classes

  • Explanation

    The number of classes in the .CLAS file does not match the current number of defined classes.

  • User Action

    Read MERG data using the Read Data option from the Workload Analysis window.

  • 74.4.15 Illegal variable in .CLAS file

  • Explanation

    Unexpected string in .CLAS file

  • User Action

    Read MERG data using the Read Data option from the Workload Analysis window.

  • 74.4.16 User number n is out of range

  • Explanation

    The user number in the .CLAS file is greater then the number of users found in the MERG file.

  • User Action

    Read MERG data using the Read Data option from the Workload Analysis window.

  • 74.4.17 MERG file is undefined

  • Explanation

    The MERG file name is missing from .CLAS file.

  • User Action

    Read MERG data using the Read Data option from Workload Analysis window.

  • 74.4.18 User number already assigned to class name

  • Explanation

    The user has already been assigned to a different class.

  • User Action

    To change class assignment of a user, use the Edit Process Classify spreadsheet.

  • 74.4.19 Unknown CPU type

  • Explanation

    Unknown CPU type value.

  • User Action

    Enter a correct CPU type value.

    See CPU Types

  • 74.4.20 Unknown Brouter type

  • Explanation

    Unknown Brouter device type.

  • User Action

    Enter valid Brouter type. See B/Router Types

  • 74.4.21 Unknown Bus type

  • Explanation

    Unknown bus type

  • User Action

    Enter a correct bus type value.

    See Bus Types

  • 74.4.22 Unknown CI Adapter

  • Explanation

    Unknown CI adapter type

  • User Action

    Enter a correct CI adapter type value.

    See CI adapter Types

  • 74.4.23 Unknown NI Adapter

  • Explanation

    Unknown NI adapter type.

  • User Action

    Enter a correct NI adapter type value.

    See NI Adapter Types

  • 74.4.24 Unknown FDDI Adapter

  • Explanation

    Unknown FDDI adapter type

  • User Action

    Enter a correct FDDI adapter type value.

    See FDDI Adapter Types

  • 74.4.25 Unknown SCSI Adapter

  • Explanation

    Unknown SCSI adapter type

  • User Action

    Enter a correct SCSI adapter type value.

    See SCSI Adapter Types

  • 74.4.26 Unknown DSSI Adapter

  • Explanation

    Unknown DSSI adapter type.

  • User Action

    Enter a correct DSSI adapter type value.

    See DSSI Adapter Types

  • 74.4.27 Unknown token ring

  • Explanation

    Unknown token ring type.

  • User Action

    Enter a correct token ring type value.

    See Token Ring Types

  • 74.4.28 Unknown disk type

  • Explanation

    Unknown disk type

  • User Action

    Enter a correct disk type value.

    See Disk Types

  • 74.4.29 Unknown disk server

  • Explanation

    Unknown disk server type

  • User Action

    Enter a correct disk server type value.

    See Disk Server Types

  • 74.4.30 Unknown operating system

  • Explanation

    Unknown operating system

    Valid operating systems are

    VMS

    AXPVMS

    AXPOSF

  • 74.4.31 Invalid MERG data version, MERG Version V5.1 expected

  • Explanation

    The version of the MERG file must be V5.1

  • User Action

    Make sure that the specified file is a MERG file produced by the Data Integrator.

  • 74.4.32 Invalid ALPHA migration name

  • Explanation

    Alpha migration valid names are defined in ECP_LIBRARY:ECP_ AXP_APPL.DBA

  • User Action

    Enter a known migration name.

  • 74.4.33 No software servers have been defined

  • Explanation

    This attempted action requires that software servers be defined.

  • User Action

    Define software server classes prior to reading MERG data.

  • 74.4.34 Node name has already been read

  • Explanation

    The Restore option will attempt to read all data files that were present for the last session. This message indicates one of the data sets was already read and has not been re-read.

  • User Action

    None

  • 74.4.35 No classes defined

  • Explanation

    Classes must be defined prior to importing MERG data or sizing new nodes.

  • User Action

    Use the Define Data option from the Workload Analysis window to create classes.

  • 74.4.36 No subclasses defined

  • Explanation

    The specifed action requires that subclasses be defined.

  • User Action

    Define subclasses prior to reading data.

  • 74.4.37 No data has been read

  • Explanation

    No performance data has been read by the Capacity Planner.

  • User Action

    Read a MERG data file or a BASE model data file.

  • 74.4.38 Invalid UIC format

  • Explanation

    The specified string was not in the correct format of a UIC. UICs must be of the form [n,n].

    Wildcards are valid. For example [10,*] or [20,1]

  • User Action

    Enter the required format for the UIC.

  • 74.4.39 No disks found

  • Explanation

    No disks were specified

  • User Action

    Specify disks.

  • 74.4.40 No base model

  • Explanation

    A base model must be built prior to this step.

  • User Action

    Select the Build Model button from the Workload Analysis window.

  • 74.4.41 Base model has already been built

  • Explanation

    A base model has already been built.

  • User Action

    None.

  • 74.4.42 No MERG file has been read

  • Explanation

    A MERG data file must be read prior to this step. The reduced data is typically a .MERG file, which is output from the Data Integrator component.

  • User Action

    Read the MERG data only after you create class definitions. To read a reduced data file, use the Read Data option from the Workload Analysis window.

  • 74.4.43 Defining subclasses has been disabled

  • Explanation

    Defining additional subclasses is disabled after an reduced data has been read.

  • User Action

    Exit the Capacity Planner, restart the application, and add the new subclasses before reading in MERG data.

  • 74.4.44 No Image data in the reduced file

  • Explanation

    When subclasses are defined, the reduced data file must have been produced with the /BY_IMAGE qualifier from the Data Integrator. From the DECwindows interface, use the By Process, By Image selection from the Processing Options section of Data Integration window.

  • User Action

    Rerun the Data Integrator and reduce the files using the optons to include image data required for subclass classification (OpenVMS only).

  • 74.4.45 Cannot find class class name

  • Explanation

  • User Action

  • 74.4.46 Cannot find subclass subclass name

  • Explanation

  • User Action

  • 74.4.47 Cannot find software server name

  • Explanation

  • User Action

  • 74.4.48 Cannot find disk name

  • Explanation

  • User Action

  • 74.4.49 Cannot find node name

  • Explanation

  • User Action

  • 74.4.50 No node has been selected

  • Explanation

    This option requires that a node be specified.

  • User Action

    Enter a nodename.

  • 74.4.51 Error adding object : name

  • Explanation

    This message indicates a failure to add a object such as a class, subclass, Adapter. This message may occur when restoring a .BASE file.

  • User Action Submit an SPR.
  • 74.4.52 Measurement period less then 15 minutes

  • Explanation

    The data measurement period in the reduced data file contains performance data for less then 15 minutes. It is possible that this is not enough data to to produce a valid base model.

  • User Action

    None.

  • 74.5 Configuration Error Messages

    74.5.1 Invalid bridge connection

  • Explanation

  • User Action

  • 74.5.2 Network data has alreay been read

  • Explanation

  • User Action

  • 74.5.3 Merging with Base model not supported

  • Explanation

    Currently the capacity planner restricts the number of .BASE file imports to one.

  • User Action

    None.

  • 74.5.4 User profile data not found

  • Explanation

    After a model is built, user profile data is no longer available. Also, user profile data is not available for nodes that are interactively added through the Draw Configuration option or for nodes whose data was read through the base file.

  • User Action

    None.

  • 74.5.5 Unsupported interconnection configuration

  • Explanation

  • User Action

  • 74.5.6 object type object name is deleted from the configuration.

  • Explanation

    This message indicates that a device has been deleted.

  • User Action

    None

  • 74.5.7 object type object name is added to the configuration.

  • Explanation

    This message indicates that a device has been added to the configuration.

  • 74.5.8 Adapter name is deleted from node nodename.

  • Explanation

  • User Action

  • 74.5.9 Invalid Zoom: Can only zoom into a Node or HSC.

  • Explanation

    An attempt is being made to zoomin into a object which is neither a HSC nor a node.

  • User Action

    None

  • 74.5.10 Object not added into the configuration

  • Explanation

  • User Action

  • 74.5.11 Cannot delete node nodenamefrom configuration

  • Explanation

  • User Action

  • 74.5.12 Cannot add node to configuration

  • Explanation

  • User Action

  • 74.5.13 Cannot delete bus, there are servers on it

  • Explanation

  • User Action

  • 74.5.14 Can not add scope if system window is there

  • Explanation

    Attempting to add system scope to the main window when the user has already zoomed into a object from the network view.

  • User Action

    Close the system window and try again.

  • 74.5.15 Can not add scope when I/O window is there

  • Explanation

    Attempting to add I/O scope to the system window when the user has already zoomed into a object from the system window.

  • User Action

    Close the I/O window and try again.

  • 74.5.16 Can not add scope if there are more than 5 HSCs"

  • Explanation

    Attempting to add I/O scope to the system window when a node has 5 or more HSC's triggers this.

  • User Action

    Zoominto each HSC and view their details.

  • 74.5.17 Invalid network configuration

  • Explanation

  • User Action

  • 74.5.18 Cannot disconnect name1 from name2. There is load routed through it

  • Explanation

  • User Action

  • 74.5.19 Cannot delete name. There is load routed through it.

  • Explanation

  • User Action

  • 74.5.20 Cannot disconnect object1 from object2. Server server name has load.

  • Explanation

  • User Action

  • 74.5.21 Cannot delete name. It has # users on it.

  • Explanation

  • User Action

  • 74.5.22 object1 and object2 cannot have multiple connections.

  • Explanation

    Attempting to connect two objects that are already connected.

  • User Action

    None

  • 74.5.23 Cannot find connection between object1 and object2

  • Explanation

    Attempting to delete a connection between two objects when they are not already connected.

  • User Action

    None

  • 74.5.24 object1 and object2 cannot be connected

  • Explanation

    A connection between the two selected object types is not possible

  • User Action

    None

  • 74.5.25 Server name cannot be deleted. It has at least one or more disks with load

  • Explanation

    Attempting to delete a server when there is at least one disk with workload connected to this server.

  • User Action

    Use the Disk load Balancing spread sheet to move all workload from disks under this server to disks under a different server.

  • 74.5.26 Disk name cannot be deleted. It has load from node nodename

  • Explanation

  • User Action

  • 74.5.27 Disk name cannot be deleted

  • Explanation

    The operation is invalid if the disk has workload.

  • User Action

    Use the Disk Load Balancing spreadsheet to move all the workload from the selected disk to another disk first.

  • 74.5.28 Disk name has workload

  • Explanation

    The last member can not removed from the diskset if the disk has load.

  • User Action

    Use the Disk Load balancing spread sheet to move all workload from the current disk to another disk first.

  • 74.5.29 Disk name is not a master volume

  • Explanation

    The opearation is valid only for a diskset master volume.

  • User Action

    Select a master volume or convert the selected disk to a master volume.

  • 74.5.30 Disk name and diskname are not of same types

  • Explanation

    All diskset members need to be of the same type.

  • User Action

    Ensure that the disk types for the selected disks are the same by displaying the Device Statistics panel for each device.

  • 74.5.31 Can only change diskset type of master volume

  • Explanation

    This operation is valid only for diskset master volumes.

  • User Action

    To convert the current disk into a diskset, use the Create New Diskset option from the Disk editing pop-up menu displayed only from an I/O window.

  • 74.5.32 Invalid diskset type

  • Explanation

  • User Action

    Select one of

    NONE

    CBVS

    HBVS

    STRIPE

  • 74.5.33 Cannot change diskset type of master to NONE

  • Explanation

    Changing diskset type from master to none is not allowed when there are member disks present.

  • User Action

    Use the Remove Members from Diskset option from the Disk editing pop-up menu first.

  • 74.6 Model Messages

    74.6.1 Non-Interactive load saturates system. Model Running...

  • Explanation

    Non-interactive classes saturates the system.

  • User Action

    Reduce the workload on one or more non-interactive classes and rerun the model.

  • 74.6.2 Convergence Problem: TREAT RESULTS WITH CAUTION

  • Explanation

    The analytical model iterations are not converging. Possible reasons include:

  • To many classes

  • The workload is already saturated or is to close to saturation levels

  • Incorrect client/server relationships definition
  • User Action

    Check client/server relationship definitions, if any. Reduce workload on most utilized classes and rerun model.

  • 74.6.3 Run Analytical or Saturation Model first

  • Explanation

    Model must be (re)run prior to this step.

  • User Action

    Press the "Performance Prediction or the Saturation Analysis pushbottons in the MODEL window.

  • 74.6.4 Configuration has been edited

  • Explanation

    After the configuration has been edited the model must be re-run before this operation is enabled.

  • User Action

    Press Performance Prediction push button in the MODEL window.

  • 74.6.5 Cannot change from 0 arrival rate

  • Explanation

    You cannot change the arrival rate of the class from 0.0. In order to add workload to this class, either move users from another node or edit class profile spreadsheet to modify class parameteres.

  • User Action

    Use Move Load spreadsheet to move users from another node. or Use edit class profile spreadsheet to enter class parameters.

  • 74.6.6 Unknown .BASE file version

  • Explanation

    The version of the .BASE file must be V1.0

  • User Action

    Make sure that the first line in the specified .BASE file is V1.0


  • Previous Page | Next Page | Table of Contents