I know that VM development increments the level with every new release of z/VM. (I've been keeping track of it for years..) You have the correct numbers - CMS level 14 (VM/ESA 2.3.0) is pipe level 110A0020 and they've incremented by 1 up to the current CMS level 23 at 110A0029. I'd say yes, look for level 110B or newer for plastic pipes. Or, combine your check with the output from PIPE q source to see if the level you're running is from the "Princeton Runtime Distribution" (it still says that) or a z/VM release.
On Thu, Feb 28, 2008 at 6:15 PM, Glenn Knickerbocker <[EMAIL PROTECTED]> wrote: > OK, is the built-in version actually frozen at sublevel 22 even though it > reports 23-29 on CMS 17-23? I was puzzled when STRLITERAL CONDITIONAL > failed on what I thought was a recent enough pipeline level. > > PIPELINE NEWS1110 says: > > Level 1.1.10 sublevel 20 (decimal 32) is the level integrated with > > CMS14. > > and I have an old list of levels showing I confirmed at the time. > PIPELINE NEWS1111 says: > > > -------- Shipped to VMTOOLS 26 Oct 1998 22:10:45 ----------------------- > > PIPELINE MODULE Modification 1.0110 sublevel 0027 (39 in decimal) > > STRLITERAL Add CONDITIONAL and IFEMPTY options. > So I double-checked the level on my system: > > > q cmslevel > > CMS Level 23, Service Level 701 > > > epipe query level > > FPLINX560I CMS/TSO Pipelines, 5741-A05/5655-A17 level 110A0029 > > But still: > > > epipe strliteral ifempty > > FPLLIT060E Delimiter missing after string "ifempty" > > READER KEEP (new in 22) works; ASMCONT OFFSET (new in 23) doesn't. > > It's probably silly to bother, but is there any way to distinguish the > fake levels from the real ones, just in case I run into a 9-year-old > runtime? Or do I just have to look for 110B if I need anything newer > than 110A0022? > > ¬R > -- Bruce Hayden Linux on System z Advanced Technical Support Endicott, NY
