I've got a couple of questions about the sysprocedures table.  First, the isproc column.  It looks like isproc is set to 'f' any time the routine has return values, regardless of whether it was created via CREATE PROCEDURE or CREATE FUNCTION.  I guess that brings up a question of whether there is any difference between a CREATE PROCEDURE that has return values vs a CREATE FUNCTION, which must have return values.  Can you use both interchageably?  Do both work the same way in projection clauses, WHERE clauses, and SPL LET statements (among other places)?

So it seems that isproc will only be 't' if the routine was created via CREATE PROCEDURE and has no return values.  Is that correct?

Next, the mode column.  Is it correct that mode would be 'D' only for those routines created via CREATE DBA PROCEDURE or CREATE DBA FUNCTION?  It sounds like mode would be 'R' for routines created via "CREATE PROCEDURE username.my_procedure" if you ran this as user informix or some other user with DBA permission.  Is that correct?  

Finally, how do you identify routines that were generated by your own staff?  I was thinking it would be a simple case of mode = "O", but that isn't it.  I've got a number of procedures that I know were created by our developers, which have mode = "O" (or possibly "R"), but there are many others, such as the binary18* routines and some of the equal and notequal routines, that also have mode = "O".  Is there some other column that differentiates those routines provided by IBM from those created in-house?  Or another table that I need to join against to get that information?

I've got a couple of questions about the sysprocedures table.  First, the isproc column.  It looks like isproc is set to 'f' any time the routine has return values, regardless of whether it was created via CREATE PROCEDURE or CREATE FUNCTION.  I guess that brings up a question of whether there is any difference between a CREATE PROCEDURE that has return values vs a CREATE FUNCTION, which must have return values.  Can you use both interchageably?  Do both work the same way in projection clauses, WHERE clauses, and SPL LET statements (among other places)?

So it seems that isproc will only be 't' if the routine was created via CREATE PROCEDURE and has no return values.  Is that correct?

Next, the mode column.  Is it correct that mode would be 'D' only for those routines created via CREATE DBA PROCEDURE or CREATE DBA FUNCTION?  It sounds like mode would be 'R' for routines created via "CREATE PROCEDURE username.my_procedure" if you ran this as user informix or some other user with DBA permission.  Is that correct?  

Finally, how do you identify routines that were generated by your own staff?  I was thinking it would be a simple case of mode = "O", but that isn't it.  I've got a number of procedures that I know were created by our developers, which have mode = "O" (or possibly "R"), but there are many others, such as the binary18* routines and some of the equal and notequal routines, that also have mode = "O".  Is there some other column that differentiates those routines provided by IBM from those created in-house?  Or another table that I need to join against to get that information?

I've got a couple of questions about the sysprocedures table.  First, the isproc column.  It looks like isproc is set to 'f' any time the routine has return values, regardless of whether it was created via CREATE PROCEDURE or CREATE FUNCTION.  I guess that brings up a question of whether there is any difference between a CREATE PROCEDURE that has return values vs a CREATE FUNCTION, which must have return values.  Can you use both interchageably?  Do both work the same way in projection clauses, WHERE clauses, and SPL LET statements (among other places)?

So it seems that isproc will only be 't' if the routine was created via CREATE PROCEDURE and has no return values.  Is that correct?

Next, the mode column.  Is it correct that mode would be 'D' only for those routines created via CREATE DBA PROCEDURE or CREATE DBA FUNCTION?  It sounds like mode would be 'R' for routines created via "CREATE PROCEDURE username.my_procedure" if you ran this as user informix or some other user with DBA permission.  Is that correct?  

Finally, how do you identify routines that were generated by your own staff?  I was thinking it would be a simple case of mode = "O", but that isn't it.  I've got a number of procedures that I know were created by our developers, which have mode = "O" (or possibly "R"), but there are many others, such as the binary18* routines and some of the equal and notequal routines, that also have mode = "O".  Is there some other column that differentiates those routines provided by IBM from those created in-house?  Or another table that I need to join against to get that information?

I've got a couple of questions about the sysprocedures table.  First, the isproc column.  It looks like isproc is set to 'f' any time the routine has return values, regardless of whether it was created via CREATE PROCEDURE or CREATE FUNCTION.  I guess that brings up a question of whether there is any difference between a CREATE PROCEDURE that has return values vs a CREATE FUNCTION, which must have return values.  Can you use both interchageably?  Do both work the same way in projection clauses, WHERE clauses, and SPL LET statements (among other places)?

So it seems that isproc will only be 't' if the routine was created via CREATE PROCEDURE and has no return values.  Is that correct?

Next, the mode column.  Is it correct that mode would be 'D' only for those routines created via CREATE DBA PROCEDURE or CREATE DBA FUNCTION?  It sounds like mode would be 'R' for routines created via "CREATE PROCEDURE username.my_procedure" if you ran this as user informix or some other user with DBA permission.  Is that correct?  

Finally, how do you identify routines that were generated by your own staff?  I was thinking it would be a simple case of mode = "O", but that isn't it.  I've got a number of procedures that I know were created by our developers, which have mode = "O" (or possibly "R"), but there are many others, such as the binary18* routines and some of the equal and notequal routines, that also have mode = "O".  Is there some other column that differentiates those routines provided by IBM from those created in-house?  Or another table that I need to join against to get that information?

