Download PDF - IBM Redbooks
Download PDF - IBM Redbooks
Download PDF - IBM Redbooks
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
DB2 members of the same data sharing group can share the following storage groups:<br />
► One SMS storage group for LOGCOPY1, BSDS01<br />
► One SMS storage group for LOGCOPY2, BSDS02<br />
With the DB2 BSDS, a single-level alias cannot distinguish between the VSAM cluster name<br />
and the alias name. Log data sets have two qualifiers before you apply the high-level qualifier:<br />
LOGCOPY1.DSnn. However, before applying the high-level qualifier, the BSDS data sets<br />
have only one qualifier: BSDS01 or BSDS02. An ACS and ICF catalog isolation issue occurs<br />
when you want to place the logs and BSDS in a separate SMS storage group and ICF<br />
catalog. For BSDS, you can have an ICF catalog alias and VSAM dataset cluster name that<br />
are identical. Both are VSAM entities, which can cause confusion. Therefore, they must be<br />
distinguishable.<br />
Therefore, a solution is to make the BSDS data sets a three-level dataset name, such as<br />
PE1.DB2.BSDS01. Alternatively, you can change the high-level qualifier for the BSDS and<br />
logs to a unique value, such as PE11L. Now the ICF catalog alias is PE11L, is a single level,<br />
can be identified by the ACS routine, and can be used for catalog isolation.<br />
If a single-level alias is desired, use the following SIDs:<br />
1. Use 1L (or 1LOG) for:<br />
– ARCHLOG1<br />
– BSDS01<br />
– LOGCOPY1<br />
2. Use 2L (or 2LOG) for:<br />
– ARCHLOG2<br />
– BSDS02<br />
– LOGCOPY2<br />
For a multilevel alias, use 1.DB2.BSDS01 and 1.DB2.BSDS02.<br />
Table B-10 shows SMS storage group name entries and definitions for DB2 active logs of<br />
SAP SID PE1 using the single log option.<br />
Table B-10 DB2 active log data sets: Single log option SAP = PE1<br />
SMS<br />
storage<br />
group<br />
Data sets Dataset name ICF<br />
catalog<br />
name<br />
PE1LOGSG DB2 active log<br />
data sets,<br />
DB2 BSDS data<br />
sets, DSNLOAD,<br />
DSNMACS,<br />
DSNEXIT<br />
PE11.LOGCOPY1.DSnn,<br />
PE11.LOGCOPY2.DSnn,<br />
PE1A.LOGCOPY1.DSnn,<br />
PE1A.LOGCOPY2.DSnn,<br />
PE11.DB2.BSDS01,<br />
PE11.DB2.BSDS02,<br />
PE1A.DB2.BSDS01,<br />
PE1A.DB2.BSDS02,<br />
PE11.DB2.DSNLOAD,<br />
PE11.DB2.DSNMACS,<br />
PE11.DB2.DSNEXIT,<br />
PE1A.DB2.DSNLOAD,<br />
PE1A.DB2.DSNMACS,<br />
PE1A.DB2.DSNEXIT<br />
PE1LOG.DB<br />
2.CATALOG<br />
Catalog<br />
ALIAS<br />
PE11.LOGC<br />
OPY1,<br />
PE11.LOGC<br />
OPY2,<br />
PE11.DB2,<br />
PE11,<br />
PE1A.LOGC<br />
OPY1,<br />
PE1A.LOGC<br />
OPY2,<br />
PE1A.DB2,<br />
PE1A<br />
SMS<br />
management<br />
class<br />
180 Running SAP Solutions with <strong>IBM</strong> DB2 10 for z/OS on the <strong>IBM</strong> zEnterprise System<br />
SMS<br />
storage<br />
class<br />
Guaranteed<br />
space<br />
Migration<br />
NULL LOGSC YES NO
Change language