OB4101 MEMORY FOR USER PROFILE TABLES NOT AVAILABLE
Explanation
There is not enough memory available for the user profile tables.
System action
The command stops.
User response
Increase the region size and retry.
OB4222 UNABLE TO LOCATE REQUIRED LEVEL-DEPENDENT BASE MODULE KOBASnnn
Explanation
OMEGAMON attempted to locate the corresponding base module required for the current operating system level. The required module could not be found.
System action
OMEGAMON stops.
User response
Make sure that OMEGAMON is executed at the operating system level for which your installation is licensed. Contact IBM® Corporation for licensing and sales information.
OB4223 CURRENT OPERATING SYSTEM LEVEL NOT SUPPORTED
Explanation
OMEGAMON has determined that the current operating system level is not supported. Only MVS/SP™ 1, 2, and 3 are supported; earlier versions are not supported. (SP™ 1 support is further limited to SP 1.3 and higher.)
System action
OMEGAMON stops.
User response
Run OMEGAMON only on those systems with supported operating system levels.
OB7001 OVUSERcc DATA FILE NOT FOUND
Explanation
The OVUSERcc DATA file specified by USER xx in the startup parms or the .USR command was not found.
System action
OMEGAMONuses all default values for execution parameters. The default OVUSER DATA file is 99.
User response
Continue with OMEGAMON initialization or restart OMEGAMON specifying the correct USER startup parameter value, or reissue the .USR command specifying the correct parameter.
OB7002 INVALID SWITCH SETTING - MUST BE ON OR OFF
Explanation
The indicated parameter must be specified as either ON or OFF.
System action
OMEGAMON uses the default value.
User response
Correct the parameter value to specify ON or OFF at next execution.
OB7003 INVALID PARAMETER
Explanation
The indicated word is not a valid OMEGAMONstartup parameter.
System action
OMEGAMON ignores the entire parameter group (including any possible subordinate keywords).
User response
Check for spelling problems. Check to make sure that a previous parameter was not continued incorrectly.
OB7004 INVALID SYNTAX
Explanation
The format of the indicated input stream is invalid.
System action
OMEGAMON ignores either all or part of the current parameter group.
User response
Correct the formatting error. Ensure that all required delimiters (commas, parentheses, and so on) are entered correctly.
OB7005 INVALID CHARACTER - ACCEPTED AS DELIMITER
Explanation
An invalid character was found in the input stream.
System action
The character is assumed to be a delimiter.
User response
Enter a valid character if a delimiter was not intended.
OB7006 INVALID KEYWORD
Explanation
The indicated word is not a valid keyword for the current parameter group being processed.
System action
OMEGAMON ignores the keyword.
User response
Check for possible spelling or continuation errors.
OB7007 INVALID KEYWORD VALUE
Explanation
The value specified for the indicated parameter keyword is invalid.
System action
OMEGAMON ignores the keyword.
User response
Specify the keyword value as required.
OB7008 INVALID HEX DATA
Explanation
EBCDIC characters were specified for a keyword requiring hexadecimal data.
System action
OMEGAMON ignores the keyword.
User response
Correct the keyword value.
OB7009 INVALID NUMERIC DATA
Explanation
EBCDIC characters were specified for a keyword requiring numeric data.
System action
OMEGAMON ignores the keyword.
User response
Correct the keyword value.
OB7010 KEYWORD VALUE OR LENGTH BELOW ALLOWED MIN
Explanation
The value specified for the indicated keyword is either too short (character) or too small (integer or hex).
System action
OMEGAMON ignores the keyword.
User response
Check the minimum that can be specified for the keyword and correct the keyword value.
OB7011 KEYWORD VALUE OR LENGTH ABOVE ALLOWED MAX
Explanation
The value specified for the indicated keyword is either too long (character) or too large (integer or hex).
System action
OMEGAMON ignores the keyword.
User response
Check the maximum that can be specified for the keyword and correct the keyword value.
OB7012 DUPLICATE PARAMETER
Explanation
A duplicate keyword has been found in the input stream.
System action
OMEGAMON ignores the duplicate parameter.
User response
Remove or correct the duplicate keyword.
OB7013 MISSVM LIMIT EXCEEDED
Explanation
The internal buffers required to hold the data specified by the OVUSER MISSVM parameter have overflowed.
System action
The MISSVM keyword specifications that will fit in storage will be accepted with the remainder ignored.
User response
Increase the virtual storage size of the OMEGAMONfor VM virtual machine or specify few MISSVM keyword values.
OB7014 MISSDA LIMIT EXCEEDED
Explanation
The internal buffers required to hold the data specified by the OVUSER MISSDA parameter have overflowed.
System action
The MISSDA keyword specifications that will fit in storage will be accepted with the remainder ignored.
User response
Increase the virtual storage size of the OMEGAMON for VM virtual machine or specify few MISSDA keyword values.
OB7017 USERID OR ACCOUNT NOT SPECIFIED
Explanation
For the PGNAMES parameter a USERID= or ACCOUNT= keyword was expected and not found.
System action
OMEGAMON ignores the entire PGNAMES parameter group.
User response
Check for a spelling error to ensure that either a USERID= or an ACCOUNT= keyword is specified.
OB7018 UNEXPECTED END-OF-FILE RECEIVED
Explanation
While processing a continuation, the end of the OVUSERcc DATA file was reached.
System action
OVUSERcc parameter processing stops.
User response
Check to see if the OVUSER DATA file is complete. If not, enter the missing parameter keyword(s).
OB7019 NAME= KEYWORD MISSING
Explanation
The NAME keyword was not specified on the PGNAME statement.
System action
OMEGAMON ignores the entry.
User response
The PGNAME statement requires a name for each group being defined. Specify a name.
OB7020 UNBALANCED OR INVALID USE OF PARENTHESES
Explanation
Either an unexpected parenthesis was detected or an expected parenthesis was not detected.
System action
OMEGAMON ignores either the current keyword or the remaining parameter keywords.
User response
Add or remove parentheses as required.
OB7021 MAXIMUM 64 PERFORMANCE GROUP NAMES ALLOWED
Explanation
For the PGNAMES parameter group more than 64 performance groups were specified.
System action
OMEGAMON ignores the remaining performance groups.
User response
Remove less important performance groups so that the maximum will not be exceeded.
OB7022 INVALID cccccccc THRESHOLD GROUP KEYWORD
Explanation
A keyword for the DEFVMTG, DASDTG, or RSCSTG parameter was entered that is not a valid exception override name.
System action
OMEGAMONignores the keyword.
User response
Check for a possible spelling error. For DEFVMTG, ensure that the exception name entered is a valid VM exception and not a SYSTEM exception. For DASDTG, ensure that the exception name entered is one of the DASD exceptions. For RSCSTG, ensure that the exception name entered is RSCA or RSCQ.
OB7023 ON/OFF EXPECTED, ON ASSUMED
Explanation
The indicated parameter must be specified as either ON or OFF.
System action
The keyword value defaults to ON.
User response
Correct the parameter value to specify ON or OFF.
OB7024 EXPECTED PARENTHESIS NOT FOUND
Explanation
A parenthesis was expected at or near the column indicated by an asterisk.
System action
OMEGAMON ignores the current keyword.
User response
Check the format for the keyword and make the appropriate corrections.
OB7025 EXPECTED ON OR AUTO, AUTO ASSUMED
Explanation
The indicated parameter must be specified as either ON or AUTO.
System action
Missing VM analysis for this VM user ID defaults to AUTO.
User response
Correct the parameter value to specify ON or AUTO.
OB7026 THRESHOLD EXCEEDS THE MAXIMUM ALLOWED, MAXIMUM WILL BE USED
Explanation
The value specified for the THRESH= keyword is larger than the value allowed for an exception name.
System action
OMEGAMON uses the maximum value allowed.
User response
Check the maximum value for this exception name and correct the keyword value.
OB7027 THRESHOLD LESS THAN MINIMUM ALLOWED, MINIMUM WILL BE USED
Explanation
The value specified for the THRESH= keyword is less than the value allowed for an exception name.
System action
OMEGAMON uses the minimum value allowed.
User response
Check the minimum value for this exception name and correct the keyword value.
OB7028 EXPECTED TIME=SS OR SL= KEYWORD NOT RECEIVED
Explanation
An invalid keyword was received for the TSF parameter group. The only valid keywords are TIME=, and either SS= or SL=.
System action
OMEGAMON ignores the remaining TSF keywords.
User response
Check for possible spelling problems.
OB7029 BOX= KEYWORD INVALID FOR VM EXCEPTIONS. ENTER OK TO CONTINUE OR C TO CANCEL.
Explanation
The BOX= keyword was specified and is not valid for a VM exception.
System action
OMEGAMON ignores the BOX= keyword.
User response
Reply OK or C, then remove the BOX= keyword from this exception.
OB7030 CHNM CPUID INVALID
Explanation
The value specified for the CPUID= keyword is invalid (must be between 0 and 15) for the CHNM parameter group.
System action
OMEGAMON skips the CPUID= keyword and subsequent CHANNELS= keywords.
User response
Specify the correct CPU identification.
OB7031 CHNM CHANNEL NUMBER INVALID
Explanation
One of the values specified for the CHANNELS= keywords is invalid for the CHNM parameter group (must be between 0 and 31).
System action
OMEGAMON ignores the channel ID value.
User response
Specify the correct channel ID.
OB7032 CPUID= KEYWORD MISSING
Explanation
The CPUID= keyword for the CHNM parameter group was expected and not received.
System action
OMEGAMON ignores the subsequent CHANNELS= parameter.
User response
Check for spelling errors or enter a CPUID= keyword preceding the CHANNELS= keyword.
OB7033 CHANNELS= KEYWORD MISSING
Explanation
The CHANNELS= keyword for the CHNM parameter group was expected and not received.
System action
OMEGAMON ignores the current CPUID= value.
User response
Check for spelling errors or enter a CHANNELS= keyword following the CPUID= keyword.
OB7036 DUPLICATE KEYWORD FOUND
Explanation
OMEGAMON encountered a duplicate keyword in OVUSER.
System action
OMEGAMON displays the message and asks if you wish to continue.
User response
Reply OK to continue processing and ignore the error or type C to cancel and correct the OVUSER file.
OB7037 INCLUDE OR EXCLUDE NOT SPECIFIED
Explanation
OMEGAMON requires either an INCLUDE or EXCLUDE list to be specified with the FORCE parameter in OVUSER.
System action
OMEGAMON displays the message and asks if you wish to continue.
User response
Reply OK to continue processing and ignore the error or type C to cancel and correct the OVUSER file.
OB7038 FORCE PARAMETER VALID ONLY FOR VM EXCEPTIONS
Explanation
OMEGAMON encountered the FORCE parameter on an exception that is not VM user-related. Force processing is not valid for other than user-related exceptions.
System action
OMEGAMON displays the message and asks if you wish to continue.
User response
Reply OK to continue processing and ignore the error or type C to cancel and correct the OVUSER file.
OB7039 SCREEN SPACE NOT FOUND
Explanation
The indicated screen space name (with file type PROCFILE) was not found on any accessed CMS disk.
System action
The screen space name is accepted. The error message displays as a warning.
User response
Correct the screen space name or create a new screen space with this name.
OB7040 TABLE WORK AREA OVERFLOW
Explanation
An internal storage buffer overflowed processing the indicated parameter or keyword.l
System action
Processing stops for the current parameter.
User response
Increase your virtual storage size or decrease the number of operands of this parameter.
OB7041 INTERNAL ERROR OBTAINING WORK BUFFERS
Explanation
An internal error occurred attempting to acquire storage.
System action
OVUSERcc processing stops.
User response
Call IBM Software Support Services.
OB7042 KEYWORD DOES NOT APPLY TO THIS EXCEPTION
Explanation
The indicated keyword does not pertain to the current exception name being processed.
System action
OMEGAMON ignores the keyword.
User response
Remove the keyword from this exception parameter.
OB7101 ERROR, COMMAND ARGUMENT UNKNOWN
Explanation
An invalid operand was given to the command.
System action
The command stops.
User response
For the proper operands, see the extended help (;commandname) for the command. Correct the operand and retry.
OB7102 USER TABLE HAS BEEN DELETED
Explanation
OMEGAMON deleted the user table.
System action
Processing continues.
User response
None. This is an informational message only.
OB7103 NAME NOT IN TABLE
Explanation
The requested name cannot be found in the tables.
System action
The command stops.
User response
Correct the name and retry the command.
OB7104 cccccccc HAS BEEN DELETED
Explanation
The indicated memory location symbol was deleted from the symbolic address table.
System action
Processing continues.
User response
None. This is an informational message only.
OB7105 cccccccc HAS BEEN ADDED TO THE TABLE
Explanation
The indicated memory location symbol was added to the symbolic address table.
System action
Processing continues.
User response
None. This is an informational message only.
OB7106 TABLE DOES NOT EXIST
Explanation
No entries have been defined in the table.
System action
The command stops.
User response
None. This is an informational message only.
OB7107 WORKAREA OVERFLOW
Explanation
The internal work area for string manipulation has overflowed.
System action
The command stops.
User response
Use shorter strings to define the storage locations.
OB7108 PLPA MZAP CANNOT CROSS PAGE BOUNDARY
Explanation
The zap would cross a page boundary and this is not allowed.
System action
Command stops.
User response
None. This is an informational message only.
OB7109 PLPA PAGES FIXED
Explanation
OMEGAMON fixed PLPA pages as requested.
System action
Processing continues.
User response
None. This is an informational message only.
OB7110 MEMORY ZAP SUCCESSFUL
Explanation
OMEGAMON successfully executed the MZAP command.
System action
Processing continues.
User response
None. This is an informational message only.
OB7111 VERIFY REJECT - MEMORY NOT ZAPPED
Explanation
The verify data in the command does not match the data in storage.
System action
The command stops.
User response
Correct the data and retry.
OB7112 SCAN DATA NOT FOUND
Explanation
The requested data could not be found within the scan limits.
System action
The command stops.
User response
None. This is an informational message only.
OB7113 DYNAMIC ADDRESS NOT RESOLVED
Explanation
A symbol in a dynamic address string could not be resolved.
System action
The command stops.
User response
Correct the symbol and retry the command.
OB7114 MODULE NOT AVAILABLE
Explanation
An OMEGAMON module address was found to be 0, indicating that it is not available for this command.
System action
The command stops.
User response
None. This is an informational message only.
OB7115 OMEGAMON NAME INVALID IN CROSS MEMORY
Explanation
The cross memory commands are not allowed against this address space.
System action
The command stops.
User response
Use the appropriate local commands.
OB7117 INDIRECT ADDRESS IS 0
Explanation
The address pointer value was 0 when an indirect request (? or %) was encountered while interpreting the address string.
System action
The command stops.
User response
None. This is not necessarily an error.
OB7118 JOB NOT FOUND
Explanation
The requested address space or jobname cannot be found.
System action
The command stops.
User response
Correct the name and retry.
OB7119 REGION DOES NOT BELONG TO CL/SUPERSESSION and CL\GATEWAY
Explanation
A cross-memory zap was attempted on an unauthorized region.
System action
The command stops.
User response
Make sure that the zap is being applied to the correct region.
OB7120 USE cccc FOR OMEGAMON PRIVATE AREA
Explanation
A cross memory command was used where a local command is appropriate.
System action
The command stops.
User response
Use the local command format.
OB7121 ADDRESS IN COMMON AREA - USE cccc
Explanation
A cross memory command was used where a local command is appropriate.
System action
The command stops.
User response
Use the local command format.
OB7122 GENERATED ADDRESS INVALID - xxxxxxxx
Explanation
The displayed address was developed while interpreting the address string. It is not valid for the named address space.
System action
The command stops.
User response
Correct as necessary.
OB7123 TARGET ADDRESS INVALID - xxxxxxxx
Explanation
The displayed address was used to fetch data and is not a valid target address.
System action
The command stops.
User response
Correct and retry.
OB7125 VERIFY FAILED - ACTUAL CODE WAS: nn
Explanation
The verify data does not match the storage data.
System action
The command stops.
User response
Correct and retry.
OB7126 INVALID RETURN CODE - cc = nn
Explanation
The SRB that was scheduled returned an unknown code.
System action
The command stops.
User response
Contact IBM Software Support.
OB7127 {TARGET|INDIRECT} ADDRESS xxxxxxxx IS STORE PROTECTED
Explanation
The target/indirect address xxxxxxxx is store-protected and should not be modified.
System action
The command stops.
User response
Use the action character if APF-authorized and retry.
OB7128 {TARGET|INDIRECT} ADDRESS xxxxxxxx IS FETCH PROTECTED
Explanation
The target/indirect address xxxxxxxx is fetch-protected and cannot be read.
System action
The command stops.
User response
Use the action character if APF-authorized and retry.
OB7129 {TARGET|INDIRECT} ADDRESS xxxxxxxx DOES NOT EXIST
Explanation
The target/indirect address xxxxxxxx cannot be located.
System action
The command stops.
User response
Correct the address and retry.
OB7130 TRUNCATION HAS OCCURRED AT PAGE BOUNDARY
Explanation
The current display truncated because of an invalid address. The next page of storage is either undefined or fetch-protected.
System action
The command stops.
User response
Correct the address or length and retry.
OB7131 SUBSTITUTION SYMBOL NOT DEFINED - cccccccc
Explanation
The MDEF command could not define the substitution symbol cccccccc. OMEGAMON cannot define a substitution symbol that begins with an ampersand (&).
System action
The command stops.
User response
Replace the ampersand with another character and retry the MDEF command.
OB8110 NOT ENOUGH REGION FOR WORKAREA - nnnK MORE NEEDED
Explanation
The specified command could not obtain a work area.
System action
The command stops.
User response
Increase the region size of the address space by a minimum of nnnK. Alternatively, use the WSIZ minor of PEEK or FNDU to decrease the work area size by nnnK.
OB8111 WARNING - WSIZ TOO SMALL ADDR= xxxxxx, SIZE = yyyyyy, USED =zzzzzz
Explanation
The FNDU or PEEK SRB to collect data failed to complete its task because the data area it needed was too small.
System action
None.
User response
Use the WSIZ minor of FNDU or PEEK to increase the work area.
OB8112 DATA COLLECTION INITIATED
Explanation
The command was issued with the action character, and OMEGAMON was collecting.
System action
None.
User response
None. This is an informational message only.
OB8113 WARNING cccc FAILED VALIDITY CHECK
Explanation
The SRB to collect data failed to complete its task because a control block does not contain valid data. The variable cccc is one of the following control blocks:
- ASCB
- DSAB
- JFCB
- JFCX
- TCB
System action
None.
User response
Re-enter the command. You may want to list the control block and verify its contents.
OB8114 WARNING - POSSIBLE LOOP DETECTED IN SRB ROUTINE
Explanation
The SRB to collect data failed to complete its task (possibly because the SRB is in a loop). xxxx is the hex offset into the PEEK module.
System action
None.
User response
If the problem persists, contact IBM Software Support.
OB8115 WARNING - INVALID RETURN CODE - RC = nn
Explanation
The SRB routine returned a nonstandard code.
System action
The PEEK process stops.
User response
If the error persists, contact IBM Software Support.
OB8116 DANGER - INSUFFICIENT SQA, COMMAND ABORTED
Explanation
There is insufficient SQA.
System action
The command aborts.
User response
Try the command later when more SQA is available.
OB8117 INSUFFICIENT MEMORY FOR SRB SAVE AREA
Explanation
There is insufficient memory for the save area.
System action
The command stops.
User response
Try the command later when there is more memory available.
OB8118 SRBD - SRB FAILED DURING INITIALIZATION
Explanation
The SRB failed during initialization.
System action
The command stops.
User response
Contact IBM Software Support.
OB8121 CHANNEL SET NOT DEFINED
Explanation
The user requested an invalid channel set.
System action
Command processing stops.
User response
Correct command parameters and retry.
OB8130 COMMAND TEXT IS TOO LONG
Explanation
The command text can be a maximum of 126 characters.
System action
The command is not executed.
User response
Specify the command text so that it is no more than 126 characters.
OB8131 INVALID CHARACTER AFTER SYSTEM NAME
Explanation
The system name was not followed by a blank space or by a comma.
System action
The command is not executed.
User response
Supply a system name followed by a blank space or a comma.
OB8132 SYSTEM NAME IS TOO LONG, MUST BE 1–8 CHARS
Explanation
System names must be from 1–8 characters in length.
System action
The command is not executed.
User response
Supply a valid system name.
OB8202 CPU NOT DEFINED
Explanation
The CPU is not defined in the PCCA.
System action
None.
User response
Specify a CPU that is defined to your system (see the IBM OS/VS2 System Programming Library or MVS/Extended Architecture Debugging Handbooks for a CPU definition).
OB8203 NO CHANNEL AVAILABILITY TABLE
Explanation
The specified channel does not exist.
System action
None.
User response
Specify a channel number that exists on the system.
OB8204 LINK ERROR, CODE = {8|12}
Explanation
The external routine for GDEV encountered a link error.
System action
The command stops processing.
User response
Contact IBM Software Support.
OB8205 INVALID INPUT - aaaaaaaaaaaaaaa
Explanation
An invalid device class was entered as input to the GLST command.
System action
The GLST command is terminated.
User response
Correct the invalid input parameter. The help text for the GLST command displays the valid input parameters.
OB8206 PROCESSING ERROR, DEVICE CLASS aaaa, RC=nn
Explanation
The EDTINFO interface routine used by the GLST command returned with a non-zero return code, nn, processing device class aaaa.
System action
Processing continues, but that device class will not be displayed.
User response
Contact IBM Software Support.
OB8207 SUBSYSTEM RETURN CODE aaaaaaaa bbbbbbbb cccccccc dddddddd
Explanation
A call to the subsystem has resulted in a nonzero return code during execution of the GDEV command.
- aaaaaaaa
- Identifies the Subsystem return code.
- bbbbbbbb
- Identifies the function return code.
- cccccccc
- Identifies the subroutine invocation return code.
- dddddddd
- Identifies the subroutine invocation reason code.
System action
The GDEV command continues to process, however, there will be no data for devices defined as dynamic.
User response
Contact IBM Software Support.