CASSI9012E JCL support failed to start. Error returned from casspool, RC=0020

Question

Hello.

I have a COBOL application composed of several projects (n COBOL-type Projects, one COPY-type project, and one COPY DCLGEN-type project), and I wonder if it is technically possible to execute any program from any project with a single existing batch region defined in Enterprise Developer 11 for Eclipse running on a Windows 11 PRO operating system. In fact, I have created a batch region in the aforementioned environment and it starts correctly when associating a single project (I performed the association using Enterprise Developer for Eclipse 11 on my PC with Windows 11 PRO operating system), but the moment I associate a second project to the region, the following message appears during startup:

JES000057E JES validation - MFJCLCFG failed for spool file SPLJOB.dat - RC = +000000007 CASSI9012E JCL support failed to start. Error returned from casspool, RC=0020

In fact, I have observed that the ESCWA environment variable in the aforementioned Enterprise Developer 11 effectively concatenates the two paths of both projects:

IDE_LOADLIB=C:\xxxxx\xxxxxx\xxxxt\rocket\Project1Batch\New_Configuration.bin\New_Configuration.bin;C:\xxxxx\xxxxxx\xxxxt\rocket\Project2Batch\New_Configuration.bin\New_Configuration.

And, of course, in the JES configuration of the aforementioned ESCWA, the paths are defined as follows:

JES Program Path: $IDE_LOADLIB

System Catalog: $IDE_LOADLIB\catalog.dat

Default Allocated Dataset Location: $IDE_LOADLIB

System Procedure Library: SYS1.PROCLIB

So, when the region starts, it does not find the path to the JES files because the path is not valid (in reality, there are two paths).

Would it make sense to define a single JES path for all projects?

If it makes sense, how could I define a new environment variable in ESCWA to have a single JES path for all projects?

At the catalog level, something similar happens. In Enterprise Developer for Eclipse 11, the following message appears when trying to consult the region's catalog:

Catalog file not found. C:\xxxxx\xxxxxx\xxxxt\rocket\Project1Batch\New_Configuration.bin;C:\xxxxx\xxxxxx\xxxxt\rocket\Project2Batch\New_Configuration.bin\catalog.dat

*This is also not a valid path for the catalog file. Would it make sense and is it technically possible to have a single catalog for all projects?

Thanks."

Kim Hoskin · Answer

Hi Sergi,You could consider to:Configure each region to have it’s own hardcoded catalog file paths to separate these, then you remove the $IDE_LOADLIB environment variable part completely.Or you could create separate regions, one for each project that use their own catalog/spools.There are several approaches that can be used, it depends on your requirement.Regards,Kim