ddddssssdddd bbbbuuuussssiiinnnneeeessssssss … · 2020. 11. 25. · windowswin dowsdows is a...

DDDDDDDDSSSSSSSSDDDDDDDD BBBBBBBBuuuuuuuussssssssiiiiiiiinnnnnnnneeeeeeeessssssssssssssss SSSSSSSSyyyyyyyysssssssstttttttteeeeeeeemmmmmmmmssssssss MAS 90 EnhancementsMAS 90 EnhancementsMAS 90 EnhancementsMAS 90 Enhancements

CodeZillaCodeZillaCodeZillaCodeZilla

MAS90 Development IDEMAS90 Development IDEMAS90 Development IDEMAS90 Development IDE

Version Version Version Version 4.4.54.4.54.4.54.4.5

CodeZilla User ManualCodeZilla User ManualCodeZilla User ManualCodeZilla User Manual 2

Copyright 2007 DSD Business Systems

Information in this document is subject to change without notice.

Copyright 1993-2007, DSD Business Systems All rights reserved.

CodeZilla Users Manual Version 4.4.5 14 December, 2007

DSD Business Systems 5120 Shoreham Place Suite 280 San Diego, CA 92122 858/550-5900 8:00am to 5:00pm PST 858/550-4900 Fax

TrademarksTrademarksTrademarksTrademarks

ProvideXProvideXProvideXProvideX is a Trademark of Sage Software.

WinWinWinWindowsdowsdowsdows is a trademark of Microsoft Corporation.

MAS 90 MAS 90 MAS 90 MAS 90 is a registered trademark of Sage Software.

All other product names and brand names are service marks, and/or trademarks or registered trademarks of their respective companies.

This documentation and the software described herein, is prepared and published under license. Sage Software has not tested or verified either the software or any representation in this documentation regarding the software. Sage Software does not make any warranty with respect to either this documentation or the software described herein, and specifically disclaims any warranty, express or implied, with respect hereto, including the warranties of fitness for a particular purpose and merchantability.



Table oTable oTable oTable of Contentsf Contentsf Contentsf Contents Table of Contents ............................................................................................................... 3 Release Notes .................................................................................................................... 5 Release Notes for CodeZilla 4.4 ................................................................................... 5 Release Notes for CodeZilla 4.3 ................................................................................... 5 Release Notes for 4.10 ................................................................................................. 5 Release Notes for 4.0.................................................................................................... 6

New Features ..................................................................................................................... 8 New Features for Version 4.5 ....................................................................................... 8 New Features for Version 4.3 ....................................................................................... 8 New Features for Version 1.10 ....................................................................................... 8

Overview ............................................................................................................................. 9 Features and Benefits ................................................................................................. 10

Menu Selections .............................................................................................................. 12 File Menu ...................................................................................................................... 13 Opening a Project Folder ......................................................................................... 13 Close Project Folder ................................................................................................. 13 Select Test System................................................................................................... 14 Install Project to Test System.................................................................................. 14 Synchronize Project and Test System .................................................................... 15 Distribute Project ..................................................................................................... 15 Add File to Project .................................................................................................... 17 Run Selected ............................................................................................................ 17 Project Properties..................................................................................................... 17 Exit ............................................................................................................................ 19

Utilities Menu ............................................................................................................... 20 Delete Application .................................................................................................... 20

Data Menu..................................................................................................................... 21 CTL (Control) File Maintenance............................................................................... 21 DD1/DD2 Roswell Data Dictionary Maintenance.................................................. 22 DCT Data Dictionary - Pre-3.60 ............................................................................... 23 MNU (Menu) File Maintenance ............................................................................... 24 FRM Form File - Pre-3.60 ........................................................................................ 27 EOP End of Period .................................................................................................... 29 RUN Run File ............................................................................................................ 30 CMP Dictionary Compile .......................................................................................... 30 FIL (File/Record) File Maintenance - Pre 3.60....................................................... 31 Create Data Files...................................................................................................... 32

Sage Menu ................................................................................................................... 35 Run Menu ..................................................................................................................... 36 Menus: ...................................................................................................................... 36 Editor (PvX) ............................................................................................................... 37 Nomads .................................................................................................................... 37 ProvideX Prompt....................................................................................................... 38 DOS Prompt .............................................................................................................. 38



Windows Explorer..................................................................................................... 38 MAS90 ...................................................................................................................... 38

View Menu .................................................................................................................... 39 Act On........................................................................................................................ 39 Refresh ..................................................................................................................... 39 Options...................................................................................................................... 39 Toolbar ...................................................................................................................... 40

Hotkeys ............................................................................................................................. 41 Using CodeZilla................................................................................................................. 42 Project Storage............................................................................................................. 42 Project Folder Structure............................................................................................... 42 Properties.ini File ......................................................................................................... 42 Project Distribution System ......................................................................................... 43 Product Distributions ................................................................................................... 43 Library patch system................................................................................................ 43 Windows Installation................................................................................................ 44

Distribution Files .............................................................................................................. 47 Product Root Folder ..................................................................................................... 48 Product SOA Folder ...................................................................................................... 49 Product Primary Module Folder (ie. AP, etc.).............................................................. 50 Files not encrypted....................................................................................................... 50

SUMDIN ............................................................................................................................ 51 Installation Programs....................................................................................................... 53 Windows Setup Program ............................................................................................. 53 NSIS Installer Program ................................................................................................ 54 UNIX Installation Script ................................................................................................ 55 Installation Instructions ............................................................................................... 55 Windows Installation Instructions........................................................................... 55 UNIX CD-ROM Installation Instructions................................................................... 55 UNIX ZIP Installation ................................................................................................ 56

Known Limitations ........................................................................................................... 58 CodeZilla Installation ....................................................................................................... 59 Additional Software Required ..................................................................................... 59 Installation Overview.................................................................................................... 59



Release NotesRelease NotesRelease NotesRelease Notes

Release Notes for CodeZilla 4.4Release Notes for CodeZilla 4.4Release Notes for CodeZilla 4.4Release Notes for CodeZilla 4.4

Integrated With UltraEditIntegrated With UltraEditIntegrated With UltraEditIntegrated With UltraEdit

Version 4.4 has been modified to start the UltraEdit Editor on file selection if the UltraEdit editor is the default program used to open .pvc files. This functionality also means that any other editor you use to open .pvc files will also work.

Nomads Library 'Patch' InstallNomads Library 'Patch' InstallNomads Library 'Patch' InstallNomads Library 'Patch' Install

Nomad’s libraries can now be delivered as a partial file and patched on the customer's system, rather than shipping the entire nomads library. This feature enables the customer to retain Nomads library customizations.

Release Notes for CodeZilla 4.3Release Notes for CodeZilla 4.3Release Notes for CodeZilla 4.3Release Notes for CodeZilla 4.3

New Installer New Installer New Installer New Installer package integrationpackage integrationpackage integrationpackage integration

The 4.3 version adds new installer functionality based on the NSIS Installer package. The new package creates an 'InstallShield' type of package installer. This package can be customized per MD by using the provided publisher.nsh file and modifying it to reflect you're organization's logo and graphics

Full information on the NSIS Installer can be found at nsis.sourceforge.net

Programs Added to the Sage MenuPrograms Added to the Sage MenuPrograms Added to the Sage MenuPrograms Added to the Sage Menu

• Message Library Maintenance (4.1)

This allows MD's to create and install System Messages into a version 4.xx system.

CodeZilla Data Menu ChangesCodeZilla Data Menu ChangesCodeZilla Data Menu ChangesCodeZilla Data Menu Changes

• SY_Message Maintenance (4.1)

Release Notes for 4.10Release Notes for 4.10Release Notes for 4.10Release Notes for 4.10

The 4.10 version adds functionality required to develop MAS 90 4.10 enhancements.

Best Menu Changed to SageBest Menu Changed to SageBest Menu Changed to SageBest Menu Changed to Sage

This is to reflect Sage's name change.

Company Code Field added to Set MAS 90 Login DialogCompany Code Field added to Set MAS 90 Login DialogCompany Code Field added to Set MAS 90 Login DialogCompany Code Field added to Set MAS 90 Login Dialog

This dialog is required to be run before Sage developer programs are run. The Company Code field was added as it is now required when launching tasks from outside of the MAS 90 launcher. If you try to launch a Sage program without first running this dialog, you will encounter an error that says, "You

http://nsis.sourceforge.net/



need to set a default company in the MAS 90 4.0 Login properties."

Programs Added to tPrograms Added to tPrograms Added to tPrograms Added to the Sage Menuhe Sage Menuhe Sage Menuhe Sage Menu

These two programs have been added to the Sage menu:

• ProvideX Class Definitions (4.0)

• Context Table Maintenance (4.0)

CodeZilla Data Menu ChangesCodeZilla Data Menu ChangesCodeZilla Data Menu ChangesCodeZilla Data Menu Changes

New menu entries:

• ProvideX Class Definitions (4.0)

• Sy Context Maintenance (4.0)

• ODBC File Definition Maintenance

ODBC File Definition MaintenanceODBC File Definition MaintenanceODBC File Definition MaintenanceODBC File Definition Maintenance

This new feature represents a major technical achievement and a great added ability.

This adds the ability to extract ODBC dictionaries that have been added or changed out of the development system. SUMDI4 install will install these into the customer's ".DD" files, without affecting existing dictionaries or ".UDF" files. This means that it is longer necessary to include a "DDICTS" directory in a distribution (unless so desired). The user will no longer need to update ODBC from UDF’s after the install. This feature is backwards This feature is backwards This feature is backwards This feature is backwards ––––compatible to version 3.xx.compatible to version 3.xx.compatible to version 3.xx.compatible to version 3.xx.

Changes to ProvideX DDE/DDF MaintenanceChanges to ProvideX DDE/DDF MaintenanceChanges to ProvideX DDE/DDF MaintenanceChanges to ProvideX DDE/DDF Maintenance

A “Copy from Tag” button has been added to the ProvideX DDE/DDF Maintenance utility that allows the programmer to scan DDE/DDF records for the tag field entered for that enhancement and only copy those into the project.

xxxxxxxx_Enhancement File Automatically Updated_Enhancement File Automatically Updated_Enhancement File Automatically Updated_Enhancement File Automatically Updated

Previously, the programmer was prompted to update the existing CTL record when you change the Project Properties, or when you distribute the Project. This has been enhanced to also update the Release Date in the xx_Enhancement file for the new date.

Note that Installations Take LongerNote that Installations Take LongerNote that Installations Take LongerNote that Installations Take Longer

Sage has modified the SY_Installation program in version 4.10, specifically the Finalize() function, which causes installs to take 30-40 seconds longer to install. You’ll see this lag at the end of the installation when it is calling this Finalize function.

Release Notes for 4.0Release Notes for 4.0Release Notes for 4.0Release Notes for 4.0

This release has addition information in Distribution Files that is important to read before attempting to create a 4.0 enhancement.

Important: Important: Important: Important: In order for CodeZilla to operate on a 4.0 (or greater) system, two tasks must be present in the system:

MDWTMPMDWTMPMDWTMPMDWTMP

MDZTMPMDZTMPMDZTMPMDZTMP

These must be added through Task Maintenance in the Master Developer menu in MAS 90. These are temporary program files that CodeZilla creates on the fly while it operates. These must be added so



MAS 90 will recognize them and allow them to be executed.



New FeaturesNew FeaturesNew FeaturesNew Features

New Features for Version 4.New Features for Version 4.New Features for Version 4.New Features for Version 4.5555

• Patched Library Installation

New Features for Version 4.3New Features for Version 4.3New Features for Version 4.3New Features for Version 4.3

• New Integrated Installer Package by NSIS

• New Maintenance Programs added for Sage MAS 90 4.10 systems

New Features for Version 1.10 • Beginning with version 1.10, CodeZilla will have a version number that changes with each

revision.

• Ability to specify a certain INI file to be used when running the *IT editor.

• Password no longer mandatory in Project Properties.

• Removed SY0SIZ.SOA creation from MDZEFI Data/Create Data Files.

• Added About Dialog.

• Project Files and Folders with names that begin with "!" (bang) are not copied into the Distribution or Test System. This allows files and folders that are needed for development to be kept but not distributed.

• Added ability to add a two-letter module code to CodeZilla's "valid module list" for a Project.



OverviewOverviewOverviewOverview

CodeZilla improves Master Developer productivity and greatly reduces the amount of work required to create MAS90 enhancements. By creating a new IDE (Integrated Development Environment), the various development tools can be associated with corresponding data and program files.

The interface used is similar to Windows Explorer. Unlike Explorer, however, CodeZilla is programmed to "know" a great deal about MD projects and associated components. Projects are effectively organized and clearly presented. Each specialized Master Developer data file has an editor integrated to the environment. Double-clicking a data file automatically opens that file in the correct editor.

