ASAXWC has not been tested in P<>H environment, but it seems likely it would work, both for the normal path that obtains a works area (since it uses STORAGE OBTAIN) and also for paths where you provide a workarea. Those paths do not issue any SVC's (which is the normal inhibitor to accommodating cross-memory invocation). In all cases all the data must be accessible in the primary address space.
I trust you're aware that the "default" exactly-one-char symbol is "?" rather than "%". There are definitely existing uses of "%" for that case, though, which is why ASAXWC allows you to specify which such symbol you want used. As to performance, it's brute-force. It's not quick. Those areas that need "quick" might well choose not to accommodate full flexibility (for example supporting only a trailing asterisk so that all they have to check are the "n" characters preceding the asterisk in the pattern). Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
