TN00 Messages

TN0001E TUNLEVEL member of CEESSAMP not found -- CA MAT terminating

TN0001E Check the CA MAT startup exec

Reason:

CA Mainframe Application Tuner will not initialize. The TUNLEVEL member of CEESSAMP is required for CA Mainframe Application Tuner to operate properly. This member is missing.

Action:

Verify that the procedure used to invoke CA Mainframe Application Tuner from TSO contains an allocation for DDname TUNSAMP and that the data set prefix.CEESSAMP is allocated to TUNSAMP and contains the member TUNLEVEL. If the member is not present, contact Customer Support.

Origin: TUNC0010

TN0002I Content-sensitive help is being initialized

Reason:

The first time CA Mainframe Application Tuner is started for a TSO user, CA Mainframe Application Tuner constructs the content-sensitive help database. This database is used throughout CA Mainframe Application Tuner to provide information and appropriate actions for the analysts.

Action:

None

Origin: TUNC0010

TN0003I Content-sensitive help is being updated (TPNnnnn)

Reason:

When maintenance is applied to the content-sensitive help database, CA Mainframe Application Tuner updates the tables that allow access to the information. The maintenance level is reported in parentheses as a PTF number; for example, (TPNnnnn).

These tables are used throughout CA Mainframe Application Tuner to provide information and actions for the analyst.

Action:

None.

Orligin: TUNC0010

TN0004I Please wait while the User Information File is initialized.

TN0004I This may take a few minutes.

Reason:

The first time a user starts a TSO session, permanent tables are created in the User Information File (UIF).

These tables are used by CA Mainframe Application Tuner to store and retain user information from session to session.

Action:

None.

Origin: TUNC0010

TN0005I User Information File maintenance update in progress (TPNnnnn)

Reason:

When applied maintenance changes data stored in the User Information File, the TSO session also updates the data in the same tables. The maintenance level is reported in parentheses as a PTF; for example, (TPNnnnn).

These tables are used by CA Mainframe Application Tuner to store and retain user information from session to session.

Action:

None.

Origin: TUNC0010

TN0006E Table create requested for 'table' is not known

Reason:

While creating internal tables in the User Information File, an error occurred. The table name specified is not one of the known tables.

Action:

Initialization terminates. Contact Customer Support.

Origin: TUNC0020, TUNC0030

TN0007I Migration of User Information File in progress from release xxx

Reason:

When converting from a previous release, all maintenance applied to the User Information File from the previous release (xxx) is migrated to the new release.

Action:

None.

Origin: TUNC0070

TN0008E User Information File allocation error

TN0008E LISTDSI error return is: rrrrrrrrrr

Reason:

An error occurred while creating the User Information File. The error from LISTDSI is reported in the second line of the message as rrrrrrrrr.

Action:

Initialization terminates. Contact Customer Support.

Origin: TUNC0090

TN0009E Open failed for Content-Sensitive Help table RC=cc RS=rr

Reason:

While initializing content-sensitive help, a severe error occurred. The return code (RC=cc) and reason code (RS=rr) are reported.

Action:

Initialization terminates. Contact Customer Support.

Origin: TUNC0010

TN0010E Unable to allocate tuntable on volser (trks tracks)

Reason:

While allocating the User Information File a severe error occurred. This error is produced when the volume for the data set is full.

Action:

Initialization terminates. Determine the reason the data set cannot be allocated on the requested volume.

Origin: TUNC0090

TN0011E Syntax error in record: record

Reason:

While producing the mapping table, an input address was encountered that did not contain a hexadecimal number.

Action:

The map table build terminates. Correct the address and ensure it contains only hexadecimal characters (0-9, A-F).

Origin: TUNC1080

TN0012E Profile ‘profile’ not found -- batch reporter terminating

Reason:

The batch reporter could not locate the profile name for the requested report. The name of the profile is in quotation marks; for example, ‘profile’.

Action:

The Batch Reporter terminates. Ensure the profile name exists in the Monitor Definition panel (option 1). If so, contact Customer Support.

Origin: TUNC1090

TN0013E Monitor data set 'data set' is not found or not available

Reason:

The batch reporter could not locate the data set containing the samples for the requested reports. The name of the data set is in quotation marks; for example, 'data set'.

Action:

The Batch Reporter terminates. Determine if the data set that contains the samples exist and is available.

Origin: TUNC1090

TN0014E Monitor data set 'data set' does not have the proper DSORG

Reason:

While running batch reports, CA Mainframe Application Tuner determined that the data set containing the samples for the requested reports did not have correct DCB attributes. The name of the data set is in quotations marks; for example, 'data set'.

This occurs when sampling has not taken place and the data set is empty.

