This group includes messages for the IOA (infrastructure) product.
Explanation: Only one subsystem parameter should be specified in the PARM field of the IOAINS program. The IOAINS installation program can install only one of the above products at a time. The product code should be specified in the PARM field of the IOAINS EXEC statement.
The IOAINS installation program terminates with a condition code of 08.
Corrective Action: Correct the PARM field and resubmit the job.
Explanation: This information message indicates that statements contained in the specified library or member will be (START) or were (END) modified depending on the operation. This message is issued at the start and after modification of each member by IOAINS.
Corrective Action: No action is required.
Explanation: This information message displays each statement before it is modified.
Corrective Action: No action is required.
Explanation: This information message displays each statement after it is modified.
Corrective Action: No action is required.
Explanation: The specified DD name could not be opened. This message is issued when errors occur during an attempt to open the mandatory DD names of the IOAINS and IOAIN1 installation programs.
The IOAINS or IOAIN1 installation program terminates with a condition code of 08.
Corrective Action: Correct the error and resubmit the job.
Explanation: In the IOAINS program, this message is issued as a result of an unrecognized parameter in the DEFPARMx member, where x represents the IOA product. In the IOAIN1 program, this message is issued as a result of an unrecognized parameter in the member pointed to by the DAINS DD statement. In both cases, the statement content follows.
The DEFPARMx member or the DAINS DD statement contains installation variables to replace constants throughout the product libraries. However one of the variables was not recognized by IOAINS or IOAIN1.
The IOAINS or IOAIN1 installation program terminates with a condition code of 08.
Corrective Action: Check the statement content. Do not modify the text between the percent signs. If needed, restore the relevant library from the original tape to determine the original variable value.
Explanation: The specified library or member could not be allocated. The DALIBS DD name contains a list of libraries and members in which modification of the product Installation Parameters takes place. If the member is blank, the entire library can not be allocated.
The IOAINS installation program continues with the next library and member as specified under the DD name DALIBS.
Corrective Action: Determine the reason the library or member could not be allocated. Then resubmit IOAINS while DALIBS contains only the problematic library and member specifications.
Explanation: Incorrect or missing PARM value in the IOAIN1 installation program. The PARM field of the IOAIN1 installation program should contain the type of run (1, 2, 3, 4, 5, or 6), followed by the product suffix, and a series of variables to be modified by the program. However, this PARM value was missing or incorrect.
The IOAIN1 installation program terminates with a condition code of 08.
Corrective Action: Check the PARM field in the IOAIN1 installation program, correct the error, and resubmit the job.
Explanation: Highlighted, unrollable message.
An invalid OS parameter was passed to the IOAIN1 installation program, with run type 4. When running the IOAIN1 installation program with run type 4, the OS parameter should be MVS or MSP.
The IOAIN1 installation program terminates with a condition code of 08.
Corrective Action: Check the PARM field in the IOAIN1 installation program, correct the error, and resubmit the job.
Explanation: This information message indicates that the IOAIN1 installation program successfully completed modification of the lines in the member pointed to by the ddName DD statement. This message is issued for each DD statement of the format DAINS xxx.
Corrective Action: No action is required.
Explanation: The value assigned to the parm parameter, which was coded in the DEFPARMx member and should be substituted by the IOAINS installation program, exceeded 44 characters. Since the maximum length for a parameter value is 44, the program cannot perform variable substitution.
The program stops executing with a return code of 08. No substitution is performed by this step of IOAINS.
Corrective Action: Correct the value of parm and rerun the job.
Explanation:The IOAFTR installation program is used for tailoring members during the copying process from one library to another.
This message is issued by IOAFTR if the SYSIN statement includes the same input and output libraries pointed to by the INDD and OUTDD statements and the same member name for input and output.
The IOAFTR installation program terminates with a reason code of 05.
Corrective Action: Check the settings or change the name of one of the members to: xxxxxxx1 and rerun the process.
Explanation: The IOACLB utility displays this message if a calendar contains invalid data. For example, a regular calendar can have a value of Y/N/+/-/blank in the months. If another value is present, this error message will be displayed. Note that the previous message identifies the calendar that contains the error. The XML output file will not contain this calendar.
Corrective Action: Check the calendar, correct the values that are invalid, and rerun the IOACLB utility.
Explanation: This message is produced for each calendar that is processed by the IOACLB utility.
Corrective Action: No action is required.
Explanation: This information message is issued by CTMAPI, and indicates that the utility identified in the message has started.
CTMAPI issues this message before calling the application that handles the appropriate action code.
Corrective Action: No action is required.
Explanation: This information message is issued by CTMAPI, and indicates that the utility identified in the message has ended with a return code of 0.
Corrective Action: No action is required.
Explanation: This information message indicates that the specified utility identified in the message has ended with a return code other than 0.
In this message, rc is the return code.
Corrective Action: Use the contents of any messages issued by the utility, together with the return code, to determine the cause of the problem and take appropriate corrective action.
Explanation: This message is issued whenever CTMAPI fails to perform an action, for example, failing to load an application.
In this message, rc is the reason code, the meaning of which is identical to the reason codes issued by the CTMBAPI DSECT, which can be found in the CTMBAPI member in the IOA MAC library.
The reason codes are listed below:
rc |
Description |
---|---|
200 |
SYNTAX ERROR |
204 |
ERROR IN OPENING DAAPI file |
208 |
DUPLICATE ERROR |
212 |
UNRECOGNIZED COMMAND IN BAPI DSECT |
216 |
CTMAPQ INTERNAL ERROR |
220 |
IF statement NOT SATISFIED |
224 |
AJF OPEN ERROR |
228 |
GETMAIN ERROR |
232 |
INVALID RBA |
236 |
QNAME ERROR |
240 |
QNAME ERROR |
244 |
READ OF RECORD 0 FAILED |
248 |
MIT WAS NOT FOUND |
252 |
CTMUCK INITialization FAILED |
256 |
RESOURCE FILE OPEN ERROR |
262 |
RESOURCE NOT FOUND |
266 |
NOT A Control-M FILE |
270 |
DYNAMIC ALLOCATION FAILED |
274 |
LOAD OF PROGRAM FAILED |
278 |
NEW DAY IN PROCESS |
282 |
TOO MANY TAGS DEFINED |
286 |
BAPI DID NOT RETURN ALL LINES |
290 |
NO VALUE SUPPLIED IN SET GLOBAL |
294 |
GLOBAL ACTION FAILED |
298 |
GLOBAL ACTION FAILED |
302 |
GLOBAL ACTION FAILED |
306 |
ILLEGAL JOBID FORMAT |
310 |
JOB FORMAT CONVERSION ERROR |
314 |
JOB NOT HELD |
318 |
JOB NOT BUILT - CTMJOB ERROR |
322 |
SAVED JOB SIZE INCORRECT |
326 |
ERROR DURING JOB SAVE |
330 |
Control-M MONITOR NOT ACTIVE |
334 |
CTMUCK RETRY LIMIT REACHED |
Corrective Action: No action is required.
Explanation: A valid action code was specified, but no other mandatory keywords were supplied. Therefore CTMAPI cannot perform the action that was requested.
For further information on mandatory keywords, see the CTMAPI appendix in the Control-M for z/OS User Guide.
The action is not performed.
Corrective Action: Correct the request by inserting the mandatory keywords.
Explanation: The same keyword was specified more than once.
The action that was requested is rejected.
Corrective Action: Correct the request by removing the duplicate keyword specifications, and resubmit the request.
Explanation: In an action request, a keyword was specified that requires a value, but no value was found.
For example, the keyword DSNAME was specified, but no data set name was specified.
The request is rejected.
Corrective Action: Correct the syntax of the command, and reissue the request.
Explanation: A parameter was set to a value that exceeds the maximum valid length.
The request is rejected.
Corrective Action: Correct the command to ensure that the lengths of the values of all parameters are valid.
Explanation: This information message serves as an echo line, showing the input to CTMAPI.
Corrective Action: No action is required.
Explanation: A CTMAPI request was issued, but the action requested is not one defined by CTMAPI.
The request is rejected.
Corrective Action: Correct the command so as to ensure that only valid actions are requested.
Explanation: This information message indicates that CTMAPI successfully performed a SEARCH or IF action.
Corrective Action: No action is required.
Explanation: This information message indicates that CTMAPI was unsuccessful in performing a SEARCH or IF action.
Corrective Action: No action is required.
Explanation: CTMAPI could not perform the action that was requested because of a syntax error in the request.
This message is usually accompanied by other messages that clarify the nature of the error.
The request is rejected.
Corrective Action: Examine the request and correct the error.
Explanation: An internal error occurred while CTMAPI was performing the SEARCH AJF command. Possible causes are such problems as failure to get memory, failure to find the AJF that was specified, and so on.
Usually this message is accompanied by other messages issued by CTMAPI or CTMAPQ.
The command is rejected.
Corrective Action: Examine any accompanying messages, and take appropriate corrective action.
Explanation: An AJF action that was requested was not performed. Usually, this message is accompanied by other messages that explain the reason.
The AJF action is not performed.
Corrective Action: Examine the accompanying messages to ascertain the nature of the problem, and take appropriate corrective action.
Explanation: An AJF action that was requested could not be performed, because the New Day procedure is holding the AJF. No action can be performed on the AJF until the New Day procedure releases it.
The AJF action is not performed.
Corrective Action: Wait for a time, until the New Day procedure ends, and reissue the request.
Explanation: This message is issued when a user edited a job definition in the Job Scheduling Definition screen (Screen 2), and
Corrective Action: Correct the problematic ON PGMST statement.
Explanation: This message describes the action taken by CTMAPI on a job in the Active Jobs file.
The variables in this message are:
CTMAPI performs the action and issues this message. This message is followed by one of the following messages:
Corrective Action: Verify that the action identified in this message was performed on the correct job.
Explanation: The CTMAPI utility failed to perform the requested action on the jobName job, whose order ID is orderId. The reason for the failure is described by the following rsn codes:
rsn |
Description |
---|---|
4 |
Invalid request (or parameters) |
8 |
Request to delete non-held entry Request to free non-held entry Request to change non-held entry |
12 |
Open of AJF (ddname DACHKPT) failed |
16 |
ENQUE failed |
20 |
MIT phase changed |
24 |
No room on AJF for more changes |
28 |
Request to act on deleted entry |
32 |
Request to rerun an unfinished job |
36 |
Request to free while still requested change |
40 |
Request for AJF action while still in process |
44 |
Request to delete while *p request active |
48 |
Security violation |
52 |
Rerun desicion was changed - rerun not performed |
56 |
Restart decision was changed - restart not performed |
60 |
Job not waiting for confirmation |
64 |
Restart decision was deleted - restart not performed |
68 |
Request to react an undisappeared job |
72 |
FORCE OK not performed - job already running |
76 |
FORCE OK not performed - job already rerun |
80 |
FORCE OK not performed - job already ended "OK" |
84 |
FORCE OK not performed - cyclic job |
88 |
Exit did the work by itself |
92 |
Load/init of CTMHCP failed |
96 |
Setup failed by CTMHCP |
100 |
Copy failed by CTMHCP |
104 |
Commit failed by CTMHCP |
108 |
Bypass not performed - job not WAIT SCHED |
112 |
KILL not performed - job not executing |
116 |
KILL not performed - job is STC |
120 |
KILL not performed - job is NJE |
Corrective Action: No action is required.
Explanation: A duplicate time zone designation was detected in the TIMEZONE member of the CTM PARM library. The time zone in question is listed in message IOA72ZI, which follows message IOA72SW.
Corrective Action: Correct the TIMEZONE member.
The duplicate entry is ignored.
Explanation: This information message indicates the number of entries found for a requested search.
Corrective Action: No action is required.
Explanation: This information message indicates that the jobName job, whose order ID is orderId, is marked to be excluded from the next downloading of jobs from the AJF to Control-M/EM. This is a response to the CTMAPI command EMDOWNLD EXCLUDE LIST, which lists the jobs currently excluded from the download process.
Corrective Action: No action is required.
Explanation: This information message appears in response to the CTMAPI command EMDOWNLD EXCLUDE LIST, which lists the jobs currently excluded from the download process. No jobs with such a status were found on the AJF.
Corrective Action: No action is required.
Explanation: This information message indicates that a request to exclude the jobName job from downloading is being processed, and the job was found to be a group entity. As a result, all jobs in the group are marked as excluded from downloading.
Corrective Action: No action is required.
Explanation: This information message contains the timezone entry and description text.
Corrective Action: See message IOA72SW.
Explanation:The MemName member is not available and cannot be overwritten.
Corrective Action: Check/release the MemName member.
Explanation: The install library specified in the message does not exist, or has an invalid DSNAME.
The variables in this message are:
A prompt is issued for the base prefix.
Corrective Action: Check if the library was installed, or if the prefix was misspelled, and correct accordingly.
Explanation: The basepref.INSTALL parameter points to a data set that is not a base library. A base library must contain the IOAIC00A member.
A prompt is issued for a base prefix.
Corrective Action: Specify the correct base library prefix.
Explanation: The Environment table was not found in the specified install library.
The ICE application terminates.
Corrective Action: Reload the required install library from the installation tape.
Explanation: The application failed to allocate the dsn dataset name in the environment’s lib library.
Corrective Action: Consult your system administrator to check for an MVS allocation problem.
Explanation: This information message indicates that no environment exists or is selected. Either this is the first time ICE was activated, or no current environment exits. The system cannot proceed with any activity other than ENVIRONMENTS.
Corrective Action: In the ICE Main Menu, select Installation and then select the ENVIRONMENTS activity. If needed, define an environment; select a defined environment.
Explanation: An invalid product ID was specified. Product ID is a three letter abbreviation of an IOA product, for example, CTM for Control-M.
Corrective Action: Specify a valid product ID.
Explanation: A value other than YES or NO was specified in the Enforce step order parameter.
Corrective Action: Specify YES or NO.
Explanation: The user specified a product and an activity that cannot be specified together. Certain activities are valid only when installing certain products. For example, activities INSTALL, COPY IOA, and MAINTENANCE are valid only for product ID IOA.
Corrective Action: Specify another activity (or change the product ID).
Explanation: The user selected an activity that is not valid when installing a product which is not product.
Corrective Action: Change the activity or the product ID.
Explanation:The message is displayed when one of the following SMP/E processes is attempted on a cloned environment:
These processes cannot be performed since cloned environments do not include the SMP/E installation utilities.
Corrective Action: Avoid selecting the above ICE options on cloned environments.
Explanation: The user requested activity COPY IOA for an environment created from the product tape. This is not permitted.
Corrective Action: If this message was issued in a Default or an IOA cloned installation, see the INCONTROL for z/OS Installation Guide, “Customizing INCONTROL Products.”
If this message was issued in a customized installation, select the ENVIRONMENTS activity and then select an environment whose CREATE FROM parameter is an environment ID.
Explanation: This error message indicates that the value of the parameter PFMSMF is incorrect.
Corrective Action: Set the value of the parameter PFMSMF to 0 or a number between 128 and 255.
Explanation: The first position of the environment name is not an alphabetic character.
A prompt is issued for the environment name parameter.
Corrective Action: Specify a value in the environment name parameter with an alphabetic character in the first position.
Explanation: The same prefix is specified for the base and for the environment. The same prefix cannot be used for both the environment data sets and for the base data sets.
A prompt is issued for the environment prefix parameter.
Corrective Action: Specify an environment prefix different from the base prefix.
Explanation: A DSNAME that does not conform to DSNAME syntax rules is specified or the field was left blank. The DSNAME must conform to DSNAME syntax rules and cannot be empty.
A prompt is issued for the DSNAME.
Corrective Action: No action is required.
Explanation: The unit or volume names are missing. Both the unit and volume names must be supplied.
A prompt requests the missing parameter.
Corrective Action: Specify the missing name.
Explanation: The environment ID is specified as TAPE or EPD. The environment ID can be any string, up to eight characters, except the strings TAPE or EPD.
A prompt is issued for the environment ID parameter.
Corrective Action: Specify an environment ID other than TAPE or EPD.
Explanation: An attempt to define a new environment uses the name/installation prefix of a previously defined environment. The name of an environment/installation prefix must be unique.
A prompt is issued for the environment name/installation prefix parameter.
Corrective Action: Specify a name for the environment/installation prefix which does not match the name/installation prefix of another environment.
Explanation: This information message indicates that the specified environment was deleted as required.
The entry in the environment table was deleted. The libraries were not deleted.
Corrective Action: No action is required.
Explanation: There was an attempt to create a new environment from an existing environment, but the environmentID source environment does not exist.
A prompt is issued for the environment ID parameter.
Corrective Action: Change the source environment ID to one that already exists.
Explanation: An attempt to install, in a single base, more than one environment from the product tape failed. Only one environment, per base library, can be installed from the same product tape.
Corrective Action: Select another environment from which to install the new environment.
Explanation: The installation application failed to load the ISPLINK module. ICE requires the use of the ISPF ISPLINK module, and therefore loads the module during installation.
Corrective Action: Consult your system administrator who should check the ISPF installation.
Explanation: The memName member does not exist.
A prompt is issued for the member parameter.
Corrective Action: Check that the member name and library are specified correctly.
Explanation: An invalid action code was specified. The valid action codes appear on each screen.
Corrective Action: Specify a valid action.
Explanation: A major or a minor step was selected, but previous steps were optional, excluded, or not completed. If ENFORCE STEP ORDER is specified as YES, the application checks the prior steps.
Corrective Action: Complete prior steps, or specify ENFORCE STEP ORDER=NO.
Explanation: This information message indicates that the current screen is in browse mode.
Corrective Action: No action is required.
Explanation: An attempt to mark a major step as completed when at least one mandatory minor step was not completed failed. A major step can be marked as completed only when all mandatory minor steps have been completed.
Corrective Action: Complete the mandatory minor steps.
Explanation: The online help file cannot be allocated. The online help file is allocated when the help is requested, or EXTERNAL STEP is selected.
Corrective Action: Check that the IOAIMxxx member, where xxx is the Product ID, appears in the basepref.INSTALL library.
Explanation: The keyword keyName in Special Edit (Data * type step) does not appear in the specified member. The Special Edit process searches for the keyword in the target member and, if requested, in the reference member. If the keyword is not found in either one of these members, this messages is issued.
Corrective Action: If the identified member is the reference member, choose another member, or specify N to relinquish the use of a reference. If the specified member is the target member, copy it from the base library into the target member.
Explanation: An attempt to specify the name of a target or distribution zone as GLOBAL failed. In SMP/E, GLOBAL is reserved for the name of the global zone.
A prompt is issued for the target or distribution zone parameter.
Corrective Action: Specify another name for the zone in question.
Explanation: Identical names were specified for the target and distribution zones. Target and distribution zone names must be unique.
A prompt is issued for the target or distribution zone parameter.
Corrective Action: Change either the target or distribution zone name.
Explanation: Identical prefixes were specified for the target and global prefixes. Target and global prefixes must be unique.
A prompt is issued for the target or prefix parameter.
Corrective Action: Change the target prefix.
Explanation: Identical prefixes were specified for the distribution and global prefixes. Distribution and global prefixes must be unique.
A prompt is issued for the distribution prefix parameter.
Corrective Action: Change the distribution prefix.
Explanation: Identical prefixes were specified for the distribution and target prefixes. Distribution and target prefixes must be unique.
Corrective Action: Change either the distribution or target prefix.
Explanation: This step can be marked as COMPLETE only after being selected at least once.
Corrective Action: Select this member, and then mark it as COMPLETE.
Explanation: The step can be marked as COMPLETE only after the process finishes OK.
Corrective Action: Make sure that the process finishes OK, and than mark it as COMPLETE.
Explanation: There was an attempt to mark the Data Type minor step as completed, but at least one of its mandatory parameter values was not specified. The names of the problematic parameters are listed in the message.
The step is not marked as completed.
Corrective Action: Select the step again and specify the missing values.
Explanation: A non-numeric or non-integer value was specified for the varName variable.
A prompt is issued for the variable.
Corrective Action: Specify a numeric value for the variable.
Explanation: An invalid value was specified for the ParmName parameter.
The word "Parameters" is a valid value for the ParmName parameter.
Corrective Action: Specify a valid value for the parameter.
Explanation: The input value for the variable identified in the message was too short.
A prompt is issued for the variable.
Corrective Action: Specify a character string for the variable that contains at least the minimum number of characters indicated in the message.
Explanation: The input value for the variable identified in the message was too long.
A prompt is issued for the variable.
Corrective Action: Specify a character string for the variable that does not exceed the maximum length indicated in the message.
Explanation: The input value for the variable identified in the message was too large.
A prompt is issued for the variable.
Corrective Action: Specify a number for the variable that is less than the value indicated in the message.
Explanation: The input value for the variable identified in the message was too small.
A prompt is issued for the variable.
Corrective Action: Specify a number for the variable that exceeds the value indicated in the message.
Explanation: The input value for the variable identified in the message was not in the indicated range.
A prompt is issued for the variable.
Corrective Action: Specify a number for the variable within the range specified in the message.
Explanation: The input value for the variable identified in the message was not one of a number of valid values.
A prompt is issued for the variable.
Corrective Action: Specify for the variable one of the valid codes indicated in the message.
Explanation: A mandatory variable has no value.
A prompt is issued for the variable.
Corrective Action: Specify a value for the variable.
Explanation: The DSNAME for the variable does not conform to DSNAME syntax rules or is empty. The DSNAME must conform to DSNAME syntax rules.
A prompt is issued for the variable.
Corrective Action: Correct the DSNAME.
Explanation: The value of the specified variable is invalid.
A prompt is issued for the variable.
Corrective Action: Refer to the INCONTROL for z/OS Installation Guide for the valid format and values of the variable.
Explanation: There is no minus sign - or plus sign + before the identified field.
A prompt is issued for the variable.
Corrective Action: Insert a minus sign - or a plus sign + at the beginning of the field.
Explanation: An invalid value specifies the hour of the day. The hour value must be between 00 and 23.
A prompt is issued for the variable.
Corrective Action: Specify an hour value between 00 and 23.
Explanation: An invalid value specifies the minute of the day. The minute value must be between 00 and 59.
A prompt is issued for the variable.
Corrective Action: Specify a minute value between 00 and 59.
Explanation: A non-hexadecimal value was specified for the specified variable. The value must be either 0 to 9, or A to F.
A prompt is issued for the variable.
Corrective Action: Specify a hexadecimal value.
Explanation: An attempt to install product prod1 before concluding the installation of the prerequisite product prod2 failed.
Some products can be installed only after other products have been installed. For example, IOA must be installed before all other IOA products.
Corrective Action: Complete all the installation steps of the prerequisite product.
Explanation: The values for variable 1 and variable 2 in xxxPARM are identical. If in xxxPARM is missing variable 1 and variable 2 are in the same member.
Corrective Action: Choose another value for one of the variables.
Explanation: The values of the CTM or CTD parameter were not specified as Y.
Corrective Action: Specify CTM or CTD as Y.
Explanation: The var variable can contain only two qualifiers (only one dot is allowed).
Corrective Action: Correct the var variable to contain only two qualifiers (with only one dot).
Explanation: An invalid value is specified for SMF. Valid values for SMF are either NO, or a numeric value in the range 128-255.
Corrective Action: Change the value of the SMF parameter to NO, or a number between 128 and 255.
Explanation: When installing IOA, installation of a dual database was requested by specifying Y in the DUALDB parameter. For improved performance and recovery capability, place the dual file on a different disk and (preferably) on a different disk controller than the rest of the IOA Core:
Corrective Action: Specify different volumes for the IOA Core and dual files.
Explanation: When installing IOA, installation of a dual database was requested by specifying Y in the DUALDB parameter. However, one or both of the following parameters were specified NONE (rather than a valid value):
Corrective Action: Either change the DUALDB field to N or make sure that both a valid unit number is specified for DUALUNIT and a valid volume is specified for DUALVOL.
Explanation: No value is specified for either MAXDAYS or MAXRUNS. A value must be specified for at least one of these parameters.
Corrective Action: Specify a value in the MAXDAYS parameter, or the MAXRUNS parameter, or both.
Explanation: No value is specified for the APPLID parameter when COMM is set to SNA, or there is no value specified for the PORT parameter when COMM is set to TCP.
Corrective Action: Specify a valid value in the APPLID or PORT accordingly.
Explanation:This is one of two messages with the same ID, but different text.
DONTCOPY is specified in the PROCLIB and SITEPROC parameters but an invalid value is specified in the PROCPRFA parameter.
Corrective Action: Change the value of the PROCPRFA parameter to IOA as indicated in the message.
Explanation:This is one of two messages with the same ID, but different text.
DONTCOPY is specified in the SYSPROCA parameter, but an invalid value is specified in the CLISTNMJ parameter.
Corrective Action: Change the value of the CLISTNMJ parameter to CTJXVER as indicated in the message.
Explanation: The value of the ISPF libraries prefix of the O.S. and/or the value of the ISPF language suffix (as set by the ISPFPREF and ISPFLANG variables, respectively) are invalid. An ISPF library with the supplied prefix and language suffix does not exist in the system.
Note that the language value must be one of the following: ENU, DES, DEU, JPN, or ENP
Corrective Action: Check and correct the ISPFPREF and ISPFLANG parameters according your system ISPF libraries.
Explanation: The supplied non-IOA data set name does not exist or is not cataloged. A data set name was specified to which an IOA data set is to be copied.
Corrective Action: Check that the specified data set name is correct.
Explanation: The SHRQNM field is blank or has the same value as the QNAME field, when the value of the IOAID field is greater than one. When the IOAID is greater than one, a unique name must be specified for the shared queue.
Corrective Action: Specify a unique name in the SHRQNM field.
Explanation: A DAYTIME value is specified for Control-O that is different from the DAYTIME value of Control-M, which was installed earlier.
Corrective Action: Change Control-O DAYTIME to match that of Control-M.
Explanation: The HSTSIZE value cannot be less than the AJFSIZE value.
Corrective Action: Change the Control-M HSTSIZE parameter or the AJFSIZE parameter values.
Explanation: When the Control-M/Tape PARALLEL parameter is specified as "S", the MODET parameter must be "TEST".
Corrective Action: Change the Control-M/Tape PARALLEL parameter or the MODET parameter values.
Explanation: When the Control-M/Tape DYNDS parameter is specified as "N", the DYNVOL parameter cannot be "Y".
Corrective Action: Change the Control-M/Tape DYNDS parameter or the DYNVOL parameter values.
Explanation: The val1 value entered for the JS3CHRS parameter is invalid. The text field contains the explanation.
Corrective Action: Change parameter JS3CHRS as required.
Explanation: If the AJFSIZE is greater than 2,000,000 the AJFTYPE parameter must be LARGE or EXTENDED to support more than 2,000,000 AJF records (65,535 tracks).
Corrective Action: Change the Control-M AJFTYPE parameter or the AJFSIZE parameter values.
Explanation: If the HSTSIZE is greater than 2,000,000 the HSTTYPE parameter must be LARGE or EXTENDED to support more than 2,000,000 history records (65,535 tracks).
Corrective Action: Change the Control-M HSTTYPE parameter or the HSTSIZE parameter values.
Explanation: The installation application could not find or open the specified file.
Corrective Action: Check that the DSNAME and library name are specified correctly.
Explanation: The user specified a non-numeric value for the number of jobs.
Corrective Action: Specify a numeric value for the number of jobs.
Explanation: A non-numeric value is specified for the number of rules.
Corrective Action: Specify a numeric value for the number of rules.
Explanation: A non-numeric value or a number that exceeds the maximum is specified for the number of retention days.
Corrective Action: In the case of a non-numeric value, specify a numeric value for the number of retention days. If the number of retention days is too large, reduce it.
Explanation: No values are specified.
Corrective Action: Specify at least one value.
Explanation: The specified value is neither Y (Yes) nor N (No).
Corrective Action: Specify either Y or N.
Explanation: After value was changed in the screen, there was an attempt to exit without confirmation.
Corrective Action: Specify Y to save the changes, or N to cancel the changes.
Explanation: Either a non-numeric value for the number of volumes or a number that exceeded the maximum was specified.
Corrective Action: Specify a numeric value that does not exceed the limit.
Explanation: A non-numeric value was specified or the field was left empty.
Corrective Action: Specify a numeric value only.
Explanation: A non-numeric block size or a number that was outside the range was specified.
Corrective Action: Specify a numeric value that is within the specified range.
Explanation: The quantities are too large to be handled by the space calculation program.
Corrective Action: Reduce one or more quantities.
Explanation: A non-numeric value was specified or the field was left empty.
Corrective Action: Specify a numeric value only.
Explanation: A value other than A (Automatic) or M (Manual) was specified for EXTEND. Only A or M is a valid value in the EXTEND parameter.
Corrective Action: Specify either A or M for EXTEND.
Explanation: No numeric value is specified for the PERCENT parameter.
Corrective Action: Specify a numeric value in the PERCENT parameter.
Explanation: The specified device type is not supported.
Corrective Action: Specify one of the listed device types in the DEVICE TYPE parameter.
Explanation: One or more volume parameters is specified incorrectly. One VOLUME parameter is mandatory. It must be specified in the first VOLUME field. Any additional VOLUME parameters must be specified consecutively in the subsequent fields, without leaving gaps between them.
Corrective Action: Specify the VOLUME parameters as described above.
Explanation: The specified number of blocks exceeds the maximum allowed.
Corrective Action: Decrease the number of blocks or enlarge the block size.
Explanation: The specified volume serial number contains an invalid character or the field was left blank.
Corrective Action: Correct the volume serial number specified for invalid characters or make sure that the field is not empty.
Explanation: DUAL=N is specified, but the field on which the cursor is positioned is neither blank nor N. When DUAL=N is specified by the user, the field in question must either be left empty, or be filled in with an N.
Corrective Action: Either blank out the field or specify N.
Explanation: The specified member was not found in the specified library.
Corrective Action: Check the member and library name, and correct if necessary.
Explanation: This information message indicates that the data specified was successfully incorporated into the specified column.
Corrective Action: No action is required.
Explanation: This information message indicates that the specified variable in the identified table was reset as required.
Corrective Action: No action is required.
Explanation: The specified value is invalid.
Corrective Action: Specify either YES or NO.
Explanation: This warning message requests confirmation for copying parameter values from a previous IOA installation to a new installation. The message “Confirm erasing and replacing all entered data” appears on the screen with a default of NO to prevent accidental override of new installation values with old ones.
Corrective Action: To override the parameter values in the new installation with those of the previous installation, specify YES in the “Confirm erasing and replacing all entered data” field.
Explanation: An internal error occurred. As a result no reference value was inserted into the table.
In this message, rc is the return code issued by ISPF. Valid values are:
Return Code |
Explanation |
---|---|
12 |
Table is not open |
16 |
Truncation occurred when reading a table |
20 |
A severe error occurred when reading a table |
24 |
Dynamic allocation of a library and member failed |
Corrective Action: Check the return code specified in the message in ISPF documentation, and correct accordingly. Rerun the activity or step.
Explanation: An internal error occurred, and as a result the requested action was not performed.
In this message, rc is the return code issued by ISPF. Valid values are:
Return Code |
Explanation |
---|---|
12 |
Table is not open |
16 |
Truncation occurred when reading a table |
20 |
A severe error occurred when reading a table |
24 |
Dynamic allocation of a library and member failed |
Corrective Action: Check the return code specified in the message in ISPF documentation, and correct accordingly. Rerun the activity or step.
Explanation: This information message indicates that there is no reference data in either of the columns in the screen.
Corrective Action: No action is required.
Explanation: This information message indicates that the existing ICE tables were replaced by a new set. The values and the step status were copied from the old table to the new.
Corrective Action: No action is required.
Explanation: You cannot select more than one row when selecting a row with "A".
Corrective Action: Make sure that only one row is selected. Clear all but one selected row.
Explanation: This information message indicates that all the values in the specified column of the ICE table were cleared in response to a clear request.
Corrective Action: No action is required.
Explanation: The IOA release, release, is not supported for adaptation.
Corrective Action: Consider upgrading to IOA release release.
Explanation: The same names were used for the input and output libraries.
Corrective Action: Change the names so that they are different.
Explanation: The Reference Libraries Prefix is missing.
Corrective Action: Provide the Reference Libraries Prefix to continue with the Express Upgrade process.
Explanation: In the environment definition panel of ICE, the user asked that the values of the referenced environment will be used in the new environment being referenced. However, the user left the References Libraries Prefix field, which points to the referenced environment, empty.
ICE displays the environment definition panel again.
Corrective Action: Specify a valid prefix in the References Libraries Prefix field and point to the referenced environment. Alternatively, you can set the Insert references into current values field in the panel to No. This means that the values will not be inserted in the current environment.
Explanation: The text describes the step that was performed during the Express installation.
Corrective Action: No action is required.
Explanation: The given prefixes for installation, operation, SMP/E, or databases for the IOA environment already exist. The installation stops and the IOA7E0I message is displayed.
Corrective Action: Return to the long parameters panel and change the prefixes.
Explanation: The given prefixes for installation, operation, or databases for the product are already allocated. The installation stops and the IOA7E0I message is displayed.
Corrective Action: Either return to the long parameters panel and change the prefixes or deselect this product from the Products and Sizes panel.
Explanation: This is a verification error. First the step where the error occurred is indicated and then the error itself is described. The installation stops.
Corrective Action: Fix the parameter and resume the installation.
Explanation: This is an installation error. First the step where the error occurred is indicated and then the error itself is described. The installation stops.
Corrective Action:Analyze the problem to determine if it is a job or a process failure.
Explanation: The installation ended successfully.
Corrective Action: Proceed to the post installation steps.
Explanation: The text describes an action that was performed during the Express Upgrade process.
Corrective Action: No action is required.
Explanation:This tracking error message can contain one of the following messages:
Corrective Action: Analyze the failure, correct the cause of the problem, and then continue with the Express Upgrade process.
Explanation:This tracking warning message can contain one of the following messages:
Corrective Action: No action is required.
Parent Topic |