10.2 Messages by key

This Section lists VICAR2 error messages in alphabetical order by key. The accompanying message, the numerical value, and the symbolic name by which the error may be referenced in a program are given, followed by a detailed description of what the message means, and the action required to correct the error.

• ALROPN Symbolic Name : FILE_IS_ALREADY_OPEN
  [VIC2-ALROPN] Attempt to open an open file; program error
  Explanation: x/zvopen has been called on a file which is already open. Program error. User action: Please notify the cognizant programmer.
• BADBAND Symbolic Name : IMPROPER_BAND_SIZE_PARAM
  [VIC2-BADBAND] Improper band size parameter; program error
  Explanation: A band size argument (BAND, NBANDS, U_NB) was provided to the indicated routine and was not in an allowable range (usually less than zero).
  User action: Check all the parameters which could have led to the bad sample size. If they are good, it is probably a program error and the cognizant programmer should be consulted.
• BADBINSIZ Symbolic Name : IMPROPER_ BINARY _SIZE_PARAM
  [VIC2-BADBINSIZ] Improper binary size parameter; program error
  Explanation: A binary size argument (U_NBB or U_NLB) was provided to the indicated routine and was not in an allowable range (usually less than zero).
  User action: Check all the parameters which could have led to the bad binary size. If they are good, it is probably a program error and the cognizant programmer should be consulted.
• BADDIM Symbolic Name : BAD_DIM_NAME
  [VIC2-BADDIM] Bad name for an image dimension (DIM1etc.).
  Explanation:
  A bad name was given for one of the dimensions in a multi-dimensional file. This error is the result of a call to x/zvopen or x/zvadd in which the DIM1.. DIM4 or the U_DIM1.. U_DIM4 optional arguments were given with a value which was not one of: SAMP, LINE, BAND, or TIME.
  User Action: If you specified the name for the dimension on the command line, re-specify it with one of the above names. If not, this error represents a program error, so notify the cognizant programmer. If there is a need to add a new name to the list, notify the MIPL system engineer.
• BADELEM Symbolic Name : IMPROPER_ELEMENT_NUMBER
  [VIC2-BADELEM] Improper element number; program error
  Explanation: A value for ELEMENT or NELEMENTS was provided to a label routine that was not in the allowable range (usually less than zero).
  User action: Check all the parameters which could have led to the bad element number. If they are good, it is probably a program error and the cognizant programmer should be consulted.
• BADFILE Symbolic Name : IMPROPER_FILE_NUMBER
  [VIC2-BADFILE] Bad file number for tape
  Explanation: The U_FILE optional is less than zero.
  User action: this is a program error. Please consult the cognizant programmer. Programmer action: Check the value of U_FILE.
• BADFOR Symbolic Name : IMPROPER_FORMAT_STRING
  [VIC2-BADFOR] Improper FORMAT string; program error
  Explanation: The pixel format being passed to the indicated routine is not one of the valid values. This is a program error.
  User action: Please consult the cognizant programmer to verify that a valid format string is being passed. Programmer action: make sure that the FORMAT argument to the indicated routine is one of following values: BYTE, HALF, FULL, REAL, DOUB, or COMP.
• BADINST Symbolic Name : ILLEGAL_INSTANCE
  [VIC2-BADINST] Illegal instance; program error
  Explanation: In a call to x/zvunit, the value given to the INSTANCE argument is greater than the actual number of files given. User action: Verify that all the proper parameters have been input. If they have then this message indicates that a program error has occurred and the cognizant programmer should be consulted. Programmer action: Modify the PDF to require that the user input the appropriate number of files.
• BADLBL Symbolic Name : BAD_ INPUT_LABEL
  [VIC2-BADLBL] Bad input label; check file contents
  Explanation: An error occurredwhile parsing the input label. Either the file has no valid VICAR2 label, or the label is corrupted. User action: If the file has no label, LABEL-CREATE may be used to create one. If the file has a label but this error still occurs, then the label has probably been corrupted, which could indicate an executive error. In the latter case, consult the system programmer.
• BADLBLTP Symbolic Name : BAD_LABEL_TYPE
  [VIC2-BADLBLTP] Bad label type; check file contents
  Explanation: A label type other than HISTORY or SYSTEM has been input to the indicated routine, or neither has been specified. User action: The validity of the label type must be checked. Please consult the cognizant programmer
  Programmer action: Verify that the call to the indicated routine contains a SYSTEM or HISTORY label, or that a valid label type was specified.
