Respectfully, I'm reasonably certain at least one of the uses of 'attitude' there means 'altitude?' (I only care about spelling when it matters)
David: I'm not so ungrateful that I didn't -look- at the file you provided; I'm just not entirely certain I understood it. =)
"Attitude" means "attitude" or if you prefer, "orientation".
Regardless, let's take a moment and look at one entry of the text file I posted, and see if we can make it a little more useful (my apologies, I sometimes assume too much, I make the same mistake with my students...).
Code:
[SIZE=1]Maneuvers contained within the current ephemeris are as follows:[/SIZE]
[SIZE=1] IMPULSIVE TIG (GMT) M50 DVx(FPS) LVLH DVx(FPS) DVmag(FPS) [/SIZE]
[SIZE=1] IMPULSIVE TIG (MET) M50 DVy(FPS) LVLH DVy(FPS) Invar Sph HA[/SIZE]
[SIZE=1] DT M50 DVz(FPS) LVLH DVz(FPS) Invar Sph HP [/SIZE]
[SIZE=1] ------------------------------------------------------------------------[/SIZE]
[SIZE=1] 189/16:05:07.738 39.9 98.1 98.1 [/SIZE]
[SIZE=1] 000/00:38:21.738 -46.6 -0.0 123.6 [/SIZE]
[SIZE=1] 000/00:01:06.417 -76.6 0.1 84.9[/SIZE]
The first column has three rows of entries, the time of ignition ("TIG") in both the GMT time, the mission elapsed time (MET) and finally the length of the burn (in this case, OMS2 was predicted to occur on the 189th day of the year (7/8/11) at 16:05:07.738 GMT (the launch was originally predicted for 15:26:46 GMT), that would have been an MET of 38m:21.738s, and the total burn duration was predicted to be 1 minute, 6.417 seconds.
The second column shows the velocity changes (DV) in each of the principle orbiter axis (x,y,z) in feet per second (FPS) in the M50 frame of reference (an 'inertial frame'). For OMS2 then, it was predicted that the x component would be changed by 39.9 FPS, the y component would be reduced by -46.6 FPS, and the z component would be reduced by -76.6 FPS
in that frame of reference.
The third column shows the velocity changes in the relative frame of reference of the local-vertical, local-horizonal (LVLH); this is probably a little easier to understand frame as it is referenced directly to the principle orbiter (shuttle orbiter, not our favorite simulation) where the x axis runs from the tail through the nose, the y axis runs from wing to wing, and the z axis runs upwards and downwards through the body of the orbiter. Again the units are feet per second, and now we can see an almost complete velocity increase
prograde of around 98.1 feet per second and a very slight increase of the vehicle along the z axis of 0.1 FPS.
The fourth and final column shows the absolute magnitude of the OMS2 burn in FPS, again referenced to the LVLH frame of reference, in this case the 98.1 FPS, then the new orbit's apogee (HA) in nautical miles of 123.6 nm and the new orbit's perigee (HP) in nautical miles of 84.9 nm.
These state vectors are frequently updated for both the shuttle (when one is flying, sadly too soon this will end), and periodically for the ISS as well. They can be found at:
http://spaceflight.nasa.gov/realdata/elements/
Hopefully, this helps make the file a little more useful, or at least informative.