Installation Instructions for Hot Fix G77008

64-bit Enabled AIX

Hot fix G77008 addresses the issue(s) in SAS Warranty Analysis 4.31 as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/G77.html#G77008

G77008 is a "container" hot fix that contains the following "member" hot fixes which will update the software components as indicated.

G75008  updates  SAS Warranty Analysis Client 4.31
G76008  updates  SAS Warranty Analysis Mid-Tier 4.31
G74004  updates  SAS Warranty Analysis Server 4.31

Before applying this hot fix, follow the instructions in SAS Note 35968 to generate a SAS Deployment Registry report, then verify that the appropriate product releases are installed on your system. The release number information in the Registry report should match the 'member' release number information provided above for the software components installed on each machine in your deployment.

The hot fix downloaded, G77008pt.zip, includes the updates required for all components listed above on all applicable operating systems. To apply this hot fix on multiple machines, you can either save G77008pt.zip on each machine or save it in a network location that is accessible to all machines.

Do NOT extract the contents of G77008pt.zip. The hot fix installation process will extract the contents as needed.

IMPORTANT NOTES

1. Files delivered in this hot fix will be backed up during the installation process. However, it is good general practice to back up your system before applying updates to software.

2. You must have Administrator Privileges on your CLIENT or SERVER machine.

3. All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix.

4. This hot fix should be installed using the same userid who performed the initial software installation.

5. If any modifications have been made to the primary SAS Warranty Analysis solution catalog, located in <SASHOME>/SASFoundation/9.3/cmacros/wrtyanlmva/sasmacr.sas7bcat, then that catalog needs to be replaced with the originally shipped (or hotfix-modified) version of the catalog. Failure to do so will cause this hot fix to install improperly. The reason for this is that the hotfix installation process utilizes file modification dates when determining what to replace - and if the modification date on the sasmacr.sas7bcat file is not what the hotfix installation is expecting, then the existing catalog will not get replaced, and the hotfix install will not be complete. It is strongly recommended that if code/catalog modifications are needed, they be applied using the "override" protocol delivered with SAS Warranty Analysis.

PRE-INSTALLATION INSTRUCTIONS

Make backup of following set of jars and then delete any versions of them from

<SASHOME>/SASWarrantyAnalysisMidTier/4.31/Static/plugins/SWA_Eclipse_RCP

• sas.analytics.mfg.queue.client
• sas.analytics.mfg.warranty.app.nls
• sas.analytics.mfg.warranty.app
• sas.analytics.mfg.warranty.core.client
• sas.graph.silk
• sas.graph.statgraph.nls
• sas.graph.statgraph
• sas.iquery.services
• sas.iqueryutil
• sas.svc.core
• sas.svc.webdav
• sas.swing

INSTALLATION

The hot fix will be applied using the SAS Deployment Manager (SDM). By default, the SDM will search in the <SASHOME>/InstallMisc/HotFixes/New directory for hot fixes to be applied, but will also prompt for a location if you have downloaded hot fixes to a different directory.

After downloading G77008pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.3: User’s Guide.

The hot fix installation process generates the log file

<!SASHOME>/InstallMisc/InstallLogs/IT_date-and-time-stamp.log

Postexec log files are created after the installation is completed and identifies the files that were added, backed up, changed and removed. These log files include the ‘member’ hot fix id in the name of the file and are also written to the <!SASHOME>/InstallMisc/InstallLogs directory. There is one postexec log for each ‘member’ hot fix applied (member hot fixes are listed at the top of these instructions).

The content of this hot fix is listed in the hot fix manifest.

POST-INSTALLATION INSTRUCTIONS

For each product installed, click the link to be redirected to post-installation instructions.

G75008  updates  SAS Warranty Analysis Client 4.31
G76008  updates  SAS Warranty Analysis Mid-Tier 4.31
G74004  updates  SAS Warranty Analysis Server 4.31

G75008  updates  SAS Warranty Analysis Client 4.31

Please perform these steps on all SAS Warranty Analysis Client machines after installing SWA4.31 client pieces for hotfix.

The installation of the hot fix to the SAS Warranty Analysis Client assumes that the client is installed in

