While I thought having the SFS SVM itself XC, you are saying general CMS users should be XC too?
-----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of David Kreuter Sent: Friday, June 15, 2007 10:37 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Slight OT -> Re: Y-disk housekeeping using SFS. XC mode is for those users that need to access SFS files from dataspaces. XC mode lets DAT off users reach out to a dataspace, which is actually a virtual storage system. SFSes that exploit dataspaces are for dircontrol directories. David -----Original Message----- From: The IBM z/VM Operating System on behalf of [EMAIL PROTECTED] Sent: Fri 6/15/2007 9:33 AM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] Slight OT -> Re: Y-disk housekeeping using SFS. Are you saying that a user who uses SFS should have their machine set to XC? For example, we set up a lot of users to use SFS as their A disk; IPL CMS from VMSYSU, stuff like that. Thanks, Steve G. Kris Buelens <[EMAIL PROTECTED]> Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> 06/14/2007 04:09 PM Please respond to The IBM z/VM Operating System To: IBMVM@LISTSERV.UARK.EDU cc: Subject: Re: Y-disk housekeeping using SFS. . . . . Make sure your end-users run with MACHINE XC, so their CMS can directly read the files from the dataspace, (without the need for data transfer from the SFS server over APPC). Non-XC users can still benefit from the dataspace, but will need some extra help from CP to have the file data copied from the dataspace into their primary address space. I would think that a "dataspaced" directory can outperform the classic 19E-minidisk: the Y disk profits of shared FSTs; a dataspace directory has shared FSTs and shared data. My customer stores its application programs in an SFS dataspace and we use the DLOR to cleanup. It works perfectly weel, except for SAS: SAS used parameters on the CSL calls to instruct SFS not to update the DOLR. We had SAS create a fix for this (and some SFS backups needed to be restored ...) Beware too for "special tools": my customer uses my LOOK tool to scan files for strings. Without precautions such tools will set all DOLRs to the date someone searched... My LOOK has since been updated to avoid that (no, I don't think it is on VM's download lib, but I can send it). Similar, a simple BROWSE when one is curious will update the DOLR. So, we have a PIEK EXEC that avoids this (in Dutch "piek" is pronounced exactly like the English "peek"). As James writes: SFS will not hide fm0 files. Furthermore I would not be surprised if an "ACCESS dirid Y/S * * Y2" would make that no dataspace is used (the SFS server constructs a dataspace to be shared by all end-users, and this form of ACCESS would ask for a filtered access). Q SPACES PERMITTED following the ACCESS can tell you. -- Kris Buelens, IBM Belgium, VM customer support -------------------------------------------------------- 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. --------------------------------------------------------
