Redwood Documentation

Product Documentation

 

›Command Line Tools

RunMyJobsPlatform Agents

External Platforms

  • Connecting Redwood Server to External Platforms

Credentials

  • Storing Credentials
  • Credential Protocols

Platform Process Servers

  • On-site Platform Process Servers
  • Cloud Platform Agents
  • Using the Wizard to Create Process Servers
  • Configuring Platform Agents
  • Spool Host Agents
  • The Environment of Platform Agent OS Processes
  • Processing Platform Processes
  • Process Server Services
  • Configuring Agentless Process Servers
  • Automatically Updating Platform Agents
  • Enabling TLS
  • Creating Monitoring Checks
  • Configuring Load Balancing on Platform Agents
  • Platform Agent Registry Entries
  • Monitoring Servers with Platform Process Servers

UNIX Agents

  • UNIX Process Servers
  • UNIX Process Server Configuration Data
  • File Events on UNIX
  • Creating UNIX Process Servers (Advanced)
  • Choosing a User Switching Security Mode
  • Controlling Unix Platform Agents
  • Uninstalling Redwood Server Platform Agents from UNIX

Windows Agents

  • Creating a Microsoft Windows Process Server
  • File Events on Microsoft Windows Process Servers
  • Configuration of a Microsoft Windows Process Server
  • Managed Services
  • Configuring Platform Agents on Microsoft Windows
  • Automating Windows tasks that require a desktop window
  • Uninstalling Redwood Server from Microsoft Windows

Agent Definition Types

  • Using the BASH Definition Type
  • Using the KSH Definition Type
  • Using the CSH Definition Type
  • Using the Perl Definition Type
  • Using the Python Definition Type
  • Using the PowerShell Definition Type
  • Using the Visual Basic Script Definition Type
  • Using the CMD Definition Type
  • Using the R Process Definition Type
  • Using the DCL Definition Type
  • Using Platform Definition Types
  • Using the OS Native Definition Type
  • Microsoft Windows Definition Types
  • Using the SQLPLUS Definition Type
  • Using the FTP Definition Type
  • Using the Groovy Definition Type

Command Line Tools

  • Command Line System Tools
  • jtool
  • jcat
  • jdescription
  • jevent
  • jecho
  • jftp
  • JFTP Return Codes
  • jgetcredential
  • jgetfile
  • jgetpar
  • jjoin
  • jlink
  • jlog
  • jmail
  • jmessage
  • jmonitor
  • jputfile
  • jregister
  • jrfc
  • jscp
  • jtool screenshot
  • jscript
  • jsecret
  • jsleep
  • jsplit
  • api-tool.jar

OpenVMS Process Servers

  • Creating HP OpenVMS Process Servers
  • Installing the Platform Agent on HP OpenVMS
  • Configuring HP OpenVMS Process Servers
  • File Events on HP OpenVMS
  • HP OpenVMS Definition Types

AS/400 Connector

  • IBM AS/400 Connector Architecture
  • Setting up the IBM AS/400 Connector
  • Creating an IBM AS/400 Process Server
  • Files on AS/400 Raise Events
  • Using the AS/400 Definition Type
  • Redwood Server OS Support
  • IBM z/OS Definition Types
  • Using the JCL_FTP Definition Type
  • IBM z/OS System Tools

Reference

  • Balancing the Load
  • Credential Protocols
← jlinkjmail →

jlog, jtool log

A platform agent tool used to log using the Redwood Logging format. You can call it as jlog or jtool log

Syntax

jlog [-h|-?|-help] [-l <loglevel>] [-f <logfile>] [-e|-exit <value>] [-c|-category <category>]
     [-n|-name <name>] <level> <message> ...
ArgumentDefaultDescription
-h, -?, -help

Show usage and exit.
-l <loglevel>${JCS_LOGLEVEL:-info}Set the logging level; defaults to environment variable ${JCS_LOGLEVEL} or info when the environment variable is not set.
-f <logfile>${JCS_LOGFILE:-stderr}Log to file instead of stderr; defaults to environment variable ${JCS_LOGFILE} or stderr when the environment variable is not set.
-j, -job-context

Obtain environment from job-context
-e,-exit <value>

Exit with given return code
-c, -category <category>${JCS_LOG_CATEGORY:-custom.log}Category
-n, -name <name>${JCS_LOG_NAME:-jlog}Name of the component
<level>

Log level
<message>

Message to log

Process Server Parameters and Environment Variables

You use the ${<name>} syntax to specify process server parameter values; note that if you shell interprets ${<val>} then you will have to escape the expression according to your shell. Any process server parameter that has remote set to true can be accessed in this way. The special ${LISTALL} variable contains a list of all environment variable and process server parameters.

jtool log -n myTool -j 'DataRootDirectory: ${DataRootDirectory}'

This can be used outside of job-context, however, only environment variables are available.

note

jlog expects a correctly escaped [environment] variable name for your shell, you must ensure the shell does not evaluate the variable. Numerous examples are available below.

Example

The LogLevel process server parameter is set to jlog.my.category=debug

The following UNIX shell example shows how to log

jlog -n myproject -c my.category debug "This will be printed to the log"

jlog -n myproject -c my.category info "This will be printed to the log"

jlog -n myproject -c my.other.category debug "This will NOT be printed to the log; the category does not match"

jlog -n myproject -c my.category trace "This will NOT be printed to the log, the verbosity level is too high"

jlog -n myproject -c my.category info "This will be printed to the log, mentioning the value ${BustWatchDirectory} of the process server parameter with the name BustWatchDirectory"

See Also

  • Command Line System Tools
← jlinkjmail →
  • Syntax
  • Process Server Parameters and Environment Variables
  • Example
  • See Also
Docs
Getting StartedInstallationFinance InstallationConcepts
TroubleshootingArchiving
Learn and Connect
Support Portal
BlogEventsResources
ISO/ IEC 27001 Information Security Management
Automate to be human

2023 All Rights Reserved |

Terms of Service | Policies | Cookies | Glossary | Third-party Software | Contact | Copyright | Impressum |