This defect manifests particularly with hourly recurring job streams defined to run throughout the day (e.g., EVERY 0100), even when the STARTOFDAY (SD) global option is set to midnight (0000).

An incorrect error message was displayed when an administrator attempted to delete a resource object that shared the same name as another resource but was defined on a different workstation.

A defect prevented administrators from successfully viewing or editing dynamic domain manager pool workstations after upgrading the environment to version 10.1.

A defect in the job management mechanism caused agents not to send job status updates to the master domain manager. This failure resulted in the continuous increase in size of the job table directory because completed job files were not properly cleaned up or communicated to the master domain manager.

A defect in the plan status reporting caused the conamn showjob command to display an incorrect job name for recovery jobs. When you used the command to retrieve the standard list (stdlist) output for a job stream containing a recovery job, the output incorrectly referenced the original job name instead of the system-generated recovery job name.

A defect in the security mechanism caused JWT to fail renewal following the successful rotation of SSL certificates on the master domain manager.

A configuration issue or defect causes the application server to fail to validate security tokens, leading to recurring CWWKS4001I error messages being written to the trace.log file.

A defect in the RMSTDLIST utility script prevents the successful deletion of old directories within the stdlist structure when using the modern find ... -delete command syntax.

A defect in the master domain manager configuration caused the server.xml file to use a hard-coded reference for the key alias within its security configuration.

Need to fix vulnerability CVE-2024-7264.

Dynamic agents encountered frequent Java Heap Space exhaustion, leading to the agent repeatedly unlinking from the master domain manager. Increasing available memory did not solve the issue. Memory consumption issue was tied specifically to the RESTful plugin.

A timing-dependent defect caused the backup master domain manager to stop responding. The issue is due to a timing conflict within the database connection pooling logic, where a request for a new connection clashed with an existing connection attempting to access a configuration file.

A defect prevents users from successfully changing their password using the alter user password in plan function when the new password string includes the backslash character.

The job log generated after rerunning a job was different from the job log generated when running the same job for the first time.

A defect in the scheduling engine caused the memory utilization on the master domain manager to continually increase. The Java process was unable to release memory resources effectively, leading to a progressive memory leak or inefficient resource management.

A critical defect in the File Transfer integration caused the job to fail with a Null Pointer Exception (NPE) when processing a large number of files. The underlying file management code experienced a logic failure when handling the resource list, which led to the NPE and prematurely terminated the file transfer job, preventing the completion of bulk transfer tasks.

When an incorrect value was set, the system incorrectly ran the utility every 5 minutes, rather than reverting to the default frequency of 60 minutes, as stated in the message. This discrepancy between the expected default and the actual operational behavior created unforeseen system load and potential performance risks.

A product defect caused job execution to fail with EXIT STATUS: 127 and the following error "script.sh: Text file busy" when attempting to run a job. This problem occurred specifically on environments where the user HOME directory was configured on a read-only file system.

A performance defect causes the intercom.msg file to grow excessively with CFJOB (Carried Forward Job) messages when multiple job streams containing rerun logic are carried forward across the plan end time.

A product defect caused WebSphere Application Server Liberty to crash frequently, resulting in the generation of JavaCore dump files. This instability occurred when the server invoked the native library LIBTWSPLANJNI.SO (Java Native Interface), indicating an issue within the JNI layer during plan-related operations.

A defect in the object handling logic caused the CPUFOLDER attribute to be erroneously deleted or ignored from the USEROBJ security object definition after modification using the composer mod sdom command. When administrators explicitly included CPUFOLDER in the USEROBJ instruction, the attribute was not maintained when editing or saving the security domain.

Vulnerabilities to be addressed: CVEs: CVE-2025-48795, CVE-2025-48924, CVE-2025-4892, CVE-2012-5783

A defect in the code causes the folder path separator character (the forward slash, /) to be incorrectly removed from the job name and workstation name of a recovery job when its properties are viewed.

The issue occurred while running the conman stop @!/@/@;wait;noask command, which uses a wildcard to target all workstations, including those defined in folders. The code failed to properly handle the memory allocation when processing the large, complex list of folder-based workstation names generated by the wildcard, leading to the memory fault.

A defect in the audit logging mechanism caused the optman option enDbGetOpsAudit (dg) to stop working in version 10.2.2, leading to severe performance degradation. This option, intended to suppress the logging of routine database GET operations, was ignored even when set to 0. Consequently, every database retrieval action was logged to the audit JSON file, which significantly increased the execution time of composer procedures.

A defect in the plan generation logic caused job stream instances scheduled with hourly recurrence to fail to load into the current plan for times occurring after the midnight boundary (12 AM).

The crash resulted in the generation of core files at the agent level, forcing the affected agents offline and disrupting scheduling operations. The issue suggested a recurrent internal stability problem specific to the AIX environment within the dynamic agent process.

A defect in the plan synchronization mechanism caused the planman resync operation, specifically following a SwitchPlan command, to randomly take an excessive amount of time to complete, significantly exceeding standard behavior.

A defect in the communication protocol caused the agent for z/OS to fail when attempting to connect to a dynamic domain manager at version 10.2.4. The connection failure was indicated in the agent log by the message EELHT15E, followed by the response code REST_SERVICE_FAILED (EELHT43I).

A critical product defect caused the WebSphere Application Server Liberty on the master domain manager 10.2.3, Linux OS) to restart frequently, generating multiple Java core files with error AWSBDJ003E The application server has stopped unexpectedly or failed..

A defect caused agents configured to use JSON Web Token (JWT) authentication to disconnect or unlink from the master domain manager following the rotation of SSL certificates rotation on the master domain manager.

A defect in the cleanuserjobs.sh script caused a failure with the database error AWKCLI102E when the environment utilized a PostgreSQL database.

A defect in the scheduling logic caused the jsuntil time to be evaluated incorrectly when a job stream was defined with a time zone that differed from the system and CPU time zones.

A product defect caused SYN flooding to occur on Azure hosts running SLES 15 SP06 when the JobManagerGW and associated agent processes were actively running.

A defect in the job log retrieval mechanism caused the system to return errors when attempting to view or fetch large job logs (observed for file sizes 1 MB or greater). This problem occurred specifically for native jobs, not Java jobs.

The system erroneously required high-level design/model permissions (such as modify rights) to perform a simple operational status change, even when the user possessed the specific operational permissions.

A defect introduced by the new 3DES to AES encryption mechanism caused SAP jobs running on an extended agent to fail with the error EEWO0012E (The extended agent could not be initialized).

A recurring issue caused RESTful API type jobs configured with a callback feature to hang and never return a completion status after submission, specifically in complex environments utilizing a load balancer.

A defect in the conman display sched command prevented locating or displaying a job stream when its assigned extended agent was defined within a folder structure.

A defect caused administrators to lose access to the composer utility on the master domain manager (MDM) following a password change, specifically when the localopts file encryption was disabled.

A defect was introduced during the upgrade of the fault-tolerant agent installed on a Windows operating system, which caused file dependencies to fail resolution. The issue occurred on Windows Server 2016 when jobs defined to run on a dynamic pool utilized a file dependency pointing to a shared file system (UNC path). The internal file check mechanism erroneously failed to verify the existence of files, resulting in the unwanted nF (No File) status.

The defect was related to a wrong location of the BMevent.conf file. In addition, the wa_pull_info command incorrectly collected and duplicated data from its previous runs placed in sensitive directories.

A defect in the logging configuration causes the system to generate an excessive volume of detailed conman entries in the twsmerge.log file, even when the logging level is set to the default INFO level.

A defect in the scheduling object modification logic caused the OUTPUTCOND keyword to be erroneously replaced by the SUCCOUTPUTCOND keyword when an administrator used the OCLI (modify or add) commands.

A defect prevents plan management scripts (including JnextPlan, MakePlan, SwitchPlan, UpdateStats, and CreatePostReports) from correctly deleting the CONSLOG file.

A defect in the Kubernetes deployment package caused integration JAR files to be deleted from the master domain manager container whenever the container was rebooted.

A defect in the cloud deployment configuration caused the master domain manager pod to fail initialization and crash with a mount error after the administrator enabled BmEvents logging. The issue was created because the deployment setup attempted to mount the BmEvents.conf file into the container volume path as if it were a directory.

A defect in the dynamic agent logic caused job duplication when a prolonged contention for an operating system resource lock occurred. The agent thread attempted to acquire a necessary lock and was forced to wait for an extended period. Because the dynamic domain manager default timeout for agent feedback was shorter, the dynamic domain manager prematurely assumed the initial job submission failed. Consequently, the dynamic domain manager submitted the identical job to a different dynamic agent within the pool. When the first job finally acquired the lock, it continued and completed, resulting in the same job executing simultaneously on two separate agents.

A security scan performed against the IBM Workload Scheduler broker port could cause numerous network connections to remain in a CLOSE_WAIT state, leading to the depletion of system resources (such as file descriptors and memory).

A defect in the REST API processing logic caused the API call to fail and return the following error AWSJDB101E: The object "Invalid argument" was not found. The failure was triggered when the JCL (Job Control Language) contained the //OPC SCAN directory. Although the directory itself is valid, the API returned an unexpected error.

A defect caused SAP jobs to fail with decryption and connection errors after upgrading the master domain manager and Dynamic Workload Console to version 10.2.5. The failure occurred specifically when the SAP password ended with the sequence of double equals signs (==), which is commonly found at the end of base64-encoded strings. The r3batch code failed to correctly read or decrypt the password string when it contained this ending sequence, resulting in connection failure and errors such as EEWO0020E ("An internal error occurred while trying to decrypt the R/3 password") and EEWO0124E ("The following SAP R/3 system... is not running").

A defect introduced with REST API 2.0 caused queries utilizing the plan filter parameter to fail, incorrectly returning "0 records". This failure occurred specifically when the enListSecChk global option was set to YES on the master domain manager.

The documentation for the REST API V2 used to submit an ad-hoc job via the swagger interface lacks a crucial example for the task field, despite this field having mandatory internal values.

A defect in the REST API V2 interface caused the plan job output to contain duplicate key names for the dependencyType field within the dependencies array.

Custom paths specified for tablespaces using the --iwstspath, --iwslogtspath, and --iwsplantspath parameters during database configuration are not supported and are therefore ignored when configuring Db2, Db2 for Z/OS, Informix, or Oracle databases.

The database administrator must be informed about reorganizing the tables.

This version incompatibility caused metrics to fail to be exposed in affected environments. Need to correct this configuration error. In subsequent releases, the prometheus.xml file has been removed and the metrics configuration procedure is automated.

Need to clearly specify the password constraints for installation, where enforced in the product. This includes a list of all supported special characters that can be utilized in administrator and system passwords.

Need to list the correct value. The configuration details for failed job events in the BmEvents.conf file should specify Event ID 111, replacing the previous, erroneous listing of Event ID 102.

The system generates platform-specific Event IDs for failed job events, which is the expected and intended behavior but requires clarification in the documentation to avoid user confusion.

Need to improve the Examples section within the absolute interval time dependency documentation to provide clearer, more comprehensive, and current usage scenarios for scheduling constraints.

This error was present in both the official product documentation and Automation Hub. Need to correct the name into application_wa_JobsInPlanCount_job in both locations.

Need to remove the redundant listing of the job count attribute application_wa_JobsInPlanCount_job metric from both the official product documentation and Automation Hub.

The "Converting default certificates" documentation does not include the case for which custom certificates had been implemented. The documentation is adequate if the default certificates are the old, self-signed certificates that were formerly packaged with the product.

Need to clarify the SSM agent documentation to include the two distinct agents: one for the fault-tolerant agent and one for the dynamic agent, including details on their specific deployment and function.

A defect caused the JobManager CPU utilization to increase usage to 100% when submitting RESTful jobs. This excessive CPU usage resulted in performance degradation.

Need to update the doc with information about best practices for job security and stability.