Re: Message Subfiles and ILE

[David & Eileen Keck <bstars@xxxxxxxxxxxxx>]

Thanks Mark - we are at V5R1 so I am sure this is the problem - thanks for
identifying it for me.  -Dave K.

----- Original Message -----
From: "Mark Phippard" <MarkP@softlanding.com>
To: <MIDRANGE-L@midrange.com>
Sent: Tuesday, May 29, 2001 5:27 AM
Subject: Re: Message Subfiles and ILE


>
> David,
>
> If you are on V5R1 of OS/400, there is a PTF named SI00975 that fixes a
> problem where subfile messages did not appear for ILE programs.
>
> Hope this helps.
>
> Mark Phippard
>
>
>
>
>
>                     David & Eileen Keck
>                     <bstars@optonline.n        To:     Midrange-L
<midrange-l@midrange.com>
>                     et>                        cc:
>                     Sent by:                   Subject:     Message
Subfiles and ILE
>                     owner-midrange-l@mi
>                     drange.com
>
>
>                     05/28/01 01:50 AM
>                     Please respond to
>                     MIDRANGE-L
>
>
>
>
>
>
> Consider a working RPG/400 program and associated DDS whose sole purpose
is
> to display a message in a message subfile on a standard *DS3 non-window
> display file.  If you create an ILE version of the program using CVTRPGSRC
> (to activation group QILE), would you expect the converted program to
> behave
> the same as original version ?  I did, but no entry ever appears in the
> message subfile of the ILE version of the program.
>
> The Send Program Message API QMHSNDPM does cause the message to be
> reflected
> in the job log, and the message details (F9) indicate a correct call stack
> entry.  In my test code I specify the Call Stack Entry / Program Queue to
> be
> '*' for both the QMHSNDPM API and the SFLPGMQ DDS keyword.  I have tried
> both SFLPGMQ(10) and SFLPGMQ(276).   I can post the code but thought
> someone
> might know what's wrong from this description alone.  Thanks - Dave K.
>
> +---
> | 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
> +---
>
>
>
> +---
> | 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
> +---
>

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