× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



With a subprocedure it adds a new call stack entry for the proc. You'll
have to send the msg up a level in the call stack...



From: "Smith, Mike" <Mike_Smith@xxxxxxxxxxxxxxxx>
To: "'RPG programming on the IBM i / System i'"
<rpg400-l@xxxxxxxxxxxx>,
Date: 05/03/2012 03:03 PM
Subject: message subfiles not working after changing from
subroutines to subprocedures
Sent by: rpg400-l-bounces@xxxxxxxxxxxx



I have a subfile program that sends a message using a message subfile when
an error is generated.

This program worked fine, until I converted all of the subroutines to
procedures. I send the messages to the message subfile via a procedure.

I tried changing the SDS program name variable to '*' but that didn't seem
to help.

I searched the archives and the answer is probably there, however, I've
been chasing this all day and just realized that the only difference is
subroutines to subprocedures and my head is all mush at this point.

What do I need to change to make this work now?

Some pertinent pieces of code

D PGMST SDS
D #PGMNM *PROC
D #PARMS *PARMS
D DSPDEV 244 253
D #USER 254 263

C Call 'TRKCREWMNT'
C Parm 'I' Mode
C Parm TRUCK
C Parm TCCREW

C Move 'RGM0005' #MSGID
C CallP AddMsgSF(#MSGID:' ':'RGCMSGF')

Mike
NOTICE: This message, including any attachment, is intended as a
confidential and privileged communication. If you have received this
message in error, or are not the named recipient(s), please immediately
notify the sender and delete this message.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.