Error message subfiles and procedures

All,

I've been through the archives, looks like I'm not the only one who has run 
into this wall.

However, the information in the archives hasn't been of much help.  I 
understand what the problem is, but I'm still trying to figure out how to solve 
it.

I've got a BNDRPG "work With" program with multiple sub procedures.

It calls routines in a service program to perform file I/O.  I'd like the 
procedures in the service program to be able to add entries to the program 
message queue so the can be displayed via the error message subfile in the 
"Work with" screen.

I've wrapped the QMHSNDPM API in a SndErrMsg() procedure in another service 
program.

Since the I/O service program doesn't know where it could be call from, ideally 
the SndErrMsg() program needs to determine where the message should be sent.

However, so far, I've been unable to get even a hard coded test case working.

Some areas I'm wondering about:
1) Behavior difference between DDS SFLPGMQ(10) and SFLPGMQ(267) when program is 
ILE?
2) Behavior difference between '*' and the *PROC name from program status DS 
when loaded to SFLPGMQ field.
3) Does it matter where (mainline or sub-procedure) the error message subfile 
control record is written or when the SFLPGMQ field is loaded.
4) What the heck do *PGMBDY, *PGMNAME, and *CTLBDY mean in English?


Does anybody have any tips/tricks/info that would help?

Thanks,


Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121