If you run the USSUNTAR job to load the tar files into HFS after the
initial install and then perform an addon of Graph, Data Mining, R3, or
Secure Dimensions, the USSUNTAR job will yield a RC 304.

This is due to the issuance of a link of JPROXY within the USSUNTAR that
was already established in the initial run of the USSUNTAR job.

Add the 3 lines of code indicated below to the USSUNTAR job to
check whether the JPROXY link exists.

Note: The xxxxxx in the paths below would be unique at each particular
      site.

Corrected code.

if test ! -h jproxy      ******************ADDED LINE ********
   then                  ******************ADDED LINE ********
    ln -e JPROXY jproxy
    rc=$?
    if test ! "$rc" = "0"
    then
     msg="Unable to establish link to JPROXY"
     echo $msg
     echo "CONTROL ASIS" >> /u/xxxxxx/tmp/ussuntar.sherr
     echo "WRITE $msg" >> /u/xxxxxx/tmp/ussuntar.sherr
     echo "EXIT(12)" >> /u/xxxxxx/tmp/ussuntar.sherr
     exit 12
    fi
   fi                    **************** ADDED LINE ***********
   pax -r -v -f /u/xxxxxx/tmp/......


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#014662

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#014662

Operating System and Release Information

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

A fix for SAS 9.1.3 (9.1 TS1M3) with Asian Language Support (DBCS) for this issue is available at :