Validation Guidance for HASTUS

Table 1. HASTUS Validation
Message	Additional Detail	What to do
The pattern identifier ([99999]) for route [xxxxx] in not defined in the PAT file. Correct the pattern data and reimport the schedule.	The route (line) does not exist in the PAT (pattern) file. The data is imported in its undefined state.	Update the PAT file.	Reimport
Stop [xxxxx] for pattern [xxxxx] is not defined. Correct the stop data for this pattern and reimport the schedule.	The NDE file does not include the stop in the pattern.	Update the NDE file.	Reimport
InterTripId [99999] does not have a VehicleUnitStart. Fix the data and reimport the schedule.	The number of rail cars required is 0. It must be a positive integer. The import continues.	Correct the number of rail cars (VehicleUnitStart).	Reimport
The duty set with CrewSchName:[xxxxx], CrewServiceName:[xxxxx], CrewScenario:[99999], CrewDayType:[99999] does not exist in the CAL file. Add this duty set and reimport the schedule.	The calendar file does not include this duty set.	Add the duty set to the CAL file.	Reimport
This sign-up period already contains activated days before [ddmmyyyy]. The selected schedule will not be imported.	You cannot import into a sign-up period with already activated days.	—	On the Activate Day screen, use the Undo Day Activation feature to undo activation for the activated days within the sign-up period. Reimport.
This sign-up period already contains activated days before [ddmmyyyy]. The schedule before this date will not be imported.	The sign-up period has activated days, but at least one week at the end of the sign-up period has no activated days. The schedule will be imported only for the weeks following the last activated day.	—	On the Activate Day screen, use the Undo Day Activation feature to undo activation for the activated days within the sign-up period. Reimport.
You are performing a mid-period import into an existing sign-up period and the to date in the CAL file is earlier than the end date of the sign-up period.	The new end date must be the same as or later than the existing date.	Change the to date in the CAL file to one equal to or later than the existing date.	Reimport.
The From Date dd:mm:yyyyy in the schedule source is not the First Day of The Week as specified in the 'OPS/Bidding/FirstWeekday' property.	—	If the OPS > Bidding > FirstWeekday setting in OPS is correct, change the schedule information.	If the schedule information is correct, change the OPS > Bidding > FirstWeekday property. Reimport.
The To Date [dd:mm:yyyy] in the schedule source is not the Last Day of The Week as determined from the 'OPS/Bidding/FirstWeekday' property.	—	If the OPS > Bidding > FirstWeekday setting in OPS is correct, change the schedule information.	If the schedule information is correct, change the OPS > Bidding > FirstWeekday property. Reimport.
Division [xxxxx] for roster [xxxxx] is not defined in the HASTUS schedule. The roster will be imported without a division.	The DIV file does not include the division specified for this roster.	Add the division to the DIV file.	Reimport.
Node [xxxxx] is missing for pattern [xxxxx] and stop [xxxxx].	The NDE file does not include the specified node.	Add the node to the NDE file.	Reimport.
Line [xxxxx] has more than two directions in this sign-up period. Change the data and try again.	A line can only have two directions (east/west or north/south). The line is imported with the incorrect data.	Correct the line data so it only has two directions.	Reimport.
Run [xxxxx] [Hastus IntrRunId:[99999]] has a pay time of zero.	A run should have a positive pay time value.	Correct the data so the run has a positive pay time.	Reimport.
Roster [xxxxx] [Hastus RosterSetId:[99999]] has a pay time of zero.	A roster should have a positive pay time value.	Correct the data sot he roster has a positive pay time.	Reimport.
Run [xxxxx] belonging to roster [xxxxx] is not specified in the CRW file.	This roster will not be imported.	Add the run to the CRW file.	Reimport.
Only one holiday service group can be associated with each division. Division [xxxxx] has the following service groups: [xxxxx] and will not be imported.	The division is imported but the extra holiday service groups are not.	Remove the incorrect service groups from the duty set and calendar files.	Reimport.
An invalid date (ddmmyyyy) was encountered in the [xxxxx] file. Correct the data and reimport the schedule.	The date is not in ddmmyyyy format.	Correct the date format.	Reimport.
The operational day for the following record is out of range in the [xxxxx] file: ([xxxxx]). Correct the data and reimport the schedule.	The day has to be in the range 1-7.	Correct the day.	Reimport.
CAL File Error: holiday is not defined for this calendar date:	There is no record in the CAL file for the holiday.	Add the holiday to the CAL file.	Reimport.
RTE file error: route or transport mode not specified: ([xxxxx])	The RTE file does not include either the route ID or the transportation mode.	Add the route ID or transportation node to the RTE file.	Reimport.
Cannot find the associated block [Hastus IntrBlockId:[9999] in the BLK file for run [xxxxx[ [Hastus IntrRunId:[9999] operating on [xxxxx].	The CRW file references a block that cannot be found.	Add the block to the BLK file or remove it from the CRW file.	Reimport.

The pattern identifier ([99999]) for route [xxxxx] in not defined in the PAT file. Correct the pattern data and reimport the schedule.

The route (line) does not exist in the PAT (pattern) file. The data is imported in its undefined state.

Update the PAT file.

Reimport

Stop [xxxxx] for pattern [xxxxx] is not defined. Correct the stop data for this pattern and reimport the schedule.

The NDE file does not include the stop in the pattern.

Update the NDE file.

Reimport

InterTripId [99999] does not have a VehicleUnitStart. Fix the data and reimport the schedule.

The number of rail cars required is 0. It must be a positive integer. The import continues.

Correct the number of rail cars (VehicleUnitStart).

Reimport

The duty set with CrewSchName:[xxxxx], CrewServiceName:[xxxxx], CrewScenario:[99999], CrewDayType:[99999] does not exist in the CAL file. Add this duty set and reimport the schedule.

The calendar file does not include this duty set.

Add the duty set to the CAL file.

Reimport

This sign-up period already contains activated days before [ddmmyyyy]. The selected schedule will not be imported.

You cannot import into a sign-up period with already activated days.

—

On the Activate Day screen, use the Undo Day Activation feature to undo activation for the activated days within the sign-up period. Reimport.

This sign-up period already contains activated days before [ddmmyyyy]. The schedule before this date will not be imported.

The sign-up period has activated days, but at least one week at the end of the sign-up period has no activated days. The schedule will be imported only for the weeks following the last activated day.

—

On the Activate Day screen, use the Undo Day Activation feature to undo activation for the activated days within the sign-up period. Reimport.

You are performing a mid-period import into an existing sign-up period and the to date in the CAL file is earlier than the end date of the sign-up period.

The new end date must be the same as or later than the existing date.

Change the to date in the CAL file to one equal to or later than the existing date.

Reimport.

The From Date dd:mm:yyyyy in the schedule source is not the First Day of The Week as specified in the 'OPS/Bidding/FirstWeekday' property.

—

If the OPS > Bidding > FirstWeekday setting in OPS is correct, change the schedule information.

If the schedule information is correct, change the OPS > Bidding > FirstWeekday property.

Reimport.

The To Date [dd:mm:yyyy] in the schedule source is not the Last Day of The Week as determined from the 'OPS/Bidding/FirstWeekday' property.

—

If the OPS > Bidding > FirstWeekday setting in OPS is correct, change the schedule information.

If the schedule information is correct, change the OPS > Bidding > FirstWeekday property.

Reimport.

Division [xxxxx] for roster [xxxxx] is not defined in the HASTUS schedule. The roster will be imported without a division.

The DIV file does not include the division specified for this roster.

Add the division to the DIV file.

Reimport.

Node [xxxxx] is missing for pattern [xxxxx] and stop [xxxxx].

The NDE file does not include the specified node.

Add the node to the NDE file.

Reimport.

Line [xxxxx] has more than two directions in this sign-up period. Change the data and try again.

A line can only have two directions (east/west or north/south). The line is imported with the incorrect data.

Correct the line data so it only has two directions.

Reimport.

Run [xxxxx] [Hastus IntrRunId:[99999]] has a pay time of zero.

A run should have a positive pay time value.

Correct the data so the run has a positive pay time.

Reimport.

Roster [xxxxx] [Hastus RosterSetId:[99999]] has a pay time of zero.

A roster should have a positive pay time value.

Correct the data sot he roster has a positive pay time.

Reimport.

Run [xxxxx] belonging to roster [xxxxx] is not specified in the CRW file.

This roster will not be imported.

Add the run to the CRW file.

Reimport.

Only one holiday service group can be associated with each division. Division [xxxxx] has the following service groups: [xxxxx] and will not be imported.

The division is imported but the extra holiday service groups are not.

Remove the incorrect service groups from the duty set and calendar files.

Reimport.

An invalid date (ddmmyyyy) was encountered in the [xxxxx] file. Correct the data and reimport the schedule.

The date is not in ddmmyyyy format.

Correct the date format.

Reimport.

The operational day for the following record is out of range in the [xxxxx] file: ([xxxxx]). Correct the data and reimport the schedule.

The day has to be in the range 1-7.

Correct the day.

Reimport.

CAL File Error: holiday is not defined for this calendar date:

There is no record in the CAL file for the holiday.

Add the holiday to the CAL file.

Reimport.

RTE file error: route or transport mode not specified: ([xxxxx])

The RTE file does not include either the route ID or the transportation mode.

Add the route ID or transportation node to the RTE file.

Reimport.

Cannot find the associated block [Hastus IntrBlockId:[9999] in the BLK file for run [xxxxx[ [Hastus IntrRunId:[9999] operating on [xxxxx].

The CRW file references a block that cannot be found.

Add the block to the BLK file or remove it from the CRW file.

Reimport.

Message	Additional Detail	What to do
Message	Additional Detail	In HASTUS	In OPS
The pattern identifier ([99999]) for route [xxxxx] in not defined in the PAT file. Correct the pattern data and reimport the schedule.	The route (line) does not exist in the PAT (pattern) file. The data is imported in its undefined state.	Update the PAT file.	Reimport
Stop [xxxxx] for pattern [xxxxx] is not defined. Correct the stop data for this pattern and reimport the schedule.	The NDE file does not include the stop in the pattern.	Update the NDE file.	Reimport
InterTripId [99999] does not have a VehicleUnitStart. Fix the data and reimport the schedule.	The number of rail cars required is 0. It must be a positive integer. The import continues.	Correct the number of rail cars (VehicleUnitStart).	Reimport
The duty set with CrewSchName:[xxxxx], CrewServiceName:[xxxxx], CrewScenario:[99999], CrewDayType:[99999] does not exist in the CAL file. Add this duty set and reimport the schedule.	The calendar file does not include this duty set.	Add the duty set to the CAL file.	Reimport
This sign-up period already contains activated days before [ddmmyyyy]. The selected schedule will not be imported.	You cannot import into a sign-up period with already activated days.	—	On the Activate Day screen, use the Undo Day Activation feature to undo activation for the activated days within the sign-up period. Reimport.
This sign-up period already contains activated days before [ddmmyyyy]. The schedule before this date will not be imported.	The sign-up period has activated days, but at least one week at the end of the sign-up period has no activated days. The schedule will be imported only for the weeks following the last activated day.	—	On the Activate Day screen, use the Undo Day Activation feature to undo activation for the activated days within the sign-up period. Reimport.
You are performing a mid-period import into an existing sign-up period and the to date in the CAL file is earlier than the end date of the sign-up period.	The new end date must be the same as or later than the existing date.	Change the to date in the CAL file to one equal to or later than the existing date.	Reimport.
The From Date dd:mm:yyyyy in the schedule source is not the First Day of The Week as specified in the 'OPS/Bidding/FirstWeekday' property.	—	If the OPS > Bidding > FirstWeekday setting in OPS is correct, change the schedule information.	If the schedule information is correct, change the OPS > Bidding > FirstWeekday property. Reimport.
The To Date [dd:mm:yyyy] in the schedule source is not the Last Day of The Week as determined from the 'OPS/Bidding/FirstWeekday' property.	—	If the OPS > Bidding > FirstWeekday setting in OPS is correct, change the schedule information.	If the schedule information is correct, change the OPS > Bidding > FirstWeekday property. Reimport.
Division [xxxxx] for roster [xxxxx] is not defined in the HASTUS schedule. The roster will be imported without a division.	The DIV file does not include the division specified for this roster.	Add the division to the DIV file.	Reimport.
Node [xxxxx] is missing for pattern [xxxxx] and stop [xxxxx].	The NDE file does not include the specified node.	Add the node to the NDE file.	Reimport.
Line [xxxxx] has more than two directions in this sign-up period. Change the data and try again.	A line can only have two directions (east/west or north/south). The line is imported with the incorrect data.	Correct the line data so it only has two directions.	Reimport.
Run [xxxxx] [Hastus IntrRunId:[99999]] has a pay time of zero.	A run should have a positive pay time value.	Correct the data so the run has a positive pay time.	Reimport.
Roster [xxxxx] [Hastus RosterSetId:[99999]] has a pay time of zero.	A roster should have a positive pay time value.	Correct the data sot he roster has a positive pay time.	Reimport.
Run [xxxxx] belonging to roster [xxxxx] is not specified in the CRW file.	This roster will not be imported.	Add the run to the CRW file.	Reimport.
Only one holiday service group can be associated with each division. Division [xxxxx] has the following service groups: [xxxxx] and will not be imported.	The division is imported but the extra holiday service groups are not.	Remove the incorrect service groups from the duty set and calendar files.	Reimport.
An invalid date (ddmmyyyy) was encountered in the [xxxxx] file. Correct the data and reimport the schedule.	The date is not in ddmmyyyy format.	Correct the date format.	Reimport.
The operational day for the following record is out of range in the [xxxxx] file: ([xxxxx]). Correct the data and reimport the schedule.	The day has to be in the range 1-7.	Correct the day.	Reimport.
CAL File Error: holiday is not defined for this calendar date:	There is no record in the CAL file for the holiday.	Add the holiday to the CAL file.	Reimport.
RTE file error: route or transport mode not specified: ([xxxxx])	The RTE file does not include either the route ID or the transportation mode.	Add the route ID or transportation node to the RTE file.	Reimport.
Cannot find the associated block [Hastus IntrBlockId:[9999] in the BLK file for run [xxxxx[ [Hastus IntrRunId:[9999] operating on [xxxxx].	The CRW file references a block that cannot be found.	Add the block to the BLK file or remove it from the CRW file.	Reimport.