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


Using Messages With Identifiers : KX: DOB Checkpoint Tasks

KX: DOB Checkpoint Tasks
S6BKX001E
VSAM HEX REQ=__ RC=__ FB=__ R15=________
DOB Checkpoint Tasks
A VSAM error occurred during checkpoint processing. Standard z/OS system messages of the form IECxxx accompany the Object Service Broker message.
Contact the Object Service Broker System Administrator. VSAM return codes are documented in the IBM z/OS DFP VSAM Macro Instructions.
S6BKX002I
DSN=' ________.________.________.______...'
DOB Checkpoint Tasks
This message is issued to indicate the name of a data set on which an action is being performed, or for which an error has occurred.
Refer to the associated messages to determine whether further action should be taken.
S6BKX004A
JOURNAL PROPAGATION ERROR
DOB Checkpoint Tasks
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.
Contact TIBCO Support with the following information:
A printout of the Data Object Broker initialization parameters
A list of any maintenance (including field modifications) made to the Data Object Broker beyond that included in PUT07
The output from S6BTLDBR run immediately after the Data Object Broker fails
The output from S6BTLPCA run immediately after the Data Object Broker fails
Restart the Data Object Broker; restart recovery will correct the problem.
S6BKX005A
NO ALTERNATE JOURNAL AVAILABLE - SYSTEM QUIESCED FOR COMMITS
DOB Checkpoint Tasks
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.
Determine why the alternate journal was taken offline and make one available. Note: As soon as the current spin completes, the quiesce will be reset.
S6BKX006A
ALL JOURNALS FULL - SYSTEM QUIESCED FOR COMMITS
DOB Checkpoint Tasks
All Journal space has been used and COMMIT processing is suspended - Object Service Broker is quiesced.
Display the current situation with the command:
Example MODIFY jobname,JOURNALSTATUS
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.
Manual intervention by using the command:
Example MODIFY jobname,RESUME
cancels the QUIESCE state, but leaves your continuous backups in an indeterminate state.
S6BKX007A
ACTIVE JOURNAL __% FULL - SPIN REQUIRED FOR JOURNAL _
DOB Checkpoint Tasks
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.
Display the current situation with the command:
Example MODIFY jobname,JOURNALSTATUS
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.
S6BKX008A
JOURNAL ___ SPIN IN PROCESS
DOB Checkpoint Tasks
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.
No action is usually required, unless other messages indicate a problem.
S6BKX009A
JRNL ___ SPIN:JOB=________ PG=__________ STATUS=__-__ DUR=__:__ CHT= _______-________
DOB Checkpoint Tasks
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.
No action is required.
S6BKX010E
UNDEFINED EVENT CODE X'____'
DOB Checkpoint Tasks
The Checkpoint task detected the completion of an unknown event.
Contact TIBCO Support.
S6BKX011A
JOURNAL SPINS DEFERRED - SPIN REQUIRED FOR JOURNAL _
DOB Checkpoint Tasks
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 spins are to once again be processed, the SPINENABLE command must be issued to inform the Data Object Broker of the change in status:
Example MODIFY jobname,SPINENABLE=Y
When this command is issued, the spin job for the offline Journal will be submitted or started as appropriate.
S6BKX012I
NO PAGE UPDATES FOUND
DOB Checkpoint Tasks
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.
No action required.
S6BKX013I
RPE CHAIN IN ERROR
DOB Checkpoint Tasks
Object Service Broker internal logic error. The resident page entry chain is incorrect. The system shuts down.
Contact TIBCO Support.
S6BKX014I
UNABLE TO SCHEDULE LAST CHPT
DOB Checkpoint Tasks
Object Service Broker cannot issue a final checkpoint because a checkpoint is still in progress. No action is taken.
Retry the shutdown command.
S6BKX015W
SHUTDOWN INITIATED
DOB Checkpoint Tasks
Object Service Broker is shutting down as requested.
No action required.
S6BKX016W
EXCP FAILURE X'__'
DOB Checkpoint Tasks
An I/O error occurred during the writing of a checkpoint.
Do the following:
1.
Contact the Object Service Broker System Administrator in case there is a hardware problem.
2.
S6BKX017E
INVALID DEVICE CLASS FOR CACHE
DOB Checkpoint Tasks
This message occurs during initialization if the cache is not cataloged on an appropriate device.
Change the device for the cache to a direct access device.
S6BKX018E
JOURNAL NOT PREFORMATTED
DOB Checkpoint Tasks
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.
Do the following:
1.
Check if an associated message S6BDA013E was issued. If it was, take appropriate action to make Journals available.
2.
If S6BDA013E was not issued, increase the Journal size. A Journal offload (spin) may be required.
S6BKX019E
INSUFFICIENT STORAGE FOR CACHE BUFFER
DOB Checkpoint Tasks
The system failed to get storage for a cache buffer. The system shuts down.
Contact the Object Service Broker system administrator to increase the region size through the Object Service Broker JCL.
S6BKX020E
CACHE DATASET NOT FOUND
DOB Checkpoint Tasks
The cache data set identified to Object Service Broker is not found.
Contact the Object Service Broker system administrator.
S6BKX021E
CACHE READ ERROR
DOB Checkpoint Tasks
The system tried to read the cache and failed. This is probably an I/O error.
Contact the Object Service Broker system administrator about a possibly bad device.
S6BKX022E
CHPT RECOVERY ERROR
DOB Checkpoint Tasks
During initialization or recovery, the system tried to recover a page that is not logically within the defined extents of Pagestores.
Contact the Object Service Broker system administrator to check the DBGEN. Also, verify that the page should be recovered.
S6BKX023I
CHPT RECOVERY IN PROGRESS
DOB Checkpoint Tasks
The Checkpoint task is recovering a checkpoint.
No action required.
S6BKX024I
VSAM I/O ERROR ON CHPT RECOVERY
DOB Checkpoint Tasks
During recovery, a VSAM I/O error occurred.
Contact the Object Service Broker System Administrator to investigate a possible hardware error.
S6BKX025I
_____ PAGES RECOVERED
DOB Checkpoint Tasks
The message indicates the number of pages that are recovered.
No action required.
S6BKX026E
UNABLE TO OPEN SPIN JCL MEMBERS - MEMBER NAME PREFIX TOO LONG
DOB Checkpoint Tasks
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.
Correct the value specified for the SPINMEMBER initialization parameter and restart the Data Object Broker.
S6BKX027E
SPIN JCL DAIR ERROR ____/____ MEMBER='________'
DOB Checkpoint Tasks
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.
Do the following:
1.
2.
Refer to the appropriate z/OS manual for an explanation of the error and information codes.
3.
4.
When the situation is resolved, do one of the following: shut down and restart Object Service Broker to restore automatic spin job submission, or be prepared to submit spin jobs manually.
S6BKX028E
SPIN JCL ________ DCB FAILED TO OPEN
DOB Checkpoint Tasks
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.
S6BKX029E
SPIN JCL ________ STORAGE BUFFER GETMAIN FAILED
DOB Checkpoint Tasks
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.
S6BKX030E
SPIN JCL ________ LINECOUNT EXCEEDS STORAGE CAPACITY
DOB Checkpoint Tasks
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.
S6BKX031E
SPIN JCL ________ IS EMPTY, INVALID, OR MISSING
DOB Checkpoint Tasks
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.
S6BKX032A
SPIN ___ DAIR ERROR ____/____ INTERNAL READER
DOB Checkpoint Tasks
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.
Manually submit the required Journal spin job. Contact the System Programmer.
S6BKX033A
SPIN ___ INTERNAL READER DCB OPEN FAILED
DOB Checkpoint Tasks
The system tried to open the reader and failed. This is probably a JES problem.
Manually submit the required Journal spin job. Contact the System Programmer.
S6BKX034A
SPIN ___ JCL NOT AVAILABLE TO SUBMIT
DOB Checkpoint Tasks
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.
Do the following:
1.
2.
3.
Manually shut down and restart Object Service Broker to restore automatic Journal spin job submission
If there were no initialization errors, contact TIBCO Support.
S6BKX040E
REQUIRED JOURNAL DATASET FAILED TO OPEN
DOB Checkpoint Tasks
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.
Take corrective action as indicated by the accompanying messages.
S6BKX042E
INSUFFICIENT SPACE AVAILABLE IN JOURNAL DATASET
DOB Checkpoint Tasks
There is not sufficient space defined in the Journal data set being brought online to support checkpoint activities.
Consult the Installation and Operations manual for information on defining the Journal data sets.
S6BKX043I
JOURNAL SPINS ENABLED
DOB Checkpoint Tasks
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.
No action required.
S6BKX044E
INITIALIZATION OF JOURNAL ___ FAILED
DOB Checkpoint Tasks
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.
Correct the problem indicated by the associated messages, and then use the JOURNALONLINE operator command to make the Journal data set available to the Data Object Broker.
S6BKX045A
SPIN JCL FOR JOURNAL ________ RELOADED
DOB Checkpoint Tasks
This message is issued to confirm that the SPIN JCL for the indicated journal data set has been successfully reloaded as requested by the operator.
No action required.
S6BKX046E
SPIN JCL RELOAD FOR JOURNAL ___ FAILED
DOB Checkpoint Tasks
The reloading of the SPIN JCL for the indicated journal has failed. Scan the Data Object Broker's job log for indications as to why the process terminated.
If possible correct the source of the failure and retry the command.
S6BKX051L
START CHECKPOINT - '________'
DOB Checkpoint Tasks
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.
No action is required.
S6BKX052L
END CHECKPOINT - '________' COUNT= '________'
DOB Checkpoint Tasks
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.
No action is required.
S6BKX053E
CHECKPOINT USER EXIT FAILURE DETECTED, DOB ABNORMALLY TERMINATED
DOB Checkpoint Tasks
The Checkpoint Start user exit returned a nonzero return code in GPR 15. The Data Object Broker is terminated with a U107 abend.
Contact the Object Service Broker system administrator.
S6BKX054W
SPIN REQUIRED FOR JOURNAL_
DOB Checkpoint Tasks
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.
S6BKX055E
JOURNAL NOT ENABLED
DOB Checkpoint Tasks
While trying to enable an offline Journal, Object Service Broker encountered a condition that made it impossible to bring the Journal online.
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.
S6BKX056E
CHECKPOINT CACHE USER EXIT FAILURE DETECTED, DOB ABNORMALLY TERMINATED
DOB Checkpoint Tasks
The Cache Complete user exit returned a nonzero return code in GPR 15. The Data Object Broker is terminated with a U107 abend.
Contact the Object Service Broker system administrator.
S6BKX057W
PAGE LIMIT REDUCED - EXCEEDS 15% OF RESIDENT PAGES
DOB Checkpoint Tasks
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 CHPAGELIMIT parameter or the RESIDENTPAGES parameter or both so that this condition is addressed.
S6BKX059W
_________ REDUCED - INSUFFICIENT SPACE IN _______ DATA SET
DOB Checkpoint Tasks
The value specified for the initialization parameter indicated by this message is too large to be supported by the indicated data set.
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.
S6BKX060I
CHECKPOINT MAXIMUM PAGES = ____, TRANSACTIONS = ____
DOB Checkpoint Tasks
This message is provided for informational purposes only and is issued to confirm the thresholds set for the maximum size of a Checkpoint.
No action is required.
S6BKX061I
GETMAIN FOR JOURNAL I/O BUFFER FAILED
DOB Checkpoint Tasks
Data Object Broker initialization was unable to obtain the Virtual Storage needed for the Journal I/O buffer.
Provide more Virtual Storage to the Data Object Broker. Consult the Installation and Operations manual for further information.
S6BKX062E
CANNOT SPIN JOURNAL ___ - NO ALTERNATE JOURNAL AVAILABLE
DOB Checkpoint Tasks
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.
S6BKX063W
JOURNAL ___ WAITING FOR SPIN
DOB Checkpoint Tasks
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.
Determine why the spin has not completed. If the SPIN had failed, submit the spin job manually to clear the data set.
S6BKX064I
JOURNAL ___ NOW
DOB Checkpoint Tasks
This message is issued to confirm the completion of a journal vary command. The journal and its new status are displayed in the message text.
No action required.
S6BKX066A
CACHE DATASET OPEN FAILURE DETECTED
DOB Checkpoint Tasks
When attempting to open the cache data set to identify the previous checkpoint a failure was detected.
Review the joblog for information and correct the problem.
S6BKX067I
SEGMENT % PAGE %
DOB Checkpoint Tasks
This message indicates which page number and segment number is causing the subsequent S6BKX022 message.
If this message appears while you are recovering after a restart with no redolog, modify the DBDGEN to include the segment as online at initialization.
S6BKX068W
parameter SET BASED ON SPACE AVAILABLE IN THE dataset DATASET
DOB Checkpoint Tasks
The value of the specified parameter is set automatically based on the calculated maximum capacity of the specified data set.
No action is required.
S6BKX069I
SYSTEM IS FROZEN: %
DOB Checkpoint Tasks
As a result of a Freeze command, the system has entered the frozen state.
No action is required.
S6BKX070I
SYSTEM IS UNFROZEN: %
DOB Checkpoint Tasks
As a result of an UNFREEZE command, the system has resumed processing.
No action is required.
S6BKX071E
SPIN NOTIFICATION REPORTED ERROR rc-re JOB jobid
DOB Checkpoint Tasks
The Data Object Broker received notification that a spin job had completed with a fatal error (return code 16 or higher). In the message:
jobid=the identification number of the spin job that reported the fatal error
Review the message in the spin job and take the appropriate action.

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