Fujitsu Personal Computer BS2OSD User Manual

Fujitsu Siemens Computers

BS2OSD(BS2000/OSD)

Version 6.0B

April 2008

Release Notice

Download from Www.Somanuals.com. All Manuals Search And Download.

3.4

3.5

3.5.1

3.5.2

3.6

3.7

3.8

Product use

Obsolete functions (and those to be discontinued)

Obsolete macros

Obsolete commands

Incompatibilities to BS2000/OSD-BC V5.0C

Restrictions

Procedure in the event of errors

4 Hardware support

4.1 Central units

4.1.1

changed support

Discontinued support

Extended support

4.1.2

4.1.3

4.2

4.2.1

4.2.2

4.3

4.4

4.4.1

4.4.2

4.5

4.5.1

4.5.2

4.6

4.6.1

4.7

Channels

Changed support

Discontinued support

FC switches

Disk controllers

Changed support

Discontinued support

Magnetic tape devices

Changed support

Discontinued support

Printers

Changed support

Other peripherals

4.7.1

4.7.2

Changed support

Discontinued support

Page 2

Download from Www.Somanuals.com. All Manuals Search And Download.

1 General

This Release Notice is a summary of the major extensions, de-

pendencies and operating information with respect to the deliv-

ery components of the BS2000/OSD-BC V6.0 *) package that are con-

tained in the following technical delivery units:

'BS2GA.APACHE V6.0', 'BS2GA.BS2OSD V6.0',

'BS2GA.CRTE-BAS V6.0', 'BS2GA.DSSM V6.0', 'BS2GA.IMON V6.0',

'BS2GA.JENV V6.0',

'BS2GA.POSIX V6.0',

’BS2GA.SNMP V6.0’,

’BS2GA.WTOSD V6.0’

'BS2GA.LLMAM V6.0', 'BS2GA.PLAM V6.0',

'BS2GA.SDF V6.0', 'BS2GA.SIR V6.0',

'BS2GA.SPOOL V6.0', 'BS2GA.STRT V6.0',

This delivery also contains DESK2000-CD V4.1. The current

DESK2000 version supports Windows 2000 and XP for the first time.

This makes the product 'SPOOL & PRINT EXPLORER' available on all

current Windows platforms.

The release level is that of April 2008. Changes in this correc-

tion level are marked with *7.

This Release Notice is supplied as a file in uppercase/lowercase.

Customers will receive an updated version of this file should any

subsequent changes be made. To print this file, use:

/PRINT-DOCUMENT FROM-FILE=SYSFGM.BS2OSD.060.D,

DOC-FORMAT=*TEXT(LINE-SPACING=*BY-EBCDIC-CONTROL)

(German)

/PRINT-DOCUMENT FROM-FILE=SYSFGM.BS2OSD.060.E,

DOC-FORMAT=*TEXT(LINE-SPACING=*BY-EBCDIC-CONTROL)

(English)

This Release Notice is also available online under

http://manuals.fujitsu-siemens.com and

In addition, the following Release Notices of the technical de-

livery units that are shipped with BS2000/OSD-BC V6.0B must also

be noted when using the product:

SYSFGM.APACHE.022.E

SYSFGM.BINDER.024.E

SYSFGM.BLSSERV.026.E

SYSFGM.BS2ZIP.012.E

SYSFGM.CRHP2AFP.010.E

SYSFGM.CRTE-BAS.016.E

SYSFGM.DISPLAY.010.E

SYSFGM.DSSM.041.E

SYSFGM.IMON.030.E

SYSFGM.JENV.050.E

SYSFGM.LLMAM.033.E

*) BS2000/OSD (R) is a trademark of Fujitsu Siemens Computers

GmbH

Page 3

Download from Www.Somanuals.com. All Manuals Search And Download.

SYSFGM.PERL.058.E

SYSFGM.PLAM.034.e

SYSFGM.POSIX-BC.060.E

SYSFGM.PTHREADS.010.E

SYSFGM.SDF.046.E

SYSFGM.SIR.150.E

SYSFGM.SNMP-LIGHT.050.E

SYSFGM.SNRTP.010.E

SYSFGM.SPCONV.011.E

SYSFGM.SPOOL.048.E

SYSFGM.STRT.150.E

SYSFGM.TOMCAT.055.D

SYSFGM.WEBTRANS-OSD.071.E

The Release Notice SYSFGM.BS2XC.022.E must also be noted for SX

Servers.

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.

1.1 Ordering

BS2000/OSD-BC V6.0 can be ordered from your local distributors

and is subject to the general terms and conditions of the soft-

ware product use and service agreement.

1.2 Delivery

The BS2000/OSD-BC V6.0 files are supplied via SOLIS.

BS2000/OSD-BC V6.0 delivery components

The following release units (RU) of the technical delivery units

(DU) are part of the delivery scope:

DU / RU

Version

Comment

BS2GA.APACHE

APACHE

PERL

TOMCAT

2.2A

5.8A

5.5A

BS2GA.BS2OSD

ACS

ADAM

AIDSYS

AIDSYSA

ANITA

ASE

15.0A

16.0A

1.0A

ASSEMBH-GEN

1.2C

ASTI

1.0B

2.4A

15.0A

2.6A

BINDER

BLSSEC

BLSSERV

Page 4

Download from Www.Somanuals.com. All Manuals Search And Download.

BS2CP

15.0B

1.0A

BS2000-EXEC

BUILDER

C-TPR-LZS

CALENDAR

CALENDAR-TU

CAPRI

2.3A

15.0A

1.5A

CCOPY

COSMOS-BC

CPR

5.0B

15.0B

15.0A

4.4A

DAMP

Utility program

DCADITO

DIV

DIVTRAC

DLMUSER

DPAGE

DWS

ELFE

ESS-DOORS

FASTPAM

FITC

15.0A

14.0C

15.0A

11.0A

15.0B

12.1A

15.0A

5.0A

Utility program

GCF

GET-TIME

GSMAN

1.6A

15.0A

1.3A

GSVOL

HELGA

IDIAS

INIT

IOCFCOPY

IOGEN

IORM

15.0A

14.0A

15.0B

6.0A

Utility program

IOTRACE

JITSYS

JMP

15.0B

3.0A

2.0A

14.0A

15.0A

2.4A

Utility program

JMU

JOBSCHED

JPPOPT

LMSCONV

LNM

3.3C

Utility program

14.0A

15.0A

1.2A

13.0A

15.0B

15.0A

15.0B

15.0A

12.1A

6.0A

15.0A

2.8C

1.0C

2.0B

1.3A

7.1E

1.0A

6.0A

MIP

MSCFANC

MSGMAKER

NDMDAMP

NKISAM

NKISTRAC

NKS

Utility program

NKV

NLMSERVE

PAMCONV

PAMINT

PASSWORD

PCA

PTHREADS

PVSREN

RESLOG

RMS

Utility program

SANCHECK

SCDM

SHOW-FILE

SMI

15.0A

1.0A

Page 5

Download from Www.Somanuals.com. All Manuals Search And Download.

SMPGEN-S

SMPGEN-U

SPCCNTRL

STATUS

SRPMNUC

SYSFILE

TANGBAS

TANGRAM

TPCOMP2

TPRLAM

TSOSLNK

TULAM

UTM-SM2

VOLIN

15.0B

15.1B

15.0B

15.0C

1.3A

Utility program

1.3A

15.0A

21.0E

15.0A

15.0B

Utility program

WARTOPT

BS2GA.CRTE-BAS

CRTE-BAS

CRTE-BASYS

CRTE-MSG

POSIX-HEADER

1.6A

BS2GA.DSSM

DSSM

ROSI

SSCM

4.1A

15.0A

2.3B

Utility program

BS2GA.IMON

IMON

3.0A

2.6A

3.0A

IMON-BAS

IMON-GPN

IMON-SIC

BS2GA.JENV

JENV

5.0A

3.3A

BS2GA.LLMAM

LLMAM

BS2GA.PLAM

PLAM

PMLOG

PMSYS150

3.4A

BS2GA.POSIX

POSIX-ADDON-LIB

POSIX-BC

POSIX-NSL

POSIX-SH

POSIX-SOCKETS

2.1A00

6.0A39

1.2A03

POSPRRTS

Page 6

Download from Www.Somanuals.com. All Manuals Search And Download.

BS2GA.SDF

DISPLAY

1.0B

8.2D

4.6A

3.0B

4.1A

2.4A

1.1A

3.1A

3.0C

4.1F

2.3B

FHS-TPR

SDF

SDF-CONV

SDF-I

SDF-P-BASYS

SDF-PAR

SDF-SFC

SDF-SRV

SDF-U

VAS

BS2GA.SIR

SIR

15.0B

5.0A

BS2GA.SNMP

SNMP-LIGHT

BS2GA.SPOOL

BS2ZIP

PRMMAN

PRMPRES

SNRTP

SPCONV

SPOOL

SPOOLSYS

SPSERVE

SPSRVMAN

1.2A

1.3A

1.2A

1.0B

1.1A

4.8A

2.2A

2.8A

2.3A

BS2GA.STRT

IPL

SLED

STRT

15.0B

BS2GA.WTOSD

WEBTRANS-OSD

7.1A

You will find the delivery components for the separate release

units listed in the SOLIS2 delivery cover letter together with

the current file and volume characteristics.

1.3 Documentation

The following documentation is available for BS2GA.BS2OSD V6.0

and the technical delivery components below:

BS2GA.DSSM V6.0, BS2GA.IMON V6.0, BS2GA.LLMAM V6.0,

BS2GA.PLAM V6.0, BS2GA.POSIX V6.0, BS2GA.SDF.V6.0

BS2GA.SIR.V6.0, BS2GA.STRT V6.0

Page 7

Download from Www.Somanuals.com. All Manuals Search And Download.

The documentation for the remaining technical delivery units is

listed in the respective Release Notices.

Core documentation

TITLE

ORDER NUMBER GERMAN

ENGLISH

-5-76 *

ADAM

BINDER

U 3563-J-Z125-5

U 9557-J-Z125-4

-4-76

Binder Loader-Starter (BLSSERV) U 5137-J-Z125-6

-6-76

CALENDAR

U23372-J-Z125-1

-1-76 *

Files and Volumes

larger than 32GB

Diagnostics Handbook

Utility Programs

Introductory Guide to DMS

DMS Macro Calls

IMON Installation Monitor

Commands Volume 1

U41253-J-Z125-1

U 5663-J-Z125-7

U 4303-J-Z125-8

U 4237-J-Z125-8

U 4250-J-Z125-8

U21926-J-Z125-5

-1-76 *

-7-76

-8-76

-5-76

U 2338-J-Z125-16 -16-76

Commands Volume 2

Commands Volume 3

Commands Volume 4

Commands Volume 5

U41074-J-Z125-3

U21070-J-Z125-6

U41075-J-Z125-3

U23164-J-Z125-5

-3-76

-6-76

-3-76

-5-76

Commands Volume 6: Output in

S-Variables and SDF-P-BASYS

Executive Macros

Migration Guide

MSGMAKER V1.2A

U23165-J-Z12-5

U 3291-J-Z125-10 -11-76

