RE: QMHSNDPM, QMHRMVPM, & Error Message Subfiles

Rory,

I've seen that technique used in some articles I found. When I get a spare
minute, I'll try that approach.

Buzz Fenner
Systems Analyst/Network Administrator
870.930.3374
mailto:bfenner@xxxxxxxxxxxxxxxx



message: 1
date: Wed, 3 Sep 2008 10:54:38 -0700
from: "Rory Hewitt" <roryhewitt@xxxxxxxxx>
subject: Re: QMHSNDPM, QMHRMVPM, & Error Message Subfiles

Buzz,

Frankly, I simplify things as follows:

1. Change the DDS to simply refer to the 10-byte program name:

A R ERRSFL SFL
A SFLMSGRCD(8)
A MSGKEY SFLMSGKEY
A PGMNAM SFLPGMQ
A R ERRCTL SFLCTL(ERRSFL) OVERLAY
A WINDOW(NTRKEY)
A LOCK
A SFLSIZ(50) SFLPAG(1)
A 03 SFLEND
A 03 SFLDSP
A 03 SFLDSPCTL
A 03 SFLINZ
A PGMNAM SFLPGMQ

2. Change the API calls to simply send messages to the program message queue
(which can be retrieved from the SDS, defined at the global level):

D PgmSDS SDS
D PgmNam 10A
...
C callp SndPgmMsg('CPF9897': 'QCPFMSG *LIBL':
C errTxt: wwMsgLen: '*INFO':PgmNam:
C 0: wwTheKey: dsEC);
...
C callp RmvPgmMsg(PgmNam:0:' ':'*ALL':dsEC);

It's also much simpler to understand for the next person.

HTH,

Rory


------------------------------







--
PRIVACY WARNING: For auditing purposes, a copy of this message has been
saved in a permanent database.