APAR status
Closed as canceled.
Error description
The MVS volume can be in either OS format (VTOC only) or Indexed format (VTOC and INDEX). The users can perform the VTOC expansion using one of the following procedures: . 1. Run REFORMAT NEWVTOC(cc,hh,n|ANY,n) to expand the VTOC. The new VTOC will be allocated on the beginning location 'cc,hh' with total size of 'n' tracks. Overlay between the new and old VTOC is not allowed. If 'cc,hh' is omitted, ICKDSF will locate the new VTOC on the volume at the first eligible location on the volume other than at the location of the old VTOC where free spacewith 'n' tracks is found. 'n' must be greater than the old VTOC size. The volume must be offline to use the NEWVTOC parameter. . 2. Run REFORMAT EXTVTOC(n) where 'n' is the total size of the new VTOC in tracks. There must be free space available to allow for contiguous expansion of the VTOC. If there isn't free space available following the current location of the VTOC, an error message will be issued. 'n' must be greater than the old VTOC size. . Expand VTOC - ONLINE 1. After VTOC expansion, a. If the VTOC is an OS-VTOC the free space chain becomes invalid. It will be rebuilt at the first allocation of a data set. If you have apar PQ97194 installed and running z/OS 1.7 or higher, the free space chains will be rebuilt for you and will not require an allocation of a data set. b. If the VTOC is an INDEX-VTOC the Index Data Set will be deleted, during the VTOC expansion and be rebuilt. The following message will be displayed when the index gets deleted: ICK01520I THE VTOC-INDEX WAS DELETED . Expand VTOC - OFFLINE 1. After VTOC expansion, the free space becomes invalid. It will be rebuilt at the first allocation of a data set after the device is varied online to MVS. If an INDEX-VTOC volume is desired at this stage, do the following three steps. Otherwise, stop right here. 2. Vary the device online to MVS. 3. If the index data set does not already exist, a new index data set must be pre-allocated prior to the next step but can be in the same JCL step. 4. Convert the volume to Indexed-VTOC format via BUILDIX command (optional for non-SMS volumes). . . POSSIBLE PROBLEMS WHEN ALL STEPS AREN'T FOLLOWED IN THIS APAR: If the VTOC is an OS - VTOC after using the EXTVTOC or REFVTOC parameters of the REFORMAT command the free space chains may be invalid because of the change in the VTOC. You might see the following message when accessing the device through ISPF - 'FREESPACE ERROR LRC=8 LSPACE ERROR'. Allocate a dataset to the volume and the free space chains will be rebuilt so the volume is then accessible. . NOTE: If the volume is shared across multiple systems and INDEX VTOC is going to be maintained, then you MUST follow the instructions documented in the REFORMAT section of the manual for volumes shared across multiple systems. It states: . When you invoke REFORMAT with the EXTVTOC or REFVTOC parameter for a volume that is shared by other systems additional serialization is needed. This additional serialization increases processing time by up to seven seconds per volume. If the volume is not shared by other systems, or you have varied the volume offline to all other systems, then the serialization is not needed and can be bypassed by using the JCL parameter PARM=NOSYSZ on your EXEC statement. For example: //stepname EXEC PGM=ICKDSF,PARM=NOSYSZ . If the user is expanding the VTOC using the REFORMAT EXTVTOC(n) procedure described above and the volume is online to more than one system, the user must ensure that APAR OA10895 is applied to all systems. This maintenance prevents the index from becoming disabled during the reformat. . Add keywords: 565899201 RG01 RG03 NEWVTOC EXTVTOC RH01 RH03 RHCD
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
take apar out of intran.
APAR Information
APAR number
II08349
Reported component name
PA LIB INFO ITE
Reported component ID
INFOPALIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1994-11-23
Closed date
1999-02-24
Last modified date
2007-07-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"001"}]
Document Information
Modified date:
09 January 2021