Sending <<Make SAS Data Step to a data table returns the text for a SAS DATA Step that can re-create the data table in SAS. For example,
Sending <<Make SAS Data Step Window produces this code in a window with a .SAS suffix, so that it can be easily sent to SAS.
Sending <<Get SAS Data Step for Formula Columns to a data table includes column formulas in the SAS data step code. Here is an example that outputs the formula for the Ratio column:
You can also include column formulas in scoring code for SAS Model Manager. Send <<Get MM SAS Data Step for Formula Columns to the data table.
As with <<Get SAS Data Step for Formula Columns, specifying column names is optional.
SAS Open For Var Names( ) opens a SAS data set only to obtain the names of its variables, returning those names as a list of strings.
The rules for SAS variable names are more strict than those of JMP. The SAS Name function converts JMP variable names to SAS variable names, changing special characters and blanks to underscores, and various other transformations to produce a valid SAS name.
To show the systime value:
First, use the Metaconnect command to connect to a SAS metadata server:
connected = Meta Connect("MyMetadataServer", port)
If you supply only the machine name (for example, myserver.mycompany.com) and the port, you are prompted to provide the authentication domain, your user name, and your password. You can also specify all that in JSL:
connected = Meta Connect("MyMetadataServer", port, “authdomain”, “user name”, “password”)
When you are finished using the SAS metadata server, use Meta Disconnect( ) to disconnect the connection. No arguments are necessary; the command closes the current metadata server connection.
Now you can send Disconnect and Connect messages to the conn object to close and open the SAS connection.
This is an example of using an object and messages with SAS server connections. You might have also connected to SAS servers using global functions. If so, the Disconnect and Connect messages do not affect those global connections. However, if there is no active global connection, that global connection is set to the connection opened by the object.
When you connect to a SAS server, use Connect Libraries to automatically connect metadata-defined libraries.
To connect specific libraries later, use the SAS Connect Libref function or Connect Libref message to a SAS server object.
After you connect to a SAS server, use the SAS Get Lib Ref command to view the libraries on that server:
SAS Get Log( ) returns the contents, which can be placed in a JSL variable and used like any JSL string.
The JMP Sample/Scripts/SAS Integration folder contains sample scripts. To run the stored process scripts successfully, the stored processes need to be placed on your SAS Metadata Server. The stored processes can be found in the sampleStoredProcesses.spk file, also in this folder.
3.
Expand the BI Manager node in the left pane of the SAS Management Console.
6.
Enter the full path to sampleStoredProcesses.spk or use the Browse button to navigate to it.
7.
Select All Objects in the Import Options section of the wizard.
8.
Click Next.
9.
Click Next.
11.
Click Next.
13.
Click Next.
After the import completes, you will find a folder named BIP Tree under the folder that you imported the stored processes into. Under BIP Tree is a folder named JMP Samples, and in the JMP Samples folder are two sample stored processes: Shoe Chart and Diameter.
Please note that the paths to the sample stored processes needs to be adjusted in the sample scripts storedProcessHTML.jsl and storedProcessJSL.jsl to match the folder into which you imported the sample stored processes. Otherwise, these scripts will not work correctly.