Talk:TSS (operating system)

message: Also, there was nothing unusual about providing all the source code to customers.  That was standard until IBM started shipping OCO (object code only) in the 1980s. John L 23:51, 16 September 2007 (UTC)
thread_title: Providing source code to customers

message: TSS/360 was succeeded by the TSS/370 PRPQ, which went through several releases. Given that, it's misleading to state that TSS/360 was withdrawn in 1971. Shmuel (Seymour J.) Metz Username:Chatul (talk) 18:55, 16 August 2010 (UTC)
thread_title:  Le roi est morte, vive le roi 

message: TSS/360 did not have a GUI. How do you take a screen shot of, e.g., a 2741? Shmuel (Seymour J.) Metz Username:Chatul (talk) 14:56, 29 October 2010 (UTC)
replies: text: With a digital camera, or with an analog camera and a scanner. :-)  Whether it's useful to show, in the article, a photograph of a printout of a session on a 2741 is another matter. Guy Harris (talk) 07:32, 2 November 2010 (UTC)
replies: text: It might even be useful, but it wouldn't be a screen shot. Shmuel (Seymour J.) Metz Username:Chatul (talk) 11:01, 4 November 2010 (UTC)
replies: text: It would not, in the literal sense, be a screen shot, as there's no screen.  However, as a representation of the user interface, it could be considered to serve the same purpose as a screen shot; perhaps the name should be changed to something other than "screen shot", but I don't see any argument for not having an image of a printing-terminal session, especially given that there are "screenshots" of applications that run in, for example, a UN*X terminal session, such as tcpdump - yes, that image happens to have been taken as a screenshot from a terminal emulator program, but it's not inherently that different from an image of a printout. Guy Harris (talk) 22:31, 4 November 2010 (UTC)
replies: text: When what you're dealing with is text, converting it to an image would be counterproductive. If you look at the example in, e.g., Coroutine#Comparison with subroutines, the sample code is much more appropriate than an embedded image of it would be. I posted a query at the help desk  Shmuel (Seymour J.) Metz Username:Chatul (talk) 23:09, 4 November 2010 (UTC)
thread_title:  Screen shot? Not applicable, 

message: The article says "TSS/360 was unique in implementing a Table Driven Scheduler."  I'm not familiar enough with either system, but is this similar to (or same as) what was later done in the OS/390 Workload Manager?  If so it might be worth a mention as another concept that originated with TSS.  Actually, I think SDS/XDS Sigma UTS had a table-driven scheduler, but that would have been later.  I seem to recall Xerox pushing the advantages of the scheduler. Peter Flass (talk) 14:55, 30 November 2012 (UTC)
thread_title:  Scheduler 

message: I wrote that TSS had "an early version" of PIC; was it the first or were there earlier? Peter Flass (talk) 14:46, 3 May 2015 (UTC)
replies: text: Multics; the implementation was very different and involved linkage segments. In TSS an external reference in a PSECT is resolved when the module is loaded; in Multics an external reference in a linkage segment is resolved only when the module attempts to call the external routine. Shmuel (Seymour J.) Metz Username:Chatul (talk) 14:56, 26 May 2015 (UTC)
replies: text: It occurs to me that MCP on the Burroughs B5000 is arguably the first to have PIC. Shmuel (Seymour J.) Metz Username:Chatul (talk) 16:49, 4 March 2019 (UTC)
thread_title:  Position-independent code