Unsolved
This post is more than 5 years old
1 Message
0
793
TimeFinder V5.8.0 z/OS 1.11 vs. 1.9
We run TimeFinder/SNAP V5.8.0 (028). I upgraded the mainframe OS to z/OS 1.11 on Sunday. Sunday night, our SNAP jobs ran as usual with one exception. When attempting to SNAP 2 of the many VSAM files we copy, I received the following error:
ESNP084E BOTH DATA SETS MUST HAVE THE SAME CI/CA, CISIZE AND TRK/AU
ESNP085I SOURCE DATA SET NAME: PRODV.P.MT.P.MT110I1.INDEX CI/CA: 33 CISIZE: 1024 TRK/AU: 1
ESNP086I TARGET DATA SET NAME: BCV.P.MT.P.MT110I1.INDEX CI/CA: 26 CISIZE: 1536 TRK/AU: 1
The control cards for this operation are:
SNAP DATASET ( SOURCE(PRODV.P.MT.P.MT110I1.CLUSTER) -
TARGET(BCV.PRODV.P.MT.P.MT110I1.CLUSTER) -
SPHERE(YES) RENAMEU(BCV) -
HCPYMODE(SHR) TOLENQF(Y) -
REPLACE(Y) BCVGROUP(GRP2) )
TimeFinder then went through its normal cleanup and deleted whatever target file it created. I figured because it did a cleanup, if I did a re-run it would create a new target file and use all the attributes of the source file, but it failed with the same condition. I got around it by using IDCAMS to perform a define for the target using the attributes of the source file and then doing a REPRO from source to target.
Do you know of any issues with z/OS 1.11 and this release of TimeFinder/SNAP?
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
August 23rd, 2010 12:00
Dennis, IBM changed their code for small VSAM datasets. Because of that you are having this problem. Because the PTF for version 5.8 is not GA yet you will be contacted by support. The PTF for 5.8 is SN58033 and the GA PTF for version 7.00 is SN70018.
PROBLEM FIXED: OPT 336939
USERS AFFECTED: SMALL VSAM
PROBLEM DESCRIPTION: SMALL VSAM ON ZOS 1.11 FAIL VERIFY
DESCRIPTION DETAIL:
SMALL VSAM ALLOCATED ON EARLIER ZOS SYSTEMS FAIL TO COPY
PROPERLY WHEN ZOS ALLOCATES THE TARGET DATASET. THIS IS
BECAUSE OF THE CISIZE AND CI/CA ALLOCATION CHANGES IN
ZOS 1.11. THIS AFFECTS VSAM DATASETS USUALLY SMALLER
THAN ONE CYLINDER WITH A CI/CA VALUE OF 2,4,6,8,10,11,12,
13 AND 14. THE SOLUTION IS TO FORCE EXTENT ALLOCATION
IN THIS SITUATION AND BRING OVER THE EXISTING ALLOCATION.