Support

Latest Notes

• Incomplete MATLAB syntax cause JMP to hang on macOS

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

  Dahlia_Watkins

  JMP Knowledge Base |

  Jan 19, 2023 1:06 PM

  977 views | 0 replies

• Data Privacy Requests

  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 

  Wendy_Murphrey

  JMP Knowledge Base |

  Jan 19, 2023 12:55 PM

  1625 views | 0 replies

• JMP® Clinical 7.1.2: the Profile y-axis label panel does not adjust according to legend size when the Chinese language is used

  In JMP Clinical 7.1.2, there is insufficient width for the y-axis label for Patient Profile and Medical History. The legend box appears to be very narrow, and some words are cut off and not displayed. This problem occurs when running JMP Clinical with the Chinese-language setting, or when running JMP Clinical with the English-language setting and using Chinese study data. This issue does not occur...

  laura_archer

  JMP Knowledge Base |

  Jan 18, 2023 11:52 AM

  247 views | 0 replies

• JMP® Clinical 7.1 subjects are dropped from the narrow search in the Standardized MedDRA Queries Incidence Screen report

  In JMP Clinical 7.1, the counts are not correct in the narrow search from the Standardized MedDRA Queries Incidence Screen report. When a subject has both a broad and narrow term within an SMQ, only the broad term is kept and the narrow term is dropped, leading to underreporting in the narrow search. The Hot Fix found here addresses this issue.   [Previously JMP Note 65907]

  laura_archer

  JMP Knowledge Base |

  Jan 18, 2023 11:42 AM

  304 views | 0 replies

