Installation Instructions for Hot Fix A13003

z/OS


Hot fix A13003 addresses the issue(s) in SAS/ACCESS Interface to Oracle 9.21 on z/OS as documented
in the Issue(s) Addressed section of the hot fix download page:

	http://ftp.sas.com/techsup/download/hotfix/HF2/A13.html#A13003

IMPORTANT NOTES

You must have SAS/ACCESS Interface to Oracle 9.21 installed on your system
  before applying this hot fix.

Technical Support strongly suggests that you verify that you have
  current backups of all SAS files.

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

Before proceeding with STEP 5 of the INSTALLATION INSTRUCTIONS, insure
  no 9.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 z/OS
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 Z/OS

  Pre-allocate a file on z/OS (e.g. 'sas.hotfix.xmit') 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 Z/OS

  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 files to a default location

                   example: C:\zos\A13003os

              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 A13003os.xmit
              file to your z/OS system doing a BINARY upload into
              the preallocated file created in step 1.

    Method 2) From z/OS, FTP to ftp.sas.com using
              userid=anonymous and password=your.email@address

              Once you are logged on, cd into the following
              directory:
              /techsup/download/hotfix/HF2/A/A13/A13003/xx/mvs/en

              Issue the following commands where
              'sas.hotfix.xmit' is the filename you created in
              step 1.

              binary
              get A13003os.xmit 'sas.hotfix.xmit' (rep
              quit


STEP 3: RECEIVE THE XMIT FILE TO CREATE THE CNTL PDS

  On z/OS issue a RECEIVE command against 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 should 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.  This PDS will be
  referred to as the CNTL data set in subsequent instructions.


STEP 4: EXECUTE THE REXX EXEC

  In the CNTL data set is a member named REXX.  This member
  contains a REXX exec that will prompt you for information,
  then, if applicable, create any new load libraries and, if
  applicable, generate any JCL required to modify SAS data
  libraries or USS content in your SAS system.  Execute this REXX
  exec from an ISPF prompt and follow the dialogs:

      ex 'sas.hotfix.cntl(rexx)'

  After the exec has built the contents of the hot fix, it will
  display a dialog telling you exactly what files it created.
  Please make note of the data sets and/or members that the REXX
  exec created.  Subsequent instructions may or may not be
  applicable based on what files / members that the REXX exec
  created.


STEP 5: RUN ANY GENERATED JCL

  If this hot fix contains any updates to SAS data libraries or
  USS directories, then the REXX exec would have generated new
  members in the CNTL data set that start with 'JCL', and told
  you about them in the dialogs.  If this is the case, then you
  will need to run the jobs contained in these members.  Be sure
  to read any comments in the jobs and follow any instructions
  contained there.  Make any site specific modifications to the
  JCL and then run the job(s).  Note that the job(s) may contain
  output data sets that require DISP=OLD.  If that is the case,
  then you will need to run it at a time when this allocation
  would be possible.


STEP 6: MERGE GENERATED LIBRARIES WITH SAS

  There are several different types of files that the hot fix may
  have created.  The dialog in the REXX exec told you exactly
  what it created.  If the REXX exec created:

    * '&prefix.HFA13003.LIBRARY'
         then you will need to replace the like-named modules in
         your current SAS 9.2 (9.2 TS2M0) installation library
         with the modules loaded to '&prefix.HFA13003.LIBRARY'.
         We suggest you rename the modules in the current SAS 9.2
         (9.2 TS2M0) installation library before replacing, or
         make a backup copy of the original modules.

    * '&prefix.HFA13003.DBCS.LIBRARY'
         then you will need to replace the like-named modules in
         your current SAS 9.2 (9.2 TS2M0) installation DBCS
         library with the modules loaded to
         '&prefix.HFA13003.DBCS.LIBRARY'.  We suggest you rename
         the modules in the current SAS 9.2 (9.2 TS2M0)
         installation library before replacing, or make a backup
         copy of the original modules.

    * '&prefix.HFA13003.SASMSG'
         then you will need to replace the like-named members in
         your current SAS 9.2 (9.2 TS2M0) installation SASMSG
         library with the members loaded to
         '&prefix.HFA13003.SASMSG'.  We suggest you rename the
         members in the current SAS 9.2 (9.2 TS2M0) installation
         SASMSG library before replacing, or make a backup copy
         of the original members.

    * '&prefix.HFA13003.AUTOLIB'
         then you will need to replace the like-named members in
         your current SAS 9.2 (9.2 TS2M0) installation AUTOLIB
         library with the members loaded to
         '&prefix.HFA13003.AUTOLIB'.  We suggest you rename the
         members in the current SAS 9.2 (9.2 TS2M0) installation
         AUTOLIB library before replacing, or make a backup copy
         of the original members.

    * '&prefix.HFA13003.ITRM.CPMISC'
         then you will need to replace the like-named members in
         your current SAS 9.2 (9.2 TS2M0) installation CPMISC
         library with the members loaded to
         '&prefix.HFA13003.ITSV.CPMISC'.  We suggest you rename
         the members in the current SAS 9.2 (9.2 TS2M0)
         installation CPMISC library before replacing, or make a
         backup copy of the original members.


STEP 7: RENAME THE SASORA MODULE FOR THE APPROPRIATE ORACLE CLIENT

  If running the Oracle 10g client, rename the ORMVS10 module to SASORA.
  Sample JCL:
	CPORA COPY INDD=((DDIN,R)),OUTDD=DDOT
	  SELECT M=((ORMVS10,SASORA))

  If running the Oracle 9i client, rename the ORMVS9 module to SASORA.
  Sample JCL:
	CPORA COPY INDD=((DDIN,R)),OUTDD=DDOT
	  SELECT M=((ORMVS9,SASORA))



ADDITIONAL NOTES:

  * If the REXX exec created '&prefix.HFA13003.LIBRARY' and it
    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.HFA13003.LIBRARY' and you
    run with an entry point of SASLPA 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 and refresh LPA.

    In the configuration 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 SAS 9.2 Foundation Into The
    LPA/ELPA" in the "Configuration Guide for SAS 9.2 Foundation
    for z/OS".


This completes the installation of hot fix A13003 on z/OS.