CA Workload Automation ESP Edition

Expand all | Collapse all

questions regarding workstation build 110

  • 1.  questions regarding workstation build 110

    Posted 05-10-2019 11:14 AM

    Hello Forum,
    Looking for some clarification on a couple of questions regarding workstation build 110
    if any have begun using it yet.
    Workstation build 110 is available now for downloading.
    I just installed build 110 for testing, (was on 106 prior), and
    noticed in the notes:
    PRODUCT: CA Workload Automation Workstation EE
    VERSION: 11.3 Build 110

    Fixed in build 110
    Date: April 2, 2019

    1. Fixed the unexpected behavior when custom views
    are sorted in Workload Director.

    PRODUCT: CA Workload Automation Workstation EE
    VERSION: 11.3 Build 109 (withdrawn)

    Fixed in build 109
    Date: December 10, 2018
    .
    .
    5. Workload Director now displays ARGS and CMDNAME
    in Job Details.
    6. Fixed the problem with an excessive number of
    predecessors in simulation.
    .
    .
    Notice that there is just 1 fix listed under 110, while 109 has many, but is
    explicitly described as 'withdrawn'
    Sorry for this dumb question but does that mean, that since 109
    is listed as 'withdrawn', all the fixes listed in these notes under 109 were NOT then
    incorporated in the latest build 110??

    For example 109, fix 5 states it now displays ARGS and CMDNAME however I
    do not see any such when I look at a distributed job's details using 110.

    Also, I've notice, after loading a filter, the status bar on the bottom of each custom screen
    always shows nothing but "Last status update received 0 minutes ago"
    though I can see jobs flowing in and out. Is that '0 minutes ago' because it is updating repeatedly in
    less that 1 minute? (my users are asking if it is not updating properly)

    thanks,



  • 2.  Re: questions regarding workstation build 110

    Broadcom Employee
    Posted 05-10-2019 04:40 PM

    Hi Mike,

     

    The build 110 should include all fixes that were in build 109.

     

    I just tested here, it shows "Last status update received 16 minutes ago". So I tend to agree with your guess, that it shows "0 minutes ago" because there is constantly job status change loaded to the Workstation. 

     

    Hope this helps,

     

    Lucy



  • 3.  Re: questions regarding workstation build 110

    Posted 05-10-2019 04:50 PM

    Hi Lucy,  good to know all the 109 fixes made the 110 grade.

    I would expect as much;

    So where then are these located?: “ Workload Director now displays ARGS and CMDNAME

                        in Job Details.”

     

    For example this sun_job passes 3 args. in the job def.

    Where would I find the ARGS and the CMDNAME (and scriptname hopefully?)

    from Director for this job?

     

    Here is all that is in Details for the job:

     

    Job Name    adpgrids

    Full Name   adpgrids

    Job ID  1591

    Job Type    SJ

    Event Name  WORK.ADP_ADPGRIDS

    Application Name    ADPGRIDS

    Tag ASSETSUITE

    State   FAIL

    Conditions  FAIL,INTVRQ

    Status  "FAILED, CC 20 AT 15.01.55 FR"

    User Status 216844757

    Agent Name  UNIX_T42CCC08Z1

    0 Predecessors  None

    Completion Code CC 20

    Start Time  15.01.31 FRI 10 MAY 2019

    End Time    15.01.55 FRI 10 MAY 2019

    0 Successors    None

    Average Run Time    1



  • 4.  Re: questions regarding workstation build 110

    Broadcom Employee
    Posted 05-10-2019 05:04 PM

    Hi Mike,

     

    They will be at the end of the "Details" for the related job, after "Average Run Time".

     

    I found that both show up for my NT_JOB, and only ARGS show up for my UNIX_JOB. So SCRIPTNAME won't show.

     

    I guess you use SUN_JOB? Could you provide your job definition? 

     

    Thank you,

     

    Lucy



  • 5.  Re: questions regarding workstation build 110

    Posted 05-10-2019 06:01 PM
      |   view attached

    I have nothing at all after Average Run Time, for either nt_job or sun_job

    I checked about a dozen

     

    For example, here are Details for nt_job hcmppin:

     

    Job Name  hcmppin

    Full Name hcmppin

    Job ID    528

    Job Type  NT

    Event Name     WORK.HCM_HCMPPHIN

    Application Name    HCMPPHIN

    State     EXEC

    Status    "Executing at NT_TCCAPPCCC01"

    Agent Name     NT_TCCAPPCCC01

    0 Predecessors None

    Start Time     16.45.01 FRI 10 MAY 2019

    Anticipated End Time     17.38.01 FRI 10 MAY 2019

    0 Successors   None

    Average Run Time    53

     

    Nothing more to scroll down to after Average Run Time.

     

    Is there a particular ptf(s) that needs to be on ESP before these, and possibly some of the other 110 features, would become available?

     

    p.s.  Here is the ‘about ca wa workstation’  , so you see it is build 110:

     

    CA Workload Automation Workstation EE

    Version 11.3, Build 110

     

    Copyright (c) 2009 CA. All rights reserved.

    Warning: This computer program is protected by copyright law and international treaties. Unauthorized reproduction or distribution of this program, or any portion of it, may result in severe civil and criminal penalties, and will be prosecuted to the maximum extent possible under the law.

     

    Restricted Rights: This Product is provided with "Restricted Rights".

    Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable,or their successors.

     

     

     

     

    Michael Bieganski

    Technical Analyst

    Exelon C&I Network, Infra & Cloud Ops -Mainframe

     

    Chase Towers

    10 S. Dearborn, 45th Floor

    Chicago, IL 60603

    Office:779 231-7707

    Michael.Bieganski@exeloncorp.com<mailto:Michael.Bieganski@exeloncorp.com>



  • 6.  Re: questions regarding workstation build 110

    Broadcom Employee
    Posted 05-13-2019 09:35 AM

    Hi Mike,

     

    We can't locate any related ESP PTF for this feature.

     

    Will you open a support ticket? And we would need the Workstation trace to understand better for the possible root cause.

     

    Thank you,

     

    Lucy