
	Software �>�Globalization�>�Terminology�>�

IBM Terminology

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z #

Please send any feedback about the terms and definitions on this site to terms@ca.ibm.com

�

�S/390: IBM enterprise servers based on Enterprise Systems Architecture/390 (ESA/390).The S/390 has been superseded by the IBM zSeries.
�S/390 storage: Storage arrays and logical volumes (LVOLs) that are connected to S/390 servers. S/390 storage sometimes also includes zSeries storage. See also zSeries storage.
�SA: (1) See system administrator.; (2) See Security Association.
�SAA: See storage accounting area.
�SAA communications interface: A programming interface that allows program-to-program communication using the SNA APPC protocols.
�SAAJ: See SOAP with attachments API for Java.
�SAA resource recovery interface: A programming interface that provides a consistent application programming interface for applications that make changes to protected system resources.
�SABM: See set asynchronous balanced mode.
�SABME: See set asynchronous balanced mode extended.
�SACL: See State Adaptive Choreography Language.
�SAF: See System Authorization Facility.
�safe condition: Any condition having a severity of 0 or 1. Such conditions are ignored if a condition handler is not handling the situation.
�SAG: See SWIFTAlliance Gateway.
�SAID: See system adapter identification number.
�sale: In WebSphere Commerce Payments, the simultaneous authorization and capture of a transaction.
�sales catalog: A section of the master catalog that contains a flexible structure for customer display purposes. Users can have only one master catalog per store, but can have as many sales catalogs as they want. See also master catalog.
�sales manager: A defined role in WebSphere Commerce that manages order processing, ensuring that orders are properly fulfilled, payment is received, and orders are shipped. The sales manager can search for customer orders, view details, manage order information, and create and edit returns. See also operations manager, order.
�SAM: See sequential access method.
�Sametime discussion: A type of Sametime program. It allows users to share information with coworkers and to keep shared documents in a central location. Users can also chat with others who are using the same discussion.
�Sametime link: See active name.
�Sametime online meeting center: The database template that Sametime users access to reserve online meetings or to attend online meetings.
�SAML: See Security Assertion Markup Language.
�sampled event: An event that happens when a situation becomes true. Situations sample data at regular intervals. When the situation is true, it opens an event, which is closed automatically when the situation returns to false.
�sample line: In RLU, a record that represents data and gives a user's report prototype a more realistic appearance but for which the user does not create data description specifications (DDS).
�sample program: An application program shipped with the CICS system. Assembler sample programs are supplied in source and executable form. High-level language sample programs are supplied in source form only.
�sample statistics program (DFHOSTAT): Batch program supplied with CICS which provides information that is useful in calculating the storage requirements of a CICS Transaction Server system, for example, the sizes of the dynamic storage areas.
�sample store: See starter store.
�SAN: (1) See system area network.; (2) See storage area network.
�SAN-attached: Describing disks that are physically attached to all nodes in the cluster using Serial Storage Architecture (SSA) connections or using fibre channel switches.
�sandbox: A restricted environment, provided by the Web browser, in which Java applets run.
�SANergy: See Tivoli SANergy.
�SAN File System console: A Web user interface used to remotely monitor and control the SAN File System with any standard Web browser. See also administrative server.
�sanity check: See smoke test.
�SAP: (1) See service access point.; (2) See Service Advertising Protocol.; (3) See system assist processor.
�SAP selector: An external identifier for a service access point.
�SAR: (1) See significant architectural requirement.; (2) See store archive.
�SAR file format: In WebSphere Commerce, SAR (store archive) is a platform-independent file format that aggregates many files into one. See also store archive.
�SAS: (1) See spool access support.; (2) See Secure Association Service.
�SASL: See Simple Authentication and Security Layer.
�satellite: A DB2 database server that is a member of a group of similar DB2 database servers. Each satellite in the group runs the same application and has a similar configuration to support the application. See also DB2 control server.
�Satellite Administration Center: A user interface that provides centralized administrative support for satellites.
�satellite control server: A DB2 database system that contains the satellite control database, SATCTLDB.
�saturation: (1) The amounts of color and gray in a hue that affect its vividness; that is, a hue with high saturation contains more color and less gray than a hue with low saturation.; (2) The level at which a system no longer operates at its full capacity. See also consumption.
�save: (1) To copy specific objects, libraries, or data by transferring them from main storage or auxiliary storage to media such as optical disc, tape, diskette, or a save file. See also restore.; (2) To make a local copy of a file that is attached to a document.
�save area: An area of main storage in which the contents of registers are saved.
�save conflict: A save conflict occurs when two or more Notes users edit the same document in a Notes database on a server at the same time. The document saved first becomes the main document; subsequent users are prompted to save their changes as responses titled '[Replication or Save Conflict].'
�save file: (1) A file allocated in auxiliary storage that can be used to store saved data on disk (without requiring diskettes or tapes), to do I/O operations from a high-level language program, or to receive objects sent through the network. The system-recognized identifier for the object type is *FILE.; (2) In Backup, Recovery, and Media Services, an online file allocated on direct access storage for use as interim or short-term storage before off-loading to removable media or permanently deleting.
�savepoint: A named entity that represents the state of data and schemas at a particular point in time within a unit of work.
�savepoint level: A distinct scope that is used for reference and for interaction between savepoint-related statements.
�save/restore media: The diskette or the tape that the user uses to save and restore the files, folders, or libraries.
�save storage: An operation that copies (sector by sector) all permanent data from configured disk units to tape.
�save system authority: A special authority that allows the user to save and restore all objects on the system and free storage of all objects on the system.
�save-while-active operation: An operation that the user runs to save objects while application programs that change the objects are running. See also dedicated save operation.
�SAVSYS tape: A tape that is generated by the SAVSYS command, on which system data is recorded and saved.
�SAX: See Simple API for XML.
�SB: See sequential buffering.
�SBA: See set buffer address.
�SBCON: See Single-Byte Command Code Sets Connection.
�SBCS: See single-byte character set.
�SBCS data: Data that is associated with a single-byte character set.
�SC: See session control.
�SCA: (1) See shared communications area.; (2) See system control area.; (3) See Service Component Architecture.
�SCA component: A building block of the Service Component Architecture, used to build SCA modules such as mediation modules.
�SCADA: See supervisory control and data acquisition.
�SCADA device protocol (MQIsdp): A protocol that implements the WebSphere MQ Telemetry Transport to connect SCADA devices to the broker.
�SCA export binding: A concrete definition that specifies the physical mechanism used by a service requester to access an SCA module; for example, using SOAP/HTTP.
�SCA export interface: An abstract definition that describes how service requesters access an SCA module.
�SCA import binding: A concrete definition that specifies the physical mechanism used by an SCA module to access an external service; for example, using SOAP/HTTP.
�SCA import interface: An abstract definition that describes how an SCA module accesses a service.
�scalability: The ability of a system to expand as resources, such as processors, memory, or storage, are added.
�scalable: (1) Pertaining to a system's ability to increase its capacity to distribute information or data as demand heightens.; (2) Pertaining to the capability of a system to adapt readily to a greater or lesser intensity of use, volume, or demand. For example, a scalable system can efficiently adapt to work with larger or smaller networks performing tasks of varying complexity.
�scalable distribution infrastructure: An infrastructure that enables the management of large numbers of target computers in a variety of topologies. It provides a fast and reliable way to scan, distribute, and install software on target computers or groups of computers.
�scalable node: A physical platform that has at least one SMP Expansion Module. Additional attributes are assigned to a physical platform when it is a scalable node. These additional attributes record the number of SMP Expansion Modules, SMP Expansion Ports, and RXE Expansion ports on the physical chassis.
�scalable object: An IBM Director managed object that is used with Scalable Systems Manager. Scalable objects include scalable nodes, scalable systems, scalable partitions, and remote I/O enclosures that are attached to scalable nodes.
�Scalable Parallel 2 (SP2): IBM's parallel UNIX system: effectively parallel AIX systems on a high-speed network.
�scalable partition: An IBM Director managed object that defines the scalable nodes that can run a single image of the operating system. A scalable partition has a single, continuous memory space and access to all associated adapters. A scalable partition is the logical equivalent of a physical platform. Scalable partitions are associated with scalable systems and comprise only the scalable nodes from their associated scalable systems.
�scalable system: An IBM Director managed object that consists of scalable nodes and the scalable partitions that are composed of the scalable nodes in the scalable system. When a scalable system contains two or more scalable nodes, the servers that they represent must be interconnected through their SMP Expansion Modules to make a multinode configuration, for example, a 16-way xSeries 455 server made from four scalable nodes.
�Scalable Vector Graphics (SVG): A vector graphics language written in XML.
�scalar: (1) Pertaining to a single data item.; (2) A type of program object that contains either string or numeric data. It provides the byte string it is mapped to with representation and operational characteristics. See also pointer.; (3) An arithmetic object, an enumerated object, or a pointer to an object.; (4) A quantity characterized by a single value. See also array, vector.
�scalar fullselect: A fullselect that returns a single value: one row of data that consists of exactly one column. See also fullselect.
�scalar function: An SQL function that optionally accepts arguments and that returns a single scalar value each time that it is invoked. A scalar function can be referenced in an SQL statement wherever an expression is valid. See also function, routine.
�scalar instruction: An instruction, such as a load, store, arithmetic, or logical instruction, that operates on a scalar. See also vector instruction.
�scale: (1) The number of digits in the fractional part of a number.; (2) In the GDDM function, the number and progression of ticks along a vertical or horizontal axis.; (3) In the GDDM function, to enlarge an image or marker.
�scale factor: A number that indicates the position of the decimal point in a real number.
�scale line: In Query, a line at the top of a report that shows column positions.
�scaling: A process by which an image is reduced or enlarged in size to fit a given area on the display.
�SCA module: A module that conforms to the Service Component Architecture (SCA) with well-defined interfaces. The module makes its function available to requesters by exporting its interface through an export. The module acts as a requester to a service provider by importing the provider's requirements through an import. It is possible to specify an export from another module as a target in an import. The modules are then packaged in a standard WebSphere Enterprise Archive (EAR) file. An EAR file contains all the files required to deploy the application.
�scan configuration file: A configuration that contains information for scanning commands.
�scan line: (1) A single row of picture elements that are typically arranged horizontally and are scanned sequentially.; (2) In a laser printer, one horizontal sweep of the laser beam across the photoconductor.
�scanner: (1) A device that examines text, graphics, or bar code patterns and generates electrical signals corresponding to the pattern. It sends the signals to a computing device for processing.; (2) The software used to gather hardware information and software information from systems and devices.
�SCA request: A service request that conforms to the Service Component Architecture (SCA). An SCA module routes the request to a service provider, after having done any additional processing specified by the module.
�SCA run time: The server functions that provide support for the Service Component Architecture.
�scattered read: A method of reading contiguous data pages from disk to discontiguous portions of memory. See also block-based I/O.
�scatter plot: A variety of line chart in which only the marked points, and not their joining lines, are drawn.
�SCB: See string control byte.
�SCbus: See Signal Computing bus.
�SCCP: See signaling connection control part.
�SCCS: See Source Code Control System.
�SCD: See system contents directory.
�SCE: See system control element.
�scenario: (1) A set of actions representing a business process within the context of a collaboration. Scenarios can be used to partition a collaboration's logic. For example, if a collaboration handles one type of business object with various possible verbs, the user might develop Create, Update, and Delete scenarios. See also activity.; (2) A specific sequence of actions that illustrates behaviors. A scenario may be used to illustrate an interaction or the execution of one or more use-case instances. See also interaction, use case.
�scenario tree: The set of scenarios, displayed hierarchically, that includes composite scenarios, subdiagrams, and iterators.
�scene: The graphical representation of information retrieved from a database. A scene can also include other graphic elements, such as static text and images, and navigational tools, such as wormholes. See also wormhole.
�schedule: To request that a task set be started at a particular interval or on occurrence of a specified program interrupt.
�scheduled item: Any of the items in an outline to be covered, in sequence, during a session that is added to the Scheduled Items folder at the top of the outline. Instructors add scheduled items when developing the course outline before a session begins.
�scheduled job: (1) A batch job that becomes eligible to run at a specified date and time.; (2) A batch job that is submitted with a value other than *CURRENT for the schedule date and schedule time parameters.
�scheduled meeting: A Sametime meeting that has been created using the New Meeting form, not by clicking an active name or using Sametime Connect. Scheduled meetings can start at a future date and time, or they can start immediately. See also meeting status.
�scheduled offering: A Learning Management System offering with a start and end date that contains one or more learning events, such as a classroom course.
�schedule performance index (SPI): An earned value metric that describes the ratio of work performed to work scheduled. A number less than 1 indicates that the project is behind schedule.
�scheduler: (1) A computer program that performs functions such as scheduling, initiation, and termination of jobs.; (2) A multithread, multiprocess background server designed to handle the scheduling and launching of jobs, based on a simple timing scheme. See also broadcast job.; (3) A service that provides time-dependent services.
�scheduler agent: A MERVA Liquidity Manager component that schedules the imported messages and updates the balances of the clearing channels.
�scheduler element: The part of the job control table (JCT) entry that represents one or more dynamic support programs (DSPs) needed for processing of jobs by JES3.
�scheduler message block (SMB): An IMS control block that represents a transaction.
�scheduler work area (SWA): An element of the CICS address space. The SWA is made up of subpools 236 and 237 which contain information about the job and the step itself. Almost anything that appears in the job stream for the step creates some kind of control block in this area.
�schedule state: A segment of a business schedule. Examples of schedule states are critical, peak, prime, standard, low impact, off hours, and no service.
�schedule variance (SV): An earned value metric used to describe the difference between the scheduled completion and the actual completion of an activity.
�scheduling environment: A list of resource names along with their required states. If an MVS image satisfies all of the requirements in the scheduling environment associated with a given unit of work, then that unit of work can be assigned to that MVS image. If any of the requirements are not satisfied, then that unit of work cannot be assigned to that MVS image.
�scheduling intent: An application program attribute that is defined in the PSB, and that specifies how the program should be scheduled if multiple programs are contending for scheduling. See also read access, read-only access, exclusive intent, update intent.
�scheduling order: The order in which MERVA Liquidity Manager schedules payments (first-in first-out, smallest first, largest first, or next best fit).
�scheduling parameter: Information that describes the prioritization characteristics of a thread.
�scheduling policy: Information that describes the algorithm that will be used to prioritize threads that are running within the current process or operating system.
�scheduling priority: A transaction attribute that is used in calculating which transaction is selected for scheduling. See also limit priority, normal priority.
�schema: (1) A collection of database objects such as tables, views, indexes, or triggers that define a database. A database schema provides a logical classification of database objects. See also collection.; (2) A group of object classes defined for and applicable to a single namespace.; (3) See XML schema.; (4) See SQL schema.
�schema document definition: A description or layout of an XML document based on an XML schema.
�schema repository: A repository that stores schemas and versions of schemas for user databases.
�SCI: See Structured Call Interface.
�SCM: (1) See software configuration management.; (2) See supply chain management.
�scope: (1) In the C language, the range within a program in which a declaration is known.; (2) The extent to which the semantic effects of language statements reach. The scope may be to the job or to the activation group.; (3) The level to which a commitment control definition applies.; (4) Information that is used to describe whether the scheduling policy indicates that threads compete directly with other threads within the process or within the system.; (5) In Web services, a property that identifies the lifetime of the object serving the invocation request.; (6) A named part of the CICSPlex SM environment that qualifies the context of a CICSPlex SM request. The scope can be the CICSplex itself, a CICS system, a CICS system group, or any set of CICS resources that are defined as a logical scope in a CICSPlex SM resource description. See also context.; (7) A specification of the boundary within which system resources can be used.; (8) The effective range of the enablement of a condition, the establishment of a user-generated routine to handle a condition, or both. Scope can be both statically and dynamically defined. See also namespace scope.; (9) In identity management, the set of entities that a policy or an access control item (ACI) can affect.; (10) The component of a policy expression that describes the class of resources that is subject to the decision of a policy. In the OGSA Policy Service, scope is the policy discipline and policy role.; (11) A part of a source program in which an object is defined and recognized.
�scope management: The process of prioritizing and determining the set of requirements that can be implemented in a particular release cycle, based on the resources and time available. This process continues throughout the lifecycle of the project as changes occur. See also change management.
�scope of control: See network management domain.
�scope operator: In C++, an operator that defines the scope for the argument on the right: if the left argument is blank, the scope is global; if the left argument is a class name or namespace name, then the scope is within that class or namespace respectively.
�scope terminator: A variable at the end of a statement.
�scoping: A mechanism for controlling multiple sign-ons of the same userid to one or more CICS regions.
�score: In DB2 Text Search and DB2 Net Search Extender, an absolute value of type DOUBLE between 0 and 1 that indicates how well a document meets the search criteria relative to the other found documents. The value indicates the number of matches found in the document in relation to the document's size.
�SCORM: See Sharable Content Object Reference Model.
�SCOS: See single copy object store.
�SCP: (1) See service control point.; (2) See System Control Process.
�SCP dependent LU: See SSCP dependent logical unit.
�SCPF job: See start-control-program-function job.
�scrapbook: An editor that can be used to experiment and evaluate Java expressions. Workbench users can run, inspect, and display snippets of code in the scrapbook.
�scratch: The state of a tape volume that is available for general use because it is not assigned. See also use attribute, nonscratch volume.
�scratchpad area (SPA): A work area used in conversational processing to retain information from an application program across executions of the program.
�scratch pool: The collection of tape cartridges from which requests for scratch tapes can be satisfied.
�scratch processing: The returning of a volume to scratch status once it is no longer in use and has no outstanding release actions pending.
�scratch tape: See scratch volume.
�scratch tape volume: An unassigned tape volume.
�scratch volume: A labeled volume that is either blank or contains no valid data, that is not currently defined, and that is available for use.
�screen: (1) The physical surface of a display device upon which information is shown to a user.; (2) The display that the user sees when he or she connects to a 3270 application on the host system. A single 3270 application can include many screens, each of which has a purpose within the context of the application.
�screen capture: An XML representation of a host screen, used to create or customize a screen customization or transformation.
�screen customization: A HATS resource with two parts: a set of screen recognition criteria used to match host screens, and a list of actions to be taken when a host screen matches the screen recognition criteria.
�Screen Definition Facility (SDF): An interactive tool used to define and maintain maps, map sets, and partition sets for CICS and BMS applications.
�screen design aid (SDA): A function of an application development program that helps the user design, create, and maintain displays and menus.
�screen edit mode: In AFP Utilities, the mode that allows a user to design and edit an overlay.
�screen editor: A 3270 terminal service development tool that enables a developer to create and modify recognition profiles for an imported screen and to assign names to the fields on the screen definition.
�screened transfer: A type of call transfer in which the transfer of the held party to the third party is completed only if the third party answers the call. See also blind transfer.
�screen file: The result of importing a screen definition from a 3270 application into the 3270 terminal service development workbench. A screen file represents a screen definition. The screen definition contains identifiers such as the number of fields on the screen and the row and column position of fields on the screen. There are multiple screen files per 3270 terminal service project. Each screen file can have multiple recognition profiles assigned to it.
�screen-image interface: The part of the Front End Programming Interface that has a buffer with one byte for each screen position.
�screen import: The process of importing a screen definition (in its current state) and saving it to a screen file within the 3270 terminal service tools workbench, for the purpose of generating recognition profiles and custom screen records. Use the 3270 terminal service recorder to import screens.
�screen page: The amount of data displayed, or capable of being displayed, at any one time on the screen of a terminal.
�screen reader: A device that renders onscreen text as audible language. See also digital speech synthesizer.
�screen recognition: A runtime function that determines the state of a screen and processes the screen in accordance with the identifiers in the recognition profiles. Screen recognition compares the screen as presented by the 3270 application to the defined recognition profiles to determine which screen state applies.
�screen recognition criteria: A set of criteria used to determine whether a host screen matches a screen customization and should have that screen customization's actions applied. Screen recognition criteria are also used in the process of recording a macro; in this context they are sometimes called descriptors.
�screen sharing: The viewing and controlling of program screens on a computer other than the user's own computer. During a screen-sharing Sametime meeting or Learning Space - Virtual Classroom Live session, one participant shares a screen with the other participants and can allow them to control the program. The program needs to be installed only on the computer of the person who is doing the actual sharing.
�screen state: The set of conditions (at the time the screen was imported from the host) that determine the allowed and required processing on the screen. A screen's state operates on input to change the status, cause an action, or result in a particular output screen. A single screen can have multiple states and the allowed user actions for the screen vary depending on which state the screen is in.
�screen view: In AFP Utilities, the presentation of a display shown while a user is in screen edit mode.
�script: (1) A series of commands, combined in a file, that carry out a particular function when the file is run. Scripts are interpreted as they are run.; (2) The logical flow of actions for a 3270 server program.; (3) An exact text for the telesales service representative to read to a customer regarding transactions. Scripts can be short-hand or prompts to remind a representative to say certain things to a customer at certain points during a call.
�scripted OS image: An unattended install action where operating system installation files that are used with some configuration files would install the operating system on the target system using boot server technology.
�scripting: A style of programming that reuses existing components as a base for building applications.
�scripting language: A high-level programming, or command, language that is interpreted (translated on the fly) rather than compiled ahead of time. See also JavaScript.
�script language: A high-level, application-specific scripting language that consists of statements used to develop 3270 scripts. These scripts are part of the interface between a state table and a 3270-based host business application.
�scriptlet: A mechanism for adding scripting language fragments to a source file.
�scroll: To move a display image vertically or horizontally to view data that is not otherwise visible in a display screen or window.
�scrollability: A property of a cursor that indicates whether the cursor can fetch in a backward direction. See also fetch orientation.
�scrollable cursor: A cursor that can be used to fetch in backward and forward directions. See also nonscrollable cursor.
�scrollable result set: A result set that is associated with a scrollable cursor that allows the application to fetch rows and to refetch previously fetched rows.
�scroll bar: A part of a window that shows a user that more information is available in a particular direction and can be moved into view by using a pointing device or the page keys.
�scrolling window: The portion of the presentation space that is mapped to the viewport at any given time. The window can be moved vertically within the presentation space by scrolling. See also presentation space.
�scrubbing: The removal from VOB and view storage directories of files that are no longer needed.
�SCS: See SNA character string.
�SCSA: See Signal Computing System Architecture.
�SCSI: See Small Computer System Interface.
�SCSI back-end layer: The layer in a Small Computer System Interface (SCSI) network that performs the following functions: controls access to individual disk controller systems that are managed by the cluster; receives requests from the virtualization layer, processes them, and sends them to managed disks; and addresses SCSI-3 commands to the disk controller systems on the storage area network.
�SCSI device: A product, such as a drive or adapter, connected to a host through an I/O interface using the Small Computer System Interface (SCSI) protocol. A SCSI device is either an initiator or a target. See also Small Computer System Interface, initiator.
�SCSI Enclosure Services (SES): A subset of the small computer system interface (SCSI) protocol used to monitor temperature, power, and fan status for enclosure devices.
�SCSI-FCP: A standard that defines the protocol used to transfer Small Computer System Interface (SCSI) commands over the transport physical layer of the fibre-channel interface. This standard is published by ANSI as X3.269-1996.
�SCSI front-end layer: The layer in a Small Computer System Interface (SCSI) network that receives I/O commands from hosts and provides the SCSI-3 interface to hosts. SCSI logical unit numbers (LUNs) are mapped to virtual disks (VDisks) in this layer as well. Thus, the layer converts SCSI read and write commands that are addressed to LUNs into commands that are addressed to specific VDisks.
�SCSI host system: A host system that is attached with a Small Computer System Interface (SCSI). These host systems run on operating systems such as UNIX, OS/400, Windows NT, Windows 2000, or Novell NetWare.
�SCSI ID: A unique identifier assigned to a Small Computer System Interface (SCSI) device that is used in protocols on the SCSI to identify or select the device. The number of data bits on the SCSI bus determines the number of available SCSI IDs. A wide interface has 16 bits, with 16 possible IDs.
�SDA: (1) See screen design aid.; (2) See statistics data area.
�SDC: See Server Display Control.
�SDDM: See source distributed data manager.
�SDEP: See sequential dependent segment.
�SDF: See Screen Definition Facility.
�SDI: See sequential data set input.
�SDK: See software development kit.
�SDL: See system directory list.
�SDLC: See Synchronous Data Link Control.
�SDO (SDO): (1) See sequential data set output.; (2) See Service Data Objects.
�SDO repository: A database that the service integration bus for Web services enablement uses for storing and serving Web Services Description Language (WSDL) definitions.
�SDRAM: See synchronous dynamic random access memory.
�SDSA: See shared dynamic storage area.
�SDSB: See spool data set browse.
�SDSF: See System Display and Search Facility.
�SDSL: See symmetric digital subscriber line.
�SDSP: See small-data-set packing.
�SDSRM: See server distributed sync point resource manager.
�SDT: (1) See start data traffic.; (2) See series definition table.; (3) See system dump table.
�SDU: See service data unit.
�SDUMP: See system dump.
�SDWA: See system diagnostic work area.
�SDY: See sequential data set system printer.
�SE: (1) See Support Element.; (2) See IBM systems engineer.
�seal: To encrypt a record containing several fields in such a way that the fields cannot be modified without either knowledge of the encryption key or leaving evidence of tampering.
�search: To request the display of objects that meet user-specified criteria.
�search application: In enterprise search, a program that processes queries, searches the index, returns the search results, and retrieves the source documents.
�search argument: (1) In RPG, a literal or field name specified in factor 1 of certain file operations (such as CHAIN) that identifies the record to be processed.; (2) The conditions specified when searching, consisting of one or several search terms and search parameters.
�search cache: A buffer that holds the data and results of previous search requests.
�search condition: A criterion for selecting rows from a table. A search condition consists of one or more predicates.
�search criteria: (1) Attribute values that are used to retrieve a stored item.; (2) In Information Integrator for Content, specific fields that an administrator defines for a search template that limit or further define choices available to the users.
�search engine: A program that accepts a search request and returns a list of documents to the user.
�search field: In a DL/I call, a field that is referred to by one or more SSAs. See also key field.
�search handle: For System i Access, a number returned by the system to an application program when the application program requests a search. The search handle is used by the application program to request subsequent searches.
�search index: An index of related topics that can be searched or browsed. The system-recognized identifier for the object type is *SCHIDX.
�search index database: The database files used by document library services for storing descriptive information about documents and folders (such as keywords, subjects, dates, and so forth). These database files are used when a search of the document library is requested on one or more document descriptors.
�search index file: A file in which an index is stored in the search engine.
�search path: A list of directories searched by the shell when a command path name is not specified.
�search result: A list of documents that match the search request.
�search template: A form, consisting of search criteria designed by an administrator, for a specific type of federated search. The administrator also identifies the users and user groups who can access each search template.
�search value: User-defined information that is used either to make a list of filed documents with similar document details or content, or to find a directory entry.
�Seascape architecture: A storage system architecture developed by IBM for open-systems servers, and S/390 and zSeries host systems. It provides storage solutions that integrate software, storage management, and technology for disk, tape, and optical storage.
�seat: To fit correctly into position.
�SECMEC: See security mechanism.
�secondary authorization ID: In DB2 for z/OS, an authorization identifier that is associated with a primary authorization ID by an authorization exit routine. See also primary authorization ID.
�secondary axis: In the GDDM function, a horizontal or vertical axis drawn parallel to the primary axis and capable of having a title, ticks, and labels different from those of the primary axis. See also primary axis.
�secondary console: In a system with multiple consoles, any console other than the master console.
�secondary data set group: In a database, the dataset group or groups defined in addition to the primary data set. A secondary data set group is normally defined to improve utilization of auxiliary storage. See also data set group, primary data set group.
�secondary device: One of the devices in a dual-copy or remote-copy logical-volume pair that contains a duplicate of the data on the primary device. Unlike the primary device, the secondary device can accept only a limited subset of channel commands. See also primary device.
�secondary disk pool: An independent disk pool that defines a collection of directories and libraries and must be associated with a primary disk pool.
�secondary domain: The domain that is defined by the DNS domain database file that a secondary name server has obtained from a master name server.
�secondary file: (1) In RPG, any input file other than the primary file.; (2) For certain types of join operations using Query, all files except the first file that are joined in a query definition for the purpose of getting data.; (3) In the DDS for a join logical file, any physical file, other than the first physical file, that is specified on the JFILE keyword. See also primary file.
�secondary GPFS cluster configuration server: In a GPFS cluster, the node chosen to maintain the GPFS cluster configuration data in the event that the primary GPFS cluster configuration server fails or becomes unavailable.
�secondary group buffer pool: For a duplexed group buffer pool, the structure that is used to back up changed pages that are written to the primary group buffer pool. No page registration or cross-invalidation occurs using the secondary group buffer pool. The z/OS equivalent is "new structure." See also primary group buffer pool.
�secondary index: (1) In IMS or VSAM, any index used to provide a path for access to a data set other than that provided by the primary keys. See also alternate index.; (2) A nonpartitioning index on a partitioned table. See also nonpartitioned index.
�secondary index database: An index that is used to establish accessibility to a physical or logical database by a path that is different from the one provided by the database definition. A secondary index contains an index pointer segment type that is defined in a secondary index database.
�secondary language: One or more additional national languages that can be installed on the system to display and print information. See also primary language.
�secondary link: The optical connection between two remote bus adapter cards.
�secondary log: A set of one or more log files used to record changes to a database when the primary log is full. See also primary log.
�secondary logical unit (SLU): In SNA, the logical unit (LU) that contains the secondary half-session for one logical unit-to-logical unit (LU-to-LU) session. See also primary logical unit.
�secondary logical unit (SLU): A nonhost port through which the end user gains access to the services of the network. Normally, a nonhost program that resides within a controller or control unit.
�secondary name server: (1) A name server that gets its domain data from a primary name server by way of a zone transfer.; (2) A Domino server that can stand in for a Notes user's home server to ensure that the Notes Name Service is always available over TCP/IP.
�secondary partition: A logical partition that has certain dependencies on the primary logical partition, but otherwise is independent from the primary logical partition. For example, a secondary logical partition may be powered off and on, dumped, or installed without affecting other logical partitions.
�secondary processing sequence: In a database, the hierarchic order of segment types in a physical or logical database that results automatically when a database is accessed through a secondary index.
�secondary referential constraint: The constraint that occurs when a unique constraint or a primary key constraint is added to file that is a parent file in a defined referential constraint relationship. The referential constraint is regarded as secondary processing because the primary request is for the processing of the unique constraint or the primary key constraint.
�secondary request: In a multisystem environment, a message inserted to a transaction code destination by an application program. See also primary request, reply.
�secondary space allocation: The amount of additional space requested by the user for a data set when existing space is full. See also primary space allocation.
�secondary system name: An alternative system name that can be used to identify a system in a SNADS network. See also primary system name.
�secondary system name table: In SNADS, the table containing all the system names that can be used to identify the local system for distributions arriving on the system.
�secondary thread: Any thread that is started by, or on behalf of, the application that is not the initial thread. See also initial thread.
�secondary virtual disk: Pertinent to remote copy, the virtual disk (VDisk) in a relationship that contains a copy of data written by the host application to the primary VDisk. See also relationship.
�secondary vital-record specification: The second retention and movement policy that DFSMSrmm matches to a data set and volume used for disaster recovery and vital records purposes. See also vital record specification, primary vital-record specification.
�secondary window: A window that obtains or displays supplemental information that is often related to the objects that appear in a primary window. Dialog boxes and message boxes are secondary windows.
�second backup object: The second backup copy of an object, which is stored in the object-backup storage group that is specified as a second, object-backup, storage group. See also object backup-storage group.
�second-level destination: The part of a JES2 destination identifier that indicates a remote workstation, special local-route code, or user ID at the target node to which input is to be sent. See also first-level destination.
�section: (1) The segment of a plan or package that contains the executable structures for a single SQL statement. See also SQL and XQuery compiler.; (2) In COBOL, a set of zero, one, or more paragraphs or entries preceded by a section header. Each section consists of a section header and the related section body.; (3) A defined area on a Notes form that can include fields, objects, layout regions, and text. Sections can be set to display (expand) or hide (collapse).; (4) A named collection of program object components, called elements. Each section is assigned a name in binder control statements.; (5) A unit of code or data produced by the compiler. Sections do not have attributes. See also segment.
�sector: (1) In disk storage, an addressable subdivision of a track used to record one block of a program or data.; (2) The smallest amount of information that can be written to or read from a disk or diskette during a single read or write operation.
�secure: To control who can use and to what extent an object can be used by controlling the authority given to the user.
�Secure Association Service (SAS): An authentication protocol used to communicate securely for the client principal by establishing a secure association between the client and server.
�secure chat: A chat that is encrypted. The default is set for all chats to be encrypted. The default can be changed in Preferences or when initiating a chat with multiple participants. See also secure meeting.
�Secure Electronic Transaction (SET): An industry standard for secure credit card and debit card payments over open networks such as the Internet. The SET protocol ensures confidentiality of information, integrity of all transmitted data, authentication of the cardholder and the merchant, and interoperability.
�Secure Hash Algorithm (SHA): An encryption method in which data is encrypted in a way that is mathematically impossible to reverse. Different data can possibly produce the same hash value, but there is no way to use the hash value to determine the original data.
�Secure Hash Algorithm digest (SHA digest): A character string used to identify a GPFS security key.
�Secure Hypertext Transfer Protocol: A security-enhanced variation of HTTP. S-HTTP allows servers and clients to authenticate each other and to define the kind of security used in transmissions. S-HTTP is an alternative to another well-known security protocol, Secure Sockets Layer (SSL). See also secure server.
�secure interface: For security gateways, the physical layer connection between the gateway and a secure network. See also nonsecure interface.
�Secure Internet Protocol Network: A SWIFT network based on the Internet Protocol (IP) and related technologies.
�secure meeting: An online meeting that is encrypted. During meeting creation, the person scheduling the meeting has the option to secure the meeting by choosing encryption. See also secure chat.
�secure/MIME (S/MIME): A secure version of the MIME protocol that allows users to send encrypted and electronically signed mail messages, even if users have different mail programs.
�secure network: A set of nodes that are controlled by a single administrative party. See also nonsecure network.
�secure server: A server that encrypts files that it is sending and decrypts files that it has received to facilitate secure communication with a client. See also Secure Hypertext Transfer Protocol.
�Secure Sockets Layer (SSL): A security protocol that provides communication privacy. With SSL, client/server applications can communicate in a way that is designed to prevent eavesdropping, tampering, and message forgery.
�SecureWay Directory: An LDAP directory that can store user-related data, such as the user ID, the user name, and passwords.
�security: The protection of data, system operations, and devices from accidental or intentional ruin, damage, or exposure.
�security administration: The administration of roles and the assignment of roles in conjunction with organizational units to users. See also system configuration administration, configuration administration.
�security administrator: (1) A programmer who manages, protects, and controls access to sensitive information.; (2) The person who controls access to business data and program functions.; (3) An individual who is responsible for managing security within a database.
�security administrator authority: A special authority that allows a user to add users to the system distribution directory, to create and change user profiles, to add and remove access codes, and to perform office tasks, such as delete documents, folders, and document lists, and change distribution lists for other users.
�Security Assertion Markup Language (SAML): An XML framework for exchanging authentication and authorization information.
�Security Association (SA): A contract between a local key server and a remote key server. This contract protects data exchanges.
�security attribute propagation: The transportation of security attributes from one server to another server in a WebSphere Application Server configuration.
�security category: A non-hierarchical grouping of sensitive information used to control access to data.
�security classification: (1) In RACF, the use of security categories, a security level, or both, to impose access controls. See also security level.; (2) An installation-defined level of security printed on the separator pages of printed output.
�security compliance check: A type of compliance check that is used to check for a variety of security issues. See also software compliance check.
�security constraint: A declaration of how to protect Web content, and how to protect data that is communicated between the client and the server.
�security context: The digitally signed token that identifies a principal, lists the roles and access rights for the principal, and contains information about when the token expires.
�security definition: In z/OS, a member containing the definitions for one identification label. These definitions include instructions for the overlay name, and the size and origin of paper to be used.
�security definitions library: In z/OS, a partitioned data set or a series of concatenated partitioned data sets that contain the security definitions for an entire system.
�security domain: The set of all the servers that are configured with the same user registry realm name.
�security DST capability: A dedicated service tools (DST) capability used by a service representative or an experienced system user that provides access to all DST functions.
�security enabling interface (SEI): The WebSphere MQ interface to which customer- or vendor-written programs that check authorization, supply a user identifier, or perform authentication must conform. A part of theWebSphere MQ Framework.
�security entity: Entities used to specify what a user is authorized to do. Security entities include roles and users.
�security exit: A channel exit program that is called immediately after the initial data negotiation has completed on channel startup. Security exits normally work in pairs and can be called on both message channels and MQI channels. The primary purpose of the security exit is to enable the message channel agent (MCA) at each end of a channel to authenticate its partner.
�security group: In a Tivoli environment, a group of managed resources over which a Tivoli administrator is granted authority. Examples of a security group include a policy region and the administrator collection.
�security id: See security identifier.
�security identifier (security id): On Windows systems, a supplement to the user ID that identifies the full user account details on the Windows security account manager database where the user is defined.
�security label: (1) In RACF, an installation-defined name that corresponds to a specific RACF security level with a set of security categories.; (2) In a trusted computing base, a label used to maintain multiple levels of security on a system. This label is a combination of a security class and a security level. See also identification label.; (3) In label-based access control (LBAC), a database object that can be granted to users and can also be applied to columns and rows in a table to protect the data. Only users who are granted appropriate security labels can access data that is protected by a security label. See also label-based access control, security label component, security policy.; (4) A classification of users' access to objects or data rows in a multilevel security environment.
�security label component: In label-based access control, a database object that represents one of the criteria that an organization uses to decide who has access to specific data. See also security label, element.
�security level: In RACF, an installation-defined name that is associated with a number in the range 1 through 254. The security level increases as the numbers become higher. See also security classification.
�security log: A log that maintains a history of administrator login activity generated by the administrative server.
�security manager domain: A CICS domain that handles all the interfaces to the external security manager, for example, RACF.
�security mechanism (SECMEC): A technical tool or technique that is used to implement a security service. A mechanism might operate by itself, or in conjunction with others, to provide a particular service. Examples of security mechanisms include access control lists, cryptography, and digital signatures.
�security message: One of the messages, sent by security exits that are called at both ends of a channel, to communicate with each other. The format of a security message is not defined and is determined by the user.
�security officer: A person assigned to control all of the security authorizations provided with the system. A security officer can, for example, remove password or resource security or add, change, or remove security information about any system user.
�security overlay: An overlay, such as one created by use of Overlay Generation Language, that resides in a secure library and is used to place security resources on a page.
�security permission: Authorization granted to access a system resource.
�security policy: (1) A written document that defines the security controls that you institute for your computer systems. A security policy describes the risks that you intend these controls to minimize and the actions that should be taken if someone breaches your security controls.; (2) In label-based access control, a database object that is associated with one or more tables and that defines how LBAC can be used to protect those tables. The security policy defines what security labels can be used, how the security labels are compared to each other, and whether optional behaviors are used. See also label-based access control, security label.
�Security Policy Index (SPI): A value that the local systems and remote systems use to identify a particular Security Association (SA).
�security profile: A role-based security model that supports classes of service, which have different levels of access to system and repository information.
�security registry: The database of user IDs, passwords, and user descriptions for a local workstation.
�security-relevant: Pertaining to anything that occurs on the system that affects, either positively or negatively, the safety and integrity of the system's processes and data.
�security role: In Java EE, an abstract logical grouping of users that is defined by the application assembler. When an application is deployed, the roles are mapped to security identities, such as principals or groups, in the operational environment. (Sun)
�security role reference: A role that defines the access levels that users have and the specific resources that they can modify at those levels.
�security service: A service within a computer system that protect its resources. Access control is an example of a security service.
�Security Support Provider Interface (SSI): The means for networked applications to call one of several security support providers (SSPs) to establish authenticated connections and to exchange data securely over those connections. It is available for use on Windows systems.
�security token: (1) In RACF, a collection of security information that represents data to be accessed, a user, or a job. A security token contains a user ID, a group ID, a security label, the node of origin, and other information.; (2) A representation of a set of claims that are made by a client that can include a name, password, identity, key, certificate, group, privilege, and so on.
�see also entry: A cross-reference from one index entry to additional information. See also see entry.
�seed: A value that adds randomness to the creation of pseudorandom numbers.
�seed file: A file, containing a list of nodes within an administrative domain, that helps create the network topology map.
�seed list page: In WebSphere Portal, an XML page that contains links to the pages that are available on a portal. Crawlers use the seed list to identify the documents to crawl. The seed list page also contains metadata that is stored with the crawled documents in the enterprise search index.
�see entry: A cross-reference to a preferred term from obsolete terms, selected synonyms, or terms used by competitive products. See also see also entry.
�seek: To position the read/write head of a disk unit or a diskette unit.
�segment: (1) One or more contiguous elements of a string.; (2) For TCP/IP, the unit of end-to-end transmission in the TCP. A segment consists of control information and data fields. A segment is transmitted as an IP datagram.; (3) A part of a program that can be run without the entire program being in main storage.; (4) In IMS, the unit of access to a database; for the database system, the smallest amount of data that can be transferred by one IMS operation. For input terminal operations using IMS TM, a segment is defined by the particular terminal type and is obtained by the application program with one call.; (5) A group of pages that holds a row of a single table.; (6) A collection of composed text and images, prepared before formatting and included in a document when it is printed.; (7) In data mining, a group of input data records within a data set that have similar characteristics. Each group is called a segment. Within a segment, each piece of data is evaluated (or scored) for the degree to which it fits the segment to which it belongs. This statistical conformance is represented by a number, called the score, which ranges between 0.0 and 1.0. In DB2 Intelligent Miner, this concept is known as a cluster.; (8) A unit of code or data produced by the linker and existing only in an executable image of the program. The linker assigns attributes to sections, orders and groups them, and puts them into segments. See also section.
�segmentation: (1) The division of text into segments, usually words, sentences and paragraphs.; (2) The division of text into distinct lexical units. Nondictionary-based processing includes white space and n-gram segmentation, while dictionary-based support includes word, sentence, and paragraph segmentation, and lemmatization.
�segmentation violation: An error caused when a program attempts to access memory not allocated to it.
�segment directory: A file containing the format of all EDI segments in an EDI standard.
�segmented table space: A table space that is divided into equal-sized groups of pages called segments. Segments are assigned to tables so that rows of different tables are never stored in the same segment. See also table space, universal table space.
�segment identifier: A unique three-character identifier at the beginning of each EDI segment.
�segment ID number: One or more numbers used to identify a voice or prompt segment.
�segment ID separator: The character that separates the segment identifier from the EDI data elements in the EDI segment. See also data element delimiter.
�segmenting: In OSI, a function performed by an (N)-entity to map one (N)-service-data-unit into multiple (N)-protocol-data-units.(I) Segmenting is the opposite of reassembly.
�segment-number: In COBOL, a user-defined word that classifies sections in the Procedure Division for purposes of segmentation. Segment numbers can contain only the characters 0 through 9. A segment-number can be expressed either as a 1- or 2-digit number.
�segment occurrence: In a database, an instance of a segment type. See also segment type.
�segment search argument (SSA): The portion of a DL/I call that identifies a segment or group of segments to be processed. Each SSA contains a segment name and, optionally, one or more command codes, and one or more qualification statements. Multiple SSAs may be required to identify the desired segment. See also qualified segment search argument, unqualified segment search argument.
�segment terminator: The character that marks the end of an EDI segment.
�segment type: In a database, a user-defined category of data. See also segment occurrence.
�SEI: See security enabling interface.
�seion: A Japanese syllable.
�select: To highlight a choice so that a subsequent action will use that choice. Selecting does not initiate the action.
�select function: A system function that determines which records from a physical file are to be included in a logical file. See also omit function.
�selection border: The visual border that appears around a control, allowing that control to be moved with the mouse or keyboard.
�selection character: A character used to select a choice in a selection list or a selection field.
�selection data set: In aggregate backup and recovery processing, a sequential data set or a member of a partitioned data set (PDS) used to define the data sets that compose the input. The selection data set contains any include, exclude, accompany, or allocate lists.
�selection entry: In System Manager, an entry that assigns each alert processed by the filter to a group. In this way, many alerts can be grouped into manageable categories.
�selection field: A panel element that contains a fixed number of choices in which the user cannot page up or page down.
�selection list: In SAA Advanced Common User Access architecture, a set of choices that a user can scroll through to make a selection.
�selection priority: See scheduling priority.
�selective backup: The process of backing up selected files or directories from a client domain.
�selective prompting: A function of the operating system that allows the user to tailor command prompts at a parameter level. See also conditional prompting.
�select/omit field: A field in a logical file record format whose value is tested by the system to determine if records including that field are to be used. The test is a comparison with a constant, the contents of another field, a range of values, or a list of values; and the record is either selected or omitted as a result of the test.
�select/omit level specifications: Data description specifications coded on the lines following the last key-field specification. These specifications are permitted only in a logical file.
�selector: An identifier for a data item. In the WebSphere MQ Administration Interface (MQAI), there are two types of selector: a user selector and a system selector.
�selector component: A component that provides a means of interposing a dynamic selection mechanism between the client application and a set of target implementations.
�self-check digit: The far right digit of a self-check field.
�self-check field: A field, such as an account number, consisting of a base number and a self-check digit. For data entry applications, the operator-entered self-check number is compared with the self-check number calculated by the system.
�self-configure: To adapt to dynamically changing environments. See also autonomic computing.
�self-defining element: An element for which no matching definition exists in the message model. See also self-defining message, predefined element.
�self-defining message: An message for which no matching definition exists in the message model. For example, a message coded in XML is self-defining. See also predefined message, self-defining element.
�self-heal: To discover, diagnose, and act to prevent disruptions.
�self-healing: Pertaining to an on-demand operating environment that responds automatically to problems, security threats, and system failures. Also describes the ability, in autonomic computing, to discover, diagnose, and prevent disruptions. See also on demand operating environment.
�self-optimize: To tune resources and balance workloads to maximize the use of IT resources.
�self-protect: To anticipate, detect, identify, and protect against attacks.
�self-referencing constraint: A referential constraint that defines a relationship in which a table is a dependent of itself.
�self-referencing row: A row that is a parent of itself.
�self-referencing table: A table that is both a parent and a dependent table in the same referential constraint.
�self-registration: The process by which a user can enter required data and become a registered user, without the involvement of an administrator.
�self test: A test that runs automatically after a device is turned on.
�self-timed interface (STI): An interface that has one or more conductors that transmit information serially between two interconnected units without requiring any clock signals to recover the data. The STI performs clock recovery independently on each serial data stream and uses information in the data stream to determine character boundaries and inter-conductor synchronization.
�self-transition relationship: In UML modeling, a relationship that indicates that the active state does not change when an object in the source state receives a specified event, performs a specific action, or meets a certain condition. See also transition relationship.
�seller: (1) A defined role in WebSphere Commerce that has access to all WebSphere Commerce Accelerator capabilities. See also expected inventory, expected inventory record.; (2) The role that supervises the overall store objectives and management, in addition to tracking the store sales. The seller role is equivalent to a merchant.
�seller administrator: The seller administrator manages the information for the selling organization. The seller administrator creates and administers the suborganizations within the selling organization and the various users in the selling organization, including the assignment of appropriate business roles.
�semantic model: In the Reusable Asset Specification (RAS), a model that describes the nature of core elements of an asset. The model elaborates on specific elements of an asset, providing insight to the asset's structure as captured in the asset structure model.
�semantics: The relationships of characters or groups of characters to their meanings, independent of the manner of their interpretation and use. Semantics is the meaning conveyed by a character string. See also syntax.
�semantic search: A type of keyword search that incorporates linguistic and contextual analysis. See also text analysis.
�semantic type: The usage or rules for an item. Base, annotation, and note are semantic types supplied by Content Manager; users can also define their own semantic types. See also item.
�semantic variation point: A point of variation in the semantics of a metamodel. It provides an intentional degree of freedom for the interpretation of the metamodel semantics.
�semaphore: (1) A mechanism that is used to synchronize one or more jobs.; (2) An indicator used to control access to a file. For example, in a multiuser application, a semaphore is a flag that prevents simultaneous access to a file.; (3) In UNIX systems, a general method of communication between two processes that extends the features of signals.; (4) An object used by multi-threaded applications for signaling purposes and for controlling access to serially reusable resources. Processes can be locked to a resource with semaphores if the processes follow certain programming conventions.
�semaphore adjustment value: A value associated with a semaphore and applied to the semaphore's value if a process ends while holding resources represented by the semaphore.
�semaphore set: An interprocess communications mechanism that contains one or more semaphores.
�semi-automatic mode: An operating mode in which all deployment requests are automatically generated, and then manually reviewed and approved by an administrator before being executed.
�semicolon: In REXX, a token that indicates the end of a clause and is implied by the REXX interpreter in three cases: by the end of a line, by certain keywords, and by a colon if it follows a single symbol.
�send and forget: See datagram.
�send depth: In SNADS, the number of items that must be on the distribution queue before any item is sent to the next system.
�sender: The object passing a stimulus to a receiver object. See also receiver, receive.
�sender bean: In extended messaging, an enterprise bean (stateless session bean) that can be built to send asynchronous messages. A sender bean translates its method invocation into a JMS message, then passes that message to JMS. It can also retrieve a response message, translate that message into a result value, and return it to the caller.
�sender channel: In message queuing, a channel that initiates transfers, removes messages from a transmission queue, and moves them over a communication link to a receiver or requester channel.
�send exit: A type of channel exit program that is called just before a message channel agent (MCA) issues a communications send to send a unit of data over a communications connection. See also receive exit.
�sending cross-domain key: In Cryptographic Support, a cross-domain key used to encrypt a data-encrypting key before it is sent to another location.
�send queue: In Q replication, a WebSphere MQ message queue that is used by a Q Capture program to publish transactions that it has captured. A send queue can be used either for Q replication or event publishing, but not both at the same time.
�send time: In SNADS, the values that specify the time that distributions are sent to other locations in a network. The from and to times inclusively specify the range during which distributions can be sent; the force time specifies the time at which distributions are sent regardless of the number of items in the queue.
�senior role: See authorization role.
�sense code: A value sent or received, or a negative response to indicate what error occurred.
�sense data: (1) In SNA, data sent with a negative response, indicating the reason for the response.; (2) In printers, sense information used to indicate the causes of command-stream and device exceptions and to direct the host program to the appropriate exception-recovery actions.
�sense type and model (STM): Command sent by the operating system to detect the type and model of an attached printer.
�sensitive cursor: A cursor that is sensitive to changes made to a database after the result table has been materialized. See also cursor, cursor sensitivity.
�sensitive segment: A segment type in a database to which an application program is sensitive.
�sensitivity: (1) A level of classification of information as defined by the X.400 Standard. Mail items can be assigned a sensitivity of none, personal, private, or confidential.; (2) An IMS capability that ensures that only data segments or fields predefined as "sensitive" are available for use in a particular application. The sensitivity concept also provides a degree of control over data security, inasmuch as users can be prevented from accessing particular segments or fields by omission of those segments or fields from the logical database. Sensitivity is implemented through the DB PCB.; (3) The amount of time by which a threshold-based health indicator must exceed its threshold or the amount of time that a state-based health indicator must be in a non-normal state before an alert is generated.
�sensor: (1) A device that converts measurable elements of a physical process into data that is meaningful to a computer.; (2) Software that monitors security networks, applications, or systems for security-related information, possibly indicative of suspicious activity.; (3) An interface that exposes information about the state and state transitions of a managed resource. A sensor is used to retrieve data from a managed resource, whereas an effector is used to alter data in a managed resource. See also managed resource, effector, externalized data value, manageability interface, touchpoint.; (4) A program that reads information from a managed software system to create configuration information.
�sensor event: An intrusion detection event that is reported by a sensor or adapter.
�sensor event adapter: Software that intercepts information generated by one or more sensors, filters the data, reformats the data into an appropriate sensor event, and forwards the sensor event.
�sensor value: In a policy-enabled system, a data value that is returned by a sensor and that can be used by a policy. See also sensor.
�sentence: In COBOL, a sequence of one or more statements, the last of which is stopped by a separator period.
�SEPA: See Software Engineering Process Authority.
�separate search space: An implementation of the Product Advisor. For this style of implementation, additional database tables must be created that contain metadata to facilitate searching a particular category of products. See also base search space.
�separator: A punctuation character that separates parts of a command or file, or that delimits character strings.
�separator page: An identifying sheet of paper between successive jobs.
�sequence: (1) To arrange in order.; (2) A database object that is independent of any one table that automatically generates unique key values based on initial user specifications.; (3) A sequentially ordered flat collection.; (4) In the XQuery and XPath data model, an ordered collection of zero or more items. See also XQuery and XPath data model.; (5) In fibre-channel technology, a group of related frames transmitted in the same direction between two node ports (N_ports).
�sequence checking: (1) In RPG, a function that checks the sequence of records in input, update, or combined files used as primary and secondary files.; (2) The process of verifying the order of a set of records relative to some field's collating sequence.
�sequence diagram: A UML structural diagram that shows the chronological sequence of messages between instances (objects or classifier roles) that work together in an interaction or interaction instance. See also collaboration diagram, lifeline.
�Sequenced Packet Exchange protocol (SPX): A session-oriented network protocol that provides connection-oriented services between two nodes on the network, and is used primarily by client/server applications. It relies on the Internet Packet Exchange (IPX) protocol, provides flow control and error recovery, and guarantees reliability of the physical network.
�sequence errors: In Performance Tools, the number of frames received by the terminal equipment (TE) that contained sequence numbers indicating that frames were lost.
�sequence field: The field in a database segment that used to store segment occurrences in sequential ascending order.
�sequence grouping: The specification of the order in which entity beans update relational database tables.
�sequence number: (1) The number of a record that identifies the record within the source member.; (2) A field in a journal entry that contains a number assigned by the system. This number is initially 1 and is increased until the journal is changed or the sequence number is reset by the user.; (3) A 2-byte field in the structured field introducer that identifies the position of the structured field in the data set.; (4) A number assigned to each message exchanged between two nodes. The number is increased by one for each successive message. It starts from zero each time a new session is established.
�sequence number wrap value: In WebSphere MQ, a method of ensuring that both ends of a communication link reset their current message sequence numbers at the same time. Transmitting messages with a sequence number ensures that the receiving channel can reestablish the message sequence when storing the messages.
�sequence page: A page in the settings of a composite project that allows the user to specify the order in which projects are built.
�sequence set: The lowest level of the index of a key-sequenced data set (KSDS); it gives the locations of the control intervals in the data set and orders them by the key sequence of the data records they contain. The sequence set and the index set together comprise the index. See also index set.
�sequence type: A data type that can be expressed by using the SequenceType syntax, which describes the type of an XQuery value. Sequence types are used to refer to a data type in an XQuery expression.
�sequential access: (1) A mode of accessing data on a medium in a manner that requires the storage device to access consecutive storage locations on the medium.; (2) The retrieval or storage of a VSAM or SAM data record in either its physical order or its collating sequence relative to the previously retrieved or previously stored record.; (3) The process of referring to records one after another in the order in which they appear on the file. See also access mode.
�sequential access method (SAM): An access method for storing, deleting, or retrieving data in a continuous sequence based on the logical order of the records in the file.
�sequential buffering (SB): Efficient sequential input buffering techniques that reduce the elapsed time required to sequentially process large IMS OSAM databases.
�sequential-by-key processing: A method of processing indexed files in which records are read or written in the order of the key field in the record.
�sequential concatenation: The allocation of sequential data sets, partitioned data set (PDS) members, partitioned data set extended (PDSE) members, UNIX files, or any combination of these such that the system retrieves them as a single, sequential, data set. See also data set concatenation.
�sequential data set: A data set whose records are organized on the basis of their successive physical positions, such as on magnetic tape. See also partitioned data set, direct data set.
�sequential data set input (SDI): A batch utility used to import messages from a sequential data set or a tape into MERVA ESA queues.
�sequential data set output (SDO): A batch utility used to export messages from a MERVA ESA queue to a sequential data set or a tape.
�sequential data set system printer (SDY): A batch utility used to print messages from a MERVA ESA queue.
�sequential data striping: A software implementation of the striping of a disk array that distributes data sets across multiple volumes to improve performance.
�sequential dependent segment (SDEP): A segment of a data entry database that is chained off the root segment and inserted (last-in first-out) into the last part of a DEDB area. After being inserted by an online program, the SDEP cannot be modified. See also data entry database.
�sequential file: (1) See sequential data set.; (2) For Network File System (NFS), a type of MVS file that has its records stored and retrieved according to their physical order within the file. It must be on a direct access volume.
�sequential millisecond response: A parameter specified in the definition of a storage management subsystem (SMS) storage class indicating the desired response time to read the next 4-KB block of a data entity assuming the prior 4-KB block has been read.

