Which SYSLIB definition is used when loading zFiles from RTC via Load Files to z/OS?

I am using IDz 14.0 with RTC 6.0.4.

I have created the zComponent project and all applicable z/OS Enterprise Extensions (Dataset Definitions, Language Definitions, Translators).

I am now looking at using the Load Files to z/OS option from the RTC Load Sandbox menu. However, I am experiencing the following behavior regarding searching of Copybook libs:

If I open a program from either the z/OS MVS subproject, or from the Remote Systems Explorer, IDz does not find the copybook libraries being referenced, even after setting the Property Group which the correct SYSLIB definition.

If I also run a Remote Syntax Check on this program, the JCL job abends with a NULLFILE error for the SYSLIB.

IEC141I 013-64,IFG0196J,ABSR731Y,COBOL,SYSLIB,,,
NULLFILE
IEA995I SYMPTOM DUMP OUTPUT
SYSTEM COMPLETION CODE=013  REASON CODE=00000064
 TIME=15.39.56  SEQ=02980  CPU=0000  ASID=005C
 PSW AT TIME OF ERROR  075C1000   80DB7456  ILC 2  INTC 0D
   NO ACTIVE MODULE FOUND
    

Looking at the JCL that was generated, it does not contain the SYSLIB definition:

//ABSR731Y JOB NOTIFY=ABSR731,             J0057300
// MSGCLASS=9,CLASS=C
//
//STP0000 EXEC PROC=ELAXFCOC,
// CICS=,
// DB2=,
// COMP=,
// PARM.COBOL=('NOC',
// 'LIB,DYNAM,ADATA,EXIT(ADEXIT(ELAXMGUX))')
//COBOL.SYSPRINT DD DISP=SHR,
//        DSN=XXXX.LISTING(PLM000D)
//COBOL.SYSXMLSD DD DSN=XXXX.ERRCOB.PLM000D.Z359858.XML,
//        DISP=MOD
//COBOL.WSEDSF1 DD DSN=XXXX.ERRCOB.PLM000D.Z464026.XML,
//        DISP=SHR
//COBOL.WSEDSF2 DD DSN=XXXX.ERRCOB.PLM000D.Z584888.XML,
//        DISP=SHR
//COBOL.WSEDSF3 DD DSN=XXXX.ERRCOB.PLM000D.Z745322.XML,
//        DISP=SHR
//COBOL.WSEDSF4 DD DSN=XXXX.ERRCOB.PLM000D.Z855117.XML,
//        DISP=SHR
//COBOL.SYSIN DD DISP=SHR,
//        DSN=XXXX.COBOL(PLM000D)
//
//
    

However, if I log out of RTC, and then open the program, then it finds the copybooks and the Remote Syntax Check works.

The generated JCL for the Remote Syntax Check does contain the correct SYSLIB concatenation:

//ABSR731Y JOB NOTIFY=ABSR731,             J0058640
// MSGCLASS=9,CLASS=C
//
//STP0000 EXEC PROC=ELAXFCOC,
// CICS=,
// DB2=,
// COMP=,
// PARM.COBOL=('NOC',
// 'LIB,DYNAM,ADATA,EXIT(ADEXIT(ELAXMGUX))')
//COBOL.SYSPRINT DD DISP=SHR,
//        DSN=XXXX.LISTING(PLM000D)
//COBOL.SYSLIB DD DISP=SHR,
//        DSN=XXXX.PCOPY
//        DD DISP=SHR,
//COBOL.SYSXMLSD DD DSN=XXXX.ERRCOB.PLM000D.Z135262.XML,
//          DISP=SHR
//COBOL.WSEDSF1 DD DSN=XXXX.ERRCOB.PLM000D.Z283341.XML,
//          DISP=SHR
//COBOL.WSEDSF2 DD DSN=XXXX.ERRCOB.PLM000D.Z386361.XML,
//          DISP=SHR
//COBOL.WSEDSF3 DD DSN=XXXX.ERRCOB.PLM000D.Z511502.XML,
//          DISP=SHR
//COBOL.WSEDSF4 DD DSN=XXXX.ERRCOB.PLM000D.Z636785.XML,
//          DISP=SHR
//COBOL.SYSIN DD DISP=SHR,
//        DSN=XXXX.COBOL(PLM000D)
//
//* ADDITIONAL JCL FOR COMPILE HERE **
//
    

I am aware that the behavior of certain IDz functionality changes when using Load to z/OS (such as Remote Syntax Check). However, I have assumed that it would now use the Translator to populate the SYSLIB instead of the Property Group. The translator does have the same SYSLIB defined as the Property Group.

Is my assumption correct? Or am I missing something?

Thank you,

Sudheer