Messages BMC9700 through BMC9799 (3270 SUPEROPTIMIZER/CICS)

Creating new table

Explanation: A new table is being created. Operation of the Optimizer is unaffected.

User response: No action is required.

Table has been created

Explanation: The table that you were building has been created. Operation of the Optimizer is unaffected.

User response: No action is required.

Edit resumed for table

Explanation: You were editing this table when something happened to your CICS system. Your edit session is being resumed at the point of interruption. Operation of the Optimizer is unaffected.

User response: Continue to edit the table.

Table type must be entered

Explanation: When you are creating a table, you must specify the type of table to be created. Operation of the Optimizer is unaffected.

User response: Type Termid, Transid, or TCAM QID in the Table Type field and reenter.

Edit already in progress for this Termid

Explanation: This table is being edited from another terminal. Operation of the Optimizer is unaffected.

User response: Wait and retry the request later.

Only one table may be processed at a time

Explanation: You requested more than one table function at a time. For example, you selected to edit a table and to delete a table. Operation of the Optimizer is unaffected.

User response: Indicate only one selection by blanking out one of the requests and pressing Enter.

All Transids cannot be selected with CRTs or Printers

Explanation: You selected All Termids and All CRTS or All Printers or both. The Monitor can display and print statistics by Termid or by Transid but it cannot process both IDs at the same time. Operation of the Optimizer is unaffected.

User response: Correct and press Enter.

Table invalid when selecting All

Explanation: You selected All Transids, All CRTs, or All Printers, and you also entered a table name. Operation of the Optimizer is unaffected.

User response: Select All fields or a table and press Enter.

Single Entry invalid when selecting All

Explanation: You selected All Transids, All CRTs, or All Printers, and you also entered a single or generic Transid or Termid. Operation of the Optimizer is unaffected.

User response: Select All fields or a single entry and press Enter.

Uppercase translation for data entry is now Off/On

Explanation: If the message lists Off, the Monitor data that you enter will not be translated to uppercase characters. If the message lists On, the Monitor data that you enter will be translated to uppercase characters. Because uppercase characters is the default, the UCTRAN parameter setting for your terminal is not altered. If UCTRAN is active, input will be translated to uppercase characters. Operation of the Optimizer is unaffected.

User response: No action is required.

Options changed

Explanation: One or more of the SCS Printer, PT Order Generation, or SNA Data Compression options have been changed. If the Optimizer is active, the changes are effective immediately.

User response: No action is required.

Table type inconsistent with selection type

Explanation: You entered a table whose type does not agree with the type of selection that was requested. For example, in the TERMIDTable field, you have entered the name of a table whose entries are a list of Transids. Operation of the Optimizer is unaffected.

User response: Type another table name and press Enter.

Termid and Transid entries are mutually exclusive

Explanation: You requested Termid and Transid single or generic entries. The Monitor can display and print statistics by Termid or by Transid but it cannot process both at the same time. Operation of the Optimizer is unaffected.

User response: Blank out the Termid or Transid entry and press Enter.

Unable to load User Exit: xxxxxxxx

Explanation: The User Exit program cannot be loaded. The Program ID can be incorrect, the PPT entry can be missing or incorrect, it can be disabled, or the library which contains the program may not be in the CICS DFHRPL concatenation. If this message occurs during Optimizer startup, the Optimizer is not started, but can be started manually if desired. (See option 1.5.1.)

User response: Correct and reenter.

User Exit Options changed

Explanation: The User Exit options have been changed from option 1.5.1. If the Optimizer is active, the changes become effective immediately.

User response: No action is required.

Unable to locate table tttttttt

Explanation: The Monitor cannot locate the table listed in the message. Operation of the Optimizer is unaffected.

User response: Correct the entry or enter another table name.

Must specify COPINIT for automatic startup

Explanation: COPMON has been specified in your startup PLT instead of COPINIT. COPMON is trying to transfer control (XCTL) to COPINIT, but has received a PGMIDERR condition. The Optimizer is not started.

User response: Ensure that your PPT contains COPINIT, and (optional) change the startup PLT to specify COPINIT rather than COPMON. For more information, see the 3270 SUPEROPTIMIZER/CICS Customization Guide.

