On Mon, Dec 21, 2015 at 8:54 AM, Paul Gilmartin < [email protected]> wrote:
> On Mon, 21 Dec 2015 07:01:22 -0600, John McKown wrote: > > >I "stumbled" across this RFE is my wanderings. I think it is a good idea. > >You might want to vote for it if you do also: > > > > > https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=78469 > > > ><quote> > >Enterprise Cobol support dynamic allocation for file (use of an > environment > >variable named with ddname an file parameters in value for allocation). > >But if we try to allocate a SYSOUT, this raise an error IGZ0251W at run > >time... > > > >It would be desirable to be able to dynamically allocate a SYSOUT in the > >same way that can dynamically allocate a file. > > > >An alternative solution is to use BPXWDYN... but this solution is not > "full > >Cobol"... > ></quote> > > > This is remarkably similar to the TSOALLOC environment variable used by > z/OS UNIX /bin/tso: > > > http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.bpxa500/tso.htm > > I notice that section says, "A complete listing of keys can be found in > z/OS Using REXX and > z/OS UNIX System Services," which I believe refers to the chapter > describing BPXWDYN, > but doesn't explicitly mention BPXWDYN. > > I'll advocate reusable code and transferrable programmer skills. Make the > values of those > argument variables employ (syntax compatible with) BPXWDYN. > It looks fairly close: http://www-01.ibm.com/support/knowledgecenter/SS6SG3_5.2.0/com.ibm.cobol52.ent.doc/PGandLR/ref/rliosass.html > > In what sense is BPXWDYN not "full COBOL"? What's empty COBOL, anyway? > I think it is not "full COBOL" in the sense that saying "per se" is not "full English". "per se" is a borrowed phrase from another language (which English loves to do). So doing a "CALL BPXWDYN" is "less COBOLish" than modifying the internal COBOL supplied code which supports dynamic allocation of data sets / UNIX files to also support SYSOUT. Or, to put it another way: "If it is full COBOL, why ain't it in the COBOL manuals?" and "why did IBM waste the coding of dynamic allocation via COBOL interfaces when BPXWDYN can do that and more?". Also, why would a COBOL programmer look for documentation on how to do something in a manual entitled "Using REXX and z/OS UNIX System Services". COBOL, and PL/I, are barely mentioned, in passing, in the documentation for BPXWDYN. And there is no example code in that book, or the COBOL book. Also, we are looking at this in a z/OS biased way. Does Enterprise COBOL support DOS/VSE (or whatever its called now)? If so, does it also allow allocation of files in VSE? Does VSE support BPXWDYN? Just some thoughts. I don't have much personal interest, given my likely eviction from the arena when I lose my current job. > > -- gil > > -- Computer Science is the only discipline in which we view adding a new wing to a building as being maintenance -- Jim Horning Schrodinger's backup: The condition of any backup is unknown until a restore is attempted. Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be. He's about as useful as a wax frying pan. 10 to the 12th power microphones = 1 Megaphone Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
