A more recent option worth checking, EMPTYEXCPSEC.
9000 SMF 30 records means a large number of something, empty EXCP
sections is a likely culprit.
EMPTYEXCPSEC(NOSUPPRESS|SUPPRESS)
Specifies whether to suppress empty execute channel program (EXCP) entries
in the SMF type 30 record. IBM recommends that the SUPPRESS option is
specified.
NOSUPPRESS
Specifies that the system generates an empty SMF type 30 record EXCP
section for each SMS candidate volume in the storage group that is not
allocated to the DD statement. By default, empty EXCP sections are also
generated for non-dataset allocations like DD DUMMY or spool file
allocations.
SUPPRESS
specifies that the system suppresses the creation of empty EXCP sections
for non-allocated candidate volumes in the SMS storage group. With this
option, empty EXCP sections that are generated for non-dataset allocations
like DD DUMMY or spool file allocations are also suppressed.
Default: NOSUPPRESS
Andrew Rowley
On 4/11/2016 12:23 AM, Vernooij, Kees (ITOPT1) - KLM wrote:
That's an old one, we ran into this 25 years ago. To my surprise the default is
currently still YES.
Kees.
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Mark Jacobs - Listserv
Sent: 03 November, 2016 14:03
To: [email protected]
Subject: Re: DB2 Shutdown Problem
Check your SMF options, If DDCONS(NO) is not set, that may be your problem.
Steve Carlson (Contractor) <mailto:[email protected]>
November 3, 2016 at 9:00 AM
When trying to shut down the DB2 regions on our Development LPAR the
DB2M1 regions are taking over 1 hour to shut down. I have also noticed
that over 9000 SMF Type 30 records for the DBM1 STC's are being
generated during this time. Here is a list of the DB2 STC's:
DB2YADMT
DB2YDBM1
DB2YDIST
DB2YIRLM
DB2YMSTR
DB2YWLM2
The following commands were issued before shutting down this DB2 region:
-DB2Y DISPLAY THREAD(*)
-DB2Y DIS UTILITY(*)
-DB2Y DIS DDF
All of the STC's except for DB2YDBM1 come down within about 10
minutes. Also these STC's have been up and running for over 60 days
and are at Release 10. The DB2YDBM1 takes over 1 hour to come down.
Has anyone else seen this problem, and what did you do to resolve this
problem?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
Please be alert for any emails that may ask you for login information
or directs you to login via a link. If you believe this message is a
phish or aren't sure whether this message is trustworthy, please send
the original message as an attachment to '[email protected]'.
--
Andrew Rowley
Black Hill Software
+61 413 302 386
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
