Output from Windows batch command shown in incorrect format in JOBS Report

book

Article ID: 84573

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine AUTOMIC WORKLOAD AUTOMATION

Issue/Introduction

Error Message :
N/A

Submitting batch commands on a Windows Agent results in additional characters such as question marks (?) being displayed in the output Report.

Depending on the tool being referenced in the batch command, it is possible to see the Windows command displayed incorrectly in the Job Report.

Examples:

Execute the Windows command:
“wmic os get lastBootUpTime”

Output from the Windows command:
LastBootUpTime 20180305094703.109999+060

Output from the Automation Engine (AE) 11.2 using a Windows Agent also running version 11.2:
LastBootUpTime 20180305094703.109999+060

The same command executed from AE 12.1 using a Windows Agent on 12.1, 11.2 or 10.0.8 results in the following output in the Job Report:  
L?a?s?t?B?o?o?t?U?p?T?i?m?e? ? ? ? ? ? ? ? ? ? ? ? ? ? 

?2?0?1?7?1?2?1?4?1?4?4?7?0?6?.?1?2?5?5?9?9?+?0?6?0? ? ? 

?

Cause

Cause type:
By design
Root Cause: AE uses single byte code pages and cannot display multi-byte-codes (i.e. UTF-8) in the output correctly.

Environment

OS: Windows

Resolution

Use command line tools with single byte output or commands that output to ANSI.

The WMIC command outputs to UNICODE, while the standard Windows batch commands output to ANSI. 

 

Fix Status: No Fix

Additional Information

Workaround :
Extend the command by redirecting the double byte output to another command that produces single byte output.

Example:
“wmic os get lastBootUpTime | more”