Fixed Issues - 11.3.6 SP2

This article details the issues fixed in CA Workload Automation AE Release 11.3.6 SP2.
wcc114sp5p
This article details the issues fixed in CA Workload Automation AE Release 11.3.6 SP2.
Contents
Global Variable Modification Time Displayed Incorrectly
Problem Number = 4291
Global value modification date was displayed incorrectly using the Java SDK. This impacted CA WCC as it did not match the modified date or times returned by the autorep – G command.
SYBASE DEADLOCK ON UJO_HA_PROCESS FROM UJO_SETNGET_STATUS
Problem Number: 4318
The Sybase server reported numerous deadlock errors on a select query on the ujo_ha_process table that is executed from the CA Workload Automation AE database stored procedure named ujo_setnget_status. This applies to MS-SQL also, but not Oracle.
R11 JOBS STUCK IN STARTING AFTER 2ND TIME SHADOW TOOK OVER
Problem Number: 4317
Jobs that are supposed to start on r11 agents were stuck in the STARTING state after the shadow scheduler took over the second time. This problem did not occur when the shadow scheduler took over for the first time. It occurred only when the primary scheduler was restarted with PrimaryFailbackMode=2 after the shadow scheduler took over for the first time and then the primary scheduler went missing again.
AS_SERVER STUCK IN SQL QUERY DURING STARTUP
Problem Number: 4308
The application server was stuck in a SQL query during startup. The SQL query deleted the invalid records from the ujo_comm_send_seq table.
NO SPECIFIC EXITCODE WHEN ATLEAST ONE AS_SERVER IS DOWN
Problem Number: 4326
When there are multiple application servers, chk_auto_up did not report a specific exit code to differentiate if at least one application server is down versus all application servers are up. It used to work in r11.0. In r11.0, if any one of the application server is down, chk_auto_up returns an exit code of 0 whereas in r11.3 and above, it returns an exit code of 100 if all the application servers are up.
SEND_NOTIICATION NOT SHOWN IN THE JOB DEFINITION REPORT
Problem Number: 4332
When you define a job, if you specify the notification_emailaddress attribute and the send_notification attribute is set to 0, the job definition report (for example, autorep -q) did not display send_notification=0.
MUST START/MUST COMPLETE ALARMS NOT GENERTAED UPON OVERRIDE
Problem Number: 4300
When the must_start_times or must_complete_times attribute is overridden, the CHK_START and CHK_COMPLETE events were not generated. This caused the job not to generate the MUST_START_ALARM or MUST_CONMPLETE_ALARM alarm.
 If you are overriding the start_times attribute of a job and your job definition includes the must_start_times or must_complete_times attribute, ensure that the start_times value is earlier than the must_start_times or must_complete_times value to avoid a false MUST_START_ALARM alarm; until  overrides are supported for the must_start_times and must_complete_times attributes.
GAPS