INSTALLATION INSTRUCTIONS FOR HOT FIX E9BC36 ON z/OS (OS/390) BEFORE DOWNLOADING: The hot fix E9BC36 addresses the issue(s) in SAS 9.1.3 (9.1 TS1M3) of Base SAS software on z/OS (OS/390) as documented in the "Issue(s) Addressed" section of the hot fix download page: http://ftp.sas.com/techsup/download/hotfix/e9_sbcs_prod_list.html#e9bc36 The following file(s) will be installed: * e9bc36os.xmit CNTL PDS in XMIT format. It contains all of the XMIT code necessary to apply the hotfix. IMPORTANT NOTE(S): 1. You must have SAS 9.1.3 (9.1 TS1M3) and SAS 9.1.3 Service Pack 4 installed on your system before applying this hot fix. 2. All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix. 3. Before proceeding with STEP 5 of the INSTALLATION INSTRUCTIONS, insure no 9.1 SAS jobs are running because this step requires exclusive access to the SASHELP library. INTRODUCTION: Please take a moment to read through this entire document before attempting to install this hot fix. There are two steps to this portion of the hot fix that must both be completed: 1) Extraction of updates 2) Copying the updated content to the appropriate target locations 3) Modify JREOPTIONS setting 1) INSTRUCTIONS FOR EXTRACTION OF UPDATES The following instructions describe the steps for extracting the contents of the downloaded file, moving the files to your z/OS (OS/390) system and installing the hot fix. STEP 1.1 PRE-ALLOCATE THE XMIT FILE ON MVS Pre-allocate a file on MVS (e.g. 'sas.hotfix.xmit') with the following DCB: Organization : PS Record format : FB Record length : 80 Block size : 3120 Check the size of the unzipped xmit file to determine the space requirements for the MVS XMIT file. STEP 1.2: FTP THE XMIT FILE TO MVS FTP the XMIT file into this newly created file. This can be done in one of 2 ways: Method 1) Download the packaged hot fix to your PC. The packaged hot fix is a is a self extracting executable. Launching the executable will extract the z/OS (OS/390) files to a default location example: C:\zos\e9bc36os You will be prompted during the extraction process to accept or overwrite the default unzip location. The remaining steps in these installation instructions assume that you have unzipped the files to the default location After extracting the file, FTP the e9bc36os.xmit file to your MVS system doing a BINARY upload into the preallocated file created in step 1. Method 2) From MVS, FTP to ftp.sas.com using userid=anonymous and password=your.email@address Once you're logged on, cd into the following directory: /techsup/download/hotfix/ve9/base/e9bc36/mvs Issue the following commands where 'sas.hotfix.xmit' is the filename you created in step 1.1 binary get e9bc36os.xmit 'sas.hotfix.xmit' (rep quit STEP 1.3: RECEIVE THE XMIT FILE TO CREATE THE CNTL PDS On MVS do a RECEIVE command on the uploaded XMIT file as follows where 'sas.hotfix.xmit' is the preallocated file in step 1. receive indataset('sas.hotfix.xmit') After doing this you will be prompted with something similar to the following: INMR901I Dataset DATA.SET.NAME from USERID on ???????? INMR906A Enter restore parameters or 'DELETE' or 'END' + at this prompt you sould enter: DA('sas.hotfix.cntl') where sas.hotfix.cntl will be a new PDS that contains all of the parts necessary to apply this hot fix. STEP 1.4: EXECUTE THE REXX EXEC In your new CNTL data set is a REXX exec that will, if applicable, create any new libraries and, if applicable, generate any JCL required to modify SAS catalogs in your SAS system and/or modify any USS content in your SAS system. Execute this REXX exec from an ISPF prompt: ex 'sas.hotfix.cntl(rexx)' STEP 1.5: RUN ANY GENERATED JCL Run all JCLxxxxx members that were generated in your CNTL data set. Be sure to review job specific instructions that are in the comments of the jobs. In the JCLUSSx job(s) for e9bc36, the INSTALL_DIR variable can be set to any directory to which that the submitting userid has write access. The USS content will be copied to the appropriate target locations in subsequent steps. You can use the same directory for all of the JCLUSSx jobs. STEP 1.6: MERGE GENERATED LIBRARIES WITH SAS If the REXX exec created: * '&prefix.HFE9BC36.LIBRARY' then you will need to replace the like-named modules in your current SAS 9.1.3 (9.1 TS1M3) installation library with the modules loaded to '&prefix.HFE9BC36.LIBRARY'. We suggest you rename the modules in the current SAS 9.1.3 (9.1 TS1M3) installation library before replacing. * '&prefix.HFE9BC36.DBCS.LIBRARY' then you will need to replace the like-named modules in your current SAS 9.1.3 (9.1 TS1M3) installation DBCS library with the modules loaded to '&prefix.HFE9BC36.DBCS.LIBRARY'. We suggest you rename the modules in the current SAS 9.1.3 (9.1 TS1M3) installation library before replacing. * '&prefix.HFE9BC36.SASMSG' then you will need to replace the like-named members in your current SAS 9.1.3 (9.1 TS1M3) installation SASMSG library with the members loaded to '&prefix.HFE9BC36.SASMSG'. We suggest you rename the members in the current SAS 9.1.3 (9.1 TS1M3) installation SASMSG library before replacing. * '&prefix.HFE9BC36.AUTOLIB' then you will need to replace the like-named members in your current SAS 9.1.3 (9.1 TS1M3) installation AUTOLIB library with the members loaded to '&prefix.HFE9BC36.AUTOLIB'. We suggest you rename the members in the current SAS 9.1.3 (9.1 TS1M3) installation AUTOLIB library before replacing. * '&prefix.HFE9BC36.ITRM.CPMISC' then you will need to replace the like-named members in your current SAS 9.1.3 (9.1 TS1M3) installation CPMISC library with the members loaded to '&prefix.HFE9BC36.ITRM.CPMISC'. We suggest you rename the members in the current SAS 9.1.3 (9.1 TS1M3) installation CPMISC library before replacing. ADDITIONAL NOTES: * If the REXX exec created a '&prefix.HFE9BC36.LIBRARY' that contains a SASHOST, SASXAL, or SASXA1 module, and if you set SAS System options by assembling the DEFAULT OPTIONS TABLE using the BAOPTS1 member of the original CNTL data set, then you must re-assemble this table after applying this hot fix. To re-assemble this table do the following: 1) Edit the BAOPTS1 member in the original CNTL data set. 2) Change the SYSLMOD DD in all three LINK EDIT steps to point to the new HLQ.LIBRARY 3) rerun BAOPTS1. * If the REXX exec created a '&prefix.HFE9BC36.LIBRARY' and you run with an entry point of SASXAL then you will need to look in the unloaded library to see if any of the new modules are installed in your LPA. If so, then you will need to replace them with the new modules. In the installation guide, the modules recommended for installation in the LPA are SASXAL SABXSPL SABXDML SABDS SABSCLL SABDBGM SABZPLH SABXGPH Please note that if you use the BNDLSUFX option, you will have to rename the modules appropriately in your LPA. For more information about the LPA bundled configuration and information about using the BNDLSUFX option, please refer to the section entitled "Installing The SAS System Into The LPA" in the "Installation Instructions and System Manager's Guide" appropriate to the Version and maintenance level for your SAS System. 2) INSTRUCTIONS FOR COPYING THE UPDATED CONTENT TO THE APPROPRIATE TARGET LOCATIONS In the directions below, there are references to several different directory locations. In general, these directories are located as follows: "Extraction Directory", this should be the directory specified as INSTALL_DIR in the JCLUSSx jobs "SAS Installation Directory", this should be the directory specified as INSTALL_DIR in the original USSUNTAR jobs used to install the SAS System. The default name of this directory is: /usr/lpp/SAS/SAS_9.1/USER.PREFyy where: - /usr/lpp/SAS/SAS_9.1/ is the mount point - USER.PREFIX is the high-level prefix specified by the installer. - yy represents the encoding "Backup Location", this location will be a directory used to make backups of updated files. The name and location of this directory is up to you; however, it should not be in your "SAS Installation Directory" or in any of it's subdirectories. You should also be logged in to your server using the same userid as was used for the original installation. Failure to do so may result in errors due to file system permission limitations. STEP 2.1: BACKUP EXISTING DIRECTORIES Prior to copying any new content into any of the directories listed above, you should backup the existing content. You should select a non-temporary location on your file system for these backups to be written to. To do this, use the mv command as follows: 1- If your directory does not exist, then create it. 2- If /hostcm directory does not exist, then create it. 3- Move the following files: sas.iquery.dataservices.jar sas.iquery.metadata.jar from: /hostcm to: /hostcm STEP 2.2 COPY THE FILES FROM YOUR EXTRACTED LOCATION You need to copy the new files from the extraction directory to the appropriate locations Copy the following files: sas.iquery.dataservices.jar sas.iquery.metadata.jar from: /hostcm to: /hostcm 3) MODIFY JREOPTIONS SETTING To fully implement the fix for SN-030898 Slow Processing when using the PROC INFOMAPS procedure http://support.sas.com/kb/30/898.html add the following option to the '-jreoptions' option in your SAS configuration file: -DProcInfoMaps.Verify=NO Note: The '-DProcInfoMaps.Verify=NO' is case-sensitive and should be specified exactly as documented. To fully implement the fix for SN-030897 Error with PROC INFOMAPS when the data source is an OLAP Cube and the password is not stored in the metadata http://support.sas.com/kb/30/897.html add the following option to the '-jreoptions' option in your SAS configuration file. This option is needed if the default authentication domain of your workspace servers is something other than DefaultAuth. -DProcInfoMaps.authDomain= When adding these options to the JREOPTIONS system option, remember that no part of the jreoptions string must go beyond column 72; that there must be a non-blank character in column 72; that continuations must start in column 1 of the next line; and that method must be continued for as many lines as needed. For example, if your configuration file contained a jreoptions option similar to the following prior to installing the hot fix: JREOPTIONS=(-DentityExpansionLimit=10000000 -Djava.security.policy=/usr /lpp/SAS/SAS_9.1.3SP4.ITRM/SDC.SAS900.TS1M3.ITRMW0/MVS/sas.policy -Djava .class.path=/usr/lpp/SAS/SAS_9.1.3SP4.ITRM/SDC.SAS900.TS1M3.ITRMW0/hostc m/sas.launcher.jar -Djava.system.class.loader=com.sas.app.AppClassLoader -Dsas.app.class.dir=/usr/lpp/SAS/SAS_9.1.3SP4.ITRM/SDC.SAS900.TS1M3.ITR MW0/itmscore/:/usr/lpp/SAS/SAS_9.1.3SP4.ITRM/SDC.SAS900.TS1M3.ITRMW0/avd obj/:/usr/lpp/SAS/SAS_9.1.3SP4.ITRM/SDC.SAS900.TS1M3.ITRMW0/hostcm/ -Dsa s.ext.config=/usr/lpp/SAS/SAS_9.1.3SP4.ITRM/SDC.SAS900.TS1M3.ITRMW0/MVS/ sas.java.ext.config -DPFS_TEMPLATE=/usr/lpp/SAS/SAS_9.1.3SP4.ITRM/SDC.SA S900.TS1M3.ITRMW0/hostcm/qrpfstpt.xml -Dsas.javaobj.experimental=no -Xmx 256m) Then after adding the new option due to the hot fix installation it should appear as follows: JREOPTIONS=(-DentityExpansionLimit=10000000 -Djava.security.policy=/usr /lpp/SAS/SAS_9.1.3SP4.ITRM/SDC.SAS900.TS1M3.ITRMW0/MVS/sas.policy -Djava .class.path=/usr/lpp/SAS/SAS_9.1.3SP4.ITRM/SDC.SAS900.TS1M3.ITRMW0/hostc m/sas.launcher.jar -Djava.system.class.loader=com.sas.app.AppClassLoader -Dsas.app.class.dir=/usr/lpp/SAS/SAS_9.1.3SP4.ITRM/SDC.SAS900.TS1M3.ITR MW0/itmscore/:/usr/lpp/SAS/SAS_9.1.3SP4.ITRM/SDC.SAS900.TS1M3.ITRMW0/avd obj/:/usr/lpp/SAS/SAS_9.1.3SP4.ITRM/SDC.SAS900.TS1M3.ITRMW0/hostcm/ -Dsa s.ext.config=/usr/lpp/SAS/SAS_9.1.3SP4.ITRM/SDC.SAS900.TS1M3.ITRMW0/MVS/ sas.java.ext.config -DPFS_TEMPLATE=/usr/lpp/SAS/SAS_9.1.3SP4.ITRM/SDC.SA S900.TS1M3.ITRMW0/hostcm/qrpfstpt.xml -Dsas.javaobj.experimental=no -Xmx 256m -DProcInfoMaps.Verify=NO -DProcInfoMaps.authDomain=domainvalue) Note: The directory structure root will depend on your site installation, and would reflect the SAS UNIX file system directory that you located in step 3. For more information about setting your JREOPTION, refer to the section "Configuring SAS Software for Use with the Java Platform" in the Configuration Guidefor SAS 9.1.3 Foundation for z/OS. This completes the installation of hot fix E9BC36 on z/OS (OS/390).