Business application language
high-level programming language similar to the BASIC programming language
Business Application Language (BAL) refers to one of many offshoots of the BASIC language and should not be confused with IBM's well-established Basic assembly language.
History
Business Application Language was originally defined by Honeywell in 1973 and the major diffusion was in their system '80-'90 in Europe with the work of French firm Prologue S.A. that used BAL for programming on their proprietary Operating System (Prologue).
In 1986 the language was ported to the Unix platform by GuyPes. The first development environment, named Balix, are distributed starting in 1988 in Italy and France. A different evolution path was made by Prologue S.A., named ABAL, in 1992.
The evolution of Balix, developed in Italy, is called B2U (an acronym for Business under UNIX) developed by GuyPes, and are used for a Banking Information System that are used by one hundred banks in Italy.
The public source identifies “Business application language” as high-level programming language similar to the BASIC programming language. This brief keeps that definition visible, then builds a research path around Business, application and language.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Business application language”, the useful work is to connect “high-level programming language similar to the BASIC programming language” to the records capable of establishing context and consequence.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Mar 31, 2025. The linked authority identifier is Q5001840. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1973, 1986, 1988 and 1992.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Business application language”, its source revision and the description used here.
- Expand the search: follow Business application language primary sources, Business application language archive and Business research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Business application language”?
- What terminology or title could unlock a more precise catalogue search?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Business application language” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.