error messages

Error 1 Invalid Report Type Specified
Error 2 Invalid Target Specification
Suggestion: Make sure the target specified is an existing target schedule
Error 3 Invalid Code Element
Suggestion: This error often indicates that the report specification contains activity
codes that do not exist for this project. Verify spelling and justification in the specified
criteria. Create another report specification.
Error 4 Invalid Line Type Specification
Error 5 Activity Line Not Specified
Error 6 Invalid Record Type for Reporting
Suggestion: Before processing a batch file, make sure you save all the necessary
blank spaces. Check the spelling of record names.
Error 7 Invalid Report Date
Error 8 Invalid Copy and Rename Specifier
Error 9 Invalid MASK Element
Suggestion: Review the report specification. The mask element specified for skip
may not apply to the current project.
Error 10 Invalid File Specified on Report Record
Error 11 Invalid Start Day of Week (Day)
Error 12 Not Used
Error 13 Project Record Data Error
Suggestion: Examine the PROJ record in the batch file. Make sure you allowed all
necessary blank spaces (no tabs allowed), and that all alphabetic characters are
upper case.
Error 14 Invalid Command
Suggestion: Check the command specified on the PROJ record in the batch file.
Error 15 Project Not Found
Suggestion: Check the spelling of the project name. The number "zero" and the letter
"O" are not interchangeable.
Error 16 Invalid Establish Target Specifier
Error 17 Project Has Not Been Scheduled
Error 18 Project in Use, Access Denied
Error 19 Input Record Sequence Error
Suggestion: Check the order of input records in the batch file. If adding a new project,
make sure a PCAL record immediately follows the PROJ record.
Error 20 Calendar Specification Error
Suggestion: Check the dates specified in the PCAL record of the batch file. All dates
must be in DDMMMYY HH:MM format (for example, 01JAN97 06:00). Hours and
minutes are used for hourly projects only.
Error 21 Invalid Project Group Name
Error 22 Project Group Name Already Exists
Suggestion: Change the name of the project group to be added to avoid duplicates.
Error 23 Target Schedule Designation Invalid
Suggestion: Verify the column position of codes on the ESTABLISH TARGET line.
Make sure the target schedule is either 1 or 2.
Error 24 Invalid Execute Command
Suggestion: Check the spelling and spacing of the EXECUTE command in the batch
file.
Error 25 Invalid Report Command
Error 26 Invalid Selection Element
Suggestion: Verify the spelling and justification of the specified criteria on the SELE
line in the file.
Error 27 Invalid Equality Type
Error 28 Invalid Limit Values
Error 29 Invalid Input Record Select File Established
Error 30 Invalid Record Type in Update Run
Error 31 Invalid Activity ID - Data Ignored
Suggestion: Check columns 6-15 of the batch file against the appropriate record
layout. When adding new activities, make sure the PREC, PRED, or SUCC record
follows the ACTV record for the activity referenced in columns 6-15. Or execute the
PREC, PRED, or SUCC record in a separate run after all activities have been added
to the network. The error diagnostic report displays asterisks under the field in error
to indicate the correct format.
Error 32 Activity Not Found in File
Suggestion: Check the activity number. When adding new activities, make sure the
PREC, PRED, or SUCC record for a new activity immediately follows the ACTV
record for that activity. Or execute the PREC, PRED, or SUCC record in a separate
run after all activities have been added to the network.
Error 33 Added Activity Already Exists
Suggestion: Check the activity number.
Error 34 Format Error, Columns Flagged
Suggestion: The field with the incorrect format is specified by asterisks. Make sure
the data do not exceed specified field limits and that numeric fields do not contain
alphabetic data. Also, check your project for any activities that have start-to-start
relationships with finish milestones or finish-to-finish relationships with start
milestones.
Error 35 New Activity Already Exists
Error 38 Illegal Cursor Position (row/column)
Error 39 Invalid Resource
Error 40 Attempt to Delete a Nonexistent Project
Error 46 Invalid Record Type in Loading Library
Suggestion: Make sure columns 1-4 in the batch file indicate a record type that is
correctly associated with the TITLE DATA command. Check the record sequence for
the correct type of specification.
Error 47 Invalid Data
Suggestion: Check the data on the CDEF record of the batch file. Make sure all field
definitions are valid.
Error 48 Invalid Title Data
Suggestion: Check the COTL record of the batch file for consistency.
Error 49 Code Value Not in File
Suggestion: Check the spelling of the code value for which a title is to be deleted.
Error 54 Resource/Cost Account Not Used by This Activity
Error 55 Array Overflow
Error 56 Resource/Cost Account Both Blank
Error 57 Error in ES Targ
Error 59 Summary Must Be Preceded by SORT
Error 60 Missing NLOG Record
Error 61 Invalid Masking Specified
Error 62 Invalid Code Fields Specified
Error 63 No Timescale Specification Record
Suggestion: Specify a timescale in hours/shifts/days/weeks/months when requesting
a timescale report.
Error 64 Invalid Timescale Specified
Suggestion: The report specification contains an invalid timescale. Make sure H, S,
D, W, or M (for hours, shifts, days, weeks, or months) is specified for the timescale,
and check the range of months specified to ensure that the dates do not exceed the
project calendar.
Errors 66 to 75 Unused
Error 76 Invalid Resource Code
Suggestion: Check the spelling of resource code(s) in the batch file. Make sure a
resource code is defined before it is assigned to activities. Verify the code justification
as defined in the Resource Dictionary (RETL record).
Error 77 Invalid Equality Type
Error 78 Invalid Select Element
Suggestion: The selection criteria specified in the resource/cost report specification
are invalid. Check the RSEL line in the run stream for valid data.
Error 80 Invalid Resource - Data Ignored
Suggestion: Make sure you defined resource codes in the batch file before you
execute the UPDATE or INPUT record.
Error 81 Invalid Critical Flag
Errors 82 to 88 Unused
Error 90 Invalid Target File Specified
Suggestion: Review the target specification in the run stream. Make sure Target 1
exists before you produce a resource/cost report with target data.
Error 91 Invalid Report Specification
Error 92 Invalid Cumulative Curve Specification
Error 93 Invalid Profile Curve Specification
Error 94 Invalid Usage Report Specification
Error 95 Invalid Resource Report Run Stream Record
Suggestion: This error usually occurs when selection criteria in the report specification
are invalid. Verify the code justification (R or L) as defined in the Resource
Dictionary (RETL record). Also check the RSEL line in the file for valid selection
criteria.
Error 96 Invalid Resource Report Specified
Errors 98 to 99 Undefined Calendar