If you install BDT in a JES3 complex, you will have to add the following
statements to the JES3 initialization stream:
- A CONSOLE statement, which requests JES3 to create a table entry that
is required for BDT console support.
- A SYSID statement with the NAME parameter to define the default BDT node
to JES3. The default BDT node is the node that executes (1) any BDT commands
that do not request a particular node via the SY(node-name) prefix and (2) any file-to-file transactions that do not request a
particular node via the SYSTEM parameter. The NAME parameter on the JES3 SYSID
statement must match the name on one of the following BDT SYSID statement
parameters:
- The NAME parameter if the BDT subsystem has a file-to-file node, without
or in addition to a SNA NJE node.
- The NJENAME parameter if the BDT subsystem has only a SNA NJE node.
- If BDT has the SNA NJE feature, one or more NJERMT statements with:
- The BDTID parameter to identify the BDT node that receives SNA NJE transactions.
The name specified on the BDTID parameter must match the name on the NAME
parameter of JES3’s SYSID statement.
- The NAME parameter to identify remote SNA NJE nodes to JES3. The name
specified on the NAME parameter must match the name on the N parameter of
BDT’s BDTNODE statement.
These JES3 statements are explained in the
z/OS JES3 Initialization and Tuning Guide.
To have these statements take effect, the JES3 operator must warm start
or cold start JES3.