I need a little more detail about how you are doing your TRANSFERs because my spidey-sense is tingling.....
My assumption based on your description is that the V6.2 processor group has a different name than the V5 processor group.
Bear with me while I document my thinking....
When one sets up TYPE definitions, you tell Endevor which processor group to use during the TRANSFER action; the MOVE processor defined at the source stage or the GENERATE processor at the target stage. The DEFAULT setting for TYPE definition is to set the value to "G" (GENERATE). So the first question is: Did you change this to "M" (MOVE)? If its left as G, then the processor group defined for the element at the "to/source" would be used maybe causing your problem?
In addition, some "clever" sites change the GENERATE processor defined to processor groups at upper stages to NOT do an actual GENERATE but instead execute the MOVE processor defined in the GENERATE processor slot. Conceivably, this could then MOVE the element without changing the TYPE definition for actions during TRANSFER whereby the MOVE processor defined at the target stage would be executed.... so Endevor would THINK its doing a GENERATE, use the processor group previously defined, but just MOVE the element. While seeming clever, this kind of solution causes my eyes to bleed....
Bottom-line: Look at what is actually happening during the TRANSFER. I believe what you want is the MOVE processor to work properly and be executed during TRANSFER; that should preserve any change to processor group defined to element at lower stage(s).
------------------------------
Consultant
John D Consulting Inc.
------------------------------
Original Message:
Sent: 06-03-2020 06:07 PM
From: James Catalano
Subject: Endevor dropping new compile proc group & keeping current compile group at the target location.
During source promotion a good majority of the time we use the TRANSFER action versus the MOVE action. I do understand the difference and "Yes" a smack on the hand for letting this occur, but this works very well for our shop when used with care. Here's my issue and question. Enterprise COBOL v5 is now off support and we have been converting to COBOL V6.2. We only compile at the stage-1 entry point and the element is frozen when promoting forward. When using the TRANSFER action, I need to have Endevor keep the "from/source" new compile processor group and not drop it to keep the current compile processor group at the target location..?
I am aware of placing the new compile PROC GROUP 'name' within the source promotion package SCL, but trying to spread this message out to many different development groups across the world is a major task. I have COBOL v6 compiled loads sitting in Production and still showing COBOL v5 compile processor groups on the source elements. This is a reporting/conversion issue. Would it be possible to have an option within the Endevor ENCOPTBL that would keep the compile processor group that is being promoted with the source element. Or possibly even a "Yes" or "No"
switch for keeping the processor group name within the Endevor ENDICNFG member. Appreciate any information to assist with this. Thanks for your time.