gn*****@rcn.com (robert) wrote in message news:<da*************************@posting.google.c om>...
what it is that imposes the 8 character limit?? OS/360?? COBOL??
VSAM?? CICS??
Robert,
DB2 for z/OS stores it's data in files. z/OS files can have names of
44 caracters max, and the names have to be composed using a number of
parts of 8 characters max each (called qualifiers). DB2 uses a strict
naming convention to assign names to the files it creates. A typical
name for a DB2 file looks about like this:
DB2T.DSNDBD.DB0008T.A177A.I0001.A001. The qualifier DB0008T is the
database name, A177A ist the tablespace name in my example. All other
qualifiers are set by DB2.
DB2 cannot get around the z/OS architecture limits, therefore the V8
has exactly the same convention for the tablespace datasets.
by the way, it is a good idea to keep the tablespace names short, as
you will have to create names for your image copy files, which can be
made for each partition of a tablespace. also these file names have to
fit in th 44 characters, which can get difficult.
We use a simple naming convention here for our tables and tablespaces,
and see no problem to administer the roughly 200'000 tables we have
per system:
Tables have a 2 byte appl code and a 3 digit number as their name
prefix, and the 3 digit number appears in the 5 byte tablespace name.
we use the same table qualifier for all tables to allow for
unqualified tablenames in appl programs. As database name and
tablespace name have to be unique, the 3 digit number start from 001
for every database. it's really no problem - but the architecture is a
bit different on the 390 systems ...
