Re: SDSF & TSS (RACF)

2022-06-09 Thread Rob Schramm
I had a couple of thoughts.
1) let them fail.  Fix security rules as needed or plan it a bit better.  I
think the STIGs are more in line with this thinking.
2) TSSINSTX may be used to alter the behavior you are talking about.  But I
still think that #1 is the way to go.

Rob

On Tue, May 24, 2022 at 1:04 PM Larre Shiller <
0102cb4997b0-dmarc-requ...@listserv.ua.edu> wrote:

> Mark -
>
> We use Top Secret as well and had the same issue that you are describing
> when we initially activated JESSPOOL control.  We happen to be using (E)JES
> instead of SDSF, but essentially we did the same thing that Robert
> described here--we use an (E)JES exit to alter the RACF call for JESSPOOL
> and set LOG=NOFAIL (as well as MSGSUPP=YES).  It does exactly what is
> necessary to make this function as you wish.  Obviously, I cannot comment
> on why the change that you made to SDSF did not appear to work, but if you
> can get SDSF to set LOG=NOFAIL for the security calls, Top Secret should
> "honor" that.  If you can't get it to work, perhaps you could open a Case
> with Broadcom and trace the security call to figure out what's going on.
>
> Larre Shiller
> US Social Security Administration
> "The opinions expressed in this e-mail are mine personally and do not
> necessarily reflect the opinion of the US Social Security Administration or
> the US Government.”
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: SDSF & TSS (RACF)

2022-05-25 Thread Robert S. Hansel (RSH)
Hi Mark,

The option prevents all the violations when you 's' select the entire job. It 
won't help when you
select the job with ? and then select individual SYSOUTs. For the latter, it is 
WAD.

Regards, Bob

Robert S. Hansel35 years of RACF Experience
Lead RACF Specialist
RSH Consulting, Inc.
617-969-8211
www.linkedin.com/in/roberthansel
www.twitter.com/RSH_RACF
www.rshconsulting.com

-Original Message-
From: Steely.Mark [mailto:steely.m...@aaa-texas.com] 
Sent: Wednesday, May 25, 2022 12:04 PM
To: IBM Mainframe Discussion List
Cc: Robert S. Hansel (RSH)
Subject: RE: SDSF & TSS (RACF)
Importance: High

Thanks for the update - yes I did forget the custom parameter. It may work for 
what I need. When I
select the complete report it comes back as unauthorized. If I expand the 
report with a ? and select
a report it still get the violation and after several attempt it suspend the 
ID. 
Is there anything for that ? 

Thank You 

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Robert S. Hansel (RSH)
Sent: Wednesday, May 25, 2022 5:53 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: FW: SDSF & TSS (RACF)

ATTENTION: This e-mail came from an external source. Do not open attachments or 
click on links from
unknown or unexpected emails.


Mark,

I'm surprised it didn't work. Did you code a CUSTOM(proplist) parameter in 
_all_ your GROUP
statements that points to the PROPLIST NAME(proplist) statement with the 
PROPERTY parameter? And did
you refresh the ISFPARMS in all the SDSF servers?

Regards, Bob

Robert S. Hansel35 years of RACF Experience
Lead RACF Specialist
RSH Consulting, Inc.
617-969-8211
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fin%2Froberthanse
ldata=05%7C01%7CSteely.Mark%40aaa-texas.com%7C343f2a1ca2e946e91dd008da3e41120f%7Cd5f618ff295149
048f7e999c2dd97ab2%7C0%7C0%7C637890746614106925%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoi
V2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=2p%2FVhwtS2wmMiwR5fCqnKzxRS25XLKssI
wHQysYGDRo%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.twitter.com%2FRSH_RACFdata
=05%7C01%7CSteely.Mark%40aaa-texas.com%7C343f2a1ca2e946e91dd008da3e41120f%7Cd5f618ff295149048f7e999c
2dd97ab2%7C0%7C0%7C637890746614106925%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLC
JBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=qHDXl9r%2Byff2po89gcCtFs3DsZD%2B5%2Bwv3OSmmgn
sek0%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rshconsulting.com%2Fdata=0
5%7C01%7CSteely.Mark%40aaa-texas.com%7C343f2a1ca2e946e91dd008da3e41120f%7Cd5f618ff295149048f7e999c2d
d97ab2%7C0%7C0%7C637890746614106925%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJB
TiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=ZyxHROF4eUWuXPXBbIR8Rls0H8o6qizNf9Ve6E7RWuA%3D&
amp;reserved=0

-Original Message-
Date:Tue, 24 May 2022 15:02:50 +
From:"Steely.Mark" 
Subject: Re: SDSF & TSS (RACF)

Thanks for the link for the output violations - it doesn't appear to work for 
TSS (Top Secret).


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Robert S. Hansel (RSH)
Sent: Tuesday, May 24, 2022 8:16 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SDSF & TSS (RACF)

ATTENTION: This e-mail came from an external source. Do not open attachments or 
click on links from
unknown or unexpected emails.


Hi Mark,

When a user attempts to select a job, SDSF does an authorization check for each 
individual SYSOUT
DDNAME associated with the job and can generate multiple violations like this.

To address this issue, see article " Avoiding Output Browse Violation Messages 
in SDSF" in the July
2008 issue of our RACF Tips newsletter.

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rshconsulting.com%2Fracftips%2
FRSH_Consulting__RACF_Tips__July_2008.pdfdata=05%7C01%7CSteely.Mark%40aaa-texas.com%7C343f2a1ca
2e946e91dd008da3e41120f%7Cd5f618ff295149048f7e999c2dd97ab2%7C0%7C0%7C637890746614106925%7CUnknown%7C
TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Cs
data=Ri6qk0FquenWot%2B7NtNwp4PQXBlpbgSzxcwFsX8E0UQ%3Dreserved=0

Regards, Bob

Robert S. Hansel35 years of RACF Experience
Lead RACF Specialist
RSH Consulting, Inc.
617-969-8211
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fin%2Froberthanse
ldata=05%7C01%7CSteely.Mark%40aaa-texas.com%7C343f2a1ca2e946e91dd008da3e41120f%7Cd5f618ff295149
048f7e999c2dd97ab2%7C0%7C0%7C637890746614106925%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoi
V2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=2p%2FVhwtS2wmMiwR5fCqnKzxRS25XLKssI
wHQysYGDRo%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.twitter.com%2FRSH_RACFdata
=05%7C01%7CSteely.Mark%40aaa-texa

Re: SDSF & TSS (RACF)

2022-05-25 Thread Rob Scott
Mark

When the user issues a browse request for the entire job, they may not be aware 
of the constituent output DDs and any security violations encountered may be  
out of their initial control (or expectation). It is not unreasonable in this 
case to tolerate the violations without penalty.

The selection of a specific output from the JDS (aka "?") action panel is 
deemed an deliberate action to browse a specific spool dataset and the custom 
property does not apply.

I assume that TSS would act the same (ie suspend the ID) if the user received 
repeated violations for attempts to read normal DASD datasets.

Rob Scott
Rocket Software


From: IBM Mainframe Discussion List  On Behalf Of 
Steely.Mark
Sent: 25 May 2022 17:04
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SDSF & TSS (RACF)
Importance: High

EXTERNAL EMAIL



Thanks for the update - yes I did forget the custom parameter. It may work for 
what I need. When I select the complete report it comes back as unauthorized. 
If I expand the report with a ? and select a report it still get the violation 
and after several attempt it suspend the ID.
Is there anything for that ?

Thank You

-Original Message-
From: IBM Mainframe Discussion List 
mailto:IBM-MAIN@LISTSERV.UA.EDU>> On Behalf Of Robert 
S. Hansel (RSH)
Sent: Wednesday, May 25, 2022 5:53 AM
To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>
Subject: FW: SDSF & TSS (RACF)

ATTENTION: This e-mail came from an external source. Do not open attachments or 
click on links from unknown or unexpected emails.


Mark,

I'm surprised it didn't work. Did you code a CUSTOM(proplist) parameter in 
_all_ your GROUP statements that points to the PROPLIST NAME(proplist) 
statement with the PROPERTY parameter? And did you refresh the ISFPARMS in all 
the SDSF servers?

Regards, Bob

Robert S. Hansel 35 years of RACF Experience
Lead RACF Specialist
RSH Consulting, Inc.
617-969-8211
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fin%2Froberthanseldata=05%7C01%7CSteely.Mark%40aaa-texas.com%7C343f2a1ca2e946e91dd008da3e41120f%7Cd5f618ff295149048f7e999c2dd97ab2%7C0%7C0%7C637890746614106925%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=2p%2FVhwtS2wmMiwR5fCqnKzxRS25XLKssIwHQysYGDRo%3Dreserved=0<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fin%2Froberthanseldata=05%7C01%7CSteely.Mark%40aaa-texas.com%7C343f2a1ca2e946e91dd008da3e41120f%7Cd5f618ff295149048f7e999c2dd97ab2%7C0%7C0%7C637890746614106925%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=2p%2FVhwtS2wmMiwR5fCqnKzxRS25XLKssIwHQysYGDRo%3Dreserved=0>
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.twitter.com%2FRSH_RACFdata=05%7C01%7CSteely.Mark%40aaa-texas.com%7C343f2a1ca2e946e91dd008da3e41120f%7Cd5f618ff295149048f7e999c2dd97ab2%7C0%7C0%7C637890746614106925%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=qHDXl9r%2Byff2po89gcCtFs3DsZD%2B5%2Bwv3OSmmgnsek0%3Dreserved=0<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.twitter.com%2FRSH_RACFdata=05%7C01%7CSteely.Mark%40aaa-texas.com%7C343f2a1ca2e946e91dd008da3e41120f%7Cd5f618ff295149048f7e999c2dd97ab2%7C0%7C0%7C637890746614106925%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=qHDXl9r%2Byff2po89gcCtFs3DsZD%2B5%2Bwv3OSmmgnsek0%3Dreserved=0>
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rshconsulting.com%2Fdata=05%7C01%7CSteely.Mark%40aaa-texas.com%7C343f2a1ca2e946e91dd008da3e41120f%7Cd5f618ff295149048f7e999c2dd97ab2%7C0%7C0%7C637890746614106925%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=ZyxHROF4eUWuXPXBbIR8Rls0H8o6qizNf9Ve6E7RWuA%3Dreserved=0<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rshconsulting.com%2Fdata=05%7C01%7CSteely.Mark%40aaa-texas.com%7C343f2a1ca2e946e91dd008da3e41120f%7Cd5f618ff295149048f7e999c2dd97ab2%7C0%7C0%7C637890746614106925%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=ZyxHROF4eUWuXPXBbIR8Rls0H8o6qizNf9Ve6E7RWuA%3Dreserved=0>

-Original Message-
Date: Tue, 24 May 2022 15:02:50 +
From: "Steely.Mark" 
mailto:steely.m...@aaa-texas.com>>
Subject: Re: SDSF & TSS (RACF)

Thanks for the link for the output violations - it doesn't appear to work for 
TSS (Top Secret).


-Original Message-
From: IBM Mainframe Discussion List 
mailto:IBM-MAIN@LISTSERV.UA.EDU>> On Behalf Of Robert 
S. Hansel (RSH)
Sent: Tuesday, May 24, 2022 8:16 AM
To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>
Subject: Re: SDSF & TSS (RACF)

ATTENTION: This e-mail c

Re: SDSF & TSS (RACF)

2022-05-25 Thread Steely.Mark
Thanks for the update - yes I did forget the custom parameter. It may work for 
what I need. When I select the complete report it comes back as unauthorized. 
If I expand the report with a ? and select a report it still get the violation 
and after several attempt it suspend the ID. 
Is there anything for that ? 

Thank You 

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Robert S. Hansel (RSH)
Sent: Wednesday, May 25, 2022 5:53 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: FW: SDSF & TSS (RACF)

ATTENTION: This e-mail came from an external source. Do not open attachments or 
click on links from unknown or unexpected emails.


Mark,

I'm surprised it didn't work. Did you code a CUSTOM(proplist) parameter in 
_all_ your GROUP statements that points to the PROPLIST NAME(proplist) 
statement with the PROPERTY parameter? And did you refresh the ISFPARMS in all 
the SDSF servers?

Regards, Bob

Robert S. Hansel35 years of RACF Experience
Lead RACF Specialist
RSH Consulting, Inc.
617-969-8211
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fin%2Froberthanseldata=05%7C01%7CSteely.Mark%40aaa-texas.com%7C343f2a1ca2e946e91dd008da3e41120f%7Cd5f618ff295149048f7e999c2dd97ab2%7C0%7C0%7C637890746614106925%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=2p%2FVhwtS2wmMiwR5fCqnKzxRS25XLKssIwHQysYGDRo%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.twitter.com%2FRSH_RACFdata=05%7C01%7CSteely.Mark%40aaa-texas.com%7C343f2a1ca2e946e91dd008da3e41120f%7Cd5f618ff295149048f7e999c2dd97ab2%7C0%7C0%7C637890746614106925%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=qHDXl9r%2Byff2po89gcCtFs3DsZD%2B5%2Bwv3OSmmgnsek0%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rshconsulting.com%2Fdata=05%7C01%7CSteely.Mark%40aaa-texas.com%7C343f2a1ca2e946e91dd008da3e41120f%7Cd5f618ff295149048f7e999c2dd97ab2%7C0%7C0%7C637890746614106925%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=ZyxHROF4eUWuXPXBbIR8Rls0H8o6qizNf9Ve6E7RWuA%3Dreserved=0

-Original Message-
Date:Tue, 24 May 2022 15:02:50 +
From:"Steely.Mark" 
Subject: Re: SDSF & TSS (RACF)

Thanks for the link for the output violations - it doesn't appear to work for 
TSS (Top Secret).


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Robert S. Hansel (RSH)
Sent: Tuesday, May 24, 2022 8:16 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SDSF & TSS (RACF)

ATTENTION: This e-mail came from an external source. Do not open attachments or 
click on links from unknown or unexpected emails.


Hi Mark,

When a user attempts to select a job, SDSF does an authorization check for each 
individual SYSOUT DDNAME associated with the job and can generate multiple 
violations like this.

To address this issue, see article " Avoiding Output Browse Violation Messages 
in SDSF" in the July 2008 issue of our RACF Tips newsletter.

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rshconsulting.com%2Fracftips%2FRSH_Consulting__RACF_Tips__July_2008.pdfdata=05%7C01%7CSteely.Mark%40aaa-texas.com%7C343f2a1ca2e946e91dd008da3e41120f%7Cd5f618ff295149048f7e999c2dd97ab2%7C0%7C0%7C637890746614106925%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=Ri6qk0FquenWot%2B7NtNwp4PQXBlpbgSzxcwFsX8E0UQ%3Dreserved=0

Regards, Bob

Robert S. Hansel35 years of RACF Experience
Lead RACF Specialist
RSH Consulting, Inc.
617-969-8211
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fin%2Froberthanseldata=05%7C01%7CSteely.Mark%40aaa-texas.com%7C343f2a1ca2e946e91dd008da3e41120f%7Cd5f618ff295149048f7e999c2dd97ab2%7C0%7C0%7C637890746614106925%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=2p%2FVhwtS2wmMiwR5fCqnKzxRS25XLKssIwHQysYGDRo%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.twitter.com%2FRSH_RACFdata=05%7C01%7CSteely.Mark%40aaa-texas.com%7C343f2a1ca2e946e91dd008da3e41120f%7Cd5f618ff295149048f7e999c2dd97ab2%7C0%7C0%7C637890746614106925%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=qHDXl9r%2Byff2po89gcCtFs3DsZD%2B5%2Bwv3OSmmgnsek0%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rshconsulting.com%2Fdata=05%7C01%7CSteely.Mark%40aaa-texas.com%7C343f2a1ca2e946e91dd008da3e41120f%7Cd5f618ff295149048f7e999c2dd97ab2%7C0%7C0%7C637890746614106925%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=ZyxHROF4eUWuXPXBbIR8Rls0H8o6qizNf9Ve6E7RWuA%3Dr

FW: SDSF & TSS (RACF)

2022-05-25 Thread Robert S. Hansel (RSH)
Mark,

I'm surprised it didn't work. Did you code a CUSTOM(proplist) parameter in 
_all_ your GROUP statements that points to the PROPLIST NAME(proplist) 
statement with the PROPERTY parameter? And did you refresh the ISFPARMS in all 
the SDSF servers?

Regards, Bob

Robert S. Hansel35 years of RACF Experience
Lead RACF Specialist
RSH Consulting, Inc.
617-969-8211
www.linkedin.com/in/roberthansel
www.twitter.com/RSH_RACF
www.rshconsulting.com

-Original Message-
Date:Tue, 24 May 2022 15:02:50 +
From:"Steely.Mark" 
Subject: Re: SDSF & TSS (RACF)

Thanks for the link for the output violations - it doesn't appear to work for 
TSS (Top Secret). 


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Robert S. Hansel (RSH)
Sent: Tuesday, May 24, 2022 8:16 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SDSF & TSS (RACF)

ATTENTION: This e-mail came from an external source. Do not open attachments or 
click on links from unknown or unexpected emails.


Hi Mark,

When a user attempts to select a job, SDSF does an authorization check for each 
individual SYSOUT DDNAME associated with the job and can generate multiple 
violations like this.

To address this issue, see article " Avoiding Output Browse Violation Messages 
in SDSF" in the July 2008 issue of our RACF Tips newsletter.

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rshconsulting.com%2Fracftips%2FRSH_Consulting__RACF_Tips__July_2008.pdfdata=05%7C01%7CSteely.Mark%40aaa-texas.com%7C09fc8b5679ff48b440c108da3d87b17c%7Cd5f618ff295149048f7e999c2dd97ab2%7C0%7C0%7C637889950261872224%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=ReJ7GWolmeh4hc2MkFDbyahA0i5EVDrdN7qsfXgAKW4%3Dreserved=0

Regards, Bob

Robert S. Hansel35 years of RACF Experience
Lead RACF Specialist
RSH Consulting, Inc.
617-969-8211
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fin%2Froberthanseldata=05%7C01%7CSteely.Mark%40aaa-texas.com%7C09fc8b5679ff48b440c108da3d87b17c%7Cd5f618ff295149048f7e999c2dd97ab2%7C0%7C0%7C637889950261872224%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=U7odhzAml3JLOoHEPMB0H%2BugsJ0Rls0Z%2Fpk8Ht9KnPc%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.twitter.com%2FRSH_RACFdata=05%7C01%7CSteely.Mark%40aaa-texas.com%7C09fc8b5679ff48b440c108da3d87b17c%7Cd5f618ff295149048f7e999c2dd97ab2%7C0%7C0%7C637889950261872224%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=E8kbU8IAtv56Y%2BoiaQn%2BRuFS0IfJ6YswSdVy12zWCUo%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rshconsulting.com%2Fdata=05%7C01%7CSteely.Mark%40aaa-texas.com%7C09fc8b5679ff48b440c108da3d87b17c%7Cd5f618ff295149048f7e999c2dd97ab2%7C0%7C0%7C637889950261872224%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=%2BF%2BtoZaedniGmSARZrgDspVsvtLk624fxaEllI4har0%3Dreserved=0

-Original Message-
Date:Mon, 23 May 2022 20:55:48 +
From:"Steely.Mark" 
Subject: SDSF & TSS (RACF)

I am trying to convert our SDSF from using ISFPARMS to TSS for security.

I need some direction on how to provide security for reports.

Currently I am trying to use JESSPOOL to control access.
The customer is allowed to view all currently active and held output jobs but 
may only look at certain JOBS & REPORTS.

During testing I have this occurring:

The customer is trying to view this job (which the customer is not authorized)

COMMAND INPUT ===>
PREFIX=*  DEST=(ALL)  OWNER=*  SYSNAME=
NP   DDNAME   StepName ProcStep DSID OwnerC Dest
 JESMSGLG JES2 2 TS0242   R LOCAL
 JESJCL   JES2 3 TS0242   R LOCAL
 JESYSMSG JES2 4 TS0242   R LOCAL

The above is displayed when I put a ? in the Held output screen.
This is just to show you the report has 3 different reports.

Then the customer goes back to the screen which shows the job name:

SDSF HELD OUTPUT DISPLAY ALL CLASSES LINES 55  LINE 1
COMMAND INPUT ===>
PREFIX=B1*  DEST=(ALL)  OWNER=*  SORT=JOBNAME/A  SYSNAME=
NP   JOBNAME  JobIDOwnerPrty C ODisp Dest
 B100042B JOB09087 TS0242144 R HOLD  LOCAL


Then select the job and receives the following messages:

TSS7257E Unauthorized Access Level for JESSPOOL 

TSS7257E Unauthorized Access Level for JESSPOOL 

TSS7257E Unauthorized Access Level for JESSPOOL 

TSS7141E Use of Accessor ID Suspended
TSS7191E Job/Session Cancelled - Excessive Violations TSS7192E Session Locked - 
Excessive Violations: Signoff
CS0042 LOGGED OFF TSO AT 14:57:54 ON MAY 23, 2022 IKJ56453I SESSION CANCELLED
**

I would hate to think someone would accidently try to look at

Re: SDSF & TSS (RACF)

2022-05-24 Thread Larre Shiller
Mark -

We use Top Secret as well and had the same issue that you are describing when 
we initially activated JESSPOOL control.  We happen to be using (E)JES instead 
of SDSF, but essentially we did the same thing that Robert described here--we 
use an (E)JES exit to alter the RACF call for JESSPOOL and set LOG=NOFAIL (as 
well as MSGSUPP=YES).  It does exactly what is necessary to make this function 
as you wish.  Obviously, I cannot comment on why the change that you made to 
SDSF did not appear to work, but if you can get SDSF to set LOG=NOFAIL for the 
security calls, Top Secret should "honor" that.  If you can't get it to work, 
perhaps you could open a Case with Broadcom and trace the security call to 
figure out what's going on.

Larre Shiller
US Social Security Administration
"The opinions expressed in this e-mail are mine personally and do not 
necessarily reflect the opinion of the US Social Security Administration or the 
US Government.”

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: SDSF & TSS (RACF)

2022-05-24 Thread Jeremy Nicoll
On Mon, 23 May 2022, at 21:55, Steely.Mark wrote:

> Then select the job and receives the following messages:
>
> TSS7257E Unauthorized Access Level for JESSPOOL 
> 

> TSS7257E Unauthorized Access Level for JESSPOOL 
> 

> TSS7257E Unauthorized Access Level for JESSPOOL 
> 

Leaving aside the other issue, why is only the first four characters of the 
syslog ddname being checked?  Surely you're going to need to look at 
whole ddnames?

Or, is the TSS7257E message assuming that the value between the < & >
is a max-length 44 chars dsname when perhaps it needs to be a resource
name (or whatever TSS calls values that can be lots longer than that)?

-- 
Jeremy Nicoll - my opinions are my own.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: SDSF & TSS (RACF)

2022-05-24 Thread Steely.Mark
Thanks for the link for the output violations - it doesn't appear to work for 
TSS (Top Secret). 


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Robert S. Hansel (RSH)
Sent: Tuesday, May 24, 2022 8:16 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SDSF & TSS (RACF)

