LeasePak

Server Configuration and Maintenance

Start here if you have finished installing or upgrading LeasePak and need to perform additional configuration or maintenance on your server. If you are installing LeasePak for the first time, refer to the document LeasePak Server Preparation and Installation. If you are upgrading or updating LeasePak, refer to LeasePak Server Upgrade and Conversion.

Configuration
- Sector7
- Printer
- Environment and Database
- LeasePak Administrative User
- Registration Codes
Maintenance

Configuration

Sector7

Parameters

Configure Sector7 parameters in the file Config (the file name begins with an uppercase C). You can find this file in /opt/sector7/s7_version/library (or your equivalent), where version is the version of Sector7 appropriate for your platform.

The top and subdirectories of Sector7 must not include hidden directories--that is, directories that begin with a dot or period (.), directory names containing a dot or period, directory names containing uppercase letters, or directories that cross physical drives or mount points.

To edit Config

Log on the server as msiadmin
Terminal emulation: you must use one of the supported terminal types. Refer to the Terminal Emulation section of the document System Requirements for more information.
If the batch or print queues are already set up and running, stop the queues before making any changes
dcl -n /opt/sector7/s7_version/com/stop_qmgr.com
Use vi or other editor to edit the file /opt/sector7/s7_version/library/Config (the file name begins with an uppercase C). Locate and edit the following parameters

SYSTEM

Shared memory key. Change this to allow multiple Sector7 versions on your system. If there are multiple installations of Sector7, this must be unique for each installation. Shared memory keys should be spaced at intervals of at least 1000.

When configuring shared memory in Sybase, reserving 100 MB for Sector7 is sufficient and will allow for up to three concurrent installations of the program, if needed.

MAXDEV

Maximum number of devices to map. May need to change if you have many terminals or pseudo-terminals.

MAXJOB

Number of Sector7 jobs. This should be set to two times the number of concurrent users, plus four times the job limit for each batch queue, plus one for each print queue.

BINDIR

Usually /opt/sector7/s7_version/bin

LIBDIR

Usually /opt/sector7/s7_version/a

SYS$SYSTEM

Unix/Linux path of the Sector7 bin directory. Usually /opt/sector7/s7_version/bin

SYS$LIBRARY

Unix/Linux path of the Sector7 library directory. Usually /opt/sector7/s7_version/library

SYS$MESSAGE

Unix/Linux path of the Sector7 message directory. Usually /opt/sector7/s7_version/message

SNDOPRLOG

Unix/Linux path to store Sector7 SNDOPR log file. Usually /tmp/sector7/

LNMDIR

Unix/Linux path to store Sector7 Logical Name temporary files. Usually /tmp/sector7/

SORTDIR

Unix/Linux path of Sector7 sort files. Usually /tmp/sector7/

MBXDIR

Unix/Linux path of Sector7 mailbox directory. Usually /tmp/sector7/

JSPDIR

Unix/Linux path to directory of the Sector7 spool directory. Usually /opt/sector7/s7_version/spool

BATCH_INTERVAL

Time interval between scans of the queues for new jobs. Default is 15 seconds, with a range of 1 to 60 seconds.

BATCH_PRIORITY

The Unix/Linux base priority of the batch queue jobs. The default is 20 (same as ordinary jobs). This can range from 0 to 40, with 0 being the highest priority. Setting it lower than 20 will affect other jobs on the system.

DCLDIR

Unix/Linux path of Sector7 directory for DCL commands. Usually /opt/sector7/s7_version/bin

Batch Queues

LeasePak primarily uses batch queues during End of Period processing. Configure batch queues in the file start_queues.com, located in /opt/sector7/s7_version/com. LeasePak requires configuration of sys$batch. MSI recommends setting up a separate batch queue for each portfolio, as each portfolio should use a different queue for its End of Period processing.

To edit start_queues.com

Log on the server as msiadmin
Terminal emulation: you must use one of the supported terminal types. Refer to the Terminal Emulation section of the document System Requirements for more information.
If the batch or print queues are already set up and running, stop the queues before making any changes
dcl -n /opt/sector7/s7_version/com/stop_qmgr.com
Use vi or other editor to edit the file /opt/sector7/s7_version/com/start_queues.com
```
$ if P1 .eqs. "" then P1 = 1
$ init/que/start/job_limit='P1'/batch sys$batch
$ init/que/start/job_limit='P1'/batch lp$eop1
$ init/que/start/job_limit='P1'/batch lp$eop2
$ wait 5
$ init/que/start/job_limit='P1'/batch lp$eop3
$ init/que/start/job_limit='P1'/batch lp$eop4
```
init/que

DCL initialize queues command. Creates the batch queue.

start

You must use the start parameter for queues to be ready to run jobs.

job_limit

Specifies how many jobs can run on the queue simultaneously. Values range from 1 to 255. Consult your MSI representative when setting this parameter. Too low a number will slow End of Period processing, while too high a number may consume excessive resources on the server.

batch

Type of queue to initialize. For batch queues, this is batch

sys$batch

DCL default batch queue. Do not remove.

lp$eop

Format lp$eopn, where n is the portfolio number. Conventional name for a portfolio's End of Period batch queue.

wait

Format wait n, where n is the number of seconds to wait. Insert a wait command after every three init/que commands to ensure that all queues are initialized by the time start_queues.com is finished.

If you are using this section to perform additional Sector7 configurations--that is, you have already completed the required configurations for LeasePak, you can now restart the queues. As msiadmin, use the following two commands to first start the queue manager, then start the queues

dcl -n /opt/sector7/s7_version/com/start_qmgr.com

dcl -n /opt/sector7/s7_version/com/start_queues.com

For more information about starting and stooping queues, refer to the System Restart section of this document.

Printer Configuration

Your printer must be able to print 132-column output in order to print LeasePak reports.

When a user prints a report in LeasePak, Sector7 directs the print job to an emulated VMS-style printer queue, then maps the printing instructions to a Unix/Linux lp command, so that the Unix/Linux print spooler handles the actual printing.

To set up the printer, first define the printer on your server OS, then use the DEVINIT, Config, and start_queues.com files to define the printer in Sector7.

Printer Name

LeasePak printer names must contain only lowercase letters (a-z) or numbers (0-9). Do not use an underscore ( _ ) in the name. In the following examples, assume there is a printer on the third floor of your office you will name 3fp.

Printer Installation and OS Configuration

Install the printer according to the manufacturer's instructions and connect it to the server, by either a direct (parallel or serial) or network connection. Logged on the server as root, define the printer using an administrative tool or direct commands. Verify that the system is ready to accept new print requests, the print queue is enabled, and the spooler is running, then test the printer

lp -d3fp file

where the -d option specifies the destination (name of printer) and file is any text file (with directory path if necessary).

DEVINIT

The DEVINIT file defines VMS-style pseudo-devices for disks, printers, magnetic tape, and null devices. The file name is all uppercase.

To edit DEVINIT

Log on the server as msiadmin
Terminal emulation: you must use one of the supported terminal types. Refer to the Terminal Emulation section of the document System Requirements for more information.
If the batch or print queues are already set up and running, stop the queues before making any changes
dcl -n /opt/sector7/s7_version/com/stop_qmgr.com
Use vi or other editor to edit the file /opt/sector7/s7_version/library/DEVINIT
```
DUA0:    /               DK      512
NL:      /dev/null       NL      10240
LP:      /dev/lp         LP      512
LP3FP:   /dev/null       LP      512
LP3FPL:  /dev/null       LP      512
LPBH:    /dev/null       LP      512
LPSP:    /dev/null       LP      512
```
(column 1)

Column 1 contains the Sector7 pseudo-device name. For each printer (other than the default LP), there are usually two listings--one for portrait printing and one for landscape. Pseudo-device names are always all uppercase and must be unique. Sector7 requires the entries for DUA0 (the disk device) and NL (the null device), and LeasePak requires an entry for the paperless print queue (LPBH). The above example includes entries for the sample printer 3fp, LP3FP (portrait) and LP3FPL (landscape).

(column 2)

Column 2 contains the full path of the corresponding Unix/Linux device. Since LeasePak print jobs are passed through to the Unix/Linux print spooler, all Sector7 printer pseudo-devices are mapped to the Unix/Linux device /dev/null.

(column 3)
Column 3 specifies the device type:
- DK disk
- LP printer
- MD media (tape drive)
- NL null
(column 4)

Column 4 specifies an internal buffer size (for VMS emulation purposes only - this number is ignored by Unix/Linux).

Config

The Config file contains the parameters Sector7 uses to map printers to their corresponding Unix/Linux lp commands.

To edit Config

Log on the server as msiadmin
Terminal emulation: you must use one of the supported terminal types. Refer to the Terminal Emulation section of the document System Requirements for more information.
If the batch or print queues are already set up and running, stop the queues before making any changes
dcl -n /opt/sector7/s7_version/com/stop_qmgr.com
Use vi or other editor to edit the file /opt/sector7/s7_version/library/DEVINIT. Locate the listings for the Sector7 printer devices and their corresponding Unix/Linux commands by searching for the pattern LP. The required options for these listings will vary depending on your type of printer and which drivers you have installed.
This is an example using an HP LaserJet printer with HP JetDirect
```
LP3FP:  /usr/bin/lp -d3fp -odouble -otl66 -oc -c -s 2>>/tmp/sector7//LP3FP_ERR < %s
LP3FPL:  /usr/bin/lp -d3fp -odouble -olandscape -ofp12.5 -otl46 -c -s 2>>/tmp/sector7//LP3FPL_ERR < %s
LPSP:  /usr/bin/lp -dsysprint -s 2>>/tmp/sector7/SYSPRINT_ERR < %s
LPBH:  :
```
This is an example using Postscript
```
LP3FP:  /usr/bin/a2ps -P 3fp --columns=1 --rows=1 --portrait --chars-per-line=132 --major=rows -SDuplex:false -B --borders=no --medium=Letter 2>>/tmp/sector7//LP3FP_ERR < %s
LP3FPL:  /usr/bin/a2ps -P 3fp --columns=1 --rows=1 --landscape --chars-per-line=132 --major=rows -SDuplex:false -B --borders=no --medium=Letter 2>>/tmp/sector7//LP3FPL_ERR < %s
LPSP:  /usr/bin/a2ps -P sysprint 2>>/tmp/sector7/SYSPRINT_ERR < %s
LPBH:  :
```
The syntax for mapping a normal printer device is

