Date:    January 31, 2000

Patch:   3.6.1-COU-0019

Component: Tivoli Software Distribution

General Description:

    This patch fixes APARs IX89729, IY04261, and IY05514, and
    supersedes patches 3.6.1-COU-0002, 3.6.1-COU-0004, 
    3.6.1-COU-0006, 3.6.1-COU-0008, 3.6.1-COU-0012, and
    3.6.1-COU-0014.

Problems Fixed:

    APAR  IY04261
    Symptom:  When doing a Filepackage Preview through the GUI or
      through wdistfp -p, if there are files with MBCS names,
      those filenames
      appear garbled in the output.  This is also true of the
      destination directories.
    Additional Info:  Until APAR IX89511 is fixed, when editing
      Platform Specific Options for the second time, all
      Japanese characters will be garbage.  If the filepackage
      is saved after this happens distributions will fail.

    APAR  IY05514
    Symptom:   Available Subscribers list is displayed in the
      Distribute File Package window.  If the list is Profile
      manager, a "+" sign is added, and it can be expanded by
      double-clicking to display a
      list of nested subscribers.  However, if you first single
      click a Profile manager, wait a second or two, and attempt
      a double-click, the list does not expand.
      This is also evident when the list is already unfolded with
      a "-" sign and you try to unexpanded it.
    Additional Info:  none

    APAR  IX89729
    Symptom:
        Following the creation of a file package, clicking on buttons 
        to specify file package properties, causes a general 
        oserv failure.   The user is able to use the source
        host button.  After the failure, if the file package is
        reopened, the user may use the button that previously caused
        the oserv failure, without getting the failure.

    Additional Information:
        This problem exhibited itself following the installation of 
        NT service pack 4


Problems Fixed in superseded patch 3.6.1-COU-0014:

    Defect  IY01878
    Symptom:
      When the field immediately below the "Directories & Files..."
      pushbutton on the "File Package Properties" dialog is used to
      add entries to the filelist, they may or may not be
      automatically quoted as can be seen in the listbox.  Problems
      with this automatic quoting combined with constraints placed on
      what can be entered make it difficult to add wildcards to
      filepack lists.
    Additional Info:
      The automatic quoting quotes wildcards that should not be quoted
      when the wildcard appears as the first character as can happen
      when the "src_relpath" filepack keyword is used.  For example:
      "*.exe" which causes the distribution to fail because the '*' is
      interpreted literally.

   Defect IY02515
   Symptom:	 
     Autopack Distribution GUI takes too long to come up for large
     numbers of targets.
   Additional Info: 
     For the 3.6 release, a change was made to alphabetize the list of
     displayed targets for an autopack distribution and to check that
     only machine types which are valid targets for autopacks can be
     selected from the Autopack Distribution window.  These changes cause
     GUI response to be very slow for large numbers of targets.  This
     defect reverts to the previous behavior.  Now, target lists will not
     be alphabetized, and machine types such as Unix which are generally
     not valid targets for Autopack distributions can be selected as
     valid targets.

    Defect  IY03389
    Symptom:
      A 3.6.1 SWD scheduled AutoPack distribution which fails is
      reported as successful in the log file/notice groups/email. 
      Because the distribution is reported as successful, it is not
      retried if the retry option is specified.
    Additional Info:
      None

    Defect IY03463
    Symptom:
      Using the GUI to schedule a SWD file package distribution of a
      profile with a name longer than 42 characters results in the
      following error message:
        "A failure was detected by the oserv daemon: general failure" 
    Additional Info:
      None

    Defect  IY03604
    Symptom:
      1) Random ADR decode failures or general failures during
         Autopack distribution or removal. 
      2) Distribution of a successful Autopack with no or invalid
         mail address for notification (or with wmailhost unset) will
         always receive a distribution error message. 
    Additional Info:
      None

    Defect  IY03671
    Symptom:
      When multiple small fpblocks are distributed and the Historical
      Database is enabled, the wdistfpblock method hangs.  Similar
      hangs have also been observed when distributing autopacks and
      filepacks when the Historical Database is enabled.
    Additional Info:
      The connections to RIM were not correctly released.  If a new
      SWD method call was executed before these connections timed out,
      it would cause the SWD method to hang.

