Re: CPYF gives CPC2957 as completion message but hangs job

Hi Dennis,

I see those last two (QWSGET and QT3REQIO) any time my interactive job is waiting for input from me; in fact, on pretty much any interactive job that's in DSPW status.

I agree that the system and the terminal are out of sync, the question is what is getting them out of sync? This has happened consistently the last 3 times they've run the job. The programs in question have not been changed for the last 10-20 times they've run the job. Nor has their Rumba telnet software been upgraded. They did upgrade their iSeries recently, but the job ran fine several times after that before this failure started occurring.

This is not a "remote" connection; the PC running Rumba is in the same room as the iSeries.

It is also not a long running job -- 5 minutes including the time required to do before & after tape backups.

*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
pdow@xxxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxxx> /


On 5/5/2010 9:54 AM, Dennis Lovelady wrote:

Type Program Statement Procedure
QCMD QSYS /04F3
INLPGMC0 QGPL 15400 /00D6
GPRM950 GP#LIBR _QRNP_PEP_GPRM950
GPRM950 GP#LIBR 1790 GPRM950
PPCP400 HS#LIBR_PP _CL_PEP
PPCP400 HS#LIBR_PP 32900 PPCP400
PPCU669 HS#LIBR_PP 3700 /001F
QCPEX0FL QSYS /0121
QCPEXCON QSYS /0AB7
QCPGENIO QSYS /01DF
QDBGETM QSYS /0533
QWTPECTL QSYS /013D
QMHDLVMS QSYS /01A3
QMHDSMSS QSYS /1772
QWSGET QSYS /065D
QT3REQIO QSYS /0253

which to me looks like it's waiting for a response from the user;
however, his (Rumba) session shows input inhibited. WRKACTJOB shows the
job in a DSPW status.

I usually only see this on remote connections. The implication I have seen
is that both the system and the terminal believe there is a connection, but
there was a break in the communication that caused them to get out of sync.

If I'm right, the terminal is useless.

Why would an important function like that be run from an interactive job
that might fail (PCs reboot, communications break, ...)_ ? "Sorry, we can't
pay you for last week because there was a lightning storm Monday."

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
One of the reasons for the fall of the Roman empire was that, lacking zero,
they had no way to indicate normal termination of their C programs.
-- Robert Firth