Re: QNTC

IMHO, QNTC is a problematic choice any time.

Let alone using it between two IBM i's..

Agree with Rob's thought that and IPL or something is causing the issue.

How do you recover from the error? If ending and restarting the NEP, take
a look at it's initialization...guessing there's a MD in there.

Charles

On Fri, May 22, 2015 at 9:55 AM, <rob@xxxxxxxxx> wrote:

1 - I am not so sure that I would use QNTC between two IBM i's. I might
be more inclined to use QFileSvr.400. Although that has limitations with
really large files.
2 - Anything significant about this "every 6-12 weeks"? Like, maybe the
first time after an IPL, restricted state, or other such operation? If
so, then maybe an MD command might be needed to initialize the connection
between them.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Gary Thompson <gthompson@xxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 05/22/2015 09:35 AM
Subject: QNTC
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



We have two iSeries exchanging data in text files on their respective IFS
by way of QNTC.

Our current solution uses code based on Scott Klement's DELTREE to process
QNTC files,
typically looking for new files in an "unprocessed" folder, copying them
to a local IFS folder
and then "moving" the remote file from the "unprocessed" to the
"processed" folder.

About every 6 to 12 weeks a "never-ending" job gets stuck on CPDB050 -
Session init error
which within a couple of messages will stall in message wait on CPE3025 -
No such path or directory.

Can anyone point me to rpg code to handle this error ?

We have the "Who Knew" and "RPG: Exception" pdf's, but I've not done much
more than CL
monmsg and occasional rpg monitor.

Thanks!


--
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.



--
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.