JMP Knowledge Base

Latest Posts

• Can I perform a multinomial logit analysis in JMP®?

  If you are using the term multinomial logit analysis to mean a logistic regression with more than 2 response levels, then yes. JMP^® can fit a nominal response with generalized logits, as well as an ordinal response with cumulative logits.   Nominal and ordinal logistic regression analysis options are available under the Personality drop down under Analyze ► Fit Model.   [Previously JMP Note 35252]

  sseligman

  Feb 5, 2023 12:16 AM

  1159 views | 0 replies

• Can I perform a Gauge Repeatability and Reliability (Gauge R&R) analysis in JMP®?

  Yes, by selecting Quality and Process ► Variability / Attribute Gauge Chart in the Analyze menu. Specify your response and grouping variables, and click OK. Then, from the Variability Gauge inverted red arrow menu, choose Gauge Studies ► Gauge R&R. [Previously JMP Note 35238]

  sseligman

  Feb 5, 2023 12:11 AM

  1220 views | 0 replies

• A DSUR/PSUR report in JMP® Clinical 8.0 might result in the error "Name arg must be quoted string . . ."

  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]

  laura_archer

  Feb 3, 2023 1:57 PM

  496 views | 0 replies

• JMP® Clinical 7.1.2 Risk Based Monitoring might result in errors when you add supplemental data

  This note addresses several issues with JMP Clinical 7.1.2 Risk Based Monitoring when supplemental data is used. While adding supplemental data, JMP Clinical 7.1.2 Risk Based Monitoring might generate an error similar to the following:
  
     Unexpected ";".
     Trying to parse operand for "=" operator.
     Line XX Column YY: objRefNS:NoActFlg = ?;
   When you add supplemental data, JMP Clinical 7.1.2 Risk Ba...

  laura_archer

  Feb 3, 2023 1:53 PM

  375 views | 0 replies

• JMP® Clinical Adverse Event Report is incorrectly labeling columns with wrong treatment group

  For some studies in JMP Clinical columns of the Adverse Event Report containing counts and percents are labeled with the wrong treatment group. To resolve this issue the two files attached to this note need to replace the existing files. To update these files please close JMP Clinical. Then use these files:  adverseeventsreport.sas should be copied to C:\Program Files\SASHome\JMPClinical\14\Clinic...

  laura_archer

  Feb 3, 2023 1:35 PM

  261 views | 0 replies

• JMP® Clinical 6.0 results in an error that LBTESTCD values are not unique when analyzing findings data

  The following error can occur in JMP^® Clinical 6.0 when analyzing findings: ERROR: Analysis cannot be completed because the LBTESTCD values are not unique across values of test category and/or subcategory. To work around this problem, replace the old FindingsMacros.sas file that is located in C:\Program Files\SASHome\JMPClinical\12\LifeSciences\MacroLib with this new FindingsMacros.sas file.    ...

  laura_archer

  Feb 3, 2023 1:29 PM

  176 views | 0 replies

• Translation files for "Overall Response" for oncology analysis

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

  laura_archer

  Feb 3, 2023 1:23 PM

  485 views | 0 replies

• The JMP® Clinical 7.1 API results in a JSL error when closeReviewBuilder() is used

  The JMP Clinical 7.1 API results in the following JSL error when the function closereviewbuilder() is used:   The namespace "this" is not defined{10378} in access or evaluation of
  'this:updateNavigatorSelection' , this:updateNavigatorSelection/*###*/() /*###*/ Click here to access the Hot Fix for this issue.   [Previously JMP Note 64958]

  laura_archer

  Feb 3, 2023 12:37 PM

  423 views | 0 replies

• The Hy's Law option to include on-trial measurements is not enabled in JMP® Clinical 8.0

  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]

  laura_archer

  Feb 3, 2023 12:36 PM

  557 views | 0 replies

• The error message "No SMQs are available based on the dialog selections" appears on the Standardized MedDRA Queries Incidence Screen

  In JMP^® Clinical 7.1, the following errors might appear on the SMQ Incidence Screen: Error:  No SMQs are available based on the dialog selections
  Error: Try selecting broad search terms or relaxing filters These errors appear when the MedDRA files do not include children’s SMQs. This issue is corrected in the JMP^® Clinical 7.1.2 Hot Fix. Errors are removed and no longer prevent the report from runn...

  laura_archer

  Feb 3, 2023 12:34 PM

  399 views | 0 replies

• The error "Variable xxTESTCD is not on file WORK.xx" might occur when findings are ADaM data sets and the variable xxTESTCD is not present

  In JMP^® Clinical 7.1, the AE Narrative might result in the following error when the ADaM data sets are used:  ERROR: Variable xxTESTCD is not on file WORK.xx. This issue can occur when the ADaM data set has the variable PARAMCD but not the xxTESTCD variable, for example.  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 ...

  laura_archer

  Feb 3, 2023 12:32 PM

  884 views | 0 replies

• The Create Live Report process fails in JMP® Clinical 8.0 when a profile has no data to display

  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]

  laura_archer

  Feb 3, 2023 12:31 PM

  465 views | 0 replies