• BADLEN Symbolic Name : IMPROPER_LENGTH
  [VIC2-BADLEN] Improper length; program error
  Explanation:
  ULEN was either required for the indicated routine and not given, or it was given an invalid value. User action: The size and existence of the value given to ULEN must be checked. Please consult the cognizant programmer.
  Programmer action:
  The value of ULEN must be positive and less than the maximum string size. It is required to be given for multi-valued string items passed from C, and all string items (multi-valued or single value) passed from FORTRAN declared with a BYTE or LOGICAL*1. Strings passed from FORTRAN declared asCHARACTER do not require the ULEN optional.
• BADLINE Symbolic Name :IMPROPER_LINE_SIZE_PARAM
  [VIC2-BADLINE] Improper line size parameter; program error
  Explanation: A line size argument (LINE, NLINES, U_NL) was provided to the indicated routine and was not in an allowable range (usually less than zero). User action: Check all the parameters which could have led to the bad sample size. If they are good, it is probably a program error and the cognizant programmer should be consulted.
• BADLINST Symbolic Name :IMPROPER_LABEL_INSTANCE
  [VIC2-BADLINST] Improper label instance number; program error
  Explanation: An INSTANCE number was provided to a label routine that was not in the allowable range (usually less than zero). User action: Check all the parameters whichcould have led to the bad instance. If they are good, it is probably a program error and the cognizant programmer should be consulted.
• BADMETH Symbolic Name : IMPROPER_METHOD_STRING
  [VIC2-BADMETH] Improper METHOD string; program error
  Explanation: The METHOD optionalargument contained an invalid value for the routine indicated. This is a program error. The valid values for METHOD are RANDOM, SEQ. User action: Please consult the cognizant programmer so that the value of METHOD can be checked.
• BADMODESTR Symbolic Name :IMPROPER_MODE_STRING
  [VIC2-BADMODESTR] Improper MODE string; program error
  E xplanation: The MODE optional parameter had an invalid value associated with it in the indicated routine. This is a program error.
  User action: Please consult the cognizant programmer so that the value of MODE can be checked.
  Programmer action: The only valid values for MODE are “ADD”, “INSERT”, and “REPLACE”. Check that the call to x/zvopen uses one of these values.
• BADNAM Symbolic Name : BAD_FILE_PARAM_NAME
  [VIC2-BADNAM] Bad file parameter name; program error
  Explanation: An error was encountered when x/zvunit tried to look up a file name in the command line. This error probably indicates a mismatch between the program and the PDF file associated withit. User action: Please consult the cognizant programmer so that any disparity between the program and the PDF can be corrected.
• BADOPR Symbolic Name : IMPROPER_OPERATION
  [VIC2-BADOPR] Operation conflicts with open attributes; program error
  Explanation:Improper operation. The program tried to perform an operation on the indicated file which is forbidden in the mode in which the file has been opened. For instance, trying to writeto a file which has been opened for READ. User action: this is generally a program error. Consult the cognizant programmer for the program in question.
• BADOPSTR Symbolic Name : IMPROPER_OP_STRING
  [VIC2-BADOPSTR] Improper OP string; program error
  Explanation: The OP optional parameter had an invalid value associated with it in the indicated routine. This is a program error. User action: Please consult the cognizant programmer so that the value of OP can be checked. Programmer action: The only valid values for OP are “READ”,”WRITE”, and “UPDATE”. Check that the call to x/zvopen uses one of these values.
• BADORG Symbolic Name : BAD_ORG
  [VIC2-BADORG]ORG key word (file organization) is not valid.
  Explanation:
  The file organizationkey word-ORG -passed to the indicated routine is not one of the valid values. The valid file organizations are BSQ (band sequential), BIL (Band interleaved by line), and BIP(Band interleaved by pixel). User Action: Notify the cognizant programmer of the program which failed or MIPL.
• BADSAMP Symbolic Name :IMPROPER_SAMP_SIZE_PARAM
  [VIC2-BADSAMP] Improper sample size parameter; program error
  Explanation: A sample size argument (SAMP, NSAMPS, U_NS) was provided to the indicated routine and was not in an allowable range (usually less than zero). User action: Check all the parameters which could have led to the bad sample size. If they are good, it is probably a program error and the cognizant programmer should be consulted.
• BADSIZ Symbolic Name :IMPROPER_IMAGE_SIZE_PARAM
  [VIC2-BADSIZ] Improper image size parameter; program error
  Explanation: A size argument (U_N1, U_N2, U_N3, or U_N4) was provided to the indicated routine and was not in an allowable range (usually less than zero). User action: Check all the parameters which could have led to the bad size. If they are good, it is probably a program error and the cognizant programmer should be consulted.
