Copyright © Cloud Software Group, Inc. All Rights Reserved |
A segment must be online in order to obtain the related DASD statistics.Either bring the segment online or select a segment that is online to review its DASD statistics.You referred to a CA-Datacom field that is not part of the CA-Datacom table on which you are defining the Object Service Broker DAT table.Remove the entry. You can use the FIELDS function to determine valid CA-Datacom fields.DAT table defn must reference CA-Datacom NameYou did specify a CA-Datacom table name for this Object Service Broker DAT table definition.You must specify the CA-Datacom table name; press <PF1> to see a list.DAT tables cannot have PARAMETERS definedYou have requested to specify PARAMETERS for this DAT Table Definition. Parameters are not supported for DAT tables.Data error detected in %. Conversion of % % to % % failedYou tried to do an operation or assignment of incompatible data types. For example, if you typeExample 'A' + 1Example Data error detected in ADDITION. Conversion of VARYING CHARACTER to BINARY failed.Verify that the operands of the expression involved are compatible with the operation performed.Data error detected in conversion of argument # of % routine "%"A routine was called with an argument value that cannot be converted to the syntax of the routine argument.Verify the argument value that you pass to the routine.Data exists in % definition; cannot save as % definitionData has been added to the table definition since the Table Definer was opened but the table type has been changed.Save as a new table definition or exit without saving.Data exists on local node; cannot save as minimal definitionData has been added to the local copy of the table since the Table Definer was opened but you are attempting to save as a minimal definition.Save as a new table definition or exit without saving.ADABAS definition for the specified DBID and File No has been extracted.Data item in expression has an invalid syntax typeInternal error. The message log contains a more detailed error message.
2. Contact TIBCO Support with the log and a description of the actions performed before the message was displayed.DATA must be set to "Y" before using INSTANCE SELECT functionYou have requested to specify which instances of the table to unload; however, the DATA indicator for the table is set to N, indicating that you do not want to unload the data.If you wish to unload the data and specify which instances of data to unload, set DATA to Y, then request INSTANCE SELECT again.DATA OBJECT BROKER BUFFER IS TOO SMALLThe buffer allocated by the Data Object Broker is too small to hold the result data.Data parameter is not allowed for "%" table typeYou have specified a data parameter which is not allowed for the given table type.Remove the data parameter from the table definition.Data parameter must have % attribute set to %The SOURCE, SOURCENAME and DEFAULT attributes apply only to the location parameter. A data parameter must have these attributes assigned NULL values.Specify a null value for the given attribute of the data parameter.Objects that you want to extract and apply to another system must go to an interim data set. The specified data set does not exist.You did not specify the data set for either the control card specification or the selection specification.Data set parameter of VSM table must be syntax %, length <= %A data set parameter of a VSAM table is restricted to the indicated syntax and maximum length.Modify the syntax and length of the parameter accordingly.Data tables LOCKED; displaying UNCHANGED Screen definitionIn the Screen Definer, you requested to DISPLAY the definition. The data store, however, is locked, so the Screen that is displayed is the one that existed when you entered the Screen Definer.No action required. If you want to display the Screen that you modified in the Screen Definer instead of the original one, try again later.Data tables LOCKED; only definition printed (not screen image)You requested to PRINT the screen definition from the Screen Definer, but the data store is locked. The definition that was printed is the screen currently defined in the Screen Definer, but its screen image cannot be printed.No action required. If you want to print the screen image as well, try again later.Database maintenance level unavailableThe database maintenance level is unavailable from the expected table.Dataset "%" for "%" not allocated, dynamic allocation error; RC = %, error = %, info = %The tool ALLOCDSN failed. The dynamic allocation return code, error code, and info code are supplied.To determine the nature of the error, look up the error code in your operating system manual.The argument DSNAME of the ALLOCDSN tool must be the name of an existing sequential data set.Verify the name of the data set or allocate one with that name.The value returned by the indicated tool is too large to be stored in the date variable.If the date variable is defined as binary 2, increase the size to binary 4. Otherwise, contact TIBCO Support.The specified DB2 Creator or table (or both) does not exist in the DB2 database.The indicated creator does not exist in the DB2 database.Enter an existing creator or press <PF4> to select one.The DB2 Gateway was not started or it failed.Verify that the DB2 Gateway and the Data Object Broker are started and available. If this problem persists, contact TIBCO Support.The creator.table was not found in the DB2 catalog. If a LOCAL catalog is being used ensure that it is up to date with the current DB2 catalog.If LOCAL was used refresh @DB2SYSTABLES and @DB2SYSCOLUMNS. If not LOCAL ensure you are pointing to the correct DB2 subsystem.DB2 Table name too long to generate a static SQL handlerThe DB2 table name is too long to fit on a line in the generated static handler module. The maximum length of the table name is 35DB2 Typ "%" is incompatible with metadata Syn "%"The indicated MetaStor syntax is incompatible with the indicated DB2 column type.Change the MetaStor syntax to a compatible type. See the Accessing DB2 Data manual for a list of compatible DB2 and MetaStor data types.You have used <PF3> to save the current DBGCOM. This provides feedback.You have used <PF4> to validate the current DBGCOM. This provides feedback.This DBID and FILENO combination has already been extracted and cannot be re-extracted from this option.Re-extract from the List of extracted definitions option.Values have not been supplied for required fields DBID and FILE NO.DDNAME allocation not allowed for parameterized "%" table "%"The table definition for the parameterized Export/Import table specifies allocation using the DDNAME option. The presence of a DATA parameter and DDNAME allocation are mutually exclusive.Either remove the data parameter and allocate the fully qualified PDS member name on the DD statement or perform allocation using the FILE option.Deallocate failed "%" dataset; module "%"; R15 = %, error = %, info = %Deallocation of sort work file failed. The DDNAME, the module name, the return code, and the dynamic allocation error and info codes are supplied for diagnostic purposes.Call your system administrator to check the return code in Register 15 against the appropriate vendor's manual. Correct the problem as required.You have entered the EXIT primary command, or pressed <PF12>. This provides feedback.For a field with syntax P, the number of decimal places cannot be equal to or larger than twice the length of the IMS field.Change the decimal length to be less than twice the length of the IMS field.Only a MetaStor field with syntax P (packed decimal) can have a decimal value larger than 0.Enter 0 in the decimal field or change the syntax to P.You cannot have decimal places if the data type is Count.You attempted to delete the specified default filters and this was not allowed. Default filters can be used by any user but they should not be deleted.Default filter % may not be modified - change name to saveYou attempted to modify the definition of the specified default filter and this was not allowed. Default filters can be used by anyone but they cannot be modified.You can save the changes to the default filter under a new filter name.Default permissions for created libraries SAVEDYou saved default permissions for created libraries in the Specify Default Permissions function. Once the information in the Specify Default Permissions screen is saved, the library defaults are applied for any libraries subsequently created by the creating member.You saved changes to default permissions for created reports and you are now viewing the Specify Default Permissions screen. Default report permissions are not committed unless the Specify Default Permissions screen is saved.You saved changes to the default screen permissions, and you are viewing the Specify Default Permissions screen. Default screen permissions are committed if the Specify Default Permissions screen is saved, or ignored if the Specify Default Permissions screen is canceled.You saved changes to the default table permissions and you are viewing the Specify Default Permissions screen. If you save the Specify Default Permissions screen, changes to the default table permissions are committed; otherwise, the changes are ignored.Default permissions for objects created by "%" SAVEDYou saved default permissions specifications.Reports with a type of DEFAULT can be used by anybody, but cannot be deleted. If you do not want to see the report in your list, use a selection.Default table % empty; see system administratorThe default table containing the S-type card values is empty.Default table % not found; see system administratorYou are missing a TDS table that contains the default S-type card values.Default value "%" is incompatible with type % syntax % length %The indicated default value for the field is incompatible with its type, syntax and length.Change the default value for the field, or change its type, syntax and length.Defaults not allowed in definition of derived field "%.%"Derived fields may not specify default values.Remove default values for all derived fields in the definition of the subview table.DEFINE can be used only from 1st level of ObjectSet DefinerYou attempted to define an object from the Object Set Definer; however, you are already in the process of defining an object set from the Object Set Definer. You cannot go more than one level from the original object set.Save your changes to the current object set. Enter the Object Set Definer for the object set from the workbench instead of the Object Set Definer.Define input data table before continuingThe application has not received an import table, nor has an input file been defined to it to provide a source of data.Defined table % is missing % entry %; No % loadedThe definition of the target table is incorrect. No occurrences are loaded.Correct the definition of the target table and load the table again.The definer you invoked from the Object Set Definer failed for the reason given.Look up the message given for the failure for more information.Your request to bind the definition and data of the indicated table was successful. The next reference to the table in this session, or the first reference to it in any other session, causes its data and definition to be bound for the duration of that session.Definition and virtual layout for Screen "%" PRINTEDThe definition and layout for the named Screen has been printed at your request.DEFINITION ERROR - report table "%" defined twiceThe same report table name appears more than once in the list of report tables and control breaks for this report.Specify each report table only once within a report definition.An internal error was detected in the table definition.Definition error for report "%": "%" scope report function "%" not supported with specified BY-FIELDsBecause of implementation restrictions, this version of the Report Server cannot compute the report function in question.Contact TIBCO Support for more information.Information of the specified object has been updated.The definition of the indicated object set was printed.You requested Define Screen from the workbench; however, the data store is locked, preventing the retrieval of the definition.You cannot save a report table definition in the Table Definer.Use the Report Painter to save the definition.The specified object type/object has been successfully created.Definition of the indicated object was not found; therefore, it was not unloaded.The definition of a table, screen, or report already exists in the system. LOAD does not overwrite the existing definition.You can delete the existing object and load the new object if you want to replace the object.The definition of the specified object has been saved.Definition of dynamically created table % is unusableThe table definition you supplied to the Dynamic Object Facility contains errors.Review the data you supplied to the Dynamic Objects Facility and correct the errors.Definition of field "%" contains a reference to itselfA derived field was defined which refers to itself in its definition.Definition of parameters for table "%" incorrect, sum of lengths of parameters too largeInternal error. The definition of the table has been altered.
2. Contact TIBCO Support with the log and a description of the actions performed before the message was displayed.Use only the Table Definer to modify table definitions.The definition of the indicated report, together with its corresponding Generator tables, was deleted.The definition of the indicated report, together with its corresponding Generator tables, was saved.Definition of report "%" too large - insufficient temporary memory to build report definitionThe definition of the report has exceeded the Report Server storage limits for building a report definition.Reduce the complexity of the report by reducing the number of report tables, body report fields, break report fields, fixed report fields, or literals.Your request to bind the definition of the indicated Screen was successful. Subsequent references to the Screen in this session, or the first reference to the Screen in any other session, cause its definition (and the definition of its constituent screen tables) to be bound.Your request to mark the indicated Screen as not bound was successful. References to this Screen in subsequent sessions will not cause its definition (and the definition of its constituent screen tables) to be bound.In the Screen Table Painter, you issued a PRINT request and the screen table definition was printed.Definition of Static SQL for Table % Member % failedYou were attempting to build Static SQL for the indicated table when an error occurred.View the message log for more information about the problem. Fix the problem, and try to generate or remove the Static SQL again.Definition of table "%" cannot be retrievedThe definition of the indicated table cannot be retrieved because of an internal error.The definition of the indicated table was copied to the table definition screen as you requested in your COPY command.Definition of table "%" deleted; rights held by %, requestor %The definition of the indicated table was deleted. Its promotion rights, however, are still held in the specified library by the specified requestor.Notify the requestor that the table definition has been deleted.The definition of the indicated table was deleted after you confirmed your request to delete.The definition of the indicated table does not exist.If your request requires the name of an existing table, use the Object Manager to see a list of tables. See the Managing Data manual for information about the Object Manager.A copy of the indicated table definition was sent to the printer at your request. You used the PRINT command or pressed <PF13>.Definition of table "%" saved; rights held by %, requestor %The definition of the indicated table was saved. Its promotion rights, however, are still held in the indicated library by the indicated requestor.The definition of the indicated table was saved at your request by pressing <PF3>.The viewing of the definition of this table is not allowed. Most likely this is an table that is used internally for special purposes.Your request to bind the definition of the indicated table was successful. The next reference to the table in this session, and the first reference to it in any other session, causes its definition to be bound.Definition of this special table can not be unloadedThe definition of a system table such as FIELDS, EVENTRULES, ORDERING, PARMS, or TABLES cannot be exported.The indicated SYSTABLES is empty.The table definition is too large to be processed. Possible reasons are:
• The Data Object Broker parameter CTABLESIZE is too smallIncrease the Data Object Broker parameter CTABLESIZE from 8 to 16 to double the CTABLE size to 16K. The Data Object Broker will have to be shut down and restarted with the new parameter.You are trying to print an object and the object is printed.DEFN rights requested for invalid object: "%" of type "%"You are trying to OBTAIN all rights, RELEASE all rights, or TRANSFER all rights on an object. However, the object or its children may have an invalid object type, or may not even exist at all. Therefore the operation fails.Check whether the object and its children exist and whether they have an invalid type.DELETE access to this object was denied. If the object is a parameterized table, the value of the first parameter for this table instance is indicated.The user can ask someone who has CONTROL access to the object to provide DELETE access.The user has deleted data from the given table with the specified parameter.An error was encountered during the deletion of a batch queue definition.You made a request to delete a batch request, and now you are required to confirm the request.Press <PF22> to delete the batch request, or press any other key to cancel the deletion.You started, but did not confirm, the delete of the logs for a specific activity on a change request.<PF22> to delete was pressed, but after getting the confirmation message to delete a subschema definition, some other key besides <PF22> was pressed.The user attempted to delete an object, but only the owner of the object, the owner's Security Administrator, or the System Administrator can delete an object.The user can contact one of the above authorized people to delete the object.The specified group definition was deleted.The specified library object was deleted.The specified report object was deleted.The specified screen object was deleted.The specified table object was deleted by the indicated user.The indicated Object Service Brokeruserid was removed from the system.DELETE failed: table "%" not positioned at any rowThe rule attempted to delete an occurrence without specifying the occurrence to be deleted.Perform a GET or a FORALL to specify the occurrence to be deleted.You are trying to delete a table but the operation fails.Check and see whether all entered values are valid. Also, check whether the specified table is deletable. If everything is correct but the operation still fails, contact TIBCO Support with the log and a description of the actions performed before the message was displayed.The report table that you want to delete is referenced in other reports.Check that the other reports are not needed or change the other reports to reference another report table.The DELETE command made to the named rule has been canceled.Delete of extracted data was aborted by user request.You have canceled your request to delete the object set.DELETE request for library "%" cancelledYou made a request to delete the library, but you did not confirm the request as required by the system. As a result, the deletion request was canceled.You have selected the specified object for deletion. When the change request is promoted, this object will be deleted. If you do not wish this to happen, use the C line command to remove it from the request.Deleting the specified table definition will cause its data to be deleted as well. You must confirm this request by pressing the indicated key.Confirm the deletion by pressing the indicated key, or press any other function key to cancel the request.You pressed <PF22> to confirm that you wanted to delete the specified object.The specified number of objects have been deleted from the target system.Deleted data for % tables or table instancesThe data of the specified number of tables or table instances have been deleted from the target system.You confirmed a deletion request for an empty library, and the library was DELETED.You confirmed your request to delete a library containing rules.You requested the deletion of an empty library and confirmation is now being solicited.You can press the specified key to confirm the request and have the library deleted, or press any other function key (including <Enter>) to have the request aborted.Deleting occurrence "%"; press <%> or type 'confirm' to confirmYou are about to delete this occurrence. Please confirm or cancel your request.If you wish to delete the occurrence, press the specified key or type confirm on the primary command line. Press another key if you do not wish to delete the occurrence.DELETING OLD VERSIONS OF OBJECTSThe Promotion tool deletes the old objects before loading the new ones.You made a request to DELETE a library with rules, and now you are being asked to confirm your request.You can press the indicated key to have the deletion carried out, or press any other key to have the deletion aborted.You canceled your request to delete by pressing a key other than <PF22>.The specified screen table or report table selected for deletion is used by the specified Screen or report that you selected for promotion.
• Do not delete the specified screen table or report table.
• The specified object cannot be accessed by a user at that security level.Derived indicator must be "S"ource or "D"erivedThe derived indicator is invalid. You must enter either S (the entry in the SOURCE NAME field is a field of the source table), or D (the entry in the SOURCE NAME field is a functional rule).Derived report field "%" of report table "%" in error; "%" is not the name of a report fieldIn a call to $RPTOVERLAP, the indicated report field is not a field of the indicated report table.Use the Report Definer to determine the correct report field and report table names. Correct the call to $RPTOVERLAP by using the Rule Editor.Descendents in LIST1 are DIFFERENT than counterparts in LIST2The change request was in a pending state before you changed the description. The description has been changed.No action required. The change request is still in a pending state.The description for the particular DBID and File No has been saved successfully.Designated line cannot be manipulated due to existing dataYou tried to use a line command in the Table Definer, but it cannot work because the table contains data.Destination object requires a name, library, or environmentSince the copy is local (no destination location is specified), the destination object should have at least a new name, library, or environment depending on the object type.Depending on the object type, enter either a new name, library, or environment.Did NOT Copy %; source & destination object are the sameYou have specified a copy such that the source and destination are the same. Therefore there is no need to copy.The two arguments, FIELD1 and FIELD2 have different numbers of fields.Dimensions of a report page cannot be changed while INSERTing occurrences into the same reportThe page length and width of a report cannot be modified while the report is being printed.In the rule application, call $RPTPARMS before the first INSERT into the report.Disclaim FAILED: SecAdmin % has lower CLEARANCE than user %If a Security Administrator tries to disclaim a user by referring the user to another Security Administrator who has a lower clearance than that user, the disclaim fails.Disclaim the user by referring the user to a Security Administrator who has the same or higher clearance than the user.DISCLAIM failed: selected SecAdmin same as current SecAdminThe Security Administrator requested to DISCLAIM a userid, but the new Security Administrator specified is the current Security Administrator.If a userid is to be disclaimed, choose another Security Administrator during the disclaim function.DISPLAY & TRANSFERCALL rule "%" does not have a handler for VALIDATEFAIL on screen "%"The validation exit key was pressed on a screen displayed by DISPLAY AND TRANSFERCALL. A VALIDATEFAIL exception was raised, but an exception handler does not exist in the DISPLAY AND TRANSFERCALL rule.Use the Rule Editor to change the rule invoked by DISPLAY AND TRANSFERCALL. Add an exception handler for VALIDATEFAIL to process the entry of the validation exit key.DISPLAY access to this screen object was denied.The user can ask someone who has CONTROL access to the screen to provide DISPLAY access.The data currently displayed on the screen is the top of the data.The specified display mask is not a valid date display mask.Reenter a valid display mask. Refer to the documentation for valid values.Display mask error detected for report field "%" of report table "%"The display mask of a report function contains a syntax error.Use the Report Definer to change the display mask to a valid syntax.Display masks are only valid for fields with syntax "B" or "P"Syntax of the field with the display mask is invalid.Specify Binary (B) or Packed (P) for syntax of the field with the display mask.Display masks are only valid for fields with syntax "B" or "P"You can specify display masks for fields with syntax Binary or Packed only.The Object Service Broker operation DISPLAY is not allowed under batch since there is no terminal associated with the Object Service Broker session. A terminal is required for the DISPLAY operation.Either run the rule as an interactive Object Service Broker user, or else change the rule to not use the DISPLAY operation.Display of report field "%" for report table "%" failed with a conversion errorThe conversion of a numeric report field to a string failed during the building of a report page.This is an internal Report Server error; contact TIBCO Support.DISPLAY operation not allowed for this environmentThe Object Service Broker DISPLAY operation is not allowed under this environment since there is no terminal associated with the session. A terminal is required for the DISPLAY operation. Examples of environments where there is no terminal are batch, CLI, SDK (C/C++) and SDK (Java).Run the rule as an interactive Object Service Broker user or change the rule to not use the DISPLAY operation.DISPLAYED RESOURCE DETAIL ENTRY HAS BEEN UPDATED/INSERTED SUCCESSFULLYThe previous update or insert request has completed.Disposition of % % in change#% of node % is inconsistentThe disposition of the named object in the specified change request is inconsistent with that in the other selected change requests. You have missed some other changes in the consolidation.Do not include the specified change request, or include other changes such that the disposition of the named object in the specified change is consistent with other select changes.Disposition of % has been changed from % to %The disposition of the specified object has been changed to match that on the target system. Note that only the change request definition loaded on the target system has been changed, the one in the extract file and the one in the source system will remain intact.You may now proceed to apply the change to the target system.The dispositions of the objects in the change request should match the target system now.You may proceed to apply the change to the target system.Distribution point "%" does not exist in source tableThe distribution point you specified does not exist in the source table.Specify a field of the source table as the distribution point.Distribution point "%" must be syntax:% length:% decimal:%The indicated field, which you specified as the distribution point, has different attributes from the source table.You added a table that is already in the join.You cannot add a table more than once. You may have to use <PF22> to delete the second instance.The SEARCH tool cannot retrieve the keywords or description of an object.You pressed <PF2> in the window for documentation, but no documentation is available.Due to locking, cannot % at this time; try againYou are trying to DISPLAY, SAVE or PRINT a screen definition, but the data store is LOCKED.Due to LOCKING cannot complete library DELETION; try againYou requested and confirmed the deletion of a library, but data locking prevents the deletion from occurring at request time.
• Wait and try to delete again, without leaving the current screenDUMP ITEM NUMBER MUST BE SPECIFIEDYou must specify which dump you wish to initiate by entering the number associated with it.Specify a dump number and try your request again.This message is used by the Object Service Broker program that produces the Information Log. It signals the beginning of a list of the tables accessed when the error occurred.Study the Object Service Broker Information Log.This message is used by the Object Service Broker program that produces the Information Log. It signals the beginning of a list of local variables used in the current transaction.Study the Object Service Broker Information Log.You specified two of the Object Service Broker fields to use the same CA-Datacom field.You can only have one field referring to a given CA-Datacom field. Remove one of the references to the CA-Datacom field.Duplicate field names in current or another segmentYou cannot have duplicate MetaStor field names in one table.Find the duplicate names and make their names unique.Two identical MetaStor field names were specified in the current segment or another segment. Duplicate names are not allowed in a MetaStor defined table.Change the duplicate field names so that each one is unique.You have specified a duplicate name for the field.Each field must have a unique name; remove one duplicate.You have specified duplicate names for some part of the core information about the MetaStor table you are defining.You must specify unique names for each entry in the part of the core information. Remove one of the duplicates, or rename it.You have specified a duplicate number for one of the fields.You must give each field a unique number. The numbers must be consecutive from 1 to the number of fields, with the primary keys coming first.You have specified a duplicate number, where duplicate numbering is not allowed.Respecify the duplicate number to be a unique number.Duplicate parameter/field name "%" not allowedEach parameter or field name must be unique within a table definition.Duplicate specification detected; remove or change entryIn the screen where the table permissions for an object set are specified, you changed a table name in the list of tables so that the entry duplicates the table specification for another entry in the list. Since the entries are both the same, one is considered invalid.Change the table name so that the entry is no longer a duplicate of another entry, or remove the duplicate entry by nullifying or blanking out the table name in that entry.During attempt to load, % Error(s) occurredThe specified number of errors were encountered during loading. This message appears in the user log file.During load, % Error(s) occurred; Read the reportAn error was encountered during the loading process.Press <PF2> to view the error messages. You can find more information about the error messages in this manual.Dynamic ; of ";" failed, Return Code = #, error code = ;, info = ;An error occurred during allocation or de-allocation of a report server work file. Additional information about the error is included in the message text.Using the "Return Code", "error code", and "info" values, refer to the appropriate operating system documentation or give the information to your systems personnel for interpretation.DYNAMIC UNALLOCATE FAILURE: RC = ____, ERROR = ____, INFORMATION =While attempting to release the allocation of the parameter card data set an error was detected. The message will present the return code, error code and any additional information codes provided by the system.Refer to the dynamic allocation/unallocation processes (SVC 99) in the manuals for the operating system to determine the most appropriate course of action.Table types available in the Dynamic Object Facility are:
•
•
•
•
•
•
•
•
Copyright © Cloud Software Group, Inc. All Rights Reserved |