Automatically tune values in the uvconfig file of the server engine by using a script

Technote (troubleshooting)


Problem(Abstract)

The default tunable values used for job control in IBM InfoSphere DataStage might not be sufficient in all customer environments. You can now use a script to configure particular tunable valuables in the server engine uvconfig file. The script automates the effort of changing default values to recommended values.

Cause

Customers that run many jobs simultaneously might need to increase tunable values to avoid job hangs or aborts.

The tunable values of concern are related to locks and files, for example: MFILES, T30FILES, RLTABSZ, and MAXRLOCK. Refer to the following technote for details on these parameters
(https://www-304.ibm.com/support/docview.wss?uid=swg21412963).


Environment

The script works on all InfoSphere DataStage platforms (Windows and all flavors of UNIX).

Resolving the problem

The DSEtune.tar image contains two files;

  • DSEtune.sh
  • Uvconfig_Updates
DSEtune.sh is the script for applying the new values.
Uvconfig_Updates is a text file which contains the name and new value for each tunable to change. It is read by DSEtune.sh.
The contents of Uvconfig_Updates is as follows:

MFILES 200
T30FILE 512
RLTABSZ 300
MAXRLOCK 299

Additional tunable values or revised values could be specified, if needed, in the future.

Before running DSEtune.sh script, make sure that no one is connected to InfoSphere DataStage. You can check this by typing: netstat -a |grep dsrpc

The only thing you should see is the dsrpcd daemon itself in LISTEN mode.

When there are no more connections, run the DSEtune.sh script located in DSHOME directory.

In Windows, check your environment variables and make sure MKSTool kit is in %PATH% and available in command windows.

The script performs the following operations:

  1. Shuts down the IBM InfoSphere Information Server,
  2. Takes back of current uvconfig file with uvconfig.<date during execution of script>
  3. Modifies the uvconfig file.
  4. If the current tunable value for a tunable name in uvconfig file is less than the tunable value in Uvconfig_Updates file, then the script replaces with the current value in Uvconfig_Updates file. Otherwise, the script leaves the value as it is.
  5. Runs the uvregen command.
  6. If running the uvregen command results in a shared segment error, the script: calculates the shared segments, replaces the shared segments in uvconfig file and runs the uvregen command again.
  7. Creates a file named Uvconfig_Changes. The following values are included in the file:
    • Tunable name
    • Current tunable value
    • Updated tunable Value
8. Restarts InfoSphere Information Server


Popular posts from this blog

Shrink you container size up to 95%.

alma linux: dnf Module yaml error: Unexpected key in data