�sequential organization: In COBOL, the permanent logical file structure in which a record is identified by a predecessor-successor relationship that is established when the record is placed into the file.
�sequential prefetch: A mechanism that triggers consecutive asynchronous I/O operations. Pages are fetched before they are required, and several pages are read by using a single I/O operation.
�sequential processing: A method of processing in which records are read, written to, or deleted in the order determined by the value of the key field. See also consecutive processing, random processing.
�sequential read: A set of several consecutive blocks that are read with a single read I/O operation. Sequential reads are issued by the Sequential Buffering (SB) component of IMS in order to reduce the elapsed time required to sequentially process large IMS OSAM databases.
�sequential stage group: The number of tracks that are obtained in advance for a sequential operation.
�sequential VDisk: A virtual disk (VDisk) that uses extents from a single managed disk (MDisk).
�sequential-within-limits processing: A method of processing indexed files in which limits are specified for the beginning and ending values of the key field for the records to be read or written.
�serial connection: A method of device interconnection for determining interrupt priority by connecting the interrupt sources serially.
�serial cursor: See nonscrollable cursor.
�serial database: See also partitioned environment.
�serial device: A device that uses serial data as opposed to parallel data.
�serialization: (1) The process of handling files or directories that are modified during backup or archive processing.; (2) The process of controlling access to a resource to protect the integrity of the resource.; (3) The consecutive ordering of items.; (4) In Q replication, the process of applying transactions in the same order in which they were committed at the source.; (5) In object-oriented programming, the writing of data in sequential fashion to a communications medium from program memory.
�serialize: To convert an XML value into a character string or binary string form. This process is the inverse of parsing.
�serialized profile: A Java object, one or more of which is produced by the SQLJ translator, that contains SQL statements and descriptions of host variables. A serialized profile file is used to describe the SQL statements so that they can be run with either with a JDBC-based or a customized runtime library.
�serialized XML: An XML value in the form of a character string or binary string. See also XML data.
�serializer: A method for converting object data to another form such as binary or XML. See also deserialization.
�serial line: A transmission medium commonly used for point-to-point link connections. Often, a serial line consists of an RS-232 connection into a modem over a telephone line.
�Serial Line Internet Protocol (SLIP): An Internet protocol that connects a computer to the Internet using a serial line.
�serially reusable: The reusability attribute with which a program can be used sequentially by multiple tasks. A serially reusable module cannot be entered by a new task until the previous task has exited.
�serial port: A connector on a serial device to which cables for other devices are attached.
�serial search: In COBOL, a search in which the records of a set of records are consecutively examined, beginning with the first record and ending with the last record.
�Serial Storage Architecture (SSA): An American National Standards Institute (ANSI) standard, implemented by IBM, for a high-speed serial interface that provides point-to-point connection for peripherals, such as storage arrays. See also Redundant Array of Independent Disks, spatial reuse, SSA adapter.
�series definition table (SDT): A CICS table that holds, for each journal, the name, size, and pointers to the first and current volume descriptors.
�servant region: A contiguous area of virtual storage that is dynamically started as load increases and automatically stopped as load eases.
�server: (1) A software program or a computer that provides services to other software programs or other computers. See also host, client.; (2) In WebSphere MQ, a queue manager that provides queue services to client applications running on a remote workstation.; (3) A definition that identifies where an application will be tested or published. See also host.; (4) The target of a request from a remote requester. In a DB2 database system, the server function is provided by the distributed data facility, which is used to access a DB2 database from remote applications.
�server addressing information: In DCE Remote Procedure Call (RPC), an RPC protocol sequence, a network address, and an endpoint that represent one way to access an RPC server over a network. Server addressing information is a part of server binding information.
�server and bus environment: The environment in which servers, service integration buses, and their resources are configured and managed.
�server application thread: In DCE Remote Procedure Call (RPC), a thread running the server application code that initializes the server and listens for incoming calls.
�server-based certificate authority: A certificatie authority (CA) that runs under the CA process, a server task. It can be either a Notes or Internet certifier. The CA process can handle any number of Notes and Internet certifiers, and it gives administrators the ability to manage them from the server console, using Tell commands. The CA process also gives Internet certifiers the ability to issue certificate revocation lists (CRLs).
�server binding information: In the Distributed Computing Environment (DCE) Remote Procedure Call (RPC), information about the location of the server.
�server certificate: An electronic stamp stored in the server's key ring file that contains a public key, a name, an expiration date, and a digital signature. The server certificate uniquely identifies the server.
�server channel: In message queuing, a channel that responds to a requester channel, removes messages from a transmission queue, and moves them over a communication link to the requester channel. See also requester channel.
�server cluster: A group of servers that are typically on different physical machines and have the same applications configured within them, but operate as a single logical server.
�server command: A command for performing a task, such as shutting down or restarting a server. A server command can be run manually at the console or automatically through the use of Program document.
�server complex: In z/VM Center, a configuration profile for Linux guest systems that includes both Linux and z/VM aspects. A server complex can define network settings, Linux configuration scripts, disk access, and VM Resource Manager (VMRM) performance goals.
�server configuration: A resource that contains information required to set up and deploy to an application server.
�server connection: A document that is in the Domino Directory or a user's Personal Address Book and that defines a connection to a server. There are four types of server connection documents: dialup, network, passthru, and remote LAN.
�server connection channel type: The type of MQI channel definition associated with the server that runs a queue manager. See also client connection channel type.
�server definition: (1) The characteristics of a specific content server that uniquely identify it to Information Integrator for Content.; (2) In a federated system, the name and information that define the data sources to the federated database. The server definition is used by the wrapper when SQL statements that use nicknames are submitted to the federated database.
�Server Display Control (SDC): An ADSI control mode in which the ADSI telephone is controlled through a dialog with a voice response system.
�server distributed sync point resource manager (SDSRM): A resource manager that extends protection to resources across multiple nodes using a client/server protocol.
�server document: A document that defines many of the settings that control how a Domino server operates. The server document is set up when the administrator or administrators register a server. The server document also enables mail routing
�server entry: In the Distributed Computing Environment (DCE)Remote Procedure Call (RPC), an entry in the name server database that stores binding information associated with the RPC interfaces of a particular RPC server and object Universal Unique Identifiers (UUIDs) for any objects offered by the server.
�server firmware: The code that resides in system flash memory, and includes a number of subcomponents, including POWER Hypervisor, power control, service processor, and logical partition firmware that is loaded into either AIX or Linux logical partitions.
�server-free data movement: The direct movement of client data by a third party data mover between source disks and target storage devices, all of which are on a storage area network (SAN). See also LAN-free data movement.
�server group: See computer group.
�server implementation object: Enterprise beans that client applications require to access and implement the services that support those objects.
�server instance: (1) A logical server that consists of a set of server jobs and configuration objects. Each server instance listens on either a unique IP address or a unique port with the same IP address. A server instance is created, configured, deleted, or controlled from the administration server. The configuration of each server instance is determined by the name of an associated configuration file, instance parameters, and values that are specified on the Configuration and Administration Forms and on the Global Attribute Values page.; (2) See server.
�server inventory: The comprehensive list of native entities and native attributes from specified content servers.
�server IPL: An initial program load (IPL) whereby all logical partitions on the server are shut down at the same time. This allows, for example, a new level of the server firmware to be activated on the server.
�server job: A job that is compiled and run on the DataStage server to connect to databases on other computers, extract and process data, and then write the data to the target data warehouse.
�server message: A message that is routed to a server application for processing, or a delivery notification that is routed to a client application to acknowledge the receipt of a client message by its destination.
�Server Message Block: A protocol that manages requests and responses in a client/server environment so that clients on a network can share files, directories, and devices.
�server migration: The process of moving data from one storage pool to the next storage pool defined in the hierarchy, based on the migration thresholds defined by the storage pools.
�server mode: A processing mode of the dump job function that runs in its own address space and can use any tape devices in the system.
�server name: An identifier that designates an application server. In a federated system, the server name also designates the local name of a data source. See also database name, alias.
�server node: In a single system image (SSI), a DirectTalk system that contains either the DirectTalk DB2 database, or the voice data, or both.
�server operation: A collection of Java or non-Java process definitions that you can define to run on middleware servers. You can create server operations to enable or disable tracing, start or stop applications, query the running state of a server, and so on.
�ServerPac: A software-delivery package consisting of products and service for which IBM has performed the System Modification Program/Extended (SMP/E) installation steps and some of the post-SMP/E installation steps.
�server process: A process that provides services to client processes. See also client process.
�server program: A program that automates an administration task, such as compacting all databases on a server. Administrators can schedule server programs to run at a particular time or can run them as the need arises.
�server project: A project that contains information about test and deployment servers and their configurations.
�Server-Requester Programming Interface: An IBM application programming interface (API) used by requester and server programs to communicate with the personal computer or host routers.
�server-side: Pertaining to an application or component of an application that runs on a server rather than on the client. JSP and servlets are two examples of technologies that enable server-side programming.
�server-side include (SSI): A facility for including dynamic information in documents sent to clients, such as current date, the last modification date of a file, and the size or last modification of other files.
�server task: A program provided with the Domino server that runs only when specifically loaded. Server tasks serve various purposes; the Administration Process, HTTP Server, and Reporter are just a few examples of server tasks.
�server template: See computer template.
�server type definition: The list of characteristics, as identified by the administrator, required to uniquely identify a custom server of a certain type to Information Integrator for Content.
�service: (1) A TCP/IP port number.; (2) In the Kerberos protocol, a software server that has been assigned a principal name and is registered with the key distribution center (KDC).; (3) In network architecture, a capability of a given layer and the layers below it that is provided to the layer above. The service of a given layer is provided at the boundary between this layer and the next higher layer. (T); (4) Work performed by a server. A service can be a simple request for data to be sent or stored (as with file servers, HTTP servers, or e-mail servers), or it can be more complex work (as with print servers or process servers).; (5) A component that accepts as input a message, and processes the message; for example, translates its payload into a different format, or routes it to one of several output queues. In WebSphere BI for FN, most services are implemented as WebSphere MQ Integrator message flows or primitives.; (6) An abstract representation of a business function, hiding the specifics of the function interfaces.; (7) A program that performs a primary function within a server or related software.; (8) In service-oriented architecture, a unit of work accomplished by an interaction between computing devices.; (9) A component type in the Tivoli Data Warehouse that is created by the IBM Tivoli Business Systems Manager product, displayed in the Executive Console, and provides independent status for associated SLAs based on violation and trend events.
�serviceable software asset: A logical unit of software packaging and sharing that has a managed development and maintenance life cycle. Common components, assemblies and offerings are all serviceable assets. See also common component, assembly, offering.
�service access point (SAP): (1) A logical address that allows a system to route data between a remote device and the appropriate communications support.; (2) In Open Systems Interconnection (OSI) architecture, the point at which the services of a layer are provided by an entity of that layer to an entity of the next higher layer.; (3) The protocol and credentials associated with a data center device for authentication of remote operations. A data center device can have more than one service access point.
�service action log: A utility that displays entries requiring action by a service representative.
�Service Advertising Protocol (SAP): A protocol that allows service providing nodes, such as file server and print server, to advertise their services so that clients can access the services. SAP also provides for responding to a user for a given type of service. This information is delivered through the use of the Internetwork Packet Exchange (IPX) protocol. A SAP packet contains sets of service entry information.
�service agreement: An agreement between a provider and supplier, or a host and recipient, to define store setup and business relationship terms and conditions.
�service alert: A serviceability feature that automatically notifies the IBM Support Center about a problem that occurred.
�service alias: A named set of protocol, source ports, and destination ports that is used to help define filters in Internet Protocol (IP) packet security.
�service application: An application used to deploy mediation modules.
�service authority: A special authority that allows the user to perform the alter function in the service functions.
�service boundary: A category that identifies a group of components that are unavailable for use when one of the components of the group is being serviced. For example, service boundaries are provided on the ESS in each host bay and in each cluster.
�service bundle: A set of services that logically belong together, for example, because they share resources such as a status table or error processing queue. A service bundle contains the definition files for all resources required to provide the services, for example definition files for message flows, queues, and database tables. A service bundle has a unique name in the scope of an instance. A service bundle must be assigned to an organizational unit and loaded into a server before it is operational.
�service call failure: A response from the connector to indicate that processing of the service call request failed.
�service call request: A request to a connector from a service call.
�service call response: A successful response from the connector to a service call request.
�service catalog: A list of available provisioning services.
�service class: (1) An eight-character identifier that is used by the z/OS Workload Manager to associate customer performance goals with a particular DDF thread or procedure. A service class is also used to classify work on parallelism assistants.; (2) A group of work that has the same service goals or performance objectives, resource requirements, or availability requirements. For workload management, a service goal and, optionally, a resource group is assigned to a service class.; (3) An entity that acts as a point of resource control and monitoring for a set of database connections and activities within a DB2 database. There are two levels of service classes: service superclass and service subclass. See also service subclass, service superclass, workload definition.
�service client: A requester that invokes functions in a service provider.
�service code: A field in a S.W.I.F.T. message used to identify a closed user group, used by MERVA Liquidity Manager to identify a clearing channel.
�service component: A collection of processes that represents a business service that publishes or operates on business data.
�Service Component Architecture (SCA): An architecture in which all elements of a business transaction, such as access to Web services, Enterprise Information System (EIS) service assets, business rules, workflows, databases and so on, are represented in a service-oriented way.
�service context: Part of a General InterORB Protocol (GIOP) message that is identified with an ID and contains data used in specific interactions, such as security actions, character codeset conversion, and Object Request Broker (ORB) version information.
�service control point (SCP): A component of the intelligent network that provides transactional services, such as translation of toll-free numbers to subscriber numbers.
�Service Data Objects (SDO): An open standard for enabling applications to handle data from heterogeneous data sources in a uniform way, based on the concept of a disconnected data graph. See also business object.
�service data unit (SDU): In OSI, a unit of data transferred between a layer and the next higher layer.
�service definition: (1) In a federated database system, a description of a data source.; (2) One or more WSDL files that describe a service. Service definitions are produced by the Definition, Deployment, Adaptor, Skeleton, and Proxy wizards.; (3) An explicit definition of all the workloads and processing capacity in a sysplex. A service definition includes service policies, workloads, service classes, resource groups, and classification rules.
�service description: The description of a Web service, which can be defined in any format such as WSDL, UDDI, or HTML.
�service desk: A front line support group who add value by performing a high proportion of first time remote fixes.
�service destination: A specialization of a service integration bus destination. Each service destination can directly represent the Web service implementation or can indirectly represent the service through a Web Services Definition Language (WSDL) document.
�service document: A document that describes a Web service, for example a Web Services Description Language (WSDL) document.
�service element: (1) In OSI, a unit of standardization specifying a complete group of functions.; (2) One of the discrete hardware and software products that provide a terminal user with processing ability.
�service endpoint: The physical address of a service which implements one or more interfaces.
�Service Focal Point: An application on the Hardware Management Console (HMC) that collects problems from the system and from logical partitions. It is used to view problems and to take action on problems.
�service functions: Specific capabilities within service tools that are typically used for problem determination and problem solving, often with the assistance of IBM support. Examples of service functions include Licensed Internal Code trace, Licensed Internal Code log, and the display, alter, dump function.
�service group (SG): In an RSR environment, a collection of all IMSs that access RSR-covered databases at an active or at a remote site, including the RECON data set. A service group usually includes one or more IMSs at a single site, with the databases and RECON data set shared between the IMSs.
�service information message (SIM): A message, generated by a storage subsystem, that is the result of error event location and analysis. A SIM indicates that some service action is required.
�service information octet (SIO): A field within an MTP message signal unit that identifies a higher layer user of MTP, and whether the message relates to a national or international network.
�service input queue: The queue from which a service retrieves the messages it is to process. In WebSphere BI for FN, this queue is implemented as a WebSphere MQ local queue.
�service integration bus: A managed communication mechanism that supports service integration through synchronous and asynchronous messaging. A bus consists of interconnecting messaging engines that manage bus resources.
�service integration bus link: A link between messaging engines on different service integration buses. This enables requests and messages to pass between the buses.
�service integration bus Web services enablement: A software component that enables Web services to use IBM service integration technologies. This capability provides a quality of service choice and message distribution options for Web services, with mediations that support message rerouting or modification.
�service integration logic: Integration logic on an enterprise service bus to mediate between requesters and providers. The logic performs a number of functions such as to transform and augment requests, convert transport protocols, and route requests and replies automatically
�service integration technology: Techonology that provides a highly-flexible messaging system for a service-oriented architecture (SOA). This supports a wide spectrum of quality of service options, protocols, and messaging patterns. The technology supports both message-oriented and service-oriented applications.
�service interface queue: The queue into which applications place messages that are to be processed by a service. In WebSphere BI for FN, each OU that uses a particular service has its own service interface queue, and this queue is implemented as a WebSphere MQ alias queue.
�service interval: A time interval, against which the elapsed time between a put or a get and a subsequent get is compared by the queue manager in deciding whether the conditions for a service interval event have been met. The service interval for a queue is specified by a queue attribute.
�service interval event: An event related to the service interval.
�service level: (1) One of the four levels of service (fast, status, data high, or data low) that determines if a distribution is put on the normal or priority distribution queue.; (2) A set of logical characteristics of storage required by a data set managed by a storage management subsystem (SMS). Examples of these logical characteristics are performance, security, and availability.; (3) A class of service that can be used in business policies to aggregate a set of desired and implied service qualities.
�service level agreement (SLA): A contract between a customer and a service provider that specifies the expectations for the level of service with respect to availability, performance, and other measurable objectives. See also service level objective.
�service level classification: A rule that is used by a monitor to evaluate how well a monitored service is performing. The results form the basis for service level agreements (SLAs).
�service level management (SLM): The disciplined, proactive methodology used to ensure that adequate levels of service are delivered to all IT users in accordance with business priorities and at acceptable cost. IT organizations must thoroughly understand the priority and relative importance of each service it provides. Service level management is the continuous process of measuring, reporting, and improving the quality of service provided by the IT organization to the business.
�service level objective (SLO): A specification of a metric property that is associated with both threshold values for peak and off-peak hours in a schedule and a guaranteed level of service that is defined in a service level agreement (SLA). See also service level agreement, metric, breach value.
�service level specification: A set of parameters and their values that defines the service offered to a traffic stream by a differentiated services domain.
�service library: The system library provided in the system that is used temporarily for loading IBM-supplied programming changes and creating APARs. Named QSRV.
�Service Location Protocol (SLP): An Internet protocol that identifies and uses network hosts without having to designate a specific network host name.
�service machine: In z/VM, a guest virtual machine that provides a system service such as accounting, error recording, or monitoring. A system service can be part of z/VM or a licensed program.
�service message: See control message.
�service message object (SMO): A service data object that can exist only in a mediation flow component. The service message object is composed of a body and headers. The body contains the parameters of the invoked interface operation, and the headers may contain information such as service invocation, transport protocol, mediation exception, JMS properties, or correlation information.
�service name: A name that provides a symbolic method of specifying the port number to be used at a remote node. To identify an application, the TCP/IP connection requires the address of the remote node and the port number to be used on the remote node.
�service network: The Ethernet network that connects the management server, the Hardware Management Console (HMC), the POWER5 Service Processors, and Bulk Power Assemblies (BPA).
�service node: (1) An element of an Intelligent Network that contains the service logic that controls an intelligent network application and resources.; (2) A Blue Gene system which is responsible for management and control of a Blue Gene solution.
�service-oriented architecture (SOA): A conceptual description of the structure of a software system in terms of its components and the services they provide, without regard for the underlying implementation of these components, services and connections between components.
�service-oriented integration (SOI): The integration of services across multiple applications inside and outside the enterprise for a business objective. SOI is a phase of service-oriented architecture.
�service pack: A collection of code fixes for an IBM licensed program that contains PC code. The fixes are contained in a single, orderable program temporary fix (PTF).
�service personnel: A generalization referring to individuals or companies authorized to service IBM products. The terms service provider, service representative, and service support representative (SSR) refer to types of service personnel. See also service support representative.
�service policy: (1) A set of performance goals for all MVS images using MVS workload management in a sysplex. There can be only one active service policy for a sysplex, and all subsystems in goal mode within that sysplex process towards that policy. However, you can create several service policies, and switch between them to cater for the different needs of different processing periods.; (2) A performance goal that is assigned to a specific application URI to help designate the business importance of different request types.
�service portfolio: The collection of business services that a subscriber is entitled to use.
�service primitive: In the OSI reference model, the smallest defined interaction between service users and service providers in adjacent layers. This interaction is a service provided by the lower layer to the higher layer.(I)
�service processor: (1) The logic that contains the processor function to start the system processor and handle error conditions.; (2) A generic term for Remote Supervisor Adapters, Advanced System Management processors, Advanced System Management PCI adapters, and integrated system management processors (ISMPs). These hardware-based management processors used in IBM Netfinity and xSeries servers work with IBM Director to provide hardware status and alert notification.; (3) The interface to the Hardware Management Console (HMC) that provides hardware control and logical partition (LPAR) support for System p5 servers.
�service program: (1) A bound program that performs utility functions that can be called by other bound programs.; (2) See utility program.
�service project: A collection of related items used to build a service.
�service provider: (1) In the OSI reference model, a layer that provides services to the next higher layer.; (2) In System Manager, the system used to provide problem-handling support to another system or systems connected to it by communications lines. The service provider can also be the alert focal point in a network. See also service requester.; (3) Any company that provides services for a fee to its customers, such as telecommunication companies, application service providers, enterprise IT, and Internet service providers.; (4) A company or program that provides a business function as a service. The service provider receives messages from a service requester and runs the requested service. The service provider might also send messages in reply to the request.
�service provider equipment (SPE): The switching equipment owned by a telephone company.
�service rate: The rate at which an entity can service requests. See also request rate.
�service representative basic user profile: A system-supplied user profile, named QSRVBAS, that provides limited authority for a service representative to use dedicated service tools (DST) and system service tools (SST). See also service representative user profile.
�service representative user profile: A system-supplied user profile, named QSRV, that provides all the authority required by a service representative to use the dedicated service tools (DST) and system service tools (SST). See also service representative basic user profile.
�service request: (1) A type of request that is created and passed to the request queue handler whenever a nucleus server requires a service that is not currently available.; (2) An element that is used to manage and track work requests.
�service request block (SRB): A control block that represents a routine that performs a particular function or service in a specified address space. See also dispatch.
�service requester: (1) In System Manager, the system with a program or equipment problem that requires and asks for problem-handling support from another system in a network. See also service provider.; (2) The application that initiates an interaction with a Web service. The service requestor binds to the service using the published information and calls the service.
�services: Collections of network endpoints or ports that are used to aggregate a set of related ports.
�service segment: The EDI segment used when an EDI document is enveloped (such as ISA, GS, ST, UNB, UNH, UNT, and so on).
�service selection policy: A policy that determines which service to use in a provisioning policy.
�service stack: The TCP/IP modules involved in service and support of the System i platform.
�service subclass: A grouping mechanism for database activities within a service superclass. Resources of a service superclass are shared by all related service subclasses. See also service class, service superclass.
�service subscriber: A user who has rights only to subscribe or cancel provisioning services.
�service superclass: A grouping mechanism for connections within a database. See also service class, service subclass.
�service support representative (SSR): An individual or a company authorized to service IBM products. See also service personnel.
�service ticket: In the Kerberos protocol, a ticket that grants access to a particular resource, or service. A ticket from a Kerberos authentication server must be presented in order to obtain a service ticket.
�service tools: Functions that are used to configure, manage, and service important operational aspects of the system, such as to configure logical partitions, manage disk units, and troubleshoot problems. Service tools are accessed through dedicated service tools (DST), system service tools (SST), and other service-related CL commands.
�service tools device ID: A programming object used by both the PC and the IBM System i5 model as a means to authenticate the network connection between the two. A service tools device ID is unique to that PC and server connection. The service tools device ID can be managed by authorized users in dedicated service tools (DST) or system service tools (SST). The default service tools device ID is QCONSOLE.
�service tools server: A server that allows the use of a PC to perform service tools functions through TCP/IP.
�service tools user ID: A user ID that is required to access DST, SST, System i Navigator (for logical partitions and disk unit management), and Operations Console. Service tools user IDs are created through DST or SST and are separate from i5/OS user profiles.
�service type definition: In Universal Discovery Description and Integration (UDDI), a description of specifications for services or taxonomies.
�service user: In the OSI reference model, a layer that uses the services of the next lower layer.(I)
�service virtualization: A virtualization that compensates for the differences in the syntactic details of the service interactions so that the service requestor and provider do not have to use the same interaction protocol and pattern or the same interface, nor do they have to know the identities of the other participants.
�service VLAN: See service network.
�servlet: A Java program that runs on a Web server and extends the server's functionality by generating dynamic content in response to Web client requests. Servlets are commonly used to connect databases to the Web.
�servlet container: A Web application server component that invokes the action servlet and that interacts with the action servlet to process requests.
�servlet filtering: The process of transforming a request or modifying a response without exposing the resource used by the servlet engine. See also filter.
�servlet mapping: A correspondence between a client request and a servlet that defines their association.
�servo: See servomechanism.
�servomechanism (servo): (1) An automatic device that uses feedback to govern the physical position of a part.; (2) A feedback control system in which at least one of the signals represents mechanical motion.
�SES: See SCSI Enclosure Services.
�session: (1) A logical or virtual connection between two stations, software programs, or devices on a network that allows the two elements to communicate and exchange data. See also SQL connection, transaction.; (2) A type of resource that controls local logical units (LUs), remote LUs, modes, and attachments.; (3) In Java EE, an object used by a servlet to track a user's interaction with a Web application across multiple HTTP requests.; (4) In a distributed application, a single conversation between a communicating pair of transactions. See also conversation.; (5) A series of requests to a servlet originating from the same user at the same browser.; (6) A collection of process groups established for job control purposes.
�session affinity: A method of configuring applications in which a client is always connected to the same server. These configurations disable workload management after an initial connection by forcing a client request to always go to the same server.
�session bean: An enterprise bean that is created by a client and that usually exists only for the duration of a single client/server session. (Sun) See also stateless session bean, entity bean, stateful session bean.
�session connection: In OSI, a connection between two nodes that enables them to communicate at the session layer.
�session connector: A session-layer component in an APPN network node or in a subarea node boundary or gateway function that connects two stages of a session. Session connectors swap addresses from one address space to another for session-level intermediate routing, segment session message units as needed, and (except for gateway function session connectors) adaptively pace the session traffic in each direction.
�session control (SC): In SNA, one of the components of transmission control. Session control is used to purge data flowing in a session after an unrecoverable error occurs, to resynchronize the data flow after such an error, and to perform cryptographic verification.
�session default: A session assumed by the system for temporary use.
�session description: An object that contains a description of the operating characteristics of an RJE session. The system-recognized identifier for the object type is *SSND.
�session facade: A mechanism for separating the business and client tiers of an enterprise application by abstracting the data and business methods so that clients are not tightly coupled with the business logic and not responsible for data integrity. Implemented as session enterprise beans, session facades also decouple lower-level business components from one another.
�session failure: The loss of all resources of a data management session due to the failure of the daemon on the session node.
�session files library: The files library that will be in use when the current System/36 environment job ends.
�session functional unit: In OSI, logical groupings of related services provided by the Session Layer, such as activity management, capability data exchange, and negotiated release. Most session functional units are optional. The peer application entities negotiate whether or not the optional functions will be used when the session connection is established.
�session global variable: A global variable whose value is shared only within the session where it exists. See also global variable.
�session ID: (1) A unique identifier that is assigned when a customer accesses WebSphere Commerce.; (2) In WebSphere MQ for z/OS, the CICS-unique identifier that defines the communication link to be used by a message channel agent when moving messages from a transmission queue to a link.
�Session Initiation Protocol (SIP): A protocol for initiating interactive multi-media sessions.
�session key: (1) In Cryptographic Support, a data-encrypting key used to encrypt data before it is sent to another location.; (2) In computer security, a temporary key that grants access to a particular resource or session. A session key is similar to a service ticket in the Kerberos protocol.; (3) A key that uniquely identifies each CICS-IMS session. The session key is formed from the CICS name for the session and the IMS subpool name.
�session layer: In OSI, the layer that provides the services that organize and synchronize communications between functional units in different open systems located in the presentation layer.
�session-layer protocol data unit (SPDU): In OSI, a protocol data unit in the session layer.(I)
�session-layer service access point (SSAP): In OSI, a service access point in the session layer.
�session-layer service data unit (SSDU): In OSI, a unit of data transferred between the presentation layer and the session layer.
�session leader: A process that has created a session.
�session-level authentication: In Systems Network Architecture (SNA), a session level security protocol that enables two logical units (LUs) to authenticate each other while they are activating a session. Session level authentication is also known as LU-LU verification.
�session-level cryptography: In Systems Network Architecture (SNA), a method of encrypting and decrypting data that flows on a session between two logical units (LUs).
�session-level security: See end-user verification.
�session limit: In SNA, the maximum number of concurrently active logical unit to logical unit (LU-to-LU) sessions that a particular logical unit (LU) can support.
�session monitor: A monitor that provides information about SNA sessions, including session partner identification, session status, connectivity of active sessions, and response time data. For problem determination, it also provides session trace data, route data, and VTAM sense code information. See also hardware monitor.
�session node: The node on which a data management session was created.
�session object: An instance of a session data class used to persist Web client state between server requests.
�session parameter: In SNA, a parameter that specifies or constrains the protocols (such as bracket protocol and pacing) for a session between two network accessible units (NAUs).
�session profile: In System i Access, a file that describes the characteristics of a PC5250 session.
�session protocol: The available set of SNA communication requests and responses.
�session qualifier pair: See session key.
�session recovery: The XRF process that switches primary sessions on class 1 terminals to backup sessions or reestablishes service on class 2 terminals during takeover.
�session security: In LU6.2 and MRO, the level of security applied when a request to establish a session is received from, or sent to, a remote system. Used to verify that the remote system is really the system it claims to be. See also link security, user security.
�session setup failure notification (SSFN): Session awareness data that is provided when there is a failure. It identifies the system services control point that detects the error, the SSCPs that are involved, and the names of the session partners affected.
�session statistics file: An online VSAM key-sequenced data set used for storing session data.
�session version: In OSI, pertaining to the two versions of the session-layer services and protocols standard. Session version 2 can handle the transmission of larger units of data than session version 1.
�SET: See Secure Electronic Transaction.
�set and test sequence number (STSN): In SNA, a communication protocol whereby transmissions can be checked.
�set asynchronous balanced mode (SABM): In communications, a data link control command used to establish a data link connection with the destination in asynchronous balanced mode.
�set asynchronous balanced mode extended (SABME): In communications, pertaining to a control command used to initiate data transfer in the extended asynchronous balanced mode of operation with a remote link station. The SABME command uses modulus 128 sequence numbers.
�set buffer address (SBA): An order used to position data in the buffer of a 3270 terminal, thereby controlling the position of data on the screen. The SBA order is followed by a 2-byte buffer address.
�set integrity pending: A state indicating that integrity processing is required on a table. To remove this state, a SET INTEGRITY statement must be processed for the table. See also check pending, integrity processing.
�set integrity pending no access state: A state indicating that integrity processing is required for a table and that no access to that table is allowed until integrity processing is complete.
�set integrity pending read access state: A state indicating that integrity processing is required for a table and that only read access to that table is allowed until integrity processing is complete.
�set normal response mode (SNRM): A data link control command that puts the link connection in normal response mode (NRM).
�set operator: The SQL operators UNION, EXCEPT, and INTERSECT, which correspond to the relational operators union, difference, and intersection. A set operator derives a result table by combining two other result tables.
�set services: In OSI, callable services that supply optional information to the subsystem. See also action service, extract service.
�setter method: A method whose purpose is to set the value of an instance or class variable. This capability allows another object to set the value of one of its variables. See also getter method, accessor method, mutator method.
�setting: A value of an attribute that determines how an object looks and functions.
�settings view: A view of an object that provides a way to display the attributes associated with the object. For example, using the settings view, the user can change the areas that display in a window, such as the title or columns.
�settle: In WebSphere Commerce Payments, to close a batch object and transfer funds.
�set-top box: A single or multiple tuner device that enables the display of cable or satellite signals on a television.
�setup: The preparation of a computing system to perform a job or job step. Setup is usually performed by an operator and often involves the performance of routine functions.
�setup program: A user-provided program that defines and inquires about FEPI resources, and performs housekeeping for the sessions.
�severity code: A number that indicates the seriousness of an error condition.
�severity level: A classification for an event that indicates its degree of severity. The predefined severity levels, in order of descending severity, are: fatal, critical, warning, minor, harmless, and unknown.
�SFM: See sysplex failure management.
�SFP transceiver: See small form-factor pluggable transceiver.
�SF record: See subfield record.
�SG: See service group.
�SGML: See Standard Generalized Markup Language.
�SH: See application shell.
�SHA: See Secure Hash Algorithm.
�SHA digest: See Secure Hash Algorithm digest.
�shadow: (1) A duplication of the Enterprise Address Book (EAB) data on another system.; (2) To duplicate Enterprise Address Book (EAB) data from one system to another and to send EAB changes, additions, and deletions to other systems.
�shadow database: In an RSR environment, a database maintained at the tracking site as a remote copy of a database at the active site. If a remote takeover occurs, the shadow database becomes the master database.
�shadow index: In index reorganization, an internal structure that is built and then used for index access after the index reorganization is complete.
�shadowing: (1) A recovery technique in which current page contents are never overwritten. Instead, new pages are allocated and written while the pages whose values are being replaced are retained as shadow copies to support system restoration. The shadow copies are deleted when they are no longer needed.; (2) The capability of a system to copy data from one system to another system and keep it up to date whenever it is changed on any system that shadows the information in the network.
�shadow log: A log of errors that occur from the time that an initial program load starts to the time storage management recovery ends. The log contains the latest occurring errors, and may contain errors not found in the error log.
�shaping: In QoS, the process of delaying packets within a traffic stream so that the traffic conforms to a user-defined profile.
�Sharable Content Object Reference Model (SCORM): A set of standards that, when applied to course content, produces small, reusable learning objects. A result of the Department of Defense's Advance Distributed Learning (ADL) initiative, SCORM-compliant courseware elements can be easily merged with other compliant elements to produce a highly modular repository of training materials.
�shared access path: An access path used by more than one file member to get data common to both members.
�shared address space: A type of address space shared by multiple UNIX System Services (z/OS UNIX) processors.
�shared area: In CICS/VSE, an area of storage that is common to all address spaces in the system. VSE/ESA has two shared areas. The first shared area (24 bit) is allocated at the start of the address space and contains the supervisor, the SVA (for system programs and the system GETVIS area), and the shared partitions.The second shared area (31 bit) is allocated at the end of the address space and contains the SVA (31 bit) for system programs and the system GETVIS area. See also private area.
�shared broadcasting: A condition in which the TSO data sets SYS1.UADS (TSO user definition) and SYS1.BRODCAST (TSO message transmission definition) are shared by all systems in the multi-access spool (MAS) complex.
�shared communications area (SCA): A coupling facility list structure that a DB2 for z/OS data sharing group uses for inter-DB2 communication.
�shared container: A reusable job element that contains stages and link and can be used by any server job in the project.
�shared database: A CICS facility that allows a DL/I batch region under a CICS controller to access a database owned by a CICS online system.
�shared dynamic storage area (SDSA): The user-key storage area for any non-reentrant user-key RMODE(24) programs, and also for any storage obtained by programs issuing EXEC CICS GETMAIN commands for storage below the 16MB boundary with the SHARED option.
�shared field: In Notes, a field that is used in more than one form. For example, many forms have a creation date field, so designers can define the field once and reuse it.
�shared file: A file whose open data path can be shared between two or more programs processing in the same job. See also open data path.
�shared file system: A type of file system in which all file systems in a sysplex share data with each other.
�shared-for-read lock state: The lock state for a file in which the file can be shared with another program if the program does not request exclusive use of the file. The predefined value for this lock state is *SHRRD.
�shared-for-update lock state: The lock state for a file in which the file can be shared either for update or for read operations with another program. The predefined value for this lock state is *SHRUPD.
�shared frame: A transparent window that is used in a screen-sharing meeting. The person sharing the screen can resize or move the shared frame around the desktop. Whatever appears in the shared frame is displayed to the meeting participants. Do not confuse a shared frame with a frame in a Web browser.
�shared inbound channel: In WebSphere MQ for z/OS, a channel that was started by a listener using the group port. The channel definition of a shared channel can be stored either on page set zero (private) or in the shared repository (global).
�shared index database: A secondary index database containing more than one secondary index in the same physical operating system data set.
�shared library: On Linux and UNIX operating systems, a library that contains at least one subroutine that can be used by multiple processes.
�shared library file: A file that consists of a symbolic name, a Java class path and a native path for loading Java Native Interface (JNI) libraries. Applications that are deployed on the same node as this file can access this information.
�shared library program: A program that, when loaded, is put in the shared library region for system-wide sharing.
�shared library region: The area of storage in the system in which shared library objects are loaded.
�shared lock: (1) A lock that limits concurrently running application processes to read-only operations on database data. See also exclusive lock, gross lock.; (2) A lock that several tasks can hold.
�shared mail: In Domino, a feature that stores messages addressed to more than one user on a mail server in a central database, called the shared mail database.
�shared memory: An interprocess communications service that provides shared memory segments.
�shared memory segment: An interprocess communications mechanism that allows a process to directly read data from, write data to, and share data with other processes without having the data manipulated by the operating system.
�shared-nothing environment: A distributed database architecture in which each database partition server has its own processor, memory, and disks.
�shared-no-update lock state: The lock state for a file in which the file can be shared with another program if the program requests either a shared-no-update lock state or a shared-for-read lock state. The predefined value for this lock state is *SHRNUP.
�shared object library: A collection of subroutines that can be shared by multiple processes.
�shared outbound channel: In WebSphere MQ for z/OS, a channel that moves messages from a shared transmission queue. The channel definition of a shared channel can be stored either on page set zero (private) or in the shared repository (global).
�shared partition: In CICS/VSE, a partition allocated for a program such as VSE/POWER that provides services for and communicates with programs in other partitions of the system's virtual address spaces. See also private partition.
�shared place: A place created for a community of people with a common purpose. Shared places can be public or restricted. The place creator (who automatically becomes the place manager) specifies whether a place is public or restricted during place creation.
�shared port: A communication port on a single input/output processor using short-hold mode on a single SDLC line description.
�shared procedure: A routine that is defined and called, using SQL, to perform operations that can include both host language statements and SQL statements.
�shared processing pool: See shared processor pool.
�shared processor pool: A group of physical processors that provide processing capacity that can be shared among multiple logical partitions. Processing capacity from the shared processor pool can be assigned to each of the logical partitions in partial processor increments. The sum of the assigned processing capacity across all logical partitions in the shared processor pool cannot exceed the total processing capacity of the shared processor pool.
�shared queue: (1) A collection of data objects with the same name that reside on a coupling facility queue structure. Data objects on a shared queue are available to all CQS clients that have access to the structure.; (2) In WebSphere MQ for z/OS, a type of local queue. The messages on the queue are stored in the coupling facility and can be accessed by one or more queue managers in a queue-sharing group. The definition of the queue is stored in the shared repository. See also queue-sharing group.
�shared record format: A record format that is used in more than one externally described file.
�shared repository: (1) In WebSphere MQ for z/OS, a shared DB2 database that is used to hold object definitions that have been defined globally.; (2) A storage location of server objects where each file is stored only once even if it belongs to several objects.
�shared resource: (1) A function that permits the sharing of a pool of I/O-related control blocks, channel programs, and buffers among several Virtual Storage Access Method (VSAM) data sets that are open at the same time. See also global shared resource, local shared resource.; (2) A software file or plug-in that is stored in a directory and can be shared by packages. See also installation directory.
�shared secret: An encrypted value that is used to retrieve the initial password of a user. This value is defined when the personal information for the user is initially loaded into the system.
�shared-secret key cryptography: A method of cryptography where the same key is used by two communicating parties, that is, for both encryption and decryption.
�shared segment: In VM, a feature of a saved system that allows one or more segments of reentrant code in real storage to be shared among many virtual machines.
�shared storage: (1) Storage within a storage facility that is configured such that multiple homogenous or divergent hosts can access the storage concurrently. The storage has a uniform appearance to all hosts; the host programs that access the storage must have a common model for the information on a storage device.; (2) An area of storage that is the same for each virtual address space. Because it is the same space for all users, information stored there can be shared and does not have to be loaded in the user region.
�shared storage pool: A storage pool that can be shared by more than one subsystem. See also private storage pool.
�shared submap: In Tivoli NetView, a submap on which multiple application programs manage objects on the application plane. Shared submaps allow application programs to cooperatively contribute information to the same submap. See also exclusive submap.
�shared view: A view that is public to more than one Notes user.
�shared virtual area (SVA): In VSE, a high address area of virtual storage that contains a system directory list (SDL) of frequently used phases, resident programs that can be shared between partitions, and an area for system support.
�shared-weight sort sequence: A sort sequence in which some graphic characters in the sequence may have the same weight as some other characters in the sequence. Those with the same weight will sort together as if they were the same character.
�shared window: The program window that is shared during a Sametime screen-sharing meeting.
�share limit: In SNA, the maximum number of control points that can control a network resource concurrently.
�share lock: (1) See shared lock.; (2) A lock that prevents concurrently executing application processes from changing data, but not from reading data. See also exclusive lock.
�shareport group: The set of server instances sharing the same TCP port on the same TCP/IP stack.
�sharing: Using a file on a remote system. Sharing is performed by mounting the remote file system and then reading or writing files in that remote system.
�sharing complex: A group of subsystems using IMS and DBRC that share the same RECON data sets.
�sharing control data set: A linear data set (LDS) that contains information DFSMSdfp requires to ensure the integrity of the data-sharing environment for record-level sharing (RLS).
�shear: The angle of slant of a character cell that is not perpendicular to a baseline.
�shelf location: A single space on a shelf for storage of removable media. In DFSMSrmm, a shelf location is defined in the removable media library by a rack number; in a storage location, it is defined by a bin number. See also bin number, rack number.
�shelf management: A function that manages the placement of volumes in individual slots in a location. In DFSMSrmm, shelf management is provided for the removable media library using rack numbers. For storage locations, shelf management is optional and uses bin numbers.
�shelf-resident optical volume: An optical volume that resides outside of an optical library. See also optical volume.
�shelf-resident tape volume: A tape volume that resides outside of a tape library. See also tape volume.
�shell: (1) The CICS facility that provides an isolated area for running CICS programs without adversely affecting other users.; (2) A software interface between users and an operating system. Shells generally fall into one of two categories: a command line shell, which provides a command line interface to the operating system; and a graphical shell, which provides a graphical user interface (GUI).
�shell program: See shell.
�shell prompt: On operating systems such as AIX or UNIX, the character string indicating that the system can accept a command. The shell prompt is typically the dollar sign ($).
�shell script: A program, or script, that is interpreted by the shell of an operating system.
�shielded twisted pair: A cable medium consisting of a telephone wire wrapped in a metal sheath to eliminate external interference.
�shift: A keyboard action to allow uppercase or other characters to be entered. See also level.
�shift control character: A shift-in character or a shift-out character.
�shift-in character: A control character (X'0F') that is used in EBCDIC systems to denote that the subsequent bytes represent SBCS characters. See also shift-out character.
�shift-out character: A control character (X'0E') that is used in EBCDIC systems to denote that the subsequent bytes, up to the next shift-in control character, represent DBCS characters. See also shift-in character.
�shim: (1) A thin, often tapered, piece of material, such as metal, used to fill in space between things for support, adjustment, or leveling.; (2) A part for adjusting gaps, play, or position in a mechanism.
�shingle: A string of consecutive tokens (words) that are taken from a sentence. For example, from "This is a very short sentence.", the 3-word shingles (or trigrams) are: This is a/ is a very/ a very short/ very short sentence/. Shingles can be used in statistical linguistics. For example, if two different texts have a lot of common shingles, the texts are probably related somehow.
�ship as complete: A shipping option that requires all items in an order to be shipped together.
�shippable terminal: In transaction routing, a terminal whose definition can be shipped to another CICS system when the other system requires a remote definition of that terminal.
�shipping carrier: A company that provides shipping services from a fulfillment center to a customer. See also fulfillment center.
�ship together: An advanced order shipping option that allows items in an order to be marked for multiple group shipping instructions in the order item list.
�SHISAM: See simple HISAM.
�SHM: See short-hold mode.
�shopper: See customer.
�shopping cart: A pending order. See also interest item, order.
�shopping currency: The currency that is used by a store in its transactions with a particular customer. See also preferred currency, supported currency.
�shopping flow URL: A controller command that has a URL interface and is run from a store interface. See also redirection URL.
�shopping language: The language that is used when displaying pages to a particular customer. See also preferred language.
�shortcut bar: In Eclipse, the vertical toolbar at the left side of the workbench window that contains buttons for open perspectives and for fast views.
�shortcut key: See keyboard shortcut.
�shortest path: The processing path that takes the shortest time to complete of all parallel paths in a process instance, where each path considered begins at a start node or an input to the process and ends at a stop node.
�Shortest Path First (SPF): A routing algorithm in which each router uses the length of the path to determine the shortest-path spanning tree. Shortest Path First is used by link-state routing protocols. See also link-state routing protocol.
�short format: In binary floating-point storage formats, the 32-bit representation of a binary floating-point number, not-a-number, or infinity.
�short-form identifier: See coded character set identifier.
�short frame: In Performance Tools, a frame that has fewer bytes between its start flag and end flag than is permitted by the data control protocol of the integrated services digital network (ISDN).
�short frame errors: In Performance Tools, the total number of short frames received by the terminal equipment (TE).
�short-hold mode (SHM): A mode specified during configuration that allows the DTE to connect or reconnect when no data is being transmitted over a circuit-switched line, while maintaining the logical connection of the sessions across the circuit.
�short host name: A host name that contains only the local identifier.
�short interface: In query management, the set of language-specific interfaces that allow commands to run that do not require access to program variables. The short interface includes the communications area, command length, and command string.
�short menu: A menu that has been shortened to display a subset of the complete set of its values. Some short menus are created automatically by the application on the basis of the functions used most frequently by the user. Others can be customized directly by the user.
�Short Message Service (SMS): A service that is used to transmit text to and from a mobile phone.
�short message service center (SMSC): A component of the mobile telephony network, specified by the GSM group of standards, that provides for exchange of alphanumeric messages of less than 160 bytes. Messages can be exchanged between different types of system such as mobile telephone, alphanumeric pager, terminal, e-mail, telex, or DTMF telephone.
�short name: In personal communications, the one-letter name (A through Z) of the presentation space or emulation session.
�short notebook: A choice that reduces the number of choices that appear in a notebook.
�short-on-storage (SOS): The condition in CICS that occurs when requests for storage from the dynamic storage areas exceed available storage. CICS cannot satisfy these requests, or can satisfy them only by using some of the storage cushion, even when all programs that are eligible for deletion, and are not in use, have been deleted. See also program compression, storage cushion.
�short-path transformer: A transformer program for function shipping over MRO links. It is designed to optimize the pathlength involved in the construction of the TIOAs send on an MRO session for function shipping.
�short string: A fixed-length string or a variable-length string whose maximum length is less than or equal to 254 bytes.
�short unit of work identifier (short UOW ID): An 8-byte value that CICS passes to resource managers, such as DB2 and VSAM, for lock management purposes.
�short UOW ID: See short unit of work identifier.
�shortwave laser adapter: A connector used between a host and the ESS to support shortwave fibre-channel communication.
�short wavelength (SWL): A type of fiber optic cabling that is based on 850-mm lasers and supports 1.0625-Gbps link speeds. SWL can also refer to the type of gigabit interface converter (GBIC) or small form-factor pluggable (SFP). See also long wavelength.
�show cause: The reason code in the record maintenance statistic that indicates to VTAM or to Tivoli NetView for z/OS the threshold that was exceeded and whether the threshold has been dynamically altered.
�shred: In XML, to map the data in an XML document to table rows and columns in a relational database.
�shredding: (1) See decomposition.; (2) The process of breaking up an XML document for storage in database tables.
�SHSAM: See simple hierarchical sequential access method.
�shunt: The status of a unit of recovery that has failed at one of the following points: while in doubt during a two-phase commit process; while attempting to commit changes to resources at the end of the unit of recovery; or while attempting to back out the unit of recovery. If a unit of recovery fails for one of these reasons, it is removed (shunted) from the primary system log to the secondary system log pending recovery from the failure.
�shunted: Pertaining to the status of a UOW that has failed at one of the following points: while in-doubt during a two-phase commit process, while attempting to commit changes to resources at the end of the UOW, while attempting to back out the UOW, or if a UOW fails for one of these reasons, it is removed (shunted) from the primary system log (DFHLOG) to the secondary system log (DFHSHUNT) pending recovery from the failure.
�SHUTC: In SNA, a command used to complete a session.
�shutdown: (1) The process of ending operation of a system or a subsystem by following a defined procedure.; (2) A status condition that describes when the cluster is shut down as intended.
�sibling document: In a Notes view or folder, a document at the same level as another document.
�sibling segments: Two or more occurrences of different sibling segment types having a common parent segment occurrence. See also twin segments.
�sibling segment types: Two or more segment types having a common parent segment type.
�SID: (1) See subject identifier.; (2) See source ID.
�side: See physical partition.
�side effect: (1) An undesirable result caused by altering the values of nonlocal variables by a procedure or function.; (2) A change in the state of the execution environment.
�sidefile: A storage area used to maintain copies of tracks within a concurrent copy domain. A concurrent copy operation maintains one sidefile in storage control cache and another in processor storage.
�side information: (1) In OSI, system-defined values that are used as the initial values of certain parameters. In OSI Communications Subsystem, side information is a combination of (a) information in the OSI Communications Subsystem information base, and (b) information provided by directory service.; (2) System-defined variables that are used for the initial values of the communications element of the SAA Common Programming Interface partner_LU_name, mode_name, and TP_name characteristics.
�SIF: See signaling information field.
�SiGe: See silicon-germanium technology.
�SIGL: A REXX special variable that contains the line number of the last instruction that caused a jump to a label.
�sign: To attach a unique electronic signature, derived from the sender's user ID, to a document or field when a document is mailed. Signing mail ensures that if an unauthorized user creates a new copy of a user's ID, the unauthorized user cannot forge signatures with it. In addition, the signature verifies that no one has tampered with the data while the message was in transit.
�signal: (1) A mechanism by which a process can be notified of, or affected by, an event occurring in the system. Examples of such events include hardware exceptions and specific actions by processes. The term signal is also used to refer to the event itself.; (2) In operating system operations, a method of inter-process communication that simulates software interrupts.; (3) In replication, an SQL statement that allows communication with the Capture program and the Q Capture program. A signal is inserted into the signal control table and received by the Capture program or the Q Capture program when the program reads the log entry for the signal insert.; (4) In UML modeling, model elements that specify one-way, asynchronous communications between active objects and that are independent of the classifiers that handle them.; (5) A condition that might or might not be reported during program execution. For example, a signal can represent erroneous arithmetic operations, such as division by zero.
�signal cable: An electrical wire or set of wires, such as twinaxial, coaxial, or twisted pair cables to attach devices to a computer.
�signal catching function: See signal handler.
�Signal Computing bus (SCbus): A time division multiplexed (TDM) hardware bus originated by Dialogic to interconnect different vendors' computer telephony adapters. Specified as part of Signal Computing System Architecture (SCSA).
�Signal Computing System Architecture (SCSA): An architecture defined by Dialogic to support interoperability of software and hardware components developed by different vendors in the computer telephony industry.
�signaled error: In OSI, an error detected but not recovered by the network layer. The error is signaled to the transport layer for action. For example, the network connection is lost and reset to a known state, possibly with loss of data, but the connection remains available for use. See also residual error.
�signal handler: A subroutine or function that is called when a signal occurs.
�signaling: (1) The exchange of control information between functional parts of the system in a telecommunications network.; (2) In WebSphere MQ for z/OS and WebSphere MQ for Windows, a feature that allows the operating system to notify a program when an expected message arrives on a queue.
�signaling connection control part (SCCP): A layer 3 protocol conforming to OSI.
�signaling information field (SIF): The user data portion of an MTP message signal unit.
�signaling link code (SLC): A code that identifies a particular signaling link connecting the destination and originating signaling points. This is used in MTP signaling network management messages to indicate the signaling link to which the message relates.
�signaling link selection (SLS): A field used to distribute MTP signal units across multiple signaling links.
�signaling mode: The type of signaling protocol, either channel-associated signaling or common-channel signaling.
�signaling NaN (sNaN): In decimal floating-point operations, a value, not interpreted as a mathematical value, that contains a mask and a sequence of floating-point digits and that causes an invalid operation condition if used in certain arithmetic operations. See also decimal floating-point number.
�signaling point: A node in a signaling network that either originates and receives signaling messages, or transfers signaling messages from one signaling link to another, or both.
�signaling process: A DirectTalk component that controls signaling for an exchange data link or common-channel signaling protocol. Some signaling processes are supplied with DirectTalk, and others can be custom-written.
�signaling protocol: A signal, such as resource reservation setup protocol (RSVP), that carries an admission control request to a network. The signal requests bandwidth resource according to an application's request. To get quality of service from a network, systems need to use signaling protocols.
�Signaling System 7 (SS7): The international high-speed signaling backbone used for the public-switched telephone network.
�signal mask: A collection of signals that are currently blocked from delivery to a process.
�signal safe: A function, macro, or operating system service that can be called from within a signal handler.
�signature: (1) A value that identifies the interfaces supported by a service program. Signatures are based on the exports and the sequence of the exports allowed from a service program.; (2) The collection of types associated with a method. The signature includes the type of the return value, if any, as well as the number, order, and type of each of the method's arguments.; (3) The set of unique information that identifies a software application, such as the name, version, and file size of an application.; (4) The name and parameters of a behavioral feature.
�signature authority: The right to approve or deny a request that is submitted to the workflow engine. A user or group of users is granted signature authority when they are designated as the participant or escalation participant in a workflow design.
�signature bank: A collection of signatures. The signature emitter gets new signatures from the signature bank.
�signature CSECT: The resident routine that indicates that the load module in which it is present contains a routine written in a particular language.
�signature file: A set of information that uniquely identifies a software application, by such information as the name, version, and file size of an application.
�signature package: A logical grouping of two or more signatures.
�sign condition: In COBOL, a condition that states that the value of a data item is less than, equal to, or greater than zero.
�signer certificate: The trusted certificate entry that is usually in a trustore file.
�significance exception: The program interruption that occurs when the resulting fraction in a floating-point addition or subtraction instruction is zero. This program interruption can be disabled through a program mask-bit setting.
�significand: (1) In binary floating-point format, the part of a number that contains the whole number and fraction.; (2) The significant digits of a floating-point number.
�significant architectural requirement (SAR): In the Reusable Asset Specification (RAS), a functional requirement, system property or constraint that influences significant architectural decisions. Not all requirements are equally important from the architectural point of view. Those requirements that impact architecture the most are grouped together into a set called SARs.
�significant data: IMS state data that keeps a resource from being deleted in RM when the resource is no longer active on any IMS. This term was introduced by ETO, when deciding whether status was significant enough to prevent the dynamic control block from being deleted when the user signed off or the node logged off. See also state data.
�significant digit: Any number of a series of numbers that follows the farthest left number, that is not a zero, and that is within the accuracy allowed.
�significant status: A resource status classified as significant. In addition to being recoverable, if the resource status is specified as significant, the resource cannot be deleted after a terminal logoff, a user signoff, or an IMS restart.
�sign-off: The act a terminal user performs in order to end an identification of a user to IMS. When the terminal is an ETO terminal, the signoff process usually disconnects the user structure from the terminal structure and deletes the user structure.
�sign-on: (1) The act a terminal user performs in order to identify a user to IMS. When the terminal is an ETO terminal, the signon process also creates a user structure and connects the user structure to the terminal structure.; (2) The procedure by which the user starts working at a workstation.; (3) A request that is made on behalf of an individual CICS or IMS application process by an attachment facility to enable DB2 for z/OS to verify that it is authorized to use DB2 resources.
�sign on: To connect to a computer system or network.
�sign-on capable terminal: A terminal that allows sign-on transactions, either CICS-supplied (CESN) or user-written, to be run.
�sign-on table (SNT): A table holding terminal operator data, including the operator name, password, and operator priority. Each entry in the table contains data used by CICS to verify an operator name and to establish a priority and operator class for transactions entered by the operator.
�sign-on table terminal entry (SNTTE): An entry created by CICS if a terminal user sign-on is valid.
�sign-on transaction program: A user-written transaction program that provides send support required by the CICS PEM server.
�sign-on verification: The verification of a user ID that takes place at sign-on. Sign-on verification is required before a user can access protected IMS resources.
�silence: A brief pause between utterances.
�silent installation: An installation that does not send messages to the console but instead stores messages and errors in log files. A silent installation can use response files for data input. See also response file.
�silent mode: A method for installing or uninstalling a product component from the command line with no GUI display. When using silent mode, you specify the data required by the installation or uninstallation program directly on the command line or in a file (called an option file or response file).
�silicon-germanium technology (SiGe): A technology that makes possible the design of complex chips that integrate the functions of a cellular telephone, an e-mailbox and an Internet browser into a hand-held information device with rapid data transfer capability.
�Silicon-On-Insulator (SOI): A microchip technology that provides faster computer chips that also require less power, a key requirement for extending the life of pervasive devices.
�SIM: (1) See subscriber identity module.; (2) See service information message.; (3) See system integration module.
�SIMD: See single-instruction, multiple-data.
�SIMM: See single inline memory module.
�Simple API for XML (SAX): An event-driven, serial-access protocol for accessing XML documents, used. A Java-only API, SAX is used by most servlets and network programs to transmit and receive XML documents.
�simple attribute: An attribute in a business object that contains only one value. Valid attribute types for simple attributes include String and Integer. See also array attribute, attribute, single-cardinality attribute.
�Simple Authentication and Security Layer (SASL): An Internet protocol that allows LDAP clients to authenticate with an LDAP server and provides security for the data transmitted with this protocol.
�simple checkpoint: The periodic recording of control information and system status on the system log at user-specified intervals.
�simple condition: In COBOL, one of the conditions chosen from the following set of conditions: relational condition, class condition, condition-name condition, switch-status condition, sign condition. See also complex condition.
�simple connection: The representation of connectivity as seen from one endpoint of a connection.
�simple element: An item in the source or target document that does not contain child items, only data. For example: EDI data elements, ROD fields, XML attributes, and XML PCData values.
�simple hierarchical sequential access method (SHSAM): A type of HSAM database that contains only root segments, which have no prefixes.
�simple HISAM (SHISAM): The support for a HISAM database that contains only one segment type.
�simple identity relationship: An identity relationship that relates two business objects through a single-attribute key. Each business object that participates in the simple identity relationship contains a key with a single unique value that identifies it.
�simple list: A list of like values; for example, a list of user names. See also mixed list.
�Simple Mail Transfer Protocol (SMTP): An Internet application protocol for transferring mail among users of the Internet.
�simple name: In the CDS Cell Directory Service (CDS), one element in a CDS full name. Simple names are separated by slashes in a full name.
�simple name server: A switch service that stores names, addresses, and attributes for up to 15 minutes, and provides them as required to other devices in the fabric. SNS is defined by Fibre Channel standards and exists at a well-known address. See also fibre channel service.

