I have a couple suggestions for you.
1) Use the facilities of Dialog Test to try to isolate your problem.
On the ISPF main menu, unless it has been remove by a fastidious
soandso, the dialog test stuff is option 7. Note, if it has been
removed from the visible menu, try option 7 anyway, unless it has been
reassigned to another option. Sometimes I've seen it removed from the
menu, but still in the ZSEL structure and still work.
7.4 allows you to test many of the features of your table access. 7.1
allows you to issue most of the function calls.
2) use Doug Nadel's ISPVCALL facility to trace the ISPF occurrences.
Search the ISPF-L archives if you're not hip to Doug's facility. Who
knows, maybe it's even described in the official doc by now. Briefly,
you can a) issue the command, TSO ISPVCALL; b) cause your problem; c)
issue the command TSO ISPVCALL a 2nd time. The 2nd invocation takes you
into browse of the trace output. There is a lot of data there. If I
recall correctly, you can look for )MSG in column 1 to see highlights of
the problem occurrences. Look for better doc than I'm lazily providing.
good luck
Dave
-----Original Message-----
From: ISPF discussion list [mailto:ISPF-***@listserv.nd.edu] On Behalf Of
Bill
Sent: Wednesday, December 13, 2006 12:48 PM
To: ISPF-***@listserv.nd.edu
Subject: Re: TBSARG/TBSCAN/TBDISPL - what am I doing wrong?
It should work and yet it doesn't - this is the problem I'm trying to
solve.
I put the TBGET in to retrieve the current row for diagnostic purposes
to see which row the cursor would point to after the TBSARG.
I had originally put in a TBSCAN and TBGET after the TBSARG to set the
cursor to the first visible row so I could retrieve one of the columns
to use as an argument for another table. I've taken those out for
diagnosing this problem.
Bill
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.