Then, z/Linux is just reading a CP formatted area instead of CMS
formatted.  Both are 4K blocks.  Some z/Linux routines do not object,
but some do get nasty if the disks are not z/Linux formatted.  And just
not at IPL time, such as when the accounting routines are run or DASD
check routines.

        -----Original Message-----
        From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of RPN01
        Sent: Friday, November 30, 2007 10:59 AM
        To: [email protected]
        Subject: Re: Formatter for/Linux Minidisk from CMS
        
        
        Worst case, try formatting them with ICKDSF, just as you would a
z/VM paging or spooling volume. This may be more toward what the Linux
system wants than the CMS format. In any case, I really don't do either,
and have had no problems.
        
        -- 
           .~.    Robert P. Nix             Mayo Foundation 
          /V\    RO-OE-5-55              200 First Street SW 
         / ( ) \  507-284-0844           Rochester, MN 55905 
        ^^-^^   ----- 
        "In theory, theory and practice are the same, but     "Join the
story... Ride Ural."
        in practice, theory and practice are different." 
        
        
        
        
        On 11/30/07 9:55 AM, "Mike Walter" <[EMAIL PROTECTED]>
wrote:
        
        

                
                Responding to both Marcy and Bob's points, I give a
fresh MDISK to the Linux sysprog who says that he receives errors when
running dasdfmt unless CMS FORMAT has been run first.  We've been
formatting them with CMS for so long now that I can't recall the error. 
                
                But I'll add trying defining a new MDISK without a CMS
FORMAT and then adding it to a Linux guest and running dasdfmt to our
task list.  Maybe something changed since "a long time ago". 
                
                We never used the RESERVE command, either.  By Dave
suggesting it, there seems to be validation that a CMS format was
required at some point.  Maybe Linux used to need to see the disk label
(volser) on cyl 0 (rec 3 ? w/o looking) of the MDISK. 
                
                I'll let you know when we've tested again.  Thanks for
the tips. 
                
                Mike Walter 
                Hewitt Associates 
                Any opinions expressed herein are mine alone and do not
necessarily represent the opinions or policies of Hewitt Associates. 
                
                
                "Marcy Cortes" <[EMAIL PROTECTED]> 
                
                Sent by: "The IBM z/VM Operating System"
<[email protected]> 11/30/2007 09:38 AM 

                Please respond to
                "The IBM z/VM Operating System"
<[email protected]> 

                
                

                To 

                [email protected] 

                cc
                Subject 

                Re: Formatter for/Linux Minidisk from CMS 
                
                
                
                
                You don't need to.  We haven't been CMS formatting them.

                
                Marcy Cortes 
                
                "This message may contain confidential and/or privileged
information. If you are not the addressee or authorized to receive this
for the addressee, you must not use, copy, disclose, or take any action
based on this message or any information herein. If you have received
this message in error, please advise the sender immediately by reply
e-mail and delete this message. Thank you for your cooperation." 
                
                
                
                
  _____  

                From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter
                Sent: Friday, November 30, 2007 7:34 AM
                To: [email protected]
                Subject: Re: [IBMVM] Formatter for/Linux Minidisk from
CMS
                
                
                OK, time to show my Linux ignorance... 
                
                I've never understood why Linux needs CMS to format the
MDISK before Linux formats it.  What a waste of I/O's (even if z _does_
perform I/O VERY, VERY quickly!).  What a waste of time, and what a set
of cludgy processes. 
                
                What's the deal?  Why can't dasdfmt just format what
it's given without CMS having to "prep" it?  What would it take to
change dasdfmt to do so? 
                
                Mike Walter 
                Hewitt Associates 
                Any opinions expressed herein are mine alone and do not
necessarily represent the opinions or policies of Hewitt Associates. 
                
                
                "Stracka, James (GTI)" <[EMAIL PROTECTED]> 
                
                Sent by: "The IBM z/VM Operating System"
<[email protected]> 11/30/2007 08:57 AM 

                Please respond to
                "The IBM z/VM Operating System"
<[email protected]> 

                
                

                To 

                [email protected] 

                cc
                Subject 

                Re: Formatter forz/Linux Minidisk from CMS 
                
                
                
                
                
                
                Kludge yes, one pack; no.  Because of striping we would
need at least thirteen differently sized template minidisks.  Unless we
could format just one very large minidisk and image copy as little as
needed.  I believe CMS gets just a little bent out of shape if one did
this.  Would not z/Linux too?   
                -----Original Message-----
                From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Imler, Steven J
                Sent: Friday, November 30, 2007 9:46 AM
                To: [email protected]
                Subject: Re: Formatter forz/Linux Minidisk from CMS
                
                Kludgy workaround ... 
                  
                Can you "correctly" format one "template" pack ... then
use HiDRO DUPLICATE (or DDR) to clone the pack with the end result being
that the packs are pre-formatted for the z/Linux guests? 
                  
                JR (Steven) Imler 
                CA 
                Senior Software Engineer 
                Tel:  +1 703 708 3479 
                Fax:  +1 703 708 3267 
                [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
<mailto:[EMAIL PROTECTED]>  
                
                
  _____  

                From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Stracka, James (GTI)
                Sent: Friday, November 30, 2007 09:39 AM
                To: [email protected]
                Subject: Formatter forz/Linux Minidisk from CMS
                
                Does anyone have or know of a utility that will z/Linux
format a minidisk from CMS? 
                  
                We have a requirement to format many minidisks for
z/Linux usage.  Many z/Linux routines flood the console if we just give
the guests unformatted minidisks.  We have been CMS formatting them
before sending them to the z/Linux guests, where it might be days before
the owners z/Linux format them.  I would like to be able to z/Linux
format the minidisks from CMS before giving the disks to the guests. 
                
  _____  

                
                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/
<http://www.ml.com/e-communications_terms/>
<http://www.ml.com/e-communications_terms/>  . By messaging with Merrill
Lynch you consent to the foregoing. 
                
  _____  

                
                  
                
                
  _____  

                The information contained in this e-mail and any
accompanying documents may contain information that is confidential or
otherwise protected from disclosure. If you are not the intended
recipient of this message, or if this message has been addressed to you
in error, please immediately alert the sender by reply e-mail and then
delete this message, including any attachments. Any dissemination,
distribution or other use of the contents of this message by anyone
other than the intended recipient is strictly prohibited. All messages
sent to and from this e-mail address may be monitored as permitted by
applicable law and regulations to ensure compliance with our internal
policies and to protect our business. Emails are not secure and cannot
be guaranteed to be error free as they can be intercepted, amended, lost
or destroyed, or contain viruses. You are deemed to have accepted these
risks if you communicate with us by email. 
                
                
  _____  

                The information contained in this e-mail and any
accompanying documents may contain information that is confidential or
otherwise protected from disclosure. If you are not the intended
recipient of this message, or if this message has been addressed to you
in error, please immediately alert the sender by reply e-mail and then
delete this message, including any attachments. Any dissemination,
distribution or other use of the contents of this message by anyone
other than the intended recipient is strictly prohibited. All messages
sent to and from this e-mail address may be monitored as permitted by
applicable law and regulations to ensure compliance with our internal
policies and to protect our business. Emails are not secure and cannot
be guaranteed to be error free as they can be intercepted, amended, lost
or destroyed, or contain viruses. You are deemed to have accepted these
risks if you communicate with us by email. 
                
                

        
        

Reply via email to