Peter Knapper wrote in a message to Linda Proulx:

 PK> A good way to understand EA's better is to look at a REXX .CMD 
 PK> file on an HPFS drive. Here is one such file on an HPFS drive -

 PK>  9/01/99   9:43       1204        4298  psend.cmd

 PK> In this case the PSEND.CMD file is 1204 bytes long, and the 
 PK> EA's for it occupy  4298 bytes. When this file is run, REXX 
 PK> checks to see if the main file (PSEND.CMD) has been updated 
 PK> since the EA's for it were created, and if so it automatically 
 PK> "re-compiles" the REXX script into the EA's, and then runs the 
 PK> EA's. Subsequent runs of the .CMD file are fast because it has 
 PK> already been "compiled".  As soon as the file date is later 
 PK> than the EA date, REXX "re-compiles" it again automatically. 

 PK> Again, the EA's for REXX files are non fatal, they will be 
 PK> automatically re-built once the file is run under OS/2, but 
 PK> they are a useful example of the relationships between files 
 PK> and EA's. They are a close cousin to the Macintosh concept of a 
 PK> Data FORK and Resource FORK for a file.

Now this is some interesting stuff...

I wasn't aware of this about REXX,  and WRT EAs in general,  I don't do all
that much with them,  and am not sure what they're good for,  for the most
part. 

---