IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

0C4 with ENDEVOR when CALL mod with TTR greater than A00000


IBM Mainframe Forums -> CA Products
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
galdino dos santos lima

New User


Joined: 22 Jan 2008
Posts: 5
Location: rio de janeiro, brasil

PostPosted: Tue Jan 29, 2008 6:04 pm
Reply with quote

Hi! I have a problem that i think is singular. When, using ENDEVOR, anyone makes the linkage of a module that calls another module with resides in a PDS with TTR greater than A00000, the job ends with a completion code 0C4. The module, itself, remains OK.
icon_redface.gif How you can easily see, my idiom is not the english, so, excuse the poor english and feel free to make any questions about the problem.
We are using z/OS 1.4 and the ENDEVOR is the 7.0.0
Back to top
View user's profile Send private message
enrico-sorichetti

Superior Member


Joined: 14 Mar 2007
Posts: 10872
Location: italy

PostPosted: Wed Jan 30, 2008 1:16 pm
Reply with quote

did You/Somebody compress the load dataset ???
Back to top
View user's profile Send private message
galdino dos santos lima

New User


Joined: 22 Jan 2008
Posts: 5
Location: rio de janeiro, brasil

PostPosted: Wed Jan 30, 2008 5:46 pm
Reply with quote

Yes. And this corrected the problem. Before this, I moved the called mod to other PDS, and this work too. But, I think that is not normal. Somebody already saw this before?
Thanks a lot for your attention.
Back to top
View user's profile Send private message
enrico-sorichetti

Superior Member


Joined: 14 Mar 2007
Posts: 10872
Location: italy

PostPosted: Wed Jan 30, 2008 5:52 pm
Reply with quote

it' s normal to get this error when using any tool for the optimization of directory searches ( LLA - like )

these tools keep track of the TTR of the modules/members requested, in order,
for the subsequent request to skip the directory search

to avoid the problem after compressing a dataset under LLA control it is enough
to issue a F LLA,refresh

check the docs on how to refresh only one library
Back to top
View user's profile Send private message
galdino dos santos lima

New User


Joined: 22 Jan 2008
Posts: 5
Location: rio de janeiro, brasil

PostPosted: Wed Jan 30, 2008 7:25 pm
Reply with quote

I think that I did not explain well. It´s not a dynamic CALL. The called mod is being incoporated to the program. And the involved archive is not in the LLA. The abend occurs after the new load module is write in the PDS.
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Wed Jan 30, 2008 10:59 pm
Reply with quote

Hello,

Quote:
The abend occurs after the new load module is write in the PDS.
When the new load module is written to the pds, it is assigned a new TTR. Sounds like "Something" is remembering the "old" TTR and causing the problem.
Back to top
View user's profile Send private message
galdino dos santos lima

New User


Joined: 22 Jan 2008
Posts: 5
Location: rio de janeiro, brasil

PostPosted: Wed Jan 30, 2008 11:47 pm
Reply with quote

Hi, dick scherrer. The abend not occur in the new module. The new program remains OK and can be executed without problem. The abend is in the ENDEVOR process. When, at linkage step, it calls a member with TTR greater than A00000 and incorporate it to the new module, the ENDEVOR abend 0C4. Thank you for the reply.
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Thu Jan 31, 2008 12:40 am
Reply with quote

You're welcome icon_smile.gif

I should have re-read the entire topic. . .

You might open a support issue with CA. They may already have a solution for this situation.
Back to top
View user's profile Send private message
galdino dos santos lima

New User


Joined: 22 Jan 2008
Posts: 5
Location: rio de janeiro, brasil

PostPosted: Thu Jan 31, 2008 4:40 pm
Reply with quote

I had the hope of somebody already had this problem here. The CA support is very slow, but seems that there is no choice to me. icon_sad.gif


Thanks a lot for your help icon_smile.gif
Back to top
View user's profile Send private message
Mistermind

New User


Joined: 08 Feb 2008
Posts: 46
Location: Dublin

PostPosted: Thu Mar 13, 2008 3:06 am
Reply with quote

Apart from producing the output loadmodule, Endevor also writes footprint info into 60 bytes of the user area in the output directory. I cannot remember the split for TTR, but it could be that use of TTR x'A00000' for data leaves insufficient room for Endevor to write its footprint. You could go into Endevor and compare the footprints of one good loadmodule and the one which produced 0C4. That 0C4 although it does not hamper program execution, could set up problems for you later, as Endevor is eternally helpful and vigilant, sometimes over zealous in its audit and warning.

Can you afford to enlarge your output PDS, so that the ceiling is not so easily reached and the Endevor problem is avoided?
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> CA Products

 


Similar Topics
Topic Forum Replies
No new posts Error while running web tool kit REXX... CLIST & REXX 5
No new posts Call program, directly from panel CLIST & REXX 9
No new posts Batch call online program, EXCI task ... CICS 3
No new posts CSQBGET - Call giving completion code... COBOL Programming 3
No new posts USECOUNT greater ZERO CICS 1
Search our Forums:

Back to Top