On Mon, Apr 15, 2019 at 12:37 PM Paul Gilmartin < [email protected]> wrote:
> On 2019-04-15, at 09:17:09, Seymour J Metz wrote: > > >> SYNADAF provides the DDname, which is sufficient > > > > Not when the dataset is dynamically allocated. I would not expect the OP > to have a clue what dataset SYS00001 is. > > That said, I consider this to be a case of missing information rather > than an issue with the data in the message; what needs clarification is the > referent of "WRNG.LNTH.RECRD"; IMHO changing the text to "Wrong Length > Record" would serve no purpose. > > > The clarification (as you suggested earlier) exists in: > > https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.idad500/xmbf.htm > > ... but this an endemic deficiency, and concealing it in HLASM would > be a further assault on the design integrity of OS/360's I/O abstraction. > > The deficiency should be remedied in DFSMS, not HLASM, and should be > extensible to provide for unforseen future enhancements in DFSMS. > I'll suggest an alternatuve SYNADAX call that returns a pointer to > an XML string with no specified maximum length, perhaps reasonably > formatted with use of vertical and linear white space. > Oh, I like that idea. XML, or even JSON (which is a bit more "compact"), for parsing would be nice. > > -- gil > -- This is clearly another case of too many mad scientists, and not enough hunchbacks. Maranatha! <>< John McKown
