Difference between revisions of "DDS"
m |
MrDolomite (talk | contribs) m (wiki formatting cleanup) |
||
| (12 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | {{AN}} is an acronym which stands for {{bu|D|ata}} {{bu|D|escription}} {{bu|S|pecifications}}. | |
| − | |||
| − | |||
| − | |||
This "programming language" is used to define the layout of files, both physical and logical, interactive and prompt screens, reports, and various other kinds of objects in the 400 family. | This "programming language" is used to define the layout of files, both physical and logical, interactive and prompt screens, reports, and various other kinds of objects in the 400 family. | ||
| Line 10: | Line 7: | ||
The objects created by DDS do not DO anything like a program, but rather they are layouts for the data to be processed by a program. | The objects created by DDS do not DO anything like a program, but rather they are layouts for the data to be processed by a program. | ||
| − | Think similar to [[SDA]] which is one way that menus, screens, and so forth were created prior to DDS. Prior to [[RPG/400]] we did not use externally defined print files, but internally defined then within the programs that were generating the reports. | + | Think similar to [[SDA]] which is one way that menus, screens, and so forth were created prior to DDS; and also [[UIM]] which [[BPCS]] uses to create help screens. Prior to [[RPG/400]] we did not use externally defined print files, but internally defined then within the programs that were generating the reports. |
| + | |||
| + | {{See also|Files}} | ||
| + | |||
| + | ==Categories== | ||
| + | [[Category:Programming]] | ||
| + | [[Category:Database]] | ||
| + | [[Category:Displays Programming]] | ||
Latest revision as of 17:13, 27 February 2007
DDS is an acronym which stands for Data Description Specifications.
This "programming language" is used to define the layout of files, both physical and logical, interactive and prompt screens, reports, and various other kinds of objects in the 400 family.
On S/36 SSP prior to RPG/400 and DDS, we were able to use alternate index files, which were conceptually similar to the logical access files of 400 today.
The objects created by DDS do not DO anything like a program, but rather they are layouts for the data to be processed by a program.
Think similar to SDA which is one way that menus, screens, and so forth were created prior to DDS; and also UIM which BPCS uses to create help screens. Prior to RPG/400 we did not use externally defined print files, but internally defined then within the programs that were generating the reports.
- See also: Files
