How to address the following CA Ramis error in IMS/DC environment?
*** DL/1 LIMIT EXCEEDED *** TERMINATION BEFORE COMPLETION REQUEST SUBMITTED TO BMP TRAN
CA Ramis Reporter
The RAMDIRDB should be checked on the DBLIM limits.
Increase the DBLIM to include all of the segments in the database.
CA Ramis Communications Interface to IMS DB/DC User Guide
2.1 CA Ramis Directory Database
A CA Ramis Directory Database (RAMDIRDB) must exist before you can use CA Ramis in the IMS DB/DC environment. RAMDIRDB is prepared by the DBA, using the RAMDRGEN utility. It contains all of the information required by CA Ramis to process CA-Ramis files; that is the names under which the files are known to CA Ramis, the segment names under which they are known to IMS, and the characteristics of each file.
RAMDIRDB must include an entry specifying the transaction code to be used for processing. This entry can also specify resource control limits that control access to the user databases and CA Ramis, and are applied to any execution of the transaction.
If your DBA has specified these limits, they will be enforced when you invoke a transaction. The limits are:
DBLIM The number of DL/l calls allowed
MQLIM The number of I/0's allowed to the message queue CPULIM The amount of time allowed for processing
In addition to the entry specifying the transaction code and resource control limits, the RAMDIRDB can also include entries that define the input and output files, output destinations (using the command OFFLINE), CA Ramis Work Files, and IMS databases to be used for executing the transaction. These and other entries are described in the CA Ramis publication Communications Interface to IMS DB/DC DBA Guide.
Refer to the Communications Interface to IMS DB/DC DBA Guide and Communications Interface to IMS DB/DC User Guide via the CA Ramis Version 7.4 set of documentation at CA Ramis Bookshelves and PDFs.