Go for it George 2M of real storage in @ LPAR and this can really save
you a recreate for a sticky problem. We have been setup this way for a
while no problems. Currently on 1.8 and looking forward to being able
to specify more than 1M @ CP in z/OS 1.9.
COM='TRACE ST,999K,BR=OFF IBM DEFAULT AFTER OA07896 IS 256K '
Best Regards,
Sam Knutson, GEICO
System z Performance and Availability Management
mailto:[EMAIL PROTECTED]
(office) 301.986.3574
Excellent firms don't believe in excellence Only in constant improvement
and constant change.
Tom Peters
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of George Dranes
Sent: Friday, September 07, 2007 11:54 PM
To: [email protected]
Subject: System Trace Table
I've been following the System Trace Table discussions and it sounds
like I
should probably be setting the table to 999K. We're currently at z/OS
1.8 so
999K seems to be the limit. Are there any issues I should be
considering
before I put TRACE ST,999K in my COMMNDxx member? Thanks for any help.
====================
This email/fax message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution of this
email/fax is prohibited. If you are not the intended recipient, please
destroy all paper and electronic copies of the original message.
----------------------------------------------------------------------
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
