FATAL ERROR - invalid opcode 254 in token table

Bruce Easton bruce at stn.com
Fri Apr 4 06:17:25 PDT 2014


On 4/4/14 8:40 AM, Aldridge, Inc. wrote:
> On 04/04/2014 02:40 AM, Nancy Palmquist wrote:
>> Remember it is important to compile with the automatic table that will
>> be used when you are running the process.
>>
>> Also have seen issues with edits when compiling.
>>
>> I have one silly process that will increment a counter in the output by
>> 5 if I forget to compile it with the right automatic table.  It
>> increments by one when I do it right.  Weird right??
>>
>> Nancy
>>
>>
>> -- Nancy Palmquist Owner Virtual Software Systems - www.vss3.com (412)
>> 835-9417
> How does one compile (tokenize) the input process table WITH the
> automatic table? Each table is tokenized separately, isn't it?
>
By default, rcabe will tokenize an input/output table against 
"automatic" (*nix) or "auto" (windows) if it exists.  If you've 
designated a different automatic table to run with the input/output 
table for an application (i.e., via "rclerk myfile -z inputxx -y 
autoxx"), then when tokenizing, you should tokenize against that same 
designated automatic table (i.e., "rcabe myfile -y autoxx").

[Note that in the last example, rcabe will bring up the "Which 
Processing Table" menu for file "myfile" from which to choose a prc 
table; see the F10 help in Define Menus on other options for interactive 
and non-interactive modes by using one of the flags that start with "c".]

Bruce



More information about the Filepro-list mailing list