|
I found the DTAARA on my V3R2 system. Bryan Dietz 3X Corp. "Al Barsa, Jr." <barsa2@ibm.net> on 12/03/97 07:23:57 PM Please respond to MIDRANGE-L@midrange.com To: MIDRANGE-L@midrange.com cc: Butch Maxwell <mmaxwell@us.ibm.com>, cegan@us.ibm.com, Carol Woodbury <cjw@us.ibm.com>, "cminer@vnet.ibm.com" <cminer@vnet.ibm.com>, jcstupca@vnet.ibm.com, debbies@rchvmw2.vnet.ibm.com, millerdr@us.ibm.com, bains@us.ibm.com, fsoltis@us.ibm.com, "glennel@VNET.IBM.COM" <glennel@vnet.ibm.com>, vanos@vnet.ibm.com, jchk@us.ibm.com, "Ransom, Julie" <jaransom@vnet.ibm.com>, "jheidelberg@vnet.IBM.COM" <jheidelberg@vnet.ibm.com>, "claeys@VNET.IBM.COM" <claeys@vnet.ibm.com>, pmattson@rchvmw3.vnet.ibm.com, pkincz@vnet.ibm.com, tjbird@us.ibm.com, wwatts@us1.ibm.com (bcc: Bryan Dietz/Columbus/3X Corp) Subject: RE: Retrieving OS version At 12:51 PM 12/2/97 -0600, you wrote: >>>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. >> >> >>0001.00 PGM >>0002.00 DCL VAR(&APIPARMLEN) TYPE(*CHAR) LEN(4) >>0003.00 DCL VAR(&APIPARM) TYPE(*CHAR) LEN(1000) >>0004.00 DCL VAR(&APIERRCDE) TYPE(*CHAR) LEN(4) >>0005.00 DCL VAR(&PRDINF) TYPE(*CHAR) LEN(27) + >>0006.00 VALUE('*OPSYS *CUR 0000*CODE ') >>0007.00 DCL VAR(&VRM) TYPE(*CHAR) LEN(6) >>0008.00 >>0009.00 CHGVAR VAR(%BIN(&APIPARMLEN 1 4)) VALUE(1000) >>0010.00 CHGVAR VAR(%BIN(&APIERRCDE 1 4)) VALUE(0) >>0011.00 >>0012.00 CALL PGM(QSZRTVPR) PARM(&APIPARM &APIPARMLEN + >>0013.00 PRDR0100 &PRDINF &APIERRCDE) >>0014.00 CHGVAR VAR(&VRM) VALUE(%SST(&APIPARM 20 6)) >> >> >>Hope this helps. >> Then someone wrote: > > >There is a data area in library QUSRSYS called QSS1MRI (at least there is in >V3R7M0) that contains the version information in the first 6 positions. A >previous release (V2R3?) had it in a different data area (Q5738SS1, not sure >if it was in the same library). I'm not sure why IBM changed the name of the data area, but if IBM did it, it must have been for a good reason <bg>! > Well, this really sucks. QSS1MRI was withdrawn some releases ago (that lovely V3R1 I think), and many of us bitched about it. At the time we were given the TOTALLY @#$%ing BULLSHIT answer that the data area was too much trouble to maintain. So many of us started writing to this API (which is about as easy to get into as Sadam Hussain's main palace). Then the data area gets put back. This note is the first I've heard it's been put back. IBM, please be honest in the future. If you take out easy to use function, and then put it back, please tell us. Al Al Barsa, Jr. - Account for Midrange-L Barsa Consulting, LLC. 400 > 390 Phone: 914-251-9400 Fax: 914-251-9406 Private mail should be sent to barsa@ibm.net +--- | 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 +--- +--- | 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 +---
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.