Action:

The Batch Reporter terminates. Determine that the sampling did take place and that the data set contains data.

Origin: TUNC1090

TN0015E Browse failed with RC=rr

Reason:

When attempting to invoke ISPF Browse to view a listing data set, CA Mainframe Application Tuner received a non-zero return code from Browse. The return code from Browse is indicated by rr.

This usually occurs when the listing member that CA Mainframe Application Tuner is attempting to browse does not exist.

Action:

Browse terminates. Determine that the member being browsed is registered by CA Mainframe Application Tuner in the correct data set.

Origin: TUNC3300

TN0016E Profile 'profile' not found

TN0016E Batch reporter terminating

Reason:

While attempting to produce batch reports CA Mainframe Application Tuner found that the profile requested did not exist in the User Information File.

Action:

The batch reporter terminates. Determine that the profile exists in the Monitor Definition panel (option 1) for the user and resubmit the report request.

Origin: TUNC3700

TN0017E Allocation failed for DDname TUNREPT with an RC of 'rc'

TN0017E CA MAT batch report generation is terminated

Reason:

While attempting to produce batch reports, CA Mainframe Application Tuner was not able to allocate the SYSOUT data set defined by ddname TUNREPT. The allocation failed with the return code indicated in quotation marks; for example, 'rc'.

Action:

The batch reporter terminates. Check the return codes from the ALLOCATE TSO command, correct the problem and resubmit the report request. Contact Customer Support if the problem persists.

Origin: TUNC3700

TN0018W Content-sensitive help maintenance is being deferred

TN0018W TUNCSHP table is in use by another user

Reason:

While attempting to update the content-sensitive help database, CA Mainframe Application Tuner determined that the data set was opened by another user.

Action:

The update is deferred. No action is required. CA Mainframe Application Tuner will attempt to update the database the next time a TSO session is invoked.

If an immediate update is required, determine who is active in the content-sensitive help application (option 6), have them exit and restart your TSO session.

Origin: TUNC5020

TN0019E Error opening TUNCSHP table

Reason:

When attempting to update the content-sensitive help database, CA Mainframe Application Tuner detected an error when issuing the open for the database.

Action:

The update of content-sensitive help terminates. Contact Customer Support.

Origin: TUNC5020

TN0020W Content-sensitive help use is suspended for this session

Reason:

When attempting to update the content-sensitive help database, CA Mainframe Application Tuner detected an error when issuing the open for the database.

Action:

The update of content-sensitive help terminates. Content-sensitive help is not available until the problem is corrected. Contact Customer Support.

Origin: TUNC5020

TN0021E Error loading input data

Reason:

While processing a request to create reports, CA Mainframe Application Tuner incurred an error loading the monitor data set.

Action:

The Batch Reporter or the online analyzer terminates.

This error could occur for several reasons. The job log from the reporter should have other error messages associated with this failure. If you cannot correct the problem after looking at these messages, contact Customer Support.

One common error is a lack of Virtual memory. CA Mainframe Application Tuner requires an address space with 4.5M below the line and 32M above the line of virtual storage.

Origin: TUNRANAL

TN0022W Monitor data set is empty

Reason:

While processing a request to create batch reports, CA Mainframe Application Tuner found that the monitor data set had no samples.

Action:

The batch reporter terminates. Check the messages in the system log to determine what happened. If necessary, run the monitor again and then resubmit the batch reports. The monitor may have either not run or ended abnormally.

Origin: TUNRANAL

TN0023E Error attaching tables

Reason:

While processing a request to create batch reports, CA Mainframe Application Tuner encountered an internal error

Action:

The Batch Reporter terminates. Contact Customer Support.

Origin: TUNRANAL

TN0024E - verb - is an unknown tutorial request in line nn

Reason:

While processing the tutorial for CA Mainframe Application Tuner, an invalid request was presented to the tutorial processor.

Action:

The tutorial terminates. Contact Customer Support.

Origin: TUNTUTOR

TN0025E SET statement in line nn is missing an equal sign

Reason:

While processing the tutorial for CA Mainframe Application Tuner a statement that assigned a value did not contain the equal sign (=).

Action:

The tutorial terminates. Contact Customer Support.

Origin: TUNTUTOR

TN0026I Global Information File update in progress (TPNnnnn)

Reason:

When maintenance is applied to one of the tables maintained in the Global Information database, CA Mainframe Application Tuner updates the tables that allow access to the information. The maintenance level is reported in parentheses as a PTF number; for example, (TPNnnnn).

These tables are used throughout CA Mainframe Application Tuner to provide information and actions for the analyst.

Action:

None.

Origin: TUNC9300

TN0027I Global Information File is being initialized (TPNnnnn)

Reason:

These tables are used throughout CA Mainframe Application Tuner to provide information and actions for the analyst.

Action:

None.

Origin: TUNC9300

TN0028I Migration of User Information File from xxxxx to User Information File yyyyy in progress

Reason:

This message indicates that the User Information File (xxxxx) specified in the ISPF Profile for CA Mainframe Application Tuner is different than the UIF (yyyyy) specified in the Global Information File (GIF).

This can occur when more than one installation exists (for example, a production system and a test system), and a different UIF is to be used for each system. This ensures that the UIF and GIF are correctly correlated.

Action:

None.

Origin: TUNC0090

TN0029E Unable to create batch report - no CSV File.

TN0029E Use Global TSO Client to create batch report.

Reason:

While attempting to produce batch reports CA Mainframe Application Tuner was unable to allocate a CSV file needed to create reports. This can be caused by the absence of a monitor profile entry and/or absence of a valid PREFIX needed to allocate the file.

Action:

The batch reporter terminates.

To create a batch report, use the Global TSO Client (Primary Option G). Select option 1 (Monitor), locate the profile, and issue the B (Batch) line command.

For TUNCALL requests (Open API), you may specify a valid prefix by using the PREFIX() keyword.

Origin: TUNC3700

TN0030I No matching transactions/tasks - check selection criteria

TN0030I All tasks will be reported

Reason:

The transactions and/or tasks specified in the Batch Reporting of CSV Reporting criteria panels do not match any of the transactions or tasks found in the monitor data.

Action:

All tasks or transactions will be reported.

Check that the specified selection criteria are correct. Verify that any wildcard characters are used correctly ( + to match any character, * to match a string of characters).

Origin: TUNC3700

TN0031E Monitor data set contains no samples - batch reporter terminating

Reason:

There were no samples contained in the monitor data set. This may be a result of the transactions or tasks selected in the Batch or CSV Reporting panels.

Action:

The batch reporter terminates. Review the transaction and/or task selection criteria and re-submit the report.

Origin: TUNC3700

TN0032E Output data set allocation failed with an RC of 'rc'

TN0032E CA MAT batch report generation is terminated

Reason:

While attempting to produce batch reports, CA Mainframe Application Tuner was not able to allocate the CSVOUT data set. The allocation failed with the return code indicated in quotation marks; for example, 'rc'.

Action:

The batch reporter terminates.

Check the return codes from the ALLOCATE TSO command, correct the problem and resubmit the report request. Contact Customer Support if the problem persists.

Origin: TUNC3700

TN0033I Output being written to data set 'data set name'

Reason:

This indicates the name of the data set which will contain the CSV information (for either a batch report or CSV export report).

The default value is prefix.userid.profile.CSV.

Action:

None.

Origin: TUNC3700

TN0034E Error in CA MAT Batch Print utility, rc=rc, rs =rs

Reason:

While attempting to produce batch reports, there was an error with the Batch Print utility program. This program converts the CSV input file into a formatted batch report.

Action:

The batch reporter terminates. Record the return code (rc) and reason code (rs). Contact Customer Support

Origin: TUNC3700

TN0035W Sample count of sssssss may be statistically invalid

Reason:

While processing a request to create batch reports, CA Mainframe Application Tuner found that the monitor data set had fewer samples than would normally be considered statistically valid.

Action:

The batch reporter continues. Check the messages in the system log to determine if anything happened. Check the monitoring criteria and if necessary run the monitor again and then resubmit the batch reports. Due to system activity the job being monitored may have been inactive for most of the monitor duration.

Origin: TUNRANAL

TN0036E Monitor file not found

TN0036E Batch reporter terminating

Reason:

While attempting to produce batch reports,CA Mainframe Application Tuner found that the monitor data set does not exist.

Action:

The batch reporter terminates.

Verify that the monitor file data set name is correct. If the correct data set exists, use the Monitor History F line command to specify the data set name. Resubmit the report request.

Origin: TUNC3700

TN0037I TUNBATPM report parameters in effect

Reason:

This indicates that the batch report parameters contained in UTRPARM member TUNBATPM are in use.

These parameters are used for generating APC batch reports.

Action:

None.

Origin: TUNC3700

TN0099E Monitoring Data is Incomplete

Reason:

While attempting to analyze the monitor data set, CA Mainframe Application Tuner found that the monitor data set is incomplete.

Action:

Analysis continues, but results are likely to be incorrect.

The most likely reason for this problem is the monitor data set is full. Increase the size of the monitor data set and reinvoke the monitor. Review the Server job log for additional information.

Origin: TNICONV

Tell Technical Publications how we can improve this information