IMHO examples of REXX calls in any documentation should include both quoted stem names and variable containing the stem name, with appropriate comments. The descriptions should make it clear that normal REXX expression syntax applies, and the manuals should not make incorrect statements in the name of simplicity.
FWIW, similar considerations apply to descriptions of the JCL for various programs; all too many manuals make incorrect statements in an effort to avoid either an accurate description or a reference to the JCL Reference manual. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@listserv.ua.edu> on behalf of Peter Hunkeler <p...@gmx.ch> Sent: Wednesday, June 13, 2018 9:00 AM To: IBM-MAIN@listserv.ua.edu Subject: AW: REXX calling bpxwunix when SIGNAL NOVALUE active >call bpxwunix cmd,"unsorted_data.","sorted_data.",stderr. The FM manual describes the parameters to be "the name of a compound variable". If you don't quote, REXX will try to dereference the variables, does not find them, and raises NOVALUE if activated. If not, those which were initialized (unsorted_data & sorted_data) are replace by a blank. I think the examples in the doc should be updated to quote any and all of the parameters which denote a stem variable. -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
