32 Customer Management Utilities

Learn about the Oracle Communications Billing and Revenue Management (BRM) customer management utilities.

Topics in this document:

• load_config_business_event

• load_pin_business_profile

• load_pin_customer_segment

• load_pin_notify

• load_pin_verify

• load_transition_type

• pin_contracts

• pin_deferred_act

• pin_deposit_calc_interest

• pin_deposit_release_purchased_deposit

• pin_deposit_transfer_deposit

• pin_gen_notifications

• pin_monitor_balance

• pin_product_clear

• pin_state_change

load_config_business_event

Use this utility to load or retrieve the list of business events that can be associated with notification specifications. This list is stored in the /config/business_events object and displayed in the Billing Care Trigger Criteria screen.

For more information, see "Configuring Billing Care to Display Business Events".

Note:

To connect to the BRM database, this utility needs a configuration (pin.conf) file in the directory from which it is run. For information about creating configuration files for BRM utilities, see "Connecting BRM Utilities" in BRM System Administrator's Guide.

Location

BRM_home/bin

Syntax

load_config_business_event [-n filename] [-w filename] [-p filename] [-o filename] [-r] [-d] [-h] [-v]

Parameters

-n filename

Creates a new /config/business_events object by loading the contents of the XML file into the database schema.

-w filename

Writes information from the /config/business_events object into the specified XML file.

-p filename

Loads business events from the payload_config file in XML format. If this option is not provided, it loads from the business_events file format.

-o filename

Loads business events from the specified XML file and overwrites entries in the /config/business_events object. Duplicates are ignored.

-r

Deletes all instances of the /config/business_events object from the BRM database.

-d

Creates a log file for debugging purposes. Use this parameter for debugging when the utility appears to have run with no errors but the configuration objects have not been loaded into the database.

-h

Displays the syntax and parameters for this utility.

-v

Displays information about successful or failed processing as the utility runs.

Results

If the load_config_business_event utility does not notify you that it was successful, look in the utility log file (load_config_business_event.pinlog) to find any errors. The log file is either in the directory from which the utility was started, or in a directory specified in the configuration file.

load_pin_business_profile

Use this utility to load business profiles and validation templates into the BRM database.

See the following topics:

• About Business Profiles

• Setting Up Business Profiles and Validation Templates

• Editing the Business Profile Configuration File

Location

BRM_home/bin

Syntax

load_pin_business_profile [-d] [-h] [-r] [-t] [-v] filename

Parameters

-d

Creates a log file for debugging purposes. Use this parameter for debugging when the utility seemed to run without error but the data was not loaded into the database.

-h

Displays syntax and parameters for this utility.

-r

Retrieves the business profile and validation template data from the BRM database and saves it in an XML file.

-t

Runs the utility in test mode to validate the XML file against its schema definition. This option does not create, modify, or delete any business profile or validation template objects in your BRM database.

Note:

To avoid load errors based on XML content problems, run the utility with this option before loading data into the database.

-v

Displays information about successful or failed processing as the utility runs.

Note:

This parameter is always used in conjunction with other parameters and commands. It is not position dependent. For example, you can enter -v at the beginning or end of a command to initiate the verbose parameter. To redirect the output to a log file, use the following syntax with the verbose parameter. Replace filename.log with the name of the log file:

load_pin_business_profile other_parameters –v > filename.log

filename

The name and location of the business profile configuration file. The default file is BRM_home/sys/data/config/pin_business_profile.xml, but the utility can take any XML file name as a parameter as long as the file's contents conform to the appropriate schema definition.

If you copy filename to the same directory from which you run the load utility, specify only the file name. If you run the command in a different directory from where filename is located, you must include the entire path for the file.

In addition, filename must be in the same directory as the default BRM_home/sys/data/config/business_configuration.xsd file.

Results

This utility notifies you only if it encounters errors. Look in the default.pinlog file for errors. This file is either in the directory from which the utility was started or in a directory specified in the utility configuration file.

Note:

You must stop and restart the Connection Manager (CM) to make new business profile and validation template data available.

load_pin_customer_segment

Use this utility to load your customer segment definitions into the BRM database.

For information about customer segments, see "Creating and Managing Customer Segments".

Location

BRM_home/bin

Syntax

load_pin_customer_segment [-t] [-v] [-d] [-h] pin_customer_segment_file

Parameters

-t

