Ibm release notes for ibm workload scheduler, version 9.4 – united states gas oil ratio calculator

######

The following are software limitations and problems that might affect IBM Workload Scheduler, and their workarounds (when available): File monitor provider events: older event configurations might stay active on workstations after rule redeployment (34103).

If you deployed rules containing event types from the FileMonitor event provider, and then you redeploy rules that no longer include these file monitoring events, you might find that, despite the new configurations, the local monitoring agents still forward the file monitoring events to the event processor. The event processor correctly ignores these events, accordingly with the new configuration specifications deployed on the server; however, a certain amount of CPU time and bandwidth are needlessly misused.

• The state of running event rule instances. This means that any complex event rules, where part of the rule has been satisfied prior to the database migration, are generated after the migration as new rules. Even if the subsequent conditions of the event rule are satisfied, the record that the first part of the rule was satisfied is no longer available, so the rule will never be completely satisfied.

If the master domain manager of your network runs with the enLegacyStartOfDayEvaluation and enTimeZone options set to yes to convert the startOfDay time set on the master domain manager to the local time zone set on each workstation across the network, and you submit a job or job stream with the at keyword, you must also add the absolute keyword to make sure that the submission times are resolved correctly.

The absolute keyword specifies that the start date is based on the calendar day rather than on the production day. File monitor provider events: if you specify a file path with forward slashes (/) in an event rule definition, on Windows workstations this results in the failed detection of the file. (53843)

The enAddWorkstation global option is set to "yes" on a V9.4 Master Domain Manager in a mixed version environment. After you successfully install a V9.4 dynamic agent, the batchman process fails on the V8.6, V9.1 fault-tolerant agents that have the mailman server process configured.

The cause is that the dynamic agent workstation is automatically added to the plan of each agent in the IBM Workload Scheduler mixed version network. The batchman process on the V8.6, V9.1 fault-tolerant agents that have the mailman server process configured is unable to manage the broadcast of the IBM Workload Scheduler event that communicates the addition of the dynamic agent to the plan.

The following are software limitations and problems that might affect the Plug-in for Informatica PowerCenter which is included in the IBM Workload Scheduler Version 9.4 installation: Cannot submit Informatica PowerCenter jobs after a Web Services Hub restart

The following are software limitations and problems that might affect IBM Workload Scheduler access methods and plug-ins included in the IBM Workload Scheduler Version 9.4 installation: Intercepted jobs cannot be relaunched in a z/OS environment (60698).

The process of defining relaunch criteria and collecting and relaunching intercepted jobs is supported only in distributed environments and not in z/OS environments. A request to rerun a process chain is made from the Dynamic Workload Console, but the operation is set to start (61976).

Rerunning a process chain from the Dynamic Workload Console where the operation in IBM Workload Scheduler for z/OS is linked to a special resource that is not available results in the operation being set to start. On AIX 6.1, batchman process does not correctly recognize the time zone of the local workstation (IZ70267)

On AIX 6.1, the batchman process does not correctly recognize the time zone of the local machine that is set to GMT, even if, in the IBM Workload Scheduler CPU definition, it is correctly set to the correct timezone. You see the following message in the stdlist log :

"10:29:39 24.11.2015|BATCHMAN:AWSBHT126I Time in CPU TZ (America/Chicago): 2015/11/24 04:29 10:29:39 24.11.2015|BATCHMAN:AWSBHT127I Time in system TZ (America/Chicago): 2015/11/24 10:29 10:29:39 24.11.2015|BATCHMAN:+ 10:29:39 24.11.2015|BATCHMAN:+ AWSBHT128I Local time zone time differs from workstation time zone time by 360 minutes."

Batchman does not recognize the correct time zone because AIX 6.1 uses (International Components for Unicode) ICU libraries to manage the timezone of the system, and these ICU libraries are in conflict with the IBM Workload Scheduler libraries. Workaround:

. This is an example of a POSIX name convention instead of an Olson name convention (for example America/Chicago). It avoids the new default TimeZone management through the ICU libraries in AIX 6.1, by switching to the old POSIX one (as in AIX 5.x).