Didn't seem worth it.  The scheme we use works fine, and didn't require
us to change PROFILE EXEC on 50-odd servers.  The package containing the
script was rolled out with a scheduled update on the Linux side.  The
directory changes could be scripted through VMSecure.

-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of
Adam Thornton
Sent: Friday, September 11, 2009 1:09 PM
To: [email protected]
Subject: Re: [LINUX-390] Dasd_diag_mod question

On Sep 11, 2009, at 12:02 PM, Hall, Ken (GTS) wrote:

> My complaint with SWAPGEN going back to when it was first announced
> was
> that it needs to know the number of blocks to format.  This means that
> if the size or number of the vdisk(s) changes in the directory, the VM
> admin also has to go to the target machine's 191 disk and update the
> PROFILE EXEC so the right number of blocks get formatted on the right
> devices.  Having to change things in multiple places seemed like
> something to be avoided.

Hm.

Did you ever send us a requirement for that?  If so, I apologize for
having missed it.

Since we already look for the number of blocks in the "reuse" code, I
think it should be pretty straightforward to do that check and then
use the number of blocks detected if the user doesn't specify.

Adam

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

--------------------------------------------------------------------------
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. 
References to "Merrill Lynch" are references to any company in the Merrill 
Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America 
Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are 
Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a 
Condition to Any Banking Service or Activity * Are Not Insured by Any Federal 
Government Agency. Attachments that are part of this E-communication may have 
additional important disclosures and disclaimers, which you should read. 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.
--------------------------------------------------------------------------
 

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to