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

Diff between Panvalet and Endevor


IBM Mainframe Forums -> CA Products
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
sree_vanteru

New User


Joined: 06 Dec 2006
Posts: 2
Location: San Francisco

PostPosted: Wed Dec 06, 2006 10:41 am
Reply with quote

Could some please let me know what is the major difference between Panvalet and Endevor, eventhough both are configuration management tools.
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: Sat Dec 16, 2006 12:08 am
Reply with quote

Hello,

Panvelet is primarily a text editor.

Endevor is a configuration/change management tool.


If you go to the CA web site, there is information on both. Here is the first bit from each product page. . .

Panvelet features
Easily change and display member attributes
All or part of a CA-Panvalet members can be displayed
Member LOCK and UNLOCK commands are supported
TSO-submitted batch jobs referencing TSO-formatted members supported
Record lengths up to 4096 bytes are supported


Endevor features
Accelerated software development life cycles
Automated, package-based change management
Automated approvals provide greater control and efficiency
Maximum application integrity
Robust security for software components
Back to top
View user's profile Send private message
sree_vanteru

New User


Joined: 06 Dec 2006
Posts: 2
Location: San Francisco

PostPosted: Sat Dec 16, 2006 12:26 am
Reply with quote

Thanks a lot.
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: Sat Dec 16, 2006 1:07 am
Reply with quote

You're welcome.

d
Back to top
View user's profile Send private message
Jwala Vattikonda

New User


Joined: 02 Dec 2006
Posts: 5
Location: Hyderabad

PostPosted: Tue Jan 02, 2007 10:53 pm
Reply with quote

hi..

Suppose that I am using Panvalet.

I am using static linking in the programs.
So.. i have few includes or subroutines cahnged. And i manually edit program to use Testversions of which ever i want. But its a tedious task for me to always check what are other elements impacted with the change of one element and recompiling them, then edit each elemnt which uses my changed include to pick new version and compile it again. And in panvalet its manual renaming of elemnts.. its again that i have to check what should be renamed, and i should rename all carefully. Can this be automised .. or its better to go to Endeavour to solve this? Is it possible that i do till unit testing in Panvalet and then move the things to Endeavour? Is it costly to use Endeavour?
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: Tue Jan 02, 2007 11:43 pm
Reply with quote

Hello,

One way to accomplish this kind of testing is to have a separate load library for test modules. When you make changes, the newly compiled modifications are linkedited into the test library.

When you run your batch programs, use a STEPLIB dd and place your test load library as the first library in the steplib concatenation.

If i understand what you need, it is not a Panvalet/Endevor question, but a general testing problem.

If you must use static calls, compile/link any changed called modules into the test load library first. Then compile any calling programs and make sure your test library is included at the head of the libraries to use for link editing.

One other thought is that if module names are changed for testing, once the testing is successful, the names have to be changed back to the "real" names. Now everything has to be re-compiled and Ta Daa - they are no longer tested code. A simple editing error could cause your "promotion" of those modules to have problems or completely fail.

If you use the test library/prod library approach, the promotion process includes moving the new modules out of the test library and into the production library.

Again, this is not simply choosing between Panvalet and Endevor, but is more a question of how to deal with modifications to an existing environment.
Back to top
View user's profile Send private message
Jwala Vattikonda

New User


Joined: 02 Dec 2006
Posts: 5
Location: Hyderabad

PostPosted: Sat Jan 06, 2007 11:05 am
Reply with quote

thnak you for the reply..

what is said is correct.. but i do the same way.imean seperate load library for test modules..
the problem i am speaking is about.. impacted elements.. if one element ic chaned, othe progrma impacted by that include or subroutine should be relinked..and.. if its an include which is changed, all the programs using it needs to be edited to pick test version of that include and relinked. when that include moves to other environment , again impacted elements should be relinked in that environment.Can this be automised?
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: Sat Jan 06, 2007 11:37 pm
Reply with quote

Hello,

I'm not sure i completely understand, but if the environment is set up to scan the test library before the production library, there should be NO changes in the code to pick between the test and production module name. Both will be the SAME name.

Regardless of what code is "included", the executable module name should be the same. If a copybook or other included piece of code is changed, the name of the new/modified components may be changed (for the "next" version, but overall the executable names will remain the same.

Going a little further, once the application has been promoted to production status, you may want 3 "sets" of executables. One is the production, one is for modified modules that are in testing (and are NOT in the production jcl), and one for emergency repair (occasionally a program will fail or a user will be so bold as to suggest something is not working correctly and must be fixed iommediately<g>). ALL will have executables of the same names. The production repair library is placed before the main production load library in the production jcl so that a "repair" can be done with NO changes to the rest of the environment. Once the emergency is past, the fix is promoted in the normal process and that includes removing the module(s) from the repair library to the production library.

Before proceeding with a library strategy, PLEASE check with the folks who are responsible for configuration management and/or change control or whatever it is called in your organization.. What i just described is what ii've done for sites that had no formal procedures and were in a situation that required immediate response.

Of all of the module management processes i've seen, none change module names to accomodate changes or fixes.

As i said at the top, i may not compoletely understand so let me know if i need to clarify something. If you include an example of what you need to do, that will help with an explanation.
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 Panvalet - 9 Character name - Issue c... CA Products 6
No new posts Updating endevor JCLs CA Products 5
No new posts Sort on different fields, removing du... SYNCSORT 8
No new posts How syntax check at Bind time is diff... DB2 5
No new posts Finding the plan when code compiled u... DB2 2
Search our Forums:

Back to Top