Fix Readme
Abstract
This readme file provides important information about Fix Pack 4 for IBM Workload Scheduler version 10.1.0
Content
IBM Workload Scheduler 10.1 Fix Pack 4 Readme File
- Date
- December, 2023
- Fix Pack Name
- 10.1.0-IWS-FP0004
- Product
- IBM® Workload Scheduler version 10.1.0.04
- General Description
- IBM Workload Scheduler Fix Pack 4 for version 10.1.0
- Product versions and components to which the Fix Pack applies
- This Fix Pack can be applied only on top of IBM Workload Scheduler V10.1.0, and subsequent Fix Packs.
This readme file provides important information about Fix Pack 4 for IBM Workload Scheduler version 10.1.0
The most up-to-date version of this readme can be accessed at the following URL: Fix Pack readmes.
IBM Workload Scheduler version 10.1.0 Fix Pack 4 supports all product versions indicated in the IBM Workload Scheduler Release Notes.
It is divided into the following sections:
Features introduced with Fix Pack 4
Changed features and feature capabilities
APARs and defects fixed in Fix Pack 4
Resolved Common Vulnerabilities and Exposures (CVE)
Known limitations and workarounds
Contacting IBM Software Support
Features introduced with Fix Pack 4
The following features have been introduced with Fix Pack 4:
- Support for TLS V1.3
- For more information on TLS V1.3, see Configuring the TLS V1.3 security protocol
- Universal Base Image 9(ubi9) on docker containers
-
- Docker containers now support UBI9.
- You must use zLinux based on a zOS version z14 or higher if you wish to use the 10.1 FP4 docker containers (with UBI9) on zLinux.
Changed features and feature capabilities
Supported WebSphere Application Server Liberty Base versions
IBM Workload Scheduler 10.1 Fix Pack 4 was formally tested by using WebSphere Application Server Liberty Base 23.0.0.10.
Updated OpenSSL libraries
IBM Workload Scheduler 10.1 Fix Pack 4 has been updated with OpenSSL libraries version to 1.1.1.23 (means 1.1.1w).
OpenJDK Runtime Environment
IBM Workload Scheduler10.1 Fix Pack 4 has been updated with OpenJDK 11.0.20.1" 2023-08-24.
Updated JDBC drivers
- DB2: 4.32.28
- Oracle: 23.3.0.23
- Informix: 4.50.10
Supports TLS v1.3
IBM Workload Scheduler10.1 Fix Pack 4 has been updated to support TLS v1.3.
APARs and defects fixed in Fix Pack 4
This section lists APARs resolved in Fix Pack 4.
APAR | ABSTRACT |
---|---|
IJ18828 | JOB_STREAM_IDENTIFIER and DEP_JOB_STREAM_IDENTIFIER ARE ALWAYS IDENTICAL EVEN WHEN IT INVOLVES DIFFERENT JOB STREAMS IN THE DEPENDENCY |
IJ26359 | JOBSTREAMINPLAN QUERY DIDN'T HAVE THE REQUIRED HOW-MANY FIELD IN THE MANDATORY PARAMETERS |
IJ29124 | JOIN DEPENDENCIES LOADED INCORRECTLY DURING FINAL EXECUTION |
IJ31613 | JNEXTPLAN SCRIPT ACCEPTS INVALID OPTIONS |
IJ31895 | RESTFUL API ON POST HTTP REQUEST THE TASKSTRING AND TASKSTRINGINFO FIELDS ARE TRUNCATED |
IJ33053 | RESTFUL API "SUBMIT JOB STREAM" - NOT POSSIBLE TO SUBMIT WITH TIME RESTRICTION FILTERS |
IJ33610 | THE FILTER DOES NOT WORK WHEN CHECKING THE ARCHIVE-PLAN IN WORKLOAD MONITOR |
IJ40795 | SEGMENTATION FAULT AFTER OPERATOR COMMAND - MODIFYFIX |
IJ40824 | OPENSHIFT DYNAMIC AGENT JOB ABEND WITH AWKKUP024I AND AWKKUP020I MESSAGE |
IJ41797 | 9.5 ON WINDOWS SUBMIT JS FINAL FROM DWC CAN CAUSE MDM CRASH |
IJ41358 | KB0099742 - TWS 9.4,95,10.1 STREAMS ARE NOT BEING ADDED TO THE PLAN DURING FINAL EVEN IF RUN CYCLE IS ALREADY DEFINED |
IJ42166 | CONFIGUREDB FAILS WITH JAVA.LANG.ILLEGALARGUMENTEXCEPTION: UNSUPPORTED PROTOCOLSSL_TLSV2 (DB2 ONLY) |
IJ43801 | A POOL CANNOT BE RECREATED AGAIN ON DATABASE IF IT HAS BEEN RENAMED BEFORE |
IJ43943 | USEROPTS DECRYPTION DOSN'T WORK WITH FIPS ENABLED |
IJ44916 | IWS 9.5 FP6 APP SERVER CRASHES ON JOB STREAM SUBMIT |
IJ44514 | KILL FAILS ONLY TO JOBS DEFINED UNDER FOLDERS |
IJ44696 | THE FILETRANSFER PLUG-IN IS NOT ABLE TO VALIDATE THE FOLLOWING DESTINATION PATH: "\ALIAS" WHERE "ALIAS" IDENTIFIES A REMOTE PATH |
IJ44938 | EVENT ON XAGENT WHITH FOLDER IS NOT WORKING |
IJ45502 | INSTALLATION OF 10.1 WITH CUSTOM CERTIFICATES FAILS (PROVIDING INTERMEDIATE CA IN THE ADDITIONALCAS SUBFOLDER) |
IJ44519 | ISSUE EDITING EVENT RULE |
IJ45023 | CONDITIONAL DEPENDENCY (DOCOND) DOES REMAIN UNDEFINED IF ANY OTHER DEPENDENCY IS NOT SATISFIED TOO |
IJ45095 | CONFIGURING TO USE THE SAME LTPA TOKEN_KEYS |
IJ45889 | STEPS DESCRIBED ON THE FOLLOWING TECHNOTE SHOULD BE ADDED INTO OFFICIAL DOCUMENTATION : HTTPS://WWW.IBM.COM/SUPPORT/PAGES/NODE/ |
IJ46158 | UNABLE TO REGISTER NEW HP-UX AGENT DUE TO ISSUES WITH WS_WSCANHW.SH SCRIPT |
IJ46607 | TEST CONNECTION IS NOT WORKING FOR CYBERARK PLUG-IN |
IJ46984 | GARBLED COMMAND OUTPUT WHEN LANG SETTING IS JAPANESE IN TWS 10.1 |
IJ46960 | WEBSPHERE APPLICATION SERVER LIBERTY BASE SERVICE IS NOT CREATED WHILE THE DOCUMENTATION SAYS THE OTHER WAY AROUND |
IJ46251 | USERS.EXE IN IWS 10.1 FOR WINDOWS NOT BE WORKING AS EXPECTED |
IJ46787 | WHILE INSTALLING AN IWS AGENT WITH -ADDJRUNTIME FALSE PARAMETER, VALUE STILL COMES AS TRUE |
IJ46714 | CHECKSYNC JOB ABEND WITH ERROR AWSJCL075E AFTER CHANGING TWSUSER PASSWORD |
IJ46420 | FTA LOCALOPTS PERMISSION USER AND GROUP ARE SHOWING AS A ROOT IN 10.1 |
IJ46698 | STARTUPLWA/SHUTDOWNLWA FAILS TO START/STOP EDWA SSM AGENT AFTER UPGRADE FTA |
IJ46850 | WHEN TWS SERICES STOP ON ONE OF THE BKM'S, AND THEN ISSUE A LINK TO THAT BKM FROM THE MDM, IT UNLINKS OTHER BACKUP MASTERS AS WELL |
IJ46851 | CENTRALIZED UPDATE FAILS ON FTA-ONLY DUE TO INCORRECT SSL CERT FOLDER |
IJ46692 | EVENT RULE FOR PROMPT STATUS ASKED DOES NOT TRIGGER EVENT ON AD-HOC JOB PROMPT |
IJ47142 | REGARDING ITERATIVE JS SETTINGS |
IJ47325 | USEROPTS FILE IS CREATED WITH A PERMISSION READABLE BY OTHER USER |
IJ47034 | SERVERINST: WAINST216E --WAPASSWORD CONTAINS INCORRECT CHARACTERS (ASTERISK '*') |
IJ47271 | INFORMATION ON COMPATIBILITY LIMITATIONS BETWEEN COMPOSER 10.1 AND 9.4 IS NOT LINKED TO THE INTEROPERABILITY TABLE |
IJ47146 | POD LABLE IS ALWAYS REMAIN AS BACKUP MASTER |
IJ47709 | AIDA THE PLAN TIME FOR RETRAINING CAN NOT BE CHANGED |
IJ47130 | ISSUE WITH IWS V10.1.0.2 FILETRANFER (SENT IS OK BUT RECEIVE IS NOT) |
IJ47233 | A CHANGE IN A RESOURCE QUANTITY IN THE DATABASE IS NOT ALSO IMPLEMENTED IN THE PLAN AFTER JNEXTPLAN |
IJ47543 | WEBSERVICE JOB NOT WORKING AFTER UPGRADE TO 10.1 FP03 |
IJ47179 | WINDOWS FTA USERS IN AD/LDAP GROUPS NOT AUTHENTICATING IN SECURITY FILE |
IJ47121 | MULTIPLE ERRORS IN IWS 10.1.0.3 STDLIST/TRACES/*.MERGE LOGS ERROR: BATCHMAN:* |
IJ47164 | STAGEMAN:AWSBHV021E AN INTERNAL ERROR HAS OCCURRED. STAGEMAN HAS STAGEMAN:ENCOUNTERED AN ERROR WHILE READING A RECORD |
IJ47323 | ENCRYPTION OF SYMPHONY FILE IN ENVIRONMENTS WHERE A LARGE NUMBER OF NEEDS AND PROMPTS, ARE USED CAN INCREASE CPU % AND CAUSE INT |
IJ47659 | AUTOMATION HUB SALESFORCE PLUG-IN DOCUMENTATION IS MISSING THE RESTRESOURCE URL MAPPING INSTRUCTIONS IN APEX FUNCTIONS |
IJ47683 | WRONG STEPS LISTED AT HTTPS://WWW.IBM.COM/DOCS/EN/WORKLOAD-AUTOMATION/9.5.0?TOPIC=EXAMPLES-EXAMPLE-10-UPGRADING-AGENTS-IN-CLUST |
IJ47663 | UNABLE TO MONITOR UPGRADE FTA/DA VIA DWC UPDATE AGENT |
IJ47481 | DBUSER IS NOT AUTOMATICALLY GRANTED ALL NEEDED ACCESS TO HCL WORK LOAD AUTOMATION TABLES ON THE DATABASE SERVER |
IJ47582 | AIDA HOW TO ADD KPI CATEGORY |
IJ47841 | IWS 10.1 DOCUMENT ABOUT AUDIT LOG |
IJ47970 | THE AGENT UPGRADE CAUSING MULTIPLE WORKSTATIONS GOING UNLINKED DURING UPGRADE FROM 9.4 TO 10.1 |
IJ47940 | DETAILED AUTHENTICATION METHOD LIKE THE OAUTH2 REFRESH TOKEN |
IJ47068 | DOCUMENTATION ABOUT VERIFY_CN_STRING DOES NEED TO BE IMPROVED/ADJUSTED |
IJ47315 | INCORRECT RESULT ON DWC FOR USER WITH MODIFY PRIVILEGE |
IJ47148 | ADHOC PROMPTS CREATED WHEN PREDECESSOT FALLS OFF PLAN CREATED AT TOP LEVEL FOLDER |
IJ47505 | MDM LIBERTY CRASHES DURING AN IWS COMPOSER REPLACE COMMAND PROCESSING |
IJ47467 | DATA GATHER OUTPUT DELETED WHEN OUTPUT AND WORKDIR PARMS HAS SAME VALUE |
IJ47471 | NOT ABLE TO ADD DEPENDENCY THROUGH CONMAN USING JOB STREAM ID |
IJ47111 | CENTRALIZED UPDATE FAILS IF WORKSTATION NAME WAS CHANGED |
IJ47135 | EVEN CHANGING CONMAN TRACE AND LOG LEVELS TO WARNING, INFO MESSAGES ARE STORED INTO LOGS |
IJ47537 | OPENS FILE DEPENDENCY IN WINDOWS NOT WORKING AFTER UPGRADING FROM 9.4.X TO 10.1.X |
IJ47583 | EVENT RULE DOCUMENTATION MISS SOME IMPORTANT NOTICE |
IJ47697 | CLEANUPUSERJOBS FILE MISSING ON 10.1 FP3 |
IJ47952 | DWC 9.5 Fix Pack 6 INSTALL ISSUE ON AIX 7.1 |
IJ47377 | SHLIB_PATH AND LD_LIBRARY_PATH ARE NOT EXTENDED IN TWS_ENV.SH FOR HP-UX |
IJ47383 | KB0104364 - IJ47383: LIBERTY STALE CONNECTION ISSUE SHOWING SLQ EXCEPTION IN MESSAGES.LOG |
IJ48456 | WAS CONSTANTLY CRASHES - LIBTWSPLANJNI.SO TENTATIVE FIX |
IJ48777 | IN CONMAN SS ONLY SOME JOB STREAMS IS NOT DISPLAYED |
IJ48505 | UPGRADING Z-CENTRIC AGENTS FOR SUPPORTED OS RELEASES FROM IWS 9.4.0.XX TO 10.1.0.XX |
IJ48417 | AGENTCERTIFICATEDOWNLOADER SCRIPT REQUIRES --DISPLAYNAME PARAMETER |
IJ48900 | CERTIFICATE ISSUE WHILE SCALING UP KUBERNETES ENVIRONMENT. |
IJ48989 | INCORRECT INFO ON THE DOCUMENTATION FOR UPDATING THE DWC |
IJ48628 | WEBSPHERE MQ PLUG-IN | UPGRADE AGENT FROM 9.X TO 10.1 DID NOT SET INTO ITA.INI THE 2 KEYWORDS ARE MISSING |
IJ48550 | UNABLE TO ADD NEW AGENT THROUGH COMPOSER IN 9.5 FP3 |
IJ48628 | WEBSPHERE MQ PLUG-IN | UPGRADE AGENT FROM 9.X TO 10.1 DID NOT SET INTO ITA.INI THE 2 KEYWORDS ARE MISSING |
IJ48550 | UNABLE TO ADD NEW AGENT THROUGH COMPOSER IN 9.5 FP3 |
IJ48841 | CONMAN SBS GENERATED JAVACORE WITH THE COMPILERJNI.CPL_CREATESYM NEW FUNCTION |
IJ48889 | APPLICATION SERVER CRASHES AND THEN SOMETIMES AUTO RESTARTS ITSELF AND SOMETIMES IT DOES NOT |
IJ48945 | THE FOLLOWING ERROR IS LOGGED IN WINDOWS VIEWER EVERY TIME A DAILY JOB IS EXECUTED. FINAL ENDS WITH "SUCC". "REPORT8.EXE" CAUSES AN ERROR |
IJ49064 | POTENTIAL EDWAPROXY COMMUNICATION FAILURE WHEN FTA CENTRALIZED UPDATE IS GOING THROUGH DM |
IJ49033 | IWS FILE WATCHING DOES NOT WORK FOR FILES LARGER THAN 2GB. |
IJ49106 | SWITCHMGR DDM TO BDDM DOESNT WORK CORRECTLY AT 9.5 FP6 SEC FIX FIXES (SECURITY-202212 +TS013441722_95FP6SEC_IJ45754 NOV) |
IJ49034 | FAILING TO GET THE BACKUP VALUE, THE ESTIMATED TIME IS SET TO THE DEFAULT ONE, WHICH IS 0 |
KB0106398 | USERS NOT ABLE TO AUTHENTICATE USING OKTA / KEYCLOAK ON HCLNOW |
KB0106666 | SINGLE SIGNON DOES NOT WORK WHEN REPLICASET IS 2 (FOR WA-CONSOLE) |
Defects | ABSTRACT |
---|---|
WA-116846 | Lar_Run_log failed in all Lar suits |
WA-120882 | Add missing directories |
WA-104172 | DOC_Change: #WA-100378 Solaris SPARC Centralized Update job process not works |
WA-120463 | Missing "audit" folder in datagather |
WA-121722 | 10.1 FP4: Upgrade from BOTH 10.1 FP4 to BOTH 10.2 GA doesn't work from Centralized Update (Linux) |
WA-121981 | 10.1 FP4: Upgrade from BOTH 10.1 FP4 to BOTH 10.2 GA doesn't work from Centralized Update (Windows) |
WA-120312 | 10.1FP4 docker server container fails to run first JnextPlan after container creation |
WA-118916 | Case TS013299667.Encrupt Feature IMPROVE HOW TO disable it and able to work with conman/dwc with archived Crypted Sym |
WA-121212 | Upgradin the z-centric agent |
WA-121905 | 10.1 FP4: Java job and database job plug-in not working properly after upgrade from 9.4 FP7 |
WA-112005 | Incorrect "File dependencies behavior" description for "Pools and dynamic pools" |
WA-113492 | DOC_Change: #WA-113350 AHA-347 - WA-100029 is causing undesired data in the audit trail |
WA-112826 | DOC_Change: #WA-112343 AHA-347 - WA-100029 is causing undesired data in the audit trail |
WA-111934 | HWA DOC:modify entitlement related documentation |
WA-117419 | Missing CURLOPT_TIMEOUT for JobManagerGW |
WA-120804 | Porting:conman: Poor performance when submitting jobs on FTA |
WA-122222 | twstrace -enable not works and raise AWSITA249E "SSL connect error" message |
WA-122225 | DA freash with local GW raise "SSL connect error" |
WA-121896 | Docker on UBI9 does not start wa-server |
WA-121740 | 10.1 FP4 docker server container fails to run first JnextPlan after container creation |
WA-101448 | CLONE - plug-in jobs in exec after agent restart |
WA-121720 | UNABLE to decrypt Symphonysendable.sth file from datagather |
WA-122102 | All external plug-ins fails test connection |
WA-123191 | 10.FP4: add information about Centralized update HP and SOLARIS |
WA-121807 | crash on the submission |
WA-123143 | TS013694489 switchmgr DDM to BDDM doesnt work correctly at 9.5 FP6 Sec Fix Nov |
WA-122669 | MDM 10.1 FP4: Update installation fails on Windows |
WA-124007 | s390x docker MDM not being generated |
WA-123939 | Harbor : WA-DEV : 10.1_L3- wa-Fileproxy : io.quarkus:quarkus-core (FileProxyApp-runner.jar) : MEDIUM |
WA-123938 | Harbor : WA-DEV : 10.1_L3-wa-Fileproxy : io.netty:netty-handler (FileProxyApp-runner.jar) : MEDIUM |
WA-123941 | Harbor : WA-DEV : 10.1_L3- wa-Fileproxy : io.quarkus:quarkus-vertx-http (FileProxyApp-runner.jar) : HIGH |
WA-123775 | DOC_Change: #WA-121171 DDM switch to BKDDM not works properly |
WA-123962 | Docker Z failing |
WA-123910 | Update LINUX DWC from 10.1FP3 to 10.2.1: DWC doesn't work |
WA-123940 | Harbor : WA-DEV : 10.1_L3- wa-Fileproxy : io.quarkus:quarkus-undertow (FileProxyApp-runner.jar) : HIGH |
WA-122828 | L3 java compile issue |
WA-123373 | New Informix JDBC drivers (4.50.10) raise ClassNotFoundException when launching configureDb script |
WA-123784 | Linux and AIX SSM agent processes not starts |
WA-122929 | Change TWS10ZCON_@MYWHITEBRAND@ references to TWS10ZCON_L3_@MYWHITEBRAND@ |
WA-122856 | 10.1 FP4: wrong JRE version on Windows platform |
WA-123682 | [Docker] HCL server installation still asks for flexera parameters |
WA-121818 | AIX twsinst output "nslookup: not found" |
WA-122292 | [CLOUD] After certificate rotation all the agents get unlinked |
WA-120366 | erroneous conman command in tws_pull_info.go |
WA-122118 | Docker WA server does not start after successful installation |
WA-122761 | Master HCL installation asks for licenseserverid parameter |
WA-123242 | missing displayname parameter in AgentCertificateDownloader usage |
WA-121427 | DWC windows fresh installation fails due to Type mismatch: 'checkMultipleUsers' |
WA-122925 | Linux MDM installation fails in commonFunctions script for unexpected token `}' |
WA-120088 | twsinst -renew fails on linux |
WA-122674 | Windows MSSQL upgrade from 9.5FP6 fails at Configuring WLP phase on TestConnection even if previous ConfigureDb succeed |
WA-123166 | 10.1 FP4 includes webui_dashboard from stable_dev and not from stable_10.1L3 |
WA-122963 | waPostConfigure.vbs still use licenseserverid and licenseserverurl parameters |
WA-123415 | Job J2EE failure due to connection factory not found |
WA-123368 | Stageman crash on Windows during JnextPlan |
Resolved Common Vulnerabilities and Exposures (CVE)
- CVE-2021-42550
- CVE-2017-5929
- CVE-2005-2541
- CVE-2022-48303
- CVE-2022-37434
- CVE-2018-12699
- CVE-2019-19012
- CVE-2019-9636
- CVE-2022-3515
- CVE-2022-24963
- CVE-2023-40743
- CVE-2023-5072
- CVE-2023-3978
- CVE-2022-47629
- CVE-2023-34462
- CVE-2023-39129
- CVE-2023-40743
- CVE-2023-27866
- CVE-2023-34462
- CVE-2023-27866
- CVE-2023-5072
- CVE-2022-47673
- CVE-2022-47695
- CVE-2022-45703
- CVE-2022-44840
- CVE-2020-19726
- CVE-2021-3826
- CVE-2022-47696
- CVE-2023-1579
- CVE-2020-35342
- CVE-2021-46174
- CVE-2023-2222
- CVE-2021-32256
- CVE-2022-47011
- CVE-2022-35206
- CVE-2022-47008
- CVE-2022-48063
- CVE-2022-48065
- CVE-2022-35205
- CVE-2023-39130
- CVE-2023-39128
- CVE-2020-21490
- CVE-2022-47010
- CVE-2022-47007
- CVE-2022-4285
- CVE-2020-19724
- CVE-2022-48064
- GHSA-xpw8-rcwv-8f8p
Known limitations and workarounds
- Upgrading the dynamic agent on Windows, the System Service Monitor (SSM) agent does not run
- Upgrading the dynamic agent to V10.1 on a Windows environment, the SSM agent does not run anymore.
Workaround:To make the SSM agent work, proceed as follows:
- Stop the dynamic agent by launching the following command: ShutDownLwa.
- Change the value of the WinServiceName property in tws_cpa_ssm_agent_<TWSUSER> in the following file: <TWA_HOME>/TWS/EDWA/monitors/ssmagent.opts.
- Start the dynamic agent by launching the following command: StartUpLwa.
- IBM Common Inventory Technology scanner ceases HP support
- IBM Common Inventory Technology scanner does not support HP operating systems starting from January 1st 2023. The IBM Workload Scheduler dynamic agent utilizes IBM Common Invetory Technology to collect system configuration data used in the definiton of dynamic pools. For customers using dynamic agents on HP and dynamic pools, we strongly recommend to review dynamic pool workstation definitions. If their requirements are based on filesystems, especially network or remote filesystems, we strongly recommend to remove the HP dynamic agent from the dynamic pool, since management of the requirements may not be accurate.
- Upgrading to V10.1 Fix Pack 4 or later on a cloud environment, an error occurs
-
When you upgrade to V10.1 Fix Pack 4 or later on a cloud environment using the helm chart, the following error occurs:
Error: failed to create patch: The order in patch list [map[name:SSL_PASSWORD valueFrom:map[secretKeyRef:map[name:iwa-ssl-secret]]] (and a long stack trace)
Workaround: To successfully upgrade the environment, proceed as follows:- Download again the helm chart from GitHub: https://github.com/WorkloadAutomation/ibm-workload-automation-chart.
- Configure the values.yaml file as described in the readme.
- Run the upgrade command from the cloud environment:
helm upgrade <workload_automation_release_name> <repo_name>/hcl-workload-automation-prod -f values.yaml -n <workload_automation_namespace>
- Rest API submit job stream not possible with time restriction filters
- Submitting a job stream with restful API is not possible when using time restriction filters.
Workaround:The Rest API is POST /plan/{planId}/jobstream/{jobstreamId}/action/submit_jobstream with the jobstreamId as NONE value, the planId where the job stream has to be submitted and the body with the SubmitJobStreamInfo as following:
To avoid inserting manually all jobs definitions, use the response of the Rest API POST /plan/{planId}/jobstream/{jobstreamId}/action/make_jobstream that requires the jobstreamId, the planId and the following body:
The response of the make_jobstream Rest API can be used as a job stream field in the submit_jobstream API body. Before calling the Rest API it is necessary to replace all the occurrences of timeRestriction with the correct ones and whatever you need to change for the submission.
- Remote Command plug-in on Cloud
- CLOUD TASK LAUNCHER - REXEC is a not supported protocol for Remote Command plug-in on Cloud.
- Pool workstation details defined on the dynamic domain manager are not visible after switching the dynamic domain manager to backup dynamic domain manager
- When you install a dynamic domain manager and then switch it to backup dynamic domain manager, the operation seems to be successful if you check the environment from the command line, but in the dynamic domain manager database some fields in the
PPS_PRODUCT_PROPERTIES
table are not correctly updated and still refer to the workstation which was previously the dynamic domain manager. An error similar to the following is returned:Workaround: To workaround the problem, perform the following steps:- Retrieve the domain ID by running a query similar to the following:
- Check that the domain ID is correct.
- Correct the following fields in the table:
DomainManager.Workstation.NameThis is the workstation name of the new dynamic domain manager. Verify the current value is the expected one. You can obtain this value using the conman command line or from the
MDL.WKS_WORKSTATIONS
table on the master domain manager.MasterDomainManager.HostName This is the full qualified host name or the IP of the new master domain manager. Verify the current value is the expected one. You can obtain this value using the conman command line or from the
MDL.WKS_WORKSTATIONS
table on the master domain manager.MasterDomainManager.Name This is the workstation name of the new master domain manager. Verify the current value is the expected one. You can obtain this value using the conman command line or from the
MDL.WKS_WORKSTATIONS
table on the master domain manager.MasterDomainManager.URIs This is the list of the master domain managers to be contacted by the dynamic domain manager The list must contain in the first position the new master domain manager and in second position the new backup master domain manager.
DomainManager.Workstation.Address This is the full qualified host name or the IP of the new dynamic domain manager.
- Retrieve the domain ID by running a query similar to the following:
- Installation 10.1 agent on IBMi with any fix pack
- Installing a 10.1 agent on IBMi requires you to use the following parameters:
- Either use wauser, wapassword, and
jwt=false
parametersThe Installation appears as follows:./twsinst -new -acceptlicense yes -agent dynamic -uname username -displayname DA_IBMI186 -inst_dir /TWSINSTANCES/DA102FP1 -tdwbhostname MDM_hostname -tdwbport MDM_port -wauser wauser -wapassword wapassword -jmport 37477 -hostname agent_ip_addr -jwt false
or
- The
agentcertificatedownloader
command must be executed withjwt=false,
jwt=false, and you must install usingjwt=true
or via sslkeysfolder and sslpassword. This is applicable to all versions of fix packs that reference a 10.2.1 master.If the certificate did not register on the MDM, you have to run the agentcertificatedownloader command to retrieve it. The command appears as follows:
./AgentCertificateDownloader.sh --tdwbport TDWB_port --tdwbhostname TDWB_hostname --wauser wauser --wapassword wapassword --work_dir /your_dir --jwt false
- Either use wauser, wapassword, and
- Performing the centralized agent update
- Before performing a centralized update on fix packs or upgrade on releases on a stand-alone fault-tolerant agent to V10.1 Fix Pack 4, you must enable, if not already enabled, the use of the HTTPS protocol to connect to the event processor server. For more information about enabling enEventProcessorHttpsProtocol | eh, see Global options - detailed description.
Fix pack structure
This section describes the structure of the images contained in this Fix Pack.
- Fix pack files available for IBM Workload Scheduler using FixCentral
-
This is the structure of the Fix Pack for the engine on Fix Central:
+----README.zip | +---10.1.0.04-IWS-AGENT-IBMi.zip | +---10.1.0.04-IWS-SERVER-AIX.zip | +---10.1.0.04-IWS-AGENT-AIX.zip | +---10.1.0.04-IWS-BATCH_REPORT-AIX.zip | +---10.1.0.04-IWS-AGENT-HPIA64.zip | +---10.1.0.04-IWS-AGENT-SOLARIS.zip | +---10.1.0.04-IWS-SERVER-LNX_X86_64.zip | +---10.1.0.04-IWS-AGENT-LNX_X86_64.zip | +---10.1.0.04-IWS-FILEPROXY-LNX_X86_64.zip | +---10.1.0.04-IWS-OCLI-LNX_X86_64.zip | +---10.1.0.04-IWS-BATCH_REPORT-LNX_X86_64.zip | +---10.1.0.04-IWS-SERVER-LNX_Z.zip | +---10.1.0.04-IWS-AGENT-LNX_Z.zip | +---10.1.0.04-IWS-FILEPROXY-LNX_Z.zip | +---10.1.0.04-IWS-BATCH_REPORT-LNX_Z.zip | +---10.1.0.04-IWS-BATCH_REPORT-LNX_X86_64.tar | +---10.1.0.04-IWS-SERVER-WINDOWS.zip | +---10.1.0.04-IWS-AGENT-WINDOWS.zip | +---10.1.0.04-IWS-FILEPROXY-WINDOWS.zip | +---10.1.0.04-IWS-OCLI-WINDOWS.zip | +---10.1.0.04-IWS-BATCH_REPORTS-WINDOWS.zip | +---10.1.0.04-IWS-AGENT-LNX_PPC_LE.zip | +---10.1.0.04-IWS-OCLI-MACx86.zip | +---10.1.0.04-IWS-BATCH_REPORTS-Z_USS.tar | +---10.1.0.04-IWS-ZAGENT-IBMi.zip | +---10.1.0.04-IWS-ZAGENT-AIX.zip | +---10.1.0.04-IWS-ZAGENT-LNX_Z.zip | +---10.1.0.04-IWS-ZAGENT-HPIA64.zip | +---10.1.0.04-IWS-ZAGENT-SOLARIS.zip | +---10.1.0.04-IWS-ZAGENT-LNX_X86_64.zip | +---10.1.0.04-IWS-ZAGENT-WINDOWS.zip | +---10.1.0.04-IWS-ZAGENT-LNX_PPC_LE.zip | +---10.1.0.04-IWS-DOCKER-ZAGENT-LNX_X86_64.zip | +---10.1.0.04-IWS-DOCKER-ZAGENT-LNX_Z.zip | +---10.1.0.04-IWS-DOCKER-SERVER-LNX_X86_64.zip | +---10.1.0.04-IWS-DOCKER-AGENT-LNX_X86_64.zip | +---10.2.1.0-IWS-DOCKER-AIDA-LNX_X86_64.zip | +---10.1.0.04-IWS-DOCKER-FILEPROXY-LNX_X86_64.zip | +---10.1.0.04-IWS-DOCKER-SERVER-LNX_Z.zip | +---10.1.0.04-IWS-DOCKER-AGENT-LNX_Z.zip | +---10.2.1.0-IWS-DOCKER-AIDA-LNX_Z.zip | +---10.1.0.04-IWS-DOCKER-FILEPROXY-LNX_Z.zip | +---10.1.0.04-IWS-OCLI-MACARM.zip | +---10.1.0.04-IWS-OCLI-MACx86.zip
Installing the Fix Pack
This section describes how to apply Fix Pack 4 to IBM Workload Scheduler.
- Installation notes
-
- Before installing the Fix Pack, ensure you have installed the required prerequisite software. To obtain the latest information about software requirements for IBM Workload Scheduler, run the Detailed Software Requirements report and browse to the relevant section.
- The minimum required WebSphere® Liberty version to successfully install the Fix Pack is 22.0.0.3 or later.
- This Fix Pack supports DB2 Advanced Enterprise Server Edition, Version 10.5 on HP-UX and Sun Solaris operating systems only. It is available for download from the Passport Advantage web site with part number: CNED3ML. After the installation of DB2 Advanced Enterprise Server Edition, Version 10.5, you must manually apply the license activation key (.lic file). The license key must be downloaded separately from the Passport Advantage web site. The part number related to the license activation key is CNED3ML. The key must be registered using the db2licm command. See Applying DB2 licenses licenses for the procedure to register the key.
If you already have installed DB2 Advanced Workgroup Server Edition, you can switch this license with a DB2 Advanced Enterprise Server Edition license, by following the procedure in Updating licenses. Note that when the procedure references the product-identifier as in step 3:
db2licm -a product-identifier
, replace the product-identifier with the file representing the license activation key (.lic). - Before installing this Fix Pack on AIX® V7.1 operating systems, you must apply the patch for APAR IZ99634. For more information, see: APAR IZ99634.
- On UNIX™ operating systems, before installing the IBM Workload Scheduler Fix Pack, ensure that your umask is set to 022. To verify that umask is set to the correct value, from a command prompt, run the umask command. If the value is different from 022, modify it by running the command:
umask 022
- On UNIX operating systems, the database administrator must have read and run privileges for the IBM Workload Scheduler installation path; otherwise the installation fails. (54367)
After the Fix Pack installation completes, verify the following information:- This Fix Pack installs a new version of the file tws_env.sh (tws_env.cmd) and also creates a backup file named, tws_env.sh.bk (tws_env.cmd.bk), which are both saved to the TWA_HOME/TWS directory, where TWA_HOME is the IBM Workload Scheduler installation directory. After installing the Fix Pack, if you have modified the original version, merge the content of the new version with the content of the original version to carry your customized content into the new version.
- On IBM i operating systems, if you want to install the Fix Pack on the agent for z/OS and IBM Workload Scheduler Dynamic Agent, verify that the user profile used as TWSUser is not a member of a group profile. Set the group profile associated with the TWSUser to *NONE. If the TWSUser is a member of a group, the Fix Pack installation fails.
- Only on Windows™ operating systems, to correctly display double-byte character set (DBCS) characters, you must perform the following actions:
- Set the
LANG
environment variable to the DBCS language code you want to use, for example,set LANG=zh_CN
. - Set the
TWS_TISDIR
environment variable to the IBM Workload Scheduler home directory, for example,set TWS_TISDIR=C:\FTA\TWS
. - Open the Control Panel window and click Clock, Language, and Region.
- Click Region and Language.
- In the Format tab, choose from the Format drop-down list the language you want to use.
- In the Keyboards and Languages tab, under Display Language, click install and follow the steps to install the DBCS language pack you want to use.
- In the Administrative tab, click Change system locale and, from the drop-down list, choose the language (system locale) you want to use.
- Set the
- When installing a dynamic agent or a fault-tolerant agent, ensure that the agent name does not start with a number. If the name of the dynamic agent starts with a number, use the -displayname parameter at installation time to specify a different name. If the name of the fault-tolerant agent starts with a number, use the --thiscpu parameter at installation time to specify a different name.
- Interoperability notes
- IBM Workload Scheduler version 10.1.0 Fix Pack 4 supports all product versions indicated in the IBM Workload Scheduler version 10.1.0 Fix Pack 4 Release Notes which can be accessed at the following link: Release Notes.
- Installation methods
-
You can install the Fix Pack using one of the following methods:
- For master domain manager or its backup:
- see Updating the master domain manager and its backup
- For dynamic domain manager or its backup:
- see Updating the dynamic domain manager
- For fault-tolerant agent, dynamic agent or domain manager:
- see Updating agents
- Disk space requirements
-
To obtain the latest information about permanent disk space requirements when installing IBM Workload Scheduler on supported operating systems, run the Hardware requirements report and click on the relevant operating system link
Before starting the Fix Pack installation, ensure that you have the necessary disk space available on the file system. Consider that the disk space check calculated by the installation considers the entire space occupied by the TWA_HOME directory. The space required by the backup is the sum of the following directories:TWA_HOME/TWS + TWA_HOME/TDWB + TWA_HOME/wastools + TWA_HOME/properties
If the installation fails because of lack of free disk space, you must stop the installation, free space on your disk, and start the installation again.
In addition to the disk space in the following table, the installation requires an additional 600 MB on the file system where the IMShared directory is located.
Table 3. Disk space requirements for installing a master domain manager or a backup master Fix Pack Operating System Installation directory Temporary directory AIX 2,5 GB 1,5 GB Microsoft® Windows 2 GB 1 GB Linux® 1,5 GB 800 MB Table 4. Disk space requirements for installing the Fix Pack for IBM Workload Scheduler fault-tolerant agents Operating System Installation directory Temporary directory AIX 900 MB 400 MB HP-UX 1.3 GB 400 MB Solaris 920 MB 400 MB Microsoft Windows 700 MB 350 MB Linux 720 MB 350 MB Table 5. Disk space requirements for installing the Fix Pack for IBM Workload Scheduler dynamic agents and z/OS agents Operating System Installation directory Temporary directory AIX 600 MB 250 MB HP-UX 920 MB 400 MB Solaris 580 MB 120 MB Microsoft Windows 800 MB 400 MB Linux 600 MB 250 MB Note: Only on HP and Solaris operating systems, the Fix Pack installation requires also 300 MB free disk space in the temporary directory/var/tmp
.
Documentation updates
Any additions or changes to the documentation as a result of this Fix Pack have been integrated into the online product documentation available in IBM Knowledge Center.
Contacting IBM Software Support
Before contacting IBM Software Support with a problem, refer to the IBM Software Support site by accessing the following Web address: https://www.ibm.com/support/home/
To access IBM support, click the IBM support link at the bottom right of the page.
If you want to contact IBM Software Support, see the IBM Software Support Handbook at the following Web site: http://techsupport.services.ibm.com/guides/handbook.html
- Registration and eligibility.
- Telephone numbers, depending on the country in which you are located.
- Information you must have before contacting IBM https://www.ibm.com/support/home/ Software Support.
Notices
This information was developed for products and services offered in the US. This material might be available from IBM in other languages. However, you may be required to own a copy of the product or product version in that language in order to access it.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
US
For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk.
IBM may use or distribute any of the information you provide in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Director of Licensing
IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
US
Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.
The performance data discussed herein is presented as derived under specific operating conditions. Actual results may vary.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
This information is for planning purposes only. The information herein is subject to change before the products described become available.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to actual people or business enterprises is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.
© (IBM) (2023).
Portions of this code are derived from IBM Sample Programs.
© Copyright IBM Corp. _2023_.
- Trademarks
-
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Adobe™, the Adobe logo, PostScript™, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.
IT Infrastructure Library™ is a Registered Trade Mark of AXELOS Limited.
Linear Tape-Open™, LTO™, the LTO Logo, Ultrium™, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.
Intel™, Intel logo, Intel Inside™, Intel Inside logo, Intel Centrino™, Intel Centrino logo, Celeron™, Intel Xeon™, Intel SpeedStep™, Itanium™, and Pentium™ are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, Windows NT™, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
Java™ and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Cell Broadband Engine™ is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom.
ITIL™ is a Registered Trade Mark of AXELOS Limited.
UNIX is a registered trademark of The Open Group in the United States and other countries.
- Terms and conditions for product documentation
- Permissions for the use of these publications are granted subject to the following terms and conditions.
- Applicability
- These terms and conditions are in addition to any terms of use for the IBM website.
- Personal use
- You may reproduce these publications for your personal, noncommercial use provided that all proprietary notices are preserved. You may not distribute, display or make derivative work of these publications, or any portion thereof, without the express consent of IBM.
- Commercial use
- You may reproduce, distribute and display these publications solely within your enterprise provided that all proprietary notices are preserved. You may not make derivative works of these publications, or reproduce, distribute or display these publications or any portion thereof outside your enterprise, without the express consent of IBM.
- Rights
-
Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either express or implied, to the publications or any information, data, software or other intellectual property contained therein.
IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of the publications is detrimental to its interest or, as determined by IBM, the above instructions are not being properly followed.
You may not download, export or re-export this information except in full compliance with all applicable laws and regulations, including all United States export laws and regulations.
IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.
Was this topic helpful?
Document Information
Modified date:
19 July 2024
UID
ibm17096422