Re: Bad backup stories (was: Re: Ransomware in VSAM and DB2)

2023-03-11 Thread David Spiegel
Hi Phil, Since you asked for bad backup stories ... In the mid '80s, I was working at the Canadian head office of a multinational food company. We were using 6250 BPI Tapes on STK 4520 drives. My boss, who also managed operations, decided that when tapes would get physical errors, the operator

Re: Bad backup stories (was: Re: Ransomware in VSAM and DB2)

2023-03-11 Thread Bob Bridges
Anything I write for a client, I take a backup home, even though some HR folks may consider that a violation of confidentiality or copyright or something so I don't ever do it and I never said I did and anyway you can't prove nuthin'. But if it gets destroyed at work, let me know; I have a very

Bad backup stories (was: Re: Ransomware in VSAM and DB2)

2023-03-11 Thread Phil Smith III
Since we're swapping bad backup stories. I'm at a small mainframe vendor, mid-90s. Data center manager quits with no notice because boy genius sociopath CFO tell him at the last minute that he can't take long-planned, prepaid vacation trip because CFO wants him there for something stupid. This

Re: Ransomware in VSAM and DB2

2023-03-11 Thread Laurence Chiu
A client I am working with uses Safeguarded Copy, a feature in IBM Copy Services Manager on the DS8K SANS On Fri, Mar 10, 2023, 12:44 PM Attila Fogarasi wrote: > Also there are various solutions for immutable backups of z/OS data, which > would protect you against ransomware. > > On Fri, Mar 3,

Re: Ransomware in VSAM and DB2

2023-03-11 Thread Charles Mills
In the early 70's I had a client -- large insurance company -- that was running DOS on a 360/50. At some point they lost a 2314 volume. When they restored from backup the restored volume was unusable. Investigation revealed that for some reason lost in the fog of time the sysprog who had set up

Re: Automatic assignment of Unix Identities.

2023-03-11 Thread Paul Gilmartin
On Sat, 11 Mar 2023 18:08:56 +, Colin Paice wrote: > >During my tests, I had a userid without an OMVS segment - and could get the >right return code. >If I then logon the userid, I get an OMVS segment allocated because my >system is set up for this. > >Is there any way of saying do *not

Re: Automatic assignment of Unix Identities.

2023-03-11 Thread Michael Babcock
If you want to prevent certain users from being able to access z/OS UNIX services, define an OMVS segment with no UID for those users. This prevents their user IDs from being automatically assigned a UID. When they attempt to use a z/OS UNIX service, the dub will fail, and a daemon will be unable

Automatic assignment of Unix Identities.

2023-03-11 Thread Colin Paice
I'm looking into pthread_security_np to change my userid to become another id. During my tests, I had a userid without an OMVS segment - and could get the right return code. If I then logon the userid, I get an OMVS segment allocated because my system is set up for this. Is there any way of

Re: Ransomware in VSAM and DB2

2023-03-11 Thread Tom Brennan
There was a magazine article maybe in the 90's that appeared to be a news report about a company that went through something like you described - systems down, won't IPL, backup disks corrupted, backup tapes deleted or corrupted, even documentation gone I think. Then about the 3rd paragraph

Re: CS/CDS instruction

2023-03-11 Thread Paul Gilmartin
On Sat, 11 Mar 2023 00:03:06 -0800, Leonard D Woren wrote: >If some particular instruction set feature is installed, the >definition of ASI/AGSI is enhanced to serialize the update, making it >a simpler solution than a CDS loop or PLO. > >In some performance testing a while back on a z14 or z15

Re: CS/CDS instruction

2023-03-11 Thread Leonard D Woren
If some particular instruction set feature is installed, the definition of ASI/AGSI is enhanced to serialize the update, making it a simpler solution than a CDS loop or PLO. In some performance testing a while back on a z14 or z15 which I think had the above serialization feature, the