Process setup

Question

Hi users,
I'm designing a test system using the batch process model. My design utilises several COM servers that must be created before the testing process begins. The obvious place to create these servers (using the ActiveX adapter), is in the Process Setup callback.
Some of my servers reside in the process model's sequence file (their handles are in the process model sequence file globals). They are always kept private to this sequence, and are consistantly used with this process model.
The rest of my servers reside inside the client's sequence file (their handles are in the client sequence file globals), as these servers change with different products begin tested.
I wish to keep the handles from both groups of servers private from each other (i.e. I don't want someone using my process model to be able to reference the process model's servers directly from the client sequence file.
Now to my problem.....
If I override the process setup callback to allow the client's sequence file to use this step, the process model's process setup callback is obviously disabled. 
Is there a clean way I can enable both process setups at once (i.e. the process model has a process setup AND the client sequence also has a process setup)?
I've currently placed a dummy subroute call in my process model just before the process setup callback is called (this happens in the Test_UUTs setup tab). I've added my process model setup steps into this dummy subroute. However this is not very intuitive. I would prefer that both process setup calls were actioned one after the other.
Any ideas?  

Answer 1

Hey bilby42,
There isn't a way to have both the code
inside your Process Setup callback within the Process Model and the code inside
your Process Setup callback from your client sequence both run.  The
behavior is to override the callback which means it completely replaces that
sequence.  What I would recommend to do is create new sequence within the
Process Model called ProcessModelProcessSetup or something similar.  This
new sequence would contain the code that you always want to run in the Process
Model.  You could then move the Process Setup callback to the end of this
sequence so all of your setup would be contained in a single sequence. 
You could also leave it as two separate sequence call steps.  Either of
these solutions would be just as good.
From your description, it sounds like you may have already
implemented something like this.  Unfortunately this is really the only
way to implement what I think you want to do.  If the code that is already
in the process model should always be there, then it probably makes sense to
put it in a regular sequence call anyway rather than a callback.  This
will make sure that someone doesn't modify it unless they go into the process
model and delete the steps or change them.  Hope this helps!
Pat P.
Software Engineer
National Instruments