Clarity

  • 1.  Upgrading is cancelling all jobs???

    Posted Dec 09, 2015 11:22 AM

    We're upgrading from 13.3 to 14.2.  So far, I've upgraded both the Development and QC environments, and in both cases almost all (but not *quite* all) of my recurring jobs have been marked "Cancelled" after the upgrade.  I did Pause all jobs before starting the upgrade.  Since I can't "un-cancel" them, this means I have to recreate 50+ jobs, which is a pain.  Why are my Paused Jobs getting Cancelled by the upgrade?  Is there anything I can do to stop that from happening when we upgrade Production?



  • 2.  Re: Upgrading is cancelling all jobs???

    Posted Dec 09, 2015 11:35 AM

    Sounds like the problem discussed here ; Saved filters being deleted during upgrade to 14.2

     

    (I am not personally familiar with the ins and outs of this, I just recalled the discussion - you should read through those links though!)



  • 3.  Re: Upgrading is cancelling all jobs???

    Broadcom Employee
    Posted Dec 09, 2015 11:53 AM

    Hi Dave,

     

    This is not exactly the issue that Allison is facing, but it's a very good point, provided she is upgrading to 14.2.

    Allison.nichols please feel free to check the links up: This would definitely be something you want to apply as workaround in Production to avoid losing any Saved User Filters.

     

    Kind Regards

     

    Nika Hadzhikidi

    CA Technologies

    Principal Support Engineer



  • 4.  Re: Upgrading is cancelling all jobs???

    Posted Dec 09, 2015 11:56 AM

    Fair enough - only the discussions around that thing I linked to do explicitly mention saved job parameters, not just filters.

     

    (but as I said, I don't know the detail! )



  • 5.  Re: Upgrading is cancelling all jobs???

    Broadcom Employee
    Posted Dec 09, 2015 11:50 AM

    Hi Allison

     

    The upgrade should not change your job status. In fact, all Paused jobs should have been kept as Paused. Are only the Paused jobs the ones that moved to Cancelled?

     

    There are few things you may do:
    As a workaround, you may think of xogging out the jobs out prior to upgrade, then xog them back. This will avoid you from having to reschedule manually. In fact for your current environment you may do the same:
    Xog them out and then you should be able to xog them in as new job definitions with the same parameters. This should help to avoid you the manual work.

     

    Also please raise a ticket with us at CA Support and provide your database copy, we will test this out and see if we can reproduce the issue and log it.

     

    Hope this helps

     

    Kind Regards

    Nika Hadzhikidi
    CA Technologies
    Principal Support Engineer



  • 6.  Re: Upgrading is cancelling all jobs???

    Posted Dec 09, 2015 02:32 PM

    We saw this as well. I observed in our environments all Scheduled Execute a Process jobs were Cancelled after our upgrade (could have happened during or after. We're in Dev & Test awaiting the go to Prod). There is a new checkbox on Execute a Process jobs called 'Allow only one running instance' - I assumed it was something around this change.



  • 7.  Re: Upgrading is cancelling all jobs???

    Posted Dec 09, 2015 03:20 PM

    We have noticed same. Only 'Execute a Process' jobs are cancelled. And primarily due to change in Job definition. I think, there may not be a fix. Just that we need to re-schedule them again.



  • 8.  Re: Upgrading is cancelling all jobs???
    Best Answer

    Posted Dec 09, 2015 04:43 PM

    Nika_Hadzhikidi and I were looking further into this, and would agree with the follow-ups.  This specific job definition type has its schedules cancelled as the upgrade passes through version 14.1, and this would also happen to any job definition that you update via XOG, which is how the change was applied:

     

    https://docops.ca.com/ca-ppm/14-3/reference/xml-open-gateway-xog-development/xog-object-reference/content-pack

     

    Jobs and reports definitions

    During import, the imported attributes of the definition match the user interface exactly. When parameters are changed, the old parameters are deleted and new ones are added. Existing scheduled jobs and reports are canceled, because the parameters no longer exist. All saved parameters are deleted. If the update flag is set to True, then only captions (job and parameters) can be changed. If the update flag is set to False, the content item is assumed to contain all the parameters and existing parameters are deleted as described above.

     

    These items will need to be rescheduled as a result.  We will report this so the documentation can be updated to include this regarding the added parameter and the existing schedules (for example in the Change and Impact guide and section).

     

    #clrt-72091



  • 9.  Re: Upgrading is cancelling all jobs???

    Posted Dec 09, 2015 05:28 PM

    FWIW I find documenting in the Change and Impact Guide that these will be cancelled and the system administrator will need to reschedule them manually to be an acceptable solution. The cancelled jobs remain so no data is lost (I believe).

    Knowing that this is going to happen and I'm going to have to reschedule these is easy. The surprise of discovering this is what brings frowns. I have 'reschedule 32 cancelled jobs' as a line item of my upgrade process - I'll have this done in under an hour and will move on with life. There are plenty of bigger end-user facing issues and ideas I'd rather smart people put development effort into.

     

    Thanks for digging into this - but IMHO don't put too many calories into work-arounds.