Re: Driving me nuts!

Shannon - much better stuff to think about than the non-economy!

Did you tell use what the error was? Even though you put the (e) on the CALLP, I think you'll still see the message in your job log - it's been several days vacation, so I might have that wrong.

Anyhow, it'd be interesting to hear what the error was. CPF2103 is normal when the library already is in the library list. Another error, well, as they say, see earlier messages in the job log.

Just curious.
Vern

Shannon ODonnell wrote:

By the way...this happened to me consistently for about 3 hours this morning
when I was trying figure out what was going on. I had logged off and on
multiple times in between also, and I had several instances of debug going
as well at different times.

Also, the code I posted here was the absolute distilled version from what I
started with, where the original code (that had the same error) was also
calling other programs (some under debug, some not).

It did finally work without errors when I logged off the last time, logged
back on again and did NOT start a debug session first.
I don't know why (or can't imagine why) debug would make a difference on
this as it never has before, but I'm equally sure I don't understand
everything that was going on during a debug session under the covers either.

Also, it wasn't always QGPL as the library to add. Originally I had a
different library in there, not that that makes a difference, but in the
interest of full disclosure...

I am baffled why this would cause a pointer error today across so many
interactive sessions that I ran, but there you go.

No new PTFs in months either, btw.

I'm am sure it is something I did incorrectly. I just don't know what it
was. Guess I may never know unless it happens again and I can glean more
information from it.

Thanks again all for considering the problem. At least it gave you
something different to think about besides the crappy economy for awhile.
:-)

Shannon O'Donnell