Re: Checking a DASD label
On 12/12/06, Rob van der Heij [EMAIL PROTECTED] wrote: How 'bout trackread? Oh, yes... there also is 'trackwrite' that will take the tracks from trackread. You may find that easier to automate than driving DDR from input files, but that's up to you. Rob
Re: Checking a DASD label
On 12/12/06, Rob van der Heij [EMAIL PROTECTED] wrote: How 'bout trackread? Sounds just what I need - but it does not work for me. I guess this is part of the alternate PIPES package? Colin Allinson Amadeus Data Processing
Re: Checking a DASD label
On 12/12/06, Colin Allinson [EMAIL PROTECTED] wrote: Sounds just what I need - but it does not work for me. I guess this is part of the alternate PIPES package? Oh, you mean you still run the 10-year old plumbing? Tssj... ;-) Yes, trackread was added back in 2001. You would need to pick up a version of the CMS Pipelines Runtime Library from the Pipelines page at Marist. Obviously you can keep it just on the users where you need that new function. Rob
Re: Checking a DASD label
On 12/12/06, Rob van der Heij [EMAIL PROTECTED] wrote: Oh, you mean you still run the 10-year old plumbing? Tssj... ;-) Yes, we are still in the dark ages here - but I think this might give me an excuse to leap into the future. ;-) Do you have a link to the Marist page to get the download and install instructions. Thanks Colin
problem with an old vm/esa environment after migration to a flex-es tserver
Hi listers, I have a customer with a really old VM/ESA 2.2, VSE/ESA 2.3 and SQLDS database. Now after migration to the tserver he complains about performance problems. What I have figured out that he has massive paging only on SQLDS service machine (300-500 pages/s). This I cannot understand, because first he has more memory available as before on multiprise (193 MB vs. 768 MB now) and second we haven't changed the system layout compared to the multiprise. We have migrated the system by dump/restoring the volumes with DDR. So what can cause only the sqlds machine to page so heavily? I have already doubled the virtual memory to 96 MB but this had no effect on the behaviour. Does anybody have an idea, where I can search for the problem? Mit freundlichen Grüßen / best regards Franz Josef Pohlen
Re: problem with an old vm/esa environment after migration to a flex-es tserver
Check your CP default MDC settings or set them off all together. The defaults hurt me very bad in a z/VM 3.1 system. Hans -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Pohlen (Mailinglist) Sent: December 12, 2006 8:54 AM To: IBMVM@LISTSERV.UARK.EDU Subject: problem with an old vm/esa environment after migration to a flex-es tserver Hi listers, I have a customer with a really old VM/ESA 2.2, VSE/ESA 2.3 and SQLDS database. Now after migration to the tserver he complains about performance problems. What I have figured out that he has massive paging only on SQLDS service machine (300-500 pages/s). This I cannot understand, because first he has more memory available as before on multiprise (193 MB vs. 768 MB now) and second we haven't changed the system layout compared to the multiprise. We have migrated the system by dump/restoring the volumes with DDR. So what can cause only the sqlds machine to page so heavily? I have already doubled the virtual memory to 96 MB but this had no effect on the behaviour. Does anybody have an idea, where I can search for the problem? Mit freundlichen Grüßen / best regards Franz Josef Pohlen
Re: problem with an old vm/esa environment after migration to a flex-es tserver
Do you know if this paging is real paging or Dataspace I/O: when using VM dataspace support in DB2, all DB2 I/O is done by CP paging, hence high page rates. Quite some years ago, I created a document to explain the difference. It is called Data in memory techniques or alike and available on the VM web page. If you search for EXECLOAD, NUCXLOAD and, BUELENS you should quickly find it back. It contains an EXEC that you can run in a server every x minutes and that then will report how many real page in/out happend and how many dataspace read/writes (based on counts reported by CP IND SPACES) If you've got RTM/ESA, its DISPLAY SYSDASD command also reports the dataspace paging I/O Kris, IBM Belgium, VM customer support Pohlen (Mailinglist) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 2006-12-12 14:54 Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject problem with an old vm/esa environment after migration to a flex-es tserver Hi listers, I have a customer with a really old VM/ESA 2.2, VSE/ESA 2.3 and SQLDS database. Now after migration to the tserver he complains about performance problems. What I have figured out that he has massive paging only on SQLDS service machine (300-500 pages/s). This I cannot understand, because first he has more memory available as before on multiprise (193 MB vs. 768 MB now) and second we haven't changed the system layout compared to the multiprise. We have migrated the system by dump/restoring the volumes with DDR. So what can cause only the sqlds machine to page so heavily? I have already doubled the virtual memory to 96 MB but this had no effect on the behaviour. Does anybody have an idea, where I can search for the problem? Mit freundlichen Grüßen / best regards Franz Josef Pohlen
Re: Checking a DASD label
If you only want the disk label, there is the DEVTYPE command. Kris, IBM Belgium, VM customer support Colin Allinson [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 2006-12-12 09:22 Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Checking a DASD label I am linking to a fullpack minidisk and, in preparation for a copy, I want to check the label on the source disk is what it should be. In our environment the label could have changed since the DASD was attached to the system so Q DASD DETAILS or looking at the RDEV block won't help. If the DASD has a standard CP/OS label then accessing it as a minidisk will get the information I require - but it is possible that some DASD might have only minimal labels. I have not found one to try yet but I don't think ACCESS will work for these. The only way I can think of is to physically read the first track of the disk and process it. Any ideas on the best way to do this? DDR seems a bit unweildy in terms of getting the output into an EXEC/PIPE for processing. My current code caters for most situations but I would like to build a comprehensive solution. Thanks in advance, Colin Allinson Amadeus Data Processing
Re: Checking a DASD label
On 12/12/06, Kris Buelens [EMAIL PROTECTED] wrote: If you only want the disk label, there is the DEVTYPE command. Kris, Brilliant - that is just what I needed. Now implemented and working. ** Why didn't I know about that - DUH!! ** Mind you, the question has been helpful because I have learnt a lot from Rob about the PIPELINES RUNTIME LIBRARY and other ways of doing things. Thanks Colin Allinson Amadeus Data Processing
Re: Checking a DASD label
DDR is easy:
/* check a DASD label */
arg vaddr .
'PIPE',
'LITERAL SYSPRINT CONS',
'| LITERAL PROMPTS OFF',
'| LITERAL INPUT' vaddr 'DASD',
'| LITERAL TYPE 0 TO 0',
'| INSTORE REVERSE',
'| OUTSTORE',
'| LABEL CHECK A'
'PIPE',
'CMS DDR LABEL CHECK A',
'| TAKE 1',
'| LOCATE /HCPDDR696I/',
'| SPECS W5',
'| VAR dasd_label'
IF symbol('dasd_label')'VAR'
THEN say vaddr 'is not a DASD'
ELSE say 'DASD label='dasd_label
Brian Nielsen
On Tue, 12 Dec 2006 09:22:33 +0100, Colin Allinson
[EMAIL PROTECTED] wrote:
I am linking to a fullpack minidisk and, in preparation for a copy, I wa
nt
to check the label on the source disk is what it should be.
In our environment the label could have changed since the DASD was
attached to the system so Q DASD DETAILS or looking at the RDEV block
won't help.
If the DASD has a standard CP/OS label then accessing it as a minidisk
will get the information I require - but it is possible that some DASD
might have only minimal labels. I have not found one to try yet but I
don't think ACCESS will work for these.
The only way I can think of is to physically read the first track of the
disk and process it. Any ideas on the best way to do this? DDR seems a b
it
unweildy in terms of getting the output into an EXEC/PIPE for processing
.
My current code caters for most situations but I would like to build a
comprehensive solution.
Thanks in advance,
Colin Allinson
Amadeus Data Processing
Re: problem with an old vm/esa environment after migration to a flex-es tserver
Hi Kris, it seems to be dasd paging, because there is also heavy i/o on one paging dasd. I have found your data in memory techniques document, but there is no exec for checking ind spaces only qnssmap exec is listed there. But it was a good hint. I have created a small exec which does the ind spaces user xxx every minute and writes the result with a timestamp into a file. This I will let the customer run a few hours and check the results. I will not parse the command now because I have zVM 5.2 and I'm not sure if the command output is the same on VM/ESA 2.2. If I have the results available I will contact you again. regards Franz Josef - Original Message - From: Kris Buelens [EMAIL PROTECTED] To: IBMVM@LISTSERV.UARK.EDU Sent: Tuesday, December 12, 2006 3:44 PM Subject: Re: [IBMVM] problem with an old vm/esa environment after migration to a flex-es tserver Do you know if this paging is real paging or Dataspace I/O: when using VM dataspace support in DB2, all DB2 I/O is done by CP paging, hence high page rates. Quite some years ago, I created a document to explain the difference. It is called Data in memory techniques or alike and available on the VM web page. If you search for EXECLOAD, NUCXLOAD and, BUELENS you should quickly find it back. It contains an EXEC that you can run in a server every x minutes and that then will report how many real page in/out happend and how many dataspace read/writes (based on counts reported by CP IND SPACES) If you've got RTM/ESA, its DISPLAY SYSDASD command also reports the dataspace paging I/O Kris, IBM Belgium, VM customer support Pohlen (Mailinglist) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 2006-12-12 14:54 Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject problem with an old vm/esa environment after migration to a flex-es tserver Hi listers, I have a customer with a really old VM/ESA 2.2, VSE/ESA 2.3 and SQLDS database. Now after migration to the tserver he complains about performance problems. What I have figured out that he has massive paging only on SQLDS service machine (300-500 pages/s). This I cannot understand, because first he has more memory available as before on multiprise (193 MB vs. 768 MB now) and second we haven't changed the system layout compared to the multiprise. We have migrated the system by dump/restoring the volumes with DDR. So what can cause only the sqlds machine to page so heavily? I have already doubled the virtual memory to 96 MB but this had no effect on the behaviour. Does anybody have an idea, where I can search for the problem? Mit freundlichen Grüßen / best regards Franz Josef Pohlen
RSCS LPR Printer Name w/spaces
I have set up an RSCS LPR link that prints to a Hummingbird LPD server on a PC. The PRINTER name has no spaces and is 27 characters. This is working just fine. Now I want to do the same thing but the printer name has embedded spaces. When I click on properties for the printer I do not get an option to rename the printer. It is a network printer. I enclosed the printer name in single quotes but I get a NAK when I try to print to it. PRINTER='eX- Printer on https://xxx.xx-.us/printers/default' Does anyone know how I could either rename this printer to remove spaces or how to make RSCS print to printer name with embedded spaces. /Fran Hensler at Slippery Rock University of Pennsylvania USA for 43 years [EMAIL PROTECTED] +1.724.738.2153 Yes, Virginia, there is a Slippery Rock
Re: RSCS LPR Printer Name w/spaces
I enclosed the printer name in single quotes but I get a NAK when I try to print to it. PRINTER='eX- Printer on https://xxx.xx- .us/printers/default' Does anyone know how I could either rename this printer to remove spaces or how to make RSCS print to printer name with embedded spaces. Have the machine that has access to the printer share it as a name that does not have spaces in it. The Windows LPD will honor shared names as well as the original name.
Re: RSCS LPR Printer Name w/spaces
I enclosed the printer name in single quotes but I get a NAK when I try to print to it. PRINTER='eX- Printer on https://xxx.xx- .us/printers/default' Does anyone know how I could either rename this printer to remove spaces or how to make RSCS print to printer name with embedded spaces. Have the machine that has access to the printer share it as a name that does not have spaces in it. The Windows LPD will honor shared names as well as the original name. Did you trace the RSCS link to see what was actually sent as the printer queue name? Did it include the entire string with the start/end quote? Best Regards, Les Geer IBM z/VM and Linux Development
Re: PPRC and R/W Minidisks
Alan is correct (of course). The VM DUPLEX DETAILS output only applies to the legacy 3990 Duplex function, not PPRC. However, if you have APAR VM63256 applied on z/VM 3.1.0, 4.2.0, or 4.3.0 you should be seeing a line on Q DASD DETAILS as follows: PPRC DETAILS: xxx VOLUME From the help file: --- The eighth line of the response, PPRC DETAILS, tells you the queried active Peer-to-Peer Remote Copy mode. In the above sample, xxx is one of the modes: o PRIMARY. The volume from which PPRC makes a copy. o SECONDARY. The volume that maintains a consistent copy of the primary volume. o CASCADING INTERMEDIATE. The volume that can be both a PPRC primary and secondary volume, allowing a multi-hop operation. In a multi-hop operation, PPRC uses a primary volume to send to a secondary volume and that secondary volume operates as a PPRC Extended Distance primary volume, sending to a tertiary volume many miles away. Such a configuration supports disaster recovery operations. If the queried DASD is not an active PPRC volume, the PPRC DETAILS line is not included in the response. --- The APAR went into the base product with z/VM 4.4.0. Regards, Steve. Steve Wilkins IBM z/VM Development Alan Altmark/Endicott/ [EMAIL PROTECTED] To Sent by: The IBM IBMVM@LISTSERV.UARK.EDU z/VM Operating cc System [EMAIL PROTECTED] Subject ARK.EDU Re: PPRC and R/W Minidisks 12/11/2006 05:28 PM Please respond to The IBM z/VM Operating System [EMAIL PROTECTED] ARK.EDU On Monday, 12/11/2006 at 02:12 PST, Judson West [EMAIL PROTECTED] wrote: 2nd somewhat related question, we are paring up both VM and MVS volumes. My MVS counterpart is doing the MVS volumes (under a z/OS partition), and I'm doing the VM ones. When I issue the CP Q DASD DETAILS command on a MVS volume known to VM, I get the following results: q dasd details 400 0400 CUTYPE = 3990-EC, DEVTYPE = 3390-0C, VOLSER = DSMP01, CYLS = 10017 CACHE DETAILS: CACHE NVS CFW DFW PINNED CONCOPY -SUBSYSTEM YY Y -N N -DEVICE Y- - YN N DEVICE DETAILS: CCA = 00, DDC = 00 DUPLEX DETAILS: -- When this volume is queried on MVS, it shows that it is the primary of a duplexed pair. Why doesn't VM show this information also? I believe that DUPLEX DETAILS is related to the older 3990 controller-based Duplex volume support, something different than Metro/Global Mirrors. Alan Altmark z/VM Development IBM Endicott
Re: RSCS LPR Printer Name w/spaces
Fran Hensler wrote: Does anyone know how I could either rename this printer to remove spaces or how to make RSCS print to printer name with embedded spaces. On Tue, 12 Dec 2006 12:14:37 -0500 David Boyes said: Have the machine that has access to the printer share it as a name that does not have spaces in it. The Windows LPD will honor shared names as well as the original name. David - Your solution works great. Thank you. /Fran Hensler at Slippery Rock University of Pennsylvania USA for 43 years [EMAIL PROTECTED] +1.724.738.2153 Yes, Virginia, there is a Slippery Rock
Re: RSCS LPR Printer Name w/spaces
Your solution works great. Thank you. You're welcome. Side note, though: that's an IPP-driven printer...8-) Remember to vote yes to add IPP support for RSCS in the next requirements go-round at your favorite user group.
When the CPU phones home....
This year's urgent question is, When the mainframe calls in a service problem to IBM, what data gets transmitted to IBM? Is this information published somewhere? I haven't even figure out who within our local IBM team I'd ask such a question of, but maybe IBM published the spec in case of auditors wanting to know that or something. Thanks, Nick ps -- yes, it's come up about three different times this year. I suspect it's the same provocateur each time, but this time, that itch is finally getting scratched.
Re: When the CPU phones home....
It sends different things depending upon what you have selected. If you have an HSC, most of the options for what it sends are set in there. If not, you can access the same screens from a service element. It can send a lot of information, but none of what it sends was important to our SOX auditors. Call 1-800-IBM-SERV and they can help you out pretty quickly with that issue. ---BeginMessage--- This year's urgent question is, When the mainframe calls in a service problem to IBM, what data gets transmitted to IBM? Is this information published somewhere? I haven't even figure out who within our local IBM team I'd ask such a question of, but maybe IBM published the spec in case of auditors wanting to know that or something. Thanks, Nick ps -- yes, it's come up about three different times this year. I suspect it's the same provocateur each time, but this time, that itch is finally getting scratched. ---End Message---
