1) AFAIK there is no way to re-size the VTOCIX except a BUILDIX OSVTOC/BUILDIX IXVTOC sequence.
Specifically an example (slightly modified from the manual "GC35-0033-39 Device Support Facilities (ICKDSF) User's Guide and Reference"): //jobname JOB //STEP1 EXEC PGM=ICKDSF,PARM='NOREPLYU' //SYSPRINT DD SYSOUT=A //DDCARD DD UNIT=(3390,,DEFER),VOL=(PRIVATE,SER=VL3390), // DISP=OLD //SYSIN DD * BUILDIX DDNAME(DDCARD) OS PURGE <----------------------------------------------------------------- Deletes the existing index /* //STEP2 EXEC PGM=ICKDSF //SYSPRINT DD SYSOUT=A //VOLDD DD UNIT=(3390,,DEFER),VOL=(PRIVATE,SER=339003), <-------- ----------------------------Allocates a new index. // DSN=SYS1.VTOCIX.V39003,DISP=(NEW,KEEP), // SPACE=(TRK,10,,CONTIG) //SYSIN DD * BUILDIX DDNAME(VOLDD) IXVTOC /* 2) The previously mentioned MAXVTOC/MAXVTOCIX sizes are in TABLE 57 on page 586 of manual "GC35-0033-39 Device Support Facilities (ICKDSF) User's Guide and Reference"): 3) I believe we have established that there is adequate space in the SDSP dataset(s) via "HI-A-RBA -1,592,647,680, HI-U-RBA -454,471,680, 455,270,400, 452,075,520, so under 33%" 4) I believe we have established that there is adequate space on the volume(s) via " Volumes are 45-48% free." Something seems to be missing from the scenario. *IF* MOBIUS is placing HLQ.pgmname.ddname.R#.Dyymmdd.Thhmmss into the SDSP dataset(s), *WHY* would there be *ANY* issues w/the VTOCIX? Are the VTOCIX's on these 3 volumes the same size as the remaining volumes? <snip> The VIR count was down to 3 on the 3 volumes, other LPAR ML1 volumes have 236-1538 VIRs. Volumes are 45-48% free. HI-A-RBA -1,592,647,680, HI-U-RBA -454,471,680, 455,270,400, 452,075,520, so under 33%. </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
