Sometimes the jobscheduler_event.cmd doesn't store the event into the csv file even though the connection failed

Current Situation
The jobscheduler_event.cmd tries to send the event to the specified JobScheduler. If the connection failed to this JobScheduler then the event data are written into a csv file for later dequeueing. All environment variables with the prefix SCHEDULER_PARAM_ are added to the event data at the end of that line which is written into the csv file.

If the last SCHEDULER_PARAM_ parameter has a numeric value then this value is interpreted as a filedescriptor and the event data are written to stdout and not into the csv file

> set SCHEDULER_PARAM_TEST=5
> .\bin\jobscheduler_event.cmd -x 0 -i HELLO -e HELLO -s localhost -r 4711
JobScheduler reports error:
Error WINSOCK-10061  Socket is not connected - Connection refused [connect] [127.0.0.1:4711]
add                                             HELLO       HELLO   0       2015-07-07 13:34:52     TEST=
Could not signal event to localhost:4711. Event data are stored for later dequeueing.

Desired Behavior
The event data are always stored into the csv file if necessary (e.g. connection failed).