I've got a couple of questions about the sysprocedures table.  First, the isproc column.  It looks like isproc is set to 'f' any time the routine has return values, regardless of whether it was created via CREATE PROCEDURE or CREATE FUNCTION.  I guess that brings up a question of whether there is any difference between a CREATE PROCEDURE that has return values vs a CREATE FUNCTION, which must have return values.  Can you use both interchageably?  Do both work the same way in projection clauses, WHERE clauses, and SPL LET statements (among other places)?

So it seems that isproc will only be 't' if the routine was created via CREATE PROCEDURE and has no return values.  Is that correct?

Next, the mode column.  Is it correct that mode would be 'D' only for those routines created via CREATE DBA PROCEDURE or CREATE DBA FUNCTION?  It sounds like mode would be 'R' for routines created via "CREATE PROCEDURE username.my_procedure" if you ran this as user informix or some other user with DBA permission.  Is that correct?  

Finally, how do you identify routines that were generated by your own staff?  I was thinking it would be a simple case of mode = "O", but that isn't it.  I've got a number of procedures that I know were created by our developers, which have mode = "O" (or possibly "R"), but there are many others, such as the binary18* routines and some of the equal and notequal routines, that also have mode = "O".  Is there some other column that differentiates those routines provided by IBM from those created in-house?  Or another table that I need to join against to get that information?

I've got a couple of questions about the sysprocedures table.  First, the isproc column.  It looks like isproc is set to 'f' any time the routine has return values, regardless of whether it was created via CREATE PROCEDURE or CREATE FUNCTION.  I guess that brings up a question of whether there is any difference between a CREATE PROCEDURE that has return values vs a CREATE FUNCTION, which must have return values.  Can you use both interchageably?  Do both work the same way in projection clauses, WHERE clauses, and SPL LET statements (among other places)?

So it seems that isproc will only be 't' if the routine was created via CREATE PROCEDURE and has no return values.  Is that correct?

Next, the mode column.  Is it correct that mode would be 'D' only for those routines created via CREATE DBA PROCEDURE or CREATE DBA FUNCTION?  It sounds like mode would be 'R' for routines created via "CREATE PROCEDURE username.my_procedure" if you ran this as user informix or some other user with DBA permission.  Is that correct?  

Finally, how do you identify routines that were generated by your own staff?  I was thinking it would be a simple case of mode = "O", but that isn't it.  I've got a number of procedures that I know were created by our developers, which have mode = "O" (or possibly "R"), but there are many others, such as the binary18* routines and some of the equal and notequal routines, that also have mode = "O".  Is there some other column that differentiates those routines provided by IBM from those created in-house?  Or another table that I need to join against to get that information?

I've got a couple of questions about the sysprocedures table.  First, the isproc column.  It looks like isproc is set to 'f' any time the routine has return values, regardless of whether it was created via CREATE PROCEDURE or CREATE FUNCTION.  I guess that brings up a question of whether there is any difference between a CREATE PROCEDURE that has return values vs a CREATE FUNCTION, which must have return values.  Can you use both interchageably?  Do both work the same way in projection clauses, WHERE clauses, and SPL LET statements (among other places)?

So it seems that isproc will only be 't' if the routine was created via CREATE PROCEDURE and has no return values.  Is that correct?

Next, the mode column.  Is it correct that mode would be 'D' only for those routines created via CREATE DBA PROCEDURE or CREATE DBA FUNCTION?  It sounds like mode would be 'R' for routines created via "CREATE PROCEDURE username.my_procedure" if you ran this as user informix or some other user with DBA permission.  Is that correct?  

Finally, how do you identify routines that were generated by your own staff?  I was thinking it would be a simple case of mode = "O", but that isn't it.  I've got a number of procedures that I know were created by our developers, which have mode = "O" (or possibly "R"), but there are many others, such as the binary18* routines and some of the equal and notequal routines, that also have mode = "O".  Is there some other column that differentiates those routines provided by IBM from those created in-house?  Or another table that I need to join against to get that information?

I've got a couple of questions about the sysprocedures table.  First, the isproc column.  It looks like isproc is set to 'f' any time the routine has return values, regardless of whether it was created via CREATE PROCEDURE or CREATE FUNCTION.  I guess that brings up a question of whether there is any difference between a CREATE PROCEDURE that has return values vs a CREATE FUNCTION, which must have return values.  Can you use both interchageably?  Do both work the same way in projection clauses, WHERE clauses, and SPL LET statements (among other places)?

So it seems that isproc will only be 't' if the routine was created via CREATE PROCEDURE and has no return values.  Is that correct?

Next, the mode column.  Is it correct that mode would be 'D' only for those routines created via CREATE DBA PROCEDURE or CREATE DBA FUNCTION?  It sounds like mode would be 'R' for routines created via "CREATE PROCEDURE username.my_procedure" if you ran this as user informix or some other user with DBA permission.  Is that correct?  

Finally, how do you identify routines that were generated by your own staff?  I was thinking it would be a simple case of mode = "O", but that isn't it.  I've got a number of procedures that I know were created by our developers, which have mode = "O" (or possibly "R"), but there are many others, such as the binary18* routines and some of the equal and notequal routines, that also have mode = "O".  Is there some other column that differentiates those routines provided by IBM from those created in-house?  Or another table that I need to join against to get that information?

With blades you can also get caught if the path has changed, very common with TS when the blade can be tightly coupled to the engine version.