Hi All, 

  I am working on V05 to V10 upgrade in Linux and currently performing the compilation of the code using cob64 and facing below issues.

Appreciate your help with these issues, attached the compiler options used for reference.

 1)  .so file not Created during Bulk compile

   We are using the below command to compile the programs, the process is creating .int, .idy , .o and .so file during the compilation if I perform the task for one module by specifying the full name but only .int, .idy and .o is created if I use wildcard *.cbl to pickup all the program. Could some one please help with the correct option to create the .so files during bulk compilation.

  cob64 -z -v -k ./SRC/*.cbl -N OBJ"/home/jenkins/loadlib/batload/" -a -g -C "USE(/opt/microfocus/EnterpriseDeveloper/cobol.dir)" -C "USE(/opt/microfocus/EnterpriseDeveloper/sql.dir)" -C "USE(/opt/microfocus/EnterpriseDeveloper/batch.dir)" -U

2) Compilation of Programs with special characters failing 

    Some of the programs have special character in the comments and also in strings which is causing the compilation to fail. I have changed the source code file to UTF-8 but still causing the same problem. Do we have any option or compiler directive to fix this issue.

3)  Sliding Data item error 

    We are getting the below error while compiling some of the programs, there is a value clause used in the depending on variable but the same code is compiling fine in Version 5.0. Do we have any way to overcome this issue through compiler options.

2623       05  XAS-FORMAT-COUNT-1  PIC 9(4).                          00650002
    [cobol] COBCH1962S A sliding data item cannot have a VALUE clause.

Hi All, 

  I am working on V05 to V10 upgrade in Linux and currently performing the compilation of the code using cob64 and facing below issues.

Appreciate your help with these issues, attached the compiler options used for reference.

 1)  .so file not Created during Bulk compile

   We are using the below command to compile the programs, the process is creating .int, .idy , .o and .so file during the compilation if I perform the task for one module by specifying the full name but only .int, .idy and .o is created if I use wildcard *.cbl to pickup all the program. Could some one please help with the correct option to create the .so files during bulk compilation.

  cob64 -z -v -k ./SRC/*.cbl -N OBJ"/home/jenkins/loadlib/batload/" -a -g -C "USE(/opt/microfocus/EnterpriseDeveloper/cobol.dir)" -C "USE(/opt/microfocus/EnterpriseDeveloper/sql.dir)" -C "USE(/opt/microfocus/EnterpriseDeveloper/batch.dir)" -U

2) Compilation of Programs with special characters failing 

    Some of the programs have special character in the comments and also in strings which is causing the compilation to fail. I have changed the source code file to UTF-8 but still causing the same problem. Do we have any option or compiler directive to fix this issue.

3)  Sliding Data item error 

    We are getting the below error while compiling some of the programs, there is a value clause used in the depending on variable but the same code is compiling fine in Version 5.0. Do we have any way to overcome this issue through compiler options.

2623       05  XAS-FORMAT-COUNT-1  PIC 9(4).                          00650002
    [cobol] COBCH1962S A sliding data item cannot have a VALUE clause.

Hi Durga,

These types of questions should be posted in one of the specific product forums like Visual COBOL or Enterprise Developer, instead of using the General Discussion forum.

For the compilation issue you could use a for loop instead of using the wildcard character directly within the cob64 command. What your command is doing is compiling all the sources to .o's and then linking them together in the same .so with the name of the first program.

i.e.

for cbl in *.cbl; do cob64 -z -v -k $cbl; done

For the value clause error that you are receiving, this is due to the ODOSLIDE directive being on. We changed this behavior to output an error back in V6.0 so that we are aligned with the IBM product. You can get around this be adding the following directive to your compile:

-C '+ ALLOWSLIDINGVALUE'

For the special characters problem, to what special characters are you referring?
Did this used to compile in 5.0?

There is a directive SOURCE-ENCODING that you can look at that may help but embedding special characters in literals should be done using hex constants such as X"0D", etc.

Thanks.

Regarding:  2) Compilation of Programs with special characters failing 

I hope you can find a directive that fixes it.  Out target OS is z/OS mainframe but we've experienced a similar problem.    The problem was caused by using text editors like Windows notepad, which can insert characters that upload can't convert.    The solution for us was to locate special character and replace with a legitimate character.     We used the mainframes ISPF editor.   It has a find option that makes it quick:

P'.'      Any character that cannot be displayed          

Many thanks for your valuable input Chris, I am new to the forum and after posting it here I found about other topics so I reposted the query in other topics too. The .so issue is resolved with the scripting , the sliding variable issue is getting fixed when I remove INIT-BY-TYPE compiler option but this will impact rest  of the program compilation. The -C '+ ALLOWSLIDINGVALUE' is not recognised and I also raised a ticket with the coretech team for this issue.