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) 12/18/2007Page 1 of 51 12/18/2007 Planning and Preparation Guide for SAP NetWeaver Version 6.
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* DB2* DB2 Universal Database e-business logo Enterprise Storage Server* GDPS* Geographically Dispersed Parallel Sysplex HiperSockets IBM* IBM eServer IBM logo* IMS PR/SM Parallel Sysplex* pSeries* System z9 System z Tivoli* xSeries* z/Architecture z/OS* z/VM* zSeries* * Registered trademarks of IBM Corporation Intel is a registered tradema
Contents 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/IP Connectivity XIII Naming Conventions XIV Application Server On z/OS Considerations XV Sample OSA-Express GB Configuration XVI DB2 Backup/Recovery Notes XVII SAP
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.
1. Identify the technical implementation team members: z/OS System Programmer zLinux Administrator Security Administrator Unix System Services Administrator Storage Administrator Network Administrator AIX/Windows Administrator DB2 DBA DB2 Systems Programmer R/3 Administrator z/OS Capacity Planning & Performance Administrator 2.
- 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.
(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 z/OS: Multiple Components In One Database(MCOD) (SG24- 6914) - DB2 for z/OS Version 8 : Everything You Ever Wanted to Know...
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/390: Configuring the AppServer on Linux for zSeries 731937: DB2-z/OS: Customizing DB2 Connect for WebAS 6.20 and DB2 V8 710466: Upgrade to 6.
797084: 892818: 821904: 686905: 818291: 144864: SUSE Linux Enterprise Server 9: Installation Note Application servers on Linux for zSeries: Settings Separating SCS instances for ABAP and J2EE DB2 for z/OS: DDIC Corrections (6.40, 7.0) zSeries: Windows 64 bit app server SAP Remote Services: Technical preparation 6. Prepare a project plan for the implementation.
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 Sales Team or implementation partner. Memory estimates will be provided as well. The questionnaire is available online at: http://www.ibm.
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 through ICKDSF DASD initialization. VVDS should be (180) tracks and the VTOC Index should be (50) tracks.Triple these values if the DASD geometry is 3390-9.
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 in conjunction with your IBM Sales Team or implementation partner. Memory estimates will be provided as well.
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 another compatible product that supports the Sysplex Data Services (ERBDSQRY, ERBDSREC, ERB2XDGS, ERB3XDRS) •DB2 UDB for z/OS V8.
**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 ability to support mySAP HA scenarios. REQUIRED FOR zLINUX APPLICATION SERVERS •SuSE Linux Enterprise Server 10 for zSeries - SLES 10 SP1 (glibc 2.4.31.
4.
9. Configure the TCP/IP protocol for GB Ethernet: A. Define the z/OS I/O configuration for the OSA-ExpressCard: - 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 OSA-Express Feature through OSA/SF or TSO. C. Configure the MPC interface using the DEVICE, LINK, HOME, GATEWAY, and START statements in the TCP/IP Profile Dataset.
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 Support for z/OS and z/OSe Web Deliverable, available on the z/OS downloads website plus PTFs. This Web deliverable contains FMID JBB772S for z/OS and z/OS.e V1.
V DB2 Preparation 1. Install DB2 subsystem. A separate ICF catalog is recommended for each DB2 subsystem based on the High Level 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. There is a DataBase Copy Pool, that will contain the SAP tablespaces, SAP indexspaces, DB2 Catalog, and DB2 Directory.
- 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 maintain enough archives between HSM migrations. Develop and implement a HSM migration strategy.
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 as a secondary authorization ID of the DB2 Connect userid. To do this replace the default secondary exit routine as described in section 3.4.2.
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 (See OSS note 83000). In addition, with DB2 V8 and DB2 9 you can leverage the RESTORE SYSTEM utility for point-in-time recovery processes.
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 RUNLIB.LOAD, DBRMLIB.DATA and SRCLIB.
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 table with compression dictionary 1032273: DB2 z/OS: Configuring DB2 9 913109: DB2 z/OS: SAPCL Patch Collection 686905: DB2 z/OS: DDIC Corrections (6.40, 7.0, 7.
509529 513750 390016 758550 686905 956517 846145 908770 958252 930025 915482 Copyright 2006 DB2 Changing the DB Host DB2 Data Sharing Topology DB2/390 BW: DB Settings and Performance DB2 System Parameter Check (DB16) History of statement cache statistics in ST04 DB2 for z/OS: Load of alert router fails DB2 for z/OS: saving space when you load using R3load DB2 for z/OS: SAP Java performance optimizer SAPCL FAQ Stored Procedure SAPCL configuration problem DB2 for z/OS: Automating DB failover IBM Solutions
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 adapter for the GbE LAN. 4.
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 sizing configuration recommendation) 4. Disk space requirements are in the manual SAP ERP 2005 SR1 ABAP+Java on Windows: IBM DB2 UDB for z/OS manual. 5.
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 documented in the Component Installation Guides, Chapter 2.
X Sample BPXPRMxx Member MAXPROCSYS(4096) MAXPROCUSER(200) MAXTHREADTASKS(1000) MAXTHREADS(1000) MAXUIDS(200) MAXFILEPROC(2000) MAXFILESIZE (omit) MAXPTYS(256) CTRACE(CTIBPX00) IPCMSGQMNUM(20000) IPCMSGQBYTES(1048576) IPCSHMSPAGES(786432) IPCSHMMPAGES(524287) IPCSHMNSEGS(100) IPCSEMNIDS(4096) IPCSHMNIDS(4096) IPCSEMNSEMS(32767) IPCSEMNOPS(32767) MAXMMAPAREA(4096) MAXCORESIZE(2147483647) MAXASSIZE(2147483647) MAXCPUTIME(2147483647) MAXSHAREPAGES(131072) USERALIASTABLE(/etc/ualiastable) FORKCOPY(COW) Copyri
FILESYSTYPE TYPE(HFS) ENTRYPOINT(GFUAINIT) ROOT FILESYSTEM('OMVS.ROOT') TYPE(HFS) MODE(RDWR) PARM('') MOUNT FILESYSTEM('OMVS.SAP.') TYPE(HFS) MODE(RDWR) MOUNTPOINT('/sap/') MOUNT FILESYSTEM('OMVS.
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 PK21861) CACHEPAC=1048576, CATALOG=DNX1SYS, * CDSSREF=1, CHGDC=NO, * CONTSTOR=YES, DECDIV3=NO, DEFLTID=IBMUSER, DESCSTAT=YES, DLITOUT=0, * DSMAX=6000, * EDMSTMTC=300000, EDPROP=NO, EXTSEC=NO, * EVALUNC=YES, HOPAUTH=YES, IRLMAUT=YES, IRLMPRC=IRLM, IRLMSID=INX1, * IRLMRWT=600, *
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=28000, * STARJOIN=2, * SJTABLES=4, * SJMXPOOL=128, * STATSINT=30, SYSADM=SYSADM, SYSADM2=P47208, SYSOPR1=SYSOPR, SYSOPR2=P47208, * UTIMOUT=3, * XLKUPDLT=TARGET DSN6ARVP ALCUN
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, * LOGAPSTG=100, * LOBVALA=1000000, * LOBVALS=50000, MAXDBAT=64, 1.
* 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, * APPENSCH=EBCDIC, * SCCSID=37, ( or any value where DB2 supports translation between SCCSID and ASCCSID, do not use 500) MCCSID=65534, GCCSID=65534, * ENSCHEME=ASCII, DATE=ISO, DATELEN=0, * DECARTH=DEC15, * DECIMAL=PERIOD, DEFLANG=C, DELIM=DEFAULT, MIXED=NO, SQLDELI=DEFAULT, DSQLDELI=APOST, SSID=DNX1, STDSQL=N
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, * EDMDBDC=value presented by DB2 install CLIST, min 150MB * EDMSTMTC=300000, * EDMPOOL = value presented by DB2 install CLIST, min 64MB EDPROP=NO, EXTSEC=NO, * EVALUNC=YES,
* 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=28000, (64000 for BI) * STARJOIN=2, * SJTABLES=4, * SJMXPOOL=128, * STATROLL=YES, * STATSINT=30, SYSADM=SYSADM, SYSADM2=P47208, SYSOPR1=SYSOPR, SYSOPR2=P47208, * SYSTEM_LEVE
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.
* * * * * * DSN6FAC * * * * DSN6GRP STATIME=30, STORMXAB=5, STORTIME=180, SYNCVAL=30, TRACSTR=NO, TRACTBL=16, TBSBPOOL=BP2, TBSBPLOB=BP40, TSQTY=720, URLGWTH=100, URCHKTH=1 DDF=AUTO, CMTSTAT=INACTIVE, IDTHTOIN=0, PRGSTRIN=DISABLE, (APAR PK46079) RESYNC=2, RLFERRD=NOLIMIT, TCPALVER=YES DSHARE=NO, GRPNAME=S4A, MEMBNAME=DNX1, COORDNTR=NO, ASSIST=NO END DSNHDECM CHARSET=ALPHANUM, * ASCCSID=819, AMCCSID=65534, AGCCSID=65534, * APPENSCH=EBCDIC, * SCCSID=37, ( or any value <= 640 and >= 700) MCCSID=65534, GCCSI
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.
XII TCP/IP Connectivity - required for SAP 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 GbE uses QDIO mode and MPC support which requires a VTAM TRLE Node Definition TCP/IP Definitions: Device: associates a TCP/IP device name with the LCS device number DEVICE LCS
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 DR11DBM1 DR11IRLM DR11DIST DB2 Member/Subsystem Name DR11 DB2 SYSADM Userid SAPINST DB2 Group Attach Name DR1 RRS Started Task Name RRSD TCP/IP Host Names SAPD TCP/IP DDF Port Numbers ICF Catalog Name CATALOG.SAPDB2.
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 should 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 central services instance will run on S/390 or z/OS, since this will affect the processing and memory requirements. 3.
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 - Routes that are directly connected to my interface ; Network First Hop Link Name Packet Size Subnet Mask Subnet VA ; 10.0.0.0 = GIGAF8 8992 0.255.255.0 0.1.1.
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 section.
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 DB2 checkpoint time the recommendation is to set CHKFREQ at 15 minutes.
- 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 minutes to keep at least a day worth of checkpoints in the current BSDS.
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 has new entities that provide support for these utilities, these are the Copy Pool construct and the Copy Poolbackup Storage Group type.
XVII SAP Automation And High Availability Solution 1. The following OSS Notes should 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.
XVIII SAP Application 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: - DB2 UDB for z/OS Version 8.1 or DB2 9 - z/VM 4.4 or higher (z/VM 5.3 is highly recommended) - a 64 bit Linux distribution with glibc 2.2.4 and kernel 2.4.
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.
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 followed by the type of dataset.
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.DSN* DR11 DR1LOG DR11.LOGCOPY1 DR11.LOGCOPY2 DR11.BSDS01 DR11.BSDS02 DR11.ARCHLOG1 DR11.ARCHLOG2 DR11.LOG*.** DR11.BSDS* DR11.
