Configuring the IBM Content Manager Toolkit by using JCL

To configure the IBM Content Manager Toolkit by using JCL, use the Job Configuration tool or run the hlq.SICMSAMP(ICMCONFG) job.

The hlq.SICMSAMP(ICMCONFG) JCL runs prefix/usr/lpp/icm/V8R7M0/config/icmconfig. The REXX run requires user input to create the configuration files. COND CODE = 0000 indicates success; COND CODE = 0016 indicates failure. You can also examine the contents of the STDOUT file that you defined in the JCL or in the job's SYSOUT for information about the parameters that were passed and the files that were created.
The SICMSAMP library contains:
ICMCFGLB
A JCL job for building component table views and default item.
ICMCFGPA
Sample parameter file to be used with the ICMCFGLB JCL.
ICMCOBOL
A JCL job that compiles the COBOL program and generates the load module.
Requirement: You must configure the IBM Content Manager Toolkit for the CICS® environment before you can run ICMCOBOL.
ICMCONFG
Runs the configuration script icmconfig.
ICMCRYPT
Adds additional encrypted user IDs and passwords to cmbicmenv.ini.
ICMDPDAT
The properties file that is used by ICMDPWEB as an input to configure and deploy the web services.
ICMDPWEB
Runs the web services script icmdpweb under USS by using ICMDPDAT as an input. It configures and deploys the web services.
ICMUNJAR
A JCL job for unpacking the zOSValidator.jar file.
ICMUNTAR
Extracts the samples.pax and WebservicesSamples.pax files after the installation and after applying maintenance.
ICMVALTL
A JCL job that runs the validation utility by launching the icmrmlsval390.sh script under IBM z/OS® UNIX® System Services (USS). Before you run this job, you must configure the ICMVUENV and ICMVUPRO files.
ICMVERFY
Verifies that the installed connector connects to the IBM Content Manager library server for z/OS.
ICMVUENV
This file contains the environment variable settings that are required by the validation utility.
ICMVUPRO
The properties file that is used by ICMVALTL as input to run the validation utility.
The ICMCONFG configuration program by default generates the following configuration files in EBCDIC (IBM-1047) file encoding:
  • cmbicmenv.ini
  • cmbicmsrvs.ini
You have the option to generate the configuration files in ASCII (ISO8859-1) encoding by specifying ENCODE=ASCII under the STDENV DD statement in the ICMCONFG JCL job. Either encoding format is accepted by applications such as IBM Content Manager Toolkit Java™ on z/OS UNIX System Services (that is, if you run the APIs outside of the WebSphere® Application Server environment).

After ICMCONFG successfully creates and populates the script prefix/usr/lpp/icm/V8R7M0/bin/cmbenv81.sh with environment variables, copy these variables to your .profile file or add code to your .profile file to run the cmbenv81.sh script. If you want to use XML services, run the cmbenv81.sh script with the xmlsdk option (that is, run the command cmbenv81.sh xmlsdk) to add the additional libraries that are required at runtime for XML services.

Tip: The message that is displayed after you run the ICMCONFG job does not necessarily indicate successful completion even if it states MAXCC=0. This message might look similar to the following output: 
20.07.57 JOB02110 $HASP165 ICMCONFG ENDED AT ISCMVSD9  MAXCC=0 CN(INTERNAL)
Examine the JES2 JOB LOG on SYSOUT for accurate condition codes. The JOB LOG might look such as the following output: 
18.44.59 JOB02093  ACT510I ICMCONFG.CONFIG   STEP TERMINATED --- COND CODE= 0000
18.45.05 JOB02093  ACT510I ICMCONFG.*OMVSEX  STEP TERMINATED --- COND CODE= 0016
The ICMCRYPT batch job adds encrypted user IDs and passwords to the cmbicmenv.ini file. You do not need to run this job for the initial configuration. If you specify ASCII in the configuration program, the cmbicmenv.ini file that contains an encrypted ID and password will be generated as ASCII. To update or add an ID and password, you must also specify ASCII on the update. The cmbicmenv.ini file allows only one entry per database location name.

To extract the samples.pax and WebservicesSamples.pax files by using JCL, run hlq.SICMSAMP(ICMUNTAR). This JCL runs prefix/usr/lpp/icm/V8R7M0/config/untar, a shell script that extracts the prefix/usr/lpp/icm/V8R7M0/samples/java/samples.pax file into the prefix/usr/lpp/icm/V8R7M0/samples/java directory, and extracts the prefix/usr/lpp/icm/V8R7M0/samples/webservices/WebservicesSamples.pax file into the prefix/usr/lpp/icm/V8R7M0/samples/webservices directory. If a PTF is applied that includes an updated samples.pax file, you only need to extract the file and do not need to reconfigure the system. The code COND CODE = 0000 indicates success; the code COND CODE = 0016 indicates failure.

Important: Run ICMUNTAR only after ICMCONFG successfully configures the environment variables in prefix/usr/lpp/icm/V8R7M0/bin/cmbenv81.sh and after you configure your .profile file to export these variables.