Re: Creating stored procedures

["Frances Denoncourt" <Frances.Denoncourt@xxxxxxxxxxxxxx>]

Thanks to those who responded. Rob, I think we agree with you. We want
visibility on the source.

We tried the source member route. That worked. I created a stored
procedure using the RUNSQLSTM and it created a C *pgm. Now the cool
thing is that we don't have the SQL dev kit installed. 

Better yet, we found that we could do the same from the RECORDSET view
utility on the PC. That was especially neat because we created the
stored procedure on our production machine which doesn't even have the
licensed compilers installed. We don't keep source on that machine. 

If we had to, I suppose we could use WRKDBF on the production machine
to add 'source' members and then create the stored procedures from
that.

While we were plunking around trying to find the objects created by the
create procedure command, we noticed we had to delete an existing one to
recreate the stored procedure. 

By then (thank you Alan Campin for prior posts and our contact at HiT)
we had found the files in QSYS2. Now wasn't that interesting that when
we deleted the stored procedure it was removed from SYSPROCS, etc. As an
aside, WRKDBF has the same problem with the phsical fiiles as does
QuestView. In fact, couldn't even look at the logicals over SYSPARMS.

Interesting also that I could create the stored procedure on the dev
box and restore it to the production box and see that when it was
restored the corresponding QSYS2 files were updated on the production
box. 

We had iSeries Navigator installed this morning. I haven't tried it
yet, but my boss is not too impressed, yet. Maybe it's a learning curve
or something.

Thanks again for all of your help. 

Fran Denoncourt
Sr. Programmer/Analyst
Pinal County Treasurer's Office
Florence, AZ 85232
(520) 866-6404

Receipt of this message does not grant you permission to send me 
Unsolicited Commercial Email