Re: Difference between creating a View on the Production box vs. Dev-box?

[Alan Cassidy <cfuture@xxxxxxxxxxx>]

I got the bright idea to use an RPG program and embed the CREATE OR 
REPLACE statement to create the View withing that RPG program, so that 
the statement actually runs on the Production box?

I shouldn't have to but I've got to get this thing done. I kept tweaking 
the statement time and again, then finally tried running the SQL script 
right on the Production box (generally a strict no-no).

I would still prefer a better idea. It doesn't make sense to me. I have 
created Views on the dev-box before and then sent them to the production 
box and it worked perfect. Shouldn't matter that this one is lot more 
complex than the others....

---Alan


On 5/25/2022 5:18 PM, Alan Cassidy wrote:
> I wrote an SQL statement to *CREATE OR REPLACE MYLIB.MYVIEW.*
> *
> *
> I ran the SQL on the production box. Worked great. The command _RUNQRY 
> *N MYVIEW _returned the data I expected (and wanted). So my work with 
> getting to the code is done.
> *But then.. *..I ran the /_*same exact statement*_ with the same/ 
> _RUNSQLSTM_ on the Dev-box to create the View and then sent the View 
> over to AEF80. When I run _RUNQRY *N MYVIEW_, now it gives me zero 
> records.
>
> ...You folks that have worked with SQL, any ideas? (I haven't even 
> gotten to where I can put it into the RPG program to work with). fI 
> haven't had this problem before. I even got it to work and got good 
> data once but had to fix some little thing, but I haven't gotten it to 
> do right by me since.
>
> Anybody know what's going on here? Any suggestions? Even something in 
> he archives? I don't even know how to search for this kind of issue. 
> It's hard to believe.
>
> --Alan