What conditions would cause a C1G0023W and C1G0333W to be issued together on a set of elements? The set of two elements that have been MOVEd with the BYPASS DELETE option on.
Release : 18.0 18.1
Component : Endevor Software Change Manager
These messages are quite normal, and can easily be obtained for example by doing a move without deleting the source of the move (i.e. by using the doing a move without deleting the source of the move (i.e. by using the option 'BYPASS ELEMENT DELETE' in the move) – then repeating the move.
The first message - C1G0023W NO CHANGES DETECTED - SOURCE MANAGEMENT MAY HAVE ALREADY BEEN PERFORMED - is issued because there are no changes between the element you are moving and the contents of the element at the target location. There may have been a failed move previously for whatever reason, or as I pointed out, there may have been a move without delete, or even possibly a programmer has simply edited the source and ended up with the same source code as is present at the target. Either way, the end result is that there has been no change to the source code, so there is not a new delta level created, and this message is issued as a warning (RC=4) just in case that was unexpected.
This checking is done regardless of the processor group, as it is essential in source management (almost the opposite of the check that you haven't changed too much code, resulting in an SMGR124W warning, and a RC=4).
Both of these situations can be regarded as abnormal, thus a warning, which should be checked.
In any move that fails, the failure will cause the final delete behind which is normally performed to be skipped, and thus a further move will be required to complete the operation. However, depending upon when and why it failed, it may not be necessary to repeat the move, in fact only a delete of the original element might be all that is needed. An example there could be a move that failed after the source was 'copied' successfully, and an associated generate failed for any reason (library full, volume full, RACF/ACF2 problem, job time-out, user canceling the job etc…) did not complete. In that case, a simple generate at the target of the move would complete that part of the move process, and a delete at the origin of the move would finish it off. I would though not normally recommend that, simply because Endevor does it all in one job.
The second message C1G0333W – PROCESS MANAGEMENT MAY HAVE ALREADY BEEN PERFORMED FOR THIS ELEMENT – is referring to “processor management”. The reason the message may be issued is the move action determined that the appropriate processor may have already been executed for that element. The message is issued when a failed move action is restarted, or when a move action with BYPASS ELEMENT DELETE is restarted.
To sum up, the warning these messages are giving is really to warn the user that their code has been moved, but the result is unusual and should be checked. Normally these messages should not occur, and when they do, then a little inspection to find out why is a good practice.
There is an option in the ENCOPTBL that will bypass the C1G0333W and execute the processor –