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.

-Walden

------------
Walden H Leverich III
President
Tech Software
(516)627-3800 x11
WaldenL@TechSoftInc.com
http://www.TechSoftInc.com



-----Original Message-----
From: Simon Coulter [mailto:shc@flybynight.com.au]
Sent: Tuesday, December 18, 2001 18:27
To: midrange-l@midrange.com
Subject: Re: Modify SYSVAL QSYSLIBL (Walden)



Hello Waden,

You wrote:
>And even then the command objects are normal command objects with two
differences.

>1) Service data at offset x31 shows V4R4M0 instead of V5R1M0 (on a V5R1
>machine)

>2) The SEPT entry for the command processing program is missing so
>normal object resolution would be used to find the CPP if you could
>call it. The second difference surprises me since I didn't think the
>SEPT could change between releases since SEPT entry numbers are
>hardcoded in programs so why bother blanking them out?

There is an additional difference:  The commands in the *PRV libraries have
an attribute indicating whether they are runnable or not.  For example

Restricted to CRTCLPGM for TGTRLS  . . :   V4R2M0

That's what causes the CPD0118 message.

Also, I'm not so sure that the SEPT cannot change but at 6500 entries it is
unlikely to change.  The SEPT in general is not an exposed interface,
although there are C includes QLIEPT and QLIEPTI that expose some of the
SEPT entries.  A cursory search through the documentation failed to find a
reference to these includes so I'm not sure how stable they are.

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  / \
--------------------------------------------------------------------

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


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2022 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.