The IMTK does not generally support the ODOSLIDE compiler directive. In addition, the ODOOSVS compiler directive and several
DIALECT directive settings automatically set ODOSLIDE; therefore, if your program does not require that you compile using
the ODOSLIDE directive, specify the NOODOSLIDE compiler directive to avoid possible compiler errors.
To compile a program that contains nested OCCURS DEPENDING ON clauses, which require the ODOSLIDE directive to compile, change
the OCCURS DEPENDING ON syntax to OCCURS COUNT IN. This change removes the ODOSLIDE directive requirement for compiling for
the IMTK, and also leaves the code valid for compilation with ODOSLIDE outside of the IMTK environment.
REST/JSON IMTK implementation -
HTTP requests sent from scripts within a web browser to REST services deployed on an enterprise server might fail due to the
same-origin policy (SOP). Some browsers might implement (or support plugins that implement) techniques for relaxing SOP such
as cross-origin resource sharing (CORS) that enable sending cross-origin requests successfully. For REST services, Enterprise
Server does not implement a method for relaxing SOP. This means that browsers that implement CORS (or any other SOP relaxation
technique) might still forbid requests made from scripts due to Enterprise Server not implementing the equivalent technique
on the server side.
Each group field (i.e. field containing subitems) in a Java interface must have a name that is unique across all operations
of that interface. Where this is not the case, client generation may fail.
If you encounter an error message
>>> COBOL Interface generation failed Could not find a part of the path <path> when generating test clients for service interfaces, the likely cause is that Microsoft Internet Information Server (IIS)
is not installed on your system.