The interface is graphical and offers multiple options regarding how to start various tools. For

instance, it offers a choice of two types of program editors, which can be started using the icon, <ctrl><e>, Run/Editor or by double-clicking a program file. This is true of most files likely to be included in a project, including Nomads library (.LIB) files, text files, MD data files and ProvideX program files.

CodeZilla associates a Project Folder with a MAS90 Test System. Project files are stored in a Project Folder and are copied to and tested with an associated Test System. Synchronize Project automatically synchronizes the two systems. You can edit a file in either system and it will be automatically updated to the other system. This frees the programmer from forgetting which system has a more recent version of a particular file.

Modified MAS90 programs can be launched directly from CodeZilla by right-clicking on a program and selecting "run" from a pop-up menu.

CodeZilla has an advanced Distribution System that allows projects to be quickly packaged in ready-to-install distributions. The distributions are multiple-platform compatible. A single distribution can be installed on either Windows or UNIX systems.



Features and BenefitsFeatures and BenefitsFeatures and BenefitsFeatures and Benefits

The standard Master Developer Utilities were developed by Sage to allow their in-house staff and Master Developers to create installation diskettes for entire applications. However, few Master Developers create entire applications. M/D's are in the business of modifying existing applications. CodeZilla is written to help programmers rapidly create modifications to MAS90.

CodeZilla is a graphical integrated development environment (IDE). It organizes an MD development project and provides instant, integrated access to the various development tools and resources. For instance, for each module, all of the modified programs are displayed - double-clicking a program opens it in the ProvideX program editor.

Rapid Application DevelopmentRapid Application DevelopmentRapid Application DevelopmentRapid Application Development

CodeZilla is created to improve efficiency and reduce effort when developing MD projects. Every effort is made to reduce keystrokes and eliminate workarounds, etc.

CodeZilla points to a Project Folder and a Test System. It keeps your project organized in the Project Folder and allows instant tests (two mouse clicks) on the Test System. It is easy to select an unmodified program from the Test System and include it in the project. Any changes subsequently made to the program are retained in the project. The Test System can be synchronized with the project at the touch of a key.

The project is stored in an ordinary Windows folder. It is easy to pop a Windows Explorer opened to the Project Folder. You can then perform any operations required and do a Refresh in CodeZilla to show any changes. This allows access to Windows programs such as WinZip or an FTP client as required with the project still open.

When you open a project, CodeZilla automatically tries to reattach to the MAS90 Test System previously used with that project. A Test System link is stored for each programmer that has worked on a particular project. If the previously used MAS90 Test System still exists, its link is reestablished when the project is reopened.

CodeZilla remembers the last project worked on and automatically opens it when CodeZilla is launched.

If you are revisiting a previous project, it is very easy to associate a Test System. Set-up a MAS90 system with the correct modules. Open the Project and open Test System in CodeZilla. Then, just install the Project into the Test System. See:See:See:See: Install Project to Test System

A Great Support ToolA Great Support ToolA Great Support ToolA Great Support Tool

Because of the ease of opening a project with CodeZilla, it is a fantastic tool for support. When a call comes in, you are always just a few seconds away from the source code and every other aspect of the project.

Maintenance ProgramsMaintenance ProgramsMaintenance ProgramsMaintenance Programs

CodeZilla uses DSD's system of maintaining delta files. Just the differences that the project makes to the target system’s standard files are maintained. This increases compatibility with multiple enhancements and allows the user's menu modifications, etc. to remain. This also reduces problems when upgrading a product.

The following special maintenance programs are provided:

• CTL Control File Maintenance



• MNU Menu File Maintenance

• FIL File Format Maintenance

• FRM Form Maintenance

• EOP End of Period Maintenance

• DCT Data Dictionary Maintenance

• RUN Run File Maintenance

• CMP Dictionary Compile Maintenance

An <F5> Copy Line feature has been added to maintenance programs for line detail maintenance.

The distribution/installation system automatically includes these files with the project's distribution and compiles the data into the target system's various data files.

Distribution/Installation SystemDistribution/Installation SystemDistribution/Installation SystemDistribution/Installation System

CodeZilla creates easy-to-install product distributions with proven installation programs. A click of the mouse and a few seconds are all that are needed.

Installs to Both Windows and UNIXInstalls to Both Windows and UNIXInstalls to Both Windows and UNIXInstalls to Both Windows and UNIX

A single distribution, created on a Windows development system, will install to either a UNIX or a Windows MAS90 target system. Further, the system does not restrict the delivery vehicle. CD-ROMs, DVD-ROMs, Zip disks, self-extracting programs...it does not matter, except whether your end user's system can read that type of media. "Setup" is used to install to Windows systems and a Bourne shell script called "INSTALL" is used to install to UNIX systems.

You can e-mail a ZIP of the project to your customer, if you choose. For instance, DSD creates self-extracting programs that "explode" and automatically run Setup



Menu SelectionsMenu SelectionsMenu SelectionsMenu Selections

Most of the features of CodeZilla are accessible through its menu system. For the most often used functions, hotkeys are made available.

See also:See also:See also:See also: Toolbar, Hotkeys, and Using CodeZilla



File MenuFile MenuFile MenuFile Menu

Opening a Project FolderOpening a Project FolderOpening a Project FolderOpening a Project Folder

Menu:Menu:Menu:Menu: File | Open Project Folder

HotkeyHotkeyHotkeyHotkey: Control-O hotkeys

Opens a Project Folder. Use the controls to select an existing Project and then click OK to open it.

Recent Projects:Recent Projects:Recent Projects:Recent Projects: The forty most recently opened projects are listed. Click to select or double-click to open.

See Also:See Also:See Also:See Also: Close Project Folder

Close Project FolderClose Project FolderClose Project FolderClose Project Folder

Menu:Menu:Menu:Menu: File | Close Project Folder

Hotkey:Hotkey:Hotkey:Hotkey: Control-C hotkeys

Closes the open Project Folder.

The last used Test System Folder will be stored in the Project's Properties.ini file. The next time that the Project is opened, CodeZilla will attempt to reattach to the same Test System, if it still exists. Note: Note: Note: Note: The Test System is stored and retrieved by programmer login name.

See Also:See Also:See Also:See Also: Open Project Folder



Select Test SystemSelect Test SystemSelect Test SystemSelect Test System

Menu:Menu:Menu:Menu: File | Select Test System

Opens the Select Test System dialog. Allows you to attach a MAS90 installation as a Test System to a Project.

CodeZilla uses the selected Test System to test the Project's programs. It also uses the Test System to run ProvideX and MAS90 programming tools. Note:Note:Note:Note: The Test System is not used to run the IT editor or Nomads, if the Tool System Path option is set.

Important: Important: Important: Important: CodeZilla has not been tested using Test Systems located on network volumes. DSD recommends using a Test System located on the development machine's local drive. If and when successful experience is gained using Test Systems on network volumes, this restriction will be removed. (Feedback appreciated.)

Install Project to Test SystemInstall Project to Test SystemInstall Project to Test SystemInstall Project to Test System

Menu:Menu:Menu:Menu: File | Install Project to Test System

Installs the open project to the selected MAS90 Test System. All of the project's files are copied from the Project Folder to the Test System. The MD data files are compiled into MAS90 using a ProvideX program. Before proceeding with the process, the following prompt will appear:

If YesYesYesYes then the project is installed and MAS90 menus are updated.

If NoNoNoNo then the project is installed to the Test System without updating menus.

CancelCancelCancelCancel cancels the process.

Note: Note: Note: Note: Files and folders in the Project Folder that have filenames that begin with "!" (bang) will not be installed to the Test System. This allows the programmer to keep files in the Project folder that should not be installed with the Project.

After the Project is installed to the Test System, Synchronize Project and Test System will keep the two sets of files synchronized.

Note:Note:Note:Note: The Project Folder and the Test System are not synchronized not synchronized not synchronized not synchronized before installing the Project to the Test System.



Synchronize Project and Test SystemSynchronize Project and Test SystemSynchronize Project and Test SystemSynchronize Project and Test System

Menu: Menu: Menu: Menu: File | Synchronize Project and Test System

Hotkey:Hotkey:Hotkey:Hotkey: Control-Y hotkeys

Synchronizes the Project folder with the Test System folder. Inspects each file in the Project Folder and compares it to the file of the same name in the Test System. The newer of the two files replaces the older.

If a project file is not found on the Test System, it is copied there. MD data files are ignored.

If you modify a file in the Test System and then decide that you do not wish to keep the changes, you can reinstall the Project. If you synchronize, the most recent file will be copied to the other folder. See See See See Install Project to Test System alternately, you could switch to Act On the Project Folder and make a change to the same file, in which case, Synchronizing will copy it over the one on the Test System.

Note:Note:Note:Note: If Nomads is open when Synchronize is run, the most recently opened Library file is probably still open and locked, in which case it will notwill notwill notwill not be copied. If you want to keep Nomads open while testing a certain panel, you can set CodeZilla to act on the Test SystemTest SystemTest SystemTest System. Then, make sure to Sync after you close Nomads so the project is updated.

See Also:See Also:See Also:See Also: Install Project to Test System

Distribute ProjectDistribute ProjectDistribute ProjectDistribute Project

Menu:Menu:Menu:Menu: File | Distribute Project

Readies the Project for distribution. Compiles the project from the Project Folder to an Image Distribution Folder, creating an installation image that is ready for installation to a MAS90 system.

• The project files are copied to a distribution folder.

• The programs are then password protected.

• Additional files that are needed to install the project to a MAS90 system are copied to the distribution folder.

The Project is then ready to be distributed. It can be copied to any suitable media.

Note: Note: Note: Note: Files and folders that have filenames that begin with "!" (bang) in the Project Folder will not be distributed. This allows the programmer to keep files in the Project Folder that should not be distributed with the Project.

Advantages of the CodeZilla Installation System:

• Can be installed to all known current MAS90 systems.

• Can be distributed on CD-ROM, DVD-ROM, Zip or other suitable media.

• Can be transformed into a self-extracting ZIP for convenient e-mail distribution.

• Can be installed to a UNIX system.

• UNIX distribution can install from ZIP or CD-ROM.



Check Project Properties Release Date vs. System DateCheck Project Properties Release Date vs. System DateCheck Project Properties Release Date vs. System DateCheck Project Properties Release Date vs. System Date

Before the Distribute Project Dialog appears, CodeZilla compares the Project Properties Release Date against the System Date. If they differ, the program will ask whether to update Project Properties Project Release Date.

YesYesYesYes updates the Project Properties Project Release Date to the System Date. NoNoNoNo does not. CancelCancelCancelCancel cancels the entire process.

Check Check Check Check Project Properties vs. CTL DataProject Properties vs. CTL DataProject Properties vs. CTL DataProject Properties vs. CTL Data

After the above check, CodeZilla compares the Project Properties data against the same data in the CTL file. If they differ, the program will ask whether to update the CTL record.

YesYesYesYes updates the CTL file Release Date to the Project Properties Release Date. NoNoNoNo does not.

Distribute Project Distribute Project Distribute Project Distribute Project DialogDialogDialogDialog

After the above check, the Distribute Project dialog appears.

PasswPasswPasswPassword:ord:ord:ord: (Optional) if present, this password will be used to encrypt the ProvideX programs included in the distribution. If no password is entered, CodeZilla will ask whether to proceed when the OK button is pressed. Password is initialized from Password in the Destination tab in Project Properties. SeeSeeSeeSee Files not Encrypted for a list of files that are not encrypted in the distribution.

Image DestinImage DestinImage DestinImage Destination Folder:ation Folder:ation Folder:ation Folder: (Required) this is where the Distribution Image will be written. The Browse button can be used open a dialog that may be used to select the Image Destination Folder. This folder must exist; CodeZilla will not create the folder. Image Destination Folder is initialized from Output Folder in the Destination tab in Project Properties.

Zip/Exe Filename:Zip/Exe Filename:Zip/Exe Filename:Zip/Exe Filename: (optional) this is the name of the package file. If this is left blank, then the default "setup.exe" will be created instead.



Add File to ProjectAdd File to ProjectAdd File to ProjectAdd File to Project

Menu:Menu:Menu:Menu: File | Add File to Project

Hotkey:Hotkey:Hotkey:Hotkey: Control-A

Add File to Project can be used to add a file to the project.

By default files are shown in the project's Test System, in the folder selected in CodeZilla's main window. The destination folder within the project is the default selected folder in the CodeZilla main window.

After selecting a file to add to the project, you can select the Project Folder in which to copy the selected file. The "As Filename" field allows you to specify what to call the file within the project. Note that the "As Filename" field is not used to select a file to add to the project, but to specify the name within the project.

