Difference between revisions of "Test268 Section 5"
From MidrangeWiki
(→Code and use Monitor operation code blocks) |
|||
| Line 29: | Line 29: | ||
=== Code and use Monitor operation code blocks === | === Code and use Monitor operation code blocks === | ||
| − | + | monitor; | |
| + | result = field1 / field2; | ||
| + | on-error *all; | ||
| + | result = 0; | ||
| + | endmon; | ||
[[Test268 Section 4|<< Previous Section]] | [[:Category:Test268|Home]] | [[Test268 Section 6|Next Section >>]] | [[Test268 Section 4|<< Previous Section]] | [[:Category:Test268|Home]] | [[Test268 Section 6|Next Section >>]] | ||
Revision as of 21:35, 30 November 2005
<< Previous Section | Home | Next Section >>
Contents
- 1 Section 5 - RPG performance and exception/error handling (9%)
- 1.1 Given user requirements, design and create physical and logical data relationships
- 1.2 Diagnose and resolve User Errors
- 1.3 Diagnose and correct application errors
- 1.4 Diagnose and correct system errors
- 1.5 Diagnose and eliminate errors for date data types and arithmetic overflow
- 1.6 Given a simple performance problem, determine appropriate course of action
- 1.7 Code and use INFDS, INFSR, SDS, and *PSSR
- 1.8 Code and use Monitor operation code blocks
Section 5 - RPG performance and exception/error handling (9%)
Given user requirements, design and create physical and logical data relationships
Diagnose and resolve User Errors
Diagnose and correct application errors
Diagnose and correct system errors
Diagnose and eliminate errors for date data types and arithmetic overflow
Given a simple performance problem, determine appropriate course of action
Code and use INFDS, INFSR, SDS, and *PSSR
Code and use Monitor operation code blocks
monitor; result = field1 / field2; on-error *all; result = 0; endmon;
