A DFSMS System‑Determined Blocksize (SDB) issue occurs after migrating to z/OS 2.5, 3.1, or 3.2 with files allocated by SAS


After upgrading to z/OS 2.5, 3.1, or 3.2, issues might occur with DFSMS‑controlled data sets that are allocated by SAS without explicitly specifying DCB attributes for BLKSIZE.

In these environments, z/OS uses System‑Determined Blocksize (SDB) to automatically calculate an optimal block size when BLKSIZE is omitted.

Symptoms

When SAS allocates a new data set without a BLKSIZE value, the following symptoms occur:

S013‑34

S002‑30

These abends occur because the BLKSIZE determined by SDB is not always compatible with programs that expect traditional BLKSIZE values.

Workaround

IBM has released Program Temporary Fixes (PTFs) to correct this behavior. Apply the appropriate fix for your z/OS release:

z/OS ReleasePTF
2.5UJ97198
3.1UJ97197
3.1UJ98495

Install the relevant PTF to ensure consistent BLKSIZE handling for SAS‑allocated DFSMS data sets and prevent the abends described above.