ATTENTION: This e-mail came from an external source. Do not open attachments or 
click on links from unknown or unexpected emails.


Hi Mark,

When a user attempts to select a job, SDSF does an authorization check for each 
individual SYSOUT DDNAME associated with the job and can generate multiple 
violations like this.

To address this issue, see article " Avoiding Output Browse Violation Messages 
in SDSF" in the July 2008 issue of our RACF Tips newsletter.

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rshconsulting.com%2Fracftips%2FRSH_Consulting__RACF_Tips__July_2008.pdfdata=05%7C01%7CSteely.Mark%40aaa-texas.com%7C09fc8b5679ff48b440c108da3d87b17c%7Cd5f618ff295149048f7e999c2dd97ab2%7C0%7C0%7C637889950261872224%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=ReJ7GWolmeh4hc2MkFDbyahA0i5EVDrdN7qsfXgAKW4%3Dreserved=0

Regards, Bob

Robert S. Hansel35 years of RACF Experience
Lead RACF Specialist
RSH Consulting, Inc.
617-969-8211
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fin%2Froberthanseldata=05%7C01%7CSteely.Mark%40aaa-texas.com%7C09fc8b5679ff48b440c108da3d87b17c%7Cd5f618ff295149048f7e999c2dd97ab2%7C0%7C0%7C637889950261872224%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=U7odhzAml3JLOoHEPMB0H%2BugsJ0Rls0Z%2Fpk8Ht9KnPc%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.twitter.com%2FRSH_RACFdata=05%7C01%7CSteely.Mark%40aaa-texas.com%7C09fc8b5679ff48b440c108da3d87b17c%7Cd5f618ff295149048f7e999c2dd97ab2%7C0%7C0%7C637889950261872224%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=E8kbU8IAtv56Y%2BoiaQn%2BRuFS0IfJ6YswSdVy12zWCUo%3Dreserved=0
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rshconsulting.com%2Fdata=05%7C01%7CSteely.Mark%40aaa-texas.com%7C09fc8b5679ff48b440c108da3d87b17c%7Cd5f618ff295149048f7e999c2dd97ab2%7C0%7C0%7C637889950261872224%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=%2BF%2BtoZaedniGmSARZrgDspVsvtLk624fxaEllI4har0%3Dreserved=0

-Original Message-
Date:Mon, 23 May 2022 20:55:48 +
From:"Steely.Mark" 
Subject: SDSF & TSS (RACF)

I am trying to convert our SDSF from using ISFPARMS to TSS for security.

I need some direction on how to provide security for reports.

Currently I am trying to use JESSPOOL to control access.
The customer is allowed to view all currently active and held output jobs but 
may only look at certain JOBS & REPORTS.

During testing I have this occurring:

The customer is trying to view this job (which the customer is not authorized)

COMMAND INPUT ===>
PREFIX=*  DEST=(ALL)  OWNER=*  SYSNAME=
NP   DDNAME   StepName ProcStep DSID OwnerC Dest
 JESMSGLG JES2 2 TS0242   R LOCAL
 JESJCL   JES2 3 TS0242   R LOCAL
 JESYSMSG JES2 4 TS0242   R LOCAL

The above is displayed when I put a ? in the Held output screen.
This is just to show you the report has 3 different reports.

Then the customer goes back to the screen which shows the job name:

SDSF HELD OUTPUT DISPLAY ALL CLASSES LINES 55  LINE 1
COMMAND INPUT ===>
PREFIX=B1*  DEST=(ALL)  OWNER=*  SORT=JOBNAME/A  SYSNAME=
NP   JOBNAME  JobIDOwnerPrty C ODisp Dest
 B100042B JOB09087 TS0242144 R HOLD  LOCAL


Then select the job and receives the following messages:

TSS7257E Unauthorized Access Level for JESSPOOL 

TSS7257E Unauthorized Access Level for JESSPOOL 

TSS7257E Unauthorized Access Level for JESSPOOL 

TSS7141E Use of Accessor ID Suspended
TSS7191E Job/Session Cancelled - Excessive Violations TSS7192E Session Locked - 
Excessive Violations: Signoff
CS0042 LOGGED OFF TSO AT 14:57:54 ON MAY 23, 2022 IKJ56453I SESSION CANCELLED
**

I would hate to think someone would accidently try to look at an  output they 
are not authorized to view and get their ID suspended.

Maybe I am going at this all wrong.

Is there a different way I should be doing this?

Any help would be appreciated.

We are currently at z/OS v2.4.

Thank You

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: SDSF & TSS (RACF)

2022-05-24 Thread Rob Scott
I think it is noteworthy to state that activating and implementing the  
JESSPOOL class (and maybe also OPERCMDS) has implications beyond just SDSF.

The profiles for these classes will be checked for other software and 
user/public tools, for example output archiving and automated operations 
products.

