Potential Situations and Solutions

The following table lists problems and offers solutions for problems you may encounter when you are using SmartMode.

Problem

Possible solutions

SmartMode cancels necessary reports.

You can do one of the following:

Have the request submitted by an ID with override privileges.

Raise the threshold.

Turn governing off or set governing to Advise to continue training for that database.

SmartMode displays a message that the SU job is down.

Try the following:

If the SU job is not down, make sure that the dataset name listed in ddname SMARTSU in the FOCUS startup procedure is the same as that name listed in the SU JCL at ddname FOCSU.

Make sure that the communications dataset is allocated to ddname SMARTSU in the FOCUS startup procedure or is listed in the GKSINK ERRORS file.

SmartMode is not collecting records in the Collections database.

You can do one of the following:

Make sure that the all the SM files are properly allocated to the SU job.

Make sure the SMARTSU ddname is allocated in the FOCUS startup procedure or in the GKSINK ERRORS file.

The SU job may not be down, but SmartMode is still unable to communicate with it. Enter ? SU SMARTSU from the FOCUS prompt and look for an error message.

The SU job may appear to be executing, but it is waiting for data sets.

SmartMode monitors, but data is garbled and/or unreadable in SMQUERY.

Make sure that the correct Master File Descriptions exist on the SU sink machine and that they match those found on the source machine.

For more information on improving SU performance, see the Simultaneous Usage for OS/390 and MVS User's Manual.

Information Builders

Problem	Possible solutions
SmartMode cancels necessary reports.	You can do one of the following: Have the request submitted by an ID with override privileges. Raise the threshold. Turn governing off or set governing to Advise to continue training for that database.
SmartMode displays a message that the SU job is down.	Try the following: If the SU job is not down, make sure that the dataset name listed in ddname SMARTSU in the FOCUS startup procedure is the same as that name listed in the SU JCL at ddname FOCSU. Make sure that the communications dataset is allocated to ddname SMARTSU in the FOCUS startup procedure or is listed in the GKSINK ERRORS file.
SmartMode is not collecting records in the Collections database.	You can do one of the following: Make sure that the all the SM files are properly allocated to the SU job. Make sure the SMARTSU ddname is allocated in the FOCUS startup procedure or in the GKSINK ERRORS file. The SU job may not be down, but SmartMode is still unable to communicate with it. Enter ? SU SMARTSU from the FOCUS prompt and look for an error message. The SU job may appear to be executing, but it is waiting for data sets.
SmartMode monitors, but data is garbled and/or unreadable in SMQUERY.	Make sure that the correct Master File Descriptions exist on the SU sink machine and that they match those found on the source machine.