Sorry for the fuss I generated. The workaround I referred to is nothing
more than an SDSF 'filter' so as to ignore any APPC output. We could not
live long or well without APPC functions.
The workaround was suggested by SDSF Level 2. It assumes that you're
running the SDSF user exit ISFUSER . We added the following line way up at
the front after label INITCK as the first instruction on the first call:
NI UPRSFLG2,X'FF'-UPRAPPC *TEMP* TURN OFF APPC DISP
This resolved the problem, but of course we can't look at APPC process
output. APPC itself works perfectly fine.
.
.
JO.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
[EMAIL PROTECTED]
"Chase, John"
<[EMAIL PROTECTED]
> To
Sent by: IBM IBM-MAIN@BAMA.UA.EDU
Mainframe cc
Discussion List
<[EMAIL PROTECTED] Subject
.EDU> "Turning off APPC"? (was RE: SDSF
slow after migration to z/OS 1.9)
05/28/2008 04:57
AM
Please respond to
IBM Mainframe
Discussion List
<[EMAIL PROTECTED]
.EDU>
> -----Original Message-----
> From: IBM Mainframe Discussion List On Behalf Of Skip Robinson
>
> We saw this problem during our 1.9 ESP when we went to our
> first production system. Turning off APPC resolved the
> slowdown. Seems no one has sorely missed APPC output, so
> we've left it off for the time being.
By "turning off APPC", do you mean system-wide? Or just "within SDSF"?
If "system-wide", that implies we'll have to re-work our connectivity
between Rational Developer for System z (RDz) and z/OS from APPC to the
SCLM interface, and we've not heretofore done anything with SCLM.
-jc-
----------------------------------------------------------------------
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
