The hot fixes and the installation actions described in this SAS Note are required for SAS IT Resource Management 3.1.1 to function properly. To update your software with the required fixes, follow these steps:

On the SAS IT Resource Management server:

1. Install the latest Base SAS^® hot-fix bundle. Hot Fixes are available on the SAS Technical Support Hot Fixes site.
   1. On the hot-fix Web page, click BASE SAS Bundle.
   2. On the "BASE SAS Hot Fix Bundle Downloads" page, search for your operating system and install the bundle for that system.

   Note: For all systems except Windows, a dialog box might appear during the hot-fix download. This dialog box includes a list of hot fixes that you need to reapply if you applied them prior to installing the Base SAS hot-fix bundle. Windows systems do not receive the dialog box because hot fixes do not need to be reapplied for Windows environments.

   For additional hot fixes that might be applicable to your site and operating system, see the SAS Technical Support Hot Fixes site. Hot-fix announcements are also provided in the TSNEWS-L listserv, which includes special notification when a hot fix is released for an ALERT-level issue. The hot fix names referenced in this note are accurate as of the ship date for SAS IT Resource Management hot fix 311IS04. If a hot fix replaces one listed in this note, the links on the Technical Support Hot Fixes site are updated to direct you to the new hot fix that you should apply.

   (The next three steps apply to z/OS sites only. All other sites continue to step 5.)

2. z/OS sites only: SAS IT Resource Management sites on z/OS should apply hot fix E9BC36.

   E9BC36 is applicable to z/OS sites only because this hot fix is included as part of the hot-fix bundle for all other operating systems. This hot fix must be applied on z/OS before you install any SAS IT Resource Management hot fixes. This hot fix requires that you manually install jar files and modify the JREOPTIONS SAS system option. Verify that the jar files are installed in the proper directories, and that backups of the original jar files are not stored in the production directories to which the new jar files are copied.

3. z/OS sites only: Sites running z/OS 1.11 operating environments require a Java level of 1.4.2 Service Refresh (SR) 13, Fix Pack (FP) 2 or higher.
   

   In z/OS 1.11 operating environments, SAS 9.1.3 requires a Java level of 1.4.2 Service Refresh (SR) 13, Fix Pack (FP) 2 or higher. Running with Java 1.4.2 SR11 can result in a segmentation violation (system abend 0C4). Sites that have SAS 9.1.3 already installed might have installed a level of Java that is not compatible with z/OS release 1.11, therefore, a problem might occur. For more information, see SAS Note 38132, "SAS® 9.1.3 requires Java 1.4.2 Service Refresh 13, Fix Pack 2 or higher in z/OS 1.11 operating environments"

4. z/OS sites only: Implement the TKOPT_CPOOL3 environment variable.
   

   In addition to installing the latest Base SAS^® hot-fix bundle, you must add the following statement to the TKMVSENV member of the &prefix.Wn.SRVENV data set. It is case-sensitive so enter it exactly as shown, with no characters to the right of the "=":

   set TKOPT_CPOOL3=

   For more details, see SAS Note 31661, "Using the TKOPT_CPOOL3= threaded-kernel environment variable causes large amounts of memory to be used" and SAS Note 31641, "TKMVSENV memory-related environment variables to consider for tuning the server environment running in z/OS"

   Existing SAS IT Resource Management sites that received a special-consideration zap from SAS Technical Support for this issue documented in SAS Note 31661 only: The latest Base SAS^® hot-fix bundle currently provides the same functionality as the special-consideration zap you received. Therefore, if you install this hot fix, you no longer need to apply the zap.

5. Install SAS IT Resource Management Hot Fix 311IS04.

   At this point, install the latest SAS IT Resource Management hot fix, 311IS04. To accomplish this task, you might need to stop the metadata server and the object spawner, as well as any other SAS sessions that use the SASHELP library, so that updates can be made to this library.

   For z/OS sites only: Make sure that you run both the JCLUSS1 and JCLSHELP jobs.
