|
Okay, now that I've upgraded to V5R1, I got rid of some of my old standby commands in my user system library. This included my special version of CRTBNDRPG, which had DFTACTGRP(*NO) specified. Now, I figured I could avoid this by simply specifying an ACTGRP(xxx) in my H spec, but the compiler bombs. Evidently the ACTGRP(xxx) keyword isn't enough to override the CRTBNDRPG's default setting of DFTACTGRP(*YES). This stinks. So, do I have to know ahead of time whether a program is meant to be in the activation group, and execute a different compile command (setting DFTACTGRP to either *YES or *NO) depending on how the program is meant to run? This seems to be a pain in the butt. If I go to the trouble of specifying the keyword in the H spec, you'd think that would override any defaults the compiler might have. Anyway, bottom line: do I have to go re-add my CRTBNDRPG command in PBDUTIL to have DFTACTGRP(*NO)? Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.