Interface to Perf Toolkit from inside a z/Linux machine
Has anyone developed any code, code fragment, technique, etc to extract information out of the Performance Toolkit from an application written in some shell script or otherwise? George Shedlock Jr AEGON Information Technology AEGON USA 502-560-3541
Changing privclass of SHUTDOWN
I want to change the SHUTDOWN command privclass to Z and Z only. Here are my commands followed by the responses. cp query cpcmd shutdown Command: SHUTDOWN Status:EnabledNot Silent IBM Class: A PrivClasses: A CMDBK Address: 00A50140 Entry Point: HCPSHUTD Ready; T=0.01/0.01 10:44:12 cp modify command shutdown ibmclass * privclass z Ready; T=0.01/0.01 10:44:20 cp query cpcmd shutdown Command: SHUTDOWN Status:EnabledNot Silent IBM Class: A PrivClasses: Z CMDBK Address: 00A50140 Entry Point: HCPSHUTD Command: Status:EnabledNot Silent IBM Class: A PrivClasses: A CMDBK Address: 1AD767F0 Entry Point: HCPSHUTD Ready; T=0.01/0.01 10:44:24 Will users with CLASS A still be able to issue the SHUTDOWN command?? The second half of the QUERY CPCMD SHUTDOWN shows IBM CLASS A and Privclasses A. I must confess I am confused with the responses to the QUERY CPCMD SHUTDOWN command. Thanks. Jim Hughes 603-271-5586 There's no sense in being precise when you don't even know what you're talking about. John von Neumann
Re: Changing privclass of SHUTDOWN
An easy way: test it... Or, less dangerous: SET PRIVCLASS * =A Q COMMAND SHUTDOWN SET PRIVCLASS * RESET It should tell: SHUTDOWN IBMCLASS=NONE 2007/11/6, Hughes, Jim [EMAIL PROTECTED]: I want to change the SHUTDOWN command privclass to Z and Z only. Here are my commands followed by the responses. cp query cpcmd shutdown Command: SHUTDOWN Status:EnabledNot Silent IBM Class: A PrivClasses: A CMDBK Address: 00A50140 Entry Point: HCPSHUTD Ready; T=0.01/0.01 10:44:12 cp modify command shutdown ibmclass * privclass z Ready; T=0.01/0.01 10:44:20 cp query cpcmd shutdown Command: SHUTDOWN Status:EnabledNot Silent IBM Class: A PrivClasses: Z CMDBK Address: 00A50140 Entry Point: HCPSHUTD Command: Status:EnabledNot Silent IBM Class: A PrivClasses: A CMDBK Address: 1AD767F0 Entry Point: HCPSHUTD Ready; T=0.01/0.01 10:44:24 Will users with CLASS A still be able to issue the SHUTDOWN command?? The second half of the QUERY CPCMD SHUTDOWN shows IBM CLASS A and Privclasses A. I must confess I am confused with the responses to the QUERY CPCMD SHUTDOWN command. Thanks. Jim Hughes 603-271-5586 There's no sense in being precise when you don't even know what you're talking about. John von Neumann -- Kris Buelens, IBM Belgium, VM customer support
Changing privclass of SHUTDOWN
No. The -- in the response means that version of the command (IBM Class A, PrivClasses A) is not active. The output shows that only a user with PrivClass Z can issue SHUTDOWN. John Franciscovich z/VM Development I want to change the SHUTDOWN command privclass to Z and Z only. Here are my commands followed by the responses. cp query cpcmd shutdown Command: SHUTDOWN Status:EnabledNot Silent IBM Class: A PrivClasses: A CMDBK Address: 00A50140 Entry Point: HCPSHUTD Ready; T=3D0.01/0.01 10:44:12 cp modify command shutdown ibmclass * privclass z Ready; T=3D0.01/0.01 10:44:20 cp query cpcmd shutdown Command: SHUTDOWN Status:EnabledNot Silent IBM Class: A PrivClasses: Z CMDBK Address: 00A50140 Entry Point: HCPSHUTD Command: Status:EnabledNot Silent IBM Class: A PrivClasses: A CMDBK Address: 1AD767F0 Entry Point: HCPSHUTD Ready; T=3D0.01/0.01 10:44:24 Will users with CLASS A still be able to issue the SHUTDOWN command?? The second half of the QUERY CPCMD SHUTDOWN shows IBM CLASS A and Privclasses A.=20 I must confess I am confused with the responses to the QUERY CPCMD SHUTDOWN command.
Re: Changing privclass of SHUTDOWN
John, Perfect. Long time, No see. At least until February at Disney. I get to attend Share again. Best regards, Jim Hughes 603-271-5586 There's no sense in being precise when you don't even know what you're talking about. John von Neumann =-Original Message- =From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On =Behalf Of John Franciscovich =Sent: Tuesday, November 06, 2007 11:10 AM =To: IBMVM@LISTSERV.UARK.EDU =Subject: Changing privclass of SHUTDOWN = =No. The -- in the response means that version of the command =(IBM Class A, PrivClasses A) is not active. The output shows =that only a user with PrivClass Z can issue SHUTDOWN. = =John Franciscovich =z/VM Development
Re: Changing privclass of SHUTDOWN
You might want to put this change in SYSTEM CONFIG as well. What we use is: Modify Command Shutdown IBMclass A Privclasses Z Over the course of 30 years as a VM sysprog, every VM sysprog who I have worked with has shutdown a VM system *ONCE.* Me too :-[ Jim Hughes, Jim wrote: I want to change the SHUTDOWN command privclass to Z and Z only. Here are my commands followed by the responses. cp query cpcmd shutdown Command: SHUTDOWN Status:EnabledNot Silent IBM Class: A PrivClasses: A CMDBK Address: 00A50140 Entry Point: HCPSHUTD Ready; T=3D0.01/0.01 10:44:12 cp modify command shutdown ibmclass * privclass z Ready; T=3D0.01/0.01 10:44:20 cp query cpcmd shutdown Command: SHUTDOWN Status:EnabledNot Silent IBM Class: A PrivClasses: Z CMDBK Address: 00A50140 Entry Point: HCPSHUTD Command: Status:EnabledNot Silent IBM Class: A PrivClasses: A CMDBK Address: 1AD767F0 Entry Point: HCPSHUTD Ready; T=3D0.01/0.01 10:44:24 Will users with CLASS A still be able to issue the SHUTDOWN command?? The second half of the QUERY CPCMD SHUTDOWN shows IBM CLASS A and Privclasses A.=20 I must confess I am confused with the responses to the QUERY CPCMD SHUTDOWN command. =20 Thanks. =20 Jim Hughes 603-271-5586 There's no sense in being precise when you don't even know what you're talking about. John von Neumann -- Jim Bohnsack Cornell University (607) 255-1760 [EMAIL PROTECTED]
Re: Interface to Perf Toolkit from inside a z/Linux machine
My linuxes aren't enabled to connect to perfkit, but if they were, I would think that the following command would work: vmcp vmcx perfsvm storage or mcp vmcx perfsvm user Mary Anne On Nov 6, 2007 10:16 AM, Shedlock, George [EMAIL PROTECTED] wrote: Has anyone developed any code, code fragment, technique, etc to extract information out of the Performance Toolkit from an application written in some shell script or otherwise? George Shedlock Jr AEGON Information Technology AEGON USA 502-560-3541
Re: Changing privclass of SHUTDOWN
2007/11/6, Jim Bohnsack [EMAIL PROTECTED]: You might want to put this change in SYSTEM CONFIG as well. What we use is: Modify Command Shutdown IBMclass A Privclasses Z Over the course of 30 years as a VM sysprog, every VM sysprog who I have worked with has shutdown a VM system *ONCE.* Me too :-[ Jim Every sysprog? No no, I never did. My worst outages happened in VM/SP where a SAVESYS of APL caused a VSE guest to abend. Impossible? That's what I told my customer and I SAVESYSed APL again... and VSE died again. So I had to admit I was the cause and started digging: the DMSSNT area for APL was in overlap with a CP PAGE area on VMPK01, mea culpa indeed. Nevertheless, we place SHUTDOWN in CLASS S. -- Kris Buelens, IBM Belgium, VM customer support
Re: Changing privclass of SHUTDOWN
On Tuesday, 11/06/2007 at 12:25 EST, Kris Buelens [EMAIL PROTECTED] wrote: Over the course of 30 years as a VM sysprog, every VM sysprog who I have worked with has shutdown a VM system *ONCE.* Me too :-[ Every sysprog? No, not *every* sysprog, just the ones Jim has worked with. Verry interesting. One might suspect (if one were of a suspicious mind) that Jim also has his Initiates issue the LOGO command, too, just for fun. So a word to the wise: If you find yourself working with Jim, watch your back! He's gonna try to get you to issue SHUTDOWN at the wrong place! -- Chuckie.
Re: Interface to Perf Toolkit from inside a z/Linux machine
Unfortunately VMCX is not a CP command. It is a CMS program that uses the VMCF protocol, SEND/RECEIVE subset, that is frowned upon, and it just isn 't linux-like either. To be linux-like you need to use TCP/IP and have a ser ver on VM interface between the your linux client and the PERFTK data. Or you could by a product that interfaces between PERFTK and linux to provide lo ts of MVS-style data. I would prefer to have a privleged linux command (VMCX) that did use the VMCF SEND/RECEIVE, and a daemon program to listen for SMSGs which are the uses of the SENDX subset of VMCF. IBM no longer ships the source for the VMCX module with PERFTK and I dele ted the RTM/SMART copy when I moved to PERFTK. /Tom Kern /301-903-2211 On Tue, 6 Nov 2007 11:26:59 -0500, Mary Anne Matyaz [EMAIL PROTECTED] om wrote: My linuxes aren't enabled to connect to perfkit, but if they were, I would think that the following command would work: vmcp vmcx perfsvm storage or mcp vmcx perfsvm user Mary Anne
Re: Changing privclass of SHUTDOWN
I have to admit that I accidently shutdown VM during one of our heaviest usage periods: academic registration. I was just learning about TCPIP and the SMTP server was not working properly so I logged onto SMTP and issued the SHUTDOWN command. BOOM! The sample directories for all of the TCPIP machines had priviledge class A. This was back at the 2.2 level. Needless to say that got fixed quickly and I learned how to change the priviledge class of CP SHUTDOWN. /Fran Hensler at Slippery Rock University of Pennsylvania USA for 44 years [EMAIL PROTECTED] +1.724.738.2153 Yes, Virginia, there is a Slippery Rock
Re: Changing privclass of SHUTDOWN
Kris never worked with me. Perhaps I'm a bad influence. For Fran--I think a major bad choice IBM made was to have SHUTDOWN be the end-stop-kill command for anything else other than VM. If I remember correctly, RSCS has a SHUTDOWN command. I haven't used PVM for 10 or 15 years, but I think it did or does. A PC that IBM made back in the '80s (PC3270??) used SHUTDOWN to stop it and park the hard disk. I've SHUTDOWN CP when I intended to kill RSCS. A fellow (lady) sysprog I worked with killed CP trying to stop the PC. Another bad choice that IBM made was to have COLD as an IPL option, at least back in the olden days, without having some kind of really big nastygram coming out on the screen saying ARE YOU REALLY SURE YOU WANT TO DO THIS. We took COLD out as an IPL choice and replaced it with a word that only the sysprogs knew. Jim Kris Buelens wrote: No no, I never did. My worst outages happened in VM/SP where a SAVESYS of APL caused a VSE guest to abend. Impossible? That's what I told my customer and I SAVESYSed APL again... and VSE died again. So I had to admit I was the cause and started digging: the DMSSNT area for APL was in overlap with a CP PAGE area on VMPK01, mea culpa indeed. Nevertheless, we place SHUTDOWN in CLASS S. -- Jim Bohnsack Cornell University (607) 255-1760 [EMAIL PROTECTED]
Re: Changing privclass of SHUTDOWN
I shutdown one on purpose once. During our initial testing of VM/370 Release 2, one of my colleagues thought it was funny to force my id from the system whenever I logged on. I managed to log on as OPERATOR and issue a shutdown while he was in the middle of something. We were the only ones on the system at the time, so it was not a disruption for others. Over the years, I have been able to accidentally cause the system to crash enough times that I have never needed to be able to issue SHUTDOWN from my own id :-) I have never given a 2nd-level system CLASS A, specifically because of the dangers inherent in doing so, and generally do not allow any id other than OPERATOR to have that privilege, not even MAINT. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Fran Hensler Sent: Tuesday, November 06, 2007 9:26 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Changing privclass of SHUTDOWN I have to admit that I accidently shutdown VM during one of our heaviest usage periods: academic registration. I was just learning about TCPIP and the SMTP server was not working properly so I logged onto SMTP and issued the SHUTDOWN command. BOOM! The sample directories for all of the TCPIP machines had priviledge class A. This was back at the 2.2 level. Needless to say that got fixed quickly and I learned how to change the priviledge class of CP SHUTDOWN. /Fran Hensler at Slippery Rock University of Pennsylvania USA for 44 years [EMAIL PROTECTED] +1.724.738.2153 Yes, Virginia, there is a Slippery Rock
Re: Changing privclass of SHUTDOWN
Be careful, Chuckie, or I'll look around and see if I can find the old XMAS greeting that caused a major disruption to IBM's VNET network about 25 years ago. Jim Alan Altmark wrote: No, not *every* sysprog, just the ones Jim has worked with. Verry interesting. One might suspect (if one were of a suspicious mind) that Jim also has his Initiates issue the LOGO command, too, just for fun. So a word to the wise: If you find yourself working with Jim, watch your back! He's gonna try to get you to issue SHUTDOWN at the wrong place! -- Chuckie. -- Jim Bohnsack Cornell University (607) 255-1760 [EMAIL PROTECTED]
Re: Changing privclass of SHUTDOWN
Thanks Chuckie. I work with Jim and already know I need to watch my back. Actually I've never done this. We did have a Systems Programmer In Training (Jim loves the acronym) some years back (and in Jim's defense I have to say this was before Jim joined us) who did it three times over the course of about a month. The head systems programmer at the time made her a button to wear with one word on it in black capital letters (SHUTDOWN), with a red circle around it and a red diagonal line through it. :-) Mark Bodenstein ([EMAIL PROTECTED]) Cornell University At 12:50 PM 11/6/2007, Alan Altmark wrote: On Tuesday, 11/06/2007 at 12:25 EST, Kris Buelens [EMAIL PROTECTED] wrote: Over the course of 30 years as a VM sysprog, every VM sysprog who I have worked with has shutdown a VM system *ONCE.* Me too :-[ Every sysprog? No, not *every* sysprog, just the ones Jim has worked with. Verry interesting. One might suspect (if one were of a suspicious mind) that Jim also has his Initiates issue the LOGO command, too, just for fun. So a word to the wise: If you find yourself working with Jim, watch your back! He's gonna try to get you to issue SHUTDOWN at the wrong place! -- Chuckie.
Re: Changing privclass of SHUTDOWN
I wholeheartedly agree about using SHUTDOWN for other than CP being a poor choice. Unfortunately, that has been the case for so long that it will be difficult to change it now. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Jim Bohnsack Sent: Tuesday, November 06, 2007 9:54 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Changing privclass of SHUTDOWN Kris never worked with me. Perhaps I'm a bad influence. For Fran--I think a major bad choice IBM made was to have SHUTDOWN be the end-stop-kill command for anything else other than VM. If I remember correctly, RSCS has a SHUTDOWN command
Re: Changing privclass of SHUTDOWN
On Tuesday, 11/06/2007 at 01:29 EST, Schuh, Richard [EMAIL PROTECTED] wrote: I wholeheartedly agree about using SHUTDOWN for other than CP being a poor choice. Unfortunately, that has been the case for so long that it will be difficult to change it now. And then there was the crowd who wanted the same command on all subsystems so as to make it simpler. Why does IBM invent a new command when we already have a perfectly good 'shutdown'? And, no, nothing is going to change at this point. Alan Altmark z/VM Development IBM Endicott
Re: Changing privclass of SHUTDOWN
Yes, PVM has a SHUTDOWN command. I know. Afterwards I changed PVM's command to SHUT. My other accident wouldn't have been prevented by something as easy as changing the privclass. We had recently migrated from a 4381 to a 3090 and I was learning how to work with the IOCDS's during the workday. So, with the manual at hand I set about learning how to do the basics. Unprotect the one I want to write to? No problem! Write a new one out? Done! Write protect it? Piece of cake! Activate it? Message says I can't until I release the active one. That makes sense, so let's release it. A message asks if I really want to do that. [I hope your spider senses are tingling.] Well, I can't activate a new one if I don't, so, yes. I hadn't realized that releasing/activating an IOCDS was essentially an IML. Ouch!! I confessed it was my fault the system stopped. After we were up again I wrote procedures for operators on how to activate a new IOCDS - which included shutting the system down first! Brian Nielsen On Tue, 6 Nov 2007 12:54:06 -0500, Jim Bohnsack [EMAIL PROTECTED] wrot e: Kris never worked with me. Perhaps I'm a bad influence. For Fran--I think a major bad choice IBM made was to have SHUTDOWN be the end-stop-kill command for anything else other than VM. If I remember correctly, RSCS has a SHUTDOWN command. I haven't used PVM for 10 or 15 years, but I think it did or does. A PC that IBM made back in the '80s (PC3270??) used SHUTDOWN to stop it and park the hard disk. I've SHUTDOWN CP when I intended to kill RSCS. A fellow (lady) sysprog I worked with killed CP trying to stop the PC. Another bad choice that IBM made was to have COLD as an IPL option, at least back in the olden days, without having some kind of really big nastygram coming out on the screen saying ARE YOU REALLY SURE YOU WANT TO DO THIS. We took COLD out as an IPL choice and replaced it with a word that only the sysprogs knew. Jim Kris Buelens wrote: No no, I never did. My worst outages happened in VM/SP where a SAVESY S of APL caused a VSE guest to abend. Impossible? That's what I told my customer and I SAVESYSed APL again... and VSE died again. So I had to admit I was the cause and started digging: the DMSSNT area for APL was in overlap with a CP PAGE area on VMPK01, mea culpa indeed. Nevertheless, we place SHUTDOWN in CLASS S. -- Jim Bohnsack Cornell University (607) 255-1760 [EMAIL PROTECTED] =
Re: Changing privclass of SHUTDOWN
=Behalf Of Mark Wheeler =Sent: Tuesday, November 06, 2007 4:47 PM =To: IBMVM@LISTSERV.UARK.EDU =Subject: Re: Changing privclass of SHUTDOWN = =I define the following in SYSTEM CONFIG: =/* Class S allows OPERATOR (and only OPERATOR) to issue SHUTDOWN */ = MODIFY Cmd SHUTDOWNPRIVclass S = DISABLE Cmd SHUTDOWN = =When OPERATOR wants to shut down the system, they must first issue CP =ENABLE COMMAND SHUTDOWN, then issue SHUTDOWN. This is way cool.
Re: FW: Issues with SLES10 and RHEL5 using FCP storage under z/VM 5.3 with guest Memory 2GB
The flash isn't quite correct, the problem in question affects z/VM 5.2.0 also. We're working to get the flash corrected. We already have the fix written and tested and verified to resolve the mo st reproducible set of symptoms (and fully expect it to resolve all known symptoms), so we'd like to offer it for fixtest / circumvention for any customers who would like it, especially those who have already experience d symptoms. The official APAR is working its way through the process, we expect the official PTF to be available within a week or so. - Bill Holder, IBM Endicott, z/VM Development and Service
Re: Changing privclass of SHUTDOWN
Mark - I really like that approach. On my system I changed the privcalss to Y for OPERATOR only. My operators are not used to typinge CP prefix for CP commands so when they type SHUTDOWN they get the my SHUTDOWN EXEC that asks them if they really want to shutdown the system. /Fran Hensler at Slippery Rock University of Pennsylvania USA for 44 years [EMAIL PROTECTED] +1.724.738.2153 Yes, Virginia, there is a Slippery Rock On Tue, 6 Nov 2007 15:46:37 -0600 Mark Wheeler said: I define the following in SYSTEM CONFIG: /* Class S allows OPERATOR (and only OPERATOR) to issue SHUTDOWN */ MODIFY Cmd SHUTDOWNPRIVclass S DISABLE Cmd SHUTDOWN When OPERATOR wants to shut down the system, they must first issue CP ENABLE COMMAND SHUTDOWN, then issue SHUTDOWN. Your gun, your bullet, your foot. But first you have to set the safety off. ;-) Mark Wheeler, 3M Company Alan Altmark [EMAIL PROTECTED] ibm.com To Sent by: The IBM IBMVM@LISTSERV.UARK.EDU z/VM Operating cc System [EMAIL PROTECTED] Subject ARK.EDU Re: Changing privclass of SHUTDOWN 11/06/2007 03:30 PM Please respond to The IBM z/VM Operating System [EMAIL PROTECTED] ARK.EDU On Tuesday, 11/06/2007 at 01:29 EST, Schuh, Richard [EMAIL PROTECTED] wrote: I wholeheartedly agree about using SHUTDOWN for other than CP being a poor choice. Unfortunately, that has been the case for so long that it will be difficult to change it now. And then there was the crowd who wanted the same command on all subsystems so as to make it simpler. Why does IBM invent a new command when we already have a perfectly good 'shutdown'? And, no, nothing is going to change at this point. Alan Altmark z/VM Development IBM Endicott
Re: Changing privclass of SHUTDOWN
On Nov 6, 2007, at 3:46 PM, Mark Wheeler wrote: I define the following in SYSTEM CONFIG: /* Class S allows OPERATOR (and only OPERATOR) to issue SHUTDOWN */ MODIFY Cmd SHUTDOWNPRIVclass S DISABLE Cmd SHUTDOWN When OPERATOR wants to shut down the system, they must first issue CP ENABLE COMMAND SHUTDOWN, then issue SHUTDOWN. Your gun, your bullet, your foot. But first you have to set the safety off. ;-) I also like to put a SHUTDOWN EXEC on the tools disk: /* SHUTDOWN EXEC */ Say No.
Re: Changing privclass of SHUTDOWN
On Tue, 6 Nov 2007 11:27:00 -0500, Jim Bohnsack [EMAIL PROTECTED] wrot e: You might want to put this change in SYSTEM CONFIG as well. What we use is: Modify Command Shutdown IBMclass A Privclasses Z Over the course of 30 years as a VM sysprog, every VM sysprog who I have worked with has shutdown a VM system *ONCE.* Me too :-[ Jim 1. I have never accidentally shut down a VM system. But then, I don't hav e any userids with class A (or class D) privileges. It always makes me cringe when I see a userid wi th class ABCDEFG. Like walking around with a loaded gun in your pocket! I have a CLASSA EXEC that issues: SET PRIVCLAS * +A CP command SET PRIVCLAS * -A when I really need a class A command. 2. We have a mod to CP SHUTDOWN that requires the system name on the SHUT DOWN command. Too many times an operator has shut down the wrong system. 3. We have a VM:Oper macro SHUTSYS that we prefer operators use. It does a clean shutdown, after bring various other things down cleanly. Maybe with the new SIGNAL SHUTDOWN this is not so necessary? 4. I am one of those that prefer the command be the same everywhere. I kn ow SHUTDOWN is dangerous. I hate it when QUIT or END is dangerous. 5. The real problem is that you shouldn't be able to bring a system down with just a single command -- no matter how you spell that command. Since at least the 1984 Apple Human Interface Guidelines, it's been expec ted that you ask the user before you let him/her do something irretreivable. Come to think of it, isn't that the same with XEDIT QUIT and QQUIT (some time before 1980)? Why doesn't CP prompt the operarator: Are you sure you want to bring this system down? Your job may be on the line. Think about it! Yes Are you really, really sure you want to bring this system down? Yes Enter your name and Social Security number: etc. Alan Ackerman Alan (dot) Ackerman (at) Bank of America (dot) com
