×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 07-Mar-2012 07:51 , Smith, Mike wrote:
<<SNIP>> the program(Program_A) is that when the dataq receives an
entry <<SNIP>>
Program_A is submitted to QBATCH and has a wait time
of -1 on the QRCVDTAQ API. <<SNIP>>
So testing, <<SNIP>> Now I perform a end job but the program won't
end. I have repeated this scenario a couple of times and have to
perform an IPL to get rid of this job.
Generally speaking... That should not happen. Thus, the best
approach may be to contact your service provider to investigate the
origin for the job not ending gracefully while in the DEQW status.
And\or...
Version, Release, Modification? Cumulative level? Spooled joblog
from the job [produced as part of IPL]? Any other spool data associated
with the job, not part of normal processing? Is the DTAQ journaled?
VLogs for the process? VLogs for the object? Messages in the history
for the job or the object? VLogs around the time of the ENDJOB? If the
API call is not library qualified with QSYS, ensure there is not another
being invoked; spooled DSPJOB of job before ENDJOB would show that, and
be good to have as reference anyhow.
Regards, Chuck
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
