, 2013 1:41 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Dynamic Allocation error in CA-Endevor
Not the problem. The problem appears to be a permanent data set
allocation with a name like: SYS13036.Thhmmss.RA0.userid.COBLST. The ACS
routines say that this allocation is not DSTYPE='TEMP'. So
Try to use EN$TRALC trace facility in your processor:
//EN$TRALC DD SYSOUT=*
Greetings
Kostas
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO
We've got a weird one. The tester is getting a dynamic allocation error.
The message from Endevor is:
C1A0010E ALLOCATION ERROR RC=9700-03E9, DDNAME=
I can find the 9700. But I can't find any 03E9 in any IBM manual. Also, I
don't know why the DDNAME is blank. From looking at the SCL processor,
John McKownwrote:
The message from Endevor is:
C1A0010E ALLOCATION ERROR RC=9700-03E9, DDNAME=
What is the level of Endevor and your z/OS?
From looking at the SCL processor, each time the DSN is referenced, it is
the only DSN in the DD statement.
Is that DSN the only one in the TSO? Ie, no
Endevor is release 12. Can't go to 15 do to some problems; which requires
changing some SCL; which is what this is trying to test. z/OS is 1.12.
User is in split screen, but only using Endevor in one screen.
The first reference to the dataset in the SCL is
@LISTSERV.UA.EDU
Subject: Dynamic Allocation error in CA-Endevor
We've got a weird one. The tester is getting a dynamic allocation error.
The message from Endevor is:
C1A0010E ALLOCATION ERROR RC=9700-03E9, DDNAME=
I can find the 9700. But I can't find any 03E9 in any IBM manual. Also, I don't
know why
Subject: Dynamic Allocation error in CA-Endevor
We've got a weird one. The tester is getting a dynamic allocation error.
The message from Endevor is:
C1A0010E ALLOCATION ERROR RC=9700-03E9, DDNAME=
I can find the 9700. But I can't find any 03E9 in any IBM manual. Also, I
don't know why
SYS13036.T095110.RA0.TSH012.COBLST
At a quick glance this looks like a temporary dataset. Could you have two
similarly named trying to be allocated within the same second 09:51:10?
Mike Wawiorko
Please consider the environment before printing this e-mail
This e-mail and any attachments are
Mike Wawiorko wrote:
SYS13036.T095110.RA0.TSH012.COBLST
At a quick glance this looks like a temporary dataset. Could you have two
similarly named trying to be allocated within the same second 09:51:10?
snip
If so...it's worth a look at the ALLOCxx parmlib support we added in
z/OS V1.12,
