1. Messages, Logs, and Cleanup
Chapter 15
Messages, Logs, and Cleanup

2. Understanding AS/400 System Operations
Overview
A message is a unit of communication
Messages not destroyed - kept in collections called logs
Cleanup - keeping old logs enough, but not too long
Understanding AS/400 System Operations

3. Understanding AS/400 System Operations
Four Logs Include
History (QHST):
Automatic.
Is kept in a physical file.
Job:
Automatic, but what is logged can be changed.
Is kept within active jobs or in spooled output files for completed jobs.
Understanding AS/400 System Operations

4. Four Logs Include (Continued)
Job accounting:
Not automatic; requires manual start.
Is kept in a journal.
Security audit:
Understanding AS/400 System Operations

5. Understanding AS/400 System Operations
Messages
Started as messages
History
Job log
Security-audit journal entries
Messages are sent to message queues
Understanding AS/400 System Operations

6. Understanding AS/400 System Operations
Message Queues
User currently signed on to the system
Each workstation
System operator
Programs running on the system
Understanding AS/400 System Operations

7. Understanding AS/400 System Operations
Messages to You
Break
Notify
Program
Understanding AS/400 System Operations

8. Message Constructions
Understanding AS/400 System Operations

9. Understanding AS/400 System Operations
CPA4002 Message Text
Understanding AS/400 System Operations

10. Understanding AS/400 System Operations
CPA4002 Field Data
Understanding AS/400 System Operations

11. System Operator Message Queue
QSYSOPR
Most important message queue
All batch jobs
Problems on the system
Hardware
Security
Software
Review the type of messages that go to QSYSOPR’s message queue
Understanding AS/400 System Operations

12. Understanding AS/400 System Operations
System Reply List
Messages requiring a reply
Almost always the same
Inquiry-only messages
Understanding AS/400 System Operations

13. Understanding AS/400 System Operations
 System Reply List
Understanding AS/400 System Operations

14. Changing System Reply List
Understanding AS/400 System Operations

15. Understanding AS/400 System Operations
History Logs (QHST)
History logs are:
Automatic.
Kept in a physical file.
This history log is named qhstyyjjjn where:
yy is the year on which the physical file was created.
jjj is the Julian date on which the physical file was created.
n is a sequence number (0-9, A-Z).
Understanding AS/400 System Operations

16. History Logs (QHST) (cont.)
Understanding AS/400 System Operations

17. History Logs (QHST) (cont.)
Understanding AS/400 System Operations

18. Understanding AS/400 System Operations
History Log Contents
Note highlighted line. It will be expanded in the next screen.
Understanding AS/400 System Operations

19. Expanded Message Screen
Understanding AS/400 System Operations

20. Understanding AS/400 System Operations
Job Logs
Job logs are:
Automatic, but what is logged can be changed
Are kept:
Within active jobs
In spooled output files for completed jobs
QPJOBLOG or QEZJOBLOG
Understanding AS/400 System Operations

21. Understanding AS/400 System Operations
Logging Level (cont.)
Logging level - what messages should be collected for job
Job Description provide characteristics
Three parts to the log parameter - Logging Level
Understanding AS/400 System Operations

22. Understanding AS/400 System Operations
Log Command Parameter
Understanding AS/400 System Operations

23. Understanding AS/400 System Operations
Logging Level Values
Level numeric code from 0 to 4.
0 nothing is logged.
1 messages sent to job’s external message queue and severity >= specified value.
2 level 1 messages plus:
Any requests/command from CL program with severity >= specified value.
All messages associated with those requests/commands with severity >= specified value.
Understanding AS/400 System Operations

24. Understanding AS/400 System Operations
Logging Level Values
Level numeric codes from 0 to 4 continued.
3 Level - 1 messages plus:
Level 2 messages plus:
All requests/commands being from a CL program.
Associated messages with requests/commands with severity >= specified value.
4 level - 1 messages plus:
Level 3 messages plus:
any message with severity >= specified value.
Understanding AS/400 System Operations

25. Logging Levels (continued)
Severity specifies level for requests/commands/messages logged.
Severity range 00 to 99.
00 informational only.
99 last message before abnormally end.
serious job messages 30 or higher.
Text - message text written to job log. All messages on the AS/400 have two levels.
Level 1- short, 80-bytes-or-less version.
Level 2 - long version - second level message.
Understanding AS/400 System Operations

26. Logging Levels (continued)
The possible values for text are:
*MSG—only level 1 text written to log.
*SECLVL—level 2 - second level messages written to log.
*NOLIST—no messages are logged unless abnormal end.
Understanding AS/400 System Operations

27. Understanding AS/400 System Operations
Displaying the Job Log
To display the job log from:
Current interactive job:
DSPJOBLOG
WRKJOB
Job active on system:
WRKUSRJOB
WRKACTJOB
Press System Request key
Sign off from session, log(*list) on sign-off command
Understanding AS/400 System Operations

28. Displaying the Job Log (Cont.)
To display the job log from:
Other job, do any of the following:
WRKUSRJOB, option 8 (display spooled file)
WRKOUTQ QPJOBLOG (or QEZJOBLOG)
Understanding AS/400 System Operations

29. Understanding AS/400 System Operations
Job Accounting
Job Accounting is:
Not automatic; requires manual start.
Data is kept in a journal receiver.
Understanding AS/400 System Operations

30. Understanding AS/400 System Operations
Job Accounting Tracks
Information about jobs
Who uses what
Tracks usage of:
Processing unit
Printer
Display stations
Database
Communications
Understanding AS/400 System Operations

31. Security Audit Journal
The security audit journal is:
Not automatic; requires manual start.
Data is kept in a journal receiver.
Understanding AS/400 System Operations

32. AS/400 Security Audit Journal
Must be set up first
Activated before use
Security-related activities
Operator sets up what is logged
Log in a journal
Understanding AS/400 System Operations

33. Understanding AS/400 System Operations
System Cleanup
Automatic Cleanup
User Profiles
Objects
Licensed Programs
Device Descriptions
Miscellaneous
Mention that for Licensed Programs you use the LICPGM menu to delete old software that is not needed.
Understanding AS/400 System Operations

34. Understanding AS/400 System Operations
Automatic Cleanup
Understanding AS/400 System Operations

35. Understanding AS/400 System Operations
User Profile Cleanup
Select option 4 to get next screen.
Understanding AS/400 System Operations

36. User Profile Cleanup (cont.)
Understanding AS/400 System Operations

37. User Profile Cleanup (cont.)
Understanding AS/400 System Operations

38. Understanding AS/400 System Operations
Object Cleanup
Two Options for System Operator to cleanup owned objects
Change Object’s ownership to another user profile
Delete the object
Understanding AS/400 System Operations

39. Understanding AS/400 System Operations
Object Cleanup
Understanding AS/400 System Operations

40. Device Descriptions Cleanup
WRKHDWRSC *xxx. Where xxx will be:
CMN for communications devices
LWS for local workstation devices
STG for storage resources
Understanding AS/400 System Operations

41. Miscellaneous Cleanup
Clear Save File (CLRSAVF) command.
Display File Description (DSPFD) determine files with large number of deleted records
Use RGZPFM command to reclaim deleted record space
Clear Message Queue (CLRMSGQ)
Delete the journal receivers after saving
Understanding AS/400 System Operations