It was mentioned about storing source as DDL instead of DDS.
Anyone doing this?
Yep! I haven't created any DDS described logical or physical file since
years. (Even though we access the database with embedded SQL and native
I/O).
Instead of DDS described logical files we create SQL Tables and instead of
keyed logical files we create SQL Indexes.
The source code of these database objects (CREATE TABLE / CREATE INDEX /
CREATE VIEW statements) are stored in traditional source physical file
members (because my manager suspects the IFS).
We include CREATE OR REPLACE, so we can rerun the SQL scripts (with either
RUNSQLSTM) or Client Access iNaviagor or Access Client Solution (ACS) - Run
SQL Scripts.
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
?Train people well enough so they can leave, treat them well enough so they
don't want to.? (Richard Branson)
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Steinmetz, Paul
Sent: Freitag, 24. Februar 2017 17:41
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: Storing source as DDL instead of DDS
I was at a new Pennsylvania IBM users group yesterday.
Name TBD, looking for new members.
It was mentioned about storing source as DDL instead of DDS.
Anyone doing this?
How is done?
Pros/cons?
Is there a migration utitlity?
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx
http://www.pencor.com/
midrange.com
