Fixed Issues - 11.3.6 SP1

This article details the issues fixed in CA Workload Automation AE Release 11.3.6 SP1.
wcc114sp5p
This article details the issues fixed in CA Workload Automation AE Release 11.3.6 SP1.
Contents
NOTIFY.$AUTOSERV NOT PASSING $2
Problem Number=4229
When the scheduler is shut down, its calls the program specified in the EP_SHUTDOWN entry in $AUTOUSER/notify.$AUTOSERV and passes the following two parameters: an alarm number and a message associated with the alarm. However, only the alarm number was passed but not the message associated with the alarm.
LOGS FOR A DAY MISSING
Problem Number=4036
The scheduler log for a part of or an entire day was lost.
ARCHIVE_EVENTS DOES NOT DELETE MANUAL CHANGE_STATUS DETAILS
Problem Number=4243
When a manual CHANGE_STATUS completion (SUCCESS/FAILUTE/TERMINATED) event is issued to a job, the following problems were noticed:
  1. The archive_events command did not delete the job run information that corresponds to the manual completion events.
  2. The historical reports generated using the autorep -r command reported the job status as RUNNING, ignoring the manual completion events.
SCHEDULER WAITS FOR DBMAINT TO COMPLETE ON A NORMAL SHUTDOWN
Problem Number=4237
When DBMaint was run as part of the scheduler, a graceful shutdown command such as unisrvcntr stop waae_sched.XXX could cause the scheduler to wait indefinitely until DBMaint completes.
APPLICATION SERVER STUCK DURING SHUTDOWN
Problem Number=4238
The application server got stuck while shutting down and continued to receive client requests such as autorep and autoping. Hence, the client requests were timed out and the timed out requests were not reissued to any other application server.
JIL SYNTAX CHECK FAILS ON BOX_NAME > 62 CHARS
Problem Number=4255
The JIL syntax check failed on a box job when the number of characters of the box_name is between 61 and 64. The syntax check passes when the number of characters is less than or equal to 60.
REFRESHAEDB DOES NOT CONTAIN CORRECT INDEX
Problem Number=4253
RefreshAEDB ignored index creation when the index is introduced in lower CA Workload Automation AE version but the same index is applicable for all versions of the product causing unnecessary database errors and sometimes affecting the performance.
Sometimes, the scheduler or application server logs contained unique constraint errors as shown below:
CAUAJM_E_18402 ORA-00001: unique constraint (AEDBADMIN.XPKUJO_REQ_JOB) violated
AUTOTRACKING INFORMATION FOR EXT-CALENDARS
Problem Number=4241
Modifications to extended calendars using autocal_asc did not update auto-tracking information.