![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
S6BTLADM INITIALIZATION FAILED - INSUFFICIENT STORAGEWhen you started your administration session there was not enough storage available to you to fulfill the requirements of the utility.Increase the region size of your TSO session. It may be beneficial to invoke the administrator from native TSO, (from the ready prompt).Same field number defaults for "%" and "%" of subview "%"Two subview fields specify the same source field name.Change one of the source field names to a different source field in the subview table definition.An error was encountered during the saving of a queue definition.An error was encountered when a batch request was saved.SAVE failed - too many report tables specified for reportThe current definition of the report cannot hold all the specified report tables.Remove the report tables from the report definition until the save can be performed.SAVE not permitted; use <PF12> to cancel and exitYou made a request to save when saving is not allowed due to authorization restrictions.Your request to save the object set would have involved overwriting an existing object set. You have decided that this is not what you desire and have thus canceled the save.Change the name of the object set to the desired name and perform the save again.Informational only. You have canceled your request to overwrite a screen table definition.Your request to save has been canceled.Before defining result set tables you must save the stored procedure definition.You have requested to save changes to core information about a MetaStor table you are defining using the generic Table Definer.SAVED changes to definition of DAT table "%"You requested to SAVE any changes made to the definition of the DAT table. This confirms that the changes were saved.You made changes to the library definition and saved them.SAVED changes to EXTENSION informationYou have requested to save the extension specification for the MetaStor table you are defining. If you save the table definition, the extensions specification you saved will be committed.You saved the definition of a newly-created library.You have specified which instances for a table should be selected for unloading using the INSTANCE SELECT function. Your specification was saved. If you press <PF3> from this screen, the instances selected for the table will be unloaded.Scanned % rules; press PF2 for more informationThe scanning has completed after examining the stated number of rules.SCHEDULE ASSOCIATION ATTEMPT FAILED, RESOURCE type group IS NOT DEFINEDYou attempted to associate the displayed schedule to a Resource Detail entry that is not defined to the system.SCHEDULE DELETE CANNOT BE PERFORMED BECAUSE THE SCHEDULE IS IN USEYou requested to remove the displayed schedule from the system (PF11) but the schedule is currently in use by one or more Resource Detail entries.From the Schedule Index display screen, position the cursor on the current schedule and press PF9 to determine which Resource Detail entries are currently using the schedule. Either associate those Detail entries to other schedules or retain the schedule you attempted to delete.Schedule of rule "%" failed - cannot find default model JCL for batch jobInternal 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.Schedule of rule "%" failed - could not create process, error code %An attempt to spawn a process used to schedule a batch job failed. Likely causes are that a system-imposed limit was reached for the number of processes that may be executed by a single user, or the system is low on virtual memory.Kill unnecessary processes that may be running on the system. Increase physical memory and swap-file space.Schedule of rule "%" failed - could not open file, error code %An attempt to open a disk file failed. Likely causes are exhaustion of file descriptors or disk full conditions.Decrease the value specified for the MAXSESSION parameter. Increase the amount of free disk space available for the directory specified by the TEMPUNIT parameter.Schedule of rule "%" failed - could not open stream, error code %An attempt to allocate a buffered I/O stream failed. The most likely cause is the exhaustion of buffered I/O stream resources.Decrease the value specified for the MAXSESSION parameter.Schedule of rule "%" failed - insert in "%(%)" rejectedYou have too many SCHEDULE TO statements in a given transaction.Intersperse a few COMMIT statements, or distribute the SCHEDULE statements among several transactions.Schedule of rule "%" failed - JCL card overflow- "%"Various limits apply to the arguments of a rule when you invoke it with the SCHEDULE statement; one of these limits was exceeded.Schedule of rule "%" failed - job submission failed, exit code %The at(1) command used to schedule the batch job exited with a nonzero exit code.Schedule of rule "%" failed - job submission failed, signal %The at(1) command used to schedule the batch job terminated abnormally as a result of the given signal.Schedule of rule "%" failed - rule parameters too long for batch JCLVarious limits apply to the arguments of a rule when you invoke it with the SCHEDULE statement; one of these limits was exceeded.Schedule of rule "%" failed - write to file failedAn attempt to write to a file on disk failed. Likely causes are disk full conditions.Increase the amount of free disk space available for the directory specified by the TEMPUNIT parameter.Schedule of rule ";" failed - cannot evaluate ";"You have used a SCHEDULE statement referring to a @SCHEDULEMODEL containing a user-defined variable, typically a field of a table. Either the field value cannot be retrieved or the value is too big.Verify the spelling of the field, table names. Verify the size of the returned value.Schedule of rule ";" failed - Password decryption exit not installedThe SCHEDULE_MODEL facility encountered a substitution variable for a password. The current password was in an encrypted format, and the site decryption exit has not been installed.Check with your site administrator to determine the cause and recommended action.Schedule of rule ";" failed - Password decryption rejected by exitThe SCHEDULE_MODEL facility encountered a substitution variable for a password. The current password was in an encrypted format, and the site decryption exit rejected the decryption call.Check with your site administrator to determine the cause and recommended action.SCHEDULE schedule HAS BEEN DELETED SUCCESSFULLYThis message is to acknowledge that the schedule you requested has been removed from the repository.SCHEDULE schedule IS CURRENTLY NOT ASSOCIATED WITH ANY RESOURCESWhen attempting to retrieve the list of resources which use the specified schedule it was determined there were none.SCHEDULE schedule SUCCESSFULLY ASSOCIATED WITH RESOURCE type groupThis message is to acknowledge the successful completion of the requested association of the specified schedule to the specified Resource Detail entry.Schedule statement failed; dynamic allocation failed with RC=% ERRCODE=% INFOCODE=%Internal error. The message log contains a more detailed error message.
2. For an explanation of the codes, refer to the appropriate IBM manual for the SVC99 error codes.
3. Contact your site's system programmer for assistance.If additional assistance is required contact TIBCO Support with the log and a description of the actions performed before the message was displayed.SCHEDULE TO BE DELETED DOES NOT EXIST IN THE REPOSITORYIn the Resource Manager Schedule screen PF11 was pressed to delete a schedule which could not be located in the Resource Repository.Check to ensure the schedule name was not change resulting in a new schedule. Select the schedule from the index list again and retry the delete.SCHEDULE UPDATE WAS REQUESTED BUT THERE ARE NO PENDING UPDATESVia PF10 your have requests that pending updates be applied to the repository but the system cannot detect any pending updates.Key in the required changes and then retry the update request.Screen "%" cannot be referred to more than onceYou referred to a particular screen more than once while specifying screen permissions for an Object set definition.Remove duplicate entries from the list by replacing the screen name with blanks, nulls, or another screen name.The screen indicated by the message has been deleted.You requested and confirmed a request to delete a screen, either from the Screen Definer or from the Screen Object List.You referred to a non-existent screen.The specified screen was previously bound but no longer exists.The user tried to delete a screen that does not exist.Delete only those screens that have been assigned a definition.Check the screen and screen table names. If necessary, modify the screen.You have specified a screen that does not exist.Correct the screen name, or if necessary, exit and define a screen.You entered a screen name more than once in the entry screen. UNLOAD cannot export a screen more than once.The screen is not defined in the system.Ensure that the screen exists and unload the screen again.You have pressed <PF12> to cancel from the Screen Definer.The definition of the specified screen is sent to the printer.The changes that have been made to the screen Help during this edit session have been canceled.The Help for the screen has been updated.Formatting of a table buffer by $FORMATROW failed. The format string parameter contains a reference to the screen field attributes of a screen table but a valid screen name was not passed to the function.Screen permissions for object set will be committed on SAVEYou saved screen permissions for an object set being defined. If the object set definition is saved, the screen permissions are committed; if not, changes to the screen permissions are ignored.Screen table "%" of Screen "%" does not fit on physical screenThe indicated screen table cannot be shown on the physical display being used.Either change the screen definition so that the indicated screen table can be shown, or run the application from a session using a terminal with a larger screen size.Screen table % does not contain a field named "DATE"The screen table must have a field where the session manager can insert the current date.Screen table % does not contain a field named "USERID"The screen table must have a field named USERID.The screen table you specified does not contain the field you specified.Screen table % does not contain a field named TITLE or VALUEThe scrollable table must provide fields that are named TITLE and VALUE.Screen table must be NEW; named (screen)table already existsYou are defining a New Session Menu and referring to tables that already exist as the head/body/history area screen tables.Since a new menu is being defined, and since the screen tables used for this menu are considered part of the menu (e.g., being deleted when the menu is deleted), the screen tables must be unique to the menu. Choose new screen table names.Screen tables "%" and "%" overlap in Screen "%"Change the starting Row and/or Column of one of the screen tables by using the Screen Table Painter.Screen update/display not allowed during screen validationThe validation rule is attempting to change or display occurrences on the screen while it is in the process of validation.Remove the update or the display statements from the validation rule.Screen validation interrupted for Screen "%"The Validation Exit key was pressed, bypassing the validation rules on the screen.This situation can be caught with a VALIDATEFAIL, and dealt with by an exception handler.The Object Manager works only for a screen which is at least 80 columns wide.Check the width of the screen and adjust accordingly.Scripted strings too long to fit on page and are truncatedThe scripted strings do not fit within the given margins and are truncated.SCROLL, EXIT or HELP function cannot use REFRESH PF keyIn the Screen Definer, you assigned a reserved PF key to one of the standard functions. For example, <PF24> is reserved for REFRESH.Reassign the changeable standard function to use a PF key other than the reserved keys.You have entered the invalid scroll amount indicated.Scroll amount "%" not valid for horizontal scrollYou entered an invalid scroll amount. Valid amounts for scrolling horizontally are:Enter a valid scroll amount and press <PF10> or <PF11>.Scroll field must be in Title of multi-occurrence screen tableYou have entered the name of a field to the SCROLL AMOUNT ENTRY prompt but the named field is not in the title area of your multi-occurrence screen table.Change the screen table definition to have the SCROLL AMOUNT ENTRY field in the Title area.You have scrolled to the TOP, or BOTTOM, of the rule.Scrollindicator field must have TYPE=S, SYNTAX=CA Field marked as a scrollindicator must be of type=S and syntax=C.Either unmark the field or change its type and syntax to correct values.The list of objects found was printed by pressing <PF13>.You have requested a search function but the search target has not been identified.A Security Administrator requested to view the profile of another SecAdmin which does not exist.You can use the OPTIONS function on the main menu to determine which Security Administrators exist, and then select from this list.Your request to build a secondary index on the specified field was successful.Your request to delete the secondary index on the indicated field was successful.Secondary index fields cannot be selectedYou cannot select any IMS secondary index fields.Security Audit Logging for EE % and user % is %The value of the Logging Control Parameter for the indicated user on the indicated Execution Environment has been logged.You do not have security access on this table.If access is required, have your Security Administrator modify the access.Security failure: Denied VIEW_DEFN access to % "%"You have requested (directly or indirectly through children) to copy the definition of an object for which you lack VIEW_DEFN security permission.You may not request to copy this object until you have obtained VIEW_DEFN security permission. This can be obtained from any user who has CONTROL permission to the object.Security failure: Denied VIEW_DEFN access to % "%"You have specified an object to copy for which you are denied VIEW_DEFN security permission.Remove the reference and continue. You must obtain the required permission prior to manipulating the object in any way.You are trying to delete an object. However, you do not have the authority to access to the object or the objects defined by that specified object.Search for the owners of those objects which you do not have the access permission. Ask them to give you access permissions on those objects and retry the operation again.The logon was prevented by a Security File Definition error.Contact either the System Administrator or Security Administrator.You confirmed a deletion request for a security Group definition. This causes the group definition to be deleted, and removes all the references to the group from the security system.The indicated security violation has halted your print request. You cannot print a table without access to it.Contact your Security Administrator if you need access to the table.Access to the indicated table is denied for security reasons.Contact your Security Administrator if you need access to the indicated table.Securityfail: % - contact security administratorAccess to a table was denied for security reasons.You encountered a security failure because you are not authorized to access the object specified in the message.Contact your Security Administrator if you need to access the object.Your action cannot be completed because of security problems. The message explains why.While processing, a security failure occurred on the specified table.See your Security Administrator with the table name.Your operation failed due to security problems. The message gives an explanation for the security failure.You tried to save your editing changes to keywords for an object but you do not have permission to update the object.Press the Skip PF key to bypass this object and continue with the next object or press the Stop PF key which takes you out of editing mode.Security clearance has not been passed for access to the indicated object.Security clearance has not been passed for access to the requested report.Due to lack of security access on the screen table(s), all checks cannot be performed.You do not have proper security for the screen table(s). Obtain security access before going back to the Screen Definer.Security clearance has not been passed as indicated by the message.Security clearance has not been passed as indicated by the message.SECURITYFAIL on REFD DATA source table "%"There is a problem with security for data referenced by an object you requested to unload.Report this problem to your System Administrator as there should not be a problem in the object type definitions for unloadable objects.SECURITYFAIL on REFD DEFN source table "%"There is a security problem with object type definition data for an object you requested to unload.Report this to your System Administrator. This should not arise for definition tables which reference definitions included in an object type.SEGMENT/DATASET RESIDENT PAGE POOL RETRIEVAL ERRORWhen attempting to send the request, the segment, and data set information you requested, an error was detected.Review the job log to determine if additional messages were produced which may help identify the problem. Retry your request. If the problem persists contact TIBCO Support.Request failed due to the data segment being offline or the indicated segment# not defined to Object Service Broker.Specify an active segment for the request. The shareable tool HURON_STATS can be used to list segment statistics. Also, check the user profile to ensure that the segment# is correct.SEGMENT CHANGE REQUEST SCHEDULEDYou have requested and confirm changes to the current processing of the segment. This message provides an acknowledgement that the request has been issued to the Data Object Broker.No action required. Monitor the segment screen to determine when the request processing has completed.SEGMENT NUMBER SPECIFIED ON MENU WAS NOT NUMERIC, IGNOREDYou attempted to specify a segment number when invoking the function from the menu. The segment number you specified failed a validation edit.Use cursor select processing to process your desired segment.SEGMENT STATISTICS COULD NOT BE RETRIEVEDAn error was detected when attempting to retrieve information about the segments currently defined to the Data Object Broker.Review the joblog to determine if there are additional messages which may help identify the cause of the problem. Retry your request. If the problem persists, contact TIBCO Support.Select a report function (such as TOTAL), or enter RULE/FIELDEither a report function, rule name, or field name must be entered as the definition for a derived field.Enter report function parameters or a rule name, field name, or expression to derive a value for this field. Consult the product documentation for further information.The cursor is not placed against one of the rules in the list.Select a SET that requires EXPLICIT CONNECT upon insertOnly pertains to a record that requires additional set connections. If additional set connections for a record that is being inserted into IDMS are required, select those sets to participate in the access path.Select all fields for COPY/APPEND and press <PF3>A COPY or APPEND command has been requested with only the table name supplied. A prompt has displayed all existing fields of the specified table.Select all fields to be copied by typing any non blank character or sequential numbers. Press <PF3> to execute the COPY or APPEND.SELECT error: "%" is not a parm or field in source tableThe indicated identifier does not exist in the source table.Look at the definition of the source table to find the name of the parameter or field.SELECT error: "%" is not a source field or a defined parameterThe indicated identifier, found in the selection criteria, is neither a field of the source table nor a newly defined parameter.
• Define the identifier as a new parameter in the parameter section
• Remove the expression that contains the identifier.SELECT error: source parm "%" can be defined only onceYou specified the indicated source parameter more than once in the selection criteria.Remove any additional references to the indicated source parameter.SELECT error: source parm "%" must use equals (=) operatorThe indicated parameter specified in the selection criteria must be set to a non-null value.Make the indicated parameter equal to a non-null value.Select field & put cursor on Print/Sort/Break/Across sectionThis instruction appears when you enter the Field screen.Select a field by typing an alphanumeric character (0-9, A-Z) beside it and placing the cursor where you want to insert the field. Press <Enter> to be prompted for the fields from the next source data table. Alternatively, you can directly type the field names into the desired section.You can select fields from only one file for each Model 204 table.Limit your selections to one file only. Define another 204 table if you need fields from another file.You can specify how to relate the source data tables you have chosen for your report by selecting from the prompt area, or by entering their relationships directly to the input area.Specify the relationships between source data tables by selecting from the lists of parameters and fields, or by entering a parameter or field name in the input area.If the current pair of tables in the prompt area is not the desired one, move the cursor to the input area to indicate the desired table or pair of tables and press <Enter>, or simply move the cursor to the prompt area and keep pressing <Enter> until the desired pair is displayed.This instruction appears when you enter the Selection screen.If you want to specify selection criteria, select items from the prompt area or enter the selection string directly in the input area. Press <Enter> to be prompted for the fields of the next source data table.Select function & field then put cursor on appropriate sectionThis instruction appears when you enter the Function screen.Select a function-field pair by typing the same alphanumeric character (0-9, A-Z) beside a function name and a field name, and place the cursor where you want to insert the function-field pair. You can select more than one pair at the same time, as long as you use the same alphanumeric character for the pair.SELECT function found % instance(s) to match criteriaYou requested to have instances selected in this screen according to the criteria for parameter name and value specified at the top of the screen. No instances matched the specification.You have pressed <Enter> without selecting the type of object for which you wish to manage/admin rights.Type S against object type and press <Enter>.You have pressed <Enter> without selecting the type of object you want to prepare this change request for.SELECT on IGNORE row of table "%" of VSAM % "%" is not allowedSelection is not allowed on a table if you specified an IGNORE value in the table definition. The variables, from left to right, are as follows:Either remove the IGNORE value from the table definition for this table, or do not request a selection operation.You entered an S next to more than one segment.You typed an S next to more than one DB2 table.You typed a character next to more than one item in a list.You can select only one file or group for each Model 204 table.Select only ONE report function OR a Rule/Field referenceYou selected more than one report function, or you selected both a report function and a rule/field reference in the definition of a derived field.Enter one report function or a rule/field reference.The Generator allows only one value be specified for each parameter of a source data table.Remove any extra parameter value selections.Select or enter a function and print field for SUMMARY PRINTYou did not specify any functions for print fields in the Summary Print section. There must be at least one function-field pair in the Summary Print section for a summary report.Select or enter a function-field pair for Summary Print, or press the FIELD function key and turn the summary flag off.Select or enter a Print field which is not a Sort/Across fieldSince it is a summary report, you have to select or enter a PRINT field that is not a SORT BY or ACROSS BY field so that you can apply a function to it on the Function screen.Select or enter a PRINT field that is not a SORT BY or ACROSS BY field.You tried to go to the next screen without selecting a field to print in the report.Specify at least one field to be printed in the report.Select or enter a Sort field for summary/across reportYou turned the SUMMARY flag on. Now you must specify a SORT BY field because a SORT BY field is also used as a SUMMARY BY field.Specify at least one SORT BY field or turn the SUMMARY flag off.Select parameter value from list or enter value(s) directlyYou can select or enter parameter values for the indicated parameter if it is not to be related to another table. However, if the first table is parameterized, then you must assign values to each of its parameter.If necessary, select a parameter value from the prompt by entering an S next to the value that you want, or type the parameter value directly in the PARM VALUE field.If you must select values for more than one parameter, and the parameter values displayed are not for the parameter that you want to see, then move the cursor to the input area to indicate the desired parameter and press <Enter>, or simply move the cursor to the prompt area and keep pressing <Enter> until the desired one is displayed.You used an invalid line command to select parameters.Select Print/Control Field screen before this actionBefore selecting the break functions or executing the report, you must select at least some report print fields from the Print/Control Fields screen.Type S in the Print/Control Fields field to access the screen.Select table from list or enter table name directlyYou must specify at least one table that will be the source of data for your report.Select source data tables from the prompt area or enter the table names in the input area.After you have selected a destination for a report, you must select the execution action to have the report executed and saved to the MetaStor.Type Y in the SAVE REPORT AND SEND TO DEST field.To execute and save a report, you must specify where you want it to be sent to by selecting a destination medium.Select the field for sixbuild by typing a 'Y' in front of itYou can choose fields for secondary index build by typing Y in the SECONDARY column beside the field name.Select fields for secondary index build by following the instruction.Select the INDEX, SET or AREA you want to navigateFor FORALL requests, select the INDEX, SET, or AREA that are to be navigated.Specify either an AREA sweep or INDEX sweep on FORALL requests. If more than one secondary index exists select the one which you wish the CA-IDMS Gateway to navigate.You were in the FIELDS context and you selected some CA-Datacom fields to include in the Object Service Broker DAT table definition. The fields you selected were inserted into the list, or have replaced entries that referred to the same CA-Datacom field name.Selected change request does not include other change requestsThe X line command applies only to consolidated change requests. Consolidated change requests are those that contain other change requests. The CONSOLIDATED field indicates whether the change request is consolidated or not.Use this line command only if CONSOLIDATED = Y.The selected table or table instance is empty.Selected field "%" is not in the definition of table "%"The field used in the selection string is not defined in the table specified.
• Remove the selection clause that contains the undefined field.
• Include the undefined field in the table definition.The object command fails because the selected object no longer exists. The object may have been deleted by another user.The X line command can be used to manage rights on objects that are contained in the object being expanded. Objects that do not contain other objects cannot be expanded. Only screens, reports, object sets and tables can be expanded.Use this line command on a screen, report, object set or table.SELECTION change; check all REPORT FUNCTIONSYou requested a change to the report selection.Check all defined report functions to determine if the modified report selection should be placed inside the WHERE clause for the report function.Selection Code must match one from Input File and be uniqueYou either assigned a selection code that is undefined in the input file, or you have assigned the same selection code to more than one output field of your table.Ensure that the selection code is defined in the input file and is assigned to only one output field of the table.Selection criteria is too long to fit in report definitionAny selection criteria and control fields specified are required for a report function to produce a derived field. One or both of the following has occurred:
• You specified too many control fields on the Field screen.
• Shorten the criteria by removing unnecessary blanks or parentheses, or by replacing "AND" and "OR" with "&" and "|" respectively.
• Press the FIELD function key to display the Field screen, and reduce the number of SORT BY or ACROSS BY fields if the SUMMARY flag is on, or reduce the number of BREAK BY fields if the SUMMARY flag is off.Parameter -d 'YYMMDD,HHMMSS' must be specified to select up to which point in time pages are to be restored from backup.Retry specifying the date and time as indicated above.A selection could not be applied against an occurrence. The message log will contain a more detailed error message.Selection for table "%" can have only one of >, <, >=, <=The selection for a table can only have only one of the following:For example, given a table T with parameters P1 and P2 and the following selection criteria:Selection (1) and (2) cannot be both specified for table T since only either > or < is allowed, but not both.Selection (1) and (3) cannot be both specified for table T since the selection criteria can have only one >.Follow the rules allowed for selection and modify the selection string accordingly.The internal representation of a selection exceeded 254 bytes.SELECTION ITEM NOT SUPPLIED, PLEASE RETRYYou must specify an item number to display the profile.Key the desired item number in the input field and retry your request.You have entered an invalid selection.Selection not allowed for non-parameterized tableYou specified a selection string for a non-parameterized table, but you can only use the selection string to specify parameter values (i.e., select table instances).Delete the selection string for the non-parameterized table.Selection on a derived field is not supported.Using the traceback log, determine the rule containing the invalid selection and remove the reference to the derived field.SELECTION OF SEGMENT VIA CURSOR POSITION FAILEDWhen attempting to process a specific segment, the cursor positioning analyzer failed to identify a valid segment.Reposition the cursor using the tab keys and try your request again.An explanation of why the specified selection string is syntactically incorrect is provided.Correct the syntax error in the selection string. Press <PF1> for Help if you want to know the correct syntax.The selection criteria cannot exceed the indicated number of lines.You can reduce the length of the selection string by removing unnecessary blanks or parentheses, or by replacing "AND" and "OR" with "&" and "|" respectively.Selection string for report field "%" of report table "%" is too bigThe selection string for a report function had too many terms.Simplify the selection criteria for the report function.Selection string for report field "%" of report table "%" is too complex to build (stack overflow)Brackets for a report function selection string are nested too deeply.Review the selection string to reduce the depth of the brackets.The selection string for a report had too many terms.Simplify the selection criteria for the body report table.Selection string for report table "%" is too complex to build - stack overflowBrackets for the body report table selection string are nested too deeply.Review the selection string to reduce the depth of the brackets.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.Selection string you have supplied for tool PROCESS_TABLE is too large to process.Selection string specified for access on table "%" is too longThe selection conditions in the table access statement are too complicated.A selection string for the body report table exceeds the maximum size.Reduce the complexity of the selection string by removing or joining terms.You tried to edit one of the lines which separate the rule quadrants.Sequence number "%" is not on the first line of the statementA sequence number was placed on a line other than the first line in a multiline statement.
• Remove the sequence number if the first line already has a sequence number.
• Move the sequence number to the first line if the first line does not already have a sequence number.Sequence number "%" is within a FORALL or UNTIL loopA sequence number was included in a loop structure.The indicated serverid is undefined.Contact your Database Administrator for valid serverids.Server parameter % must be defined with USAGE "%"Invalid gateway parameter values are entered for field USAGE.Specific correct value for USAGE as indicated in the message.There is no gateway parameter defined for the specified table type.Invoke option "Define server parameters" in tool GENDT to define gateway parameter for the new table type.The specified Serverid has not been defined.Serverid is longer than maximum allowed (8 characters)Length of serverid is longer than allowed.Specify serverid with length less than or equal to 8.Log, transaction or session deactivation failed.SESSEXRN - executor environment call stack overflow
2. Contact TIBCO Support with the log and a description of the actions performed before the message was displayed.Call to $SETSESSIONEND is attempting to set an invalid session end abend code. The user abend codes must be greater than zero but less than 4000.Change the call to $SETSESSIONEND to pass a valid user abend code.Call to $SETSESSIONEND is attempting to set an invalid session end return code. The user return code must be greater than or equal to zero but less than 4000.Change the call to $SETSESSIONEND to pass a valid user return code value.You referred to a non-existent session menu in the user profile being updated.Use STANDARD until you find the name of a valid session menu.Set and index files incompatible...check their contentsThe data contained in the set and index import files is not from the same subschema.
1. Check the contents of the set and index files that you were going to load.
2. Use the LOAD AN IDMS SUBSCHEMA manager utility again to change the files that you import.Set and record files incompatible...check their contentsThe data contained in the set and record import files is not from the same subschema.
1. Check the contents of the set and record files that you were going to load.
2. Use the "Load an IDMS Subschema" manager utility again to change the files that you import.CONTROL access to this object by the specified user was denied.The user can ask someone who has CONTROL access to the object to provide CONTROL access.Set permission of LIBRARY % by % to grant % access to %The indicated discretionary access permissions to the given library were granted to the indicated user/group.Set permission of LIBRARY % by % to remove % access from %Discretionary access permissions to the specified library were removed from the indicated user/group.Set permission of REPORT % by % to grant % access to %The indicated discretionary access permissions to the given report were granted to the indicated user/group.Set permission of REPORT % by % to remove % access from %Discretionary access permissions to the specified report were removed from the indicated user/group.Set permission of SCREEN % by % to grant % access to %The indicated discretionary access permissions to the given screen were granted to the indicated user/group.Set permission of SCREEN % by % to remove % access from %Discretionary access permissions to the specified screen were removed from the indicated user/group.Set permission of TABLE % by % to grant access % to %The indicated discretionary access permissions to the given table were granted to the indicated user/group.Set permission of TABLE % by % to remove access % from %Discretionary access permissions to the specified table were removed from the indicated user/group.Set security of LIBRARY % by % to delete recordA library entry was deleted from the security table (@LIB_SECURITY) by executing rules.Set security of LIBRARY % by % to insert recordA library entry was inserted into the security table (@LIB_SECURITY) by executing rules.Set security of LIBRARY % by % to update recordThe security information (e.g. classification) of the specified library was changed by the indicated user.Set security of REPORT % by % to delete recordA report entry was deleted from the security table (@RPT_SECURITY) by executing rules.Set security of REPORT % by % to insert recordA report entry was inserted into the security table (@RPT_SECURITY) by executing rules.Set security of REPORT % by % to update recordThe security information (e.g. classification) of the specified report was changed by the indicated user.Set security of SCREEN % by % to delete recordA screen entry was deleted from the security table (@SCR_SECURITY) by executing rules.Set security of SCREEN % by % to insert recordA screen entry was inserted into the security table (@SCR_SECURITY) by executing rules.Set security of SCREEN % by % to update recordThe security information (e.g. classification) of the specified screen was changed by the indicated user.A table entry was deleted from the security table (@TBL_SECURITY) by executing rules.A table entry was inserted into the security table (@TBL_SECURITY) by executing rules.The security information (e.g. classification) of the specified table was changed by the indicated user.The security information for the indicated userid was changed. Because some of the changes take effect immediately, and others may not take effect until the next time the user logs on, it is recommended that changes are made to a user's security information only when the user is not on the system.Set security of USERID % to change logon password deniedThe user cannot change the logon password because the user failed to provide the current password.Setting of blank overlap for report field "%" not allowed because blank overlap enabled for report table "%"You cannot alter the blank overlap for a report field if the blank overlap setting was requested for the same report table.Do not use the blank overlap option on a report table basis. Set the blank overlap for each report field of the report table.The changes to the given setup have been processed as indicated.Your specified action cannot be performed on the given setup. For example you may be attempting to save or delete the PRINT setup. This is not allowed since PRINT is one of the standard setups.A message to confirm that the specified action is to be performed on the given setup.Follow the instruction to confirm the action or not.An error has been determined between the gateway/server EE and the Data Object Broker it is communicating with.Check the communications definitions and their status.The Dynamic Object Facility encountered an event that should never happen in normal operation.The VSAM I/O request could not be completed successfully. The feedback code (displayed in hexadecimal) corresponds to the 3-byte RPL feedback area described in the current VSAM Macro Instruction Reference IBM manual.Refer to the IBM manual for additional information about the type of error that occurred.An error occurred when you tried to access a VSAM data set. The VSAM RPL feedback return code and reason code may be included in this message.If the RPL feedback code is provided, check the z/OS system documentation for further explanation.No occurrence found for the bound table. This is additional information concerning bound storage. The message appears in the system log when a transaction failure causes other problems.Severe error occurred in communications ServerA message could not be sent to the Data Object Broker or a gateway/server or a message reply was not received from the Data Object Broker or gateway/server.Data Object Broker output or logs will give further information. The user message log may also provide a message issued by the Data Object Broker or gateway/server.After the Data Object Broker or gateway/server problem has been resolved, it may be necessary to log off the user session and log back on.The native server is unable to satisfy the request. The message log will contain a more detailed error message.The IMS Gateway could not continue.Check the IMS Gateway log for error messages.The indicated tool failed for the reason shown.Use the reason shown to correct the failure. If you need further help, contact TIBCO Support with the log:
• Internal processing error - contact TIBCO Support with the log
• Truncation occurred - contact TIBCO Support with the log
• Input parameter specification error - contact TIBCO Support with the log
• Source literal has invalid length - correct the length of the source literal to match the requirements
• Source field has invalid length - correct the length of the source field to match the requirements
• Source literal has invalid format - correct the format of the source literal
• Source literal contains invalid data - examine the literal and correct the contents to match the specificationThe client machine ran out of memory.The client machine ran out of memory.Show IF NO OWNER only valid for Optional or Manual setsInvalid SHOW flag. Show IF NO OWNER is only supported for set options OA, OM and MM.Show IF SET EMPTY invalid for 2nd level record in a parameterized tableThe second-level record in the access path cannot have "SHOW IF SET EMPTY" if the table is parameterized.Invalid value entered for SHOW indicator.Specify value Y, N, or blank for SHOW indicator.The side title exceeds the width of the screen.Shorten the title or remove optional items such as the library name, TEST and BROWSE, or the date and time.Signature does not match parameters for Java external routine %The signature of the Java external routine in the LIBNAME field of the corresponding row in the table ROUTINES does not match one or more of the parameter descriptions in the corresponding instance of the table ARGUMENTS.Correct either the signature or the parameter description in the ARGUMENTS table instance.Single Occurrence Editor is not supported for this utilityYou invoked the Single Occurrence Editor which is not supported in this utility (e.g., BROWSER).If you need to use the Single Occurrence Editor, terminate the current transaction and invoke a utility (e.g., STE, STEBROWSE) that supports the Single Occurrence Editor.Single Rule Menus can not be updated; they may be used onlySupport for Single Rule Manager menu type is being removed since this capability is encompassed in other menu types (e.g., Simple). Use of existing Single Rule menus (via DISPLAY_MENU or SINGLEMGR) is supported, but support will eventually be removed when these menus have been converted to other menu types.No action required. You cannot update the menu.A secondary index has been built on the indicated field since the Table Definer was opened but this field has either been renamed or deleted from the definition.If the definer allows it, you can restore the field name or add the field back to the definition. Otherwise, you can save as a new table definition or exit without saving.A secondary index has been built on the indicated field since the Table Definer was opened but the field attribute specified has been changed.Change the attribute value for the field to the value specified.Size error detected in %. Conversion of % % to % % failedInternal error that may indicate a problem with the scheduling of rules. 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.Size error detected in conversion of argument # of % routine "%"A routine was called with an argument value that is too big for the routine argument.Some objects could not be FETCHed because they do not existSome of the objects that you attempted to FETCH from the object set are objects that do not exist. These objects were not fetched.Some occs no longer exist; some are incomplete due to securitySome of the selected occurrences no longer exist (i.e. they were deleted). Others are not viewable by you because of security, for these occurrences you will only see the primary key, the other fields will be blank.Some of the selected occurrences no longer exist (i.e. they were deleted).Some type of Static SQL to be generated must be chosenYou made a request to generate Static SQL, but you did not identify the type of Static SQL to generate.Under the columns marked by S, I, D, R, enter Y to generate SELECT (Get/Forall), INSERT, DELETE, and REPLACE Static SQL statements respectively. Enter N under the ones for which no Static SQL statement is to be generated.Some Unicode or raw data fields are omitted from table %Unicode and raw data fields are not allowed in screens.Some Unicode or raw data fields were omitted from table %. Press <Enter>Unicode and raw data fields are not allowed in reports.Sort field "%" for report "%" is an unsupported syntax for sortingSORT only supports syntaxes of B (binary), P (packed), C (fixed-length string), and V (variable-length string).Redefine the syntax of the report field to allow sorting.Sort for report "%" failed; # rows read but # rows output by sortThe number of SORT input records does not match the number of SORT output records.Sort for report "%" failed with a return code of #The system sort failed when the server attempted to print the report.Refer to your installation system sort documentation to determine the reason for the error return code.SORTIN/SORTOUT record total mismatch; module "%"A mismatch occurred between the number of records input to the sort and the number of records output. The name of the module in which this mismatch occurred is specified.Call your system administrator to check the sort parameters for validity, and to check the return code in Register 15 against the appropriate vendor's manual. Correct the problem as required.Source & destination libraries are alike, must specify a nameYou have requested to copy a rule such that the source and destination libraries are the same. To copy the rule, you must supply a new name.Source & Destination libraries are alike; must specify a nameYou have specified only one library as both the source and destination of the copy.You must specify a rule name to copy into since the source and destination libraries are identical.Source (rule) name must be specified for "D"erived indicatorYou entered a D in the SRC field, but did not enter anything in the SOURCE NAME field.Enter the name of a functional rule that will derive values for the field, or remove the D from the SRC field.Source expression for report field "%" of report table "%" is too complex to evaluate - stack overflowInsufficient storage exists to evaluate a derived report field. This problem can be caused by a derivation based on a rule call that returned a string which is too long.Source location parm "%" is not defined in parameter listLocation parameter in the source table is missing from the subview table definition.Ensure the location parameter of the source table is being defined in the subview.Source name of field % is undefined in source tableThe preprocessor cannot find the name of a field in the definition.Check the definitions of the subview and the base table.Source name of parameter % is undefined in source tableThe preprocessor cannot find the name of a parameter.Check the definition of the subview and the base table.You entered an S in the SRC field, but did not provide a field name in the SOURCE NAME field.Enter a field name from the source table in the SOURCE NAME field, or remove the S from the SRC field and type the source field name directly in the FIELD NAME field.Source parm "%" is already defined in parameter listThe specified parameter of the source table has been defined more than once in the parameter information section of a subview table definition.Remove the excess definitions of the indicated source parameter.Source parm "%" is already defined in selectionThe indicated parameter of the source table is defined in both the selection section and the parameter information section of the subview table definition.Remove the indicated parameter from the selection criteria or from the parameter information.Source parm "%" is not defined in selection or parameter listThe indicated parameter of the source table is not defined in the selection section nor in the parameter section of the current subview definition.Define the indicated parameter of the source table in either the selection criteria (SELECT field) or the parameter information for the subview.The indicated parameter does not exist in the indicated source table.
• Look at the definition of the source table to get the name of an existing parameter
• If the source table does not contain data, you can add a parameter to the source table.Source parm "%.%" not defined in subview "%"A source table parameter was not specified. It must be specified in one of the following places:Specify the source table parameter in one of the following:Source record length (#) > lrecl (#) of the output dataset "%" for "%"The length of the record to be output to a data set is bigger than the defined length of a record in the data set.Ensure that the source record is not too big for the data set record, or define the data set record length to be longer.Source string for report field "%" of report table "%" is too bigThe source of a derived report field is too complex to be stored in the Report Server data structure.Source table "%" cannot be updated because the data is boundThe user tried to update a source table in which data is stored in the bound area.Correct the appropriate rule and do not update this table.You must define the source table before defining a parameter (PRM) or subview (SUB) table for it.The indicated source table does not have any data parameters; therefore the current PRM table cannot be created.Provide the name of a table that has data parameter(s) as the source for the PRM table, or cancel the table definition.Source table "%" no longer exists. Use Select Table(s) screen to verifyOne of the source tables used in this report no longer exists. The table has either been deleted or renamed.Verify if the table has been deleted or renamed, and do one of the following:
• If the table has been renamed, select "Select Table(s)" from the main Report Generator screen. Exclude the table in question from the report and enter the new table name.
• If the table has been deleted and is no longer required in the report, select "Select Table(s)" from the main Report Generator screen and exclude the table in question from the report.Source table "%" potential occurrence width is too wide to COMMITThe total length of the occurrence in the internal storage is greater than 2 016 bytes.Reduce the occurrence length in the definition of the table.You did not enter the name of a source table.Enter the name of a table that will provide data for your current table definition.You cannot define a parameter (PRM) or subview (SUB) table on the indicated type of table.If you are defining a subview table, you can choose a DB2, 204, IDM, IMP, IMS, TDS, or VSM table as the source table.If you are defining a PRM table, you can choose an IMP, TEM, or TDS table as the source.Source value overflowing mask specifications in $PICThe number you have used in a VALUE specification requires more digit placeholders than are available in the MASK specification.Verify that MASK, VALUE specifications are compatible.The values of SOURCENAME and SOURCE must either be both present or both set to nulls.Remove the values from SOURCENAME and SOURCE, or set the both their values accordingly.Specification of parameter values CANCELLEDYou canceled from the screen where you supply parameter values to specify a table instance.SPECIFIED ACCUMULATIVE SCREEN PRINT INVALID, MUST BE "A", "E" OR "N"The value you entered for the accumulative screen print function is invalid.Correct the input and retry your request. See the online help for more information.SPECIFIED BUFFER NUMBER IS INVALIDThe buffer number entered is negative, too large or contains invalid characters.SPECIFIED DISPLAY SCREEN INVALID, MUST BE "A" OR "I"The value you entered to identify which screen is to be displayed is invalid.Correct your input and retry the request. See the online help screens for additional information.SPECIFIED INTERVAL IS OUT OF RANGE (5 TO 60)The time interval you specified is not within the specified range.Correct the interval and retry your request.SPECIFIED INTERVAL SCREEN PRINT INVALID, MUST BE "Y" OR "N"The value you specified for the interval screen print is invalid; it must be Y or N.SPECIFIED ITERATION IS OUT OF RANGE (5 TO 60)The number of iterations you requested is outside the specified range.SPECIFIED MEMORY ADDRESS-LENGTH CONTAINS INVALID CHARACTERSThe value you entered for the memory location and or response length contains invalid characters.SPECIFIED SCHEDULE IS NOT DEFINEDYou have identified a schedule name that is invalid.Either rekey the schedule name or use <PF10> to determine what schedules are currently available.SPECIFIED SEG-DSN-ENT CONTAINS INVALID CHARACTERSThe segment-data set or data set number you specified contained invalid characters.Correct your input and retry your request.SPECIFIED SEG-PAGE CONTAINS INVALID CHARACTERSThe segment and or page number you have specified is invalid.SPECIFIED START ENTRY EXCEED DIRECTORY LIMITSThe entry number you specified (segment-data set-entry number) exceeds the limit of the resident page directory.Specify "Default" fields in "Source" section for Objectset "%"You requested to copy an object set. However, you did not specify information required to identify objects referenced by that object set. For example, if the object set contains rules and you want to copy them as well, you must specify a Default Library.Specify a medium and select an action to produce reportThis instruction appears when you enter the Execute screen. Before you do so, you may want to edit your report title, modify your field labels, add masks for the fields, save the report to the MetaStor only, or create the report rule.Use Y to select one of the four destination media, as well as SAVE REPORT AND SEND TO DEST; then press <Enter> to produce your report.You must specify either a parameter, Data Set or DDname for a VSM table.Define a parameter or enter a data set name or DDname.SPECIFY A SELECTION CODE AND PRESS <ENTER> FOR A NEW HELP TOPICYou must enter the selection number specified at the end of the current help text in order to progress to the next level (more detailed) of Help text.Specify all parameters either with table name or in WHERESome table parameters appear in parentheses after the table name, and some appear in the WHERE clause.Put all the parameters together in one place or the other.Specify an IDgen parameter (parameter with a reference table)You turned the IDgen flag on, but you did not specify an IDgen parameter for the table. A parameter with a reference table is treated as an IDgen parameter.Specify an IDgen parameter, or turn the IDgen flag off.Specify any justification required for titles shownIn a titles only report table, all rows are marked with T. The Titles/Mask screen can be used to specify any justification required for the displayed title rows.Specify Default fields in Source section for Objectset "%"You have specified an object set but you have not specified the Default Library and Default Environment in the Source section. These are required to properly identify all objects in the object set.Fill in the DEFAULT LIBRARY and DEFAULT ENVIRONMENT field in the Source section. Default Library will be used to find RULES in the object set; Default Environment will be used to copy screens in the object set.Specify either default printer options or data set, not bothYou specified both the default printer options and a data set.You must specify a data set name or a DDNAME for IMP or EXP tables.Specify NEW OWNER to transfer ownership of selected objectsYou attempted to use the TRANSFER&EXIT function from the Transfer Ownership function without specifying the new owner of objects to be transferred.Type in the userid of the new owner, or use the USERIDS function to select from a list of potential new owners.The report can be sent to only one destination at a time, and you have specified more than one.SPECIFY OR PLACE THE CURSOR ON THE DESIRED TYPE AND RETRY YOUR REQUESTIn order to proceed from the current Resource Type List screen you must identify the "Type" you wish to process. The type can be identified by cursor positioning or by keying it into the Type input field at the bottom of the screen.Specify Parameter(s) screen unavailable - no parameters for specified tablesThe Specify Parameter(s) screen is irrelevant because none of the source data tables are parameterized.The first percent sign (%) is replaced with Name or Value. The indicated parameter name or parameter value is not accompanied by a table name.Enter the table name for the parameter name or value.CLASS is a required attribute for a parameter and a value must be specified for it.Specify the appropriate class for the parameter. D is for data parameter and L is for Location parameter.Your action cannot be performed because you have not specified the name of the table.Specify TYPE and PATTERN before requesting SEARCHYou requested the SEARCH function in the Transfer Ownership screen, but you did not specify the type of object to search for and the pattern to search for.Specify the pattern (e.g., *USR40* or XYZ) and the type of object being sought: TBL (table), SCR (screen), RPT (report), LIB (library), GRP (group). Press the SEARCH PF key again.Specify a value for the object indicated in the message.Specify values for ALL table parameters or set ALL DATA="Y"One of the following situations occurred:
• You are specifying a table instance or the whole table before managing permissions to a parameterized table
• While specifying table permissions for an object set definition, you left ALL DATA set to N and did not specify values for each parameter of the tableIf you want to refer to the whole table, set ALL DATA to Y and set all the parameter values to NULL. If you want to refer to just one instance of the table, set ALL DATA to N and supply a value for each table parameter before pressing <Enter> to continue.Split this line before trying to replace "%" with "%"Replacing the first token by the second one may cause a line overflow.SRBMODE=N SRB STATISTICS NOT SUPPORTEDThe user has attempted to retrieve SRB enclave statistics. These are only supported if SRBMODE=Y or Z.To generate a report, you must first supply a source table name. The source table(s) will provide the information needed.Type S in the Select Table(s) field to access the screen.START CONNECTION REQUEST REJECTED, CONNECTION IN PROGRESS OR AT LIMITAfter verifying your <PF9> start request the system determined either all the required connections were present or the system was currently initiating connections for the displayed resource detail.START NUMBER must be less than or equal to END NUMBERThe START NUMBER and END NUMBER fields provide a way to limit the range of the change requests queried. The first number in the range must be less than or equal to the last number. If both numbers are the same, only one change request will be in the range of the query.START position operand of the SUBSTRING function is greater than the length 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.START position operand of the SUBSTRING function is less than 1Internal 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.START REQUEST IS INVALID FOR RESOURCES THAT DO NOT SUPPORT USER IDPREFIXYou pressed <PF9> to start a Data Object Broker generated connection; however, the Detail entry currently displayed does not have a "User ID Prefix" and does not support connection generation.Starting Phase 1 of the apply process used to apply a promotion to a separate system. There are 3 phases.STARTING APPLY FOR CHANGE REQUEST #% FROM NODE %The Promotion tool is starting the application of the specified change request from the specified source node.STARTING BACKOUT OF CHANGE REQUEST #%The Promotion utility is starting to back out the specified change request.STARTING EXTRACT OF CHANGE REQUEST #%The Promotion utility is extracting the change request specified.STARTING PROMOTION OF CHANGE REQUEST #%The promotion of the specified change request is beginning.Static SQL was successfully generated for the table.The definition of the table indicates that Static SQL is no longer available.Manually delete the code previously generated.You have cleared the status for the specified object. If this object was previously selected for promotion, deletion, or execution, it is no longer included in the change request.The status of the specified change request has been changed to one of the following:You tried to back out a promotion, but you cannot do so unless the status is C (Completed).You have entered the STOPDEBUGGER primary command. This provides feedback.STOP TYPE = type AND GROUP = group REQUEST HAS BEEN ISSUEDThis message acknowledges the receipt of confirmation for the stop server request for the type and group identified in the message.This message is used by the Object Service Broker program that produces the Object Service Broker Information Log.For more information, show this message to a System Programmer.Insufficient memory exists to run the transaction.Ensure that the applications you are running do not use an excessive amount of storage. Review the usage of session tables.Storage management initialization of scope TRANSACTION failed with a return code of #
2. Contact TIBCO Support with the log and a description of the actions performed before the message was displayed.Storage management termination of scope TRANSACTION failed with a return code of #
2. Contact TIBCO Support with the log and a description of the actions performed before the message was displayed.Stored procedure extract verify successful, PF3 to extractThe input values provided return 1 or more result sets. @RESULT@ contains the number returned.PF3 to extract. Note: you will be asked to execute the stored procedure one more time.Stored procedure result set table creation SUCCESSFULThe result set table definitions have been createdA table definition stored selection could not be parsed. The message log will contain a more detailed error message.A stored table selection refers to a field which is not specified in the definition of the table.The string does not contain a valid Object Service Broker name.Enter a valid Object Service Broker name. Valid entries are any character string up to 16 characters beginning with a letter (A-Z) or a special character ($ or #), and continuing with more letters, special characters, digits (0-9), or underscore characters (_).The string does not contain a valid Object Service Broker name.Enter a valid Object Service Broker name. Valid entries are any character string up to 16 characters beginning with a letter (A-Z) or a special character ($ or #), and continuing with more letters, special characters, digits (0-9), or underscore characters (_).String size error on table %; occurrence skipped % %The specified field of the specified table was too small to hold the specified value; hence, the occurrence was skipped.The string is too long to be scripted and displayed on the screen.
• The argument LENGTH for HEADSTRING exceeds 4000.
• The argument LENGTH for TAILSTRING exceeds 3999.STRINGSIZE detected when evaluating source of report field "%" of report table "%"The derived report field is too small to hold the string value that is assigned to it.Review the source of the derived report field and the input data used to set its value. Change the definition of the derived field appropriately.You cannot select a subdivided field as a parameter.You cannot select a subdivided field as a primary key.You cannot store an access value in a subdivided field.An error was encountered when a batch request was submitted to a batch queue.You pressed <PF5> or <PF6> and directed the output to a data set. The output is the PRINT TREE if you pressed <PF5>, or CROSS REFERENCE if you pressed <PF6>. The name of the data set is given in the message.This message notifies you that you have printed the specified report to the given medium.You pressed <PF5> or <PF6> with Hardcopy set to Y. The output is either a PRINT TREE if you pressed <PF5>, or a CROSS REFERENCE if you pressed <PF6>.Subroutine "%" is being called as a functionYou are using a procedural routine as a function. Note that CICS or IMS external routines may not be used as functions.Subview "%"'s primary key fields are not the same as its source table primary key fieldsThe primary key fields of the subview must be compatible with the source table, and the same number of fields must exist.Subview "%" has different primary key(s) than its sourceThe source field name of a subview primary key field is different from the name of the primary key for the source table.Modify the subview table definition so that the source field of the subview primary key is the same as the primary key in the source table.An INSERT, REPLACE, or DELETE operation on a subview table has failed. The occurrence to be manipulated did not meet the stored selection criteria.Modify the selection criteria in the subview table definition.Sum of parameter value lengths (%) exceeds maximum (%)You are specifying a table instance by providing values for the table's parameters (i.e., before viewing a permissions list of the instance, or while specifying table instances for the object set definition), and the sum of the lengths exceeds the maximum.You can shorten the parameter values or use the whole table permissions to set the permissions.SUMMARY field "%" of report table "%" must be a sort field of across report "%"For Across Reports, all SUMMARY fields must also be SORT fields.Use the Report Definer to add the SUMMARY field to the list of SORT fields.SUMMARY LIST SORTED BY XXXXXXXXXXXXXXNotification of the sort order of the displayed list of Execution Environment connections.SUMMARY_BY field must exist if ACROSS_BY specifiedAll Across Reports must be summaries. SUMMARY_BY controls rows; SORT_ACROSS_BY controls columns.SUPPLIED TYPE (type) IS INVALID, RETRY YOUR REQUEST OR PRESS PF5 TO ADDThe type value you keyed in does not exist.If you want to add a new Resource Type, press <PF5> to invoke the Resource Detail screen in input mode so the new resource can be added. If you are trying to display an existing Resource, either rekey the value or select the type from the displayed list.SUPPLIED TYPE (type) IS MISSING OR INVALID, STOP REQUEST WILL BE IGNOREDWhen the Stop request was made the cursor was not positioned on a defined Resource Type or the value keyed in the Type input field does not identify an existing Resource Type.Identify a valid Resource Type and reissue the Stop request.Supply target (line command A = after) for MOVE commandA move (M) line command was issued without a corresponding after (A) line command to indicate where to move the rows.Place an after (A) line command on the row that is the target position for the moved rows.SYNC failed - too many updates to be committedThe updates to be committed exceeded 16 KB in size, and therefore were not applied.Change the appropriate rules to commit more frequently.SYNC processing failed, possible duplicate or non-existent key in mass update tableWithin the mass insert data, an entry with a duplicate key or an entry without a key occurred.Find and remove the duplicate entry, or ensure that every entry has a key.You cannot define the specified syntax as a primary key. Valid syntaxes for a primary key are:
• Change the syntax of the primary key to C, V, B, or P.SYNTAX ERROR:"%" is not a valid field on table "%"The indicated field was entered as part of a selection string and does not exist in the current definition of the report.Ensure that selection strings contain only valid fields that appear in the definition area of the report.Syntax error: "%" encountered when expecting %SYNTAX ERROR: "%" when expecting "%","%","%"The input token was seen when the parser expected to see the token named.Check the syntax of the input and change it as required.You have mismatched parentheses in your input; there are too few or too many parentheses.Review your input and add or remove parentheses as required.The table name or parameter list is not syntactically correct.The Rule/Field value entered as a definition for a derived field contains a syntax error.Correct the syntax error. If the definition is a rule or an expression, see the Object Service Broker documentation for syntax information. If the definition is an Object Service Broker tool, see the Object Service Broker documentation for the correct syntax.Syntax error in primary command; press <PF1> for HelpYou entered a primary command with invalid syntax.Press <PF1> for descriptions of valid syntax for the primary commands and correct the command.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.SYNTAX ERROR in SELECTION specified for DAT tableYour selection information, in the CORE context of this Table Definition, contains a syntax error.Go to the CORE context and correct the syntax error in the SELECTION specification.Syntax error in signature for Java external routine "%"There is a syntax error in the specification of the Java external routine in the LIBNAME field of the corresponding row of the ROUTINES table.SYNTAX ERROR on SELECTION for REFD DATA source table "%"One of the objects which was requested for unload has, as part of it, some data which is referenced in the object's definition. However, there is a problem with the specification of this data to unload in the object type definition data.This problem should be reported to the System Administrator since it should not be the case the there are problems in the object type specifications for unloadable objects.SYNTAX ERROR on SELECTION for REFD DEFN source table "%"There is a problem in the object type definition for one of the objects you requested to unload.Report this problem to your System Administrator since there should not be a problem with object type definitions of unloadable objects.Syntax F is not permitted for a parameter definitionYou cannot define a floating point field as a parameter field in a MetaStor IMS table.Change the syntax of the field or do not select it as a parameter.A field defined with floating point syntax cannot be chosen as a primary key for a MetaStor IMS table.Change the syntax of the field or do not select it as a primary key.The indicated field has a syntax that is not valid for reports.System error, please see your system administratorAn error occurred in the preprocessor.System error - error detected in table scope stack; expected "%" but found "%"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.System error - overflow of executor scope stackInternal 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.System error - table name "%" cannot be found in executorInternal 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.A table provided with the system contains an error.The Data Object Broker was unable to complete the updates in a SYNC message. There was either a lock buffer overflow or there were too many updates.Commit updates more often. If many table sets are being updated in the same transaction, use the EXECUTE statement to update them in separate transactions.System internal error - display of argument prompt screen failedVerify that your 3270 display is functioning correctly. If it is not, then contact your system administrator.System routines cannot be edited: routine "%"You placed the cursor beside a system routine and pressed <PF6>. System routines cannot be edited.GEN_SYS_TBLS has run successfully.LOAD_SYS_TBLS has run successfully.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |