Naming Convention

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
vipson
Premium Member
Premium Member
Posts: 52
Joined: Thu Jan 03, 2008 10:31 pm

Naming Convention

Post by vipson »

Hello Gurus,

I am trying to come up with Naming Conventions.

Any recommendations naming conventions for
1. dsn entries in uvodbc.config and .odbc.ini files
2. Data connections

I was thinking about <3 letter ACRONYM of PROJECT>_<Database Server Name>_<DatabaseName> as dsn entries
and
<3 letter ACRONYM of PROJECT>_<Database Server Name>_<DatabaseName>_P as connection names.

I want to track what project, what server, db it is using.
Each project will have their own access for the databases.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Whatever conventions are meaningful in context are suitable, provided they are documented, promulgated and adhered to.

:idea:
Do not create conventions so complex that it takes longer to work out what name to use than to create the entire job.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
vipson
Premium Member
Premium Member
Posts: 52
Joined: Thu Jan 03, 2008 10:31 pm

Post by vipson »

I agree. I have decided to use:
<Three Letter Project Acronym>_<Server Name>_<Database/Library Name>
eg.
DSN: TST_COBRA01_SQL101
The Parallel connection will be TST_COBRA01_SQL101_P
Parameter will be: ps_TST_COBRA01_SQL101
where TST is project - three letter acronym
COBRA01 is server name
SQL101 is database name....

This way we can manage project level access to the databases, no one shares the connections, name tells what it is for..
Bit lengthy but helps the situation.
Post Reply