> # Multiplatform Log Messages

> Some log messages are generated by a Service Task, and are not platform-specific. These messages begin a service name and in some cases a threadid, followed by the name of the service and a specific error message.

> See "Error Messages" for the specific details on the error code.

> VAIL021E | Tnnnnnnn-ServiceName@Hostname>,ErrorCode=<xxxx>, ErrorMessage=<tttttttttt>.
> | Severity: | Error
> | Explanation: | This is a generic message that is used for different purposes.
> VAIL022W | Tnnnnnnn-ServiceName@Hostname>,ErrorCode=<xxxx>, ErrorMessage=<tttttttttt>.
> | Severity: | Warning
> | Explanation: | The explanation depends on the exact nature of the failure.
> | System action: | The system action depends on the exact nature of the failure.
> | User response: | The user response depends on the exact nature of the failure.
> VAIL023I | Tnnnnnnn-ServiceName@Hostname>,ErrorCode=<xxxx>, ErrorMessage=<tttttttttt>.
> | Severity: | Information
> | Explanation: | The explanation depends on the exact nature of the failure.
> | System action: | The system action depends on the exact nature of the failure.
> | User response: | The user response depends on the exact nature of the failure.
> VAIL024T | Tnnnnnnn-ServiceName@Hostname>,ErrorCode=<xxxx>, ErrorMessage=<tttttttttt>.
> | Severity: | Trace
> | Explanation: | The explanation depends on the exact nature of the failure.
> | System action: | The system action depends on the exact nature of the failure.
> | User response: | The user response depends on the exact nature of the failure.
> VAIL109T | Thrdid(tttttttt) SAPI passing control to Application.
> | Severity: | Trace
> | Explanation: | After the worker thread was initialized, control was passed to the application.
> | System action: | None.
> | User response: | None.
> VAIL112E | Thrdid(________) SAPI control returned from Application with rc(__).
> | Severity: | Error
> | Explanation: | The ServiceApplication returned from MAIN with a nonzero return code.
> | System action: | If rc= 8, the Thread Control Block (TCB) will be abended to force DB2 to roll back the Unit of Work (UOW). This message is followed by VAIL113E. If any other return code is reported, the return code is ignored.
> | User response: | None.
> VAIL113E | Thrdid(________) Application requested an Abend.
> | Severity: | Error
> | Explanation: | The ServiceApplication returned from MAIN with rc(8).
> | System action: | This message follows a VAIL112E message. The Thread Control Block will be abended to force DB2 to roll back the Unit of Work.
> | User response: | None.
> VAIL114E | Threadid - SAF service failed for callable service (callname); rc=rr; reason=X'ssssssss'.
> | Severity: | Error
> | Explanation: | The given Security Server RACF Callable Service call failed. Threadid: Identifies the thread. callname: Identifies the name of the callable service, R_usermap or R_ticketserv. rr: Identifies the return code. ssssssss: Identifies the reason code.
> | System action: | The user logon will fail.
> | User response: | Refer to the reason code in your z/OS Security Server RACF Callable Services for the recommended user response.
> VAIL115E | Threadid - No RACF user found for principal pppp.
> | Severity: | Error
> | Explanation: | Threadid: Identifies the thread. pppp: The Kerberos principal was not defined in the RACF KERBLINK profile.
> | System action: | The user logon will fail.
> | User response: | Map the Kerberos principal to a RACF user using the RACF KERBLINK profile.