SETSPPFP fails over a V4R4 *PGM

This appears to be an unintended side effect of a change in V4R4, and
is being looked at.  As a possible circumvention it appears that the
Store Program Associated Space (QCLSPGAS) API will create the
associated space if it doesn't exist so you could in the mean while
use this API to write a blank to the associated space after using
the QPRCRTPG API.  SETSPPFP should be OK then.

An APAR to formally document this change wouldn't hurt.

Bruce

>
>Our SETSPPFP fails with MCH0601, space class X"00" (primary associated
>space), over a V4R4 QPRCRTPG-made program.  Is this new behavior normal for
>V4R4 QPRCRTPG-made associated spaces, or an OS bug?
>
>SETSPPFP on V4R4 works okay over V4R3-and-earlier QPRCRTPG-made programs,
>but gets MCH0601, space class X"00", over V4R4 QPRCRTPG-made programs.
> V4R4 System API Reference still says QPRCRTPG creates 480 bytes in
>associated space.  Has this changed?  Neeed we switch to terraspace
>pointers here?
>

+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---