U21630-J-Z125-6

U23715-J-Z125-2

-5-76

-6-76

-2-76 *

Performance Handbook

POSIX Basics for Users and

System Administrators

POSIX Commands

U 1794-J-Z125-11 -11-76

U22795-J-Z125-5

U22794-J-Z125-5

U26110-J-Z125-3

-5-76

-3-76

POSIX SOCKETS/XTI

SDF V4.5 Introductory Guide

to the Dialog Interface

SDF V4.5 SDF Administration

SDF-CONV V3.0A

U 2339-J-Z125-8

-8-76 *

U 2622-J-Z125-10 -10-76*

U 6540-J-Z125-3 -3-76 *

U 2417-J-Z125-15 -15-76

Systems Support

System Exits

U 3619-J-Z125-7

-7-76 *

System Managed Storage

(User Guide)

U25174-J-Z125-3

-3-76

System Installation

System Messages Volume 1

System Messages Volume 2

System Messages Volume 3

Commands Ready Reference

Computer Center Ready Reference

Volume 1

Volume 2

Unicode in BS2000/OSD

Overview Manual

Subsystem Management

(DSSM/SSCM)

U 2505-J-Z125-16 -16-76

U 5854-J-Z125-7

U 5855-J-Z125-7

U41076-J-Z125-3

U23378-J-Z125-5

-7-76

-3-76

-5-76

U 370-J-Z125-14

U23908-J-Z125-5

-15-76

-5-76

U41646-J-Z125-1

U23166-J-Z125-3

-1-76

-3-76 *

The manuals marked with * have not been revised for

BS2000/OSD-BC V6.0.

Page 8

Download from Www.Somanuals.com. All Manuals Search And Download.

The documentation is available as online manuals under

http://manuals.fujitsu-siemens.com

or can be ordered in printed form at extra cost under

http://fsc-manualshop.com

The product Adobe Acrobat Reader is required to read or print the

manuals in PDF format.

The Release Notices are also available online under

http://manuals.fujitsu-siemens.com or under

You will also require the hardware manuals for the hardware pe-

ripherals you are using.

The BS2000/OSD documentation is also available on CD-ROM in Ger-

man and English under the title BS2000/OSD SoftBooks.

There may also be README files available for the manuals listed

above. These files contain modifications and supplements for the

manual applying to each relevant product. The names of these

files are structured as follows:

SYSRME.<prod>.<vers>.D

SYSRME.<prod>.<vers>.E

(file with German text)

(file with English text)

The README files listed below have been regenerated for

BS2000/OSD-BC V6.0:

Filename

relevant manual

SYSRME.ASTI.010.E

SYRME.BS2CP.150.E

SYSRME.IORM.060.E

SYSRME.NKISAM.150.E

SYSRME.SPCCNTRL.150.E

SYSRME.SANCHECK.010.E

System Installation (SIR)

Utility Programs

System Support

Utility Programs

Page 9

Download from Www.Somanuals.com. All Manuals Search And Download.

2 Software extensions

Only the main extensions and enhancements over the previous ver-

sion BS2000/OSD-BC V5.0 are described in the following sections.

2.1 Adaptations to CFCS 4.3

The progress reporting in CFCS 4.3 for different requirements has

been implemented in BS2000/OSD V6.0.

2.2 Enhancement of multiprocessor performance via

AS/RM lock breakup

A rise in the multiprocessor degree also increases the probabil-

ity of lock conflicts, which in turn reduces performance.

The memory management has been modified internally to replace the

AS/RM lock with several separate locks and CPU-specific memory

domains have been introduced for the RM lock.

Each memory domain behaves in the same way as the complete memory

of a system and is protected with a lock of its own.

This does not result in any changes to the external interfaces.

2.3 Data spaces

As of this version, data spaces are also supported for SX servers

to further decrease the load on the system address space. Among

others, data spaces are used by memory management, DAB and for

external storage of the F5 label.

OSD/XC 2.0 and X2000 3.0A are required for supporting ESA data

spaces in customer applications on SX servers.

Data spaces are implemented for TU applications in CISCFW 4.4,

that is supplied with X2000 3.0.

2.4 Performance enhancement of CCOPY in conjunction

with HSMS V7.0A and ARCHIVE V7.0B

The initialization phase in CCOPY V5.0 has been considerably re-

duced for backups using TimeFinder/BCV, to allow the applications

concerned to reopen their files faster. This minimizes the times

in which applications cannot work.

Further performance improvements are achieved by optimizing

catalog access; the File List is eliminated and the Wildcard

Syntax resolution does not occur until the ARCHIVE.

When Shared Pubsets are used, backups are always carried

out locally, independent of the master-slave role.

Page 10

Download from Www.Somanuals.com. All Manuals Search And Download.

2.5 Functional extensions for SM pubsets

The new SMPGEN MODIFY-SYSTEM-MANAGED-PUBSET statement can be used

to extend existing system managed pubsets by single feature pub-

sets, where each single feature pubset is turned into a volume

set of the system managed pubset.

The user data and the management and protection information of

the new single feature pubsets and the existing system managed

pubsets remain unchanged.

Note: Before converting a single feature pubset into a system

managed pubset, you should make a physical backup with FDDRL and

a logical backup with HSMS, since the single feature pubset can

be destroyed if an error abort occurs.

PVSREN V2.0 offers the new functionality of creating independent

pubsets from pubset mirrors within a system. Either single fea-

ture pubsets or system managed pubsets can be used as the source

for this.

With system managed pubsets, the renaming rules for the volume

sets are stored in a parameter file. Even pubset mirrors that

have been separated off and whose VSNs satisfy the "colon syntax"

can be converted into independent pubsets.

2.6 Number of MRSCAT entries > 1024

The previous limit of maximum 1024 MRSCAT entries has been re-

moved. A maximum of 4096 MRSCAT entries are now possible in

BS2000/OSD-BC V6.0.

2.7 Faster failure detection in MSCF

If the system is being monitored with the Live Monitor (component

of HIPLEX AF V3.2), the failure of a participant in the MSCF net-

work is now detected faster and more reliably. After the failure

has been surely detected by the live monitor, failure processing

in MSCF can be started automatically after a minimal wait time.

Fast failure detection and processing is possible in an XCS and

SPVS network with any number of participants and in a CCS net-

work.

A prerequisite for this is that HIPLEX AF is installed on all

participants in the MSCF network as well as on the subsidiary

systems (e.g. the VM2000 monitor systems) and the Live Monitor is

active.

The products HIPLEX-MSCF V4.0 und HIPLEX AF V3.2 are required for

this function. In addition to the functions of the Live Monitor,

HIPLEX AF V3.2 also offers further innovations such as, e.g.

fully automatic warm standby high availability solutions and

AutoSwap.

No dependencies exist between the MSCF configuration and the

HIPLEX AF configuration for fast failure detection.

Please consult the SYSFGM.MSCF.150.E and SYSFGM.HIPLEX-AF.032.E

Release Notices for detailed information on the functional scope.

Page 11

Download from Www.Somanuals.com. All Manuals Search And Download.

2.8 Reorganizing open files

Previously, it was only possible to reorganize closed files in

pubsets or volumes with SPACEOPT.

As of SPACEOPT V3.0, open files can also be included when reor-

ganizing pubsets and reducing file extents.

Please consult the Release Notice SYSFGM.SPACEOPT.030.E for the

complete scope of the innovations.

2.9 Tape blocks > 32 KB

Block sizes ranging from 32 KB to 256 KB are supported for tape

I/O with the BTAM access method for record formats V and U, to

allow high-performance backups to be made.

The new block size is specified at the TPR-FCB program interface.

The function is only available in TPR and for users with the TSOS

or HSMS-ADMINISTRATION privilege.

Large tape blocks are supported by the products ARCHIVE V7.0B,

FDDRL V15.0 and PERCON V2.8

2.10 File encryption

Data encryption fulfills the requirements for the security of

critical data, such as protection against physical reading from

the disk, protection against unauthorized reading, also with TSOS

special rights, protection against unauthorized usage of backup

tapes or monitoring the data contents with file transfer connec-

tions.

The files are stored on the disk in encrypted form and decrypted

in blocks for an authorized access in the system/server. The

files are taken over encrypted into backups or during file trans-

fers.

Two special commands have been introduced for encrypting and de-

crypting a file. An eight character crypto password is defined

for each file that is to be encrypted/decrypted. The key for en-

cryption/decryption is then derived from this during access.

ENCRYPT-FILE: converts a normal file into an encrypted file

DECRYPT-FILE: converts an encrypted file into a normal file

Working with encrypted files and the crypto password is similar

to working with ID-protected files and the file password. The

crypto password is registered as an access right with the command

ADD-CRYPTO-PASSWORD. This registration is valid for the current

task. The access right can be removed again with the command

REMOVE-CRYPTO-PASSWORD.

The openCrypt-Serv 1.2 subsystem with a corresponding Crypto Box

is required for file encryption on S servers.

openCRYPT-SOFT 1.2 in conjunction with X2000 as of V3.0A are

required for encryption on the SX100-C and SX150 servers.

An additional crypto CPU is required on SX150, whereas the

encryption processes run on the X2000 CPU on SX100-C

Page 12

Download from Www.Somanuals.com. All Manuals Search And Download.

The files are encrypted in pages with the symmetrical DES or AES

encryption method. The encryption method can be selected via the

FILECRYPT system parameter and can be changed dynamically. AES is

used by default.

The FREFCRYP system parameter can be used to limit the number of

crypto passwords by only allowing new crypto passwords to be as-

signed for files of a specific ID. Only the crypto passwords of

reference files from this specific ID can be selected for files

on other IDs.

Restrictions:

Files on private disks, EAM files, tape files,

job variables and

files on the home pubset under the TSOS ID

cannot be encrypted.

Recommendations: - Connection of two Crypto Boxes, each with two

paths (failure-safety)

- Read buffering with DAB

- Only encryption of selected files, not

complete pubsets.

Important notes:

1. If the crypto password is lost, there is no way of recon-

structing the file via decryption, even with measures em-

ployed by the privileged system administrator or by FSC. In

other words, organizational precautions must be taken for

such a case, e.g. storing the crypto password in a safe

place (key escrowing).

2. In HIPLEX configurations it must be ensured that the

standby system of an application that is to be moved and

has encrypted files, has the necessary resources available,

e.g. an S server with a Crypto Box.

3. In Symmetrix disaster protection configurations with SRDF

mirroring, the encrypted files are also available on the

mirrors, i.e. the encryption is transparent for the known

switch-over scenarios.

2.11 Increasing the size of volumes (disk resizing)

In SPACEOPT V3.0, a new function is provided for adapting the

size of public disks.

The command ADAPT-PUBSET-SPACE can be used in RAID disk subsys-

tems to adapt the size of BS2000 disks to the actual size of the

logical units (LUN) with which they are implemented. Such an ad-

aptation may, for example, be necessary after data migration with

DRV V3.0 from an ECKD disk to a D3435-FBA disk.

With this migration, the source disk and the destination disk

must be the same size. If the LUN is larger than the source disk,

unusable space is left at the end of the disk that can be made

available with the new function.

Disk size increasing can only be used for public disks with D3435

format on Symmetrix and FibreCat.

Please consult the Release Notice SYSFGM.SPACEOPT.030.E for de-

tailed information on the functional scope.

Page 13

Download from Www.Somanuals.com. All Manuals Search And Download.

2.12 Four character mnemonic name for tape devices

A four character hexadecimal device mnemonic (1000 – FFFF) is now

also allowed for tape devices. A two character alphanumeric name

is still allowed as previously for all device types. This makes

more than 1300 tape devices addressable.

Note: As of SINIX-2000-Z V8.1A K818.4, the SKP-X based on the

PRIMERGY 470 hardware supports the CD drive as a tape device for

reading CDs. Four character device mnemonics are not permitted

for the CD drive on SKP-X.

2.13 New functions on SX 150 business servers

Dynamic reconfiguration

The SX150 supports dynamic system board reconfiguration for both

Solaris and BS2000 partitions, whereby both BS2000 and VM2000 can

be used in the BS2000 partition. The configuration of the SX150

standard models may have to be extended, depending on the planned

usage scenario for dynamic reconfiguration.

Please consult your sales representative.

CAPACITY on DEMAND (CoD)

The capacity on demand function is available to provide an

increase in performance that is free of interruption and limited

in time, as on S140/S145/S155/S170/S180/S190 business servers.

In addition to the working processors that are enabled as

standard, one or more CoD processors can be used (with

appropriate contractual agreement). They are switched in or

out as required during operation.

Big Pages

Pages with a size of 4 MB, so-called big pages, are used for JIT

memory and class 1 memory on the SX150 business server to save

TLB entries.

The Release Notice SYSFGM.BS2XC.021.E provides information on

further innovations.

2.14 New functions in BS2000/OSD V6.0B

2.14.1 Catalog administration

2.14.1.1 “Extra Large” catalog format

In a Pubset catalog, the file and job variable allocations

are deposited in catalog entries. Large Object Pubset

catalogs previously comprised a maximum of 16184 4K blocks,

conventional Pubset catalogs 8192 4K blocks.

The previous catalog size allows ca. 120000 – 160000 or

60000 – 80000 files/JVs to be created. If this space is used

up, no new IDs may be created on the Pubset; for already

existing users, the extension or recreation of files/JVs

may fail.

Page 14

Download from Www.Somanuals.com. All Manuals Search And Download.

For SF and SM Pubsets, the maximum catalog file size will be

increased to 32008 4K blocks, representing a 98% enlargement.

In the case of SM Pubsets, the special catalogs #MIN, #JVC

and #PTV can also be shared out among upto 100 catalog files,

which corresponds to a new maximum catalog size of 32008 4K

blocks and a 187-fold increase.

The new part catalogs will be numbered serially from

$TSOS.TSOSCAT.#M00 - $TSOS.TSOSCAT.#M99

$TSOS.TSOSCAT.#J00 - $TSOS.TSOSCAT.#J99

$TSOS.TSOSCAT.#P00 - $TSOS.TSOSCAT.#P99

For this extended catalog, a new catalog format “extra large”

will be introduced alongside the previous catalog formats

“large” and “normal”.

Pubsets with “extra large” catalog format can be generated with

SIR when the Pubset is imported or installed:

Command:

/IMPORT-PUBSET…. EXTRA-LARGE-CAT-CONV=*YES

With SM Pubsets this command affects all part

catalogs.

SIR instruction: DECLARE-PUBSET …,TSOSCAT-TYPE=*EXTRA-LARGE

Important information:

The new catalog format is incompatible. A Pubset that uses

the catalog extension can no longer be imported into versions

prior to BS2000/OSD V6.0B.

An inhomogeneous SPVS network with versions prior to BS2000/OSD

V6.0B is not possible.

For certain products new or corrected versions must be installed:

DRV

openSM2

V3.1A

V14.0C

V6.0B

SCA

SHC-OSD

V15.0B

V5.0A

SPACEOPT V3.0B

2.14.1.2 Automatic catalog enlargement

The command /SHOW-PUBSET-CATALOG-ALLOCATION displays the format

and current workload of the catalog or catalogs.

During operation, catalog files that have not yet reached their

maximum size are automatically enlarged; this applies to all

catalog formats. However, the catalog format is never modified

by this automatic enlargement. As before, the catalogs can

of course also be enlarged manually. On SM Pubsets the new

command ADD-CATALOG-FILE is available for the manual enlargement

of special catalogs by single catalog files.

Page 15

Download from Www.Somanuals.com. All Manuals Search And Download.

2.14.2 Self-configuring NK-ISAM Pools in Data Spaces

To further relieve the system address area, NK-ISAM files are

buffered in Data Spaces. At the same time, buffer areas are

created strictly for individual files and no longer for file

groups, thus reducing the number of lock conflicts over access

to the buffer areas. The buffer areas are generated automatically

by the system; the user does not need access to programs or

JCL in order to make use of the function. Previously an optimal

configuration of the ISAM pools was possible only through user-

defined ISAM pools, and required JCL access.

2.14.3 Performance improvements in BS2000/OSD V6.0B

RSC for emulated disks

On SX servers, IOs are run on emulated disks via RSC (Remote

System Call). This allows the IO CPU to be relieved and inputs

and outputs to be parallelized, resulting in a significant

increase in capacity.

Acceleration of the command COPY-FILE

The doubling of the IO size from 32 kbyte to 64 kbyte reduces

CPU usage and significantly shortens running time.

Own SRPM Server task for Data Pubsets

Previously both the Home Pubset and Data Pubsets were

administered by an SRPM server task (RP01).

From this version onwards, a new SRPM server task (RP02) is

generated for the administration of Data Pubsets and the Home

Pubset is administered exclusively by the RP01 task. Wait states

caused by Data Pubsets therefore no longer affect access to

the Home Pubset.

2.14.4 New sub-system STATUS

In the course of command expansions, the commands SHOW-JOB-

STATUS, SHOW-USER-STATUS, SHOW-SYSTEM-STATUS and STATUS (ISP

format) have been merged in the new sub-system STATUS. The

requirements for new software products or future BS2000

versions can therefore be implemented faster and more easily.

Page 16

Download from Www.Somanuals.com. All Manuals Search And Download.

2.15 New functions of BS2000/OSD V6.0B with

Correction Package 1/2006

2.15.1 JENV V5.0

BS2000/OSD with the JENV V5.0 component has been certified as

JAVA COMPATIBLE by Sun Microsystems, Inc. This provides the

assurance that Java programs can run on BS2000/OSD without re-

compilation or other modifications.

The current version 5.0 of the Environment for Java fulfils the

relevant specifications:

- “The Java Language Specification, Third Edition”

- “The Java Virtual Machine Specification, Second Edition”

- the version-specific API specification “Java 2 Platform Stan-

dard Edition API Specification 5.0”

The conformity to these specifications was approved by Sun Micro-

systems Inc. by the grant of the “Java Compatible”-Logo for the

Fujitsu Siemens BS2000/OSD Environment for Java ^TMV5.0

(on 10/08/2005).

Java Development Kit V5.0 is supplied as an optimized variant for

the particular hardware, together with the BS2000/OSD basic con-

figuration. The JDK gives programmers a basic tool for developing

Java applications.

It comprises:

- HotSpot compiler

- Java interpreter

- Debugger

- Java class libraries

- Various other tools

In addition, JENV(BS2000/OSD) V5.0 includes the JRIO package.

This package is a collection of Java classes for native access

to record- and/or block-structure files and for record- or

block-oriented input/output with respect to such files. JENV V5.0

supports the files of the BS2000 data management system.

JENV V5.0 was released in 2006, January and henceforth is con-

tained in new BS2000/OSD-BC V6.0 shipments.

Page 17

Download from Www.Somanuals.com. All Manuals Search And Download.

2.16 New functions in BS2000/OSD V6.0B with

Correction Package 2/2006

2.16.1 Autonomous, dynamic control of I/O resources (IORM)

The new utility program IORM facilitates autonomous, dynamic

control of the I/O resources, devices, controllers, channels

(type S and type FC) and paths. Both S and SX servers are

supported in native and in VM2000 operation.

The following functions are implemented:

- IOPT: I/O priority control for tasks with competing access

to one device (I/O Priority Handling for Tasks)

- DPAV: Dynamic I/O load distribution for S server disks

on the FC channel (Dynamic Parallel Access Volume)

- DDAL

Optimized load distribution in CentricStor operation

(Dynamic Device Allocation)

- IOLVM: Limiting of I/O throughput for single VM2000 guest

systems (I/O-Limit for Virtual Machines)

- TCOM: Adapting the compression for LTO devices

(Tape Compression)

The IOPT, DPAV and IOLVM functions control disks, the DDAL and

the TCOM functions control tape devices.

IORM links itself into the BS2000 I/O system and collects I/O

data to determine the I/O resources utilization. IORM also

periodically checks whether intervention in the I/O operation

is required.

The values set for intervention such as thresholds, selection of

devices to be monitored or I/O priorities can be passed to IORM

in the form of a parameter file or in dialog.

IORM has a HELP function that outputs all permitted statements

together with their syntax.

You will find a detailed description in the SYSRME.IORM.060.E

file or in the utilities manual.

I/O-Priority control for tasks (IOPT)

I/O-intensive but relatively unimportant applications can

obstruct other, more important applications if the I/Os are on

the same device or on devices on the same controller, path,

port or channel.

Three I/O priorities, low, medium and high, were therefore

introduced for IORM.

If the IOPT function is activated in IORM (IOPT_SET_ON=YES

statement), IORM applies brakes to the tasks with low and medium

priorities by assigning time penalties if these tasks hinder

tasks with higher priorities.

IORM does not affect tasks with I/O priority high.

I/Os via FDDRL, ARCHIVE, VOLIN or PAGING are also not braked.

Page 18

Download from Www.Somanuals.com. All Manuals Search And Download.

Dynamic I/O load distribution for disks on the FC channel of

the S server (DPAV)

Only one I/O can be executed at any particular time on a disk.

If several applications with a large number of I/Os use the same

disk, this can lead to high wait times.

Until now, static PAV (Parallel Access Volume) has been used on

S servers since BS2000/OSD-BC V5.0 to alleviate this problem.

The function allows multiple concurrent accesses to one logical

device.

With PAV, several device addresses (alias devices) are assigned

to one logical (base) device on the same controller, thus

allowing multiple I/O orders to be started concurrently via

the base and alias devices.

PAV on the FC channel is a pure software solution that can be

operated without intervening in the Symmetrix controller. To do

this, BS2000 uses the fact that disks on the FC channel can

still accept I/O orders if an I/O is already active.

Static PAV assigns the alias devices statically to the base

device and therefore requires predictive planning of device

utilization.

Dynamic PAV (IORM DPAV function) assigns the alias devices

autonomously to the volumes that would profit most from them.

For devices connected via type FC, DPAV switches an alias

device from the current base device to another base device by

dynamically changing the I/O configuration.

In VM2000 operation, DPAV must be activated for each guest

system in which DPAV is to be active.

Note: /START-VM cannot be used during dynamic I/O configuration

changes on S servers while operating under VM2000.