S7DEVICE: command printer_name options error_output < %s

The syntax for mapping the paperless queue device is

LPBH: :

Copy the pseudo-device names exactly from the DEVINIT file. If the printer has both portrait and landscape devices, create two configurations--one for portrait printing and another for landscape printing. Use whatever print command options are necessary to produce 132-column output with your particular printer(s). One of the print command options must specify that the spooler make a copy of the file to be printed. This ensures all files will be printed, particularly in the case where the user is running many reports of the same type, such as multiple Lease Inquiry [R0905] reports. If needed, contact your MSI representative for assistance with mapping your printers.

start_queues.com

This file, located in /opt/sector7/s7_version/com, contains the commands for initializing the printer queues as well as the batch queues.

To edit start_queues.com

Log on the server as msiadmin
Terminal emulation: you must use one of the supported terminal types. Refer to the Terminal Emulation section of the document System Requirements for more information.
If the batch or print queues are already set up and running, stop the queues before making any changes
dcl -n /opt/sector7/s7_version/com/stop_qmgr.com

Use vi or other editor to edit the file /opt/sector7/s7_version/com/start_queues.com.

The first section of the file contains the initializations for portrait and landscape documents

$ define/form default 0 -
  /description="Portrait Compressed Letter Document" -
  /Length=66 -
  /margin=(Bottom=6,Top=6, Left=10, Right=10) -
  /stock=default -
  /truncate -
  /width=132
$ define/form landscape 50 -
  /description="Landscape Letter Document" -
  /Length=46 -
  /margin=(Bottom=6,Top=6, Left=10, Right=10) -
  /stock=default -
  /truncate -
  /width=132

Do not alter the parameters in this section. Contact your MSI representative for more information.

Farther down the file, you will find the printer queue initializations
```
$ init/que/start/form=default/on=LP3FP: sys$print
$ init/que/start/form=landscape/on=LP3FPL: csl$print
$ init/que/start/form=default/on=LPBH: sys$blackhole
$ wait 5
```
init/que

DCL initialize queues command. Creates the printer queue.

start

You must use the start parameter for queues to be ready to run jobs.

form

For a portrait printer device, use form=default. For a landscape printer device (such as the example LP3FPL), use form=landscape.

on

Set to the Sector7 printer pseudo-device name, followed by a colon (:). The pseudo-device name is all uppercase.

sys$batch, csl$print, sys$blackhole
DCL printer queue names. You can specify queue names using the following rules
- the queue name can include letters (a-z), numbers (0-9), the dollar sign ($), and the underscore ( _ )
- the name can be up to 31 characters in length
- begin the name with a letter or number
- include at least one letter in the name
- for letters, use all lowercase
wait

Format wait n, where n is the number of seconds to wait. Insert a wait command after every three init/que commands to ensure that all queues are initialized by the time start_queues.com is finished.

dcl -n /opt/sector7/s7_version/com/start_qmgr.com

dcl -n /opt/sector7/s7_version/com/start_queues.com

For more information about starting and stopping queues, refer to the System Restart section of this document.

Environment and Database Configuration

setup_new_env

Use the setup_new_env script to create new production, test, and Visitor environments.

Example: these are the two most common examples of setup_new_env.

setup_new_env [-[ncf]] env-name db-type db-server db-name

for production environments, where env-name is the environment the new database will be associated with, db-type is either ora for Oracle or syb for sybase, db-server is the the DBMS server, and db-name is the database name. You will be prompted for the srvadm password and, if necessary, the dbo name and password.

setup_new_env -tl env-name db-type db-server db-name build-descriptor

(the options are the letters t and l) for test environments, where build-descriptor is either live, host, or an actual build number bldn.nn.nnnn (for example, bld.0000). You will be prompted for the srvadm password and, if necessary, the dbo name and password.

Sybase only: for more information on dbo names and passwords, refer to the Database Owner section of Sybase 12.x Server.

Syntax

production	setup_new_env [-[ncf]] env-name db-type db-server db-name
test	setup_new_env -t[blncf] env-name db-type db-server db-name build-descriptor
visitor	setup_new_env -v[bln] env-name host-env build-descriptor

Options

Flag	Description	Notes
-c	closed to visitor	Without this option, environment is open to visitors.
-b	build-id used for `live`	Without this option, `live` is used for `live`.
-f	foreign (non-LeasePak) database	Without this option, environment contains a LeasePak database
-l	links used to populate `exe` directory	Without this option, `exe` is a link to the `exe/$DBMS` directory in build.
-n	no client information display	Without this option, environment displays client information.
-t	test environment	Requires build-descriptor. Without this option, environment is production type.
-v	visitor environment	Requires build-descriptor. Without this option, environment is production type.

The -b option tells the environment to link directly to the build that live is linked to. That way, even if live changes to another build, the environment will still use the build live pointed to when the environment is created. Otherwise, the environment will point to live and will use whatever build live points to at the time.

Arguments

env-name: Your name for the environment. An environment name must be unique within the specific LeasePak installation. For environment naming conventions, including requirements and restrictions, refer to the document Naming Conventions.
db-type: Use ora for Oracle or syb for Sybase.
db-server: DBMS server name corresponding to this installation of LeasePak.
db-name: Database names must be unique for the specific LeasePak installation and comply with your selected type of naming conventions. For more information on naming conventions, refer to Naming Conventions.
host-env: For visitor environments, the actual environment serving as the host.
build-descriptor: For test and visitor environments, either live, host, or an actual build number bldn.nn.nnnn (for example, bld.0000).

Configuration Worksheet

Note the following values for running setup_new_env:

Description	Example	Notes
env-name (environment name)		Must be unique for the specific LeasePak installation.
db-type (database type)	(database-specific)	`ora` for Oracle or `syb` for Sybase.
db-server (database server name)	(database-specific)
db-name (database name)	(database-specific)	Database names must be unique for the specific LeasePak installation and comply with your selected type of naming conventions. For more information on naming conventions, refer to Naming Conventions.
host-env (host environment)		For Visitor environments only.
build-descriptor		For Test and Visitor environments only.

Environment Configuration

To create and configure a new environment, use setup_new_env

Log on the server as msiadmin
Terminal emulation: you must use one of the supported terminal types. Refer to the Terminal Emulation section of the document System Requirements for more information.
Using the syntax and options described above, run setup_new_env

Example: these are the two most common examples of setup_new_env.

setup_new_env [-[ncf]] env-name db-type db-server db-name

setup_new_env -tl env-name db-type db-server db-name build-descriptor

Sybase only: for more information on dbo names and passwords, refer to the Database Owner section of Sybase 12.x Server.

change_env

Log on the server as msiadmin and use the command change_env to change another user (other than msidba) to a different version or environment of LeasePak. You can no longer use change_env to change the environment of msiadmin or msidba. The script will prompt (one line at a time)

Enter LeasePak version []:
Enter environment [environment]:

Type a new value and press Enter or simply press Enter to leave the value unchanged. The user must exit and log back on for the changes to take effect.

whatami

Log on the server as the user to verify, then use the script whatami to confirm your current working environment and version of LeasePak.

db_create

Do not create a database in the administrative environment (either adm_ora or adm_syb).

The msidba user runs the script db_create to create a new LeasePak database for a particular environment

