Re: Masking SMF data internally

2024-01-23 Thread Martin Packer
arc-requ...@listserv.ua.edu> Date: Tuesday, 23 January 2024 at 09:45 To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: Masking SMF data internally You talk about fields. However user see records, not fields. Various records. Manual editing single records with known fields is easy, however mass

Re: Masking SMF data internally

2024-01-23 Thread Itschak Mugzach
At the end, you mask specific fields (which are defined in records). The method I offered is generic. The data for this logic is unstructured, and the translation purpose is to identify possible texts and numbers the user might wish to hide. A loop of TRANSLATE, VERIFY and OVERLAY does need

Re: Masking SMF data internally

2024-01-23 Thread Radoslaw Skorupka
You talk about fields. However user see records, not fields. Various records. Manual editing single records with known fields is easy, however mass change can be risky. Note: as usually *we don't know* what is the author's need. IMHO this is the least active person in this thread. Without that

Re: Masking SMF data internally

2024-01-22 Thread Jon Perryman
>You can mask any character or external decimal field by using translate As an alternative, you should run those programs on your systems and provide them with the reports that you review for sensitive information. . -- For

Re: Masking SMF data internally

2024-01-22 Thread ITschak Mugzach
You can mask any character or external decimal field by using translate everything but a-z and 0 to 9 and check for minimum length (say, not less than three characters) in order not to convert hex data. Now find the positions and mask the original record. This way you do not care for the actual

Re: Masking SMF data internally

2024-01-22 Thread Radoslaw Skorupka
W dniu 22.01.2024 o 16:49, Willy Jensen pisze: Most SMF records can be copied to a normal VB dataset. As I recall, only one or two CICS records were really that big (or perhaps it is DB2, it's been a while)? Anyway, you can select the record types that you need and the use SORT to convert to

Re: Masking SMF data internally

2024-01-22 Thread Willy Jensen
Most SMF records can be copied to a normal VB dataset. As I recall, only one or two CICS records were really that big (or perhaps it is DB2, it's been a while)? Anyway, you can select the record types that you need and the use SORT to convert to normal VB.

Re: Masking SMF data internally

2024-01-22 Thread Allan Staller
Classification: Confidential Use Fiale-Aid or File Manager if you have them available. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Jake Anderson Sent: Sunday, January 21, 2024 12:43 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Masking SMF data internally

Re: Masking SMF data internally

2024-01-22 Thread Scott Chapman
On Sun, 21 Jan 2024 07:38:44 -0600, Paul Feller wrote: >Jake, I agree you need to identify what record types are needed for the >sizing operation. After you know which record types (and subtypes) you may >not need to do anything. As an example, I can't think of any sensitive data >that might

Re: Masking SMF data internally

2024-01-21 Thread Michael Oujesky
REVIEW (CBT134) can at least browse SMF VBS files. Michael At 12:43 AM 1/21/2024, Jake Anderson wrote: I am not even able to browse It says 'Invalid record length'. I tried setting the block size and LRECL but by default it takes as Record length': 32767 Block size : 32760 On Sun, Jan 21,

Re: Masking SMF data internally

2024-01-21 Thread Paul Feller
- From: IBM Mainframe Discussion List On Behalf Of Binyamin Dissen Sent: Sunday, January 21, 2024 1:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Masking SMF data internally On Sun, 21 Jan 2024 09:58:29 +0400 Jake Anderson wrote: :>We have a requirement of sharing our SMF data to ven

Re: Masking SMF data internally

2024-01-20 Thread Binyamin Dissen
On Sun, 21 Jan 2024 09:58:29 +0400 Jake Anderson wrote: :>We have a requirement of sharing our SMF data to vendor for a sizing :>operation of our hardware connected to our mainframe :>Our organization has a policy of masking the critical values before sharing :>it. I see SMF datasets are are

Re: Masking SMF data internally

2024-01-20 Thread ITschak Mugzach
It is a span record format probably. Rexx can read it, it you need to be more careful by identifying text fields. I have done that with dump masking. Maybe I still have the code *| **Itschak Mugzach | Director | SecuriTeam Software **|** IronSphere Platform* *|* *Information Security Continuous

Re: Masking SMF data internally

2024-01-20 Thread Paul Gilmartin
On Sun, 21 Jan 2024 09:58:29 +0400, Jake Anderson wrote: >Hello > >We have a requirement of sharing our SMF data to vendor for a sizing >operation of our hardware connected to our mainframe > > >Our organization has a policy of masking the critical values before sharing >it. I see SMF datasets

Re: Masking SMF data internally

2024-01-20 Thread Jake Anderson
I am not even able to browse It says 'Invalid record length'. I tried setting the block size and LRECL but by default it takes as Record length': 32767 Block size : 32760 On Sun, Jan 21, 2024, 10:26 AM ITschak Mugzach wrote: > Are these files machine or human readable? As you can edit them, I

Re: Masking SMF data internally

2024-01-20 Thread ITschak Mugzach
Are these files machine or human readable? As you can edit them, I believe they are human readable and no Hex data inside. If so, write a rexx to translate everything a-z to blanks and write back. ITschak *| **Itschak Mugzach | Director | SecuriTeam Software **|** IronSphere Platform* *|*

Masking SMF data internally

2024-01-20 Thread Jake Anderson
Hello We have a requirement of sharing our SMF data to vendor for a sizing operation of our hardware connected to our mainframe Our organization has a policy of masking the critical values before sharing it. I see SMF datasets are are editable from ISPF. Is there a way or someone has undergone