In response to the .VTM command, OMEGAMON attempted to display multi-session status information. However, OMEGAMON detected one or more problems in the internal subtask configuration for OBVTAM. This problem may be caused by transitory changes in OBVTAM subtask structures, which could result in a program check.
The command terminates.
Reissue the command. If this message persists, contact IBM Software Support.
No tasks within the address space specified by the PEEK major command own any data-only spaces.
The command terminates.
None. This is an informational message and does not require further action. Typically, this type of message clarifies some aspect of system behavior during normal operations.
An internal subroutine detected an error while collecting information on data-only spaces for the specified address space.
The command terminates.
Try the command again. If this message persists, contact IBM Software Support.
The command cccc is not a minor of the current major command or is not itself a major or immediate command.
OMEGAMON bypasses this line.
Correct the command and retry.
OMEGAMON no longer supports the specified command. Command cccc now performs a similar function.
OMEGAMON selects the new version of the command.
None. In the future, use command cccc.
This command is not valid with the MVS version you are running (nnn).
OMEGAMON selects the next command.
Use this command with the correct version of MVS.
The INFO-line command entered does not exist.
The command is not executed.
Correct the command and retry.
The specified command was disabled by user security processing.
OMEGAMON bypasses this line.
Issue another command.
An OMEGAMON command terminated abnormally due to a program check at location xxxxxxxx.
OMEGAMON aborts the command.
Retry the command. If the problem persists, follow the instructions given in the Preface, then contact IBM Software Support.
Cross memory operations were attempted to an address space that was swapped out.
Program recovery is successful, although the operation is suppressed.
None. This is an informational message and does not require further action. Typically, this type of message clarifies some aspect of system behavior during normal operations.
A pattern-controlled operation was requested, but the pattern was not defined.
Operation is ignored.
Set a proper pattern using the .SPT command.
The command requires a pattern that only has numeric values.
Pattern operation is ignored.
Correct the command and retry.
No pattern exists for the requested pattern number.
Pattern operation is ignored.
Correct the command or assign a pattern.
Invalid pattern number.
Pattern operation is ignored.
Correct the command and retry.
OMEGAMON built-in loop detection encountered a possible loop in an OMEGAMON command processor.
OMEGAMON terminates the command.
Use the .SET command to increase the LOOPTIME and/or LOOPCOUNT values. If the problem persists after setting these values to the maximum, follow the instructions given in the Preface and contact IBM Software Support.
A password was not supplied for the security level associated with this command.
OMEGAMON suppresses the command.
Supply a valid password, or see your security administrator.
The OMEGAMON external security interface determined that the command is not authorized for execution.
OMEGAMON suppresses the command.
See your security administrator.
This command does not support a .D or a .R argument.
The command is not executed.
Correct the command syntax and retry.
OMEGAMON’s built-in loop detection encountered a possible loop in an OMEGAMON service module.
OMEGAMON terminates with a user ABEND 0925.
Use the .SET command to increase the LOOPTIME and/or LOOPCOUNT values. If the problem persists after setting these values to the maximum, follow the instructions given in the Preface and contact IBM Software Support.
A loop was detected while termination operations were under way.
Termination operations are suspended and OMEGAMON abends.
If the problem persists, contact IBM Software Support.
OMEGAMON abend protection (ESTAE) processing detected a program check error in a module at location xxxxxxxx.
OMEGAMON terminates the command.
Follow the instructions given in the Preface, then contact IBM Software Support.
The command cannot be executed without having either the authority to issue the CP LOCATE, or the IBM® Tivoli® Candle User Diagnose installed.
OMEGAMON® terminates the command.
Get the privilege class needed to execute the CP LOCATE command or install the IBM Tivoli CandleUser Diagnose as documented in the OMEGAMON and EPILOG for VM Installation and Customization Guide and regenerate the VM operating system.
The command cannot be executed without having either the IBM Tivoli Candle User Diagnose installed or authority to issue the CP LOCK command.
OMEGAMON terminates the command.
Install the IBM Tivoli Candle User Diagnose as documented in the OMEGAMON and EPILOG for VM Installation and Customization Guide and regenerate the VM operating system, or get the privilege class needed to execute the CP LOCK command.
An abend occurred for an OMEGAMON session, and the non-private area resources will be removed. ccccc is the abend code and xxxxxxxx is the return code associated with the failure. This message is always followed by OB0935.
Termination continues.
None. This is an informational message and does not require further action. Typically, this type of message clarifies some aspect of system behavior during normal operations.
At initialization, this message appears if OMEGAMON was unable to load the designated user security exit.
All EXTERNAL=YES commands with associated security levels of 0 are disabled.
Ensure that the user security exit is specified in the MODULE= keyword of the security update program.
Abend processing removed non-private area resources in preparation for abnormal termination.
Termination continues.
None. This is an informational message and does not require further action. Typically, this type of message clarifies some aspect of system behavior during normal operations.
The MVS version level of OMEGAMON you are attempting to initialize (nnn) does not match the MVS version under which you are running (mmm). Because we do not distinguish among all possible MVS variations, mmm can be 13x, 2xx, or 3xx. The variable bbb is the correct level.
The system prompts you on whether you want to continue initialization. If you do continue to run an OMEGAMON version that does not match the MVS version level, the integrity of some OMEGAMON data may be compromised.
Determine whether your site is licensed for the version of OMEGAMON that matches your MVS level. If so, check the version level specified in the start-up parameters and change nnn to bbb. If not, contact IBM Software Support.
The variable nnn is the MVS version on which the module (pppppppp) is supported. It does not match the MVS version under which you are running (mmm). Because we do not distinguish among all possible MVS variations, mmm can be one of 13x, 2xx, or 3xx.
The system prompts you on whether you want to continue initialization. If you do continue and run an OMEGAMON version that does not match the MVS version level, the integrity of some OMEGAMON data may be compromised.
Determine whether your site is licensed for the version of OMEGAMON that matches your MVS level. If so, check the version level specified in the start-up parameters and change nnn to bbb. If not, contact IBM Software Support.
OMEGAMON no longer supports versions of MVS prior to SP1.3.
The system prompts you on whether you want to continue initialization. If you continue to run an OMEGAMON version that does not match the MVS version level, the integrity of some OMEGAMON data may be compromised.
Upgrade your MVS version.
A collector is starting and needs memory for the work area to communicate with the director. The request for memory has failed.
The collector terminates.
Increase region size and try again.
During the last 5 minutes, an OMEGAMON collector session did not detect a response from its associated director session.
OMEGAMON terminates the collector.
Determine why the director failed and restart the session.
The user tried to establish more than the maximum number (7) of cross memory collector sessions with a single OMEGAMON director.
OMEGAMON cancels the request.
If you need to display more than 7 cross memory collectors on this system, start another OMEGAMON director.
A cross memory collector at a different (and incompatible) release level tried to start a cross memory session with an OMEGAMON director.
OMEGAMON cancels the request.
Bring up the director and cross memory collector using the same (or a compatible) version of OMEGAMON.
An OMEGAMON director did not detect a response from one of its associated collectors during the last 5 minutes.
The director terminates this collector session.
Determine why the collector failed, and restart the collector. If the condition continues, contact IBM Software Support.
An attempt to bring up an OMEGAMON director failed because OMEGAMON was already running in another address space using the same system ID (via the SYS= start-up keyword).
OMEGAMON cancels the request.
To initialize the OMEGAMON director, specify a unique value for the SYS= parameter.
An attempt was made to bring up an OMEGAMON director that did not have APF authorization.
OMEGAMON terminates the director.
APF authorize all of the necessary load libraries and restart the director.
OMEGAMON could not start the requested OMEGAMON cross memory collector because it could not find the specified director (via the DIR= start-up keyword).
OMEGAMON cancels the request.
Bring up the OMEGAMON director before you try to initialize the collector or specify the ID of an active director.
An attempt to start the requested OMEGAMON collector failed because another collector was already active using the specified system ID (via the SYS= start-up keyword). You must specify a unique system ID for each collector when you bring up multiple OMEGAMON collectors in the same system.
OMEGAMON cancels the request.
Specify a unique system ID for each collector.
The number of columns you specified (via the COLS= keyword) for the cross memory or cross system collector does not match the number of columns for the director with which the collector is attempting to begin a session.
OMEGAMON cancels the request.
Correct the COLS= value at either the collector or director and restart the session.
A cross memory collector tried to start a cross memory session with an OMEGAMON director of a different and incompatible release level.
OMEGAMON cancels the request.
Bring up the director and cross memory collector using the same (or compatible) version of OMEGAMON.
This session’s cross system data set was formatted with an incompatible version of the format program.
OMEGAMON cancels the request.
Reformat the cross system data set with the current version of the KOBXDSK program.
The /ATTACH command generates this message. OMEGAMON allows no more than 7 collectors plus the director segment at the director screen for cross memory/cross system mode terminal input/output processing.
OMEGAMON cancels the request.
If you need to display more than 7 collectors on this system, start another OMEGAMON director.
The /ATTACH command generates this message. While trying to bring up a cross system collector session, OMEGAMON detected that this collector was already in session with a director.
OMEGAMON cancels the request.
Specify the correct collector ID.
This message may be issued in either of two situations:
OMEGAMON cancels the request.
To correct the error, check the following:
When you have corrected the error, restart the OMEGAMON director.
The /ATTACH command generates this message. An /ATTACH INFO-line command was entered without a collector ID.
OMEGAMON cancels the request.
Re-enter the /ATTACH command and specify a valid collector ID.
The /ATTACH command generates this message. A different release level format program was used to format the cross system data set for this cross system session and its director.
OMEGAMON cancels the request.
Reformat the cross system data set with the current version of the KOBXDSK program.
The /ATTACH command generates this message. The cross system data set used for cross system session initialization was formatted for a different screen size (via the COLS= parameter) than that of the director terminal.
OMEGAMON cancels the request.
Reformat the cross system data set with KOBXDSK and specify the proper COLS= value.
The /ATTACH command generates this message. The attempt to attach a cross system collector at an OMEGAMON console failed because it was not initiated as an OMEGAMON director.
OMEGAMON cancels the request.
Restart OMEGAMON, specifying the proper parameter for director mode.
An enqueue attempt by the director controller failed.
The attach is suppressed.
If this problem persists, contact IBM Software Support.
A dequeue attempt by the director controller failed.
The detach is suppressed.
If this problem persists, contact IBM Software Support.
You are using two incompatible levels of OMEGAMON load modules.
OMEGAMON does not start.
Verify that the proper libraries are in use. If necessary, reinstall OMEGAMON using the appropriate distribution tape.
OMEGAMON could not bring up the requested dedicated OMEGAMON session because the OMEGAMON console (specified by the UNIT= start-up keyword) is not available.
If this is the first OMEGAMON console session in the address space, OMEGAMON terminates. Otherwise, the particular OMEGAMON console session terminates.
Check to see whether the terminal address is attached to another user or owned by VTAM®. Specify an available console and retry.
You can only specify TS or LS mode at OMEGAMON start-up when OMEGAMON is running under a TSO session.
OMEGAMON terminates.
Correct the MODE= parameter and restart OMEGAMON.
An OMEGAMON TSO session was altered to low-speed mode, since the OMEGAMON terminal is not a display device.
TS mode becomes LS mode.
Specify MODE=LS when starting OMEGAMON at this device.
The value specified for the ROWS= start-up parameter does not match the actual size of the OMEGAMON terminal screen.
OMEGAMON changes ROWS to match the terminal size; initialization continues.
Specify a ROWS= value that matches your terminal’s physical characteristics at OMEGAMON start-up.
The RKOMPCSV DD statement consists of more than one data set.
MVS data management constraints prevent OMEGAMON from performing any PDS updates to RKOMPCSV. OMEGAMON ignores requests by the /SAVE and /REP INFO-line commands and the DELT and RENM immediate commands.
Remove the concatenated data sets from the RKOMPCSV DD statement and restart OMEGAMON.
A /SAVE or /REP command failed due to a security problem.
The command terminates.
Consult your security coordinator to gain access to the data sets in the xxPROC DD statement.
OMEGAMON was unable to GETMAIN enough virtual storage to complete initialization.
Start-up fails.
Increase the region size address space and restart OMEGAMON. (See message OB0970).
Initialization failed because OMEGAMON needed additional virtual storage.
OMEGAMON terminates.
Increase the REGION= parameter by the amount that this message indicates and restart OMEGAMON. (See message OB0969.)
This ruler appears below message OB0972 to help you locate PARM line errors. The following additional message text displays below the ruler line, followed by the column location of the error, except when the error is in column 1.
The OMEGAMON session terminates.
Examine the message text and make suitable corrections. Additional message text:
OMEGAMON issues this message with OB0971 (see above).
OMEGAMON terminates.
See the error code for OB0971.
This level of OMEGAMON (nnn) is incompatible with this level of VM (yyy).
OMEGAMON initialization continues, but with unpredictable results.
If OMEGAMON did not terminate itself, stop it, install the correct OMEGAMON level, and restart OMEGAMON.
OMEGAMON attempted to load module aaaaaaaa, but could not find it in the load library.
The load fails and OMEGAMON issues an abend code 0974.
Check that module aaaaaaaa is in the load library.
OMEGAMON could not update the module aaaaaaaa because it resides in a store-protected subpool.
OMEGAMON terminates.
Relink module aaaaaaaa without the RENT linkage editor parameter.
OMEGAMON was unable to locate proper ASCB during RMF search.
The process terminates.
Contact IBM Software Support.
The user security exit has explicitly requested that SMF and/or WTO auditing be suppressed for this session; this request is made at initialization and/or relogon time. This message only appears once.
The command terminates.
None. This is an informational message and does not require further action. Typically, this type of message clarifies some aspect of system behavior during normal operations.
An external security routine passed back a non-zero return code to initialization.
OMEGAMON terminates.
See your security officer.
The product module could not be loaded successfully.
OMEGAMON terminates.
Be sure the named module is in the product library. See accompanying MVS system messages and take appropriate action. If it is not in the product library, contact IBM Software Support.
The save area stack overflowed.
The command terminates.
Contact IBM Software Support.
A validation error occurred while loading the command table module.
OMEGAMON terminates.
Contact IBM Software Support.
An error occurred while loading the command tables.
This is a secondary message. It follows messages that contain validation error information.
Examine the previous errors and follow the recommended user responses.
The usual cause of this message is insufficient region size for OMEGAMON to load the command table module.
OMEGAMON aborts the session start.
See your installer to increase the region size. For other possible causes, look up the abend code in the IBM System Codes manual for your system. You may also need to refer to the IBM System Messages manual.
An error occurred in command table processing.
OMEGAMON terminates.
Contact IBM Software Support.
Invalid stack release by a command.
OMEGAMON terminates the command execution.
This is an internal error. Contact IBM Software Support.
The request for storage for a copy of the command module failed.
OMEGAMON terminates.
Increase the region size for OMEGAMON.
The product initialization routines have returned an error code which is non-zero.
OMEGAMON terminates.
Read any other messages that accompany this message. If unable to find the problem, contact IBM Software Support.
The base driver module cannot service the current product.
OMEGAMON initialization stops.
Use a base driver which is at the same or greater level than the product you are trying to initialize. Retry using this new driver.
The user assembled an old KOBCICSUSER module that is incompatible with the current release of OMEGAMON.
OMEGAMON initialization stops.
Obtain the current KOBCICSUSER from the product tape and reassemble.
The security settings of the command table produce this security logging message. The variable cccccccc is the command being validated and aaaaaaa is the result. The userid is displayed if AUDIT=WTO is specified.
OMEGAMON terminates execution of any command to which it denies access.
None. This is an informational message and does not require further action. Typically, this type of message clarifies some aspect of system behavior during normal operations.
A dynamic allocation request failed with the ERROR and INFO codes indicated.
The allocation process terminates.
Examine the error and information codes in the message and take appropriate action.
The user profile aaUSERbb did not pass product validation.
Session initialization terminates.
If other messages were issued previously, take the action suggested for those messages. If no other messages were issued, contact IBM Software Support.
A valid argument was not supplied for the command.
The command terminates.
Supply a valid argument and reissue the command.
A valid pattern was not supplied for the command.
The command terminates.
Supply a valid pattern and reissue the command.
A non-zero return code was received from SVC 83 while attempting to track an audited command. These codes are documented in the IBM System Programming Library: System Management Facilities (SMF) manual for your system.
A WTO is issued to the console with audit information.
Consult the appropriate IBM documentation for an explanation and interpretation of the non-zero return code. This return code may indicate a serious problem with SMF.
OMEGAMON cannot write SMF records unless it is APF-authorized. This message will appear only once; thereafter, all audit activity will be directed to the console for the duration of the session.
A WTO is issued to the console with audit information.
Determine whether OMEGAMON should be authorized. This is an installation decision.
OMEGAMON detected a request to write an SMF record with an invalid record ID. User SMF records must use a record ID between 128 and 255, inclusive. This message will appear only once; thereafter, all audit activity will be directed to the console for the duration of the session.
A WTO is issued to the console with audit information.
Use the Security Update Program to specify a valid SMF record ID.
OMEGAMON could not locate the user security routine to process a command for which external security was requested. Internal security was not invoked because the command did not have a security level associated with it.
OMEGAMON suppresses command execution.
Determine why the user security routine is missing. Make sure it is in a link-list library or in the OMEGAMON STEPLIB.
The requested collector is not currently active.
The IPRO command processor suppresses the display.
Start the collector and retry the command.