![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
You used a WHERE clause to pass arguments to a rule, but one argument name does not correspond to any argument of the rule.Names of Object Service Broker objects must meet specific requirements (type/syntax).Name has been changed - Unable to DELETE object set "%"You cannot delete an object set in the Object Set Definer if you have changed the name that appears at the top of the screen of the object set.If you want to delete the object set, you must first exit the Object Set Definer, reenter it with the name of the object set to be deleted, and then delete it by pressing <PF22>.Name has been changed - Unable to delete report "%"The user tried to both rename and delete a report.Either rename or delete the report, but do not do both.NAME OF COUNTFIELD must exist in the ADABAS file definitionThe countfield you specified does not exist in the ADABAS file definition.Specify a valid ADABAS field name for the countfield.Name of Location parameter cannot be a Globalfield nameThe name of the location parameter in the table definition is defined as a global field. This is not allowed.Change the name of the location parameter to a valid MetaStor name that is not a global field.Need documentation for % before selecting itThe object selected for promoting or deleting requires documentation.Use the E object command to edit the summary. Save it before repeating the action.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.Nested FORALL statements access the indicated table; this is not supported.Eliminate nesting by using GETFIRST and GETNEXT to create a loop.Nesting of FORALL and/or UNTIL statements is too deepSeparate the loops within the rule, or across two or more rules.The object indicated in the message does not currently exist in the MetaStor.You changed the field name after entering the Field Manager. The change is accepted.Informs you that this field definition was not found in the global field dictionary.You can fill in the appropriate information and press <PF3> to add the field definition, or press <PF12> to cancel it.You attempted to use the blank area below the bottom of the history stack.Confirms that a new occurrence is being added to this table, in the Single Occurrence Editor.An error occurred when trying to find this rule to examine it for the given token.Attempt to edit the rule and save it. If a similar error occurs, contact TIBCO Support.The subschema being loaded is a new definition in Object Service Broker.NEW table definition... Select SUBSCHEMA and RECORDS firstThis is a new IDM table definition. The record access path must be selected first.Enter the SUBSCHEMA name and <PF6> to display the CA-IDMS records defined in the subschema.You can cancel (press <PF12>) this table definition and it will not exist, or you can proceed to define a table.NEXT BUFFER REQUESTED FROM DISPLAY OF LAST BUFFERYou are currently displaying the last buffer from a buffer list function. The next buffer request you requested cannot be honored.NLS check failed. Return Code=% for locale.codepage: %The NLS check that validates local.codepage failed. The return code indicates the reason.Review your NLS setup and verify the locale.codepages you specified are correct and supported by Object Service Broker.NLS translation failed due to an invalid or unknown configuration.Check the values in table @NLS1 and @SERVERCONFIG with parameters values "_NT" and "_NS". They must contain valid locale.codepage combinations.No. of parms in table % does not match with that on source systemThe number of parameters in the specified table does not match with the number on the target system, so the apply process cannot proceed as requested.On the source system, Unaccept the change and return it to the developer. The developer should roll back the change request and make the specified table compatible with the one on the target system. The change can then be re-extracted and reapplied to the target system.The % is replaced with one of the following:The message indicates that a request was not performed. The explanation precedes this message.No log is available for phase 1, 2, or 3. Logs are produced after each phase of the apply process. If for some reason the phase failed before a log could be produced, this message appears. It is usually accompanied by another message indicating which phase failed and the reason for the failure.See the message indicating which phase failed and the reason for failure, and take the appropriate action.An error was detected in an Object Service Broker statement that prevented the generation of the corresponding COBOL statements.Correct the Object Service Broker statement.You must use "S" to select one or more object types before pressing the key to select individual objects for promotion.Type "S" beside the object type(s) that you want to select and then press the key to select individual objects for promotion.No @RULESDOCUMENT entry exists for the ruleThe message log will contain a more detailed error message.
2. Contact TIBCO Support with the log and a description of what actions were being performed when this message was generated.No ACROSS-BY fields for body table "%" when TITLE COLUMNs or FINAL COLUMNs not zeroThe number of title columns and final columns must be zero unless the report is an Across Report.Use the Report Definer to do one of the following:
• Change the report to an Across Report by adding ACROSS-BY fields.You have used the DUMP (for instance, DUMP LOCAL) primary command to obtain a listing of some items. This provides feedback.This message indicates that there are no active tables.You requested to view the activity for a change request but none was found. This may occur if the activity has been deleted from the TDS table where it is stored.NO ALERT MESSAGE ON THE SYSTEM AT THIS TIMEThere are currently no alert-level messages to report.No authorization for Logon Library "%"; HOME library usedYou specified a Logon Library in your User Profile to which you do not have VIEW_DEFN permission. As a result, the session manager puts you in your home library at logon time.
• Obtain at least VIEW_DEFN permission for a logon library
• Remove the reference to this library from the LOGON LIBRARY field of your User Profile.No authorization for menu %, STANDARD is usedYou have a session menu specified in your User Profile for which you do not have proper authorization; therefore, the STANDARD session menu is displayed instead.Obtain the proper security authorization for the indicated session menu, or change the logon session menu to one for which you have proper authorization.You have used the OFF primary command to remove a specific break event. However, this break event had not been set. You may have misspelled the break event to be removed.Verify the spelling of the break event to be removed.You were in the FIELDS context looking at the list of CA-Datacom fields and you did not select any of the fields for inclusion into the definition.You are attempting to create a consolidated change request but there are no change requests on this system. A consolidated change request is one that contains other change requests. Since there are no change requests at this time, a consolidated change request cannot be defined.Do not create a consolidated change request at this time or choose a different source node for the included change requests.No change requests for the specified source node and locationThere are no change requests for the FROM and AT nodes specified on the query screen. This means that there is nothing to query given these nodes.Change the FROM and AT nodes for subsequent queries.You requested to query a given set of change requests but no matches were found.Verify that the FROM and AT nodes are correct. Also, check the selection criteria specified on the query screen. You may need to broaden the scope to find the change request(s) you are looking for.Before doing a target apply, the necessary change requests must be loaded from extract files. You have attempted to APPLY REQUESTS before any change requests have been loaded.Fill in the FROM CHANGE # and TO CHANGE # fields and select APPLY REQUESTS again.No rules had to be changed for the tokens you entered.Press PF2 and review the report. You may wish to change the tokens you entered.Example CHANGE x xThis may mean that your input is not correct. For instance, the FROM and TO tokens may be the same. Check that you have specified changes correctly.The preprocessor will not create further code for this command.No CONTROL TABLE entry for % object "%" (version=%)There is a problem with the object type definition data for one of the objects you requested to unload.Report this to your System Administrator as there should not be a problem with the object type definition data for unloadable object types.The table definition for the indicated report table cannot be found.This message indicates that no data was found in the table and so it was not cleared.No data in ACCESSLOG to purge/archive for dates:%-%You attempted to purge the audit log contents of a specified date range but that date range contained no data.Check the date range that you want to purge and try again.NO data LOADED in populated table because action is % %No data was loaded because the table already contained data and the action was IS.Since there are no data tables in the specified change request, you do not need to specify the backup options.There is no data on the screen so there is nothing to print.You attempted to print a report of the audit log but the audit log was empty and contained no data.NO DATA TO REPORT FOR SPECIFIED SEG, DSN AND START ENTThe segment data set and entry you specified are valid; however, there is data to be displayed.No default DATE mask defined or accessibleThe Object Service Broker tool $DATE_DEFAULT cannot find the default DATE mask due to one of following:
• LIST definition failed. No ADABAS definition found.Invoke utility @ADAEXTRACT to extract ADABAS definition into Object Service Broker before listing the definitions.No definition for "%.%" referenced by subview field "%.%"
• A source table field name was not specified for a subview field.
• The source table definition cannot be found for the subview field name.
• Specify a source table field name for the subview field.
• Modify or add the definition of the source table so that it contains the reference field used in the subview field.There is a problem with the object type definition data for one of the objects you requested to unload.Report this to your System Administrator as there should not be a problem with the object type definition data for unloadable object types.A non-existent table is specified in a table operation.
•
• Correct the pertinent rule, as indicated by the traceback, to reference an existing table.The screen name is not found in the table SCREENS.You cannot request the deletion of the table because you have the wrong type of promotion rights.You can get Definition Rights, which will allow you to request deletion of the table, by using the Table Definer.No definitions were loaded. Occurrences of tables, but not the definitions, may have been loaded, and will be mentioned by other messages.You issued the DELETE primary command but did not specify the document to be deleted.No eligible change requests exist for the selected source nodeYou are attempting to create a consolidated change request but the source node you selected for included change requests contains none that are eligible. Change requests must be promoted before they may be included in another change request.Promote change requests you wish to include before creating the consolidated change request.A request was made to delete a field from the global field dictionary. No such field existed in the dictionary.No field has been selected for SIXBUILDYou tried to prepare control cards for the S6BBRSIX/ hrnbrsix utility without selecting a field for secondary index building.No field to be CUT at the cursor positionYou pressed <PF5> to cut a field, but the cursor is not positioned on a field.Position the cursor on the field to be cut and press <PF5> again.No field to be CUT at the cursor positionYou pressed <PF5> to cut the field, but the cursor is not positioned on a field.Position the cursor on the field to be cut and press <PF5> again.No field to be DELETED at the cursor positionYou pressed <PF18> to delete a field, but the cursor is not positioned on a field.Position the cursor on the field to be deleted and press <PF18> again.No field to be DELETED at the cursor positionYou pressed <PF18> to delete a field, but the cursor is not positioned on a field.Position the cursor on the field to be deleted and press <PF18> again.No fields copied; relocate the cursor position.When you copy fields into the table, they are positioned beginning at the cursor position. You put the cursor into a position which did not allow enough room for the fields being copied.Repeat the command with the cursor in a position which accommodates all the fields being copied, or copy fewer or smaller fields.A table without fields was defined in a rule.Correct the table definition in the appropriate rule so that at least one field definition exists.No field entries can be found for the Model 204 table definition.Use the Table Definer to verify or recreate the table definition.The IMS table does not have any fields defined.The specified DB2 table does not have any fields defined.A COPY command was issued and a prompt of available fields was displayed. No fields were selected from this display.In the Screen Table Painter, you requested the loading of part of a table definition, but did not select any fields to be copied.You issued a request for Help, but no further Help exists.No IMS database definitions exist in the current MetaStor. IMS definitions must be imported into the MetaStor before any IMS tables can be defined.Contact the System Administrator to have an IMS database definition imported into the MetaStor through the IMS utility.NO IN-DOUBT TRANSACTIONS OUTSTANDING AT THIS TIMEYou requested the list of current in-doubt transactions. At the time the request was received, there were no in-doubt transactions and Fail Safe transactions in progress.No index on library "%"; press PF5 to build indexYou have entered the name of a library for which there is no index to search. You can build an index by pressing PF5. If the library is large, this may tie up your terminal for some time.If you want to search this library, press PF5 to build the index, or use another tool, such as SEARCHLIB, which does not use an index.You pressed <PF2> but there is nothing in the message logs.You specified a pattern and a parameter name and requested that any data instances which match the specification become selected in this screen. No instances were found that match your specification.Recheck the pattern you have specified as well as the parameter name you expect to find the pattern in. If they are correct, then there is no such instance.In INSTANCE SELECT you issued a FIND request after specifying the parameter and value to look for. No instances were found that match the request.The definition for the subview table does not contain a primary key.Modify the definition of the subview table so that it contains a primary key.This message is used by the Object Service Broker program that produces the Information Log.Study the Object Service Broker Information Log.You requested to view, print, or delete the logs for an activity on a change request but no logs were found. This will occur if the activity does not produce any logs (e.g., SAVE, SUBMIT). It will also occur if the SAVE LOGS flag in @PROM_CONSTANTS is not set. Finally, it may be that the logs have been deleted by your Promotion Administrator.Verify that the activity produces logs. Check the SAVE LOGS flag in @PROM_CONSTANTS for the activity and make sure it is set to Y.There are no optional manual sets involved with this record.No mask can be generated for field "%" of type "%" syntax "%"You selected a mask but placed the cursor on a nonnumeric field.Select a mask again and place the cursor on a numeric field.The segment that you selected with your cursor before you pressed <PF6> does not have any child segments. You have reached the bottom level of the current IMS access path.You pressed <PF2> but there is no other message log to display.Table definition exceeded the limit as indicated in the message. For example, you can only define one Address parameter in a MAP table definition.Reduce to the specified limit as indicated in the messageYou marked more than 4 DB2 fields with a P.No need to copy "%", source and destination are the sameThere is no need to copy the specified object because the source and the destination are the same.No need to copy % "%"; source and destination are the sameYou have specified the copy in such a way that an object will be copied to itself, resulting in no change. Therefore the object is not copied.No object of type % found to match requested nameYou requested a SEARCH in the Transfer Ownership screen, but nothing was found to match the requested pattern or name.No objects are found under this selection specificationYou are trying to search for objects that match the selection specification. No objects are found.The Object Manager found an empty list.No objects selected for promotion/deletionYou submitted a change request but did not select any rules, screens or reports for promotion or deletion.Specify at least one object to promote or delete. If you need more information about selecting objects, press <PF1> for Help or see the Promotions manual.No action required unless there are errors reported in other messages.States that a FIND or CHANGE command did not locate any occurrences.The FIND command that you issued did not locate any occurrences.You are trying to delete a table but the table is empty.A security violation occurred. The table occurrences cannot be loaded.Ensure that you have the proper security clearance for the objects that you are loading.
• The table, or the instance of a table, that you are attempting to browse or edit contains no occurrences.
• You have requested a selection which no occurrences satisfy.No option list is associated with the field where the cursor is placed.You requested a list of Screens referring to a specified screen table, but since the date given, no screens fit the description.Check again after a new Cross Reference has been run.When you use the COPY command, provide the source MetaStor IMS table name. Note that the source table must have a type of IMS; no other types are allowed.Enter the COPY command again followed by a valid MetaStor IMS table name.You did not select parameter values. UNLOAD will export all of the parameter values.Could not find the parameter tables associated with the object.Quit the tool, and make sure that the parameter tables exist.You pressed <PF9> to recall the previous command, but you have not yet entered a primary command in this session of the Search tool.You pressed <PF9> to recall the previous command, but you have not entered a command as yet.You have attempted to recall the last command when there have been no commands used on this screen yet.Use this PF key when there have been previous commands.You pressed <PF9> to recall the last command but there was no previous command to be recalled.You pressed <PF5> to repeat a FIND command, but did not enter a FIND command.You pressed <PF5> to find another occurrence, but you did not enter a FIND primary command in this session of the Search tool.You tried to recall a previous batch request, but you did not save any previous batch requests.You did not select a field to be the primary key for the MetaStor IMS table. The primary key field always has the order number 1.Use the S command to select the segment that contains the field that you want to designate as the primary key. On the next screen, which lists the fields for the segment, select the key field by entering a K next to it.The specified table is empty; therefore, nothing was printed.NO PRM table available to unload ALL INSTANCES of table "%"You have requested to unload data from a parameterized table. There is no PRM table defined which lists those instances, and therefore the data in the table cannot be unloaded.When data is to be unloaded from a parameterized table, there must be a PRM table defined to list the instances in that table. Also, you must have authorization to READ the contents of the PRM table so that it may be used for the unload.This message indicates that data could not be copied from a table with parameters since there is no PRM type table defined such that the table being copied is the source.To copy data from the parameterized table using this tool, you must first define a PRM table which has the table containing the data to be copied as the SOURCE table.No PRM table for %; cannot extract occurrencesCannot extract occurrences from a parameterized table without a PRM table for the specified table.No promotion rights/documentation for selected % %No rights or documentation exists for the specified rule.If no documentation exists, use the E line command; otherwise, contact the System Administrator.
• Current screen is where you entered S against the object type. You do not hold any promotion rights on any objects of the object type selected.
• Current screen is an object manager screen. You have entered an object command but no promotion rights are held for the named object.
• Case 1: Choose another type of object for which rights may be held.No prompt possible for table "%" - enter parametersYou entered the name of a parameterized table, but did not enter the parameters. You then pressed <PF5> or <PF6>. This table does not have a corresponding PRM table; therefore, prompting for parameters is not possible.The rule for this item is to be called, and a prompt rule is specified. At present, prompting is supported only for rules that are executed.Remove the prompt rule, or set the NEW_TRANS field to Y to execute the rule.No READ authorization for library; rule "%" was not executedYou specified a rule to execute at logon time, but you do not have READ access to the library in which the logon rule is stored. The library is probably a local library.
• From an authorized user, obtain READ permission for the library containing the rule, or remove the reference to the rule from your user profile.
• Possibly, you meant to execute a rule from the system or installation libraries, but this rule also exists in the logon library. In this case, select another logon library.No report media specified choose either printer, screen or fileYou attempted to generate an audit log report but you did not specify the output medium.Specify the output destination for the report and try again.NO RESOURCE NAME AVAILABLE TO IDENTIFY DESIRED DETAIL, USE TYPE LISTThe system did not have a Resource Detail entry name (type and group) to identify which desired entry to display. Step to the Detail display screen via the Type List.Select the detail entry by stepping through the Type and Group lists.No result set table definitions found, use Refresh to generateNo result set table definitions were found for this stored procedure.Use the Refresh button to generate the result set table definitions.In order to describe result set cursors the stored procedure must return a result setNo rights for "%" type "%"; rights held by %, requestor %You tried to perform one of the following operations on an object: OBTAIN all rights, RELEASE all rights, or TRANSFER all rights. However, the promotion rights for the object are held by other users and therefore the operation on the object failed.Contact the person who has the rights and, if available, have the rights transferred.No room after this definition to INSERT a new fieldYou pressed <PF6> to add a field but there is no room to add a field where the cursor is positioned.Put the field elsewhere, or move the other fields to allow the field to be inserted.No room in physical record to insert occurrence of table "%"There is no room to insert an occurrence of the child VSAM table into the physical record.Correct the rule which tries to insert the occurrence.You have pressed <PF14> (EXPAND) after reaching a break event where no rule is executing, for instance TRANSACTIONEND. This provides feedback.No rule name provided for derived field "%.%"A derivation rule has not been provided for a derived field.Using the Table Definer, supply a derivation rule name for the field specified in the message.The rule you are attempting to copy, append, or delete does not exist.Copy or append an existing rule. DELETE requires no action.You requested a display of the definition of a library that has no rules. This message is issued when the empty list of rules is displayed.You pressed <PF4>, but the list of rules to print was empty.To see a list of rules, ensure that the library name is the one that you want and press <Enter>.The screen for an existing menu no longer exists.No SecAdmin was selected; DISCLAIM function CANCELLEDThe security administrator made a request to disclaim the userid at the cursor position, but the administrator did not select a new SecAdmin for the user when prompted. The disclaim was canceled.Select a new security administrator for the user to be disclaimed.You have requested to unload an object; however, you do not have the appropriate security authorization to do so. For any object you specify, you will require at least VIEW_DEFN authorization; for data in a table, you will require both VIEW_DEFN and READ.You must remove the entry to complete the unload of any other objects you have specified. To unload the unauthorized object, you must obtain the required permissions from a person who is authorized to give them to you.No source "%.%" found for subview field "%.%"The subview field definition refers to a source field name which is not in the source table definition.Modify the source table definition so that it contains the source fields that are referred to in the subview field definition.A WHERE clause or stored subview selection refers to a subview field that does not exist in the source table.
• Remove the subview field reference in the WHERE clause or stored subview selection.
• Modify the subview field name in the WHERE clause or stored subview selection so that the field is contained in the source table definition.A calculation (CLC) table must have a field whose source (by the same name) is a secondary index.
• Change the CLC field name to one of the source fields that are secondary indexes.The field whose source is a secondary index should have no SOURCE, SOURCENAME and KEYTYPE in its FIELDS definition.A subview or parameter table has no source table.Add a source table name in the subview or parameter table.The rule specified has no actions and so cannot be saved.
• Insert at least one action line so that you can save the existing rule and exit the Rule Editor.
• Use the CANCEL command to exit the Rule Editor without saving the rule.No stored procedure result sets to describeThe DB2 table @SYSROUTINES indicated that this procedure has zero result setsYou specified an undefined JCL name on the batch submission screen.Correct the JCL name or press <PF2> to get a list of defined JCL names.One of the objects you have requested to unload included by reference another object. There is no such type as that specified by the reference.No action required; feedback only. You may want to report this to the System Administrator since this indicates that there are non-existent object types specified in some object type definition data referenced definitions.No SUMMARY-BY fields for body table "%" when ACROSS-BY fields presentAcross Reports must have at least one summarization field.Use the Report Definer to add a SUMMARY-BY field.<PF3> or <PF13> was pressed, but no table was specified for printing.No tables, screens, or reports have a unit name that matches the specified unit.You have pressed <PF5> to find next, or <PF6> to change next, before issuing a FIND or CHANGE command.Give a FIND or CHANGE command first, and then press <PF5> or <PF6>.No target specified for "FIND" commandYou pressed <PF5> to find the next occurrence before issuing a FIND command.Issue the FIND command first and then press <PF5> to find the next occurrence.Either <PF5> or <PF6> was pressed without first entering a FIND or CHANGE command.NO TDS LOCK FOR THE TRANSACTION BEING PROCESSEDThe logical lock request was processed successfully, but there were no logical locks to report.When TED is executed with null input, you see a list of your documents to choose from. You pressed <PF12> to exit without making a selection.The message log will contain a more detailed error message.
2. Contact TIBCO Support with the log and a description of what actions were being performed when this message was generated.You have specified a parameterized table. However, to determine what all the instances of that table are, a PRM table having the specified table as SOURCE must be defined.Define a PRM type table having the parameterized table as a source and then reattempt the operation.You tried to change the definition of a parameterized dictionary table.Do not update dictionary table definitions.No updates allowed on TABLES entry for dictionary table "%"You tried to change the Table of Tables occurrence of a dictionary table.Do not update dictionary table definitions by varying corresponding TABLES occurrences.Informs you that you have pressed <PF3>, or entered the SAVE command, without having made any updates to the table or the occurrence.You tried to log on to Object Service Broker with a userid that has no user profile.Contact the System Administrator to correct or add your Object Service Broker userid.NO USER SESSIONS CURRENTLY ACTIVEYou requested a list of all active Execution Environment connections; at this point in time there are no connections present.No valid destination specified for MOVE/COPY commandYou positioned the cursor in an area where the lines to be moved or copied cannot be placed.Use the cursor or line commands A or B (After or Before), to indicate where the lines are to be moved or copied.No prompt values were found that meet the selection criteria specified.You pressed <PF15> when no Windows were open.Source nodename supplied for Target Promotion matches nodename of target system.Either use Source Promotion or correct Source nodename.Non-paired SO/SI in syntax W (DBCS) field "%"The syntax W field string value has non-matching shift-out/shift-in control character pair.Check for matching SO/SI, unintentionally SO/SI (hex 0F/0E) characters. You may also remove all SO/SI if only single-byte characters are to be displayed.Non-updateable fields must be immediately after the key fieldsThe ordering of your nonupdateable fields is invalid.Define nonupdateable fields right after key fields.Non IDgen M204 table cannot have any data parmsOnly IDgen M204 tables can contain parameters.If you want the data parameter, make the table an IDgen table. Otherwise remove the data parameter.PF9=SP_RSET is only usable for stored procedure table definitions.Not able to locate or start the Execution EnvironmentCheck the Execution Environment parameters.You specified an invalid security group on the batch request submission screen.Not allowed to delete batch queue definitionYou do not have the authority to delete the definition of a batch queue. Only users in the security group ADMIN are allowed to delete queue definitions.Not cleared to use current group at remote locationA distributed data request was attempted but the local group, userid and/or password is not valid at the remote location.Either retry using a userid/password/group combination that is valid at the remote location or arrange for the security administrator of the remote location to provide a valid combination.There is insufficient storage to hold the table data.
• Delete occurrences that are no longer needed in tables of the type displayed in this error message.
• Increase the relevant Execution Environment storage parameter value.Not enough "%" table directory space to bind table %The internal table of EES/session tables is full.
• Change the value of the TAMBSTS Execution Environment parameter to increase the available space.The storage where bound table definitions and data are placed is full.
• Change the REGIONTABLESIZE Execution Environment parameter to increase the available memory.Not enough storage to bind fixed definition for "%"The indicated screen requested FIXED storage, but not enough storage was available to bind it.Reset the bind for the screen or increase the Execution Environment REGIONTABLESIZE parameter.The storage where TEM tables are placed is full.
• Change the value of the TRANMEMMAX Execution Environment parameter to provide more space.NOTE: definition modes can be set only when ALL DATA="Y"You are managing permissions for a table instance and you tried to set definition permissions from this screen. When you specify a table instance, only the data permissions are effective (READ, INSERT, REPLACE, DELETE). Definition permissions to a parameterized table can be set only when ALL_DATA is Y.Specify appropriate data permissions in this screen and then either update definition permissions for the whole table, or have an authorized user do so. NOTE: If a user is given INSERT access to a table instance, and the user does not have VIEW_DEFN access for the whole table, the user cannot insert into that table instance.NOTE: definition modes must be set with ALLDATA=YYou made a request to manage permissions for a table instance, and only data modes apply. If definition permissions are to be managed, these should be done for the whole table. Note that any users or groups who are given data permissions to an instance must have at least VIEW_DEFN set to Y for the whole table permission.Set data modes only in this screen, and ensure that the definition modes are set in the screen for the whole table.NOTE: layout of LOADED screen tables remains unchangedIn the Screen Table Painter, you loaded a table definition with a table type of SCR. This message reminds you that the layout of the loaded screen table stays as defined in its stored screen table definition.NOTE: Press <PF14> for permissions LOST when object set ENABLEDYou just saved an object set enable list when the object set was not previously enabled; any permissions on free objects in the object set are wiped out of the permissions lists. A report on permissions lost in this way is available by immediately pressing <PF14> from the main menu.You can ignore this message, or press <PF14> to view and perhaps print the report on lost permissions.NOTE: Type % tables have no DATA; set DEFINITION modes onlyYou made a request to manage permissions to a table, and the table type is TEM, SCR or RPT. Since these tables have no data in the table data store, only the definition modes can be set.NOTE: You are viewing a list of the rules in library "%"You made a request to view the definition of a library, and the first screen shows the list of rules in the library.Nothing has been selected for TRANSFER; to exit use CANCELIn the Transfer Ownership screen, you made a request to TRANSFER&EXIT, but did not select any objects to transfer.Either select an object to transfer, or cancel the operation.No objects are entered for comparison.NULL can not be involved in an expression with %The specified field cannot support NULL values; therefore, the expression cannot be allowed.Change the definition of the field or change the expression.The user tried to issue an INSERT or DELETE operation for an occurrence that has a null primary or secondary key.Modify the occurrence to contain a non-null primary key.You have not specified a primary key value for this occurrence (and blanks are considered Null for a field of syntax C.)Null value detected for % OF-FIELD "%" in report "%"The Of-Field of a TOTAL or AVERAGE report function was null.Review input data for the field of the report. If null values are possible, but a total or average is required, use a selection string on the report function to exclude null values.Number of columns on a page too small to produce report "%"The page width of the report is too small to display the title column or the final column areas of an Across Report.Increase the page width to accommodate the minimum required number of columns, or use the $RPTPARMS tool to change the width in the rule that prints the report.Number of conditions exceeds maximum of %Number of conditions exceeds maximum allowed in a rule.Number of data parameters cannot be more than 4 per tableYou have defined more than 4 data parameters for this table and this is not allowed.Number of decimal places must be 0 for packed field length < 4In the Screen Table Painter, you defined a packed field with a length of less than 4 and a nonzero number of decimal places.
• Change the syntax of the field to allow for the number of decimal places required
• Change the length of the field to allow for required decimal placesNumber of digit selectors in mask is greater than 15You have used more than 15 digit placeholders in a MASK specification.Number of IDMS records in this subschema: %The number of records in a subschema is indicated when you select a subschema from the list of IDMS databases defined in Object Service Broker.The number of IDMS databases (subschemas) defined in Object Service Broker is indicated when you select one of the following the menu options from the Object Service Broker/IDMS Manager Utility:The indicated number is the number of IDMS tables currently defined in the system.The indicated number is the number of IMS databases currently defined in the system.Number of lowest title line "#" + number of highest footing line "#" + 1 is not < page length "#" after call to "%"Any line above the lowest title line is considered a title line; likewise, any line below the highest footing line is considered a footing line.Reduce the number of title or footing lines. If you have less than 28 of these lines, increase the page length.Errors were encountered when attempting to rebind some objects.Review the output of @PROMBINDOBJS for list of objects not rebound and the reasons for the failures. Resolve the reasons for the failures and re-run @PROMBINDOBJS.Errors were encountered when attempting to unbind some objects.Review the output of @PROMUNBINDOBJS for a list of objects not unbound and the reason for the failure. If you require these objects to be unbound, resolve the reasons for the failures then run @PROMBINDOBJS and re-run @PROMUNBINDOBJS.Number of parms must be % for source table "%"You specified too many or too few parameters for the indicated source table.Specify the indicated number of parameters for the source table.Number of rows on a page too small to produce report "%"The page length defined in the report is too small to allow the report to be printed.Increase the page length to allow the printing of at least one body report table on a report page.You entered a negative value in the duration field. The valid range is from 0 to 32400.Number of TITLE ROWS required for this table is "%"A titles report table (TITLE ONLY=Y) must define every row that has a report field as a title row.Change the number of TITLE ROWS to the number specified in the message.Numbering for entries must be consecutive: 1..%You are supposed to assign consecutive numbering to the list of entries on the screen; however, the numbering is not consecutive.The entries should be numbered so that there are no gaps in the numbering.Numbers of %s loaded and defined differ for table "%"The table definition or the processed program was modified since the last pass through the preprocessor.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |