My recollection is that STOW at least and probably BLDL and FIND are utterly character agnostic. You can create member names with non-printable characters in them, for example. As I recall you cannot reference them in JCL (of course) but ISPF displays them correctly and you can rename or delete them from 3.1. Been a long time -- I may be off on some of the details. Experiments would have been done around 1997.
Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Friday, January 13, 2017 12:09 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: New free / open source z/OS tools from Dovetailed Technologies On Fri, 13 Jan 2017 13:43:37 -0600, John McKown wrote: > >There is a UNIX command: cob2 which will do a COBOL compile and link. >Basically this is just a "driver" which, as Gil indicated, parses the >UNIX command line parameters, does dynamic allocations for DDs needed >and then does (I think) a normal MVS LINK command to invoke the >standard COBOL compiler. Note that any UNIX directories in the command >are allocated to the proper DD and the "normal" BSAM / BPAM UNIX >interface code in the access method takes care of the I/O. That is, >there is no UNIX I/O code in the COBOL compiler itself. At least, I >don't think that there is. This is why the COBOL COPY verb cannot >process a file name like "SOMEFILE.cpy" and why the file in the UNIX directory >must in in UPPER CASE, not in "normal" >lower case. On my system (z/OS 1.12), the cob2 command's full path >is: /usr/lpp/cobol/bin/cob2 > I believe BPAM/BLDL/FIND is case-indifferent and that any UPPER CASE restriction lies in the compiler. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
