S6BBRPGC requires an ERRORLOG file created by S6BBRPTR. Check your JCL to ensure the file is correctly specified. S6BBRPGC must be run immediately after the S6BBRPTR which created the ERRORLOG and before any activity on the segment.
S6BBRPGC requires an ERRORLOG file created by S6BBRPTR. Check your JCL to ensure file is correctly specified. S6BBRPGC must be run immediately after the HRNBRPTR which created the ERRORLOG and before any activity on the segment.
S6BBRPGC - ERRORLOG file segment number and segment number requested in the PARMS are not the same. S6BBRPGC must be run immediately after the S6BBRPTR which created the ERRORLOG and before any activity on the segment.
The ERRORLOG file must be current. Check that you are not running an old ERRORLOG against your segment, as this can have serious consequences. S6BBRPGC must be run immediately after the S6BBRPTR which created the ERRORLOG and before any activity on the segment.
There are certain page types in the database which are critical. If these page types are freed it could affect the segment to the extent that it becomes unusable or that the path to tables is lost. These page types include: "0" data set control page; "1" RTIX Index; "R" RTIX; as well as reserved system pages.
If the request in the ERRLOG was generated by S6BBRPTR, contact TIBCO Support for assistance. This problem should NOT occur; the segment from which the archive was taken could be seriously damaged. If the request was built manually, the reason for attempting this activity should be discussed with TIBCO Support before any further action is taken.
There are certain page types in the database which are critical. If these page types are modified it could affect the segment to the extent that it becomes unusable or that the path to tables is lost. These page types include: "0" data set control page; "1" RTIX Index; "R" RTIX; as well as reserved system pages.
If the request in the ERRLOG was generated by S6BBRPTR, contact TIBCO Support for assistance. This problem should NOT occur; the segment from which the archive was taken could be seriously damaged. If the request was built manually, the reason for attempting this activity should be discussed with TIBCO Support before any further action is taken.
hrnbrptr which creates the ERRLOG used as input for this request selects a timestamp from one of the pages in the segment processed. hrnbrpgc then checks the timestamp against that in the same page on the target segment, if there is no timestamp in the ERRLOG then this error occurs and the request is aborted. This probably means that the ERRLOG was created by a previous (old) version of hrnbrptr, it could also mean that this orphan recovery is being run against the wrong version of the target segment.
If this version of the segment is in doubt then rerun hrnbrptr to create a new ERRLOG and try again. If after an investigation you wish to force hrnbrpgc to use the invalid ERRLOG then follow the instructions outlined in the product documentation. NOTE: This is a high-risk decision and should not be made lightly, the audit report will indicate that you made this choice
The hrnbrptr that created the ERRLOG used as input for this request selects a timestamp from one of the pages in the segment processed. hrnbrpgc then checks the timestamp against that in the same page on the target segment. If the timestamps do not match, this error occurs and the request is aborted. The failure to match could mean that this orphan recovery is being run against the wrong version of the target segment.
If after an investigation you want to force hrnbrpgc to use the invalid ERRLOG, follow the instructions outlined in the product documentation.
NOTE: This is a high-risk decision and should not be made lightly, the audit report will indicate that you made this choice.
Refer to the Utilities manual for your operating system for more information.
Indicates that the utility has determined that translation is not required. No character-file-field to character-table-field is specified in the Control File.
The record size of the input file is larger than is acceptable to hrnbrtbl (offline batch load); therefore, neither the input file nor the output file will be accepted as input to hrnbrtbl.
Warning only. The input file record size indicates it is probably not an unloaded Object Service Broker table. If it is, redo the unload and specify a record size closer to the maximum size of an Object Service Broker row. Refer to the Utilities documentation for your operating system for more information.
Invalid data has been encountered on the input file; the format does not match the file-definition on the Control File. The data in error is ignored and no sequence checking is performed on the error record.
You must ensure that Static Values on the Control File are correctly encoded to match the code page of the table data once loaded. Make sure when modifying the Control File manually that you do not inadvertently change the encoding of other Control File information. Any changes to Static Values must be done prior to attempting the load (hrnbrtbl).
z/OS only: Either the RECFM specified for OUTFILE is not compatible with INFILE (they must both be fixed or both be variable); or the RECFM specified for INPLACE is neither fixed nor variable.
Ensure that the input file is described correctly both in the Control File (-C) and on the command line (-m). If the requested process completed successfully, check that the format is specified correctly before using the translated file.
The utility attempts to continue processing using the segment number found in the data as the actual SEG. If the job finishes successfully, no action is required; however, if other errors occur, refer to the actions for those error(s).
This message is provided for information only. It is possible that an archive could contain corrupted data, and if hrnbrptr was not run against the archive prior to porting, this corruption could go undetected. If this job finishes successfully, run S6BBRPTR prior to using the output data set as a z/OS Archive.
The file size specified in the optional parameter BYTES does not match the actual size of the input data read. This can be because the BYTES value was incorrect or you ported the archive from Windows or Solaris into an FB rather than a VB data set. An FB LRECL could result in padding of the last record.
Data Object Broker failures can leave pages in an indeterminate state; the utility has found such pages. Database corruption should be fixed prior to porting, but may be done on z/OS after reformatting.
For PARM='REFORMAT=MVSLOAD' requests, the data set must be in Object Service Broker data format (DSBIFTYPE) and must have been FTPed in binary mode from Windows or Solaris.
For PARM='REFORMAT=OFFLINE' requests, the data set must have been created on Windows or Solaris using one of the offline unload utilities (hrnbrulb, hrnbrulh, or hrnbrula). It must also have been FTPed to z/OS in binary mode.
For PARM='REFORMAT=NOBDW' requests, the data set must have been originally created (on z/OS) as VB. When the data set was FTPed to Windows or Solaris, it must have been in binary mode with RDW enabled. When FTPed from Windows or Solaris to z/OS, it must have been in binary mode.
This indicates that there was data left after end of file and after building the last reformatted record. This could happen if the input (ported) data set is RECFM=FB (rather than VB) and the last record is padded to its full LRECL.
This indicates that there was data left after end of file and after building the last reformatted record. This could happen if the input (ported) data set is RECFM=FB (rather than VB) and the last record is padded to its full LRECL.
The TABLES table has a field, SEGMENT#, that should contain the segment number of the segment that contains ACCESSLOG's data. This utility does not accept a NULL value in this field.
Informational message only: the ACCESSLOG entry has been found in the MetaStor table index and its pointers are about to be checked to ensure that the data portion of the table is located on the MetaStor.
Informational message only: indicates that the target segment is about to be modified. If a failure occurs at this time you must assume that the target segment is unusable until restored from an archive.
Informational message only: indicates that the necessary changes have been made to the target segment to create an ACCESSLOG data allocation. If a failure occurs at this stage the target segment must be restored from archive before attempting a rerun of this utility.
Informational message only: The data allocation for ACCESSLOG on the target segment has been completed and the MetaStor pointers are about to be changed. A failure at this time requires that both the MetaStor and target segments be restored before attempting any further Pagestore processing.
The Data Object Broker must be shut down before running this utility and the target segment must exist. Check that you have allowed for the requirements of this utility and that the segment indicated in the PARM/OPTION is correct.
Attempt to discover how this situation occurred, bearing in mind that both these segments were in the process of being changed and must be considered unusable. Restore the backups taken prior to running this utility and try again.
