Charles Hardee wrote on 2007-07-20 10:16:57: > What about simply another internal variable, similar to say, TITLE. > One could then code > > For Page: EVAL PAGENUM CLIST|REXX(STO(variable_name)) > For Line: EVAL LINENUM CLIST|REXX(STO(variable_name)) > > I mean, if one could dream and hope, I would think this might be the > easiest to implement. I'm guessing here, but there's probably a table of > keywords that are looked for, like TITLE, etc, that trigger an internal > routine call rather than a read of the dump directory to satisfy the > return of the value, maybe? > > Just a thought. > > In any case, I can and have coded my own page logic before but in this > case, I didn't want to start the display generation on a new page, I > just wanted to generate it right in line with headers when appropriate. > > Thanks for listening Bob, and the rest of the list as well.
IPCS symbol tables are attached to dumps, traces, or other data sources. The information that you want to extract pertains to the current session environment and is not necessarily related to such a source of data, but the answer would change depending on routing to terminal, print, or both. That's why I mentioned an EVALPAGE subcommand whose operands could be designed to do several things. (a) Let you foreshadow message routing options that you intend to employ shortly afterward. (b) Indicate whether the command procedure that was listening was written as a CLIST, REXX exec, or ISPF dialog. (c) Select the information to be extracted rather than having IPCS blast data into many times the number of command procedure variables than you want or need. Bob Wright - MVS Service Aids ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
