HiRDB Dataextractor Version 8 Description, User's Guide and Operator's Guide

[Contents][Index][Back][Next]

6.2.2 Starting and terminating HiRDB Dataextractor when using OSI

This section explains the HiRDB Dataextractor startup and termination procedures when the OSI protocol is used to execute data extraction, data import, and file creation with a mainframe database.

When the OSI protocol is used, the host used to start HiRDB Dataextractor depends on the HiRDB Dataextractor facility being used. Table 6-1 shows the host used to start HiRDB Dataextractor when the OSI protocol is used.

HiRDB Dataextractor is started by the startup user. You should note the following:

* If the system manager is not connected with XDM/XT by the OSI protocol, the TCP/IP protocol is used to establish communication between the system manager and the target server to which data is sent. For this reason, to start and terminate the HiRDB Dataextractor running on the system manager, use the procedures described in 6.2.1 Starting and terminating HiRDB Dataextractor when using TCP/IP.

Organization of this subsection
(1) Starting HiRDB Dataextractor when using OSI
(2) Terminating HiRDB Dataextractor when using OSI

(1) Starting HiRDB Dataextractor when using OSI

When the OSI protocol is being used, you can start HiRDB Dataextractor either automatically or manually.

(a) Automatic startup

To start HiRDB Dataextractor automatically, you must register to /sbin/rc a script for starting the shell that executes the xtstart command.

Environment setup procedure for automatic startup
  1. Creating the execution shell for the xtstart command
    Create the execution shell for the xtstart command in any directory.
  2. Creating the startup script to be started from rc
    In /sbin/init.d, create the startup script for shell execution that was created in 1.
  3. Registering the startup script
    Register the startup script to sequencer-directory/sbin/rc*.d (* (execution level): 0-n) according to the execution level and the naming conventions. The sequencer directory must consist of a symbolic link to the startup script found in /sbin/init.d.
    For naming conventions of the file to be specified, see the rc reference.

Example
 
ln -s /sbin/init.d/XTS /sbin/rc2.d/S600XTS
 
Note: The underlined sections must be the same.

Note
Because a 3-digit number is used for sequencing the script in the sequencer directory, set the number so that it is executed after XNF is started. For details about the execution level, see the manual of the OS being used.

Example of creating the xtstart command execution shell
 
#!/sbin/sh
#
# HiRDB Dataextractor Start
#
export XTTEMPNAM=0
/opt/HIRDBXT/bin/xtstart /HIRDBXT/user01/xtenv1 /HIRDBXT/user01/xtosi1

Example of creating /sbin/init.d/XTS (when the path name of the xtstart command execution shell is /HIRDBXT/user01/xts)
 
#!/sbin/sh
#
# HiRDB Dataextractor Start script
#
 
PATH=/usr/sbin:/usr/bin:/sbin
export PATH
 
rval=0
 
case $1 in
'start_msg')
  echo "Starting HiRDB Dataextractor"
  ;;
 
'stop_msg')
  echo "Stopping HiRDB Dataextractor"
  ;;
 
'start')
  for start_file in ls /HIRDBXT/user01/xts  ; do
    if [ -x ${start_file} ]  ; then
      ${start_file}
      if [ $? !=0 ]  ; then
        rval=1
        break
      fi
    fi
  done
  ;;
'stop')
  ;;
 
*)
  echo "usge: $0 {start|stop|start_msg|stop_msg}"
  rval=1
  ;;
esac
 
exit $rval
(b) Manual startup

You can start HiRDB Dataextractor manually in the following cases:

Specification format
/opt/HIRDBXT/bin/xtstart environment-variable-information-setup-filename communication-configuration-definition-information-filename
(c) Notes

(2) Terminating HiRDB Dataextractor when using OSI

HiRDB Dataextractor terminates processing when it receives the SIGTERM signal.

To terminate only HiRDB Dataextractor:

  1. Obtain HiRDB Dataextractor's process ID from a message output to the log file.
  2. Use kill(1) to send SIGTERM to HiRDB Dataextractor.