We use SNDTCPSPLF to send spool files from a clients V7.1 machine to our v5.4 machine. This happens every 10 minutes or so.
The problem is that recently the send has been going to Status SELW and hanging there.
We have to end the sending job and start a new job and away it goes until the next time.
The "freeze" seems to happen with spool file which
reports what on records set by our systems to control some processes.
A lock record is set at 6.15 and then this is reported on by another job. This report is being sent to our system and it seems to be the one that hangs each
time, and from memory, if it hangs, it will be at about
So, it almost seems as if the job creating the report retains a lock on the report long enough to trip up the SNDTCPSPLF command.
One other factor we have found, on a recent occurance, that points to this is that the report actually got through to our system but it was 2 minutes after the previous report rather than a few seconds.
So the send happens but the command trips up at a lower
level than we control and rather than ending to proceed to the next step it just sits there.
Can anyone offer some clues/remedies for us to consider?
ibm iseries v7.1 and v5.4
June 25, 2012 9:51 PM
June 26, 2012 11:41 AM