1. System Administrator's Guide
  2. Basic BRM System Administration
  3. Fine-Grained Opcode Tracing

6 Fine-Grained Opcode Tracing

Learn how to enable selective opcode tracing in an on-premises Oracle Communications Billing and Revenue Management (BRM) environment as part of the initiative to provide more granularity in error-code, class, and location reporting by Perflib.

Topics in this document:

Enabling Selective Opcode Tracing

Use the selective opcode tracing feature to control which opcodes are traced for flist and summary tracing (the default behavior is to trace all opcodes). You can enable selective opcode tracing at startup using a configuration file or during runtime using the pstatus application.

To enable selective opcode tracing at startup:

  1. Open the CM and Oracle DM Perflib environment files in a text editor:

    • CM: BRM_home/apps/perflib/perf.env

    • Oracle DM: BRM_home/apps/perflib/perf_dm.env

  2. Set PERFLIB_VAR_TRACE_OPCODES to a comma-separated list of opcodes to trace when using Perflib's full or summary flist tracing mode: 
    export PERFLIB_VAR_TRACE_OPCODES=opcodeNameOrNumber

    where opcodeNameOrNumber is either the name or number of a BRM opcode. If you list multiple opcodes, use a comma as a delimiter. If the parameter is empty or missing, Perflib traces all opcodes.

    For example, the following entry specifies to enable flist tracing only for opcodes PCM_OP_CUST_COMMIT_CUSTOMER and PCM_OP_SUBSCRIPTION_PURCHASE_DEAL (108):
    export PERFLIB_VAR_TRACE_OPCODES=PCM_OP_CUST_COMMITCUSTOMER,108
  3. Restart the CM and Oracle DM services to initialize the new configuration.

To enable selective opcode tracing for a CM or Oracle DM at runtime, run the pstatus application:

  • To enable tracing for specific opcodes on the CM:

    pstatus -FopcodeNameOrNumber BRM_home/apps/perflib/perflib_data.dat

  • To enable tracing for specific opcodes on the Oracle DM:

    pstatus –FopcodeNameOrNumber BRM_home/apps/perflib/perflib_data_dm_oracle_data.dat

Note:

The data file name used by Perflib must be unique per component, so it may have been modified if your deployment has multiple CM and DM processes deployed on a single host server.