Français dropdown-ico

Fujitsu BS2OSD manuel d'utilisation

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47

Aller à la page of

Les manuels d’utilisation similaires

Un bon manuel d’utilisation

Les règles imposent au revendeur l'obligation de fournir à l'acheteur, avec des marchandises, le manuel d’utilisation Fujitsu BS2OSD. Le manque du manuel d’utilisation ou les informations incorrectes fournies au consommateur sont à la base d'une plainte pour non-conformité du dispositif avec le contrat. Conformément à la loi, l’inclusion du manuel d’utilisation sous une forme autre que le papier est autorisée, ce qui est souvent utilisé récemment, en incluant la forme graphique ou électronique du manuel Fujitsu BS2OSD ou les vidéos d'instruction pour les utilisateurs. La condition est son caractère lisible et compréhensible.

Qu'est ce que le manuel d’utilisation?

Le mot vient du latin "Instructio", à savoir organiser. Ainsi, le manuel d’utilisation Fujitsu BS2OSD décrit les étapes de la procédure. Le but du manuel d’utilisation est d’instruire, de faciliter le démarrage, l'utilisation de l'équipement ou l'exécution des actions spécifiques. Le manuel d’utilisation est une collection d'informations sur l'objet/service, une indice.

Malheureusement, peu d'utilisateurs prennent le temps de lire le manuel d’utilisation, et un bon manuel permet non seulement d’apprendre à connaître un certain nombre de fonctionnalités supplémentaires du dispositif acheté, mais aussi éviter la majorité des défaillances.

Donc, ce qui devrait contenir le manuel parfait?

Tout d'abord, le manuel d’utilisation Fujitsu BS2OSD devrait contenir:
- informations sur les caractéristiques techniques du dispositif Fujitsu BS2OSD
- nom du fabricant et année de fabrication Fujitsu BS2OSD
- instructions d'utilisation, de réglage et d’entretien de l'équipement Fujitsu BS2OSD
- signes de sécurité et attestations confirmant la conformité avec les normes pertinentes

Pourquoi nous ne lisons pas les manuels d’utilisation?

Habituellement, cela est dû au manque de temps et de certitude quant à la fonctionnalité spécifique de l'équipement acheté. Malheureusement, la connexion et le démarrage Fujitsu BS2OSD ne suffisent pas. Le manuel d’utilisation contient un certain nombre de lignes directrices concernant les fonctionnalités spécifiques, la sécurité, les méthodes d'entretien (même les moyens qui doivent être utilisés), les défauts possibles Fujitsu BS2OSD et les moyens de résoudre des problèmes communs lors de l'utilisation. Enfin, le manuel contient les coordonnées du service Fujitsu en l'absence de l'efficacité des solutions proposées. Actuellement, les manuels d’utilisation sous la forme d'animations intéressantes et de vidéos pédagogiques qui sont meilleurs que la brochure, sont très populaires. Ce type de manuel permet à l'utilisateur de voir toute la vidéo d'instruction sans sauter les spécifications et les descriptions techniques compliquées Fujitsu BS2OSD, comme c’est le cas pour la version papier.

Pourquoi lire le manuel d’utilisation?

Tout d'abord, il contient la réponse sur la structure, les possibilités du dispositif Fujitsu BS2OSD, l'utilisation de divers accessoires et une gamme d'informations pour profiter pleinement de toutes les fonctionnalités et commodités.

Après un achat réussi de l’équipement/dispositif, prenez un moment pour vous familiariser avec toutes les parties du manuel d'utilisation Fujitsu BS2OSD. À l'heure actuelle, ils sont soigneusement préparés et traduits pour qu'ils soient non seulement compréhensibles pour les utilisateurs, mais pour qu’ils remplissent leur fonction de base de l'information et d’aide.

Table des matières du manuel d’utilisation

  • Page 1

    Fujitsu Siemens Computers BS2OSD(BS2000/OSD) *2 Version 6.0B *7 April 2008 Release Notice Copyright (C) Fujitsu Siemens Computers GmbH 2008 All rights reserved[...]

  • Page 2

    Page 1 *2 Release Notice BS2OSD V6.0B 1 General 3 1.1 Ordering 4 1.2 Delivery 4 1.3 Documentation 7 2 Software extensions 10 2.1 Adaptations to CFCS 4.3 10 2.2 Enhancement of multiprocessor perfor mance via AS/RM lock breakup 10 2.3 Data spac es 10 2.4 Performance enhancement of CCOPY in conjunction with HSMS V7.0A and ARCHIVE V7.0B 10 2.5 Function[...]

  • Page 3

    Page 2 3.4 Product use 34 3.5 Obsolete functions (and those to be discontinued ) 39 3.5.1 Obsolete macros 39 3.5.2 Obsolete commands 39 3.6 Incompatibilities to BS2000/OSD-BC V5.0C 39 3.7 Restrictions 40 3.8 Procedure in the event of errors 40 4 Hardware support 43 4.1 Central units 43 4.1.1 changed sup port 43 4.1.2 Discontinued support 44 4.1.3 E[...]

  • Page 4

    Page 3 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&apo[...]

  • Page 5

    Page 4 *7 SYSFGM.PERL.058.E SYSFGM.PLAM.034.e SYSFGM.POSIX-BC.060.E SYSFGM.PTHREADS.010.E SYSFGM.SDF.046.E *1 SYSFGM.SIR.150.E SYSFGM.SNMP-LIGHT.050.E *1 SYSFGM.SNRTP.010.E SYSFGM.SPCONV.011.E *5 SYSFGM.SPOOL.048.E SYSFGM.STRT.150.E *7 SYSFGM.TOMCAT.055.D *5 SYSFGM.WEBTRANS-OSD.071.E *5 The Release Notice SYSFGM.BS2XC.022.E must also be noted for S[...]

  • Page 6

    Page 5 *2 BS2CP 15.0B *2 BS2000-EXEC 15.0B BUILDER 1.0A C-TPR-LZS 2.3A CALENDAR 15.0A CALENDAR-TU 15.0A CAPRI 1.5A *2 CCOPY 5.0B *2 COSMOS-BC 15.0B CPR 15.0A DAMP 4.4A Utility program DCADITO 15.0A Utility program DIV 15.0A DIVTRAC 15.0A DLMUSER 14.0C DPAGE 15.0A Utility program DWS 11.0A *2 ELFE 15.0B Utility program ESS-DOORS 12.1A FASTPAM 15.0A [...]

  • Page 7

    Page 6 *2 SMPGEN-S 15.0B Utility program *2 SMPGEN-U 15.0B *2 SPCCNTRL 15.0B Utility program *5 STATUS 15.1B *2 SRPMNUC 15.0B *5 SYSFILE 15.0C TANGBAS 1.3A TANGRAM 1.3A TPCOMP2 15.0A Utility program TPRLAM 15.0A TSOSLNK 21.0E Utility program TULAM 15.0A UTM-SM2 15.0A *2 VOLIN 15.0B Utility program WARTOPT 15.0B BS2GA.CRTE-BAS *4 CRTE-BAS 1.6A *4 CR[...]

  • Page 8

    Page 7 BS2GA.SDF DISPLAY 1.0B FHS-TPR 8.2D SDF 4.6A SDF-CONV 3.0B SDF-I 4.1A *5 SDF-P-BASYS 2.4A SDF-PAR 1.1A SDF-SFC 3.1A SDF-SRV 3.0C SDF-U 4.1F VAS 2.3B BS2GA.SIR *2 SIR 15.0B BS2GA.SNMP SNMP-LIGHT 5.0A BS2GA.SPOOL *7 BS2ZIP 1.2A PRMMAN 1.3A PRMPRES 1.2A SNRTP 1.0B SPCONV 1.1A *5 SPOOL 4.8A SPOOLSYS 2.2A SPSERVE 2.8A SPSRVMAN 2.3A BS2GA.STRT *2 [...]

  • Page 9

    Page 8 The documentation for the remaining technical delivery units is listed in the respective Release Notices. Core documentation TITLE ORDER NUMBER GERMAN ENGLISH ADAM U 3563-J-Z125-5 -5-76 * BINDER 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 U412[...]

  • Page 10

    Page 9 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.c[...]

  • Page 11

    Page 10 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 loc[...]

  • Page 12

    Page 11 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 si[...]

  • Page 13

    Page 12 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 b[...]

  • Page 14

    Page 13 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-[...]

  • Page 15

    Page 14 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 base[...]

  • Page 16

    Page 15 *2 For SF and SM Pubsets, the maximum catalog file size will be *2 increased to 32008 4K blocks, representing a 98% enlargement. *2 In the case of SM Pubsets, the special catalogs #MIN, #JVC *2 and #PTV can also be shared out among upto 100 catalog files, *2 which corresponds to a new maximum catalog size of 32008 4K *2 blocks and a 187-fol[...]

  • Page 17

    Page 16 2.14.2 Self-configuring NK-ISAM Pools in Data Spaces *2 To further relieve the system address area, NK-ISAM files are *2 buffered in Data Spaces. At the same time, buffer areas are *2 created strictly for individual files and no longer for file *2 groups, thus reducing the number of lock conflicts over access *2 to the buffer areas. The buf[...]

  • Page 18

    Page 17 2.15 New functions of BS2000/OSD V6.0B with Correction Package 1/2006 2.15.1 JENV V5.0 *3 BS2000/OSD with the JENV V5.0 component has been certified as *3 JAVA COMPATIBLE by Sun Microsystems, Inc. This provides the *3 assurance that Java programs can run on BS2000/OSD without re- *3 compilation or other modifications. *3 The current version[...]

  • Page 19

    Page 18 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) *4 The new utility program IORM facilitates autonomous, dynamic *4 control of the I/O resources, devices, controllers, channels *4 (type S and type FC) and paths. Both S and SX servers are *4 supported in native a[...]

  • Page 20

    Page 19 *4 Dynamic I/O load distribution for disks on the FC channel of *4 the S server (DPAV) *4 Only one I/O can be executed at any particular time on a disk. *4 If several applications with a large number of I/Os use the same *4 disk, this can lead to high wait times. *4 Until now, static PAV (Parallel Access Volume) has been used on *4 S server[...]

  • Page 21

    Page 20 *4 Limiting the I/O inclusion of single VM2000 guest systems (IOLVM) *4 Less important guest systems that have intensive I/O activity, *4 can severely impede other, much more important guest systems *4 that use the same I/O resources. *4 The IORM function can detect such conflict situations and *4 intervene predictively. To do this, IORM co[...]

  • Page 22

    Page 21 *4 data. As of BS2000/OSD-BC V6.0, a new system behavior will *4 therefore be introduced with which the default value of the CCS *4 name of a file is determined. *4 Note: *4 ISO8859-x variants should not be used as a system or user *4 character set since all programs in BS2000 assume that the *4 data is provided with a so-called invariant E[...]

  • Page 23

    Page 22 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 *5 Due to new EU directives, the previously supported character sets *5 are no longer sufficient in the medium term. As of BS2000/OSD-BC *5 V6.0B (correction level B62), support for Unicode supplements the *5 EBCDIC ch[...]

  • Page 24

    Page 23 *5 The UTF codes (Unicode Transformation Format) UTF-8, UTF-16 (2 *5 Byte) and UTF-E that follows UTF-EBCDIC from IBM are supported in *5 BS2000/OSD. 2.17.2 Support for Unicode by the software products *5 The software environment required for supporting the Unicode *5 functionality is provided in BS2000/OSD-BC V6.0 and V7.0. *5 The support [...]

  • Page 25

    Page 24 2.17.3 Improved SAN support (SANCHECK function) *5 Since the introduction of the fibre channel, the FC connection *5 technology SAN (Storage Area Network) is being used increasingly *5 for connecting Symmetrix storage subsystems and magnetic tape de- *5 vices (CentricStor and LTO). The previous control functions in *5 BS2000/OSD only allow [...]

  • Page 26

    Page 25 *5 The following tuning parameters can be modified dynamically: *5 FORCEDTERM Forces termination of the subsystem. *5 HDSTNI Number of server tasks for asynchronous I/Os. *5 HDPTNI Maximum number of mounted local file systems. *5 HEAPSZ Maximum possible value for brk() system call. *5 MAXTIMERC Maximum number of seconds for terminating *5 r[...]

  • Page 27

    Page 26 2.18 New functions in BS2000/OSD V6.0B with Correction Package 2/2007 *6 BS2000/OSD V6.0B correction level B72 does not contain functional *6 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 *7 In 2007, December release was given for the DMX-4 series S[...]

  • Page 28

    Page 27 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 task[...]

  • Page 29

    Page 28 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 i[...]

  • Page 30

    Page 29 2.20.9 Catalog expansion commands *2 ADD-CATALOG-FILE *2 With this command up to 100 special catalogs can be created for *2 SM Pubsets in the catalog format “extra large” for migrated *2 files, job variables and private disk/volume files. *2 The names of the new catalog files have the form *2 :<catid>:$TSOS.TSOSCAT#xnn, where x re[...]

  • Page 31

    Page 30 2.20.11 Extended commands for setting CCS defaults *4 CREATE-FILE / CREATE-FILE-GROUP *4 The CODED-CHARACTER-SET operand has been extended by the *4 USER-DEFAULT parameter which is simultaneously also the new *4 default value. *4 If this entry is not EDF03IRV, when a file is created the CCS *4 entry of the ID is taken over into the CCS name[...]

  • Page 32

    Page 31 3.2 Software configuration The following SOLIS correction levels are required in the source version for BS2000/OSD-BC V6.0: *5 BS2000/OSD-BC V5.0 (as of correction level C71) or *5 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 o[...]

  • Page 33

    Page 32 *2 OMNIS V8.3/V8.4 *2 OMNIS-MENU V3.3/V3.4 *1 openCRYPT V1.2 SERV *5 openFT V8.0/V9.0/V10.0 *5 openNet Server V3.0/V3.1/V3.2 *5 openUTM V5.2/V5.3 *1 PASCAL-XT V2.2 *1 PASSAT V6.2 *1 PLI1 V4.2 *1 PCS V2.7 *5 PERCON V2.8/V2.9 *1 PROP-TPM V3.0 *1 PROP-XT V1.2 *1 RAV V5.0 *1 RFA V15.0 *5 ROBAR V5.0/V6.0 *1 RPG3-XT V4.0 *5 RSO V3.4/V3.5 *1 SBA-B[...]

  • Page 34

    Page 33 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[...]

  • Page 35

    Page 34 *4 Innovations in IMON V3.0 *4 With IMON V3.0, delivery units that are parked on a key-formatted *4 pubset can be installed on a non-key-formatted pubset. *4 Previously, the statement GENERATE-IDF displayed all delivery *4 units. Only the installed delivery units are now offered in the *4 dialog. *4 As of IMON V3.0, the TASKLIB and MACROLIB[...]

  • Page 36

    Page 35 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 inpu[...]

  • Page 37

    Page 36 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 shou[...]

  • Page 38

    Page 37 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 defa[...]

  • Page 39

    Page 38 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. *1 The two new parameters/commands are only available on SX150 *1 servers. They are ignored on [...]

  • Page 40

    Page 39 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. *5 - Software product CRHP2AFP *5[...]

  • Page 41

    Page 40 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/O[...]

  • Page 42

    Page 41 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 [...]

  • Page 43

    Page 42 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: - H[...]

  • Page 44

    Page 43 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 *2 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 [...]

  • Page 45

    Page 44 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: *5 S120, S140, S145, S155, S165, S170, S180, S190 and S200 (the IPL of FC is not possible on S120) *5 See the separate Release Notice [...]

  • Page 46

    Page 45 *5 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, 57[...]

  • Page 47

    Page 46 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[...]