VI0001 -  A write error occurred while VPLX was performing an
          unformatted write to the primary OUT= output file.
         
          VPLX will attempt to delete the file.

          The FORTRAN implementation gave an error return from a WRITE
          statement.  Specific diagnostic information may be provided
          by a system error message but is not available to VPLX.

          Possible explanations include:

          1) The error may have occurred if the target device for the
          file became full.  Once the file is deleted, however, the
          device may no longer be full, so some of the evidence for
          overflow may be consequently destroyed.  If the program is
          rerun, try to monitor the size of free space on the device and
          see if the free space disappears just before VPLX terminates.
         
          2) There may be a system protection on the file denying
          write access.
         
          3) Less likely, hardware failure.

          (Technical: called from subroutine FWSTOP.)

VI0002 -  A write error occurred while VPLX was performing an
          unformatted write to an output file.
         
          VPLX will attempt to delete both this file and the primary
          output file.
         
          The FORTRAN implementation gave an error return from a WRITE
          statement.  Specific diagnostic information may be provided
          by a system error message but is not available to VPLX.

          Possible explanations include:

          1) The error may have occurred if the target device for the
          file became full.  Once the file is deleted, however, the
          device may no longer be full, so some of the evidence for
          overflow may be consequently destroyed.  If the program is
          rerun, try to monitor the size of free space on the device.
         
          2) There may be a system protection on the file denying
          write access.
         
          3) Less likely, hardware failure.

          (Technical: called from subroutine FWSTOP.)

VI0003 -  A write error occurred while VPLX was performing a formatted
          write to the primary OUT= output file.
         
          VPLX will attempt to delete the file.

          The FORTRAN implementation gave an error return from a WRITE
          statement.  Specific diagnostic information may be provided
          by a system error message but is not available to VPLX.
          
          Possible explanations include:
         
          1) There may be a syntactic error in the format.  The primary
          output file from REWEIGHT is a character data file governed by
          the OUTFORMAT, so this format should be checked carefully if 
          this error occurred during REWEIGHT.
         
          2) VPLX may be trying to output a number requiring more
          characters than allowed by the format.  In some FORTRAN 
          implementations, an execution error occurs.  During REWEIGHT,
          check OUTFORMAT for the space allotted for each field, 
          remembering that FORTRAN always includes the decimal point
          under Fw.d format.  For example, F1.0 will not generally 
          be adequate to write a number from 0-9 -- at least F2.0 is
          instead required, etc.
        
          3) The error may have occurred if the target device for the
          file became full.  Once the file is deleted, however, the
          device may no longer be full, so some of the evidence for
          overflow may be consequently destroyed.  If the program is
          rerun, try to monitor the size of free space on the device.
         
          4) There may be a system protection on the file denying
          write access.
         
          5) Less likely, hardware failure.

          (Technical: called from subroutine FWSTOP.)

VI0004 -  A write error occurred while VPLX was performing a
          formatted write to an output file.
         
          VPLX will attempt to delete both this file and the primary
          output file.
         
          The FORTRAN implementation gave an error return from a WRITE
          statement.  Specific diagnostic information may be provided
          by a system error message but is not available to VPLX.

          Possible explanations include:

          1) There may be a syntactic error in the format.  Try to
          match the unit associated with the error with the 
          "assigned to" statements in the VPLX listing to discover
          which file produced the error.  Check the format associated
          with this file.
         
          2) VPLX may be trying to output a number requiring more
          characters than allowed by the format.  In some FORTRAN 
          implementations, an execution error occurs.  Check the 
          format for the space allotted for each field, remembering
          that FORTRAN always includes the decimal point under Fw.d
          format.  For example, F1.0 will not generally be adequate
          to write a number from 0-9 -- at least F2.0 is instead 
          required, etc.
        
          3) The error may have occurred if the target device for the
          file became full.  Once the file is deleted, however, the
          device may no longer be full, so some of the evidence for
          overflow may be consequently destroyed.  If the program is
          rerun, try to monitor the size of free space on the device.
         
          4) There may be a system protection on the file denying
          write access.
         
          5) Less likely, hardware failure.

          (Technical: called from subroutine FWSTOP.)

VI0101 -  A read error occurred while VPLX was performing an unformatted
          read of the primary IN= input file.
         
          The error may have occurred if the input file did not conform
          to VPLX's expectations at this point.

          (Technical: called from subroutine FRSTOP.)

VI0102 -  A read error occurred while VPLX was performing an unformatted
          read of an input file.
         
          (Technical: called from subroutine FRSTOP.)
          
VI0105 -  Error reading first record of VPLX input file.

          The file appears not to be a VPLX file, which was expected.

          (Technical: called from PREAMB)

VI0106 -  The VPLX file version number, contained in the first record
          of the file, is not one of the recognized values to this
          version of the program.
          
          A typical value of the version number is 9203, i.e. March,
          1992.  Later versions of the file may appear.

          (Technical: called from PREAMB)

VI0107 -  The information for crossed variables is not internally
          consistent, indicating that the incoming VPLX file may be
          damaged, or the previous step of VPLX that created the file
          may have made an error.

          (Technical: called from PREAMB)


VI0108 -  The information for labels for levels is not internally
          consistent, indicating that the incoming VPLX file may be
          damaged, or the previous step of VPLX that created the file
          may have made an error.

          (Technical: called from PREAMB)

VI0200 -  Unable to assign file to a FORTRAN unit number.

          VPLX uses FORTRAN unit numbers 10-17 for specific uses.  It
          attempts to use 8-9, and 18-39 for all other file assignments.
          Too many files are open at once for this strategy.
          
          (Technical: called from IUFIND.)

VI0201 -  File format or positioning error, TRANSFORM step scratch file

          During the execution of the TRANSFORM step, subroutines may
          write information to a file for the full sample and reread the
          information for each replicate.  An error has occurred
          positioning the file.
          
          This error is unusual and would indicate an internal error in
          VPLX.

          (Technical: called from SCPOSN.)

VI0202 -  File is already assigned to another unit.

          A file cannot be opened for more than one purpose at the
          same time.  Check the reported unit number by looking back
          to messages "Assigned to unit" in the listing before this 
          point.
          
          (Technical: called from OPENCH.)
          
VP0001 -  a "*" in a class specification must be used only after the
          name of a class

         (Technical: called from subroutine CLSCAN)

VP0002 -  a "(" in a class specification must be used only after the
          name of a class
         
         (Technical: called from subroutine CLSCAN)

VP0003 -  an expression enclosed in apostrophies "(" ")" was expected to
          include one or more ranges to specify levels of a class
          variable, but no valid ranges were found.
         
          (Technical: called from subroutine CLSCAN)       

VP0004 -  MISSING is not allowed in a level specification for a class
          variable.
         
          (Technical: called from subroutine CLSCAN)

VP0005 -  The specification for the level of the class variable
          referenced a level outside the scope of the class variable,
          such as a negative level, (e.g., AGE(-1)), or an upper end of
          the range  that is too high, (e.g., AGE (0-5), when AGE has
          only 4 levels)  
         
          (Technical: called from subroutine CLSCAN)

VP0006 -  VPLX ran out of space in an internal array attempting to store
          a class specification.
         
          Solution: break the problem down into smaller parts for
          separate processing.
         
          (Technical: called from subroutine CLSCAN, overflow in array
          IA)
         
VP0007 -  An error occurred while attempting to read the name of a class 
          variable.
         
          (Technical: CLSCAN called VNFIND to read the names of one or
          more classes, but VNFIND returned an error condition to
          CLSCAN.)
         
VP0008 -  TOTAL may not be used in a product with other class variables,
          e.g., AGE * TOTAL.
          
          (Technical: called from subroutine CLSCAN)

VP0009 -  Class variable expected here.  The named variable is not a
          class variable.
          
          (Technical: called from subroutine CLSCAN)
          
VP0010 -  A class variable is in a product with itself, e.g. AGE * AGE.
          This form of product is not allowed.
          
          (Technical: called from subroutine CLSCAN)
          
VP0011 -  Unidentified variable name.  Variable names must be spelled
          exactly to be recognized (although in any mixture of upper and 
          lower case).  The variable in question was expected to be the
          name of a class variable.
          
          (Technical: called from subroutine CLSCAN)
          
VP0030 -  More constants were specified than the available space.

          Solution: check the syntax of the statement.  More constants
          may be implied than intended.
          
          (Technical: called from subroutine DASCAN.  The array in
          question is governed by the parameter MSIZED.)
          
VP0031 -  Value preceding '*' not an appropriate integer for this
          syntax.
          
          Solution: check the use of the * syntax.  The value preceding
          must be a positive integer and is not allowed to exceed 
          1000000.
          
          (Technical: called from subroutine DASCAN.)
          
VP0032 -  Ambiguity caused by repeated use of * in specifying constants

          (Technical: called from subroutine DASCAN.)
          
VP0035 -  Run-on number - apparent constant longer than VPLX syntax
          allows.  VPLX expects constants to be of length 30 or shorter.
          
          (Technical: called from subroutine DFIND)
          
          
VP0036 -  Error on reading apparent number.
          
          (Technical: called from subroutine DFIND)
          
          
VP0037 -  Error creating number to indicate precision of primary number.
          
          (Technical: called from subroutine DFIND.  DFIND creates a
          second number to measure the precision of the primary number.
          A FORTRAN read error occurred while trying to read this 
          number.)
          
VP0040 -  Run-on integer - apparent constant longer than VPLX syntax
          allows.  VPLX expects integer constants to be of length 9 or
          shorter.
          
          (Technical: called from subroutine IFIND)
          
VP0043 -  An expression KEYWRD = has not been followed by any nonblank
          character.  KEYWRD = must be followed by some specification.
          
          (Technical: called from subroutine EQSCAN)
          
VP0045 -  Key word not matched.  Key words may be spelled in upper or 
          lower case.  Check the intended spelling in the documentation.
          
          (Technical: called from subroutine KYFIND)
          
VP0046 -  An ambiguity exists interpreting the key word because it
          appears to be a shortened form of more than one key word
          recognized by VPLX.  Shortened forms must imply a single
          key word.
          
          (Technical: called from subroutine KYFIND)
          
VP0050 -  During the process of scanning for labels, a line ended with
          an odd number of apostrophes.  Apostrophes are required to
          delimit labels.  An individual label may not be continued from 
          one command line to the next, so each command line must have an
          even number of apostrophes.
          
          To include an apostrophe within a label, place two apostrophes
          next to each other.  For example, the command line
            'Respondent''s age' 
          becomes the label "Respondent's age"
          
          
          (Technical: called from subroutine LEVELR)

VP0055 -  During reading of an option, the expression KEYWRD = has been
          followed by a noninteger.  Only an integer is expected at this
          point.
          
          (Technical: called from OPTNTR)

VP0060 -  A RENAME statement must specify a minimum of one existing
          variable name, "AS" or "INTO", and one new variable name.
          
          (Technical: called from RENAME)
          
VP0061 -  "AS" or "INTO" missing in an appropriate place to complete the
          renaming of variables.
          
          (Technical: called from RENAME)
          
VP0062 -  Placement of "AS" or "INTO" too far near the end to establish
          appropriate balancing of lists.
          
          Solution: RENAME expects lists of equal length to appear
          before and after each occurrence of "AS" or "INTO".  Check
          the statement for this condition.  If necessary for clarity,
          adopt one of the two strategies:
          1) restructure the statement into one list of old variable
          names, a single 'AS' or 'INTO', and a list of equal length 
          of new names, or
          2) rename one at a time, i.e., 
                  oldname1 AS newname1
                  oldname2 AS newname2
          etc.
          
          (Technical: called from RENAME)
          
VP0063 -  At this point, the new name is already in use as the name
          of an existing variable.  The potential ambiguity is not
          allowed.
          
          Solution: If the conflict was unintended, simply use a new
          name.  If the conflict resulted from trying to interchange
          names, break the list into smaller groups, each connected by
          'AS' or 'INTO' (even a one variable at a time strategy), and
          rename variables in such a way that a name does not have two
          uses simultaneously.
          
          (Technical: called from RENAME)
          
VP0065 -  Level array exceeded.  The level array was being used as 
          a scratch array during the reading of variable labels, but
          the number of specified variables exceeded this maximum.
          
          Solution:  Breaking the statement up into single assignments
              var1 'Label 1'
              var2 'Label 2'
          etc., is likely to help, since this approach uses only one 
          element of the scratch array.
          
          (Technical: called from RLABEL.  The limit is governed by the
          parameter MLEVEL in the FORTRAN source.)
          
VP0070 -  Level array exceeded.  The level array overflowed in
          attempting to store the levels.
          
          (Technical: called from RLEVEL.  The limit is governed by the
          parameter MLEVEL in the FORTRAN source.)
          
VP0075 -  A concluding ")" was not encountered to mark the end of range
          specifications.  Either the ")" needs to be added, or there 
          are other errors in specifying the ranges.
          
          (Technical: called from RNSCAN)

VP0076 -  A minus sign "-" was iterpreted to be part of a number, but a
          negative number was not successfully read at this point.
          
          (Technical: called from RNSCAN)

VP0077 -  A string within a range had none of the expected forms.  It 
          was not a valid number, one of the possible delimitors "," 
          etc., nor one of the accepted special words possible at this
          point: LOW, MISSING, RES

          (Technical: called from RNSCAN)

VP0078 -  HIGH and N may be used as the upper end of a range but not at
          this point.

          (Technical: called from RNSCAN)

VP0079 -  A string within a range had none of the expected forms.  It 
          was not a valid number, one of the possible delimitors "," 
          etc., nor one of the accepted special words possible at this
          point: HIGH, N

          (Technical: called from RNSCAN)

VP0080 -  MISSING, LOW, RES may be used as the lower end of a range but
          not at this point.

          (Technical: called from RNSCAN)

VP0081 -  Negative number here is incompatible with previous use of
          blank as a delimitor.
          
          Solution: Use commas to provide a clear delination of ranges.
          
          (Technical: called from RNSCAN)

VP0082 -  Use of blank as a delimitor here is incompatible with previous 
          appearance of a negative number 
          
          Solution: Use commas to provide a clear delination of ranges.
          
          (Technical: called from RNSCAN)

VP0083 -  Unexpected characters here.  Either the error occurred because
          the character string is an unexpected part of a range or
          because a string such as LOW, HIGH, etc. occurs in the wrong
          place.
          
          Solution: Check the syntax.  Possibly, commas may be required
          to provide a clear delination of ranges.
          
          (Technical: called from RNSCAN)

VP0084 -  Range array exceeded.

          Solution:  The number of ranges in use in the step is too 
          great.  If possible, break the step into pieces.
          
          (Technical: called from RNSCAN.  The limit is governed by the
          parameter MRANGE in the FORTRAN source.)
          
VP0085 -  LOW cannot be used alone to specify a range.  Instead, the form
          must be LOW - value, where value can be a number, HIGH, or N.
          
          (Technical: called from RNSCAN.)
          
VP0100 -  The specification of a file name has become intermixed with
          a continuation line of a substitution based on a SET
          statement.
          
          Solution: break up the complex substitution.  Equate one string
          to the file name and optional characteristics only, without
          including additional information.

          (Technical: called from REFRSH)          

VP0101 -  Substitutions from SET have expanded a single input line of
          80 or fewer characters beyond 240 characters, the maximum 
          buffer for the results of substitutions.
          
          Solution: break up the line to simplify the substitutions.
          If necessary, place each use of &stringname& on separate
          lines.

          (Technical: called from REFRSH)          

VP0102 -  Substition implied by &stringname& not matched to any
          stored name.
          
          Solution: Check the spelling of the stringname.  If it is
          spelled correctly, use a SET statement before this line to
          assign a value to stringname.

          (Technical: called from REFRSH)          

VP0103 -  Substition implied by &stringname& cannot be matched since
          no SET statements have yet appeared.
          
          Solution: Use a SET statement before this line to assign a
          value to stringname.

          (Technical: called from REFRSH)          

VP0104 -  The file named by the INCLUDE statement could not be opened.

          Solution: Check the spelling of the file name.  If the file
          exists, check that VPLX run has read access to the file, since
          the error could occur if the system blocks reading of the file.

          (Technical: called from REFRSH)          

VP0105 -  The maximum depth of INCLUDE files has been exceeded.

          The initial input file contained an INCLUDE pointing to
          a first alternate file, which contained an INCLUDE pointing
          to a second alternate file, which contained an INCLUDE
          pointing to a third alternate file, which is the maximum 
          allowed depth.  This INCLUDE statement exceeded the limit.
          
          Solution: simply the INCLUDE structure by one level.

          (Technical: called from REFRSH)          

VP0106 -  The file could not be opened for use as a scratch file.

          An error occurred in trying to open the file for writing.
          The file name may be inappropriate for the host system or
          point to a disk or file system that the user does not have
          the ability to write to.  A new name must be provided.

          (Technical: called from REFRSH)          

VP0107 -  The file could not be opened for use by MACROWRITE.

          An error occurred in trying to open the file for writing.
          The file name may be inappropriate for the host system or
          point to a disk or file system that the user does not have
          the ability to write to.  A new name must be provided.

          (Technical: called from REFRSH)          

VP0108 -  Maximum number of substitution strings exceeded.
   
          Solution: simplify the number of set statements in the
          application. 

          (Technical: called from REFRSH.  Storage has exceeded the
          allowance governed by MAXSUB.)          

VP0109 -  Maximum number of lines allotted for substitution strings
          exceeded.
   
          Solution: simplify the number of set statements in the
          application. 

          (Technical: called from REFRSH.  Storage has exceeded the
          allowance governed by MAXSBL.)          

VP0110 -  Maximum number of characters alloted for substitution
          strings exceeded.
   
          Solution: simplify the number of set statements in the
          application. 

          (Technical: called from REFRSH.  Storage has exceeded the
          allowance governed by MAXSBC.)          

VP0111 -  Name of a substitution string must begin with an underscore
          or letter.
          
          (Technical: called from REFRSH)

VP0112 -  Name of a substitution string must not exceed 12 characters.
          
          (Technical: called from REFRSH)

VP0140 -  Variable name is too long.  A variable name must be limited to
          12 characters.
          
          (Technical: called from VNFIND.)
          
VP0141 -  A minus/dash is not expected here.  Variable names are
          expected at this point. "-" or "--" may be used to denote
          ranges of variables, but must occur between two names.

          (Technical: called from VNFIND.)
          
VP0142 -  Overflow in variable name array.
          
          Too many variable names are now in use.  Attempt to simplify
          the application to reduce the number of variables.

          (Technical: called from VNFIND.  Controlled by parameter
          MVAR.)
          
VP0143 -  In specifying a range of the form VARA -- VARB, both VARA 
          and VARB must be previously defined.
          
          Solution: check the spelling of the variable names.  It may
          be necessary to name the variables in another way.
          
          (Technical: called from VNFIND.)
          
VP0144 -  A range of the form VARA -- VARB is not expected here, since
          both VARA and VARB must be previously defined to use this
          syntax, and new or primarily new variables are expected at
          this point.
          
          Solution: Explicitly list all variables or use a single "-"
          to indicate ranges of variables ending in digits.

          (Technical: called from VNFIND.)

VP0145 -  A range of the form VARn1 - VARn2, where n1 and n2 are both
          numbers, requires that they share the same stem.

          (Technical: called from VNFIND.)
          

VP0146 -  For a range of the form VARn1 - VARn2, difficulty determining
          n1 or n2.

          Both VARn1 and VARn2 must end with digits indicating a number
          in each case.

          (Technical: called from VNFIND.)
          
VP0147 -  For a range of the form VARn1 - VARn2, n1 > n2 not allowed.

          (Technical: called from VNFIND.)
          
VP0170 -  The number of variables being scanned exceeds the work array.

          Solution: simplify problem by breaking it into segments.
          
          (Technical: called from VTSCAN.  VPLX reports the size of a
          temporary array.  This size of this array is governed by the 
          FORTRAN parameter MVAR.)
          
VP0200 -  Overflow in the double precision array.  This array is used
          for most calculations, and the usage of this array is reported
          at the end of VPLX runs.  The size of the array is set by the
          FORTRAN parameter MSIZED.
          
          Solution: either reduce the size of the problem or increase
          the parameter and recompile VPLX.
          
          Consider whether the specification of the problem may have
          required much more storage than necessary.  As an example,
          use of several variables and several class statements in the
          CREATE step, if not accompanied by one or more block
          statements, asks VPLX to cross-classify all analytic variables
          by all class variables.
          
          (Technical: called from ROOMD.)

VP0201 -  Overflow in the general integer array.  This array has varying
          size depending on the step, but is governed by the value of
          the FORTRAN parameter MSIZEI.
          
          Solution: either reduce the size of the problem or increase
          the parameter and recompile VPLX.
          
          (Technical: called from RCHECK.)

VP0202 -  Maximum number of variables exceeded.  There is an attempt to
          define more variables than permitted by the FORTRAN parameter
          MVAR.
          
          Solution: either reduce the size of the problem or increase
          the parameter and recompile VPLX.
          
          (Technical: called from RCHECK.)

VP0203 -  Maximum number of variance identifies and by variables
          exceeded.  Variables defining the replication, such as
          CLUSTER and STRATUM, and by variables affect the size of
          a number of internal arrays.  The specification of the problem
          now uses more of these variables than permitted by the FORTRAN
          parameter MAXIDS.
          
          Solution: either reduce the size of the problem or increase
          the parameter and recompile VPLX.
          
          (Technical: called from RCHECK.)

VP0204 -  Recode arrays exceeded.  The arrays are governed by the FORTRAN
          parameter MRECOD.

          During CREATE and related steps, recode arrays hold
          information related to each executable statement, INPUT, ADD
          IF, etc.  The number of such operations now exceeds the
          allotted space.
          
          During TRANSFORM, recode arrays hold information on each
          variable passed to subroutines.
          
          Solution: either reduce the size of the problem or increase
          the parameter and recompile VPLX.
          
          (Technical: called from RCHECK.)

VP0205 -  Maximum number of ranges exceeded.  There is an attempt to
          employ more ranges than permitted by the FORTRAN parameter
          MRANGE.
          
          As an example, the statement
          
            cat quest1 (1/2-3/4,5-9/10/res)
          
          results in 6 ranges: 1; 2-3; 4; 5-9; 10; res
          
          Solution: either reduce the size of the problem or increase
          the parameter and recompile VPLX.  Look for syntax that
          might reduce the number of ranges in use.  For example,
          
            cat quest1 - quest100 (1/2) 'Yes' 'No'
          
          recodes 100 variables while only requiring the storage of 
          2 ranges
          
          (Technical: called from RCHECK.)

VP0206 -  Maximum number of sets of ranges exceeded.  There is an 
          attempt to employ more sets of ranges than permitted by the
          FORTRAN parameter MRNSET.
          
          As an example, the statement
          
            cat quest1 (1/2-3/4,5-9/10/res)
          
          results in 6 ranges: 1; 2-3; 4; 5-9; 10; res; but represents
          a single set of ranges.
          
          Solution: either reduce the size of the problem or increase
          the parameter and recompile VPLX.  Look for syntax that
          might reduce the number of sets of ranges in use.  For
          example,
          
            cat quest1 - quest100 (1/2) 'Yes' 'No'
          
          recodes 100 variables while only requiring the storage of 
          1 set of ranges
          
          (Technical: called from RCHECK.)

VP0207 -  Maximum number of levels exceeded.  Each level of a class
          or categorical variable has an associated level.  The
          total number of such levels is governed by the FORTRAN
          parameter MRNSET.
          
          Solution: either reduce the size of the problem or increase
          the parameter and recompile VPLX.
          
          (Technical: called from RCHECK.)

VP0208 -  Maximum number of blocks exceeded.  The total number of 
          allowed blocks is governed by the FORTRAN parameter MCLBLK.
          
          Solution: either reduce the size of the problem or increase
          the parameter and recompile VPLX.  
          
          (Technical: called from RCHECK.)

VP0209 -  Maximum number of class specifications for blocks exceeded.
          Arrays hold information for each class variable associated
          with each block.  The dimension of these arrays is governed
          by the FORTRAN parameter MCLBAR.
          
          Solution: either reduce the size of the problem or increase
          the parameter and recompile VPLX.  
          
          (Technical: called from RCHECK.)


VP0210 -  An integer array to hold information for crossed variables
          (crossed real, crossed categorical, and crossed derived) is
          full.  The dimension of this array is governed by the FORTRAN
          parameter MCRSSD.
          
          Solution: either reduce the size of the problem or increase
          the parameter and recompile VPLX.  Consider alternatives to
          crossed variables, such as the use of blocking and class 
          variables.  
          
          (Technical: called from RCHECK.)

VP0211 -  Maximum storage for formats and other long strings exceeded.
          The total number of strings, each of 128 characters, is
          governed by the FORTRAN parameter MAXFMT.
          
          Solution: Formats can be shortened by use of multipliers -
          for example, f3.0,f3.0,f3.0, can be shortened to 3f3.0, etc.
            
          (Technical: called from RCHECK.)
          
VP0212 -  Maximum number of TRANSFORM step subroutines exceeded.  The
          total number of subroutines is governed by the FORTRAN
          parameter MTRANS.
          
          Solution: Long TRANSFORM steps can be broken into separate
          TRANSFORM steps, with the output of one shortened step 
          fed directly into the next.  
          
          (Technical: called from RCHECK.  Simply increasing MTRANS,
           however, may have other consequences, since the space to
           handle subroutines comes out of the general integer array
           governed by MSIZEI.  The relationship among parameters is
           described in TSET1.)

VP0213 -  Maximum storage for temporary names exceeded.  During
          parsing of control statements, remaining space not assigned
          to defined variables made available.  Indirectly, this space
          is governed by the FORTRAN parameter MVAR.
          
          Solution: The temporary space may be inadequate because the
          number of defined variables at this point may be close to
          the allowed maximum MVAR.
            
          (Technical: called from RCHECK.)

VP0300 -  A file name is expected here, but no characters remain on 
          this record.
          
          (Technical: called from FNFIND.)                 

VP0301 -  During the reading of a file name, an unexpected apostrophe
          has been encountered.
          
          (Technical: called from FNFIND.)

VP0302 -  During the reading of a file name, the file name has exceeded
          80 characters, the maximum allowed.

          Solution: consider the use of default directories or other
          devices to shorten the spelling of the file name.
                    
          (Technical: called from FNFIND.)

VP0303 -  An unexpected "(" appears here while trying to read a file
          name.
          
          When not enclosed in parenthesis, a "(" may be used to set 
          off optional file parameters, after the name of the file has
          been given.  VPLX expected a file name here instead of "(".
          
          (Technical: called from FNRD2.)             
          
VP0304 -  An unexpected ")" appears here while reading a file name.
          
          When not enclosed in parenthesis, a ")" may be used to set 
          off optional file parameters, after the name of the file has
          been given and followed by a "(".  The appearance here of ")"
          is unexpected.
          
          (Technical: called from FNRD2.)            
          
VP0305 -  Unclear whether named file is input or output.

          Solution: use IN = or OUT = syntax.
          
          (Technical: called from FNRD2.)            
          
VP0306 -  Unsuccesful attempt to find file name.

          Solution: A file name is expected here.  Check spelling and 
          syntax.
          
          (Technical: called from FNRD2.)
          
VP0307 -  During attempt to read a file name, the construction KEYWORD =
          was encountered, but KEYWORD was not IN, OUT, or VPLXIN as
          expected.
          
          (Technical: called from FNRD2.)

VP0308 -  During attempt to read optional parameters associated with a
          file, the required construction KEYWORD = value was not
          followed as expected.
          
          (Technical: called from FNRD2.)
          
VP0309 -  During attempt to read optional parameters associated with a
          file, the key word in a KEYWORD = value construction was not
          one of the expected forms.
          
          Solution: Check spelling of the key word.  As of version
          95.07, the expected forms are UNIT, VOL, VOLSER, RECL, LRECL,
          TRK, MAXREC, SECOND and BLKSIZE.
          
          (Technical: called from FNRD2.)
          
VP0310 -  During attempt to read optional parameters associated with a
          file, the required construction KEYWORD = VALUE had a longer
          than anticipated length.
          
          (Technical: called from FNRD2.)

VP0311 -  During attempt to read optional parameters associated with a
          file, the required construction KEYWORD = VALUE required VALUE
          to be an integer.
          
          (Technical: called from FNRD2.)
          
VP0312 -  During attempt to read optional parameters associated with a
          file, the required construction KEYWORD = VALUE, value was
          outside the expected range.
          
          (Technical: called from FNRD2.)

VP0313 -  More than one input file has been defined, where only one is
          expected. (Excluding a VPLXIN = file, if any.)
          
          (Technical: called from FNRD2.)          

VP0314 -  More than one output file has been defined, where only one is
          expected.
          
          (Technical: called from FNRD2.)          

VP0315 -  More than one VPLXIN= file has been defined, where only one is
          expected.
          
          (Technical: called from FNRD2.)          

VP0316 -  The IN= file does not exist.

          According to the host system, the file does not exist.  Check
          the spelling of the file name, the use of directories.  This 
          message may occur if the file exists but the run does not
          have read access to the file because of file protections.
          
          (Technical: called from FNRD2.)          

VP0317 -  The VPLXIN= file does not exist.

          According to the host system, the file does not exist.  Check
          the spelling of the file name, the use of directories.  This 
          message may occur if the file exists but the run does not
          have read access to the file because of file protections.
          
          (Technical: called from FNRD2.)          

VP0318 -  A VPLXIN= file is required for this step but has not been
          defined.
          
          (Technical: called from FNRD2)

VP0319 -  An IN= file is required for this step but has not been
          defined.
          
          (Technical: called from FNRD2)

VP0320 -  An input file is required for this step but has not been
          defined.
          
          (Technical: called from FNRD2)

VP0321 -  An output file is required for this step but has not been
          defined.
          
          (Technical: called from FNRD2)
