System automation
System automation of z/OS® software usually involves trapping messages that are issued to the z/OS console and performing actions in response to those messages. For example, to confirm that a IBM® z/OS Connect server was started or shutdown successfully.
zosConnect-2.0 Applies to zosConnect-2.0.
Specifying IBM z/OS Connect messages to be written to z/OS operator console
By default, IBM z/OS Connect logs all messages to the
UNIX System Services file messages.log,
and only a subset of these messages are written to the z/OS
console. However, the server configuration file element zosLogging can be used to
specify additional server messages to be logged to the z/OS
console. For more information about the zosLogging server configuration element,
see z/OS Logging
(zosLogging) in the WebSphere® Application
Server documentation.
For example, you might find the following messages useful.
- BAQR7000I: z/OS Connect API archive file apiName installed
successfully.
This message is zosConnect-2.0 specific and indicates that an API was installed successfully.
- SRVE0250I: Web Module z/OS Connect has been bound to default_host.
CWWKT0016I: Web application available (default_host): http://hostname:port/
These messages indicate that a IBM z/OS Connect server started successfully.
- CWWKE1101I: Server quiesce complete.
This message indicates that a IBM z/OS Connect server shutdown successfully.
<zosLogging enableLogToMVS="true"
wtoMessage="BAQR7039E,BAQR7042E,BAQR1108E,GMOBA0113E,GMOBA0108E,BAQR0660E,BAQR0661E,BAQR0662E,BAQR0663E,BAQR0664E,BAQR0558E,SRVE0250I,CWWKT0016I,CWWKO0219I,CWWKE0939I,CWWKF0011I,CWWKB0001I,CWWKE1101I,CWWKG0014E,CWPKI0016W,CWPKI0017E,CWWKE1200W,FFDC1015I"/>N 4000000 MVxx yyddd hh:mm:ss.sss JOBnnnnn nnnnnnnn +CWWKE0001I: The server serverName has been launched. N 4000000 MVxx yyddd hh:mm:ss.sss JOBnnnnn nnnnnnnn +BAQR7000I: z/OS Connect API archive file apiName installed successfully. N 4000000 MVxx yyddd hh:mm:ss.sss JOBnnnnn nnnnnnnn +CWWKF0011I: The server serverName is ready to run a smarter planet. N 4000000 MVxx yyddd hh:mm:ss.sss JOBnnnnn nnnnnnnn +SRVE0250I: Web Module z/OS Connect has been bound to default_host. M 4000000 MVxx yyddd hh:mm:ss.sss JOBnnnnn nnnnnnnn +CWWKT0016I: Web application available (default_host): E 870 nnnnnnnn http://hostname:port/
N 4000000 MVxx yyddd hh:mm:ss.sss JOBnnnnn nnnnnnnn +CWWKB0001I: Stop command received for server serverName. N 4000000 MVxx yyddd hh:mm:ss.sss JOBnnnnn nnnnnnnn +CWWKE1101I: Server quiesce complete.
CWWKB0111I: IBM Corp product z/OS Connect EE Unlimited version vv.rr.mm successfully deregistered from z/OS. CWWKE0036I: The server serverName stopped after m minutes, s.sss seconds.
Using IBM Tivoli System Automation for z/OS with IBM z/OS Connect
IBM Tivoli® System Automation for z/OS can be used to trap and respond to z/OS console messages issued by IBM z/OS Connect servers to keep them highly available.
*IBMCOMP add-on policy, similar to sample solutions for
products like IMS, CICS®,
Db2®, and others. For more information, see the APAR
problem description and Using SA z/OS Sample
Policies in the IBM
Tivoli System Automation for z/OS, Version 3.5 documentation. With IBM System Automation for z/OS V3.5 APAR OA51440, messages CWWKB0001I,
CWWKF0011I, CWWKT0016I, and CWWKE1101I are used
to automate and monitor IBM z/OS Connect. This automation
also uses a pre-defined IBM z/OS Connect configuration
that is provided by the *IBMCOMP add-on policy.