Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Using Messages Without Identifiers : Messages beginning with: P

Messages beginning with: P
Packed field cannot have length greater than 15
Screen Definer
You have defined a field to have a SYN of packed decimal but defined its length to be greater than 15, which is the maximum valid length for a syntax of this type.
Change the length to less than 15, or change the SYN definition.
Pad character for "%" is not printable (decimal "#")
Builtin Routines
The argument FILL of the $PRINTFIELD tool must be a printable character.
Supply a printable character.
Page '%' has an invalid length
Offline Utilities
The specified page header had a page length that exceeded 4 KB.
This usually indicates a corrupted page.
Page '%' has invalid type '%'
Offline Utilities
The page number indicated in the message has an invalid page type in the page header information. The page image is restored and the utility continues. This message is most common when pages are encountered that were the target of a table delete operation. While the pages of the table are being deleted, their page type indicator is converted to lowercase. This may be a normal occurrence in this case.
If the page type is not simply a lowercase letter, the Pagestore may be corrupted. Validate and correct the Pagestore in this case.
Page file % only contains % pages
Offline Utilities
There are more pages for the specified page file than can fit into the file.
Reformat the file, expanding it enough to hold the number of pages in the file.
Page file '%' was encountered in backup set
Offline Utilities
This message is issued when a page file is encountered in the backup but is not available for processing. This can happen when the DBGEN definition for the segment being processed does not specify enough page files in the ACBS= parameter.
See accompanying message for further details. Respond as appropriate and rerun the utility.
Page Length/Width must be greater than 0
Report Definer
The page length and width must be greater than 0.
Correct the page length and width.
Page length cannot be less than 1
Print Table
You defined the page length to be too small for any data to print.
Make the page length 1 or greater.
Page size of report ";" too large - length * width greater than 262100 bytes
Report Server
The size of the page to be output is too large. The page size is equal to the number of lines on the page multiplied by the maximum length of a line on the page.
Decrease the number of lines on a page, the line length, or both.
Page width cannot be greater than 132
Print Table
You defined the page to be too wide.
Make the page width greater than or equal to 50 but not greater than 132.
Page width cannot be less than 50
Print Table
You defined the page width to be too small.
Define the page length to be 50 or greater, but less than 132.
Page width too small to hold a TITLE COLUMN and a FINAL COLUMN for report table "%"
Report Server
The current page width does not permit you to print the title column and the final column on the same page.
Use the Report Definer or the $RPTPARMS tool in the rule that prints the Across Report to increase the page width.
Page width too small to hold a TITLE COLUMN and one repeating body for report table "%"
Report Server
The current page width does not allow you to print a title column and one repeating body report table in an Across Report.
Use the Report Definer or the $RPTPARMS tool in the rule that prints the report to increase the page width.
Parameter "%" does not exist in table "%"
Report Generator
The indicated parameter name does not exist in the definition of the indicated table.
Remove or change the indicated parameter name.
Parameter "%" is not a correct % identifier
HLIPREPROCESSOR
The name used for a parameter is not a valid identifier in the host language.
Change the name of the parameter.
Parameter "%" is not a location parm of source table "%"
Table Definer
You have specified the given parameter as a location parameter for the subview table. However, the given parameter is not a location parameter of the source table.
Check the source table definition for location parameter and change definition of subview accordingly.
Parameter "%" is not a source parm; must specify syntax
Table Definer
The parameter you specified is not a parameter of the source table therefore you must specify a syntax.
Specify a syntax for the parameter.
Parameter "%" is not defined in selection or source table "%"
Table Definer
The indicated parameter does not exist in the source table nor does it appear in the selection section of the current subview table definition.
Do one of the following:
Remove the parameter name from the subview table definition.
Change the parameter name to a parameter of the source table.
Fill in the source parameter field with a parameter from the source table.
Define the parameter in the selection criteria by relating it to one of the source table fields.
Parameter "%" is specified more than once in the selection
Batch Control Card
You specified the indicated parameter more than once in the selection string.
Change the selection string so that it refers to the parameter only once.
Parameter "%" of "%" has already been specified
Report Generator
You specified the indicated parameter name more than once.
Remove one of the duplicate parameter names from the input area.
Parameter "%" of table "%" is null or an empty string
Interpreter
You tried to access a parameterized table, but the parameter specified cannot be a null value or an empty string.
Ensure that the table parameter is neither null nor an empty string.
Parameter % does not match corresponding key attributes of parent table
Table Definer
For VSAM multiple record definition, each data parameter in the child table must correspond exactly to the keys in the parent table. In this scenario, you either entered an extra data parameter that does not correspond to keys in parent table, or the attributes do not match that of the parent.
Delete extra data parameters or correct the attributes to match that of the parent.
Parameter % is undefined
HLIPREPROCESSOR
The indicated parameter was not defined either in the Object Service Broker database or in the DEFINE TABLE statement.
Correct the definition or the access statement to refer to the correct parameter name.
Parameter % must be Type %, Syntax %, Length %
Table Definer
Parameter attributes are invalid.
Define parameter attributes as indicated in the message.
Parameter % of table % is incompatible with that on % system
Promotion
The specified table parameter is incompatible with the one on the specified system, so the APPLY process cannot proceed as requested.
On the source system, Unaccept the change and return it to the developer. The developer should roll back the change request and make the specified table compatible with the one on the target system. The change can then be re-extracted and reapplied to the target system.
Parameter does not exist in table %
HLIPREPROCESSOR
A parameter named in the DEFINE TABLE or access statement does not exist.
Correct the COBOL program to agree with the definition of the table.
Parameter error(s) for "%"
Builtin Routines
The indicated Object Service Broker routine encountered some unresolved error in an input argument or arguments.
Ensure that all the arguments are correctly specified. If they are, contact TIBCO Support.
Parameter length > 127; cannot be selected as parameter
Table Definer
You cannot choose a field that is longer than 127 bytes to be a parameter.
Use another line command so that the field is not selected as a parameter for the MetaStor/IMS table.
Parameter list specified for access on table "%" is too long
Builtin Routines
The total length of parameters in the table access is greater than 256 bytes.
Verify the supplied parameter values.
PARAMETER must be N for a rule that is called
Menu Definer
A rule that is called cannot be passed arguments; therefore, PARAMETER must be N.
Correct the value of PARAMETER.
Parameter MUST be the KEY of the first record in access path
Table Definer
If you want to define a parameterized IDM table, you must select the key of the first-level CA-IDMS record as the parameter.
Remove the P line command from the non-key element.
PARAMETER must be Y for EXECUTE_PARSE
Menu Definer
When you call the special rule EXECUTE_PARSE for your Standard Session Manager Menu, you must set the PARAMETER field to Y.
Enter Y in the PARAMETER field.
PARAMETER must be Y or N
Menu Definer
When ACTION is N, PARAMETER determines whether or not arguments are passed to the rule being executed. The choices are:
Enter a value in the PARAMETER field.
Parameter name "%" is already defined in parameter list
Table Definer
The indicated parameter is defined more than once in the same parameter section: once in the PARAMETER NAME field and once in the SOURCE PARM field.
Remove one of the duplicate parameter definitions.
Parameter name "%" is already defined in selection
Table Definer
The indicated parameter name was defined in both the selection section and the parameter information section of the current subview table definition.
Remove the indicated parameter name from either the selection criteria or the parameter information.
PARAMETER NAME must be specified for the FIND function
Unload
In INSTANCE SELECT you have requested a FIND. However, no parameter has been specified which should be searched for the pattern provided.
To use the FIND function, the name of the required parameter must be specified.
PARAMETER NAME must be specified for the SELECT function
Unload
You have requested to have parameter instances which match a pattern you have specified in the top area of the screen. You have not specified which parameter column to search for this pattern.
The FIND/SELECT functions will search only one parameter value column, so you must specify which parameter column should be searched.
Parameter not allowed for defn with only 1 record selected
Table Definer
You cannot define a single record access with as a parameterized table.
Change the parameter to a primary key.
Parameter of % table must be syntax %, length <= %
Table Definer
A parameter of the indicated type of table is restricted to the indicated syntax and the indicated maximum length.
Modify the syntax or length or both accordingly.
Parameter processing error
Batch Client
Client parameters are wrong.
Check the command line.
Parameter processing error
Start Execution Environment
An error occurred when the Execution Environment was processing the parameters.
Check the Execution Environment parameters.
Parameter selection for table "%" is not unique
TAM
A selection (WHERE clause or stored selection) contains an ambiguous predicate that mentions a table parameter. For example:
Example GET TABLE WHERE TABLEPARM = <value> AND TABLEPARM = <value2>;
Use the Rule Editor or Table Definer to remove the ambiguity. For example, change the above statement to:
Example GET TABLE WHERE TABLEPARM = <value>;
Parameter syntax of "V" not allowed.
Table Definer
Syntax of V is not valid for parameter.
Enter valid syntax for parameter.
Parameter value for the first table "%" must be specified
Report Generator
The Generator requires all parameter values to be specified for the first source data table.
Enter a value in the input area or select one from the prompt screen.
Parameter value list unavailable - "%" is empty
Report Generator
You cannot be prompted for parameter values because the source data table is empty.
You may want to put data in the table before you complete the report definition.
Parameter value list unavailable - no PRM table for "%"
Report Generator
You cannot be prompted for parameter values because a PRM table was not created for the indicated table.
You must type in the parameter values in the PARM VALUE field, or exit the Report Generator and create a PRM table for the indicated table.
Parameter values must be NULL when ALL DATA="Y"
Security
You are specifying a table instance by supplying parameter values either before specifying permissions to the instance, or while specifying table permissions for an object set definition. You have specified that ALL DATA = Y as well as filled in some values for the individual table parameters.
You must either specify ALL DATA = Y and leave all the parameter values blank (or null), or you must specify ALL DATA = N and supply values for each parameter.
Parameters cannot have access values
Table Definer
You cannot associate a parameter field with an IMS table access value.
If you want to select a field as a parameter and that field already has an access value associated with it, you must remove the access value before selecting the field as a parameter.
Parent Name "%" and type "%" must point to an object in list
Copy Definition
The name of the parent and its type for an object must also exist in the list exactly as specified.
Either enter the parent object, or set the parent only flag to N.
Parent Name "%" and type "%" must point to an object in list
Copy Defn/Data
You have requested to have copies of children referenced by the copy of the parent. However, the parent specified does not have as a child the entry which you specified for it.
Change the parent to be one that references the object copied from.
Parm#% must be name:% type:% syntax:% len:% dec:% class:%
Table Definer
The attributes of the parameter that you entered are different from that of the source. You cannot modify the attributes of the source parameter for a calculation (CLC) table.
Correct the parameter's attributes according to the message.
Parm name is %. Will not be able to create PRM tbl. Rename parm?
Table Definer
This is a warning message to inform you that, if the indicated parameter name is used in the table definition, you will not be able to create a PRM table based on it in the future.
Rename the parameter if you will be defining a PRM table based on the current table definition. Otherwise, you may proceed.
PARMS changes IGNORED; instance permissions already specified
Security
You supplied parameter values for the table instance specification in the Table Permissions screen of an object set definition. However, these specifications already exist in another entry for the same table; therefore, the changes are ignored.
Remove the entry because the table instance is already specified. If you want to change the parameter values, use the PARMS function on the table entry again and specify a different table instance.
Parms of defined Table in different order than one loaded
Unload/Load
The order of the table parameters from the import file is not the same as the order of parameters for the table in the target system.
Ensure that the parameter definition of the target table is the same as the source table.
PASSWORD and PASSWORD VERIFY are different; erase and reenter
Security
You made a request to save your user profile after changing the PASSWORD field (and possibly the VERIFY PASSWORD field). The verification failed because the value in the PASSWORD is different from the value in the VERIFY PASSWORD field.
Erase and reenter values in both the PASSWORD and VERIFY PASSWORD fields to ensure that the password is the same in both. Erasing the fields first is recommended because overstriking a long password with a shorter password causes the new password to retain the end of the old password.
PASTE such that field and literal are SEPARATED by blank
Screen Definer
In the Screen Table Painter, you tried to paste the content such that a literal would occur immediately adjacent to a field (i.e., literal is immediately to the right of the field). A blank must appear between the field and literal since blanks serve as field delimiters.
Choose another place to paste into:
Permission % is not valid for % %
Security
The specified object permission is not valid for the object which is being protected. For example, READ access does not apply to the SCREEN object type.
Correct the object permission.
Permissions cannot be specified for META-DATA tables
Security
You referred to a meta-data table while requesting to manage permissions to a table object, or while specifying table permissions for an object set definition. Permissions cannot be specified for these tables (e.g., TABLES, SCREENS, SCREENFIELDS, PARMS).
You must remove or change the entry from the table permissions specification of the object set by replacing the table name with blanks, nulls or another table name. If you need to specify permissions for a meta-data table, contact TIBCO Support.
PF key % is not supported
Global Cross Ref. Search
You pressed a PF key that is not supported on this screen.
Choose another PF key. The valid keys are listed at the bottom of the screen and you can press <PF1> for Help.
PF key % is not supported
Session Manager
You pressed a function key that is not supported by the session manager.
No action required.
PF key NOT supported INSIDE this window
Rule Editor
Rule Editor PF keys only function when the cursor is outside of the window.
Move the cursor and press the PF key again.
PHASE% failed: %
Promotion
Phase 1, 2, or 3 failed and the reason indicates which phase of the 3 apply phases failed and why.
Based on the reason, take appropriate action.
Phase 1 of Apply Completed
Promotion
Phase 1 of the target apply has completed successfully.
No action required.
Phase 2 of Apply Completed
Promotion
Phase 2 of the target apply has completed successfully.
No action required.
Phase 3 of Apply Completed
Promotion
Phase 3 of the target apply has completed successfully.
No action required.
Physical screen buffer overflowed
Screen Server
The output buffer containing data to be written to the screen is full and more data remains to be written.
 
