Weeeelllll,
after setting GRSQ to CONTENTION (IBM default) and fortunately Q=NO, too, NDM
proved true to prediction and dumped again in production with an 'already
fixed' problem :-)
But: Here's the relevant part of the dump statistics (some stuff snipped):
Dump was complete
Total dump capture time 00:00:59.980731
System nondispatchability start 09/18/2042 01:53:47.370496 - nice
System set nondispatchable 09/18/2042 01:53:47.370496
Time to become nondispatchable 00:00:00.000000
Global storage start 04/15/2008 18:37:11.899468
Global storage end 04/15/2008 18:37:19.323612
Global storage capture time 00:00:07.424144
System reset dispatchable 09/18/2042 01:53:47.370496
System was nondispatchable 00:00:00.000000
Asid 01DA (NDM):
Local storage start 04/15/2008 18:37:12.316164
Local storage end 04/15/2008 18:38:11.861746
Local storage capture time 00:00:59.545582
Tasks reset dispatchable 04/15/2008 18:38:11.861760
Tasks were nondispatchable 00:00:59.545596
Asid 0042 (VTAM):
Local storage start 04/15/2008 18:37:12.316141
Local storage end 04/15/2008 18:37:50.354166
Local storage capture time 00:00:38.038024
Tasks reset dispatchable 04/15/2008 18:37:50.354187
Tasks were nondispatchable 00:00:38.038046
Dump Exits
Exit address 04353880
Home ASID 0005
Exit start 04/15/2008 18:37:19.323615
Exit end 04/15/2008 18:37:45.453518
Exit time 00:00:26.129902
Exit attributes: Global, Sdump, SYSMDUMP
What the heck is the GRS exit doing so long with the IBM default of
grsq(CONTENTION)? This was longer than with the grsq(all) setting! It is still
a global exit and would still run during global nondisp when Q=YES is set.
Best regards, Barbara
--
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
