That data is encoded with UTF-16LE. Although I'm not sure if there's a more elegant way to solve this because I'm not familiar with the "uemcli" command, by adding the following code to the example I posted above, you will get the properly decoded Perl string in $str.

use Encode qw/decode/;
my $str = decode('UTF-16', $out, Encode::FB_CROAK);
[download]

Hi Haukex,

All thanks to your clever code, I am finally able to capture the output to text files too!!. Here's the addition to your code.

my $aref_cmd1= ['uemcli','-d',$vnxe_ip,'-u',$username,'-p',$password, 
+'/sys/general','show','-detail'];
my $aref_cmd2 = ['uemcli', '-d', $vnxe_ip, '-u', $username, '-p', $pas
+sword, '/env/bat', 'show', '-detail'];
my $aref_cmd3 = ['uemcli', '-d', $vnxe_ip, '-u', $username, '-p', $pas
+sword, '/env/ps', 'show', '-detail'];

run3 $aref_cmd1, undef, \my $out1;

run3 $aref_cmd2, undef, \my $out2;
run3 $aref_cmd3, undef, \my $out3;

use Encode qw/decode/;
my $str1 = decode('UTF-16', $out1, Encode::FB_CROAK);
print "$str1\n";

my $textfile2 = "textfile2.txt";
open (my $fh2, '+>', $textfile2) or die "Cannot open file.$!";
my $str2 = decode('UTF-16', $out2, Encode::FB_CROAK);
print $fh2 $str2;
[download]

Here, the cmd1 prints to screen, cmd2 can be output to a file. cmd3 I am yet to work on. Thank you once again..

Of course, a loop would be a bit more elegant, here's just one example.

use warnings;
use strict;
use IPC::Run3;
use Encode qw/decode/;

my @outputs;
for my $loc ('/sys/general', '/env/bat', '/env/ps') {
    run3 ['uemcli','-d',$vnxe_ip,'-u',$username,'-p',$password,
        $loc,'show','-detail'], undef, \my $out;
    my $str = decode('UTF-16', $out, Encode::FB_CROAK);
    push @outputs, $str;
}

print $outputs[0], "\n";
open my $fh, '>', $textfile or die "$textfile: $!";
print $fh $outputs[1];
close $fh;
[download]

Update: Note that both prints in this example assume you don't have any Unicode (non-ASCII) characters in the strings (as your sample data shows). If you did, you'd need to set an encoding on the filehandles you're writing the data to - that's STDOUT, with for example use open qw/:std :utf8/; or several variations on that, and for filehandles, for example open my $fh, '>:encoding(UTF-8)', $filename or die "$filename: $!";.

Simpler:

open (my $fh2, '>:encoding(UTF-16)', $textfile2)
[download]

Hi Haukex,

Yes, it works and perfectly shows the output!! Thank you so much.

All I now how to figure out is how to put this my script so that I get the desired output. Quite frankly I'm not able to make much out of the clever stuff you wrote. You've wrapped the command in what I think is a anonymous aref along with undef, \my $out. Wish there were an easier way to do this, but , that is something for me to figure out. Thank you once again.

You've wrapped the command in what I think is a anonymous aref along with undef, \my $out.

Yes, all of this is part of the API of IPC::Run3, its documentation explains it. I used an arrayref because this will cause the module to do its best to avoid the shell (which is a slightly complicated topic on Windows, but at least newer versions of the module will use Win32::ShellQuote to help with some of the issues). The undef causes the child process to inherit STDIN from the parent, and \my $out causes the command's STDOUT to be stored in that variable. Then, I use Encode to decode the data from the command, which is encoded in UTF-16LE; note that I specify the encoding to simply be UTF-16 because the module is smart enough to use the BOM that is part of the output you showed.