Start the Node server before starting the Liberty server.
Before you begin
This task must be completed by the ID that starts the IBM Z Database Assistant Node.js and Akira Liberty servers.
About this task
The Node server must be up and running in order to support the Liberty processes that execute on
startup.
Procedure
To start IBM Z Database Assistant from a
JCL procedure:
- To start the Node server from a proc, use the JCL contained in the file
hlq.SAURSAMP(AURND).
To start the Node server, use the following
z/OS® SDSF
command:
/S AURND
where AURND is the default name for the proc.
See the comments inside AURND and AURNDP for
instructions on how to customize them for your environment.
Note: When starting the
IBM Z Database Assistant
processes from JCL, the processes will no longer run under the OMVS subsystem type. Instead, the
subsystem type will be changed to STC.
Verify that your WLM settings are appropriate for these
started tasks when running under the STC subsystem type.
- To start the Liberty server from a proc, use the JCL contained in member
AURLBTY. Modify the CONFIG_DIR variable within the proc to
point to the ZDBA home directory.
Then start the proc with the following command:
/S AURLBTY
where AURLBTY is the default name for the proc.
See the comments in the JCL for instructions on how to customize the JCL for your
environment.
(Optional) To start IBM Z Database Assistant from USS:
- If you want to start IBM Z Database Assistant
from USS rather than a JCL procedure, go to the $ZDBA_HOME/scripts directory
and run the start_all_servers script to start the IBM Z Database Assistant user interface and services.
/start_all_servers.sh
Note: This script starts both the Liberty and Node servers.
To stop IBM Z Database Assistant from
JCL:
- To stop IBM Z Database Assistant from JCL, see
Stopping the Liberty and Node.js servers with started task procedures.
To stop IBM Z Database Assistant from
USS:
- To stop IBM Z Database Assistant from USS, see
Stopping the Liberty and Node.js servers from USS.