Vet the `ldmadmin` Script

["To vet" is to examine and possibly modify or correct.]

The shell-script for administering the LDM should have been installed as the file ldmadmin in the directory $VERSIONDIR/bin (which should also be ../bin at this point). What follows is information on possible modifications to this script for your site.

First, ensure that the pathname of the perl 5 utility in the first line of the script is correct for your system.

Then, you will probably need to manually configure several variables in the ldmadmin script. If you have a previous installation of the LDM package, then you can use that installation's ldmadmin script to help you determine appropriate values.

Vet the following variables:

Variable Meaning

hostname The fully-qualified name of the host computer on which the LDM will execute. This name must contain periods. If the command uname -n doesn't return such a name, then set the value appropriately.

udunits The pathname of the database of the UDUNITS package. It should only be necessary to define this variable if your LDM system will decode incoming products using the gribtonc(1) utility (i.e. if an exec entry that uses gribtonc exists in a pqact configuration-file).
pq_size
The size, in bytes, of the LDM's product-queue and the maximum number of products. These parameters are used when the product-queue is created. The size should equal the desired minimum residency-time for a data-product in the product-queue (e.g., 1 hour) times the maximum rate of data arrival. (e.g., 13.4 MB/h for the IDS|DDPLUS data-feed) plus some amount for overhead (e.g., 5%). The number of products should equal the maximum number of products expected over the desired minimum residency-time (e.g., 16000 for one hour of IDS|DDPLUS data). The format of this variable is
pqSize [-S maxProdNum]
	    
where the brackets mean that the maximum data-product parameter is optional. If this parameter is omitted, then a default value will be computed using 2000 bytes as the mean data-product size.
The value for these parameters can be fine-tuned by using the pqmon utility.
numlogs The maximum number of LDM logfiles to keep around.

Variable	Meaning
hostname	The fully-qualified name of the host computer on which the LDM will execute. This name must contain periods. If the command `uname -n` doesn't return such a name, then set the value appropriately.
udunits	The pathname of the database of the UDUNITS package. It should only be necessary to define this variable if your LDM system will decode incoming products using the `gribtonc(1)` utility (i.e. if an `exec` entry that uses `gribtonc` exists in a `pqact` configuration-file).
pq_size	The size, in bytes, of the LDM's product-queue and the maximum number of products. These parameters are used when the product-queue is created. The size should equal the desired minimum residency-time for a data-product in the product-queue (e.g., 1 hour) times the maximum rate of data arrival. (e.g., 13.4 MB/h for the `IDS\|DDPLUS` data-feed) plus some amount for overhead (e.g., 5%). The number of products should equal the maximum number of products expected over the desired minimum residency-time (e.g., 16000 for one hour of `IDS\|DDPLUS` data). The format of this variable is pqSize [-S maxProdNum] where the brackets mean that the maximum data-product parameter is optional. If this parameter is omitted, then a default value will be computed using 2000 bytes as the mean data-product size. The value for these parameters can be fine-tuned by using the pqmon utility.
numlogs	The maximum number of LDM logfiles to keep around.

Workshop-specific instructions.

You can check the configuration of the ldmadmin script by executing the following command in the bin/ subdirectory of the LDM version:

$VERSIONDIR/bin/ldmadmin config

Vet the ldmadmin Script

Vet the `ldmadmin` Script