How To Use Builder On A Microsoft Ubuntu 7.1.3.3 (Windows 2000) With A Microsatellite (Unix) Or Ubuntu 8.1 (Windows) (Unison) (Windows 2) (For

Enterprise Application Developer and Builder Software Release Announcement for Release 3.3 Unisys Copyright 2003 Unisys Corporation. All rights reserved. Printed in USA March 2003 78616349-004

NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information described herein is only furnished pursuant and subject to the terms and conditions of a duly executed agreement to purchase or lease equipment or to license software. The only warranties made by Unisys, if any, with respect to the products described in this document are set forth in such agreement. Unisys cannot accept any financial or other responsibility that may be the result of your use of the information in this document or software material, including direct, special, or consequential damages. You should be very careful to ensure that the use of this information and/or software material complies with the laws, rules, and regulations of the jurisdictions with respect to which it is used. The information contained herein is subject to change without notice. Revisions may be issued to advise of such changes and/or additions. Notice to U.S. Government End Users: This is commercial computer software or hardware documentation developed at private expense. Use, reproduction, or disclosure by the Government is subject to the terms of Unisys standard commercial license for the products, and where applicable, the restricted/limited rights provisions of the contract data rights clauses. Correspondence regarding this publication should be forwarded to Unisys Corporation by addressing remarks to Product Information, Australian Centre for Unisys Software (ACUS), UNISYS, Locked Bag 3111, Rhodes, NSW, 2138, Australia. Comments about documentation can also be sent through e-mail to eae.pi@unisys.com. All terms which may be mentioned in this document that are known to be trademarks or service marks have been appropriately capitalized. Unisys Corporation cannot attest to the accuracy of this information. Use of a term in this document should not be regarded as affecting the validity of any trademark or service mark. Unisys, LINC, INFOConnect, ClearPath, and PowerClient are registered trademarks, and e-@ction and Griffin are trademarks of Unisys Corporation. HP and HP-UX are registered trademarks of the Hewlett-Packard Company. IBM, DYNIX/ptx, AIX and RS/6000 are registered trademarks of International Business Machines Corporation. Micro Focus and Net Express are registered trademarks of Merant International Limited. Microsoft, Windows, Windows NT, Windows 2000, Visual Basic, and Internet Explorer are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. ORACLE and SQL*Plus are registered trademarks of Oracle Corporation. SPARC is a registered trademark of SPARC International, Inc. Products bearing SPARC trademarks are based on an architecture developed by Sun Microsystems, Inc. SQL Server is a trademark of Sybase, Inc. or its subsidiaries Sun, Java and Solaris are registered trademarks of Sun Microsystems, Inc. in the United States and other countries. UNIX is a registered trademark in the U.S. and other countries, licensed exclusively through X/Open Company, Ltd. UnixWare is a registered trademark of The Santa Cruz Operation, Inc.

Contents Section 1. General Description... 1 1 About This Document...1 1 Purpose...1 1 Audience...1 1 About Release 3.3...1 1 What is Different?...1 1 Why Upgrade to Developer and Builder Release 3.3?...1 2 Enterprise Application Environment Overview...1 4 Enterprise Application Developer...1 4 Enterprise Application Builder...1 5 Enterprise Application Runtime...1 7 Section 2. Product Interdependencies... 2 1 Hardware Requirements...2 1 Stand-alone Workstation...2 1 Multi-user Environment...2 2 Version Control Server Requirements...2 3 Software Requirements...2 4 Enterprise Application Environment Software...2 5 Section 3. Migration Requirements... 3 1 Pre-migration Tasks...3 1 Migration Issues...3 1 Host Builder and Runtime Test Environment Discontinued...3 2 DYNIX/ptx Discontinued...3 2 UnixWare 7.1.3...3 2 Transferring Host Subsystem Screens to Developer...3 2 Automatic Generate on Migration...3 2 Configuring for Remote Subroutines in Developer Test...3 3 Configuring for Remote Routines in the Administration Client...3 4 SQL Scripts and Embedded Static SQL...3 4 Running Multiple Versions...3 5 Migrating Systems with National Language Support CER...3 5 Migrating to Developer Release 3.3...3 5 Migrating to Builder Release 3.3...3 5 Migrating to Developer Version Control Release 3.3...3 6 78616349 004 iii

Contents Section 4. Release Functionality... 4 1 New Features in Developer and Builder... 4 1 Developer Features... 4 2 Developer Console Enhancements... 4 2 LCIF Format Changes Ignored option in LCIF Viewer... 4 3 Keyword Support... 4 3 Developer Painter Enhancements... 4 5 Painting Host Subsystem Screens... 4 7 Cross-host access to Callable Global Logics... 4 7 Data Invocation (for ClearPath MCP)... 4 8 Static Embedded SQL (for Windows)... 4 9 User-Maintained Tables (for Windows)... 4 10 Host Database Access (for Windows and ClearPath OS 2200) 4 10 Builder Features... 4 12 Builder Scriptable Interface... 4 12 Builder Infrastructure Enhancements... 4 13 Improved generate performance for multi-processor machines... 4 13 Bulk Options functionality (for ClearPath MCP)... 4 13 Section 5. Restrictions and Known Limitations... 5 1 Developer and Builder Release 3.3 Restrictions... 5 1 General Restrictions... 5 1 Developer Limitations... 5 3 Builder Client Limitations... 5 5 Section 6. Support... 6 1 Unisys Support Online... 6 1 Unisys Client Support Center... 6 1 Direct Telephone Support... 6 2 Software Support Services... 6 2 De-implementations... 6 3 Section 7. Customer Product Information... 7 1 Developer and Builder Documentation... 7 1 Documentation CD-ROM... 7 1 Additional Documentation... 7 2 Online Help... 7 2 Computer-based Training... 7 3 Instructor-led Courses... 7 3 Introduction to Enterprise Application Environment for Management (CEL8001)... 7 4 Introduction to Enterprise Application Environment for Management and Technical Personnel (CEL8002)... 7 4 Introduction to Enterprise Application Developer (CEL800)... 7 4 Managing Enterprise Application Developer (CEL8006)... 7 4 Component Enabler Workshop (CEL8007)... 7 5 iv 78616349 004

Contents Runtime for Windows 2000 (003386)...7 5 Runtime for Windows 2000 (003785)...7 5 Section 8. Ordering Procedure... 8 1 Enterprise Application Environment Product Package...8 1 Ordering Developer and Builder, and Version Control...8 2 Licensing Options...8 2 Developer Licenses...8 3 Version Control Licenses...8 3 License Styles...8 3 Software Update Subscriptions...8 4 Developer Style IDs...8 5 New Licenses...8 5 Update Licenses...8 5 Software Update Subscriptions...8 6 Version Control Style IDs...8 6 78616349 004 v

Contents vi 78616349 004

Section 1 General Description About This Document Purpose This Software Release Announcement provides an overview of Enterprise Application Developer and Builder Release 3.3. Audience The audience for this Software Release Announcement includes: Current users of Enterprise Application Developer and Builder 3.1, 3.1A, 3.1B, or 3.2 who want to upgrade to Release 3.3. Current users of Host Builder who want to upgrade to Enterprise Application Developer and Builder Release 3.3. Current users of LINC Development and LINC Generate who want to upgrade to Enterprise Application Developer and Builder Release 3.3. Prospective customers who are considering purchasing Enterprise Application Developer and Builder Release 3.3. About Release 3.3 What is Different? Release 3.3 marks the final stage in the move from host-based development of Enterprise Application Environment systems to Developer workstation-based development and generation. Developer and Builder Release 3.3 incorporate the outstanding features from host development and generation into the workstation environment. This release provides improved compatibility, as well as increased programmer productivity for those who have not yet moved to Developer and Builder, allowing for confident migration without loss of functionality or performance. 78616349 004 1 1

General Description Developer Release 3.3 offers improved usability and performance, as well as new features designed to provide both increased opportunities for automation and enhanced user control. It also provides a new suite of client interface products for accessing your systems, that provides component-oriented solutions which use an enhanced Component Enabler product. This new client option replaces Graphical Interface Workbench and Web Enabler. This release provides greater interoperability with.net and Java-based component Runtime environments, as well as ASP-X in the ASP Generator. Host Builder and Runtime Test Environment Discontinued Host Builder, which previously provided host-based development, generation, and deployment functions, has been discontinued with this release. All Enterprise Application Environment development is now performed using Developer, with systems generated directly from the workstation using Builder. Runtime Test Environment has also been discontinued in Release 3.3. For more information, see Host Builder and Runtime Test Environment Discontinued under General Restrictions on page 5 1. DYNIX/ptx Discontinued Support for the DYNIX/ptx platform has been discontinued as IBM no longer supports it. For more information, see DYNIX/ptx Discontinued under Migration Issues on page 3 1. Why Upgrade to Developer and Builder Release 3.3? New Developer Features for Release 3.3 This release of Enterprise Application Developer provides the following reasons to upgrade: The Developer Console has been enhanced to allow you to perform additional Version Control functions, including checking in and out, undoing checkouts, labeling, deleting, and purging. It also supports additional Developer commands, including those for validating logic, and checking and consolidating the repository. LCIF format changes that occur as a result of a change in Developer release levels can now be ignored in the LCIF Viewer, making it easier to identify actual changes to the items being compared. Keyword Support has been added to Developer, simplifying migration from a hostbased development environment. 1 2 78616349 004

General Description Developer Painter has been enhanced to incorporate features that were previously only available in Graphical Interface Workbench. Enhanced graphical items: display and edit items can span multiple lines, text item backgrounds are now transparent, and password edit fields are available. Enhanced flexibility: graphical control items can be added without having to create associated Data Items and CopyFrom Groups can be ungrouped into cells. Enhanced functionality: a color dialog box is displayed for selecting and previewing colors, tab order maintenance functions are available, and you can view the default value of a Data Item or the name of a Data Item or graphical control object from new menu items. Developer now allows you to paint screens for host subsystems such as ROC and ADHOC. This was previously only possible using Graphical Interface Workbench. Component Enabler and the RATL protocol now offers cross-host access to Callable Global Logics. Data Invocation for ClearPath MCP systems, previously provided by Host Builder, is now supported by Developer. This feature allows values of Data Items and Profile Ordinates that are stored in the Profile itself, as well as in the Ispec records, to be accessed without accessing the Ispec record, reducing the number of database reads. Static Embedded SQL is now available for Runtime for Windows Operating System systems. Static Embedded SQL provides an efficient use of the database enabling optimizations for data retrieval and/or updates. User-Maintained Tables are now available for Runtime for Windows Operating System systems, presenting greater database control. Host Database Access has been extended to the Windows Operating Systems and ClearPath OS 2200 platforms. Host Database Access enables you to test and debug systems against test databases on the Runtime host using Developer Test. New Builder Features for Release 3.3 This release of Enterprise Application Builder provides the following reasons to upgrade: A scriptable interface, allowing interaction between Developer Console and Builder, enabling automation of generate and system deployment tasks. Infrastructure enhancements that allow you to download error logs. Improved generate peformance for multi-processor machines. The ability to set or unset DMS II Extended Edition and Optimize Blocksize to VSS-2 options for multiple Ispecs in ClearPath MCP systems, using the Bulk Options feature. 78616349 004 1 3

General Description Enterprise Application Environment Overview The Enterprise Application Environment consists of three primary, integrated tools that are used to develop, generate, and deploy applications to a target host. These are: Enterprise Application Developer Enterprise Application Builder Enterprise Application Runtime Enterprise Application Developer Developer provides a Windows-based development environment that allows you to: Design, develop, test, and maintain Enterprise Application Environment systems. Import existing Enterprise Application Environment specifications from any supported host platform, and enhance or re-engineer them. Developer Modules The following table shows the Developer modules available in Typical, Custom, Developer Server, and Version Control Server installations. Installation Type Developer Modules Typical Installation Developer Developer Test Developer Repository Custom, Developer Server, or Version Control Server Installations Developer Security Developer Server Developer Test Remote Server Builder Version Control Client Version Control Server Note: Version Control is a separately licensed product requiring an installation key. Developer Developer provides a Windows-based graphical environment that enables you to design, develop, and analyze Enterprise Application Environment systems. Its features include a logic editor, logic validation, and a screen painter. 1 4 78616349 004

General Description Developer Test Developer Test provides Developer with its own test environment. It allows Runtime applications to be tested in an interpretive environment before they are generated and deployed. Developer Repository The Developer Repository is the database in which system specification data is held. It can be located on either a Developer workstation or on another LAN-connected machine. Developer Security Developer Security controls access to operations and objects in the Developer Repository accessed by Developer and Developer Test. Developer Server The Developer Server controls all interactions with the Developer Repository in a multiuser Developer environment. Developer Test Remote Server The Developer Test Remote Server module allows Component Enabler clients to access the Developer Test D-ISAM database via the Remote Access Server interface. Version Control Server The Version Control Server manages the Version Control Bank(s), to provide integrated support for versioning objects from within Developer. Version Control Client The Version Control Client exists in the Developer environment and interacts with the Version Control Server. Enterprise Application Builder Builder is a client/server software application that lets you generate and deploy an Enterprise Application Environment system to a target host, directly from the Developer workstation. To generate a system, the Builder Client (running on the workstation) and Server (running on the deployment host) communicate to extract, transfer, and compile the necessary files, and install and deploy them on the target host. Note: Host Builder has been discontinued. This release does not include the ability to perform host-based development or manual host generates. 78616349 004 1 5

General Description Builder Client/Server Interaction To generate and deploy Enterprise Application Environment systems, you must have both the Builder Client and Builder Server of the same release level for the required platform installed. The Builder Client is installed as part of a Custom installation of Developer. The Builder Server is installed as part of the Runtime installation. The following figure shows how Builder bridges the development and deployment environments: Enterprise Application Builder Builder Client Builder Client provides functionality that allows you to: Perform change analysis of your system Direct-generate source files for the database(s) appropriate for your platform Transfer the Runtime system to the host (via FTP) Send requests to the Builder Server to compile and deploy the system Builder Server The Builder Server is installed with Runtime 3.3/3R3 for your chosen platform. 1 6 78616349 004

General Description Its functionality includes: Compilation of the source code to create the system executable code on the host Deployment of the system to the host Response to messages received from the Builder Client Enterprise Application Runtime Runtime Release 3.3/3R3 software is used to deploy and support Enterprise Application Environment systems on a target host operating system. You must have the Runtime environment installed on the host before you can generate your system. For more information, see the Runtime Release 3.3/3R3 Software Release Announcement for the relevant host operating system. 78616349 004 1 7

General Description 1 8 78616349 004

Section 2 Product Interdependencies This section covers hardware and software requirements for the following Enterprise Application software: Developer Release 3.3 Builder Release 3.3 Version Control Release 3.3 Hardware Requirements Enterprise Application Developer Release 3.3 can be installed either on stand-alone workstations, or on a server for use by multiple users. Requirements for each configuration option are described below. The hardware requirements for the Version Control Server are listed separately, as it is often located on a dedicated machine. If the Developer Server and Version Control Server software are on the same machine, the hardware requirements will be considerably greater than what is specified for either product alone. Note: The Developer Test database must be located where it can be accessed by all the workstations, preferably at each Developer workstation, although the LAN file server or the Developer Server may also be used. Stand-alone Workstation The following table shows the minimum hardware requirements for a workstation in a single user environment when Developer (Server and Client) is installed, either on its own, or together with Builder (Client) or Version Control (Client). Note: If you want to install Developer with Builder and Version Control (Client), use the requirements listed in the Developer and Version Control Client column of this table. Hardware Developer Developer and Builder Developer and Version Control Client Processor Pentium II 200 MHz Pentium II 200 MHz Pentium II 400 MHz RAM 128 MB 128 MB 128 MB Disk space* 500 MB 500 MB 500 MB 78616349 004 2 1

Product Interdependencies Hardware Developer Developer and Builder Developer and Version Control Client Other SVGA monitor CD-ROM drive ISO 9660 format SVGA monitor CD-ROM drive ISO 9660 format Paging file 300 MB SVGA monitor CD-ROM drive ISO 9660 format Paging file 300 MB Network Speed 100 Mbps * Additional disk space is required if the repository is stored on this machine. The required space will vary depending on the size and complexity of the system. Note: The only limitation that exists when the Developer Server software is installed on a workstation is that it cannot be registered as a service. This is due to the dependence on the Computer Browser running on the workstation. Multi-user Environment The minimum hardware requirements for the Developer Server and workstations in a multi-user environment are described below. Developer Server Hardware Requirements The Developer Server should be the most powerful machine in a multi-user environment, as it controls all interactions with the Developer Repository. The following table shows the minimum hardware requirements for the Developer Server in a multi-user environment, where Developer (Server) is installed either on its own, or together with Builder (Client). Hardware Developer only Developer & Builder Processor Pentium II 300 MHz Pentium II 300 MHz RAM 128 MB 128 MB Disk space* 500 MB 500 MB Paging file Not required 300 MB Other SVGA monitor CD-ROM drive ISO 9660 format 10 MB LAN card format SVGA monitor CD-ROM drive ISO 9660 format * Additional disk space is required if the Developer Repositories are on this machine. The required space will vary depending on the size and complexity of the system. 2 2 78616349 004

Product Interdependencies Developer Workstation Hardware Requirements The following table lists the minimum hardware requirements for the Developer workstation in a multi-user environment, where Developer (Client) is installed either on its own, or together with Builder (Client) or Version Control (Client). Note: If you want to install Developer, Builder Client and Version Control Client on the same workstation, use the requirements listed in the Developer and Version Control Client column of this table. Hardware Developer only Developer & Builder Developer and Version Control Client Processor Pentium II 200 MHz Pentium II 300 MHz Pentium II 400 MHz RAM 128 MB 128 MB 128 MB Disk space* 500 MB 500 MB 500 MB Paging file Not required 300 MB 300 MB Other SVGA monitor CD-ROM drive ISO 9660 format 10 MB LAN card SVGA monitor CD-ROM drive ISO 9660 format SVGA monitor CD-ROM drive ISO 9660 format * Additional disk space is required if the Developer Repositories are on this machine. The required space will vary depending on the size and complexity of the system. Version Control Server Requirements The following table shows the minimum hardware requirements for the Version Control Server. If the Version Control and Developer Server are on the same machine, the requirements will be greater than indicated in the specifications below. Note: Version Control Client requirements are included with the workstation hardware requirements for single or multi-user environments. Hardware Requirement Processor Small workgroups 2 x Pentium II 333 MHz Medium workgroups 4 x Pentium III 500 MHz Large workgroups 8 x XEON 500 MHz RAM Small workgroups 512 to 2048 MB Medium workgroups 1024 to 4096 MB Large workgroups 4096 to 8192 MB Disk space UREP 5.1 software requires 500 MB (minimum) Version Control Bank requires 440 MB (minimum) 78616349 004 2 3

Product Interdependencies Hardware Requirement Other Paging file 300 MB, plus an additional 10 MB per connection to Version Control Server CD-ROM Drive ISO 9660 format SVGA monitor Note: Version Control features a Configuration Wizard that calculates the required disk space for the Version Control Bank, based on your estimates of the number of objects it will contain. For details, see the Enterprise Application Developer Version Control Guide. Software Requirements The following table lists the software requirements for Developer, Builder, and Version Control Release 3.3. Software Requirement Operating system Windows 2000 operating systems: Windows 2000 Professional (Service Pack 1), for single users Windows 2000 Server Windows 2000 Advanced Server, for multi-users Windows 2000 DataCenter Comms protocols and services File transfer utility Platform-specific software (required if Builder is installed) TCP/IP and Printing Services RPC Services Internet Information Server (IIS) or Peer Web Services (PWS) required if you plan to use Developer Test Remote Server FTP UNIX platforms support for standard UNIX character mode terminals ClearPath OS 2200 CMS 1100 8R4A or Communications Platform ClearPath MCP Unisys Transaction Server Unisys Transaction Server Language Support Heritage Network Services, TCP, or OSI as a comms network protocol Other Internet Explorer 6.0 Optional Unisys Output Manager Release 5R1 or higher For platform-specific software requirements, see the Runtime Release 3.3/3R3 Software Release Annoucement for the relevant host operating system. 2 4 78616349 004

Product Interdependencies Enterprise Application Environment Software Essential Enterprise Application Environment Software Due to the inter-relationships between the components of the Enterprise Application Environment, the following software is required to develop and deploy an Enterprise Application Environment system: Enterprise Application Developer Release 3.3 Enterprise Application Builder Release 3.3 Note: As of Release 3.3, Builder no longer requires a license. Builder Client is packaged on the Developer CD-ROM, and Builder Server is packaged on the Runtime CD-ROM. Optional Enterprise Application Environment Software Use these products to web-enable and provide remote access to your Runtime systems: Component Enabler Release 3.3 Presentation Client Release 3.3 ASP Generator Release 3.3 ASP Generator Customization Kit Release 3.3 Client Generator for Microsoft Visual Basic Release 3.3 Business Integrator Release 3.3 These products are provided on the Enterprise Application Client Tools 3.3 CD-ROM. 78616349 004 2 5

Product Interdependencies 2 6 78616349 004

Section 3 Migration Requirements This section provides information on migrating existing Enterprise Application Environment or LINC systems to Developer and Builder Release 3.3. Note: The information in this section is included as a guide only. Refer to the detailed instructions in the Enterprise Application Developer Installation and Configuration Guide Release 3.3 before attempting to migrate your systems. Pre-migration Tasks Before you migrate a system to Developer and Builder Release 3.3, you need to: Ensure your environment meets the hardware requirements for this release. See Hardware Requirements on page 2 1. Install Developer and Builder Release 3.3 and all required associated software. See Software Requirements on page 2 4. If applicable, install the latest Interim Corrections (ICs) for all software. See the Product Support page of Unisys Support Online, at http://www.support.unisys.com for IC information. Back up the system and data. Consider any relevant migration issues. See below for details. Migration Issues This section describes the main migration issues that apply when migrating to Developer and Builder Release 3.3. Note: If you are migrating from a release prior to Release 3.2, additional migration requirements may apply. To check these requirements, refer to the Migration Requirements section of the Software Release Announcements for all supported releases subsequent to your existing release level (available from the Support website, http://www.support.unisys.com). 78616349 004 3 1

Migration Requirements Host Builder and Runtime Test Environment Discontinued In Release 3.3, Host Builder is no longer available. All development now takes place in Developer. If you are using Host Builder, you will need to migrate your systems to Developer. The Enterprise Application Environment: Host to Developer Migration Guide provides information on migrating your environment, including differences between the Developer and Host Builder development environments. DYNIX/ptx Discontinued IBM no longer supports the DYNIX/ptx platform, so Enterprise Application Environment for DYNIX/ptx has been discontinued. If you are currently generating to DYNIX/ptx, you will need to migrate your systems either to one of the supported UNIX platforms (Solaris 8, AIX5L, or Unixware 7.1.1), or to another supported platform (Windows 2000, ClearPath MCP, or ClearPath OS 2200). UnixWare 7.1.3 UnixWare 7.1.3 (formerly known as Open Unix 8) is based on a component called the Linux Kernel Personality (LKP). Unixware 7.1.3 (including its supporting Oracle database and Micro Focus COBOL compiler) was not generally available for the Enterprise Application Environment 3.3 release date. A Runtime version supporting UnixWare 7.1.3 and related components will be made available after the general release of Enterprise Application Environment 3.3. For information on this release, see the Enterprise Application Environment Release and Support Plan, available from the Product Support website, at http://www.support.unisys.com/ind/txt/web-platform?pla=lin Transferring Host Subsystem Screens to Developer Host subsystems screens previously modified in Graphical Interface Workbench can be transferred to Developer using the Workbench to Developer utility. Automatic Generate on Migration When a system is migrated from a previous release of Enterprise Application Environment or LINC to Runtime Release 3.3, a full system generate automatically occurs. 3 2 78616349 004

Migration Requirements Configuring for Remote Subroutines in Developer Test Previously, to configure Developer Test to use remote subroutines you were required to create an LRSS configuration file to be referenced from the LINC.INI file. In this release, the details entered in the LRSS configuration file are retrieved from options defined in Developer. The Developer options that replace the LRSS configuration parameters for Developer Test must be manually defined to reflect the previous settings. The following table lists the parameters used to communicate with the host, and the corresponding Developer options: Parameter Host Type Developer Option Location REMOTEHOST All Host Name or TCP/IP address Developer Systems Defined in the Generate Set wizard or the New Host wizard. PORT All Port Developer Systems Developer Test page on Business Segment options dialog box USER All User Name, User ID, User Code Developer Test Open a Session dialog box PASSWORD All Password Developer Test Open a Session dialog box AUTHENTTYPE OS 2200 Security Environment SEARCHLOCAL All Enable Remote CALL statements LOCALMAP All Map Library Names for CALL statements Developer Systems Developer Test page on Business Segment options dialog box Developer Systems Developer Test page on Business Segment options dialog box Developer Business Segment options dialog box Developer Test Options ENVIRONMENT All Host Type Developer Systems Defined in the Generate Set wizard or the New Host wizard TRANSLATE All Data translation routines Developer Systems Developer Test page on Business Segment options dialog box ACCESSCODE MCP Access Code Developer Test Open a Session dialog box 78616349 004 3 3

Migration Requirements Parameter Host Type Developer Option Location ACCESSPASSWORD MCP Password Developer Test Open a Session dialog box CHARGECODE MCP Charge Code Developer Test Open a Session dialog box PRIMARYDISK MCP Primary Disk Developer Systems Developer Test page on Business Segment options dialog box SECONDARYDISK MCP Secondary Disk Developer Systems Developer Test page on Business Segment options dialog box LANGUAGE MCP Language Developer Systems Develoepr Test page on Business Segment options dialog box CODESET MCP Code Set Developer Systems Developer Test page on Business Segment options dialog box AUXILIARYDATA OS 2200 Authentication Data Developer Test Open a Session dialog box NTDOMAIN Windows Domain Developer Test Open a Session dialog box Configuring for Remote Routines in the Administration Client For Runtime for Windows Operating System environments, the settings previously entered in the LRSS.ini file must be manually transferred to the new Developer Test Host Server dialog box in Administration Client. SQL Scripts and Embedded Static SQL If your current UNIX system includes SQLScripts, these may become invalid when you migrate your system to Windows using SQL Server. This will occur if your static embedded SQL contains Oracle-specific entities, such as: ROWID The DUAL table Built-in Oracle SQL functions such as CONCAT and DECODE 3 4 78616349 004

Migration Requirements Running Multiple Versions It is recommended that only one copy of Enterprise Application Developer be installed on each workstation. However, if you choose to install more than one copy, you must keep all files from each version separate. The easiest way to do this is to specify a different target directory during installation. Migrating Systems with National Language Support CER Systems that utilize the National Language Support (NLS) CER require a special migration procedure, as this release does not support the NLS CER. To migrate an AIX system, you need to uninstall the NLS CER (EIF4964). You then need to set the National Item option in Developer for all Ispec alpha Data Items that are used as Profile keys for the Profiles defined as NLS under the workaround. For detailed instructions, refer to the Unisys Enterprise Application Runtime Release 3.3 for the UNIX Operating System Administration Guide. Migrating to Developer Release 3.3 To migrate your systems to Developer Release 3.3, you need to extract and load them into the new release. If you are migrating from a release earlier than LINC Development 2.4, you should contact your Support Administrator prior to migrating. Automatic Repository Upgrade For Upgrade Packs and ICs following Release 3.3 of Developer, the Automatic Repository Upgrade utility may be available. This utility lets you upgrade without extracting and loading. This utility is generally available for a release only if there are relatively minor changes to the Repository schema. Migrating to Builder Release 3.3 As the Builder Client is installed with Developer, and the Server is installed with Runtime, you must migrate to Release 3.3 of both Developer and Runtime before you can generate your Enterprise Application Environment systems. 78616349 004 3 5

Migration Requirements Migrating to Developer Version Control Release 3.3 To migrate the Version Control Bank to Release 3.3, you need to extract the contents of the Version Control Bank, and reload them into the new release. 3 6 78616349 004

Section 4 Release Functionality Enterprise Application Developer Release 3.3 introduces a host of new features that offer increased usability and configurability, greater database control, and improved screen design capabilities, enabling you to create systems quickly and cost effectively. In addition, Developer Release 3.3 offers an overall improvement in the performance of repository intensive transactions. Improvements have been made in the internal handling of transactions, optimization of the repository cache, and a reduction of deadlock situations. With the refinement of these mechanisms, Developer now performs 2-3 times better than Developer 3.2 for transaction and (non-exclusive mode) repository intensive operations, such as Load, Validate, and Version Control get and check-in functions. New Features in Developer and Builder The major new features of Developer and Builder Release 3.3 are introduced below: Developer features Developer Console enhancements LCIF Format Changes Ignored option in LCIF Viewer Keyword support Developer Painter enhancements Painting Host Subsystem Screens Cross-host access to Callable Global Logics Data Invocation (for ClearPath MCP) Static Embedded SQL (for Windows) User-Maintained Tables (for Windows) Host Database Access (for Windows and ClearPath OS 2200) Builder features Builder Scriptable Interface Builder Infrastructure enhancements Improved generate performance for multi-processor machines Bulk Options functionality (for ClearPath MCP) These features are outlined in the following subsections. 78616349 004 4 1

Release Functionality You can also find new feature information in the InfoPack Release 3.3, at http://www.support.unisys.com, under the Advanced Search option for the selected Enterprise Application Environment release. Developer Features Developer Console Enhancements Background Developer Console was introduced in Release 3.2. It consists of a command line interface to Developer that also allows script files to carry out standard Developer and Version Control operations. This means repetitive, time-consuming processes can be automated. Functionality Developer Console now offers the full range of basic Version Control commands provided by Developer. In addition to the existing Developer Console commands, the following Version Control operations are now available: Check in Check out Undo check out Labeling Delete and purge Developer Console also provides a number of Developer commands that do not need user intervention, but are usually time consuming and generally executed after hours. The Developer commands are: Validate logic Check repository Consolidate repository Developer Console also allows execution of a child process. Any process that can be run from Windows is acceptable, including Builder's Scriptable Interface. 4 2 78616349 004

Release Functionality LCIF Format Changes Ignored option in LCIF Viewer Background Differences between Developer Repository objects, Version Control Bank revisions, and LCIF (.mdl) files can be compared using the LCIF Viewer, or merged using the Developer merge facility. Previously, changes to the LCIF file format between Developer releases were displayed as differences, in addition to any actual changes made by you. Functionality Developer now provides the option to ignore differences that are a result of LCIF file format changes between Developer releases, and show only the actual changes that you have made. When this option is selected: The view, difference, and merge functions display all LCIF files as though they were created with the installed Developer release. The difference and merge functions only display differences that are a result of changes made by you. When this option is not selected, the view, difference, and merge functions behave as in previous Developer releases. Interface Changes The existing Merge, Difference and View Display Attributes dialog box now has an additional Ignore LCIF Format Changes option in the Attribute group. When the Ignore LCIF Format Changes option is selected: If Change is clicked, the new Ignore LCIF Format Changes dialog box is displayed. If Reset Default is clicked, the Ignore LCIF Changes setting reverts to OFF, without displaying the Ignore LCIF Format Changes dialog box. Keyword Support Background The Keywords feature has always been available in Host Builder. With the de-implementation of Host Builder for Release 3.3, this feature is designed to ease migration from a Host Builder to a Developer-based system. 78616349 004 4 3

Release Functionality Functionality Keywords allow you to associate multiple data fragments with a single Data Item. When the Data Item is displayed on a screen, the data fragments appear as individual Data Items. A Keyword can contain the following components: Displays (TERM.DISPLAY) Data fragments (TERM.ITEM) For example, a company could store employees payroll bank details using the full account number as the ordinate of a Bank Details Ispec. However, when displaying this data for browsing or update, the constituent parts (BSB, Branch, Account-Number) appear as individual Data Items. A Keyword is defined to display the Data Items as: BSB-No <nnnnnnnn>, Branch <nnnnnnn>, Account-Number <nnnnnnnnnn> Each fragment can be changed individually, but within the application the single Data Item BANK-ACCT contains the aggregate of the data fragments. Keywords can be included in the layouts of Ispecs and Insertable Global Logics. Users can add them either in the character Painter, or in the Model Directory window. They can position Keywords using Painter character mode, and modify the graphical and presentation attributes of individual Keyword components in Painter graphics mode. Interface Changes Keywords are created in the new Business Segment Keyword list, using the Keyword Options dialog box. The Business Segment Keyword list can be accessed from the new Keyword List button on the Open Business Segment dialog box. Alternatively, it can be accessed by a new Go command. The following new Go commands apply to Keywords: KEY Displays the Business Segment Keyword list. PA or PAI <keyword name> Displays the Painter screen of the specified Keyword. OP <keyword name> Displays the options dialog box of the specified Keyword. BR <keyword name> or TX <keyword name> Displays the Business Rules editor of the specified Keyword. DA <keyword name> Displays the Data Item list of the specified Keyword. The Keyword Painter allows you to add and maintain TERM.ITEMs and TERM.DISPLAYs. The Keyword Painter is similar to the character mode Painter for Ispecs and Insertable Global Logics, but it is only one line long.there is no equivalent graphics mode for the Keyword Painter. TERM.ITEMs can also be added from the Keyword Data Item list. 4 4 78616349 004

Release Functionality Developer Painter Enhancements Background This feature introduces several enhancements to the Developer Painter. Functionality from Graphical Interface Workbench has been incorporated into the Developer Painter. The following sections are covered: Text background transparency Color dialog box Multi line Display items Control Palette Tab order maintenance Multi Line Edit fields Password Edit fields Menu additions and changes CopyFrom Cells Text background transparency Developer Painter now allows the background of text objects to be transparent. Previously, the background for text objects was limited to a specific color. Transparency at the screen level inherits the transparency set at the Business Segment level. However, you can override this at the screen level. Use the Reset Defaults dialog box at the Screen level to reset the transparency set at the Business Segment level. Color Dialog Box This release of Developer Painter introduces the Color dialog box. The Color dialog box allows you to select different color settings for screens and Data Items. Selecting Default uses the colors defined at the Business Segment level. Selecting OS uses the colors defined for the operating system. Selecting User Specified allows you to define any color. The new Color dialog box gives you more options to define a form or Data Item s color settings. New preview fields have also been added to dialog boxes so you can see the current color settings defined for a Business Segment, Form or Data Item. Backcolor and Forecolor Preview Fields Preview fields that show the backcolor and forecolor selections have been added to the Screen Data Item - Display Attributes dialog box and Screen Display Item (for Graphic Screens) dialog box. 78616349 004 4 5

Release Functionality Multi Line Display items Developer Painter now allows you to create multi line text display items. Add lines to your display items by pressing Enter at the end of a line. Control Palette Developer Painter introduces the Control Palette. The Control Palette allows you to add graphical control objects to a screen without creating a Data Item. The Control Palette allows you to add: Push Buttons Radio Buttons List Boxes Combo Boxes Fields Images Check Boxes Note: You can also add graphical control objects using the Graphic Control command from the Add menu. Tab order maintenance Developer Painter has been enhanced to display the tab order numbers of Data Items and Graphical Control Objects on screens. This also allows you to re-sort the tab order by moving an item forwards, backwards, to the front, or to the back in the tab order, by using the keyboard or clicking a menu command. Multi Line Edit fields Edit fields can now span multiple lines. To specify an Edit field as multi line, double-click the Edit field and check the Multi Line checkbox. Password Edit fields Edit fields can now be defined as Password fields. That is, input characters are displayed as asterisks (*). View Field Names All Data Items and graphical control objects can now display their names. Previously, only Edit fields showed their names. Show Field Names by checking the Field Names command on the View menu. If the Field Names command is unchecked, the Display Value (if any) displays. 4 6 78616349 004

Release Functionality For consistency, the following menu item name changes have been made: Show Names command has been changed to Field Names Show Spaces command has been changed to Spaces. CopyFrom Cells In the past, Developer Painter only allowed CopyFrom Groups (Data and Display Items, rectangles and lines) to be modified as a whole block. In this release, Developer Painter allows CopyFrom Groups to be ungrouped as cells. Each cell can now be modified individually. A cell can be moved and/or hidden, and its graphical and presentation attributes changed. To ungroup a CopyFrom block into cells, uncheck the Grouped CopyFrom check box on the Form Characteristics dialog box. To set the tab order of CopyFrom cells, use the new CopyFrom Order field on the Screen Data Item dialog box. Painting Host Subsystem Screens Background This feature introduces to Developer the Graphical Interface Workbench functionality that enables you to change the screen layout of host subsystems such as ROC and ADHOC. Functionality The Developer installation includes a number of model files containing the host subsystem screens available for each host. You can load these screens into Developer as Ispecs, and use Painter to create graphical screens from the character-based screen layouts. Using Builder's Component Enabler capabilities, you can then generate the modified screens to be accessed by the deployed systems. Cross-host access to Callable Global Logics Background Callable Global Logics were introduced in Enterprise Application Environment Release 3.2. They provided a means of calling Performable Global Logic directly from 3GL and Enterprise Application Environment systems that are on the same host. However, the Callable Global Logics could not be called from other hosts or client PCs. This feature uses Component Enabler and the RATL protocol to provide cross-host access to Callable Global Logics. 78616349 004 4 7

Release Functionality Functionality This feature provides an option to generate an interface to Callable Global Logics. There is also a general client, called CGLGGeneral, that provides access to all the Callable Global Logics in the system. You might use the CGLGGeneral client if you want to call a number of Callable Global Logics. When using it, you need to specify the names of the Callable Global Logics and their parameters, as well as the host details. Interface Changes The Component Enabler Bundle Options dialog box in Developer contains a new check box for generating Callable Global Logic interfaces, and radio buttons for choosing either the default generator or a user-defined generator: Callable GLG Interface generation required check box Generate interfaces to Callable Global Logics. Default Generator radio button Use the supplied generator to generate the interfaces. User Defined radio button Use your own generator to generate the interfaces. Java Class text box Enter the Java Class name of the generator, if you are not using the default generator. Data Invocation (for ClearPath MCP) Background Data invocation is a feature of MCP based Host Builder, that has been incorporated into Developer, now that Host Builder has been discontinued. Functionality For an MCP based System, values of Data Items and Profile Ordinates may be stored on the Profile itself, as well as in the Ispec records. With data invocation, the value of the Data Item can be accessed without accessing the Ispec record, reducing the number of database reads. This can provide significant performance benefits when accessing the database, if used appropriately. Interface Changes The Use Data Invocation check box (on the Generate page of the Business Segment Options for ClearPath MCP dialog box) is now supported. Checking the check box activates data invocation for the generated system. By default, the check box is unchecked. 4 8 78616349 004

Release Functionality Static Embedded SQL (for Windows) Background In Enterprise Application Environment Release 3.2, the use of static embedded SQL was enabled for UNIX systems. Release 3.3 now brings the use of static embedded SQL for Windows systems. Functionality Prior to the introduction of this feature, standard Enterprise Application Environment data access commands were structured around record-by-record processing from a database. You could use successive nested DETERMINE; commands to achieve the effects of a table join, but there was no optimization (although it was possible to optimize database access for individual commands). With the introduction of this feature, you can now access database tables directly by invoking static embedded SQL constructs from within logic. Static embedded SQL can also use advanced constructs such as table joins and updates over a selected set of rows. Use of table joins avoids the need to use nested DETERMINE; commands, and updates over a selected set of rows can increase efficiency in appropriate circumstances. The ability to encode static embedded SQL means that you can make more efficient use of the database by allowing the database engine to use optimizations for data retrieval and/or update. If you are developing for multiple platforms you can use the variable GLB.MACHINE (which determines the runtime platform) together with conditional statements such as DO.WHEN; or CASE; to determine whether or not to use the static embedded SQL. For example, you can specify that if the platform is UNIX or Windows, the static embedded SQL is executed, and if it is ClearPath OS 2200 or ClearPath MCP, to use alternative code that you provide for these platforms. Interface Changes In Developer, there are no interface changes from Release 3.2. However, the following items, which were ignored for all target hosts other than UNIX, are now implemented for Windows target hosts as well as UNIX: SQLScript object SQLScript Options dialog box Open SQLScript dialog box SQLScript List Script List option in the Open Business Segment dialog box Script command from the Add menu 78616349 004 4 9

Release Functionality In Developer Security, two new functions have been added to the User/Function Matrix: SCRIPT, which allows you to add, delete, and modify SQL Scripts LOGIC,SCPT, which allows you to edit SQL Script logic User-Maintained Tables (for Windows) Background Enterprise Application Environment uses third party database engines for Windows and UNIX operating environments. Previously, Runtime for the Windows Operating System users depended exclusively on Enterprise Application Environment to take advantage of a database's functionality. Functionality This release now allows Runtime for Windows Operating Systems users to mark Ispecs (tables) and Profiles (indexes) as user-maintained. This functionality is available for both Oracle and Microsoft SQL Server database engines. This new functionality presents you greater database control without the need to wait for features to be incorporated into Enterprise Application Environment. Interface Changes The User-Maintained check box has been added to the Environment tab of the: Component options for Windows dialog box Profile options for Windows dialog box Access these dialog boxes by selecting a Windows Generate Set, a Component or Profile, and then the Open Selected command on the File menu. Additionally, user-maintained Ispecs are disabled on the Bulk Options tab of the Business Segment options for Windows dialog box. Host Database Access (for Windows and ClearPath OS 2200) Background For Release 3.2, Host Database Access was implemented for ClearPath MCP only. For this release, the functionality has been extended to Windows and ClearPath OS 2200, and the implementation of the feature has changed. This feature also includes changes to the configuration of Developer Test for remote subroutine calls. 4 10 78616349 004

Release Functionality Functionality Host Database Access allows you to test and debug systems against test host databases using Developer Test. This removes any anomalies that can be encountered when testing against a local D-ISAM database. The configuration details for accessing a host database are defined using the Generate Set options in Developer. From here you can enable Developer Test to access specific systems on the host and specify that the necessary files be generated by Builder. Some configuration is also required on the host. The configuration of Developer Test for remote subroutine calls now also uses options defined in Developer, replacing the need to manually create a configuration file and edit the LINC.ini file. Interface Changes In Release 3.2 the configuration for Host Database Access for ClearPath MCP was performed in Developer Test. In this release, the configuration options have been moved to the Developer Systems Generate Set options, along with the options for configuring Developer Test to use remote subroutine calls. In Developer Systems, a Developer Test properties page has been added for each platform, enabling you to enter the information necessary for locating LRSS, and control the CALL statement when accessing LRSS. Note: For the UNIX operating system, the properties page provides options that enable Developer Test to access the subroutine on the host, and sets some of the required configuration options. Host database access is not implemented for UNIX in this release. In the Windows Administration Client, the Developer Test Host Server page has been added to the Environment Configuration property sheet. It allows you to enter the information needed to configure the server for access by Developer Test, and replaces the need to manually edit the LRSS.ini file. 78616349 004 4 11

Release Functionality Builder Features Builder Scriptable Interface Background Regular daily generates are often performed in an off-peak timeslot, without the need for manual intervention. This feature provides a method for generating and building systems in batch mode. Functionality The Scriptable Interface is an extension to Developer and Developer Console that allows you to generate and build your systems and reports without any manual intervention. The interface consists of a set of scripts to automatically control Builder Client functionality. These scripts can be executed from Developer Console to control the Direct Generate process. This means a generate can be run in batch mode and unattended, such as overnight. It can also be used when Developer is running to allow you to test your script properties interactively. The Scriptable Interface is installed as part of a standard Builder Client installation, and includes sample scripts to set up a properties file, generate a system, generate reports or report groups, install a system, and generate a Component Enabler Bundle. You can modify these scripts or write your own in any language that supports Windows COM objects, to include any extra functions you require for example, sending an SMS message to the responsible engineer if the generate is not successful. However, modification of the supplied Builder scripts is generally not required; nor is it recommended in the majority of cases, as it demands an advanced level of scripting and process automation experience. If you do have specific requirements that are not addressed by the functionality of the Builder scripts, you should contact Unisys Technical Consulting Services to discuss your needs. Interface Changes A new command, exec, has been added to the Developer Console. The exec command can execute any process that can be run from Windows. The syntax is: exec (commandline) 4 12 78616349 004

Release Functionality Builder Infrastructure Enhancements The Builder Infrastructure has been enhanced to: Allow you to download error logs Remove the obsolete In All Subsystems option Downloading Server Error Logs Previously, if a Direct Generate failed after being transferred to the host, it was difficult to locate the error log files to determine the cause of the failure. In this release, if a generate failure occurs on the host, the Builder Client is notified that deployment has failed and you are given the option to download the error log files created on the host. The size of the log file is determined and if it is larger than 1MB, you are given the option to skip the download. The names and location of the downloaded files are displayed in the Builder Client Status window. The ability to download host error log files to the workstation makes the analysis of compile and deployment problems more time efficient. Removal of the In All Subsystems Option The ClearPath MCP Ispec option In All Subsystems is obsolete and has been removed from Developer and Builder. Improved generate performance for multi-processor machines The Direct Generation process performed by Builder has been improved to ensure that when using multi-processor machines the overall elapsed time is reduced. This has been achieved by increasing the number of generate threads to eight. Bulk Options functionality (for ClearPath MCP) Background The options to use DMS II Extended Edition (Enterprise Database Server Extended Edition for ClearPath MCP) and to optimize blocksize to VSS-2 are available for ClearPath MCP. They can be set for a whole Business Segment, or for individual Ispecs. When you first set these options, it causes a database reorganization. For very large databases the DMS II software may not be able to handle the changes in a single reorganization, but Builder cannot determine in advance whether the reorganization will fail. If it does, you need to split the changes between two or more reorganizations, by setting the options for only some Ispecs at a time. 78616349 004 4 13

Release Functionality Functionality In this release, the DMS II Extended Edition and Optimize Blocksize to VSS-2 options can be quickly set (or unset) for several individual Ispecs at a time, using the Bulk Options functionality. The effect of reorganization on Profiles is different for the two options: The DMS II Extended Edition option causes extra data to be included within an Ispec. The Ispec is reorganized, as are any Profiles that access it. The Optimize Blocksize to VSS-2 option only affects Profiles that access the Ispec's dataset. This means that the Profiles are reorganized, but not the dataset. You will need to regenerate any reports that access or use Ispecs or Profiles that have been reorganized. 4 14 78616349 004

Section 5 Restrictions and Known Limitations This section describes the restrictions and limitations that apply to Developer and Builder Release 3.3. For the latest restrictions information, refer to the README.HTM file available on the Unisys Support Online website at http://www.service.unisys.com. Note: If you are migrating from a release prior to Release 3.2, additional restrictions may apply. To check these restrictions, refer to the Restrictions and Limitations section of the Software Release Announcements for all supported releases subsequent to your existing release level (available from the Support website, http://www.support.unisys.com). Developer and Builder Release 3.3 Restrictions General Restrictions Matching Developer, Builder, and Runtime Required You can only generate systems that were developed in Developer Release 3.3 with Builder Client and Server Release 3.3. Similarly, you can only Direct Generate using Builder Client and Server Release 3.3 to a target host that is running Runtime Release 3.3 for the appropriate operating system. You cannot generate or deploy Developer Release 3.3 systems using earlier releases of Builder, Host Builder, and Runtime. Windows 2000 Restriction For Windows 2000, Terminal Services requires Windows 2000 Server or Advanced Server. Host Builder and Runtime Test Environment Discontinued With the release of LINC (Enterprise Application Environment) on Windows platforms, came the ability to generate a Runtime system directly from LDA (Developer). With subsequent releases, this capability was extended to all host platforms, making the hostbased development environment redundant. 78616349 004 5 1

Restrictions and Known Limitations In Release 3.3, Host Builder is no longer available for any platform. All development now takes place in Developer. Builder Client is provided on the Developer CD-ROM and no longer requires an installation key. Builder Server is packaged on the media for each supported Runtime environment. A Runtime package that includes Builder Server is available for each host platform. With the de-implementation of Host Builder in Release 3.3, the Runtime Test Environment is no longer required, as Developer Test can be used for testing and debugging. For this reason, Runtime Test Environment has also been discontinued. Separate Enterprise Application Environment utilities, such as ROC and ADHOC (for ClearPath MCP), are still available. For UNIX platforms, the Griffin database is no longer required, as it was only used for Host Builder. The following interfaces are no longer available: Host Builder Runtime Test Environment Griffin Database (on UNIX platforms) On OS 2200, Host Builder supports multi-table Ispecs, allowing up to 2400 columns per Ispec and a record size of 70,000 characters, provided that no single column was greater than 7000 characters. Multi-table Ispecs are not supported by Developer, so only 250 columns and a maximum of 7000 characters per Ispec are now allowed. If you are using Host Builder, you will need to migrate your systems to Developer. However, before doing so, ensure that Ispecs are within column and size limits. If not, Ispecs must be recoded to correspond to the new limits. The Enterprise Application Environment Host to Developer Migration Guide provides information on migrating your environment, including differences between the Developer and Host Builder development environments. DYNIX/ptx Discontinued Support for the DYNIX/ptx platform has been discontinued as IBM no longer supports it. For more information, see DYNIX/ptx Discontinued under Migration Issues on page 3 1 ON.CHANGE; Command Restrictions The following restrictions apply to the ON.CHANGE; command: Developer cannot detect when an ON.CHANGE; command uses a heading or footer containing another ON.CHANGE; command in its Frame logic. Nested ON.CHANGE; commands produce unpredictable results. If you are using multiple ON.CHANGE; loops, you must initialize any Data Items used as control breaks within each loop. 5 2 78616349 004

Restrictions and Known Limitations When using the ON.CHANGE; statistical routines, internal working storage variables are generated in the report to store the intermediate values for some of the calculations. If you are using multiple ON.CHANGE; loops, you must ensure your working storage variables are unique to the loop in which they are used, or initialized at the beginning of the loop. TRACE; Command The TRACE; command (giving the facility to trace the execution of logic and send to a file) is not implemented in Developer Release 3.3. This command was only available when developing and generating on the host. Developer Limitations Developer Console Enhancements The following limitations apply to the Developer Console Enhancements feature: The check repository and consolidate repository commands can only be run while in single-user mode. This is consistent with existing Developer behavior. The consolidate repository command can only be issued at the end of a Developer Console session, as it will shutdown Developer Console after completing, even if subsequent commands exist in the script file from which it was issued. This is also consistent with existing Developer behavior. LCIF Format Changes Ignored in LCIF Viewer Regardless of the Ignore LCIF Changes setting, a Specification Difference Report displays: GSD Blocks as added, if GSD Blocks are not present in the first specification being compared. GSD Blocks are displayed as deleted if not present in the second specification. For example, GSD Block may not be present if a specification was created with a version of Developer prior to Release 3.1, or simply that GSD Blocks have yet to be added to the specification. LCIF file format Keyword differences between the two specifications. LCIF file format differences between a host-generated LCIF file and another specification (host-generated or otherwise). LCIF file format Fast Load Report data differences between the two specifications. Keyword Support The following limitations apply to the Keywords feature: The definition of a Keyword cannot be modified in the Ispec or Insertable Global Logic where it is inserted. If you attempt to delete any TERM.ITEM from a Keyword in the graphics painter, the entire Keyword is removed from both the character and graphics Painter. A message box displays warning you of this behavior. 78616349 004 5 3

Restrictions and Known Limitations A zero length Keyword (one that does not contain any TERM.ITEMs or TERM.DISPLAYs) cannot be inserted in an Ispec or Insertable Global Logic. The length of a Keyword is not set, but changes with the number of TERM.ITEMs or TERM.DISPLAYs added to it. Correspondingly, you cannot create a Keyword from a Data Dictionary item. Similarly, the individual TERM.ITEMs cannot be Data Dictionary items Cross-host access to Callable Global Logics To use this feature, you must: Install Component Enabler Enable Big Buffer Ispecs Data Invocation (for ClearPath MCP) Data invocation is ignored if Integrity is enabled for the Business Segment and not disabled for the Ispec or Report. Static Embedded SQL (for Windows) Static embedded SQL is ignored for ClearPath MCP and ClearPath OS 2200 target hosts, and in Developer Test. Developer does not validate your SQL syntax. It simply performs a lexical scan to replace unqualified names with their qualified equivalents during generation. User-Maintained Tables (for Windows) The following limitations apply to the User-Maintained Tables feature: Conditional Profiles and Ispecs containing Conditional Profiles cannot be usermaintained. SQL Views are not created, maintained, or dropped for user-maintained Ispecs and Profiles. Profiles over Events may only be user-maintained if they span all Events. Extra columns in user-maintained Ispecs that are not part of the Ispec definition must allow nulls or have default values specified. Before reverting user-maintained Ispecs or Profiles, related database table and indexes must be in a compatible Enterprise Application Environment form. Host Database Access (for Windows and ClearPath OS 2200) Generate time may be increased due to the need to generate and deploy files for the Developer Test Host Server. The performance of Developer Test may be affected by the speed of network connections, traffic on the network, and by the size and number of records retrieved from the deployed database. 5 4 78616349 004

Restrictions and Known Limitations Host Database Access is not implemented for UNIX operating systems. Builder Client Limitations Builder Scriptable Interface Since the Builder Scriptable Interface is designed to be run for unattended Direct Generates, it cannot be used for most tasks that require decisions and intervention, such as restarting a failed generate. The interface does not allow concurrent scripted generates on a single workstation. Bulk Options functionality (for ClearPath MCP) These option settings make use of features of DMS II, which has its own limitations. Before using these features, you should read the DMS II documentation thoroughly. 78616349 004 5 5

Restrictions and Known Limitations 5 6 78616349 004

Section 6 Support This section describes the support services that are available to users of Developer and Builder Release 3.3. Unisys Support Online Unisys Support Online is a web-based online technical resource that is available to all Unisys clients with a service agreement. Unisys Support Online puts a wealth of technical information regarding hardware and software product support services at your fingertips. Unisys technical specialists provide updated symptom and solution information, including frequently asked questions. Unisys Support Online is available 24 hours a day, 7 days a week at http://www.service.unisys.com. Unisys Support Online allows you to: Search technical databases for information on a problem. Download IC files containing fixes. Track the progress of software updates and fixes. Participate in support forums. Access instructional information in Customer Technical Bulletins. Log and track support requests. Unisys Client Support Center The Unisys Client Support Center is your information resource for problems that cannot be resolved through Unisys Support Online or your site administrator. Your site administrator can place a support request electronically. The Electronic Support Request interface allows you to pose technical questions, discuss technical issues, and escalate design concerns with the experts at the Unisys Client Support Center. 78616349 004 6 1

Support When logging an Electronic Support Request you need to specify the: Hardware model number Operating environment Software product and level code The software product and level code for Developer and Builder Client Release 3.3 is LINC-3R3DEV. Direct Telephone Support Unisys also offers direct telephone support. If you are located within the continental United States or Canada, you can call one of the following toll-free numbers during the times indicated in your service agreement: United States 800-328-0440 (prompt 4) Canada (English) 800-387-6181 Canada (French) 800-361-8097 Customers outside the continental United States or Canada should refer to their local Unisys representative for support contact information. Software Support Services Unisys Client Support Centers offer Software Support Services, a full complement of technical services to help clients with cost effective, fast-cycle support. Software Support Services include: Software support ambassador personalized attention from a dedicated Unisys Client Support Center specialist. System generation assistance in installing or generating system software upgrades and enhancements. System migration planning and optimization of system migration and upgrades. Performance Reviews evaluation of existing systems and networks, and tuning recommendations. Communications systems enhancements assistance in the configuration, generation, and installation of communications systems. Database management consulting evaluation of systems and database backup procedures to ensure they promote data recovery. Administration seminars, and recovery tape and audit trail configuration. 6 2 78616349 004

Support For more information on Software Support Services, see Unisys Support Online at http://www.service.unisys.com, call Unisys directly on 800-328-0440 (prompt 4), or contact your local Unisys representative. De-implementations Support for all of the following releases has ceased: All releases up to and including LINC 16.4 All releases up to and including LDA 2.4 Product Information for these products can no longer be ordered. For the latest information about de-implementations, see the Enterprise Application Environment Release and Support Plan, accessed via the Product Support page on the Unisys Support Online website, at http://www.support.unisys.com/ind/txt/web-platform?pla=lin. 78616349 004 6 3

Support 6 4 78616349 004

Section 7 Customer Product Information This section describes the Customer Product Information that is available for Enterprise Application Developer and Builder Release 3.3. Developer and Builder Documentation Documentation for Developer and Builder Release 3.3 is provided on the Enterprise Application Environment 3.3 Documentation CD-ROM. Use Adobe Acrobat Reader, provided on the Documentation CD-ROM, to read the product documentation (see instructions in the CD-ROM insert booklet). Documentation CD-ROM The Enterprise Application Environment 3.3 Documentation CD-ROM is a dedicated documentation CD-ROM included with all Enterprise Application Environment products. It provides product information on all Release 3.3 software, including: Developer, Builder, and Version Control Runtime for all platforms Client Tools: Component Enabler, Presentation Client, ASP Generator, ASP Generator Customization Kit, Client Generator for Microsoft Visual Basic, and Business Integrator. The Documentation CD-ROM also includes the Enterprise Application Environment InfoPack Release 3.3, an online guide to the new features in this release. These documents are also available from the Product Support page at Unisys Support Online (http://www.support.unisys.com). Copies of the Documentation CD-ROM (Part Number 7861 6513-005) can be ordered separately from the Unisys Online Bookstore at http://www.bookstore.unisys.com. 78616349 004 7 1

Customer Product Information Enterprise Application Environment Documentation The following table lists the generic Enterprise Application Environment documentation that is available on the Documentation CD-ROM. Document Title Part Number Enterprise Application Programming Reference Manual 7861 6075-003 Enterprise Application Ad Hoc Inquiry Guide 7861 6059-003 Enterprise Application Environment: Host to Developer Migration Guide 7862 6074-002 Enterprise Application Developer and Builder Documentation The following table lists the documentation on the Documentation and software CD-ROMs that is specific to Enterprise Application Developer and Builder. Document Title Part Number Enterprise Application Developer Installation and Configuration Guide 7861 6109-004 Enterprise Application Developer User Guide 7861 6117-004 Enterprise Application Developer Administration Guide 7861 6125-004 Enterprise Application Developer Version Control Guide 7861 6133-004 Enterprise Application Builder Guide 7861 6166-004 Additional Documentation The following hard copy and PDF documentation is also available for Developer Release 3.3. Document Title Part Number Enterprise Application Programming Reference Handbook 7861 6067-003 Localization Instructions for Enterprise Application Developer 7861 6141-004 Online Help Developer and Builder Release 3.3 have comprehensive online manuals and contextsensitive help. The online manuals provide overview and procedural information about the software and its features, and are accessed via the product Help menus. The context-sensitive help provides specific information about a window, command, or field, and is accessed by pressing [F1] from the required menu or screen. 7 2 78616349 004

Customer Product Information Context-sensitive help topics are intuitively linked to the online manuals. This provides the ability to navigate quickly between the context-sensitive help and related topics in the online manuals. Computer-based Training Getting Started with Enterprise Application Developer is a self-paced guide to developing user applications using Enterprise Application Developer. Interactive lessons help students to understand concepts, and practical hands-on activities apply these concepts to build and test a simple Enterprise Application Environment system. This course is ideal for organizations already using Enterprise Application Developer, where experienced developers can mentor the students. Intended Audience This course was designed for: Developers with little or no experience in developing Enterprise Application Environment systems Experienced Enterprise Application Environment developers wanting to extend or refresh their knowledge Course Content Getting Started with Enterprise Application Developer explains Enterprise Application Environment basics, including components, the runtime cycle, and logic. The course contains: A student guide with lesson summaries and activities Computer-based training lessons Screen demonstrations on how to complete tasks in the Developer environment Getting Started with Enterprise Application Developer (Part Number 7861 6612-002) can be ordered from the Unisys Online Bookstore at http://www.bookstore.unisys.com. Instructor-led Courses There are also a number of instructor-led Enterprise Application Environment courses available. Some examples are: Introduction to Enterprise Application Environment for Management Introduction to Enterprise Application Environment for Technical and Management Personnel 78616349 004 7 3

Customer Product Information Introduction to Enterprise Application Developer Managing Enterprise Application Developer Component Enabler Workshop Runtime for Windows 2000 (SQL) Runtime for Windows 2000 (ORACLE) For more information on these (or other) courses, and bookings, see the Unisys Customer Education website, at http://www.unisys.com/customer-education/, or contact your local Client Support Center or Unisys representative. Introduction to Enterprise Application Environment for Management (CEL8001) Introduction to Enterprise Application Environment for Management is a modular course intended for first-time and prospective users of Enterprise Application Environment software. It teaches participants about the Enterprise Application Environment development process: explaining what it is, how it works, and the benefits of using it. Introduction to Enterprise Application Environment for Management and Technical Personnel (CEL8002) This course provides a more technical treatment of the material presented in CEL8001 Introduction to Enterprise Application Environment for Management. Introduction to Enterprise Application Developer (CEL800) Introduction to Enterprise Application Developer is a practical workshop designed to train developers in the skills they need to develop and maintain Enterprise Application Environment systems. It is aimed at developers with little or no experience with developing for the Enterprise Application Environment. With guidance from the instructor, participants will practise coding and debugging an Enterprise Application Environment system in a Windows-based Developer environment. Managing Enterprise Application Developer (CEL8006) For participants responsible for the set-up, deployment, maintenance, and administration of the Developer environment. The Course addresses the use of features and functions that promote secure management of the development, testing, and deployment environment. 7 4 78616349 004

Customer Product Information Component Enabler Workshop (CEL8007) Designed to assist developers to Web-enable their Enterprise Application Environment Runtime Systems using a variety of technologies to match their needs and environments. The Course provides instruction on installing, customizing, and writing applications for Component Enabler, using a wide variety of technologies. Runtime for Windows 2000 (003386) Runtime for Windows 2000 is an instructor-led course for those involved in developing and supporting Enterprise Application Environment systems for Windows 2000 using SQL Server as the database management system. Designed to cover the support environment and processes for the generation, deployment, and management of an Enterprise Application Environment system for Windows 2000, the course consists of a number of related modules. It covers topics from installation of the software, to managing and running the system on the Windows operating systems. Runtime for Windows 2000 (003785) As above, but using ORACLE as the database management system. 78616349 004 7 5

Customer Product Information 7 6 78616349 004

Section 8 Ordering Procedure This section provides licensing and ordering details for Enterprise Application Developer and Builder Release 3.3. Enterprise Application Environment Product Package Developer and Builder Product Package When you purchase the Enterprise Application Developer Release 3.3 license, you will receive: Enterprise Application Developer 3.3 CD-ROM, containing: Developer Release 3.3 software, including Developer Test, Developer Security and Repository Builder Client Release 3.3 software (this software no longer requires an installation key, and can optionally be installed by selecting the Custom option during installation) Version Control Release 3.3 software (separately licensed and accessed by an installation key) Developer, Builder Client, and Version Control documentation Enterprise Application Environment 3.3 Documentation CD-ROM A printed copy of this Software Release Announcement Host Builder and Runtime Test Environment Discontinued In Release 3.3, Host Builder is no longer available for any platform. All development now takes place in Developer and systems are generated directly from the workstation using Builder Client and Builder Server, also known as Direct Generate. Note: There is no requirement to license a Builder style when ordering Release 3.3. The Builder Client is provided on the Developer CD-ROM and the Builder Server is packaged on the Runtime CD-ROM or tape. Customers requiring earlier versions of Builder software must request the specific release level required when ordering. With the de-implementation of Host Builder, the Runtime Test Environment is no longer required, as Developer Test can be used for testing and debugging. For this reason, Runtime Test Environment has also been discontinued. Earlier releases of Host Builder and Runtime Test Environment are still available. 78616349 004 8 1

Ordering Procedure Developer Version Control Product Package When you purchase the Developer Version Control license for Release 3.3, you will receive: Installation key letter (hard copy) required for the Version Control software. Ordering Developer and Builder, and Version Control Clients/Sites in the USA To order the products described in this Software Release Announcement, clients in the USA can contact: Unisys Corporation Software Services 1 Unisys Way Blue Bell, PA 19424 Telephone: 800-829-1313 (valid only in the USA) Fax: 215-986-9281 Email: SUOA@unisys.com The local Unisys representative or organization An authorized Unisys Value Added Reseller Clients/Sites Outside the USA To order the products described in this Software Release Announcement, clients outside the USA can contact: The local Unisys representative or organization An authorized Unisys Value Added Reseller Licensing Options To order Developer or Version Control you need to identify the number of licenses you require. Each license is identified by a style ID, with separate styles for new and update licenses. Software Update Subscriptions that provide no charge updates to future releases are also available for an additional annual fee. 8 2 78616349 004

Ordering Procedure Developer Licenses Developer Release 3.3 uses Concurrent licensing only. That is, one license is required for each development user that that will use Developer and/or Builder Client at any one time. Named Developer version New license styles for the Named Developer version have been discontinued and can no longer be ordered. Update styles are still available and can be ordered by customers who have current license agreements for previous releases. For more information, see License Styles on page 8 3. Note: Builder Client is installed by selecting the Custom option during installation. An installation key is no longer required. To generate a system, Runtime licenses are required for each Runtime environment you plan to generate to. For more information, see the Runtime Release 3.3 Software Release Announcement for the relevant operating system. Version Control Licenses Version Control is licensed separately from Developer and requires a software installation key. A license is required for each for each installation of Version Control Client. License Styles Different license styles are available, depending on your current licensing agreement (if any): New licenses Update licenses New Licenses New licenses are for users who do not have a current license agreement for Developer/ LINC Development, or Version Control. They are subject to the full new license fee for the product. Update Licenses Update licenses are for users who have a current license agreement for an earlier version of LINC Development (for example, Release 2.4). Update licenses may be subject to an update fee when moving from one chargeable release level to the next (for example, to upgrade from LINC Development 2.4 to Developer Release 3.3). 78616349 004 8 3

Ordering Procedure Customers with a valid Software Update Subscription and maintenance agreement for the product are entitled to the update style at no charge. Customers without a Software Update Subscription will be charged an update fee. Updates within the same release series (for example, from Release 3.2 to 3.3) are provided at no additional charge to users with current maintenance agreements. Software Update Subscriptions Software Update Subscriptions provide no charge updates to future releases for an annual subscription fee. Customers with a Software Update Subscription do not pay the update license fee when updating to a new release level, provided they have a valid maintenance agreement, and Software Update Subscription coverage has been continuous from the original software shipment date. Software Update Subscriptions for Developer include coverage for these separately priced software products: Version Control ASP Generator ASP Generator Customization Kit Client Generator for Microsoft Visual Basic Separate subscription styles do not exist for these products. For this reason, the number of licenses for each of these products cannot individually exceed the number of Developer licenses. Software Update Subscriptions for Developer are based solely on the number of Developer licenses. The same subscription style applies to all license types and are ordered using the relevant Software Update Subscription style ID. Note: Software Update Subscriptions must be ordered when the new or update license to which it applies is purchased. 8 4 78616349 004

Ordering Procedure Developer Style IDs New Licenses The following table shows the style ID used to order new licenses for Developer Release 3.3. Usage type Style ID One Concurrent user EDV999-CD 10 Concurrent user pack EDV999010-CD 20 Concurrent user pack EDV999020-CD 30 Concurrent user pack EDV999030-CD 50 Concurrent user pack EDV999050-CD 75 Concurrent user pack EDV999075-CD 100 Concurrent user pack EDV999100-CD Note: New license styles for the Named Developer version have been discontinued and can no longer be ordered. Update Licenses The following table shows the style ID used to order update licenses for Developer Release 3.3. Usage type Style ID One Concurrent user One Named user EDV223-CD EDV223-ND Customers who have licensed Developer multiple-user packs should order the appropriate number of update licenses (for example, 10, 20, 30, 50, 75 or 100). Note: Whether you order the Concurrent user, or Named user update license, you will receive the Concurrent user version of Developer as there is only one version of Developer for Release 3.3. Nonetheless, you should order the correct update style based on your current license agreement. 78616349 004 8 5

Ordering Procedure Software Update Subscriptions The following table shows the style ID used to order Software Update Subscriptions for Developer Release 3.3. Note: Software Update Subscriptions must be ordered when the new or update license to which it applies is purchased. Usage type Style ID One Concurrent user One Named Developer EDV100-CDS EDV100-NDS Version Control Style IDs The following table shows the style ID used to order licenses for Version Control Release 3.3. Note: The Software Update Subscription for Version Control is bundled with the Developer Software Update Subscription. A separate Software Update Subscription for Version Control is not offered or necessary. License type Style ID Standard EDV999-VCC 8 6 78616349 004

*78616349-004* 78616349-004