HiDRO; COM220W catalog Job failed

Document ID:  TEC1089566
Last Modified Date:  08/04/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA VM:Backup High-Speed Disaster Recovery Option (HiDRO)

Releases

  • CA VM:Backup High-Speed Disaster Recovery Option (HiDRO):Release:2.8

Components

  • CA VM:Backup HiDRO:HIDRO
Question:

We recently used DIRMAINT to increase the virtual storage for SYBCOM.

Since making that update, we are receiving the following error that is listed in the SYBCOM LOG.



/*------------------------- SYBCOM LOG A -----------------------*/ 
06/21/17 08:00:01 PRTLOG EXEC 
06/21/17 08:00:01 RC= 0 
06/22/17 00:01:05 CATJOB- COM220W HIDRO catalog Job failed with RC = 8. 
06/22/17 00:01:05 IUSEND: User= DIRMAINT, RC= 74. COMMUNICATION SEVERED BY THE PARTNER 
06/22/17 00:15:06 HIDRO $REFRESH 
06/22/17 08:00:00 SYBMON CMD PRTLOG , NOERASE NORPC 

 

 

What does this mean?

 

 

Environment:
Running HiDRO and using DIRMAINT to make directory updates.
Answer:

 

 

This is specific to DIRMAINT's auditing. DIRMAINT writes an audit record for every directory entry that gets changed and during DIRMAINT's end-of-day processing, it sends a file 
to any user who has had their directory entry updated, notifying them of the changes made. 

DIRMAINT keeps these audit records for a 3-month period and sends the end user a notification of that change each time its housekeeping tasks are run.  We believe this to be configurable but IBM will know for certain.

 

So, the directory update that was recently made to SYBCOM is what triggered all of this. 
When DIRMAINT's housekeeping runs at midnight, it checks its AUDIT disk for any directory updates that have been made and then sends those users a notification of such. 

That's what SYBCOM is receiving from DIRMAINT each night and causing the COM220W warning. SYBCOM expects a job file, not something like this from DIRMAINT. 

You may want to contact IBM and ask them how to prevent DIRMAINT from sending a file to every user whose directory gets updated.  

 

You may also want to consider deleting SYBCOM's audit file from DIRMAINT's audit disk (or wherever it keeps these records), that way, none of this will occur. 

 

 

Additional Information:

DIRMAINT's daily processing reads the audit disk and sends out the notifies which are in the form of a RDR file.

IBM should be able to advise you how to disable that, or, how to change the retain from months to days. 

 

 

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >