Release Notes for IBM Workload Scheduler, version 9.3

IBM Tivoli Workload Scheduler for Applications and IBM Tivoli Workload Scheduler Plug-in for Informatica PowerCenter are no longer separate installable components. All of the access methods and plug-ins formerly packaged with IBM Tivoli Workload Scheduler for Applications V8.6 and IBM Tivoli Workload Scheduler Plug-in for Informatica PowerCenter V8.6 are now automatically included in the IBM Workload Scheduler Version 9.3 installation.

The level of support provided for the products and components listed in the interoperability tables covers all the shown versions.

In the tables in this section the following acronyms are used:

IBM Workload Scheduler: compatibility

Dynamic Workload Console: compatibility

IBM Workload Scheduler Command-line client: compatibility

Fix packs released for this version of the product

To find the fix packs released for IBM Workload Scheduler, and the Dynamic Workload Console including links to the related readmes files, see Fix Central.

The following are problems that affect the installation or upgrade of IBM Workload Scheduler, and their workarounds (when available):

Tivoli Common Reporting Installation fails on Linux for missing prerequisites (130480).

For Linux operating system, Tivoli Common Reporting installation fails for missing prerequisites. The error message is the following:
CRIMA1217E: A problem occurred during the execution of the /opt/IBM/JazzSM/install/reporting_services/tcrWrapperInstall.xml file.

Two defects have been opened to Jazz for Service Management development team (59346 and 59497).

Workaround

To circumvent the problem, install the following libraries:

• libpng16-16-1.6.13-2.4.1.i586.rpm
• openmotif-libs-32bit-2.3.4-25.3.x86_64.rpm
• openmotif-libs-2.3.4-25.3.x86_64.rpm
• openmotif22-libs-32bit-2.2.4-189.1.x86_64.rpm
• openmotif22-libs-2.2.4-189.1.x86_64.rpm

Error while opening the TCR administrator panel after a successful installation of the Dynamic Workload Console (131760).

After a successful installation of the Dynamic Workload Console and its prerequisites, trying to open the TCR administrator panel, the following error message is displayed:
Error!
Refresh Edit Minimize Maximize
PF-VAL-6171 Error retrieving metadata for the target fragment.
Details | Retry | Hide this message.
Details
DashboardException
PF-VAL-6171 Error retrieving metadata for the target fragment.

A defect has been opened to Jazz for Service Management development team (59497).

Workaround

To circumvent the problem, rename or remove the following jar file:
BirtAdapterB.jar presente in questo path: /reporting/lib/birt-runtime-2_2_2/ReportEngine/lib

Upgrade from V9.1 or V9.2 fails if ipc temporary files are present (111225).

For Unix operating system, during the upgrade from V9.1 or V9.2 to V9.3, if there are files or directories in the path
Inst_Dir/TWS/ITA/cpa/temp/ipc,
these files or directories are not copied into the backup directory and the upgrade fails.

Workaround

To circumvent the problem, before upgrading to V9.3, perform the following steps:

• Stop all processes.
• Check if there are files or directories in the path
  Inst_Dir/TWS/ITA/cpa/temp/ipc
  and, if any, remove them.
• Perform the upgrade to V9.3.

The following are software limitations and problems that 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 status of the local monitoring configuration on the agent is corrected when one of the following occurs:

• The planman deploy -scratch command is issued
• The event processing server is restarted
• Another rule containing an event condition involving the FileMonitor provider is deployed to the agents.

Some data is not migrated when you migrate database from DB2® to Oracle, or to Informix® Dynamic Server, or vice versa. (38017)

Neither of the two migration procedures migrate the following information from the source database:

• The pre-production plan.
• The history of job runs and job statistics.
• 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.

"Absolute" keyword required to resolve time zones correctly with enLegacyStartOfDayEvaluation set. (41192)

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)

This is due to the fact the SSM agent is not currently designed to automatically convert the slash sign to be Windows compatible when running the rule.

Workaround

Use backward slashes when you specify file paths in the definitions of rules that run on Windows systems.

Problems when International Date Line West time zone is used. (80881)

IBM Workload Scheduler is unable to manage the Date Line West time zone (UTC -12).

Batchman fails on V8.6, V9.1 and V9.2 fault-tolerant agents configured with the mailman server process. (96620)

The enAddWorkstation global option is set to "yes" on a V9.3 Master Domain Manager in a mixed version environment. After you successfully install a V9.3 dynamic agent, the batchman process fails on the V8.6, V9.1 and V9.2 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 and V9.2 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.

To solve this problem, set enAddWorkstation to "no" on the master domain manager to prevent the automatic addition of the dynamic agent workstation in the plan.

On Windows 2012: all cli not supported on windows power shell. (100237)

On Windows 2012, the IBM Workload Scheduler command lines are not supported in the Windows Power shell. They work only in the traditional shell.

Wrong Process Name value submitting a Sterling job (133442).

A Sterling type job is defined and submitted. When it completes successfully, the stdlist format of showjobs conman command shows a wrong Process Name (SUBPROC ). This happens because IBM Workload Scheduler submits the Sterling job without specifying the Process Name.

Under certain conditions, the job stream definition keywords maxdur and mindur are not correctly set for the job, as shown by the showjobs conman command (133709).

When maxdur/mindur are expressed as a percentage of the latest estimated duration of the job, and when the job duration is so high that maxdur/mindur values exceed the maximum duration managed by IBM Workload Scheduler (500h:59min), it might happen that maxdur/mindur are not correctly set for the job, as shown by the showjobs conman command. The problem doesn't occur when specifying maxdur/mindur in minutes or as a low percentage value.

The following are software limitations and problems that affect IBM Tivoli Workload Scheduler Plug-in for Informatica PowerCenter that is now automatically included in the IBM Workload Scheduler Version 9.3 installation:

Cannot submit jobs after a Web Services Hub restart

Following a restart of the Web Services Hub, the Plug-in for Informatica jobs launched from the command line end in FAIL state (Error state in the Dynamic Workload Console) and return the following exception in the job log:

AWKIPC005E Failed to run workflow.
---------------------------------------
Remote Exception
----------------------------------------

To enable the correct submission of plug-in jobs, after restarting the Hub, connect to the Informatica PowerCenter Web Services Hub URL and follow these steps:

1. In the Navigator pane, expand Web Service -> Batch WebService, and then click Integration WebService.
2. In the Operations pane, click Try-It from the toolbar.
3. In the Web Service Operations Navigator pane, click login.
4. Fill out the form in the right pane, specifying the required information in the UserName, RepositoryName, and Password text fields.
5. Click Send.
6. In the SOAP Response pane, copy the value for the SessionId tag.
7. In the Web Service Operations Navigator pane, click getWorkflowLog.
8. Paste the value copied previously in the SessionId text field and then enter the required information in the FolderName, WorkflowName, Timeout, and ServiceName text fields.
9. Click Send.

   You can now submit jobs safely again.

The problem is due to an Informatica Powercenter defect, for which change request 296859 is outstanding. A formal solution to the problem should be provided by the Informatica HotFix that will address this change request.

Failure in upgrading Tivoli Workload Scheduler version 9.1 to version 9.x on Oracle partitioned DB (IV79707).

If you perform a direct upgrade from Tivoli Workload Scheduler version 8.5.1 or 8.6 to version 9.3 using an Oracle partitioned DB, the installation might stop with the following error:

"AWSJIM018E The product cannot retrieve the Report tablespace name parameter from the Tivoli Workload Scheduler instance you want to upgrade."

To solve the problem, search on IBM Fix Central for APAR IV79707 and download the related iFix .

Wrong return code evaluation for output conditions present on a job defined on a dynamic agent (148259)

If you define a job with output conditions containing the "AND" or "OR" strings on a dynamic agent, the job completes in ABEND status even if the condition is satisfied.

To solve the problem, type the "AND" or "OR" strings in lowecase.

The following are software limitations and problems that affect IBM Tivoli Workload Scheduler for Applications that is now automatically included in the IBM Workload Scheduler Version 9.3 installation:

Federal Information Processing Standards (FIPS) cryptographic modules are not supported on SuSE Linux 32 bit (55580).

The enigma utility installed with Tivoli Workload Scheduler for Applications, Version 8.6 for encryption on SuSE Linux 32 bit does not work in FIPS operation mode because it is built using libraries that are not compatible with FIPS.

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:

Export the TZ environment variable before starting IBM Workload Scheduler to the old POSIX format, for example, CST6CDT. 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).

IJ02930: Plan data replication in the database (aka mirroring): a job is shown as completed even though job number and start date are missing.

Workaround:

Run planman resynch to update the information in the database to the current status.

• IV15710: MVS OPENS DEPENDENCY IS NOT RECOGNIZED.
   
• IV31688: JOB NAME TRUNCATED FOR EVENT 203 WHEN JOB NAME CONTAINS UNDERSCORE OR HYPHEN CHARACTERS .
   
• IV46778: WHEN TZ IS DISABLED, JOB_RUN_DATE_TIME RESPECTS LOCAL TIME HOWEVER JOB_START_TIME IS NOT IN JOB_HISTORY_V VIEW .
   
• IV47992: "TWSUSER" FILE IS NOT CLOSED BY APPSERVMAN UNTIL APPSERVMAN IS STOPPED.
   
• IV47998: JOB FAILED WHEN JOBNAME CONSISTS OF SPECIAL CHARACTERS.
   
• IV51390: PAM AUTHENTICATION SWITCH LOCAL OS MODE.
   
• IV51987: TIME STAMP IS OFF BY (-) 5 HOURS IN EVENT RULE EMAIL BODY.
   
• IV52046: INCLUDE NEW TIMEZONE TABLE IN NEXT TWS RELEASE(S).
   
• IV53983: WHEN RUNNING TWO DATASTAGE JOBS CURRENTLY ONE IS SUCCESSFUL.
   
• IV54764: WINDOWS REMOTE COMMAND JOB ENDS WITH EXIT CODE 259 AFTER 5 MINUTES.
   
• IV54821: CAN NOT SAVE ER, IF A MBCS CHARACTER IS AT A TRUNCATION POINT OF THE "SCOPE".
   
• IV54879: COMPANY NAME IN OUTPUT BANNER FROM CONMAN.
   
• IV56113: SUBMITTING 2ND JOBSTREAM FROM SAME DISPLAY AFTER SUBMITTING THE 1ST JOBSTREAM WILL CAUSE RESUBMISSION OF THE 1ST JOBSTREAM NAME.
   
• IV56125: EVENT RULE FOR RECOVERY PROMPT DOES NOT WORK.
   
• IV56439: REPORT 10B OUTPUT TRUNCATES JOBSTREAMID AT 15 BYTES.
   
• IV56645: WINDOWS FTP JOBS ABEND WITH A CONNECTION REFUSED MSG.
   
• IV56870: JBXTRACT RETURNS USAGE WHEN THE SECOND CHARACTER OF THE JOB NAME IS U.
   
• IV58430: DST FEATURE CAUSING JOB FLAGS TO BE OVERWRITTEN IN SOME RARE SCENARIO.
   
• IV59126: TWS SERVICE GOES IMMEDIATELY DOWN AFTER RESTART ON WIN 2012.
   
• IV60377: JOBS RUNNING ONE HOUR LATER AFTER DST CHANGE.
   
• IV60621: IMPROVE IV41929, SWITCHING TO OLD INTERACTIVE JOBS BEHAVIOR ONLY.
   
• IV60988: RUNTIME ERROR! R6034 R6034AM: C:\OPT\IBM\TWA91\TWS\CLI\BIN\PARAM91.EXE.
   
• IV61100: MAILMAN RELINK ON STOPPED AGENTS SLOWS PROCESSING.
   
• IV61275: GARBLED CHARACTER AT ZCENTRIC SIDE WHEN USING FRENCH CODEPAGE .
   
• IV61550: HOLD ACTION IS GRAY OUT AND CANNOT PERFORM "HOLD" FOR JOBS ON  TWS 9.1.0 FP0001/TDWC 9.1.0 FP0001 ENVIRONMENT. 
   
• IV61731: GOT THE WRONG JOB NAME THROUGH TWS JAVA API AND WEB SERVICES. 
   
• IV62658: MISSING CHECKS IN JOB STATISTICS UPDATES BY LOGMAN. 
   
• IV62662: COMPLEX VARIANT ARE NOT DISPLAY BY TDWC.
   
• IV62676: PLANMAN CHECKSYNC FAIL WITH AWSJCL075E.
   
• IV62797: THE JOBMANAGER.INI PARAMETER DELAYBEFORECOMPRESSINGSECONDS DOES.
   
• IV62800: VARIABLES DEFINED BY 'PARAM' COMMAND ARE NOT RESOLVED LOCALLY.
   
• IV62943: TIMING OF RELEASING A RESOURCE DIFFERS IN JOB STREAM. 
   
• IV63159: EVENT SEND FROM FTA IS NOT RECOGNIZED BY EVENT SERVER.
   
• IV63216: OPENS FILE TAKES ABOUT 1 SECS PER FILE.
   
• IV63524: ENHANCE THE CHECK ON LIFECYCLE OF SSMAGENT, TO PREVENT MULTIPLE.
   
• IV63764: WS DB LOCK AND LOCK/WAIT CREATED WHEN TDWC QUERIES AND SUBMISSIONS WHEN LOCK ESCALATION.
   
• IV64151: CROSS_DEP PERFORMANCE ISSUES.
   
• IV64313: "WAPPMAN -DISPLAY" OUTPUT IS DISPLAYED AS UNICODE CODE NUMBERS FOR MBCS CHARACTERS.
   
• IV64500: UPDATESTATS JOB ABEND IF USETCL=NO IS USED.
   
• IV64661: AN EXTRA SLASH IS ADDED TO THE TWSREGISTRY.DAT .
   
• IV64796: ZCENTRIC AGENT AT V9.1 LEVEL ON WINDOWS IS FILLING THE DIRECTORY JMJOBTABLEDIR WITH TEMPORARY FILES.
   
• IV64818: AFTER CONMAN STOP THE OK JOBS COUNT IS NOT TALLY WITH ACTUAL SUCC JOBS.
  Note that this problem has been fixed only for conman command-line, but it is still present in the DWC.
   
• IV65189: SATURDAY OR SUNDAY AS NON-WORKING DAY CHECK BOX DOE.
   
• IV65481: "REP11 -M MMYY" RETURNS "START > END" ERROR.
   
• IV65671: JSTREAMS SCHEDULED TO RUN FROM 20 TO 21 (UTC) THE DAY BEFORE DST.
   
• IV66240: RUNNING SIMULTANEOUSLY 2 LOGMAN OR LOGMAN AND UPDATESTATS.
   
• IV66331: "EVENTS-MESSAGE.JAR FILE NOT FOUND" EXCEPTION DURING SERVER STARTUP.
   
• IV66913: KILLED JOB RETURNS ZERO EXIT STATUS.
   
• IV67024: SAP JOBS FOR DYNAMIC AGENT REMAINS IN READY STATE CONSUME CPU LIMIT.
   
• IV67340: PLANMAN RESYNC FAIL IN RARE SITUATION.
   
• IV67413: DWB LEAKS WHEN JOBOUTPUT REQUESTED AFTER JOB COMPLETION.
   
• IV67745: SENDEVENT CRASH ON WINDOWS USED BY DYNAMIC AGENT JOBS.
   
• IV67925: CHECKHEALTHSTATUS NOT CORRECTLY MANAGING.
   
• IV68108: ENGINE TEST CONNECTION ON TDWC FAILS IF REPORTING IS ENABLED AND THE DATABASE IS USING A SECURITY MECHANISM DIFFERS FROM DEFAULT. 
   
• IV68392: MEMORY LEAK ON DYNAMIC AGENT WHEN EDWA IS ACTIVATED. 
   
• IV69081: PARAM "VARIABLE" CMD RETURNS THE VALUE OF A DIFFERENT VARIABLE. 
   
• IV69167: UPDATE FAILS AWSFAB028E THE SUPPLIED PORT NUMBER IS NOT IN THE RANGE 1-65535. 
   
• IV69507: MAGENT CRASH WHEN ISSUING ERROR MESSAGES.
   
• IV70798: NATIVE HEAP COULD ENCREASE DUR TO INCORRECT DIRECT BUFFER USAGE.
   
• IV71081: DEADLOCKS OCCURS DURING WHILE MIRRORING DATA TO DB.
   
• IV71379: SUBMIT JOBS TO STERLING C:D GIVES ERRORAWKSTE029E.
   
• IV71394: BROWSE JOBLOG SOMETIME CRASHES ON LINUX .
   
• IV72096: THE RC4 "BAR MITZVAH" ATTACK FOR SSL/TLS AFFECTS TWS.
   
• IV72947: PLANMAN RESYNC WHEN FAILS IT GOES IN LOOP.
   
• IV86677: JOBSTATCHGEVT.ACTUAL DURATION VALUE IS NOT CORRECT INTO TDWC DISPLAY..
   

Top

© Copyright International Business Machines Corporation 1991, 2015. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.