![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Largest positive ROW must be for body; use a negative rowAny report tables with a positive row origin must be printed above the body report table. In other words, the row origin of the report table must be less than the row origin of the body report table.If you want to print the report table below the body report table, change the ROW specified to a negative number. The number indicates the row offset relative to the bottom of the report page (e.g., row -1 represents the bottom line on a page).This message warns you that the indicated number of columns will be truncated from the document when the document is saved.Confirm whether the truncation is acceptable or adjust the document accordingly if you do not want it to be truncated.This message is used by the Object Service Broker program that produces the Information Log.Study the Object Service Broker Information Log.You pressed <PF1> until you reached the left edge of the displayable information. No more information exists to the left of the screen you are viewing.You have requested to page left and the screen is already at the left border.Length + pos - 1 is "#" for "%", it must be <= print width which is "#"The sum of the POS and LENGTH arguments for $PRINTFIELD must be less than the print width.Length argument extends beyond end of buffer - length=#,buflen=#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.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 valid lengths for a MetaStor floating point field are 4, 8, or 16.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.LENGTH field is insufficient for mask "%"; need length of %The specified display mask extends beyond the length of the field.Either increase the length of the field or adjust the display mask to the existing length.The length for a MetaStor logical field must be 1.Length must be between 1 and 12 for syntax BThe length for a MetaStor binary field must be either 2 or 4.Length must be between 1 and 16 for syntax PThe length for a MetaStor packed decimal field must be between 1 and 8.Length must be positive for % % of dynamically created table %The length you specified for the indicated Field or parameter is negative.LENGTH MUST BE STRICTLY POSITIVEInternal 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.Length of "%" cannot be null for offset calculationExternal length must be entered for offset calculation.Specify starting length for offset calculation.Length of # specified for function PAD exceeds the current maximum permissible value of #The length specified for the output string is larger than the current maximum permissible value.Either specify a smaller value for the length, or increase the session parameter EXECSTACKSIZE to allow for larger strings. The maximum permissible value of the length for PAD is approximately (EXECSTACKSIZE - 32K). Note that if the result of PAD is to be assigned to a local variable, the value of the session parameter EXECLOCALSIZE may need to be increased as well.Specify new value with correct length as specified in the message.Length of 2 or 4 required with Binary syntax for % % of dynamically created table %The indicated Field or Parameter is of syntax BINARY and of length other than 2 or 4.Consult the Managing Data manual for information about valid representations of numerical data.Length of 4/8/16 required with Float syntax for % % of dynamically created table %The indicated Field or Parameter is of syntax FLOAT and length other than 4, 8, or 16.Consult the Managing Data manual for information about valid representations of numerical data.LENGTH OF A BINARY NUMBER MUST BE <= 4Internal 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.LENGTH OF A FLOATING POINT NUMBER MUST BE 4, 8 OR 16Internal 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.LENGTH OF A PACKED NUMBER MUST BE <= 8Internal 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.Length of argument for rule "%" too long for an asynchronous eventThe operating system imposes a limit on the total size of the arguments of a rule to be run in batch (by using the SCHEDULE statement). This limit was exceeded.The length of the indicated binary field is not 2 or 4.Change the length of the indicated field to 2 or 4. If the length is 2, the field can store numbers from -32,768 to 32,767. If the length is 4, the field can store numbers from -2,147,483,648 to 2,147,483,647.The user specified a length that is outside the bounds for the field syntax. This message continues:Example = %, is above the range %:%Example = %, is below the range %:%Change the length to a number within the bounds specified in the error message.You did not specify 4, 8, or 16 as the length for a floating point field.Change the length of the indicated field to 4, 8, or 16. The lengths correspond to 24, 56, or 112 binary digits of precision.You entered a length for a logical field that is not equal to 1. This message continues:Example = %, is above the range 1:1Example = %, is below the range 1:1The defined length of the parameter is greater than 127.Correct the length parameter in the table definition so that it is less than or equal to 127 bytes.Strings cannot contain more than 32767 characters.Verify that no string can become larger than 32767 characters.Length of title/footing for "%" is # and must be <= #The arguments L, C and R of $SETP#POS or $SETTITLE cannot have a total length that exceeds the print width or 132, whichever is smaller.LENGTH operand of the SUBSTRING function goes beyond the end of the stringInternal 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.LENGTH operand of the SUBSTRING function is a negative numberInternal 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.Level 7 clearance required to use PAGE_STATS or PAGE_ENTRYThese Object Service Broker routines require level-7 security clearance.Request that your system administrator run the affected rule.Libraries permissions for object set will be committed on SAVEYou saved library permissions specifications for an object set.No action required. To cancel any changes made to library permissions for an object set, you must cancel from the object set definition screen.Library "%" cannot be referred to more than onceYou referred to a particular library more than once while specifying library permissions for an Object set definition.Remove duplicate entries from the list by replacing the library name with blanks, nulls, or another library name.You referred to a non-existent library.No action required unless you have to remove the reference.Library "%" was defined since create user began; cannot SAVEA Security Administrator is trying to create a userid, but since this request was initiated, someone has created a library of the same name as the userid being created. The home library cannot be created for the userid.You must cancel and restart with a new userid, or you can have the created library renamed by authorized individuals.Library % is empty; no changes to cross reference.The library named in the call to REFMAKER is empty. No changes have been made to the existing cross reference.Library % is not defined; you are in your HOME library, %You specified a logon library that existed at the time of the specification, but does not exist at the time of this logon. Since the library no longer exists, the session manager puts you into your home library at logon.A recommended action is to remove the non-existent library reference from your User Profile Logon Library.You attempted to set the current library field in the workbench to a library that does not exist.Replace the name of the non-existent library with an existing library, preferably one for which you have at least VIEW_DEFN authorization.The library was copied successfully. The source library should contain the number of rules indicated as copied in the message.Library definition and rules in library "%" DELETEDYou requested and confirmed the deletion of a library.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.LIBRARY is required for %, which can include %SYou have requested to unload an object which includes rules by reference. You must specify from which LIBRARY the referenced rules should be unloaded.In the top area of the screen, type in the LIBRARY which should be used as the source of these referenced rules.The library name entered cannot be a source library for promotions, or a rollback library.You entered a rule name but did not enter a library name.On the first line beneath Rules in Library, type in a valid library name.Library names can only be eight characters longA library name cannot exceed 8 characters in length.Retype the library name, up to 8 characters.There is no library name on the screen.Enter the name of the library containing the rules you want changed.You specified a negative number in the limit field of the queue definition screen.You entered an invalid line command.Enter a valid line command; you can press <PF1> for a list of valid line commands.The output line is set too long for the field in the destination table. This length is the sum of the adjust and linelength parameters.Check the most recent .setup, .ll, or .ad commands for specifying too large a value for linelength or adjust. There is a .setup default implied if no actual .setup command appears at the start of the document.The top and bottom can each fit only three lines which are numbered 1, 2, and 3.Line position must be T=top or B=bottomTitle lines must appear at the top or bottom of the screen.Link to the sort program failed. For diagnostic purposes, the module to which the link was directed and the return code are supplied.Call your system administrator to ensure that the module being linked to is available and to check the return code in Register 15 against the appropriate vendor's manual. Correct the problem as required.The interface for listing tables and/or columns from external DBMS has not been defined.Invoke the "Define list tbl/col interface" option in GENDT to define the LIST interface.One or both of the TDS tables @COLOURS and @SCREENCOLOURS cannot be accessed during initialization of the list of valid screen colors.You pressed <PF13> to print the list of objects.Lists do not contain the same number of objects (out of synch)You are trying to compare two lists of objects but the number of objects in these two lists is not the same.Insert the missing objects or remove the extra objects and try again.Literal '%' contains a word which spans the fixed columnsThe specified literal contains a word that extends beyond the fixed column boundary.Either adjust the fixed columns to include the interfering word, or adjust the literal to fit within the fixed columns.Literal text cannot start in the first column of Image AreaYou have entered literal text which starts in the first column of the Image Area.Either move, or remove, the character(s) in the first column.The subschema definition identified in the import files has been loaded into the Object Service Broker/IDMS dictionary tables.A system error occurred during the LOAD process.Press <PF2> to view the error messages. Print the log file and contact TIBCO Support.Load of definition of table "%" will cause nested FORALLInternal error. You used a system table in a FORALL statement, then attempted to access the table again within the FORALL loop.
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.Load of VSAM table "%" exit routine "%" failedThe indicated exit routine cannot be loaded from the library of external routines.Make sure that the exit routine exists as an executable load module in a library that is currently allocated to Object Service Broker.Loaded % Tbls % Scrs % Rpts % Rules % Objsets % MenusThe specified number of objects were loaded.The specified number of objects were loaded as a result of applying the change to the system.This is an informational message that indicates what is being loaded (the definition, occurrences, or both definition and occurrences), the type of object (table, screen, rule or report), and the object name.Definitions and occurrences of the named tables were loaded.The definitions of the named tables were loaded.Definitions of the named objects were loaded. When tables are named, this message implies that only the definition and not the occurrences of the table was loaded.Definitions of the named objects were loaded. When this message names a table, it implies that only the definition and no occurrences was loaded.Occurrences only were loaded for the named tables.Local Variable "%" has not been declaredYou have tried to list (or set) a local variable which has not yet been declared by your application.Verify the spelling of the local variable to be listed (or set).You assigned a value to a local variable that you did not define.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 created too many local variables in one transaction, or the variables use up too much storage. This message may indicate an infinite loop or a recursion that is too deep.Verify that recursion does not get out of control. Try increasing the value of the EE parameter EXECLOCALSIZEThe Locale of the locale.codepage combination is invalid.Location parameter "%", cannot be used in the selectionfieldLocation parameter is referenced in the Selection string which is invalid.Remove location parameter reference in Selection string.Location parameter is not allowed for "%" table typeYou defined a location parameter for the specified table type for which location parameter is not supported.Remove the location parameter in the table definition.Location parameter is not last parameter in dynamically created table %In @DOFPARMS, you assigned a CLASS of "L" to a parameter other than the last.Ensure that only the last Parameter is given a CLASS of "L".The location parameter must be defined with a semantic type of I, a syntax of C, and a length of 16.Specify the attributes of the location parameter accordingly.You have tried to save a minimal definition but you have not specified the location parameter.The update operation "%" failed for this EES table. The row has been modified between fetch and update operations. A LOCKFAIL signal is raised.If there is a need to update this EES table row, refetch and update the row again, else fail the transaction. See the Managing Data manual for details of the lock processing on EES tables.Internal error. % represents a table name. The table named, which is required by the tool, is locked by another user.Try again. If the problem persists contact your System Administrator to determine who is holding the lock.Check for locking on the table and retry when the lock is released.LOCK MANAGER STATISTICS RETRIEVAL ERRORThe attempt to retrieve the statistics for the lock manager display failed.Review the message log for possible additional information. Retry the request. If a problem persists contact the support center.Lock request blocked for TABLE=% by self (parent/child deadlock)The user was executing a transaction which started another transaction or transactions. The child transaction required share or exclusive lock(s) on the table name displayed and/or a key or table instance of it. A parent transaction had previously obtained lock(s) on these resources, so the child transaction's lock request is blocked. This information message is returned to the blocked user's terminal. The LOCKFAIL exception is raised and the transaction is terminated.To prevent this deadlock, you may need to make changes to one or more the Object Service Broker rules which are being executed.Lock request blocked for TABLE=% by USER=% (upgrade deadlock) <on NODE=%>A rule executed by the user had previously obtained lock(s) on the table name displayed and/or a key or table instance of it. This rule now requires a stronger lock on at least one of these resources due to a more exclusive rule statement (e.g., first GET, then REPLACE), or because the user's lock count has reached an escalation threshold while the lock manager was running short of free lock buffers.Another user or users had previously obtained locks on these resources and these locks are currently being retained, so this upgrade request is blocked. The resource contention situation is already sufficiently complex (other transactions queued) that waiting is not expected to succeed. This information message is returned to the blocked user's terminal. The LOCKFAIL exception is raised and the transaction terminated. If the blocking user is from a remote node, the NODE name is appended to the message.If there is an immediate need to complete the failed transaction, then the blocked user should contact the blocking user to arrange the release of the table/resource in contention. Contention situations can be resolved more permanently by making appropriate changes to the rules and/or table definitions. Escalation can be postponed by increasing the size of the lock buffer pool specified, using the LOCKBUFFERS Data Object Broker parameter.Lock request blocked for TABLE=% by USER=% <on NODE=%>A rule executed by the user required share or exclusive lock(s) on the table name displayed and/or a key or table instance of it. Another user or users had previously obtained locks on these resources and the locks are still retained, so the new request is blocked. The blocked user's lock request may have waited without success, or failed without waiting due to a complex wait queue or because the blocker was a long-running transaction. This information message is returned to the blocked user's terminal. The LOCKFAIL exception is raised and the transaction terminated. If the blocking user is from a remote node the NODE name is appended to the message.If there is an immediate need to complete the failed transaction, the blocked user should contact the blocking user to arrange the release of the table/resource in contention. Contention situations can be resolved more permanently by making appropriate changes to the rules and/or table definitions.If the user is displayed as IN*DOUBT, a transaction is being held in pending status. To investigate why the transaction did not complete successfully, use the Administration Menu, IN-DOUBT TRANSACTIONS option. For more information on the Administration Menu, refer to the Object Service Broker Installing and Operating manual for your platform.LOCK REQUEST BLOCKED FOR TABLE=% BY USERID=%Another user or another transaction for this user has locked the requested occurrence or table.Access to a certain system table was blocked by another transaction.Repeat the function you were trying to invoke when you received this message.You encountered a locking problem.You tried to save your editing changes to keywords for an object, but another user has blocked you from saving your changes.
• Wait until the other user is finished, then save your changes
• Press the CANCEL PF key, which takes you out of editing mode.The current action cannot be performed because someone else is holding a lock on the indicated table.The report indicated cannot be changed because of a lockfail. Someone else is holding a lock on the report.LOCKFAIL - lock request for report table "%" blockedThe lock for the indicated report table is being held by another user.Access to the indicated table is blocked by another transaction.A locking error occurred on an insert to @PROMUNBOUNDOBJS and the @PROMUNBINDOBJS tool terminated.Resolve the error specified and run @PROMBINDOBJS before re-running @PROMUNBINDOBJS.LOCKFAIL on table @BORROWED_OBJYou cannot get the promotion rights.Lockfail on TABLES; unable to locate PRM table for %The TABLES table is locked. As a result, the parameter table for the specified table cannot be accessed.LOCKS COULD NOT BE FOUND FOR TRANSACTION XXXXXXXXNo logical locks for the specified transaction when you attempted to zoom in on the detailed list to the selected stream.You pressed <PF13> and the message log you are viewing was printed.You have defined a field to have a "Typ" of Logical but defined its length to be greater than 1, which is the maximum valid length for this Type.Change the field length to 1, or change the syntax.Logical type requires Length = 1 for % % of dynamically created table %The indicated Field or Parameter is of semantic type LOGICAL and of length other than 1.Logoff from SYSTEM % by % from environment ID %A user with the specified external environment user ID logged off of the specified Object Service Broker system.Logon failed: Access prevented for userid at this time: userid "%"You attempted to log on, but the logon restriction parameters in your user profile prevent you from logging on at this time.Contact your Security Administrator or try again later.Logon failed: Invalid userid for logon used: userid "%"You attempted to log on with an invalid userid.Try again with a valid userid or contact your Security Administrator.Logon failed: null SESSION MENU, START RULE & "R" keyword parmYou requested to log on, but did not specify the RULE keyword parameter. Since the User Profile does not have a Session Menu or Logon Startup Rule specified, the logon cannot proceed past authorization.Either specify a rule with the RULE (R) keyword parameter, or have your Security Administrator specify a Session Menu or a Logon Startup Rule in your User Profile.Logon failed: Userid not defined to system: userid "%"The logon failed because the specified identifier is not defined in the MetaStor.Either define the identifier to the MetaStor using the Security Manager interface, or attempt to log on with a different identifier.You canceled your logon request from the Password panel.Logon Restrict "%" parameter is not a valid time (HHMM)A Security Administrator supplied an invalid time in the User Profile. The supplied value is not in the valid range for hours and minutes of the form HHMM. For example, 2655 is invalid, and 1528 is valid.Correct the time to be a valid time in the form HHMM.Logon Restrict parameters indicate logon will always be deniedA Security Administrator updated a user's profile so that the Logon Restrict parameters are equal and nonzero (e.g., 1145 to 1145). These values never allow a user to log on. 0 to 0 is accepted to mean that the user is never restricted from logging on. 0 to 945 indicates that the user cannot logon between midnight and 9:45 a.m.Only Data Object Broker operator sessions are valid at this point in time.Resubmit the session when the environment is ready.Logon Rule was not executed because it was not foundYou just logged on and the rule to execute at logon, as specified in your User Profile, is not in the local, installation, or system libraries.Remove the reference to a non-existent rule, or ensure that the rule exists in the local, installation, or system library.Logon to SYSTEM % by % from environment ID % denied: incorrect passwordThe specified external environment user ID attempted to log on to the specified Object Service Broker system but did not use the correct password for the Object Service Broker userid.The user must retry with the correct password or consult the security administrator.Logon to SYSTEM % by % from environment ID % denied: restricted time windowThe user attempted to log on within the restricted time boundaries set in the user's profile. The user is not permitted to log on within these times.The user must log on to TIBCO Object Service Broker within the allowed time range or consult the Security Administrator.Logon to SYSTEM % by % from environment ID % denied: user is not "real user"The password associated with the Object Service Broker userid that the user tried to use is blank. Because the password is blank, the following must be satisfied in order for the user to log on to Object Service Broker:
• The EXTERNALSECURITY parameter should be set to something other than Internal.
• The user's external environment user ID and Object Service Broker userid must be the same.
• Log on to Object Service Broker from an account where the external environment user ID matches the Object Service Broker userid.
• Ask the security administrator to change the password to a non-blank value.Logon to SYSTEM % by % from environment ID % denied: user is suspendedThe security clearance is zero for the specified userid. The user cannot log on to the Object Service Broker system.If the user needs access to Object Service Broker, the user should contact a security administrator to have the security clearance changed.Logon to SYSTEM % by % from environment ID % denied: user undefinedA user tried to log on to the specified Object Service Broker system from the specified external environment user ID, but the Object Service Broker userid is not valid.The user must use a userid and password that Object Service Broker recognizes. See the External Environments for z/OS manual for more information about logging on to Object Service Broker with the USERID and PASSWORD parameters.Logon to SYSTEM % by % with clearance % from environment ID %A user logged on to the specified Object Service Broker system using the specified external environment user ID and the specified clearance level. The user passed the userid and password security check.Lowest title line "#" > highest footing line "#" or more than 28 title/footing/page number lines 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.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |