cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Don’t miss your chance to experience Discovery Summit Europe at our best available rate! Early bird registration through 31 Oct.
  • Graph Builder Toolbar streamlines interactive graphing. Creates shortcuts on Report and GraphBuilder Helpers toolbars. Download and install the extension.
  • JMP will suspend normal business operations for our Rest and Recharge Day on Friday, October 2, 2026.
    Regular business hours will resume on Monday, October 5, 2026.

JMP Knowledge Base

Choose Language Hide Translation Bar

Featured Items

  • JMP® System Requirements

    To view the system requirements for JMP®, JMP Pro, JMP Live, and JMP Clinical, click the following links:   JMP system requirements for Windows operating systems JMP system requirements fo...

    Bobby_Riggs
    JMP Knowledge Base |
    Mar 4, 2025 9:16 AM
    3250 views | 0 replies
  • JMP® New Features and Release Notes

    New in JMP/New Features documentation is published with the initial (.0) release of a new version of JMP and describes new or significantly enhanced capabilities introduced in that release. Re...

    Bobby_Riggs
    JMP Knowledge Base |
    Nov 30, 2022 11:28 AM
    32602 views | 2 replies

Latest Posts

  • JMP® Clinical 7.1 Adverse Event Report can incorrectly label columns with the wrong treatment group

    The output of the Adverse Event Report in JMP® Clinical 7.1 may be incorrect. The column headers indicating the treatment group may be incorrect, so that the counts and percentages are being attributed to an incorrect treatment group.   This issue is resolved in the JMP Clinical 7.1.1 Hot Fix. To resolve the problem apply the Hot Fix available here. 
        [Previously JMP Note 65320]

    laura_archer laura_archer
    Jan 6, 2023 12:07 PM
    305 views | 0 replies
  • JMP® Clinical 7.1 Adverse Event Narrative templates do not split prior and con meds based on study day

    In JMP Clinical 7.1 there is not a standard way of splitting medications into prior treatment vs. on treatment. This hot fix standardizes this based on study day. The split is now based on study day and is calculated in loaddata to split prior and conmeds. The standardization uses the study day when available, and then either the first of the month if day is missing or the first of the year if mon...

    laura_archer laura_archer
    Jan 6, 2023 12:06 PM
    491 views | 0 replies
  • JMP® Clinical 7.0: Mortality Time To Event Deaths that occur on study day one

    JMP® Clinical 7.0 and 7.1 removed deaths on study day 1 for Mortality Time to Event reports. JMP Clinical removes disposition records that occur on or before study day 1 to remove randomization and informed consent records. This means that a death on study day 1 will be removed. This issue is resolved in the Hot Fix available here.   [Previously JMP Note 64869]

    laura_archer laura_archer
    Jan 6, 2023 12:03 PM
    644 views | 0 replies
  • JMP® Clinical 6.1 might exhibit slow performance when loading sample data

    This Hot Fix improves system efficiency to address performance issue in JMP® Clinical 6.1 when loading a study. To resolve the problem, apply the Hot Fix available here.   [Previously JMP Note 60234]

    laura_archer laura_archer
    Jan 6, 2023 12:01 PM
    602 views | 0 replies
  • JMP® Clinical 6.1 hotfix to resolve issues with AE Narrative

    The Hot Fix available here resolves several issue with AE Narratives in JMP® Clinical 6.1. 1.  Enhancements so that AE Narrative can accommodate non-unique Findings test codes 2.  Resolved a bug that AE Narratives show incorrect information for USUBJID, medical history and findings 3.  There was a logic error that was preventing original units from working correctly This has been fixed 4.   Invest...

    laura_archer laura_archer
    Jan 6, 2023 11:59 AM
    316 views | 0 replies
  • JMP® Clinical 6.1 Hotfix for Findings Reports

    The Hot Fix available here addresses a variety of issues with Findings Reports in JMP® Clinical 6.1   The first resolved issue is that Action Buttons are not enabled in Findings Distribution. This error occurs when running the following steps. 1) Run a Findings Distribution on data for LB domain
    2) Go to the Missing Test Details section of report
    3) Select subject counts in the summary table
    4) Notic...

    laura_archer laura_archer
    Jan 6, 2023 11:57 AM
    345 views | 0 replies
  • JMP® Clinical 6.1 hotfix for Add Study issues

    The Hot Fix available here for JMP® Clinical 6.1 resolves four issues for Add Study.    1.  This Hot Fix allows JMP Clinical 6.1 to be compatible with SAS® 9.4 TS1M5, and allows studies to be added to JMP Clinical when SAS 9.4 TS1M5 is installed. This Hot Fix also resolves the following errors: 2.  The following error may also occur in JMP Clinical 6.1 when adding a study:  ERROR: The following do...

    laura_archer laura_archer
    Jan 6, 2023 11:55 AM
    310 views | 0 replies
  • JMP® Clinical 6.1 Gives an Error Message when the Add Study Button is Clicked

    JMP® Clinical 6.1 gives the following error when the Add Study button is clicked: The namespace addStudyDiag:addStudyOptions is not defined in access or evaluation of 'Expr:setParent', Expr:setParent/*###*/(addStudyDiag << getName)/*###*/ This error affects computers where the Regional Operating System (OS) and Language settings are set to a Language there the decimal separator is represented with...

    laura_archer laura_archer
    Jan 6, 2023 11:52 AM
    435 views | 0 replies
  • JMP® Clinical 6.1 does not use supplemental domains by default

    JMP® Clinical 6.1 does not use supplemental domains, by default. To resolve the problem, apply the Hot Fix available here. For domain distribution reports at subject level the option to Merge Supplemental data is now on by default. This affects Distribution reports for the following domains:  AE, Events, Interventions, Findings and Study Visits.    [Previously JMP Note 60239]

    laura_archer laura_archer
    Jan 6, 2023 11:50 AM
    330 views | 0 replies
  • JMP® Clinical 6.1 Adverse Event Narratives do not handle Supplemental Data

    This Hot Fix allows supplemental data to be used in Adverse Events Narratives in JMP® Clinical 6.1.  One option is to specify the full path and name to the input SAS data set containing supplemental data for AE narratives. This data set merges events using USUBJID and AESEQ. If AESEQ is not available in the original SDTM or ADAM data, AESEQ is defined after sorting events by USUBJID, AESTDTC, and...

    laura_archer laura_archer
    Jan 6, 2023 11:38 AM
    339 views | 0 replies
  • JMP® Clinical 5.0 Cluster Subjects Across Study Sites might give empty results window

    There is an issue in JMP® Clinical 5.0 where the results from Cluster Subjects Across Study Sites are blank. This occurs when run after Cluster Subjects Within Study Sites. This Hot Fix addresses the issue for viewing output from reports when analyzed within the same Clinical Review: Cluster Subjects Across Study SitesCluster Subjects Within Study Sites This has been fixed so that both reports can...

    laura_archer laura_archer
    Jan 6, 2023 11:28 AM
    314 views | 0 replies
  • JMP® Clinical 7.0 may result in an error in Exposure Summary

    When running Exposure Summary in JMP® Clinical 7.0 with SAS 0.4 TS1M6 an error will be generated. The error is    ERROR: Improper use of macro reserved word to.   Results are still generated. To resolve the problem apply the Hot Fix available here.   [Previously JMP Note 63535]

    laura_archer laura_archer
    Jan 6, 2023 5:51 AM
    469 views | 0 replies
  • JMP Clinical 6.1 errors when Animal Profiles are run with PDF and RTF unchecked

    In JMP Clinical 6.1 if the Animal Profile report is run with both PDF and RTF unchecked, the report tries to run but an error will occur. The Hot Fix available here resolves this error.       [Previously JMP Note 61822]

    laura_archer laura_archer
    Jan 6, 2023 5:37 AM
    354 views | 0 replies
  • Incidence Screens are not honoring the value ordering for the Treatment Control Level in JMP® Clinical 8.0

    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]

    laura_archer laura_archer
    Jan 6, 2023 5:30 AM
    565 views | 0 replies
  • Incidence Screen label names are truncated on graphs and in data tables

    In JMP® Clinical 7.1 in Incidence Screen output, when there are long values within a column that are used as label names on graphs or in data tables, the label names are truncated on graphs and in data tables. This issue is corrected in the JMP® Clinical 7.1.2 Hot Fix. Click here to access the hot fix for this issue.   [Previously JMP Note 65970]

    laura_archer laura_archer
    Jan 6, 2023 5:28 AM
    378 views | 0 replies
  • Hotfix for JMP® Clinical Patient profiles

    The Hot Fix found here addresses three issues in JMP® Clinical Patient Profiles.   1.  Patient Profile saved in a review cannot be open when in Reviewer Mode only.  The following error may be observed when attempting to open a saved review containing a Patient Profile JMP ERROR:
    Name Unresolved: severityNLev in access or evaluation of 'severityNLev' ,
    severityNLev/*###*/ This error is resolved, and ...

    laura_archer laura_archer
    Jan 6, 2023 5:26 AM
    473 views | 0 replies
  • General enhancements found in the JMP® Clinical 8.0 hot fix

    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]

    laura_archer laura_archer
    Jan 6, 2023 5:23 AM
    546 views | 0 replies
  • Findings Time Trends in JMP® Clinical 8.0 might result in the error "There are no tests with measurements for at least two time points..."

    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]

    laura_archer laura_archer
    Jan 6, 2023 5:21 AM
    469 views | 0 replies
  • A JMP® Genomics 10.1 hot fix provides enhancements and new features

    The JMP Genomics 10.1 hot fix is for users of JMP® Genomics 10.0. Click here to access the hot fix. Important: After installing the hot fix, you must regenerate the dialogs for the updates to appear in JMP Genomics. Select Genomics ► General Utilities ► Generate Genomics Dialogs. For descriptions of the updates, see the release notes for JMP Genomics 10.1.   [Previously JMP Note 67654]

    AdamMorris AdamMorris
    Jan 4, 2023 7:41 AM
    793 views | 0 replies
  • When fitting a model with random effects, are the effects tested correctly?

    When fitting a model with random effects using the expected mean squares method, JMP® tests the effects correctly. The "Test Denominator Synthesis" output may be different than what you think it should be. However, JMP follows the references of Hocking and Hartley and Searle (listed below) to determine the appropriate error terms in models with random effects. This issue is an item of controversy ...

    sseligman sseligman
    Jan 3, 2023 8:17 AM
    549 views | 0 replies
  • What is the Specified Sigma option in capability analysis, and how is the default value calculated?

    Specified sigma allows the user to enter a specific, known sigma used for computing capability analyses. Sigma is user–specified and is not computed. When accessing the capability dialog from the Distribution platform, the default value for Specified Sigma on the dialog is the same as the overall standard deviation. When accessing the capability dialog from the Control Chart platform, the default ...

    sseligman sseligman
    Jan 3, 2023 8:07 AM
    859 views | 0 replies
  • What is the largest number JMP® can display?

    JMP® can display numbers between 10−308 and 10308, with full 15–17 decimal digits precision.    [Previously JMP Note 61003]

    laura_archer laura_archer
    Jan 3, 2023 8:00 AM
    243 views | 0 replies
  • The SHASHInv function produces incorrect results in JMP® 14

    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 ...

    laura_archer laura_archer
    Jan 3, 2023 7:59 AM
    340 views | 0 replies
  • JMP® might crash if you open a table that uses the List Check property for columns and the table was also created in JMP® 15

    A table created in JMP 15 that uses the List Check property can crash JMP when the JMP version is earlier than JMP 15. In some cases, the table can be opened, but data are not displayed as expected. A change was made in JMP 15 to better handle the List Check property. The property can now handle more than 256 values. After this change was made, some new limitations were introduced. If the List Che...

    laura_archer laura_archer
    Jan 3, 2023 7:57 AM
    235 views | 0 replies
  • If I change my columns from ordinal to nominal or vice versa, my parameter estimates do not match. Why?

    This is due to the different parameterizations JMP® uses for the two column types. See the discussion of Nominal Factors and Ordinal Factors in the JMP Online Help for more information on the exact parameterizations. The parameter estimates differ, but the predicted values from the two models are consistent.   [Previously JMP Note 36638]

    sseligman sseligman
    Jan 3, 2023 7:56 AM
    593 views | 0 replies