errors

[vmsserbo]

While running our backups we received these errors?

What exactly are they and what could have caused this?? Do I need to look at any other logs.

Received numerous file access conflict errors.

%SET-E-READERR, error reading DUA4:[RMS]SUSPFIL.DAT;53 -SYSTEM-W-ACCONFLICT, file access conflict %SET-E-READERR, error reading DUA4:[RMS]SYSPATH.DAT;35 -SYSTEM-W-ACCONFLICT, file access conflict

SYSTEM-F-DUPLNAM, duplicate name
12-JUL-2006 22:08:36
FINISHED RESET_RMS_PROT
ANY ERROR ABOVE WILL NEED TO BE INVESTIGATED ???

[Ian Miller. · Accepted solution]

The files
DUA4:[RMS]SUSPFIL.DAT;53
DUA4:[RMS]SYSPATH.DAT;35

where open at the time that a SET command tried to do something to them and the SET command failed. If this is not the normal case then investigate what may have been running that had those files open.

[vmsserbo]

Thanks!

Normally no users should be logged in the system during backups. What should I look at to see what was running??

[Volker Halle]

Miles,

determining which jobs were still running and had those files opened will be difficult or impossible afterwards. You could look at accounting records to determine, which jobs might have been running at that time.

You could add the following command in your DCL procedure, if the SET FILE command returns with an error:

$ SHOW DEV/FILES DUA4:

This would show the open files on that disk (on the local node) and the processes, which were accessing them.

Volker.

[Mike Kier]

Miles,

Any chance you had two copies of the backup procedure running at the same time? That could explain the access conflicts as well as the DUPLNAM error if the procedure is attemting to set a fixed process name.

This situation might be the result of a prior backup run waiting for an operator to put a tape in the drive if the running backup exceeded the capacity of the first tape.

[vmsserbo]

I was about to look into that! Thanks! MAybe?

[Arch_Muthiah]

Miles,

If it is in a cluster env, this access conflict error common.

You can use SYSMAN command to find any access conflict cluster wide

$ MCR SYSMAN
SYSMAN> SET ENVIRONMENT/CLUSTER
SYSMAN> DO SHOW DEVICE disk-name

Archunan

[Arch_Muthiah]

Miles,

Pls make sure there are no scheduled job running and there are chances any of those scheduled job and scheduler may attempt to use the SET FILE command to set global buffers or statistics on a file, this alsocause SET-E-READERR errors.

Btw, have you resolved your problem?


Archunan