RE: Record Lock on Read from IFS file?

Hello, Chuck.

That parallels my experience, as well. But I have stepped through every
line of code in these programs in debug, and have not encountered any
deliberate wait. However, I also seem to recall seeing that status appear
on a job retrieving or sending a large file via FTP to a remote system.
This lends weight, at least in my mind, to the thought of splitting the FTP
and file processing functions into separate jobs. Not just separate
programs in the same stack.

On the other hand, Scott Klement has asserted that the FTPAPI functions
should not lock the streamfile, and I have used similar logic to retrieve
files and process them without incident.

I will report back after making the change.

Thanks.

______________________
Scott Sanders
scott@xxxxxxxxxxxxxxxxxx

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-
bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Tuesday, May 15, 2012 10:13 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Record Lock on Read from IFS file?

On 14 May 2012 15:30, Scott Sanders wrote:

Job status sits at TIMW, for as long as I am willing to wait.

That job status reflects a "coded wait", meaning that some code
deliberately has requested to pause the thread, awaiting a timed event;
e.g. sleep() or DlyJob had been issue. So rather than reviewing the
job "status", review the program "stack"; WRKJOB OPTION(*PGMSTK) to see
what code has requested a timed-wait.

Regards, Chuck
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.