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


Using Messages With Identifiers : DB: File Task

DB: File Task
S6BDB001E
FILE INITIALIZATION FAILED
File Task
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.
Investigate the relevant messages and take corrective action. Contact the System Programmer responsible for Object Service Broker.
S6BDB002I
FILE INITIALIZATION OK
File Task
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.
S6BDB003W
UNKNOWN VSAM EVENT COMPLETED
File Task
Internal logic error. A VSAM request that the Object Service Broker supervisor does not recognize has completed.
Contact TIBCO Support.
S6BDB004W
VSAM HEX REQ=__ RC=__ FB=__ R15=________ RBA=________
File Task
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.
Contact the Object Service Broker system administrator. Reason codes are documented in z/OS DFP VSAM Macro Instructions. z/OS messages are documented in the z/OS System Messages manual.
S6BDB005E
UNDEFINED EVENT CODE X'____'
File Task
Internal logic error. Object Service Broker supervisory code detected an invalid system service request. The transaction is aborted.
Contact TIBCO Support.
S6BDB006I
DSN=________.________.________.________ ...
File Task
This message is issued to indicate the name of the data set associated with a failed I/O request.
No action is required for this message. Refer to preceding messages for details of the failure.
S6BDB007W
FREBUF ERROR FOR PAGE QUEUE
File Task
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.
Contact TIBCO Support.
S6BDB008W
INVALID FILE REQUEST
File Task
Internal logic error. The Object Service Broker COMMIT processor detected an invalid system service request. The transaction is aborted.
Contact TIBCO Support.
S6BDB009W
LOGGING ERROR - COMMIT ABORTED
File Task
I/O errors were detected during normal logging operations. The COMMIT transaction was aborted.
See the accompanying messages for details about the error. Contact TIBCO Support.
S6BDB010E
REDOLOG PRIMARY AND DUPLEX CI-SIZE/DATASET SIZE DIFFERENCE DETECTED
File Task
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.
The Data Object Broker cannot initialize.
Correct the difference and retry.
Note: If the REDOLOG is to be redefined, ensure the CACHE is redefined as well.
S6BDB013W
ERROR DURING RESIDENT PAGE LOOKUP
File Task
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.
Contact TIBCO Support.
S6BDB015W
SESSION NOT ON DEFERRED PAGE QUEUE
File Task
During session cleanup, no deferred page requests were found on the queue. The system continues processing.
No action required.
S6BDB016I
SESSION REMOVED FROM PAGE QUEUE
File Task
The session was removed.
No action required.
S6BDB017I
CLEANUP DONE - FREE SESSBUFF
File Task
A cleanup was performed; session buffers are free.
No action required.
S6BDB018E
INVALID DBD RELEASE IDENTIFIER
File Task
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.
Regenerate the DBD using the correct release of Object Service Broker and re-execute the failing program.
S6BDB020A
REDOLOG WRITE ERROR
File Task
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.
Contact your Object Service Broker system administrator.
If the system was terminated, follow the action outlined for message S6BDB027A.
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.
S6BDB021A
REDOLOG DUPLEX WRITE ERROR
File Task
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.
Contact your Object Service Broker system administrator.
If the system was terminated, follow the action outlined for message S6BDB027A.
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.
S6BDB026W
VSAM LOG ERROR RC=__ FB=__
File Task
An I/O error occurred during log processing. The return code (RC) and feedback code (FB) are given in the message.
Contact your Object Service Broker System Administrator about a possible media or space problem.
S6BDB027A
'_______' SUSPENDED DUE TO PHYSICAL ERRORS
File Task
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.
S6BDB028E
DBDLIB OPEN ERROR
File Task
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.
Verify that the Object Service Broker startup procedure or utility program correctly identifies a valid DBDLIB.
S6BDB029E
DBDLIB READ ERROR
File Task
Object Service Broker startup processing was unable to read the DBDLIB. Object Service Broker terminates abnormally.
Ensure that an Object Service Broker DBGEN has been successfully run to build a valid DBDLIB. Accompanying VSAM error messages indicate the nature of the problem.
S6BDB030E
DBDLIB DEFINITION ERROR
File Task
During initialization, the DBDLIB was found to be logically incorrect.
Contact the Object Service Broker System Administrator. Ensure that a valid DBDLIB was allocated to the Object Service Broker startup procedure or batch utility JCL.
S6BDB031E
DATABASE OPEN ERROR X'__'
File Task
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.
Standard IBM messages of the form IECxxxI accompany such failures. Contact your Object Service Broker system administrator to review the probable causes.
S6BDB032E
PAGESTORE INITIALIZATION FAILED
File Task
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.
Review the associated error messages to determine recovery action. Contact your System Programmer to correct the configuration or environmental problems.
S6BDB033E
REDOLOG INITIALIZATION FAILED
File Task
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.
Review the associated error messages to determine recovery action. Contact your System Programmer to correct the configuration or environmental problems.
S6BDB034E
GETMAIN FAILED FOR DB INITIALIZATION
File Task
Object Service Broker startup processing cannot obtain sufficient storage to complete Object Service Broker initialization.
Contact the Object Service Broker System Administrator to increase the region size.
S6BDB035I
REDOLOG CI SIZE = ' _____'
File Task
Object Service Broker startup processing displays the control interval size as currently defined in the redolog.
No action required.
S6BDB036E
REDOLOG.PENDING IS NOT CATALOGUED
File Task
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.
Define and format the Redolog.Pending data set.
S6BDB037E
REQUIRED SEGMENT FAILED TO INITIALIZE
File Task
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.
Contact TIBCO Support.
S6BDB043E
REDOLOG NOT PREFORMATTED
File Task
The redolog is normally formatted at installation time. If it is not formatted, Object Service Broker does not start up.
Contact TIBCO Support.
S6BDB044E
GETMAIN FOR SMF SUBTYPE 13 RECORD BUFFER FAILED
File Task
During Data Object Broker initialization, Object Service Broker was not able to obtain the virtual storage needed for the SMF subtype 13 record.
Modify the REGION parameter in the Data Object Broker's JCL to provide more virtual storage. Restart the Data Object Broker.
S6BDB045E
SEGMENT ID DOES NOT MATCH DBDGEN
File Task
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.
Contact your Object Service Broker System Administrator. Invalid data may have been inadvertently loaded into the wrong segment by offline utilities.
S6BDB046E
PAGESTORE HAS NOT BEEN PREFORMATTED
File Task
The segment and data set as previously displayed (S6BDB092I, S6bDB090I) have not been properly configured for Object Service Broker use.
Review the Installation and Operations manual for Pagestore setup requirements.
S6BDB047E
EXCP ERROR X'__' ON CONTINGENCY LOG (REDOLOG.PENDING)
File Task
An I/O recovery error occurred while the Data Object Broker was writing recovery information to the contingency log.
Investigate the reason for the I/O error and, if necessary, move the REDOLOG.PENDING data set.
S6BDB048E
PAGE ID DOES NOT MATCH DBGEN
File Task
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.
Contact your Object Service Broker system administrator. Invalid data may have been inadvertently loaded into the wrong page by offline utilities.
S6BDB050A
RESTORE OF PAGE SEGMENT= ___ NAME= ________ DID NOT COMPLETE
File Task
During segment initialization, indicators were found within the Pagestore data set that indicate that a restore was started but failed to complete successfully.
The segment will not be brought online. Try the segment restore again and then bring the segment online.
S6BDB051A
FORMAT OF PAGE SEGMENT= ___ NAME= ________ DID NOT COMPLETE
File Task
The initialization of the segment indicated in the name segment data sets show the formatting of the data set started but never completes.
Reformat the Pagestore data set and retry.
S6BDB052W
ERROR IN ABORT CLEANUP FREEING PAGE
File Task
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.
Contact TIBCO Support.
S6BDB053W
VALIDATION ERROR FREEING LOCK
File Task
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.
Contact TIBCO Support.
S6BDB058I
SEGMENT ________ SET TO ________ MODE
File Task
The segment identified in the message has been set to the mode shown in response to a request by the operator.
No action is required.
S6BDB063W
SEGMENT ___:________ BUSY - SHUTDOWN DEFERRED (PENDING CHECKPOINT ___)
File Task
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.
No action is required.
S6BDB064W
VSAM CLOSE ERROR ___ DSN='________.________._______'
File Task
A VSAM error was encountered while closing the data set indicated in the message.
Look for additional messages that provide information identifying the specific cause of the error, and take the appropriate corrective action.
S6BDB065E
STORAGE NOT AVAILABLE FOR RESIDENT PAGE POOL
File Task
During Data Object Broker Initialization, there was not enough storage available to construct the Resident Page Pool.
Increase the amount of Virtual Storage available to the Data Object Broker.
S6BDB066W
INSUFFICIENT STORAGE AVAILABLE FOR RESIDENT PAGES
File Task
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.
S6BDB067I
RESIDENT PAGES REQUESTED = _____, AVAILABLE = _____
File Task
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.
No action required.
S6BDB090I
OPEN '________.________.________.________.________'
File Task
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.
No action is required. This message may be followed by IEC161I 056-084 and IEC161I 062-086 if the files were not closed normally when the previous Object Service Broker execution terminated.
S6BDB092I
ACTIVATING SEGMENT=___ NAME=' ________'
File Task
The indicated segment is being activated.
No action required.
S6BDB093I
SHUT DOWN SEGMENT=___ NAME=' ________'
File Task
The indicated segment is being shut down.
No action required.
S6BDB095A
FREE SPACE SHORTAGE DETECTED FOR SEGMENT=________ - ___% FULL
File Task
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.
It is recommended that you increase the number of free pages available either by clearing up or moving existing tables, or by increasing the size of the data sets within the segment.
S6BDB096I
FREE SPACE SHORTAGE FOR SEGMENT=________ RELIEVED
File Task
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.
No action required.

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