�Simple Network Management Protocol (SNMP): A set of protocols for monitoring systems and devices in complex networks. Information about managed devices is defined and stored in a Management Information Base (MIB).
�Simple Object Access Protocol: See SOAP.
�simple page set: A nonpartitioned page set. A simple page set initially consists of a single data set (page set piece). If that data set is extended to 2 gigabytes, another data set is created, and so on up to a total of 32 data sets. The data sets are considered to be a single contiguous linear address space that contains a maximum of 64 gigabytes. Data is stored in the next available location within this address space without regard to any partitioning scheme.
�simple policy group: A policy group whose policies belong to a scope and have a single common characteristic, such as an application name. See also node-attached policy group, node-level policy group.
�simple repetitive loop: In REXX, a repetitive DO loop in which the repetitive phrase is an expression that evaluates to a count of iterations.
�simple rule: A rule that pertains to only one event and contains predefined conditions and actions. See also compound rule.
�simple symbol: In REXX, a symbol that does not contain any periods and does not start with a digit (0-9).
�simple table space: A table space that is neither partitioned nor segmented.
�simple type: In the XML, a type that cannot have element content and cannot carry attributes. Elements that contain numbers (and strings, and dates, and so on) but do not contain any sub-elements are said to have simple types. See also complex type.
�simplex: (1) Pertaining to printing on only one side of the paper. See also tumble.; (2) A communication channel that carries a signal in one direction only. Radio transmission is an example of simplex communication.
�simplex state: The state of a volume that is not part of a dual-copy or a remote-copy volume pair. Ending a volume pair returns the two devices to the simplex state, in which there is no longer any capability for either automatic updates of the secondary device or for logging changes.
�simplex volume: A volume that is not part of a FlashCopy, Extended Remote Copy (XRC), or Peer-to-Peer Remote Copy (PPRC) volume pair.
�Simplified Chinese: The Chinese character set that has been simplified by reducing the number of strokes in common characters and deleting complicated variants. Simplified Chinese characters are used primarily in the People's Republic of China.
�Simplified Chinese double-byte character set: An IBM-defined double-byte character set for Simplified Chinese. It consists of Simplified Chinese non-Chinese set, primary set, secondary set, and up to 1,880 user-definable characters.
�Simplified Chinese non-Chinese character set: A subset of the Simplified Chinese DBCS, consisting of non-Chinese characters, such as Latin alphabet, Greek, Russian, Roman numeric, alphanumeric and related symbols, Katakana, Hiragana, Japanese, special symbols, and Chinese phonetic symbols. There are 712 characters in this set.
�Simplified Chinese primary character set: A subset of the Simplified Chinese DBCS, consisting of commonly used Chinese characters. There are 3,755 characters in this set.
�Simplified Chinese secondary character set: A subset of the Simplified Chinese DBCS, consisting of less commonly used Chinese characters. There are 3,008 characters in this set.
�Simplified Message Desk Interface (SMDI): A Northern Telecom service that transmits out-of-band information between DirectTalk and certain switches.
�Simplified Message Service Interface (SMSI): A Lucent Technologies service that transmits out-of-band information between DirectTalk and certain switches.
�Simplified Policy Language: A human-readable syntax for the Autonomic Computing Policy Language and policy templates. See also Autonomic Computing Policy Language.
�simulation: A faster-than-real-time performance of a process. Simulation enables organizations to observe how a process will perform in response to variations of inputs to the process, just as in a real-life work environment. Simulation also provides the ability to vary process input volume over time by adjusting resources and current allocations. Simulation output provides detailed information regarding resource utilization levels and the results of cost and cycle-time calculations.
�simulation profile: A copy of a process model and the elements on which it depends, augmented with simulation attributes, that you use to run a simulation. Each simulation profile in a snapshot is based on the process as it existed at the time that the snapshot was taken.
�simulation snapshot: A company or program that provides a business function as a service. The service provider receives messages from a service requester and runs the requested service. The service provider might also send messages back through the bus in reply to the request.
�single-area structure: In a data-sharing environment, a coupling facility structure that contains only one VSO DEDB area. See also multiple-area structure.
�single authorization: A setting allowing an action to be carried out by a single person. See also dual authorization.
�single bus connection: The connection that links a single bus to the optical link card. One connector is not used.
�single-byte character set (SBCS): A coded character set in which each character is represented by a 1-byte code. A 1-byte code point allows representation of up to 256 characters. See also double-byte character set, multibyte character set.
�single-byte coded font (single-byte font): A font in which the characters are defined by a 1-byte code point. A single-byte coded font has only one coded font section.
�Single-Byte Command Code Sets Connection (SBCON): The standard, approved by the American National Standards Institute (ANSI), for the command set used by ESCON and FICON, known as FC-SB as used over a standard fibre-channel physical interface.
�single-byte font: See single-byte coded font.
�single-cardinality attribute: An attribute that represents a single value, which may be either a simple attribute or a single child business object. When this attribute represents a child business object, its type is the same as that of the business object it represents. See also array attribute, attribute, child business object, simple attribute.
�single-choice selection field: A field that contains a fixed number of choices arranged in a list in which only one selection can be made.
�single-choice selection list: A field that contains a potentially scrollable list of choices in which only one selection can be made.
�single-cluster control data set: In DFSMShsm, a migration control data set (MCDS) or backup control data set (BCDS) that is represented by a single, Virtual Storage Access Method (VSAM), key-sequenced data set (KSDS) cluster. The cluster can be a key-range cluster or a cluster not employing a key range.
�single copy object store (SCOS): The Domino feature that allows mail addressed to multiple users to be stored in a central database, called the shared mail database.
�Single Digital Trunk Processor: The combination of a single digital signal processing card and supporting equipment that provides high-level voice compression, high voice quality, and digital telephone signaling functions (transmit and receive) using an external shielded cable to an attached IBM RS/6000 computer. The Single Digital Trunk Processor supports one T1 or E1 trunk. See also Multiple Digital Trunk Processor.
�single-entry font: Fonts with a single entry in the Map Coded Font structured field. This includes all single-byte fonts and those double-byte fonts being defined as coded fonts. See also multiple-entry font.
�single-image mode: The state of a processor complex when all of its hardware resources are in a single configuration.
�single inheritance: A semantic variation of generalization in which a type may have only one supertype. See also multiple inheritance.
�single inline memory module (SIMM): In computer hardware, a small circuit card that carries a number of surface-mounted memory chips in a space-saving configuration with the connector pins protruding in a single line from the edge of the card. Varying numbers of SIMMs can be plugged easily into slots in a memory board to expand random access memory. See also dual inline memory module.
�single-instruction, multiple-data (SIMD): A parallel programming technique where multiple processors execute the same instructions on different data at the same time.
�single-level wildcard: A wildcard that can be specified in subscriptions to match a single level in a topic.
�single lock manager: A concept where locks for database resources shared between programs or subsystems are handled by one control point. Either an IRLM or a Program Isolation locking function can be invoked for the subsystem.
�single logging: A method of recording WebSphere MQ for z/OS activity where each change is recorded on one data set only. See also dual logging.
�single-member warm start: A type of warm start in which a member that ended abnormally joins an active configuration. This member can recover only work in process when it failed or stopped.
�single message mode: A processing mode in which synchronization points occur as each message is read from the queue, as well as at application termination. See also message mode, multiple message mode.
�single-mode optical fiber: An optical fiber in which only the lowest-order bound mode (which can consist of a pair of orthogonally polarized fields) can propagate at the wavelength of interest. See also multimode optical fiber.
�single-MVS environment: An environment that supports one MVS image. See also MVS image.
�single-occurrence mapping: A form of mapping in which a specific occurrence of a repeating compound or simple element is mapped to a compound or simple element.
�single-partition database environment: A database server with all instances, databases, and logical database partitions residing on one computer.
�single-phase backout: A method in which an action in progress must not be allowed to finish, and all changes that are part of that action must be undone.
�single-phase commit: A method in which a program can commit updates to a commitment resource without coordinating those updates with updates the program has made to resources controlled by another resource manager.
�single point of control (SPOC): (1) The ability to access and manage all CICS systems and their resources in a CICSplex from a single terminal or user session.; (2) The control interface that sends commands to one or more members of an IMSplex and receives command responses.
�single point of failure: An environment in which one failure can result in simultaneous loss of both the coupling facility (CF) list structure for a log stream and the local storage-buffer copy.
�single port sharing: An arrangement for short-hold mode operation in which each port is shared by a set of DTEs, with the restriction that all reconnection calls (recalls) must use the same port as the first call for that logical connection.
�single precision: (1) The specification that causes the floating-point value to be stored internally in the short format. See also double precision.; (2) The use of one computer word to represent a number, in accordance with the required precision.
�single-precision floating point number: A 32-bit approximate representation of a real number. See also floating-point number.
�single-process installation: The process of installing licensed programs one at a time.
�single quote: See quotation mark.
�single-selection field: In System i Access, a list from which a user can select only one item.
�single session: A type of APPC connection with limited function. A single-session connection supports only one session and does not have SNA service manager support.
�single set: A single CD-ROM that contains one licensed program or a separately orderable feature for the system and its secondary languages.
�single sign-on (SSO): An authentication process in which a user can access more than one system or application by entering a single user ID and password. See also global sign-on.
�single system image (SSI): (1) The collection and presentation of data about multiple CICS systems as though they were a single CICS system. In CICSPlex SM, the single-system image is provided by the CICSPlex SM address space (CMAS).; (2) A cluster of DirectTalk systems that are connected together using a local area network. Each system (known as a node) in the cluster is configured as either a client or a server.
�single-system sysplex: A sysplex in which only one system can be initialized as part of the sysplex. In a single-system sysplex, cross-system coupling facility (XCF) provides XCF services on the system, but does not provide signaling services between MVS systems.
�single threading: The execution of a program to completion. Processing of one transaction is completed before another transaction is started.
�single-thread test: In CICS, a test of a single application or transaction running by itself. See also multithread test.
�singleton: A class that can be instantiated only once. A singleton class cannot be an interface.
�single-valued: Pertaining to a model element whose Multiplicity Type:: upper attribute is set to 1. See also multivalued.
�single-VSE environment: An environment that supports one VSE image. See also VSE image.
�sink: A port that takes voice data from the SCBus. See also source.
�SIO: See service information octet.
�SIP: See Session Initiation Protocol.
�SIT: See system initialization table.
�site: In cross-site mirroring, a location containing a node or nodes with access to either the production copy or mirror copy. The sites can be in close proximity or geographically dispersed.
�site administrator: A defined role in WebSphere Commerce that installs, configures, and maintains WebSphere Commerce and the associated software and hardware. See also access group, customer group.
�site certificate: A certificate obtained for an individual site. A site certificate is different from a trusted root certificate in that a site certificate lets you access only a specific site. A trusted root certificate lets you access any servers with certificates issued from that trusted root certificate authority.
�site primary node: In cross-site mirroring, a node that owns the independent disk pool, either the production copy or mirror copy, at a particular site. The production-site primary node is also the primary node for the cluster resource group. The mirror-site primary node is a backup node in a cluster resource group.
�situation: (1) Any significant change in the state of a system resource, as represented in a Common Base Event. An event can be generated for a situation, such as a problem, the resolution of a problem, or the successful completion of a task. See also Common Base Event.; (2) A set of conditions that, when met, creates an event. A condition consists of an agent attribute, an operator such as greater than or equal to, and a value. It can be read as, "If - system condition - compared to - value - is true". An example of a situation is: IF - CPU usage - GT - 90% - TRUE. "IF" and "TRUE" are part of every situation. The expression "CPU usage GT 90%" is the situation condition.; (3) A significant occurrence that is detected when a set of conditions are met. For example, exceeding the limits of a Key Performance Indicator (KPI).
�situation event: A Common Base Event that is emitted when a defined situation occurs.
�SIU: See smallest installable unit.
�sizing border: In VisualAge RPG, the border or frame around a control or set of controls that allows resizing of the control by selection with the mouse or the keyboard.
�skeleton: Scaffolding for an implementation class.
�skew: (1) The position of being slanted or tilted; oblique.; (2) The time difference between two clocks or clock values.
�skin: An element of a graphical user interface that can be changed to alter the appearance of the interface without affecting its functionality.
�skip: (1) To ignore one or more instructions in a sequence of instructions.; (2) A move of the current print position to another location.
�SKU: See stock keeping unit.
�SL: See standard label.
�SLA: See service level agreement.
�slash: The character /, also known as forward slash. This character is named <slash> in the portable character set.
�SLC: See signaling link code.
�SLDS: See system log data set.
�slice: The set of blocks that contains pages with data having a certain value of one of the clustering dimensions.
�slice label: In the GDDM function, the alphanumeric label that a user can assign to each slice on a pie chart.
�slide: Hardware attached to a device that moves the device in and out of the rack in a drawer-like action. See also rail.
�slider: A graphical representation of a quantity and its relationship to the range of possible values for that quantity. A user can change the value of the quantity by using the slider.
�sliding window: A positive acknowledgment and retransmission technique, used by protocols when sending a stream of packets, that allows the sender to transmit a certain number of packets (usually about 10 packets) before an acknowledgment arrives. After the sender receives an acknowledgment for the first packet, it "slides" along the stream and sends another.
�SLIP: See Serial Line Internet Protocol.
�SLM: See service level management.
�SLO: See service level objective.
�slot: (1) A section of a JSP set aside for displaying personalized data or content.; (2) A space in a library where a cartridge is stored. See also cell.; (3) For a fixed-length relative record data set (RRDS), the data area addressed by a relative record number that may contain a record or be empty.
�slot condition: See attribute condition.
�SLP: See Service Location Protocol.
�SLS: See signaling link selection.
�SLU: See secondary logical unit.
�SLU2: A secondary logical unit that uses LU2 protocols.
�SLU P: An LU0 protocol defined by IMS as a protocol to communicate between a programmable workstation, such as a 4700, and IMS. IMS is the Primary Logical Unit (PLU) and the workstation is the Secondary Logical Unit (SLU) in the connection.
�SMAE: See systems management application entity.
�Small Computer System Interface (SCSI): (1) An ANSI-standard electronic interface that allows personal computers to communicate with peripheral hardware, such as disk drives, tape drives, CD-ROM drives, printers, and scanners faster and more flexibly than previous interfaces. See also iSCSI, fixed-block device, SCSI device.; (2) A standard hardware interface that enables a variety of peripheral devices to communicate with one another. See also target.
�small-data-set packing (SDSP): In DFSMShsm, the process used to migrate data sets that contain actual data that is equal to or less than a specified amount. The data sets are written as one or more records into a Virtual Storage Access Method (VSAM) data set on a migration-level-1 volume.
�small-data-set-packing data set: In DFSMShsm, a Virtual Storage Access Method (VSAM) key-sequenced data set (KSDS) allocated on a migration-level-1 volume and containing small data sets that have been migrated.
�smallest installable unit (SIU): The file or set of files that comprise the atomic (non-aggregated) installable unit (IU) that is intended to be deployed into a single hosting environment. The SIU delivers the capability of the IU and its descriptor. An SIU can be added and aggregated with other IUs into a container installable unit (CIU) or into a solution module. See also container installable unit, hosting environment, solution module.
�small form-factor pluggable transceiver (SFP transceiver): An optical transceiver used to convert signals between optical fiber cables and switches.
�small integer: In DB2 for i5/OS, a data type indicating that the data is a binary number with a precision of 15 bits.
�small programming enhancement (SPE): In zSeries, any new function being shipped in the service stream as a Development APAR (D-APAR), including rollback to lower releases of new release line items. Each SPE is managed as a line item within the scope of a given release, regardless of whether the new function is being integrated into that release or not.
�small queue element: A queue element that is smaller than the smaller of either the limiting value specified during the customization of MERVA or 32KB.
�Smalltalk: A library-oriented programming language that uses a large library and an interactive environment to produce window-based graphical user interfaces.
�SMAPP: See system-managed access-path protection.
�smart card: An intelligent token that is embedded with an integrated circuit chip that provides memory capacity and computational capabilities
�smart phone: A phone that enables connections to the Internet or Lotus Notes network so that users can access e-mail, faxes, voice mail, Web pages and other files. It can also connect to a speech recognition server by phone so that a user can dictate notes or responses and then see the recognized text as it is returned from the server.
�smart relay host: A mail relay or mail gateway that has the capability to correct e-mail addressing problems.
�SmartSet: A customer-defined group of objects that can be acted on as an entity by some Tivoli functions, facilitating policy-based management. Users define SmartSets by specifying selection criteria or by identifying specific objects. Examples of criteria-derived SmartSets are all Cisco routers or all routers with a status of critical.
�SMB: (1) See system-managed buffering.; (2) See scheduler message block.
�SMBIOS: See system management BIOS.
�SMD: See solution module descriptor.
�SMDE: See system-managed directory entry.
�SMDI: See Simplified Message Desk Interface.
�SMF: See System Management Facilities.
�SMF header: Component of a CICS monitoring or statistics SMF record that describes the system creating the output.
�SMF product section: Component of a CICS monitoring or statistics SMF record. The SMF product section describes the CICS data section that follows it in the record and contains operational data pertaining to the processing of the data.
�SMF record: A collection of information about capacity and system management that is written to a Systems Management Facility (SMF) data set. Each SMF record includes information about the system's configuration, paging activity, and workload.
�SMF type 6 record: The record that PSF uses to record data for each print data set.
�SMI: See Structure of Management Information.
�S/MIME: See secure/MIME.
�SMI-S: See Storage Management Initiative Specification.
�SMIT: See System Management Interface Tool.
�SMO (SMO): See service message object.
�smoke test: A subset of tests that can be run against each software build to determine whether the software has regressed in form or function since a previous build.
�smoothness of curve: In the GDDM function, the connection of the plotted points in a data group by a continuous curve. On the System/370 system GDDM function, called curve fitting.
�SMP: (1) See symmetric multiprocessor.; (2) See symmetrical multiprocessor system.
�SMP/E: See SMP/E for z/OS.
�SMP/E for z/OS (SMP/E): An IBM licensed program that is used to install software and software changes on z/OS systems.
�SMP Expansion Module: An IBM xSeries hardware option. It is a single module that contains microprocessors, disk cache, random access memory, and three SMP Expansion Port connections. Two SMP Expansion Modules can fit in a chassis.
�SMP system: See symmetrical multiprocessor system.
�SMS: (1) See Software Management Services.; (2) See storage management subsystem.; (3) See Short Message Service.
�SMSC: See short message service center.
�SMS class: A list of attributes that the storage management subsystem (SMS) applies to data sets having similar allocation (data class), performance (storage class), or backup and retention (management class) requirements.
�SMS complex (SMSplex): A group of one or more systems that share a common storage management subsystem (SMS) configuration. All systems in an SMSplex share a common set of SMS control data sets: the active control data set (ACDS) and the communications data set (COMMDS).
�SMS configuration: The entity that DFSMS uses to manage storage: a base configuration; definitions of storage management subsystem (SMS) classes, group, library, and drive definitions; and automatic class selection (ACS). See also active configuration, base configuration, source control data set.
�SMSI: See Simplified Message Service Interface.
�SMS-managed volume: A volume, managed by the storage management subsystem (SMS), that is defined in the active configuration.
�SMSplex: See SMS complex.
�SMS table space: See system-managed space table space.
�SMSVSAM: The name of the VSAM server that provides VSAM record-level sharing (RLS). See also VSAM record-level sharing.
�SMT: See symmetric multithreading.
�SMTP: See Simple Mail Transfer Protocol.
�smurf attack: A denial-of-service attack in which a spoofed source address is flooded with echo replies. The replies are caused when many ping (ICMP echo) requests using the spoofed source address are sent to one or more broadcast or multicast addresses.
�SNA: See Systems Network Architecture.
�SNA 3270 API: See SNA 3270 program interface.
�SNA 3270 device emulation: A function of the operating system that allows a system to appear to the host system as a 3274 Control Unit.
�SNA 3270 program interface: A function that allows an application program to communicate with a System/370, 30xx, or 43xx VTAM program by sending and receiving 3270 data streams.
�SNA-attached: In PSF, pertaining to a device that is linked to the host system through VTAM or ACF/VTAM and uses an SNA protocol to transfer data. See also TCP/IP-attached.
�SNA backbone: In an SNA network, the set of all interconnected nodes that consist of 37xx products running the Network Control Program.
�SNA character string (SCS): In SNA, a string of EBCDIC control characters carried within a request/response unit (RU); the string can also contain user data.
�SNA distribution services (SNADS): See Systems Network Architecture distribution services.
�SNADS (SNA distribution services): See Systems Network Architecture distribution services.
�SNADS receiver: A user-configured (using the ADDCMNE command) batch job that is started in the subsystem specified on the communications entry when the system receives SNADS distribution from a sending system in the SNADS network. See also SNADS sender.
�SNADS router: A system-provided batch job that runs in the QSNADS subsystem and routes distributions to the configured distribution queue.
�SNADS sender: A user-configured (by using the CFGDSTSRV command to add the SNADS distribution queue) batch job that is started in the QSNADS subsystem, and sends distributions to another system in the SNADS network. See also SNADS receiver.
�SNA/File Services (SNA/FS): See Systems Network Architecture File Services.
�SNA/FS (SNA/File Services): See Systems Network Architecture File Services.
�SNA/Management Services Transport: See Systems Network Architecture Management Services Transport.
�S-name: In C, a single-case external modifier that is, at most, 8 characters in length.
�SNA/MS Transport: See Systems Network Architecture Management Services Transport.
�sNaN: See signaling NaN.
�SNA network: The part of the user application network that conforms to the formats and protocols of Systems Network Architecture (SNA). The SNA network consists of network addressable units (NAUs), a gateway function, intermediate session routing function components, and the transport network.
�SNA/NJE: See Systems Network Architecture/network job entry.
�SNA pass-through: The i5/OS software processes through which SNA data is passed from source secondary applications or devices to target primary applications. SNA pass-through supports LU session types 0 through 3.
�snap dump: A dump that can be requested by a task at any time during which that task is being processed.
�snap-in: A registered user exit program that is defined to be called from mail server framework user exit points. The mail server framework user exit points are referred to as ports by the mail server framework. Systems will snap-in the programs that are needed to operate.
�snap-in provided information (SPIN): An area where snap-in user exit points programs can store information that other snap-ins can use. SPIN provides a place where information relating to a specific recipient can be stored and used by snap-ins in the same user exit point or in different user exit points. The information that is stored in snap-in provided information is completely user defined and interpreted data.
�SNA Primary LU2 Support (SPLS): The i5/OS communications support that allows 3270-type displays and 3287-type printers to communicate with System i systems through an SNA network.
�snapshot: (1) A record of the current state of the database environment.; (2) In Tivoli NetView, a copy of a map that reflects the topology and status of the map's nodes and links at a given moment in time.; (3) A copy of changed data in the active files and directories of a file system with the exception of the inode number, which is changed to allow application programs to distinguish between the snapshot and the active files and directories.
�SnapShot: A function of the IBM RAMAC Virtual Array (RVA) that allows an instantaneous copy to be made of data sets using DFSMS software.
�snapshot copy: A copy services function that can quickly copy data from a source location to a target location.
�snapshot dump: See snap dump.
�snapshot view: A view that uses a local file system to access versions of elements.
�SNA remote job entry: See remote job entry.
�SNA report code: In SNA, a registered code identifying the condition that is being reported.
�SNA sense data: An SNA-defined encoding of error information. In SNA, the data sent with a negative response, indicating the reason for the response.
�SNASVCMG mode name: SNA service manager mode name. This is the architecturally defined mode name identifying sessions on which CNOS is exchanged. Most APPC-providing products predefine SNASVCMG sessions.
�SNA upline facility (SNUF): The communications support that allows a System i system to communicate with CICS/VS and IMS/VS application programs on a host system. For example, DHCF communicates with HCF and DSNX communicates with the NetView Distribution Manager program.
�SNBU: See switched network backup.
�SNIA: See Storage Networking Industry Association.
�sniffing: The practice of monitoring or eavesdropping on electronic transmissions. Information that is sent across the Internet might pass through many routers before it reaches its destination. Any of those routers can sniff the transmission and attempt to interpret the information. Passwords or other confidential information that is sent in an unencrypted form might be discovered.
�snippet: An excerpt of source code.
�SNL: See SWIFTNet Link.
�SNMP: See Simple Network Management Protocol.
�SNMP Access and Trap Forwarding: An IBM Director Agent feature that enables SNMP to access managed-system data. When installed on a managed system, this feature enables SNMP-based managers to poll the managed system and receive its alerts. If System Health Monitoring is installed on the managed system also, hardware alerts can be forwarded as SNMP traps.
�SNMP agent: A server process that resides on a network node and is responsible for communicating with managers regarding that node. The node is represented as a managed object, which has various fields or variables that are defined in the appropriate MIB.
�SNMP device: An embedded device that uses SNMP to monitor network-attached devices, printers, or computers for conditions that require system-management attention.
�SNMP manager: A managing system that runs a managing application or suite of applications. These applications depend on Management Information Base (MIB) objects for information that resides on the managed system. The SNMP manager generates requests for this MIB information, and an SNMP agent on the managed system responds to these requests.
�SNRM: See set normal response mode.
�SNT: See sign-on table.
�SNTTE: See sign-on table terminal entry.
�SNUF: See SNA upline facility.
�SOA: See service-oriented architecture.
�SOAP: A lightweight, XML-based protocol for exchanging information in a decentralized, distributed environment. SOAP can be used to query and return information and invoke services across the Internet.
�SOAP encoding: Rules for serializing data over the SOAP protocol. SOAP encoding is based on a simple type system that is a generalization of the common features found in type systems in programming languages, databases, and semi-structured data.
�soap-opera testing: A technique for defining test scenarios by reasoning about dramatic and exaggerated usage scenarios. Like a soap opera on television, these scenarios reflect "real life", but are condensed and exaggerated to depict dramatic instances of system use.
�SOAP with attachments API for Java (SAAJ): An application programming interface (API) that is used to send XML documents over the Internet from a Java base.
�SOA record: See start-of-authority record.
�Society for Worldwide Interbank Financial Telecommunication (SWIFT): An industry-owned cooperative that supplies standardized messaging services and software to financial institutions.
�socket: (1) A communications handle used by TCP/IP.; (2) An identifier that an application uses to uniquely identify an end point of communication. The user associates a protocol address with the socket by associating a socket address with the socket.; (3) A means for directing data to an application in a TCP/IP network using a unique identifier that is a combination of an IP address and a port number.; (4) In the Network Computing System (NCS), a port on a specific host; a communications end point that is accessible through a protocol family's addressing mechanism. A socket is identified by a socket address.; (5) A callable TCP/IP programming interface that TCP/IP network applications use to communicate with remote TCP/IP partners.
�socket address: A data structure that uniquely identifies a specific communications end point. It also specifies the protocol family. For example, a TCP/IP socket address consists of a port number and a host address.
�socket API: See socket application programming interface.
�socket application programming interface (socket API): An industry standard API that provides application programs with a connection-oriented or a connectionless transfer of data over multiple protocols.
�Sockets Secure (SOCKS): (1) A mechanism by which a secure proxy data channel can be established between two computers.; (2) A client/server architecture that transports TCP/IP traffic through a secure gateway. A SOCKS server performs many of the same services that a proxy server does.
�sockets server: See SOCKS server.
�SOCKS: See Sockets Secure.
�socks-enabled: Pertaining to TCP/IP software, or to a specific TCP/IP application, that understands the SOCKS protocol.
�SOCKS server: A proxy server that provides a secure one-way connection through a firewall to server applications in a nonsecure network. The server applications in the secure network must be compatible with the socket interface.
�soft booking: The allocation of a resource that assigns the resource to work on a project for its entire duration. Contoured work is placed in a proposed state.
�soft checkpoint: The process of writing information to the log file header; this information is used to determine the starting point in the log in case a database restart is required.
�soft commit: A form of commitment control that differs from traditional commitment control in that it limits the number of times that the system writes journal entries that are associated with a transaction to disk. Soft commit improves transaction performance and guarantees transaction atomicity, but does not guarantee the durability of recently committed transactions in case of a system failure.
�softcopy: One or more files that can be electronically distributed, manipulated, and printed by a user.
�soft error: (1) An error that occurs sporadically and that may not appear on successive attempts to read data.; (2) An intermittent error on a network that requires retransmission. A soft error by itself does not affect overall reliability of a network, but reliability may be affected if the number of soft errors reaches the ring error limit.
�soft error page: A type of Web page that provides information about why the requested Web page cannot be returned. For example, instead of returning a simple status code, the HTTP server can return a page that explains the status code in detail.
�soft page segment: A resource that is not declared in the Map Page Segment structured field but is sent to the printer inline with data.
�soft resource: A resource that is not declared in a Map structured field but is sent to the printer inline with data. It cannot be reused during the job without being reloaded to the printer. See also hard resource.
�software: The programs, procedures, rules, and associated documentation pertaining to the operation of a system. See also hardware.
�software catalog: All software defined in the data center model.
�software compliance check: A compliance check that determines if a software application should be present on a computer. See also security compliance check.
�software configuration management (SCM): The tracking and control of software development. SCM systems typically offer version control and team programming features.
�software configuration template: A set of parameters that define configuration options and software resources to create on a managed system during software installation.
�software definition: The deployment configuration that describes how to install one or more installable software dependencies. It includes a list of installable files, software prerequisites, and advanced attributes. See also installable file.
�software development kit (SDK): A set of tools, APIs, and documentation to assist with the development of software in a specific computer language or for a particular operating environment.
�software distribution application: An application that controls software management tasks such as software distribution, configuration, version control, and asset inventory management.
�software distribution catalog: A file that contains a list of the installed software packages and their associated version number.
�Software Engineering Process Authority (SEPA): The organizational entity with responsibility for process definition, assessment and improvement.
�software installation: The set of files that is created by an installable file.
�software instance: An activation of an application system or environment.
�software license key: An authorization that regulates the use of software licensed programs. Software license keys need to be installed on the system when software is upgraded or moved, the hardware processor group is changed, additional license usage is added, or new software that requires license keys is purchased.
�software life cycle: The set of states that represent a software component within an IT environment. Throughout the life cycle of a software component, change management operations affect the state of the component.
�Software Management Services (SMS): A set of offerings that provide the user with a consistent distribution, installation, and service strategy for both IBM licensed programs and System Manager-packaged programs.
�software package: (1) In software distribution, a compressed text file that describes the actions to perform on the target system to which it is distributed. See also stanza.; (2) A file that defines a collection of artifacts and the actions to take with those artifacts on the target system to which it is distributed.
�software package block: In software distribution, a file that contains the resources referred to by the actions in a software package.
�software package definition: In software distribution, a non-compressed text file that describes the actions to perform on the target system to which it is distributed. Formerly called file package definition.
�Software Platform Extension (SPX): The collection of architectures and specifications that define how the IBM software componentization strategy is implemented, and guide the changes to IBM software development processes, management systems, and culture.
�software repository: An internal library of software patches and associated installation and configuration data.
�software requirements specification (SRS): A requirement that defines the external behavior of the system to be built. Sometimes called a functional specification.
�software resource: Installed software, software configurations, and application data that is created when a piece of software is installed. Software resources are defined by a software configuration template.
�software scanner: Software scanner verifies that the provided signature catalog is syntactically correct.
�software signature: A signature that is used in system management applications to represent and detect installed software products.
�software specification review (SSR): In the waterfall life cycle, the major review held when the software requirements specification is complete.
�software stack: A list of software products, organized in the required installation order. A software stack can contain individual pieces of software as well as other software stacks.
�software support facility (SSF): An IBM online database that allows for storage and retrieval of information about all current authorized program analysis reports (APARs) and program temporary fixes (PTFs).
�software system: A set of runtime software components and computing devices (on which these components are deployed) that interoperate to provide the system's functionality.
�software transparency: Criteria applied to a processing environment that states that changes do not require modifications to the host software in order to continue to provide an existing function.
�software view: A way to organize software in the data center based on specific criteria. There are two types of software views. Public views are available to all users. Personal views are specific to the user account of the person who created them.
�SOH character: See start-of-header character.
�SOI: (1) See Silicon-On-Insulator.; (2) See service-oriented integration.
�solicited: Pertaining to the act of requesting information from an autonomic manager. See also unsolicited.
�solicited message: A response from VTAM to a command entered by a program operator. See also unsolicited message.
�solid compound: A compound that does not have any white space, for example: 'Autofahren' in German. See also compound word, multiword expression.
�solution: A combination of products that addresses a particular customer problem or project. A solution is the realization of a business process. See also code project.
�Solution Install: A core capability of the IBM Autonomic Computing Initiative that addresses the need to easily deploy complex systems.
�Solution Installation for Autonomic Computing: The core technology of the IBM Autonomic Computing initiative that provides a single, consistent installation technology that provides standard methods for determining dependencies, deploying and configuring components into a complex system, and analyzing the system for failed components.
�Solution Install runtime environment: A subset of the Solution Install code that includes the Java Virtual Machine (JVM), core classes, executables, and files.
�solution instance: A managed resource that represents a collection of other managed resources, which can be managed as a single unit. An example of a solution instance is a composite application that includes a set of J2EE applications, queues, and message flows.
�solution module: The installable unit (IU) that aggregates smallest installable units (SIUs), container installable units (CIUs), and other solution modules for multiple hosting environments. The solution module also contains a descriptor for the SIUs, CIUs, and solution modules. See also installable unit, smallest installable unit.
�solution module descriptor (SMD): See installable unit deployment descriptor.
�solution module installable unit: See solution module.
�SOM: See System Object Model.
�sort: To rearrange some or all of a group of items, based upon the contents or characteristics of those items.
�sorted map: A sorted flat collection with key and element equality.
�sorted relation: A sorted flat collection that uses keys, has element equality, and allows duplicate elements.
�sorted search: A search that allows a client to receive search results sorted based on a list of criteria, where each criteria represents a sort key. This moves the responsibility of sorting from the client application to the server, where it might be done more efficiently.
�sorted set: A sorted flat collection with element equality.
�sort file: In COBOL, the temporary file that contains all the records to be sorted by a SORT statement. The sort file is created and used only by the sort function.
�sorting: The process of establishing a specific order for the information in a RequisitePro view. See also filtering, query.
�sort-merge file description entry: In COBOL, an entry in the File Section of the Data Division that is composed of the level indicator SD, followed by a file name, and then followed by a set of file clauses as required.
�sort sequence: The order in which characters are arranged within the computer to sort, combine, or compare data. A binary sort uses the internal representation of a character to sort characters in a sequence. When you use binary representation to sort characters, your resulting data may not be in the order that you expect.
�sort sequence table: A table containing the order in which characters are arranged within the computer for sorting, combining, or comparing.
�sort utility: A function of the operating system used to arrange records in a sequence determined by data contained in one or more fields in the record.
�SOS: See short-on-storage.
�source: (1) In VisualAge RPG, a part that can notify target parts whenever the state of the source part changes. A source part can have multiple targets.; (2) A system, a program within a system, or a device that makes a request to a target.; (3) A resource, such as a host, that is being monitored by an event adapter.; (4) A port that places voice data on the SCBus. See also sink.; (5) The markup-language pertaining to files that define a HATS project or one of its resources. Also the name of a folder contained in each HATS project.; (6) In distributed data management (DDM), the platform that originates a request for remote data. See also Distributed FileManager, target.
�source address: The location from which information is to be sent. See also destination address.
�source application: An application whose data is collected from its operational data stores and placed into the central data warehouse using an extract, transform, and load (ETL) process. See also consumer application.
�source based map: A map based on the order elements that are defined in the source document definition.
�source catalog entry: A product or SKU that contains one or more merchandising associations. When a source catalog entry is displayed, the user can view the defined merchandising associations. See also target catalog entry.
�source code: A computer program in a format that is readable by people. Source code is converted into binary code that can be used by a computer. See also object code.
�Source Code Control System (SCCS): A program for maintaining version control of the source files in a developing program. SCCS stores the changes made to a file instead of the changed file, thus allowing several versions of the same file to exist in the system.
�source control data set: A linear data set (LDS) containing a storage management subsystem (SMS) configuration. The SMS configuration in an SCDS can be changed and validated using the Interactive Storage Management Facility (ISMF). See also active control data set, communications data set, control data set, SMS configuration.
�source data queue program: In System i Access, a series of PC programs that allow end users or user-written programs to manipulate data using data queues.
�source debugger: A tool for debugging Integrated Language Environment (ILE) programs by displaying a representation of their source code. See also symbolic debugger.
�sourced function: (1) A function that duplicates the semantics of another function, called a source function. Only scalar and aggregate functions can be sourced functions. See also function, routine.; (2) A function that is implemented by another built-in or user-defined function that is already known to the database manager. This function can be a scalar function or an aggregate function; it returns a single value from a set of values (for example, MAX or AVG). See also external function, SQL function, built-in function.
�source directory: In VisualAge RPG, the directory in which all source files for the VRPG application are stored.
�source distributed data manager (SDDM): In a distributed data management network, programming support that translates local data management requests for remote files or SQL requests for a remote database into a DDM request, establishes communications to the remote system where the data file or database is located, and sends the request to the remote (target) system for processing. See also target distributed data manager.
�source document: A document that is going to be translated.
�source document definition: A description of a document layout that is used to identify the format of the source document for a translation.
�source file: A file of programming code that is not compiled into machine language. See also data file.
�source host: The managed node on which the source files and directories referred to in a software package or a file package reside.
�source ID (SID): The 3-byte identifier of the originator device.
�source interface: In a mediation flow component, the interface that allows the service requester to access the mediation flow through an export.
�source language: A programming language acceptable as input to a translator.
�source listing: A portion of a compiler listing that contains source statements and, optionally, test results.
�source member: A member of a database source file that contains source statements, such as ILEC, COBOL, RPG, or DDS statements.
�source module: See source program.
�source node: The node on which a data management event is generated.
�source overlay: In AFP Utilities, a file member that contains the definition of an overlay.
�source physical file: In i5/OS, a file that contains members and that stores text or source statements instead of data.
�source program: (1) A set of host language statements and SQL statements that is processed by an SQL precompiler.; (2) A set of instructions that are written in a programming language and must be translated into machine language before the program can be run.; (3) In communications, the program that starts a session with a remote system. See also target program.; (4) In DB2 for i5/OS, the source in an i5/OS source file member used to create an SQL program.
�source queue manager: See local queue manager.
�source release: During software upgrades, the version, release, and modification level of the installed product before a new level of the product is installed. See also target release.
�source root: The directory that source files are relative to. This is also used as the target for code generation.
�source route bridging: In LANs, a bridging method that uses the routing information field in the IEEE 802.5 medium access control (MAC) header of a frame to determine which rings or token-ring segments the frame must transit. The routing information field is inserted into the MAC header by the source node. The information in the routing information field is derived from explorer packets generated by the source host.
�source router: In LANs, the router that determines the route that the frame will follow.
�source routing: In LANs, a method by which the sending station determines the route the frame will follow and includes the routing information with the frame. Bridges then read the routing information to determine whether they should forward the frame.
�source segment: A database segment containing the data used to construct the secondary index pointer segment.
�source server: (1) A database or subsystem that contains the source tables for replication.; (2) A server that is being upgraded with new hardware or software or whose data is being migrated.; (3) In distributed data management (DDM), the function that converts source requests to data streams containing DDM commands and output data, and sends them over the network to the target server.
�source service access point (SSAP): In SNA and TCP/IP, a logical address that allows a system to send data to a remote device from the appropriate communications support. See also destination service access point.
�source statement: A statement written in the symbols of a programming language. For example, COBOL, RPG, and DDS statements are source statements.
�source system: (1) In communications, the system that issues a request to establish communications with another system.; (2) In distributed data management (DDM), a system containing an application program that requests access to data in another system.; (3) The system that sends information in a network of systems that exchange objects and data. See also target system.; (4) The system that currently owns the production copy of an independent disk pool in a cross-site mirroring (XSM) environment. Changes to the production copy of an independent disk pool are replicated to all mirror copies of the independent disk pool that exist on backup nodes within the recovery domain.
�source table: A table that contains data that is to be replicated to a target table. See also target table.
�source temporary store (STS): The SMP/E primary data set, used to hold updated versions of source elements.
�source tree: The XML input document that is transformed by an XSL stylesheet.
�source type: (1) An existing type that is used to internally represent a distinct type.; (2) In the application development tools, a characteristic of i5/OS members that allows the user to select a subset of the members available in a CoOperative Development Environment/400 session. Source types include i5/OS members with a particular member type.
�SP2: See Scalable Parallel 2.
�SPA: See scratchpad area.
�space: (1) A sequence of one or more blank characters.; (2) Any storage area that can be directly accessed, down to its individual (8-bit) bytes, by a machine interface user such as a program or procedure.; (3) A site intended for storage of data, such as a location in a storage medium.
�space bar: A control key for the spacing function.
�space character: In the portable character set, the <space> character.
�space management: (1) The process of keeping sufficient free storage space available on a client node by migrating files to server storage. The files are migrated based on criteria defined in management classes to which the files are bound and the include-exclude list.; (2) The process of managing aged data sets on DFSMShsm-managed and migration volumes. The three types of space management are migration, deletion, and retirement.
�space token (STOKEN): An 8-byte identifier for an address space, data space, or hiperspace. A STOKEN is similar to an address space identifier (ASID), except for two important differences: the system does not reuse the STOKEN value while a program is running and data spaces do not have ASIDs.
�SPACK: A logical component consisting of a base card, which connects to the digital trunk adapter in the RS/6000, and a trunk interface card (TIC), which manages the trunk connection to the switch. See also VPACK, XPACK.
�span: (1) A user-defined group of network resources within a single domain. Spans provide a level of security by allowing the system administrator to define (a) the resources to which an operator can issue commands, (b) the views of resources that an operator can display, and (c) the resources in a view that an operator is allowed to see (an operator might not be authorized to see all the resources in a particular view).; (2) An attribute of a policy that defines the range of influence of a policy in a policy hierarchy. For example, the span attribute indicates whether a policy in a policy hierarchy is inherited only by its immediate child nodes or by its immediate child nodes and all their descendents.
�span check: The process of verifying that an operator is authorized to perform actions on a network resource, a NetView management console view, or a resource within a view.
�spanned record: (1) A logical record stored in more than one block on a storage medium.; (2) In the Virtual Storage Access Method (VSAM), a logical record whose length exceeds control interval length and, as a result, crosses, or spans, one or more control interval boundaries within a single control area.
�spanning tree: A loop-free subset of a network topology.
�spare: An extra storage component, such as a disk drive or tape, that is predesignated for use as a replacement for a failed component.
�spare metadata server: An idle metadata server that has no statically assigned file sets. It is used for failover to take on the workload of another metadata server that goes offline.
�spare pool: See resource pool.
�spatial column: A column in a table that is defined using one of the spatial data types provided by DB2 Spatial Extender.
�spatial data: Data that is made up of coordinates that identify a geographic location or geographic region.
�spatial function: A function provided by DB2 Spatial Extender that performs various operations on spatial data.
�spatial reference system: In DB2 Spatial Extender and DB2 Geodetic Extender, a set of parameters that includes coordinates that define the maximum possible extent of space that is referenced by a given range of coordinates, an identifier of the coordinate system from which the coordinates are derived, and numbers that convert coordinates into positive integers to improve performance when the coordinates are processed.
�spatial reuse: A feature of Serial Storage Architecture (SSA) that enables a device adapter (DA) loop to support many simultaneous read/write operations. See also Serial Storage Architecture.
�spawn: A function in which a calling process (the parent process) creates a new process called a child process. The child process inherits attributes from the parent process. A new program is specified and starts running in the child process.
�SPCN: See system power control network.
�SP command: A CICS API command (COLLECT, DISCARD, INQUIRE, PERFORM, or SET) that requires the special CICS translator option, SP, and for which command security checking can be done.
�SPD: See system product division.
�SPD bus: A System i input/output bus architecture.
�SPDU: See session-layer protocol data unit.
�SPE: (1) See service provider equipment.; (2) See small programming enhancement.; (3) See Synergistic Processor Element.
�speaker-dependent speech recognition: Identification of spoken words based on knowledge of the speech characteristics of one speaker. See also speaker-independent speech recognition.
�speaker-independent speech recognition: Identification of spoken words based on aggregated knowledge of the speech characteristics of a population of speakers. See also speaker-dependent speech recognition.
�spec: See specification.
�special authority: The types of authority a user can have to perform system functions, including all object authority, save system authority, job control authority, security administrator authority, spool control authority, service authority, and system configuration authority. See also specific authority.
�special character: (1) A character other than a digit, a letter, or one of these characters: $, #, @, ., or _. For example, the following characters are special characters: *, +, and %.; (2) In COBOL, a character that is neither numeric nor alphabetic.; (3) In REXX, a token that acts as a delimiter when found outside a literal string. Special characters include the comma (,), semicolon (;), colon (:), right parenthesis ()), left parenthesis ((), and the individual characters from the operators.; (4) A character that is not alphabetic, numeric, or blank. For example, a comma (,) or an asterisk (*).; (5) A non-alphabetic and non-numeric character, such as %, &, /, ?, ], and a number of other characters that have a unique function in the SQL language.
�special-character keyboard set: In System i Access, an optional keyboard set, used by Western European countries and the Americas, that contains special characters like the Spanish tilde or the international currency symbol.
�special-character word: In COBOL, a reserved word that is an arithmetic operator or a relational character.
�special cost: The cost of a resource for work performed during non-standard working hours, such as overtime or holidays.
�special file: A file that provides an interface to input or output devices. There is at least one special file for each device attached to the computer.
�specialization: A user-supplied definition which replaces a corresponding template instantiation.
�special register: (1) A storage area that is defined for an application process by the database manager and is used to store information that can be referenced in SQL statements. Examples are USER and CURRENT DATE. See also global variable, built-in global variable.; (2) In COBOL, compiler-created data items used to store information produced by specific COBOL features (for example, the DEBUG-ITEM special register).
�special selling rate: The rate at which a resource's time is billed for work performed during non-standard working hours, such as overtime.
�special-subject: Generalization of a particular class of users; a product-defined entity independent of the user registry.
�special text: Text that allows document-placement information from views to be automatically recalculated as a postprocessing step. After the column formulas in a view are calculated, special text is replaced with an integer. For this reason, although special text appears to be a number, it is not.
�special variable: (1) In REXX, a variable set automatically by the language processor. Special variables are RC, RESULT, and SIGL.; (2) A variable that is similar to a local or global variable, except that it is predefined in Data Interchange Services. Special variables are created during translation at the start of a document and cannot be created or maintained by the user.
�specific applid: In XRF, the name used by the active CICS system when it opens the VTAM ACB. See also generic applid.
�specification (spec): (1) A declarative description of what something is or does.; (2) A document that describes, in a complete, precise, verifiable manner, the requirements, design, behavior, or characteristics of a system or system component, for the purpose of developing or validating the system.
�Specification 1170: A series of system interfaces, headers, and utilities. Specification 1170 is a superset (with some changes) of the POSIX 1003.1 and POSIX 1003.2 standards. Specification 1170 is also a superset of XPG4 Base. It includes sockets, the SVID real-time model for interprocess communications, and miscellaneous interfaces.
�specification X.21 (X.21): In data communications, a specification of the CCITT that defines the connection of data terminal equipment to an X.21 (public data) network.
�specific authority: The types of authority a user can be given to use the system resources, including object authorities and data authorities. See also special authority.
�specific function name: A particular user-defined function that is known to the database manager by its specific name. Many specific user-defined functions can have the same function name. When a user-defined function is defined to the database, every function is assigned a specific name that is unique within its schema. Either the user can provide this name, or a default name is used.
�specific gate: Entry point or interface to a CICS domain. A specific gate gives access to a set of functions that are provided by that domain only. The functions are likely to be requested by many different callers.
�specific poll: One of the locations on a polling list.
�specific polling: In Managed System Services, a type of polling used by the topology manager when collecting topology information for a particular system in the network.
�specified resolution: See format resolution.
�specifier: A name or keyword used in declarations to indicate storage class, fundamental data type and other properties of the object or function being declared.
�spectator: An individual member of a Sametime audience. See also audience.
�speech recognition: The process of identifying spoken words.
�Speech Recognition Control Language (SRCL): In WebSphere Voice Server, a structured syntax and notation used to define speech grammars. SRCL defines annotations, repetitions, words, phrases, and associated rules.
�speech recognition session: In WebSphere Voice Server, a sequence of recognition commands that allocate a recognition engine and return a unique identifier to identify the engine.
�speech synthesis: The production of speech by a computer, by putting together sounds that are created either algorithmically or from recordings of human speech.
�spell mode: The method of operation that uses spell aid and spell check functions to proofread and replace words in a document.
�SPF: See Shortest Path First.
�sphere: A Virtual Storage Access Method (VSAM) cluster with one or more associated alternate indexes and paths.
�sphere component: The Virtual Storage Access Method (VSAM) cluster (sometimes referred to as the base cluster), alternate indexes, and paths that compose a sphere.
�sphere of control: In SNA, a collection of network node control points for which another system is acting as a focal point. This collection includes both control points explicitly defined by the customer, if the controlling system is a primary focal point, and control points assumed by the system if the controlling system is a default focal point.
�sphere record: A collection of logically related records describing a Virtual Storage Access Method (VSAM) data set.
�SPI: (1) See Security Policy Index.; (2) See stub programming interface.; (3) See schedule performance index.
�spider label: In the GDDM function, a label used to add a comment or a note for a pie-chart slice. Each label is joined to its associated slice by a line.
�spill area: A storage area that is used to save the contents of registers.
�spill backup volume: A volume owned by DFSMShsm to which either all but the latest backup version of a data set are moved when more space is needed on a direct access storage device (DASD), daily, backup volume, or all valid versions are moved when a tape backup volume is recycled.
�spill file: In SQL replication, a temporary file that the Apply program creates to hold data for updating target tables.
�spill process: A DFSMShsm process that moves all but the latest backup version of a data set from a direct access storage device (DASD), daily, backup volume to a spill backup volume.
�spill queue: In Q replication, a dynamic queue that the Q Apply program creates to hold transactions that occur at the source table while a target table is being loaded. The Q Apply program later applies these transactions and then deletes the spill queue.
�spill storage group: See overflow storage group.
�SPIN: See snap-in provided information.
�spin button: A type of entry field that shows a scrollable ring of choices from which a user can select a choice. After the last choice is displayed, the first choice is displayed again. A user can also type a choice from the scrollable ring into the entry field without interacting with the spin button.
�spin data set: A data set that is available for printing, or deallocated, when it is closed.
�split horizon: A technique for minimizing the time to achieve network convergence. A router records the interface over which it received a particular route and does not propagate its information about the route back over the same interface.
�split task: A task that has an interruption in its duration.
�splitting: In OSI, the technique of a single transport connection using multiple network connections so that an application entity can use more than one line to send data on an association. Splitting can increase data throughput and resistance to network failure. It might be used, for example, to send a large file more quickly than if a single line were used. Splitting is available only with transport layer class 4.
�SPLS: See SNA Primary LU2 Support.
�SPOC: See single point of control.
�spoofed source address: A source IP address that is not the actual source address of a datagram, but the address of a victim of an attack. All responses to the datagram are sent to this source IP address.
�spoofing: The practice of masquerading as a trusted system to try to obtain confidential information. For example, when a would-be intruder sets up a client system with an IP address that is trusted by another system, it is called IP spoofing.
�spool: (1) The system function of putting files or jobs into disk storage for later processing or printing.; (2) To reduce, through the use of auxiliary storage as buffer storage, processing delays when transferring data between peripheral equipment and the processors of a computer.
�spool access support (SAS): A function of VSE/POWER that allows user programs or subsystems running on VSE system to access the spool files of VSE/POWER.
�spool control authority: A special authority that allows the user to perform spooling functions, such as display, delete, hold, and release spooled files on the output queue for himself and other users. This authority also allows the user to change the spooled file attributes, such as the printer used to print the file.
�spool data management: The recording and retrieval of data on the spool data set and the management of space within the spool data set.
�spool data set: A data set written on an auxiliary storage device and managed by the Job Entry Subsystem (JES).
�spool data set browse (SDSB): An application that allows a program to read spool data sets.
�spool device: A direct-access device used for intermediate storage of control blocks and data needed for processing jobs. During multiprocessing, the spool device becomes a collection point for job input data to be distributed to local mains, and for job output data coming from local mains on route to I/O devices attached to the global.
�spooled file: A file that holds output data waiting to be processed, such as information waiting to be printed.
�spool file: A file containing output that has been saved for later printing.
�spooling: The sending of data to auxiliary storage for later processing. The most common spooling application is print spooling.
�spooling job: A batch job that is started by the spooling subsystem.
�spooling reader: The general name to refer to the function of the diskette reader and the database reader.
�spooling subsystem: A part of the system that provides the operating environment for the programs that read jobs onto job queues to wait for processing and write files from an output queue to an output device. IBM supplies one spooling subsystem: QSPL.
�spooling writer: The general name to refer to the function of the diskette writer and printer writer.
�spool partition: A named collection of spool data sets.
�spot mapping: The assignment or correlation of a rule to a content spot.
�SPQB: See Subpool Queue Block.
�SPU: See Synergistic Processor Unit.
�SPUFI: See SQL Processor Using File Input.
�SPX: (1) See Sequenced Packet Exchange protocol.; (2) See Software Platform Extension.
�SPX Component Metamodel: A metamodel that defines the categories of software entities along with their characteristics and relationships in addition to features, capabilities, interfaces and versions, and clarifies how we can use these concepts to further clarify our component model. See also SPX Component Model Reference Architecture, SPX component model, SPX Component Modeling UML Profile.
�SPX component model: A formal specification of specific offerings, assemblies, common components, and features that conforms to the SPX Component Metamodel and is created in the SPX Component Modeling UML Profile. See also SPX Component Metamodel, SPX Component Modeling UML Profile.
�SPX Component Modeling UML Profile (SPX UML Profile): A tool for visually modeling how software components can be shared among development teams in a way that is conformant to the SPX Component Metamodel. See also SPX Component Metamodel, SPX component model.
�SPX Component Model Reference Architecture (CMRA): A reference architecture that defines the SPX Component Metamodel. See also SPX Component Metamodel.
�SPX model package: A container that provides a means to organize and specify visibility for software entities contained in an SPX component model. See also owner.
�SPX UML Profile: See SPX Component Modeling UML Profile.
�SQA: See system queue area.
�SQL: See Structured Query Language.
�SQL and XQuery compiler: A DB2 component that analyzes the semantics of an SQL or XQuery statement and produces an efficient executable form of the statement. See also section.
�SQL Assist: A tool that assists in formulating and running well-structured SQL statements. This tool can be accessed from multiple interfaces, including the DB2 Command Editor and the DB2 Control Center.
�SQL authorization ID (SQL ID): In DB2 for z/OS, the ID that is used for checking the authorization of dynamic SQL statements in some situations.
�SQLCA: See SQL communication area.
�SQL communication area (SQLCA): A set of variables that provides an application program with information about the execution of its SQL statements, XQuery expressions, or requests from the database manager.
�SQL connection: An association between an application process and a local or remote application server or database server. See also connection, session.
�SQLDA: See SQL descriptor area.
�SQL data change statement: An SQL statement, such as the INSERT, UPDATE, DELETE, or MERGE statement, that is used to make changes to data that is stored in user tables.
�SQL descriptor area (SQLDA): A set of variables in a structure used in the processing of certain SQL statements that describe input variables, output variables, or the columns of a result table. The SQLDA is intended for dynamic SQL programs.
�SQL/DS: See Structured Query Language/Data System.
�SQL function: A function that is implemented entirely by using a subset of SQL statements and SQL PL statements. See also function, routine, built-in function, sourced function.
�SQL ID: See SQL authorization ID.
�SQLJ: See Structured Query Language for Java.
�SQL method: A method that is implemented entirely by using a subset of SQL statements and SQL PL statements. See also method, routine.
�SQL path: An ordered list of schema names that is used to resolve unqualified references to user-defined functions, distinct types, and procedures.
�SQL PL: See SQL procedural language.
�SQL procedural language (SQL PL): A language extension of SQL that consists of statements and language elements that can be used to implement procedural logic in SQL statements. SQL PL provides statements for declaring variables and condition handlers, assigning values to variables, and for implementing procedural logic. See also inline SQL PL.
�SQL procedure: A user-written program that is implemented entirely by using a subset of SQL statements and SQL PL statements and that is invoked by using the SQL CALL statement. See also SQL routine, routine, procedure.
�SQL processing conversation: Any conversation that requires access of DB2 for z/OS data, either through an application or by dynamic query requests. See also conversation.
�SQL Processor Using File Input (SPUFI): A facility of the TSO attachment subcomponent that enables the DB2I user to run SQL statements without embedding them in an application program.
�SQL query: (1) In query management, a type of query that is created by running an IMPORT command against a file containing an SQL statement.; (2) A component of certain SQL statements that specifies a result table.
�SQL replication: A type of replication that uses staging tables. See also staging table, Q replication.
�SQL return code: The SQLSTATE or SQLCODE that indicates whether the previously run SQL statement completed successfully, with one or more warnings, or with an error.
�SQL routine: A function, method, or procedure that has its routine logic implemented entirely with SQL statements and SQL PL language elements and statements. See also SQL procedure, routine.

