                    SMARTdata UTILITIES (SdU) - READ.ME
                    ===================================
 
 
Welcome to SMARTdata UTILITIES
 
This READ.ME file contains information you need for installing
SdU, as well as information that was not available for our printed
publications. This READ.ME file is divided into the following cate-
gories:
 
    0) SdU fixes included in CSD 1
    1) Before You Install SdU
    2) Getting Help
    3) Installing SMARTdata UTILITIES
    4) Late-Breaking News
    5) Trademarks and Copyright Notices
 
SMARTdata UTILITIES fixes included in CSD 1.
--------------------------------------------
 
    o       Conversion table files (*.CVT files) are opened in read
            only mode. This allows SdU to be installed on a LAN
            that is defined to have only read access.
 
    o       Fix for the occurrence of an invalid record length condition
            when a DDMOpen request is issued for a sequential or direct
            file that is to be subjected to ADL translation.
 
    o       Leading backslashes for a file name were passed to the
            remote target system which resulted into an invalid file
            name condition.
 
            DFM/2 now removes all leading backslashes before sending
            the file name to the remote target system.
 
    o       Enable stream data conversion (client end).
 
    o       Fix to prevent access violation when VSAM (local processing)
             attempts to open an index file.

    o       Issue message EHN0123 only when both the ADL and DDF files 
             are missing. 

    o       Correct improper record-locking behavior.
   
    o       Enable DFM configuration file parser to process the DFM_CACHE keyword.

    o       Enable file sharing.

    o       Only change timestamp to files when they are actually updated.

 
Before You Install SMARTdata UTILITIES
----------------------------
 
   Software Requirements
   ---------------------
 
   OS/2 2.1 or OS/2 3.0 must be the base operating system
   installed on your system.
 
   OS/2 Communications Manager 1.0 or later must be installed on
   your system for remote access of files.
 
   Hardware Requirements
   ---------------------
 
   Any IBM or IBM compatible system that can run OS/2 can be
   used. The amount of disk space required for SdU depends on the
   size of the files SdU will be storing locally.  The larger
   the files, the more disk space will be required.
 
 
Getting Help
------------
 
  Help is available in the following ways:
 
  1) Through the online and softcopy versions of the SMARTdata UTILITIES
     for OS/2: VSAM in a Distributed Environment.
 
  2) In the United States, Europe and Canada, contact the Personal
      Systems Support Family Project Office at 1-800-799-7765
      or the IBM Support Family Information Center at 1-800-742-9235.
 
 
 
Installing SMARTdata UTILITIES
------------------------------
 
  Currently, SdU is not separately installable.  Follow the installation
  instructions for the product with which SdU was shipped.
 
