Re: paradox ?

DCL DD     TEMPLATE   AUTO CHAR(32);
DCL DD     OPTIONS    DEF(TEMPLATE) POS(1) CHAR(4) INIT(X"80000001");
DCL SYSPTR ?PGM       DEF(TEMPLATE) POS(17) INIT("A");
DCL SPCPTR ?TEMPLATE  AUTO INIT(TEMPLATE);

CALLX   ?PGM, *, *;
CALLX   ?TEMPLATE, *, *;

The first CALLX form respects A's state and propogates adopted user
profiles.  The second CALLX form forces A to user state and
suppresses adopted user profiles.  By the way the QPRODT index
entry for CALLX lists "pointer" twice for the operand 1 value.
I assume this indicates once for system pointer, once for space
pointer.  Now extrapolate this assumption to the MATPG entry in
QPRODT index, where we find operand 2 lists "pointer" twice and
"machine space pointer" once.  Now why in the world does MATPG
allow a space pointer or machine space pointer in operand 2, in
place of a system pointer to an OPM program?  Does this indicate
a secret template that materializes more stuff than regular MATPG?


+---
| 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
+---