|
John, Although there are a few objects in QSYS2 that follow the AS/400 naming convention (start with a Q followed by the component identifier of the development team) QSYS2 is historically for all those objects which did not follow the AS/400 naming convention, and therefore were not "allowed" into QSYS but were part of OS/400. These are primarily cross system interfaces (SAA APIs, DB2 tables/views, etc.) where changing the names to Qxxx would defeat the whole idea of cross platform portability. There have, over time, been a few exceptions allowed for QSYS and non-Q object names (like SUBRxx for S/36) but that doesn't change the original reason for QSYS2. Bruce > >1) What is the reason for QSYS2? I know what's in it, but >it isn't clear to me why it exists separately from QSYS. > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@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.