Messages BMC9700 through BMC9799 (ULTRAOPT and MainView for VTAM)

Creating new table

Explanation: A new table is being created.

User response: No action is required.

Table has been created

Explanation: The table you were building was created.

User response: No action is required.

Edit resumed for table

Explanation: You were in the process of editing a table when something happened to your VTAM system. Your edit session is being resumed at the point of interruption.

User response: No action is required. You may continue to edit the table.

Table type must be entered

Explanation: When creating a table, you must enter the type of table.

User response: Type either LU, APPLID, or ApplTran in the appropriate Table field and an action in the Action field, and press Enter.

Edit already in progress for this LU

Explanation: This table is being edited from another terminal.

User response: Try 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 a table to edit and a table to be deleted.

User response: Indicate one selection only by blanking out one of the requests, and reenter.

All Applids cannot be selected with CRTs or Printers

Explanation: You selected All LUs and either (or both) All CRTs or All Printers. The Monitor can display and print either statistics by LU or by APPLID, but it cannot process both at the same time.

User response: Correct this conflict and reenter.

Table invalid when selecting All

Explanation: You selected either All APPLIDs, All CRTs, or All Printers and entered a table name.

User response: Select either one of the All fields or a table, and reenter.

Single Entry invalid when selecting All

Explanation: You selected All APPLIDs, All CRTs, or All Printers and entered a single or generic APPLID or LU.

User response: Select either one of the All fields or a Single entry, and reenter.

Uppercase translation for data entry is now xxx

Explanation: The status of uppercase character translation is displayed. xxxx is the status. If xxx = Off, the Monitor data that you enter is not translated to uppercase characters. If xxx = On, the Monitor data that you enter is translated to uppercase characters.

User response: No action is required.

1.3 Options changed

Explanation: The SCS Printer, PT Order Generation, or SNA Data Compression options was changed. The changes are effective immediately.

User response: No action is required.

Table type inconsistent with selection type

Explanation: You entered a table with a type that does not agree with the type of selection that was requested. For example, in the LU Table field, you typed the name of a table with entries that are a list of APPLIDs.

User response: Type another table name and press Enter.

LU and Applid entries are mutually exclusive

Explanation: You entered both LU and APPLID single or generic entries. The Monitor can display and print statistics by LU or by APPLID, but it cannot process both at the same time.

User response: Blank out either the LU or the APPLID entry and press Enter.

Unable to load User Exit: xxxxxxxx

Explanation: The User Exit Program cannot be loaded. The Program ID is incorrect, or the library that contains the program is not in the subsystem JOBLIB, STEPLIB, or LINKLIST concatenation. If this message occurs during Optimizer component startup, the Optimizer component is not started.

User response: Correct and reenter.

User Exit Options changed

Explanation: The User Exit options were changed from Option 1.5. The changes are effective immediately.

User response: No action is required.

Unable to locate table tttttttt

Explanation: The Monitor cannot locate the table listed in the message.

User response: Correct or type another table name.

VSAM File ID required with diagnostic dump

Explanation: To print a diagnostic dump, you must specify a VSAM File ID.

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

Trace Buffer Allocation Size must be at least xxxx K

Explanation: xxxx is the minimum size (in kilobytes) that must be allocated to the Trace Buffer Storage to capture a diagnostic dump. The Wraparound Data Stream Trace is not started.

User response: Correct and reenter.

Unknown/Unsupported VTAM release

Explanation: The subsystem does not support or cannot detect the release of VTAM that is installed at your data center. The subsystem is not started.

User response: Determine the VTAM release that you are using and compare it to the minimum release requirements that are listed in the ULTRAOPT Customization Guide, then contact BMC Customer Support.

Direction must be I or O

Explanation: You typed an invalid character in the Inbound or Outbound field. Valid selections are I (inbound) and O (Outbound).

User response: Correct and reenter.

Valid parameters are A and B

Explanation: You typed an invalid character in the After or Before field. Valid characters are A (after) and B (before).

User response: Correct and reenter.

Edit has been forced off

Explanation: When you were editing an online table (the first edit), it was necessary to edit the same table from another terminal. The first edit was canceled from the second terminal. The Monitor cancels the first edit of the table from the second terminal.

User response: If the reason for the canceled edit is unknown, contact the VTAM or system programmer.

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: Wait until the other user is finished before you attempt to edit the table. If you must edit the table (for example, you were editing the table when your terminal became inoperative), the first edit may be canceled with a force.

FILE xxxOPT closed at initialization--updates will be lost

Explanation: An xxxOPT VSAM file was created, but it is closed. This action occurs when the file is not verified (VERIFY) after a VTAM or system failure. The subsystem is not started.

User response: Verify the file.

FILE xxxOPT closed--reenter option to initialize with defaults

Explanation: A xxxOPT VSAM file is closed. xxx is the product code. The subsystem is not started.

User response: To start data stream optimization without the options file, type the option again and press Enter. The Optimizer component uses the default options to optimize data streams, but without an options file, changes are lost when the subsystem is shut down.

FILE xxxOPT closed at initialization--tables not allowed

Explanation: A xxxOPT VSAM file has been defined, but it is closed. This condition is usually caused by the file not being verified after a VTAM or system failure. Because the online Monitor tables are stored in the SOPOPT Options file, no processing can be performed on any tables. Tables cannot be created, edited, renamed, or deleted.

User response: Determine why the options file is closed and correct the problem. If you need assistance, contact 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.

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

Maximum optimization not achieved--data streams excluded from Imaging

Explanation: You excluded all or some of your data streams from Imaging. Optimization is occurring, but the advanced Imaging technology is not being used for all or some data streams.

User response: To achieve maximum optimization, use Imaging for as many data streams as possible. Check Option 1.2 to determine what is excluded from Imaging. If changes are made to the Imaging exclusion options, reset the optimization statistics from Option 9.

xxxHELP not able to be loaded

Explanation: The xxxHELP module cannot be loaded. The library that contains the program may not be in the subsystem JOBLIB, STEPLIB, or LINKLIST concatenation. xxx is the product code. The Monitor online help panels are unavailable.

User response: Ensure that the xxxHELP module is in a library that is in the subsystem JOBLIB, STEPLIB, or LINKLIST concatenation.

INVREQ condition occurred when updating global area

Explanation: Operation of the subsystem is not affected, but changes to the Monitor options are not retained after the subsystem is shut down.

User response: If the problem persists, contact BMC Customer Support.

Internal logic failure, contact BMC Customer Support

Explanation: The subsystem is not started.

User response: Contact BMC Customer Support.

product not started-- modname not version 1 module

Explanation: During startup processing, the product ensures that all of its modules are the correct version. The module modname listed in the message is not the correct version. This condition could be caused by another program with the same module name in another library. The Optimizer component is not started.

User response: Check your subsystem libraries.

A Sxxx ABEND HAS OCCURRED IN program CSECT cccccccc OFFSET + aaaa

Explanation: An S xxx system abend code occurred in program CSECT cccccccc at OFFSET + aaaa. This message is issued to the console during a Monitor abend. The terminal issuing the transaction that is causing the abend is notified. The Monitor request is terminated.

User response: Contact BMC Customer Support.

Line length must be less than 256

Explanation: The SCS Print Line Length must be greater than 0 and less than 256.

User response: Correct and reenter.

Line length must be numeric

Explanation: The SCS Print Line Length must be a number from 1 to 255.

User response: Correct and reenter.

Entry/Table required for Alternate Line Length

Explanation: The Alternate Print Line Length that was entered applies to the LUs or APPLIDs specified only.

User response: Enter the LUs or APPLIDs that apply to the Alternate Print Line Length.

Entry/Table not allowed without Alternate Line Length

Explanation: An Alternate Print Line Length is used to calculate the print line length for the LUs, APPLIDs, or both that were entered. No alternate print line length was entered.

User response: Specify an Alternate Print Line Length.

UNSUPPORTED SCREENSIZE (xxxxxxxx), PRESS CLEAR, incompatible terminal

Explanation: The Optimizer component does not support the screen size that you defined.

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 tablename

Explanation: The table you were editing was suspended, usually because of a conflict with another user.

User response: Re-edit the table.

THE OPTIMIZER WILL EXPIRE IN x DAYS

Explanation: You are running ULTRAOPT on a bypass product authorization password that will expire in x days. ULTRAOPT continues to operate normally.

