The doc for GQSCAN says that "ISGQUERY is the recommended replacement for the GQSCAN service". But it says nothing about GQSCAN being deprecated - let alone eventually removed. We've used GQSCAN "forever" (actually since July 2000), and I need to make some updates to the code that uses it. But the interface to ISGQUERY is *very* different, looks much harder to use for my purposes, and in particular does not return RIBs and RIBEs as does GQSCAN.
So... Given that what I'm doing is a cross-system (SCOPE=SYSTEMS,XSYS=YES) query on a QNAME/RNAME combo with the RNAME wildcarded: Is there any clear advantage to converting to ISGQUERY? Are there performance issues (beyond the general cost of the XSYS=YES)? Given that ISGRIB comments say that the RIB/RIBE are copied from the GRS private area to the user-supplied area, it would seem that this would perform better than manufacturing the new-style return values from them, *if* the RIB and RIBE are the underlying control blocks used within GRS. Is there any serious chance that this use of GQSCAN will stop working in future (yeah, I know - no commitment...) The RIB and RIBE mappings in macro ISGRIB are classified PI. It's rare for IBM to change these classifications, but it has happened. Any thoughts on this? Thanks. Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
