Re: Modify SYSVAL QSYSLIBL (Walden)

Hello Walden,

You wrote:
>I'd guess that it's the non-current VRM in the service data that triggers
>this display and error. If I get a change I'll hack a command and see
>what happens.

It's not the service data.  A command saved from an earlier release and
restored on a later release will show the old release in the service data
yet should still run on the later release.

I duplicated the DSPMSG command and started patching it using SST.
Setting the data at offset x'4CF' (which in a current command is
x'000000000000) to V4R2M0 caused DSPCMD to show it as restricted to
CRTCLPGM for TGTRLS.  However, the command was still runable.

So further playing:
Setting the data at offset x'140' (normally x'48') to x'60' results in the
CPD0118 message indicating the command cannot be run on the current
release.  To be strictly accurate, any value for this field that sets bit
2 will result in CPD0118.  I haven't deciphered the meaning of all the
other bits yet.

Leif! If you're watching you can include this stuff in a future chapter of
your MI e-book.

I also found the bits that control the state used to call the CPP.
Setting these to other (invalid) values has a number of interesting
effects when the command is invoked -- haha, I really should get a life --
typing hex values into an object to see what happens is the sign of a very
sick mind!

Regards,
Simon Coulter.

--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists
   http://www.flybynight.com.au/

   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175   mailto: shc@flybynight.com.au   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------