OB1116 REQUEST NOT SUPPORTED
Explanation
The request is not supported by the target collector.
System action
The IPRO command processor suppresses the display.
User response
Correct the parameters and retry the request.
OB1120 REQUESTED DATA NOT VALID
Explanation
The IPRO collector’s data is currently statistically invalid. Sufficient data has not yet accumulated for a meaningful display.
System action
The IPRO command processor suppresses the display until enough samples have accumulated.
User response
Wait for sufficient time to gather data. 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.
OB1124 REQUESTED DATA NOT AVAILABLE
Explanation
The requested data is not being collected at this time.
System action
The IPRO command processor suppresses the display.
User response
Stop and restart the collector requesting the required data, or correct the collector start-up parameters and retry the request.
OB1140 REQUEST INCONSISTENT OR UNDEFINED
Explanation
The IPRO display parameters are not valid, so the processor suppresses the display.
System action
The extractor was unable to process the parameters successfully.
User response
Correct the parameters and retry.
OB1148 SUCCESSFUL ABEND RECOVERY IN EXTRACTOR
Explanation
An error occurred in the IPRO data display extractor. No presentation is made during this cycle.
System action
The IPRO command processor suppresses the display.
User response
Contact IBM Software Support.
OB1191 UNABLE TO LOAD IANL PROCESSOR MODULE
Explanation
OMEGAMON could not find the Impact Analysis processor module to load.
System action
The IPRO command processor suppresses the display.
User response
If this module should be available, contact IBM Software Support.
OB1195 MISSING EXTRACTOR NAME
Explanation
No extractor identification was given to the IPRO command processor. Either this is the first time the command was used, or it was cleared by the first extractor and there are no new operands.
System action
The IPRO command processor suppresses the display.
User response
Supply a proper extractor ID.
OB1196 DATA EXTRACTOR ADDRESS = 0 - xxxx
Explanation
The IPRO display processor for xxxx could not be located in this set of OMEGAMON modules.
System action
The IPRO command processor suppresses the display.
User response
Contact IBM Software Support.
OB1197 UNKNOWN RETURN CODE FROM EXTRACT - cc
Explanation
The IPRO display processor returned the code cc which is unknown to the IPRO command.
System action
The IPRO command processor suppresses the display.
User response
Contact IBM Software Support.
OB1198 INVALID PARAMETER - cccc
Explanation
The first 4 characters (cccc) of the operand are invalid.
System action
The IPRO command processor suppresses the display.
User response
Specify a valid IPRO collector and retry.
OB1199 IPRO COMMAND NOT SUPPORTED
Explanation
The IPRO command is not supported at this product level. IPRO requires DEXAN.
System action
The IPRO command processor suppresses the display.
User response
Contact IBM Software Support.
OB1200 SEVERE ISPF ERROR DETECTED
Explanation
ISPF has returned a severe error condition code to the OMEGAMON ISPF driver.
System action
The ISPF session terminates.
User response
Look for other messages and take appropriate action.
OB1201 TSO SERVICE ERROR RETURN CODE nnn
Explanation
The TSO service task has returned the error code indicated.
System action
The ISPF session terminates.
User response
Examine the error code and take appropriate action. Refer to the IBM® manual, TSO Extensions User’s Guide.
OB1202 ATTACH FAILED FOR MONITOR TASK
Explanation
ISPF issued a non-zero return code in response to /ATTACH.
System action
The ISPF session terminates.
User response
Examine the return code and take appropriate action.
OB1203 MONITOR TASK COMPLETE, RETURN CODE = cc
Explanation
The monitor task (OMEGAMON) terminated with the indicated return code.
System action
The task terminates.
User response
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.
OB1204 MONITOR TASK ABENDED, COMPLETION CODE = cc
Explanation
The monitor task (OMEGAMON) terminated with the indicated abend code.
System action
The task terminates.
User response
Contact IBM Software Support.
OB1210 PARM STRING LENGTH ERROR
Explanation
The PARM string entered was too long, causing internal buffer overflow.
System action
The task terminates.
User response
Shorten the PARM string and retry the command.
OB1211 UNABLE TO LOAD ISPLINK MODULE
Explanation
The ISPF driver module was unable to load ISPLINK, the ISPF interface.
System action
The task terminates.
User response
Make sure a copy is available to the ISPF driver.
OB1212 PANEL OMSPF01 NOT FOUND
Explanation
The SPF driver module could not find the OMSPF01 panel.
System action
The task terminates.
User response
Be sure the panel is in the correct ISPF library and retry.
OB1213 VARIABLE OMSPFD NOT IN PANEL OMSPF01
Explanation
The OMSPFD variable was not in the panel.
System action
The task terminates.
User response
Make sure that the correct panel is installed and that user changes have not caused this field to be omitted.
OB1214 INSUFFICIENT SPACE FOR PQUERY FUNCTION
Explanation
ISPF indicated a short-on-storage condition.
System action
The task terminates.
User response
Increase the TSO address space region and retry.
OB1215 DATA TRUNCATION HAS OCCURRED
Explanation
Internal data truncation occurred within a panel variable.
System action
The task terminates.
User response
Make sure that the variable lengths shown in the panel have not been changed.
OB1216 VARIABLE NOT FOUND
Explanation
A variable that the ISPF driver requires could not be found in the ISPF subpools.
System action
The task terminates.
User response
This is an internal error. Contact IBM Software Support.
OB1217 INVALID SCREEN SIZE
Explanation
The screen parameters are invalid for ISPF mode. COLS and ROWS must match the TSO specification for the device.
System action
The task terminates.
User response
Correct the screen specification parameters (COLS and ROWS) and restart.
OB1220 UNKNOWN RETURN CODE FROM ISPLINK
Explanation
ISPLINK returned a code 20 or above to the calling task.
System action
The task terminates.
User response
Contact IBM Software Support.
OB1250 cccccccc STORAGE REQUEST FAILED
Explanation
The request for storage for module cccccccc failed.
System action
The TSO or ISPF mode task terminates.
User response
Increase the region size for the TSO address space.
OB1251 ATTACH FAILED FOR cccccccc, RETURN CODE = xx
Explanation
A non-zero return code from ATTACH of module cccccccc was received.
System action
The TSO or ISPF mode task terminates.
User response
Examine the error code and call your systems support. If the problem persists, contact IBM Software Support.
OB1252 MODULE ABENDED, COMPLETION CODE = xxx
Explanation
The module abended with the indicated return code.
System action
The application using the module is terminated.
User response
Examine the abend code and call your systems support. If the problem persists, contact IBM Software Support.
OB1253 SET STFSMODE ON FAILED AT INITIALIZATION
Explanation
OMEGAMON could not set full-screen mode on as requested for TSO mode.
System action
The task terminates.
User response
Contact IBM Software Support.
OB1254 SET STTMPMD OFF FAILED AT INITIALIZATION
Explanation
OMEGAMON could not set display manager off as requested for TSO mode.
System action
The task terminates.
User response
Contact IBM Software Support.
OB1255 SET STFSMODE OFF FAILED AT TERMINATION
Explanation
OMEGAMON could not set full-screen mode off as requested for TSO mode.
System action
The task terminates.
User response
Contact IBM Software Support.
OB1256 SET STTMPMD ON FAILED AT TERMINATION
Explanation
OMEGAMON could not set display manager on as requested for TSO mode.
System action
The task terminates.
User response
Contact IBM Software Support.
OB1257 {TSO|ISPF} MODE TASK TERMINATED
Explanation
The task completed its processing with a normal termination.
System action
The TSO or ISPF mode task terminates.
User response
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.
OB1258 cccccccc FREE STORAGE REQUEST FAILED
Explanation
The free storage request has failed in module cccccccc.
System action
The task terminates.
User response
Examine the error code in the SYSLOG. If the problem persists, contact IBM Software Support.
OB1259 LOAD cccccccc FAILED
Explanation
The load request for module cccccccc has failed.
System action
The task terminates.
User response
Examine the error code in the SYSLOG. Ensure that load module cccccccc is in the proper load library. If the problem persists, contact IBM Software Support.
OB1260 DELETE cccccccc FAILED
Explanation
The delete request for module cccccccc has failed.
System action
The task terminates.
User response
Contact IBM Software Support.
OB1261 GTTERM FAILED
Explanation
The request to get terminal attributes has failed.
System action
The task terminates.
User response
Contact IBM Software Support.
OB1401 MISSING USER ID
Explanation
The user ID field in the logon panel is missing.
System action
OMEGAMON redisplays the logon panel.
User response
Enter the required user ID.
OB1402 MISSING PASSWORD
Explanation
The password field in the logon panel is missing.
System action
OMEGAMON redisplays the logon panel.
User response
Enter your password.
OB1404 RE-ENTER NEW PASSWORD FOR VERIFICATION
Explanation
The system asks the user to re-enter the new password.
System action
The system waits for the user to re-enter the new password to verify that the new password is correct.
User response
Enter the new password in the new password field.
OB1405 VERIFICATION OF NEW PASSWORD FAILED
Explanation
When the password was entered a second time for verification, it did not match the new password.
System action
The system waits for the user to attempt another logon.
User response
Enter the correct password.
OB1501 INVALID ARGUMENT: cc
Explanation
The argument field contains invalid data for the command that appears above this message on the screen.
System action
OMEGAMON does not process the command.
User response
Enter appropriate data in the command argument field.
OB1502 INSUFFICIENT MEMORY FOR SCRN COMMAND
Explanation
OMEGAMON does not have sufficient memory to build the screen member name lists from the various sources (main storage, KOBCICSPROC, and RKOMPCSV) that the SCRN command displays.
System action
OMEGAMON does not process the command.
User response
Provide additional storage resources for the executing OMEGAMON.
OB1503 DATA SET EMPTY
Explanation
There were no members in the indicated KOBCICSPROC data set for the SCRN command to display.
System action
The SCRN command displays member names in the other KOBCICSPROC data sets.
User response
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.
OB1504 NO MEMBERS FOUND WITHIN RANGE (cccccccc THRU cccccccc)
Explanation
OMEGAMON found no screen names within the from/through range specified by the SCRN command.
System action
None.
User response
Enter a different from/through selection range.
OB1505 TOO MANY MEMBERS SPECIFIED
Explanation
There are too many screen space members for the LSCR command to load into main storage. The maximum number is 62.
System action
OMEGAMON does not load the screen spaces into main storage.
User response
Reduce the number of members to load.
OB1506 INVALID MEMBER NAME cccccccc
Explanation
The LSCR command detected a screen member name that is too long or that contains invalid characters.
System action
OMEGAMON does not load the screen into main storage.
User response
Correct the screen member name on the LSCR command.
OB1507 LOAD FAILED - MEMBER cccccccc NOT FOUND
Explanation
The user specified screen space cccccccc with an LSCR command; OMEGAMON did not find it in the KOBCICSPROC library.
System action
OMEGAMON ignores specification of screen space cccccccc and loads any other specified screen spaces.
User response
Make sure that the specified screen space exists in KOBCICSPROC or RKOMPCSV library. Check KOBCICSPROC concatenation.
OB1508 nnn MEMBERS LOADED
Explanation
The LSCR command successfully loaded nnn screen spaces to main storage.
System action
The command executes.
User response
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.
OB1509 ENTER MEMBER NAMES TO LOAD
Explanation
The LSCR command attempted to load screen spaces to main storage, but there were no member names specified.
System action
The command terminates.
User response
Enter member names following the LSCR command.
OB1521 MEMBER cccccccc DELETED BOTH IN-STORAGE AND FROM RKOMPCSV
Explanation
The user specified screen space cccccccc with a DELTB command, and OMEGAMON successfully deleted it from main storage (in-storage) and RKOMPCSV.
System action
The command executes.
User response
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.
OB1522 MEMBER NAME - cccccccc NOT FOUND IN-STORAGE
Explanation
The user specified screen space cccccccc with a DELTI or DELTB command; OMEGAMON did not find it in main storage (in-storage).
System action
None.
User response
Verify that the screen space name is correct.
OB1523 MEMBER cccccccc DELETED IN-STORAGE
Explanation
OMEGAMON successfully deleted screen space cccccccc from main storage (in-storage) as a result of DELTB or DELTI command.
System action
The command executes.
User response
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.
OB1524 MEMBER cccccccc DELETED FROM RKOMPCSV
Explanation
OMEGAMON successfully deleted screen space cccccccc from RKOMPCSV as a result of DELTB or DELTD command.
System action
The command executes.
User response
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.
OB1525 DELETE FAILED - cccccccc NOT FOUND IN RKOMPCSV
Explanation
The user specified screen space cccccccc with a DELTB or DELTD command, and OMEGAMON did not find it in RKOMPCSV.
System action
None.
User response
Verify that the screen space name is correct.
OB1531 MEMBER oldname RENAMED TO newname BOTH IN-STORAGE AND IN RKOMPCSV
Explanation
The user specified screen space oldname with a RENMB command, and OMEGAMON successfully renamed it to newname in main storage (in-storage) and in RKOMPCSV.
System action
The command executes.
User response
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.
OB1532 MEMBER NAME - cccccccc NOT FOUND IN-STORAGE
Explanation
The user specified screen space cccccccc with a RENMI or RENMB command; OMEGAMON did not find it in main storage (in-storage).
System action
None.
User response
Verify that the screen space name is correct.
OB1533 MEMBER oldname RENAMED TO newname IN-STORAGE
Explanation
OMEGAMON successfully renamed screen space oldname to newname in main storage (in-storage) as a result of RENMI or RENMB command.
System action
The command executes.
User response
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.
OB1534 MEMBER oldname RENAMED TO newname IN RKOMPCSV
Explanation
OMEGAMON successfully renamed screen space oldname to newname in RKOMPCSV as a result of a RENMD or RENMB command.
System action
The command executes.
User response
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.
OB1535 RENAME FAILED - cccccccc NOT FOUND IN RKOMPCSV
Explanation
The user specified screen space cccccccc on a RENMD or RENMB command, and OMEGAMON did not find it in main storage (in-storage).
System action
None.
User response
Verify that the screen space name is correct.
OB1537 RENAME FAILED - cccccccc DIRECTORY FULL
Explanation
The PDS directory for file cccccccc is full and cannot contain additional screen space names.
System action
OMEGAMON does not rename the screen space in RKOMPCSV.
User response
Compress the PDS library or provide additional directory space.
OB1538 RENAME FAILED - cccccccc ALREADY EXISTS IN-STORAGE
Explanation
The user issued a RENMI or RENMB command with a screen space name cccccccc that already exists in main storage (in-storage) and cannot be renamed.
System action
OMEGAMON does not change the original screen space name.
User response
Correct the new screen space name and retry the command.
OB1539 RENAME FAILED - cccccccc ALREADY EXISTS IN RKOMPCSV
Explanation
The user issued a RENMD or RENMB command with a screen space name cccccccc that already exists in RKOMPCSV and cannot be renamed.
System action
OMEGAMON does not change the original screen space name.
User response
Correct the new screen space name and retry the command.
OB2001 DATA-ONLY SPACE cccccccc DOES NOT EXIST
Explanation
The data-only space cccccccc specified in the command cannot be found. cccccccc is the name of the data-only space or the first 1–7 characters of the data-only space name. If cccccccc is displayed in the message as less than 8 characters, it means that there were no data-only spaces found beginning with the characters cccccccc.
System action
The command is terminated.
User response
Correct the data-only space name and reissue the command. The PEEK command may be used to find the names of data-only spaces owned by a job.
OB2002 DATA-ONLY SPACE cccccccc IS NOT OWNED BY JOB aaaaaaaa
Explanation
Job aaaaaaaa is not the owner of data-only space cccccccc. aaaaaaaa is the jobname given in the command or the name of the job identified by the ASID.
System action
The command terminates.
User response
Correct the data-only space name, the jobname, or ASID and reissue the command. The PEEK command may be used to find the names of data-only spaces owned by a job’s TCBs. The OSPC command may be used to find the jobname and ASID of the owning TCB of a data-only space.
OB2003 aaaaaaaa cccccccc HAS BEEN DELETED
Explanation
The TCB owning data-only space aaaaaaaa of type cccccccc has deleted the space or has itself been terminated. The space no longer exists.
System action
The command is terminated.
User response
None.
OB2005 DATA-ONLY SPACE PROCESSING UNAVAILABLE - RC=nnnn
Explanation
Due to an internal OMEGAMON error, OMEGAMON is unable to perform data-only space processing.
System action
The command terminates.
User response
Contact IBM Software Support with the return code.
OB2006 DATA-ONLY SPACE NAME MUST BE 8 CHARACTERS OR LESS
Explanation
A data-only space name of greater than 8 characters was entered as input.
System action
The command terminates.
User response
Correct the name of the data-only space. The OSPC command may be issued to obtain the name of all data-only spaces in the system.
OB2007 DATA-ONLY SPACE NAME IS A REQUIRED PARAMETER
Explanation
A data-only space command (e.g., SLST, SZAP) was issued without the name of a data-only space as input.
System action
The command terminates.
User response
Correct the command input by supplying a data-only space name as the second parameter. The OSPC command may be issued to obtain the name of all data-only spaces in the system.
OB2008 ALESERV ADD NON-ZERO RETURN CODE, RC = nn
Explanation
An attempt to obtain addressability to a data space failed with return code nn.
System action
The command terminates.
User response
Ensure that the data space input to the affected command has not been deleted. If the data space still exists, contact IBM Software Support.
OB2009 HSPSERV return code, RC = xx
Explanation
An attempt to access a Hiperspace™ failed with return code xx.
System action
The command terminates.
User response
Contact IBM Software Support.
OB2010 ACCESS TO aaaaaaaaaa cccccccc IS NOT AUTHORIZED
Explanation
An attempt was made to access a non-shareable data-only space aaaaaaaa of type cccccccc without authorization.
System action
The command terminates.
User response
Authorization may be obtained to non-shareable data-only spaces by issuing the command .DSAON.
OB2011 ACCESS TO DATA SPACE aaaaaaaa DENIED, SCOPE UNKNOWN
Explanation
An attempt was made to access data space aaaaaaaa, but OMEGAMON was not able to determine the SCOPE of the data space.
System action
The command terminates.
User response
Contact IBM Software Support.
OB2100 RMF SUBROUTINE LOAD MODULE OBRMFSnn NOT AVAILABLE
Explanation
OMEGAMON attempted to access module OBRMFSnn but failed.
System action
The command terminates.
User response
Check to make sure that the OBRMFSnn modules were copied from the OMEGAMON distribution tape. If the modules are in the OMEGAMON load library, contact IBM Software Support.
OB2101 RMF LEVEL nnnnn IS NOT IN TABLE
Explanation
An attempt was made to set the RMF level to a level that OMEGAMON did not recognize.
System action
The command terminates.
User response
Check to make sure that the correct RMF level is entered on the input screen. If it is entered correctly but OMEGAMON does not recognize it, contact IBM Software Support. You may need to receive support for a new level of RMF.
OB2102 INPUT MUST BE EITHER nnn OR n.n.n
Explanation
The operand on the RMFS command must have the format nnn or n.n.n.
System action
The command terminates.
User response
Correct the input to the RMFS command and press ENTER.
OB2103 RMF LEVEL HAS BEEN DYNAMICALLY DETERMINED - COMMAND INVALID
Explanation
OMEGAMON determined the level of RMF dynamically. RMFS cannot be used to override the RMF level in this situation.
System action
The command terminates.
User response
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.
OB2104 RMF LEVEL UNCHANGED - UNABLE TO LOAD MODULE nnnnnnnn
Explanation
An attempt was made to change to a new level of RMF, however, the required load module was not available.
System action
The command terminates. The RMF level stays unchanged.
User response
Make sure that the load module is copied from the installation tape. If the module is not on the tape, contact IBM Software Support.
OB2200 SUBSYSTEM aaaa REQUEST RETURNED RC=bbbb AND ERRCODE cccccccc
Explanation
A call to the Candle Subsystem has resulted in a non-zero return code.
- aaaa
- Identifies the type of request: INIT or REQ.
- bbbb
- Identifies the return code.
- 4
- Internal error
A common cause of this return code is a version or maintenance level mismatch between the running Candle subsystem and the product issuing the message. If you have multiple SMP/E environments make sure that all have the same Candle subsystem FMID and maintenance installed.
- 8
- Subsystem not active
- 20
- Subsystem module not found
- cccccccc
- Identifies the error code.
System action
The interface to the Candle Subsystem returns the address of the static device table that might be obsolete. You may also need a later version of the Candle Subsystem.
User response
Contact IBM Software Support.
OB4101 MEMORY FOR USER PROFILE TABLES NOT AVAILABLE
Explanation
There is not enough memory available for the user profile tables.
System action
The command terminates.
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 terminates.
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 above.)
System action
OMEGAMON terminates.
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
OMEGAMON® uses 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 OMEGAMON startup 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 OMEGAMON for 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 terminates.
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
OMEGAMON ignores 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.