1 / 40

Messages, Logs, and Cleanup

Understanding AS/400 System Operations. 2. Overview . A message is a unit of communicationMessages not destroyed - kept in collections called logsCleanup - keeping old logs enough, but not too long . Understanding AS/400 System Operations. 3. Four Logs Include. History (QHST):Automatic.Is kep

marty
Download Presentation

Messages, Logs, and Cleanup

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. Chapter 15 Messages, Logs, and Cleanup

    2. 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

    3. 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.

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

    5. Messages Started as messages History Job log Security-audit journal entries Messages are sent to message queues

    6. Message Queues User currently signed on to the system Each workstation System operator Programs running on the system

    7. Messages to You Break Notify Program

    8. Message Constructions

    9. CPA4002 Message Text

    10. CPA4002 Field Data

    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 QSYSOPRs message queueReview the type of messages that go to QSYSOPRs message queue

    12. System Reply List Messages requiring a reply Almost always the same Inquiry-only messages

    13. System Reply List

    14. Changing System Reply List

    15. 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).

    16. History Logs (QHST) (cont.)

    17. History Logs (QHST) (cont.)

    18. History Log Contents Note highlighted line. It will be expanded in the next screen. Note highlighted line. It will be expanded in the next screen.

    19. Expanded Message Screen

    20. 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

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

    22. Log Command Parameter

    23. Logging Level Values Level numeric code from 0 to 4. 0 nothing is logged. 1 messages sent to jobs 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.

    24. 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 2 messages plus: Level 3 messages plus: any message with severity >= specified value.

    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 - short, 80-bytes-or-less version. Level 2 - long version - second level message.

    26. Logging Levels (continued) The possible values for text are: *MSGonly level 1 text written to log. *SECLVLlevel 2 - second level messages written to log. *NOLISTno messages are logged unless abnormal end.

    27. 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 Other job, do any of the following: WRKUSRJOB, option 8 (display spooled file) WRKOUTQ QPJOBLOG (or QEZJOBLOG)

    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)

    29. Job Accounting Job Accounting is: Not automatic; requires manual start. Data is kept in a journal receiver.

    30. Job Accounting Tracks Information about jobs Who uses what Tracks usage of: Processing unit Printer Display stations Database Communications

    31. Security Audit Journal The security audit journal is: Not automatic; requires manual start. Data is kept in a journal receiver.

    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

    33. 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.Mention that for Licensed Programs you use the LICPGM menu to delete old software that is not needed.

    34. Automatic Cleanup

    35. User Profile Cleanup Select option 4 to get next screen.Select option 4 to get next screen.

    36. User Profile Cleanup (cont.)

    37. User Profile Cleanup (cont.)

    38. Object Cleanup Two Options for System Operator to cleanup owned objects Change Objects ownership to another user profile Delete the object

    39. Object Cleanup

    40. Device Descriptions Cleanup WRKHDWRSC *xxx. Where xxx will be: CMN for communications devices LWS for local workstation devices STG for storage resources

    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

More Related