JMP® New Features and Release Notes
JMP® 18:New in JMP 18 Release Notes for JMP/JMP Pro 18.x JMP® 17:New Features for JMP 17 Release Notes for JMP/JMP Pro 17.1 Release Notes for JMP/JMP Pro...
JMP® 18:New in JMP 18 Release Notes for JMP/JMP Pro 18.x JMP® 17:New Features for JMP 17 Release Notes for JMP/JMP Pro 17.1 Release Notes for JMP/JMP Pro...
Background
Currently on macOS, submitting any incomplete MATLAB syntax can cause JMP to hang. The hang experienced by JMP is the result of MATLAB getting stuck in a waiting state.
For example, a user submits the following MATLAB syntax via MATLAB Submit(). Note the *]* is missing in the malformed MATLAB expression.
MATLAB Init();
Matlab Submit("
a = [5;5;5
");
As a result, MATLAB get...
As a wholly-owned subsidiary of SAS, JMP takes the security and privacy of your personal data seriously. If you wish to exercise a privacy right you have under the law, including GDPR, or if you have a concern about any personal data JMP and/or SAS may hold about you, use the link to our privacy form below to submit a request. SAS Data Privacy Request Form
JMP® licenses are now stored at my.jmp.com. The site representative for each account is able to view and download license files for each version and operating system. JMP licenses are version and operating system-specific. To obtain an updated JMP license file: Log in to my.jmp.com with the site representative's My JMP IDClick the "Manage Software" section.Use the table to determine the Version ...
R 4.1.2 introduces R binary for Apple silicon arm (M1) chips. When JMP connects to the Application Response Management (ARM) build of R 4.1.2, JMP is unresponsive on the M1 Mac systems that are running Big Sur or Monterey. Note: This behavior is experienced running JMP natively or with Rosetta. It is recommended that you remove the R 4.2.1 ARM build and install R 4.1.2 for Intel, provided at https...
When the JSL Debugger is launched, a second instance of JMP® is created. The two JMP instances communicate with one another using sockets. Due to various VPN and firewall settings, launching of the JSL Debugger may be blocked. In these instances, you might see the following error messages:
Time out encountered attempting to connect to the JSL Debugger GUI.
Unknown error encountered during the initi...
Background
Beginning October 3, 2022, Google changed how Google Sheets are accessed. This change disrupted JMP’s ability to access Google Sheets using the Google Sheets Internet Open option.
Accessing JMP will result in the following error message:
We expect this functionality to be restored in a future version of JMP.
Google Sheets Internet Open in JMP is normally performed by selecting File > I...
JMP® Presentation Virtualization (PV) or JMP® for the Cloud licenses cover the legacy PV agreements and the new JMP for the Cloud packaging. The level of support and what is supported remain the same. A JMP Presentation Virtualization license grants organizations the right to install JMP on a Windows Server operating system and allow licensed users to connect to the server using Remote Desktop P...
When your license is renewed for JMP®, the designated JMP site representative receives an email from Licensing Support with the new license data in the form of a text file attachment. If your JMP license is expired, you are prompted for a new license upon launch. To renew your JMP license: Save the TXT license file to your local hard driveRight-click the JMP icon and select "Run as Administrato...
R 4.2.x versions are currently not working with various JSL R functions that pull data from R. To address this issue, SAS recommends that you downgrade to an R 4.1.x version to use the R integration with JMP. Note: Reference JMP Note 575310 when considering using the integration on Apple (macOS) silicon arm (M1) architecture. [Previously JMP Note 69504]
The JMP Clinical 8.0 hot fix available here contains a few general enhancements. A detailed description of these enhancements can be found in these release notes. [Previously JMP Note 67941]
When you try to open a review template that was created in a previous version of JMP Clinical, the template does not open, and the following error appears:
error: argument should be character in access or
evaluation of 'Lowercase' , Bad Argument( SAS Name( filterNm ) ),
Lowercase/*###*/(SAS Name( filterNm ))
Click here to access the Hot Fix for this issue.
[Previously JMP Note 67933]
In JMP Clinical 8.0, when you save a review template with a subject filter, the action results in an error that is similar to the following:
could not find column{1} in access or evaluation of 'Column' ,
Column/*###*/("USUBJID")
In addition, the template fails to save.
Click here to access the Hot Fix for this issue.
[Previously JMP Note 67928]
In JMP Clinical 8.0, the Medical Query Risk Report does not honor colors that are set in value colors. Click here to access the hot fix for this issue. [Previously JMP Note 67923]
In JMP Clinical 8.0, Incidence Screens are not honoring the value ordering for the Treatment Control Level. Click here to access the hot fix for this issue. [Previously JMP Note 67913]
In JMP Clinical 8.0, an Adverse Events Distribution might result in the following error when calculating relative risk: ERROR: More positional parameters found than defined. This error can occur when values in the data contain commas. Click here to access the hot fix for this issue. [Previously JMP Note 67905]
In JMP Clinical 8.0, an error is generated and the Create Live Report process fails when a subject has no profile data to display. Click here to access the Hot Fix for this issue. After you apply the Hot Fix, the JMP® Live report publishes, without error, and you see a note indicating that there is no profile data to display. [Previously JMP Note 67883]
In JMP Clinical 8.0, the DSUR/PSUR report might result in an error that is similar to the following:
Name arg must be quoted string
Line XX Column YY: ... Grouping Columns( :Name(?Planned Treatment for Per...
This problem occurs when the Term Level and Group Level selections are set to the same term.
Click here to access the Hot Fix for this issue.
[Previously JMP Note 67910]
Findings Time Trends in JMP Clinical 8.0 might result in this error message: ERROR: There are no tests with measurements for at least two time points. Time Trends cannot be plotted. The error appears even when there are time points available in the Analysis Data Model (ADaM) data sets. Click here to access the Hot Fix for this issue. [Previously JMP Note 67870]
In JMP Clinical 8.0, the column names in a standard safety report after the first column are not aligned with the data. Click here to access the hot fix for this issue. [Previously JMP Note 67864]
In JMP Clinical 8.0, the Hy's Law option Only include on-trial measurements is disabled. This option should be enabled when you select Normalize laboratory values: by Upper Limit of Normal. Click here to access the Hot Fix for this issue. [Previously JMP Note 67863]
An Adverse Event Narrative that is created in JMP Clinical 8.0 might not display some dates correctly when you are using Analysis Data Model (ADaM) data sets with ASTDTM and AENDTM. Although there are dates in the data sets, the Adverse Event Narrative does not have the appropriate sentences that reflect the treatment dates. These statements are missing from the output. Click here to access the ...
JMP Clinical 8.0 contains two translation errors for the Chinese language. In the Show Patients at Risk drill-down information, the output contains an untranslated string. In the DefaultBySubjectChinese or DefaultByEventChinese template that is used for the Adverse Event Narrative, the output contains an incorrect translation for information about sex. Click here to access the Hot Fix for this ...
JMP Clinical 8.0 has an issue that affects many reports that use non-English data. An error message about this issue can look similar to the following: ERROR: No subjects satisfy the Filter to Include Subjects or are in all populations selected on the Population tab. This problem is the result of a translation error in JMP Clinical 8.0. Click here to access the Hot Fix for this issue. [Previous...
In JMP 14 the SHASHInv function is supposed to be defined by the following mathematical equation: SinH( (ArcSinH( x ) - gamma) / delta ) * sigma + theta; However, there is a bug in JMP 14 where the SHASHInv function does not match the results of the mathematical formula. In JMP 14 the function SHASHInv should not be used, but instead the actual formula should be used. The formula can be found by ...
In Chinese, there are four meanings of "Overall Response," with different translations in Chinese. These terms, loosely translated into English, are "Assessment," "Efficacy," "Remission," and "Response." The files in this note enable the different translations in Chinese. To update the files in JMP® Clinical, first close JMP Clinical completely. Then back up the existing files. Finally, replace th...