A VSAM error occurred during checkpoint processing. Standard z/OS system messages of the form IECxxx accompany the Object Service Broker message.
Object Service Broker internal logic error. The number of pages written to the Journal do not match the number of pages written to the Pagestore. The message will be followed by a user 105 abend.
The system is preparing to spin the journal and no alternate journal is available because the alternate journal was taken off-line. The Data Object Broker does not accept any more commits until such time as a journal becomes available.
Check for a Journal offload (spin) job awaiting execution, requiring a tape mount, or failed, and resolve the situation immediately. As soon as the spin job completes successfully, QUIESCE status is automatically removed.
cancels the QUIESCE state, but leaves your continuous backups in an indeterminate state.
The currently active Journal is nearing the end of its extent, and the alternate Journal is still offline. When this Journal reaches 100% capacity, message S6BKX006A will be issued and the Data Object Broker will stop accepting COMMIT requests.
Check for a Journal offload (spin) job awaiting execution, requiring a tape mount, or failed, and resolve the situation immediately. As soon as the spin job completes successfully, this condition will be relieved.
A Journal backup is being taken. The Journal is now offline to Object Service Broker. A system task or job is submitted automatically to offload this filled Journal. When the offload is complete the S6BSPJEX utility will notify the Data Object Broker to bring the Journal back online.
A Journal backup is signalled finished. The Journal is ready for Object Service Broker use. It becomes active when it is the next available journal after a spin is initiated.
The currently active Journal has exhausted its available space and needs to be spun; however, the operator has requested (via the SPINENABLE command) that Journal spins are to be delayed until a more appropriate time. The filled journal is taken offline.
When this command is issued, the spin job for the offline Journal will be submitted or started as appropriate.
No page updates were found for the current checkpoint. This may occur during Object Service Broker shutdown if no activity occurred since the previous checkpoint.
Either no Journals are available, or the Journal size is less than 10 cylinders. A Journal size of at least 50 cylinders is recommended. A Journal size of less than 10 cylinders is not permitted. Object Service Broker does not startup.
During initialization, the Data Object Broker was not able to load the SPIN job JCL due to the value specified for the SPINMEMBER initialization parameter. This value cannot exceed (8 - the number of digits in the highest numbered journal data set ID) characters in length. Data Object Broker initialization is terminated.
During Object Service Broker initialization, SPIN JCL is loaded for later submission. A dynamic allocation error occurred for the indicated SPINDSNAME member. The first code is the error code, and the second code is the information code. Object Service Broker initialization continues. Unless the problem is resolved and Object Service Broker is shut down and restarted, automatic Journal spin job submission does not function. An explanation of the codes is in the IBM Application Development Guide for z/OS system programming.
During Object Service Broker initialization, SPIN JCL is loaded for later submission. The OPEN for the indicated spin data set member has failed. Object Service Broker initialization continues. Unless the problem is resolved and Object Service Broker is shut down and restarted, automatic Journal spin job submission does not function.
Investigate possible SPINDSNAME specification error or deleted data set. When the situation is resolved, do one of the following: shut down and restart Object Service Broker to restore automatic Journal spin job submission, or be prepared to manually submit spin jobs.
During Object Service Broker initialization, SPIN JCL is loaded for later submission. The request for storage in which to load the SPIN JCL has failed. The required amount of virtual storage may not be available. Object Service Broker initialization continues. Unless the problem is resolved and Object Service Broker is shut down and restarted, automatic Journal spin job submission does not function. It is unlikely that an Object Service Broker system that cannot obtain enough virtual storage to load its SPIN JCL can function successfully.
Increase the Object Service Broker Data Object Broker memory specification (REGION=). Shut down and restart Object Service Broker to restore automatic Journal spin job submission, or be prepared to submit spin jobs manually.
During Object Service Broker initialization, SPIN JCL is loaded for later submission. Sufficient storage for 300+ JCL cards per spin job is obtained, not including comment cards which are discarded to conserve space. The number of cards supplied for the indicated member exceeds this capacity. Object Service Broker initialization continues. Unless the problem is resolved and Object Service Broker is shut down and restarted, a partial JCL deck is submitted whenever the Journal fills.
300 cards are sufficient for any normal spin process. It is recommended that the JCL loaded consist of job cards and EXEC procedure cards only, with the necessary procedure stored in a PROCLIB. This greatly reduces the card count, and if JCL errors occur, most can be corrected without reloading the SPIN JCL decks.
During Object Service Broker initialization, SPIN JCL is loaded for later submission. The indicated member is empty, invalid, or missing. Object Service Broker initialization continues. Unless the problem is resolved and Object Service Broker is shut down and restarted, automatic Journal spin job submission does not function.
Provide suitable JCL. When the situation is resolved, do one of the following: shut down and restart Object Service Broker to restore automatic Journal spin job submission, or be prepared to submit spin jobs manually.
A dynamic allocation error occurred while attempting to allocate an internal reader during automatic spin job submission. The first code is the error 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.
A Journal data set exceeded its primary extent and is now using secondary extents. An attempt was made to automatically submit a Journal spin job to offload the filled Journal. Presumably due to an error at initialization time, no suitable SPIN JCL was found to submit.
The ACTIVE Journal data set failed initialization during system startup. Accompanying messages will indicate the failing Journal data set, and the reason for the failure.
This message indicates that the spin process has completed its processing of the offline journal, and that the Journal data set has been successfully brought online to the Data Object Broker. The Data Object Broker is now able to process journal SPIN requests.
The Data Object Broker was unable to bring the indicated Journal data set on line. Refer to the accompanying messages to determine the cause of the initialization failure.
A checkpoint started. The checkpoint number, the timestamp stored in the Pagestore records and journals, and whether the timestamp is Local or UTC is included in the message.
The checkpoint was successful. The checkpoint number, the timestamp stored in the Pagestore records and journals, and whether the timestamp is Local or UTC is included in the message. Count is the number of pages written by this checkpoint.
During Object Service Broker initialization, it was discovered that the indicated Journal was also being processed by a Journal spin job when the system terminated, and no notification was given to Object Service Broker that the spin had completed. Object Service Broker initialization continues, and the Journal is taken offline.
Determine the status of the last spin job for the indicated Journal and take the appropriate action. If the spin job completed successfully, you can use the SPINENABLE operator command to make the Journal available to Object Service Broker.
From the accompanying messages, determine the cause of the failure and take the appropriate action for the error. Once the cause of the failure has been corrected, the Journal can be brought online with the SPINENABLE operator command.
The value specified for the CHPAGELIMIT initialization parameter must not exceed 15% of the Resident Page Directory as defined by the RESIDENTPAGES initialization parameter. The value of CHPAGELIMIT has been automatically reduced so as to conform to this requirement.
Adjust the indicated initialization parameter to relieve this condition, or increase the amount of space available to the indicated data set. Consult the Installation and Operations manual for further information.
If the data set is a cache, it must be big enough to hold at least a full checkpoint's worth of data pages.
If the data set is a journal, it must be big enough to hold at least 3 full checkpoints' worth of data pages.
During Data Object Broker initialization, it was determined that the active journal was full and needed to be spun. The Data Object Broker cannot switch to the alternate journal because this journal is offline.
Determine why the alternate journal is offline. Correct the situation and restart the Data Object Broker. Alternatively, the full active journal could be spun manually while the Data Object Broker is down.
During Data Object Broker initialization, an incomplete spin was detected for the indicated journal data set. The data set remains offline to the Data Object Broker until the spin is completed.