Multiple volume allocations are required when a data set allocation is expected to consume more space than, which is available on a single volume. Review this topic to understand how to enable multiple volume/extent support when using non-SMS- or SMS-managed allocations.
SMS automatically manages storage-space related issues. However, you may encounter situations where SMS is not an option. Adequately addressing your storage needs before configuration can ensure that you complete the procedure without SB37/SD37/SE37 abends.
Important! This topic applies to Automatic Configuration users. CA CSM does not support multiple volume designations.
If the space is insufficient on a data set allocation, request more volume serials. For example, code VOLUME=SER=(ser1,ser2,ser3) to request three volume serials on the specified device.
Use non-SMS for the following cases:
If the space is insufficient on a data set allocation, request more units. For example, replace UNIT=3390 with UNIT=(3390,2) to request two units on specified STORCLAS.
Example Use Cases
You have installed and deployed CA Chorus. Before you configure the product, you want to understand how to configure multiple volumes using non-SMS and/or multiple SMS extents. In both cases, you are increasing the volumes to help with a database backup.
If you are using non-SMS and to allocate a large format dataset to three multiple volumes, replace it with VOL=SER=(DASD01,DASD02,DASD03). In the following sample, the bold text indicates the change location within the Auto Configuration CONFIG.DATA file.
//*RT_UNIT - DASD storage UNIT type for new datasets //* Special characters must be enclosed in apostrophes. //* If you are using SMS values for the SET RT_DD_STORAGE keyword, //* leave this value as the default (3390). //* DFSMS overrides the UNIT keyword automatically with the UNIT //* that the SMS volume needs. // SET RT_UNIT='UNIT=3390' //*SET RT_UNIT='UNIT=(3390,n)' //* //*RT_VOLUME - DASD volume for non-SMS allocations // SET RT_VOLUME='VOLUME' //*SET RT_VOLUME='(VOLUME1,VOLUME2,VOLUME3)' //* //*RT_VOLSER - DASD VOL=SER number for new datasets: non-SMS allocations //* Note: //* a. Special characters must be enclosed in apostrophes. //* b. For SMS allocations, this symbol can be left as-is. // SET RT_VOLSER='VOL=SER=@RT_VOLUME@'
In the following sample, the bold text indicates the change location within the Auto Configuration CONFIG.DATA file to use SMS extents.
//*RT_UNIT - DASD storage UNIT type for new datasets //* Special characters must be enclosed in apostrophes. //* If you are using SMS values for the SET RT_DD_STORAGE keyword, //* leave this value as the default (3390). //* DFSMS overrides the UNIT keyword automatically with the UNIT //* that the SMS volume needs. // SET RT_UNIT='UNIT=3390' //*SET RT_UNIT='UNIT=(3390,n)' //* //*RT_VOLUME - DASD volume for non-SMS allocations // SET RT_VOLUME='VOLUME' //* //*RT_VOLSER - DASD VOL=SER number for new datasets: non-SMS allocations //* Note: //* a. Special characters must be enclosed in apostrophes. //* b. For SMS allocations, this symbol can be left as-is. // SET RT_VOLSER='VOL=SER=@RT_VOLUME@'
Important! After you run ETJICUST more than once, the runtime JCL appears as follows to enable SMS multiextent allocation for data sets:
//BKP4003B DD DSN=CAI.CHORUS.DATACOM.TSF4003.NEW, // DISP=(NEW,CATLG,DELETE), // STORCLAS=SCTSO, // MGMTCLAS=MCTSO, // UNIT=(3390,3),DSNTYPE=LARGE, // SPACE=(CYL,(2000,500),RLSE
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|