IDCAMS is recalling Dataset when deleting it

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

Hello,

We have some LPARS sharing same HSM control datasets. To reduce CPU usage by one LPAR, we put RECALL on hold in that system. and expected that all recall made in this lpar would be routed to some other lpars sharing same recall queue.

after making these changes when i submitted recall in the lpar where we have put recall on hold, recall request was properly directed to some other lpar and was executed successfully.

When I am using IDCAMS Delete statetmenet to delete some migrated datasets in the lpar where we have put recall on hold. it is working fine.
but when same is done by some production jobs. it is trying to recall those datasets and since migration is held job is failing.

So I have two problems here.

1. Why IDCAMS delete statement is issuing a recall?

2. if a recall is made by IDCAMS delete statement why it is not getting
routed to some other lpar which are sharing same recall queue?

expat · Posted: Sun Mar 29, 2009 3:10 pm

1) Please post the IDCAMS statements

2) Without access to the HSM logs, parameter file and your SMS ACS routines it would be a little difficult to tell. I do recall a similar situation in the past but can not for the life of me remember the solution. I do know that as an interim fix we substituted IDCAMS with IKJEFT01 and issued HDELETE WAIT commands for the datasets and then DELETE commands in the same IKJEFT01 step.

I will try and contact the other site and see if the will tell me

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

Sorry,Last time i put the information that was able to delete dataset using IDCAMS when it was in migrate status. but it was not the case. When I am trying to delete it using IDCAMS. it is trying to recall dataset which it can't as recall is on hold.

I have read some document for this and it seems that there are 2 categories (WAIT and NOWAIT) in which recall can be submitted. When I use HRECALL command then recall is submitted in WAIT catagory and then it is routed to some other lpar in which recall is not on hold.

When recalll is issued by IDCAMS when i try to delete any migrated dataset using IDCAMS that time recall might be issued with NOWAIT in the same lpar where recall is on hold, hence it fails.

Certainly we can put hdelete parameter in the job to delete the datasets.
but following are the problem.

1. Dataset is not migrated alll the time, so if HDELETE is used, it may fail when dataset is not migrated.

2. There are hundreds of jobs that will be affected by this. and we have to make change in all those jobs

3. Can't we change something in HSM or some other environment where when any RECALL is issued by IDCAMS(when we are trying to delete it). It should be submitted with WAIT catagory, so that recall request can be routed to some other lpar as it happpens in the case when we submit HRECALL command.

expat · Posted: Sun Mar 29, 2009 6:18 pm

That is why I asked to see your IDCAMS statements.

1) That is why I said to use HDELETE AND IDCAMS in the same IKJEFT01 step

3) Without access to the HSM logs, parameter file and your SMS ACS routines it would be a little difficult to tell.

Anuj Dhawan · Posted: Mon Mar 30, 2009 6:09 pm

Hi,

Is this been resolved? As asked earlier, why don't you show us the IDCAMS statements -we might take it from there?