RE: Dumb SQL question

<< if you do not know what you are doing, do not mess with it>>

I hear you. This particular vendor fits that description. They just upgraded
a different client to their latest service pack, and now their GUI interface
software is not firing up unless Websphere is started manually.

The nightly backup program tries to start it, but they left behind some
residue in an HTTP instance that is making the routine fall over.

Unfortunately, these guys are the only ones in the "Rochester product name"
space for the construction industry. All the others that were out there have
abandoned the platform.

Paul Nelson
Office 512-392-2577
Cell 708-670-6978
nelsonp@xxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Wednesday, October 26, 2011 2:57 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Dumb SQL question

On 26-Oct-2011 12:02 , Paul Nelson wrote:

The PRTMSTID field seems to point to the PRTMST file. Same goes for
the SYTCNC file.

Rewriting an application just to say you use SQL seems to be penny
wise and pound foolish. I know there are other clients of this vendor
who have embedded CPYF statements in some of their custom CLP's that
are going to be cranky at having them break just because of this.

If the presumed-as or alluded possible issues with CPYF are meant to
imply some specific relationship to Foreign Key constraints, then please
realize that the issue is not specific to the SQL. Either ADDPFCST
TYPE(*REFCST) or ALTER TABLE ADD CONSTRAINT FOREIGN KEY is [with
necessary attributes established; e.g. MAXMBRS(1)] still valid for
DDS-PF, just as for SQL TABLE.

How CPYF is utilized must be understood within the context of the
database file definitions and means of data manipulation irrespective of
DDS or SQL DDL as the definition\description language.

In other words, no matter what definitional language, if CPYF is used
without proper understanding of the database and how the database is
being manipulated, the use of CPYF may be problematic. But the same
could be said about using SQL or RPG without the same level of
understanding about the database; i.e. if you do not know what you are
doing, do not mess with it :-)

Regards, Chuck