During Object Service Broker startup processing, certain database initialization errors were detected. Other messages have already indicated the environmental errors. Object Service Broker terminates abnormally with abend code 301.
Object Service Broker database initialization completed successfully at system startup. For cold starts, the active database configuration is as defined in the DBDLIB. For warm starts, the active database configuration is the same as it was when the system abnormally terminated.
No action required. If active Object Service Broker segments are subsequently required for BATCH operations, they must be manually shut down with Object Service Broker console commands before the BATCH jobs are submitted.
Object Service Broker detected a VSAM error. The error was intercepted and the request code (REQ), return code (RC), feedback code (FB), macro return code (R15), and the address of the failing record (RBA) are shown in the message. Standard z/OS system messages of the form IECxxxI precede the Object Service Broker message.
During transaction cleanup processing, a transient work area was not returned to the buffer pool. Object Service Broker continues to run, possibly with degraded resources. Cumulative error counts are available in the BUFFER pool displays.
During start-up validation of the Data Object Broker, it was determined that the primary and duplex REDOLOG data set definitions are different, that is, either the Control Intervals or the allocated spaces are not identical.
During the freeing of locks, the RPE LOOKUP routine compared the owner of the page to be freed with the requestor. The request failed because the owner and requestor did not match.
An attempt has been made to use a DBD library which is incompatible with the version of Object Service Broker being executed. The Data Object Broker or utility program is terminated.
An error occurred while writing to the REDOLOG. A previous S6BDB026W message was issued detailing the nature of the error. If it is a physical error, the write is retried once. When this error occurs during system initialization or on the last available REDOLOG data set, the system is terminated and a subsequent S6BDB027A message is issued. If a DUPLEX REDOLOG data set is available and DUPLEXLOGFAIL is set to CONTINUE, system processing continues using the remaining data set.
If system operation continued, prior to the next restart of the system it will be necessary to re-synchronize the two redolog data sets as outlined in the Object Service Broker Backup and Recovery for z/OS manual.
An error occurred while writing to the REDOLOG. A previous S6BDB026W message appeared detailing the nature of the error. If it is a physical error, the write is retried once. When this error occurs during system initialization or on the last available REDOLOG data set, the system is terminated and a subsequent S6BDB027A message is issued. If a the REDOLOG data set is available and DUPLEXLOGFAIL is set to CONTINUE, system processing continues using the remaining data set.
If system operation continued, you must re-synchronize the two redolog data sets prior to the next restart of the system, as outlined in the Object Service Broker Backup and Recovery for z/OS manual.
This message results from the I/O error mentioned in message S6BDB026W. The system retries once, and then stops logging. If the problem is with the redolog, the system shuts down. If the problem is with logging to anything else, processing carries on as usual. The variable portion of the message text indicates which log encountered the I/O error.
Contact your Object Service Broker system administrator. Recovery from loss of the REDOLOG requires manual intervention as detailed in the Object Service Broker Backup and Recovery for z/OS manual. The minimum action required is the formatting of the REDOLOG/DUPLEX data sets.
Object Service Broker startup processing, or an Object Service Broker utility program, is unable to open the DBDLIB. This message is accompanied by standard z/OS messages indicating the DDNAME and reason code. Object Service Broker terminates abnormally.
An error was encountered while opening the VSAM data set specified in message S6BDB090I or S6BKX002I. All Object Service Broker Pagestores and journals, and the redolog, are opened at initialization. Object Service Broker Pagestores can be reopened dynamically using the DBONLINE command. Journals are reopened at the conclusion of SPIN processing. The VSAM OPEN return codes are documented in z/OS DFP VSAM Macro Instructions. Object Service Broker online processing continues without the segment becoming available, or in the case of an Object Service Broker offline utility, processing is terminated.
The Pagestore segment indicated in message S6BDB092I is not available to Object Service Broker. Additional Object Service Broker or IBM messages have already been displayed to indicate the exact cause of error. Object Service Broker processing continues unless the base segment has failed.
Initialization of the Object Service Broker redolog failed. Additional Object Service Broker or IBM messages have already been displayed to indicate the exact cause of error. Object Service Broker terminates abnormally.
When trying to open the contingency log (Redolog.pending), the system could not locate a catalog entry for the data set. The Data Object Broker initialization fails with a U049 abend.
Segment 0 or a segment which has been defined in the DBGEN as Required by the system cannot be initialized. Object Service Broker terminates abnormally since the required meta-data is not available for Object Service Broker transaction processing.
NOTE: All segments previously online must be available after an abnormal termination.
During Data Object Broker initialization, Object Service Broker was not able to obtain the virtual storage needed for the SMF subtype 13 record.
During segment activation, the data set as indicated in message S6BDB090I or S6BKX002I does not contain the correct segment ID as specified in the DBGEN. Object Service Broker startup continues, but does not activate this segment, or in the case of an offline utility, processing is terminated.
The segment and data set as previously displayed (S6BDB092I, S6bDB090I) have not been properly configured for Object Service Broker use.
During segment activation, the data set as indicated in message S6BDB090I or S6BKX002I does not contain the correct page number as specified in the DBGEN at Object Service Broker startup.
During segment initialization, indicators were found within the Pagestore data set that indicate that a restore was started but failed to complete successfully.
An Object Service Broker user requested a free page, but aborted the transaction before the page was used. When processing was aborted, the File task validated the free page to ensure that the owner of the page and the user running the current session are the same. This message is issued because the page owner and the user are not the same.
The File task received a request to free a lock. During this process, the File task ensures that the page for which the lock is being released is owned by the same user who is running the current session. This message is issued because the page owner and the user are not the same.
A shutdown of segment number:name was requested, but the segment is still active. The shutdown request is deferred until the next checkpoint is taken.
During Data Object Broker Initialization, there is not enough storage available to construct the Resident Page Pool to the size specified in the RESIDENTPAGES parameter.
The Data Object Broker attempts to continue initialization with a reduced number of resident pages. The message "RESIDENT PAGE REQUESTED..." indicates the number of resident pages available to the Data Object Broker. Increase the amount of Virtual Storage available to the Data Object Broker.
The requested size of the Resident Page Pool as requested via the RESIDENTPAGES initialization parameter, and the number of Resident Pages obtained are displayed in this message.
OPEN '________.________.________.________.________'
This message appears during Data Object Broker initialization. It identifies the data set names of the database segments, journals, redolog, Statistics Log, and any other control files that are active for this Object Service Broker Data Object Broker. These data set names were defined in an Object Service Broker DBGEN. They are stored in a VSAM data set, the Data Object Broker DBDLIB.
When obtaining a free page for the segment, the Object Service Broker system detected that the space utilization threshold for the indicated segment has been exceeded. This message will be repeated for every increment defined in the DBGEN entry for the segment up to 100% unless implicit or explicit corrective actions bring it below the minimum allowable threshold.
This message indicates that the space utilization for the segment had earlier increased beyond the warning threshold but has now come back to below this threshold.