Automatic reordering of Actions for one element in a single SCL

[Jean-Christophe GUILLEMIN]

Bonjour
Does anyone knows if there is an automatic order applied to actions for a unique element in a single SCL file? For example when the following sequence is defined in the SCL : 1/ TRANSFER element X, 2/DELETE element X (2 actions for 1 single element). When running the SCL in batch mode the action sequence is automatically changed as follows : 1/ DELETE 2/TRANSFER
Is there a general rule regarding the automatic sequence of actions when multiple actions are selected for one element in a single SCL command file? If yes, can this rule be manually updated somewhere in Endevor parameters?
Thanks for your support
Rgds
Jean-Christophe​

[Phontilla Shuffitt]

My question is why have two different actions, when you can issue the TRANSFER action with a DELETE 'FROM' Element, which will do what you want.  But I do not know of any customization that you can make to force one action before another. 

Phon

------------------------------
Software Engineer
Enterprise Technology
Fiserv
Ky, USA
------------------------------

[Jean-Christophe GUILLEMIN]

Bonjour Phon
Thanks a lot for your feedback. I agree with you it should have been better to Transfer the element with the Delete From option​. Becasue this was not the case I discovered this issue where you enter multiple Actions for 1 single element in a SCL file, and when Endevor is executing those actions they are automatically reorder.
Here is a part of a SCL for a dedicated package :
STATEMENT #1
             SET STOPRC 16 .

             STATEMENT #2
             TRANSFER ELEMENT 'RFQ0600'
               FROM ENVIRONMENT 'NDVPROD' SYSTEM 'JCLPROD' SUBSYSTEM 'PCL'
                 TYPE 'JSTCA7' STAGE P
               TO   ENVIRONMENT 'NDVPROD' SYSTEM 'REGUL' SUBSYSTEM 'ARCHIVE'
                 TYPE 'ARCHDIV' STAGE P
                 ELEMENT 'RFQ0600'
               OPTIONS CCID 'SBS201130A' WITH HISTORY BYPASS ELEMENT DELETE
                 BYPASS GENERATE PROCESSOR
              ….
STATEMENT #6
             DELETE ELEMENT 'RFQ0600'
               FROM ENVIRONMENT 'NDVPROD' SYSTEM 'JCLPROD' SUBSYSTEM 'PCL'
                 TYPE 'JSTCA7' STAGE P
               OPTIONS CCID 'SBS201130A'
              .

Now the Sysout when executing the Package :
                                       E N D E V O R   A C T I O N   S U M M A R Y   R E P O R T         VERSION 17.0 SERIAL B1700C
                                                ( P A C K A G E   I N S P E C T I O N )


                                  PROC  NDVR   +------------  INVENTORY  INFORMATION  -----------+  ACTION   ACTION   STMT    SCL
            ACTION    ELEMENT      RC    RC    ENVIRONMENT   SYSTEM    SUBSYSTEM   TYPE     STAGE    TIME    NUMBER  NUMBER WRITTEN
            DELETE    RFA600C     0000  0000   NDVPROD       REGUL     RVT         BND        P    09:43:47       1       8
            DELETE    RFA600C     0000  0000   NDVPROD       REGUL     RVT         PGMCB2B    P    09:43:47       2       7
            DELETE    RFA620B     0000  0000   NDVPROD       REGUL     RVT         PGMCB2B    P    09:43:50       3       9
            DELETE    RFQ0600     0004  0000   NDVPROD       JCLPROD   PCL         JSTCA7     P    09:43:50       4       6
  *NOTFND*  TRANSFER  RFQ0600           0004   NDVPROD       JCLPROD   PCL         JSTCA7     P                           2
  *NOTFND*  TRANSFER  RFA600C           0004   NDVPROD       REGUL     RVT         PGMCB2B    P                           3
  *NOTFND*  TRANSFER  RFA600C           0004   NDVPROD       REGUL     RVT         BND        P                           4
  *NOTFND*  TRANSFER  RFA620B           0004   NDVPROD       REGUL     RVT         PGMCB2B    P                           5
            END OF EXECUTION LOG - HIGHEST ENDEVOR RC = 0004

When executing the Package SCL, the DELETE actions have been automatically executed first. The initial order of the Actions is not taken into account (action #6 is now on 5th position, and action #1 is on 6th position in the list).

As it might leads to serious problems (in this case the source of the elements have been totally deleted from Endevor!!), it should be interesting to know that there is a default sequence applyed in Endevor to execute actions in a SCL. If we cannot change this sequence, at least we should be aware of it, dont you think so?

Thanks a lot
Have a nice day
Rgds
Jean-Christophe

​​

[Phontilla Shuffitt]

Agree we should know the sequence of actions processed in a batch execution.

------------------------------
Software Engineer
Enterprise Technology
Fiserv
Ky, USA
------------------------------

[Guy Derkinderen]

Bonjour Jean-Christophe,

I can think of one reason for doing delete actions first: optional table feature OPTIONAL_PTF_PROCESS_DELETE_ACTIONS_FIRST. As its name suggests, it causes DELETE actions to be processed before any other actions. Can you verify your ENCOPTBL?

If the OPTIONAL_PTF_PROCESS_DELETE_ACTIONS_FIRST feature isn't active, I'd say to open a support ticket.

BTW, the excerpt of the Endevor report shows that you're still running 17.0. Are you aware that Endevor 17.0 isn't supported any more? The currently supported releases are 18.0 and 18.1.Kind regards,

Guy Derkinderen

[Jean-Christophe GUILLEMIN]

Bonjour Guy

Thanks a lot for your feedback as ENCOPTBL is the table I should have focus on. In our configuration this line is 'asterisked' (?) therefore I suppose that the default value of this parameter is used. I suppose that this default value is 'ON', and that is the explanation of this Actions sequence reorder. Good job Guy!!

*        ENHOPT PROCESS_DELETE_ACTIONS_FIRST=ON  

​Concerning the Enedevor release we are using, yes we are still in R17.0. Our wish was to upgrade to the latest version somewhere in 2020 but due to the circumstances we had to postpone it to 2021. I did open a ticket to get the official feedback from the Endevor Support Team, but my ticket was automatically closed because our Endevor version was no longer supported. This is why I took a last chance on this forum, hoping to find someone that could help me understand this Endevor process.

A big thank you to you and Phontilla who took the time to help me on this topic.

Wish you all the best for 2021 :-)

Best regards

Jean-Christophe

[Guy Derkinderen]

Bonjour Jean-Christophe,

We're not there yet, an asterisk in column 1 means that the option is commented out, in other words, it's NOT active.

Having said that, it would be safer to have a run-time report. It can be obtained by adding this DD to your JCL:

//EN$TROPT DD SYSOUT=*

Then run NDVRC1 program C1BM3000 with an empty input (make sure that you use the same libraries that were used in the job step that processed deletes first).

In the EN$TROPT output, look for the string "Optional Features Table". It's structured in 2 columns: "Enabled Options" and "Options Not Enabled". See in which column you find PROCESS_DELETE_ACTIONS_FIRST.

Guy

[Jean-Christophe GUILLEMIN]

Guy,

I ran the C1BM3000 pgm and from the EN$TROPT output I can see that this option is currently on the right side of the report, under the title 'Options Not Enabled'.

Therefore ENDEVOR should use a default value for this option : either consider DELETE actions as firsts actions to execute, or keep the actions order as defined in the SCL. It can just be one way or another, no? My guess is that the default value is 'Yes', but I might be wrong.

Once again thank for your support and your time.

Best rgds

Jean-Christophe