Page 1 of 1

EXFMT closes program

Posted: Mon Apr 02, 2012 4:42 pm
by leomoore
I am perplexed. The RPG code was working on Friday. Today, it seemed possible that my bull-in-a-china-shop approach of modifying the DDS to get rid of what I thought was an extraneous subfile control record I might have damaged the Meta-data accidentally. I decided to scrap my display file and start over. I rebuilt my screen including all fields and indicators as well as redefining the subfile. This time, I did nothing directly in the DDS and once I had recompiled both display file and RPG. I tested. I hit my first breakpoint. I watched the program first clear the subfile with SFLCLR *On then then write records to the subfile with SFLCLR *Off. Once the program determined that records had been written, it turned on SFLDSP and SFLDSPCTL. The program hit a breakpoint at the primary EXFMT statement. I had established breakpoints at the line directly following. The program executed the EXFMT and ended. There is no error message that I can find. It never hit the next statement where I had a breakpoint. ProfoundUI Design ended the session exactly as it would with a normal.

Any ideas? Any secret logs that might contain ProfoundUI information.

I would appreciate any assistance.

Re: EXFMT closes program

Posted: Mon Apr 02, 2012 5:48 pm
by David
I think some error is happening on the handler call. When this happens you would normally get a descriptive error message on the browser screen to explain what is going on.

I remember when I was down before that you guys had something setup on your system that was replying with 'C' to any inquiry messages received in the HTTP server jobs. This causes any jobs with a message to end immediatley.

I'm thinking this behavior is back?

Can you try this:

WRKJOBD JOBD(QHTTPSVR/QZHBHTTP)

Then take option 5 to display.

What is the value for "Inquiry message reply"?

Re: EXFMT closes program

Posted: Tue Apr 03, 2012 9:07 am
by leomoore
The value for Inquiry Message Reply is *RQD.

Re: EXFMT closes program

Posted: Tue Apr 03, 2012 9:08 am
by David
So, it's still set to require reply to the inquiry messages -- that is good. I'm not sure, then, why you would not get an error message display.

I would recommend opening an issue with technical support.