|
|
|
Reason:
Indicates that the VIP is starting to read control statements from the system input file.
System Action:
None.
User Action:
None.
Reason:
Indicates that the VIP is finished reading control statements from the system input file. Valid requests will now be actioned.
System Action:
None.
User Action:
None.
Reason:
During validation of the control statements, VIP assigns a request number to each separate request. Following a copy of the command P1. statement images, message IUVC01 is issued showning the request number, At the end of the validation phase, valid requests are processed in turn and this message (IUV003) indicates the start of processing for this request.
System Action:
None.
User Action:
None.
Reason:
Indicates normal end of VIP processing. All requests were valid and were actioned.
System Action:
VIP terminates with JCL return code of zero.
User Action:
None.
Reason:
Indicates end of VIP processing. However one or more requests were not actioned due to validation or processing errors which are detailed in previous messages.
System Action:
Program completes with JCL return code 4.
User Action:
Review the system output for other messages. Correct the invalid requests and rerun.
Reason:
Indicates that VIP has abnormally terminated because of unrecoverable errors in one or more requests. These processing errors are detailed in previous messages.
System Action:
Program completes with JCL return code greater than 4.
User Action:
Review the system output for other messages. Correct the invalid requests and rerun.
Reason:
This message is issued at the completion of a VIP request that specified a sublist of applications. For example APPL=(AAA,BBB,CCC) and no records existed for one or more applications:
- for the LIST and COPY functions on the file(s) identified by the INDD= parameter
- for the DELETE functions on the file(s) identified by the OUTDD= parameter
System Action:
Program completes with JCL return code 4.
User Action:
Review the system output for other messages. Determine if the application(s) should exist on the relevant file(s) and rerun if required.
Reason:
An error occurred when trying to access a data set. P1 is the last processed input DD name and P2 the last processed output DD name. The function P3 indicates the type of file function that was being performed.
The internal return code P4, VSAM completion code P5 and VSAM feedback code P6 are also shown.
System Action:
The VIP processing terminates.
User Action:
Contact Technical Support.
Reason:
The VIP has requested system storage during the processing of a request. No storage is available.
System Action:
The program terminates.
User Action:
Increase the region size and rerun, or simplify the VIP requests to process less requests in a single execution step.
Reason:
During validation of the control statements, VIP assigns a request number to each separate request. The number that has been assigned to a request P1 is shown in this message, issued following a copy of the control cards. At the end of the validation phase, valid requests are processed in turn and message IUV003 is issued at the start of processing for this request.
System Action:
None.
User Action:
None.
Reason:
An error has been found during the validation of the VIP control statements. The start of the first command cannot be identified because the first keyword P1 on the first statement is not a valid command name.
System Action:
Control statements are skipped until a command can be recognized.
User Action:
The first word on the first statement (except for blank or comment statements) must be a valid command name (LIST, COPY, DELETE). Correct the control statement and rerun.
Reason:
An error has been found during the validation of the VIP control statements. The word following the command name (LIST, COPY, DELETE) is omitted, that is, the next word is either a new command name or is end of file.
System Action:
Control statements are skipped until a new command can be recognized.
User Action:
Correct the control statement and rerun.
Reason:
An error has been found during the validation of the VIP control statements. The word P1 following the command name (LIST, COPY, DELETE) is not a valid file type. Valid types are PANELS, MODS and OSCNTL.
System Action:
Control statements are skipped until a new command can be recognized.
User Action:
Correct the control statement and rerun.
Reason:
An error has been found during the validation of the VIP control statements. The data starting at P1 is not a valid keyword. Valid keywords are INDD=, OUTDD=, APPL=, LANG= and OPT=.
System Action:
Control statements are skipped until a new command can be recognized.
User Action:
Correct the control statement and rerun.
Reason:
An error has been found during the validation of the VIP control statements. The combination of keyword P1 and command P2 is invalid. For example, the OUTDD= keyword is invalid for the LIST command.
System Action:
Control statements are skipped until a new command can be recognized.
User Action:
Correct the control statement and rerun.
Reason:
An error has been found during the validation of the VIP control statements. The operand value for the keyword identified by P1 has been omitted making the keyword operand incomplete. For example, APPL= was specified but without any data.
System Action:
Control statements are skipped until a new command can be recognized.
User Action:
Correct the control statement and rerun.
Reason:
An error has been found during the validation of the VIP control statements. The operand value for the keyword identified by P1 has been specified as a sublist but the particular command P2 does not support multiple values, making a sublist format invalid. For example, the OUTDD= keyword must specify a single DD name for all commands.
System Action:
Control statements are skipped until a new command can be recognized.
User Action:
Correct the control statement and rerun.
Reason:
An error has been found during the validation of the VIP control statements. The keyword identified by P1 has been specified more than once.
System Action:
Control statements are skipped until a new command can be recognized.
User Action:
Keywords may only be specified once per command. Use sublist format if multiple values are required, for example: invalid: INDD=IN1 INDD=IN2 valid: INDD=(IN1,IN2) Correct the control statement and rerun.
Reason:
An error has been found during the validation of the VIP control statements. The keyword identified by P1 has an invalid sublist because of one of the following reasons:
- The character immediately following the keyword is an opening (left) parenthesis but the last character is not a closing (right) parenthesis. For example: INDD=(AAA,BBB
- The closing (right) parenthesis is followed by a non-blank character. For example: INDD=(IN1,IN2)IN3)
- There are no suboperands in the sublist. For example: INDD=() or INDD=(,,)
System Action:
Control statements are skipped until a new command can be recognized.
User Action:
Complete the sublist specification. Correct the control statement and rerun.
Reason:
An error has been found during the validation of the VIP control statements. The keyword identified by P1 has an invalid value within the operand list. The value P2 is not valid for the type of keyword. For example, the DD name for INDD= or OUTDD= is not a valid DD name.
System Action:
Control statements are skipped until a new command can be recognized.
User Action:
Correct the control statement and rerun.
Reason:
An error has been found during the validation of the VIP control statements. The keyword identified by P1 is not valid for the file type that is identified by P2. For example, the LANG= keyword is invalid when used for an OSCNTL file.
System Action:
Control statements are skipped until a new command can be recognized.
User Action:
Correct the control statement and rerun.
Reason:
An error has been found during the validation of the VIP control statements. The keyword identified by P2 is mandatory for the command identified by P1. For example, the LIST command requires the INDD= keyword.
System Action:
Control statements are skipped until a new command can be recognized.
User Action:
Correct the control statement and rerun.
Reason:
An error has been found during the validation of the VIP control statements. The sublist for the P1 keyword contains a duplicated value,
P2. For example INDD=(IN1,IN2,IN1). Duplicated values are not permitted.
System Action:
Control statements are skipped until a new command can be recognized.
User Action:
Correct the control statement and rerun.
Reason:
An error has been found during the validation of the VIP control statements. A DD name specified within the INDD= or OUTDD= operands is invalid because it is reserved for use as a VIP system file. For example SYSIN or SYSPRINT.
System Action:
Control statements are skipped until a new command can be recognized.
User Action:
Correct the control statement and rerun.
Reason:
An error has been found during the validation of the VIP control statements. The parameter and value identified by P1 is not valid for the file type that is identified by P2. For example, OPT=MAINT is invalid when used for an OSCNTL file.
System Action:
Control statements are skipped until a new command can be recognized.
User Action:
Correct the control statement and rerun.
Reason:
The VIP has requested system storage during the validation of a request. No storage is available.
System Action:
The program terminates.
User Action:
Increase the region size and rerun, or simplify the VIP requests to process less requests in a single execution step.
Reason:
An error has been found during the validation of the VIP control statements. The format of keyword P1 is invalid when used with command
P2. For example:
- the APPL=* keyword value was specified on a DELETE command
- a COPY command specifying OPT=INSTALL and with a sublist of input files (INDD=(DD1,DD2,....) also has applications (APPL=) specified (other than APPL=*).
System Action:
Control statements are skipped until a new command can be recognized.
User Action:
Correct the control statement and rerun.
Reason:
An error has been found during the validation of the VIP control statements. The command identified by P1 is not valid for the file type that is identified by P2. For example, the BUILD command is invalid when used for a PANELS file.
System Action:
Control statements are skipped until a new command can be recognized.
User Action:
Correct the control statement and rerun.
Reason:
An error has been found during the validation of the VIP control statements. The output file DD name P1 is the same as one of the input file DD names specified for the same request. For example: INDD=(FILE1,FILE2,FILE3) OUTDD=FILE2
System Action:
Control statements are skipped until a new command can be recognized.
User Action:
Correct the control statement and rerun.
Reason:
This message is written to the system log when the VIP abends and is unable to write a VIP formatted dump to the system print file because is has failed to open.
System Action:
The VIP ends abnormally.
User Action:
Contact Technical Support.
Reason:
This message is written to the system log when the VIP abends due to an internal error ($NMDUMP). The VIP module P1 and reason code P2 are shown.
System Action:
A VIP formatted dump is written to the system output data set and a system dump requested.
User Action:
Contact Technical Support.
Reason:
The VIP has read an unrecognized record from the input file P1. This message is followed by the record contents in dump format.
System Action:
The VIP terminates.
User Action:
Check the following:
1. Ensure that the input file matches the VIP operation type. For example, when using the COPY PANELS operation, ensure that the dataset indicated by the INDD parameter is a PANELS dataset.
2. Ensure that you are running the correct version of the VIP and that all maintenance has been supplied, as the VIP may have been updated to support new record types.
3. Check the validity of the indicated file and record. Many files used by the VIP have keys that include hex characters which may have become corrupted if they have been transmitted using FTP etc.
If the problem persists, contact Technical Support and provide the following information:
1. The VIP parameter cards (SYSIN)
2. The VIP output (SYSPRINT)
3. A copy of the input file containing the error
Reason:
An error occurred when trying to access a dataset. P1 is the last processed input DD name and P2 the last processed output DD name. The function P3 indicates the type of file function that was being performed.
The internal return code P4, VSAM completion code P5 and VSAM feedback code P6 are also shown.
System Action:
The VIP processing terminates.
User Action:
Contact Technical Support.
Reason:
The VIP has requested system storage during the processing of a request. No storage is available.
System Action:
The program terminates.
User Action:
Increase the region size and rerun, or simplify the VIP requests to process less requests in a single execution step.
Reason:
A BUILD MODS request has completed successfully.
System Action:
None.
User Action:
None.
Reason:
The VIP is processing a COPY MODS request with OPT=MAINT specified but a record on the current input file contains an invalid maintenance tag. Valid tags are A|, U|, and D|. Message IUVM03 follows showing the key of the invalid record and the previous occurrence of message IUVR10 details the DD name of the current input file.
OPT=MAINT must only be used with files that have been created using the MODS Compare Definition Utility (D.AD.U.CM). It may not be used on files that are designed for OPT=INSTALL.
System Action:
The VIP terminates.
User Action:
Check that the correct input file has been specified. Correct and rerun.
Reason:
This message follows IUVM02 and shows the key of the current record. Refer to message IUVM02 for more details.
System Action:
Refer to IUVM02.
User Action:
Refer to IUVM02.
Reason:
An error occurred when trying to access a MODS dataset.
P1 is the last processed input DD name
P2 is the last processed output DD name
P3 indicates the type of file function that was being performed
P4 is the internal return code
P5 is the VSAM completion code
P6 is the VSAM feedback code
System Action:
The VIP processing terminates.
User Action:
Contact Technical Support.
Reason:
The VIP has requested system storage during the processing of a request. No storage is available.
System Action:
The program terminates.
User Action:
Increase the region size and rerun, or simplify the VIP requests to process less requests in a single execution step.
Reason:
The VIP has read an unrecognized record. P1/P2 indicate the data values obtained from the key that are not supported. P3 is the full key value of the record.
System Action:
The record is ignored and the VIP reads the next record. At the end of processing all requests, the VIP will complete with a return code of at least 4.
User Action:
Check that you are using the correct version of the VIP program. If the latest VIP is installed correctly then report the error to Technical Support.
Reason:
The VIP has read an unrecognized MODS message ($MS) record. P1 indicates the message identifier obtained from the key that is not recognized as being owned by an application. P2 is the full key value of the record.
System Action:
The record is ignored and processing continues. However the process may be incomplete. A minimum return code value of 4 is set.
User Action:
Check that you are using the correct files. This error indicates that there is a mismatch between the applications defined in the application register records and the message records.
Reason:
The VIP has read an MODS record for which an application register entry does not currently exist and the record read is not itself an application register definition. P1 is the required aplication ID and
P2 is the full key of the record.
System Action:
The record is processed as normal. An internal application register entry is built without message identifier details.
User Action:
Check that you are using the correct files. This error indicates that there is a mismatch between the applications defined in the application register records and the input records being processed.
Reason:
During processing of a VIP COPY PANELS command where OPT=MAINT has been specified, a record other than a Panel Services record has been found on the current input file. Only panel services may be copied using OPT=MAINT.
System Action:
The current request is terminated and totals (so far) are printed. The VIP continues with the next request.
User Action:
The output file will be partially updated and should be restored before correcting the input file and re-running.
Reason:
An error has occured as indicated by a previous message.
System Action:
The current request is incomplete. The VIP continues with the next request.
User Action:
Refer to the user action(s) specified for any prior messages.
Reason:
An error occured trying to access a PANELS data set.
P1 is the last processed input DD name
P2 is the last processed output DD name
P3 indicates the type of file function that was being performed
P4 is the internal return code
P5 is the VSAM completion code
P6 is the VSAM feedback code
System Action:
The VIP processing terminates.
User Action:
Contact Technical Support.
Reason:
The VIP has requested system storage during the processing of a request. No storage is available.
System Action:
The program terminates.
User Action:
Increase the region size and rerun, or simplify the VIP requests to process less requests in a single execution step.
Reason:
During processing of a VIP LIST or COPY OSCNTL command, some obsolete record types were found on the input file. These records are not appropriate for the current version of the VIP and indicate that the input file was prepared for use with a previous version of the VIP.
System Action:
For the COPY function, the obsolete records are copied to the output file. The VIP continues processing all requests but will terminate with return code 4 (and message IUV005 issued).
User Action:
Contact Technical Support.
Reason:
An error has occured as indicated by a previous message.
System Action:
The current request is incomplete. The VIP continues with the next request.
User Action:
Refer to the user action(s) specified for any prior messages.
Reason:
An error occured trying to access an OSCNTL data set.
P1 is the last processed input DD name
P2 is the last processed output DD name
P3 indicates the type of file function that was being performed
P4 is the internal return code
P5 is the VSAM completion code
P6 is the VSAM feedback code
System Action:
The VIP processing terminates.
User Action:
Contact Technical Support.
Reason:
The VIP has requested system storage during the processing of a request. No storage is available.
System Action:
The program terminates.
User Action:
Increase the region size and rerun, or simplify the VIP requests to process less requests in a single execution step.
Reason:
This message, together with subsequent IUVR02 and IUVR03 messages show record count statistics that are issued for a VIP LIST/COPY/DELETE command for an OSCNTL or PANELS file. This message, IUVR01 is a heading line, and is followed by groups of messages IUVR02 and IUVR03 as follows:
OSCNTL file: Message IUVR02 shows the number of records for a specific record type and message IUVR03 is the total of these for the application or final indicated.
PANELS file: Message IUVR02 is the only message issued. IUVR03 is unused.
The Appl column shows the specific application ID that relates, or "Total" for all application IDs listed. The Record category and type column details the specific record type (IUVR02), or the total type (IUVR03). Depending upon function, one or two record counts and associated headings P1 and P2 will be printed as follows:
LIST Command: In the heading P1 is Records and P2 is blank. The P1 column gives the count of records on the current input file. The P2 column is blank.
DELETE Command: In the heading P1 is Deleted and P2 is blank. The P1 column gives the count of records deleted from the output file. The P2 column is blank.
COPY Command: In the heading P1 is Copied and P2 is Deleted. The P2 column gives the count of records deleted from the output file before copying. The P1 column shows the number of records copied from the current file to the output file.
System Action:
None.
User Action:
None.
Reason:
This message, together with messages IUVR01 and IUVR03 show record count statistics that are issued for a VIP LIST/COPY/DELETE command for an OSCNTL or PANELS file. In the message:
P1 is the application ID
P2 and P3 are record count fields
P4 the specific record type or category Refer to message IUVR01 for further details.
System Action:
None.
User Action:
None.
Reason:
This message, together with messages IUVR01 and IUVR02 show record count statistics that are issued for a VIP LIST/COPY/DELETE OSCNTL file command. In the message:
P1 is the application ID
P2 and P3 are record count fields
P4 is the specific total type Refer to message IUVR01 for further details.
System Action:
None.
User Action:
None.
Reason:
This message, together with subsequent IUVR05 and IUVR06 messages show record count statistics that are issued for a VIP LIST/COPY/DELETE command for a MODS file. This message, IUVR04 is a heading line and is followed by groups of messages IUVR05 and IUVR06 in which:
- The Appl column shows the specific application ID that relates, or "Total" for all application IDs listed.
- Message IUVR06 provides the totals for the preceeding group of IUVR05 messages. IUVR05 shows the total for a specific record type identified in the column headed Record category and type.
System Action:
None.
User Action:
None.
Reason:
This message, together with messages IUVR04 and IUVR06 show record count statistics that are issued for a VIP LIST/COPY/DELETE command for a MODS file. The fields in this message correspond to the columns in message IUVR04 as follows:
P1 is the application ID
P2 and P3 are the MODS component and sub-component codes respectively
P4, P5 and P6 are the UPDATE, ADD and DELETE record counts respectively
P7 is the record category and type
Refer to the descripion of message IUVR04 for additional information.
System Action:
None.
User Action:
None.
Reason:
This message, together with messages IUVR04 and IUVR05 show record count statistics that are issued for a VIP LIST/COPY/DELETE command for a MODS file. The fields in this message correspond to the columns in message IUVR04 as follows:
P1 is the application ID
P2 and P3 are the MODS component and sub-component codes respectively
P4, P5 and P6 are the UPDATE, ADD and DELETE record counts respectively
P7 is the specific total type
Refer to the descripion of message IUVR04 for additional information.
System Action:
None.
User Action:
None.
Reason:
This message is produced for each DD name opened by the VIP. P1 may be either Input or Output and relates to the INDD= or OUTDD= operand accordingly. The specific DD name is identified by P2 and the Dataset Name P3 is obtained from the run JCL.
System Action:
None.
User Action:
None.
Reason:
This message relates to the VIP LIST/COPY command. It shows the total number of records P2 that have been read from the current input file. P1 is a current input DD name from the INDD= operand.
System Action:
None.
User Action:
None.
Reason:
An attempt to process the file identified by DD= P1 has failed because there is no JCL statement for the DD name.
System Action:
The request is terminated.
User Action:
Check that the DD name specified is correct. Either correct the VIP request or amend the run JCL to specify the DD name.
Reason:
An error occurred during a VIP LIST/COPY/DELETE command when trying to open a data set where:
P1 is the DD name
P2 is the VIP return code, values below
P3 is the VSAM completion code
P4 is VSAM feedback code
VSAM completion codes and feedback codes are listed in the appropriate VSAM manual. VIP return codes are as follows:
14 - VSAM error - refer to completion and feedback codes
18 - Invalid file type: Input File is neither a VSAM file nor a sequential file Output File is not a VSAM file
1C - Dummy file, unsupported
System Action:
The VIP processing terminates.
User Action:
Use the return code information described above to determine the exact error cause. If the problem persists contact Technical Support.
Reason:
On opening a VSAM file, the keylength for the KSDS did not match the requirements for the file type that was specified in the request. The value for each file type is as follows:
File Type PANELS MODS OSCNTL
Key Length 36 75 80
The most likely cause of this error is that the DD card for the specific file has the DSN of the wrong data set. For example:
//INDD1 DD DSN=........PANLDIS LIST MODS INDD=INDD1
System Action:
The VIP terminates.
User Action:
Check the DD names specified in the INDD= and OUTDD= parameters. Check the JCL to ensure that the DSN= is for the correct dataset. If necessary use IDCAMS LISTCAT to check the file's attributes. Correct the job and rerun.
| Copyright © 2012 CA. All rights reserved. |
|