Created On:  03 August 2010
Problem:
When running a COBOL program in Linux or UNIX, using Enterprise Server batch JCL, files created by the program are cataloged in Enterprise Server, but are not physically present in the target folder.
Resolution:
When using Enterprise Server in conjunction with UNIX or Linux, you may find that although output files created by your COBOL application program are cataloged in Enterprise Server, they have not been created in the target folder.
In order to get Enterprise Server to work correctly with UNIX or Linux, you must use the following compiler directive:
-C"dialect(entcobol)"
This dialect includes a number of directives, one of which is "charset(ebcdic)", which may not be appropriate, given that the character set used by UNIX and Linux is ASCII.
You can override this explicitly by adding the ascii compiler directive:
-C"dialect(entcobol) charset(ascii)"
In order to get Enterprise Server to work correctly with UNIX or Linux, you must use the following compiler directive:
-C"dialect(entcobol)"
This dialect includes a number of directives, one of which is "charset(ebcdic)", which may not be appropriate, given that the character set used by UNIX and Linux is ASCII.
You can override this explicitly by adding the ascii compiler directive:
-C"dialect(entcobol) charset(ascii)"
Incident #2465628
Old KB# 31478
#MFDS
#EnterpriseDeveloper

