Start a Conversation

Unsolved

This post is more than 5 years old

803

August 23rd, 2010 11:00

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?

No Responses!
No Events found!

Top