James--
I think the following includes most of what you need to do, but caveat emptor!
1) Ideally, you should have created a library that is positioned in
the System portion of the library list -before- QSYS. This is where
you keep things like your copy of system objects. This is where we
keep our subsystem descriptions, some JOBDs, and our copies of IBM
commands with our own defaults.
2) Make a copy of the subsystem description you plan to mutilate into
the library in #1. You should NOT change subsystem QCTL-- that's
your console and 'escape hatch.' And you should never change the
objects in the QSYS library directly.
3) If you look at the subsystem description for an interactive
subsystem (ie QINTER) the "Operational Attributes" screen shows a
display file name and its library:
CHGSBSD SGNDSPF(yourlib/yourfile). The display file should live
in the library in #1 as well.
4) Now you need to test the subsystem and make sure it works before
committing the entire system to it...
a) Make sure your interactive session is signed on in the QCTL
subsystem-- you want your job running in a subsystem unaffected by
your test-- somewhere so you can end the changed subsystem in case it
doesn't work!
b) STRSBS yourlib/yoursbsd
c) the new subsystem will take over the screeens defined in the
subsystem description. You should see them display your customized
display file
d) Sign on to one of the screens with the new signon screen--
make sure everything still works!
e) If it does NOT work, ENDSBS yourlib/yoursbsd. The signon
screens should revert to the standard screen, and show they are under
control of the original subsystem.
If it does work, change your procedures to start your new, modified
subsystem description, and ignore the original. But leave the
original around just in case. Plus, it's a 'plain vanilla' version
you can use should you need to make another customized subsystem.
I think that covers it... but your mileage may vary!
--Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx
At 10:36 PM -0600 12/31/08, James Newman, CDP wrote:
I finally took time and made one of those fancy-smancy sign on screens with
the company name and everything. It compiles fine. Now the only problem is
where the object module is supposed to go so the system can find it. Can
someone help me out? TIA.
midrange.com
