Page 1 of 1

DFHSM ABACKUP

PostPosted: Mon Jan 17, 2011 12:37 am
by DFuhr2010
Trying to locate error in a DFHSM ABACKUP process. Receiving ARC6164E RC99 X'0000029'. Dynamic allocation error. Cannot isolate the data set it is having the issue with. Reran the ABACKUP with same results. System messages manual is not clear on where to track the issue. Any suggestions would be greatly appreciated.

Re: DFHSM ABACKUP

PostPosted: Mon Jan 17, 2011 1:59 am
by dick scherrer
Hello,

The diagnostic info presented for the ARC6164E should look like:

ARC6164E DYNAMIC {ALLOCATION | DEALLOCATION | RETRIEVAL} FAILED FOR
{dsname | volser | ddname} DURING AGGREGATE {BACKUP | RECOVERY} -
SVC 99 REASON CODE IS reason-code, INFORMATION CODE IS infocode,
EXTENDED REASON CODE IS extreas


which should show the dataset name.

Re: DFHSM ABACKUP

PostPosted: Mon Jan 17, 2011 2:15 am
by DFuhr2010
You are correct. The data set name is DFHSM.HMIGTAPE.DATASET. How can I determine which one. No volume mount issued for the request. Just ends with RC-164

Re: DFHSM ABACKUP

PostPosted: Mon Jan 17, 2011 2:45 am
by dick scherrer
Hello,

How can I determine which one.
I do not understand how there is an issue of "which one". The "one" will be the one the job is trying to use. . .

First this is posted:
ARC6164E RC99 X'0000029'.
Now this:
Just ends with RC-164

Suggest you work with your people who support hsm to resolve. Someone closer to what is actually going on will be much more able to help. . .

Re: DFHSM ABACKUP

PostPosted: Mon Jan 17, 2011 3:01 am
by DFuhr2010
Mr Scherrer
I am supporting the HSM functionality. I apologize for not being thorough and posting the full message. It is failing with SVC99 on DFHSM.HMIGTAPE.DATASET.
Full message is:
ARC6164E DYNAMIC ALLOCATION FAILED FOR DFHSM.HMIGTAPE.DATASET DURING AGGREGATE BACKUP - SVC 99 REASON CODE IS X'0000029C' INFORMATION CODE IS X'00000000' EXTENDED REASON CODE IS 00000

I am attempting to determine which ML2 tape it is. One filter in this aggregate are archlog data sets and they have over 80000 entries (of course most are on ML2).

Re: DFHSM ABACKUP

PostPosted: Mon Jan 17, 2011 3:34 am
by Robert Sample
There should be a mount message in the console log -- find it and you'll get the volume serial. It should show up in the HSM started task log as well (which is the console messages restricted to only the HSM started task), so you've got at least two places to look for the message.

Re: DFHSM ABACKUP

PostPosted: Mon Jan 17, 2011 6:10 am
by steve-myers
I looked up dynamic allocation error code X'029C. I found this -
Meaning: There was a library automation communication services (LACS) mount failure for
a device in a IBM 3495 Tape Library Dataserver.

System Programmer or Operator Action: Depending
on the messages accompanying this error reason
code, different actions are needed. For
required actions, see the accompanying message.
This is not particularly helpful. There should be more messages which are not here, but it does appear to indicate why there was no mount message.