IBM Content Manager, Version 8.5 Operating systems: z/OS

Configuring the Content Manager for z/OS Toolkit for the CICS environment

You can configure the Content Manager for z/OS® Toolkit by modifying options in the JVM profile, modifying the security policy file, and setting the connection parameters to the library server. After you configure the Toolkit for the CICS® environment, you can run the CICS COBOL samples.

The Content Manager for z/OS Toolkit Java™ APIs can run under CICS. The Toolkit includes sample Java and COBOL applications. IBM® Content Manager applications can be written in the Java language for the CICS environment by using the ICM connector APIs in the DB2® Connector Manager Toolkit for z/OS. A sample Java application prefix/samples/java/icm/zosDelta/SCICSTransactionICM.java is provided with the Content Manager for z/OS Toolkit.

A second sample application program ICMCOBOL (in HLQ.SICMSAMP) shows a COBOL application calling a Java program SCICSCMAPI that invokes IBM Content Manager Java APIs. These samples use CICS services through the JCICS class. Therefore, you must include the dfjcics.jar file (a Java class library provided by CICS) in your class path.

When you use the ICM connector APIs in a CICS environment on z/OS, the following limitations apply:

The following methods are not supported:
- DKDatastoreICM.execute() method. The suggested workaround is to use DKDatastoreICM.evaluate() instead.
- DKDatastoreICM.executeWithCallBack() method.
Only explicit transactions are supported (that is, those that use DKDatastoreICM.startTransaction()/commit()/rollback()).
Client for Windows (deprecated) and custom clients (IBM Content Manager APIs) do not support the display of objects.
Each Content Manager for z/OS Java API application is run as a task in the CICS region, and only one CICS task can run in a Java Virtual Machine (JVM) at a time. For multiple users or applications to run at the same time, the CICS environment can be set up to run multiple JVMs per CICS region or have more than one CICS region.
The library server must be on the same z/OS system where the CICS Transaction server for z/OS is located. The library server on a remote system is not supported.
Connecting to DB2 by using a shared connection ID is not supported. Each IBM Content Manager user is required to be uniquely defined in RACF® and must be authorized to access the IBM Content Manager database. Likewise, the DB2CON option (to allow a shared database connection) is not supported for the ICMSERVERREPTYPE parameter in the cmbicmsrvs.ini file.

Important: Before you can configure the Content Manager for z/OS Toolkit for the CICS environment, you must have a fully operational Content Manager for z/OS Toolkit.

To configure the Toolkit for the CICS environment, you must:

Modify options in the JVM profile. The sample JVM profiles are placed in the HFS directory $CICS_HOME/JVMProfiles and the default profile is DFHJVMPR. You must modify the options in Table 1 for the Toolkit.

Table 1. Options to set in the JVM profile when using the CICS environment with the Toolkit
Option	Value	Description
REUSE	YES	Continuous reusable JVM is the only reusability mode supported.
CLASSPATH	Class paths from the cmbenv81.sh file	The CLASSPATH option should contain all the class paths that are specified in the `prefix`/usr/lpp/icm/V8R5M0/bin/cmbenv81.sh file.

Modify the security policy file. By default, CICS is set up to run with the Java 2 security manager with the sample CICS security policy file specified as $CICS_HOME/security/dfjejbpl.policy. If you choose to use the Java 2 security with the ICM Java APIs, you must change the policy file to grant permission to the ICM Java API driver by adding the following line to the dfjejbpl.policy file:
```
grant codeBase "file:prefix/usr/lpp/icm/V8R5M0/-" {
  permission java.security.AllPermission;
};
```

Set the connection parameters to the library server in the cmbicmsrvs.ini file (located by default in the prefix/usr/lpp/icm/V8R5M0/cmgmt/connectors directory). The following parameters must be set as:

Table 2. Connection parameter settings that are needed to run Content Manager for z/OS Toolkit for Java APIs in the CICS environment
Parameter	Value	Description
ICMSSO	TRUE	The underlying CICS DB2 security procedure performs the necessary authentication for each execution of a transaction. You can also set this value at the application level by specifying it in the DKDatastoreICM.connect() method.
ICMDBAUTH	CLIENT	This setting is used with the ICMSSO parameter. The underlying CICS DB2 attachment facility performs the required security verification. You can also set this parameter at the application level by specifying it either in the DKDatastoreICM constructor or in the DKDatastoreICM.connect() method.
ICMREMOTE	FALSE	Type 4 connectivity is not supported under CICS. Only the local server is supported.

After you configure the Toolkit for the CICS environment, you can run the CICS COBOL samples.

To run the ICMCOBOL and SCICSCMAPI samples:

Customize and run the ICMCOBOL job that compiles the COBOL program and generates the load module.
Use javac to compile SCICSCMAPI.java to generate the SCICSCMAPI.class file.
Define the program, transaction, and DB2ENTRY resources for ICMCOBOL in CICS.
Define the program and DB2ENTRY resources for SCICSCMAPI in CICS.
Log on to CICS region and issue the transaction ID defined for ICMCOBOL.

Feedback