========================================================================= G C O S 8 R U N - T I M E E X P R E S S v4.0.05 Windows NT/2000/XP RELEASE ========================================================================= RELEASE NOTES ============= TABLE OF CONTENTS ================= INTRODUCTION INSTALLATION INTEGRATION DATABASE SERVER TP8 BATCH COMMANDS ERRORS FIXED & IMPROVEMENTS IN THIS RELEASE TIPS & HINTS KNOWN ERRORS KNOWN LIMITATIONS MANUAL INSTALLATION PROBLEM REPORTING INTRODUCTION ============ This version of GCOS8 Run-time Express (G8RE) is the Initial Release supporting the Micro Focus Application Server. It is issued on CD-ROM (diskettes available upon request), with limited new documentation. G8RE includes Micro Focus Application (a run-time version of Mainframe Express, named AS) and a run-time version of the GCOS8 Mainframe Express (MFE8), which may be used to execute GCOS8 applications prepared with MFE8. Most of the features of G8RE are documented in MFE8, MFE and AS documentation set, however the G8RE Release Notes and Update Notes provides details on G8RE specific features and differences from the MFE8 environment. INSTALLATION ============ Like MFE8, the installation procedure is separated into a Server and a Workstation installation. o The Server installation is used to setup shared directories and a database Server, to support a number of Workstation users. o The Workstation installation is used to setup a single Workstation for testing of GCOS8 Batch or TP applications. Note: Although the shared directories G8RBGDIR, G8RBDDIR, G8RBFDIR and G8RBDIR are similar to MFE8, they CANNOT be installed into the same directories as MFE8. CD-ROM ------ The G8RE CD-ROM is structured as follows: G8RENOTE.TXT - release notes (this document) G8RE\DISK1\SETUP.EXE - start installation of RHE8 (including lastest update) G8REUPD.TXT - update notes G8REUP\DISK1\SETUP.EXE - start installation of RHE8 update WEBSYNC - Service-, Add- and Fix-packs for Application Server SERVER Installation ------------------- The Server installation must be made first, and is normally only done once. The installation involves the following steps: - install Application Server software - update AS with websync packs (optional) - install G8RE software (includes latest update) The Server installation should be performed on a LAN Server or a PC Workstation dedicated as Server for the G8RE environment. Application Server Installation ------------------------------- The Application Server installation procedure is quite simple. o Directory: When prompted select a directory for installation of software, ex. \Program Files\Micro Focus\Application Server. o License info: When prompted for license information, you should enter a serial number provided on the software package. Next you need may optionally update Application Server with Websync service and fix packs as provided on this CD-ROM. Application Server rely on registry settings setup during installation. G8RE Installation ----------------- The G8RE installation procedure is quite simple and similar to installation procedure for MFE8. o Installation type: Select 'Server Installation'. o Global Directory: Target directory for Global files, ex. D:\G8REG. o Program Directory: Target directory for Program files, ex. D:\G8REP. o Forms Directory: Target directory for Forms files, ex. D:\G8REF. o Database Directory: Target directory for Database files, ex. D:\G8RED. o Select Components: 'Basic' includes support for TPFF. Select other components as required. o Folders: Icons are grouped under a default folder 'GCOS8 Run-time Express'. The default folder name can be changed as required. Following entries area created under the default folder: 'Books' will contain: Getting Started (Help file) 'Notes' will contain: Release Notes (Notepad) Update Notes (Notepad) Open-Client-Toolkit (Notepad) The G8RE software will now be installed into the specified target directories. Note: Before proceeding with Workstation installation, make sure the G8RE Global, Program, Forms and Database directories can be accessed (shared) from PC Workstations. WORKSTATION Installation ------------------------ The Workstation installation must be made next. This installation must be repeated for each PC Workstation where you want to use G8RE. The very first Workstation Installation will perform some additional setup of the Server directories. The installation involves the following steps: - install Application Server software - update AS with websync packs (optional) - install G8RE software (includes latest update) - customize/integrate G8RE with Application Server Application Server Installation ------------------------------- The Application Server installation procedure is quite simple. o Directory: When prompted select a directory for installation of software, ex. \Program Files\Micro Focus\Application Server. o License info: When prompted for license information, you should enter a serial number provided on the software package. Next you need may optionally update Application Server with Websync service and fix packs as provided on this CD-ROM. Application Server rely on registry settings setup during installation. G8RE Installation ----------------- The G8RE installation procedure is quite simple and similar to installation procedure for G8RE. o Installation type: Select 'Workstation Installation'. o License info: When prompted for license information, you should enter a serial number indicated on the CD-ROM, ex. G8RE/BTDM/0201. Your name and company is setup with Windows defaults. o Local Directory: Target directory for local non-shared files, ex. C:\G8REL. o Global Directory: Reference directory for Global files, ex. F:\G8REG (network share = F:\ = D:\ on Server PC). o Program Directory: Reference directory for Program files, ex. F:\G8REP. o Forms Directory: Reference directory for Forms files, ex. F:\G8REF. o Database Directory: Reference directory for Database files, ex. F:\G8RED. o Select Components: 'Basic' includes support for TPFF. Select other components as required. o Folders: Icons are grouped under a default folder 'GCOS8 Rehosting Express'. The default folder name can be changed as required. Following entries area created under the default folder: 'Books' will contain: Getting Started (Help file) 'Notes' will contain: Release Notes (Notepad) Update Notes (Notepad) Open-Client-Toolkit (Notepad) 'FS Administration Tools' will contain: Run FS2 RGLOBAL Server FS Backup Database FS Restore Database Initialize FS2 RGLOBAL Server FS Q2UT Database Utility 'DB Administration Tools' will contain: IIDS Database Utility Unload Database Utility Load Database Utility Others icons are: Configuration GCOS8 Customization G8RE Command Prompt Run TP8 Run TP8 Client The G8RE software will now be installed into the specified target directory, and references setup for the shared directories. Upon completion of installation, you are adviced to run two setup steps: Launch CCI Configuration: This is used to setup and configure the CCI communication software. You are prompted for the name of the CCITCP2 Registration Server location (usually the name of the server). Launch GCOS8 Customization: This is used to customize, setup and integrate G8RE with Application Server. CCI Registration Server ----------------------- The CCI Registration Server is used to facilitate TCP/IP communication between CCI Clients (TP8 and Batch) and CCI Servers (Database Server). The Registration Server is normally started on the PC server, where you also have your Database Server, however, it could be started on any PC Workstation also. You need only ONE Registration server. The Registration Server may be installed as a Windows Service. This need only be done once, ex. \CCITCP2 -i or \CCITCP2 -c where path = path of Application Server -c option will show a debug console. You can remove the Regsitration Server as follows: \CCITCP2 -u Note: The Registration Server must be installed BEFORE you attempt to access a Database Server, otherwise this will fail. =========== INTEGRATION =========== The G8RE environment is now fully operational, however, none of your GCOS8 applications components are available within the environment. Your next step is thus to integrate your GCOS8 application components and parts of your configuration from the G8RE environment. Database integration -------------------- The $g8rbddir\DBMS.CFG file must be amended with information from your MFE8 environment. This step must be done manually, i.e. copying from $g8wbddir\DBMS.CFG and pasting into $g8rbddir\DBMS.CFG. The Schema and Subschema file can either be used directly from your MFE8 environment, or copied into $g8rbddir. MFE8 has a Move Schema and Move Subschema function to facilitate this. Note: Existing databases may be unloaded with nnHDBU, either from GCOS8 or MFE8 environment, or simply copied from the MFE8 environment (copy the 99xxx.DAT files). Schema ------ The Schema configuration is slightly different for G8RE, due to the use of a Database Server. Following example illustrate a schema configuration (must be on one line, split into multiple lines only for illustration): ; Number Location Location Location [Perm Concurrent Protect] ; (1-99) Schema client server [R/W OFF/ON/FS2 OFF/ON] [SCHEMA-SECTION] CLASS 26 CURRENT or D:\G8WBD $$RGLOBAL\$G8RBDDIR\RDBMS -S $$RGLOBAL\D:\G8RED\RDBMS W FS2 ON Location Schema: Specifies the path for the schema files. 'CURRENT' means $g8rbddir (within G8RE). To access schema files directly within MFE8 you specify the path = $g8wbddir, ex. D:\MFE8D. Location Client: When database is accessed directly by a client application, this path is used. Direct access is done by DB Backup, DB Restore, Q2UT, DB Load and DB Unload utilities. Location Server: When database is accessed indirectly by a client, i.e. via Database Server, this path is used. Indirect access is done by Batch, TP and IIDS Utility. The $$RGLOBAL\ setting designate use of a File Share 2 Server name RGLOBAL. The 'D:\G8RED\RDBMS' setting designate where File Share 2 will access the files LOCALLY on the Server PC (not the same as $g8rbddir\rdbms). Permission: When Write permission is specified for a schema, you must enable concurrency and protection. For Read permission you can leave these OFF. Concurrency: FS2 setting designate the database will be accessed via File Share 2 with concurrency control (similar to MODE-4 in TP8). Protect: ON setting designate the database will be accessed with Rollback protection (similar to ABORT/ROLLBACK/). Subschema --------- The Subschema configuration is similar for G8RE and MFE8. ; Short Location Auto ; name Subschema generated [SUBSCHEMA-SECTION] CLASS : CLASS CURRENT ; example SS-CLASS : 26SCHS CURRENT -AUTO ; example Defaults -------- The Defaults configuration may be slightly different for G8RE, due to the use of a Database Server. [DEFAULT-SECTION] TP-WAIT-TIME : 30 ; Concurrency wait time in secs This setting specify the time-out before a transaction is aborted (similar to deadlock). Note: TP transactions can be restarted (see TP8.CFG). BATCH-WAIT-TIME : 180 ; Concurrency wait time in secs This setting specify the time-out before a batch program is aborted (similar to deadlock). Note: Concurrency control is done at record level and reservation is exclusive for both read and write. Batch programs should take frequent checkpoints, if executed concurrently with TP. DYNAMIC-DEBUG : OFF ; Dynamic Debug Mode ON/OFF (Drop-in) The Dynamic Debugger (IIDS drop-in) should be OFF, so DB exceptions are passed directly to the application. CONCURRENCY-CONTROL : OFF ; DB Concurrency Control OFF/ON/FS2 ; ON - Standard Record Locking ; FS2 - Use File Share 2 INTEGRITY-CONTROL : OFF ; Transaction logging OFF/ON ; ON - Rollback logging The CONCURRENCY-CONTROL and INTEGRITY-CONTROL settings, which specify the default if schema does not have explicit Concurrency and Protect settings. We recommend specifying Concurrency and Protec explicitly for each schema. GCOS8-DBK-ALLOCATION : OFF ; OFF/ON GCOS8 Compatible DBK allocation You may use GCOS8-DBK-ALLOCATION : ON to get a more GCOS8 compatible IDS-II space allocation. When enabled, new DBKs are assigned almost like on GCOS8, i.e. CALC-hashing, Set-clustering, and storage may be refused if ALLOCATE n DB_KEYS for a given area is exhausted. When disabled, new DBKs are assigned at the next higher DBK, and storage is only refused if you run out of disk space. Note: GCOS8-DBK-ALLOCATION is considered ONLY at the time when you initialize the database with Q2UT Utility (complete initialize). Note: When enabled, concurrency locking is more severe, since a number of reads may be required to determine assignment of DBK. Backup-set ---------- The Backup-set configuration is similar for G8RE and MFE8. ;Backup-Set No. Location [Compression Method ] ; (1-99) LOCAL|SCHEMA|path -PAC|-ZIP SPEED|SIZE [BACKUP-SECTION] EXAMPLE : 1 SCHEMA -ZIP; example Location: SCHEMA designate $g8rbddir\dbms (shared). LOCAL designate $g8rbldir\dbms (non-shared). Path could specify a backup-set within MFE8 environment, ex. D:\MFE8D\DBMS. TP8 Integration --------------- The $g8rbgdir\TP8.CFG file must be amended with information from your MFE8 environment. This step must be done manually, i.e. copying from $g8wbgdir\TP8.CFG and pasting into $g8rbgdir\TP8.CFG. The TP8 configuration is similar for G8RE and MFE8, except you may want to use some of the optimization features. [CREATE_TP8_EXTENSION] TPR_POOL : 5 RANDOM ; # TPRs (0-25) [FIFO|RANDOM] May be used to cache TPRs and obtain RANDOM use/reuse of TPRs (similar to real TP8 execution). MAXIMUM_STACK : 100 ; Maximum modules within TPR Whenever a TPR is cancelled from memory (fresh copy), MFE8 has to cancel all modules called by the TPR also to obtain similar behavior as TP8 (RHE8 use dynamic linking). G8RE will keep track of modules called directly or indirectly through a stack. The maximum setting must be sufficient to cope with the maximum number of modules called from an application TPR (application modules only). PROGRAM_CACHE : 25 ; 0-100 program entries May be used to optimize execution, by caching the most used TPRs and or modules in memory. STATISTICS : 500 ; TPR/Module usage entries G8RE will collect statistics for TPR and module use. The maximum setting must be sufficient to cope with the maximum number of TPR and modules within your application. If overflow occur, this is indicated in the Journal and additional statistics are lost. MAXIMUM_RESTART : 3 ; Maximum deadlock restarts May be used to control how many times a transaction will be restarted in case of concurrency deadlock. A restart will be indicated in a status message on the TP8 screen. [CREATE_TPR] ;TPR or pathname Loaded as resident TPRA MODULEA May be used to load high use TPRs and/or modules resident in memory. The $RDY command will trigger execution of your ready TPRs. For G8RE (and MFE8) use of ready TPRs are optional. For G8RE it is not recommended to use ready TPRs (leave out $RDY), since this would force all IDS-II databases to be opened during TP startup. Without ready TPRs, database are only opened when required, i.e. first time a schema is used by the application. Defaults integration -------------------- The $g8rbgdir\G8WB.CFG file must be amended with information from your MFE8 environment. This step must be done manually, i.e. copying from $g8wbgdir\G8WB.CFG and pasting into $g8rbgdir\G8WB.CFG. The Defaults configuration is similar for G8RE and MFE8. Some options may be changed to suit a run-time environment, and mixture of Global and Local configuration may be changed also. Note: Local Defaults configuration file is $g8wbldir\G8WB.CFG. [G8WB-DEFAULTS] ; Defaults configuration SYSTEM-DATE : CURRENT ; CURRENT or YYMMDD SYSTEM-DAY : CURRENT ; CURRENT or YYDDD SYSTEM-TIME : CURRENT ; CURRENT or HHMMSSHS May be used to 'fix' specific data/time for testing. LOGON-MESSAGE : STRT ; Automatic Log-on message for TP May used to automatically execute a transaction at logon. MESSAGE-ID : LAZY ; Default Message-id/Command for TP May used to automatically execute a specific transaction whenever an empty transmit is given. HELLO-MESSAGE : "THIS IS MY OWN TP HELLO" May be used to change TP HELLO message. SPAWN-AUTO-RUN : ON ; Process Spawn automatically OFF/ON May be used to automatically execute spawned transaction(s), when the current transaction terminate. When OFF, spawned transactions must be executed manually via TP-Escape menu. G8RB-ESC-MENU : REDUCED ; Run-Time ESC-menu FULL/REDUCED May be used to limit the functionality of the TP-Escape menu. [G8WB-TRACE] ; Trace configuration TP-TX-SEQUENCE : OFF ; Trace TX/TPR state Normally OFF to limit the amount of information in the TP Journal. TP-EXEC-CALL : OFF ; Trace TP Interface/procedure calls Normally OFF to limit the amount of information in the TP Journal. TP-COMM-DETAIL : OFF ; Trace SEND/RECEIVE details Normally OFF to limit the amount of information in the TP Journal. TP-TPR-EXECUTE : ON ; OFF(default)/ON Normally ON, so user can see 'progress' in a status message on the TP8 screen. TP-RESPONSE-TIME : PROFILE ; OFF(default)/ON/PROFILE May be used to obtain response-time (and other statistics) in the TP Journal. OFF - No response time statistics given TPR/Module use and IDS-II statistics given at termination ON - Response time summary statistics given at termination TPR/Module use and IDS-II statistics given at termination PROFILE - Like ON, however Response time, TPR/Module use and IDS-II statistics are given both after each TX or Phase, and summary at termination Note: Response time statistics are naturally not comparable to real TP8 response times, however it does give you an idea of performance variances within or between transactions. Note: IDS-II statistics are comparable to GCOS8 for Logical (DML) operations, whereas Physical statistics are not comparable to GCOS8. However it does give you an idea of I/O performance variances within or between transactions. TP-GLOBAL-JOURNAL : ON ; OFF(default)/ON May be used to consolidated all TP Journals. When ON, each TP Journal will be appended to a Global Journal file $g8rbgdir\JOURNAL.ddd, where ddd = day number. BATCH-EXEC-CALL : OFF ; Trace Interface/procedure calls Normally OFF to limit the amount of information in the TP Journal. BATCH-GLOBAL-LOG : ON ; OFF(default)/ON May be used to consolidated all Batch Logs. When ON, each Batch Log will be appended to a Global Log file $g8rbgdir\BATCH.ddd, where ddd = day number. Note: G8RE Utilities like DB Backup etc. will by default produce output on $g8rbldir\BATCH.LOG (like batch application programs). Environment integration ----------------------- The $g8rbgdir\ENV.CFG file must be amended with information from your MFE8 environment. This step must be done manually, i.e. copying from $g8wbgdir\ENV.CFG and pasting into $g8rbgdir\ENV.CFG. Note: If you have made no changes to ENV.CFG, no integration is required. Forms Integration ----------------- G8RE will only install an empty Forms directory structure, and since Forms directory is only used by some Forms software, you may not be required to do any integration. TPFF ---- Forms are embedded in TPR and Forms directory not used during execution. FORMAT ------ Forms are embedded in TPR and Forms directory not used during execution. SOLD ---- Forms are embedded in TPR and Forms directory not used during execution. PILSPRAAK --------- Forms are embedded in TPR and Forms directory not used during execution. DIMS8 ----- Forms are loaded from Forms directory during execution. Either copy the entire $g8wbfdir\FORMS structure to $g8rbfdir\FORMS, or change G8RBFDIR setting to point to G8WBFDIR (during installation of G8RE Workstation). TSM8 ---- Forms are loaded from Forms directory during execution. Either copy the entire $g8wbfdir\FORMS structure to $g8rbfdir\FORMS, or change G8RBFDIR setting to point to G8WBFDIR (during installation of G8RE Workstation). SOLD+ ----- Forms are loaded from Forms directory during execution. Either copy the entire $g8wbfdir\FORMS structure to $g8rbfdir\FORMS, or change G8RBFDIR setting to point to G8WBFDIR (during installation of G8RE Workstation). Application integration ----------------------- The application programs checked and compiled in MFE8 environment must be made available within the G8RE environment, so you are able to execute the entire application system, as if it was running on GCOS8. COBDIR ------ Like MFE8, G8RE use COBDIR setting to dynamically search through multiple directories for application programs. Such programs may be either INT or GNT format, however GNT (compiled) is recommended for best performance. COBDIR settings may be placed in the G8REENV.CFG file, which is processed during startup of any RHE8 operation. The G8REENV.CFG is located using following technique: $g8reenv\g8reenv.cfg (if G8REENV setting is present) \g8reenv.cfg $g8rbldir\g8reenv.cfg $g8rbgdir\g8reenv.cfg no g8reenv.cfg used The G8REENV.CFG is a simple text file with one or more environment settings, ex. AP1=F:\APP1 AP1=F:\APP2 SUB=F:\SUB DBPROC=F:\DBPROC COBDIR=%SUB%;%DBPROC%;%COBDIR% COBDIR=%AP1%;%AP2%;%COBDIR% Note: SET is not specified. Existing environment variables must be expanded using %symbol% technique. Libraries --------- An alternative technique is to use application libraries, and allocate these libraries through Environment configuration ($g8rbgdir\ENV.CFG). Although library technique is faster than directory searching through COBDIR, we do not recommend use of libraries because libraries cannot be updated if they are busy, i.e. some G8RE user is executing somewhere. DATABASE SERVER =============== The Database Server function of G8RE is used to share IDS-II databases between multiple Batch or TP users, unlike MFE8 where you would normally work with local/non-shared databases. The Database Server is implemented using File Share 2, and G8RE includes a preconfigured server named RGLOBAL for you to use. Before using the Database Server the first time, and after you have restored one or more IDS-II databases, you need to initialize the RGLOBAL Server. Use 'Initialize FS2 RGLOBAL Server' in 'FS Administration Tools' folder to do this. This only takes a few seconds and it will prepare the server for operation and delete any RollBack log files. Use 'Run FS2 RGLOBAL Server' on the Server PC to launch the Database Server process. The Server becomes operation within a few seconds, and you can at any time use the Escape-key to request termination of the Database Server. Note: You can leave the Database Server running at all times, however, when performing DB Backup/Restore/Load/Unload or using Q2UT Utility, you should either shutdown the Database Server (recommended) or make sure there are no active users of the Database Server. TP8 === Like MFE8, a complete TP8 single-user system is executed on each PC Workstation running G8RE environment, however each TP8 system will acces a shared Database Server. TP8 is launched with the RUN TP8 command or icon, ex. RUN TP8 Following configuration entries in Defaults Configuration (G8WB.CFG) may be used to control TP8 Server: [G8WB-DEFAULTS] ; Defaults configuration TERMINAL-EMULATION : DKU71XX TNVIP ; ; Emulator [Interface] ; VIP77XX ; VIP78XX ; DKU71XX ; IBM327X ; TNVIP ; TN3270 The Terminal-emulation setting defines the default terminal emulation for TP8. The TNVIP|TN3270 setting may be used to connect through a terminal emulator, ex. Glink, instead of the built-in terminal emulators provided by G8RE. [G8WB-TRACE] ; Trace configuration TP-TX-SEQUENCE : OFF ; Trace TX/TPR state TP-EXEC-CALL : OFF ; Trace TP Interface/procedure calls TP-COMM-DETAIL : OFF ; Trace SEND/RECEIVE details TP-TPR-EXECUTE : OFF ; OFF(default)/ON TP-RESPONSE-TIME : ON ; OFF(default)/ON/PROFILE TP-GLOBAL-JOURNAL : ON ; OFF(default)/ON TP-RESPONSE-TIME:ON cause a one line trace to be written to $g8rbldir\ JOURNAL.LOG for each TX/PHASE. TP-GLOBAL-JOURNAL:ON cause the JOURNAL.LOG to be appended to $g8rbgdir\JOURNAL.nnn file, where nnn = current day number. TP-TPR-EXECUTE should be left OFF, otherwise a message is sent to the client, whenever a TPR is executed. TP-TX-SEQUENCE, TP-EXEC-CALL, TP-COMM-DETAIL:ON cause a substantial amount of debug/trace information to be written to JOURNAL.LOG. Note: TP8 will continue to run until it is stopped, either using $TERM (or disconnect within Glink), or using the ESC-key to trigger menu for built-in emulators. BATCH ===== Batch application are launched with the RUN PRG command or icon. The command line format is as follows: RUN PRG ["title"] programname [normal|exclusive|nolog| auto|query|nodb] [cbl85|cbl74] [=outfilename] [/ldirpath|/.]" Title: When specified, the title is applied to the execution window. Must be first argument and a quoted value. Programname: The programname or filename of the application program. Databasemode: May be used to control access to the database, if applicable. The default is normal. Nodb = database not used by program Exclusive = lock database and perform auto-commit Nolog = access database without logging (exclusive) Auto = access database with auto-commit Query = access database with query Note: All schema and subschema domains configured are pre-loaded before the application is launched. Environment: The execution environment for COBOL-85 or COBOL-74 is now preloaded. The default is cbl85. Redirect: The log may be redirected to a file. The default is $g8rbldir\BATCH.LOG. G8RBLDIR: The setting for G8RBLDIR may be changed on-the-fly, ex. /c:\temp (specific path) /. (current path) Following configuration entries in Defaults Configuration (G8WB.CFG) may be used to control Batch: [G8WB-TRACE] ; Trace configuration BATCH-EXEC-CALL : OFF ; Trace Interface/procedure calls BATCH-GLOBAL-LOG : ON ; OFF(default)/ON BATCH-GLOBAL-LOG:ON cause the BATCH.LOG to be appended to $g8rbgdir\BATCH.nnn file, where nnn = current day number. BATCH-EXEC-CALL:ON cause debug/trace information to be written to BATCH.LOG. ======== COMMANDS ======== The graphical IDE used in the MFE8 environment is not available within G8RE environment. Likewise only a subset of the functions are available. G8RE functions are either launched from icons 'GCOS8 Run-time Expres' folder (and sub-folders), or launched as commands from the 'G8RE Command Prompt' or within BAT files. G8RE commands may be launched using the RUN command from 'GCOS8 Run-time Command Prompt', ex. RUN command [arguments] To launch G8RE commands from OS Command Prompt, or an OS Command file, you need to prefix the RUN command with the G8RE path, unless this has been included in the PATH setting, ex. c:\g8rep\bin\RUN command [arguments] The following G8RE commands are available: Syntax: TP8 Start TP8 system. Syntax: PRG programname Start Batch program. Syntax: IIDS subschema FILE filename [=output-file] Execute IIDS Utility with DML script. Syntax: PRCEXP print-file[.ext] [report-file] Expand Report-code or Report-writer print-file into separate report files. Default extension for print-file is DAT. Report-file extension is forced to Dnn, where nn = report-code. Syntax: PSWS nn+|- [...] where nn = 00-35 or 99(all) + = set switch ON - = set switch OFF Set or reset PSW switch or switches. Syntax: PSWT nn where nn = 00-35 Test status of PSW switch and set ErrorLevel 1 = ON. Syntax: PSM psm-file [_List-source] Execute PSM sort. Syntax: G8WFL profile[.g8p] [inputfile[.g8f] outputfile[.dat]] Convert GCOS8 file. Syntax: DBBCK schemaname backup-set Backup a database. Syntax: DBRES schemaname backup-set Restore a database. Syntax: DBUNLD schemaname unload-file[.dat] Unload a database. Syntax: DBLOAD schemaname load-file[.dat] [_Update [Only]] [_Force] [_Trace] [_1|_2] Load whole or parts of a database. Syntax: BATLOG some message Write message to consolidated Batch Log. Syntax: BATCH command-file[.cbt] Execute a G8RE command-file. Default extension is CBT. Some G8RE commands may also be launched in interactive mode: Syntax: IIDSG Execute IIDS Utility interactively. Syntax: DBBCKG Execute DBBCK Utility interactively. Syntax: DBRESG Execute DBRESG Utility interactively. Syntax: DBUNLDG Execute DBUNLD Utility interactively. Syntax: DBLOADG Execute DBLOAD Utility interactively. Syntax: Q2UTG Execute Q2UT Utility interactively. Syntax: G8WFLG Execute G8WFL Utility interactively. Syntax: PRCEXPG Execute PRCEXP Utility interactively. Syntax: PSWG Execute PSW Utility interactively. Syntax: CONFIG Launch Configuration Utility. Syntax: BCF Execute BCF Utility interactively. File mapping ------------ Like MFE8, G8RE utilize External mapping for conventional files. By default the GCOS8 file-code is used as 'logical name', except for I* and P* which use SYSIN and SYSOUT respectively as 'logical name'. PSM files are mapped slightly different, ex. PSM-file is named TEST.PSM TESTSA is input file TESTSZ is output file Default ------- Files are by default accessed through their 'logical name' under the current directory. Ex. GCOS8 $ prmfl I1,R,S,UMC/myfile $ sysout P* Ex. G8RE read I1 under current directory write SYSOUT under current directory Setting ------- 'Logical name' may be mapped to a physical file through environment settings. ex. SET I1=C:\g8rbl\myfile.dat SET I1=$App1\files\Myfile.dat Mapping file ------------ 'Logical name' may be mapped to a physical file through a mapping file. This file is name 'MFEXTMAP.DAT'. ex. program mapping I1 $app1\files\Myfile.dat O1 $app1\files\Myfile.dat SYSOUT $g8rbldir\SYSOUT. G8RE will search for MFEXTMAP.DAT under current directory and if not found under all directories specified in COBDIR (left-to-right). G8RE can be directed to a specific MFEXTMAP.DAT file through the following setting: SET MFEXTMAP=$app1\files Note: G8RE can ONLY use one 'MFEXTMAP.DAT', and will stop searching as soon as a MFEXTMAP.DAT file is found. Search for MFEXTMAP.DAT can be disabled through the following setting: SET MFEXTMAP=NO Mapping Rules ------------- File mapping rules are applied in the following priority order: o Environment: Use if setting is found. o Mapping-file: Use if mapping is found within MFEXTMAP.DAT file. o Logical-name: Use default access through 'logical name' under current directory. Command Files ------------- GCOS8 JCL and job streams are not supported by G8RE, however, you can use G8RE commands to build command files (BAT) with similar functionality. When using Environment setting for file mapping, remember mapping must be done before execution of batch program. Ex. rem My example batch stream SET SYSIN=$app1\files\par1.txt SET LS=$app1\files\output.dat rem Execute P1 RUN PRG p1 rem Expand report-file and print it RUN PRCEXP $app1\files\output wrk PRINT wrk.D10 DELE wrk.D10 Conditional JCL using Program-Switch-Word can be tested as follows. Ex. rem My example batch stream rem Reset all switches RUN PSWS -99 rem Execute P1 RUN p1 rem Test switch 21 RUN PSWT 21 if errorlevel 1 goto label2 :label1 rem Execute P2 RUN PRG p2 :label2 ERRORS FIXED & IMPROVEMENTS IN RELEASE ====================================== o DBSP: G8RE now support DBSP and thus allows you to develop and test DBSP programs within MFE8. See $g8rbgdir\dbsp.txt for details. o WEB8: Support has been updated to v2.0 and support of browser connection via HTTP-DSA Gateway and GEAP. o IDS-II: When a database is created, the maximum sizes for Data record, Calc key and Index key are used to minimize the size of the physical database files. If these maximum sizes are increased, i.e. adding new record, calc or index key to schema, you were required to unload the database (before making such changes) and load the database (after making such changes), otherwise database access would fail with error 110018 (CALC/INDEX/Record-size-overflow). You are now able to 'fix' this overflow problem, by doing a Rebuild (ALL) with Database Utility (Q2UT). During Rebuild, maximum size changes are detected, and this will trigger a recreation of the entire database, ex. RUN WB Q2UT class r all Note: Above solution will only work if the schema changes do NOT involve any existing records in the database. o TP: The default entry for CREATE_COMMAND, which is used to start a transaction without a create_command entry, may now specify a first-tpr and profile, ex. ******** : SLDINP SOLDDBK ; Default is SOLD+ TX o TP Bibo: The TPCLI command now support a command line to enable execution of a single BIBO transaction or a BIBO transaction file. The command line syntax is as follows: RUN WB TPCLI [BIBOTX "command"|BIBOFILE bibo-file [secs]] [defaults] Command - must quoted if spaces are present (single or double quote). Bibo-file - a file containing one or more transaction. For conversational transaction, the special BIBO format must be used, ref. MFE8 documentation. Secs - may be used to set a delay in seconds between each read of the bibo file (default is 0). Note: BIBOTX and BIBOFILE will terminate TPCLI once BIBO transcation(s) have been executed. Defaults format is: [lid [terminal-emulation]] [/ldirpath|/.] Lid - may be used to set a lid for the session, and thus override default configuration. Terminal-emulation - may be used to set terminal emulation and interface for the session, and thus override default configuration. VIP77XX|VIP78XX|DKU71XX|IBM327X REMOTE|TCLIENT G8RBLDIR: The setting for G8RBLDIR may be changed on-the-fly, ex. /c:\temp (specific path) /. (current path) o Terminal Emulation: When using terminal emulation software, ex. Glink, VTD/Amaril, with TELNET or TNVIP interface, the national character-set configuration may now be identical for GCOS and G8WB (adapted to/from PC standard by the interface, whenever CHARACTER-SET-ADJUST is active). o IDS-II: By default all index files (databases) share a common 16KB buffer for index handling. This is normally sufficient, however when loading 'large' databases or when extensive changes are made to keys (Calc and Index), the I/O-system may report problems (9/041 corrupt index). A new option in DBMS.CFG may be used to allocate more buffer space for index handling, ex. [DEFAULT-SECTION] IDX-BUFFER-KB : 32 ; Min. 4 Max. 60 KB When present, the IDX-BUFFER-KB will allocate a buffer of the given size for each index file. This may require substantially more memory if many databases are used concurrently. o IDS-II: FIND DUPLICATE processing has been optimized and now use less I/O, especially when many duplicates exists for the same calc-key. o IDS-II: STORE processing has been optimized and now use less I/O for duplicate calc- and/or index keys, especially when many duplicates exists for the same key(s). o WEB8: The 'Referer:' header field is now emulated, so a TPR can retrieve the information through HTTP_GETHDR. The format is GCOS compatible, ex. http://gateway:8080/node.mbx/TPLocG8WB/Command/Options ---------------------------- I I-> constant o TP/TNVIP: The command $BYE is treated as $TERM when connection to TP is done trough terminal emulation software, ex. GLINK. o Terminal Emulation: 'Real' Terminal Emulators may now be used with G8RE, provided they can use either TNVIP or TN3270 communication interface. The TERMINAL-EMULATION entry in Default Configuration (G8WB.CFG) has been changed as follows: TERMINAL-EMULATION : emulation [interface] ; Emulation ; VIP78XX ; DKU71XX ; IBM327X ; WEB8 ; Other = Name of own Program ; Interface ; TNVIP ; TN3270 ; REMOTE When no interface is specified, the G8RE terminal emulators are used. When REMOTE interface is specified, the Open-Client-Interface is used. TNVIP/TN3270 ------------ When TNVIP or TN3270 is specified, G8RE will act as a telnet Server and listen for a connect on the standard Telnet port (23). The Terminal emulator must be configured with TNVIP or TN3270 as communication interface, and the host name or IP adress of your PC. G8RE will attempt to negotiate a terminal model, and if this fails or the terminal model is not recognizable, the G8RE emulation configuration will be used. The G8RE window will show status messages and you may use ESC-key to trigger the Escape-menu, or request this through a command from the terminal emulator. The following commands are recognized: $*$DIS - terminate and disconnect $*$LOGOUT - terminate and disconnect $*$ID - show connect information $*$BRK - Abort conversational transaction ($ABORT) 'break' signal, treated as $*$BRK $*$ESC - request G8RE escape menu $ESC - request G8RE escape menu $BYE - logon with a new Lid $TERM - terminate TP Note: IBM3270 emulation can only be used with TN3270. Note: TSACC and TSDSP (batch) can also use this feature. o Open-Client-Toolkit: A new DSA interface is now available. With Client DSA, G8RE may present itself as a DSA Node in your network and allow a DSA session (direct or through DNS) to be established with G8RE. The DSA interface may be used to connect Terminal Emulation products or applications through various client interfaces. DSA interface is based on G&R Ggate, and requires either Host Links or Ggate from G&R. Refer to $g8rbgdir\site\client\g8wbotc.txt for details. o WEB8: Graphic files are now supported. o WEB8: Forms import now provide a more flexible configuration of //localhost. o WEB8: Forms import now provide additional default file extensions for the index function. o Open-Client-Toolkit: A new and simpler interface is provided for interfacing TP8 client application with G8RE. Refer to $g8rbgdir\site\client\g8wbotc.txt for details. ============ TIPS & HINTS ============ n/a ============ KNOWN ERRORS ============ o MFEXTMAP: If the MFEXTMAP.DAT file contains an entry with only one word on the line, the file is not processed correctly (mapping does not work) and the MFEXTMAP.DAT file will be left in a 'busy' state (unable to update). This error can typically occur if comment lines are placed in MFEXTMAP.DAT, ex. * * Above line will trigger problem * Line below will not trigger problem * * * My test files sysin in1.dat o CONFIG: If you forget the ":" (separate keyword from arguments) in a config-file entry, you do not always get an error message. ================= KNOWN LIMITATIONS ================= o SYSOUT: The SYSOUT file will be closed if a program is cancelled. If generic or default mapping is used, then some SYSOUT may be lost if a program writing to SYSOUT (DISPLAY verb) is cancelled. o MFEXTMAP: The number of entries in MFEXTMAP.DAT is limited by Environment Space under Windows 95 and 98, as all entries in MFEXTMAP.DAT file is placed into environment during startup of a Workbench function. The maximum size of environment space may be controlled via a 'SHELL=... /E:nnnn' entry in config.sys. If no size is specified, the maximum is 32768 bytes. Note: If environment space is insufficient, the MFEXTMAP.DAT file is not processed correctly (mapping does not work) and the MFEXTMAP.DAT file will be left in a 'busy' state (unable to update). o MFEXTMAP.DAT: General performance is very sensitive to the placement and size of the MFEXTMAP.DAT. Placing an MFEXTMAP.DAT with more than a few (10-20) mapping entries on a network drive, can result in degraded performance, depending on network setup. As a temporary solution, you should either only work with a local MFEXTMAP.DAT or copy your global (on a network drive) MFEXTMAP.DAT file into a local drive during startup of RHE8, if you experience such degraded performance. =================== MANUAL INSTALLATION =================== Manual installation is not possible with G8RE and Application Server. ================= PROBLEM REPORTING ================= Please use the enclosed Software Problem Reporting (SPR) forms for problem reporting. Describe your problem in as much detail as possible, providing example(s) and/or other supporting material if possible, and send this to B & C Solution P.O. Box 54 Ole Piisvej 4 DK-3100 Hornbaek Denmark or fax to +45 49.70.47.80 or send through email to support@bc-solution.com If you have any questions, suggestions for changes and/or improvements, please do not hesitate to let us know. More recent updates are available through INTERNET for download or verification of update content. Connect to our web-site 'http://www.bc-solution.com', go to the Support section and select 'GCOS8 Run-time Express V4.0 Update' under Download Software Update. DISCLAIMER ========== THIS SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. B & C SOLUTION DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL B & C SOLUTION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF B & C SOLUTION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY. ========================================================================= GCOS8 Run-time Express and GCOS8 Mainframe Express are trademarks of B & C Solution. All other trademarks and trade names are the property of their respective owners. ========================================================================= Copyright (C) 1998-2004 B & C Solution. All Rights Reserved.