S**3: See Shared Stand-alone Storage.
S.M.A.R.T.: See SMART2.
S/390: See System/390.
S/3x0: Any or all of the System/390, 370 and 360 series. The complete set of IBM mainframes before the eserver zSeries 900 was announced October 3, 2000.
SA: IBM System Automation for OS/390. See System Automation.
SAA: Systems Application Architecture. Yet another architectural edifice from IBM – vintage March 1987. This one was designed to provide consistent interfaces across the products which conform to it. At its simplest, it meant that programs written to the SAA standards would run virtually unchanged on the mainframe, AS/400, and PS2/2. However, the real function of SAA was to provide an infrastructure for distributed and cooperative processing, and for presenting the most complex system as a single system image. The four pillars of SAA are CPI (Common Programming Interface), CUA1 (Common User Access), CCS1 (Common Communications Support), and Common Applications. It did a lot of good in helping IBM and the mainframe industry rationalize its product lines and standards, and has now been allowed to gently expire. Bringing REXX to z/OS was also a big benefit to anyone who ever had to use CLIST for anything beyond saving a set of TSO commands.
SAA-compliant: Products which can internetwork with SAA applications are SAA-compliant. SAA-compliant products include IMS DB, CICS, VSE/ESA. According to IBM (June 1989) an SAA compliant product must: run in SAA environments; conform with the CUA1; use the CPI; use the CCS1; be structured for cooperative processing. However, the concept became very much watered down, and was often used (although not by IBM) to mean runs on an IBM mainframe or has a CUA front-end. See also SAA-conformant.
SAA-conformant: Products whose internals are built according to SAA specifications are SAA-conformant. SAA-conformant products include DB2, CSP1, COBOL, C, RPG/400, FORTRAN. See also SAA-compliant.
SAA Delivery Manager: See Delivery Manager.
SAA Networking Services/2: IBM’s implementation of APPN for OS/2 environments – announced March 1991. Provides APPN network node (routing) and end-node (user) support. Withdrawn April 1993.
SAA Office: A widely used term for IBM’s set of office applications written around the SAA standards, which were designed to replace the mish-mash of ill-coordinated office facilities with a whole range of consistent, coherent, walk-up-and-use products. Announced in May 1989 as OfficeVision.
SAA Personal Application System/2: See Personal Application System.
SAD: System Activity Display. Special display on mainframe system consoles providing dynamic details of processor activity.
SAF1: Security Access Facility (sometimes System Authorization Facility). IBM’s security interface within SAA. Used by various subsystems, including CICS.
SAF2: System Authorization Facility. A z/OS access control interface that that software can call to use system authorization services in order to protect access to resources without having to know which security software (RACF or a non-IBM product) is installed.
Salmon: The code name for the IBM PC/AT.
Salutation: Consortium (originally called SmartOffice) set up by IBM at the beginning of 1995 to develop and promote standards for connecting office equipment. The Salutation Specification (formerly known as the Smartlink architecture) is the consortium’s architecture (APIs and exchange protocols) for connecting photocopiers, PDAs, computers, fax machines, and the like.
SAM1: Sequential Access Method. Method of reading sequential datasets – from the beginning to the required record. Originally a collective term for QSAM and BSAM, when the situation applied to both. But SAM grew to include SAM-E in 1983 with the announcement of DFP1, now DFSMSdfp. See also ESDS.
SAM2: Software Asset Management.
SAM-E: Sequential Access Method–Extended. Souped-up version of the original SAM sequential access method. The main innovation is that it supports sequential data striping. Until 1983, SAM-E was a separate software product. After being incorporated into DFP1 (now DFSMSdfp), SAM-E lost its name and became simply SAM. See also SAM1.
Sametime: Lotus software supporting extended teams with instant messaging.
Sametime Everyplace: Sametime for mobile devices.
SAMON: SNA Application MONitor. z/OS system which enables a terminal to monitor the status of all VTAM applications within a network. Announced January 1987. Replaced December 1997 with NetView Access Services as the recommended replacement.
SAN: Storage Area Network. Typically, a disk drive subsystem attached via fiber to a network, accepting and processing requests from multiple platforms. cf NAS.
Sandbox: This term is usually used in the expression system programmers’ sandbox to refer to a machine dedicated to systems development. It is unclear whether it is meant to refer to a child’s sandpit, or a cat’s sanitary facilities.
San Francisco: See SanFrancisco.
SanFrancisco: Cross-system, client/server object-based application development environment, delivered by IBM in August 1996, with a lot of help from business partners such as JBA in the UK and IBS in Sweden. Includes re-usable frameworks together with tools such as IBM’s VisualAge, plus third party offerings and PC-based tools to build business applications in the areas of logistics, finance, distribution, and manufacturing. Much of the development work for San Francisco was done by IBM and third parties with OS/400 expertise, but it currently runs in AIX1, HP-UX, Sun Solaris, Siemens Reliant Unix, OS/400 and Windows Server operating systems. The promised mainframe version has yet to materialize. It’s apparently called SanFrancisco (SF) because it’s about Shareable Frameworks (SF). The underlying model is CORBA-compliant. Java-based. There are application-specific packages including Ledgers and Supply Chain. Part of the IBM Framework for e-business and a member of the WebSphere Business Components family. Originally San Francisco, but the blank was removed beginning with Version 1 Release 3.
SAP1: System Assist Processor.
SAP2: A software company formed in Germany in 1972 by five former IBM SEs. Leader in the ERP1 market. SAP stands for Systems Applications and Products.
SAPR: Solution Assurance Product Review.
SAR: Solution Assurance Review.
SAT/400: Systems Administration Tools/400.
Satellite: Yet another code name for the machine variously called Summit and Planet. According to IBM, Satellite was introduced to put analysts off the track about the development.
SATT: Software Analysis Test Tool. OS/2 tool providing test, measurement, and analysis for developers of application software for z/OS, z/VM, VSE/ESA, and OS/400 environments. Announced in September 1989 as part of AD/Cycle. Withdrawn March 1994.
Saturn: At one time, a rumored 47-bit operating environment on top-end mainframe machines. Instead, z/OS was announced October 3, 2000, supporting 64-bit addressing. See also AMODE, ESB.
SAX: Simple API for XML.
SBCS: Single-Byte Character Set. A character set in which a character is represented by a single byte (i.e., the character set has a maximum of 256 entries). ASCII and EBCDIC are SBCSs. cf. DBCS, MBCS.
SBS: Satellite Business Systems. IBM’s joint venture, originally with Aetna Life and Comsat, to provide a wide bandwidth, digital transport service for voice and data. Subsequently SBS was largely acquired by MCI, which was partly acquired by IBM. By July 1989 IBM had got rid of most of its interests in SBS when it sold its last three satellites to Hughes Communications, a GM subsidiary. (Times must be really hard when you have to sell your last three satellites to keep the wolf from the door.)
SCADA: Supervisory Control And Data Acquisition. Generic term for software that collects data from industrial shop floors, and uses it for applications such as simple control, monitoring, trend identification, and transfer of data to other systems. MQSeries Integrator (MQSI) allows SCADA devices to be connected into an MQSeries environment.
Scalability: The ability of an architecture to run across a number of different size processors. Unix is usually held up as being the most scalable architecture with its ability to run on small PCs/workstations and top-end mainframes. IBM’s z/Architecture doesn’t do so badly – it can run on mainframes across more than a 100-fold power range, including systems that are essential a PC with a low power z/Architecture processor card added. In fact, go back a few years and mainframes were slower than today’s home PCs. Scalability is a requirement for POSIX compliance.
Scalar: Within most programming languages a scalar is a number, or a variable which holds a number. Within IBM’s SQL, a scalar is a function which can be used to extract data from strings in a database. Scalar is also used to refer to computers which carry out a single arithmetic operation per computer instruction (cf. Vector).
Scanmaster: See 8815.
Scanner1: In the communications environment, a scanner is a device, normally within a FEP, which scans and controls the transmission lines. Also known as a line adapter.
Scanner2: A device for capturing a graphical image in digital form. See Scanmaster, 3117-9, 2456.
Scanner3: Bar code reader. For reading the UPC on retail products, typically at a cash register in a store. The 4686, 4687, 4697 and 4698 are IBM Point-of-Sale Scanners. See also 468x, 469x.
SCB: Subsystem Control Block architecture. MCA standard for bus interfaces. Announced by IBM October 1989 to encourage third-party vendors to produce MCA compatible boards.
SCD: SemiConductor Disk. Same as SSD1 (Solid State Disk).
SCDS: Source Control DataSet. The file which contains the SMS1 rules.
SCE: System Controller Element. The part of the CEC which controls data movement between the processors and central storage, and to and from the ICE1. All data passes though the SCE, and the efficiency of the SCE at handling data transfers is what determines how well the processor complex handles multiprocessing. Built around an IBM-proprietary RISC processor, it has its own buffers, is highly intelligent and will probably play a major part in the automatic movement of data around the CEC. The SCE board may also have some main storage on it. cf. ICE1.
SCIF: Single User Console Facility.
SCLM: Software Configuration and Library Manager. Long a part of z/OS ISPF, SCLM includes a library manager and a configuration manager, and also provides change management and impact analysis. There is also an API for integration with other software, as well as user exits. Also a part of the IBM z/OS SCLM Suite. Integrated with Tivoli Information Management for z/OS (Info/Man) and WebSphere Studio Asset Analyzer for z/OS. See also Cloud 9 for SCLM for z/OS and Breeze for SCLM for z/OS.
SCM: Software Configuration Management. SCLM is an IBM SCM product.
SCO1: Santa Cruz Operation. Software house which develops Unix systems for Intel-based PCs.
SCO2: Special Conversion Offering. Yet another IBM name for a discount scheme. The SCO gives a special discount to people making a specific conversion, for example, from a non-System/3x machine to an AS/400. The latter SCO was made and then hastily withdrawn in mid 1990, apparently because too many 9370 users used it to trade their unloved 9370s for shiny bright AS/400s.
Scorfire: Hard drives used in some 7133 and 7131 models.
Scorpion: Hard drives used in some 7133 and 7131 models.
SCP: System Control Program. The core component of an operating system. Used frequently when discussing z/OS, z/VM and VSE/ESA.
SCR: Sustainable Cell Rate. The maximum average rate at which an ATM2 end system can transmit cells into the network.
ScreenCam: Lotus PC screen recording software. Typically used to demonstrate a(nother) software product in action. The recording is known as a movie.
Screen Customizer: IBM SecureWay Screen Customizer for Host Integration. Creates GUIs for host-based 3270 and 5250 applications, without touching the host application: no source code changes, no recompiles, and no rebind of the load module. Replaced by Host Access Client Package September 2000.
Screenmail: E-mail service provided by INS and the Personal Services and PROFS products. Also provided access to database services. Disappeared when AT&T took over INS.
Screen Reader: Software enabling a PC to read text aloud (through a suitable synthesizer). Designed to help blind people use the PC. Obsolete. See Independence Series.
Screen scraping: A programming technique for interacting with on-line host applications that generate text-only display output. The display output is read (scraped) right off a virtual screen by the workstation-based software and input generated on a virtual keyboard. What the user sees is quite different, and usually includes a GUI. It can be very effective in giving an application a new look. With enough analysis, it can also eliminate a lot of tedious interaction, assuming the host application had to some eliminate, of course. It’s a quick and dirty way of providing GUI solutions without re-writing the original TP program, but not recommended as a long-term strategy – it typically doubles the screen maintenance overhead. Easel and Mozart can be used to do this sort of thing. See also ECI.
ScreenView: The graphical interface to SystemView – announced September 1991. Supported connectivity to z/OS, z/VM and VSE/ESA, plus facilities for defining and manipulating icons and the like. Died with SystemView.
SCRIPT/VS: The formatting component of the DCF system. Also the name of the PC-DOS version of DCF in the 1980s. See DCF.
ScriptX: The much-delayed, hardware-independent, multimedia scripting language that had been under development by Kaleida. Version 1 was finally released in 1995 just as it and Kaleida were folded back into Apple. And neither have been heard from since.
Scrollable cursors: A DB2 cursor allows a program to remember where it is in a query result table, and to get back there at some future point. Scrolling allows the cursor to be moved, such as to the next row. Without scrollable cursors, applications have to cache all of the required data for later use, or reinvoke the query to reposition within the result table.
Scrubbing: Storage background scrubbing. Constant reading and rewriting of unused central and expanded storage (memory), and monitoring for errors, even soft errors where the data was successfully recovered, to ensure early detection of failures. A feature of eserver zSeries 900 storage arrays.
SCS: SNA Character String. A sequence of control commands that allows sophisticated operation of printers and other devices. Makes up for the limitations of the 3270 DSC.
SCSE: SuperComputing Systems Extensions. Package for users of MVS/XA and MVS/ESA on 3090 and ES/9000 vector machines introduced May 1989. Included high-speed channel, Clustered FORTRAN and a new access method for high-speed I/O. See also Supercomputer, Virtual coupling, Wizard Adapter, HIPPI, SVE. Obsolete.
SCSI: Small Computer Systems Interface. A non-proprietary interface for microcomputers and their devices. Very fast parallel interface used for hard disks, backup tapes, etc. Typically used on servers and some client workstations in organizations, but EIDE has remained the interface of choice for the home and office Intel-based workstation. SCSI is standard for Apple’s Macintosh. See also Serial Storage Architecture.
SCU1: System Control Unit. The unit of the IBM mainframe hardware which executes the instructions.
SCU2: Storage Control Unit. Another name for a disk/tape controller.
SCV: Software Compatible Vendor. IBMspeak for a PCM CPU vendor. Also known within IBM as a parasite. See also CCV.
SDA: Screen Design Aid. Utility on the System/38, AS/400 and iSeries 400 for creating and maintaining screen and menu designs. Part of ADTS.
SDB: Storage Descriptor Block.
SDDI: Shielded twisted pair Distributed Data Interface. A version of the FDDI standard that runs on shielded twisted pair (STP) cable. Since most companies already have miles of STP, SDDI is a very attractive option as it provides 100Mbps data rates without re-cabling. In June 1992, 11 vendors, including IBM, announced that they would support SDDI.
SDE1: System Delivered Education. A set of on-line tutorials in OS/400.
SDE2: Software Development Environment. IBM’s open CASE1 environment for AIX1 and the pSeries, announced January 1992. SDE uses technology licensed from HP (BMS). Replaced by C Set++ for AIX in January 1997.
SDF1: Screen Definition Facility. Began life as SDF/CICS: an application programmers’ tool for developing and maintaining CICS screen and printer formats. SDF II changed all that, becoming a versatile user interface (screens, maps, formats) tool covering the creation and maintenance of CSP1, VisualGen, IMS TM MFS, CICS BMS1, GDDM-IMD and ISPF panels. It can even convert from one to another. Programming languages supported include COBOL, PL/I, Assembler, C and RPG. Versions are available for z/OS, z/VM and VSE/ESA, though each is at a different release level, some older than others, and may not support all of the screen formats and programming languages listed above.
SDF2: System Data Format. A fixed length ASCII database format supported by dBase and other PC-based databases. Fields are filled with trailing blanks so that each column starts in the same character position for each row in a database table. Much as fields are stored in VSAM and other files used by mainframe applications. SDF is used as a data interchange format.
SDF3: Serial Data Field.
SDF4: See Software Delivery and Fulfillment.
SDH: Synchronous Digital Hierarchy. European standard for fiber networks which has been put together specifically for technologies such as ATM2. Above 155Mbits/s it’s the same as the American SONET. cf. PDH.
SDK: Software Developer’s Kit.
SDLC1: Synchronous Data Link Control. IBM data communications protocol, used in SNA and covering the physical and link control levels. SDLC is, to a large extent, compatible with the HDLC international standard. SDLC is typically used over telephone lines (leased line or dial-up) and may include a multi-drop connection to several different devices.
SDLC2: System Development Life Cycle. A generic term for any organized way of planning and building a computer-based solution.
SDN: Subject’s Distinguished Name. The X.509-defined name of the owner in a digital certificate.
SDO: System Delivery Offering. Pre-packaged software, usually an operating system. For example, the z/VM SDO includes the z/VM operating system and other systems software products, all with current maintenance (fixes) applied. See also VM/ESA SDO.
SDRAM: Synchronous Dynamic Random Access Memory. So named because it synchronizes itself with the clock speed of the microprocessor’s data bus (aka system bus). Used in PCs.
SDSF: System Display and Search Facility. On-line tool for programmers and operators monitoring jobs awaiting execution in the JES2 input spool queues and, most commonly, viewing the printed output of batch jobs in the Held output spool queues, to save printing it on paper. Most users can only view their own jobs, but systems programmers and operators are normally allowed to view everything, making SDSF especially useful for monitoring jobs currently executing, or the rest of the output of that seemingly endless print job. Runs in ISPF or directly in TSO without ISPF. An optional, separately priced feature of z/OS.
SDSS: Software Diagnosis Support System. IBM expert system research project.
SDT: Start Data Traffic.
SDVT: Skeleton Destination Vector Table.
SDWA: System Diagnostic Work Area.
SE1: System Engineer. An IBM support person. Many users believe that the SE is extinct, but specimens are occasionally sighted on large sites. A good way of verifying whether they still exist in your area is to let your IBM salesman know that you’re inviting a PCM to tender for a new processor or that you’re planning to downsize, when they appear in droves – like lawyers round a Washington traffic accident.
SE2: See Support Element.
SearchManager: Full-text storage and retrieval product based on STAIRS (for which it is a replacement). The z/OS CICS and z/VM CMS1 versions have interfaces to OfficeVision. There is also a Windows client. An AIX1 version, SearchManager/6000, was announced in May 1994 and withdrawn less than two years later.
SearchVision: Text management and contextual search software announced as an optional add-on for OfficeVision. By January 1991 SearchVision had become fully integrated into OfficeVision and lost its separate identity.
SEAS: Share European Association. Replaced by GUIDE SHARE Europe.
Seascape: Storage architecture based on the Serial Storage Architecture interface. Covers disk, tape and optical storage. Supports the range of eserver lines, from xSeries to zSeries 900. First spotted mid 1995, but not formally announced for another two years. Seascape implementations include Versatile Storage Server, Network Storage Manager (3466), Virtual Tape Server and Cross Platform Extension.
SeaStar: Code name for what became the 2105 Enterprise Storage Server family. Most notably a DASD controller replacing the 3990, which can be used to build fault-tolerant RAMAC clusters based on a ring architecture. The clusters promised to implement disk storage pools with multiple controllers which would off-load some processing from host systems and back each other up in the event of failures.
Seat: A slang term that refers to the number of licensed users of a software product, which is the same as the number of installations of the product.
Second-level cache: Type of memory which resides between high speed buffers and main memory. First appeared on the top ES/9000s. A similar feature was used on the top Hitachi EX processors where it was called Dynamic Working Storage. See DWS.
Second-level high-speed buffer: Another name for second-level cache.
Secured Network Gateway: AIX firewall1 software (vintage late 1994) which isolates an internal network from the Internet.
Secured signon: A RACF function that provides an alternative to a password.
Secure Electronic Transaction: Developed by VISA and MasterCard in conjunction with IBM and others. SET provides a secure means for transmitting credit card information from customers, via a Web browser, to a merchant’s application and then on to a financial institution for processing. There are three important security benefits: a credit card number is never revealed to the merchant, a SET ID number is linked to the access software, and a second number is required to decrypt the information.
Secure Sockets Layer: See SSL.
SecureWay: A common brand for IBM’s broad portfolio of security offerings announced January 1995 – no new products, just a new name. Mid 1996, a Single Sign-On and Internet firewall were added. After IBM acquired Tivoli, it became Tivoli SecureWay. There are a few exceptions, including IBM SecureWay Boundary Server, IBM SecureWay Directory, IBM SecureWay Firewall,
SecureWay Boundary Server: A package including SecureWay Firewall with ACE/Server (Security Dynamics), MIMEsweeper for SecureWay (Content Technologies) and SurfinGate (Finjan). Part of SecureWay FirstSecure. Withdrawn July 2001.
SecureWay Directory: IBM SecureWay Directory. LDAP cross-platform directory server intended to provided a common directory for all applications. Runs on AIX1, z/OS, OS/400, Sun Solaris and Windows servers.
SecureWay Firewall: IBM SecureWay Firewall1. Software that runs on AIX and Windows servers. Includes filtering, proxy and circuit level gateway. Based on technology introduced by IBM Research in 1985.
SecureWay FirstSecure: A framework for secure e-business by medium to large companies. Includes SecureWay Policy Director, SecureWay Boundary Server, SecureWay Trust Authority, SecureWay Toolbox. Withdrawn July 2001.
SecureWay Global Sign-On: Replaced by Tivoli SecureWay Global Sign-On.
SecureWay Policy Director: Replaced by Tivoli SecureWay Policy Director.
SecureWay Privacy Manager: Replaced by Tivoli SecureWay Privacy Manager.
SecureWay Public Key Infrastructure: Replaced by Tivoli SecureWay Public Key Infrastructure.
SecureWay Risk Manager: Replaced by Tivoli SecureWay Risk Manager.
SecureWay Security Manager: Replaced by Tivoli SecureWay Security Manager.
SecureWay Security Server: IBM SecureWay Security Server for z/OS. An optional, separately priced feature of z/OS. Security software that includes RACF, DCE Security Server, z/OS Firewall Technologies and LDAP Server.
SecureWay Server: See SecureWay Security Server.
SecureWay Toolbox: Seecurity and encryption tools for developers. Part of the obsolete SecureWay FirstSecure.
SecureWay User Administration: Replaced by Tivoli SecureWay User Administration.
SecureWay Wireless Gateway: AIX1 software that extends 5250 and 3270 Web-based client applications to mobile and wireless users. Replaced eNetwork Wireless Gateway and replaced by Everyplace Wireless Gateway for Multiplatforms December 2001.
Security APARs: A special type of APAR for reporting problems in existing security mechanisms where the problem descriptions do not meet the precise definition of system integrity, but which do constitute an exposure to the security of the system as a whole or to an IBM product which runs on the system. Security APARs are accepted for z/OS.
Security category: The name defined to RACF for a department or area within an organization whose members have similar security requirements.
Security classification: Use of a security category or security level within RACF to increase protection of sensitive resources.
Security label: The name defined to RACF for a security level containing zero or more security categories. See also security category.
Security level: The name defined to RACF for a numeric security level, where the larger the number, the higher the security level.
Security Server: See SecureWay Security Server.
Security token: A collection of identification and security information.
Segment: The portion of a RACF profile defined by one template.
Select: Select/MVS, Select/VM, Select/VSE, and Select/VM with VSE were pre-bundled packages of software which IBM introduced in April 1992 to try to inveigle users into the wonderful world of ESA. For the first year, you got the software and lots of help free.
SelectaDock System: A docking system for ThinkPads announced April 1996. Docking systems make it easier to use a laptop system at a desk by providing connections to a desktop style keyboard, mouse and monitor, as well as to a LAN.
Selector channel: An I/O channel that operates with only one I/O device at a time. Once an I/O device is selected, a complete record is transferred, one byte at a time. cf. Byte multiplexer, Block multiplexer.
Self service portal: A portal that permits Web browser users to easily perform their own inquiries and transactions, on-line, without having to interact with a telephone-based call center.
Self-Timed Interface: A zSeries 900 high speed connection between I/O subsystem and the processors and memory. The Internal Bus (IB) was used for this purpose prior to the System/390 G3, but became a bottleneck.
Self-Voicing Kit: IBM software that provides speech output for Java applications.
SEMPER: Secure Electronic Marketplace for Europe. European Commission (EC) consortium (vintage November 1995) headed by IBM, which aims to develop protocols and standards to deliver secure Internet commerce. Part of the EC’s Advanced Communications Technologies and Services (ACTS) program.
Sequent: A so-called (for tax reasons) merger with IBM that began July 1999 brought the NUMA-Q into the IBM product line. The announcement of eserver on October 3, 2000, included a NUMA-Q in the xSeries line (Model 430).
Sequential data striping: Technique for distributing a single sequential file across a number of devices to eliminate bottlenecks. Implemented in SAM-E. See also Data striping, File striping.
Sequential detect: A feature introduced mid-1996 in the 3990-6 DASD controller that automatically distinguishes applications which process sequential records from applications which process randomly selected records, and optimizes processing for the structure of the data.
Serial Line Internet Protocol: See SLIP.
Serial number: Term used to denote the machine which you own today, which may be very different from the one you originally bought – in the 3090 range every single bit of technology was changed between the first 3090 and the final J model; if you upgraded it in a piecemeal fashion, you could end up with a computer with the same serial number as the one you originally bought but with nothing else in common. Preserving a serial number in this way may offer tax advantages (i.e., what, in effect, is capital expenditure may be treated as revenue expenditure for tax purposes), and can be helpful in certain very bureaucratic environments where buying a new box may be a very difficult procurement process compared to just upgrading an existing machine. See also Velcro Serial Number, VPD.
Serial Storage Architecture: IBM dual-port, full duplex architecture (vintage 1994) for connecting storage devices. Originally promoted by IBM in opposition to the parallel SCSI architecture, which it claims is not as fast, and is more complex to cable (SCSI cables have 50- and 68-wires, whereas SSA cables have just four). And successfully made into ANSI standard X3T10.1. Adapter cards for SSA became available early 1995, and the first fully-fledged SSA system (the 7133) in July 1995. Part of the Seascape architecture.
Series/1: IBM minicomputer widely used for special purpose communications. It’s now too late to buy one – they were withdrawn from February 1991, although IBM maintained them up to 1996. The withdrawal notice said there are no direct replacements... however, the IBM 9370, AS/400, RS/6000, and the PS/2 families of products offer highly effective alternatives for most Series/1 users which seems to confirm that the Series/1 was all things to all men, and nothing to anybody.
Series 2200: See 8363.
Server: See Client/server.
Server farm: Same concept as a DASD farm.
Server footprint: See footprint1.
ServerPac: Customized installation materials for operating systems including z/OS. Part of the CustomPac family.
ServiceElect: A combination of hardware maintenance with other support services that generates a single monthly invoice from IBM.
Service Level Agreement: Generic term for an agreement between a user and the people providing a computer service. The SLA specifies such things as response time, availability, etc.
ServicePlan: Service contract introduced in the US January 1989 to replace all previous IBM service contracts. Basically the user picked a range of services from a limited selection to cover a specified amount of kit. The charge stayed constant unless the amount of kit increased above an agreed threshold. Not a bad idea – it simplified billing and budgeting, but at the expense of giving IBM increased account control. Unfortunately, about the only place you will see ServicePlan these days is in IBM trademark lists; ServicePlan Estimated Billing (EB) was withdrawn October 1999.
Service Point: A product at a node in a Tivoli NetView for z/OS network management system which acts as an interface between an upstream Focal Point and downstream devices which are not necessarily addressable directly from the Focal Point – e.g., they’re probably not SNA devices. Basically it’s the network management interface between an SNA network and a non-SNA network.
Service Unit: The basic charging unit in Usage pricing. An IBM SU is roughly equivalent to a MIPS.
Service Update Facility: An Internet-based method for ordering and receiving z/OS, z/VM and VSE/ESA software service from IBM.
Servlet: A Java applet, without a user interface, that is executed on a Web server. Often used to replace CGI routines, because they support dynamic HTTP requests.
SES: Shared Expanded Storage. Technique of sharing Expanded Storage among the systems in a sysplex.
SESSEND: Session ended.
Session1: SNA term for a relationship (a logical connection) between two devices. A session is usually set up by the issuing of a BIND1 request by one NAU to another NAU.
Session2: Multiple transmissions protected by the same encryption key(s).
Session manager: A mainframe utility (usually in VTAM) which allows a user on a terminal to switch between mainframe applications without logging off and on again. The session manager typically gives the terminal user a log-on screen which does all the sign-on authorizations. Thereafter, the session manager provides full-screen, menu, and/or command line interfaces which allow the user to specify switches between the applications. Most session managers provide security support, and many include the ability to take the sessions from one physical terminal to another, and for Help Desk staff to monitor terminal activity. There are many session managers; two of IBM’s offerings are Tivoli NetView Access Services and NLDM.
Session monitor: NetView Session Monitor. See NLDM.
Session stealing: IP splicing.
SESSST: Session started.
SET: See Secure Electronic Transaction.
SETROPTS RACLISTed profiles: Globally RACLISTed profiles.
SEU: Source Entry Utility. Full-screen syntax checking editor for program development on the System/38, AS/400 and iSeries 400. Powerful tool which uses the syntax checkers from the languages. Includes facilities for on-screen formatting appropriate to each language, copy, move, delete, scrolling, etc. Now part of ADTS.
Seven Dwarves: In the 1960s the computer industry was dominated by IBM and seven other companies, the so called Seven Dwarves. These were Burroughs, Control Data, General Electric, Honeywell, NCR, RCA, and Univac. However, the attrition of IBM’s little friends was heavy. GE sold out, and RCA merged with Univac. The remnants of the Seven Dwarves became the BUNCH.
SFS: Shared File System. Component of z/VM allowing file-sharing at the file level rather than at the mini-disk level. SFS files are held in pools and managed by a file server machine. Considered by z/VM buffs to be a great leap forward in storage management.
SGML: Standard Generalized Mark-up Language. The canonical markup language from which HTML and XML are derived. International standard for page make-up for electronic publishing systems derived from the IBM GML language, and fulfilling roughly the same functions as DCA. SGML is used in the US government CALS initiatives, and was at one time promoted by a number of companies, including IBM, as a standard for EDI1.
SGMP: Simple Gateway Monitoring Protocol. A network management protocol for TCP/IP networks.
SHARE: IBM users association covering a lot of interest areas, but especially strong in z/OS systems programming. Began with five members in Santa Monica, California in 1955. Conferences have had as many as 6500 attendees. Has spread worldwide in one form or another under the auspices of the International User Group Council. See also GUIDE.
Shared Expanded Storage: See SES.
Shared stand-alone storage: A rumored enhancement to the System/390 architecture which separates the memory from a specific processor and makes it shareable among all the processors in a sysplex via the ICE1. The ICE is a key enabler for shared stand-alone storage, and should enable data to go from DASD directly into expanded storage without processor intervention, and without channel transfers. Shared stand-alone storage is also known as S**3 and SSS.
SHARE OPTION 4: A file sharing setting for VSAM files.
shdaemon: An AIX1 command function that provides a SMIT-configurable mechanism to detect system hangs and initiate the configured action. Actions include an error message (logged and/or displayed), high priority login for the system administrator, specific commands or a reboot. See also daemon.
Shell: Generic term with a lot of different meanings. Early Internet service often involved an interface, called a Shell, on a host computer, rather than a direct connection to the Internet. And there was the IBM DOS Shell, a menu driven interface to basic PC-DOS functionality. Shell is also widely used in the expert systems and Unix communities, to mean software providing a skeleton which can be customized to produce a specific application. For example, IBM’s The Integrated Reasoning Shell (see TIRS) provides a generalized problem solving tool, which users can modify to create an expert system to solve a specific problem.
Shop Application Edition: IBM SCADA software developed jointly by IBM and Cincinatti-Milacron. Obsolete.
Short wavelength: One of two types of optical transceiver used for 1 Gbps Ethernet LAN. SX is the other.
Shrink-wrapped: IBMspeak for a stand-alone product. The rest of the world uses it to describe retail software products, because they are sealed in plastic to prevent consumer purchase, copy and return scams.
SI: See Systems Integration.
SIC: Serial Interface Chip.
SID: Systems Integration Division. Set up by IBM in 1988 to sell systems integration services, and dismembered two years later and replaced by ISSC.
SIE: Start Interpretive Execution. Firmware machine command originally introduced for use by VM/XA SP to initiate the execution of a guest system (to make it work, not start killing it). Makes some advanced facilities available and improves performance.
Sierra: Internal IBM code name for the replacement for the 308x. Sierra appeared as the 3090 in 1985.
SiGe: See Silicon/germanium.
Sight and Sound: 17 inch monitor with flat square tube, integrated stereo speakers, and camera enablement. The 7091-7S1 was announced October 1994 and withdrawn April 1996.
Signature: Word processing package developed by XyQuest for PC-DOS, Windows, and OS/2. IBM acquired exclusive worldwide rights in March 1991, making it the heir apparent to DisplayWrite. IBM set up a Signatoires program to encourage independent software vendors to write Signature-compatible software, but it all ground to a halt later in 1991, when IBM took up with Lotus, and assigned the marketing and distribution rights for Signature back to XyQuest.
Signature files: Stored information on known viruses used by anti-virus software.
Signed-on-from list: Used for persistent verification, a list of users with a session in progress between two LUs.
Silicon/germanium: Semiconductor fabrication technique which employs silicon and germanium (SiGe). Benefits include considerable speed increases compared with current generation silicon, higher densities than gallium arsenide, and the ability to use current silicon fabrication facilities for cost-effective production. To date, SiGe has been used mainly in embedded processors, especially for cell phones. Ironically, germanium was used in the 1960s as a cheaper alternative to silicon for semiconductors. Audio equipment using it had a characteristic white noise.
Silicon-On-Insulator: A processor technology that prevents electrical leakage from the processor chips. Copper and SOI account for the 20-35% processor performance improvement of pSeries 680 over RS/6000 S-series and iSeries 400 over AS/400e.
Silicon Valley Lab: The home of, among others, a z/OS DB2 UDB services team that delivers fee-based services to IBM customers.
Silverlake: Common term for the project that produced the AS/400. IBM denies that Silverlake was ever an official code name, but admits that it’s the name of a man-made lake just outside the Rochester plant where the AS/400 was developed.
Silverstone: Code name for the hybrid 9370 + PS/2 which eventually appeared in January 1990 as the 9371.
SIM1: Service Information Message.
SIM2: Strategic Investment Methodology. IBM technique for linking business objectives to a corporate business plan. Consists of structured meetings which produce a report advising the customer about its IT strategy.
Simon: IBM’s first foray into the PDA market, released in August 1994. It was a digital telephone with a few extra bits on, rather than a very small personal computer. Initially it was sold by BellSouth Corp, and not by IBM. Obsolete. See WorkPad.
Simply Speaking: See VoiceType.
Single-Byte Character Set: See SBCS.
Single Pallet Delivery: Consolidates pSeries hardware, the AIX1 operating system and selected AIX software installation materials into a single delivery.
Single subsystem scope: DB2 classes with the subsystem ID as part of the class name.
Single system node: See single system RRSF node.
Single system RRSF node: An RRSF node consisting of one z/OS system image.
Single Version Charging: See SVC1.
SIO1: Start I/O. Mainframe machine-level instruction which tells a channel to begin running a channel program.
SIO2: Special Installation Offering. IBM marketing program which IBM uses either to knock out old boxes cheap, or to dig itself out of a hole when it can’t supply the boxes people want. For example, IBM introduced an SIO in which it offered to lend customers an interim model of the AS/400 until the model they really wanted became available.
SIT: System Initialization Table. A table which defines general system options for CICS.
Site certificate: A RACF-managed digital certificate associated with a server, or network entity.
SiteManager: SystemView SiteManager Services.
SLA: See Service Level Agreement.
SLED: Single Large Expensive Disk. An acronym much used by proponents of RAID to pour contempt and contumely on large disks such as IBM’s 3380/3390 families.
SLIC: System Licensed Internal Code – a new name for LIC1, vintage mid 1995.
SLIP: Serial Line Internet Protocol. Defines the transport of data packets through an asynchronous telephone line. The original protocol used for dial-up access to the Internet.
SLP: Server Location Protocol. An IETF standard written by IBM and Zephyr to facilitate optimum load balancing between tn3270(E)/tn5250 servers.
SLR: Service Level Reporter. z/OS report generator cum job accounting package that works on system performance data. Although it’s an z/OS product, SLR can report on datasets created by z/VM and many individual pieces of system software, and seemed destined for loftier things when it was included in SystemView. Replaced by Tivoli Decision Support for z/OS December 1998.
SLU: Service Level Update. Installation materials for a software product with all current maintenance fixes applied. Each SLU has a number indicating how recent the included maintenance is.
SLUP: Secondary Logical Unit Program.
SM/400: System Manager for iSeries 400. See System Manager.
SMA: System Management Architecture. A name for the architecture which appears to underlie SystemView.
SMAF: System Migration Assist Feature. Feature under PR/SM which allowed a mainframe to emulate a Fujitsu or Hitachi processor. Available only in the Japanese market. See also VM/MPI, VM/MPII.
Smalltalk: Object-oriented programming system from Digitalk. Smalltalk/V is one of the enabling technologies for CUA 91, and has been used heavily within IBM for its own developments. There was a Smalltalk-based language for the iSeries 400 known as Envy/400 but it was replaced by VisualAge in March 1995. Today, VisualAge has been renamed to VisualAge Smalltalk and is available for AIX1, HP-UX, z/OS, OS/2, Sun Solaris, UNIX and Windows. It also supports Java platforms. See also CUA 91, Object.
SMAO: SystemView System Management Automation Offerings. SystemView software, announced August 1993, which allowed a focal point on a z/OS host to manage a network of pSeries or iSeries 400 systems. Withdrawn July 1995.
SMART2: Self-Monitoring, Analysis, and Reporting Technique. Standard for monitoring the performance of SCSI hard disks. Supported by IBM, and implemented in the UltraStar family of drives. Also spelled S.M.A.R.T.
SmartBatch: SmartBatch for OS/390. See BatchPipes, which it replaced, then was replaced by.
Smart cache: IBM improvement to conventional applet caching, pioneered with Host On-Demand 5.0, where the older version of an applet is activated while a newer version of it is being downloaded in the background.
Smart Card: Credit card-sized authenticator.
SmartCard Security Kit: Security hardware/software that prevents unauthorized access to a workstation. There was a desktop and notebook version. Announced September 1999 and withdrawn September 2000 (desktop) and January 2001 (notebook).
SmartCenter: Lotus software that provides access to major Web sites within software such as Microsoft Office, without starting up a Web browser.
SmartLink: See Salutation.
SmartOffice: See Salutation.
SmartSuite: Suite of desktop products from Lotus.
SMB: Server Message Block. Part of the obsolete PC Network system. Was a de facto standard in its time. An enhanced version of SMB is used in OS/2 LAN Server.
SME: Small to Medium Enterprise.
SMF: System Management Facilities. Function within z/OS which collects data on all system activities for use in accounting, performance monitoring, capacity planning, etc. SMF creates log entries (SMF records) of this data.
SMFF: SCRIPT Mathematical Formula Formatter.
SMI1: Server Management Interface. Server management standard developed under the auspices of DMTF.
SMI2: Synchronous Memory Interface.
SMI3: Structure of Management Information. See SNMP.
SMIT: System Management Interface Tool. A component of AIX.
SmoothStart: SmoothStart Services. On-site implementation (installation, configuration, customization and integration) and training startup. Provided by IBM Global Services for a number of platforms, including z/OS and even some non-IBM systems, but not z/VM. Announced March 1996.
SMP/E: System Modification Program Extended. An element of z/OS that is used to install most software products. Applies the relevant parts of Change Management to the installation and maintenance of software delivered in executable (OCO) format, with no source code. Most notably, the ability to test a new version of software (or maintenance to an old one) on a production system while the old version is simultaneously being used by production applications.
SMP1: System Modification Program. See SMP/E.
SMP2: Simple Management Protocol. A re-naming of SNMP.
SMP3: See Symmetric multiprocessing.
SMPO: See Software Migration Project Office.
SMS1: System Managed Storage. The philosophy of letting the computer system manage the storage of data rather than having it done by a human data administrator. The key benefit is that it provides device transparency – i.e., it removes the need for the data user to know where or how the data is stored. IBM promised SMS for years but delivered little more than promises until DFSMS, which was a good deal more solid than earlier vagaries. Today, it is almost universally used in z/OS environments and some software will not work without it.
SMS2: Storage Management Services. A Novell standard for file backup across the LAN.
SMS3: Microsoft Systems Management Server. Software distribution for Windows Server operating systems ala Tivoli Storage Manager.
SMSDSA: System Managed Storage DASD Space Analyzer. Software that was used mainly by IBM SE1s to sell DFSMShsm but also freely available to customers. When run on a z/OS system, it would calculate how much DASD space would be saved by running hsm. Obsolete.
SMSSMA: System Managed Storage Storage Management Assessment. Software that was used mainly by IBM SE1s to sell SMS1 but also freely available to customers. When run on a non-SMS z/OS system, it would calculate the benefits of moving to SMS. Obsolete.
SMSVMA: System Managed Storage Volume Mount Analyzer. Software that was used mainly by IBM SE1s but also freely available to customers. When run on a z/OS system, it would calculate the benefits of storing smaller tape datasets on DASD. Obsolete.
SMT1: Surface Mount Technology. A technique (used inter alia in some PS/2s, and in the InfoWindow displays) for fitting components onto boards. Lends itself well to automated assembly lines.
SMT2: Station Management. A protocol for FDDI networks. SMT was the last part of the FDDI to be specified by the US standards people, and IBM lent its weight to their efforts.
SMTP: Simple Mail Transfer Protocol. The protocol which allows the transmission of e-mail messages across the Internet.
SMU: System Management Utilities. iSeries 400 software (announced September 1990) which enables an iSeries 400 to control a network of other iSeries 400s, and also to act as a single focal point for the distribution of PTFs and the like. Replaced December 1991 by SAA SystemView System Manager/400, which, in turn, was replaced by the SystemView Operations Control Center for OS/400 withdrawn December 1998.
SNA: Systems Network Architecture. IBM’s data communications architecture defining levels of protocols for communications between terminals and applications, and between programs. For most of its life, which began in 1974, SNA was strictly host-based with VTAM providing all the network management functions except for path control which was provided by NCP in the communications FEP. More recently SNA has become less autocratic with control being distributed around the network nodes.
SNA/APPN Services: The component of z/OS Communications Server that includes VTAM.
SNA/FS: SNA File Services. Subsystem within Tivoli NetView Distribution Manager which supports movement of files across a network. Operates on a store-and-forward principle so that the receiver and transmitter don’t have to be on-line simultaneously.
SNA/MS1: SNA Management Services. IBM’s grand scheme for data distribution around a network. Incorporates SNADS and SNA/FS. Supports configuration, problem determination, statistics, and accounting.
SNA/MS2: SNA change Management System. Subsystem within Tivoli NetView Distribution Manager that supports change management, including planning, scheduling, and tracking of changes to remote/unattended SNA nodes.
SNADS: SNA Distribution Services. An architecture which provides a general, de-synchronized (delayed delivery) data distribution facility for SNA LU6.2 systems. Originally developed for document exchange, but extended to cover data, image, and voice. Not a separate product as such – consists of software residing in SNA nodes. IBM seems to prefer to spell it SNA/DS these days.
SNA Gateway: Synonymous with SNI.
SNAMCS: SNA Master Console Support.
SNAPP: System Networking, Analysis, and Performance Pilot. Provides a hand-held Personal Digital Assistant (PDA) menu-driven interface for performing AIX1 administration tasks.
Snapshot1: System Network Analysis Program Simulated Host Overview Technique. A proprietary IBM network simulator for optimizing network design. Not available as a product, but IBM will sometimes lend it to you if you ask nicely or promise to buy something.
SnapShot2: High-speed data duplication software for the RAMAC Virtual Array Storage.
SNA Server for AIX: Software (launched at the end of 1994) which enabled an RS/6000 to function as a high-end SNA server. September 1995 upgrade provided SMP3 support and better performance. Replaced by Communications Server for AIX1 June 1996.
SNASwitch: Cisco marketing-speak for IBM’s Enterprise Extender.
SNA Upline: Facility on OS/400 allowing OS/400 to start CICS transactions and to exchange data between OS/400 and CICS systems. An alternative to APPC.
SNCP: Single Node Control Point. In effect the network control element within a type 2.1 node. Provides some SSCP-type functions for type 2.1 peer-to-peer coupled sessions.
SNI: System Network Interconnection. SNA software in NCP and VTAM enabling dissimilar SNA networks to exchange information. One of two ways of building very large SNA networks, the other being ENA.
SNM: See Tivoli Storage Network Manager.
SNMP: Simple Network Management Protocol (there appear to be moves afoot to drop the Network from its name, and turn it into the Simple Management Protocol). Unix protocol originally developed for management of TCP/IP networks, but now used for a variety of network types, including Ethernet, TRN, and OSI. SNMP has three elements: structure of management information (SMI); management information base (MIB); and the protocol itself, which carries the SMI to and from the MIB. SNMP provides a similar range of functions to CMIP1/CMIS, but is less resource-hungry. Supported by IBM passim.
SOAP: Simple Object Access Protocol. A lightweight form of middleware for accessing services, objects, and servers in a platform-independent manner. Carries a payload of XML on top of HTTP or some other protocol. A W3C standard originally developed by Microsoft and endorsed by IBM.
Social engineering: A hacker’s technique of impersonating a staff member in an attempt to deceive other staff, to gain access to an organization’s computing resources.
Sockets: Software interfaces that allow two Unix application programs to talk to one another using TCP/IP protocols.
SoD: Statement of Direction. An official promise by IBM. An SoD comes with a (fairly) firm commitment that it will be implemented (or retracted) within two years. See SoI1.
SOEMI: Serial OEM Interface. Interface on the 9370 to allow connection of equipment from OEMs.
Soft.Switch: See Soft-Switch.
Soft5080 for AIX: Emulates the 5080 graphics system on the eserver pSeries. Announced June 1995. Withdrawn July 2001.
SoftBench: A Unix development environment from HP, which became a de facto standard in the Unix world.
SoftCopy: IBM documentation (manuals) on CD-ROM, DVD and the Internet, and the software tools to use it.
Soft Switch: See Soft-Switch.
Soft-Switch: At one time, an independent software vendor specializing in communications between office systems. IBM sold Soft.Switch’s z/OS and z/VM software to users wishing to communicate between OfficeVision and non-IBM systems, as a replacement for the OIF software which IBM announced but which was never shipped. The formal marketing agreement terminated in February 1993. Lotus bought Soft-Switch in June 1994, then disbanded the product line, with support ending April 2002.
SoftSwitch: See Soft-Switch.
Software Analysis Test Tool: See SATT.
Software Delivery and Fulfillment: An area within IBM US that accepts and fulfills orders for software.
Software Inventory Utility: OS/400 software that autosenses what release it is being run on, outputs a report showing what software is currently installed and displays the software in different categories which indicate how it can be ordered.
Software Mall: Facility on IBM’s IN service, announced November 1991 for the US only, which enabled software vendors to run a range of support and sales services for users to dial in to. Obsolete.
Software Migration Project Office: IBM group formed in 1993 to help migrate customers from utilities software vendors (USVs) to IBM and Tivoli products. The Tivoli Migration Team specializes in z/OS. The DB2 Migration Team covers all platforms. The Software Portfolio Strategies Group (SPS) also focuses on the mainframe.
Software Publishing Certificate: A PKCS #7 signed-data object containing X.509 digital certificates.
Software Server: Family of seven software bundles announced March 1996: Lotus Notes, Internet Connection Server, Database Server, Communications Server, Directory & Security Server, Systems Management Server, and Transaction Server. Available (but not necessarily all seven) for AIX, OS/2, and Windows NT platforms.
Software Subscription: Name for various, most notably OS/400 and AIX, flat rate fee offerings that provide the latest version/release of software without additional charge. See also Software Upgrade Assistant.
Software Upgrade Assistant: A Web-based tool that allows Software Subscription customers to directly order release upgrades based on the software subscription they have and the products they want upgraded. Requires registration through IBM Electronic Services.
SoftwareXcel: IBM software services program announced in the USA December 1989. The customer pays for a chosen level of support – Basic, Extended, Custom – ranging from remote database access up to permanent in-house IBMer. A key innovation is that it may include support of non-IBM products, although cynical observers have suggested that this aspect of SoftwareXcel is IBM’s method of getting customers to pay for its research into competitive suppliers. SoftwareXcel presages the end of IBM’s policy of bundled software support for mainframe users. August 1991 the program was extended to include installation of mainframe operating systems.
SoHo: Small office Home office. Generic term for the low end of the small business market. Even housing contractors use the term.
SoI1: Statement of Intent. An official half-promise by IBM. An SoI does not appear to have a timescale attached to it (cf. SoD).
SOI2: See Silicon-On-Insulator.
Solid State Disk: See SSD1.
Solution Assurance eSAR: See eSAR.
SolutionPac: Bundle of software and/or hardware providing (fairly) complete solutions for a specific application. Some of the SolutionPacs add value to their component products by providing some interfaces, and creating consistency, but otherwise the SolutionPac is just a bit of IBM marketing puff. Obsolete.
Solution Repository: Accessible via the Web, a consolidated inventory of eserver solutions and links to testing and integration centers, solution assurance processes, service offerings, and reports based on IBM, customer experience, and other sources.
SOM: System Object Model. Standard implemented first in OS/2 Version 2.0, designed to help users develop class libraries and object-oriented programs. Supports the CORBA standards. A distribut