Starting Your Product › Preparing to Start CA Gen › Preparing to Start Host Encyclopedia › DB2 Secondary Authorization IDs › TICGENB2 and TIRGENB2 Skeletons

TICGENB2 and TIRGENB2 Skeletons

The DB2 secondary authorization variable is passed through OWNERID. Variables are passed as control card input through the DATAIN DD Statements. Change TICGENB2 and TIRGENB2 as follows so that the DB2 secondary authorization variable is available to background installation:

Follow these steps:

1. Create a copy of TICGENB2 and TIRGENB2 in a library concatenated ahead of the CA Gen SLIB library.
2. Add the OWNERID variable to the copied TICGENB2 and TIRGENB2. See the samples of TICGENB2 and TIRGENB2 that follow.

The following code sample is an example of passing OWNERID as a variable in TICGENB2:

TICGENB2
)TB 10 14
OWNERID!SHR!&OWNERID
MODLNAME!SHR!&MODLNAME
TISNAME!SHR!&TISNAME
TICSLIB1!SHR!&TICSLIB1
.
.
//*                           END OF RUNTIME VARIABLE INPUT

An example of passing OWNERID as a variable in TIRGENB2 is shown next.

TIRGENB2
)TB 10 14
OWNERID!SHR!&OWNERID
.
//*                          END OF RUNTIME VARIABLE INPUT

Each line after the line beginning with )TB contains the name of an ISPF variable, the pool to which it belongs, and the value for that variable being passed to batch code generation.