|
Al, Neil and Others: Remember, V3R1 when they added the new system calues QQRYDEGREE and QQRYTIMLMT? This was done by PTF. The system value space can easily support a couple of additional values! The problem with a data area is that it is not sacred. Adding this as a system value for both CISC and CISC boxes should have been done when the advanced series first came out. (IMHO) > ------------------------------ > > Date: Fri, 02 Jan 1998 13:20:31 -0500 > From: "Al Barsa, Jr." <barsa2@ibm.net> > Subject: Re: Data Area for Processor Model and Feature # > > At 06:11 AM 1/2/98 -0700, you wrote: > > I will proudly stand up and take credit for this. I have been screaming > since V3R1 that we needed a system value for the feature number. IBM's > response has consistently been 'no business requirement'. In a recent trip > to Rochester, I sat an IBM exec down at a workstation, with normal > authority (e.g.: not *ALLOBJ or *SERVICE), and showed how to get the feature. > > What I asked for was either a system value QFEATURE, or to allow you to > retrieve the feature by making the retrievable length of QMODEL either 4 > digits or optionally 8 digits (thus providing the feature). > > They indicated that you can't make a system value retrievable in different > lengths, so I pointed out QTIME and QIGCCDEFNT. Ah well, they settled on a > new system value in the release after next. (At that time, it was deemed > to be too late for the next release.) > > The data area is an interim solution, although I thought it was going into > QSYS or QUSRSYS. The name QPRCFEAT is as meaningful as #$%@, but this is > the way that the developer who responded with 'no business requirement' got > back at me. > > This is not a good solution to enforce software tiering, but there's an API > to do that. It is a good solution for when you (as a vendor) has to call > the system operator and say what software tier are you at? > > Does anyone know what V4R1M4 is about? > > Al > > > >There have been postings to the list in the past asking is there is a > >way to find the processor feature number. Well, until now there wasn't > >an easy way to find the processor feature. > >Now, with the required PTF's, you will find the information in a data > >area in QGPL.. Hopefully they will make this a read only system value in > >the future. > > > >Of course, if your plan was to use it in some way related to enforcing > >tiered pricing in your software, it's too easily changed for that ! > >Especially as it gets created with *PUBLIC *CHANGE authority. Shame, > >Shame IBM - should have been *PUBLIC *USE. Still, thanks anyway ! :-) > > > >PTF List: > > Release 320 : SF43978 available 97/10/22 (1000 ) > > Release 370 : SF44314 available 97/10/30 (1000 ) > > Release 410 : SF43981 available 97/10/21 (7308 ) > > Release 414 : SF45311 available 97/12/04 (1000 ) > > Release 420 : PTF not available yet > > > >======================================================================== > >= > > APAR Identifier ...... SA68233 Last Changed..97/12/04 > > OSP-UNPRED DATA AREA FOR SYSTEM PROCESSOR FEATURE CODE > > > > Symptom ...... DD DOC Status ........... CLOSED PER > > Severity ................... 2 Date Closed ......... 97/10/08 > > Component .......... 5769SS100 Duplicate of ........ > > Reported Release ......... 410 Fixed Release ............ 999 > > Component Name 5769 BASE V4 Special Notice > > Current Target Date .. Flags > > SCP ................... OS/400 > > Platform ............ OS/400 > > > > Status Detail: SHIPMENT - Packaged solution is available for > > shipment. > > PTF List: > > Release 410 : SF43981 available 97/10/21 (7308 ) > > Release 414 : SF45311 available 97/12/04 (1000 ) > > Release 420 : PTF not available yet > > > > Parent APAR: SA68229 > > Child APAR list: > > > > ERROR DESCRIPTION: > > THIS APAR WAS SYSROUTED FROM R370 SA68229. > > THIS APAR WAS SYSROUTED FROM R320 SA68226. > > Today, there is not an easy way for the customer to determine > > the system processor feature. They can go thru SST, but these > > are not easy steps. There needs to be a data area created in > > QGPL called QPRCFEAT that will contain the Model and processor > > feature. > > > > PROBLEM CONCLUSION: > > The data area QGPL/QPRCFEAT containing the Model and processor > > feature will be created. > > > >... Neil Palmer AS/400~~~~~ > >... NxTrend Technology - Canada ____________ ___ ~ > >... Thornhill, Ontario, Canada |OOOOOOOOOO| ________ o|__||= > >... Phone: (905) 731-9000 x238 |__________|_|______|_|______) > >... Cell.: (416) 565-1682 x238 oo oo oo oo OOOo=o\ > >... Fax: (905) 731-9202 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > >... mailto:NPalmer@NxTrend.com http://www.NxTrend.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 > >+--- > > > > > > 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 > +--- > > ------------------------------ > > End of MIDRANGE-L Digest V2 #2 > ****************************** > > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * > * 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 MAJORDOMO@midrange.com and specify * > * 'unsubscribe MIDRANGE-L-DIGEST' in the body of your message. * > * Questions should be directed to the list owner / operator: * > * david@midrange.com * > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * > uucp +--- | 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-2025 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.
midrange.com
