|
rob wrote:
The attributes on CHGIPLA are only good for the next IPL. Is there some where to make something more permanent, short of changing QSTRUP? On my HA target machine I'd like to do a permanent CHGIPLA STRPRTWTR(*NO)
Rob:(Late response due to the hurricane-that-wasn't-one hit here a week ago...)
My startup programs have "exit" points where they pull commands from CL members. I can place commands in members that get processed at the beginning of, end of or anywhere inside of the startup.
If that's a standard, then you should be able to stick CHGIPLA STRPRTWTR(*NO) into the ENDSTRUP member and simply leave it there permanently on that box. Then, every time the box IPLs, the last thing it will do is reset that attribute to *NO.
Or you could add another auto-start entry to QCTL. That's really about all that the current default system startup is after work management, etc., get going. The default auto-start entry names job description QSTRUPJD which has CALL QSYS/QWDAJPGM for its request data. AFAIK, about all that QWDAJPGM does is to retrieve the QSTRUPPGM system value and call whatever program is named there. (I suppose it also does a few things such as reset CHGIPLA attributes.)
So add your own entry that waits until the startup job finishes and then does CHGIPLA. That results in the same as the previous possibility. Naturally, you could have a data area that's in control if you wish.
Customizing the system startup opens possibilities. Tom Liotta
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.
midrange.com