• BADTRANS Symbolic Name :INVALID_FORMAT_TRANSLATION
  [VIC2-BADTRANS] Invalid format translation
  Explanation:
  The data format translation specified with U_FORMAT is not legal. Currently no translations are allowed for DOUB data formats. User action: make sure you specified the correct file.
  Programmer action: Don't allow conversions to/from DOUBle format.
• BUG Symbolic Name : INTERNAL_ERROR
  [VIC2-BUG]Internal VICAR bug check failure —Notify system programmer
  Explanation: An internal bug check in the VICAR run-time library failed, indicating a bug in the run-time library. User Action: this error should never occur, hence please notify the VICAR system programmer immediately.
• CONVERR Symbolic Name : CONVERSION_ERROR
  [VIC2-CONVERR] Conversion error; program error
  Explanation: The data item passed to the indicated routine is incompatible with the FORMAT parameter. For example, an integer is expected and a real is passed. User action: If the parameter is user specified check to see that the data item being passed to the routine is in the expected format. If the problem is still not obvious, consult the cognizant programmer. Programmer action: Check the value of the item passed to the the indicated routine.
• DUPKEY Symbolic Name : DUPLICATE_KEY
  [VIC2-DUPKEY] Duplicate key; program error
  Explanation: An attempt has been made to add a label item with the label routine, x/zladd, for a key that already exists. A duplicate item cannot be added under the same HISTORY subset. User action: If the item is user specified a new subset must be created to accept the item. If the item is not user specified and this message is displayed consult the cognizant programmer.
• END OFVOL Symbolic Name : END_OF_VOLUME
  [VIC2-END OFVOL] End of volume (double tape mark) reached
  Explanation: The end of volume mark (double tape mark or double end of file) was hit when trying to open a file on an input tape. User action: Scan the tape to determine the actual number of files on it, and make sure that the program does not try to access a file beyond that number.
• EOF Symbolic Name : END_OF_FILE
  [VIC2-EOF] End of file
  Explanation: The end of file was reached. For input disk files, this error probably indicates an attempt to read beyond the number of lines in the image. Otherwise, this error indicates that the physical end of file was reached on an I/O operation. User action: this could be either a user or a programmer error. Verify that all the parameters to the program in question are good values, and if so, consult the cognizant programmer.
• EOLAB Symbolic Name : END_OF_LABEL
  [VIC2-EOLAB] End of label
  Explanation: you have reached the end of the label on an x/zlninfo . This is an informational message which is used as a flag within a routine. User action: If this message is displayed consult the cognizant programmer.
• ERRACT Symbolic Name : BAD_ERR_ACT_ VALUE
  [VIC2-ERRACT] Bad IO_ACT, OPEN_ACT, or ERR_ACT; program error
  Explanation: Arguments IO_ACT, OPEN_ACT, and ERR_ACT must contain the characters: 'U', 'A', or 'S', or any combination thereof. User action: The contents of the arguments must be checked. Please consult the cognizant programmer. Programmer action: Verify that the arguments IO_ACT, ERR_ACT, and OPEN_ACT contain the characters 'U', 'S', 'A', alone or in any combination.
• FILETYPE Symbolic Name : BAD_FILE_TYPE
  [VIC2-FILETYPE] Invalid file type
  Explanation:
  The file type (the TYPE optionalto the indicated routine) was not a supported type. Currently the types supported are'IMAGE', 'PARM', and 'PARAM', and the IBIS types 'GRAPH1', 'GRAPH2', 'GRAPH3', and'TABULAR'. User action: If the file type was specified on the command line (eg, you tried to use LABEL-REPLACE to change it), then use one of the valid types. Otherwise, it may be a program error. Programmer action: Use only the valid types listed above.
• FNDKEY Symbolic Name : CANNOT_FIND_KEY
  [VIC2-FNDKEY] Cannot find key; program error
  Explanation: The indicated routine is unable to find the specified key in the label.
  User action: If the key is user specified, check the label to verify that the label item exists. If, after checking, the problem is not obvious, consult the cognizant programmer.
• FORREQ Symbolic Name : FORMAT_ OPTIONAL_REQUIRED
  [VIC2-FORREQ] The FORMAT optional is required with xladd
  Explanation: The FORMAT optional cannot be defaulted.
  User action: Enter the desired FORMAT.
• HSTNTASC Symbolic Name : HIST_NAME_HAS_NON_ASCII_CHAR
  [VIC2-HSTNTASC] History name has non-ASCII characters;program error
  Explanation: HIST name has a non-ASCII character. The HIST optional for the label processing routines was given a name which contains a character which is not a valid ASCII character. The HIST item (TASK name) must be a valid ASCII string, less than 8 characters long. User action: this is most likely a program error. Please consult the cognizant programmer.
• ILLFOREQ Symbolic Name : ILLEGAL_FORMAT_REQUEST
  [VIC2-ILLFOREQ] Illegal format request; program error
  Explanation: Type is not STRING, INT, or REAL. User action: Consult the cognizant programmer so that the validity of the type specified can be checked.
• INSUFMEM Symbolic Name : INSUFFICIENT_MEMORY
  [VIC2-INSUFMEM] Insufficient memory; consult system programmer
  Explanation: Insufficient memory for operation. VICAR2 was not able to allocate sufficient memory foran internal function. User action: this error probably indicates a memory quota was exceeded. See the system manager or system programmer to determine the exact cause and perhaps increase the amount of memory available.
• LBLIO Symbolic Name : LABEL_IO_ERROR
  [VIC2-LBLIO] Label I/O error; check file contents
  Explanation: Usually a system error or VICAR2 bug. User action: Inform VICAR2 system programmer.
• LNGACT Symbolic Name : ACT_STRING_TOO_LONG
  [VIC2-LNGACT] ACT string too long; program error
  Explanation: The argument CLOS_ACT is longer than the maximum number of allowed characters.
  User action: The size of, CLOS_ACT must be checked. Please consult the cognizant programmer. Programmer action: Verify that the string passed is the proper length.
• LNGCOND Symbolic Name : COND_STRING_TOO_LONG
  [VIC2-LNGCOND] COND string too long; program error
  Explanation: COND string has exceeded maximum number of allowable characters. User action: The size of the string, COND, must be checked. Please consult the cognizant programmer. Programmer action: Check COND argument in indicated routine and verify that it is within the allowable stringlength.
• LNGHST Symbolic Name : HISTORY_NAME_TOO_LONG
  [VIC2-LNGHST] History name too long; program error
  Explanation: The history NAME is too long. The HIST optional for the label processing routines was given a name which contains more than eight characters. The HIST item (TASK name) must be a valid ASCII string, less than 8 characters long. User action: Most likely a program error. Consult the cognizant programmer.
• LNGMES Symbolic Name : ERROR_MESS_TOO_LONG
  [VIC2-LNGMES] Error message too long; program error. Not used.
• LNGMESS Symbolic Name : ERR_MESS_TOO_LONG
  [VIC2-LNGMESS] Error message too long; program error
  Explanation: Error message has exceeded the maximum string size allowed (132 characters). User action: Consult the cognizant programmer.
• MODINPLBL Symbolic Name :CAN_NOT_MODIFY_AN_ INPUT_LABEL
  [VIC2-MODINPLBL] Attempt to modify input label; program error
  Explanation: An attempt was made to modify a read only file. User action:Consult the cognizant programmer.
• MODOPNUN Symbolic Name : CANNOT_MOD_OPEN_UNIT
  [VIC2-MODOPNUN] An open unit cannot be modified; call x/zvclose first
  Explanation: An attempt to call the routine x/zvadd was made after a unit was already open. In order to prevent the internal table from being corrupted, this operation is defined as illegal. User action: Consult the cognizant programmer. Programmer action: Prevent the calling of x/zvadd after a unit has been opened. NL may be updated by using only x/zladd, and other fields may not be modified after a unit is opened.
• MULTPARMFILE Symbolic Name :MULTIPLE_PARAMETER_FILES
  [VIC2-MULTPARMFILE] Multiple parameter files cannot be open at once
  Explanation: An attempt was made to open a parameter file before the previous one was closed. Only one parameter file can be open at a time. User action: this is a program error. Consult the cognizant programmer. Programmer action: Finish processing one parameter file before using another. Make sure that all parameter files are closed using x/zvpclose. x/zvclose will not properly close a parameter file.
• NOARRAY Symbolic Name : ARRAY_IO_NOT_ALLOWED
  [VIC2-NOARRAY] Array I/O not allowed to non-disk device
  Explanation: An attempt was made to open a non-disk file for array I/O. The program being used was designed only to work on disk files. User action: Use a disk file for the file on which the program failed.
