Content deleted Content added
PHProgrammer (talk | contribs) |
→External links: {{Hewlett-Packard software}} |
||
| (36 intermediate revisions by 26 users not shown) | |||
Line 1:
{{Short description|Fourth-generation programming language}}
{{
{{Infobox software
| name = UNICOM PowerHouse
|logo =
| logo alt = Unicom Systems corporate logo
| screenshot =
| caption =
| author =
| developer = UNICOM Systems, a division of [[UNICOM Global]]
| latest_release_version =
| latest_release_date =
| operating_system =
| genre =
| license = [[Proprietary software]]
| website = {{URL|https://teamblue.unicomsi.com/products/powerhouse-4gl/}}
}}
'''PowerHouse''' is
* ''QDD, or Quasar Data Dictionary'': for building a central data dictionary used by all other components
* ''QDesign'': a character-based [[screen generator]]
* ''Quick'': an interactive, character-based screen processor (running screens generated by QDesign)
* ''Quiz'': a report writer
Line 9 ⟶ 25:
== History ==
PowerHouse was introduced in 1982 and bundled together in a single product Quiz and Quick/QDesign, both of which had been previously available separately, with a new batch processor QTP. In 1983, Quasar changed its name to ''[[Cognos]] Corporation'' and began porting their application development tools to other platforms, notably [[Digital Equipment Corporation]]'s
The PowerHouse language represented a considerable achievement.{{According to whom|date=March 2011}} Compared with languages like
▲PowerHouse was introduced in 1982 and bundled together in a single product Quiz and Quick/QDesign, both of which had been previously available separately, with a new batch processor QTP. In 1983, Quasar changed its name to ''[[Cognos]] Corporation'' and began porting their application development tools to other platforms, notably [[Digital Equipment Corporation]]'s ''[[VAX]]'', [[Data General]]'s ''[[Eclipse MV]]'', and [[IBM]]'s ''[[AS/400]]'', along with the [[UNIX]] platforms from these vendors. Cognos also began extending their product line with add-ons to PowerHouse (for example, ''Architect'') and end-user applications written in PowerHouse (for example, ''MultiView''). {{Fact|date=February 2007}} Subsequent development of the product added support for platform-specific relational databases, such as HP's ''Allbase/SQL'', DEC's ''[[Oracle_Rdb | Rdb]]'', and [[Microsoft]]'s ''[[ Microsoft_SQL_Server | SQL Server]]'', as well as cross-platform relational databases such as [[Oracle_Database | Oracle]], [[Sybase_SQL_Server | Sybase]], and [[IBM]]'s [[IBM_DB2 | DB2]].
▲The PowerHouse language represented a considerable achievement. Compared with languages like ''[[COBOL]]'', [[Pascal programming language|''Pascal'']] and ''[[PL/1]]'', ''PowerHouse'' substantially cut the amount of labour required to produce useful applications on its chosen platforms. It achieved this through the use of a central data-dictionary, a compiled file that extended the attributes of data fields natively available in the DBMS with frequently used programming idioms such as:
* display masks
* help and message strings
* range and pattern checks
* help and information texts.
In order to support the data dictionary, PowerHouse was tightly coupled to the underlying database management system and/or file system on each of the target platforms. In the case of the HP3000 this was the ''[[TurboIMAGE
Once described in the data dictionary, there was no further need to describe the attributes through any of the applications unless there was a need to change them on the fly, for example, to change the size of an item to make it fit within the constraints of a defined item.
Simple QUICK screens could be generated in as few as
SCREEN <screenname>
FILE <filename>▼
GENERATE▼
GO▼
{{code|<screenname>}} was the name of the screen that the programmer assigned to the program. {{code|<filename>}} was the file name to be accessed in the data dictionary. Whether the items in the file would all fit in the screen would be determined by how many items and the size of them. If they didn't all fit, the program would have to be modified to eliminate unneeded items, change the size of items to some other size, etc. But, for a file with only a couple of items in it, it is quick and easy to generate a screen for data entry, deletion, or to
▲FILE <filename>
▲GENERATE
ACCESS <filename>▼
▲GO
REPORT ALL▼
GO▼
▲<screenname> was the name of the screen that the programmer assigned to the program. <filename> was the file name to be accessed in the data dictionary. Whether the items in the file would all fit in the screen would be determined by how many items and the size of them. If they didn't all fit, the program would have to be modified to eliminate unneeded items, change the size of items to some other size, etc. But, for a file with only a couple of items in it, it is quick and easy to generate a screen for data entry, deletion, or to simple look up data by an index.
▲Simple QUIZ reports were almost as easy. A one file report was a simple as:
▲ACCESS <filename>
▲REPORT ALL
▲GO
All items in the file would be sent to the screen, maybe not in the most desired fashion, but that simple.
Line 46 ⟶ 56:
Since QTP programs usually involved adding, deleting, or modifying data, there was not much need for simple code programs. More care was exercised because of this potential danger, as a whole file (or files) of data could be wiped out rather easily.
Any QUICK, QUIZ, or QTP programs could be run compiled (converted to machine language) or uncompiled (source code). Compiled programs generally ran faster, but
Commands could be abbreviated to the first three characters when writing source code. ACCESS could be abbreviated to ACC, as well as DEFine, REPort, SCReen, etc.
QUIZ reports could be routed to a printer, screen, or ASCII text files with the <code>SET REPORT DEVICE <printer> <screen> <disk>
Given the right access and commands, a novice could write simple report programs. Just as dangerous, though, the same novice could easily destroy the data as there was no security to whether
Like all [[virtual machine]] languages, PowerHouse is CPU intensive.{{
== Migration to the PC ==
Cognos initially attempted to move to the [[Intel]] platform in 1988 with the [[DOS]]-based ''PowerHouse PC''. While the product was used by numerous partners to build bespoke applications for small to medium
▲Cognos initially attempted to move to the [[Intel]] platform in 1988 with the [[DOS]]-based ''PowerHouse PC''. While the product was used by numerous partners to build bespoke applications for small to medium sized customers it was not entirely unsuccessful at that time. However, Cognos eventually produced Axiant (c.1995), which ported PowerHouse-like syntax to an Intel-based [[Microsoft Windows]] visual development environment and linked it to [[SQL]] aware [[DBMS]] running on these machines. The radical changes wrought by the PC revolution, which began just at the time ''PowerHouse'' was introduced, eventually brought down the cost of host computers to such an extent that high-priced software development tools such as PowerHouse became unattractive to customers.{{Fact|date=February 2007}}
==PowerHouse in the 21st Century==
Cognos was acquired by IBM on January 30, 2008
The PowerHouse Application Development Tools including PowerHouse server, Axiant 4GL and PowerHouse Web were acquired from IBM by UNICOM Systems, a division of [[UNICOM Global]] on December 31, 2013, and UNICOM continues to support the worldwide customer base for the products.<ref>{{cite news |last=Woodie |first=Alex |url=http://www.itjungle.com/fhs/fhs012114-story07.html |title=Unicom Adds HP3000 Biz with Cognos ADT Buy |work=Four Hundred Stuff |date=2014-01-21 |accessdate=2016-03-24 }}</ref>
==References==
{{Reflist}}
==External links==
* [http://
{{Hewlett-Packard software}}
[[Category:Minicomputers]]▼
{{Authority control}}
[[Category:Hewlett-Packard products|3000]]▼
▲[[Category:Minicomputers]]
[[Category:HP software|PowerHouse]]
[[Category:Fourth-generation programming languages]]
| |||