DOCSLIB.ORG

Visualage C++ for AIX Compiler Reference

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Visualage C++ for AIX Compiler Reference VisualAge C++ for AIX Compiler Reference SC09-4959-00 VisualAge C++ for AIX Compiler Reference SC09-4959-00 Before using this information and the product it supports, be sure to read the information in “Notices” on page 411. May 2002 Edition This edition applies to Version 6 Release 0 of VisualAge C++ Professional for AIX (product number 5765–F56) and to all subsequent releases and modifications until otherwise indicated in new editions. IBM® welcomes your comments. You can send them by either of the following methods: v Internet: [email protected] Be sure to include your e-mail address if you want a reply. v By mail to the following address: IBM Canada Ltd. Laboratory Information Development B3/KB7/8200/MKM 8200 Warden Avenue Markham, Ontario, Canada L6G 1C7 Include the title and order number of this book, and the page number or topic related to your comment. When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 1995,2002. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents How to read syntax diagrams .....vii Specify Compiler Options for Architecture-Specific, Symbols...............vii 32-or64-bitCompilation..........29 Syntax items ..............vii Resolving Conflicting Compiler Options .....31 Syntax examples ............viii Specify Path Names for Include Files 33 Part 1. Concepts ..........1 Directory Search Sequence for Include Files Using RelativePathNames...........33 VisualAge C++ Compiler .......3 Structure a Program that Uses Compiler Modes .............3 Object Models ..............4 Templates .............35 Compiler Options.............5 Declaration of Stack in stack.h ........35 Types of Input Files ............6 Declaration of operator Functions in stack.c . 35 Types of Output Files ...........7 Template Functions Declared Inline and Template Compiler Message and Listing Information ....8 Functions With Internal Linkage .......36 Compiler Messages ...........8 Template Functions Defined within the Compilation Compiler Listings............8 Unit.................37 Use -qtempinc to Generate Template Functions Program Parallelization ........9 Automatically .............38 How the Compiler Generates the Function IBM SMP Directives ............9 Definitions..............39 OpenMP Directives ............10 Specifying the Template-Implementation File . 40 Countable Loops ............11 Specifying a Different Path for the tempinc Reduction Operations in Parallelized Loops . 12 Subdirectory .............40 Shared and Private Variables in a Parallel Regenerating the Template Instantiation File . 40 Environment ..............13 Breaking a Template Instantiation File into More Than One File ............40 Using VisualAge C++ with Other ContentsofTemplateInstantiationFile....40 Programming Languages.......15 Using #pragma Directives in Header Files . 41 Considerations for Shared Libraries .....42 Part 2. Tasks ...........17 Use -qnotempinc to Define Template Functions . 42 Use -qtemplateregistry to Define Template Functions 43 Recompiling Parts of Your Program After Making Set Up the Compilation Environment 19 Source Changes ............43 Set Environment Variables .........19 Set Environment Variables in bsh, ksh, or sh Control Parallel Processing with Shells ...............19 Pragmas ..............45 Set Environment Variables in csh Shell ....19 Set Environment Variables to Select 64- or 32-bit Modes................20 Use C and C++ with Other Set Parallel Processing Run-time Options ....20 Programming Languages.......47 Set Environment Variables for the Message and Interlanguage Calling Conventions ......47 Help Files ...............20 Corresponding Data Types .........47 Special Treatment of Character and Aggregate Invoke the Compiler .........23 Data................48 Invoke the Linkage Editor .........23 Use the Subroutine Linkage Conventions in Interlanguage Calls ............49 Specify Compiler Options ......25 Interlanguage Calls - Parameter Passing ....50 Interlanguage Calls - Call by Reference Specify Compiler Options on the Command Line. 25 Parameters .............51 -qOptions..............25 Interlanguage Calls - Call by Value Parameters 52 FlagOptions.............26 Interlanguage Calls - Rules for Passing Specify Compiler Options in Your Program Source Parameters by Value ..........52 Files .................27 Interlanguage Calls - Pointers to Functions . 54 Specify Compiler Options in a Configuration File. 27 Interlanguage Calls - Function Return Values . 54 TailoraConfigurationFile........28 Interlanguage Calls - Stack Floor ......55 Configuration File Attributes .......28 © Copyright IBM Corp. 1995,2002 iii Interlanguage Calls - Stack Overflow .....55 haltonmsg.............144 Interlanguage Calls - Traceback Table.....56 heapdebug .............145 Interlanguage Calls - Type Encoding and hot................146 Checking..............56 hsflt ...............148 Sample Program: C Calling Fortran ......57 hssngl...............149 I.................150 Part 3. Reference .........59 idirfirst ..............151 ignerrno ..............152 ignprag ..............153 Compiler Options ..........61 info...............154 Compiler Command Line Options .......61 initauto..............157 +(plussign).............71 inlglue..............158 # (pound sign) ............72 inline...............159 32,64...............73 ipa................163 aggrcopy ..............74 isolated_call.............170 alias................75 keepinlines.............171 align................77 keyword..............172 alloca...............81 L................173 ansialias..............82 l.................174 arch................83 langlvl...............175 assert ...............86 largepage..............189 attr................87 ldbl128, longdouble ..........190 B.................88 libansi ...............191 b.................89 linedebug.............192 bitfields ..............90 list ................193 bmaxdata ..............91 listopt ...............194 brtl................92 longlit...............195 C.................93 longlong ..............197 c.................94 M................198 cache...............95 ma................199 chars...............97 macpstr..............200 check...............98 maf................203 cinc...............100 makedep..............204 compact..............101 maxerr..............206 cpluscmt..............102 maxmem..............208 D................106 mbcs,dbcs.............209 dataimported ............108 mkshrobj..............210 datalocal..............109 namemangling............214 dbxextra ..............110 O,optimize.............215 digraph..............111 o................219 dollar...............113 objmodel..............220 dpcl...............114 oldpassbyvalue ............221 E................115 P................222 e ................117 p................223 eh................118 pascal...............224 enum...............119 path...............225 expfile...............125 pdf1,pdf2.............226 extchk...............126 pg................229 F................127 phsinfo..............230 f.................128 print...............231 fdpr...............129 priority ..............232 flag................130 proclocal, procimported, procunknown ....233 float...............131 proto...............235 flttrap ...............135 Q................236 fold...............137 r.................239 fullpath..............138 report...............240 funcsect ..............139 rndflt...............241 G................140 rndsngl..............243 g................141 ro................244 genproto..............142 roconst..............245 halt................143 rrm................246 iv VisualAge C++ for AIX Compiler Reference rtti ................247 #pragma langlvl ...........317 S ................248 #pragma leaves............318 s ................249 #pragmamap............319 showinc..............250 #pragmamc_func...........321 smallstack .............251 #pragmanamemangling.........322 smp...............252 #pragma nameManglingRule .......323 source...............254 #pragma object_model .........324 spill...............255 #pragmaoptions...........325 spnans ..............256 #pragma option_override ........331 srcmsg..............257 #pragmapack............332 staticinline .............258 #pragma pass_by_value .........335 statsym..............259 #pragma priority ...........336 stdinc...............260 #pragma reachable ..........337 strict ...............261 #pragma reg_killed_by .........338 strict_induction............262 #pragmareport............339 suppress ..............263 #pragma strings ...........341 symtab..............264 #pragmaunroll............342 syntaxonly .............265 Pragmas to Control Parallel Processing .....344 t.................266 #pragma ibm critical ..........346 tabsize...............267 #pragmaibmindependent_calls......347 tbtable...............268 #pragmaibmindependent_loop......348 tempinc..............269 #pragma ibm iterations .........349 templaterecompile...........270 #pragma ibm parallel_loop ........350 templateregistry ...........271 #pragmaibmpermutation........351 tempmax..............272 #pragmaibmschedule.........352 threaded..............273 #pragmaibmsequential_loop.......354 tmplparse.............274 #pragmaompatomic..........355 tocdata..............275
Load more