• NOBINTRAN Symbolic Name :NO_TRANSLATION_WITH_ BINARY
  [VIC2-NOBINTRAN] binary labels not allowed with dataformat conversions
  Explanation: binary labels may not be accessed (via'COND',' BINARY ') when data format translation is needed. User action: make sure you specified the correct file. Programmer action: Don't use 'COND',' BINARY' unless you are reading from the file in its “natural” format. If extract the labels ( binary header or binary prefix), open it once with binary access, get the labels, then close it and re-open it with a different U_FORMAT.
• NOEFLG Symbolic Name :UNABLE_TO_ACQUIRE_AN_EVENT_FLAG
  [VIC2-NOEFLG] Unable to get EF; re-try or consultsystem programmer
  Explanation: Unable to acquire an event flag. VICAR2 I/O needs event flags to control the different file units. This error generally means that the system provided event flags are all being used.
  User action: this is probably a program error, caused by having too many files open at once or by using event flags for some other purpose. Consult the cognizant programmer.
• NOFREUN Symbolic Name : NO_FREE_UNITS
  [VIC2-NOFREUN] No free units available
  No free units. Explanation: The maximum number of units has been reached. This error generally means that too many files are opened at once. User action: Consult the cognizant programmer for the progra m in which the error occurred and determine whether or not it is a programe rror. If not, consult the system programmer.
• NOKEY Symbolic Name : NO_SUCH_KEY
  [VIC2-NOKEY]No such key in the indicated task
  Explanation: The indicated routine is unable to find the specified key in the label. This can be either a user or programmer error. User action: If the key is user specified, check the label to verify that the label item exists. If, after checking, the pr oblem is not obvious, consult the cognizant programmer.
• NOLAB Symbolic Name : FILE_HAS_NO_LABEL
  [VIC2-NOLAB] File has no label; check file contents
  Explanation: input file does not contain a valid VICAR2 label. User action: Check file to verify that a label does exists. LABEL-CREATE may be used to create a label.
• NOLBL Symbolic Name : NO_SYSTEM_LABEL
  [VIC2-NOLBL] No system label; check file contents
  Explanation: Unlabeled file. User action: Use the program LABEL to create a label for the file.
• NOMEM Symbolic Name :NO_MEMORY_FOR_LABEL_PROCESS
  [VIC2-NOMEM] No memory for label process; consult system programmer
  Explanation: Memory required for label processing is dynamically allocated. There is insufficient memory for operation. User action: this is a system error which probably indicates a memory quot a was exceeded. See the system manager or system programmer to determine the exact cause and perhaps increase the amount of memory available.
• NONASC Symbolic Name :STRING_HAS_NON_ASCII_CHARS
  [VIC2-NONASC] String has non-ASCII characters
  Explanation: A string was passed to the indicated routine which contained characters which are not valid ASCII characters. This generally indicates a program error. User action: The contents of the string should be checked. Please consult the cognizant programmer. Programmer action: Use the debugger or a print statement to determine what the indicated string contains.
• NONSEQWRITSymbolic Name :NON_SEQUENTIAL_WRITE
  [VIC2-NONSEQWRIT] A non-sequential write was attempted on a sequential—only device
  Explanation: Some devices, such as tapes, only allow sequential access on writes. The program attempted to either back up and re-write a recordor write only part of a record to a file on a sequential device. User action: If the program requires a file, use a disk or memory file. If the problem is not obvious consult the cognizant programmer.
• NOSCHTSK Symbolic Name : NO_SUCH_TASK
  [VIC2-NOSCHTSK] No such task in label
  Explanation: The requested task was not in the history label of the image file. This could be either a program or user error. User action: Use “LABEL-LIST 'TASK” on the image file to determine the tasks contained in the label. If a task name is being given on the command line, check the detailed help for the program being used to verify that the correct syntax is being used. If the problem is still not evident, consult the cognizant programmer.
• NOSCHUN Symbolic Name : NO_SUCH_UNIT
  [VIC2-NOSCHUN] No such unit; probable error in unit number
  Explanation: An action was requested on a nonexistent unit. This error generally indicates that the program failed tocall x/zvunit before using a unit number, or that the variable which contains the unit number has been inadvertantly written over. User action: Verify that the unit number being used is valid. If this is not the problem then consult the cognizant programmer.
• NOT ASK Symbolic Name : NO_TASKS_IN_LABEL
  [VIC2-NOT ASK] No tasks in label;check file contents or create new label
  Explanation:The history label of the indicated file does not contain any history subsets, denoted bythe TASK key word. This situation is usually caused by the user deleting the history label. User action: Use the program LABEL or the DCL DUMP facility to examine the label of the image file in question. If the label contains any TASK key words, there is probably an executive bug, so consult the system programmer. If not, and a history label is desired, use LABEL-REMOVE to remove the system label, and LABEL-CREATE to create a new one.
