How to identify true "root" FileGlobals using NI Batch process model?

[Bob Rafuse]

Using the NI Batch process model, how do I access the FileGlobals of the
root process model (the one that runs before the Test Sockets are created
and initialized) from a client test sequence file? I've tried accessing
them via "RunState.Root.FileGlobals..." from the client test sequence file,
but the FileGlobal values I set in the Process Model can't seem to be seen
in the clients.

For example, in the ProcessSetup callback in the Batch process model
sequence file, I set FileGlobals.SomeFlag = 2. However, when I try to
examine "RunState.Root.FileGlobals.SomeFlag" from the Context tab in the
client's execution window, the value is always 0. I'm starting from the
stock NI Batch model, so I know I'm not acc
identally setting SomeFlag to 0
after the ProcessSetup call but before the Test Socket's MainSequence call.

I'm fairly new to using the Batch process model, but I thought "Root" was
supposed to point to "the first sequence context of the execution". Isn't
this the root process model? Does "RunState.Root" point to some 'other'
Root context?

---
Bob

[Bob Rafuse]

> Using the NI Batch process model, how do I access the FileGlobals of the
> root process model (the one that runs before the Test Sockets are created
> and initialized) from a client test sequence file? I've tried accessing
> them via "RunState.Root.FileGlobals..." from the client test sequence
file,
> but the FileGlobal values I set in the Process Model can't seem to be seen
> in the clients.

I "solved" my problem... apparently something was toasted in my TestStand
setup.

I had "All Executions Share the Same File Globals" selected on the process
model sequence file properties page, but clients could still not seem to see
File Global values set by the process model or other clients, regardless of
the "Sequence File Globals:" setting.

After experiencing some other
weirdness (occasional exceptions and strings
appearing corrupt in the Context windows), I tried uninstalling TestStand
3.0, rebooting and reinstalling. All the weirdness went away and clients
can now share the same FileGlobals fine. Not sure what happened but
everything works as expected.
---
Bob