C:\Program Files\SASHome\

<SASHOME>\SASWarrantyAnalysisClient\4.31\configuration\config.ini

C:/Program Files/SASHome/

Example: to change the chunk size to '50 MB'
For CD client (in wrtyanl.ini file) add this line:

-Dswa.io.chunksize=50

For JWS client (in SWA_Eclipse_RCP.jnlp file) add this line:

< property name="swa.io.chunksize" value="50" > < /property >

1. Log on to SWA rich client and perform ‘export table to spreadsheet’ action once. This will create subdirectory named ‘Warranty’ under user’s Temp location.

2. Go to that ‘Warranty’ subdirectory under user’s TEMP directory. (The location of the TEMP directory varies by operating system version, this example assumes a user name of ‘dummyuser’):
   

   For Windows 7: C:\Users\dummyuser\AppData\Local\Temp
   For Windows XP: C:\Documents and Settings\dummyuser\Local Settings\Temp
   For Windows Server 2008: C:\Users\dummyuser\AppData\Local\Temp\2
   

3. Create a file in the ‘Warranty’ directory mentioned above with name DO_NOT_EXPORT.txt (it can be empty). Subsequent exports will all go to this "Warranty" subdirectory.

4. If the administrator wants to configure different subdirectory name, s/he needs to add property 'swa.io.tmpdirname' and assign desired value.
   

   Example: to change default subdirectory name from ‘Warranty’ to 'SWADownloadArea':
   For CD client (in wrtyanl.ini file) add this line:
   -Dswa.io.tmpdirname=SWADownloadArea
   
   For JWS client (in SWA_Eclipse_RCP.jnlp file) add this line:
   <property name="swa.io.tmpdirname" value="SWADownloadArea"> < /property >
   
   NOTE: If '-Dswa.io.tmpdirname=SWADownloadArea' parameter is set then DO_NOT_EXPORT.txt file needs to be created in this subdirectory.

5. A new configuration parameter has been defined to control how long the downloaded CSV files will remain in the user’s TEMP area before being automatically deleted. To set this parameter, open SAS Management Console (as the administrator), and navigate to Configuration Manager -> SAS Application Infrastructure -> Warranty Analysis 4.3 and right click to bringing up the Properties. In the advanced tab, enter swa.io.tmpdirfile.daysoldtodelete=N (where N equals the number of days for files to age out - recommended setting is 30).

6. In Warranty Analysis, right-click on analysis result table and choose Export Table to Spreadsheet.

7. Exported file will be saved in the subdirectory (Warranty / user defined value for -Dswa.io.tmpdirname parameter) of the user’s TEMP area with a new naming convention (analysisName_analysisType_dateTimeStamp.CSV):
   

   - a Details Analysis having the name 'DetailsTable1', the file name would be 'DetailsTable1_DETAIL_2013_06_11_05_49_23.CSV'
   - a Pareto Analysis having the name 'Pareto1', the file name would be 'Pareto1_PARETO_2013_06_11_05_42_27.CSV'

8. The UI will display a message containing the location of the saved file.

9. The behavior of exporting to CSV files will change if ‘DO_NOT_EXPORT.txt’ is present in mentioned subdirectory under TEMP then message would be shown and file will not be opened directly. However there will be no change to the naming convention for CSV files export from places other than analysis/report output.

G76008  updates  SAS Warranty Analysis Mid-Tier 4.31

Web application Update

1. Delete

<SASHOME>/SASVersionedJarRepository/eclipse/com.sas.app.launcher.cacheFile

In order for this step to execute correctly, the Metadata Server must be running.

1.1 Invoke the SAS Deployment Manager 9.3

From the SASDeploymentManager directory launch sasdm.sh.
SAS Deployment Manager is installed in the following default location:

<SASHOME>/SASDeploymentManager/9.3

1.2 Select a language in the Choose Language box

1.3 Select Rebuild Web Applications

1.4 Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated

1.5 Specify Connection Information, including the sasadm User ID and Password

1.6 Select Warranty Analysis 4.3 as the Web Application to Rebuild

1.7 Verify the information on the Summary screen and select Start

1.8 Select Finish when the deployment is complete

