HiDRO keeps logging itself off.

book

Article ID: 51151

calendar_today

Updated On:

Products

CA VM:Backup for z/VM CA VM:Backup High-Speed Disaster Recovery Option (HiDRO) CA Mainframe VM Product Manager CA VM:Manager Suite for Linux on System z CA VM:Manager Suite for z/VM VM SUITE

Issue/Introduction

Description:

  CATALOG CONDENSE 
  
   *----------------------------------------------------------------------- 
   *   1 SYBCON373E FSREAD ERROR 3 ON CATALOG FILE "SYBCAT  FNAMES  A1" 
   *   1 SYBCON008E OPERATION ENDED DUE TO ABOVE ERROR OR WARNING 
   *   0 SYBCTL291W 6:00:06.89 - TASK 1 ENDED ABNORMALLY  CODE=16 
   *======================================================================= 

Solution:

One of the files that comprise the HiDRO catalog structure is corrupted. If you try to xedit it, you should receive an FSREAD ERROR 3.

You will need to replace the 2 or 3 SYBCAT files (3 if running with SFS ON) from the most current copy. That will most likely be on the 291 disk of HIDRO. Once you find them, verify that copy of the file that is corrupted on the 191 disk, is *okay* on this one. If so, it is a simple matter of copying the files from the backup disk to the 191, all three.

It is recommended that you xedit several other files on the 191 disk to ensure that there are no other corrupted files, or a corrupted disk.

It may be that you have to restore the 191 disk back from the most recent backup. HiDRO backs up the 191 disk at the end of every job. Using the SM file from that job, you can construct a Restore command to restore that disk back. If you do have to use the tape backup, once restored, the CATalog UPDATE command needs to be executed. HiDRO's Command Reference Guide provides more information on this command.

Environment

Release:
Component: HIDRO