• NOT AVAIL Symbolic Name : NOT_IMPLEMENTED
  [VIC2-NOT AVAIL] Function is not yet implemented; Program error.
  Explanation: The indicated routine was called with an optional argument which although listed in the programmer's reference manual has not yet been implemented. User Action: this indicates a program error, so consult the cognizant programmer or inform MIPL of the bug. Programmer Action: Find another way to accomplish the same function if possible. If the function is not indicated as being unimplemented in the VICAR RTL programmer reference manual, inform MIPL of the problem.
• NOTERM Symbolic Name : NO_IO_TO_TERMINAL
  [VIC2-NOTERM] Terminal not allowed for file name, use another name
  Explanation: Terminal not allowed for I/O operation. The file name given to a program points to the user's terminal (for example the logical name TT). Data can not be written to the terminal. User action: Use another file name.
• NOTEXTEND Symbolic Name :CANNOT_EXTEND_ARRAY_FILE
  [VIC2-NOTEXTEND] Cannot extend array file, consult cognizant programmer
  Explanation: An attempt was made by the executive to extend an array file. Array files currently may not be extended. User action: this is an executive error and the system programmer should be consulted.
• NOTEXTMEM Symbolic Name :CANNOT_EXTEND_MEMORY_FILE
  [VIC2-NOTEXTMEM] Cannot extend memory file, consult cognizant programmer
  Explanation: An attempt was made by the executive to extend a memory file. Memory files currently may not be extended. User action: this is an executive error and the system programmer should be consulted.
• NOTMOUNTED Symbolic Name : DEVICE_NOT_MOUNTED
  [VIC2-NOTMOUNTED] A file open was attempted on a tape device that is not mounted
  Explanation: Magnetic tape devices must be mounted prior to use with the MOUNT command.
  User action: Mount the tape with the MOUNT command, and try opening the file again.
• NOTMULT Symbolic Name : BUF_NOT_MULT_OF_REC
  [VIC2-NOTMULT] Tape blocksize is not an integral number of records
  Explanation: For a tape which is being blocked, the block size for the tape (usually given by BLOCKINGin the mount command) is not an integral number of records. This case is not allowed because it makes reading the tape difficult and puts da ta in a non-standard format. Asecond possibility is that the record size is greater than 65,534 bytes. If this is thecase, default the block size on the mount, and not use the NOBLOCK option in the x/zvopen call, or you will get this error. User action: Verify that block size you gave on the MOUNT command is a multiple number of records. The record size for a band-sequential (BSQ) or band-interleaved by line (BIL) image is NS *(bytes per pixel), and for a band interleaved by pixel (BIP) image is NB * (bytes per pixel). If your record size is greater than 65,534 bytes, then do not specify the blocksize on the MOUNT command, and do not use the NOBLOCK option from x/zvopen.
• NOTOPN Symbolic Name : FILE_NOT_OPEN
  [VIC2-NOTOPN] File not open; program error
  Explanation: The indicated routine triedto operate on an unopened file. User action: this indicates a program error. See the cognizant programmer. Programmer action: make sure that x/zvopen is called prior to the indicated operation. If so, make sure that the program checks the status of the open. The status checking can be achieved automatically with the OPEN_ACT option in x/zvopen.
• NOTPARMFILE Symbolic Name : NOT_PARAMETER_FILE
  [VIC2-NOTPARMFILE] File specified in PARMS is not a parameter file
  Explanation: The file given with PARMS must be a parameter file created by another program with x/zvpopen , x/zvpout, etc. and not an image file.
  User action: Check that the filename you gave is correct. If it is, then consult the cognizant programmer for the program that created the file. Programmer action: Parameter files must be created using x/zvpopen, x/zvpout, and x/zvpclose . Normal image files cannot be used as parameter files.
• NULLREQ Symbolic Name : NULL_REQUEST
  [VIC2-NULLREQ] Null request; program error
  Explanation: The NHIST argument passed to the routine x/zlhinfo is either zero or negative. No information is being requested. User action: The value of the argument passed to the indicated routine must be checked. Please consult the cognizant programmer. Programmer action: Check the argument NHIST being passed to the routine x/zlhinfo.
