-a
Annotation
| (Optional) Specifies the license annotation (up to 80 characters).
|
-d
NumberOfDays
| Specifies the duration of the password. If the password type is
license, then this value specifies the number of days for which the licenses
are valid; if the password type is compound, then this value specifies
the number of days during which license passwords may be derived from the
compound password.
|
-D
NumberOfDays
| (Compound passwords only). Specifies maximum aggregate duration
(in days) of all derived passwords.
|
-e
mm/dd/yy
| Specifies the end date of the password. If the password type is
license, then this value specifies the end date of the licenses; if the
password type is compound, then this value specifies the end date for creating
license passwords derived from the compound password.
|
-E
mm/dd/yy
| (Compound passwords only). Specifies the derived license end
date. This is the date after which no license password derived from the
compound password is valid.
|
-h
| Command usage information. (Same as -usage)
|
-i
VendorID
| Specifies the vendor ID. Supply the vendor ID specified by the
provider of the compound licenses.
|
-l
| (Uppercase i) Specifies the license type; use one of the following
keywords:
- nodelock
-
- useonce
-
- concurrent
- If you specify concurrent, you may optionally define
multiple-use rules for the licenses being created.
- -m
- (Optional) Specifies the rules whereby multiple invocations of a product
require only a single concurrent license. You can specify the rules as
any combination of the following arguments: u (same user),
n (same node), g (same group), j (same job
ID).
For example, the specification
-m un means that, if the user and node are the same as those
associated with a previously granted license, then any succeeding invocations
of the product will not require any additional concurrent-use licenses.
Note: Arguments
to the -m option are specified without separating spaces, commas,
etc. (ungj).
|
-k
supplier
| Use the keyword supplier: this causes
ls_dpass to use the supplier's vendor key (which is known to
the license server) to encode the passwords.
|
-n
| Number of licenses. Supply the total number of licenses over all
target IDs on the list.
|
-N
ProductName
| (Optional) Specifies the product name. If an argument is not
supplied, a product name of the form "Product <product ID>" is created
by ls_dpass.
|
-p
ProductID
| Specifies the product ID.
|
-r Version
| Specifies the product revision text.
|
-s
mm/dd/yy
| Specifies the start date of the password. If the password type is
license, then this value specifies the start date of the
licenses; if the password type is compound, then this value
specifies the start date for creating license passwords derived from the
compound password.
|
-S
mm/dd/yy
| (Compound passwords only). Specifies the derived license start
date. This is the date before which no license password derived from
the compound password is valid.
|
-t
| Specifies the target type; default if omitted: domain.
Or supply one of the following keywords: aix, dgux,
domain, hpux, intergraph, msdos,
next, novell, sco, sgi, svr4, sun,
ultrix, or vms. (See the release notes for the
latest list of supported targets).
|
-u (Optional)
| Generates ls_admin command lines as part of the
ls_dpass output. These ls_admin command lines can
be used to install the passwords generated by ls_dpass.
|
-v
VendorName
| Specifies the vendor name.
|
-w
| Specifies the password type; supply one of the following
keywords: license or compound. If the
password type is compound, you must also supply the derived
start/end dates (-S, -E) and the aggregate duration in
days (-D).
Note: If this option is omitted, the start date of the
password defaults to the current date as the start date. Start dates
cannot be "before" the current date.
|
-z
| Debugging flag. (Prints RPC debugging information)
|
-usage
| Command usage information. (Same as -h)
|
Exit Button
| Select this button to exit from ls_dpass.
|
Select Menu
| Select an item from this menu to specify the type of object you want to
work with (vendor, product, password, or customer).
|
Vendor
| Select this button to display a list of vendors in the List box, and a
menu of vendor-related commands in the Command box. Select a
vendor. Then select either a vendor-related command to operate on the
vendor list, or Product to display a list of products for the vendor you
selected.
|
Product
| After you have selected a vendor, select this button to display a list of
the vendor's products in the List box, and a menu of product-related
commands in the Command box. Select a product. Then select
either a product-related command to operate on the vendor list, or Customer to
display a list of customers for the product you selected.
|
Password
| After you have selected a vendor, product, and customer, select this
button to display information fields related to the creation of passwords for
the selected customer.
|
Customer
| Select this button to display a list of customers in the List box, and a
menu of customer-related commands in the Command box.
|
Password type:
| Select the button to the right of the label Password type: to
toggle between License (default) and Compound.
|
License type:
| Select the button to the right of the label License type: to
display a menu of License Use Management license types, from which you can
choose one. The types are concurrent, use once,
and node locked.
|
Multiple-Use Rules
| Use this menu to specify the rules whereby multiple invocations of a
product require only a single concurrent-use license. Do not specify
different rules for passwords for any single version of a product that are
destined for installation in the same network environment.
|
Same User
| Check this item to indicate that only a single concurrent-use license is
required for multiple invocations of the product so long as the same user is
invoking the product.
|
Same Group
| Check this item to indicate that only a single concurrent-use license is
required for multiple invocations of the product so long as the invocations
originate from the same group.
|
Same Node
| Check this item to indicate that only a single concurrent-use license is
required for multiple invocations of the product so long as the product is
being invoked at the same node.
|
Same Job
| Check this item to indicate that only a single concurrent-use license is
required for multiple invocations of the product so long as the invocations
are associated with the same job ID.
|
Exit
| Exits from the multiple-use rules menu.
|
Target type:
| Select the button to the right of the label Target Type: to display
a menu of target types from which you can choose one to specify the type of
node for which you are creating passwords. The default choice is
AIX. Other choices include: DGUX, Domain,
HPUX, Intergraph, MSDOS,
NeXT, Novell, SCO, SGI, SVR4,
Sun, Ultrix, and VMS.
|
Next target
| Select this button to switch to the next target.
|
Create Passwords
| Creates passwords based on the product/vendor data specified. If
you have used the Output file option, this information is saved in the file
you specify. Note that when you create license passwords,
ls_dpass decrements the number of compound licenses available
according to the type and number of licenses specified.
|
Create script
| ls_dpass can output scripts that customers can use to automate
the installation of the passwords. The script is appended to the
ls_dpass transcript. If you want ls_dpass to
generate the shell script, select the check box.
|
Output file
| Use this to enter a filename in which you want customer passwords to be
saved. (Optional) You must select this button before you select Create
Passwords.
|
Number of
targets:
| Enter the total number of target nodes on which passwords are to be
installed. (Optional; default is 1.)
|
Number of Licenses
(total):
| Enter the total number of licenses to be created (that is, the aggregate
of all licenses specified by all passwords to be created in this
session).
|
License annotation
| Enter an annotation of up to 80 characters for the licenses
(optional). The software product defines the annotation, and when
licenses are created, ls_dpass outputs the annotation along with
the passwords. If there is no annotation, leave this field
blank. Do not specify different annotations for passwords for any
single version of a product that are destined for installation in the same
network environment.
|
Target n of n
| Indicates the target for which ls_dpass is currently
displaying password information.
|
Target id:
| Enter the target ID. The passwords generated are installable only
at the target having the specified ID.
|
Start:
| If the password type is License, enter the start date for the
licenses (the licenses become effective at midnight on the day before the
specified date). This date can't be earlier than the current
date. (Default is the current date.)
If the password type is
Compound, enter the start date for the compound password(s)
(passwords become effective at midnight on the day before the specified
date). This date can't be earlier than the current date.
(Default is the current date.)
|
Duration
(days):
| If the password type is License, enter the duration of the
licenses (in days); or skip this field and enter the expiration date
instead. The maximum duration of a license is 4096 days.
(Default is 0.)
|
Expiration:
| If the password type is License, enter the expiration date of
the licenses in date format (licenses expire at midnight on the specified
date). If you prefer, skip this field and enter the duration in days
instead. The latest expiration date may be no more than 4096 days after
the start date. (Default is today's date, corresponding to a
duration of 0 days.)
If the password type is
Compound, enter the expiration date of the password(s) in date
format (passwords expire at midnight pm on the specified date). The
latest expiration date may be no more than 4096 days after the start
date. (Default is today's date, corresponding to a duration of 0
days.)
|
Derived license
start:
| Enter the earliest start date for licenses that are to be derived from a
compound password (this item is not applicable to license passwords).
The derived licenses may start later, but not earlier, than the date you
specify here.
|
Derived license
expiration:
| Enter the latest expiration date for licenses that are to be derived from
a compound password (this item is not applicable to license passwords).
The derived licenses may expire earlier, but not later, than the date you
specify here.
|
Aggregate duration
(days):
| Enter the aggregate duration of all licenses that are to be derived from
a compound password (this item is not applicable to license passwords).
For example, a compound password from which 100 licenses may be derived might
have an aggregate duration of 36500 days. From this password may be
derived 100 1-year licenses, or 50 6-month licenses and 50 18-month licenses,
and so on.
|
Number of licenses (this
target):
| Enter the number of licenses to be installed on the current target if
this number is different from the default number shown here. (By
default, ls_dpass divides the total number of licenses to be
installed by the number of targets on which the licenses are to be
installed.) (This information applies only to concurrent-use and
use-once license types; passwords for nodelock licenses are always one
per target.)
|