OB0310 PARAMETER keyword value DATA IS INVALID
Explanation
The value associated with the keyword parameter is incorrect.
System action
OMEGAMON bypasses the parameter.
User response
Correct the parameter and retry.
The value associated with the keyword parameter is incorrect.
OMEGAMON bypasses the parameter.
Correct the parameter and retry.
The value associated with the keyword parameter is incorrect. The data does not uniquely distinguish between entries.
OMEGAMON bypasses the parameter.
Correct the parameter and retry.
The indicated parameter is not in any of the tables associated with this command.
OMEGAMON bypasses the parameter.
Correct the parameter and retry.
The data nnnn associated with parameter cccc contains too many significant digits to the right of the decimal point.
OMEGAMON bypasses the parameter.
Correct the parameter and retry.
The parameter was specified in the wrong format. It must either be specified as a single word or as a keyword followed by an equal sign (=) and a data value.
OMEGAMON bypasses the parameter.
Correct the parameter and retry.
The data xxxx associated with parameter cccccccc must contain only hex digits (0–9 and A–F).
OMEGAMON bypasses the parameter.
Correct the parameter and retry.
The data aaaaaaaaaaaa associated with parameter cccccccccccc must be either bbbbbbbbb or ddddddddd. No other values are allowed.
OMEGAMON bypasses the parameter.
Correct the parameter and retry.
The data nnnn associated with parameter cccccccc must be a numeric value. Only the digits 0–9 and a decimal point are allowed.
OMEGAMON bypasses the parameter.
Correct the parameter and retry.
The data aaaaaaaa associated with parameter cccccccc is in error. This message will be followed by additional messages explaining the error.
OMEGAMON bypasses the parameter.
Correct the parameter and retry.
The length of the character or hex string data must be within the bounds xxxxxxxx and yyyyyyyy.
OMEGAMON bypasses the parameter.
Correct the parameter and retry.
The value of the number in message OB0320 must be within the bounds cccccccc and aaaaaaaa.
OMEGAMON bypasses the parameter.
Correct the parameter and retry.
The length of the data is too long. The maximum length of any data string is 12 characters.
OMEGAMON bypasses the parameter.
Correct the parameter and retry.
An exception in the KOBCICSUSER module could not be processed because of an error in the exception analysis tables.
Exception analysis initialization terminates.
Contact IBM Software Support.
An attempt has been made to set the bell interval to more than 99 seconds.
The command terminates.
Enter a value that is less than 99 seconds.
An attempt has been made to set the bell interval to less than 5 seconds.
The command terminates.
Enter a value that is 5 seconds or more.
An internal exception analysis table is missing from the OMEGAMON module.
Exception analysis initialization terminates.
Contact IBM Software Support.
OMEGAMON requires nnnK more storage to initialize exception analysis.
The command terminates.
Run OMEGAMON in a larger region.
Exception analysis has not been initialized.
None.
Contact IBM Software Support.
OMEGAMON does not recognize the group ID supplied as a valid group ID.
OMEGAMON ignores the request.
Enter a defined group ID or define the group to OMEGAMON.
A user attempted to enter more than 25 exceptions into this group. It is not possible to have more than 25 exceptions in a single user exception group.
The command terminates.
Create a group of 25 or less exceptions.
A user entered the keyword LIST= without any exceptions.
The command terminates.
Enter the desired exceptions for the group.
A user requested the deletion of an exception from a group that does not have that exception assigned.
The command terminates.
Determine the correct exception to be deleted.
The GROUP= keyword was not entered.
The command terminates.
Enter the GROUP= keyword along with the desired group ID.
The DELETE= keyword does not have GROUP or EXCEPTION specified.
The command terminates.
Enter the DELETE= keyword with either GROUP or EXCEPTION as the option.
An undefined keyword was specified for this command.
The command terminates.
Correct the keyword and retry.
Exception group trip statistics were reset.
Last, worst, and cumulative counters were set to zero.
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 user entered an option for an exception state other than NULL, NDSP, TEST, ON, or OFF.
The command terminates.
Enter a valid option.
Exception bbbb was previously in exception group cc before being assigned to group aa.
None.
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.
Requested delete for exception group not processed, exception group is not in the table.
The command terminates.
Correct the exception group code and retry.
OMEGAMON deleted exception group cc from exception group table.
The command terminates.
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.
OMEGAMON deleted exception cccc from exception group aa. It is now available for assignment to another exception group.
The command terminates.
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 color entered was not a valid color.
The command terminates.
Enter a valid color (red, yellow, green, blue, turquoise, pink, or white).
The exception name specified was not defined.
The command terminates.
Enter a defined exception name.
A non-numeric sequence was entered for the exception.
The command terminates.
Enter a numeric sequence number.
The GROUP= parameter for the XACB command was not specified or was specified incorrectly.
The XACB command terminates.
Enter a valid group identification code.
The POSITION= keyword was entered with no value following it.
The command terminates.
Enter a correct POSITION= value.
OMEGAMON received a POSITION=nnn request that is greater than the number of entries in the table that was specified.
The command terminates.
Enter a value within the table range.
The exception group NAME is null.
The command terminates.
Enter a valid name for the exception group.
An undefined group ID was entered with no other parameters.
The command terminates.
Enter the group ID, name, and list of desired exceptions to add a new entry to the table.
An undefined keyword was entered.
The command terminates.
Correct the spelling of the keyword.
The XACB command uses the ALL, LIST, and GROUP keywords to select exceptions for display. Only one of these selection options may be specified at a time.
XACB output is suppressed.
Enter only one of the three keywords.
The XACB command produces either a VERBOSE or TERSE display. The presence of both keywords creates a conflict.
XACB output is suppressed.
Select either VERBOSE or TERSE.
The XACB command was used to select exception group cc for display. There are no exceptions currently assigned to group cc.
The command is ignored.
Select another exception group for display.
The XACB command did not find any exceptions that met the selection criteria specified. This could have happened because the LIST= parameter was specified without any exception name.
The command is ignored.
Enter a valid group identifier or exception name.
The user added a new profile cc to the profile library.
The command executes.
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 user deleted profile cc from the profile library.
The command executes.
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 user replaced existing profile cc in the profile library.
The command executes.
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 user attempted to delete profile cc which does not exist in the library.
The command terminates.
Correct the profile ID and retry.
This message indicates which profile defaults will execute for this session.
The command completes processing.
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.
This message indicates which profile defaults will execute for this session.
The command executes.
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 user issued a profile command with an invalid profile identifier (suffix).
The command terminates.
Enter a valid 2-character profile identifier. Use the PPRF LIST command to list valid identifiers at your installation.
The user issued a profile command with an invalid profile keyword.
The command terminates.
Enter the profile keyword SAVE or DELETE.
The installer deleted the installation profile from the library.
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.
The installer added a new installation profile to the profile library.
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.
The installer deleted the existing installation profile from the profile library.
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.
The installer replaced the existing installation profile in the profile library.
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.
The user entered a profile identifier for the installation profile command. It does not accept an identifier.
The command terminates.
Either use the PPRF command for a user profile, or delete the identifier on the IPRF command for the installation profile.
The installer attempted to delete or replace a non-existent installation profile from the profile library.
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.
A comment was added with the PPRF command that is longer than the maximum allowed.
The command terminates.
Add a comment that is a maximum of 18 characters and retry the command.
A user profile request failed for the specified reason.
The request is terminated.
The reasons that appear follow. Take the appropriate action for the reason displayed with this message.
An X'13' abend occurred when the specified routine (cccc) tried to open the profile data set.
The request is terminated.
Check the SYSLOG for the X'13' abend and correct the problem.
An X'14' abend occurred attempting to close the profile data set from routine cccc.
The request is terminated.
Check the SYSLOG for the X'14' abend and correct the problem.
An X'37' abend occurred while processing the profile data set from routine cccc.
The request is terminated.
Compress and/or re-allocate the data set as required.
An abend 913 occurred attempting to access a profile data set.
The request is terminated.
Contact the person in charge of system security at your installation.
A prior error occurred during user profile facility processing and the file was flagged as unavailable to this OMEGAMON session.
The request is terminated.
There should be a prior error message. Follow the instructions to correct the first error.
An attempt to GETMAIN storage failed with a non-zero return code.
The request is terminated.
Increase the region parameter on the EXEC statement or job card of the OMEGAMON session.
An attempt to open the input profile data set was not successful.
The request is terminated.
Make sure that the input profile data set is properly defined. Contact IBM Software Support.
A prior error occurred during user profile facility processing and the input file was flagged as unavailable to this OMEGAMON session.
The request is terminated.
Another OB0590 message with a different reason was issued prior to this one. Follow the procedure to correct the first error.
Routine cccccc has detected an OMEGAMON internal error.
The request is terminated.
Contact IBM Software Support.
The user profile header record about to be written to the output data set has an error.
The request is terminated.
Contact IBM Software Support.
An internal OMEGAMON error has occurred.
The request is terminated.
Contact IBM Software Support.
An invalid parameter type was presented to the user profile facility I/O driver.
The request is terminated.
Contact IBM Software Support.
The user profile I/O work area is not available.
The request is terminated.
Contact IBM Software Support.
The requested profile member contains no records.
The request is terminated.
Delete or replace the empty profile.
Member nnnnnnnn was not found in the profile data set.
The request is terminated.
Insure that the proper member name was requested. Use the PPRF LIST command to see what profiles are available and what profile data sets are allocated.
An attempt to open a profile data set in routine cccc was not successful.
The request is terminated.
Insure that the profile data sets are properly defined. If you still cannot open the data set, contact IBM Software Support.
An attempt to open the output profile data set was not successful.
The request is terminated.
Make sure that the output profile data set is properly defined. Contact IBM Software Support.
A prior error occurred during user profile facility processing and the output file was flagged as unavailable to this OMEGAMON session.
The request is terminated.
Another OB0590 message with a different reason was issued prior to this one. Follow the procedure to correct the first error.
The output profile data set is being used by another OMEGAMON session.
The request is terminated.
Once the output profile data set is free, you can enter the command again. If the condition persists, contact IBM Software Support.
The KOBCICSPROF and KOBCICSPROFSV data sets are not allocated.
The request is terminated. Profile services are not available.
Allocate the KOBCICSPROF and KOBCICSPROFSV data sets by DD statements or CLIST as appropriate for the session mode. If the problem persists, contact IBM Software Support.
An internal error occurred during user profile facility processing in routine cccc.
The request is terminated.
Another OB0590 message with a different reason was issued prior to this one. Follow the procedure to correct the first error.
An invalid parameter was presented to the user profile facility I/O driver.
The request is terminated.
Contact IBM Software Support.
A profile being read for input was found to have an invalid value in the spanned record field.
The request is terminated.
Attempt to recreate the profile and if the problem still exists, contact IBM Software Support.
In response to the .VTM command, OMEGAMON determined that the current environment does not support multi-user sessions. There is no meaningful information for the .VTM command to display. Valid multi-user environments are VTM, VTS, and VTT.
The command terminates.
Use this command only in a valid multi-user environment controlled by OBVTAM.