For
CICS BAC host mainframe components, you specify the language
you want use as follows:
- For the communication server, specify the LANGUAGE parameter as
described under Communication server runtime parameters
- For the batch request utility, specify the LANGUAGE parameter
as described under CICS BAC batch request utility runtime parameters.
- For CICS system console and job log messages, the language used
is the language in effect for the CICS BAC region startup processor
transaction at the time the CICS component starts.
- If you start the CICS component during CICS initialization through
a CICS PLTPI entry, CICS BAC uses the default language as specified
by the CICS NATLANG system initialization parameter.
- If you start the CICS component from a terminal using the KBKM
transaction, the language used is the language in effect for the user
signed on to the terminal at the time you issue the START command.
If the terminal does not have a signed-on user, CICS BAC uses the default
language for the region.
For CICS BAC KBKM transaction maps, CICS BAC uses the language
in effect for the user signed on to the terminal when the transaction
is issued. If there is no user signed on at the terminal, CICS BAC uses
the default language for the CICS region.
- For audit log messages, CICS BAC writes all audit log messages in
US English, regardless of the language in effect for the various components
at the time the messages are written.