When using the IORM DPAV function, dynamic I/O reconfiguration

can be called at any time, thus disrupting /START-VM

For this reason, as of VM2000 V9.0 with /START-VM and active

dynamic I/O reconfiguration the system waits a maximum of 15

seconds for the I/O reconfiguration to be completed. If the I/O

reconfiguration takes longer, /START-VM is rejected.

The following restrictions apply when using HIPLEX AF under

VM2000 < V9.0:

- If the "warm standby" scenario is used, the DPAV function must

be deactivated on all virtual machines of the standby system.

- When monitoring the guest system with VM2000 resources via the

live monitor while using DPAV, RESTART-AFTER-STOP=*NO must be

set in the ADD-VM2000-MONITORED-SYSTEM statement.

Optimized load distribution in CentricStor operation (DDAL)

This function can be activated but the controlling intervention

will only be implemented in future BS2000/OSD-BC versions. DDAL

must be activated on all guest systems and the monitor system

for IORM to be able to take control in VM operation.

Page 19

Download from Www.Somanuals.com. All Manuals Search And Download.

Limiting the I/O inclusion of single VM2000 guest systems (IOLVM)

Less important guest systems that have intensive I/O activity,

can severely impede other, much more important guest systems

that use the same I/O resources.

The IORM function can detect such conflict situations and

intervene predictively. To do this, IORM continuously collects

the utilization values for all known I/O devices, checks the

settings for IOLVM and intervenes in the control if necessary.

IOLVM only considers disk devices. As with the IOPT function,

FDDRL, ARCHIVE, VOLIN and PAGING I/Os are not braked.

Adapting the compression of LTO devices (TCOM)

To ensure optimum data backup to LTO tapes, a minimum data rate

must be maintained to keep the tapes continuously streaming.

This minimum data rate is sometimes only achieved if the

compression is disabled on the device. However, this reduces the

tape capacity accordingly. By default, the compression is always

enabled in BS2000/OSD-BC V6.0, even if IORM is not used.

The compression can be fully disabled with the TCOM function.

TCOM can also dynamically enable/disable the compression

according to the data rate. The compression is disabled if the

data rate is sufficient for tape streaming without compression

but not with it.

2.16.2 Support for conversion from 7 bit to 8 bit character set

By default, BS2000/OSD uses the 7 bit EBCDIC character set

EDF03IRV with 95 printable characters and 65 control characters

in the system. The designation 7 bit has established itself

since the reproducible characters available correspond to the

ASCII 7 bit character set although 8 bits are used for coding.

Via the XHCS (Extended Host Code Support) subsystem, BS2000/OSD

supports both the 7 bit and 8 bit character sets that encompass

128 or 256 characters respectively.

This allows BS2000/OSD to depict all languages that are defined

in the international code tables as per ISO 8859. The concept of

"coded character sets" (CCS) that defines the character coding

in a file is used to depict the different character sets and

codes. The programs get the information about the character sets

from XHCS and do not have to store it themselves. Regardless of

the input source, XHCS identifies the character sets via their

character set names, the so-called CCS name, and makes them

available in the form of tables.

The class 2 option HOSTCODE=<CCS name> can be used to define a

different, specific 8 bit EBCDI code instead of EDF03IRV for the

complete BS2000/OSD system. Code definition via the CCS name is

possible for separate IDs and pubsets.

The default value for inputs on the terminal to TIAM, UTM and

DCAM applications can be modified globally via the VTSU-B

parameter file SYSPAR.VTSU-B.<vers>. Once the appropriate

parameters are set, the character set of the home pubset for

this ID apply. This is done for a single process with the command

MODIFY-TERMINAL-OPTIONS CODED-CHARACTER-SET=*8BIT-DEFAULT.

If data is converted from a 7 bit character set to an 8 bit one,

the converted data must be distinguishable from the unconverted

Page 20

Download from Www.Somanuals.com. All Manuals Search And Download.

data. As of BS2000/OSD-BC V6.0, a new system behavior will

therefore be introduced with which the default value of the CCS

name of a file is determined.

Note:

ISO8859-x variants should not be used as a system or user

character set since all programs in BS2000 assume that the

data is provided with a so-called invariant EBCDIC core.

Previous behavior:

Up to BS2000/OSD-BC V6.0B, the BS2000 system always assigns the

default *NONE for the CCS name of the file (CCS-Name=*NONE). If

a different character set is used, the file attribute CCS name

must be specified explicitly.

Changed behavior:

The two commands CREATE-FILE and MODIFY-FILE-ATTRIBUTES have

been extended by the parameter *USER-DEFAULT that defines the

default character set for the ID concerned.

If it is not EDF03IRV, when a new file is now created the CCS

name of the user entry of the destination pubset is taken over

as the CCS name of the file. As previously, the file does not

receive an entry for the CCS name (CCS-Name = *NONE) if EDF03IRV

is in the user entry. The file attribute CCS name is included in

the transfer when copying, saving and restoring files. The

behavior of LMS has also been changed analogously when new

elements are added. If a CCS name is not explicitly specified,

they are assigned the CCS name of the library.

There is therefore no change if the default system character set

is used. If an 8 bit character set is selected, the code is

clearly specified on the file and library element level via the

CCS name. However, explicit specification of the character set

always has priority.

You will find further information on converting from 7 bit to 8

bit character sets in the white paper under

http://extranet.fujitsu-siemens.com/vil/pc/vil/bs2000

/bs2000_operating_system/wp_zeichensatz-bs2000.pdf

2.16.3 New ASTI Subsystem

ASTI (Assistant for Service Task Integration) is implemented as

a subsystem and provides support for the system developer when

developing client / server applications. ASTI takes over the

communication between client and server by forwarding the orders

placed by the client to the server, receiving the feedback

messages and managing both in internal ASTI wait queues. A

server application must be started via ASTI to allow it to be

managed by ASTI. It is also possible to specify for client

orders whether recovery measures are to be initiated for the

orders concerned if the server terminates prematurely.

The ASTI functions are made available to the developer via a

macro interface.

ASTI is part of the BS2000/OSD basic configuration and is

initially only released for internal use by BS2000 products.

The first user of ASTI is the product interNet Services V3.2.

The ASTI subsystem is started automatically when the system is

booted.

You will find a detailed description of ASTI in the file

SYSRME.ASTI.010.E.

Page 21

Download from Www.Somanuals.com. All Manuals Search And Download.

2.17 New functions in BS2000/OSD V6.0B with

Correction Package 1/2007

2.17.1 Support for Unicode in BS2000/OSD via XHCS-SYS

Due to new EU directives, the previously supported character sets

are no longer sufficient in the medium term. As of BS2000/OSD-BC

V6.0B (correction level B62), support for Unicode supplements the

EBCDIC character sets previously available in BS2000/OSD systems

with the additional characters required in the European language

theater. This is done by using selected Unicode code points in

addition to the previous EBCDIC variants.

Unicode is an international standard in which a digital code is

defined for each character of all known languages over the long

term. You will find information on Unicode in the Internet under

http://www.unicode/org/.

The basis for the Unicode support in BS2000/OSD is extensions in

the XHCS-SYS V2.0 subsystem, the central source of information

about the coded character sets available in the system.

XHCS-SYS V2.0 is a component part of openNetServer V3.2.

In addition to the previously supported 8 bit ISO codes ISO8859-

1/2/3/4/5/7/9/15 and the EBCDIC codes belonging to them, XHCS-SYS

V2.0 also supports the Unicode formats UTF-8, UTF-16 (2 byte,

BS2000) and UTF-E in BS2000, that follows UTF-EBCDIC from IBM.

XHCS-SYS V2.0 also includes conversion tables from the supported

8 bit ISO codes to Unicode and vice versa. In addition to the

characters supported in these ISO codes, XHCS-SYS supports around

70 further characters from the Unicode character set, e.g. spe-

cial characters such as those used in public administrations

Using Unicode in the system

To support using Unicode in BS2000/OSD systems, the character

sets used in the system are extended by additional characters and

a programming and runtime environment are provided to extend ex-

isting applications with Unicode fields. It is thereby assumed

that only a few fields, mainly name and address fields, have to

be converted to Unicode.

The Unicode support is provided on the basis of the existing

products. Unicode-based characters are allowed for texts to be

processed but not for field or container names.

The product-specific rules for commands and object names remain

as they were.

Further preparations must be made for using Unicode beyond updat-

ing the system base, the system level applications and the pro-

gramming environment.

These include:

- All data/files must be brought into a defined,

consistent state.

- The CCS (Coded Character Sets) names of all data must be

consistent since the CCS name is a central component for

handling the data.

- Applications must be extended by the additional Unicode fields

that have to be processed.

Page 22

Download from Www.Somanuals.com. All Manuals Search And Download.

The UTF codes (Unicode Transformation Format) UTF-8, UTF-16 (2

Byte) and UTF-E that follows UTF-EBCDIC from IBM are supported in

BS2000/OSD.

2.17.2 Support for Unicode by the software products

The software environment required for supporting the Unicode

functionality is provided in BS2000/OSD-BC V6.0 and V7.0.

The support encompasses the following functional areas:

- Programming (COBOL2000, ESQL-COBOL, IFG/FHS, AID).

- Data storage (SESAM/SQL, ORACLE).

- Data processing (EDT, SORT, PERCON).

- Data I/O to terminals, printers and file transfer

(VTSU, MT9750,WebTransactions, FHS, RSO, Spool, openFT).

Unicode-specific extensions have been implemented in the above

products.

The different variants of the NATIONAL data type are supported

for the programming environment in COBOL2000 V1.4 and ESQL-COBOL

V3.0 and its use is permitted as a host variable in SQL state-

ments. CRTE V2.6 allows the procedural use of this data.

IFG V8.3 and FHS V8.3 allows separate format fields to be identi-

fied for Unicode.

With appropriate support by COBOL, AID V3.2 offers symbolic de-

bugging of data type UTF-16.

In the database systems SESAM/SQL V5.0 and Oracle 10g, Unicode

characters can be stored and processed with SQL resources using

the new data types NCHAR and NVARCHAR.

XHCS-SYS provides SORT V7.9 with the sorting tables required for

processing data. PERCON V2.9 is correspondingly extended for

standardizing diacritical characters and converting files. Files

with Unicode code sets can be processed as of EDT V17.0.

The EBCDIC variant of UTF-8 (UTF-E) is supported by the terminal

emulation MT9750 V7.0 and VTSU-B V13.2 for input/output. VTSU-B

V13.2 is a component part of openNetServer V3.2.

FHS V8.3 can output messages coded in UTF-E. Inputs in Unicode

fields are converted field-specifically to EBCDIC or UTF-16 be-

fore transfer to the applications.

RSO V3.5 supports network printers with UTF-8 capability and

accepts print files with UTF-8, UTF-16 and UTF-E coding.

In the local spool, files can be printed on OCE high performance

printers in UTF-16 format.

DMS and POSIX files can be transferred in the Unicode formats

UTF-8 and UTF-16 in BS2000 with openFT V10.0.

Note:

The size of all files remains unchanged. Since UTF-16 occupies 2

bytes per character, a SAM record can only contain 16000 charac-

ters and not 32000 characters as previously. The same applies

analogously for the database fields NCHAR and NVCHAR.

You will find detailed information on Unicode support in the Re-

lease Notices of the separate products.

Page 23

Download from Www.Somanuals.com. All Manuals Search And Download.

2.17.3 Improved SAN support (SANCHECK function)

Since the introduction of the fibre channel, the FC connection

technology SAN (Storage Area Network) is being used increasingly

for connecting Symmetrix storage subsystems and magnetic tape de-

vices (CentricStor and LTO). The previous control functions in

BS2000/OSD only allow a limited view of the actually present pe-

ripherals and their connections. If problems occur when mounting

devices or during operation, the cause is often very difficult to

find, e.g. the INOP message from a device may be caused by con-

nection malfunction anywhere in the SAN, but it may also be due

to a generation or wiring error.

The new SANCHECK function supports detecting generation errors

with S and SX servers as well as localizing error conditions in a

SAN.

Generation errors in BS2000, wiring errors or faulty zoning set-

tings are detected by comparing the path generated in BS2000 to a

device with the connections actually present in the SAN. Possible

generation errors are, e.g. wrong specification of the controller

WWPN (World Wide Port Number).

With errors in I/O operation, the error information on the path

between the channel and controller/device and to the FC switch or

fabric is output, thus allowing the error to be localized.

The SANCHECK function is called with the START-SANCHECK command.

The command requires the TSOS command privilege or OPERATING or

SERVICE.

SANCHECK offers the two statements SHOW-SAN-PATH and

SHOW-SAN-CONFIGURATION.

The SAN configuration data is determined with the first command

execution. The data is then used for subsequent call accesses

unless a data update is explicitly requested.

SANCHECK requires the POSIX subsystem since the SAN configuration

data is determined via POSIX-based SNMP interfaces. The SNMP

functions "getmany" used by SANCHECK are provided in the

BS2000/OSD-BC component SNMP-LIGHT and in the product SBA-BS2

(SNMP-Basic-Agent BS2000).

Note:

With SX servers up to and including SX150, only path and

zoning information can be shown because the X2000 V3.0 carrier

system does not support reading out the BS2000 disk configura-

tion. It is therefore not possible to check the disk configura-

tion against the physical wiring. This function will be offered

for future SX servers with X2000 V4.0.

2.17.4 New functions in POSIX A39

Dynamic modification of POSIX tuning parameters

The control parameters for the POSIX system kernel are stored in

the POSIX parameter file (SYSSSI.POSIX-BC.<version>). Changes to

this parameter file only take effect after the POSIX subsystem is

restarted.

As of POSIX A39, some selected POSIX tuning parameters can be

modified dynamically using the new privileged shell command usp.

If the modified values are also to be valid for the next POSIX

session, they must be entered in the SYSSSI file.

Page 24

Download from Www.Somanuals.com. All Manuals Search And Download.

The following tuning parameters can be modified dynamically:

FORCEDTERM

HDSTNI

HDPTNI

HEAPSZ

MAXTIMERC

Forces termination of the subsystem.

Number of server tasks for asynchronous I/Os.

Maximum number of mounted local file systems.

Maximum possible value for brk() system call.

Maximum number of seconds for terminating

rc scripts.

Maximum number of processes per user.

Maximum number of processes in complete system.

Maximum number of ttys.

MAXUP

NPROC

NOTTY

NOSTTY

Maximum number of sttys.

Size of the global program cache in MB for the

posdbl command.

DBLPOOL

Extensions to the POSIX installation program

The POSIX installation program START-POSIX-INSTALLATION has been

extended by the following functions for automated installation

(batch mode):

- Installation errors are recorded in the logging file

/var/sadm/pkg/insterr.

- The feedback of a command return code (MAINCODE, SUBCODE1,

SUBCODE2) and triggering the SPIN-OFF mechanism within

procedures are supported via the new SDF ERROR-HANDLING

operand.

Extensions to the mmap() function

- As of POSIX A39, the mmap() function also supports files

mounted via NFS.

- mmap also supports mapping /dev/zero for increasing

performance and reducing the porting effort of JAVA versions.

You will find detailed information about all innovations to POSIX

A39 in the Release Notice SYSFGM.POSIX-BC.060.E.

2.17.5 New system diagnostic tool Auxiliary SERSLOG Extensions

(ASE)

The Auxiliary SERSLOG Extensions (ASE) are implemented in the ASE

subsystem and represent an automated extension to the SERSLOG

events. With ASE, SERSLOG events can be monitored and actions can

be triggered when they occur. Both single record types and com-

plete message classes can be monitored. It is also possible to

set boundary conditions for the actions, such as frequency of the

SERSLOG events.

Possible actions are:

- Message output to the console.

- Teleservice call.

- Logging into an internal buffer.

The SERSLOG events to be monitored by ASE, the thresholds and the

actions are defined via commands.

ASE is a global system resource. Each user that has the TSOS

privilege required for command execution can also execute any ASE

command.

Page 25

Download from Www.Somanuals.com. All Manuals Search And Download.

2.18 New functions in BS2000/OSD V6.0B with

Correction Package 2/2007

BS2000/OSD V6.0B correction level B72 does not contain functional

extensions in the software products.

2.19 New functions in BS2000/OSD V6.0B with

Correction Package 1/2008

2.19.1 Support for new Hardware

In 2007, December release was given for the DMX-4 series Sym-

metrix disk subsystems with microcode e5772 for connection to

BS2000/OSD via type FC channel and via type S channel.

For BS2000/OSD-BC V6.0B correction package 2/2007 (release 2007,

November) is required.

The SHC-OSD V6.1 subsystem serves for controlling the Symmetrix

functions. At least correction level V6.1A01 (release 2007, De-

cember) is required.

2.19.2 Extensions in Software products

APACHE V2.2

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 and TOMCAT V5.5 instead of JSERV/JSP.

APACHE(BS2000/OSD) V2.2 includes support for the SSL (Secure

Socket Layer) protocol for secure transfer of documents and data

over the internet.

The Release Notice SYSFGM.APACHE.022.E provides detailed informa-

tion.

BS2ZIP V1.2

BS2ZIP V1.2 offers amongst others the following functional en-

hancements:

- The output of the BS2ZIP SHOW-FILE-ATTRIBUTES statement can be

moved into S-variables to exploit in SDF-P procedures.

- The files within the ZIP container can be protected by a con-

tainer-associated crypto password.

- In BS2ZIP V1.2 the new statement CONVERT-ZIP-CONTAINER is inte-

grated to convert a BS2ZIP PAM file in a SAM file that can be

managed by openFT.

- The PLAM-LIB indicator is set when a PLAM library is extracted

from a BS2ZIP container.

Detailed information on the extensions provides the Release

Notice SYSFGM.BS2ZIP.012.E

Page 26

Download from Www.Somanuals.com. All Manuals Search And Download.

2.20 Implemented change requests / extended commands

2.20.1 MOVE-TASK-TO-CATEGORY

The system administration can use the new MOVE-TASK-TO-CATEGORY

command to change the assignment of a task to a category if, for

example, it is necessary to provide better control of this task

or relieve the load on a category. The command does not handle

tasks with the task type "SYSTEM" and the category "SYSTEM" can-

not be specified as the target category. It is not necessary to

use the PCS (Performance Control System).

2.20.2 SHOW-USER-ATTRIBUTES

The USER-IDENTIFICATION parameter can be specified with wild-

cards. Further criteria for selecting user entries can be speci-

fied with the new SELECT parameter.

2.20.3 ACS (Alias Catalog System) for job variables

As of ACS V15.0, job variables can also be assigned an alias as

was previously possible for files. The alias catalog is extended

with the additional RANGE indicator for the required validity

range.

The validity range is set with the new RANGE operand of the

/ADD-ALIAS-CATALOG-ENTRY command

It is possible to set whether the alias catalog is valid:

- just for replacing file names:

- just for replacing JV names:

RANGE=*FILE

RANGE=*JV

- or for replacing both file and JV names: RANGE=*BOTH

ACS RANGE=*BOTH is set as default when ACS is installed.

The validity range can be changed with the command

/MODIFY-ALIAS-CATALOG-ENTRY ,RANGE=*UNCHANGED/*FILE/*JV/*BOTH

/SHOW-ALIAS-CATALOG-ENTRY without the RANGE operand specified

outputs all entries. The validity range of the alias catalog en-

try can be found at the left in the third position of the output:

F for file

J for job variable

B for file and job variable.

Note: The insertion of an extra letter shifts the command output

to the right by one position. Procedures that use the output of

/SHOW-ALIAS-CATALOG-ENTRY may have to be adjusted.

In addition, as previously, an alias catalog name must be unambi-

guously identifiable with the alias name, i.e. there can only be

one single alias catalog entry for each alias name.

It is therefore not possible to assign the same alias name for

two alias catalog entries with different RANGE entries. The fol-

lowing assignments, for example, are therefore not possible:

Alias name A, file name X, RANGE=*FILE

Alias name A, file name Y, RANGE=*JV

You will find a complete description of the ACS commands in the

manual "BS2000/OSD-BC V6.0 Commands".

Page 27

Download from Www.Somanuals.com. All Manuals Search And Download.

2.20.4 NTP/BS2 TimeServer with highest priority

The time server NTP (NETWORK-TIME-PROTOCOL) is the server with

the highest priority in BS2000 when the stratum value is less

than five or the system parameter NTPSHIGH is set to "Y" (yes)

and BS2000 has not received a value from NTP about the supplied

time quality (stratum) because interNet Services earlier than

V3.0B is in use.

This ensures that ADJUST-TIME jobs only change the system time

under the control of the NTP server.

2.20.5 Introduction of a default account number

From BS2000/OSD V6.0A onwards, the attribute LOGON-DEFAULT can

be assigned as an account number for each user. This is used

if no account number was entered at login. The command

/MODIFY-DEFAULT-ACCOUNT allows each user to determine his own

default account number.

2.20.6 Increase in the maximum paging area size

In BS2000/OSD V6.0A, the maximum paging area size has been

increased from 256 Gbyte to 4 Tbyte.

2.20.7 Advanced support of large SM Pubsets

The maximum size of a volume set is 4 Tbyte.

An SM Pubset can consist of up to 255 volume sets and can have

a maximum total size of approx. 1000 Tbyte. The previous limit

of 4 Tbyte for a user’s space allocation in an SM Pubset can

be exceeded. In the parameter TOTAL-SPACE, the command MODIFY-

USER-PUBSET-ATTRIBUTES for the operands PERM-SPACE-LIMITS, TEMP-

SPACE-LIMITS and WORK-SPACE-LIMITS has been expanded with the

value *UNLIMITED. The user’s space contingent is displayed with

the command SHOW-USER-ATTRIBUTES.

If in the case of part-qualified SHOW-FILE-ATTRIBUTES the

previous maximum value of 4 Tbyte is exceeded, the entire place

allocation is issued in units of 1000 PAM pages.

2.20.8 COPY-FILE for open UDS files

Open UDS database files affixed in the catalog with UDS_FAR bit

are protected by COPY-FILE until their physical end.

Copies of the database can therefore be produced in parallel

with the expansion of the UDS database.

Page 28

Download from Www.Somanuals.com. All Manuals Search And Download.

2.20.9 Catalog expansion commands

ADD-CATALOG-FILE

With this command up to 100 special catalogs can be created for

SM Pubsets in the catalog format “extra large” for migrated

files, job variables and private disk/volume files.

The names of the new catalog files have the form

:<catid>:$TSOS.TSOSCAT#xnn, where x refers to the special

catalog and nn is a consecutive numbering (00 – 99).

IMPORT-PUBSET

This command has been extended by the operand EXTRA-LARGE-CAT-

CONV. This operand determines whether the catalog is to be

converted into the new format “extra large”.

In the case of SM Pubsets all part catalogs are converted to

the new format.

Note: Pubsets in the catalog format “extra large” may no longer

be imported into BS2000/OSD < V6.0B.

SHOW-PUBSET-CATALOG-ALLOCATION

This command gives information about the format of a Pubset,

its catalogs and how full the catalogs are.

Contrary to the description in the BS2000/OSD V6.0 handbook,

within an SPVS network the commando can only be called up on

the master computer.

A detailed description of the commandos may be found in the

handbook “BS2000/OSD-BC V6.0 Commands”.

2.20.10 Extended STATUS information

With the use of the sub-system STATUS, the following extensions

are incorporated into STATUS commands:

SHOW-JOB-STATUS

When the operand INFORMATION=*STD/*ALL is entered, the CPU

time taken (with 10 digits to the left of the decimal point) is

displayed in an additional line CPU LONG: if the CPU time

exceeds the value 999999.9999.

In addition, INFORMATION=*ALL displays the PRINCIPAL names

recently introduced in SECOS V5.0, in a maximum of 128

characters in the line PRINCIPAL:.

The command output S-Variable has been extended by the two

variables CPU-USED-LONG and PRINCIPAL.

SHOW-USER-STATUS

As with SHOW-JOB-STATUS, when INFORMATION=*STD is entered, an

additional line CPU LONG: is displayed for long entries.

SHOW-SYSTEM-STATUS

The time at which an assignment was entered in the condition

queue is now displayed in the complete date format

yyyy-mm-dd.hhmm when INFORMATION=*WHEN-QUEUE is entered.

No change is made in the variable display, as there the date

was already complete.

Page 29

Download from Www.Somanuals.com. All Manuals Search And Download.

2.20.11 Extended commands for setting CCS defaults

CREATE-FILE / CREATE-FILE-GROUP

The CODED-CHARACTER-SET operand has been extended by the

USER-DEFAULT parameter which is simultaneously also the new

default value.

If this entry is not EDF03IRV, when a file is created the CCS

entry of the ID is taken over into the CCS name of the file. If

EDF03IRV is entered for the ID, the file is assigned the CCS

name *NONE, as previously. New LMS elements are analogously

assigned the CCS name of the library if no other value is

specified.

MODIFY-FILE-ATTRIBUTES / MODIFY-FILE-GROUP-ATTRIBUTES

The CODED-CHARACTER-SET operand was also extended by the

parameter USER-DEFAULT.

The default value remains as previously *UNCHANGED.

3 Technical information

3.1 Resource requirements

With respect to BS2000/OSD-BC V5.0, using BS2000/OSD-BC V6.0

requires hardly any more CPU performance (below 2%).

Main memory requirements:

You must clarify the main memory required with your sales repre-

sentative before ordering the machine. The recommended minimum

main memory required for using BS2000/OSD-BC V6.0 depends on the

model of the business server.

Increases in main memory requirements:

The additional static requirement compared with BS2000/OSD-BC

V5.0 is 3 - 5 MB. The additional dynamic requirement is approxi-

mately 30 - 50 KB per task, depending on the size of the user

space allocated.

Before changing versions, you should clarify any additional in-

stallation-related resource requirements with your regional ser-

vice

Disk storage space:

You will find the disk storage space required by the SOLIS2 de-

livery for BS2000/OSD-BC V6.0 in the SOLIS2 delivery letter. In

addition, you must also plan in the space required for the system

files (PAGING area, TSOSCAT, CONSLOGs, SERSLOGs, etc.).

Page 30

Download from Www.Somanuals.com. All Manuals Search And Download.

3.2 Software configuration

The following SOLIS correction levels are required in the source

version for BS2000/OSD-BC V6.0:

BS2000/OSD-BC V5.0 (as of correction level C71) or

BS2000/OSD-BC V4.0 (as of correction level A71)

If systems running BS2000/OSD-BC V5.0 or V4.0 are operated in

parallel, this correction level must also be used on these sys-

tems.

When using BS2000/OSD-BC V6.0, new versions of many of the system

level software products must also be used. The following table

shows the versions required for use under BS2000/OSD V6.0.

Further information is also available online under

http://extranet.fujitsu-siemens.com/com/products_supply/

bs2000/markarch/brochur/pf/bs2-osd6b-swkonf_pf0510d.pdf

and in English under

http://extranet.fujitsu-siemens.com/com/products_supply/

bs2000/markarch/brochur/pf/bs2-osd6b-swkonf_pf0510e.pdf

Product

Version

ADILOS

AID

ARCHIVE

ASSEMBH

C/C++

COBOL85

COBOL2000

COSMOS

CRTE

V6.4

V3.0/V3.1/V3.2

V7.0/V8.0

V1.2

V3.0/V3.1/V3.2

V2.3

V1.2/V1.3/V1.4

V15.0

V2.5/V2.6

V9.0

V1.0/V1.1

DAB

Distributed

Print Services

DRIVE

DRV

EDT

ESQL-COBOL

FDDRL

FDDRL-OS

FHS

FOR1

GOLEM

HIPLEX AF

HIPLEX MSCF

HSMS

HSMS-SV

IFG

interNet

Services

LEASY

LMS

V3.1

V3.0/V3.1

V16.6/V17.0

V2.0/V3.0

V15.0/V16.0

V8.2/V8.3

V2.2

V9.2

V3.2

V4.0

V7.0/V8.0

V8.1/V8.3

V3.0/V3.1/V3.2

V14.0

V6.1/V6.2

V3.3

V10.0/V11.0

V3.0

MAREN

NFS

Page 31

Download from Www.Somanuals.com. All Manuals Search And Download.

OMNIS

V8.3/V8.4

V3.3/V3.4

V1.2

OMNIS-MENU

openCRYPT

SERV

openFT

openNet Server

openUTM

PASCAL-XT

PASSAT

PLI1

V8.0/V9.0/V10.0

V3.0/V3.1/V3.2

V5.2/V5.3

V2.2

V6.2

V4.2

V2.7

V2.8/V2.9

V3.0

V1.2

V5.0

V15.0

V5.0/V6.0

V4.0

V3.4/V3.5

V6.0/V6.1

V15.0

V1.0/V1.1

V4.1

V2.2/V2.3/V2.4

V5.0/V5.1

V3.1/V3.2/V4.0/V5.0

V4.0/V5.0/V6.0/V6.1

V6.0

V7.8/V7.9

V3.0

V5.0

V6.0

V15.0

V13.1

V1.2

PCS

PERCON

PROP-TPM

PROP-XT

RAV

RFA

ROBAR

RPG3-XT

RSO

SBA-BS2

SCA

SCCA-BS2

SDF-A

SDF-P

SECOS

SESAM/SQL

SHC-OSD

openSM2

SORT

SPACEOPT

SSA-OUTM-BS2

SSA-SM2-BS2

SSC-BS2

TASKDATE

TIAM

TLS

UDS/SQL

VM2000

V2.3/V2.4/V2.5

V8.0/V9.0 (for S servers and SX servers)

At least the correction levels of the SOLIS delivery release from

19.05.2007 is required on the products of the software configura-

tion.

Note: BLSSERV V2.6 is the software prerequisite for running POSIX

applications produced with the POSIX Shared Library libdl.a,

which is delivered within correction package 2/2007.

3.3 Product installation

Installation must be carried out with the IMON installation moni-

tor. At least IMON V2.8 is required for installation.

IMON V2.8, V2.9 or V3.0 must be installed beforehand if it is not

already installed on the system.

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 de-

scribed in the IMON manual (or any available README file).

Page 32

Download from Www.Somanuals.com. All Manuals Search And Download.

Innovations in IMON V2.8:

The new CHECK-UNITS function allows you to check that the system

is complete, correct and up to date.

For customer-specific installations, all installation parameters

can be saved into a standardized parameter file and passed over

to IMON for all subsequent installations.

All //SHOW statements are extended with the STRUCTURE-OUTPUT op-

erand.

The /MODIFY-IMON-SCI command also works for parked software and

working files.

Special features of the POSIX installation are supported.

The UNDO function also supports PLAM libraries as SAVE-MEDIUM.

IMON V2.8B contains enhancements for dynamically activating sub-

systems in the running system.

You will find detailed information on all innovations in the

SYSFGM.IMON.028.E Release Notice.

Innovations in IMON V2.9

With the new command //REQUEST-CORRECTION-DELIVERY information

on correction deliveries or correction deliveries can be

requested.

When installing, parking and printing delivery documentation

from the delivery medium tape a difference is made between

Original SOLIS2 data carriers (DISTRIBUTION-MEDIUM=*SOLIS2-

VOLUME) and a copy produced by a customer (DISTRIBUTION-

MEDIUM=*LOCAL-VOLUME), which may also be found on a virtual

CentricStor volume. Instead of the previous installation

status “On Tape”, the statuses “On SOLIS2 Volume” and “On Local

Volume” are now displayed and on selection information is

offered.

During installation the new function “installation on the

basis of release notes” is availabe.

The two new commands SET-CUSTOMER-APPROVAL and RESET-CUSTOMER-

APPROVAL have been introduced for the release and withdrawal

of a delivery unit. For the operand UNIT-NAME, the instruction

INSTALL-UNITS has been extended by the value *CUSTOMER-APPROVED.

Detailed information on all innovations is provided by the

release notice SYSFGM.IMON.029.E.

Page 33

Download from Www.Somanuals.com. All Manuals Search And Download.

Innovations in IMON V3.0

With IMON V3.0, delivery units that are parked on a key-formatted

pubset can be installed on a non-key-formatted pubset.

Previously, the statement GENERATE-IDF displayed all delivery

units. Only the installed delivery units are now offered in the

dialog.

As of IMON V3.0, the TASKLIB and MACROLIB can also be installed

under a default user ID (DEFLUID system parameter) other than

TSOS. The parameter ZVDEFSUP in the IMON parameter file must be

set to "Y" for this.

Important note: if the parameter ZVDEFSUP is set to "Y", the two

files $TSOS.TASKLIB and $TSOS.MACROLIB must be copied under the

default user ID and deleted from under $TSOS before the next IMON

installation.

In addition, IMON V3.0 also contains preliminary functions for

future hardware platforms and BS2000/OSD-BC versions.

CRTE-BASYS:

The subsystem CRTEBASY of CRTE-BASYS V1.6 is available as a run-

time environment for BS2000-internal applications. This subsystem

should only be preloaded if this is recommended in the Release

Notice of another installed product.

By default the subsystem is loaded in upper class 4 memory. As an

alternative, the subsystem can also be loaded below 16 MB in

class 4 memory using the SYSSSC file with the extension LOW

(SYSSSC.CRTE-BASYS.016.LOW) if there is enough space available

there.

In addition, IMON copies the IC@RTSXS, IC@STLNK and IC@ULINK mod-

ules from the SYSLNK.CRTE-BASYS.016.CLIB library to CLIB. If no

$.CLIB file exists on the source system it is created by IMON.

This $.CLIB can be used for programs which were compiled with C

V2.0 or earlier.

The compatibility library SYSLNK.ILCS is also installed with

CRTE-BASYS.

If a default user ID other than TSOS is used (DEFLUID system pa-

rameter), it should be noted that during installation of CRTE-

BASYS not all libraries are automatically installed under the de-

fault user ID. When installation with IMON is completed, the

$TSOS.CLIB file must be copied to $<default_user_ID>.CLIB.

3.4 Product use

All conversion activities for BS2000/OSD-BC V6.0 are described in

the manual BS2000/OSD-BC V6.0 Migration Guide.

An update to BS2000/OSD-BC V6.0 is possible on the basis of

BS2000 versions OSD-BC V4.0 and V5.0. A first-time installation

of BS2000/OSD-BC V6.0 must be made for all earlier BS2000 ver-

sions. Configurations with V4.0 and V5.0 are possible with a

shared pubset network using MSCF.

Page 34

Download from Www.Somanuals.com. All Manuals Search And Download.

For availability reasons, you are strongly advised not to perform

an update installation on the active home pubset!

Certain hardware requirements must be fulfilled for a first-time

installation: the installed hardware configuration must be a su-

perset of the minimum configuration, i.e. it must include at

least one business server with input/output system and operator

terminal with associated service processor, plus one tape con-

troller and disk controller with one tape device and two disk de-

vices respectively.

Note: Only a two character tape mnemonic is allowed for the CD

drive of the SKP-X.

The CD drive of the SKP-X based on the PRIMERGY 470 hardware is

supported as a tape device as of SINIX-2000-Z V8.1A K818.4 and

BS2000/OSD V5.0C (device with type code E8) for reading CDs. This

allows the CD to be used as a data media for software deliveries.

CALENDAR:

The public holiday file (file for managing public holidays) must

be generated by systems support from the sample file

$TSOS.SYSDAT.CALENDAR.140.HOLIDAY or from an old public holiday

file:

/COPY-FILE FROM-FILE=$TSOS.SYSDAT.CALENDAR.150.HOLIDAY,

TO-FILE=$TSOS.SYSDAT.CALENDAR.HOLIDAY,PROTECTION=*SAME

File protection attributes:

Files with protection attributes intended to prevent deletion are

deleted without these protection attributes being taken into con-

sideration if a FREE-FOR-DELETION date was assigned and this has

expired (since BS2000/OSD-BC V3.0).

DEFLUID user ID and subsystems:

When upgrading subsystems whose start time is defined as 'BEFORE-

SYSTEM-READY' you should make sure that all files required for

starting these subsystems are available under $TSOS on the home

pubset SYSLNK, (SPMLNK, SPULNK), SYSREP, possibly also SYSMES,

SYSSDF (SPMSDF) and SYSSSI or SYSPAR).

The user ID for loading and starting programs, procedures etc.

that can be set via the class 2 system parameter 'DEFLUID' is not

supported for these subsystems.

MSGMAKER:

Files can be exchanged or included using /COPY-MSG-FILES or

/MERGE-MSG-FILES.

For performance reasons, large numbers of messages should be

processed with MERGE-MSG-FILES. This command is not listed when

MSGMAKER is started. However, by entering '?' in the 'command'

field of the screen mask you can switch to guided dialog. The

call can also be made via the batch interface. The output file

must always be empty.

Page 35

Download from Www.Somanuals.com. All Manuals Search And Download.

BCAM memory values:

The values for the maximum size of the resident and paging memory

for data transfers are calculated by BCAM at startup from the

size of the system memory (BS2000 MEMSIZE system value). The

relevant RESMEM and PAGMEM parameters should not be generally be

specified in the BCAM /DCSTART, /DCOPT and /BCMOD commands, but

should retain their values set by BCAM.

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.

Any adjustments to the memory values should only be made in

agreement with the responsible first level support.

Parameter service:

The following class 2 system parameters have been supplemented:

- FILECRYP

Defines which symmetric encryption method is used for converting

into an encrypted file with the ENCRYPT-FILE command.

Possible settings: AES (default) or DES.

The parameter can be changed during operation. The change has no

effect on files that are already encrypted.

- FREFCRYP

The optional parameter can be used to limit the number of crypto

passwords by only allowing new crypto passwords to be assigned

for files of a specific ID.

Only the crypto passwords of reference files from this specific

ID can be selected for files on other IDs.

The files from this ID are then assigned the same password as the

reference file.

- NTPSHIGH

The parameter can be assigned the value "N" (default) or "Y". In

the setting "Y", the time server NTP (NETWORK-TIMEPROTOCOL) is

specified as the highest priority time server in BS2000.

With the default setting "N", the time quality (stratum value) is

the deciding factor. NTP is assigned the highest priority if the

stratum value is from 1 to 4.

Note: The parameter may only be used on S servers.

- JTSHMEM

Defines how much memory space (in MB) JITSYS is to use for stor-

ing share compilations on SX servers.

Memory values between 0 and 255 MB can be specified. The default

is 64 MB.

The memory size specified with JTSHMEM is allocated immediately

when JITSYS is initialized.

Specifying JTSHMEM = 0 prevents share compilations from being

created.

Page 36

Download from Www.Somanuals.com. All Manuals Search And Download.

The following class 2 system parameters have been discontinued:

- CCPUNORM

- DELLOGLN

The following class 2 system parameters have been changed:

- JTABSMEM

Defines the maximum JIT memory on SX servers.

The memory is requested as resident and must therefore match the

memory available on the machine.

As of BS2000/OSD V6.0A, the parameter default is 0 and JIT calcu-

lates the maximum memory space from the two values for

MEMORY-SIZE and MINIMAL-MEMORY-SIZE.

The previous default value for JTABSMEM was 1200 MB.

The size of the requested memory is logged with the message

HJT0039 on the console.

The memory size can also be set to a fixed value by specifying a

value between 1 and 65535.

The parameter can be changed during operation.

- DMCMAXP

Defines the maximum number of entries in the MRSCAT of the home

pubset.

The new maximum value is 4096.

Changes to parameter sets:

- MEMORY parameter set

Discontinued parameter:

The parameter PAGING-GSSIZE is no longer available since the

function "Using global storage for page changing" has been dis-

continued.

New parameters:

The parameters BIG-PAGE-QUOTA and BIG-PAGE-SHRSIZE have been

introduced for using so-called "big pages" for JIT compilations

on SX150 business servers. A "big page" is taken to mean a

collection of 512 consecutive 8 KB sized frames in main memory.

BIG-PAGE-QUOTA defines the amount of main memory as a percentage

that is to be reserved for the big pages.

The default value is 40%.

BIG-PAGE-SHRSIZE defines the size of the "shared big pages" that

are used for the JIT compilation of shared programs. A range of

from 0 to 64 MB can be specified.

The default value is 64.

Page 37

Download from Www.Somanuals.com. All Manuals Search And Download.

New commands:

The percentage of main memory used for big pages can be changed

with the new command MODIFY-MEMORY-PARAMETERS. The command SHOW-

MEMORY-CONFIGURATION displays the current configuration of main

memory, including the use of big pages.

The two new parameters/commands are only available on SX150

servers. They are ignored on S systems and on SX100, SX130 and

SX140 servers.

The command MODIFY-MEMORY-PARAMETERS is rejected with the message

EMM2350.

- ISAM parameter set

Discontinued parameter:

The parameters GLBDFPS, DFPPROC, GLBDFPN are no longer evaluated

as of BS2000/OSD-BC V6.0B due to the modified default mechanism

for NK-ISAM-Pools

New parameter:

The new parameter MAXDSBN defines the maximum number of DATA

SPACES that are generated for task-independent NK-ISAM-Pools.

A range from 1 to 127 can be specified, the default value is 2.

System generation:

It is not necessary to generate the software for BS2000/OSD-BC

V6.0. The organization program SYSPRG.BS2.150 is part of the re-

lease unit BS2000-EXEC.

The utility program UGEN is no longer supplied.

The product IOGEN has been used for generating the I/O configura-

tion data since BS2000/OSD V5.0B.

As of IOGEN V15.0A, tape devices with DVC type CC (LTO-U2) can be

generated.

Note: If an IOCF with DVC type CC is used on a system with

BS2000/OSD V5.0B, the correction A0502425-001 is absolutely im-

perative.

System address space:

The limitation to system address space by the selected SYSSIZE

has been eliminated since BS2000/OSD-BC V5.0. The system also

uses less address space by moving internal tables into data

spaces.

Page 38

Download from Www.Somanuals.com. All Manuals Search And Download.

3.5 Obsolete functions (and those to be discontinued)

The following functions are no longer supported as of this ver-

sion:

- Paging on global memory

- The utility program UGEN is no longer supplied.

The internal name of the standard EXEC or the SYSSIZE is modified

with the procedure SYSPRC.BS2000-EXEC.150.

- Software product CRHP2AFP

As of SPOOL V4.8, the program is no longer part of the delivery

scope. CRHP2AFP converts HP print resources into APA print re-

sources. The function is covered redundantly by the OCE tool

TRANSCON.

The following function is supported for the last time as of this

version:

- The conversion of the file catalog to BS2000 V10.0 format with

the command ADD-MASTER-CATALOG-ENTRY (Operand NEXT-CATALOG-

EXPORT).

3.5.1 Obsolete macros

- none -

3.5.2 Obsolete commands

- none -

3.6 Incompatibilities to BS2000/OSD-BC V5.0C

- If the product interNet Services is used, the POSIX time can be

synchronized with an external time source via the Network Time

Protocol (NTP). If this time source supplies a "stratum" value

less than 5 in the NTP protocol, as of BS2000/OSD V6.0 and inter-

Net Services as of V3.0B, the BS2000 system time is also synchro-

nized with the time source.

- The checks of the ADDRSPACE allocation for an ID have been

intensified.

When the ADDRSPACE allocation is checked all class 6 memory pages

are now included, i.e. also pages in the memory pool and the 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 BS2000/OSD V5.0 can be reinstated with the optional

REP correction A0518446-001.

Page 39

Download from Www.Somanuals.com. All Manuals Search And Download.

3.7 Restrictions

- Processing encrypted files

Encrypted files cannot be accessed in BS2000/OSD < V6.0, they can

only be displayed and deleted.

However, in an SPVS network a slave access from within BS2000/OSD

V6.0 is possible even if BS2000/OSD < V6.0 is running on the mas-

ter system.

- Tape backups with blocks > 32 KB

In BS2000/OSD < V6.0, processing large tape blocks is rejected.

- In BS2000/OSD < V6.0, the four character mnemonic name is not

supported for tape devices. Using four character mnemonic names

can therefore lead to unforeseeable problems.

- Importing Data Pubsets in BS2000/OSD < V6.0

Pubsets once imported in BS2000/OSD V6.0 can only be

re-imported in BS2000/OSD < V4.0 indirectly, via an import

in BS2000/OSD V5.0 or BS2000/OSD V4.0, otherwise the process

is cancelled and the message SRM2016 displayed.

Note: For an import in BS2000/OSD V5.0 or BS2000/OSD V4.0 the REP

correction to A0507759 must be in use there.

Pubsets with an extended catalog (catalog format “extra large”)

can no longer be imported in BS2000/OSD < V6.0B, due to the

incompatibly modified catalog format.

- Unicode

Files with Unicode character sets cannot be processed in versions

earlier than BS2000/OSD-BC V6.0B (correction level B62).

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. As far as possible, documents for

the software problems should be provided in file form so that

they can be processed with diagnostic tools.

In the case of reproducible errors you should describe exactly

how the error can be reproduced. If possible, you should provide

procedures, enter jobs, execution logs etc. so that the error

situation can be reproduced.

Information on the system environment

In addition to the error documents, the following general

information is important for error diagnosis:

- operating system version number and revision level of

BS2000/OSD-BC (loader version and any modifications in

BS2000)

- version numbers of any subsystems, OSD-BC version-independent

products or TU programs contributing to the problem together

with their correction levels or REP files

- information as to which system exits were active

- information on the connected hardware peripherals

Page 40

Download from Www.Somanuals.com. All Manuals Search And Download.

Document types

The following documents will be needed, depending on the situa-

tion:

- SLED

(following a system crash)

- SNAPFILE

- SYSTEMDUMP

(following a system dump message)

- SYSOUT/SYSLST logs

- STARTUP parameter files

- USERDUMP

- Diagnose-Dump (IDIAS call: CREATE-SYSTEM-DUMP <tsn>)

- SERSLOG file

- CONSLOG file

- SYSTEMREPFILE

- Rep files of any subsystems involved and separate products

- HERSFILE and possibly IOTRACE for input/output problems

or device error messages

User documents

Depending on the error boundary conditions, the following docu-

ments will be required:

user files, tapes, procedures, job streams (including job class

information), programs (source listing, load module and librar-

ies, execution log for the process, printer logs, as far as pos-

sible in file form).

In the case of functional errors information on all commands,

program inputs etc. is essential.

Documents needed for special problems

For performance problems and problems in task management:

- possibly COSMOS listing or tape or SM2 reports.

For job management problems:

- SHOW-JOB-CLASS or SHOW-JOB-STREAM listing

- compiler listing from your own scheduler

- SJMSFILE

- SYSTEM-JOBPOOL

- entry in the user catalog of the user IDs affected

- 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': DAMP)

- CONSLOG file

Page 41

Download from Www.Somanuals.com. All Manuals Search And Download.

For BCAM problems:

- activate all DCM traces with /DCDIAG DCM.,MODE=SAVE and

after reproducing the error, save the generated trace

files S.DCTRAC.* with /DCDIAG DCM.,MODE=CLOSE or submit

the diagnostic information to main memory with

/DCDIAG DCM.,MODE=HOLD and evaluate it with ASTRID.

For problems at the hardware and software interface:

- HERSFILE

- Hardware and software configuration

- possibly IOTRACE listing.

For tape problems:

- if possible you should send in the original tape for

error diagnosis, otherwise you should at least provide

a listing of all tape labels and the first data blocks

- SYSOUT log and CONSLOG file

For SPD problems:

- dump of the VTOC area

- NDMDAMP

- CONSLOG files of all systems involved

For IORM problems:

- IORM dump

- CONSLOG file

If problems occur with the IORM DPAV or IOLVM functions, under

VM operation these documents are required from both the guest

and the monitor system.

Final note

The above description does not contain any information on gener-

ating documents in conjunction with using BS2000 tracers. Please

consult the reference manuals of the relevant tracers for this.

Page 42

Download from Www.Somanuals.com. All Manuals Search And Download.

4 Hardware support

4.1 Central units

4.1.1 changed support

The following business servers are supported in BS2000/OSD-BC

V6.0. A prerequisite for using BS2000/OSD V6.0 on SX servers is

the hardware abstraction layer X2000 V3.0 based on Solaris V8 as

the base system.

Business Server S110

Business Server S115

Business Server S120

Business Server S130

Business Server S135

Business Server S140

Business Server S145

Business Server S150

Business Server S155

Business Server S160

Business Server S165

Business Server S170

Business Server S180

Business Server S190

Business Server S200

Business Server SX100

Business Server SX130

Business Server SX140

Business Server SX150

The following versions of the HCP (Hardware Control Program) at

least are required for using BS2000/OSD-BC V6.0.

- E05L01A-03R+008

- E20L02A-01N+011

- E45L01G-01R+008

- E02L01F-02C+021

- E25L01G-02N+111

- E39L01G-02N+122

- E40L01G-02Q+016

- E14L01S-02Q+000

- E60L02G-02E+120

for Business Server S110

for Business Server S115

for Business Server S120

for Business Server S130

for Business Server S135 and S150

for Business Server S160

for Business Server S140 and S170 *

for Global Store SSU-4

for Business Server S145, S155,

S180, S190

- E16L02S-02E+011

- E70l01G-01U+039

for Global Store SSU-5

for Business Server S165 and S200

Notes:

If you want to use fibre channel, before using the HCP versions

marked with *, a new generation with an IOGEN version as of

V14.0C is mandatory (inhibition of I/O interface time monitor-

ing).

The HCP version required for using BS2000/OSD-BC V6.0A can be ob-

tained from your regional service.

Page 43

Download from Www.Somanuals.com. All Manuals Search And Download.

4.1.2 Discontinued support

- none -

4.1.3 Extended support

- none -

4.2 Channels

4.2.1 Changed support

FC connections are supported by the following business servers

with F-CON capability via the FC channel:

S120, S140, S145, S155, S165, S170, S180, S190 and S200

(the IPL of FC is not possible on S120)

See the separate Release Notice SYSFGM.BS2XC.022.E for SX series

business servers.

4.2.2 Discontinued support

- none -

4.3 FC switches

The following FC switches are supported by S servers:

FCSW-8P2GB01-Z

FCSW-16P2GB01-Z

FCSW-32P2GB01-Z

FCSW-64P2GB01-Z

FCSW-128P2GB01-Z

FCSW-8P2G3250-Z

FCSW-16P2G3850-Z

FCSW-32P2G3900

FCSWR-32P4100L

FCSWR-32P4100E

FCSW-32P4116

FCSW-128P24032

FCSW-8P200EL

FSCWR-8P200EL

FCSW-8P200EE

FSCWR-8P200EE

FCSW-16P200EL

FSCWR-16P200EL

FCSW-16P200EE

FSCWR-16P200EE

FCSW-64P4932L

FCSW-64P4932E

FCSW-24P5000L

FCSW-24P5000E

PSFS-B641

PSFS-BE084

PSFS-B081

PSFS-B161

Page 44

Download from Www.Somanuals.com. All Manuals Search And Download.

See the separate Release Notice SYSFGM.BS2XC.022.E for SX series

business servers.

4.4 Disk controllers

4.4.1 Changed support

No changes have been made to the support for disk controllers

with respect to BS2000/OSD V5.0C.

The following models of the Symmetrix controllers from EMC2 are

supported in BS2000/OSD-BC V6.0:

5330, 5430, 5630, 5700, 5830, 5930

8230, 8430, 8530, 8730, 8830,

DMX800, DMX801, DMX1000, DMX2000

DMX3000

DMX-3

DMX-4

up to microcode 5267

up to microcode 5568

as of microcode 5669

as of microcode 5670

as of microcode 5771

as of microcode 5772

See the separate Release Notice SYSFGM.BS2XC.022.E for SX series

business servers.

4.4.2 Discontinued support

- none -

4.5 Magnetic tape devices

4.5.1 Changed support

The following magnetic tape devices are supported in BS2000/OSD-

BC V6.0 on S servers: the magnetic tape devices supported by SX

servers are described in the Release Notice SYSFGM.BS2XC.021.E.

- the MTC systems

3588-M1, 3588-M2, 3588-GL

3590-A10, 3590-A20 (controllers)

3590-B20, 3590-B40 (drives)

3590-C10, 3590-C11, 3590-C22 (units)

3590-C1A, 3590-C2A units for the 3594 archive system

3591-B1, 3591-B2, 3591-B3, 3591-B4,

3591-B1A, 3591-B1GL, 3591-BU, 3591-EX

- the MTC archive systems

3594-L10, 3594-L12

3560

AML/2

AML/E

AML/J

Scalar 1000, Scalar I2000 with LTO2

Scalar 10K with LTO2, connected via channel type FC

Scalar 10K with 3590/3591, connected via SPCC, channel type S

- CentricStor VTC (Virtual Tape Controller)

CentricStor SBU (Smart Backup Unit)

- CentricStor VTA (Virtual Tape Appliance)

VTA-1000, VTA-2000, VTA-3000, VTA-4000, VTA-5000

Page 45

Download from Www.Somanuals.com. All Manuals Search And Download.

4.5.2 Discontinued support

The following is no longer supported in BS2000/OSD-BC V6.0:

- the magnetic tape device 3505 via SPCC

4.6 Printers

4.6.1 Changed support

The following printers are supported in BS2000/OSD-BC V6.0:

- the fast- / tape printers

3348-120x, 3349-120x

- the laser printers

3351-23, 3351-231

3353-23, 3353-231

2050-2x, 2050-1x

2075-2x, 2075-1x

2090-4, 2090-Lx, 2090-2

2140-4, 2140-2

2240-4, 2240-2

PAGESTREAM 55, 75, 88, 110DC, 145, 158DC, 200DSC, 235,

350, 440, 470, 700, 880,

Vario Print 5100, 5160

Vario Stream 6100, 7000, 9210, 9220

4.7 Other peripherals

4.7.1 Changed support

The following are supported in BS2000/OSD V6.0:

- terminals

Time Server 3920

ATOP 3925

Radio clock 3919

- LAN channel connection HNC 91850

HNC 91851

HNC 91852

- encryption:

openCrypt-BOX

- DUE pre-processor:

9681, 9686, 9688 und 9689

with central unit connection controller

ZAS-I 9631-6x

4.7.2 Discontinued support

The following are no longer supported in BS2000/OSD-BC V6.0:

- DUE pre-processor 75009-4X, 75409-X

- Connection Director SCD 3950-4

Page 46

Download from Www.Somanuals.com. All Manuals Search And Download.

Electro Voice Portable Speaker QRx153 User Manual
Estate Cordless Telephone TERZOWOY User Manual
Eton Radio FR200G User Manual
Extron electronic Network Card 68 1405 01 User Manual
Extron electronic Portable Speaker SPA 12 AAP User Manual
Extron electronic Power Supply EPS 1210 B User Manual
Faber Ventilation Hood 630000815 User Manual
Fishman Musical Instrument Loudbox 100 User Manual
Geemarc Cordless Telephone CL10 User Manual
Gemini CD Player CD 4700 E User Manual