1.
2.
Contact TIBCO Support with the log and an exact description of what actions were being performed when this message was generated.
Place an "S" on the option to be selected
Tool for IMS Data
A selection must be made.
Type an S beside the desired option and press <Enter>.
Place cursor %
Rule Editor
If this message is:
Example Place cursor on object to be expanded
the cursor is not on a valid token for you to press <PF14>. If the message is:
Example Place cursor on line to be scrolled
you selected a scroll amount of C, but the cursor is not on the body of the rule.
Do one of the following:
Place cursor on a menu option before pressing <Enter>
Security
You pressed <Enter> from the main menu without having the cursor on a valid option.
Place the cursor on a menu option and fill in the required information before pressing <Enter>.
Place cursor on an object
Global Cross Ref. Search
You pressed <PF6> to edit an object, but did not place the cursor on an object.
Place the cursor on the object that you want to edit and press <PF6> again.
Place cursor on appropriate entry then PF5 to edit or PF6 to add
National Lang. Support Mgr
Instructions to user.
None.
Place cursor on appropriate field
Session Manager
You pressed <Enter> when the cursor was not on a user entry field.
Move the cursor to an entry field before you press <Enter>.
Place cursor on field of your choice
Keyword Manager
The cursor was not on a field when you pressed <Enter>.
Choose any action by placing the cursor on the corresponding field and pressing <Enter>.
Place cursor on menu line to be deleted
Menu Definer
The cursor was not placed on a line of the menu items when <PF16> was pressed.
Position the cursor on the line to be deleted and press <PF16>.
Place cursor on row to be %
Table Editor
Your action failed because you did not position your cursor properly on a specific row or occurrence.
Position your cursor on a specific row and try again.
Place cursor on row to scroll to
Secure Audit Log
You specified C as the scroll amount but you did not place the cursor on the destination row when you pressed the scroll key.
Place the cursor on the row to be scrolled to and try again.
Place cursor on TABLE for which instances are to be SELECTED
Unload
In the UNLOAD first context, you have requested the INSTANCE SELECT function. However, the cursor is not positioned on an object entry.
Position the cursor on a row which names a table to unload, and then request the INSTANCE SELECT function.
Place cursor on TABLE for which you wish to specify parameters
Security
You requested the PARMS function while specifying table permissions for an object set definition, but the cursor is not positioned on an entry.
Position the cursor on a row containing a parameterized table name, and then request the PARMS function.
Place cursor on the field to %
Table Editor
You have pressed the <PF18> key (exclude field) or the <PF19> key (show field) without placing the cursor on a field.
Before pressing <PF18> or <PF19>, position the cursor on the field to be excluded or shown.
Place cursor on the menu line
Menu Definer
The cursor was not placed on a menu line when the PF key was pressed.
Position the cursor and press the PF key again.
Place cursor on the object you wish to define
Object Set Definer
You must first place your cursor on an object before you press <PF9>.
Place your cursor on the object you wish to define, then press <PF9>.
Place cursor on the table to be excluded
Report Generator
The cursor must be placed on a table name before <PF23> is pressed.
Move cursor to a table name, and press <PF23> again.
Place cursor on title line
Menu Definer
The cursor was not placed on a title line when a PF key was pressed.
Position the cursor on a title line and press the PF key again.
Place the cursor on a command
DEFINE_OBJLIST Tool
You pressed either <PF4> or <PF16> to insert or delete a command line, but you did not position your cursor on the line on which the operation is to take place.
Position your cursor on a specific command line and try again.
Place the cursor on a menu item before requesting OPTIONS
Security
You requested the OPTIONS function from the main menu, but the cursor is not on a menu item.
Position the cursor on the item for which you are requesting a list of options, and invoke the OPTIONS function again.
Place the cursor on an active segment, then press <PF6>
Statistics
The cursor is not positioned on a screen occurrence for an active segment.
Move the cursor to a screen occurrence for an active segment and press <PF6> again.
Place the cursor to indicate your choice
Menu Definer
The cursor was not placed in a field to indicate a choice.
Place the cursor and press <Enter>.
Please enter the export file name
Unload/Load
You did not provide an export file name on the entry screen.
Type in a preallocated export file name.
PLEASE SPECIFY A DATASET NUMBER; SEG-DSN-ENT
S6BTLADM - RPP DIRECTORY
In order to continue processing a segment and data set or a data set number must be specified.
Supplied the required input and retry your request.
PLEASE SPECIFY A MEMORY ADDRESS TO BE DISPLAYED
S6BTLADM - MEMORY DISPLAY
You must specify the memory address you wish to review.
Specify the memory address start point you wish to view and retry the request.
PLEASE SPECIFY A PAGE NUMBER; SEG-PAGE
S6BTLADM - PAGE IMAGES
The segment and page number must be input. If omitted the segment will default to 0.
Enter the segment and page number to continue.
Position cursor %
Table Definer
Invalid cursor positioning.
Position your cursor at the precise location on the screen as indicated by the message.
Position cursor in Image Area or on existing field definition
Screen Definer
You have pressed a context sensitive function key but the cursor is not positioned in either the Image Area, or the Field Definition Area.
Reposition the cursor.
Position cursor in paint area at row/col for new field origin
Report Definer
When requesting a COPY of fields from a table (which is not a report table), the cursor position indicates the target row and column for the first copied field.
Place the cursor at the row or column where the first field resulting from the COPY command is to be placed.
Position cursor on a field/literal defined in report table "%"
Report Definer
An EXPAND FIELD DEFINITION request was issued for a body table field from within the Report Table Painter for a break table, or when the cursor was not positioned on an appropriate defined field.
You can only request the expanded field definition for a body table field from within the Report Table Painter for the body table itself.
Position cursor on a LIST before you select objects
Definition Differences
You are trying to select objects for comparison but the cursor is not positioned at one of the two lists.
Position the cursor at one of the two lists and try again.
Position cursor on a valid report table or control break
Report Definer
When a Paint operation was requested, the cursor was not positioned on a valid report table or control break. Report tables and control breaks must be assigned names before they can be painted.
Position the cursor on a valid report table or control break.
Position cursor on field to be deleted
Report Definer
When requesting a DELETE operation for a report table, the cursor should be positioned on the report field which is to be deleted.
Position cursor on the report field to be deleted, and request the DELETE operation again.
Position cursor on GROUP entry before requesting VIEW GROUP
Security
You requested to view a Group without specifying the Group to view.
Position the cursor on a Group entry before requesting to view Group.
Position cursor on INSTANCE for which DETAIL is to be shown
Unload
You have requested to see an instance specification in detail by pressing the DETAIL function. The cursor is not positioned in such a way as to indicate which instance you wish to detail.
Position the cursor on the row where the instance required is located and then press the DETAIL function again.
Position cursor on starting field for offset calculation
Table Definer
Offset not calculated since cursor is not positioned on any field in the table definition.
Position cursor at the starting field where you want offset to be calculated.
Position cursor on the ITEM you wish to remove
General Table Definer
You have requested to remove an entry from some part of the core information about the MetaStor table you are defining. Your cursor is not positioned on an entry.
Position the cursor on the same row as the entry you wish to delete, then request to remove the item again.
Position cursor on the USERID you wish to DISCLAIM
Security
A Security Administrator in a SecAdmin profile disclaimed a userid without indicating (by the cursor position) which userid to disclaim.
Position the cursor on the userid to be disclaimed and try DISCLAIM again.
Position cursor on title of the list from which to DELETE
General Table Definer
You have requested to remove an entry from some part of the core information about the MetaStor table you are defining. You cannot remove these items, although you may update them.
Make the necessary updates to the items you cannot remove, or leave them as is.
Position cursor on title of the list to which to ADD
General Table Definer
You have requested to update information about the MetaStor table definition in the core context of the generic Table Definer. You cannot update the core information in this context.
Use the extensions context to update the core information as it is extended by the definition of the table type you are defining.
Position cursor within Paint Area at row/col requiring shift
Report Definer
When a SHIFT operation is requested, the cursor must be positioned within the Image Area. All report fields on the indicated row at or beyond the indicated column are then shifted left for negative shift numbers, and right for positive shift numbers.
Position the cursor in the Paint Area at the row and column desired for the shift.
Position the cursor on a Field Definition
Screen Definer
You have pressed a context specific function key in the Field Definition Area but not positioned the cursor on a field.
Reposition the cursor on the appropriate field.
Possible values for EXTRACT field are D, O, or A
Promotion
You have entered an invalid value in the EXTRACT field.
Change the value in the EXTRACT field to D, O or A.
PREFIX must have a valid leading character and must be a length of 3
Static SQL for DB2 Gateway
The 3 character prefix name for the static SQL handler name must start with an allowable character and must be three characters in length.
Correct and retry.
Preprocessing completed with possible errors - Please check Preprocessor output.
Host Language Interface
The Preprocessor has reported one or more errors which could possibly be caused by invalid source code.
Review the error messages in the Preprocessor output and take actions accordingly.
PRESENTATION ENVIRONMENT is required to unload SCREENS
Unload
You have requested to unload a screen; however, there is no presentation environment specified in the top portion of the screen. This information is required to fully specify the screen to be unloaded.
In the top area of the screen, type in the presentation environment.
Press <%> to confirm, or type "CONFIRM" at the command prompt
Rule Editor
This message will be appended to message 38 of this module. You have received a warning message about an action that is about to be performed on a rule.
Press the indicated PF key or type CONFIRM in the command line to perform the action. Press any other key to cancel the action.
Press <PF21> for Table Editor
Table Definer
You pressed <PF21> to edit table data. Normally the Table Definer saves the table definition and invokes the Table Editor right away. In this scenario, the Table Definer is unable to save your table definition under your default segment but has saved under segment 0. The purpose of this message is to inform you of the above, and to confirm your request to invoke the Table Editor.
Press <PF21> to invoke the Table Editor.
PRESS key TO ABANDON PENDING UPDATES AND request
S6BTLADM-Resource Management
The schedule screen currently has updates that have not been saved and your request will cause those updates to be lost.
Press the identified key to continue processing the identified request or any other key to abandon the request and preserve the pending updates.
PRESS PF10 TO CONFIRM COMMIT
S6BTLADM - INDOUBT TRX
You have requested the manual commit of the displayed indoubt transaction. Before the request is issued you are required to confirm your intentions.
Press PF10 to confirm your desire to commit the transaction, press any other function key to abandon it.
PRESS PF10 TO CONFIRM SCHEDULE UPDATE REQUEST
S6BTLADM-Resource Management
You have requested the pending changes be committed to the repository, before the request is issued you must confirm your intension by pressing PF10.
Press PF10 to continue the update request or any other key to abandon the request.
PRESS PF10 TO CONFIRM USER TRACE "OFF" REQUEST
S6BTLADM - USER ACTIVITY
Your have requested that the user trace for the displayed user be turned off. In order to verify your intention a confirmation is required.
Press <PF10> to issue the stop trace request. Press any other function key to abandon the request.
PRESS PF10 TO CONFIRM USER TRACE "ON" REQUEST
S6BTLADM - USER ACTIVITY
You have requested that tracing be started for the displayed user. In order to verify your intention <PF10> must be pressed.
Press <PF10> to issue the tracing request, press any other function key to abandon the request.
PRESS PF11 TO CONFIRM CANCEL USER REQUEST
S6BTLADM - USER ACTIVITY
You have requested a cancel user function. Before the request can be issued to the Data Object Broker you must confirm your intention by pressing <PF11>.
Press <PF11> to issue the cancel user request or any other function key to abandon the request.
PRESS PF11 TO CONFIRM OPERATOR COMMAND -
S6BTLADM - OPERATOR FUNCT
You have selected the indicated operator function. In order to issue the request you must first confirm your intentions by pressing <PF11>.
To issue the request press <PF11>, to abandon the request press any other function key.
PRESS PF11 TO CONFIRM RESOURCE DETAIL ENTRY DELETE
S6BTLADM-Resource Management
You have requested the deletion of the Resource detail entry currently being displayed. In order to continue with the processing the request must be confirmed by pressing <PF11>.
Press <PF11> to continue with the Resource Detail entry delete or any other key (i.e. <Enter>) to abandon the request.
PRESS PF11 TO CONFIRM SCHEDULE DELETION REQUEST
S6BTLADM-Resource Management
Before preparations to delete the schedule are performed you must confirm your intensions by pressing PF11.
Press PF11 to continue with Schedule deletion preparations or any other key to abandon the request. NOTE: after the delete is confirmed press PF10 to complete the delete processing.
PRESS PF11 TO CONFIRM STOP REQUEST FOR PATH user-id
S6BTLADM-Resource Management
Before the system will continue to process the requested stop gateway/server, your intensions must be confirmed by pressing <PF11>.
Press <PF11> to confirm your desire to stop the identified path or any other key (i.e. <Enter>) to abandon the request.
PRESS PF11 TO CONFIRM THE DETAIL ENTRY INSERT/UPDATE
S6BTLADM-Resource Management
You completed valid changes to the Detail entry and requested the saving of the changes.
Press <PF11> to confirm your request or any other key (i.e., <Enter>) to abandon the request.
PRESS PF11 TO CONFIRM YOUR STOP REQUEST FOR ALL RESOURCES WITH TYPE = type
S6BTLADM-Resource Management
You have requested that all gateways/servers with the identified type be stopped. Before the request can be honored you must confirm your intensions by pressing <PF11>.
Press <PF11> to confirm the stop request or another key to ignore the stop request.
PRESS PF11 TO CONFIRM YOUR STOP REQUEST FOR ALL TYPE = type,GROUP = group
S6BTLADM-Resource Management
You have requested a stop server for all resources in the specified type and group. Before the request is sent to the gateway/server, you must confirm your desire to stop the active paths.
Press <PF11> to continue with the request or another key (i.e., <Enter>) to abandon the request.
PRESS PF11 TO CONFIRM
S6BTLADM - SEGMENT/DASD
You have requested an operational type function that will affect the processing in the Data Object Broker. In order for that request to be submitted, a confirmation of the action is requested.
Press PF11 if you wish the function invoked or any other function key if you wish to abandon the request.
Press PF2 for more.
General
More information is in a message log.
Press the <PF2> key.
Press PF2 for status report
Promotion
Indicates what key to press to see the audit trail of actions performed as a result of the object command entered.
Press <PF2> to see the audit trail.
Press PF2=LOGS for report on UNLOAD
Unload
You have requested to UNLOAD and specified which objects to unload and then pressed <PF3> to unload and exit. A report was created to confirm what was unloaded; it is available via <PF2>.
To see the UNLOAD report, press <PF2>.
PRESS PF4 TO GENERATE REQUEST FOR
S6BTLADM - DIAGNOSTIC DUMP
Your dump request has been received. Press PF4 to send the request to the Data Object Broker to have the specified dump generated.
Press PF4 to send the dump request or any other function key to abandon the request.
PREV OR NEXT REQUESTED BUT NO PAGE CURRENTLY DISPLAYED
S6BTLADM - PAGE IMAGES
You have requested a scrolling function; however, there is currently no page image being processed.
No action required.
PREVIOUS BUFFER REQUESTED FROM DISPLAY OF FIRST BUFFER
S6BTLADM - MEMORY DISPLAY
You are processing a pool buffer display. The buffer currently displayed if the first buffer. The previous buffer function cannot be honoured.
No action required.
PREVIOUS BUFFER REQUESTED FROM DISPLAY OF FIRST BUFFER
S6BTLADM - PAGE DISPLAY
PF10 has been used to request the previous buffer whilst the first resident page buffer is displayed
No action required.
Previous message(s) returned from location "%"
TAM
Advises that messages previous to this one in the message log came from the named location. Remote messages referred to by this message are flagged with the characters " >" in columns 1 and 2.
This message is produced only during distributed data transactions.
As indicated by the remote messages returned.
Primary command % not supported
Field Dictionary
You entered a command that is either misspelled or does not exist.
Press <PF1> for a list of valid commands.
Primary KEY can not be chosen from the parameter record
Table Definer
For parameterized IDMS table definition, the primary key must be defined on the second level.
Define primary key on the second level of your access path.
Primary key cannot be on Owner record for parameterized table
Table Definer
You have made an invalid primary key selection.
Make the necessary corrections.
Primary key field must be mapped if not IDGEN
Batch Control Card
The primary key of the table to be loaded is not IDGEN and all of the key fields are not mapped to fields of the input file.
Either map all of the key fields to fields of the input file or define the primary key of the table to be IDGEN.
Primary key must be in second level record for parameterized table
Table Definer
You have defined the first record in the access path as a parameter; therefore, the primary key must be defined in the second record.
Choose primary keys from the second-level IDMS record in your table definition.
Primary key must be in second level record for PARM table
Table Definer
For a parameterized IDM table definition, the primary key must be defined in the second record in the access path.
Define the primary key in the second record in the access path. Or, alternately, remove the parameter definition.
Primary key must be in the highest level record
Table Definer
If the CA-IDMS access path is composed of multiple records, you must select the primary key from the first level.
Remove the primary key field selection and select a primary key field from the first level.
Primary key must be the first field
Table Definer
The primary key must start from the first field.
Move the field that you want to designate as a primary key to the top of the list of fields.
Print access of REPORT % by % denied
Audit Log Message
PRINT access to a report object was denied.
The user can ask someone who has CONTROL access to the report to provide PRINT access.
Print definitions for object "%" type "%" completed
Print Definition
You are trying to print an object and an object, which is defined by the object you specified, is printed.
No action required.
Print definitions for object "%" type "%" partially completed
Print Definition
Not all definitions of the specified object are printed.
Read the message log and find out why all the definitions were not printed. Fix the problems and try the operation again.
Print destination must be "PRT" or "SCR"
Print Table
The print destination has some other value than PRT or SCR.
Make the output destination the printer (PRT) or the screen (SCR).
Print failed: %
Rule Editor
Internal error during printing.
The message log will contain a more detailed error message.
 
