Message format
Messages that are logged by IBM® Verify Identity Access adhere to message standards. Each message consists of a message identifier (ID) and accompanying message text.
Message ID format
A message ID consists of 10 alphanumeric characters that uniquely identify the message.
- Three-character product identifier
- Two-character or three-character component or subsystem identifier
- Three-digit or four-digit serial or message number
- One-character type code that indicates the severity of the message
The figure that follows shows a graphical representation of a possible message ID and identifies its different parts. (Some messages might use 2 characters for the component ID and 4 digits for the serial number.)

Component identifiers
The component identifier indicates which component or subsystem produced the message.
- ADM
- Administration commands
- AUD
- Audit
- AUT
- Authentication service
- CC
- Common Auditing and Reporting Service disk cache
- CE
- Common Auditing and Reporting Service emitter
- CFG
- Configuration properties
- CO
- Common Audit Service Configuration Console
- CON
- Verify Identity Access console
- CTG
- Authorization service
- CTJ
- Single Sign On for Bluemix service
- DIS
- Directory Integrator component used by Single Sign On
- DPW
- Secure reverse proxy
- FBT
- Protocol service
- FDB
- Database
- FMS
- Management service
- ELA
- End-user license agreement
- HRD
- HTTP redirect
- IAS
- Single sign-on administration
- IDA
- Single sign-on administration
- IDS
- Identity service
- IN
- Common Auditing and Reporting Service installation
- ISJ
- Alias service JDBC component
- ISL
- Alias service LDAP component
- KES
- Key encryption and signature service
- KJK
- Key encryption and signature service Java KeyStore
- KQA
- Knowledge questions
- LOG
- Logging
- MB
- Common Audit Service Configuration MBean
- MET
- Metadata handling
- MGT
- Management
- MOD
- Module
- OAU
- OAuth 2.0
- OTP
- One-time password
- PWD
- Password handling
- RBA
- Context-based access
- RPT
- Report messages
- RTE
- Runtime environment component configuration
- SDK
- Software development kit
- SO
- Single Sign On service
- SOC
- SOAP client
- SPS
- Single sign-on protocol service
- STM
- Secure token service
- STS
- Secure token service modules
- STZ
- RACF® PassTicket tokens
- SU
- Common Audit Staging Utility
- SYS
- System alert messages
- TAC
- Verify Identity Access configuration
- TRC
- Trust client
- UPD
- Username password
- UTI
- Utility
- WS
- Common Auditing and Reporting Service Mobile service
- WSS
- Mobile services security management
- XS
- Common Audit Service XML data store
- XU
- Common Audit Service XML store utilities
Severity
Associated with each message is a severity level that indicates whether corrective action must be taken.
| Severity | Description |
|---|---|
| I (Informational) | Provides information or feedback about normal
events that occur. In general, no action needs to be performed in
response to an informational message. |
| W (Warning) | Indicates that a potentially undesirable
condition has occurred, but processing can continue. Intervention
or corrective action might be necessary in response to a warning message. |
| E (Error) | Indicates that a problem has occurred that
requires intervention or correction before processing can continue.
An error message might be accompanied by one or more warning or informational
messages that provide additional details about the problem. |
Message text
The text of the message, in the system locale, also is recorded in the log file. If the message text is not available in the language that you want, the English language text is used.