========================================================================= G C O S 8 M A I N F R A M E E X P R E S S v2.5.05 Windows NT/2000/XP RELEASE ========================================================================= UPDATE NOTES ============ TABLE OF CONTENTS ================= INTRODUCTION ERRORS FIXED IN THIS UPDATE IMPROVEMENTS IN THIS UPDATE DOCUMENTATION CHANGES TIPS & HINTS KNOWN ERRORS KNOWN LIMITATIONS PROBLEM REPORTING INTRODUCTION ============ This update contains fixes to all problems and all new features since release v2.5.01. Previously provided updates are obsolete and no longer required. ============== UPDATE V2.5.05 ============== Improvements in this update --------------------------- o Schema Utilities: The translate and view functions will now open all appropriate source/listing/error files as multiple windows in the MFE8 Editor. o Subschema Utilities: The translate and view functions will now open all appropriate source/listing/error files as mutilple windows in the MFE8 Editor. o Rehosting: A new nnMETA.SQL script is now generated during schema validation. The scripts may be used to create meta information about the IDS-II schema in the target RDBMS. The script will also document db-key usage (minimum, maximum, low, high, available). ============== UPDATE V2.5.04 ============== Errors fixed in this update --------------------------- o IDS-II: The syntax "RESERVE 0 DATA_BASE_KEYS" in DMCL was incorrectly flagged. o Web8: Binary images (GIF, JPEG, etc.) could be corrupted in the embedded CGI solution. o Convert file: An empty UFAS file was not recognized correctly and could cause misleading error messages. o IDS-II: A DB-exception status of xx03100 is now returned, if record currency is missing. Previously xx03200 was returned, however this was not compatible with GCOS. Improvements in this update --------------------------- o Web8: DOCS wil now handle binary images (GIF, JPEG, etc.). o Database load/unload: When you request animated load or unload, the GNT version of the load/unload program had to be deleted under $G8WBDDIR\schema. This would prevent use of INT in the current project. This has been changed so the INT is recognized and the program is animated. o Convert file: Fatal errors in UFAS/GRFC format will now force an EOF, and the file convert up to the point error will be completed. o DATE/TIME: Configuration of Date, Day and Time has been made more flexible. The Default configuration has been changed as follows: SYSTEM-DATE : CURRENT|DYNAMIC|yymmdd ; default current SYSTEM-TIME : CURRENT|DYNAMIC|hhmm[ss[hs]] ; default current Note: SYSTEM-DAY setting no longer exist, instead julian date is derived from system date. For Batch, the DYNAMIC setting will trigger read of the environment variables: GCOS-SYSTEM-DATE GCOS-SYSTEM-TIME the value setting is similar to default configuration. For TP8, the DYNAMIC or an explicit setting will allow date and/or time to be changed through service transaction as follows: $DATE yymmdd $TIME hhmm[ss[hs]] may be used to change the date and/or time during a TP8 session. o File Mapping: A new file mapping technique has been implemented for MFE8 development environment. The MFE8FMAP.DAT is used instead of MFEXTMAP.DAT. The following template is automatically used, when 'File mapping' is launched for a project, which do not already have a mapping file. ; MFE8 File Mapping ; Use TP for generic allocation ; Use BATCH for generic allocation ; Use [programname] for specific allocation (main program only) ; Specific overrides generic ; ; SYSIN = I* ; SYSOUT = P* ; LOG = $$ (batch only) ; ; $MFE8Project may be used to place file under current project ; ; NUL setting can be used to provide empty input file or ; ignore output file ; ; For BATCH, SYSOUT and LOG mapping you may use %programname% to ; produce specific mapping from a generic entry, ex. ; ; SYSOUT=$MFE8Project\DATA\%programname%.OUT.DAT ; LOG=$MFE8Project\DATA\%programname%.LOG.DAT ; [TP] sysin=NUL sysout=$MFE8Project\DATA\SYSOUT.DAT [BATCH] sysin=NUL sysout=$MFE8Project\DATA\SYSOUT.DAT [example1] f1=$MFE8Project\DATA\example1.dat f2=$MFE8Project\DATA\example2.dat The MFE8FMAP.DAT is retrieved from \DATA, or (if found) and $g8wbgdir, during launch of TP or a batch program. File mappings are documented on the journal (batch and TP8). Note: 'View SYSOUT' and 'View LOG' for batch, will use MFE8FMAP.DAT to locate the appropriate file for viewing. o Non-IDSII Index Files: The following enhancements have been implemented to support index files, which are used as database files, but are not included in a schema. General ------- Index files must be allocated through File Mapping like other conventional files. Such mapping is used both for TP8 and Batch when index files are opened. Backup/Restore -------------- You may now create one or more virtual schema's in the IDS-II configuration, and use these for backup/restore operations similar to IDS-II databases. Following example illustrate such virtual schema's (manually added to DBMS.CFG): ; Number Location Location [Perm Concurrent Protect] ; (1-99) Schema files [R/W OFF/ON/FS2 OFF/ON/FULL] [SCHEMA-SECTION] MYSCHEMA : 99 CURRENT $$LOCAL\$G8WBLDIR\DBMS W OFF ON ; INDEX-DB-1 : 81 INDEX-DB $$LOCAL\$G8WBLDIR\DBMS; INDEX-DB-2 : 82 INDEX-DB $$LOCAL\$G8WBLDIR\DBMS; The 'INDEX-DB' setting in 'Location schema' is used indicate a virtual schema. The setting of 'Location files' designate where the index file(s) are located, and you MUST use the following naming convention for the index file(s): nnIDBxxx[.DAT|IDX] where nn = the virtual schema number xxx = an identification of the index file, ex. BTW A backup/restore operation for a virtual schema will thus backup/restore one or more index files to/from a backup-set, like an IDS-II database. Note: You must use backup-sets with 'ZIP' format. TP8 Operation ------------- Index Files are opened by the application as conventional files (OPEN/CLOSE) and a working-storage switch is often used to determine whether a file is already open or not. This technique is supported by MFE8, however you need to consider: - if a TPR or module is cancelled, working-storage values are reset and this could lead to incorrect Open/Close handling MFE8 will cancel a TPR (and any modules called by TPR) if - the TPR aborts - TPR Pooling trigger cancel of TPR The cancel operation may be suppressed by making the TPR and/or module resident. Use CREATE_TPR configuration in TP8.CFG to make one or more TPRs and/or modules resident, ex. [CREATE_TPR] BT008 ... BT970 Abort rollback protection ------------------------- IDS-II databases are automatically allocated and protected in accordance with its configuration in SCHEMA_SECTION, ex. MYSCHEMA is a local single-user database with Abort Rollback protection. You are now able to enable similar protection for Index Files as follows: The program accessing the Index file must be compiled with the following preprocessor directive (inserted in program source), ex. *set>mfe8 index-protect:local IDENTIFICATION DIVISION. PROGRAM-ID. BT960. This diretive will trigger redirection of I/O to FHREDIR (File Share 2), and will amend the clause 'LOCK MODE EXCLUSIVE WITH ROLLBACK' to SELECT clauses with 'ORGANIZATION UFF INDEXED'. The file mapping for the index file must be changed to include the name of the 'local' File Share 2 server, ex. Before: cm=$g8wbldir\dbms\81IDBean.DAT After: cm=$$local\$g8wbldir\dbms\81IDBean.DAT Note: Abort rollback protection will only be effective if both of above measures are applied. o GCOS8 Export: A new utility G8CEXP may be used to collect one or more source-text files for export to MFE8. It's operation is very similar to G8SEXP - the program source export utility. The export file must be imported as 'Import Source' as $$SELECT, so copy members (CPY) are created instead of programs (CBL). The Reference Directory is normally a directory (ex. PrjCopy) under the MFE project, and this must be added as 'Dependency library' in the MFE project, otherwise the cannot be found during compilation. Note: By default, G8CEXP will assume source-text files have TSS line numbers and strip these during export. The source-text file must have APPEND and *END* directives embedded. o GCOS8 Import: Copies may be exported back to GCOS8 using 'Export Source' and a new utility G8CIMP. With 'Export Source' you can export one or more copies, similar to program sources, from the Reference Directory where the copies were imported to. A new utility G8CIMP may be used to import one or more source-text files into the GCOS8 files holding the source-text for each copy. It's operation is very similar to G8SIMP - the program source import utility. Note: By default, G8CIMP will assume source-text files have TSS line numbers and insert these during import. The source-text file will have APPEND and *END* directives embedded. G8CIMP may be configured to include a DELETE directive also. o Expand report files: The default naming for expanded report files has been changed to .Rnn.DAT, and the expanded files are automatically added to the MFE project. o GCOS8 Convert file: You are now able to convert directly to Indexed-sequential file format, from a GCOS8 UFAS Sequential file (Indexed-to-sequential conversion is still required on GCOS8). Key information may either be created interactively, or you may use the GCOS8 utility G8FAB (provided under $g8wbgdir\host) to create a key definition file, and attach this. o GCOS8 Convert file: A new GFRC-text option may be used to convert a text file into a Record-Sequential GFRC file. Note: Default for GFRC files is Record-Sequential, unless you use GFRC-TEXT:ON settings when compiling programs. o GCOS8 Convert file: The converted file is now automatically added to the MFE project. ============== UPDATE V2.5.02 ============== Errors fixed in this update --------------------------- o COBOL: File-codes CF, DE, PF, RF, RH, PH and CH will now have an X appended, ex. CF becomes CFX, to avoid conflict with reserved words (Report Writer syntax). o COBOL: The word "WITH" is now treated as optional in a SEND verb. 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. 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. Improvements in this update --------------------------- o COBOL: Whenever a file-code is adapted, the warning 'W-8525 File- code xxx must be used for mapping' is given. 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, MFE8 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 MFE8, since only one process is used. - before execution of a TPR or module, MFE8 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 MFE8 using a permanent environment setting for the file-code, ex. SET F1=f:\data\file1.dat ===================== DOCUMENTATION CHANGES ===================== o Please refer to Release Notes for further details. ============ TIPS & HINTS ============ o Please refer to Release Notes for further details. ============ KNOWN ERRORS ============ o Please refer to Release Notes for further details. ================= KNOWN LIMITATIONS ================= 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 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 Mainframe Express V2.5 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 Mainframe Express is a trademark 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.