Glossary

$BLDDIR: The directory below $TOPDIR that contains all LeasePak builds. If the site needs to keep ore than the active build on the application host, then extraneous builds can be moved to other disks. In order for a build to remain "on line", it must be present in $BLDDIR, at least via a symbolic link. See Directory Trees.
$CFGDIR: The directory named $TOPDIR/etc, where several important files are stored, including the answers to the SETUP interview (relscfg.msirc) and the start-up files produced from them (HOST_v99x_rt.*), terminators.txt, etc. See Directory Trees.
$CSTDIR: The directory used to store EUCOs, typically located within the $NSTDIR. There should be only one $CSTDIR per site. The code within $CSTDIR is organized by build ID, thus $CSTDIR can store the EUCOs for many releases. See Directory Trees.
$datasets: The directory named $TOPDIR/datasets that is the default destination and source for user-produced datasets. See About Datasets and Directory Trees.
$DBMS_INSTANCES_LIST: For the LeasePak init script, nst_dbora, this variable contains the file name /etc/netsol_dbms_instances. The file contains an assignment to ORA_INSTANCES, which is a list of Oracle instances that are to be managed by nst_dbora.
$EFSDIR: This environment variable references the External File System DIRectory, which is the parent directory of $NSTDIR, the installation location of LeasePak releases. It is thus "external" to LeasePak. See Directory Trees.
$ENVDIR: This represents the current environment directory. That is, this is the directory containing the LeasePak environment that the current session points to. This is where the user of an environment, whether via the client, via a shell login, or via a batch job, goes to obtain the locaiton of all the parts of LeasePak, relative to that release and environment.
$ENVDIR/data: This is the path of the environment's $udata directory.
$HOME: The environment variable $HOME is the standard way of referring to the Unix or Linux directory where each OS user's home, or default, directory is located.
$INITDIR: System directory where the OS stores initialization scripts and lists. On Linux, it is at /etc/init.d on Solaris and Linux, /etc/sbin on HP-UX. Typically the DBMS nst_dbora and nst_dbsyb start-up files, and the nst_qm_{ID}99x Queue Manager start-up files are located here.
$INST_ID: The installation ID of the LeasePak instance. The System Administrator sets this variable during SETUP at the prompt: 'Short identifier for this instance (2 to 4 characters) [**]'. Often referreed to as simply the ID. Used in naming a variety of things, such as queue manager instances, and other locations where it may be necessary to distinguish among instances of LeasePak on the same server.
$LEASEPAKD_LOCKOUT: A variable, set by the SETUP program, in response to the interview question Max bad logins before lockout (0=disabled) [0]. This represents the tolerance given by leasepakd for consecutive failed login attempts for any given user account.
$live: A symbolic link that is always tied to the current, official, supported, approved build of LeasePak. Like all builds, the 'live' build is always stored in the build directory (also known by the variable "$BLDDIR"). All production type LLDBs point to the 'live' build. As a parameter to a utility command such as setup_new_env that requires a build ID, the name is used unadorned 'live' without the '$'. This is the build used in the daily work of the leasing enterprise operation. See Directory Trees.
$NSTADMIN: Also known as the LeasePak Administrator. The LeasePak server role/user, referred to by the environment variable $NSTADMIN. Owns most files within the LeasePak release structure. It is the only LeasePak role that can execute certain commands: cfg_gen, change_env, configure_rels, db_setup_job, eop_suite II, linkpoint, set_access, setup_new_env, setup_rels_dirs, and upgrade_env. It owns the whole Queue Manager installation and is the only LeasePak role that can start and stop the queues. See roles for more information.
$NSTDBA: Also known as the LeasePak Database Administrator. The LeasePak server role/user, referred to by the environment variable $NSTDBA. Owns and runs all LeasePak database utility scripts ($ubin/db_*). See roles for more information.
$NSTDIR: $NSTDIR is the environment variable referring to the default location on the application host where LeasePak releases are installed. It is the immediate subdirectory of $EFSDIR. In some circumstances, LeasePak components may be installed in $EFSDIR as well. See Directory Trees for more information.
$NSTGROUP: An environment variable that refers to the single, default LeasePak login group. This group is determined by the administrator prior to the installation of LeasePak, and must be reserved for the use of LeasePak and its related software. The administrator must insure that this group exists in /etc/group before LeasePak is installed. All OS users who are to use LeasePak must have the GID of this group as the user's default login group listed in /etc/passwd. Because it is the default login group for these users, it should not list the users in the /etc/group file.
$ORADIR: Environment variable containing the path of the installation directory of the Oracle DBMS.
$QMDIR: The Queue Manager directory. Typically located within the $NSTDIR and heads the local instance of the Queue Manager. See Directory Trees.; The full path of the start_queues.com command file.
$QMDIR/library: The configuration directory for an instance of the Queue Manager.
$QMJOB_LIM_FILE: A file used in the Queue Manager to store the queue manager job limit, input by the administrator during SETUP. See discussion at About Job Limits. the value is stored in the form of an assignment to the variable QLIM.
$QMDIR/library/Config: The full path of the Queue Manager's central configuration file.
$QMSPOOLDIR: Directory used by the Queue Manager to contain the files and devices required by the Queue Manager, including queues, temporary job files, and print jobs.
$QMTMPDIR: Directory used by hte Queue Manager to contain temporary work files, logicals tables, mailboxes, and queue error logs.
$SRVADM: Th environment variable that refers to the LeasePak Database Server Administrator. This is a database system user only, and does not have an OS account. It is a role that is delegated certain privileges normally exercised by the database system root user (SYSDBA or sa). These privileges involve adding new users to the DBMS and allocating disk resources to LLDBs.
$SYBBKSRV: The environment variable that store the name of the Sybase Backup-Server.
$SYB_AUTODBO: An environment variable that governs how Sybase-based LLDBs are owned. This is a parameter input by the administrator during the SETUP interview, where the Sybase DBMS is installed. See DBO for more information.
$SYBDIR: The environment variable that contains the name of the Sybae installation directory.
$SYBSRV
: The environment variable that stores the name of the Sybase dataserver.
$SYSINSTALLFLAGS: The envirinment variable that stores a summary of the package installation instructions derived from the SETUP interview provess. The summary is in the form of a string of Ys and Ns, representing:

flag position Service to be installed

1 Queue Manager init service

2 Not used

3 Oracle init service

4 Sybae init service

5 leasepakd internet service

