Defining Unique CONNX Environment Variables per Started Task/Batch Job

To define CONNX environment variables specific to a single Started Task/Batch Job using a PDS member such as CNXPARMS, create a new member in the CONNX.STASK.CNTL PDS, and enter the environment variables as =variable=value. Next, change the Started Task/Batch Job JCL symbolic parameter CNXPARMS to the new member name; for example:

//CNXPARMS=CNXPARMZ

which substitutes as:

//CNXPARMS DD DSN=CONNX.STASK.CNTL(CNXPARMZ)

Defining unique CONNX environment variables per Started Task/Batch Job in the same CNXCFG VSAM KSDS is not supported. To do so, define separate copies of the CNXCFG VSAM KSDS for each started task/batch job, and update the execution JCL to point to the new CNXCFG VSAM KSDS. For example, to override the default CNXCFG DDNAME in the execution JCL:

//CNXCFG DD DSN=CONNX.STASK.CNXCFG.NEW,DISP=SHR

The REXX exec file CNXCFG supports overriding the CNXCFG VSAM KSDS file name via the following syntax:

cnxcfg f(“fpref”.cnxcfg)

From the ISPF Command Shell (usually ISPF main menu option 6):

Implicit:
cnxcfg p(variable value) f(CNXCFG data set name)

Verbose:
exec 'CONNX.STASK.CNTL(CNXCFG)' 'p(variable value) f(CNXCFG
data set name)'

From any ISPF command line:

Implicit:
tso cnxcfg p(variable value) f(CNXCFG data set name)

Verbose:
tso exec 'CONNX.STASK.CNTL(CNXCFG)' 'p(variable value)
f(CNXCFG data set name)'

For IDCAMS DELETE / DEFINE control records and execute JCL for the CNXCFG VSAM KSDS, refer to members IDCCNX0, CNXIDC, and @INST of CONNX.STASK.CNTL.