View previous topic :: View next topic
|
Author |
Message |
Steve Coalbran
New User
Joined: 01 Feb 2007 Posts: 89 Location: Stockholm, Sweden
|
|
|
|
When did the LRECL, BLKSIZE etc cease to need to be sub-parameters of the DCB statement.
It must have been a while ago but I still see...
Code: |
DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB) |
and stuff like this!
/S |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
I checked an OS/390 V2R10 manual and they are separate parameters in it, so the change dates to 2000 or earlier.
Fortunately, IBM maintains backward compatability -- a LOT -- so using them as DCB subparameters is still supported and will be for at least quite some time to come. |
|
Back to top |
|
|
prino
Senior Member
Joined: 07 Feb 2009 Posts: 1306 Location: Vilnius, Lithuania
|
|
|
|
I very vaguely seem to remember that this change happened at about the time of the introduction of the JCLLIB, INCLUDE & SET statements, which was in the years between 1991 and 1995. |
|
Back to top |
|
|
Nic Clouston
Global Moderator
Joined: 10 May 2007 Posts: 2455 Location: Hampshire, UK
|
|
|
|
Hi Steve - think it came in with SMS and BLKSIZE=0. I dont' use DCB= any more for most stuff but I think it is still needed for things like BUFNO and dummy dscbs but I am probably wrong on that. |
|
Back to top |
|
|
Steve Coalbran
New User
Joined: 01 Feb 2007 Posts: 89 Location: Stockholm, Sweden
|
|
|
|
Thanks for all the responses.
Hi Nic
It is certainly still used for backward references. DCB=*.SYSUT1 etc..
I suspect BUFNO can probably be specified separately as the other sub-parameters like LRECL.
(Dummy DSCBs - ugh, don't!)
PS:How's Ireland? It's hot and sunny, well 'sunny' anyhow (at least for the moment) in Stockholm. |
|
Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009 Posts: 580 Location: London
|
|
|
|
It happened with around 1988-89 with DFPv3.1
LRECL,RECFM,BLKSIZE can all be coded independent of the DCB parameter, but can still be coded with it. BLKSIZE doesn't even need to be coded most of the time now, or just coded as BLKSIZE=0 and the system will determine the optimal half track BLKSIZE for you.
EXPDT and RETPD can also be specified without 'LABEL=' which dates from the same period. |
|
Back to top |
|
|
|