INSTALLATION INSTRUCTIONS FOR HOT FIX 82IS03 ON OS/390 BEFORE DOWNLOADING: The hot fix 82IS03 addresses the issue(s) in Release 8.2 (TS2M0) of IT Service Vision software on OS/390 as documented in SAS Note(s): SN-006767 %CPXHTML allows for default exception reports in ITSV 2.5 SN-006786 ERROR when IT Service Vision 2.5 started, but exited before selecting a PDB SN-006779 OUTTYPE=ascii does not work in CPSRCRPT without upcasing SN-006785 "Warning: Client could not be resized to fit client area..." in IT Service Vision SN-006781 %CPIDTOPN needs "SAME AND" support in WHERE clause SN-006775 ERROR: Data set DICTLIB.TREDINFO does not contain the index specified by the KEY= option, TABLRED SN-006777 DCOLLECT and other MXG-based collectors fail with SCL dump due to a %INCLUDE statement SN-006780 WELCOME.HTM file should be recreated for all report output SN-006788 Updated metrics and tables for HP Openview C.03.50 available for IT Service Vision 2.5 SN-006929 Saving exception rule using IT Service Vision MVS GUI does not retain BY list SN-007632 SAR Device Table (SARBD) not populated properly in IT Service Vision SN-004010 Cannot access Version 8 PDB via SAS/SHARE server SN-007578 Incorrect documentation for CMIMSLD member in hlq.ITSV.CPMISC SN-007631 SAP QuickStart Wizard SPROCESS job contains truncated code for SAPHST SN-007563 Restart of failed CPREDUCE results in lost data SN-007565 CPREDUCE fails to restart MONTH level of the PDB after a timeout SN-009029 CPMANRPT fails if location contains only print reports SN-008997 Creating a variable number of gallery columns in ITSV web reports SN-009012 QuickStart Wizard for SNORT data generates CPPROCES macro code for non-related tables SN-009000 Support for new SAS IT Security Management Solution SN-009030 CPRUNRPT resubmits previous report if new report definition not found SN-007801 Numeric summary variables at the reduction levels do not have their lengths verified and instead default to eight bytes SN-009005 Missing values can cause PROC FORMAT errors in the CPSPEC macro SN-007278 "ERROR: A character operand was found in the %EVAL function or %IF condition where a numeric operand is required." from ITSV SN-009028 Need to support LTCUTOFF parameter when CPRUNRPT is executed from CPXHTML SN-009032 Value of 24:00 appearing on CPPLOT X axes SN-009034 Allow customer to label statistics in CPCHART SN-009008 CPSPEC sort error when SUMMARY=ASIS and YVAL=TOTVARS SN-009046 CPSETHAX is not useful for datetime ranges SN-006759 CPCHART macro may produce incorrect results when STACK option is specified SN-009010 CPSPEC produces incorrect results with multiple analysis variables SN-008996 Drop-down lists for ITSV Web Gallery reports with single BY variable which may be reviewed at: http://www.sas.com/service/techsup/unotes/SN/006/006767.html http://www.sas.com/service/techsup/unotes/SN/006/006786.html http://www.sas.com/service/techsup/unotes/SN/006/006779.html http://www.sas.com/service/techsup/unotes/SN/006/006785.html http://www.sas.com/service/techsup/unotes/SN/006/006781.html http://www.sas.com/service/techsup/unotes/SN/006/006775.html http://www.sas.com/service/techsup/unotes/SN/006/006777.html http://www.sas.com/service/techsup/unotes/SN/006/006780.html http://www.sas.com/service/techsup/unotes/SN/006/006788.html http://www.sas.com/service/techsup/unotes/SN/006/006929.html http://www.sas.com/service/techsup/unotes/SN/007/007632.html http://www.sas.com/service/techsup/unotes/SN/004/004010.html http://www.sas.com/service/techsup/unotes/SN/007/007578.html http://www.sas.com/service/techsup/unotes/SN/007/007631.html http://www.sas.com/service/techsup/unotes/SN/007/007563.html http://www.sas.com/service/techsup/unotes/SN/007/007565.html http://www.sas.com/service/techsup/unotes/SN/009/009029.html http://www.sas.com/service/techsup/unotes/SN/008/008997.html http://www.sas.com/service/techsup/unotes/SN/009/009012.html http://www.sas.com/service/techsup/unotes/SN/009/009000.html http://www.sas.com/service/techsup/unotes/SN/009/009030.html http://www.sas.com/service/techsup/unotes/SN/007/007801.html http://www.sas.com/service/techsup/unotes/SN/009/009005.html http://www.sas.com/service/techsup/unotes/SN/007/007278.html http://www.sas.com/service/techsup/unotes/SN/009/009028.html http://www.sas.com/service/techsup/unotes/SN/009/009032.html http://www.sas.com/service/techsup/unotes/SN/009/009034.html http://www.sas.com/service/techsup/unotes/SN/009/009008.html http://www.sas.com/service/techsup/unotes/SN/009/009046.html http://www.sas.com/service/techsup/unotes/SN/006/006759.html http://www.sas.com/service/techsup/unotes/SN/009/009010.html http://www.sas.com/service/techsup/unotes/SN/008/008996.html http://www.sas.com/service/techsup/unotes/SN//.html The following file(s) will be installed: * 82is03os.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 Release 8.2 (TS2M0) installed on your system before applying this hot fix. 2. Before proceeding with STEP 5 of the INSTALLATION INSTRUCTIONS, insure no Version 8.2 SAS jobs are running because this step requires exclusive access to the SASHELP library. INSTALLATION INSTRUCTIONS: The following instructions describe the steps for extracting the contents of the downloaded file, moving the files to your OS/390 system and installing the hot fix. Please be sure to read the 'ADDITIONAL NOTES' section for situations where additional actions may be required. STEP 1: PRE-ALLOCATE THE XMIT FILE ON MVS Pre-allocate a file on MVS with the following DCB. Be sure to check the space requirement on the download page: Organization : PS Record format : FB Record length : 80 Block size : 3120 STEP 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 OS/390 files to a default location example: C:\os390\82xxxxos (where 82 is the release and xxxx is the hot fix number) 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 82xxxxos.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/v82/itsv/82xxxx/mvs (where 82 is the release and xxxx is the hot fix number) Issue the following commands where 'sas.hotfix.xmit' is the filename you created in step 1. binary get 82xxxxos.xmit 'sas.hotfix.xmit' (rep STEP 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 4: EXECUTE THE REXX EXEC In your new CNTL data set is a REXX exec that will, if applicable, create any new load libraries and, if applicable, generate any JCL required to modify SAS catalogs in your SAS system. Execute this REXX exec from ISPF prompt: ex 'sas.hotfix.cntl(rexx)' STEP 5: RUN ANY GENERATED JCL If the REXX exec generated any JCLxxxxx members in your CNTL dataset you will need to edit the JCL to make any site specific modifications and then run the JCL. Note that the output data sets in this JCL requires DISP=OLD, so you will have to run it at a time when this would be possible. STEP 6: MERGE GENERATED LIBRARIES WITH SAS If the REXX exec created: (note: HF82xxxx where 82 is the release and xxxx is the hot fix number) * '&prefix.HF82xxxx.LIBRARY' then you will need to replace the like-named modules in your current Release 8.2 (TS2M0) installation library with the modules loaded to '&prefix.HF82xxxx.LIBRARY'. We suggest you rename the modules in the current Release 8.2 (TS2M0) installation library before replacing. * '&prefix.HF82xxxx.DBCS.LIBRARY' then you will need to replace the like-named modules in your current Release 8.2 (TS2M0) installation DBCS library with the modules loaded to '&prefix.HF82xxxx.DBCS.LIBRARY'. We suggest you rename the modules in the current Release 8.2 (TS2M0) installation library before replacing. * '&prefix.HF82xxxx.SASMSG' then you will need to replace the like-named members in your current Release 8.2 (TS2M0) installation SASMSG library with the members loaded to '&prefix.HF82xxxx.SASMSG'. We suggest you rename the members in the current Release 8.2 (TS2M0) installation SASMSG library before replacing. * '&prefix.HF82xxxx.AUTOLIB' then you will need to replace the like-named members in your current Release 8.2 (TS2M0) installation AUTOLIB library with the members loaded to '&prefix.HF82xxxx.AUTOLIB'. We suggest you rename the members in the current Release 8.2 (TS2M0) installation AUTOLIB library before replacing. * '&prefix.HF82xxxx.ITSV.CPMISC' then you will need to replace the like-named members in your current Release 8.2 (TS2M0) installation CPMISC library with the members loaded to '&prefix.HF82xxxx.ITSV.CPMISC'. We suggest you rename the members in the current Release 8.2 (TS2M0) installation CPMISC library before replacing. ADDITIONAL NOTES: * If the REXX exec created a '&prefix.HF82xxxx.LIBRARY' that contains a SASHELP, 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.HF82xxxx.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 SASXAL2 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. This completes the installation of hot fix 82IS03 on OS/390.