Re: Physical Planning Manuals
Thanks Ron! Peter
Re: MONWRITE files
And ideal on the amount of data were talking here on a typical day? i have several vm systems, and we also ftp the data to z/OS for reporting, so it is quite a lot of space that is occupied in z/VM and z/OS to hold all the data. For the performance toolkit its good to have a lot of data being collected in the mondcss so you can monitor your system, but for the reporting on z/OS only little of this data is required. thats why i set up this procedureto reduce the required disk space: * monwrite is defined with 2 minidisks,, both 500 cylinders * every 2 hours a stop and start is send to monwrite, which will close the current file and switch ofer to the other disk and start a new file * the old file is read by a rexx procedure and only a subset of the monitoring records are selected from it building a new file (about 10% of the original size), this reduced file is then send to z/OS by ftp for reporting. -- Less storage needed in VM and less storage needed on z/OS. Regards, Stefan Deutsche Börse Systems AG Chairman of the Supervisory Board/ Vorsitzender des Aufsichtsrats: Reto Francioni Executive Board/Vorstand: Michael Kuhn (Chief Executive Officer/Vorsitzender), Yves Baguet (Deputy Chief Executive Officer/ stellvertretender Vorsitzender), Thomas Eichelmann, Gerhard Leßmann. Aktiengesellschaft with registered seat in/mit Sitz in Frankfurt am Main. Commercial register/Handelsregister: Local court/Amtsgericht Frankfurt am Main HRB 42413. - Diese E-Mail enthaelt vertrauliche oder rechtlich geschuetzte Informationen. Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte sofort den Absender und loeschen Sie diese E-Mail. Das unbefugte Kopieren dieser E-Mail oder die unbefugte Weitergabe der enthaltenen Informationen ist nicht gestattet. The information contained in this message is confidential or protected by law. If you are not the intended recipient, please contact the sender and delete this message. Any unauthorised copying of this message or unauthorised distribution of the information contained herein is prohibited. Legally required information for business correspondence/ Gesetzliche Pflichtangaben fuer Geschaeftskorrespondenz: http://deutsche-boerse.com/letterhead
Re: MONWRITE files
Hi Stefan, In response to your statement, * the old file is read by a rexx procedure and only a subset of the monitoring records are selected from it building a new file (about 10% of the original size), this reduced file is then send to z/OS by ftp for reporting. I'd be interested in what this rexx is extracting. Our intent is to produce reports on CPU and memory usage and I agree the data is huge. Thanks Brian From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Stefan Raabe Sent: Tuesday, March 18, 2008 8:55 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: MONWRITE files Diese E-Mail enthaelt vertrauliche oder rechtlich geschuetzte Informationen. Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte sofort den Absender und loeschen Sie diese E-Mail. Das unbefugte Kopieren dieser E-Mail oder die unbefugte Weitergabe der enthaltenen Informationen ist nicht gestattet. The information contained in this message is confidential or protected by law. If you are not the intended recipient, please contact the sender and delete this message. Any unauthorised copying of this message or unauthorised distribution of the information contained herein is prohibited. Legally required information for business correspondence/ Gesetzliche Pflichtangaben fuer Geschaeftskorrespondenz: http://deutsche-boerse.com/letterhead
Re: MONWRITE files
Maybe this is where we need a NEW utility program, since MONWRITE is doin g exactly the job it was written for (copying ALL monitor data to disk/tape ?). Perhaps a utility that when pointed at a selection criteria file and a monwrite output file, will copy only those monitor records sellected. Or when pointed at such a selection criteria file and the MONDCSS segment, w ill connect to the MONDCSS segment and in real-time copy only those monitor records selected, thereby reducing the amount of VM DASD needed for a z/O S based capacity planning process. /Tom Kern On Tue, 18 Mar 2008 09:10:12 -0400, Hamilton, Brian [EMAIL PROTECTED] om wrote: Hi Stefan, In response to your statement, * the old file is read by a rexx procedure and only a subset of the monitoring records are selected from it building a new file (about 10% of the original size), this reduced file is then send to z/OS by ftp for reporting. I'd be interested in what this rexx is extracting. Our intent is to produce reports on CPU and memory usage and I agree the data is huge. Thanks Brian
Re: MONWRITE files
Unless the objective is to have a program that will collect some of the records for one reporting function and another instance of the program collecting a different selection of the monitor records for a different reporting function, why not just limit the amount of records written to the monitor segment in the first place? Jim Thomas Kern wrote: Maybe this is where we need a NEW utility program, since MONWRITE is doin= g exactly the job it was written for (copying ALL monitor data to disk/tape= ?). Perhaps a utility that when pointed at a selection criteria file and a monwrite output file, will copy only those monitor records sellected. Or when pointed at such a selection criteria file and the MONDCSS segment, w= ill connect to the MONDCSS segment and in real-time copy only those monitor records selected, thereby reducing the amount of VM DASD needed for a z/O= S based capacity planning process. /Tom Kern On Tue, 18 Mar 2008 09:10:12 -0400, Hamilton, Brian [EMAIL PROTECTED] om wrote: Hi Stefan,=20 In response to your statement,=20 * the old file is read by a rexx procedure and only a subset of the monitoring records are selected from=20 it building a new file (about 10% of the original size), this reduced file is then send to z/OS by ftp for reporting. I'd be interested in what this rexx is extracting. Our intent is to produce reports on CPU and memory usage and I agree the data is huge. Thanks Brian -- Jim Bohnsack Cornell University (607) 255-1760 [EMAIL PROTECTED]
Re: MONWRITE files
Because as someone pointed out before (Barton, I think), for performance monitoring, you want more event data and for capacity planning you need appropriate sample data. I think PerfTK could deal with more data than it needs for online real-time performance monitoring, while another process selectively collects from the same source a subset of that data for capac ity planning using that other z/OS product. /Tom Kern On Tue, 18 Mar 2008 11:01:07 -0400, Jim Bohnsack [EMAIL PROTECTED] wro te: Unless the objective is to have a program that will collect some of the records for one reporting function and another instance of the program collecting a different selection of the monitor records for a different reporting function, why not just limit the amount of records written to the monitor segment in the first place? Jim
Mdisk 3390 Model 9 dasd
NB: This email and its contents are subject to our email legal notice which can be viewed at http://www.sars.gov.za/Email_Disclaimer.pdf Good day, Firstly, apologies for a very basic question from a z/OS system programmer. Not being a VM expert, I've been struggling with this for most of the day and was hoping someone could perhaps help while I'm still downloading the manuals. I am busy with the zLINUX installation on zVM. I would like to make use of 3390 Model 9 disk for the Linux software. We would like to make use of a bit more space (over 3338 cyl or 2.7Gb) and hence have the following definitions in USER DIRECT : USER LINUX02 LNX4VM 512M 2G G INCLUDE LINDFLT OPTION APPLMON MDISK 100 3390 0001 4500 LNX000 MR LNX4VM LNX4VM LNX4VM MDISK 102 3390 4501 0300 LNX000 MR LNX4VM LNX4VM LNX4VM MDISK 103 3390 4801 3038 LNX000 MR LNX4VM LNX4VM LNX4VM MDISK 104 3390 7839 2177 LNX000 MR LNX4VM LNX4VM LNX4VM When I logon to LINUX02, I get the following msg : LOGON LINUX02 HCPLNM1151E LINUX02 0100 has not been linked because it is not within CP volume extents. HCPLNM1151E LINUX02 0102 has not been linked because it is not within CP volume extents. HCPLNM1151E LINUX02 0103 has not been linked because it is not within CP volume extents. HCPLNM1151E LINUX02 0104 has not been linked because it is not within CP volume extents. Searching on this msg does not provide any clues how to specify that this is a 3390 Model 9 dasd. Your assistance is very much appreciated. Kind Regards, Vikesh Bhoola
Re: Mdisk 3390 Model 9 dasd
According to help HCPLNM1151E your LNX000 DASD volume is not a 3390-9. I would guess that it is a 3390-3. You may want to ATTACH the device ucb for LNX000 to yourself then do DEVTYPE ucb. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Vikesh Bhoola Sent: Tuesday, March 18, 2008 11:18 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Mdisk 3390 Model 9 dasd NB: This email and its contents are subject to our email legal notice which can be viewed at http://www.sars.gov.za/Email_Disclaimer.pdf Good day, Firstly, apologies for a very basic question from a z/OS system programmer. Not being a VM expert, I've been struggling with this for most of the day and was hoping someone could perhaps help while I'm still downloading the manuals. I am busy with the zLINUX installation on zVM. I would like to make use of 3390 Model 9 disk for the Linux software. We would like to make use of a bit more space (over 3338 cyl or 2.7Gb) and hence have the following definitions in USER DIRECT : USER LINUX02 LNX4VM 512M 2G G INCLUDE LINDFLT OPTION APPLMON MDISK 100 3390 0001 4500 LNX000 MR LNX4VM LNX4VM LNX4VM MDISK 102 3390 4501 0300 LNX000 MR LNX4VM LNX4VM LNX4VM MDISK 103 3390 4801 3038 LNX000 MR LNX4VM LNX4VM LNX4VM MDISK 104 3390 7839 2177 LNX000 MR LNX4VM LNX4VM LNX4VM When I logon to LINUX02, I get the following msg : LOGON LINUX02 HCPLNM1151E LINUX02 0100 has not been linked because it is not within CP volume extents. HCPLNM1151E LINUX02 0102 has not been linked because it is not within CP volume extents. HCPLNM1151E LINUX02 0103 has not been linked because it is not within CP volume extents. HCPLNM1151E LINUX02 0104 has not been linked because it is not within CP volume extents. Searching on this msg does not provide any clues how to specify that this is a 3390 Model 9 dasd. Your assistance is very much appreciated. Kind Regards, Vikesh Bhoola This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing.
Re: Mdisk 3390 Model 9 dasd
From the MAINT id, enter Q DASD LNX000. This will give you the device address of that volume, such as: DASD 6903 CP SYSTEM LNX000 Then enter Q DASD DETAILS and find out how many cylinders CP thinks it has. If it is incorrect, it isn't configured correctly in the storage controller or you have the wrong address. On Tue, Mar 18, 2008 at 11:18 AM, Vikesh Bhoola [EMAIL PROTECTED] wrote: NB: This email and its contents are subject to our email legal notice which can be viewed at http://www.sars.gov.za/Email_Disclaimer.pdf Good day, Firstly, apologies for a very basic question from a z/OS system programmer. Not being a VM expert, I've been struggling with this for most of the day and was hoping someone could perhaps help while I'm still downloading the manuals. I am busy with the zLINUX installation on zVM. I would like to make use of 3390 Model 9 disk for the Linux software. We would like to make use of a bit more space (over 3338 cyl or 2.7Gb) and hence have the following definitions in USER DIRECT : USER LINUX02 LNX4VM 512M 2G G INCLUDE LINDFLT OPTION APPLMON MDISK 100 3390 0001 4500 LNX000 MR LNX4VM LNX4VM LNX4VM MDISK 102 3390 4501 0300 LNX000 MR LNX4VM LNX4VM LNX4VM MDISK 103 3390 4801 3038 LNX000 MR LNX4VM LNX4VM LNX4VM MDISK 104 3390 7839 2177 LNX000 MR LNX4VM LNX4VM LNX4VM When I logon to LINUX02, I get the following msg : LOGON LINUX02 HCPLNM1151E LINUX02 0100 has not been linked because it is not within CP volume extents. HCPLNM1151E LINUX02 0102 has not been linked because it is not within CP volume extents. HCPLNM1151E LINUX02 0103 has not been linked because it is not within CP volume extents. HCPLNM1151E LINUX02 0104 has not been linked because it is not within CP volume extents. Searching on this msg does not provide any clues how to specify that this is a 3390 Model 9 dasd. Your assistance is very much appreciated. Kind Regards, Vikesh Bhoola -- Bruce Hayden Linux on System z Advanced Technical Support Endicott, NY
Re: MONWRITE files
On Tue, 18 Mar 2008 09:41:24 -0500 =?ISO-8859-1?Q?Thomas_Kern?= said: Maybe this is where we need a NEW utility program, since MONWRITE is doing exactly the job it was written for (copying ALL monitor data to disk/tape?). Perhaps a utility that when pointed at a selection criteria file and a monwrite output file, will copy only those monitor records sellected. Or when pointed at such a selection criteria file and the MONDCSS segment, will connect to the MONDCSS segment and in real-time copy only those monitor records selected, thereby reducing the amount of VM DASD needed for a z/OS based capacity planning process. Actually, there already is such a utility program, and it is shipped with every z/VM system. It's kept on the 190 or S-disk so you may not think to look there. It's called CMS Pipelines. There is a STARMON stage for reading data from the MONDCSS and *MONITOR IUCV service. There is a DEBLOCK MONITOR stage for reformating the headers, and there are LOCATE and other stages for selecting the records desired. (DFSORT or SYNCSORT is often used for selecting SMF records on MVS, when lots of SMF records are recorded, but not need for every process. Pipelines would be the corresponding tool) For more details, PIPE AHELP STARMON, and PIPE AHELP DEBLOCK. Also see http://www2.marist.edu/~pipeline/pipeline.news117 http://www2.marist.edu/~pipeline/pipeline.news1110 http://www2.marist.edu/~pipeline/bhelp/ACH0201.html /ahw /Tom Kern On Tue, 18 Mar 2008 09:10:12 -0400, Hamilton, Brian [EMAIL PROTECTED] wrote: Hi Stefan, In response to your statement, * the old file is read by a rexx procedure and only a subset of the monitoring records are selected from it building a new file (about 10% of the original size), this reduced file is then send to z/OS by ftp for reporting. I'd be interested in what this rexx is extracting. Our intent is to produce reports on CPU and memory usage and I agree the data is huge. Thanks Brian
Re: MONWRITE files
Almost. I would consider the PIPE that uses the starmon stage to be a utility; the stage by itself is simply a tool used to build the utility. An interesting thought: when was the last time someone sat down and went through everything that's on the default S disk? It might be very interesting/useful to do that as a community and undertake to write replacements for some of the more elderly pieces of code.
Re: MONWRITE files
Here some code from y TSLAMON EXEC that performs some calculations
(CPU usage and WAIT%), These waits is something RTM/ESA nor VMPRF
didn't provide in real-time, hence my -old- code.
'|Irefr: FaninAny',
'|R: REXX ('myname mytype')' refresh, /* Perform calculations */
'|FILESLOW' fid,
'?IMMCMD SUSPEND|SPEC /SUSPEND/ 1|Irefr:',
'?IMMCMD $$REXX$$|INSERT /$$REXX$$ / 1|Irefr:',
'? starmon mondcss sample',/* Obtain data */
'|R4: STRFIND X404040400444', /* Keep Domain 4, record 4 */
'|R:',/* Pass for calculations*/
'?R4:|STRFIND X404040400443', /* Also Domain 4, record 3 */
'|R:',/* Pass for calculations*/
The complete TSLAMON EXEC is available on request.
2008/3/18, Schuh, Richard [EMAIL PROTECTED]:
Almost. I would consider the PIPE that uses the starmon stage to be a
utility; the stage by itself is simply a tool used to build the utility.
Regards,
Richard Schuh
-Original Message-
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of A. Harry Williams
Sent: Tuesday, March 18, 2008 8:59 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: MONWRITE files
Actually, there already is such a utility program, and it is
shipped with every z/VM system. It's kept on the 190 or
S-disk so you may not think to look there. It's called CMS
Pipelines. There is a STARMON stage for reading data from
the MONDCSS and *MONITOR IUCV service. There is a DEBLOCK
MONITOR stage for reformating the headers, and there are
LOCATE and other stages for selecting the records desired.
(DFSORT or SYNCSORT is often used for selecting SMF records
on MVS, when lots of SMF records are recorded, but not need
for every process. Pipelines would be the corresponding tool)
For more details, PIPE AHELP STARMON, and PIPE AHELP DEBLOCK.
Also see
http://www2.marist.edu/~pipeline/pipeline.news117
http://www2.marist.edu/~pipeline/pipeline.news1110
http://www2.marist.edu/~pipeline/bhelp/ACH0201.html
/ahw
/Tom Kern
On Tue, 18 Mar 2008 09:10:12 -0400, Hamilton, Brian
[EMAIL PROTECTED]
wrote:
Hi Stefan,
In response to your statement,
* the old file is read by a rexx procedure and only a subset of the
monitoring records are selected from it building a new file
(about 10%
of the original size), this reduced file is then send to
z/OS by ftp
for reporting.
I'd be interested in what this rexx is extracting. Our
intent is to
produce reports on CPU and memory usage and I agree the
data is huge.
Thanks
Brian
--
Kris Buelens,
IBM Belgium, VM customer support
Re: MONWRITE files
I would be interested in getting a copy of the complete TSLMON EXEC.
Thanks for your help.
/Thomas Kern
/301-903-2211
/U.S. Department of Energy
/[EMAIL PROTECTED]
On Tue, 18 Mar 2008 18:19:43 +0100, Kris Buelens [EMAIL PROTECTED]
wrote:
Here some code from y TSLAMON EXEC that performs some calculations
(CPU usage and WAIT%), These waits is something RTM/ESA nor VMPRF
didn't provide in real-time, hence my -old- code.
'|Irefr: FaninAny',
'|R: REXX ('myname mytype')' refresh, /* Perform calculations */
'|FILESLOW' fid,
'?IMMCMD SUSPEND|SPEC /SUSPEND/ 1|Irefr:',
'?IMMCMD $$REXX$$|INSERT /$$REXX$$ / 1|Irefr:',
'? starmon mondcss sample',/* Obtain data */
'|R4: STRFIND X404040400444', /* Keep Domain 4, record 4 */
'|R:',/* Pass for calculations*/
'?R4:|STRFIND X404040400443', /* Also Domain 4, record 3 */
'|R:',/* Pass for calculations*/
The complete TSLAMON EXEC is available on request.
Kris Buelens,
IBM Belgium, VM customer support
Re: MONWRITE files
If you search google, using z/VM performance capacity planning, you should see velocitysoftware.com/whylps.html as the first link. This is the description of instrumentation requirements. I've also offered zMON (dirt cheap, by the way) as a real time monitor that will produce records for MICS or MXG. The benefit to this is that you have a monitor with a standard one minute granularity, but you write out the records that MICS or MXG want every 15 minutes. This reduces your disk requirements by usually more than factor of 100, and satisfies most basic needs for performance data AND capacity planning data (as well as operational alerts). Thomas Kern wrote: Because as someone pointed out before (Barton, I think), for performance monitoring, you want more event data and for capacity planning you need appropriate sample data. I think PerfTK could deal with more data than it needs for online real-time performance monitoring, while another process selectively collects from the same source a subset of that data for capac ity planning using that other z/OS product. /Tom Kern On Tue, 18 Mar 2008 11:01:07 -0400, Jim Bohnsack [EMAIL PROTECTED] wro te: Unless the objective is to have a program that will collect some of the records for one reporting function and another instance of the program collecting a different selection of the monitor records for a different reporting function, why not just limit the amount of records written to the monitor segment in the first place? Jim
Re: MONWRITE files
Or you could look at the Redbooks. The additional files from REDP3818
has a sample for a monwrite machine that filters records. In this case
CPU usage records.
Kris, isn't TSLAMON avalable on the VM download packages?
Regards, Berry.
Kris Buelens schreef:
Here some code from y TSLAMON EXEC that performs some calculations
(CPU usage and WAIT%), These waits is something RTM/ESA nor VMPRF
didn't provide in real-time, hence my -old- code.
'|Irefr: FaninAny',
'|R: REXX ('myname mytype')' refresh, /* Perform calculations */
'|FILESLOW' fid,
'?IMMCMD SUSPEND|SPEC /SUSPEND/ 1|Irefr:',
'?IMMCMD $$REXX$$|INSERT /$$REXX$$ / 1|Irefr:',
'? starmon mondcss sample',/* Obtain data */
'|R4: STRFIND X404040400444', /* Keep Domain 4, record 4 */
'|R:',/* Pass for calculations*/
'?R4:|STRFIND X404040400443', /* Also Domain 4, record 3 */
'|R:',/* Pass for calculations*/
The complete TSLAMON EXEC is available on request.
Sir Arthur C. Clarke, RIP
Somewhat OT, but of interest none the less, imho Sci-fi writer Arthur C. Clarke dies at 90, aide says http://www.chron.com/disp/story.mpl/headline/world/5630362.html DJ
Re: Mdisk 3390 Model 9 dasd
Did you ever resolve this? -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Vikesh Bhoola Sent: Tuesday, March 18, 2008 10:18 To: IBMVM@LISTSERV.UARK.EDU Subject: Mdisk 3390 Model 9 dasd NB: This email and its contents are subject to our email legal notice which can be viewed at http://www.sars.gov.za/Email_Disclaimer.pdf Good day, Firstly, apologies for a very basic question from a z/OS system programmer. Not being a VM expert, I've been struggling with this for most of the day and was hoping someone could perhaps help while I'm still downloading the manuals. I am busy with the zLINUX installation on zVM. I would like to make use of 3390 Model 9 disk for the Linux software. We would like to make use of a bit more space (over 3338 cyl or 2.7Gb) and hence have the following definitions in USER DIRECT : USER LINUX02 LNX4VM 512M 2G G INCLUDE LINDFLT OPTION APPLMON MDISK 100 3390 0001 4500 LNX000 MR LNX4VM LNX4VM LNX4VM MDISK 102 3390 4501 0300 LNX000 MR LNX4VM LNX4VM LNX4VM MDISK 103 3390 4801 3038 LNX000 MR LNX4VM LNX4VM LNX4VM MDISK 104 3390 7839 2177 LNX000 MR LNX4VM LNX4VM LNX4VM When I logon to LINUX02, I get the following msg : LOGON LINUX02 HCPLNM1151E LINUX02 0100 has not been linked because it is not within CP volume extents. HCPLNM1151E LINUX02 0102 has not been linked because it is not within CP volume extents. HCPLNM1151E LINUX02 0103 has not been linked because it is not within CP volume extents. HCPLNM1151E LINUX02 0104 has not been linked because it is not within CP volume extents. Searching on this msg does not provide any clues how to specify that this is a 3390 Model 9 dasd. Your assistance is very much appreciated. Kind Regards, Vikesh Bhoola
