IBM DB2 V8 Bedienungsanleitung

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
48
49
50
51

Zur Seite of

Richtige Gebrauchsanleitung

Die Vorschriften verpflichten den Verkäufer zur Übertragung der Gebrauchsanleitung IBM DB2 V8 an den Erwerber, zusammen mit der Ware. Eine fehlende Anleitung oder falsche Informationen, die dem Verbraucher übertragen werden, bilden eine Grundlage für eine Reklamation aufgrund Unstimmigkeit des Geräts mit dem Vertrag. Rechtsmäßig lässt man das Anfügen einer Gebrauchsanleitung in anderer Form als Papierform zu, was letztens sehr oft genutzt wird, indem man eine grafische oder elektronische Anleitung von IBM DB2 V8, sowie Anleitungsvideos für Nutzer beifügt. Die Bedingung ist, dass ihre Form leserlich und verständlich ist.

Was ist eine Gebrauchsanleitung?

Das Wort kommt vom lateinischen „instructio”, d.h. ordnen. Demnach kann man in der Anleitung IBM DB2 V8 die Beschreibung der Etappen der Vorgehensweisen finden. Das Ziel der Anleitung ist die Belehrung, Vereinfachung des Starts, der Nutzung des Geräts oder auch der Ausführung bestimmter Tätigkeiten. Die Anleitung ist eine Sammlung von Informationen über ein Gegenstand/eine Dienstleistung, ein Hinweis.

Leider widmen nicht viele Nutzer ihre Zeit der Gebrauchsanleitung IBM DB2 V8. Eine gute Gebrauchsanleitung erlaubt nicht nur eine Reihe zusätzlicher Funktionen des gekauften Geräts kennenzulernen, sondern hilft dabei viele Fehler zu vermeiden.

Was sollte also eine ideale Gebrauchsanleitung beinhalten?

Die Gebrauchsanleitung IBM DB2 V8 sollte vor allem folgendes enthalten:
- Informationen über technische Daten des Geräts IBM DB2 V8
- Den Namen des Produzenten und das Produktionsjahr des Geräts IBM DB2 V8
- Grundsätze der Bedienung, Regulierung und Wartung des Geräts IBM DB2 V8
- Sicherheitszeichen und Zertifikate, die die Übereinstimmung mit entsprechenden Normen bestätigen

Warum lesen wir keine Gebrauchsanleitungen?

Der Grund dafür ist die fehlende Zeit und die Sicherheit, was die bestimmten Funktionen der gekauften Geräte angeht. Leider ist das Anschließen und Starten von IBM DB2 V8 zu wenig. Eine Anleitung beinhaltet eine Reihe von Hinweisen bezüglich bestimmter Funktionen, Sicherheitsgrundsätze, Wartungsarten (sogar das, welche Mittel man benutzen sollte), eventueller Fehler von IBM DB2 V8 und Lösungsarten für Probleme, die während der Nutzung auftreten könnten. Immerhin kann man in der Gebrauchsanleitung die Kontaktnummer zum Service IBM finden, wenn die vorgeschlagenen Lösungen nicht wirksam sind. Aktuell erfreuen sich Anleitungen in Form von interessanten Animationen oder Videoanleitungen an Popularität, die den Nutzer besser ansprechen als eine Broschüre. Diese Art von Anleitung gibt garantiert, dass der Nutzer sich das ganze Video anschaut, ohne die spezifizierten und komplizierten technischen Beschreibungen von IBM DB2 V8 zu überspringen, wie es bei der Papierform passiert.

Warum sollte man Gebrauchsanleitungen lesen?

In der Gebrauchsanleitung finden wir vor allem die Antwort über den Bau sowie die Möglichkeiten des Geräts IBM DB2 V8, über die Nutzung bestimmter Accessoires und eine Reihe von Informationen, die erlauben, jegliche Funktionen und Bequemlichkeiten zu nutzen.

Nach dem gelungenen Kauf des Geräts, sollte man einige Zeit für das Kennenlernen jedes Teils der Anleitung von IBM DB2 V8 widmen. Aktuell sind sie genau vorbereitet oder übersetzt, damit sie nicht nur verständlich für die Nutzer sind, aber auch ihre grundliegende Hilfs-Informations-Funktion erfüllen.

Inhaltsverzeichnis der Gebrauchsanleitungen

  • Seite 1

    Planning And Preparation Guide For SAP NetWeaver 7.0: z/OS Implementation: DB2 V8 DB2 9 Albert D. Rodi Consulting IT Specialist IBM Solution Technical Sales International Business Machines Corporation 1503 LBJ Freeway Dallas, TX 75234 (972) 280-4791 or TieLine 8-542-4791 E-mail: adrodi@us.ibm.com Copyright 2006 IBM Solutions Technical Sales (STS) 1[...]

  • Seite 2

    Trademarks The following are trademarks of the International Business Machines Corporation in the United States and/or other countries AIX* On Demand Business Logo CICS* PR/SM DB2* Parallel Sysplex* DB2 Universal Database pSeries* e-business logo System z9 Enterprise Storage Server* System z GDPS* Tivoli* Geographically Dispersed Parallel Sysplex x[...]

  • Seite 3

    C ontents I General Preparation Steps II z/OS Hardware Preparation III AIX Hardware Preparation IV z/OS Software Preparation V DB2 and DB2 Connect Preparation VI DB2 Related OSS Notes VII AIX Software Preparation VIII Windows NT Hardware/Software Preparation IX SAP Installation Preparation X Sample BPXPARMxx Member XI Sample DB2 DSNZPARMS XII TCP/I[...]

  • Seite 4

    What is new with SAP Web Application Server 7.0 ? • The z/OS USS Application Server is no longer supported. However you can install the Central Services on USS as part of a High Availability solution. • rfcoscol is replaced by sapccmsr and SAPCL  Transaction ST04 allows monitoring of remote DB2 subsystems  The mass processing tool to conv[...]

  • Seite 5

    1. Identify the technical implementation team members: z/OS System Programmer z Linux Administrator Security Administrator Unix System Serv ices Administrator Storage Administrator Network Administrator AIX/Windows Administrator DB2 DBA DB2 Systems Programmer R/3 Administrator z/OS Capacity Planning & Performance Administrator 2. Available Docu[...]

  • Seite 6

    - Installation of SAP Solution Manager - Configuration of SAP Solution Manager - Front End Installation - Homogeneous and Heterogeneous System Copy for SAP Systems based on NetWeaver 2004s 3. Available Documentation (IBM): - High Availability for SAP on zSeries Using Autonomic Computing Technologies (SC33- 8206) - SAP on DB2 UDB for OS/390 and z/OS[...]

  • Seite 7

    (IBM SG24- 6287) - DB2 UDB for z/OS V8: Through the Looking Glass and What SAP Found There (IBM SG24- 7088) - Disaster Recovery with DB2 UDB for z/OS (SG24- 6370) - DB2 Performance Expert for z/OS (SG24- 6867) - DB2 UDB for z/OS Version 8 Technical Preview (SG24- 6871) - Distributed Functions of DB2 for z/OS and OS/390 (SG24- 6952) - SAP on DB2 for[...]

  • Seite 8

    5. Important OSS Notes: (service.sap.com/ notes ) 660528: Requirements to run SAP NetWeaver on zSeries 661260: Transports and Support Pac kages for 6.40 728743: zSeries: Release of DB2 V8 for SAP Components 746924: Planning information for customers with SAP on zSeries 606682: High availability and automation solution for Linux zSeries 563060: DB2/[...]

  • Seite 9

    797084: SUSE Linux Enterprise Server 9: Installation Note 892818: Application servers on Linux for zSeries: Settings 821904: Separating SCS instances for ABAP and J2EE 686905: DB2 for z/OS: DDIC Corrections (6.40, 7.0) 818291: zSeries: Windows 64 bit app server 144864: SAP Remote Services: Technical preparation 6. Prepare a project plan for the imp[...]

  • Seite 10

    II z/OS Hardware Preparation 1. Review Checklist in Installation Manual and at service.sap.com/platforms for supported z/OS server models . 2. Determine Hardware Configuration by completing the SAP sizing questionnaire for R/3 . Review the sizing deliverable document prepared by the IBM ISV TechLine Sizing Department in conjunction with your IBM Sa[...]

  • Seite 11

    1.2 GB (Temporary installation disk space) 2 x zLinux Guest Memory (Swap Space) 4.3 GB (temporary disk space for every Installation DVD to be copied locally for installation) 13GB (disk space for the SAP filesystems ) 8-12GB (Linux) 200MB (CMS and the Linux boot disk) 4. Define a (400 ) track VTOC for each DASD volume that will contain DB2 data thr[...]

  • Seite 12

    III AIX Hardware Preparation 1. Review Checklist in theComponent Installation Guide : SAP ERP 2005 ABAP+Java on AIX: IBM DB2 UDB for z/OS for base Hardware Requirements . 2. Determine Hardware Configuration by completing the SAP sizing questionnaire for R/3 . Review the sizing deliverable document prepared by the IBM ISV TechLine Sizing Department [...]

  • Seite 13

    IV z/OS Software Preparation 1. Review Software Checklist in Installation Manual. REQUIRED • z/OS 1.6* or higher with the following components installed: UNIX System Services, DFSMS, TCP/IP, LE370, DFSORT • JES2 or JES3 • z/OS Security Server (RACF V 2.2 or higher) or a similar security function • z/OS RMF (Resource Management Facility) or [...]

  • Seite 14

    **Documentation and sample scripts for TSA are available from IBM. If the customer chooses an equivalent product they take full responsibility for configuring and testing that product with mySAP. High availability solutions are available from a number of providers, the customer is responsible for checking with the provider directly to verify their [...]

  • Seite 15

    4. Define the necessary users via RACF definitions (review the SAP Security Guide for IBM DB2 UDB for z/OS) : - define z/OS groupid <SCHEMA> as this will be the creator of all DB2 objects (Default = SAP R3) - define R/3 installation userid (superuser) for z/OS (zLinux uses linux root user) - define userid <sid>adm and groupid SAPSYS to [...]

  • Seite 16

    9. Configure the TCP/IP protoco l for GB Ethernet : A. Define the z/OS I/O configuration for the OSA-Express Card: - Define channel path ID for OSA-Express channel with type=OSA - Define OSA-Express control unit with type=OSA - Define 2 OSA-Express devices - Define Unit Addresses for the Control Unit (2 Devices for LCS (D118,D119) B. Customize the [...]

  • Seite 17

    SAPCL as per Chapter 4 of the SAP Planning Guide for SAP NetWeaver for IBM DB2 UDB for z/OS. These processes run under Unix System Services (USS). 17. For z/OS V1.7 and z/OSe V1.7: If the SAP implementation will exploit the IBM System z9 Integrated Information Processor(zIIP), this requires the "IBM System z9 Integrated Information Processor S[...]

  • Seite 18

    V DB2 Preparation 1. Install DB2 subsystem. A separate ICF catalog is recommended for each DB2 subsystem based on the High L evel Qualifier for DB2 datasets. the ICF Catalog should contain only the catalogued objects for a single DB2 subsystem. However, with DB2 V8 and DB2 9 the recommendation is to have two ICF Catalogs, one for each Copy Pool. Th[...]

  • Seite 19

    - recommended production initial definitions for DSNDB07 for an initial installation (each should be on a separate volume) : (4) 4K TableSpaces @ 200 cylinders each (2) 32K TableSpaces @ 200 cylinders each , Total = 1200 cylinders 5. Define archive log environment . If archiving to DASD, create a SMS storage group and configure enough DASD to maint[...]

  • Seite 20

    10. Install the Control Center Stored Procedures required by SAP as described in described in Chapter 3 of the SAP Database Administration Guide for SAP NetWeaver on IBM DB2 UDB for z/OS. The procedures are used for Database administration and replace the FTP submission of JCL streams used in previous releases. 11. Define <SCHEMA> as a second[...]

  • Seite 21

    15. Establish and test DB2 Backup/Recovery Procedures. These procedures should include a combination of DB2 and non-DB2 utilities in order to handle various recovery scenarios. In addition, DB2 V8 provides two new utilities for providing DB2 controlled system wide backup and a point in time recovery. These are the BACKUP SYSTEM and RESTORE SYSTEM ([...]

  • Seite 22

    16. The recommendation is to develop a DB2 system libraries configuration that allows each DB2 subsystem to be migrated to a new level of DB2, or DB2 maintenance, individually. For instance, if this is a DB2 data sharing group, you want to migrate members one at a time. The system libraries include SDSNLOAD, SDSNEXIT, SDSNMACS, SDSNSPFP, etc. The R[...]

  • Seite 23

    VI DB2 Related OSS Notes 1043951: Release of DB2 9 for SAP components 1072066: DBA Cockpit: New function for DB Monitoring 1027452: DB2 z/OS CCMS: DBA Cockpit 746299: Recommended Settings for Linux for zSeries JVM 1022334: DB2 z/OS Load ing a ta ble with compression dictionary 1032273: DB2 z/OS: Configuring DB2 9 913109: DB2 z/OS: SAPCL Patch Colle[...]

  • Seite 24

    509529 DB2 Changing the DB Host 513750 DB2 Data Sharing Topology 390016 DB2/390 BW: DB Settings and Performance 758550 DB2 System Parameter Check (DB16) 686905 History of statement cache statistics in ST04 956517 DB2 for z/OS: Load of alert router fails 846145 DB2 for z/OS: saving space when you load using R3load 908770 DB2 for z/OS: SAP Java perfo[...]

  • Seite 25

    VII AIX Software Preparation 1. Review Checklist in the Installation Guide: SAP ERP 2005 ABAB+Java on AIX: IBM DB2 UDB for z/OS for base Software Requirements. HIGHLY RECOMMENDED FOR AIX APPLICATION SERVERS • AIX Performance Toolbox and Performance AIDE for POWER Version 3.0 2. Apply all recommended PTFs as per OSS note 81737. 3.Configure the GbE[...]

  • Seite 26

    VIII Windows Hardware/Software Preparation 1. Review Checklist in Component Installation Guide: SAP ERP 2005 SR1 ABAP+Java on Windows:IBM DB2 UDB for z/OS for base Software Requirements. 2. Certified Hardware is required for application servers. Current certified IBM models are: IBM eServer xSeries IBM BladeCenter Servers 3. 3 GB RAM minimum (use s[...]

  • Seite 27

    IX SAP Installation Preparation 1. Order SAP Installation Kit. 2. Build project plan for installation. 3. Setup OSS connection to SAP and test FTP capability to sapserv. * Pre-Install Check* 4. Obtain all necessary OSS notes. 5. Gather the information necessary to respond to the SAPinst system parameters required for the installation. These are doc[...]

  • Seite 28

    X Sample BPXPRMxx Member MAXPROCSYS(4096) MAXPROCUSER(200 ) MAXTHREADTASKS( 1000 ) MAXTHREADS(1000) MAXUIDS(200) MAXFILEPROC(2 000) MAXFILESIZE (omit) MAXPTYS(256) CTRACE(CTIBPX00) IPCMSGQMNUM(20000) IPCMSGQBYTES(1048576) IPCSHMSPAGES(786432) IPCSHMMPAGES( 524287 ) IPCSHMNSEGS(100) IPCSEMNIDS(4096) IPCSHMNIDS(4096) IPCSEMNSEMS(32767) IPCSEMNOPS(327[...]

  • Seite 29

    FILESYSTYPE TYPE(HFS) ENTRYPOINT(GFUAINIT) ROOT FILESYSTEM('OMVS.ROOT') TYPE(HFS) MODE(RDWR) PARM('') MOUNT FILESYSTEM('OMVS.SAP.<SID>') TYPE(HFS) MODE(RDWR) MOUNTPOINT('/sap/<sid>') MOUNT FILESYSTEM('OMVS.TMP') TYPE(HFS) MODE(RDWR) MOUNTPOINT('/tmp') FILESYSTYPE TYPE(IBM UDS) [...]

  • Seite 30

    XI Sample DB2 DSNZPARMS DB2 V8 * = required /recommended value for SAP DSN6ENV MVS=XA DSN6SPRM RESTART, ALL, ABEXP=YES, ABIND=YES, AUTH=YES, AUTHCACH=4096, BINDNV=BINDADD, BMPTOUT=0, * CACHEDYN=YES, * CACHEDYN_FREELOCAL=1, (APAR PK21 861) CACHEPAC=1048576, CATALOG=DNX1SYS, * CDSSREF=1, CHGDC=NO, * CONTSTOR=YES , DECDIV3=NO, DEFLTID=IBMUSER, DESCSTA[...]

  • Seite 31

    RECALL=YES, RECALLD=120, * RELCURHL=YES, * RETLWAIT= 1, (Data Sharing only) RGFCOLID=DSNRGCOL, * RETVLCFK=NO, RGFDBNAM=DSNRGFDB, RGFDEDPL=NO, RGFDEFLT=ACCEPT, RGFESCP=, RGFFULLQ=YES, RGFINSTL=NO, RGFNMORT=DSN_REGISTER_OBJT, RGFNMPRT=DSN_REGISTER_APPL, * RRULOCK=NO, * SEQCACH=SEQ, SEQPRES=YES, SITETYP=LOCALSITE, * SJMXPOOL= 128, * SRTPOOL=28 000, * [...]

  • Seite 32

    DSN6LOGP DEALLCT=( 1440), MAXARCH=500, MAXRTU=2, * OUTBUFF=4000, * TWOACTV=YES, * TWOARCH=YES DSN6SYSP AUDITST=NO, * ACCUMACC=5, * CHKFREQ =10, CONDBAT=64, (>= MAXDBAT) * CTHREAD=1900 , (sum of TSO users + IDBACK) DLDFREQ=5, * IDBACK=1800 , 1.3 * (number of all SAP work processes + RFCOSCOL alert threads*2 ) IDFORE=60, * LBACKOUT =NO, * LOGA PST[...]

  • Seite 33

    * IDTHTOIN=0, RESYNC=2, RLFERRD=NOLIMIT, TCPALVER=YES DSN6GRP DSHARE=NO, GRPNAME=S4A, MEMBNAME=DNX1, COORDNTR=NO, ASSIST=NO END DSNHDECM CHARSET=ALPHANUM, * ASCCSID=819, AMCCSID=65534, AGCCSID=65534, * APPEN SCH=EBCDIC, * SCCSID=37, ( or any value where DB2 supports translation between SCCSID and ASCCSID , do not use 500 ) MCCSID=65534, GCCSID=6553[...]

  • Seite 34

    DB2 9 * = required /recommended value for SAP DSN6ENV MVS=XA DSN6SPRM RESTART, ALL, ABEXP=YES, ABIND=YES, AUTH=YES, AUTHCACH=4096, BINDNV=BINDADD, BMPTOUT=0, * CACHEDYN=YES, * CACHEDYN_FREELOCAL=1, CACHEPAC=1048576, CATALOG=DNX1SYS, * CDSSREF=1, CHGDC=NO, * CONTSTOR=YES , DECDIV3=NO, DEFLTID=IBMUSER, DESCSTAT= YES, DLITOUT=0, * DSMAX=20000 , * EDMD[...]

  • Seite 35

    * PARTKEYU=YES, RECALL=YES, RECALLD=120, * RETLWAIT= 1, (Data Sharing only) RGFCOLID=DSNRGCOL, * RETVLCFK=NO, RGFDBNAM=DSNRGFDB, RGFDEDPL=NO, RGFDEFLT=ACCEPT, RGFESCP=, RGFFULLQ=YES, RGFINSTL=NO, RGFNMORT=DSN_REGISTER_OBJT, RGFNMPRT=DSN_REGISTER_APPL, * RRULOCK=NO, * SEQCACH=SEQ, SEQPRES=YES, SITETYP=LOCALSITE, * SJMXPOOL= 128, * SRTPOOL=28 000, (6[...]

  • Seite 36

    TSTAMP=YES, UNIT=CART, UNIT2=CART DSN6LOGP DEALLCT=( 1440), MAXARCH=500, MAXRTU=2, * OUTBUFF=4000, * TWOACTV=YES, * TWOARCH=YES DSN6SYSP AUDITST=NO, * ACCUMACC=5, * ACCUMUID=11, * CHKFREQ =2, CONDBAT=64, (>= MAXDBAT) * CTHREAD=200 , (sum of TSO users + IDBACK) DLDFREQ=5, * IDBACK=50 , (>=20 and at least1.3 times the sum of: ICLI work processe[...]

  • Seite 37

    STATIME=30, STORMXAB=5, STORTIME=180, * SYNCVAL=30, TRACSTR=NO, TRACTBL=16, * TBSBPOOL=BP2, * TBS BPLOB=BP40, * TSQTY= 720, * URLGWTH=100, * URCHKTH=1 DSN6FAC * DDF=AUTO, * CMTSTAT= INACTIVE, * IDTHTOIN=0, * PRGSTRIN =DISABLE, (APAR PK46079) RESYNC=2, RLFERRD=NOLIMIT, TCPALVER=YES DSN6GRP DSHARE=NO, GRPNAME=S4A, MEMBNAME=DNX1, COORDNTR=NO, ASSIST=N[...]

  • Seite 38

    TIMELEN=0 END Copyright 2006 IBM Solutions Technical Sales (STS) 12/18/2007Page 38 of 51 12/18/2007 Planning and Preparation Guide for SAP NetWeaver Version 6.40: z/OS Implementation[...]

  • Seite 39

    XII TCP/IP Connectivity - required for S AP NetWeaver - strategic communications protocol - any HW supporting standard TCP/IP can be used - ongoing enhancements are planned - take advantage of standard TCP/IP functions: acknowledgement management re-transmission keep alive support in order delivery - over Gb E uses QDIO mode and MPC support which r[...]

  • Seite 40

    XIII Naming Conventions 1. The following elements should be part of an overall naming convention plan: SAP SID DR1 DB2 Started Task Names for MSTR, DBM1,DIST, IRLM DR11MSTR DR1 1DBM1 DR11IRLM DR11DIST DB2 Member/Subsystem Name DR11 DB2 SYSADM Userid SAPINST DB2 Group Attach Name DR1 RRS St arted Task Name RRSD TCP/IP H ost Name s SAPD TCP/IP DDF Po[...]

  • Seite 41

    XIV Application Server On z/OS Considerations * Note that only the SAP Central Services ASCS and SCS are now supported on Unix System Services under z/OS * 1. The following OSS Notes shoul d be reviewed : 595331 - z/OS enhanced ascii support & FTP updates 1009521 - Central Services does not start 2. Indicate at the time of the sizing that the c[...]

  • Seite 42

    XV Sample OSA-Express GB Configuration SYS1.VTAMLST(XXTRL) XXTRL VBUILD TYPE=TRL * TRLEGBF8 TRLE LNCTL=MPC, READ=600,WRITE=601, DATAPATH=602, PORTNAME=PORTGBF8, MPCLEVEL=QDIO TCPIP.PROFILES(PROFILXX) ;OSA GIGABIT ETHERNET CHP F8 LG06 DEVICE PORTGBF8 MPCIPA NONROUTER LINK GIGAF8 IPAQGNET PORTGBF8 HOME 10.1.1.254 GIGAF8 GATEWAY ; ; Direct Routes - Ro[...]

  • Seite 43

    XVI DB2 Backup/Recovery Notes (OSS Note 83000) NOTE: The procedures described here are applicable to DB2 Version 8. Version 8 provides two new utilities for backup and point in time recovery that provides a more robust solution that is less prone to errors, and reduces recovery time and labor time. These new utilities are described later in this se[...]

  • Seite 44

    Recover to prior point in time - A recovery of all tablespaces, indexspaces, DB2 catalog, and DB2 Directory to a previous log RBA (three ways to acomplish this) - Conditional Restart to recover to any previous point in time using DB2 Image Copies - Identify LOG RBA of prior point in time time : With DB2 V7 and the CHKFREQ parameter for controlling [...]

  • Seite 45

    - Recover to a prior point in time corresponding to the time of FlashCopy - Reset volumes using FlashCopy, including BSDS and logs - Restart DB2 - Use transaction SM13 to resolve R/3 units of work - Recover to a prior point in time using FlashCopy + logs - Reset volumes using FlashCopy , but use current BSDS and active logs. Use CHKFREQ of 15 minut[...]

  • Seite 46

    DB2 Version 8 Enhancements DB2 Version 8 enhances the SAP backup and recovery process by providing two new system utilities for system level backup and a point in time recovery for the entire SAP system. These are the BACKUP SYSTEM and RESTORE SYSTEM. They provide an efficient and non-dusruptive method for backing up the entire SAP database. DFSMS [...]

  • Seite 47

    XVII SAP Automation And High Availability Solution 1. The following OSS Notes shoul d be reviewed : 569996 (Redbook Updates) 524816 2. Indicate at the time of the sizing that the SAP Central Services instance will run on z/OS, since this will affect the processing and memory requirements. 3. The following IBM Manuals provide detailed implementation[...]

  • Seite 48

    XVIII SAP A pplication Server on zLinux Considerations 1. Review the latest version of OSS Note 81737 for the supported Linux distribution. 2. Hardware requirements: - IBM eServer zSeries z800, z900, z990, z890, z9, z9 BC, z9 EC - Each Linux image requires disk space for boot and swap(20GB) - Minimum 512 MB Central Storage 3. Software requirements:[...]

  • Seite 49

    7. Recommendations from the j oint IBM/SAP Platform Team:  Always use the latest z/VM release available , currently z/VM 5.3  Apply z/VM 5.1 APAR 63636 (PTF UM31312)  Apply all z/VM APARs listed in OSS Note 81737  Additional z/VM Considerations (these are specific to the customer configuration and the workload characteristics) :  Con[...]

  • Seite 50

    XIX Sample SMS Storage Group Assignments 1. Here is a sample assignment methodology for setting up SMS Storage Groups. One recommendation is to name the storage groups starting with the 3 character SAP <SID> followed by the type of dataset. STORAGE GROUP Name Dataset Type Sample Name (<SID>=DR1) LOG DB2 Active Log Datasets/BSDS/ SGDR1LO[...]

  • Seite 51

    ICF Catalog Names: CATALOG.SAPDB2.DR1LOG CATALOG.SAPDB2.DR1USR CATALOG.SAPDB2.DR1DB2 CATALOG.SAPDB2.DR1IC Catalog Structure: Catalog Alias ACS Dataset Name DR1USR DR1U DR1U.* DR1IC DR1IC DR1IC.** DR1DB2 DR1 DR1.SRCLIB DR1.DBRMLIB DR1.RUNLIB.LOAD DR1.DSNDB*.DSN*.** DR11 DR11.DSN* DR1LOG DR11.LOGCOPY1 DR11.LOG *.** DR11.LOGCOPY2 DR11.BSDS* DR11.BSDS0[...]