JCICS supports most of the functions of the EXEC
CICS API commands.
The JCICS classes are fully documented in Javadoc that is generated
from the class definitions. The Javadoc is available at JCICS Class Reference.
JavaBeans
Some of the classes
in JCICS can be used as JavaBeans,
which means that they can be customized in an application development
tool such as Eclipse, serialized, and manipulated using the JavaBeans
API.
Library structure
Each JCICS library component falls into one of four categories:
Interfaces, Classes, Exceptions, or Errors.
CICS resources
CICS resources, such as programs or temporary storage queues, are
represented by instances of the appropriate Java class, identified
by the values of various properties such as the name
of the resource.
Arguments for passing data
You can pass data between programs using channels and containers,
or by using a communication area (COMMAREA).
System.out and System.err
For each Java-related CICS task, CICS automatically creates two Java PrintWriters classes
that can be used as standard out and standard error streams. The standard
out and standard error streams are public fields in the Task class
called out and err.
Threads
Only the initial thread in the JVM can access
the JCICS API. You can create other threads, but you must route all
requests to the JCICS API through the initial thread. In a JVM server
environment, multiple initial threads can access the JCICS API using
the same JVM.