Hi Simon,

how do set up the debuggable identifiers? Also I couldn't figure out
how to display the value of a pointer (at least using dsppgmvar)


On Sat, May 17, 2008 at 1:03 AM, Simon Coulter <shc@xxxxxxxxxxxxxxxxx> wrote:

On 16/05/2008, at 9:04 AM, Paul Jackson wrote:

Sorry, I was a bit premature with that statement. The pointers are at
the normal position but for some reason it seems as if the SETSPPFP
.WCBSPC, .WCB-TABLES(THE-TABLE); statement is not setting .WCBSPC
properly as the based on structure is all hex zeros.

That's very odd. Can you recompile it with debuggable identifiers and
determine what .WCBSPC is set to before and after the SETSPPFP

You said you were running this on VRM540, QSECURITY=40, and program
set to system-state. I compiled on 510, set system state (including
proper checksums) and tried it and it worked. I then saved the
program and test program, restored on VRM540, and tried it, and it

So the code seems fine--although it's not the most efficient way of
locating a given job.

I wonder what else is different on the failing system? Same level of
LIC? Same Cume level?

Simon Coulter.
FlyByNight Software OS/400, i5/OS Technical Specialists

Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
ASCII Ribbon campaign against HTML E-Mail / \

This is the MI Programming on the AS400 / iSeries (MI400) mailing list
To post a message email: MI400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mi400
or email: MI400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mi400.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].