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


Using Messages With Identifiers : TL: DOB Support Offline Utils

TL: DOB Support Offline Utils
S6BTL001I
RESTORE IN PROGRESS FOR SEGMENT=___
DOB Support Offline Utils
The Pagestore restore utility (S6BTLRPS) was invoked to restore the segment number indicated by this message.
No action is required.
S6BTL002E
VSAM ERROR READING DBDLIB
DOB Support Offline Utils
An error was detected reading the DBDLIB defined by the DBDLIB DD card. The utility terminates with a return code of 12.
Ensure that the data set specified on the DBDLIB DD statement points to a valid DBDLIB.
S6BTL003W
WARNING - PAGESTORE SMALLER THAN BACKUP
DOB Support Offline Utils
The Pagestore restore utility (S6BTLRPS) determined that the receiving Pagestore data set currently being processed is smaller than the original, but should be large enough to hold the data. The restore continues, and a return code of 4 is issued upon its completion.
If a reduction of the total space for the Pagestore data set was intended, then no further action is required. Otherwise, reallocate the Pagestore data set to a larger size and rerun the restore utility.
S6BTL004E
VSAM WRITE ERROR RC=__ FB=__
DOB Support Offline Utils
An I/O error was detected while writing to the Pagestore data set currently being processed. The utility terminates with a return code of 12.
Verify that the Pagestore data set indicated is properly defined and rerun the job.
S6BTL005E
PAGE SPACE ALLOCATION TOO SMALL
DOB Support Offline Utils
This message is issued when the minimum space requirement, as determined by the executing utility, is not satisfied. Utilities which issue this message are S6BTLFPS and S6BTLRPS. In the case of the Pagestore formatting utility (S6BTLFPS) the space allocated for the failing segment data set does not meet or exceed the minimum space allocation allowed for this data set. Failures encountered by the restore utility (S6BTLRPS) are issued when the segment which is the target of the restore function does not have enough space to contain all of the pages in the backup set.
Reallocate the failing segment data sets so that they are large enough to satisfy the requirements of the executing utility. Rerun the failed job.
S6BTL006E
SYNTAX ERROR IN PARAMETER
DOB Support Offline Utils
A syntax error was detected, an invalid parameter was passed, or a required parameter was omitted in the PARMS specified on the EXEC card for this utility. The utility terminates with a return code of 12.
Correct the parameters specified and rerun the utility.
S6BTL007W
BAD PAGE NUMBER DETECTED
DOB Support Offline Utils
An invalid page number was detected in the input file to the Pagestore restore utility (S6BTLRPS). This may indicate a problem with the backup file being processed. Message S6BTL008I is also issued to indicate which record was found to be in error. The restore utility continues processing, but issues a return code of 8 upon completion.
The database may be corrupted. Contact the Object Service Broker System Administrator for further assistance.
S6BTL008I
RELATIVE RECORD NUMBER ____
DOB Support Offline Utils
The indicated record is associated with a previous error.
Refer to the accompanying message to determine the cause of the problem and the appropriate action.
S6BTL009E
DYNAMIC ALLOCATION FAILED
DOB Support Offline Utils
A dynamic allocation error was been detected. The utility is terminated with a return code of 12.
Refer to the accompanying messages to determine the failing data set and the cause of the failure.
S6BTL010E
OPEN FAILED FOR _______ DATASET RC=__
DOB Support Offline Utils
The opening of a Journal or a Pagestore data set failed with the indicated VSAM return code. The utility terminates with a return code of 8 or 12.
Return codes appearing in the message are for OPEN failures documented in the IBM "DFSMS Macro Instructions for Data Sets" manual. The RC= value is actually returned in the VSAM ACB field ACBERFLG and is expressed as a decimal number.
Refer to the accompanying system messages to determine the cause of the failure.
RC=168 is most commonly caused by another z/OS job or started task using the data set and preventing the current job from successfully opening the data set. Retry the failing job later or, if the Data Object Broker is the user, vary the associated segment offline to the Data Object Broker and then retry the failing job.
S6BTL011E
JOURNAL DD NOT FOUND
DOB Support Offline Utils
The required DD card for the Journal data set was not found in the JCL stream. The utility terminates with a return code of 12.
Include a Journal DD card in the JCL stream that points to a valid Object Service Broker Journal data set.
S6BTL012I
_______ PAGES RESTORED FROM JOURNAL
DOB Support Offline Utils
This message indicates the total number of pages restored by the Pagestore utility (S6BTLRPS).
No action required.
S6BTL013E
INVALID SEGMENT SPECIFIED
DOB Support Offline Utils
The segment number specified was not located in the DBDLIB. The utility terminates with a return code of 12.
Verify that the correct segment number was requested.
S6BTL015E
BITMAP MISSING FROM BACKUP, RESTORE TERMINATED
DOB Support Offline Utils
The first record in the journal (backup) used to restore the PageStore data set was not a bitmap page as expected. If you are attempting to apply a spinout journal onto a PageStore data set, the positional parameter APPLY must be specified before the "SEG=" or "DUP=" keyword parameter.
If applying a spinout journal, specify APPLY. If attempting to restore a backup, verify the backup using the S6BBRPTR (Batch Pointer Check) utility before rerunning the restore.
S6BTL016E
ERROR DETECTED EXTRACTING ARCHLOG DEFINITION FROM DBDLIB
DOB Support Offline Utils
The utility requires access to the ARCHLOG but was unable to access the DBDLIB definition for it. Possible causes are:
Correct the specification of the DBDLIB.
S6BTL017E
ORIGINAL DATA FOR ARCHLOG UPDATE COULD NOT BE LOCATED
DOB Support Offline Utils
When an Object Service Broker S6BTL*** utility was attempting to update an entry in the ARCHLOG, the entry to be modified could not be located. The log update process terminates with a nonzero return code.
Contact TIBCO Support.
S6BTL018E
ERROR DETECTED WHEN UNALLOCATING ARCHLOG DATASET
DOB Support Offline Utils
An error was detected when attempting to release the ARCHLOG after it had been updated.
No action is required.
S6BTL019E
OPEN ERROR FOR REPORT LISTING
DOB Support Offline Utils
The utility being executed was not able to open the DD for the output listing (DDNAME=REPORT). The utility stopped executing.
Accompanying messages indicate the reason that the open failed. Correct the situation and rerun the job.
S6BTL020E
I/O ERROR ON JOURNAL
DOB Support Offline Utils
An I/O error was encountered while processing the Object Service Broker Journal data set. The utility terminates with a return code of 12.
Contact the Object Service Broker System Administrator for further assistance.
S6BTL021E
JOURNAL RECORDS OUT OF SEQUENCE
DOB Support Offline Utils
Input journal records are not in the expected sort sequence.
Sort the input journal data set in the expected sequence and rerun.
S6BTL022I
_________ PAGES ARCHIVED TO JOURNAL
DOB Support Offline Utils
This message indicates the number of pages that are archived to the Object Service Broker Journal data set.
No action required.
S6BTL023E
VSAM ERROR RC=__ FB=__ RBA=________
DOB Support Offline Utils
A VSAM error was encountered on the data set currently being processed, as indicated by the accompanying messages. The VSAM Return Code (RC), Feedback Code (FB), and the RBA of the failing record are provided in the message text. The utility terminates with a return code of 8.
Contact the Object Service Broker system administrator. Reason codes are documented in the z/OS DFP VSAM Macro Instruction Reference. z/OS messages are documented in the z/OS System Messages Manual.
S6BTL024E
DATA CONTROL ERROR
DOB Support Offline Utils
A page was found in an Object Service Broker Pagestore that contains invalid control data. The utility terminates with a return code of 12.
Contact your Object Service Broker system administrator for assistance.
S6BTL025E
READ ERROR RBA=0
DOB Support Offline Utils
The record located at RBA=0 did not contain the expected Object Service Broker control data. The utility terminates with a return code of 12.
Contact your Object Service Broker System Administrator for assistance.
S6BTL026E
ARCHLOG OPEN ERROR FOR (READ|WRITE)
DOB Support Offline Utils
An error was detected by the system when the ARCHLOG processor was attempting to open the ARCHLOG for either a read or a write operation.
Review the joblog to identify the cause of the problem.
S6BTL027E
DOB NOTIFICATION FAILED FOR SPIN PROCESSING
DOB Support Offline Utils
After the completion of the data offload from the Data Object Broker Journal data set, the owning Data Object Broker could not be contacted to reactivate the journal. The journal is not available for reuse until the Data Object Broker is manually notified or recycled.
If the Data Object Broker is currently active, try rerunning the spin job to re-send the spin complete notification to the Data Object Broker.
S6BTL028E
ERROR DETECTED IN SEND WHEN ATTEMPTING TO NOTIFY DOB
DOB Support Offline Utils
After the completion of the data offload from the Data Object Broker journal data set, the notification of the completion could not be sent to the owning Data Object Broker. The journal is not available for reuse until the Data Object Broker is manually notified or recycled.
If the Data Object Broker is still active, rerun the SPIN process to attempt to re-send the notification.
S6BTL029E
ERROR DETECTED WHEN RELEASING ACQUIRED STORAGE
DOB Support Offline Utils
When attempting to release storage obtained by a utility, the system found the release to be in error. The process terminates with a nonzero return code.
Contact TIBCO Support.
S6BTL030W
ARCHLOG RECORD FAILURE DETECTED, PROCESSING CONTINUED
DOB Support Offline Utils
The ARCHLOG update processing routine returned a nonzero return code.
Processing continues. No action is required.
S6BTL031E
S6BBKCXO ERROR R15=X'XXXXXXXX'
DOB Support Offline Utils
An error was detected in the data compression subroutine. Processing terminated.
Review the user-supplied compression exit to determine the cause of the error.
S6BTL032E
ARCHLOG PROCESSING ROUTINE LOAD REQUEST FAILED
DOB Support Offline Utils
The common subroutine that manipulates the ARCHLOG is dynamically loaded by various S6BTL*** utilities. The load failed.
Review the joblog to determine why the ARCHLOG could not be loaded.
S6BTL033W
ARCHLOG PROCESSING IGNORED, DBDLIB NOT DEFINED IN JCL
DOB Support Offline Utils
The DBDLIB is not defined in the utility job stream, the ARCHLOG cannot be identified and therefore it cannot be processed.
Correct the job stream to include a DD statement for the DBDLIB.
S6BTL034E
S6BBKCXR ERROR R15=X'XXXXXXXX'
DOB Support Offline Utils
A failure was returned from the user-supplied data compression routine.
Determine the cause of the error as per the supplied exit.
S6BTL035W
HRNBKDXI ERROR R15=X'XXXXXXXX'
DOB Support Offline Utils
An error was detected by the user-supplied data decompression routine.
Determine the error by looking at your routine.
S6BTL036W
COMPRESSION DISABLED BY HRNBKDXI
DOB Support Offline Utils
A user-supplied compression routine elected to disable compression.
No action is required.
S6BTL037W
HRNBKDXR ERROR R15=X'XXXXXXXX'
DOB Support Offline Utils
A user-supplied decompression exit returned a nonzero return code.
Determine the error via the user exit.
S6BTL038E
ARCHLOG CLOSURE ERROR DETECTED, PROCESSING CONTINUES
DOB Support Offline Utils
After the successful completion of ARCHLOG update processing, the process detected an error when closing the ARCHLOG.
Refer to the joblog for further failure information. No action is required, processing continues.
S6BTL039W
HRNBKDXE ERROR R15=X'XXXXXXXX'
DOB Support Offline Utils
A user-supplied data decompression exit returned a nonzero return code.
Correct the error via the user exit.
S6BTL040W
DATASET JFCB EXTRACT FAILED, PROCESSING CONTINUES
DOB Support Offline Utils
During an attempt to obtain the data set name and DASD volume for the Cache data set, the read "JFCB" failed. Processing continues even though the DSN and volume are not available.
No action is required.
S6BTL041E
INVALID DEVICE CLASS FOR LOGGING
DOB Support Offline Utils
The Object Service Broker logging data set specified does not reside on a direct access device.
Change the allocation of the logging data set so that it resides on a direct access volume.
S6BTL042E
EXCP ERROR ON RELATIVE TRACK ___
DOB Support Offline Utils
An EXCP error was encountered while reading or writing to the Cache or Contingency Log data set at the indicated relative track. The utility terminates with a return code of 12.
Refer to the accompanying z/OS messages for further information regarding this error, and contact TIBCO Support for assistance.
S6BTL043I
RELATIVE TRACK ___ FORMATTED SUCCESSFULLY
DOB Support Offline Utils
The relative track indicated by the message text was successfully formatted. In cases where the cache data set is being formatted, the Cylinder and Head (CC HH) address of the track are also indicated.
No action is required.
S6BTL044E
REDO.PENDING RESTRICTED TO 255 TRACK MAXIMUM
DOB Support Offline Utils
The contingency log format routine detected the data set was defined to have more than 255 tracks.
Redefine the clog with 255 or less tracks and rerun the format utility (S6BTLFCL).
S6BTL045E
REDO.PENDING RESTRICTED MUST HAVE AT LEAST 6 TRACKS
DOB Support Offline Utils
When formatting the contingency log it was detected to have less than 6 tracks.
Redefine the CLOG with 6 to 255 tracks and rerun the format utility (S6BTLFCL).
S6BTL046W
WORKING STORAGE NOT AVAILABLE CONFIGURATION RECOVERY IGNORED
DOB Support Offline Utils
When the contingency log formatting routine was attempting to acquire storage to process the configuration initialization data set the storage was not available.
Increase the region parameter of your job control statements and rerun the format utility (S6BTLFCL).
S6BTL047E
REDOLOG RECORD SIZE MUST BE CONTROL INTERVAL SIZE - 7
DOB Support Offline Utils
In order to allow the REDOLOG to be dump using IDCAMS it is important that the maximum record length defined for the VSAM data set is adequate. To ensure the size is appropriate the S6BTLFRL (REDOLOG Format Utility) required the record length to be the VSAM maximum which is the CISIZE-7 (Control Interval Size).
Change the VSAM define parameters to correct the record length. For example (CISZ(4096) RECSZ(200,4089)).
S6BTL048E
DEVICE CHARACTERISTICS EXTRACT FAILURE DETECTED
DOB Support Offline Utils
When attempting to extract the device characteristics of the media on which the ARCHLOG is defines an error was detected.
Ensure the ARCHLOG is defined on DASD. If the problem recurs, contact TIBCO Support.
S6BTL049E
DEVICE DOES NOT SUPPORT DIRECT ACCESS
DOB Support Offline Utils
The ARCHLOG is maintained using "Update In Place" processing and must therefore reside on media that supports direct access.
Redefine the ARCHLOG data set on DASD and run the S6BTLFAL format utility again.
S6BTL050E
REDOLOG CI SIZE NOT 2K OR 4K
DOB Support Offline Utils
While processing the redolog, an unacceptable value for the CISIZE of the data set was found as displayed in the message text. The utility terminates with a return code of 12.
Redefine the Object Service Broker redolog with an acceptable CISIZE.
S6BTL051E
WRITE ERROR ON RELATIVE TRACK ___ - CC HH=____ ____
DOB Support Offline Utils
An error was encountered writing to the data set indicated by previous informational messages, at the relative track indicated in the message. The physical track address (CC HH) is also noted by this message. The utility terminates with a return code of 12.
This message has probably been issued in response to a media failure. Try redefining the affected data set on another volume, and contact your Object Service Broker System Administrator.
S6BTL052E
DATASET JFCB EXTRACT FAILED, PROCESSING TERMINATED
DOB Support Offline Utils
When attempting to extract the JFCB (data set characteristics) for the ARCHLOG and error was detected.
Ensure the ARCHLOG is defined, the JCL is correct and run the format utility again. If the problem recurs, contact TIBCO Support.
S6BTL053W
SCHEDULE CANNOT HAVE BOTH APPLICABLE DAYS AND OVERRIDE DATE, CARD REJECTED
DOB Support Offline Utils
When processing the path management cards in S6BTLFCL, it was detected that an override date was supplied on a card that also specified applicable days. The two scheduling techniques are mutually exclusive and the card is rejected.
Correct the rejected card and reformat the CLOG.
S6BTL054E
ARCHLOG MUST HAVE AT LEAST 2 BLOCKS PER TRACK
DOB Support Offline Utils
The ARCHLOG is fixed blocked (FB) with a record length of 132. In order to support processing the blocksize must be defined to be less than one half of a track.
Redefine the ARCHLOG with an appropriate blocksize, (half track blocking is recommended) and rerun the format utility.
S6BTL055I
TRACKS SUCCESSFULLY FORMATTED
DOB Support Offline Utils
During the formatting of the Data Object Broker's data sets, the specified tracks were formatted successfully. This message is generated when formatting the cache and the contingency log. The CACHE formatter suffixes the message with "CCHH=..." to indicate the track head position. The CLOG formatter indicates if the tracks are "RESERVED" or "CLOG" with a suffix to the message.
No action is required.
S6BTL056I
FORMATTING DUPLEX REDOLOG
DOB Support Offline Utils
This informational message identifies this run is formatting the duplex copy of the REDOLOG.
No action required.
S6BTL057E
ARCHLOG CONTROL ENTRY NOT FOUND
DOB Support Offline Utils
The first entry in the ARCHLOG data set is a control entry used to retain information about the ARCHLOG and the next insert point. When attempting to read this entry, it could not be found. The most probable cause is that the ARCHLOG was not formatted.
Format the ARCHLOG using the S6BTLFAL utility.
S6BTL058E
ARCHLOG BLOCK SIZE TOO SMALL
DOB Support Offline Utils
The entries on the ARCHLOG are grouped together for each Object Service Broker utility execution. The number of lines within a group depends on the configuration. In order to support processing requirements, it is required that the blocksize be such that it is large enough to retain one full group. For example, if a segment is defined with 100 ACBS the backup utility (S6BTLBPS) generates an ARCHLOG group of 103 items, therefore the minimum blocksize would be 103 * 132.
Redefine and reformat the ARCHLOG with a large blocksize (half track blocking is recommended).
S6BTL059E
ARCHLOG I/O ERROR DETECTED, PROCESSING TERMINATED
DOB Support Offline Utils
When attempting to read the ARCHLOG in order to produce the ARCHLOG report, S6BTLPAL detected an I/O error.
Rerun the S6BTLPAL. If the problem recurs, contact TIBCO Support.
S6BTL060E
NO ENTRIES FOR ARCHLOG UPDATE PROCESS
DOB Support Offline Utils
The ARCHLOG update processing routine was called to add records to the ARCHLOG. The calling program failed to provide the entries to be added.
Contact TIBCO Support.
S6BTL061E
PAGESTORE DATASET LIMITED TO 507904 PAGES, ALLOCATION EXCEEDS LIMITS
DOB Support Offline Utils
When the Pagestore data set was defined, the number of cylinders allocated provided more space than the Data Object Broker can support.
Redefine your Pagestore data set with a smaller allocation. Refer to the Installation and Configuration manual for more information. If you need to expand your segment capacity, an alternative would be to increase the ACB limit (number of Pagestore data sets).
S6BTL070E
NO ____STORES DEFINED IN DBDLIB
DOB Support Offline Utils
Processing was requested for the indicated Object Service Broker data set type. However, none was defined in the DBGEN information provided by the DBDLIB DD card. The utility terminates with a return code of 12.
Correct your DBGEN to include the required Object Service Broker data set type, and rerun the utility.
S6BTL071E
DDNAME=________ NOT A VSM DATASET
DOB Support Offline Utils
The data set pointed to by the DDNAME indicated in the message text is not a VSAM data set. The utility terminates with a return code of 12.
Correct the data set referenced by the DDNAME, and rerun the utility.
S6BTL072E
DDNAME=________ NOT A VALID PAGESTORE
DOB Support Offline Utils
The data set pointed to by the DDNAME reflected in the message text was not defined in the DBGEN as an Object Service Broker data set of the type indicated. The utility terminates with a return code of 12.
Correct the indicated DDNAME to point to a valid Object Service Broker data set, and rerun the utility.
S6BTL073I
_______ PAGES SUCCESSFULLY FORMATTED
DOB Support Offline Utils
This message confirms the number of pages formatted by one of the formatting utilities.
No action required.
S6BTL074E
NO INPUTS SPECIFIED VIA DD CARDS
DOB Support Offline Utils
The executing utility expected to find "DDn" DD cards in the JCL that indicate the data sets to be processed. However, none were found. The utility terminates with a return code of 12.
Correct the JCL stream to include DD cards for processing.
S6BTL075E
________ DATASET NOT EMPTY
DOB Support Offline Utils
The format utility has determined that the data set being processed may contain valid data. The utility terminates with a return code of 12.
Correct the JCL stream to point to an empty data set. If you are reformatting a previously used data set, delete and redefine a new cluster prior to executing this utility.
S6BTL079E
REDOLOG OPEN FAILED
DOB Support Offline Utils
HRNTLRDO was unable to open a redolog file and terminates with a return code of 12.
Correct the JCL stream to point to a valid redolog file.
S6BTL080E
TIBCO(r) Object Service Broker NOT AVAILABLE
DOB Support Offline Utils
The requested Object Service Broker system is not currently available.
Ensure that the correct Object Service Broker system was requested, and wait for it to become available. Contact your Object Service Broker System Administrator for further assistance.
S6BTL081E
TIBCO(r) Object Service Broker VERSION MISMATCH
DOB Support Offline Utils
The version of Object Service Broker under which this utility is executing does not match the version of Object Service Broker under which the requested Data Object Broker is executing. The utility terminates with a return code of 12.
Ensure that any JOBLIB/TASKLIB/STEPLIB DD cards present in either the utility program's JCL, or the Object Service Broker Data Object Broker's startup JCL are referencing the proper level of the Object Service Broker software. Contact your Object Service Broker System Administrator for further assistance.
S6BTL083E
TIBCO(r) Object Service Broker COMMUNICATION ERROR CODE
DOB Support Offline Utils
When attempting to establish a communication link from a batch utility to the Data Object Broker, the Object Service Broker communication subsystem detected an error. In the current release the only valid return codes are 0 - successful and 16 - unsuccessful.
View the SYSLOG for additional data on the error, and contact TIBCO Support if further assistance is required.
S6BTL084E
TIBCO(r) Object Service Broker CONNECT ERROR CODE
DOB Support Offline Utils
When attempting to open communications between the application and the Object Service Broker Data Object Broker, either the communications subsystem or the Data Object Broker detected an error.
View the SYSLOG for additional data on the error, and contact TIBCO Support if further assistance is required.
S6BTL085E
MDLAPPL COULD NOT BE MATCHED
DOB Support Offline Utils
When attempting to open VSAM communications to the Object Service Broker Data Object Broker, the model APPLID was found to be invalid. No such VTAM resource is defined or available in the network.
Ensure that the appropriate TDS= and/or MDL= parameters represent real resources in your environment.
S6BTL090E
'TDSAPPL,MDLAPPL' PARAMETERS OMITTED OR INVALID
DOB Support Offline Utils
Mandatory parameters to describe the target Object Service Broker connection name were not provided.
Ensure that the appropriate TDS= and MDL= parameters are provided.
S6BTL091E
'##,TDSAPPL,MDLAPPL' PARAMETERS OMITTED OR INVALID
DOB Support Offline Utils
Mandatory parameters to describe the target Object Service Broker connection name or timing delays were not provided to S6BTLCMD.
Ensure that the appropriate TDS= and MDL= parameters are provided.
S6BTL092E
UNEXPECTED KEYWORD PARAMETER, ________
DOB Support Offline Utils
A keyword parameter passed to an offline utility is not supported by that utility.
Correct the keyword specification and resubmit the job. View the SYSLOG for additional data on the error, or contact TIBCO Support if further assistance is required.
S6BTL093E
NO TEXT FOLLOWING KEYWORD PARAMETER, ________
DOB Support Offline Utils
A keyword parameter passed to an offline utility has not specified a corresponding value.
Correct the keyword specification and resubmit the job. View the SYSLOG for additional data on the error, or contact TIBCO Support if further assistance is required.
S6BTL094E
UNEXPECTED POSITIONAL PARAMETER
DOB Support Offline Utils
A startup parameter passed to an offline utility via the PARM=.... JCL directive was specified incorrectly or contains parameters not supported by this utility.
View the SYSLOG for additional data on the error, and contact TIBCO Support if further assistance is required.
S6BTL095E
,
DOB Support Offline Utils
The S6BTL095E message label provides a reference point for the display of error text returned from the Data Object Broker when a SPIN ENABLE process fails to complete properly. It is expected that the message text will be detailed enough to identify the problem so it can be corrected.
Base your action on the message text received from the Data Object Broker.
S6BTL096E
User -------- has been denied access to this service by External Secur
DOB Support Offline Utils
DOB is running with SECUREADMIN=Y and user uuuuuu does not have External Security authorization to issue DOB Commands. Rest of the input stream is flushed and the utility stops since there is no point in keep s sending the commands to the DOB.
Contact your Security Administrator and either run the DOB without SECUR EADMIN=Y or update this user's External Security profile to allow_him/he the privillege of issuing DOB Commands via S6BTLCMD
S6BTL100E
BATCH INITIALIZATION FAILED
DOB Support Offline Utils
The initialization of the batch processing environment failed. Refer to the accompanying messages to determine the cause of the failure.
Correct the problem indicated and resubmit the job.
S6BTL101I
BATCH INITIALIZATION OK
DOB Support Offline Utils
The initialization of the batch processing environment completed successfully.
No action required.
S6BTL102I
SUMMARY STATS: READS ________ WRITES ________
DOB Support Offline Utils
This message is issued to summarize the database activity generated by an offline utility.
No action required.
S6BTL103I
FREE PAGES ACQUIRED ________
DOB Support Offline Utils
This message is issued to summarize the database activity generated by an offline utility.
No action required.
S6BTL104E
TERMINATION EXIT ERROR
DOB Support Offline Utils
A nonzero return code was returned by the batch processing termination exit (BATCHTMX).
Contact your system administrator for further information.
S6BTL105I
BATCH FUNCTION COMPLETED
DOB Support Offline Utils
This message is issued to signal the end of batch processing.
No action required.
S6BTL106E
I/O ERROR WHILE WRITING THE CONTROL PAGE
DOB Support Offline Utils
An I/O error occurred while writing the Object Service Broker control page.
Read the accompanying messages to find the cause of the I/O error.
S6BTL107E
MESSAGE ERROR
DOB Support Offline Utils
An invalid Object Service Broker message unit was encountered during batch processing.
Contact your System Administrator for assistance.
S6BTL108E
NO HOST SESSION FOR BATCH SERVER
DOB Support Offline Utils
The requested host session either does not exist or is not able to service your request at this time.
Ensure that a valid host VTAM APPLID was coded. If the APPLID is valid, retry your request at a later time, or contact your Object Service Broker System Administrator.
S6BTL109E
BATCH - PUTFREE PAGE FAILED
DOB Support Offline Utils
During batch processing, a PUTFREE page request failed.
Contact your Object Service Broker System Administrator for assistance.
S6BTL110E
FREE OVERFLOW FAILED
DOB Support Offline Utils
An attempt to free an overflow area has failed.
Contact your Object Service Broker System Administrator for assistance.
S6BTL111E
FREE HASH EXTENT FAILED
DOB Support Offline Utils
An attempt to free a HASH table extent has failed.
Contact your Object Service Broker System Administrator for assistance.
S6BTL112E
PAGE NUMBER OUT-OF-RANGE FOR THIS PAGESTORE
DOB Support Offline Utils
The requested page number is not within the range of available pages for this segment.
Contact your Object Service Broker System Administrator for assistance.
S6BTL121I
PAGESTORE INPUT OPEN ERROR
DOB Support Offline Utils
An error was detected by the operating system when attempting to open the Pagestore data set. The utility terminates with a return code of 8.
View the job SYSLOG for more information about the open failure.
S6BTL122I
OUTPUT TAPE OPEN ERROR
DOB Support Offline Utils
An error was detected by the operating system when attempting to open the tape file for output. The utility terminates with a return code of 8.
View the job SYSLOG for more information about the open failure.
S6BTL123I
VSAM LOGICAL ERROR ON INPUT
DOB Support Offline Utils
An error was detected by the operating system when attempting to read the VTAM RPL for the next Pagestore record. The read attempt resulted in a return code of 4 or 8. The utility terminates with a return code of 8.
View the job SYSLOG for more information about the open failure.
S6BTL124I
VSAM PHYSICAL ERROR ON INPUT
DOB Support Offline Utils
An error was detected by the operating system when attempting to read the VTAM RPL for the next Pagestore record. The read attempt resulted in a return code of 12. The utility terminates with a return code of 8.
View the job SYSLOG for more information about the open failure.
S6BTL130I
INVALID NUMERIC FIELD SET TO ZERO
DOB Support Offline Utils
The configuration input record to S6BTLFCL contains invalid numeric data. The value of 0 is assumed.
Correct the configuration cards and rerun S6BTLFCL.
S6BTL131I
INPUT: ______ CONTROL, ______ SCHEDULES
DOB Support Offline Utils
This message is issued by the contingency log formatting utility (S6BTLFCL) to report on the number of Path Management control cards processed while formatting the log. The variable portions of the message text indicate the number of Path control cards (CONTROL) and the number of Path Management control cards (SCHEDULES) processed.
No action is required.
S6BTL132E
DBDLIB PROCESSING ERROR
DOB Support Offline Utils
ERROR READING DBDLIB
CORRECT ERROR & RESUBMIT
S6BTL133E
GETMAIN STORAGE FAILED "OR" GETMAIN FAILED
DOB Support Offline Utils
insufficient memory available
increase region size & resubmit
S6BTL134E
REPORT PROCESSING PROBLEM
DOB Support Offline Utils
ERROR ALLOCATING REPORT DD
CHECK JCL TO ENSURE ALL REQUIRED REPORT DD STATEMENTS ARE PRESENT
S6BTL135E
INVALID ADDRESS - LOGIC ERROR
DOB Support Offline Utils
There is an invalid address pointer to the next bitmap page.
This is the result of a program logic error; the program is unable to continue. Contact TIBCO Support.
S6BTL136I
DATE CONVERSION ACTIVATED
DOB Support Offline Utils
Date Conversion Parameter CONV appears in JCL.
No action required; date conversion is automatic.
S6BTL137I
#DATTIM CONVERSION ERROR
DOB Support Offline Utils
Something got triggered during execution of the date conversion routine.
Open a problem incident and retain the image of the backup for analysis.
S6BTL150E
KEYWORD PARAMETER TOO LONG
DOB Support Offline Utils
The identified keyword is too long. Possibly the "=" is missing.
Correct and retry.
S6BTL151E
PARAMETER IS TOO LONG
DOB Support Offline Utils
The parameter value supplied for the specified keyword is too long.
Correct and retry.
S6BTL152E
IS AN UNRECOGNIZED KEYWORD PARAMETER
DOB Support Offline Utils
The specified keyword parameter could not be identified.
Correct and retry.
S6BTL153E
HOST AND MODEL ARE REQUIRED PARAMETERS
DOB Support Offline Utils
The host and model parameters are required to make the connection to the Data Object Broker. One or both of these parameters is missing or not recognized.
Correct and retry.
S6BTL154E
OUTPUT FILE COULD NOT BE OPENED, SEE JOB LOG
DOB Support Offline Utils
The file onto which the Resource repository is to be backed up could not be opened. Check the job log for more information.
Correct and retry.
S6BTL155E
REQUEST COULD NOT BE SENT TO THE DOB
DOB Support Offline Utils
When attempting to send a request to the Data Object Broker the send function returned an error.
Correct and retry, review the job log for further information.
S6BTL156E
RETRIEVAL ERROR DETECTED
DOB Support Offline Utils
When attempting to retrieve resource detail information the retrieval request failed.
If the job log messages do not identify the problem, contact TIBCO Support.
S6BTL160I
REDOLOG COPY INPUT CI SIZE IS (4096|8192) BYTES
DOB Support Offline Utils
Identifies the control interval (CI) size of the input redolog on the REDOIN DD. Valid CI sizes are 4096 or 8192 - any other size causes S6BTLFRL to fail with RC=12.
None - information only.
S6BTL161I
REDOLOG COPY OUTPUT CI SIZE IS (4096|8192) BYTES
DOB Support Offline Utils
Identifies the control interval (CI) size of the output redolog on the REDOOUT DD. Valid CI sizes are 4096 or 8192 - any other size causes S6BTLFRL to fail with RC=12.
None - information only.
S6BTL162E
REDOLOG COPY REDOIN OPEN FAILED
DOB Support Offline Utils
The open of the input redolog on the REDOIN DD failed. The task terminates with a RC=12.
Check that the file is not in use by any other task. Check that the file is a valid VSAM REDOLOG. Rerun the job.
S6BTL163E
REDOLOG COPY REDOOUT OPEN FAILED
DOB Support Offline Utils
The open of the input redolog on the REDOOUT DD has failed. The task terminates with a RC=12.
Check that the file is not in use by another task. Check that the file is a valid VSAM REDOLOG. Rerun the job.
S6BTL164E
REDOLOG COPY REDOIN/OUT HI-U-RBA NOT EQUAL TO HI-A-RBA
DOB Support Offline Utils
A valid redolog has a VSAM HI used RBA equal to the HI alloc RBA. If either the input REDOLOG or the output REDOLOG does not meet this requirement, the file could be corrupt or not be a redolog.
Obtain a listcat of the respective redologs. Identify which one is invalid. Confirm that it is a redolog.
S6BTL165E
REDOLOG COPY REDOIN/OUT CI SIZE MISMATCH
DOB Support Offline Utils
The CISIZE for the input REDOLOG is different from the CISIZE of the output redolog. Both LOGS must have the same CISIZE for the copy to work.
Delete and redefine the target REDOLOG with the correct CISIZE. Reformat the target redolog. Rerun the copy task.
S6BTL166E
REDOLOG COPY DATASET SIZE MISMATCH
DOB Support Offline Utils
The input and output redologs are not the same size. For the copy to work, they must be the same size. The task is terminated with RC=12.
Delete and redefine the target REDOLOG with the correct CISIZE. Reformat the target redolog. Rerun the copy task.
S6BTL167E
REDOLOG COPY REDOOUT DATASET NOT FORMATTED
DOB Support Offline Utils
The target redolog is not formatted. The copy is terminated with RC=12.
Check that the target redolog is the correct data set. Reformat the target redolog. Rerun the copy task.
S6BTL168E
REDOLOG COPY INPUT DATASET IS FORMATTED - COPY DISALLOWED
DOB Support Offline Utils
The input REDOLOG is formatted. The copy task terminates with RC=12.
Check that you have specified the correct REDOLOG, and then rerun the job.
S6BTL169E
REDOLOG COPY I/O ERROR WRITING REDOOUT
DOB Support Offline Utils
An I/O error occurred while writing to the target REDOLOG. The job is terminated with RC=12.
Refer to message S6BTL172E for VSAM feedback codes to determine the cause of the error.
S6BTL170E
REDOLOG COPY I/O ERROR READING REDOIN
DOB Support Offline Utils
There was an I/O error reading the input REDOLOG. The job is terminated with a RC=12.
Refer to message S6BTL172E for VSAM feedback codes to determine the cause of the error.
S6BTL171E
REDOLOG COPY I/O ERROR READING REDOOUT
DOB Support Offline Utils
There was an I/O error reading the target redolog.
Refer to message S6BTL172E for VSAM feedback codes to determine the cause of the error.
S6BTL172E
REDOLOG COPY I/O ERROR RC=__ FB=
DOB Support Offline Utils
An I/O error occurred processing either the REDOIN or REDOOUT DD. This message contains the VSAM return code and feedback code, and is issued after messages S6BTL169E, S6BTL170E, or S6BTL171E.
Refer to the appropriate IBM manual for the meaning of the VSAM error codes.
S6BTL173I
REDOLOG COPY REDOIN CI COUNT =
DOB Support Offline Utils
This message indicates the number of control intervals (CIs) read from the input REDOLOG.
None - Information only.
S6BTL174I
REDOLOG COPY REDOOUT CI COUNT = ____
DOB Support Offline Utils
This message indicates the numbers of control intervals (CIs) written to the output REDOLOG.
None - Information only.
S6BTL175E
CACHE OPEN ERROR DETECTED
DOB Support Offline Utils
During the execution of a utility where the cache is processed, the cache data set open failed.
Review the job log for further identification of the problem.
S6BTL176E
DATASET MUST BE CONTAINED WITHIN ONE EXTENT
DOB Support Offline Utils
When formatting a Data Object Broker file, Object Service Broker detected that the allocation required multiple extents. This is not supported.
Do one of the following:

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