Its just that it was a temporary dataset allocated to SYSPRINT that got the B37
abend.
> On Jun 21, 2017, at 12:05, Mark Pace wrote:
>
> I'm not sure how I would that, or how to point ERBSCAN to use that dataset.
>
>> On Wed, Jun 21, 2017 at 11:26 AM, J R
I used DDLIST and member to search for ERBSCAN and found it was a REXX exec
and I was able to modify the temp file allocations. It works fine now.
On Wed, Jun 21, 2017 at 12:05 PM, Mark Pace wrote:
> I'm not sure how I would that, or how to point ERBSCAN to use that
I'm not sure how I would that, or how to point ERBSCAN to use that dataset.
On Wed, Jun 21, 2017 at 11:26 AM, J R wrote:
> Have you tried preallocating a large SYSPRINT dataset?
>
>
>
> > On Jun 21, 2017, at 11:05, Mark Pace wrote:
> >
> > I'm
Have you tried preallocating a large SYSPRINT dataset?
> On Jun 21, 2017, at 11:05, Mark Pace wrote:
>
> I'm trying to run an ERBSCAN against a really large SMF file.
>
> Please Wait... Copying to temporary VSAM dataset...
>
> Then after a minute.
>
> IEC030I
I'm trying to run an ERBSCAN against a really large SMF file.
Please Wait... Copying to temporary VSAM dataset...
Then after a minute.
IEC030I B37-04,IFG0554A,MARPACE,IKJACCNT,SYSPRINT,B420,TMPL05,
SYS17172.T110243.RA000.MARPACE.R0116499
***
So my impression is that the Temporary dataset was