Mike,

 

Thank you for the advice.

 

We have the DIRMAP and the DISKMAP for the proper functions of the directory and I am using this EXEC only for facilities to consolidate disk space.

 

Regards.

 

Nelson Freitas

 


De: Mike Walter [mailto:[EMAIL PROTECTED]
Enviada em: quinta-feira, 27 de outubro de 2005 20:14
Para: [email protected]
Assunto: Re: RES: DASD map tool?

 


Nelson,

WARNING!  That's a terrific tool (it actually looks like an off-shoot from the a sample in: HELP PIPE JUXTAPOSE).
But it does not show gaps into which you can allocate new minidisks.

But most importantly of all, IT DOES NOT WARN ABOUT MINIDISK OVERLAPS!!!

You probably won't care about minidisk overlaps until you create one.  Then you'll care a LOT!  :-(
Do your users and yourself a favor... use the DIRMAP and/or DISKMAP commands.

Mike Walter

Hewitt Associates
The opinions expressed herein are mine alone, not my employer's.


"FREITAS Nelson Ivo" <[EMAIL PROTECTED]>

Sent by: "VM/ESA and z/VM Discussions" <[email protected]>

10/27/2005 04:38 PM

Please respond to
"VM/ESA and z/VM Discussions" <[email protected]>

To

[email protected]

cc

 

Subject

RES: DASD map tool?

 

 

 




We are using the EXEC below to do this.
We are using has many years ago and I do not remember who is its author
 
/* MDISK exec */
  'PIPE (ENDCHAR ?) | < USER DIRECT * |',    
    'L: CASEI NLOCATE 1.72 "MDISK "|',          
    'FIND USER_|',                              
    'SPECS W2 1.8 ": " N |',                    
    'J: JUXTAPOSE |',
    '> MDISK MAP A',                            
    '? L: |',                                  
    'SPECS W1.7 1 |',                          
    'J:'                                        
 
USER DIRECT is the input file and the output file is MDISK MAP A
 
The output file is:
$ALLOC$ : MDISK A01 3390 000 001 SYSRES R          
$DIRECT$: MDISK A04 3390 001 017 SYSRES R          
$SYSCKP$: MDISK A06 3390 021 004 SYSRES R          
$SYSWRM$: MDISK A07 3390 025 004 SYSRES R          
$PAGE$  : MDISK A03 3390 194  084 SYSRES R        
$PAGE$  : MDISK A05 3390 2922 108 SYSPK1 R        
$SPOOL$ : MDISK B01 3390  079 115 SYSRES R        
$SPOOL$ : MDISK B02 3390 3030 100 SYSPK1 R        
$SPOOL$ : MDISK B03 3390 3268 053 SYSPK1 R        
$SPOOL$ : MDISK B04 3390 000 2338 SYSISP R        
$T-DISK$: MDISK B01 3390 029 050 SYSRES R          
LGLOPR  : MDISK 191 3390 2387 001 SYSRES MR        
MAINT   : MDISK CF1 3390 278 017 SYSRES MR        
MAINT   : MDISK CF2 3390 295 017 SYSRES MR        
MAINT   : MDISK 190 3390 312 107 SYSRES MR        
MAINT   : MDISK 2C2 3390 419 005 SYSRES MR        
MAINT   : MDISK 490 3390 424 107 SYSRES MR        
MAINT   : MDISK 123 3390 000 END SYSRES MR        
MAINT   : MDISK 124 3390 000 END SYSPK1 MR        
MAINT   : MDISK 2D2 3390 1057 105 SYSRES MR        
MAINT   : MDISK 3B2 3390 1162 131 SYSRES MR        
 
Best regards.
 
Nelson Freitas.
 

 



De: Clark, Carl [mailto:[EMAIL PROTECTED]
Enviada em:
quinta-feira, 27 de outubro de 2005 17:31
Para:
[email protected]
Assunto:
DASD map tool?

 

VM enthusiasts:

   Thanks for all the answers about saving CMS for the 2nd Level system.  Now a different issue has arisen.  How may I determine exactly which minidisks are on a particular real DASD volume?

q 5629
DASD 5629 CP OWNED  510RES   109
Ready; T=0.01/0.01 15:30:31

I understand that many minidisks are defined to this volume, is there a tool that will map all the mdisks for a particular volume?

Your help is appreciated,
Carl Clark

BCBST

Please see the following link for the BlueCross BlueShield of Tennessee E-mail
disclaimer:  http://www.bcbst.com/email_disclaimer.shtm


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.

Reply via email to