About this task
There are several parameters that you can pass to the communication
server at its startup, all of which are optional. You can specify
communication server parameters using any combination of the following
methods:
- Allow the communication server to use its built-in defaults.
- Define your own values in CBKSRVR, which can be a member
of either a CBKPARMS data set, or a data set in the MVS™ logical
parmlib concatenation.
- Define your own values in the PARM string of the EXEC JCL statement.
The communication server searches for startup parameters, and processes
them, in the following way:
- Default values: CBKSMAIN first sets the
default values for each parameter and continues at step 2.
- CBKPARMS data set: The communication server
searches for a CBKSRVR member in the CBKPARMS data set, if present.
If the server finds a CBKSRVR member it uses any runtime parameters
in the CBKSRVR member to override the defaults. If the member is empty,
the defaults are not changed. When the communication server has finished
processing the CBKSRVR member, it continues at step 4.
- Logical parmlib concatenation: If the communication
server cannot find a CBKSRVR member in CBKPARMS, it searches for a
CBKSRVR member in the MVS logical parmlib concatenation.
If the server finds a CBKSRVR member it uses any runtime parameters
in the CBKSRVR member to override the defaults. If the member is empty,
the defaults are not changed.
- PARM string: The communication server reads
any parameters specified in the PARM string of the JCL EXEC statement,
and uses these to override default or CBKSRVR parameter values.
Note: If you want to use all default values, or
specify parameters in the PARM string only, do one of the following:
- Include an empty CBKSRVR member in the CBKPARMS data set. The
communication server skips to step 4 above when it finds an empty
CBKSRVR member.
- Authorize the communication server task to have READ access to
all the data sets in the MVS logical parmlib concatenation.
The communication server continues with step 4 if it cannot find a
CBKSRVR member. If the communication server does not have at least
READ access to the logical parmlib concatenation, the server fails
with a 913 abend.
All parameters can be truncated to their shortest unique character
string. However, be aware that a unique abbreviation for this release
of CICS BAC might not be unique in future releases. Therefore, you should
not use the shortest abbreviation for a parameter, especially when
the parameter is being stored in many different data sets.
- CBKID(name)
- Specifies the name for the communication server as a 1-8 alphanumeric
character name. Ensure that each communication server that you start
has a unique name within the MVS system.
If you omit this parameter, the name defaults to the job name of
the communication server address space.
- CICSMIRRORTRANS({CSMI | transid})
- Specifies the name of the CICS® mirror
transaction to be specified on EXCI requests issued by the communication
server. When the EXCI request is executed in the target CICS region, it runs under this transaction ID as an MRO mirror transaction.
- CSMI
- This is the normal CICS EXCI default mirror transaction
ID.
- transid
- Specifies the 4-character name that you want CICS to use as the name of the MRO mirror transaction when it executes
the EXCI requests it receives from the communication server. To avoid
confusion with other mirror transactions that might be running in
your CICS regions, you might want to choose a unique
ID to identify CICS BAC communication server mirrors. Define the appropriate
transaction ID in the CICS region for a CICS mirror
transaction, ensuring the following:
- The program associated with the transaction ID must be DFHMIRS
- The profile for the transaction ID must be DFHCICSA.
You might consider using the CICS-supplied CSMI transaction definition
as a basis for this transaction ID.
- LANGUAGE({ENU | JPN})
- Specifies the language used by the communication server for
console and job log messages. See CICS BAC national language support (NLS) for more
information. The values you can specify are:
- ENU
- US English
- JPN
- Japanese
Note: Specify the language parameter only on the PARM
string of the JCL EXEC statement for the communication server. The
parameter is ignored if it is specified in the CBKSRVR member of either
the CBKPARMS data set or the logical parmlib concatenation.
- TCPPORTNUM({56677 | number})
- Specifies the TCP/IP port number that the communication server
is to use to receive TCP/IP requests from the workstation client.
- 56677
- The default port number.
- number
- Specify the TCP/IP port number in the range 1 to 65535.
- TCPTIMEOUT({60 | number-of-seconds})
- Specifies the length of time in seconds after which
the communication server times out a request if it has not received
additional data.
- 60
- The default is 60 seconds.
- seconds
- Specify the time-out value in seconds in the range 1 to 99.
- TRACEOPTIONS({C0 | options})
- Specifies the types of trace entries you want CICS BAC to
create. There are eight trace entry types, each controlled by a single
bit in the TRACEOPTIONS hexadecimal byte flag. Specify this
option only at the direction of a Technical Support representative.
The
meaning of each bit position is as follows (bits from left to right):
Bit position |
Type of trace entry |
0 |
Module entry |
1 |
Module exit |
2 |
Module flow |
3 |
Module loop |
4 |
Module call |
5 |
Reserved |
6 |
Reserved |
7 |
Reserved |
- C0
- The hexadecimal value C0 is the default trace setting.
- options
- Specify the hexadecimal byte flag that represents the type of
trace entries CICS BAC is to create, as directed by a Technical Support
representative.
- TRACESIZE({1000 | number-of-entries})
- Specifies the size of the trace table in terms of the number
of entries to be traced for diagnostic purposes. Change this value
only at the direction of Technical Support.
- 1000
- The default trace size.
- number
- Specify the trace table size as requested by Technical Support.