MAI COMPANY CONFIDENTIAL FIELD INFORMATION BULLETIN SERVICE GROUP(S): MINI MFG: BASIC FOUR NACS TYPE(S): N038 MFG. MODEL(S): ORIGIN CATEGORY: SOFTWARE DESC: PACKAGE *** TABLE OF CONTENTS AS OF 07/31/91 *** FIB 00001.ORIGIN Release 1.3B Software Announcement...................09/23/85 FIB 00002.ORIGIN and OMS update node..................................02/06/86 FIB 00003.Release 2.0A has a key check problem........................02/26/87 FIB 00004.Release 2.0A - four-tuple 0,12,500,0 (MPx) or ERROR 12 (2/3002/26/87 FIB 00005.Release 2.0A compact date fix...............................02/26/87 FIB 00006.ERROR 31 Rel 2.0A*21 on 2000 Rel 7.2A and 7.2B..............02/26/87 FIB 00007.MAI ORIGIN Version 2.0 Software Announcement................05/04/87 FIB 00008.Report line maintenance on 2000/3000........................09/17/87 FIB 00009.MAI.Origin 2.0A and INSTALLKEY on 8/9.6 [ WPS 413 ].........12/29/87 FIB 00010.Can't log-on to Origin 2.0A on 8/9.6 OS [ WPS 419 ]........02/12/88 FIB 00011.MAI ORIGIN 2.1A ADS/DATA Software Announcement [ WPSS 155 ].03/28/88 FIB 00012.MAI ORIGIN~ Support Grid [ WPSF 440 ].......................03/28/88 FIB 00013.Origin 2.1A Notes and Problems [ WPSF 454 ]................06/23/88 FIB 00014.ORIGIN 2.1A Helpful Hints [ WPSF 454-4 ]...................12/21/88 FIB 00015.ERROR 47 during add of a new input item [ WPSF 518 ]........02/08/89 FIB 00016.No data displayed on ORIGIN reports [ WPSF 517 ]............02/08/89 FIB 00017.Rel. 2.1A report function 'FNBLANK$' incorrect [ WPSF 515 ].02/08/89 FIB 00018.Error 47 on line 2720 in "ENGNNW" [ WPSF 454-5 ]............04/18/89 FIB 00019.Error 47 in ORIGIN 2.1A Generated Reports [ WPSF 454-6 ]...08/31/89 FIB 00020.Errs 26, 41, 47 - Letter Generation - ORIGIN 2.1A [ WPSF 45408/31/89 FIB 00021.Upgrading 2.0A IDDs to 2.1A [ WPSF 454-8 ].................08/31/89 FIB 00022.Error 42 in ORIGIN 2.1A Order Entry [ WPSF 454-9 ].........08/31/89 FIB 00023.Error.47 in Program RT.ENGNNR at line 8756 [ WPSF 454-10 ].08/31/89 FIB 00024.ORIGIN 2.1A Problems [ WPSF 454 A-11,12,13 ]...............10/11/90 FIB 00025.GENERAL ORIGIN NOTES..............................(Text Inco02/08/90 FIB 00026.ORIGIN 2.1B on GPx40, Notes & Cautions [ WPSF 620 R ]......10/11/90 FIB 00027.ORIGIN 2.1B ADS/Bus. DATA Software Announcement [ WPSS 176 11/19/90 FIB 00028.Known ORIGIN 2.1B Problems [ WPSF 664 ].....................11/30/90 FIB 00029.ORIGIN 2.1B*23 Reports don't Print with num Start/Stop Keys.11/30/90 FIB 00030.2.1B*23 - Erroneous Prompt after Start/Stop Key Used [ WPSF 02/06/91 FIB 00031.Err 47 using '?' in IDD Maintenance - ORIGIN 2.1B [ WPSF 6204/03/91 FIB 00032.Err 41 using IDD examine at 2.1B*23 [ WPSF 713 ]...........05/15/91 FIB 00033.Application Generator Shell Change..........................06/27/91 SOFTWARE-BASIC FOUR-ORIGIN--------------------------Table Of Contents Pg01 of 01 FIB 00001 09/23/85 *** ORIGIN Release 1.3B Software Announcement *** Version 1.3B ORIGIN Now Available For Distribution We are pleased to announce the availability of ORIGIN Version 1.3B. This release supersedes all previous versions of ORIGIN and includes many enhancements and corrections to known problems. This Version of ORIGIN is also the official carrier for ORIGIN support of the System 2000. To obtain a copy of ORIGIN Version 1.3B software, submit a copy of the ORIGIN Distribution Request Form to Software Distribution. This document describes the major enhancements, corrections, and the installation procedures for ORIGIN Version 1.3B. ORIGIN SOFTWARE ANNOUNCEMENT - Version 1.3B Table Of Contents 1.0 Enhancements and Corrections. 1.1 ORIGIN naming convention changed to eliminate use of special characters. 1.2 Small program generation option repaired. 1.3 Item rename repair. 1.4 Report and Query selector enhancements. 1.5 Automatic screen refresh on changed items. 1.6 Various input default repairs. 1.7 Enhanced date defaults. 1.8 Batch generation now operational. 1.9 Screen Editor display cleanup. 1.10 Intermittent IDD initialization failure corrected. 1.11 Expanded file relationship limitations as well as expanded related file fields. 2.0 Installation Procedures for First Time Users, 8000 Systems. 2.1 Installation of the ORIGIN R13B Tape. 2.2 Initializing the ORIGIN system and installing the installation code. 3.0 ORIGIN Version 1.3A to 1.3B Installation/Conversion Procedure, For 8000 Systems. 3.1 Installation of the ORIGIN R13B Tape. 3.2 Data File Conversion From Version 1.3A to 1.3B. 3.3 Initializing the ORIGIN system and installing the installation code. 4.0 Installation Procedures for First Time Users, 2000 Systems. 4.1 Installing ORIGIN (DSS, ADS). 4.2 Setting your working directory and prefix list. 5.0 Warnings and Cautions. 5.1 Concurrency of generated code. 5.2 Known difficulties. ORIGIN SOFTWARE ANNOUNCEMENT - Version 1.3B SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB001 Pg001 1.0 Enhancements and Corrections. This new release of ORIGIN Version 1.3B contains many repairs to the system's known and reported problems. There have also been many corrections made in this new release. For the sake of simplicity, however, only the significant repairs will be documented here. 1.1 ORIGIN Naming Convention Changed To Eliminate Use Of Special Characters. In previous ORIGIN releases, the programs of the system were all prefixed with a three character "+QK" designator, the documentation files were suffixed with the "DC?" designator, and the Data Dictionary files were all prefixed with the "AID" designator. ORIGIN Version 1.3B now changes those conventions to a more centralized naming technique that eliminates special characters. The following chart shows the new ORIGIN naming conventions. Pre-Version_1.3B________________Version_1.3B +QK ORI AID ORI DC? DC0 1.2 Small Program Generation Option Repaired. In previous ORIGIN release versions, when the small program option was selected at the time of code generation, the operator could be surprised by the resultant program not performing in the same manner as a fully generated version of the same parameters. This release of ORIGIN corrects that deficiency. ORIGIN Version 1.3B small programs now support the full functionality of the large program code generation technique. 1.3 Item Rename Repair. If an already defined and referenced data item were renamed in previous ORIGIN releases the where used references were not automatically updated at the same time. This release of ORIGIN repairs that deficiency as well. Now if a data item is renamed, all references to that data item's where used, and where referenced matricies are also automatically searched and updated at the same time the original data item's base record is modified. 1.4 Report and Query Selector Enhancements. Numerous problems have been reported and corrected concerning the Report and Query Selector functions of the ORIGIN system. Among those problems were: The start and stop key specifiers did not work as expected; not all items would be displayed on some selector or report screens; and the use of default options on Query programs did not always work correctly. All of these problems, and several others that are not documented in this software announcement, are corrected with the ORIGIN Version 1.3B. 1.5 Automatic Screen Refresh On Changed Items. When a data item is changed in an ORIGIN generated applications program, previous releases of ORIGIN would refresh display of SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB001 Pg002 the changed item only. This could lead to contradictory data being displayed to the screen when derived data items would display the old data values even though the variable contents had been updated in memory. This new release of ORIGIN will refresh the entire screen when a single data item is changed. 1.6 Various Input Default Repairs. There had been several problems with calculated default values not being rounded to smaller precisions correctly via numeric mask rounding. An example of this would be a default value that is calculated as the result of previous input of a higher pre- cision level than the input with the calculated default value. This problem has been corrected with ORIGIN Version 1.3B. In addition to this, input masking of minimum and maximum values on the order of 99.99999999 did not perform as expected either. These, and several other input anomalies, have been addressed and corrected with the new ORIGIN Version 1.3B. 1.7 Enhanced Date Defaults. Date inputs into ORIGIN generated applications programs now allow for three different types of default input: system date, a default programmatic date or a blank filled date. Previous ORIGIN releases did not allow for blank filled date entries at all, forcing operators to input some sort of valid date entry before they could proceed onto the next input. This enhancement now eliminates that restriction. 1.8 Batch Generation Now Operational. Previous release versions of ORIGIN contained an option to batch generate systems and sub systems. Unfortunately this option was not operational. ORIGIN Version 1.3B now supports the batch generation feature of the system. 1.9 Screen Editor Display Cleanup. There were several annoying and intermittent problems with the applications and report screen editor routines. The displayed screens could become corrupted by a sequence of complicated block moves or deletes. Those problems were not catastrophic to the ORIGIN system since leaving and re-entering the screen editor would reconstruct the screens correctly. These problems have also been corrected with this release of ORIGIN. 1.10 Intermittent IDD Initialization Failure Corrected. There was a sporatic failure that could occur during the initialization phase of the work file set-up processes when being initialized from the Integrated Data Dictionary. The initialization failure has been diagnosed and corrected with this release of ORIGIN. 1.11 Expanded File Relationships As Well As Expanded Related File Fields. There were two related file limitations with previous ORIGIN releases that have been expanded with this release. The total number of simultaneous file relationships in a particular applications program has been increased from 11 to 49, greatly increasing the power of the applications system. The second limitation was with the total number of transferable fields from SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB001 Pg003 a related file. In ORIGIN the maximum number of fields allowable within a given file structure is 160 fields. However, when a file is referenced as a related file, there was a maximum number of fields having been specified at 90. This discrepancy of maximums could create situations where a file with more than 90 fields could not be effectively referenced as a related file because only the first 90 fields would be transfered by a related file read. This release of ORIGIN now increases the related file field maximum from 90 to 160 fields to be consistent with the primary file maximum. 2.0 Installation Procedures For First Time Users, 8000 Systems. 2.1 Installation of the ORIGIN R13B tape. ORIGIN tapes are very simple to install and require no special procedures or training. The following checklist is all that is necessary to successfully install ORIGIN onto an 8000 system for the first time. 2.1.1 Log-on to the 8000 system. 2.1.2 Place the terminal into command execution mode so that exclamation point prompt appears on the screen. ("!") 2.1.3 Set the user prefix to '.ORIGIN.R13B.DATA., .ORIGIN.R13B.' by executing the following command line. !PREFIX .ORIGIN.R13B.DATA.,.ORIGIN.R13B. 2.1.4 Execute the tape utility !SAVERESTORE and select the option to restore files from tape. 2.1.5 Carriage return default entries into the primary restore set-up screen and respond to the 'Entries Correct?' prompt with a "Y". 2.1.6 In the secondary file specifier screen input an ampersand ('&') as the file specifier. (This is the 8000 code for a 'wildcard' and will prompt the system to restore all files from the tape to the current default primary family.) 2.1.7 Input a carriage return for the second file specifier line. (A blank line in the file specifier screen of SAVERESTORE indicates the termination of file specification.) From this point on the restore process from tape to disk is automatic; no further inputs are required. 2.2 Initializing the ORIGIN system and installing the installation code. Once ORIGIN Version 1.3B has been copied down to disk the system must be initialized before it can be accessed. The first step in ORIGIN initialization is to run the installation procedure "UPDATE". The full name of the Update procedure is: (family).ORIGIN.R13B.UPDATE The user's FAMILY name, of course, varies from site to site, and is indicated in this document with the lower case, underlined SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB001 Pg004 and parenthesized FAMILY name displayed above. Before "UPDATE" can be run however, the user PREFIX must be set to the ORIGIN program node. !PREFIX (family).ORIGIN.R13B. After the PREFIX has been set to the ORIGIN node then simply RUN "UPDATE" from BASIC. The following screen will appear. ORIGIN 1.3B UPDATE ----------------------------------------------------------------------- ENTER THE NODE OF YOUR CURRENT ORIGIN SYSTEM INCLUDING FAMILY NAME, 'CR' IF THIS IS A NEW INSTALLATION : ____________ The ORIGIN 1.3B Update procedure is designed to update users from previous ORIGIN releases as well as to install ORIGIN for first time users. If this is a first time installation then enter 'CR'. Once the 'CR' has been entered no other prompts are required to complete first time installation. The update procedure will automatically install the ORIGIN utility set into the systems SYSTEM PREFIX node. While the ORIGIN update procedure is installing the ORIGIN Utilities it will display the following message: INSTALL STANDALONE UTILITIES IN SYSTEM NODE (family).Rxxxx.SYS. where the FAMILY and the Release Node will vary from system to system and are indicated above by the underlining. "UPDATE" will then display a series of program names that it is copying into the user's SYSTEM node. The file names that it is copying is kept in the file named (family).ORIGIN.R13B.STANDALONELIST, but is listed below for your reference. .ORIGIN.R13B.ORI6H .ORIGIN.R13B.ORIENQ .ORIGIN.R13B.ORIPCK .ORIGIN.R13B.ORIAD1 .ORIGIN.R13B.ORIER2 .ORIGIN.R13B.ORIPOW .ORIGIN.R13B.ORIAD2 .ORIGIN.R13B.ORIFSL .ORIGIN.R13B.ORIPRE .ORIGIN.R13B.ORICDN .ORIGIN.R13B.ORIHDR .ORIGIN.R13B.ORIRHD .ORIGIN.R13B.ORICJ1 .ORIGIN.R13B.ORIJC1 .ORIGIN.R13B.ORIROL .ORIGIN.R13B.ORICJ2 .ORIGIN.R13B.ORIJC2 .ORIGIN.R13B.ORISIN .ORIGIN.R13B.ORICJ3 .ORIGIN.R13B.ORIJC3 .ORIGIN.R13B.ORIT12 .ORIGIN.R13B.ORICMD .ORIGIN.R13B.ORILRE .ORIGIN.R13B.ORITC9 .ORIGIN.R13B.ORICOS .ORIGIN.R13B.ORIMES .ORIGIN.R13B.ORITRF .ORIGIN.R13B.ORICSL .ORIGIN.R13B.ORIMFL .ORIGIN.R13B.ORITXT .ORIGIN.R13B.ORIDSI .ORIGIN.R13B.ORIMSK .ORIGIN.R13B.ORIUPD .ORIGIN.R13B.ORIDW1 .ORIGIN.R13B.ORINFS .ORIGIN.R13B.ORIUPK .ORIGIN.R13B.ORIDW2 .ORIGIN.R13B.ORINRO .ORIGIN.R13B.ORIUSR .ORIGIN.R13B.ORIDW3 When this process is completed the ORIGIN update program will display the message : ORIGIN UPDATE COMPLETE and terminate execution. The user PREFIX should then be reset to the following PREFIX. !PREFIX (family).ORIGIN.R13B.DATA.,.ORIGIN.R13B. Once the PREFIX has been set ORIGIN can then be run. However, the ORIGIN Installation Code will need to be installed onto the SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB001 Pg005 user system. The installation procedure for ORIGIN is automatically executed by running ORIGIN. At this point the ORIGIN system will display the System Serial Numer (SSN) to the screen and prompt the operator to input the installation code. The installation code should be written on the tape label of the ORIGIN Version 1.3B tape. Once the installation code has been input correctly into the ORIGIN system it will not need to be input again. The installation code is only required upon user execution for the first time. Your ORIGIN Version 1.3B system is now fully installed and ready for use. ***** N-O-T-E ***** AN INSTALLATION CODE CAN ALSO BE OBTAINED BY CALLING MAI BASIC FOUR, SOFTWARE DISTRIBUTION, (714) 730-2548, AND GIVING THE COMPANY NAME AND SYSTEM SERIAL NUMBER TO THE PARTY. 3.0 ORIGIN Version 1.3A to 1.3B Installation/Conversion Procedure For 8000 Systems. 3.1 Installation of the ORIGIN R13B tape. ORIGIN tapes are very simple to install and require no special procedures or training. The following checklist is all that is necessary to sucessfully install ORIGIN onto an 8000 system for the first time. 3.1.1 Log-on to the 8000 system. 3.1.2 Place the terminal into command execution mode so that the exclamation point prompt appears on the screen. ("!") 3.1.3 Set the user prefix to '.ORIGIN.R13B.DATA., .ORIGIN.R13B.' by executing the following command line: !PREFIX .ORIGIN.R13B.DATA.,.ORIGIN.R13B. 3.1.4 Execute the tape utility !SAVERESTORE and select the option to restore files from tape. 3.1.5 Carriage return default entries into the primary restore set-up screen and respond to the 'Entries Correct?' prompt with a "Y". 3.1.6 In the secondary file specifier screen input an ampersand ('&') as the file specifier. (This is the 8000 code for a 'wildcard' and will prompt the system to restore all files from the tape to the current default primary family.) 3.1.7 Input a carriage return for the second file specifier line. (A blank line in the file specifier screen of SAVERESTORE indicates the termination of file specification.) From this point on the restore process from tape to disk is automatic; no further inputs are required. 3.2 Data File Conversion From Version 1.3A to 1.3B. Once ORIGIN Version 1.3B has been copied down to disk the files must be converted before it can be accessed. The first step in SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB001 Pg006 ORIGIN data conversion is to run the conversion procedure "UPDATE". The full name of the update procedure is: (family).ORIGIN.R13B.UPDATE The user's FAMILY name, of course, varies from site to site, and is indicated in this document with the lower case, underlined and parenthesized FAMILY Name displayed above. Before "UPDATE" can be run however, the user PREFIX must be set to the ORIGIN program node. !PREFIX (family).ORIGIN.R13B. After the PREFIX has been set to the ORIGIN node then simply RUN "UPDATE" from BASIC. The following screen will appear. ORIGIN 1.3B UPDATE ---------------------------------------------------------------- ENTER THE NODE OF YOUR CURRENT ORIGIN SYSTEM INCLUDING FAMILY NAME, 'CR' IF THIS IS A NEW INSTALLATION : ____________ The ORIGIN 1.3B Update procedure is designed to update users from previous ORIGIN releases as well as to install ORIGIN for first time users. Since this is a conversion and not an installation it will be necessary to input the previous ORIGIN node at this point: (family).ORIGIN.R13A. Once the previous ORIGIN node has been input the utility will automatically convert all of the old ORIGIN Data Files over from the 1.3A naming convention, (+QK), to the 1.3B naming convention, (ORI). The file names converted automatically by the ORIGIN Update program are contained in the file (family).ORIGIN.R13B.DATALIST and can be listed. However, they are listed below for your reference. ORIGIN R13A NAME --> ORIGIN R13B NAME ==========================---------------======================== .ORIGIN.R13A.DATA.AID4D1 --> .ORIGIN.R13B.DATA.ORI4D1 .ORIGIN.R13A.DATA.AID4D2 --> .ORIGIN.R13B.DATA.ORI4D2 .ORIGIN.R13A.DATA.AID4D3 --> .ORIGIN.R13B.DATA.ORI4D3 .ORIGIN.R13A.DATA.AID4D4 --> .ORIGIN.R13B.DATA.ORI4D4 .ORIGIN.R13A.DATA.AID4D5 --> .ORIGIN.R13B.DATA.ORI4D5 .ORIGIN.R13A.DATA.%6+QKDS1 --> .ORIGIN.R13B.DATA.ORIDS1 .ORIGIN.R13A.DATA.%6+QKDS2 --> .ORIGIN.R13B.DATA.ORIDS2 .ORIGIN.R13A.DATA.%6+QKPDF --> .ORIGIN.R13B.DATA.ORIPDF .ORIGIN.R13A.DATA.%6+QKPF2 --> .ORIGIN.R13B.DATA.ORIPF2 .ORIGIN.R13A.DATA.%6+QKPS2 --> .ORIGIN.R13B.DATA.ORIPS2 .ORIGIN.R13A.DATA.%6+QKPS3 --> .ORIGIN.R13B.DATA.ORIPS3 .ORIGIN.R13A.DATA.%6+QKPS4 --> .ORIGIN.R13B.DATA.ORIPS4 .ORIGIN.R13A.DATA.%6+QKPS5 --> .ORIGIN.R13B.DATA.ORIPS5 .ORIGIN.R13A.DATA.%6+QKPS6 --> .ORIGIN.R13B.DATA.ORIPS6 .ORIGIN.R13A.DATA.%6+QKPS7 --> .ORIGIN.R13B.DATA.ORIPS7 .ORIGIN.R13A.DATA.%6+QKQF1 --> .ORIGIN.R13B.DATA.ORIQF1 .ORIGIN.R13A.DATA.%6+QKQF2 --> .ORIGIN.R13B.DATA.ORIQF2 .ORIGIN.R13A.DATA.%6+QKQFL --> .ORIGIN.R13B.DATA.ORIQFL .ORIGIN.R13A.DATA.%6+QKQP1 --> .ORIGIN.R13B.DATA.ORIQP1 .ORIGIN.R13A.DATA.%6+QKQS1 --> .ORIGIN.R13B.DATA.ORIQS1 .ORIGIN.R13A.DATA.%6+QKQS2 --> .ORIGIN.R13B.DATA.ORIQS2 .ORIGIN.R13A.DATA.%6+QKQST --> .ORIGIN.R13B.DATA.ORIQST SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB001 Pg007 .ORIGIN.R13A.DATA.%6+QKUFL --> .ORIGIN.R13B.DATA.ORIUFL .ORIGIN.R13A.DATA.%6+QKUST --> .ORIGIN.R13B.DATA.ORIUST .ORIGIN.R13A.DATA.%6+QKV01 --> .ORIGIN.R13B.DATA.ORIV01 .ORIGIN.R13A.DATA.%6+QKVDC --> .ORIGIN.R13B.DATA.ORIVDC As the new Data Files are being created and loaded with data the Update procedure will display the file names to the screen. When the Data File re-naming has completed the update procedure will automatically install the ORIGIN utility set into the systems SYSTEM PREFIX node. While the ORIGIN update procedure is installing the ORIGIN utilities it will display the following message: INSTALL STANDALONE UTILITIES IN SYSTEM NODE (family).Rxxxx.SYS. where the FAMILY and the release node will vary from system to system and are indicated above by the underlining. "UPDATE" will then display a series of program names that it is copying into the user's SYSTEM node. The file names that it is copying is kept in the file named (family).ORIGIN.R13B.STANDALONELIST but is listed below for your reference. .ORIGIN.R13B.ORI6H .ORIGIN.R13B.ORIENQ .ORIGIN.R13B.ORIPCK .ORIGIN.R13B.ORIAD1 .ORIGIN.R13B.ORIER2 .ORIGIN.R13B.ORIPOW .ORIGIN.R13B.ORIAD2 .ORIGIN.R13B.ORIFSL .ORIGIN.R13B.ORIPRE .ORIGIN.R13B.ORICDN .ORIGIN.R13B.ORIHDR .ORIGIN.R13B.ORIRHD .ORIGIN.R13B.ORICJ1 .ORIGIN.R13B.ORIJC1 .ORIGIN.R13B.ORIROL .ORIGIN.R13B.ORICJ2 .ORIGIN.R13B.ORIJC2 .ORIGIN.R13B.ORISIN .ORIGIN.R13B.ORICJ3 .ORIGIN.R13B.ORIJC3 .ORIGIN.R13B.ORIT12 .ORIGIN.R13B.ORICMD .ORIGIN.R13B.ORILRE .ORIGIN.R13B.ORITC9 .ORIGIN.R13B.ORICOS .ORIGIN.R13B.ORIMES .ORIGIN.R13B.ORITRF .ORIGIN.R13B.ORICSL .ORIGIN.R13B.ORIMFL .ORIGIN.R13B.ORITXT .ORIGIN.R13B.ORIDSI .ORIGIN.R13B.ORIMSK .ORIGIN.R13B.ORIUPD .ORIGIN.R13B.ORIDW1 .ORIGIN.R13B.ORINFS .ORIGIN.R13B.ORIUPK .ORIGIN.R13B.ORIDW2 .ORIGIN.R13B.ORINRO .ORIGIN.R13B.ORIUSR .ORIGIN.R13B.ORIDW3 When this process has completed the screen will clear and the following prompt will appear at the bottom of the screen: CR=DATA DICTIONARY FILES, CTL-I=TECHNICAL DOCUMENTATION FILE, CTL-IV=EXIT A carriage return at this point will proceed onto the ORIGIN Data Dictionary file conversion processes. Enter the carriage return at this point. The next screen prompt will be: ENTER THE NODE OF YOUR 1.3A DATA DICTIONARY FILES : _______________ At this point the operator would input the native node of the user's Data Dictionary files. Normally, this would be: (family).ORIGIN.R13A. And the next prompt will appear: ENTER THE NODE OF YOUR 1.3B DATA DICTIONARY FILES : _______________ The operator should respond with: SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB001 Pg008 (family).ORIGIN.R13B. The last and final prompt of the Data Dictionary conversion process is the verification prompt. 'CR' TO PROCEED, CTL-IV TO EXIT : _ The input of a carriage return at this point will proceed onto the rename and data convert processes of the ORIGIN Data Dictionary files. These files are the files that had been prefixed with the "AID" prefix on Version 1.3A and are now prefixed with the "ORI" prefix on Version 1.3B. The file names follow for your reference. .ORIGIN.R13A.DATA.AID4D1 --> .ORIGIN.R13B.DATA.ORI4D1 .ORIGIN.R13A.DATA.AID4D2 --> .ORIGIN.R13B.DATA.ORI4D2 .ORIGIN.R13A.DATA.AID4D3 --> .ORIGIN.R13B.DATA.ORI4D3 .ORIGIN.R13A.DATA.AID4D4 --> .ORIGIN.R13B.DATA.ORI4D4 .ORIGIN.R13A.DATA.AID4D5 --> .ORIGIN.R13B.DATA.ORI4D5 When the Data Dictionary files have completed the conversion process the screen will clear and display the entry prompt again. CR=DATA DICTIONARY FILES, CTL-I=TECHNICAL DOCUMENTATION FILES, CTL-IV=EXIT At this point it is desirable to input a Motor Bar I to proceed on with the Documentation Files conversion. The next three prompts will appear in sequence. ENTER THE NODE OF YOUR 1.3A TECH. DOC. FILE : _______________ ENTER THE NODE OF YOUR 1.3B TECH. DOC. FILE : _______________ ENTER YOUR PROJECT CODE : ___ The operator should be aware of the specific nodes and project codes in use by the installation site. For example, the first two prompts should be responded to thusly: (family).OLDNODEA.OLDNODEB... - and - (family).NEWNODEA.NEWNODEB... After the old and new nodes have been input the project code must then be input. This is the same project codes as were used in the creation of the systems generated with ORIGIN under Version 1.3A, and needless to say, are not only site specific, but program system specific as well. When an active project code has been input the program will proceed on with the documentation file conversion process and will rename the file previously suffixed with the "DC?" sequence to the new suffix of "DC0". When this step has completed the program will repeat the entry prompt of: CR=DATA DICTIONARY FILES, CTL-I=TECHNICAL DOCUMENTATION FILES, CTL-IV=EXIT and the technical documentation file conversion steps will need to be repeated for each project code of the system. Upon entry SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB001 Pg009 of a Motor Bar IV code (CTL-IV) the program will terminate operation and display the following sign-off. ORIGIN UPDATE COMPLETE This completes the ORIGIN Version 1.3B conversion process from Version 1.3A to 1.3B. ***** N-O-T-E ***** The program that actually performs the Data Dictionary and Technical Documentation files conversion is named "ORIGIN.R13B.ORIA2B" and can be run directly. Therefore, if an operator does not include all of the project codes at the time of the initial conversion the program can be run again at a latter time against the specific project codes in question. 3.3 Initializing the ORIGIN System and Installing the Installation Code. Once the conversion process has been completed ORIGIN can then be run. However, the ORIGIN installation code will need to be installed onto the user system. The installation procedure for ORIGIN is automatically executed by running ORIGIN. At this point the ORIGIN system will display the System Serial Number (SSN) to the screen and prompt the operator to input the installation code. The installation code should be written on the tape label of the ORIGIN Version 1.3B tape. Once the installation code has been input correctly into the ORIGIN system it will not need to be input again. The installation code is only required upon user execution for the first time. The ORIGIN Version 1.3B system is now fully installed and ready for use. ***** N-O-T-E ***** AN INSTALLATION CODE CAN ALSO BE OBTAINED BY CALLING MAI BASIC FOUR, SOFTWARE DISTRIBUTION, (714) 730-2548, AND GIVING THE COMPANY NAME AND SYSTEM SERIAL NUMBER TO THE PARTY. 4.0 Installation Instructions For 2000 Systems. An understanding of the 2000 utilities and commands is helpful for installation. As a supplement to these instructions refer to the MAI 2000 Users Guide (BFISD 6200), Part 1 of 1, Section 9, Utilities and Part 2 of 2, Section 10, Command Language. Requirements o 2000 OS Level 7.1A*34 or higher o 6 or more megabytes of disk space o Prefix list must contain the following directories: 1) user defined directory 2) /origin/r13b/data 3) /origin/r13b Installation SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB001 Pg010 Setting up ORIGIN for the first time involves two steps. One, installing the DSS and ADS savesets, and two, setting the working directory and prefix list. ORIGIN can then be executed by entering BASIC with a start size of 128 Pages. eg. ADMIN>basic s=128 -nr pgm=ORIGIN 4.1 Installing ORIGIN (DSS, ADS). Install the savesets DSS and ADS from the ORIGIN 1.3B tape using the install command. eg. ADMIN>install cs DSS ADS During the installation you will be prompted for your installation key: "Input 8-character installation key (cr=no change): _" If the installation keys for DSS and ADS are not readily available to continue. The key can be easily installed after the files on tape have been restored to disk. Upon completion of restoring the files from tape run the following program from basic : run "/origin/r13b/UPDATE" The following prompt will appear: "Enter ORIGIN disk name (CR if none):" If you are installing onto drive 0 carriage return. Otherwise, enter the directory name of drive 1. The UPDATE program will then prompt: "Is this a new installation ?" YES - Will rename the ORIGIN data files from: "/origin/r13b/data/new" - to - "/origin/r13b/data" NO - Will prompt with the following: "Save data files from current ORIGIN system ?" YES - Will prevent the program from updating over your current ORIGIN data files. NO - Will first erase the current ORIGIN data files, then rename the "new" data files as described earlier. The "UPDATE program will then prompt with: "Install stand alone ORIGIN utilities ?" YES - Will enable the user to run ORIGIN from one directory. The program will prompt with the following: "Enter directory for stand alone programs CR=/std" SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB001 Pg011 Upon entering the directory name the "UPDATE" program will copy the program and data files contained in the filelist "/origin/r13b/STANDALONELIST" into the specified directory. NO - Update is complete. If the installation key has not yet been installed, then it will be necessary to call Software Distribution at (714) 730-2548, and relay the System Serial Number and the company name to the contact in order to obtain the installation key. Once the installation key has been obtained it can be installed by executing the following commands. eg. ADMIN>install_key /etc/level/DSS ADMIN>install_key /etc/level/ADS 4.2 Setting the Working Directory and Prefix List. The ORIGIN prefix list contains two directories: o "/origin/r13b" - Program Files. o "/origin/ri3b/data" - Data Files. These directories can be added manually in command mode, through the add command, or in basic console mode, through the PREFIX directive each time you run ORIGIN. They can also be added automatically by adding a command file to an operator's initial program. Manual Add: The following details how to add the ORIGIN prefix: 1. Set the directory to the desired user prefix. ie. ADMIN>cd /usr/name 2. Add the ORIGIN prefix to the list. o From command mode use the add command. eg. ADMIN>ad /usr/name /origin/r13b/data /origin/r13b o From BASIC use the PREFIX command. eg. >PREFIX "/usr/name /origin/r13b/data /origin/r13b" Automatic Add: The following steps detail how to set up an operator with a command file that automatically adds the ORIGIN prefix and then executes "ORIGIN". A. Create an Operator. (If the operator already exists, skip to step 'B') 1. Log onto the 2000 as ADMIN. 2. From command mode enter ADMIN>oprinfo 3. Choose option 1, Add an operator. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB001 Pg012 4. Enter the operator name and password as prompted. B. Create a Command File. 1. Create a ved file under the new operator's directrory. eg. ved /usr/name/startorigin 2. Enter in the data as shown in the following example: (example of a command file for the operator "name") ---------------------------------------------------------------- _ #:1 \default /usr/name/startorigin NEW FILE _ _ _ _ ad /origin/r13b/data /origin/r13b _ _ basic s=128 -nr pgm=ORIGIN _ ---------------------------------------------------------------- *See the MAI 2000 Users Guide (BFISD 6200), Part 2 of 2, Section 10 for more information on ved. 3. In command mode, make this ved file executable. This can be done useing the filemodes command. eg. ADMIN>filemodes +x +x /usr/name/startorigin C. Modify the operator. 1. From command mode enter: ADMIN>oprinfo 2. Choose option 2, Modify an operator. 3. Enter the operator name. 4. Choose option 4, Initial program. 5. Choose option 4, Other. 6. Enter the command file nane. "/bin/command,/usr/name/startorigin" ... for no change: /bin/command,/usr/name/startorigin This completes the ORIGIN automatic execution sequence. 5.0 Warnings And Cautions. ORIGIN is a powerful and very well designed tool that MAI is proud to offer along with our family of other outstanding products. It is also, however, a very complex and intricate system. Anything of high complexity will have occasional difficulties. This section is intended to warn our field systems personnel of known difficulties in advance of installation. 5.1 Concurrency Of Generated Code. ORIGIN generated systems call standardized sub-routines to perform basic and redundant operations. It is for this reason SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB001 Pg013 that the file "STANDALONELIST" is included with the ORIGIN system so that the system's designer can include these shared routines along with generated code when the system is installed at a customer or end user location. If the installation is going to support both 1.3A and 1.3B generated systems then it will be necessary to save the 1.3A "STANDALONELIST" and associated 1.3A files so that code generated under ORIGIN Version 1.3A will continue to run. THIS IS VERY IMPORTANT! None of the generated systems will function without the subroutines. If the installation has enough free disk space, and will be supporting both 1.3A and 1.3B generated systems, it is recommended that both versions be left active on the systems. 5.2 Known Difficulties. Conditioning on capital "X" problem. In an executive query, or a report program, if an attempt is made to condition upon a capital "X" ORIGIN will accept the input and the generator will generate the code. However, the condition will not perform when run in the generated program. If this feature is absolutely required by a particular application, then it is suggested that the generated code be modified to correctly handle the condition. Standard report output to Indexed, Spread Sheets, or Graphics does not output to the specified option, but error's instead. There is no simple work-around for this problem at this time. It is suggested that these output options simply not be used with this release of ORIGIN. ORIGINATOR: MBF SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB001 Pg014 FIB 00002 02/06/86 *** ORIGIN and OMS update node *** In an effort to provide fixes for problems reported in OMS and ORIGIN, an update node will be provided, between releases, to the field. The update node contains programs with the fixes to particular problems. This node is restored onto the system replacing the old files. This method of fixing problems will begin with OMS levels 8.3.1/7.3.0 and ORIGIN 1.3B (MPx and 2000). Below are the installation instructions for the update node. Accompanying the update node will be a serial file named 'REVISION' on MPx and 'revision' on the 2000. This file contains the history of what was fixed with this release of the update node. It can be submitted directly to the system spooler to obtain hard copy. The update node is first restored to the branch/dealer/subsidiary/distributor system. This is explained in the domestic/international installation section. A tape is then made for the customer. This process is explained in the customer installation section. Domestic Installation (OMS and ORIGIN) STEP 1: Restore OMS or ORIGIN update node to disk. The files on the tape may be prefaced by ".UPDATE." on the MPx and "/update/" on the 2000. Restore the files to the node/directory specified on the tape. MPx: Use SAVERESTORE to restore the update node to disk. 2000: Use 'mcsrestore' to the update node to disk. International Installation (OMS only) For international installation, the OMS update node must be implanted first. To do this, the update files must be restored into the OMSBASE node on their respective systems. These files then can be implanted individually into the UPDATE node. STEP 1: Rename the files to be replaced (in the OMSBASE node) to another node. The files that need to be renamed can be found by using the revision file. STEP 2: Restore the OMS update node to disk. The files on the tape may be prefaced by ".UPDATE." on the MPX and "/update/" on the 2000. Restore the files to the node/directory specified on the tape. MPx: Use SAVERESTORE to restore the update node to disk. 2000: Use 'mcsrestore' to restore the update node to disk. STEP 3: Copy files into the ".OMSBASE." node on the MPx and "/omsbase/" on the 2000. STEP 4: Implant the programs. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB002 Pg001 MPx: Use the implanter IMI to implant the messages. Create a filelist using the 'EDIT' utility. Then use the filelist to implant the files. To use the filelist, use '#.@filelist' at the 'MESSAGE SPECIFIER PROMPT'. Use the .UPDATE.OMS. node as the destination node. 2000: Use the implanter 'mplant' to implant the messages. Use the /update/oms directory as the destination node. Once, the programs have been implanted, the update node is ready for release to customers. For installation at the customer site, please follow the steps in the customer installation section. International Installation (ORIGIN only) STEP 1: Restore the ORIGIN update node to disk. The files on the tape may be prefaced by ".UPDATE." on the MPx and "/update/" on the 2000. Restore the files to the node/directory specified on the tape. MPx: Use SAVERESTORE to restore the update node to disk. 2000: Use 'mcsrestore' to restore the update node to disk. To install ORIGIN at the customer site, follow the instructions below. To install at customer site STEP 1: Make a tape containing the update files and change the prefix from .UPDATE.OMS. (.UPDATE.ORIGIN.) to .OMS. (.ORIGIN.) on the MPx and /update/oms/ (/update/origin/) to /oms/ (/origin/) on the 2000. STEP 2: Rename the files to be replaced to another node. The files that need to be renamed can be found by using the revision file. STEP 3: Restore the node to disk. MPx: Use SAVERESTORE to restore the update node to disk. 2000: Use 'mcsrestore' to restore the update node to disk. After the update node is released to the support locations and verified, it will be incorporated into the product release distributed by Software Distribution. Notification of effectivity will be issued via a Field Bulletin also documenting the changes that have been implemented. ORIGINATOR: MBF SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB002 Pg002 FIB 00003 02/26/87 *** Release 2.0A has a key check problem *** MAI ORIGIN 2.0A on the 2000 and the MPx will not allow you to modify non-key items if the item number contains some of the same characters as the primary key items. For example, if your primary was the combination of items 1+2, you would not be able to modify items 10 or 20 because they contain the characters "1" and "2". To correct this problem, insert ",3" in statement 5170 of program "IDD4AB": OLD: 5170 IF POS(I0$(21,3)=M2$)>0 ... NEW: 5170 IF POS(I0$(21,3)=M2$,3)>0 ... This program change will be included in the next release of ORIGIN. ORIGINATOR: T. TIANGCO SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB003 Pg001 FIB 00004 02/26/87 *** Release 2.0A - four-tuple 0,12,500,0 (MPx) or ERROR 12 (2/3000) *** A four-tuple error 0,12,500,0 may occur on the MPx and an error 12 on the 2000 when CTL-I is entered to create a new relationship. To correct this problem, add statement 105 to program "ORIFRM". 105 U=UNT; OPEN(U)"ORILGF"; READ(U,KEY=FID(0),DOM=8960)U2$,*,*,U3$; CLOSE(U) This program change will be included in the next release of ORIGIN. ORIGINATOR: T. TIANGCO SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB004 Pg001 FIB 00005 02/26/87 *** Release 2.0A compact date fix *** There are 2 problems that can occur with MAI ORIGIN~ 2.0A and compact dates. PROBLEM 1: An error 43 will occur in MAI ORIGIN~ 2.0A *21 generated programs on the 2000 that access ASG data files and use packed dates. SOLUTION: NOTE - THIS CHANGE IS NOT NECESSARY IF YOU ARE NOT ACCESSING ASG DATA FILES WITH COMPACT DATES ! If you are using Report Generator : Change the "-1" to "-129" in statement 107 of program "ORIRP7". OLD: 107 DEF FND30$(X1$)=STR((ASC(X1$)-1)*(POS(" "<>X1$)):"00") NEW: 107 DEF FND30$(X1$)=STR((ASC(X1$)-129)*(POS(" "<>X1$)):"00") If you are using Program Generator : Changed the "-1" to "-129" in statements 107 and 110 in program "ORI6". You must regenerate your report for these changes to take effect. If you do not want to regenerate, you must make the same program changes to your generated program. PROBLEM 2: Records that contain pack dates can not be deleted in MAI ORIGIN~ 2.0A on BOTH MPx and SPx systems in Application Generator programs. SOLUTION: Replace all occurances of "X1$" with "XX$" in statement 107 of program "ORI6" and regenerate your program. OLD: 107 DEF FND30$(X1$)=STR((ASC(X1$)-129)*(POS(" "<>X1$)):"00") NEW: 107 DEF FND30$(XX$)=STR((ASC(XX$)-129)*(POS(" "<>XX$)):"00") NOTE - The variable "XX$" may be changed to a different variable name in the next release of ORIGIN. Both of these program changes will be included in the next release of ORIGIN. ORIGINATOR: T. TIANGCO SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB005 Pg001 FIB 00006 02/26/87 *** ERROR 31 Rel 2.0A*21 on 2000 Rel 7.2A and 7.2B *** An error 31 can occur in ORIGIN 2.0A *21 on the 2000 levels 7.2A and 7.2B in program "READFILE". This is caused by a problem in BASIC with the CALL routine on OS levels 7.2A and 7.2B. The data area used by the variables that are passed in a CALL is not cleared when the variables are modified. The following program changes will alleviate the error 31's in the ORIGIN program 'READFILE'. LOAD "READFILE" o Modify statement 30: OLD 30 ENTER TYPE$, RETRN$ NEW 30 ENTER TYPE$, RTRN$ o Append to statement 40: OLD 40 RETRN$="" NEW 40 RETRN$="", RTRN$="" o Added Statement 9015: 9015 LET RTRN$=RETRN$ SAVE the program This workaround will be implemented in the next release of ORIGIN. ORIGINATOR: T. TIANGCO SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB006 Pg001 FIB 00007 05/04/87 *** MAI ORIGIN Version 2.0 Software Announcement *** MAI ORIGIN~ Version 2.0 is now available for distribution. TABLE OF CONTENTS 1.0 OVERVIEW 2.0 REQUIREMENTS 3.0 NEW FEATURES AND ENHANCEMENTS 3.1 INTEGRATED DATA DICTIONARY 3.1.1 Decoupled Integrated Data Dictionary 3.1.2 New Item Types 3.1.3 Derived Items 3.1.4 Rules of Recognition 3.1.5 View Maintenance 3.1.6 Data Impact Report 3.2 Decision Support 3.2.1 Enhanced Output Device Interfaces 3.2.2 Multi-Item Print Sequence Now Allowed 3.2.3 Sub-totaling Allowed in Executive Query 3.2.4 Conditioning Between Items in User Conditions 3.2.5 Arithmetic Expressions Allowed at Total Time in a Standard Report. 3.2.6 Non-Total Items Allowed in Total Area of Report 3.2.7 Page Breaks at Each Level of Breaking 3.2.8 Override of Mask Verification During Report Line Maintenance 3.3 Application Generator 3.3.1 Changed 'QUERY BY EXAMPLE' Exit Location 3.3.2 Numeric Input Prompts Now Use Numeric Mask 3.3.3 Allow Change of Screen for Input Prompts 3.3.4 Creation of Derived Items During Screen Maintenance 3.3.5 Enhanced User Interface of File Relationships 3.4 System Administrator Utilities 3.4.1 Select User-Defined Ending 3.4.2 Maintain ORIGIN System Parameters 3.4.3 Language Translation Menu 3.4.5 Maintain Data Handling Files 3.5 Miscellaneous Enhancements 3.5.1 Easy Access Menus 4.0 INSTALLATION AND UPGRADE PROCEDURES 4.1 Installations/Upgrades on the MPx SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB007 Pg001 4.2 Installations/Upgrades on the 2000 5.0 HELPFUL HINTS 5.1 General 5.2 Integrated Data Dictionary 5.3 Application Generator 5.4 Report Generator 6.0 WARNINGS AND CAUTIONS 6.1 General 6.2 Integrated Data Dictionary 6.3 Application Generator 6.4 Report Generator [ MAI ORIGIN~ Version 2.0 Software Announcement] 1.0 OVERVIEW ] This release adds many new enhancements and features to MAI ORIGIN~. It also corrects many of the bugs reported on previous versions. The improvements to ORIGIN have made it easier to use and learn. There have been substantial improvements to the Data Dictionary and to the creation process of File Relationships and Derived Items. This release also integrates products in the MAI OFFICE~ package such as, MAI Business MATH~, and Business GRAPH~. 2.0 REQUIREMENTS The same amount of disk space is required for a system installed with just the Decision Support System (DSS) as a system installed with both the Application Development System (ADS) and DSS. This is because both ADS and DSS use many of the same programs and data files. MPx o OS level of 8.5C or higher o Approximately 8.7 MB of disk space 2000 o OS level of 7.2A or higher o Approximately 5 MB of disk space Note - You should add at least 1 MB per generating ORIGIN user to the disk space to allow for warkspace on both the MPx and 2000 systems. 3.0 NEW FEATURES AND ENHANCEMENTS 3.1 INTEGRATED DATA DICTIONARY THE 1.3B Data Dictionary file names have been renamed from "ORI4D1" through "ORI4D5" to "IDDF01" through "IDDF05". There are also 12 new files: o "IDDF06" through "IDDF14" contain globally derived items and views SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB007 Pg002 o "IDD000" contains available databases o "IDDF00" contains the current terminal data and o "IDDFT1" contains changes made in the dictionary for the New Data Impact report. 3.1.1 DECOUPLED INTEGRATED DATA DICTIONARY The Integrated Data Dictionary has been decoupled from ORIGIN to accommodate future modifications to ORIGIN. 3.1.2 NEW ITEM TYPES The following Item Types have been added to MAI ORIGIN~: W - Word Processing Field D - Date E - Expanded Date T - Time B - Binary L - Left Justified 3.1.2.1 Word Processing Field The Word Processing item TYPE (formerly a Special Input Text Field) has been added to the IDD. The number of lines and characters are selected from the FORMAT/MASK input as the number rows and characters separated by a comma. Thus, the input "3,60" would signify a word processing field of 3 lines at 60 characters each. 3.1.2.2 Date The six character date format has been enhanced to allow the description and creation of date formats other than 'MMDDYY'. The new date formats are selected from the MASK/FORMAT field where '1 = DDMMYY', '2 = MMDDYY' and '3 = 'YYMMDD'. 3.1.2.3 Expanded Date The Expanded date type has been created to account for processing across the centuries. The expanded date format will always be written in the format 'YYYYMMDD' but, may be displayed or entered in the American, Canadian, or European format. These formats are selected from the MASK/FORMAT field where '1 = DDMMYYYY', '2 = MMDDYYYY' and '3 = YYYYMMDD'. 3.1.2.4 Time Time is now a recognized data type. The Time field will be written in the format 'HHMMSS' using the 24 hour clock but, may be displayed or entered using either the 12 or 24 hour format. The format is selected by entering SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB007 Pg003 either '12' or '24' at the MASK/FORMAT field. 3.1.2.5 Binary Data type BINARY is now available in the IDD. This data type contains 3 new functions : Encrypt, Decrypt and Conversion. o The encrypt function enables you to encrypt data through a derived item as it is written. o The decrypt function enables you decrypt data through a derived item as it is read. o The conversion function enables you to convert data from 7 bit ASCII to 8 bit and vise versa. With the new encrypt/decrypt functions not only can you use it to convert data into binary format but, you can also manipulate the data in many ways such as stripping off trailing blanks. Thus, you can truly have variable length fields. When the BINARY data type is chosen, the following prompt will display : '1' = COMPACTED DATE FIELD (MMDDYY), OR '0' = NOT COMAPCTED DATE FIELD If a '1' is entered, you should CR at the LENGTH, ENCRYPT WITH DECRYPT WITH, and CONV prompts. ORIGIN will automatically give the data item a length of 3 and the mask of MMDDYY. It will also automatically encrypt the 6 character date into a 3 character compacted date field when the record is written and will decrypt it back into a 6 character date field when it is read. If a '0' is entered you must enter a length, the 'CONV' type (conversion type) and encrypt and decrypt derived item names. At the 'CONV:' prompt, the following will also display : 'T' = CONVERT 7 BIT/8 BIT IF TRANSPORTED, OR 'T' = DO NOT CONVERT If the encrypted data does NOT look the same when printed in hex format on both the 2000 and the MPx you should enter a 'T' for standard text that will require conversion. If the encrypted data looks the same on both the 2000 and MPx you should enter a 'B' for binary. At the 'ENCRYPT WITH:' and 'DECRYPT WITH:' prompts, you must enter derived item names. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB007 Pg004 A "?" at this input will bring you to Derived Item Maintenance thus, allowing you to create and maintain derived items. The following is an example of an ENCRYPT derived item expression that will strip off blanks at the end of a data item. (1,POS(" "=+" ")-1) The following is an example of a DECRYPT derived item expression that will add blanks to the end of a data item. +O0$(1,n-LEN()) Where 'n' equals the length (maximum or defined size) of the item. Note - You must use the "?" as shown. 3.1.2.8 Left Justified The Left Justified type is the string data type or ('S') type renamed to "L". Therefore, it will left justify string data. 3.1.3 DERIVED ITEMS Derived Items may now be created throughout the IDD. The menu option 'DERIVED ITEM MAINTENANCE' has been added the IDD main menu. Derived Items may also be created in 'PRIMARY KEY' maintenance, 'SORT FILES' maintenance and 'VIEW MAINTENANCE'. Derived items may now be used as the primary KEY and/or sort KEY. These keys are created in 'PRIMARY KEY' maintenance and 'SORT FILES' maintenance. When you are creating a primary key or sort file a new prompt will display allowing you to access 'DERIVED ITEM MAINTENANCE'. CTL-I = DERVIED ITEM After you have created your derived item, you may use it as a key. (See Binary Item Type 3.1.2.4 and View Maintenance 3.1.6.) 3.1.4 RULES OF RECOGNITION The rules of recognition is an enhancement to Record Type Selection. Rules of Recognition allows programs to recognize multiple record formats. After primary and secondary key structures have been entered for a record number, a new prompt will be displayed. ...................................................... ...................................................... ENTER THE RULES OF RECOGNITION FOR THIS RECORD (FOR MULTI-RECORD TYPE FILES ONLY) SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB007 Pg005 EXAMPLE: KEY(1,3)="000" OR KEY(1,2)>" " Enter a string expression that states where in the key or data area the record type identifier is located. The record identifier must be located in a fixed position in the key area. The expression must contain "KEY" followed by the position and the length of the identifier in the parentheses and finally what the identifier should be compared to. Example: KEY(5,2)="00" indicates that if characters 5 and 6 of the key are zero, this record is the correct record type. KEY(1,4)>"1000" indicate that if the first 4 characters of the key area of the record are greater than "1000", the record is the correct type. 3.1.5 VIEW MAINTENANCE View maintenance enables the user to create and maintain DERIVED ITEMS and FILE RELATIONSHIPS, mix them with user selected primary data items and sort files (ALT. INDICES) and place them into a 'VIEW'. Once a 'VIEW' of items is created, it may be used by the application and report generators. View Maintenance can be found in the DATA DICTIONARY MAINTENANCE menu. This feature can eliminate the problems your users may have in determining how files are related. 3.1.6 DATA IMPACT REPORT / ORIGIN IDD TIE BACKS Tie backs have been created between the generators and the Data Dictionary. These tie backs enable ORIGIN to check item attributes for consistency during program generation. Similarly, if an item is changed in the Data Dictionary, a report will be made available to show what programs may be affected by the change. This report can be accessed from the Data Dictionary main menu. If the DATA IMPACT REPORT option is chosen, the user may select the output device and other report characteristics using the ORIGIN report option selector. The program will then display or print a report, listing all items changed since the last reset. After the report is complete, the following prompt will display: 'CR' TO RESET IMPACT FILE OR CTL-IV TO EXIT A CR will clear the file for future changes. A CTL-IV will allow the report to be printed again. Once the change file has been reset, all previous changes will not show up on any future reports. Note: A new cross reference file, "IDDFT1", will be created to use this report function. 3.2 DECISION SUPPORT INTERFACES SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB007 Pg006 The Decision Support interface has been greatly enhanced to work MAI OFFICE~ products such as, MAI Business GRAPH~, MAI Business MATH~. It also been given substantial flexibility in manipulating report outputs. 3.2.1 Enhanced Output Device Interfaces When selecting an output device other than a printer or terminal, ORIGIN will allow the user to save the output into a data file. This data file will be created upon execution of the report. This static data can then be used with the variety of output devices available without re-running the report. This data file is accessed from the DECISION SUPPORT FILE MANAGER option on the ORIGIN MAIN MENU. When transfering data to Business GRAPH or Business MATH, ORIGIN will give the user the option to SORT on any print items and/or TOTAL on any numeric print items as well as the option to break on any of the print items for sub-totaling. Thus, a user can output just the totals into a graph or spreadsheet. ORIGIN will also allow the user to automatically invoke the interface product at the completion of the report. 3.2.2 Multi-Item Print Sequence The user may now select multiple items to sort on in User Print Sequence. Any combination of data items including numerics, as long as the combined length of the items plus the Main File Key does not exceed the maximum KEY length of 56 bytes. 3.2.3 Sub-totaling in Executive Query Sub-totaling is now allowed in (EQM) Executive Query Manager. The query will break and sub-total on the first sort item of the print sequence. The print sequence must be the MAIN key or a User Sequence. The items to sub-total are selected from the ITEMS FOR NUMERIC CALCULATION screen. There are 4 new sub-total options in EQM : SUM, MINIMUM, MAXIMUM and AVERAGE. The user may one or more of the options for each of the numeric items in the query. 3.2.4 Conditioning Between Data Items in User Conditions Users may now condition between Data Items. For Example: There are 4 data items - , ,
, and . You want a report of all customers who have not paid their bill by its DUE DATE. So, you would: o Select USER CONDITIONS from your report menu. o Select as the data item to condition. o Select the GREATER THAN option. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB007 Pg007 o CTL-I to select a data item to condition against. o Select as the data item that must be greater than. o You should also condition to print records where is equal to spaces. 3.2.5 Arithmetic Expressions Allowed at Total Time Arithmetic expressions are now allowed in the total line of standard reports. Numeric items as well as the following 2 variables are allowed in these expressions: N = The total number of records printed, so far, in the report. B = The number of records printed for your sub-total or break item. These variables are generally used for obtaining averages. To create an Arithmetic Expression in a total line you should perform the following steps: 1. Enter in the total line where "n" equals a number from 1 to 99. 2. Upon exiting Report Line Maintenance, you will be prompt to enter the expression for each Arithmetic Expression in your total line. The following is an example of adding the total of numeric items <4>,<5>, and <6>. ENTER EXPRESSION <4>+<5>+<6>....................................... The expression above will print the total of the numeric items at each break. 3. Step 2 will be repeated for each expression contained on your total line. 3.2.6 Non-total Items Allowed in Total Area of Report. Non-total data items may now be selected to print as text in the total area of a report for use as sub-titles or footers. Example: TOTAL FOR CUSTOMER : 3.2.7 Page Breaks at Each Level of Breaking of breaking. The question "PAGE CHANGE ON BREAKS" has been removed from the screen. To specify page changes, modify option 7 (Main File Break Items) on the REPORT PARAMETER MAINTENANCE screen. Enter the item number of each item to break on followed by an asterisk (*). The asterisk signifies a page break. A number without the asterisk signifies a break WITHOUT a page change. Multiple break levels are specified by SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB007 Pg008 a comma between level. Example: 7. MAIN FILE BREAK ITEMS : 1*,2,3*.................... 3.2.8 Override of Mask Verification During Report Line Maintenance The user may now skip the verification of numeric TOTAL masks in Report Line Maintenance. Previously, the user would have to carriage return for each TOTAL mask in his report. If he had 10 totals, he would have to carriage return 10 times before exiting REPORT LINE MAINTENANCE. ORIGIN now gives the user the option CTL-II to skip all mask verifications and use the existing mask for each TOTAL mask. Example: CR=EXISTING MASK, CTLII=VERIFY OFF, CTLIII=DO NOT TOTAL 3.3 APPLICATION GENERATOR 3.3.1 Changed QUERY BY EXAMPLE Exit Location When no more records are found that match your search criteria, the QUERY BY EXAMPLE option of a generated file maintenance program, you will exit to the prompt: ENTER THE INPUT NUMBER OR NAME TO BE SEARCHED......... CTL-IV = EXIT Previously, you would exit to the mode selector display. 3.3.2 Numeric Input Prompts Now Use Numeric Mask The numeric input prompts in a generated file maintenance program have been changed from a single dot to the actual numeric mask. Example: Customer Balance: . Customer Balance: ###,##0.00- 3.3.3 Change of Screen For Input Items The screen on which an input item is entered may now be changed without deleting the item and recreating it on the new screen. In ITEM MAINTENANCE, selecting option 2 (POSITION OF INPUT) will prompt the user : ENTER INPUT POSITION (COLUMN#,LINE#),CTLI TO POSITION MANUALLY: If more than one screen exists for this program, a new prompt will display: ENTER INPUT POSITION (COLUMN #, LINE #, SCREEN #): 3.3.4 Allow Creation of Derived Items During Screen SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB007 Pg009 Maintenance Derived items may now be created while in screen maintenance. The following prompt will display: CTL-I = NEW DERIVED ITEM NOTE - Derived items created in an individual program are not placed in the Integrated Data Dictionary and therefore, may not be shared by other programs. 3.3.5 Enhanced User Interface of File Relationships Creating relationships and related items has been made easier to use. You may now view your file names and descriptions before selecting a file in which to create a relationship. When creating related items the data items in the related file will be displayed. You may then select 1 or all of the data items in the related file through a menu without worrying about what field number it comes from or what file relation number to add to it. 3.4 SYSTEM ADMINISTRATOR UTILITIES The System Administrator Utilities is a new menu that may be selected from the ORIGIN main menu or by entering 'SYS' from most ORIGIN menus. 3.4.1 Select User-Defined Ending This option enables you to select the text and the action for each control key in the ORIGIN ending prompt. For example - The default prompt now displays: CR STOP, CTLI CHANGE LOGON, CTLIII LOG OFF & RELEASE, CTLIV RETURN You can change CTLIV to display "MAI OFFICE" instead of "RETURN" and execute the program "MS" when CTLIV is selected. 3.4.2 Maintain ORIGIN System Parameters This option enables you to maintain the following ORIGIN default parameters: 1. The heading title for generated programs. 2. * The Affirmative Response character. 3. * The Negative Response character. 4. Maximum files that can be opened at one time. This number is determined by the System and OS level. 5. File Prefix/Suffix directory to be inserted or appended to generated files. 6. Default Date Type in IDD file maintenance. 7. Date Separator character. (eg. "/", ".") 8. Default terminator in IDD file maintenance. 9. System Time Format (12 or 24) * This feature is not currently supported. The SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB007 Pg010 input will be used in a future release. 3.4.3 Language Translation Menu (For International use Only) Provides an easy access to the International Translation programs. 3.4.4 Maintain Decision Support Packages This program enables you to maintain the output devices used in the Decision Support Interface feature: MAI Business GRAPH, MAI Business MATH, LABEL PRINTING, ETC... (For more information regarding this package, please contact Keith Kanneg or Melinda Chance in Product Marketing EXT. 2440) 3.4.5 Maintain Data Handling Files This option enables you to use the Decision Support Interface files you create when outputing a report and interface them with selected MAI OFFICE modules and user defined interface modules. 3.5 MISCELLANEOUS ENHANCEMENTS 3.5.1 Easy Access Menus You can now access menus in ORIGIN by entering 1 to 2 characters at the selection prompt of most menus. For example, entering an "R" at the 'ENTER SELECTION (CTL-IV=END)' prompt in the Applications Generator main menu will bring you to the Report Generator main menu. The following lists the Easy Access characters and their associated menus. D = Integrated Data Dictionary A = Application Generator R = Report Generator M = Menu Generator U = Utilities H = User Help DOC = Technical Documentation DSM = Decision Support Manager EQM = Executive Query Manager ORI = ORIGIN Main Menu SYS = System Administrator Utilities 4.0 INSTALLATION/UPGRADE PROCEDURES *** PRIOR TO INSTALLATION, REMEMBER TO BACK-UP YOUR ORIGIN DIRECTORIES ! *** 4.1 Installations/Upgrades on the MPx The security for ORIGIN on MPx systems has been changed to SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB007 Pg011 work like the ORIGIN security on the 2000. A public key is now required for both ADS and DSS. To install/upgrade ORIGIN 2.0 onto your MPx system perform the following steps: 1. Set your prefix to (family).ORIGIN.R20A.PGM.,.ORIGIN.R20A.DATA. 2. Restore the appropriate files on tape using the SAVERESTORE utility : o FOR INSTALLATIONS UPGRADING FROM ORIGIN 1.3A. You must first update your ORIGIN 1.3A system to 1.3B. The update program "ORIA2B" is included on the ORIGIN 2.0 tape. Please refer to the ORIGIN 1.3B software Announcement for instructions on how to upgrade from R13A to R13B. o FOR NEW INSTALLATIONS OR INSTALLATIONS UPGRADING FROM ORIGIN 1.3B. Restore all program and data files. Enter an '&' at the SAVERESTORE prompt 'ENTER FILE SPECIFIERS'. WARNING - Entering an '&' for an installation with an existing ORIGIN 2.0 system results in the loss of the Data Dictionary and the ability to re-generate any programs previously generated because it will restore over your existing data files. Eg: ENTER FILE SPECIFIERS: >& o FOR INSTALLATIONS UPGRADING FROM A BETA VERSION OF ORIGIN 2.0A. Restore the ".ORIGIN.R20A.PGM" node. Eg: ENTER FILE SPECIFIERS: >.ORIGIN.R20A.PGM.& 3. Install the appropriate public key for each module you're installing : ADS (Applications Development System), DSS (Decision Support System). o To Install your DSS public key, enter the following from command mode: !INSTALLKEY .ORIGIN.R20A.ETC.LEVEL.DSS You will then be prompt: Current Public Key: 12345678 Input 8-character public key (cr=no change): Enter your public key obtained from Software Distribution. o To Install your ADS public key repeat the same instructions as for DSS: SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB007 Pg012 4. RUN "UPDATE" from BASIC. This program contains 2 steps. It will first copy the ORIGIN data files from your ORIGIN R13B directory into the new R20A directory. It will then transfer and convert the R13B dictionary files into R20A dictionary files. Answer the following UPDATE prompts accordingly: o ENTER THE FAMILY NAME FOR .ORIGIN.R20A.: (family) o ENTER THE NODE OF YOUR CURRENT ORIGIN SYSTEM INCLUDING FAMILY NAME, CR IF THIS IS A NEW INSTALLATION: (family).ORIGIN.R13B. If you CR for a new installation, skip to the 'INSTALL STAND ALONE ORIGIN UTILITIES' step. o CR TO PROCEED WITH ORIGIN .ORIGIN.R20A. UPDATE, CTLIV=EXIT: CR will copy the following ORIGIN R13B data files into the R20A directory: ORIDDF ORIPF2 ORIPS5 ORIQF2 ORIQS2 ORIV01 ORIDHF ORIPS2 ORIPS6 ORIQFL ORIQST ORIVDC ORIDSP ORIPS3 ORIPS7 ORIQP1 ORIUFL ORIPDF ORIPS4 ORIQF1 ORIQS1 ORIUST o CR TO BEGIN UPDATE OF DICTIONARY FILES, CTL-IV TO EXIT CR to begin. The update program will execute the conversion program "IDDCNV". This program transfers and converts the 1.3B dictionary files into the new 2.0A dictionary. During the conversion, each database (project code) will be displayed as it is converted followed by the file names within the database and their record numbers. Eg: DATA FILE RECORD BASE NAME NUMBER ABC ABCF01 01 Each file is checked for orphan information such as a file header without any record descriptions, records without reference names, or record layouts without data items. If a discrepancy is found, a message will be written to the conversion impact file "IDDCN0". This file can be displayed at the completion of the conversion. Each item will also be checked for consistency against the 'GLOBAL' dictionary. Global dictionary entries are made at the first occurrence of a data item. Example: The first time 'COMPANY-ID' is mentioned in a file, the attributes for 'COMPANY-ID' will be written to the global dictionary for the file being converted. When all of the files have been transferred, the following prompt will display: SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB007 Pg013 o CONVERSION COMPLETE. CR TO CONTINUE You will be given the option to output the conversion impact report to either the terminal or a printer. If no discrepancies were found during the conversion, the report will be blank. o ENTER ITEM NAME OR NUMBER TO SELECT OR DE-SELECT (CR TO CONTINUE) To run the conversion impact report independently, RUN "IDDCNR" from BASIC. o INSTALL STAND ALONE ORIGIN UTILITIES IN SYSTEMS NODE (family).R5C15.SYS. CR TO PROCEED, CTL-IV TO END : CR will copy the files contained in the filelist ".ORIGIN.R20A.DATA.STANDALONE" into your system node. ORIGIN INSTALLATION COMPLETE : User Prefix set 5. Set your primary prefix to the node in which you want all of your ORIGIN generated programs and data files created followed by the 2 ORIGIN directories. !PREFIX (family).user selected.,(family).ORIGIN.R20A.DATA.,.ORIGIN.R20A.PGM. 6. RUN "ORIGIN" from BASIC to begin processing. If you have removed or added an ORIGIN module (ADS or DSS) to an existing ORIGIN 2.0A system, you must RUN "ORINST" from BASIC. This will re-write your public keys into ORIGIN's security file. 4.2 Installation/Upgrades on the 2000 To install/upgrade ORIGIN 2.0 onto a 2000 system, perform the following steps: 1. Restore the appropriate modules from tape using the 'install cs' command. The ORIGIN data files are written into the /origin/r20a/data/new to avoid the accidental deletion of existing ORIGIN data files. o To install the Application Development System (ADS) enter the following command: admin>install cs ADS o To install the Decision Support System (DSS) enter the following command: admin>install cs DSS o To install the ORIGIN Translation Utilities (OTU) enter the following command: admin>install cs OTU The ORIGIN Translation Utilities is required for SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB007 Pg014 international translation ONLY. During the installation you will be prompted for your installation key. Input 8-character installation key (cr=no change): If the installation keys are not readily available to continue. The keys can be installed at the completion of the update using the following commands: ADMIN>install key /etc/level/DSS ADMIN>install key /etc/level/ADS No key is required for OTU. 2. Start 256 in BASIC and set your prefix to "/origin/r20a/pgm /origin/r20a/data" using the prefix directive: ADMIN>basic s=256 -nr >prefix "/origin/r20a/pgm /origin/r20a/data" 3. In BASIC and RUN "UPDATE". Answer the following "UPDATE" prompts accordingly: o Enter ORIGIN 2.0A disk name (CR if none): CR If you are installing onto drive 0, CR. Otherwise, enter the directory name of drive 1. o Enter directory of your current Origin system. CR if this is a new installation: /origin/r13b A CR for new installation will rename the data files from "/origin/r20a/data/new" to "/origin/r20a/data" it will then, skip to the Install STANDALONELIST step. o Save data files from current Origin system ? YES - Will rename the ORIGIN data files from "/origin/r20a/data/new" to "/origin/r20a/data" directory. It will then copy the ORIGIN data files from the "/origin/r13b/data" directory into the "/origin/r20a/data" directory. NO - Will rename the data files from "/origin/r20a/data/new" to "/origin/r20a/data" directory. o CR TO BEGIN UPDATE OF DICTIONARY FILES, CTL-IV TO EXIT CR to begin. The update program will execute the conversion program "IDDCNV". This program transfers and converts the 1.3B dictionary files into the new 2.0A dictionary. During the conversion, each database (project code) will be displayed as it is converted followed by the SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB007 Pg015 file names within the database and their record numbers. Eg: DATA FILE RECORD BASE NAME NUMBER ABC ABCF01 01 Each file is checked for orphan information such as a file header without any record descriptions, records without reference names, or record layouts without data items. If a discrepancy is found, a message will be written to the conversion impact file "IDDCN0". This file can be displayed at the completion of the conversion. Each item will also be checked for consistency against the 'GLOBAL' dictionary. Global dictionary entries are made at the first occurrence of a data item. Example: The first time 'COMPANY-ID' is mentioned in a file, the attributes for 'COMPANY-ID' will be written to the global dictionary for the file being converted. When all of the files have been transferred, the following prompt will display: o CONVERSION COMPLETE. CR TO CONTINUE You will then be given the option to output the conversion impact report to either the terminal or a printer. If no discrepancies were found during the conversion, the report will be blank. o ENTER ITEM NAME OR NUMBER TO SELECT OR DE-SELECT (CR TO CONTINUE) To run the conversion impact report independently, RUN "IDDCNR" from BASIC. o Install standalone ORIGIN utilities ? YES - Will enable the user to run ORIGIN generated programs from one directory. You will then be prompted: Enter the directory for the standalone programs CR=std CR - will restore the program and data files contained in the "/origin/r20a/pgm/STANDALONELIST" into the "/bin" directory. Entering a directory name will copy the STANDALONE files into the specified directory. NO - Done with update. Executing ORIGIN When executing ORIGIN your primary directory should ALWAYS be the directory in which you want your ORIGIN generated files created. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB007 Pg016 To insure that all of your ORIGIN generated files are created in the same directory, you should create a command file that changes your prefix and executes ORIGIN. This command file should ALWAYS be used when accessing ORIGIN. o Executing ORIGIN Automatically The following is an example of how to create a command file where "/user/origin" is the directory in which all ORIGIN generated files are to be created: 1. Create the string file "/origin/startorigin" using the ved command. ADMIN>ved /origin/startorigin Your string file should look like this: cd /usr/origin ad /origin/r20a/pgm /origin/r20a/data basic s=256 -nr pgm=ORIGIN 2. CTRL-C to exit and answer "Y" to save. 3. Make your string file executable using the filemodes command. ADMIN>filemodes +x +x /origin/startorigin 4. Create the directory in which you want all of your ORIGIN generated file created. ADMIN>makedir /usr/origin 5. To execute your command file, enter the name of the file form command mode. ADMIN>/origin/startorigin This command file can be used as the initial program for an operator in the 2000 "oprinfo" menu. o Executing ORIGIN Manually 1. Create the directory in which you want all of your ORIGIN generated files created. ADMIN>makedir /usr/origin 2. Set your prefix to "/usr/origin /origin/r20a/pgm /origin/r20a/data" (where "/usr/origin" equals the user defined directory in which all ORIGIN generated files are to be created.) ADMIN>cd /usr/origin ADMIN>cd /origin/r20a/pgm /origin/r20a/data 3. Enter BASIC with a start size of 256 and run "ORIGIN". ADMIN>basic s=256 -nr pgm=ORIGIN 5.0 HELPFUL HINTS SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB007 Pg017 5.1 General o 'RELEASE' as the return program name in menu maintenance will release the terminal. o Pressing ESC then CTRL-A will allow you to escape in most ORIGIN programs. 5.2 Integrated Data Dictionary o If you are setting up a file with a single record type in the IDD, you should leave the record description blank. This field is used for the default for File Reference Name. If the record description field is blank, the default will be the File Description. o Used the Zero Filled type item on all numeric items defined as part of a key intead of the X-type. The Zero Filled item can be used for all numerics that do not require special characters in the mask such as commas and decimal points. 5.3 Application Generator o If you are using the 'repeat at input' option in Applications Generator and the 'repeat at' input and the remaining inputs are all on the same line, the input line will scroll down after each record input. o If you select 1 as the line number at the 'clear screen from line #' option in Applications Generator, the mode selector will print at the bottom of the screen. Also, make sure that you enter a 'Y' at the Clear First Screen option. o The Print Mask control key (Function key 5 on the EDT and EVDT terminals) will re-display your input prompts when modifying screen text in Applications Generator. 5.4 Report Generator o To obtain the Order Entry line number in a report, use . 6.0 WARNINGS AND CAUTIONS The following list has been created to help you avoid potential problems. PLEASE read ALL of them before executing ORIGIN. The problems documented in this list are scheduled for a future release of ORIGIN. 6.1 General o Do not use commas "," in Masked Numeric items. An error 26 may occur in generated reports using conditions which compare two derived items and an error 47 in generated File Maintenance programs. o When logging on to ORIGIN, remember to periodically CTL-I to check the status of your technical documentation files. When these files become full the user may receive the message "USER INCORRECTLY LOGGED ON". SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB007 Pg018 o The message "USER INCORRECTLY LOGGED ON" is displayed for 4 reasons: 1. The user is incorrectly logged on and must log on correctly by running "ORIGIN". 2. File(s) full in the technical documentation. The user must log on to "ORIGIN", CTL-I to display the technical documentation files and copy and expand the files that are displayed as full. 3. The disk or family is full. Room must be made on the disk or family. 4. Someone logged the user off from another terminal. 6.2 Integrated Data Dictionary o When copying a file from one data base to another, you must re-input the SORT file KEY EXPRESSION if the EXPRESSION is a derived item. o Data Item names can not be the same as Derived Items names. o Do NOT CTL-II to display the previous page in the Data Impact Report: the program will hang. To exit from this condition, press the ESCAPE key and then CTL-A. This will drop you into console mode. You can then RUN "ORIGIN" to return to the ORIGIN main menu. o An error 10 may occur in program "ORIDFC" when you copy an entire data base (project code) to a new data base. The program will then exit you to the menu. If you return to copy and follow the exact same steps, everything will work fine. 6.3 Application Generator o When creating Order Entry Applications, do not use CTL-I to create a new line type in Application Generator. Create line items from scratch on a new screen. o If you have over 60 inputs in a File Maintenance program use the option for smaller program. This will help you avoid error 31's (Insufficient Memory within Task). o When adding or deleting Input Items in a file maintenance program, remember to change the input numbers that are used in Sub-Menu Maintenance to reflect these changes. o MAIN KEY ITEMS in Program Parameter Maintenance must be entered manually when initializing from the IDD. An entry at this option is not required. o The MAXIMUM character length of an Order Entry item is 75. o If a FM program is linked to the IDD, all changes made to data items in the FM program must be made in the IDD. 6.4 Report Generator o Do NOT use CTL-II to back-up to a previous page in a SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB007 Pg019 generated report if you are performing numeric calculations such as Sub-totals or Totals. ORIGINATOR: MBF SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB007 Pg020 FIB 00008 09/17/87 *** Report line maintenance on 2000/3000 *** PROBLEM : The Report Line Maintenance option does not appear on the MAI ORIGIN 2.0A Report Generator screen on SPx systems if the system has DSS only. SOLUTION : Modify statement 31 in program ORIPMS: OLD: 0031 SETERR 0 NEW: 0031 SETERR 0; IF B$="S" AND C=71 THEN LET C=72 ELSE IF B$="G" AND C=572 THEN LET C=571 After this change, the Report Line Maintenance option can be selected from the Report Generator large menu. This menu is accessed by entering CTL-III from the small four option menu. FUTURE : This problem will be corrected in the next release of ORIGIN. ORIGINATOR: T. Tiangco SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB008 Pg001 FIB 00009 12/29/87 *** MAI Origin 2.0A and INSTALLKEY on 8/9.6 [ WPS 413 ] *** PROBLEM : The INSTALLKEY command on the MAI ORIGIN 2.0A tape cannot be executed on the 8/9.6 OS because it is in 8.5 format. Therefore, you cannot install your Public ID's for ORIGIN using this command. The message : This code file may not be executed on this release of the system (7,1,14,10) will display when you attempt to install your Public ID WORKAROUND : Use the MPx editor to install your 8 character Public ID into the .ORIGIN.R20A.ETC.LEVEL files. 1. For serial terminals, Set your function keys using the SETKEYS command. Ex: !SETKEYS 2. Install your DSS and/or ADS keys using the EDIT command. Ex: !EDIT .ORIGIN.R20A.ETC.LEVEL.DSS 3. Replace the current Public id with your 8 character Public key. This is how it will look in the level file: 5. Public id: 12345678 4. RUN "ORINST" to complete your installation. FUTURE : The 8/9.6 version of the INSTALLKEY program will be on the release of MAI ORIGIN release 2.1A. ORIGINATOR: Tony Tiangco SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB009 Pg001 FIB 00010 02/12/88 *** Can't log-on to Origin 2.0A on 8/9.6 OS [ WPS 419 ] *** ********************************************************************* * PLEASE PLACE A COPY OF THIS FIELD BULLETIN INTO THE MAI ORIGIN * * HELPFUL HINTS MANUAL. * ********************************************************************* PROBLEM: You can't log on to ORIGIN 2.0A when your OS is at 9.6/8.6. An error 20 will occur in statement 1040 of program "ORIULG". CAUSE: The error 20 is caused because ORIGIN uses the variable MSG$, which is now a function in BB86. WORKAROUND: o LOAD "ORIULG" o Replace the 3 occurences of MSG$ in statement 1040 with MESG$. OLD: 1040 X5$="G";CALL"ORIPMS",7,X5$,903,0;READ(4,KEY=A4$, ERR=1041) *,LAN$;MSG$="G"; CALL"ORIPMS",7,MSG$, 897,0; X5$=MSG$+LAN$(1,POS(" "=LAN$+" ")-1+", "+X5$ NEW: 1040 X5$="G";CALL"ORIPMS",7,X5$,903,0;READ(4,KEY=A4$, ERR=1041) *,LAN$;MESG$="G"; CALL"ORIPMS",7,MESG$, 897,0; X5$=MESG$+LAN$(1,POS(" "=LAN$+" ")-1+", "+X5$ o SAVE FUTURE: This fix will be included in the next release of ORIGIN (2.1A). ORIGINATOR: Tony Tiangco SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB010 Pg001 FIB 00011 03/28/88 *** MAI ORIGIN 2.1A ADS/DATA Software Announcement [ WPSS 155 ] *** ________________________________________________________________ This software announcement describes the Enhancements and New Features that have been added to MAI ORIGIN~ 2.1A ADS / MAI Business DATA~. It also contains the Installation Procedures and Requirements for both the MPx and 2000/3000/4000 systems. ________________________________________________________________ MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement __________________________________________________________________________ TABLE OF CONTENTS OVERVIEW REQUIREMENTS 2.1 MPx 2.2 2000/3000/4000 INSTALLATION AND UPGRADE PROCEDURES 3.1 MPx 3.1.1 New Installations, Installations Upgrading from 2.0A 3.1.2 Installations Upgrading from 1.3B or 1.3A 3.1.3 Executing ORIGIN on the MPx 3.2 2000/3000/4000 3.2.1 New Installations and Installations Upgrading from 2.0A and Installations Upgrading from a Beta Release of 2.0A 3.2.2 Installations Upgrading from 1.3B 3.2.3 Executing ORIGIN on the 2000/3000/4000 3.2.4 Setting Up an ORIGIN User on the 2000/3000/4000 NEW FEATURES AND ENHANCEMENTS 4.1 LOG-ON 4.1.1 Menu System Log-on 4.1.2 ORIGIN User Log-on 4.2 PRESENTATION SERVICES 4.3 DISTRIBUTED PROCESSING 4.3.1 Data Base Table Maintenance 4.3.2 Distributive Processing Allowance Flag in Function Maintenance 4.3.3 Runtime Use of Distributive Processing MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement __________________________________________________________________________ SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg001 TABLE OF CONTENTS 4.4 INTEGRATED DATA DICTIONARY 4.4.1 File Name 4.4.2 Extended File Names 4.4.3 Multi-keyed File Support 4.4.4 Alternate Keys 4.4.5 Composite Item Type 4.4.6 Order Entry Files 4.4.7 Numeric Items Now Allowed as Keys ('X' to 'N') 4.4.8 File Examine Utility 4.4.9 Alternate/Duplicate Keys in Record Layout Printing 4.4.10 Freeform Text in Record Layout Printing 4.5 REPORT GENERATOR 4.5.1 Creation of Runtime Numeric Items 4.5.2 Support of Spooler Options 4.5.3 Conditioning 4.5.4 Multi-level User Defined Breaks 4.5.5 Total Only and Total After Detail 4.5.6 Start/Stop Key Entry 4.5.7 Start/Stop Prefix 4.6 APPLICATION GENERATOR 4.6.1 Conditioning 4.6.2 Skipping Display Only Fields 4.6.3 Alpha/Numeric Masking for String Fields 4.6.4 Expanded Sub-Menu Descriptions 4.6.5 Verification Windows for Inputs 4.6.6 Remove from Screen Option on Derived Items 4.6.7 Input Routine Optimized 4.6.8 Insert/Delete Multiple Order Entry Lines 4.6.9 Input Case Conversion MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement __________________________________________________________________________ TABLE OF CONTENTS 4.7 TECHNICAL DOCUMENTATION 4.8 GENERAL IMPROVEMENTS 4.8.1 Creation of Derived Items in Edit Mode 4.8.2 Related Files - Next Record If Missing Option 4.8.3 Work Node for Temporary Files 4.8.4 Release Level Comment Added to Generated Programs 4.8.5 Use of Arrow Keys in Selectors 4.8.6 Sumarize Data Function 4.8.7 Acceptance Key Changed from CTL-III to CR RELATED DOCUMENTS HELPFUL HINTS MAI ORIGIN 2.1A~ Software Announcement SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg002 __________________________________________________________________________ OVERVIEW Many new features and enhancements have been added to MAI ORIGIN in this release. It is the first version of ORIGIN to conform to the Presentation Services display standard. Here are some of the highlights of the 2.1A release: o Introduces the new features implemented in BB86 (such as, Multi-keyed files and MAGNET support) o Enhances the performance of ORIGIN o Adds to ORIGIN's user friendliness and ease of use o Adds expanded data file names o Adds a user specified work directory o Shortens the prefix required to execute ORIGIN o Corrects problems found in the 2.0A release There are 9 directories included on the 2.1A tape: DIRECTORY___________ DESCRIPTION_____________________________________ .ORIGIN.R21A. Contains ORIGIN log-on files. .ORIGIN.R21A.PGM. Contains the programs required to generate programs. .ORIGIN.R21A.DATA. Contains the Integrated Dictionary files along with other data files. .ORIGIN.R21A.LANGUAGE. Contains the ORIGIN translation utilities. These files are used primarily by international to translate ORIGIN from English to a different language. .ORIGIN.R20A.RT. Contains program and data files required to execute 2.0A generated programs. .ORIGIN.R21A.RT. Contains program and data files required to execute 2.1A generated programs. .PS. Contains the Presentation Services menu files. .PS.TOOLS. Contains the programs required to build and maintain PS menus. .ORIGIN.R21A.UTIL. The programs in this directory are NOT SUPPORTED They are included on the tape to help the user examine data files, debug programs and to help create the Integrated Data Dictionary (IDD). MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement __________________________________________________________________________ REQUIREMENTS SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg003 2.1 MPx o OS Level 8.6A or higher o Presentation Services 3.1A or higher o Aproximately 15.1 megabytes of free disk space plus 1 megabyte for each generating user. 12.1 MB - for ORIGIN (This includes a MAI Business Data only system.) 0.5 MB - for ORIGIN menus 2.5 MB - for Presentation Services 15.1 MB Total + 1 MB for each generating user. o MAGNET~ (If you plan to use Distributed Processing to access remote systems.) o New legend strips are required for the DT-4309, DT-4312, DT-4313 and the DT-4314. Please refer the marketing announcement for market codes. 2.2 2000/3000/4000 o OS Level 7.3A or higher o Presentation Services 3.1A or higher o Aproximately 11.4 megabytes of free disk space plus 1 megabyte for each generating user. 8.9 MB for ORIGIN (This includes a DSS only system.) .5 MB for ORIGIN menus 2.5 MB for Presenation Services 11.4 MB Total + 1 MB for each generating user o MAGNET~ (If you plan to use Distributed Processing to access remote systems.) o Your 2000/3000/4000 conf parameters must be set to at least these settings: lus=184, opens=77, eventcalls=85 NOTE - Please refer to the 2000/3000/4000 Software Announcement #153 for suggested settings if you have more than 1 MB of memory. o New legend strips are required for the DT-4309, DT-4312, DT-4313 and the DT-4314. Please refer the marketing announcement for market codes. MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement __________________________________________________________________________ INSTALLATION AND UPGRADE PROCEDURES ******************************************************************* * * * BACK UP the .ORIGIN.R20A.DATA. directory and the directory in * * which your *DC0 files are located BEFORE installing this * SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg004 * release. The *DC0 files (the technical documentation files) * * are normally located in your primary prefix. * * * ******************************************************************* 3.1 MPx 3.1.1 NEW INSTALLATIONS AND INSTALLATIONS UPGRADING FROM 2.0A ______________________________________________________________ 1. Set your PREFIX to (family).ORIGIN.R21A. Ex: !PREFIX (family).ORIGIN.R21A. ______________________________________________________________ 2. Restore all files from tape using the SAVERESTORE utility. Enter an '&' at the SAVERESTORE prompt 'ENTER FILE SPECIFIERS'. Ex: ENTER FILE SPECIFIERS: >& ______________________________________________________________ 3. If Presentation Services (PS) is not already installed on your system, you must install it by running the program ".PS.INSTALL" from BASIC. This program will copy the files from the .PS.SYS. directory into your system directory. Ex: >RUN ".PS.INSTALL" During the copy the following will display: Install Program PS 3.1 ----------------------------------------------------- NOW COPYING : .PS.SYS.MSXXXX TO : ().R6AXX.SYS.MSXXXX Installation of PS3.1 is now complete .. ______________________________________________________________ MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement __________________________________________________________________________ (MPx New Installations and Installations Upgrading from 2.0A) ______________________________________________________________ 4. RUN "UPDATE" from BASIC. If you are a new installation, this program will rename several 2.1a data files. If you are upgrading from 2.0A, this program will program will convert your 2.0A dictionary files and user files into the 2.1A files. Answer the following UPDATE prompts accordingly: SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg005 A. ENTER THE FAMILY NAME FOR .ORIGIN.R21A.: (family) B. ENTER THE NODE OF YOUR CURRENT ORIGIN SYSTEM INCLUDING FAMILY NAME, CR IF THIS IS A NEW INSTALLATION : (family).ORIGIN.R20A. If you CR for a new installation, skip to step F to install the STANDALONE files. C. CR TO PROCEED WITH .ORIGIN.R21A. UPDATE, CTL-IV = EXIT : CR Press CR - This will copy the following files from the R20A directory into the .ORIGIN.R21A.DATA. directory. ORIDDF ORIQF1 ORIQFL ORIQS2 ORIV01 ORIPS7 ORIQF2 ORIQS1 ORIQST ORIVDC It will then convert the program files ORIPS4 thru PS6 into the 2.1A files. D. CR TO BEGIN UPDATE OF DICTIONARY FILES, CTL-IV TO EXIT CR Press CR to convert R20A program documentation and Integrated Data Dictionary (IDD) files, Expressions, and Views into R21A format. E. IDD CONVERSION COMPLETE. CR TO CONTINUE: CR Press CR to continue the installation of the R21A Runtime files. ______________________________________________________________ MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement __________________________________________________________________________ (MPx New Installations and Installations Upgrading from 2.0A) ______________________________________________________________ F. INSTALL STAND ALONE ORIGIN UTILITIES IN SYSTEM NODE (family).R6Axx.SYS. CR TO PROCEED, CTL-IV TO END: CR Press CR to copy the files contained in the Runtime directory, ".ORIGIN.R21A.RT." into the system node. Example: .ORIGIN.R21A.RT.ENGxxx ---> .R6Axx.SYS.RT.ENGxxx ______________________________________________________________ 5. Install your new public key(s) for each module you're installing using the INSTALLKEY program. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg006 o To install ADS (Application Development System) A. Enter the following from command mode: !INSTALLKEY ADS You will then be prompted: SYSTEM SERIAL NUMBER: 810-12345 CURRENT SECURITY KEY: 12345678 NEW SECURITY KEY : ENTER NEW SECURITY KEY ('CR' IF NO CHANGE) B. Enter your 8 character security key obtained from Software Distribution. o To install MAI Business DATA~ repeat items A and B and replace the characters 'ADS' with 'DSS'. ______________________________________________________________ MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement __________________________________________________________________________ (MPx New Installations and Installations Upgrading from 2.0A) ______________________________________________________________ 6. This step is optional. If you do not plan to use the language translation utilities, you can delete the .ORIGIN.R21A.LANGUAGE. node. These utilities are used primarily by international sites to translate ORIGIN from English to a different language. To delete this node, enter the following from command mode: !DELETE .ORIGIN.R21A.LANGUAGE.& ______________________________________________________________ 7. Skip to section 1.3 EXECUTING ORIGIN ______________________________________________________________ MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement __________________________________________________________________________ 3.1.2 MPX INSTALLATIONS UPGRADING FROM 1.3B OR 1.3A ______________________________________________________________ 1. Upgrade the ORIGIN dictionary files to 2.0A format. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg007 1.3B Users: Follow the 2.0A upgrade instructions in the MAI ORIGIN 2.0A Software Announcement #143 on page 14. The dictionary conversion program "IDDCNV" described in the Software Announcement is contained on the 2.1A tape in the .ORIGIN.R21A.UTIL. directory. 1.3A Users: Follow the 2.0A upgrade instructions in the MAI ORIGIN 2.0A Software Announcement #143 on page 13. The conversion program "ORIA2B" described in the Software Announcement must be restored from an MAI ORIGIN 2.0A tape. ______________________________________________________________ 2. Turn to Section 1.1 New Installations and Installations Upgrading from 2.0A ______________________________________________________________ MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement __________________________________________________________________________ 3.1.3 EXECUTING ORIGIN on the MPx You may execute 1.3B and 2.0A generated programs as long as the R20A standalone files are installed in the system node or the R20A runtime directory is in your prefix. However, if you want to take advantage of the 2.1A features you must re-generate your programs. Here are the steps for executing 2.1A on the MPx: ______________________________________________________________ 1. Set your prefix with your user prefix first followed by the ORIGIN and Presentation Services directories. Ex: !PREFIX (family).user.,.ORIGIN.R21A.,().PS.TOOLS. ______________________________________________________________ 2. From BASIC, RUN "ORINST". This program needs to be executed only when you are installing ORIGIN. You should run "ORIGIN" after your initial installation. ______________________________________________________________ 3. Enter the account name "MAI.ORIGIN" and the password "ADMIN" at the Menu system Log-on. ______________________________________________________________ 4. Set up your ORIGIN users. _____ Select Utilities from the ORIGIN main menu. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg008 _____ Select User Maintenance, use the password "ADMIN". ______________________________________________________________ 5. Set up your ORIGIN System Parameters. _____ Select Utilities from the ORIGIN main menu _____ Select System Administrator Utilities The password is ADMIN. _____ Select ORIGIN System Parameters Maint _____ Enter a Work Files Node. This node will be the directory in which all of your temporary ORIGIN files will be created. Normally, this node is ".ORIGIN.R21A.WORK.". ______________________________________________________________ MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement __________________________________________________________________________ 3.2 2000/3000/4000 3.2.1 NEW INSTALLATIONS, INSTALLATIONS UPGRADING FROM 2.0A ______________________________________________________________ 1. If you are installing ORIGIN onto your second drive perform the following commands from ADMIN ; otherwise, skip to step 2. ADMIN>cd / ADMIN>makedir /origin ADMIN>mount /dev/your-partion-name /origin ______________________________________________________________ 2. Restore the ORIGIN modules plus the Presentation Services menu system from tape using the install command. If you're installing ORIGIN onto your second drive, append 'to=/origin' to your install command. Ex: ADMIN>install cs DSS ADS EPS OTU to=/origin NOTE - Replace "cs" with "ts" if you installing from an MTS unit. o To install MAI Business Data and the PS menu system enter: ADMIN>install cs DSS EPS o To install MAI Business DATA and ADS and the PS menu system enter: ADMIN>install cs DSS ADS EPS SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg009 o To install MAI Business DATA, ADS, the PS menu system, and the ORIGIN Translation Utilities enter: (For International Only) ADMIN>install cs DSS ADS OTU EPS ______________________________________________________________ MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement __________________________________________________________________________ 2000/3000/4000 (New Installations, Installations Upgrading from 2.0A ______________________________________________________________ 3. Enter the 8 character installation key obtained from Software Distribution after each module is installed from tape. The following message will display after each module is restored from tape: Input 8-character installation key (cr=no change): If your keys are not readily available, CR to continue. These keys can be installed at the completion of the update by entering the following commands from the ADMIN> prompt: ADMIN>install_key /etc/level/DSS ADMIN>install_key /etc/level/ADS ______________________________________________________________ 4. Set your prefix to '/origin/r21a'. Ex: admin>cd /origin/r21a ______________________________________________________________ 5. Get into BASIC and start 256 pages. Ex: admin>basic s=256 -nr ______________________________________________________________ 6. RUN "UPDATE" If you are a new installation, this program will rename several 2.1a data files. If you are upgrading from 2.0A, this program will program will convert your 2.0A dictionary files and user files into the 2.1A files. ______________________________________________________________ Answer the following UPDATE prompts accordingly: ______________________________________________________________ A. ENTER THE DISK NAME FOR /origin/r21a/ (CR IF NONE): CR if you are installing onto drive 0; Otherwise, enter the directory name of drive 1. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg010 ______________________________________________________________ MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement __________________________________________________________________________ 2000/3000/4000 (New Installations, Installations Upgrading from 2.0A ____________________________________________________________ B. ENTER DIRECTORY OF YOUR CURRENT ORIGIN SYSTEM INCLUDING DISK NAME, CR IF THIS IS A NEW INSTALLATION: o If you are upgrading from 2.0A, enter /origin/r20a The files in the /origin/r21a/data/new will be moved into the /origin/r21a/data directory. o If you are installing a new installation, enter CR. The files in the /origin/r21a/data/new will be moved into the /origin/r21a/data directory. ______________________________________________________________ C. CR TO PROCEED WITH /origin/r21a UPDATE, CTL-IV = EXIT ____________________________________________________________ D. CR TO BEGIN UPDATE OF DICTIONARY FILES, CTL-IV TO EXIT A CR will convert your r20a ORIGIN dictionary files into r21a format. IDD CONVERSION COMPLETE. CR TO CONTINUE: ______________________________________________________________ E. INSTALL STANDALONE ORIGIN UTILITIES IN SYSTEM DIRECTORY /bin/ CR TO PROCEED, CTL-IV TO END: Install the standalone utilities if you want your users to be able to run your ORIGIN generated programs without having the ORIGIN directory in their prefix list. ORIGIN INSTALLATION COMPLETE: ______________________________________________________________ 6. Turn to section 3.2.3 Executing ORIGIN on the 2000/ 3000/4000. ______________________________________________________________ MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement __________________________________________________________________________ SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg011 2000/3000/4000 3.2.2 INSTALLATIONS UPGRADING FROM 1.3B ______________________________________________________________ 1. Upgrade your your ORIGIN dictionary files to 2.0A format. Follow the 2.0A upgrade instructions in the MAI ORIGIN 2.0A Software Announcement #143 on page 14. The dictionary conversion program "IDDCNV" described in the Software Announcement is contained on the 2.1A tape in the /origin/r21a/util directory. ______________________________________________________________ 2. Turn to Section 3.2.1 NEW INSTALLATIONS AND INSTALLATIONS UPGRADING FROM 2.0A. ______________________________________________________________ 3.2.3 EXECUTING ORIGIN ON THE 2000/3000/4000 ______________________________________________________________ 1. Set your prefix with your user directory first followed by the ORIGIN and Presentation Services directories. Ex: ADMIN>cd /usr/origin ADMIN>ad /origin/r21a /PS /PS/tools ______________________________________________________________ 2. Enter BASIC with a start size of 256 and run "pgm/ORINST". This will install your keys into the ORIGIN security file. Ex: ADMIN>basic s=256 -nr pgm=pgm/ORINST ______________________________________________________________ 3. Enter the account name "MAI.ORIGIN" and the password "ADMIN" at the Menu system Log-on. *See section 4.1 LOG-ON for more information. ______________________________________________________________ MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement __________________________________________________________________________ 2000/3000/4000 (Executing Origin On The 2000/3000/4000) ______________________________________________________________ 4. Set up your ORIGIN users as decribed in the section below. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg012 NOTE - Upgrading installations must also set up their ORIGIN users. ORIGIN 2.0A users are not converted to 2.1A due to the major security enhancements in the PS menu system. ______________________________________________________________ 3.2.4 SETTING UP A USER FOR ORIGIN ON THE 2000/3000/4000 ______________________________________________________________ 1. Create a string file using the ved command that sets your prefix and executes ORIGIN. Ex: ADMIN>ved /origin/startorigin Your string file should look like this: ---------------------------------------------- cd /usr/origin ad /origin/r21a /PS /PS/tools basic s=256 -nr pgm=ORIGIN --------------------------------------------- Note - The directory /usr/origin is just an example. Your primary directory should be the one in which you want all of your ORIGIN generated programs and data files created. ______________________________________________________________ 2. Make your string file executable using the filemodes command. Ex: ADMIN>filemodes +x +x /origin/startorigin ______________________________________________________________ 3. Make this file the initial program for the ORIGIN user in the 2000/3000 Operator Maintenance. Your initial program should look like this: 4. Initial program:/bin/command,/origin/startorigin ______________________________________________________________ MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement __________________________________________________________________________ (Setting Up A User For Origin On The 2000/3000/4000) ______________________________________________________________ 4. Set up your ORIGIN users. _____ Select Utilities from the ORIGIN main menu. _____ Select User Maintenance Make the ORIGIN account name the same as the system log-on account name. * Please refer to the MAI ORIGIN Systems Support SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg013 Manual M7510A for more information on user log-on. ______________________________________________________________ 5. Set up your ORIGIN System Parameters. _____ Select Utilities from the ORIGIN main menu _____ Select System Administrator Utilities The password is ADMIN. _____ Select ORIGIN System Parameters Maint _____ Enter a Work Files Node. This node will be the directory in which all of your temporary ORIGIN file will be created. Normally, this node is "/origin/r21a/work/". ______________________________________________________________ MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement __________________________________________________________________________ NEW FEATURES AND ENHANCEMENTS 4.1 LOG-ON 4.1.1 ORIGIN Menu System Log-on A menu system log-on has been added to insure that only valid ORIGIN users may log on to ORIGIN. This log-on prompts the user for an Account Name and Password. The Account name defaults to the system WHO variable. Here is an illustration of how the Menu System Log-on screen appears on the MPx: ______________________________________________________________ 07/21/87 MAI Basic Four 1:30 PM MENU SYSTEM LOG-ON ______________________________________________________________ ACCOUNT NAME: MAI.ORIGIN PASSWORD : ______________________________________________________________ 4.1.2 ORIGIN User Log-on The user log-on screen has been enhanced in both display and function. The following features have been added to the log-on: o Default Project Code o A 30 character description for Project Code. o The PROGRAM NODE and DATA NODE now display. These directories are where your generated programs and data files will be created. These nodes are user selectable at log-on. The default is your primary node. o ORIGIN now checks the terminal type you are using and SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg014 displays only the your terminal type plus the PT-4301. MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement __________________________________________________________________________ (ORIGIN User Log-on) Here is an illustration of how the ORIGIN log-on screen appears on the MPx: ______________________________________________________________ 07/21/87 MAI ORIGIN Data Management System 4:30 PM MAI ORIGIN USER LOG-ON ______________________________________________________________ 1. USER CODE : MAI MAI ORIGIN 2. PROJECT CODE : ABC ABC'S PROGRAMS 3. DATA BASE : XYZ XYZ COMPANY'S IDD FILES 4. TERMINAL TYPE : 04 EVDT (4312) 5. LANGUAGE : ENG ENGLISH 6. DATA NODE : (DISK).CLASS. 7. PROGRAM NODE : (DISK).CLASS. ENTER NAME OR NUMBER TO MODIFY ______________________________________________________________ MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement __________________________________________________________________________ 4.2 PRESENTATION SERVICES ORIGIN now uses Presentation Services to keep in line with the single look and feel for all MBF products. The MENU GENERATOR option has been replaced with Presentation Services option MENU BUILDER, and the USER HELP TEXT GERNERATOR has been replaced with HELP TEXT BUILDER. Customers may still use their existing menu programs, but they may only be modified using ORIGIN 2.0A. Here is an illustration of the ORIGIN main menu. ---------- ORIGIN Main Menu ----------- Integrated Data Dictionary Executive Query Manager Decision Support Manager Technical Documentation Utilities Menu Builder Help Text Builder Report Program Generator Application Generator --------------------------------------- SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg015 F1 F2 F7 F8 F9 F10 CONSOLE CHG LOG STACK IDD HELP LOG OFF Please refer the Presentation Services User Manual M7561 and to the MAI ORIGIN System Support Manual M7510A for information on how to use the new menu system. 4.3 DISTRIBUTIVE PROCESSING Using MAGNET~ Distributive processing enables your Generated Applications, Reports, and Queries to access data stored on alternate directories and remote systems. If you want to access remote systems, you must have MAGNET installed on your system. For information on MAGNET, please refer to the MAGNET BOSS/VS User Reference Manual M6363 or the MAGNET BOSS/IX User Reference Manual M6360. MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement ____________________________________________________________________________ (DISTRIBUTIVE PROCESSING Using MAGNET~) To enable Distributive Processing, you must set the following 2 options: 1. Data Base Table Maintenance 2. Distributive Processing Allowance Flag Programs generated on a level prior to 2.1A must be regenerated to take advantage of this new feature. NOTE - MULTI-KEYED files are not supported through Distributive Processing at this time. 4.3.1 Data Base Table Maintenance This program enables you to create and maintain the translation tables used for Distributive Processing. These tables are string files on the 2000/3000/4000 and serial files on the MPx. Their format is described in the MAGNET BOSS/VS User Reference Manual M6363 and the MAGNET BOSS/IX User Reference Manual M6360. The Data Base Table Maintenance option is accessed from the ORIGIN DATA DICTIONARY MAINTENANCE menu. For instructions on how to use this option, please refer to the MAI ORIGIN System Support Manual M7510A. 4.3.2 Distributive Processing Allowance Flag This flag determines which generated programs may use Distributive Processing. It must be set before generating your program. The following prompt has been added to both the Application Generator and the Report Generator Function Maintenance option: MAI MAGNET ALLOWED: SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg016 Y - Distributed Processing is ALLOWED for this program. N - Distributed Processing is NOT ALLOWED. This option will not be available if you are using multi-keyed files or if MAI MAGNET is unavailable. o To set this flag for an application program, access the PROGRAM FUNCTION MAINTENANCE option from the Application Generator menu. o To set this flag for a Report or Query, access the REPORT FUNCTION MAINTENANCE option from the Report Generator menu. MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement ____________________________________________________________________________ 4.3.3 Runtime Use of Distributive Processing If an application, report or query program was generated with the distributed processing flag set to "Y" and there is more than 1 table available, the following screen will display when the program is executed. ________________________________________________________ SELECT DATA BASE TABLE TO USE 1. *XXXXXXXXXXXXXX 3. XXXXXXXXXXXXX 2. XXXXXXXXXXXXXX SELECT ITEM NAME OR NUMBER "." TO SELECT, CR TO ACCEPT, CTL-IV TO EXIT ________________________________________________________ The X's represent the data base tables created in Data Base Table Maintenance. 4.4 INTEGRATED DATA DICTIONARY 4.4.1 File Name The FILE NAME field is NO longer the actual file name on the system, it is now used for reference purposes only. The field DEFINED NAME has been added to FILE/RECORD LAYOUT maintenance to enter the actual file name on the system. 4.4.2 Extended File Names The field DEFINED NAME has been added to the dictionary to enable you to use extended file names. You may now enter up to 30 character filesnames. 4.4.3 Multi-Keyed File Support The following areas have been added or changed to accomodate the Multi-keyed file type: o FILE TYPE o ALTERNATE KEYS SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg017 o COMPOSITE Field Type o The Removal of RECORD RECOGNITION RULES (For Multi-keyed files only) MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement ____________________________________________________________________________ (INTEGRATED DATA DICTIONARY) Multi-Keyed FILE TYPE Multi-keyed files can now be defined, created, and modified in the Integrated Data Dictionary. MULTI-KEYED is the default file type when you define files in the dictionary. If the multi-keyed file you define in the dictionary exists on disk, then the dictionary definition will be verified against the file. If the definition does not match the file on disk, you will be given the option to update the disk file or to update file definition in the dictionary. 4.4.4 Alternate Keys Alternate keys may now be defined, created and modified in the Data Dictionary. These keys are used by both Application Generator programs and Report Generator programs. You may add or drop alternate keys without having to modify or re-generate your application and report programs. ALTERNATE KEYS are supported with MULTI-KEYED files ONLY. 4.4.5 Composite Item Type This new item type has been added to the dictionary to enable you to create a multi-item key that can be used as your primary or alternate key. Example: COMPOSITE SAMPLE + COMPOSITE items are supported with MULIT-KEYED files ONLY. MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement ____________________________________________________________________________ (INTEGRATED DATA DICTIONARY) 4.4.6 Order Entry Files The Order Entry file type has been added to the dictionary. When you define a file as an Order Entry type, the key size will not display because it is determined when you use this file with AG and RG programs. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg018 Note - Sort files for Order Entry Files are not supported. 4.4.7 Numeric Items Now Allowed as Keys Numeric items are now allowed as keys. ORIGIN will write these items to the file as fixed length strings using the mask to determine its' length. As a result, 'X' type and 'N' type items have been combined. NOTE - When using a numeric as a key, you should give a mask of all zero's. Ex: 0000.00 4.4.8 File Examine Utility This utility enables you to examine the actual data in the files defined in the dictionary. This utility is helpful in determing whether your dictionary layout matches the actual file layout. 4.4.9 Alternate/Duplicate Keys in File/Record Layout Printing A list that contains Alternate keys and whether or not duplicates are allowed has been added to the File/Record Layout Printing option. The format is shown below: ALT / DUP KEYS: XXXXXXXX XXXXXXXXXXXXXXXXXX XXXXXXXX XXXXXXXXXXXXXXXXXX 4.4.10 Freeform Text in File/Record Layout Printing You may now print up to 80 characters of freeform text at the bottom of Record/Layout Printing. Text in this field is automatically centered when printed. It is normally used for entering a customer's company information. Ex: ABC Company's File Layouts - DO NOT COPY MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement ____________________________________________________________________________ 4.5 REPORT GENERATOR 4.5.1 Runtime Numeric Derived Items Numeric items may be created at run-time from other numeric items, literal numeric values, or a combination of the two. Up to 10 items may be added, subtracted, multiplied, or divided. Please refer to the MAI Business Data Report Program Generator User Guide M7511B for instructions on how to use this new feature. 4.5.2 Support of Spooler Options The spooler options of CLASS, NUMBER OF COPIES and PRIORITY have been added to the report option selector when SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg019 choosing either LP, P*, or P#. Once the report has finished, the spooler will take control of the print request. If the output device selected is a valid spooler device, the following prompts will display: SPOOL OPTIONS - CLASS: A COPIES: 1 PRIORITY: 5 4.5.3 DOES NOT CONTAIN option for Report Conditions A DOES NOT CONTAIN option has been added to report conditions to determine if a record should be printed or displayed if it does not contain the user specified characters. 4.5.4 Multi-level User Defined Breaks User defined breaks can now have more than 1 level. For each item in the user defined sort the user may break and/or page break. This break will function for both an Executive Query and a Standard Report. The user may sub-total on each break item until sub-total is not chosen. Example: A user selects items <3>+<2>+<5> to sort. If he wants to sub-total/break on item <5>, he must also sub- total and break on items <3> and <2>. MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement ____________________________________________________________________________ (REPORT GENERATOR) 4.5.5 Summary Reports This new option enables user to print total lines only or totals after detail for fixed format reports. To use the summary feature, select REPORT SUMMARY from the REPORT OPTIONS SELECTOR. The following prompt will display: ENTER 'CR' FOR STANDARD REPORT, 'CTL-I' FOR SUMMARY ONLY, 'CTL-III' FOR SUMMARY AFTER DETAIL Here are examples of each type of report: Standard Report: Summary Report with Detail: ___________________________ ___________________________ detail detail detail detail detail detail detail detail detail detail detail detail total total total detail detail detail detail detail detail detail detail detail detail detail detail break total total total total total break total total SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg020 ___________________________ final final final __________________________ Summary Only: ___________________________ break total total break total total final final final ___________________________ MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement ____________________________________________________________________________ 4.5.6 Start/Stop Key Entry Display The key structure for selecting the range in a report now displays to aid the user in making the selection. The description of the key is displayed above the area for entry. The entry itself will be by the individual parts that comprise the entire key. Example: REPORT START KEY: ... REPORT START KEY: ...... 4.5.7 Start/Stop Key Prefix A fixed key prefix may now be specified before a report is generated. This new feature will help limit keystrokes at run-time for a report. The key prefix may be a literal value, or the result of a derived or related file item. Here is an example of using a key prefix: You have a file where the key is made up of + and the company code is determined by information in a related file. By using the related item as the key prefix, the user would have to only enter the customer code in the start and stop key at run time. To create a key prefix, o Select the REPORT FUNCTIONS option from the report menu. o Answer "Y" to the START KEY or STOP KEY option. The following prompt will display: ENTER KEY ITEM OR NUMBER OF ITEM THAT WILL BE ADDED TO THE BEGINNING OF THE KEY. CTL-I = GO FORWARD, SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg021 CTL-II = PREVIOUS FIELD, CTL-III = DEFAULT Normally, you would enter a related item or a derived item input. For information on derived item inputs and related items, please refer to the Business Data Report Program Generator User Guide M7511B. MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement ____________________________________________________________________________ 4.6 APPLICATION GENERATOR 4.6.1 Conditioning Maintaining conditions on items has been greatly enhanced. You can now maintain the condition logic for each item. When you select Condition Number from Item Maintenance, the following screen will display: _________________________________________________________________ ERROR MESSAGE ## WHEN CONDITION OPERATION SKIP TO INPUT _ 01 1 = BEFORE INPUT, 2 = AFTER INPUT I = INSERT LINE, D = DELETE LINE _________________________________________________________________ 4.6.2 Skipping Display Only Fields Carriage returns and CTL-II's will now skip Display Only Fields. 4.6.3 Alpha/Numeric Masking for String Fields Alpha numberic masking is now available for STRING type items. Here are the allowed character types: A - Alpha characters between a and Z # - Numeric characters between 0 and 9 X - Any characters 4.6.4 Expanded Sub-Menu Descriptions Sub-Menu descriptions have been expanded from 15 characters to 30 characters. MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement ____________________________________________________________________________ 4.6.5 Verification Windows for Inputs The new Verifcation Window will look-up all valid input items from a related file or from a string expression. It will then SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg022 display these items on a menu and let you select one for your input entry. For information on how to use this feature, please refer to the MAI ORIGIN Application Generator User Guide M0060A and the MAI ORIGIN Application Generator Technical Reference Manual M7512A. 4.6.6 Remove from Screen Option on Derived Items You may now remove derived items from your screen without exiting screen maintenance. 4.6.7 Input Routine Optimized The input routine for file maintenance programs has been optimized, thereby reducing the total overhead of each program. 4.6.8 Insert/Delete Order Entry Lines You may now insert and delete multiple order entry lines. The following prompt will display during entry/maintenance of order entry lines: ENTER LINE NUMBER TO MODIFY ('D'=DISPLAY LINES): CR = CONTINUE, CTL-I = NEW LINE, CTL-II = DELETE LINE, CTL-III = INSERT LINE Up to 99 lines may be inserted in a single insert session. The inserted lines are written to temporary lines and are updated to your file when insert mode is terminated. For information on how to use this feature, please refer to the MAI ORIGIN Application Generator User Guide M0060A and the MAI ORIGIN Application Generator Technical Reference Manual M7512A. MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement ____________________________________________________________________________ 4.7 TECHNICAL DOCUMENTATION The FORMATS ONLY option has been added to the 'Documentation of Individual Programs' selection. This enables you to print or display just the FILE/RECORD LAYOUT REPORT of multiple user selected programs within a specific project code. Once you have completed your selection of programs to document, the following prompt will display : 'CR' = COMPLETE DOCUMENTATION, 'CTL-I' = FORMATS ONLY 4.8 GENERAL IMPROVEMENTS 4.8.1 Creation of Derived Items in Edit Mode Derived items may now be created while in Report Line Maintenance and Screen Maintenance. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg023 This feature saves the user time and key strokes by eliminating the need to exit the edit screen. 4.8.2 Related Files - Next Record If Missing Option The 'Next Record If Missing' option has been added to File Relationship maintenance in both the Report and Application generators. If the key to a related file is missing, the next record will be read. 4.8.3 Work Node for Temporary Files You may now specify a temporary work node/directory for your User Code work files. This node/directory is specified in the ORIGIN System Parameters selection on the Utilites menu. 4.8.4 Release Level Comment Added to Generated Programs The release level of the software has been added to a REM statement in the beginning of each generated program. 4.8.5 Use of Arrow Keys in Selectors Arrow keys may now be used at the ORIGIN selectors. MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement ____________________________________________________________________________ (General Improvements Continued) 4.8.6 Summarize Data Subroutine The new subroutine "SUM" will count the number of records in a related file or summarize the value of a field. This subroutine can be used in both the application and report generators. The value returned from this subroutine is a string. To use this subroutine, Select Item Maintenance in your generator. Create a Derived Item Expression using the following format: SUM("file name","key prefix","field #") o If you want to count records in a file you should enter "0" for the field number. o If you want to read all records in a file you should enter "" for the key prefix. NOTE - All of the items in this expression are strings, so if you use literal values you must have quotes around them. Example: SUM("file1","AAA","5") SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg024 The following explains the parameters used in this subroutine. ______________________________________________________________ filename is the name of file that you want to summarize. key prefix is the KEY item that determines which records in the related file should be summarized. This item must be part of the key to the related file. Here is an example of counting all employees in each department where the key to the file is equal to a department number + an employee number: SUM("EMPFIL",,0) ____________________________________________________________ MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement ____________________________________________________________________________ (Sumarize Data Subroutine Continued) ______________________________________________________________ (key prefix continued) NOTE - If the key prefix item is not a string, you must convert it using the STR function. Example: SUM("EMPFIL",STR(),0) ______________________________________________________________ field # is the item that determines which field should be summarized. o To count the number of records read, enter "0" o To summarize the value of a field, enter the field number. o To summarize the value of a sub-string field enter "field, start byte, length". ______________________________________________________________ MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement ____________________________________________________________________________ (General Improvements Continued) 4.8.7 File Acceptance Key Changed from CTL-III to CR SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg025 The acceptance key to use a file that already exists on your system has been changed from a CTL-III to a CR. The old 2.0A prompt displays : THIS FILE ALREADY EXISTS (CR = ENTER AGAIN, CTL-III USE THIS FILE): The new 2.1A prompt displays : THIS FILE ALREADY EXISTS (CR = USE THIS FILE, CTL-II ENTER AGAIN): MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement ____________________________________________________________________________ RELATED DOCUMENTS Manual Number Description _ M0058A MAI ORIGIN~ User Guide for Running Reports and Programs M0060A MAI ORIGIN~ Application Generator User Guide M7510A MAI Business DATA~ System Support Manual M7511A MAI Business DATA~ Report Program Generator User Guide M7512A MAI ORIGIN~ Application Generator Technical Reference Manual M7561 Presentation Services User Guide M7573A MAI Business DATA~ Report Program Generator Technical Reference Manual MAI ORIGIN~ 2.1A ADS / MAI Business DATA Software Announcement ____________________________________________________________________________ HELPFUL HINTS GENERAL: o An ESCAPE at any PS menu will return you to your log-on menu. o ADMIN is the security password in consolelock. o Local Distributive Processing can be used without having MAGNET~ installed on your system. o Remember to RE-INITIALIZE your program from the IDD if you add or delete an item to the multi-keyed file in the IDD. INTEGRATED DATA DICTIONARY o The maximum number of items for a composite field is 8. o Numerics are not allowed as the first character of the 6 character SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg026 ORIGIN FILE NAME. o DO NOT use numerics in defined file names if your are creating your files to be used with the Application Generator. APPLICATION GENERATOR o You may have a maximum of 199 derived items 160 input items. If you have over 50 input items, your should set the SMALLER PROGRAM option to yes and enter a PARAMETER FILE name in Program Parameter Maintenance. o Expressions displayed in an ORDER ENTRY program will move down with each input. REPORT GENERATOR o You may have a maximum of 299 items in a report. o To print expressions in the header of the FINAL TOTAL page of a standard report, you should precede the item number with an "*" in the report heading. Ex: COMPANY NAME - <*003> ORIGINATOR: Tono Tiangco SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB011 Pg027 FIB 00012 03/28/88 *** MAI ORIGIN~ Support Grid [ WPSF 440 ] *** The following tables show what operating systems and levels of OMS and MAI OFFICE~ are supported with MAI ORIGIN~. MAI ORIGIN / OPERATING SYSTEMS ___________________________________________________________________ ORIGIN MPx 2000/3000/4000 1800 _LEVEL OS Level OS Levels OS Level _ _ 1.3B 8.4A or higher 7.1A or higher Not Supported_ _ 2.0A 8.4E and 8.5C or higher 7.2A or higher TBD _ _ 2.1A 8.6A or higher 7.3A or higher Not Supported_ MAI ORIGIN / OMS / MAI OFFICE ____________________________________________________ ORIGIN OMS MAI OFFICE MAI OFFICE _ LEVEL 8.3.1 3.1A 3.2A * _ _ 1.3B YES NO NO _ _ 2.0A YES YES YES _ _ 2.1A NO NO YES _ * MAI OFFICE 3.2A is supported only on 7.4A and later. ******************************************************************************. * NOTE: - Please place a copy of this bulletin into the * * ORIGIN Helpful Hints Guide * ******************************************************************************. ORIGINATOR: Toni Tiangco SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB012 Pg001 FIB 00013 06/23/88 *** Origin 2.1A Notes and Problems [ WPSF 454 ] *** MAI Basic Four, Inc. announces the availability of MAI ORIGIN~ Application Development System and MAI Business DATA~ Version 2.1A on the MPx and 2000/3000/4000 Series. The required Operating System levels are 8.6/9.6, 7.3/7.4A and above. Version 2.1A will not be a supported product on the MAI 1800 System. Below are Warnings and Cautions for version 2.1A. Please keep a copy of this Field Bulletin in your ORIGIN Helpful Hints Manual. GENERAL: o EXPRESSIONS - You must completely re-enter an expression if it is greater than 160 characters and you change any items after its initial creation. o Masks based on a derived item must NOT have a greater size than the item using the mask. o ALWAYS re-enter an expression if you receive a "BAD EXPRESSION" message. An error 1 may occur in statement 3611 of program IDDDIM if you don't. o After Upgrading the O/S you may get the message "MESSAGE FILE CANNOT BE FOUND". Run ".PS.INSTALL" to reinstall the PS files under the System Node. o When expanding a file, DO NOT try to input a number that is obviously too large. INTEGRATED DATA DICTIONARY o DO NOT use a numeric as the first character of a data item in a multi-keyed file. o DO NOT use reserved BASIC words (such as RELEASE, WHO, CLASS, etc.) as data items descriptions in multi-keyed files. o DO NOT USE spaces in item names in Multi-keyed files. It can cause error 41's if those items are used as a key item. o DO NOT use variable length fields in Multi-keyed files. o DO NOT CTL-II for PREVIOUS on the last page of the Data Impact Report. It will hang and you must escape to stop it. o DO NOT use numerics in defined file names if you are creating your files to be used with the Application Generator. o You should ALWAYS make your numeric mask zero filled when you are using a numeric item as part of the key in a Multi-keyed file. Ex: USE --> 000.00 DO NOT USE --> ##0.00 In Multi-keyed files, numeric keys are always written to the file as zero filled, regardless of the mask specified in the IDD. However, in OE programs and programs with related files the mask specified in the IDD is used and may cause records not to be found. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB013 Pg001 o The maximum number of items for a composite field is 8. o Numerics are not allowed as the first character of the 6 character DEFINED FILE NAME, but are allowed in the FILE NAME. o When copying files in the IDD, you may sometimes receive the incorrect message "THIS ITEM DOES NOT MATCH GLOBAL DEFINITION". Ignore this message during the copy. o DO NOT create file relationships against Order Entry files in Views; create them in the application and report generators. APPLICATION GENERATOR o DO NOT use a default in a Word Processing field. An error 47 may occur. o DO NOT press keys on your terminal while you are doing a CTL-III to print your screen. An error 47 might occur at statement 136. o Expressions displayed in an ORDER ENTRY program will move down with each input of an order entry line. o The Display of Existing Programs in the Application Generator does not always display the correct titles. Use the Generated Programs Report option instead. o If you have 'Special Modify' set to 'Y', do not select Inquiry and Modify directly prior to selecting Special Modify. If this condition exists, a loop can occur. REPORT GENERATOR o The REMOVE RECORDS option in Batch File Update does not remove associated SORT files records. o An error 47 may occur when you save report options with 7 or more conditions for the first time. The next time you run the report, it will run fine - the saved options will display and work properly. o To change the Print Sequence Description for Main File, go into File Relationship Maintenance and modify number one, File Reference name. ............................................................................... 454 Addendum-1 An error 17 in program rt/ENGNNR at line 7534 may occur on the 2000/ 3000/4000 system when attempting to print an MAI Business DATA~ generated report to a printer. This occurs because the report program, generated under MAI ORIGIN~ 2.1A, is trying to default to a 'system' class, which is not resident on the 7.4 O/S. To correct this error, go into pparams and create a class called 'system' and accept all the defaults. ............................................................................... 454 Addendum-2 During an MAI ORIGIN~ 2.1A upgrade on the MPx system a loop may occur at statement 155 in the program UPDATE. This is due to the absence of parenthesis () around the family name. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB013 Pg002 To ensure that the loop does not occur, please be sure to specify the parenthesis () around the family name when prompted by: ENTER THE FAMILY NAME FOR .ORIGIN.R21A.: The above prompt is the first prompt the user will see when running UPDATE. ............................................................................... 454 Addendum-3 A problem has been discovered with MAI ORIGIN~ Level 2.1A on BOSS/IX systems. The problem occurs when the "Terminal-Editor Key Association" option is chosen from the Utilities, Screen Editor Function Menu. When this option is chosen, a message "AN ERROR 026 OCCURRED AT STATEMENT 7106, CR = CONTINUE" is displayed. The program will not allow the user to get out of the error condition and the process running this option must be killed by another task. The fix for this problem is as follows: 1. Load the program "/origin/r21a/pgm/ORITC3" 2. Modify statement number 7106 as follows: 7106 TTYPE$=INFO$(1,POS(CHAR(10)=INFO$)-1,INFO$=INFO$(POS(CHAR(10)= 7106: INFO$)+1),FELD=FELD+1;IF FELD<3 THEN GOTO 7106 ELSE DIM INFO$(0); 7106: IF TTYPE$ install cs DSS ADS EPS to /mntdir ** NOTES: Only specify DSS if ADS was not purchased. Include the OTU save set if International installation. Do not install the keys when prompted after the install. Install the keys using the install_key command described in step d. b. If the directory /etc/level does not exist on the root directory, you must first make that directory using the following commands: ADMIN> makedir /etc ADMIN> makedir /etc/level c. Move the /mntdir/etc/level files to the root directory. ADMIN> move /mntdir/etc/level/* /etc/level/ -v d. Install the public keys using the following commands: ADMIN> install_key DSS ADMIN> install_key ADS e. Change your prefix to look at ORIGIN and then go into BASIC. ADMIN> cd /mntdir/origin/r21a ADMIN> basic s=256 -nr f. Load the "UPDATE" program and make the following modifications: >LOAD "UPDATE" >137 REM".... >RUN You will be prompted,'ENTER THE DISK NAME FOR /origin/r21a/ (CR IF NONE):' enter :/mntdir SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB014 Pg001 'ENTER THE DIRECTORY OF YOUR CURRENT ORIGIN SYSTEM INCLUDING DISK NAME, CR IF THIS IS A NEW INSTALLATION:' enter 'CR'. g. After the update is complete, the PS files must be moved to the root: ADMIN> makedir /PS ADMIN> makedir /PS/tools ADMIN> move /mntdir/PS/* /PS/ -r -v ADMIN> basic s=256 -nr h. Load the ORIGIN program and modify statement 350 as follows: >350 LET LOGNAME$="/mntdir/origin/r21a/ORIGINSTAT", OPNAME$=USERCODE$; REM"OPNAME$=ACCTNAME$(1,POS(" "=ACCTNAME$+" ")-1 CAN'T BE >8 CHARS >SAVE i. Run "pgm/ORINST" to update the security keys from the "/etc/level" file to the "rt/ORILGF" file. 4. Numerics are not being converted properly during an upgrade from 2.0A to 2.1A with ASG data dictionaries using program "PGM.IDDCNV". Make the following changes to this program to correct the problem: 1621 IF POS(A0$(24,1)="NF")=0 THEN GOTO 1630 ELSE IF POS(" "=A4$+" ")=1 THEN GOSUB 7000 1622 ISIZE=POS(" "=A4$+" ")-1;IF A0$(24,1)="F" AND POS("."=A0$)>1 THEN ISIZE=ISIZE-1 1623 MASK$=A4$ 1624 FOR COUNT=1 TO POS(" "=MASK$+" ")-1 1625 IF MASK$(COUNT,1)="," THEN ISIZE=ISIZE-1 1626 NEXT COUNT 1627 A0$(25,4)=STR(ISIZE:"0000") 7000 REM"BUILD A MASK" 7010 LET INTPART=NUM(A0$(25,1)),FPART=NUM(A0$(26,1)) 7020 IF INTPART>0 THEN DIM A4$(INTPART-1,"#");LET A4$=A4$+"0" 7030 IF FPART>0 THEN LET A4$=A4$+".";DIM TMP$(FPART,"0");LET A4$=A4$+TMP$ 7040 RETURN II. INTEGRATED DATA DICTIONARY (IDD) 1. Error Message, "Illegal File Name" in IDD File Maintenance when defining a file on 7.4. Modify the following line of code in "pgm/ORICHC": 0090 IF POS("."=J$)<1 THEN E=NUM(J$,ERR=121) ELSE GOTO 121 2. Error message "File Cannot Be Found In Current Prefix List" when attempting to examine a file from IDD file maintenance. The workaround for this is to fully specify the file name at the defined name prompt or to have the file in the first directory of the user's prefix list. III. REPORT PROGRAM GENERATOR 1. Problem with Compact Dates in ORIGIN 2.1A. Modify the following line of. code in PGM.ENGRP7, PGM.ENG6, PGM.ENG60E: 104 IF CHAR(128)=CHR(128) THEN INC=129 ELSE INC=1 2. START/STOP keys will look for the literal values "BEGINNING" and "END" when specifying beginning and ending. There are code changes to correct this but they are quite extensive. If you do encounter this problem, please contact FPS so that a copy of these changes can be sent to you. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB014 Pg002 3. On the MPx machines, an error 26 at line 1020 in a generated report can. occur when using Multi-keyed files that contain composite fields. To correct this problem, please modify the following line of code in program "PGM.ORINR2": 1215 IF LEN(D3$)<5 OR (INITFRM<>5 AND INITFRM<>2) THEN D3$="00";GOTO 1230 4. On ORIGIN 2.0A, conditions with expressions greater than 160 bytes were maintainable. On ORIGIN 2.1A the expressions length is checked not to exceed 160 bytes. In order to maintain larger expressions in condition maintenance, make the following modifications to "PGM.ORIEXP". 0087 IF E1=2 THEN MAXSIZ=480 ELSE MAXSIZ=160 4015 DIM BLANKS(MAXSIZ) 6930 DIM BLANK$(MAXSIZ);IF POS(BLANK$=E1$+BLANK$)-1 > MAXSIZ THEN DIM BLANK$(0);E9=1680;F6$="",E$=E1$;GOTO 6920 ELSE DIM BLANK$(0) 7846 DIM BLNK$(MAXSIZ);E7$=E7$(1,POS(BLNK$=E7$+BLNK$)-1);DIM BLNK$(0) 5. Report programs that have been originally created on 2.0A and then upgraded to 2.1A with Report lines greater than 1000 characters, may generate an error 26 at line 6010 and an error 20 at line 6011 in the generated report. The reason this occurs is because ORIGIN is trying to break up the PRINT statement into two PRINT statements and will break the line at the first "," after the 1000th character. If this happens to be part of the subscript then the errors will occur. Please make the following changes to the program "PGM.ORIN2": 1170 IF LEN(S9$)<=1000 THEN PRINT (4) STR(J:"0000")+S9$;GOTO 1190 1172 P0=1000 1175 P=POS("'"=S9$(P0));SYNTAX STR(J:"0000")+" "+S9$(1,P0+P-1),ERR=1176;. GOTO 1177 1176 P0=P0+P;GOTO 1175 1178 PRINT(4) STR(J:"0000")+S9$(1,P0+P-1);J=J+1,S9$="PRINT(7,ERR=8200)"+ S9$(P0+P);GOTO 1170 IV. APPLICATION GENERATOR 1. ORIGIN 2.1A does not allow spaces in conditions at run-time (it used to on 2.0A). The following modifications need to be made to the following programs: Program: RT.ENGNNW 2730 IF INP$="" GOTO 5000 2735 THELEN=LEN(INP$),INP$=FNS$(INP$); DIM FILLER$(THELEN-LEN(INP$), CHR(255));INP$=FILLER$,INP$=FNB$(INP$,LENGTH) 5225 IF INP=4 THEN INF01$=FNS$(INF01$) 5350 PRINT @(COL,ROW),FNB$(INP$,LENGTH),;IF INP$<>4 THEN INP$= FNB$ (INP$,LENGTH) PROGRAM: RT.ENGNNU 5080 IF LEN(D5$)<1 OR D5$(1,1)<>CHR(1) THEN D5$="'"+D5$+"'";GOTO 5110 5135 PP=POS(CHR(255)=D5$);IF PP>0 THEN D5$(PP,1)=" ";GOTO 5135 5140 LET D2$=D2$+D3$+" "+D4$+" "+D5$+" "+D6$+" " PROGRAM: PGM.ENGRP7 4736 IF LEN(T4$)>3 AND T4$(4,1)=CHR(1) THEN U2=NUM(T4$(5,3));GOSUB 7000;A$=X8$,Q=X8 ELSE A4$=T4$(4);FOR Q=1 TO LEN(A$;A$(Q,1)=A$( SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB014 Pg003 Q,1-POS(A$(Q,1)=CHR(255)))+O0$(1,POS(A$(Q,1)=CHR(255)));NEXT Q;Q =NUM(A$,ERR=4765);GOTO 4765 2. Distributed Processing on BOSS/IX systems does not work properly. The following changes should be made to program "rt/ENGSMT": 1080 IF TYPE$<>"SER" THEN GOTO 1085;REM "IF (LEVEL$="VS" AND TYPE$<> "SER") OR (LEVEL$="IX" AND TYPE$<>""STR") THEN GOTO 1085 3. Reports using Distributed Processing do not open remote files unless the file names exist on the local system. To correct this problem, the following changes should be made to program "rt/ENGNNR": 0126 LET STRTCLR=3;CALL RNODE$+U3$+"SMT",I0$,"","",CRTL$,STRTCLR,1, MAGTBL$;GOSUB 8800 4. On ORIGIN 2.0A, conditions with expressions greater than 160 bytes were maintainable. On ORIGIN 2.1A the length is checked not to exceed 160 bytes. In order to maintain larger expressons in condition maintenance, make the following modifications to "PGM.ORIEXP": 0087 IF E1=2 THEN MAXSIZ=480 ELSE MAXSIZ=160 4015 DIM BLANK$(MAXSIZ) 6930 DIM BLANK$(MAXSIZ);IF POS(BLANK$=E1$+BLANK$)-1>MAXSIZ THEN DIM BLANK$(0);E9=1680;F6$="",E$=E1$;GOTO 6920 ELSE DIM BLANK$(0) 7846 DIM BLNK$(MAXSIZ);E7$=E7$(1,POS(BLNK$=E7$+BLNK$)-1);DIM BLNK$(0) ORIGINATOR: J. Shea SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB014 Pg004 FIB 00015 02/08/89 *** ERROR 47 during add of a new input item [ WPSF 518 ] *** An error 47 may occur when attempting to add a new input item for an ORIGIN application program. This problem only occurs on the 2000, 2500, 3000, 4000 systems. The error may be reported at line 9000 of "pgm/ORIIT0" or at line 5870 of "pgm/ORIFMS". To correct this problem, the following changes underlined must be made to "pgm/ORINTO": 0012 IF POS ($00$=A$)=0 THEN DIM AT$(LEN(A$),CHR(64)) ELSE LET 0012:AT$=A$(POS($00$=A$)+1),A$=A$(1,POS($00$=A$)-1) 7414 IF LEN(A$)> 1760 THEN LET A$=A$(1,1760)+" ",AT$=AT$+$40404040$ This problem will be fixed on the next release of ORIGIN. ORIGINATOR: D. Jensen SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB015 Pg001 FIB 00016 02/08/89 *** No data displayed on ORIGIN reports [ WPSF 517 ] *** ORIGIN reports based on a Sort file will not run correctly, no data will be displayed. To correct this problem, the following changes should be made to "pgm/ORINR2" (2000, 2500, 3000, 4000) or "PGM.ORINR2" (MPx): Add the following lines: 1241 IF FILT$ <> "S" THEN GOTO 1250 1242 READ (1,KEY="##",DOM=1243) 1243 READ (1) *,*,*,*,*,*,*,*,*,*,*,VAR$ 1245 PRINT (4) "1020 "+VAR$+"(1)=Z9$;GOSUB 9101" This problem will be corrected in the next release of ORIGIN. ORIGINATOR: D. Jensen SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB016 Pg001 FIB 00017 02/08/89 *** Rel. 2.1A report function 'FNBLANK$' incorrect [ WPSF 515 ] *** A problem has been found when using the ORIGIN defined function 'FNBLANK$' as described in the MAI Business Data Report Program Generator User Guide, number M7511B, pages 5-8 and 5-9. To use this function as described, you must first make the following changes to "pgm/ENGRP7" (2000/2500/3000/4000) or "PGM.ENGRP7" (MPx): Was : 145 DEF FNBLANK$(X$,X)=X$((-X)*INT(POS(" "=X$)/X)+X+1,X) Change to: 145 DEF FNBLANK$(X$,X)=X$(X*INT(POS(" "<>X$)/X)+1,X) This problem will be corrected in the ORIGIN 2.1B release. ORIGINATOR: D. Jensen SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB017 Pg001 FIB 00018 04/18/89 *** Error 47 on line 2720 in "ENGNNW" [ WPSF 454-5 ] *** PROBLEM: An error 47 is reported at line 2720 in the program "RT.ENGNNW" (MPx) or "rt/ENGNNW" (SPx). This error occurs when selecting user conditions and CTL-I is entered to compare value to another item. FIX: To correct this problem, the following changes should be made to "ENGNNW": OLD: 2720 IF C0=1 AND INP$(1,1) <>CHR(1) THEN GOSUB 6500; 2720: GOSUB 6540 NEW: 2720 IF C0=1 AND POS(CHR(1)=INP$) <> 1 THEN GOSUB 2720: 6500; GOSUB 6540 FUTURE: This problem will be corrected on the next release. ORIGINATOR: Dale Jensen SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB018 Pg001 FIB 00019 08/31/89 *** Error 47 in ORIGIN 2.1A Generated Reports [ WPSF 454-6 ] *** PROBLEM: Error 47 at 5212 in generated report program when using item suppression. SOLUTION: Make the following modification to the generated report program: OLD: 0029 DIM O0$(240) NEW: 0029 DIM O0$(240), T4$(240) OLD: 0224 O0$=O0$+CHR(127)+$CD ...$ NEW: 0224 O0$=O0$+CHR(127)+$CD ...$; DIM T4$(240) ORIGINATOR: Jackie Shea SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB019 Pg001 FIB 00020 08/31/89 *** Errs 26, 41, 47 - Letter Generation - ORIGIN 2.1A [ WPSF 454-7 ] *** PROBLEM: Error 26's, 47's and 41's using Letter Generation with saved options. SOLUTION: Make the following code modifications to RT.ENGLG1 OLD: 0115 A10$=A0$; IF POS(CHR(1)=A0$)=0 THEN LET A1$=""; GOTO 130 NEW: 0115 A10$=A0$, A10$=A10$(1,POS($03$=A10$+$03$)-1); IF POS(CHR (1)=A0$)=0 THEN LET A1$=""; GOTO 130 OLD: 0260 LET R1$="STANDARD OPTIONS", H1$=R1$+07$(1,14), P3$=A10$ NEW: 0260 LET R1$="STANDARD OPTIONS", H1$=R1$+07$(1,14),P3$=N2$ OLD: 1551 REM "Q5$="***" NEW: 1551 J$(1,4)="YNYN" OLD: 4350 LET E=999 NEW: 4350 LET E=4350 ORIGINATOR: Jackie Shea SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB020 Pg001 FIB 00021 08/31/89 *** Upgrading 2.0A IDDs to 2.1A [ WPSF 454-8 ] *** BFMS and many other software packages ship with Integrated Data Dictionaries already defined. However, some of these are in 2.0A format and need to be upgraded to 2.1A format before they can be used with ORIGIN 2.1A. Please follow the steps below to upgrade the dictionary format: 1. NEW INSTALLATION: a. Note the path names of the IDD's set up by application software, e.g., (.BFMS.FILES). b. Install the ORIGIN product following the instructions in the ORIGIN 2.1A Software Announcement. c. After installation is complete, run "PGM.IDDCNV" (pgm/IDDCNV on SPx) The following prompts will display: o ENTER THE NODE OF YOUR 2.0A DATA DICTIONARY FILES: Enter the full path name of IDD files, e.g., (FAMILY).SWNODE.DATA. o ENTER THE NODE OF YOUR 2.1A DATA DICTIONARY FILES: Enter the full path name of ORIGIN IDD files, e.g., (FAMILY).ORIGIN. R21A.DATA. 2. UPGRADE from Previous level of ORIGIN: a. Install ORIGIN 2.1A following the installation/upgrade procedures in the ORIGIN 2.1A Software Announcement. b. Verify that old dictionaries (1.3B, 2.0A) are accessible under 2.1A before continuing with next step. c. Run "UTIL.IDDCOPY" to create a blank set of 2.1A dictionaries for the 2.0A dictionaries to be upgraded to and stored until they are merged with the current ORIGIN 2.1A dictionaries. The following prompts will display: o ENTER PREFIX OF SOURCE DICTIONARY: (FAMILY).ORIGIN.R21A. o ENTER PREFIX OF DESTINATION DICTIONARY: (FAMILY).NEWTEMPNODE. The program will automatically append .DATA. to the source node and destination nodes. When the program realizes that no dictionaries exist in the destination node, the following prompts will display: o DICTIONARIES DO NOT EXIST WITH THIS PREFIX (CR=CREATE, CTL IV=RE- ENTER) to create a new set of empty 2.1A dictionaries o SELECT DATA BASE TO COPY All current data bases in ORIGIN 2.1A will be displayed. Do NOT SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB021 Pg001 select a data base at this time. CTL IV to exit d. Follow step 1c to upgrade the application software's 2.0A dictionaries to the 2.1A dictionaries under (FAMILY).NEWTEMPNODE.DATA. e. To merge the newly converted dictionaries in .NEWTEMPNODE.DATA. with the .ORIGIN.R21A.DATA. dictionaries, run "UTIL.IDDCOPY" The following prompts will display: o ENTER PREFIX OF SOURCE DICTIONARY: (FAMILY).NEWTEMPNODE. o ENTER PREFIX OF DESTINATION DICTIONARY: (FAMILY).ORIGIN.R21A. The program will automatically append .DATA. to the source node and destination nodes. o SELECT DATA BASE TO COPY All current data bases in (FAMILY).NEWTEMPNODE. will be displayed. Select the applicable data bases that need to be merged into ORIGIN 2.1A dictionaries. ORIGINATOR: Jackie Shea SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB021 Pg002 FIB 00022 08/31/89 *** Error 42 in ORIGIN 2.1A Order Entry [ WPSF 454-9 ] *** PROBLEM: An ORIGIN ADS application with an associated Order Entry program may produce an error 42 if an item defined in the Order Entry file requires a precision to be set other than 2. SOLUTION: This is caused by a statement in the Order Entry program that is no longer there. The statement that sets the precision overwrites that line. The line number that is overwritten is 17. This line would usually dimension several variables that are used in the Order Entry program. To correct this problem, either of the following changes may be made. Modify the Order Entry shell program "PGM.ENG6OE" (MPx) or "pgm/ENG6OE" (SPx), line 17 so that it becomes statement 18. Regenerate your application program after making this change. or If you don't want to regenerate your program, hard code the the statement below, in your Order Entry program at line number 18. 18 U3$="ENG",RNODE$="RT"; DIM X(12), Z(23); IF CHR(65)= 18:"A" THEN RNODE$="rt/" ELSE RNODE$=RNODE$+"." ORIGINATOR: Jackie Shea SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB022 Pg001 FIB 00023 08/31/89 *** Error 47 in Program RT.ENGNNR at line 8756 [ WPSF 454-10 ] *** PROBLEM: An error 47 will occur in program RT.ENGNNR at line 8756, when a user specifies a short start key while running their ORIGIN generated report. SOLUTION: Please make the following change to RT.ENGNNR: 5001 IF C0$(POS("Y"=P6$)*16-15,1)="M" THEN C5$=C0$(POS("Y"= P6$)*16-14,15),C5$=C5$(1,POS(" "=C5$+" ")-1),F8=POS (C5$=A0$,15) ,W9=F8; IF F8>0 THEN C5$="Y",F8= (F8+14)/15,F8=NUM(A1$(F8*5-3, 4)),W99=F8; REM " GOTO 5009 ORIGINATOR: Jackie Shea SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB023 Pg001 FIB 00024 10/11/90 *** ORIGIN 2.1A Problems [ WPSF 454 A-11,12,13 ] *** o PROBLEM: MPx System MK file updates in ORIGIN cause data to be lost if the file being updated and the temporary file are on different families. An error 17 will occur and when the user ends the session, the temporary file is deleted and the main file has already been deleted. The problem occurs in ENGCMD because it tries to do a rename of the temporary file to the permanent file and you cannot do a rename across families. There is a check for a family name but IDD4AL never assigns a fully qualified path name to the temporary file so the check is not successful. SOLUTION: PGM.IDD4AL 1210 UN1=UNT;OPEN(UN1)TEMPNAME$;TEMPNAME$=ATTR(UN1, "NAME") o PROBLEM: (SPx system only) Error message, 'MESSAGE PROGRAM OR FILE CAN'T BE FOUND .. CHECK PREFIX', displays blinking when logging onto ORIGIN. to continue logs user off system. SOLUTION: User has started ORIGIN with 64 pages of memory or less. ORIGIN MUST be started with 256 pages. o PROBLEM: (SPx system only) Error message, 'AN MS ERROR HAS OCCURRED - UNKNOWN FATAL ERROR', displays after successfully logging onto ORIGIN and attempting to select one of the Main Menu items. SOLUTION: User has started ORIGIN with 128 pages of memory. ORIGIN MUST be started with 256 pages. o PROBLEM: Possible error 525 (PCDUMP) at line 5010 in RT.ENGTRM selecting ORIGIN generated program off an application menu or using Letter Generator. SOLUTION: Add the following line of code in RT.ENGTRM 5001 INFO$=""; GOTO 5020 o PROBLEM: Error 20 at 5511 in generated application program when defaulting an input to previous value (/PRE). SOLUTION: Make the following modifications to PGM.ORI501: 8491 CURRDIM$=DM$,XX$=DM$(10),DM$="5511 DIM ", IDDDIM$=""; READ (6, KEY=A0$+"5512 ",DOM=8492) 8493 IF POS(","=XX$)=0 THEN GOTO 8496 ELSE VAR$=XX$ (1,POS(","=XX$)-1), XX$=XX$(POS(","=XX$)+1) ADD 8496 IF POS("="=CURRDIM$)=0 THEN RETURN ELSE XX$= CURRDIM$ SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB024 Pg001 ADD 8497 IF POS("="=XX$)=0 THEN PRINT (2)"5512 "+ IDDDIM$; GOTO 8499 ELSE VAR$=XX$(POS("="=XX$) +1),XX$=XX$(POS("="=XX$)+1),VAR$="X8$="+VAR$ (1,POS("="=VAR$))+"X8$", XX$=XX$(POS("="=XX$) +1), VAR1$=VAR$(5,POS(";"=VAR$(5))-1); IF POS(VAR1$=IDDDIM$)=0 THEN IDDDIM$=IDDDIM$ +";"+VAR$; GOTO 8497 ADD 8498 PPP=POS(VAR1$=IDDDIM$), PPP1=POS(")"=IDDDIM$ (PPP)); IF IDDDIM$(P PP+PPP1,1)=";" THEN IDDDIM$=IDDDIM$(1,PPP-2)+IDDDIM$(PPP+PPP1) ELSE IDDDIM$=IDDDIM$(1,PPP-1)+IDDDIM$(PPP+PPP1 +1) FI; IDDDIM$= IDDDIM$+";"+VAR$; GOTO 8497 If you are working on a SPx system with ORIGIN 2.1A, you must also check statement 8492 to replace REM OVE(6,KEY=K$) for REMOVE(6,KEY= K$). o PROBLEM: Grand Totals are not executed in Executive Query Reports that use an alternate sort and subtotal. SOLUTION: Make the following code modification in the program PGM.ENGRP7. PROGRAM: 5001 IF N(0)>0 THEN LET Z2$="END",Y9=Y7,Y8=0; GOSUB 6800 This code change is for the Report program generator shell. It will NOT effect your program unless you regenerate. You can make the mod to your program also and then you won't have to regenerate. *SPX/MPX -------- o PROBLEM: ERR=2 at 6850 in generated program when running a Summary Report. SOLUTION: The file with the error 2 is "yourpgmname.SUMMARY". This file is actually created in the runtime program ENGNNR at statement 8130. Change the "10" in that statement to a larger number so the file will be created with more records. Program Name: ENGNNR Original: 8130...IO$+".SUMMARY","","SE","10","132","0","" ^^ *SPx ONLY --------- o PROBLEM: If going from operating system level 7.5B to 7.4B; ERR=30, User Program Incorrect Checksum, will occur on protected programs because of a change in the encryption algorithm between the operating system levels. SOLUTION: Restore all protected programs from the ORIGIN installation tape. o PROBLEM: All data file definitions in one database are not SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB024 Pg002 copied to another database during IDD copy when a 'FILE FULL' message appears with the option to 'COPY AND EXPAND'. If the user selects the option to copy and expand, it appears that the process of copying data from one database to another resumes. The IDD file is expanded but the completed copy of file definitions is not successful. SOLUTION: Make the following modification to the program PGM.IDDCPY. PGM.IDDCPY OLD: 0270 NEXT I NEW: 0270 IF E$="RETRY" THEN E$="", GOTO 0180 ELSE 0270:NEXT I After making this modification, go back into the IDD, delete the new database you created to copy into and redo the copy. This problem is corrected in ORIGIN 2.1B. ORIGINATOR: Elaine Titus SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB024 Pg003 FIB 00026 10/11/90 *** ORIGIN 2.1B on GPx40, Notes & Cautions [ WPSF 620 R ] *** MAI Basic Four, Inc. announces the availability of MAI ORIGIN Application Development System and MAI Busness DATA Version 2.1B on the GPx Series 40. The required operating system level is 1.0A and above. Below are Notes and Cautions for ORIGIN 2.1B on the GPx Series 40. Please keep a copy of this Field Bulletin in your ORIGIN Helpful Hints Manual. INSTALLATION o Usage rights and system 'umask': Problems may occur when trying to run ORIGIN if you installed ORIGIN on your GPx system while the system 'umask' was defined with a value other than '0000' because all the installed program and data files will have incorrect usage rights. Reset the system 'umask' and re-install ORIGIN or change the usage rights to 777 ( chmod 777 * ) on the following directories: /usr/mbf/PS usr/origin/r21b/* usr/origin/r21b/pgm/* usr/origin/r21b/data/* usr/origin/r21b/rt/* You must be super user and change your current directory to one listed above in order to execute the change modes command. CONVERSION o IN IDD: Message 'NOT IN GPX FORMAT. TO CONVERT' PROBLEM: Whenever the user pulls up a file in the dictionary, the above message is displayed. If the user does a , the file is converted but as soon as a file in the dictionary is pulled up, the same message is displayed again. FIX: Program: pgm/IDDOD1 Add the following to the beginning of statement 190: 0190 DIM K1$(22," "); .... ACTION: Fixed in ORIGIN 2.1B on the 1.0B operating system tape. o Usage Rights: PROBLEM: The usage rights of any directory created while porting ORIGIN documentation files (IDD files, project files, user files) must be verified for valid access rights. These directories and/or data files may be created without sufficient privilege for the owner. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB026 Pg001 ACTION: Check the directories usage rights after porting files to the GPx Series 40. o Porting ORIGIN Files from MPx/AS Systems: Problem: When using the BQR utility, file names are truncated to the last dot within that file name. For example, .ABCR01.OPTIONS will be truncated to .OPTIONS unless you rename it to .ABCR01OPTIONS, removing the last dot separator. This is not only a GPx porting problem but is also true when porting from MPx to SPx systems. GENERAL o Usage Rights: ORIGIN defines work, temporary and production files with unrestricted usage rights. Any ORIGIN 2.1B user is allowed to access any ORIGIN defined files. The usage rights are -rw -rw -rw for the GPx Series 40. o MAI ORIGIN User Log-on: The PROGRAM and DATA file nodes (directories) requested during the user log-on into ORIGIN are not being recorded into the file ORIUFL when the user logging in uses a for the current default value displayed on the screen. FIX: Program: ORIGIN.BEGIN Original: 1060 ...X4$=A4$, Z5$=O0$(1,30), X5=31, X6 ... New: 1060 ...X4$=A4$, Z5$=A4$, X5=31, X6 ... ^^^ Original: 1070 ...X4$=A5$, Z5$=O0$(1,30), X5=31, X6 ... New: 1070 ...X4$=A5$, Z5$=A5$, X5=31, X6 ... ^^^ Original: 9004 RETURN New: 9004 IF POS(" "<>A4$)=0 THEN LET A4$=TMPNODE$ ENDIF; IF POS(" "<>A5$)=0 THEN LET A5$=TMPNODE$ ENDIF; RETURN ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ACTION: Fixed in ORIGIN on the 1.0B operating system tape. Any ORIGIN user must log-on again and re-enter these nodes using RETURN for default (if the modification had been installed) or the whole prefix manually (if no modification was made). o Related File Relationship: There is a new maximum of 254 file relationships per file within the Integrated Data Dictionary, Application Generator and Report Generator. o Derived Item Maintenance: User may get into an infinite loop while trying to create item 255 in the current data base. FIX: Program: /pgm/IDDDIX SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB026 Pg002 Add: 0225 KK=NUM(ATTR(U2,"KEY_SIZE")) 0243 IF LEN(K$)0 THEN LET 0450:C$=C$(1,PP-1)+C$(PP+1); GOTO 450 ACTION: Fixed in ORIGIN on the 1.0B operating system tape. Avoid SORT file names of less than 6 bytes. o Screen Maintenance: Do not hold the function three key (F3 - running character) for more than a second. If you do, garbage will display on the screen when using the ORIGIN screen editor in SCREEN Maintenance (ADS). o Line Order Entry: A maximum of 8 line order entry definitions are supported. There is no validation on this maximum so the user needs to be aware of this limitation. o ITEM DataBase: If you have derived items and try to delete the line order entry definition, the item database may get corrupted. FIX: Program: /pgm/ORIOED Original: 0470 A3$=A$(P1+1); P2=POS($20$>A3$); P1=P1+P2 SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB026 Pg003 New: 0470 A3$=A$(P1+1); P2=POS($0A$>A3$); P1=P1+P2 ^^ ACTION: Fixed in ORIGIN on the 1.0B operating system tape. REPORT GENERATOR o Reports based on indexed files have an invalid statement 1020. WORKAROUND: In generated program: Original: 1020 READ (6,IND=NUM(Z9$))IOL=0401 ... New: 1020 READ (1,IND=NUM(Z9$))IOL=0401 ... ^ ACTION: Fixed in 2.1B*16. Fix is in the PSAVED program, ORINR1, which means the fix cannot be done in the field, except in the generated program. o Report Format Maintenance: Do not hold the function three key (F3 - running character) for more than a second. If you do, garbage will be displayed on the screen while using report format maintenance (DSS). o Start/Stop Key: In a generated report based on a direct or multikey file with a main key consisting of more than one field, the 'CTL-I=END' for any of the remaining key items for the stop key will be set to a null value. The report will look like it is executing a bad stop key although it is working correctly. INTERFACES o Spreadsheet Interface: When answering the prompt, "INVOKE SPREADSHEET AFTER INTERFACE (CR=N/MB-I=Y) ", a 'Y' (yes) response returns an error 47 at statement 4745 in the generated report program. No fix or workaround is available. o Generated reports with Decision Software Interface for Label Printing, Spreadsheet or Direct File Interface: The following programs are missing a 'NEXT T' on statement 4005: FIX: Programs: ENGDIR, ENGGRF, ENGLBL and ENGRNC: Original: 4005 ...(T,1)=SYSTM$ THEN I=T,T=0 ENDIF; F1$=F1$ 4005:(I+1) New: 4005 ...(T,1)=SYSTM$ THEN I=T,T=0 ENDIF; NEXT T; 4005:F1$=F1$(I+1) ^^^^^^^ ACTION: Fixed in ORIGIN on the 1.0B the operating system tape. o DIRECT File Interface, Error 20 When running a direct file interface from a generated report, user will get an error 20 at statement 0860. FIX: Program: /rt/ENGDIR Original: 0860 LET NUMRECS=NUM( ... "RECORDS_SIZE")) New: 0860 LET NUMRECS=NUM( ... "RECORD_SIZE")) SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB026 Pg004 ORIGINATOR: Elaine Titus SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB026 Pg005 FIB 00027 11/19/90 *** ORIGIN 2.1B ADS/Bus. DATA Software Announcement [ WPSS 176 ] *** MAI Basic Four, Inc. announces the availability of MAI ORIGIN 2.1B ADS and MAI Business DATA on the BOSS/VS and BOSS/IX Systems. Along with the installation procedures and requirements for both systems, this software announcement contains descriptions of new features and helpful hints. MAI ORIGIN 2.1B release level has been tested on the BOSS/IX platform using the 7.5B operating system level which is the recommended operating system level for those systems. On BOSS/VS, the operating system level recommended is M.6C and above. MAI ORIGIN 2.1B installation instructions for the GPx Series 40 and GPx Series 70 platforms can be found in the operating system Software Announcements. Version 2.1B is located on the GPx 40 and GPx 70 operating system tape along with the Presentation Services product. MAI Business Data no longer requires a public key. MAI ORIGIN ADS still requires a public key and contains some encrypted programs. TABLE OF CONTENTS 1.0 MPX/AS SYSTEMS . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.1 INITIAL INSTALLATION OF ORIGIN 2.1B . . . . . . . . . . . . . . 1 1.2 INSTALLATIONS UPGRADING FROM 2.1A . . . . . . . . . . . . . . . 3 1.3 INSTALLATIONS UPGRADING FROM 2.0A . . . . . . . . . . . . . . . 5 1.4 INSTALLATIONS UPGRADING FROM 1.3A/B . . . . . . . . . . . . . . 7 1.5 OPTIONAL STEP - DOMESTIC SITES. . . . . . . . . . . . . . . . . 8 1.6 EXECUTING ORIGIN ON MPX/AS SYSTEMS. . . . . . . . . . . . . . . 8 2.0 2000/2500/3000/4000. . . . . . . . . . . . . . . . . . . . . . . . . 9 2.1 NEW AND UPDATE INSTALLATIONS - ALL . . . . . . . . . . . . . . 9 2.2 NEW ORIGIN 2.1B INSTALLATIONS. . . . . . . . . . . . . . . . .11 2.3 UPDATE INSTALLATION - ORIGIN 2.1A TO ORIGIN 2.1B . . . . . . .12 2.4 UPDATE INSTALLATION - ORIGIN 2.0A TO ORIGIN 2.1B . . . . . . .13 2.5 UPDATE INSTALLATION - ORIGIN 1.3A/B TO ORIGIN 2.1B . . . . . .14 2.6 EXECUTING ORIGIN ON THE 2000/2500/3000/4000. . . . . . . . . .14 2.7 SETTING UP A USER FOR ORIGIN ON THE 2000/2500/3000/4000. . . .15 3.0 ORIGIN INSTALLATION. . . . . . . . . . . . . . . . . . . . . . . . .16 3.1.1 ORIGIN BACKUP. . . . . . . . . . . . . . . . . . . . . .16 3.1.2 UPDATE PROGRAM . . . . . . . . . . . . . . . . . . . . .16 3.1.3 DOCUMENTATION AND WORK FILE INFORMATION. . . . . . . . .16 3.1.4 DUPLICATE FILES. . . . . . . . . . . . . . . . . . . . .17 3.1.5 PRESENTATION SERVICES ORIGIN RUN TIME PROGRAMS . . . . .17 3.2 UPGRADES FROM LEVEL 2.0B AND PRIOR . . . . . . . . . . . . . .18 3.2.1 RUN TIME UTILITIES . . . . . . . . . . . . . . . . . . .18 3.2.2 ORIT12 PROGRAM NOT USED. . . . . . . . . . . . . . . . .18 NEW FEATURES, NOTES AND CAUTIONS. . . . . . . . . . . . . . . . . . . . .18 4.0 GENERAL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg001 4.1 USAGE RIGHTS . . . . . . . . . . . . . . . . . . . . . . . . .18 4.2 RELATED FILE RELATIONSHIP. . . . . . . . . . . . . . . . . . .18 4.3 MEMORY REQUIREMENTS. . . . . . . . . . . . . . . . . . . . . .19 4.4 DERIVED ITEM CONDITIONED EXPRESSION. . . . . . . . . . . . . .19 4.5 APPLICATION OR REPORT PROGRAM STANDARD HEADINGS. . . . . . . .20 4.6 USER WORKFILE NODE . . . . . . . . . . . . . . . . . . . . . .20 4.7 GRAPH INTERFACE. . . . . . . . . . . . . . . . . . . . . . . .20 4.8 CUSTOMIZING ORIGIN SHELL PROGRAMS. . . . . . . . . . . . . . .21 4.9 RUN TIME UTILITIES USE ON SPx OR GPx . . . . . . . . . . . . .21 4.10 DISPLAY OR PRINT ATTRIBUTES IN GENERATED PROGRAMS. . . . . . .21 4.11 TRANSLATION TABLE NAMES. . . . . . . . . . . . . . . . . . . .21 4.12 FILE TYPES ALLOWED FOR APPLICATION OR REPORT PROGRAMS. . . . .22 4.13 DT-4313/14 ARROW KEYS AND NUMERIC PAD. . . . . . . . . . . . .22 4.14 SCREEN EDITOR FUNCTION MODULE, TERMINAL SETUP. . . . . . . . .22 4.15 DERIVED ITEM EXECUTION . . . . . . . . . . . . . . . . . . . .23 4.16 LINKING MULTIPLE CONDITIONS. . . . . . . . . . . . . . . . . .24 4.17 TOLD MESSAGE AT LOG-ON . . . . . . . . . . . . . . . . . . . .24 4.18 TRANSLATION TABLE . . . . . . . . . . . . . . . . . . . . . .25 4.19 ITEM DEPENDENCIES . . . . . . . . . . . . . . . . . . . . . .25 4.20 TEMPORARY FILES . . . . . . . . . . . . . . . . . . . . . . .25 4.21 GENERATED PROGRAMS ON TERMINALS GREATER THAN T99 . . . . . . .26 4.22 MODIFYING ORIGIN FIELD INFORMATION . . . . . . . . . . . . . .26 5.0 INTEGRATED DATA DICTIONARY . . . . . . . . . . . . . . . . . . . . .26 5.1.1 NUMERIC FILE NAMES . . . . . . . . . . . . . . . . . .26 5.1.2 FULL PATH NAME IN DEFINED NAME FIELD . . . . . . . . .26 5.1.3 BUSY FILE CONTROL RECORD . . . . . . . . . . . . . . .26 5.1.4 NUMERIC ITEM AS KEY ELEMENT . . . . . . . . . . . . . .27 5.1.5 FILE COPY WITH DERIVED ITEM AS A KEY . . . . . . . . .27 5.2 MULTI-KEYED FILES . . . . . . . . . . . . . . . . . . . . . .27 5.2.1 DIRECT TO MULTI-KEY FILE CONVERSION . . . . . . . . . .27 5.2.2 MULTI-KEYED FILE FORMAT vs DICTIONARY FORMAT. . . . . .27 5.2.3 MULIT-KEYED FILE FORMAT CHANGES UPDATE . . . . . . . .28 5.2.4 COMPOSITE ITEMS IN MULTI-KEYED FILES. . . . . . . . . .28 6.0 MULTI-RECORD TYPE FILES IN ORIGIN. . . . . . . . . . . . . . . . . .28 6.1 USING MULTI-RECORD FILES IN ORIGIN. . . . . . . . . . . . . . .29 7.0 APPLICATION GENERATOR . . . . . . . . . . . . . . . . . . . . . . .30 7.1 IOLIST STRUCTURE . . . . . . . . . . . . . . . . . . . . . . .30 7.2 KEY ITEMS ALLOWED. . . . . . . . . . . . . . . . . . . . . . .30 7.3 PREVIOUS VALUE FOR NUMERIC INPUTS. . . . . . . . . . . . . . .30 7.4 SCREEN MAINTENANCE . . . . . . . . . . . . . . . . . . . . . .30 7.5 QUERY BY EXAMPLE ON FILE WITH NO FIELD SEPARATOR . . . . . . .30 7.6 CONDITIONS . . . . . . . . . . . . . . . . . . . . . . . . . .31 7.7 VARIABLES . . . . . . . . . . . . . . . . . . . . . . . . . .31 7.8 FUNCTION KEYS . . . . . . . . . . . . . . . . . . . . . . . .31 7.9 MISSING RECORD MESSAGE FOR FILE RELATIONSHIPS . . . . . . . .31 7.10 SUB-MENU DEFINITION. . . . . . . . . . . . . . . . . . . . . .31 7.11 PREFIX/SUFFIX DEFINITION . . . . . . . . . . . . . . . . . . .32 8.0 REPORT GENERATOR . . . . . . . . . . . . . . . . . . . . . . . . . .32 8.1 IOLIST STRUCTURE . . . . . . . . . . . . . . . . . . . . . . .32 8.2 MASK OVERFLOW CONTROL . . . . . . . . . . . . . . . . . . . .32 8.3 MASK WITH NEGATIVE SIGN. . . . . . . . . . . . . . . . . . . .33 8.4 132-COLUMN SUPPORT . . . . . . . . . . . . . . . . . . . . . .33 SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg002 8.5 FOOTNOTE DEFINITION . . . . . . . . . . . . . . . . . . . . .33 8.6 SPOOLING ATTRIBUTES . . . . . . . . . . . . . . . . . . . . .33 8.7 SLAVE PRINTERS AS OUTPUT DEVICES . . . . . . . . . . . . . . .33 8.8 MULTI-KEYED FILES . . . . . . . . . . . . . . . . . . . . . .34 8.9 SORT FILE REPORTS. . . . . . . . . . . . . . . . . . . . . . .34 8.10 SAVED OPTIONS. . . . . . . . . . . . . . . . . . . . . . . . .34 8.11 DEFINING START/STOP KEYS . . . . . . . . . . . . . . . . . . .34 8.12 SUMMARY FILE SIZE. . . . . . . . . . . . . . . . . . . . . . .35 8.13 INPUT FIELDS . . . . . . . . . . . . . . . . . . . . . . . . .35 8.14 RENAME RESTRICTION ON GPx. . . . . . . . . . . . . . . . . . .36 8.15 USER DEFINED PRINT SEQUENCE. . . . . . . . . . . . . . . . . .36 9.0 PROGRAM SIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 9.1 ERROR 31 TROUBLE-SHOOTING. . . . . . . . . . . . . . . . . . .37 9.2 ERROR 31 GENERATING LARGE PROGRAMS . . . . . . . . . . . . . .37 9.3 ERROR 31 DIAGNOSIS ON LARGE STATEMENTS . . . . . . . . . . . .38 9.4 ERROR 31 ON LARGE STATEMENTS - RECOVERY. . . . . . . . . . . .38 9.5 ERROR 31 ON LARGE STATEMENTS AT 1030 RANGE . . . . . . . . . .39 10.0 ORIGIN WORK ENVIRONMENT. . . . . . . . . . . . . . . . . . . . . . 39 10.1 DEFAULT STRUCTURE. . . . . . . . . . . . . . . . . . . . . . 39 10.2 WORKFILE DIRECTORY . . . . . . . . . . . . . . . . . . . . . 40 10.3 DEVELOPMENT ENVIRONMENT. . . . . . . . . . . . . . . . . . . 42 10.4 APPLICATION ENVIRONMENT. . . . . . . . . . . . . . . . . . . 44 11.0 ADS AND DSS GENERATED PROGRAM LINKS OR INTERFACES . . . . . . . . .46 11.1 ADS APPLICATION PROGRAMS USING DSS GENERATED REPORTS. . . . .46 11.1.1 REPORT OUTPUT FORMAT SIMILAR TO APPLICATION PROGRAM .46 11.1.2 REPORT RUN WITH ONE REQUESTED RECORD. . . . . . . . .46 11.2 ADS PROGRAM CALLING A DSS REPORT. . . . . . . . . . . . . . .48 11.3 ADS WITH DSS LINK FUNCTIONALITY . . . . . . . . . . . . . . .48 11.4 DSS REPORT PROGRAMS USING ADS APPLICATION PROGRAMS. . . . . .49 11.4.1 APPLICATION PROGRAM AS A REPORT PARAMETERS INPUT PROGRAM. . 49 11.4.2 REPORT PROGRAM USING PARAMETER INFORMATION WRITTEN TO FILE. . . . . . . . . . . . . . . . . . . . . . . . 52 11.4.3 DSS WITH ADS LINK FUNCTIONALITY . . . . . . . . . . .53 12.0 KNOWN ERRORS. . . . . . . . . . . . . . . . . . . . . . . . . . . .53 12.1 ERROR 2 USING LABEL PRINT INTERFACE . . . . . . . . . . . . .54 12.2 LINE ORDER ENTRY DETAIL LINES . . . . . . . . . . . . . . . .54 12.3 EXECUTIVE QUERY ON LINE ORDER ENTRY REPORTS . . . . . . . . .54 12.4 ORIGIN ADS PROGRAMS DO NOT EXIT THROUGH CTL-IV. . . . . . . .54 13.0 TRANSLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 13.1 LETTER GENERATION UPDATE TIPS . . . . . . . . . . . . . . . .55 14.0 SPR'S FIXED IN ORIGIN 2.1B . . . . . . . . . . . . . . . . . . . . . FIGURES 10.1 GPX'S ORIGIN STRUCTURE UNDER ROOT................................. 10.2 GPX'S ORIGIN STRUCTURE UNDER A DISK OR PARTITION.................. 10.3 MPX'S ORIGIN STANDARD STRUCTURE................................... SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg003 10.4 SPX'S ORIGIN STRUCTURE UNDER ROOT................................. 10.5 SPX'S ORIGIN STRUCTURE UNDER A DISK OR PARTITION.................. 10.6 GPX ORIGIN STRUCTURE WITH WORKFILE NODE 'WORK'.................... 10.7 MPX ORIGIN STRUCTURE WITH WORKFILE NODE 'WORK'.................... 10.8 SPX ORIGIN STRUCTURE WITH WORKFILE NODE 'WORK'.................... 10.9 GPX ORIGIN STRUCTURE WITH DEVELOPMENT ENVIRONMENT................. 10.10 MPX ORIGIN STRUCTURE WITH DEVELOPMENT ENVIRONMENT................. 10.11 SPX ORIGIN STRUCTURE WITH DEVELOPMENT ENVIRONMENT................. 1.0 MPx/AS SYSTEMS 1.1 INITIAL INSTALLATION OF ORIGIN 2.1B 1. Set your PREFIX to (family).ORIGIN.R21B. Ex: !PREFIX (family).ORIGIN.R21B. 2. Restore all files from tape using the SAVERESTORE utility. Ex: !SAVERESTORE : Option 2. "RESTORE FILES FROM TAPE" : MB-III to use defaults : At the prompt "ENTRIES CORRECT (Y/N)", 'Y' : At the prompt "ENTER FILE SPECIFIERS :" '&' : Press NOTE: The example above will restore both PS and ORIGIN on the same drive. 3. Presentation Services (PS) must be installed to your system node, by running the program ".PS.INSTALL" from BASIC. This program will copy the files from the .PS.SYS. directory into your system directory. First set your prefix to (family).PS. Ex: !PPUSH (family).PS. : !BASIC : >RUN ".PS.INSTALL" : "Install Program PS 3.1A *18" displays, press During the copy the following will display: Install Program PS 3.1 NOW COPYING : .PS.SYS.MSXXXX TO : ().R6HXX.SYS.MSXXXX Installation of PS3.1 is now complete... READY >!PPOP (to reset your prefix to ORIGIN) > NOTE: Even when PS 3.3A is installed on the system, the PS on the ORIGIN tape should be installed or the ORIGIN menu files will be missing. NOTE: If PS 3.3A is going to be installed, restore PS Forms files from the PS 3.3A tape and repeat. The level displayed during the PS.INSTALL will be 3.3A *12. 4. RUN "UPDATE" from BASIC SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg004 NOTE: This program has long pauses between steps. During a new installation, this program renames several 2.1B data files. Answer the following UPDATE prompts accordingly: A. ENTER THE FAMILY NAME FOR .ORIGIN.R21B. : (family) B. ENTER THE NODE OF YOUR CURRENT ORIGIN SYSTEM INCLUDING FAMILY NAME, CR IF THIS IS A NEW INSTALLATION : C. INSTALL STANDALONE ORIGIN UTILITIES IN SYSTEM NODE (family).R6Hxx.SYS. CR TO PROCEED, CTL-IV TO END : This will copy the files from the runtime node ".ORIGIN.R21B.RT.", into the system node. A message "COPY IN PROGRESS..." will be displayed. When the copy is complete the following message will display: ORIGIN INSTALLATION COMPLETE : User Prefix Set READY > 5. To install your new public key for the ORIGIN ADS module please do the following: A. Enter the following from command mode: !INSTALLKEY ADS You will then be prompted: SYSTEM SERIAL NUMBER: ###-##### CURRENT SECURITY KEY: 12345678 NEW SECURITY KEY : ENTER NEW SECURITY KEY ('CR' IF NO CHANGE) B. Enter your 8 character security key obtained from Software Distribution. You will be prompted twice to enter the security key. C. The following messages will display: SECURITY KEY INSTALLATION COMPLETE SECURITY INSTALLATION COMPLETE, CR TO CONTINUE: Press to return to command mode. You have now completed all steps necessary to install ORIGIN 2.1B. Please refer to instructions in section titled 'EXECUTING ORIGIN ON THE MPx'. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg005 1.2 MPx INSTALLATIONS UPGRADING FROM 2.1A ******************************************************************* * * . * BACK UP the .ORIGIN.R21A.DATA. node and the node in which * * your *DC0 files are located BEFORE installing this release. * * The *DC0 files (the technical documentation files) are * * normally located in your primary prefix. * * * . ******************************************************************* 1. Set your PREFIX to (family).ORIGIN.R21B. Ex: !PREFIX (family).ORIGIN.R21B. 2. Restore all files from tape using the SAVERESTORE utility. Ex: !SAVERESTORE : Option 2. "RESTORE FILES FROM TAPE" : MB III to use defaults : At the prompt "ENTRIES CORRECT (Y/N)", 'Y' : At the prompt "ENTER FILE SPECIFIERS :".ORIGIN.R21B. : Press The PS installed on the system prior to this update will not be over-written during this procedure. 3. RUN "UPDATE" from BASIC. NOTE: This program has long pauses between steps. When you are upgrading from 2.1A, this program will convert your 2.1A dictionary files and user files into the 2.1B files. Answer the following UPDATE prompts accordingly: A. ENTER THE FAMILY NAME FOR .ORIGIN.R21B.: (family) B. ENTER THE NODE OF YOUR CURRENT ORIGIN SYSTEM INCLUDING FAMILY NAME, CR IF THIS IS A NEW INSTALLATION : (family).ORIGIN.R21A. NOTE: Current = existing before update After pause, a message appears, 'USER PREFIX SET'. At bottom of screen the next prompt appears: C. CR TO PROCEED WITH .ORIGIN.R21B. UPDATE, CTL-IV = EXIT : This will copy the files from the R21A node into the .ORIGIN.R21B.DATA. node. During this step a message displays: 'Now copying current 2.1A files to 2.1B nodes'. D. INSTALL STANDALONE ORIGIN UTILITIES IN SYSTEM NODE (family).R6Hxx.SYS. CR TO PROCEED, CTL-IV TO END: This will copy the files from the runtime node, SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg006 ".ORIGIN.R21B.RT.", into the system node. A message 'COPY IN PROGRESS' will be displayed. Message appears - ORIGIN INSTALLATION COMPLETE: User prefix set READY > 4. Install your new public key for the ORIGIN ADS module as follows: NOTE: If ADS was installed with 2.1A, the key will not change and this step can be skipped. A. Enter the following from command mode: !INSTALLKEY ADS You will then be prompted: SYSTEM SERIAL NUMBER: ###-##### CURRENT SECURITY KEY: 12345678 NEW SECURITY KEY : ENTER NEW SECURITY KEY ('CR' IF NO CHANGE) B. Enter your eight (8) character security key obtained from Software Distribution. You will be prompted twice to enter the security key. C. The following messages will display: SECURITY KEY INSTALLATION COMPLETE SECURITY INSTALLATION COMPLETE, CR TO CONTINUE: You have now completed all steps necessary to install ORIGIN 2.1B. Please refer to instructions in section titled 'EXECUTING ORIGIN ON THE MPx'. 1.3 MPx INSTALLATIONS UPGRADING FROM 2.0A ******************************************************************* * * * BACK UP the .ORIGIN.R20A.DATA. node and the node in which * * your *DC0 files are located BEFORE installing this release. * * The *DC0 files (the technical documentation files) are * * normally located in your primary prefix. * * * ******************************************************************* 1. Set your PREFIX to (family).ORIGIN.R21B. Ex: !PREFIX (family).ORIGIN.R21B. 2. Restore all files from tape using the SAVERESTORE utility. Ex: !SAVERESTORE : Option 2. "RESTORE FILES FROM TAPE" : Use defaults except for the prompt, "DELETE EXISTING FILES" which should be 'N' for No : At the prompt "ENTRIES CORRECT (Y/N)", 'Y' SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg007 : At the prompt "ENTER FILE SPECIFIERS :" '&' : Press 3. Presentation Services (PS) must be installed on your system node, by running the program ".PS.INSTALL" from BASIC. This program will copy the files from the .PS.SYS. node into your system node. Set your prefix to (family).PS. Ex: !PPUSH (family).PS. : !BASIC : >RUN ".PS.INSTALL" : "Install Program PS 3.1A*18" displays, press During the copy the following will display: Install Program PS 3.1 NOW COPYING : .PS.SYS.MSXXXX TO : ().R6HXX.SYS.MSXXXX Installation of PS3.1 is now complete .. READY >!PPOP NOTE: Even when PS 3.3A is installed on the system, the PS on the ORIGIN tape should be installed or the ORIGIN menu files will be missing. NOTE: If PS 3.3A is going to be installed, restore PS Forms files from the PS 3.3A tape and repeat. The level displayed during the PS.INSTALL will be 3.3A *12. 4. RUN "UPDATE" from BASIC. If you are upgrading from 2.0A, this program will convert your 2.0A dictionary files and user files into the 2.1B files. Answer the following UPDATE prompts accordingly: A. ENTER THE FAMILY NAME FOR .ORIGIN.R21B.: (family) B. ENTER THE NODE OF YOUR CURRENT ORIGIN SYSTEM INCLUDING FAMILY NAME, CR IF THIS IS A NEW INSTALLATION : (family).ORIGIN.R20A. NOTE: Current = existing before update C. CR TO PROCEED WITH .ORIGIN.R21B. UPDATE, CTL-IV = EXIT: This will copy the following files from the R20A node into the .ORIGIN.R21B.DATA. node. ORIDDF ORIQF1 ORI1FL ORIQS2 ORIV01 ORIPS7 ORI1F2 ORIQS1 ORIQST ORIVDC This will convert the program files ORIPS4 thru PS6 into the 2.1B files. D. CR TO BEGIN UPDATE OF DICTIONARY FILES, CTL-IV TO EXIT: SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg008 This will convert R20A program documentation and Integrated Data Dictionary (IDD) files, Expressions, and Views into R21B format. E. IDD CONVERSION COMPLETE. CR TO CONTINUE: This will continue the installation of the R21B runtime files. F. INSTALL STANDALONE ORIGIN UTILITIES IN SYSTEM NODE (family).R6Hxx.SYS. CR TO PROCEED, CTL-IV TO END: This will copy the files in the runtime node, ".ORIGIN.R21B.RT." into the system node. A message 'COPY IN PROGRESS' will be displayed. Message appears - ORIGIN INSTALLATION COMPLETE: User prefix set READY > 5. Install your new public key for the ORIGIN ADS module please do the following: A. Enter the following from command mode: !INSTALLKEY ADS You will then be prompted: SYSTEM SERIAL NUMBER: ###-##### CURRENT SECURITY KEY: 12345678 NEW SECURITY KEY : ENTER NEW SECURITY KEY ('CR' IF NO CHANGE) B. Enter your eight (8) character security key obtained from Software Distribution. You will be prompted twice to enter the security key. C. The following messages will display: SECURITY KEY INSTALLATION COMPLETE SECURITY INSTALLATION COMPLETE, CR TO CONTINUE: You have now completed all steps necessary to install ORIGIN 2.1B. Please refer to instructions in section titled 'EXECUTING ORIGIN ON THE MPx'. 1.4 MPx INSTALLATIONS UPGRADING FROM 1.3B OR 1.3A 1. Upgrade the ORIGIN dictionary files to 2.0A format. 1.3B Users: Follow the 2.0A upgrade instructions in the MAI ORIGIN 2.0A SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg009 Software Announcement #143 on page 14. The dictionary conversion program "IDDCNV" described in the Software Announcement is contained on the 2.1B tape in the .ORIGIN.R21B.UTIL. node. 1.3A Users: Follow the 2.0A upgrade instructions in the MAI ORIGIN 2.0A Software Announcement #143 on page 13. The conversion program "ORIA2B" described in the Software Announcement must be restored from an MAI ORIGIN 2.0A tape. 2. Turn to Section 1.2 'UPGRADING FROM 2.0A'. 1.5 OPTIONAL STEP - DOMESTIC SITES This step is optional. If you do not plan to use the language translation utilities, you can delete the .ORIGIN.R21B.LANGUAGE. node. These utilities are used primarily by international sites to translate ORIGIN from English to a different language. To delete this node, enter the following from command mode: !DELETE .ORIGIN.R21B.LANGUAGE.& 1.6 EXECUTING ORIGIN ON THE MPx Here are the steps for executing 2.1B on the MPx: 1. Set your prefix with your user prefix first followed by the ORIGIN and Presentation Services nodes. !PREFIX (family).USER.,.ORIGIN.R21B.,(family).PS.,PS.TOOLS. 2. If ORIGIN ADS was installed, run "PGM.ORINST" from BASIC. The DSS key is no longer required with 2.1B. 3. Run "ORIGIN". If the version displayed at the top of the screen does not read "Version 2.1*B23" you must change log-on using the function key [F2]. 4. Enter the account name "MAI.ORIGIN" and the password "ADMIN" at the Menu system Logon. NOTE: ORIGIN 2.1A account names will remain when updating from ORIGIN 2.1A. ORIGIN 2.0A and ORIGIN 1.3A/B users are not converted to ORIGIN 2.1B due to the major security enhancements in the Presentation Services menu system. NOTE: When logging into ORIGIN 2.1B for the first time, you must re-enter the data node and program node at the MAI ORIGIN USER LOG-ON screen. 5. If users were not converted or new users must be created, set up ORIGIN users as follows: SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg010 o Select Utilities from the ORIGIN main menu. o Select User Maintenance Make the ORIGIN account name the same as the system log-on account name. Refer to the MAI ORIGIN Systems Support Manual, M7510A for more information on user log-on. 6. Set up your ORIGIN System Parameters. (optional) o Select Utilities from the ORIGIN main menu o Select System Administrator Utilities. The password is ADMIN. o Select ORIGIN System Parameters Maint o Enter a Work Files Node. This node will be the node in which. all of your temporary ORIGIN files will be created. Normally, this node is ".ORIGIN.WORK.". 7. The .ORIGIN.R20A.RT node may be deleted if this is a new ORIGIN 2.1B installation and/or no applications generated with ORIGIN 2.0A will be running on the system. 2.0 2000/2500/3000/4000 ***************************************************************************** * *. * o ORIGIN 2.1B must be installed on operating system level 7.5B or later. * * *. * o Please read these instructions before installing ORIGIN 2.1B from the * * tape. Because of changes in the tape build process, some important * * changes have been made in the installation procedure. * * *. ***************************************************************************** 2.1 NEW AND UPDATE INSTALLATIONS - ALL 1. If ORIGIN 2.1B will be installed on drive 0, skip to step 2. If ORIGIN 2.1B will be installed on an alternate drive perform the following commands from ADMIN: ADMIN>cd / ADMIN>makedir /origin ADMIN>mount /dev/your-partition-name /origin 2. If this installation is an ORIGIN 2.1A update, skip to step 3. All new ORIGIN 2.1B installations and upgrades from ORIGIN 2.0A or 1.3A/B, install PS 3.1A delivered on the ORIGIN 2.1B tape. Presentation Services must be installed on drive 0. ADMIN>install cs EPS NOTE: Replace 'cs' with 'ts' if you are using an MTS unit. NOTE: Because of changes in the product tape, the EPS product must be installed first in a separate step as above. If PS 3.3A will be installed, it must be installed after the PS 3.1A has been installed. Refer to Software Announcement #164 for detailed instructions. 3. Restore the ORIGIN modules from tape using the install command. Only the modules ordered should be installed. DSS must be installed when installing ADS and/or OTU since both require DSS SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg011 before they can be executed. ADMIN>install cs DSS ADS OTU For alternate drive installations, use: ADMIN>install cs DSS ADS OTU to=/origin NOTE: Replace 'cs' with 'ts' if you are using an MTS unit. *********************************************************** * ORIGIN 2.1B MODULES * * * * o EPS - PS 3.1A, Menubuilder * * o DSS - MAI Business DATA * * o ADS - Application Development System * * o OTU - ORIGIN Translation Utilities * *********************************************************** 4. To install the new public key for the ORIGIN ADS module, enter the 8-character installation key obtained through Software Distribution when the following message is displayed: Input 8-character installation key (cr=no change): If the new ADS key is not readily available, CR to continue. This key can be installed during the UPDATE program. NOTE: The public key request is not executed when installing ORIGIN on an alternate drive. 5. Set your prefix to '/origin/r21b'. ADMIN>cd /origin/r21b 6. Go into BASIC and start 256 pages.. ADMIN>basic s=256 -nr ************************************************************************* * Section 2.1, which should be done for all installations and updates, * * is now complete but the installation of ORIGIN 2.1B is not. The * * following sections should be chosen according to the type of * * installation or upgrade being done. * * *. * 2.2 New ORIGIN 2.1B Installation * * 2.3 ORIGIN 2.1A to ORIGIN 2.1B Update * * 2.4 ORIGIN 2.0A to ORIGIN 2.1B Update *. * 2.5 ORIGIN 1.3A/B to ORIGIN 2.1B Update * ************************************************************************* 2.2 NEW ORIGIN 2.1B INSTALLATIONS RUN "UPDATE" For new installations, this program renames several ORIGIN 2.1B data files. Answer the following prompts accordingly: 1. ENTER THE DISK NAME FOR ORIGIN 2.1B, (CR IF NONE) : SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg012 CR if you are installing on drive 0; otherwise, enter the directory name of drive 1. 2. ENTER DIRECTORY OF YOUR CURRENT ORIGIN SYSTEM INCLUDING DISK NAME, CR IF THIS IS A NEW INSTALLATION: Enter CR to move files from the /origin/r21b/data/new into the /origin/r21b/data directory. 3. INSTALL STANDALONE ORIGIN UTILITIES IN SYSTEM DIRECTORY /bin/ CR TO PROCEED, CTL-IV TO END: Install the standalone utilities if you want the user to run ORIGIN generated programs without having the ORIGIN directory in their prefix list. In this case, each user would need the '/bin' directory at the end of their prefix list. ORIGIN INSTALLATION COMPLETE: 4. SYSTEM SERIAL NUMBER: ####-##### CURRENT SECURITY KEY: 12345678 NEW SECURITY KEY : ENTER NEW SECURITY KEY ('CR' IF NO CHANGE) o Enter 'CR' if the public key displayed on the screen is correct. o Enter your 8-character security key obtained from Software Distribution if the key displayed is incorrect. You will be prompted to enter the security key twice. 5. SECURITY KEY INSTALLATION COMPLETE SECURITY INSTALLATION COMPLETE, CR TO CONTINUE: ORIGIN INSTALLATION COMPLETE. 6. Turn to Section 2.6 EXECUTING ORIGIN ON THE 2000/2500/3000/4000. 2.3 UPDATE INSTALLATION - ORIGIN 2.1A TO ORIGIN 2.1B RUN "UPDATE" When updating ORIGIN 2.1A to ORIGIN 2.1B, this program converts ORIGIN 2.1A files into ORIGIN 2.1B files. Answer the following prompts accordingly: 1. ENTER THE DISK NAME FOR ORIGIN 2.1B, (CR IF NONE) : CR if you are installing on drive 0; otherwise, enter the directory name of drive 1. 2. ENTER DIRECTORY OF YOUR CURRENT ORIGIN SYSTEM INCLUDING DISK NAME, CR IF THIS IS A NEW INSTALLATION: When updating from ORIGIN 2.1A, enter /origin/r21a The files in the /origin/r21b/data/new will now be moved into the /origin/r21b/data directory. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg013 3. CR TO PROCEED WITH ORIGIN 2.1B UPDATE, CTL-IV = EXIT 4. INSTALL STANDALONE ORIGIN UTILITIES IN SYSTEM DIRECTORY /bin/ CR TO PROCEED, CTL-IV TO END: Install the standalone utilities if you want the user to run ORIGIN generated programs without having the ORIGIN directory in their prefix list. In this case, each user would need the '/bin' directory at the end of their prefix list. ORIGIN INSTALLATION COMPLETE: 5. SYSTEM SERIAL NUMBER: ####-##### CURRENT SECURITY KEY: 12345678 NEW SECURITY KEY : ENTER NEW SECURITY KEY ('CR' IF NO CHANGE) o Enter 'CR' if the public key displayed on the screen is correct. o Enter your 8-character security key obtained from Software Distribution if the key displayed is incorrect. You will be prompted to enter the security key twice. 6. SECURITY KEY INSTALLATION COMPLETE SECURITY INSTALLATION COMPLETE, CR TO CONTINUE: ORIGIN INSTALLATION COMPLETE. 7. Turn to Section 2.6 EXECUTING ORIGIN ON THE 2000/2500/3000/4000. 2.4 UPDATE INSTALLATION - ORIGIN 2.0A TO ORIGIN 2.1B RUN "UPDATE" When updating ORIGIN 2.0A to ORIGIN 2.1B, this program converts ORIGIN 2.0A dictionary and user files into the ORIGIN 2.1B files. Answer the following prompts accordingly: 1. ENTER THE DISK NAME FOR ORIGIN 2.1B, (CR IF NONE) : CR if you are installing on drive 0; otherwise, enter the directory name of drive 1. 2. ENTER DIRECTORY OF YOUR CURRENT ORIGIN SYSTEM INCLUDING DISK NAME, CR IF THIS IS A NEW INSTALLATION: When updating from ORIGIN 2.0A, enter /origin/r20a The files in the /origin/r21b/data/new will now be moved into the /origin/r21b/data directory. 3. CR TO PROCEED WITH ORIGIN 2.1B UPDATE, CTL-IV = EXIT 4. CR TO BEGIN UPDATE OF DICTIONARY FILES, CTL-IV TO EXIT A CR will convert ORIGIN 2.0A dictionary files into ORIGIN 2.1B format. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg014 IDD CONVERSION COMPLETE. CR TO CONTINUE: 5. INSTALL STANDALONE ORIGIN UTILITIES IN SYSTEM DIRECTORY /bin/ CR TO PROCEED, CTL-IV TO END: Install the standalone utilities if you want the user to run ORIGIN generated programs without having the ORIGIN directory in their prefix list. In this case, each user would need the '/bin' directory at the end of their prefix list. ORIGIN INSTALLATION COMPLETE: 6. SYSTEM SERIAL NUMBER: ####-##### CURRENT SECURITY KEY: 12345678 NEW SECURITY KEY : ENTER NEW SECURITY KEY ('CR' IF NO CHANGE) o Enter 'CR' if the public key displayed on the screen is correct. o Enter your 8-character security key obtained from Software Distribution if the key displayed is incorrect. You will be prompted to enter the security key twice. 7. SECURITY KEY INSTALLATION COMPLETE SECURITY INSTALLATION COMPLETE, CR TO CONTINUE: ORIGIN INSTALLATION COMPLETE. 8. Turn to Section 2.6 EXECUTING ORIGIN ON THE 2000/2500/3000/4000. 2.5 UPDATE INSTALLATION - ORIGIN 1.3A/B TO ORIGIN 2.1B 1. Update your ORIGIN dictionary files to 2.0A format following the ORIGIN 2.0A update instructions in the MAI ORIGIN 2.0A Software Announcement #143 on page 14. The dictionary conversion program "IDDCNV" described in the software announcement is contained on the ORIGIN 2.1B tape in the /origin/r21b/util directory. 2. Turn to Section 1.4 UPDATE INSTALLATION - ORIGIN 2.0A TO ORIGIN 2.1B, to complete the update to ORIGIN 2.1B. 2.6 EXECUTING ORIGIN ON THE 2000/2500/3000/4000 1. Set your prefix with the user directory first followed by the ORIGIN and Presentation Services directories. ADMIN>cd /usr/origin ADMIN>ad /origin/r21b /PS /PS/tools 2. Enter BASIC with a start size of 256 and run "ORIGIN" ADMIN>basic s=256 -nr pgm=ORIGIN NOTE: If a 'SECURITY VIOLATION' message occurs, run "pgm/ORINST" to install the key in /etc/level/ADS to the ORIGIN security file. Normally, this is done during the UPDATE program but the pgm/ORINST can be used if the above message occurs. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg015 3. Enter the account name "MAI.ORIGIN" and the password "ADMIN" at the menu system log-on. NOTE: ORIGIN 2.1A account names will remain when updating from ORIGIN 2.1A. ORIGIN 2.0A and ORIGIN 1.3A/B users are not converted to ORIGIN 2.1B due to the major security enhancements in the Presentation Services menu system. NOTE: When logging into ORIGIN 2.1B for the first time, you must re-enter the data node and program node at the MAI ORIGIN USER LOG-ON screen. 4. If users were not converted or new users must be created, set up ORIGIN users as described in Section 2.7. NOTE: Installations being updated from ORIGIN 2.1A do not need to set up ORIGIN users but they must log-off any 2.1A user left active and then log-on again. 5. The /origin/r20a/rt directory may be deleted if this is a new ORIGIN 2.1B installation and/or no applications generated with ORIGIN 2.0A will be running on the system. 2.7 SETTING UP A USER FOR ORIGIN ON THE 2000/2500/3000/4000 NOTE: A Business BASIC program may be written to set the user's prefix and run "ORIGIN" since a lot of overhead will be used going into command mode and then BASIC. 1. Using the ved command, create a string file that sets your prefix and executes ORIGIN. ADMIN>ved /origin/startorigin The string file should look like this: _____________________________________________________ | cd /usr/origin | | ad /origin/r21b /PS /PS/tools | | basic s=256 -nr pgm=ORIGIN | |_____________________________________________________| NOTE: The /usr/origin directory is an example only. The primary directory should be where you want all of your ORIGIN generated programs and data files created. 2. Make your string file executable using the filemodes command. ADMIN>filemodes +x +x /origin/startorigin NOTE: Steps 1 and 2 should only be done once. Multiple copies of the start origin file are not needed. 3. Use this file as the initial program for the ORIGIN user in the 2000/2500/3000/4000 operator maintenance, oprinfo. Your initial program should look like this: /bin/command,/origin/startorigin 4. Set up your ORIGIN users: SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg016 o Select Utilities from the ORIGIN main menu. o Select User Maintenance Make the ORIGIN account name the same as the system log-on account name. Refer to the MAI ORIGIN Systems Support Manual, M7510A for more information on user log-on. 5. Set up your ORIGIN System Parameters: o Select Utilities from the ORIGIN main menu. o Select System Administrator Utilities. The password is ADMIN. o Select ORIGIN System Parameters Maintenance. o Enter a Work Files Node. This node will be the directory in which all the temporary ORIGIN files will be created. If you are updating ORIGIN from. a previous level, keep the directory already in use. Normally, this node is " /origin/work/ ". 3.0 ORIGIN INSTALLATION 3.1.1 ORIGIN BACKUP: Back up all ORIGIN data files before upgrading your current version. This backup can be done either to a tape or to the disk in a separate directory or node. By using a separate prefix, this backup would allow you to work with the previous ORIGIN release. 3.1.2 UPDATE PROGRAM: The UPDATE program should be run just one time when installing the ORIGIN product. After a successful installation you may want to delete, rename or change the usage rights of this program to avoid any further use of this program. 3.1.3 DOCUMENTATION AND WORK FILE INFORMATION: ORIGIN 2.1B introduces many code modifications to fix problems with the IOLIST structure but ORIGIN is not able to correct corrupted information written to the documentation and work files on prior ORIGIN releases. You MUST re-initialize your program from the IDD or application program documentation to reset the program item structure. If this is not done, ORIGIN 2.1B will be working from corrupted data. This is extremely important to remember when troubleshooting any ORIGIN 2.1B problems. You should be aware of your current ORIGIN documentation: when it was generated and by which ORIGIN level. If the documentation was created on a previous level of ORIGIN, the ORIGIN programs MAY need to be re-initialized from the IDD. 3.1.4 DUPLICATE FILES: After installing ORIGIN and Presentation Services on the system, there are copies of the same programs and files in various nodes or directories. To explain what the different directories are used for please read the following: SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg017 1) .ORIGIN.R21B.RT.xxxxxx : Master copy 2) .PS.TOOLS.RT.xxxxxx : PS copy (see Section 3.1.5) 3) .Rxxxx.SYS.RT.xxxxxx : Standalone copy (MPx system) 4) /bin/rt/xxxxxx : Standalone copy (SPx or GPx system) The master copy is always located in the developers' prefix list for development and testing purposes. The Presentation Services copy is used for the Presentation Services Report if no ORIGIN was installed. The standalone copy is created during the installation. The 'Rxxx.SYS.' is the current system prefix on an MPx system. this copy will be used for any ORIGIN generated application so ORIGIN would not need to be included in the users' prefix. With an SPx or GPx system, the '/bin' directory must be included in the users' prefix although the ORIGIN directory would not need to be included. 3.1.5 PRESENTATION SERVICES ORIGIN RUN TIME PROGRAMS: If Presentation Services Menu Builder or Presentation Services Form Builder is installed on the system, update the ORIGIN run time programs located under the PS tools directory with the programs provided on the ORIGIN 2.1B tape. All ORIGIN run time programs begin with RT.ENG*. 3.2 UPGRADES FROM LEVELS 2.0B AND PRIOR: 3.2.1 RUN TIME UTILITIES: The ORIGIN 2.0A run time utilities provided with the ORIGIN 2.1B product tape can be used when working with application programs generated with ORIGIN 2.0A or 2.0B. The prefix list for any user running these applications must include the ORIGIN run time prefix, for example: MPx: ().ORIGIN.R20A.RT. SPx: /origin/r20a/rt GPx: /usr/origin/r20a/rt The prefix may be different depending on how the product is installed on your system. This prefix should be placed after. your current ORIGIN prefix. 3.2.2 ORIT12 PROGRAM NOT USED: The 12-hour time function was changed with ORIGIN 2.1A so the program ORIT12 is no longer used. Change all derived items using the time format to use the FNT12 function introduced in ORIGIN 2.1A. NEW FEATURES, NOTES AND CAUTIONS The following sections in this software announcement will cover new features, notes and cautions, and helpful hints. Many of the helpful hints include workarounds for creating reports and application programs. 4.0 GENERAL: 4.1 USAGE RIGHTS: SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg018 ORIGIN defines files (work, temporary and production files) with unrestricted usage rights. Any user is allowed to access all ORIGIN defined files. The usage rights used are W(*.*) on MPx, -rw -rw on SPx and -rw-rw-rw-on GPx. 4.2 RELATED FILE RELATIONSHIPS: There is a new maximum of 254 file relationships per file within the Integrated Data Dictionary, Application Generator and Report Generator. 4.3 MEMORY REQUIREMENTS: There is no memory requirement validation in ORIGIN when generating an application or report program. If you get an error 31 during program generation, apply the suggestions listed in Section 9.0, PROGRAM SIZE. If you work with ORIGIN on an SPx or GPx system, set the terminal memory to a minimum of 256 pages. This restriction applies only when working with ORIGIN to generate programs. Most ORIGIN generated applications can be executed using less than 256 pages of memory. 4.4 DERIVED ITEM CONDITIONED EXPRESSION: You may define one condition within the derived item expression to assign two possible values to the same derived item upon condition evaluation. The derived item expression syntax for this new feature is as follows: log-expr?= := Where: log-expr: The logical expression portion of the statement containing two expressions, either string or numeric, separated by a relational operator. The log-expr syntax is: -or- is any valid numeric or string expression. is any valid business basic logical operator: >, >=, <, <=, =, <>, ><. NOTE: We suggest using '><' instead of '<>' for a 'not equal to' comparison. is used when you want to know if a numeric item is not equal to zero, or a string item is null. This generates code like: IF A><0 THEN ... ELSE ... for numeric items IF POS(" "> is a valid ORIGIN derived item or expression to be executed after the condition evaluation. You must enter one after the condition's THEN ('?=') and another after the condition's ELSE (':='). The THEN and ELSE must be the same type. The user should set the condition expressions as derived items instead of putting the full expression in the condition. Example below is too complicated: POS("CODE"=<2>)><0 ?= <10>+<11>/<15>*<201> := <215> Example below is better: First derived item : <2XX> = POS("CODE"=<2>) Second derived item: <2YY> = <10>+<11>/<15>*<201> Derived expression : <2XX>?=<2YY>:=<215> The goal is to define a derived item expression as simply as possible to avoid syntax compiling problems. Avoid the use of logical operators AND/OR in this condition. 4.5 APPLICATION OR REPORT PROGRAM STANDARD HEADINGS: The CUT and PASTE function within the screen editor may be used to define standard headers or any other display/report related standard for your application or report programs. The CUT/PASTE function works with the file 'usrWPS' where 'usr' is the current user logged into ORIGIN. This file is located in the 'User Workfiles Node',if one was specified; or in the users' primary prefix. ORIGIN will create this file only when the user uses the CUT/PASTE function the first time but you may have one 'usrWPS' master file with all your screen standards and copy this file for any new ORIGIN user working on your system. The copy may be 'total', overwriting the current user CUT/PASTE file, or record by record, saving any user 'clip' record. You may also use the CUT AND PASTE function to move or copy screens between projects or programs. The file 'usrWPS' is defined at statement 7090 in the program ORIWPS with ten records of 1920 bytes . per record. 4.6 USER WORKFILE NODE: A common system directory or prefix may be defined for your ORIGIN users. This directory or node could be used by ORIGIN to define any related user work files, except the project documentation file. The project documentation file is named DC0 and is created in the user's primary prefix node or directory. The user workfile node can be used for improving the backup procedure, implementing standards, evaluating the current ORIGIN disk space usage, porting, etc. 4.7 GRAPH INTERFACE: When running ORIGIN generated reports or ORIGIN generated applications SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg020 interfacing with MAI Business GRAPH, include the GRAPHICS prefix and the '/etc' directory (SPx or GPx) or ().ETC. node (MPx) in your current prefix list. Also, verify the 'plotters' file has the proper usage rights. 4.8 CUSTOMIZING ORIGIN SHELL PROGRAMS: The shell programs ORIGIN uses to generate application or report programs may be customized to include any additional code required. You may add any code needed for: functions, large dimensioned items, special timeouts, etc. The shell programs are: .PGM.ENGRP7 - Report shell .PGM.ENG6 - Application Program shell .PGM.ENG6OE - Line Order Entry shell These programs do not use statements 10000 - 16000, so additional routines may be added within that range, using a GOSUB to do the link. 4.9 RUN TIME UTILITIES USE ON SPX OR GPX: The ORIGIN installation procedure will allocate a set of programs under your current '/bin' (SPx) or '/usr/mbf/bin' (GPx) directory. This directory is not used as a system directory, so you must include this directory for any user working with ORIGIN generated applications which require the run time programs. 4.10 DISPLAY OR PRINT ATTRIBUTES IN GENERATED PROGRAMS: To display or print attributes in your generated application or report programs, define derived items to store and execute them. The derived item expression must be set as: 'EG'++'BG' The escape sequence required by the mnemonic must be enclosed between the 'EG' and 'BG' mnemonics which will disable/enable the error 29 generation (unsupported mnemonic) in order to execute the print directive on either screen or printer device. If the escape sequence is an MBF mnemonic, it should be enclosed by single quotes ('). For a non-MBF escape sequence start with CHAR(27) which is an ESCAPE. This increases the program portability. For example: 'EG'+'SB'+'BG' - Set background 'EG'+'SF'+'BG' - Set foreground 'EG'+'FF'+'BG' - To force a formfeed in the report. 'EG'+CHR(12)+'BG' - Standard printer code for a formfeed. 'EG"+CHAR(27)+ "SF"+'BG" - Set foreground using CHAR(27). 4.11 TRANSLATION TABLE NAMES: On an MPx/AS system, the translation table name must be in upper case and begin with an alphabetic character. Avoid the use of a slash in the name when using an SPx or GPx system. 4.12 FILE TYPES ALLOWED FOR APPLICATION OR REPORT PROGRAMS: Application programs may be based on MULTIKEY or DIRECT file types only. Report programs may be based on MULTIKEY, DIRECT, SORT and INDEXED SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg021 files. If a report must be based on a SERIAL file, define the serial file as an INDEXED file in the IDD. Generate a report based on that INDEXED file but then run the report on the serial file. 4.13 DT-4313/14 ARROW KEYS AND NUMERIC PAD: ORIGIN 2.1B will not change the user's current numeric pad setup. The BACK SPACE and BACK ARROW keys have the same HEX value (CHR(8) or $08$) so you will get the same results using the ORIGIN editor in screen or report line maintenance, or word processor type fields. If you want the back space and back arrow keys to work differently, edit statement 0143 in ORIGIN. This statement is REM'd out but if the REM is removed, a hex value of $12$ or CHR(18) will be used. Redefine your terminal setup for the left arrow only in ORIGIN's Screen Editor Function module. You may need to modify the runtime program ENGNFS at statement 0064 to remove the reference to 'CHR(10)'. If you have any application working with the arrow keys values, you may not be able to use this modification. 4.14 SCREEN EDITOR FUNCTION MODULE, TERMINAL SETUP: DT-4313 and DT-4314 Terminals Only. After installing ORIGIN 2.1B, you must reset the Screen Editor Function for your DT-4313 and DT-4314 terminals. To do this, use the following procedure on the DT-4313/14 terminal: 1. Perform a master reset: +++ 2. At the ORIGIN Main Menu select "Utilities". 3. At the UTILITIES menu select "Screen Editor Function Menu". 4. At the SCREEN EDITOR FUNCTION Menu select "Terminal Editor Key Association". 5. At the TERMINAL EDITOR KEY ASSOCIATION program function selector, enter CR for ENTER NEW RECORD. 6. At the TERMINAL TYPE NUMBER input enter 5. 7. At the FUNCTION input enter 16 for a "Left 1 Character" function (Left Arrow key). Two possible prompts are: - 1. TOUCH THE KEY FOR THIS FUNCTION ('X' = NO CHANGE): or - 2. ENTER NAME OR NUMBER TO MODIFY: With the first prompt, go to step 8. For the second prompt, enter 3 and continue to step 8. 8. At the TOUCH THE KEY FOR THIS FUNCTION ('X' = NO CHANGE): Check the terminal status line: the numeric pad should be enabled which means the 'Pd' status will not display. If you see 'Pd' displayed on the terminal status line, reset it as follows: + After you enable your numeric pad, press the following key sequence: + If the message 'THIS HEX VALUE USED IN ANOTHER FUNCTION' is generated when setting a function with an already used hex value, the conflicting function number will be displayed; otherwise, the program will stop at the input for the key id. 9. At the KEY ID input, enter a brief description for the Screen Editor key just defined. This description will be used for help displays. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg022 10. Repeat steps 7, 8 and 9 to perform a complete redefinition of the four arrow keys. The function numbers are: '08' for the UP arrow, '09' for the DOWN arrow, '14' for the RIGHT arrow and '16' for the LEFT arrow key. 11. When the arrow key re-definition is complete, return to the "Screen Editor Function Menu". 12. At the SCREEN EDITOR FUNCTION Menu, select the "Set-up Terminal After Changes" 13. At the TERMINAL FUNCTION SET-UP, enter the terminal type prompt with a '05' (for DT4313 and DT4314). 14. After performing all above steps, all current ORIGIN users must log-off and log-on ORIGIN to work with the latest modification; otherwise, they will get unexpected results using the ORIGIN editor program. 4.15 DERIVED ITEM EXECUTION: ORIGIN executes each derived item after the last item belonging with the derived item expression has been executed. For example: Derived item expression: Executed after execution of item: <1>+5*<7> <7> <5>*<212> <5> or <212> (latest executed) "STRING" Once, at initialization 3.1416 Once, at initialization To control the execution of a derived item in a generated report or application program, append a 'null reference to the derived item being used. A 'null reference' for a string item would be: <2>(1,0). For numeric items it would be: <3>-<3>. Both produce a null or zero result. For example: Derived item expression: Executed after execution of item: "T"+<7>(1,0) <7> (assumming item <7> is a string) 3.1416+<5>-<5> <5> (assumming item <5> is numeric) 4.16 MULTIPLE CONDITIONS: To link two or more conditions to a report line or derived item within a report or application program, use the following logic: 1. Define all the conditions required by the algorithm using condition maintenance on application or report program. 2. Create a derived item for each condition. For example, we will assume the following derived items: COND01, COND03, ..., COND0n 3. The expression for each derived item must be: "T"+(1,0) The value will be 'T' meaning true. The timing item is used to indicate when the derived item execution will take place. 4. Each of these derived items must be assigned to one of the conditions created/defined in step 1 above. When one of these derived items is being executed, the value will be 'T' if the SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg023 condition is true or ' ' (blank space) for a negative result upon the condition evaluation. 5. Create the LINKER condition with an expression. Example: ="T" AND ="T" AND ="T" -or- ="T" AND =" " AND ="T" -or- (="T" OR ="T") AND =" " -or- whatever combination required by the program. 6. The previous condition, called LINKER in our example, pulls all required conditions together. This logic allows you to link unlimited conditions. 4.17 TOLD MESSAGE AT LOG-ON: The message 'USER ALREADY ON TERMINAL TOLD' displays when the user is logging into ORIGIN. This occurs when the USER logging into the system is running a BATCH GENERATION. Do not log this user out of ORIGIN unless the batch generation process is aborted first. 4.18 TRANSLATION TABLE: The translation table directory is defined under the current product location with no level dependence. Refer to the ORIGIN structure figures 10.1, 10.2, 10.3, 10.4 and 10.5 for where the translation tables are defined for each system type. When generating an application or report program, the translation table directory is assigned to the 'TNODE$' variable and is initialized at statement 16 in the application or report program. This node or directory must be included if you plan to port ORIGIN generated applications using the distributed process feature or when moving ORIGIN to a different disk or disk partition. 4.19 ITEM DEPENDENCE: Item dependence was improved in ORIGIN 2.1B so item deletion will not occur when third level dependencies are used. Third level dependency is when there are file related items based on a file relationship defined with a derived item as the key, so the file related items are depending on the items or derived items used to define the key expression. When trying to delete the items used to define the file relationship key expression, a reject message will be displayed. 4.20 TEMPORARY FILES: When using some ORIGIN functions, such as copy and expand during initialization, temporary files are defined. The temporary files used are TxMULTI, ORITx, usrTx, ORI991, ORI998, ORIIx and TEMPx. They are defined in the current user data node entered at the ORIGIN log-on procedure or in the user's current primary prefix. The file allocation depends on whether the user is working with ORIGIN or an ORIGIN generated application. The 'Tx' is your current terminal ID or FID(0). The 'x' refers to your current terminal number without the starting 'T' from the basic variable FID(0). The 'usr' refers to the current user code working with ORIGIN on that terminal and 'prj' is the active project code for the terminal in use. Temporary file explanation: SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg024 TxMULTI: Used by the IDD for miscellaneous processes performed on multi-key files. ORI991: Used during the file COPY AND EXPAND process during ORIGIN log-on or when changing the current project code. ORI998: Used by the run time utilities and graph interface process. usrTx: Used by the Application Generator when the file has been modified in the IDD and is being updated. ORITx: Used by the run time for executing the user sequence. ORIIx: Used by the run time for letter generation. TEMPx: Used by the ORIGIN program and the generated application and report programs. This is the temporary file used to expand a full file. ORIGIN 2.1B will create these files with general usage rights and will delete them during a successful execution of the routine. If the routine is aborted or you are working with a prior ORIGIN release which did not delete temporary files, error 12's may occur. If an error 12 does occur, the temporary file must be deleted through a command or the system utilities. 4.21 GENERATED PROGRAMS ON TERMINALS GREATER THAN T99: ORIGIN 2.1B now supports generated programs running on terminals greater than T99. 4.22 MODIFYING ORIGIN FIELD INFORMATION: Not all ORIGIN fields in the Data Dictionary, Application or Report Generators can be edited with word processing type functions. Functions such as inserting or deleting characters by moving across text without deleting the current information are not allowed. If fields are modified using left or right arrow keys, form-feed characters will be inserted in the field even though the edit function appeared to work and the text looks correct. The form-feed characters inserted in the modified field would affect any report being printed if it includes that field, causing extra form feeds. 5.0 INTEGRATED DATA DICTIONARY 5.1.1 NUMERIC FILE NAME: Do not use a numeric name for a file defined in the Integrated Data Dictionary. Enter a name beginning with an alpha character instead. The name in the FILE NAME field is an internal ORIGIN name and is not used to define a physical file on your system. The DEFINED NAME field is the file name used for creating files. A numeric name can be entered in this field to allow application or report programs based on files with numeric names. Multi-key files with numeric names are not supported in application or report programs generated by ORIGIN unless a full path name is used. 5.1.2 FULL PATH NAME IN DEFINED NAME FIELD: Although the IDD allows a full path name to be entered for the DEFINED NAME field, the application and report program SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg025 generators may have problems when trying to define that file since ORIGIN is designed to create all files in the user's DATA NODE and PROGRAM NODE. 5.1.3 BUSY FILE CONTROL RECORD: A busy file control record is written to the ORIGIN data dictionary file 'IDDF01' when selecting a file for maintenance. This record remains in the file if there is abnormal exit from your IDD. Examples of abnormal exits are dropping to console mode or releasing a task working in this module. This record may be removed by selecting the file again or writing a program to remove any record from the IDDF01 file with a key size equal to nine. 5.1.4 NUMERIC ITEM AS A KEY ELEMENT: When using a numeric item as the key, ORIGIN uses the current numeric mask for the required string type key expression. If. this will cause a problem for the user, create a string derived item with the mask required for the application and use it to create the file relationship instead of allowing ORIGIN to create it. 5.1.5 FILE COPY WITH DERIVED ITEM AS A KEY: You should not copy file structures defined with derived items as primary key or sort file keys between databases because an error eleven may occur. You should remove any derived item references from the file record layout before copying to the new database then redefine these items at the new database. 5.2 MULTI-KEYED FILES 5.2.1 DIRECT TO MULTI-KEY FILE CONVERSION: When converting a direct file with a derived item as a key to multi-key file format, if the derived item expression contains constant elements like string text, that element will be removed from the composite item being generated to become the multi-key file key. 5.2.2 MULTI-KEYED FILE FORMAT VS DICTIONARY FORMAT: The error message 'The multi-keyed format is not the same as the dictionary format' will be displayed whenever a multi-keyed file containing subscripted (composite) fields is created or defined in the IDD. In the example below the second field in the file is 50 bytes. The next four field definitions are subscripted from the second: FIELD1 STRING 10 BYTES FIELD2 STRING 50 BYTES FIELD3 COMPOSITE <2>(1,10) FIELD4 COMPOSITE <2>(11,10) FIELD5 COMPOSITE <2>(21,10) After the error message displays, to update the IDD definition. This will not alter the file structure or damage data. ORIGIN will change the last subscript to match what FMTINFO returns. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg026 5.2.3 UPDATE FORMAT CHANGES: After modifying a multi-keyed file item, the system displays a warning message about the difference when exiting the File/Record Layout Maintenance. The three possible responses to this message: 1. Update IDD 2. Redefine 3. Leave Unchanged The 'Update IDD' option will not work when leaving the File/Record Layout Maintenance but if the 'Leave Unchanged' option is chosen, the user will exit and can then return to the File/Record Layout Maintenance. A prompt will appear with the same three responses. Now if the user selects the 'Update IDD', it will work. This is the correct procedure for format change updates. The UPDATE IDD routine does not keep track of binary items ENCRYPT or DENCRYPT derived items. If a multi-keyed file has been defined with these types of binary items and the record structure must be modified, the binary items must be re- entered. If re-define is used the binary fields with encrypt and decrypt derived items will be kept. It is recommended that 'live' files are not used and a backup is done before using this option. 5.2.4 COMPOSITE ITEMS: Multi-keyed files may be defined with composite fields in the middle of a record when working with the Integrated Data Dictionary in ORIGIN 2.1A. This definition could then be used to generate application programs. With ORIGIN 2.1A, report programs could not be based on this type of multi-keyed file but you could enter all the multi-key composite items at the end of the record in order to produce report programs. This problem has been resolved in ORIGIN 2.1B. 6.0 MULTI-RECORD TYPE FILES IN ORIGIN: Multi-record file structure defines a file capable of storing more than one record format. The application programs working with multirecord file structures sort the file records based on recognition rules. These recognition rules depend on the file type being used. Multi-record file structures were popular on early computer environments when programming languages did not provide enough resources for data file handling. For example, our Business Basic only allowed a maximum of seven active files per task in those early years. This limitation caused programmers and system analysts to improve the utilization of any available system resource. The restriction on the number of data files allowed in application programs made allocating more than one data record structure into a data file almost a necessity. This meant that the data records for customer SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg027 and vendor information were written together into the same file so the application program handling this file saved one file channel and the ability to allocate and address information improved. It also caused some odd combinations. 6.1 USING MULTI-RECORD FILES IN ORIGIN: ORIGIN allows the definition and utilization of multi-record file organization for direct, sort, indexed and line order entry file types although not all possible definitions are allowed. A. Integrated Data Dictionary: o The ORIGIN IDD allows the record recognition rule definition on any direct, indexed, sort and line order entry file being defined. o The record recognition rule may use key and data record items. A data record item is one that is never used as part of the record key. o The record recognition rule is only used for data file documentation through the ORIGIN IDD and for report and/or executive query generation. B. Report and Executive Query Programs: o The record recognition rule defined for the file in the ORIGIN IDD is used during the program initialization. o Only the key items should be used to define the record recognition rule. All the record items can be used for the record recognition rule for a report when the condition is moved from the generated location at statement 1008 to a new statement located after the report item initialization which is between statements 1020 and 1799. o The record recognition rule condition is located in the generated program at statement 1008. The basic variable Z9$ contains the current key value. o The condition is always executed. It does not matter if the current program mode is standard report, executive query or updating for user defined print sequence. If the report allows the definition of user defined print sequence then the condition must be edited to verify the report item D1$ value is not "UPDATE". 7.0 APPLICATION GENERATOR 7.1 IOLIST STRUCTURE: ORIGIN 2.1B introduces many code modifications to fix problems with the IOLIST structure but ORIGIN is not able to correct corrupted information written to the documentation and work files on prior ORIGIN releases. You MUST re-initialize your program from the IDD or application program documentation to reset the program item structure. If this is not done, ORIGIN 2.1B will be working from corrupted data. This is extremely important to remember when troubleshooting any . ORIGIN 2.1B problems. If the documentation was created on a previous level of ORIGIN, the ORIGIN programs may need to be re-initialized from the IDD. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg028 7.2 KEY ITEMS ALLOWED: The maximum number of key items supported is eleven. Use derived items to bypass this restriction. 7.3 PREVIOUS VALUE FOR NUMERIC INPUTS: Numeric inputs will now support defaulting to the value entered on the previous record. 7.4 SCREEN MAINTENANCE: With the application generator screen maintenance, the item name is displayed when using the move item option. 7.5 QUERY BY EXAMPLE ON FILE WITH NO FIELD RECORD SEPARATORS: This query only works for the first field in the record. To address. all the fields in the record, make the following modification: 0358:;XU8$=BIN(DEC(U8$(LEN(U8$)-3,2))+DEC(U8$(LEN(U8$)-1,2) )-1,3), U8$(5,3)=XU8$(2) NOTE: Add this code to the end of statement 0358. The target field must be the first field and the target string will be searched through all fields in the record. 7.6 CONDITIONS: The 'CTL-II' will not always backup on conditioned items because the condition keeps you in the same field. This can be controlled with another condition set just before the input. Define this condition to skip to the appropriate field. The variable 'C0$', which is used to store the value of the last 'CTL', can be used to create the suggested condition. 7.7 VARIABLES: Some variables used in the application programs are listed below: X(3): Contains the input number in execution and is always an integer. C0$ : Contains the CTL value used for the executing input. Possible values are: '0', '1', '2', '3', and '4'. X8$ : Contains the information being entered. When the value of POS(" "<>X8$) is zero or X8$ is null, nothing was entered. 7.8 FUNCTION KEYS: To enable or disable your function keys when running a generated application program, use the following keyboard sequence: + + <0> Enables the terminal function keys. + + <1> Disables the terminal function keys. 7.9 MISSING RECORD MESSAGE FOR FILE RELATIONSHIPS: Application programs generated by ORIGIN now feature a detailed message on a missing record with a defined file relationship. The message for the missing record will display the FILE REFERENCE NAME assigned to the ,record in the Integrated Data Dictionary and the current key value between parenthesis. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg029 7.10 SUB-MENU DEFINITION: Be especially careful when defining an overlay program through the sub-menu option if parameter items are defined between the programs. ORIGIN generates the application program with a link CALL statement without saving the variable values being passed between the two programs. The CALL statement will be as follows: 880X ...; CALL "xxxxxx",ERR=8890,P1$,P2$ ... Pn$ Whatever modification or change is made on any of these variables will be reflected in the calling program. If the called program is able to modify any of the parameter values, which is most likely to happen with ORIGIN generated programs, and this is a problem for your application program, you need to create a derived item for each parameter that needs to be protected. Items being used as the key on related file references and parameters for sub-menu programs could cause missing record messages when returning from the called program. 7.11 PREFIX/SUFFIX DEFINITION: The C$ variable for prefix or suffix is now properly set on application programs. Statements 3855, 3904, 5606 and 7714 for standard applications and statements 3855, 4609 and 7714 for line order entry programs now have C$ as a prefix or suffix based on the current system parameter. Using the variable 'FP$' as VARIABLE NAME allows the generation of statement 20 for application programs and statement 17 for report programs to assign a value to 'C$'. This must be set through derived items only. Do not use on input or related file items. Both statements will display as: #### ; C$=FP$ When FP$ is used to assign a value to C$, the derived item is not generated where it should be on statements 71xx in an application program and statements 103x in a report program. The FP$ variable will be initialized like any other item. ORIGIN does not validate information being stored in C$ to be used for file system activity but is left up to the user. If the derived item is a link to a SUBROUTINE program, the user will get a call to a public program which can set the appropiate value to C$ according to application requirements. This allows the user to prepare and set a value for C$ which then allows ORIGIN to open different sets. of files for companies, division, department and/or whatever else is needed for individual applications. 8.0 REPORT GENERATOR 8.1 IOLIST STRUCTURE: ORIGIN 2.1B introduces many code modifications to fix problems with the IOLIST structure but ORIGIN is not able to correct corrupted information written to the documentation and work files on prior ORIGIN releases. You MUST re-initialize your program from the IDD or application SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg030 program documentation to reset the program item structure. If this is not done, ORIGIN 2.1B will be working from corrupted data. This is extremely important to remember when troubleshooting any ORIGIN 2.1B problems. If the documentation was created on a prior level of ORIGIN, the programs may need to be re-initialized from the IDD. 8.2 MASK OVERFLOW CONTROL: Asterisks will now print on numeric items with mask overflow where an error 31 would normally occur. 8.3 MASK WITH NEGATIVE SIGN: (EXECUTIVE QUERY ONLY) Masking a whole number with the negative sign on the right side is not supported. If this type of mask is required, use a decimal point after the number followed by the negative sign. So the mask would appear as '##.-', not '##-'. 8.4 132-COLUMN SUPPORT: When printing a 132-column report on a terminal supporting 132 columns, the report will be displayed in 132 columns. Executive Query reports routed to a slave printer or serial file now includes 132-column support. Standard reports already included 132-column support prior to this release. 8.5 FOOTNOTE DEFINITION: To display footnotes on pages, define two derived item using the following procedure: o Use the ITEM MAINTENANCE routine to create the following definitions: - Create a derived item (string) to contain the footnote text. The maximum length allowed is 160 characters. This derived item can be an expression or related from a file but the variable name must be NT$. The derived item definition parameter must be changed so the VARIABLE NAME is NT$. - Create a second derived item (numeric) to contain the output size of the footnote text. This can be either 80 or 132 columns, depending on your application. The derived item definition parameter must be changed so the VARIABLE NAME is RS. 8.6 SPOOLING ATTRIBUTES: All ORIGIN reports will prompt for system spooling attributes like class, copies and priority. 8.7 SLAVE PRINTERS AS OUTPUT DEVICES: Reports may only be printed to the slave printer attached to your current terminal if this printer has been configured on the system. When working on an SPx or GPx system, select a printer class with the SPOOL parameter set to 'no' because the operating system does not support slave printer references to a class with the SPOOL parameter set to 'yes'. 8.8 MULTI-KEYED FILES: Reports based on multi-keyed files now feature the IOLIST with a SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg031 multi-keyed file format which allows the definition of multi-keyed files in the data dictionary with composite fields in the middle of the record. 8.9 SORT FILE REPORTS: Reports based on sort files are now supported. 8.10 SAVED OPTIONS: On prior releases of ORIGIN an error 26 or error 47 sometimes occurred on re-generated reports working with old saved option sets. This was because the new report program would add, delete or modify report variables, sort file definitions and other critical items in the report which then caused these errors. An option file compile feature was added to ORIGIN 2.1B to keep the option file integrity between generations of the same report. To prevent these errors, rename the old generated program and option files located in each user's primary prefix whenever a new program version is being released and define some naming standards for each options set for easy updates. Please refer to Section 10.0 ORIGIN WORK ENVIRONMENT in this software announcement for further information. 8.11 DEFINING START/STOP KEYS: When start or stop keys are entered for sorting or reporting while the key displayed is 'BEGINNING' or 'END', a carriage return for the default will set the key to blanks. Enter CTL-I to keep the 'BEGINNING' or 'END' as the default. There are limitations for using masked items for start/stop keys. Invalid items include a masked string, masked dates and masked time format. 8.12 SUMMARY FILE SIZE: Error 2's, end-of-file, may occur when running summary reports based on a report with many breaks and sub-totals. The SUMMARY file was . being defined by ORIGIN with an standard size of ten records with 132 bytes per record which may be enough for almost all reports. With ORIGIN 2.1B, the SUMMARY file is now being created with 10000 records: 132 bytes per record, initial number of records=10 and a growth parameter of 10 records. The file is not re-defined by the run-time program but will remain at the initially defined size for all previously generated reports. If a larger file size is required for previously generated reports, modify the program 'ENGNNR' under the ORIGIN run time directory at statement 8130 to replace the current value of "10" with a larger value. Remember, a report working with the summary option will allocate the summary file as large as specified in statement 8130. The summary file size may be customized using the report name stored in the variable I0$. 8.13 INPUT FIELDS: SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg032 Derived items can be defined in your report program data base to be executed as a parameter input when running your generated report. To do this enter the keyword INPUT at the begining of the derived item expression in uppercase with no spaces followed by syntax rules described below: Expression syntax: INPUT : : [ CASE = < U|L > :] [ LIST = :] [ HELP = [^|!] :] [ MIN = :] [ MAX = :] [ DEFAULT= :] [ MASK = :] o - The input prompt text o CASE = < U|L > - Keyword used to define some text attributes for the data coming through the input statement. This parameter allows two possible values: 'U' for uppercase and 'L' for lowercase. The input text will remain unchanged when this parameter is not used. o LIST = - Keyword used to define a verification list which will be applied to the data coming through the input statement. Each value in the list should be separated by a comma. o HELP = [ ^|! ] - Keyword used to select a program or command to be executed while the input is in progress. The symbols '^' or '!' must be used to indicate the kind of file (program or command) that will be used. The '^' indicates a basic program name was entered at the file name and the '!' indicates a command or serial file was specified at the file name. o MIN = - Keyword used to specify the minimum value or length of the item being entered. The minimum value applies to numeric data; otherwise, this parameter specifies the expected length. o MAX = - Parameter used to specify the maximum value or length of the item being processed. o DEFAULT = - Allows a default value to be assigned to the input being processed. o MASK = - Keyword used to specify the mask used for the input routine of the item being requested. The masking character is 'X'. Example: INPUT:ENTER ZIP CODE: HELP=^ZIPPGM : MIN=5:MAX=9:DEFAULT= 926260000:MASK= XXXXX-XXXX 8.14 RENAME RESTRICTION ON GPX: Do not use a name over six caracters for ORIGIN generated reports on the GPx. The operating system only allows a maximum of fourteen characters for file and program names. An ORIGIN generated report SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg033 defines files with '.OPTIONS' and '.SUMMARY' appended to the current report program name. With the 8-character suffix, the maximum length of the report program can only be 6 bytes long. 8.15 USER DEFINED PRINT SEQUENCE: When working with defined sequences, error 11's may be generated when maintaining the report's main file if a record is removed that had already been sorted by the report. 9.0 PROGRAM SIZE An error 31 may occur when generating an application or report program from ORIGIN. The error 31 may occur when the definitions used to generate the program use all the current terminal memory. Error 31's can be classified as two different types. The first occurs if the generated statement code is too big to be compiled. The second occurs if the program being generated is too large, causing basic to return a memory error. The following sections include helpful hints for trouble-shooting and resolving error 31's. 9.1 ERROR 31 TROUBLE-SHOOTING: Before an error 31 can be resolved, some time must be spent determining what caused the error to be generated. In order to identify the reason for the error, first record the MERGE SECTION number in progress when the error occurred and drop to CONSOLE mode . without losing the program that is in memory. If generating a report program, the program name will be ENGRP7. If generating an application program, the program name will be ENG6 or ENG6OE. Once you are in console mode, do not save the program. If you do, an original copy of that program will need to be restored from the latest backup or product tape. While in console mode, print the current program size divided by 1024, using the code: PRINT PSZ/1024. The maximum program size supported in Business Basic is 64Kb so if the current program size is close to that number, the error is being caused by the program size. If not, the error is caused by a statement that is too large. 9.2 ERROR 31 GENERATING LARGE PROGRAMS: o Report Program Generation: After verifying the error 31 is caused by a large program, try to save some space by removing unused functions from the shell or using sub-routines to perform some of the report processes. o Application Program Generation: When generating application programs, there are more alternatives to resolving the error 31 since ADS provides parameters to control the program size. These parameters may be found under 'Program Parameter Maintenance' and 'Program Function Maintenance'. Program parameter maintenance allows the definition of 'Smaller Program' and the call module, 'Screens'. The 'Smaller Program' directs the generation process to define an indexed file to store each input item parameter which may help programs using many input items. The 'Screens' parameter causes the generation process to build a program sub-routine to display all the program screens . SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg034 which may help programs using many screens. Program function maintenance controls different sections of the program being generated so the required code for each of these functions is removed from the shell program during generation when DISABLE is set to 'N'. Even though program design will be affected, it may be necessary to generate one program for the file maintenance process and another for queries in order to avoid memory errors. 9.3 ERROR 31 DIAGNOSIS ON LARGE STATEMENTS: This is a common report program generation error occurring with programs containing many derived items. This error occurs when ORIGIN is generating statements 1030, 1032, 1034, etc. which will be referred to as the '1030 group' in the troubleshooting sections. The error 31's may also occur elsewhere although this is not common. For general trouble-shooting use the following steps: Application Report --------------------------- ------------------------- >PRINT ATTR(Z,"NAME") >PRINT ATTR(1,"NAME") filename filename >PRINT IND(Z) >PRINT IND(1) value value >READRECORD(Z,IND=value-1)L$ >READRECORD(1,IND=value-1)L$ >PRINT L$ >PRINT L$ ####: ... ####: ... >RUN >RUN Where 'filename' is the file being merged, 'value' is the current index in execution and '####' is the statement being executed when the error occurs. The program then resumes generation. 9.4 ERROR 31 ON LARGE STATEMENTS - RECOVERY: After generation is over, go into console mode and enter the missing statement. To do this, create a serial file with 10 records of 1024 bytes. Then enter and run the following program: >END >DELETE >0010 BEGIN >0020 INITFILE "sefilename" >0030 OPEN(1)"filename" >0040 OPEN(2)"sefilename"; LOCK(2) >0050 READRECORD(1,END=1000)LINE$ >0060 IF POS("####"=LINE$)=1 THEN WRITERECORD(2)LINE$ >0070 GOTO 50 >END >RUN NOTE: The 'sefilename' is the serial file created in the first paragraph of Section 9.4. The 'filename' is the file created in Section 9.3. Use the system editor to divide the statement from above into smaller statements of less than 2000 bytes each. Since ORIGIN never uses statement numbers from the 10000-16000 range, the easiest method is to enter '#### GOSUB 10000'. The first SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg035 '####' section of the original statement then becomes statement '10000'. If this method is used, do not forget the RETURN after the last section. Use the following steps after statement '####' has been divided into smaller sections: >END >LOAD "your generated program" >OPEN(1)"sefilename" >MERGE(1) >SAVE If an error 2 occurs at the MERGE(1), ignore it and keep going. This procedure should be followed each time a program is generated with an error 31 caused by a large statement. 9.5 ERROR 31 ON LARGE STATEMENTS AT 1030 RANGE: If the error 31 occurs on a statement in the '1030' range, the procedure described in Section 9.4 is unnecessary. Instead, ORIGIN can be forced to cut the statement by assigning a condition to one item belonging to the large statement producing the error. The suggested condition can be as simple as '1 = 1' or "A"="A". It only needs to be a condition that will always be true. When used, this condition will divide a large statement in two. 10.0 ORIGIN WORK ENVIRONMENT: This section gives an overview of the ORIGIN working environment including helpful hints on setting up the working environment for your organization. 10.1 DEFAULT STRUCTURE: Figures 10.1, 10.2, 10.3, 10.4 and 10.5 displays the standard ORIGIN structure for GPx, MPx and SPx systems. There is a slight difference between the GPx and SPx systems when ORIGIN is installed on a second disk drive or partition because the ORIGIN prefix path must include that directory. Also, on GPx systems the ORIGIN 'transtable' directory is found under 'usr/origin' because all translation table definitions or maintenance occurs under ORIGIN. The public key file location is not shown. 10.2 WORKFILE DIRECTORY: A common directory may be defined for all ORIGIN users involved with program generation. ORIGIN provides a method for defining this directory. Users do not need the working directory in their prefix to work with it. Follow the steps below to define the working directory: - Set your prefix to work with ORIGIN. - RUN "ORIGIN" - log-on if necessary. - Select: Utilities at the ORIGIN MAIN MENU. - Select: System Administration Utilities at the UTILITIES MENU. - Enter your password. - Select: ORIGIN System Parameter Maintenance at the SYSTEM ADMIMISTRATOR'S MENU. - Select option 11: USER WORKFILES NODE and enter the name of the SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg036 common directory. NOTE: If there is already a directory defined in this option, do not change it since that directory will already be used as the working directory. The workfile directory is defined with general usage rights. A common workfile directory may help with: - ORIGIN backup procedure. - ORIGIN update procedure. - ORIGIN porting procedure. - ORIGIN enhancement. - System maintenance. The user workfiles defined under the common directory are not ORIGIN level dependent so do not define the workfile directory under the current origin level node or directory, either r21a or r21b. / || / | || | usr || | || | origin || usr | || | ----------------- || origin | | || | r21b transtable || ------------------- | || | | ---------------------- || r21b transtable | | | | || | data pgm rt language || ---------------------- || | | | | || data pgm rt language || Figure 10.1 Figure 10.2 GPx's ORIGIN structure under GPx's ORIGIN structure under root a disk or partition (FAMILY) | ----------- | | ORIGIN TRANSTABLE | R21B | ---------------------- | | | | DATA PGM RT LANGUAGE Figure 10.3 MPx's ORIGIN standard structure SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg037 / || / | || | ----------- || ----------------- | | || | | origin transtable || transtable | || | r21b || origin | || | ---------------------- || r21b | | | | || | data pgm rt language || ---------------------- || | | | | || data rt rt language Figure 10.4 Figure 10.5 SPx's ORIGIN structure under SPx's ORIGIN structure under root a disk or partition Figures 10.6, 10.7 and 10.8 display an example of an ORIGIN working environment for GPx, MPx and SPx with a workfile directory, 'work'. The files defined under this directory for each user are 'xxx001', 'xxxD01', 'xxxMR1', 'xxxMR2', 'xxxMR3', 'xxxMR4', 'xxxRF2', 'xxxRPF', 'xxxT01', 'xxxV01' and 'xxxWRK' where 'xxx' is the user code. If an ORIGIN WORKFILE NODE is not defined, ORIGIN defines these files at each user's primary prefix when they log-on into the system. If the user returns to work on ORIGIN with a new or different prefix without the previous files in any of his current directories or nodes, ORIGIN will either display an INVALID LOG-ON message or the files will be defined again. All user work files should be moved to the ORIGIN workfile node after one has been defined if another had been defined previously. 10.3 DEVELOPMENT ENVIRONMENT: Each time a user logs into ORIGIN, there is a prompt for a DATA NODE and PROGRAM NODE. One of these directories should be the user's primary prefix. All ORIGIN workfiles associated with the current user will be defined in the current primary prefix if the files have not been defined there previously or if no ORIGIN WORKFILE NODE has been defined. Because ORIGIN does not connect these files to a single user, the same user may log-on again into a different project with a different prefix list. These two nodes or directories are called development directories, one for data files and one for program files. Each is used by ORIGIN for defining program or data files. When working with ORIGIN and one of the user application files involved in the generation must be redefined, ORIGIN will redefine this file under the current DATA NODE since ORIGIN expects a working environment setup for development and production environments. Using the development directories for a project development environment will have the following benefits: - All user's development programs and data files will be under the same directory. The user may reset their prefix for testing when SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg038 needed. - The project integrity is maintained by reducing chances of having. more than one project file defined. A project file will be defined if it cannot be found during ORIGIN logon. - Improve development backup procedures. - The project manager could audit any project by listing the development directories. / | usr | origin | ----------------------------------- | | | r21b transtable work | ---------------------- | | | | data pgm rt language Figure 10.6 GPx ORIGIN Structure with Workfile Node 'work' (FAMILY) | ----------- | | ORIGIN TRANSTABLE | ------------------------------ | | R21B WORK | ---------------------- | | | | DATA PGM RT LANGUAGE Figure 10.7 MPx ORIGIN Standard Structure with Workfile Node 'WORK' / | ----------- | | origin transtable | --------------------------- | | r21b work | ---------------------- | | | | data pgm rt language Figure 10.8 SPx ORIGIN Structure with Workfile Node 'work' SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg039 10.4 APPLICATION ENVIRONMENT: The previous sections included ideas which could be used to improve the ORIGIN working environment. This section is related to the 'real life' application environment. Specifically, the application development and application production which must be kept separate on the system. Application development involves all the required steps to build the application including but not limited to data collecting, analysis, design, code development and testing until a finished product is developed. Application production begins as soon as you complete the application development when after being trained, the user is able to start working with the application. Some programs may require some minor changes during this time. Once the application reaches the production stage, the application maintenance (maintenance, sustaining, improving, etc) activities must be done with extreme caution. Any modification in file structure, process execution and logic will need to be done 'off-line'. This means any file or program modification requires a documented procedure. In most cases the modification must be done on 'temporary' copies, the backups should be up to date, and the implementation of the modifications should be done with complete knowledge of all persons involved with the process. Figures 10.9, 10.10 and 10.11 display an example of an ORIGIN working environment with the application development included for GPx, SPx and MPx systems. / | ------------------------------------- | | development usr | | ------------- origin | | | data pgm ----------------------------------- | | | r21b transtable work | ---------------------- | | | | data pgm rt language Figure 10.9 GPx ORIGIN Structure with the Development Environment SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg040 (FAMILY) | ------------------------------------------------- | | | DEVELOPMENT ORIGIN TRANSTABLE | | ------------- ------------------------------ | | | | DATA PGM R21B WORK | ---------------------- | | | | DATA PGM RT LANGUAGE Figure 10.10 MPx ORIGIN Standard Structure with the Development Environment / | ------------------------------------------- | | | development origin transtable | | ------------- --------------------------- | | | | data pgm r21b work | ---------------------- | | | | data pgm rt language Figure 10.11 SPx ORIGIN Structure with the Development Environment 11.0 ADS AND DSS GENERATED PROGRAM LINKS OR INTERFACES: The following sections explain what must be done to link ORIGIN generated programs. Directions to link ADS generated programs with DSS report and DSS reports with ADS generated programs are included. Some of the procedures may require some code modifications in generated programs or . additional customization in ORIGIN shell and provided subroutines. Backup copies should be made for any program to be modified for this purpose. 11.1 ADS APPLICATION PROGRAMS USING DSS GENERATED REPORTS: Creating a link between a generated application program and a generated ORIGIN report may be used for multiscreen application programs where the print option only prints a hard copy of the current screen. The user may need a print out with a different format from the current screen. 11.1.1 REPORT OUTPUT FORMAT SIMILAR TO APPLICATION PROGRAM: This report is unique and should only be used for the purposes given. The following steps can be used to create this report: o Clipping the application program screens: - Use the Application Generator to load the application. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg041 program with the screen to be used in the report into your workfile using the initialization option. - Select the screen maintenance option to select the screen to be copied. - Use the 'Cut and Paste' function to make a screen clip. Refer to Section 4.5 in this document for more detail. - Perform this procedure as many times as the number of screens to be copied. Assign different names for each screen clip record. o Pasting the application program screens: - Use the Report Generator to load the report program to be updated with the application screen. - Select Report Line Maintenance to update the report lines with the screens picked up from the application program. - Use the 'Cut and Paste' function to recall or merge the screens into the report lines. Refer to Section 4.5 in this document. - The report format may now be edited: reformat, add or remove static text and variables. 11.1.2 REPORT RUN WITH ONE REQUESTED RECORD: To modify the report linked with the application program, use the steps outlined below. These modifications do not affect the current logic for the report. o A one record report: - Using the Report Generator load the report to be modified. - Using the Report Parameter, option-7, change the current main file break items. Enter the required fields for page breaks on each main file key. - Using the report's record type selection, enter a selection condition as: IF KEY=ADS$ The ADS$ variable initialization will be explained later. - Using the Report Function Maintenance under General Information Menu set all report functions to 'N'. These include: EXECUTIVE QUERY, USER CONDITIONS, USER SEQUENCE, START RECORD, LAST RECORD, DISPLAY KEY OPTION and DECISION SUPPORT. Now, a report program allowing only the output device to be changed will be generated. - Generate the report which will need to be modified. - The ADS$ variable definition will now be done. Load the generated report program and modify statements 0015 and 5022 as follows: Report initialization: Change: 0015 BEGIN EXCEPT Z9$; SETESC 8590; SETERR 8200;IF Z9$ 0015:="QUERY" OR Z9$="LGNEW" THEN GOTO 0016 ELSE IF Z9$ 0015:="REENTERQUERY THEN Z9$="QUERY", Z8$="REENTER" ELS 0015:E IF POS("REENTER"=Z9$)>0 THEN Z8$="REENTER" ELSE 0015:Z9$="" * This statement may be slightly different on ORIGIN 2.1A but the suggested modification is the same. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg042 To: 0015 BEGIN EXCEPT Z9$; SETESC 8590; SETERR 8200;IF Z9$ 0015:="QUERY" OR Z9$="LGNEW" THEN GOTO 0016 ELSE IF Z9$ 0015:="REENTERQUERY THEN Z9$="QUERY", Z8$="REENTER" ELS 0015:E IF POS("REENTER"=Z9$)>0 THEN Z8$="REENTER" ELSE 0015:IF POS("ADS"=Z9$)=1 THEN ADS$=Z9$(4),Z9$="" ELSE Z . -------------------------------------------------- 0015:9$="" ----- NOTE: The "--" indicates changed section. All ORIGIN generated reports include the Z9$ ENTER parameter. This may be used to add functionality to the generated report. Restarting the report: Change: 5022 CLOSE(7);IF CTL=4 GOTO 9000 ELSE IF RESTRT$=CHR(2) 5022: THEN RESTRT$=DEV$,DEV$=""; GOTO 321 ELSE Z9$="REE 5022:NTER"+U0$; GOTO 15 To: 5022 CLOSE(7);IF CTL=4 GOTO 9000 ELSE IF RESTRT$=CHR(2) 5022: THEN RESTRT$=DEV$,DEV$=""; GOTO 321 ELSE IF ADS$= 5022:"" THEN Z9$="REENTER"+U0$; GOTO 15 ELSE Z9$="ADS"+ --------------- 5022:ADS$; GOTO 15 ------------- 11.2 ADS PROGRAM CALLING A DSS REPORT: An application program and a DSS report may be linked through the sub-menu feature available for any application program. No further modification to the application program is required to define this link. Perform the following steps to define the link between an ADS programs and a DSS report: - Using the Application Generator, load the application program being linked with the DSS report into your workfile. - Using item maintenance define a derived item with the following expression: "ADS" + + + ... + ^^^^^^^^^^^^^^^^^^^^^ Must be the main file key expression NOTE: For this example, a derived item number of <2XX> was assumed. - Using the Submenu Maintenance option, under the General Information menu, define the sub-menu entry for the report link. A standard definition could be: 1. SELECTION NUMBER : as applicable 2. SELECTION DESCRIPTION : user's choice 3. SELECTION TYPE : 2 4. SCREEN INPUT NUMBER : not applicable 5. PROGRAM NAME : DSS report name 6. VARIABLE NAME OR NUMBER: <2XX> as only parameter one. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg043 NOTE: Options above are not necessarily in the order requested. - Generate the application program. The sub-menu is displayed at the top of the screen. If needed, redefine functions 8 and 9 of the Program Function Maintenance. 11.3 ADS WITH DSS LINK FUNCTIONALITY: The report program is executed when the defined sub-menu options are selected. The program stops at the standard report selection screen which allows the selection of any available system printers. You may also change another program parameter unless the report functions were disabled as explained in Section 11.1.3. To modify the generated report so it is executed without stopping for any selection, use the following steps: - Load the generated report. - Change statement 0250 to 0251. Change: 0250 CALL RNODE$+U$+"NNR",D0$,D1$,U5$,U4$,U3$,Z5$, ... To: 0251 CALL RNODE$+U$+"NNR",D0$,D1$,U5$,U4$,U3$,Z5$, ... ---- - Modify the original statement 250 (not deleted) to: Change: 0250 CALL RNODE$+U$+"NNR",D0$,D1$,U5$,U4$,U3$,Z5$,M1$, 0250:U4,P9$,T$,Z3$,N0$,P8$,T0$,T2$,D2$,U,D6$, F9$,C$, 0250:K,K2,U0$,Z9$,Z8$,Y8$ To: 0250 IF ADS$<>"" THEN CALL RNODE$+"MYNNR",D0$,D1$,U5$, ---------------- 0250:U4$,U3$,Z5$,M1$,U4,P9$,T$,Z3$,N0$,P8$,T0$,T2$, 0250:D2$,U,D6$ ,F9$,C$,K,K2,U0$,Z9$,Z8$,Y8$; GOTO 252 ---------- This modification performs a CALL to the program MYNNR instead of ENGNNR. The program MYNNR will be defined in the next step. - Copy your current program ENGNNR under the runtime directory to a new name, MYNNR, using the same directory. - Modify the MYNNR program as follows: Change: 1020 INPUT (0,ERR=1010,SIZ=3)@(40,22),'CI',Q$:(""=1100, 1020:LEN =1,2); IF Q$="X" AND U0$<>"" THEN GOTO 283 To: 1020 Q$=""; GOTO 1100 ---------------- With this modification, the report program is executed from your application program, and the options screen is displayed but the program continues without requesting more information. The options set used is the current default set which may be maintained by running the generated report from console. 11.4 DSS REPORT PROGRAMS USING ADS APPLICATION PROGRAMS: The DSS report generator allows the definition of derived items to be executed as inputs in a generated report. In this section an application program is used to do this instead of the generated report. 11.4.1 APPLICATION PROGRAM AS A REPORT PARAMETERS INPUT PROGRAM: SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg044 This program will write all external information required to execute a report into a parameter file. The key to be used must include the terminal identification ( FID(0) ). The report program name to be executed and the current system date and time could also be included. Use the following steps in order to generate this program: - Define a parameter file with the following items in the Integrated Data Dictionary: ITEM# DESCRIPTION TYPE LENGTH 001 RPTPGM L 6 002 TASKID L 4 003 RTDATE D 6 004 RTTIME T12 8 ................................. 00n RPT Parameter x x The key must be items 001+002. This file can be used by as many reports as the application requires. Just create the file with the number of records equal to the number of report programs. - Initialize for a new application program using the file defined on the previous step. - Use the Program Function Maintenance routine (under the General Information Menu) to disable the following functions for the program to be generated: 2. INQUIRY AND MODIFY : N 4. QUERY BY EXAMPLE : N 5. DELETE RECORDS : N 6. ? TO ALTERNATE PGM : N The ENTER NEW RECORDS must be kept as ENABLE (Y). - Change the current key expression to be used by the application program to a temporary value of ten (10) spaces. To do this use the Program and File Maintenance routine (under the General Information Menu) and select option 4 to change the current KEY EXPRESSION. Enter ten spaces between quotes ("). The KEY SIZE will remain with a value of 10. - Use the ITEM MAINTENANCE routine to perform the following definitions: o Derived item 200, named TSKID, must be created with FID(0) as its expression and a length of 4. o Item number 2, named TASKID, must be deleted. o Derived item 201 must be created with the following definition parameters: Name : TASKID Expression : <200> Length : 4 Display Position : at appropiate screen location. Field in main file : FIELD IN FILE (WRITE TO FILE) o Item number 1, named RPTPGM, must be deleted. o Derived item 202 must be created with the following definition parameters: SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg045 Name : RPTPGM Expression : "report name" Length : 6 Display Position : at appropiate screen location. Field in main file : FIELD IN FILE (WRITE TO FILE) NOTE: The "report name" is the report program to be run after this application program execution. o Derived item 203 must be created with the following definition parameters: Name : WRKDATE Expression : DAY Length : 8 o Item number 1, named RTDATE, must be deleted. o Derived item 204 must be created with the following definition parameters: Name : RTDATE Expression : <203>(1,2)+<203>(4,2)+<203>(7,2) Length : 6 Display Position : at appropiate screen location. Field in main file : FIELD IN FILE (WRITE TO FILE) o Item number 1, named RTTIME, must be deleted. o Derived item 205 must be created with the following definition parameters: Name : WRKTIME Expression : FNT12$(TIM) Length : 8 Display Position : at appropiate screen location. o Derived item 206 must be created with the following definition parameters: Name : WRKRTTIME Expression : FNT24$(TIM) Length : 8 o Derived item 207 must be created with the following definition parameters: Name : RTTIME Expression : <206>(1,2)+<206>(4,2)+<206>(7,2) Length : 6 Field in main file : FIELD IN FILE (WRITE TO FILE) - Change the key expression using the Program and File Maintenance routine located under the General Information Menu to: <203>+<202> with a length of 10. - Change the RETURN PROGRAM parameter using the Program Parameter Routine located under the General Information Menu to be the report program to be executed after all the parameters have been entered. - Generate the application program. This application program will write all parameter information used by a report program into a file, direct or multi-keyed, after it is executed. When the report is run, it will use this file information during execution. 11.4.2 REPORT PROGRAM USING PARAMETER INFORMATION WRITTEN TO FILE: The procedure to generate a report program that will use the information written by the application program as default parameters, is as follows: - Use the ITEM MAINTENANCE routine to perform the following SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg046 definitions: o Another derived item must be created with the following definition parameters: NOTE: The number will be different in each program but in this example, assume as the derived item number. Name : RPTPGM Expression : "report name" Length : 6 Query priorities : 0,0,0 NOTE: The "report name" is the current report program being defined. o Another derived item must be created with the following definition parameters: NOTE: The number will be different in each program but in this example, assume as this derived items number. Name : TSKID Expression : FID(0) Length : 4 Query priorities : 0,0,0 o Another derived item must be created with the following definition parameters: NOTE: Assume as this derived item number for this example. Name : TASKID Expression : Length : 4 Query priorities : 0,0,0 o Another derived item must be created with the following definition parameters: Name : PARKEY Expression : + or + . Length : 10 Query priorities : 0,0,0 o The next derived item definition will read all the written information from the parameter file. Use the following steps: - CR TO DEFINE A NEW DERIVED ITEM - CTL-I = RELATED FILE ITEM - ENTER FILE REFERENCE NAME OR FILE NAME: Enter the file name used for the parameter file as defined in the process described in Section 11.4.1. - ENTER KEY ITEM OR NUMBER: The derived item to be used as the key for this file was named PARKEY. Enter PARKEY at this prompt. - CR to CREATE this FILE RELATIONSHIP - RELATIONSHIP RULE SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg047 Enter '0' so the report will not be run without parameters; otherwise,the report will be executed with no conditions. - Select the items to be read from the parameter file. - Complete all the report definitions. - Generate the report. 11.4.3 DSS WITH ADS LINK FUNCTIONALITY: The DSS report program is now using an application program to enter additional parameter information useful for the report. The procedure described in the above sections has the following advantages: - The application program performs all the report input parameter validation. - A report execution status book is being maintained which could be used in some installations. 12.0 KNOWN ERRORS: ORIGIN 2.1B release levels on each system: System ORIGIN level ------ ------------ GPx 2.1B*23 MPx 2.1B*23 SPx 2.1B*23 12.1 ERROR 2 USING LABEL PRINT INTERFACE: System : All Error : Error 2 at statement 4910 in generated program. Action : Using label print interface. Program: RT.ENGDFS or rt/ENGDFS Change : 0830 CALL RNODE$+LAN$+"CMD",3,INFILE$,"","I", STR(NUMREC),STR(RECSIZ),"","";REM "CREATE" To : 0830 CALL RNODE$+LAN$+"CMD",3,INFILE$,"","I", STR(NUMREC),STR(RECSIZ), ""," "+ATTR(1,"RECORDS_ ------------------- USED")+",50,"+STR(NUM(ATTR(1,"RECORDS_USED"))+ ---------------------------------------------- 1000)+"," ;REM "CREATE" --------- NOTE: Codes changes are dashed. Notice that a space was introduced between quotes dashed in original statement. 12.2 LINE ORDER ENTRY DETAIL LINES Detail lines do not show up on Line Order Entry report. The key cannot be "numeric only" for line order entry, where the header file is a multi-keyed file. No fix available 12.3 EXECUTIVE QUERY ON LINE ORDER ENTRY REPORTS First record prints twice, the first time without the first detail SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg048 line, when running Executive Query on Line Order Entry reports. No fix available. 12.4 ORIGIN ADS PROGRAMS DO NOT EXIT THROUGH CTL-IV WHEN ONLY ONE FUNCTION WAS USED. System : SPx only Program: pgm/ENG6 Change : 0880 if L8$= " " Then GOTO 9901 To : 0880 if L8$= " " or CTL=4 Then GOTO 9901 -------- 13.0 TRANSLATION 13.1 LETTER GENERATION UPDATE TIPS In order to translate ORIGIN 2.1B to use with Letter Generation: o You must have an ORIGIN 2.1A with the following files: PGM.ENG004 - ORIGIN message file (english) PGM.ENG005 - ORIGIN screen file (english) PGM.ENG* - ORIGIN shells (english) RT.ENG* - ORIGIN run time programs (english) - and - PGM.lll004 - ORIGIN message file in foreign language PGM.lll005 - ORIGIN screen file in foreign language PGM.lll* - ORIGIN shells in foreign language RT.lll* - ORIGIN run time programs in foreign language NOTE: Where 'lll' stands for the three character foreign language code. Examples would be DEU for German or SPA for Spanish. So the file names would look like DEU004, DEU005, SPA004, SPA005, etc. DEU will be used in this document to designate the language. o Install ORIGIN 2.1B on the system, including the LANGUAGE node or directory which provides all the tools needed to translate . ORIGIN. -- * MESSAGE TRANSLATION * -- o Set the prefix to work with ORIGIN 2.1B and perform the following procedure to define a language code: 1. RUN "ORIGIN" 2. Log-on if necessary. 3. At the main ORIGIN menu, go into the Utilities menu option. 4. The choose the System Adminstraion Utilities option. Password is ADMIN. 5. Choose the Language Translation Menu option. 6. Choose Language option. 7. Choose Maintain Language option. 8. Enter the language code for your country. 9. Go to console mode. o Copy the 'DEU004' and 'DEU005' DATA files from ORIGIN 2.1A into ORIGIN 2.1B, replacing all existing files of the same name. o Compare the ORIGIN 2.1A ENG004 file with the ORIGIN 2.1B ENG004 file using the system compare utility to get a report of the SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg049 new, modified and deleted messages on ORIGIN 2.1B. ENG004 has 1800 records with only 36 new records in 2.1B so expect approximately 100 messages (new and modified) that need to be translated in order to complete the 2.1B message file. On the MPx the utility, !COMPARE, may be used to do this but on the SPx and GPx a program would need to be written. o Using the same method as above, compare the ORIGIN 2.1A ENG005 file with the ORIGIN 2.1B ENG005 file to get a report with the new, modified and deleted screens on ORIGIN 2.1B. When going from 2.1A to 2.1B, you probably will not get any. o Use the ORIGIN language translation utilities to update any messages and screens reported as changed by the compare procedure. -- * PROGRAM TRANSLATION (RUN TIME and SHELL) * -- o Use the system compare utility to compare all the programs that begin with 'ENG' located under the ORIGIN 2.1A run time and program nodes or directories with the programs of the same name in ORIGIN 2.1B. The results of this compare will determine the translation logic. - A short compare report means the program has few code changes from 2.1A to 2.1B which will allow the current translated version of this program to be used: - Copy the translated 2.1A version of this program into the ORIGIN 2.1B node or directory, renaming it to 2.1B: Ex: .ORIGIN.R21A.PGM.DEU* -> .ORIGIN.R21B.PGM.DEU* - Update this renamed program with the changed statements displayed in the compare report. - A long compare report means the program was heavily modified from 2.1A to 2.1B, so this program should be retranslated: - Copy the ORIGIN 2.1B ENG* version of the program into the same node but with the name starting with DEU*. Ex: .ORIGIN.R21B.RT.ENGNNR to .ORIGIN.R21B.RT.DEUNNR - Get a report with all the MESSAGES, everything within quotes ("), used in this program. You must then translate all these messages by editing each statement. NOTE: There are few message changes within the run time and shell programs so the same messages reported from your old DEU programs will make this process easier. -- PRIORITY ITEMS TO BE TRANSLATED -- o Message file PGM.ENG004 --> PGM.DEU004 o Report shell PGM.ENGRP7 --> PGM.DEURP7 o Run time programs RT.ENGLG1 --> RT.DEULG1 RT.ENGNNR --> RT.DEUNNR - Any program called by DEULG1 or DEUNNR beginning with U3$+"XXX" where U3$ may be ENG or DEU, for example, U3$+"XXX" really refers to ENGXXX or DEUXXX. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg050 14.0 FIXED AND VERIFIED SPR LISTING: The following is a listing of SPR's which were verified as fixed in the ORIGIN 2.1B release. _SPR#_ ___________________________DESCRIPTION___________________________ 427245 ERR=31 at 992Y in ORIDIO initializing for appl pgm with 102 items 507082 Parameter maintenance does not check for bad input at breaks. 507537 User cannot select/deselect saved option that has a numeric name 507791 ERR=0 at 4005 in IDD4AA: accessing file def maintained by another 507794 ERR=12 at 5022 in ORIBPI when a user work file is being erased. 509253 Report allows you to obtain item fm same file using 2 dif items. 512443 R21A: RG: Print sequence should allow item only once. 512457 ERR=27 at 9070 in ORIGIN displaying an INVALID MSID message. 513823 SPx ERR=41 at 1050 in ENGER2 expanding file,adding too many rec. 514430 Clear line needed in ORILG9 if bad start key entered to list msgs. 514431 ERR=26 at 910 in ORILG9 listng msgs if start/stop key is non-numeric 514437 Confusing prompt in related file update maint. regarding deletion. 514531 If condition "00" is true, update will be performed. 514674 ERR=47 at 136 in ENGTRF: if second key pressed after CTL-III:scrn prnt. 514913 Display problem if CTL-II at numeric operator in detail calculation 515055 ERR=47 at 1431 in ENGNNS when option saved with over 7 conditions. 515330 If input prompt diff than display prompt, display mask not cleared. 515314 Unable to deselect dup keys if previous key item are variable length 515316 ERR=12 at 2280 in IDD4AJ when ALT key modified to length over 80. 515632 ERR=47 at 5502 in ORIDDG during file/pgm cross-reference. 515707 R21A RG: Chk item dependence before allowing condition in item/maint 515740 ERR=14 at 1300 in ENGNNS:report output to se file uses bad name. 515770 Report Pgm. Parameter Maintenance. Verify input for break items. 515772 CTL-II and CTL-III options modifying main file breaks does not work. 515977 ERR=11 at line 7000 in Query Only. RETURN missing on Related Item. 516074 AG:ERR=41 at 6438 in FM when decimal entered at number to modify. 516081 IDD:Screen erased at CTL-III to create new dbase during copy. 516409 ERR=47 at 8756 in ENGNNT when specifying one letter as Start key. 516626 Window setup to redisplay screen and does not display data. 516633 Order Entry report prints two extra pages with headings only. 516638 Inquiry/Modify option does not work on alt keys of MK file. 516640 Start/Stop keys looking for literal "BEGINNING" and "END". 516641 Technical Documentation doesn't display item numbers in expressions. 516655 Record not having value passed fm another pgm defaults to prev. rec. 516875 If output SE file already exists, it is overwritten with no warning. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg051 517052 Report line counter is off by one. 517053 Report that specifies 'next record' does not have end trap. 517058 Automatic logoff doesn't run user logoff program-runs ORIGIN.OFF. 517066 ERR=40 at 200 in ENGINP: validatn window & file name begins w/ 'W'. 517067 ERR=47 at 1260 in ENGNNS: CTL-III pressed at report selector screen. 517068 ORIGIN allows a "+" or "-" in first position of date field. 517070 Auto CR at end of SP line wiped out first character of second line. 517071 changing proj code, copy/expand puts DC0 file in primary node. 517073 ERR=2 at 0050 in ORI555 generating application and xxxWRK file full. 517075 ERR=47 Printing label to a 'T' device. 517080 Decimal precision incorrect paging backwards in report screen disply 517084 ERR=47 at 540 in ORID03 printing "ALL" documentation. 517085 Provide a RESTART capability on reports and label prints. 517138 Chg clear screen from line 19 to 20. 517139 OE Report:pg line counter wrong when last rec falls on last pg . line. 517220 R21A: path at line 350 hardcoded, causes problems for some users. 517380 Error 26 at 6070 in Screen overlay program. 517420 Wrong msg displayed when linked to IDD and input not same type:SvsN. 517426 Runtime calculation allows NEW EXPRESSIONS name to be NEW EXPRESSION 517429 Can't exit input prompt if you decide not to enter NEW EXPRESSION. . 517721 A/P: No error msg when can't enter vendor for range of reports. 517871 SPx-Error 26 line 7106 in ORITCX using Term-Editor Key Association. 518219 IDD:Msg "File can't be found in current prefix, CR to continue". 518292 IDD:Msg "Illegal file name displayed when file name I13. entered. 518525 SPx:ERR=12 at 8120 in ENGNNR trying to initialize .SUMMARY file. 518526 ERR=47 at 736 in ORINTL when expression in total starts at POS 128. 518705 R21A:Report cannot output 132 column format to serial file. 518728 Msg: 'User Incorrectly Logged On' displayed on SPx. 519183 RG: 'DEVICE CAN'T BE OPENED' Err. specifying '0' for term. only. Rpt. 519240 RSC: Option to choose menu driver to run at end of AG/RG for menus. 519380 RG: Setting seq. pri. to 0 on item fails. Item still displays. 519593 ERR=21 at 9924 at ENG6 generating pgm with associated OE program. 519622 4312 loses function keys after exiting and returning to ORIGIN. 519867 No prompt GRAPH INTERFACE first try, !ERR 38 on second try. 520191 On terminals >99 receive Err=47 @ 4920 in Generated Reports. 520253 Rpt. using LABEL PRINTING interface says pgm. complete but more left. 520276 Num. filenames in IDD can't be used to INIT. REPORT/APPL. fm files 520288 MPx/SPx !ERR 26 when selecting saved options. 521509 Cannot delete IDDFILE.bak from IDD. Must remove from BASIC. 521564 Cond. test for rltd file reads (read if entered option) not working. 521568 Implement control over usage rights for pgm. & data files. 521569 Variables in IOL do not match those in RG pgm. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg052 521571 Err=47 at line 1900 in PGM.ORING9 building rpt. from FM pgm. 521578 RSC: Allow class specification for all output from ORIGIN. 522207 Date in Start Key confuses display & prevents CTL-III from working. 522214 Err=2 during sort of Rpt. while another user is entering records. 522875 Error Messages Report not reporting all error messages in file. 522902 Small case 'y' entered at prompt is accepted, but not acted upon. 522913 In IDD, F/R layouts, option '11. Examine File' not working. 522981 Sort files ORI+FID(0) should be deleted after rpt is run. 522982 Err=1 during generation of large executive query @ 900. 523619 Key size & record size information prints out twice on report. 523893 No input validation & missing msg. indicating '?' to display. 524272 STANDARD OPT. screen: 'CTL-I' to compare items' clears entered info. 524283 USER MAINT.: unable to change existing CONSOLE MODE from No to Yes. 524337 is inoperable for ENTER NEW RECORD/QUERY by E.G. after pgm. gen. 524429 Err=47 while doing print screen in Terminal Types Maintenance. 524467 Unable to search for a reference name or expression for a derived item 524489 Attempt to use CTL-II while viewing IMPACT REPORT; terminal hung. 524509 2.1B: Err=41 in ORIWPS changing the loc. of Primary Key in Sort Def. 524510 2.1B: trying to maintain Primary key, pad lock does not work on 4314. 524511 2.1B: Modifying SORT file name does not retain data. 524512 2.1B: IOLIST does not match variables in ITEM MAINTENANCE. 524513 Mod. Loc. of Prim. Key & drops to next input instead of data correct. 524514 Related files cleared w/main file in Batch update process.Destructive. 524516 Missing relationship does not display data in Inquiry / Modify . mode. 524517 2.1B: Item still dependent even if exp. is changed & pgm regenerated. 524519 2.1B: Err=41 @ 27 in ORINRE initializing Rpt from Application Pgm. 524522 2.1B: Err=0 @ 7925 in Generated OE Rpt trying to read channel 0. 524524 2.1B: Err=11 @ 5010 in IDD4AC printing TECH DOC in AG work area. 524533 2.1B: Err=14 @ 6090 in ORIDIO generating OE Application program. 524534 Keyboard locked in pad lock mode when generated DSS. 524535 TECH DOC print hangs after #199 item prints in rpt. pgm work area. 524538 Can't define new file FM the IDD or FM ADS. 524542 Statement 8010 gets an error 12 during UPDATE. 524543 Chng Ln 400 to 0400 if I=0 GOTO 9000-msg inconsistent W/existing opt. 524544 Remove statement 1450: 1450 ESCAPE. 524577 Item TIM=24 incorrect, 7115 tries to use FNT2424 which doesn't exist. 524578 Expression accepted but ret. msg. 'AN ERR 47 MAY OCCUR ON STMT 7112..' 524584 Attempting to initialize for a new report, Err=47 @ 1790, ORIRTI. 524971 Err=47 @ 3020 while building applic. from a VIEW. (using index file). 524974 file maint. from IDD screen entry rejects file types SORT & INDEXED. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg053 524993 Mis-matched '('s causing problems while conditioning in gen. rpt. pgm. 525056 App. pgm. from a direct file without terminators does not take data. 525110 When dt4314 in 132 col. mode and error occurs, term. remains in 132 m. 525117 Gen. rpt. pgm. output to both pntrs. & terms. with total lines def. 525123 Pgm. ORIEXP does not use the '$' mask when validating numeric masking. 525124 Rpt: MK files don't print 1st rec. of file if start key is actual key. 525128 Some programs missing SETESC and/or SETERR please enhance programs. 525134 Screen not displaying upon entering of a generated query -only pgm. 525136 RPG init from ASG/doc lose defined conditions. 525137 ASG/DSS Invalid expression when maintaining file related item's cond. 525163 International letter generation problems 525183 Err=46 @ 3620 ENGDHU running graph interface from ORIGIN generated Rpt 525190 2.1B: Error 47 in synonym from relationship files. 525526 After changing type parm. for bin. type ORIGIN not updating correctly. 525528 IDD copying DB keeps going unsuccessfully after COPY & EXPAND executed 525537 Item/display lookup info - either not displayed or displayed twice. 525552 DSS gen. rpts. drop with err=41 when no executive items are selected. 525613 IDD, attempt to use CTL-II to the file type causes file corruption. 525677 ORIGIN 2.1B must work without public key for DSS. 525669 IDD: infinite loop trying to create derived item 255 on current D.B. 525787 Run UPDATE (to 2.1B) with FREEFORM TEXT undefined results in Err=11. 525921 Current pgm. & Data node not getting updated at user log-on. 525959 DSS: Generated report based on INDEXED files got invalid stmt 1020. 526244 A generated ORIGIN to SPREADSHEET pgm receives err=12 @ line 4945. 526262 Generated report may run into !ERR=47 using EXECUTIVE QUERY opts. 526263 DISPLAY DOC: rpts: several blank pgs with only headers are printing. 526265 Running executive query reports the screen gets messed up after 1st. 526302 Alpha lookup in generated FM program does not always work properly. 526386 ORIGIN -> GRAPH: unable to plot using last entry in plotters file. 526398 Multi-screen App. pgms. do not display entered info on 2nd screen. 526772 Rpt. pgm. gen.: Batch file update - UPD routine falls through. 526901 !ERR=45 @ 9943 in Gen. Rpt. Pgm. after deleting EXEC QUERY options. 527184 DSS: LOE rpt based on files named with less than 6 chr get problems. 527198 The IDDF01 file is sometimes closed; thus, 9920 does not take place. SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg054 527268 File lookup on Multi-Key files does not return requested key. 527480 SUMMARY file for DSS report is created w/o GROWTH Parm. get err=2. 527481 The ORIGIN 'FILE PREFIX SUFFIX' is not working properly. ****** IOLIST generation problem. ****** Updated ORIGIN level message (ADS, DSS, ENG004). ****** NAIT recomendations to fix three problems which they fixed. ****** Missing 'NEXT T' Directive at the Statement 4005 (ENGDIR, ENGGRF). ****** HOLLAND reported ERR=47 @ 6490 while working in Dutch (ORIAV3). ****** Excluded some non-2.1A files from the UPDATE filelist (UPDATE21A). ORIGINATOR: Elaine Titus SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB027 Pg055 FIB 00028 11/30/90 *** Known ORIGIN 2.1B Problems *** Type: Informational Purpose This document will list the currently known problems with ORIGIN 2.1B and any possible work-arounds. Symptom ORIGIN generated reports do not print all the data selected. Cause Although no errors occur, the data in subscripted fields do not print on the generated report output (ie, screen or printer) because the variables used by ORIGIN for the subscripted fields are not dimensioned properly at lines 990 and 9101 of the generated report. Solution Currently there is no fix for this problem. The only solution right now is to generate the reports and modify lines 990 and 1901 to correctly dimension the variables used for subscripted fields. Symptom Error 12's trying to load ORIGIN generated reports and applications in BASIC even though the prefix is set correctly (Gpx System). Cause The problem occurs because the data and program directory at the initial ORIGIN log-on screen does not have a '/' at the end. Solution Re-enter the data and program directory at the ORIGIN log-on and enter the '/' at the end of the directory names specified. Symptom Cannot modify the query priorities for an ORIGIN generated report. Cause Regression from 2.1A (unknown cause right now). Solution Currently there is no workaround for this problem. ORIGINATOR: Jackie Shea SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB028 Pg001 FIB 00029 11/30/90 *** ORIGIN 2.1B*23 Reports don't Print with num Start/Stop Keys *** Type: Problem Purpose ORIGIN 2.1B*23 generated reports do not print any data if an alternate NUMERIC print sequence is used in conjunction with a NUMERIC start key AND stop key. Symptom The report will appear to be working by SORTING through the file, but no data will print. The report selector will redisplay and the message. 'Program Complete to Continue' will display at the bottom of the screen. Cause The problem occurs because ORIGIN doesn't know it is a Numeric field that is being used for the Start or Stop key. Solution The ORIGIN report generator shell must be modified to include the following lines of code. All the lines are new with the exception of lines 224 and 651. These two lines have been modified. In addition, the program, RT.ENGTRM, must also be modified. **NOTE** On SPx systems make all the code changes for PGM.ENGRP7 EXCEPT line 224. Do NOT include this line when making code modifications. Load ".ORIGIN.R21B.PGM.ENGRP7" 0224 O0$=O0$+CHAR(127)+$CECDCACACFC7D0C6E2D9C3BFC4C0C0BFC1$ -- 0651 PK1$=K1$; GOSUB 10000;K1$=PK1$; IF K1$=$00$ THEN READ(6,KEY="",DOM=670); ------------------------------- 0651:GOTO 670 ELSE IF D2$="D" THEN EXTRACT(6,KEY=NOT(K1$(1,POS($00$=K1$+$00$) 0651:-1)),DOM=670);GOTO 670 ELSE EXTRACT(6,KEY=K1$(1,POS($00$=K1$+$00$)-1),DO 0651:M=670);GOTO 670 0900 PK1$=Z3$; GOSUB 10000; Z3$=PK1$ 10000 REM 10000 10010 IF D1$<>"DELETE" THEN RETURN 10020 IF D6$="" OR PK1$=$00$ OR PK1$=$FF$ OR POS($FF$<>PK1$)=0 OR POS($00$<>PK 10020:1$)=0 RETURN 10030 FOR U=1 TO LEN(D6$) STEP 6 10040 U2=NUM(D6$(U,3)); GOSUB 7000; IF M2$="N" THEN EXITTO 10100 10050 NEXT U 10060 RETURN 10100 REM "THE START KEY HAS A NUMERIC IN IT! 10110 NK1$="",SKEYPTR=1 10120 FOR U=1 TO LEN(D6$) STEP 6 10130 U2=NUM(D6$(U,3)); GOSUB 7000; IF M2$<>"N" THEN GOTO 10200 10140 IF XDEC$="." THEN YDEC$="," ELSE YDEC$="." 10145 XK1$=PK1$(SKEYPTR,K1) 10150 P=POS(YDEC$=XK1$); IF P<>0 THEN XK1$=XK1$(1,P-1)+XK1$(P+1); GOTO 10150 10151 P=POS("-"=XK1$); IF P>1 THEN XK1$=XK1$(P,1)+XK1$(1,P-1)+XK1$(P+1); GOTO 10151:10151 10152 P=POS("+"=XK1$); IF P>1 THEN XK1$=XK1$(P,1)+XK1$(1,P-1)+XK1$(P+1); GOTO 10152:10152 10155 P=NUM(XK1$),XK1$=STR(P:XMSK$) 10160 IF P<0 THEN XK1$="0"+NOT(XK1$) ELSE XK1$="1"+XK1$ SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB029 Pg001 10165 NK1$=NK1$+XK1$; GOTO 10210 10200 NK1$=NK1$+PK1$(SKEYPTR,K1) 10210 SKEYPTR=SKEYPTR+K1 10220 NEXT U 10230 PK1$=NK1$ 10240 RETURN 16000 END In order for the changes above to take effect, the ORIGIN report must be re-generated. Load ".ORIGIN.R21B.RT.ENGTRM" 0046 IF Q1$="!" THEN FUNKEYS$="NO", Q1$=""; GOTO 60; REM "DETERMINE TERMINAL. ------- 0046:DON'T SET KEYS ORIGINATOR: Jackie Shea SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB029 Pg002 FIB 00030 02/06/91 *** 2.1B*23 - Erroneous Prompt after Start/Stop Key Used [ WPSF 666 ] *** MAI ORIGIN 2.1B*23 ERRONEOUS INPUT PROMPT AFTER 666 ENTERING START/STOP KEYS FOR REPORT JACKIE SHEA 1/91 CODE '9' TYPE: Problem PURPOSE: Code modifications need to be made to RT.ENGNNT to correct a problem where an erroneous input prompt appears after entering a start or stop key for report. SYMPTOM: After entering a start and/or stop key for SORT and REPORT, an input fill prompt (ie, '.........') will display, and wait for an input. The normal message at the bottom, ' to Continue, Enter Name or Number to Modify, CTL IV to End', is displayed twice. SOLUTION: Make the following code modifications to RT.ENGNNT. These code changes are valid for GPx and SPx system as well. Load ".ORIGIN.R21A.RT.ENGNNT" 8720 IF LEN(Z3$)=0 THEN Z3$=Z1$;IF NUM(C1$)=2 THEN GOTO 8710 8720:ELSE GOTO 8749 8856 IF POS(I$(1,SGN(LEN(I$)))="NF")<>0 THEN IF X4$="" THEN 8856:C1$="1",X4$=CHAR(0) ELSE X4$=STR(NUM(X4$,ERR=8857):X9$) 8865 IF POS(I$(1,1)="NFX")>0 THEN GOTO 8870; REM LET X4$=STR(NUM 8865: (PREX4$);X9$; GOTO 8870 The changes above are made to a CALLed program in ORIGIN. Consequently, ORIGIN generated reports do NOT have to be regenerated in order for the changes to take effect. ORIGINATOR: Jackie Shea SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB030 Pg001 FIB 00031 04/03/91 *** Err 47 using '?' in IDD Maintenance - ORIGIN 2.1B [ WPSF 620 A1 ] *** ORIGIN 2.1B - GPx SERIES 40 620 ERROR 47 USING '?' IN IDD MAINTENANCE JACKIE SHEA 3/91 ADDENDUM-1 TYPE: Problem SYMPTOM: Entering a '?' in file/record layout maintenance on ORIGIN 2.1B using FACTS data dictionary layouts on a GPx system results in an error 47. CAUSE: The error occurs because the ORIGIN 2.1B level on the GPx system for 1.0A, 1.0B and 1.0C operating systems is a beta version (2.1B*10). SOLUTION: Upgrade to operating system level 1.0D or higher which contains the released version of ORIGIN 2.1B*23. ORIGINATOR: Jackie Shea SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB031 Pg001 FIB 00032 05/15/91 *** Err 41 using IDD examine at 2.1B*23 [ WPSF 713 ] *** Error 41 using IDD Examine Jackie Shea in ORIGIN 2.1B*23 Type: Problem Purpose: Code changes to correct error 41 at line 1190 in PGM.IDD4AM Symptom: An error 41 occurs after selecting the option 'Examine' in the Integrated Data Dictionary under File/Record Layout Maintenance. Solution: The error occurs because an item reference name is 15 characters in length. The maximum length of a reference name is 15 but the ORIGIN program is not allowing for that length. FIX: Program: .ORIGIN.R21B.PGM.IDD4AM 1190 I$=K$(2,I-1),I$=I$+B$(1,15-LEN(I$)),K$=K$(I+1) --- The code modification above is applicable to the SPx and GPx systems also. SPx program: /origin/r21b/pgm/IDD4AM SPx program: /usr/origin/r21b/pgm/IDD4AM ORIGINATOR: Jackie Shea SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB032 Pg001 FIB 00033 06/27/91 *** Application Generator Shell Change *** ************************* * P R E L I M I N A R Y * ************************* ORIGIN 2.1B*23 Jackie Shea Application Generator Shell Change Type: Problem Purpose Provide a code modification to the application generator shell program to prevent incorrect exiting from 'INQUIRY AND MODIFY' or 'QUERY BY EXAMPLE'. Symptom Application generated program exits back to main menu or calling program when 'INQUIRY AND MODIFY' or 'QUERY BY EXAMPLE' option is selected. No BASIC error occurs. Cause This problem occurs only when a user first enters 'INQUIRY AND MODIFY' or 'QUERY BY EXAMPLE' mode and presses CTL IV immediately and then attempts to reselect 'INQUIRY AND MODIFY' or 'QUERY BY EXAMPLE'. This is only an ORIGIN 2.1B problem. Applications work correctly on the ORIGIN 2.1A version. Solution To prevent the incorrect exit routine from an ORIGIN application generated program, make the following modification: PROGRAM: .ORIGIN.R21B.PGM.ENG6 MPx /origin/r21b/pgm/ENG6 SPx /usr/origin/r21b/pgm/ENG6 GPx OLD: 0880 IF L8$=" " OR CTL=4 THEN GOTO 9901 NEW: 0880 IF L8$=" " THEN GOTO 9901 The code modification above is for the application generator shell program, NOT the generated program. All new applications created will have the new code changes. To have existing programs take advantage of the code modifications, the application programs need to be re-generated in the Application Generator. Applications do NOT have to be re-created from the drawing board, just re-generated from the work area. ORIGINATOR: Jackie Shea SOFTWARE-BASIC FOUR-ORIGIN--------------------------FIB033 Pg001