Hi Ken
DISP=MOD was the first thing I tried when experiencing these problems, to no
avail. I suspect that there are multiple (possibly even parallel)
OPEN/WRITE/CLOSE to SYSPRINT in that product, but I don't understand at all why
this would work differently with different datasets/dataclasses.
*GUESSING* here...
There was a hiper apar against DFSORT that it dropped records.
Ed
On Sep 8, 2014, at 3:06 PM, Beat Gossweiler wrote:
Pushing this up again Anybody with a guess?
Thanks, Beat
On Mon, 1 Sep 2014 06:58:19 -0500, Beat Gossweiler
wrote:
Hi Peter,
EATTR settings are
Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Beat Gossweiler
Sent: Monday, September 08, 2014 4:06 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [IBM-MAIN] Missing Records in SMS Managed PS Dataset - Dataclass
dependant
Pushing this up again Anybody with a guess?
Thanks, Beat
On
Pushing this up again Anybody with a guess?
Thanks, Beat
On Mon, 1 Sep 2014 06:58:19 -0500, Beat Gossweiler
wrote:
>Hi Peter,
>
>EATTR settings are the same (blank) for both DataClasses. When allocating with
>either DataClass, IEHLIST shows EATTR=NS and ISPF shows no 'Extended
>Attribut
Hi Peter,
EATTR settings are the same (blank) for both DataClasses. When allocating with
either DataClass, IEHLIST shows EATTR=NS and ISPF shows no 'Extended
Attributes' line in the Data Set Information panel.
When allocating with explicit EATTR=NO on the DD-Statement (using the same
DataClass
Hi Beat,
I've had numerous problems with weird behavior of the software when
datasets were allocated on EAV volumes with the data set extended
attribute (EATTR) set to "Opt" and the software was not prepared for
this. EATTR=OPT allows the data set to reside in the extended
addressability are ov EA
