Re: Dynamic Allocation error in CA-Endevor

2013-02-07 Thread Gibney, Dave
ent: Tuesday, February 05, 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 &g

Re: Dynamic Allocation error in CA-Endevor

2013-02-06 Thread John McKown
Thanks! I'll pass that on to my boss. On Wed, Feb 6, 2013 at 3:44 AM, Καπα Ζαφ wrote: > Try to use EN$TRALC trace facility in your processor: > > //EN$TRALC DD SYSOUT=* > > > Greetings > Kostas > > -- > For IBM-MAIN subscribe / s

Re: Dynamic Allocation error in CA-Endevor

2013-02-06 Thread Καπα Ζαφ
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 IBM-

Re: Dynamic Allocation error in CA-Endevor

2013-02-05 Thread Lester, Bob
: Tuesday, February 05, 2013 2:41 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Dynamic Allocation error in CA-Endevor [ External ] 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

Re: Dynamic Allocation error in CA-Endevor

2013-02-05 Thread John McKown
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 that test does not match. Eventually the STORCLAS falls down to the OTHERWISE which fails the allocat

Re: Dynamic Allocation error in CA-Endevor

2013-02-05 Thread John Eells
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? If so...it's worth a look at the ALLOCxx parmlib support we added in z/OS V1.12, which s

Re: Dynamic Allocation error in CA-Endevor

2013-02-05 Thread Mike Wawiorko
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 c

Re: Dynamic Allocation error in CA-Endevor

2013-02-05 Thread John McKown
sday, February 05, 2013 11:30 AM > To: IBM-MAIN@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= > &g

Re: Dynamic Allocation error in CA-Endevor

2013-02-05 Thread Mingee, David
@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&#

Re: Dynamic Allocation error in CA-Endevor

2013-02-05 Thread John McKown
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 DSN=&&COBLST,DISP=(NEW,PASS),DCB=(...),U

Re: Dynamic Allocation error in CA-Endevor

2013-02-05 Thread Elardus Engelbrecht
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,

Dynamic Allocation error in CA-Endevor

2013-02-05 Thread John McKown
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",