This action might not be possible to undo. Are you sure you want to continue?
volume = 15 disks disk = 3990 tracks track = 47 Kb byte = 8 bit
and 1 cyl = 15 tracks
For a 3390 DASD 1 Track = 48 KB 1 Cylinder = 720 KB 1 Cylinder = 15 Tracks I am told to change all the Current JOBS in production, I have to change CYL to TRK, If space parameter is CYL (1,2). I have to change it to TRK(15,30) I am not very sure why they asked me to do it, But i was just told that it is for better performance and Access
Alternate cylinders 1 1 1 3 3 3 0 0
Tracks per cylinder 15 15 15 15 15 15 15 15
Bytes per Bytes per track 56,664 56,664 56,664 56,664 56,664 56,664 46,456 46,456 cylinder 849,960 849,960 849,960 849,960 849,960 849,960 696,840 696,840
Bytes per module
3390-1 3390-2 3390-3 3390-9 3390-27 (2) 3390-54 9345-1 9345-2
1113 2226 3339 10017 32760 65520 1440 2156
946,005,480 1,892,010,960 2,838,016,440 8,514,049,320 27,844,689,600 55,689,279,200 1,003,449,600 1,502,387,040
Fixed Block Architecure (FBA) Devices
3390 disks and channel speeds
3390 disk information
Every 3390 disk volume contains 56,664 bytes per track, 15 tracks per cylinder and 849,960 Bytes per Cylinder. The terms 'track' and 'cylinder' come from old pre-raid disks, which were like 8 old fashioned vinyl records stacked in a pile, with a set of fixed read/write heads which moved in and out of them. The disks had recording surfaces on both sides. Of the 16 surfaces, one surface was used for control information which left 15 for data. A 'track' was the amount of data which could be read from a single surface in one revolution, without moving the heads. Think of it as the needle on the vinyl record doing one revolution. A 'cylinder' could be read from all 15 surfaces without moving the heads. This was quite important, as a cylinder could be read quite quickly, without any mechanical movement. The diagram might help explain
017 32. For these data sets. the block size is set to 16 384.84 GB 8. so the terms 'track' and 'cylinder' are still used. The rule of thumb is that the primary amount is used when acquiring the initial extents on any volume.520 Cylinders per Volume 1. as is the case with multistripe or DB2 linear data sets.226 50. In addition.085 3. The requested target is used to calculate the primary and secondary amounts that are used by VSAM EOV.800 65.84 GB 55.Modern disks use FBA storage. 3390 disk numbers Model Tracks per Volume Model 1 Model 2 Model 3 Model 9 Model 27 Model 54 16. or megabytes for a linear data set. The secondary amount is used when allocating additional extents on the current volume. The system chooses the best physical record size to use the track size geometry. the primary amount is only used for the initial allocation on the first volume(s).68 GB Linear Data Sets You must allocate space in tracks.255 491. The Media Manager programming interface allows a program to request a target relative block address (RBA) or relative block number (RBN). When additional space is needed to write more records.695 33. LACK OF AVAILABLE SPACE AT TIME OF EXTEND One of the primary functions of EOV is to acquire more space when a data set becomes full. If the specified BUFFERSPACE is greater than 8192 bytes.113 Bytes per Volume 946 MB 1. For example. MAINVIEW SRM StopX37/II can add candidate volumes when no more candidates exist for the data set.390 2. MAINVIEW SRM StopX37/II can alter the primary or secondary amounts that are used by VSAM EOV to fit in the available space. The amount of space added is usually determined by the defined primary or secondary amounts in the catalog entry for the VSAM data set. if you specify CISIZE(16384). If not an integer multiple of 4096. Note: The Additional Volume Amount field in a DFSMS Dataclass also allows you to specify which amount (primary or secondary) is used when extending to an additional volume. where the secondary amount is also used when allocating the initial extents on additional volumes. but they have to emulate 3390 CKD format.339 150. records. you can specify a control interval size of 4096 to 32 768 bytes in increments of 4096 bytes.760 982.89 GB 2. There are some exceptions. When you define a linear data set. access method services issues a message and fails the command.400 10. it is decremented to a multiple of 4096. cylinders. How VSAM allocates additional space during EOV A VSAM data set is considered full when the high-used-relative-byte-address (HI-U-RBA) reaches the high-allocatedrelative-byte-address (HI-A-RBA). If VSAM is unable to obtain additional space. the control interval size is rounded up to the next 4096 increment. If BUFFERSPACE is less than 8192. kilobytes.51 GB 27. This paper focuses on the more widely used allocation amounts that are defined in a VSAM data set catalog entry. EOV is invoked to increase the HI-A-RBA. .
The CYL (cylinder) parameter in the DEFINE CLUSTER statement shown in Figure 1 specifies the primary and secondary allocation amounts for SAMPLE. y y The HI-A-RBA indicates 319488000 bytes are now available for storing records(Bytes ya están disponibles para almacenar registros).DATA is allocated to a task. This indicates that volume TSG331 was nearly full at the time the data set was defined and 400 cylinders were not available in one contiguous extent.STOPX.It should be noted that MAINVIEW SRM StopX37/II does not alter the primary and secondary amounts in the catalog during EOV. A volume with allocated extents will be flagged (VOLFLAG) as PRIME. . The VOL (volume) parameter specifies TSG331 is the only volume allocated to this data set.STOPX.NONSMS) CYL(400 50) VOL(TSG331) FREESPACE(0 ) NONINDEXED RECORDSIZE(4160 4160) SHAREOPTIONS(2 3) ) The excerpt from a subsequent LISTCAT (see Figure 2) shows the results of the DEFINE CLUSTER statement. This paper uses a nonstriped ESDS VSAM data set to show how EOV extends a typical VSAM data set. Figure 1 Sample define of a nonstriped ESDS DEFINE CLUSTER (NAME(SAMPLE.STOPX. The ALLOCATION and VOLUME sections hold much of the essential catalog information that is used by the VSAM EOV process.NONSMS. A cylinder allocation amount is multiplied by 15 to determine the number of tracks because all DASD is configured as 15 tracks per cylinder today. Also. The EOV process is essentially the same for any VSAM component. When SAMPLE. which makes the HIGH-RBA field of the last allocated extent 1 byte less than the total bytes allocated to the data set. The LOW-CCHH and HIGHCCHH addresses indicate the location of each extent on volume TSG331. Figure 2 Sample LISTCAT excerpt ALLOCATION SPACE-TYPE------CYLINDER HI-A-RBA-------319488000 SPACE-PRI------------400 HI-U-RBA---------------0 SPACE-SEC-------------50 VOLUME VOLSER------------TSG331 PHYREC-SIZE--------26624 HI-A-RBA-------319488000 DEVTYPE------X'3010200F' PHYRECS/TRK------------2 HI-U-RBA---------------0 VOLFLAG------------PRIME TRACKS/CA-------------15 EXTENTS: LOW-CCHH-----X'02C40000' LOW-RBA----------------0 TRACKS--------------1185 HIGH-CCHH----X'0312000E' HIGH-RBA--------63098879 LOW-CCHH-----X'036E0000' LOW-RBA---------63098880 TRACKS---------------210 HIGH-CCHH----X'037B000E' HIGH-RBA--------74280959 LOW-CCHH-----X'0A360000' LOW-RBA---------74280960 TRACKS--------------1980 HIGH-CCHH----X'0AB9000E' HIGH-RBA-------179711999 LOW-CCHH-----X'0ABF0000' LOW-RBA--------179712000 TRACKS--------------1620 HIGH-CCHH----X'0B2A000E' HIGH-RBA-------265973759 LOW-CCHH-----X'0CC80000' LOW-RBA--------265973760 TRACKS--------------1005 HIGH-CCHH----X'0D0A000E' HIGH-RBA-------319487999 LISTCAT notes y VSAM allocates extents in TRACKS. a chain of 5 EDBs are built to indicate the location of the allocated space for the VSAM data set. MAINVIEW SRM StopX37/II also ensures that any adjusted amounts are a full increment of the VSAM data set control area (CA) size. whether SPACE-TYPE is defined as CYLINDER or TRACK.DATA. note the 400 cylinders of primary space were actually allocated in 5 extents. an initial primary amount of 400 cylinders is acquired on volser TSG331. The first allocated extent in a VSAM data set always starts the LOW-RBA field at relative zero. and the HI-U-RBA is 0.NONSMS. At the time of definition.
If space is available and the extend is successful. (If this was a SMS-managed data set.DATA qualified for SPACSECB processing.". Because the sample data set is defined with a secondary amount greater than 0.STOPX. . The SPACSECB function can serve two purposes: y y It can reduce the extent fragmentation for the data set. MAINVIEW SRM StopX37/I I would have changed the secondary request to 48 cylinders (720 tracks) and only allocated one additional extent. The following sample LISTCAT shows another 50 cylinders (750 tracks) were allocated on volume TSG331 and the HI-A-RBA is now 359424000 bytes.) SPACSECR SPACSECR reduces the secondary amount when EOV is unable to obtain the requested space seen in EOV scenario 2. VSAM EOV adds the additional extent information to the task's EDB chain and the catalog entry for the data set. If SAMPLE. EOV scenario 2 As we saw in "EOV scenario 1.EOV scenario 1 (Y hay una solicitud para escribir registros suplementarios para el conjunto de datos) After the HI-U-RBA meets the HI-A-RBA and there is a request to write additional records to the data set.NONSMS.STOPX.DATA qualified for SPACSECR processing and space was available on volume TSG331.NONSMS. the extend would fail and VSAM EOV would issue an IEC070I 104-204 error message. MAINVIEW SRM StopX37/II would lower the secondary request to fit in the available space. If SAMPLE. However. It helps keep the total extent count from reaching the 123 maximum allowed on an individual volume for a VSAM data set. EOV will be invoked to acquire more space. if volume TSG331 did not have 50 cylinders available. VSAM EOV will attempt to allocate 50 cylinders on current volume TSG331. 50 cylinders were allocated in two physical extents(En este escenario. Figure 3 Sample LISTCAT excerpt after a successful extend of 50 cyl inders ALLOCATION SPACE-TYPE------CYLINDER HI-A-RBA-------359424000 SPACE-PRI------------400 HI-U-RBA-------34611200 SPACE-SEC-------------50 VOLUME VOLSER------------TSG331 PHYREC-SIZE--------26624 HI-A-RBA-------359424000 DEVTYPE------X'3010200F' PHYRECS/TRK------------2 HI-U-RBA-------346112000 VOLFLAG------------PRIME TRACKS/CA-------------15 EXTENTS: LOW-CCHH-----X'02C40000' LOW-RBA----------------0 TRACKS--------------1185 HIGH-CCHH----X'0312000E' HIGH-RBA--------63098879 LOW-CCHH-----X'036E0000' LOW-RBA---------63098880 TRACKS---------------210 HIGH-CCHH----X'037B000E' HIGH-RBA--------74280959 LOW-CCHH-----X'0A360000' LOW-RBA---------74280960 TRACKS--------------1980 HIGH-CCHH----X'0AB9000E' HIGH-RBA-------179711999 LOW-CCHH-----X'0ABF0000' LOW-RBA--------179712000 TRACKS--------------1620 HIGH-CCHH----X'0B2A000E' HIGH-RBA-------265973759 LOW-CCHH-----X'0CC80000' LOW-RBA--------265973760 TRACKS--------------1005 HIGH-CCHH----X'0D0A000E' HIGH-RBA-------319487999 LOW-CCHH-----X'082C0000' LOW-RBA--------319488000 TRACKS---------------720 HIGH-CCHH----X'085B000E' HIGH-RBA-------357826559 LOW-CCHH-----X'07700000' LOW-RBA--------357826560 TRACKS----------------30 HIGH-CCHH----X'0771000E' HIGH-RBA-------359423999 SPACSECB SPACSECB is the one VSAM EOV function in MAINVIEW StopX37/II that is not invoked for error recovery. 50 cilindros fueron asignados en dos grados física). VSAM EOV was able to allocate the secondary amount (50 cylinders) on the current volume. (Hace mejor uso de los actuales EXTENTE sobre el actual volumen seleccionando el tamaño de la principal medida cuando más de uno es necesaria para satisfacer la solicitud secundaria) In this scenario. VSAM EOV would issue an IEC070I 209-220 error message. SPACSECB makes better use of the existing extents on the current volume by selecting the size of the largest single extent when more than one is required to satisfy the secondary request. One extent is 720 tracks(48 CYL) and the other is 30 tracks (2 CYL).
Under these conditions. Primary and Secondary Space Allocations for Striped Data Sets . This feature allows VSAM EOV to acquire additional space on the new volume.STOPX. The result is improved performance for sequential data access by achieving data transfer into the application at a rate greater than any single I/O path. MAINVIEW SRM StopX37/II would add a candidate volume to its catalog entry and rebuild the task's internal control blocks to indicate the additional volume. All VSAM data set organizations are supported for striped data: y y y y y Key-sequenced data set (KSDS) Entry-sequenced data set (ESDS) Relative-record data set (RRDS) Variable-length relative-record data set (VRRDS) Linear data set (LDS) A striped data set has tracks that spread across multiple devices. by using the primary amount defined for the data set. MAINVIEW SRM StopX37/II can add a candidate volume with the SPACVOLA function to prevent the error.DATA qualified for SPACVOLA processing. as is the case for sequential access method or the CIs for VSAM. Figure 15 illustrates primary and secondary space allocations on multiple volumes for a striped VSAM data set. Any data set listed with one stripe is in the extended format and is not considered to be a striped data set. This format allows a single application request for records in multiple tracks or CIs to be satisfied by concurrent I/O requests to multiple volumes. VSAM Data Striping z/OS V1R10.SPACVOLA If no space was available on the current volume in EOV scenario 2. a data set must be in extended format.NONSMS. If SAMPLE. The scheduling of I/O to multiple devices to satisfy a single application request is referred to as an I/O packet. VSAM data striping applies only to data sets that are defined with more than one stripe. Figure 15. SPACSECR would be unable to recover the error.0 DFSMS Using Data Sets SC26-7410-08 To use striped data.
the definition of striped is a stripe count greater than 1. those volumes that will participate as part of the I/O packet. The sequential access method (SAM) does not support the concept of multilayering. Figure 16. the volumes that constitute this I/O packet should be viewed in the same context as a single volume data set. As relates to striped data. Control Interval in a Control Area Layering Concept for Data Striping Layering is a concept generally associated with data that is striped. composing this I/O packet changes. up to a maximum of stripe count. A layer in a striped environment is defined as the relationship of the volumes that make up the total number of stripes. That is. as opposed to multivolume if the data were not striped. Once the data set extends to a second layer.Figure 16 shows examples of the CIs within a control area (CA) on multiple volumes for a four-stripe VSAM data set. Once any volume or volumes. Figure 17 shows an example of the concept of . this would be analogous to a multivolume nonstriped data set. this constitutes another layer. Again. VSAM supports multilayering.
When the system allocates space for |a striped extended-format data set. This only occurs after attempts |by the system to allocate the exact amount for each stripe does not succeed. The amount |is the secondary amount divided by the number of stripes. Secondary Allocation Quantity of Zero When you specify a secondary allocation quantity of zero for nonstriped VSAM data sets.layering with a four-stripe data set. All data set extends are as described for striped data set extends. For extended-format data sets. control area size. resulting in some differences in allocation quantity required to meet the stripe count and CA requirements. The remaining stripes space amount is adjusted to match to ensure all |stripes contain the same amount of space. If the primary amount is not divided evenly. The number of stripes influences the size of the control area. as well as extending to a new layer. Layering (Four-Stripe Data Set) Other Considerations for Data Striping To use data striping. The following topic on CA size considerations discusses this in more detail. the system divides the primary amount |among the volumes. when the primary space |on any volume is full. you also need to consider space allocation. extensions occur by stripe and can occur on the same volume or on a new volume. the system |rounds up the amount. Restriction: Volume High Used RBA statistics do not apply for multistriped VSAM data sets. including a data set with the guaranteed space attribute from the associated storage class (SC). This situation might |happen when cylinder-managed space has been selected which might cause the |requested space amount of that stripe to be rounded to the next multicylinder |unit. using the primary-space amount. the system rounds up the amount. Space Allocation for Striped VSAM Data Sets |The general rules discussed for striped extended format data |sets apply to striped VSAM data sets. an extend causes the allocation to occur on a new volume. Figure 17. the system allocates space on that volume. The system |might have to perform additional rounding of space for each stripe if one |or more extended address volumes have been selected. Basically. The highuse RBA is kept on the volume for the first stripe because the value is the same for all stripes. If the secondary |amount does not divide evenly. Some additional considerations apply to the control area (CA) for VSAM. For striped VSAM data sets. the system divides the secondary amount by the stripe count and allocates the result to each stripe. and processing. using the primary-space amount when a secondary-space amount of zero is specified. This occurs in all cases. . You can also use this feature to spread data over multiple volumes. All allocations must be rounded to a CA boundary.
regardless of striping. traditional VSAM. Provide >5 extent relief (completed for all allocations for VSAM striped data. Only the data component is striped. The default value is N (no). If you analyze the output of the LISTCAT command there is ALLOCATION information which shows two fields HURBA and HARBA. and the maximum CA now becomes 16 tracks. The index component of a striped VSAM data set has a limit of 255 extents. The intended purposes for data striping follow: y y Spread the data across volumes (a basic implementation technique for any data that is striped). A larger CA results in a larger number of control intervals (CIs) in the CA.Increased Number of Extents A striped VSAM data set can have 255 extents per stripe in the data component. That changes with striped VSAM data set in that the maximum CA size now has to accommodate the maximum stripe count (16). a striped data component can have a maximum of 4080 extents. resulting in a larger number of entries to index in a data set organization containing an index (KSDS and VRRDS). to enforce the 255-extent limit. Processing Considerations for Striped Data Sets The basic restrictions associated with data sets in the extended format also apply to striped data sets. based on 3390 geometry. As an example. with the end result being a requirement for a larger index CI size. In addition. For a striped data set with a striped count = maximum =16. the 255-extent per stripe limit is removed if the extent constraint removal parameter in the data class is set to Y (yes). A VSAM striped data set can be striped up to a count of 16. The required allocation quantity now becomes a factor of both user specified amount and stripe count. the control area size is then 16 tracks with a resulting primary and secondary quantity of 16 tracks. regardless of the specification). VSAM striped data sets do not support: y y RLS access Improved CI access For the alternate index. . take a specification for space of TRACKS(1 1) with the following results: y y For nonstriped. would be 15 tracks. This limit must be enforced if the data set might be shared with a pre-V1R7 system. neither the data nor the index will be striped. Allocation Restrictions The Space Constraint Relief attribute will not be considered for striped data sets. Starting in z/OS V1R7. The maximum CA size is a cylinder. Control Area Size Calculation The control area (CA) size for striped VSAM data is a factor of the stripe count. Because a striped VSAM data set can have a maximum of 16 stripes. The minimum size for an allocation is a single track. a control areas size of one track with a resulting primary and secondary allocation quantity of 1 track. Traditionally that would have meant that the maximum CA size.
The difference is that the guaranteed space data set uses the "candidate with space" amount that is already allocated on that volume. which reduces the amount of extents. The data set initially gets three cylinders and an additional cylinder every time the data set is extended.High-Used-RBA (HURBA)points to the end of the data. track 14. When all of the space on the primary volume is used. This value reflects the portion of the space allocation that is actually filled with data records. Example: The old extent begins on cylinder 6.3. High-Allocated-RBA (HARBA) is the highest byte that can be used. The system consolidates adjacent extents for VSAM data sets when extending on the same volume. the LISTCAT output might show allocations of cylinders 5. track 0. For SMS-managed VSAM data sets. this extent limit is removed if Extent Constraint Removal is specified in the Data Class. PL/I Assembler Language. in CICS) and use the statements provided by these languages to write and read VSAM datasets A primary space allocation is the initial amount of allocated space. The system reserves the last four extents for extending a component when the system cannot allocate the last extent in one piece. the primary allocation is allocated on the first volume as "PRIME" and all of the other guaranteed space volumes as "candidate with space". When no more space can be allocated on the primary volume. or 7257 extents.1.1. When the primary amount on the first volume is used up. Then the system uses the "candidate with space" amount on the next volume. to enforce the 255-extent limit. there is only one extent. and so forth. The theoretical limit is then the maximum number of volumes (59). when you allocate space for your data set. There are actually to HURBAs one in the VSAM control bl ock of the cluster and one in the catalog entry for the cluster. and ends on cylinder 9. If none of the extents are adjacent. HIGH-ALLOC-RBA indicates the Relative Byte Address(plus 1) of the last allocated data control area.5. a secondary amount is allocated on that volume. VSAM extent consolidation is automatic and requires no action on your part. Subsequent extends again use the secondary amounts to allocate space until the volume is full.1. the 255-extent per stripe limit is removed if the extent constraint removal parameter in the data class is set to Y (yes). The VSAM limit of 255 extents is still enforced for any non-SMS-managed data set. Instead of two extents.1.1.1. track 14. Results: Depending on which extents are adjacent. the new extent is incorporated into the previous extent. This value reflects the total space allocation for the data component. and the new extent begins on cylinder 10. The system repeats allocating this space until the volume is out of space or the volume extent limit of 123 is reached. track 14. If the extents are adjacent. You can expand the space for a nonstriped VSAM component to 255 extents. The two extents are combined into one extent beginning on cylinder 6. the system gets space on the primary volume using the secondary amount. the system uses the "candidate with space" amount on the next volume. the system allocates more space in the secondary space amount. Guaranteed and nonguaranteed space allocation work similarly until the system extends the data set to a new volume. The default value is N (no). you can specify in the SMS data class parameter whether to use primary or secondary allocation amounts when extending to a new volume.2. For both guaranteed and nonguaranteed space allocations. With guaranteed space allocations. track 0. or cylinders 3.1. For nonstriped VSAM data sets. and ends on cylinder 12. track 0. You can write application programs (in COBOL. This limit must be enforced if the data set might be shared with a pre-V1R7 system. as follows: . and ending on cylinder 12. Because VSAM combines the two extents. HIGH-USED-RBA indicates the Relative Byte Address(plus 1) of the last used data control area. Suppose you extend this data set five times. Example: You allocate a VSAM data set with CYLINDERS(3 1). it does not increment the extent count. Each time a new record does not fit in the allocated space. You can expand the space for a striped VSAM component to 255 times the number of stripes. Note: Starting in z/OS V1R7. the LISTCAT output shows allocations of cylinders 3. or cylinders 3. you can specify both a primary and a secondary allocation. or a total of eight cylinders. times 123 extents per volume.1.
All types of SMS-managed VSAM data sets (KSDS.5 example. RRDS. but the third through eighth extent are adjacent.3 example.1. and the last three extents are adjacent. the first and second extent are not adjacent.1 example. For the 3. Restriction: VSAM does not support extent consolidation for the following types of data sets: y y y y y y y Key-range data sets System data sets such as page spaces Catalogs VVDSs Non-system managed data sets Imbedded or replicated indexes VSAM data sets that you access using record-level sharing . only the first three extents are adjacent. VRRDS.y y y For the 5. For the 3.1. the first and second extent are not adjacent. and LDS) use extent consolidation. ESDS. the second and third extents are adjacent. the third and fourth extents are not adjacent.2.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.