Use the JDBC Service wrapper to control the JDBC server with batch jobs or shell commands. Four batch jobs are included in the sampjcl sub-directory of the CA IDMS Server HFS (referred to as /idmsdir):
Starts the JDBC server.
Stops the JDBC server.
Suspends the JDBC server.
Resumes the JDBC server.
These files can be customized and copied to an MVS PDS to facilitate job submission from MVS.
These jobs use BPXBATCH to run the corresponding shell scripts. The JDBC server process inherits the CPU time limit from the job that runs BPXBATCH to start it (member JSRVSTRT in the /sampjcl sub-directory). Set the CLASS and TIME parameters appropriately for the length of time that you plan to keep the JDBC server running.
Each example job has been coded so that the PARM parameter of the EXEC PGM=BPXBATCH statement specifies "nohup" and "& sleep 1." This is an IBM recommendation for running shell commands in batch. For more information, see the z/OS UNIX System Services User's Guide.
You can control the JDBC server with shell commands in the following format:
jsrv <command> [<jsrv options>] [-jvm] [<java options>]
The following commands are used to control the JDBC server:
Starts the JDBC server as a background process.
Stops the JDBC server.
Suspends the JDBC server.
Resumes the JDBC server.
Checks the JDBC server status.
Starts the JDBC server as a foreground process.
Displays usage information.
These commands are designed to run from the home directory of the CA IDMS Server installation and therefore must be prefixed with "bin/", such as bin/jsrv start. The commands invoke a shell script that sets the required environment variables (described earlier in the chapter "Configuring the Client on z/OS") and runs the JDBC server service wrapper. The service wrapper starts the Java VM and passes control to the JDBC server entry point. You can also enter the commands in the following form: jsrv.start, jsrv.stop, and so on.
You can override the run-time options from the configuration file by specifying them on the command line.
All options that follow "-jvm" are passed unchanged to the Java VM to allow specification of Java tuning and debugging options.
When started in normal mode, the JDBC server forks a new process and detaches from the terminal. All tracing and debugging is written to the log file specified in the configuration file. When started in debug mode, the JDBC server runs in the foreground and stays attached to the terminal. Pressing Enter shuts down the JDBC server. Tracing output can be displayed on the terminal, redirected to the standard output, or written to the trace file. Messages to the system log can also be echoed on the standard output.
Note: For detailed information about the command line options, see Using the JDBC Server in the chapter "Using the Java Client." For more information about customizing the sample JCL, see the chapter "Installing the Client on z/OS."
|
Copyright © 2009 CA.
All rights reserved.
|
|