AFAIK TCAM and the 3850 were defunct by the time OPERCMDS came along. The last I heard, MSS staging drives had to be either 3330 or 3350 in compatibility mode and TCAM didn't support Y2K.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Radoslaw Skorupka <[email protected]> Sent: Tuesday, December 19, 2023 3:31 PM To: [email protected] Subject: Re: Z/OS Survey - Unusuall system commands Unusal commands? Well, it is enough to open both MVS System Commands and JES2 Commands manuals. OBEY is not exactly the system command, however it is widely used. My favourite is QUIESCE. There are also other commands which I (almost) never use, but I understand their purpose. JES2 world is more complex - there are many commands which I vaguely understand the purpose. And many which I consider really obsolete. Fun fact: recently I've been cleaning some z/OS installation, RACF definitions. I've found approx. 400 OPERCMDS profiles. Some of them were really, really obsolete - like MSS related command, TCAM commands, etc. What's funny, even not-so-current documentation does not mention such commands or profiles, but at least few of them are still present in the system code. Explanation: MSS - Mass Storage Subsystem. Very interesting tape-disc device, but withdrawn in early 80's. TCAM - VTAM predecessor. I have no idea how old it is. I'm pretty sure the OPERCMDS profiles were created for an installation with neither MSS nor TCAM. -- Radoslaw Skorupka Lodz, Poland W dniu 19.12.2023 o 09:12, ITschak Mugzach pisze: > There are some MVS commands that are hard to understand how and why they > were created. What bothers me is the fact that the input of the commands > that modify MVS behavior allows input from private dataset. These are the > first commands I am trying when I do a pentest... > For example: > *SETLOAD* allows on-the-fly change of parmlib concatenation using a dataset > that is not part of the parmlib concatenation itself. for example: SETLOAD > 03,PARMLIB,DSN=sys4.relson > TCPCIP *OBEY* command allows specification of TCPIP configuration from a > private library. > > How frequent do you use these commands (if ever) and how do you identify > the use (assuming that the commands are protected by your ESM). I wonder > why IBM allows such a scenario. > > ITschak ---------------------------------------------------------------------- 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