1.
2.
Contact TIBCO Support with the log and a description of what actions were being performed when this message was generated.
PRINT failed: %
Screen Definer
You have tried to print out a virtual layout and screen definition. For security reasons you are not allowed to do this, for the named screen.
No action required.
Print of report "%" failed; keyed data access not supported for external files
Report Server
The Report Server detected an inconsistent server action.
Contact TIBCO Support.
Print successful
Promotion
The print operation you started has completed successfully.
No action required.
Print successful
Secure Audit Log
The specified selection list was printed as a result of the PRINT command.
No action required.
PRINTDEFN failed, security failed on object "%"
Print Definition
You want to print an object. However, you do not have the authority to access an object which is required by PRINTDEFN to print your object.
Find out what those objects are and ask the owners if they could give you access to those objects. Retry the operation again.
Printed %
Print Table
A table was printed.
No action required.
PRINTED definition of table "%"
General Table Definer
You requested to print the definition of the table and the request has been sent to the output.
No action required.
PRM table is not available for parameter "%" of table "%"
Report Generator
This message shows that there is no PRM table existing for the specific parameterized table.
Using the Table Definer, create the PRM table for the parameterized table.
Processing Execution Environment startup parameters
Start Execution Environment
The Execution Environment is processing startup parameters.
Wait until the Execution Environment is finished the processing.
PROCESSING FAILURE REPORTED FOR REQUEST (___), REASON CODE IS __
S6BTLADM-Resource Management
When attempting to extract information from the Data Object Broker, an error was detected. In the message, the request code is one of the following:
The reason code is one of the following:
This error typically represent an internal error which should be reported to TIBCO Support. Before contacting Support review the joblog to determine what messages were produced to help identify the problem. In the case of a reason code 44 recycle the Data Object Broker, storage allocation is based on defined configuration, you are trying to expand the configuration beyond the allocated buffer zone.
PROFILE EXTRACT RETRIEVAL ERROR
S6BTLADM - COMMON MESSAGES
When attempting to obtain statistics for a profile display the retrieval failed.
Review the job log for additional information and retry.
Program abnormally terminated with code=%
Interpreter
This message is used by the program that produces the Object Service Broker Information Log. More detailed messages usually follow.
Read the detailed messages that follow.
Program ADALNK must be in EXLIB library concatenation
Adabas Extract
Server is unable to locate program ADALNK.
Add program ADALNK in EXLIB library concatenation.
PROM_TYPE must be "DATA"
Promotion
Field RIGHTS of table @RULE_RIGHTS must be set to the character string DATA.
Correct the field.
Promotable flag set to % for % % %
Promotion
You have toggled the value of the PROM field for the specified table. This field indicates whether a table is promotable or not. If you wish to change the value, use the T line command to toggle it back.
No action required.
Promote selected for % % %
Promotion
You have selected the specified object for promotion. This object is now included in the change request. It will be promoted when the change request is promoted. If you do not wish this to happen, use the C line command to remove it from the request.
No action required.
Promoted %
Promotion
The specified number of objects have been promoted to the target system.
No action required.
Promoted data for % tables or table instances
Promotion
The data of the specified number of table or table instances has been promoted to the target system.
No action required.
Promotion FAILED; @BORROWED_OBJ entry for object % not found
Promotion
Borrowing rights on the object named were released before the promotion was completed. The system may be in an inconsistent state.
Contact TIBCO Support.
Promotion of change#% failed
Promotion
The promotion of the specified change has failed. The cause of the failure can be found in the message log of the promotion.
Correct the problem described in the message log and apply the change again.
Promotion request %
Promotion
The promotion request was saved or canceled.
No action required.
Promotion request % does not have the appropriate status
Promotion
Cannot accept a change request unless the status is P. Cannot extract a change request unless the status is A or X.
Change the status of the change request before proceeding with the promotion.
Promotion request marked incomplete
Promotion
The user has pressed <PF3> and saved the change request as incomplete (Status=I). This has saved the intentions on objects as well as any description.
The user can resume preparing this change request at a later time by entering C against the CR number on the Manage Incomplete/ Pending screen.
Promotion rights for % % lost
Promotion
In order to submit the CR, you need promotion rights on the named object. Either you have released/transferred rights on the object, or you have deleted the named object, or you are continuing the CR from a different library.
Check if you need this object to be part of the CR, and if so, ensure you have rights on the object.
Promotion rights held by % - requested by %
Table Definer
The promotion rights of the current table definition are held in the indicated library by the indicated user.
If you want to modify the table definition, contact the indicated user to have the rights released.
Promotion rights not obtained %
Rule Editor
You do not have promotion rights for this rule and therefore you cannot promote this rule to the development library. Possible reasons:
You have created a new rule and renamed it to the name of a rule that already exists in the development library. You do not have promotion rights to this rule.
Obtain promotion rights, if possible.
PROMPT must be N for a rule that is called
Menu Definer
A rule that is called cannot have arguments; therefore, PROMPT must be N.
Correct the value of PROMPT.
PROMPT must be O or N for EXECUTE_PARSE
Menu Definer
When you call the special rule EXECUTE_PARSE for your Standard Session Manager menu, you must set the PROMPT field to O or N.
Enter O or N in the PROMPT field.
PROMPT must be one of O, P, N
Menu Definer
When ACTION is N, the PROMPT field requires a value to determine whether prompting is needed or not. The choices are:
P - Prompting asks for the parameters of the rule, using the actual names of the parameters
N - No prompting is done. The rule is passed NULL values for each parameter.
Enter the O, P, or N in the PROMPT field.
PROMPT_RULE must be one of %
Menu Definer
Only certain rules can be used for prompting.
Choose a rule from the list presented.
Prompting cannot be "Y" for a protected field
Screen Definer
If the PROTECT attribute for a screen table is Y, the AUTOPROMPT and USERPROMPT attributes cannot be Y.
Change either the PROTECT attribute, or the AUTOPROMPT and USERPROMPT attributes.
Protocol error obtaining definition for table "%"
TAM
The size of the parameter name is not equal to 16.
This is an internal error; contact TIBCO Support.
Provide a database name; press <PF4> for DB NAMES
Table Definer
You did not enter an IMS database name in the DB NAME field.
Enter a valid IMS database name, or press <PF4> for a list of valid names and select one from the list.
Provide a JCL name
Batch Submission Tool
No JCL name was specified on the batch submission screen.
Enter a valid JCL name or press <PF2> to get a list of all valid JCL names.
Provide a queue name
Batch Submission Tool
No target batch queue name was specified on the batch request submission screen.
Enter a valid queue name or press <PF2> to see a list of valid queue names.
PSW at time of error % % ILC # INTC %
Interpreter
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.
Purge and archive cancelled
Secure Audit Log
You canceled the purging and archiving of the audit log contents.
No action required.
Purge batch processing finishing
Secure Audit Log
This message informs you that the purging of the audit log contents in batch mode has been completed.
No action required.
Purge batch processing starting
Secure Audit Log
This message informs you that the purging of audit log contents in batch mode has started.
No action required.
Put cursor on any Break/Summary section & press % to continue
Report Generator
You selected a function-field pair in the prompt area of the Function screen, but you did not move the cursor to a break/summary section to indicate where to insert the selected function-field pair.
Use the cursor to indicate where to insert the selected function-field pair, and press the indicated key to complete the specification.
Put cursor on break event in Breakevent Control section
Debugger Utility
You have pressed <PF6> to associate a debugger command with a break event. However, the cursor is not positioned in the primary command area nor on a break event.
Verify the position of the cursor.
Put cursor on Print/Sort/Break/Across & press % to continue
Report Generator
You selected a field in the prompt area of the Field screen, but you did not move the cursor to a section (PRINT, SORT, BREAK, or ACROSS) to indicate where to insert the selected field.
Use the cursor to indicate where to insert the selected field, and press the indicated key to complete the specification.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved