RE: SQL Stored Procedure

The difference between the dot (".") and the slash ("/") is controlled by
the naming convention being used at the time the procedure is created.  *SQL
requires the dot and *SYS requires the slash.  I noticed you're using *SQL
in your creation statement. 

I believe the library is controlled by the current library in force at the
time the creation is executed.  If no current library is defined, QGPL is
used.  

Hope that helps. 

Donald R. Fisher, III
Project Manager
Roomstore Furniture Company
(804) 784-7600 extension 2124
DFisher@xxxxxxxxxxxxx

<clip>
Questions:
1. Can the dot (.) in "delete from library01.file1" be replaced by slash
('/')? Like library01/file1? What is the difference? 

2. What we are seeing is if we hardcode the library in CREATE PROCEDURE
statement (CREATE PROCEDURE PROCLIB.DB@BETT001), it is compiling fine with
the dot, otherwise we are giving slash. Is there any link between these two
things? Or are we doing all wrong?

3. If we don't want to hardcode the library in CREATE PROCEDURE statement,
where does the object goes? I thought (somebody told me) that it goes to the
top most library in the library list. But that is not happening. The object
is going to the user's, who ever is signed in, default library. How do we
control that?

4. We are using the following command to create the objects
RUNSQLSTM SRCFILE(PROCLIB/QSQLSRC) SRCMBR(DB2BETT001) COMMIT(*NONE)
NAMING(*SQL) DYNUSRPRF(*OWNER) 
<clip>