Hawkeye Mass Compile

210 pts.
Tags:
*SRCDBG
COBOL
CRTCBLPGM
Hawkeye
How close do other change management products keep COBOL compile parms for CRTCBLPGM, CRTBDNCBL when replacing an object? Have looked at Hawkeye's Mass Compile but had to tell them a while back they were not keeping the Activation group was defaulting to QILE even if the object it was replacing was something different. Also currently Parms like.....

OPM...Source listing options.......: *SRCDBG goes to*SOURCE after mass compile  

ILE......Debug view........: *SOURCE goes to *STMT after mass compile.   

Just curious is this normal or do other change management do better?       



Software/Hardware used:
Hawkeye

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Discuss This Question: 11  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta
    How close do other change management products... Hawkeye wouldn't have come to mind if you asked me to list "change management products" for the AS/400 line. I guess it technically fits in there though. For me, that simply isn't the purpose of the product. Maybe that's only because I haven't been exposed to it in recent years, but I haven't seen it included in anyone else's list of CMSes either. Tom
    125,585 pointsBadges:
    report
  • BeanBaggs
    Ok yes, I wouldn't consider it a change managment product (more analysis), but they do have a mass compile that is suppose to copy the properties of the object that it is overlaying. I have notice properties with COBOL programs don't always work(not up to date), so was curious how other products that are true change management products do with this?
    210 pointsBadges:
    report
  • TomLiotta
    ...they do have a mass compile that is suppose to copy the properties of the object that it is overlaying. If the product documentation says it's "suppose to copy the properties" when recompiling, then the vendor should explain to you why it's not happening. It might be a configuration element somewhere in the product or there might be a fix you can download and apply. As for other CMS products, I can't say -- mostly because it doesn't seem to quite match up with how such a product is normally used. I've written some functions in the past that retrieve object attributes in order to recreate them with the same attributes later, but those were always for personal use outside of any CMS. When working in a CMS, attributes of objects have always been explicitly entered or retrieved and stored into the CMS before attempting compiles for production. Technically I haven't ever seen an option like a "mass recompile" in use in the sense that you seem to be using it. It seems a little contradictory to a CMS philosophy. It implies that attributes may be changed outside of the CMS, and the CMS should then use whatever was on the objects rather than use the configured settings from the CMS product's database. Now, I've definitely seen where a CMS will import settings from one release of an application into a definition of a new release of that application, and the new release is then initially created by the CMS product. And I've seen imports from existing objects during initial setup. But I might be misunderstanding the whole question. I'm also hoping someone else will add some comment here. I've just been trying to keep the issue visible to others. Maybe what you need is just a basic RECRTCBL command. Tom
    125,585 pointsBadges:
    report
  • BeanBaggs
    Well the COBOL object attributes I was wondering about, they can't see so can't recompile the object as is. I would have to manually select them each time or make them the default. No need to discuss any further. I was just wondering how do I get someone to compile the COBOL program with same attributes I compiled with. I would use the COBOL PROCESS statment (similar to RPG H-SPEC) in the program, but it doesn't have certain attributes that you can set.(COBOL always Lags behind). So I was just seeing what other people do in this situation, thought CMS handled this better but maybe not? Never used one so not for sure?
    210 pointsBadges:
    report
  • TomLiotta
    Never used one so not for sure? A question for me? I've used Aldon, TurnOver and Implementer on AS/400s for COBOL; so I've used a reasonable variety. I used HawkEye quite a few years ago for its application xref capabilities, but it's been long enough not to be decently familiar anymore. ...the COBOL object attributes I was wondering about, they can’t see... Can you provide them here? There's always a chance of a bright idea that might come from anyone. Tom
    125,585 pointsBadges:
    report
  • NickHutcheson1
    Pathfinder's Hawkeye package is generally NOT considered a Change Management System. It is a cross reference utility that can even show you where a field is used in all files in all libraries(depending on how you set up the Document library list and Source library list). It does have a Mass Compile option which, as you find objects that need to be recreated due to a (example) field change, can add the file name to a compile list entry. When Mass Compile is selected, the software will build a list of all related (Logical) files, and programs that use any of the files. It will pull in and keep (behind the scenes) the create options that it has found. Note: It does have trouble finding references to /copy source. I never could get that to work as well as I wanted. Now, with that, I defend Hawkeye. If you can not programatically find options on how an object was created, how can they? And, none of the Mass Compile processes, to me, relates to any true CMS I have ever seen. Let's don't confuse the two. So, If you know how a cobol or any object should be created and cannot change it on the final create object (parameters screen of the Mass Compile), flag the objects with special create parms as Exclude(or let Hawkeye create them so you can roll changes back if your MC fails) and include your own user exit program within the MC command options, to create the objects the way you need them. Or you can run the MC command within a clp and then run your own create program for the special attributes. I hope I didn't sound too harsh. I just think the apples go in the apple basket and oranges go in the orange basket.
    1,380 pointsBadges:
    report
  • TomLiotta
    If you can not programatically find options on how an object was created, how can they? That's where I get confused, too. I'd like a couple specific examples just to know where the trouble comes in. Tom
    125,585 pointsBadges:
    report
  • NickHutcheson1
    Back to the original question: OPM...Source listing options.......: *SRCDBG goes to*SOURCE after mass compile ILE......Debug view........: *SOURCE goes to *STMT after mass compile. I think, he is refering to compile options (F4). Can all of these be seen on the object atributes or through some API?
    1,380 pointsBadges:
    report
  • BeanBaggs
    Nick, Agree with you that Hawkeye is just a cross reference utility. Should of not mention Hawkeye at all in question would of been easier. Just wondering how change management systems do with recompiling an object pulling in the compile options of the old object, so it gets compiled the same way. Like if old object had ACTGRP = PAYROLL some other programmer recompiles it and takes default ACTGRP=QILE. Or with the options I mentioned in my original question, which might be more on IBM not management product. Just wondering how others handle this since things like ACTGRP are not in PROCESS statement of COBOL program yet(V7R1)?
    210 pointsBadges:
    report
  • TomLiotta
    ...if old object had ACTGRP = PAYROLL some other programmer recompiles it and takes default ACTGRP=QILE. Activation group is easily retrieved along with most attributes with the Retrieve Program Information (QCLRPGMI) API. But debug settings seem to take more effort, especially if both OPM and ILE programs are involved. And note that ILE "programs" aren't compiled -- modules are compiled and then bound into programs. ILE programs don't have debug settings; the settings may be different for each module in a program. I've never needed to retrieve debug settings, so I'm doing some research and experimenting (...which must wait for off-work hours.) If I learn anything useful, I'll post what might help. Two generic workarounds come to mind -- set defaults that would always be used by any "mass compile" command/process or feed the desired settings into the command/process every time a "mass compile" is done. Until I have more info, or until someone else who's done it posts info, workarounds are about the only choice. Tom
    125,585 pointsBadges:
    report
  • BeanBaggs
    Tom don't worry about looking any farther into not a big deal.
    210 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following