|
View previous topic :: View next topic
|
| Author |
Message |
kavikesav
New User
Joined: 22 Mar 2007
Posts: 21
Location: chennai
|
|
|
|
| Is there any commands available in rexx to find ut the number of datsets present before our dataset in the recall queue... |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10889
Location: italy
|
|
|
|
I do not remember the existance of such a command,
but anyway the info You might get from it does not really have much meaning
standard disk recalls are processed in fifo order
SDSP disk recalls same thing
tape recalls are fifo/batched, it means that HSM will try to optimize the tape mounts recalling in one "logical step" all the datasets residing on that tape volume
( so the processing order of the recalls is unpredictable, without looking at the hsm MCDS ) |
|
| Back to top |
|
|
cpuhawg
Active User
Joined: 14 Jun 2006
Posts: 331
Location: Jacksonville, FL
|
|
|
|
TSO HQ works in our office to display DFSMShsm requests. TSO HELP HQ explains its usage.
You could probably build an REXX around the command using OUTTRAP. Capture and edit the returned information to suit your needs. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10889
Location: italy
|
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8796
Location: Welsh Wales
|
|
|
|
| Q WAITING ??? |
|
| Back to top |
|
|
kavikesav
New User
Joined: 22 Mar 2007
Posts: 21
Location: chennai
|
|
|
|
| Yes ... I want to know how many datasets are waiting before mine to recall in the queue |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8796
Location: Welsh Wales
|
|
|
|
Well, we both have the link to the manual, and I am not going to look at it for you.
Also, HSM will perform all recalls from the same tape in one mount, so if your request is queued last it may be the next one to be executed. Conversely it may be number 1 in the queue but be the last request executed.
I think that you will also find that a REXX that issues a Q ??? command will be unable to outtrap the results because HSM will only write to its own log for these requests. |
|
| Back to top |
|
|
db2sysdba.zos
New User
Joined: 04 Oct 2011
Posts: 25
Location: INDIA
|
|
|
|
/*REXX*/
"ALLOC FI(IN1) DA('PADMANA.HQUERY.INPUT') SHR REUSE"
"EXECIO * DISKR IN1(STEM INDD. FINIS"
"FREE FILE(IN1)"
C=1
DO A = 1 TO INDD.0
GROUP = WORD(INDD.A,1)
CMD = "HQUERY DATASETNAME("GROUP") REQUEST("A")"
/* SAY CMD */
CALL OUTTRAP "D."
CMD
CALL OUTTRAP "OFF"
OUT1.C =CMD
C=C+1
DO B = 1 TO D.0
OUT1.C = D.B
C=C+1
END
DROP D.
END
SAY DONE
"ALLOC FI(OUT1) DA('PADMANA.HQUERY.OUTPUT') SHR REUSE"
"EXECIO * DISKW OUT1(STEM OUT1. FINIS"
"FREE FILE(OUT1)"
|
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8796
Location: Welsh Wales
|
|
|
|
Enrico, the stats of dormancy if you please 
db2sysdba.zos
Perhaps you could show the results and how this will help determine the number of requests to execute before the selected recall. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10889
Location: italy
|
|
|
|
not worth calculating, just around three years  |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8796
Location: Welsh Wales
|
|
|
|
| 4 years minus 4 days |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10889
Location: italy
|
|
|
|
OK OK... here it is
The topic has been resurrected after
| Code: |
... 4 year(s) - (months difference / 12 )
... 4 year(s) - (difference )
... 48 months
... 1456 days
... 34964 hours
... 2097896 minutes
... 125873760 seconds
... 125873760 seconds
... 2097896 minutes
... 34964 hours
... 1456 days
... 48 months
... 4 year(s) - (difference )
... 4 year(s) - (months difference / 12 )
|
|
|
| Back to top |
|
|
|
|
