sing wsmancli, when the response XML is invalid (such as due to
invalid characters) an error is displayed with only a partial view of
the XML and no other information that could tell us where exactly the
problem is.

In debug mode (using -d option), it would be useful if the tool could
dump the raw XML for further analysis before it could be interpreted
by libxml functions.

Patch by Chris Poblete

This fixes the default port setting to match wsmc_create() call.

(upstream issue 3257661, Zoltan Micskei)

Using wsmancli 2.2.5, we also got a segmentation fault.

Analysis of the code found that output_file is NULL and is being used.
This is occurring when there are multiple instances returned and pull
operation is done and output file is not defined.

Patch by Chris Poblete

From: Kamil Dudka <kdudka@redhat.com>

wsman client doesn't work correctly on some architectures (ppc, s390x).
It ignores the given port number as well as all integral parameters.

The integer parsing function does not return the value but passes it
by writing through a pointer, assuming long int target.

In an enumerate operation where output to file is requested and the
response require more than one pull, only the last pull is saved to
file.  The rest of the response is overwritten.

Our proposal solution is for each pull response, it is saved to a file
with numbered suffix. This is only applicable to an enumerate
operation and an enumeration context is returned.

Also included is a minor fix to file open from read/write to write
mode. I find no reason for the operation to read the output file.