Re: Keeping RCVJRNE running over receiver changes

Reeve,
Prompt the RCVJRNE command with F4=Prompt, then move the cursor up one line and press F1=Help, and you will get the full help for the entire command and all parameters.    This is one of the more extensive command help texts that I have seen.   Page down a few pages, and you will see that your exit program should be receiving a "3" in the first byte of parameter two.

At that point, what will happen is control will also return to the program that issued the RCVJRNE command, at the next sequential instruction.

You should be able to set up some simple mechanism using either a QTEMP *DTAARA or a *DTAQ etc. to allow your exit program to post a "message" or notification that a "3" was received, so the program that issued the RCVJRNE can check that indicator to know to loop back around and re-issue the RCVJRNE  for the next journal receiver.

I hope this "makes sense" and helps ...

All the best,

Mark S. Waterbury

On Thursday, August 18, 2022 at 08:52:52 PM EDT, Reeve <rfritchman@xxxxxxxxx> wrote:

Greetings all--

RCVJRNE passes two entries to an exit program--a buffer and a three-byte
control field.  When the journal receiver changes, RCVJRNE passes data into
the control field and my exit program sees "3N0", where byte 1 ('3')
indicates the RCVJRNE command is ending.  It ends--and so does my
application.  The return code in the job log is 0 and no message is posted.

It's easy to test this process: I start my program, it waits, I change the
journal receiver with *NEW, and my program ends with a "3".  This is an
unplanned and undesired feature.

I can't see if/where the control field is available as a returned parameter
in RCVJRNE; did I miss it?  Having this data would enable a clean mechanism
for restarting the RCVJRNE command.  Otherwise, I'll have to use a data
queue, a data area, or my configuration manager to pass the status back to
my CLLE program so I can restart.  I save the last processed entry sequence
number as part of my start/restart logic--the restart will be easy.

The API doesn't appear to return this data, so that option appears to be
off the table.

I'm surprised RCVJRNE isn't capable of handling a journal receiver change.

I'd appreciate ideas/suggestions/education.  Thank you!

--reeve