|
|
|
|
|
This group includes messages for the IOA (infrastructure) product.
Explanation: The options line commands S, I, J, B, F/O, and D cannot be requested simultaneously. Only one option type can be selected at a time.
None of the options selected is performed.
Corrective Action: Select options one at a time.
Explanation: The options line commands S, I, J, B, and G cannot be selected simultaneously on multiple lines. Only one of the options can be selected at a time.
None of the options selected is performed.
Corrective Action: Select the options one at a time.
Explanation: There was an attempt to select a table that is in use by another user. As a result, access is automatically given to the table in Browse mode only. No jobs may be added or deleted, and no changes may be made to existing jobs, when a table is accessed in Browse mode.
The Job List screen is displayed in Browse mode.
Corrective Action: If the required action cannot be performed when the table is in Browse mode, exit, and try again later. If required, contact your INCONTROL administrator to modify your User Profile definition to specify that the Table List screen remains displayed when an attempt is made to select a table that is in use.
Explanation: An invalid request was specified while accessing a table in Browse mode. The D (Delete) and I (Insert) options are not valid when a table is accessed in Browse mode. A list of options valid in Browse mode is at the bottom of the screen.
The requested option is not performed.
Corrective Action: In order to delete or insert entries, exit the Job List screen and re-enter by specifying the S (Select) option.
Explanation: An invalid value was specified for the field. This field must be blank (in some cases) or must contain a numeric value that includes leading zeroes.
No action is taken until a valid value is specified in the field, or until the screen is reset.
Corrective Action: Enter a valid value in the field, or reset the screen (if possible).
Explanation: A value other than Y, N or blank was specified in a Yes/No field.
No action is taken until a valid value is specified in the field, or until the screen is reset or cancelled.
Corrective Action: Specify Y, N or blank in the field, or reset or cancel the screen, if possible.
Explanation: Syntax errors were detected in the Display Type definition member. The Display Type definition member was loaded and analyzed and syntax errors were detected. Specific errors were previously displayed with the erroneous source lines.
The panel is not displayed.
Corrective Action: Correct the Display Type definition errors in the $$XXX member in the IOA MSG library and try to re-enter.
Explanation: An internal error occurred while attempting to display the error messages that resulted from the syntax check of the Display Type definitions.
The error messages are not displayed.
Corrective Action: Have your INCONTROL administrator notify BMC Customer Support.
Explanation: An attempt was made to specify an option, for example, Insert, Update, and the like. However, the OPTION field is not present in the current Display Type. The OPTION field must be defined in a Display Type in order to specify a required operation option.
No operations are performed.
Corrective Action: Add the OPTION field to the Display Type.
Explanation: Invalid option specified in the field.
Corrective Action: Correct the option, and try again.
Explanation: The function requested is not authorized for the user. The message is issued by the IOA security mechanism.
Corrective Action: Check with your system security administrator.
Explanation: An internal error occurred while attempting to place the Display Type header in the screen.
The screen is not displayed.
Corrective Action: Have your INCONTROL administrator notify BMC Customer Support.
Explanation: No valid Display Type code was specified when entering the DISPLAY command. The DISPLAY command requires a one letter Display Type parameter. This parameter must indicate an existing Display Type.
The current Display Type is not changed.
Corrective Action: Specify a valid Display Type with the DISPLAY command.
Explanation: More than one letter was specified for the Display Type code when entering the DISPLAY command. The DISPLAY command requires a one letter Display Type parameter. This parameter must indicate an existing Display Type.
The current Display Type is not changed.
Corrective Action: Specify a valid, one letter Display Type with the DISPLAY command.
Explanation: Display of an invalid Display Type was requested. Only Display Types that are defined in appropriate $$ xxx files in IOA MSG libraries are valid, for example, Default Display Type D.
The requested Display Type is not displayed.
Corrective Action: Specify a valid Display Type.
Explanation: Record length of the requested data set is not 80.
Corrective Action: Make sure you chose the correct library.
Explanation: Both calendar types, Regular/Periodic and Rule-Based (RBC) (in screen 8), have been selected. Only one is allowed.
Corrective Action: Select one of the calendar types.
Explanation: Neither the Regular/Periodic nor the Rule-Based (RBC) calendar type (in screen 8) has been selected.
Corrective Action: Select either the Regular/Periodic or the Rule-Based (RBC) calendar type (in screen 8).
Explanation: Invalid value specified in the field. The cursor points to the field that contains the invalid value.
Corrective Action: Select Y for yes, or N for no.
Explanation: The field contains a leading blank, or two strings separated by blanks. Leading blanks and embedded blanks are not allowed in this field.
The cursor points to the first blank.
Corrective Action: Correct the field contents.
Explanation: The entry contains invalid data. Possible causes are:
Corrective Action: If the contents of the entry were modified, try to restore the entry to its original state. If you cannot or if this is not the problem, have your system programmer call BMC Customer Support.
Explanation: Each IOA screen is controlled by an external command member that contains a list of all commands and synonyms supported under the screen. Command members reside in IOA Parameter Libraries. They should be named TscrCMD1, where scr is the screen name. The Parameters library should be allocated to the DACMDxx DD statement, where xx is the application ID. Possible causes are:
For more information about Command Members, see the section on defining new application types in the IOA Installation Considerations section of the INCONTROL for z/OS Installation Guide.
The screen is locked.
Corrective Action: To exit, press PA1 a few times. Ask your INCONTROL administrator for assistance.
Explanation: Invalid scroll amount specified. Valid scroll amounts are: PAGE, HALF, CRSR, and MAX.
Corrective Action: Correct the scroll amount field.
Explanation: Insufficient memory to perform the task.
Corrective Action: For jobs, increase the REGION size. For TSO, log on again using a larger SIZE parameter, or exit one of the screens using an END command.
Explanation: Loading of IOA or Control- x Installation Parameters failed.
The function requested is terminated.
Corrective Action: Look on the system log for additional messages.
Explanation: The subsys subsystem is already active for another IOA environment. The same subsystem name cannot be used for two IOA environments in parallel.
IOA subsystem initialization fails for the subsys subsystem.
Corrective Action: Either choose another subsystem name for the current environment of the IOA products, or deactivate the IOA online monitor and all the subsystem components of the old IOA environment and restart the subsystem.
Explanation: If OPTION was set to D for IOASINIT, the subsystem name does not exist. If OPTION was set to M for IOASINIT, or Control-O is started, the subsystem name does not exist and dynamic allocation of the MVS subsystem tables is not allowed.
If OPTION was set to D for IOASINIT, possible causes are:
If OPTION was set to M for IOASINIT, or Control-O is started, possible causes are:
Initialization of the subsystem fails.
Corrective Action: Define the subsystem name in the MVS table.
If OPTION was set to D for IOASINIT, see the section on Control-D Operational Parameters for details about the AMNAME parameter. See the section on installing the Compressed Dataset Access Method (CDAM) in the Control-D chapter of the INCONTROL for z/OS Installation Guide for details about defining the subsystem name in MVS tables.
If OPTION was set to M for IOASINIT, or Control-O is started, see the following:
Explanation: Options D (Delete) and C (Change) were specified together. Options D and C cannot be mixed. Only one of these option types can be specified at a time.
Corrective Action: Remove conflicting options, and request one option type at a time. After one option type has been performed, request the other option type.
Explanation: Options A (Add) and E (Erase) were specified together. Options A and E cannot be mixed. Only one of these option types can be specified at a time.
Corrective Action: Remove conflicting options and request one option type at a time. After one option type has been performed, request the other option type.
Explanation: Open of IOA Log file failed (the DALOG DD statement). Possible causes are:
The requested function ends.
Corrective Action: Look on the computer log for additional messages that clarify the reason for the failure. Then, correct the JCL for the job, or the allocations of the CLIST.
Explanation: There is insufficient storage available to insert a new entry in the list.
A new entry is not added.
Corrective Action: Increase the REGION size, exit any open screens, and retry the operation. An alternative is to reduce the number of generations.
Explanation: No data entered in an obligatory field.
Corrective Action: Fill in all obligatory fields.
Explanation: Normal message of the I (Insert) option when a new entry is added successfully.
Corrective Action: No action is required.
Explanation: This information message indicates that for security reasons, one or more entries was not displayed. Control-M/Analyzer security exit CTBX003 determined that the user is not authorized to look at some entries.
One or more entries will be hidden from the user.
Corrective Action: No action is necessary. All entries for which there is authorization will be displayed. To change authorization settings, call your INCONTROL administrator.
Explanation: An invalid value was entered in the SEND WITH CC field.
Valid values for the SEND WITH CC field are:
The cursor points to the field that contains the invalid value.
Corrective Action: Correct the value in the field.
Explanation: An invalid value was entered in the CONVERT TO ASCII field.
Valid values for the CONVERT TO ASCII field are:
The cursor points to the field that contains the invalid value.
Corrective Action: Correct the value in the field.
Explanation: A HOLD request was specified for an entry that was deleted. Once an entry is deleted it cannot be held.
Corrective Action: No action is required.
Explanation: A HOLD request was specified for an entry that is already being held. If an entry is already held, a new HOLD request in invalid.
The option is not performed.
Corrective Action: No action is required.
Explanation: A FREE request was specified for an entry that is not being held. Only an entry that is held can be freed.
The option is not performed.
Corrective Action: No action is required.
Explanation: A DELETE request was entered for an entry that is not being held. Only an entry that is held can be deleted.
The option is not performed.
Corrective Action: No action is required.
Explanation: A DELETE request was specified for an entry that was already deleted. Once an entry is deleted, it cannot be deleted again.
Corrective Action: No action is required.
Explanation: A FREE request was specified for an entry that was already deleted. Once an entry is deleted it cannot be freed.
Corrective Action: No action is required.
Explanation: An option was rejected by a security or user exit. Each option request by a user is sent to both the security exit and the user exit, if any. Either can reject the option.
The option is not performed.
Corrective Action: To get authorization to perform this function, contact your INCONTROL administrator.
Explanation: The Why option ? was specified for an entry that does not have a WAIT ACTIVATION status. The Why option shows why an entry has a WAIT ACTIVATION status. The option is invalid if the entry has a different status.
Corrective Action: No action is required.
Explanation: An invalid TIME FROM and/or TO value was specified. Specified TIME values must be valid times based on a 24 hour clock, in format hhmm, where hh is hours and mm is minutes.
Corrective Action: Correct the specified TIME values.
Explanation: Loading of the modName module failed. Possible causes are:
The function requested is terminated.
Corrective Action: Look on the system log for additional messages that clarify the problem. Suggested actions:
Explanation: Insufficient storage available to insert a new entry.
Corrective Action: Suggested actions:
Explanation: Definition member is too large to be handled by IOA. Possible causes are:
Corrective Action: Suggested actions:
Explanation: Insufficient storage available to enter the definition screen.
Corrective Action: Suggested actions:
Explanation: Insufficient storage available to process the changes in the definition screen. All changes are ignored, and the user returns to the list screen. You can still try to save the entry.
Corrective Action: Do one of the following:
Explanation: IOA did not build the entry list as no entries were found in the library.
Corrective Action: Enter new entry name.
Explanation: Internal IOA error while processing an entry. Possible causes are:
Corrective Action: If the contents of the entry were modified, try to restore the entry to its original state. If you cannot, or if this is not the problem, have your system programmer call BMC Customer Support.
Explanation: Code line_code could not be found in the help member. A HELP request was entered, but the line-sensitive help data could not be retrieved.
The Help screen displayed is the beginning of the help member of the screen, instead of the information relevant specifically to the line at which the cursor is located.
Corrective Action: Have your INCONTROL administrator inform BMC Customer Support of this message and the code displayed.
Explanation: The requested entry is not a valid IOA definition member.
Possible causes are:
Corrective Action: Enter a valid IOA definition. If the specified entry was incorrectly modified, try to restore it to its original state.
Explanation: Another IOA user is currently working on the entry. Two users cannot work on the same entry simultaneously. The other user may be using the entry through either the IOA Online Facility or the ISPF editor.
Corrective Action: Try again later.
Explanation: Insufficient storage available to load the definition member.
Corrective Action: Do one of the following:
Explanation: Too many entries in the definition member. The maximum number of entries permitted is number. This variable is site modifiable, and has a default of 500.
Corrective Action: Split the IOA definition member into two. If necessary, contact your INCONTROL administrator to increase the maximum number of entries permitted.
Explanation: This message is displayed from user exit IOAX028. The code displayed is an internal user code. Exit IOAX028 is invoked from certain IOA definition screens. For more information, refer to IOAX028 in the SAMPEXIT library.
Corrective Action: If necessary, contact your INCONTROL administrator for further information.
Explanation: This message indicates that user exit IOAX028 was called more than ten times consecutively between ENTER commands. This exit was modified and activated so that for each invocation it enforces a new check of the screen, and after each check of the screen the exit is invoked again before the user regains control of the screen. This probably indicates an inner loop.
After the tenth time exit IOAX028 is called in a row, it is not called again, and the user regains control of the screen.
Corrective Action: Notify your INCONTROL administrator of the occurrence of this message.
Explanation: An attempt was made to delete the $$SPACE member in one of the directory lists. The $$SPACE member is a not an IOA member. It is a member of PDSMAN, and therefore, user access to it is restricted. The IOA delete option is invalid for deleting non IOA members like $$SPACE.
The $$SPACE member is not deleted.
Corrective Action: No action is required.
Explanation: This information message indicates that the memName member was:
In this message, cpuSmfId is the SMFID of the CPU on which the session is active.
Corrective Action: No action is required.
Explanation: The definition member is full. The maximum number of entries in an IOA definition member is number. This variable is site-modifiable, and has a default of 500.
Corrective Action: Split the IOA definition member into two. If necessary, ask your INCONTROL administrator to increase the maximum number of entries permitted.
Explanation: Missing library name. The LIBRARY field is required.
Corrective Action: Fill in the name of the IOA definition library.
Explanation: Two exit options are marked. Only one exit option may be marked with Y or N.
Corrective Action: Fill in Y or N in only one of the exit options.
Explanation: This information message indicates that an IOA definition entry was saved or created. In some of the IOA entry definition lists this message is displayed after a definition entry is saved or created.
Corrective Action: No action is required.
Explanation: The command member could not be accessed. Each IOA screen is controlled by an external command member. The Parameters library should be allocated to the DACMDxx DD statement, where xx is the application ID.
Possible causes are:
The screen is locked.
Corrective Action: To exit, press PA1 a few times. Call your system programmer for assistance.
Explanation: No value was specified for the NAME parameter. The NAME parameter is mandatory.
Corrective Action: Specify a valid name.
Explanation: An invalid value was specified in the MODE field. The MODE parameter enables the user to determine whether specific actions are really performed, or only recorded and not implemented. Valid modes are P (Prod) and T (Test). In mode P, actions are implemented normally. In mode T, actions that would have been performed in mode P are merely recorded and not implemented.
Corrective Action: Specify a valid mode.
Explanation: An OWNER value was not specified. The OWNER parameter is mandatory. It identifies the ID of the user who requests IOA services.
Corrective Action: Specify a valid OWNER (user ID).
Explanation: A non-numeric value was specified in a numeric field.
Corrective Action: Specify a numeric value.
Explanation: An internal error occurred during preparation or transmission of a panel for display on the screen. The name of the module in which the error occurred, and the return code, appear in the message.
The panel is not displayed.
Corrective Action: If modName is IOADAS and RC=000016, check the IOA LOG for message CTDE12E. If CTDE12E was issued, see “CTDE12E RESOURCE LIBRARY HAS AN INCORRECT FORMAT”.
Try to reenter the online environment after logging out and reconnecting. If this is unsuccessful, call BMC Customer Support with the information in the message.
Explanation: An invalid name was specified in the NAME field. A valid name must begin with an alphabetic character or with one of the following characters: $, # or @. All other characters must be alphabetic, numeric or one of the following: $, #, @, ., _ or %. Characters * and ? are valid only for mask representations.
Corrective Action: Correct the name specification.
Explanation: An invalid date was specified. The date should be a valid date in the format determined by Installation Parameters. Valid formats are ddmmyy, mmddyy, or yymmdd. In some date fields, four digits (no yy year) or eight digits with a 4-digit year (ddmmyyyy, mmddyyyy or yyyymmdd) are valid.
Corrective Action: Specify a valid date.
Explanation: User specified an invalid range in FROM and TO fields. The FROM value cannot exceed the TO value.
Corrective Action: Specify a valid range or a mask, if a mask is valid in the FROM field.
Explanation: The cursor is positioned in a required field but the field was not filled in.
Corrective Action: Fill in the field.
Explanation: The IOA Online Facility sent a message to the screen but the message cannot be displayed due to an internal program error.
Corrective Action: Call BMC Customer Support for assistance.
Explanation: An ON statement is not linked to the preceding ON statement by the AND/OR/NOT parameter. When more than one ON statement is specified, the relationship between them must be defined. The AND/OR/NOT field for an ON statement cannot be blank if another ON statement follows.
Valid AND/OR/NOT field values are:
Corrective Action: Fill in a valid AND/OR/NOT parameter, or delete the unlinked ON statement.
Explanation: The field is not entirely filled in. The field specifies data that is valid only if all character positions are used. In some cases these fields may receive masked values.
Corrective Action: Fill in the field entirely.
Explanation: An invalid value was specified in the AND/OR/NOT field. AND/OR/NOT parameter links ON statements. The AND/OR/NOT field for an ON statement cannot be blank if another ON statement follows.
Valid values: A (AND), O (OR), N (NOT) and blank (no more ON statements).
Corrective Action: Specify a valid AND/OR/NOT field value.
Explanation: No ON statement was specified. At least one ON statement must be defined in the Rule Definition.
Corrective Action: Specify at least one ON statement.
Explanation: An invalid value was specified in the AND/OR field.
Valid values for the AND/OR field are:
Corrective Action: Specify a valid value in the AND/OR field.
Explanation: A prerequisite condition name is missing in a DO COND statement.
At least one condition must be specified in a DO COND statement.
Corrective Action: Specify a prerequisite condition name.
Explanation: An invalid date or date reference was specified in the date field. The date reference should be a valid date in the format determined by Installation Parameters: mmdd or ddmm. In some date reference fields, the following values are also valid: PREV, DATE, NEXT, ODAT, *** * or $$$$. For details, refer to the appropriate user guide.
Corrective Action: Specify a valid date reference.
Explanation: The common API for the condition file failed.
Execution stops.
Corrective Action: Contact your IOA administrator for assistance.
Explanation: Control-M is not installed and the CONDITION option has not been marked as Y.
Mark at the CONDITION option as Y.
Corrective Action: No action is required.
Explanation: The condition option is invalid or missing. Use condition option + (plus) to add a condition to the IOA Conditions file, or - (minus) to delete a condition from the IOA Conditions file.
Corrective Action: Specify + (plus) or - (minus) in the condition option field.
Explanation: The screen window requested by the IOA Online Facility cannot be displayed because of an internal program error.
Corrective Action: Re-enter the information. Notify BMC Customer Support if the error occurs again.
Explanation: The screen window requested by the IOA Online Facility cannot be displayed because of an internal program error.
Corrective Action: Contact BMC Customer Support.
Explanation: The screen that is being prepared for display does not contain any data.
The screen which is being prepared is not displayed. The previous screen is displayed with the error message.
Corrective Action: Consider one or more of the following:
Explanation: An invalid SHOUT destination code was specified.
Corrective Action: Correct the SHOUT destination field. For valid destinations, refer to the appropriate user guide.
Explanation: An invalid SHOUT urgency was specified. Valid SHOUT urgency values are R (Regular), U (Urgent), or V (Very urgent). For details, refer to the appropriate user guide.
Corrective Action: Specify R, U, or V in the SHOUT urgency field.
Explanation: The mandatory field in which the cursor is positioned was not filled in.
Corrective Action: Fill in the field.
Explanation: Code option + (plus) was specified for a generic date reference. The Add condition option + cannot be specified with generic date references ($$$$/****).
Corrective Action: Specify - (minus) as the code option, or use a different date reference.
Explanation: A quantitative resource quantity was specified without a corresponding quantitative resource name.
Corrective Action: Fill in the quantitative resource name.
Explanation: The specified style ID on a @STYLE line in the Display Type definition member is reserved by the IOA Online Facility for system purposes. See the INCONTROL for z/OS Installation Guide for more information.
Corrective Action: Specify another style ID.
Explanation: A date that passed was specified in a DATE field. Only the current date or a future date can be specified in the DATE field.
Corrective Action: Specify the current date or a future date.
Explanation: An invalid AutoEdit statement or expression was specified in the DO SET statement.
Corrective Action: Specify a valid AutoEdit statement. For an explanation of the AutoEdit Facility, see the appropriate user guide.
Explanation: An invalid action was specified in a DO statement.
Corrective Action: Correct the DO action field. For valid actions, refer to the appropriate user guide.
Explanation: An invalid character has been specified in the SHIFT field. Valid values are < (Shift back), > (Shift forward) or blank (do not shift).
Corrective Action: Specify a valid value.
Explanation: This information message indicates that the current entry is the first entry in the entry list. This message can be displayed if a PREV command (PF10) is specified in a list screen when the first entry of the list is already displayed.
Corrective Action: No action is required.
Explanation: This information message indicates that the current entry is the last entry in the entry list. This message can be displayed if a NEXT command (PF11) is specified in a list screen when the last entry of the list is already displayed.
Corrective Action: No action is required.
Explanation: A logical error was detected in the Control-M/Tape Media Database (MDB) when reading a record. Probable causes:
Corrective Action: Notify your system administrator.
Explanation: The user has specified an invalid sign preceding a numeric value.
Corrective Action: Specify the correct sign: < or >.
Explanation: An AND/OR/NOT parameter was used without a subsequent ON statement. The AND/OR/NOT parameter links a subsequent ON statement with the preceding ON statement. Every AND/OR/NOT value must be followed by an ON statement.
Corrective Action: Either delete the value in the AND/OR/NOT field, or enter the missing ON statement.
Explanation: A TO value cannot be specified if the FROM field contains a mask. A group is specified by a mask in the FROM field, or by filling in the TO field to specify a range. However, these methods cannot be combined.
Corrective Action: Clear the TO field, or do not specify a mask in the FROM field.
Explanation: Too many digits were specified in a field. When a numeric value is specified in this field, a limited number of digits or columns can be filled in. This may occur when the field receives different types of data, for example a date or a four digit number.
Corrective Action: Decrease the number of digits specified in the field.
Explanation: This information message indicates that changes in the definition screen or Entry List caused the entry to change location in the table after exit from the definition screen and return to the Entry List Panel. Automatic sort of the table is active. The sort criteria of an entry changed in the particular definition screen or in the Entry List.
The order of entries in the table is changed.
Corrective Action: No action is required.
Explanation: This information message indicates that an unsorted table member was sorted on entry to list of entries in a table.
Automatic sort of the table is active. If the sort changed the order of entries in the table, this message is issued. This situation may occur when selecting tables that were created by conversion utilities, or if sort was previously inactive when modifying the table.
The order of entries in the table is changed.
Corrective Action: No action is required.
Explanation: The CHANGE command was issued using an invalid format. Valid format of the CHANGE command is:
CHANGE string_in_definition replacement_string
Corrective Action: Reissue the command using the valid format.
Explanation: The RCHANGE could not be performed because the original CHANGE command was not successfully completed.
Corrective Action: Use the CHANGE command to substitute a string in an IOA definition with another string.
Explanation: This information message indicates that the CHANGE command was used to change the value of a certain string in an IOA definition to the value of another string.
Corrective Action: No action is required.
Explanation: This information message indicates that the user issued a CHANGE command to change the value of a string in an IOA definition to another string’s value. However, no matching string was found in any of the fields of the definition.
The requested string substitution does not take place.
Corrective Action: No action is required.
Explanation: The change requested by means of the CHANGE command is not performed because it would cause an error in the IOA definition. Before performing the requested change, a validity check is performed to ensure that the field will not grow beyond its boundaries, and that its contents remain valid for the IOA definition.
The requested change is not performed.
Corrective Action: No action is required.
Explanation: The user requested the Online Scheduling Plan for a specific range of dates and then attempted to view the job scheduling dates for a month that is outside the defined date range.
Corrective Action: To view the scheduling plan for the requested month, exit the current display of the plan, define a new range, and reenter.
Explanation: An invalid sort option or no sort option was requested when activating the SORT command from the scheduling job list.
Corrective Action: Specify one of the valid sort options shown in the message when activating the SORT command.
Explanation: An invalid return code, abend code or reference was entered in one of the IOA definition panels.
Corrective Action: Enter a valid code. For information on valid codes, see the appropriate product guide.
Explanation: A command was activated that was incorrectly defined in the Command member of the current screen. The number of a command defined in the Command member of the current screen must be positive, but less than 45.
The command is not executed.
Corrective Action: Correct the corresponding Command member in the IOA Parameter Library. See the section on defining new application types in the section on IOA installation considerations of the INCONTROL for z/OS Installation Guide.
Explanation: One of these operands, which are invalid for this type of code, was specified.
Corrective Action: Use only valid operands for this type of code.
Explanation: An invalid sign was specified for quantity change in the CHANGE window.
Valid quantity signs are:
Corrective Action: Specify one of the above quantity signs.
Explanation: An attempt was made to open a comment line in an IOA definition. However a comment line cannot be inserted before the line on which the cursor is positioned.
Corrective Action: Try to open the comment on a different line.
Explanation: An invalid option or command was entered in an IOA list. The current list of valid options or commands appears at bottom of the screen.
Corrective Action: Enter a valid option.
Explanation: The specified command contained too many parameters.
The command is not issued.
Corrective Action: Delete parameters until the remaining ones are accepted.
Explanation: The parameter specified is not a valid parameter of the command.
The command is not issued.
Corrective Action: Either delete the parameter or replace it with a valid one.
Explanation: Command SHOW filterName was entered to activate predefined selection criteria, but the filter specified was not in the user profile member or in the global profile member ($PROFILE).
The command is not issued.
Corrective Action: Edit and save this filter as a new filter using the EDIT keyword, or specify an existing filter with the command. If the fields of the specified filter match those of the DEFAULT filter, the filter is not saved in the user profile member.
Explanation: All Y/N fields in a logical group of fields in the SHOW window are set to N. At least one must be set to Y; otherwise no lines will be displayed.
The selection criteria of the SHOW window are not activated.
Corrective Action: Set at least one field to Y.
Explanation: A request to save a GLOBAL filter defined in the $PROFILE member failed because a GLOBAL filter cannot be saved by a user.
The filter is not saved.
Corrective Action: Specify a filter name that is not defined in the $PROFILE member.
Explanation: The SAVE field on the SHOW WINDOW was set to Y, but no filter name was specified. SAVE can be performed only on a specific filter.
SAVE is not performed.
Corrective Action: Specify a filter name.
Explanation: The currently edited filter in the SHOW window was changed, but the SAVE field was left empty.
Corrective Action: Suggested actions:
Explanation: A request to save changes made to a filter failed because there is not enough memory available. When filter fields are changed, the changed values are first saved in memory. Because the current region is used up, changes cannot be saved.
The changes are not saved.
Corrective Action: Exit the SHOW window without saving the changes by specifying N in the save field, or by pressing the RESET key (PF4 is the installation default). To enable saving a new filter, or changes to an existing filter, either exit some open online applications, or increase the value of the REGION parameter.
Explanation: The x line command is supported for job entries, but not SMART tables.
The command is not executed.
Corrective Action: No action is required.
Explanation: An invalid sort option or no sort option was requested when activating the SORT command from the rule definition list
Corrective Action: Specify either R or T when activating the SORT command.
Explanation: This information message indicates that the defn definition was:
In this message, cpuSmfId is the SMFID of the CPU on which the session is active.
Corrective Action: No action is required.
Explanation: This message is issued when the error occurred during parsing the IOADEST member of the IOA PARM library. The ROUTCODE of parameter parameter is invalid. A valid value of ROUTCODE is a number between 1 and 15.
Corrective Action: Update the route_code with the correct value.
Explanation: Highlighted, unrollable message.
An internal error occurred while building the online environment.
The online environment is not started.
Corrective Action: Try to reenter the online environment after logging out and reconnecting. If this is unsuccessful, contact BMC Customer Support with the information in the message.
Explanation: A user exit or security exit did not allow performance of the specified operation in the online environment.
The operation is not performed.
Corrective Action: Contact your IOA security administrator to get authorization to perform this operation.
Explanation: The selected job or SMART table is not scheduled to run within the specified time period. Option P on the Job List screen of the Job Schedule Definition facility (2.P) shows when the selected job or SMART table will run in the specified time period.
The system waits for a response from the operator.
Corrective Action: Press the PF3 key to continue.
Explanation: This information messages indicates that an entry in an IOA list has been modified.
Corrective Action: No action is required.
Explanation: Two rule-based calendar entries with the same name were defined in the SMART Table Entity. Rule-based calendar names must be unique within a SMART Table Entity.
Corrective Action: Change one of the rule-based calendar names so that all the rule-based calendar names in the SMART Table Entity are unique.
Explanation: An attempt to exit a SMART Table Entity definition for which no rule-based calendar name was defined failed. At least one rule-based calendar entry must be defined in a SMART Table Entity.
Corrective Action: Specify at least one rule-based calendar name in the SMART Table Entity.
Explanation: When specifying the WHEN string (x‘######’) in hexadecimal format the user used an invalid digit. Valid hexadecimal digits are: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, F.
Corrective Action: Correct the WHEN string to contain valid digits only.
Explanation: An odd number of hexadecimal digits was specified in the WHEN string, for example, x‘40A12’. The WHEN string must contain an even number of digits since each pair of digits represents one byte.
Corrective Action: Correct the WHEN string to contain an even number of valid digits.
Explanation: An attempt was made to save a filter that is identical to the default filter. A user filter can be saved only if its filtering criteria are different from the default filter criteria (filter DEFAULT).
Corrective Action: Change some of the criteria in the current filter, or use filter DEFAULT whenever these criteria are desired.
Explanation: The main screen formatting routine encountered an internal error. The ID, type, and class are specified as three characters in the message. The first character represents the ID, the second character represents the type, and the third character represents the class.
The screen is not displayed, or displayed incorrectly.
Corrective Action: Save the contents of the message and try to reenter the environment. If the problem persists, report the information from the message to your INCONTROL administrator.
Explanation: In a SMART Table Entity scheduling definition, an invalid character has been typed in the RBC field. The RBC field may contain any displayable characters except for '*' and '?'.
The SMART Table Entity scheduling definition cannot be saved.
Corrective Action: Remove invalid characters from the RBC field.
Explanation: An option that must be the last option entered in the screen was requested. No other option can be entered on any line after this line.
The request is ignored.
Corrective Action: Either delete the option that must be the last in the screen, or delete all options that follow it.
Explanation: An option that cannot be combined with any other option was requested. No other option can be entered on any other line.
The request is ignored.
Corrective Action: Either delete the option that must be specified alone, or delete all other options.
Explanation: An UP, DOWN, FIND, or LOCATE command was entered in a nonscrollable screen.
The requested command is not performed.
Corrective Action: No action is required.
Explanation: The first character is used for the exclude sign, therefore the RBC name cannot start with that character.
Corrective Action: Change the first character in the RBC name to a different character.
Explanation: The first character is used for the exclude sign, therefore the RBC name cannot start with that character.
Corrective Action: Change the first character in the RBC name to a different character.
Explanation: An invalid comparison operator was specified in the WHEN string.
Corrective Action: Correct the WHEN string to contain one of the following comparison operators: GT, LT, GE, LE, EQ, GL, or NE
Explanation: Even when the Exclude RBC feature is turned off (EXCLURBC=N in CTMPARM), new RBCs cannot have a name starting with "!".
However, existing CTM-level RBCs with such names can be used, but will be processed according to the setting of EXCLURBC. If EXCLURBC=N, the CTM-level RBCs will be processed as regular (Include) RBCs. If EXCLURBC=Y, the CTM-level RBCs will be processed as reference to Exclude RBCs (without the “!” and will result with a message of missing RBC).
When editing a SMART table RBC section, an existing Table level RBC with a name starts with “!”, will be treated according to the value of EXCLURBC. With EXCLURBC=N, it will be treated as an include RBC, while with EXCLURBC=Y, it will be treated as an Exclude RBC.
Corrective Action:Change the name of the RBC so it starts with a character other than "!", and make sure that all jobs referring to this RBC are updated with the new name (and do not use “!” as the first character of the name).
Explanation: The date range in the scheduling plan of a job or group entity in calendar format exceeds 3 years.
The requested command or option is not performed.
Corrective Action: Correct the date range and press Enter.
Explanation: An attempt was made to define a calendar that duplicated an existing calendar.
The duplicate calendar is not saved.
Corrective Action: Enter N (No) in the Save window.
Explanation: The current attempt to run a job or enter a command is not authorized. This error message is issued when there is an attempt to perform an operation that is not allowed. For example, someone tried to use an IOA Online option without the necessary authority.
The operation terminates.
Corrective Action: Notify your INCONTROL administrator.
Explanation: A command that requires an operand was entered without an operand.
The command is not performed.
Corrective Action: Reenter the command with the operand.
Explanation: A new line or record was inserted, but no other step was taken before another command was entered.
When a new line or record is inserted, no other command can be performed until either the new line or record is deleted, or data is entered in the new line or record.
Corrective Action: Either delete the newly inserted line or record, or type some data into the newly inserted line or record and press Enter.
Explanation: There was insufficient memory to perform a task.
The action that could not be performed accompanies this message. It may vary depending on the environment in which the message was issued.
Corrective Action: For jobs, increase the REGION size. For TSO, log on again using a larger SIZE parameter, or exit one of the screens.
Explanation: An error occurred during the initialization of an INCONTROL product. The CREATE or RETRIEVE service failed, and the related IBM Module (IEANTCR or IEANTRT) ended with a nonzero return code.
Corrective Action: Refer to the relevant IBM publication.
Explanation: An internal error occurred during the initialization of an INCONTROL product.
Corrective Action: Contact BMC Customer Support.
Explanation: During IOA environment initialization, processing of the parm source parameter failed. Sometimes the optional part of the message is displayed, indicating that the modName module was needed to process the parm parameter, but the module was not found in a load library.
This message is usually preceded by a message detailing either a READ error or a syntax error.
The program stops.
Corrective Action: Check and correct the parm member in the IOA PARM library. BMC recommends that you use the ICE Customization option to correct this member.
Explanation: During IOA environment initialization, the initialization of the module that provides the serv service failed.
Valid values for serv are:
This message is usually preceded by a message issued by the service module, which usually describes the problem.
The probable source of the problem is either the IOADSN or the allocation members in the libraries referenced by DD name DAPARM.
The program stops.
Corrective Action: Attempt to solve the problem described in the service module message.
Explanation: An internal error occurred during the initialization of an INCONTROL product.
Initialization stops.
Corrective Action: Contact BMC Customer Support.
Explanation: No value was set for the JESTYPE parameter, and the IOAENV module could not identify the type of JES in use.
The program stops.
Corrective Action: Check and correct the JESTYPE parameter in the IOAPARM member in the IOA PARM library.
Explanation: An internal error occurred during the initialization of an INCONTROL product.
Initialization stops.
Corrective Action: Contact BMC Customer Support.
Explanation: An internal error occurred during the initialization of an INCONTROL product.
Initialization stops.
Corrective Action: Contact BMC Customer Support.
Explanation: The initialization of the desired environment could not be completed because the DAPARM DD statement was not found.
The session ends.
Corrective Action: Add the DAPARM DD statement to the relevant JCL.
Explanation: An internal error occurred during the initialization of an INCONTROL product.
Initialization stops.
Corrective Action: Contact BMC Customer Support.
Explanation: The IOAENV module could not load the modName module.
Initialization stops.
Corrective Action: Contact BMC Customer Support.
Explanation: The IOA/Control-M routine, rtn-name, failed with a return code of rc and a reason code of rsn.
When the rtn-name is CTMBAPI and the rc=8, refer to the explanation in message IOA723I for a complete list of all the reason codes and their meaning.
When the rtn-name is CTMBAPI and rc=4, and rsn=0 the meaning is that an internal request to the Control-M application interface program (CTMAPI) to Search for a specific job in the AJF failed because the job was not present in the AJF.
Corrective Action: Take action based on the rc and rsn. Contact BMC Customer Support if you are unable to determine an appropriate course of action.
Parent Topic |