Based on the manual, it seems your understanding is correct. However, I would
look at the dump statistics from IFASMFDP to verify that type19 are not present.
I have explicitly coded SYS(NOTYPE(19)).
Also check for record suppressing in the SMF exit(IEFU83/IEFU84). In this case,
the data is gathered and discarded. NOTE: Turning off SMF19 (SYS(NOTYPE) took 5
minutes off my IPL time.
The display below indicates that there is a reserve on MSTCAT from SYSID MVS1.
Do a 'D U,,ALLOC,4299,1' and
D GRS,C
when the issue is occurring (on MVS1).
I would expect some long-running task that issues a reserve (e.g. DF/DSS, DFHSM
w/ADRDSSU option,....) to be running.
I would expect (at a minimum) that the CATALOG task is allocated to the volume.
There are a number of low-level items that can affect this. We'll know more
with the results of the display commands above.
HTH,
<snip>
Looks like we are not collecting smf 19 on either system. The grs display below
is for the sandbox, the production lpar was kind of long so I did not paste it
here but it did not contain dasd files just tape volsers. tks
RESPONSE=MVS1
IEE457I 10.48.44 UNIT STATUS 010
UNIT TYPE STATUS VOLSER VOLSTATE
4299 3390 A -R MSTCAT PRIV/RSDNT
D U,,,4299,1
IEE457I 10.49.31 UNIT STATUS 768
UNIT TYPE STATUS VOLSER VOLSTATE
4299 3390 OFFLINE /RSDNT
D GRS,C
ISG343I 10.50.41 GRS STATUS 770
NO ENQ RESOURCE CONTENTION EXISTS
NO LATCH CONTENTION EXISTS
SYS(TYPE(0:3,6:18,21:31,33,36:39,41:68,70:78,80:98,100:109,
110(0,2:5),111:254),
EXITS(IEFU83,IEFU84,IEFACTRT,IEFUJV,
IEFUSI,IEFUJI,IEFUTL,IEFU29),
INTERVAL(SMF,SYNC),DETAIL)
SYS(TYPE(0:3,6:18,21:31,33,36:39,41:68,70:78,80:98,100:255),
EXITS(IEFU83,IEFU84,IEFACTRT,IEFUJV,
IEFUSI,IEFUJI,IEFUTL,IEFU29),
INTERVAL(SMF,SYNC),DETAIL)
</snip>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
