On Thu, 9 Feb 2017 08:00:26 -0600, Elardus Engelbrecht wrote:
>
>To Esmie, I see there are NO LRECL and BLKSIZE in this snippet. Seemed you can
>just let IDCAMS figure it out for you.
>
Oooh! This is tricky. Some utilities "figure it out for you", others don't,
yet others will
override whatever you code, sometimes corrupting an existing non-empty PDS.
And the prevailing recommendation is omit BLKSIZE; let SDB operate. But are
there still facilities that require an absurd BLKSIZE, auch as <=3120?
And a few selected attributes are not replicated by LIKE. And is
DD PATH=...,LIKE=CATALOGUED.DATA.SET.NAME allowed?
Why not?
And allocation will not write an EOF with DISP=NEW unless you code DSORG.
Why not?
Syntax. Years ago, I instructed a colleague on the form for allocating a UNIX
file:
//SYSPRINT DD FILEDATA=TEXT,PATH=...,LRECL=125,BLKSIZE=12500
"But don't I need":
//SYSPRINT DD FILEDATA=TEXT,PATH=...,DCB=(LRECL=125,BLKSIZE=12500)
"No. Don't do that." He tried it his way; got JCL error. (Why!?)
"I told you so."
I hate JCL! If DCB=(...) is optional for tape, DASD, (terminal, punch,
reader, printer, spool, ...), why not likewise for PATH?
And some facilities would work better if one were allowed to code
DSORG with PATH.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