Runs the utility in test mode to validate the XML file format against the XSD file, and does not load the data or overwrite any existing data. Use this option before loading data into the /config object.

-v

Displays information about successful or failed processing as the utility runs.

Note:

This parameter is always used in conjunction with other parameters and commands. It is not position dependent. For example, you can enter -v at the beginning or end of a command to initiate the verbose parameter. To redirect the output to a log file, use the following syntax with the verbose parameter. Replace filename.log with the name of the log file:

load_pin_customer_segment other_parameters –v > filename.log

-d

Creates a log file for debugging purposes. Use this parameter for debugging when the utility appears to have run with no errors, but the data has not been loaded into the database.

-h

Displays help information for using this utility.

pin_customer_segment_file

The name and location of the XML file that stores localized strings for customer segments. The XML file is referenced by the pin_business_configuration.xsd file; therefore these files must be located in the same directory. The default customer segment file is in BRM_home/sys/data/config.

If you copy the pin_customer_segment.xml file and the pin_business_configuration.xsd file to the same directory from which you run the load_pin_customer_segment utility, you do not have to specify either the path or the file name.

If you run the command in a different directory from where the pin_customer_segment.xml file is located, you must include the entire path for the file.

Results

The load_pin_customer_segment utility notifies you when it successfully creates the /config/customer_segment object.

If the load_pin_customer_segment utility does not notify you that it was successful, look in the utility log file (default.pinlog) to find any errors. The log file is either in the directory from which the utility was started, or in a directory specified in the configuration file.

Note:

You must restart the Connection Manager to start recording your customer login failure preferences.

load_pin_notify

Use this utility to add an event notification list to your BRM database. See "Loading the Event Notification List" in BRM Developer's Guide.

For general information about event notification, see "Using Event Notification" in BRM Developer's Guide.

Location

BRM_home/bin

Syntax

load_pin_notify [-d] [-v] [-h] pin_notify_file

Parameters

-d

Specifies debug mode. The utility logs messages to the default.pinlog file in the current directory or in a directory specified in the utility configuration file. Use this parameter for troubleshooting when the utility runs with no errors but the notification file is not loaded into the database.

-v

Displays information about successful or failed processing as the utility runs.

Note:

This parameter is always used in conjunction with other parameters and commands. It is not position dependent. For example, you can enter -v at the beginning or end of a command to initiate the verbose parameter. To redirect the output to a log file, use the following syntax with the verbose parameter. Replace filename.log with the name of the log file:

load_pin_notify other_parameters –v > filename.log

-h

Displays the syntax and parameters for this utility.

pin_notify_file

The name and location of the configuration file that contains the event notification list you want to load into your database. The default event notification configuration file, pin_notify, is in BRM_home/sys/data/config.

For more information, see "Merging Event Notification Lists" in BRM Developer's Guide.

Note:

If you copy the pin_notify_file to the same directory from which you run load_pin_notify, you do not have to specify the path or the file name.

Results

This utility notifies you when it successfully creates the /config/notify object.

If the utility does not notify you that it was successful, look in the utility log file (default.pinlog) to find any errors. The log file is either in the directory from which the utility was started or in a directory specified in the configuration file.

Note:

You must restart the Connection Manager to make new events and the corresponding opcodes available.

load_pin_verify

Use this utility to load your preferences for recording customer login failures into the BRM database. See "Recording Login Failures".

Location

BRM_home/bin

Syntax

load_pin_verify pin_verify_file

Parameters

pin_verify_file

The name and location of the file that contains preferences for recording login failures. The default pin_verify file is in BRM_home/sys/data/config.

Note:

If you copy the edited pin_verify file to the same directory from which you run the load_pin_verify utility, you do not have to specify the path or the file name.

Results

The load_pin_verify utility notifies you when it successfully creates the /config/verify object.

If the load_pin_verify utility does not notify you that it was successful, look in the utility log file (default.pinlog) to find any errors. The log file is either in the directory from which the utility was started, or in a directory specified in the configuration file.

Note:

You must restart the Connection Manager to start recording your customer login failure preferences.

load_transition_type

Use this utility to load custom bundle and package transition types into the BRM database.

For information, see "Creating Custom Transition Types for Bundles and Packages".

Location

BRM_home/bin

Syntax

load_transition_type [-v] [-d] [TransitionTypeFile]

Parameters

-v

Displays information about successful or failed processing as the utility runs.

-d

