![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
READ 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 READ access.Read access to the indicated table is denied for security reasons.Remove the table from the report. If you need that table to generate the report, contact your Security Administrator.The user has read the given table with the specified parameter.You must enter a valid ready mode on the VERIFY ACCESS PATH screen to prepare the CA-IDMS database for a certain type of access. Valid ready modes are:Rebind of % "%" with FIX=% failed due to error "%"An error was encountered when attempting to rebind the specified object.Resolve the error specified and re-run @PROMBINDOBJS.Record and element files incompatible...check their contentsThe data contained in the record and element import files is not from the same subschema.
1. Check the contents of the record and element files that you were going to load.
2. Use the "Load an IDMS Subschema" manager utility again to change the files that you import.Record length for table "%" is larger than record length of VSAM % "%"The length of an occurrence in the indicated table does not equal the length of a record in the VSAM data set. The variables, from left to right, are as follows:Change the definition of the Object Service Broker table so that the sum of the lengths of all the fields equals the actual length of the VSAM record.Record of % file smaller than occurrence size of table "%"The record size for the Import or Export table must be equal to or greater than the sum of the field lengths given in the definition of the table.
• Allocate a larger record size for the file that corresponds to the Import or Export table.
• Reduce the total field length by changing the definition of the Import or Export table.You have requested to unload an object which includes by reference other data. The table which references the data to be included does not exist.Report this to the System Administrator as it indicates a problem in the object type definition data for the object you requested to unload.There is a problem with the object type specification for an object which you have requested to unload.This should be reported to the System Administrator as there should not be a problem with the object type definitions for unloadable objects.The indicated field of the indicated table has an entry in the REFNAME field of the table definition. The table in the REFNAME field, however, is invalid.Check the REFNAME field to ensure that you are referring to the correct table. Also check your field definition to ensure that it is compatible with the field in the referred table.Reference data for '%' cannot be deleted, error in resolvingYou are trying to delete a reference data table of an object but the process fails.The utility fails to resolve the reference data tables for the specified object.You are trying to delete a reference data table of an object and the table has been deleted.Reference table for data parameter must refer to the same VSAM parent tableYou have entered different values for REFERENCE in your data parameter list. The field REFERENCE is used to store the name of the parent table used to access multiple record format VSAM file, and therefore, all REFERENCE values must refer to the same table.Change REFERENCE in your data parameter list to refer to the same VSAM parent.Reference table must be an unparameterized table of type VSM and IDGEN NReference table (parent table to access multiple record format VSAM file) has to be defined as a MetaStor VSM table with no data parameter and IDgen set to N.Specify a valid Reference table with no data parameter, table type of VSM and IDgen set to N.Reference to null in selection string for access on table "%"References to a NULL value are not currently supported in selection conditions for table access statements when using the High Level Language interface.Reference to report field "%" of report table "%" cannot be resolved, name refers to itselfA loop exists in the definition of a derived report field. The source of the report field refers to itself.Use the Report Definer to review the definition of the derived report field and resolve the name conflict.Referenced data for object "%" not printed, error in resolvingYou are trying to print an object and an error occurred when PRINTDEFN tries to resolve the referenced data tables of that object.Check and see whether the referenced data tables for that object do exist and are defined properly. Retry the operation again.You are trying to print an object and a table which is referenced by that object is empty and therefore not printed.In order to group connections together a region or group code can be specified at connection time; if omitted a default code will be set based on the connection type. An error was detected when trying to retrieve the list of known region names.Review the joblog for possible additional messages which may help identify the cause of the problem. Retry your request. Contact TIBCO Support if the problem persists.Relate Tables screen unavailable - only one table has been specifiedThe Relate Tables screen is irrelevant because you selected only one source data table.Relation for "%" of table "%" has already been specifiedThe indicated field is already related to another field of a source data table. Each field can only be related to one field from another table.Remove one of the duplicate fields from the input area.
2. A communicating failure occurred during lock release initiation.The session will be terminated but the message can be reviewed first.Contact TIBCO Support if the error is not identifiable.Renamed rule % is in library %. Promotion rights not obtainedYou have renamed a rule to a name that exists in the Installation library. The promotion rights are not obtained.No action required. If you want to modify the rule in the Installation library, you must explicitly edit it.The name of the rule was changed as one token was changed for another.The named object has been repackaged from the specified change request created from the specified node.REPEAT failed - Max number of screen tables has been reachedThe REPEAT command failed because the maximum number of screen tables allowed for a screen has been reached. You are not allowed to add any more screen tables.If you still want to use REPEAT to add another screen table, remove or combine some of the existing screen tables.REPEAT TYPE must be specified for Period group and Multiple Occurring fieldYou specified N for MU/Special Fld in Grp which is incompatible with the repeat type. A value of N is only valid for repeat type "GRP".Specify a value for MU/Special Fld in Grp that is compatible with the repeat type.Repeating and non-repeating fields cannot be mixed in the same definitionYou have selected repeating and non-repeating fields in the same table definition; this is not supported in Object Service Broker.Specify field selection by choosing only repeating fields or non-repeating fields.When a Repeating Group table is defined its parameter must have a "reference" to a parent table. The parent table must not be parameterized nor can the FORALL, in which it is used to parent a repeating group FORALL, request "ordering".Repeating Group - parent table not found "%"A Repeating Group Table FORALL can only be used within a Parent Table FORALL, for example,Example FORALL parent-table-name...REPLACE 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 REPLACE access.The user has replaced data in the given table with the specified parameter value.REPLACE failed: table "%" not positioned at any rowThe rule attempted to replace an occurrence.The occurrence to be replaced has not been specified. Only the replacement data has been specified.Perform a GET or a FORALL to specify the occurrence to be replaced.These occurrences which were in the table before loading have been replaced with occurrences from the file because the action was MR.Report "%" already exists; cannot overwriteThe report name was changed and an attempt was made to save the current report definition under a new name. Because a definition already exists for the specified name, the request to save has been denied.Rename the report to the original name or a name that is not already associated with a report definition.Report "%" cannot be referred to more than onceYou referred to a particular report more than once while specifying report permissions for an Object set definition.Remove duplicate entries from the list by replacing the report name with blanks, nulls, or another report name.A DELETE operation has been performed.The user tried to delete a report that does not exist.Delete only those reports that have been assigned a definition.You referred to a non-existent report.Report "%" has been defined with more than 24 breaksA report can have at most a total of 24 break and summary report fields.Reduce the complexity of the report by using fewer break and/or summary fields.The indicated report was sent to the requested destination.Report "%" has too many break and summary report fields; the maximum number is #The definition of the report contains too many break and summary control fields.Simplify the report by reducing the number of break or summary fields.If the report name was misspelled, use the Report Definer to determine the correct name of the report. Otherwise, use the Report Definer to create the named report.The indicated report was not deleted because you did not confirm the deletion request.The indicated report was not overwritten because you did not press the confirmation key.Report ";" can not request immediate output to a currently active output mediumAnother report in the same transaction has already requested immediate output to the same medium (Log, Printer or File).Either send the reports to different output media or remove one of the immediate output requests.You confirmed a deletion request for a report definition. This message confirms that the specified report definition has been deleted.You entered a report name on the UNLOAD selection screen more than once. A report can only be unloaded once.A report by the name specified does not exist.Report % not deleted - PF2 to check the message logAn error occurred while deleting the given report. Refer to the message log <PF2> for more information.Correct the errors which are described in the message log and try again.Report cannot be produced due to run time errorThe report cannot be produced due to an internal problem.If the Data Object Broker parameters CTABLESIZE and XTABLESIZE are both set to 31, the definition of the indicated report is too complex. In other words, there are too many report tables, report fields, or literals for this report.Ensure the Data Object Broker Parameters CTABLESIZE AND XTABLESIZE are set to 31. If the problem still occurs, decrease the number of report fields and literals for this report.The report definition print has been completed.Report field "%" of report table "%" in error, display masks not supported for string valuesThe value in the indicated report field cannot be converted to a number.Review the source of the report field and the input data used to set its value. Change the display mask or the report field as appropriate.Report field "%" of report table "%" is defined as both an input field and a derived report fieldA report field of a body report table has been defined as both an input field for the report and a derived report field.Use the Report Definer to remove the source string for the report field.Report field definition required for control field "%"A control field (e.g., SORT, BREAK) has been specified without a corresponding definition for the field in the Definition Area.Ensure that each field specified on the common screen is also in the Definition Area.Report field names can be a maximum of 16 characters and consists of letters, digits, @, $, #, and underscores. The name cannot begin with a digit or underscore.Report function "%" must have exactly one operand fieldReport functions TOTAL, AVERAGE, MIN, and MAX can have at most one Of-Field.Use the Report Definer to review the derived report fields of the report.An error was detected during selection processing for a report or a report function.See the appended message from the selection evaluator to determine the action to take.Report functions cannot be referenced in TITLES report tablesTitles report tables cannot contain report functions.Remove the report function from the Titles report table.Report Functions screen unavailable - no print field has been specifiedThe Report Functions screen is irrelevant because you have not selected any fields yet.You ended the Report Generator session and returned to the Object Manager or workbench.A report name was not specified when $RPTOVERLAP was called.Use the Rule Editor to change the call to $RPTOVERLAP to include a report name as the first argument.Heading for report issued by LOAD. The file which was the source is named.Report permissions for object set will be committed on SAVEYou saved the report permissions specifications for an object set definition and you are viewing the object set definition screen. If the object set definition screen is saved, the report permissions are committed; if not, changes to the report permissions are ignored.The print process you started is complete.A DELETE operation for a report table has been performed.Report table names can be a maximum of 16 characters and consist of letters, digits, @, $, #, and underscores. The name cannot begin with a digit or an underscore.A report table name was not specified when $RPTOVERLAP was called.Use the Rule Editor to change the call to $RPTOVERLAP to include a report table name as the second argument.Report tables/control breaks require a valid nameA report table or control break must have a valid name before it can be painted.Assign the report table or control break a valid name before painting it.The requested table operation cannot be performed because of the table type. For example: PRM and IMP tables cannot be updated.Request DENIED - cannot update permissions to META-DATA tablesYou requested to update permissions for a meta-table (e.g., FIELDS, TABLES, REPORTS, PARMS, SCREENTABLES); this is not allowed.If meta-table permission updates are required, contact TIBCO Support.Request for attribute for screen field "%" failedFormatting of a table buffer by $FORMATROW failed. The format string contains a request for the attributes for the i-th screen field of a screen table.REQUEST ISSUE INDICATED BUT NO CHANGES WERE REQUESTEDYou have requested the invocation of pending changes to the segment status or mode. However, there are no changes pending.The specified dump request has been sent to the Data Object Broker.REQUEST LENGTH ROUNDED UP TO BE DIVISIBLE BY 16Notification that the system has adjusted your requested length to be divisible by 16.REQUEST POOL CONTROL BLOCK COULD NOT BE RETRIEVEDWhen attempting to send the request to the Data Object Broker to retrieve the pool management information for the pool you selected an error was detected.Review the joblog to determine if there are other messages that may help identify the cause of the problem. Retry your request. If the problem persists contact TIBCO Support.You rejected the request to delete the specified field by pressing a key other than <PF22>.Request to manage permissions to "%" CANCELLEDYou canceled from either the individual object permissions list or from the ObjectSet permissions list; changes are ignored.Request to manage permissions to % CANCELLEDYou canceled a request from the object permissions list.REQUEST TO START CONNECTIONS TO group ISSUEDThis acknowledgement message indicates that the system has been requested to initiate the generated connects as per your request.REQUESTED ACTION WILL NOT BE HONORED BECAUSE THERE ARE PENDING UPDATESSchedule copy and associate requests may not be issued while there are pending updates that have not been saved to the repository.Either refresh the schedule recalling the current schedule using the Schedule Index selection or save the pending updates before proceeding with the copy or associate request.REQUESTED BUFFER NUMBER IS TOO LARGEThe buffer number requested is larger than the number of buffers allocated to the resident page pool.REQUESTED DATASET IS EITHER INVALID OR NOT AVAILABLEThe input data set number is either invalid or the data set is not available for processing.REQUESTED DETAIL ENTRY NOT FOUND, REENTER TYPE + GROUP OR GOTO GROUPLISTThe Resource Detail entry for the specified type and group could not be located by the system; either reenter the type and group or step through the Group List Screen.An INSERT, GET, or REPLACE operation was requested for an occurrence. The occurrence has been deleted, but the deletion has not yet been committed.Remove the INSERT, GET, or REPLACE operation request.REQUESTED MEMORY ADDRESS IS INVALIDThe memory address you specified is not valid within the Data Object Broker you are currently processing under.Correct your address specification and retry the request.REQUESTED PAGE NUMBER IS INVALIDThe page number you requested for display is invalid or could not be retrieved.Specify the page you desire again and resubmit your request.REQUESTED SEGMENT IS EITHER INVALID OR NOT AVAILABLEThe segment number specified is invalid or currently offline. Only valid online segments can be processed.REQUESTED SEGMENT IS NOT IN LIST OF DEFINED SEGMENTSThe specified segment number is not known to the Data Object Broker.Use cursor select processing from the segment list to select a valid segment number.Required field "%" in source "%" but not in subview "%"The subview occurrence that is being inserted or replaced does not contain a field that is required in the source table definition.Include all fields required by the source table in the definition of the subview table.To continue, you need to specify a value for the highlighted field.Required value for "%" in table "%" (or secondary key value) is null
• A primary or secondary key field with a null value has been specified.
• The field contains a null value but REQUIRED=YES is specified and no default value is present.For a primary or secondary key field, assign a non-null value. For a non-key field, provide a default value.RESOURCE DETAIL ENTRY NOT DEFINED FOR THE OUTBOUND PATH TO node-nameVia cursor position the named node was identified. You requested the display of the Resource Detail screen for that Node but it is not defined in the configuration.Select a different Node or add the desired node selecting PF5 off the Resource Type List screen.RESOURCE MANAGER INTERNAL PROCESSING ERROR DETECTED, REASON CODE -When attempting to process a request or obtain data from the Data Object Broker an error was detected. The processing that detected the error is indicated by the reason code. The error code could be any of the following:
• 001 - The internal processing code was outside acceptable values.
• Reason codes 002 - 016 pertain to data retrieval failures resulting from communication problems or security violations in the Data Object Broker:
•
• 013 - Request to associate a schedule to a resource
• 015 - Schedule list retrieval (list of all known schedule names)
• 016 - User of a specified schedule retrievalReview the joblog to determine if there are additional messages which may help identify the cause of the problem. Try your request again. If the problem persists contact TIBCO Support.RESOURCE TYPE HAS NOT BEEN SPECIFIED, PLEASE PRESS PF2 TO DISPLAY TYPELISTThe resource detail screen was entered via PF5 off the type list, PF4 was then pressed to display the list of groups within type. At this point the system has never had a type identified and therefore cannot satisfy the request.press PF2 to display the type list and then select the desired type.RESPONSE BUFFER NOT AVAILABLE FOR LOCK OWNER LISTWhen the Data Object Broker was attempting to obtain a buffer in which to build the lock owner list for a given table, the acquisition failed.This should be a temporary problem, retry the request.RESTART THE EXECUTION ENVIRONMENT AND REAPPLYSome of the objects included in the change request are bound on the target system. These objects have to be unbound before the change can be applied. This message is preceded by message 101.If you are in a multiple session system, restart the Execution Environment and apply the change again. If you are in a single session system, log off and log on to apply the change.RESTORING RIGHTS AND PERFORMING HOUSEKEEPINGThis message appears on the source system when you do a promotion and the rights are reset.RESTORING VERSIONS OF OBJECTSThe Promotion utility is restoring previous versions of objects as a result of a back out request.Result of expression in condition is not a logical valueYou have not followed the restrictions that apply to expressions in the conditions part of a rule.Result of ROUND is not between - 2 ** 31 and 2 ** 31 - 1 inclusiveThe result of the ROUND tool does not fall within the valid range.Result Set table name conflicts with existing table name %You are defining a stored procedure table definition that has one or more result sets. The result set table name that will be generated already exists.The first 14 characters of the table name must be unique.Loading module M204DISP, M204ENCR or M204CMD failed.You pressed <PF11> until you reached the right edge of the displayable information. No more information exists to the right of the screen you are viewing.You have requested to page right; however, there is no more content to the right.Rights are already held for this object.You do not have the rights for the specified object.Depending on the operation, you may need to obtain the rights if it is required. However, if the rights are not required, you may take no actions on it.You are trying to do one of the following operations on an object: OBTAIN rights, RELEASE rights, and TRANSFER rights. The operation is successful.While obtaining/releasing/transferring rights on an object which can have children, this informative message is shown in the audit trail.The promotion rights for the specified object are held by the specified user.If you want to continue backing out a change, press <PF22>. If the object is not a rule, rights for the object are reset and the object is deleted. You will not be able to restore the object.While obtaining/releasing/transferring rights on an object which can have children, the message is shown on the audit trail if an action is being performed on child objects.Rights for object "%" type "%" not obtained, object not existYou are trying to obtain the rights on an object but the object does not exist.Rights for rule "%" cannot be obtained in library "%"You are trying to obtain the rights for a specified object; however, the operation fails. This is due to one of the following:
1. If the type of the object is a rule, the rule may not exist in the library.Check and see whether or not the object you specified really exists.Rights for rule "%" cannot be transferred to library "%"You are trying to transfer the rights of one rule from one library to another but the transfer fails. This failure is caused by one of the following reasons:
• The destination library does not contain the specified rule.Check whether you have the rights for the specified rule, or whether the destination library exists and contains that rule.Rights on % % in CR#% of loc % are not held, cannot submitYou cannot submit the change because you do not have rights on the named object which is part of the specified change of the specified source node.Remove the specified change request or ask the person/group who is holding rights on the named object to release or transfer the rights to you.The request to roll back the change request is canceled, accepted, or accepted and the description is saved.Root is required for tree or cross referenceYou pressed <PF5> or <PF6> but did not specify a root rule.This message is used by the Object Service Broker program that produces the Information Log.Study the Object Service Broker Information Log.Routine "%" not available in current environmentA routine has been called in an environment (BATCH, CICS, IMS/DC and so on) where it is not available.Confirm that you are using the right environment and/or routine.Routine "%" returned an invalid exception code (#)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.Routine "%" unsupported in 3270 presentation environmentThe specified routine needs services from the operating system; these services are not currently available in a 3270 environment.Reorganize your application so that it does not use operating system dependent tools.The routine cannot be invoked by this shareable tool. Either the routine returns a value and is being invoked using shareable tool S6BCALL or the routine does not return a value and is being invoked by S6BFUNCTION.Use the correct shareable tool to invoke the routine.Row argument larger than maximum number of rowsInternal 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.The indicated rule was overwritten at your request.Rule "%" has been saved for generating report "%"You requested that the indicated rule be saved in the local library.The rule named is too complex in its present form to save.Split the rule into two or more less complex rules.You pressed <PF4>, but a rule on the list was not found. The rules listed above the specified rule have been printed.Correct or remove the name of the rule that could not be found. You can delete the names above that rule to avoid printing them again.Rule to be debugged must be in one of the following rule libraries: SYSTEM, INSTALLATION, LOCAL.The rule specified for execution from the workbench was not found.Check the spelling of the rule name and the library in which it resides.The indicated rule was not overwritten because you did not confirm your request to save the rule.The rule was copied successfully. It resulted in overwriting a rule in the destination library with the same name.Rule "%" used as a function but does not return a valueYou called a procedural rule as a function.Confirms that one of the following actions was successful:The specified rule cannot be found in the specified local library. Consequently, the promotion has failed.Restore the specified rule into the specified library and reapply the change.You entered the rule name more than once on the UNLOAD selection screen. A rule cannot be unloaded more than once.Repeat the operation when no other user is editing the rule.The requested rule cannot be found in the specified library.Correct the name of the rule or the name of the library.The promotion system attempts to bind all the rules being promoted, but this will fail unless the userid applying the promotion has level-7 security.No action is required. At this point the promotion has completed without binding the rules. If binding rules during promotion is desired, a level-7 user should administer the promotions.The program has been placed in the indicated data set.Rule call for derived report field "%" of report table "%" failedThe source of the derived report field contains a rule function call that failed when the derivation was evaluated.Look at the error log to determine why the rule failed.TheObject Service Broker program that produces the information Log cannot analyze the error.Study the Object Service Broker Information Log.% stands for one of the following warnings:A non-executable statement is missing a sequence # on the action (when outside a FORALL or UNTIL loop). An unreachable statement appears in the rule after a RETURN or SIGNAL statement in the same execution path.Check the rule to determine if statements should be added, deleted or moved.The rule does not reside in the library specified.Rule has too many parameters for parameter values promptIf the name of a rule to be executed is specified from the workbench without values for the required parameters being specified, a new screen is written to prompt for the parameter values. The number of required parameter values must fit on one screen without scrolling. For 3270 models 2, 3, 4, and 5, a maximum of 10, 14, 19, and 11 parameter values can be specified. The rule to be executed has more parameters than the allowed maximum.
•
• Execute the workbench from a 3270 terminal with a larger number of rows
• Write a "wrapper" rule with fewer parameters to call the desired target ruleRepeat the operation when no other user is editing the rule.You pressed <Enter> and the rule names from the library chosen are displayed on the screen.Rule may be missing "RETURN" statementsThe rule has conditions. One path has a RETURN statement, but at least one other does not.Enter a RETURN statement or press <PF3> to confirm that you do not want another RETURN statement.Rule name "%" exceeds maximum length of % charsThe name of rule % has too many characters. The maximum number of characters presently allowed is 16.Rule name and parameters could not be parsed properlyThere is a syntax error in the rule name or parameters.Rule name not passed as command line parameterThe rule name has not been specified.When prompting for parameter values for a rule, the user pressed <PF3> or <PF12> to terminate the prompt. The specified rule was therefore not executed.The batch request was submitted to the indicated queue.Rules to execute from a different library % are foundYou selected one or more rules to execute from the named library, so you cannot select another rule to execute in the current library.Do not select a rule to execute in the current library.RULESMGR ERROR - Initialization failed with code %The Rules Manager failed to initialize correctly. The error code displayed indicates the type of failure.
• RULESMGR ERROR - RULES BUFFER OVERFLOWThe shared rules binding area is full and no more rules can be bound.Increase the size of the rules binding area and/or recycle the Execution Environment.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |