× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



It's very strange : it works and after CHGPGM FRCCRT(*YES), CHKOBJITG
doesn't signal violation ! (Lvl 30 of course).

My problem now is to do it programatically. I found that this 'Module
Literal Pool Component' is part of the 3rd "segment" (I did my test  with
only one module, maybe there are more than 3 segments with more modules ?
I'll see later ...).
But how to touch this 3rd segment. Is counterfeited pointer the only way ?

TIA

Penasse Jean-Michel
EXPERIA Europe
www.experia.com



-----Message d'origine-----
De : mi400-bounces@xxxxxxxxxxxx [mailto:mi400-bounces@xxxxxxxxxxxx]De la
part de Gene_Gaunt@xxxxxxxxxxxxxxx
Envoye : mardi 13 avril 2004 14:23
A : MI Programming on the AS400 / iSeries
Objet : RE: [MI400] RE: Changing *module "LITERAL POOL"



Instead of running CRTPGM over an altered *MODULE only to face MCH42B0,
running CHGPGM FRCCRT(*YES) over an altered observable *PGM with altered
literal pool seems to work okay.

_______________________________________________
This is the MI Programming on the AS400 / iSeries (MI400) mailing list
To post a message email: MI400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mi400
or email: MI400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mi400.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.