• ODDOPT Symbolic Name : ODD_NUMBER_OF_ OPTIONALS
  [VIC2-ODDOPT] Unpaired optionals; program error
  Explanation: the number of optional arguments to the indicated routine is odd. Since the optional arguments are given in pairsas KEY WORD, VALUE, an odd number is not allowed. User action: Please consult the cognizant programmer to check that the calling sequence is valid. Programmer action: Check the indicated routine call and verify that the calling sequence is legitimate.
• OPNINP Symbolic Name :UNABLE_TO_OPEN_PRIMARY_ INPUT
  [VIC2-OPNINP] Unable to open primary input; check filespecification
  Explanation: In the course of opening a file other that the primary input, an attempt was made to open the primary input to get label/control information which failed. User action: Check the file specification of the primary input. Also, if it is on tape, make sure that it is not on the same tape as the output file which is being processed.
• ORGMSMTCH Symbolic Name : ORG_MISMATCH
  [VIC2-ORGMSMTCH] File organization is not that required by this program
  Explanation: The program being used requires a specific file organization (BSQ, BIL, or BIP), and the image file in question is not in that organization. User Action: Check the documentation of the program in question to find out what organization the file should be in, and convert the file to the proper organization.
• OUTLBL Symbolic Name :UNABLE_TO_CREATE_OUTPUT_LABEL
  [VIC2-OUTLBL] Unable to create output label; consult system programmer
  Explanation: An error occurred while trying to create the system label for the output file indicated. User action: Consult the system programmer.
• PARBLKERR Symbolic Name : PARBLK_ERROR
  [VIC2-PARBLKERR] Internal error in GET_PARM
  Explanation: An invalid type was found in a variable in the parblk passed from TAE.
  User action: Notify the VICAR system programmer.
  Programmer action: The VARIABLE structure for the parameter requested in a call to GET_PARM had an invalid type. It was not V_INTEGER, V_REAL, or V_STRING. Check the parblk passed from TAE for vailidity.
• PARNOTFND Symbolic Name : PARAM_NOT_FOUND
  [VIC2-PARNOTFND] A program parameter was not found in the PDF
  Explanation: A call to x/zvparm or a related routine requested a parameter that is not in the PDF.
  User action: this is a program error. Consult the cognizant programmer. Programmer action: A parameter in an x/zvparm call (or another parameter routine such as x/zvp) was not found in the par block passed to the program from TAE. Check both the x/zvparm call and the PDF to make sure the parameter exists in both places and that the spellings match.
• QUALNOTFND Symbolic Name : QUAL_NOT_FOUND
  [VIC2-QUALNOTFND] A parameter qualifier was not found in the PDF
  Explanation: A call to x/zvparm or a related routine requested a parameter qualifier that is not in the PDF. User action: this is a program error. Consult the cognizant programmer.
  Programmer action: A parameter qualifier in an x/zvparm call (or another parameter routine such as x/zvp) was not found in the par blockpassed to the program from TAE. Check both the x/zvparm call and the PDF to make sure the qualifier exists in both places and that the spellings match.
• RECPARFAIL Symbolic Name : x/zvrecpar_FAIL
  [VIC2-RECPARFAIL] x/zvrecpar could not retrieve thepar block from TAE
  Explanation: x/zvrecpar was unable to get thepar block from TAE that contains the RECVAR parameters. User action: this is most likely a program error. Make sure your inputs to the program were correct, then notify the cognizant programmer. Programmer action: Check that you executed a RECVAR statement before calling x/zvrecpar. If you did, it is most likely a communication problem between TAE and the application. Check your quotas (especially BYTLIM) and if they are ok, then consult the VICAR system programmer.
• SECDEL Symbolic Name : CANNOT_DELETE_SECTION
  [VIC2-SECDEL] Unable to free array file, consult system programmer
  Explanation: The area of memory allocated for an array file, called a mapped Section, cannot be deleted. User action: this is an executive error. Consult the cognizant programmer for the VICAR executive.
• SIZREQ Symbolic Name : IMAGE_SIZE_REQUIRED
  [VIC2-SIZREQ] Image size required ; re-enter command
  Explanation: x/zvopen was asked to process a file with incomplete information, such as creating an output filewhere no input file is present and no size information was supplied by the user. User action: Use size field to work around the problem, and notify the cognizant programmer of the failure of the program to either calculate the size or require its input.
• STOROPT Symbolic Name :UNABLE_TO_STORE_ OPTIONAL
  [VIC2-STOROPT] Unable to store optional; consult system programmer
  Explanation: An internal error occurred, preventing the storage of an optional argument to the routine indicated. User action: this error probably indicates an internal error. Please consult the system programmer.
• STRTELEM Symbolic Name : BAD_STARTING_ELEMENT
  [VIC2-STRTELEM] Bad starting element; program error
  Explanation: Cannot delete a multi-valued element starting out of range. User action: Check to see if the parameter could have tried to delete a label item. If the problem is still not obvious, consult the cognizant programmer. Programmer action: Verify that the proper values are being passed to the routine x/zldel.
• STRTREC Symbolic Name : START_REC_ERROR
  [VIC2-STRTREC] Bad starting record for read or write operation; program error.
  Explanation: The starting record for a read or write operation, given by the LINE, BAND, or SAMP optional arguments, is only partially specified. This conditi on a rises whenan image file has a third dimension which is greater than one unit in size (for example, a band-sequential image with more than one band), and the starting value in either thesecond or third dimension was defaulted (for example, you have a band-sequential image and you specify BAND but not LINE). The error condition was raised because the record being requested is ambiguous. User Action: this is a program error. Notify the cognizant programmer. Programmer Action: Either completely specify the record in the call to x/zvread or x/zvwrit(for band-sequential images, giveboth LINE and BAND), or completely default it (give neither).
• TAPMETH Symbolic Name : ILLEGAL_TAPE_METHOD
  [VIC2-TAPMETH] Tape cannot be opened for random access.
  Explanation: An attempt has been made to open a tape file for random access. User action: If the program requires a file, use a disk or memory file. If the problem is not obvious consult the cognizant programmer.
• TAPOPR Symbolic Name : ILLEGAL_TAPE_OPERATION
  [VIC2-TAPOPR] Tape cannot be opened for update.
  Explanation: An attempt has been made to open a tape file for update. User action: If the program requires a file, use a disk ormemory file. If the problem is not obvious consult the cognizant programmer.
• TAPPOS Symbolic Name : TAPE_POSITIONING_ERROR
  [VIC2-TAPPOS] Tape positioning error; check drive status
  Explanation: Bad device status. Failed to position tape. User action: Check to see that the tape drive isfunctioning properly.
• TOOLATE Symbolic Name : TOO_LATE
  [VIC2-TOOLATE] Attempt to modify tape label after write; program error
  Explanation: Occurs when label processing to a tape file happens after first tape I/O. User action: Program may require file to be on disk. Write desired file to disk. If the problem is still not obvious consult the cognizant programmer.
• UNDEFOPT Symbolic Name : UNDEFINED_ OPTIONAL
  [VIC2-UNDEFOPT] Undefined optional argument; program error
  Undefined optional. Explanation: An optional argument given to a VICAR2 routine is not recognized as a valid optional argument. User action: this error is usually a program error and the cognizant programmer should be notified. Programmer action: Check the appropriate document to determine what optional parameters are allowed for the subroutine call in question, ornotify the system programmer.
• VARREC Symbolic Name : VARREC_ERROR
  [VIC2-VARREC] COND=VARREC must have NOLABELS, NOBLOCK and tape
  Explanation: If the vARREC option is given to COND, NOLABELS, NOBLOCK, and a tape file must be specified as well. User action: this is a program error. Please consult the cognizant program mer. Programmer action: If VARREC is specified, verify that NOLABELS, NOBLOCK, and a tape file is also specified.
• WAITFL Symbolic Name : IO_WAIT_FAIL
  [VIC2-WAITFL] I/O wait fail; consult system programmer
  Explanation: I/O wait fail. A wait for asynchronous I/O returned a bad status. User action: this is an executive error and the system programmer should be notified.
• x/zvcmderr Symbolic Name : x/zvcommand_ERROR
  [VIC2-XVCMDERR] Internal error in x/zvcommand
  Explanation: An internal error occurred in x/zvcommand having to do withmessage-passing to the TAE host. Either the PARBLK could not be built, or it could not besent or received. User action: Notify the VICAR system programmer.
• x/zvcmdfail SymbolicName : x/zvcommand_FAIL
  [VIC2-XVCMDFAIL] The command submitted via x/zvcommand had an error
  Explanation: The command submitted with a call to x/zvcommand returned an error status.
  User action: this is most likely a program error. Make sure your inputs to the program were correct, then notify the cognizant programmer. Programmer action:
  Check the command submitted with x/zvcommand . Only intrinsic commands and procedures using intrinsic commands may be used with x/zvcommand, i.e. no processes or DCL commands. The failure may be a syntax error, an error in the parameters, or an execution error. The commandshould have printed an error message; use this to find the problem.