Troubleshooting Report Problems in Enterprise GUI

Products Required to View Reports as PDFs

To view reports that were generated by the Hub the following license programs must be installed on the Hub:

57xxSS1 option 3 - Extended Base Directory Support
57xxSS1 option 33 - Portable App Solutions Environment
57xxTS1 - IBM Transform Services for i
57xxTS1 option 1 - Transforms - AFP to PDF Transform

NOTE: 57xx indicates the release of the operating system the product or option, for example 5770SS1 would indicate i 7.1.

'Save as a report' Action

The IBM i graphical-user-interface (GUI) has an action for table entries called 'Save as a report'. This action is not related to BRMS Enterprise Reports or Report Definitions, it is simply a standard action that allows the user to save the html table.

Reports generated using BRMS Enterprise are stored on the Hub as spooled files. The reports can be viewed or saved as PDFs using the 'View reports' action for the Node or for the Report Definitions defined for a Node.

TCP/IP LPD Server on the Hub

Since report generation on a Node uses a remote output queue associated with the Hub, the TCP/IP LPD server must be active on the Hub. If the TCP/IP server is not active on the Hub, the writer that uses the remote output queue on the Node will time out and the spooled files for reports will not moved to the Hub. To determine if the LPD server is active, run the following commands:

WRKACTJOB SBS(QSYSWRK) JOB(QTLPD*)

If jobs are found then the TCP/IP LPD server is active.
If no jobs are found then the following command can be run to start the TCP/IP LPD server:

STRTCPSVR SERVER(*LPD)

Verify Remote Spool Activities are Functioning from the Node to the Hub

Verify that the remote writer is functioning properly on the Node run the following commands.

On the Hub, create an output queue:

CRTLIB LIB(TESTLPR) CRTOUTQ OUTQ(TESTLPR/OUTQ)

On the Node, send a spooled file to the Hub:

DSPJOBLOG OUTPUT(*PRINT) LPR RMTSYS(xxxxxxx) PRTQ('TESTLPR/OUTQ') FILE(QPJOBLOG) SPLNBR(*LAST) DESTTYP(*AS400) TRANSFORM(*NO)

where xxxxxxxx is the Hub name

On the Hub, check the output queue to verify the spooled file was transferred:

WRKOUTQ OUTQ(TESTLPR/OUTQ)

Verify Q1ABRMNET and Q1ABRMENT subsystems are functioning

End and restart the Q1ABRMNET and Q1ABRMENT subsystems.

ENDSBS SBS(Q1ABRMNET) OPTION(*IMMED)ENDSBS SBS(Q1ABRMENT) OPTION(*IMMED)

STRSBS SBSD(QBRM/Q1ABRMNET) STRSBS SBSD(QBRM/Q1ABRMENT)

Reports Seem to Take Too Long to Run

If reports seem to loop/hang when the are run, check the remote writer spool job on the Node:

WRKACTJOB JOB(QZNOD*)->5->F17->10

If you see these messages, it can indicate the LPD server is not running on the Hub.

CALL QSYS/QSPWTRM1
Remote host system rejected the open attempt.
Send request failed for spooled file QP1ALG.
Remote host system rejected the open attempt.
Smote host system rejected the open attempt.
...

Start the server on the Hub by running:

STRTCPSVR SERVER(*LPD)

Report Fails with Message BRM8014 Reason Code 1

If a report fails with BRM8014 reason code 1, it indicates that the report ran successfully on the Node but the spooled files generated by the report could not be transferred back to the Hub.

A remote writer is used by BRMS to transfer spooled files from the Node to the Hub. The remote writer runs under user profile QUSER on the Hub and requires access to objects in library QUSRBRM. By default, library QUSRBRM has *EXECUTE public authority. If the public authority for library QUSRBRM is changed to a more restrictive authority, it will cause Enterprise reports to fail with message BRM8014 reason code 1. If it is not possible to set the public authority to *EXECUTE, *EXECUTE private authority for user profile QUSER can be added to library QUSRBRM.

