|
|
| Copyright © Cloud Software Group, Inc. All Rights Reserved |
A MetaStor page read operation failed.A target segment read page operation failed.The target segment cannot be reset in its present state.If the target segment contains data that you want to retain, the segment may be corrupted. Contact TIBCO Support. Otherwise, reformat the target segment and try again.At least one RTIX table entry exists on both the MetaStor and the target segment. The target segment cannot be reset under this condition.If needed data exists on the target segment, the segment cannot be reset. Otherwise, reformat the target segment and try the utility again.A problem was experienced with header data from the MetaStor. This may indicate data corruption.There is a page format problem on the MetaStor, which may indicate either data corruption or a newly formatted segment 0.If the MetaStor has not been completely built, complete the build according to the documentation. Otherwise, contact TIBCO Support.A target segment page has a bad page header.If the target segment contains needed data, contact TIBCO Support. Otherwise, format the segment and try again.No definition was found on the MetaStor for a table (name) that exists according to the RTIX.The FIELDS table entry indicates that more Secondaries exist for the table than the permitted maximum.Investigate and correct the table's definition data. If in doubt, contact TIBCO Support.A table's definition data is corrupted.A MetaStor page header corruption was encountered.During the processing of the group index or data trees for the table being reset, an unexpected page type code was detected. Abend code 200 is issued.Validate the table structure using S6BBRPTR.A request was made to reset a segment (target) but no tables exist for it on the base segment.If the request is directed at the correct segment, this run is unnecessary.The audit trail (printer) failed to open. User abend code 932 is issued.No Data Object Broker communication identification specifiedNo communication identifier (e.g., VTAM name) is specified in the startup parameters data set.Specify the Data Object Broker's communications identifier in the startup parameters data set, BPARM. The format is:The target queue name is not specified in the STARTUP PARAMETERS data set.Specify the target queue name in the STARTUP PARAMETERS data set; the format is:The batch server is not able to communicate with the Data Object Broker.Check the execution status of the Data Object Broker. The Data Object Broker must be active when the batch server is running. You may find messages in the batch server or Data Object Broker JES joblogs to explain why communications cannot be established or sustained.The batch server failed to connect with the Data Object Broker.
|
|
| Copyright © Cloud Software Group, Inc. All Rights Reserved |