Neoview Database Administrator's Guide (R2.2)

User Name and Password
You can specify environmental variables for the user name and password so that you do not
have to store the user name and password as part of any command files that you use.
For example, if you use the environment variables USER and PSW to pass in the user name and
password, any loader tasks could refer to these environment variables as -un $USER and -pw
$PSW. You must set environment variables prior to executing the load command, as shown in
this example:
export USER=roledba
export PSW=xyz
Use these variables in the start task command:
gcmd -rt START_TASK -tk LOADMASTER -un $USER -pw $PSW
Multi-Line Task Commands
If you want to set up a task command on multiple lines to make it more readable, you can use
the "\" character at the end of each line. Here is an example that requires multiple lines and uses
the "\" line-continuation character:
gcmd -rt CONFIG_TASK_LOAD -tk MYTASK1 \
-gs atnsk03 -tn NEO-CMSERVER \
-un user1 -pw User9999 \
-ii /home/user1/test/data/data01 -oi CAT.SCH.T1 \
-fd '|' -of N
You can view syntax help by entering this command at the prompt:
gcmd -h -rt CONFIG_TASK_LOAD
Logs
gcmd logs all messages for commands in the file gcmd.log.
The default location for the log file is /opt/tandem/genus/gel/log/gcmd.log. You can
confirm its location by viewing the gelserver.config.xml file.
The log directory has a load directory and an extract directory. For a standard Loader system
installation, the task instance logs for load tasks are stored in the directory location
/opt/tandem/genus/gel/log/load.
The name of the task instance log files on the Linux and Neoview systems is
task-name.task-instance-name.log.
For example, suppose you start this task:
-rt START_TASK -tk LOAD_TASK1 -ti LOAD_TASK1_RUN1 -un user1 -pw
mypassword
The task instance’s log name is:
LOAD_TASK1.LOAD_TASK1_RUN1.log
If you do not specify a task instance name, a system-generated task instance name is used:
LOAD_TASK1.LOAD_TASK1212017497848504080.log
If a task instance log file exists from a previous successful execution of the same load task with
the same task instance name, the existing task instance log file will be renamed by appending
the modification timestamp to the task instance log file name. For example, if the task instance
log file name was DAILY-LOAD.OCT01.log, it will be renamed to
DAILY-LOAD.OCT01.1og.2007613192033, where 2007613192033is a modification
timestamp. This also applies to any files with rejected records.
Logs 115