Re: We have a mystery

Are these records perhaps written just before they're read? If so, what
method is being used to write the records?

___________________________________
Darren Strong
Dekko





From: Mike Cunningham <mike.cunningham@xxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 10/05/2017 12:45 PM
Subject: We have a mystery
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



We have an RPG with embedded SQL program running in a CL program that has
calls to multiple RPG programs. This CL is run from the job scheduler late
at night. We were having issues with this night job that looked like it
was not running the one RPG app but when run during the day by itself it
would work perfect. So we added a trace to the program to see what it was
doing at night. It showed that no data was being read from the SQL fetch
command. When it was run by itself during the day it showed it read
thousands of records. The next debug step we did was to have the main CL
that runs at night CALL the RPG app and then also do a SBMJOB to call the
same RPG app. When run from the main CL with a CALL it read nothing. 2
minutes later when it was submitted it ran fine and read thousands of
records.

We are stumped. Has anyone ever seen this happen before? There are no
overrides or explicit sharing of open data paths.

Mike Cunningham

________________________________
This email may contain confidential information about a Pennsylvania
College of Technology student. It is intended solely for the use of the
recipient. This email may contain information that is considered an
"educational record" subject to the protections of the Family Educational
Rights and Privacy Act Regulations. The regulations may be found at 34
C.F.R. Part 99 for your reference. The recipient may only use or disclose
the information in accordance with the requirements of the Federal
Educational Rights and Privacy Act Regulations. If you have received this
transmission in error, please notify the sender immediately and
permanently delete the email.