![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
OAI Server Error: Invalid data received on connectionThe header for the data being sent or received is invalid.OAI Server Error: OAI client version #.# is not supported by this Execution EnvironmentThe version of the ActiveX Adapter client is not compatible with the version of the Execution Environment.Upgrade your ActiveX Adapter client to a more current version.OAI Server Error: Screentable '%' not in active screen '%'The screentable requested by the ActiveX Adapter client is not in the list of screentables for the current active screen. This can happen if an ActiveX Adapter client requests a screentable data from a previous screen during the display of the current screen and OAIBLOCKFACTOR is set too low (or set to the default value).
1. Avoid fetching data from screen other than the active/displayed one
2. Set OAIBLOCKFACTOR=32000 so that all screen data is retrieved and buffered in the ActiveX Adapter client without needing subsequent requests to the ActiveX Adapter server.OAI Server Error: System operation failed, '%'An internal system call failed. The name of the system call is given in the message.The ActiveX Adapter Compression Engine could not compress the requested data, probably due to an internal programming error.OAI Server Error: Unable to decompress dataThe ActiveX Adapter Compression Engine is unable to decompress the requested data, probably due to an internal programming error.OAI Server Error: Unable to initialize compression engine, level = #The ActiveX Adapter compression engine could not be initialized.An object does not exist in the specified library, environment or a location.Check to see whether the object is really located in the specified library, environment or location and try again.Object "%" in LIST1 and object "%" in LIST2 are alikeYou have specified the name and type of an object you wish to have unloaded; however, there is no such object of that type.Recheck the object specification to ensure that the name is correctly spelled and that the type is also correct. If the object indeed does not exist, you cannot unload it.Object "%" requires LIBRARY to be specifiedYou have requested to unload an object which requires the library to be specified. For example, if you have requested to unload a rule, you must specify which library the rule should be unloaded from. If you have requested to unload an object which itself contains rules, the library must be specified to unload the rules which are part of that object.In the top portion of the UNLOAD screen, type the name of the library to unload rules from.An object you want to print does not exist.Check and see whether the object exists or not before printing.Object "%" type "%" not printed because %The named object does not exist in the MetaStor.Object % % with disposition "%" already existsAn object that was marked as NEW already exists. The list of objects in the source system does not match the actual objects on the target system.Refer to the Promotions manual for information on running the GEN_SYS_TBLS rule.Object % % with disposition "%" is not part of the systemAn object marked as MOD (modify), DEL (delete), or DELOCC (delete occurrences) does not exist.Refer to the Promotions manual for information on running the GEN_SYS_TBLS rule.The specified object that you want to back out is used in a later change request.Informs you that the object has been copied to the destination.Informs you that the specified object is not copied.You are trying to delete an object and the operation is successful.You are trying to delete an object but the object does not exist.A condition prevents the line command from being executed. A system message follows this message and specifies the condition, such as locking or the rule to execute does not exist.Confirms that the indicated object list is deleted at your request.Confirms that the indicated object list is saved at your request.Confirms that the delete action is canceled at your request.OBJECT MODEL Table % cannot be included in a promotion requestThis table cannot be promoted through the promotion system because it is an object model definition table. That is, it is one of the tables that contain details about a specific object type.The relevant object model tables are automatically promoted when a particular object is requested for promotion and therefore these object model tables must not be promoted independently.Promote the required object, not these underlying tables.Object name "%" invalid for break event "%"You have performed a delete from the Object Set Definer, and the object set has been successfully deleted.You were trying to delete an object set that does not exist.You cannot rename your current object set to the indicated object set because the indicated object set has its security enabled.Choose a different name for your current object set.You have performed a SAVE from the Object Set Definer. Any changes made to the object set are now saved.The percent sign (%) can be one of the following:
• ENABLED - The object set will have an enabled status when you save it. Users/groups on the Enable List will obtain those permissions specified for the object set.
• DISABLED - The object set will have a disabled status when you save it. The users/groups on the Enable List will have those permissions specified in the object set permissions unless they have obtained these permissions through some other enabled object set permissions.The named object type (e.g., rule) cannot be protected by the Object Service Broker security system.If the object type is in error, correct it. If it is a rule, you can protect the library in which it resides. If it is another non-protectable object type (e.g., menu or object set,) you can protect the underlying tables which contain the object's definition.Object type "object" is not found; i.e., rule "x" is not found.The type of the specified object is invalid.Object TYPE and NAME or UNIT are required for query by objectYou are attempting to query change requests that contain a certain object or objects. An object search requires a valid TYPE and NAME or UNIT.Fill in the missing information and try the query again.OBJECT TYPE DEFINITION table "%" has more than ONE Primary KeyThere is a problem with the object type definition data for an object you requested to unload.Report this to your system administrator as there should not be a problem with the definition data of unloadable object types.OBJECT TYPE is required for each object namedYou have specified the name of an object to unload; however, you have not specified its type.Object names are not unique across object types, so you must supply a valid object type. You can press <PF1> to get a list of valid object types.Object TYPE must be one of: TBL, SCR, RPT, LIB, FRM, CON, APPYou made a request to manage permissions to an object, or you requested a list of objects (from the main menu), but you supplied an invalid type of object.Fill in the object type before pressing <Enter> or invoking the OPTIONS function.Objects "%" & "%" are deleted from 'list1' & 'list2'You are trying to delete an object on list 1 and its counterpart on list 2 and both of them are deleted.Objects are missing from selection list, due to securityThe list of selected objects is incomplete because security prevents some objects from appearing in the list.Objects did not pass the checking process, press <PF2> for logPress <PF2> to see the list of objects which cannot be included in the change request.Press <PF2> to see the list and remove the objects from the change.Objects in LIST1 and corresponding objects in LIST2 are alikeYou are trying to compare two lists of objects to see whether there are any differences between them. The result is: there are no differences.These objects were not loaded because the action caused them to be skipped.You have specified an object for which version information is required to identify the object. For example, to identify a RULE object, you must specify the LIBRARY in addition to the NAME.Specify the version of the object so it can be identified.These objects were replaced because they collided with the database and the action was IR.The specified number is the number of undisplayed occurrences above the current screen. The message appears as a result of the # primary command.The specified number is the number of changed occurrences as a result of a CHANGE command with the PAGE, ALL, or REST option.Confirms that the occurrence has been saved, deleted, or printed.
1. A GET or DELETE operation specified a non-existent primary or secondary key.
2. The selection conditions could not be satisfied.Change the selection to refer to an existing primary or secondary key value, or use an ACCESSFAIL exception handler.The FIND primary command was unable to find an occurrence that matched the search criteria.A FIND command has been unsuccessful.The FIND command did not find a match for the criteria you specified. If you are repeating a previous successful find this simply means you have reached the end of the list without finding another match.Verify the string you are attempting to find is correct.Occurrences NOT LOADED because action is MI:These occurrences were not loaded because occurrences with identical primary keys already exist in the database.As requested, the occurrences of the specified table are deleted.Occurrences, but not the definitions, were loaded for the listed tables.Odd number of bytes between SO/SI in field "%"The syntax W field string value contains an odd number of bytes between an SO/SI pair (which make double-byte character display impossible).Check how the field string value is assigned. Review the various string functions (such as concatenation, headstring, etc.) used to derive the erroneous string.OFFSET + LENGTH > LENGTH( STRING)Internal 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.Offset has been calculated at your request.Internal 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.ONE and ONLY ONE selected rule to execute must be entry levelOf the rules that you have marked with the X line command, only one can, and must, have a Y in its ENTRY field. It must call all the other rules marked with an X.Mark only one X rule with a Y in the ENTRY field.One field must be defined as the primary keyThe MetaStor requires that all tables have a primary key field.Use the K line command to specify which field is the primary key.You did not enter a P in the KEY field for any of the fields defined.Enter a P in the KEY field for a field that you want to be the primary key. Ensure that this field is at the top of the list of fields. You can find more information about primary keys in the Managing Data manual.One scrolling screen table is required if scroll entry usedYou have defined your screen to have a scroll entry but not provided a scrolling screen table.Define one of your screen tables to scroll, or delete the information in the SCROLL AMOUNT ENTRY specification.A MetaStor IMS table can have only one primary key.Unselect the previously selected key field (line command D), or select it as an ordinary field (line command S).Only first 200 valid values shown; use selection to see othersThe prompt screen is filled with the first 200 valid values.Enter a valid selection command to see additional prompt values.Only IDMS CALC keys can be selected as parametersThe MetaStor parameter can only be an CA-IDMS CALC key. If composite CALC keys exist, select all composites as parameters.Choose CALC field in the first IDMS record as data parameter.Only INSERT and PRINT table accesses are supported for a report tableThe Report Server was passed an invalid table access code.This is an internal Object Service Broker error; contact TIBCO Support.Only line command allowed for this row: "I"You have entered a line command other than I in the first line command area. All other line commands are not allowed in this area.Change the line command to I or remove the line command from this area.Only literal source definitions may exceed 255 charactersSource definition value is too large. Only a literal can be greater than 255 characters.Only occurrences for selected parm values are unloadedYou have unloaded some of the occurrences of a parameterized table.Use the Delete line command (D) to remove any extra count fields.Only one data parameter can be specified for % tableYou have specified more than one data parameter for the given table type.You selected more than one repeating group. This is an invalid selection.You can specify only one key field for an IDgen table.Remove any additional P designations from the fields.ONLY ONE ITEM MAY BE CHANGED IN A SINGLE REQUESTYou have attempted to make too many changes within a single update function.Retry your changes but restrict your request to one action at a time.You cannot select any more primary key fields because only one primary key field is allowed, and it is preselected for you.Remove the primary key selection command (K).You have specified more than one location parameter for the table. Each table can have only one location parameter.Delete the additional location parameters of the table.You selected more than one MU group field. This selection is invalid.Only one non-titles report table is allowed per reportOnly one fixed report table within a report can be defined with TITLE ONLY=N. This report table can then have multiple occurrences and control information (e.g., SORT, BREAK).Ensure that all TITLE ONLY=Y except for one report table.You have selected more than one primary key.A composite key is not supported for this type of table.Remove all but one P from the KEY field of the Table Definer.In a screen, one scroll indicator is allowed.There is more than one statement ending in semicolon (;) or a colon (:) on a line.Separate the statements so that there is only one statement to a line.Only one table can be specified for Batch Unload.You specified more than one table for your control card. The Batch Unload utility for unloading data from the MetaStor accepts only one table at a time.Lines that you move or copy are all placed in one position marked by A, B, or the cursor. More than one position is marked.Only parameters allowed for GETNEXT; % is not a parameterOnly table names and parameters can be specified on a GETNEXT.You attempted to clear a nonnative Object Service Broker table. Only native Object Service Broker tables (i.e., tables that store their data physically in the Object Service Broker database) can be cleared by using CLRTAB.A nonnative Object Service Broker table can be cleared by executing the rule CLEARTABLE_APPL.Your request to move a nonnative Object Service Broker table was rejected. Only native Object Service Broker tables contain data that is stored physically in the Object Service Broker database; thus, only native Object Service Broker tables can be moved.Do not attempt to move nonnative Object Service Broker tables.Your attempt to build a secondary index on a non-TDS table was rejected. Secondary indexes are only supported on TDS tables.Do not attempt to build a secondary index on a non-TDS table.Only the OWNER may allow CONTROL access to an objectYou are authorized to control an object and you were in the Manage Permissions function when you tried to extend that control access to another user. However, only the owner of the object, the owner's Security Administrator, and level-7 users may pass control in this way.Set the control permission to N or remove the entire row. If you want to provide control access to another user, consult a user who is authorized to pass control.The only line command permitted is S (Select).You are only allowed to use the select ("S") line command.Either "blank out" the line command, or type an "S" in the line command.The SHOW IF NO OWNER option is only valid where:
• Owner records are retrieved using an Obtain-Owner GET and FORALL directives, and
• Specify valid values for SHOW IF NO OWNER field.Unable to open the specified DBID and File No in ADABAS.Review the returned response code in the message to determine the appropriate action required to fix the problem with ADABAS.Open of sort work file failed. The DDNAME, the module name, and the return code are supplied for debugging purposes.Call your system administrator to check the return code in Register 15 against the appropriate vendor's manual. Correct the problem as required.Open of the named file failed. For more error messages explaining the cause for the open error, refer to the operating system log.Call your system administrator for assistance.Open of a print file for report "%" failed: %The Report Server cannot open a print file for a report output media of PRT.Use the system message appended to this message to determine the action to take.Open of an output dataset for report "%" failed: %The Report Server cannot open a file as a report output media.Use the system message appended to this message to determine the action to take.OPERATOR COMMAND NOT CONFIRMED, REQUEST IGNOREDThe operator function you previously requested was not confirmed, it has been abandoned.OPERATOR COMMAND NOT SUPPORTED THROUGH THIS FUNCTIONOnly the highlighted operator commands can be supported via the Administrator operator function. The request you have selected should either be handled through the function indicated in brackets or through the operator console.An ordering field in a table request or in a stored ordering is not defined in the table.
• Include the ordering field in the table definition.ORDER field "%.%" has invalid LENGTH, DECIMAL, SYNTAX or POSITIONThe specified field has invalid attributes. The table definition was probably altered without using the Table Definer.Use the Table Definer to correct the attributes of the order field.Ordered GET not allowed because ordered FORALL in progress for table "%"You issued a GET statement with a WHERE clause that specifies a field that is ordered (in the table definition), and this GET statement falls within a FORALL loop. This kind of GET statement is not permitted within a FORALL loop.Move the GET from within the FORALL loop, or remove the ordering from the field.Ordering "%" is invalid - must be "A"scending or "D"escendingThe specified ordering indicator is invalid; it must be either A (Ascending) or D (Descending).Ordering error for table "%" - sequence not A or DThe ordering for a field must be either A (ascending) or D (descending).
• Modify the appropriate rule to use a different ordering field.
• Modify the table definition so that the ordering field contains the ordering character either A or D.ORDERING field "%" not referred to in field listYou have specified a field to use for ordering the DAT table. The field you have referred to is not defined in the EXTENSIONS information of the table definition.You must remove the field named from the ORDERING part of the CORE context, or you must include a field in the EXTENSIONS context which has this name.Ordering must be "A"scending or "D"escending for field %The order of the occurrences in the table as determined by the indicated field must be either A (Ascending) or D (Descending).Specify A or D only, or remove the specification.Ordering on derived fields is not supported.Using the traceback log, locate the rule containing the ordering clause and remove the reference to the derived field.Remove the ordering specification from beside the indicated field.Ordering is not allowed on a field with the specified syntax.Ordering string specified for access on table "%" is too longMore than 15 fields were specified in the table access statement.OTMA component not properly installedThe Object Service Broker OTMA Callable Interface component was not properly installed. Specifically, the IBM IMS OTMA "C" stub, DFSYCRET, was not linked-in with the Object Service Broker S6BDRSES load module.Refer to the Object Service Broker install manual or contact TIBCO Support for assistance.The specified OTMA request failed. The return code and reason codes are provided in the Map table. For an explanation of the codes, refer to the IBM "IMS Open Transaction Manager Access Guide and Reference" manual.OUT OF MEMORY: Unable to LOAD/INSERT any more occurrencesThe table is too large for all of it to be held in the memory allotted.
• Reduce the number of occurrences, for example use a SELECT command.
• Increase the amount of memory for the Object Service Broker session.Output buffer overflow - no room to clear screenInternal 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.Internal 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.You pressed <PF5> or <PF6> with Hardcopy set to N. The output is either a PRINT TREE if you pressed <PF5>, or a CROSS REFERENCE if you pressed <PF6>.Output medium type in $SETRPTMEDIUM was not recognized as an accepted valueThe second parameter in the $SETRPTMEDIUM tool is not one of:
• INDIRECTFILE (Output to file named in variable or ddname).Correct the second parameter in the $SETRPTMEDIUM tool to match one of the above entries.Formatting of a table buffer by $FORMATROW failed. The length of the result of the function is greater than 16 KB.You attempted to send the output to both a printer and a data set.You tried to delete the definition of a batch queue, but the queue may still have outstanding batch requests.Ensure that no outstanding pending batch requests exist on the queue to be deleted.OVERFLOW: Total length of report function must not exceed 128The total length of the source definition for a report function entered on the derived field derivation screen must not exceed 128.Remove some of the fields specified in your OF or BY parameters, or shorten your selection string. You may use a single derived field to contain the definition of a number of fields that are defined separately.Overflow detected when evaluating source of report field "%" of report table "%"An arithmetic overflow was detected when a derived report field was assigned a value.Review the source of the derived report field and the input data used to set its value.The conversion of a string yields a number that is bigger than the maximum currently supported (approximately 10E75).Ensure that the string corresponds to a number that does not exceed the maximum.The indicated report tables overlap in their current definition.Change the specified row or column for the report tables to remove the overlap.OVERLAP : "%" in rows %-%, "%" in rows %-%Two report tables will overlap. The message indicates the rows occupied by each report table, with at least one row being in common.Correct the report table definitions and ensure that they do not overlap.Overlap detected between the indicated fields. The second percent sign (%) is either "literal" or "field"; the third % is the offending field. If it is a literal, the value of the literal is displayed; otherwise, the field name is displayed.Overlap exists between %(Col:%-%) and %(Col:%-%)The two indicated elements overlap each other.Modify the columns/lengths of the elements so that they do not overlap each other.CANCEL was requested when the current screen was displaying the definition of two report tables that overlap. CANCEL might not be able to resolve the overlap because changes to the Paint Screen have already been saved. For example, fields were added.If you cannot execute the report because the overlap condition still exists, then return to the Report Definer. Either change the row and column of the report table to prevent the overlap or move the overlapping report field in the Paint Screen.Overlapping of external fields is not allowed for the indicated table type.Cannot add the field as it will overlap the indicated element.Either relocate the indicated element or add the field somewhere else.The batch options specified on the screen for the indicated rule are about to replace the options that were saved previously for the same rule.Press <PF3> to save the options on the screen, or press any other key to cancel the SAVE function.Overwrote the control table occurrence for the specified object in the specified control table. This is part of the audit trail for the COPY tool.OWNERSHIP of selected objects TRANSFERRED to "%"You used the TRANSFER&EXIT function from the Transfer Ownership function of the main menu. Any objects that were selected have been transferred to the new owner specified in the Transfer Ownership screen.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |