Fujitsu Siemens Computers GmbH *2 OSD/XC (BS2000/OSD) Version 2.
Release Notice OSD/XC V2.2A 1 General 1.1 Ordering 1.2 Requirement 1.3 Delivery 1.4 Documentation 1.5 On-site consulting or customer workshop 2 Software extensions 2.1 Support for SPARC64 computer architecture 2.2 X2000 Carrier System based on Solaris V8 2.3 I/O connectivity 2.4 SX servers partitioning concept 2.5 Dynamic systemboard reconfiguration (DR) on SX150 server 2.6 PCI hot plug on SX150 server 2.7 Capacity on demand on SX150 servers 2.8 Disk sharing with S-systems 2.9 MIN-MEMORY-SIZE on SX150 2.
4.5 Magnetic tape devices 4.5.1 Supported magnetic tape devices 4.5.2 Discontinued support 4.6 Printers 4.6.1 Supported channel printers 4.6.2 Discontinued support 4.7 Channel adapters 4.7.1 Channel adapters 4.7.2 Discontinued support 4.8 Fibre channel switches 4.9 Other peripherals 4.9.1 Supported special devices 4.9.
1 General The OSD Extended Configuration (OSD/XC) V2.2A is the BS2000/OSD-BC V6.0B*) operating system whose functionality has been extended with additional system level software products for the SPARC64-based servers in the SX series (SX servers). This Release Notice is a summary of the major extensions, dependencies and operating information with respect to the delivery components of the OSD/XC V2.2A package that are contained in the following technical delivery units: 'BXC.APACHE V2.2' 'BXC.CRTE-BAS V2.
The information in the Release Notices SYSFGM.BS2OSD.060.E and SYSFGM.BS2XC.021.E with the functional enhancements with correction package 1/2007 must be noted. These Release Notices contain the basic information for OSD/XC 2.2A. This Release Notice describes additional information and functional enhancements. All BS2000 product Release Notices are available in the Internet under the following URL: http://manuals.fujitsu-siemens.
The delivery of OSD/XC V2.2A contains a checklist for changing from OSD/XC V1.* to OSD/XC V2.2A. X2000 V3.0 ordering information for customers with SX servers: X2000 V3.0 has been available since September 2004 for upgrades. Automatic delivery will commence in 2006 to SX server customers with hardware maintenance contracts, as part of the basic software update. Installation of the new X2000 version must be requested from servicing.
GSMAN HELGA IDIAS INIT IOCFCOPY IOGEN IORM IOTRACE JITSYS JMP JMU JOBSCHED JPPOPT KDCMON LMSCONV LNM MIP MSCFANC MSGMAKER NDMDAMP NKISAM NKISTRAC NKS NKV NLMSERVE PAMCONV PAMINT PASSWORD PCA PTHREADS PVSREN RESLOG RMS SCDM SHOW-FILE SMI SMPGEN-S SMPGEN-U SPCCNTRL SRPMNUC STATUS SYSFILE TANGBAS TANGRAM TPCOMP2 TPRLAM TSOSLNK TULAM UTM-SM2 VOLIN WARTOPT 15.0A 15.0A 15.0A 15.0A 14.0A 15.0B 6.0A 15.0B 3.0A 2.0A 14.0A 15.0A 2.4A 15.0A 3.3B 14.0A 15.0A 15.0A 1.2A 13.0A 15.0B 15.0A 15.0A 15.0B 15.0A 12.1A 6.
BXC.DSSM DSSM ROSI SSCM 4.1A 15.0A 2.3B BXC.EDT *2 EDT 17.0A BXC.HSMS ARCHIVE HSMS HSMS-API 8.0B 8.0B 8.0B BXC.IMON IMON IMON-BAS IMON-GPN IMON-SIC 3.0A 3.0A 2.6A 3.0A BXC.JENV JENV 5.0A BXC.JV JV 14.0C BXC.LLMAM *1 LLMAM 3.3A BXC.LMS LMS 3.3B BXC.ONETSERV BCAM BCAM-DIAG BCAM-GEN CMX DCAM DCM-DIAG IPSEC ONETSERV PLUS PRNGD SOCKETS VTSU-B VTSUTRAC XHCS-SYS 19.0A 1.0A 1.0A 1.3A 13.2A 1.0A 1.1A 3.2A 9.1B 1.0A 2.3A 13.2A 13.1A 2.0A BXC.PERCON PERCON 2.9A BXC.
PLAM PMLOG PMSYS150 3.4A 3.4A 3.4A BXC.POSIX POSIX-ADDON-LIB POSIX-BC POSIX-NSL POSIX-SH POSIX-SOCKETS POSPRRTS 2.1A 6.0A 6.0A 6.0A 6.0A 1.2A BXC.RSO RSO RSOSERVE 3.5A 3.5A BXC.SCA SCA 15.0B BXC.SDF DISPLAY FHS-TPR SDF SDF-CONV SDF-I SDF-P-BASYS SDF-PAR SDF-SFC SDF-SRV SDF-U VAS 1.0B 8.2D 4.6A 3.0B 4.1A 2.4A 1.1A 3.1A 3.0C 4.1F 2.3B BXC.SIR SIR 15.0B BXC.SNMP SNMP-LIGHT 5.0A BXC.SORT SORT 7.9A BXC.SPOOL *2 BS2ZIP PRMMAN PRMPRES SNRTP SPCONV SPOOL SPOOLSYS SPSERVE SPSRVMAN 1.2A 1.3A 1.2A 1.
IPL SLED STRT 15.0B 15.0B 15.0B BXC.TIAM TIAM 13.1C BXC.WTOSD WEBTRANS-OSD 7.1A You will find the delivery components for the separate release units listed in the SOLIS2 delivery cover letter, which also contains the current file and volume characteristics. Since BS2000/OSD-BC V4.0, full message files are no longer supplied. Message files defined in the DSSM catalog are also activated via the MIP parameter file. This makes the help texts available even if the subsystem is not preloaded. 1.
MSGMAKER V1.2A Performance Handbook POSIX Basics POSIX Commands POSIX SOCKETS/XTI PRM V1.2A User Guide SDF V4.5A Introductory Guide SDF V4.5A Management SDF-CONV V3.0A SPOOL V4.6 User Guide SPOOL & Print Commands SPOOL & Print Macros and Exits SPOOL & Print Messages SPSERVE V2.9A User Guide SPCONV V1.0A User Guide SNS V1.
http://manuals.fujitsu-siemens.com. Documentation on the OSD Extended Configuration OSD/XC products TITLE *2 *2 *2 ORDER NUMBER ARCHIVE V6.0A User Guide BCAM V19.0A Volume 1+2 CMX V1.0 CRTE V2.5A User Guide DCAM V11.0A DCAM Programming DCAM Macro Calls User Guide DCAM-COBOL Calls User Guide EDT V16.6A Statements EDT V16.6A Subroutine Interface EDT V16.6A Ready Reference EDT V17.0A Unicode Mode Statements EDT V17.0A Unicode Mode Subroutine Interface EDT Operands Reference Card HSMS/-SV V8.
1.5 On-site consulting or customer workshop On-site consulting or a customer workshop with the following content is offered to provide intensive advice and training: - SX series overview Hardware construction of the SX series business servers, interfaces, control elements and networking of the servers with regard to administration.
2 Software extensions 2.1 Support for SPARC64 computer architecture OSD/XC V2.2A is based on the functionality of BS2000/OSD-BC V6.0B and its software configuration. The BS2000/OSD-BC V6.0B code has been ported to SPARC64 code to provide the best possible performance. BS2000/OSD-BC V6.0B will run as the operating system base of OSD/XC V2.2A, as required on type SX business servers with SPARC64 processors or on business servers with /390 processors. The subsystems of the BS2000/OSD-BC V6.
Partitioning the SX130 model series All SX130 models have a basic configuration with two system boards. These either form one partition with two system boards for the first BS2000/OSD instance or two partitions with one system board each for the first BS2000/OSD instance and the first Solaris instance.
2.6 PCI hot plug on SX150 server On SX150, the PCI boards of a BS2000 partition can be disabled, removed, inserted or enabled during operation. This functionality can be used for changing the configuration or for maintenance (replacing a defective board without rebooting). It can be used for all current PCI boards apart from channel connections. 2.
2.11 Incompatibilities to OSD/XC V1.1A The checks of the ADDRSPACE allocation for an ID have been intensified. They now include beside all class 6 memory pages, also pages in memory pools and data spaces as long as they can be associated with the creator task. If increasing the ADDRSPACE allocation does not suffice, the old behavior of OSD/XC V1.1A can be reinstated with the optional REP correction A0518446-001. 2.12 New Functions in OSD/XC V2.
The consequence of Unicode representation in the work files is that all interfaces that allow the user to access work file records directly cannot be maintained compatible. This applies to the L-Mode subprogram interface, to the @RUN interface and to the IEDTGLE interface in Locate-Mode. Thus you can no more use these interfaces if you want to use the new functions. The compatibility mode offers the full EDT V16.6B function inclusive the old L-Mode subprogram interface.
Performance optimization when SORT is called very often as a subprogram (e.g. more than 10.000 times in a main program) while very few records are sorted (e.g. less than 100). 2.14 Support for new hardware FibreCAT CX3 and LTO-3 FibreCAT CX3 The FibreCAT CX3 is the successor system of the FibreCAT CX500/CX700. LTO-3 LTO-3 drives operation on SX servers is being released as of OSD/XC V2.1 in connection with X2000 V3.0A09 (General release 01.07).
*2 *2 *2 *2 *2 *2 *2 *2 *2 In the current release version, Apache, the world’s most popular web server, is also available for BS2000/OSD, as well as for Windows, Linux, Solaris.With Apache V2.2, the migration to the Apache HTTP Server 2.2.8 of the Apache Software Foundation is complete, with support for PHP V5.2, PERL V5.8, TOMCAT V5.5 instead of JSERV/JSP. APACHE (BS2000/OSD) V2.
3 Technical information 3.1 Resource requirements 3.1.1 Main memory As of X2000 V3.0A the system fixes a model dependent minimal size of the X2000-/Solaris-memory: SX100-B: SX100-B with fibre channel: SX100-C: SX130-10A up to -30C: SX130-40C up to -60C: SX140 up to -20C SX140 as of -30C SX150 up to -50C SX150 60C 512MB 1024MB 1024MB 1024MB 2048MB 1024MB 2048MB 2048MB 3072MB The recommended amount of main memory that is generally also sufficient for VM2000 operation can be found in section 4.1.1.
The version required for use under OSD/XC V2.2A of software products that are not in the OSD Extended Configuration are shown in the following table: Product version --------------------------------ADILOS V6.4 AID V3.0/V3.1/V3.2 ASSEMBH V1.2 C/C++ V3.1 COBOL85 V2.3 COBOL2000 V1.1/V1.2/V1.3/V1.4 COSMOS V15.0 DAB V9.0 DCE V1.0 DPRINT V1.0/V1.1 DRIVE V3.1 DRV V3.0/V3.1 FDDRL V15.0/V16.0 FDDRL-OS V15.0/V16.0 FHS V8.2/V8.3 FOR1 V2.2 GOLEM V9.2 HIPLEX-AF V3.2 HIPLEX-MSCF V4.0 HSMS-SV V8.0 IDOM V1.3 IFG V8.1/V8.
3.3 Product installation Installation of the product with the installation monitor IMON is mandatory. At least IMON V2.8 is required. If IMON V2.8, V2.9 or V3.0 is not already in use on the system, it must be installed first. The installation information provided in the delivery letter and in the manual or Release Notice for each relevant product should be noted. The inputs required and the IMON installation procedure are described in the IMON manual (and possibly a README file for IMON).
3.4 Product use The version change from BS2000/OSD-BC on /390 systems to OSD-XC V2.2A is described in the manual "OSD/XC Migration Guide". When upgrading from OSD/XC V1.0 or OSD/XC V1.1 to OSD/XC V2.2A, X2000 V3.0 must already be in use. As of OSD/XC V1.1A the support of device type D3435 for FibreCat CX400/CX600, CX500/CX700 and Symmetrix systems on FC is provided.
The alphanumeric identifier in column 72 controls selection of the REP records for the different code variants. Column 72='P' The correction considered for The correction considered for Column 72=' ' (space) is only SPARC64 code is only /390 code The standard names of the REP files at system startup are: Basic configuration SYSREP.BS2.150 SYSIPL SYSREP.IPL.150 SYSSTART SYSREP.STRT.150 SLED SYSREP.SLED.
However, if a small amount of real memory is used (< 100 MB), due to a lack of BCAM memory this can lead to problems occurring during connection setup or to low transaction rates. This behavior can be improved by increasing the PAGMEM and RESMEM values. Memory monitoring can be activated with the BCAM /BCMON command (RECORD=(RES-MEMORY,PAG-MEMORY)) and this allows detection of whether the current values reach the limits.
3.4.3 Startup/Shutdown System startup The Initial Program Load (IPL) of OSD/XC is triggered in the X2000 Carrier System with the "KVP Console" application. The KVP main function menu is activated with the "F2" function key after logging on to a console ID in the X2000 Carrier System. The KVP commands are available to you after selecting the menu item "SVP Commands". A form for starting BS2000 is opened by selecting "ipl - start BS2000".
3.5 Obsolete functions (and those to be discontinued) The following functions are not supported in OSD/XC V2.2A with respect to the BS2000/OSD-BC V6.0B operating system base on /390. - HW-AUDIT - Global storage: the GSVOL subsystem is not in OSD/XC V 2.1A - the interface DIV - F2/Q3 operation of UTM (hardware memory protection key not usable).
Pubsets with an extended catalog (catalog format “extra large”) can no longer be imported in OSD/XC < V2.0A, due to the incompatibly modified catalog format. The import in OSD/XC V2.0 is possible as of correction package 2/05 (BS2000/OSD V6.0B). 3.8 Procedure in the event of errors General information on generating error documents To successfully diagnose and eliminate software problems, error documents must be generated or saved to the extent required and at the earliest possible time.
2. The SVP commands are available for use at the KVP console after selecting menu item "SVP Commands" in the main KVP function menu. IOSDUMP generation can be forced by selecting "iosdump". The name of the IOSDUMP is output. - IOHDUMP 1. With DUMP-IPL, an IOHDUMP is stored automatically in the SLED file IOHIOSDP section and in the /var/opt/SMAW/X2000/dump/ directory (the file name is output in SLED message NSD7900). 2.
- SJMSFILE SYSTEM-JOBPOOL entry in the user catalog of the user IDs involved in exceptional cases: diagnostic dump instead of SLED SCHEDLOG file For problems in the binder loader system: - if the error can be reproduced: libraries involved and phase - for SHARE problems: console log and entire class 4 memory dump - for ELDE problems: phase For SYSFILE management problems: - procedures/enter jobs in file form - SYSOUT or SYSLST log For NDM problems: - NDMDAMP (PRODAMP procedure, see 'Diagnostics Manual': D
4 Hardware support 4.1 Central units 4.1.1 Supported central units OSD/XC V2.2A is executable on all models of the SX100, SX130, SX140 and SX150 business servers.
SX140-40C | 235 | 4 | 2048 MB | 8 GB ----------|-----|-------------|-----------------|---------------SX140-50C | 280 | 5 | 2048 MB | 8 GB ----------|-----|-------------|-----------------|---------------SX140-60C | 320 | 6 | 2048 MB | 12 GB ----------|-----|-------------|-----------------|---------------SX150-10A | 42 | 1 | 2048 MB | 8 GB ----------|-----|-------------|-----------------|---------------SX150-10B | 75 | 1 | 2048 MB | 8 GB ----------|-----|-------------|-----------------|---------------SX150-10
A part of 25% of total memory for X2000 is the recommended value. If necessary, please consult your service delegate. 4.1.2 Discontinued support - none - 4.2 Consoles/terminals 4.2.1 Supported consoles The delivery scope of an SX130, SX140 and SX150 series server includes an SMC (System Management Console). System control on an SX100 series server is via the integrated console. Consoles can additionally be connected to the SX server via the LAN interface. 4.2.2 Discontinued support - 4.
FibreCat CX400, CX600 FibreCat CX500, CX700 FibreCat CX3 Symmetrix DMX800, DMX801 Symmetrix DMX-3 950 *2 DMX-3 and DMX-4 requires X2000 V3.0A07. 4.4.2 Discontinued support - 4.5 none – Magnetic tape devices 4.5.1 Supported magnetic tape devices Magnetic tape devices are supported in OSD/XC V2.2A on SX-servers via channel (not on servers of the SX100 series server), fibre channel or SCSI according to the following list.
SX150: - SXFCTX24-112-L2H: FibreCAT TX24 (LTO2) via SCSI-LVD on controller SX70F-CS12 - SXFCTX24-112-L3F: FibreCAT TX24 (LTO3) via fibre channel - SX9084-221F-L2 (LTO2) via fibre channel *2 *2 *2 Notes: A CS12 controller is to be assigned exclusively to a TX24 device with SCSI connection (no parallel use of the second slot in the CS12 controller). Software support is via the device management. It is not necessary to use MAREN/ROBAR.
4.6 none – Printers 4.6.1 Supported channel printers A list of the supported printers is available in the Internet under the following URL: http://extranet.fujitsu-siemens.com/products/ bs2000/peripher/print/doc/bs2-supported-printers.xls 4.6.2 Discontinued support - 4.7 none – Channel adapters 4.7.
