Type Go SERVICE or GO CMDSRVAGT to view the many options for the system service agent.

Generally, if you don’t know how to use the various service logs, you shouldn’t have access to any service functions.

Tom

Maybe he mean service action log of Hardware Service Manager in System Service Tools.
Try run STRSST command.

I heard it from my collegues..thats it

The Product Activity Log, the Licensed Internal Code log and any others are created for “service” actions. They are meaningful to “service” personnel, which usually means some level of IBM Support.

When such service is needed and IBM Support (or 3rd-party) is available, IBM will direct you in any needed actions. They know which logs they’ll want to review and will tell you how to access them.

When there is no contracted Support, the various service logs are unlikely to do any good for anyone except perhaps determined hobbyists working on their personal systems. Without Support, entries in service logs generally can’t be dealt with anyway.

There are logs that are available outside of “service” activities. E.g., you can use PRTERRLOG to review a variety of statistics and conditions. DSPPRB can print general info about ‘problems’ logged by the system. PRTINTDTA can print some detailed problem analysis data. Those commands have help text that gives overviews of their purposes. Most variations are harmless to run (but can sometimes generate very large spooled files.)

A number of “logs” exist that can be viewed or printed. Whether or not a particular one that is outside of System Service Tools should be called a “service log” might depend on semantic interpretation.

Tom