Templates
The SAS Program block can be used to execute a SAS program or a JMP script. Optionally, the InQueueData and InServerData ports can be used to generate custom SAS reports based on the output of a Queue Stats Collector or Server Stats Collector block, respectively.
- InQueueData
-
Input data port for the pathname of a folder that contains the output data set of a Queue Stats Collector block. This port is typically connected to the ResultLocation output data port of a Queue Stats Collector block. A SAS program can use the Queue library reference name (libref) to access the Queue Stats Collector data set location. This port is ignored for JMP scripts.
- InServerData
-
Input data port for the pathname of a folder that contains the output data set of a Server Stats Collector block. This port is typically connected to the OutResultLocation output data port of a Server Stats Collector block. A SAS program can use the Server library reference name (libref) to access the Server Stats Collector data set location. This port is ignored for JMP scripts.
- InSubmitCode
-
Input Boolean data port that starts the execution of the SAS program or JMP script if the value true is passed in. For example, a Value Generator block that produces Boolean data can have its OutValue port connected to a SAS Program block’s InSubmitCode port.
- SAS Code Path
-
Specifies the pathname of the SAS program or JMP script to be executed.
- Auto Submit
-
If selected, causes the SAS program or JMP script to automatically execute at the end of each design point replication run. If the Submit to Remote SAS Workspace Server option is selected, then the SAS program or JMP script will execute on the remote SAS workspace server host specified in the Simulation Studio Configuration dialog box.