HSM and command LIST

[samb01]

Hello,

i have deleted dataset mirgated in HSM getting from the list command :

Code: Select all

HSEND WAIT LIST LEVEL(X.GTFD) MCDS -    
SELECT(AGE(365))                        -
 

After deleting those datasets, i run this command list again
and i have the same list .
I can't anderstand why i have the same list because i have deleted the dataset of this list..

[expat]

Was the dataset really deleted,

You say that it was, but where is the output to prove it. RACF problems perhaps ?
The fact that the listing says that it is there tends to make me believe HSM rather than you.

[samb01]

I'm sorry you can't believe me.
But i don't have anymore the sysout of the job wiche have deleted the dataset but i 've just run an extract for example :

Code: Select all

Command ===>                                                  Scroll ===> CSR  
****** ***************************** Top of Data ******************************
000001 1- DFSMSHSM CONTROL DATASET - MIGRATED DATASET-- LISTING ----- AT 10:05:
000002                                                                        
000003  DATASET NAME                                 MIG     LAST REF MIGRATED
000004                                               VOLUME     DATE    DATE  
000005                                                                        
000006  X.DEPT1.REPRISE                         751904  17/11/15 18/01/22
000007       ENCRYPTION TYPE = *******  KEYLABEL = ****************************
000008  X.EM.SUPAA.ATTSXXX.DX7101Y              801191  07/10/30 07/12/10
000009       ENCRYPTION TYPE = *******  KEYLABEL = ****************************
000010  X.EM.SUAAR.ATTSXXX.DX7102Y              801191  07/10/30 07/12/10
000011       ENCRYPTION TYPE = *******  KEYLABEL = ****************************

 

and for example, the dataset : X.DEPT1.REPRISE
is not migrated and not on catalog because it was deleted.

So i think there is a probleme with the MCDS...

[NicC]

What happens when you try recalling X.DEPT1.REPRISE?

[willy jensen]

As the datasets are still there, you could try the delete again and post the output.

[enrico-sorichetti]

all depends on which delete command was used

one of them issues both a delete and an hdelete
the other one just a simple delete

[samb01]

we used thois jcl to suppress the dataset miragted :

Code: Select all

//HDELETE EXEC PGM=IKJEFT01,REGION=512K                          
//SYSPRINT DD SYSOUT=*                                          
//SYSTSPRT DD SYSOUT=*                                          
//SYSTSIN  DD *                                                  
 PROFILE NOPREFIX                                                
 HDELETE X.DEPT1.REPRISE
 HDELETE ...    
 

I can't do an hrecall of the dataset because tey were deleted by the batch...

May be there is a problem with the control dataset..

I found this link : https://www.ibm.com/support/knowledgece ... /fxcds.htm

may be i have to fix it ?

[expat]

I would suggest at the very least that you perform an audit of the control datasets, as this picks out errors / anomolies in the xCDS datasets, along with the option to automatically apply fixes.