|
I didn't see that *OPSYS method. I thought you had to do something stupid like 5722SS1, which will bite you in the ... when you jump versions of the OS. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Elvis Budimlic" <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 05/19/2005 11:45 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx> cc Subject RE: How to retrieve current OS400 targt release Rob's method works just fine. If you want IBM sanctioned method you should use QSZRTVPR api. PGM DCL &RELEASE *CHAR 6 DCL &RCVR *CHAR 128 DCL &RCVRLEN *CHAR 4 VALUE(X'00000080') DCL &FORMAT *CHAR 8 VALUE('PRDR0100') DCL &PRDINFO *CHAR 27 VALUE('*OPSYS *CUR 0000*CODE ') DCL &ERRCODE *CHAR 4 VALUE(X'00000000') CALL QSYS/QSZRTVPR PARM(&RCVR &RCVRLEN &FORMAT &PRDINFO &ERRCODE) CHGVAR &RELEASE (%SST(&RCVR 20 6)) SNDPGMMSG MSG('THIS SYSTEM IS AT RELEASE' |> &RELEASE) ENDPGM -----Original Message----- Subject: RE: How to retrieve current OS400 targt release Seems to be. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com <ganeshkumar.murugesan@xxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 05/19/2005 11:10 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To <midrange-l@xxxxxxxxxxxx> cc Subject RE: How to retrieve current OS400 targt release Do you mean that the object QCMD would be created every time when a new release is launched? Please advice. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx Sent: Thursday, May 19, 2005 9:36 PM To: Midrange Systems Technical Discussion Subject: Re: How to retrieve current OS400 targt release 1 - Adopt authority with your existing solution. 2 - RTVOBJD OBJ(QCMD) OBJTYPE(*PGM) SYSLVL(&SYSLVL) Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com <ganeshkumar.murugesan@xxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 05/19/2005 10:45 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To <midrange-l@xxxxxxxxxxxx> cc Subject How to retrieve current OS400 targt release I need to retrieve current OS400 target release level inside a CL program. Any ideas?? I tried using the WRKLICINF command, but I don't seem to have authority in all the AS400 boxes, where the program should be implemented. I can't trust the DSPLICKEY command also because it gives information about products not installed along with the products installed. Is there any other command or API that can be used?? Thanks, Ganesh Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or Mailadmin@xxxxxxxxx immediately and destroy all copies of this message and any attachments. -- 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 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. Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or Mailadmin@xxxxxxxxx immediately and destroy all copies of this message and any attachments. -- 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 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 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.
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.