COZBATCH step fails due to dataset contention with own job after upgrade to z/OS 2.5

Discussion of the COZBATCH utility for z/OS
Post Reply
rhutson
Posts: 10
Joined: Wed May 12, 2021 3:43 pm

COZBATCH step fails due to dataset contention with own job after upgrade to z/OS 2.5

Post by rhutson »

Reposting this from Co:Z SFTP forum:

In our installation, COZBATCH utility job step started failing after Z/OS 2.5.0 upgrade. It complains that the dataset to be transferred is in use

But the problematic datasets are created in the same job and down the line in the same job, they are SFTP’d using COZBATCH utility.

Below is a job that fails in COZBATCH utility job step.

Job Job# Started Ended Code
XXXX039D J010445 01202023 2008 01202023 2008 8

The below messages appear in the sysout of COZBATCH utility step of the above job

X 1 B01:XXXX039D.STEP04.SYSOUT Line 37 of 49
Command ===> SPF Scroll ==> CSR
IKJ56225I DATA SET HS.XXXX039D.WKLD.RPT.DAEH ALREADY IN USE, TRY LATER+
IKJ56225I DATA SET IS ALLOCATED TO ANOTHER JOB OR USER
IEFA110I DATA SET CONTENTION
DATA SET HS.XXXX039D.WKLD.RPT.DAEH IN USE BY
SYSNAME JOBNAME ASID
TEST XXXX039D 00A2
DatasetHandlerÝE¨: BPXWDYN allocation failed S99ERROR=0x0210 S99INFO=0x0000
DatasetHandlerÝE¨: BPXWDYN command was: "alloc fi(SYS00007) reuse msg(2) da('HS.
DatasetHandlerÝE¨: Dataset HS.XXXX039D.WKLD.RPT.DAEH open error: EDC5000I No err

If I check the SMF 30 record of the above job in the SMFLOG screen of SYSVIEW,
I can see that “Address space identifier is 00A2”.

So the COZBATCH utility job step complains, it has contention with the same job that started it.

SYSVIEW 17.0 TEST ------------- SMFLOG, SMF Log ----------- 2023/01/21 03:01:06
Command ====> Scroll *===> PAGE
------------------------------------------------ Lvl 2 Row 1-12/25 Col 1-79/223
LogStream TEST150.SMFDATA.SMFD.TEST Retention 5 days
Available 02:01:41 2023/01/12 to 02:55:25 2023/01/21
Searched 20:08:23 2023/01/20 to 20:08:33 2023/01/20
Displayed 20:08:29 2023/01/20 to 20:08:33 2023/01/20
Options Lines 25 Limit 1000000 Period NONE
-------------------------------------------------------------------------------
Cmd Date Time Type SubType SysID SSID Resource
___ 2023/01/20 20:08:29 30 4 TEST JES2 ID=JOB10445 Job=XXXX039D Step=E


We have tried adding FREE=CLOSE on the DD that creates the dataset, and adding DSENQSHR=ALLOW to the jobcard, but the job still fails. We have found that the jobs fail only if a step references the same dataset (DISP=SHR) after the COZBATCH step. Job runs fine on z/OS 2.4 but fails on 2.5 system.

Anyone else experiencing this after upgrading z/OS to 2.5 (from 2.4).
Post Reply