Copyright (C) Fujitsu Siemens Computers GmbH 2005 *3 All rights reserved *3

Transcription

1 Fujitsu Siemens Computers GmbH CRTE (BS2000/OSD) Version 2.4C *4 October 2005 *4 Release Notice Copyright (C) Fujitsu Siemens Computers GmbH 2005 *3 All rights reserved *3

2 Release Notice CRTE V2.4C 1 General Ordering Delivery Documentation Software extensions Technical information Resource requirements Software configuration Product installation Important information regarding upgrades Product use Obsolete functions (and those to be discontinued) Incompatibilities Restrictions Procedure in the event of errors Hardware support

3 1 General The Common Run-Time Environment CRTE V2.4C is the common runtime system for all variants of the following compilers: COBOL85 as of V2.1, COBOL2000 as of V1.0, C and C++ as of V2.1 or C/C++ as of V3.0 in BS2000/OSD-BC as of V4.0 *) or OSD-SVP as of V4.0 and OSD/XC as of V1.0. CRTE comprises language-specific and non-language-specific libraries, e.g. for program linking, mathematics and uniform event and error handling as well as memory and I/O management. The header files of the C and C++ library functions are also part of the CRTE. The CRTE is a software prerequisite for COBOL85, COBOL2000, C and C++ applications and for the above-mentioned versions of the compilers for the languages COBOL, C and C++. CRTE is also a prerequisite for applications with a "foreign" language mix. CRTE also supports the COBOL85, COBOL2000, C and C++ compilers and their applications in POSIX. Some of the CRTE libraries are shareable and can be preloaded as a subsystem. The modules of the C/C++ and COBOL runtime systems and the ILCS are also available as RISC MIPS code for use on systems belonging to the SR2000 family with RISC MIPS architecture. CRTE V2.4C is included there in OSD-SVP as of V4.0. This Release Notice is a summary of the major extensions, requirements and operating information with regard to CRTE V2.4C under the operating systems BS2000/OSD-BC as of V4.0 or OSD-SVP as of V4.0 and OSD-XC as of V1.0. The release level is that of October *4 Customers will receive an updated version of this file should any subsequent changes be made. To print the file, use: /PRINT-FILE FILE-NAME=SYSFGM.CRTE.024.D, - / LAYOUT-CONTROL=PAR(CONTROL-CHARACTERS=EBCDIC) (German) /PRINT-FILE FILE-NAME=SYSFGM.CRTE.024.E, - / LAYOUT-CONTROL=PAR(CONTROL-CHARACTERS=EBCDIC) (English) *) BS2000/OSD (R) is a trademark of Fujitsu Siemens Computers GmbH - 1 -

4 All BS2000 product Release Notices are available in the Internet. This one is available under the following URL: fgm_gr/bs2000/index_gr.htm. If one or more previous versions are skipped when this product version is used, the information from the Release Notices (and README files) of the previous versions must be noted. The use of names, trademarks, etc. in this Release Notice does not entitle readers to assume that these names/ designations may be used without restriction by anyone; often the names/designations are protected by law or contract, even if this is not indicated here. 1.1 Ordering CRTE V2.4C can be purchased from your local distributors and is subject to the general terms and conditions of the software product use and service agreement. CRTE V2.4C is included in OSD-SVP as of V4.0 and OSD/XC as of V1.0 (see section 3.2 "Software configuration" for details). 1.2 Delivery The CRTE V2.4C files are supplied via SOLIS. Delivery components The following delivery components are required, regardless of the hardware type: SINLIB.CRTE.024 SINPRC.CRTE.024 SPULNK.CRTE.024 SPULNK.CRTE.024.COMPL Library for installation in POSIX Library with installation procedures C runtime system including macros (RISC-SPARC) Modules for complete partial bind (RISC-SPARC) - 2 -