Problems Fixed in superseded patch 3.6.1-COU-0012:

    Defect IX89572
    Symptom:
      While distributing an autopack, if a second distribution of the 
      same autopack is attempted the second distribution fails with 
      the following popup message:
      "An unexpected error occurred when accessing the TME database:
      Lock/Data consistency error"
    Additional Information:
      This change causes the size of the autopack .pak file to be
      calculated and stored in the Tivoli database at the time the
      autopack profile properties are set.  This size is used to 
      allow Userlink to correctly display a progress bar.  If the 
      .pak file is replaced on the filesystem with one of a different 
      size (still the same name, so there is no need to change the 
      autopack profile property), the user should use the "Calculate 
      Size" menu item (right click on the Autopack Profile) to 
      recalculate the size so that it will be correct for Userlink.

    Defect IX76774
    Symptom:
      This problem occurs when copying an Autopack .pak file from a PC
      managed node to a Unix managed node using the "Set Autopack
      Properties" window.  If the destination path specified is a 
      directory and not a complete path to a file, the permissions
      on the specified directory may be corrupted.
    Additional Information:
      This defect has already been delivered in 3.6.1-COU-0004 but
      only for Aix platforms. Now it is available also for other
      UNIX systems.

    Defect IY00380
    Symptom:
      After an AutoPack is renamed via the GUI, the wchkdb -u command returns
      the error "The cached data for member object "<OLD_NAME>"
      (1894616056.1.8242 AutoPack::View ) is inconsistent."  After 
      receiving this error, the Profile Manager which contains the
      AutoPack incorrectly shows the old AutoPack name.
    Additional Information:
      None.

    Defect IX75347
    Symptom:
      When previewing a distribution with the "Distribute entries with
      ANY changes" selected, and the source files do not exist, an
      ambiguous error message is generated.
    Additional Information:
      This fix applies to both "Distribute all entries" and "Distribute
      entries with changed source files".  Now, when any of the source
      files do not exist, a meaningful error message is displayed.
      This message will list all the files not found.  This fix requires
      3.6.1-TMF-0046 or superseding to be complete.

    Defect IY01696
    Symptom:
      An attempt to distribute an autopack via the gui to a Netware
      Managed Site results in the following pop-up error message:
      "The destination host (nwms) that you attempted to distribute
      this autopack to is not a valid autopack destination host."
    Additional Information:
      None.

    Defect IY02015
    Symptom:
      When invoking the wchkpol command for the policy region in 
      which an autopack resides, the policy validation methods for 
      autopacks are not executed.
    Additional Information:
      None.

    Defect IY02016
    Symptom:
      When invoking the wchkpol command for the policy region in 
      which a filepackage resides, the policy validation methods 
      for filepackages are not executed.
    Additional Information:
      None.

    Defect IY01517
    Symptom:
      Software Distribution does not generate a notice or send an
      e-mail when a filepack block is distributed using the
      "wdistfpblock" command regardless of the keyword settings for
      "mail_id" and "post_notice".  This is in contrast to how Software
      Distribution works when a filepack is distributed.
    Additional Information:
      This fix will address this problem in the same way it was
      addressed for AutoPack against defect IX69100 in this patch.
      Consequently this fix depends on 3.6.1-TMF-0012 or superseding.

    Defect IY02985
    Symptom:
      Software Distribution generates various temporary files with a 
      prefix of "fpop" in the temporary directory that it then fails 
      to remove.  Because the temporary files are not removed the 
      temporary directory may fill and cause any functionality, such 
      as distributing large filepacks, that depends on creating 
      temporary files to fail.  
    Additional Information:
      The temporary files in question have a prefix of "fpop" and are
      created in the following three scenarios:
      1) A preview with any changes.  Ex:
         wdistfp -np @FilePackage:test_fp @Endpoint:test_ep
      2) The distribution of a filepack block.  Ex:
         wdistfpblock /tmp/test.fp @Endpoint:test_ep
      3) The setting of the path of an AutoPack.  Ex:
         o Change the "Path" field that can be found in the "Set 
           AutoPack Properties" dialog which can be seen by right
           clicking on the "Properties..." menu item available on 
           AutoPack icons.
         o Click "Save & Close"

      This fix only addresses the normal case where the "fp_operation"
      method indirectly invoked by each of the above completes
      successfully.  This fix does not address the exceptional case
      where the "fp_operation" method fails with an exception.  An
      example of such an exceptional case can be seen by entering an
      invalid path in scenario 3) given above.

      This fix only addresses the accumulation of temporary files with
      a prefix of "fpop".  Other temporary files and other "any 
      changes" distribution failures are not addressed by this fix.

   Defect 74558(Internal defect)
   Symptom:
     Courier 3.6.1 AutoPack Profile does not recognize DEC NT
     (w32-axp) as a valid subscriber. In "Distribute AutoPack" dialog
     box, DEC NT endpoints do not get listed in the "Available
     subscribers" list
   Additional Information:
     None.

    Defect IX69100
    Symptom: 
      Distribution of an autopack does not send to the Software 
      Distribution Notice Group or E-mail as it should.
    Additional Information:  
      Patch 3.6.1-TMF-0037 or superseding must be installed on your source host and 
      ManagedNode in order for this change to take effect.

