I think this might be your problem. Here's what I found in IBMlink:
The problem is with SDSF. The local fix is to issue SET CSORT OFF. CSORT
stands for cursor-sensitive sorting.
APAR PM59695 - PTF - UK77441 superceeded by UK79343 (neither ptf has been
received)
With CSORT enabled,
I heard the IBM support center received a problem call for product 'Jazz Tube'.
Turns out it was for JES2.
Alan
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Phil Smith III
Sent: Monday, August 26, 2013 6:36 PM
To:
Found it. IPCS option 6 and entered SYSTRACE TIME(LOCAL)
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Schwartz, Alan
Sent: Wednesday, July 03, 2013 9:36 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: SYSTRACE Timestamps
I seem to recall
You shouldn't make the maximum size too large.
There is a somewhat new health check called XCF_CF_STR_POLICYSIZE that Check
that structures in the CFRM active policy do not have too large a difference
between the value specified for INITSIZE and |the value specified for SIZE. All
IIRC, After restoring the dataset to the same volume I believe you can submit a
job with a /*JOBPARM PROCLIB=ddname where that's one of the proclib
concatenation DD's in the JES2 proc. That will have JES reallocate the
proclibs and you should be ok.
Alan Schwartz
ITO Global Services
There's a conflict here. The CA APAR says This APAR will have a greater
affect on regions running STGPROT=NO.
Jim said Therefore, on workloads (i.e. CICS running with STGPROT=YES) ,
this can show up as the z196 spending more time
Can't be both.
Alan Schwartz
ITO Global Services
From one of my old SHARE buttons A feature is a bug with seniority
Alan Schwartz
ITO Global Service Operations and Engineering
Xerox Business Services, LLC
www.xerox.com/businessservices
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf
