Initial Setup Concepts

To enable BRMS SQL services, the supporting IBM i BRMS PTFs needs to be applied first, followed by running this command to install the new services: INZBRM OPTION(*SQLSRVINZ) 

7.5 SI80273, 7.4 SI780272, 7.3 SI80271

Step 1 : Contacts

Contacts are used for a variety of notifications including reports or errors encountered while generating reports so they need to be created first using the SQL procedure QUSRBRM.ADD_ENTERPRISE_CONTACT.

Example:

CALL QUSRBRM.ADD_ENTERPRISE_CONTACT(

CONTACT_USER_NAME=> 'ADMIN',

EMAIL_ADDRESS=> 'JOHN.DOE@MYCOMPANY.COM',

FIRST_NAME=> 'JOHN',

LAST_NAME=> 'DOE',

PRIMARY_PHONE=> '111-222-3333',

SECONDARY_PHONE=> '444-555-6666',

DESCRIPTION=> 'BRMS Enterprise HUB Administrator' )

Step 2: Establish Communication

• BRMS Enterprise communications use TCP/IP communications and relational database (RDB) entries for all of its network operations which must be configured by your site security administrator. BRMS does not set up communication or create the necessary systems configuration. BRMS expects that the communication setup has been done by the site security administrator.

• BRMS connectivity can be checked by running the Initialize BRMS (INZBRM) command with *VFYSYS, *VFYENT specified for the Option (OPTION) parameter. For more information please reference Verify BRMS Network and BRMS Enterprise Network Connections

Step 3: Nodes

The systems being monitored by the Hub are called Enterprise Nodes. The Enterprise Network is comprised of Nodes that can be stand-alone BRMS systems, part of a BRMS Network or any combination of stand-alone and BRMS Networked systems. To create a new Node use the SQL procedure QUSRBRM.ADD_ENTERPRISE_NODE.

Example:

CALL QUSRBRM.ADD_ENTERPRISE_NODE (

SYSTEM_NAME=> 'APPN.SYSTEM1',

RELATIONAL_DATABASE_NAME=> 'SYSTEM1',

PRIMARY_CONTACT=> 'PRIMARY',

SECONDARY_CONTACT=> 'BACKUP',

HUB_OUTPUT_QUEUE_LIBRARY=> 'BRMREPORTS',

HUB_OUTPUT_QUEUE=> 'BRMREPORTS',

DESCRIPTION=> 'CENTRAL PRODUCTION SYSTEM')

Step 4: Report Definitions

Report Definitions define how and when a report will be generated for a Node. The Report Definition can be run manually or it can be scheduled to run at defined intervals. To create a new Report definition use the SQL procedure QUSRBRM.ADD_ENTERPRISE_REPORT_DEFINITION.

Example:

CALL QUSRBRM.ADD_ENTERPRISE_REPORT_DEFINITION(

REPORT_DEFINITION=>'DAILY',

SYSTEM_NAME=>'APPN.SYSTEM1',

GENERATION_TIME=> '100000',

COMMAND=> 'STRMNTBRM',

FREQUENCY_INTERVAL=> 'WEEKLY',

WEEK_DAYS=>'MON TUE WED THU FRI SAT SUN',

SEND_ERROR_EMAIL=> 'YES',

NUMBER_REPORTS=> '7',

SEND_REPORT_EMAIL=>'YES',

DESCRIPTION=> 'DAILY STRMNTBRM')

Step 5: Verify Report Definition Runs Manually (Optional)

Report Definitions can define how and when a report will be generated for a Node. The Report Definition can be run manually or it can be scheduled to run at defined intervals. To run Report Definition manually, use the SQL procedure QUSRBRM.RUN_ENTERPRISE_REPORT_DEFINITION.

Example:

CALL QUSRBRM.RUN_ENTERPRISE_REPORT_DEFINITION(

REPORT_DEFINITION=>'DAILY',

SYSTEM_NAME=>'APPN.SYSTEM1')