Anyone using Dirmaint with a z10?
We just installed a z10 processor this morning, and the Dirmaint satellite on it won¹t install a directory. The message I get says that there is no DIRECTORY statement which matches the serial and model number, and then has the serial and model in parens. OK, so I cut and paste the serial and model and copied it into a directory statement in Dirmaint (which actually matched what I had there, but hey, I wanted to be sure it was right). I tried direct again, and it still says the same thing. The old statement for our z9 was: DIRECTORY 0123 3390 54GRES 0123 025A7E-2094 GRIZZLY And I replaced it with the following for the z10: DIRECTORY 0123 3390 54GRES 0123 02B3E6-2097 GRIZZLY What small gem of wisdom am I missing here? -- Robert P. Nix Mayo Foundation.~. RO-OC-1-18 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different.
Re: VARY command update?
... and good stuff too from Melinda Varian and others on the Distribution Page ... http://vm.marist.edu/~pipeline/ http://vm.marist.edu/~pipeline/#MWV
Re: Anyone using Dirmaint with a z10?
You've got the model from Q CPUID? (a z10 BC is a 2098, an EC is a 2097) No hex 41 somewhere? SET OUTPUT 41 _ can make those visible. The DIRMSAT has no CPUID statement in its directory entry? So CP FOR DIRMSAT CMD Q CPUID can help. 2011/3/20 RPN01 nix.rob...@mayo.edu We just installed a z10 processor this morning, and the Dirmaint satellite on it won’t install a directory. The message I get says that there is no DIRECTORY statement which matches the serial and model number, and then has the serial and model in parens. OK, so I cut and paste the serial and model and copied it into a directory statement in Dirmaint (which actually matched what I had there, but hey, I wanted to be sure it was right). I tried direct again, and it still says the same thing. The old statement for our z9 was: DIRECTORY 0123 3390 54GRES 0123 025A7E-2094 GRIZZLY And I replaced it with the following for the z10: DIRECTORY 0123 3390 54GRES 0123 02B3E6-2097 GRIZZLY What small gem of wisdom am I missing here? -- Robert P. Nix Mayo Foundation.~. RO-OC-1-18 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. -- Kris Buelens, IBM Belgium, VM customer support
Re: Anyone using Dirmaint with a z10?
I recall using SET CPUID (command or directory) to make yourself immune to the system CPUID changing.. - Set the DIRMAINT guests (DIRMAINT/DIRMSAT/DATAMOVE) to a simple CPUID number (e.g. 1) - Use the CPUID in the directory (1) - Use different numbers if you need to distinguish between systems (2, etc) -- DIRMSAT machines only -- everyone else can stay 1 in the complex. I tried this a long time ago and it worked fine - but others were uncomfortable with 'hiding' the real CPUID... I can't recall the objections now. You can also play games with CPUID to make SYSTEM NETID immune .. (1 is always MYVM1, 2 is MYVM2, etc). I think setting CPUID (making it truly virtual) can be a useful method in the right circumstances (sorry - perhaps not germane to Robert's problem (though it may be a future strategy?) - but Kris's comment on the CPUID got me thinking about it again) Scott Rohling On Sun, Mar 20, 2011 at 7:02 AM, Kris Buelens kris.buel...@gmail.comwrote: You've got the model from Q CPUID? (a z10 BC is a 2098, an EC is a 2097) No hex 41 somewhere? SET OUTPUT 41 _ can make those visible. The DIRMSAT has no CPUID statement in its directory entry? So CP FOR DIRMSAT CMD Q CPUID can help. 2011/3/20 RPN01 nix.rob...@mayo.edu We just installed a z10 processor this morning, and the Dirmaint satellite on it won’t install a directory. The message I get says that there is no DIRECTORY statement which matches the serial and model number, and then has the serial and model in parens. OK, so I cut and paste the serial and model and copied it into a directory statement in Dirmaint (which actually matched what I had there, but hey, I wanted to be sure it was right). I tried direct again, and it still says the same thing. The old statement for our z9 was: DIRECTORY 0123 3390 54GRES 0123 025A7E-2094 GRIZZLY And I replaced it with the following for the z10: DIRECTORY 0123 3390 54GRES 0123 02B3E6-2097 GRIZZLY What small gem of wisdom am I missing here? -- Robert P. Nix Mayo Foundation.~. RO-OC-1-18 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. -- Kris Buelens, IBM Belgium, VM customer support
Re: Anyone using Dirmaint with a z10?
On Sunday, 03/20/2011 at 05:53 EDT, RPN01 nix.rob...@mayo.edu wrote: We just installed a z10 processor this morning, and the Dirmaint satellite on it won?t install a directory. The message I get says that there is no DIRECTORY statement which matches the serial and model number, and then has the serial and model in parens. OK, so I cut and paste the serial and model and copied it into a directory statement in Dirmaint (which actually matched what I had there, but hey, I wanted to be sure it was right). I tried direct again, and it still says the same thing. The old statement for our z9 was: DIRECTORY 0123 3390 54GRES 0123 025A7E-2094 GRIZZLY And I replaced it with the following for the z10: DIRECTORY 0123 3390 54GRES 0123 02B3E6-2097 GRIZZLY What small gem of wisdom am I missing here? My guess is that you forgot to turn off minidisk cache for the shared disks on the satellite system and you're not seeing the directory update. I had that problem a couple of weeks ago. I couldn't figure it out until I linked to the DIRMAINT 1DF on the satellite system and noticed that the file content didn't match the primary system. (slap forehead) I suggested to one of the developers that satellites should turn off MDC for all config and db disks if their partner DIRMAINT server is on a different system. Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott
Re: Temp SFS environment
The work space is not allocated the same way if control and logs have many blocks defined or not. I did several tests to suit my needs and i remarked that dasd pages could be used or (vs. Memory) not depending of what coded in the pooldef file. That seems normal anyway to me and glad to see that this resolves my need. Alain Envoyé de mon iPhone Le 17 mars 2011 à 20:23, Gentry, Stephen stephen.gen...@lafayettelife.com a écrit : Wasn't the original poster trying to do this with virtual disk(s)? And if that's the case it has a high potential of being in memory anyway? Or did I miss something. Steve -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of David Boyes Sent: Thursday, March 17, 2011 2:51 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Temp SFS environment All that brings a subsidiary question : is it important to preserve the machine xc in the VMSERVx directories (I should read the doc I think...) ? You need the XC mode setting if you want SFS to use VM dataspaces to map parts of the data into memory (which would be consistent with the errors you saw) for performance reasons. It works fine without it (as you've seen), but performance will be impaired with very heavily loaded SFS servers.
