When defining and initializing a new CA Intertest PROTSYM file the job automatically allocates secondary extents to the PROTSYM file and generates several V370040 messages.
Article ID: 131660
Updated On:
Products
InterTest - CICS
InterTest - Batch
InterTest VSE - CICS
Issue/Introduction
The client is defining and initializing a small 10,000 record PROTSYM file just to contain the CA Intertest demo programs. The PROTSYM file is not allowed to have secondary extents.
During the IN25UTIL initialization step the job step automatically allocates many secondary extents to the PROTSYM file and generates several V370040 messages.
13.15.37 JOB09335 V370040 END OF VOLUME RECOVERY OPERATION STARTING FOR
13.15.37 JOB09335 V370040 ZADSATRA,LOAD,PROTSYM,INTRTEST.PROTSYM.DATA
13.15.37 JOB09335 V370040 CURRENTLY ON EXTENT # 1 ON VOLUME VP0038
13.15.37 JOB09335 V370040 END OF VOLUME RECOVERY OPERATION SUCCESSFUL FOR
13.15.37 JOB09335 V370040 ZADSATRA,LOAD,PROTSYM,INTRTEST.PROTSYM.DATA
13.15.37 JOB09335 V370040 NEW VOLUME SMS ADDED, NEW VOLUME COUNT 2
The batch job runs a long time and continues to allocate additional secondary extents until the job is cancelled or the volume runs out of space.
During the IN25UTIL initialization step the job step automatically allocates many secondary extents to the PROTSYM file and generates several V370040 messages.
13.15.37 JOB09335 V370040 END OF VOLUME RECOVERY OPERATION STARTING FOR
13.15.37 JOB09335 V370040 ZADSATRA,LOAD,PROTSYM,INTRTEST.PROTSYM.DATA
13.15.37 JOB09335 V370040 CURRENTLY ON EXTENT # 1 ON VOLUME VP0038
13.15.37 JOB09335 V370040 END OF VOLUME RECOVERY OPERATION SUCCESSFUL FOR
13.15.37 JOB09335 V370040 ZADSATRA,LOAD,PROTSYM,INTRTEST.PROTSYM.DATA
13.15.37 JOB09335 V370040 NEW VOLUME SMS ADDED, NEW VOLUME COUNT 2
The batch job runs a long time and continues to allocate additional secondary extents until the job is cancelled or the volume runs out of space.
Environment
Z/OS
Cause
During the IN25UTIL initialization step CA Allocate determined the primary allocation was full and added and continued to add secondary extents.
Resolution
The messages in the IN25UTIL initialization step V370040 pointed to CA Allocate getting control and allocating secondary extents to the PROTSYM file when it determined the primary allocate was full.
V370040 END OF VOLUME RECOVERY OPERATION STARTING FOR
Since the PROTSYM file is not allowed to have secondary extents we needed to BYPASS the PROTSYM initialization step IN25UTIL from CA Allocate control. In order to bypass CA Allocate in a step you need to add a DD statement to the JCL to exclude the step from CA Allocate control. Please see the following.
Bypassing Allocations
To bypass CA Allocate DASD Space and Placement for all allocations in a step, allocate DDNAME VDSBYPAS to the step or TSO session.
In a batch job step:
//VDSBYPAS DD DUMMY
For a TSO session:
ALLOC FI(VDSBYPAS) DUMMY
In this case the JCL statement
//VDSBYPAS DD DUMMY
was added to the IN25UTIL INITIALIZATION step so secondary extents would not be allocated to the PROTSYM file.
V370040 END OF VOLUME RECOVERY OPERATION STARTING FOR
Since the PROTSYM file is not allowed to have secondary extents we needed to BYPASS the PROTSYM initialization step IN25UTIL from CA Allocate control. In order to bypass CA Allocate in a step you need to add a DD statement to the JCL to exclude the step from CA Allocate control. Please see the following.
Bypassing Allocations
To bypass CA Allocate DASD Space and Placement for all allocations in a step, allocate DDNAME VDSBYPAS to the step or TSO session.
In a batch job step:
//VDSBYPAS DD DUMMY
For a TSO session:
ALLOC FI(VDSBYPAS) DUMMY
In this case the JCL statement
//VDSBYPAS DD DUMMY
was added to the IN25UTIL INITIALIZATION step so secondary extents would not be allocated to the PROTSYM file.
Feedback
Yes
No
Powered by
