Configuration parameters
The following table lists the description and values of the key parameters that you might want to change for your BMC II for z/OS connection.
Parameter | Description | Sample value |
|---|---|---|
Trace | Boolean indicator that specifies whether tracing is enabled |
|
TraceSrc | Specifies whether to display the source code file name and line number where trace message originated | YES or ON – display file name and line number NO or OFF – do not display file name and line number |
TraceConfigFileName | Path and file name for the integrationName.trace file Required when Trace=YES | //'hlq.connectionID.TRACONF' or //DD:BBIPARM(IIMTRCnn) |
TraceDefaultFileName | Default destination file to which trace messages are redirected from stderr, when the integration runs as a daemon or a service Required when Trace=YES | //'hlq.connectionID.TRACEOUT' |
TraceFileSize | Maximum size, in KB, of the trace messages file | 12000 |
TraceFileAppend | Specifies whether to append new trace messages to the existing message trace file when the connection is restarted | YES or ON –appends new messages to the existing trace message file (default) NO or OFF –empties the current trace message file |
LocaleConfigFileName | The file name where the LOCALE files are located. | //'hlq.LOCALE.CONF' or //DD:BBIPARM(IIMLCL00) |
EnableHeartBeats | Boolean indicator that determines whether the integration component uses the heartbeat signal |
|
HeartBeatInterval | Integer that indicates the number of seconds between heartbeats | 30 (default), 1 (minimum), no maximum |
ServerDirectoryName | The file name of the directory file | //'hlq.IIM.DIR' |
PersistencyEnabled | Boolean indicator for disk queuing of outbound events | Yes |
PersistencyLevel | Buffer mode used when the Default buffering mode is specified This parameter is enabled only when the PersistencyEnabled parameter value is Yes. | High, Low, None |
PersistencyFileName | Name of the file in which the buffered messages are stored The contents of the file are not deleted when the connection terminates unexpectedly. | //'hlq.connectionID.SENDQUE' |
PersistencyDisconnectRemovesMessages | Indicates whether messages written to the persistency file are deleted when the connection ends intentionally | No |
EnableRecvPersist | Boolean indicator for disk queuing of inbound events | Yes |
RecvBufferFile | Destination file to which incoming buffer events are sent | //'hlq.connectionID.RECVQUE' |
RecvBufferFileTemp | Destination file to which incoming buffer events are compacted | //'hlq.connectionID.RCVQUETM' |
SourceCodePage | Defines the character set used in translating the data from EBCDIC to UTF-8 or from UTF-8 to EBCDIC The value for SourceCodePage is comprised of the literal IBM followed by the three or four digit identifier for the character set, such as the value IBM1047 for the Latin 1 (1047) character set. See Source-code-page-reference for a list of character set identifiers. | IBM1047 (default) |
UseTCPIPStack | Specifies the job name of the TCP/IP stack. This parameter is put into the hlq.IIM.CONF file for each BIIZ connection. | UseTCPIPStack=jobName |
CertificateKeyring | Specifies the name of the key database file, SAF key ring or the z/OS PKCS #11 token. If CertificatePasswordFile is specified, then it is considered that this value is a name of a key database file. If SAF keyring is used then Biiz must be the owner to be able to access the private keys. If z/OS PKCS #11 is used then Biiz must be granted access to resource USER.tokenname in the CRYPTOZ class. |
|
CertificateKeyringStash | certificate data base password file - /home/biiz/biiz.sth |
|