SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 14624: SASIQ fails to validate a Credit Score file updated as part of SAS 9.x (Japanese) installation

DetailsHotfixAboutRate It
After you update SAS 9.x (Japanese) and run the SAS Installation
Qualification (IQ) tool, the following error message appears in the
SASIQ.pdf report:

   ERROR:  Unable to locate a match for Option creditscrnod in product
   Japanese NLS Support for hot fix Japanese NLS Support.

The file is part of the Credit Score product. It is updated as part of
SAS 9.x (Japanese). The file is added to the db_nls_ja_dmine.ini
file, but it is in reference to the credit score product, not dmine.

In db_nls_ja_dmine.ini, you find:

   RequiredBy=nls_ja
   Component=db_nls_ja_dmine:Japanese NLS Support::48583137
   Option1=creditscrnod:SAS Credit Scoring ::410624:0:0
   Option2=dmine:Enterprise Miner ::48172513:19096033:0
   [creditscrnod]
   vfile1 =
   emcredit.sas7bcat,nls\ja\sashelp,nls\ja\sashelp,410624,,2004/11/11
   10:30:36,SASROOT

The problem is that there is no creditscrnod option in nls_ja.ini (the
RequiredBy component).

As long as the installed file that causes this error (in this case
emcredit.sas7bcat) is not added during the software update, that is, it
previously existed on the your machine and the SoftwareUpdate is
simply updating the file, then the file still gets validated correctly.
It is updated correctly because a new core\sasint\checksums file is
installed with each SoftwareUpdate and the original component INI file
has an entry for the file. Therefore, the default checksum for the file
is correct and a SASIQ entry in the original INI file is found.

However, if the file is new to the component, no entry exists in the
component's original INI file and the file is ignored by SASIQ.

This message might appear at the same time

   ERROR:  Unable to locate a match for Option mysql in product DBCS
   support for hot fix DBCS support.

under the following conditions

   * Any Asian language or English with DBCS support
   * Appears in the DOS window where the sasiq.exe process is running
   * Occurs at the beginning of the process when the checksums data
     files are being processed
   * Does not produce a checksum failure.


A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

http://www.sas.com/techsup/download/hotfix/e9_sbcs_prod_list.html#014624

For customers running SAS with Asian Language Support (DBCS), this
fix should be downloaded from:

http://www.sas.com/techsup/download/hotfix/e9_dbcs_prod_list.html#014624


Operating System and Release Information

Product FamilyProductSystemSAS Release
ReportedFixed*
SAS SystemBase SASMicrosoft Windows XP Professional9.1 TS1M39.1 TS1M3 SP4
Microsoft Windows Server 2003 Standard Edition9.1 TS1M39.1 TS1M3 SP4
Microsoft Windows NT Workstation9.1 TS1M39.1 TS1M3 SP4
Microsoft Windows Server 2003 Enterprise Edition9.1 TS1M39.1 TS1M3 SP4
Microsoft Windows Server 2003 Datacenter Edition9.1 TS1M39.1 TS1M3 SP4
Microsoft Windows 2000 Server9.1 TS1M39.1 TS1M3 SP4
Microsoft Windows 2000 Advanced Server9.1 TS1M39.1 TS1M3 SP4
Microsoft Windows 2000 Datacenter Server9.1 TS1M39.1 TS1M3 SP4
Microsoft Windows 2000 Professional9.1 TS1M39.1 TS1M3 SP4
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.