Unfortunately, an empty value for $Proc2Execute is not so strange ...

This variable is set to "" by the script Itself, which then will look in File _Connect-Parms.Kix to see if user/operator has indicated a reference to a personnal script to execute.

If it's the case, the script tries to execute this external script by a 'Call "$Proc2Execute" ' command.

If not, this empty value compells the procedure to execute the internal procedure "JobToDo" ...

Actually you'll see this loop has been correctly executed once (connection to the first resource) but hangs when apparently connected to the second resource (both resource values are set in file _Connect-ResourceNames.Kix).

That's sadly why I suspect more a problem with credentials in NT (already discussed earlier on the Board, but I don't really understand what's all about [Frown] ), than a syntax or logic problem in the script.
But it's perhaps pretentious to think my code is bug free [Big Grin]
Fresh Eyes will perhaps find something ... When you have time 'f course.