rtc 4 scm --dir option no longer setting sandbox?

Hello.

previous to rtc 4  we used scm load --dir <path_to_sandbox> --remote-rules dir/x.loadrules -t <path to fetch files>

The .jazz5 & .metadata files would be created in <path_to_sandbox>, which was not the current directory.
The files would be fetched in -t <path to fetch files>

I am trying to use rtc 4 scm and new Xml format loadrules.   And on Windows Server 2007, used the 64-bit package.
 
the -t <path to fetch files> gives an error when used with --remote-rules, as it has now been replaced by <sandboxRelativePath pathPrefix="some_dir"/> in the XML loadrules file, I generated the rtc4 loadrtules files using the client, added that entry, and removed the -t option, that seems to work okay.

But the --dir option no longer seems to set the sandbox root, the .jazz5 & .metadata files are getting created in the current directory, as opposed to the one specified by --dir.  Is this intentional?  if not, how to get the sandbox root specified on scm commandline?

The help for scm commandline in rtc 4 still says the following:

-d [--dir] arg

The root directory to save files to.

am in curdir:
> D:/x/y/z
>scm -u y -a n --non-interactive
   --config "c://rtc_login" load -r https://<repos>:9502/ccm/ <workspace>
    --dir D:/x/y/z/src--force --remote-rules loadrules/build.loadrule  <component>