Creates a log file for debugging purposes. Use this parameter for debugging when the utility appears to have run with no errors, but the data has not been loaded into the database.

TransitionTypeFile

The name and location of the file that contains your custom transition types. By default, the utility uses pin_transition_type.

If you run the command in a different directory from where the pin_transition_type file is located, you must include the entire path for the file.

Results

This utility notifies you only if it encounters errors. Look in the default.pinlog file for errors. This file is either in the directory from which the utility was started or in a directory specified in the utility configuration file.

pin_contracts

Use this utility to renew customer contracts or cancel contracts that have expired.

Note:

To connect to the BRM database, this utility needs a configuration (pin.conf) file in the directory from which it is run. For information about creating configuration files for BRM utilities, see "Connecting BRM Utilities" in BRM System Administrator's Guide.

Location

BRM_home/bin

Syntax

pin_contracts [-renew | -expire | -expire-renewed] [-help] [-verbose] [-test]

Parameters

-renew

Renews all contracts that expire today and have auto-renewal enabled.

-expire

Cancels all non-renewable contracts that expire today.

-expire-renewed

Cancels all contracts that have already been renewed and are now at the end of their second commitment period.

-help

Displays the syntax and parameters for this utility.

-verbose

Displays information about successful or failed processing as the utility runs.

-test

Tests the utility, but does not affect accounts or contracts. Use this parameter to see which contracts would be renewed or canceled.

Results

If the pin_contracts utility does not notify you that it was successful, look in the utility log file (pin_contracts.pinlog) to find any errors. The log file is either in the directory from which the utility was started, or in a directory specified in the configuration file.

pin_deferred_act

Use this utility as part of your daily billing to run deferred actions. For example, if a CSR has scheduled an account to become inactive, the pin_deferred_act utility performs the status change on the scheduled date. This utility is included in the pin_bill_day script.

See "Scheduling Status Changes in Advance".

Location

BRM_home/bin

Syntax

pin_deferred_act [-report|-purge|-retry] [-deferred_notifications] 
                 [-opcode opcode_name] [-status pending|done|error]
                 [-start mm/dd/yy] [-end mm/dd/yy] [-verbose] [-test] [-help]

Parameters

-report

Displays the progress and current state of /schedule objects.

This parameter can take one or more of these options as search criteria to filter the results of your report:

• -opcode [opcode_name]

• -status pending|done|error

• -start mm/dd/yy or yyyy

• -end mm/dd/yy or yyyy

For example:

pin_deferred_act -report -start 01/10/03 -end 01/24/03 -verbose

-purge

Purges from the Oracle Communications Billing and Revenue Management (BRM) database all /schedule objects whose actions have been run successfully. This helps reduce the size of your database.

This parameter can take one or more of these options as search criteria for purging:

• -opcode [opcode_name]

• -status pending|done|error

• -start mm/dd/yy or yyyy

• -end mm/dd/yy or yyyy

For example:

pin_deferred_act -purge -start 01/10/03 -end 01/24/03 -verbose -opcode PCM_OP_BILL_MAKE_BILL_NOW

-retry

Retries all the /schedule objects whose schedule actions have failed to run and whose status is marked as ERROR.

This parameter can take one or more of these options as search criteria for purging:

• -opcode [opcode_name]

• -status pending|done|error

• -start mm/dd/yy or yyyy

• -end mm/dd/yy or yyyy

For example

pin_deferred_act -retry -start 01/10/03 -end 01/24/03 -verbose

-deferred_notifications

Runs deferred actions against /schedule/notification objects only. For information, see "About Events Occurring Outside of Delivery Times".

-opcode [opcode_name]

Used as search criteria by the –report, –purge, and –retry parameters for retrieving /schedule objects containing the specified opcode responsible for the deferred action.

For example:

pin_deferred_act -report -start 01/10/03 -end 01/24/03 -verbose -opcode PCM_OP_BILL_MAKE_BILL_NOW

-status pending|done|error

Used as search criteria by the –report, –purge, and –retry parameters for retrieving /schedule objects having the specified status.

For example:

pin_deferred_act -retry -start 01/10/03 -end 01/24/03 -verbose -status ERROR

-start mm/dd/yy or yyyy

-end mm/dd/yy or yyyy

Used as search criteria by the –report, -purge, and –retry parameters for retrieving /schedule objects with an execution date matching the start and end dates specified. The value you supply for the start date is inclusive, but the value for the end date is non–inclusive and also defaults to the current date. If a start date is not specified, this utility retrieves all valid /schedule objects up to the specified end date. If an end date is not specified, this utility uses the current date as the end date and retrieves all valid /schedule objects until the current date.

