Endevor Processor FG execution fails with a C1G0005S PROC ¬FND
Article ID: 254715
Updated On:
Products
Issue/Introduction
When executing a new Generate processor called GSVYSDMT in batch, it works. However, when executing the processor in Foreground, it fails with this C1G0005S PROC NOT FOUND error:
C1G0005S PROC ¬FND - SYS00158/iprfx.iqual.PROCESS.P1.LOADLIB/iprfx.iqual.PROCESS.P2.LOADLIB
C1G0144I PROCESSOR GSVYSDMT EXECUTION COMPLETED, HIGHEST PROCESSOR STEP RC WAS 0016
From the batch execution, the processor is found and loaded from the Processor LOADLIB:
C1G0246I PROCESSOR GSVYSDMT LOADED FROM iprfx.iqual.PROCESS.P2.LOADLIB
C1G0247I FOOTPRINT: ENV: ENV1 SYS: SYS1 SBS: PROCESS ELM: GSVYSDMT TYPE: PROCESS STG NBR: 2
C1G0248I VER: 0100 DATE: 27OCT22 13:27
NOTE: This only happens in when using SYSVIEW in the same TSO session with Endevor
Environment
Release: All supported versions of Endevor
Cause
Apparently, there's a SYSVIEW module with the same name.
When the SYSVIEW session is active, SYSVIEW executable GSVYSDMT is loaded. When Endevor goes to load the processor, it is getting the address of the SYSVIEW load module, sees that it's not a processor and fails the processor.
Resolution
Apparently, there's a SYSVIEW module with the same name. When the SYSVIEW session is active, SYSVIEW executable GSVYSDMT is loaded.
When Endevor goes to load the processor, it is getting the address of the SYSVIEW load module, sees that it's not a processor and fails the processor.
To resolve this problem:
1) Retrieve the GSVYSDMT processor without Signout.
2) Rename the processor with a different name and Add it to Endevor.
3) Update the Processor Groups to use the new processor name
4) Delete GSVYSDMT from Endevor
Feedback
