# LICENSE STATUS

## Qualifiers:

None

## Purpose:

This command provides the following license status information:

- License violation level

- Length of time in license violation mode

- Time until the license violation level escalates

- Cause of license violation event on the local system (if applicable)

- Cause of license violation on the application group (if applicable)

- Status of "Try as You Buy" licenses

The system's Licensing Model determines how much information is provided. If the system is operating in "standalone" or "non-shared enterprise" mode, information for the local node is provided. If the system is operating in "shared enterprise" mode, information for the entire application group is provided (if it is available).

## Details:

### License Violation Levels:

- Clear

- Warning

- Minor

- Major

- Critical

- System Lock

### Cause of License Violation Events:

- Over Allocation

- Missing DLM

- Missing Application Group Member

- Core Package Capability Exceeded (Local Limits exceeded)

- License Keys Cannot be Validated

- System ID Mismatch

- SDS is off

- Duplicate System

- Multiple DLMs

- VApp Environment

- Failure of Required Synchronization with the AMC

- Application Group is in LV

- "licensekeys” or “licensecert” file Tampering

## Examples:

### Entry: LICENSE STATUS

System Response:

### Example 1

Example 1 shows a system response where the system has missed a synchronization with the AMC. If the system misses two more synchronizations it will be in license violation.

License Violation Level: Clear

Time to next AMC Sync: 2 days, 23 hours

Number of missed AMC Syncs: 1

### Example 2

Example 2 shows a system response where the license violation level is "Critical" (the second highest level) due to a local event.

License Violation Level: Critical

Length of time at current License Violation Level: 2 days.

Time remaining until next escalation: 4 days, 23 hours

Local Violation Cause(s): Over Allocation, Core Package Capability Exceeded

### Example 3

Example 3 shows a system response where the license violation level is "System Lock" (the highest level) due to a local event.

License Violation Level: System Lock

Length of time at current License Violation Level: 1 days.

Time to next AMC Sync: 3 days, 2 hours

Number of missed AMC Syncs: 0

Local Violation Cause(s): Core Package Capability Exceeded

### Example 4

Example 4 shows a system response where the license violation level is "System Lock" due to events that have occurred on other members of the application group. The example also shows that the local system is not in license violation mode.

License Violation Level: System Lock

Length of time at current License Violation Level: 1 days.

Time to next AMC Sync: <nn> days, 2 hours

Number of missed AMC Syncs: 0

Local Violation Cause(s):

Member 1 Violation Cause(s): Over Allocation

Member n Violation Cause(s): System ID Mismatch

TBYB - IP User Licenses is in trial, 72 hours remain in trial.

TBYB - External Hot Desk User Licenses is in trial, 48 hours remain in trial.

### Example 5

Example 5 shows a system response where the local system cannot determine the license violation level of the application group members.

License Violation Level: Major

Length of time at current License Violation Level: 3 days.

Time to next AMC Sync: 2 days, 10 hours

Number of missed AMC Syncs: 0

Local Violation Cause(s): Application Group is in LV