User response: For uninterrupted operation when the bypass password expires, contact your BMC sales representative to purchase a license and receive a permanent password.

program has terminated with aN S xxx IN cccccccc AT OFFSET + aaaa--processing continues

Explanation: Program program abended with a system abend code S xxx at + aaaa in CSECT cccccccc. This message is issued to the console during a Monitor abend. The terminal that is issuing the transaction causing the abend is notified. The Monitor will be restarted and a dump written to the SYSUDUMP data set.

User response: Contact BMC Customer Support.

Error trying to write DDNAME ddname. FDBK= ffffffff, R15= xxxxxxxx. Write failed.

Explanation: An error was encountered while trying to write to a VSAM cluster referenced by ddname. The contents of register 15 xxxxxxxx is the VSAM return code, and ffffffff is the VSAM feedback code. The write to the specified VSAM cluster is not completed. Processing continues.

User response: To determine the cause of the error, see the IBM VSAM Programmer’s Guide.

Error trying to read DDNAME ddname. FDBK= ffffffff, R15= xxxxxxxx. Read failed.

Explanation: An error was encountered while trying to read from a VSAM cluster referenced by ddname. The contents of register 15 xxxxxxxx is the VSAM return code, and ffffffff is the VSAM feedback code. The read from the specified VSAM cluster is not completed. Processing continues.

User response: To determine the cause of the error, see the IBM VSAM Programmer’s Guide.

Error trying to rewrite DDNAME ddname. FDBK= ffffffff, R15= xxxxxxxx. Rewrite failed.

Explanation: An error was encountered while trying to rewrite a VSAM cluster referenced by ddname. The contents of register 15 xxxxxxxx is the VSAM return code, and ffffffff is the VSAM feedback code. The rewrite from the specified VSAM cluster is not completed. Processing continues.

User response: To determine the cause of the error, see the IBM VSAM Programmer’s Guide.

Error trying to allocate DDNAME ddname. Allocation failed.

Explanation: An error was encountered while trying to allocate a VSAM cluster referenced by ddname. The requested file is not allocated. Processing continues.

User response: Determine whether the VSAM cluster is defined and not allocated by another task.

Error trying to open DDNAME ddname. FDBK= ffffffff, R15= xxxxxxxx. Open failed.

Explanation: An error was encountered while trying to open a VSAM cluster referenced by ddname. The contents of register 15 xxxxxxxx is the VSAM return code, and ffffffff is the VSAM feedback code. The open of the specified VSAM cluster is not completed. Processing continues.

User response: To determine the cause of the error, see the IBM VSAM Programmer’s Guide.

Unable to load xxxESTA. Optimizer subtasking not started.

Explanation: An error was encountered while trying to load module xxxESTA during initialization of the Optimizer subtask. xxx is the product code. Subtasking for the Optimizer is not started, no file access is done, and no timer services are processed.

User response: Determine whether xxxESTA was renamed or deleted from the subsystem’s load library. Correct the problem and restart the subsystem.

Unable to GETMAIN storage. product subtasking not started.

Explanation: An error was encountered while trying to issue a GETMAIN for storage to initialize end-of-task processing for the product subtask. Subtasking for the product is not started, no file access is done, and no timer services are processed.

User response: Verify that enough virtual storage is available for the subsystem region, and restart the subsystem.

Unable to load xxxEOST. product subtasking not started.

Explanation: An error was encountered while trying to load module xxxEOST during initialization of the product subtask. xxx is the product code. Subtasking for the product is not started, no file access is done, and no timer services are processed.

User response: Determine whether xxxEOST was renamed or deleted from the subsystem’s load library. Correct the problem and restart the subsystem.

Unable to load xxxST. product subtasking not started.

Explanation: An error was encountered while trying to load module xxxST during initialization of the product subtask. xxx is the product code. Subtasking for the product is not started, no file access is done, and no timer services are processed.

User response: Determine whether xxxST was renamed or deleted from the subsystem’s load library. Correct the problem and restart the subsystem.

Error during GETMAIN. product subtasking not started.

Explanation: An error was encountered while trying to issue a GETMAIN for storage to initialize the product subtask. Subtasking for the product is not started, no file access is done, and no timer services are processed.

User response: Verify that enough virtual storage is available for the subsystem region and restart the subsystem.

Error during FREEMAIN. product subtasking not started.

Explanation: An error was encountered while trying to issue a FREEMAIN for storage to initialize the xxxST subtask. xxx is the product code. Subtasking for the product is not started, no file access is done, and no timer services are processed.

User response: Contact BMC Customer Support.

xxxST has terminated with a dump. System restarting xxxST.

Explanation: An abend occurred in xxxST. If a DD statement was included in the subsystem region JCL, a dump is being written to SYSUDUMP. xxx is the product code. The current xxxST subtask is terminated, and a new subtask is started to take its place. Depending on the point of abend, this action may mean the loss of at least one request being processed by xxxST.

User response: Route the abend dump to BMC Customer Support for analysis.

Error during GETMAIN. xxxST terminating with a User 4050.

Explanation: An unknown error occurred while trying to perform a GETMAIN. The current xxxST subtask is terminated with a user 4050, and a dump is taken to SYSUDUMP. The subtask is restarted a maximum of three times. xxx is the product code.

User response: Contact BMC Customer Support.

Error during GETMAIN. xxxST terminating with a User 4051.

Explanation: An unknown error occurred while trying to perform a GETMAIN. The current xxxST subtask is terminated with a user 4051, and a dump is taken to SYSUDUMP. The subtask is restarted a maximum of three times. xxx is the product code.

User response: Contact BMC Customer Support.

Error during FREEMAIN. xxxST terminating with a User 4052.

Explanation: An unknown error occurred while trying to perform a GETMAIN. The current xxxST subtask is terminated with a user 4052, and a dump is taken to SYSUDUMP. The subtask is restarted a maximum of three times. xxx is the product code.

User response: Contact BMC Customer Support.

Error during FREEMAIN. xxxST terminating with a User 4053.

Explanation: An unknown error occurred while trying to perform a GETMAIN. The current xxxST subtask is terminated with a user 4053, and a dump is taken to SYSUDUMP. The subtask is restarted a maximum of three times. xxx is the product code.

User response: Contact BMC Customer Support.

Error during GETMAIN. xxxST terminating with a User 4054.

Explanation: An unknown error occurred while trying to perform a GETMAIN. The current xxxST subtask is terminated with a user 4054, and a dump is taken to SYSUDUMP. The subtask is restarted a maximum of three times. xxx is the product code.

User response: Contact BMC Customer Support.

Error during GETMAIN. xxxST terminating with a User 4055.

Explanation: An unknown error occurred while trying to perform a GETMAIN. The current xxxST subtask is terminated with a user 4055, and a dump is taken to SYSUDUMP. The subtask is restarted a maximum of three times. xxx is the product code.

User response: Contact BMC Customer Support.

Error found during product initialization. Unable to load program.

Explanation: product initialization was unable to load program. Product initialization is terminated with a user 4060 abend. The product is not initialized.

User response: Determine whether the requested program was renamed or deleted from the subsystem’s load library.

Error found during product initialization. Unable to GETMAIN xxxxxxxx.

Explanation: Optimizer initialization failed because ULTRAOPT was unable to complete a GETMAIN for xxxxxxxx. product initialization is terminated with a user 4060 abend. The product is not initialized.

User response: Ensure that enough virtual storage is available for the subsystem region.

INSUFFICIENT STORAGE TO PROCESS MONITOR TRANSACTION.

Explanation: The Monitor initialization failed while attempting to GETMAIN storage for the save areas. The Monitor initialization is terminated, and a formatted output panel is sent to the terminal issuing the TSO command processor that provides access to the Monitor.

User response: Ensure that enough virtual storage is available in the ULTRAOPT region.

product Subsystem inactive or unauthorized

Explanation: The ULTRAOPT subsystem is not active.

User response: Ensure that the product authorization password has not expired and that you have already started the subsystem before starting the monitor on the same system.

product control block ID invalid

Explanation: The ULTRAOPT CSAT control block header may have been overlaid or corrupted.

User response: Contact BMC Customer Support.

Cannot obtain product CSAT interlock

Explanation: A CSAT lock could not be obtained for ULTRAOPT.

User response: Contact BMC Customer Support.

Cannot release product CSAT interlock.

Explanation: The CSAT lock could not be released for ULTRAOPT.

User response: Contact BMC Customer Support.

product subsystem ASCB not present.

Explanation: ULTRAOPT was terminated during monitor processing.

User response: Restart the product.

xxxSST has terminated with a dump. System restarting xxxSST.

Explanation: An abend occurred in xxxSST, and a dump was written to SYSUDUMP. xxx is the product code. The current xxxSST subtask is terminated, and a new subtask is started. Depending on the point of abend, this action may mean the loss of at least one request that is being processed by SOPSST.

User response: Send the dump to BMC Customer Support.

TGET GETMAIN failed.

Explanation: A GETMAIN request for the TGET buffer failed.

User response: Increase TSO region size and retry.

TGET failed return code 08--NOWAIT

Explanation: TGET failed with return code 08.

User response: Contact BMC Customer Support.

TGET failed return code 0C - Input buffer is too small--EDIT mode

Explanation: TGET failed with return code 0C, which means that the input buffer is too small in the EDIT mode.

User response: Contact BMC Customer Support.

TGET failed return code 10--Invalid parameters.

Explanation: TGET failed with return code 10, which means that there were invalid parameters.

User response: Contact BMC Customer Support.

TGET failed return code 14--terminal disconnected.

Explanation: TGET failed with return code 14, which means that the terminal was disconnected.

User response: Contact BMC Customer Support.

TGET failed return code 1C--Input buffer is too small--NOEDIT mode.

Explanation: TGET failed with return code 1C, which means that the input buffer is to small in the NOEDIT mode.

User response: Contact BMC Customer Support.

TGET failed return code 04--NOWAIT.

Explanation: TGET failed with return code 04 - NOWAIT.

User response: Contact BMC Customer Support.

TPUT failed return code 0C--ASID not allowed.

Explanation: TPUT failed with return code 0C.

User response: Contact BMC Customer Support.

TPUT failed return code 10--Invalid parameters.

Explanation: TPUT failed with return code 10 for invalid parameters.

User response: Contact BMC Customer Support.

TPUT failed return code 14--terminal disconnected.

Explanation: TPUT failed with return code 14, and the terminal was disconnected.

User response: Contact BMC Customer Support.

Cannot connect to product subsystem.

Explanation: You cannot connect to ULTRAOPT through a PC link.

User response: Contact BMC Customer Support.

ULTRAOPT/IMS has detected SUPEROPT/IMS Options file--Optimizer not started.

Explanation: The SOPOPT file is in the SUPEROPT/IMS format and is not usable by ULTRAOPT. The Optimizer component does not start.

User response: For information about defining a VSAM options file, see the <docTitle>ULTRAOPT Customization Guide</docTitle> .

ULTRAOPT has detected ECSA at 90%--Optimization suspended.

Explanation: ECSA usage has reached 90 percent. The Optimizer does not optimize any data streams until ECSA usage falls below 90 percent. ULTRAOPT has not intercepted any new APPLIDs since ECSA reached 80 percent.

User response: If you can reduce ECSA usage below 90 percent, optimization will resume.

Local Format Storage function not supported with ULTRAOPT/IMS

Explanation: An attempt was made to use the LFS panel from ULTRAOPT/IMS.

User response: With version 1, LFS is not a feature of ULTRAOPT/IMS. If you need to use LFS, you must install ULTRAOPT/IMS version 2 or later.

Cannot access Monitor from both sessions of split-screen.

Explanation: Access to the ULTRAOPT ISPF Monitor is allowed only once per user. An attempt was made to access the Monitor concurrently from both sessions under ISPF. The second access to the ULTRAOPT Monitor is denied.

User response: Perform any activity necessary in the ULTRAOPT Monitor from the existing session.

Maximum number of ISPF Monitor users reached, access denied.

Explanation: The maximum number of ULTRAOPT ISPF Monitor users is 16. This limit has been reached. Access to the ULTRAOPT Monitor via ISPF invocation is denied.

User response: If immediate access is required, use the non-ISPF invocation of the Monitor. Otherwise, wait until an existing ISPF user of the ULTRAOPT Monitor exits the Monitor.