I don't believe there are any profile effects. ISFUSER is executable code
that runs for each user at initialization, at exit, and many times in
between. Changing the exit code should change product behavior with no
memory of previous logic.
Mark Zelden
<[EMAIL PROTECTED]
CHNA.COM> To
Sent by: IBM [email protected]
Mainframe cc
Discussion List
<[EMAIL PROTECTED] Subject
.EDU> Re: "Turning off APPC"? (was RE:
SDSF slow after migration to z/OS
1.9)
05/28/2008 08:51
AM
Please respond to
IBM Mainframe
Discussion List
<[EMAIL PROTECTED]
.EDU>
On Wed, 28 May 2008 08:03:46 -0700, Skip Robinson
<[EMAIL PROTECTED]>
wrote:
>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.
>
>.
Will running with that for some period of time, then removing it
be okay since the value is saved in the profile? Or doesn't that affect
the profile setting? If it does, then (educated) users can turn it on
when
needed and then off again.
<snip>
Mark
----------------------------------------------------------------------
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
