Fixed Issues - 11.3.6 SP2 CUM1

This article details the issues fixed in CA Workload Automation AE Release 11.3.6 SP2 CUM1.
wcc114sp5p
This article details the issues fixed in CA Workload Automation AE Release 11.3.6 SP2 CUM1.
Contents
QUE_WAIT JOB RUNS ON OFFLINE MACHINE
Problem Number: 3813
Jobs in the QUE_WAIT (QU) state ignore the OFFLINE machine status, hence the jobs ran although the status of the machine is OFFLINE.
SCHEDULER DOES NOT REACTIVATE JOBS IN A FAILED BOX ON RESTART
Problem Number: 4338
When you define a box within another box and specify the n_retrys attribute value and when the scheduler executes the jobs in the inner box and the inner box runs to FAILURE, the inner box was re-run but the jobs inside the box were not re-activated.
SCHEDULER CORES ON STARTUP WHEN REQUEUING AGENT STATUSES
Problem Number: 4349
When the scheduler starts up to process job status messages that were saved from a previous run of the scheduler, the scheduler exited ungracefully. 
In this issue, the scheduler might have been shut down while it was processing many incoming statuses from the agent. Or, the scheduler process might have been abnormally terminated during the previous run leaving unprocessed agent statuses in the database.
When the issue occurs, the scheduler ends immediately on startup. The scheduler log file may contain the following trace message:
Assertion failed: NULL !=
g_ssf._setNget_comm_update,
file /<path>/SystemAgentComm.cpp, line 2619
UJO_COMM_SEND_SEQ TABLE CONTAINS UN-USED COLUMNS
Problem Number: 4350
The UJO_COMM_SEND_SEQ table contains two unused columns (destination and dest_host_alias) that occupy unnecessary space in the database. These two columns were introduced in one of the previous incremental, but were not used in the later versions. Hence, they do not have any significance in the later versions.
UPDATE STATEMENTS IN DB UPGRADE TO USE BATCH MODE
Problem Number: 4351
Applying incremental failed for fix_data.sql when the update statement defined in the fix_data.sql is going to update huge number of rows. The RefreshAEDB.pl script complains that the transaction log is full or there is not enough memory or no space while running fix_data.sql. fix_data.sql runs partially and the required updates do not happen resulting in invalid data in the database.
BOX ENDS INCORRECTLY WHEN FINAL ACTIVATED JOB GOES ON_ICE
Problem Number: 4352
The scheduler always evaluates a box to SUCCESS after you manually place the last remaining ACTIVATED job on ice even if the box contains jobs that completed in a FAILURE status. Also, when you manually place the last remaining ACTIVATED job on ice, the scheduler did not honor the box's box_success or box_failure conditions of the box. 
The box can evaluate to SUCCESS after you manually place the last remaining ACTIVATED job on ice even when jobs in the box failed or the box_failure condition is satisfied.