Fixed Issues - 11.3.6 INCR1

This article details the issues fixed in CA Workload Automation AE Release 11.3.6 INCR1.
wcc114sp5p
This article details the issues fixed in CA Workload Automation AE Release 11.3.6 INCR1.
Contents
AUCKLAND-Z POSIX VALUE WRONG IN UJO_TIMEZONE TABLE
Problem Number = 3907
The Pacific/Auckland Posix TZ value did not reflect the correct DST change for Australia/Pacific. The jobs running with Auckland-Z time zone were scheduled incorrectly.
SAP JOB INTRODUCES IN PS_ARGS ATTRIBUTE
Problem Number = 3918
The JIL utility escaped the colon (:) character in the ps_args attribute with backslash (\). This resulted in miss interpretation of the attribute. For example, if the ps_args value contains a URL, the link did not work in the browser.
UJO_COMM_SEND_SEQ TABLE HAS INVALID RECORDS
Problem Number = 4060
The application server and scheduler intermittently failed to start due to the unique constraint error from the ujo_comm_send_seq table as the invalid data was not deleted at application server startup.
LOGMAXENDLINES VALUE NOT DISPLAYED ON STARTUP
Problem Number = 4019
The application server log did not display the LogMaxEndLines configuration parameter value at startup.
SUCCESS_CODES/FAIL_CODES ATTRIBUTES NOT DISPLAYED
Problem Number = 4034
If you set the success_codes or fail_codes attribute value to -1 and used the autorep command with the -q option to list the job details, the report did not display the success_codes or fail_codes fields.
JOB TERMINATION EVENTS NOT SENT TO CA7
Problem Number = 4064
If you defined job dependencies between CA7 and CA Workload Automation AE, only the JOBINITU and RUNNING events were sent successfully. The JOBTERMU, SUCCESS, and FAILURE events were not sent to CA7.
SERVER LOGS TIMESTAMP DELAYED BY ONE HOUR
Problem Number = 4089
The scheduler and application server printed timestamps with a delay of one hour; especially after applying the Microsoft August-2013 patch KB2863058 (Windows) or Time zone data 2013 (UNIX) patch for timezones such as Israel, Taipei, and Seoul.
JOB DOES NOT HONOR LOOKBACK '0'
Problem Number = 4113
When you define a job with a look-back dependency of 0 (zero), the scheduler examines the last end time of the condition job and if the condition job has not run since the last run of the job for which the condition is set for, the job should not run. However, the scheduler ignored the look-back dependency of 0 and scheduled the job as if the look-back dependency is not defined when the condition job and scheduled job went into terminal status (such as SUCCESS or FAILURE) in same second.
DEFAULT TIMEZONE FOR ISRAEL WRONG
Problem Number = 3594
The CA Workload Auto