On 06-Jan-2016 19:20 -0700, rob wrote:
If it was strictly for compatibility (compiling to n-1 or n-2) then
the command should be in the appropriate QSYSN-1 library.

Yet that would ignore the existence of a /rule/ [convention], that a command must be removed only after what is deemed a sufficient warning. The assumption that all source and binary code will [have been coded or will default to] operate with Target Release (TGTRLS) specification of *PRV is no less troubling to those who would be affected indirectly; their time is no less valuable than others more directly impacted.


Interesting concept of virtualizing it. I think you'd play heck
getting anyone to place money on that marker though.

Considering the biggest investments in that infrastructure were by businesses already committing many millions of dollars to mainframe hardware...

p.s. I still am having troubles posting, per messages ending up in the infamous bit-bucket, but only for specific message thread(s); presumably this one will post.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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.