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.
Re: Temp SFS environment
Scott My VM is used as hypervisor for DR needs and defined with minimal dasd. I was looking for a way to transfer big files without adding perm or temp dasd space and avoid to increase time of backup... And we are waiting for a new dasd array coming in end of may. All the rest of free space is used to migrate 3380 to 3390. Alain Envoyé de mon iPhone Le 16 mars 2011 à 23:12, Wandschneider, Scott scott.wandschnei...@infocrossing.com a écrit : My curious mind wants me to ask. . . Why would you want a temporary SFS Directory in memory? Thank you, Scott -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Alain Benveniste Sent: Wednesday, March 16, 2011 5:01 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Temp SFS environment Hi, I tried to create a Temp SFS environment in using FB-512 VDSK. Part of my directory looks like this: MDISK 0191 3390 11 1 VM0HVF MR MDISK 0301 FB-512 V-DISK 64000 MDISK 0302 FB-512 V-DISK 64000 MDISK 0303 FB-512 V-DISK 64000 MDISK 0304 FB-512 V-DISK 64000 MDISK 0305 FB-512 V-DISK 64000 The fileserv generate command works perfectly but when I do a fileserv st= art I get: DMSWFV1117I FILESERV processing begun at 22:55:02 on 16 Mar 2011 DMSWFV1121I SFS DMSPARMS A1 will be used for FILESERV processing DMS4PD3400I Initializing begins for DDNAME = CONTROL DMS4PD3400I Initializing ends for DDNAME = CONTROL DMS4PD3400I Initializing begins for DDNAME = MDK1 DMS4PD3400I Initializing ends for DDNAME = MDK1 DMS4PD3400I Initializing begins for DDNAME = MDK2 DMS4PD3400I Initializing ends for DDNAME = MDK2 DMS4PG3404W File pool limit of 2 minidisks has been reached DMS4PD3400I Initializing begins for DDNAME = LOG1 DMS4PD3400I Initializing ends for DDNAME = LOG1 DMS4PD3400I Initializing begins for DDNAME = LOG2 DMS4PD3400I Initializing ends for DDNAME = LOG2 DMS5FD3032I File pool server has terminated DMSWFV1120I File SFS POOLDEF A1 created or replaced DMSWFV1117I FILESERV processing ended at 22:55:52 on 16 Mar 2011 DMSWFV1117I FILESERV processing begun at 22:55:52 on 16 Mar 2011 DMSWFV1121I SFS DMSPARMS A1 will be used for FILESERV processing DMSWFV1121I SFS POOLDEF A1 will be used for FILESERV processing DMS5FE3040E File pool server system error occurred - DMS4FK 02 DMS3040E File pool server system error occurred - modulename nn Explanation: An internal error occurred within the file pool server. A du= mp is taken according to the dump option chosen in the server startup parameter= s. This is a system error. The modulename is the name of the module that detected the error. The nn is the error detection point within the module. The modulename nn is intended only for service personnel. What modulename 02 means ? Fileserv works fine when the MDK are 'normal' mdisk but not when they= are defined as temp... Is it just possible to do that ? Alain Confidentiality Note: This e-mail, including any attachment to it, may contain material that is confidential, proprietary, privileged and/or Protected Health Information, within the meaning of the regulations under the Health Insurance Portability Accountability Act as amended. If it is not clear that you are the intended recipient, you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this e-mail, including any attachment to it, is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system. Thank you.
Re: Temp SFS environment
Thank you for sharing your reasoning. Makes sense to me. Thank you, Scott -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Alain Benveniste Sent: Thursday, March 17, 2011 1:47 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Temp SFS environment Scott My VM is used as hypervisor for DR needs and defined with minimal dasd. I was looking for a way to transfer big files without adding perm or temp dasd space and avoid to increase time of backup... And we are waiting for a new dasd array coming in end of may. All the rest of free space is used to migrate 3380 to 3390. Alain Envoyé de mon iPhone Le 16 mars 2011 à 23:12, Wandschneider, Scott scott.wandschnei...@infocrossing.com a écrit : My curious mind wants me to ask. . . Why would you want a temporary SFS Directory in memory? Thank you, Scott -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Alain Benveniste Sent: Wednesday, March 16, 2011 5:01 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Temp SFS environment Hi, I tried to create a Temp SFS environment in using FB-512 VDSK. Part of my directory looks like this: MDISK 0191 3390 11 1 VM0HVF MR MDISK 0301 FB-512 V-DISK 64000 MDISK 0302 FB-512 V-DISK 64000 MDISK 0303 FB-512 V-DISK 64000 MDISK 0304 FB-512 V-DISK 64000 MDISK 0305 FB-512 V-DISK 64000 The fileserv generate command works perfectly but when I do a fileserv st= art I get: DMSWFV1117I FILESERV processing begun at 22:55:02 on 16 Mar 2011 DMSWFV1121I SFS DMSPARMS A1 will be used for FILESERV processing DMS4PD3400I Initializing begins for DDNAME = CONTROL DMS4PD3400I Initializing ends for DDNAME = CONTROL DMS4PD3400I Initializing begins for DDNAME = MDK1 DMS4PD3400I Initializing ends for DDNAME = MDK1 DMS4PD3400I Initializing begins for DDNAME = MDK2 DMS4PD3400I Initializing ends for DDNAME = MDK2 DMS4PG3404W File pool limit of 2 minidisks has been reached DMS4PD3400I Initializing begins for DDNAME = LOG1 DMS4PD3400I Initializing ends for DDNAME = LOG1 DMS4PD3400I Initializing begins for DDNAME = LOG2 DMS4PD3400I Initializing ends for DDNAME = LOG2 DMS5FD3032I File pool server has terminated DMSWFV1120I File SFS POOLDEF A1 created or replaced DMSWFV1117I FILESERV processing ended at 22:55:52 on 16 Mar 2011 DMSWFV1117I FILESERV processing begun at 22:55:52 on 16 Mar 2011 DMSWFV1121I SFS DMSPARMS A1 will be used for FILESERV processing DMSWFV1121I SFS POOLDEF A1 will be used for FILESERV processing DMS5FE3040E File pool server system error occurred - DMS4FK 02 DMS3040E File pool server system error occurred - modulename nn Explanation: An internal error occurred within the file pool server. A du= mp is taken according to the dump option chosen in the server startup parameter= s. This is a system error. The modulename is the name of the module that detected the error. The nn is the error detection point within the module. The modulename nn is intended only for service personnel. What modulename 02 means ? Fileserv works fine when the MDK are 'normal' mdisk but not when they= are defined as temp... Is it just possible to do that ? Alain Confidentiality Note: This e-mail, including any attachment to it, may contain material that is confidential, proprietary, privileged and/or Protected Health Information, within the meaning of the regulations under the Health Insurance Portability Accountability Act as amended. If it is not clear that you are the intended recipient, you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this e-mail, including any attachment to it, is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system. Thank you. Confidentiality Note: This e-mail, including any attachment to it, may contain material that is confidential, proprietary, privileged and/or Protected Health Information, within the meaning of the regulations under the Health Insurance Portability Accountability Act as amended. If it is not clear that you are the intended recipient, you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this e-mail, including any attachment to it, is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system. Thank you.
Re: Temp SFS environment
I don't know about detach, but re-link definitely happens. File pool minidisks can be defined in the directory with linkmode R and they still become linked R/W when the server starts and remain R/W after the server terminates. Ivica Brodaric BNZ
Re: Temp SFS environment
V-disks stay around until the last user releases them, so could you have them linked read-only by a second user as well to keep them alive until you¹re done with them? -- 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. On 3/17/11 8:43 AM, Ivica Brodaric ivica.broda...@gmail.com wrote: I don't know about detach, but re-link definitely happens. File pool minidisks can be defined in the directory with linkmode R and they still become linked R/W when the server starts and remain R/W after the server terminates. Ivica Brodaric BNZ
Re: Temp SFS environment
Feedback: Reading Alan¹s answer, I thought to be unlucky,I changed my point of view in making some tests by defining my MDISK 301 to 305 as 3390 T-DISK. I fall in what Simon talked about : fileserv generate cmd didn¹t see the tdisk and ask me to link them... More ugly than my previous tests. I decided to freely supersede¹ Alan¹s directives to go back with my v-disk and check again the directory... and I got a idea. I had copied a VMSERVx directory to create my own SFS user. VMSERVx come with a MACHINE XC definition. I removed that line. And it works ! I am ready for communication¹. I don¹t say I will not have problems later but I think to be on the good way. 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...) ? Thanks to all Alain
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.
Re: Temp SFS environment
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.
Re: Temp SFS environment
With Dataspaces, the SFS end-user can directly read the CMS file data, without APPC communication to the SFS server. Only at ACCESS time, the end-user of a dataspaced DIRC must talk to the SFS server. 2011/3/17 Gentry, Stephen stephen.gen...@lafayettelife.com 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. -- Kris Buelens, IBM Belgium, VM customer support
Re: Temp SFS environment
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 In this case, it probably doesn't matter at all, but that's the reason the XC mode setting is in the VMSERVx directory entries. There's probably some coding advantages to be able to just flip over to another address space and directly read or write a page, but I doubt it matters nearly as much as it used to.
Temp SFS environment
Hi, I tried to create a Temp SFS environment in using FB-512 VDSK. Part of my directory looks like this: MDISK 0191 3390 11 1 VM0HVF MR MDISK 0301 FB-512 V-DISK 64000 MDISK 0302 FB-512 V-DISK 64000 MDISK 0303 FB-512 V-DISK 64000 MDISK 0304 FB-512 V-DISK 64000 MDISK 0305 FB-512 V-DISK 64000 The fileserv generate command works perfectly but when I do a fileserv st art I get: DMSWFV1117I FILESERV processing begun at 22:55:02 on 16 Mar 2011 DMSWFV1121I SFS DMSPARMS A1 will be used for FILESERV processing DMS4PD3400I Initializing begins for DDNAME = CONTROL DMS4PD3400I Initializing ends for DDNAME = CONTROL DMS4PD3400I Initializing begins for DDNAME = MDK1 DMS4PD3400I Initializing ends for DDNAME = MDK1 DMS4PD3400I Initializing begins for DDNAME = MDK2 DMS4PD3400I Initializing ends for DDNAME = MDK2 DMS4PG3404W File pool limit of 2 minidisks has been reached DMS4PD3400I Initializing begins for DDNAME = LOG1 DMS4PD3400I Initializing ends for DDNAME = LOG1 DMS4PD3400I Initializing begins for DDNAME = LOG2 DMS4PD3400I Initializing ends for DDNAME = LOG2 DMS5FD3032I File pool server has terminated DMSWFV1120I File SFS POOLDEF A1 created or replaced DMSWFV1117I FILESERV processing ended at 22:55:52 on 16 Mar 2011 DMSWFV1117I FILESERV processing begun at 22:55:52 on 16 Mar 2011 DMSWFV1121I SFS DMSPARMS A1 will be used for FILESERV processing DMSWFV1121I SFS POOLDEF A1 will be used for FILESERV processing DMS5FE3040E File pool server system error occurred - DMS4FK 02 DMS3040E File pool server system error occurred - modulename nn Explanation: An internal error occurred within the file pool server. A du mp is taken according to the dump option chosen in the server startup parameter s. This is a system error. The modulename is the name of the module that detected the error. The nn is the error detection point within the module. The modulename nn is intended only for service personnel. What modulename 02 means ? Fileserv works fine when the MDK are 'normal' mdisk but not when they are defined as temp... Is it just possible to do that ? Alain
Re: Temp SFS environment
My curious mind wants me to ask. . . Why would you want a temporary SFS Directory in memory? Thank you, Scott -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Alain Benveniste Sent: Wednesday, March 16, 2011 5:01 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Temp SFS environment Hi, I tried to create a Temp SFS environment in using FB-512 VDSK. Part of my directory looks like this: MDISK 0191 3390 11 1 VM0HVF MR MDISK 0301 FB-512 V-DISK 64000 MDISK 0302 FB-512 V-DISK 64000 MDISK 0303 FB-512 V-DISK 64000 MDISK 0304 FB-512 V-DISK 64000 MDISK 0305 FB-512 V-DISK 64000 The fileserv generate command works perfectly but when I do a fileserv st= art I get: DMSWFV1117I FILESERV processing begun at 22:55:02 on 16 Mar 2011 DMSWFV1121I SFS DMSPARMS A1 will be used for FILESERV processing DMS4PD3400I Initializing begins for DDNAME = CONTROL DMS4PD3400I Initializing ends for DDNAME = CONTROL DMS4PD3400I Initializing begins for DDNAME = MDK1 DMS4PD3400I Initializing ends for DDNAME = MDK1 DMS4PD3400I Initializing begins for DDNAME = MDK2 DMS4PD3400I Initializing ends for DDNAME = MDK2 DMS4PG3404W File pool limit of 2 minidisks has been reached DMS4PD3400I Initializing begins for DDNAME = LOG1 DMS4PD3400I Initializing ends for DDNAME = LOG1 DMS4PD3400I Initializing begins for DDNAME = LOG2 DMS4PD3400I Initializing ends for DDNAME = LOG2 DMS5FD3032I File pool server has terminated DMSWFV1120I File SFS POOLDEF A1 created or replaced DMSWFV1117I FILESERV processing ended at 22:55:52 on 16 Mar 2011 DMSWFV1117I FILESERV processing begun at 22:55:52 on 16 Mar 2011 DMSWFV1121I SFS DMSPARMS A1 will be used for FILESERV processing DMSWFV1121I SFS POOLDEF A1 will be used for FILESERV processing DMS5FE3040E File pool server system error occurred - DMS4FK 02 DMS3040E File pool server system error occurred - modulename nn Explanation: An internal error occurred within the file pool server. A du= mp is taken according to the dump option chosen in the server startup parameter= s. This is a system error. The modulename is the name of the module that detected the error. The nn is the error detection point within the module. The modulename nn is intended only for service personnel. What modulename 02 means ? Fileserv works fine when the MDK are 'normal' mdisk but not when they= are defined as temp... Is it just possible to do that ? Alain Confidentiality Note: This e-mail, including any attachment to it, may contain material that is confidential, proprietary, privileged and/or Protected Health Information, within the meaning of the regulations under the Health Insurance Portability Accountability Act as amended. If it is not clear that you are the intended recipient, you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this e-mail, including any attachment to it, is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system. Thank you.
Re: Temp SFS environment
On Wednesday, 03/16/2011 at 06:01 EDT, Alain Benveniste a.benveni...@free.fr wrote: DMS5FE3040E File pool server system error occurred - DMS4FK 02 That error code indicates a failure of the MAPMDISK IDENTIFY function (see CP Programming Services), and the likely candidate error is V-DISK not supported. I think you should be able to use T-disk, however. 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
I am not sure about this, but I think it might be that the mdisks get detached and re-linked, which would kill your SFS server if they were TDISK. See what response you get to: #cp q v 301-305 immediately after the failure. The reason I think I remember this is that years ago I once tried to define the mdisks as slightly different addresses than the ones in the CP directory (#CP DEF B301 301), and ran into problems. IIRC the server wanted to be able to LINK to the addresses I had given it. Shimon On Thu, Mar 17, 2011 at 12:01 AM, Alain Benveniste a.benveni...@free.frwrote: Hi, I tried to create a Temp SFS environment in using FB-512 VDSK. Part of my directory looks like this: MDISK 0191 3390 11 1 VM0HVF MR MDISK 0301 FB-512 V-DISK 64000 MDISK 0302 FB-512 V-DISK 64000 MDISK 0303 FB-512 V-DISK 64000 MDISK 0304 FB-512 V-DISK 64000 MDISK 0305 FB-512 V-DISK 64000 The fileserv generate command works perfectly but when I do a fileserv st art I get: DMSWFV1117I FILESERV processing begun at 22:55:02 on 16 Mar 2011 DMSWFV1121I SFS DMSPARMS A1 will be used for FILESERV processing DMS4PD3400I Initializing begins for DDNAME = CONTROL DMS4PD3400I Initializing ends for DDNAME = CONTROL DMS4PD3400I Initializing begins for DDNAME = MDK1 DMS4PD3400I Initializing ends for DDNAME = MDK1 DMS4PD3400I Initializing begins for DDNAME = MDK2 DMS4PD3400I Initializing ends for DDNAME = MDK2 DMS4PG3404W File pool limit of 2 minidisks has been reached DMS4PD3400I Initializing begins for DDNAME = LOG1 DMS4PD3400I Initializing ends for DDNAME = LOG1 DMS4PD3400I Initializing begins for DDNAME = LOG2 DMS4PD3400I Initializing ends for DDNAME = LOG2 DMS5FD3032I File pool server has terminated DMSWFV1120I File SFS POOLDEF A1 created or replaced DMSWFV1117I FILESERV processing ended at 22:55:52 on 16 Mar 2011 DMSWFV1117I FILESERV processing begun at 22:55:52 on 16 Mar 2011 DMSWFV1121I SFS DMSPARMS A1 will be used for FILESERV processing DMSWFV1121I SFS POOLDEF A1 will be used for FILESERV processing DMS5FE3040E File pool server system error occurred - DMS4FK 02 DMS3040E File pool server system error occurred - modulename nn Explanation: An internal error occurred within the file pool server. A du mp is taken according to the dump option chosen in the server startup parameter s. This is a system error. The modulename is the name of the module that detected the error. The nn is the error detection point within the module. The modulename nn is intended only for service personnel. What modulename 02 means ? Fileserv works fine when the MDK are 'normal' mdisk but not when they are defined as temp... Is it just possible to do that ? Alain