�SQL schema: A collection of database objects such as tables, views, indexes, functions, user-defined types, or triggers that defines a database. An SQL schema provides a logical classification of database objects.
�SQL statement: A complete instruction to the database manager that is written using SQL.
�SQL statement coprocessor: An alternative to the DB2 for z/OS precompiler that lets the user process SQL statements at compile time. The user invokes an SQL statement coprocessor by specifying a compiler option.
�SQL string delimiter: See string delimiter.
�SQL/XML: A section of the ISO Database Languages - SQL standard that defines XML-related functionality in SQL that allows SQL statements to construct, manipulate, and query XML data.
�SQL/XML constructor: A function that creates XML structures or typed atomic values within an SQL statement.
�square bracket: See bracket.
�SR-ASPDU: The status report application support PDU, which is used by MERVA Link for acknowledgment messages.
�SRB: See service request block.
�SRC: See system reference code.
�SRCB: See subrecord control byte.
�SRCL: See Speech Recognition Control Language.
�SRDS: See structure recovery data set.
�S reference point: In Performance Tools, the interface (including the cable) between the terminal equipment (TE) and network termination 2 (NT2).
�SRF: See symbol registration file.
�SRL: See system reference library.
�SRM: See system resources manager.
�SRM database object: See system resource management database object.
�SRS: See software requirements specification.
�SRT: (1) See Structure Rule Table.; (2) See system recovery table.
�SS: (1) See start-stop.; (2) One of the types of network services in the control point (CP) and in the logical unit (LU). These services provide facilities for an LU or a network operator to request that a control point (an ENCP, NNCP, or SSCP) assist with initiating or terminating sessions between logical units. Assistance with session termination is needed only by SSCP-dependent LUs.
�SS7: See Signaling System 7.
�SSA: (1) See Serial Storage Architecture.; (2) See segment search argument.
�SSA adapter: A physical adapter based on Serial Storage Architecture (SSA). SSA adapters connect disk drive modules (DDMs) to ESS clusters. See also Serial Storage Architecture, device adapter.
�SSAP: (1) See session-layer service access point.; (2) See source service access point.
�SSAP selector: In OSI, an external identifier for a service access point at the session layer. The SSAP selector is part of a presentation address.
�SSCP: See system services control point.
�SSCP dependent logical unit (SCP dependent LU): See dependent logical unit.
�SSCP domain: The system services control point (SSCP), the physical units (PUs), the logical units (LUs), the links, the link stations, and all the resources that the SSCP has the ability to control by means of activation and deactivation requests.
�SSCP ID: See system services control point identifier.
�SSCP-independent logical unit (SSCP-independent LU): See independent logical unit.
�SSCP-independent LU: See SSCP-independent logical unit.
�SSCP-LU session: In SNA, a session between a system services control point (SSCP) and a logical unit (LU). The session enables the LU to request the SSCP to help initiate LU-LU sessions.
�SSCP-PU session: In SNA, a session between a system services control point (SSCP) and a physical unit (PU); SSCP-PU sessions allow SSCPs to send requests to and receive status information from individual nodes in order to control the network configuration.
�SSCP takeover: See resource takeover.
�SSDU: See session-layer service data unit.
�SSF: See software support facility.
�SSFN: See session setup failure notification.
�SSI: (1) See subsystem interface.; (2) See single system image.; (3) See server-side include.; (4) See system status index.; (5) See Security Support Provider Interface.
�SSIB: See subsystem identification block.
�SSI-compliant custom server: A custom server that runs correctly in a single system image. The custom server complies with all the guidelines for the operation of custom servers in an SSI environment.
�SSID: See subsystem identifier.
�SSI-tolerant custom server: A custom server that runs in a single system image, but only with some restrictions.
�SSL: See Secure Sockets Layer.
�SSL authentication: Authentication in which the server exchanges the server certificate with the client and, optionally, the client exchanges the client certificate with the server. This exchange determines whether the client and server have a certificate in common and verifies the identities of the server and, optionally, the client.
�SSL channel: A type of channel within a transport chain that associates a Secure Sockets Layer (SSL) configuration repertoire with the transport chain.
�SSLight: An implementation of SSL, written in Java, and no longer supported by CICS Transaction Gateway.
�SSO: See single sign-on.
�SSOB: See subsystem options block.
�SSP: See System Support Program.
�SSR: (1) See software specification review.; (2) See service support representative.
�SST: See system service tools.
�stack: (1) An area in memory that typically stores information such as temporary register information, values of parameters, and return addresses of subroutines and is based on the principle of last in, first out (LIFO).; (2) An area of storage in which stack frames can be allocated.
�stacked icon: A Notes database icon that represents a database and all of its associated replicas that are currently added to the workspace.
�stacked product: A product that extends the tooling, functionality, or features of another product. For example, Rational Software Architect is a stacked product of Rational Application Developer.
�stacked status: In mainframe computing, the condition in which the control unit is in a holding status for the channel, and, the last time the control unit attempted to present the status, the channel responded with the stack-status control.
�stacked volume: A volume that has a one-to-one association with physical tape media and is used in a virtual tape server (VTS) to store logical volumes (LVOLs). Stacked volumes are not used by MVS applications but by the VTS and its associated utilities. They may be removed from a VTS to allow transportation of LVOLs to a vault or to another VTS. See also container.
�stack frame: (1) A section of the stack that contains the local variables, arguments, and register contents for an individual routine, as well as a pointer to the previous stack frame.; (2) See dynamic storage area.; (3) The physical representation of the activation of a routine. The stack frame is allocated and freed on a last-in, first-out basis.
�stack frame collapse: An action that occurs when the condition manager skips over one or more active routines and execution resumes in an earlier routine on the stack.
�stack segment: A contiguous area of storage obtained directly from the operating system. The Language Environment storage management scheme subdivides stack segments into individual dynamic storage areas (DSAs). If the initial stack segment becomes full, a second segment or increment is obtained from the operating system.
�stack storage: (1) An area of storage used for suballocation of stack frames. Such suballocations are allocated and freed on a LIFO (last-in, first-out) basis. A stack is a collection of one or more stack segments consisting of an initial stack segment and zero or more increments.; (2) See automatic storage.
�staff activity: An activity in a process that queries human interaction for decisions on how to proceed. A staff activity is used in a long-running process where the process will halt to await the outcome of the human interaction.
�stage: (1) An element of a DataStage job that describes a database or process. Stages are added to a job and linked together.; (2) A component that represents a data source, a processing step, or the data mart in a DataStage job.
�stage 1 system definition: The first part of the process of defining an IMS system. Stage 1 checks input specifications and generates a series of MVS job steps that are the input to stage 2.
�stage 2 system definition: The second part of the process of defining an IMS system. Stage 2 builds IMS system libraries, execution procedures, and the IMS online control program tailored to support the desired set of IMS functions. Stage 2 then stores these in an IMS library.
�staging: The process of returning return data or an object from an offline or low-priority device to an online or higher priority device, usually on demand of the system or on request of the user.
�staging area: (1) See resource manager cache.; (2) An area into which subsystem interface routines store data to be transferred between address spaces. Staging areas can be contained in the common service area (CSA) or in an address space used by auxiliary storage.
�staging data set: Data sets that are created by the system logger to safeguard log data when there is an error that leaves the only copy of log data in a volatile configuration.
�staging drive group: A collection of staging drives for space management and recovery.
�staging libraries: Those libraries that are modified by offline functions in a system using online change. Changes are first applied to the staging libraries, which are then copied to the inactive libraries.
�staging server: An instance of a WebSphere Commerce Server that is used for testing purposes before new functions or data are deployed to the production server. See also production server, authoring server, production-ready data.
�staging table: In SQL replication, a consistent-change-data table that is used to save data before that data is replicated to the target database. A consistent-change-data table used for staging data can function as an intermediate source for updating data in one or more target tables. See also consistent-change-data table, SQL replication.
�stakeholder: (1) A person or role that has interest in and influence on the system.; (2) An individual who is materially affected by the outcome of the system. See also customer.; (3) An individual or organization that is involved in or may be affected by project activities.
�stakeholder need: The business or operational problem that must be fulfilled in order to justify purchase or use.
�stakeholder request: A request of various specialized types for example, change request, enhancement request, request for a requirement change, defect from a stakeholder.
�stale copy status: A copy status that specifies that a volume copy is not available to the database or the recovery log.
�stale file handle: A file handle for a file or prefix that is no longer valid.
�stand-alone: (1) Independent of any other device, program, or system. In a network environment, a stand-alone machine accesses all required resources locally.; (2) Pertaining to a program that is capable of running separately from the DB2 database system, without using DB2 services.
�stand-alone client: The node in a one-node cluster.
�stand-alone dump: A printout of main storage requested separately from normal system operations, which does not require the system to be in a condition for normal operations.
�stand-alone optical drive: An optical drive housed outside of an optical library.
�stand-alone relationship: In FlashCopy and remote copy, relationships that do not belong to a consistency group and that have a null consistency-group attribute.
�stand-alone restore: A DFSMSdss program that runs independently of the z/OS system environment and provides a full or partial restoration from a dump tape.
�stand-alone server: A fully-operational server that is managed independently of all other servers, using its own administrative console.
�stand-alone system: (1) A system that runs application programs independently of another system. The exchange of data files or applications with another system is done manually, through portable media, such as diskette or tape.; (2) A DirectTalk system that is not part of a single system image (SSI). A stand-alone system is not connected to other DirectTalk systems, so it contains its own application and voice data.
�stand-alone task: A unit of work that exists independently of a business process, and implements human interaction as a service. See also human task, inline task.
�standard: An agreed-upon set of specifications for hardware or software.
�standard connector configuration properties: Configuration settings typically used by the connector controller to manage the connector (for example, to set the trace level, log file name, or polling information). These settings are generic for all connectors. See also connector configuration property, connector-specific configuration property.
�standard database: In high availability disaster recovery, a database that is neither the primary nor the standby. A standard database is not configured for high availability disaster recovery. See also high availability disaster recovery.
�standard data format: In COBOL, the format in which data is described as it appears when it is printed rather than how it is stored in the computer.
�standard DL/I application program: An application program that uses the existing DL/I call interface. It does not issue any CPI communications calls, nor does it allocate any LU 6.2 conversations.
�standard envelope: See EDI envelope.
�standard error (STDERR): The output stream to which error messages or diagnostic messages are sent. See also standard input, standard output.
�standard format dictionary: A dictionary where a match will only be found if exactly the same sequence of characters is found in a text as the dictionary entry.
�Standard Generalized Markup Language (SGML): A standard metalanguage for defining markup languages that is based on the ISO 8879 standard. SGML focuses on structuring information rather than presenting information; it separates the structure and content from the presentation. It also facilitates the interchange of documents across an electronic medium.
�standard input (STDIN): An input stream from which data is retrieved. Standard input is normally associated with the keyboard, but if redirection or piping is used, the standard input can be a file or the output from a command. See also standard error.
�standard label (SL): An IBM, ANSI, or ISO standard tape label.
�standard output (STDOUT): The output stream to which data is directed. Standard output is normally associated with the console, but if redirection or piping is used, the standard output can be a file or the input to a command. See also standard error.
�standard property: A configuration option shared by all instances of a particular WebSphere business integration component, such as all collaborations or all connectors. These properties differ from options that are unique to a particular component. See also property.
�standard set: A group of CD-ROMs that contains the i5/OS program, no-charge options, and no-charge licensed programs.
�standard system action: The name given to the language-defined default action taken when a condition occurs and it is not handled by a condition handler.
�standard volume: A volume that emulates one of several S/390 volume types, such as the 3390-2, 3390-3, 3390-9, 3390-2 (3380-track mode), or 3390-3 (3380-track mode). A standard volume presents the same number of cylinders and capacity to the host as the native S/390-volume type of the same name presents. See also custom volume.
�Standard Widget Toolkit (SWT): An Eclipse toolkit for Java developers that defines a common, portable, user interface API that uses the native widgets of the underlying operating system. See also Abstract Window Toolkit, Swing Set.
�standby database: In high availability disaster recovery, a copy of the primary database. Updates to this database occur by rolling forward log data that is generated on the primary database and sent to the standby database. See also high availability disaster recovery.
�stanza: (1) A group of lines in a file that together have a common function or define a part of the system. Stanzas are usually separated by blank lines or colons, and each stanza has a name.; (2) A section of a software package that defines either a specific action to be performed on that the software package or a set of conditions under which actions are to be performed on the software package. The complete software package is a stanza that contains a hierarchy of many different stanzas. See also file package.; (3) A grouping of options in a configuration file to control various aspects of compilation by default.
�star-connected communications network: A network in which all nodes are connected to a central node.
�star join: A method of joining a dimension column of a fact table to the key column of the corresponding dimension table. See also star schema, dimension table, fact table, join.
�star network: A local area network in which all nodes are connected in a star-like configuration to a central computer. Each node exchanges data directly with the central node.
�star schema: (1) A type of relational database schema that is composed of a set of tables comprising a single, central fact table surrounded by dimension tables. See also dimension table, star join.; (2) A type of relational database schema that is made up of a fact table and a set of dimension tables. In Tivoli Enterprise Data Warehouse, the fact table holds the values of the component's metrics, and the dimension tables hold the values of the attributes of a component or a metric.
�start-control-program-function job (SCPF job): A job used during a portion of the initial program load process that starts the operating system.
�start data traffic (SDT): In SNA, a command issued by the primary logical unit, which allows user data to be sent on the logical unit-to-logical unit (LU-to-LU) session.
�started procedures table: A function that provides a method for assigning RACF identities to started procedures
�started task: In MVS, a process that begins at system start and runs unattended. Started tasks are generally used for critical applications. The UNIX equivalent of a started task is a daemon.
�started transaction: A CICS transaction initiated by a terminal user can start other transactions by means of a CICS START command. A transaction started in this way is known as a started transaction.
�starter set: In the OSI Communications Subsystem licensed program, the subset of the programming interface that can be used by customer programs that use simplified data communications.
�starter store: A fully functional online store, provided in store archive format with WebSphere Commerce. Starter stores are designed to be used as a base on which an online store can be created.
�starter store archive: A store archive for the WebSphere Commerce starter store.
�start node: A node that identifies where a process begins.
�start-of-authority record (SOA record): In the Domain Name System (DNS), the resource record that defines a zone.
�start-of-day processing: Processing performed by the scheduler agent at the beginning of each day to do such things as initialize the clearing channels for the day and archive payments.
�start-of-header character (SOH character): In binary synchronous communications, the transmission control character indicating that the information that follows is a header.
�start-of-text character (STX character): In binary synchronous communications, a transmission control character used to begin a logical set of records that will be ended by the end-of-text character or end-of-transmission-block character.
�start-stop (SS): Pertaining to asynchronous communications line control that uses start signals and stop signals to control the transfer of data over a communications line. Each group of signals representing a character is preceded by a start signal and followed by a stop signal. See also asynchronous communication.
�start time: The time when a channel starts a settlement.
�start-to-finish: A dependency type between two project elements where the predecessor element must start before the successor element can finish.
�start-to-start: A dependency type between two project elements where the predecessor element must start before the successor element can start.
�start Uniform Resource Locator (start URL): The starting point for a crawl.
�startup: The operation of starting up CICS by the system operator.
�startup job stream: A set of job control statements used to initialize CICS.
�startup procedure: A procedure used to start an application and to specify initialization parameters and libraries containing system resources.
�start URL: See start Uniform Resource Locator.
�state: (1) The attribute of a program that determines the domain of objects that it can access directly.; (2) One step in the logical sequence of actions that comprises a WebSphere Voice Response application.; (3) A stage in the life cycle of an object that identifies the status of that object.; (4) An object's characteristic that is manifested in its public and private data members, and can be divided into two categories: essential state and non-essential state.; (5) The situation of a conversation from the point of view of one of the participating transactions. The conversation state determines the commands (if any) that a transaction can validly issue. The state of each transaction changes dynamically in the course of a conversation. See also state variable.; (6) A condition or situation during the life of an object during which it satisfies some condition, performs some activity, or waits for some event. See also vertex.; (7) An indication associated with an icon, color, and severity level assigned to a situation at a point in time. A situation can reflect one of the following states: critical, warning, or informational.; (8) In a business state machine, one of several discrete individual stages that are organized in sequence to compose a business transaction.
�State Adaptive Choreography Language (SACL): An XML notation that is used to define state machines.
�state change: (1) In the OSI Communications Subsystem licensed program, a change in the status of an application entity or association--for example, an application entity changing from activated to deactivated.; (2) In the OSI Communications Subsystem licensed program, an event that indicates that a resource--such as a line--has had a change in status. State change events are logged and generate a message to the operator.
�state chart diagram: See state machine diagram.
�state data: IMS state data is information that needs to be kept in RM, so that a user can sign onto another IMS and resume his state. See also significant data.
�stateful: Of or pertaining to a system or process that keeps track of the state of interaction. See also stateless.
�stateful session bean: A session bean that acts on behalf of a single client and maintains client-specific session information (called conversational state) across multiple method calls and transactions. See also stateless session bean, session bean.
�stateless: Having no record of previous interactions. A stateless server processes requests based solely on information provided with the request itself, and not based on memory from earlier requests. See also stateful.
�stateless session bean: (1) A session bean with no conversational state. All instances of a stateless bean are identical. (Sun) See also session bean, stateful session bean.; (2) A session bean that is a collection of operations. The server can optimize resources by reusing bean instances on every method call.
�state machine: A behavior that specifies the sequences of states that an object or an interaction goes through during its life in response to events, together with its responses and actions.
�state machine diagram: A UML behavioral diagram that models the dynamic behavior of individual class objects, use cases, and entire systems. There are two types of state machines: behavioral and protocol.
�statement: (1) An instruction in a program or procedure.; (2) In programming languages, a language construct that represents a step in a sequence of actions or a set of declarations.
�statement cache: The portion of the package cache related to dynamic SQL statements. See also package cache.
�statement handle: The data object that contains information about an SQL statement or XQuery expression that is managed by the DB2 call level interface. Such information includes dynamic arguments, bindings for dynamic arguments and columns, cursor information, result values, and status information. Each statement handle is associated with a connection handle. See also connection handle.
�statement optimization guideline: An optimization guideline that applies to a single DML statement. See also optimization guideline.
�statement string: The character string form of a dynamic SQL statement.
�statement trigger: A trigger that is defined with the trigger granularity FOR EACH STATEMENT.
�state table: A list of all the actions used in a particular voice application. A component of DirectTalk.
�state table action: One instruction in a set of instructions contained in a DirectTalk state table that controls how DirectTalk processes various operations such as playing voice prompts or recording voice messages.
�state transition: The change from one state to another.
�state transition diagram: See state machine diagram.
�state transition model: The sequence of states that a change request goes through from submission through disposition. This model specifies the actions that a user can take to move a change request from one state to another.
�state variable: A program can obtain values that indicate the conversation state. CICS places such values in a variable named by the program, known as the state variable. See also state.
�static: (1) Pertaining to an operation that occurs at a predetermined or fixed time. See also dynamic.; (2) A Java programming language keyword that is used to define a variable as a class variable.
�statically known namespaces: In XQuery, a set of prefix and URI pairs that defines all of the namespaces that are known during static processing of an expression. Statically known namespaces are a component of the static context of an expression.
�static analysis: The process of extracting targeted types of information on the models in their static form. This differs from dynamic analysis, which extracts information based on the results of process simulations.
�static artifact: An artifact that is used, but not changed, by a process. See also input.
�static bind: A process by which SQL statements are bound after they are precompiled. All static SQL statements are prepared for execution at the same time. See also dynamic bind, incremental bind, automatic bind.
�static binding: The act of resolving references to external variables and functions before run time.
�static call: A type of call in which the program is link-edited into the same load module as the calling program. See also dynamic call.
�static classification: A semantic variation of generalization in which an object cannot change its type or role. See also dynamic classification.
�static cluster: A backup cluster that is defined statically to handle requests if the primary cluster fails.
�static compression: A data compression algorithm that uses tables that are currently not being updated, while continuing to substitute compression codes for source data.
�static connection: A connection between two nodes created by either a JES2 initialization or an operator command.
�static context: The information that is available during compilation of an XQuery expression before the expression is evaluated. See also dynamic context, expression context.
�static cursor: A named control structure that does not change the size of the result table or the order of its rows after an application opens the cursor. See also cursor, dynamic cursor.
�static data: (1) Data that is stored in static storage. See also automatic data.; (2) Data that retains its last-used state across calls.
�static file set: A file set that is manually assigned to a specific metadata server by the administrator.
�static information: Web content that does not change every time a Web page is accessed.
�static IP address: A fixed IP address for a persistent device or logical unit on a network that uses the IP standard. See also IP address.
�static kit: An unmodifiable group of products that are ordered as a unit. See also bundle, stock keeping unit.
�static library: A library linked with other modules when those modules are built.
�static linking: The incorporation of procedures and data into a load module at build time, instead of dynamically loading them at run time. Compared to dynamic linking, static linking increases the size of the executable file. See also dynamic linking.
�static method: See class method.
�static mode: An operating mode of node DniConfigProvider, in which this node inserts environment data and values of its properties in the incoming message. This mode is enabled, if the 'DSN of Configuration DB' property is empty.
�static NAT: See static network address translation.
�static network address translation (static NAT): A one-to-one mapping of IP addresses that allows a user to map an IP address on an internal network to an IP address that is to be made public. If static NAT is used, traffic can initiate from either side of the connection. See also network address translation.
�static node: A VTAM node defined by the IMS system definition.
�static node group: A node group consisting of nodes specified by the user.
�static organizational role: An organizational role that is manually assigned to a person.
�static partition: (1) A view-only scalable partition.; (2) In CICS/VSE, a partition, defined at IPL time and occupying a defined amount of virtual storage that remains constant. See also dynamic partition.
�static procedure call: A high-level language (HLL) call statement that specifies the name of an Integrated Language Environment (ILE) procedure to be called. See also procedure pointer call.
�static program call: A connection among programs during binding (program creation time). See also dynamic program call.
�static ranking: A type of ranking in which factors about the documents that are being ranked, such as date, the number of links that point to the document, and so on, augment the rank. See also dynamic ranking, text-based scoring, ranking.
�static route: A route between hosts, between networks, or between a host and a network, that is entered into a routing table.
�static SQL: SQL statements that are embedded within a program and are bound before the program is executed. After being bound, a static SQL statement does not change, although values of host variables specified by the statement can change. See also deferred embedded SQL, dynamic SQL, incremental bind statement.
�static storage: An area that is allocated by the system when a program is activated. Static storage exists as long as the program activation exists. If the program has not been deactivated, the values in the storage persist from one call to another. See also automatic storage, dynamic storage.
�static summarization: A type of summarization in which the search results contain a specified, stored summary from the document. See also dynamic summarization, summarization.
�static terminal: A terminal created through the system definition process. See also dynamic terminal.
�static text: Text that remains constant on every document created with a particular form, as opposed to fields in which the user types or in which Notes calculates information.
�static transaction routing: Non-dynamic terminal-initiated transaction routing. The transaction routing request is routed to a predetermined system. Static transaction routing occurs when DYNAMIC(NO) is specified in the transaction definition and the request is routed to the system named in the REMOTESYSTEM attribute.
�static user: Non-ISC user or ISC user defined statically through the IMS system definition process.
�static Web page: A Web page that can be displayed without the additional client- or server-side processing that would be required for JavaServer Pages, servlets, or scripts.
�static Web project: A project that contains resources for a Web application with no dynamic content such as servlets or JavaServer Pages (JSP) files, or Java code. A static Web project can be deployed to a static HTTP server and does not require additional application server support.
�station: A computer or device that can send or receive data.
�station address: A 2-character hexadecimal value from 01 to FE. For a primary controller, it is called the SDLC station address; for a secondary controller, it is called the remote system address.
�station ID: For the IBM 3800 Printing Subsystem, a 2-byte pipeline counter that is incremented when the last copy of a page reaches the point in the hardware represented by that counter.
�station protector: A device attached to the system cable to protect work stations attached in different buildings from lightning.
�statistical event: In OSI, an event counted for a specific purpose. Statistical events are logged but do not generate a message to the operator.
�statistical view: A view for collecting statistics that the query optimizer uses to obtain the most appropriate access plan.
�statistics data area (SDA): A control block that contains processing information. The SDA consists of a header and function-dependent extensions.
�statistics domain: Major component of CICS that controls the collection of resource statistics for a CICS system. It collects data at user-specified intervals, at shutdown and logical end-of-day, and when requested by the user.
�statistics profile: A file that contains all of the option information that specifies which statistics are collected for a table when using a particular RUNSTATS command.
�statistics utility program (DFHSTUP STUP): CICS program that provides offline formatting of the CICS statistics written to the SMF data set (CICS Transaction Server) or the DFHSTM statistics data set (CICS/VSE). DFHSTUP can format all types of statistics generated by CICS and provides a summary function to collect all statistics produced in a given period. See also summary report.
�status: (1) The current condition or state of a program or device, for example, the status of a printer.; (2) The true or false condition of a situation.
�status area: A part of a window that displays information indicating the state of the current view of an object.
�status bar: In System i Access, the part of a window that displays information indicating the current state of that window's content.
�status code: A two-character code in the program communication block (PCB) mask that indicates the results of a DL/I call. See also PCB mask.
�status line: A line at the top of a display that contains information about a document and current operations, including an audit window, the document name, and page and line number.
�status monitor: A monitor that collects and summarizes information on the status of resources that are defined in a VTAM domain.
�status recovery mode: The scope of recovery for a resource, it determines where the resource status can be recovered from. GLOBAL indicates the status is managed by RM, LOCAL indicates the status is managed by IMS in local control blocks and log records, and NONE indicates the status is not recovered.
�STDERR: See standard error.
�STDIN: See standard input.
�STDOUT: See standard output.
�stem: (1) In REXX, that part of a compound symbol up to and including the first period. It contains just one period, which is the last character. It cannot start with a digit or a period. A reference to a stem can also be used to manipulate all variables sharing that stem.; (2) The root of an inflected or derived word form that is obtained by stripping off inflectional or derivational affixes, for example: 'polit' is the stem of 'political'. A stem does not have to be a valid word. See also lemma.
�stemming: See word stemming.
�step: (1) A part of an XQuery path expression that generates a sequence of items and then filters the sequence by zero or more predicates. The value of the step consists of those items that satisfy the predicates. See also node test, path expression.; (2) To cause a computer to run one operation.
�step allocation: The system function that establishes a logical connection between a running program and a data set, device, or volume in preparation for running the program. See also dynamic allocation.
�step restart: A restart that occurs at the beginning of a job step. There are two types of step restart: automatic or deferred. See also checkpoint restart.
�step-up authentication: A protected object policy (POP) that relies on a preconfigured hierarchy of authentication levels and enforces a specific level of authentication according to the policy set on a resource. The step-up authentication POP does not force the user to authenticate using multiple levels of authentication to access any given resource, but it requires the user to authenticate at a level at least as high as that required by the policy protecting a resource.
�stereotype: A meta-classification of an element. Stereotypes have semantic implications which can be specified for every specific stereotype value.
�steward: A user or group that has responsibility for one or more metadata objects in the metadata repository. A steward is typically assigned to the objects that the user or group is responsible for managing or is the appropriate contact for.
�STI: See self-timed interface.
�sticky bit: A type of access permission bit that causes an executable program to remain on the swap area of the disk. Only someone with root authority can set the sticky bit. This bit is also used on directories to indicate that only file owners can link or unlink files in that directory.
�sticky key: An input method that enables the user to press and release a series of keys sequentially (for example, Ctrl+Alt+Del), yet have the keys behave as if they were pressed and released at the same time. This method can be used for those who require special-needs settings to make the keyboard easier to use.
�sticky pool: The part of the page pool that is made available to cache the first block of frequently used interactive files. Sticky pool size is one of the file manager startup configuration parameters.
�still frame: See information frame.
�S/T interface: In Performance Tools, the interface at the S and T reference points defined in the reference model of the integrated services digital network (ISDN). When there is no network termination 2 (NT2), the S and T reference points become one S/T point.
�STI policy: See Synthetic Transaction Investigator playback policy.
�STM: See sense type and model.
�stock keeping unit (SKU): An alphanumeric identifier for each item of merchandise, or catalog entry. The smallest unit available for keeping inventory control. It can include variables for department, class, vendor, style, color, size, and location. See also package.
�STOKEN: See space token.
�stop: To end, in a controlled manner, the current processing activity in a computer system.
�stop node: A node that marks the end of a process. When a flow reaches a stop node while the process is running, the process immediately terminates, even if there are other currently executing flows within the process.
�stopped state: A state that allows a device to be made unavailable although it is still known by the device driver, which remains loaded and bound in the kernel.
�stop-the-world time: The duration of a full garbage collection where processing stops during the collection time.
�stop word: (1) A word that is commonly used, such as "the," "an," or "and," that is ignored by a search application.; (2) A frequently occurring word that many natural language processing (NLP) applications identify as such, to improve processing.
�stop word removal: The process of removing stop words from the query to ignore common words and return more relevant results.
�storage: (1) A functional unit into which data can be placed, in which it can be retained, and from which it can be retrieved. See also virtual storage.; (2) The location of saved information.
�storage accounting area (SAA): A field at the start of a CICS storage area that describes the area and enables CICS to detect some storage violations. Each CICS storage area has either an SAA or a storage check zone.
�storage administration group: A centralized group within the data processing center that is responsible for managing the storage resources within an installation. See also system operator, user group.
�storage administrator: A person in the data processing center who is responsible for defining, implementing, and maintaining storage management policies. See also system operator.
�storage area network (SAN): A dedicated storage network tailored to a specific environment, combining servers, systems, storage products, networking products, software, and services.
�storage check zone: A pair of fields at the beginning and end of a CICS storage area that enable CICS to detect some storage violations. Each CICS storage area has either a storage check zone or a storage accounting area (SSA).
�storage class: (1) The type of media that an object is stored on. It is not directly associated with a physical location; however, it is directly associated with the device manager. See also storage group, storage system.; (2) In WebSphere MQ for z/OS, the page set that is to hold the messages for a particular queue. The storage class is specified when the queue is defined.; (3) A named list of data-set storage attributes that identify performance goals and availability requirements. A storage class is defined by the storage administrator to select a device that can meet those goals and requirements.
�storage class specifier: A storage class keyword that determines storage duration, scope, and linkage.
�storage client network: A classic, interconnected, fibre-channel fabric with a single, fibre-channel, fabric name.
�storage complex: Multiple storage facilities.
�storage construct: Any of the predefined models (data class, management class, storage class, and storage group) that are used to classify storage management needs and procedures for data sets under the storage management subsystem (SMS). Each data set has construct names associated with it, by explicit specification or by default. See also data class.
�storage control: (1) In CICS, a facility that controls requests for main storage to provide intermediate work areas not automatically provided by CICS.; (2) The component in a storage subsystem that handles interaction between processor channel and storage devices, runs channel commands, and controls storage devices. Storage control is an example of a control unit.
�storage controller: A device, such as a Redundant Array of Independent Disks (RAID) controller, that creates and manages other storage devices.
�storage cushion: A noncontiguous area of storage in the dynamic storage areas reserved for use by CICS when processing a short-on-storage condition. See also short-on-storage.
�storage device: (1) A physical unit that provides a mechanism to store data on a given medium so that it can be subsequently retrieved.; (2) A logical unit number (LUN) that terminates a collection of ports on the storage network.
�storage device subsystem: A part of the computer consisting of the controller and one or more attached storage devices.
�storage director: A physical or logical element that manages multiple paths to storage components, such as devices or controllers. See also storage path.
�storage facility: A physical unit that consists of a storage server integrated with one or more storage devices to provide storage capability to a host computer.
�storage group: (1) A named set of disks on which DB2 for z/OS data can be stored.; (2) A group that associates a storage system to a storage class. See also storage class, storage system.; (3) A collection of storage volumes and attributes that are defined by the storage management subsystem (SMS) administrator to meet a defined service strategy. The collections can be a group of direct access storage device (DASD) volumes; tape volumes; or a group of DASD, optical, or tape volumes treated as a single, object-storage hierarchy. See also tape storage group, virtual input/output storage group, object backup-storage group, object storage group, pool storage group.
�storage group category: A grouping of specific storage groups that contain the same type of data. This concept is analogous to storage pools in an environment that is not system-managed.
�storage heap: An unordered group of program stack areas that may be associated with programs running within a process.
�storage hierarchy: (1) The logical ordering of primary storage pools, based on the speed and capacity of the devices that the storage pools use, as defined by the appropriate administrator.; (2) An arrangement of storage devices with different speeds and capacities. The levels of the storage hierarchy include: main storage, such as memory and direct access storage device (DASD) cache; primary storage (DASD containing user-accessible data); migration level 1 (DASD containing data in a space-saving format); and migration level 2 (tape cartridges containing data in a space-saving format). See also hierarchical storage management, migration level 1, migration level 2, object storage hierarchy, primary storage.
�storage key: A key associated with each 4KB block of storage that is available in the CICS region. Access to CICS storage is controlled by key-controlled storage protection. When key-controlled protection applies to a storage access, a store operation (write) is permitted only when the storage key matches the access key associated with the request; a fetch (read) is permitted when the keys match or when the fetch-protection bit of the storage key is zero. In most cases, the access key for a storage operation is the PSW key in the current PSW.
�storage location: (1) In Backup, Recovery, and Media Services, a place where media and containers can be stored awaiting expiration or movement to another location such as off-site storage, vaults, or long-term (permanent) retention. Backup, Recovery, and Media Services has two predefined locations that can be overridden by the user: 1) *HOME, the system keyword for the on-site library (or home location); and 2) VAULT, a default storage location that refers to the default off-site storage location.; (2) Data elements within a storage system that can be mapped to (a) the schema of the storage system, such as a column in a database table, (b) an aggregation of data, such as a table, or (c) a way of accessing the data, such as a transaction identifier. See also storage system, user key.; (3) A location physically separate from the removable media library where volumes are stored for disaster recovery, backup, and vital records management. See also inventory management.
�storage location dominance: A priority scheme used to decide where in the hierarchy of physical storage locations a specific volume or logical unit number (LUN) should be located.
�storage-location management processing: In DFSMSrmm, the process of inventory management that assigns a shelf location to each volume that has moved as a result of vital record processing. See also vital record processing, inventory management.
�storage management: The activities of data set allocation, placement, monitoring, migration, backup, recall, recovery, and deletion. Storage management can be performed either manually or using automated processes. The storage management subsystem (SMS) automates these processes while optimizing storage resources. See also storage management subsystem.
�storage management cycle: An invocation of the OAM Storage Management Component (OSMC). The purpose of the storage management cycle is to ensure that every object scheduled for processing is placed in the correct level of the object storage hierarchy (as specified by its storage class), has expired or is backed up (as specified by its management class or by an explicit application request), and, if necessary, is flagged for action during a subsequent storage management cycle.
�Storage Management Initiative Specification (SMI-S): A design specification developed by the Storage Networking Industry Association (SNIA) that specifies a secure and reliable interface with which storage management systems (SMSs) can identify, classify, monitor, and control physical and logical resources in a storage area network (SAN). The interface integrates the various devices to be managed in a storage area network (SAN) and the tools used to manage them.
�storage management recovery: A function that prepares the system to access data from all disk units configured to the system.
�storage management station: A system that is used to manage the storage subsystem. A storage management station does not need to be attached to the storage subsystem through the fibre-channel I/O path.
�storage management subsystem (SMS): Software that automates as much as possible the management of physical storage by centralizing control, automating tasks, and providing interactive controls for system administrators. See also storage management.
�storage manager domain: Major component of CICS which manages virtual storage requests.
�storage model: A creation attribute for modules, programs, and service programs that describes the type of storage supplied by the system at run time for automatic, static, and constant storage. The system-recognized identifiers for storage model are *SNGLVL (single-level store), *TERASPACE (teraspace), and *INHERIT (inherit). *INHERIT, which is specified only for modules and service programs, indicates that the object must be created such that it will run when either single-level store or teraspace is supplied.
�storage network: An arrangement that provides shared access to a set of logical unit numbers (LUNs) across one - n storage client networks.
�Storage Networking Industry Association (SNIA): An alliance of computer vendors and universities that focus on developing and promoting industry standards for storage networks.
�storage path: The hardware within storage control that transfers data between the direct access storage device (DASD) and a channel. See also storage director.
�storage pool: (1) A logical division of storage reserved for processing a job or group of jobs.; (2) A named set of storage volumes that is the destination that is used to store client data. See also archive, retrieve.; (3) A grouping of storage space consisting of volumes, logical unit numbers (LUNs), or addresses that share a common set of administrative characteristics. See also user pool.
�storage port: An engine's connection point to a storage client network. A storage port is a member of a single fabric. See also engine.
�storage protection: An optional facility in CICS Transaction Server 3.3 that enables users to protect CICS code and control blocks from being overwritten inadvertently by application programs. See also transaction isolation.
�storage protection key: (1) An indicator that appears in the current program status word whenever an associated task has control of the system. This indicator must match the storage keys of all main storage blocks that the task is to use.; (2) A hardware key associated with each page of virtual memory that is available in POWER6 processors and is supported as of AIX Version 5.3 with the 5300-06 Technology Level. Access to pages is controlled on a per-thread basis depending on the access mode of the running thread as represented in the authority mask register (AMR). See also authority mask register.
�storage server: A physical unit that manages attached storage devices and provides access to the storage or storage related functions for one or more attached hosts.
�storage subsystem: A storage control and its attached storage devices. See also tape subsystem.
�storage system: (1) A generic term for storage in the Content Manager system. See also media archiver, storage class, storage group.; (2) Any system in a network that persistently stores data that has been collected for future use or that acts as a gateway to such data. See also storage location.
�storage template: A model that describes a set of storage requirements and configurations.
�storage unit: Hardware that contains one or more drive bays, power supplies, and a network interface. Some storage units contain Redundant Array of Independent Disks (RAID) controllers; in this case, the storage unit is accessed by the appliance.
�storage violation: An error in a storage accounting chain in the dynamic storage area. A storage violation can be detected by the storage manager domain in CICS Transaction Server or the storage manager program in CICS/VSE.
�storage violation dump: A formatted memory dump created as a result of a storage error detected by the storage control program, including a dump of the dynamic storage error.
�store: (1) To place and retain data in a storage device, so that it is available for retrieval and updating.; (2) In WebSphere Commerce, the place where all transactions for an online business occur. Store types include customer-facing store, asset store, and proxy store.
�store and forward: The temporary storing of packets, messages, or frames in a data network before they are retransmitted toward their destination.
�store archive (SAR): A compressed file that contains all the assets (including file assets and database information) necessary to create a store. Publishing the store archive to a WebSphere Commerce Server creates an operational store. See also SAR file format, composite store archive.
�store controller: See retail controller.
�stored descriptor definition: The information from which IMS builds a runtime descriptor definition. See also runtime descriptor definition.
�stored procedure: (1) A block of procedural constructs and embedded SQL statements that is stored in a database and that can be called by name. Stored procedures allow an application program to be run in two parts, one on the client and the other on the server, so that one call can produce several accesses to the database.; (2) See procedure.
�stored record: A data record, together with its control information, as stored in auxiliary storage.
�stored resource definition: The resource information that is stored offline, from which IMS builds runtime resource definitions. Stored resource definitions can reside in system data sets, such as IMS.MODBLKS, IMS.ACBLIB, IMS.FORMAT, and a resource definition data set (RDDS). See also resource definition data set.
�store entity: An abstract super class that can represent either a store or a store group.
�storefront asset: Any part of an online store that customers see while shopping. Storefront assets include HTML pages, JSP files, style sheets, images, graphics, and other multimedia file types. See also back-office business logic.
�storefront asset store: A type of asset store that is a collection of JSP files, commands, business processes (for example, order processing), business policies and access control policies that create a virtual storefront. See also asset store, catalog asset store.
�store owner: In WebSphere Commerce, the position that controls and owns the database and the file assets related to the online store. A store owner can be an organization.
�store-through caching: A process in which changed data is written to the cache structure and to permanent storage simultaneously and under the same serialization; as a result, the data in the cache structure always matches the data in permanent storage
�strategy: The overall plan of action (for a brand unit, business unit, channel, company, etc.) to achieve a stated goal. Strategies normally cover a period of more than one year.
�stream: (1) A continuous sequence of data elements being transmitted one character at a time, or intended for transmission, using a defined format.; (2) In the CVS team programming environment, a shared copy of application resources that is updated by development team members as they make changes. The stream represents the current state of the project.; (3) A method of topic partitioning that is used by applications that connect to MQSeries Publish/Subscribe SupportPac brokers.; (4) An object that specifies configuration rules for a UCM view.; (5) A file access object that allows access to an ordered sequence of characters, as described by the ISO C standard. Such objects can be created by the fdopen() or fopen() functions, and are associated with a file descriptor. A stream provides the additional services of user-selectable buffering and formatted input and output.
�stream buffer: In C++, an area of storage between the ultimate consumer and the I/O Stream Library functions that format data.
�stream data file: Data sets with a byte-oriented structure, which are accessed as continuous streams of data bytes. This structure is common in workstation environments. See also record-oriented file.
�stream decryption: A symmetric algorithm that decrypts data one bit or byte of data at a time.
�streamed data: Any data sent over a network connection at a specified rate. A stream can be one data type or a combination of types. Data rates, which are expressed in bits per second, vary for different types of streams and networks.
�stream editor: A type of editor that is used to perform basic transformations on text read from a file or a pipe. The results are sent to a standard output.
�stream encryption: A symmetric algorithm that encrypts data one bit or byte of data at a time.
�stream file: (1) A file that contains continuous streams of bits such as PC files, documents, and other data stored in System i folders.; (2) A file containing a continuous stream of data. Stream files are well suited for storing strings of data such as the text of a document, images, audio, and video. The content and format of stream files are managed by the application rather than by the system.
�streaming: (1) A method of writing and reading data on magnetic tape as continuous fields without record boundaries.; (2) In object-oriented programming, the serialization of class information and object instance data.
�streaming client: A Sametime client that can receive streaming data from the Streaming Gateway but that has no interactive capabilities. These clients provide a user attending a meeting with an experience similar to watching television: users can watch but cannot interact.
�streaming gateway: A Sametime server component responsible for broadcasting audio, video, and data streams to receive-only clients. Communication from the streaming gateway is one-way (from the server to the client). The streaming gateway scales to a large audience but does not support interactive clients.
�streaming gateway controller: In Sametime, the component that tells the streaming gateway when to join a meeting, ensures that streaming clients can connect to the streaming gateway, and terminates the meeting on the streaming gateway.
�stream mode: (1) A method of sending and receiving data in which records are defined as a stream of data without boundaries.; (2) In MFS, the input mode in which fields are defined as a stream of data without record boundaries. See also input mode, record mode.
�stress: A shortage of free space in the DSA or EDSA, such that CICS cannot recover from virtual storage depletion.
�strikeover: A character entered in a space currently occupied by another character.
�string: (1) In programming languages, the form of data used for storing and manipulating text.; (2) A group of auxiliary storage devices connected in a series on the system. The order and location in which each device is connected to the system determines the physical address of the device.; (3) A sequence of elements of the same nature, such as characters considered as a whole. For example, character string, binary string, and hexadecimal string.; (4) A sequence of bytes that might represent characters.; (5) A contiguous sequence of bytes terminated by and including the first null byte.
�string concatenation: In REXX, an operation that joins two characters or strings in the order specified, forming one string whose length is equal to the sum of the lengths of the two characters or strings.
�string constant: Zero or more characters enclosed in double quotation marks. See also string literal.
�string control byte (SCB): In MTAM and RJE, a control character in the SNA character string that identifies how user data is compressed.
�string delimiter: A symbol that is used to enclose an SQL string constant. The SQL string delimiter is the apostrophe (') except in COBOL applications, where the user assigns either a quotation mark (") or an apostrophe (').
�string literal: Zero or more characters enclosed in double quotation marks. See also string constant.
�stripe: (1) The portion of a striped data set (for example, an extended sequential data set) that resides on one disk. The records in that portion are not necessarily logically consecutive. The system distributes records among the stripes such that the disks can be read or written simultaneously to gain better performance.; (2) The set of tracks located on the set of physical disk drives configured in a Redundant Array of Independent Disks (RAID) logical unit (LU) that have the same parity track. See also striped data set.
�striped data set: An extended-format data set that occupies multiple volumes. A striped data set is a software implementation of sequential data striping. See also striping, stripe, extended format.
�stripe group: (1) A collection of disks that are grouped together for serving media streams. The multimedia file system uses stripe groups to optimize delivery of multimedia assets.; (2) The set of disks comprising the storage assigned to a file system.
�stripe width: The size of the block that data is split into for striping.
�striping: (1) A data mapping technique for disk arrays in which fixed-length sequences of virtual-disk data addresses are mapped to sequences of member disk addresses in a regular rotating pattern. See also striped data set.; (2) A storage process in which information is split into blocks (a fixed amount of data) and the blocks are written to or read from a series of disks in parallel.
�strong export: An export that allows only one definition of an external symbol to be used by the binder. The first definition in the binder search is chosen, and duplicate definitions are discarded. The binder always chooses a strong export over a weak export for the same symbol. See also weak export.
�strong typing: A process that guarantees that only user-defined functions and operations that are defined on a distinct type can be applied to that type. For example, two currency types, such as Canadian dollars and U.S. dollars, cannot be directly compared, but a user-defined function can be provided to convert one currency to the other and then do the comparison.
�struct: (1) An aggregate of elements having arbitrary types.; (2) See structure.
�struct tag: See structure tag.
�structural feature: A static feature of a model element, such as an attribute.
�structural model aspect: A model aspect that emphasizes the structure of the objects in a system, including their types, classes, relationships, attributes, and operations.
�structure: (1) A class data type that contains an ordered group of data objects. Unlike an array, the data objects within a structure can have varied data types.; (2) A name that refers collectively to different types of DB2 objects, such as tables, databases, views, indexes, and table spaces.; (3) A series of elements that have been graded or ranked in some useful manner. In Business Integration Modeler, a graphical representation of the relationships between different real entities in an organization.; (4) A construct used to map and manage storage on a coupling facility.
�structure attributes: In OSI, keywords and syntax that tell the Abstract Syntax Checker how to build the data structures.
�Structured Call Interface (SCI): A CSL component that manages communications between the IMSplex members.
�structured content: Content that has a structured format, such as specific fields. Structured content is created by using JSP or XML templates.
�structured data: Data that resides in fixed fields within a record or file. Relational databases and spreadsheets are examples of structured data.
�structured field: (1) A self-identifying string of bytes and its data or parameters.; (2) Output from the DFSMSrmm application programming interface (API) consisting of a structured field introducer (SFI) and output data.
�structured field introducer: The first 8 bytes of a structured field that indicate its length, type, and number.
�Structured Query Language (SQL): A standardized language for defining and manipulating data in a relational database. See also Data Manipulation Language.
�Structured Query Language/Data System (SQL/DS): An IBM relational database management facility used for processing SQL or DB2 databases.
�Structured Query Language for Java (SQLJ): A standard for embedding SQL in Java programs, defining and calling Java procedures and user-defined functions, and using database structured types in Java.
�structured type: (1) In OSI, an ASN.1 type defined by reference to one or more other ASN.1 types.; (2) A data type that is a named collection of attributes (standard data types or other structured types). A structured type allows for greater semantic control than a predefined type allows. See also method.
�structured viewing: The tabular aspect of the Design view of the XML editor that separates the structural constituents of an XML document, such as elements and attribute types, from values, such as attribute values and textual content.
�structure item: In EGL, a field in a structure or record. Each structure item is substructured (as a word is substructured into letters) or is not divisible (as a letter is not divisible).
�Structure of Management Information (SMI): In the Simple Network Management Protocol (SNMP), the rules used to define the objects that can be accessed by means of a network management protocol.
�structure owner: In relation to group buffer pools, the DB2 member that is responsible for the following activities: coordinating rebuild, checkpoint, and damage assessment processing; and monitoring the group buffer pool threshold and notifying castout owners when the threshold has been reached
�structure pair: A primary queue structure and its associated overflow structure.
�structure recovery data set (SRDS): Shared data sets that contain structure checkpoint information for shared queues on a structure pair. There are two SRDS data sets per structure pair.
�Structure Rule Table (SRT): A recurring attribute of the directory schema containing the permitted structures of distinguished names.
�structure tag: The identifier that names a structure data type.
�Struts: An open source framework designed to help developers create Web applications that keep database code, page design code, and control flow code separated from each other.
�Struts action: A class that implements a portion of a Web application and returns a forward. The superclass for a Struts action is called the Action class.
�Struts module: A Struts configuration file and a set of corresponding actions, form beans, and Web pages. A Struts application comprises at least one Struts module.
�Struts project: A dynamic Web project with Struts support added.
�STS: See source temporary store.
�STSN: See set and test sequence number.
�STSN Handler: A user-provided part of a FEPI application that handles STSN requests.
�stub: (1) A program module that transfers remote procedure calls (RPCs) and responses between a client and a server. Stubs perform marshalling, unmarshalling, and data format conversion. Both clients and servers have stubs. The Network Interface Definition Language (NIDL) compiler generates client and server stub code from an interface definition.; (2) A small module, link-edited into application code, that locates and transfers control to a larger body of related code.; (3) The two types of Remote Procedure Calls (RPCs) that are produced by the compiler when an interface is defined. The application code calls the stub, and the RPC mechanism translates this into a call to the appropriate function on the remote machine.; (4) A line in a state table that is only partially displayed.; (5) A small program routine that substitutes for a longer, possibly remote, program. For example, a stub might be a program module that transfers procedure calls (RPCs) and responses between a client and a server. In Web services, a stub is an implementation of a Java interface generated from a Web Services Definition Language (WSDL) document.; (6) A replica or Notes database copy that has not yet been filled with documents. The database is no longer a stub after the first replication takes place.; (7) A component containing functionality for testing purposes. A stub is either a pure "dummy", just returning some predefined values, or it is "simulating" a more complex behavior.; (8) A protocol extension procedure that connects with the library but remains outside the library.
�stub procedure: In transport independent remote procedure call (TI-RPC) programming, a functional subset of procedures that is needed to implement a client or server protocol.
�stub programming interface (SPI): In DCE Remote Procedure Call (RPC), a private run-time interface whose routines are unavailable to application code.
�stub routine: Within a runtime library, a routine that contains the minimum lines of code needed to locate a given routine.
�stuck process: A process that cannot proceed because it is waiting for an event that cannot, or does not, occur.
�STX character: See start-of-text character.
�style sheet: A specification of formatting instructions that, when applied to structured information, provides a particular rendering of that information (for example, online or printed). Different style sheets can be applied to the same piece of structured information to produce different presentations of the information.
�subactivity state: A state in an activity graph that represents the execution of a non-atomic sequence of steps that has some duration.
�subaddress: An extension of an ISDN address used to identify individual users, processors, or groups of users within a large group of users or processors that are identified by a single network number.
�subagent: (1) An extension to an SNMP agent that permits a user to dynamically add, or in some cases replace, management variables in the local MIB, thereby providing a means of extending the range of information that network managers may access.; (2) An agent that the coordinator agent enlists to speed up SQL processing. See also coordinating agent.; (3) A logical grouping of bundles and services on the common agent. An application uses a subagent to perform actions on a system where the common agent is installed. See also agent, bundle, common agent.
�suballocated file: A Virtual Storage Access Method (VSAM) file occupying a portion of a data space that is already defined. The data space may contain other files. See also unique file.
�subarea: A portion of the SNA network consisting of a subarea node, attached peripheral nodes, and associated resources. Within a subarea node, all network addressable units (NAUs), links, and adjacent link stations in attached peripheral or subarea nodes that are addressable within the subarea share a common subarea address and have distinct element addresses.
�subarea address: In SNA, a value in the subarea field of the network address that identifies a specific subarea.
�subarea node: In SNA, a type 4 or type 5 node that uses network addresses for routing and whose routing tables are, therefore, affected by changes in the configuration of the network. Subarea nodes can provide boundary function support for peripheral nodes.
�subblock: The smallest unit of data accessible in an I/O operation, equal to one thirty-second of a data block.
�subcapacity licensing: Licensing of a product for use on less than the full capacity of the machine. A product must be isolated to a logical partition to be eligible for subcapacity licensing.
�subcapacity pricing: In a partitioned operating environment, a software license that bases charges on the capacity of the partition where the licensed program is used, rather than on the total capacity in the server. See also full-capacity pricing.
�subchannel: A logical function of a channel subsystem associated with the management of a single device.
�subchannel set: A set of subchannel addresses and the mode of operation to be used on those addresses.
�subclass: (1) In Java, a class that is derived from a particular class, through inheritance.; (2) In a generalization relationship, the specialization of another class; the superclass.
�subcommand: A request for an operation that is within the scope of work requested by a previously issued command.
�subcomponent: A group of closely related DB2 for z/OS modules that work together to provide a general function.
�subdiagram: In a collaboration template's activity diagram, a nested diagram. Also, the activity diagram symbol that represents a nested diagram.
�subdirectory: A directory contained within another directory in a file system hierarchy.
�subdomain: A domain that makes up a part of a larger domain.
�subelement: In UN/EDIFACT EDI standards, an EDI data element that is part of an EDI composite data element. For example, an EDI data element and its qualifier are subelements of an EDI composite data element.
�subelement separator: A character that separates the subelements in an EDI composite data element.
�subentry: Secondary or tertiary entry that provides added detail or classification of the main entry. Subentries are used to help users find specific information.
�sub-event: An atomic event that has been added to a composite event.
�sub-event queue: A list of the sub-events of a particular composite event that have fired. Each composite event has a sub-event queue associated with it. The queue may be empty. Sub-events remain on the sub-event queue until they are retrieved, or until a syncpoint occurs.
�subfield: (1) In RPG, the layout of a field within a data structure.; (2) A subdivision of a field with a specific meaning. For example, the SWIFT field 32 has the subfields date, currency code, and amount. A field can have several subfield layouts depending on the way the field is used in a particular message.
�subfield record (SF record): SF records are part of the user data that follows the attach FMH header in an APPC basic conversation. These records indicate the subfield being passed, for example, the userid, password, or new password.
�subfile: In i5/OS, a group of records of the same record format that can be displayed at the same time at a display station. The system sends the entire group of records to the display in a single operation and receives the group from the display in another operation.
�subfile control record format: One of two record formats required to define a subfile in DDS. The subfile control record format describes the size of the subfile and the size of the subfile page, and is used by the program to write the subfile to and read the subfile from the display.
�subfile record format: One of two record formats required to define a subfile in DDS. The subfile record format defines the fields in a subfile record and is used by the program to perform input, output, and update operations to the subfile.
�subflow: A sequence of processing steps, implemented using message flow nodes, that is designed to be embedded in a message flow or in another subflow. A subflow must include at least one Input or Output node. A subflow can be executed by a broker only as part of the message flow in which it is embedded, and therefore cannot be deployed. See also message flow.
�subflow node: A message flow node that represents a subflow. See also primitive.
�subfolder: A folder that is in another folder. For example, if folder A contains folder B and folder B contains folder C, then B and C are subfolders of A because the folder path for each begins with A (A/B/C).
�subform: A form-building shortcut that lets designers store regularly used fields, sections, actions, and other form elements together. Subforms can be placed on a form either permanently or as computed subforms that display on documents as dictated by a formula.
�subgroup: A set of modifications within a copy group that applies to a certain number of copies of a form. A copy group can contain more than one subgroup.
�subject identifier (SID): In the Distributed Computing Environment (DCE), a string that identifies a user or a set of users.
�subject table: The table for which a trigger is created. When the defined triggering event occurs on this table, the trigger is activated.
�subkeyword: In REXX, a symbol reserved by the language processor within the clause of individual instructions. For example, the symbol FOREVER is a subkeyword of the DO instruction.
�sublayer: In OSI, a subdivision within a layer.(I)
�submachine state: A state in a state machine which is equivalent to a composite state but its contents are described by another state machine.
�submap: (1) In Tivoli NetView, a particular view of some aspect of a network that displays symbols that represent objects. The application program that creates a submap determines what part of the network the submap displays.; (2) A map that is called from within another map. Submaps are often used to map child business objects.
�submap stack: The queue of Tivoli NetView submaps that are used to navigate to a particular submap.
�submitter: In the Query Patroller environment, a user given access to submit queries. See also profile, query submission preferences.
�subnet: (1) A network divided into smaller independent subgroups, which still are interconnected.; (2) To divide a network into smaller interconnected, but independent subgroups.
�subnet address: In Internet communications, an extension to the basic IP addressing scheme where a portion of the host address is interpreted as the local network address.
�subnet address mask: A bit mask used by a local system to determine whether a destination is on the same network as the source or if the destination can be reached directly through one of the local interfaces.
�subnet mask: For internet subnetworking, a 32-bit mask used to identify the subnetwork address bits in the host portion of an IP address.
�subnet value: The bit template that identifies to the TCP/IP protocol code which host or hosts are defined by this route. This bit template must be a subset of the subnet mask.
�subnetwork: (1) The communications media that join two network nodes together. A subnetwork is a representation within the OSI reference model of a real network, such as a carrier network, a private network, or a local area network (LAN).; (2) A distinct partitioned piece of an internet network represented by two or more sets of addresses that are subsets of the network's range of addresses.; (3) A configuration whereby a single IP network address is split up so it can be used on several interconnected local networks. A subnetwork is a local configuration; outside it appears as a single IP network.
�subnetwork address: In OSI, a DTE address.
�subnetwork mask: A bit mask of 32 bits that defines the particular subnetwork to which an interface attaches.
�subnormal number: In floating-point representation, any non-zero number that is smaller than the smallest normal number. A subnormal number has zero as the leftmost digit of the significand. See also decimal floating-point number, normal number.
�suboption: A value that can be provided as part of a compile-time or runtime option to specify the meaning of the option.
�suborder: The part of an order that is being shipped to a specific address.
�subordinate: (1) In two-phase commit processing, a recovery manager that must wait for confirmation from its coordinator before committing or backing out changes made to recoverable resources by its part of a distributed unit of work. The subordinate can be in doubt in respect to its coordinator. See also coordinator, in-doubt.; (2) A system in which a child unit of recovery (UR) of a multisystem cascaded transaction resides.
�subordinate agent: See subagent.
�subpage: (1) The unit into which a physical index page can be divided.; (2) A part of a logical page on which traditional line data can be placed. In the page definition, multiple subpages can be placed on a physical page as specified in the print data.
�subplex: A subset of a sysplex that consists of all the members in the sysplex that communicate through cross-system coupling facility ( XCF) groups with each other, and not with members outside the subset.
�subpool: A collection of logical terminals (LTERMs) that can be allocated to an ISC node and can be used with parallel sessions.
�Subpool Queue Block (SPQB): An IMS control block that represents a user.
�subpool storage: All of the storage blocks allocated under a subpool number for a particular task.
�subport: An access point for data entry or exit over a logical connection. The relationship between the physical line and the port is analogous to the relationship between the logical connection and the subport.

�subprocess: A local process that is also a part of another process.
�subprogram: (1) A called program that is combined with the calling program at run time to produce a run unit. A subprogram is below the calling program in the call stack.; (2) A program that is called by another program, such as a subshell. See also main program.; (3) In FORTRAN, a program unit that has a FUNCTION, SUBROUTINE, or BLOCK DATA statement as its first statement.; (4) In the IPA Link version of the Inline Report listing section, an equivalent term for 'function'.
�subquery: (1) A form of a fullselect that is enclosed within parentheses and used as a component of a query.; (2) In SQL, a subselect used within a predicate. For example, a select-statement within the WHERE or HAVING clause of another SQL statement.
�subquery in a basic predicate
�subrecord: The user definition level of a sphere, such as an alternate index, cluster, or generation data set (GDS).
�subrecord control byte (SRCB): In MTAM and RJE, a control character used to provide additional information about a record.
�subroutine: (1) A sequence of instructions within a larger program that performs a particular task. A subroutine can be accessed repeatedly, can be used in more than one program, and can be called at more than one point in a program.; (2) In REXX, an internal, built-in, or external routine called by the CALL instruction that may or may not return a result string. If a subroutine returns a result string, a subroutine can also be called by a function call, in which case it is being called as a function.
�subscribe: (1) To register to access data published by another application or system. See also publish.; (2) In SQL replication, to enable tables or views registered as replication targets to receive initial source data and subsequent changes from tables or views registered as replication sources.
�subscriber: (1) In a Tivoli environment, a resource that is subscribed to a profile manager.; (2) In voice mail, any person who owns a mailbox.; (3) An application that requests information about a specified topic from a publish/subscribe broker.; (4) The consumer of a business service.
�subscriber class: A named set of variables used to define a specific level of service available to telephone subscribers, such as maximum number of messages per mailbox and maximum number of members per mailbox distribution list.
�subscriber identity module (SIM): A smart card inserted into GSM phones that contains the user's telephone account information, and that allows the user to use a borrowed or rented GSM phone as if it were his or her own.
�subscript: (1) A character that is printed one-half line below the normal printing line. For example, the number 2 in the chemical formula for water, H 2 O, is a subscript. See also superscript.; (2) In COBOL, a positive number or variable whose value refers to a particular item in a table.; (3) One or more expressions, each enclosed in brackets, that follow an array name. A subscript refers to an element in an array.; (4) An integer or variable whose value selects a particular element in a table or array.
�subscripted data-name: In COBOL, a data name that is made unique with a subscript.
�subscription: (1) In a Tivoli environment, the process of identifying the subscribers that the profiles are distributed to.; (2) A record that contains the information that a subscriber passes to its local broker to describe the publications that it wants to receive.; (3) In SQL replication, an object that creates subscription sets and subscription-set members. See also replication subscription, registration, Q subscription.; (4) E-mail notices and Really Simple Syndication (RSS) feeds that repository users create to receive when the state of an asset changes.
�subscription cycle: The process in which the Apply program retrieves changed data for a given subscription set, replicates the changes to the target table, and updates the appropriate replication control tables to reflect its status and current progress.
�subscription filter: A predicate that specifies a subset of messages that are to be delivered to a particular subscriber.
�subscription list: In a Tivoli environment, a list that identifies the subscribers to a profile manager. A profile manager can be included in a subscription list in order to subscribe several resources simultaneously rather than adding each resource individually.
�subscription point: The name that a subscriber uses to request publications from a particular set of publication nodes. It is the property of a publication node that differentiates it from other publication nodes in the same message flow.
�subscription set: In SQL replication, a definition that controls the replication of changed data during a subscription cycle. A subscription set can contain zero or more subscription-set members. See also replication source, subscription.
�subscription-set member: In SQL replication, a definition that maps a registered replication source to a replication target. Each member defines the structure of the target table and the rows and columns that are replicated from the source table. See also replication source.
�subselect: The form of a query that does not include a UNION, INTERSECT, or EXCEPT operator. Subselect query syntaxes can differ depending on the platform.
�subsequence field: In a secondary index, a field added to the index segment key data to make the pointer segment key unique.
�subset: To replicate data from part of a source table, rather than from the entire table, to a target table. Data can be subset by rows or by columns.
�subset pointer: In IMS, a pointer used to give direct access to subsets of long twin chains of segments; this can speed up processing of DEDBs.
�subshell: An instance of the shell program started from an existing shell program.
�subspace group: A group of subspaces and a single base space, where the base space is the normal MVS address space as in releases of MVS/ESA prior to MVS/ESA 5.1. See also subspace group facility.
�subspace group facility: A facility in MVS/ESA that can be used for storage isolation to preserve data integrity within an address space. See also subspace group.
�substate: A state that is part of a composite state. See also disjoint substate.
�substitution character: A unique character that is substituted during character conversion for any characters in the source program that do not have a match in the target coding representation.
�substitution group: An XML Schema feature that provides a means of substituting one element for another in an XML message. A substitution group contains a list of global elements that can appear in place of another global element, called the head element.
�substitution relationship: In UML modeling, a dependency relationship in which the client model element takes the place of the supplier model element. See also dependency relationship.
�substitution string: A specified string of characters that replaces a string of characters that were located by a scan operation.
�substitution variable: (1) A variable used to pass information, such as a file name, for use in a message.; (2) In pseudo-JCL, a symbol that is used in a build script and that receives a value from a build server default, from the build script itself, or from a symbolic parameter.; (3) A variable in a procedure or query whose value is specified either by a global variable or by a runtime variable.; (4) A variable in a form whose value is specified by a global variable.
�substring: A part of a character string.
�substructured array: In EGL, a structure item that has an occurs value greater than one and that has subordinate structure items.
�subsystem: (1) In DB2 for z/OS, a distinct instance of a relational database management system (RDBMS).; (2) An operating environment, defined by a subsystem description, where the system coordinates processing and resources.; (3) A secondary or subordinate system, usually capable of operating independently of, or asynchronously with, a controlling system.; (4) In z/OS, a service provider that performs one or many functions, but does nothing until asked. For example, each WebSphere MQ for z/OS queue manager is a z/OS subsystem.; (5) In the Remote System Explorer, a container for a particular user's remote System i libraries, command sets, and jobs.; (6) A model element that has the semantics of a package, such that it can contain other model elements, and a class, such that it has behavior. The behavior of the subsystem is provided by classes or other subsystems it contains. A subsystem realizes one or more interfaces, which define the behavior it can perform.; (7) In Unified Modeling Language (UML), a grouping of model elements, of which some constitute a specification of the behavior offered by the other contained model elements.
�subsystem description: A system object that contains information defining the characteristics of an operating environment controlled by the system. The system-recognized identifier for the object type is *SBSD.
�subsystem identification block (SSIB): The control block that identifies the particular subsystem to which a request is being directed.
�subsystem identifier (SSID): (1) A user-assigned number that identifies a direct access storage device (DASD) subsystem. This number is set by the service representative at the time of installation and is included in the vital product data (VPD).; (2) A number that uniquely identifies a logical subsystem (LSS) within a computer installation.
�subsystem information base: In OSI, an information base that specifies configuration information. The subsystem information base is built mostly by the Administrative Facility and used by OSI Communications Subsystem to control its own operations and network operations.
�subsystem interface (SSI): The means by which system routines request services of the master subsystem, a job entry subsystem, or other subsystems defined to the subsystem interface.
�subsystem options block (SSOB): The control block that identifies the function being requested.
�subtask: A task that is initiated and ended by a higher order task.
�subtasking: The use by CICS of an additional TCB to perform certain functions, such as VSAM requests, as system subtasks. This is in addition to the TCB that CICS uses for normal processing.
�subtransaction: An individual step (such as a single-page request) in an overall transaction.
�subtree: (1) A section of a directory hierarchy, which is also called a directory tree. The subtree typically starts at a particular directory and includes all subdirectories and objects below that directory in the directory hierarchy; that is, any subdirectories or objects connected to the directory or to any lower level of its subdirectories.; (2) A tree structure created by arbitrarily denoting a node to be the root node in a tree. A subtree is always part of a whole tree.
�subtype: A type that extends or implements another type; the supertype.
�subvocabulary: A vocabulary that is called by another vocabulary.
�success code set: One or more expressions that specify the return codes of a successful task. For example, > -1 can be specified to consider all return codes of zero or more a success.
�suffix: (1) A character string attached to the end of a file name that helps identify its file type.; (2) A distinguished name that identifies the top entry in a locally held directory hierarchy. Because of the relative naming scheme used in Lightweight Directory Access Protocol (LDAP), this suffix applies to every other entry within that directory hierarchy. A directory server can have multiple suffixes, each identifying a locally held directory hierarchy.
�summarization: (1) The process of aggregating events and then submitting the set of events with a much smaller number of summary events.; (2) The process of including non-redundant sentences in search results to briefly describe the content of a document. See also dynamic summarization, static summarization.
�summary records: In System i Access, an operation that allows a user to specify that only summary information be transferred instead of entire records.
�summary report: (1) In Query, a report that contains only summary information, such as the total, average, minimum, maximum, or count by a query. See also detail report.; (2) A report that shows the values of many metrics for many components from only one star schema. Typically, a summary report examines large numbers of metrics, often showing subtotals for a particular grouping and grand totals for the entire report. Data in a summary report is typically displayed as a text table, rather than in a graphical format. See also extreme case report, health check report.; (3) A statistics report produced by the CICS statistics utility program (STUP). It summarizes the interval, unsolicited, requested reset, and end-of-day statistics on an applid by applid basis. See also statistics utility program.
�summary table: A materialized query table whose fullselect contains a GROUP BY clause that summarizes data from the tables referenced in the fullselect. See also materialized query table.
�summary task: A task that comprises a series of subtasks.
�superclass: (1) In Java, a class from which a particular class is inherited, perhaps with one or more classes in between.; (2) See parent class.
�supernet mask: A bit template that identifies to the TCP/IP code which bits of the host address are used for routing to specific subnets. A subnet mask has fewer 1 bits than the corresponding class mask for a given Internet Protocol (IP) address.
�super role: See authorization role.
�superscript: A symbol, number, or letter written immediately above and to the right or left of another character. For example, a footnote can be identified in text with a superscript number. See also subscript.
�supersede: To replace or take the place of another component. For example, when you undo an operation, a previous instance of a component supersedes the current component.
�superseded patch: A patch made obsolete by a later version of itself or another related patch.
�supersedes relationship: A concept of one component taking the place of another component. For example, when a user undoes an operation, a previous instance of a component supersedes the current component.
�superset: Given two sets A and B, A is a superset of B if and only if all elements of B are also elements of A. That is, A is a superset of B if B is a subset of A.
�supertype: (1) All the interfaces and classes that are extended or implemented by that type.; (2) In a type hierarchy, a type that subtypes inherit attributes from.
�superuser: (1) A user who has various system control authorities above and beyond that of the ordinary user. In UNIX environments, the standard superuser is root.; (2) See root user.
�superuser authority: The unrestricted ability to access and modify any part of the operating system, usually associated with the user who manages the system.
�supervisor: The part of a control program that coordinates the use of resources and maintains the flow of processor operations.
�supervisor call (SVC): (1) A request that serves as the interface into operating system functions, such as allocating storage. The SVC protects the operating system from inappropriate user entry. All operating system requests must be handled by SVCs.; (2) An instruction that interrupts the program being run and passes control to the supervisor so that it can perform the specific service indicated by the instruction.
�supervisory: Pertaining to a frame format that performs data link control functions such as acknowledging information frames, requesting retransmission, and requesting temporary suspension of transmission. Receive ready (RR), receive not ready (RNR), and reject (REJ) are examples of supervisory frame formats.
�supervisory control and data acquisition (SCADA): A broad term, used to describe any form of remote telemetry system used for gathering data from remote sensor devices (for example, flow rate meters on an oil pipeline) and for the near real time control of remote equipment (for example, pipeline valves). These devices communicate with the broker using the SCADA device protocol (MQIsdp).
�supervisory terminal functions: Part of the CICS system services component that provide a terminal-oriented subset of the services available to the master terminal. These services are limited to the terminals under a given supervisor's control using the CEST transaction. See also terminal list table.
�supervisory terminal operator: Any CICS operator whose security key(s) allow use of the supervisory terminal functions.
�supplemental group: One or more group profiles of which the user is a member. The user's first group profile is specified in the group profile (GRPPRF) parameter of the user profile. Supplemental group profiles are specified in the supplemental group profile (SUPGRPPRF) parameter of the group profile.
�supplementary group ID: A process attribute that is used when file access permissions are determined.
�supplementary service: In Euro-ISDN, a service outside the minimum service offering that each signatory is obliged to provide. For example, calling line identification presentation (CLIP) and call session.
�supplier: A classifier that provides services that can be invoked by others.
�supplier server: A server that sends changes to a consumer server.
�supplier system: For directory shadowing, a system that provides initial or changed Enterprise Address Book (EAB) data to a collector system in a network. See also collector system.
�supply chain: A value chain that supports procurement and sourcing of goods. See also demand chain, value chain business model.
�supply chain management (SCM): The management of resources, functions, and sequence of processes used by organizations involved in the supply of raw materials and products, and their delivery to manufacturers, wholesalers, retailers, and finally consumers.
�support: In system development, to provide the necessary resources for the correct operation of a functional unit.
�Support Assistant (ISA): See IBM Support Assistant.
�support catcher: See catcher.
�supported currency: A currency that an online store is capable of displaying and handling. See also preferred currency, shopping currency.
�Support Element (SE): A hardware unit that provides communications, monitoring, and diagnostic functions to a central processor complex (CPC).
�suppression: In AFP support, a page-and-form-definition function that is used to identify fields in a print record that are not printed on selected pages of a document.
�suppression local ID: A value assigned in the Map Suppression coded field to a suppression named in a Line Descriptor (LND) or Record Descriptor (RCD) structured field. This value is contained in the Begin and End Suppression text controls.
�suppression number: An identification number from 1 to 127 generated by the Map Suppression structured field and assigned to text designated for suppression in the data map transmission subcase.
�surface chart: In the GDDM function, a chart similar to a line chart, except that no markers appear, and the areas between successive lines are shaded.
�surface form: The form of a word or multiword unit as it is found in surface text.
�surface graph: In Performance Tools, a graph similar to a line graph, except that no markers appear, and the areas between successive lines are shaded.
�surface text: Any unprocessed text used for input.
�surrogate pair: A coded representation for a single character that consists of a sequence of two 16-bit code units, in which the first value of the pair is a high-surrogate code unit in the range U+D800 through U+DBFF and the second value is a low-surrogate code unit in the range U+DC00 through U+DFFF. Surrogate pairs provide an extension mechanism for encoding 917 476 characters without requiring the use of 32-bit characters.
�surrogate TCTTE: In CICS transaction routing, a TCTTE in the transaction-owning region that is used to represent the terminal that invoked, or was acquired by, the transaction. See also surrogate terminal.
�surrogate terminal: A terminal whose terminal definition is shipped from a terminal owning region (TOR). See also surrogate TCTTE.
�surveillance: In XRF, a series of processes by which the alternate CICS system monitors the active CICS system for a lapse of activity in order to detect potential failure conditions requiring a takeover. The active and alternate CICS systems use the CAVM surveillance mechanism to monitor each other's well-being.
�surveillance mechanism: A way for IMS in the alternate to determine that the active is processing satisfactorily.
�surveillance signal: In XRF, the signal continuously written to the CAVM data sets by the active and alternate CICS systems to inform each other of their states.
�suspect relationship state: A state applied to a traceability or hierarchical relationship when a change occurs to one or both of the requirements in the relationship. A suspect relationship state indicates that, because of the modification to one or both requirements, the relationship may require modification as well. See also change-managed relationship, traceability matrix.
�suspend: (1) To remove an object from its workflow and define the suspension criteria needed to activate it. Later activating the object enables it to continue processing.; (2) In cross-site mirroring, to temporarily stop geographic mirroring. If the mirror copy contained usable data when suspended, the mirror copy still contains usable, though possibly outdated, data.; (3) To pause a process instance.
�suspended state: (1) In cross-site mirroring, the configuration state of the mirror copy that does not attempt to perform geographic mirroring when the independent disk pool is available. The mirror copy state is suspended when it is not resuming or active.; (2) A state in which only one of the devices in a dual-copy or remote-copy volume pair is being updated as a result of a permanent error condition or an authorized user command. All writes to the remaining functional device are logged. Suspended state allows for automatic resynchronization of both volumes when the volume pair is reset to the active duplex state.
�sustained data rate: The maximum rate at which a device can supply data without pause or interruption.
�SUT: See system under test.
�SV: See schedule variance.
�SVA: See shared virtual area.
�SVC: (1) See switched virtual circuit.; (2) See supervisor call.
�SVC dump: A dump that is issued when a z/OS or a DB2 functional recovery routine detects an error.
�SVC interruption: An interruption caused by the execution of a supervisor call (SVC) instruction, causing control to be passed to the supervisor.
�SVG: See Scalable Vector Graphics.
�SWA: See scheduler work area.
�swab: Cotton attached to the end of a small stick. Used to clean dirt particles or lint from an area.
�swap data set: A data set dedicated to the swapping operation.
�swap file: A file that contains segments of a program or data temporarily moved out of main memory.
�swapped: When using the REXX REVERSE function, pertaining to a process that exchanges the values in the input string by reversing their positions.
�swapping: A process that interchanges the contents of an area of real storage with the contents of an area in auxiliary storage.
�SWDT: See switch data traffic.
�sweep: In AFP support, the movement around an arc from the center point of the arc.
�SWIFT: See Society for Worldwide Interbank Financial Telecommunication.
�SWIFT address: See bank identifier code.
�SWIFTAlliance Gateway (SAG): A SWIFT interface product extending SWIFTNet Link by additional services such as profile-based processing, and offering a WebSphere MQ interface.
�SWIFT Correspondents File: The file containing the bank identifier code (BIC), together with the name, postal address, and zip code of each financial institution in the BIC Directory.
�SWIFT financial message: A message in one of the SWIFT categories 1 to 9 that you can send or receive via the SWIFT network.
�SWIFT header: The leading part of a message that contains the sender and receiver of the message, the message priority, and the type of message.
�SWIFT input message: A SWIFT message with an input header to be sent to the SWIFT network. See also SWIFT output message.
�SWIFT link: The MERVA ESA component used to link to the SWIFT network.
�SWIFTNet FileAct: SWIFT's interactive communication service supporting exchange of files between two applications.
�SWIFTNet FIN: SWIFT's service providing FIN access using the Secure IP Network (SIPN) instead of the SWIFT Transport Network (STN). See also FIN.
�SWIFTNet InterAct: SWIFT's interactive communication service supporting exchange of request and response messages between two applications.
�SWIFTNet Link (SNL): SWIFT's mandatory software product to access all SWIFTNet services.
�SWIFTNet PKI: See SWIFTNet public key infrastructure.
�SWIFTNet public key infrastructure (SWIFTNet PKI): SWIFT's mandatory security software and hardware installed with SWIFTNet Link.
�SWIFTNet service: SWIFT's IP-based communication services that run on the SIPN.
�SWIFTNet service application: An application that uses SWIFTNet services. Financial organizations such as Continuous Linked Settlement (CLS) or the Global Straight Through Processing Association (GSTPA) offer such applications to financial institutions.
�SWIFT network: Refers to the SWIFT network of the Society for Worldwide Interbank Financial Telecommunication (S.W.I.F.T.).
�SWIFT network format: Format of a message used within the SWIFT Network.
�SWIFT output message: A SWIFT message with an output header coming from the SWIFT network. See also SWIFT input message.
�SWIFT system message: A SWIFT general purpose application (GPA) message or a financial application (FIN) message in SWIFT category 0.
�SWIFT transport network: SWIFT's network providing FIN and IFT service based on X.25 technology.
�swimlane: (1) See partition.; (2) A visually separated row within a process flow diagram that groups all the activities in the process that are performed by a particular combination of roles, resources, organization units, or locations.
�Swing Set: A collection of GUI components that runs consistently on any operating system that supports the Java virtual machine (JVM). Because they are written entirely in the Java programming language, these components provide functionality above and beyond that provided by native-platform equivalents. See also Abstract Window Toolkit, Standard Widget Toolkit.
�switch: (1) A network infrastructure component to which multiple nodes attach. Unlike a hub, a switch typically has internal bandwidth that is a multiple of link bandwidth and the ability to rapidly switch a node connection from one to another. A typical switch can accommodate several simultaneous full-link bandwidth transmissions between different pairs of nodes.; (2) A device that provides connections between telephone lines and trunks.; (3) A half-duplex or full-duplex device that detects which devices are attached at each port and passes only frames addressed to those devices on that port. A switch has a small collision domain.
�switchable entity: The physical resource containing the independent disk pools that can be switched between systems in a cluster. This can be a expansion unit containing disk units in a multiple system environment. This could also be an IOP containing disk units in an LPAR environment. See also device cluster resource group.
�switchable hardware group: See device cluster resource group.
�switch back: In a remote journal network, to direct clustering functions to allow the primary system to reassume its role from a previously promoted backup system.
�switch-back: In a remote journal network, pertaining to the processing that is performed by a hot-backup application to allow the primary system to reassume its role from a previously promoted backup system.
�switch data traffic (SWDT): In an XRF configuration, a VTAM session control request sent to the NCP that initiates the switch of LU sessions from backup XRF session status to active XRF session status. The former XRF session, if still 'active', is terminated with an UNBIND. The switch request is issued to VTAM from the application program (alternate CICS system). VTAM passes the request to the boundary network node, where the sessions are actually switched by NCP.
�switched connection: A connection established by dialing. See also nonswitched connection.
�switched fabric: (1) A Fibre Channel topology that provides the underlying structure to interconnect multiple nodes and provides the necessary switching functions to support communication among multiple nodes. See also arbitrated loop, point-to-point.; (2) The physical or logical mapping of the location of networking components or nodes within a network. Common network topologies include bus, ring, star, and tree.
�switched line: In data communications, a connection between computers or devices that is established by dialing. See also nonswitched line.
�switched major node: In VTAM, a major node whose minor nodes are physical units and logical units attached by switched SDLC links.
�switched network backup (SNBU): A modem feature that allows a nonswitched line to be used alternatively as a switched line or allows a switched line to be used as a nonswitched line depending on the characteristics of the modem.
�switched virtual circuit (SVC): (1) A virtual circuit that is requested by a virtual call. It is released when the virtual circuit is cleared.; (2) In OSI, a temporary association between two DTEs that is initiated when one DTE makes a call request to the network.
�switch expression: The controlling expression of a switch statement.
�switch module: The BladeCenter component that provides network connectivity for the BladeCenter chassis and blade servers. It also provides interconnectivity between the management module and blade servers.
�switch over: In a remote journal network, to direct clustering functions to change all uses of a cluster resource to a backup node that becomes the new primary access point of the resource.
�switchover: (1) In a remote journal network, pertaining to the processing that is performed by a hot-backup application to logically promote a backup system to assume the role of a primary system.; (2) A cluster event where the primary database server or application server switches over to a backup system due to the manual intervention from the cluster management interface.
�switchover order: The defined relationship among the primary and backup nodes in a recovery domain.
�switch port: A port on a switch. Switch ports can be expansion ports (E_ports), fabric ports (F_ports), or fabric loop ports (FL_ports).
�switch profile: In WebSphere MQ for z/OS, a RACF profile used when WebSphere MQ starts up or when a refresh security command is issued. Each switch profile that WebSphere MQ detects turns off checking for the specified resource.
�switch statement: A C or C++ language statement that causes control to be transferred to one of several statements depending on the value of an expression.
�SWL: See short wavelength.
�SWT (SWT): See Standard Widget Toolkit.
�syllable hyphen: A hyphen used to divide a word at the end of a line; it may be removed when a program adjusts lines. See also required hyphen.
�symbol: (1) Any combination of alphabetic or numeric characters (A-Z, a-z, or 0-9) and the characters @, #, $, ., !, ?, and _.; (2) In MVS, a group of 1 - 8 characters, including alphanumeric characters and the three characters: #, @, $. The symbol begins with either an alphabetic character or one of the three characters (#,@,$).
�symbolic checkpoint: A checkpoint in a batch, BMP, or JBP application that indicates to IMS that the program has reached a commit point and that establishes a place in the program from which the application can be restarted. See also extended restart.
�symbolic debugger: A tool that aids in the debugging of programs written in certain high-level languages. See also source debugger.
�symbolic description map: A symbolic description map is a source language data structure that the assembler or compiler uses to resolve source program references to fields in the map.
�symbolic destination: A destination identifier specifying a symbolic name that represents a destination. See also destination identifier, explicit destination.
�symbolic destination name: In the OSI Communications Subsystem licensed program, a name by which an application entity identifies to OSI Communications Subsystem the peer application entity with which it is to communicate. OSI Communications Subsystem uses the symbolic destination name to determine (a) the presentation address of the peer application entity, and (b) the application mode to be used on the association.
�symbolic feedback code: The symbolic representation of the first 8 bytes of the 12-byte condition token. In a condition handling routine, a symbolic feedback code is substituted for the hexadecimal coding of the condition token.
�symbolic link: A type of file that contains a pointer to another file or directory.
�symbolic name: (1) A unique name used to identify an entity such as a field, file, data structure, or label within an RPG program.; (2) A string composed of characters from the ISO 646 code set that is used in locales to represent a character.
�symbolic parameter: In EGL, a symbol specified at declaration time, either to override a substitution variable that is used in a pseudo-JCL build script or to specify a value for use in certain build descriptor options.
�symbolic pointer: The concatenation of the keys in the sequence fields of all segments that must be retrieved to reach the desired segment including the sequence field key of the desired segment.
�symbol registration file (SRF): A file that is used to define symbol classes and subclasses.
�symbol resolution: In ILE, the process the binder uses to match unresolved imports from the set of modules to be bound by copy with the set of exports provided by the specified modules and service programs.
�symbol set: (1) In Business Graphics Utility, a supplied character set used for text strings on charts; for example, headings, legend text, labels, and notes.; (2) In PSF, a type of font that resides in a printer but has fewer attributes than can be specified for resident coded fonts.
�symbol table: A list of symbol names and their associated values, usually in an object or executable file, which gives the names of external symbols and their addresses.
�symmetric algorithm: An algorithm where the encryption key can be calculated from the decryption key and vice versa. In most symmetric algorithms, the encryption key and the decryption key are the same.
�symmetrical multiprocessor system (SMP, SMP system): A system containing multiple processors that are essentially identical and perform identical functions.
�symmetrical network: A network in which all the initiators are connected at the same level and all the controllers are connected at the same level. See also oversubscription.
�symmetric cryptography: See shared-secret key cryptography.
�symmetric digital subscriber line (SDSL): A technology that uses digital pulses to send data over copper telephone lines. SDSL cannot operate simultaneously with voice connections over the same wires.
�symmetric encryption: A common key and mathematical algorithm used to both encrypt and decrypt a message. For two people to communicate securely with each other, both need to agree on the same mathematical algorithm to use for encrypting and decrypting data. They also need to have a common key: the secret key. Symmetric encryption is also referred to as secret key encryption.
�symmetric key cryptography: A system of cryptography in which the sender and receiver of a message share a single, common, secret key that is used to encrypt and decrypt the message. See also asymmetric key cryptography.
�symmetric multiprocessor (SMP): A system in which functionally identical multiple processors are used in parallel, providing simple and efficient load balancing.
�symmetric multithreading (SMT): A processor design that combines hardware multithreading with superscalar processor technology. Using SMT, a single physical processor emulates multiple processors by enabling multiple threads to issue instructions simultaneously during each cycle.
�symmetric virtualization: A virtualization technique in which the physical storage, in the form of a Redundant Array of Independent Disks (RAID), is split into smaller chunks of storage known as extents. These extents are then concatenated, using various policies, to make virtual disks (VDisks). See also asymmetric virtualization.
�sympathy sickness: In intercommunication, a condition in which the impaired performance of one region spreads to, and impairs the performance of, connected regions.
�symptom: In the logging tools, an error message. A symptom can have a solution associated with it in the symptom database.
�symptom database: An XML file of symptoms including one or more string match patterns with one or more associated solutions that is used in the analysis of event and error messages that occur in an activity log.
�symptom string: Diagnostic information displayed in a structured format designed for searching the IBM software support database.
�SYN: See synchronization character.
�SYN character: See synchronization character.
�synchpoint: In SQL replication, a control table value for the sequence number in the DB2 log or journal record corresponding to the last change that was applied during the most recent Apply cycle. This value is also used to coordinate the pruning of CD tables. See also change-data table.
�synchronization: (1) A coordinated commitment control process between communicating transactions that ensures that all logically-related updates to recoverable resources are completed or that all are backed out.; (2) The cross-site mirroring (XSM) processing that copies data from the production copy to the mirror copy.; (3) In Unified Modeling Language (UML), the visual representation of the forks and joins representing parallel workflows. Synchronizations enable you to see a simultaneous workflow in an activity diagram or state chart diagram.; (4) The process by which a satellite downloads and runs the same DB2 database commands, operating system commands, and SQL statements from the satellite control server as the other members of its group download and then reports the results to the satellite control server.
�synchronization copy: An initial volume copy that is a track image copy of each primary track on the volume to the secondary volume.
�synchronization level (sync level): The level of synchronization (0, 1, or 2) established for an APPC session between intercommunicating CICS transactions. Level 0 gives no synchronization support, level 1 allows the exchange of private synchronization requests, and level 2 gives full CICS synchronization support with backout of all updates to recoverable resources if failure occurs.
�synchronization mode: In high availability disaster recovery, an option that specifies the level of coordination between the primary and standby databases when logs are sent from the primary database to the standby database in peer state. Synchronization mode determines the balance between performance and the potential for data loss. See also asynchronous mode, synchronous mode, near synchronous mode.
�synchronization phase: The XRF phase, immediately after initialization, when the alternate builds the IMS control blocks to mirror those in the active.
�synchronization point (syncpoint): (1) In APPC, a reference point during transaction processing to which resources can be restored if a failure occurs.; (2) In OSI, a point to which a session can be reset. Setting a synchronization point requires the appropriate token. Synchronization points are a session-layer service.; (3) A point in time from which IMS or an application program can start over if a failure makes recovery necessary. The two types of synchronization points are system checkpoints done by IMS itself, and application program synchronization points (also known as commit points) done on behalf of individual application programs. See also commit point, system checkpoint.
�synchronization character (SYN, SYN character): In binary synchronous communications, the transmission control character that provides a signal to the receiving station for timing the characters received.
�synchronization time interval: The elapsed time in seconds between storage management subsystem (SMS) checks for volume status, space statistics, and configurational changes from other systems in the SMS complex (SMSplex).
�synchronize: To add, subtract, or change one feature or artifact to match another.
�synchronized: Pertinent to remote copy and Peer-to-Peer Remote Copy, the status condition that exists when both virtual disks (VDisks) of a pair that has a copy relationship contain the same data.
�synchronized copy status: A copy status that specifies that a volume copy is either the only volume copy or is synchronized with other volume copies in the database or in the recovery log. When a volume copy is synchronized, mirroring has started.
�synchronize/minor token: In OSI, a session layer token that controls the insertion of minor synchronization points.
�synchronous: (1) Pertaining to two or more processes that depend upon the occurrences of specific events, such as a common timing signal. See also asynchronous.; (2) Occurring with a regular or predictable time relationship.; (3) In cross-site mirroring, pertaining to the mode of geographic mirroring where the program that issues the update waits until the operation is completed on both the production copy and the mirror copy. This mode ensures that once control is returned to the client, the operation is accurately reflected on both the production copy and the mirror copy.
�synchronous action: A request sent by an object that pauses to wait for results. See also asynchronous action.
�Synchronous Data Link Control (SDLC): A protocol for managing synchronous information transfer over a data link connection.
�synchronous data transfer: A physical transfer of data to or from a device that has a predictable time relationship with the execution of an I/O request.
�synchronous disk I/O: In Performance Tools, a disk access operation that must complete before program operation can continue. See also asynchronous disk I/O.
�synchronous dynamic random access memory (SDRAM): A type of dynamic random access memory (DRAM) with features that make it faster than standard DRAM.
�synchronous I/O: In VTAM, suspension of processing of a request sent by the system services control point (SSCP) until the response is received. A variable work area remains allocated while the SSCP waits for the response. When the response is received, the suspended process resumes at the next sequential instruction.
�synchronous level: In finance communications, a level at which a logical unit (LU) determines if it can allocate and deallocate system resources.
�synchronous messaging: A method of communication between programs in which a program places a message on a message queue and then waits for a reply to its message before resuming its own processing. See also asynchronous messaging.
�synchronous mode: In high availability disaster recovery, the synchronization mode in which the primary database considers a transaction to be committed when it gets an acknowledgment message from the standby system that confirms that the relevant log data was received and written to disk on the standby system. See also synchronization mode.
�synchronous PPRC: A function of a storage server that maintains a consistent copy of a logical volume (LVOL) on the same storage server or on another storage server. All modifications that any attached host performs on the primary LVOL are also performed on the secondary LVOL. See also Peer-to-Peer Remote Copy, PPRC Extended Distance.
�synchronous process: A process that starts by invoking a request-response operation. The result of the process is returned by the same operation.
�synchronous processing: A series of operations that are done as part of the job in which they were requested; for example, calling a program in an interactive job at a work station. See also asynchronous processing.
�synchronous replication: A type of replication that delivers updates continuously and within the scope of source transactions. See also asynchronous replication.
�synchronous signal: A signal attributable to a specific thread.
�synchronous transmission: A method of transmission in which the sending and receiving of data is controlled by timing signals. See also asynchronous transmission.
�synchronous write: A form of synchronous I/O that writes the file data to disk, updates the inode times, and writes the updated inode to disk. When the write returns to the caller, both the data and the inode have been written to disk.
�synch state: A vertex in a state machine used for synchronizing the concurrent regions of a state machine.
�sync level: See synchronization level.
�sync point: (1) See point of consistency.; (2) A point during the processing of a transaction at which protected resources are consistent.
�syncpoint: See synchronization point.
�sync point agent: Any transaction that receives a syncpoint request issued by the sync point initiator during a conversation in a dynamic transaction processing environment.
�sync point initiator: The transaction that initiates sync point activity for a distributed unit of work.
�sync point manager: A function that coordinates the two-phase commit process for protected resources, so that all changes to data are either committed or backed out.
�sync point tree: A multilevel tree structure representing a hierarchical relationship among transaction programs and other resource managers in a distributed two-phase commit operation. The root node of the sync point tree is the initiator of the original commit or backout request.
�syndicated content: Content on a Web site that is owned by an outside organization or person. News feeds are an example of syndicated content.
�Synergistic Processor Element (SPE): In the Cell Broadband Engine architecture, a grouping of multiple Synergistic Processor Units (SPUs). The SPEs perform specialized tasks that involve high computational density, such as those required by game, multimedia, and broadband applications. See also Cell Broadband Engine processor, Synergistic Processor Unit.
�Synergistic Processor Unit (SPU): A 128-bit processor with single-instruction multiple-data (SIMD) capabilities specialized for computationally-intensive tasks. The SPUs use a specialized instruction set, for SIMD operations. Multiple SPUs make a up a Synergistic Processing Element (SPE). See also Synergistic Processor Element.
�SYN flood: A type of denial-of-service attack in which an attacker sends a large number of TCP connection requests to a target computer, without answering the target computer's acknowledgment requests. The target computer becomes overloaded and denies service to legitimate users.
�synonym: (1) See alias.; (2) An alternative name for a table or view that can be used in SQL statements to refer only to objects at the subsystem in which the synonym is defined. A synonym cannot be qualified and cannot be used by other users. See also alias.
�synonym aid: A document proofreading function that replaces a given word with one having a similar meaning that the user chooses from a list of synonyms provided by a dictionary.
�synonym dictionary: A dictionary that enables users to search for synonyms of their query terms when they search a collection.
�syntactic analysis: In CoOperative Development Environment/400, a compiler analysis of a program to determine the structure of the program and whether it is valid for a given programming language.
�syntax: (1) The rules for the construction of a command or statement. See also semantics.; (2) In DCE X/Open Object Management (XOM), any of the various categories into which the object management (OM) specification statically groups values on the basis of their form.
�syntax checker: A feature that detects syntax errors in program statements, displays a message, and shows the field or statement in reverse image.
�syntax diagram: A diagram for a command that displays how to enter the command on the command line.
�syntax highlighting: In source editors, the ability to differentiate text and structural elements, such as tags, attributes, and attribute values, using text highlighting differences, such as font face, emphasis, and color.
�syntax tree listing: In OSI, a report produced by the Abstract Syntax Checker that lists the order and hierarchical relationships of presentation data values (PDVs) and data structures--and shows the associated type assignments.
�syntax type: A category used to classify different formats of documents. Data Interchange Services supports three syntax types: XML, EDI, and record oriented data. The user can map and translate between any of these syntax types.
�Synthetic Transaction Investigator playback policy (STI policy): A policy that collects performance data from played back transaction recordings so that the overall performance and availability of a Web site can be evaluated. Transaction recordings often represent common user activity on a Web site, such as searching for information, enrolling in a class, opening or accessing an account, or purchasing goods or services online.
�SYSEVENT class data: A class of monitoring data that provides a special kind of transaction timing information. SYSEVENT monitoring (that is, the collection of SYSEVENT class data) is activated by the MNEVE system initialization parameter. See also monitoring record.
�SYSGEN: See system generation.
�SYSIN: See system input stream.
�SYSLOG: See system log.
�SYSMOD: See system modification.
�SYSOUT: See system output stream.
�sysplex: A set of z/OS systems that communicate with each other through certain multisystem hardware components and software services. See also base sysplex.
�sysplex CDS: See sysplex couple data set.
�sysplex couple data set (sysplex CDS): A couple data set (CDS) that contains sysplex-wide data about systems, groups, and members that use cross-system coupling facility (XCF) services. All systems in a sysplex must be connected to the sysplex CDS. See also couple data set.
�sysplex data sharing: The ability of multiple IMS subsystems to share data across multiple MVS images. Sysplex data sharing differs from two-way data sharing in that the latter allows sharing across only two z/OS images.
�sysplex failure management (SFM): The specification of failure detection intervals and recovery actions to be initiated in the event of the failure of a system in the sysplex.
�sysplex query parallelism: Parallel execution of a single query that is accomplished by using multiple tasks on more than one DB2 for z/OS subsystem. See also query CP parallelism.
�Sysplex Timer: An IBM unit that synchronizes the time-of-day (TOD) clocks in processors. See also external time reference.
�SYSRES volume: See system residence volume.
�system: (1) A set of individual components, such as people, machines, or methods, that work together to perform a function.; (2) A computer and its associated devices and programs.; (3) A single node or a cluster of nodes acting as a single computing entity. A system in this sense may run multiple instances of the operating system. See also cluster node.; (4) A functional unit, consisting of one or more computers and associated software, that uses common storage for all or part of a program and also for all or part of the data necessary for the execution of the program. A system can be a stand-alone unit, or it can consist of multiple connected units.
�System/36 environment: A function of the i5/OS operating system that processes most of the System/36 operator control language (OCL) statements and procedure statements to run System/36 application programs and allows the user to process the control language (CL) commands. See also System/38 environment.
�System/36 object: A configuration description in System/36 terms that defines the System/36 environment. The system-recognized identifier for the object type is *S36.
�System/38 environment: A function of the operating system that processes most of the System/38 control language (CL) statements and programs to run System/38 application programs. See also System/36 environment.
�System/38 Utilities: A licensed program for running and maintaining Data File Utility and Query applications for those who migrate from the System/38 system.
�system abend: An abend caused by the operating system's inability to process a routine. See also user abend.
�system activity keypoint: A keypoint written to the system log automatically while CICS is running normally. See also activity keypoint.
�system adapter identification number (SAID): The unique identification number automatically assigned to each TESS host adapter for use by ESS Copy Services.
�system administrator (SA): (1) The person who controls and manages a computer system.; (2) In OSI, a person who controls how the open system resources of a system or enterprise are used.; (3) A DB2 database user with administrative authority. In DB2 Database for Linux, UNIX, and Windows, this authority is SYSADM. In DB2 for i5/OS, this authority is *ALLOBJ authority. In DB2 for z/OS, this authority is SYSADM.
�system affinity: See affinity.
�system agent: A work request that DB2 for z/OS creates, such as prefetch processing, deferred writes, and service tasks. See also allied agent.
�system analyst: An individual who leads and coordinates requirements elicitation and use-case modeling by outlining the system's functionality and delimiting the system.
�system area network (SAN): The connectivity of multiple systems with the characteristic of high-performance communications and thus an implied short distance between nodes in the network.
�system ASP: The auxiliary storage pool where system programs and system data reside. It can also include user programs and user data. The system ASP (ASP1) always exists. See also auxiliary storage pool, user ASP.
�system assist processor (SAP): The processor that manages the storage and I/O part of the server.
�system authority: An authority level that has full privileges for managing a system but no ability to access the system's data. The system authority level can be SYSCCTRL or SYSMAINT. See also authority level.
�System Authorization Facility (SAF): An MVS interface with which programs can communicate with an external security manager, such as RACF.
�system authorization ID: The primary DB2 authorization ID that is used to establish a trusted connection. A system authorization ID is derived from the system user ID that is provided by an external entity, such as a middleware server.
�system bag: A type of data bag that is created by the MQAI.
�system call: A call by a program to an operating system subroutine.
�system catalog: See catalog.
�system checkpoint: A point at which IMS records its internal status--control information, plus a unique checkpoint ID--and writes the checkpoint table to the restart data set (RDS). This information allows IMS to reconstruct its condition if recovery is later necessary. System checkpointing is done automatically each time a user-selected number of records is written to the log. See also synchronization point.
�system configuration administration: The administration of configuration object types, organizational units, and roles. This is carried out after the product has been installed and is running. See also security administration.
�system configuration list: A list of devices that are provided with the system.
�system configuration special authority: A special authority that allows the user to make changes to system configuration information, such as communications definitions.
�system console: (1) A display station from which an operator can control and observe the system operation.; (2) The device that is in control of the i5/OS operating system after the system has been shut down and when the system is in a restricted state. Only one device can be the system console at one time. See also backup console.
�system contents directory (SCD): A data area whose primary function is to contain major entry pointers for all IMS facilities. Its secondary function is to contain system data and the status of the log functions and commands.
�system control area (SCA): In MFS, a message field that allows an application program to control specific terminal features when the features apply to the terminal for which the message is destined. See also default system control area.
�system control commands: Commands used to manipulate platform-specific entities such as buffer pools, storage classes, and page sets.
�system control element (SCE): Hardware that handles the transfer of data and control information associated with storage requests between the elements of the processor.
�System Control Process (SCP): A MERVA Link component that handles the transfer of MERVA ESA commands to a partner MERVA ESA system, and the receipt of the command response. It is associated with a system control process entry in the partner table.
�system conversation: The conversation that two DB2 for z/OS subsystems must establish to process system messages before any distributed processing can begin.
�system data: The data sets required for initialization and control.
�system database directory: A directory that contains entries for every database that can be accessed by using the database manager. The directory is created when the first database is created or cataloged on the system. See also local database directory.
�system data set: Data set used to store system information that is only accessible to the system.
�system date: The date assigned in the system values when the system is started.
�system default: A default value defined in the system profile.
�system definition: An IMS process that describes databases, application programs, terminals, and other resources to IMS.
�system definition preprocessor: An optional step in the system definition process that performs resource name checking, thus bypassing that procedure in stage 1.
�system description: A description of the system that should include the full name and version identification of the hardware type for the system, the software operating system, and the networking software.
�system diagnostic work area (SDWA): In a z/OS environment, the data that is recorded in a SYS1.LOGREC entry that describes a program or hardware error.
�system directory list (SDL): (CICS/VSA only.) A list containing directory entries of frequently-used phases and of all phases resident in the SVA. The list resides in the SVA.
�System Display and Search Facility (SDSF): An IBM-licensed program that provides a menu-driven full-screen interface that is used to obtained detailed information about jobs and resources in a system.
�system distribution directory: A list of user IDs and identifying information, such as network addresses, used to send distributions.
�system domain object: An object on the system that can be accessed only by a system state program. The object types that can be either system domain or user domain are: *USRSPC, *USRIDX, *USRQ, *PGM, *SQLPKG. All other object types are system domain. See also domain.
�system dump (SDUMP): A dump of all the storage in the system that can be used for problem determination.
�system dump code: A name of up to eight characters by which a system dump will be known. A system dump code can be defined by CICS or by the user and identifies a set of system actions held in the form of an entry in the system dump table. See also dump code.
�system dump table (SDT): A CICS table which may contain an entry for each system dump code. See also dump code.
�system dump table entry: An entry in the system dump table.
�system event: (1) A type of input event that is triggered by BTS's internal processing. For example, issuing a RUN command against an activity for the first time in a process instance triggers a DFHINITIAL system event. See also input event, user-defined event.; (2) An event that is generated by the management server or a management agent for changes related to system operation; for example, a server starting or stopping, failure of the ARM engine on an application server, or authentication problems. See also application event.
�system generation (SYSGEN): (1) See system definition.; (2) The process of creating a particular system tailored to the requirements of a data processing installation.
�system greeting: In voice mail, a default greeting heard by callers to the mailboxes of subscribers who have not recorded a personal greeting or who have selected the system greeting. See also personal greeting.
�system group: (1) In System i Navigator, a logical collection of endpoint systems.; (2) In SNADS, the second part of a system name in the system distribution directory.; (3) All systems that are part of the same Parallel Sysplex and are running the storage management subsystem (SMS) with the same configuration, excluding any systems in the Parallel Sysplex that are explicitly defined in the SMS configuration.
�System Health Monitoring: An IBM Director Agent feature that provides active monitoring of critical system functions, including system temperatures, voltages, and fan speeds. It also handles in-band alert notification for managed systems running Windows and some managed systems running Linux.
�System i: A family of IBM systems distinguished by their object-oriented architecture, integrated relational database, and high-level machine interface. System i systems support the i5/OS, Operating System/400, AIX, and Linux operating systems. See also i5/OS.
�System i5: See System i.
�System i Access asynchronous communications: The support that connects a personal computer to an ASCII Work Station Controller on the system. See also asynchronous communication.
�System i Access for Windows: The IBM licensed program that allows select Windows clients to perform client/server functions from a personal computer over TCP/IP.
�system identification: In an IMS multisystem environment, the means by which a system that is part of a logical link path is identified.
�System i environment: A specific user configuration on a System i server, including the user's default job description, user profile, library list, and current library.
�System i Navigator: A no-charge feature of System i Access for Windows that is bundled with the i5/OS operating system. System i Navigator provides a graphical user interface to common System i management functions. Some of the common management functions include basic operations, TCP/IP configuration, job management, users and groups, database management, and Management Central.
�system initialization: A CICS facility (part of the system support component) that is used to start the CICS job. The facility is resident only long enough to bring CICS into storage and start up CICS.
�system initialization parameter: Parameter used to define capabilities of a CICS system at the time of system initialization. A system initialization parameter can be predefined in the system initialization table (SIT), or specified dynamically from the console, in the SYSIPT data set (CICS/VSE only) or the SYSIN data set, or as a parameter in the startup JCL.
�system initialization program (DFHSIP SIP): CICS program that builds a CICS system using the resources you have defined and any user-designed or purchased applications. DFHSIP receives instructions from system initialization parameters.
�system initialization table (SIT): A table containing parameters used by CICS on start up.
�system input/output bus: A set of hardware components that provide the physical path and logical protocol through which input/output (I/O) processors and I/O adapters communicate with system processors and main storage.
�system input stream (SYSIN): A data definition (DD) statement used to begin an in-stream data set. See also system output stream.
�system integration module (SIM): A program that is invoked during a process activity, which interacts with a management software system.
�system integrity: The ability of an operating system and authorized programs to protect data and the system from unauthorized changes.
�System i object: An object that exists in a library on the server and is represented by an object on the PC. For example, a user profile is a server object represented on the PC by the user profile object.
�System i project: A local container for local source files that allows offline System i development on Windows platforms.
�System i resource: In System Manager, an entity that contains objects and other resources that reside on the server and are represented by System Manager on the PC. System resources supported by System Manager include items within lists, such as user profile and user.
�System i Support Family of Services: A selection of support services, which can be purchased individually or in packages, offered by IBM to customers. These services range from answering questions about system usage and support to consulting on complex system problems.
�system item: A type of data item that is created by the MQAI.
�system job: A batch job created by the i5/OS operating system to control system resources and to schedule jobs.
�system library: (1) The library shipped with the system that contains objects, such as authorization lists and device descriptions created by a user, and the system commands and other system objects required to run the system. The system identifier is QSYS.; (2) A collection of data sets or files in which the parts of an operating system are stored. See also user library.
�system link library: A particular system library.
�system literal: In MFS, a literal field provided by MFS and defined by the user for inclusion in an output message. See also default literal, explicit literal, literal field.
�system log (SYSLOG): (1) See local error log.; (2) The journal (identification='01') that is used by CICS to log changes made to resources for the purpose of backout on emergency restart. See also general log.; (3) A data set or file in which job-related information, operational data, descriptions of unusual occurrences, commands, and messages to and from the operator may be stored.
�system log data set (SLDS): (1) The permanent destination data set for IMS log records. The SLDS is usually on tape or MSS. In an IMS batch region, the SLDS is created at execution time. In an IMS online region, the SLDS is created by copying the online log data set to it by means of the Log Archive utility. See also online log data set, write-ahead data set.; (2) A data set on which IMS archives a full online log data set (OLDS). An SLDS can be on DASD or tape. The contents are used as input to the database recovery process. See also online log data set.
�system logger: A central logging facility provided by MVS/ESA SP 5.2. The MVS system logger provides an integrated MVS logging facility that can be used by system and subsystem components. For example, it is used by the CICS log manager.
�system-managed access-path protection (SMAPP): An i5/OS function that allows a user to specify a goal for the maximum amount of time the system should use to recover access paths after an abnormal system end. The system automatically protects access paths so that they can be recovered within the time specified.
�system-managed buffering (SMB): A facility available for system-managed, extended-format, Virtual Storage Access Method (VSAM), data sets in which DFSMSdfp determines the type of buffer management technique, along with the number of buffers needed, based on data set and application specifications.
�system-managed data set: A data set that has been assigned a storage class. A system-managed data set is sometimes referred to as an SMS-managed data set.
�system-managed directory entry (SMDE): A directory that contains, in the extensible format, all the information contained in the partitioned data set (PDS) directory entry and information specific to program objects.
�system-managed space table space (SMS table space): A table space whose storage space is managed by the operating system's file system manager. This storage model is based on files that are created under subdirectories and are managed by the file system. See also database-managed space table space.
�system-managed storage: Storage managed by the storage management subsystem (SMS). System-managed storage attempts to deliver required services for availability, performance, space, and security to applications. See also DFSMS environment.
�system-managed storage environment: An environment that helps automate and centralize the management of storage. This goal is achieved through a combination of hardware, software, and policies. In the system-managed storage environment for z/OS, the function is provided by DFSMSdfp, DFSMShsm, DFSMSdss, DFSMSrmm, DFSORT, Security Server (RACF), and MVS. See also system-managed storage.
�system-managed tape library: A collection of tape volumes and tape devices that are defined in the tape configuration database (TCDB). A system-managed tape library can be automated or manual. See also tape library.
�system-managed volume: A direct access storage device (DASD), optical, or tape volume that belongs to a storage group. See also DFSMShsm-managed volume, DFSMSrmm-managed volume.
�system management BIOS (SMBIOS): A specification that extends BIOS to support the retrieval of management data.
�System Management Facilities (SMF): A component of z/OS that collects and records a variety of system and job-related information.
�System Management Interface Tool (SMIT): An interface tool of the AIX operating system for installing, maintaining, configuring, and diagnosing tasks.
�System Manager: (1) The IBM licensed program that enables a system in a network to function as a service provider for other systems in the network.; (2) A graphical user interface to administer and manage the WebSphere business integration system. Most administration tasks are performed using System Manager, and many of the tools, such as Map Designer and Relationship Designer, can be accessed through System Manager.
�System Manager Security: An application on the Hardware Management Console (HMC) that ensures that the HMC can operate securely in the client/server mode.
�system menu: (1) A drop-down menu that is activated by clicking the icon at the left of a window's title bar and that allows users to restore, move, size, minimize, or maximize the window.; (2) A list of options that affect the window or the view it contains.
�system menu symbol: A symbol in the leftmost corner of a title bar that gives a user access to choices that affect the window or the view it contains.
�system message field: In MFS, an output device field on 3270 display devices that can be defined to receive system messages, there bypreventing unsolicited IMS messages from destroying a screen format.
�system metadata: Information that is created and managed by the metadata server, such as information about file sets, storage pools, volumes and policies. This information is stored in the system storage pool.
�system modification (SYSMOD): Input to SMP/E that specifies the introduction, replacement, or update of elements in the operating system and associated distribution libraries.
�system monitor: (1) A System i Navigator tool that gathers and displays real-time performance data for the system.; (2) In finance communications, a 4700 controller program used to perform service, configuration, and debugging functions on that controller.; (3) See database system monitor.
�system name: (1) An IBM-supplied name that uniquely identifies the system. It is used as a network value for certain communications applications such as APPC.; (2) An IBM-defined name that has a predefined meaning to the COBOL compiler. System names include computer names, language names, device names, and function names.
�system object: A machine object classification. Any of the machine objects shipped with the system or any of the operating system objects created by the system. See also program object.
�System Object Model (SOM): Object-oriented programming technology for building, packaging, and manipulating binary class libraries.
�system operator: The person responsible for performing system-oriented procedures. See also system programmer, storage administrator, storage administration group, user group.
�system operator message queue: A special message queue to which the system sends messages regarding changes in the status of the system, devices, and jobs, and messages indicating a condition that needs operator intervention. This message queue is identified by the name QSYSOPR.
�system output stream (SYSOUT): A data definition (DD) statement used to identify a data set as a system output data set. See also system input stream.
�system output writer: A job scheduler function that transcribes specified output data sets onto a system output unit, independently of the program that produced the data sets.
�system performance: A major factor in measuring system productivity. Performance is determined by a combination of throughput, response time, and availability.
�system pointer: A pointer that contains addressability to a machine interface system object.
�system policy: In Backup, Recovery, and Media Services, a policy that defines the overall default controls and values to be used by Backup, Recovery, and Media Services. These values can be defaulted to, or overridden by, the backup policy, archive policy, media policies, or move policies.
�system pool: A storage pool that contains the system metadata (system and file attributes, configuration information, and metadata server state) that is accessible to all metadata servers in the cluster. There is only one system pool. See also metadata server.
�system port: A serial port that is available for specifically supported functions. This port is limited to serial-connected TTY console function and use of approved call-home modems, and, in some cases, an uninterruptible power supply.
�system power control network (SPCN): An asynchronous serial communications network. SPCN connects the power system in participating components to the operating system and can report critical changes and power failures in those components to the operating system. SPCN gives the operating system control of electrical power.
�system process: An implementation-dependent object, other than a process executing an application, that has a process ID. X/Open.
�system processor: The logic that contains the processor function to translate and process the i5/OS control language commands and programming language statements.
�system product division (SPD): A bus architecture that allows I/O to communicate to the processor. SPD-I/O refers to devices that use the SPD bus architecture to communicate with the rest of the system.
�system profile: The partition layout and list of files to deploy an operating system, either by unattended setup or by cloning. A system profile can have several configurations.
�system program: A program providing services in general support of the running of a system.
�system programmer: A programmer who plans, maintains, and controls the use of an operating system with the aim of improving overall productivity of an installation. See also system operator.
�system programming commands: Commands used to monitor and change parameters within a CICS control region.
�system programming interface: A subset of the CICS application programming interface that accesses special system-orientated CICS services.
�system queue area (SQA): An area of virtual storage below the 16MB line reserved for system-related control blocks.
�system recovery table (SRT): A table listing the ABEND or abnormal condition codes that CICS will intercept.
�system reference code (SRC): (1) The characters that identify the name of the unit that detected the condition and the reference code that describes the condition.; (2) A group of characters that identifies the machine status or a specific error condition. The system reference code can be displayed on the console from the problem log.
�system reference library (SRL): The IBM-provided manuals that describe programming and hardware products.
�System Request key: A key that allows the user to start another interactive job at the user's workstation. The user can then use the System Request key to switch back and forth between jobs. An alternative job can be particularly useful for doing another task or viewing information without having to leave other work.
�system requirements review: In the waterfall life cycle, the name of the major review held when the system specification is completed.
�system residence volume (SYSRES volume): The volume on which the nucleus of the operating system and the master catalog are stored.
�system resource: Any computer resource that is controlled by the system, such as programs, devices, and storage areas that are assigned for use in jobs.
�system resource management database object (SRM database object): In the system resource management (SRM) database, a repository of information about the hardware of the system. This information includes vital product data (VPD) from self-reporting hardware and additional topology and location information provided by manufacturing, service representatives, and users. This repository is carried out by system data space and index objects and provides a means for users to manage their system resources.
�system resources manager (SRM): (1) A group of programs that controls the use of system resources, such as programs, devices, and storage areas that are assigned for use in jobs.; (2) A component of the MVS control program.
�systems analyst: A specialist who is responsible for translating business requirements into system definitions and solutions.
�system security: A system function that restricts the use of files, libraries, folders, and devices to certain users.
�system selector: In the WebSphere MQ Administration Interface (MQAI), a system item identifier that is included in the data bag when it is created.
�system services control point (SSCP): A focal point in an SNA network for managing configuration, coordinating network-operator and problem-determination requests, and providing directory support or other session services for network users.
�system services control point identifier (SSCP ID): In SNA, a number uniquely identifying a system services control point. The SSCP ID is used in requests sent to physical units and to other system services control points.
�system service tools (SST): The part of the service function used to service the system while the operating system is running.
�system service tool user profile: The system-supplied user profile that has the authority necessary to service the system programming and the special authorities of save system authorities and job control authorities. Named SRV or QSRVBAS.
�systems management: (1) In OSI, the process of monitoring, coordinating, and controlling resources within open systems.; (2) In System Manager, all of the actions and procedures that accomplish the business support activity of making information systems services available. Information systems services include host, application, network, and data services.; (3) Functions in the application layer related to the management of Open Systems Interconnection (OSI) resources and their status across all layers of the OSI architecture.
�systems management application: In OSI, an application that provides systems management services.
�systems management application entity (SMAE): In OSI, the part of an agent process or a managing process that performs systems management communications functions. In OSI Communications Subsystem, both the agent process and the managing process use the same SMAE.
�Systems Network Architecture (SNA): The description of the logical structure, formats, protocols, and operational sequences for transmitting information through and controlling the configuration and operation of networks.
�Systems Network Architecture distribution services (SNA distribution services, SNADS): An IBM asynchronous distribution service that defines a set of rules to receive, route, and send electronic mail in a network of systems.
�Systems Network Architecture File Services (SNA/FS, SNA/File Services): A service that allows files to be fetched, moved, and stored at nodes in a SNADS network. SNA/FS provides name structure and version identification mechanisms that uniquely identify files in a network.
�Systems Network Architecture Management Services Transport (SNA/MS Transport, SNA/Management Services Transport): A service that allows files to be fetched, moved, and stored at nodes in a SNADS network. SNA/FS provides name structure and version identification mechanisms that uniquely identify files in a network.
�Systems Network Architecture/network job entry (SNA/NJE): A networking capability that works in combination with MVS/Bulk Data Transfer (MVS/BDT). Networking is established between nodes through MVS/BDT sessions.
�system-specific format: A print descriptor naming convention required to store a print descriptor in a print descriptor group.
�systems programming facility: A runtime facility of the C language that supports the development of programs that do not require Language Environment common library.
�System SSL: An implementation of SSL, no longer supported by CICS Transaction Gateway on z/OS. Written in native code, it supports hardware encryption technology available to z/OS, and can be used only for SSL servers on that operating system.
�system state program: A program that can access a user domain object or a system domain object. The system state is reserved for IBM-supplied programs.
�system statistics: Statistics that are accumulated continually by CICS management programs in CICS system tables during the execution of CICS. System statistics can be captured and recorded, either on request or automatically at intervals, by any operator whose security code allows access to such information. In addition, system statistics are recorded on shutdown of the system.
�system status index (SSI): A field in the directory entry of a program module which can be used to record current maintenance status.
�system storage pool: A storage pool containing file-system control structures, reserved files, directories, symbolic links, special devices, and the metadata associated with regular files, including indirect blocks and extended attributes. The system storage pool can also contain user data.
�system-supplied formats: The communications record formats provided as part of the ICF support that allows a user's program to control data communications with a remote system. System-supplied formats perform such communications functions as starting remote programs, sending and receiving data, ending communications transactions, and ending sessions.
�System Support Program (SSP): An IBM licensed program, made up of a collection of utilities and small programs, that supports the operation of the NCP.
�system temporary table space: A temporary table space that stores system temporary tables. A system temporary table space is created by default when a database is created. See also temporary table space.
�system time: (1) The elapsed time from the point when the system was started to the current time.; (2) The amount of time that the operating system spends providing services to an application. System time includes time spent by the operating system allocating storage or devices to a program and time spent processing operating system calls that a program makes. See also run time, user time, execution time.
�system under test (SUT): A system, subsystem, or component that is being tested.
�system unit: The part of a computer that contains the processing unit, and may contain devices such as disk units and tape units.
�system value: Control information for the operation of certain parts of the system. A user can change the system value to define the user's working environment. System date and library list are examples of system values. See also network attribute.
�system variable: (1) A permanent global variable defined by WebSphere Voice Response for use by state tables. Many system variables are loaded with values when the state table is initialized. Some values are taken from system parameters. See also input parameter, local variable.; (2) A user-defined keyword and value pair that can be used to test and track the status of network resources. System variables can be referred to wherever event-data substitution is allowed.

�

Back to top