• How to select rows based upon multiple conditions using a JMP® script

  Overview The following examples demonstrate how you can use the logical AND (&) and OR (|) operators with the Select Where message to select rows that meet multiple conditions. Instructions In a JMP® session, click the File menu and select New ► Script. Copy the below script and paste it into the script window. To run the sample script, click the Edit menu and select Run Script.   /* Open a sample...

  Wendy_Murphrey

  JMP Knowledge Base |

  Jan 12, 2023 5:46 AM

  2770 views | 0 replies

• How to add a Graphics Script using a variable within a For() loop

  Overview The following example demonstrates how you can use a variable in a Graphics Script whose value changes over iterations of a For() loop. To make this work as desired, you must replace the variable with its value during each iteration. You can accomplish this using Substitute() or Eval Expr(), as demonstrated in the below example. The Eval Expr() function evaluates and replaces any variable...

  Wendy_Murphrey

  JMP Knowledge Base |

  Jan 12, 2023 5:41 AM

  1273 views | 0 replies

• Analyzing Repeated Measures in JMP® Software

  Analyzing Repeated Measures Data in JMP^® Software     Often in an experiment, more than one measure is taken on the same subject or experimental unit. This means that a repeated measures analysis of the data may be necessary to make valid inferences and to draw meaningful conclusions. JMP offers multiple methods to analyze repeated measures: a multivariate repeated-measures approach, a univariate ...

  Duane_Hayes

  JMP Knowledge Base |

  Jan 11, 2023 4:41 AM

  18866 views | 3 replies

• Launching the JSL Debugger might result in time out and unknown errors

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

  Wendy_Murphrey

  JMP Knowledge Base |

  Jan 10, 2023 12:51 PM

  799 views | 0 replies

• The Control Chart Builder does not use limits from a limits table when there is only one phase

  The Control Chart Builder provides the ability to specify a Phase variable and to use control limits specified in an external data table. In the situation where only one phase is represented in the data, the limits specified in the external table are ignored. A workaround is to create the Control Chart Builder without using a Phase variable when only one phase exists in the data. The limits table ...

  Wendy_Murphrey

  JMP Knowledge Base |

  Jan 10, 2023 11:56 AM

  299 views | 0 replies

• The Rename Directory() function might fail to rename directories on network drives

  Using the Rename Directory() function to change the name of a file system directory might return 0 when you attempt to rename a directory that is found on a network drive. To work around the issue, use the Move Directory() function, which can work for both local and network drives.  Here is an example: rc1 = Move Directory( "$TEMP/Loss Function Templates", "$TEMP/subB" );     [Previously JMP Note ...

  Wendy_Murphrey

  JMP Knowledge Base |

  Jan 10, 2023 11:48 AM

  271 views | 0 replies

• Using a JMP® script to delete a non-existent table property now returns error: cannot find table property

  Attempting to delete a table property that does not exist in a data table returns the error "cannot find table property." Because this is an error condition, the JSL script stops executing.  Prior versions of JMP® ignored the condition and proceeded with the next JSL statement. As a workaround, the Try() function can be used to escape the error condition and optionally execute a catch expression (...

  Wendy_Murphrey

  JMP Knowledge Base |

  Jan 10, 2023 11:45 AM

  278 views | 0 replies

• Using lists in JSL to perform the same task on multiple objects

  Overview Sometimes it is necessary to perform the same task on several objects of the same type. One approach is to repeat the statement for each object. However, this requires you to retype the statement for each object or use a loop. A handy approach is to send the message to a list of objects. This method requires you to type the message only once. Two examples are given below.   Example 1 Supp...

  Ryan_Gilmore

  JMP Knowledge Base |

  Jan 10, 2023 11:40 AM

  794 views | 0 replies

• Scripts that create a modal New Window might result in an error: Deleted Object Reference

  DisplayBoxes in a New Window that uses the <<Modal option are no longer accessible after the window is closed.  When a New Window is closed, the DisplayBoxes that make up the contents of the window are destroyed.  Earlier versions of JMP on Windows operating systems incorrectly allowed scripts to access the DisplayBoxes due to a delay in the actual destruction of the objects.   There are several w...

  Wendy_Murphrey

  JMP Knowledge Base |

  Jan 10, 2023 10:41 AM

  534 views | 0 replies

• SAS® data set created by submitting SAS code from JMP® leads to an invalid SAS variable name

  When JMP^® connects to SAS^®, the SAS VALIDVARNAME system option is set to ANY because JMP is more permissive with respect to column names. This can cause an error similar to the one below if the SAS code submitted from inside JMP creates a variable with a name that does not follow the default SAS variable name rules. ERROR: The value <variable name> is not a valid SAS name. To ensure that the SAS...

  Wendy_Murphrey

  JMP Knowledge Base |

  Jan 10, 2023 10:37 AM

  1388 views | 0 replies

• Missing values in SAS® datasets might be imported incorrectly

  When connecting to local SAS^® using a 64-bit version of JMP^®, the 64-bit SAS 9.4 IOM OLE DB provider used to import SAS datasets will import missing data with incorrect values. This problem is limited to importing data from local SAS using a 64-bit version of JMP where the 64-bit SAS 9.4 TS1M0 version of the SAS IOM OLE DB provider is installed. The recommended workaround for this issue is to inst...

  Wendy_Murphrey

  JMP Knowledge Base |

  Jan 10, 2023 10:30 AM

  870 views | 0 replies

• JMP® File Import does not find any files on Microsoft OneDrive®

  When importing files in JMP®, including Multiple File Import, JMP might not be able to see the file(s) in Microsoft OneDrive®.  This is due to how OneDrive represents the file(s) on some computers. To resolve this issue, please save the file to the local computer, including the Desktop or Documents.   Once saved to the local computer, JMP is able to see the file during the import process. If you c...

  Wendy_Murphrey

  JMP Knowledge Base |

  Jan 10, 2023 10:09 AM

  305 views | 0 replies

• JMP® date columns are exported as character data types through ODBC

  When exporting a JMP^® data table to a database using ODBC, JMP exports the data as either character (CHAR or NCHAR) or numeric (FLOAT or DOUBLE PRECISION) data types. If a column is defined as a JMP date or time, it exports as character data. Changing the data type to a proper date format would need to be handled by the receiving database.   [Previously JMP Note 46350]

  Wendy_Murphrey

  JMP Knowledge Base |

  Jan 10, 2023 10:07 AM

  254 views | 0 replies

• JMP® Clinical 7.1 Risk Based Monitoring report is missing cell coloring, and the Risk Indicator Selector

  In JMP^® Clinical 7.1 when running the Risk Based Monitoring report, the output might be incomplete. In the report the cells might not be colored, and/or the Risk Indicator selection outline could be missing. This issue is resolved in the JMP® Clinical 7.1.1 Hot Fix available here.     [Previously JMP Note 65319]

  laura_archer

  JMP Knowledge Base |

  Jan 6, 2023 12:31 PM

  261 views | 0 replies

• JMP® Clinical 7.1 Findings Time Trends: error for Lab Test Results equal zero

  There is a coding error in JMP^® Clinical 7.1 that sets a lab results with value 0 to missing. This issue is resolved with the Hot Fix available here.   [Previously JMP Note 64954]

  laura_archer

  JMP Knowledge Base |

  Jan 6, 2023 12:18 PM

  464 views | 0 replies

• JMP® Clinical 7.1 Exposure Summary: Inconsistency in calculation of total duration of exposure

  In JMP^® Clinical 7.1, the durations from Exposure Summary are calculated inconsistently. This issue is resolved in the Hot Fix  available here.   [Previously JMP Note 64956]

  laura_archer

  JMP Knowledge Base |

  Jan 6, 2023 12:17 PM

  335 views | 0 replies

• JMP® Clinical 7.1 API JSL results in an error when try to remove section

  In JMP^® Clinical 7.1 when trying to remove section using the JSL API, the following error can occur: The symbol "TabFilterReferenceList" is not defined in namespace "results" in
  access or evaluation of 'results:TabFilterReferenceList' , results:TabFilterReferenceList/*###*/ This issue is resolved by the Hot Fix available here.   [Previously JMP Note 64957]

  laura_archer

  JMP Knowledge Base |

  Jan 6, 2023 12:15 PM

  351 views | 0 replies

