SAVLIB V3R7 back to V3R2

I recently had troubles saving files on a V3R7 box back to V3R2.  On the
SAVLIB (save accesss paths *yes), I specified V3R2M0 as the target and
got errors on some files saying "File XXXXX in library YYYY could not be
saved for the specified target release for reason code 2.  The reason
codes are:  2 - An attribute of the physical file's access path(s) is
not supported on the target release. "

The odd thing is that the files it picked on are quite random.  All of
the files were, and still are, on the V3R2 box and I moved them to the
V3R7 box to do some work on them (no recompiles or anything, just some
CPYF's and other misc) and now I am trying to move them back.  Some of
the files on the V3R7 box I didn't do ANYTHING to before trying to get
them back to V3R2.

Anyone hear of a PTF or something fixing such an oddity??  I don't
recall having such a problem before and I'm sure I've done it, but just
not between these to boxes.  TIA!

> **************************************************
> Sannan Solberg                          (406)523-1392
> Business/Programmer Analyst       (406)523-1636  fax
> Washington Corporations             ssolberg@washcorp.com
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---