• env-name is the environment the new LLDB will be associated with
• db-type is the database type: either ora for Oracle or syb for Sybase
• db-server is a database server associated with the selected database type when SETUP was run
• db-name is the LLDB name

• -tl (minus-lowercase-T-L) signifies a test environment
• build-descriptor determines where the environment will find its executable copies of LeasePak. For a test environment, it can be the build ID alias live or a build ID in the form bldn.nn.nnnn (for example bld6.10.0179)

• env-name is the environment in which the LLDB will be (re)created
• Other inputs
  • The operator will be prompted for the $SRVADM's (the database server administrator) password. For security, the characters of the password are not printed on the screen as the operator types them.
  • The operator may be prompted for the DBO's password. If creating a new LLDB, the operator may be prompted to reenter the DBO's password to confirm. For security, the characters of the passwords are not printed on the screen as the operator types them.
  • The operator will be prompted for the storage segments on which to construct the LLDB. The DBMS determined by the db-type that was indicated when the environment was constructed using setup_new_env is the DBMS under which the LLDB will be constructed; this in turn will determine how db_create prompts for storage segments.
    • Under Oracle (db-type of ora), the operator will be presented with a list of one or more storage segments. Each storage segment is an Oracle tablespace. An Oracle LLDB can use only one storage segment, but an Oracle storage segment can contain multiple LLDBs. Only storage segments constructed for LeasePak using the LeasePak db_create_tablespace command may be used for LeasePak LLDBs.
      For small LLDBs under 300MB, when prompted, the operator enters a common storage segment and specifies the required size of the LLDB in megabytes when prompted.
      For larger LLDBs over 300MB, the system administrator must create a dedicated storage segment specifically for the particular LLDB under construction; this along with any common storage segments will be displayed. The operator enters the dedicated storage segment when prompted and when prompted for the size, enters UNLIMITED so that the LLDB will utilize the entire segment.
      Each common storage segment can contain multiple LLDBs; each dedicated storage segment can contain only one.
      If the Strict naming convention is in force, only common storage segments and a possible dedicated storage segment will be displayed. If the Loose naming convention is in force, then other system and/or non-LeasePak storage segments may be displayed as well.
    • Under Sybase (db-type of syb), the operator will be presented with a list of two or more storage segments. Each storage segment is a Sybase database device. The system administrator must create these storage segments before LLDB creation. Two kinds of storage segments must be created: data devices and log devices. Each Sybase LLDB requires space on both kinds of storage segments.
      When prompted, the operator enters the name of a storage segment to use, then enters the number of megabytes of space available on that storage segment to allocate to the LLDB, and then enters D for data or L for log to indicate how the storage segment is to be used. The operator continues selecting storage segments until sufficient space has been allocated for the LLDB's needs for both data storage segments and log storage segments have been met.
      data storage segments must be used for only the data segments of LLDBs, and log storage segments must be used for only the log segments of LLDBs. Mixing data and log from any LLDBs on the same storage segment is not allowed.
      Each Sybase storage segment can hold parts or all of multiple LLDBs.
      When setting up Sybase devices, it is strongly advised that the system administrator choose a naming convention that will make the purpose of each device clear.
• If the LLDB already exists, db_create will ask the operator whether or not to drop the LLDB. If the operator enters Y or y, the existing LLDB will be destroyed, and all data in it will be permamemtly lost unless the system administrator has made suitable backups. If the operator enters anything else, the LLDB will not be affected, and db_create will abort.

• env-name is the environment containing the LLDB that is to be (re)loaded with data from the data-set
• data-set-name is the group of files containing a complete image of a LeasePak logical database (LLDB), and must be one of:
  • a standard Netsol-provided data-set, seed or level7, found in the current build dsets directory ($udsets)
  • a locally produced data-set found in the release datasets directory ($datasets)
  • a data-set at an arbitrary location on the application host, provided that the data-set parameter is the absolute pathname of a directory containing the files of a compatible data-set
• [-p proc-count], where proc-count is an integer from 1 to 15, which determines the number of concurrent processes that will be used to move the data from the data-set into the LLDB. The [...] indicates that this parameter is optional; if omitted, the number of concurrent processes defaults to 4, as if -p 4 had been typed on the command line. Values greater than 4 are intended for loading large or very large data-sets.
• Other Inputs
  • db_restore will require that the operator enter the DBO's password when prompted. This password was assigned to the DBO when the LLDB was built using db_create.
  • There are other options which may be used with db_restore; see the full syntax of db_restore here.

