Difference between revisions of "RPG/400"
From MidrangeWiki
< RPG
(→New stuff as of RPG/400) |
(→New stuff as of RPG/400) |
||
Line 13: | Line 13: | ||
* Massive new support for various kinds of Data Structures and Data Areas, which also can be Externally described | * Massive new support for various kinds of Data Structures and Data Areas, which also can be Externally described | ||
* Open and Close files | * Open and Close files | ||
+ | * Rename files and fields on input | ||
+ | ** Suppose you have two files with same record format names ... you can rename one to keep them straight ... for example if you accessing the same file more than once in the same program for different reasons | ||
+ | ** Suppose naming convention of some files are such that the same field name ends up in two or more files ... you can do renaming to avoid aliases | ||
+ | ** You can also do renaming to make it easier to see what the function of some field names are in this program | ||
* Key Lists for access to indexed files | * Key Lists for access to indexed files | ||
* Expansion to the controls on accessing a file where | * Expansion to the controls on accessing a file where |
Revision as of 13:00, 7 June 2005
Note that
- RPG/400 can do just about anything that earlier versions of RPG such as RPG III could do and a whole lot more,
- while RPG 4 can do just about anything that RPG/400 could do and a whole lot more.
New stuff as of RPG/400
This is from the perspective of someone moving from RPG on S/36 SSP to RPG on the 400. Some of these capabilities may have existed with RPG on S/38.
- Test a field for various kinds of validity before processing it
- External File Definition Support. Previously we just had Internal File Definitions. Innitially Externally Described Files were programmed using DDS and later SQL.
- Massive new support for various kinds of Data Structures and Data Areas, which also can be Externally described
- Open and Close files
- Rename files and fields on input
- Suppose you have two files with same record format names ... you can rename one to keep them straight ... for example if you accessing the same file more than once in the same program for different reasons
- Suppose naming convention of some files are such that the same field name ends up in two or more files ... you can do renaming to avoid aliases
- You can also do renaming to make it easier to see what the function of some field names are in this program
- Key Lists for access to indexed files
- Expansion to the controls on accessing a file where
- Many new structured programming capabilities in conjunction with IFxx
- Refer to indicators using *IN## *ON or *OFF
- Concatenation and Substringing
- Scan a file to locate some character string, and record where it is (byte count sideways)
- CALL a sub-program and be-called, with parameters passed between them
- Output an interactive screen to the users, then read it back in and act on the data provided