Record Lock on Read from IFS file?

Long time lurker, first time posting. As such, I would like to take the
opportunity to express my appreciation to everyone who has posted here and
responded. I have learned a lot by monitoring the daily back and forth, and
the archives have provided answers to my own dilemmas more than once. But I
haven't found the answer to this.

V6R1. All RPGLE code.

Procedure in one program retrieves files into IFS via FTP. (Mr. Klement's
fine FTP API stuff.) FTP session is ended, then another program is called
to process the files.

The list of files is read into a user space, then each is opened and read
individually.

If I call the second program separately, (after retrieving the files, or
copying them into the IFS directory manually), everything works fine.
Records are read, the business logic is applied, the file is closed and
archived, then the next file is opened and processed. When called from the
first program, however, the process hangs on the read of the first record.
This is using the readf proc in QC2LE binding directory. No error is
logged. It is similar to the condition I have seen when trying to read a
locked record, but without the ensuing "Unable to allocate a record" error
that native IO would issue. Job status sits at TIMW, for as long as I am
willing to wait.

Is this, indeed, a "record lock"? Even though no other process has touched
the file?

Permissions? *PUBLIC has full authority.

Activation Group? First program is ActGrp(*New), the second one is
ActGrp(*Caller)

My next attempt at addressing this will be to submit the second program as a
separate job, but I don't see why I should need to.

TIA for any help.



______________________

Scott Sanders

scott@xxxxxxxxxxxxxxxxxx