The client noticed they were getting a TN5132E in the CA Mainframe Application Tuner (MAT) LOG.
TN5132E
Last update September 4, 2015
Neither ERBSMFI or CX10GVID could be loaded - DA cmd disabled
Reason:
During Open/CA Mainframe Application Tuner initialization, ERBSMFI or CX10GIVD are preloaded to improve the response time of the DA command. This message indicates that neither could be loaded.
Action:
DA command is disabled and will not display data.
Check the server Job Log for messages from LOAD indicating why neither load module could be preloaded. Normally, this is caused either by insufficient private storage in the server or because neither ERBSMFI or CX10GVID are in the system link-list.
Origin:
TNOINIT
The client added to STEPLIB the library "SYS2.BB1601.BBLINK" and the error was resolved and option 2 (Active - Select an active job to monitor)
worked. Why use BBLINK of MainView on CA MAT?
Some functionality of CA Mainframe Application Tuner requires ERBSMFI:
https://www.ibm.com/support/knowledgecenter/SSLTBW_1.13.0/com.ibm.zos.r13.erbb700/erbzpgb022.htm
Obtaining SMF record data directly
z/OS RMF Programmer's Guide
SC33-7994-14
Programming Interface information
The RMF data interface service for Monitor II allows you to directly access
SMF record data from storage in real time, rather than through SMF. Application
programs can easily access SMF record data. The service provides easy access
to SMF data for application programs. SMF record type 79, and the Monitor
II header information for system CPU utilization and system demand paging
rate, are supported.
To use the RMF data interface service, invoke the module ERBSMFI with the
registers and parameters described in Parameter list contents.
Note:
Do not link the module ERBSMFI into your application
program. Code the program to call ERBSMFI at run time. How to do this depends
on the programming language you use:
In Assembler, use LOAD or LINK macros
In PL/I, use FETCH and RELEASE
In C, use the fetch built-in function
The service returns only one record to the caller,
which contains all the data. There is no 32K size limit; that is, the record
is not broken up into 32K records.
The caller must be in 31-bit addressing mode and can run unauthorized.
Note that for some of the records, Monitor I must be running. These are
as follows:
Subtype 9 - Device activity
Subtype 11 - Paging activity
Subtype 14 - I/O queuing activity
For more information about SMF record type 79, see SMF record type 79.
<END>
CA MAT is making use of this IBM module, and it resides in that load library that you needed to point to.