parms

These parameters are resolved at submission time on the workstation where the job or job stream is submitted. If there is no match between the specified parametername and the name of the parameters defined in the local database on the workstation, then a null value is returned.

Authorization

Syntax

parms {[-V | -u] | -build}

parms {-replace | -extract} filename

parms [-d][folder/]parametername

parms -c parametername value

Arguments

-V

Displays the command version and exits.

-u

Displays command usage information and exits.

-build

Creates the parameters database on the workstation if it does not exist. Rebuilds the parameters database, removing unused records and avoiding fragmentation from numerous additions and deletions, if it already exists.

-extract

Extracts all parameter definitions from the local database and stores them in the file with name filename.

Use this option if you want to export local parameter definitions to import them as global parameter definitions into the scheduling objects database using the add or the replace commands.

-replace

Add in the local database new parameter definitions stored in a file named filename or substitute the already existing ones.

Use this option if you want to import, as local parameter definitions, the global parameter definitions contained in the file named filename and extracted from the scheduling objects database using the extract command.

-d

Deletes the parameters with name [folder/]parametername from the local database on the workstation.

[folder/]parametername

Specifies the name of the parameter, optionally preceded by the folder within which it is defined, whose value is displayed. When used with the argument -d it represents the name of the parameter to be deleted.

-c name value

Specifies the name and the value of a parameter. The name can contain up to 16 alphanumeric characters, including dashes (-) and underscores (_), and must start with a letter. The value can contain up to 72 characters. Enclose the value in double quotation marks if it contains special characters. If the parameter does not exist, it is added to the database. If the parameter already exists, its value is changed.

Comments

When parms is run on the command line without arguments, it prompts for parameter names and values.

The use of parms in either job definitions and job script files requires that the parameter already exists locally in the parameters database on the workstation.

schedule test_js
on everyday
opens "/usr/home/tws_99/'/usr/home/tws_99/bin/parms MYFILE'"
:
test_job
end

The following example explains how the variable var enclosed by carets (^) is replaced while the job is in process. If the job is submitted as an ad hoc job, the parameter var is expanded, that means replaced by the value assigned to var in the local database, at submission time and not when the job launches.

DATA#UX_P_TEST DOCOMMAND "ls ^var^"
STREAMLOGON "mae82"
DESCRIPTION "Test parms in job definition on UNIX."
RECOVERY STOP

BORG#WIN_P_TEST DOCOMMAND "dir ^var^"
STREAMLOGON "mae82"
DESCRIPTION "Test parms in job definition on Windows."
RECOVERY STOP

When used in a job script file, the parameter is not expanded until the script launches. It is not expanded when the job stream containing the job is processed by JnextPlan. These are examples on how to use the var parameter in job script files.

#!/bin/sh
TWS_HOME="/opt./tws/mae82/maestro"
export TWS_HOME
MDIR='$TWS_HOME/bin/parms var'
export MDIR
ls -l $MDIR

set TWS_HOME=d:\win32app\TWS\mae82\maestro
echo %TWS_HOME%
FOR /F "Tokens=*" %%a in (%TWS_HOME%\bin\parms var) do set MDIR=%%a
echo %MDIR%
dir %MDIR%