db_create env-name [-[pbocs] [new-dbo-passwd [srvadm-password]]

Example: this is the most common example of db_create.

db_create env-name

where env-name is the environment the new database will be associated with. You will be prompted for the srvadm password and, if necessary, the dbo name and password.

Sybase only: for more information on dbo names and passwords, refer to the Database Owner section of Sybase 12.x Server.

Options

Flag	Description	Notes
-p	selects physical storage units for database (`db_setup_phys`)	required for new databases
-b	builds new database on the physical storage units (`db_build`)	required for new databases
-o	loads tables, indexes, and views (`db_load_obj`)	required for new databases
-c	loads packages, procedures and triggers (`db_load_code`)	required for new databases
-s	grants access to various objects (`db_set_security`)	required for new databases

Arguments

env-name: The environment this database will be paired with. You must set up the environment before you can create its database.
new-dbo-passwd: The password of the database owner (dbo) for this database. The dbo name is the same as the database/schema. If omitted, the dbo password defaults to the srvadm password. Create a new password for the dbo.
srvadm-password: The password of the DBMS server administrator (srvadm) user.

Database Configuration

To run db_create

Log on the server as msidba
Terminal emulation: you must use one of the supported terminal types. Refer to the Terminal Emulation section of the document System Requirements for more information.

Using the syntax and options described above, run db create.

Example: this is the most common example of db_create.

db_create env-name

where env-name is the environment the new database will be associated with. You will be prompted for the srvadm password and, if necessary, the dbo name and password.

Sybase only: for more information on dbo names and passwords, refer to the Database Owner section of Sybase 12.x Server.

The script will display the physical data and log devices and how much space (in megabytes) is available in each, then prompt you (one line at a time) to select devices and sizes for the data and log segments

-03-16 16:20:22 db_setup_phys: Set up physical storage description for lpr_ship_syb in ship-syb

Storage segments with available space:
           msi_log01   23                         msi_data08   1748
           msi_log02   30                         msi_data09   4095
           msi_log04   2822                       msi_data12   4095
          msi_data04   6                          msi_data13   4095
          msi_data05   1476

[<RET>/Q/q]=quit  [R/r]=redisplay list  [V/v]=view physdb.msirc
Enter Segment name from list above: 50 
 Enter # MBs required from segment: msi
 Segment type: 'D[ATA]' or 'L[OG]': x
Invalid segment 50

[<RET>/Q/q]=quit  [R/r]=redisplay list  [V/v]=view physdb.msirc
Enter Segment name from list above: msi_log04
 Enter # MBs required from segment: 50
 Segment type: 'D[ATA]' or 'L[OG]': l

[<RET>/Q/q]=quit  [R/r]=redisplay list  [V/v]=view physdb.msirc
Enter Segment name from list above: msi_data05
 Enter # MBs required from segment: d
 Segment type: 'D[ATA]' or 'L[OG]': d
Segment size D is invalid for segment msi_data05

[<RET>/Q/q]=quit  [R/r]=redisplay list  [V/v]=view physdb.msirc
Enter Segment name from list above: v
Current contents of physdb.msirc:
setenv  MSIDB_SEG01     "msi_log04,50,LOG"


[<RET>/Q/q]=quit  [R/r]=redisplay list  [V/v]=view physdb.msirc
Enter Segment name from list above: msi_data05
 Enter # MBs required from segment: 150
 Segment type: 'D[ATA]' or 'L[OG]': d

[<RET>/Q/q]=quit  [R/r]=redisplay list  [V/v]=view physdb.msirc
Enter Segment name from list above: v
Current contents of physdb.msirc:
setenv  MSIDB_SEG01     "msi_log04,50,LOG"
setenv  MSIDB_SEG02     "msi_data05,150,DATA"


[<RET>/Q/q]=quit  [R/r]=redisplay list  [V/v]=view physdb.msirc
Enter Segment name from list above: q
Current contents of physdb.msirc:
setenv  MSIDB_SEG01     "msi_log04,50,LOG"
setenv  MSIDB_SEG02     "msi_data05,150,DATA"

-03-16 16:22:10 db_setup_phys: New physical configuration of database lpr_ship_syb stored in $TOPDIR/env/ship-syb/etc/physdb.msirc

Type values for the data and log segments and press Enter. Specify sizes in megabytes. In most cases, LeasePak requires approximately 60 K for each lease.

Use different devices for the data and log segments. Do not create data or log segments on any device used by the DBMS for its system databases, schemas, or tables.

The script will create the database (this can take up to 10 minutes). The following is a complete example of what the terminal will display (your display will be slightly different)

-09-21 10:47:56 db_setup_phys: New physical configuration of database lpr_test stored in $TOPDIR/env/test/etc/physdb.msirc
-09-21 10:47:56 db_build: Build (test)lpr_test
-09-21 10:47:56 db_build: Running commands as srvadm
-09-21 10:47:57 db_build: Constructing logical LeasePak database...
-09-21 10:49:53 db_set_dbo: Start
-09-21 10:49:53 db_set_dbo: Creating new login account for lpr_test ...
-09-21 10:49:54 db_set_dbo: Changing DBO of test to lpr_test ...
-09-21 10:49:55 db_set_dbo: End
-09-21 10:49:55 db_build: End

-09-21 10:49:55 db_load_obj: Load logical database objects in lpr_test for test
-09-21 10:49:55 db_load_obj: Running commands as DBO, lpr_test
Xmap: tbl(vertex) tbl(mcml) tbl(mcmu) tbl(mja) tbl(raa) tbl(rab) tbl(rac) 
Xmap: tbl(rad) tbl(radr) tbl(raf) tbl(rag) tbl(rai) tbl(raia) tbl(ral) 
Xmap: tbl(rale) tbl(rap) tbl(rapa) tbl(rapd) tbl(raph) tbl(rapp) tbl(rapr) 
Xmap: tbl(raps) tbl(raq) tbl(raqc) tbl(raqu) tbl(rar) tbl(rarb) tbl(ras) 
Xmap: tbl(rase) tbl(rau) tbl(rax) tbl(raxp) tbl(raxr) tbl(rba) tbl(rbc) 
Xmap: tbl(rbd) tbl(rbi) tbl(rbk) tbl(rbl) tbl(rblt) tbl(rbp) tbl(rbr) 
Xmap: tbl(rbs) tbl(rca) tbl(rcc) tbl(rcd) tbl(rce) tbl(rcf) tbl(rcfa) 
Xmap: tbl(rcfb) tbl(rcg) tbl(rcga) tbl(rcgb) tbl(rcgf) tbl(rcgg) tbl(rcgl) 
Xmap: tbl(rcgu) tbl(rcgv) tbl(rcgw) tbl(rcgx) tbl(rcgy) tbl(rcgz) tbl(rch) 
Xmap: tbl(rck) tbl(rco) tbl(rcp) tbl(rcr) tbl(rcs) tbl(rcu) tbl(rcx) 
Xmap: tbl(rdc) tbl(rdcd) tbl(rdf) tbl(rdg) tbl(rdh) tbl(rdl) tbl(rdm) 
Xmap: tbl(rdmi) tbl(rdq) tbl(rdr) tbl(rdrp) tbl(rdrq) tbl(rdt) tbl(rdu) 
Xmap: tbl(rep) tbl(repe) tbl(req) tbl(reqa) tbl(reqc) tbl(requ) tbl(rer) 
Xmap: tbl(res) tbl(rex) tbl(rfa) tbl(rfl) tbl(rfs) tbl(rfu) tbl(rfx) 
Xmap: tbl(rgc) tbl(rgg) tbl(rgl) tbl(rglc) tbl(rgr) tbl(rha) tbl(rhab) 
Xmap: tbl(rhe) tbl(rhh) tbl(rhl) tbl(rho) tbl(rhp) tbl(rhq) tbl(rhqa) 
Xmap: tbl(rhqc) tbl(rhqu) tbl(rhr) tbl(rhs) tbl(rhsa) tbl(rhsb) tbl(rhsc) 
Xmap: tbl(rhsp) tbl(rhsr) tbl(rhss) tbl(rht) tbl(rhx) tbl(rhy) tbl(rid) 
Xmap: tbl(rig) tbl(rin) tbl(rip) tbl(ris) tbl(rkp) tbl(rkr) tbl(rle) 
Xmap: tbl(rlec) tbl(rlh) tbl(rli) tbl(rll) tbl(rlo) tbl(rlr) tbl(rls) 
Xmap: tbl(rlsa) tbl(rlsb) tbl(rlsc) tbl(rlsp) tbl(rlsr) tbl(rlss) tbl(rlt) 
Xmap: tbl(rmf) tbl(rmfp) tbl(rmp) tbl(rmt) tbl(rna) tbl(rnc) tbl(rnh) 
Xmap: tbl(rnl) tbl(rnm) tbl(rno) tbl(rnon) tbl(rnp) tbl(rns) tbl(rnt) 
Xmap: tbl(roa) tbl(rop) tbl(rpa) tbl(rpar) tbl(rpay) tbl(rpaz) tbl(rpc) 
Xmap: tbl(rpd) tbl(rpf) tbl(rpfa) tbl(rph) tbl(rpha) tbl(rpi) tbl(rpl) 
Xmap: tbl(rpm) tbl(rpn) tbl(rpo) tbl(rpp) tbl(rpr) tbl(rps) tbl(rpsp) 
Xmap: tbl(rpu) tbl(rpw) tbl(rpx) tbl(rpy) tbl(rpz) tbl(rqm) tbl(rqp) 
Xmap: tbl(rqs) tbl(rqt) tbl(rqtr) tbl(rqu) tbl(rqy) tbl(rqz) tbl(rrf) 
Xmap: tbl(rrg) tbl(rrgc) tbl(rrp) tbl(rrpf) tbl(rrr) tbl(rrrp) tbl(rrrq) 
Xmap: tbl(rru) tbl(rsa) tbl(rsb) tbl(rsc) tbl(rsf) tbl(rsfs) tbl(rsh) 
Xmap: tbl(rsp) tbl(rsq) tbl(rsr) tbl(rst) tbl(rsu) tbl(rtd) tbl(rtl) 
Xmap: tbl(rtm) tbl(rtmn) tbl(rtn) tbl(rtp) tbl(rtr) tbl(rtx) tbl(rty) 
Xmap: tbl(rtz) tbl(rua) tbl(rub) tbl(rubt) tbl(ruc) tbl(rud) tbl(rue) 
Xmap: tbl(ruet) tbl(ruf) tbl(rug) tbl(ruh) tbl(ruht) tbl(ruj) tbl(ruk) 
Xmap: tbl(rukt) tbl(rum) tbl(run) tbl(runt) tbl(ruo) tbl(ruq) tbl(ruqt) 
Xmap: tbl(rur) tbl(rus) tbl(rust) tbl(rut) tbl(rvd) tbl(rwt) tbl(rxf) 
Xmap: tbl(rxp) tbl(rxu) tbl(ryr) tbl(rza) tbl(rzg) tbl(rzga) tbl(rzp) 
Xmap: tbl(rzq) tbl(rzu) tbl(mjc) tbl(mjl) tbl(mlo_city) tbl(mlo_county) tbl(mlt) 
Xmap: tbl(mpa_assmt) tbl(msg) tbl(msvb) tbl(msvc) tbl(msvh) tbl(msvi) tbl(msvl) 
Xmap: tbl(msvr) tbl(msvs) tbl(msvu) tbl(msvv) tbl(mvd_mdl) tbl(mvd_mnf) tbl(mwa) 
Xmap: tbl(mwc) tbl(mwi) tbl(mwk) tbl(mwm) tbl(mwr) tbl(mws) tbl(mxd) 
Xmap: idx(vertex) idx(mcml) idx(mcmu) idx(mja) idx(raa) idx(rab) idx(rac) 
Xmap: idx(rad) idx(radr) idx(raf) idx(rag) idx(rai) idx(raia) idx(ral) 
Xmap: idx(rale) idx(rap) idx(rapa) idx(rapd) idx(raph) idx(rapp) idx(rapr) 
Xmap: idx(raps) idx(raq) idx(raqc) idx(raqu) idx(rar) idx(rarb) idx(ras) 
Xmap: idx(rase) idx(rau) idx(rax) idx(raxp) idx(raxr) idx(rba) idx(rbc) 
Xmap: idx(rbd) idx(rbi) idx(rbk) idx(rbl) idx(rblt) idx(rbp) idx(rbr) 
Xmap: idx(rbs) idx(rca) idx(rcc) idx(rcd) idx(rce) idx(rcf) idx(rcfa) 
Xmap: idx(rcfb) idx(rcg) idx(rcga) idx(rcgb) idx(rcgf) idx(rcgg) idx(rcgl) 
Xmap: idx(rcgu) idx(rcgv) idx(rcgw) idx(rcgx) idx(rcgy) idx(rcgz) idx(rch) 
Xmap: idx(rck) idx(rco) idx(rcp) idx(rcr) idx(rcs) idx(rcu) idx(rcx) 
Xmap: idx(rdc) idx(rdcd) idx(rdf) idx(rdg) idx(rdh) idx(rdl) idx(rdm) 
Xmap: idx(rdmi) idx(rdq) idx(rdr) idx(rdrp) idx(rdrq) idx(rdt) idx(rdu) 
Xmap: idx(rep) idx(repe) idx(req) idx(reqa) idx(reqc) idx(requ) idx(rer) 
Xmap: idx(res) idx(rex) idx(rfa) idx(rfl) idx(rfs) idx(rfu) idx(rfx) 
Xmap: idx(rgc) idx(rgg) idx(rgl) idx(rglc) idx(rgr) idx(rha) idx(rhab) 
Xmap: idx(rhe) idx(rhh) idx(rhl) idx(rho) idx(rhp) idx(rhq) idx(rhqa) 
Xmap: idx(rhqc) idx(rhqu) idx(rhr) idx(rhs) idx(rhsa) idx(rhsb) idx(rhsc) 
Xmap: idx(rhsp) idx(rhsr) idx(rhss) idx(rht) idx(rhx) idx(rhy) idx(rid) 
Xmap: idx(rig) idx(rin) idx(rip) idx(ris) idx(rkp) idx(rkr) idx(rle) 
Xmap: idx(rlec) idx(rlh) idx(rli) idx(rll) idx(rlo) idx(rlr) idx(rls) 
Xmap: idx(rlsa) idx(rlsb) idx(rlsc) idx(rlsp) idx(rlsr) idx(rlss) idx(rlt) 
Xmap: idx(rmf) idx(rmfp) idx(rmp) idx(rmt) idx(rna) idx(rnc) idx(rnh) 
Xmap: idx(rnl) idx(rnm) idx(rno) idx(rnon) idx(rnp) idx(rns) idx(rnt) 
Xmap: idx(roa) idx(rop) idx(rpa) idx(rpar) idx(rpay) idx(rpaz) idx(rpc) 
Xmap: idx(rpd) idx(rpf) idx(rpfa) idx(rph) idx(rpha) idx(rpi) idx(rpl) 
Xmap: idx(rpm) idx(rpn) idx(rpo) idx(rpp) idx(rpr) idx(rps) idx(rpsp) 
Xmap: idx(rpu) idx(rpw) idx(rpx) idx(rpy) idx(rpz) idx(rqm) idx(rqp) 
Xmap: idx(rqs) idx(rqt) idx(rqtr) idx(rqu) idx(rqy) idx(rqz) idx(rrf) 
Xmap: idx(rrg) idx(rrgc) idx(rrp) idx(rrpf) idx(rrr) idx(rrrp) idx(rrrq) 
Xmap: idx(rru) idx(rsa) idx(rsb) idx(rsc) idx(rsf) idx(rsfs) idx(rsh) 
Xmap: idx(rsp) idx(rsq) idx(rsr) idx(rst) idx(rsu) idx(rtd) idx(rtl) 
Xmap: idx(rtm) idx(rtmn) idx(rtn) idx(rtp) idx(rtr) idx(rtx) idx(rty) 
Xmap: idx(rtz) idx(rua) idx(rub) idx(rubt) idx(ruc) idx(rud) idx(rue) 
Xmap: idx(ruet) idx(ruf) idx(rug) idx(ruh) idx(ruht) idx(ruj) idx(ruk) 
Xmap: idx(rukt) idx(rum) idx(run) idx(runt) idx(ruo) idx(ruq) idx(ruqt) 
Xmap: idx(rur) idx(rus) idx(rust) idx(rut) idx(rvd) idx(rwt) idx(rxf) 
Xmap: idx(rxp) idx(rxu) idx(ryr) idx(rza) idx(rzg) idx(rzga) idx(rzp) 
Xmap: idx(rzq) idx(rzu) idx(mjc) idx(mjl) idx(mlo_city) idx(mlo_county) idx(mlt) 
Xmap: idx(mpa_assmt) idx(msg) idx(msvb) idx(msvc) idx(msvh) idx(msvi) idx(msvl) 
Xmap: idx(msvr) idx(msvs) idx(msvu) idx(msvv) idx(mvd_mdl) idx(mvd_mnf) idx(mwa) 
Xmap: idx(mwc) idx(mwi) idx(mwk) idx(mwm) idx(mwr) idx(mws) idx(mxd) 
-09-21 10:55:05 db_load_obj: Loaded 574 object scripts
-09-21 10:55:05 db_load_obj: Loading views from /opt/msi//env/test/sql/syb_create_views.sql
-09-21 10:55:15 db_load_obj: End

-09-21 10:55:15 db_load_code: Load SQL code in lpr_test for test
-09-21 10:55:15 db_load_code: Running commands as DBO, lpr_test
Xproc: aacompare(dates) lessee(add_remove) mp(altleasesum) ar(dtl) chk(upd) mjc(convert) rase(dbaconv_ras) 
Xproc: related(del_app) upd(drawdown_clnt) ext(ela_asset) ext(ela_codes) hist(ela) ext(ela_les) ext1(ela_lse) 
Xproc: ext2(ela_lse) ext3(ela_lse) ext4(ela_lse) ext5(ela_lse) ext6(ela_lse) ext(ela_pcro) ext(ela_sales) 
Xproc: del(eop_ral) gl(conversion) update1(gl_note) gl(update1) gl(update2) init(codes) keychng(upd) 
Xproc: mp(leasesum) lxproc(misc) mp(mdeleter) mja(insert) mjc(insert) mjl(insert) upd(mjl_mwc) 
Xproc: delq(mwc) update(mwc_delq) mwc(excl) mwc(insert) delete(mwc_mjc) transfer(mwc_mjc) delete(mwc_mjl) 
Xproc: move(mwc) qry(mwc_opr) prev(mwc_proc) update(mwc_q) mwc(query) mwc(update) mwi(insert) 
Xproc: delete(mwi_mjl) qry(mwi_opr) mwk(insert) delete(mwk_mja) qry(mwk_opr) mwm(insert) delete(mwm_mjl) 
Xproc: qry(mwm_opr) move(mwr) prev(mwr_proc) mwr(qry) mwr(update) mxd(upd) mwc(non_delq) 
Xproc: note(get) mp(nxtnum) mp(outsassmt) mp(outsinv) upd(port_status) mp(prefetch) raa(gen) 
Xproc: rab(gen) rac(gen) rad(gen) radr(gen) raf(gen) rag(gen) rai(gen) 
Xproc: raia(gen) ral(gen) rale(gen) rap(der) rap(gen) rapa(gen) rapd(gen) 
Xproc: raph(gen) rapp(gen) rapr(gen) raps(gen) raq(gen) raqc(gen) raqu(gen) 
Xproc: rar(gen) l19(rar_k0) rarb(gen) ras(gen) rase(gen) rau(gen) rax(gen) 
Xproc: raxp(gen) raxr(gen) rba(gen) rbc(gen) rbd(gen) rbi(gen) rbk(gen) 
Xproc: rbl(gen) rblt(gen) rbp(gen) rbr(gen) rbs(gen) rca(gen) rcc(conversion) 
Xproc: rcc(gen) rcd(gen) rce(gen) rcf(gen) rcfa(gen) rcfb(gen) rcg(gen) 
Xproc: rcga(gen) rcgb(gen) rcgf(gen) rcgg(gen) rcgl(gen) rcgu(gen) rcgv(gen) 
Xproc: rcgw(gen) rcgx(gen) rcgy(gen) rcgz(gen) rch(gen) rck(gen) l13(rck_k0) 
Xproc: rco(gen) rcp(gen) rcr(gen) rcs(gen) rcu(gen) rcx(gen) l9(rcx_k1) 
Xproc: rdc(gen) rdcd(gen) rdf(gen) rdg(gen) rdh(gen) rdl(gen) rdm(gen) 
Xproc: rdmi(gen) rdq(gen) rdr(gen) rdrp(gen) rdrq(gen) rdt(gen) rdu(gen) 
Xproc: rep(gen) repe(gen) status(repo_acct) req(gen) l19(req_k0) l10(req_k5) reqa(gen) 
Xproc: reqc(gen) requ(gen) rer(gen) res(gen) l10(res_k0) rex(gen) rfa(gen) 
Xproc: rfl(gen) rfs(gen) rfu(gen) rfx(gen) rgc(gen) l10(rgc_k0) rgg(gen) 
Xproc: rgl(gen) rglc(gen) rgr(gen) rha(gen) l19(rha_k0) rhab(gen) rhe(gen) 
Xproc: rhh(gen) rhl(gen) rho(gen) rhp(gen) rhq(gen) rhqa(gen) rhqc(gen) 
Xproc: rhqu(gen) rhr(gen) rhs(gen) rhsa(gen) rhsb(gen) rhsc(gen) rhsp(gen) 
Xproc: rhsr(gen) rhss(gen) rht(gen) rhx(gen) rhy(gen) rid(gen) rig(gen) 
Xproc: l9(rig_k0) rin(gen) rip(gen) ris(gen) l10(ris_k1) l18(ris_k1) rkp(gen) 
Xproc: rkr(gen) rle(gen) rlec(gen) rlh(gen) rli(gen) rll(gen) rlo(gen) 
Xproc: rlr(gen) range(rls_dles) rls(gen) l9(rls_k6) range(rls_lse) rlsa(gen) rlsb(gen) 
Xproc: rlsc(gen) rlsp(gen) rlsr(gen) rlss(gen) rlt(gen) rmf(gen) rmfp(gen) 
Xproc: rmp(gen) rmt(gen) rna(gen) rnc(gen) rnh(gen) rnl(gen) rnm(gen) 
Xproc: rno(gen) rnon(gen) rnp(gen) rns(gen) rnt(gen) roa(gen) rop(gen) 
Xproc: rpa(gen) rpar(gen) rpay(gen) rpaz(gen) rpc(gen) l10(rpc_k0) rpd(gen) 
Xproc: rpf(gen) rpfa(gen) rph(gen) l16(rph_k1) rpha(gen) rpi(gen) rpl(gen) 
Xproc: rpm(gen) l10(rpm_k1) rpn(gen) l10(rpn_k1) rpo(gen) rpp(gen) rpr(gen) 
Xproc: rps(gen) rpsp(gen) rpu(gen) rpw(gen) rpx(gen) rpy(gen) rpz(gen) 
Xproc: rqm(gen) rqp(gen) rqs(gen) rqt(gen) rqtr(gen) rqu(gen) rqy(gen) 
Xproc: rqz(gen) rrf(gen) rrg(gen) rrgc(gen) rrp(gen) rrpf(gen) rrr(gen) 
Xproc: rrrp(gen) rrrq(gen) rru(gen) rsa(gen) rsb(gen) rsc(gen) rsf(gen) 
Xproc: rsfs(gen) rsh(gen) rsp(gen) rsq(gen) rsr(gen) l10(rsr_k1) rst(gen) 
Xproc: rsu(gen) l10(rsu_k1) rtd(gen) rtl(gen) l10(rtl_k0) rtm(gen) rtmn(gen) 
Xproc: rtn(gen) rtp(gen) l10(rtp_k1) rtr(gen) l24(rtr_k0) l30(rtr_k0) rtr(range) 
Xproc: rtx(gen) l19(rtx_k0) rty(gen) rtz(gen) rua(gen) rub(gen) rubt(gen) 
Xproc: ruc(gen) rud(gen) rue(gen) ruet(gen) ruf(gen) rug(gen) ruh(gen) 
Xproc: ruht(gen) ruj(gen) ruk(gen) rukt(gen) rum(gen) run(gen) runt(gen) 
Xproc: ruo(gen) ruq(gen) ruqt(gen) rur(gen) rus(gen) rust(gen) rut(gen) 
Xproc: rvd(gen) rwt(gen) rxf(gen) rxp(gen) rxu(gen) ryr(gen) rza(gen) 
Xproc: rzg(gen) rzga(gen) rzp(gen) rzq(gen) rzu(gen) mp(srchclnt) mp(srchvin) 
Xproc: mp(u0112) u0201(delete) u0203(delete) u0205(delete) u0216(delete) u0217(delete) u0219(delete) 
Xproc: u0220(delete) u0229(delete) u0411(1) mp(u0463) mp(u0488) mp(u1101lx1) mp(u1101lx1b) 
Xproc: mp(u1101lx2) mp(u1111) upd(allowed) update(passwd) archv(vertex_rlo) rnm(vertex_rlo) rlo(vertex) 
Xproc: mt(mcml) mt(mcmu) mt(mja) mt(mjc) mt(mjl) mt(rad) mt(raf) 
Xproc: mt(rag) mt(rai) mt(ral) mt(rap) mt(raq) mt(rar) mt(ras) 
Xproc: mt(rau) mt(rax) mt(rbk) mt(rbl) mt(rca) mt(rcc) mt(rce) 
Xproc: mt(rcf) mt(rcg) mt(rcp) mt(rcu) mt(rcx) mt(rdc) mt(rdm) 
Xproc: mt(rdq) mt(rdr) mt(rep) mt(req) mt(rfs) mt(rgl) mt(rgr) 
Xproc: mt(rha) mt(rhl) mt(rhq) mt(rhs) mt(rin) mt(rip) mt(rkp) 
Xproc: mt(rle) mt(rlo) mt(rlr) mt(rls) mt(rmf) mt(rmp) mt(rna) 
Xproc: mt(rnm) mt(rno) mt(rpa) mt(rpar) mt(rpf) mt(rph) mt(rpr) 
Xproc: mt(rps) mt(rqt) mt(rqu) mt(rrg) mt(rrp) mt(rrr) mt(rsc) 
Xproc: mt(rsf) mt(rst) mt(rtm) mt(rub) mt(ruc) mt(rue) mt(ruh) 
Xproc: mt(ruk) mt(run) mt(ruq) mt(rus) mt(rvd) mt(rzg) 
-09-21 11:09:52 db_load_code: Loaded 454 source files
-09-21 11:09:53 db_load_code: End

-09-21 11:09:53 db_set_security: Set db security in lpr_test for test
-09-21 11:09:53 db_set_security: Running commands as lpr_test
-09-21 11:10:10 db_set_security: End
-09-21 11:10:10 db_create: End

Sybase only: the script creates a database with the "truncate log on checkpoint" option enabled. This will clean transaction logs generated each time an automatic checkpoint is performed. For production databases, disable the Sybase "truncate log on checkpoint" option so that the entire transaction log is available for recovery in the event of a system failure between full backups. You can always manually clean out the transaction log as needed. Refer to your Sybase documentation for more information or contact your MSI representative.

Sybase Only: Loading Data

Log on the server as msidba and use the db_restore script to load data into a LeasePak database. If you do not have a previous dataset from another LeasePak database or have converted data to load (contact your MSI representative about converting data to LeasePak), use the seed dataset to populate the database with the minimum required data to begin using LeasePak

db_restore env-name dataset [dbo-password]

where env-name is the name of the particular LeasePak environment, dataset is the name of the dataset to load, and dbo-password is the password for dbo (the script will prompt you for this if needed).

`.lplogin` and `.lpprofile`

Every LeasePak environment includes two hidden files, .lplogin and .lpprofile, located in the $top/env/environment/etc directory, where environment is the particular LeasePak environment. The file .lplogin is a C shell startup file and .lpprofile is a Korn/Bourne/HP-UX Posix shell startup file. You must include these files in the appropriate startup files of the MSI release administrator (msiadmin), the MSI database administrator (msidba), the LeasePak administrative user (lpadmin), and any other user that needs to log directly on the server to perform LeasePak and LeasePak-related tasks.

MSI provides two sample startup files containing the .lplogin and .lpprofile information, sample.login (for C shell users) and sample.profile (for Korn/Bourne/HP-UX Posix shell users), located in the $top/env/environment/lib directory, where environment is the particular LeasePak environment.

To use the sample files

Log on the server as msiadmin
Terminal emulation: you must use one of the supported terminal types. Refer to the Terminal Emulation section of the document System Requirements for more information.
Copy the file sample.login from $top/env/environment/lib (where environment is the particular LeasePak environment) to msiadmin/$HOME. For the initial administrative environment(s) (adm_ora and/or adm_syb), the setup program copies these into the home directories of msiadmin and msidba.

Edit the file

###########################################
#  MSI Sample .login file
###########################################

# Source users .lplogin file to set up LEASEPAK/UX environment

        if ( -f $HOME/.lplogin )  then 
                source $HOME/.lplogin
        else
                echo "Warning:  You don't have a .lplogin file"
        endif

Insert any startup information needed for your particular server into the beginning of the file. Leave everything from the comment # Source users .lplogin file to set up LEASEPAK/UX environment to the end of the file in place

Copy the file sample.profile from $top/env/environment/lib (where environment is the particular LeasePak environment) to msiadmin/$HOME For the initial administrative environment(s) (adm_ora and/or adm_syb), the setup program copies these into the home directories of msiadmin and msidba.

Edit the file

###########################################
#  MSI Sample .profile file
###########################################

# Source user's .lpprofile file to set up LEASEPAK/UX environment

        if [ -f $HOME/.lpprofile ] ; then 
                . $HOME/.lpprofile
        else
                echo "Warning:  You don't have a .lpprofile file!"
        fi

Insert any startup information needed for your particular server into the beginning of the file. Leave everything from the comment # Source user's .lpprofile file to set up LEASEPAK/UX environment to the end of the file in place

Save a backup copy of the current startup file for msiadmin
Rename the two sample files
mv sample.login .login
mv sample.profile .profile
Copy the .lplogin and .lpprofile files from $top/env/environment/lib (where environment is the particular LeasePak environment) to msiadmin/$HOME
Source the appropriate startup file for your shell, or exit and log back on for it to take effect.

Use the command whatami to verify that the startup files are properly configured. The terminal will display something similar to the following

User                       : user_name
LeasePak version           : 
Environment name           : environment
Environment type           : (production, test, or visitor) 

Database name              : lpr_database
Database vendor            : (Oracle or Sybase)
Database server            : database_server_name
Database home              : (usually /opt/oracle or /opt/sybase)

Designated build           : live
Executable directory is a  : link to build directory

You will need the following for LeasePak PC Client setup:
IP Address or name         : server_name
Server Port                :

Use the values for IP Address or name, Environment name, and Server Port to configure the LeasePak client for connection to this particular environment.

MSI recommends setting up both the .lplogin and .lpprofile files, regardless of which shell is normally in use. You can repeat the above steps to configure the startup files for msidba and lpadmin (and others as needed), or you can copy the configured files from msiadmin/$HOME to the other's home directories, then make any necessary changes to personalize the files.

change_env

Log on the server as msiadmin and use the command change_env to change another user (other than msidba) to a different version or environment of LeasePak. You can no longer use change_env to change the environments of msiadmin and msidba. The script will prompt (one line at a time)

Enter LeasePak version []:
Enter environment [environment]:

Type a new value and press Enter or simply press Enter to leave the value unchanged. The user must exit and log back on for the changes to take effect.

whatami

Use the command whatami to verify your current environment before performing any LeasePak or LeasePak related tasks. For users msiadmin and msidba, the working environment is adm_*.

LeasePak Administrative User

For each environment you create within your LeasePak installation, you need an administrative user--that is, an account that can log on the LeasePak client, server, and DBMS to perform advanced LeasePak operational tasks such as End of Period administration, submission of LeasePak batch jobs, tasks within $uexe/lpautil.exe, and user security through the Security [U0706] update.

Although the msiadmin user can assume this role, it can no longer use change_env to move from one environment to another. MSI recommends creating one or more administrative users for your various environments, keeping the msiadmin role separate. Within the System Administration Guide, MSI refers to a generic LeasePak administrative user lpadmin. If needed, you can create a separate lpadmin user (using different user names) for each of your environments.

The LeasePak administrative user (lpadmin), like all LeasePak client users, requires configuration of the LeasePak client password system with corresponding accounts on the server, DBMS, and within LeasePak itself. Unlike other LeasePak client users, the administrative user knows the translated passwords and can log on the server or DBMS directly. For an overview of the LeasePak password system, refer to the Passwords section of the document LeasePak Users.

The following is an overview of the steps for adding a new LeasePak administrative user

Select an initial user name client string. The user lpadmin can change the client string (and the translated passwords with it) later through the LeasePak client Change Password option
Use $uexe/lpautil.exe 112 to determine the translated server and DBMS server passwords based on the client string
Create server and DBMS server accounts for lpadmin with the correct translated passwords
Add lpadmin to the appropriate LeasePak database/schema
Use $uexe/lpautil.exe 108 to add a LeasePak security record for lpadmin.

Do not use $uexe/lpautil.exe 108 to add any user to the LeasePak security table other than the LeasePak administrative user. The $uexe/lpautil.exe 108 function provides no control in how the user is added to LeasePak security, and the LeasePak administrative user must still log on the LeasePak client in order to correctly configure a user's security.

User Names

Create user names in compliance with your company's security guidelines. Use the same user name when setting up the server and DBMS accounts.

Client Strings

Create client strings in compliance with your company's security guidelines. Client strings must be 6 to 8 characters long and all lowercase.

Translating Passwords

Use $uexe/lpautil.exe 112 to translate the client string

Log on the LeasePak server as msiadmin or lpadmin
Terminal emulation: you must use one of the supported terminal types. Refer to the Terminal Emulation section of the document System Requirements for more information.

Type $uexe/lpautil.exe 112 and press Enter The terminal will prompt

This Utility option may be used to translate a Client password 
into the equivalent Unix and SQL Server passwords.

Do you wish to continue (Y/N)?

Type y and press Enter.

The utility will prompt for the client string

Unix and SQL Server password translation utility

Instructions: Enter the Client password. The equivalent Unix and SQL Server passwords will be displayed.

Enter the Client string, <RETURN> to exit:

Type the selected client string and press Enter. If type password as the client string, the terminal will display

Client string: password
SQL Server string: rkqcguh4
Unix string: rrchglt1

MSI does not recommend using the word "password" as an actual client string.

The utility will prompt for another client string
```
Enter the Client string, <RETURN> to exit:
```
Press Enter to exit the utility.

Server Accounts

Follow the appropriate instructions for your OS platform to add a LeasePak user account with the translated password. Make the LeasePak group msi the primary group for the user, and ensure that the user can write to the $HOME directory. If you assign a user's UID number manually, do not use a number greater than 32757. Contact your MSI representative for more information.

`.lplogin` and `.lpprofile`

Copy the .lplogin and .lpprofile files from the $top/env/environment/etc directory (where environment is the default LeasePak environment for lpadmin) to the $HOME directory of lpadmin and modify them to create the appropriate startup files, or, if lpadmin already has startup file from another environment, log on the server as msiadmin and run change_env to switch lpadmin to the correct environment. For more information on .lplogin and .lpprofile, refer to the .lplogin and .lpprofile section of this document.

DBMS Accounts

Use the LeasePak script db_add_login to create an account on your DBMS server

Log on the server as msidba
Terminal emulation: you must use one of the supported terminal types. Refer to the Terminal Emulation section of the document System Requirements for more information.
Run the db_add_login script
db_add_login dbms-type new-login-name [new-login-password [srvadm-password]]

where dbms-type is either ora for Oracle or syb for Sybase, new-login-name is the same user name as the server account, new-login-password is the corresponding translated password, and srvadm-password is the password for the srvadm user.

Database Permissions

Use the LeasePak script db_add_user to grant permissions to a specific LeasePak environment and database

Log on the server as msidba
Terminal emulation: you must use one of the supported terminal types. Refer to the Terminal Emulation section of the document System Requirements for more information.
Run the db_add_user script
db_add_user environment-name legal-DBMS-user msi-access-group dbo-password

where environment-name is the specific LeasePak environment, legal-DBMS-user is the user's DBMS account user name, msi-access-group is either msi for normal read/write permissions or msir for read-only permissions, and dbo-password is the password for the dbo of the specific database (as specified during db_create.

LeasePak Security Records

Use $uexe/lpautil.exe 108 to add a security record for the user lpadmin only. The user lpadmin will then log on the LeasePak client and use the Security [U0706] update to add subsequent users' security records. Each LeasePak database contains its own security table and set of records.

To add a security record through $uexe/lpautil.exe 108

Contact your MSI representative to obtain a daily password for $uexe/lpautil.exe 108. The daily password is only good during the day it is issued.
Log on the server as msiadmin
Terminal emulation: you must use one of the supported terminal types. Refer to the Terminal Emulation section of the document System Requirements for more information.
Use whatami to verify that you are in the correct environment. Use change_env to change environments if necessary. You must log out and back in again for the new settings to take effect.

Type $uexe/lpautil.exe 108 and press Enter. The terminal will display

This Utility option is an MSI Client Services tool used in initial client account setup. WARNING: Improper use of this utility will 
cause severe harm.
Do you wish to continue (Y/N)?

Type y and press Enter. The terminal will prompt for the client string
```
Client Password?
```
Type the LeasePak client string for lpadmin and press Enter. The terminal will prompt for the $uexe/lpautil.exe 108 password
```
Password?
```
Type the one-day password from MSI and press Enter. The terminal will prompt for the user name
```
Enter username, <RETURN> to exit:
```
Type the lpadmin user name and press Enter, or simply press Enter to exit the utility. The terminal will prompt for the user initials
```
Enter user initials:
```
User initials are three characters and must be unique within the specific LeasePak database. For lpadmin, you can use the initials lpx.
Type the initials and press Enter to complete the update.

Registration Codes

Use the /ver option with lpadriver.exe to obtain registration codes for dx Generation (automated document generation) and Print Spy, FormPak, EOP Monitor, and LeasePak EC.

$uexe/lpadriver.exe /ver

        LEASEPAK UX
        Copyright (c) 1995 -  by McCue Systems Incorporated
        ------------------------------------------------------------
        Version        : -
        Build date     : 15-Aug- 00:18   
        Client name    : LeasePak Development                
        Client code    : V5
        User License   : 99999
        Report License : 99999
        Partial License: 99999

        Registration Codes
        ------------------------------------------------------------
        dx Generation   : SER-0541-ZZZ-P92ERR
        Print Spy       : SER-0541-ZZZ-P92ERR
        FormPak         : SER-0541-ZZZ-FE2O3
        Eop Monitor     : SER-0541-ZZZ-SO2
        LeasePak EC     : SER-0541-ZZZ-AL2O3

If you are installing or upgrading LeasePak, this completes the server portion of the LeasePak installation. Restart the DBMS server and Sector7 (see the next section for more information), then continue the installation with the procedures described in the document LeasePak Client.

Maintenance and Troubleshooting

System Restart

Normally, the LeasePak server setup program installs Sector7 and Sybase system restart files, as well as entries in /etc/services and /etc/inetd.conf (or for Linux, /etc/xinetd.d) for the LeasePak and (if applicable) mPower daemons. MSI provides the following procedures for building your own restart files, as well as for performing manual shutdowns and startups.

Log on the server as root to perform the procedures described in this section.

LeasePak Daemon

/etc/services

Create an entry in the /etc/services file using the following format:

<official service name> <port number/protocol name> [<aliases>] [ #<comment>]

<official service name>: Must be unique for the server. By default leasepakd_.
<port number/protocol name>: The port number must be greater than 1023 and unique for the server. By default . The protocol name is tcp.

Example:

leasepakd_v51a_5100  5100/tcp  # LeasePak v51a leasepakd /opt/msi/v51a

Multiple concurrent versions: if you have more than one version of LeasePak installed on the same server, each installation requires its own entry in /etc/services with a unique service name and port number.

inetd.conf (xinetd.d)

HP and Sun: create an entry in the /etc/inetd.conf file.

Linux: create a file service_name in the /etc/xinetd.d directory, where service_name is the official service name (<official service name> from /etc/services).

The entry or file consists of one line. Delimit fields with a space or tab. If you need to continue the entry on a second line, end the first line with a backslash (\).

Example:

leasepakd_v51a_5100 stream tcp nowait root \
    /opt/msi/v51a/live/bin/leasepakd leasepakd \
    -d /opt/msi/v51a -l /opt/msi/v51a/log/leasepakd.log -f /opt/msi \
    /v51a/etc/pidgeon_v51a_rt.lpkd

The required fields are:

Field	Value for `leasepakd`	Notes
official service name	value from `/etc/services`
socket type	stream
protocol	tcp
wait\|nowait	nowait	For Linux, use `no` instead of `nowait`
user to run service	root
full path to server program	$top/env/environment/bin
server program command line with arguments (if any)	leasepakd -d $top/env/environment/bin -l $top/log/leasepakd.log

mPower Daemon

/etc/services

Create an entry in the /etc/services file using the following format:

<official service name> <port number/protocol name> [<aliases>] [ #<comment>]

<official service name>: Must be unique for the server. By default leasepakd_.
<port number/protocol name>: The port number must be greater than 1023 and unique for the server. By default . The protocol name is tcp.

Example:

mPowerd_v51a_5106  5106/tcp  # mPower v51a mPowerd /opt/msi/v51a

Multiple concurrent versions: if you have more than one version of mPower installed on the same server, each installation requires its own entry in /etc/services with a unique service name and port number.

inetd.conf (xinetd.d)

HP and Sun: create an entry in the /etc/inetd.conf file.

Linux: create a file service_name in the /etc/xinetd.d directory, where service_name is the official service name (<official service name> from /etc/services.

The entry or file consists of one line. Delimit fields with a space or tab. If you need to continue the entry on a second line, end the first line with a backslash (\).

Example:

mPowerd_v51a_5106 stream tcp nowait root \
    /opt/msi/v51a/live/bin/mPowerd mPowerd \
    -d /opt/msi/v51a -l /opt/msi/v51a/log/mPowerd.log -f /opt/msi \
    /v51a/etc/pidgeon_v51a_rt.lpkd

The required fields are:

Field	Value for `mPowerd`	Notes
official service name	value from `/etc/services`
socket type	stream
protocol	tcp
wait\|nowait	nowait	For Linux, use `no` instead of `nowait`
user to run service	root
full path to server program	$top/env/environment/bin
server program command line with arguments (if any)	mPowerd -d $top/env/environment/bin -l $top/log/mPowerd.log

Sample Restart Files

You can find sample restart files for Sector7 and Sybase in the $top/env/environment/lib directory. These include

_sector7.que Sector7 queue manager and queues
sybase12 Sybase 12.0 (HP and Sun only)

Editing Restart Files

_sector7.que

Copy the sample _sector7.que file to your $HOME directory and edit the beginning of the file for your sh shell, Sector7 directory location, and version of LeasePak

#!<SHELL>
# $Header: _sector7.que,v 5.1.0.1 2004/07/22 07:38:17 garysk WorkElement $
# Startup and shutdown sector 7 queue manager.
#--------------------------------------------------------------------------------

#--------------------------------------------------------------------------------
# Site customization.
#--------------------------------------------------------------------------------
SECTOR7=<Sector 7 directory>
leasepak_version=<Leasepak version>

where <SHELL> is the full path and name of your sh shell file, <Sector 7 directory> is the full path of your Sector7 directory (including version numbers), and <Leasepak version> is your version of LeasePak in vNNa format (example: ).

HP, Sun only: `sybase12`

Copy the sample sybase12 file to your $HOME directory and, using vi or other editor, complete the Site Customization at the top of the file

#!shell
# Startup and shut down Sybase ASE and ASE Backup Server
#--------------------------------------------------------------------------------

#--------------------------------------------------------------------------------
# Site Customization.
# Please change these variables to reflect your site's requirements
#--------------------------------------------------------------------------------
SYBDIR=sybase_directory
DATASERVER=sybase_dataserver
BACKUPSERVER=sybase_backup_server

#--------------------------------------------------------------------------------
# IMPORTANT NOTE: Sybase shutdown script (${SYBASE}/${SYBASE_ASE}/bin/syb_shutdown)
#                 must have sa password as first line.
#                 If you use this, protect the file!! (sybase:sybase 600 recommended)
#--------------------------------------------------------------------------------

where

shell is your Bourne shell with directory (usually /sbin/sh for HP or /bin/sh for Linux and Sun)
sybase_directory is the top directory where Sybase is installed
sybase_dataserver is the name of your Sybase dataserver
sybase_backup_server is the name of your Sybase backup server

syb_shutdown

Edit the script syb_shutdown to insert the sa password in the top line of the script. The file sybase12 calls the script syb_shutdown to shut down the backup and data servers and require the sa password to complete their processes. You can find the syb_shutdown script in the $SYBASE/bin directory

sa_password

shutdown SYB_BACKUP
go
shutdown
go
exit

(the blank line after sa_password is required) where sa_password is the sa password.

To protect the sa password, change the owner of syb_shutdown to root and its permissions to 600.

Not performing this step leaves the sa password exposed to other users.

init.d

Place your edited restart files in the init.d directory, found in one of the following locations

HP: /sbin/init.d

Linux, Sun: /etc/init.d

Ownership and Permissions

After placing the files in init.d, change their owner:group to bin:bin their permissions to 555.

Run Level and `rc?.d`

Run Level

Use the appropriate procedure below to determine your server's default run level

HP, Sun: use who -r
The server will display something similar to the following:

. run-level 3 Apr 25 18:17 3 0 S

The normal run level is 3.

Linux: use cat /etc/inittab | grep :initdefault:
The server will display something similar to the following:

id:3:inidefault:

The normal run level is 3.

Use the default run level to determine which rc?.d directory to place your Sybase startup command, where ? is the numbers corresponding to a run level. The next step assumes a default run level of 3.

Refer to your system documentation and man documents for more information on run levels and system startup and shutdown sequences.

rc?.d

Locate the run command directories rc?.d, where ? are the numbers corresponding to the run levels

HP: /sbin/rc?.d

Linux, Sun: /etc/rc?.d

Then create symbolic links to startup and shutdown (kill) files in the appropriate rc?.d directories

HP:

ln -s /sbin/init.d/_sector7.que /sbin/rc3.d/S900_sector7.que
ln -s /sbin/init.d/_sector7.que /sbin/rc1.d/K100_sector7.que
ln -s /sbin/init.d/sybase12 /sbin/rc3.d/S900sybase12
ln -s /sbin/init.d/sybase12 /sbin/rc1.d/K100sybase12

Linux:

ln -s /etc/init.d/_sector7.que /etc/rc3.d/S900_sector7.que
ln -s /etc/init.d/_sector7.que /etc/rc1.d/K100_sector7.que

Sun:

ln -s /etc/init.d/_sector7.que /etc/rc3.d/S90_sector7.que
ln -s /etc/init.d/_sector7.que /etc/rc1.d/K10_sector7.que
ln -s /etc/init.d/sybase12 /etc/rc3.d/S84sybase12
ln -s /etc/init.d/sybase12 /etc/rc1.d/K09sybase12

Manual Startup and Shutdown

Once you have the automatic restart files configured, you can use them to manually start up and shut down inetd (or xinetd for Linux), Sector7, and the Sybase servers.

inetd (xinetd)

HP:

Log on the server as root and run the following command

/usr/sbin/inetd -c

Linux:

Log on the server as root and run the following command

service xinetd restart

Sun:

Log on the server as root
Find the PID number for the inetd daemon
```
ps -ef | grep inetd | grep -v grep
```
Restart the daemon
```
kill -HUP PID
```
where PID is the PID number for the inetd daemon.

Sector7

Startup

Use the start procedure to start up the servers

location/init.d/_sector7.que start

where location is the location of your init.d directory.

The terminal will display

	Starting Sector 7 queue manager
	VX/DCL - DEC VMS DCL Emulation for Unix
	Copyright © 1985-1995 Isleworth Ltd.
	All Rights Reserved
	VX/DCL - DEC VMS DCL Emulation for Unix
	Copyright © 1985-1995 Isleworth Ltd.
	All Rights Reserved

followed by a list of queues and their statuses.

You can also start Sector7 by logging on as the user msiadmin and using the following commands to first start the queue manager and then the queues

	dcl -n sector7_directory/com/start_qmgr.com
	dcl -n sector7_directory/com/start_queues.com

ps -ef | grep mgr

Use the command ps -ef | grep mgr to verify that the Sector7 batch and print queues are running. The terminal will display something similar to the following excerpt

    msiadmin  2002  1252  0  Aug 10  ?         0:06 qmgr sector7_directory/spool LP$EOP1 2
    msiadmin  2124  1252  0  Aug 10  ?         0:01 qmgr sector7_directory/spool CS$PRINT 7
    msiadmin  2053  1252  0  Aug 10  ?         0:07 qmgr sector7_directory/spool DTM_QUE 3
    msiadmin  2055  1252  0  Aug 10  ?         0:02 qmgr sector7_directory/spool SYS$PRINT 4

where sector7_directory is the path of your Sector7 directory.

show_que.com

You can also use the command show_que.com to verify that the Sector7 queues are running

	dcl -n sector7_directory/com/show_que.com

The terminal will display the list of queues and their current status, along with their parameters as set in start_queues.com.

Shutdown

location/init.d/_sector7.que stop

where location is the location of your init.d directory.

The terminal will display

	Stopping Sector 7 queue manager
	VX/DCL - DEC VMS DCL Emulation for Unix
	Copyright © 1985-1995 Isleworth Ltd.
	All Rights Reserved

You can also stop Sector7 queues by logging on as the user msiadmin and using the following command to stop the queue manager

	dcl -n sector7_directory/com/stop_qmgr.com

Sybase

Startup

Use the start procedure to start up the servers

location/init.d/sybase_file start

where location is the location of your init.d directory and sybase_file is sybase12.

The terminal will display

Sending output to nohup.out
Sending output to nohup.out

You can also start the servers by logging on as the user sybase and using the startserver command from the Sybase ASE install directory:

startserver -f SERVER_SYBASE -f SYBASE_BACKUP > startup.log 2>&1

where SERVER_SYBASE is the name of your dataserver and SYBASE_BACKUP is the name of your backup server. Refer to your Sybase documentation for more information.

ps -f -u sybase

Use the command ps -f -u sybase (where sybase is your Sybase user) to verify that the data and backup servers are running. The terminal will display something similar to the following

       UID    PID   PPID  C  STIME  TTY      TIME   COMMAND
	sybase  21966  21964  0  Jun 8    ?      0:02   /opt/sybase/ASE-12_0/bin/backupserver -SSYBASE_BACKUP -e/op
	sybase  21961  21959  0  Jun 8    ?   1080:38   /opt/sybase/ASE-12_0/bin/dataserver -sSERVER_SYBASE -d/dev/

where SYBASE_BACKUP is the name of your backup server and SERVER_SYBASE is the name of your dataserver.

You can also verify that the servers are running by logging on as the user sybase and using the showserver command from the Sybase ASE install directory. Refer to your Sybase documentation for more information.

Shutdown

Use the stop procedure to shut down the servers

location/init.d/sybase_file stop

where location is the location of your init.d directory and sybase_file is sybase12.

The terminal will display

	Shutting sybase down
	Password: 
	Backup Server: 3.48.1.1: The Backup Server will go down immediately. 
	Terminating sessions.
	Server SHUTDOWN by request.
	The SQL Server is terminating this process.
	DB-LIBRARY error:
	    Unexpected EOF from SQL Server.

The DB-LIBRARY error is normal.

Backups

Server Backups

MSI recommends incremental and periodic full backups of the LeasePak server.

Snapshot and Restore

Use db_snapshot and db_restore to backup and restore LeasePak datasets. Unlike native DBMS backup utilities, these scripts handle both the LeasePak table data and the required accompanying C-ISAM files.

db_snapshot

Syntax

db_snapshot environment-name dataset-name [dbo-password]

where environment-name is the LeasePak environment for which you want to copy the data, dataset-name is the name you specify for the dataset, and dbo-password is the associated database's owner (dbo) password (the script will prompt you for this if needed).

Log on the server as msidba, change to the $top/env/environment/bin directory, and run this script to take a copy of the specified LeasePak data and create a dataset for it in $top/datasets.

db_snapshot uses characters specified in the $top/etc/terminators.txt file to delimit and terminate fields and records. To use this file to customize the characters used, contact your MSI representative.

db_restore

Syntax

db_restore environment-name dataset-name [dbo-password]

where environment-name is the LeasePak environment for which you are restoring the data, dataset-name is the name of the dataset you want to use, and dbo-password is the associated database's owner (dbo) password (the script will prompt you for this if needed).

Log on the server as msidba, change to the $top/env/environment/bin directory, and run this script to take the specified LeasePak dataset from $top/datasets and load it into the specified environment/database. You cannot use db_restore to load a dataset into a visitor environment.

Sybase only: you may also need to run db_update_statistics. For more information on when to run this script, refer to the Sybase documentation on update statistics or contact your MSI representative.

Native DBMS Backups

Periodically use native DBMS commands to back up databases/schemas, including system ones used by the DBMS. For more information, refer to the appropriate document below:

Oracle: coming soon.

Sybase:

Housekeeping

Changing Passwords

If you need to administratively change a LeasePak client user's password, you can use lpchgpass to change it without logging on the LeasePak client.

lpchgpass

Syntax

lpchgpass cfggen_config_file environment user_name_to_change db_owner [new_user_password db_owner_password]

where cfggen_config_file is the name of the $top/etc/host_version_lpkd.msirc file, environment is the LeasePak environment, user_name_to_change is the name of the user whose passwords you are changing, db_owner is the LeasePak database owner (dbo), new_user_password is the new client string (password the user types to log on the LeasePak client), and db_owner_password is the dbo password.

Log on the server as root, change to the $top/env/environment/exe directory, and run this program to change a user's client string and, with it, the encrypted server (OS) and DBMS passwords.

Disk Space

Use the appropriate command below to check for disk space used on the server:

HP: bdf

Linux: df

Sun: df -k

If the space used on any file system is over 90%, you may run out of disk space during End of Period processing.

Dropping Databases

Databases and schemas consume large amounts of disk space; use db_drop to remove unused databases/schemas.

Sybase only: db_drop

Syntax

db_drop environment-name [srvadm-password]

where environment-name is the LeasePak environment associated with the database and srvadm-password is the password for the DBMS server administrator (srvadm).

Log on the server as msiadba, change to the $top/env/environment/bin directory, and run this script to remove the database. This script does not remove the associated environment directories. Log on the server as root and use rm with the appropriate options to remove these.

Sector7 Temporary Files

Avoid problems with End of Period processing by periodically running the Sector7 housekeeping programs cleanup and cleanse_s7. You can set these to run in cron, as long as you schedule them as required (see below). Do not run either of these programs during End of Period processing.

cleanse_s7

Syntax

cleanse_s7 admin_user

where admin_user is usually msiadmin.

Log on the server as msiadmin, change to the $top/env/environment/bin directory, and run this program to clean up Sector7 files (or run through cron). This program cleans more thoroughly than cleanup. Do not run this program while users are in LeasePak; MSI recommends running it before (but never during) End of Period processing.

cleanup

Syntax

cleanup

Log on the server as msiadmin, change to the Sector7 bin directory, and run this program to delete excess Sector7 temporary files (or run through cron). MSI recommends running this several times a day, even while users are in LeasePak, but never during End of Period processing.

RHR Table

During End of Month, LeasePak writes Historical Tax Released records to the rhr table. LeasePak does not use these records after End of Month is complete, and the table will grow indefinitely unless you clean it periodically.

db_truncate_rhr

Syntax

db_truncate_rhr environment-name [dbo-password]

where environment-name is the specific environment and dbo-password is the corresponding database's dbo password.

Log on the server as msidba and run this script to clean up the rhr table only after End of Month is complete.

`$top/log` Log Files

Log files in the $top/log directory, including the leasepakd and mPowerd daemon log files, will grow over time. Periodically clean up these files to conserve disk space.

Users' Home Directories

Monitor and periodically clean up, if necessary, the following files found in LeasePak users' home directories, which are either very large to begin with (core files) or can grow very large over a period of time (leasepak_error.log files:

Core files, named core; LeasePak creates core files containing the entire contents of memory at the time when a user encounters certain types of errors
Error log files, named leasepak_error.log; LeasePak appends error messages to these each time an error is encountered.

The information contained in this document is the property of McCue Systems, Inc. Use of the information contained herein is restricted. Conditions of use are subject to change without notice. McCue Systems, Inc. assumes no liability for any inaccuracy that may appear in this document; the contents of this document do not constitute a promise or warranty. The software described in this document is furnished under license and may be used or copied only in accordance with the terms of said license. Unauthorized use, alteration, or reproduction of this document without the written consent of McCue Systems, Inc. is prohibited.

LeasePak

Server Configuration and Maintenance

Parameters

Batch Queues

Printer Name

Printer Installation and OS Configuration

DEVINIT

Config

start_queues.com

setup_new_env

Syntax

Options

Arguments

Configuration Worksheet

Environment Configuration

change_env

whatami

db_create

Options

Arguments

Database Configuration

Sybase Only: Loading Data

change_env

whatami

User Names

Client Strings

Translating Passwords

Server Accounts

.lplogin and .lpprofile

DBMS Accounts

Database Permissions

LeasePak Security Records

LeasePak Daemon

/etc/services

inetd.conf (xinetd.d)

mPower Daemon

/etc/services

inetd.conf (xinetd.d)

Sample Restart Files

Editing Restart Files

_sector7.que

HP, Sun only: sybase12

syb_shutdown

init.d

Ownership and Permissions

Run Level and rc?.d

Run Level

rc?.d

Manual Startup and Shutdown

inetd (xinetd)

Sector7

Sybase

Server Backups

Snapshot and Restore

Native DBMS Backups

Changing Passwords

Disk Space

Dropping Databases

Sector7 Temporary Files

RHR Table

$top/log Log Files

Users' Home Directories

`.lplogin` and `.lpprofile`

HP, Sun only: `sybase12`

Run Level and `rc?.d`

`$top/log` Log Files