-verbose | -v

Displays information about successful or failed processing as the utility runs.

Note:

This parameter is always used with other parameters and commands. It is not position dependent. For example, you can enter -v at the beginning or end of a command to initiate the verbose parameter. To redirect the output to a log file, use the following syntax with the verbose parameter. Replace filename.log with the name of the log file:

pin_deferred_act any_other_parameter –v > filename.log

-test

Runs a test to find out how many accounts meet the criteria without performing the action. The test has no effect on the accounts. This is most useful when run with the -verbose option.

-help| -h

Displays the syntax and parameters for this utility.

Results

If the utility does not notify you that it was successful, look in the utility log file (default.pinlog) to find any errors. The log file is either in the directory from which the utility was started, or in a directory specified in the configuration file.

When it is called internally by the pin_bill_day script, the pin_deferred_act utility logs error information in the pin_mta.pinlog file.

pin_deposit_calc_interest

Use this utility to search for appropriate purchased deposits and calculate the interest amount based on the frequency.

The utility looks for the purchased deposits which match the following criteria:

• The balance amount and the deposit amount are greater than zero.

• The last interest calculation date is less than the current date and is not zero.

• The next interest calculation date is greater than or equal to the current date.

Note:

The final interest calculation frequency is calculated based on the interest offset and the offset unit. The offset unit value can be either days, weeks, months, or years. If the effective date is updated, the interest is calculated on daily basis.

Location

BRM_home /bin

Syntax

pin_deposit_calc_interest [-verbose] [-help]

Parameters

-verbose

Displays information about successful or failed processing as the utility runs.

-help

Displays the syntax and parameters for this utility.

Results

If pin_deposit_calc_interest does not notify you that it was successful, look in the utility log file (pin_deposit_calc_interest.pinlog) to find any errors. The log file is either in the directory from which the utility was started, or in a directory specified in the configuration file.

pin_deposit_release_purchased_deposit

Use this utility to search for purchased deposits for which the end date is less than the current system date, then release the deposit amount.

Location

BRM_home/bin

Syntax

pin_deposit_release_purchased_deposit [-help] [-verbose] [-test]

Parameters

-help

Displays the syntax and parameters for this utility.

-verbose

Displays information about successful or failed processing as the utility runs.

-test

Tests the utility but does not affect the purchased deposit. Use this parameter to check if the deposit amounts are releasing correctly.

Results

If pin_deposit_release_purchased_deposit does not notify you that it was successful, look in the utility log file (pin_deposit_release_purchased_deposit.pinlog) to find any errors. The log file is either in the directory from which the utility was started, or in a directory specified in the configuration file.

pin_deposit_transfer_deposit

Use this utility to transfer the deposit balance amount from one account or service to another account or service. The input for this utility is a CSV file.

Location

BRM_home/bin

Syntax

pin_deposit_transfer_deposit -f input_file.csv [-verbose] [-test] [-help]

Parameters

-f input_file.csv

Specifies the name and location of the file that specifies how BRM will transfer the deposit amount. For example, \deposit\transfer_deposit.csv.

For more information on the CSV file, see "About Transferring Multiple Deposits Simultaneously".

-verbose

Displays information about successful or failed processing as the utility runs.

-help

Displays the utility’s syntax and parameters.

Results

pin_deposit_transfer_deposit handles each deposit transfer as a separate transaction. If any single deposit transfer fails, BRM does not need to roll back the entire deposit transfer. Successful transfers remain in place.

If pin_deposit_transfer_deposit does not notify you that it was successful, look in the utility log file, ${PIN_LOG_DIR}/pin_deposits/pin_deposit_transfer_deposit.pinlog, to find any errors.

pin_gen_notifications

Use this utility to generate notifications either several days before or several days after the following occurs:

• A customer's balance expires

• A customer's bill is due

• A collections action is performed against a customer

• A customer's installment payment is due

• A customer's subscription expires

• A customer's subscription is due for renewal

• A customer's service lifecycle state changes

The utility determines when to generate notifications for expiring resources by reading the /config/notification_spec object.

For more information, see "About Generating Notifications In Advance" and "About Generating Notifications After an Event Occurs".

Note:

To connect to the BRM database, this utility needs a configuration (pin.conf) file in the directory from which it is run. For information about creating configuration files for BRM utilities, see "Connecting BRM Utilities" in BRM System Administrator's Guide.

Location

BRM_home/bin

Syntax

pin_gen_notifications  -custom BusinessEventName|-svc_lifestate_change|-balance_expiry|-product_expiry|
                       |-subscription_renewal_due|-bill_due|-collections_action [action]|-installment due_date|end_date
                       [-after_expiry] [-search_level self|account|bal_grp|service|billinfo] [-virtual_start_time timestamp]
                       [-start timestamp -end timestamp] [-file filename]
                       [-help] [-verbose] [-test]

Parameters

-custom BusinessEventName

Generates notification events for any custom business events.

-svc_lifestate_change

Generates the /event/notification/service/state_change/pre_expiry notification event for service lifecycle state changes a specified number of days before the event occurs.

Note:

If used with the -after_expiry parameter, it generates an /event/notification/service/state_change/post_expiry notification event for service lifecyle state changes a specified number of days ago.

-balance_expiry

Generates the /event/notification/balance/expiry notification event for each customer balance whose validity period expires in the specified number of days before the event occurs.

Note:

If used with the -after_expiry parameter, it generates an /event/notification/balance/post_expiry notification event for each customer balance whose validity expired the specified number of days ago.

-product_expiry

Generates an /event/notification/product/expiry notification event for each customer subscription that expires in the specified number of days.

Note:

If used with the -after_expiry parameter, it generates an /event/notification/product/post_expiry notification event for each customer subscription that expired the specified number of days ago.

-subscription_renewal_due

Generates an /event/notification/subscription/renewal_due notification event for each customer subscription that renews in the specified number of days.

Note:

If used with the -after_expiry parameter, it generates an /event/notification/subscription/post_renewal_due notification event for each customer subscription that was due for renewal a specified number of days ago.

-bill_due

Generates an /event/notification/billing/due notification event for each customer bill that is due in the specified number of days.

Note:

If used with the -after_expiry parameter, it generates an /event/notification/billing/post_due notification event for each customer bill that expired a specified number of days ago.

-collections_action [action]

Generates an /event/notification/collections_action/due notification event for each collections action that is almost due. If you run -collections_action without the action option, the utility generates notification events for all types of collections actions.

To generate notification events for just one collections action type, set the action option to one of the following:

• close_billinfo: Generates notifications before bill units are closed.

• collect_payment: Generates notifications before collections payments are due.

• dunning_letter: Generates notifications before dunning letters are sent to customers.

• finance_charge: Generates notifications before finance charges are applied to accounts.

• inactive_billinfo: Generates notifications before bill units are inactivated.

• invoice_reminder: Generates notifications before invoice reminders are sent to customers.

• late_fee: Generates notifications before late fees are applied to accounts.

• manual_action: Generates notifications before collections agents make phone calls to customers.

• promise_to_pay: Generates notifications before promise-to-pay payments are due.

• policy_action: Generates notifications before policy actions are performed for bill units.

• refer_to_outside_agency: Generates notifications before bill units are referred to an outside agencies.

• writeoff_billinfo: Generates notifications before bill units are written off.

Note:

If used with the -after_expiry parameter, it generates an /event/notification/collections_action/post_due notification event for each collections action that is past due.

-installment due_date | end_date

Generates an /event/notification/installment_schedule/due notification event for each installment that is due on the current date (-installment due_date) or that ends on the current date (-installment end_date).

Note:

If used with the -after_expiry parameter, it generates an /event/notification/installment_schedule/post_due notification event for each installment action that is past due.

-after_expiry

Generates notifications after an event has occurred. For example, a configured number of days after a customer's subscription has expired.

-virtual_start_time timestamp

The utility assumes the passed value as the current system time. The timestamp must be in the format mm/dd/yyyy-HH:mm:ss. For example: 04/23/2030-18:22:45.

-search_level self | account | bal_grp | service | billinfo

Consolidates multiple in-advance or post-expiration events that expire at the same time into one notification that is sent to an external notification application. You can consolidate events at different levels:

• -search_level self: Creates separate notifications for each business event.

• -search_level account: Creates a single notification for an account with multiple events expiring at the same time.

• -search_level bal_grp: Creates a single notification for a balance group with multiple events expiring at the same time.

• -search_level service: Creates a single notification for a service with multiple events expiring at the same time.

