Allow Override of Allocated Data Sets in Batch CLIST Input (DSNTIDOM) in DB2 Migration/Install

In Db2 for z/OS, the DSNTIDOM input member defines parameter values that control how the installation/migration/function‑level activation CLIST generates tailored JCL jobs and artifacts when run in batch mode. DSNTIDOM corresponds to the panel fields normally entered interactively via the DB2 installation CLIST (DSNTINST) but is used for background generation of jobs and datasets.

Currently, only the “optional parameters” listed in DSNTIDOM support overrides by assigning a value and removing the leading asterisk in the override file. SMP/E‑allocated data sets such as the LOAD library, SDSNLINK, and SDSNLOD2 are not considered optional parameters and therefore cannot be overridden in the Batch CLIST; they are forced to follow the standard SMP/E naming convention (prefix.SDSN*.suffix) as determined by the DSNTIPA1 / DSNTIPAP panels.
IBM

This restriction makes it difficult to resolve specific SMP/E data sets in customized or non‑standard deployment scenarios without manual editing or workaround step

Proposed Enhancement:
Extend DSNTIDOM’s override capability to include SMP/E‑allocated data sets such as:

• LOAD library

• SDSNLINK library

• SDSNLOD2 library

• SDSNEXIT library

• Other SMP/E allocated data sets used in installation, migration, or function‑level activation CLIST flows

This enhancement would follow the same override methodology used for existing parameters (assign value + remove leading asterisk), enabling these data sets to resolve to user‑specified targets when running the CLIST in batch mode.

Benefits:

• Enables consistent and predictable resolution of SMP/E data sets in automated environments.

• Reduces manual intervention, temporary edits, and workarounds when generating jobs through Batch CLIST.

• Improves flexibility for non‑standard library layouts (e.g., custom repository names, isolated test environments).