From: J L. T. <jlt...@ma...> - 2022-06-18 06:37:00
|
This is quite frustrating. In CMS/TSO Pipelines Author's Edition 1.1.12, Chapter 2 (pg 14 in my edition) it says, "Most stages in the PIPE command in Figure 19 have been described already; cons is an abbreviation of console. A few program names have an abbreviation, but most must be spelt out." In Chapter 20, pg 220, it says, "Keywords are shown in a Gothic font with the minimum abbreviation in upper case. When writing the keyword, you must provide at least the minimum abbreviation. Write the keyword in upper case or lower case; write it mIxEd if you like." but I'm fairly sure that the editor merely incorporated the boiler-plate syntax diagram help information from another manual. Otherwise, the author seems to have forgotten to tell us WHICH program names have abbreviations; in the rest of the manual they are either given entirely in upper case (Chapter 23) or entirely in lower case (Appendix A). Strangely, keywords other than the stage name are presented in the usual IBMish manner of upper case letters denoting minimum abbreviations, but not the stage names themselves. I suppose you can get some of the abbreviations from the z/VM CMS Pipelines Reference, but there are so many stages that are not documented there... Leslie On 2022-06-17 13:44:27 Jeff Hennick wrote: > My ERROR! I apologize. > > In getting NetRexx Pipelines stages updated last year, I did not look at > the working LOCATE stage, and did not inspect the IBM documentation to see > it could be abbreviated to just L. I will supply the needed short class > files (one is needed for each "word": L, LO, LOC, etc. to call the LOCATE > stage) to do this. When I have time, I'll scan the IBM documentation to > see if there are other such stages I have missed. Jeff Hennick -- |