checking WLMs and policies

william giannelli

checking WLMs and policies

Hello,

What is the best way to check all your WLMs are functioning and the policies are in place?

thanks

Bill

Lizette Koehler

checking WLMs and policies
(in response to william giannelli)
Most shops have a person or team that manages the WLM function in z/OS.



There is probably a WLM ISPF Application that you might be able to see what it going on.



It would help to understand the context of your question.



If the policies were not in place, your system would be not running very well.



I think you can use SDSF (if at z/OS V2.3 or higher) to start to look at various functions in WLM, like panel ENC



Or you can use the RMF ISPF function to view how the system is working.



If you have something else in mind, please provide some details about what problem you are trying to solve.







Lizette





From: william giannelli <[login to unmask email]>
Sent: Saturday, June 22, 2019 12:52 PM
To: [login to unmask email]
Subject: [DB2-L] - checking WLMs and policies



Hello,

What is the best way to check all your WLMs are functioning and the policies are in place?

thanks

Bill



-----End Original Message-----

william giannelli

RE: checking WLMs and policies
(in response to Lizette Koehler)

We were doing a DR test and only after a long period did we find that a WLM Application Environment policy did not have the required startup parameters. I have a batch job that can display the Application Environment and shows the Status. I am hoping that is the status shows as available we can assume the policy is setup correctly.

thanks

Bill

James Campbell

checking WLMs and policies
(in response to william giannelli)
"Correctly" to whom?

/D WLM,APPLENV= ...
will merely show that it is defined and available to WLM. WLM doesn't really have any idea
about what would be correct in terms of running a Db2 environment. Because you could set
up a situation where the WLM definition doesn't need to provide any parameters - it's all in
the STC JCL (well, non data sharing, at least). Who is to say that it is incorrect?

DSNTIJRV might be as good as it gets.

James Campbell


On 23 Jun 2019 at 18:16, william giannelli wrote:

> We were doing a DR test and only after a long period did we find that a WLM Application Environment policy did not have the required startup parameters. I have a batch job that can display the Application Environment
> and shows the Status. I am hoping that is the status shows as available we can assume
> the policy is setup correctly.
> thanks
> Bill


---
This email has been checked for viruses by AVG.
https://www.avg.com

Chris Hoelscher

checking WLMs and policies
(in response to James Campbell)
We verify that db2 wlms are "correct" by executing WLM_REFRESH against a list of environment names - that seems to work for us

Chris Hoelscher| ITI . DB Services . Mainframe Database | Humana Inc.| T 502.476.2538 or 502.407.7266


-----Original Message-----
From: James Campbell <[login to unmask email]>
Sent: Monday, June 24, 2019 9:05 PM
To: [login to unmask email]
Subject: [DB2-L] - RE: checking WLMs and policies

"Correctly" to whom?

/D WLM,APPLENV= ...
will merely show that it is defined and available to WLM. WLM doesn't really have any idea about what would be correct in terms of running a Db2 environment. Because you could set up a situation where the WLM definition doesn't need to provide any parameters - it's all in the STC JCL (well, non data sharing, at least). Who is to say that it is incorrect?

DSNTIJRV might be as good as it gets.

James Campbell


On 23 Jun 2019 at 18:16, william giannelli wrote:

> We were doing a DR test and only after a long period did we find that
> a WLM Application Environment policy did not have the required startup
> parameters. I have a batch job that can display the Application Environment and shows the Status. I am hoping that is the status shows as available we can assume the policy is setup correctly.
> thanks
> Bill


---
This email has been checked for viruses by AVG.
https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.avg.com&amp;data=02%7C01%7Cchoelscher%40humana.com%7C0d5b3acc280d45d4ac1c08d6f90943d1%7C56c62bbe85984b859e511ca753fa50f2%7C1%7C0%7C636970215522679030&amp;sdata=9qsW0P7yMJBZNts69TDCu0B9aQuPM%2BcV8B6TGHdJvlI%3D&amp;reserved=0

-----End Original Message-----

Peter Conlin

RE: checking WLMs and policies
(in response to Chris Hoelscher)

Bill,

If you need to see the symbolics defined to WLM policy for the START command, you can use the PRINT action from the WLM panel in ISPF (under OS in the ISPF master application menu).

It adds one significant line to the output you get from Db2's DSNTWLMB,PARM='ACTION(WLMINFO)':

Start parameters  . . . . DB2SSN=&IWMSSNM,APPLENV='DBC0WLMC' 

I don't see any other tools that easily extract this information. 

Chris' WLM_REFRESH or James' DSNTIJRV are certainly better starting points, especially on the Db2 side. 

pete conlin

william giannelli

RE: checking WLMs and policies
(in response to Peter Conlin)

thank you all for your responses!

I think the best way is to see what each proc requires in terms of start parameters, then go into WLM ISPF panels and display each policy.

thank you all!

Bill