Difference between revisions of "Test268 Section 6"
From MidrangeWiki
m |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
[[Category:Test268]] | [[Category:Test268]] | ||
| − | |||
| − | |||
[[Test268 Section 5|<< Previous Section]] | [[:Category:Test268|Home]] | [[Test268 Section 7|Next Section >>]] | [[Test268 Section 5|<< Previous Section]] | [[:Category:Test268|Home]] | [[Test268 Section 7|Next Section >>]] | ||
| Line 33: | Line 30: | ||
=== Use journaling in Commitment Control for data integrity === | === Use journaling in Commitment Control for data integrity === | ||
| + | |||
| + | |||
| + | [[Test268 Section 5|<< Previous Section]] | [[:Category:Test268|Home]] | [[Test268 Section 7|Next Section >>]] | ||
Latest revision as of 20:19, 5 August 2007
<< Previous Section | Home | Next Section >>
Contents
- 1 Section 6 - RPG data handling (10%)
- 1.1 Utilize embedded SQL in an RPG program
- 1.2 Differentiate between different options for communicating between application processes (e.g., data queues, data areas, parameters, user spaces)
- 1.3 Code and use I/O directly to/from Data Structures
- 1.4 Code and use nested Data Structures
- 1.5 Determine appropriate use of LIKEREC keyword
- 1.6 Determine appropriate use of LIKEDS keyword
- 1.7 Code multiple ways to use partial keys, including KLISTS, key Data Structures, and direct specification of key fields on I/O operations
- 1.8 Demonstrate how to convert character and numeric data fields containing date values into Date data types and vice versa
- 1.9 Use journaling in Commitment Control for data integrity