• The Adverse Events Time to Event in JMP® Clinical 7.1 might incorrectly calculate days when datetime variables are used

  In JMP Clinical 7.1, the Adverse Events Time to Event might incorrectly calculate days when using datetime variables. The error arises because JMP Clinical is not considering time for the Adverse Event start date in calculating the days.   This issue is resolved in JMP^® Clinical 7.1.2 and JMP^® Clinical 8.0 with the following logic. If the Adverse Event start date and the Treatment start date both ...

  laura_archer

  Feb 3, 2023 12:29 PM

  313 views | 0 replies

• SMQ Analyses ERROR in algorithm to determine scope

  A bug was identified in the algorithm for determining SMQ analyses for a NARROW scope. This has been fixed in the Hot Fix found here. 
      [Previously JMP Note 61780]

  laura_archer

  Feb 3, 2023 12:27 PM

  335 views | 0 replies

• Running JMP® Clinical 6.1 on Non-English Operating Systems

  In order to run JMP® Clinical 6.1 on Chinese or Japanese operating systems apply the Hot Fix found here. This Hot Fix makes system accommodations to support JMP Clinical localized to Chinese Language and run in Chinese Operating Systems with Chinese data, as well as add additional enhancements for Japanese Operating Systems.   [Previously JMP Note 60231]

  laura_archer

  Feb 3, 2023 12:25 PM

  498 views | 0 replies

• Review templates that were created in a previous version of JMP® Clinical fail to open in JMP® Clinical 8.0

  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]

  laura_archer

  Feb 3, 2023 12:18 PM

  624 views | 0 replies

• Patient Recruitment results in the ERROR: A character operand was found in the %EVAL function

  An error may occur when running Patient Recruitment on a non-English operating system in JMP Clinical 7.0.  The error is    ERROR: A character operand was found in the %EVAL function or %IF condition where a numeric operand is required.
  The condition was: &mon = APR and &day = 31
  ERROR: The macro CHKDT will stop executing. MPRINT(PATRECRUIT): ;
  ERROR: The target date must be of this form: DDMMMYYY...

  laura_archer

  Feb 3, 2023 12:16 PM

  605 views | 0 replies

• You save a review template with a subject filter and an error occurs in JMP® Clinical 8.0

  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]

  laura_archer

  Feb 3, 2023 12:13 PM

  656 views | 0 replies

• Mortality Time to Event can incorrectly calculate the number of deaths

  Processing the DS domain data set made algorithmic assumptions of where to look for values representing death that would lead to not accurately counting/finding death records depending on the record order and disposition event categorization. Any studies/reports that used this analysis should be regenerated after applying the Hot Fix found here to avoid any possibility of death miscalculation.   [...

  laura_archer

  Feb 3, 2023 12:11 PM

  447 views | 0 replies

• JMP® Clinical 8.0 values that contain apostrophes have records deleted from results in incidence screens

  In JMP Clinical 8.0, some CDISC values (such as in AETERM and AELLT) can contain apostrophes. When you run incidence screen records for subjects with values that contain apostrophes, the records for the subjects are not counted in the results. Click here to access the Hot Fix for this issue.   [Previously JMP Note 67890]

  laura_archer

  Feb 3, 2023 12:09 PM

  439 views | 0 replies

• JMP® Clinical 8.0 translation errors occur for the Chinese language

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

  laura_archer

  Feb 3, 2023 12:04 PM

  532 views | 0 replies

• JMP® Clinical 8.0 produces an error that states that no subjects are found for data in non-English languages

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

  laura_archer

  Feb 3, 2023 12:02 PM

  633 views | 0 replies

• JMP® access to a SAS® Secure Metadata server requires sas.rutil.jar on the JMP system

  In order to be able to access data through a SAS^® Secure server using encryption on a remote system from JMP^® using SAS Integration, the file sas.rutil.jar needs to be copied from the secure server system and installed on the JMP client system in the following directory:   C:\Program Files\SAS\JMP\<version>\jmptojava\nnnn   where nnnn reflects the SAS version being accessed such as 9.2, 9.3, o...

  Ryan_Gilmore

  Jan 27, 2023 12:37 PM

  545 views | 0 replies

• JMP memory limitations imposed by operating systems

  JMP was designed and intended for interacting between the program, graphs and the data.  Thus, JMP stores everything in memory. The physical size of the file is not a true indicator of the amount of RAM needed to store the data.  For example, suppose you have a data table with only 1 numeric column and 1 million rows.  The amount of RAM needed to just hold the data would be calculated as 10 * 1,00...

  Ryan_Gilmore

  Jan 27, 2023 12:35 PM

  977 views | 0 replies

• JMP file types and their intended uses

  File types in JMP^® and their intended uses: JMP: JMP data table This table is the form data takes in JMP once it is read in, pasted or entered manually, in rows and columns as in a spreadsheet program. JRN: JMP Journal file A Journal file is a static copy of JMP analysis results or a means of producing a JMP based presentation. These are separate purposes with some crossover. The journal (.JRN fil...

  Bobby_Riggs

  Jan 27, 2023 12:14 PM

  8541 views | 0 replies