Building the Java samples

To build the Java samples, you need write permission for the HFS directory in which the samples are stored and for its subdirectories. These directories are part of the directory structure that includes the other CICS files which have been installed on HFS. If you do not want users to have write permission for these directories, you should copy the samples directory and its subdirectories to another location on HFS before building the samples.

If you use OMVS to perform this task, note that you might need to increase the size of your TSO region when you are using the IBM® Software Developer Kit for z/OS®, Java™ 2 Technology Edition, Version 1.4.2.

Build the samples as follows:
  1. Change directory to samples/dfjcics.
  2. Type make jvm to build all the samples, or alternatively:
    make -f <sample_name>.mak jvm

    where sample_name is the name of the specific sample you want to build.

    The makefiles invoke javac and store the output files in the $CICS_HOME/samples/dfjcics/examples/sample_name HFS directory, where sample_name is the name of the sample program.

The following CICS C language programs are stored in SDFHSAMP during CICS installation. They are linked by the Program Control and one of the “Hello World” Java sample programs. You need to compile and translate these supplied C programs, link them into a load library in the CICS DFHRPL concatenation, and define them to CICS as described in Defining CICS resources.
  • DFH$LCCA
  • DFH$JSAM
  • DFH$LCCC
Note:
  1. In the names of sample programs and files described in this book, the dollar symbol ($) is used as a national currency symbol and is assumed to be assigned the EBCDIC code point X'5B'. In some countries a different currency symbol, for example the pound symbol (£), or the yen symbol (¥), is assigned the same EBCDIC code point. In these countries, the appropriate currency symbol should be used instead of the dollar symbol.
  2. DFH$LCCA and DFH$JSAM are standard CICS programs that could be written in any of the CICS-supported languages. If, for example, you do not have a C compiler, you could write COBOL versions of the supplied programs and use them in place of the supplied C versions.