I am still trying to figure out, what the staticValue line is for...
It really doesn't make any sense to me.
I position my camera and want to save for later use to my cam library.
I want Poser to apply the settings used when adding the cm2 to the library.
Poser does that, but only when the camera is set to animating.
If animating is off, Poser writes a staticValue (with values prior to my changes)
and applies those.

When saving a cm2 for more than one frame, Poser writes k values and spline indicators and no staticValues as long as animating is on when saving.
If you turn animating off prior to saving the cm2, Poser 7 writes staticValue, using the last k line's value.

When applying the 30 frame preset to a cam that's set to animting, everything is fine.
If you apply the same cm2 to a cam that is not set to animating, Poser reads the staticValue (which is the cam position from your last frame).
The moment you change this camera to animating, Poser changes to the values from the first k line and plays your original animation.
Still, this doesn't help to understand why one would need staticValue...

To sum it up, in order to avoid any staticValue statements in your cm2, make sure your camera is set to animating when adding the cm2 to the library.
Even if it is not an animated camera.

Oh... and all my tests were done with no figure present!
Who knows, what might happen with a figure in the scene.

 

Yesterday's the past, tomorrow's the future, but today is a gift. That's why it's called the present.