I am not an expert here, but you may want to try a boot-time recovery environment like ZZSA, NewEra SAE, or just the VM installation media.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Karl Severson Sent: Sunday, July 24, 2022 7:51 PM To: [email protected] Subject: Locked out of my account and therefore my System ​Embarrassed to report that I locked myself out of my system. System is running VM/ESA 2.3 with VM:Manager 2.6 and running the Rules Facility. Broadcom is no help as we don't have maintenance on a product that has reached end of life as Broadcom won't support it because of that. What I have tried: I thought I set up VM:Operator to be able to link nopass to VM:Secure 1b0 but for some reason that doesn't work. I also can't link to VMXSYSAD 191, where we stash a nightly backup of the directory. I've tried the LINK command and the system wants a READ password and that doesn't work as I don't know what it is.I think someone undid things that I set up before I retired, because I knew I would be back. Link attempt to VMX 1b0 fails because of some RULE. We use logonby so we only have to know OUR own account password but I've managed to lock myself out of my account so no dice in anything I try. What is left? There are a few privileged accounts left that I might try (OP1) for instance, but if someone changed its password to something other than OP1, my plan will fail. Any ideas are most welcome! TIA Karl Severson RTX ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
