17)If a message breaks on an AS/400 system, how do you find out what caused it to break?

Answer 1

WOW. AS/400. not many of them still running. you need to be a lot more specific. Error message? Application message? email message? breaks in what way?
general troubleshooting though means look through the log files. and try to reproduce the problem so you can observe the state of the system when the breakdown occurs.

And as the old saying goes: "A reboot forgives many sins" Even on an old horse like an AS/400

Answer 2

You can place your cursor on the message and hit F1....this will give you the full message detail but no joblog details.

go back to the command line and do WRKACTJOB....put your cursor on the STATUS column and press F16(Shift f4 on a regular keyboard) to sort the column alphabetically. Then press F8 put MSGW in the "String" line and *STS in the "Column" line. This will bring you to all the jobs in a message (IF ANY).

On the job in question put a 5-ENTER then F10. This will bring up the full joblog for that job. Scroll through the joblog to find any information that may have directly or indirectly caused the job to go into a message.........at anytime, you can put your cursor on any part of the joblog and press F1 for further information.

Hope this helps

PS: The AS/400, now known as iSeries or System i is not old....it is still full time and is fully current and in the business community. It is a VERY powerful machine able to handle much more than a M$ server anytime.