1.0 Release notes, known problems, limitations, and workarounds
1.1 Provided RAMs are Samples
1.2 SCLM RAM Allocation Job
1.3 COBOL RAM load module
1.4 Submit CLIST naming limitation
1.5 Compiling CRASUTIL as a DLL
All RAMs provided with CARMA are samples, and not intended for use in a production environment.
For each user ID that will access CARMA, the CRAS#ASLM job in the hlq.SCRASAMP library must be run. Instructions for customizing the job are within its source. There can only be a single SCLM RAM connection at a time for each user ID or a 630 error will occur.
A PDS RAM written in COBOL is provided. To use this RAM, it must be enabled within the VSAM clusters.
The COBOL RAM can also support a custom action. Directions for enabling this custom action are in the CRACOB24 member of the hlq.SCRASAMP library.
The CLIST used to run the CARMA job hlq.SCRASBMT(CRASUBMT) should not include a '$' in its name. A 655 error will result.
The members CRA#CUTL and CRA#PUTL in the SCRASAMP library are provided as sample JCL for compiling the source in CRASUTIL as a DLL. They are provided for convenience, but are not required for building the sample COBOL ram.
(C) Copyright IBM Corporation 2005, 2006, 2007. All Rights Reserved.