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 data portion of the LDM's product-queue. This parameter is 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 if only the IDS|DDPLUS data-feed is being received).
For convenience, a "K", "M", or "G" suffix can be appended to the numeric specification to mean "kilo", "mega", and "giga", respectively. Thus the specifications "1G" "1000M", "1000000K", and "1000000000", are all equivalent, for example.
The value for this parameter can be fine-tuned by using the pqmon utility.

pq_slots The number of data-product slots for the LDM product-queue. This is the maximum number of data-products that the product-queue can contain (assuming that the data portion of the product-queue is sufficiently capacious). This parameter is used when the product-queue is created. The number of slots should equal the maximum number of data-products expected over the desired minimum residency-time (e.g., 16000 for one hour of IDS|DDPLUS data, if that is all that's being received). If this parameter is defaulted, then the number of slots will be computed using the size of the data portion of the product-queue and 4096 bytes as the mean data-product size (which is, undoubtably, incorrect).
The value for this parameter 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 data portion of the LDM's product-queue. This parameter is 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 if only the `IDS\|DDPLUS` data-feed is being received). For convenience, a "K", "M", or "G" suffix can be appended to the numeric specification to mean "kilo", "mega", and "giga", respectively. Thus the specifications "1G" "1000M", "1000000K", and "1000000000", are all equivalent, for example. The value for this parameter can be fine-tuned by using the pqmon utility.
pq_slots	The number of data-product slots for the LDM product-queue. This is the maximum number of data-products that the product-queue can contain (assuming that the data portion of the product-queue is sufficiently capacious). This parameter is used when the product-queue is created. The number of slots should equal the maximum number of data-products expected over the desired minimum residency-time (e.g., 16000 for one hour of `IDS\|DDPLUS` data, if that is all that's being received). If this parameter is defaulted, then the number of slots will be computed using the size of the data portion of the product-queue and 4096 bytes as the mean data-product size (which is, undoubtably, incorrect). The value for this parameter 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