CICS - Glossário Letra S

Letra S

SAA: See Systems Application Architecture (SAA).
SAA communications interface: A programming interface that allows program-to-program communication using the SNA APPC protocols.
SAA resource recovery interface: A programming interface that provides a consistent application programming interface for applications that make changes to protected system resources.
SAF: See System Authorization Facility (SAF).
SAM: See sequential access method (SAM).
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 (DFH0STAT): 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.
SAS: See spool access support (SAS).
SBA: See set buffer address (SBA).
SBCS: See single-byte character set.
schedule: To select jobs or tasks that are to be run.
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. See The dynamic storage areas for more information.
scheduling intent: An application program attribute defined in the PSB that specifies how the program should be scheduled if multiple programs are contending for scheduling.
scope: 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. For configuration tasks, where the context is a CICSPlex SM address space (CMAS), the scope is ignored. When you are applying security, scope must be a single CICS system or CICSplex. It cannot be a CICS system group or any combination of individual CICSplexes or CICS systems. See also context.
scoping: A mechanism for controlling multiple sign-ons of the same userid to one or more CICS regions.
screen: The physical surface of a display device upon which information is shown to a user.
Screen Definition Facility (SDF): An interactive tool used to define and maintain maps, map sets, and partition sets for CICS and BMS applications.
screen-image interface: The part of the Front End Programming Interface that has a buffer with one byte for each screen position.
screen page: The amount of data displayed, or capable of being displayed, at any one time on the screen of a terminal.
SCS: See SNA character string (SCS)
SDF: See Screen Definition Facility (SDF).
SDL: See system directory list (SDL).
SDLC: See syncpoint.
SDSA: See shared dynamic storage area (SDSA).
SDT: See series definition table (SDT).
SDWA: See system diagnostic work area (SDWA).
secondary index: 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 alternate index (AIX).
secondary logical unit (SLU): In an SNA session, the logical unit that received the bind request that established the session. The same logical unit can be the SLU in some sessions and the primary logical unit (PLU) in others.
security: The protection of data, system operations, and devices from accidental or intentional ruin, damage, or exposure.
security category: In RACF, an installation-defined name corresponding to a department or area within an organization with similar security requirements.
security classification: In RACF, the use of security categories, a security level, or both, to impose additional access controls on sensitive resources. An alternative way to provide security classifications is to use security labels.
security label: In RACF, an installation-defined name that corresponds to a specific RACF security level with a set of (zero or more) security categories.
security level: In RACF, an installation-defined name that corresponds to a numerical security level; the higher the number, the higher the security level.
security manager domain: A CICS domain that handles all the interfaces to the external security manager, for example, RACF.
security role: An attribute of an enterprise bean that represents a type of user of an application in terms of the permissions that the user must have to successfully use the application. The security roles for an application are defined by the application assembler, and are specified in the bean's deployment descriptor. For more information, see Security roles, deployed security role.
security token: In RACF, a collection of identifying and security information that represents data to be accessed, a user, or a job. This contains a userid, groupid, security label, node of origin, and other information.
segment: 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.
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.
sequential access: 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.
sequential access method (SAM): An access method for storing and retrieving data blocks in a continuous sequence. In CICS Transaction Server only, the queued sequential access method (QSAM) extends the basic sequential access method (BSAM) by queuing the input and output blocks.
sequential data set: In an OS/390 environment, 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 (PDS).
serially reusable: The attribute that describes a serially reusable load module. Only one copy of a serially reusable load module is loaded into virtual storage to satisfy the requirements of any number of tasks, but only one task can execute the module at any one time. If the copy is in use when a request is issued for the module, the task requiring the module is placed in a wait condition until the module is available. The module is designed to be reused and therefore must contain the necessary logic to reset control variables and data areas at entry or exit. A second task may not enter the module until the first task has finished.
series definition table (SDT): A CICS table that holds, for each journal, the name, size, and pointers to the first and current volume descriptors.
server: In a network, hardware or software that provides facilities to other stations; for example, a file server, a printer server, a mail server. The station making the request of the server is usually called the client. See also client, host.
service class: A subset of a workload having the same service goals or performance objectives, resource requirements, or availability requirements. For workload management, you assign a service goal to a service class.
service definition: 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 elements: The discrete hardware and software products that provide a terminal user with processing ability.
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.
service policy: 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.
service request block (SRB): An MVS dispatchable unit. See also dispatch.
servlet: A Java program that is executed on a Web server or application server, generally to access a database or perform a B2B function.
session: (1) A logical or virtual connection between two stations, programs, or devices on a network that allows the two elements to communicate and exchange data, or the activities that occur during the establishment, maintenance, and release of the connection. A session can be activated and deactivated as requested. Sessions may be uniquely identified. See also network addressable unit (NAU).; (2) A name for a type of resource that controls local LUs, remote LUs, modes, and attachments. See also mode.; (3) In a distributed application, a single conversation between a communicating pair of transactions. For further information, see the Intercommunication Guide. See also conversation, connection.; (4) In CICS intersystem communication, the resource that is used by a single conversation. Each CICS SESSION definition identifies a remote system by naming a CONNECTION definition.
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 entity bean.
session key: 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 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. Also known as bind-time security. See also BIND, link security, and user security.
SESSION segment: The portion of a RACF profile containing data used to control the establishment of sessions between logical units under LU6.2.
set and test sequence number (STSN): In SNA, a communication protocol whereby transmissions can be checked.
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.
setup program: A user-provided program that defines and inquires about FEPI resources, and performs housekeeping for the sessions.
SF record (subfield 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.
shareable application class path: The class path used in a JVM for shareable application classes, which are cached either in the application-class system heap or in the shared class cache. It is specified by the ibm.jvm.shareable.application.class.path option in the JVM properties file. See also standard class path.
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 class cache: A cache of Java class files that is shared by a set of JVMs within an address space. A master JVM manages the shared class cache, and worker JVMs share it.
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. For more details, see the The dynamic storage areas.
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. Storage in a shared partition is addressable by programs running concurrently in other partitions. See also private partition.
shared virtual area (SVA): In CICS/VSE, a major element of VSE/ESA virtual storage both above and below the 16MB line. The storage areas that make up the SVA contain all the common reentrant modules shared by the system. The SVA provides economy of real storage by sharing one copy of the modules, protection because SVA code cannot be overwritten except by key 0 programs, and reduced pathlength because the modules can be branched to. The SVA is duplicated above the 16MB line and is often referred to as the 31-bit SVA. See the CICS/VSE Performance Guide for more information.
shift-out/shift-in (SO/SI): In CICS, control characters that delimit DBCS characters in a mixed datastream.
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.
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 storage cushion and program compression.
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 UOW id: An 8-byte value that CICS passes to resource managers, such as DB2 and VSAM, for lock management purposes.
shunted: 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.
side information: 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.
sign on: In CICS, to perform user identification and verification. The CICS user signs on to CICS using a CICS transaction: CESN in CICS Transaction Server, CSSN in CICS/VSE.
signon 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.
signon table terminal entry (SNTTE): An entry created by CICS if a terminal user signon is valid.
signon transaction program: Used by the PEM requester. The signon transaction program is a user-written transaction program that provides send support required by the CICS PEM server.
single-byte character set (SBCS): A character set in which each character is represented by a one-byte code. A one-byte code point allows representation of up to 256 characters. Languages that are based on an alphabet, such as the Latin alphabet (as contrasted with languages that are based on ideographic characters) are usually represented by a single-byte coded character set. For example, the Spanish language can be represented by a single-byte coded character set. See also double-byte character set (DBCS).
single-MVS environment: An environment that supports one MVS image. See also MVS image.
single point of control: The ability to access and manage all CICS systems and their resources in a CICSplex from a single terminal or user session.
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 system image: 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).
single threading: The execution of a program to completion. Processing of one transaction is completed before another transaction is started. See also multithreading.
single-use JVM: A Java Virtual Machine (JVM) that is initialized, is used to run a single Java program, and then is destroyed. A single-use JVM has the option REUSE=NO specified in its JVM profile.
single-VSE environment: An environment that supports one VSE image. See also VSE image.
SIT: See system initialization table (SIT DFHSIT).
SLA: See service level agreement.
SLDS: See system log data set (SLDS).
SLU: See secondary logical unit (SLU).
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.
SMF: See system management facility (SMF).
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.
SMP/E: See System Modification Program Extended (SMP/E).
SMSVSAM: The name of the VSAM server that provides VSAM record-level sharing (RLS). See also VSAM RLS.
SNA: See Systems Network Architecture (SNA).
SNA character string (SCS): In SNA networking, a string of EBCDIC control characters carried within a request/response unit (RU); the string may also contain end-user data.
snap dump: A dump that can be requested by a task at any time during which that task is being processed.
snapshot dump: See snap dump.
SNT: See signon table (SNT).
SNTTE: See signon table terminal entry (SNTTE).
software: The programs, procedures, rules, and associated documentation pertaining to the operation of a system. See also hardware.
SOS: See short-on-storage (SOS).
SO/SI: See shift-out/shift-in (SO/SI).
source program: A set of instructions that are written in a programming language and must be translated to machine language before the program can be run.
source temporary store (STS): The SMP/E primary data set, used to hold updated versions of source elements.
spanned record: In a VSAM KSDS or ESDS, a logical record that occupies more than one control interval.
SP commands: The subset of CICS API commands (COLLECT, DISCARD, INQUIRE, PERFORM, and SET) that require the special CICS translator option, SP, and for which command security checking can be done. For programming information, see Introduction to System Programming commands.
specific applid: In XRF, the name used by the active CICS system when it opens the VTAM ACB. See application identifier (VTAM applid), generic applid.
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.
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.
spooling: The use of auxiliary storage as buffer storage in order to reduce processing delays when transferring data between peripheral equipment and computer processors.
SQA: See system queue area (SQA).
SQL/DS: See Structured Query Language/Data System (SQL/DS).
SRB: See service request block (SRB).
SRL: See system reference library (SRL).
SRM: See system resources manager (SRM).
SRT: See system recovery table (SRT).
SSA: See segment search argument (SSA).
standalone JVM: A JVM that can be used to run Java programs, but does not share the class cache owned by the master JVM. A standalone JVM has the option CLASSCACHE=NO specified in its JVM profile (or does not have the option specified at all).
standard class path: The class path used in a JVM for non-shareable application classes, which are not cached. In CICS, it is specified by the CLASSPATH option in the JVM profile. See also shareable application class path.
standard label: A label format predefined for automatic processing by IBM programs.
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.
startup: The operation of starting up CICS by the system operator.
startup job stream: A set of job control statements used to initialize CICS.
state (conversation): 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 transition, state variable.
stateful session bean: A session bean with a conversational state. (Sun) See also stateless session bean.
stateless session bean: A session bean with no conversational state. All instances of a stateless bean are identical. (Sun) See also stateful session bean.
state transition: A change by a conversation from one state to another. See also state (conversation).
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 state (conversation).
static partition: 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 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.
statistics: System statistics 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. See unsolicited statistics, end-of-day statistics, requested statistics, and requested reset statistics.
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 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 summary report.
steal: The situation when CICS assigns an available TCB from a TCB pool, when the TCB is of the wrong mode (for example, it is a J8 TCB instead of a J9 TCB). The TCB must be destroyed and replaced with a TCB of the correct mode (that is, it must be "stolen" from one TCB mode by another TCB mode). See also mismatch.
storage: A functional unit into which data can be placed and from which it can be retrieved. See main storage, real storage, virtual storage.
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 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 cushion: A noncontiguous area of storage in the dynamic storage areas reserved for use by CICS when processing a short-on-storage condition.
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 manager domain: Major component of CICS which manages virtual storage requests.
storage protection: An optional facility in CICS Transaction Server that enables users to protect CICS code and control blocks from being overwritten inadvertently by application programs.
storage protection key: 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.
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.
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.
stress: A shortage of free space in the DSA or EDSA, such that CICS cannot recover from virtual storage depletion.
string: A sequence of elements of the same nature, such as characters considered as a whole. For example, character string, binary string, and hexadecimal string. OS/2
Structured Query Language/Data System (SQL/DS): An IBM relational database management facility used for processing SQL or DB2 databases.
STS: See source temporary store (STS).
STSN: See set and test sequence number (STSN).
STSN handler: A user-provided part of a FEPI application that handles STSN requests.
stub: A small module, link-edited into application code, that locates and transfers control to a larger body of related code.
stuck process: A process that cannot proceed because it is waiting for an event that cannot, or does not, occur.
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 record: See SF (subfield) record.
subordinate: 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, two-phase commit, in-doubt.
subroutine: A sequenced set of instructions that can be used in one or more programs and at one or more points in a program. The execution of a subroutine is usually invoked by a call.
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.
subspace group facility: A facility in MVS/ESA 5.1, which can be used for storage isolation to preserve data integrity within an address space.
substring: A part of a character string.
subsystem: A secondary or subordinate system, usually capable of operating independently of, or asynchronously with, a controlling system.
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.
summary report: 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.
supervisor: The part of a control program that coordinates the use of resources and maintains the flow of processor operations.
supervisor call (SVC): An instruction that interrupts the program being run and passes control to the supervisor so it can perform a specific service indicated by the instruction.
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 (TLT).
supervisory terminal operator: Any CICS operator whose security key(s) allow use of the supervisory terminal functions.
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 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 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.
SVA: See shared virtual area (SVA).
SVC: See supervisor call (SVC).
SWA: See scheduler work area (SWA).
SWDT: See switch data traffic (SWDT).
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 that is established by dialing.
switched line: In data communications, a connection between computers or devices that is established by dialing. See also nonswitched line.
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.
sympathy sickness: In intercommunication, a condition in which the impaired performance of one region spreads to, and impairs the performance of, connected regions. For more details, see Overview of session queue management.
symptom string: Diagnostic information displayed in a structured format designed for searching the IBM software support database.
synchronization: In CICS, 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.
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.
synchronous: (1) Pertaining to an event that happens, exists, or arises at precisely the same time as another event.; (2) Pertaining to an operation that occurs regularly or predictably with regard to the occurrence of a specified event in another process; for example, the calling of an input/output routine that receives control at a precoded location in a program.
Synchronous Data Link Control (SDLC): (1) A discipline conforming to subsets of the Advanced Data Communication Control Procedures (ADCCP) of the American National Standards Institute (ANSI) and High-level Data Link Control (HDLC) of the International Organization for Standardization, for managing synchronous, code-transparent, serial-by-bit information transfer over a link connection. Transmission exchanges may be duplex or half-duplex over switched or nonswitched links. The configuration of the link connection may be point-to-point, multipoint, or loop.; (2) A discipline for managing synchronous information transfer over a data link connection. See also binary synchronous communication (BSC).
synchronous processing: A series of operations performed as part of the application in which they are requested. For example, function shipping, distributed transaction programming. See also asynchronous processing.
sync level: See synchronization level (sync level).
syncpoint: A logical point in the execution of an application program where the changes made by the program are consistent and complete, and can be committed. The output, which has been held up to that point, is sent to its destination, the input is removed from the message queues, and updates are made available to other applications. When a program terminates abnormally, CICS recovery and restart facilities do not backout updates prior to the last completed sync point.
syncpoint agent: Any transaction that receives a syncpoint request issued by the syncpoint initiator during a conversation in a dynamic transaction processing environment.
syncpoint initiator: The transaction that initiates syncpoint activity for a distributed unit of work. See also syncpoint agent.
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.
SYSMOD: See system modification (SYSMOD).
sysplex: See system complex.
system: (1) The computer and its associated devices and programs.; (2) A single 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.
system activity keypoint: A keypoint written to the system log automatically while CICS is running normally. See also activity keypoint.
System Authorization Facility (SAF): A z/OS facility through with programs communicate with an external security manager such as RACF.
system complex: Multiple MVS images coupled together by hardware elements and software services. When multiple MVS images are coupled using the OS/390 cross-system coupling facility (XCF), which provides the services to form a sysplex, they can be viewed as a single entity.
system data set: Data set used to store system information that is only accessible to the system.
system diagnostic work area (SDWA): Data recorded in a SYS1.LOGREC entry, which describes a program or hardware error.
system directory list (SDL): (CICS/VSE 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 dump (IDUMP): A dump of all the storage in the system that can be used for problem determination. A system dump can be requested with the CEMT PERFORM SNAP command.
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. CICS system dump codes contains a list of the CICS system dump codes. 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. The key for an entry is a system dump code. A system dump table entry contains the following system action options: whether to create a system dump, whether to shut down CICS, and the maximum number of times action is to be taken. The following statistics are recorded in a system dump table entry: number of times action has already been taken, number of system dumps created, and the number of system dumps suppressed. For more information, see the CICS Transaction Server Problem Determination Guide.
system event: 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.
system generation: The process of creating a particular system tailored to the requirements of a data processing installation.
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 log: The journal (identification='01') that is used by CICS to log changes made to resources for the purpose of backout on emergency restart.
system log data set (SLDS): 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 OLDS.
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 Management Facility (SMF): A z/OS facility that collects and records a variety of system and job-related information. For example, statistics, accounting information, and performance data.
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 Modification Program Extended (SMP/E): An IBM licensed program used to install software and software changes on z/OS systems. In addition to providing the services of SMP, SMP/E consolidates installation data, allows more flexibility in selecting changes to be installed, provides a dialog interface, and supports dynamic allocation of data sets.
system performance: A major factor in measuring system productivity. Performance is determined by a combination of throughput, response time, and availability.
system program: A program providing services in general support of the running of a system.
system programming interface: A subset of the CICS application programming interface that accesses special system-orientated CICS services.
system property: For a JVM, a name and value pair that contains information about the JVM and its environment, such as the operating system in which the application is running.
system queue area (SQA): A major element of MVS/ESA virtual storage below the 16MB line. This storage area contains tables and queues relating to the entire system. Its contents are highly dependent on the configuration and job requirements at installation. The equivalent area above the 16MB line is the extended system queue area (ESQA).
system recovery table (SRT): (1) A table listing the ABEND or abnormal condition codes that CICS will intercept.; (2) System initialization parameter that specifies the system recovery table suffix.
system reference library (SRL): The IBM-provided manuals that describe programming and hardware products.
system resources manager (SRM): A component of the MVS control program.
Systems Application Architecture (SAA): A set of common standards and procedures for working with IBM systems and data. SAA enables different software, hardware and network environments to coexist. It provides bases for designing and developing application programs that are consistent across different systems. See also: acquired process, CPI, SAA communications interface, Common User Access (CUA), and SAA resource recovery interface.
Systems Network Architecture (SNA): An architecture that describes the logical structure, formats, protocols, and operational sequences for transmitting information units through the networks and also the operational sequences for controlling the configuration and operation of networks. The layered structure of SNA allows the ultimate origins and destinations of information (the users) to be independent of and unaffected by the specific SNA network services and facilities that are used for information exchange.
system support program: A program product that defines and generates an NCP and provides it with utility programs.