Entities enter a Switch block from a single input port, but may flow out from different output ports, and the output path will be determined using the switch cases.  If no switch case matches, the entity flows out the OutDefault port.  The Switch block is used to route entities to different paths in the model. On the otherhand, the Selector block chooses which entites may pass through it based on a condition (it chooses which entity input port to pull the next entity from).  But all entities entering a Selector block leave from the same output port.   Said a different way, the cases in the Selector block define entity input ports, while the cases in a Switch block define entity output ports.   Hopefully this helps a bit more! ... View more

When an entity enters a Switch block, a switch value will be determined (either through the InSwitchValue port or by an attribute value on the entity).  Based on that switch value, an output port will be selected from the cases defined in the Switch block.  If the switch value does not match any of the case values, then the entity will flow out of the OutDefault port of the Switch block.  In summary, the Switch block is used to route entities down different paths, based on a switch value (where the switch value can be computed dynamically by using the InSwitchValue port on the Switch block or by using an entity attribute value).  For example, you can use a Switch block to route an entity to the shortest of a series of queues (see docQueueRouting in the projects\examples folder where Simulation Studio is installed).  The Switch block is widely used in Simulation Studio models.   The Selector block pulls entities from upstream from one of its defined input entity ports based on a case value that is pulled from the InCaseValue port.   When the Selector block receives a message from downstream to output an entity, it checks its InCaseValue port to determine which input entity port to pull an entity from.  Also, when an entity arriving to the Selector block attempts to enter the block, the current case value is checked to see if the incoming entity's input port matches the value.  If it doesn't, it will not flow through the Selector.  One example where the Selector block is useful is when you have multiple queues feeding into another queue with fixed capacity.  You can use the Selector block to determine which queue should have priority when a space opens up in the fixed capacity queue.  See the attached figure.       ... View more

Ok, I checked with tech support about the windows registry warning message.  Here is additional info from them.  If you continue to have problems, I suggest contacting tech support directly: 919-677-8008 800-727-0025 http://support.sas.com/en/technical-support.html#contact-technical-support   Based on the warning message showing in the log, the system is having problems opening the windows registry key below on the machine: HKEY_LOCAL_MACHINE\Software\JavaSoft\Prefs You may need to verify that this registry key does exist on the machine, or if it does not exist , you may need to try manually creating the key and then attempt the batch mode submission again. You will likely need the assistance of an IT staff person who has administrative level permissions to check the windows registry settings on the machine, and to create the key if necessary.   Depending upon whether you are on 32-bit or 64-bit windows, the keys will be as follows:   32 bit Windows HKEY_LOCAL_MACHINE\Software\JavaSoft\Prefs   64 bit Windows HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\JavaSoft\Prefs   Be sure you are doing your batch mode submission using “run as administrator” , if you are running from a batch script file. ... View more

One other thing to try...run as administrator once.  That should create an entry in the registry that seems to be missing right now. ... View more

I looked at your model, and as far as I can tell, everything looks fine (I did have to modify your project file to open it though because it was trying to open model2_0, which was not there.  I opened model2_1).  I ran your model for 50 replications in parallel with no problems.     I went back and looked at the attached image of the java error.  I am thinking now that this is not related to your resource scheduler.  The first event processed in your model when it starts is the resource scheduler, which is why we see messages relating to it.  But I also see a warning before that about the windows registry.  Something seems to be preventing the model run from starting normally.  Could you possibly have some sort of permissions issue?  Are you sure your input data sets are being generated and accessed correctly in the Sim Studio model?  In the version of the model that you are running, are there other input data sets, other than the one that sets the batch size for the entity generator?     I will look into the windows registry warning further.   One last thing to try...try adding the -nonparallel option to your batch run command.   ... View more

I agree with the previous response.  There is an error in the simulation model that is causing the batch run to hang.  I also suggest running the model interactively to try to pin point where the error in the model is occuring.  From the attached error message, it looks like it has something to do with the resource scheduler entity and possibly how its attributes are set. ... View more

I highly recommend installing v14.1 if possible.  Many changes to Simulation Studio have been made since v12.1, including major changes to the way the local SAS server is launched.  Sorry, I know that is not necessarily an ideal response, but the server updates in v14.1 were specifically designed to eliminate these types of problems with the SAS IOM server connection.   That being said, this sounds like a permissions issue.  When you run the .bat file to launch the server, it writes a log file.  If you do not have write permissions to the folder where the .bat file is located, then there will be problems.  You could try moving the entire launchSASServer directory to some location where you have write permissions and then launch the .bat file from there.  If that still doesn't work, then you might have to contact SAS technical support.   Hope that helps! ... View more

Currently you cannot update specific fields in a data model (such as the one you are reading in to represent the bus inventories).  You can only update the entire table.  If you somehow can write a SAS data set with the new bus inventories, then you can use the InUpdateNow port on the Observation Source block to read the new data set, as specified by the InDataPolicy port (see the overview file of the Observation Source block for the format of the string required by the InDataPolicy port).  Essentially, you would have some sort of controlling entity that cycles around each time period, creates the new file path string for the Observation Source (that points to the new bus inventory data set) and then signals the Observation Source to update.   If you cannot read the new bus inventories from a data set, maybe you could try creating a resource entity for each model year and then have an attribute for the current inventory.  You can still read the data from an Observation Source block to create the entities, but you might have to rotate your inventory data set (have each row in the data set represent a different model year).  You would then connect a Modifier block to the Observation Source to pull the Inventory value and set it as an attribute on the entity.  Each time period, you can then seize each model year entity (using a simple Attribute Rule in a Seize block), immediately release the model year entity and send it to a Modifier block where you update the current inventory attribute. ... View more

What version of Simulation Studio are you using? Assuming it is not v14.1, then you might need to modify the files SAS_Sim_Server.bat and Sim_Obj_Spawn.cfg in your launchSASServer folder to point to the location of sas.exe on the machine you are using. It is possible that you have SAS installed in a non-standard location.   Be sure to save backups of the original files before modifying.   By default, a results folder will be created under the current project folder and any output data sets will be saved there.You can change the location of the results folder by right-clicking on your project name in the Simulation Studio Projects tree (upper left of the Sim Studio window) and selecting the option Results. ... View more

If you are using a version of Simulation Studio that is prior to v14.1., make sure the SAS Server is launched.  You can launch the SAS IOM server by double clicking the file SAS_Sim_Server.bat in the folder launchSASServer where Simulation Studio is installed (usually C:\Program Files\SASHome\SASSimulationStudio\13.2\launchSASServer) Once you run SAS_Sim_Server.bat, you can minimize the window that it opens, but don't close it.   You will need to do this step every time you run a Simulation Studio model that reads or writes data. Simulation Studio v14.1 no longer requires this step, however.  ... View more