Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Compiler listing in Endevor Browse Panel

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> CA Products
View previous topic :: :: View next topic  
Author Message
jvivek88

New User


Joined: 25 May 2011
Posts: 3
Location: India

PostPosted: Sat Jul 09, 2011 1:16 pm    Post subject: Compiler listing in Endevor Browse Panel
Reply with quote

In the Endevor element DISPLAY panel, usually prefixing 'LL' (List Listing) before the element displays the compiler listing of that element. But I am getting the error 'MEMBER NOT FOUND' for a few elements when I specify 'LL' before them. I am not getting this message for all the elements; only for some of them.

But when I use the FOOTPRINT option, I get the listing for all the elements. I need to know the difference between these 2 options.. both the options extract the listings from the same list library, don't they?

I am just curious to know how the 'LL' command fetches the listing. Is there any way to make the LL option work properly, as it seems to be easier than typing the list library data set each time in the footprint option?
Back to top
View user's profile Send private message

Bill Woodger

DFSORT Moderator


Joined: 09 Mar 2011
Posts: 7315

PostPosted: Sat Jul 09, 2011 1:40 pm    Post subject: Reply to: Compiler listing in Endevor Browse Panel
Reply with quote

Maybe the listing for those modules is not in Endevor?
Back to top
View user's profile Send private message
dbzTHEdinosauer

Global Moderator


Joined: 20 Oct 2006
Posts: 6967
Location: porcelain throne

PostPosted: Sat Jul 09, 2011 2:20 pm    Post subject:
Reply with quote

well, maybe the default listing library dataset for the DISPLAY panel (where you enter LL) does not contain all the members that you are looking for.

maybe you can demand that endevor be setup so that all possible library datasets are automatically concatentated for every panel.

upps! forgot, you can not concatenate vsam datasets.

and there is the other point. if you are forced to enter the library dsn, at least you know what you are looking at.
Back to top
View user's profile Send private message
jvivek88

New User


Joined: 25 May 2011
Posts: 3
Location: India

PostPosted: Sat Jul 09, 2011 11:49 pm    Post subject:
Reply with quote

dbzTHEdinosauer wrote:
well, maybe the default listing library dataset for the DISPLAY panel (where you enter LL) does not contain all the members that you are looking for.


Is there any way to find out what's exactly the default listing library data set for the DISPLAY panel? I want to find out whether its the same dsn which we enter in the FOOTPRINT panel.
Back to top
View user's profile Send private message
dbzTHEdinosauer

Global Moderator


Joined: 20 Oct 2006
Posts: 6967
Location: porcelain throne

PostPosted: Sun Jul 10, 2011 1:39 am    Post subject:
Reply with quote

jvivek88,

you either talk to your support people and ask them,
or start going thru the panels, clists, and rexx scripts that drive your sites' endevor product.

my site has 2 levels each with 4 components:
PROD, ACPT, SYST, UNIT
LG1/LG2/LG3/LG4

since I have 8 libraries to deal with, I always use the footprint menu.
changing the DISPLAY menu would require outside of display menu activity - maybe defaults?

in DISPLAY menu, you can use the 'BUILD USING MAP' option,
along with wildcards '*' in the Stage or Leg portion,
means the DISPLAY panel displays the same module in different stages.
yeah, the 'B' for browse/view
will access the correct cobol source for the stage/leg selected,
but that is only 1 vsam file for all the cobol sources,
whereas the listings are keeping in separate vsams, one for each environment.

by the way,
i changed my default for browse to be VIEW,
wrote an edit macro that modifies the source to be left justified and only 80 chars
which allows me to
  • copy/create to my own pds
  • use my edit macros for analyzing Source files
.

i suggest that you live with it.
Do not think you will be able to change the default
but I never needed to, so I don't know how.

Most of the time, I only need to see listings when I have a pre-compile/compile/link error
and then it is in SDSF.
Back to top
View user's profile Send private message
jvivek88

New User


Joined: 25 May 2011
Posts: 3
Location: India

PostPosted: Sun Jul 10, 2011 5:32 pm    Post subject:
Reply with quote

dbzTHEdinosauer,

Thanks a lot for your detailed explanation. I only need to see the listings so that I could have the copybooks expanded while browsing an element.
I found this in the Endevor User Guide:

"The Listing Dataset String field is initially set to the value found in the Default Configuration Table (ENDICNFG) COMPONENT_LIST_WORD field. If the value of this field is blank, the Listing Dataset String field is set to a default value of "LIST". If you modify the Listing Dataset String field, the value you specified will remain until you modify it to another value or you clear the value, in which case the field is initialized again."

I probably won't have access to the COMPONENT_LIST_WORD field.
As you suggested, I will have to learn to live with it.
Back to top
View user's profile Send private message
dbzTHEdinosauer

Global Moderator


Joined: 20 Oct 2006
Posts: 6967
Location: porcelain throne

PostPosted: Sun Jul 10, 2011 6:44 pm    Post subject:
Reply with quote

our setup has 'outside of endevor' pds's populated with
copybooks for every level
cobol source for production only.

the only way to get at the different versions/levels of cobol source
is thru the endevor display panel.

because copybooks are pds'd at every level, i have
PROD/LG1 copybooks pds
ACPT/LG1 copybooks pds
SYST/lg1 copybooks pds
UNIT/LG1 copybooks pds
(as well as the lg2/3/4 versions).

this allows me to utilitize ISPF macros to access these different PDS's
and expand my source at the level I wish.

but that does not answer you question of which copybook was used for the compile.
unfortunately for that, you need the compile listing.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> CA Products All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts CA-Endevor Admin - 3 years minimum vasanthz Mainframe Jobs 0 Tue Apr 04, 2017 5:36 am
No new posts CICS Question RE: Browse, Readnext an... moezbud CICS 7 Sun Mar 05, 2017 5:45 am
No new posts ISPF - How to come out of ISPF Panel parasmalik20 TSO/ISPF 5 Tue Feb 21, 2017 7:44 pm
No new posts the use of 'B3'x character in a panel Pedro TSO/ISPF 1 Thu Feb 16, 2017 3:09 am
No new posts Who can recomend or to know a PL1 com... Miguel Fernandez DB2 0 Tue Feb 14, 2017 1:42 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us