6 mpowerd internet service
$TERM: Also $term. An environment variable in Unix and Linux that contains the type of interactive input/output device that the unix user is using. See terminal type.
$TOPDIR: The head directory of a LeasePak release, typically '/opt/nst/v77a'.
$ubin: Directory containing NetSol-provided LeasePak server utility software, excluding drivers and conversion software.
$udata: Data directory, a directory within each LeasePak environment directory, used to store non-relational data, though it still functions as an intrinsic part of the , and must be backed up along with the relational database part of the LLDB.
$udsets: A directory in every build that is the location of the level7 and seed datasets. Each build gets a copy of these datasets, so they are available to the $NSTDBA. Every build produced contains updated seed and level7 datasets that are compatible with the schema the build contains, and incorporate all changes to the LeasePak schema, or data layout, from previous builds, in that release.
$ueop: The variable that stores the path of the environment End of Period directory. It can also be exressed as $ENVDIR/eop.
$uecop/com: The path of the directory used to store the command files that implement a particular day's worth of End of Period processing.
$lpdlogin-lck: This is a semaphore file to tell leasepakd to not allow the user to connect and directly access the LLDB environment, because of failed log-in attempts. See $LEASEPAKD_LOCKOUT.
/etc/sservices: The central location on a network-capable server where the services that the system may provide are stored, allowing servers and clients to discover the details of teh service via the associated inetd.conf file (HP-UX and SunOS) or xinetd.d file.
/var/lock/subsys/: On Linux servers, this directory is used by init and services started by init. If a service has a file in /var/lock/subsys/, then this indicates to init that the service is running, so that init will not start a duplicate instance of the service; if there is no file for the service in /var/lock/subsys/, then init will start the service. The starting and stopping of services is determined by the system's runlevel; certain services are required in certain runlevels, and others are not allowed. When init transitions the system runlevel, it must end services that are running in the original runlevel and are not required in the new; likewise it must start services that are required in the new level that weren't running in the original.
[U0706] Security: The client Security Update.
absolute pathname: See pathname. An absolute pathname is a pthname that begins with the "/" path component delimiter. This indicates that the route through the filesystem to the indicated file will start at the filesystem root. See also relative pathname
access modes: These are the mode bits that determine which users can access a given file and in what ways. They are bits in a binary word that is stored as part of each file's descriptive data on the filesystem. Usually they are referred to in groups of 3, "r", "w", and "x". If a file is read-only to certain users then the mode bits for that user are "r--". A file that may be read and written is indicated by "rw-", and one that can be read and executed by "r-x". Each of these triads can be represented by a single octal (base 8) digit, 0-7. Thus, "r--" is octal 4, and "rw-" is octal 6 and "r-x" is octal 5. For each file there are 3 triads, one pertaining to the owner of the file, one pertaining to the members of the file's group, and one pertaining to all other users. So access modes of 640 (or rw-r-----) mean that the file may be read and written by its owner, and can only be read by members of the file's group, and that any other user has no access to the file.
administrative environment: Special LeasePak environment that is able to interact with the DBMS but does not tie to a specific LeasePak database (LLDB). There is an admin environment for each installed DBMS: adm_ora or adm_syb. Used to perform LeasePak server administrative tasks. Required environment for $NSTADMIN and $NSTDBA.
administrative user: An administrative user is a user/role within LeasePak that is delegated certain system-level functions within LeasePak. The administrative users are $NSTADMIN, $NSTDBA, $SRVADM, and DBO. $NSTGROUP is usually included, though it is not strictly a user. See non-administrative users and also administrative users.
administrator: This term is inherently ambiguous, since it can apply to system administrators, database administrators, several different LeasePak roles, and likely others as well. When used in the phrase "the administrator" within the SAG, it means "the system administrator" (see).
alphanumeric character: A character within the ASCII character set that falls in the range of alphabetic characters, 'A-Z', 'a-z', and usually '_', or that falls in the range of digit characters, '0-9'. Thus, 'cat' contains 3 alphanumeric characters, and '15999' contains 5 of them, but '$1.19' contains only 3, the other two being punctuation symbols.
API: See Application Program Interface.
application code: The programming instructions that make up an application program.
application host: Host containing the LeasePak server software and DBMS client software. See host.
application program: A computer program that is designed to accomplish a specific task or set of tasks via manipulation of user input and previously stored data. The end users of a computer system typically interact with applications that accomplish the user's purposes for using a computer system. LeasePak is an application. Word processors and spreadsheet programs are also application programs. Computer games are another form of application. The programs that control the electrical grid or subway systems are application programs, too.
Application Program Interface: Also known as an "API". This is a set of technical conventions that define how an application program, such as LeasePak, can obtain data, computations, or actions from a service or data source, such as a relational database or an external provider, such as the Vertex Sales Tax system, or a bank or a manufacturer.
ASCII: American Standard Code for Information Interchange. Formerly the gold standard character set of computing.
ATT: The installation configuration file and journal of the Queue Manager, located in $QMDIR.
awk: A standard UNIX/Linux utility that does pattern-matching on textual data organized into fields and records.
backup: A backup is a copy of the data, settings and software on a computer system, made to removable or remote media, kept in case of severe error or failure or crash of the computer system, whereby the computer system can be restored to a reasonably recent point in time after the failure or error has been addressed. The LeasePak package requires frequent backups, and getting them right is critically important. See Backups.
bash: The so-called "born again shell" favored on Linux systems. It is a command-line interpreter (CLI very closely related to the original UNIX sh shell, which is often called the "Bourne Shell" after its author. Thus the name of bash is an elaborate, insiders-only, pun. Though its name was concocted with humor, it is a considerably more powerful shell than its ancestor 'sh', while remaining largely compatible with it.
batch job: A batch job is a job that performs large quantities of processing in an unattended mode, allowing for maximization of system resources.
batch queue: A batch queue is a software construct sponsored by the Queue Manager. It behaves like a first-come/first-serve type of waiting line. It controls access to CPU time, such that only a certain number of tasks at a time can execute and use resource. It is primarily used for End of Period and other bulk or batch processing.
bcp - bulk copy: A Sybase utility that can copy data stored in Sybase tables to a variety of formats. In particular, LeasePak uses the bcp utility to create ASCII files containing rows from the LLDB in the form of database snapshots. The format of the exported data has proven useful to many users of LeasePak, and is replicated in a NetSol utility lpobcpout for exporting Oracle data.
Also, '.bcp' is a filename extension applied to filesystem files containing bcp-format data.
bcp query: .bcpqry - the file name extension of files prepared for use with db_snapshot's -q option to produce user-customized data exports. For more information see Custom Bcp Queries.
BLDDIR: See $BLDDIR.
boot: An item of footwear, often stylish, often rugged, that is characterized by having straps on either side of the leg opening of the shoe, to facilitate getting one's foot into it. It is in reference to these that the popular phrase "lifting oneself up by one's own bootstraps" was coined. In computer systems, when a computer is first started, it has to find its instructions for operation somewhere. These instructions are usually useful only to a particular type of computer, and are present with the computer hardware, waiting to be read and executed by the computer when it first runs.

These instructions typically tell the computer how to find the more elaborate instructions that comprise the operating system, and thus came to be called 'bootstrap instructions', whereby the computer was able to lift itself up by its own efforts to a higher level of usefulness. And thus, 'to boot' a computer is to turn on or reset the computer, such that it again accesses those bootstrap instructions, and on loading the operating system, lifts itself up to become a useful tool. 'boot' has been extended to quite a number of ancillary terms in computer parlance, with the meaning, "initial instructions" or "initial capabilities".
Bourne Shell: The original shell program of Unix. Mostly replaced by the POSIX shell.
build: A build is the output of the LeasePak build system, which constructs LeasePak's libraries and drivers from source code on a nearly daily basis. These are packaged up in a single directory hierarchy, together with the suite of LeasePak utility scripts, the SQL code necessary for database construction and processing, and other important files. The head of this hierarchy is the entity called the build. A build may be installed in an existing LeasePak instance, and can be promoted to the $live build, so that all environments using the $live build are immediately and completely upgraded to the new software contained in the build.
build directory: See $BLDDIR.
build ID: The build ID is different for every iteration of the build system. Each time time the build system completes a cycle, the build sequence is incremented. The sequence increments once per cycle when that cycle produces a sequenced object. The sequenced objects are the LeasePak link libraries, and the LeasePak drivers themselves. By keying the sequence number to the production of an object, we are guaranteed that no two instances of the same objects will have the same sequence.

The build ID is made up of the release in #.##. format (for example 7.70), plus "." plus the 4-digit build-sequence.
build ID alias: The build ID alias is the name of a symbolic link within the LeasePak $TOPDIR directory tree. It points to a build in the $BLDDIR directory. live is an example of a build ID alias; $live contains the full pathname of the live link. In Runtime LeasePak, live is the only alias available. In Development LeasePak, bld, dlvy and stage are also available aliases.
cfg_gen: The NetSol-supplied script that uses relscfg.msirc and templates from NetSol to generate a set of files used to configure the environment of users who connect to the application host to use LeasePak.
change_env: A Netsol-provided utility script which finds and assigns the LeasePak start-up files to a user's home directory, such that when the user logs onto the application host, his UNIX environment is configured with all the necessary values allowing him to function within LeasePak. Each LeasePak environment has its own unique set of start-up files which cause the user's environment to point him or her to a particular environment and LLDB. This command is used by the $NSTADMIN to assign users to particular environments where they may do their work.
CHAR(length): Oracle DBMS fixed-length character string. Typically used for string columns which are less than 20 characters in length. Always used for string columns that are indexed, regardless of length. length denotes the maximum number of characters the string can contain.
char(length): Sybase DBMS fixed length character string. Used for all LeasePak string columns, except the info_s columns in the Notebook tables. length denotes the maximum number of characters the string can contain.
C-ISAM: C-ISAM is an acronym for "(?) Indexed Sequential Access Method", a standardized method of creating indexes for data files. It is generally used only with flat files, as it is in LeasePak for non-relational tables. See $udata.
chkconfig: A Linux command that handles installation of init services, such as the Queue Manager start-up files. See svcctrl. See the Linux man page for chkconfig and service.
chmod: A Unix/Linux command for modifying the access rights on files and directories. See the relevant man page.
cleanse_s7: A NetSol-provided utility script that shuts fown the Queue Manager, cleans up various Queu Manager temporary files, releasing important resources, and then restarts the queues.
cleanup: A Queue Manager utility that removes unused logicals from the system. Called by cleanse_s7, and also by cron.
CLI: An abbreviation for command-line interface or command-line interpreter.
client: 'Client' is an ambiguous term. A NetSol client is an organization that purchases the LeasePak software package from NetSol. A client system is a computer system that acts as the consumer for services served by a server. The user of LeasePak typically has clients that are customers of the leasing operation. The LeasePak client is the PC-based software package that integrates with the LeasePak server.
client string password: The original password used by the user of the LeasePak client software.
column: See database column.
com-file: See command file.
combined host: An architecture that combines the functions of a database host and of an application host onto a single host. Also known as a unified host.
command file: A file that contains commands intended to be executed by a computer-system's CLI. A script.
command introducer: A feature of some CLIs that requires that every command be preceded by one or more specific characters to notify the CLI that a command follows.
command-line interface: A function offered by some programs that enable the user to instruct some associated software by typing in commands from the keyboard, or placing the commands in a text file. This necessitates that the associated software have a command-line interpreter function that allows for the user's input to be parsed and, if valid, performed. Often abbreviated as CLI.
command-line interpreter: A function required of some software to parse, validate, and execute instructdions typed in by a user, or found in a file, to control the behavior of the software. The classic case is that of command shells, or shell, programs used in many operating systems. Each shell has its own particular syntax, or means of constructing commands, that the command-line interpreter must be able to comprehend. Often abbreviated as CLI.
command prompt: A short message printed to the terminal screen that indicates to a user that the command-line interface that prints the message is ready to accept user input at the keyboard. Often may consist only of a single character, but also may contain various data, such as the current working directory or the user's name, etc.
command qualifier
command shell: A program, typically found in an operating system's core, that provides a command-line interface with which users can interact and instruct the operating system to perform various tasks. Sometimes simply called a shell. Usually the shell waits on a terminal, displaying a command_prompt to indicate to a user that it is ready for user input at the keyboard. Command shells also typically are capable of reading their instructions from a text file, just as if a user had typed them at the keyboard. See bash, csh, ksh, sh, tcsh.
command syntax: The grammar or rules that dictate the composition of command-line interpreter programming, and define what the CLI does with each construct. While there are significant diferences between sh style shells and the csh style, the basic order of commands is the same: {command} [param] [param] [...], that is, the name of the command and a list arguments, or parameters, for the command to work with. There are control structures available in most shells, which conditionally execute commands arranged in blocks, based on the current state of the program's environment.
common storage segment: See storage segment and About Storage Segments. A common storage segment is an Oracle tablespace, set up for LeasePak use, and recommended for small test LLDBs, such as ones used to load Level7 data. The maximum space allocation allowed on a common storage segment is 300MB. Under Sybase, all storage segments are available in fragments to any LLDB.
concurrent: Literally, "running together". In a cmputer system, concurrent describes the situation when multiple tasks are being executed in a round-robin fashion, such that the users requesting the tasks are only slightly aware that they are not getting 100% of the computer system's power. Concurrency is that state where tasks are perfoemd concurrently. Concurrent users are ones who are accessing and using the computer system at the same time.
Config: When capitalized (Config versus config), refers to the Queue Manager's primary configuration file, located at $QMDIR/library/Config. This file contains the primary settings for tailoring the Queue Manager to the site's needs.
core: A core file is an image of the memory in use by a program upon its forced termination. Often when a program encounters severe error, or the OS decides that the program is out of control, the program or operating system can cause the program to terminate, and in so doing, the OS makes a copy of the memory used by the program so that it can be analyzed to determine the cause fo the error. This process is called dumping core or dropping core, and the result is a core dump or core file.
core.PID: On Linux, core files are named core.PID, where PID is the process id of the program that created the core.
core dump: A core file.
core file: See core.
cron: The scheduling daemon on Unix and Linux systems. It is controlled by a crontab, which defines jobs to be run at specific times or inetervals. In LeasePak it is used to automatically run the Queue Manager cleanup program several times a day.
cron job: A scheduled task executed by cron.
csh: Csh is a command shell that is supported on most unix and Linux computers. It's command syntax is rather different than the standard sh shell syntax, making portability of scripts problematical. Its syntax purports to be somewhat like the C programming language, hence its name "C-shell" (also a lame pun). While the LeasePak-generated start-up files with the .msirc extension are designed to be compatible with both sh and the csh, the NetSol scripting libraries are written and executed as sh programs. There is a slightly more sophisticated version of csh, called tcsh.
CSTDIR: see $CSTDIR.
Custom BCP Queries: A means by which db_snapshot can be configured by the end users to produce bcp files using SQL to extract records from the LLDB according to a SQL query, and output them to text files suitable for formatting. See Overview of Custom Bcp Queries;
Custom General: A family of record types in a LeasePak database, used to store user-customized settings and preferences.
Custom General Printer Device: One of the family of Custom General tables, used to store information about printers and print queues.
custom General Printer Form: One of the family of Custom General tables, used to store information about the forms and papers used by LeasePak for print formating.
data: The base name of the $udata directory.
data device: Sybase storage segments are divided into two classes: those for data storage, and those for transaction log storage. A Sybase device is a particular set of hard disk resources grouped together for manageability and referred to by a single name. When allocated to LLDBs, the space on the device can be broken into fragments of space. CRITICAL Data devices and log devices must never be placed on the same physical media, or the database, if error occurs, may not be able to be repaired..
data segment: Sybase databases each have two segments: the data segment, used to store tables, and procedures, and indexes and views; and the log segment, used to store transaction logs. The current, internally consistent state of the data is stored in the data segment. The data in transition or in the past is stored in the log segment. See log segment.
database client: The software of a DBMS that is available to, or compiled into, an application program, providing an API that enables it to connect to a database server to store and retrieve application data from the DBMS.
database column: One of two dimensional aspects of a database table in a relational database. See row. Rows are the individual units of storage, sometimes called "records". Each row contains a specific set of database columns, detailing the "fields" of the "record". Each column has certain attributes, such as datatype, width, name and whether the column can contain a NULL value.
database device: A set of hard disk resources that are managed by the Sybase database server for allocation among the individual databases that Sybase supports. There are two kinds of database devices: data devices and log devices.
database environment: See LeasePak database environment.
database host: An architecture that locates the database management system database server processes and storage on a host separately from the host containing the LeasePak server software and the database client software.
database management system: (DBMS) A software package that provides all services necessary to support end-user databases and data stores. Typically includes a server portion and a client portion that can reside on separate servers, or together on a single server. The two database management systems that LeasePak supports are Oracle and Sybase.
database owner: Another name for the DBO.
database row: The individual units of storage making up a table. Also called a 'record'. It consists of a specific set of database columns, containing the values pertaining to that record. Each row in a table has the same set of columns as every other row in the same table. The values in each column may vary from row to row, but the layout of columns is the same across all the rows in that table.
database server: The software of a DBMS that centrally manages the storage and retrieval of data for a group of associated database client processes, usually on a network. The database server provides an API that allows external programs to connect and obtain services from the server. Usually the server's API connects to a complimentary database client that itself presents the API to an application program for its use.
database server administrator: This role is usually known by the $SRVADM. This role is empowered to allocate disk resources to LLDBs, and to add users to the DBMS.
database snapshot: see snapshot.
database system: synonymous with database management system (see).
database system root user: The super-user of a DBMS, the role given ultimate authority within the DBMS. In Oracle, this is usually called the sysdba; in Sybase it is called sa. Both roles are sometimes called DBAs.
database type: The database type indicates which DBMS is to be used to implement and manage the LLDB. The possible values are 'ora' for Oracle and 'syb' for Sybase. Also sometimes called db-type.a
database user: A person or role who has an account set up under the aegis of a database server is a database (system) user. See also OS user and LeasePak user.
dataset: A dataset is an integrated group of export files that together can comprise a working instance of an LLDB. A dataset can also contain just a sub-set of the data from a LLDB. See also About Datasets.
datasets: See $datasets.
DATE: Oracle DBMS date and time. Contains century, year, month, day, hour, minute, and second information. LeasePak uses only the date portion (century, year, month, day). It does not use the time portion (hour, minute, second). If the datatype of a column is DATE, the column name begins with 'd_'.
datetime: Sybase DBMS date and time. Contains century, year, month, day, hour, minute, second, and second fraction (accurate to 1/300 second) information. If a column has a datetime datatype and the column name begins with 'd_', LeasePak uses only the date portion (century, year, month, day); it does not use time portion (hour, minute, second, second fraction). If a column has a datetime datatype and the column name begins with 'dt_', LeasePak uses both the date and time portions.
DB type: See database type.
db_add_login: A NetSol-supplied utility script that is the only supported way of adding a new user to the database system. It adds a given user name (who must be a UNIX user as well) to the DBMS user table, and assigns the user's password from the command line, which should be the SQL server string password from lease /util 112.
db_add_user: A NetSol-supplied utility script that is the only supported way of enabling a user to use a particular LLDB. It gives the user, who is a user in the database system, having been added by db_add_login, the ability to access the given environment's LLDB, by assigning him or her to the DBMS group (role) msi or msir. If the user is to be a report user, then msir should be used.
db_create: A NetSol-supplied utility script that is the only supported way of constructing the relational database portion of a LLDB. It is a shell program that calls several others in order to perform all of the critical steps in precisely the correct order to successfully construct the DBMS portion of a LLDB. See About LLDBs for more information.
db_restore: A NetSol-supplied utility scripts that optionally wipes one or more tables clean in an LLDB, and then loads one or more snapshot files into the database tables. When this is done for an entire snapshot or dataset then the state of the LLDB at the time the snapshot was made is effectively "restored".
db_snapshot: A NetSol-supplied utility script that exports contents of the LLDB to ASCII files in a dataset. Also supports export of partial contents via Custom Bcp Queries. See LeasePak Server Configuration and Maintenance.
DB type: See database type.
db_update_statistics: LeasePak server script. Updates statistics, selected and tuned for LeasePak databases (LLDB), for an entire LeasePak database, a single LeasePak database table, or the Oracle data dictionary.
DBA: Acronym for Database Administrator. A role in DBMSes. Often synonymous with database system root user, the role accorded the greatest privileges in the DBMS.
DBMS: See database management system.
DBMS Account: A user who is to access an LLDB must have an account, that is, be a registered user, with the DBMS. In LeasePak, this account is created by the utility db_add_login. A user who has an account in the DBMS, is said to have a DBMS login and is a DBMS user. Having the DBMS account does not give a user access to a LLDB, that action requires use of db_add_user.
DBMS group: In terms of access to the LLDB, there are users who are allowed to run update programs which change the contents of the LLDB. Other users are allowed only to query the database, such as running reports. In addition to restricting access via the different types of users, each DBMS user is identified to the database server as an update user, or a read-only user. This is done via the DBMS group that is a parameter given to the db_add_user command. The group for update users is msi, for read-only users it is msir.
DBMS host: Host containing the DBMS server software.
DBMS login: See DBMS account.
DBMS root user: See database system root user.
DBMS user: A user who has a DBMS account.
DBO: Also called the LeasePak Database Owner. DBMS role who owns the LLDB. Typically, each LLDB will have its own dedicated owner fulfilling this role. For Oracle DBMS, this user is the Oracle schema for the LLDB. For the Sybase DBMS, there are two modes of ownership, distinguished by the environment variable $SYB_AUTODBO If $SYB_AUTODBO is set to N, then db_create will ask the operator to enter the name of an existing Sybase user to be assigned the role of DBO. If $SYB_AUTODBO is set to Y, then db_create will create a new Sybase user with the same name as the LLDB (and prompt for a password) to be the DBO. See Environments & Databases. This behavior in Sybase then emulates the situation in Oracle. It is strongly recommended that $SYB_AUTODBO be set to Y.
DCL: Acronym for DEC Command Language, the native language of the Queue Manager.
decimal notation: Numeric values expressed in base-10 digits, 0-9.
dedicated port: The TCP port on which LeasePak listens for connection requests from users, where each user has a unique Unix server account.
dedicated storage segment: Under Oracle, there are two types of storage segments (tablespaces) usable by LeasePak: 1) common storage segments and 2) dedicated storage segments. The common tablespace by convention contains multiple test and experimental LLDBs, all with their own allocations of space from one or more common tablespaces. The dedicated tablespace is by convention related to the LLDB to which it is dedicated by name. It must be clear to the operator of db_create which table space is intended to be the source of the space needed by the LLDB. It is recommended that the system administrator adopt a naming convention for Oracle tablespaces that makes the database to which a dedicated tablespace belongs unequivically clear. See Naming Conventions.
dedicated user: In the terminology of the Shared User module, there are dedicated users, who each have their own UNIX account, their own DBMS account, and a LeasePak Security Record; and there are hosted users, who access the application host and the database system uaing the credentials of a proxy user, set up especially for this purpose. Once a LeasePak driver is running on the application host, then the hosted user's password is authenticated and he is allowed to interact with LeasePak. Hosted users each have a LeasePak security record, where their scrambled RSC password is stored. See also the Shared User Overview.
delimiter: One or more characters used to define the boundaries of fields or records of textual data. Frequently used delimiters are spaces, tabs, commas, periods, colons, slashes, etc. An example of a delimiter in common use is the slash (/) character in denoting dates: 08/10/2015.
Development LeasePak: The full installation of LeasePak, with all of its source code and utilities, used to program and modify LeasePak. See also Runtime LeasePak.
DEVINIT: A Queue Manager configuration file located in $QMDIR/Library. It contains entries for the disk drives the QM expects to interface with, as well as terminals expeted. Slao contains entries for printers.
disk device: Sybase manages physical disk space via software constructs called "disk devices". Each disk device consists of all or part of a disk partition designated as storage for Sybase on an available disk. Sybase can allocate multiple devices for eacb LLDB. Also, partial disk devices can be allocated to LLDBs as well. See Storage Segments for details.; The storage capacity of a computer disk storage device. Can refer to either the gross space available (how much data can teh disk hold?) or the net space available (how much user data can it still hold after overhead is accounted for?) or the remaining space available (how much capacity is left after overhead and all the other data being stored there).
double precision: Sybase DBMS floating-point number. Used to store percentages, rates, and dollar amounts.
driver: See LeasePak driver;
EFSDIR: See $EFSDIR.
end of month: The processing associated with closing out an accounting month in a business operation. LeasePak has certain jobs that are run at End of Period, specifically targeted to end of month processes.
end of period: Also known as "EOP". Processing that is used to close out daily, monthly and other periodic bookkeeping work. Many tasks that cannot be performed while the users are using the system are performed during EOP. See Reference Guide, U04 for more information.
environment: See LeasePak database environment
environment variable: Each running Unix process has what is called an execution environment which includes the process's command line with which it was started, including its parameters, the memory that the process occupies, and a list of name/value pairs, which are environment variables. Programs often rely on these environment variables to direct their work, and to locate their resources. In LeasePak, a very large set of name/value pairs are added to the environment, which allow LeasePak to find its myriad and often scattered parts, its data, its set of allowed actions, the names and locations of resources, etc. Each name/value pair is stored in the environment as an assignment, name=value;. When a program, such as a shell, requires the value of one of these, it references it by prefixing a $ sign to the name: $name. Thus the user will see many times in this documentation references to environmental variables or values, with $ prepended.
env-name: The name of a LeasePak database environment.
EOP: See end of period.
EOP updates: The various update programs that run during End of Period Processing. See Reference Guide,U04 for more information.
EUCO: Acronym for End User Code Objects. See EUCO.
export file: Files containing LeasePak data exported from the LLDB by an export utility, such as bcp or lpobcpout. These are one of the types of files found in LeasePak datasets.
export segment: When Oracle data is exported by lpobcpout, export files are limited in export size to 2GB. Each time the exported size approaches 2GB, the file is closed and a new file, whose name is extended by the next sequence number available, is opened. Therefore, for a large table such as the rtx, there may be several export files, such as rtx.bcp.1, rtx.bcp.2, and so on, each containing approximately 2GB of ASCII data. These files are called export segments. Separate segments are also created when using custom bcp queries.
file path component separator: A special character used to separate components (directories) in file pathnames. For example, / in Unix/Linux, \\ in Windows, and others.
form: An ambiguous term, just in the context of computer systems. It can refer to a set of screen fields intended for data entry; it can refer to similar paper objects. In the context of paper obejcts, forms may be designed to be filled out by humans, or they may be designed to have their contents printed. The form may be entirely digital, and is expressed along with its data in printed form without a preprinted paper container. In the context of LeasePak and its Queue Manager, it refers to different paper stocks, preprinted or not, and different orientations according to the capabilities of the printers. Forms are defined in the start_queues.com file, and any output device can specify that its output be formatted for a defined form.
full backup: A copy of a computer's hard-drive storage systems onto a separate medium, stored in a safe place away from the computer is a backup. A full backup is a complete copy with no significant exceptions. As opposed to an incremental backup.
GID: This is an acronym for group identifier, the unique number given to each OS group. When it comes to arbitrating access to machine resources on the host, the UID is considered first, but then the user's process GID is considered in light of the permission modes on the file. This allows different users to access the same resources that may be owned by various UIDs, provided they belong to the group which is the group owner of the file in question.
hexadecimal notation: Numeric values expressed in base-16 digits, 0-9 and a-f.
HOME: See $HOME.
home directory: Each OS user typically has a home or default directory on the host that typcally bears the same name. Usually located in /home, it is the user's working directory upon logging onto the host. LeasePak uses this as the default location for many reports and other files read and written by LeasePak.
Host (disambiguation): This term is used in at least three contexts in LeasePak.

