RE: How to retrieve current OS400 targt release

If you use QSZRTVPR use format PRDI0100 with product id *OPSYS, release
level *CUR, load id *CODE and product option "0000".  This will return
the current system's OS level regardless of LPAR you are running on.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
ganeshkumar.murugesan@xxxxxxxxx
Sent: Thursday, May 19, 2005 9:39 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: How to retrieve current OS400 targt release



Thanks for the information. But I can't trust the creation date of QCMD.


So I would better use some other known objects which would be created
inside the program, where I need this information.

BTW, I tried using QTEMP *LIB and unfortunately I didn't get any value
for the SYSVAL. Don't know why !!!!


-----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.