Reference Guide › Utilities › sepmd Utility › sepmd Utility—Administer Dual Control

sepmd Utility—Administer Dual Control

Valid on UNIX

The sepmd utility manages Dual Control transactions. The sepmd utility gives each transaction a unique ID number when it is created.

Note: For more information about Dual Control, see the Endpoint Administration Guide for UNIX.

When you use Dual Control, the name of the PMDB must be maker and the is_maker_checker configuration setting must have the value yes for both the PMDB and CA ControlMinder.

This command has the following format:

sepmd -m {l|la|lo}

sepmd -m {d|r} transactionId

sepmd -m p transactionId code

‑m d

Deletes the transaction. A transaction is one or more commands that must be approved before they are implemented on the PMDB. Only the user who created the transaction can delete it.

‑m l

Lists the unprocessed transactions (awaiting the Checker) of the user who invoked the command. Each transaction is listed with its ID number, the name of its Maker (the user who created the transaction-in this case the same user who invoked the command), and its description, if any.

‑m la

Lists all the unprocessed transactions of all the Makers. Each transaction is listed with its ID number, the name of its Maker, and its description, if any.

‑m lo

Lists the unprocessed transactions (awaiting the checker) of all the Makers except the transactions of the user who invoked the command.

‑m p

Processes a transaction. When the Checker (any admin user except the Maker who created the transaction) enters an ID number, all the commands in the specified transaction appear in a list.

This option does not work in the following circumstances:

• If one or more of the commands in the transaction pertain to the user who invoked the command.
• If the transaction is locked by a different Checker.
• If the transaction was created by the user who invoked the command-Makers cannot act as Checkers for their own transactions.
• If the specified transaction ID does not exist.
• If the user who invokes the command does not have the authority to be a Checker.

‑m r

Retrieves or locks a transaction.

• If you are the user who created the transaction (the Maker) this parameter retrieves a specific, unprocessed transaction. After you retrieve the transaction, you can direct it to an appropriate file and use the ASCII editor of your choice (vi, emacs, and so on) to update the transaction.
• If you are a user who is not the Maker (Checker) this parameter locks the transaction prior to processing. You cannot change a locked transaction.

transacationID

Specifies the unique identifying number that sepmdd gives to the transaction when it is created.

code

Specifies a numeric code that specifies what the Checker should do when processing the transaction:

0

Rejects the transaction, in which case all the commands in the transaction are deleted and no changes are implemented in the PMDB

1

Authorizes the transaction, in which case the commands are immediately implemented in the PMDB

2

Unlocks the transaction so that it can be processed later, or by a different Checker.