Checking jobs, job logs, and message logs

You can view jobs, job logs, and messages to identify problems and make adjustments to solve them.

If you are having problems with TCP/IP connectivity, you should take a look at the jobs that are running on your system. All work on your system is performed through jobs. Most jobs have associated job logs that record the jobs' activities. The job log contains information, such as when the job starts and ends, which commands are running, and error messages. Here are some ways to use jobs and job logs to help solve your TCP/IP problems.

• Verifying that necessary jobs exist
  TCP/IP requires that certain basic jobs are running. You can verify that these basic jobs are running.

• Checking the job logs for error messages and other indication of problems
  You can use job logs to help identify the source of your problem.

• Changing the message logging level on job descriptions and active jobs
  If you are having problems with TCP/IP or the server jobs, you might need to change the message logging level text value on the job description or on the active job associated with your TCP/IP server.

• Other job considerations
  Considerations regarding the job log maximum size and the resulting job actions might help you solve the problem.

Parent topic: