Release Notes
Abstract
IBM Workload Scheduler Version 10.1.0 Release Notes
Content
The Release Notes for IBM Workload Scheduler, version 10.1.0 contain the following topics:
- Interoperability tables
- Fix packs
- Software limitations and problems, and their workarounds
- APARS Fixed in this release
- Documentation updates
- Support statements about IBM Workload Scheduler containers on Amazon Elastic Container Service (ECS)
To download the appropriate package for your operating system, see the IBM® Workload Scheduler download page.
For detailed system requirements for all supported operating systems, see the Detailed System Requirements page.
To download AI Data Advisor (AIDA), see AI Data Advisor download page.
For detailed system requirements for AI Data Advisor (AIDA), see AI Data Advisor Detailed System Requirements page.
To access the IBM Workload Scheduler documentation, see the online IBM Documentation.
A complete list of new or changed functions in this release are documented in the Summary of enhancements. More information about new features can be found on the IBM Workload Automation What's New page. See also the V10.1.0 dedicated playlist on the Workload Automation YouTube channel.
- Java software prerequisite changed to version 11
- Java is a prerequisite for Java job plug-ins and other Java-based functions. With this release, the supported version has been changed to Version 11. This version of Java is not available on HP-UX and Solaris SPARC operating systems. If you install on these operating systems, use the Java Version 11 provided with the operating systems. This change applies to the twsinst script: before launching this command on HP-UX and Solaris SPARC operating systems, provide the path to Java. For more information, see Agent installation procedure Agent installation parameters - twsinst script.
Interoperability tables |
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:
| AIDA | AI Data Advisor |
| DA | IBM Workload Scheduler dynamic agent |
| DDM | IBM Workload Scheduler dynamic domain manager or backup dynamic domain manager |
| DM | IBM Workload Scheduler domain manager |
| DWC | Dynamic Workload Console |
| FTA | IBM Workload Scheduler fault-tolerant agent |
| MDM | IBM Workload Scheduler master domain manager or backup master domain manager |
| ZWS Agent | IBM Z Workload Scheduler Agent |
IBM Workload Scheduler: compatibility
Compatibility is supported on the latest available fix pack for each IBM Workload Scheduler release listed in the table:
|
MDM |
DDM |
DM |
FTA |
DA |
ZWS Agent |
|
| MDM 10.1 |
10.1, 9.5, 9.4
|
10.1, 9.5, 9.4
|
10.1, 9.5, 9.4
|
10.1, 9.5, 9.4
|
9.4
|
|
| DM 10.1 |
10.1, 9.5, 9.4*
|
10.1, 9.5, 9.4
|
||||
| FTA 10.1 |
10.1, 9.5, 9.4*
|
10.1, 9.5, 9.4
|
10.1, 9.5, 9.4
|
|||
| DA 10.1 |
10.1, 9.5, 9.4
|
10.1, 9.5, 9.4
|
10.1, 9.5, 9.4
|
|||
| DDM 10.1 |
10.1, 9.5, 9.4
|
10.1, 9.5, 9.4
|
10.1, 9.5, 9.4
|
IBM Workload Scheduler no longer supports TLS V1.0 and TLS V1.1. Only TLS V1.2 is supported and enabled by default in version 10.1 and later. This enhancement ensures a higher security level for SSL communication. Ensure that all agents connecting to a master domain manager version 10.1 or later use TLS 1.2.
* Notes:
1) If you want to upgrade the master domain manager from V9.4 to V10.1, you first need to apply the APAR IJ47731 on V9.4, and then you can proceed with the upgrade. For V9.4 FP7, the APAR is available in Fix Central. The iFix is recommended for mixed environments, such as master domain manager V9.4 and agents V10.1.
2) The composer command line of the agent at version 10.1 works correctly with master domain managers at version 9.5 and later.
Dynamic Workload Console: compatibility
Compatibility is supported on the latest available fix pack for each release listed in the table:
|
MDM
|
DDM | |||
| DWC 10.1 |
10.1, 9.5 FP2 and later, 9.4
|
10.1, 9.5 FP2 and later | ||
AI Data Advisor (AIDA): compatibility
Compatibility is supported on the latest available fix pack for each release listed in the table:
|
MDM
|
DDM | DWC | |
| AIDA 10.1 |
10.1
|
10.1 | 10.1 |
Compatibility scenarios and limitations
You are strongly recommended to maintain all IBM Workload Scheduler components at the latest fix pack level as regular maintenance activity. Keeping your environment consistent also ensures you can implement the new features available with each new release.
Depending on the WebSphere Application Server Liberty version you are using, you might encounter the problems described in the following technotes:
- Versions equal to or higher than 24.0.0.8
- See Possible IWS compatibility issues with Liberty 24.0.0.8 or higher
- Versions ranging from 24.0.0.3 to 24.0.0.9
- See Dynamic Workload Console is not able to open "Monitor Event Rules" nor "Manage workload security" with OpenID authentication
If you are upgrading from version 9.5 to version 10.1.0, you can perform both a parallel and a direct upgrade. If you are upgrading from version 9.4 to version 10.1.0, you can perform a parallel upgrade. For more information, see Upgrading from the CLI.
Note: When upgrading to V10.1 or later, it is required to manually import the certificates of all the required Root CAs into the truststore of the dynamic agent.
If you are using the composer command line of the agent, the following limitation applies:
• The composer command at version 10.1 works correctly with master domain managers at version 9.5 and later.
Environment with agents at version 9.4 and master domain managers at version 10.1
The following consideration applies:
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.
Software limitations and problems, and their workarounds |
The following are software limitations and problems that might affect IBM Workload Scheduler, and their workarounds (when available):
- Mixed-version environment with a master domain manager at a version earlier than 9.5 FP4
- Before you install a component at version 10.1 in an environment with a master domain manager at a version earlier than 9.5 FP4, install the fix for IJ47731 on the back-level master domain manager.
- The fix is available on IBM Fix Central for version 9.4 FP7.
- For other product versions, contact Software Support.
- For more information, see IJ47731: CHECKSYNC JOB FAILED IN IWS 10.1 FP02 - AWSJCL075E ERROR.
- Solution Manager: Wrong filter for Job Monitoring setup
- If you use a workstation as a filter in the plan, the search returns no results.
If the workstation is deleted or a wildcard is used, the jobs in the plan are correctly found.
- Folder management limitations
- Information about some limitations of the folder management are available at IBM Workload Scheduler Version 9.5 Release Notes.
-
Upgrading to 10.1 FP1 can break the JWT functionality if custom certificates were in use
<!-- Starting JWT Token configuration --> <!-- JWT configuration for DA -->
To work around this problem, perform the following steps:
- Update the <jwtBuilder> elements by modifying the keyAlias property to the correct value.
- To verify the signature of a JWT received in a connection from another entity, WebSphere Application Server Liberty Base retrieves the public information associated to the certificate from the <WA_DATA>/usr/servers/engineServer/resources/security/TWSServerTrustFile.jks file. You can find the public information in the keyName=”${mp.jwt.trust.key}” property within the <mpJwt> elements. These elements uses a variable which is declared within the new jwt_variables.xml file that appears in the overrides folder after the upgrade:
<server description=”jwt_variables”>
<variable name=”mp.jwt.trust.key” value=”twstrustkey”/>
</server
- Here the default twstrustkey value is specified. It is required to also add the public information only of the custom certificate in the TWSServerTrustFile.jks file, under that alias (overwriting the already existing one). Alternatively, it is possible to add it as a new entry with a new label, but the jwt_variables.xml file should be updated accordingly. See https://www.ibm.com/docs/en/workload-automation/10.1.0?topic=upgrading-enabling-api-key-authentication-after for reference on this.
- Also the Agent must have the public information associated to the certificate used by the master when creating a new JWT. The reason for this is that also the Agent needs to verify the signature of a JWT received from the master .
Therefore, it is required to also add the public information only of the custom certificate of the master ( the file that was added in the TWSServerTrustFile.jks file on the master ) in the TWSClientKeyStore.kdb file of the Agent.
APARS Fixed in this release |
| APAR | ABSTRACT |
|---|---|
| IJ07357 | EVENT 153 IS NOT LOGGED FOR MDM JOB STREAM |
| IJ08197 | PLAN MIRRORING ISSUE. COMPLETED JOB STREAM REMAINS IN READY |
| IJ20779 | CENTRALIZED UPDATE ON WIN CPUS ARE FAILING |
| IJ21596 | CROSS D/Z DEPENDENCY BEHAVIOR IN THE TIME WINDOW 01:00 - 02:00 |
| IJ22165 | FM - WAS 8.5.5.13 HOLDING "DELETED" SPACE |
| IJ22363 | COMPOSER VALIDATE RUNCYCLEGROUP DOESN'T WORK FOR 9.4 FIX PACK 5 |
| IJ23360 | WAS IS CREATING CORE FILES. APPSERVMAN RESTARTS WITHOUT ISSUE AND NO APPARENT EFFECT ON FUNCTION |
| IJ23565 | DEADLOCKS OCCURING DUE TO PARALLEL CANCEL OF DIFFERENT INSTANCES OF THE SAME JOB STREAM WHEN JOBS HAVE OPENS DEPS |
| IJ23755 | A WRONG FULLYQUALIFIEDNAME ON A DYNAMICAGENT COULD CAUSE OUTOFMEMORY ISSUES ON THE MASTER. |
| IJ24075 | TWS MIRRORING ON OPENS WITH QUALIFIER CONTAINING A BACKSLASH |
| IJ24341 | RETRIEVE JOBLOG BEHAVIOR WHEN SET BEHINDFIREWALL ON ON FTA |
| IJ24741 | "GET STATEMENT" IN THE JOB DEFINITION RETRIEVES ONLY BODY NOT IN THE HEADER |
| IJ25131 | MIRRORING SCHEDULE SCHEDULE STATUS DOES NOT REFLECT THE CORRECT STATE VERSUS THE JOB STATUS |
| IJ25781 | REQUIRED BODY FIELDS ON REST CALL ARE NOT SPECIFIED |
| IJ26357 | IWSHOME/CONFIG/IWA_INIT_IWSUSER SCRIPT HAS NOT BEEN UPDATED FOR 9.5.0 |
| IJ26950 | MIRRORING - DEPENDENCIES NOT UPDATED IN CASE OF DATABASE DEADLOCK |
| IJ28142 | JOB FAILED WITH EXIT STATUS: 127 SCRIPT.SH: CANNOT EXECUTE [TEXT FILE BUSY] |
| IJ28181 | RERUN JOB IS NOT LAUNCHED AFTER RECOVERY JOB FAILED |
| IJ28256 | JOBMANAGER CANNOT START BECAUSE CIT SCAN 0 CORE RESULT |
| IJ28464 | API CALLS: COMPLEX FILTERS NOT WORKING |
| IJ28475 | COMPATIBILITY OF IWS 9.5 WITH SUSE LINUX ENTERPRISE SERVER 15 SP2 |
| IJ28561 | DWC 9.5 FP2 OBJECT VERSION HISTORY NOT VISIBLE |
| IJ28666 | ORACLE EBS JOB PARAMETER IS NOT PASSING CORRECTLY FROM IWA TO ORACLE |
| IJ28693 | REPTR -POST -DETAILS RESULT SHOWS INCORRECT ACTUAL RUN TIME |
| IJ28943 | DOCUMENTATION FOR GLOBALOPTION "ENPREVENTSTART" |
| IJ28947 | TWS 9.5 FP2 WORKLOAD APPLICATION TEMPLATE EXPORT IN XML DEFINITION -HARDCODED- VALUES INSTEAD OF VARIABLES IN EVENTRULE TWSACTION |
| IJ29098 | JOB MANAGEMENT PLUGIN JOB FAILED WITH THE ERROR MESSAGE AWKJMJ043E IF ITS MONITORED JOB ABEND |
| IJ29119 | IWS 9.5.0.1 EXECUTABLE JOB DOES NOT DISPLAY NOR CLONE PARAMETERS IN DWC WORKLOAD DEFINITIONS |
| IJ30074 | PARAMETER WITH A "NULL" VALUE IS NOT PASSED TO ORACLE WHILE SUBMITTING EBS ORACLE JOBS - SHOWS BLANK INSTEAD |
| IJ30181 | SUBMITTING JOBSTREAMS FROM RESTAPI IMMEDIATELY EXECUTES THE JOBSTREAM EVEN WITH INPUTARIVALTIME USED |
| IJ30187 | MDM LIBERTY TERMINATES WITH JAVACORE WHEN LOADING LARGE NUMBER OF JOBS IN ALTERNATE PLAN |
| IJ30316 | DOCUMENTATION SHOULD MENTION THAT THE USE OF DERBY DATABASE FOR TWS SHOULD BE FOR TESTING PURPOSES ONLY OR FOR TEST ENVIRONMENTS |
| IJ30356 | TWS 9.5 WA_PULL_INFO DID NOT COLLECT SYSTEM_INFO DIR WHEN EXECUTED FROM NON -ROOT USER |
| IJ30367 | ADHOC JOB SUBMITTED THROUGH DWC SHOWING AS NULL IN DB TABLE. |
| IJ30421 | DATETIME FORMAT FOR REST CHANGED BETWEEN 9.5.0.1 AND 9.5.0.3 |
| IJ30491 | STERLING PLUGIN DOESN'T WAIT STERLING JOB PROCESS EXECUTION COMPLETION |
| IJ30661 | IN IWS 9.5 JOB STREAM LATE EVENTS(163) ARE FORMATTED DIFFERENTLY FROM THE WAY THEY WERE IN 9.3.X |
| IJ30692 | TWS LOG FILE START TIME NOT CHANGED AFTER CHANGE SOD |
| IJ30714 | ADHOC PROMPTS ON SCHEDULES ARE NOT CHECKED AGAINST THE SCHEDULER FOLDER SECURITY |
| IJ30755 | SPECIAL CHARACTER SEMICOLON (;) IGNORED IN CREATION OF NEW EVENT RULE IN DWC 9.5 FP02 |
| IJ30756 | THE RECOVERY ACTION ON DWC AGAINST THE OBJECT LIKE WORK STATION CLASS OR RESOURCE USING THE VERSION FEATUREFAILS |
| IJ30771 | ZCENTRIC AGENT INSTALL FAILED ON SOLARIS SPARK SERVER WITH PREREQUISITE CHECK |
| IJ30794 | STACK OVERFLOW VIA TIS_CODESET |
| IJ30803 | PREDEFINED SUBMIT JOBSTREAM FAILS WITH AWSJSY508E |
| IJ30805 | ZCENTRIC SSL PEER NAME VALIDATION |
| IJ30827 | JOB STREAM NOT LOADING INTO PLAN |
| IJ30895 | FILE MONITOR EVENT RULE NOT TRIGGERING |
| IJ30902 | 9.5 COMPOSER VALIDATE RETURNS AWSJDB810E |
| IJ30909 | AWSJSY508E ERROR MESSAGE WHEN ANSWERING ADHOC PROMPT ON A JOB IN A FOLDER |
| IJ30951 | TWS 9.5 FP3 FILE TRANSFER JOB ISSUE USING "WINDOWS" PROTOCOL |
| IJ30952 | TWS 9.5 FP3 FILE TRANSFER JOB ISSUE - USER AUTHENTICATION ERROR |
| IJ30991 | AWKAZR008E GET VIRTUAL MACHINES FAILED IWS 9.4 FP5 |
| IJ31007 | TWS ON REDHAT 8.2 AND UPPER LEVEL COULD FAILS AT START TIME WITH ERROR AS <SU: CANNOT OPEN SESSION: MODULE IS UNKNOWN) |
| IJ31169 | FILEWATCH ERROR DUE TO MISSING MOZART DIRECTORY |
| IJ31219 | SPOOL LIST NOT GETTING CAPTURED IN TWS LOGS |
| IJ31250 | CHANGES AND CLARIFICATION NEEDED FOR CONFIGUREDBDB2Z.TEMPLATE TO COMPLY WITH DB2 FOR Z/OS |
| IJ31522 | 9.5 FP3 FILETRANSFER PLUGIN DOES MAKE FILE NAMES CASE SENSITIVE ON WINDOWS PLATFORMS |
| IJ31632 | "CENTRALISEDAGENT UPDATE" PLUGIN JOB FAILS TO UPDATE AGENTS |
| IJ31850 | SUCC IBMI JOBS FAIL ON IWS (CEE9901 AND MCH3601 IN OUT.LOG FILE) |
| IJ31867 | RMSTDLIST SCRIPT FAILING WITH IWS 9.4 FP07 AND IWS 9.5 FP03 |
| IJ31869 | TWS 9.5 FP3 MDM WINDOWS CRASH ON BROWSEJOBLOG AGAINST EXTERNAL AGENT WHEN SSL IS ON. ISSUE WITH OPENSSL 1.1.1G |
| IJ31907 | LIBERTY JAVACORE BY TWSPLANAPI:INI:MAE_ADDSCHEDULEINSTANCE |
| IJ32086 | WAT: THE WS IN FILE MONITOR EVENTS NOT BE MAPPED IN THE DEST ENV (AWSJCO026E IN SOME CASES) |
| IJ32099 | ERROR MIGRATING TWS DATABASE OBJECT (JOBSTREAMS) USING DATAIMPORT SCRIPT. |
| IJ32303 | AFTER THE STREAM NAME IS CHANGED, THE EVENT RULE WHICH HAS THE ACTION SUBMITTING TO THE STREAM DOES NOT WORK AFTER JNEXTPLAN |
| IJ32333 | TWS 9.5 DWC REPORT FROM PLAN COULD HANG WHEN BIG REPORTS WITHOUTANY FILTERS ARE EXECUTED |
| IJ32334 | JOBMANAGEMENT JOBTYPE GETTING FAILED WHILE PERFORMING CANCEL ACTION IN IWS 9.4 FP07 |
| IJ32526 | THE SETTING OF DWC 9.5 WHICH WAS INSTALLED USING NON-ROOT USER WILL BE OVERRIDEN IF UPGRADE TO FP3 |
| IJ32535 | WHEN THE STREAM IS INSIDE A FOLDER PATH, THE JOB "JOB STREAM SUBMISSION" ABENDS WITH -6 (AWKJSJ044E AWKJSJ048E) |
| IJ32769 | IMPORTED EVENT RULES WITH MC_CUSTOM_EVENT TYPES FROM 9.3 CAN'T BE OPENED (VIEW/EDIT) ON DWC 9.5 FP3 |
| IJ32914 | CONMAN INFORMATIONAL MESSAGE NOT BEING SUPRESSED |
| IJ32942 | JOBSTREAM SHOWS IT IS SUCCESSFUL WHILE JOB IS STILL IN EXEC STATE |
| IJ32943 | DYNAMIC AGENT SSH FILETRANSFER MEMORY LEAK |
| IJ33141 | IWS JOBS ON IBM I DO NOT COMPLETE EVEN IF LAUNCHED JOBS DID |
| IJ33146 | BROKER JOBS GO ABEND EVEN WITH EXIT 0 WITH WLP BOUNCE |
| IJ33147 | MISSING RUNCYCLE WHEN USING RUN CYCLE GROUP (RCG) ALONG WITH DELAY FOR DAYS -1 |
| IJ33191 | EVENT RULES CREATED WITH COMPOSER CANNOT BE EDITED PROPERLY WITH DWC |
| IJ33534 | FORECAST PLAN IS NOT WORKING AS EXPECTED. JS FOR SOME WKS MISSING |
| IJ33576 | SCHEDULE'S END TIME PRINTED EARLIER TIMING THAN THE LAST JOB'S END TIME IN IWS94 FP6 |
| IJ33578 | IN DWCINST SCRIPT, -SKIPCHECKPREREQ VALUE MUST BE SPECIFIED IN |
| IJ33584 | FTA JOB STATUS INCONSISTENT WITH MDM AFTER CONFRIM SUCC ON DWC |
| IJ33750 | SKIPCHECKEMPTYDIR PARAMETER MISSING IN IWS 9.5 INSTALLATION DOCUMENTATION |
| IJ33951 | FTP PLUGIN ISSUE, MOVE OPTION IS NOT WORKING |
| IJ34135 | ENEXPANDEDRESOURCES / ER-YES BUT IN MERGE.LOG ERROR IS FOR 32 HOLDERS, HOWEVER 60 JOBS DOES EXECUTE AT A TIME IN THE CURRENT PLAN |
| IJ34150 | COMPLETELY NEW AGENT INSTALLATION ON IBM I FAILS (WCITINST_OS400 NO SUCH FILE OR DIRECTORY) |
| IJ34228 | SQL BASED DB JOBS ENDING WITH "AWKDBE011E SQL JOB EXECUTION ERROR "NULL"" |
| IJ34309 | VALID SAMPLE OF TDWCGLOBALSETTINGS.XML |
| IJ34682 | MISLEADING AWKFTE039E ERROR MESSAGE RETURNED BY FILETRANSFER PLUGIN WHEN PORTS ARE CLOSED ON FIREWALL |
| IJ34794 | FILETRANSFER PLUGIN DOES NOT RETAIN GRANTS ASSIGED TO THE FILE IF THE FILE IS REPLACED |
| IJ34828 | DWC 9.5 FP4 WILL NOT INSTALL CORRECTLY ON Z/OS |
| IJ34844 | PERFORMANCE DEGRADATION QUERYING ALTERNATE PLANS FROM DWC, WHEN THE ALTERNATE PLANS ARE BIG |
| IJ34851 | EXTENDED AGENT JOBS ABENDING AFTER SWITCHING DOMAIN MANAGERS |
| IJ34893 | TWS 9.5 FP4 ONLY: WHEN SSL IS ENABLED BETWEEN EVENT PROCESS AND AGENT SOME EVENT CAN BE LOST AND MONMAN IS NO LONGER RESPONDING |
| IJ34916 | AGENT UPGRADE FAILS DUE TO DOMAIN CONFLICT |
| IJ34924 | CURRENT PLAN EXTENTION TOOK UP TO 1 HOUR |
| IJ34942 | DURING UPGRADE FROM DWC 9.5 FP2 TO FP3: IT WAS OBSERVED THAT THE DWCUSER WAS BEING CHANGED FROM (DWCUSER TO DWCADMIN) |
| IJ34964 | COMMA IS NOT A VALID CHARACTER TO BE USED IN WINDOWS AGENT INSTALLATION USING TWSINST.VBS SCRIPT |
| IJ34965 | DOCUMENTATION TO INCLUDE LIST OF ALL USED PORTS FOR TWA COMPONENTS |
| IJ35447 | CAN NOT RUN START_TWS.SH ON REDHAT 8.X |
| IJ35500 | AGENT NOT RESPONDING PERIODICALLY WITH ITA ERROR THE SEMAPHORE TIMEOUT PERIOD HAS EXPIRED |
| IJ35516 | ADHOC JOB SUBMIT WITHOUT A FOLDER VIA DWC9.5 HAVING THE MDM A SECURITY FILE LIKE 9.3/9.4 GENERATES ERROR. |
| IJ35597 | AGENT DOES NOT START IF NETWORK SERVICES ARE DOWN |
| IJ35626 | 9.5.03 HANDLE LEAK CAUSING AGENT DOWN |
| IJ35680 | SWITCHPLAN JOB CAUSES FINAL JOB STREAM ABEND (AWSBHV004E) DUE TO STAGEMAN CARRYFORWARD JS RECORD EVALUATION AND CORRUPT SYMPHONY FILE. |
| IJ35701 | SHADOW JOBS FROM Z WHEN TRACKING D JOBS DON'T SEEM TO BE USING THE CURRENT PLAN AND USE LAST RUN OF OLD VERSION OF D JOBSTREAM |
| IJ35717 | DYNAMIC JOBS REMAIN IN INTRO AFTER DB SWITCH IN DR PROCEDURE |
| IJ35757 | JOB STREAM SUBMISSION JOB EXECUTION GENERATES TWO JOBS JOBSTREAMS, ONE CORRECT AND ONE IN ADD STATE |
| IJ35878 | WHEN USING TWS 9.5 FP03 OR HIGHER FTP FAILS USING DATASETS IN MAINFRAME WITH LRECL=0 |
| IJ35943 | FAIL TO GET STATUS OF POWERCENTER JOB |
| IJ36139 | AWKAZR008E GET VIRTUAL MACHINES FAILED ON AZURE PLUGIN |
| IJ36203 | RFC_COMMUNICATION_FAILURE, 19 ERROR IN SAP JOBS |
| IJ36244-KB0095296 | JOBS ON DDRIVWN ARE GETTING STUCK IN INTRO, READY STATUS IN PROD WHEN INCREASING THE LIMIT |
| IJ36332 | SPORADIC DUPLICATE PROCESSES BEING TRIGGERED/KOGGED BY DA |
| IJ36844 | AFTER UPGRADING AN IBMI DA TO 95FP5 SOME JOBS DOES NOT COMPLETE AND CPU IS 100% |
| IJ36892 | INCORRECT STATUS OF REMOTE COMMAND JOB IN TWSD AND TWSZ |
| IJ36980 | SQL JOBS - DBMS OUTPUT STATEMENT PROCESSED VALUES NEEDS TO GET PRINTED IN THE IWA JOB LOGS |
| IJ37477 | AFTER PRIORITY IS CHANGED THROUGH DWC, THE STREAM KICKS OFF IMMEDIATELY EVEN IF NOT SCHEDULED TO RUN YET |
| IJ37774 | 4-5 MINS DELAY WHEN USING SSH PROTOCOL FOR REMOTE COMMAND JOB TO WINDOWS SERVER WITH SSH |
| J32749 | STAGEMAN CRASH WHEN GENERATING ORPHANED |
| KB0095518 | IMPROPER TRANSFER OF GDG FILE FROM Z/OS AGENT |
| KB0096483 | MFT FAILS RETRIEVING MORE THAN 10000 FILES (SEARCH COMMAND) |
Documentation updates |
In the Planning and Installation manual, section Reference, add the following commands:
- uninstall
- Use this command to uninstall the File Proxy.
- fileproxystop
- Use this command to stop the File Proxy.
The unistall command syntax is as follows:
UNIX
./uninstall -inst_dir installation_directory [-lang language]
WINDOWS
uninstall.exe -inst_dir installation_directory [-lang language]
where
-inst_dir is the directory where the File Proxy is installed.
-lang is the language in which the messages returned by the command are displayed
The command removes all data related to the File Proxy and leaves the data_dir unchanged.
The fileproxystop command syntax is as follows:
UNIX
./fileproxystop
WINDOWS
fileproxystop.exe
In the Planning and Installation manual, section Reference, File Proxy installation - fileproxyinst script topic, note that the following parameters are required, even though they are documented as optional:
inst_dir
acceptlicense
All other updates to the IBM Workload Scheduler documentation that are required for version 10.1.0 are included in the editions of the publications in online IBM Documentation.
Support statements about IBM Workload Scheduler containers on Amazon Elastic Container Service (ECS) |
Users are not entitled to open a case if the issue is related to the configuration and deployment of IBM Workload Scheduler containers on Amazon ECS.
If an issue occurs on IBM Workload Scheduler at running time, users can open a case only if all these conditions are met:
- The user has a container started
- IBM Workload Scheduler is running
- The user can restart the container inside Amazon ECS
If support believes that a user issue is generated by container deployment, support can ask the customer to reproduce the issue in an officially supported environment.
© Copyright International Business Machines Corporation 2006, 2016. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
© Copyright HCL Technologies Limited 2016, 2022.
Was this topic helpful?
Document Information
Modified date:
05 November 2024
UID
ibm16426831