9.5 Fix Pack 1:

An incorrect run number is sent to Flexera and causes the engine functionality to stop

If you encounter the error message AWKFLX002E One or more job run numbers are missing in the job count, then an error has occurred in calculating the job run number. The updateStats script of the first FINALPOSTREPORTS could end after the switchPlan script of the FINAL job stream, thus the job run number changes before the end of the updateStats script. Flexera server finds that the run number is not the expected one and stops the engine functionality.

Workaround: to make the job run number reliable, the FINAL and FINALPOSTREPORTS should be modified as follows:

• The FINAL's FOLLOWS dependency must be changed from WKS#FINAL.SWITCHPLAN PREVIOUS to FOLLOWS WKS#FINALPOSTREPORTS.UPDATESTATS FROM 2359 - 1 DAYS TO 2358 job.
  Following an example of the complete FINAL definition:

  SCHEDULE WKS#FINAL
          DESCRIPTION "Added by composer."
          ON RUNCYCLE RC1 "FREQ=DAILY;"
          AT 2359
          CARRYFORWARD
          FOLLOWS WKS#FINALPOSTREPORTS.UPDATESTATS FROM 2359 - 1 DAYS TO 2358
          :
          WKS#STARTAPPSERVER
   
          WKS#MAKEPLAN
          FOLLOWS STARTAPPSERVER
   
          WKS#SWITCHPLAN
          FOLLOWS MAKEPLAN

• The FINALPOSTREPORTS.UPDATESTATS job must be set to have a RECOVERY STOP option instead of the RECOVERY CONTINUE one.
  Following an example of the complete UPDATESTATS definition:

  WKS#UPDATESTATS
          SCRIPTNAME "/opt/HCL/WA95/TWS/UpdateStats"
          STREAMLOGON wauser
          DESCRIPTION "Added by composer."
          TASKTYPE UNIX
          RECOVERY STOP
          FOLLOWS CHECKSYNC

Jobs are not able to run on a domain manager after a repeat rerun

If the recovery job workstation is a dynamic agent, to make jobs run on a domain manager after a repeat rerun, the dynamic agent must belong to the same domain as the parent job workstation.

SendMail action is not performed due to a missing WebSphere Application Server Liberty Base third-party library

When an event rule includes sending a user an email as the triggered action in response to the occurrence of the event, the email is not sent due to the absence of a WebSphere Application Server Liberty Base third-party library.

Workaround: to load the missing third-party library available in Liberty, you must define the API type visibility in the section of the server.xml file that is related to the TWSEngineModel.ear deployment. Set the apiTypeVisibility attribute of the classloader element to third-party as follows:

<enterpriseApplication id="TWSEngineModel" location="TWSEngineModel.ear" name="TWSEngineModel"> <classloader apiTypeVisibility="+third-party" commonLibraryRef="DBDriverLibs, libs.native" delegation="parentFirst"  privateLibraryRef="libs.sdo, libs.plugin, libs.jackson, twa-properties, libs.ccmdb, libs.emf, libs.jlog, libs.act">
</classloader>

Once the change has been performed, restart the WebSphere Application Server Liberty Base

A communication failure could occur when removing an ACL defined on a deleted folder

Removing an ACL defined on a deleted folder from the DWC, you could receive the following error message:

"AWSUI0833E The operation could not be completed. There has been a communication failure. The internal message is: AWSJDB201E The object "acl=/FOLDER1_1/+F" cannot be locked, updated, or deleted because it is locked by user "null"."

Workaround: to remove the ACL and avoid communication issues, perform the following steps:

1. Recreate the deleted folder.
2. Delete the ACL defined on the folder you just recreated.
3. Delete the folder.

A fully qualified path length of a folder cannot be longer than 254 chars

The folder path cannot be longer than 254 chars, otherwise a security file corruption occurs.

The CWWKS4001I information message is logged several times in the messages.log file

In case of Dynamic Workload Console concurrent users generating more than 15 pages/second traffic, the CWWKS4001I information message is logged several times in the WebSphere Application Server Liberty Base messages.log of the master domain manager. This behaviour makes the log file difficult to read and might cause potential performance impacts on Dynamic Workload Console response time.

This is the structure of the Fix Pack for the engine on Flexnet:

When installing the HCL Workload Automation Fix Pack, follow these recommendations:

• Before installing the Fix Pack, ensure you have installed the required prerequisite software. To obtain the latest information about software requirements for HCL Workload Automation, see https://workloadautomation.hcldoc.com/help/topic/com.hcl.wa.doc_9.5/distrDDguides.html.
• This Fix Pack supports DB2 Advanced Enterprise Server Edition, Version 10.5 on HP-UX and Sun Solaris operating systems only. It is available for download from Flexnet. After the installation of DB2 Advanced Enterprise Server Edition, Version 10.5, you must manually apply the license activation key (.lic file). The license key must be downloaded separately from the Passport Advantage web site. The part number related to the license activation key is CNED3ML. The key must be registered using the db2licm command. See Applying DB2 licenses licenses for the procedure to register the key.

  If you already have installed DB2 Advanced Workgroup Server Edition, you can switch this license with a DB2 Advanced Enterprise Server Edition license, by following the procedure in Updating licenses. Note that when the procedure references the product-identifier as in step 3:db2licm -a product-identifier, replace the product-identifier with the file representing the license activation key (.lic).

• Before installing this Fix Pack on AIX® V7.1 operating systems, you must apply the patch for APAR IZ99634. For more information, see: http://www-01.ibm.com/support/docview.wss?uid=isg1IZ99634.
• On UNIX operating systems, before installing the HCL Workload Automation Fix Pack, ensure that your umask is set to 022. To verify that umask is set to the correct value, from a command prompt, run the umask command. If the value is different from 022, modify it by running the command:

  umask 022

• On UNIX operating systems, the database administrator must have read and run privileges for the HCL Workload Automation installation path; otherwise the installation fails. (54367)

After the Fix Pack installation completes, verify the following information:

• This Fix Pack installs a new version of the file tws_env.sh (tws_env.cmd) and also creates a backup file named, tws_env.sh.bk (tws_env.cmd.bk), which are both saved to the <TWA_HOME>/TWS directory, where <TWA_HOME> is the HCL Workload Automation installation directory. After installing the Fix Pack, if you have modified the original version, merge the content of the new version with the content of the original version to carry your customized content into the new version.
• On IBM i operating systems, if you want to install the Fix Pack on the agent for z/OS and HCL Workload Automation Dynamic Agent, verify that the user profile used as TWSUser is not a member of a group profile. Set the group profile associated with the TWSUser to *NONE. If the TWSUser is a member of a group, the Fix Pack installation fails.
• Only on Windows operating systems, to correctly display double-byte character set (DBCS) characters, you must perform the following actions:
  • Set the LANG environment variable to the DBCS language code you want to use, for example, set LANG=zh_CN.
  • Set the TWS_TISDIR environment variable to the HCL Workload Automation home directory, for example, set TWS_TISDIR=C:\FTA\TWS.
  • Open the Control Panel window and click Clock, Language, and Region.
  • Click Region and Language.
  • In the Format tab, choose from the Format drop-down list the language you want to use.
  • In the Keyboards and Languages tab, under Display Language, click install and follow the steps to install the DBCS language pack you want to use.
  • In the Administrative tab, click Change system locale and, from the drop-down list, choose the language (system locale) you want to use.
  Note that all the settings must be coherent, that is they must refer to the same DBCS language setting. After you have completed these changes, reboot your workstation to have the changes take effect.
• When installing a dynamic agent or a fault-tolerant agent, ensure that the agent name does not start with a number. If the name of the dynamic agent starts with a number, use the -displayname parameter at installation time to specify a different name. If the name of the fault-tolerant agent starts with a number, use the --thiscpu parameter at installation time to specify a different name.

Before starting the Fix Pack installation, ensure that you have the necessary disk space available on the file system. Consider that the disk space check calculated by the installation considers the entire space occupied by the <TWA_HOME> directory. The space required by the backup is the sum of the following directories:

<TWA_HOME>/TWS + <TWA_HOME>/TDWB + <TWA_HOME>/wastools + <TWA_HOME>/properties

In addition to the disk space in the following table, the installation requires an additional 600 MB on the file system where the IMShared directory is located.

You can install the Fix Pack using one of the following methods:

For master domain manager or its backup:

see Updating the master domain manager and its backup

For dynamic domain manager or its backup:

see Updating the dynamic domain manager

For fault-tolerant agent, dynamic agent or domain manager:

see Updating agents

Before installing the Fix Pack using any of the methods described in the following sections, perform the following actions:

1. If you have jobs scheduled to run on the instance you are upgrading, make sure that they have completed otherwise some processes, such as jobmon or joblnch, might still be active.
2. Download the appropriate ZIP files for the operating system from HCL License Portal Flexnet.
3. Extract the content of the ZIP files into a directory, using one of the extraction tools available on your system or downloadable from the Internet. The tool you use must be able to keep the file permissions on the extracted files, for example, infozip.
   Note:

   • If you want to install the Fix Pack on IBM i, to untar the eImages, see Extract the eImages for the HCL Workload Automation for Z Agent and Dynamic Agent on IBM i operating systems.
   • To extract the .zip file onto a Windows 64-bit system, ensure that the eImage is not located on the desktop because the Windows operating system extract tool has a problem. Choose another directory into which to extract the Fix Pack eImage.