PERCobol produces .class files which are the Java equivalent of .obj or .exe files. These class files get bundled by the deploy wizard into a .jar (java archive) file, along with the PERCobol runtime. In  Windows, .jar files can be setup so that the user can double click on the .jar file to run the program. The deploy wizard will also create a .bat file that the user can use to execute the program.

To use the deploy wizard:

1. In the navigator view, highlight the project to be deployed.

2. Choose file->export...->PERCobol Deploy Wizard, click next.

3. The class files will show up in the window.

4. Type the path/name of the jar file to create into the 'export destination' field and click next.

5. You can choose to exclude certain runtime elements from the deploy if you are not using those runtime elements. This can be helpful inthat it decreases the size of the jar file.

6. Make sure that the main program shows in the main program field.

7.  Click finish.

To Verify the results

From windows explorer, go to the folder that contains the new jar file. You should see the new jar file and a .bat file with the same name. Make sure that any indexed files and such are in the correct locations (current working directory, etc.) before running your program outside of eclipse.

NOTE:

Java finds other .class files using a classpath. Since PERCobol programs that are CALLed are .class files, these files need to be found via the classpath. For instance, when running theprogram from the command line or .bat file:

java -classpath <jar_1>.jar;<jar_2>.jar <program-name>

where <jar_1>.jar is where one program is located, and <jar_2>.jar is where the other program is located. <program-name> is the name of your main .class file, not including the .class extension. (This name is the main cobol program's program-id, all lowercase, with
underscores instead of dashes.)



Last updated on December 28, 2009 by Daniel Myers