Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

CPF228A - Function QIBM_Q1A_ENT not registered.

'CPF228A - Function QIBM_Q1A_ENT not registered.' can be corrected by running the following command:

INZBRM OPTION(*DATA)

BRMS Licenses

The Hub and the Nodes must all have current base licenses for IBM Backup, Recovery and Media Services for i. The Hub must also have current licenses for the BRMS - Network Feature and BRMS - Advanced Feature options.

BRMS PTFs

The following PTFs must be applied to all the systems that will be part of the Enterprise Network:

  • 7.2 and later - No PTF required.
  • 7.1 - SI47935 - Note: For this release, there will also be language specific PTFs applied for each secondary language on the system.
  • 6.1 - SI47934
  • V5R4M0 - SI47933

NOTE: As stated in the PTF coverletter for BRMS PTFs:

  1. All BRMS activity must be stopped while a PTF is being applied and users must signoff and signon before using BRMS after the PTF is applied.
  2. After a BRMS PTF is applied, IBM System i Navigator (GUI) users should always uninstall and re-install the BRMS plug-in to get the latest level of BRMS code on their PCs.
  3. After a BRMS PTF is applied, IBM Navigator for i (web) users should always end and re-start the TCP/IP HTTP server to get the latest level of BRMS code for their browsers.

ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)

User Interface

BRMS Enterprise is supported through the BRMS on IBM Navigator for i (web) release 7.1 and above.  BRMS Enterprise is also supported on IBM System i Navigator (GUI) release 7.1. If the User Interface is not functioning as expected, see Troubleshooting User Interface Problems in Enterprise for more information.

Enterprise Network Connectivity

BRMS Enterprise Networks do not use traditional BRMS Network configuration, see Troubleshooting Network Connectivity Problems in Enterprise for more information.

Report Output Configuration

The spooled files that are generated for a report on a Node are stored in a remote output queue. The spooled files are then copied or moved to the Hub using a remote writer. The remote writer requires that a TCP/IP interface is configured in the operating system, an IP address on the printer side, and a Line Print Daemon (LPD) TCP/IP process running on the print server.

If reports cannot be generated for a Node, see Troubleshooting Report Problems in Enterprise for more information.

Email Notification Configuration

Email addresses can be specified for Enterprise Contacts. The Contacts can be used to indicate where to send email for Enterprise functions. For example, reports or report error notifications can be sent to the Contacts for a Node.

If emails are not being sent as expected, see Troubleshooting Email Problems in Enterprise for more information.

Time Zone Considerations

Dates and times used for scheduled activities that are initiated through the Hub, such as Report Definition run times, are relative to the Hub. For example, if the Hub is in the Central Standard Time (CST) time zone and has a Report Definition run time defined as 6:00AM, the Report Definition will run on the Node at 6:00AM CST regardless of the time zone of the Node.

User Requirements to Access Nodes

Node operations that can be initiated from a Hub require a remote connection to the Node. An RDB entry Node is required for the user profile that is initiating the operation on the Hub.

BRMS Enterprise Function Enhancements RedPaper

For a more detailed overview see BRMS Enterprise Function Enhancements Redpaper.

  • No labels