Invalid entries in the options XML files (Container.xml, PlatformProperties.xml, ServicesSpecification.xml) may cause null pointer exceptions during the execution of the batch processor.
To avoid this event, follow the format for correctly specifying entries in the options XML files.
Even though the COBOL data names are not case sensitive, the exact case must be specified in the specification xml files. For example, if in the COBOL data source, the data name is called MY-Data, in the Service specification xml the nativeTypeName attribute must be set to nativeTypeid="MY-Data". If the exact case is not specified, the data name is not found and the first available level 01 data name is used by default.
The location of the COBOL input files can be specified in the importDirectory attribute as an absolute path, starting with the drive specification (for example, C:\mypath\test).
Try doing either of the following:
OR
If a relative path is desired (for example, so that the configuration files and Cobol source code can be relocated without changing any file locations in the xsebatch configuration files). Perform the following:
(For example, importFile="cobol_src/DFH0ACDT.cbl" or importFile="../cobol_src/DFH0ACDT.cbl".)
These paths are relative to the location from which xsebatch is invoked.
| Directory: | Description: |
|---|---|
| C:\workspace\account_details | Main project |
| C:\workspace\account_details\cobol_src | Subdirectory with COBOL source files to import |
| C:\workspace\account_details\xsebatch_config | Subdirectory with XML configuration files for xsebatch |
<InputOutputMessage importFile="../cobol_src/DFH0ACTD.cbl">
</InputOutputMessage>