Endevor

 View Only

  • 1.  BYPASS ELEMENT DELETE

    Posted Sep 25, 2015 01:12 PM

    Hi, We had a situation where a few elements needed to be removed from package 1 before package 1 was shipped to production by Endevor Ship.  Package 1 had BYPASS ELEMENT DELETE in the MOVE SCL, so the source and outputs were still on the source stage.  In order to remove the bad elements from package 1, we reset package 1 and built package 2 without the bad elements.  Package # 2 executed and didn't do any source management or process management.  No backout information was created.  So package 2 couldn't be shipped.  Has anyone encountered this?  Any options for getting package 2 shipped?  Thanks, Phil



  • 2.  Re: BYPASS ELEMENT DELETE
    Best Answer

    Posted Sep 28, 2015 02:50 PM

    Hi Phil,

     

    If there are no back out members associated to a Package , it can not be shipped.

     

    Tim O'Neill



  • 3.  Re: BYPASS ELEMENT DELETE

    Posted Sep 30, 2015 10:38 AM

    Thanks Tim.  I was hoping for some way to force the ship of package 2.  We talked about this at our EUNE meeting yesterday - no way to force.



  • 4.  Re: BYPASS ELEMENT DELETE

    Broadcom Employee
    Posted Sep 29, 2015 06:51 AM

    Hi Phil,

     

    I agree with Tim and would know if the 2nd Package execution completed with RC 04 and messages below have been issued ?

    C1G0023W  NO CHANGES DETECTED - SOURCE MANAGEMENT MAY HAVE ALREADY BEEN PERFORMED FOR THIS ACTION

    C1G0333W  PROCESS MANAGEMENT HAS ALREADY BEEN PERFORMED FOR THIS ELEMENT  

    In such a case, no backout are created by package.                    

     

    Regards,

    Ollivier



  • 5.  Re: BYPASS ELEMENT DELETE

    Posted Sep 30, 2015 09:35 AM

    yes Ollivier, we did receive the messages you described.  I hope this post makes people aware that in the scenario I describe, package # 2 cannot be shipped.  Thanks!



  • 6.  Re: BYPASS ELEMENT DELETE

    Broadcom Employee
    Posted Oct 01, 2015 04:39 AM

    Hi Philip,

     

    If you want to force package 2 creating backout member, you should have generated(again) before elements moved by this package.

     

    Regards,

    Ollivier



  • 7.  Re: BYPASS ELEMENT DELETE

    Posted Oct 01, 2015 05:03 AM

    Hi,

     

    isn't there an option "Do the process management no matter if changes are detected!"?

    Have a look at BYPASS_C1G0333W= at your ENCOPTBL!

    Maybe this could help more generally!

     

    Regards,

    Willi



  • 8.  Re: BYPASS ELEMENT DELETE

    Posted Oct 01, 2015 11:11 AM

    Thanks Willi -  I'll give this a test.  I also just received this note from Marc Hanna

     

     

    I don’t know if this was your issue, but it sounded similar to what I encountered a couple years ago. I got around it by activating this feature in a temporary version on ENCOPTBL I used just to complete my package processing.

     

     

     

    ***********************************************************************

     

    * OC00512

     

    * WHEN A MOVE ACTION IS RESTARTED OR RE-EXECUTED AND PROCESSOR        

     

    * MANAGEMENT DETERMINES THAT THE TARGET PROCESSOR HAS ALREADY BEEN    

     

    * EXECUTED PREVIOUSLY, MESSAGE C1G0333W WILL BE ISSUED AND TARGET     

     

    * PROCESSOR EXECUTION IS SKIPPED.

     

    * IF THIS OPTIONAL FEATURE IS ON, MESSAGE C1G0333W IS BYPASSED AND    

     

    * THE TARGET PROCESSOR IS EXECUTED ANYWAY. THIS OPTION, HOWEVER,      

     

    * DOES NOT TAKE EFFECT IF THE PREVIOUS MOVE ACTION FAILED ON A DELETE 

     

    * PROCESSOR. IN SUCH A CASE, C1G0333W IS ISSUED AS NORMAL AND ONLY    

     

    * THE DELETE PROCESSOR IS RESTARTED.

     

    *

     

    *---------------------------------------------------------------------*

     

    *        ENHOPT BYPASS_C1G0333W=ON

     

    *

      ***********************************************************************