6. Verify the installation of Hot Fix 311IS04

   To verify the installation of Hot Fix 311IS04, invoke the macro %RMVINST, as follows:

   %RMVINST( metaserver=mybox.subdomain.domain.com, metaport=port, metauser=username, metapass=password);

   For more information about this macro and each of these parameters, see the documentation that is provided inside the macro. Once the macro is invoked successfully, you should find a note similar to the following in your SAS log:

   NOTE: Found copy of sas.solutions.itms.omil.jar at 
   file:/[installedlocation]/sas.solutions.itms.omil.jar, 
   version is 3.1.1.4.[datestamp].[build]
   

   • In this note, installedlocation specifies the location of SAS^® Foundation. The location varies by platform, but typically it is as follows:
     • Under Windows, the value for installedlocation is itmsmvadata\sasmisc.
     • Under UNIX, the value is misc/itmsmvadata.
     • Under z/OS, the value is itmscore, which is found under the default directory that is specified in the INSTALL_DIR= line of the &CNTLSDSN(USSUNTAR) SAS installation job. The default value for INSTALL_DIR directory is similar to /usr/lpp/SAS/SAS_9.1/BI/USER.PREFenen, where USER.PREF is the high-level qualifier used for the traditional data sets in the installation, and en is the encoding of this installation (for example, W0 is the encoding for US sites).
   • You can ignore the datestamp and build fields in this note, but you do need to verify that the 3.1.1.4 version stamp is correct. Verify that the implementation versions shown in your log matches those shown above.

     For z/OS sites only: The RMVINST macro provided with this hot fix determines the location of the sas.iquery.services.jar file. Verify that the sas.iquery.dataservices.jar file found by this macro and the sas.iquery.metadata.jar file that is stored at this same location match those jar files provided with Hot Fix E9BC36. Incorrect versions of these jar files cause unpredictable behavior when you access the information maps created by the ITRM aggregation jobs.

7. If your installation requires interaction with MXG, then you must also modify your custom SAS IT Resource Management autoexec file that is used by your workspace server by adding the %GLOBAL and %LET macro statements, as follows:
   %RMMXGINI; %global cpcolect; %let cpcolect=SMF;
   For more details about this customization, see SAS Note 35328, "RMDUPCHK macro incorrectly removing records as duplicate with SMF data in ITRM 3.1.1".
8. Finally, select the action that applies to your site from the following list:

   • For a new SAS IT Resource Management installation on a z/OS system: Return to the Configuration Guide for SAS^® 9.1.3 Foundation for z/OS^® to perform the next step, which is to update default authorizations.

     For a new SAS IT Resource Management installation on a Windows or a UNIX system: Perform the client-tier modifications, which are found in the Post-Installation Guide for SAS^® 9.1.3 Foundation for Microsoft^® Windows^® and Configuration Guide for SAS^® 9.1.3 Foundation for UNIX^® Environments

   • For existing SAS IT Resource Management sites: After you apply Hot Fix 311IS04, you must redeploy all existing SAS IT Resource Management jobs. Failure to redeploy existing jobs might generate errors when you try to use the staging or aggregation jobs.

On SAS IT Resource Management client machines:

1. Apply the latest SAS Data Integration Studio hotfix:
   http://ftp.sas.com/techsup/download/hotfix/dis34.html
2. Apply the latest SAS Enterprise Guide hotfix:
   http://ftp.sas.com/techsup/download/hotfix/ent_guide41.html
3. Apply the latest hotfix for SAS Information Map Studio:
   http://ftp.sas.com/techsup/download/hotfix/ims31.html
4. Apply the client portions of IT Resource Management hotfix 311IS04. This will require that you download the Windows version of this hotfix:
   http://ftp.sas.com/techsup/download/hotfix/itrm311.html

Operating System and Release Information