The CA Ramis Accounting option has been activated but there are no entries written to the RAMACTG file when a user RPI application accessing a CA Ramis database is executed.
Is this as expected?
Release: 7.4
CA Ramis
CA Ramis Reporter
Only the non-procedural CA Ramis execution (PGM=RAMIS) activity in batch, TSO, or CICS cause entries to be written to the CA Ramis accounting file RAMACTG.
An RPI (CA Ramis Procedural Language Interface) program can be written in Cobol, Assembler, PL/1, or Fortran to access the Ramis database outside of non-procedural CA Ramis.
An RPI application written in Cobol will have calls similar to:
CALL 'RAMIS' USING PCB, ..etc....
The CA Ramis Accounting file is not accessed for the execution of an RPI application. With RPI, the RAMACTG data set is not opened and no records are written to it.
CA Ramis Accounting is activated via the link-edit of the main RAMIS module including RAMACTG.
See CA Ramis 7.4 SAMPJCL members ACCNOVLY, ACCOVLVS, ACCOVL1, or ACCOVREF for various overlay options when link-editing the RAMIS module to activate the accounting option.he CA Ramis Version 7.4 set of documentation can be found at CA Ramis Bookshelves and PDFs.