========================================================================= G C O S - 8 C O B O L W O R K B E N C H v1.4.53 32bit RELEASE ========================================================================= UPDATE NOTES ============ TABLE OF CONTENTS ================= INTRODUCTION MIGRATION ERRORS FIXED IN THIS UPDATE IMPROVEMENTS IN THIS UPDATE DOCUMENTATION CHANGES TIPS & HINTS KNOWN ERRORS KNOWN LIMITATIONS PROBLEM REPORTING INTRODUCTION ============ This update diskette contains fixes to all problems and all new features since release v1.4.40. Previously provided update diskettes are obsolete and no longer required. MIGRATION ========= ===> V1.4.53 o n/a ===> V1.4.52 o n/a ===> V1.4.51 o WEB8: Consult $g8wbgdir\web8.doc for details on migration. ===> V1.4.50 o VMPS: Due to changes in VMPS copy handling, the following migration activity should be performed, if you are using VMPS services: Change the VMPS library definitions in $g8wbgdir\COPYMAP.CFG as follows (copy from $g8wbgdir\refcfg\copymap.cfg): [VS] ; Standard VMPS copies (VS Library) ; &VS008P/DATA/BLAISTATCOPY DEFAULT-DIRECTORY : $g8wbdir\vmpscpy\s [VF] ; Standard VMPS copies (VF Library) ; &VE008P/DATA/BLAIFMSCOPY DEFAULT-DIRECTORY : $g8wbdir\vmpscpy\f [VB] ; Standard VMPS copies (VB Library) ; &VE008P/DATA/BLAIBATCHCOPY DEFAULT-DIRECTORY : $g8wbdir\vmpscpy\b [VQ] ; Standard VMPS copies (VQ Library) ; &VS008P/DATA/BLAIQRYCOPY DEFAULT-DIRECTORY : $g8wbdir\vmpscpy\q [VE] ; Standard VMPS copies (VE Library) ; &VE008P/DATA/BLEIFILECOPY DEFAULT-DIRECTORY : $g8wbdir\vmpscpy\e ===> V1.4.49 o n/a ===> V1.4.40 o New base release for 32-bit environment. ============== UPDATE V1.4.53 ============== Errors fixed in this update --------------------------- o COMP-4 Analyzer: The check for UNRELATED redefines now detect redefine of COMP with numeric DISPLAY. o IDS-II: Use of shared INDEX KEY, i.e. multiple record using same key name, would only work for the first shared key. o COBOL: The combination DECIMAL-POINT IS COMMA and files using REPORT-CODE would result in incorrect flagging. Problem introduced by enhancement in V1.4.49. o WEB8: HTML_BASE failed to include the script-name for CGI interface, and use of HREF (relative references) would thus fail. o TP8: Use of Default Command (********) to start an undefined TX (entered command = first tpr, only worked the first time. This problem was introduced in V1.4.48. Improvements in this update --------------------------- o COBOL: COMP-1 and COMP-2 may now be processed in ALT mode (like COMP-6) to supported redefines, ex. *w8prep alt 01 status-key COMP-1 VALUE ZERO. *w8prep on 01 status-key-r. 05 filler PIC X(01). 05 status-key-byte PIC X(01). o TP8 Services: A number of TP8 Service functions are now fully or partially supported as follows: _TP_SPAWN_TRANSACTION _TP_RECEIVE_MESSAGE _TP_SEND_MESSAGE _TP_PURGE_MESSAGES _TP_GLOBAL_STORAGE _TP_CANCEL_TPR _TP_SLEEP_SERVICES _TP_TPR_SERVICES _TP_WORKSTATION_SERVICES _TP_BROADCAST _TP_SPAWN_BATCH _TP_RESOURCE_SERVICES (partial) _TP_SEGMENT_SERVICES _TP_PROCESS_SERVICES _TP_GET_PARAMETER_SIZES _TP_JOURNALIZE _TP_USER_TRACE _TP_SET_PRIORITY _TP_FILE_SERVICES .BCST .SRCVM .TPRST .CNVRS (partial) .AJCMT (partial) .FNLCP .PILNK .CRPRM .ALPRM .DAPRM .CATMP .DLTMP .GRPRM .GRTMP .CAPRM .CRCLG .BAKDR .FLINF .PGPRM o Batch spawn: The batch spawn functions (VMPS, TP8 etc.) will both document the spawned JCL on the Batch/TP log, and create a file with the spawned JCL, ex. $g8wbldir\.job The generated snumb now use a start value of (time of first spawn), which is incremented for each spawn, ex. 1000Z, 1001Z. o TP8: To obtain better compatibility for use of conventional files within TP8, G8WB has been enhanced as follows: - files allocated through VMPS or ACCESS are permanent, and thus not deallocated until TP8 is terminated - files allocated through _TP_FILE_SERVICES, .ALPRM, .CATMP or .CAPRM are temporary, and thus automatically deallocated and reset when the transaction terminate (normal or abnormal) Note: Files are not deallocated/reallocated after commitment like GCOS, however, this is not required for G8WB, since only one process is used. - before execution of a TPR or module, G8WB will check all file-codes (all select's defined) for dynamic allocation, and reset mapping for any file-code not currently allocated Note: If a reset file-code is used (OPEN Input/Output), the status 9/9 (No room in directory) is triggered. Temporary files are created under $g8wbldir (\hhmmss.TMP), however like GCOS, such files are automatically released when deallocated. If you need to permanently allocate a file to TP8, i.e. using a $ PRMFL for the TP8 process JCL, you can obtain similar behavior in G8WB using a permanent environment setting for the file-code, ex. SET F1=f:\data\file1.dat ============== UPDATE V1.4.52 ============== Errors fixed in this update --------------------------- o DBWFL: Load of database in 'update' mode would fail during load of set records (Corrupt Database abort). This problem was introduced in V1.4.48. Note: Load program must be regenerated for this fix to become effective. o VMPS: When only a umc specified, the X_LIST_CATALOG and X_LIST_FILE would report the catalog as non existing. o VMPS: Files are catalogs with a period, ex. myfile.idx, were were not reported correctly by X_LIST_CATALOG and X_LIST_FILE (period and the remainder was missing). o VMPS: An empty catalog (created by hand) was not be recognized (treated as non-existing) by functions like X_LIST_FILE. o VMPS: The date fields (create, changed etc.) for catalog and files had incorrect year value. o VMPS: The X_CONTINUE_CATALOGS/FILES function will now return an error (primary = 3), if called without token or with an invalid token. Improvements in this update --------------------------- o VMPS: The standard copies for VMPS makes extensive use of under- score (_) and this complicates query operations within Animator, since fields are adapted to use dash (-) by G8WB. Since fields names in the original source are not the same, it is not possible to double-click (or use Query Cursor) to view the content of a field. A new Preprocessor directive may be used to trigger use of standard VMPS copies, where the underscore is changed to dash, ex. [DEFAULT-SECTION] USE-CPA : ON ; OFF(default)/ON When specified in $G8WBGDIR\PREP.CFG, all standard VMPS copies are adapted globally. The directive may also be specified in local configuration or in the program source, ex. *set>g8wb use-cpa:on IDENTIFICATION DIVISION. Note: Any REPLACING arguments are automatically adapted from underscore to dash, so original source will be compatible with GCOS. o TP8: The service calls ACCESS, DEACCS and FMSG, may now be used from a COBOL-85 TPR/module (non documented GCOS feature). o DBSP: G8WB now support DBSP and thus allows you to develop and test DBSP programs within G8WB. See $g8wbgdir\dbsp.doc for details. ============== UPDATE V1.4.51 ============== o Limitations has been updated, ref. below. Errors fixed in this update --------------------------- o Pilspraak: The command _A did not work correctly (others part of screen cleared), due to a problem in the IBM3270 terminal emulation (RA command). o COBOL-85: END-RECEIVE and END-SEND verbs were not processed correctly and would cause fatal errors. o Dispatch8: When requesting print of a specific report (active or complete), the retention check could override the specified day and time, and the wrong report would be printed/reprinted. o Format: A problem fix introduced in v1.4.33 would cause a non-Format send to fail (only send with length = 1). Improvements in this update --------------------------- o TP8: Stack level checking may now be enforced. A new keyword under CREATE_TP8_EXTENSION in TP8.CFG may be used to define the maximum stack level. [CREATE_TP8_EXTENSION] STACK_LEVEL : 4 ; Range 0-32, default is 4 o TP8: The standard copy for TP-STORAGE has been changed for compatibility with GCOS and now has two new fields: STACK-LEVEL - contains current stack-level (1 through 32) USER-SAVE-AREA - same as LID-STORAGE o WEB8: Support has been updated to v2.0 and support of browser connection via HTTP-DSA Gateway and GEAP. o RFV: RFVCXAP send procedures will now provide additional debug information in the journal log, whenever the TX is aborted by RFVCXAP. ============== UPDATE V1.4.50 ============== o Tips and Hints has been updated, ref. below. Errors fixed in this update --------------------------- o COBOL: Preprocessing of SEND (without FROM) could lead to incorrect preprocessing of subsequent SEND and cause run-time errors (CD not passed). Problem introduced by enhancement in V1.4.49. o IDS-II: Sorted sets did not work correctly for SIGNED DECIMAL field(s) in the KEY clause - positive values were placed before negative values. o COBOL: Preprocessing of DECIMAL-POINT IS COMMA was incorrect if specified on the same line as SPECIAL-NAMES. Problem introduced by enhancement in V1.4.49. o Create-Copy: Could fail when trying to register an existing copy file from the reference directory. o Create-Copy: Could override an existing copy, if this had been manually copied to the reference directory (unregistered). o IDS-II: When a database is initialized with GCOS8-DBK-ALLOCATION setting = ON, allocation of DBK's could fail if the schema was not translated with sufficient information. This situation is now detected and GCOS8-DBK-ALLOCATION is ignored, if schema has insufficient information. Improvements in this update --------------------------- o VMPS: Support of VMPS services has been substantially improved. Copies ------ A new and more complete set of COBOL-85 copy members are now provided. Remapping from long to short file name is no longer used, ref. migration notes above. The library &VE008P/DATA/BLEIFILECOPY is now available through library tag VE, ex. COPY ... OF VE. Services -------- The following services, which were previously ignored, are now fully or partially emulated. X_CREATE_CATALOG X_DELETE_CATALOG X_MODIFY_CATALOG X_CREATE_FILE X_DELETE_FILE X_MODIFY_FILE X_INIT_CATALOG_ATTRIBUTES X_LIST_CATALOGS X_COUNT_CATALOGS X_COUNT_CATALOG_PERMISSIONS X_CONTINUE_CATALOGS X_QUERY_CATALOG_ATTRIBUTES X_QUERY_CATALOG_PERMISSIONS X_INIT_FILE_ATTRIBUTES X_LIST_FILES X_COUNT_FILES X_COUNT_FILE_PERMISSIONS X_CONTINUE_FILES X_QUERY_FILE_ATTRIBUTES X_QUERY_FILE_PERMISSIONS X_CONTINUE_FMS_QUERY X_SORT_CATFILE_NAMES X_QUERY_FILE_STRING X_QUERY_PHYSICAL_FILE_ADDRESS X_ALLOC_PERM_FILE X_ALLOC_TEMP_FILE X_DEALLOC_FILE X_GROW_FILE X_SHRINK_FILE X_ALTER_FILE_DISPOSITION X_QUERY_IDENT_CARD X_SPAWN_JOB_FROM_FILE (validated and documented) X_SPAWN_JOB_FROM_MEMORY (validated and documented) X_CALLUSER Module must be configured, ex. $g8wbgdir\site\vmps\w8callu. X_WRITE_SYSOUT File-code = P* = display on SYSOUT (normal mapping) = 00 = write to journal/batch.log = other = use FAT or $g8wbldir\. X_BACKDOOR_SYSOUT X_WRITE_SCF Information appended to $g8wbldir\scf.log (Record Seq file) X_QUERY_BASE_RELEASE X_QUERY_SECURITY_OPTIONS X_QUERY_SOFTWARE_SET X_QUERY_SYSTEM_ID X_QUERY_SYSTEM_PRODUCTS_USERID X_QUERY_SYSTEM_TYPE X_QUERY_IDENTIFIERS X_PROCESS_GETINFO X_WIRE_UNWIRE_BUFFER X_RANDOM_IO Roadblock = Y is ignored, iocb I/O status not available X_WAIT X_RELINQUISH X_ROADBLOCK X_QUERY_SNUMB_ACTIVITY (limited) X_SNUMB_QUERY X_CONTINUE_SNUMB_QUERY X_QUERY_JOB_STATUS Snumb information may be configured, ref. below. X_DOMAIN_DUMP (validation only) X_SNAP_DUMP (validation only) X9CL$PROGRAM_NAME X9CL$CALLER_NAME Caller name is ONLY available until a CALL is issued by current program. X9ST$IPR (ignored) X9ST$IPR_R (ignored) X9ST$IPR_EXIT (ignored) X8RV$UNMASK_IPR (ignored) X8RV$MASK_IPR (ignored) X9IA$LANGUAGE (ignored) TSTCHK (allways 0 returned) Dynamic file allocation ----------------------- An internal FAT table is used to keep track of dynamically allocated files. At normal termination, entries in the FAT table is processed according to the associated disposition code: R(elease) will cause temporary files to be deleted S(ave) will cause information to be logged in the journal The same processing occur for abnormal termination, provided this is triggered through X_ABORT. Note: Temporary files are allocated under $g8wbldir with the name .tmp. Note: No automatic allocation (from FAT) is possible for a subsequent activity, saved files are merely documented in the journal. Configuration ------------- A new configuration section [GCOS-CONFIG] has been added to Environment configuration $G8WBGDIR\ENV.CFG (Global/Local). These new settings are used by VMPS services. [GCOS-CONFIG] USERID : umc ; Default is OPNSUTIL IDENT : "umc,mail" ; Default is "UNDEFINED" PERSONID : "myself" ; No default PROJECTID : "project1" ; No default BILLING-ACCOUNT : "acc1" ; No default CALLUSER : $g8wbgdir\site\vmps\w8callu ; No default SYSTEM-ID : sys-test ; Default is SYS-G8WB SYSTEM-TYPE : "DPS 90" ; Default is "DPS 9000" BASE-RELEASE : 4020 ; Default is 5000 SOFTWARE-SET : 40202 ; Default is 50002 PRODUCTS-USERID : sys_umc ; Default is sys_software RELEASE-ID : 402020 ; Default is 500020 LINES-PER-PAGE : 48 ; Default is 64 TIME-ZONE : CET ; Default is EDST TIME-DELTA : +1 ; Default is 0 SECURITY-OPTIONS : "11000" ; Default SSM not active ; 1=active, 0=not active ; x.... = access ; .x... = pid ; ..x.. = pic ; ...x. = scc ; ....x = system Configuration settings may also be specified through environ- ment variable (except lines-per-page, time-delta) by prefixing the keyword with "GCOS-", ex. SET GCOS-SYSTEM-ID=SYS-TEST SET GCOS-USERID=sys_software Environment settings override any settings in ENV.CFG. A new configuration section [FMS-CONFIG] has been added to Environment configuration $G8WBGDIR\ENV.CFG (Global/Local). These settings are used to emulate FMS within the related VMPS services. [FMS-CONFIG] DEFAULT-PATH : $g8wbgdir\gcos8fms ; No default CHECK-PERMISSION : ON ; Default OFF CHECK-PASSWORD : ON ; Default OFF myumc1 : F:\myumc1 ; UMC specific mapping myumc2 : F:\myumc2 ; UMC specific mapping DEFAULT-PATH when set: The UMC is automatically created under the default-path during CREATE_FILE or CREATE_CATALOG services. DEFAULT-PATH when NOT set: A UMC must be configured before creating files or catalog. Configuration settings may also be specified through environ- ment variable by prefixing the keyword with "FMS-", ex. SET FMS-DEFAULT-PATH=F:\fms_structure SET FMS-CHECK-PERMISSION=ON SET FMS-MYUMC1=F:\myumc1 Environment settings override any settings in ENV.CFG. A new configuration section [GCOS-SNUMBS] has been added to Environment configuration $G8WBGDIR\ENV.CFG (Global/Local). These new settings are used to provide snumb information for snumb query services. [GCOS-SNUMBS] ;Snumb Job status Z1001 : SWAPPED A5000 : "NOT ACCESIBLE" ... FMS --- Catalog attributes are partially implemented. This is done through creation of a CAT.ATT.ATT file under the catalog (UMC or sub- dinate catalogs). File attributes are partially implemented. This is done through creation of a .ATT file, alongside the actual file. Catalog and/or files may be created 'by hand' with or without the associated attribute file. If no attribute file is present, default attributes are assumed. The attribute file is a text-file, which can be created/edited 'by hand' also. Example for catalog: ORIGINATOR= DATE-CREATED= TIME-CREATED= DATE-CHANGED= TIME-CHANGED= SECURITY-LOCK GENERAL-PERM= = ... Example for file: ORIGINATOR= DATE-CREATED= TIME-CREATED= DATE-ATTR-CHANGED= TIME-ATTR-CHANGED= DATE-CHANGED= TIME-CHANGED= PASSWORD= SECURITY-LOCK ACCESS-MODE=RANDOM MAX-SIZE=UNLIMITED| GENERAL-PERM= = ... o COBOL: Dynamic file allocation/creation is now supported in batch environment. ACCESS (allocate/create file) DEACCS (deallocate file) FMSG (print error message) FMS handling is similar to VMPS, ref. above. o COBOL-85: The following services are now recognized in Batch environment and are now fully or partially emulated. .DFLSH (treated like CHECKPOINT_FILES) .DCNCL (treated like ROLLBACK_FILES) X9CL$CLIMB (treated as direct CALL of module) S$ABORT SETL X9CL$MAIN_NAME TSWAIT TSCOPT WRAP (ignored) X9GC$SELECT_CONSOLE (ignored) X9PP$PAGE_PRINT (ignored) X9RS$REWIND_AND_STANDBY (ignored) X9DB$DSS (ignored) o GFRC: All GFRC files, except files with CARD-READER, CARD-PUNCHER or PRINTER specification in the ASSIGN clause, are treated as RECORD sequential files (like UFAS). CARD-READER/PUNCHER files are treated a LINE sequential (text) files. Since GCOS can use GFRC format for both text and non-text, and CARD-READER/PUNCHER is often not specified, a G8WB developer may be surprised to find a GFRC file cannot be edited as a text file. G8WB now provides two new techniques for making a GFRC file a text file, without the need to change the SELECT clause, i.e. adding CARD-READER/PUNCHER. A new preprocessor directive GFRC-TEXT may be used to change the default format of GFRC files, ex. [DEFAULT-SECTION] GFRC-TEXT : ON ; OFF(default)/ON(text format) When specified in $G8WBGDIR\PREP.CFG, the default for GFRC files can be changed globally. The directive may also be specified in local configuration or in the program source, ex. *set>g8wb gfrc-text:on IDENTIFICATION DIVISION. The ALT mode directive may also be used to change default format for GFRC files, ex. *w8prep ALT SELECT my-file ASSIGN TO F1 ORGANIZATION GFRC ... *w8prep ON When using ALT mode, the current default for GFRC files is reversed, i.e. format changed to text or RECORD if GFRC-TEXT is ON. Warning: The text format is not fully compatible with GCOS for a read operation, as G8WB will clear the record (process area) with space, whereas GCOS will not. If you prefer to use text format, you can ensure compatibility by placing a 'MOVE SPACES TO record' before the READ. ============== UPDATE V1.4.49 ============== o Limitations has been updated, ref. below. o Tips and Hints has been updated, ref. below. Errors fixed in this update --------------------------- o Preprocessor: The combination G8WFL-BSF-GENERATE:ON and Report Section could lead to a failure (R6018 Heap error), especially when checking multiple sources through a command file (CBT). o COBOL: A PIC clause for COMP-11 and COMP-12 would be flagged. The PIC clause is now removed, provided it is specified on the same line as the usage. o COBOL: A CALL without USING followed by a valid identifier would not be flagged. o Preprocessor: STACK-NEW and STACK-COPY maximum setting is 255, however, documentation said 256, and a misleading error message was given if the maximum of 255 was exceeded. o G8WFL: COMP-7 and COMP-8 fields are now supported. o G8WFL: COMP-6 fields with ALT-mode or 36-bit were not converted correctly. o G8WFL: DB-KEY fields with 36-bit were not converted correctly. o DBWFL: A COMP-6 field with ALT-mode did not have a PIC clause in the generated unload/load programs. o COBOL-85: Usage GBCD and EBCDIC is now recognized, however, they are treated as usage DISPLAY. o COBOL: COMP-7 fields in ALT-mode can now be redefined as PIC x(02), similar to COMP-6 in ALT-mode. o TP: SEND/RECEIVE verbs did not accept qualification, subscript and reference modification for identifier-1 (FROM or INTO). o COBOL: If the last source line contained a COPY and it was not terminated by period, G8WB preprocessor would abort. o G8WFL: Conversion of GRFC files could cause incorrect warning messages (sign or numeric errors) or fatal error message (invalid media-code). G8WFL was incorrectly assuming the last record in a block was followed by an 'low-value' RCW (or EOF), however this is not always true, and BCW/RCW information is now used to detect end-of-block and end-of-file. o WEB8: When importing HTML, the syntax was incorrectly adapted, when either file:/http:/ftp: format was used. o COBOL-85: $set>mfwb directives did not work for COBOL-85. Improvements in this update --------------------------- 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. WB W8 Q2UT class r all Note: Above solution will only work if the schema changes do NOT involve any existing records in the database. o TP8: CALL "USERID" is now supported. Note: BATCH-USERID setting under G8WB-DEFAULTS in G8WB.CFG is used both for batch and TP. o COBOL: A numeric literal with period, ex. 1.23, is accepted by GCOS even if DECIMAL-POINT IS COMMA. Such literals are now accepted by G8WB. o TP8: The DSA-MODEL field is now available in TP-STORAGE, and set on the basis of TERMINAL-EMULATION configuration. Following value are possible: 8243 = VIP7700 8254 = VIP7804 8257 = DKU7107 8289 = IBM3270 8352 = BROWSER (WEB8 or GTEA) 8214 = TTY (VT) BROWSER is now accepted as setting for TERMINAL-EMULATION and this automatically implies REMOTE. o G8WFL: EBCDIC-SIGN setting is now retrieved from BSF file, instead of PREP.CFG. ============== UPDATE V1.4.48 ============== Errors fixed in this update --------------------------- o COBOL: A CALL with "BY CONTENT" before the first argument was not preprocessed correctly. o TP: The execution trace of TPRs failed to show the first tpr of a transaction. o IDS-II Load: When host load is performed TYPE=RECORDS or SETS, the unload file is transferred as text (UFT or FTP), the load program could not recognize the file format. Note: Load program must be regenerated for this fix to become effective. o Dispatch8: When printing multiple reports via a single Print function, the print spool file was not initialized, and excess copies of reports were printed. o Dispatch8: Character-Set-Adjustment is now ignored as default, i.e. PC character-set used for printing. A new option in D8.CFG may be used to enable CSA, ex. [DEFAULT-SECTION] CSA-ACTIVE : ON ; OFF(default)/ON o Schema: For translate with separate SDM file, the GUI dialog- box would show SDM file after a translate. This could load to confusing if translate was repeated. o Copy import: Failed to create a new library-tag in COPYMAP.CFG. o Dispatch8: The S(erve) function could not handle midnight rollover. o Schema: The schema configuration file $g8wbddir\schema\nnschs.cfg was incorrectly overridden after a translate/validate. Improvements in this update --------------------------- o COBOL and Virtual-C: The $G8WBGDIR\SITE\COBOLTOC directory provides documetation and an example of how to integrate and interface with virtual-C subroutines. o COBOL and Fortran-77: The $G8WBGDIR\SITE\COBOLTOF directory provides documetation and an example of how to integrate and interface with Fortran-77 subroutines and TPRs. 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 Source Import: A new _Backup argument may be used to backup current source (BAK) before import (it also implies _Force). o Source Import: A new _X argument may be used to suppress CHARACTER-SET-ADJUST setting. o Source Export: A new _X argument may be used to suppress CHARACTER-SET-ADJUST setting. o Copy Import: A new _Backup argument may be used to backup current copy (BAK) before import (it also implies _Force). o Copy Import: A new _X argument may be used to suppress CHARACTER-SET-ADJUST setting. o Copy Export: A new _X argument may be used to suppress CHARACTER-SET-ADJUST setting. o IDS-II Unload: A new tag [OWN-TEHDU] may now be used to insert procedure logic to be executed at termination of nnHDBU host unload program, ex. additional statistics. o GUI: The 'Utility continue' check-box is now unchecked as default. o Source Checkin: ANS85 may be now specified as compile-type. o Source Checkin: When compile-type is specified, a check/ generate is now run even if the program has not been changed (cancelled checkout). 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: WB W8 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. G8WB 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 W8TPC 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 G8WBLDIR: The setting for G8WBLDIR may be changed on-the-fly, ex. /c:\temp (specific path) /. (current path) o Re-hosting: G8WB may now be used to test GCOS applications for rehosting with GCOS8 Rehosting Workbench (G8RHB). The SQL-IMPLEMENTATION of DBMS.CFG may be used to enable IDS-II re-hosting via SQL database systems, ex. Informix. When enabled, schema validation will automatically generate SQL script files for creation/deletion of IDS-II database. The Generate SQL function is now also available as a seperate function in the Schema menu. For Batch applications a special run/animate technique is used, which require the application program is launched via W8LQ. The Char menu's are automatically changed to use this technique, whereas GUI tools/action now include new Run/Animate RHB entries. W8LQ launcher accepts the following command line arguments: programname [normal|exclusive|nolog|auto|query|nodb] [cbl85|cbl74] [=outfilename] Programname: The programname or filename of the application program. Databasemode: May be used to control access to the database, if applicable. This feature is primarily provided for G8RHB use. The default is normal. Nodb = database not used by program For SQL implementation Exclusive = lock database and perform auto-commit Nolog = access database without logging (exclusive) Auto = access database with auto-commit Query = access database with query For non-SQL implementation Exclusive = access database without Integrity (FS2) Nolog = access database without Integrity (FS2) Auto = ignored (like Normal) Query = ignored (like Normal) Environment: The execution environment for COBOL-85 or COBOL-74 is now preloaded. The default is cbl85. Redirect: The log may now be redirected to a file. The default is $g8wbldir\BATCH.LOG. ============== UPDATE V1.4.47 ============== o Tips and Hints has been updated, ref. below. Errors fixed in this update --------------------------- o WEB8: The CGIG8WBx programs no longer use a window. o WEB8: When an EMI send is forced due to buffer overflow, and ETX character would be included in the message sent to the Web server. ETX(s) are now removed by the CGIG8WBx programs. Note: The updated programs $g8wbgdir\web8\cgi\CGIG8WBL.EXE and CGIG8WBN.EXE must be copied to your web server (cgi-bin or scripts), see WEB8.DOC for details. o Dispatch8: The S(erve) function did not clear the spool file, when a network printer was configured. This would cause duplicate reports to be printed. o IDS-II: FIND ... RETAINING did not raise proper db-exception, ex. end-of-set or end-of-realm. o Interactive IDS-II: FIND ... RETAINING did raise proper db- exception (see problem above), however, the RETAINING clause was carried over to the next DML verb, and could lead to a subsequent currency problem, ex. 0503100. o WEB8: When importing HTML files, G8WB would truncate lines longer than 250 characters. o WEB8: The CGIG8WB program, which is launched by Personal/Internet Server, would abort if application was sending HTML lines longer than 512 characters. Note: The updated program $g8wbgdir\web8\cgi\CGIG8WB.EXE must be copied to your web server (cgi-bin or scripts), see WEB8.DOC for details. Improvements in this update --------------------------- 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 RFV: Type=2 (Sort) function has been implemented in RFVCXPP. 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). ============== UPDATE V1.4.46 ============== o Limitations has been updated, ref. below. Errors fixed in this update --------------------------- o DBWFL: The fix to accept CR and/or LF as data within a record introduced in v1.4.44, would cause problems for nnHBDU programs converted to upper-case or unload-files being converted to upper-case. Also the last record could be lost, if unload-file use on LF as delimiter. Note: Unload/Load programs must be regenerated for this change to become effective for a schema. o IDS-II: If a DML verb, ex. FINISH, is last in a copy and the verb is terminated with a period in the main source, the DML logic could be inserted after and not before the period, and thus change logic of the program. o RFM/SQL: An END-EXEC with period termination on a separate source line and just in front of a label, would cause a missing period, and in most instances trigger error flagging. o RFM/SQL: A Host variable starting with decimal point, ex. PIC V99, would not be adapted for XDB and cause field to be flagged. o WEB8: All header and environment fields are in upper-case for G8WB, and field name(s) are now converted to upper-case by G8WB. o COBOL: The syntax 'SET field TO true' would incorrectly be flagged (problem introduced with v1.4.45). Improvements in this update --------------------------- 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 ============== UPDATE V1.4.45 ============== o Limitations has been updated, ref. below. Errors fixed in this update --------------------------- o Installation: If manual installation has been used for MFWB, and MFENV32 setting is not done through Registry, then G8WB instal- lation would fail. This has been changed, so G8WB installation can work with MFENV32 environment setting by others means than registry. o Installation: For NON-KEYED version of G8WB, an update instal- lation would incorrectly attempt to install Sentinel key software (no harm done, merely confusing). o Installation: For G8WB update installation, SAMPLES would be selected, even if SAMPLES was deselected during G8WB installation. o Terminal Emulation: The TNVIP interface did not work correctly with VTD-Amaril. o Pilspraak: The command _N did not work correctly (wrong cursor placement). o RFM: XDB Preprocessor would fail if parts of an SQL statement was within a COPY, ex. exec sql select * into copy Fcourse. from course end-exec G8WB has been changed to prevent XDB from seeing the COPY, and thus process the statement correctly. Note: The content of the COPY is not visible during animation, and animator will position to first line after copy instead of exec sql. Note: Copy syntax MUST be terminated with period. o RFM: The value of SQL-MSG-LENGTH did not always reflect the value of SQL-ERROR-MESSAGE (zero instead of length). o COBOL: Mnemonic names defined in SPECIAL-NAMES were limited to 20 characters (use of name flagged if longer). o COBOL: The syntax 'BY CONTENT' in a CALL statement would be flagged, if preceeded by a 'normal' call argument. o PSM: Overpunch field type - format OnT or OnL where n = 1-18, is now supported (undocumented feature of PSM). o Copy/Source Import: The CIMP and SIMP commands did not show results/errors in the text window. o DBWFL: Handling of UFT/FTP unload files (text format) would not accept CR or LF characters as data within a record, and treat these as record delimiters. The remaining data would cause an error - Record type invalid, and load operation would be stopped. DBWFL will now accept CR and LF characters as data, and the error for Record type invalid has been changed to a warning, so load operation is continued. Note: Unload/Load programs must be regenerated for this change to become effective for a schema. o Batch Support: 'View SYSOUT' function (GUI) did not recognize generic mapping of SYSOUT. o TP Support: 'View SYSOUT' function (GUI) did not recognize generic mapping of SYSOUT. o TP: Send in edit-mode failed to insert a trailer in the message for an EGI send. The trailer consists of a CR and a LF, unless advancing BEFORE is specified. o COBOL: Preprocessor will give a warning 'W-8504 Period missing at end of level' if no period was specified after a field definition in Data Division. If the syntax was ending with '... VALUE "..."', the following level number would be lost an cause a fatal error. o COBOL: The error 'E-1007 VALUE literal size > data size. Literal truncated' was not GCOS compatible, and has been changed to a warning accordingly. o Source/COBOL-85: The Source Import, Export, Create functions and Preprocessor has been changed to support program names longer than 8 characters. o Subschema: The subschema translation utility could abort, if a non-existing record was referenced. o Subschema: If automatic subschema configuration failed, i.e. duplicate short name, this was reported as a syntax error. To avoid confusion, the translation is now aborted and a more detailed error message is given. o Schema: If a schema is removed from DBMS.CFG, the schema number could be re-used when translating a 'new' schema, and translate would incorrectly sense a previous version of the schema (simply files left over). Such 'old' files are now removed, when auto- configuration of a new schema takes place. o COBOL: G8WB preprocessing of STOP RUN clause could cause problems due to a missing END-IF in syntax inserted before the clause, ex. IF condition STOP RUN END-IF MOVE ... <--- not executed due to missing END-IF Improvements in this update --------------------------- o TP/TNVIP: The command $BYE is treated as $TERM when connection to TP is done trough terminal emulation software, ex. GLINK. o RFM/COBOL: G8WB now support dynamic SQL with a few limitations. PREPARE/EXECUTE IMMEDIATE ------------------------- The Host Variable holding the SQL syntax is not compatible with GCOS. G8WB has been changed to accomodate this, however, currently you need to include a G8WB directive in the source, whenever PREPARE or EXECUTE IMMEDIATE is used with a Host Variable, ex. EXEC SQL BEGIN DECLARE SECTION END-EXEC 01 ws-dynstmnt PIC x(512). EXEC SQL END DECLARE SECTION END-EXEC *w8prep :ws-dynstmnt EXEC SQL PREPARE dynstmnt FROM :ws-dynstmnt END-EXEC *w8prep :ws-dynstmnt EXEC SQL EXECUTE IMMEDIATE :ws-dynstmnt END-EXEC The G8WB directive, which must be placed before EXEC SQL, tell G8WB Preprocessor that the following SQL syntax makes a reference to the Host Variable ':ws-dynstmnt', and trigger insert of two lines in front of the statement and replacement of the name in the statment, ex. MOVE ws-dynstmnt TO w8dynhvarv MOVE LENGTH of ws-dynstmnt TO w8dynhvarl EXEC SQL PREPARE dynstmnt FROM :w8dynhvar END-EXEC The definition of W8DYNHVAR is automatically included in WS Section. Note: If the G8WB directive is not specified, the XDB error message 'E-WB135 Host Variable type mismatch' is given. DELETE ------ The word 'FROM' must be specified (not optional). INSERT ------ The word 'INTO' must be specified (not optional). EXECUTE IMMEDIATE ----------------- 'USING' clause is ONLY supported for EXECUTE (not IMMEDIATE). SQLDA ----- The layout of SQLDA is not fully GCOS compatible, and special care must be taken depending on how SQLDA is used. When defining SQLDA yourself (not using INCLUDE SQLDA): - the length for name is not present with XDB, ex. 03 SQLNAME. *w8prep gcos8 49 SQLNAMEL COMP-7. *w8prep on 49 SQLNAMEC PIC X(30). - include G8WB directives for declare, ex. *w8prep declare 01 SQLDA. ... *w8prep end The SQLTYPE field values are not GCOS compatible, and conditional coding must be used if your application manipulate SQLTYPE. Depeding on SQLTYPE value, the SQLLEN field may NOT be GCOS compatible. o RFM/COBOL: XDB require numeric host variables to be signed COMP-3. This is not GCOS compatible, however G8WB Preprocessor will auto- matically adapt host variables during checking. If host variables are moved as part of group, the automatic adaption to COMP-3 will cause problems, ex. exec sql begin declare section end-exec 01 host-variables. 05 hv-field1 pic 9(8). exec sql end declare section end-exec 01 ws-variables. 05 ws-field1 pic 9(8). move host-variables to ws-variables (does not work) A new G8WB source directive may be used to trigger special numeric field adaption similar to host variables, ex. *w8prep declare 01 ws-variables. 05 ws-field1 pic 9(8). *w8prep end move host-variables to ws-variables (does work) Note: When defining SQLDA yourself (not using INCLUDE SQLCA), you must include G8WB directives for declare, ex. *w8prep declare 01 SQLCA. ... *w8prep end o COBOL-85: The "X9ST$EXIT_DOMAIN" service call is now recognized and treated like 'EXIT PROGRAM'. o Source Import: The name of a source may now be retrieved from PROGRAM-ID during import. The new feature is configured through a new keyword in G8WB.CFG. [G8WB-DEFAULTS] SOURCE-IMPORT-ID : ON/OFF ; Default OFF o Source Import/Export: The insertion/removal of G8WB header lines may now be configured through new keywords in G8WB.CFG. [G8WB-DEFAULTS] SOURCE-IMPORT-COMMENT : ON/OFF ; Default ON (Insert header) SOURCE-EXPORT-COMMENT : ON/OFF ; Default OFF (Remove header) Note: Import setting will also impact 'Create Source' and 'Source Checkin' functions. o Copy Import/Export: The insertion/removal of G8WB header line may now be configured through new keywords in G8WB.CFG. [G8WB-DEFAULTS] COPY-IMPORT-COMMENT : ON/OFF ; Default ON (Insert header) COPY-EXPORT-COMMENT : ON/OFF ; Default OFF (Remove header) Note: Import setting will also impact 'Create Copy' and 'Copy Checkin' functions. ============== UPDATE V1.4.43 ============== Errors fixed in this update --------------------------- o DISPATCH8: Direct print to a device ex. LPT1: does not work under Windows 98. Physical printer configuration may now specify a network-name for the printer, and print is then routed through Windows Spooler. Example of D8.CFG configuration: [PRINTER-SECTION] ; Physical Printer(xx) FF-Code CC-Code Device Comments A1 : 50 50 LPT1: A2 : 50 50 =c:\pfile.dat A3 : 50 50 \\ps1\laser1 o Forms: The 'modify' panel in the Screen-Painter did not react to COLOR configuration. o DIMS8: Forms configured in DD-CACHE of DIMS8.CFG did not work correctly (fields missing or incorrect). o IDS-II: An ERASE could lead to failure, if the erased record was not current for the set and the currency for the set was having erased record as prior pointer. o IDS-II: A MODIFY (of set membership) could lead to incorrect set pointers, if the currency for the set was having current record as either prior or next pointer, and set has 'insertion next'. o Forms: The FFCIN and FFCOUT commands were missing from the W8 command file. o TP8: When TP8 attempted load of a TPR with an all numeric name, ex. 602, a run-time error was reported and TP8 was stopped. This behavior has been changed so the transaction is aborted with X01 abort-code. o TP8: When returning from CALL ".ILINK", G8WB would have restored NEXT-TPR value. This behavior is not GCOS compatible and NEXT-TPR will now contain low-value after execution of .ILINK. o Pilspraak: If was filled for a form, the title information would be exported as a comment line. The syntax would, however, overflow column 72, and would be flagged with an error if the form was later imported. o RFV CXPP: Type = 21 with Function = 1 (only called from virtual TPR) was not implemented. o RFV CXAP: The field TXS-MARKOR-POS and TXS-FORSTA-FALT-POS were incorrectly filled with a binary cursor. The cursor information is now given in the format llcc. Receive procedure 126 did not always setup the screen image correctly (line 1 placed in line 2 etc.). Improvements in this update --------------------------- o CHAR Editor: When WBW is used to start CHAR version, and default embedded editor is used, Animator2 will be launched for most embedded editor calls. A new configuration in G8WB.CFG may be used to force call of CHAR Editor instead, ex. [G8WB-DEFAULTS] USER-CHAR-EDITOR : ON ; Force use of MF CHAR Editor ============== UPDATE V1.4.42 ============== o Tips and Hints has been updated, ref. below. o Limitations has been updated, ref. below. Errors fixed in this update --------------------------- o DBWFL: Own coding, which is preprocessed for WDBUnn and WDBLnn, would use preprocessor directives under [HDBU-INIT]. This has been changed so PREP.CFG settings for COMP-36-BIT-SUPPORT and DB-KEY-36-BIT-SUPPORT are used as default. A new tag in the nnSCHS.CFG file may be used to explicitly give directives for such embedded preprocessing, ex. [WDBX-INIT] *set>g8wb comp-36-bit-support:force o SQL: A cursor name may contain a hyphen, however this flagged as default by G8WB. Change XDB entry in PREP.CFG as follows to allow hyphen in cursor name: XDB : "VALIDATE HYPHEN" o SQL: A host variable with underscore in the name would not be preprocessed correctly, and cause flagging by XDB. o SQL: An EXEC SQL DECLARE ... END-EXEC statement followed by a label would cause incorrect flagging (label treated as data-name). o IDS-II: Calc or Index keys would be truncated if BINARY field(s) were part of the key (Maximum key size not calculate correctly). This could lead to unexpected 'duplicate' exception when storing/ loading records. Note: Schema must be translated and validated to correct this problem. Also, Q2UT must be used to initialize database before running DB load. o Copy: The error 'E-8074 Copy File-path too long' is given by G8WB Preprocessor if the path (absolute) for a copy exceeds 57 characters. Since G8WB no longer re-map long copy names, the length of the copy path, ex. F:\appl\copylib\std\my-very-long-copy-member-name-0001.cpy could more easily exceed this limit. Create copy and Import copy functions have been changed, so re-mapping is used when this problem would occur. Note: You need to re-import copies to trigger re-mapping. o Copy: Edit Copy function (GUI) did not allow TP-xxx library-tag. o Source Filter: Apply Source Filter did not work for copies with long (>8 chars) names. Improvements in this update --------------------------- o Terminal Emulation: 'Real' Terminal Emulators may now be used with G8WB, 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 G8WB terminal emulators are used. When REMOTE interface is specified, the Open-Client-Interface is used. TNVIP/TN3270 ------------ When TNVIP or TN3270 is specified, G8WB 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. G8WB will attempt to negotiate a terminal model, and if this fails or the terminal model is not recognizable, the G8WB emulation configuration will be used. The G8WB 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 G8WB escape menu $ESC - request G8WB 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, G8WB may present itself as a DSA Node in your network and allow a DSA session (direct or through DNS) to be established with G8WB. 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 $g8wbgdir\site\client\g8wbotc.doc for details. o Advanced Organisor: The Check and Batch Check functions will no longer show a 'Completion' window. o Source import: When '_Force' option is used, an override action will now: If Checked out - remove LCK (disable checkin) If Changed - backup current source (name.BAK) Document override action Note: For an automated import environment, where '_Force' is used as default, accidential overwrite is not possible and modified source can be recovered. o Copy import: When '_Force' option is used, an override action will now: If Checked out - remove LCK (disable checkin) If Changed - backup current copy (name.BAK) Document override action o Source Checkin: A new option 'Cancel Checkout' may be used to cancel a checkout and disgard any changes made. For command operation a new argument '_Cancel' or '_A' may be used to request cancel checkout. o Copy Checkin: A new option 'Cancel Checkout' may be used to cancel a checkout and disgard any changes made. For command operation a new argument '_Cancel' or '_A' may be used to request cancel checkout. o RFM: Change Location will now verify for presence of XDB structure for the requested location, and refuse change if not present. o RFM: Restore Database will now verify for presence of XDB structure for the requested location, and refuse restore if not present. Note: A Location must be created, before you can restore from a backup-set. ============== UPDATE V1.4.41 ============== Errors fixed in this update --------------------------- o WEB8: DOCS will now include ".../docs" in BASE HREF, to be compatible with GCOS 8. o WEB8: The HTML_BASE function was missing. o WEB8: Problem with re-launch of Forms after TP session. o WEB8: Problem with Opera browser. o WEB8: Problem with use of other than port 80. Improvements in this update --------------------------- 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 G8WB. Refer to $g8wbgdir\site\client\g8wbotc.doc for details. ============== UPDATE V1.4.40 ============== o New base release for 32-bit environment. ===================== DOCUMENTATION CHANGES ===================== o Please refer to Release Notes. ============ TIPS & HINTS ============ o Batch: By default output (SYSOUT) from DISPLAY is limited to 132 characters and input (SYSIN) for ACCEPT is limited to 80 characters. Any excess characters are truncated. This behavior is triggered by SYSIN directive, which is used by G8WB to direct ACCEPT/DISPLAY to work with SYSIN/SYSOUT files, however it is possible to raise this limit through use of other directives, ex. INDD OUTDD"SYSOUT 2048" Above directives will raise DISPLAY limit to 2048 characters or INDD"SYSIN 256" OUTDD Above directives will raise ACCEPT limit to 256 characters The INDD and OUTDD may be placed in $g8wbdir\mfi\usercbl7.dir and/or $g8wbdir\mfi\usercbl8.dir to override the standard SYSIN directive. o COBOL-SQL: Although BEGIN/END DECLARE is intended to surround only host variables, GCOS will allow the entire Working-Storage between BEGIN/END DECLARE. Since G8WB is adapting numeric host variables and use BEGIN/END DECLARE to trigger such adaption, you should restrict BEGIN/END DECLARE to include ONLY host variables, otherwise this can trigger both compilation errors, or compatibility problems for numeric fields during execution. o Windows 2000: If you have problems installing MFWB under Windows 2000, we recommend using the 'manual' installation procedure (ref. Release Notes for details) using a previous MFWB installation under Windows 9X, ME or NT. o GFRC Text files: When creating GFRC text files, non-printable characters (less than octal 037) are prefixed with an escape character (NULL), so no data is lost. If the text file is to be processed elsewhere, you can use the run-time switch -N to disable use of escape character, i.e. COBSW=-N%COBSW%. o Binary File-transfer: FTP, unlike UFT, support true binary file transfer, so CPAC is not required if you are using FTP to transfer UFAS/GFRC files for conversion with G8WFL. o SRCH: If SRCH option of COBOL-85 is used for resolving of COPY on GCOS, the following technique(s) can be used to achive similar results within G8WB. a) Import copies as $$SELECT source type, or transfer each copy manually (remember to use CPY extension). b) Configure [.L] library in COPYMAP.CFG with the path or path where copy files has been placed. The .L configuration is used for all COPY syntax without 'OFF ..'. c) Or, use COBCPY setting to trigger scan of path or paths where copy files has been placed. A search via COBCPY is done for all COPY syntax, if the copy cannot be found through COPYMAP.CFG configuration. o MFEXTMAP: The number of entries in MFEXTMAP.DAT can severily impact startup performance of Workbench functions, and it is recommended to work with multiple/smaller MFEXTMAP.DAT files. o DateWarp: Be careful when using DateWarp to change the date, because the date change will be applied to the entire COBOL environment. Since G8WB functions are implemented in COBOL, all such functions will use the changed date, ex. - Date-stamp for compile (checked against schema/subschema) - Backup-set date-time stamp - etc. Note: To test applications with a differenty date and/or time, use CURRENT-DATE, CURRENT-DAY and CURRENT-TIME configuration in G8WB default configuration, since this will ONLY affect ACCEPT DATE/DAY/TIME. o GUI: G8WB functions are grouped into Batch Support, TP Support, Source Administration, IDS-II and INTEREL/RFM Tools, however, most G8WB functions are also defined as separate actions and may thus be included in popup action menus as required. Following is a list of G8WB functions and the related 're-use' arguments. A 're-use' argument, ex. $schema$, may be used to setup previous used value as default. W8L Launcher ------------ Most functions use the common W8L launcher program, where actions are setup as follows: Program = $g8wblbr\g8wb.lbr\W8L.GNT Command line = (see following) Library = COBCLI.LBR IDS-II Database Backup /d W8DBBCK $schema$ $backup-set$ IDS-II Database Restore /d W8DBRES $schema$ $backup-set$ IDS-II Utility /d W8Q2UT $schema$ $function$ IDS-II Translate Schema /d W8TSCH $schema-file$ IDS-II Validate Schema (re-use current version) /d W8VSCH $schema$ _R IDS-II View Schema /d W8WSCH $schema$ IDS-II Translate Subschema /d W8TSSCH $subschema-file$ IDS-II Validate Subschema /d W8VSSCH $subschema$ IDS-II View Subschema /d W8WSSCH $subschema$ IDS-II Generate IIDS Record Panels /d W8DBDSS $subschema$ IDS-II Generate Unload/Load programs /d W8DBWFL $schema$ _U $subschema$ IDS-II Unload Database /d W8USCH $schema$ $db-file$ IDS-II Load Database /d W8LSCH $schema$ $db-file$ Edit Copy /d W8CEDT $copy-member$ $library-tag$ Create/Register Copy /d W8CCRE $copy-member$ $library-tag$ Checkout Copy /d W8CCOUT $copy-member$ $library-tag$ Checkin Copy /d W8CCIN $copy-member$ $library-tag$ Import Copy /d W8CIMP $copy-file$ $library-tag$ Export Copy /d W8CEXP $copy-file$ $library-tag$ Checkout Source /d W8SCOUT $program$ $ref-dir$ Checkin Source /d W8SCIN $program$ $ref-dir$ Create/Register Source /d W8SCRE $program$ $gcos-file$ $ref-dir$ Import Source /d W8SIMP $source-file$ $ref-dir$ Export Source /d W8SIMP $source-file$ $ref-dir$ GCOS 8 File Conversion /b /d W8G8WFL $profile$ $input-file$ $output-file$ PSM Sort /d W8PSMEX $psm-file$ Expand Print File /d W8PRCEXP $print-file$ Build Command File /d W8BCF $file-mask$ $skeleton-file$ $command-file$ Process Error Log (Bulk check) /d W8BELOG Delete Error Log (Bulk check) /d W8BELOG _D Build Source Filter /d W8BSFLT Apply Source Filter /d W8ASFLT Other ----- Some functions are launched directely, and actions are setup as follows: Program = $g8wblbr\g8wb.lbr\<program>.GNT Command line = <option> IDS-II Interactive program = W8IIDS.GNT option = -WB View SYSOUT program = W8VSYSO View/Edit MFEXTMAP.DAT program = W8EEXTM View/Edit Program Switch Word program = W8EPSW View Batch/IDS-II Log program = W8LEDIT.GNT option = $g8wbldir\batch.log View TP Journal program = W8LEDIT.GNT option = $g8wbldir\journal.log INTEREL Database Backup program = W8XDBBCK.GNT option = -WB INTEREL Database Restore program = W8XDBRES.GNT option = -WB INTEREL Change Location program = W8XDBLOC.GNT option = -WB INTEREL Create Location program = W8XDBCRE.GNT option = -WB INTEREL Drop Location program = W8XDBDEL.GNT option = -WB INTEREL Setup/Import/Export program = W8XDBIED.GNT option = -WB View Error Log (Bulk check) program = W8LEDIT.GNT option = CERROR.LOG View Info Log (Bulk check) program = W8LEDIT.GNT option = CINFO.LOG Note: Configuration files - Global or Local, may be edited as follows: View/Edit Defaults Configuration (Local) program = W8LEDIT.GNT option = $g8wbldir\g8wb.cfg View/Edit Defaults Configuration (Global) program = W8LEDIT.GNT option = $g8wbgdir\g8wb.cfg o Please refer to Release Notes for further details. ============ KNOWN ERRORS ============ o SETMFENV.BAT: Running the SETMFENV.BAT command under Windows 98, 98SE and ME could cause the error message "Too many parameters" to occur, whenever the command prompt is launched, or SETMFENV is executed within a DOS prompt. The message actually appear twice. The problem is caused by space in the PATH setting, and you need to modify following files to resolve the problem. c:\install.mf\wbw3.sys : Here you need to put %PATH% between double- quotes, ex. SET PATH=D:\COBOL32\EXEDLL;"%PATH%" c:\windows\setmfenv.bat : Here you need to put %MFPATHENV% between double-quotes, ex. SET PATH="%MFPATHENV%" 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 p1.sysin in1.dat o Please refer to Release Notes for further details. ================= KNOWN LIMITATIONS ================= o COBOL-85: The combination of DISPLAY verb and data-item with dynamic reference modification can lead to incorrect output on SYSOUT. Ex. DISPLAY "Here is a value=" myfield(1:mylength) Above statement will result in a blank line or only myfield being shown. Avoidance: You can get an almost correct result if you split the DISPLAY verb and use ... WITH NO ADVANCING. Ex. DISPLAY "Here is a value=" *w8prep G8WB WITH NO ADVANCING DISPLAY *w8prep myfield(1:mylength) The Char-Editor will show a line-split, where as the GUI-Editor will show a (CR) symbol, where the separation was done. o COBOL: Use of paired parentheses in a WHEN condition for a SEARCH ALL verb can cause incorrect flagging by G8WB, ex. SEARCH ALL ... AT END ... WHEN (field1(indx) = field2) <- flagged WHEN (field2 = field1(indx)) <- not flagged WHEN field1(indx) = field2 <- not flagged Avoidance: Remove parentheses (has no impact on condition) or reverse left/right side of condition. o COBOL-SQL: A cursor used in 'FETCH' verb must have been declared previously in the source, unlike GCOS which only require the 'DECLARE' verb to be present somewhere in the source code. o G8WFL: Files with GBCD codeset cannot be converted by G8WFL, and you need to convert the codeset to ASCII on GCOS, before transfer of file. Note: Within G8WB codeset is ignored, and all files read or written use ASCII codeset. o COBOL: G8WB cannot handle literal continuation if the continuation line starts with an ascii-literal, ex. 05 field value "xxxxxxx - ""31"yyyyy". Avoidance: Adjust literal so the continuation line does NOT start with an ascii-literal, ex. 05 field value "xxxxxx - " "31"yyyyy". o COBOL: GCOS will accept partial zero-supression after the decimal-point, ex. PIC Z.Z9, although documentation says otherwise, and G8WB will flag such syntax. Change syntax for compatibility, ex. PIC Z.99 or Z.ZZ. o COBOL: GCOS default to the first occurence when a subscripted fields is used in ASCENDING clause, however, G8WB requires fields in ASCENDING clause to be elementary without any occurs or subordinate to an occurs. o COBOL-85: GCOS will accept 'RECORD n TO m DEPENDING ...', although documentation says 'RECORD VARYING ...' is required when DEPENDING is used. To obtain compatibility between GCOS and G8WB, use 'RECORD CONTAINS n ...' or 'RECORD VARYING ...'. o COBOL-85: Truncation is not compatible for ACCEPT verb (DATE or TIME). GCOS COBOL-85 will right truncate always, whereas GCOS COBOL-74 and G8WB COBOL-74/85 will left truncate numeric fields and right truncate alphanumeric fields. Note: GCOS COBOL-74 and COBOL-85 is NOT compatible. o COBOL-85: GCOS will give a syntax error if the last verb is not terminated with a period. No flagging is done for COBOL-74 and G8WB likewise. o COBOL: G8WB will accept a numeric field as Record or Alternate key for an Indexed file, although the key field is treated as alpha- numeric. The GCOS compiler will flag such syntax, as only PIC X is allowed for key field(s). o COBOL: G8WB will assume an 'implied' END-IF, when an IF structure is closed via another construct, ex. PERFORM ... IF ... [END-IF] <-- required by GCOS END-PERFORM The GCOS compiler will flag this syntax, as END-IF is required. 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 COBOL: The syntax 'IF (BEST EMPTY) ...', where is an IDS-II set name, is not preprocessed correctly and cause BEST to be flagged. () must be removed from syntax. o Please refer to Release Notes for further details. ================= 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 INTERNET support@bc-solution.com If you have any questions, suggestions for changes and/or improvements, please do not hesitate to let us know. The most recent updates available through INTERNET for download or browsing of update notes. Connect to our web-site 'http://www.bc-solution.com', go to the Support section and select 'GCOS-8 COBOL Workbench 32-bit Update' under Download Software Update. ========================================================================= GCOS-8 COBOL Workbench is a trademark of B & C Solution Sarl. All other trademarks and trade names belong to their respective companies. ========================================================================= Copyright (C) 1992-2001 B & C Solution Sarl. All Rights Reserved.