The only security resources owned by SDSF are the profiles in the “SDSF” class.

There are some old Share presentations about JESSPOOL that may be useful :

Share session 2665 “JES2 RACF Calls, Control Points and Profiles” (2007)
Share session 19490 “Security in JES Best Practices” (2016)

There was also a presentation I gave to GSE earlier this year entitled “SDSF 
Security – How it works on z/OS 2.5 and what has changed” that describes the 
SAF-only approach we now use in SDSF (If anyone wants a copy of this 
presentation, please let me know).

There is also the new “SDSF Security Migration Guide” manual that we released 
to help with the SAF-only requirements for z/OS 2.5.

Rob Scott
Rocket Software

From: IBM Mainframe Discussion List  On Behalf Of 
Robert S. Hansel (RSH)
Sent: 24 May 2022 14:16
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SDSF & TSS (RACF)

EXTERNAL EMAIL



Hi Mark,

When a user attempts to select a job, SDSF does an authorization check for each 
individual SYSOUT DDNAME associated with the job and can generate multiple 
violations like this.

To address this issue, see article " Avoiding Output Browse Violation Messages 
in SDSF" in the July 2008 issue of our RACF Tips newsletter.

https://www.rshconsulting.com/racftips/RSH_Consulting__RACF_Tips__July_2008.pdf<https://www.rshconsulting.com/racftips/RSH_Consulting__RACF_Tips__July_2008.pdf>

Regards, Bob

Robert S. Hansel 35 years of RACF Experience
Lead RACF Specialist
RSH Consulting, Inc.
617-969-8211
www.linkedin.com/in/roberthansel<http://www.linkedin.com/in/roberthansel>
www.twitter.com/RSH_RACF<http://www.twitter.com/RSH_RACF>
www.rshconsulting.com<http://www.rshconsulting.com>

-Original Message-
Date: Mon, 23 May 2022 20:55:48 +
From: "Steely.Mark" 
mailto:steely.m...@aaa-texas.com>>
Subject: SDSF & TSS (RACF)

I am trying to convert our SDSF from using ISFPARMS to TSS for security.

I need some direction on how to provide security for reports.

Currently I am trying to use JESSPOOL to control access.
The customer is allowed to view all currently active and held output jobs but 
may only look at certain JOBS & REPORTS.

During testing I have this occurring:

The customer is trying to view this job (which the customer is not authorized)

COMMAND INPUT ===>
PREFIX=* DEST=(ALL) OWNER=* SYSNAME=
NP DDNAME StepName ProcStep DSID Owner C Dest
JESMSGLG JES2 2 TS0242 R LOCAL
JESJCL JES2 3 TS0242 R LOCAL
JESYSMSG JES2 4 TS0242 R LOCAL

The above is displayed when I put a ? in the Held output screen.
This is just to show you the report has 3 different reports.

Then the customer goes back to the screen which shows the job name:

SDSF HELD OUTPUT DISPLAY ALL CLASSES LINES 55 LINE 1
COMMAND INPUT ===>
PREFIX=B1* DEST=(ALL) OWNER=* SORT=JOBNAME/A SYSNAME=
NP JOBNAME JobID Owner Prty C ODisp Dest
B100042B JOB09087 TS0242 144 R HOLD LOCAL


Then select the job and receives the following messages:

TSS7257E Unauthorized Access Level for JESSPOOL 

TSS7257E Unauthorized Access Level for JESSPOOL 

TSS7257E Unauthorized Access Level for JESSPOOL 

TSS7141E Use of Accessor ID Suspended
TSS7191E Job/Session Cancelled - Excessive Violations
TSS7192E Session Locked - Excessive Violations: Signoff
CS0042 LOGGED OFF TSO AT 14:57:54 ON MAY 23, 2022
IKJ56453I SESSION CANCELLED
**

I would hate to think someone would accidently try to look at an output they 
are not authorized to view and get their ID suspended.

Maybe I am going at this all wrong.

Is there a different way I should be doing this?

Any help would be appreciated.

We are currently at z/OS v2.4.

Thank You

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu<mailto:lists...@listserv.ua.edu> with 
the message: INFO IBM-MAIN


Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ 
Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support: 
https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - 
http://www.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy


This communication and any attachments may contain confidential information of 
Rocket Software, Inc. All unauthorized use, disclosure or distribution is 
prohibited. If you are not the intended recipient, please notify Rocket 
So

Re: SDSF & TSS (RACF)

2022-05-24 Thread Robert S. Hansel (RSH)
Hi Mark,

When a user attempts to select a job, SDSF does an authorization check for each 
individual SYSOUT DDNAME associated with the job and can generate multiple 
violations like this.

To address this issue, see article " Avoiding Output Browse Violation Messages 
in SDSF" in the July 2008 issue of our RACF Tips newsletter.

