DOCSLIB.ORG

Powerhouse Rules

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Powerhouse Rules PowerHouse Rules Type the text for the HTML TOC entry Type the text for the HTML TOC entry Type the text for the HTML TOC entry PowerHouse Rules POWERHOUSE RULES Cognos(R) Application Development Tools PowerHouse(R) 4GL VERSION 8.4E POWERHOUSE RULES Product Information This document applies to PowerHouse(R) 4GL Version 8.4E and may also apply to subsequent releases. To check for newer versions of this document, visit the Cognos Global Customer Services Web site (http://support.cognos.com). Copyright Copyright (C) 2007 Cognos Incorporated. Portions of Cognos(R) software products are protected by one or more of the following U.S. Patents: 6,609,123 B1; 6,611,838 B1; 6,662,188 B1; 6,728,697 B2; 6,741,982 B2; 6,763,520 B1; 6,768,995 B2; 6,782,378 B2; 6,847,973 B2; 6,907,428 B2; 6,853,375 B2; 6,986,135 B2; 6,995,768 B2; 7,062,479 B2; 7,072,822 B2. Cognos and the Cognos logo are trademarks of Cognos Incorporated in the United States and/or other countries. All other names are trademarks or registered trademarks of their respective companies. While every attempt has been made to ensure that the information in this document is accurate and complete, some typographical errors or technical inaccuracies may exist. Cognos does not accept responsibility for any kind of loss resulting from the use of information contained in this document. This document shows the publication date. The information contained in this document is subject to change without notice. Any improvements or changes to either the product or the document will be documented in subsequent editions. U.S. Government Restricted Rights. The software and accompanying materials are provided with Restricted Rights. Use, duplication, or disclosure by the Government is subject to the restrictions in subparagraph (C)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, or subparagraphs (C) (1) and (2) of the Commercial Computer Software - Restricted Rights at 48CFR52.227-19, as applicable. The Contractor is Cognos Corporation, 15 Wayside Road, Burlington, MA 01803. This software/documentation contains proprietary information of Cognos Incorporated. All rights are reserved. Reverse engineering of this software is prohibited. No part of this software/documentation may be copied, photocopied, reproduced, stored in a retrieval system, transmitted in any form or by any means, or translated into another language without the prior written consent of Cognos Incorporated. Table of Contents About this Book 13 Overview 13 Conventions in this Book 13 Getting Help 13 Cognos PowerHouse 4GL Documentation Set 14 Cognos PowerHouse Web Documentation Set 15 Cognos Axiant 4GL Documentation Set 16 Chapter 1: Running PowerHouse 17 Before Running PowerHouse 17 Getting Help 17 Setting Up the PowerHouse Environment 18 MPE/iX 18 OpenVMS 18 UNIX 18 Windows 19 Running QDESIGN 20 Running QUICK 21 Running QUIZ 22 Running QTP 24 Running PDL 27 Running PHDPDL (OpenVMS) 28 Running QSHOW 29 Running QUTIL 30 PowerHouse Commands (OpenVMS) 31 @SETPOWERHOUSE (OpenVMS) 32 POWERHOUSE (OpenVMS) 33 SETDICTIONARY (OpenVMS) 36 SHOWDICTIONARY (OpenVMS) 38 SHOWPOWERHOUSE (OpenVMS) 39 SHOWQUOTA (OpenVMS) 40 Locating Files 41 Locating the Data Dictionary 41 How the BUILD and SAVE Statements Locate Files 41 How the EXECUTE and USE Statements and auto Program Parameter Locate Files 42 Locating Start Screens or QKGO files in QUICK 43 How the GO Statement Locates Files 44 Locating Subfiles 44 Locating ODS5 File Names (OpenVMS) 46 Designated Files 48 PDC Shared Dictionary (OpenVMS) 53 Introduction 53 Requesting Dictionary Installations 53 Shared Memory Configuration 53 PHD Shared Dictionary (OpenVMS) 55 PDL Shared Dictionary (UNIX) 56 Installing Your Dictionary 56 Shared Memory Management 58 Mailbox Support in PowerHouse (OpenVMS) 59 PowerHouse Rules 3 Creating a Temporary or Permanent Mailbox 59 Temporary Mailbox Application 59 Permanent Mailbox Application 60 Using Mailboxes to Pass Source Statements 62 Mailboxes and System Crashes 62 sitehook (OpenVMS) 63 Large File Support (UNIX, Windows) 64 DISAM Data Storage (Windows) 65 Chapter 2: Program Parameters 67 About Program Parameters 67 Summary of Program Parameters 67 auto 75 autodetach|noautodetach 76 blockmode (MPE/iX) 77 broadcast (OpenVMS) 78 bulkfetch 79 cc 80 charmode 81 checksum710 (OpenVMS) 82 close_detach 84 columnowner 85 commitpoints 87 compress_buffers 88 confirmer 89 consolekeys|noconsolekeys (Windows) 90 createall 91 createbase (MPE/iX) 92 createfile 93 cursorowner 94 dbaudit 96 dbdetach|nodbdetach 98 dbwait|nodbwait 99 dcl|nodcl (OpenVMS) 100 debug (QDESIGN) 101 debug (QUICK) 102 deleteall 103 deletebase (MPE/iX) 104 deletefile 105 designer_noretain 106 detail|nodetail 107 dictionary|dict 108 dicttype|dt (OpenVMS) 109 direct_file_base_zero (OpenVMS) 110 disable_nulls 111 dont_store_module 112 downshift|upshift|noshift 113 entryrecall 114 errlist 115 fastread (OpenVMS) 116 fdl|nofdl (OpenVMS) 117 initnulls|noinitnulls 118 intsize6|nointsize6 (OpenVMS) 119 jcwbase (MPE/iX) 120 lineread (MPE/iX) 121 list|nolist 122 lockword (MPE/iX) 123 4 PowerHouse(R) 4GL Version 8.4E moduleext (MPE/iX) 124 moduleloc (MPE/iX) 125 nls (no line split) (MPE/iX, UNIX) 126 noblobs 127 nobreakset (MPE/iX) 128 nonportable 129 nontermcompat (Windows) 130 noowner 131 noprefix_ownername 132 nosetwarnstatus (OpenVMS) 133 nouicbrackets (OpenVMS) 134 nxl (no extra line) 135 obsolete 136 omnidex|noomnidex (MPE/iX) 137 osaccess|noosaccess 138 owner 139 parmfile (OpenVMS, UNIX, Windows) 140 parmprompt 141 patch 142 pollspeed (MPE/iX) 143 pre_chooseall 144 procloc 145 prompt 146 qktrace 147 quotedproccall 149 read (MPE/iX) 150 resetbindvar|noresetbindvar 151 resource 152 restore 153 retainmark|noretainmark 154 reuse_screen_buffers|noreuse_screen_buffers 155 search 156 secured 157 setjobshow|nosetjobshow (Windows) 158 statistics|nostatistics 159 subdictionary|subdict 160 subformat 161 term 162 termpoll|notermpoll (MPE/iX, OpenVMS) 165 timezone|notimezone (MPE/iX) 166 tpi|notpi (MPE/iX, HP-UX, Windows) 167 trusted|notrusted (OpenVMS) 168 update 170 version 171 vmsdate (OpenVMS) 172 Chapter 3: Resource File Statements 173 About Resource File Statements 173 Summary of Resource File Statements 173 ALLBASE MODULE EXTENSION (MPE/iX) 180 AUTODETACH 181 BROADCAST (OpenVMS) 182 BULKFETCH n 183 CC 184 CHECKSUM710 185 CLOSE DETACH 187 COLUMNOWNER 188 PowerHouse Rules 5 COMMITPOINTS OBSOLETE 190 COMPRESS BUFFERS 191 CONSOLE KEYS (Windows) 192 DATABASE 193 DBAUDIT 195 DBDETACH 197 DBWAIT 198 DEBUG 199 DEFAULT CURSOR OWNER 200 DESIGNER NORETAIN 201 DICTIONARY 202 DIRECTORY (UNIX, Windows) 204 DISABLE NULLS 205 ENTRY RECALL 206 EXIT 207 HPSLAVE EXTRA LINE 208 HPSLAVE SPLIT LINES (MPE/iX, UNIX) 209 INITIALIZE NULLS 210 INTEGER SIZE 6 (OpenVMS) 211 JCWBASE (MPE/iX) 212 LIST 213 LOCATION MODULE (MPE/iX) 214 LOCATION PROCESS 215 LOCKWORD (MPE/iX) 216 NOBLOBS 217 NONPORTABLE 218 NOOWNER 219 NOSET WARN STATUS (OpenVMS) 220 OBSOLETE 221 OMNIDEX (MPE/iX) 222 OSACCESS 223 OWNER 224 PREFIX ORACLE OPEN NAME 225 PROMPT 226 QUIT 227 RESET BIND VARIABLES 228 RESTORE LINES 229 RETAIN MARK 230 REUSE SCREEN BUFFERS 231 RMS FAST READ (OpenVMS) 232 RMS FILE BASE (OpenVMS) 233 SET 234 SETJOBSHOW (Windows) 235 SHIFT 236 STATISTICS 237 STORE MODULES 238 SUBDICTIONARY 239 SUBFORMAT n 240 TERMINAL 241 TERMINAL BLOCKMODE (MPE/iX) 244 TERMINAL CHARACTERMODE 245 TERMINAL CONFIRMER 246 TERMINAL POLLING SPEED (MPE/iX) 247 TERMINAL READ (MPE/iX) 248 TERMPOLL (MPE/iX, OpenVMS) 249 TIC RESOURCE FILE (UNIX, Windows) 250 TIME ZONE (MPE/iX) 251 6 PowerHouse(R) 4GL Version 8.4E TPI (MPE/iX, HP-UX, Windows) 252 TRUNCATE PARM VALUES 253 TRUSTED (OpenVMS) 254 UIC BRACKETS (OpenVMS) 256 UPDATE ORDER 257 USE 258 VMSDATE 259 Chapter 4: Messages in PowerHouse 261 PowerHouse 4GL Messages 261 Service Layer Messages 265 How the Service Layer Locates Message Files 265 Format of a Default Message File 266 Service Message Compiler 268 Designer Messages 270 Text Order Numbering 271 Chapter 5: PowerHouse Language Rules 273 Syntax Symbols in PowerHouse 273 Uppercase and Lowercase 273 Square Brackets 273 Braces 274 Ellipsis 274 Or-Bars 274 Stacked Syntax 274 Indented Syntax 274 General Terms in PowerHouse 275 Entering Statements 281 Abbreviating Keywords 281 Avoiding Conflicts Between Keywords and Record or Item Names 281 What Happens When You Enter Statements 281 Entering Comments 281 Entering Conditional Compile Statements 282 Operating System Commands 283 Arrays in PowerHouse 284 Using Arrays in QDESIGN 284 Subscripting in QUIZ and QTP 285 Using Arrays in QUIZ 285 Using Arrays in QTP 286 Conditions in PowerHouse 289 Logical Function 289 Logical Expression 289 Predefined Conditions in QDESIGN 290 Predefined Conditions in QTP 293 Predefined Conditions in QUIZ 295 Simple Conditions 295 Compound Conditions 296 Modifying Simple and Compound Conditions 296 Conditional Command List 296 Conditions and NULL Values 297 Conditions in SQL 298 sql-expression operator {sql-expression|subquery} 298 sql-expression operator {ALL|SOME|ANY} subquery 298 columnspec [NOT] LIKE 'sql-pattern' [ESCAPE 'character'] 298 columnspec IS [NOT] NULL 299 sql-expression [NOT] IN (value, value[...])|subquery 299 [NOT] EXISTS subquery 299 Expressions in PowerHouse 300 PowerHouse Rules 7 String Expressions 300 Numeric Expressions 300 Date Expressions 301 Conditional Expressions 301 Case Processing 302 Expressions in SQL 303 String Expressions 303 Numeric-Expressions 303 Date Expressions 303 SQL Case Processing 303 Expressions within Program Variables 304 SQL
Load more

Recommended publications
  • Bag-Of-Features Image Indexing and Classification in Microsoft SQL Server Relational Database
    Bag-of-Features Image Indexing and Classification in Microsoft SQL Server Relational Database Marcin Korytkowski, Rafał Scherer, Paweł Staszewski, Piotr Woldan Institute of Computational Intelligence Cze¸stochowa University of Technology al. Armii Krajowej 36, 42-200 Cze¸stochowa, Poland Email: [email protected], [email protected] Abstract—This paper presents a novel relational database ar- data directly in the database files. The example of such an chitecture aimed to visual objects classification and retrieval. The approach can be Microsoft SQL Server where binary data is framework is based on the bag-of-features image representation stored outside the RDBMS and only the information about model combined with the Support Vector Machine classification the data location is stored in the database tables. MS SQL and is integrated in a Microsoft SQL Server database. Server utilizes a special field type called FileStream which Keywords—content-based image processing, relational integrates SQL Server database engine with NTFS file system databases, image classification by storing binary large object (BLOB) data as files in the file system. Microsoft SQL dialect (Transact-SQL) statements I. INTRODUCTION can insert, update, query, search, and back up FileStream data. Application Programming Interface provides streaming Thanks to content-based image retrieval (CBIR) access to the data. FileStream uses operating system cache for [1][2][3][4][5][6][7][8] we are able to search for similar caching file data. This helps to reduce any negative effects images and classify them [9][10][11][12][13]. Images can be that FileStream data might have on the RDBMS performance.
    [Show full text]
  • Read and Write Images from a Database Using SQL Server
    HOWTO: Read and write images from a database using SQL Server Atalasoft is an imaging SDK and we do not directly have any dependencies on, or specific functionality for Database access (with the single exception of our DbImageSource class). However, since the typical means of image storage in a database is a BLOB (Binary Long Object), developers can take advantage of the AtalaImage.ToByteArray and AtalaImage.FromByteArray methods to use in their own code to store and retrieve image data to and from databases respectively. Atalasoft dotImage has streaming capabilities that can be used jointly with ADO.NET to read and write images directly to a database without saving to a temporary file. The following code snippets demonstrates this in C# and VB.NET. Please note that the code examples below are provided as a courtesy/convenience only and are not meant to be production code or represent the only way to access a database. The code is provided as is as but an example of how to get the needed data in a byte array suitable for use in storing to a database and how to take binary data containing an image back into an AtalaImage to use in our SDK. Write to a Database C# rivate void SaveToSqlDatabase(AtalaImage image) { SqlConnection myConnection = null; try { // Save image to byte array. // we will be storing this image as a Jpeg using our JpegEncoder with 75 quality // you could use any of our ImageEncoder classes to store as the respective image types byte[] imagedata = image.ToByteArray(new Atalasoft.Imaging.Codec.JpegEncoder(75)); // Create the SQL statement to add the image data.
    [Show full text]
  • Peoplesoft Financials/Supply Chain Management 9.2 (Through Update Image 40) Hardware and Software Requirements
    PeopleSoft Financials/Supply Chain Management 9.2 (through Update Image 40) Hardware and Software Requirements July 2021 PeopleSoft Financials/Supply Chain Management 9.2 (through Update Image 40) Hardware and Software Requirements Copyright © 2021, Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software
    [Show full text]
  • Powerhouse(R) 4GL Migration Planning Guide
    COGNOS(R) APPLICATION DEVELOPMENT TOOLS POWERHOUSE(R) 4GL FOR MPE/IX MIGRATION PLANNING GUIDE Migration Planning Guide 15-02-2005 PowerHouse 8.4 Type the text for the HTML TOC entry Type the text for the HTML TOC entry Type the text for the HTML TOC entry Type the Title Bar text for online help PowerHouse(R) 4GL version 8.4 USER GUIDE (DRAFT) THE NEXT LEVEL OF PERFORMANCETM Product Information This document applies to PowerHouse(R) 4GL version 8.4 and may also apply to subsequent releases. To check for newer versions of this document, visit the Cognos support Web site (http://support.cognos.com). Copyright Copyright © 2005, Cognos Incorporated. All Rights Reserved Printed in Canada. This software/documentation contains proprietary information of Cognos Incorporated. All rights are reserved. Reverse engineering of this software is prohibited. No part of this software/documentation may be copied, photocopied, reproduced, stored in a retrieval system, transmitted in any form or by any means, or translated into another language without the prior written consent of Cognos Incorporated. Cognos, the Cognos logo, Axiant, PowerHouse, QUICK, and QUIZ are registered trademarks of Cognos Incorporated. QDESIGN, QTP, PDL, QUTIL, and QSHOW are trademarks of Cognos Incorporated. OpenVMS is a trademark or registered trademark of HP and/or its subsidiaries. UNIX is a registered trademark of The Open Group. Microsoft is a registered trademark, and Windows is a trademark of Microsoft Corporation. FLEXlm is a trademark of Macrovision Corporation. All other names mentioned herein are trademarks or registered trademarks of their respective companies. All Internet URLs included in this publication were current at time of printing.
    [Show full text]
  • Eloquence: HP 3000 IMAGE Migration by Michael Marxmeier, Marxmeier Software AG
    Eloquence: HP 3000 IMAGE Migration By Michael Marxmeier, Marxmeier Software AG Michael Marxmeier is the founder and President of Marxmeier Software AG (www.marxmeier.com), as well as a fine C programmer. He created Eloquence in 1989 as a migration solution to move HP250/HP260 applications to HP-UX. Michael sold the package to Hewlett-Packard, but has always been responsible for Eloquence development and support. The Eloquence product was transferred back to Marxmeier Software AG in 2002. This chapter is excerpted from a tutorial that Michael wrote for HPWorld 2003. Email: [email protected] Eloquence is a TurboIMAGE compatible database that runs on HP-UX, Linux and Windows.Eloquence supports all the TurboIMAGE intrinsics, almost all modes, and they behave identically. HP 3000 applications can usually be ported with no or only minor changes. Compatibility goes beyond intrinsic calls (and also includes a performance profile.) Applications are built on assumptions and take advantage of specific behavior. If those assumptions are no longer true, the application may still work, but no longer be useful. For example, an IMAGE application can reasonably expect that a DBFIND or DBGET execute fast, independently of the chain length and that DBGET performance does not differ substantially between modes. If this is no longer true, the application may need to be rewritten, even though all intrinsic calls are available. Applications may also depend on external utilities or third party tools. If your application relies on a specific tool (let’s say, Robelle’s SUPRTOOL), you want it available (Suprtool already works with Eloquence). If a tool is not available, significant changes to the application would be required.
    [Show full text]
  • Turboimage/XL Database Management System Reference Manual
    TurboIMAGE/XL Database Management System Reference Manual HP e3000 MPE/iX Computer Systems Edition 8 Manufacturing Part Number: 30391-90012 E0701 U.S.A. July 2001 Notice The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material. Hewlett-Packard assumes no responsibility for the use or reliability of its software on equipment that is not furnished by Hewlett-Packard. This document contains proprietary information which is protected by copyright. All rights reserved. Reproduction, adaptation, or translation without prior written permission is prohibited, except as allowed under the copyright laws. Restricted Rights Legend Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. Rights for non-DOD U.S. Government Departments and Agencies are as set forth in FAR 52.227-19 (c) (1,2). Acknowledgments UNIX is a registered trademark of The Open Group. Hewlett-Packard Company 3000 Hanover Street Palo Alto, CA 94304 U.S.A. © Copyright 1985, 1987, 1989, 1990, 1992, 1994, 1997, 2000, 2001 by Hewlett-Packard Company 2 Contents 1. Introduction Data Security . 27 Rapid Data Retrieval and Formatting . 28 Program Development .
    [Show full text]
  • Oracle Multimedia Image PL/SQL API Quick Start
    Oracle Multimedia Image PL/SQL API Quick Start Introduction Oracle Multimedia is a feature that enables Oracle Database to store, manage, and retrieve images, audio, video, and other heterogeneous media data in an integrated fashion with other enterprise information. Oracle Multimedia extends Oracle Database reliability, availability, and data management to multimedia content in media-rich applications. This article provides simple PL/SQL examples that upload, store, manipulate, and export image data inside a database using Oracle Multimedia’s PL/SQL packages. Some common pitfalls are also highlighted. The PL/SQL package used here is available in Oracle Database release 12c Release 2 or later with Oracle Multimedia installed (the default configuration provided by Oracle Universal Installer). The functionality in this PL/SQL package is the same as the functionality available with the Oracle Multimedia relational interface and object interface. For more details refer to Oracle Multimedia Reference and Oracle Multimedia User’s Guide. The following examples will show how to store images within the database in BLOB columns so that the image data is stored in database tablespaces. Oracle Multimedia image also supports BFILEs (pointers to files that reside on the filesystem), but this article will not demonstrate the use of BFILEs. Note that BFILEs are read -only so they can only be used as the source for image processing operations (i.e. you can process from a BFILE but you can’t process into a BFILE). NOTE: Access to an administrative account is required in order to grant the necessary file system privileges. In the following examples, you should change the command connect sys as sysdba to the appropriate one for your system: connect sys as sysdba Enter password: password The following examples also connect to the database using connect ron Enter password: password which you should change to an actual user name and password on your system.
    [Show full text]
  • A 10 Million Image Database for Scene Recognition
    This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI 10.1109/TPAMI.2017.2723009, IEEE Transactions on Pattern Analysis and Machine Intelligence 1 Places: A 10 million Image Database for Scene Recognition Bolei Zhou, Agata Lapedriza, Aditya Khosla, Aude Oliva, and Antonio Torralba Abstract—The rise of multi-million-item dataset initiatives has enabled data-hungry machine learning algorithms to reach near- human semantic classification performance at tasks such as visual object and scene recognition. Here we describe the Places Database, a repository of 10 million scene photographs, labeled with scene semantic categories, comprising a large and diverse list of the types of environments encountered in the world. Using the state-of-the-art Convolutional Neural Networks (CNNs), we provide scene classification CNNs (Places-CNNs) as baselines, that significantly outperform the previous approaches. Visualization of the CNNs trained on Places shows that object detectors emerge as an intermediate representation of scene classification. With its high-coverage and high-diversity of exemplars, the Places Database along with the Places-CNNs offer a novel resource to guide future progress on scene recognition problems. Index Terms—Scene classification, visual recognition, deep learning, deep feature, image dataset. F 1 INTRODUCTION Whereas most datasets have focused on object categories If a current state-of-the-art visual recognition system would (providing labels, bounding boxes or segmentations), here send you a text to describe what it sees, the text might read we describe the Places database, a quasi-exhaustive repos- something like: “There is a sofa facing a TV set.
    [Show full text]
  • Using Free Pascal to Create Android Applications
    Using Free Pascal to create Android applications Michaël Van Canneyt January 19, 2015 Abstract Since several years, Free pascal can be used to create Android applications. There are a number of ways to do this, each with it’s advantages and disadvantages. In this article, one of the ways to program for Android is explored. 1 Introduction Programming for Android using Free Pascal and Lazarus has been possible since many years, long before Delphi unveiled its Android module. However, it is not as simple a process as creating a traditional Desktop application, and to complicate matters, there are several ways to do it: 1. Using the Android NDK. Google makes the NDK available for tasks that are CPU- intensive (a typical example are opengl apps), but warns that this should not be the standard way of developing Android apps. This is the way Delphi made it’s Android port: Using Firemonkey – which uses OpenGL to draw controls – this is the easiest approach. There is a Lazarus project that aims to do things in a similar manner (using the native-drawn widget set approach). 2. Using the Android SDK: a Java SDK. This is the Google recommended way to create Android applications. This article shows how to create an Android application using the Java SDK. 2 FPC : A Java bytecode compiler The Android SDK is a Java SDK: Android applications are usually written in Java. How- ever, the Free Pascal compiler can compile a pascal program to Java Bytecode. This is done with the help of the JVM cross-compiler. Free Pascal does not distribute this cross-compiler by default (yet), so it must be built from sources.
    [Show full text]
  • COMMUNICATOR 3000 MPE/Ix-Powerpatch 5 (Powerpatch Tape C.55.05) Based on Release 5.5
    COMMUNICATOR 3000 MPE/iX-PowerPatch 5 (PowerPatch Tape C.55.05) Based on Release 5.5 HP 3000 MPE/iX Computer Systems Volume 9, Issue 4 Customer Order Number 30216-90257 30216-90257 E0798 Printed in: U.S.A. July 1998 Notice The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material. Hewlett-Packard assumes no responsibility for the use or reliability of its software on equipment that is not furnished by Hewlett-Packard. This document contains proprietary information which is protected by copyright. All rights reserved. Reproduction, adaptation, or translation without prior written permission is prohibited, except as allowed under the copyright laws. Acknowledgements Microsoft Windows ™, Windows 95 ™, Windows NT ™, Microsoft Access ™, Visual Basic ™, Visual C ++ ™, Visual FoxPro ™, and MS-Query ™are U.S. registered trademarks of Microsoft Corporation. ODBCLink/SE ™is a registered trademark of M. B. Foster Software Labs, Inc. Dr. DeeBeeSpy© 1995 Syware, Inc., all rights reserved. Axiant ™ and Impromptu ™ are registered trademarks of Cognos. Foxbase ™ is a registered trademark of Fox Software. Lotus ™ is a registered trademark of Lotus Development Corporation. Jetform is a registered trademark of Jetform Corporation. Paradox ™ is a registered trademark of Borland International Inc. PowerBuilder ™ is a registered trademark of Powersoft Corporation.
    [Show full text]
  • Decision Support and Data Warehousing in an HP 3000 Environment
    Paper# : 3011 Decision Support and Data Warehousing in an HP 3000 Environment. Christophe Jacquet Hewlett-Packard Co. 19447 Pruneridge Ave Cupertino, CA, 94087 Email: [email protected] Decision Support and Data Warehousing in an HP 3000 Environment. 3011 - 1 As corporate downsizing continues, flatter organizational structures give end users more decision making responsibilities. HP 3000 users can take advantage of powerful tools such as Image/SQL and ODBC drivers to gain direct access to the data in the databases. While these tools provide real benefits, the limitations of directly accessing operational data, in terms of performance, concurrency, ease of use and data quality, are rapidly becoming apparent. A current approach to Decision Support is the consolidation of company-wide data into a separately designed environment, commonly called a Data Warehouse. This paper covers the benefits and history of Data Warehouses and examines a variety of approaches available within the HP 3000 marketplace to implement such a Decision Support environment. It describes the elements needed to create a Data Warehouse environment from the Decision Support data store to the end user desktop, including extraction and cleansing tools. Data Warehousing is just one example of how enhancements to the MPE/iX operating environment permit HP 3000 customers to take full advantage of the many new technologies and approaches emerging in the Information Technology marketplace. Why is decision support important. In today’s world, companies have to be able to make decisions much faster than before. Making the right decisions at the right time can provide significant competitive advantage for a company.
    [Show full text]
  • Free Pascal and Lazarus Programming Textbook
    This page deliberately left blank. In the series: ALT Linux library Free Pascal and Lazarus Programming Textbook E. R. Alekseev O. V. Chesnokova T. V. Kucher Moscow ALT Linux; DMK-Press Publishers 2010 i UDC 004.432 BBK 22.1 A47 Alekseev E.R., Chesnokova O.V., Kucher T.V. A47 Free Pascal and Lazarus: A Programming Textbook / E. R. Alekseev, O. V. Chesnokova, T. V. Kucher M.: ALTLinux; Publishing house DMK-Press, 2010. 440 p.: illustrated.(ALT Linux library). ISBN 978-5-94074-611-9 Free Pascal is a free implementation of the Pascal programming language that is compatible with Borland Pascal and Object Pascal / Delphi, but with additional features. The Free Pascal compiler is a free cross-platform product implemented on Linux and Windows, and other operating systems. This book is a textbook on algorithms and programming, using Free Pascal. The reader will also be introduced to the principles of creating graphical user interface applications with Lazarus. Each topic is accompanied by 25 exercise problems, which will make this textbook useful not only for those studying programming independently, but also for teachers in the education system. The book’s website is: http://books.altlinux.ru/freepascal/ This textbook is intended for teachers and students of junior colleges and universities, and the wider audience of readers who may be interested in programming. UDC 004.432 BBK 22.1 This book is available from: The <<Alt Linux>> company: (495) 662-3883. E-mail: [email protected] Internet store: http://shop.altlinux.ru From the publishers <<Alians-kniga>>: Wholesale purchases: (495) 258-91-94, 258-91-95.
    [Show full text]