VSAM File ID required with diagnostic dump

Explanation: To print a diagnostic dump, you must specify a VSAM File ID. Operation of the Optimizer is unaffected.

User response: Type a VSAM File ID and press Enter.

Trace Buffer Allocation Size must be at least xxxxK

Explanation: The message lists the minimum amount that must be allocated to the Trace Buffer Storage so you can capture a diagnostic dump. The Wraparound Data Stream Trace is not started.

User response: Correct the allocation size on the option 3.4.0 panel and press Enter.

Unknown/Unsupported CICS release

Explanation: The Optimizer does not support or cannot detect the release of CICS that is installed at your site. The Optimizer is not started.

User response: Contact BMC Customer Support.

Direction must be I or O

Explanation: You entered an invalid character in the Direction field. The only valid selections are I (for in ) and O (for out ). Operation of the Optimizer is unaffected.

User response: Correct and press Enter.

Valid parameters are A and B

Explanation: You entered an invalid character in the After or Before field. The only valid commands are A (for after ) and B (for before ). Operation of the Optimizer is unaffected.

User response: Correct and press Enter.

Edit has been forced off

Explanation: While you were editing an online table (the first edit), it became necessary to edit the same table from another terminal. The first edit was canceled from the second terminal. If the reason for the canceled edit is unknown, you may want to contact the CICS systems programmer. The Monitor cancels the edit of the table from the first terminal. See message BMC7171.

User response: No action is required.

Table in use by user at xxxxxxxx

Explanation: The online table that you want to edit is already being edited by another user at the terminal designated in the message. The Monitor allows a table to be edited by only one user at a time.

User response: Before you edit the table wait until the other user is finished. If you were editing the table when your terminal became inoperative and you still must edit the table, cancel the first edit with a force. See message BMC7171.

File COPOPT closed/disabled at initialization - updates will be lost

Explanation: A COPOPT VSAM file is defined in the file control table (FCT), but it is closed or disabled. This condition is usually caused by the file not being verified after a CICS or system failure. Any changes that you make to the options will not be saved when the Optimizer is shut down. The Optimizer is not started.

User response: Verify the file.

File COPOPT closed - re-enter option to initialize with defaults

Explanation: A COPOPT VSAM file is defined in the file control table (FCT), but it is closed. The Optimizer is not started.

User response: To start data stream optimization without your COPOPT file, retype the option and press Enter. The Optimizer will use the default options to optimize data streams. Any changes that you make to the options will not be saved when the Optimizer is shut down.

File COPOPT disabled - re-enter option to initialize with defaults

Explanation: A COPOPT VSAM file is defined in the file control table (FCT), but it is disabled. The Optimizer is not started.

User response: To start data stream optimization without your COPOPT file, retype the option and press Enter. The Optimizer will use the default options to optimize data streams. Any changes that you make to the options will not be saved when the Optimizer is shut down.

File COPOPT closed/disabled at initialization - tables not allowed

Explanation: A COPOPT VSAM file is defined in the file control table (FCT), but it is closed or disabled. This condition is usually caused by the file not being verified after a CICS or system failure. Because the online Monitor tables are stored in the COPOPT options file, no processing can be performed on any tables. Tables cannot be created, edited, renamed, or deleted.

User response: Determine why the COPOPT file is closed or disabled, and correct the problem. If you need assistance, call BMC Customer Support.

Only one trace display allowed at a time

Explanation: You selected more than one data stream to be displayed. Only one DATA STREAM, ENVIRONMENT, or OPTIONS command can be entered. Operation of the Optimizer is unaffected.

User response: Blank out all but one of the selections.

Maximum optimization not achieved - data streams excluded from Imaging

Explanation: Your site has excluded all or some of your data streams from imaging. Optimization occurs, but the advanced Imaging technology is not being used for all or some data streams.

User response: To achieve the highest optimization, use Imaging for as many data streams as possible. Check option 1.2.1 to determine what has been excluded from Imaging. If any changes are made to the Imaging exclusion options, use option 9 to reset the optimization statistics.

