On 1/17/2006 2:38 AM, Víctor de la Fuente wrote:
Our problem is also SMF starts losing data before all files are full:
IEE979W SMF DATA LOST - NO BUFFER SPACE AVAILABLE TIME=08:19:30
...
D SMF
IEE974I 08.20.04 SMF DATA SETS 177
NAME VOLSER SIZE(BLKS) %FULL STATUS
P-SYS1.MAN1E1 CGEHAA 43200 100 CLOSE PENDING
S-SYS1.MAN1E2 CGEHAB 43200 16 ACTIVE
S-SYS1.MAN1E3 CGEHAC 43200 0 ALTERNATE
S-SYS1.MAN1E4 CGEHAD 43200 0 ALTERNATE
S-SYS1.MAN1E5 CGEHAE 43200 0 ALTERNATE
So sys1.man1e1 does not reach "Dump Required" state, and also SMF has used
all of his space available...
The fact that SYS1.MAN1E1 is "CLOSE PENDING" rather than "DUMP REQUIRED"
does not seem relevant to your problem. You DO have an ACTIVE data set:
SYS1.MAN1E2, which should be able to record the records. Thus, the
switch has occurred, even if the old data set is not yet available for
dumping.
Assuming that SYS1.MAN1E1 does go to "DUMP REQUIRED" and you can dump
it, before you fill SYS1.MAN1E5, then your only problem is that your
in-storage buffers are filling before they can be written to
SYS1.MAN1E2, and for that you need more buffers or faster DASD, I think.
Walt
----------------------------------------------------------------------
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