If QUSER has sufficient authority to library QUSRBRM, take the following actions to help determine what is causing message BRM8014 reason code 1:

BRM8014 contains the job information for the remote writer job on the Node that was trying to transfer the spooled files to the Hub. Use the job information to determine whether the remote writer transferred the spooled files to the Hub by running the following command on the Node:

WRKJOB JOB(<jobNumber>/<jobUser>/<jobName>)

If the remote writer job cannot be found, run the following commands on the Node so the remote writer job log will not deleted when the job ends:

CHGJOBD JOBD(QSPLRMTW) LOG(4 00 *SECLVL)

Re-run the report for the Node.

WRKJOB JOB(<jobNumber>/<jobUser>/<jobName>)

If the job log for the remote writer job indicates there was a failure, use the information from the failure to diagnose the problem.
If the job log for the remote writer job indicates the spooled files were transferred, run the following commands on the Hub:

CHGJOBD JOBD(QTMPLPD) LOG(4 00 *SECLVL)
ENDTCPSVR SERVER(*LPD)
STRTCPSVR SERVER(*LPD)

Re-run the report for the node.

The LPD server job on the Hub that processed the remote writer requests from the Node needs to be checked for errors. To see the job log for the LPD server job, run the following commands on the Hub:

WRKSPLF SELECT(QTCP)

If the job log for the LPD server job indicates there was a failure, use the information from the failure to diagnose the problem.
If the job log for the LPD server job indicates the spooled files were received, run the following commands on the Hub to diagnose the problem:

DSPMSG MSGQ(QSYSOPR) DSPLOG

Report Fails with Message BRM8014 Reason Code 205

If a report fails with BRM8014 reason code 205, it indicates spooled files that have been generated for the report cannot be found. Verify that the output queue specified for the Output queue field in the system policy is not set up as follows:

There is not an active writer configured to the output queue.
The output queue is not a remote output queue.

Report Fails with Message BRM1014 Reason Code 1

If the spooled file generated on the node is held, a BRM1014 RC1 may be logged. The command WRKSPLFA can be used to determine the status of the spooled file. Ensure that the printer file used to generate the spooled files is not been held.

To ensure all BRMS print files are not held, run the following command:

CHGPRTF FILE(QBRM/*ALL) HOLD(*NO)

Report Fails to be emailed even though the reports are genrated in the hub outq. If reports are generated successfully on the hub, but do not get emailed to the contacts specified, here are some items to check:

On the hub, review the Q1AZGENRPT joblog. Look for message indicating a problem. For instance, look for messages BRM8014, TCP5090, etc
If TCP5090 is logged, this indicates that QBRMS is not enrolled in SMTP Local Mailbox Directory. Use ADDUSRSMTP to add QBRMS to the SMTP local mailbox directory.
If BRM8014 is logged, review the reason code and Recovery section of this message. Verify the public authority is *EXECUTE for library QUSRBRM or user profile QUSER has *EXECUTE authority for library QUSRBRM. The recovery will also reference a joblog on the node to review. If it refers to a QRWTSRVR job, you many need to change the following job description on the node to generate joblogs for QRWTSRVR jobs.
- CHGJOBD JOBD(QDFTSVR) LOG(4 00 *SECLVL) LOGCLPGM(*YES)
- Review the joblog on the node to determine root cause.
- If BRM4040 is logged in the QRWTSRVR joblog, QBRMS does not have authority to a particular function that is needed. One way to resolve authority issues for QBRMS is to run the following on the problem node(s):
  - SETUSRBRM USER(QBRMS) USAGE(*ADMIN)

Additional Resources for Remote Output Queues and Remote Writers

Rochester Support Center knowledge base document - Configuring a RMTOUTQ to Send SPLFs from one IBM System i to Another using LPR/LPD.