This process will update the SAS Warranty Analysis Mid-Tier 4.31 ear in

<CONFIGDIR>/Lev1/Web/Staging (The "Level" here should be the same Level as in Step 1.4 above)

Step 2: Re-deploy Web Applications

Follow the steps provided for your initial Solution deployment to re-deploy the updated ear to your web application.

G74004  updates  SAS Warranty Analysis Server 4.31

The following set of instructions are listed in the order they were delivered in SAS Warranty Analysis (cumulative) Hotfixes. Perform them in order beginning with the hotfix that is not currently applied on the server - in other words, if a step has already been performed during a previous hotfix installation, then it does not need to be repeated.

>>>Start of Hotfix 1 updates <<<
The following files are delivered to the SAS install area. Take a backup of below files from configuration directory and then copy files locations mentioned below:

From: <SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/smd/analysisoptionattributes_nls.smd
To: <CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/smd

From: <SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/install/swa43_migration.sql
To: <CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install

From: <SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/install/swa42_migration.sql
To: <CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install

From: <SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/install/swa431_hotfix.sas
To: <CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install

From: <SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/install/swa431_migration.sql
To: <CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install

From: <SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/install/configure/analysisoptions.csv
To: <CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install/configure

1. Start an interactive SAS session using the configuration file
   <CONFIGDIR>\Lev1\Applications\SASWarrantyAnalysis4.3\install\sasv9_swaconn.cfg
   to ensure that the PARMSL library reference is properly assigned.
   

   a. Navigate to "<SASHOME>/SASFoundation/9.3/"
   b. Run "sas -config <CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install/sasv9_swaconn.cfg"
   
   OR
   
   a. execute the below path
   "<SASHOME>/SASFoundation/9.3/sas -config <CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install/sasv9_swaconn.cfg" Press enter

2. File > Open > then select this program:
   <CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install/swa431_hotfix.sas"
   in your interactive SAS session, submit it, and it will update the PARMSL datasets.
   

Delivered: <SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/interactionxml/analysisSetup.xml
Merge With: <CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/interactionxml/analysisSetup.xml

<Interaction> 

     <!-- 

     //If Exposure Type = Usage
     //   Disable Apply Usage Profile and set to Yes
     //      Disable Calculation Method and set to Adjusted
     //      Disable Warranty Usage Max Mileage combo box
     //End If
     -->
    <FieldSelected fieldId="AOA163">
    <Value label="Usage">USAGE</Value>
    </FieldSelected>
    <Field fieldId="AOA5" fieldVisibility="DISABLED" requiresValue="true" minSelections="1" maxSelections="1">
    <SelectedValue>True</SelectedValue>
    </Field>
    <Field fieldId="AOA30" fieldVisibility="DISABLED" requiresValue="true" minSelections="1" maxSelections="1">
    <SelectedValue>projected</SelectedValue>
    </Field>
    <Field fieldId="AOA8" fieldVisibility="DISABLED" requiresValue="true" minSelections="1" maxSelections="1">
        <SelectedValue>100000-UNLIMITED</SelectedValue>
    </Field>
    <Field fieldId="AOA134" fieldVisibility="DISABLED" requiresValue="true" minSelections="1" maxSelections="1">
        <SelectedValue>frombuild</SelectedValue>
    </Field>
</Interaction>

<Interaction>
                <!--
                //Applicable to Summary Tables
                //If Exposure Type = TIS
                //            Enable Apply Usage Profile and set to Yes
                //      Enable Calculation Method and set to Adjusted
                //      Enable Warranty Usage Max Mileage combo box
                //End If
                -->
    <FieldSelected fieldId="AOA163">
                <Value label="TIS">TIS</Value>
    </FieldSelected>
    <Field fieldId="AOA5" fieldVisibility="ENABLED" requiresValue="true" minSelections="1" maxSelections="1">
                <SelectedValue>True</SelectedValue>
    </Field>
    <Field fieldId="AOA30" fieldVisibility="ENABLED" requiresValue="true" minSelections="1" maxSelections="1">
                <SelectedValue>projected</SelectedValue>
    </Field>
    <Field fieldId="AOA8" fieldVisibility="ENABLED" requiresValue="true" minSelections="1" maxSelections="1">
        <SelectedValue>36000</SelectedValue>
    </Field>
    <Field fieldId="AOA134" fieldVisibility="ENABLED" requiresValue="true" minSelections="1" maxSelections="1">
        <ResetField keepCurrentValuesIfValid="true"/>
    </Field>
