Re: Viewing files in qtemp while in batch

On 10-Sep-2014 11:54 -0500, RPGLIST wrote:

On Wednesday, September 10, 2014 9:02 AM CRPence wrote:

On 09-Sep-2014 16:15 -0500, RPGLIST wrote:

I'm running a program in batch and debugging it with a service
entry point, is there a way to see those files in QTEMP and the
respective records? I can't seem to see them.

<<SNIP comments re both changing application and RtgE to enable>>

See also the following two messages authored by Bruce Vining; they
should elucidate an earlier response from Vern, though possibly no
more than the information\link provided by Carsten:

<http://archive.midrange.com/mi400/200602/msg00037.html>

<http://itknowledgeexchange.techtarget.com/itanswers/trace-job-trcjob/>
"... exit point called QIBM_QWC_JOBITPPGM and the Call Job
Interrupt Program (QWCJBITP) API. ... sample program demonstrating
this capability in my
<http://www.brucevining.com/Presentations/PPT_Presentations/Whats_new_in_system_APIs.pdf>
_What's New in System APIs_ presentation. ..."

The problem is this is part of a web service and there is no way I
know of to debug a web service other than through a service point
entry.... that still does not allow me the ability to see what is in
the files.

There is nothing about either a web service or the use of SEP debug
that would vitiate any of what was suggested; though the efficacy of
Routing Data for establishing IPC likely would be challenged. Both
[re]designing the /batch/ application to use a library other than QTEMP
[if the job is or will be serviced\debugged] and using the QWCJBITP API
will enable an ability to access the data in the objects in the QTEMP of
the serviced job.

Note: the QWCJBITP API effectively was a replacement for the
EXITPGM() function available prior via the old Trace Job (TRCJOB)
feature that was since eliminated; the API provided an alternative with
greater capabilities and controls to help ensure system integrity.

Obviously for an existing job, [re]designing the application is not
an option, thus looking to the API would seem more apropos.

--
Regards, Chuck
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.