About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Troubleshooting
Problem
This document provides basic information about LIC logs (LICLOGS) .
Resolving The Problem
This document describes how to display Licensed Internal Code (LIC) logs and how to identify the common components of them. Not all LIC Logs indicate an error or a problem; however, they can describe an informational condition.
LIC Logs are usually described as a combination of their Major and Minor codes, for example, major code 1000 and minor code DDDD. However, searching for APARs and PMRs requires a LIC Log prefix of VL. For example, the documentation for this major/minor code is: VL1000DDDD.
Viewing LIC Logs
To view the LIC logs, do the following:
Identifying Components
Each LIC Log will have the same identifying components:
Entry ID:
Each LOG has a unique eight character entry identifier, which ranges from 00000000 to FFFFFFFF. By searching on 00000000 for the ID, the oldest LIC Log will be displayed. The default of FFFFFFFF will display the most recent LIC Logs. Some QSYSOPR messages will mention an eight character log ID, which is different from the eight character Major and Minor code combination.
Major Description:
Every Major Description corresponds with a Major Code. In the above example, every Major Description of 'IPL' is a Major Code of 0500. Conversely, every 0500 LIC Log is an IPL LIC Log.
Major Code:
A four character identifier for each type of LIC Log. In the above example, every 0200 Major Code is a Function Check LIC Log. Searching on just the Major Code will display only those types of LIC Logs.
Major
Code Description
0100 Machine check
0200 Function check
0300 Damage set
0301 Damage encountered
0302 Damage log request
0303 Damaged context rebuilt
0304 Damage assessment
03FF Test
0400 Tolerance
0401 LIC log interface
0402 Enable exception
0403 Tolerated exception
0404 EAO threshold
0405 Recovered object list
0406 Locking exception
0500 IPL
0501 End machine processing
0505 Object conversion
0600 Database
0700 Source/Sink
0701 Source/Sink information
0800 MI request
0A00 Machine index
0B00 Authority
0C00 Service function
0D00 Journal
0E00 Recovery
0F00 Commit
0F01 Transaction management
1000 Storage management
1001 ASP management
1100 Translator
1101 Optimizing translator
1200 Program management
1300 Process management
1400 Context management
1500 Module object manager
1600 Binder
1700 Resource management
1800 Product activity log
1900 Machine observation
1A00 Cryptography
1B00 Common function
1C00 Debug interpreter
1D00 Queue space
1E00 Low level I/O
1F00 Stream I/O
2000 System journal
2100 Synchronization
2200 Select
2300 Adv Sys 36 DLC
2400 Adv Sys 36 common DLC
2500 Adv Sys 36 BSC
2600 Adv Sys 36 services
2700 File server I/O proc
2800 Activation/Invocation
2900 Hardware service manage
2A00 MI transformer
2B00 Integrated file system
2C00 Local sockets
2C01 Fast response cache
2D00 System object model
2E00 Tape support
2F00 DASD manager
3000 Comm hardware driver
3100 Controller hdw driver
3200 Display hardware driver
3300 DASD support
3400 IOP support
3401 I/O concurrent maint
3402 Switchable I/O support
3500 Printer hardware driver
3600 I/O service
3700 I/O statistics
3800 Logical hdw resources
3900 Packaging hdw resources
3A00 Optical
3B00 ILAN communication
3C00 Process table
3C01 Kernel utilities
3D00 Modula-2 runtime
3E00 Virtual CD IOM
3F00 Virtual console IOM
4000 I/O protection
4100 Virtual tape IOM
4200 Performance data collec
4201 Perf collection service
4300 Java virtual machine
4400 Server message block
4401 NetBIOS on TCP/IP
4500 Transport layer interf
4600 Signals management
4700 OS/400 PASE
4800 Clustering
4900 Crypto hardware drivers
4A00 Error analysis
4B00 Telephony driver
4C00 Composite object group
4D00 Pseudo-terminal driver
4E00 Virtual I/O
FFFF Exception dump
Minor Code:
A four character value that corresponds to its Major Code. Not every Major Code will have a variety of Minor Codes. For example, 0600 Database LIC Logs tend to have several different Minor Codes. However, 0500 IPL LIC Logs can have just a few possible Minor Codes. If searching by Minor Code, a valid Major Code must also be specified.
Date and Time:
There will be times that no LIC Logs are written, depending upon what the system is doing. At other times, a lot of LIC Logs can be logged. LIC Logs can be searched by their date and time, especially if the Major Code or Entry ID are not known.
LIC Logs are usually described as a combination of their Major and Minor codes, for example, major code 1000 and minor code DDDD. However, searching for APARs and PMRs requires a LIC Log prefix of VL. For example, the documentation for this major/minor code is: VL1000DDDD.
Viewing LIC Logs
To view the LIC logs, do the following:
| 1. | On the operating system command line, type the following: STRSST Press the Enter key. |
| 2. | Sign on SST with the QSECOFR or QSECOFR equivalent authority profile and the corresponding password. |
| 3. | From the SST main menu, select Option 1, Start a Service Tool. |
| 4. | Select Option 5, Licensed Internal Code log. |
| 5. | Select Option 1, Select entries from the Licensed Internal Code (LIC) log. |
| 6. | At the screen titled Specify Licensed Internal Code Log Selection Values, pressing the Enter key will display the most recent LIC Log entries. However, LIC Logs can also be displayed by date range, type, or entry ID. |
Identifying Components
Each LIC Log will have the same identifying components:
| Entry ID |
Major Description |
Major Code |
Minor Code |
Date | Time |
| 01014C6D 01014C6E 01014C6F 01014C70 01014C71 01014C72 01014C73 01014C74 01014C75 |
IPL Resource management IPL Database Database Database Function check Function check Function check |
0500 1700 0500 0600 0600 0600 0200 0200 0200 |
0000 0731 ADFE 5CFC 5CFC AAAA 1720 1720 1720 |
05/02/06 05/02/06 05/02/06 05/02/06 05/02/06 05/02/06 05/02/06 05/02/06 05/02/06 |
05:37:10 05:37:14 05:39:32 05:39:40 05:39:40 05:40:16 08:03:06 08:13:25 08:19:16 |
Entry ID:
Each LOG has a unique eight character entry identifier, which ranges from 00000000 to FFFFFFFF. By searching on 00000000 for the ID, the oldest LIC Log will be displayed. The default of FFFFFFFF will display the most recent LIC Logs. Some QSYSOPR messages will mention an eight character log ID, which is different from the eight character Major and Minor code combination.
Major Description:
Every Major Description corresponds with a Major Code. In the above example, every Major Description of 'IPL' is a Major Code of 0500. Conversely, every 0500 LIC Log is an IPL LIC Log.
Major Code:
A four character identifier for each type of LIC Log. In the above example, every 0200 Major Code is a Function Check LIC Log. Searching on just the Major Code will display only those types of LIC Logs.
Major
Code Description
0100 Machine check
0200 Function check
0300 Damage set
0301 Damage encountered
0302 Damage log request
0303 Damaged context rebuilt
0304 Damage assessment
03FF Test
0400 Tolerance
0401 LIC log interface
0402 Enable exception
0403 Tolerated exception
0404 EAO threshold
0405 Recovered object list
0406 Locking exception
0500 IPL
0501 End machine processing
0505 Object conversion
0600 Database
0700 Source/Sink
0701 Source/Sink information
0800 MI request
0A00 Machine index
0B00 Authority
0C00 Service function
0D00 Journal
0E00 Recovery
0F00 Commit
0F01 Transaction management
1000 Storage management
1001 ASP management
1100 Translator
1101 Optimizing translator
1200 Program management
1300 Process management
1400 Context management
1500 Module object manager
1600 Binder
1700 Resource management
1800 Product activity log
1900 Machine observation
1A00 Cryptography
1B00 Common function
1C00 Debug interpreter
1D00 Queue space
1E00 Low level I/O
1F00 Stream I/O
2000 System journal
2100 Synchronization
2200 Select
2300 Adv Sys 36 DLC
2400 Adv Sys 36 common DLC
2500 Adv Sys 36 BSC
2600 Adv Sys 36 services
2700 File server I/O proc
2800 Activation/Invocation
2900 Hardware service manage
2A00 MI transformer
2B00 Integrated file system
2C00 Local sockets
2C01 Fast response cache
2D00 System object model
2E00 Tape support
2F00 DASD manager
3000 Comm hardware driver
3100 Controller hdw driver
3200 Display hardware driver
3300 DASD support
3400 IOP support
3401 I/O concurrent maint
3402 Switchable I/O support
3500 Printer hardware driver
3600 I/O service
3700 I/O statistics
3800 Logical hdw resources
3900 Packaging hdw resources
3A00 Optical
3B00 ILAN communication
3C00 Process table
3C01 Kernel utilities
3D00 Modula-2 runtime
3E00 Virtual CD IOM
3F00 Virtual console IOM
4000 I/O protection
4100 Virtual tape IOM
4200 Performance data collec
4201 Perf collection service
4300 Java virtual machine
4400 Server message block
4401 NetBIOS on TCP/IP
4500 Transport layer interf
4600 Signals management
4700 OS/400 PASE
4800 Clustering
4900 Crypto hardware drivers
4A00 Error analysis
4B00 Telephony driver
4C00 Composite object group
4D00 Pseudo-terminal driver
4E00 Virtual I/O
FFFF Exception dump
Minor Code:
A four character value that corresponds to its Major Code. Not every Major Code will have a variety of Minor Codes. For example, 0600 Database LIC Logs tend to have several different Minor Codes. However, 0500 IPL LIC Logs can have just a few possible Minor Codes. If searching by Minor Code, a valid Major Code must also be specified.
Date and Time:
There will be times that no LIC Logs are written, depending upon what the system is doing. At other times, a lot of LIC Logs can be logged. LIC Logs can be searched by their date and time, especially if the Major Code or Entry ID are not known.
Anecdotal Note: LIC logs are were initially known as VLOGs).
[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000C4BAAU","label":"IBM i"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]
Historical Number
418577676
Was this topic helpful?
Document Information
More support for:
IBM i
Component:
IBM i
Software version:
All Versions
Operating system(s):
IBM i
Document number:
637457
Modified date:
29 October 2024
UID
nas8N1014906
Manage My Notification Subscriptions