EOV Support for Zero Secondary (PLSZSEC(Y) )

Products

• Allocate DASD Space and Placement

Issue/Introduction

We are running with "ZERO SECONDARY SUPPORT" (cfr the parameter in the Subject) but this set up caused some issue with SYS1.* datasets (i.e. SYS1.NUCLEUS).

indeed we don't want to have secondary extent for this kind of DS but it seems that Allocate intercept the B37 and expand this DS with further extent. Is it possible to exclude some volume (or DS) from "EOV ZERO SECONDARY SUPPORT" ?

Please take into account that these DS are NOT_SMS!

Resolution

Setting the EXTEND environment in this way (with PLSZSEC(Y)):

IF &DSORG = 'PO' THEN

DO

IF (&VOLSER = 'Z22RTB' OR

&VOLSER = 'Z22RTA') AND

&SECONDARY_HAD_ZERO = 'Y' THEN

DO

WRITE 'VAMMSG EXT DATASET &DSN HAD SECONDARY SPACE EQUAL ZERO'

WRITE 'VAMMSG EXT SPACE NOT INCREASED BY ZEXTEND ROUTINE '

EXIT CODE(4)

END

WRITE 'VAMMSG EXT DATASET &DSN IS A PDS '

WRITE 'VAMMSG EXT SPACE INCREASED BY ZEXTEND ROUTINE '

EXIT CODE(0)

Consider adding FILTLIST &SYSV INCLUDE(Z22RT*,ZOSCA*)
at the beginning of VDSPROG ASR.