Purpose
The view_log command allows the log for the specified job to be viewed.
Parameters
- job_name
- Name of the job to be viewed.
- dir
- [Optional] Directory where the log files are written.
- filename
- [Optional] Name for the file when saving the log. This file will be overwritten if a file of the same name already exists.
- security_username
- [Optional] User ID of the super user or authorized Viewpoint user. The user ID of the super user is dmcl_admin and cannot be changed.
- security_password
- [Optional] Password for the super user or authorized Viewpoint user.
- security_password_encrypted
- [Optional] Encrypted password for the super user.
- broker.url
- [Optional] You may enter a broker URL to overwrite the default value specified in the commandline.properties file in order to connect to a different ActiveMQ server (and therefore a different daemon) at runtime.
- broker.port
- [Optional] You may enter a broker port to overwrite the default value specified in the commandline.properties file in order to connect to a different ActiveMQ server (and therefore a different daemon) at runtime.
Usage Notes
A log file for the specified job is generated only if that job failed or the log_level parameter was set to a value other than 0 when running the create or move command.
XML File Example
For the view_log command, type datamove view_log -f parameters.xml.
In the following example, the parameters file specifies that Data Mover writes logs for job 12315DFHJKS to /home/datamover/logs/12315DFHJKS_log.txt.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <dmViewLog xmlns= "http://schemas.teradata.com/dataMover/v2009" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schemas.teradata.com/unity/datamover.xsd"> <job_name>12315DFHJKS</job_name> <dir>/home/datamover/logs</dir> <filename>12315DFHJKS_log.txt</filename> </dmViewLog>