Late Breaking News
------------------
 
  This section contains information that may be useful for initially
  configuring and using SMARTdata UTILITIES.  The following hints
  and advice supplements but is not intended to replace the product
  documentation.
 
  Topics Covered:
  o  Quick start for remote file access
  o  Problems with remote file access.
  o  Platform dependent behavior of file access.
  o  Problems with the data conversion function of remote file access.
  o  Conversion of double-byte file names during remote access.
  o  Using SdU when SdU is installed on a LAN disk.
  o  Location of sample files
  o  Settings for environment variables.

 1.  Quick start for remote file access:

      a.  Install and configure CM/2 on your OS/2 for APPC.  Define an
          LU alias for the remote host.
 
          Note:  You will need a user ID and password on that host.
      b.  Copy the file config.dfm from the samples subdirectory to
          the directory defined by the EHNDIR environmental variable
          in your config.sys file.
      c.  Edit config.dfm as follows:
          -  Activate one of the target definitions by removing the
             appropriate semicolons.
          -  Edit the remote_lu line and replace the sample value with
             the LU alias defined in CM/2 for the target you wish to ac-
             cess.
          -  Edit the line containing local_lu and replace the existing
             value with the LU alias of your local machine as defined in
             CM/2.
      d.  From an OS/2 command line, issue the command startdfm.
      e.  Enter your user ID and password on the remote system when prompted.
      f.  Assign a drive to that host with the following command:
          dfmdrive assign x: //LUALIAS
 
          Where x is a drive not currently accessed and LUALIAS is the
          LU alias of the host system.
      g.  You can now access files on the remote host both through OS/2
          commands and through VSAM applications through the drive letter
          assigned in the previous step.
 
 
  2.  Problems with remote files access.
 
      We have found that the majority of problems that people encounter
      when installing DFM involve problems configuring the communications
      between the local machine and the host.  Here are some common problems
      that people can make when setting up DFM with some solutions.
 
      a.  startdfm cannot find config.dfm.  startdfm looks for the config-
          uration file in the following places (in order): Full path name,
          if provided on the command line;  config.dfm in the current dir-
          ectory;  config.dfm in the directory defined by the EHNDIR
          environmental variable.
      b.  Problem in the configuration file.
          -  Ensure all semicolons are removed from the target definition.
          -  Ensure the remote_lu value for the target definition matches
             exactly the LU alias assigned to the target system in CM/2.
          -  Ensure your local_lu value matches the local LU alias in CM/2.
          -  Check for case mismatches between configuration file values
             and CM/2 values.
      c.  Ensure you entered the correct user ID and password at the
          prompt.
      d.  Communication Manager setup problems.  The most common cause of
          problems tends to be errors in the CM/2 setup that prevent DFM/2
          from initializing an APPC conversation with the host.  The APING
          utility available with the APPC Productivity Suite allows you to
          verify that you are able to make an LU 6.2 connection to the
          target system.
      e.  The DFM target is not available on the host system.  For MVS, the
          target DFM is part of the DFSMS/MVS 1.2.0 product.  It is a start-
          able procedure.  Ask your MVS administrator whether DFM/MVS is
          started.  Also, have your administrator ensure that the SNA mode
          of QPCSUPP is defined on the MVS system.
 
 
  3.  Platform specific behavior when accessing remote files: 

      It is important to remember that when accessing files on a remote system,		
      you are constrained by the limitations of the remote file access method.
 
      To better understand the limitations of the remote access methods,
      refer to the following documents:
 
      SC26-4915  - Distributed FileManager/MVS Guide and Reference
      SC41-9600  - AS/400 Distributed Data Management Guide
 
      A list of known restrictions:
 
      MVS Target:
      ___________
 
      o  The MVS file access method associated with the remote file will
         limit the type of access you may use.  For instance,  if the
         remote file is a PDSE member, then you can only access it sequen-
         tially.  The same holds for SAM and VSAM ESDS files.  You can only
         use keyed access if the remote file is a VSAM KSDS.
 
 
      AS/400 Target:
      ______________
 
      o  Specifying a SECURITY value other than the default PROGRAM may
         cause file space allocation problems.
      o  File names appear to be limited to 10 characters including
         periods.
      o  File names must be specified in upper case.
      o  AS/400 allocate direct files with 3 extents with 1000 records
         per extent.  All records are defined with unused records
         designated as inactive.  This may cause problems if you access
         the file the return inactive flag (DDM_RTNINA).
      o  AS/400 requires upper case for user ID and password.
 
 
  4.  Problems with the data conversion function of remote file access:

      When accessing remote files, it is possible to have DFM convert the
      records between their native format on the target system and a local
      format used on the workstation.  For instance, DFM can convert EBCDIC
      into ASCII or binary encoded decimal into byte reversed binary.  Refer
      to the product documentation for the details of how to take advantage
      of this function.  The following are some common problems that users
      may encounter:
 
      a.  Data conversion does not occur.  Note that the data conversion
          function only applies when files are accessed through the VSAM
          interface.  This means when files are viewed or edited from the
          command line, they will not be converted;  however, if they are
          opened and accessed by an application that invokes the VSAM APIs
          either directly or through a high level language like COBOL or
          PL/I, then the conversion should occur. In this case, data
          conversion should occur if the file that is to be subjected to
          data conversion is defined by the configuration file's
          FILE_DESCRIPTOR_MAP entry and all the required ADL support
          files have been created.
 
          A case mismatch between the file name specified in the FILE_
          DESCRIPTOR_MAP statement of the DFM configuration file and the
          file name specified when accessing the file will also prevent
          conversion.  While specifying the file name user1.ddm.file1 may
          open the correct file on MVS, it will not match against
          USER1.DDM.FILE1 in the FILE_DESCRIPTOR_MAP.
 
      b.  Data conversion does not work when the dfmdrive GUI is used to
          assign a drive.  When using the directory mapping function of
          the dfmdrive GUI, the value entered for the directory is pre-
          pended to the file name with a slash separating the directory
          name from the file name.  The MVS target then removes the slash
          and replaces it with a dot before accessing the file.  If the
          TARGET_FILENAME in the FILE_DESCRIPTOR_MAP entry contains a
          dot instead of a slash, then the comparison will fail.
 
  5.  Conversion of double-byte file names during remote access:
 
      When accessing a remote file, SdU converts the file name from the
      local character set (as defined by the CODEPAGE environmental vari-
      able in config.sys) into codepage 0500 used by DFM target systems.
      The current release of SdU is capable only of converting between
      single byte character sets. If you are running the Kanji or Simp-
      lified Chinese version of SdU (CODEPAGE of 0932, 1381 respectively),
      use only single byte characters when specifying remote file names.
 
  6.  Using SdU when SdU is installed on a LAN disk:

      If one wishes to use the remote file access portion of SdU when SdU
      is installed on a LAN disk then the following step must be taken:
 
      Change directory to the subdirectory of the LAN disk where SdU is
         installed.
      Change directory into the dll subdirectory.
      Copy the file dfmsfl0.dll to a local disk.
      Locate the line of your config.sys file that references the file
        dfmsfl0.  Change the full path name to point to its location on your
        current disk.
 
  7.  Location of sample SdU files:

      Sample SdU code can be found in the subdirectory:		
      x:\product\samples\sdu; x: is the drive and \product is the directory
      where the SdU products were installed.
 
  8.  Settings for environment variables:

      The environment variable FMTCDRA should be set to the name of
      the directory that contains the CDRA translation tables. To set
      this variable, issue the following command.
 
      FMTCDRA={Root_directory}\BIN\CONVTABL
 
      For example, FMTCDRA=K:\IBMDDM\BIN\CONVTABL where
      K:\IBMDDM represents the root directory.
 

 
Trademarks and Copyright Notices
--------------------------------
 
Licensed Materials - Property of IBM
5648-02011 A11(VSAM), 5648-02012 A11 (DFM), 5622-75101 (DD&C)
(C) Copyright IBM Corp. 1995
All Rights Reserved.
US Government Users Restricted Rights - Use, duplication or
disclosure restricted by GSA ADP Schedule Contract with
IBM Corp.
