Tom,

 

The most valuable suggestion in addition to the one on SMS manuals is the one 
found at the bottom of every note on this list:

 

Search the archives at http://bama.ua.edu/archives/ibm-main.html

 

We both know that topics about ACS routine coding have been discussed many 
times over. Tommy's post suggests a certain lack of understanding about SMS 
pooling concepts and capabilities. The archives cover a wealth of information.

 

Regardless, as I re-read Tommy's last post, I came to a different conclusion 
than before. It may be the wrong one, but here goes:

 

I believe what he is asking here, “if we plan to use SMS managed all volumes 
how can I distinct the STORAGE volumes” followed by his example, is the right 
question to ask but with the wrong example. It all depends on what he is trying 
to accomplish. 

 

When I converted non-SMS pools, I seem to recall using selection logic in the 
*Storage Class* routine to first differentiate between explicit dataset 
allocations (PRIVATE mounted), then temporary dataset allocations (generally a 
PUBLIC mounted pool) and finally as a catch-all, UNIT/Esoteric allocations 
using ANYVOL for *storage mounted* volumes. Exceptions to these rules were 
coded first, but then the logic flowed top to bottom from most explicit to most 
generic. For the most part, storage groups were only assigned by storage 
classes. The exceptions I mentioned were to allow some allocations to continue 
to proceed to their existing non-SMS pools until such time as you were ready to 
manage them.    

 

Does this post make sense? 

  

 

Bob

 

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Tom 
Marchant
Sent: Thursday, August 17, 2006 12:56 PM
To: [email protected]
Subject: Re: 轉寄: Re: How can the ACS r outine to bypass checking the storage 
volu me datasets?

 

On Thu, 17 Aug 2006 12:13:57 -0400, Richards.Bob 

<[EMAIL PROTECTED]> wrote:

 

>Timeout!

> 

>Before this gets into a "my way is the best way" thread, let's agree that

>Matthew would not actually convert to SMS that way. I thought he was

>merely mentioning a logical one for one concept. :-)

 

I think Tommy was asking how to tell which allocations would have gone to a 

STORAGE volume pre-SMS, so that he could assign a corresponding storage 

group.  Matthew suggested that he create a "STORWRK" storage group.  If 

that's how he would do it, that's fine (it's not my dog), but it doesn't answer 
the 

question of how to determine that a data set should be assigned to that 

storage group.

> 

>What *is* important in what Matthew wrote is that Tommy needs to do

>some more reading.

 

It does seem that he needs more reading.  I was merely offering "My 

preference" for him to consider.  I figured others might have other opinions to 

contribute.  When I first implemented SMS, I found the discussions here of 

different people's preferences to be very valuable. 
  
  
  
LEGAL DISCLAIMER 
The information transmitted is intended solely for the individual or entity to 
which it is addressed and may contain confidential and/or privileged material. 
Any review, retransmission, dissemination or other use of or taking action in 
reliance upon this information by persons or entities other than the intended 
recipient is prohibited. If you have received this email in error please 
contact the sender and delete the material from any computer. 
  
Seeing Beyond Money is a service mark of SunTrust Banks, Inc. 
[ST:XCL] 
 
 
 
 

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to