Hi all, I think the simplest solution for an audit trail is z/OSMF 2.1. The WLM Policy Manager in z/OSMF keeps an audit trail of every change you make, AND keeps a history of previous definitions and policies. Whey create a new system when one already exists? You're going to need to go to z/OSMF at some point, so why not install it first for WLM? Users love WLM under z/OSMF. If you can wait for 2.1, it's best because there are more functions in 2.1, it uses far fewer resources, and is much easier to install. And now that there is no financial reason to delay moving to z/OS 2.1, I recommend that you go for it (see Cheryl's List #179). z/OS 2.1 has been in the field for a year and is a quite stable release.
I partly disagree with John, who said "I'm not holding my breath. z/OSMF is the way IBM is going because the money people in the most companies today don't seem to want experts, they want cheap labor. Like most of today's people who vote "good enough" instead of "excellent" with their wallets." Yes, z/OSMF is the way IBM is going, which means a requirement for a batch audit trail would likely be rejected (given that a function already exists). But the reason to go to z/OSMF is not because people want cheap labor, but because it's simply better (at least in 2.1). If I were a sysprog again, I would definitely prefer z/OSMF to do my standard tasks. I could get my work done more quickly, and with a better audit trail of who did what. The history function of z/OSMF is one of its strengths. Just because the tool is easier doesn't mean that you don't need experts. You still need to understand service classes, performance indicators, and much more. I personally think that z/OSMF reduces the manual effort to let you concentrate on more important matters. Best regards, Cheryl ====================== Cheryl Watson Watson & Walker, Inc. www.watsonwalker.com cell & text: 941-266-6609 ====================== On Nov 24, 2014, at 3:42 AM, Vernooij, CP (ITOPT1) - KLM <[email protected]> wrote: John, This is part of the process we are looking for: unload - batch modify - reload of a policy. This tool does the reload (install) part. This is, together with unload, is the easiest part, it can be done online, because in the OP's and my situation, we have a running system. What is lacking is the batch mass modify part. Kees. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of John Eells Sent: 20 November, 2014 15:00 To: [email protected] Subject: Re: WLM in batch? (Reposting to the list server.) A while back, when it became obvious that we needed a way to prime a WLM policy for new systems, SYS1.SAMPLIB(IWMINSTL) was born. Maybe you'll find the IWMARIDU program useful in this context, and maybe not...if I recall correctly it uses an ISPF table. (I actually helped work on this a long time ago...I've just forgotten the details, I'm afraid.) [email protected] (John Compton) wrote: > Currently, the only way I know of handling WLM policy changes is though the > > ISPF dialogs, screens, etc., that sit behind IWMARIN0. That's all very > > well, but beyond the NOTES function (and/or in-house change control > > documentation), there is no real possibility of an audit trail. > > Is there any way of handling WLM policy processing in batch? > <snip -- John Eells z/OS Technical Marketing IBM Poughkeepsie [email protected] -- John Eells z/OS Technical Marketing IBM Poughkeepsie [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ******************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ******************************************************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
