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.xxxxx
High Level Qualifier For Dataset Names DR1U for SAP Data
DR1IC for DB2 Image Copies
DR1 for DB2 Catalog,
Directory,
DR11 for System Libraries
DR11 for DB2 Active Logs,
Archive Logs, BSDS
SAP SMS Storage Groups SGDR1CAT
SGDR1LOG
SGDR1ARC
SGDR1SAP
SGDR1IC
DB2 Connect Instance Name DR1INST1
DB2 Connect Userid DR1DB2C
DDF Location Name DR1DDF
USS superuser (to run saposcol,sapccmsr) DR1SUSER
2. For multiple mySAP.com components consider a naming convention such as:
- First character identifies the type of system (e.g., development=D, production=P,
quality assurance=Q, training=T, sandbox=S)
- Second character identifies the component (e.g., R/3=R, BW=B, APO=A, EBP=E,
CRM=C)
- Third character is the system number or region:
Example: DR1 is the first development R/3 system
PR1 is the first production R/3 system
QR1 is the first quality assurance R/3 system
PB1 is the first production BW system
Copyright 2006
IBM Solutions Technical Sales (STS)
12/18/2007Page 40 of 51
12/18/2007
Planning and Preparation Guide for SAP NetWeaver Version 6.40: z/OS Implementation