• JMP® Clinical 7.1 AE Narrative "ByNarrativeCategoryDetails" template not not populated diagnosis heading if MHCAT value for cancer history is missing

  The Adverse Event Narrative template "ByNarrativeCategoryDetails" has a section in the heading for "Diagnosis" that is populated when MHCAT=CANCER HISTORY. The Medical History section is populated with values when MHCAT=GENERAL MEDICAL HISTORY. The Hot Fix available here makes the requirement generic for cases when the narrative is run with a study that does not have these particular MHCAT values....

  laura_archer

  JMP Knowledge Base |

  Jan 6, 2023 12:13 PM

  400 views | 0 replies

• JMP® Clinical 7.1 Adverse Events Incidence screen can report a zero of infinite relative risk

  This hot fix makes an adjustment to the JMP Clinical 7.1 Adverse Event Incident Screen report. Results in the table are changed to
  apply a continuity correction (Gart and Nam 1988) to avoid infinity or zero as a Relative Risk value. The Hot Fix for this issue is available here.   [Previously JMP Note 65365]

  laura_archer

  JMP Knowledge Base |

  Jan 6, 2023 12:11 PM

  382 views | 0 replies

• JMP® Clinical 7.1 Adverse Event Report can show percentages greater than 100

  JMP^® Clinical 7.1 Adverse Event Report counts subjects multiple times in the Body System heading counts and percentages causing the values to be incorrect, and the percentages may exceed 100 percent. This issue is resolved in the Hot Fix available here.   [Previously JMP Note 65366]

  laura_archer

  JMP Knowledge Base |

  Jan 6, 2023 12:09 PM

  363 views | 0 replies

• 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

  JMP Knowledge Base |

  Jan 6, 2023 12:07 PM

  297 views | 0 replies