View previous topic :: View next topic
|
Author |
Message |
ashek15
New User
Joined: 20 Oct 2015 Posts: 48 Location: USA
|
|
|
|
Hi All
Can someone pls advise whose responsibility is to maintain(stop/start etc) the WLM address spaces which are used to run DB2 stored procedures? Is it done by Physical DBAs or Systems DBA or Systems Programmer?
Regards |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
Quote: |
Is it done by Physical DBAs or Systems DBA or Systems Programmer? |
The answer is ... Yes! The responsibility depends upon the site; one site may have them started during IPL, another site by the system programmer upon request, another site by automation at a certain time each day, another site .... In other words, your question makes no sense as posted since you are asking about site-specific things and you need to go to your site and ask your site support group or team leader or manager. |
|
Back to top |
|
|
ashek15
New User
Joined: 20 Oct 2015 Posts: 48 Location: USA
|
|
|
|
Thanks Rob for reply. Just to clarify my question is more about whose actually own the responsibility to issue below wlm commands should a dispute occur the same between different teams regarding the same. My understanding is it's system programmer's responsibility and surely not application dba's responsibility as evident from your reply also. Also, pls advise if quiescing wlm address space can impact anything on databases or applications side? Thanks
/VARY WLM QUIESCE/RESUME |
|
Back to top |
|
|
ashek15
New User
Joined: 20 Oct 2015 Posts: 48 Location: USA
|
|
|
|
Sorry for typo above. Imeant to say who should own the responsibility for wlm address space stop/start using '/vary wlm' in case there arise dispute regarding the same between different teams like system programmer , application dba etc. Also what's the command impact on applications? Can it do any damage? |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
Again, you are asking things that are site-specific. There is no general answer saying team X is responsible for such and such a command -- I've worked at sites where operators had to issue all console commands; the site I'm working at now I can issue console commands if needed.
Talk to your site support group -- if there are issues with who should issue certain commands, your company management should be the ones to resolve the issue. |
|
Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010 Posts: 3048 Location: NYC,USA
|
|
|
|
As Robert Said, it is purely site specific but most of the times it is done by DBA's.
In your case, as a programmer you should not make the decision or try to find who does what, delegate it to you Manager for the decision. |
|
Back to top |
|
|
ashek15
New User
Joined: 20 Oct 2015 Posts: 48 Location: USA
|
|
|
|
Thanks guys for your inputs. Can you also suggest what might be the impact of 'quiescing' and then subsequently 'restarting' DB2 WLM address spaces? can it impact/damage anything on application side?
Thanks |
|
Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010 Posts: 3048 Location: NYC,USA
|
|
|
|
This command puts the WLM application environment in QUIESCED state. When the WLM application environment is in QUIESCED state, the stored procedure requests are queued. If the WLM application environment is restarted within a certain time, the stored procedures are executed. If a stored procedure cannot be executed, the CALL statement returns SQL code -471 with reason code 00E79002. |
|
Back to top |
|
|
ashek15
New User
Joined: 20 Oct 2015 Posts: 48 Location: USA
|
|
|
|
Many thanks Rohit |
|
Back to top |
|
|
|