The DSNPARMS DD card (for DB2 users only)
DB2 applications using QUICKSTART can use the TSO, IMS or CALL Attach to DB2. The user should place highest in the STEPLIB concatenation the library containing the DSNHLI module for the appropriate attach facility to DB2. The QUICKSTART Load Library contains DSNHLI for BATCHCAF, QUICKSTART's CALL Attach Facility. BATCHCAF is discussed later in this section.
API Mode applications that use BATCHCAF are required to identify the DB2 Subsystem and Plan name using the DSNPARMS DD card. Transparent Mode applications must use BATCHCAF, and can either use the DSNPARMS DD card to identify the DB2 Subsystem and Plan name, or use QSCTRL1 control cards as discussed in The-QSCTRL1-DD-card.
The //DSNPARMS DD card must be added to the job step with a dataset name which contains both the DB2 Subsystem and Plan name. To comply with any installation naming conventions, this dataset name can have any valid High Level Qualifier (HLQ). BATCHCAF skips the HLQ when parsing the dataset name for the DB2 SubSystem Name and the Plan Name. For example:
.
.
.
//DSNPARMS DD DSN=hlq.db2subsystemname.planname.jobname,
// UNIT=SYSDA,SPACE=(TRK,0)
Note that the dataset never actually occupies any space, and is not retained after the Step has completed execution. An example of such a dataset name would be:
This example would cause BATCHCAF to “ATTACH” to the DB2 SubSystem named DB2T and “OPEN” the Plan named PLAN0001. The job name on the end of the dataset name is ignored by QUICKSTART, but is specified to make the dataset unique to avoid possible contention.
Also note that the number of dataset name high level qualifiers that are skipped to find the DB2 Subsystem name is installation dependent. See CONFIGURATION in the QSMENU CLIST to view your site's installation settings.
Optionally, the plan name can be followed by '.PKGSET.packagesetname', where packagesetname is a name up to 8 characters long. If present, BATCHCAF will issue an 'EXEC SQL SET CURRENT PACKAGESET = packagesetname' as the first statement. This provides the ability for two users to access the same plan with different versions of the program or to different table qualifiers. Example:
Related topic