RE: Stored procedure test environment

A test user ID sounds like an easy way to set the proper library list.


What about choosing the proper stored procedure (SP)? Right now, all our SP calls include the schema name. I seem to recall I you don't specify a schema, DB2 tries to use the user ID as the schema. We don't to have to change the calls between test and production environments.



-----Original Message-----
From: Buck Calabro [mailto:kc2hiz@xxxxxxxxx]
Sent: Monday, June 08, 2015 10:35 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Stored procedure test environment

On 6/5/2015 7:15 PM, Justin Taylor wrote:

We're starting to rely heavily on RPG programs exposed as DB2 stored procedures and the time has come for an improved test environment. I don't have a test server/partition. My plan is to create a test schema and duplicate my stored procedures and tables there, while continuing to use the production programs and users.

First, I'll have to set the library list. Is there a good way to do this? My thought is to determine the schema of the stored procedure (assuming that's even possible) and set the library list in code. Is there a better way?

Second, I need the IP address of the caller. Currently, these are kept in data areas by application. Is there some easy way to get the client IP for a QZDASOINIT job?

I do this by user ID.

The user id is assigned a job description and the job description has the correct library list.

My test people have a separate user ID that they need to use to access the test procedures. The test user IDs are not authorised to the production libraries and vice versa, so even if they explicitly specify a library they can't access the SP or the data.

--
--buck