COPHELP not able to be loaded

Explanation: The COPHELP module cannot be loaded. The Program ID may be incorrect; the PPT entry may be missing, incorrect, or disabled; or the library that contains the program may not be in the CICS DFHRPL concatenation. The Monitor online help panels are not available.

User response: Ensure that a PPT entry exists for COPHELP and that the correct PPT is being used. (For more information, see the 3270 SUPEROPTIMIZER/CICS Installation Guide.) Also ensure that the COPHELP module is in a library which is in the DFHRPL library concatenation.

INVREQ condition occurred when updating global area

Explanation: The WRITE failed for the COPOPT file. The message is logged. Operation of the Optimizer is not affected, but any changes to the Monitor options will not be retained after the Optimizer is shut down.

User response: Verify that the COPOPT file control table (FCT) entry matches the specifications that BMC has supplied. Specifically, ensure that the SERVREQ options selected include the options indicated in the sample FCT entry. If the problem persists, contact BMC Customer Support.

Internal logic failure, contact BMC Product Support

Explanation: A severe error occurred during Optimizer initialization. The message is logged. The Optimizer is not activated.

User response: Contact BMC Customer Support.

Optimizer not started - module not Version 2.5/Version 13.5 module

Explanation: During startup processing, the Optimizer verifies that all modules are version 2.5 or version 13.5 modules. The module ( module) that is listed in the message is not a version 2.5 or version 13.5 module. This condition could be because of one of the following reasons:

• old version 1 or version 12 library concatenated that is in front of your new library in your DFHRPL

• old module residing in your LPA (for MVS) or SVA (for VSE/ESA)

• program with the same module name in another library at your site

User response: Check your SUPEROPT libraries.

COPOPT V1/V12 Options file - Optimizer not started

Explanation: Your site has tried to start 3270 SUPEROPTIMIZER/CICS 2.5 from a PLT. However, the COPOPT options file that you specified is the options file for 3270 SUPEROPTIMIZER/CICS 1.0. The Optimizer is not started.

User response: Create a new COPOPT options file, and use the BMC Software-supplied Batch Migration Program to migrate your version 1 or version 12 options to the new version. For more information, see the 3270 SUPEROPTIMIZER/CICS Customization Guide.

COPOPT V1/V12 Options file - re-enter to initialize with defaults

Explanation: Your site has tried to start 3270 SUPEROPTIMIZER/CICS 2.5 from the online Monitor. However, the COPOPT options file that you specified is the options file for 3270 SUPEROPTIMIZER/CICS 1.0. The Optimizer is not started.

User response: If you reenter your last request, the Monitor automatically reformats your version 12/version 1 file for the new version. However, the old options are not saved and the version 13.5/version 2.5 default options is used. Create a new COPOPT options file, and use the BMC Batch Migration Program to migrate your version 12 or version 1 options to the new version. For more information, see the 3270 SUPEROPTIMIZER/CICS Customization Guide.

CICS INQ/SET programs xxxxxxxxxxxx, nnnnn terminals will be optimized

Explanation: CICS INQUIRESET modules are not available or not authorized. xxxxxxxxxxxx will be replaced by “unavailable” or “unauthorized.” nnnnn will be replaced with the number of terminals that will be optimized. This number is determined from the number of Dynamic Terminal Areas that your site has allocated. The Optimizer is started. However, only nnnnn terminals are optimized.

User response: To increase your optimization, you can perform one of the following actions:

• Define the INQUIRESET modules to CICS by reassembling your PPT or by using the CICS RDO facility:

  • To update your PPT, use the following information:

    DFHPPT TYPE=GROUP,FN=INQUIRESET

  • For RDO, add DFHINQUI to the list that is specified in your SIT parameter, GRPLIST=.

• Use option 1.6.1 to increase the number of Dynamic Terminal Areas that are available.

File COPOPT was Read-Only at initialization - updates will be lost

Explanation: A COPOPT VSAM file is defined in the file control table (FCT). However, when the Optimizer was initialized, the file was defined as read-only. The file cannot be updated, so any changes to the Monitor options will be lost when the Optimizer is shut down. Operation of the Optimizer continues with the new options.

User response: If you want the updates to be retained after the Optimizer is shut down, change the service request for the COPOPT file to specify update.

File COPOPT Read-Only at initialization - no table updates allowed

Explanation: A COPOPT VSAM file is defined in the file control table (FCT). However, when the Optimizer was initialized, the file was defined as read-only. Because the online Monitor tables are stored in the COPOPT options file, the tables can only be browsed. Tables cannot be created, edited, renamed, or deleted.

User response: Change the service request for the COPOPT file to specify update.

Line length must be less than 256

Explanation: The default print line length must be a number greater than 0 and less than 256. Operation of the Optimizer is unaffected.

User response: Correct and press Enter.

Line length must be numeric

Explanation: The default print line length must be a number from 1 to 255. Operation of the Optimizer is unaffected.

User response: Correct and press Enter.

Entry/Table required for Alternate Line Length

Explanation: The alternate print line length will apply only to the Termids or Transids that are specified. Operation of the Optimizer is unaffected.

User response: Type the Termids and/or Transids that are to apply to the alternate line length.

Entry/Table not allowed without Alternate Line Length

Explanation: The Optimizer will use the alternate print line length to calculate the print line length for the Termids and/or Transids entered. However, no alternate line length has been entered. Operation of the Optimizer is unaffected.

User response: Specify an alternate line length.

Unsupported SCREENSIZE ( xxxxxxxxx). Press CLEAR, incompatible terminal

Explanation: The Optimizer does not support screen size that you have defined. Operation of the Optimizer is unaffected.

User response: Press CLEAR. Then define a standard screen size. Do not use an alternate screen size. Or, use a different terminal.

Table edit Suspended for table xxxxxxxx

Explanation: The table that you have been editing has been suspended, usually because of a conflict with another user. Operation of the Optimizer is unaffected.

User response: Reedit the table.

The Optimizer will expire in xxxx days

Explanation: Your trial period or authorization to use the product is about to expire. The number of days decrements to zero, at which time the Optimizer becomes inoperable.

User response: Contact BMC Contracts Administration for product authorization.

Transid xxxx must invoke program COPMON

Explanation: The transaction that you entered does not execute the COPMON program. Operation of the Optimizer is unaffected.

User response: Define the Transid to COPMON, or change the transaction prefix to one that calls COPMON.

Required Transid xxxx not found

Explanation: The Transid that you entered has not been defined to CICS before your attempt to invoke it. Operation of the Optimizer is unaffected.

User response: Change the transaction prefix.

Transaction prefix changed to xxxx

Explanation: The transaction prefix has been changed successfully. The Monitor begins to use the new prefix immediately.

User response: No action is required.

Invalid entry detected for type of maintenance

Explanation: You must select 1, 2, 3, or 4 to indicate what type of CPU ID authorization maintenance you are requesting. Any selection other than 1, 2, 3, or 4 is invalid. The request is rejected and you are prompted for a valid entry.

User response: Select 1, 2, 3, or 4.

Invalid entry detected for product selection

Explanation: You must select 1 or 2 to indicate on what product you are applying CPU ID authorization code maintenance. Any selection other than 1 or 2 is invalid. The request is rejected and you are prompted for a valid entry.

User response: Select 1 or 2.

HEX authorization code contains invalid characters

Explanation: The product authorization code that you entered contains invalid characters. Only valid hexadecimal digits (0 to F) are allowed in this field. The request is rejected and you are prompted for a valid entry.

User response: Use only hexadecimal digits in the authorization code field.

The data set name is invalid

Explanation: The data set name is blank, null, or contains characters that are invalid. The request is rejected and you are prompted for a valid entry.

User response: Supply a valid data set name in the field.

CPUID contains invalid characters

Explanation: You entered invalid characters in the CPU ID field. Only hexadecimal digits (0 to F) are allowed in this field. The request is rejected and you are prompted for a valid entry.

User response: Use only hexadecimal digits in the CPU ID field.

CPU TYPE contains invalid characters

Explanation: You entered invalid characters in the CPU TYPE field. Only hexadecimal digits (0 to F) are allowed in this field. The request is rejected and you are prompted for a valid entry.

User response: Use only hexadecimal digits in the CPU TYPE field.

NEWCPUID contains invalid characters

Explanation: You entered invalid characters in the NEW CPU ID field. Only hexadecimal digits (0 to F) are allowed in this field. The request is rejected and you are prompted for a valid entry.

User response: Use only hexadecimal digits in the NEW CPU ID field.

NEW CPU TYPE contains invalid characters

Explanation: You entered invalid characters in the NEW CPU TYPE field. Only hexadecimal digits (0 to F) are allowed in this field. The request is rejected and you are prompted for a valid entry.

User response: Use only hexadecimal digits in the NEW CPU TYPE field.

Data set name for output JCL is not valid

Explanation: The data set name is blank, null, or contains invalid characters. The request is rejected and you are prompted for a valid entry.

User response: Supply a valid data set name in the field.

The JCL has been output to the TD queue

Explanation: The transient data queue output was selected and the COPA transaction has successfully written the JCL to the specified destination. Operation of the Optimizer is unaffected.

User response: Check the batch job for completion.

The JCL has been output to the JES internal reader

Explanation: The spool interface for output was selected and the COPA transaction has successfully written the JCL to the spooler. Operation of the Optimizer is unaffected.

User response: Check the batch job for completion.

Cannot spool JCL-- change SIT to SPOOL=YES

Explanation: The spool interface for output was selected and it has been determined that SPOOL=YES was not coded in the SIT table. Operation of the Optimizer is unaffected. It is not possible to write to the spool.

User response: Change SIT table to SPOOL=YES.

You have pressed an invalid key

Explanation: Valid keys are shown on the screen. Only one of these keys may be selected. Operation of the Optimizer is unaffected. An invalid key is ignored.

User response: Select a valid key.

The TD queue specified is not valid

Explanation: The transient data queue output was selected and it has been determined that the queue name is invalid. Operation of the Optimizer is unaffected.

User response: Check queue name and supply a valid TD queue.

More than one destination selected--not accepted

Explanation: More than one destination was selected for the job control language (JCL). Operation of the Optimizer is unaffected.

User response: Select only one destination.

PF10 has been detected but no destination chosen

Explanation: PF10 is the correct action key for this panel, but you must select a destination for the JCL. Operation of the Optimizer is unaffected.

User response: Select one of the available destinations.

Allocation for data set failed. Please check

Explanation: While trying to dynamically allocate the specified data set, the SVC 99 returned a nonzero return code. No data set allocation can take place.

User response: Check the file name for accuracy.

De-allocation of the data set has failed

Explanation: While trying to dynamically deallocate the specified data set, the SVC 99 returned a nonzero return code. No data set deallocation can take place.

User response: Use ADYN to deallocate.

The JCL has been written to the data set

Explanation: The data set output was selected. The COPA transaction has written the JCL to the specified destination successfully. Operation of the Optimizer is unaffected.

User response: Edit the data set for job submission.

No member name given and file is not sequential

Explanation: The data set output was selected and the file was found to be a PDS, but no member name was supplied. Operation of the Optimizer is unaffected.

User response: To write to a PDS, supply a member name.

Member name given but the file is sequential

Explanation: The data set output was selected and the file was found to be a sequential file, but a member name has been supplied. This condition creates a conflict. Operation of the Optimizer is unaffected.

User response: To write to a sequential data set, leave the member name blank.

SPOOLOPEN failed. Could be spool is busy. Try again

Explanation: The spool interface for output was selected and the COPA transaction has not been able to issue the SPOOLOPEN command successfully. The spool interface is probably busy. Operation of the Optimizer is unaffected.

User response: Retry this selection in a few minutes.

Open failed on the file. Please check the file

Explanation: The specified file has been allocated, but open has failed. Operation of the Optimizer is unaffected.

User response: Check the file to determine whether someone else is using it.

JCL write to variable length file is not supported

Explanation: The file that is specified to receive the JCL must have fixed-length records. Operation of the Optimizer is unaffected.

User response: Write the JCL to a different file that has fixed-length records.