|
|
|
This section is common to all problems. It explains how to collect the diagnostic data required by the other tasks.
No single problem requires all of this data. Collect only what is required by your specific problem or what is requested by Technical Support.
Important! Ensure that all information and diagnostic data that you provide to Technical Support is collected from the same incident.
To collect diagnostic data from CA NetMaster products, use the OCS ST command on the ReportCenter Control Region or Data Region.
This shows what CA NetMaster products run in the region, their version or release, and their Service Pack levels.
REPTEST is a self-test facility that verifies ReportCenter components. You can run it from the 3270 or WebCenter, whatever is more convenient.
To run REPTEST from the 3270, use the OCS command REPTEST. This runs all component tests.
Place your cursor on any message number, and then press F1 (Help) for more information.
REPTEST ? displays the separate tests available.
To write the test output to the activity log, use SUB BLOG REPTEST.
To write the test output to a separate SYSOUT file, for printing or saving to a data set, use LOGSWAP; SUB BLOG REPTEST; LOGSWAP
then manage the SYSOUT file using SDSF.
To run REPTEST from WebCenter
The Report Activity Status page appears.
You can view the Java Task log from the 3270 or WebCenter.
Viewing the log from the 3270 is recommended for troubleshooting.
To view the Java Task log from the 3270, logon to TSO, and issue the following OMVS command:
obrowse /?log_files_HFS_directory/nm/reporter/usr/logs/Adaptor001.log
To list your log files HFS directory, use OCS command REPTEST INST and look for the following message:
WRSTIN01 HFS Java Task logs: /u/users/abcde/nm/nm01
Using obrowse displays the entire log file. This file can contain log data from many different runs of the Java Task. The most recent run is at the end of the log.
A new run starts with lines similar to the following:
************************************************************ **** ReportCenter Log Number n **** System initialised at 2007-Jul-31 19:41:25.449 2007-Jul-06 00:26:32.726 Using timezone GMT-04:00, built from "tz=EST5EDT" 2007-Jul-06 00:26:32.727 Starting ReportCenter Java Task; version nn.n
To find the start of the latest run, browse the file, go to the end, and find (backwards) the first starting ReportCenter Java task.
To view the Java Task log from WebCenter, select ReportCenter, Java Task Log to display the end of the log.
Because the log may be very long, only the most recent entries are displayed.
For this reason, viewing the Java Task log from the 3270 is more useful for troubleshooting.
Java code PTF levels appear near the top of the Java Task log. Find the start of the latest run and look for messages such as the following:
adaptor.jar PTF level is base (compile date 2006-Mar-31). datawarehouse.jar PTF level is base (compile date 2006-Jun-01). reportgenerator.jar PTF level is base (compile date 2006-May-31). reportservices.jar PTF level is base (compile date 2006-May-31).
You can view the CA NetMaster Activity log from the 3270 or WebCenter.
To view the CA NetMaster activity log, do one of the following:
You can also type HELP from the log.
Notes:
To view the CA NetMaster activity log, select Utilities, View activity log.
The REPORTCENTER Customizer Ilog can be viewed only from the 3270.
To view the REPORTCENTER Customizer Ilog
The Customizer : Parameter Groups menu appears.
$WR REPORTCENTER ReportCenter Control Region
The Customizer : Initialization Log appears.
Note: Do not confuse the CA NetMaster activity log with the ReportCenter Customizer ILog. They are both produced by the CA NetMaster region, and messages that appear on one may also appear on the other; however, only the ILog contains the complete details of what happens when the ReportCenter parameter group performs its work.
You can obtain the DB2 version from your DB2 Database Administrator.
The Datacom version is dispayed on the Datacom MUF JOBLOG.
Look for message DB00215I.
Example: Display CA Datacom/AD Version
DB00215I - CA DATACOM/DB SYSTEM VERSION: 10.0 AT SERVICE PACK: AD04 DB00215I - Advantage CA Datacom/DB Database r11 at service pack: SP02
The REPTEST command lists the initial content of the STDOUT and STDERR HFS files if they exist, and if the CA NetMaster region can read them. If you do not want all of the REPTEST output, use OCS command REPTEST STC and look for message numbers WRSTJF03 and WRSTJF13.
Example: STDOUT and STDERR HFS Files
WRSTJF03 Job DENMX2JV produced the following STDOUT output:
WRSTJF03 * DENMX2JV NetMaster ReportCenter USS Environment Variable WRSTJF03 * DENMX2JV PATH set to /bin:/sys/javatm2/v1r4m2/usr/lpp/ja WRSTJF03 * DENMX2JV LIBPATH set to /lib:/sys/usr/lpp/db2/db2710/lib WRSTJF03 * DENMX2JV STEPLIB set to DB2.DB2710.SDSNEXIT:DB2.DB2710.S WRSTJF03 * DENMX2JV DB2SQLJPROPERTIES set to /sys/usr/lpp/db2/db271 WRSTJF03 * DENMX2JV LD_LIBRARY_PATH set to /sys/usr/lpp/db2/db2710/ WRSTJF13 Job DENMX2JV produced the following STDERR output: WRSTJF13 * java version "1.4.2" WRSTJF13 * Java(TM) 2 Runtime Environment, Standard Edition (build WRSTJF13 * Classic VM (build 1.4.2, J2RE 1.4.2 IBM z/OS Persistent
If this does not work, or you need to see the full contents of these files, log on to TSO, and use the following OMVS commands:
obrowse /?runtime_control_files_HFS_directory/nm/reporter/usr/adaptor/stderr.txt obrowse /?runtime_control_files_HFS_directory/nm/reporter/usr/adaptor/stderr.txt
To list your runtime control files HFS directory, use OCS command REPTEST INST and look for the following message:
WRSTIN01 HFS Working Data: /u/users/abcde/nm/nm01
To display the contents of an HFS file, obtain the full path name of the file and use the TSO OMVS command obrowse.
To list an HFS directory, you can issue some USS commands from OCS, if the CA NetMaster region is set up correctly.
Example: List HFS Directory
USS ls -l /?directory_pathnam
| Copyright © 2012 CA. All rights reserved. |
|