Easy,

Just do a RTVOBJD of QSYS/QCMD  *PGM and look at the SYSLVL return value. It's 
a 9-position CL variable that contains V03R02M00 (or whatever your OS level 
is).  The nice thing is, you can depend on QCMD always being there...

Bob Cozzi



> -----Original Message-----
> From: mcsnet!midrange.com!midrange-l-owner@Mcs.Net
> [SMTP:mcsnet!midrange.com!midrange-l-owner@Mcs.Net]On Behalf Of Denis
> Robitaille
> Sent: Tuesday, December 02, 1997 8:29 AM
> To: MIDRANGE-L@midrange.com
> Subject: Retreiving OS version
> 
> 
> Is there an easy way to retreive, inside a CL, the version of the OS 
> (v3r2m0, v4r1m0 ...)?
>  I would like a solution that work from version v3r2m0 and up. I 
> tried looking at the system values but there is none that i could see.
> 
> Denis Robitaille
> Cascades Inc.
>                                                                       
>                                                                       
>                                                                       
>                                                                       
>                                                                       
>                                                                       
>                                                                       
>                                                                       
>              
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
> | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: david@midrange.com
> +---
> uucp
> 

winmail.dat


This thread ...

Replies:

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

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