# Active Service Operations with No Routings
LLMS index: [llms.txt](/llms.txt)
---
-
Target Database:
—
-
Context Type:
—
-
Alert Severity:
—
-
Triggered Time:
—
-
Firing Context:
—
## Active Service Operations with No Routings
**Report ID:** `ib-svcops-no-routing`
**Category:** Integration Broker
## Purpose
This report identifies active service operations that have no active routing definitions. These operations have at least one active version but cannot process any messages because no routing is configured to direct traffic to or from them. Usually this means a half-finished setup or an operation that should have been deactivated when its routings were.
## What It Detects
An operation is flagged when:
1. It has at least one active version (`ACTIVE_FLAG = 'A'` in PSOPRVERDFN)
2. It has **zero** active routings (`EFF_STATUS = 'A'` in PSIBRTNGDEFN)
The report also shows the count of inactive routings, which helps distinguish between operations that never had routings and those whose routings were intentionally deactivated.
## Tables Queried
### PSOPERATION — Service Operation Definitions
Paginated to discover all operations.
| Field | Description |
| ---------------- | ------------------------------ |
| IB_OPERATIONNAME | Operation name (primary key) |
| IB_SERVICENAME | Parent service name |
| RTNGTYPE | Routing type (S=Sync, A=Async) |
| DESCR | Short description |
### PSOPRVERDFN — Operation Version Definitions
| Field | Description | Filter |
| ----------- | ------------------------- | -------------------------- |
| VERSIONNAME | Version name (e.g., "v1") | |
| ACTIVE_FLAG | Version active status | At least one must be `'A'` |
### PSIBRTNGDEFN — Integration Broker Routing Definitions
| Field | Description | Filter |
| --------------- | ----------------------- | ----------------------------- |
| ROUTINGDEFNNAME | Routing definition name | |
| EFF_STATUS | Effective status | Must have **none** with `'A'` |
## Data Flow
```text
1. Paginate through all PSOPERATION records
(batches of 300)
|
v
2. For each operation, fetch full details
(versions, routings)
|
v
3. Filter to operations with at least one
active version (ACTIVE_FLAG = 'A')
|
v
4. Exclude operations that have any active
routing (EFF_STATUS = 'A')
|
v
5. Generate summary table of flagged operations
```
## Report Output
The generated report contains:
- **Summary** with total operations, active operations, and count flagged with no routings
- **Flagged operations table** with operation name (linked to detail page), service, type, active version count, inactive routing count, and description
- **Recommendations** for remediation actions
## Interpreting Results
- **Operations with zero total routings** likely never had routings configured. These may be newly created or inherited operations that were never fully set up
- **Operations with inactive routings only** suggest the routings were intentionally deactivated. Verify whether the operation itself should also be deactivated
- **Async operations** without routings are especially notable since they rely on routings for subscription/publication contracts
- **Sync operations** without routings cannot receive inbound requests
## Recommendations
1. **If the operation is needed:** Create and activate routing definitions to enable message processing
2. **If the operation is not needed:** Inactivate all versions to keep the IB configuration clean
3. **If routings exist but are inactive:** Review whether deactivation was intentional or an oversight