The module identified by "taskname" received an event to process "xxxx" and the Data Object Broker started the termination process. The "termtype" value can be either "NORMALLY" indicating a SHUTDOWN request was issued or "ABNORMALLY" indicating a task abended. The requested event processing is ignored.
The Data Object Broker requested a dump. The dump which is generated by the SDUMP macro was not successful for the return and reason code provided in the message. Review the SDUMP macro document in the IBM Authorized Reference Manual.
This message is present to identify the Object Service Broker Data Object Broker for both a VTAM application identifier and peer Object Service Broker node name used for distributed data access.
In the run time parameters for the Data Object Broker, you specified a nonzero value for the SMF27INTERVAL Data Object Broker parameter (default 0) and the SMF24INTERVAL parameter was nonzero (it defaults to 30). Data Object Broker processing does not allow the creation of both the default response time SMF record (SMF24) and the extended response time SMF record (SMF27). If you require the extended response time record, the SMF24INTERVAL parameter must explicitly be set to zero. If you want to use the default response time record, either omit the SMF27INTERVAL parameter or explicitly set it to zero.
This message appears at the time of Data Object Broker shutdown and the number in the message is the highest number of end users connected simultaneously to this instance of the Data Object Broker.
The Object Service Broker Data Object Broker is executing from an Authorized library. The following features are available to assist performance and tuning when you execute. Object Service Broker from an Authorized library:
SMFRECORD=### was specified as a Data Object Broker initialization parameter with a valid value between 128 and 255. No internal SMF recording is possible because the Data Object Broker is executing from a data set or concatenation that is not Authorized.
If Object Service Broker internal SMF records are required, the Object Service Broker Data Object Broker load library must be Authorized. Contact the System Programmer responsible for Object Service Broker installation.
Object Service Broker manages its own storage in blocks referred to as pools. When attempting to acquire storage to support, the specified pool the storage was not available.
During Data Object Broker initialization, it was determined that the Data Object Broker was not executed in an APF Authorized state as required. The Data Object Broker will abend with user code 33.
When acquiring storage to build the pool used to retain connection information (COMMPOOL) the storage was not available above the line. The COMMPOOL must reside above the 16 MB line in order to support some processing issues.
During Data Object Broker initialization, a failure was encountered in obtaining Virtual Storage. The job will abend with user code 38.
During Abnormal Termination of the Data Object Broker, the ESTAE routine was not provided with an SDWA from RTM. Due to this, the ESTAE routine was unable to report on the cause of the ABEND.
During Abnormal Termination of the Data Object Broker, the ESTAE routine was unable to locate certain control blocks needed for cleanup processing. Due to this circumstance, certain fixed storage pools will not be release back to the system.
Certain portions of REAL storage will remain unavailable to the system until an IPL is performed. If the amount of storage occupied by these orphaned control blocks causes system performance problems, an immediate IPL may be required. Contact System Programming and/or Operations staff for further assistance.
A dynamic allocation error occurred during initial or subsequent allocation of a SYSOUT file to receive copies of all WTO messages issued by the Data Object Broker. For an explanation of the codes, refer to the appropriate IBM manual that describes dynamic allocation (SVC99) and its functionality.
The Object Service Broker SRB program responsible for Pagestore I/O functions has abnormally terminated. The Data Object Broker is terminated as this failure may cause a loss of data integrity. User abend code 77.
A severe error occurred during the indicated subtask. The Object Service Broker Data Object Broker terminates abnormally. S___ is the system abend code and U___ is the Object Service Broker abend code.
If an Object Service Broker return code is provided, look at previous console messages for more information. If only a system return code is provided and you cannot resolve the problem based on this code, contact TIBCO Support.
The Data Object Broker has abended as described in the message. If a SYSxDUMP data set was allocated to the Data Object Broker, it will contain the dump for the error.
An INITPARM DD statement was provided but failed to open properly. Data Object Broker initialization continues. Parameter values are default values unless a PARM= string containing override values is provided.
An INITPARM DD statement was provided, but its record format was not fixed block, or its record length was not 80. Data Object Broker initialization continues. Parameter values are default values unless a PARM= string containing override values is provided.
The MAXDISPLAY parameter specified a value that was greater than the setting of MAXUSERS. It is not possible to have more users on than MAXUSERS, therefore the Display CICS limit is reduced to the MAXUSERS level.
The indicated parameter was abbreviated so that it is no longer unique. The parameter is rejected. Object Service Broker startup terminates abnormally.
You can spell Data Object Broker parameters in full or abbreviate them through truncation. For example, SNAPOVERRIDE or SNAPOVER or SNAPO are all accepted. Excessive truncation, however, results in abbreviations that can be one of several parameters. For example, SNAP might be any one of SNAPCLASS, SNAPREMOTE, SNAPQUERY, SNAPOVERRIDE, or SNAPVOLSER.
Spell the parameter keyword name more fully or completely. In general, five characters are sufficient to achieve uniqueness. Refer to the Installation and Operations manual if necessary.
The indicated parameter (only the first 13 characters appear in the message) is not defined to Object Service Broker. You may have used an unrecognizable abbreviation. The parameter is rejected. Object Service Broker startup terminates abnormally.
Verify the spelling of the parameter. Refer to the Installation and Operations manual if necessary. Abbreviation through truncation is permitted, but it is recommended that at least the first five letters be supplied to ensure uniqueness.
The indicated parameter used to be functional in a previous Object Service Broker release but has been superseded. The parameter is ignored. Object Service Broker initialization continues.
Update the file referenced by the INITPARM DDNAME in your Object Service Broker Data Object Broker JCL, or by the PARM= string in the Object Service Broker EXEC statement to discard obsolete parameters.
The keyname specified was a recognized Object Service Broker Data Object Broker parameter, but it is not eligible for modification after startup or once set. The parameter change is rejected. Object Service Broker execution continues.
If the parameter must be changed then this change must be made to the Object Service Broker Data Object Broker initialization parameters and will take effect the next time Object Service Broker is restarted.
The parameter name listed is compulsory and the Object Service Broker Data Object Broker cannot be initialized successfully without it. Object Service Broker Data Object Broker startup terminates abnormally.
The indicated parameter does not have an associated assigned value. All Data Object Broker parameters are of the form: keyword=value. Spaces are not permitted between the keyword, equal sign, or value. The parameter is rejected. Object Service Broker Data Object Broker startup terminates abnormally.
The value assigned to the parameter has failed its edit validity check. This occurs for any non-alphanumeric value, or for a discrepancy between edit specifications and the input provided. The parameter is rejected. Object Service Broker startup terminates abnormally.
The value assigned to the parameter has failed its validity check. A data set name or qualifier, member name, or other entity with similar syntax was expected. The parameter is rejected. Object Service Broker startup terminates abnormally.
The value assigned to the parameter is too big or too small. The parameter is rejected. Object Service Broker startup terminates abnormally.
The special value of 9999 for the indicated interval parameter is no longer supported. This value was used in previous releases to disable the indicated parameter. Effective with this release, a value of 0 is used to disable an interval value. This message is only a warning. The indicated parameter is still disabled.
Refer to the Job message log for preceding specific parameter error(s). Refer to the Object Service Broker Documentation for parameter syntax, spelling, ranges, defaults.
During the initialization of the Data Object Broker, it was determined that the number of resident CTABLEs was too low for the maxthread limit set. In an attempt to keep physical CTABLE builds to a minimum, the CTABRESIDENT parameter value has been overridden. The value is increased to the maxthread limit or the maximum allowable resident CTABLEs, whichever is lower.
The PAGESWEEPACTION specifies that an SMF record should be cut and the PAGESWEEPLIMIT threshold is exceeded.
An Object Service Broker transaction has aborted. Depending on the type of database access (QUERY/COMMIT) and the settings of the control flags (SNAPQUERY/SNAPOFF) a snap dump may be produced for diagnosis. Object Service Broker standard recovery is taken.
Look for and investigate associated write-to-operator messages and any snap dumps. Corrective action is indicated if messages are frequent or related to important tables, or if application problems result.
This message accompanies a transaction abend in order to help identify the problem. Included in the message is the: transaction type, transaction number, userid, requested segment id, requested page number , calling program and table name.
A dynamic allocation error occurred for an Object Service Broker snap dump SYSOUT file. The snap dump cannot be printed. Object Service Broker execution continues. The first code is the error reason code, and the second code is the information code. For an explanation of the codes, refer to the appropriate IBM manual that describes dynamic allocation (SVC99) and its functionality.
Look up the codes and take corrective action, if possible. Operator MODIFY commands are available to change the SYSOUT class (SNAPCLASS) or remote printer (SNAPREMOTE). Contact the System Programmer responsible for Object Service Broker if the problem persists.
A dynamic allocation error occurred for an Object Service Broker snap dump data set. The snap dump cannot be printed. Object Service Broker execution continues. The first code is the error reason code and the second code is the information code. For an explanation of the codes, refer to the appropriate IBM manual that describes dynamic allocation (SVC99) and its functionality.
Look up the codes and take corrective action, if possible. Operator MODIFY commands are available to change the target volume (SNAPVOLUME). Contact the system programmer responsible for Object Service Broker if the problem persists.
to direct snap dumps to a data set and compare results. Contact TIBCO Support if the problem persists.
to direct snap dumps to a SYSOUT class and compare results. Contact TIBCO Support if the problem persists.
Trial allocation of a snap disk data set failed and SNAPs are routed to SYSOUT. Some routine causes of this problem include:
If the USEREXIT parameter value was Y then the user exit initialization module was not found during system initialization. If the USEREXIT parameter value was N then the user exit initialization module was found during system initialization. System initialization is terminated.
The XCF control task has not started. Other messages will indicate the reason for this failure. Data Object Broker initialization will be terminated
XCFTASK received an event to process "xxxx" and the Data Object Broker had started the termination process. The "termtype" value can be either "NORMALLY" indicating a SHUTDOWN request was issued or "ABNORMALLY" indicating a task abended. The requested event processing is ignored.
Other messages will have been issued indicating the reason for the failure. If you are still unable to determine the cause of the switch failure contact TIBCO Support. The system will terminate the switch process
A SWITCH is in progress and some members of the XCF group have not completed the SWITCH in a timely manner. A list of members delaying the switch completion follows this message.
See also messages KS420, KS421 and KS422 for details. Either terminate the Secondary Data Object Broker and correct the error or if a SWITCH is to be allowed ignoring the differences then use SWITCH command ALLOW option to ignore the differences. WARNING only do this if you are sure that the differences will not impact the system. For example to increase the number of users, buffers or to add extra datasets to the DBD. Attempting to reduce any of the parameters may cause the system to fail.