• User Type - one of the four types of non-administrative users described in this section.
• OS Acct? - does this type of user require an OS account?
• DBMS Acct? - does this type of user require an account under the a database server?
• Shell Access? - does this type of user require direct access to a command shell running on the application host?
• Security Record Created By - which utility is used to create the security record for this type of user? Util 108 or [U0706] Security.
• Range of Available Options - which LeasePak menu options are available to this type of user?
• License Class - The LeasePak license authorizes certain numbers of security records to be created. There are three classes of users involved in this authorization; this column specifies which class each of the user types is authorized by: User, Report or Partial.

• lease is an alias for $uexe/lpadriver.exe, which is usually a link to the executable, or driver, in the build assigned to the environment when it was created using setup_new_env.
• /util indicates that the driver should execute in LeasePak Utilities mode
• 112 is the selector for the password translation facility
• Other inputs
  • The utility prompts for a client string, and when entered, displays the SQL server string and the Unix string.
  • It then prompts for another client string. If the operator simply presses ENTER, the utility will exit back to the shell.

• db-type indicates to which database server the user login is to be added: ora indicates Oracle and syb indicates Sybase. This is necessary because LeasePak can be installed to run on multiple database systems at a single site.
• user-name is an existing OS user who has not previously been added to the database server.
• user-password is the user's SQL server string translated password obtained by running lease /util 112.
• Other inputs
  • The operator will be prompted for the $SRVADM's (the database server administrator) password. For security, the characters of the password are not printed on the screen as the operator types them.

• env-name indicates the LeasePak environment which contains the LLDB that will be affected by the command
• user-name is the name of an existing user login within the database system, who is not already a user of the LLDB
• access-group is either msi or msir. msi is the access that all users who access LeasePak using the LeasePak client, and grants read and write permission on all LeasePak tables, and execute permission on all LeasePak stored procedures. msir grants only read permission on the LeasePak tables. It cannot be used to access LeasePak through the LeasePak client or to access any LeasePak Utility on the application host. msir is intended for use by non-LeasePak users such as analysts who require read access but will not be able to make any changes to the data.
• Other inputs
  • The operator will be prompted for the DBO's (the database owner) password. For security, the characters of the password are not printed on the screen as the operator types them.

• user-name is the OS login account name of the user whose environment is to be set. This user should already be completely set up in LeasePak by the system administrator and the LeasePak supervisor following these procedures.
• release-version is the LeasePak release version that contains the environment that the use is to be assigned to
• env-name is the environment to which the user is assigned, and to which he has been given access via the above procedures
• modes are the file access modes that are to be applied to the LeasePak start-up files copied to the user's home directory by change_env. If the user is allowed to change his own environment, then the modes should be 660, writable by owner and group. If the user is not allowed to change her own environment, then the modes should be 640, writable only by owner.

 # service nst_qm_${INST_ID}62a start

• nst_qm_${INST_ID}62a is the service script created by SETUP.
• start is the command the operator wishes to send to the service, nst_qm_${INST_ID}62a in this instance. This command tells the service to initialize itself and begin providing its services.

 # service nst_qm_${INST_ID}62a stop

• nst_qm_${INST_ID}62a is the service script created by SETUP.
• stop is the command the operator wishes to send to the service, nst_qm_${INST_ID}62a in this instance. This command tells the service to stop providing its services and to free any resources it may have acquired.

 # service nst_qm_${INST_ID}62a status

• nst_qm_${INST_ID}62a is the service script created by SETUP.
• status is the command the operator wishes to send to the service, nst_qm_${INST_ID}62a in this instance. This command tells the service to display information about its current status.

 [nsadm62a:~] ipcs -mbco

• -mbco indicates that basic information on the shared memory resource is to be displayed.

 [nsadm62a:~] ipcs -q 

• -q indicates that basic information on the message queues resource is to be displayed.

 $AWK '{printf "%08x\n", $1}' 

 # ipcrm -opt key [-opt key] ... 

• key is the IPC key that the administrator wishes to remove. Multiple keys may be listed, each preceded by opt.
• opt is either -M for shared memory segments or -Q for message queues.

  $ init/que/start/job_limit=n/batch batch-queue-name 

• $ is the command introducer
• init is the actual command name
• in DCL, /-characters introduce command qualifiers, not file path component separators. Command qualifiers are basically equivalent to "-"-options.
• /que - indicates a queue is to be created
• /start - indicates that the individual manager process, qmgr, should be started
• ?!/job_limit=!? - controls the maximum number of jobs that can run on the queue concurrently
• n - indicates the number of jobs job_limit should allow
• /batch - indicates the kind of queue being created
• batch-queue name - name by which the queue will be known to the Queue Manager.

  set noon

• the command introducer $ which must precede every command
• the command continuation - which must terminate every command line that wraps to the next line
• the comment character, !, which hides everything up to the end of the line, or until the next !