Classification: UNCLASSIFIED Caveats: NONE EMERGENCY was the explanation. Thanks Allan. I believe that HSM set EMERG=YES when the Journal dataset got a D37-04.
Thanks again... -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Staller, Allan Sent: Wednesday, January 22, 2014 1:35 PM To: [email protected] Subject: Re: DF/SMShsm HRECALL request waiting forever (UNCLASSIFIED) Issue hsend query setsys. Check for EMERGENCY (should be NO). If YES, HSEND SETSYS NOEMERGENCY. Is there a BACKVOL CDS in progress (or failed). If so, complete the BACKVOL and retry. Is this ML1 volume shared among multiple HSM images? Check for outstanding enqueues on the MCDS. If none of the above bears fruit, get a dump and open an issue w/IBM. While getting the dump to IBM, restart HSM and see if that clears the condition. HTH, <snip> Yes, I believe so. It is SMS-managed: the smallest FREE-CYL size in the SG is CYL(389) and all volumes in the SG have between TRK(2385) and TRK(19860) free in one extent. </snip> Alan <snip> Is there enough space on the volume you are attempting to recall to? <snip> ARC0101I QUERY ACTIVE COMMAND STARTING ON HOST=2 ARC0144I AUDIT=HELD AND INACTIVE, LIST=NOT HELD AND 843 ARC0144I (CONT.) INACTIVE, RECYCLE=HELD AND INACTIVE, REPORT=NOT HELD ARC0144I (CONT.) AND INACTIVE ARC0160I MIGRATION=HELD, AUTOMIGRATION=HELD, 844 ARC0160I (CONT.) RECALL=NOT HELD, TAPERECALL=NOT HELD, DATA SET ARC0160I (CONT.) MIGRATION=INACTIVE, VOLUME MIGRATION=INACTIVE, DATA ARC0160I (CONT.) SET RECALL=INACTIVE ARC0163I BACKUP=HELD, AUTOBACKUP=HELD, RECOVERY=NOT 845 ARC0163I (CONT.) HELD, TAPEDATASETRECOVERY=NOT HELD, DATA SET ARC0163I (CONT.) BACKUP=NOT HELD, VOLUME BACKUP=INACTIVE, DATA SET ARC0163I (CONT.) RECOVERY=INACTIVE, VOLUME RECOVERY=INACTIVE ARC0276I DATA SET BACKUP=INACTIVE, DATA SET BACKUP 846 ARC0276I (CONT.) ACTUAL IDLETASKS=(ALLOC=00, MAX=00) </snip> <snip> After an HRECALL is issued for dataset A.B.C, the request remains waiting and is not fulfilled. Cancelling all requests and reissuing HRECALL produces identical results. A.B.C HRECALL RC=0 MIGRAT1 QUERY REQ displays: ARC0101I QUERY REQUEST COMMAND STARTING ON HOST=2 ARC0167I RECALL MWE FOR DATA SET A.B.C FOR USER xxxxxxx, REQUEST ARC0167I (CONT.) 00000093, WAITING TO BE PROCESSED, 00000 MWE(S) AHEAD OF THIS ARC0167I (CONT.) ONE ARC0101I QUERY REQUEST COMMAND COMPLETED ON HOST=2 HLIST displays: DSN=A.B.C MIGVOL=SHSM05 DSO=PO SDSP=NO LAST REF=13/11/15 MIG=13/11/17 TRKS=0001020 2K BLKS= 0026219 TIMES MIG= 00001 16K BLKS=****** LAST MIGVOL=****** ARC0140I LIST COMPLETED, 3 LINE(S) OF DATA OUTPUT I find no additional information in SYSLOG or in the DFHSM logs. The DFHSM address space is not waiting on any ENQ, D GRS,C shows no contentions and D GRS,RES=(*,A.B.C) shows no users Can anybody help me determine the reason that HSM is waiting? </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN Classification: UNCLASSIFIED Caveats: NONE Classification: UNCLASSIFIED Caveats: NONE ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
