Oppolzer - Informatik / Blog

Of course it is no good practice to have DB2 SPs which
are called by Java callers tested this way, because every time
you make changes, you have to have a Java caller which does the
testing for you.

That's why at our site we wrote a generic test driver which tests
all the DB2 SPs of this kind (there are many) using normal batch
jobs. What makes things easier is: the parameters passed by Java
are translated by a standardized framework from Java classes to
XML and from XML to PL/1 structures (and the same way back,
if necessary), this way eliminating problems with character sets
and data representation on the different platforms. The framework
procedures doing the translation need not be tested. What is tested
is only the PL/1 routine which does the actual work of the SP, and
that routine has a "normal" PL/1 interface, no XML.

If you have further questions, contact me offline.

Kind regards

Bernd



Am 05.04.2014 11:03, schrieb Bernd Oppolzer:
> From what you wrote in an older post
>
> <citation>
>
> Everytime I make changes to this SP, I copy the generated load module
> into the load library specified in the WLM JCL.
>
> Now, my requirement is to have to different versions(by versions I
> mean different sources) of the same SP ABCD1234 executing in same WLM
> environment DB2X, so that two differnt front application can invoke
> different versions of this SP ABCD1234. Is this something which can be
> achived, as we have cannot have 2 members in the Load library
> specified in the WLM JCL at the same time?
>
> </citation>
>
> it really sounds to me that you want to support
> two environments, test and production.
>
> Is this the reason behind your request?
>
> If so: I guess the answer would be: different schemas, different WLM
> ENVs,
> different STEPLIBs on the SP JCL.
>
> Thank you, kind regards
>
> Bernd
>
>
>
>
> Am 05.04.2014 10:53, schrieb Bernd Oppolzer:
>> Maybe you should give a bit more information
>> about the reasons for your request, for example:
>> are the two different Java callers different branches
>> or different regions? What's the reason why they need
>> different versions of the SP? Or different stages (test
>> and production)?
>>
>> If we knew that, we could probably come up with some
>> propositions for a solution
>>
>> kind regards
>>
>> Bernd
>>
>>
>>
>> Am 05.04.2014 01:52, schrieb K.K.:
>>>
>>> Team,
>>>
>>> We needed two versions are the same SP with same name in same WLM
>>> environment, as these SPs are being accessed by distributed
>>> applications(which run on Java). Our requirement is to have 2
>>> different sources for the same SP in same WLM environment. We are
>>> currently following different name approch to overcome the
>>> limitation. We are looking at options to see if there is way to have
>>> same SP with diffrent sources in same WLM environment.
>>>
>>> Thank you.
>>>
>>>
>>> ------------------------------------------------------------------------
>>> -----End Original Message-----
>>> ------------------------------------------------------------------------
>>
>
>
> -----End Original Message-----