Fixed Issues - 11.3.6 SP5 CUM1

This article details the issues fixed in CA Workload Automation AE Release 11.3.6 SP5 CUM1.
wcc114sp5p
This article details the issues fixed in CA Workload Automation AE Release 11.3.6 SP5 CUM1.
MACHINE REPORT DOESNT CALCULATE THE CORRECT CURRENT LOAD
Problem Number: 4525
When you define multiple virtual machines that specify the same machine and their own max load values and then run jobs with loads on those machines, the autorep command machine report displayed incorrect total load on the machine.
SAP JOB COPY JOB DOES NOT HONOR KILLJOB COMMAND
Problem Number: 4527
The scheduler failed to terminate a SAP Job Copy job(SAPJC) when you issue the KILLJOB event.
GLOBAL VARIABLE - ESCAPED SINGLE QUOTE NOT REMOVED
Problem Number: 4533
The global variable value with a single quote gets escaped with two single quotes during global variable creation. While sending the global variable value to the agent, the scheduler should replace two quotes with a single quote, but the scheduler always sends two quotes causing job failures.
DATABASE ERR WHEN SCH PUTS JOB W/ MULTIPLE MACHS IN RESWAIT
Problem Number: 4534
When you start or force start a job with a resource dependency and no load-balancing attributes that specify a comma-separated list of machines or a virtual machine with multiple machine components and no resources are available, the scheduler generated database errors while placing the job in the RESWAIT status.
AUTOSYS_SECURE OPTION 3 CORRUPTS DATABASE PASSWORD
Problem Number: 4535
On Solaris, when you select option 3 from the autosys_secure interactive menu to change the password of the autosys user, the autosys_secure command generated errors and stored a corrupted password in the ujo_alamode database table.
SCH IGNORES AMOUNT WHEN IT FORCESTARTS JOBS SHARING RESOURCE
Problem Number: 4536
When you force start multiple jobs that specify the same virtual resource, the scheduler started the jobs even when no more resources are available.
AS_SERVER SLOWER THAN 11.3 SP1 IN DOING JIL OPERATIONS
Problem Number: 4539
The job or machine insert, update, or delete operation was taking 40 to 50 percent more time when compared with the time it takes with the r11.3 latest maintenance.
AUTOSYSLOG DOES NOT FETCH LOG WHEN STD_OUT_FILE IS INVALID
Problem Number: 4540
When you set the value of the std_out_file attribute to a non-existent path and try to run the job, a non-zero exit code is generated by the agent. This prevents a row to be created in the ujo_job_run table. As a result, the autosyslog command is unable to display the agent log. You cannot fetch the previous run information using the autorep -J j
ob_name
-r
number
command or the job run details using CA WCC.
SCH PROCESSES DUPLICATE STATUSES AFTER PROBLEM 4455