For DB2 on Linux, UNIX and Windows environments, the query performance is related to the input variable values (or literals) that are passed to the database. When a query is issued by a user or an application, the database engine will parse the query and transform the query into an internal format that the DB2 engine understands. With the internal query representation, the DB2 query optimizer will try to estimate the execution cost of the possible access plans. Based on the statistics collected in the database, the cost of the query execution will be estimated, and one of the access plans will be selected based on the cost estimate.
If the cost estimate does not correctly reflect the execution cost in real time, it is likely that the access plan picked by the query optimizer might not be optimal. With the literals specified in the query, it would be easier for the query optimizer to have a more accurate cost estimate. On the other hand, it would be more difficult to pick the right plan with parameter markers, especially if the data is not uniformly distributed, since the query optimizer would have to use a generic rule to estimate an average cost because the values are not known. Typically, the normal distribution of the data is assumed.
For IBM Tivoli service management products, if the statement concentrator is enabled, all queries will be translated into queries with parameter markers. To help DB2 query optimizer select a more efficient access plan, specify the bind option REOPT(ONCE) when running the queries. For REOPT(ONCE), query optimization occurs when the query is executed for the first time and the access plan will be reused for subsequent query execution. Through our benchmark measurements, we found that this bind option will help query performance with DB2 in IBM Tivoli service management products.
When opening a PMR with IBM support for a performance issue with IBM Tivoli service management products, there is specific hardware and operating system information that can assist the performance team in diagnosing potential issues that you may be asked to provide. Here is a quick overview of that information the performance team uses to assist in problem determination and the values that are recommended when applicable to a particular environment.
Document available at the following link:
Hi, this is to inform you that there is a new PDF document on the TWS WIKI (path Tivoli Workload Scheduler>TWS Distributed>Distributed-driven scheduling on JES) that compares the two solutions available to schedule wokload from TWS distributed on JES of z/OS. In fact, there are two products that can accomplish this task: Tivoli Workload Scheduler for Applications for z/OS and the Tivoli Workload Scheduler distributed Agent for z/OS. If you have Tivoli Workload Scheduler and a z/OS system where you would like to schedule workload that does not require the use of the Tivoli Workload Scheduler for z/OS apparatus, eiher may provide an interesting solution. The TWSdistributed Agent for z/OS, being of a newer design, is better integrated wih the concept of dynamic scheduling. An for this reason, soon the document will be extended with information on how to migrate from the extended agent of TWS for Applications to the newer agent for z/OS.
alucches 2700012QJC Tags:  data ros v7 collection hoc bilog report qbr ad configure ld 5,607 Views
Over on the Asset Management blog, Pam Denny wrote a helpful post about how to include long descriptions in ad hoc reports.
TWS Integration Workbench V8.6. - How to customize your automation environment by creating a custom Job Type plug-in
Tivoli Workload Scheduler version 8.6 introduced the new Job Type plug-in.
The main feature of this type of job is that everyone can create a new job type that suits various business needs, from the integration with an advanced reporting suite to a file copy. This is possible through the integration of Java and IBM Tivoli Workload Scheduler Integration Workbench V8.6. This, combined with the multiple capacities of scheduling of Tivoli Workload Scheduler, allows end users to extend, integrate and maximize their automation environments. Available tasks for automation include not only advanced software suites but also user's daily tasks.
In the document below we will describe how to create a Job Type Plug-in that meets your automation needs.
MarcusMiranda 270004U8AN Tags:  listener tpae smtp things maximo useful email tiny little 12 Comments 20,129 Views
Welcome to Useful Tiny Little Things, a series of topics published in the Process Automation blog. My name is Marcus Miranda and I work at IBM. The purpose of this series is to provide useful simple things that we sometimes have no idea exist. These tips apply to any Tivoli process automation engine based products.
In this post I’ll show you how to configure the process automation engine to use a preexisting SMTP Server and how to use email features, specifically the Email Listener feature.
I’ve split the instructions into separate sections below so you can configure the process automation engine and the Email Listener separately.
Configuring the Process Automation Engine to Use the SMTP Server
-Log in as maxadmin
-Select Go To > System Configuration > Platform Configuration > System Properties
-On "Global Properties", filter by "Property Name" the text "smtp" and select the "mail.smtp.host" property
-In the field "Global Value", put the name of your machine (it doesn't work if you put localhost or your IP). You can check it in System Properties on the tab "Computar Name". Look for "Full computer name"
-Mark the "mail.smtp.host" property , click the Live Refresh button then click OK to make your changes available right away.
To test whether the configuration is correct, start the SMTP Server, then in a process automation engine product, select Go To > Administration > Resources > People and try setting a new password to anyone registered.
If it is configured correctly, when you click OK to set the password, a new mail should be sent to the person’s email.
Configuring the Email Listener
To configure the Email Listener, a POP email server is required. Any public POP email should work. After the POP email account is created, take note of the email’s address, password, POP server and port (the default port is 110).
-Log in as maxadmin
-Select Go To > Administration > Resources > People, choose anyone but maxadmin and configure the field "Primary Email" with the email (the email created above or the one you already have with an open POP server)
-Select Go To > System Configuration > Platform Configuration > Email Listeners and click the new button
-Complete the fields with the information that you have.
Note that the field "Mail Server" is the POP Server Address (like POP3.server.com, where server.com is usually the public mail domain name) and the field "Protocol" should be POP with the correct port configured.
Note as well, that the workflow should be set to LSNRBP. (If the workflow is not available on the Select Value list, Go To > System Configuration > Platform Configuration > Workflow Designer, select the LSNRBP workflow then activate and enable it).
Using the "Schedule" field you can define how often the email listener will run.
After the configuration, the new email listener should look like this:
-Save your new Email Listener, and then click Select Action > Activate/Deactivate Listener to activate it.
-Click the Select Action menu again, select Security Settings, add a new row as shown bellow:
Using Email Listener to create Service Requests
-Make sure the SMTP Server is running.
-Send a test email to the email address you configured in the Configurating the Email Listener section.
-Wait the Email Listener to run. If everything is correct, a new Service Request should be created with the Subject and the message body of the test email, as the Service Request Summary and Details respectively.
Well, that's it for today!
I hope it helps.
Tivoli Workload Automation 8.6 Customer Collaboration Program DemoDay Session Sprint2 Held on 15th October
on 15th October TWA development team held the DemoDay session for TWA 8.6 Enhancements.
During this special session we presented the TWA Roadmap and demos the incoming new features.
Business User Scenarios has been showed in Short demos and during the interactive session TWA team posted polling questions to collect a concrete feedback and clarify some key points for our next sprint
If you read anything here that spins your fan please contact firstname.lastname@example.org!
TWA Development team is working on main themes:
.....Systems are getting more Instrumented
.....Scheduling is growing in Business Executors
.....Unleash Customer evolution
.....Improve TWS in the Cloud
.....Growing in third-party ERP system
We had an audience of 42 Partecipants and 12 Companies on that session.
All the material that has been presented is now on Early Access Program website:EAP website
Next session will be held on Middle of December.
Hope to see you there!
PamDenny 270000BXV7 Tags:  analysis report bilog v7 data ibmpa translation localization bi 5,608 Views
When disasters like the massive earthquake earlier this year
in Japan, or the deadly earthquake
that hit Haiti
in 2010, people and organizations from all over the world work together to help
and rebuild these devastated areas.
I am very lucky to have the opportunity to help locally by rebuilding houses for people in need thru Habitat thru Humanity. Recently, I worked with an amazing team of individuals, including Power Company Employees, a school teacher, housewife, retired architect, and high school teenagers, in rebuilding a property that will soon house 10 families. Although our knowledge of sister joists and smart squares was minimal, with some explanations we were all quickly on the path of using our universal knowledge of crowbars, hammers and nails.
So how does rebuiliding tie into today’s BiLog entry on localization? Some icons like hammers and nails speak a universal language. Similar universal icons exist in Version 7 to communicate functionality, like the save, edit, delete and print icons. The functionality enabled thru these icons does not have to be explained in words – their images symbolize their functionality.
However, other items must be explained in a language the user understands. Whether it is breaking down the concept of a sister joist to a to a group on non-tradesmen, or detailing the description of an asset or ticket in the language of the user – we often need to enable text in localized languages in V7 and in V7 reports.
V7 reporting has unique requirements, as there are four very different components which must be enabled for localized text values. These include
1. Report Description displayed in Maximo Session
2. Report Request Page displayed in Maximo Session
3. Report Titles/Labels displayed in the Report
4. Report Data displayed in the Report
Each one of these four components is enabled for
localization in a unique way. Whether it
is it thru the corresponding L_Database tables, or thru the use of unique
scripting code within the report design file, the applicable report
description, parameters, titles, labels and data can all display within the
user’s specified language. You can find
information on how each of these components is enabled here.
To enable localization, there are a few key setup steps which you must enable if you have a multiple language environment which are detailed here
And finally, if you have created
custom reports, information on how you can enable them for localization is
This report localization information can also be found in the Report Localization Reference Guide, which contains more details and screenshots, along with detailed sample use cases explaining how you can enable custom report localization. This is listed, along with other report reference guides on this V7 wiki site.
Please comment back if you have any feedback on this, or other topics you’d like to hear about. Thank you!
Do you remember the feeling when you put on a pair of pants that you haven’t worn in awhile, and find money in your pocket? Whether its $1, $5 or even sometimes $20 – its an unexpected wow surprise – finding this great treasure that you didn’t know you had.
This same feeling holds true to the Business Intelligence (BI) features in Maximo. We often spend so much time talking about the new features in each release, that we neglect the hidden treasures.
What are these hidden treasures that you already have in Version 7? The hidden functionality that makes you think ”Sweet” “Cool” “Nice’” “No upgrades required”. It’s functionality in your pocket.
Here’s are just a few of the administrative report hidden features available in Version 7 that I want to make sure you find…..
Reports in a Page – Set the number
of reports that display for your users in the ‘Run Report’ Listing by
configuring this property file
Report Display Order – Define which most frequently accessed reports display first in the Report menu by configuring the Display Order for the report. by accessing the information here
Reporting Database – Configure your reports to execute from a non-production V7 database thru the Configure Data Source action in the Report Administration application, which are detailed here.
Schedule Only Reports – Enable your complex reports to only be scheduled, and not executed immediately as a performance enabler. You can find the details here
Specify Report Run Time – Also as a performance enabler, for your very complex, batch reports, enable your users to only schedule them at non-peak business hours thru this feature
To learn more about these hidden features check out the referenced V7 Report url’s. In the meanwhile, I’ll continue to intermix the ‘functionality in your pocket’ features…along with new features….in the BiLog (Business Intelligence) Blog entries.
Paola Carlesimo 120000BR5P 3,843 Views
Starting from TWS 8.4 the Job Scheduling Console has stopped being the main graphical user interface of TWS and started being replaced by the Tivoli Dynamic Workload Console.
Changing user interface is never an experience particularly appreciated by users, however, in some cases it can provide several advantages.
If you want to understand which benefits you can obtain moving from the Job Scheduling Console to the Dynamic Workload Console and see a summary of the differences and pros and cons of the two interfaces, you can find the following document useful and interesting:
Choices. Every aspect of our lives is packed with them. Firefox, Chrome, Safari or IE? Small, Medium, Large or Jumbo? Mouse or touchpad? Apple pie – with or without ice cream? Shoes, Sneakers or flip flops? To tweet or not to tweet?
Keeping with that trend, we are now enabling you additional choices for your development of V7 reports with the delivery of Portrait Report Templates.
Report Templates are one of a few different ways your report developers can create custom reports in the Version 7 Report Design Tool. Other ways include modifying the delivered reports, or exporting an ad hoc report from the Maximo applications.
When you use the report templates as a starting point for your custom report designs, they already contain for you the required library files and data source to enable the integration between Maximo and reporting. The templates are available in a variety of graph types, and include listing and detail report formats.
Currently, the V7 product delivers landscape templates so the maximum number of fields can be displayed on a report. However, to enable you additional choices and increasing flexibility to meet your unique business needs, you can now download a set of portrait report templates from IBM’s ISM Library. You can download these templates here or by accessing its shortened url at http://bit.ly/iwBvoc
Enabling the new portrait report templates is straightforward. Simply extract the zip file located in the ISM library to the Maximo report directory of your report developer. Then, open the BIRT Report Designer, and select New Report. You will then see an updated listing of templates, including both the previous Landscape and New Portrait Templates. The Portrait templates are identified with the text Portrait in their title, like 'Tivoli Maximo Portrait Subreport Template'.
Your selection of a landscape versus portrait report template impacts the amount of page area available to you horizontally. Landscape reports enable 10” of field space horizontally versus 7.5” of field space with letter size paper.
You can view additional details and on report page size and orientation on this wiki page or by accessing its shortened url at http://ibm.co/ms8QtD. Additionally, information is also in this V7 Report Page reference document here . This document additionally details how you can change all or a subset of your existing reports to use portrait orientation by either modifying the System Library File or the Master Page.
New features in V7 reporting continually enable you additional
report choices……but for your apple pie selection...we would suggest yes...with a scoop of cold, vanilla ice cream!
This document provides information about the Tivoli Workload Automation V8.6 performance tests.
In particular we provide some performance results for the following features:
Document available at the following link:
A document providing information and answers to customers that need to identify and size a suitable environment to successfully manage their required workload for the Tivoli Workload Scheduler V8.5.1 engine in now available at the following link: