What are the different patch numbers for Autosys 11.3.6 SP7 CUM1

Document ID : KB000115644
Last Modified Date : 24/09/2018
Show Technical Document Details
Question:
What are the different patch numbers for Autosys 11.3.6 SP7 CUM1 and what do they fix?
Environment:

CA WAAE 11.3.6 SP7 CUM1 on any platform
Answer:

Patch numbers for Autosys 11.3.6 SP7 CUM1 and their related test fixes are:


 
SO05574T43B6684740NOPrereq: NAWindows 
 
SO05571T43B6674740NO 
Prereq: NA
LINUX 
 
SO05575T42B3584740NO
Prereq: NA
AIX 
 
SO05576T42B3594740NO
Prereq: NA
HP-UX 
 
SO05577T5Q81244740NOPrereq: NASolaris Sparc 
 
SO05578T5Q81254740NOPrereq: NASOLAR-x86 
 
Additional Information:
Problems fixed are:
 
PROBLEM DESCRIPTION: LNX-CA WORKLOAD AUTOMATION AE 11.3.6 SP7 CUM1
                     ----------------------------------------------------
                 Notes:
                 - This patch applies only to CA Workload
                 Automation AE release 11.3.6 SP7.
                 - This patch is applicable to machines where
                 the server or client is installed.
                 - This patch need not be applied on CA WCC or
                 agent only machines.
 
                 ==========================================
                 The following problems are fixed in this
                 cumulative
                 ==========================================
 
                 1.APPSERVER/SCH STUCK IN SQL QUERY DURING STARTUP
                 AFTER PR4308.
 
                 When you start up the application server or
                 scheduler after communicating with many agents,
                 the process experienced long delays while
                 executing a SQL query that validates the rows in
                 the communication tables.
 
                 Problem Number: 4697
 
                 2.FORECAST REPORT GENERATION FAILS FROM WCC
 
                 CA Workload Control Center fails to generate the
                 CA Workload Automation AE forecast report when a
                 job depends on a job that runs more than a day
                 every time it runs. CA Workload Control Center
                 validates the date and time for every job and
                 reports an error when the job duration is more
                 than 24 hours.
 
                 Problem Number: 4698
 
                 3.IMPROVE ACCURACY OF IP ADDRESSES SHOWN IN
                 ISDBGACTIV TRACES
 
                 When you run the CA Workload Automation AE
                 product binaries on a machine that supports both
                 IPv4 and IPv6 address resolution and you enable
                 ISDBGACTIV=COMM,LIGHT traces, the traces  were
                 ambiguous about the display of the IPv4 or IPv6
                 address.
 
                 Problem Number: 4701
 
                 4.CROSS INSTANCE DEPENDENCY BETWEEN 11.3.6 & 4.5
                 FAILS
 
                 When a predecessor job of type BOX is defined in
                 CA Workload Automation AE Release 11.3.6 and the
                 successor job resides in 4.5, the successor job
                 did not start when the predecessor job that is in
                 the NO_EXEC status is started.
 
                 The following message is displayed in the Release
                 11.3.6 scheduler log:
                 CAUAJM_W_40284 Postponing send of event
                 <ACE00G318g00>
                 due to offline external instance <R45>.
 
                 Problem Number: 4705
 
                 5.SETTING TIMEOUT TO EMAIL NOTIFICATION
 
                 Email notification feature sometimes gets stuck
                 in sending emails for almost five (5) mins
                 without sending other emails. This fix will allow
                 user to specify a timeout in cases where SMTP
                 server becomes unresponsive and try the email
                 notification for next job. Use
                 ASNOTIFY_SMTP_TIMEOUT environment variable to
                 specify the timeout in seconds.
 
                 If ASNOTIFY_SMTP_TIMEOUT=20 then email
                 notification
                 will return timeout after 20 seconds when the
                 SMPT server becomes unresponsive.
 
                 Problem Number: 4707
 
                 6.JOB STUCK IN STARTING AFTER FIRST COMMUNICATION
                  WITH AGENT
 
                 When the scheduler schedules a job to a remote
                 machine and contacts the agent for the first
                 time, it initiates an exchange to introduce
                 itself to the agent. After the exchange
                 completes, the scheduler placed the job in the
                 STARTING status but the agent did not execute the
                 job.
 
                 Problem Number: 4708
 
                 7.AUTOREP -J -Q DISPLAY BLANK OR GARBAGE DATA
 
                 autorep -J -q ALL prints blank or garbage data
                 when jobs are inserted and deleted while running
                 autorep.
 
                 Problem Number: 4709
 
                 8. SAP PLUGIN RECEIVER OBJECT COULD NOT BE CREATED
 
                 When the sap_recipients attribute of the SAP
                 job_type contains a space in the recipient part
                 of the value, the agent returns the following
                 message to the Scheduler:
 
                 "<JobName> function failed. R/3 Code: Receiver
                 object could not be created.
 
                 Problem Number: 4711
 
                 9.EXT CAL DATE_CONDITION #E AND #O OPTIONS
 
                 You must add every EVEN or ODD week of the year
                 to an extended calendar date_condition field,
                 however field length is limited to 255 characters.
 
                 Problem Number: 4713
 
                 10.DBMAINT FAILS WHEN DBMAINTCMD VALUE INCLUDES
                 AN ENVIRONMENT VARIABLE WITH SPACES
 
                 CA Workload Automation Scheduler fails to run the
                 database maintenance activity on Windows machine
                 when the product is installed on a drive that does
                 not support 8dot3name file naming convention and
                 the DBMaintCmd variable has an environment
                 variable
                 with spaces in the value of the environment
                 variable.
 
                 Problem Number: 4714
 
                 11.DATABASE ERROR IN  UJO_GET_PREDS_AND_SUCCS
                 STORED PROCEDURE
 
                 When you try to edit a job using the Quick Edit
                 tab in the CA WCC, the job details are not
                 populated, and the page remains blank. This
                 problem occurs when the CA Workload Automation AE
                 is running on MSSQL or SYBASE databases.
 
                 Problem Number: 4715
 
                 12.INFORMATICA JOB INSERT FAILS WHEN YOU  DEFINE
                 SECURITY DOMAIN
 
                 When you define an INFORMATICA-type job and
                 specify a value for the
                 informatica_security_domain JIL attribute, the
                 application server fails the job insert operation.
 
                 Problem Number: 4718
 
                 13.HANDLING ESCAPED SINGLE/DOUBLE QUOTES OF STRING
 
                 When the POJO job uses string with escaped double
                 quotes as part of the input for j2ee_parameter,
                 those string values are truncated in parsing,
                 which results in incorrect AFM formation.
 
                 Problem Number: 4719
 
                 14.FAILED TO UPDATE CONFIG DURING DATABASE
                 ROLLOVER
 
                 In dual server mode, the scheduler fails to
                 rename the configuration file
                 $AUTOUSER/config.$AUTOSERV,
                 while attempting to rollover to single server
                 mode.
 
                 Problem Number: 4720
 
                 15.SHADOW IN BAD STATE AFTER RESTARTING WHILE
                 AGENTPOLLER EXECS
 
                 When the primary scheduler fails back after the
                 shadow scheduler took over processing jobs, the
                 shadow scheduler stops processing jobs and
                 restarts in dormant mode without exiting the
                 process. When the shadow scheduler restart takes
                 place while the 11.3.6 SP7 agent poller feature
                 is in progress and the shadow fails over a second
                 time following the loss of the primary scheduler,
                 the shadow sets the status of some of the
                 machines to the unqualified status. When the
                 primary fails back again, the shadow scheduler
                 deadlocks while trying to restart without exiting
                 the process.
 
                 Problem Number: 4723
 
                 16.SCHEDULER DEADLOCKS WITH ISDBGACTIV  WHEN
                 GETADDRINFO DELAYS
 
                 When you have enabled ISDBGACTIV=LIGHT traces for
                 the UNIX scheduler and the scheduler's attempts
                 to resolve the agent's node name into an IP
                 address delay, the scheduler process deadlocks
                 and hangs indefinitely.
 
                 Problem Number: 4726
 
                 17.JOBS STUCK WHEN PRIMARY AND SHADOW  SCHEDS RUN
                 AT SAME TIME
 
                 When you configure CA Workload Automation AE
                 instance to run in high availability mode and you
                 manually restart the primary scheduler following
                 an ungraceful exit, while the shadow scheduler
                 begins to take over, both schedulers
                 run simultaneously for a moment. During this
                 time, both schedulers compete for job events
                 stealing events from the other resulting in jobs
                 getting stuck in the wrong status.
 
                 Problem Number: 4727
 
                 18.UPGRADE OF AGGREGATOR TABLES TO 11.3.6 SP6
                 TAKES A LONG TIME
 
                 When you upgrade your CA Workload Automation AE
                 instance to Release 11.3.6 SP6 and the tables
                 that are associated with the aggregation of
                 statistics have many rows, the installer
                 completes after many minutes.
 
                 Problem Number: 4728
 
                 19.UNDER NATIVE SECURITY NON OWNER COULD NOT
                 EXECUTE SENDEVENT
 
                 When you are not a job owner and have job execute
                 permissions, you cannot execute sendevent command
                 in native security mode.
 
                 Problem Number: 4729
 
                 20.SCHED HANGS WHEN RUNNING LOAD BALANCING JOBS
                 AFTER PR4606
 
                 When you define a box that contains many load
                 balancing jobs, and the jobs in the box specify a
                 dependency on one another and the scheduler
                 schedules most of the jobs for execution, the
                 scheduler process hung while it processed the
                 incoming completion events for the jobs.
 
                 Problem Number: 4730
 
                 21.CCI COMMUNICATION DELAY WHEN MANAGERHOSTALIAS
                 IS FQDN
 
                 When ManagerHostAlias is defined with fully
                 qualified domain name, then the CA Workload
                 Automation AE scheduler sends all messages over
                 cross-platform using fully qualified domain name
                 and mainframe takes almost 40 seconds more to
                 resolve the hostname when compared to node name
                 without FQDN.
 
                 Problem Number: 4731
 
                 22.ORACLE DATABASE QUERY PERFORMANCE DEGRADES
                 AFTER PR4688
 
                 This problem addresses the following issues that
                 are related to the performance of the database
                 queries: When you define many jobs that specify
                 the must_start, must_complete, max_run_alarm, and
                 term_run_time  attributes, and the scheduler
                 schedules the jobs, it delayed while it processed
                 the incoming completion events for the jobs.
 
                 Problem Number: 4732
 
                 23.SCHEDULER DID NOT RETRY UPON
                 UJO_BATCH_GET_EVENT DB ERRORS
 
                 The scheduler executes database stored procedure
                 ujo_batch_pkg.ujo_batch_get_event twice every
                 second to get the events from the database. When
                 there is a failover from Oracle datagaurd,
                 execution of this stored procedure is considered
                 as success even though there is a database error.
 
                 Problem Number: 4733
 
                 24. QUERY FOR GET_JOB_RUNS_WITH_FILTER TIMED OUT
 
                 When you create filters to view jobs in the CA
                 Workload Command Center (CA WCC) and the
                 application server executes a query on behalf of
                 CA WCC, the query gets timed out because oracle
                 server takes more time in parsing.
 
                 Problem Number: 4734
 
                 25.ENABLE DEBUG FOR SIMPLE EMAIL NOTIFICATION
 
                 Problem Number: 4736
 
                 When VERBOSE option is enabled for simple email
                 feature in CA Workload Automation AE, the debug
                 output is written to the end of the file and
                 after the scheduler is stopped gracefully. Debug
                 information is useful when the verbose
                 information is written to the log file
                 immediately after the event occurs.
 
                 26.AVOID SENDING EMAILS WHEN AN EMAIL IS  WRONG
 
                 Problem Number: 4737
 
                 In CA Workload Automation AE, the scheduler does
                 not send emails to all the addresses when one of
                 the address that is specified as part of the job
                 definition is wrong. Some SMTP servers are strict
                 in checking the email addresses and will block
                 the email sending attempts.
 
                 27.FILE TRIGGER DELETE/EXIST/NOTEXIST OPERATIONS
                 NOT WORKING
 
                 When a file trigger job is created (job_type: FT)
                 for watch_file_type: DELETE or EXIST or NOTEXIST,
                 then "watch_no_change: 1" is added by default and
                 the job fails. The following messages are
                 displayed:
                 Invalid format, "No Change does not make sense
                 here"
                 or
                 File does not Exist.
 
                 Problem Number: 4739
 
                 28.SCHED HANGS WHEN RUNNING LOAD BALANCING JOBS
                 AFTER PR4730
 
                 When you define many load balancing jobs that
                 specify multiple dependencies on one another and
                 the scheduler schedules most of the jobs for
                 execution while queuing other jobs, the scheduler
                 process hung while it processed the incoming
                 completion events for the jobs.
 
                 Problem Number: 4740
 
                 29.AUTOREP -J % COMMAND TAKES LONGER TIME TO
                 EXECUTE
 
                 The autorep -j ALL command fetches all the job
                 runs and displays the results faster than the
                 autorep -j % command.
 
                 Problem Number: 4742
 
                 30.DUAL DATABASE EVENT SYNCHRONIZATION DEADLOCK
                 AFTER PR4603
 
                 When you configure the CA Workload Automation AE
                 instance to run in dual event server mode and the
                 scheduler is busy processing hundreds of events
                 at one time, the scheduler was unable to
                 synchronize events between both databases and
                 shut itself down.
 
                 Problem Number: 4743
 
                 31.RESOURCES ARE NOT HONORED WHEN BOX JOBS ARE
                 FORCE STARTED
 
                 When multiple box jobs are force started and are
                 waiting on resources, the scheduler does not
                 honor resources.
 
                 Problem Number: 4745
 
                 32.AUTOREP -J -Q RETURNS J2EE_PARAMETER VALUES IN
                 REVERSE ORDER
 
                 autorep -j -q returns j2ee_parameter values in
                 reverse order because of Standard Template
                 Library (STL) sort.
 
                 Problem Number: 4747
 
                 33.IMPROVE RATE OF LOAD BALANCE JOB STARTS
                 DURING HIGH ACTIVITY
 
                 When the scheduler must start many load balancing
                 jobs at once, it reduced the number of job start
                 evaluations to one or two jobs starts per second
 
                 Problem Number: 4749
 
                 34.SCHEDULER FAILED TO CREATE SERVICEDESK/SERVICE
                 NOW TICKETS
 
                 The scheduler failed to create
                 servicedesk/service now tickets intermittently.
                 This problem is resolved with gsoap 2.8.55
                 library.
 
                 Problem Number: 4754