5 SPULNK.CRTE.024.CPP-COMPL Modules for complete partial bind of ANSI-C++ programs (RISC-SPARC) SPULNK.CRTE.024.PARTIAL-BIND Modules for standard partial bind (RISC-SPARC) SPULNK.CRTE.024.POSIX SPULNK.CRTE.024.RTSCPP SPULNK.CRTE.024.STDCPP SPULNK.CRTE.024.TIME SPULNK.CRTE.024.TOOLS SRULNK.CRTE.024 SRULNK.CRTE.024.COMPL POSIX link switch (RISC-SPARC) Standard C++ runtime system for C/C++ V3.1 (RISC-SPARC) Standard C++ library for C/C++ V3.1 (RISC-SPARC) Time link switch (RISC-SPARC) C++ library Tools.h++ for C/C++ V3.1 (RISC-SPARC) C/COBOL runtime system including macros (RISC-MIPS) Modules for complete partial bind (RISC-MIPS) SRULNK.CRTE.024.CPP-COMPL Modules for complete partial bind of ANSI-C++ programs (RISC-MIPS) SRULNK.CRTE.024.PARTIAL-BIND Modules for standard partial bind (RISC-MIPS) SRULNK.CRTE.024.POSIX SRULNK.CRTE.024.RTSCPP SRULNK.CRTE.024.STDCPP SRULNK.CRTE.024.TIME SRULNK.CRTE.024.TOOLS SYSFGM.CRTE.024.D SYSFGM.CRTE.024.E SYSLIB.CRTE.024 SYSLIB.CRTE.024.CPP SYSLNK.CRTE.024 POSIX link switch (RISC-MIPS) Standard C++ runtime system for C/C++ as of V3.0 (RISC-MIPS) Standard C++ library for C/C++ as of V3.0 (RISC-MIPS) Time link switch (RISC-MIPS) C++ library Tools.h++ for C/C++ as of V3.0 (RISC-MIPS) Release Notice (German) Release Notice (English) Header and macros for C, C++, Tools.h++ Header and macros for C++ Cfront mode C/COBOL runtime system including macros - 3 -

6 SYSLNK.CRTE.024.CFCPP SYSLNK.CRTE.024.COMPL SYSLNK.CRTE.024.COMPV1 SYSLNK.CRTE.024.COMPV2 SYSLNK.CRTE.024.CPP Macro/module library for C/C++ compiler as of V3.0B (Cfront) Modules for complete partial bind Compatibility library C V1.0 Compatibility library C V2.0 Macro/module library for C++ compiler as of V2.1 (Cfront) SYSLNK.CRTE.024.CPP-COMPL Modules for complete partial bind of ANSI-C++ programs SYSLNK.CRTE.024.PARTIAL-BIND Modules for standard partial bind SYSLNK.CRTE.024.POSIX SYSLNK.CRTE.024.RTSCPP SYSLNK.CRTE.024.SHARE SYSLNK.CRTE.024.STDCPP SYSLNK.CRTE.024.TIME SYSLNK.CRTE.024.TOOLS SYSRME.CRTE.024.D SYSRME.CRTE.024.E POSIX link switch Standard C++ runtime system for C/C++ as of V3.0 Shareable components Standard C++ library for C/C++ as of V3.0 Time link switch C++ library Tools.h++ for C/C++ as of V3.0 README file (German) README file (English) SYSSSC.CRTE.024.C Subsystem declarations SYSSSC.CRTE.024.C.LOW (CRTEC) SYSSSC.CRTE.024.COBOL Subsystem declarations SYSSSC.CRTE.024.COBOL.LOW (CRTECOB) SYSSSC.CRTE.024.COB-PART Subsystem declarations SYSSSC.CRTE.024.COB-PART.LOW (COBPART) SYSSSC.CRTE.024.PARTIAL Subsystem declarations SYSSSC.CRTE.024.PARTIAL.LOW (CRTEPART) SYSSSC.CRTE.024.SIS SYSSSC.CRTE.024.SIS.LOW SYSSII.CRTE.024 Subsystem declarations (CRTESIS) IMON information file The files identified with RISC-MIPS can only be used for producing applications for SR2000 hardware

7 The files identified with RISC-SPARC can only be used for producing applications for SPARC64 hardware. Their use is not generally released. The following delivery components are only required on SPARC64 hardware: SPUSSC.CRTE.024.PARTIAL Subsystem declarations SPUSSC.CRTE.024.PARTIAL.LOW (CRTEPARP) The following delivery components are only required on SR2000 hardware: SRUSSC.CRTE.024.COB-PART Subsystem declarations SRUSSC.CRTE.024.COB-PART.LOW (COBPARR) SRUSSC.CRTE.024.PARTIAL Subsystem declarations SRUSSC.CRTE.024.PARTIAL.LOW (CRTEPARR) POSIX-HEADER and the message files for CRTE are component parts of BS2000/OSD-BC, OSD-SVP and OSD/XC (see section 3.2 "Software configuration" for details). The current file and volume characteristics are listed in the SOLIS2 delivery cover letter. 1.3 Documentation The following manual is needed for operating CRTE (BS2000/OSD) V2.4C: Title! Order number CRTE 2.4A (BS2000/OSD)! U21446-J-Z Benutzerhandbuch!! CRTE 2.4A (BS2000/OSD)! U21446-J-Z User Guide! You will find a description of the language-specific application possibilities in the user guides and in the language reference manuals for the compilers as well as in the descriptions of the C and C++ library functions. You will find a list of the manual order numbers in the Release Notices of the relevant compilers

8 The manual below was produced for the C library functions: Title! Order number C-Bibiliotheksfunktionen V2.6A! U4351-J-Z125-8 Referenzhandbuch!! C Library Functions V2.6A! U4351-J-Z Reference Manual! The following additional manual was produced for the C library functions in POSIX as of CRTE V2.3: Title! Order number C-Bibiliotheksfunktionen V2.5A! U23711-J-Z125-3 fuer POSIX-Anwendungen! (BS2000/OSD)!! C Library Functions V2.5A! U23711-J-Z for POSIX Applications! (BS2000/OSD)! Please also note the following manuals when using the product on systems from the SR2000 model family with RISC MIPS architecture: Title! Order number OSD-SVP V4.0! U25001-J-Z125-4 SR2000 Bedienen/Verwalten!! OSD-SVP V4.0! U25001-J-Z SR2000 Operation/Administration! Please also note the following manuals when using the product on SX systems with RISC SPARC architecture: Title! Order number Business Server! U41272-J-Z385-1 SX130 Bedienen und Verwalten!! Business Server! U41279-J-Z125-1 SX130 Konzepte und Funktionen!! Business Server! U41272-J-Z SX130 Operation/Administration!! OSD/XC V1.0! U41279-J-Z SX130 Concepts and Functions! The manuals of the BS2000/OSD-BC basic configuration are additionally recommended for operating CRTE

9 The documentation is available as online manuals under or can be ordered in printed form against extra cost in the Internet under

10 2 Software extensions CRTE V2.4C contains the following extensions over CRTE V2.4B: New snprintf, vsnprintf and initgroups functions. The new snprintf() and vsnprintf() functions are basically identical to the previous sprintf() and vsprintf() functions. They have an additional buffer limit parameter to prevent buffer overrun. The initgroups() function initializes an additional group access list of the calling process by reading the group database /etc/group and using all groups that the specified user is a member of. You will find further details in the README file. Extension of the getopt function The optopt variable is now supplied with values each time getopt() is called instead of only when an error occurs as previously. This makes it possible to use the question mark as a valid option. You will find further details in the README file

11 3 Technical information 3.1 Resource requirements Depending on the application involved, CRTE V2.4C requires approximately 1 MB of static virtual address space. The files delivered with the product occupy approximately 120,000 PAM pages. Of these, around 44,000 PAM pages are needed just for files to produce RISC MIPS applications for SR2000 systems. 41,000 PAM pages are needed just for files to produce RISC SPARC applications for SPARC64 hardware. On systems from the system family and systems of the SR2000 model range with RISC-MIPS architecture, the latter files can be deleted if it is not intended to generate RISC-SPARC applications. The following space is required in class 4 memory to load the subsystems: CRTEC 1880 KB CRTECOB 210 KB CRTESIS 740 KB CRTEPART 2570 KB CRTEPARR 5940 KB (only for RISC MIPS systems) CRTEPARP 4330 KB (only for RISC SPARC systems) COBPART 160 KB COBPARR 430 KB (only for RISC MIPS systems) All subsystems are loaded by default into the upper 16 MB of class 4 memory. 3.2 Software configuration CRTE V2.4C is released for BS2000/OSD-BC as of V4.0 and is contained in OSD-SVP as of V4.0 and OSD/XC as of V1.0. The POSIX subsystem must be loaded for the CRTE V2.4C POSIX support. POSIX applications produced with CRTE V2.4C require the version of POSIX-BC that is released for the OSD version concerned. The correction levels of correction package III/2002 are required with PLAM >= V3.1A and BINDER >= V2.0B PLAM >= V3.1A is required to process the libraries for supporting the C/C++ compiler as of V3.0 with PLAM resources, as these have secondary names > 32 bytes. BINDER >= V2.0B is required if existing C++ objects as of V3.0 are to be linked with the libraries contained in CRTE V2.4C with C/C++ as of V

12 You will also need the following correction packages of the CRTE-BAS delivery unit: BS2GA.CRTE-BAS V4.0 (ab SOLIS-Aenderungsstand B52), bzw. *4 BS2GA.CRTE-BAS V5.0 (ab SOLIS-Aenderungsstand C52), bzw. *4 BS2GA.CRTE-BAS V6.0 (ab SOLIS-Aenderungsstand C52), bzw. *4 BSVP.CRTE-BAS V4.0 (ab SOLIS-Aenderungsstand B52), bzw. *4 BSVP.CRTE-BAS V4.1 (ab SOLIS-Aenderungsstand B52), bzw. *4 BSVP.CRTE-BAS V4.2 (ab SOLIS-Aenderungsstand B52), bzw. *4 BXC.CRTE-BAS V1.0 (ab SOLIS-Aenderungsstand C52), bzw. *4 BXC.CRTE-BAS V1.1 (ab SOLIS-Aenderungsstand C52), bzw. *4 BXC.CRTE-BAS V1.2 (ab SOLIS-Aenderungsstand A00), bzw. *4 BXC.CRTE-BAS V2.0 (ab SOLIS-Aenderungsstand C52) *4 Among other things, this delivery unit includes release of CRTE-MSG as of V1.4C and POSIX-HEADER as of V1.4C. *4 Please refer to the NFS V3.0 Release Notice for the SOLIS change state of BS2GA.POSIX or BSVP.POSIX required for the new interfaces for supporting NFS V3.0 (see section 2 "Software extensions"). 3.3 Product installation Installation of the product with the installation monitor IMON is mandatory, as execution of the product requires a consistent Software Configuration Inventory (SCI). All the most important information on installing the product is contained in the CRTE V2.4A User Guide. The standard installation in BS2000 is performed using IMON. The inputs needed and the installation process are described in the IMON manual. The standard installation of CRTE in the POSIX file system is then performed using the POSIX installation tool. The following additional types of installation are also described in the manual: - Installation under a non-standard ID - Private installation - Installing the header files and link switches in any POSIX directory Important information regarding upgrades Upgrading from previous CRTE versions: - The headers from an earlier CRTE version installed in POSIX must first be removed. For this, refer to the information in the CRTE V2.4A User Guide

13 - Subsequently, all files from previous CRTE versions can be deleted. - Any preloaded CRTEC, CRTECOB, CRTESIS, CRTEPART, CRTEPARR, COBPART or COBPARR subsystems from a previous version may not be accessed while or after installing CRTE V2.4C. These subsystems should be stopped before CRTE V2.4C is installed, and either replaced by the new version of the subsystem concerned (in the case of a standard installation, IMON automatically generates the appropriate entries in the subsystem catalog) or removed from the subsystem catalog. - There is no equivalent for CRTECOM in CRTE V2.4C. This entry must always be removed from the subsystem catalog. CRTE replaces ILCS. Parallel operation of CRTE and ILCS will result in undefined program behavior. Therefore, you should make note of the following: - You may not access an existing ILCS subsystem while or after installing CRTE V2.4C. ILCS must be stopped and removed from the subsystem catalog before CRTE V2.4C is installed. - If ILCS is supplied with another product, you cannot install this ILCS as long as CRTE is installed. 3.4 Product use The CRTE V2.4A User Guide contains all the main information on using the product. Using the libraries SRULNK.CRTE.PARTIAL-BIND, SRULNK.CRTE or other modules containing RISC MIPS code results in RISC MIPS objects being created. In contrast to /390 objects, such RISC MIPS objects can only run on systems with RISC MIPS processors (SR2000 systems), i.e. they cannot run on other CPUs supported by BS2000/OSD-BC. Note on optional REP A : This optional REP ensures that page 0 is not allocated after ILCS initialization. This REP should only be used in debug operation to detect erroneous access to page Obsolete functions (and those to be discontinued) No functions have been discontinued since CRTE V1.0A. RISC-MIPS code is provided for the last time in version 2.4C

14 3.6 Incompatibilities CRTE V2.4C contains the following incompatibilities to CRTE V02.4B. CRTECOB and CRTEC subsystems As of CRTE V02.4C, the CRTECOB and CRTEC subsystems are loaded into the upper address space by default. This is, in the meantime, common practice for most users. However the subsystem declarations SYSSSC.CRTE.024.COBOL.LOW and SYSSSC.CRTE.024.C.LOW are provided for users that still want to load the CRTECOB and CRTEC subsystems into the lower address space. You will find further details in the README file. Enhancement of support for ASCII environments The compiler option LITERAL-ENCODING can be used to define the coding of strings in a compilation unit. Previously, the strings for parameter passing (argv), environment variables (environ-structure) and the global variable tzname were passed to the main program regardless of this in EBCDIC code. This made continuous processing in ASCII format difficult since the values concerned had to be converted by accessing the source. This behavior has been enhanced in CRTE V02.4C. The new compiler option ENVIRONMENT-ENCODING can be used to control the format in which the program environment is presented. The new compiler option is supported as of CPP V03.1A30. You will find further details in the README file. Moved PTHREAD libraries The libraries and subsystem declarations provided for PTHREAD support have been moved to CRTE-BASYS V01.4C as of CRTE V02.4C. CRTE-BASYS V01.4C is supplied with the basic configuration of the operating system. For this reason, all files named *.CRTE.*.PTH* and the relevant subsystems are deleted from CRTE. 3.7 Restrictions - The libraries (SPULNK...) and subsystems (SPUSSC...) that are supplied exclusively for RISC-SPARC systems, are not released for use. The files can be deleted if necessary (see section 3.1 "Resource requirements" for details). - The functionality implemented for supporting POSIX threads is not generally released. - Compiling the header files supplied with CRTE and POSIX-HEADER with the C/C++ compiler option MODIFY-MODULE-PROPERTIES C-NAMES=*SHORT leads to messages with the error weight warning

15 3.8 Procedure in the event of errors In the event of an error, the following error documentation will be required for diagnostic purposes: - Options, source and error lists with COPY and INCLUDE expansion (LISTING option) - Run log - Source including COPY and INCLUDE elements and if necessary, COSSD - Binder listing - Input/output files - Expected result - Brief description of execution - Product version number - REP files used - CONSLOG - DUMP, if available - Subsystems used

16 4 Hardware support CRTE V2.4C will run on all - XS31 systems of the family, - systems of the SR2000 model family with RISC MIPS architecture - and SX systems with RISC SPARC architecture that are supported by the operating system versions listed in section

17 Information on this document On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Computers. This new subsidiary of Fujitsu has been renamed Fujitsu Technology Solutions. This document from the document archive refers to a product version which was released a considerable time ago or which is no longer marketed. Please note that all company references and copyrights in this document have been legally transferred to Fujitsu Technology Solutions. Contact and support addresses will now be offered by Fujitsu Technology Solutions and have the The Internet pages of Fujitsu Technology Solutions are available at and the user documentation at Copyright Fujitsu Technology Solutions, 2009 Hinweise zum vorliegenden Dokument Zum 1. April 2009 ist Fujitsu Siemens Computers in den alleinigen Besitz von Fujitsu übergegangen. Diese neue Tochtergesellschaft von Fujitsu trägt seitdem den Namen Fujitsu Technology Solutions. Das vorliegende Dokument aus dem Dokumentenarchiv bezieht sich auf eine bereits vor längerer Zeit freigegebene oder nicht mehr im Vertrieb befindliche Produktversion. Bitte beachten Sie, dass alle Firmenbezüge und Copyrights im vorliegenden Dokument rechtlich auf Fujitsu Technology Solutions übergegangen sind. Kontakt- und Supportadressen werden nun von Fujitsu Technology Solutions angeboten und haben die Die Internetseiten von Fujitsu Technology Solutions finden Sie unter und unter finden Sie die Benutzerdokumentation. Copyright Fujitsu Technology Solutions, 2009