Problems Fixed in superseded patch 3.6.1-COU-0008:

    Defect IX78023
    Symptom:  
      When distributing a FilePackage, setting the Log Info Option 
      "Send E-Mail to", the message is sent to the host selected but
      is not correctly displayed.
      This problem can be verified only for NT platform.
    Additional Information:  
      This problem is present in the FilePackage and Autopack 
      profile. Patch 3.6.1-TMF-0037 must be installed on your source 
      host and Managednode in order for this change to take effect for
      an Autopack Profile.

    Defect IX89105
    Symptom: 
      When creating a filepack, the fp_val_src_host method is not 
      called.
    Additional Information: 
      Equivalent behavior exists with autopacks and is addressed 
      through this defect as well.

    Defect IX87427 
    Symptom: 
      An administrator cannot source an autopack file from a managed 
      node in a region where s/he does not have Senior privilege.
    Additional Information: 
      With this change, autopack profiles have the same behavior as
      filepack profiles. Sourcing of autopack files is now by default
      wide open to any machine in any policy region.  In a given 
      policy region, the ap_val_autopack_host_file policy method can 
      be used to limit the access of administrators who do not have 
      senior privilege in that region.
    
    Defect IX86878
    Symptom: 
      When the UserLink try to install an AutoPack profile stored as
      c:\temp\autopack\xxxx.pak, it gets an error.
      The error is :
      An error occurred while attempting to perform the software
      Distribution operation.
    Additional Information: 
      None.

    Defect IX88991
    Symptom:
      The title of this defect is misleading.  Not selecting the 
      source host does not cause the error reported on the defect.  
      Occasionally, when adding to the file list on the File Package 
      properties gui, a general oserv failure occurs.  This 
      completely kills the gui and all changes are lost.  The file 
      path that causes the error must contain a wildcard character -
      e.g. "/tmp/test_fp/dir1/*.so.a".
    Additional Information:
      None.

    CMVC 69154
    Symptom: 
      When trying to preview what is going to be distributed to
      a Tier2 Managed Node or Endpoint, the preview fails with
      the error "could not determine interp "
    Additional Information: 
      None.


Problems Fixed in superseded patch 3.6.1-COU-0006:

    Defect IX83054
    Symptom: 
      WDISTFPBLOCK does note properly form events to TEC console if 
      fpblock includes a special character.
    Additional Information:
      None.

    Defect IX88464
    Symptom:  
      When customer fill out the Product Name field on the "Optional 
      Information" dialog box a general SQL error is displayed.
    Additional Information:  
      None.

    Defect 66513
    Symptom:  
      Support override of logging options in wdistfp.
    Additional Information:  
      This defect has been used to complete the defect 54259.
      For a correct behaviour the TMP level 3.6.1-TMF-0037 must  
      be installed (when it will be available).
               
   Defect 67042
   Symptom:   
     The option -f is now supported for commands : wdistfp wrmfp 
     wdistfpblock wrmfpblock.  -f could be used to specified an input
     file with the list of targets.               
   Additional Information:  
     This defect has been used to port the enhancement 53272 
     (implemented in COURIER 3.1)
              

Problems Fixed in superseded patch 3.6.1-COU-0004:

    Defect 64069
    Symptom: 
      UserLink incorrectly traverses child PMs of EP's PMs.
    Additional Information:
      None.

    Defect IX76774
    Symptom: 
      Getting a file using AutoPack from a PC ManagedNode, if the 
      destination file name is not specified, destination dir 
      properties are changed. 
    Additional Information:    
      Currently this fix is only available for AIX (aix4-r1).  This 
      fix may be available on other platforms in future patches.  
      Defect 67092 is being used to track the porting of this fix to 
      other platforms.

    Defect IX74941
    Symptom: 
      When the fp_def_nestedlist method fails, the error messages 
      which is displayed should read: "The `fp_def_nestedlist' policy
      default method failed."
    Additional Information:
      None.

    Defect IX79770
    Symptom: 
      If a policy region has it's default policy methods for the
      FilePackage or Autopack class of objects set to "NONE" creation
      of profiles for these types of objects fails.
    Additional Information:
      None.

    Defect IX86669
    Symptom: 
      When a distribute with any changes to an OS/2 endpoint is 
      attempted in preview mode the distribution fails with an 
      "Unknown interp error".
    Additional Information:
      None.

    Defect IX87023
    Symptom: 
      In Set AutoPack Properties, in the Copy From: field, if the
      hostname is invalid for a PC Managed Node or Managed Node, and 
      you click on 'Save & Close', the error message erroneously 
      refers to resource 'endpoint'.
    Additional Information:
      None.

    Defect IX88126
    Symptom: 
      When doing a software distribution with Historical Database
      enabled, an error shows up in a RIM trace.
    Additional Information:
      None.

    Defect IX88962
    Symptom: 
      An attempt to distribute an Autopack to a profile which 
      contains one or more offline PC managed nodes results in a 
      popup saying that nodes are down.
    Additional Information:
      None.