• -search_level billinfo: Creates a single notification for a bill unit with multiple events expiring at the same time.

-start timestamp -end timestamp

Specifies to search for objects that expire during the specified time period. The timestamp must be in the format mm/dd/yyyy-HH:mm:ss.

When this option is used, the time constraints in /config/notification_spec are ignored.

-file filename

Specifies to generate notification events for the objects listed in the specified file only. For information about the file's format and contents, see "Creating a File of POIDs".

-help

Displays the syntax and parameters for this utility.

-verbose

Displays information about successful or failed processing as the utility runs.

-test

Tests the utility by retrieving the list of balance resources that are about to expire, but it does not generate notification events.

Results

If the pin_gen_notifications utility does not notify you that it was successful, look in the utility log file (pin_gen_notifications.pinlog) to find any errors. The log file is either in the directory from which the utility was started, or in a directory specified in the configuration file.

pin_monitor_balance

Use this utility to update monitored balances and to check whether the balances have crossed thresholds.

For more information on using the pin_monitor_balance utility, see "Running pin_monitor_balance to Update Monitored Balances".

Note:

To connect to the BRM database, this utility needs a configuration file in the directory from which you run it. The pin.conf file for this utility is in BRM_home/apps/pin_monitor. See "Connecting BRM Utilities" in BRM System Administrator's Guide.

Location

BRM_home/bin

Syntax

pin_monitor_balance [-d] [-v] [-t] [-h]

Parameters

-d

Prints error logs for debugging.

-v

Displays detailed information on status and error messages as the utility updates balances and generates notification events.

-t

Runs a test to find out how many accounts meet the criteria without performing the action. The test has no effect on the accounts. This is most useful when run with the -v option.

-h

Displays the syntax and parameters for this utility.

Results

This utility generates notification events when a balance crosses a credit threshold. It logs errors in the log file, which is either in the directory from which the utility was started or in a directory specified in the configuration file.

pin_product_clear

Use this utility to purge data from the Audit Accounts Product table that is older than a specified time period. When you modify a charge offer, BRM records the details of the charge offer modifications in the AUDIT_ACCOUNTS_PRODUCT_T table. BRM stores audit data when a customer purchases an item charge offer and modifies or cancels an existing subscription charge offer.

Note:

The pin.conf file for this utility is located in BRM_home/apps/pinapps/pin_rerate. Run pin_product_clear from this directory.

Location

BRM_home/bin

Syntax

pin_product_clear   -n days -d mm/dd/yyyy [-verbose] [test] 
                    [-help]

Parameters

-n days

Deletes all records from the AUDIT_ACCOUNTS_PRODUCT_T table that are older than the number of days specified.

-d mm/dd/yyyy

Deletes all records from the AUDIT_ACCOUNTS_PRODUCT_T table that are dated prior to the midnight of the date you have specified.

-verbose

Displays information about successful or failed processing as the utility runs.

Note:

This parameter is always used in conjunction with other parameters and commands. It is not position dependent. For example, you can enter -verbose at the beginning or end of a command to initiate the verbose parameter. To redirect the output to a log file, use the following syntax, replacing filename.log with the name of the log file:

pin_product_clear other_parameters –verbose > filename.log

-test

Tests the utility, but does not affect the AUDIT_ACCOUNTS_PRODUCT_T table.

-help

Displays the syntax and parameters for this utility.

Results

If the pin_product_clear utility doesn't notify you that it was successful, look in the utility log file (pin_product_clear.pinlog) to find any errors. The log file is either in the directory from which the utility was started, or in a directory specified in the configuration file.

pin_state_change

Use this utility to perform bulk service state transitions based on the state expiration time. See "Creating Custom Service Life Cycles".

Location

BRM_home/bin

The configuration file for this utility is located in the BRM_home/apps/pin_state_change directory. Run pin_state_change from that directory.

Syntax

pin_state_change [-help] [-state] [-service] [-verbose]

Parameters

-help

Displays the syntax and parameters for this utility.

-state

Performs state transitions for services in this state only. Use the name of a state defined in the <NAME> element in a config_lifecycle_states.xml file.

-service

Performs state transitions for this service type only. Use the name of a BRM service type (/service/*) that uses a custom life cycle.

-verbose

Displays information about successful or failed processing as the utility runs.

Results

The log file specified in the utility's configuration (pin.conf) file records the following:

• The number of services for which this utility made a state change

• The number of state changes that were successful