Re: Question on CALLP use

1) If the first condition is true, the DOWNLOAD program waits until
CRSDnld44R is finished before it fgets the next IFS record.
2) To see why CRSDnld44R has a lock on the record that CRSDnld80R is trying
to update, I would have to see the code for CRSDnld44R.

There is also a chance that CRSDnld80R, a different call to DOWNLOAD, or
some other process has the record lock, but I will take your word for it
that you determined that it is CRSDnld44R that has the record lock, and that
it is really the CRSDnld44R from the same instance of DOWNLOAD.

In a message dated 4/21/2009 8:47:07 P.M. Jerusalem Daylight Time,
Stephen_Mooney@xxxxxxxxxx writes:

I have an ILE program (DOWNLOAD) that performs an 'fgets' on an IFS file.

Depending upon the record type (first two positions of the above read
record), I move the entire contents of that line into a pre-defined data
structure and then callp a procedure with that line to update records.

Here is an example of the code DOWNLOAD:

We fget data into p_data and dow p_data < > *NULL

If RecType = '44';
C44REC = line;
callp CRSDnld44R(C44REC);
Endif;

If RecType = '80';
C80REC = line;
Record = line;
callp CRSDnld80R(Record);
Endif;

We then fget data into p_data again followed by an enddo.

My question is, if the first condition is true, and we execute the callp
to CRSDnld44R, does the DOWNLOAD program wait until CRSDnld44R is finished
before it fgets the next IFS record, or does it continue to the point
where both CRSDnld44R and CRSDnld80R could be active at the same time?

The issue we seem to be having is that when CRSDnld80R runs, CRSDnld44R
has a lock on the record that 80 is trying to update. Thanks for any
help.

Stephen M. Mooney
Application Development Manager
Rural/Metro Corporation
9221 E. Via de Ventura
Scottsdale, AZ 85258
480-606-3216
encryptme

-----------------------------------------
This communication may contain confidential and/or proprietary
information
and may not be disclosed to anyone other than the intended
addressee.
Any other disclosure is strictly prohibited by law. If you are not
the
intended addressee, you have received this communication in error.
Please
notify the sender immediately and destroy the communication
including all
content and any attachments. Thank you.