I would agree with regard to brand new code that became the essence of MVS, eg storage management and the paging subsystem. But there was a lot of MVT that was included pretty much as-is. Conversion of such to PL/S was for the sake of appearance only.
Sent from my iPhone > On Sep 5, 2016, at 11:35, Mike Myers <[email protected]> wrote: > > Not true. As the technical team leader for the development of the paging > subsystem for the first release of MVS, I can attest that most of ASM, RSM > and VSM were written in PL/S (with a few exceptions). For the most part, the > GENERATE/ENDGEN approach was used for the inclusion of instructions that the > compiler would not generate (like PTLB). > > Mike Myers > z.OS systems programmer and consultant > Mentor Services Corporation > >> On 09/03/2016 09:03 PM, J R wrote: >> That may not reliably indicate "size" in lines of PL/S code. As I recall, >> the vast majority of modules were migrated to PL/S by simply wrapping them >> in the equivalent of: >> PROC >> GENERATE >> <original assembler source> >> ENDGEN >> END >> >> >> Sent from my iPhone >> >>> On Sep 3, 2016, at 20:35, Rob Schramm <[email protected]> wrote: >>> >>> Maybe lines of PL/s code?? >>> >>> Rob Schramm >>> >>>> On Sat, Sep 3, 2016, 5:22 PM Mick Graley <[email protected]> wrote: >>>> >>>> I think we're comparing apples and oranges here though. S/370 >>>> assembler (you said original MVS) ¬= C/C++ lines of code or generated >>>> object (machine) code. >>>> Cheers, >>>> Mick. > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