Recommended publications
  • KDE 2.0 Development, Which Is Directly Supported
    23 8911 CH18 10/16/00 1:44 PM Page 401 The KDevelop IDE: The CHAPTER Integrated Development Environment for KDE by Ralf Nolden 18 IN THIS CHAPTER • General Issues 402 • Creating KDE 2.0 Applications 409 • Getting Started with the KDE 2.0 API 413 • The Classbrowser and Your Project 416 • The File Viewers—The Windows to Your Project Files 419 • The KDevelop Debugger 421 • KDevelop 2.0—A Preview 425 23 8911 CH18 10/16/00 1:44 PM Page 402 Developer Tools and Support 402 PART IV Although developing applications under UNIX systems can be a lot of fun, until now the pro- grammer was lacking a comfortable environment that takes away the usual standard activities that have to be done over and over in the process of programming. The KDevelop IDE closes this gap and makes it a joy to work within a complete, integrated development environment, combining the use of the GNU standard development tools such as the g++ compiler and the gdb debugger with the advantages of a GUI-based environment that automates all standard actions and allows the developer to concentrate on the work of writing software instead of managing command-line tools. It also offers direct and quick access to source files and docu- mentation. KDevelop primarily aims to provide the best means to rapidly set up and write KDE software; it also supports extended features such as GUI designing and translation in con- junction with other tools available especially for KDE development. The KDevelop IDE itself is published under the GNU Public License (GPL), like KDE, and is therefore publicly avail- able at no cost—including its source code—and it may be used both for free and for commer- cial development.
    [Show full text]
  • Note on Using the CS+ Integrated Development Environment
    Tool News RENESAS TOOL NEWS on April 16, 2015: 150416/tn2 Note on Using the CS+ Integrated Development Environment When using the CS+ IDE, take note of the problem described in this note regarding the following point. Statements in source code which form a deeply-nested block 1. Products Concerned Products from the following list for which the version number of the CS+ common program is 3.00.00 to 3.01.00. - RX Family C/C++ Compiler Package (with IDE) - RL78 Family C Compiler Package (with IDE) - RH850 Family C Compiler Package (with IDE) - CS+ evaluation edition To check the version number of the product you have, refer to the following URL. https://www.renesas.com/cubesuite+_ver 2. Description CS+ might be terminated forcibly when a program is downloaded to a debugging tool or when an editor panel is opened after downloading a program. 3. Conditions Forced termination may occur when the source code for a project includes code that meets any of the following conditions. (a) { } blocks nested to a depth of 128 or more within a function. (b) 64 or more consecutive "else if" conditions are in sequence. (c) The total of double the number of consecutive "else if" conditions and the depth of the nesting of {} blocks at some point in the sequence of consecutive "else if" conditions is 128 or more. With conditions (b) and (c) above, the problem only arises when the C99 option is designated and the product is the RX family C/C++ compiler package (with IDE). 4. Workaround To avoid this problem, do any of the following.
    [Show full text]
  • Embrace and Extend Approach (Red Hat, Novell)
    Integrated Development Environments (IDEs) Technology Strategy Chad Heaton Alice Park Charles Zedlewski Table of Contents Market Segmentation.............................................................................................................. 4 When Does the IDE Market Tip? ........................................................................................... 6 Microsoft & IDEs ................................................................................................................... 7 Where is MSFT vulnerable?................................................................................................. 11 Eclipse & Making Money in Open Source........................................................................... 12 Eclipse and the Free Rider Problem ..................................................................................... 20 Making Money in an Eclipse World?................................................................................... 14 Eclipse vs. Microsoft: Handicapping the Current IDE Environment ................................... 16 Requirements for Eclipse success......................................................................................... 18 2 Overview of the Integrated Development Environment (IDE) Market An Integrated Development Environment (IDE) is a programming environment typically consisting of a code editor, a compiler, a debugger, and a graphical user interface (GUI) builder. The IDE may be a standalone application or may be included as part of one or more existing
    [Show full text]
  • IMS Connector for Java User's Guide and Reference
    IBM VisualAge® for Java™,Version3.5 IMSConnectorforJava User’s Guide and Reference Note! Before using this information and the product it supports, be sure to read the general information under Notices. Edition notice This edition applies to Version 3.5 of IBM VisualAge for Java and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 1998, 2000. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Chapter 1. Understanding IMS Connector for Java ...........1 Prerequisites for using IMS Connector for Java .............3 IMS Connector for Java concepts and terms ..............4 Chapter 2. Preparing to use IMS Connector for Java ..........17 Preparing your VisualAge for Java Environment .............17 Preparing your WebSphere Studio Environment .............21 Preparing your WebSphere Application Server Environment ........22 Chapter 3. Building Java applications and servlets ..........31 Building Java Applications and Servlets for Conversational Transactions ....32 Chapter 4. Building a Java Application to Run an IMS Transaction ....35 Chapter 5. Building a Java Application to Run a Navigator .......53 Chapter 6. Building a Java Application for an IMS Transaction with Multi-Segment Output Messages.................69 Chapter 7. Building a Java Application for an IMS Transaction with Multi-Segment Input Messages .................75 Chapter 8. Building an Application to Run an IMS Transaction with Synchronization Level Confirm .................81 Chapter 9. Building the Graphical User Interface ...........87 Chapter 10. Building a Java Servlet to Run an IMS Transaction .....95 Chapter 11. Building a Web Application that Uses One Servlet to Run an IMS Conversation ......................107 Chapter 12.
    [Show full text]
  • The C Programming Language
    The C programming Language The C programming Language By Brian W. Kernighan and Dennis M. Ritchie. Published by Prentice-Hall in 1988 ISBN 0-13-110362-8 (paperback) ISBN 0-13-110370-9 Contents ● Preface ● Preface to the first edition ● Introduction 1. Chapter 1: A Tutorial Introduction 1. Getting Started 2. Variables and Arithmetic Expressions 3. The for statement 4. Symbolic Constants 5. Character Input and Output 1. File Copying 2. Character Counting 3. Line Counting 4. Word Counting 6. Arrays 7. Functions 8. Arguments - Call by Value 9. Character Arrays 10. External Variables and Scope 2. Chapter 2: Types, Operators and Expressions 1. Variable Names 2. Data Types and Sizes 3. Constants 4. Declarations http://freebooks.by.ru/view/CProgrammingLanguage/kandr.html (1 of 5) [9/6/2002 12:20:42 ] The C programming Language 5. Arithmetic Operators 6. Relational and Logical Operators 7. Type Conversions 8. Increment and Decrement Operators 9. Bitwise Operators 10. Assignment Operators and Expressions 11. Conditional Expressions 12. Precedence and Order of Evaluation 3. Chapter 3: Control Flow 1. Statements and Blocks 2. If-Else 3. Else-If 4. Switch 5. Loops - While and For 6. Loops - Do-While 7. Break and Continue 8. Goto and labels 4. Chapter 4: Functions and Program Structure 1. Basics of Functions 2. Functions Returning Non-integers 3. External Variables 4. Scope Rules 5. Header Files 6. Static Variables 7. Register Variables 8. Block Structure 9. Initialization 10. Recursion 11. The C Preprocessor 1. File Inclusion 2. Macro Substitution 3. Conditional Inclusion 5. Chapter 5: Pointers and Arrays 1.
    [Show full text]
  • FEI~I<Ts Ltistttute NEWS LETTER
    NEWS LETTER FEI~I<tS ltiSTtTUTE from l\Yron J. Brophy, President VOL. 1. NO.7 Big Rapids, !.Iichigan July 23, 1951 . BUlmmG ffiOOR,i1SS. Mon~ Progress Meeting was held at the site at 1 p.m. Wednesday, Jul¥ lB. Those present were: For the Institution" . President Brophy, It'. Pattullo" and Mr. DeMOSS; for the Building Division" Mr. J. ~-'angema.n, and 11:r. Arthur Decker, the project Superintendent; for the IJuskegon Construction Company, Mr. Smith and Mr. Mastenbrook; fC1!.' t...~e Distel Heating Company, ur. Holgate; and for the Electric Construction t.; Machiner"J COmpany, ur. Brabon and Mr. Knight,; and for the Architect, l!r'. Roger Allen. Mr. Allen reported that the color scheme for all rooms in the East Wing has been determined. Mr. lD:rnest King, from the architect1s office, conferred With l!r. pattullo Friday to discuss the preparation of similar color schemes for the Vlest Wing. Work on General C~struction is proceeding rapidq and all mechanical contractors are keeping up with the construction. All structural steel roof framing for the one-story sections will be in place by the middle of this 'week and will be ready to receiVe steel roof deck. ];!t'. Smith hB.f3 received word from the Detroit Steel Products Company (sub­ contractors for the steel deck) that this material Will be Shipped some­ time bet\"loon July 30th and August loth. The fin!ll poUring of cement sla.bin the classroom building was completed last l'leck. The stone Window Sills have been received and installation has started. The alllnlinum vlindow frames Bl'e now being in­ stalled and arc ready for the laying of the glass blockS.
    [Show full text]
  • 2.3.7 80X86 Floating Point
    Open Watcom C/C++ Compiler Options data segment. For example, the option "zt100" causes all data objects larger than 100 bytes in size to be implicitly declared as far and grouped in other data segments. The default data threshold value is 32767. Thus, by default, all objects greater than 32767 bytes in size are implicitly declared as far and will be placed in other data segments. If the "zt" option is specified without a size, the data threshold value is 256. The largest value that can be specified is 32767 (a larger value will result in 256 being selected). If the "zt" option is used to compile any module in a program, then you must compile all the other modules in the program with the same option (and value). Care must be exercised when declaring the size of objects in different modules. Consider the following declarations in two different C files. Suppose we define an array in one module as follows: extern int Array[100] = { 0 }; and, suppose we reference the same array in another module as follows: extern int Array[10]; Assuming that these modules were compiled with the option "zt100", we would have a problem. In the first module, the array would be placed in another segment since Array[100] is bigger than the data threshold. In the second module, the array would be placed in the default data segment since Array[10] is smaller than the data threshold. The extra code required to reference the object in another data segment would not be generated. Note that this problem can also occur even when the "zt" option is not used (i.e., for objects greater than 32767 bytes in size).
    [Show full text]
  • Eclipse Project Briefing Materials
    [________________________] Eclipse project briefing materials. Copyright (c) 2002, 2003 IBM Corporation and others. All rights reserved. This content is made available to you by Eclipse.org under the terms and conditions of the Common Public License Version 1.0 ("CPL"), a copy of which is available at http://www.eclipse.org/legal/cpl-v10.html The most up-to-date briefing materials on the Eclipse project are found on the eclipse.org website at http://eclipse.org/eclipse/ 200303331 1 EclipseEclipse ProjectProject 200303331 3 Eclipse Project Aims ■ Provide open platform for application development tools – Run on a wide range of operating systems – GUI and non-GUI ■ Language-neutral – Permit unrestricted content types – HTML, Java, C, JSP, EJB, XML, GIF, … ■ Facilitate seamless tool integration – At UI and deeper – Add new tools to existing installed products ■ Attract community of tool developers – Including independent software vendors (ISVs) – Capitalize on popularity of Java for writing tools 200303331 4 Eclipse Overview Another Eclipse Platform Tool Java Workbench Help Development Tools JFace (JDT) SWT Team Your Tool Plug-in Workspace Development Debug Environment (PDE) Their Platform Runtime Tool Eclipse Project 200303331 5 Eclipse Origins ■ Eclipse created by OTI and IBM teams responsible for IDE products – IBM VisualAge/Smalltalk (Smalltalk IDE) – IBM VisualAge/Java (Java IDE) – IBM VisualAge/Micro Edition (Java IDE) ■ Initially staffed with 40 full-time developers ■ Geographically dispersed development teams – OTI Ottawa, OTI Minneapolis,
    [Show full text]
  • Top Productivity Tips for Using Eclipse for Embedded C/C++ Developers
    Top Productivity Tips for Using Eclipse for Embedded C/C++ Developers Garry Bleasdale, QNX Software Systems, [email protected] Andy Gryc, QNX Software Systems, [email protected] Introduction This paper presents a selection of Eclipse IDE tips and tricks gathered from: the QNX® development community: our engineers, techies and trainers Foundry27, the QNX Community Portal for open development, where we have an Eclipse IDE forum Eclipse.org forums public web sites and blogs that offer Eclipse-related expertise The 27 tips described in this paper are the tips that we received from these sources and identified as most interesting and useful to developers. We present them here with the hope that they will help make you more productive when you use the Eclipse IDE. About Eclipse A modern embedded system may employ hundreds of software tasks, all of them sharing system resources and interacting in complex ways. This complexity can undermine reliability, for the simple reason that the more code a system contains, the greater the probability that coding errors will make their way into the field. (By some estimates, a million lines of code will ship with at least 1000 bugs, even if the code is methodically developed and tested.) Coding errors can also compromise security, since they often serve as entry points for malicious hackers. No amount of testing can fully eliminate these bugs and security holes, as no test suite can anticipate every scenario that a complex software system may encounter. Consequently, system designers and software developers must adopt a “mission-critical mindset” and employ software architectures that can contain software errors and recover from them quickly.
    [Show full text]
  • Eclipse (Software) 1 Eclipse (Software)
    Eclipse (software) 1 Eclipse (software) Eclipse Screenshot of Eclipse 3.6 Developer(s) Free and open source software community Stable release 3.6.2 Helios / 25 February 2011 Preview release 3.7M6 / 10 March 2011 Development status Active Written in Java Operating system Cross-platform: Linux, Mac OS X, Solaris, Windows Platform Java SE, Standard Widget Toolkit Available in Multilingual Type Software development License Eclipse Public License Website [1] Eclipse is a multi-language software development environment comprising an integrated development environment (IDE) and an extensible plug-in system. It is written mostly in Java and can be used to develop applications in Java and, by means of various plug-ins, other programming languages including Ada, C, C++, COBOL, Perl, PHP, Python, Ruby (including Ruby on Rails framework), Scala, Clojure, and Scheme. The IDE is often called Eclipse ADT for Ada, Eclipse CDT for C/C++, Eclipse JDT for Java, and Eclipse PDT for PHP. The initial codebase originated from VisualAge.[2] In its default form it is meant for Java developers, consisting of the Java Development Tools (JDT). Users can extend its abilities by installing plug-ins written for the Eclipse software framework, such as development toolkits for other programming languages, and can write and contribute their own plug-in modules. Released under the terms of the Eclipse Public License, Eclipse is free and open source software. It was one of the first IDEs to run under GNU Classpath and it runs without issues under IcedTea. Eclipse (software) 2 Architecture Eclipse employs plug-ins in order to provide all of its functionality on top of (and including) the runtime system, in contrast to some other applications where functionality is typically hard coded.
    [Show full text]
  • Using the Java Bridge
    Using the Java Bridge In the worlds of Mac OS X, Yellow Box for Windows, and WebObjects programming, there are two languages in common use: Java and Objective-C. This document describes the Java bridge, a technology from Apple that makes communication between these two languages possible. The first section, ÒIntroduction,Ó gives a brief overview of the bridgeÕs capabilities. For a technical overview of the bridge, see ÒHow the Bridge WorksÓ (page 2). To learn how to expose your Objective-C code to Java, see ÒWrapping Objective-C FrameworksÓ (page 9). If you want to write Java code that references Objective-C classes, see ÒUsing Java-Wrapped Objective-C ClassesÓ (page 6). If you are writing Objective-C code that references Java classes, read ÒUsing Java from Objective-CÓ (page 5). Introduction The original OpenStep system developed by NeXT Software contained a number of object-oriented frameworks written in the Objective-C language. Most developers who used these frameworks wrote their code in Objective-C. In recent years, the number of developers writing Java code has increased dramatically. For the benefit of these programmers, Apple Computer has provided Java APIs for these frameworks: Foundation Kit, AppKit, WebObjects, and Enterprise Objects. They were made possible by using techniques described later in Introduction 1 Using the Java Bridge this document. You can use these same techniques to expose your own Objective-C frameworks to Java code. Java and Objective-C are both object-oriented languages, and they have enough similarities that communication between the two is possible. However, there are some differences between the two languages that you need to be aware of in order to use the bridge effectively.
    [Show full text]
  • Visualage Generator: User's Guide
    VisualAge Generator User’s Guide Ve r s i o n 4 .5 SH23-0268-01 Note Before using this document, read the general information under “Notices” on page xi. Third Edition (April 2001) This edition applies to the following licensed programs: v IBM VisualAge Generator Developer for OS/2 and Windows NT Version 4.5 v IBM VisualAge Generator Server for OS/2, AIX, Windows NT, HP-UX, and Solaris Version 4.5 v IBM VisualAge Generator Server for AS/400 Version 4 Release 4 v IBM VisualAge Generator Server for MVS, VSE, and VM Version 1.2 Order publications by phone or fax. IBM Software Manufacturing Solutions takes publication orders between 8:30 a.m. and 7:00 p.m. eastern standard time (EST). The phone number is (800) 879-2755. The fax number is (800) 445-9269. Faxes should be sent Attn: Publications, 3rd floor. You can also order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address below. IBM welcomes your comments. You can send your comments in any one of the following methods: Electronically, using the online reader comment form at the address listed below. Be sure to include your entire network address if you wish a reply. v http://www.ibm.com/software/ad/visgen By mail to the following address: IBM Corporation, Attn: Information Development, Department G7IA Building 503, P.O. Box 12195, Research Triangle Park, NC 27709-2195. When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.
    [Show full text]