Problems Fixed in superseded patch 3.6.1-COU-0002:

    Defect IX85076
    Symptom: 
      Specifying a directory instead of a file for the destination 
      of an Autopack causes the permissions to be set on the 
      directory.
    Additional Information:
      None.

Architecture(s): SunOS, Solaris, AIX 4.1, HP-UX 10.0, Windows NT 3.5.1 and 4.0

Patches superseded by this patch: 

   3.6.1-COU-0002
   3.6.1-COU-0004
   3.6.1-COU-0006
   3.6.1-COU-0008
   3.6.1-COU-0012
   3.6.1-COU-0014 
 
Dependencies:  None

Database Changes and other Special Considerations:  None

Files Replaced or Added by this Patch:

   TME/COURIER/FPDO/cour_cbs
   TME/COURIER/FPO/fpo_driver

Patch Contents:

   - This README file
   - Verification Status Report
   - A cdrom image for this patch

Applying the Patch:

    1)  Extract the patch:

        On a Unix system:
        
        Extract the contents into a scratch directory. For 
        the purpose of this release note, assume that the 
        symbol $PATCH points to this directory.

        # cd $PATCH
        # tar xvf 3.6.1-COU-0019.tar

        On a Windows NT system:

        Extract the contents into a scratch directory. 
        For the purpose of this release note, assume 
        that the symbol %PATCH% points to this directory.

        > %SystemRoot%\system32\drivers\etc\Tivoli\setup_env
        > X:              
          ^-- 'X' is drive letter where %PATCH% is found
        > cd %PATCH%
        > tar xvf 3.6.1-COU-0019.tar

        NOTE: If you are extracting the tar image on a 
        Windows NT system, you will find an executable
        for tar in the TME installation on Windows NT under
        bin/w32-ix86/tools/tar.exe.


    2)  If this patch is to be installed on a release level 
        of 3.6 or greater, follow these instructions for 
        using Software Installation Service (SIS). 
        If not, skip to step 3 below.

        NOTE: SIS can install Tivoli products on any hardware
              platform supported by Tivoli, but there are some
              hardware platforms on which SIS cannot be run.
              Please check your SIS User's Manual for the list
              of platforms on which SIS can be run.

        NOTE: You must have the install_product and super 
              authorization roles to successfully install this patch.

        a)  From the Tivoli Desktop, pull down 
            Desktop --> Install --> Software Installation Service.
        b)  SIS will initialize, and bring up the Get Installation
            Password Dialog.  Enter your Installation Password.
        c)  Click the Install Button on the dialog which contains
            the Tivoli image.
        d)  Click the Select Product Button on the Install 
            Spreadsheet Dialog.
        e)  Click the Import Product Button on the Select Product
            Dialog.
        f)  Locate the media to 3.6.1-COU-0019 using the file 
            browser,and select the PATCHES.LST file by 
            double-clicking it.
        g)  Select 3.6.1-COU-0019 in the Import Product Dialog, and 
            click the Import Button.
        h)  When the import is complete, click the OK Button on the
            Global Progress Dialog.
        i)  Select 3.6.1-COU-0019 in the Select Product Dialog, if it
            is not already selected, and click the OK Button.
        j)  Now click the Select Machine Button on the Install
            Spreadsheet Dialog.
        k)  Select the machine(s) you would like to install 
            3.6.1-COU-0019 to, and click the OK Button.
        l)  Click the appropriate cell(s) in the Install
            Spreadsheet Dialog. (NOTE: This should yield 
            an "X" in the cell(s)for the machines you want 
            to install 3.6.1-COU-0019 to).
        m)  Click the Install Button.
        n)  Select the install algorithm you want to use on the
            Installation Algorithm Dialog, and click OK.
        o)  SIS will perform the installation(s) you designated
            in the Install Spreadsheet Dialog.
        p)  Installation is complete. Check the Additional 
            Installation Instructions section below.


    3)  Use the following steps to install the patch using the old
        Tivoli install mechanism.  NOTE: You must have the
        install_product and super authorization roles to
        successfully install this patch.

        a) Select the "Install -> Install Patch..." option from the
           "Desktop" menu to display the "Install Patch" dialog.

        b) Press the "Select Media..." button to display the "File
           Browser" dialog.

        c) Enter the path to the directory containing the patch,
           $PATCH, in the "Path Name:" field.

        d) Press the "Set Media & Close" button to return to the
           "Install Patch" dialog.

        e) The patch install list now contains the name of the patch.
           Select the patch by clicking on it.

        f) Select the clients to install this patch on. This patch
           changes two binaries and needs to be installed on the TME
           server and on each client.

        g) Press the "Install" button to install the patch.

Additional Installation Instructions:  None

Known Defects:  None
