Skip to Content

Transport sequence of Normal Change in CHaRM

Dear Experts,

In our case we have ChaRM – Maintenance cycle configured for three system landscape DEV, QA and PRD.

So when we change Normal Change status to “to be tested” it creates a TOC of released Task and move that TOC to QA. And then Tester test the changes in QA and put Normal Change status to “successfully tested” which releases the main TR from DEV and that TR gets imported to QA. And gets added into production buffer. Then Solman team import change cycle into production as part of Monthly release.

Now I want to put a situation here to understand about normal change sequencing.

Let’s say we have 3 normal changes and respective TOC of those are as mentioned below which moved to QA by putting status “to be tested” in given order.

NC1 – TR1 - TOC1 status was put “to be tested” 1st order

NC2 – TR2 - TOC3 status was put “to be tested” 3rd order

NC3 – TR3 - TOC2 status was put “to be tested” 2nd order

Now whole testing was done in QA based on TOC movement sequence by Tester i.e. NC1,NC3,NC2 order

As tester may be different for different Normal changes so after testing they may put the NC status to successfully tested in any random order lets say NC3,NC2,NC1 order which will release and import main TR in QA in this order only. And TR would get added into production buffer in NC3,NC2,NC1 order. This Order is different from TOC import order in QA which was NC1,NC3,NC2 based on which testing was done.

How to handle this sequencing situation when you have so many Normal changes in a Monthly cycle.. How it can be ensured that TRs gets released in that order only in which their TOCS were moved to QA. We don’t have any control over putting NC status to “successfully tested” by tester.

Regards

G. Sharma

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Aug 15, 2018 at 12:14 PM

    Hi Gagan

    Since you're working with Normal Change, it means your changes will be released into Production using the Tasklist "as a block". It is my understanding that the ChaRM will therefore use the release date on the task to correctly sequence the import (almost like it does a merge of the transport in the background.)

    If however you have a valid reason to interfere in the sequencing, you can configure ChaRM to use selective import (you would then 'tick' the NC's you want to import first, perform the import and repeat the process for the next NC and so on until all the NC's have been imported.I have not had the need to do this - I find ChaRM's sequencing to to good enough.

    Further safeguards can be put in place by activation Downgrade Protection checks.

    Regards, Rob

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 14, 2018 at 11:06 AM

    Hello Rob,

    thanks for your reply and I am sorry being late on this,

    So I really agree with your downgrade protection suggestion this is we plan to implement soon.

    But what you said about my original query -

    " It is my understanding that the ChaRM will therefore use the release date on the task to correctly sequence the import (almost like it does a merge of the transport in the background."

    I have doubt on above statement because normal change TR gets released from DEV when status is changed to successfully tested by tester where we have no control over this.So TR will get added into QA and further production import buffer in the order it which TR got released and not in the order in which tasks got released.as you said..

    Regards

    Gagan Sharma

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 17, 2018 at 04:56 AM

    Hi,

    Soultion Manager uses the release date/time of the TR.

    Your case above would not be possible:

    NC1 – TR1 - TOC1 status was put “to be tested” 1st order - This one is fine

    NC2 – TR2 - TOC3 status was put “to be tested” 3rd order - If TR1 is released you can create TR2 else you would have a read/write lock in the development system.

    NC3 – TR3 - TOC2 status was put “to be tested” 2nd order - Same as for the one above, since TR2 is not released you cannot start development on TR3.

    If you would use Preliminary Import it would be possible to import TR3 before TR2. Preliminary Import works in the same way as Urgent and keeps the TR in the buffer for PROD, this way the sequence would still be correct when you do a Import_all through the task list.

    I would suggest that you get the Down Grade Protection in place as soon as possible :)

    Just send me a message if you need more information on the subject.

    BR,

    Mike

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 26, 2018 at 09:34 AM

    Hello,

    My suggestion would be, try clubbing all the dependent-changes in a Normal Change, since this will give you better control over the sequence.

    Any transports which are dependent to the transports available in another change needs to be taken care manually, and while importing the TRs from the task list, select the NC1 and import this, and then proceed with NC3 and then with NC2. If these three NCs are not having any dependent TRs, this will not be a reason to worry.

    Regards

    Add comment
    10|10000 characters needed characters exceeded