Jan Vanbrabant wrote:
Hi,
We pre-allocate a dataset *without* EXPDT
(trust me there are good reasons why we don't set a EXPDT hic et nunc at
pre-allocation time, which I'm not going to elaborate upon).
Looking into SMS confirms: Expiration date . . : ***None***
In a next SyncSort step we use that dataset as
//SORTOUT DD DSN=...bla.bla.bla...,DISP=OLD,EXPDT=filled-in
i.e. with an expiration date set in the JCL this time.
This EXPDT setting is *NOT* honoured.
Is this WAD (Working As Designed) with SyncSort?
*
We think indeed it is a 'problem' with SyncSort.
We did another test with a pre-allocation without *EXPDT* and with another
program + EXPDT, in this case the EXPDT *got* honoured.
This doesn't sound like a sort issue at all. The application is not
normally involved in such matters.
I suspect that EXPDT in the format-1 DSCB for an existing file can be
reset like this only when the file is opened for output or update. I
would have to run some tests to be sure.
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
