So is the idea here that you want to pass a cursor (result set) into the StoreProce1 procedure via the third parameter?
If so, then I'm afraid that this isn't something we support....
One workaround might be to create a "wrapper" stored procedure to call both the query which produces the result set as well as calling StoreProce1. But depending on what the exact use case is, there might be better ideas.
I would think about another way to accomplish this--can you combine the two stored procedures in some other way?
I don't think that the product is close to supporting something like this. I'm also not sure that it makes sense for it to; if a customer needs to perform this much specialized processing to combine results from multiple stored procedures, they're probably better of defining this logic inside a "wrapper" stored procedure which is able to return results to PegaRULES in a simpler format (e.g. a single result set).
If you want to provide more information about exactly what the customer is doing, then perhaps we can come up with another idea.