Troubleshooting › Diagnose Miscellaneous Problems

Diagnose Miscellaneous Problems

This section describes other problems that you may encounter.

Incorrect Time and Date

If the time and date stamps reported in the ReportCenter Java Task log (or any other time and date stamps generated by ReportCenter) are offset from your local time by a few hours, it is likely that the UNIX System Services time zone variable is not set correctly.

ReportCenter determines the current time and date by using the system clock and the TZ (time zone) environment variable in USS. The TZ environment variable specifies the offset between your local time and Coordinated Universal Time (UTC) (also known as Greenwich Mean Time (GMT)).

Note: The ReportCenter Java Task ignores the value specified in the user.timezone Java environment variable.

The time zone actually used by the ReportCenter Java Task appears at the start of the Java Task log.

The value for TZ is in the /etc/profile USS file. Your systems programmer updates this value to specify the time zone where your z/OS system is located. The default entry is TZ=EST5EDT.

Note: For information about how to specify a value for TZ, see IBM's Unix System Services Command Reference.

If the ReportCenter Java Task reports the wrong time or schedules its activities at the wrong time, check this variable and ask your systems programmer to set it to the correct value for your location. If it is not possible to have the value changed, you can override it by specifying a value in the prefix2/nm/reporter/usr/adaptor/Adaptor.ini ReportCenter Java Task control file. In the section headed [Adaptor] add a line with “timezone=x”, where x is the timezone specification for your location. You must restart the ReportCenter Java Task to bring the change into effect.

Example: GMT

TZ=GMT0

This is Greenwich Mean Time with 0 hours offset from UTC and no adjustment for daylight saving in the summer.

Example: EST

TZ=EST5EDT

This is Eastern (American) Standard Time, which is 5 hours behind UTC. In the summer, Eastern Daylight Time (EDT) is used. For daylight saving, the default amount (1 hour), the default start date (the last Sunday of March), and the default end date (the last Sunday of October) are used.

Example: ACT

TZ=ACT-09:30ACDT-10:30:00,M10.5.0,M3.5.0

This is Australian Central Time, which is 9.5 hours ahead of UTC. In the summer, Australian Central Daylight Time (ACDT) is used, which is 10.5 hours ahead of GMT. M10.5.0 indicates that daylight saving starts on the last Sunday of October (10 indicates the tenth month, 5 indicates the last week of the month, and 0 indicates Sunday). M3.5.0 indicates that daylight saving ends on the last Sunday of March.

Out of HFS Space

Running out of space in a ReportCenter HFS can have a variety of symptoms, depending on the file and operation that encountered the condition. Symptoms range from none at all-the Java Task just hangs-to error messages.

To see how much space is available in a file system, use one of the following commands:

• ishell and the U action code
• OMVS and the df -P /?your_ReportCenter_directory command.

Contact your UNIX System Services administrator who may need to do the following:

1. Stop the Java Task.
2. Unmount the HFS file system that runs out of space.
3. Reorganize or expand the file system.
4. Remount the file system.
5. Start the Java Task.

/DWS Display Shows Red

Sometimes, when you issue the /dws command, you notice that the following is displayed in RED:

CM31                          0      0      0       0      0
Issue the CHK command; if this does not bring it into OK (GREEN) status, then issue the RCY command.

If the RCY command has no effect, the connection between the database and the ReportCenter Java Task may be broken. This problem occurs if the database is brought down or the Warehouse service (or any other service) did not connect at initialization. From OCS, run the command REPTEST and check for any errors.

You can also verify this problem by reviewing the Adaptorxxx.log. Check for the following:

Port sharing protocol WAREHOUSE not supported by this Adaptor, cannot service Connection ID 60 to at 141.202.200.72:2101

You may see the following messages at initialization:

**************************************
Cannot establish database connection.
**************************************

To correct this problem, ensure that the database and all prerequisite and corequisite tasks are running, then cancel and restart the ReportCenter Java Task. Review the Adaptorxxx.log on startup to verify that proper connection is made. When the socket is open for connection, reissue the CHK command and the /DWS service should go into the OK (green) state.