I change the Ready prompt as follows: id
MAINT AT ZVM5VSE VIA RSCS 09/26/2008 09:25:11 EDT FRIDAY <MAINT AT ZVMESA5> Ready; T=0.01/0.01 09:25:11 I too have many UserIDs on many VM systems and this really helps. Thank you, Scott R Wandschneider Senior Systems Programmer Infocrossing Office 402.963.8905 > -----Original Message----- > From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf > Of Dave Hansen > Sent: Friday, September 26, 2008 7:51 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: Modifying the CMS Ready Message > > I must have got this from Kris indirectly: > > > /* This exec changes CMS' READY message by including userid info. > +-----------------------------------------------------------+ > | format: | RDYMSG | > +-----------------------------------------------------------+ > Adapted by: Kris Buelens IBM Belgium; BUELENSC at IECVM 19 Apr 1993 > from: David Lybrand & Joachim Becela */ > parse upper source . . myname mytype . syn . > address command > > /*---------------------------------------------------------------------+ > | Have a RDYMSG with a highlighted 'USERID at NODE' | > +---------------------------------------------------------------------*/ > 'ID (LIFO' > pull myid . mynode . > rdymsg.1 = '& 3' > /* > rdymsg.2 = '8116 '||'1DE8'x||myid 'at' mynode||'1D60'x||'is ready' > */ > rdymsg.2 = '8116 Ready'||'1DE8'x||myid 'at' mynode||'1D60'x > 'RENAME DMSUME REPOS A RDYMSG REPOS A' > ren_rc = rc > if rc*(rc<>28) = 0 then do > 'EXECIO 2 DISKW DMSUME REPOS A3 0 F 80 (FINIS STEM RDYMSG.' > 'GENMSG DMSUME REPOS A3 DMS (NOLIST MARGIN 63' > 'SET LANG (ADD DMS USER' > 'ERASE DMSUME TEXT' > end > if ren_rc = 0 then 'RENAME RDYMSG REPOS A DMSUME REPOS A' > > Later, Dave H. > > > > > > "Gentry, Stephen" > <[EMAIL PROTECTED]> > Sent by: The IBM z/VM Operating System > To > <IBMVM@LISTSERV.UARK.EDU> > IBMVM@LISTSERV.UARK.EDU > > cc > > 09/26/2008 07:46 AM > Subject > Re: > Modifying the CMS Ready Message > > Please respond to > The IBM z/VM Operating System > <IBMVM@LISTSERV.UARK.EDU> > > > > > > > I modify it to help keep track of what userid I'm logged on to. > Sometimes, I'll have 2(two) or more sessions going. > Steve > > -----Original Message----- > From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On > Behalf Of Buettner, Wolfgang > Sent: Friday, September 26, 2008 4:16 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Modifying the CMS Ready Message > > Mike's respond to "DASD VOLUME SIZES" below pointed me to the obviously > modified Ready Messages. > What idea is behind and how is it implemented? > > Thank you, > Wolfgang Buettner > > > > Software AG - Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, > Germany, - Registergericht/Commercial register: Darmstadt HRB 1562 - > Vorstand/ Management Board: Karl-Heinz Streibich > (Vorsitzender/Chairman), David Broadbent, Mark Edwards, Dr. Peter > Kurpick,Arnd Zinnhardt; - Aufsichtsratsvorsitzender/ Chairman of the > Supervisory Board: Frank F. Beelitz - http://www.softwareag.com > > > > -----Original Message----- > > From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On > Behalf Of Mike Walter > Sent: Thursday, September 25, 2008 8:16 PM > To: ibmvm@listserv.uark.edu > Subject: Re: DASD VOLUME SIZES > > You might want to put a 1 cylinder minidisk on the highest real disk > cylinder as a 'tail end charley' so that you know not to allocate past > that. For each read DASD, I create a userid such as (just added the > FFFF mdisk as an example): > USER -540RES- NOLOG > MDISK A00 3390 00000 00001 540RES R > MDISK F00 3390 00000 END 540RES R > MDISK FFFF 3390 10017 00001 540RES R > This allows authorized automation EXECs to link to the Allocation Bit > map (mdisk A00), the full volume (mdisk F00), and with the described > mdisk > FFFF: provides the 'tail end charley' as a clear indicator of the last > cylinder when looking at DISKMAP or DIRMAP output. How important is one > cylinder per DASD any more? > > But .... to answer the question directly with an real-life example: > cp query dasd 540res > DASD 6A40 CP SYSTEM 540RES 0 > M2WALTER HALINVA1; T=0.01/0.01 13:06:13 > cp query dasd details 6a40 6A40 CUTYPE = 3990-E9, DEVTYPE = 3390-0C, > VOLSER = 540RES, CYLS = 10017 > <---- note the total cylinders on this line > CACHE DETAILS: CACHE NVS CFW DFW PINNED CONCOPY > -SUBSYSTEM Y Y Y - N N > -DEVICE Y - - Y N N > DEVICE DETAILS: CCA = 40, DDC = -- > DUPLEX DETAILS: -- > M2WALTER HALINVA1; T=0.01/0.01 13:06:19 > > Mike Walter > Hewitt Associates > Any opinions expressed herein are mine alone and do not necessarily > represent the opinions or policies of Hewitt Associates. > > > > "Howard Rifkind" <[EMAIL PROTECTED]> > > Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> > 09/25/2008 11:58 AM > Please respond to > "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> > > > > To > IBMVM@LISTSERV.UARK.EDU > cc > > Subject > DASD VOLUME SIZES > > > > > > > What would be the quickest way to find out the size of a volume which > currently has minidisks allocated on it. > > Cylinders? > > > > _____________ > LEGAL NOTICE > Unless expressly stated otherwise, this message is confidential and may > be privileged. It is intended for the addressee(s) only. > Access to this E-mail by anyone else is unauthorized. > If you are not an addressee, any disclosure or copying of the contents > of this E-mail or any action taken (or not taken) in reliance on it is > unauthorized and may be unlawful. If you are not an addressee, please > inform the sender immediately, then delete this message and empty from > your trash. > > > > > > > The information contained in this e-mail and any accompanying documents > may contain information that is confidential or otherwise protected from > disclosure. If you are not the intended recipient of this message, or if > this message has been addressed to you in error, please immediately > alert the sender by reply e-mail and then delete this message, including > any attachments. Any dissemination, distribution or other use of the > contents of this message by anyone other than the intended recipient is > strictly prohibited. All messages sent to and from this e-mail address > may be monitored as permitted by applicable law and regulations to > ensure compliance with our internal policies and to protect our > business. E-mails are not secure and cannot be guaranteed to be error > free as they can be intercepted, amended, lost or destroyed, or contain > viruses. You are deemed to have accepted these risks if you communicate > with us by e-mail. > > > Disclaimer: Information in this message or an attachment may be government > data and thereby subject to the Minnesota Government Data Practices Act, > Minnesota Statutes, Chapter 13, may be subject to attorney-client or work > product privilege, may be confidential, privileged, proprietary, or otherwise > protected, and the unauthorized review, copying, retransmission, or other use > or disclosure of the information is strictly prohibited. If you are not the > intended recipient of this message, please immediately notify the sender of > the transmission error and then promptly delete this message from your > computer system.
