|
View previous topic :: View next topic
|
| Author |
Message |
karthikr44
Active User
Joined: 25 Aug 2007
Posts: 235
Location: Chennai
|
|
|
|
Hi All,
I have seen one of our JCL being coded as
| Code: |
DEFINE CLUSTER (NAME(TEST.CLUSTER) -
INDEXED -
KEYS(11 0) -
RECORDSIZE(250 250) -
SPEED -
SHAREOPTIONS(2 3)) -
DATA (NAME(TEST.DATA) -
CYL(600 250) -
VOLUMES(*,*,*,*,*,*,*,*) -
|
Here I am not sure,why it is coded as *,*,*,* for VOLUMES parameter.
Anyone has idea about this.Kindly share ur thoughts.
Thanks
R KARTHIK |
|
| Back to top |
|
 |
PeterHolland
Global Moderator
Joined: 27 Oct 2009
Posts: 2481
Location: Netherlands, Amstelveen
|
|
|
|
| You can let SMS choose the volumes for SMS-managed data sets by coding an * for the volser with the VOLUMES parameter. If both user-specified and SMS-specified volumes are requested, the user-specified volser must be input first in the command syntax. The default is one volume. |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
Peter,
thanks for sharing your consolidated knowledge with us.
saved me a lot of time looking at manuals. |
|
| Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009
Posts: 2481
Location: Netherlands, Amstelveen
|
|
|
|
| Any time, Dick. |
|
| Back to top |
|
|
karthikr44
Active User
Joined: 25 Aug 2007
Posts: 235
Location: Chennai
|
|
|
|
| Thanks peter for sharing ur knowledge.... |
|
| Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009
Posts: 2481
Location: Netherlands, Amstelveen
|
|
|
|
karthikr44,
any time |
|
| Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009
Posts: 582
Location: London
|
|
|
|
If they're SMS managed datasets then it will assign a 'canidate' volume for each * specified.
The first volser that the dataset is actually allocated on becomes a prime volume (a real volume), and as the dataset needs to extend to another volume another of the candidate volumes is changed to become a prime volume. You can also later do an IDCAMS ADDVOLUMES to add more candidate volumes if necessary.
Candidate volumes can also be defined by the Dataclas assigned to the dataset via its Initial or Dynamic volume count settings.
NOTE: If the dataset is NONSMS and it is VSAM the define will fail unless some other OEM allocation product like ProSMS or CA-Alllocate deals with it. If it is NONVSAM it may successfully allocate if there is some volumes mounted as STORAGE amd an EDT (Eligible Device Table) is defined that includes the addresses of the Storage mounted volumes. |
|
| Back to top |
|
|
|
|