Host may refer to a hardware computer server, such as the DBMS Host or the application host or a combined host, or a split host. More generically, any computer server system can be called a 'host', and is usually qualified with the nature of the capabilities that the host provides, such as 'DBMS', or 'application', or 'internet', etc.

Host may also refer to a LeasePak environment configured to accept visitor environment connections. See Environments & Databases.

Host may also refer to the capabilities connected to a proxy user in an implementation of the Shared User module; users using the proxy are said to be hosted users.
host environment: A LeasePak database environment that has been set up to share its LLDB with one or more visitor environments. See also host.
host printing system: Most business level OSes have a system for controlling access to printers that may be attached. In LeasePak, printing services are provided by the Queue Manager, which in turn feeds the task of printing to the hsot printing system, which does the actual printing.
host system: A computer system, or server, that hosts software systems like LeasePak. Some sites may require multiple hosts. LeasePak is hosted on 3 operating systems, each running an OS derived from the UNIX operating system. All LeasePak host systems are of this type.
hosted user: A hosted user is a user of the LeasePak client, who accesses the application host and the database system using the credentials of a proxy user, set up especially for this purpose. Once a LeasePak driver is running on the application host, then the hosted user's password is authenticated and she is allowed to interact with LeasePak. Hosted users each have a LeasePak security record, where their scrambled RSC password is stored. See also the Shared User Overview.
HOST_v99x_rt.*: For example, host_v77a_rt.*. During the installation of LeasePak, SETUP asks the administrator for various locations and preferences; these then guide the installation process, and also determine all of the OS environment values for the users of LeasePak. The answers to this "interview" are stored in $CFGDIR/relscfg.msirc. Then another process (cfg_gen) combines these answers with skeletal structures from NetSol, and produces 3 shell start-up files, named "HOST_v99x_rt.*" where "HOST" is replaced by the hostname of the server or cluster where LeasePak is being installed, and plus the LeasePak release version, and "*" is replaced by "msirc", and "com", and "lpkd". These 3 files are then available to users who successfully log into the application host via a shell login (the "*.msirc" file), via a client LeasePak session from a network PC (the "*.lpkd" file), or via jobs running on the batch queues (the "*.com" file). See also host.
HOST_v99x_rt.msirc: The run-time configuration file containing values from SETUP, that is read into LeasePak shell environments. There are several such files. See HOST_v99x_rt.*.
incremental backup: Part of a computer backup scheme that utilizes a full backup on a periodic basis, usually more than a day, and then during intervening time periods, incremetal backups are made, each expressing the changes since the last full backup. This enables much shorter backup time periods, during which the system is unavailable.
index: An index is another aspect of a relational database table. An index provides a means of retrieving a single database row using a minimal amnount of identifying information. If an application program has enough of this identifying data, then the record can be retrieved in the shortest amount of time. If the application does not have all of the data needed to retrieve a single record, then it often can use the data it does have to retrieve a group records that match the available data. The index makes this retrieval process automated, efficient and complete. Tables often have multiple indexes, each comprised of a different, but overlapping, set of columns extracted from the same group of records.
init: init is the primary process of a Unix/Linux system. It is responsible for the inception and termination of all user and system processes. In particular it insures that services are running or not running at appropriate times.
init.d: The directory in Unix and Linux used to store computer tasks that are performed when the system is being booted up or shutdown.
initialization file: A file, usually a text file, containing program instructions and data for a particular program to be run, which instruct the program as to its environment and what tasks it is to perform. Very few programs run without some sort of details as to the user's expectations, and some sort of explanation of the lay of the land, so to speak. The initialization file provides this information.
INITDIR: see $INITDIR.
instance: See LeasePak instance.
instance ID: See $INST_ID.
INST_ID: See $INST_ID.
integer: Sybase DBMS integer number. Used to store whole numbers.
internet service: A service provided by a computer system to other computer systems to which the server may be connected via networking. A service implies a location (a port on the server, a communications protocol, such as TCP/IP so that systems needing a service can communicate their needs to the server, an application notation that provides the meaning to the protocol. A client requests the published service it needs from the server, establishing communication with it, and sending it its request. The server responds with the requested data. A single transaction may encompass a very small or very large number of such exchanges.

LeasePak advertises two particluar internet services, leasepakd and mpowerd. Both of these result in ongoing conversations between the client and the server.
IP address: IP stands for Internet Protocol. An IP address is the internet network address of a particualr computer system.
ipc: The Unix/Linux Inter-Process Communication system. See IPC. See also man 7 svipc on a Linux system to get an overview of the System V IPC mechanisms.
IPC key: An arbitrary number attached by a user process to an instance of an IPC facility, whereby the facility can be shared among cooperating processes simply by sharing the key.
isql: The Sybase DBMS command-line interface utility.
job: In computer terms a job is a planned sequence of computer operations that take data from some source, and process it, and produce new data. A job may require the execution of multiple applications, some of which may be repeated any number of times to accomplish the purpose of the job.
job limit: The maximum number of jobs a queue can execute concurrently. See About Job Limits.
job logical: In the Queue Manager system, there is a peculiar breed of environmental variables, called logicals. When running in a Unix/Linux environment, all Unix environment variables are available to teh Queue manager as logicals. There is a DCL statement that can be used to export logicals to the environment. There are different levels, or categories, of logicals: job logicals are scoped to the job, or program. System logicals are system-wide. The Queue Manager builds disk structures of logicals, and frequently runs out of space. For thsi reason, the Queue Manager cleanup must be run nearly hourly, typically through cron
job queue: See batch queue.
jspctl: The Queue Manager utility that accepts jobs from user processes, and schedules them for execution on a queue. Stands for Job Spool Control.
key: See IPC key.
ksh: The so-called "Korn Shell". An sh-derived command shell which enjoyed some popularity in the 1990's. Not often sought for in today's Unix/Linuix world.
lastsnapshot.txt: This file is present in every LeasePak-originated dataset. It is updated every time the dataset is re-exported. It describes the LLDB from which the data has been exported, who the user was that exported the data, and other internal details.
Leasepak administrative user: A standardized set of Unix/Linux users/roles useful in administering LeasePak. They include $NSTADMIN, $NSTDBA, and $SRVADM. $NSTGROUP, though not a user, is included in this set for documentation purposes.
LeasePak Administrator: See $NSTADMIN.
LeasePak client: The NetSol software product that runs on a LeasePak user's PC, giving access to the LLDB, and to all the functionality of LeasePak located on one or more servers or hosts. The client is in frequent communication with the LeasePak server processes.
leasepakd: leasepakd is an internet service that provides qualified users with connections to an instance of LeasePak.
LeasePak database: See LeasePak Logical Database.
LeasePak database administrator: See $NSTDBA.
LeasePak database environment: Directory tree containing configuration data, live ASCII data, and software links tying a LeasePak database (LLDB) to its LeasePak release. See Environments and Databases
LeasePak Database Owner: Also called the 'DBO'. DBMS user/role who owns the LLDB. For Oracle DBMS, this user is the Oracle schema for the LeasePak database. For Sybase DBMS, this is the owner of the LLDB. See Environments and Databases.
LeasePak driver: Usually plural, the compiled binary programs that make up the bulk of the user's interaction with LeasePak. The drivers include:

lpachkls.exe

lpadavox

lpadbdrvr.exe

lpadriver.exe

lpaeopdrvr.exe

lpaglintf.exe

lpainvc.exe

lparevolv_feeassmt.exe

lpaxmldrvr.exe

lpchgpass
LeasePak environment: See LeasePak database environment
LeasePak instance: An instance of LeasePak exists wherever on a server there has been a complete installation via the LeasePak SETUP program. It includes the $NSTDIR, $CSTDIR, $TOPDIR, $QMTMPDIR, $QMSPOOLDIR directories, the leasepakd service, the nst_qm_{ID}99x init service. The properly configured instance can, separately from other instances located on the same application host, run all LeasePak functions without conflict. To fully qualify, there must be an environment built (setup_new_env), and a working LLDB (db_create, loaded (see db_restore with level7 data, and a lease booked, and an EOP run.
LeasePak License: Since LeasePak is a proprietary product, and because extensive support is often needed for a LeasePak installation, and to restrict NetSol's services to paying customers, NetSol provides each customer with a license file created just for that customer. The license enables modules that the individual site has purchased from NetSol. Without a license that allows these function to be used, the clients's purchase of LeasePak would be useless. In addition to the module switches, the license also lmmits the number of users authorized on the client's servers, by license class.
LeasePak Logical Database: Also known as an 'LLDB', this is a logical database designed to hold the tables, views, indexes, stored procedures and other objects related to the operation of LeasePak. It consists of two parts: the relational database portion stored and managed by a DBMS, and the non-relational portion, consisting of datafiles and their indexes stored in the $udata directory of the LLDB's associated environment. See about LLDBs.
LeasePak non-administrative user: A LeasePak user who is not a LeasePak administrative user. All non-administrative users have RSC records in the LLDB. There are several categories of non-administrative users: There are 3 types of licensed users: regular users, report users, partial update users. Also among the non-administrative users is the proxy user. See license class.
LeasePak release owner: A term descriptive of one of the functions performed by the $NSTADMIN.
LeasePak security record: A row in the LeasePak security table, the rsc, is a LeasePak security record. It contains flags for allowed menu optons, ranges of values to be validated against, the RSC password for the Shared User module, etc. A user is not a LeasePak user unless he or she has a LeasePak Security Record
LeasePak server: The LeasePak drivers, utility scripts, and Queue Manager comprise the LeasePak server. This software may be located on a host separate from the database host or may be located on the same host as the DBMS. See also combined host.
LeasePak Start-up File: This is a configuration file read by LeasePak-oriented processes to configure their execution environment for using LeasePak.
LeasePak Supervisor: LeasePak Supervisor -- Although the site can assign this role to $NSTADMIN, $NSTADMIN cannot change its own environment (or the environment of $NSTDBA) by using change_env, so NetSol recommends creating a separate user, such as lpadmin, as the LeasePak Supervisor. This user performs software administration tasks such as adding new LeasePak users into the Security [U0706] update, submitting batch files, running End of Period, and using programs in lease /util, as well as general system configuration through refU0712 and the tracking module updates.

See LeaasePak Supervisor for details on this important role.
LeasePak user: A person or role who has all of the following: an OS user account, a database user account, and a LeasePak security record.
LeasePak utility: An ambiguous term. See utility script and also LeasePak /util menu.
LeasePak /util menu: A large menu of text-based maintenance operations provided by the LeasePak Server, and accessed by using the command lease /util nnn, where nnn is the 3-digit utility number.
lease /util 108: A LeasePak utility program that may be used to set up the security record for the LeasePak Supervisor, or Lpadmin
lease /util 110: A LeasePak utility program that may be used to store the encrtypted proxy DBMS user's password.
lease /util 112: The LeasePak password translation utility. This utility produces 3 different hashes of a single input user password. These hashes are calculable from the other hashes of that password, but they are all unreversible; the original password cannot be calculated based on any of the output hashes.
level7: One of the two default, standard datasets shipped with LeasePak. This dataset represents a small leasing operation and has clients, assets, applications, leases, vendors, accounting transactions already existing in the data. It is used for training new users, and for testing scenarios both for experimentation and for diagnostic purposes.
license: LeasePak is a product that is licensed to NetSol clients to use in their leasing operations. In order to maintain control over the use of the product, NetSol provides each client with a software license, which is a written contract. The salient points of which modules are licensed by this contract to a particular client, and for how many employees are to be supported, is encoded into a license file that is unique to every client. This file is named lplicense.dat, located in the $TOPDIR/exe/syb or $TOPDIR/exe/ora directory.
license class: The LeasePak license authorizes three classes of users: regular users, report users, partial update users. In this context user means one who has an RSC record.
Linux: A Unix-like operating system that has become the de facto standard operating system for non-Windows Intel-based personal computers in today's industry.
live: See $live, also build id alias.
LLDB: See LeasePak logical database.
lock contention: A multi-user computer system, such as is used to run LeaePak, often has a mechanism that allows a user to prevent other users from changing the dataabse contents while the first user is making a set of changes. This prevents incomplete changes and is thus vital to data integrity. The mechanism for preventing other users access is often called "locking", which, when a user has a lock on a set of data, prevents others from changing the locked data. If there are two or more users trying to access the same data, frequently one or more users must wait for the preceding user to complete his task and release the lock. This waiting is called lock contention.
lockout: A lockout is a semaphore file informs the system that a certain user is no konger allowed to log onto the system. This is usually placed by the login authority when a user fails to enter a correct password a certain number of times. See Locked Accounts.
log device: In Sybase, each database must have disk space in a data area, called the data segment, and disk space in a log area, called the log segment. The log segment must be located on one or more log devices, which are exclusively for the use of transaction logs.
log segment: The portion of a Sybase database that is used for transaction logs. These logs are essential to the repair of a database that has encountered error or system failure. They instruct the recovery system on how to undo transactions that were not completed at the time of the failure. This recovery helps insure that the database contents are made internally consistent after a failure.
logdb.msirc: A configuration file that sets a shell session to point to a particular database environment. Stored in the environment's etc directory.
logicals table: A table used by the Queue Manager package to store important envinonment values.
login name: Another term for user name"
loose naming: The loose naming convention (see also strict naming convention), which imposes only a few restrictions on the administrator in regards to chosing names of various LeasePak entities (environments and databases, etc).
LPAdmin: Another name for the LeasePak Supervisor.
lpchgpass: A LeasePak utility that allows an adminstrative user change a user's passwords in a single transaction, including the original client string password, but also the translated passwords.
lpkdport
: The TCP/IP port where leasepakd is asssigned to wait for connection requests. Set in SETUP, in response to the question TCP port assignment for leasepakd inet daemon [####].
lpobcpout: A NetSol-provided utility program that replicates some of the behavior of the Sybase bcp utility, insofar as creating export segments in datasets.
man page: An abbreviation of manual page. A tradtional Unix documentation system that features a separate file for each page of the Unix manual. Documentation for a Unix command, such as ls, can be accessed by simply typing at the command prompt: % man ls
message queue: Message Queues are part of the IPC (Interprocess Communication system). They are used to communicate between the jspctl job spooler and the qmgr processes that run the individual queues.
month end: See End of Month.
mPower: LeasePak's web origination tool.
mPowerd: The mPower package's equivalent program to leasepakd (see).
msirc: Thr .msirc file name extension signifies that the file is a text file containing shell-neutral commands for the configuration of a user's environment for working with LeasePak. Using only idioms found in the major kinds of command shells, sh and csh, and performing workarounds where no compatibility could be found, msirc files can be executed by either shell, resulting in equivalent environments regardless of the shell used.
multiple hosts: A site configuration consisting of one or more application hosts together with one or more DBMS hosts
multisegment: Describes exported data files that span more than one filesystem file (export segment) in a dataset.
naming convention: A set of rules that prescribes the format of various names, database objects, program variables. There are two types of naming conventions in LeasePak: strict naming and loose naming. See Naming Conventions.
native: in-born, innate, intrinsic, original
native backup utility: A computer system backup program that is designed especially for makng backup copies of technically complex and propritary data; considered the best option for backing up DBMSes because it should take nto account all of the internal proprietary features of the DBMS, which non-natie utilities sometimes lack.; See native backup utility.
NetSol Help Desk: There is an operator standing by during US business hours, ready to assist LeasePak users, wherever located. This is the central point of contact between the user community and the NetSol Alameda headquarters staff. If they do not know the answer to a customer question about LeasePak, they assuredly will know someone who does know the answer.
non-administrative user: See administrative users for a list of the admin users. A non-administrative user is a LeasePak user who is not an administrative user. Non-administrative users have RSC records. See non-administrative users.
non-volatile environment: For environments that point to production databases, you may wish to protect the production database by disabling the LeasePak scripts that can drop the database or delete all of its data. This will prevent the inadvertant deletion of the database by those scripts. The two scripts to disable are db_drop and db_restore. The way to disable them is to designate the environment as "non-volatile".
A 'non-volatile environment' is one for which the db_drop and db_restore LeasePak scripts have been disabled. You can designate any environment as non-volatile, though typically it would be applied to production environments..
NSTADMIN: See $NSTADMIN.
NSTDBA: See $NSTDBA.
nst_dbora: A NetSol-provided init service to start-up and shutdown an Oracle instance.
nst_dbsyb: A NetSol-provided init service to start-up and shutdown a Sybase dataserver.
NSTDIR: See $NSTDIR,
$NSTGROUP: See NSTGROUP.
nst_qm_{ID}99x: The Queue Manager init service created by SETUP that starts and stops the batch queues during system start-up and shutdown.
NUMBER(15,scale): Oracle DBMS floating-point number. Used to store percentages, rates, and dollar amounts. scale denotes the maximum number of digits to the right of the decimal point. The maximum number of digits to the left of the decimal point is 15 minus the scale.
NUMBER(10): Oracle DBMS integer number, maximum 10 digits. The standard datatype used for most integers.
NUMBER(precision,0): Oracle DBMS integer number with a maximum of precision digits. Used only for integers which may exceed 10 digits and the "next number" columns in the msv* tables.
operating system: Abbreviated as OS. The operating system of the application host or the dbms host. HP-UX, Solaris, and Linux are the operating systems that can support LeasePak.
Oracle database: (ODB)—a physical database. The set of physical files—datafiles, control files, redo log files, etc.—which together constitute an Oracle database. Not the same as a LeasePak database. Each LLDB (Logical LeasePak database) is implemented as a schema within an Oracle database.
Oracle instance: An oracle instance is a set of software operating on an Oracle database.
Oracle software owner: Linux or Unix user account which installs, owns, maintains, and upgrades the Oracle software. The Oracle software owner is usually named oracle.
oracle service script: The script for use by init in maanging the Oracle instance(s).
origination: Origination is the portion of a leasing enterprise that seeks out new customers and business opportunities who need to lease capital equipment. The leases negotiated by the originator are sent to a leasing back office where the lease qualification and final negotiations take place. LeasePak has the ability to take data input by an originator (who uses an origination tool to collect and present the data) and process it into the system, allowing the back office to service the lease on behalf of the originator.
OS: See operating system.
OS account: A login account on a Unix or Linux server. Each Unix user has a separate login account. An OS account usually places the user in a command shell upon logging in. An OS account has a UID and a GID, and a home directory. In the home directory typically will be found shell start-up files that insure that the user's environment is properly configured.
OS group: Operating system groups are stored in the file /etc/group. They are part of the server security structure. Each group has a group name and a GID. All LeasePak users must have $NSTGROUP as their primary login group.
OS group name: See OS group.
OS login account: See OS account.
OS start-up file: This is a synonym for a shell start-up file from the perspective that the command shells are part of the operating system.
OS user: An operating system user is a person or role with a user account on the application host or the DBMS host. This is contrasted to the database user and the LeasePak user. In the context of LeasePak, this is synonymous with Unix user. Each OS user has an OS account, or OS login account.
Partial Update User: One of the three license classes of non-administrative users. This class is given access to the full report menu and to a small number of updates via [U0706] Security.
password: A word or phrase known only to persons authorized to access certain data or resources; the keepers of this data or resource require that the person prove their authority by providing the password. LeasePak uses passwords to arbitrate access to almost every function it provides. The database and the database system are protected by multiple passwords arbitrating access to multiple resources. The hosts on which LeasePak resides are also protected by multiple passwords to access multiple resources.

See client string password, Unix string password, SQL server string password, RSC string password, translated password.
password of the day: A password issued by NetSol that allows a user site to use lease /util 108 to provide the LeasePak supervisor with an RSC record. See Non-administrative users ?>.
path component: A directory or file specification within a pathname. The components are separated by file path component separators.
pathname: A pathname is a string of characters that describe the location of a file or resource in a computer environment. It is characterized by providing the chain of inter-related directories that lead one to the indicated file or resource. A pathname can be composed of several components, depending on the OS. On Unix and Linux servers, path names contain only directories, separated by "/", and possibly at the end of the string of directories might be a file name. Paths that begin with "/" are called absolute pathnames and give the location of the file starting at the very top directory, or root, of the server's filesystem. If the path is valid, it may be followed from subdirectory to subdirectory until the destination is reached. Paths that do not begin with "/" are relative pathnames, and show the path to the indicated file starting off with the current working directory.
pbcp: A partial bcp file that results from db_snapshot being used with Custom Bcp Queries. It is so called because it does not represent a full table snapshot as .bcp files usually do.
perl: Perl is a scripting language that enjoys widespread popularity and growth within the Unix/Linux community.
point: To point in LeasePak, means to be configured for use of. When a user logs onto LeasePak, a LeasePak startup file is read into the user's session, setting a large number of environment variables that LeasePak depends on to find the data and programs needed to peform its work. When a user's session points to an environment and release, he must read in all the necessary values.
port: A port is a part of the addressing system used by TCP/IP to direct network communications to the desired destination. There are thousands of possible ports at a given IP address. LeasePak uses up to 4 ports to provide connections to qualified users in order for them to access LeasePak. There is always a dedicated leasepakd port for dedicated users. There may be another for hosted users if the site implements the shared user module. If the site license includes mPower, then there will be a port for dedicated mPower connections and one for hosted mPower connections.
portfolio: In LeasePak accounting, the portfolio is at the highest level. All LeasePak business is done in terms of portfoilios.
POSIX: POSIX (Portable Operating System Interface) is a set of standard operating system interfaces based on the Unix operating system.
POSIX shell: The POSIX consortium's version of sh.
primary DBMS: Occasionally is it desirable for a site to support both the Sybase DBMS and the Oracle DBMS simultaneously, for instance to evaluate the other DBMS while keeping the currently in-use DBMS. If such an arrangement is made within a single instance, then one of the two DBMes must be designated the primary DBMS through the SETUP question Primary DBMS in this release.
primary login group: The operating system on the server typically has as part of its security structure the oncept of a group. Individual users are members of one or more groups. Certain files and commands can be accessed only by their owners, or by members of specific groups. When a user logs into the server, his/her process is assigned a default group ID. Which group is defaulted is determined by an entry in the /etc/passwd file. This is the primary login group. Membership in secondary groups is not denoted in /etc/passwd, but is instead denoted in the file /etc/group. While the primary login group must be in /etc/group, the users who have this group as their primary login group, should not be listed in /etc/group, as their membership is established by /etc/passwd. Secondary group membership only should be placed in /etc/group.
print queue: A print queue is a Queue Manage queue that has as its processing, th sequential prouction of printed matter. First in,first out.
print spooler: A print spooler on Unix/Linux machines is essentially a queue manager in its own right. This is how Unix/Linux handles the resource contention problem.
production: A production implementation of LeasePak is one that is being actively used to run a leasng busines, producing income for its investors.
production environment: LeasePak environment that can only link to drivers in $live. Typically ties to a LeasePak database (LLDB) containing production data.
protocol: In computer networking, a protocol represnts the "how-to" of the communications channel: who speaks first, who has to provide the other party with what, in order to establish a useful connection, where each participant knows what is expected of him and what to expec from the other parties.
proxy DBMS user
proxy server user: In the LeaePak Shared User Module, the proxy server user shares his credentials to enable one or more hosted users to access the LeasePak databawe and software; the hosted users the appear as multi-processes of the same single user, saving on licensing costs, and simplifying user administration.
proxy user: A proxy user is a regular OS user, but has no password. The proxy user's UID is used to give ownership to LeasePak processes spawned to run LeasePak drivers on behalf of anonymous LeasePak client connections. The proxy user also has DBMS credentials, also shared by the anonymous connections.
pseudo-device: A virtual disk, null device or print queue listed in the file DEVINIT in the $QMDIR/library directory. This represents the hardware the queeu Manager expects to find, allowing it to remain true to its DCL roots. The disk and null entries are generic, but each print queue must have its device in DEVINIT.
qjob_limit: This is the file, located in $QMDIR/library, that stores the queue job limit in the assignment of $QLIM=$QMJOBSPERQ. $QMJOBSPERQ is set when the administrator runs SETUP in response to the prompt, "Number of simultaneous jobs to allow for per queue[10]".
QMDIR: See $QMDIR.
qmgr: This term has two meanings:

it is the general abbreviation used to refer to the Queue Manager, found in many LeasePak names.

it is the name of the Queue Manager program which manages each individual queue, under the control of jspctl
QMJOB_LIM_FILE: See $QMJOB_LIM_FILE.
QMSPOOLDIR: See $QMSPOOLDIR.
QMTMPDIR: See $QMTMPDIR.
queue: A queue is a data storage structure used in computer hardware and software, that features the characteristic of first-in/first-out behavior.
queue com-file: See com-file. There are three primary Queue Manager com-files: start_qmgr.com, start_queues.com, and stop_qmgr.com.
Queue Job Limit: A Queue Manager system parameter that dictates the maximum number of jobs that can be running concurrently in a Queue Manager queue.
Queue manager configuration: The configuration of the Queue Manager takes place in several files. Some of these are in $QMDIR/library: Config, DEVINIT, qjob_limit. Some are in $QMDIR/com: start_queues.com, and in $QMDIR: ATT.
Queue Manager: The Queue Manager is a software system integrated with LeasePak that provides facilities for creating and managing software structures call "batch queues" which allow for balanced, reliable parallel processing of multiple concurrent tasks. See article on the Queue Manager.
quiescent: A database is said to be quiescent when it has no users actively engaged with the instance.
rc1.d: A script executed by init when the system enters runlevel 1 (single user mode).
rc3.d: A script executed by init when the system enters runlevel 3 (multi-user mode).
read-only: A read-only file is one that cannot be written, only read, by a particular process. This state of a file usually can be changed by a user with adequate permissions. Rad-only status helps to protect a file from unintentional or unauthorized changes.
reboot: To cycle a computer system from running, through shutdown, and then to boot again.
record: See database row. See also about LLDBs and also relational database.
regular user: Regular user is one of the license classs of users. Regular users may be given permmission through the [U0706] Security update by the LeasePak Supervisor to any of the modules and menu choices licensed to that site.
relational database: A computerized data storage and retrieval system that features structures where data items shared among records (also known as database rows) are themselves the keys to other records, such that information about the data item is stored in only one location, reducing redundancy and conflicting versions of supposedly identical data. Records of different types can be placed in relationships according to their shared data. This facilitates retrieval of groups of records by addressing the records based on their common keys consisting of data items, called fields (also known as database columns.
relative pathname: A pathname that does not begin with "/", and indicates the path of directories to follow to reach the target file or directory, starting at the current working directory. See also absolute pathname.
release: A release is a series of LeasePak builds, identified by a release_version. The thread that binds the builds into a single release is the layout of the database. Once a release of LeasePak is provided to NetSol customers, there are no further database changes until the next release version is created.
release version: LeasePak is delivered to the customer in the form of an install kit. Each install kit installs one build of the LeasePak package. The version contained in the build will be of exactly one release of LeasePak. It is possible through time for a site to install several different builds of the same release of LeasePak. The important point of multiple installations is that every build is an instance of a LeasePak release, and the release version is the identifier of the version contained in that install kit. Builds within the same release version may be installed one on top of another in the same directory hierarchy. The release version is always v + major release number, such as lpmajor + (optionally) . + minor release number, such as lpminor + the patch level such as a. For example the current release version of LeasePak is v77a.
relscfg.msirc: The file, stored in $CFGDIR, that contains the administrator's responses to the SETUP interview.
remote procedure call: When a program connects one another computer that
report user: One of the three license classes of users. Report users are restricted to running only options on the LeasePak [R] Reports menu.
role (disambiguation): The term role is used in a number of different contexts in LeasePak.

Sybase roles (System Security Officer, Database Owner)

Oracle roles (groups of privileges and roles, system privileges)

LeasePak roles ($NSTADMIN, $NSTDBA, $SRVADM, DBO, etc.)

Generally, in this System Administration Guide, role is referring to a LeasePak role, unless otherwise specified.
roll back: Typically the contents of a database are changed in batches, such that the end result is complete for the purpose. If a batch fails part way through, then the parts that were already completed are rolled back so that no inconsistencies remain due to the partially completed batch of modifications.
rolled back: See roll back.
root: This term has two meanings:

the root user is a user that is given full, unrestricted permissions to control a system

the top-most directory of a filesystem, or disk, aso known as /.
row: See database row.
RSC record: A row in the LeasePak RSC (user security) table. A user who has such a record is thus allowed to access LeasePak, with certain restrictions as inidicated by hte RSC. See also LeasePak security record.
RSC string password: The client string password is "hashed", or scrambled to become the RSC string password, which is used to gain access to LeasePak by a hosted user. See also translated password and lease /util 112.
runlevel: A Unix/Linux system has various runlevels that dictate what sorts of services are expected to be available. This helps organize the process of starting up a computer system.
Runtime LeasePak: LeasePak as it is installed at a NetSol client site. Cannot be used to develop or modify the product. It is a subset of Development LeasePak.
sa: The super user or root user of a Sybae database installation is called "sa". Typically functionality of this role is determined system design.
SAG: Acronym for the System Administration Guide.
schema: The term schema has two similar uses. The first is in Oracle, where the schema is the collection of objects that LeasePak calls an LLDB, called a database in Sybase. The second is in general discussions of relational databases, schema refers to the over-all layout of the data, indexes, procedures, etc. The LeasePak schema in this sense is the same in Oracle as it is in Sybase. There is even a generic data-definition language used in LeasePak implementation that presents a single set of terms for all the different types of data items, applicable to both DBMSes; these terms have consistent and documented equivalents in both Oracle and Sybase. Since the schema is identical between DBMSes, the server code by and large can remain unified, as long as the unified schema is used.
script: A script is a type of program, written in a textual programming language, such as sh or awk or perl, etc. These are considered to be text files, even though they may be executable. They are not compiled into binary programs like C or BASIC or COBOL might be, but remain as text. The basic structure of a script is that each line is potentially something that could be typed at a command prompt; the cumulative effect of those command lines is the effect of the script.

The individual command lines in the script are executed in sequence, unless special constructs (if,while, etc) direct the flow to some other command line.
security admin: A person responsible for administering the database's security authority.
security authority: The authority to change users' DBMS passwords is granted to the $SRVADM role. In order for a less privileged user to have this authority, perform the procedure at Granting Security Authority.
seed: One of the two default datasets provided by NetSol with the package. Its purpose is to create the basic foundation of a LLDB for a leasing enterprise. It contains the minimum information required by LeasePak to enable the first users of a new system to enter their own client-specific data, to initiate the implementation of LeasePak at a new site.
segmented BCP: Files in bcp format that are in separate files, but are in reality parts of a larger set of data. Segmented bcp files have a numeric suffix, that indicates the relative position of their contained date to the data in other bcp files. The numeric suffix takes the form of "." + the sequence number of the file within the larger sete of data.
semaphore file
server: A computer host that provides services for multiple users and processes. A computer program that provides services for multiple users and processes.
service: A capability or function offered by a computer system to other processes or systems.
server ID: The identifier by which the service is known, via a service directory, such as /etc/services or /etc/init.d.
service script: A script that initializes or controls a service.
SETUP: The LeasePak installer, which constructs needed directories, sets up various software resources then extracts the software from the LeasePak distribution media. Begins with an "interview" where the administrator is asked a number of questions, the answers to which determine how the package is deployed. The answers are stored in the directory $CFGDIR, in a file named relscfg.msirc.
setup_mew_env: NetSol-supplied script used to create and provision a fresh database environment, which can then be used to contain a LLDB, which can then contain local data.
shared memory: A facility provided by the IPC system. It allows two or more processes to access memory on the system as if it were part of the process's core memory.
shared port: Also called the proxy port. A TCP/IP port that has a LeasePak internet daemon, such as leasepakd, or mpowerd running on it. When leasepakd discovers that it is running on the shared port, it treats incoming connection requests as hosted users, and thus spawning drivers running under the proxy user's UID.
shared user: This is the name of the module that provides the proxy user, shared port, and hosted users. Sometimes used to refer to the proxy user.
sh: This is the Bourne Shell the original shell of Unix systems. There are actually two versions of sh: the traditional, original program from Bell Labs, and the modern, updated version called the POSIX shell. This is the form most oten seen nowadays. All of NetSol's scripts distributed with LeasePak, except for the cross-shell-compatible msirc shell start-up files are actually written in the POSIX shell.
shell: A shell is a command-line interpreter that provides a means of controlling the under-lying operating system. There are two methods for doing this: the first, interactively entered commands, typed by an operator, whose action is monitored by the operator, all in real time; the second, scripts, or batches of pre-prepared commands, are entered into text files, and then the shell could execute the commands sequentially at full speed, and the operators could review accumulated output from these batches and determine if the intended results were obtained.

In Unix and Linux, there are a number of shell utilities that have been written, some succrssful, and others perhaps less so. These include: sh, ksh, bash, csh, tcsh. Wikipedia lista 11 different shell programs in its article on operating system shell programs: Bourne shell (sh), POSIX shell, bash, csh, tcsh, Hamilton C shell, Scsh, ksh, pdksh, zsh, ash for Linux and Unix. None of these, besides sh, ksh, bash, csh, and tcsh, have been tested by NetSol.
shell access: In LeasePak administration, only certain users are allowed to log into the application host, and run an instance of a shell. This ability is called shell access. There are some requirements that must be met before a user can successfully be given shell access. The user must be a dedicated user, must have a true home directory, and must know the password for his Unix account. The user should have a basic knowledge of the operating system and of the shell, and an understanding of the tasks she is given this acess to perform.
shell-neutral: A shell-neutral script is one that will run correctly under either a csh type of shell or a sh type of shell. Shell-neutrality comes at a significant cost to the capabilities available to the programmer. Because csh is not widely used for general system maintenance, it was determined that shell-neutrality would require sh in separately executable scripts. Shell-neutral scripts are most often used in setting up other processes to use standardized environment values.
shell prompt: See command prompt.
shell start-up file: A configuration file read by a shell whenit is first initialized, providing additional data for its execution environment.
shutdown: To shutdown a computer system, the various processes and services that are running must be terminated, and allowed enough time to save unsaved work, and to perform orderly termination of record keeping, so that on the next boot, the services can begin in an orderly fashion.
snapshot: Another name for a dataset.
socket: A socket is a software construct that provides for programmatic access to networking capabilities. While using different keywords and semantics, sockets are like files in the final analysis: they can be opened and closed, and written to and read from, their features can be controlled.
split host: See split system.
split system: System design containing LeasePak server software and DBMS client software on one host (application host), and DBMS server software on a separate host (DBMS host). See also host.
SQL: Structured Query Language, a standardized language used to search and maintain the rows stored in relational databases. See sql programming language.
SQL*Loader: This is the Oracle data import utility, the equivalent of Sybase bcp.
sqlplus: The Oracle DBMS command-line interface utility.
SQL programming language: The native language of most modern relational database systems. SQL, or "Structured Query Language", provides a common API for extraction and modification of data stored in relational database systems. Each DBMS has its own dialect, differing some in terminology and differing more greatly in extensions added by the DBMS vendors. SQL is standarized by ISO/IEC 9075, although vendor extensions make portability difficult.
SQL server string password: The client string password password is scrambled or "hashed" to create the SQL server string password, which is used to authenticate a user within the database system that contains the LLDB.
SRVADM: See $SRVADM.
standard error: The accepted output channel on which a program should list its errors.
start-up file: A file that is read and processed by a program when the program begins to run. Usually used to configure the program's execution environment.
start_qmgr.com: A com-file that is normally executed from the nst_qm_{ID}99x script. It starts the system spooler jspctl.
start_queues.com: A com-file that is normally executed from the nst_qm_{ID}99x script. It starts the qmgr processes, one per queue, to manage them.
stop_qmgr.com: A com-file that is normally executed from the nst_qm_{ID}99x script. It stops the system spooler jspctl, which in turn tells the individual qmgr processes to terminate.
storage segment: A storage segment is a generic term that encompasses both Oracle tablespaces and Sybase devices. Each LLDB is physically built of one or more storage segments. See Storage Segments for details.
stored procedure: A stored procedure is a program written in the relational database's SQL programming language dialect that performs needful functions on behalf of the application code within the context of the LLDB. The compiled code of the procedure is stored in the LLDB itself, and is thus available for immediate execution at the command of the application.
strict naming: See also naming convention. Strict naming is a naming convention where various program and computer names are required to conform to certain patterns, which help to communicate to the user what type of object the name refers to. This is primarily inside the DBMS. The objects involved are roles, groups, databases, storage segments, and the like.
structured query language: See SQL programming language.
svcctrl: A NetSol-provided script that can be used on HP-UX and Solaris to provide the same funcionality as provided by the service and chkconfig commands in Linux. See the program header for more information at $ubin/svcctrl;
Sybase backup-server: The Sybase Backup Server, which is a part of the Sybase DBMS, used to perform native backups of the Sybase DBMS. Also known by the variable $SYBBKSRV.
symbolic link: A symbolic link is a file system redirector. Each symbolic link references another file (or possibly another link), and when itself is referenced, it is as if the reference is the file that it refers to. This enables the administrator to deploy a single file into multiple locations on the host, greatly reducing maintenance of separate copies.
sysdba: An Oracle role more or less equivalent to the Sybase sa or Unix root.
system administrator: The person in charge of managing the host(s) on which LeasePak and its database are installed. In the System Administration Guide often called simply "the administrator".
system spooler: Th program jspctl is the Queue Manager's controlling program. It directs the work of the individual queues.
table: A unit of storage within a relational database, consisting of one or more records containing the same column layout, such that the individual records contain comparable sets of data. Tables also feature indexes and triggers, as well as rows and columns.
tablespace: Oracle manages physical disk space via software constructs called "tablespaces". Each tablespace consists of one or more datafiles specially allocated for storage. Under LeasePak, any one Oracle LLDB can span only one tablespace. A single tablespace can support multiple LLDBs. However, additional disk space in the form of additional datafiles can be allocated to the LLDB's tablespace. See Storage Segments for details.
TCP/IP: The Transport Control Protocol / Internet Protocol. A common network standard using throughout the internet and many kinds of hardware. Used by LeasePak to connect LeasePak clients to LeasePak servers, to connect LeasePak servers to databases.
TCP port: TCP is an abbreviation for Transport Control Protocol which is the application programming side of the Internet's TCP/IP communications system. The TCP protocol provides, in addition to sockets, the concept of a port. There are 65,535 possible ports on a server under TCP. Many are preallocated to specific purposes, FTP, NFS, etc. Some are not allocated. Among the many allocated ports, there are a number that are not in use, even though allocated. LeasePak and mPower allocate ports based on the release number, for example, 6400 for v64a, and 6500 for v65a. If these assignments are causing conflict with other packages, then the administrator will have to redirect the conflicting software, or give different numbers for LeasePak in SETUP.
tcsh: A derivative of the csh shell.
TERM: See $TERM.
terminal: A hardware device that communicates with a computer server, providing the keyboard for making computer inputs and displaying the output.
terminal emulation: That which is done by a terminal emulator.
terminal emulator: A program that communicates with a server or other process, usually providing a simple keyboard and display connection, in emulation of a real hardware terminal.
terminal type: Each terminal is of a particular type, whih governs how the terminal behaves, what codes it requires to perform basic text formatting, what codes cause it to switch display widths, clear the screen, display inverse video, etc. The server communicating with the terminal must know what type of terminal it is. The industry has produced a standard list of terminal type abbreviations. In Unix/Linux, there is an environment variable $TERM (or $term) set with the terminal type. The LeasePak server software will not operate in the absence of this variable, and its value is restricted to one of those listed in ERROR: INVALID SHORTHAND LINK IDENTITY
terminators.txt: This file resides in $CFGDIR. NetSol ships this file with LeasePak configured to avoid conflict with LeasePak data. This file designates the field and record terminators to be used in constructing export files. It is copied into the dataset, at the start of the db_snapshot process so that db_restore can decode the export files. At the site the $NSTADMIN can tailor these terminators to suite site preferences. This must be done carefully and with adequate knowledge of the data content of the export files, as the data may prove to be irretrievable if the delimiters conflict with the data in a snapshot.
test: A type of LeasePak environment. Has slightly more liberal permissions. Used for putting up small datases and trying scenarios for training, debugging and documentation.
test environment: LeasePak environment that can link to drivers in different LeasePak builds or drivers in $live. Typically ties to a LeasePak database (LLDB) containing test data.
text: Sybase DBMS long-length character string. Used only for the info_s columns in the Notebook tables.
TIMESTAMP(3): Oracle DBMS date and time. Contains century, year, month, day, hour, minute, second, and second fraction (accurate to 1/1000 second) information. LeasePak uses both the date and time portions. If the datatype of a column is TIMESTAMP(3), the column name begins with 'dt_'.
timestamp: Sybase DBMS binary timestamp. Whenever a table includes a timestamp column, Sybase automatically updates the binary time information in the timestamp column each time a user inserts or updates the record. LeasePak uses the timestamp information to prevent corruption when multiple users attempt to update the same record simultaneously.
TOPDIR: See $TOPDIR
top directory: See $TOPDIR.
transaction log: The transaction log is used by DBMSes to provide fault tolerance and recoverability. This works by the DBMS recording the transactions that it is working on. In event of a system failure, the log can be examines and transactions marked as complete in the log can be repeated if the database does not agree, and transactions that are not complete can be reversed, or rolled back. The end result is a definitive condition of the data in the database, and being able to assure the users that the database reflects completed work only.
translated password: The client string password is scrambled or translated in such a way that it is impossible to reliably reconstruct the original client string from the scrambled result. This allows passwords to be transmitted over a network without security concerns. LeasePak uses the client string password to generate the Unix string password and SQL server string password versions that are used to authenticate the user to the LeasePak host and to the LLDB.
trigger: A piece of code, written in the SQL programming language, that is executed ('fired' or 'triggered') by the DBMS when one or more records is modified by an application program issuing an insert, update or delete command. The trigger code may perform any needful task, focused primarily on maintaining the consistency of the data stored in the database. Such tasks include updating, inserting or deleting records related to the record being modified by the application. For example, when a LeasePak application record is modified such that its status changes, the update of the Application record triggers the insertion of a new application status history record.
U0706: See [U0706] Security.
ubin: See $ubin.
udata: See $udata
udsets: See $udsets.
UID: This is an acronym for user identifier. It is the Unix user's unique identifier, by which the host systems know the user. The username is just a symbolic construct that the host translates to the real ID, the UID, and back again. If two systems have users with the same name, this does not mean they are the same user. Only if their UIDs match does the OS regard them as the same user.
unified host: See unified system
unified system: System design containing LeasePak server software, DBMS client software, and DBMS server server software on the same host (combined host).
UNIX: The UNIX operating system was developed in the 1970's at AT&T's Bell Labs. UNIX is a trademark of AT&T, but is used generically throughout the industry to categorize a wide array of computer operating systems that have been derived from or based upon UNIX. All host systems that are used by LeasePak run some variety of a UNIX-like operating system. See also Linux.
Unix account: A user who is to access a unix host must have an account, that is, be a registered user, with the DBMS. This account is created by the utility useradd on most systems. A user who has an account on a host, is said to be a Unix user. Having the Unix account does not give a user access to LeasePak software, that action requires further setup.
Unix start-up file: See shell start-up file.
Unix string password: The client string password password is "hashed", or scrambled to become the Unix string password, which is used to gain access to a host that LeasePak is installed on. See also translated password.
Unix user: A person or role that has an account to access a UNIX or Unix-like host system. All LeasePak users, except for some database system administrative users are Unix users. For LeasePak purposes, all OS users are Unix users.
useradd: A native Unix utility program that handles inserting and editing entries in the Unix /etc/passwd file.
user name: The user name is noted in one or more of the following: /etc/passwd, a DBMS user table, LeasePak's RSC table. Each user is given a unique UID within /etc/passwd.
user security reoord: See LeasePak security record.
utility: A application program that provides a means to manipulate, create, or delete files, systems and services on a host. Most software packages include their own utilities, which are generally available to administrators and users. Thus there are Unix and Linux utilities, DBMS (Sybase or Oracle) utilities, Queue Manager utilities and LeasePak utilities on a host used for LeasePak.
utility script: LeasePak utility software mostly consists of proprietary scripts created by NetSol. Some utilities are binary programs from NetSol and NetSol's partners.
VARCHAR2(length): Oracle DBMS variable-length character string. Used for non-indexed strings over 19 characters in length. length denotes the maximum number of characters the string can contain.
vi: vi (called vim on Linux) is a sophisticated full-screen text editor. While it can be quite complicated, its basic command set is very simple and easy to learn. It is designed to work with almost any kind of character terminal. It is particularly sensitive to the value of $TERM.
view: A view is a database structure that consists of selected columns from one or more tables, presented by the DBMS as if it were a table in its own right. Is very light-weight as it really consists of just a fixed query of one or more tables, without storage of its own and no indexes. May be freely used in stored procedures and triggers as well as in application code as if it were a table.
visitor: See visitor environment.
visitor environment: LeasePak environment that ties to a LeasePak database (LLDB) through its connection to a host environment. Can link to drivers in different LeasePak builds, drivers in $live, or drivers determined by its host.

flag position	Service to be installed
1	Queue Manager init service
2	Not used
3	Oracle init service
4	Sybae init service
5	leasepakd internet service
6	mpowerd internet service