I believe turning off "write to programmer" messages with TSO PROFILE
NOWTPMSG will hide the ICH408I but you might miss something else you want
to see.
Cheers,
Mick.
On 4 July 2018 at 09:47, Barbara Nitz wrote:
> Something has changed with SDSFAUX between z/OS 2.1 and z/OS 2.3.
>
> Under z/OS 2
has not changed in SDSF 2.3.
Access to ISF.CONNECT only allows the user to use SDSF server provided
facilities, it does not grant access to any command and it does not override
ISFCMD SAF authority.
The access check to ISF.CONNECT was introduced in the SPE that introduced the
SDSFAUX server
I am curious: Why is Rocket Software defending missing SDSF actions and bad
documentation??? Has IBM 'outsourced' the SDSFAUX server?
I am annoyed with the ISFTABL thing (which we addressed in our logon
procedure), too, because that message was irritating all of us.
The ISF.CONNEC
On 7/4/2018 12:13 PM, Rob Scott wrote:
For the record, you do not need ISFTABL to be allocated for SDSF to function
and, in fact, I run without ISFTABL on many of the systems that I use.
If ISFTABL is not found, SDSF retrieves and stores system commands in the ISPF
profile dataset and in this
onley
Sent: Wednesday, July 4, 2018 5:01 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ISF.CONNECT.*
On 7/4/2018 11:23 AM, Rob Scott wrote:
> Tom,
>
> I think "cheated" is a bit strong.
>
> If migration actions were omitted it was not by design or with intention to
> deceive, it
For the record, you do not need ISFTABL to be allocated for SDSF to function
and, in fact, I run without ISFTABL on many of the systems that I use.
If ISFTABL is not found, SDSF retrieves and stores system commands in the ISPF
profile dataset and in this mode the user can store up to 50 commands
he ISFTABL message wasn't a migration action, I was
told flat out "It's not". I suspect Barbara got the same when asking
about the ISF.CONNECT profile.
Tom
--
For IBM-MAIN subscribe / signoff / archive acce
o:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Tom Conley
Sent: Wednesday, July 4, 2018 4:02 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ISF.CONNECT.*
On 7/4/2018 6:38 AM, Rob Scott wrote:
> Barbara,
>
> From the SDSF z/OS 2.3 Operation and Customization Guide :
>
> "As of z/OS V2
On 7/4/2018 6:38 AM, Rob Scott wrote:
Barbara,
From the SDSF z/OS 2.3 Operation and Customization Guide :
"As of z/OS V2R3, SDSF requires the SDSF and SDSFAUX address spaces to be
active for full functionality. The SDSF address space manages connections,
processes ISFPRMxx statements, handles
m, please raise an RFE as this will help the
development team prioritise the request.
Rob Scott
Rocket Software
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Barbara Nitz
Sent: Wednesday, July 4, 2018 9:47 AM
To: IBM-MAIN@LISTSE
Something has changed with SDSFAUX between z/OS 2.1 and z/OS 2.3.
Under z/OS 2.3, each and every user gets a RACF Message when they access their
part of SDSF (that's the primary RACF panel). That missing right is for
ISF.CONNECT.system, which is described as access to SDSFAUX. None of those
use
11 matches
Mail list logo
