Dataset Level backup failed By HSM

jayp_agrawal · New User Joined: 23 Jun 2005 Posts: 25 Location: Norwich

I am using ARCINBAK for taking dataset level backup by HSM.
it seems to be failing with message
BACKUP FOR PRD.PE.PE2C1X02.R08254.DATAF FAILED, RC = 058,REAS = 056.

I have included many datasets in the job. Some of them seems to be working fine but some are failing.
I have looked for error mesage also

ARC1358I BACKUP FAILED FOR DATA SET
56 Data set backup to TAPE is not allowed.

I am not sure what might have caused this problem. as we have not changed anthing from a long time in HSM parameters and everthing seemed to work fine earlier.

expat · Posted: Sat Jan 03, 2009 2:38 pm

Why not use HBACKDS instead, much more efficient.

nevilh · Active User Joined: 01 Sep 2006 Posts: 262

You would first want to verify that BACKUP of data sets was not HELD
for any reason. Issue QUERY SETSYS and look for message ARC0163I to see what it says.
Data set BACKUP is controlled by Management Class attribute:
There are several other scenarios where events such as ARC0381A caused the occurance of messages ARC1388W and ARC1389E. The number of TAPE BACKUP tasks in those cases had been reduced to zero.
Had you seen such messages sometime earlier on this system (could have been a few days ago).
You can try verifying if this is the case by displaying the BGCB
control block with command:
hsend display (.bgcb.+0) lengths(248) ods('userid.bgcb')
At offset x'82' you will see what was specified, and at offset x'8A'
what the number of allowed tape backup tasks currently is.

jayp_agrawal · New User Joined: 23 Jun 2005 Posts: 25 Location: Norwich

I checked, dataset backup was not held.Though, I believe second suggestion by you 'There are several other scenarios where events such as ARC0381A caused the occurance of messages ARC1388W and ARC1389E. The number of TAPE BACKUP tasks in those cases had been reduced to zero.
Had you seen such messages sometime earlier on this system '

might have caused the problem. During that day uses of tapes drives was quite high and there was no tape drive available for the whole day, this might have caused tapebackup tasks to reduced to 0.

we run release dataset backup and then tried running backup for these datasets, It ended Ok.

Thanks a lot for your help.

expat · Posted: Mon Jan 05, 2009 5:22 pm

nevilh · Active User Joined: 01 Sep 2006 Posts: 262

Aha....... I was thinking in terms of machine eficiency ...... had not considered JCL coding etc