[Transcript] APAC Office Hours for CA Workload Automation Autosys Edition [Wednesday, 16 November 2016 | 2:30PM ~ 3:30PM AEDT (UTC +11)]

Document created by Chandru_V Employee on Nov 16, 2016
Version 1Show Document
  • View in full screen mode

  Chandrasekaran Venkataraman to Everyone:    Hello everyone, Welcome to this edition of CA Workload Automation AE (AP) Office Hours! We will get started in a moment...
  Chandrasekaran Venkataraman to Everyone:    Hello Blaise - Thanks for joining!
  Chandrasekaran Venkataraman to Everyone:    Hi Raymond - Good afternoon!
  Chandrasekaran Venkataraman to Everyone:    Hello Greg - Welcome!
  Chandrasekaran Venkataraman to Everyone:    Hi Jamie
  Blaise to Everyone:    Hi Chandru, Jamie is logging as well , Hi Raymond
  Raymond Ho to Everyone:    Hi Chandru
  Raymond Ho to Everyone:    Hello Blaise & Greg
  Ahmed Khan to Everyone:    Hi Everyone
  Greg Bradley to Everyone:    no sound here?
  Greg Bradley to Everyone:    I see it
  Greg Bradley to Everyone:    sorry
  Chandrasekaran Venkataraman to Everyone:    @Greg: No audio. Chat-only sessions.
  Chandrasekaran Venkataraman to Everyone:    Okay...let us get started. If you have any questions or topic for discussion, please bring them on.
  Ahmed Khan to Everyone:    Let me start
  Jamie to Everyone:    hi guys
  Ahmed Khan to Everyone:    We had a situation where a job was stuck in ST for 5 mins
  Ahmed Khan to Everyone:    I looked at the event_demon and app_server log, nothing userful
  Ahmed Khan to Everyone:    By the time I went to look at agent logs, they were over written
  Ahmed Khan to Everyone:    Its a unix machine
  Ahmed Khan to Everyone:    sar output was ok
  Ahmed Khan to Everyone:    Is there anything else that I can look into
  Chandrasekaran Venkataraman to Everyone:    @Ahmed - Job stuck in starting could mean that the Agent could not send the status back to the Scheduler. The Agent transmitter*.log usually contains indication as to why the Agent could not connect to the SCheduler.
  Raymond Ho to Everyone:    @Ahmed - have you take a look at the unix agent log?
  Ahmed Khan to Everyone:    They have been over written
  Blaise to Everyone:    @Ahmed , can you describe what the job was doing ? , what is "ST" ?
  Ahmed Khan to Everyone:    yes ST
  Chandrasekaran Venkataraman to Everyone:    @Ahmed - Logs get overwritten when the Agent is restarted. The previous log is archived.
  Chandrasekaran Venkataraman to Everyone:    @Ahmed - Please check the transmitter_queue_spool_ace_sch*
  Chandrasekaran Venkataraman to Everyone:    @Ahmed - "ace" refers to the $AUTOSERV in the previous example.
  Ahmed Khan to Everyone:    log.level=5
log.archive=1
log.maxsize=1M
  Avinash Panicker to Everyone:    @Blaise - ST is "STARTING" Status
  Ahmed Khan to Everyone:    We have a current file say X
  Ahmed Khan to Everyone:    Then we have X.archive.log
  Reginold D Almeida to Everyone:    @Ahmed There are multiple logs which refer to the job. So it is possible that some logs are not overwritten. We can also check the spool files created. The joblog is in the spool location
  Ahmed Khan to Everyone:    The activity on the agent is huge, and the log gets overwritten every 5 mins
  Ahmed Khan to Everyone:    The job logs is removed when the Job is SUCCESS
  Ahmed Khan to Everyone:    May be we should increase the log.maxsize=1000M to store 24 hours data
  Chandrasekaran Venkataraman to Everyone:    @Ahmed - The "transmitter_queue_spool_AUTOSERV_sch*.log" file may have a clue. If none obvious, please raise a Case with CA Support and we will investigate.
  Ahmed Khan to Everyone:    Not sure if that size will be possible
  Ahmed Khan to Everyone:    @Chandru - transmitter_queue_spool_pr1_sch.log just has 5mins data in current log and 5 mins data in archive.log
  Ahmed Khan to Everyone:    Problem happened at 0800 hours
  Ahmed Khan to Everyone:    When I looked at 1000 hours , 0800 was already overwritten
  Ahmed Khan to Everyone:    Lets proceed to next question. If CA has anything else they can contact me directly.
  Chandrasekaran Venkataraman to Everyone:    @Ahmed: How about spool logs. Each run has its corresponding log created. If the job completed successfully,, then the spool log is removed. However, the agent did not communicate the status (RU, SU) back to the Scheduler.
  Ahmed Khan to Everyone:    The job was in ST for 5 mins
  Ahmed Khan to Everyone:    Then came RU and SU
  Ahmed Khan to Everyone:    $ jr JobName -d -r 46079611
Job Name                                                         Last Start           Last End             ST Run/Ntry Pri/Xit
________________________________________________________________ ____________________ ____________________ __ ________ _______
JobName                     11/15/2016 08:15:24  11/15/2016 08:15:26  SU 46079611/1 0
  Status/[Event]  Time                 Ntry ES  ProcessTime           Machine
  --------------  --------------------- --  --  --------------------- ----------------------------------------
  STARTING        11/15/2016 08:08:05    1  PD  11/15/2016 08:08:05   xxxxxxxx
  RUNNING         11/15/2016 08:15:24    1  PD  11/15/2016 08:15:25   xxxxxxxx
    <Executing at xxxxxxxx>
  SUCCESS         11/15/2016 08:15:26    1  PD  11/15/2016 08:15:27   xxxxxxxx
  [JOB_ON_HOLD]   11/15/2016

 

  Chandrasekaran Venkataraman to Everyone:    @Ahmed - A friendly reminder that there are other customers and possibly non-customers in thie forum as well, it is wise not to share hostnames, IP,, etc
  Chandrasekaran Venkataraman to Everyone:    @Ahmed - Please raise a Case and we'll investigate.
  Chandrasekaran Venkataraman to Everyone:    @Everyone - Any other queries, please.
  Chandrasekaran Venkataraman to Everyone:    @Everyone: A friendly reminder to customers to periodically review CA Workload Automation Support Lifecycle Dates and associated policies.
http://www.ca.com/us/support/ca-support-online/product-content/status/support-life-cycle/indexes/ca-workload-automation-release-and-support-lifecycle-dates.aspx
  Ahmed Khan to Everyone:    We have applications using multiple commands in one jil job, any documentation against the practice please...
  Ahmed Khan to Everyone:    Example: sleep 5; ls -lrt
  Ahmed Khan to Everyone:    Example: "command: sleep 5; ls -lrt"
 Chandrasekaran Venkataraman to Everyone:    @Ahmed: WAAE does support command-chaining. However, the caveat is this, the Agent will only capture the exit/return code from the last ccomman in the chain. So, if there are 4 commands chained. Ex: "sleep 5; /bin/false; /bin/false; /bin/true", the job will go to SUCCESS, even though the "false" commands return with code 1.
  Chandrasekaran Venkataraman to Everyone:    @Ahmed: To support chained commands (commands separated by a semicolon) on UNIX, ensure that the oscomponent.wrapper.exec.force parameter in the agentparm.txt file is set to false (the default).
  Ahmed Khan to Everyone:    Agree, do we have any documentation which discourages this practice
  Chandrasekaran Venkataraman to Everyone:    @Blaise: Any questions or experience you'd like to share?
  Blaise to Everyone:    no, I am very interested in command line syntax, autorep, sendevent and jil syntax, but so far I have been able to write scripts to do the work I need to do
  Chandrasekaran Venkataraman to Everyone:    @Ahmed: Will search and see if we have any official word against command-chaining. WAAE DocOps says this "To support chained commands (commands separated by a semicolon) on UNIX, ensure that the oscomponent.wrapper.exec.force parameter in the agentparm.txt file is set to false (the default). ". https://docops.ca.com/ca-wla-ae-wcc/11-4-2/en/scheduling/ae-scheduling/command-jobs-overview/define-a-command-job
  Ahmed Khan to Everyone:    When was this parameter introduced?
  Ahmed Khan to Everyone:    I do not have this parameter in my agentparm.txt
  Ahmed Khan to Everyone:    does it mean we are running with default (false) ?
  Chandrasekaran Venkataraman to Everyone:    @Ahmed: Another, "gotcha".  KILLJOB may not work when multiple (chaining) commands are used.
  Ahmed Khan to Everyone:    Yup agree
  Ahmed Khan to Everyone:    does it mean we are running with default (false) ?
  Chandrasekaran Venkataraman to Everyone:    @Ahmed: "oscomponent.wrapper.exec.force" was introduced with CA WA Agent 11.3 SP1 Cum4.
  Chandrasekaran Venkataraman to Everyone:    @Ahmed: Yes, default for "oscomponent.wrapper.exec.force" is fale. As a result, you can specify chained
commands in a job, for example, bin/sleep 10; echo hello
  Chandrasekaran Venkataraman to Everyone:    @Ahmed: Typo there. False.
  Chandrasekaran Venkataraman to Everyone:    @Everyone: Okay, we will wrap up in 5 minutes if no further questions.
  Greg Bradley to Everyone:    so then question is
  Greg Bradley to Everyone:    if we do not have the parm coded - is it still enforced hardcoded in the product
  Greg Bradley to Everyone:    ?
  Chandrasekaran Venkataraman to Everyone:    @Everyone: Please bookmark this URL for WAAE KBs. http://www.ca.com/us/services-support/ca-support/ca-support-online/support-by-product/ca-workload-automation-ae.html?d=t&language=en&type=ALL&sortby=daten&page=1&typeofcontent=Knowledge%20Base%20Articles. We are improving and adding more KBs regularly.
  Greg Bradley to Everyone:    as we are r11.3.6 sp4
  Greg Bradley to Everyone:    @chandru - am I too late to ask that question ?
  Chandrasekaran Venkataraman to Everyone:    @Greg: Checking on the info....
  Chandrasekaran Venkataraman to Everyone:    @Greg: If the parm is NOT coded, the value is false.
  Chandrasekaran Venkataraman to Everyone:    @Greg: We need to check and confirm whether the AutoSys installer sets this parm up (either false or true) by default.
  Chandrasekaran Venkataraman to Everyone:    @Greg: We will get back.
  Greg Bradley to Everyone:    @Chandru - thank you
  Chandrasekaran Venkataraman to Everyone:    @Eveyone: We'll wrap up. Thank you for joining! We will post the transcript on the CA Workload Automation Communities page.
  Ahmed Khan to Everyone:    Thanks Chandru
  Ahmed Khan to Everyone:    Bye
  Ahmed Khan to Everyone:    Bye everyone

Attachments

    Outcomes