RE: I need faster SQL

I am starting to feel like a beginner again, so I'm going to take things
step by step.

Steve Ellsberry said:

First thing to do is run the job in debug so you can see what SQL is
doing. Pay special attention to whether or not SQL if SQL is having to
build an access path. If so you'll significantly improve performance if
you create one so that SQL doesn't have to do it every time your job
runs.

Kim says: 

When I first read this, I knew that I was going to have a problem in
that I wouldn't know what to look for in debug to determine if SQL is
having to build an access path.  Turns out, the problem is greater than
I thought.

When I run in debug and step through the service program function
$Allocate, the debugger seems to jump to various points in the listing
in a manner that doesn't make sense to me.  The calling batch program is
compiled with DBGVIEW(*LIST) and the service program module is compiled
with DBGVIEW(*SOURCE).