# TSS/360

> 1960s era timesharing operating system for IBM mainframes; generally considered a failure, although was used by a small number of customers through the 1970s

**Wikidata**: [Q15956143](https://www.wikidata.org/wiki/Q15956143)  
**Wikipedia**: [English](https://en.wikipedia.org/wiki/TSS_(operating_system))  
**Source**: https://4ort.xyz/entity/tss-360

## Summary
TSS/360 is a 1960s-era timesharing operating system developed by IBM for the IBM System/360 mainframe family. It was published in 1967, was programmed in assembly language, and is generally considered a failure, though a small number of customers continued using it into the 1970s.

## Key Facts
- TSS/360 is an operating system designed for timesharing on IBM mainframes.  
- Developer: IBM.  
- Platform: IBM System/360.  
- Publication date: 1967.  
- Programming language: assembly language.  
- Instance of: operating system.  
- Common description: a 1960s-era timesharing operating system generally considered a failure.  
- Continued use: was used by a small number of customers through the 1970s.  
- Freebase ID: /m/0fz10v.  
- Wikipedia title: "TSS (operating system)"; available in en, ko, no (sitelink_count: 3).

## FAQs
### Q: What is TSS/360?
A: TSS/360 is a timesharing operating system for IBM System/360 mainframes, developed by IBM and published in 1967.

### Q: Was TSS/360 successful?
A: No. TSS/360 is generally considered a failure, although a small number of customers continued to use it into the 1970s.

### Q: What was TSS/360 written in?
A: TSS/360 was programmed in assembly language.

### Q: Which platform did TSS/360 target?
A: TSS/360 targeted the IBM System/360 mainframe platform.

## Why It Matters
TSS/360 is a notable historical example of an early timesharing operating system developed by a major vendor for a leading mainframe platform. As an IBM System/360 timesharing OS published in 1967, it represents the industry effort to bring interactive, multi-user computing to large-scale machines during the 1960s. Its reputation as a failure, coupled with continued niche use into the 1970s, illustrates the technical and market challenges of early timesharing system design as well as the persistence of certain customers with specific operational needs. Studying TSS/360 helps explain the evolution of mainframe operating systems, the role of assembly-language implementation in that era, and the risks vendors faced when introducing ambitious system software for new hardware families.

## Notable For
- Being a 1960s-era timesharing operating system specifically for the IBM System/360.  
- Published in 1967 and developed by IBM.  
- Implemented in assembly language.  
- Generally considered a failure despite continued use by a small number of customers into the 1970s.  
- Listed in reference systems (Freebase ID /m/0fz10v) and covered under the Wikipedia title "TSS (operating system)".

## Body

### Overview
- Name: TSS/360 (commonly referenced as TSS).  
- Role: Timesharing operating system for IBM mainframes.  
- Era: 1960s; published in 1967.  
- Reputation: Generally considered a failure in historical accounts.  
- Continued use: Small number of customers used it through the 1970s.

### Development and Publication
- Developer: IBM.  
- Publication date recorded as 1967.  
- Implemented in assembly language.

### Platform and Technical Details
- Target hardware platform: IBM System/360 mainframe family.  
- Programming language: assembly language (strong correspondence to machine instructions, consistent with low-level system software practices of the era).

### Reception and Usage
- The system is described as generally failing to meet expectations or achieve broad success.  
- Despite that assessment, some customers continued operational use into the 1970s.

### Related Systems
- Related entry: TSS-8, a 1968 operating system for the PDP-8 (listed as related in reference material).

### Identifiers and References
- Freebase ID: /m/0fz10v.  
- Wikipedia title: "TSS (operating system)".  
- Wikipedia language availability: English, Korean, Norwegian (sitelink_count: 3).