</Interaction>

<Interaction>
                <!--
                //Applicable to Summary Tables
                //If Exposure Type = none
                //            Enable Apply Usage Profile and set to Yes
                //      Enable Calculation Method and set to Adjusted
                //      Enable Warranty Usage Max Mileage combo box
                //End If
                -->
    <FieldSelected fieldId="AOA163">
                <NoValues/>
    </FieldSelected>
    <Field fieldId="AOA5" fieldVisibility="ENABLED" requiresValue="true" minSelections="1" maxSelections="1">
                <SelectedValue>True</SelectedValue>
    </Field>
    <Field fieldId="AOA30" fieldVisibility="ENABLED" requiresValue="true" minSelections="1" maxSelections="1">
                <SelectedValue>projected</SelectedValue>
    </Field>
    <Field fieldId="AOA8" fieldVisibility="ENABLED" requiresValue="true" minSelections="1" maxSelections="1">
        <SelectedValue>36000</SelectedValue>
    </Field>
    <Field fieldId="AOA134" fieldVisibility="ENABLED" requiresValue="true" minSelections="1" maxSelections="1">
        <ResetField keepCurrentValuesIfValid="true"/>
    </Field>
</Interaction>

1. Edit the init.sas file in a text editor and declare the g_dpi global variable:
   Look for the line that reads: %global _server; and edit it to read: %global _server g_dpi;
2. Initialize the g_dpi variable by adding the following line below the %global statement (which concludes with a semi-colon).
   %let g_dpi=300;

Replace this section of code:

	%util_assignUserLibname(p_username=&l_personname,
		p_libname=WARRUSER, p_subDirPath=filteredData,
		p_options=%str(access=readonly));

With this section of code:

	/* *****************************************************
	not using this call because it will create the directory if it does not exist;
		%util_assignUserLibname(p_username=&l_personname,
			p_libname=WARRUSER, p_subDirPath=filteredData,
			p_options=%str(access=readonly));
	***************************************************** */

	%global g_serverPath g_guarc;        /* cis: S0796738 */
	%local l_dirpath nummems;
	%let nummems = 0;
	%util_getuserattributes(p_personomrname=&l_personname,
							servername_mv=g_servername,
							serverpath_mv=g_serverPath
	);
	%if &g_guarc EQ 0 %then  /* user's data directory exists in the PARMSL.USERATTRIBUTES table */
	%do;
			%let l_dirpath = &g_serverPath.&g_slash.filteredData;
			data _null_;
			rc = filename("tempdir", "&l_dirpath");
			dirid = dopen("tempdir");
			if dirid GT 0 then
				members = dnum(dirid);
			dirid = dclose(dirid);
			call symput("nummems",members);
			run;

			%if &nummems GT 0 %then  /* USERFDL physical directory exists and contains data */
			libname WARRUSER "&l_dirpath" access=readonly;
	%end;
	/* -------------------------------------- */

Then make this modification after "%put &l_Errormsg;" and before "%mend util_allocWARRUSER;":

   	%put &l_Errormsg;

   	%sysmstoreclear;;         /* insert these 3 new lines */
   	libname swasrcl clear;   /* <<<                      */
   	libname response clear;  /* <<<                      */

	%mend util_allocWARRUSER;

1. Make a backup of the existing Graphics Template Catalog (templat.sas7bitm) which is located in USERTL library before continuing.
   
   
2. The following files which are delivered to the SAS Install area need to be copied over to the SAS Configuration area (<CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install/templates):

   	<SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/install/templates/sgTemplate_BarChart.sas
   	<SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/install/templates/sgTemplate_BarChart_MVA.sas
   	<SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/install/templates/sgTemplate_BarChartOverlay.sas
   	<SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/install/templates/sgTemplate_ControlChart.sas
   	<SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/install/templates/sgTemplate_Dummy.sas
   	<SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/install/templates/sgTemplate_LineOverlay.sas
   	<SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/install/templates/sgTemplate_OverlayTrend.sas
   	<SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/install/templates/sgTemplate_ProbPlot.sas
   	<SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/install/templates/sgTemplate_SDChart.sas
   	<SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/install/templates/sgTemplate_SolidDashLines.sas
   	<SASHOME>/SASFoundation/9.3/misc/wrtyanlmva/install/templates/styleTemplate_SWAStyle.sas
   

3. Start an interactive SAS session using the configuration file (please refer to step #1 of ‘Update the PARMSL datasets’ section to start an interactive SAS session).

   <CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install/sasv9_swaconn.cfg
   (to ensure that the USERTL library reference is properly assigned)

4. Modify the path in the following code to point to your configuration directory, and modify the g_slash macro variable below to run in your environment:
   

   	Options validvarname=v7;
   	%let g_swaConfigRoot = <CONFIGDIR>\Lev1\Applications\SASWarrantyAnalysis4.3\install;
   	%let g_slash = /;   /* this designates the path separator used with the operating system: "/" for unix, "\" for Windows */
   
   	%include "&g_swaConfigRoot.&g_slash.templates&g_slash.sgTagsets_GTL.sas";
   	%include "&g_swaConfigRoot.&g_slash.templates&g_slash.sgTemplate_BarChart.sas";
   	%include "&g_swaConfigRoot.&g_slash.templates&g_slash.sgTemplate_BarChart_MVA.sas";
   	%include "&g_swaConfigRoot.&g_slash.templates&g_slash.sgTemplate_BarChartOverlay.sas";
   	%include "&g_swaConfigRoot.&g_slash.templates&g_slash.sgTemplate_ControlChart.sas";
   	%include "&g_swaConfigRoot.&g_slash.templates&g_slash.sgTemplate_Dummy.sas";
   	%include "&g_swaConfigRoot.&g_slash.templates&g_slash.sgTemplate_LineOverlay.sas";
   	%include "&g_swaConfigRoot.&g_slash.templates&g_slash.sgTemplate_OverlayTrend.sas";
   	%include "&g_swaConfigRoot.&g_slash.templates&g_slash.sgTemplate_ProbPlot.sas";
   	%include "&g_swaConfigRoot.&g_slash.templates&g_slash.sgTemplate_SDChart.sas";
   	%include "&g_swaConfigRoot.&g_slash.templates&g_slash.sgTemplate_SolidDashLines.sas";
   	%include "&g_swaConfigRoot.&g_slash.templates&g_slash.styleTemplate_SWAStyle.sas";
   

   Note: this code was excerpted from <CONFIGDIR>/Lev1/Applications/SASWarrantyAnalysis4.3/install/runinstall.sas.
   
   
5. Run this code in your interactive SAS session, and it will update the contents of your Graphics Template Catalog.

	proc sql noprint;
   		insert into parmsl.analysismacvars
   		values ("COMMON", "ShowDataAsOfDateFootnote", "TRUE")
   		values ("COMMON", "ShowHollowPointFootnote", "TRUE");
	quit;

1. Both in the application (Reports Workspace) and in the thin client (SAS Warranty Analysis Reports portal tab), the new default sort order of Reports is descending by Run Date.
2. Also, in the thin client (SAS Warranty Analysis Reports portal tab), there is new information being displayed about the filters which have been applied in the viewer. The user will see a new icon next to the column label to designate that the table has been sorted by that column.

1. Modifications have been made to adjust the layout of legends that appear underneath the SAS Warranty Analysis graphs. The dimensions have been changed to ensure that a legend will appear with the graph, when applicable, both in the UI and when saved as a PDF.
2. On line charts, the square marker has been replaced with an upside down triangle.
3. When viewing an exported PDF, a page break will precede each graph, to ensure that the graph’s title appears at the top of the page.
4. And finally, when a graph displays both mature and immature points, there is no longer a gap in the line between a mature point and an immature point.

This completes the installation of hot fix G77008 on 64-bit Enabled AIX.