Start the ReportCenter Java Task

Running the ReportCenter Java Task › Start the ReportCenter Java Task

Start the ReportCenter Java Task

Start the ReportCenter Java Task from the MVS console. Be aware that this started task runs in the USS environment and may generate several spawned tasks.

What to Look For

Consider the following:

The task must remain active, that is, it does not fail with a JCL error or terminate itself after a few minutes.
If the task remains active, you must also ensure that it initialized correctly and connected to the database. To do this, enter the REPTEST command from OCS in the ReportCenter control region. This runs tests on a variety of ReportCenter components.
Successful tests indicate the following:
- The ReportCenter Java Task initialized successfully.
- The ReportCenter Java Task is communicating with the ReportCenter control region.
- The JDBC connection between the ReportCenter Java Task and the ReportCenter database is active. If a test produces errors, then you must investigate and correct the causes. You may need to update and reapply the REPORTCENTER parameter group, and make changes to external components such as databases, HFS directories and permissions, or security.
  The REPTEST error messages provide more help. Place your cursor on an error message and press F1 (Help).
  
  Note: The tests may produce large numbers of Java Task error messages at this initial stage. Common implementation problems can cause many errors to result from a single simple cause.
  
  Do not proceed with any additional tasks until all tests complete successfully.

Common Problems

For most ReportCenter Java Task problems, you need to look for further error details. Depending on the nature of the problem, error messages can appear in some or all the following locations:

The ReportCenter Java Task UNIX STDOUT and STDERR HFS files
Use the REPTEST JAVAFW OCS command or browse the following files:
```
?prefix2/nm/reporter/usr/adaptor/stderr.txt
?prefix2/nm/reporter/usr/adaptor/stdout.txt
```
The ReportCenter Java Task log HFS file
Browse the ?prefix2/nm/reporter/usr/Adaptornnn.log file, but be aware that if the failure is early, this file may not be created or updated yet.
The SDSF system console log
The ReportCenter Java Task SDSF job log

Note: The activity log of the region does not contain any information from the ReportCenter Java Task. The region and the task are in separate address spaces.

Task Fails with JCL Error

The most frequent causes of JCL errors are the following:

At least one of the path names specified in the JCL does not exist on the system on which the task started. Verify that the path names are correct, mount the file system if necessary, and start the task on the correct system.
The Java command cannot be invoked, as indicated by the following STDERR message:
```
FSUMnnnn java not found
```
Review and correct the specification of the Java command directory path name. From this directory, enter java -version.

Task Fails with MVS Abend

This happens very infrequently, usually caused by underlying error conditions in the MVS software components such as LE, JVM, USS, DBMS, or security system.

Task Terminates with No External Error

The most frequent causes of the ReportCenter Java Task failing include the following. These are usually indicated in the ReportCenter Java Task log.

Class not found

Review the specification of the SMP/E target library directory, the database JDBC directory, and all class file names. ReportCenter specifies its Java class path explicitly at runtime with the -cp option. It does not set or use the CLASSPATH environment variable. To see the directories and files in the class path, browse the generated Adaptor.bat file.

System class not found may indicate an error with the JVM implementation. Verify the correct installation and implementation of your mainframe Java product.

ClassNotFoundException indicates that the class is not found at runtime.

NoClassDefFoundError indicates that the class is found at runtime; however, the class imports another class, which, while present at compile time, is not found at runtime.

User ID not authorized

If the associated user ID is not defined correctly to your security system, errors or other failures can result.

Unknown host exception error

A Java getLocalHost function fails to return the IP address of the local host, as indicated by a message similar to the following in the ReportCenter Java Task log:

Adaptor initialisation failed with exception java.net.UnknownHostException ?hostname

This often indicates problems with the name server setup. Creating or updating the /etc/hosts file with the IP address and name of the local host usually corrects this problem.

ReportCenter Java Task terminates

Indicated by a message similar to the following in the ReportCenter Java Task log:

*****************************************
Java framework terminating due to error: error details
Please correct the condition and restart.
*****************************************

The ReportCenter Java Task terminates when it detects a fatal condition that stops it doing any useful processing. Usually, these are database-related conditions. ReportCenter terminates to avoid wasting resources on repeated and unsuccessful database connection attempts. Following are some common terminal conditions. Rectify the condition, and start the task again.

DBMS (DB2 subsystem or CA Datacom MUF) is not active.
ReportCenter database is not defined correctly or accessible.
Required component such as RRS or CA Datacom Server is not active.
User ID is not permitted to access database. Look for SQL -551 errors.
RRS security setup errors are encountered-'RRSAF not authorized.'
Serious JDBC errors are encountered.
IP Sockets interface is unavailable or is experiencing problems.

USS Commands

A few of the most useful commands for ReportCenter problem diagnosis are described here.

Most UNIX shell commands are accepted. Useful commands include the following:

cd and pwd (changes directory and displays current directory)
obrowse and oedit (browses and edits file)
ls and ls -l (lists directories and files)
grep, egrep, and fgrep (finds text in a file)
chmod (changes the access permissions of a file)
df -P directory-mount-point (shows the percentage space used and available in the HFS file system)

Note: You may need changes to your TSO user ID or profile to access these commands; if so, contact your systems programmer.

obrowse Command

Use this command to browse an HFS file.

This command has the following format:

obrowse pathname/file

Example: obrowse Command

obrowse /?ics_prefix2/nm/reporter/wr76/usr/adaptor/Adaptor.ini

ishell Command

Use this command to display a selection list of the objects in a directory. You can enter Browse, Edit, List, and other commands next to an object.

This command has the following format:

ishell directory-pathname

Example: ishell Command

To see how many logs files there are and select one for browsing, enter the following command:

ishell /u/users/ca/nm/reporter/wr76/usr/logs

Example: ishell Command

To see the Java Task control and output files, enter this command:

ishell /u/users/ca/nm/reporter/wr76/usr/adaptor

omvs Command

Use this command to invoke the shell command line interface.

This command has the following format:

omvs

Browse the ReportCenter Java Task Log

You can browse the log by using WebCenter or USS.

To browse the Log using WebCenter, select ReportCenter, Java Task Log from the WebCenter Menu. For space reasons, this shows only the most recent entries in the log.

To browse the log using USS, enter the following command from TSO or OMVS:

obrowse /?ics_prefix3/nm/reporter/wr76/usr/logs/Adaptor001.log

obrowse has the advantage of displaying the entire log file, and being more easily searchable.

Notes:

For information about z/OS UNIX Interactive Interfaces and z/OS UNIX File Systems, see IBM's Introduction to the New Mainframe: z/OS Basics.
For more information about UNIX System Services, see IBM's UNIX System Services Command Reference and UNIX System Services User Guide.