https://www.rshconsulting.com/racftips/RSH_Consulting__RACF_Tips__July_2008.pdf

Regards, Bob

Robert S. Hansel35 years of RACF Experience
Lead RACF Specialist
RSH Consulting, Inc.
617-969-8211
www.linkedin.com/in/roberthansel
www.twitter.com/RSH_RACF
www.rshconsulting.com

-Original Message-
Date:Mon, 23 May 2022 20:55:48 +
From:"Steely.Mark" 
Subject: SDSF & TSS (RACF)

I am trying to convert our SDSF from using ISFPARMS to TSS for security.

I need some direction on how to provide security for reports.

Currently I am trying to use JESSPOOL to control access.
The customer is allowed to view all currently active and held output jobs but 
may only look at certain JOBS & REPORTS.

During testing I have this occurring:

The customer is trying to view this job (which the customer is not authorized)

COMMAND INPUT ===>
PREFIX=*  DEST=(ALL)  OWNER=*  SYSNAME=
NP   DDNAME   StepName ProcStep DSID OwnerC Dest
 JESMSGLG JES2 2 TS0242   R LOCAL
 JESJCL   JES2 3 TS0242   R LOCAL
 JESYSMSG JES2 4 TS0242   R LOCAL

The above is displayed when I put a ? in the Held output screen.
This is just to show you the report has 3 different reports.

Then the customer goes back to the screen which shows the job name:

SDSF HELD OUTPUT DISPLAY ALL CLASSES LINES 55  LINE 1
COMMAND INPUT ===>
PREFIX=B1*  DEST=(ALL)  OWNER=*  SORT=JOBNAME/A  SYSNAME=
NP   JOBNAME  JobIDOwnerPrty C ODisp Dest
 B100042B JOB09087 TS0242144 R HOLD  LOCAL


Then select the job and receives the following messages:

TSS7257E Unauthorized Access Level for JESSPOOL 

TSS7257E Unauthorized Access Level for JESSPOOL 

TSS7257E Unauthorized Access Level for JESSPOOL 

TSS7141E Use of Accessor ID Suspended
TSS7191E Job/Session Cancelled - Excessive Violations
TSS7192E Session Locked - Excessive Violations: Signoff
CS0042 LOGGED OFF TSO AT 14:57:54 ON MAY 23, 2022
IKJ56453I SESSION CANCELLED
**

I would hate to think someone would accidently try to look at an  output they 
are not authorized to view and get their ID suspended.

Maybe I am going at this all wrong.

Is there a different way I should be doing this?

Any help would be appreciated.

We are currently at z/OS v2.4.

Thank You

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


SDSF & TSS (RACF)

2022-05-23 Thread Steely.Mark
I am trying to convert our SDSF from using ISFPARMS to TSS for security.

I need some direction on how to provide security for reports.

Currently I am trying to use JESSPOOL to control access.
The customer is allowed to view all currently active and held output jobs but 
may only look at certain JOBS & REPORTS.

During testing I have this occurring:

The customer is trying to view this job (which the customer is not authorized)

COMMAND INPUT ===>
PREFIX=*  DEST=(ALL)  OWNER=*  SYSNAME=
NP   DDNAME   StepName ProcStep DSID OwnerC Dest
 JESMSGLG JES2 2 TS0242   R LOCAL
 JESJCL   JES2 3 TS0242   R LOCAL
 JESYSMSG JES2 4 TS0242   R LOCAL

The above is displayed when I put a ? in the Held output screen.
This is just to show you the report has 3 different reports.

Then the customer goes back to the screen which shows the job name:

SDSF HELD OUTPUT DISPLAY ALL CLASSES LINES 55  LINE 1
COMMAND INPUT ===>
PREFIX=B1*  DEST=(ALL)  OWNER=*  SORT=JOBNAME/A  SYSNAME=
NP   JOBNAME  JobIDOwnerPrty C ODisp Dest
 B100042B JOB09087 TS0242144 R HOLD  LOCAL


Then select the job and receives the following messages:

TSS7257E Unauthorized Access Level for JESSPOOL 

TSS7257E Unauthorized Access Level for JESSPOOL 

TSS7257E Unauthorized Access Level for JESSPOOL 

TSS7141E Use of Accessor ID Suspended
TSS7191E Job/Session Cancelled - Excessive Violations
TSS7192E Session Locked - Excessive Violations: Signoff
CS0042 LOGGED OFF TSO AT 14:57:54 ON MAY 23, 2022
IKJ56453I SESSION CANCELLED
**

I would hate to think someone would accidently try to look at an  output they 
are not authorized to view and get their ID suspended.

Maybe I am going at this all wrong.

Is there a different way I should be doing this?

Any help would be appreciated.

We are currently at z/OS v2.4.

Thank You






--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN