Support for run-time elements in dynamically called program names

The following situation is pervasive across the Tesco Continuous Replenishment application.

Program JL0F30 has a call to JL0F40 using the following variable:

03 JLF40-PROGRAM-NAME PIC X(8) VALUE "JL F40". (Note the embedded space in the program name).

Prior to the call, this is amended as follows:

MOVE ENDEVOR-FOOTPRINT-SUBSYSTEM-C3 TO JLF40-PROGRAM-NAME (3:1).

The Endevor Footprint is put into the code at compilation time, so it is present in the run-time executable, but not in the source code. We know, because of the code we have been supplied, that SUBSYSTEM-C3 will be '0', but it is not present in the supplied source code, where we see the following:

01 ENDEVOR-FOOTPRINT.
03 FILLER PIC X(30) VALUE
"**LEGENT*ENDEVOR*C1FOOTPRT*INS".
03 FILLER PIC X(30) VALUE
"ERTED*BY*PDSMAN*SCAN/REPLACE**".
*
01 ENDEVOR-FOOTPRINT-INFO REDEFINES ENDEVOR-FOOTPRINT.
03 ENDEVOR-FOOTPRINT-SITE PIC X.
03 ENDEVOR-FOOTPRINT-ENVIRONMENT PIC X(8).
03 ENDEVOR-FOOTPRINT-SYSTEM PIC X(8).
03 ENDEVOR-FOOTPRINT-SUBSYSTEM.
05 ENDEVOR-FOOTPRINT-SUBSYSTEM-3 PIC X(3).
05 ENDEVOR-FOOTPRINT-SUBSYSTEM-3R REDEFINES
ENDEVOR-FOOTPRINT-SUBSYSTEM-3.
07 ENDEVOR-FOOTPRINT-SUBSYSTEM-2 PIC X(2).
07 ENDEVOR-FOOTPRINT-SUBSYSTEM-C3 PIC X.

The only way to currently resolve this is by use of the manual resolution override facility, which will have to be done for EACH call of this type in EACH program making calls (@1400 programs making multiple calls per program).

Attached: Program JL0F30, copybook ZFFTPRNT, copybook JLF40C.