I don't know if you "own" the system or if you are an application running
on client systems, but the approach I've taken when having to run on an
arbitrary system is:

1. at install/upgrade time I check the defined controlling subsystem
(system value QCTLSBSD). I then look for "my" autostart job entry. If it's
not there I add it. The job started by the AJE then starts everything I
need started

2. at install/upgrade time I register an exit program to the CHGSYSVAL
command. If someone changes QCTLSBSD then I remove the AJE from the
original controlling subsystem and add the AJE to the new controlling

Using this approach I get what I need done done and don't have to worry
about monkeying with the client startup program.


On Mon, Aug 18, 2014 at 7:27 AM, <rob@xxxxxxxxx> wrote:

I am a wee bit reluctant to modify the start up programs. IBM does
occasionally change those. Sometimes quite drastically. I don't want to
get into a debate on the pros/cons of doing so. Nor be told to just "man
up" and do it. Nor do I want to get into a discussion over my definition
of "drastic".

What I really want to know is, are there any exit points for system start
up? Like before leaving restricted state, and after leaving restricted

Rob Berendt
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page