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 = MDK00001 > DMS4PD3400I Initializing ends for DDNAME = MDK00001 > DMS4PD3400I Initializing begins for DDNAME = MDK00002 > DMS4PD3400I Initializing ends for DDNAME = MDK00002 > 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 MDKnnnn 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.