Run SelectedRun SelectedRun SelectedRun Selected

Menu:Menu:Menu:Menu: File | Run Selected

Hotkey:Hotkey:Hotkey:Hotkey: Control-R

This will first synchronize the Project and Test System and then run the currently selected ProvideX program in the Test system.

Project PropertiesProject PropertiesProject PropertiesProject Properties

Menu:Menu:Menu:Menu: File | Project Properties

HotkeHotkeHotkeHotkey:y:y:y: Control-P

The Project Properties values are stored in the file Properties.ini in the Project's "root" folder. When the OK button is selected, the Release Date and Part Number are compared to the same fields in the CTL record. If they differ, the program will ask whether to update the CTL record. See See See See Update Prompt



Main Tab FieldsMain Tab FieldsMain Tab FieldsMain Tab Fields

Name:Name:Name:Name: (Required) used when creating CTL records. Maximum length of 31 characters.

3333----Letter Code:Letter Code:Letter Code:Letter Code: (Required) Used for various functions throughout the project, including filename extensions on the project's data files. The program automatically converts the text to uppercase and requires a length of 3-characters. This data is used for the 3-letter filename extensions when creating MD data files. If this field is changed, CodeZilla responds with a warning to change data filenames and CTL record keys.

Version:Version:Version:Version: (Required) Appears in the Project Distribution.

Release Date:Release Date:Release Date:Release Date: (Required) Appears in the Project Distribution. When "OK" is selected, this value is compared against date in the "l" (lowercase-L) Level records in the project's CTL Control file. If they do not match, the program will ask whether to update the records in the CTL file.

Dates can be entered in any of four formats: mm/dd/yymm/dd/yymm/dd/yymm/dd/yy, mm/dd/yyyymm/dd/yyyymm/dd/yyyymm/dd/yyyy, mmddyy or mmddyyyymmddyy or mmddyyyymmddyy or mmddyyyymmddyy or mmddyyyy (where mmmmmmmm is month, dddddddd is day and yyyyyyyy or yyyyyyyyyyyyyyyy is year).

Today button:Today button:Today button:Today button: Sets the Release Date to the System Date.

Part Number:Part Number:Part Number:Part Number: (Optional) Appears in the project's CTL records.

L/M Version:L/M Version:L/M Version:L/M Version: Enter the version of Library Master that this Project targets. This is needed so CodeZilla will use the correct tools when open data files and possibly to use different included programs when creating a Distribution.

Addl Module:Addl Module:Addl Module:Addl Module: (Optional) If your Project targets a non-standard MAS90 module, enter the two-letter, uppercase code for that module. Else, leave blank. This data is used by CodeZilla when determining whether a module included in the Project is allowed.

Primary:Primary:Primary:Primary: (Required) The Primary Modified MAS90 module. Required. Must be a valid MAS90 module.

All:All:All:All: (Required) A list of all modified MAS90 modules. Required. Must be valid MAS90 modules. Includes the Primary Modified MAS90 module.

Patch InstallPatch InstallPatch InstallPatch Install: Checking this box will create a nomads library patch install file that the installation program will run to patch changes from the development library into the system library. Checking this box will determine the difference between the development library (test system) and the control library (Control System).

Distribution Tab FieldsDistribution Tab FieldsDistribution Tab FieldsDistribution Tab Fields

Password:Password:Password:Password: Used when encrypting ProvideX programs for the Project Distribution.

Output Folder:Output Folder:Output Folder:Output Folder: The path where the distribution will be written. This is the image that is distributed to the Customer. For instance, you could copy this image to a CD-ROM and install the project to the target system from the CD-ROM.

Browse button: Browse button: Browse button: Browse button: Use this button to select an Output Folder with a browse folders dialog.



Update PromptUpdate PromptUpdate PromptUpdate Prompt

When the OK button is selected, the Release Date and Part Number are compared to the same fields in the CTL record. If they differ, the program will ask whether to update the CTL record.

ExitExitExitExit

Menu:Menu:Menu:Menu: File | Exit

Exits CodeZilla.



Utilities MenuUtilities MenuUtilities MenuUtilities Menu

Delete Application

Menu:Menu:Menu:Menu: Utilities | Delete Application

Deletes an application from the MAS90 Test System.

This wipes-out a MAS90 application. It can be used to remove a modified MAS90 application in preparation to installing a new modification.

It is important to remove a modified application's data before installing unmodified source due to the potential for data "corruption". For instance, let's say that you've just added a new data file to A/P for an enhancement, and you've added two new fields to AP1. Merely reinstalling unmodified source code over your modifications does not remove your changes. The new file and the two new fields will still be there after you reload unmodified source code, and it could cause problems.

Likewise, reinstalling new source code does not erase programs you've added, Data dictionary files you've created, etc. That's what this utility is for.

When you've selected the application to delete, you can specify what to erase. For instance, you can erase programs and SY0FIL.SOA records, but leave the Forms and EOP information intact.



Data Menu These are the Master Developer data file maintenance programs. The files they maintain are included with the Distribution of the Project. This data is compiled into the target MAS90 system during the Installation Process (the first time MAS90 is run after the project has been copied into the MAS90 system, a program called SUMDIN is called, which does this work)..

CTL (Control) File MaintenanceCTL (Control) File MaintenanceCTL (Control) File MaintenanceCTL (Control) File Maintenance

Menu:Menu:Menu:Menu: Data | CTL Control File

The project's CTL file contains records that are transferred into the SY0CTL.SOA file of the end-user's system, during installation. This file should contain a "level" record for each modified application (including the Base Application), as well as any other appropriate control records. It is necessary to create level records for all modified applications (not just the Base Application) so that if the end-user attempts to re-install any of those applications, or upgrade them, the warning message will be displayed by SUINST, informing the end-user that the application has been modified.

In general, you should avoid including level records having an "lX/Y" (note that the first character in quotes is a lower-case letter L) format. Those records are written to SY0CTL.SOA when a standard MAS90 application module is installed, and we don't want to overwrite those records with our enhancement level records.

If the Release Date or Part Number is changed in Project Properties, CodeZilla asks whether to update the project's "l" (lowercase "L") records in the project's CTL file.

These records are compiled into the MAS90 system's "SY0CTL.SOA" file by SUMDIN during the distribution installation process. SeeSeeSeeSee Distribution Files



Enhancement Level Record FormatEnhancement Level Record FormatEnhancement Level Record FormatEnhancement Level Record Format

Field DescriptionField DescriptionField DescriptionField Description TypeTypeTypeType StartStartStartStart LengthLengthLengthLength Key?Key?Key?Key?

"l" (lower-case "L") STR 1 1 Yes

Application Code (i.e. "A/P) STR 2 3 Yes

"_" (underscore character) STR 5 1 Yes

Enhancement Code STR 6 3 Yes

Part Number STR 9 10

Description STR 19 31 Level Number STR 50 10

Release Date STR 60 6 Extended File Names? Y/N 66 1

CTL File Maintenance WindowCTL File Maintenance WindowCTL File Maintenance WindowCTL File Maintenance Window

M/D Control File M/D Control File M/D Control File M/D Control File Maintenance Program Maintenance Program Maintenance Program Maintenance Program Fields Fields Fields Fields

When there is no existing FIL file in the Project, the following prompt will be displayed:

THE 'GL0CTL.MUL' FILE DOES THE 'GL0CTL.MUL' FILE DOES THE 'GL0CTL.MUL' FILE DOES THE 'GL0CTL.MUL' FILE DOES NOT EXIST.NOT EXIST.NOT EXIST.NOT EXIST.

DO YOU WISH TO CREATE IT? DO YOU WISH TO CREATE IT? DO YOU WISH TO CREATE IT? DO YOU WISH TO CREATE IT? (Yes, No, END): [Yes(Yes, No, END): [Yes(Yes, No, END): [Yes(Yes, No, END): [Yes ] ] ] ]

If Y is entered, the control file for the enhancement will be created in the proper subdirectory, and "level" records will be automatically created for the Base Application and all modified applications. The data used comes from the Project's Properties.

Up to 99 records (lines) may be entered into this file. There are only two fields, and they are:

KEY FIELD: KEY FIELD: KEY FIELD: KEY FIELD: This field may be one to nine characters in length. Please note that all trailing spaces will be stripped from the key field. In other words, if a key field is entered as "1234", it will be four characters long, not nine.

DATA:DATA:DATA:DATA: This field may be up to 61 characters in length. When the record is written to the file, the Key Field is automatically appended to the data field to form the data record.

At the bottom screen prompt, the user may Print a control file listing, or DELETE the enhancement's control file in its entirety.

DD1/DD2 Roswell Data Dictionary MaintenanceDD1/DD2 Roswell Data Dictionary MaintenanceDD1/DD2 Roswell Data Dictionary MaintenanceDD1/DD2 Roswell Data Dictionary Maintenance

Menu:Menu:Menu:Menu: Data | DD1/DD2 SQL Data Dictionary



This utility allows the developer to copy records to and from the Project and the Test System. Actual record maintenance must be done in the Test System and the records then copied to the Project for Distribution.

Definitions are maintained in DD1 using the Sage utility Roswell Data Dictionary Maintenance. That utility is then used to compile the DD1 data into DD2. DSD's utility is then used to copy selected records into the Project, for inclusion distribution or later modification.

DD2 records are compiled into the MAS90 system's "SY0DD2.SOA" file by SUMDIN during the distribution installation process. SSSSeeeeeeee Distribution Files

This maintenance screen behaves the same way that the standard Generic Form Maintenance (MDZMDA) program does.

DCT Data Dictionary DCT Data Dictionary DCT Data Dictionary DCT Data Dictionary ---- Pre Pre Pre Pre----3.603.603.603.60

Menu:Menu:Menu:Menu: Data | DCT Data Dictionary

Note: ThisNote: ThisNote: ThisNote: This is for pre is for pre is for pre is for pre----3.60 3.60 3.60 3.60 versions of MAS 90 only.versions of MAS 90 only.versions of MAS 90 only.versions of MAS 90 only.

DCT Data Dictionary Maintenance allows the maintaining of Data Dictionary files for an enhancement.

This maintenance screen behaves the same way that the standard Data Dictionary Maintenance (MDZDDA) program works, except that you enter the Enhancement Code first. Installation does not wipe out the entire Data Dictionary; you need only include the new or modified Data Dictionary files in your enhancement's DCT file.



You can combine more than one application's Data Dictionary files in the enhancement's DCT file.

When selected in a Project in which there is no existing DCT file, the following prompt will be displayed:

THE 'GL0DCT.MUL' FILE DOES NOT EXIST.THE 'GL0DCT.MUL' FILE DOES NOT EXIST.THE 'GL0DCT.MUL' FILE DOES NOT EXIST.THE 'GL0DCT.MUL' FILE DOES NOT EXIST. DO YOU WISH TO CREATE IT? (Yes, No, END): [Yes ]DO YOU WISH TO CREATE IT? (Yes, No, END): [Yes ]DO YOU WISH TO CREATE IT? (Yes, No, END): [Yes ]DO YOU WISH TO CREATE IT? (Yes, No, END): [Yes ]

If Y is entered, the data dictionary file for the enhancement will be created in the proper subdirectory.

All other screen fields and functions are identical to the standard MDZDDA program, with the exception of the <F3> (Delete) and <F5> (Copy) features. At the FILE NAME field, the screen prompt has been modified as follows:

ENTER FILE NAME (F1=help, F2=list, F3=delete file)ENTER FILE NAME (F1=help, F2=list, F3=delete file)ENTER FILE NAME (F1=help, F2=list, F3=delete file)ENTER FILE NAME (F1=help, F2=list, F3=delete file) (F4=print, F5=copy from/to sy0dct, F10=next recd, ESC=end)(F4=print, F5=copy from/to sy0dct, F10=next recd, ESC=end)(F4=print, F5=copy from/to sy0dct, F10=next recd, ESC=end)(F4=print, F5=copy from/to sy0dct, F10=next recd, ESC=end)

To delete the enhancement's DCT file in its entirety, press the <F3> key.

To copy data dictionary files back and forth between the enhancement's DCT file, and the SY0DCT.SOA system file, press the <F5> key. The following will be displayed:

COPY FROM OR TO SY0DCT? (F/T): COPY FROM OR TO SY0DCT? (F/T): COPY FROM OR TO SY0DCT? (F/T): COPY FROM OR TO SY0DCT? (F/T): Enter F to copy one or more dictionary files from SY0DCT.SOA to the enhancement file. Enter T to copy one or more dictionary files from the enhancement file To SY0DCT.SOA.

TAG OUTBOUND RECORDS? (Y/N): TAG OUTBOUND RECORDS? (Y/N): TAG OUTBOUND RECORDS? (Y/N): TAG OUTBOUND RECORDS? (Y/N): Enter Y if you want to insert a "#" as the first character of the File Description field for identification purposes.

DICTIONADICTIONADICTIONADICTIONARY TO BE COPIED: RY TO BE COPIED: RY TO BE COPIED: RY TO BE COPIED: Enter the dictionary file to be copied to or from SY0DCT.SOA. You may use a "*" wildcard for the copy (i.e. AP* or AR*).

MNU (Menu) File MaintenanceMNU (Menu) File MaintenanceMNU (Menu) File MaintenanceMNU (Menu) File Maintenance

Menu:Menu:Menu:Menu: Data | MNU Menu File

The MDUT format for the MNU file has one record for each menu bar selection, and one record for each menu selection. These records are processed the installation program, and menu selections for your enhancement are added to existing menus instead of replacing menus in their entirety. This allows the end-user to save important changes that they've made to their own menus, and it allows two separate enhancements to add menu selections to the same menu without overwriting each



other.

These records are compiled into the MAS90 system's "SY0MNU.SOA" file by SUMDMN (which is called by SUMDIN) during the distribution installation process. SeeSeeSeeSee Distribution Files

Note: Note: Note: Note: MNU files maintained by the MDUT programs are not similar to the format of the SY0MNU.SOA system file. In the SY0MNU.SOA file, there is one record for each entire menu.

Menu Record FormatMenu Record FormatMenu Record FormatMenu Record Format

Field DescriptionField DescriptionField DescriptionField Description TypeTypeTypeType StartStartStartStart LengthLengthLengthLength

Sequence Number STR 1 3

Line Type (Add/Menu/Bar/Delete) UPPR 4 1

Application Code UPPR 5 2

Menu Code UPPR 7 3

Selection Number ZERO 10 2

Program Name UPPR 12 6

Description STR 18 34

Menu Bar Description STR 52 14

AAAA Addition of a menu item

DDDD Delete a menu entry

BBBB Rename a menu bar



MNU File Maintenance WindowMNU File Maintenance WindowMNU File Maintenance WindowMNU File Maintenance Window

M/D Menu File M/D Menu File M/D Menu File M/D Menu File Maintenance Maintenance Maintenance Maintenance Program FieldsProgram FieldsProgram FieldsProgram Fields

There may be up to 299 records (lines) in this file.

When there is not an existing MNU file, the following prompt will be displayed:

THE 'GL0MNU.MUL' THE 'GL0MNU.MUL' THE 'GL0MNU.MUL' THE 'GL0MNU.MUL' FILE DOES NOT FILE DOES NOT FILE DOES NOT FILE DOES NOT EXIST.EXIST.EXIST.EXIST. DO YOU WISH TO DO YOU WISH TO DO YOU WISH TO DO YOU WISH TO CREATE IT? (Yes, No, CREATE IT? (Yes, No, CREATE IT? (Yes, No, CREATE IT? (Yes, No, END): [YesEND): [YesEND): [YesEND): [Yes ] ] ] ]

LIN TYP: LIN TYP: LIN TYP: LIN TYP: Enter the line type of this entry. You have four choices:

MMMM

Addition of a new menu

APP CD: APP CD: APP CD: APP CD: Enter the Application Code for this entry. Use L/M or

SYS for Library Master.

MNU CD: MNU CD: MNU CD: MNU CD: Enter the Menu Code for this menu entry. You may want to use SUMNUA to determine what the code is for the menu item you are adding. If you are adding a new menu, you can create a new menu code.

SEL NO: SEL NO: SEL NO: SEL NO: Enter the Selection Number of the menu. If it is a new menu that is added, then this field will be the position on the Application Menu Bar. If it is a menu item that is added to an existing menu, then this field is the position on the menu for the menu item. You may leave this field blank, or enter '00', to find the next available position in which to add this entry.

PROG NAME: PROG NAME: PROG NAME: PROG NAME: Enter the six-character Program Name for the menu item being added or deleted. This field is skipped for 'M' or 'B' Line Types.

DESCRIPTION: DESCRIPTION: DESCRIPTION: DESCRIPTION: Enter the 30-character Menu Item Description that appears as the menu.

Menu BarMenu BarMenu BarMenu Bar

DESCRIPTION: DESCRIPTION: DESCRIPTION: DESCRIPTION: Enter the 14-character Menu Bar Description. This field allows entry for 'M' or 'B' Line Types. This is the Description that is displayed onto the Application Menu Bar.



At the bottom screen prompt, the user may Print a file listing, DELETE the enhancement's menu file in its entirety, or Copy records from SY0MNU.SOA.

At the bottom screen prompt, the user may PrintPrintPrintPrint a file listing, DELETEDELETEDELETEDELETE the enhancement's menu file in its entirety, or CopyCopyCopyCopy records from SY0MNU.SOASY0MNU.SOASY0MNU.SOASY0MNU.SOA.

When CopyCopyCopyCopy is selected, the following is displayed:

This same Copy feature is available in many of the

maintenance programs. Copy allows the user to pull records from the main system file (in this case SY0MNU.SOA) into the enhancement file. This process is best performed once all programming has been completed, and it's time to create final documentation and an installation diskette.

The Menu Maintenance Copy fields are described below:

APPLICATION: APPLICATION: APPLICATION: APPLICATION: Enter the application module that you wish to copy a menu from. Please note that the Menu Copy process will copy an entire menu, such as the A/P Reports Menu, or the G/L Budget Menu. You must then use the edit screen to remove unwanted lines, or make other changes.

Once the Application Code has been entered, all menu bar selections for the application (except DATE and END) will be displayed at the right.

MENU CODE: MENU CODE: MENU CODE: MENU CODE: Select the desired Menu Code. All menu selections for that Menu will be pulled into the enhancement's menu file.

Note:Note:Note:Note: The Copy feature can be used whether or not there are existing records in the MNU file. New records copied into the file will be added right after the last current record.

FRM Form File FRM Form File FRM Form File FRM Form File ---- Pre Pre Pre Pre----3.603.603.603.60

Menu:Menu:Menu:Menu: Data | FRM Form File

Note: This is for preNote: This is for preNote: This is for preNote: This is for pre----3.60 3.60 3.60 3.60 versions of MAS 90 only.versions of MAS 90 only.versions of MAS 90 only.versions of MAS 90 only.

M/D Generic Form Maintenance, accessed as option 6 on the new Enhancement Menu, allows the maintaining of Generic Forms for an enhancement.

These records are compiled into



the MAS90 system's "SY0FRM.SOA" file by SUMDIN during the distribution installation process. SeeSeeSeeSee Distribution Files

This maintenance screen behaves the same way that the standard Generic Form Maintenance (MDZMDA) program works.

When there is no existing FRM file, the following prompt will be displayed:

THE 'GL0FRM.MUL' FILE DOES NOT EXIST.THE 'GL0FRM.MUL' FILE DOES NOT EXIST.THE 'GL0FRM.MUL' FILE DOES NOT EXIST.THE 'GL0FRM.MUL' FILE DOES NOT EXIST. DO YOU WISH TO CREATE IT? (Yes, No, END): [Yes ]DO YOU WISH TO CREATE IT? (Yes, No, END): [Yes ]DO YOU WISH TO CREATE IT? (Yes, No, END): [Yes ]DO YOU WISH TO CREATE IT? (Yes, No, END): [Yes ]

If YYYY is entered, the form file for the enhancement will be created in the proper subdirectory.

All other screen fields and functions are identical to the standard MDZMDA program, with the exception of the <F3> (Delete)<F3> (Delete)<F3> (Delete)<F3> (Delete) and <F5> (Copy) <F5> (Copy) <F5> (Copy) <F5> (Copy) features. At the FORM NAME field, the screen prompt has been modified as follows:

ENTER FORM NAME (F2=list, F3=delete file, F4=print)ENTER FORM NAME (F2=list, F3=delete file, F4=print)ENTER FORM NAME (F2=list, F3=delete file, F4=print)ENTER FORM NAME (F2=list, F3=delete file, F4=print) (F5=copy from/to sy0frm, F10=next recd, ESC=end)(F5=copy from/to sy0frm, F10=next recd, ESC=end)(F5=copy from/to sy0frm, F10=next recd, ESC=end)(F5=copy from/to sy0frm, F10=next recd, ESC=end)

To delete the enhancement's FRM file in its entirety, press the <F3><F3><F3><F3> key.

To copy record layouts back and forth between the enhancement's FRM file, and the SY0FRM.SOA system file, press the <F5> <F5> <F5> <F5> key. The following will be displayed:

COPY FROM OR TO SY0FRM? (F/T): COPY FROM OR TO SY0FRM? (F/T): COPY FROM OR TO SY0FRM? (F/T): COPY FROM OR TO SY0FRM? (F/T): Enter F to copy one or more forms FROM SY0FRM.SOA to the enhancement file. Enter T to copy one or more forms from the enhancement file to SY0FRM.SOA.

FORM NAME TO BE COPIED: FORM NAME TO BE COPIED: FORM NAME TO BE COPIED: FORM NAME TO BE COPIED: Enter the generic form to be copied to/from SY0FRM.SOA.



EOP End of PeriodEOP End of PeriodEOP End of PeriodEOP End of Period

Menu:Menu:Menu:Menu: Data | EOP End of Period

This maintenance screen behaves the same way that the standard Period End Option Maintenance (MDZMGA) program works.

These records are compiled into the MAS90 system's "SY0EOP.SOA" file by SUMDIN during the distribution installation process. SeeSeeSeeSee Distribution Files

When no existing EOP file, the following prompt will be displayed:

THE 'GL0EOP.MUL' FILE DOES NOT EXIST.THE 'GL0EOP.MUL' FILE DOES NOT EXIST.THE 'GL0EOP.MUL' FILE DOES NOT EXIST.THE 'GL0EOP.MUL' FILE DOES NOT EXIST. DO YOU WISH TO CREATE IT? (Yes, No, END): [Yes ]DO YOU WISH TO CREATE IT? (Yes, No, END): [Yes ]DO YOU WISH TO CREATE IT? (Yes, No, END): [Yes ]DO YOU WISH TO CREATE IT? (Yes, No, END): [Yes ]

If YYYY is entered, the EOP options file for the enhancement will be created in the proper subdirectory. All other screen fields and functions are identical to the standard MDZMGA program, with the exception of the <F3> (Delete) <F3> (Delete) <F3> (Delete) <F3> (Delete) and <F5> (Copy) <F5> (Copy) <F5> (Copy) <F5> (Copy) features. At the APPLICATION CODE field, the screen prompt has been modified as follows:

ENTER APPLICATION CODE (F2=lisENTER APPLICATION CODE (F2=lisENTER APPLICATION CODE (F2=lisENTER APPLICATION CODE (F2=list, F3=delete file, F4=print)t, F3=delete file, F4=print)t, F3=delete file, F4=print)t, F3=delete file, F4=print) (F5=copy from/to sy0eop, F10=next recd, ESC=end)(F5=copy from/to sy0eop, F10=next recd, ESC=end)(F5=copy from/to sy0eop, F10=next recd, ESC=end)(F5=copy from/to sy0eop, F10=next recd, ESC=end)

To delete the enhancement's EOP file in its entirety, press the <F3> key.

To copy the option record from or to the SY0EOP.SOA system file, press the <F5> key. The following will be displayed:

COPY FROM OR TO SY0EOP? (F/T): COPY FROM OR TO SY0EOP? (F/T): COPY FROM OR TO SY0EOP? (F/T): COPY FROM OR TO SY0EOP? (F/T): Enter F to copy the options record FROM SY0EOP.SOA to the enhancement file. Enter T to copy the options record from the enhancement file TO SY0EOP.SOA.

APPLICATION TO BE COPIED: APPLICATION TO BE COPIED: APPLICATION TO BE COPIED: APPLICATION TO BE COPIED: Enter the application code to be copied to/from SY0EOP.SOA.



RUN Run FileRUN Run FileRUN Run FileRUN Run File

Menu:Menu:Menu:Menu: Data | RUN Run File

The enhancement Run File mm0RUN.eee (where mm represents the module and eee represents the enhancement code) contains a list of programs which you would like to be called by the MAS90 program during diskette data file installation. Any such program is called after the enhancement's files have been copied from the diskette into the Base Application subdirectory on the hard drive, and before any of those installation files are accessed by SUMDIN.

RUN Record FormatRUN Record FormatRUN Record FormatRUN Record Format

Field DescriptionField DescriptionField DescriptionField Description TypeTypeTypeType StartStartStartStart LengthLengthLengthLength Key?Key?Key?Key?

Sequence Number (i.e. "01", etc.) STR 1 2 Yes

MAS90 Dir Containing Called Program STR 3 12 Called Program Name STR 15 12

ScreenshotScreenshotScreenshotScreenshot

When an Enhancement code is entered for which there is no existing RUN file, the following prompt will be displayed:

THE 'GL0RUN.MUL' THE 'GL0RUN.MUL' THE 'GL0RUN.MUL' THE 'GL0RUN.MUL' FILE DOES NOT FILE DOES NOT FILE DOES NOT FILE DOES NOT

EXIST.EXIST.EXIST.EXIST. DO YOU WISH TO DO YOU WISH TO DO YOU WISH TO DO YOU WISH TO

CREATE IT? (Yes, No, CREATE IT? (Yes, No, CREATE IT? (Yes, No, CREATE IT? (Yes, No, END): [Yes ]END): [Yes ]END): [Yes ]END): [Yes ]

If Y is entered, the run file for the enhancement will be created in the proper subdirectory. Up to 99 records (lines) may be entered into this file. There are only two fields, and they are:

PROGRAM NAME: PROGRAM NAME: PROGRAM NAME: PROGRAM NAME: This field may be one to 12 characters in length, and it may consist of upper and lower case characters. Only valid filename characters should be entered.

SUBDIRECTORY: SUBDIRECTORY: SUBDIRECTORY: SUBDIRECTORY: This field may be up to 12 characters in length. This is the subdirectory that will be located by SYPATH, in order to find your program for execution.

At the bottom screen prompt, the user may Print a file listing, or DELETE the enhancement's run file in its entirety.

CMP Dictionary CompileCMP Dictionary CompileCMP Dictionary CompileCMP Dictionary Compile

Menu:Menu:Menu:Menu: Data | CMP Dictionary Compile

The enhancement Dictionary Compile file mm0CMP.eee (where mm represents the module and eee



represents the Enhancement Code) contains only those Data Dictionary files which have been added or modified as a result of your enhancement. New files (records representing files) will be added to the SY0DCT.SOA file, and modified files will replace existing SY0DCT.SOA records.

CMPCMPCMPCMP Record Format Record Format Record Format Record Format

Field DescriptionField DescriptionField DescriptionField Description TypeTypeTypeType StartStartStartStart LenLenLenLengthgthgthgth Key?Key?Key?Key?

Sequence Number (i.e. "01", etc.) STR 1 2 Yes

Application Code to Compile STR 3 2

ScreenshotScreenshotScreenshotScreenshot

When selected in a Project for which there is no existing CMP file, the following prompt will be displayed:

THE 'GL0CMP.MUL' FILE THE 'GL0CMP.MUL' FILE THE 'GL0CMP.MUL' FILE THE 'GL0CMP.MUL' FILE DOES NOT EXIST.DOES NOT EXIST.DOES NOT EXIST.DOES NOT EXIST. DDDDO YOU WISH TO O YOU WISH TO O YOU WISH TO O YOU WISH TO

CREATE IT? (Yes, No, CREATE IT? (Yes, No, CREATE IT? (Yes, No, CREATE IT? (Yes, No, END): [Yes ]END): [Yes ]END): [Yes ]END): [Yes ]

If Y is entered, the compile file for the enhancement will be created in the proper subdirectory.

Up to 99 records (lines) may be entered into this file. There is only one field:

APP CODE: APP CODE: APP CODE: APP CODE: This is the application code of the Data dictionary to compile.

At the bottom screen prompt, the user may Print a file listing, or DELETE the enhancement's compile file in its entirety.

FIL (File/Record) File FIL (File/Record) File FIL (File/Record) File FIL (File/Record) File Maintenance Maintenance Maintenance Maintenance ---- Pre 3.60 Pre 3.60 Pre 3.60 Pre 3.60

Menu:Menu:Menu:Menu: Data | FIL File Format

Note: This iNote: This iNote: This iNote: This is for pres for pres for pres for pre----3.60 3.60 3.60 3.60 versions of MAS 90 only.versions of MAS 90 only.versions of MAS 90 only.versions of MAS 90 only.

Overall, this maintenance screen behaves the same way the standard File/Record Format Maintenance (MDZMCA) works, except that you enter the Enhancement Code first.

These records are compiled into



the MAS90 system's "SY0FIL.SOA" file by SUMDIN during the distribution installation process. SeeSeeSeeSee Distribution Files

When this program is run in a Project for which there is no existing FIL file, the following prompt will be displayed:

THE 'GL0FIL.MUL' FILE DOES NOT EXIST.THE 'GL0FIL.MUL' FILE DOES NOT EXIST.THE 'GL0FIL.MUL' FILE DOES NOT EXIST.THE 'GL0FIL.MUL' FILE DOES NOT EXIST. DO YOU WISH TO CREATE IT? (Yes, No, END): [Yes ]DO YOU WISH TO CREATE IT? (Yes, No, END): [Yes ]DO YOU WISH TO CREATE IT? (Yes, No, END): [Yes ]DO YOU WISH TO CREATE IT? (Yes, No, END): [Yes ]

If YYYY is entered, the record layout file for the enhancement will be created in the proper subdirectory. Other screen fields and functions are identical to the standard MDZMCA MDZMCA MDZMCA MDZMCA program, with the exception of the <F3> (Delete)<F3> (Delete)<F3> (Delete)<F3> (Delete) and <F5> (Copy) <F5> (Copy) <F5> (Copy) <F5> (Copy) features. At the FILE NAMEFILE NAMEFILE NAMEFILE NAME field, the screen prompt has been modified as follows:

ENTER FILE NAME (F2=list, F3=delete file, F4=print)ENTER FILE NAME (F2=list, F3=delete file, F4=print)ENTER FILE NAME (F2=list, F3=delete file, F4=print)ENTER FILE NAME (F2=list, F3=delete file, F4=print) (F5=copy from/to sy0fil, F10=next recd, ESC=en(F5=copy from/to sy0fil, F10=next recd, ESC=en(F5=copy from/to sy0fil, F10=next recd, ESC=en(F5=copy from/to sy0fil, F10=next recd, ESC=end)d)d)d)

To delete the enhancement's FILFILFILFIL file in its entirety, press the <F3> <F3> <F3> <F3> key.

To copy record layouts back and forth between the enhancement's FILFILFILFIL file, and the SY0FIL.SOA SY0FIL.SOA SY0FIL.SOA SY0FIL.SOA system file, press the <F5> <F5> <F5> <F5> key. The following will be displayed:

COPY FROM OR TO SYCOPY FROM OR TO SYCOPY FROM OR TO SYCOPY FROM OR TO SY0FIL? (F/T): 0FIL? (F/T): 0FIL? (F/T): 0FIL? (F/T): Enter FFFF to copy one or more layouts from SY0FIL.SOASY0FIL.SOASY0FIL.SOASY0FIL.SOA to the enhancement file. Enter TTTT to copy one or more layouts from the enhancement file to SY0FIL.SOAY0FIL.SOAY0FIL.SOAY0FIL.SOA.

TAG OUTBOUND RECORDS? (Y/N): TAG OUTBOUND RECORDS? (Y/N): TAG OUTBOUND RECORDS? (Y/N): TAG OUTBOUND RECORDS? (Y/N): Enter YYYY if you want to insert a "#" as the first character of the File Description field (i.e. #I/M INVENTORY MASTERFILE for the IM1 file) when copying to SY0FIL.SOASY0FIL.SOASY0FIL.SOASY0FIL.SOA, for identification purposes.

FILE LAYOUT TO BE COPIED: FILE LAYOUT TO BE COPIED: FILE LAYOUT TO BE COPIED: FILE LAYOUT TO BE COPIED: Enter the file layout(s) to be copied to or from SY0FIL.SOASY0FIL.SOASY0FIL.SOASY0FIL.SOA. You can use a "*" wildcard for the copy (i.e. AP_* or AR* or GL_0*).

RECORD ID TO BE COPIED: RECORD ID TO BE COPIED: RECORD ID TO BE COPIED: RECORD ID TO BE COPIED: Enter the Record ID to be copied. You may use a "*" wildcard to select all formats. If you used a wildcard at the "FILE LAYOUT TO BE COPIED" prompt then this field will be skipped.

Create Data FiCreate Data FiCreate Data FiCreate Data Filesleslesles

Menu:Menu:Menu:Menu: Data | Create Data Files

This is an alternative to manually creating the MD data files. This program is a legacy from version 3.21 and prior Extended Master Developer Utilities. It is probably easier and more effective to create the various data files using individual utilities. This utility can be used if you have modified the Test



System's data files and wish to scan those modified data files and pull your modifications into the project.

This utility scans the system files (i.e. SY0FIL.SOA, SY0CTL.SOA, SY0DCT.SOA, etc.) for the modified MAS90 modules (as defined in Project Properties), and pulls those records into the MD data installation files for this project. You can then use the maintenance utilities to remove any unwanted records.

CREATE XX0CTL FILE?:CREATE XX0CTL FILE?:CREATE XX0CTL FILE?:CREATE XX0CTL FILE?: Answer Y to create the CTL installation file. One "level" record will be created in the CTL file for the Base Application and each Modified Application. It is necessary to create level records for all modified applications (not just the Base Application) so that if the end-user attempts to re-install any of those applications, or upgrade them, the warning message will be displayed by SUINST, informing the end-user that the application has been modified.

Other records may be manually entered into the enhancement's CTL file using the Control File Editor, but only "level" records will be created automatically.

CREATE XX0MNU FILE?:CREATE XX0MNU FILE?:CREATE XX0MNU FILE?:CREATE XX0MNU FILE?: Answer Y to create the MNU installation file. It is extremely important to note that the MNU files maintained by the MDUT programs are not in any way similar to the format of the SY0MNU.SOA system file. In the SY0MNU.SOA file, there is one record for each entire menu.

The MDUT format for the MNU file, on the other hand, has one record for each menu bar selection, and one record for each menu selection. These records are processed one at a time by the installation program, and menu selections for your enhancement are added to existing menus, rather than replacing menus in their entirety. This allows the end-user to save important changes that they've made to their own menus, and it allows two separate enhancements to add menu selections to the same menu without overwriting each other.

If the INCLUDE TAGGED RECORDS ONLY? is set to Y, only records tagged with a # sign in the SY0MNU.SOA file will be created in the enhancement file. If set to N then all menus contained in the Base Application and modified applications, will be written to the enhancement MNU file.

CREATE XX0FIL FILCREATE XX0FIL FILCREATE XX0FIL FILCREATE XX0FIL FILE?:E?:E?:E?: Answer Y to create the FIL installation file. The record layout for the MDUT File/Record Format Maintenance file is identical to the layout used in SY0FIL.SOA.

If the INCLUDE TAGGED RECORDS ONLY? is set to Y, only records tagged with a # sign in the SY0FIL.SOA file will be created in the enhancement file. If set to N then all record layouts contained in the Base Application and modified applications, will be written to the enhancement FIL file.

Refer to the M/D File/Record Format Maintenance section of this manual for further details concerning tagging.



CREATE XX0FRM FILE?:CREATE XX0FRM FILE?:CREATE XX0FRM FILE?:CREATE XX0FRM FILE?: Answer Y to create the FRM installation file. The record layout for the MDUT Generic Form Maintenance file is identical to the layout used in SY0FRM.SOA.

If the INCLUDE TAGGED RECORDS ONLY? is set to Y, no form records will be created in the enhancement file. If set to N then all forms contained in the Base Application and modified applications, will be written to the enhancement FRM file.

CREATE XX0EOP FILE?:CREATE XX0EOP FILE?:CREATE XX0EOP FILE?:CREATE XX0EOP FILE?: Answer Y to create the EOP installation file. The record layout for the MDUT Period End Option Maintenance file is identical to the layout used in SY0EOP.SOA.

CREATE XX0SIZ FILE?:CREATE XX0SIZ FILE?:CREATE XX0SIZ FILE?:CREATE XX0SIZ FILE?: Answer Y to create the SIZ installation file. The record layout for the MDUT File Sizing Maintenance file is identical to the layout used in SY0SIZ.SOA.

CREATE XX0DCT FILE?:CREATE XX0DCT FILE?:CREATE XX0DCT FILE?:CREATE XX0DCT FILE?: Answer Y to create the DCT installation file. The record layout for the MDUT Data Dictionary Maintenance file is identical to the layout used in SY0DCT.SOA.

If the INCLUDE TAGGED RECORDS ONLY? is set to Y, only records tagged with a # sign in the SY0DCT.SOA file will be created in the enhancement file. If set to N then all dictionary files contained in the Base Application and modified applications, will be written to the enhancement DCT file.

Refer to the M/D Data Dictionary Maintenance section of this manual for further details concerning tagging.

CREATE XX0CMP FILE?:CREATE XX0CMP FILE?:CREATE XX0CMP FILE?:CREATE XX0CMP FILE?: Answer Y to create the CMP installation file. One record will be created in the CMP file for the Base Application and each Modified Application.

CREATE XX0MOD FILE?:CREATE XX0MOD FILE?:CREATE XX0MOD FILE?:CREATE XX0MOD FILE?: Answer Y to create the MOD installation file. One record will be created in the CMP file for the Base Application and each Modified Application.

INCLUDE APPLICATIONS:INCLUDE APPLICATIONS:INCLUDE APPLICATIONS:INCLUDE APPLICATIONS: You can include or exclude any of the enhancement's modified applications, for purposes of the file scan. You may not exclude the Base Application.



Sage MenuSage MenuSage MenuSage Menu

Menu:Menu:Menu:Menu: Sage

This menu leads to various standard Sage Master Developer programs. Note the four programs that have function keys assigned for faster access.

Hotkey:Hotkey:Hotkey:Hotkey: Control-C hotkeys



Run MenuRun MenuRun MenuRun Menu

Editor (PvX) Nomads ProvideX Prompt MAS90 DOS Prompt Windows Explorer FTP Voyager (if installed) WinZip (if installed)

Most of the features of CodeZilla are accessible through it's menu system. For the most often used functions, hotkeys are made available.

Menus:Menus:Menus:Menus:

Menu SelectionMenu SelectionMenu SelectionMenu Selection DescriptionDescriptionDescriptionDescription

Editor (PvX) Opens the ProvideX editor, as selected in Options.

Nomads Opens the Nomads ProvideX graphical library editor. ProvideX Prompt Runs a ProvideX interpreter.

MAS90 Runs the MAS90 Launcher, as selected in Select Test System. Note that this value is saved for each program that has worked on the project in Properties.ini.

DOS Prompt Opens a DOS Command Interpreter. The path in the DOS interpreter is set to the current selection in the CodeZilla IDE.

Windows Explorer Opens Windows Explorer to same path as the current selection in the CodeZilla IDE.

FTP Voyager

If FTP Voyager is installed, this menu selection appears. When selected, FTP Voyager is executed. Shortcut: Ctrl-F

FTP Voyager must be installed to the default directory to be detected.

HotkeyHotkeyHotkeyHotkey: Control-F hotkeys

FTP Voyager website: http://www.ftpvoyager.com

WinZip

If WinZip is installed, this menu selection appears. When selected, WinZip is executed. Shortcut: Ctrl-W

WinZip must be installed to the default directory to be detected.

HotkeyHotkeyHotkeyHotkey: Control-W hotkeys

WinZip website: http://www.winzip.com

See Also: Menu Selections, Using CodeZilla

http://www.ftpvoyager.com/

http://www.winzip.com/



Editor (PvX)Editor (PvX)Editor (PvX)Editor (PvX)

Menu:Menu:Menu:Menu: Run | Editor (PvX)

Hotkey:Hotkey:Hotkey:Hotkey: Control-E hotkeys

Runs the ProvideX program editor that has been selected in View/Options. Depending on the setting, either *IT*IT*IT*IT or *E*E*E*E are used.

Double-clicking a program file runs the editor with that file loaded.

NomadsNomadsNomadsNomads

Menu:Menu:Menu:Menu: Run | Nomads

Hotkey:Hotkey:Hotkey:Hotkey: Control-N hotkeys

Runs Nomads, the ".lib" Library editor.

Double-clicking a ".lib" library file runs the Nomads editor with that file loaded.

Note:Note:Note:Note: CodeZilla modifies Nomads "on-the-fly" to add the ability to open a selected file. This modification does not otherwise affect the operation of Nomads.



ProvideX PromptProvideX PromptProvideX PromptProvideX Prompt

Menu:Menu:Menu:Menu: Run | ProvideX Prompt

Hotkey:Hotkey:Hotkey:Hotkey: Control-X hotkeys

Launches a ProvideX session.

DOS PromptDOS PromptDOS PromptDOS Prompt

Menu:Menu:Menu:Menu: Run | DOS Prompt

Hotkey:Hotkey:Hotkey:Hotkey: Control-D hotkeys

Launches a DOS Prompt window. Selects the currently selected folder (either Test System or Project Folder). For instance, if you are currently acting on the Project and have the "AP" folder open, the DOS prompt will have the path set to the Project's "AP" directory, like "C:\PROJECT\AP".

Windows ExplorerWindows ExplorerWindows ExplorerWindows Explorer

Menu:Menu:Menu:Menu: Run | Windows Explorer

Hotkey:Hotkey:Hotkey:Hotkey: Control-W hotkeys

Launches a Windows Explorer. Selects the currently selected folder (either Test System or Project Folder).

MAS90MAS90MAS90MAS90

Menu:Menu:Menu:Menu: Run | MAS90

Hotkey:Hotkey:Hotkey:Hotkey: Control-M hotkeys

Launches the MAS90 test system.



View MenuView MenuView MenuView Menu

ActOn Refresh Options

Act OnAct OnAct OnAct On

Menu:Menu:Menu:Menu: View | Act On

Shortcut:Shortcut:Shortcut:Shortcut: Double-click on the status bar.

Selects whether to act on the Project Folder or the Test System.

When "Project" is selected, all edits will take place in the Project's folder. When you synchronize, the changes will then be copied to the Test System folder on your system.

Or, if "Test System" is selected, your changes are made to the Test System's folder.

The right side of the status bar on the bottom of CodeZilla's window shows which system is currently being acted upon.

.

See Also:See Also:See Also:See Also: Synchronize Project

RefreshRefreshRefreshRefresh

Menu:Menu:Menu:Menu: View | Refresh

Shortcut:Shortcut:Shortcut:Shortcut: F5

Reloads/displays the selected Project folder.

See Also:See Also:See Also:See Also: Hotkeys

OptionsOptionsOptionsOptions

Menu:Menu:Menu:Menu: View | Options

Main TabMain TabMain TabMain Tab

PvX Program Editor:PvX Program Editor:PvX Program Editor:PvX Program Editor: Select "*E" to use the "_E" ProvideX program editor or "*IT" to use the "_IT" ProvideX editor.

IT Pvx Program Editor Optional INI File:IT Pvx Program Editor Optional INI File:IT Pvx Program Editor Optional INI File:IT Pvx Program Editor Optional INI File: If present, this fully qualified filename will be used when the IT program editor is launched.

Character MAS90:Character MAS90:Character MAS90:Character MAS90: If checked, CodeZilla will show the menu choice on the Run Menu and a toolbar



icon to launch the old Character MAS90. This is provided to allow development on older character-based systems.

Project Bar:Project Bar:Project Bar:Project Bar: Selects whether the Project toolbar is shown.

Test System Bar:Test System Bar:Test System Bar:Test System Bar: Selects whether the Test System toolbar is shown.

Paths TabPaths TabPaths TabPaths Tab

Tool Tool Tool Tool System Path:System Path:System Path:System Path: Select the MAS90 system to use to run the "*IT" program editor (if selected) and Nomads. If blank, the Test System will be used to run these programs. This option is made available because programmers may prefer to use the latest versions of these programs, even when working on older Test Systems. Note: Note: Note: Note: If the "\MAS90" portion of the path is not included, it will be appended to the path entered. The entry is made without a trailing "\" character - if entered, "\" will be trimmed from the path entry.

Standard Distribution Files Path:Standard Distribution Files Path:Standard Distribution Files Path:Standard Distribution Files Path: The path to the folder that contains CodeZilla's standard distributions files. These files and folders are included with every product distribution created by CodeZilla. By default, this is a folder called "DistFiles" under the CodeZilla program directory. SeeSeeSeeSee Distribution Files

ToolbarToolbarToolbarToolbar

The toolbar allows quick access to auxiliary programs and shows the currently selected Project folder and currently selected Test System. It also allows you to select a Project folder or a Test System.

The function of a particular icon can be ascertained by hovering the mouse cursor over it.

See also:See also:See also:See also: Menu Selections, Hotkeys



HotkeysHotkeysHotkeysHotkeys

ProjectProjectProjectProject

ControlControlControlControl----A:A:A:A: Add File to Project ControlControlControlControl----C:C:C:C: Close Project Folder ControlControlControlControl----D:D:D:D: DOS Prompt ControlControlControlControl----E:E:E:E: Editor (PvX) ControlControlControlControl----F: F: F: F: FTP Voyager (if installed) ControlControlControlControl----I: I: I: I: Distribute Project ControlControlControlControl----M:M:M:M: MAS90 ControlControlControlControl----N:N:N:N: Nomads ControlControlControlControl----O:O:O:O: Open Project Folder ControlControlControlControl----P:P:P:P: Project Properties ContContContControlrolrolrol----R:R:R:R: Run Selected ControlControlControlControl----T:T:T:T: Install Project to Test System ControlControlControlControl----W:W:W:W: Windows Explorer ControlControlControlControl----X:X:X:X: ProvideX Prompt ControlControlControlControl----Y:Y:Y:Y: Synchronize Project and Test System ControlControlControlControl----Z: Z: Z: Z: WinZip (if installed)

F1: F1: F1: F1: Help F3: F3: F3: F3: Sage File/Record Display/Maintenance F4: F4: F4: F4: Sage File Display and Maintenance F5: F5: F5: F5: Refresh F6: F6: F6: F6: Sage Roswell Data Dictionary Maintenance F7: F7: F7: F7: Sage ALE Listmode Maintenance F8:F8:F8:F8: Sage DCT Dictionary Maintenance

See also:See also:See also:See also: Menu Selections, Toolbar



Using CodeZillaUsing CodeZillaUsing CodeZillaUsing CodeZilla

Menu Selections Toolbar Hotkeys

Project StorageProject StorageProject StorageProject Storage

CodeZilla uses a simple, easy to understand storage system. The project is simply stored in a folder on the system as normal files. CodeZilla does not compress files or consolidate data into a proprietary file.

Project Folder Structure Properties.ini File

Note: Note: Note: Note: Files and folders with names beginning with a "!" (bang) character are not included in the Distribution.

See Also: See Also: See Also: See Also: Project Properties

Project Folder StructureProject Folder StructureProject Folder StructureProject Folder Structure

The structure used to store CodeZilla projects is very simple. The "root" of the project contains folders that correspond to folders in the target customer MAS90 system. For instance "SOA" and "AP". Files in the Project's folders are copied during installation to the corresponding folders on the target system

In this version of CodeZilla, the directory structure is one level deep. Neither CodeZilla nor the installation programs have the ability to copy trees of folders.

Additional files can be stored in the "root" of the Project. These files are shown and can be modified in CodeZilla, but are not included in the Project distribution.

The file "Properties.ini" is stored in the Project "root". This is a standard Windows "ini" file that contains the Project Properties.

See Also:See Also:See Also:See Also: Project Storage, Properties.ini File

Properties.ini FileProperties.ini FileProperties.ini FileProperties.ini File

The Project's Properties, as set in the Project Properties dialog, contain all of the Project's various properties.

Below is an example of a Properties.ini file. The field names correspond with the field names in the Project Properties dialog, with the exception of LastTestSystemFolder, which is stored under the programmer's username. The last Test System folder is stored for each programmer that works on a Project.

[Main] ProjectName=MRWV West Virginia Mag Media Code3=RWV Version=3.06 ReleaseDate=4/24/00



PartNumber=***DSD*** PrimaryModule=MR AllModules=MR; [Installation] ZipExeOutputFolder=n:\dsde\seinst OutputFolder=M:\dsde\inst\MRWV.306 Password=XXXXXXXX ZipExeFilename=MRWV306 [andya] LastTestSystemFolder=C:\341\MAS90

See Also:See Also:See Also:See Also: Project Properties dialog, Project Folder Structure

Project Distribution SystemProject Distribution SystemProject Distribution SystemProject Distribution System

Project Distributions Distribution Files Installation Programs Installation Instructions

Product DistriProduct DistriProduct DistriProduct Distributionsbutionsbutionsbutions

Products created with CodeZilla can be installed to all current MAS90 systems, whether Windows or UNIX based. This allows development and distribution to be performed on the Windows platform without installation issues on UNIX systems. See Distribute Project for information on how to create a distribution.

The distributions created are not media specific. You can use any suitable media such as CD-ROM, DVD-ROM, Zip, ZIP files or Self-extracting ZIP files. This allows you to easily e-mail your product to a customer. The exact same CD-ROM can be installed to either Windows or UNIX. The exact ZIP image will likewise install to either (though, you cannot install a self-extracting EXE/ZIP to UNIX).

The system does not, however, create distributions that are split across multiple disks. So, many distributions will not fit on a floppy disk. Your customer will probably appreciate getting your product on a CD-ROM or by e-mail. The system also does not compress files into a single image. The previous diskette-based installation system compressed all of the files into proprietary libraries. This saved a little bit of disk space, but had little practical benefit.

Whether for Windows or UNIX, the installation program's job is easy to understand. Distributions have subdirectories named after the same subdirectories found in a MAS90 system. For instance, all files that are to be copied to the MAS90's "AP" directory are found in the distribution's "AP" directory.

Library patLibrary patLibrary patLibrary patch systemch systemch systemch system

The Library patch system, if checked in project properties, will create a ‘patch file’ (MM_inst.pip, which is really a ProvideX program that is called during installation) in the projects primary module folder. This system uses the Control System to compare your changes to a standard MAS90 system. Your control system should have no modifications on it prior to distribution. If the library in the project exists in the control system, then only the difference in libraries are shipped in the patch file. If the library is a new one you have created, then the whole library is shipped instead. This patch file can also be used to upgrade a new version of MAS with your library changes, simply by running it, which should help to speed upgrades.



Windows InstallationWindows InstallationWindows InstallationWindows Installation

Installation to a Windows system is performed "Setup.exe". Setup requires that the customer agree to a license agreement before installing the software. It displays the version of the software being installed. It uses the Windows interface to help the installer select a MAS90 system to install to (by default it tries to select an installation of MAS90).

The "Setup.exe" program changes a file's read-only attribute off after copying it. This is because files copied from a read-only media such as a CD-ROM can have this attribute left turned-on when the files is copied to the destination.

The NSIS installer system can create a package with a filename provided in the Zip/Exe Filename box. This is a complete setup package in one file.

Setup WindowSetup WindowSetup WindowSetup Window

In this example, DSD's product APCB Cash Basis is being installed. Note that the user has to select "Agree" to the License Agreement before the "Install" button is available. The "Version" button leads to an HTML window showing exactly which MAS90 Module versions this product is compatible with. The setup program has found "N:\90CS", where a MAS90 system is located. Windows Setup Program

NSIS Installer WizardNSIS Installer WizardNSIS Installer WizardNSIS Installer Wizard

CodeZilla now has an “InstallShield” like installation packager. This is the NSIS installation System. This system can be downloaded from http://nsis.sourceforge.net. In order to use this feature, then NSIS must be installed to its default directory on the same workstation as CodeZilla. Once this is done; CodeZilla then finds the NSIS programs and uses NSIS to create a project distribution.

http://nsis.sourceforge.net/



A license page will automatically be generated if there is a file named ‘license.rtf’ in RTF format in the Standard distribution files directory.

NSIS is configurable for your own graphics and icons. In this example, DSD's product APCB Cash Basis is being installed. This is the first wizard screen. Note that this system is familiar to Windows users as a standard setup sequence. You can see that DSD’s graphics display on the Welcome screen. In order to use your graphics, you must ensure the graphics are in the correct .bmp format. The dimensions and specifications for the graphics are as follows:

Welcome/Finish page bitmap:

164x314 pixels

Header Bitmap: 150x57 pixels

The plain text publisher.nsh file, found in the CodeZilla/DistFiles directory, is a ‘header’ file that is included into the package generation script. This file will have to be modified in order for your graphics to show up. Modify this file, and ensure that it is in the Standard Distribution Files Directory as you have chosen in the Options. There are comments in the publisher.nsh file which will help you chose the right paths to your graphics.

The package executable is created in the Image destination folder, named either setup,exe or the name that you entered in the Project Distribution Dialog Zip/Exe Name field.



UNIX InstallationUNIX InstallationUNIX InstallationUNIX Installation

Installation to UNIX systems is via a Bourne shell script called "INSTALL". UNIX Installation Script

See Also:See Also:See Also:See Also: Distribute Project, Windows Installation Instructions, UNIX ZIP Installation Instructions, UNIX CD-ROM Installation Instructions, Distribution Files



Distribution FilesDistribution FilesDistribution FilesDistribution Files

In addition to the files that you have created or included in your project, these files are included by CodeZilla to facilitate product installation and operation. Some files are generated by CodeZilla during creation and others are copied from the Standard Distribution Path.



Product Root FolderProduct Root FolderProduct Root FolderProduct Root Folder

FileFileFileFile DescriptionDescriptionDescriptionDescription

Autorun.inf

Windows Automatic CD-ROM Run Script: This (text) script file causes Windows to execute the Setup.exe installation program, if the distribution is located in the root directory of the CD-ROM.

Automatically generated during Distribution creation.

Dsdinst.exe

(New for the 4.0 release)(New for the 4.0 release)(New for the 4.0 release)(New for the 4.0 release)

A new program, Dsdinst.exeDsdinst.exeDsdinst.exeDsdinst.exe, has been added to the distribution. If this program is present in the Setup.exe directory then it is called by Setup.exe after the files have been copied to the MAS 4.0 System.

Dsdinst.exeDsdinst.exeDsdinst.exeDsdinst.exe accepts one command line argument: the Target Installation path. Dsdinst.exeDsdinst.exeDsdinst.exeDsdinst.exe searches this target path’s SOA directory to find a file named MDINST

CodeZilla creates an MDINST file with the primary Module for the product, but if you wish to just use Dsdinst.exeDsdinst.exeDsdinst.exeDsdinst.exe in another context, then MDINST must contain the Module(s) to be modified in the 2 letter form on separate lines.

After Dsdinst.exeDsdinst.exeDsdinst.exeDsdinst.exe finds the MDINST file, it is read and the Modules to perform installation on are stored line by line.

Dsdinst.exeDsdinst.exeDsdinst.exeDsdinst.exe then attempts to find the Pvxcom.exePvxcom.exePvxcom.exePvxcom.exe program, and if successful, starts that program. Dsdinst.exeDsdinst.exeDsdinst.exeDsdinst.exe then initializes the pvcompvcompvcompvcom object, loads the MAS 4.0 SY Installation Object, and calls the object.nInstall(“Module code”) method, for each module stored from MDINST.

Inst_id.txt Text file that identifies the distribution.


INSTALL UNIX Installation Script (Bourne Shell) See See See See UNIX Installation Script

License.htm

HTML License Agreement: Used by Setup.exe. User must agree with the License before the product can be installed.

Must be created by the developer and copied to the CodeZilla Standard Distribution Path. Copied from the CodeZilla Standard Distribution Path.

Setup.exe

Windows Installation Program. Copied from the CodeZilla Standard Distribution Path. It is stored as CZsetup.exe to avoid naming conflicts with the Microsoft installation system used to distribute and install CodeZilla. CodeZilla renames it when it is copied to the Project Distribution. SeeSeeSeeSee Windows Setup Program

Versions.txt

Text file that identifies the exact Sage MAS90 modules that the distribution is compatible with.




Product SOA FolderProduct SOA FolderProduct SOA FolderProduct SOA Folder


EMD.BMP 320 pixels wide by 240 pixels high Windows bitmap that is displayed by SUMDIN during the MAS90 installation phase. Copied from the CodeZilla Standard Distribution Path SOA folder.

MDINST

When present, triggers MAS90 to run the SUMDIN program and compile the project's MD Data Files into the MAS90 system's various data files such as SY0CTL.SOA. This file is generated when the distribution is created. It is a text file in which the first two characters are "MD" (minus quotes, in caps). Generated by CodeZilla during distribution creation.

SUMDI4

(New for the 4.0 release)(New for the 4.0 release)(New for the 4.0 release)(New for the 4.0 release)

Compiles the Master Developer data files in to the MAS90 system's data files (SY0CTL.SOA, SY0FILE.SOA, SY0MNU.SOA, etc.) Copied from the CodeZilla Standard Distribution Path SOA folder.

In 4.0 MAS 90, SUMDIN is not called by "MAS90" during startup, so it is never run. SUMDI4 is executed by the !mm_Installation.pvc (which must be renamed to remove the "!" and substitute the 2-letter primary module code for "mm") in the primary module folder.

SUMDI4 inserts new system data records, and properly builds the new task and menuing system files, without having to have the xxINST directory installed in MAS 90.

Ignored for installations prior to 4.0.Ignored for installations prior to 4.0.Ignored for installations prior to 4.0.Ignored for installations prior to 4.0.

SeeSeeSeeSee SUMDIN

SUMDIN

Compiles the Master Developer data files in to the MAS90 system's data files (SY0CTL.SOA, SY0FILE.SOA, SY0MNU.SOA, etc.) Copied from the CodeZilla Standard Distribution Path SOA folder.

Ignored for 4.0 + installations.Ignored for 4.0 + installations.Ignored for 4.0 + installations.Ignored for 4.0 + installations.

SeeSeeSeeSee SUMDIN

SUMDN2

A subprogram used by SUMDIN that scans the MAS90 program directories for Master Developer data files. It then constructs a list of MD enhancements that are to be compiled into the MAS90 system. Control is then returned to SUMDIN, which completes installation of those products. Copied from the CodeZilla Standard Distribution Path SOA folder.

SUMDMN

This program is run near the end of the MAS90 MD installation process. It compiles enhancement menu entries into the system menu file (SY0MNU.SOA). This data is later compiled into the MAS90 Graphical Launcher data file. Copied from the CodeZilla Standard Distribution Path SOA folder.

SYLEVL

MD Installed Application Listing: Replaces the standard MAS90 programs and displays MD modifications (from MD Level Records) separately from standard Sage modules. Copied from the CodeZilla Standard Distribution Path SOA folder.

SWLEVL as SYLEVEL

SWLEVL.LIB as SYLEVEL



Product Primary Module Folder (ie. AP, etc.)Product Primary Module Folder (ie. AP, etc.)Product Primary Module Folder (ie. AP, etc.)Product Primary Module Folder (ie. AP, etc.)


!mm_Installation.pvc

(New(New(New(New for the 4.0 release) for the 4.0 release) for the 4.0 release) for the 4.0 release)

This file must be copiedmust be copiedmust be copiedmust be copied from the Program Program Program Program Files/CodeZilla/distfiles/SOAFiles/CodeZilla/distfiles/SOAFiles/CodeZilla/distfiles/SOAFiles/CodeZilla/distfiles/SOA folder to the primary module folder in the project. It must then be renamed as mm_Installation.pvc (where mm is the Primary Module 2-letter code).

Inside this Providex program, rename the CLASS "MD_Installation", substituting the upper case 2-letter module code for "MD".

The SY_Installation class searches for an mm_Installation.pvc file, and attempts to “new up” the mm_Installation class for the module code passed in the Sy_installation’Install method. If this is successful, then the four functions, PreInstall(), PostInstall(), PreFinalize(), PostFinalize() are performed from this mm_Installation class in SY_Installation’Install.

The template contains a call to SUMDI4, which works on the same principle as the SUMDIN program, in MAS versions prior to 4.0.

Ignored for installations prior to 4.0.Ignored for installations prior to 4.0.Ignored for installations prior to 4.0.Ignored for installations prior to 4.0.

Note: Note: Note: Note: This program must be in ProvideX format, not ASCII.

SeeSeeSeeSee SUMDIN

Files nFiles nFiles nFiles not ot ot ot encryptedencryptedencryptedencrypted

These files are not encrypted by CodeZilla when a distribution is created.

FileFileFileFile

DIZRMW

DIZRMZ

RMZRML

DIZRLA|

DIZRML

PMZRMZ

PMZRML

TBZSHZ

TBZSHL

DIZCHK

DIZUAB



SUMDINSUMDINSUMDINSUMDIN

The SUMDIN program performs these tasks, in the following order:

1. Check for a correctly formatted MDINST MDINST MDINST MDINST file. Some versions of SUINS* do not create correctly formatted MDINST files. If MDINST is found to be incorrect, call SUMDN2SUMDN2SUMDN2SUMDN2, which rebuilds it correctly. SeeSeeSeeSee Distribution Files

2. Display a bitmap called eeeeeeeeeeee.BMP.BMP.BMP.BMP (where eee represents the Project's 3-Letter Code). If this file does not exist, then a bitmap file named EMD.BMPEMD.BMPEMD.BMPEMD.BMP is displayed. SeeSeeSeeSee Distribution Files

3. Read the next MDINST record.

4. If the enhancement installation data files include a mm0RUN.eee (where mm represents the module and eee represents the Project's 3-Letter Code) file, open it and call each of the indicated programs, in the order that they appear in the mm0RUN.SOA file. SeeSeeSeeSee RUN Run File

5. Install menu records mm0MNU.eee (where mm represents the module and eee represents the Project's 3-Letter Code), if they exist (using SUMDMN). SeeSeeSeeSee MNU Menu File

6. If MAS90/W is installed, update the file MNUMOD.TXT in the ../MAS90/LAUNCHER directory. This file contains the menu structure for the MAS90 Launcher.

7. Install file/record layout records mm0FIL.eee (where mm represents the module and eee represents the Project's 3-Letter Code), if they exist. Existing records for that file layout (only) are erased first. In other words, if the AP1 layout is about to be installed, all existing AP1 records are first erased from SY0FIL.SOA. This ensures that no unwanted AP1 records are left in SY0FIL.SOA after the installation has taken place. SeeSeeSeeSee FIL File Format

8. Install Data Dictionary files, if they exist. As with the SY0FIL.SOA installation, all records for each D/D file are first erased, before installing. Unlike the MAS90 installation process, all D/D files for the entire application are not first erased. Only the D/D files being installed are erased first!

9. Install Forms records, if they exist. SeeSeeSeeSee FRM Form File

10. Install EOP records, if they exist. SeeSeeSeeSee EOP Period End

11. Install SIZ records, if they exist. 12. If the mm0MOD.eee (where mm represents the module and eee represents the Project's

3-Letter Code) file exists, process those records. For each record, add the "tag string" to the appropriate level record in SY0CTL.SOA, for the enhancement's Base Application and any modified applications. The existence of this tag string ensures that users will be warned in the future that they have modified software, when they attempt to reinstall or upgrade.

13. If the mm0CMP.eee (where mm represents the module and eee represents the Project's 3-Letter Code) file exists, write its records to a temporary file. It is necessary to create a temporary file, because two or more enhancements may be installed at the same time, and it is not desirable to have the same application compile twice. All compilations are performed at once just before SUMDIN execution terminates. SeeSeeSeeSee CMP Dictionary Compile

14. Install REC records, if they exist. 15. Install CTL records, if they exist. SeeSeeSeeSee CTL Control File

16. Repeat steps 2 through 15 for each enhancement record in MDINST.

17. Perform all Data Dictionary compilations.

18. Perform a GUI menu compilation.

19. Erase temporary files and exit. Control is returned to the MAS90 MAS90 MAS90 MAS90 program.

See Also:See Also:See Also:See Also: Distribution Files



Installation ProgramsInstallation ProgramsInstallation ProgramsInstallation Programs

Windows Installation Program NSIS Installation Package UNIX Installation Script

Windows Setup ProgramWindows Setup ProgramWindows Setup ProgramWindows Setup Program

When CodeZilla distributions are installed on Windows MAS90 systems (including CS), Setup.exe is used to copy the project's various files and installation files to the system. Setup is a Windows 32-bit program, written in Delphi. It clearly shows the steps needed to install the program and in our experience, does not generate very many support calls.

The Product Name and Version are displayed.

The user can check which Sage modules the enhancement is compatible with. (It executes the file "Versions.htm".)

The License Agreement has to be agreed to before the program will install the product.

The default MAS90 Path is searched for by Setup from the highest available drive letter to the lowest. The user does not have to enter the "\MAS90" part of the path. For instance, if MAS90 is in "C:\90W\MAS90", the user could enter either "C:\" or "C:\90W\MAS90".

See Also: See Also: See Also: See Also: Distribution Files



NSIS Installer ProgramNSIS Installer ProgramNSIS Installer ProgramNSIS Installer Program

The new NSIS Installer generation option will produce either a setup.exe or a filename that was entered in the Product Distributions Zip/Exe Filename box.

When CodeZilla distributions are installed on Windows MAS90 systems (including CS), the NSIS package is used to copy the project's various files and installation files to the system. This Installer is a Windows 32-bit program. It clearly shows the steps needed to install the program and in

our experience, does not generate very many support calls.

The Product Name and Version are displayed, and developers have the option to place their own logos or graphics on the wizard screens.

The License Agreement has to be agreed to before the program will install the product.

The default MAS90 Path is retrieved from the Windows Registry. The user must enter the "\MAS90" portion of the path if they chose to install to another Sage MAS 90 System.




UNIX Installation UNIX Installation UNIX Installation UNIX Installation ScriptScriptScriptScript

The UNIX Installation script is an ASCII UNIX text file called "INSTALL". The filename is in uppercase so it can be distributed on a High Sierra format CD-ROM.

If you modify this script, you must retain DSD's Copyright declarations.

Note that UNIX text files do use Window's CR/LF standard, instead using a UNIX newline character. If you wish to convert the script to a Windows file, use the UNIX utility "xtod". To convert it back to a UNIX text file, use "dtox". (Detox, get it? Those UNIX guys are such scamps.) You can find these utilities on a UNIX machine or on the Internet (including DOS versions).

You may note that the script does a bunch of stuff like renaming all of the files to lower case and setting UNIX file attributes. This is one of the reasons that the single project distribution can install to UNIX systems, as well as Windows systems.


Installation InstructionsInstallation InstructionsInstallation InstructionsInstallation Instructions

Windows Installation Instructions UNIX CD-ROM Installation Instructions UNIX ZIP Installation Instructions

Windows Installation InstructionsWindows Installation InstructionsWindows Installation InstructionsWindows Installation Instructions

The following are the instructions to install a CodeZilla developed project to a Windows based MAS90 system (including CS).

Read this entire section before proceeding.

1. Exit MAS 90: Exit MAS 90: Exit MAS 90: Exit MAS 90: Exit all MAS 90 sessions. 2. BackBackBackBack----up: up: up: up: Back-up existing MAS 90 data. 3. Check Levels:Check Levels:Check Levels:Check Levels: MAS 90 module levels must match those for this exact version of the

enhancement. 4. Install the Software:Install the Software:Install the Software:Install the Software: Run Setup. Enter the name of the directory where MAS 90 is installed

and click the Install button. This can be run from the server or a workstation. 5. ReReReRe----Start MAS 90: Start MAS 90: Start MAS 90: Start MAS 90: The MAS 90 system will be updated.

UNIX CDUNIX CDUNIX CDUNIX CD----ROM Installation InstructionsROM Installation InstructionsROM Installation InstructionsROM Installation Instructions

Products created with CodeZilla can be installed to a UNIX MAS90 system from a CD-ROM Distribution. Though CodeZilla is strictly a Windows program, the product distributions created can be installed on any type of MAS90 system.

This takes advantage of the High Sierra (ISO9960) CD-ROM standard and the fact that MAS90 programs use a naming standard that works across platforms. The installer needs to mount the CD-ROM as a High Sierra file system and then run the Bourne shell installation script "INSTALL".

Note that when you burn the CD-ROM, you need to select the "ISO9660" format, if available. We have not tested UNIX installation using the "Joliet" extensions.



The following are instructions for installing a CodeZilla developed product to a UNIX MAS90 system from a CD-ROM distribution:

6. Exit MAS 90: Exit MAS 90: Exit MAS 90: Exit MAS 90: Exit all MAS 90 sessions. 7. BackBackBackBack----up: up: up: up: Back-up existing MAS 90 data. 8. Check Levels:Check Levels:Check Levels:Check Levels: MAS 90 module levels must match those for this exact version of the

enhancement. 9. Mount CDMount CDMount CDMount CD----ROM:ROM:ROM:ROM: Mount the CD-ROM to the UNIX file system.

SCO UNIX:

mkdir /mnt mkdir /mnt/cdrom mount -f HS /dev/cd0 /mnt/cdrom

AIX:

mkdir /mnt mkdir /mnt/cdrom mount -v cdrfs /dev/cd0 /mnt/cdrom

10. Login as a MAS 90 User:Login as a MAS 90 User:Login as a MAS 90 User:Login as a MAS 90 User: This is to ensure that files will be written with the correct group ID. 11. Run Installation Script:Run Installation Script:Run Installation Script:Run Installation Script: Execute the installation script.

/mnt/cdrom/INSTALL.

This script uses the Borne Shell (sh).

The script will ask you to enter two directories: Destination Directory and Source Directory. The Destination Directory is the directory where MAS 90 is installed (i.e.: /mas90). The Source Directory is the directory where the CD-ROM is mounted (i.e.: /mnt/cdrom).

12. ReReReRe----Start MAS 90: Start MAS 90: Start MAS 90: Start MAS 90: The MAS 90 system will be updated. 13. UnUnUnUn----mount CDmount CDmount CDmount CD----ROM:ROM:ROM:ROM:

cd / umount /dev/cd0

Note: "/dev/cd0" ends with a zero.

UNIX ZIP InstallationUNIX ZIP InstallationUNIX ZIP InstallationUNIX ZIP Installation

Products created with CodeZilla can be installed to a UNIX MAS90 system from a ZIP of the Distribution Image. The Distribution needs to be "unzipped" into a temporary directory. The user can then use an included (Bourne) shell script to install the product into the MAS90 system.

CodeZilla is strictly a Windows program; however, the product distributions created can be installed on any type of MAS90 system.

Note: Note: Note: Note: Utilities to explode ZIP files on UNIX systems are readily available - search the Internet.

The following are instructions for installing a CodeZilla developed product to a UNIX MAS90 system from a ZIP of the distribution:

UNIX ZIP Installation InstructionsUNIX ZIP Installation InstructionsUNIX ZIP Installation InstructionsUNIX ZIP Installation Instructions

14. Exit MAS 90: Exit MAS 90: Exit MAS 90: Exit MAS 90: Exit all MAS 90 sessions. 15. BackBackBackBack----up: up: up: up: Back-up existing MAS 90 data.



16. Check Levels:Check Levels:Check Levels:Check Levels: MAS 90 module levels must match those for this exact version of the enhancement.

17. UnzipUnzipUnzipUnzip Distribution into temporary directory: Distribution into temporary directory: Distribution into temporary directory: Distribution into temporary directory: Use a compatible utility to unzip the distribution into a temporary directory of your choosing.

18. Login as a MAS 90 User:Login as a MAS 90 User:Login as a MAS 90 User:Login as a MAS 90 User: This is to ensure that files will be written with the correct group ID.

19. Run Installation Script:Run Installation Script:Run Installation Script:Run Installation Script: Execute the installation script.

./INSTALL

This script uses the Borne Shell (sh).

The script will ask you to enter two directories: Destination Directory and Source Directory. The Destination Directory is the directory where MAS 90 is installed (i.e.: /mas90). The Source Directory is the directory where the enhancement is being installed from (i.e.: /temp).

20. ReReReRe----Start MAS 90: Start MAS 90: Start MAS 90: Start MAS 90: The MAS 90 system will be updated.

See Also:See Also:See Also:See Also: Product Distributions



Known LimitationsKnown LimitationsKnown LimitationsKnown Limitations

CodeZilla LimitationsCodeZilla LimitationsCodeZilla LimitationsCodeZilla Limitations

Library Master Program Password Protection: Library Master Program Password Protection: Library Master Program Password Protection: Library Master Program Password Protection: If certain ProvideX programs are included in a project are created using a Sage Library Master ProvideX Activation Key andandandand the ProvideX interpreter being used by CodeZilla does not have Library Master program modification permission, those programs in the Distribution will not be password protected. To be able to include the files into the project Distribution with password protection, you need to either convert the program to the same PvX permission as the rest of the project or use a LM ProvideX key to Distribute the project.

Installation ProgInstallation ProgInstallation ProgInstallation Programs Only Install One Level Deep:rams Only Install One Level Deep:rams Only Install One Level Deep:rams Only Install One Level Deep: The CodeZilla installation programs only install sub-directories that are one level deep. So, if you have a sub-directory under AP, the AP directory will be carried to the target system, but not the sub-directory in it. No No No No longer applies with the NSIS Install longer applies with the NSIS Install longer applies with the NSIS Install longer applies with the NSIS Install package generation feature.package generation feature.package generation feature.package generation feature.

Only One CTL (Control) File Per Project:Only One CTL (Control) File Per Project:Only One CTL (Control) File Per Project:Only One CTL (Control) File Per Project: The Project cannot have more than one CTL file.

Projects are Max One Level Deep:Projects are Max One Level Deep:Projects are Max One Level Deep:Projects are Max One Level Deep: Project folders are one level deep, inside the Project Root.



CodeZilla InstallationCodeZilla InstallationCodeZilla InstallationCodeZilla Installation

Installation Overview Additional Software Required

Additional Software RequiredAdditional Software RequiredAdditional Software RequiredAdditional Software Required

CodeZilla integrates the tools needed to complete and distribute Master Developer enhancements. It interfaces with other software tools to increase developer efficiency.

CodeZilla requires that the MAS90 Test System have the Sage Master Developer modules installed.

CodeZilla uses Microsoft HTML Help, which requires that Microsoft Internet Explorer 3.02 or newer be installed.

Installation OverviewInstallation OverviewInstallation OverviewInstallation Overview

CodeZilla uses a standard Microsoft installation program called "Setup". It operates like other Microsoft installation programs. Run Setup and follow the on-screen instructions.

It is recommended that the defaults be used, so your system is similar to our test systems.

The installation process will install everything needed besides a MAS90 system.

ddddssssdddd bbbbuuuussssiiinnnneeeessssssss … · 2020. 11. 25. · windowswin dowsdows is a...

Documents