SC20 1043 6_CICS_System_Programmers_Reference_Manual_Mar75 6 CICS System Programmers Reference Manual Mar75
SC20-1043-6_CICS_System_Programmers_Reference_Manual_Mar75 manual pdf -FilePursuit
SC20-1043-6_CICS_System_Programmers_Reference_Manual_Mar75 SC20-1043-6_CICS_System_Programmers_Reference_Manual_Mar75
User Manual: SC20-1043-6_CICS_System_Programmers_Reference_Manual_Mar75
Open the PDF directly: View PDF .
Page Count: 246
Download | |
Open PDF In Browser | View PDF |
SH20-1043-6 Program Product Customer Information Control System (CICS) System Programmer's Reference Manual Program Nos. 5736-XX6 (DOS-ENTRY) 5736-XX7 (DOS-STANDARD) 5734-XX7 (OS·STANDARD V2) The IBM Customer Information Control System (CICS) is a transaction-oriented, multiapplication data base/data communication interface between a System/360 or System/370 operating system and user-written application programs. Applicable to most online systems,CICS provides many of the facilities necessary for standard terminal applications: message switching, inquiry. data collection, order entry, and conversational data entry. CICS is available in three systems - two for DOS users and one for OS users. Because the two CICS/DOS systems are compatible with each other and with the CICS/OS system, it is possible to start with a small data base/data communication configuration and move up through DOS into OS. This manual provides information essential for persons who have the responsibility to define, prepare, and administer CICS in the environment it supports. Seventh Edition (March 1975) This edition applies to Version 1, Modification Level 1, of the CICS/DOS-ENTRY (5736-XX6) and CICS/DOS-STANDARD (5736-XX7) program products and to Version 2, Modification Level 3, of the CICS/OS-STANDARD (5734-XX7) program product; it also applies to all subsequent versions and modifications unless otherwise indicated in new editions or Technical Newsletters. If changes are made to the information herein, the edition that is applicable and current will be indicated in the latest System/360 and System/370 SRL Newsletter (GN20-0360). This is a reprint of SH20-1043-5, incorporating changes released in the following Technical Newsletter: SN20-9045 (dated October, 1973) Copies of this and other IBM publications can be obtained through IBM branch offices. © Copyright International Business Machines Corporation 1971, 1972, 1973, 1975 PREFACE This publication contains detailed information necessary to implement three IBM program products: CICS/DOS-ENTRY, CICS/DOS-STANDARD, and CICS/OS-STANDARD V2. It provides system programmers, system analysts, and system administrators with information that is primarily independent of the operating system involved; for example, the use of CICS macro instructions to selectively generate CICS management programs and service programs and selectively prepare system control tables and service tables. It is assumed that the reader of this publication has some knowledge and/or experience concerning the Basic Telecommunications Access Method (BTAM) or has access to persons with such knowledge and/or experience. This publication should be used in conjunction with the appropriate CICS Operations Guide when generating CICS and when preparing the system tables that describe the environment CICS is to support. Throughout this publication, parentheses are used in the notation of CICS macro instructions to indicate those operands where more than one applicable parameter can be specified with a single use of the operand. Where parentheses are not used, only one parameter at a time can be specified as part of the operand. An asterisk in (card) column 72 indicates that the macro instruction is continued on the next line (card). The first operand on a continuation card must begin in column 16. The words "transaction" and "task" have the same connotation in CICS and are used interchangeably throughout this publ.ication; the processing of a transaction may involve the execution of one or more "programs". For further information concerning CICS, see the following IBM publications: General Information Manual (GH20-1028) Application Programmer's Reference Manual (SH20-1047) Terminal Operator's Guide (SH20-1044) Operations Guide (CICS/DOS) (SH20-1034) Operations Guide (CICS/OS) (SH20-1048) Logic Manual (CICS/DOS-ENTRY) (LY20-0712) Logic Manual (CICS/DOS-STANDARD) (LY20-0713) Logic Manual (CICS/OS-STANDARD V2) (LY20-0714) All references to CICS/OS and CICS/OS-STANDARD in this publication are references to the CICS/OS-STANDARD V2 system. Note: Information in this publication concerning TCAM is applicable only to the CICS/OS system. Information concerning 3735 support is not applicable to CICS/DOS-ENTRY. In troduction. • • • 1 General Description •••• The Real-Time System Environment. Real-Time System Programming • • Preparing the System. • • • System Generation • • • • System Table Preparation. • • • • • System Maintenance. • • • • System Data Set Considerations. User Data Base Considerations • . • • • User Extrapartition Data Sets User Exits. • • • • • • •.• Executing the System. • • • • • Job Control • • • • • System Initialization • Terminating the System • • Process ing Du mp Dat a Sets 3 3 3 4 4 5 5 6 7 9 10 10 10 11 11 11 System Generation . • • • General Description • • • Initialization of System Generation • Control System Operational Group (CSO) • • Control System Service Group (CSS). Control System Dummy Group (CSD). • Control System utility Group (CSU). Control System Management Programs. Task Control Program (KCP). • • • Storage Control Program (SCP) • . Program Control Program (PCP) Program Interrupt Control Program (PIP) Interval Control Program (ICP). • Dump Control Program (DCP). • • • Terminal Control Program (TCP). • Pile Control Program (PCP). • • • Transient Data Control Program (TDP). • Temporary Storage Control Program (TSP) Common System Area (CSA) • • • • • • Master Terminal Program (MTP) • • • Dynamic Open/Close Program (OCP). • • • • • Graphic Attention Program (GAP) • • • ••• High-Level Language Support Group (HLL) • • • • Terminal Dependent Control Program (TDCP) • • • • Asynchronous Transaction Processing Group (ATP) Termination of CICS/DOS System Generation • • • • Generation of CICS/OS Data Language/I Facilities • • • • • Defining PSB's and PCB's • • • • • • • • • • • • Defining PSB and DMB Directories During CICS Generation • • 13 13 19 23 24 25 25 26 26 27 28 29 29 31 32 38 39 41 42 42 43 43 43 44 44 44 45 45 46 System Table Preparation • • • • • • • • • System Initialization Table (SIT) • • • • Terminal Control Table (TCT). • • • • • • • • • • • • • Establish Control section for Terminal Control Table. • specify Data set Control Information. • • • Describe Communication Lines. • • • • • • • • • • Describe Terminal Types • • .• • • • • • • • • • • Define Digital Response Messages for 7770 Audio Response Unit Specify End of Terminal Control Table • • • • • • • Terminal Control Table Example. • • • • • File Control Table (PCT). • • • • • • • • • • • • • Establish Control Section for Pile Control Table. • Describe Data Set for Pile Management • • • • • • • 48 48 53 55 56 61 70 76 77 77 80 82 82 ,/ Describe Cross-Index Data Set Record • • • • Define Header of Segmented Record • • . • • Describe Each Segment of a Segmented Record Describe Segment Sets • • • • • • • Specify Last Segment Set. • • • • • • • • . . • • • • • Speci fy End of File Control Table • • • • • Create Superset ISAM Logic Module (CICS/DOS Only) • • • • • File Control Table Example. • • • • • • • • • • • • Destination Control Table (DCT) • . • • • • • • . • Establish Control Section for Destination Control Table • Specify Data Set Control Information • • Specify Extrapartition Destinations ..•. Specify Intrapartition Destinations. • • ••• Specify Indirect Data Destinations. • • . . • • • • • • Terminate Entries for the Destination Control Table • . Nonresident Extrapartition Data Set Definition. Destination Control Table Examples. • • • • • Program Control Table (PCT) • • • • • • • • • • . • • • Establish Control section for Program Control Table Specify Transaction Control Information Specify End of Program Control Table • • Program Control Table Example • • • • • • Proce ss ing Program Table (PPT). • • • • • • • • • Establish Control section for Processing Program Table. Describe Processing Programs. • • • . Specify End of Processing Program Table • Processing Program Table Example. • • • • • System Service Tables • • • • • • • • • • • • • • Sign-on Table (SNT) • • • • . • • Terminal List Tables (TLT) • • • System Programming Considerations • • • • • • Creating User Exits for CICS Management Programs. Creating a Terminal Error Program (DFHTEP) • • • • Terminal Abnormal Condition Line Entry (TACLE). DFHTEP Programming Considerations • • • • DFHTEP Alternate Interface (CICS/OS Only) 7770 32-Second Timeout Considerations. • • • • writing a Transaction to IPL the System/7 • 2260 Compatibility for the 3270 • • • • • . CICS Table Preparation for 2260 Compatibility 2260 Model-Dependent Data Stream • • Screen Techniques • • • • • • • • • Start of Message Indicator (SMI). • New Line Symbol (NL).. •••• Line Addressing • • • • •• • • 2848 Lock Feature • • • •• • • • • 2845/2848 Tab Feature • • ••• Initiating Transactions 3735 Programming Considerations • System Generation • • • • • • • Terminal Control Table Preparation. Inquiry Mode. . • • • • • • • • • • CICS/TCAM Interface Considerations. • TCAM Application Program Interface. • • CICS/TCAM Interface • • • • • TCAM Device Considerations. • TCAM User Exits. • • • • ••• CICS/TCAM start up • • • • • • • CICS/TCAM Abend/Restart • • • • • • .. CICS/TCAM Termination • •• • • .. System Administration.. • ••• Real-Time System Administration System Control Functions. • • • Master Terminal • • • • • • • • Date and Time of Day Control. System statistics • • • • • • . 87 89 89 90 90 91 91 91 93 94 92 97 98 99 100 100 100 104 105 105 106 107 108 108 108 \ 109 109 110 110 113 116 116 120 120 121 129 129 129 130 131 132 132 135 135 135 135 135 136 137 137 137 137 137 138 139 146 148 150 151 151 152 152 152 152 156 157 Dynamic Open/Close Function • • Open Data Sets (OPEN) • • • • Close Data Sets (CLOSE) • • • Switch Dump Data Sets (SWITCH) Con trol System Messages • • • • Appendix Appendix Appendix Appendix Appendix Appendix Appendix A: B: C: D: E: F: G: Index • • • • • • • • • •• • • Required Entries to CICS Control Tahles. Examples of Terminal Control Table Preparation • CICS/TCAM Program Interrelationship. Terminal Control Table Configurator. • • File Control Table Configura tor. • • • • CICS Macro Instructions • • • • • • • • • Examples of User-Written Transactions • • 158 159 161 162 162 176 179 190 194 199 200 211 217 The IBM Customer Information Control System (CICS) is a multi-application data base/data communication interface between OS or DOS and user-written application programs. Applicable to most online systems, CICS provides many of the facilities for standard terminal applications: message switching, inquiry, data collection, order entry, and conversational data entry. Functions performed by CICS include: • • • • • Control of a mixed telecommunications network Concurrent management of a variety of programs Controlled access to the data base Management of resources for continuous operation Prioritization of processing By eliminating many of the development requirements for such functions of a real-time control system, CICS allows programmers to concentrate instead on implementing applications, dramatically reducing implementation time and cost. Functions needed to support a data base/data communication system and standard terminal applications are provided by the following CICS management programs: • Task Management - Provides its own dynamic multitasking facilities necessary for effective, concurrent transaction processing. Functions associated with this facility include priority scheduling, transaction synchronization, and control of serially reusable resources. This CICS facility is in addition to the multitasking or multiprocessing facilities of the host operating system. • Storage Management - Controls main storage allocated to CICS. Storage acquisition, disposition, initialization, and request queuing are among the services and functions performed by this component of CICS. • Program Management - Provides a multiprogramming capability through dynamic program management while offering a real-time program fetch capability. • Program Interrupt Management - Provides for the interception of program interrupts by CICS to prevent total system termination. Individual transactions that program check are terminated by CICS with a dump (if Dump Management is used), thus preventing the entire CICS partition/region from terminating. Under CICS/OS, supports the runaway task control function of CICS Time Management. • Time Management - Provides control of various optional task functions (system stall detection, runaway task control, task synchronization, etc.) based on specified intervals of time or the time of day. • Dump Management - Provides a facility to assist in analysis of programs and transactions undergoing development or modification. Specified areas of main storage are dumped onto a sequential data set, either tape or disk, for subsequent offline formatting and printing using a CICS utility program. 1 • Terminal Management - Provides polling according to user-specified line traffic control as well as user requested reading and writing. This facility supports automatic task initiation to process new transactions. Optionally, the user can request that certain lines be under control of TCAM (rather than BTAM) in which case polling and other network control functions are performed by the Message Control program (MCP) residing in another partition/region. The testing of application programs is accommodated by the simulation of terminals through sequential devices such as card readers, line printers, disk, tape, etc. • File Management - Provides a data base facility using direct access and indexed sequential data management. This function supports updates, additions, random retrieval, and selective retrieval (browsing) of logical data on the data base. Optional access to the Data Language/I (DL/I) facility of the IBM Information Management System (IMS/360) is also provided under CICS/OS. Use of DL/I requires the installation of the IMS/360 Version 2, Modification Level 2 (or later) Data Base System (5734-XX6). • Transient Data Management - Provides the optional queuing facility for the' management of data in transit to and from user-defined destinations. This function facilitates message switching, data collection, and logging. • Temporary Storage Management - Provides the optional general purpose "scratch pad" facility. This facility is intended for video display paging, broadcasting, data collection suspension, conservation of main storage, retention of control information, etc. In addition to these management functions, CICS provides system service programming to identify terminal operators, to give dynamic control of the entire system to a master terminal, to display real-time system statistics, to intercept abnormal conditions not handled directly by the operating system, and to end operation by gathering summary statistics, closing data sets, and returning control to the operating system. 2 The real-time data base/data communications (DB/DC) environment is characterized by a number of factors which distinguish it from the conventional batch processing environment. For example, the system programmer must be aware of considerations inherent to the real-time system environment, such as: • Transactions are not batched by type, but arrive randomly. o Online data storage is expensive, so that storing redundant subsets of data is an undesirable approach to providing the data access required by other applications and programs. • Sorting and scanning data prohibits the rapid access needed by a single transaction. • A number of transactions can simultaneously try to change the same data. • A terminal user may attempt an unauthorized access of confidential data. • A (software) '---- recovery capability is required to prevent data losses. The real-time data base/data communications environment (DB/DC) differs from the traditional batch processing environment primarily in the amount and types of concurrent activities that are likely to occur within the system at a given time. Whereas a batch processing system schedules each application independently and provides data support unique to each application, a DB/DC system controls many transactions arriving on a random nonscheduled basis and provides a data base (with integrated data) supporting each application. In the conventional batch processing environment, the application programmer plans a series of runs to edit batches of input transactions, update master files, and write output reports. To optimize total run time and streamline the cycle, he must concentrate on careful manipulation of data. In accomplishing this, the data becomes intricately tied to his program logic and is of little value in other applications. CICS solves many of these complexities by managing data centrally in a data base on behalf of all applications. This relieves the application programmer of system management considerations, allowing him to concentrate instead on the application, and shifts the responsibility for an integrated data base to the system programmer. As an effective interface, the system programmer must organize all the data and optimize its storage, making tradeoffs between cost of storage, performance, and service level according to management guidelines. The DB/DC system has a common data set (data base) manager, and usually provides the system programmer with specialized interfaces. 3 CICS is modularly designed to allow the user to configure a data base/data communications system appropriate to his needs. While some of the system components are essential, many are optional and can be configured into the system under user control. CICS modularity allows the user to: 1. 2. 3. 4. 5. Include or omit functions or components. Replace or extend a function or component. Evolve and expand the support of the user's environment. Conduct maintenance on a component level. Bring the most current individual components together at execution time to support the desired environment. To assist the user in tailoring the system to meet his needs, source code is distributed to the user which must be assembled to provide the specific functions and components the user desires. The detailed instructions in preparing the system from the distributed machine-readable material is contained in the appropriate CICS Operations Guide. SYSTEM GENERATION CICS provides a system generation facility whereby the user can define what CICS-provided functions or components he desires as well as certain variables he wants included. The system is then generated according to that description. CICS provides ten executable management programs which can be selected and generated by the user to perform the following functions: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. Task Management Storage Management Program Management Program Interrupt Management Time Management (Interval Control) Dump Management Terminal Management File Management Transient Data Management Temporary Storage Management In addition to the managment programs, a number of system service programs (which run as application programs) can be generated. The service functions which these programs provide are: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. Sign on/sign off Master terminal Supervisor terminal Operator terminal System statistics Abnormal condition handling Terminal abnormal condition handling Asynchronous Transaction Processing System termination Terminal test Time of day control Two utility programs can also be generated. These are the Dump Utility program for formatting and printing the dumps (produced during execution), and the High-Level Language Preprocessor which is used to prepare the ANS COBOL and PLII application programs for execution under 4 CICS. In the CICS/DOS systems, a special linkage-editor facility is also generated for use in preparing the object modules for execution. An optional user-defined Common Work Area (CWA) is provided as an extension of the Common System Area (CSA) in static main storage. This work area is available for the use of all user-written programs and can be used to contain user-defined data (which is not to be altered by CICS) such as tables, accumulators, and sequence numbers. The length of the CWA must be specified during system generation. The details concerning how to use the DFHSG macro instruction to generate the system are provided in the System Generation section of this manual. The necessary JCL is detailed in the appropriate CICS Operations Guide. SYSTEM TABLE PREPARATION This feature gives the user flexibility in CICS is table-oriented. describing his terminal, data base, and queuing environments. It allows him to describe several versions of existing environments, simplifying evolution and growth to new environments. Because of the table orientation, the user need change only that part of his environment that needs to be changed. All tables are specified and constructed by the user with assistance provided by CICS. These tables are declarative in nature and are used by CICS to control the environment according to the design criteria established by the user. Major tables are used to describe System Initialization and terminal, data set, and queuing environments. Other tables identify user programs, transactions, operators, etc. Detailed information on the contents of these tables and the macro instruction used to prepare them are provided in the section "System Table Preparation". The Process Control Information field (PCI) is an optional user-defined terminal work area which is provided as an extension of the Terminal Control Table (TCT) in static main storage. The PCI is associated with a particular TCT terminal entry (TCTTE) and is available for the use of all user-written programs that are logically attached to that TCTTE. The-PCI can be used to contain user-defined data (which is not to be altered by CICS) such as user statistics and sequence numbers. The PCI is a variable-length field (0-255 bytes) which is specified during system generation. For CICS/OS, PCI's of fixed length (15 bytes) may also be specified during system generation for the purpose of upward compatiblity from CICS/OS-STANDARD V1 to CICS/OS-STANDARD V2. The length of the PCI is specified during preparation of the TCT. SYSTEM MAINTENANCE Because CICS is both modular and table-oriented, maintenance is simplified considerably. If a change in the user's environment should occur which, in turn, requires a change to a CICS management program and/or table, only the affected program or table needs to be generated again~ This, of course, is also true of any corrections that must be applied to the system. To make a correction to a particular program only the source code for that program needs to be updated, using the appropriate operating system update facility, and then reassembled and link edited. 5 SYSTEM DATA SET CONSIDERATIONS The access methods and record content of the system data sets are predBfined within CICS. Any required formatting is performed by CICS during system initialization or by the maintenance functions. For space considerations and requirements, see the appropriate CICS Operations Guide. The system data sets (files) • • • • • • include: Real-Time Relocatable Program Library Real-time Pre-Located Program Library Transaction Rollout Data Set Dump Data Set Intrapartition Data Set Temporary Storage Data Set The Real-Time Relocatable Program Library contains all user programs and CICS programs to be loaded and executed in real-time including the control system itself and certain user-prepared System Control Tables. The library contains program text and, where applicable, a relocation dictionary for each program. The contents of this library are asynchronously fetched into main storage for real-time execution in the CICS/DOS-STANDARD and CICS/OS-STANDARD systems by the Program Control Program. This library is not used for real-time execution in the CICS/DOS-ENTRY system. For the CICS/DOS-STANDARD system, the Real-Time Relocatable Program Library is a user allocated extent. Programs are prepared for this library by DFHLINK. For the CICS/OS-STANDARD system, the Real-Time Relocatable Program Library is a standard partitioned data set. Programs are prepared for this library by the as Linkage Editor. CICS/OS users may concatenate other private libraries to this library. The CICS Real-Time Pre-Located Program Library is used in the CICS/DOS-ENTRY system to retain the nonresident application programs during real-time execution. All application programs, so designated by the user, are loaded into main storage by the CICS System Initialization program and are written into the library for subsequent fetch and refresh. The Processing Program Table in main storage serves as the directory for this library. The Transaction Rollout data set (file) is used in the CICS/DOS-ENTRY system to retain certain transaction information in order to support conversational interaction with a terminal. The types of transaction information that may be expected to be rolled into this data set include: 1. 2. 3. 4. 5. 6. 6 Task Control Area Transaction Work Area User-acquired work areas File, Temporary storage, Transient Data input/output areas, work areas, and control areas Register storage areas Loaded programs The optional dump data set is used by the Dump Control program to record dumps of transactions within the system. It is a sequential data set located on either magnetic tape or direct access and can be subsequently formatted and printed by the CICS Dump utility program. CICS provides the capability to open/close the active dump data set during the real-time ~xecution of the system. Optionally, the user can define two dump data sets (DFHDMPA and DFHDMPB), alternating between them during real-time execution of CICS. The Intrapartition data set is a system option and is used for the queuing of user data and, optionally, CICS data by the Transient Data Centrol program (CrCS's general purpose queuing facility). Data, as requested, is stored chronologically into this data set according to previously identified symbolic destinations for subsequent retrieval when all applicable system conditions and facilities are in the appropriate status. This data set is reusable and is required for applications such as message switching, broadcasting, order distribution, etc. The record format for this data set is standard System/360 variable length. The Temporary storage data set is a system option, and should be allocated, if required, by the user as general purpose scratch pad storage for use by the Temporary storage Control program. User data, as requested, is stored into this data set under a dynamically-provided symbolic identification for subsequent retrieval and release (when appropriate). This data set is intended for applications such as broadcasting, video display paging, transaction suspension, main storage conservation, etc. This data set consists of variable-length records within a preformatted fixed-length DAM data set record and is required if the "time ordered" automatic task initiation feature of CICS is generated. Any tasK which requests the use cf Temporary storage when space is not available will be suspended until adequate space is freed 1:y another task. USER DATA BASE CONSIDERATIONS CICS File Management allows the user a high degree of flexibility when defining the structure of his data base. Individual data sets (files) within the data base can be accassed under control of the Direct Access Method (DAM) or the Indexed Sequential Access Method (ISAM). The following optional CICS features allow certain variations in data organizaticn to provide the user with the most efficient data base structure suitable to his environment. CICS stores data in and retrieves data from the user's data sets. It is possible to retrieve an individual record or selected segments of an individual record. A segmented record is one in which the components of the record have been identified and grouped according to frequency of use, functicn, and logical relationship. The identifiable groups are called segments. Some segments are in all records, such as those that contain identification or major record control fields. Other segments apply only in certain records. The primary reason for 7 segmenting records is to ccnserve main storage, or, in the case of variable-length records, to conserve direct access storage. If additienal infcrmation is to be included in a segmented record, either a new segment is created or an existing segment is altered. In either case, only the affected segment descriptiens need be changed and the new programming added to support the change. Symbolic references to unchanged segments are not affected. Adding information to a fixed format record cculd require considerably more programming than using the segmented record approach. The user must define the record segments to CICS. In addition, each record to be retrieved in segments must have control information in the first segment which is used to indicate the presence or absence of each segment. A segment should contain logically related data so that only selected segments are required to satisfy the processing requirements of a transaction. A transaction that uses only selected record segments requires less main storage for its processing. The user, in selecting those segments necessary for processing transaction groups, identifies them to CICS as a part of the data set (file) definitions in the File control Table. Such a group of segments is a segment set. A segment set can include a single segment, a number of segments, or all segments of a record. When a request is made to File Control identifying a segment set in the request, CICS always returns the header control segment plus the segments in that set. Segmented records can be used with either DAM or ISAM data set organizatiens. For further details concerning segmented records, see "Data Base Considerations" in the fl£~ !EElifg1i£1! R1:Qg!~!!1!!1~~§ B~!§~enc§ Ma1!Y~l (SH20-1047). CICS provides deblecking of logical records which are blocked and written on a direct access (DAM) data set. This service is provided for both fixed- and variable-length records. The data set must be created according to standard System/360 record formatting conventions. CICS (optionally) allows the use of cross-index data sets to access another data set which may be the main data set or another level of index data set. If a record retrieved from a cross-index data set indicates multiple entries in the main data set, information is returned to the user-written application ~rograms to be used in selecting the a~propriate main data set entry. When the cross index does not indicate rrultiple entries in the main data set, the File Centrel ~rogram reads the requested re90rd from the main data set. Organization of the cross-index data set may be either indexed sequential or basic direct access. The index record contains, in additien to the information used to find it, the search argument for the record on the data set which the index data set references. The index record may contain any other information desired by the user. !he location of the search argument, its length, and the data set identification for the referenced data set are supplied to CICS as part of the data set definitions in the file Central Table. For further details concerning indirect accessing, see "Data Base Considerations" in the £1£~ AEBlifE1iQll Rf9gf~!!1!!1~~~§ E§!~I~n£§ ]~1!Y~! (SH20-1047). 8 QQ~ IS!~ Y££1ab1§-L§ng!h ggcord§ The CICS/DOS systems support the retrieval and static update (no length variation) of variable-length logical records within fixEd-length blocks under an ISAM organization. These pseudo-variable blocks must conform to System 360/370 variable-length record format conventions. That is, the first four bytes must contain the block length of the form LLbb. Since all blocks are fixed length, this value will be the same for all blocks. Each logical record within the block must reflect the length of the record in the first four bytes (LLbb). A logical record may not be continued onto the next block. The first byte of any unused portion of a block must contain a hexadecimal FF. The addition and deletion of records on a DOS ISAM variable-length record data set must be handled by the user in an offline batch environment. When creating the data set, it must be defined as fixed unblocked, and the key for each block must be the same as the last logical record in that block. The block size must be an even number of bytes. All records must reside in the prime data area; no overflow records are allowed. For details concerning the CICS definition of a DOS ISAM variable-length record data set, see the discussion of the File Control Table in the section "System Table Preparation". Optional access to the Data Language/I (DL/I) facility of the IBM Information Management System (IMS/360) requires the installation of the IMS/360 Version 2, Modification Level 2 (or later) Data Base System (5734-XX6) • As CICS is initialized, an IMS batch job is attached (via OS) as an subtask of CICS in much the same fashion as a regular IMS system is executed as an as job. All data sets required for a batch IMS job are required for access to DL/I under CICS. as USER EXTRAPARTITION DATA SETS Extrapartition data is the name given in CICS to transient stream data which is corning into or going out of the data base/data communication system environment. This data is usually coming from or going to high-speed magnetic devices and is characterized by, but not required to be, blocked, variable-length stream data. The extrapartition disposition facility is intended for use with the following types of data and applications: 1. 2. 3. 4. 5. Message logging Transaction logging Reconstruction records and information Data collection Data entry and all other output stream data intended for subsequent processing (usually offline). The user defines this data consistent with his requirements and facilities. The extrapartition acquisition facility is intended for limited stream (batch-like) data processing in the data base/data communication environment. 9 USER EXITS Exit routines may be provided by the user to extend or add functions to CICS management programs. All CICS management program exits are included at the source level and are assembled with the management program during system generation. The user exits provided for are as follows: Task Control (DFHKCP) Before request analysis Before task dispatch Storage Control Before request analysis (DFHSCP) Program Control (DFHPCP) After program load Interval Control (DFHICP) Before request analysis At expiration of time interval Terminal Control (DFHTCP) Before transaction attach Before output event initiation After input event completion File Control (DFHFCP) Before service request analysis Before output event initiation Before input event initiation After input event completion Transient Data Control (DFHTDP) Before service request analysis Before output event initiation After input event completion Temporary Storage Control (DFHTSP) Before service request analysis Before output event initiation After input event completion For further information concerning user exits, see the discussion of the individual CICS management programs in the section "System Generation"; see also the section "Creating User Exits for crcs Management programs". crcs is designed to bring together at execution time the most current individual components to support the environment requirements present at that time. Through the use of the appropriate System Initialization Table and the necessary overrides, any combination of crcs management programs and tables may be loaded and executed. Thus, the user may have a test module and a standard module of any of the various crcs management programs and tables (only one of which may be in main storage for a given execution). He can then execute crcs using the test module; if it doesn't work satisfactorily, he can execute crcs again using the standard module that he knows is working. JOB CONTROL The job control language (JCL) statements needed to execute crcs varies not only with the operating system environment desired but also with the choice of crcs functions and types of data organization. 10 Specific examples of JCL can be found in the appropriate CICS operations Guide. In a CICS/OS environment, a procedure may be set up so that execution of a "standard" system requires a minimal amount of JCL to be submitted as a job. Only for execution of a test system or for other than the defined standard system would a larger JCL deck be necessary. In a CICS/DOS environment, the user can elect to use Single Program Initiate (SPI) to activate CICS with a minimal amount of JCL. SYSTEM INITIALIZATION The flexibility in specifying which CICS management programs and tables are to be loaded for a particular execution is accomplished through the System Initialization program (DFHSIP). This program is named on the EXEC card in the JCL and is used to accomplish the following: 1. 2. 3. 4. 5. 6. 7. Load the specified System Initialization Table. Request any overrides that are desired. Load the requested CICS management programs and tables. Initialize tables and areas. Open all required data sets. Load any resident application programs. Pass control to the Terminal Control program (which then executes as the initial task) • System termination is provided for through use of the master terminal transaction (CSMT) and several CICS-provided programs (DFHMTP, DFHSTP, DFHSTKC, DFHSTTD, DFHSTTR). The Termination program (DFHSTP) allows normal completion of transactions currently in progress, prepares statistics, closes data sets, and optionally, takes a dump before exiting to the operating system. A detailed description of the use of the transaction CSMT in terminating the system is found in the appropriate CICS Operations Guide. The dump data set produced by the Dump Management facility of CICS is a sequential data set, on either magnetic tape or disk, which exists in a semi-processed form. The CrCS-provided utility program (DFHDUP) is used to produce the final formatted dump. The user can define an alternate as well as a primary dump data set. unless the user chooses to provide an alternate dump data set, DFHDUP must be used only when CICS is not in real-time execution. That is, if the user wishes to print the dump data set, he must first terminate CICS, run DFHDUP, then reinitialize CICS. This may satisfy the user who only requires crcs for a part of the day. However, for the user who requires crcs operations for a long period of time, an alternate dump data set may be allocated. Thus, at periodic intervals, the user may request, through the CICS Master Terminal switch function, that CICS begin using the alternate dump data set so that the primary data set can be processed by DFHDUP in another partition/region. When the primary data set has been processed, the user may again "switch" back to the primary data set and then process 11 the alternate data set. This procedure can be repeated any number of times. If tapes are being used, this switching procedure causes the old dump tape to be closed and dismounted, and a new tape to be mounted and opened. If the user switches to the alternate dump data set, then fails to process the primary data set before again switching, the dumps on the primary data set are destroyed by the CICS Dump Management facility when new dumps are recorded. A detailed description of the use of the Dump utility program is found in the appropriate CICS operations Guide. 12 Generation of CICS/DOS is accomplished in three stages: stage I consists of the assembly of the CICS/DOS generation macro instructions and the preparation of the input for stage II; stage II consists of the assembly of the CICS/DOS system; and stage III consists of the link editing of the non-real-time system and tables used by the System Initialization program to the DOS Core Image Library using the DOS Linkage Editor (LNKEDT) and the link editing of the CICS/DOS real-time system to the CICS/DOS Real-Time Relocatable Program Library (DFHRPL) using the CICS/DOS Linkage Editor (DFHLINK). Generation of CICS/OS is accomplished in a two-stage operation: (1) assembly of the generation macro statements and (2) the running of the job stream produced by this assembly. During the generation of CICS, the user must specify the CICS management programs and system service programs he requires to meet his environmental needs. The specification and naming of the desired programs are accomplished through the use of DFHSG system generation macro instructions, which are processed by the Assembler. The order in which DFHSG macro instructions are specified is not important, except that the first macro instruction specified must be the DFHSG TYPE=INITIAL macro instruction. In the CICS/DOS systems, the DFHSG TYPE=FINAL macro instruction must be the last statement of the system generation input stream preceding the Assembler END statement. DFHSG macro instructions are written in Assembler language and, as all Assembler language instructions, are written in the following format: blank or symbol DFHSG One or more operands separated by commas In this publication, parentheses are used to indicate those operands where more than one applicable parameter (keyword and otherwise) can be specified with a single use of the operand. Where parentheses are not used, only one parameter at a time can be specified as part of the operand; a choice must be made in the case of more than one applicable parameter. Since a blank character indicates the end of the operand field, the operand field must not contain blanks except after a comma on a continued card or after the last operand of the macro instruction. The first operand of a continued card must begin in column 16. The following operands can be included in the DFHSG macro instruction: DFHSG TYPE=INITIAL, STATUS=FIRST, ASMBLR=Assembler name, OPSYS=(VS1,VS2,number), TRACE=YES,NO, TIMECTL=YES,NO, DSIZE=number, * * * * * * * 13 MPS=YES,NO, JOBNAME=jobname, ACCTID=accounting information, PGMERID='programmer's name', MSGLVL=O,l, DEVICE=2311,2314,3330, CONDCD= ( (code, opera tor) , ••• , (code, opera tor) ) , PRIORTY=nn, MSGCLAS=x, CLASS=jobclass, REGION=(n1K,n2K) , PROCNMS=(procedure names), DL1=YES,NO, ATP=YES,NO, PREFIX=prefix, TCTUA=(V1COMPAT,VARIABLE) DFHSG PROGRAM=CSO, MPS=YES,NO, NSD=number, DEVICE=2311,2314,3330, SVC=number, CAA=appendage suffix, V1CMPAT=YES, TCAMSIP=YES * * * * * * * * ** * * * * * * * * * * * * DFHSG PROGRAM=CSS DFHSG PROGRAM=CSD 14 DFHSG PROGRAM=CSU, DEVICE=(TAPE,2311,2314,3330) * DFHSG PROGRAM=KCP, CONSEC=YES, RUNAWAY=YES, STALCTL=YES, ENQUEUE=YES, OPSECUR=YES, ICPTIME=YES, ICPAUTO=YES, ICPSYNC=YES, SUFFIX=program suffix, XTYPREQ=symbolic name, XDSPCHR=symbolic name, DEVICE= (2311,2314,3330) ** * * * * * * ** * * DFHSG PROGRAM=SCP, XTYPREQ=symbolic name, SUFFIX=program suffix * * DFHSG PROGRAM=PCP, PCPLOAD=YES,NO, LANG=(COBOL,PL/I) , HLLTR=YES,NO, COBOL=(V2,V3,V4,SUBSET) , XFETCH=symbolic name, SUFFIX=program suffix * * * * DFHSG PROGRAM=PIP, SUFFIX=program suffix * DFHSG PROGRAM=ICP, RUNAWAY=YES, ICPTIME=YES, * * * * * ICPAUTO=YES, ICPSYNC=YES, SUFFIX=program suffix, XTYPEEQ=symbolic name, XICEEXP=symbolic name, .DUMMY=YES * * * * * DFHSG PROGRAM=DCP, D"EVICE=TAPE,2311,2314,3330, DEVADDR=nnn, CICSDMP=YES, SUFFIX=pLogram suffix, DUMMY=YES * * * * * DFHSG PROGRAM=TCP, ACCMETH=(BTAM,BSAM,SAM,BGAM,TCAM), DEVICE=(1403,1404,1442,1443,1445,2311,2314,3330, 2501,2520,2540,CRLP,BASD,DISK,TAPE), BTAMDEV=(1030,1050,1050D,1053,1130,1130D,2020,2020D, 2260,L2260,2265,2740,2140D,2740-2,2741C, 2741E,2741DC,2741DE,2760,2770,2770D,27S0,27S0D, 29S0/1,29S0j2,2980j4,3275,3277,L3277,3284, L3284,3286,L3286,3735D,7770,SYSj3,SYS/3D,SYS/7, SYSj7D,Sj360,Sj360D,Sj370,Sj370D,TWX,BISYNC), FEA!URE=(AUTOANSW,AUTCPOLL,BUFFRECV,PSEUDOBIN), ANSWRBK=(EXIDVER,TERMINAL,AUTOMATIC,7770TERM,7770NULL), INI!RL=YES, LOCKF=YES, WRAFLST=YES, BSCOBE= (EBCDIC, ASCII,TRANSCODE) , AUTOTRN=YES, UCTRAN=NO, (EBCDIC,ASCII), CCMEAT=NO, (FORMAT,FULLBUF) , FMT2260=(6X40,12X40,12XSO,15X64), FMT3270= (12X40, 24X80) , CMPT60L=(n1,n2,n3), SMI=user character, TAB=YES,NO, CCNVTAE=(AEE,ABC), XATTACH=symbolic name, XOUTPUT=symbolic name, XINPUT=symbolic name, XTCMIN=symbolic name, XTCMOUT=symbolic name, TCM3270=YES, TCM7770=YES, BMS=YES,NO, SUFFIX=program suffix * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * DFHSG PROGRAM=FCP, CONSEC=YES, FILSERV=(INBA,INIS,tAUPD,ISUPD,BAADD,ISADD,INDIRACC, EXCTL,INSEG,OUTSEG,BABLKNG,VLR,HEXAD,BECAD, ACTAD,IVBR,LOCATE,IBROWSE,DBROWSE) , SUFFIX=program suffix, XTYPREQ=symbolic name, XOUlPUT=symbolic name, XINPUT=symbclic name, XINPUTC=symbolic name, DUMMY=YES * * * * * * * * * * DFHSG PROGRAH=TDP, INTRA=YES,TRANSINIT, EXTRA=(ACQUISITION,DISPOSITION) , SUFFIX=pLogram suffix, * * * * 15 DEVICE=2311,2314,3330, XTYPREQ=symbolic name, XOUTPUT=symbolic name, XINPUT=symbolic name, DUMMY=YES * * ** DFHSG PBOGRAM=TSP, DEVICE=2311,2314,333C, SUFFIX=p~og~am suffix, VIRTUAL=VIRTUAL,REAl, XTYPBEQ=symbolic name, XOU~PUT=symbolic name, XINPUT=symbolic name, DUMMY=YES ** * * ** DFHSG PROGRAM=CSA, WRKAREA=number, SUFFIX=program suffix * * DFHSG PBOGRAM=MTP, TLT=YBS,NO * * DFHSG PROGRAM=OCP DFHSG PROGRAM=GAP DFHSG PROGRAM=HLL, LANG=(COBOL,PL/I) , PL1=(O,F) * * DFHSG PROGRAM=DDM DFESG PROGRAM=ATP, INBUFF=number, OUTBUFF=number DFHSG TYPE=FINAL Table 1 shows the symbolic names and program codes used during CICS generaticn in the specification and naming of CICS management programs and system service programs. 16 ** Table 1 (Part 1 of 2) • Symbolic names and program codes used in system generation RBOG]!.tl B!l1] ~X1:!~Q11£ Terminal Control 3270 Basic Mapping Support Terminal Dependent Control Task Control File Control Program Control Storage Control Dump Control Transient Data Control Common System Area CICS Dummy CSA Temporary Storage Control Interval Control Program Interrupt Dump utility CICS/DOS Linkage Editor Master Terminal programs "- '---- "- Asynchronous Transaction Processor Asynchronous Transaction Read'er Asynchronous Transaction Writer Asynchronous Transaction Queue Purge Dynamic Open/Close Graphic Attention System Service programs Sign-On Sign-Off Field Engineering Control System Dummy programs Transient Data dummy Dump Control dummy File Control dummy Temporary Storage dummy Interval Control dummy Control System Operational programs Abnormal Condition Terminal Abnormal Condition Time Adjustment Transmission Error System Initialization NAl1] ~Ql!] RBQQBAM TY,R] (Note 1) RBQQ]AM (Note 2) DFHTCP (Note 6) DFHBMSMM TCP TCP Control program Service program DFHTDCP DFHKCP DFHFCP DFHPCP DFHSCP DFHDCP Note 9 KCP FCP PCP SCP DCP Service Control control Control control Control program program program program program program DFHTDP (Note 6) DFHCSA (Note 6) DFHDCSA DFHTSP (Note 6) TDP CSA Note 10 TSP Control Control Control Control program program program program DFHICP (Note 6) DFHPIP (Note 6) DFHDUP DFHLINK DFHMTPA DFHMTPB DFHMTPC DFHMTPD DFHMTPE DFHMTPF DFHATP ICP PIP CSU INITIAL MTP MTP MTP MTP MTP MTP ATP Control Control Service Service Service Service Service Service Service Service Service program program program program program program program program prog ram program program DFHRD1 DFHRD2 DFHWT1 DFHWT2 DFHAQP ATP ATP ATP ATP ATP Service Service Service Service Service program progra m progra m program program DFHOCP DFHGAP OCP GAP Service program Control program DFHSNP DFHSFP DFHFEP CSS Note 3 Note 3 Note 3 Service Service Service Service program program program program DFHTDPDY DFHDCPDY DFHFCPDY DFHTSPDY CSD Note Note Note Note Control Control Control Control Control program program program program program DFHICPDY Note 4 Control program DFHACP DFHTACP CSO Note 5 Note 5 Control program Service program Service program DFHTAJP DFHTEP DFHSIP Note 5 Note 5 Note 5 Service program Service program Control program (Note (Note (Note (Note (Note 6) 6) 6) 6) 6) 4 4 4 4 17 Table 1 (Part 2 of 2). Symbolic names and program codes used in system generation ,RROGBAl1 BAM.£; SYMBOLIC (Note-'f System Termination System Statistics programs DFHSTP DFHSTTR DFHSTTD DFHSTKC DFHTRP DFHTRPDY DFHRWP70 DFHCAA70 Note Note Note Note Note Note Note Note 5 5 5 5 5 5 5 5 Service program Service program Service program Service program Service program Service program Feature program Appendage DFHDEB70 DFHDLI DFHDLIDY DFHDLA DFHDLQ DFHDLE Note Note Note Note Note Note 5 11 SVC Feature Feature Feature Feature Feature Trace programs 7770 Read/Write 7770 Channel/Abnormal End Appendage 7770 SVC DL/I Interface DL/I Interface dummy DL/I Initialization DL/I Application DL/I CALL Execution High-Level Language programs PL/I-OPT Entry Interface PL/I-F Entry Interface PL/I Interface CICS Preprocessor NAl1~ ,RROGBAl1 (Note 2) 4 11 11 11 HLL DFHPL10I DFHPL11 DFHSAP DFHPRPR Note Note Note Note ~QQ~ RROGBAl1 !X£~ program program program program program Feature program 7 7 7 8 Feature Feature Feature Feature program program program program The symbolic name is the name supplied to the linkage edit procedure. The program code. is the keyword parameter used in the system generation macro instruction (DFHSG). These programs are included in CICS if the user specifies the system service programs with a DFHSG PROGRAM=CSS macro instruction. These programs are included in CICS if the user specifies the control system dummy programs with a DFHSG PROGRAM=CSD macro instruction. These programs are included in the generation of CICS if the user specifies the control system operational programs with a DFHSG PROGRAM=CSO macro instruction. A two-character suffix (other than IDY' and 'NO' which are reserved) may be appended to these symbolic names. Suffix 'DY' is reserved for dummy programs. These programs are included in CICS if the user specifies the high-level language feature with a DFHSG PROGRAM=HLL, LANG=PL/I macro instruction. PLI=(O,F) causes appropriate program selection. This program is included in CICS if the user specifies the high-level language feature with a DFHSG PROGRAM=HLL, LANG=(COBOL,PL/I) macro instruction. This program is included in CICS if the user specifies BTAMDEV=1030. 18 For CICS/OS, this program is given control by the System Initialization program (DFHSIP) via an OS XCTL macro instruction to function as the Request Block (RB) for CICS. These programs are included in CICS if the user specifies DL1=YES in the DFHSG TYPE=INITIAL maCIO instruction. The system use of of the can te DFESG TYPE=INITIAL maCIO instruction must be the first of the generation maCIO instructions. Procedures developed from the this maCIO instruction can be reused for subsequent generations entire system or fOI parts of the system. The following operands included in this maCIO instruction: DFHSG TYPE=INITIAL, STA'IUS=FIRST, ASMELR=Assembler name, OPSYS=(VS1,VS2,number) , TRACE=YES,NO, TIMECTL=YES,NO, DSIZE=number, MPS=YES,NO, JOENAME=jobname, ACC'IID=accounting information, PGMERID='programmer's name', MSGLVL=O,1, DEVICE=2311,2314,3330, CCN~Ct>= «code,operator) , ••• , (code,operator», PRIORTY=nn, MSGCLAS=x, CLASS=jobclass, REGION=(n1K,n2K) , FRCCNMS=(procedure names), DL1=YES,NO, ATP=YES,NO, PREFIX=prefix, TCTUA=(V1CMPAT,VARIABIE) * * * * * * ** * * * * * * * * * * * * * * TYPE: The TYPE=INITIAL operand specifies that this is the initial macro instruction in a CICS system generation run. S'IATUS: In the CICS/DOS systems, the STA'IUS=FIRST operand must be used during the very first CICS/DOS system generation. The presence of this o~erand results in the generation of the CICS/DOS Linkage Editor and Library Maintenance pIogram (DFHLINK). This program is used to place all CICS management and application pIograms in the Real-Time Relocatable Program Library (DFHRPL). Once the generation of DFHLINK is complete, it is used to format the Real-time Relocatable Program Library. The user must provide a label set for DFHNPL in the partition standard label definitions and include the DSIZE operand. In the CICS/OS system, the STATUS=FIRST operand is used to cause the CICS cataloged procedures to be placed in SYS1.PROCLIB. If TCTUA=V1COMPAT is specified, jobs are created during stage II of system generation that modify the DFHTCT macro instruction and DFHTCT symbolic storage definiticn (DSECT) to provide upward compability from CICS/OS Version 1 to CICS/OS Version 2. 19 ASMBLR: This operand is used to identify the name of the Assembler to be used during stage II of system generation and to produce the proper JCL. The default is ASMELR=ASSEMBLY for CICS/DOS and ASMBLR=IEUASM for CICS/OS. For CICS/OS, if the first three characters of the Assembler name are 'lEV', Assembler H is assumed and only one work data set is allocated (SYSUT1). Otherwise, Assembler F is assumed and three work da'ta sets are allocated (SYSUT1, SYSUT2, and SYSUT3). TRACE: The TRACE=NO oFerand is used to indicate that the optional trace function is not to be used during execution of CICS. The default is TRACE=YES. TIMECTL: The TIEECTL=N_O operand is used to indicate that none of the optional time management functions are to be included in any of the CICS management programs. If TIMECTL=NO is specified, the macro instructions of the Interval Contrcl program (ICP) are not expanded and warning messages appear on the assembly listings of the affected CICS management programs. The time management functions excluded include runaway task centrol and support of ICP macro instructions. The default is TIMECTL=YES. DSIZE: Applicable only to the CICS/DOS systems, this operand is used to specify the number of directory tracks to be used for the Real-Time Relocatable Program Library (created if the STATUS=FIRST operand is included). The default is DSIZE=2. MPS: Applicable only to the CICS/DOS systems, this operand is used to indicate whether the DOS system for which CICS is being generated has multiprogramming system (MPS) sUFPort. The default is MPS=YES. JOENAME: This oFerand is used to specify a JCL (OS) or job control (DOS) jetname for systems generation. The default name is CICS. The entire jotname is a concatenation of the jobname operand (truncated to four positions), program name, and suffix. (Example: JOBNAME=NEW, ~ROGRAM=KCP, SUFFIX=01.) The jobname would be NEWKCP01. For the default jotname operand, PROGRAM=KCP, SUFFIX=03. The jotname would be CICSKCPO. The combined jobname will be truncated to eight positions. ]Q!~: The program name for DFHSG TYFE=INITIAL is provided by the system as GEN. Therefore the default jobname is CICSGEN. ACCTID: Applicatle only to the CICS/OS-ST~NDARD system, this operand is used to specifJ the JCL accounting information for the system generation procedure. The default is ACCTID=CICSGEN. PGMERID: Applicable only to the CICS/OS-STANtARD system, this operand is used to specify the programmer's name to be placed in the JCL. The name must be enclosed in quotation marks and should not exceed 20 Fositions. The default is PGMERID='SYSTEM PROGRAMMER'. MSGLVL: Applicable only to the CICS/OS-STANDARD system, this operand is used to specify the message level desired for the JCL during stage II. The default is MSGLVL=O. 20 DEVICE: Applicable only to the CICS/DOS systems, this operand specifies for DFHLINK the device type on which the Real-Time Relocatable Program Library is resident. This operand is propagated to the DEVICE= parameters of DFHSG TYPE=CSO and TYPE=KCP. The default is 2311. ]ot~: The Relocatable Program Library (DFHRPL) must be on the same dEvice type as SYSRES. For the DOS-ENTRY system, the Transaction Rollout File (DFHTRF) and the preallocated Program Library (DFHPPL) must also be on the same device type. OPSYS: Applicable only to the CICS/OS STANDARD system (release 2.3 or later) this operand is used to specify the VS environment in which CICS is to be run. For example, OPSYS=(VS1,1) is the decimal release number of the operating system. In the case of release 2.3, the fix for APAR No. P10780 must also be applied. ceNDCD: Applicable only to the ClCS/OS-STANDARD system, this operand is used to specify up to eight condition codes which, if met on any job step, cause further processing of that job to be bypassed. "code" can 1:e any decimal number from 0 through 4095. "operator" can be any of the fcllowing: GT, GE, EQ, LT, LE, NE. For further details, see the publication Q~ g2~ ~~n!£21 1~ng~~~ (GC28-6704). PRIOBTY: Applicable only to the CICS/OS-STANDARD system, this operand is used to assign a priority to the jobs in Stage II of system generation. All jobs are given the same priority, where "nn" can be any decimal number from 0 through 13. For further details, see the publication Q~ ~Q~ ~fn~~21 1~ng~Eg§ (GC28-6704). MSGCLAS: Applicable only to the CICS/OS-STANDARD system, this operand is used to route all messages issued by the OS Job Scheduler to an output class othEr than the normal message class (Al. "x" can be any alphabetic (A-Z) or numeric (0-9) character. If this operand is omitted, or if MSGCLAS=A is specified, job scheduler messages are routed to the standard output class, A. For further details, see the publication Q~ ~ob ££n~fQl 1~ng~~g§ (GC28-6704). CLASS: Applicable only to the CICS/OS-STANDARD system, this operand is used to assign a jobclass to all Stage II jobs. "jobclass " can be an alphatetic character A through o. If this operand is omitted, or if CLASS=A is specified, A is the default jobclass assigned to the jobs. For further details, see the publication Q~ ~Q~ ~~ntrgl 1Engy~§ (GC28-6704) • Applicable only to.the ClCS/OS-STAN£ARD system, this operand REGION: allows the user to (1) specify the maximum amount of main storage to be allocated to the job, or (2) specify the maximum amount of main storage to be allocated to the jcb and specify in which storage hierarchy or hierarchies (if OS/MVT is generated with hierarchy support) the space is to be allocated. "-- If REGION=n1K is specified (for example, REGION=52K), "n1" indicates the number of contiguous 1024-byte areas of main storage to be allocated for the job (n1 should be an even number and must not excEed 16383). If REGION= (n1K,n2K) is specified (for example, REGION= (60K, 150K), "n1" indicates the number of contiguous 1024-byte areas to be allocated in main storage (hierarchy 0), and "n2" indicates the number of contiguous 1024-byte areas to bE allocated in ~CS (hierarchy 1). For further details, see the publication g~ ~Q~ £Qnt~l 1ang~~g§ (GC28-6704). 21 If this operand is omitted, the default value (as established in the input reader procedure) is aEsumed. FRCCNMS: Applicable only to the CICS/OS-STANDARD system, this operand allows the UEer to specify the names of CICS cataloged procedures to be used as follows: (1) First Name - assembly of CICS programs and user written Assembler language pregrams, (2) Second Name - link edit of CICS Frograms and applicaticn programs, (3) Third Name - update of a temporary library during system generation, (4) Fourth Name - assembly and link edit during the preparation of system tables. The default is PRCCNMS={DFHASMV2,DFHLNKV2,DFHUPDV2,DFHAUPLK). DL1: Applicable only to the CICS/OS-STANDARD system, this operand allows the UEer to specify whether or not the Data Language/I (DL/I) interface is to be included in this generation of CICS. The default is DI1=NO. ]Q!~: The Program Specification Directory (PDlR) and Data Management Block Directory (DDlR) lists mUEt be in CICS.LOADLlB for the link edit of the CICS-DL/I interface modules. Therefore, if DI/l is being generated, the listE must be assembled and link edited before stage II of system generatien is executed. For further informaticn, see the section "Generation of ClCS/OS Data Language/I Facilities". ATP: Applicable only to the ClCS/OS-STANDARD and ClCS/DOS-STANDARD Eystems, this operand allows the UEer to Epecify whether or not Asynchronous Transaction Processing (ATP) support is to be included in this generation cf ClCS. The default is ATP=NO. PREFIX: Applicable cnly to the CICS/OS-STANDARD system, this operand is used to specify the index name for CICS system data sets. The Job Centrol Language (JCL) generated specifies these data sets as prefix.LOADLIB, prefix.MACLlB, and prefix.SOURCE, where "prefix" can centain frem one to eight characters and must conform to the data set naming conventions outlined in the publication Q2 ~QE ~Qn~~l 1~ngy~g~ (GC28-6704). The default is PREFlX=ClCS. !CTUA: !his operand is used to specify user-defined Process Control Informatien (PCl) fields of fixed length (15 bytes) and/or variable length (0-255 bytes). These fields are located in the Terminal Control Table and can be used as terrrinal work areas. TCTUA=V1CMPAT should only be used by ClCS/OS Version 1 users who are currently using the £ixed-Iength 15-byte PCl field (the address of which is at TCTTECl) and who desire Version 2 PCl compatibility with Version 1. This operand must be specified in conjunction with the STA!US=FlRST operand. !CTUA=VARlABLE is used to specify a variable-length (byte aligned) PCI field (the address of which is at TCTTECIA and the length of which is at TCTTEClL) and should be used by all but CICS/OS Version 1 users (who have used PCl fields) if a terminal work area is desired. The default is TCTUA=VARIABLE. 22 The system generation macro instruction necessary to generate the Control System Operational group is: DFHSG PROGRAM=CSO, MPS=YES,NO, NSD=number, DEVICE=1311,2314,3330, SVC=number, CAA=appendage suffix, V1CMPAT=YES, TCAMSIP=YES * * ** * * * The following Control system operational modules are generated in response to this macro instruction: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. System Initialization program (DFHSIP) and its overlays Trace Contrel program (DFHTRP), unless TRACE=NO was specified in the DFHSG TYPE=lNlTlAL macro instruction A dummy trace program (DFHTRPDY), unless TRACE=NO was specified in the DFESG TYPE=lNITIAL macro instructien System Termination program (DFHSTP) Abnormal Condition program (DFHACP) Terminal Abnormal Condition program (DFHTACP) Terminal Error program (DFHTEP) Time Adjustment program (DFHTAJP), unless TlMECTL=NO was spEcified in the DFHSG TYPE=lNITIAL macro instruction File and Terminal Statistics program (DFHSTTR) Supervisory·Statistics programs (DFHSTKC) Data Management statistics program (DFHSTTD) Real-Time Pre-Located Program Library DTF - CICS/DOS systems only 7770 Read/Write program (DFHRWP70) - CICS/OS-STANDARD system only, and only if SVC and CAA operands are specified 7770 Channel/Abnormal End Appendage program (DFHCAA70) CICS/OS-STANDARD system only, and only if SVC and CAA operands are specified 7770 SVC program (DFHDEB70) - ClCS/OS-STANBARD system only, and only if SVC and CAA operands are specifeid DL/l Interface program (DFHDLl) - ClCS/OS-STANDARD system only, and only if Dl1=YES was specified in the DFHSG TYPE=lNlTIAL macro instruction DL/l InterfacE dummy program (DFHDLlDY) - ClCS/OS-STANDARD system only, and only if DL1=YES was specified in the DFHSG TYPE=INITlAL macro instruction DL/l Initialization program (DFHDLA) - ClCS/OS-STANDARD system only, and only if DL1=YES was specified in the DFHSG TYPE=INlTlAL macro instruction DLIl Application program (DFHDLQ) - CICS/OS-STANDARD system only, and only if DL1=YES was specified in the DFHSG TYPE=INITIAL macro instruction. DL/I CALL Execution program (DFHDLE) - ClCS/OS-STANDARD system only, and only if DL1=YES was specified in the DFHSG TYPE=lNITIAL macro instruction EROGRAM: The ERCGBAM=CSO operand is used to indicate that the control System Operational group is being generated. MPS: The MPS=NO operand is used to indicate that the DOS system for which ClCS/DOS is being generated does not have multiprogramming system (MPS) support. !he default is MPS=YES. Applicable only to the CICS/DOS systems. 23 NSD: Applicable only to the CICS/DOS systems, this operand is used to specify the maximum number of nonseguential disk extents that will exist for any data set involved in the real-time execution of CICS. CICS system generation uses this value to determine the amount of main storage to be reserved at the beginning of the partition for label processing when the data sets are opened. Although most data sets are opened during system initialization, the dynamic open/close feature of the CICS Master Terminal program may require the use of this label ~rocessing area at any time during CICS execution. The presence of this operand makes it unnecessary for the user to supply a DOS LBLTYP job control statement with his CICS execution deck. If this operand is omitted, the default is NSD=9. The minimum which may be specified is one since CICS opens the Real-time Relocatable Program Library even if the user has no data sets to be opened. DEVICE: Applicable only to the CICS/DOS systems, this operand is used to specify the type of device upon which the Relocatable Program Library and the Real-Time Pre-Located Program Library (DOS-ENTRY only) are to reside. The default is the value propagated from the DEVICE= operand of DFHSG TYPE=TNTTIAL. Applicable only to the CTCS/OS-STANDARD system, this operand is SVC: used to specify the SVC number under which the 7770 SVC routine provided by CICS is to be link edited to SYS1.SVCLIB. The number specified must be in the range 200-255. The default is SVC=200 for system generation ~urposes; however, the SVC is not link edited. This operand is required if the ACCMETH=B!AM and ETAMDEV=7770 operands are included in the DFHSG FROGRAM=TCP macro instruction. For information concerning adding SVC routines to thg operating system, SEe the publication Q~ ~Y§1~ID E~£E£sID~~£~§ guig§ (GC28-6550). CAA: Applicable only to the CICS/OS-STANDARD system, this operand is used to specify the two-character alphameric suffix to be assigned to the 7770 Channel End/Abncrmal End Appendage routine provided by CICS when that routine is link edited to SYS1.SVCLIB. The suffix specified must be in the range WA-Z9. This ope~and is required if the ACCME!H=E!AM and ETAMDEV=7770 operands are included in the DFHSG fEOGRAM=TCP macro instruction and if the APPENDG operand is included in the DFHTCT TYPE=SDSCI macro instruction during preparation of the Terminal Control Table. For information concerning adding appendages to the operating system, see the publication Q~ ~lst~~ E£Qg~sIDID§~~§ g~1g~ (GC28-6550). V1CMPAT: Applicable only to the crcs/os STANDARD system, V1CMPAT=YES must be specified if the user wishes to have the Terminal Abnormal Ccndition program (DFHTACP) provide a crcs/os Version 1 interface when linking to the user-written Terminal Error program (DFHTEP) under crcs/os Version 2. This operand is to be used only by those former crcs/os Version 1 users who have an existing DFHTEP. TCAMSIP: Applicable only if TCAM is used in the CICS/OS-STANDARD system, this operand is used to generate TCAM support in the System Initialization program (DFHSIP). 24 The system generation macro instruction necessary to generate the Centrol System Service group is: DFHSG ·PBOGBAM=CSS The programs generated by this macro instruction are as 1. 2. 3. follo~s: Sign-on program (DFHSNP) Sign-off ~rogram (DFHSFP) F~E. Terminal Test Fregram (DFHFEP) If the user does not require a particular CICS management program (for example, File Centrel), he can elect to not generate that program and, as a result, save the amount of static main storage that would be required to contain the program. However, a dummy program must be Frovided for every CICS management program not actually generated. If the Control System Dummy group is generated in response to the DFHSG PBOGRAM=CSD macro instruction, dummy programs with the suffix 'DY' are produced for the fellowing: 1. 2. 3. 4. 5. 6. File Ccntrel program Transient Data Control program Dump Centrel program Temporary Storage Centrol program Interval Centrol pregram DL/I Interface program This facility permits all dummy programs to be generated without generating each one separately. The system generation macro instruction necessary to generate the Centrol System utility group is: DFESG PBCGBAM=CSU, DEVICE=(TAPE,2311,2314,3330) * The Dump utility program (DFHDUP) is generated in response to this macro instruction. FROGRAM: The PRCGBAM=CSU operand indicates that the Central System utility group (currently ccnsistently only of DFHDUP) is to be generated. DEVICE: Applicable only to the CICS/DOS systems, this operand is used to specify the type(s) of input devices(s). The default is DEVICE=(TAPE,2311,2314,3330) • 25 ~~]1]g1 ~1~1!~ ~~~~g~~]B1 R]~g]!~~ ~ASK CCNTRCL PBCGBAM (KCP) The system generation macro instruction necessary to generate the Contrcl pregram is as fellows: ~ask DFHSG PROGRAM=KCP, CCNSEC=YES, RUNAWAY=YES, STALCTL=YES, ENQUEUE=YES, OPSECUR=YES, ICPTIME=YES, ICPAUTO=YES, ICPSYNC=YES, SUFFIX=program suffix, XTYPREQ=symbolic name, XDSPCHR=symbolic name, DEVICE=(2311,2314,3330) * * * * * Unless otherwise indicated, the omission of an operand results in the corresponding functicn not being included. FROGRAM: The PRCGBAM=KCP operand indicates that the Task Control Program is to ce generated. CONSEC: Applicacle only to the CrCS/DeS-ENTRY system, the CONSEC=YES operand causes lcgic to be generated in Task Control that limits the number of consecutive I/O's initiated by File Control. When the specified limit (centained in the CSA at CSAKCCDL) is reached, the task is rolled out. This consecutive dispatch limit is specified in the System Initialization Table. RUNAWAY: The BUNAWAY=YES operand indicates that the optienal runaway task ccntrol feature of Interval Control is to be supported by Task Ccntrol. STALCTL: The STALCTL=YES operand indicates that the optional stall detection feature of Task Control is to be included in CICS. If this operand is specified, DFHACP must be made resident. ENQUEUE: The ENQUEUE=YES operand indicates that the optional enqueue/dequeue feature of Task Control is to be included in CICS. This operand must be included if the exclusive control feature is to be generated as part of the File Centrcl program. OPSECUR: The OPSECUR=YES operand indicates that the optional operator security checking feature of Ta~k Central is to be included in CICS. ICFTIME: The ICPTIME=YES operand indicates that the optional time-of-day feature cf Interval Control is to be supported by Task Central. IePAUTO: The ICPAUTO=YES operand indicates that the optional automatic task initiation feature of Interval Control is to be supported by Task Control. 26 * * * * * * * ICPSYNC: The ICPSYNC=YES operand indicates that the optional task synchronization service of Interval Control is to be supported by Task Centrol. SUFFIX: This operand is used to provide a two-character alphameric suffix for the Task Centrol program being assembled. If this operand is omitted, a suffix is not provided. XTYPBEQ: This oferand is used to generate linkage to a user-written exit routine at the peint in Task Centrol prior to determining what type of request for task services was issued. For further information concerning user exits, see the section "Creating User Exits for CICS Management programs". XDSPCHR: This operand is used to generate linkage to a user-written exit routine at a point in the Task Dispatcher subsequent to determining which task to dispatch but prior to passing control to the task. For further informatien concerning user exits, see the section "Creating User Exits for CICS Management Programs". DEVICE: Effective only in the CICS/DOS-ENTRY system, a rollout data set DTF is generated for the device(s) specified. The default is the value propogated from the DEVICE= operand of DFHSG TYPE=INITIAL. STORAGE CeNTRaL PROGRAM (SCP) The system generation macro instruction necessary to generate the Storage Centrel pregram is: DFHSG PROGRAM=SCP, XTYPREQ=symbolic name, SUFFIX=program suffix * * PROGRAM: The PROGRAM=SCP operand indicates that the storage Control program is to be generated. XTYPREQ: This operand is used to generate linkage to a user-written exit routine at the entry point of storage Centrel. For further informatien concerning user exits, see the section "Creating User Exits for CICS Management Programs". SUFFIX: This operand is used to provide a two-character alphameric suffix for the storage centrel program being assembled. If this operand is omitted, a suffix is not provided. 27 PROGRAM CONTROL FEOGRAM (PCP) The system generation macro instruction necessary to generate the Pregram Centrol program is: DFHSG PROGRAM=PCP, PCPLOAD=YES,NO, LANG=(COBOL,PL/I) , HLL~R=YES,NO, COBOL=(V2,V3,V4,SUBSET) , XFETCH=symbolic name, SUFFIX=program suffix * * * * * * Unless otherwise indicated, the omission of an operand results in the corresponding functien not being included. PROGRAM: ~rogram The PROGRAM=PCP operand indicates that the Program Control is to be generated. PC~LOAD: su~port The PCPLOAD=NO operand is used to specify that the optional for the Pregram Centrel Load feature is net to be geherated. PCPLOAD=YES must be specified in order to use a sign-on Table or a Terminal List Table or if application programs use either the DFHPC TYPE=LOAD or the DFHBMS macro instruction. See System service Tables. The default is PCPLOAD=YES. LANG: This operand is used to specify that the optional support for ANS COBOL and/or PL/I is to be generated. HLLTR: This operand is used to specify that support for DFHTR (trace) macro instructions is to be generated for high-level language application programs. If this operand is used, the LANG operand must also be used. The default is HLLTR=NO. CCBCL: This operand is used to indicate which ANS COBOL compilers are to be used to compile user-written applicaticn programs. COBOL=V2 indicates that the ANS COBOL Version 2 Compiler (360N-CB-482 for DOS, 360S-CE-545 for OS) is to be used; COBCL=V3 indicates that the ANS COBOL Version 3 Compiler (5736-CB2 for DOS, 5734-CB1 for OS) is to be used; COBOL=V4 indicates that the ANS COBOL Version 4 Compiler (5734-CB2) for as is to be used. ~he SUBSET parameter indicates that the DOS Subset Compiler (5736-CB1) is to ce used. If this operand is used, LANG=COBOL must also be specified. The default is COBOL=V3. This ope~and is used to generate linkage to a user-written XFtTCH: exit routine at the point in Program Control following the loading of the requested pregram. For further information ccncerning user exits, see the section "Creating User Exits for CICS Management Programs". SUFFIX: This operand is used to provide a two-character alphameric suffix for the Pregram Centrel program being assembled. If this operand is omitted, a suffix is not provided. 28 PROGRAM INTERRUPT CONTROL PROGRAM (PIP) The Program Interrupt Control program is a generalized program interrupt handler that is given control by the operating system via the STXIT (DOS) or SPIE (OS) macro instruction. This program is required under CICS/OS if the runaway task control feature of Interval Control is to be supported. The system generation macro instruction necessary to generate the Program Interrupt program is: DFHSG PROGRAM=PIP, SUFFIX=program suffix * PROGRAM: The PROGRAM=PIP operand is used to indicate that the Program Interrupt program is to be generated. SUFFIX: This operand is used to provide a two-character alphameric suffix (other than 'NO' which is reserved) for the Program Interrupt program being assembled. If this operand is omitted, a suffix is not provided. INTERVAL CONTROL PROGRAM (ICP) The system generation .macro instruction necessary to generate the Interval Control program is as follows: DFHSG PROGRAM=ICP, RUNAWAY=YES, ICPTIME=YES, ICPAUTO=YES, ICPSYNC=YES, SUFFIX=program suffix, XTYPREQ=symbolic name, XICEEXP=symbolic name, DUMMY=YES * * * * * * * * unless otherwise indicated, the omission of an operand results in the corresponding function not being included. PROGRAM: The PROGRAM=ICP operand indicates that the Interval control program is to be generated. If the TIMECTL=NO operand was included in the DFHSG TYPE=INITIAL macro instruction, only a dummy Interval Control program is generated. If the TIMECTL=NO operand was not included, the remaining operands of the DFHSG PROGRAM=ICP macro instruction are applicable and must be compatible with the corresponding operands included in the DFHSG PROGRAM=KCP macro instruction. RUNAWAY: The RUNAWAY=YES operand indicates that the optional task control feature of Interval Control is to be included in Note that the Program Interrupt Control program (PIP) is used this feature and must be generated if the RUNAWAY=YES operand under CICS/OS. runaway CICS. to support is used ICPTIME: The ICPTIME=YES operand indicates that the optional time-of-day feature of Interval Control is to be included in CICS. 29 Note that this operand must be used unless TIMECTL=NO was specified in the DFHSG TYPE=INITIAL macro instruction. ICPAUTO: The ICPAUTO=YES operand indicates that the optional "time-ordered" automatic task initiation feature of Interval Control is to be included in CICS. This feature allows tasks to be automatically initiated by CICS at a specified time of day or after a specified interval of time has elapsed. Note that the Temporary Storage Control program (TSP) is used to support this feature and must be generated if the ICPAUTO=YES operand is used. Either this operand or ICPSYNC=YES operand must be used unless TIMECTL=NO was specified in the DFHSG TYPE=INITIAL macro instruction. This feature is used by application programmers using the DFHIC macro instruction. ICPSYNC: The ICPSYNC=YES operand indicates that the optional task synchronization feature of Interval Control is to be included in CICS. This feature allows tasks to be synchronized with a specified time of day or with a specified interval of time. Either this operand or the ICPAUTO=YES operand must be used unless TIMECTL=NO was specified in the DFHSG TYPE=INITIAL macro instruction. SUFFIX: This operand is used to provide a two-character alphameric suffix (other than 'NO' or 'DY' which are reserved) for the Interval Control program being generated. If this operand is omitted, a suffix is not provided. XTYPREQ: This operand is used to generate linkage to a user-written exit routine at the entry point of Interval Control. For further information concerning user exits, see the section "Creating User Exits for CICS Management Programs". XICEEXP: This operand is used to allow the Interval Control program to generate linkage to a user-written exit routine when an Interval Control Element (ICE) has expired. For further information concerning user exits, see the section "creating User Exits for CICS Management Programs" • DUMMY: The DUMMY=YES operand is used to specify that a dummy Interval Control program is to be generated. If this operand is used, a 'DY' suffix is automatically generated for the dummy program; any use of the SUFFIX operand is ignored. This operand is used in lieu of the DFHSG PROGRAM=CSD macro instruction to selectively generate a dummy Interval Control program. Any other operands which may have been included in the DFHSG PROGRAM=ICP macro instruction are ignored. 30 DUMP CONTROL PROGRAM (DCP) The system generation macro instruction necessary to generate the Dump Centrel pregram is as follows: DFHSG PROGRAM=DCP, DEVICE=TAPE,2311,231ij,3330, DEVADDR=nnn, CICSDMP=YES, SUFFIX=program suffix, DUMMY=YES * * * * * unless otherwise indicated, the omission ef an operand results in the corresponding function not being included. PROGRAM: ~rcgram The Pregram=DCP operand indicates that the is to te generated. Dum~ Centrol DEVICE: Applicatle only to the CICS/DOS systems, this o~erand is used to Epecify the type of output device. If this operand is omitted, DEVICE=TAPE is assumed. A particular Dump Centrol program in the CICS/DOS systems will only one type of output device. If it is desired that different device types be used on different runs, more than one Dump Control program must be generated using the SUFFIX operand. su~port tEVADDR: If the DEVICE=TAPE operand iE used, the DEVADDR=nnn operand must be used to Epecify the DOS device address to be assigned for the tape drive. It should be a three-digit decimal number with leading zeros, if necessary. For example, if SYS008 is the device address to be used, DEVADDR=008 must be specified. If the DEVICE=2311 operand or the DEVICE=2314 operand is used, the DEVADDR value is picked up from the label information su~~lied for the Dump Control data set. This e~erand is applicable only to the CICS/DOS systems. CICSDMP: The CICSDMP=YES operand is used to specify that the optional feature of dumping CICS management programs and tables is to be generated. SUFFIX: This operand is used to provide a two-character alphameric suffix (other than 'NO' or 'DY' which are reserved) for the Dump Control program being assembled. If this operand is omitted, a suffix is not provided. DUMMY: The DUMMY=YES operand is used to specify that a dummy Dump Centrel ~rogram is to be generated. If this operand is used, a 'DY' suffix is automatically generated for the dummy program; any use of the SUFFIX o~erand is ignored. This operand is used in lieu of the DFHSG PROGRAM=CSD macro instruction to selectively generate a dummy Dump Centrol program. Any ether operands which may have been included in the DFHSG PROGRAM=DCP macro instruction are ignored. 31 TERMINAL CCNTRCL PBCGBAM (TCP) Tbe system generation macro instruction necessary to generate the Terminal Centrel program is as fellows: DFHSG PROGRAM=TCP, ACCMETH=(BTAM,BSAM,SAM,EGAM,TCAM), DEVICE=(1403,1404,1442,1443,1445,2311,2314,3330, 2501,2520,2540,CRLP,DASD,DISK,TAPE), BTAMDEV=(1030,1050,1050D,1053,1130,1130D,2020,2020D, 2260,L2260,2265,2740,2740D,2740-2,2741C, 2741E,2741DC,27Q1DE,2760,2770,2770D,2180,2180D, 2980/1,2980/2,2980/4,3215,3271,L3271,3284, L3284,3286,L3286,3735D,7110,SYS/3,SYS/3D,SYS/1, SYS/1D,S/360,S/360D,S/310,S/310D,TWX,BISYNC), FEATURE=(AUTOANSW,AUTOPOLL,BUFFRECV,PSEUDOBIN), ANSWRBK=(EXIDVER,TERMINAL,AUTOMATIC,1110TERM,1110NULL), INITRL=YES, LOCKF=YES, WRAPLST=YES, BSCOtE=(EBCDIC,ASCII,TRANSCODE), AUTCTRN=YES, UCTRAN=NO, (EBCDIC,ASCIT) , COMPAT=NO, (FORMAT,FULLBUF) , FMT2260=(6X40,12X40,12X80,15X64), FMT3210= (12X4Q,24X80), CMPT60L=(n1,n2,n3), SMI=user character, TAB=YES,NO, CONVTAE= (AEE,ABC) , XATTACH=symbolic name, XOUTPUT=symbolic name, XINPUT=symbolic name, XTCMIN=symbolic name, XTCMOUT=symbolic name, TCM3270=YES, TCM7710=YES, BMS=YES,NO, SUFFIX=program suffix * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Unless otherwise indicated, the omission of an operand results in the corresponding functicn not being included. PROGRAM: The PRCGRAM=TCP operand indicates that the Terrrinal Control program is to be generated. ACCMETH: This operand identifies the access methods to te used in the terminal environment. One or more of the following keyword parameters must be specified: 1. 2. 3. 4. 5. BTAM BSAM SAM BGAM TCAM Basic Telecommunication Access Method Basic Sequential Access ,Method Sequential Access Method Graphics Access Method Telecommunication Access Method BT'AMDEV DEVICE DEVICE BGAM and TCAM are applicable only to the CICS/OS system. BGAM causes support for local 2260's to te generated. If TCAM is specified, CICS support for TCAM (360S-CQ-548) is generated. SAM and BSAM are functionally synonymous in CICS and can be used interchangeably. Only unblocked data sets can be used with SAM or BSAM. 32 In the generation of a TCAM only Terminal Control Program, the fcllowing operands do not apply: DEVICE, BTAMDEV, FEATURE, ANSWRBK, INITRI, lCCKF, WRAPLST, BSCODE, UCTRAN=ASCII, CONVTAB, XOUTPUT, XINPUT. DEVICE: This operand identifies the direct access or sequential devices that are to be used in the terminal envircnment. This operand must be used if ACCMETH=SAM or ACCMETH=BSAM is specified. For direct access devices, specify Eith~r the device type or the generic parameter DASD or DISK. ETAMDEV: This operand identifies the ETAM device types and must be present if ACCME1H=BTAM is specified. The applicable keyword parameters are: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 1030 1050 1050D 1053 1130 1130D 2020 2020D 2260 L2260 2265 2740 2740D 2740-2 15. 16. 17. 2741C 2741E 2741DC 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. 41. 42. 43. 44. 2741DE 2760 2770 2770D 2780 2780D 2980/1 2980/2 2980/4 3215 3211 L3211 3284 L3284 3286 L3286 3735D 7710 SYS/3 SYS/3D SYS/7 SYS/1D S/360 S/360D S/310 S/370D TWX 45. BISYNC 1030 Data Collection System 1050 Data Communication System 1050 Data Communication system (dial-up) 1053 Printer on a local/remote 2848 Display Control 1130 computing System 1130 Computing System (dial-up) System/360 Model 20 System/360 Model 20 (dial-up) 2260 Display station (remote) 2260 Display station (local) 2265 Display Station 2740 Communication Terminal Models 1 and 2 2740 Communication Terminal Models 1 and 2 (dial-up) 2740 Communication Terminal Model 2 (2140 must also be specified) 2141 Communication Terminal with correspondence code 2741 communication Terminal with PTTC/EBCD code 2741 Communication Terminal with correspondence code (dial-up) 2741 Communication Terminal with P1TC/EBCD code (dial-up) 2760 optical Image unit 2110 Data Communication System 2110 Data Communication System (dial-up) 2780 Data Transmission Terminal 2780 Data Transmission Terminal (dial-up) 2980 General Banking Terminal System Model 1 2980 General Banking Terminal System Model 2 2980 General Banking Terminal System Model 4 3215 Display Station (remote) 3217 Display Station (remote) 3271 Display station (local) 3284 Printer on a remote 3271 Control unit 3284 printer on a local 3212 Control Unit 3286 Printer on a remote 3271 Control Unit 3286 Printer on a local 3272 Control Unit 3735 Programmable Buffered Terminal (dial-up) 1710 Audio Response Unit Model 3 system/3 Models 6 and 10 System/3 Models 6 and 10 (dial-up) System/7 System/1 (dial-up) System/360 System/360 (dial-up) System/370 System/310 (dial-up) Ccmmon Carrier Teletypewriter Exchange Terminal (Model 33/35) Binary synchronous devices (for CICS/OS-STANDARD V1 compatibility) 33 The L2260 paramete~ is applicable only to the CICS/DOS systems. The BISYNC parameter includes 1130, System/360 Model 20, and System/360 Model 25 or higher. One or more parameters can be included in the ETAMDEV operand. Individual device type parameters are provided for the BTAMDEV operand so that system generation input is self documenting. If the parameter length for this operand exceeds assembler limit of 255 characters for the particular system being generated, synonymous parameters can, be omitted. Specifying anyone of the parameters from a group prod~ces su~portive code for all devices in the group. These groups are: 1. 2. 3. 4. 5. ]ote~ 2020,SYS/3,S/360,S/37C,1130,BISYNC 2020D,SYSj3D,S/360D,S/370D,1130D 3275,3277 3284,3286,13284,13286 1053,2260,2265 When bin~ry. synchronous communica tion lines are part of the user's configuration, it is possible for these communication lines to time out if cont~ol is not returned to the terminal before a timeout can occur. The user can alleviate this condition in either of two ways: (1) by baving the application program issue a CICS Task Control WAIT macro instruction to voluntarily relinquish control, or (2) by setting the runaway task time interval to a value that causes the long-running task to be terminated before the line timeout can occur. FEATURE: This operand is used to specify the special features present in the terminal envi~cnment. The applicable keyword parameters are: 1. 2. AUTOANSW AUTOP01L 3. 4. BU"FFRECV PSEUDOBIN Switched·lines Automatic polling feature required for multipoint binary synchronous communication terminals Buffer feature support for 2740 Model 2 Pseudo-binary transmission code for System/7 One or more parameters can be included in the FEATURE operand. ANSWBBK: This operand is used to specify the type of terminal identification; it must be used if FEATURE=AUTOANSW is specified. parameters of this operand are net mutually exclusive. The ANSWRBK=EXIDVER specifies that BTAM-expanded ID verification is to be employed to identify those terminals which transmit unique identification sequences. ANSWRBK=EXIDVER must be specified if ETAMDEV=3735D. ANSWREK=TERMIN~L specifies that the operator will supply the identificaticn for switched lines. ANSWREK=AUTOMATIC specifies that automatic terminal identification is to be sent by the terminal. For terminals that communicate with a 7770 Audio Response Unit, the applicable keywo~d parameters are 7770TERM and 7770NULL. ANSWEBK=7770TERM specifies that the operator will supply the terminal identification. ANSWRBK=7770NULL specifies that no terminal identification is to be sent by either the terminal or operator; instead, the Terminal Control program will connect the line to the next available terminal in the terminal pcol. The default is ANSWRBK=7770TEBM, providing BTAMDEV=7770 has also been specified. 34 ]Q~~: The ANSWRBK operand must include all keyword parameters for which the corresponding parameter is to be included in the DFHTCT TYPE=LINE specification during Terminal control Table preparation. INITRL: Applicable only to the CICS/OS-STANDARD system, the INITRL=YES operand (initial read lock) is used to indicate that all reads from other than an applicatien program are with the keyboard lock option. The FEATURE=KBRDLOCK operand must be included in the DFHTCT TYPE=LINE macro instruction to have the keyboard lock feature operative for that line. This operand applies to the 2848 Model 21 and 22 with the optional keytoard lock feature. LOCKF: The LOCKF=YES operand is used to indicate that the optional keyboard lock feature, su~porting the 2848 models 21 and 22, is to be included in CICS. The FEATURE=KBRDLOCK operand must be included in the DFHTCT TYPE=LINE macro instruction to have the keyboard lock feature operative for that line. For the CICS/DOS systems, if LOCKF=YES is specified and if FEATURE=KBRDLOCK is included in the DFHTCT TYPE=LINE macro instruction, the keyboard is locked on all reads including the initial read. WRAPLST: The WRAPLS!=YES operand is used to specify that the optional wrap list feature is to be included in CICS. The list to be constructed is a wra~around polling list for a nonswitched line. BSCODE: This operand is used to indicate what types of binary synchronous communication code are to be supported. The default is BSCODE=(EECDIC,ASCII,TRANSCODE). . AUTOTRN: The AUTOTRN=YES operand is used to specify that the optional automatic transaction initiation feature is to be included in CICS. Automatic transaction initiation is specified by the TRANSID operand of the DFHDCT macro instruction. OCTRAN: This operand is used to generate support for the translation ef lowercase data to uppercase in 3270 input data streams. If UCTRAN=NO is specified, uppercase translation support for the 3270 is not generated. The default is UCTRAN=NO. If BSCODE=EBCDIC and/or CONVTAB=EBCDIC have been specified for particular lines, UCTRAN=EBCDIC specifies that support is to be generated for local and remote 3270'5 on those lines. If BSCODE=ASCII and/or CCNVTAB=ASCII have been specified for particular lines, OCTRAN=ASCII indicates that support is to be generated for remote 3270's en those lines. Uppercase translation for the 3270 is performed only on input data streams received from those 3270's for which FEATURE=UCTRAN was specified during preparation of the Terminal Control Table. COMPAT: This operand is used to generate 2260-compatibility support for the 3270 Infcrmation Display System. Such support allows the user to run his currently operational 2260-based transactions from a 3270. If COMPAT=NO is specifi€d, 2260-compatibility support for the 3270 is not generated. The default is CCMPAT=NO. 35 Two modes of compatibility operation are provided: FORMAT and FUILBUF. Either or both may be ~pecifiBd with a single use of the COMPAT operand. If COMPAT is specified, then FMT2260 and FMT3270 must be used to specify the screen formats. CCMPAT=FORMAT indicates that FORMAT compatibility mode is to be generated. FORMAT mode takes full advantage of the 3270 formatting and data compression facilities, and is the preferred method of 2260-compatibility operation, particularly for the operation of remote 3270's. CCMPAT=FULLBUF indicates that PULLBUP compatibility mode is to be generated. FULLBUP mode does not us~ the 3270 data compression facilities and must therefore be used when all lines of input data are desired. ]~!~~ If a 4S0-character 2260 is mapped onto a 4S0-character 3270, use of FORMAT mode causes the loss of the last character of each 2260 output line. Use of FULLBUP mode limits the data loss to the last eharacteI position of the last line but at the expense of tIansferIing a full 4S0 characters for each interaction involving a data entry key. FMT2260: This opeIand is used to specify the various 2260 screen fCImats to be simulated for 2260-based transactions on the 3270 Informaticn Display System. The applicable keyword parameters are: 1. 2. 3. 6X40 12X40 12XSO 4. 15X64 240-character 2260 Display station 4SQ-character 2260 Display station 960-character 2260 Display station or 12-row, SO-column fermat for the 2265 Di~play Station 15-row, 64-column format for the 2265 Display Station FMT3270: This operand is used to ~pecify the 3270 SCIeen formats on which 2260 SCIeen fOImats are to be simulated for 2260-based transactions. The applicable keyword parameters are: 1. 2. 12X40 24XSO 4S0-character 3275/3277 Display Station 1920-character 3275/3277 Display station CMFT60L: This operand specifies the minimum size of the Terminal Input/Output Area (TIOA) that will be passed when an input operation completes for any transaction running under 2260 compatibility. This operand must be specified if any of the transactions that are to be run under 2260 ccmpatibility require an input TIOA larger than the standard compatibility default. This operand corresponds in function to the INAREAL= specification formerly made in the DFHTCT TYPE=LINE maCIO instruction for the 2260/2265 configuration. The n1 parameter specifies the minimum size TIOA for a 3270 simulating a 240 character scr~en sized 2260/2265, the n2 parameter specifies the minimum for a 4S0 screen size simulation, and the n3 parameter specifies the minimum for a 960 screen size simula.tion. The default values are CMFT60L=(240,4S0,960). If a value is supplied for any of the parameters which is smaller than its corresponding default, the default value will be taken. SMI: This operand is used to specify the character that is to represent the start of message indicator (SMI) in all messages to and from the 3270 operating in 2260 compatibility mode. This character is generated as a X'4A' and must be a valid alphameric displayable character. If 36 the SMI character is contained in an output data stream, its display is dependent upon the language feature specified for the 3270. Whatever character is chosen, it remains the same for all transactions. The default is SMI=¢. TAB: TAE=YES must be specified if any of the 2260-compatible 3270 transactiens make use of the 2260 tab feature. In this case, all colon (:) characters are hbnored as 2260 tab characters when included in the output data stream. The default is TAB=NO. CCNVTAB: This operand is used to specify the type of conversion to be perfermed on the data received from the 7770 Audio Response Unit. CCNVTAE=AEB specifies conversion from ABB' transmission code; CCNVTAE=ABC specifies conversion from ABC transmission code. Either er both may be specified with a single use of the CONVTAB operand. If this operand is used, ACCMETH=BTAM and BTAMDEV=7770 must also be specified. The default is CONVTAB=(AEB,ABC). XATTACH: This operand is used to generate linkage in the Terminal Centrel program to a user-written exit routine. The linkage is generated at the point prior to issuing a Task control ATTACH for a transaction identification which is received in response to polling. For further informatien concerning user exits, see the section "Creating User Exits for CICS Management Programs" or the section "CICS/TCAM Interface Considerations". XOUTPUT: This oFerand is used to generate linkage in the Terminal Centrel program to a user-written exit routine. The linkage is generated for output events at the Foint prier to translating or framing output data. For further information concerning user exits, see the section "Creating User Exits for CICS Management Programs". XINPU~: This operand is used to generate linkage in the Terminal Centrel Fregram to a user-written exit routine. The linkage is generated at the point following completion of any input event. For further informaticn concerning user exits, see the section "Creating User Exits for CICS Management Pregrams". XTCMIN: Applicable only to the crcs/os system, this operand is used to generate linkage in the Terminal Contrel program TCAM module to a user written exit routine. The linkage is generated following completion of any input event. For further information concerning TCAM user exits, see the section "CICS/TCAM Interface Considerations". X~CMOUT: Applicable only to the CICS/OS system, this ~perand is used to generate linkage in the Terminal Contrel program TCAM module to a user written exit routine. The linkage is generated for output events at the point prier to placing data on the output queue. For further informatien concerning TCAM user exits, see the section "crCS/TCAM Interface Considerations". TCM3270: Applicable only to the CICS/OS system, this operand is required if TCAM sUFPort is to include the 3270 Information Display System. 37 TCMl170: Applicable only to the CICS/OS system, this operand is required if TCAM support is to include the 7770 Audio Response unit. BMS: This operand is used to generate the Basic Mapping Support module (DFEBMSMM) and tte necessary sUFFort code in the Terminal Control program for Basic MaFPing Support (BMS). If BMS=YES is specified, a corresponding entry (DFEEMSMM) must be included during preparation of the Processing Program Table (PPT). The default is BMS=NO. SUFFIX: !his operand is used to provide a two-character alphameric suffix for the Terminal Ccntrol program being assembled. If this operand is omitted, a suffix is not provided. FILE CCN!FCI FECGEAM (FCP) The system generation macro instruction necessary to generate the File Crintrcl program is as follows: * * DFESG PROGRAM=FCP, CONSEC=YES, FILSERV=(INDA,INIS,tAUPD,ISUPD,tAADD,ISADD,INDIRACC, * EXCTL,INSEG,OUTSEG,tABLKNG,VLR,HEXAD,DECAD,ACTAD, * IVBR,LOCATE,IBROWSE,DBROWSE) , SUFFIX=program suffix, XTYFREQ=symbolic name, XOU!PUT=symbolic name, XINPUT=symbolic name, * XINPUTC=symbolic name, DUMMY=YES * * * * * Unless otherwise indicated, the omission of an operand results in the corresponding functicn not being included. PROGEAM: The PROGEAM=FCP operand indicates that the File Control Frogram is to be generated. CCNSEC: This operand is effective only in the CICS/DOS-ENTRY system; it causes logic to be generated in File Ccntrol that limits the· number cf consecutive I/O events initiated by File Control that can occur on tehalf of a given task. When the limit (contained in the CSA at CSAKCCDL) is reached, the task is rolled out by Task Control. This facility helps protect CICS from being "seized" by a single task. This consectuive dispatch limit is specified in the System Initializetion Table. FILSERV: This operand is used to specify which of the file services are to te generated into the File Control program. The applicable keyword parameters are as follows: 1. 2. 3. 4. 5. 6. 7. 8. 38 I NtA INIS DAUPD I SUPD tAADD ISADD INDIRACC EXCTL Input DAM Input ISAM Update DAM Update ISAM Add DAM Add ISAM Indirect accessing Exclusive contrcl (requires Task Control enqueue feature) 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. INSEG OUTSEG DABLKNG VLR HEXAD DECAD ACTAD IVBR LOCATE IBBOWSE DBFOWSE Input segmenting Output segmenting Direct access blocking Variable length-records Hexadecimal relative track addressing (DAM) Zened decimal relative track addressing (DAM) Actual track addressing (DAM) ISAM variable-length records (CICS/DOS only) Dynamic open/clese/locate ISAM sequential record retrieval DAM sequential record retrieval Any number of these keyword parameters can be included in the FILSERV operand or CSMT File Service functions. ]Q1~§: Use of the file browse option under CICS/OS reguires that the user create the CVT macro and place it in SYS1.MACLIB. For guidance in creating the CVT macro instruction, see the CICS/OS O~erations Guide. LOCATE must be specified when DFHOCP is generated. LOCATE must be specified if the Master Terrrinal facility is used tc access data base. SUFFIX: This operand is used to provide a two-character alphameric suffix (other than 'DY' which is reserved) for the File Control program being assembled. If this operand is omitted, a suffix is not provided. XTYPREQ: This operand is used to generate linkage in the File control program to a user-written exit routine. The linkage is provided prior to determining what type of request for file services was issued. For further informatien concerning user exits, see the section "Creating User Exits for CICS Management Programs". XOUTPUT: This oFerand is used to generate linkage in the File Control Frogram to a user-written exit routine. The linkage is provided prior to writing data in response to an output request. For further informatien concerning user exits, see the section "Creating User Exits for CICS Management Programs". XINPUT: This operand is used to generate linkage in the File Centrol program tc a user-written exit routine. The linkage is provided after the File Control Table (FCT) is searched in response to an input request. For further information concerning user exits, see the section "Creating User Exits for crcs Management Programs". XINPUTC: This operand is used to generate linkage in the File Control prcgram to a user-written exit routine. The linkage is provided upon completion of an input event but prior to deblocking requested input records. For further information concerning user exits, see the section "Creating User Exits for CICS Management Programs". DUMMY: The DUMMY=YES operand is used to specify that a dummy File Centrel Frogram is to be generated. If this operand is used, a 'DY' suffix is automatically generated for the dummy program; any use of the SUFFIX oFerand is ignored. 39 This operand is used in lieu of the DFESG PROGRAM=CSD macro instruction to selectively generate a dummy File Control program. Any ether operands which may have been included in the DFHSG PROGRAM=FCP macro instruction are ignored. ~RANSIENT tATA CONTRCL PBCGRAM (~DP) The system generation macro instruction necessary to generate the Transient Data Centrel fregram is as follows: DFHSG PROGRAM=TDP, INTRA=YES,TRANSINTT, EXTBA=(ACQUISITION,DISPOSI~ION) , SUFFIX=program suffix, DEVICE=2311,2314,3330, XTYPREQ=symbolic name, XOU!PUT=symbolic name, XINPUT=symbelic name, DUMMY=YES Unless otherwise in1icated, the omission of an operand results in the corresponding functien not being included. PROGRAM: ~he PROGRAM=TDP operand indicates that the Transient Data Centrel fregram is to be generated. INTRA: !he INTRA=YES operand specifies that intrapartition data sets are to be used. The INTRA=TRANSINIT operand is used to specify that intrapartition data sets are to be used and that the automatic task initiation feature is also to be included. For further information concerning intrafartition data sets, refer to Transient Data Services section of the ~1~2 !EElj£~1iQn RIQ9~~ID~~~§ B§!§I§n£§ ~~nY~l SH20-1041. EX~RA: This operand specifies that extrapartition data sets are to be used. EXTRA=ACQUISITION indicates input from an extrapartion data set. EXTRA=DISPOSITION indicates output to an extrapartition data set. One or both of these parameters can be included in this operand. For further informatien concerning extrapartition data sets, refer to Transient Data Services section of the fl~~ AEE!ic~1ion RIQg~~~~±§ ~§l~£§n£§ ~~nYsl SH20-1041. SU~FIX: This operand is used to provide a two-character suffix (other than 'DY' which is reserved) for the Transient Data Control program being assembled. If this operand omitted, a suffix is not provided. DEVICE: Applicable only to the CIC5/DOS systems, this operand is used to specify the type of device on which the intrapartition data set resides. The default is DEVICE=2311. XTYPREQ: This operand is used to generate linkage in the Transient Data Centrel pregram to a user-written exit routine. The linkage is provided prior to determining what type of request for Transient Data services was issued. For further information cencerning user exits, see the section "Creating User Exits for CICS Management Programs". XOUTPU!: This oferand is used to generate linkage in the Transient Data Contrel pre gram to a user-written exit routine. The lir.kage is 40 * * * ** * * * provided after locating the appropriate entry in the Destination Control Table (DCT) but prior to writing data in response to an output request. For further information concerning user exits, see the section "Creating User Exits for CICS Management Programs". XINPUT: This operand is used to generate linkage in the Transient Data Ccntrol program to a user-written exit routine. The linkage is provided after acquiring data in response to an input request. For further informaticn concerning user exits, see the section "Creating User Exits for CICS Management Programs". DUMMY: The DUMMY=YES operand is used to specify that a dummy Transient Data Contrcl program is to be generated. If this operand is used, a 'DY' suffix is automatically generated for the dummy program; any use of the SUFFIX operand is ignored. This operand is used in lieu of the DFESG PROGRAM=CSD macro instruction to selectively generate a dummy Transient Data Control "-- 40.1 program. Any other operands which may have been included in the DFHSG PROGRAM=TDP macro instruction are ignored. TEMPORARY STORAGE CONTROL PROGRAM (TSP) The system generation macro instruction necessary to generate the Temporary Storage Centrol program is as follows: DFHSG PROGRAM=TSP, DEVICE=2311,2314,3330, SUFFIX=program suffix, VIRTUAL=VIRTUAL,REAL, XTYPREQ=symbolic name, XOUTPUT=symbolic name, XINPUT=symbolic name, DUMMY=YES ** * ** * * Unless otherwise indicated, the omission of an operand results in the corresponding function not being included. PROGRAM: The PROGRAM=TSP operand indicates that the Temporary Storage Control program is to be generated. DEVICE: Applicable only to the CICS/DOS systems, this operand is used to specify the type of device on which the temporary storage data set resides. This operand is required in the CICS/DOS-ENTRY system; it can be omitted in the CICS/DOS-STANDARD system if the temporary storage data set resides in main storage. The default is DEVICE=2311. SUFFIX: This operand is used to provide a two-character suffix (other than 'NO' or 'DY' which are reserved) for the Temporary Storage program being assembled. If this operand is omitted, a suffix is not provided. VIRTUAL: This operand specifies whether Temporary Storage is to be run in a real or virtual environment. Specification of VIRTUAL for this operand generates a Temporary Storage program capable of running in a V=V or V=R environment, but consumes a greater amount of address space. specifying REAL generates a Temporary Storage program capable of running only in a V=R environment. B2i§: This operand is valid only for CICS/OS STANDARD Version 2.3 with the fix for APAR No. P10780 applied or for later releases. XTYPREQ: This operand is used to generate linkage in the Temporary Storage Control program to a user-written exit routine. The linkage is provided prior to determining what type of request for Temporary Storage services was issued. For further information concerning user exits, see the section "Creating User Exits for CICS Management Programs". XOUTPUT: This operand is used to generate linkage in the Temporary Storage Control program to a user-written exit routine. The linkage is provided prior to writing data in response to an output request. For further information concerning user exits, see the section "Creating User Exits for CICS Management Programs". 41 XINPUT: This operand is used to generate linkage in the Temporary storage Control program to a user-written exit routine. The linkage is provided prior to returning control to the application program after servicing an input request. For further information concerning user exits, see the section "Creating User Exits for CICS Management Programs" • DUMMY: The DUMMY=YES operand is used to specify that a dummy Temporary storage program is to be generated. If this operand is uSEd, a 'DY' suffix is automatically generated for the dummy program; any use of the SUFFIX operand is ignored. This operand is used in lieu of the DFHSG PROGRAM=CSD macro instruction to selectively generate a dummy Temporary Storage Control program. Any other operands which may have been included in the DFHSG PROGRAM=TSP macro instruction are ignored. The system generation macro instruction necessary to generate the Common System Area is as follows: DFHSG PROGRAM=CSA, WRKAREA=number, SUFFIX=program suffix * * In addition to generating the CSA, the execution of this macro instruction causes the assembly of Terminal Control's TCA, Task Control's TCA, and, in the CICS/DOS systems, a write to Operator (WTO) routine. In the ClCS/OS system, a dummy CSA is also generated. PROGRAM: The PROGRAM=CSA operand indicates that the Common System Area is to be generated. WRKAREA: This operand is used to specify the number of bytes to be allocated to the common work area portion of the CSA. This area is initially set to binary zeros and is available to all programs. If the WRKAREA operand is omitted, the size of the work area defaults to 512. The maximum size for the work area is 3584 bytes. SUFFIX: This operand is used to provide a two-character suffix for the CSA being generated. If this operand is omitted, a suffix is not provided. The system generation macro instruction necessary to generate the Master Terminal program is: DFHSG PROGRAM=MTP, TLT=YES,NO PROGRAM: The PROGRAM=MTP operand indicates that the Master Terminal program is to be generated. TLT: The TLT=NO operand indicates that the user does not desire to use the Master Terminal program to load Terminal List Tables during 42 * real-time execution of ClCS. TL1=YES indicates that the Master Terminal ~rogram will be used to lead a Terminal List Table to change the status of a class of terminals and/or ensure that a supervisory terminal operator can change the status of only those terminals under his centrol. The default is TLT=YES. ]Q!~: If the Master Terminal facility is used to access data base, LOCATE must be specified on the FILSERV operand of the DFHSG PBCGRAM=FCP macro instruction. The system generation macro instruction necessary to generate the Dynamic Open/Close program is: DFHSG PBOGBAM=OCP This macro instruction must be issued if the Dynamic Open/Close program is to be used either through the Master Terminal facility or in response to a DFHOC request in an application program. Whenever this program is used, FCP must be generated with FILSERV=( ••• ,LOCATE). The system generation macro instruction necessary to generate the Graphic Attention prcgram is: DFHSG PROGRAM=GAP This macrc instruction is effective only in the CICS/OS-STANDARD system and is used to generate sUFPort for the local 2260. The system generation macro instruction necessary to generate the High-Level Language Support group is: DFHSG PROGRAM=HLL, LA NG= (COBOL, PL/I) , PL1=(O,F) * * The su~port programs generated in response to this macro instruction are as fellows: 1. 2. 3. ClCS preprocessor program (DFHPRPR) - for either or both languages Entry Interface program (DFHPL1l) for PL/I F and/or for PL/I optimizer (DFHPL10I) . PL/I Interface program (DFHSAP) for PL/I F and/or for PL/I o~timizer (DFHPL10I) PROGRAM: Su~port The PRCGRAM=HLL operand indicates that the High-Level Language group is to te generated. LANG: This operand is used to identify the languages for which support is to ce generated. PL1: Applicable only to the CICS/OS system, this operand is used to identify the PL/I compilers for which sup~ort is to be generated. The default is PL1=F. If both compilers are to be used, PL1=(O,F) must be specified. 43 The system generation macro instruction necessary to generate the Terminal Dependent Centrel program is: DFHSG ~ROGRAM=DDM This macre instructien must be issued when using 1030 terminals. The system generation macro instruction necessary to generate the Asynchronous Transaction processing group is: DFHSG PROGRAM=ATP, INBUFF=number, OUTBUFF=number * * The fellowing programs are generated in response to this macro instruction: 1. 2. 3. 4. Asynchronous Transaction Asynchronous Transaction (BFHRD1 and DFHRD2) Asynchronous Transaction (DFHWT1and DFHWT2) Asynchronous Queue Purge Control program (DFHATP) Input processing programs Output Processing programs program (DFHAQP) Note that this maero instruction is effective only if ATP=YES was included in the BFHSG TYPE=INITIAL macro instruction. PROGRAM: The PRCGRAM=ATP operand indicates that the Asynchronous Transaction Processing group is to be generated. INBUFF: This operand is used to specify the size (in bytes) of the input tuffer used by the Asynchronous Transaction Input processing programs. The value specified should not exceed full track capacity for the device being used, or, in the case of CICS/OS, should not exceed the block size specified on the intra partition data set data definition (DD) card at start-up time. OUTBUFF: This operand is used to specify the size (in bytes) of the output tuffer used by the Asynchronous Transaction Contrel program. The value specified should not exceed full track capacity for the device being used, or, in the case of CICS/OS, should not exceed the block size specified on the intrapartition data set data definition (DD) card at startup time. Terminating JCL for stage II is produced in response to the DFHSG TYPE=FINAL macro instruction. This macro instruction is effective only in the CICS/DOS systems and must be the last statement of the CICS/DOS system generation input stream preceding the Assembler END card. 44 To provide CICS/OS application programs optional access to the Data Language/I (DL/I) facility of the IBM Information Management System (IMS/360), the following steps are necessary: 1. Generate an IMS/360 Version 2 Data Base System capable of executing batch IMS/360 programs. This system must be Modification Level 2 or later. 2. Indicate during generation of CICS that application programs can access DL/I. This is done by coding DFHSG TYPE=INITIAL,DL1=YES 3. Generate a System Initialization Table (SIT) which includes parameters for the CICS-DL/I interface. Applicable parameters are DL1, PSB, BUFPL, PSBPL and DMBPL; these parameters may be included or overridden at execution time. 4. Include the following CICS options during generation of CICS: a. b. c. 5. Task Control ENQUEUE/DEQUEUE File Control LOCATE Interval Control program (ICP) Generate IMS/360 Control Blocks as detailed below. DEFINING PSB'S AND PCB'S The CICS-DL/I interface has the following requirements for Program specification Block (PSB) generation: 1. A special initialization PSB is used by CICS-DL/I Initialization to bring the proper DL/I modules into storage. This PSB, called the "initialization" PSB is not used by any transaction. Program Communication Blocks (PCB's) are defined within the PSB to indicate what type of CALL's and data bases DL/I will be called upon to service. The following rules apply. a. Define one data base PCB (TYPE=DB) for each of the following access methods to be used: HSAM, HDAM. b. Define two data base PCB's for the same data base for each of the following access methods to be used: HISAM, HIDAM. These PCB's will be referred to as a PCB pair. Their specification causes BISAM rather than QISAM to be used. c. Within each PCB, define PROCOPT (processing options) to include all processing options to be performed against all the data bases using that access method. That is, if one HDAM data base is to be accessed via PROCOPT=GE and another via PROCOPT=GRP, the combined PROCOPT to be specified is PROCOPT=G RPE. d. For each PCB being defined, provide one SENSEG statement. For the PCB pairs required for HISAM or HIDAM (see above), the SENSEG statements must refer to the same segment type. If the use of QISAM is desired in addition to BISAM, provide an additional SENSEG statement in one PCB of the PCB pair. e. In the PCB statement, specify KEYLEN to be the length of the key field defined in the SENSEG statement in (d) above. 45 f. The last statement preceding the END statement in the assembly should be written: PSBGEN LANG=ASSEM,PSBNAME=psbname If DL1=YES is specified during CICS System Initialization, the PSB used is named CICS PSB unless overriden in the System Initialization Table or by the execution time PSB parameter. 2. If an application programmer does not uame a PSB in the DL/I CALL, the PSB used has the name of the program whose name is in the Program Control Table (PCT) entry for this transaction. Therefore, for all transactions with DL/I CALL's where the PSB name is not specified, there must be a PSB generated with the same name as the program name in the PCT entry for the transaction. For PL/I programs, specify that the PSB is for PL/I. 3. If an application programmer names a PSB in the DL/I CALL, there must be a PSB generated with the name used in that CALL. For PL/I programs, specify that the PSB is for PL/I. The CICS-DL/I Interface uses the pre-built blocks feature of DL/I. After all Program Specification Blocks (PSB's) and Data Base Descriptions (DBD's) have been generated, the user must then generate Application Control Blocks (ACB's) in the IMS/360 ACB Library for all PSB's to be used. The instructions for this generation are included in the l11~l'§Q utilitie§ !1an£~l. DEFINING PSB AND DMB DIRECTORIES DURING CICS GENERATION A PSB Directory (PDIR) list and DMB Directory (DDIR) list must be built for the CICS-DL/I Interface. Each of these lists is built by a separate assembly and link edit. Both lists are then included in the link-edit of DFHDLQ as described in the CICS/OS Operations Guide. Each PSB excluding the initialization PSB, to be used by transactions is defined via the statement: label DFHDLPSB PSB=psbname The last statement in the assembly preceding the END statement is: label DPHDLPSB TYPE=FINAL The NAME card for the Linkage Editor is written: NAME DFHDLPSB (R) Each Data Base Description (DBD) the statement: label used by the system is defined via DPHDLDBD (INDEX,) DBD=dbdname where the positional operand, INDEX, indicates that this is a DFHDLDBD statement for the INDEX DBD of a HIDAM data base. 46 The last statement in the assembly precEding the END statement is: (label) DFHDLDBD TYPE=FINAL The NAME card for the Linkage Editor is written: NAME DFHDLDBD(R) 47 CICS is dependent upon user-created system tables which describe the user's data base/data communications environment and the treatment the user wishes given to the elements of that environment. contained in the system tables is information regarding the user's terminals, data sets (permanent and temporary), programs, and transactions. These tables are created independently of system generation. However, they are required for the system to be operational. CICS is dynamically configured under user control during system initialization. The desired system tables are selected by the user, based on a standard naming and suffixing convention. Each of the tables is created separately and may be recreated at any time prior to system initialization. More than one system table of each type can be maintained at the same time. This allows the user to maintain special tables for testing in addition to the operational tables. The system tables are prepared (generated) by assembling the appropriate macro instruction and its associated operands using the Assembler program. The output of each assembly contains the required Linkage Editor control cards. The tables are named in the following manner: System Initialization Table Terminal Control Table File Control Table Destination Control Table Program Control Table Processing Program Table DFHSITxx DFHTCTxx DFHFCTxx DFHDCTxx DFHPCTxx DFHPPTxx The first six positions are standard for each of the tables. The last two positions (xx) may be specified by the user to allow several versions of a table to be maintained; any two characters (other than 'NO') are valid. The suffix which the user assigns to a table is used to determine which version of that table is to be loaded into the system during system initialization. When generating system tables, the assembly of each table must be terminated by an Assembler END statement which includes a mandatory label (symbol) of the form DFHxxxBA, where xxx is the three-character table designation (for example, END DFHFCTBA terminates the assembly of the File Control Table). See the appropriate CICS Operations Guide for details concerning the link editing of the tables. A detailed description follows of what is required to complete the control cards or macro instructions for each of the system tables. The initialization of CICS is both flexible and dynamic. The flexibility at the time of initialization is provided by the System Initialization Table (base name: DFHSIT). The contents of the DFHSIT macro which is assembled as a table supplies the System Initialization program with the information to initialize the system to meet the user's unique environment. During the initialization process, the user is 48 given an opportunity to dynamically change some of the parameters, as required. The information contained in DFHSIT may be grouped into three catagories for purposes of discussion: 1. 2. 3. Information used to initialize and control system functions (for example, storage cushion size, system partition/region exit time interval, etc.). Module suffixes used to load the user-specified version of the CICS control modules and tables (for example, DFHPCTxx, DFHFCPxx, etc.) • Special information used to control the initialization process. The user also has the flexibility of generating several System Initialization Tables and selecting the appropriate one at the time of initialization. The following operands can be included in the DFHSIT macro instruction: DFHSIT TYPE=CSECT,DSECT, SUFFIX=xx, TRT=decimal value, SCS=decimal value, SP1=decimal value, DVT=2311,2314,3330, MSGLVL=O,l, TSBLK=decimal value, ICV=decimal value, ICVS=decimal value, ICVR=decimal value, CDL=decimal value, MXT=decimal value, TCT=xx, PPT=xx, PCT=xx, FCT=xx,NO, DCT=xx,NO, CSA=xx, KCP=xx, SCP=xx, PCP=xx, DCP=xx,NO, ICP=xx,NO, TCP=xx, FCP=xx, TDP=xx, TRP=xx, PIP=xx,NO, TSP=xx,NO, OSCOR=decimal value, PL1=YES,NO, DL1=YES,NO, PSB=name, PSBPL=number, DMBPL=number, BUFPL=number, ATP=YES,NO, ATPMT=number, ATPMB=number, SIMODS=(A2,Bl,C1,C2,C3,Dl,El) (A2,Bl,Cl,Dl,E1) * * * * * * * * * * * * * * * * * * * * * * * ** ** * * * * * * * * ** * * * or ."---... 49 TYPE: Specifies whether a CSECT or DSECT of the System Initialization Table is to be generated. If alternate or additional System Initialization modules are coded by the user, a DSECT may be required to provide symbolic addressability to values in the table. The default is TYPE=CSECT. SUFFIX: Specifies a two-character alphameric suffix for the System Initialization Table being assembled. This suffix, if specified, is appended to the standard module name (DFHSIT) and is used to name the module on the linkage editor output library. If this operand is omitted, a suffix is not provided. TRT: Specifies the number of entries that are to be provided in the CICS Trace Table. If the user has not generated the Trace facility, this operand should be ignored or set to O. (See the discussion of DFHSG TYPE=INITIAL.) If Trace has been generated and this parameter is 0, a dummy Trace facility is loaded (DFHTRPDY). The default is TRT=O. SCS: Specifies the number of bytes (minimum 20) which are to be reserved for the storage cushion. The default is SCS=500. SP1: Specifies the number of bytes to be reserved for subpool 1 storage in the CICS/DOS-ENTRY system. The default is SP1=0. To arrive at the size required, refer to "Storage Estimates and Considerations" in the CICS General Information Manual (GH20-1028). DVT: Applicable only to the CICS/DOS systems, this operand specifies the device type on which the CICS/DOS system data sets reside. These data sets include the following: 1. 2. 3. CICS Real-Time Relocatable Program Library CICS Real-Time Pre-Located Program Library (CrCS/DOS-ENTRY system only) CICS Transaction Rollout Data Set (CICS/DOS-ENTRY system only) Since no default is provided, 2311, 2314 or 3330 must be specified. MSGLVL: Specifies a message level of either 0 or 1 which controls the generation of messages to the console during system initialization. MSGLVL=O allows only critical I/O errors or interactive messages to appear. MSGLVL=1 allows all messages to be printed. The default is MSGLVL=1. TSBLK: Applicable only to the CICS/DOS systems, this operand specifies the maximum block size (as a decimal value) for records on the auxiliary temporary storage data set. The default is TSBLK=3625. rcv: Specifies the system partition/region exit time interval in milliseconds. The default is ICV=1000. For further information concerning exit time interval, see the section "System Administration". rcvs: Specifies the system stall time interval in milliseconds as a decimal value. The default is ICVS=20000. For further information concerning stall time interval, see the section "System Administration". 50 ICVR: Specifies the runaway task time interval in milliseconds as a decimal value. The default is ICVR=5000. If ICVR=OOOO, runaway task control is suspended for the duration of the current execution of CICS. For further information concerning runaway task time, see the section "System Administration". CDL: Applicable only to the CICS/DOS-ENTRY system, this operand specifies the consecutive dispatch limit as a decimal value. The default is CDL=5. MXT: This operand is used to specify the maximum number of tasks (both synchronous and asynchronous tasks in the case of the CICS/DOS-STANDARD and CICS/OS-STANDARD systems) that can be initiated concurrently within CICS. When the number of active tasks reaches this level, no new tasks are initiated by the Terminal Control program. The default is MXT=5. TCT ••• TSP: Each of the operands contained in Figure 1 allows the user to specify a two-character suffix which is appended to the standard name before loading the CICS nucleus. For example, KCP=B1 causes the DFHKCPB1 Task Control module to be included in the CICS nucleus. In each case, the default suffix is blank • .§1ANQARQ NAME! TCT=xx PPT=xx PCT=xx FCT=xx,NO DCT=xx,NO CSA=xx KCP=xx SCP=xx PCP=xx DCP=xx,NO ICP=xx,NO TCP=xx FCP=xx TDP=xx TRP=xx PIP=xx,NO TSP=xx,NO M2i§: DFHTCT DFHPPT DFHPCT DFHFCT DFHDCT DFHCSA DFHKCP DFHSCP DFHP,CP DFHDCP DFHICP DFHTCP DFHFCP DFHTDP DFHTRP DFHPIP DFHTSP Terminal Control Table Processing Program Table Program Control Table File Control Table Destination Control Table Common System Area Task Control Program Storage Control Program Program Control Program Dump Control Program Interval Control Program Terminal Control Program File Control Program Transient Data Program Trace Control Program Program Interrupt Program Temporary Storage Progra~ If NO is coded, a dummy module is loaded (except in the case of PIP where the program interrupt facility is not provided if NO is coded). FCT=NO and DCT=NO cause a dummy FCP and a dummy TDP to be loaded, respectively. For CICS/OS, PIP must be included in the CICS nucleus if the runaway task control feature is to be supported. Since CICS does not provide generatable options for DFHPIP and DFHTRP, PIP=xx and TRP=xx are used, respectively, only if the user wishes to provide his own version of these programs, or if the user specified a suffix when generating PIP, then that suffix should be used in the SIT. Figure 1. Resident program suffixes OSCOR: Applicable only to the CICS/OS-STANDARD system, this operand specifies a one- to six-digit decimal value indicating the amount of 51 main storage to be provided from the CICS partition/region for the use of the operating system during CICS execution. The default is OSCOR=Oi however, the minimum amount of main storage available to the operating system is equal to the size of the system Initialization program (DFHSIP) • If the value specified is greater than the size of DFHSIP, the amount of main storage provided for the use of the operating system is equal to ~he si~e of DFHSIP plus the amount specified in excess of the size of DFHSIP. Note that this main storage is not available to the operating system until DFHSIP transfers control to the Dummy CSA program (DFHDCSA) • The user should be aware that an incorrect OSCOR specification could adversely affect system performance. The value specified should accurately reflect the amount of main storage required by the operating system, depending upon the CICS configuration. PL1: The PL1=YES operand indicates that programs coded in PL/I are to be processed. The default is PL1=NO. DL1: Applicable only to the CICS/OS-STANDARD system, this operand is used to indicate whether or not Data Language/I (DL/I) data bases are to be accessed during execution of CICS. The default is DL1=NO. PSB: Applicable only to the CICS/OS-STANDARD system and only if the CICS-DL/I Interface is being generated, this operand is used to specify the one- to eight-character name of the Program Specification Block (PSB) used during IMS initialization. This PSB contains a Program Communication Block (PCB) for each DL/I access method to be used (two PCB's in the case of HISAM), and is uSEd to load all required DL/I modules during initialization. The default is PSB=CICSPSB. PSBPL: Applicable only to the CICS/OS-STANDARD system and only if the CICS-DL/I Interface is being generated, this operand is used to specify the Program Specification Block (PSB) pool size in 1024-byte blocks for CICS-DL/I Interface support. The number of 1024-byte blocks specified must be in the range 0-999. This operand corresponds to the PSB operand of the IMS/360 BUFPOOLS system generation macro instruction and to the III parameter of the IMS/360 CTL or CTX parameter list for online execution. The default is PSBPL=4. DMBPL: Applicable only to the CICS/OS-STANDARD system and only if the CICS-DL/I Interface is being generated, this operand is used to specify the Data Management Block (DMB) pool size in 1024-byte blocks for CICS-DL/I Interface support. The number of 1024-byte blocks specified must be in the range 0-999. This operand corresponds to the DMB operand of the IMS/360 BUFPOOLS system generation macro instruction and to the JJJ parameter of the IMS/360 CTL or CTX parameter list for online execution. The default is DMBPL=4. BUFPL: Applicable only to the CICS/OS-STANDARD-system and only if the CICS-DL/I Interface is being generated, this operand is used to specify the DL/I data base buffer pool size in 1024-byte blocks. The number of 1024-byte blocks specified must be in the range 0-999. This operand corresponds to the DBASE operand of the IMS/360 BUFPOOLS system generation macro instruction and to the HHH parameter of the IMS/360 CTL or CTX parameter list for online execution. The default is BUFPL=8. 52 ATP: Applicable only to the CIC~/DOS-STANDARD and CICS/OS-STANDARD systems, this operand is used to indicate whether or not the Asynchronous Transaction processing facility (ATP) is to ce generated. The default is A~F=NO. ATFMT: Applicable only to the CICS/DOS-STANDARD and CICS/OS-STANDARD systems, this operand is used to specify, as a decimal value, the maximum number of asynchronous tasks that can be initiated concurrently within CICS by the Asynchronous Transaction Processing centrol program (DFHATP). When the number of active asynchronous tasks reaches this level, nc new asynchronous tasks are initiated by DFHATP. The default is A'IPMT=1. ATPMB: Applicable only to the CICS/DOS-STANDARD and CICS/OS-STANDARD systems, this operand is used to specify, as a decimal value, the asynchronous task inhibitor value. When the number of active tasks (both synchronous and asynchronous) reaches this level, the Asynchronous Transaction Processing control program (DFHATP) does not initiate any new asynchronous tasks, even though the number of asynchronous tasks currently active is less than the value specified in the ATPMT operand. Thus, even though no asynchronous tasks are active, none are initiated if the tctal of all other active tasks has reached the level specified in this operand. If this operand is omitted, the default value is egual to one less than the value specified in the MXT operand. SIMODS: Applicable only to the CICS/DOS systems, this operand is used to change the last two characters of thQ phase names of the System Initialization overlays and/or allow the addition of one user-written overlay. The phase names of the System Initialization overlays are located in the DOS Core Image Library and must be seven characters in length; the first five characters are DFHSI and the last two characters are specified through use of this operand. The default is SIMODS=(A2,B1,C1,C2,C3,D1,E1) for the CICS/DOS-ENTRY system and SIMODS={A2,B1,C1,D1,E1) for the CICS/DOS-STANDARD system. The order in which the overlays are executed is determined by the sequence of the parameters of the SIMODS specification. For example, in response to the SIMODS=(AS,BS,CS,DS,ES) specification, the overlays are loaded in the order DFHSIAS, DFHSIBS, DFHSICS, DFHSIDS, DFHSIES. In response to the SIMODS=(AS,BS,CS,DS,US,ES) specification, the overlays are loaded in the order DFHSIAS, DFHSIBS, DFHSICS, DFHSIDS, DFHSIUS, DFHSIES. If an additional user-written overlay is to be provided, the SIMODS specification for the CICS/DOS-ENTRY and CICS/DOS-STANDARD systems would contain eight parameters and six parameters, respectively. BQ!~: The interface to user-written overlays is subject to change with later releases of CICS programs. The Terminal Control Table provides a means whereby the user of CICS can specify the terminal environment in which the system will operate. 'Ihe Terminal Control Table contains the data needed by the control system to perform its ter«inal management functions. The user can create more than one Terminal control Table to describe both his operational and his terminal testing environment. The Terminal Control Table macro instruction (DFHTCT) is used to specify the user's terminal environment which can include telecommunication devices, sequential processing devices, and graphic devices. The following operands can be included in the DFHTCT macro instruction: 53 DFHTCT TYFE=INITIAL, SUFFIX=xx * DFHTCT TYPE=SDSCI, DEVADDR=SYSnnn, DEVICE=1030,1050,1130,1403,1404,1442,1443,1445, 2020,2260,L2260,2265,2311,2314,2501,2520, 2540,2740,2740/2760,2741C,2741E,2770,2780, ·2980 , 327 5 , 3 277 , L3 277 , 32 84 , L 3 284 , 328 6 , L3286 , 3330,3735,7770,BSCMDMPT,BSCMDPPT,BSCMDSi,DASD, DISK,SYS/3,SYS/7,S360,TAPE,TW33,TW35,TCAM, DSCNAME=name, EREOPT=E,R,W,C,N,RW,T, FEATURE=(STC,CHK,BSC,KBL,OIU,SIX,SXW,SIW,RIX, RXW,RIW,MAS,SLV,APL), LINELST= (nnn1, ••• ,nnn31) , SWITCH=YES,NO, CU=2701,2702,2703,2848,3272,7770, CCNFIG=FPT,MFT, BSCODE=EBCDIC,ASCII,TRANSCODE, MODELS'!= (n 1, ••• , n 31) , RETRY=number, * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * ~ERMTS'I=YES,NO, LERBADR=symbclic address, DDNAME=name, MACRF=(R,W), FLNNAME=name, NCP=number, MODE=(,CNTRL,A or E,A or B), BLKSIZE=length, RECFM=F,V,U, SYNAD=symbolic name, OP'ICD=~,WU,WC,WUC, AFFENDG=appendage suffix * * * * * * * * * * * * * * * * * * * * * * symbol DFHTCT TYFE=lINE, ACCMETH=SAM,ESAM,BTAM,EGAM,'ICAM,SEQUENTIAL,GRAPHIC, TELECOMMUNICATION, * TRMTYPE=1030,1050,1053,1130,2020,2260,L2260,2265, 2740,2740/2760,2741C,2741E,2770,2780,2980, * 3275,3277,L3277,3284,L3284,3286,L3286,3735,7770, SYS/3,SYS/7,S360,CRLP,DASD,TAPE,TWX,U/R, CLASS=(CONV,EATCH,VIDEO,HARDCOPY,BISYNC,AUDIO), DSCNAME=name, ISADSCN=name, * OSADSCN=name, INAREAl=length, * TRMMODL=number or character, BTAMRLN=number, LISTADR=(name,WRAP), FEATURE=(AUTCANSR,AUTOCALL,AUTOPOLL,CHECKING, * SCCNTROL,BUFFRECV,KBRDLOCK), NPDELAY=number, FOCLADR=symbclic address, ANSWRBK=AUTOMATIC,TERMINAL,NULL,EXIDVER, LINS'IA'I='OUT OF SERVICE', BSCODE=EBCDIC,ASCII,TRANSCODE, CONVTAE=EBCDIC,ASCII,TRANSCODE,TEXTMODE,AEB,ABC, * RDYMSG=symtclic address, ERRMSG=symbolic address, GENPOLL=YES, FCCLCNT=number, * TCTUAL=number, OUTQ=symbolic name, * FCCL=YES, 54 QUEUEID=hexadecimal number * symbol DPHTCT TYPE=TERMINAL, * TRMIDNT=name, * TRMPRTY=number, * TRMMODL=number,character, * TRMTYPE=1030,1050,1053,1130,2020,2260,L2260,2265, * 2740,2740/2760,2741C,2741E,2770,2780,2980, * 3275,3277,L3277,3284,L3284,3286,L3286,3735,7770, * SYS/3,SYS/7,S360,CRLP,DASD,TAPE,TWX,U/R, * CLASS= (CONV, BATCH, VIDEO, HARDCOPY, BISYNC, AUDIO) , * LVUNIT=number, * LASTTRM=LINE,GACB,POOL, * TRMADDR=address,name, * TRMSTAT=(TRANSACTION,TRANSCEIVE,RECEIVE,'OUT OP SERVICE',* INPUT) , * COMPAT=NO, (number of characters, number of lines, * device type, model number), * FEATURE=(PTRADAPT,SELECTPEN,AUDALARM,COPY,BUFEXP, * DCKYBD,UCTRAN), * POLLPOS=number, * TRANSID=name, * STN2980=number, * TAB2980=number, * TIOAL=number, * TCTUAL=number symbol DPHTCT TYPE=7770MSG, MESSAGE='message' * DPHTCT TYPE=FINAL ESTABLISH CONTROL SECTION FOR TERMINAL CONTROL TABLE The area of main storage into which the Terminal Control Table is assembled is established in response to the DFHTCT TYPE=INITIAL, SUFFIX=xx * macro instruction, which must precede all other DFHTCT macro instructions in a Terminal Control Table assembly. SUFPIX: This operand specifies a two-character alphameric suffix for the Terminal Control Table being assembled. This suffix, if specified, is appended to the standard module name (DPHTCT) and is used to name the module on the linkage editor output library. If this operand is omitted, a suffix is not provided. 55 SPECIFY DATA SET CONTROL INFORMATION The user must specify data set control information through use of the DFHTCT TYPE=SDSCI macro instruction, which causes the control system to generate the appropriate data set control information. DTF information is generated in the CICS/DOS systems; DCB information is generated in the CICS/OS system. This macro instruction can include the following operands: DFHTCT TYPE=SDSCI, DEVADDR=SYSnnn, DEVICE=1030,1050,1130,1403,1404,1442,1443,1445, 2020,2260,L2260,2265,2311,2314,2501,2520, 2540,2740,2140/2760,2741C,2741E,2110,2780, 2980,3215,3277,L3217,3284,L3284,3286,L3286, 3330,3735,1170,BSCMDMPT,BSCMDPPT,BSCMDSW,DASD, DISK,SYS/3,SYS/1,S360,TAPE~TW33,TW35,TCAM, DSCNAME=name, ERROPT=E,R,W,C,N,RW,T, FEATURE=(STC,CHK,TRC,BSC,KBL,OIU,SIX,SXW,SIW,RIX, RXW,RIW,MAS,SLV,APL), LI NELST= (nnn 1, ••• , nnn31) , SWITCH=YES,NO, CU=2701,2102,2103,2848,3272,1110, CONFIG=PPT,MPT, BSCODE=EBCDIC,ASCII,TRANSCODE, MOD EL S T= (n 1 , ••• , n 3 1) , RETRY=number, TERMTST=YES,NO, LERBADR=symbolic address, DDNAME=name, MACRF= (R, W) , FLNNAME=name, NCP=number, MODE= (,CNTRL,A or BrA or B), BLKSIZE=length, RECFM=F,V,U, SYNAD=symbolic name, OPTCD=W,WU,WC,WUC, APPENDG=appendage suffix Two DFHTCT TYPE=SDSCI macro instructions must be coded for each sequential terminal. One macro instruction is for the sequential input data set and the other macro instruction is for the sequential output data set. This input/output data set combination simulates the input and output functions of a terminal. One DFHTCT TYPE=LINE macro instruction must be coded for this I/O combination. One DFHTCT TYPE=SDSCI macro instruction must be coded for each BTAM line group, where a line group is a group of communication lines that meet the following operational requirements: 1. 2. 3. 56 All lines in the group are attached to the channel through the same type of telecommunications control unit; for example, a 2101. (This is true only for the CICS/DOS systems.) The line connection between the control unit and the remote devices is of the same type; for example, a switched network. All devices within the line group have the same line features and operating characteristics; for example, autopoll. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * DEVADDR: Applicable only to the CICS/DOS systems, this operand specifies the symbolic unit address (sequential device) used for sequential terminal data sets. DEVICE: Specifies the valid device types for this Terminal Control Table. 12260 signifies "lccal video attachment". 2260 and 2265 signify "remote video attachment". L3277, L3284, and L3286 signify "local 3270 attachment". 3275, 3277, 3284, and 3286 signify Uremote 3270 attachment". BSCMDPPT signifies "mixed binary synchronous point-to-point devices". BSCMDSW signifies "mixed binary synchronous switched devices". ESCMDMPT signifies "mixed binary synchronous multipoint devices u • For direct access devices, specify either the device type or the generic parameter DASD or DISK. The TAPE specification defines the tape as work files for both the input and the output data set. Note that if an input tape with an expired label is entered, the header may be re-written causing the first"data record(s) to be destroyed. Support for a 1053 printer is included when 2260, L2260, or 2265 is specified. In the CICS/OS-STANDARD system, this operand automatically generates the MACRF operand. A 2740 Communication Terminal with 2760 Optical Image unit can be specified as either a 2740 or 2740/2760. DEVICE=TCAM (applicable only to CICS/OS) causes CICS to generate the appropriate data set control infcrmation to handle the TCAM input or output process queue. ]Q1~~ In the generation of a TCAM only the system, the following operands do not apply to TCP and TCT: ANSWRBK, BTAMDEV, BSCODE, CCNVTAB, FEATURE, INITRL, LOCKF, UCTRAN=ASCII, WRAPLST, XINPUT, XOUTPUT. DSCNAME: Specifies the symbclic data set control name associated with the data set contrcl infcrmation. The DSCNAME for the sequential input data set must be the same name as that specified in the ISArSCN=name operand of the DFH!CT TYPE=LINE macro instruction. The DSCNAME for the sequential output data set must be the same name as that specified in the OSADSCN=name operand of the DFH!C! TYPE=LINE macro instruction. The DSCNAME for ETAM data sets must be the same name as that specified in the DSCNAME=name operand of the DFH!CT TYPE=LINE macro instruction. ERROPT: Specifies the error recovery, error recording, and online test tc be provided for the line group. The applicable keyword parameters are: op~ions 1. 2. E, specifies that the basic error recovery procedures are to be provided for the line group. If EEROPT is omitted, ERROPT=E is assumed. R, specifies that text-read errors are to be retried in addition to the casic error recovery.procedures. This option is valid only for the following terminals: 1050 terminals (valid for the card reader and paper tape reader only if the line correction 57 3. 4. 5. 6. 7. ]Q1~: feature is installe~, 2740 terminals with the checking feature, and 2260 terminals. W, specifies that text-write errors are to be retried in addition to the basic error recovery procedures. This option is valid fer all start-stop terminals. It is invalid for binary synchronous terminals. It results in an additional copy of the message for each retry (except for the 2260 with the line address feature, and the 1050 card punch and paper tape punch with the line correcticn feature). This parameter is ignored for binary synchronous terminals. C, specifies that threshold errer counts and cumulative error counts are to be maintained in the line error recording block (LERB) for the line for data check, intervention required, and nentext timeout errors. This parameter is applicable only to the CICS/OS-STANDARD system; however, for the CICS/DOS systems, the LERB support is generated if the LERBADR parameter is specified. N, specifies that no error recovery procedures are to be provided for the line group. This parameter and E,R,W, and C are mutually exclusive. This parameter is invalid for binary synchronous stations; if coded, it is ignored. BW, specifies that error recovery is to be performed with "read text retry" and "write text retry". T, specifies that the online test facility is to be used for the line group. Applicable only to the CICS/OS-STANDARD system, this parameter is valid for all IBM terminals with or without error recovery capability. For CICS/OS, EROPT is also a valid spelling of this operand. Commas must not be coded in this parameter. For example, EFBOP'I=RECiT. Applicable only to the CICS/DOS systems, this operand FEATURE: specifies device-dependent machine special features and programming special features. The applicable keyword parameters are: 1. 2. 3. 4. 5. 6. 14 8. 58 STC, specifies that the 2740 or System/7 is equipped with the statien centrcl feature. CHK, specifies that the 2740 is equipped with checking feature (CHK must always be specified for the System/1.) BSC, must be coded when the DEVICE operand specifies a binary synchronous device. KEL, specifies that the 2848 control unit is equipped with the data entry feature. The Lock optypes are rejected as undefined if this parameter is not used. OIU, specifies that a 2760 Optical Image unit is attached to a 2740 with the checking feature and, optionally, the dial feature. SIX, sxw, or SIW, used if ID verification for a calling operation is to occur in a binary synchronous point-to-point dial system. A more detailed expl&nation of these codes is given in the publicaticn, DO~ ~~§i£ 1§1~£Q~~Yni£~1ion§ !££~§§ ~ethQg (GC30-5001). (See Note) RIX, RXW, or RIW, used if ID verification for an answering operation is to occur in a binary synchronous point-to-point dial system. A· more detailed explanation of these codes is given in the publication, ]Q~ ~~i£ 1~1~£QIDIDYni£~!io~§ !££~§§ ~§1.hQQ (GC30-S001). (See Note) MAS or SLV, used to specify whether the CPU is to be Master (MAS) or Slave (SLV) when contention occurs in a binary synchronous cpu-to-cPU contention system (private line). If this operand is not used, FEATURE=MAS is assumed for this system. If FEATURE=MAS is specified, the remote device is to be the slave when contention occurs. If FEATURE=SLV is specified, the remote device is the master. When the remote device is the 9. 2780, FEA!URE=SLV must always be coded. The CPU must always be the slave when contenticn occurs between the CPU and the remote 2780. AFL, specifies that the autopoll feature is to be employed for the start-stop devices. If FEATURE=APL is omitted, the generated channel programs for these devices will perform the standard programmed polling. A more detail€d explanation of this code is given in the publication, ]Q§ ]~si£ 1§1~£2IDIDYn1f~~iQ~~ !cc~~§ ~&1nQQ (GC30-5001). '. B2~~~ These parameters should not be used with "Extended ID Verification" i.e., they should not be coded if ANSWREK=EXIDVER is coded for TYPE=LINE. lINELST: Applicable only to the CICS/DOS systems, this operand specifies the correspondence between symbolic unit (SYSnnn) and relative line numcer. The user codes one three-digit number (nnn of SYSnnn) for each line in the line group. The order in which the three-digit numbers are coded determines which symbolic units are associated with the individual lines in the line group. As many as 31 three-digit numbers from 000-244 may be coded in this operand. For local 2260's and local 3270's, each number entry represents a physical device; all local devices attached to the same control unit must be specified in the same LINELST operand. S~ITCH: Applicable only to the CICS/DOS systems, this operand specifies the type cf line ccnnection between the system and the remote device. SWITCH=YES indicates that the line connection is through a switched network. SWITCH=NO indicates that the line connection is dedicated. The default is SWITCH=NO. CU: Applicable only to the CICS/DOS systems, this operand defines the central unit attached to the channel (such as a 2701, 2702, 2703, 2848, 3272 or 7770). !his operand is required for all non-sequential devices. If using the System/360 Model 25 with the Integrated Communications Attachment, CU=2703 must be specified; for System/370 with Integrated Communications Attachment, CU=2701 must be specified. CONFIG: Applicable only to the CICS/DOS systems, this operand specifies the type of binary synchronous line configuration. CONFIG=PPT indicates that the data link between the CPU and the remote binary synchronous device is point-to-point. CONFIG=MPT indicates that the data link between the CPU and the remote binary synchronous devices is a multi-point link. The nefault is CONFIG=PPT. BSCODE: Specifies the type of binary synchronous transmission code. BSCODE=EECDIC indicates transmission in Extended Binary Coded Decimal Interchange Code. BSCODE=ASCII indicates transmission in American Standard Code for Information tnterchange. BSCODE=TRANSCODE indicates transmission in six-bit TRANSCODE. The default is BSCODE=EBCDIC. MODELST: Applicable only to the CICS/DOS systems, this operand is used to specify a code (0,1,2,3) for each line in a binary synchronous line group to be used by BTAM at OPEN time. If this operand is omitted, code 0 is assumed for each line in the line group. A more detailed explanation of this operand is given in the publication DO§ ]~~i£ ~§1~2~~~nic~tiQ~§ A£fg§§ ]~!nQQ (GC30-5001). crcs does not support 59 the use of codes 4, 5, 6, and 7. If converting from CICS/DOS to CICS/OS, this operand must be recoded as MODE. RETRY: Specifies the number of retries (0-15) by BTAM for recoverable errors that cccur on I/O operations for binary synchronous communication. If this operand is omitted, RETRY=7 is assumed. !ERMTST: Applicable only to the CICS/DOS systems, this operand specifies whether cr not the online terminal test facility is to be used. The default is TEBMTST=NO. A more detailed explanation of this c~erand is given in the ]Q§ ]s~if l§l§£Q~~YD~fs!iQn§ A££~§~ ~§1hQQ publication, (GC30-5001 for DOS Release 26 or lower, GC27-6978 for DOS Release 27 or higher). For CICS/OS, the online terminal test facility is specified through the ERROPT operand. LERBADR: Specifies the label of the BTAM line error recording block (LIRB) in which tte user has specified his LERB parameters. For CICS/OS, this operand is valid only if EREOPT=C is also specified. For CICS/OS, LIRB is alsc a valid spelling of this operand. DDNAME: Applicable only to the CICS/OS-STANDARD system, this operand is used to supply the name of the data definition (DD) statement associated with a particular data set (line group). If converting from CICS/DOS to CICS/OS and this operand is omitted, the DSCNAME becomes the DDNAME. MACRF: Applicable only to'the CICS/OS-STANDARD system, MACRF=(R,W) indicates that access to the BTAM line group or to sequential devices is to be gained via either READ or WRITE macro instructions, or both. The default for ETAM line groups is MACRF=(R,W); the OPEN option for ETAM line groups defaults to input. For sequential devices (other than card reader and line printer)~ MACRF=R or MACRF=W must te specified. The default is MACRF=R for a card reader and MACRF=W for a line printer. FINNAME: Applicable only to the CICS/OS-STANDARD system, this operand specifies the name of the first line entry (DFHTCT TYPE=LINE) for local 2260's. NCP: Applicable only to the CICS/OS-STANtARD system, this operand is used to indicate the number of channel programs that are to be specified when using the Graphics Access Method. The default is NCP=1. MODE: Applicable only to the CICS/OS-STANDARD system, this operand specifies the mode of communication for a binary synchronous line group. A more detailed explanation of this operand is given in the publication, os Basic Telecommunications Access Method (GC30-2004). Note that since CICS-does-not-suFPort-the-IBc-parameter-aescribed in GC30-2004, a comma must be substituted in place of the IBC parameter. ELKSIZE: This operand is used for 3's to specifiy th maximum length Model 3's this value should be the in the line entries that reference macro instruction. 60 sequential data sets and 7770 Model (in bytes) of a block. For 7770 same as that specified for INAREAL the DSCNAME of this DFHTCT TYPE=SDSC1 For the CICS/OS-STANDARD system, the default is BLKSIZE=O. If this operand is omitted, the block size can be specified in the data definition (DD) statement associated with the data set. A more detailed explanation of this operand is given in the publication Q2 2YE~Ivi§QI En~ ~~!~ ~~D~E~~~D! ~~IQ Jn~!~~£1iQD§, GC28-6647. For the CICS/DOS systems, the default is BLKSIZE=80. explanation of this operand is given in the pUblication ang JLQ ~~£IQ§, GC24-5037. A.more detailed DO~ SUE~~i~QI 60.1 RECFM: Applicable only to the CICS/OS-STANDARD system, this operand is used for sequential data sets to specify the record fromat for the DCB. Applicable keyword parameters are F (fixed-length records), V (variable-length records), and U (undefined records). The default is RECFM=U. If this operand is omitted, the record format can be specified in the data definition (DD) statement associated with the sequential data set. SYNAD: Applicable only to CICS/OS with TCAM, this symbolic name specifies the address of a subroutine to be given control if message processing is used; the work unit is larger than the work area, and OPTCD=C is not specified. For input queues, the user has the option of specifying his own SYNAD routine for which an EXTRN is generated. If SYNAD is not specified, a CICS generated SYNAD routine is provided. If CICS SYNAD is used and the exit occurs: 1. 2. 3. 4. Message DFH4000 is issued. The DCB is closed. The DCB is reopened. Data is truncated to the specified blocksize and is passed to the CICS application program. OPTCD: Applicable only to CICS/OS, this operand specifies the optional fields for the TCAM work unit. The W specifies that for input, the name of the source of each message is to be placed in an eight-byte origin field in the work area. For output, it specifies that TCAM expects the name of the destination of the message to be placed in an eight-byte destination field in the work area before a TCAM WRITE macro instruction is executed. OPTCD=W must be specified for both the input and output macro instruction. U specifies that the work unit to be handled is either a message or a message segment that is not a record. If U is omitted, the work unit is assumed to be a record. C specifies that a one-byte field in the work area, called the position field, indicates whether the work unit being handled is the first, an intermediate, or the last segment of the message, and, on input, whether a record delimiter has been detected in the data. For further information concerning the OPTCD operand, see the Guide (GC30-2024). Q~L~f1 ~ng OS/~I! 1£!~ g£Qg~£IDill~~§ APPENDG: Applicable only to the CICS/OS-STANDARD system when DEVICE=7770 is specified, this operand is used to specify a two-character alphameric suffix for the 7770 Channel End/Abnormal End Appendage routine. The suffix specified must be in the range WA-Z9 and must be the same suffix as was specified in the CAA operand of the DFHSG PROGRAM=CSO macro instruction. DESCRIBE COMMUNICATION LINES communication paths to the terminals on the system are described by the DFHTCT TYPE=LINE macro instruction. The expansion of this macro instruction is the Terminal Control Table line entry (TCTLE) and contains the Data Event Control Block (DECB) that is used to communicate with the appropriate access method. The terminals related to this line must be described immediately following this macro instruction through use of the DFHTCT TYPE=TERMINAL macro instruction. However, when 61 describing a switched-line network, all the lines for a given pool should be described before describing the terminals for that line pool. If TCAM is used, the TCTTE's that follow a TCAM TCTLE represent: 1. 2. Physical terminals, if POOL=YES is not coded. The maximum number of tasks (transactions) that can be initiated for this TCTLE, if POOL=YES is coded. The following operands can be included in the DFHTCT TYPE=LINE macro instruction: symbol DFHTCT TYPE=LINE, ACCMETH=SAM,BSAM,BTAM,BGAM,TCAM,SEQUENTIAL,GRAPHIC TELECOMMUNICATION, TRMTYPE=1030,1050,1053,1130,2020,2260,L2260,2265, 2740,2740/2760,2741C,2741E,2770,2780,2980, 3275,3277,L3277,3284,L3284,3286,L3286,3735,7770, SYS/3,SYS/7,S360,CRLP,DASD,TAPE,TWX,U/R, CLASS=(CONV,BATCH,VIDEO,HARDCOPY,BISYNC,AUDIO), DSCNAME=name, ISADSCN=name, OSADSCN=name, INAREAL=length, TRMMODL=number,character, BTAMRLN=number, LISTADR= (name, WRAP) , FEATURE=(AUTOANSR,AUTOCALL,AUTOPOLL,CHECKING, SCONTROL,BUFFRECV,KBRDLOCK), NPDELAY=number, POOLADR=symbolic address, ANSWRBK=AUTOMATIC,TERMINAL,NULL,EXIDVER, LINSTAT='OUT OF SERVICE', BSCODE=EBCDIC,ASCII,TRANSCODE, CONVTAB=EBCDIC,ASCII,TRANSCODE,TEXTMODE,ABB,ABC, RDYMSG=symbolic address, ERRMSG=symbolic address, GENPOLL=YES, POOLCNT=number, TCTUAL=number, OUTQ=symbolic name, POOL=YES, QUEUEID=hexadecimal number * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * One or more DFHTCT TYPE=LINE macro instructions must be coded for each line group. The DSCNAME=name operand of each of the DFHTCT TYPE=LINE macro instructions must contain the same name as was specified in the DSCNAME=name operand of the related DFHTCT TYPE=SDSCI macro instruction. A DFHTCT TYPE=LINE macro instruction must be coded for each logical pair of sequential SDSCI macro instructions. A DFHTCT TYPE=LINE macro instruction must be coded for each symbolic unit (relative line) coded in the LINELST=parameter operand of the BTAM SDSCI macro instruction. The DFHTCT TYPE=LINE macro instruction entries must be contiguous on switched-line pools. For the local 2260 Display Station under CICS/DOS and the local 3270 Information Display System under CICS/DOS or CICS/OS, only one DFHTCT TYPE=LINE macro instruction is coded for each line group. Noig: 62 For sequential devices, the last entry in the input stream must be 'CSSF GOODNIGHT' to provide a logical close. If all input is sequential, 'CSMT SHUTDOWN' must be entered at one of the terminals to terminate CICS. ACCME~H: This oferand is used to specify the access method to be used. GrouFed according to syncnymity cf function, the applicable keyword parameters are: 1. 2. 3. 4. SAM, ESAM, SECUENTIAL BGAM, GRAPHICS (CICS/OS only) E~AM, TELECOMMUNICATION TeAM, TELECOMMUNICATION (CICS/OS only) !RMTYPE: This operand is used to specify the terminal type associated with this communication line. Only one TEMTYPE operand can be included in each DFHTCT TYPE=LINE macro instruction. This operand, when specified, establishes the default specification that will be used when the !EMTYPE operand is not specified in a DFHTCT TYPE=TERMINAL macro instructicn associated with this line. If no TRMTYPE operand is specified in the DFHTCT TYPE=LINE macro instruction, a TRMTYPE operand must be supplied in each DFHTCT TYPE=TERMINAL macro instruction for that line. The use of the TRMTYPE operand in the DFHTCT TYPE=LINE macro instruction is optional unless one of the following conditions exists: 1. 2. 3. A 7770 is associated with the line. A local 3270 is associated with the line. One cr more remote 3270's are associated with the line. In each of these cases an appropriate device-type parameter must be specified in the TRMTYPE operand; for example: "'-- 1. 2. 3. TBMTYPE=7770 for the 7770. ~RMTYPE=L3277, TBMTYPE=L3284, or TEMTYPE=L3286 for a local 3270. TRMTYPE=3275, TEMTYPE=3277, TRMTYPE=3284, or TRYTYPE=3286 for a remote 3270. TWX is the Common Carrier Teletypewriter Exchange Terminal Station (Model 33/35), DASD is the direct access storage device, CELP is the card reader and line printer (a pair of sequential devices simulating a terminal), TAPE is the magnetic tape device, and U/E is a general term that refers to any reader, printer or punch. 1053 indicates a 1053 Printer Model 4. CLASS: This operand is used to indicate the device classification associated with this communication line. The applicable keyword parameters are: 1. 2. 3. 4. 5. 6. CONV BATCH VIDEO HARDCOPY BISYNC AUDIO Device with ccnversational type application Data collection type device Device with cathode ray tube Start/stop hard-copy device Binary synchronous device Audio response device Multifle parameters may be specified, except that parameters within the following groups are mutually exclusive: CONV and BATCH; VIDEO, HARDCOPY and AUDIO. BISYNC must be specified for any binary synchronous line. For example, remote 3270s could be specified CLASS=(CONV,VIDEO,BISYNC) and local 3270s CLASS=(CONV,VIDEO). 63 DSCNAME: Specifies the data set control information for this communicatien line. It is not a~plicable for BSAM. The DSCNAME for BTAM data sets must be the same name as that specified in the tSCNAME=name operand of the related DFHTCT TYPE=SDSCI macro inst~uction. In case of TCAM, this operand specifies the data set contrel name for an input TPROCESS queue; the OUTQ operand is also required. ISAtSCN: Specifies the input BSAM data set contrel name for a particular communication line. This data set control name must be the same name as that specified in the DSCNAME=name o~erand of the related DFHTCT TYPE=SDSCI maCIO instruction. This operand is not applicable to ETAM, GAM, or TCAM. OSADSCN: Specifies the output ESAM data set control name for a particular communication line. This data set control name must be the same name as that specified in the DSCNAME=name operand of the related tFHTCT TYPE=SDSCI macro instruction. This operand is not applicable to BTAM or GAM. In the case of TCAM, this operand specifies the data set contrel name for an output TPROCESS queue; the OUTQ operand may not be used. INAREAL: Specifies the message input area length. rrinimum, must be specified as fellcws: 1. 2. 3. 4. 5. 6. 7. !Qi~: This value, as a For start/stop devices, the length should be equal to the length of the longest initial sentence of a transaction. For start/stop devices with the buffer receive feature (for example, the 2740 Communication Terminal Model 2), the length sheuld be equal to the length of the buffer less two bytes. For binary synchronous devices, the length may be calculated as (a+1) (b+2) + 1, where "a" is the number of blocks sent by a device in re~~onse to an RVI (reverse interrupt) from CICS, and "b" is the size, in bytes, of each block. For the local 2260 Display station under CICS/DOS, the length of the input message can at no time be greater than the length s~ecified through this operand. For the remote 3270 Information Display System, the length specified should not be less than 254. For the local 3270 Information Display System, the value specified may be any number greater than zero. This value indicates the minumum size of the Terminal Input/Output Area (TIOA) that will ce passed to the transaction by the Terminal Centrel program. However, for performance considerations, the value specified should be equal to or greater than the length of the expected input message; at no time can a message be read whose length excEeds the INA REAL value by more than 2000 bytes (unless the transactien provides a TIOA for the read large enough te contain the message). For sequential devices, the length should be equal to the blocksize (and record length) of the data set. The mimimum size TIOA passed to a transaction which is running under control of 2260 compatibili~y is governed by the CMPT60L operand in the system generation of the Terminal Control program (DFHSG PRCGBAM=TCP). TRMMODL: This operand specifies the model number of the terminal associated with this communication line. This operand must be used if the device is one of the following: 64 1. 2. 3. 4. 5. 6. 7. CemIonent of the 1050 Data Communication System 2740 Communication Terminal Model 2 CemFonent of the 2980 General Banking Terminal System ComFonent of the 3270 Informatien Display System 2740 Communication Terminal with 2760 Optical Image unit 2260 Display station 2265 Display station The TBMMODL Farameter sets the default value that will be taken, when it is not specified in the DFHTCT TYPE=TERMINAL macro instruction associated with that line. If models vary on a line, the macro instruction can have a TRMMODL parameter associated with it, which is different from that specified in the DFHTCT TYPE=LINE. This will override the DFHTCT TYPE=LINE macro for that DFHTCT TYPE=TERMINAL macro. TRMMODL=1 is used to specify the 2980 ~eller station Model 1, 3275 Display station Model 1, 3277 Display station Model 1, 3284 Printer Model 1, or 3286 printer Model 1. TRMMODL=1 is the default for the 3270 Information Display System. TBMMODL=2 is used to specify the 2740 Communication Terminal Model 2, 2980 Administrative Staticn Model 2, 3215 Display Station Model 2, 3277 Display station Model 2, 3284 Printer Model 2, or 3286 Printer Medel 2. TRMMODL=4 is used to specify the 2980 Teller Station Model 4. TRMMODL=5 is used to specify compcnent polling of the keyboard for the 1050 Data Communication System using non-switched communication lines. Component selection character 5 (OB) must be coded in the polling list (DF~RMLST). See note. TRMMODL=6 is used to specify component polling of reader 1 for the 1050 Data Communication System using non-switched communication lines. Component selection character 6 (OD) must be coded in the polling list (DF~RMLS'I). See note. TRMMODL=7 is used to specify (1) the 2740 Communication Terminal with 2760 optical Image Unit, or (2) compcnent pelling of reader 2 for the 1050 Data Communication System using non-switched communication lines. Ccm~onent selection character 7 (OE) must be coded in the FoIling list (DFTRMLST). See note. TRMMODl=O is used to specify an input component for the 1050 Data Communication System. Cemmon pelling character 0 (15) must be coded in the polling list (DFTRMLST). TRMMODL=O is the default specification for a 1050 Data Communication System. The TRMMODL=character operand is used to specify the applicable screen fermat for a 2260/2265 Display station as follows: TRMMODL=A TRMMODL=B TRMMODL=C TBMMODL=D TRMMODL=E 6x40 12x40 12x80 15x64 12x80 2260 2260 2260 2265 2265 For example, TRMMODL=A specifies a 2260 Display station with a 6x40 screen format. BQ~~: "'---- When TRMMODL is specified, the user must also specify the component selection character with control unit address via the TRMADDR operand of the DFH~CT TYPE=TERMINAL macro. 65 ETAMRLN: Specifies the relative line number within a line group. The relative line number can be specified in the range 1-31 for CICS/DOS and 1-256 for CICS/OS. This operand is not applicable to BSAM, TCAM, local 2260's, or local 3270's. LISTADR: Specifies the label of the BTAM Define Terminal List macro statement (DFTRMLST) in which the user has specified his polling list for the communication line. (A terminal may not be specified more than once in a polling list.) DFTRMLST entries should be coded immediately preceding DFHTCT TYPE=LINE entries or immediately following DFHTCT TYPE=TERMINAL entries. If a .wraplist is specified in the DFTRMLST, the WRAP eperand must be included. The default is to an open list. LISTADR is not applicable when ACCMETH=BSAM, ACCMETH=GAM, or for some devices when ACCMETH=BTAM (for example, dial-up 2741's). The DFTRMLST macro instruction establishes a terminal list from which ETAM attains the infermatien it needs to establish contact with a terminal. This information consists of telephone numbers, polling and addressing sequences, and identification sequences to be sent to terminals, or against which an incomming sequence can be checked to ensure that contact has been established with a valid station. For more information, see the publication ]Q~ ]~§i£ ~~1~£2~~YDi£~!iQD§ ~££~§§ ]~~hoQ (GC30-5001) or the ]~§i£ 1~1~£g~~~~jf~!jgn§ !££~§§ ~~!EQ£ (GC30-2004). Note: publication Q~ Polling list entries for remote 2260/2265 and remote 3275/3277 systems must specify a general poll. The use of a general poll allows a single entry in the polling list to invite input from all devices attached to each remote control unit or display station. In this ferm of operation, the polling list should contain only one entry for each 2845, 2848, or 3271 Control Unit or for each 3275 Display Station on the line. For 2260/2265 display systems, this form of operation is achieved by coding X'FF' as the second byte of each entry in the pelling list. For 3270 systems, this ferm of operation is achieved by using a device address code of X'7F' (EBCDIC) or X'22' (ASCII) in each polling list entry applicable to a 3271 Control Unit or 3275 Display Station. For remote 3270's, see the discussion of GENPOLL in this section and the discussion of POLLPOS in the section "Describe Terminal Types". If ANSWRBK=EXIDVEB is specified, the LISTADR operand must specify the label of a DFTRMLST macro instruction of the SWLST,AN format. The user data portion of the entries in this list must be either of the following: 1. The label of the corresponding DFHTCT TYPE=TERMINAL macro instructien for each 3735; or 2. Hexadecimal zeros for terminals that share the line with the 3735 but do net transmit unique ID sequences. For a dial-up line containing 3735'5 and other bisynchronous devices, the answering list must be coded as follows: symbol DFTRMLST SWLST,AN,xx,4,yy,zz, (authsequence,O,userdata) " , (2D,O,'lERO) * * where: symbol is the user· label specified by the LISTADR= operand of the DPHTCT TYPE=LINE macro instruction, xx,yy,zz as defined in 66 the BTAM manual, (authsequence,O,userdata) is a sublist in the answering list for each 3735 (authsequence is defined in the BTAM manual), must be specified for the control value, userdata is the label of the DFHTCT TYPE=TERMINAL entry and (2D,O,ZERO) is a sub1ist in the answering list for all non-3735 devices on the line where 2D is the ID ENQ sequence for non-3735 devices, must be specified for the control value, ZERO is the label used to represent userdata (the following statement must be coded: ZERO EQU 0). ° ° FEATURE: This oferand is used to indicate that one or more optional 66.1 features are present on a given terminal. These features can be specified in any order using the following keyword parameters: 1. 2. 3. 4. 5. 6. 7. AUTOANSR, the automatic answering capability for switched lines. AUTOCALL, the automatic calling capability for switched lines. AUTOPOLL, the automatic polling capability required for multi-point binary synchronous communication terminals and optional for the 1050 Communication system and 2740 Communication Terminal. If AUTOPOLL is specified for the 2740, SCONTROL must also be specified. CHECKING, the VRC/LRC feature on the 2740 Communication Terminal. SCONTROL, the station control feature on the 2740 Communication Terminal and on the System/7. BUFFRECV, the buffer receive capability for the 2740 Communication Terminal Model 2. If BUFFRECV is specified, SCONTROL must also be specified. KBRDLOCK, the lock option capability for the 2848 Display Control Models 21 and 22. For terminals on switched-line networks, FEATURE=AUTOANSR must always be specified. NPDELAY: Applicable only to start/stop operand is used to specify the interval between line polls (invitations) when a detected. This number can be specified default values varying by device type. poll delay". and BISYNCH devices, this of time, in milliseconds, negative response to a poll is in the range 0 to 20000, with NPDELAY signifies "negative When used with a TCAM line, this operand specifies the time interval that is to expire before control is passed to TEP when a CICS task is not ready to accept a subsequent record from the input process queues. If the CICS task issues a read before the time interval expires, processing continues normally and TEP is not notified. This number can be specified in the range of 0 to 20,000 milliseconds. The default value is o. POOLADR: This operand must be used for switched-line processing and for the local 3270 Information Display System. Used for switched-line processing, this operand specifies the label assigned to the first terminal description (DFHTCT TYPE=TERMINAL) associated with a particular pool of communication lines. POOLADR should be coded only for the first line in a given line pool; FEATURE=AUTOANSR must also be specified. Used for the local 3270 Information Display System, this operand specifies the label assigned to the first terminal description associated with a particular pool of local 3270's. FEATURE=AUTOANSR need not be specified. ANSWRBK: This operand must be coded for switched lines to specify the terminal identification to be used. If this operand is used, FEATURE=AUTOANSR must also be specified. Only one of the following keyword parameters may be specified: 1. AUTOMATIC, indicates automatic terminal identification. This parameter may be coded only for the Common Carrier Teletypewriter Exchange Terminal station (Model 33/35). 2~ TERMINAL, indicates that the terminal will be identified by the operator. This parameter may be coded for the TWX, 1050, 2740, 2741, and dial-up binary synchronous devices. (After the dial-up 67 connection has been made, the operator must enter the Terminal Identification as it appears in the Terminal Control Table.) If 3735's share the line, specify EXIDVER. 3. NULL, indicates that the terminal will not be identified by either the terminal or operator. This parameter may be coded only for the 7770. (After the dial-up connection has been made, the Terminal Control program connects this line to the next available terminal in the terminal pool.) 4. EXIDVER, not applicable to CICS/DOS-Entry, this keyword parameter indicates that the terminal's unique ID sequence will be identified by BTAM-expanded ID verification. This parameter must be coded for any line on which there is a 3735. If devices which do not transmit unique ID sequences share the line with 3735's, the non-3735 operator must enter the terminal identification after the dial-up connection has been made. BQi~: These keyword parameters are valid only if the corresponding keyword parameters have been included in the DFHSG PROGRAM=TCP,ANSWRBK=(parameters) specification during system generation. LINSTAT: The LINSTAT='OUT OF SERVICE' operand indicates that the line is to be initiated with an "out of service" status. BSCODE: This operand is used to specify the type of communication code to be used for a given binary synchronous communication device. The applicable keyword parameters are EBCDIC, ASCII, and TRANSCODE. The default is BSCODE=EBCDIC. CONVTAB: This operand is used to specify the type of transmission code, and may be used in lieu of the BSCODE operand for binary synchronous devices. The applicable keyword parameters are: 1. 2. 3. 4. 5. EBCDIC ASCII TRAN SCODE ABB ABC Extended Binary Coded Decimal Interchange Code American Standard Code for Information Interchange Six-bit transmission code ABB' code for the 7770 Audio Response unit Model 3 ABC code for the 7770 Audio Response unit Model 3 RDYMSG: Required when TRMTYPE=7770 is specified, this operand is used to specify the symbolic address of the ready message used by CICS to communicate with terminals attached to the 7770 Audio Response Unit. The ready message is defined through the DFHTCT TYPE=7770MSG macro instruction. (See the section "Define Digital Response Messages for the 7770 Audio Response unit".) ERRMSG: Required when TRMTYPE=7770 is specified, this operand is used to specify the symbolic address of the error message used by CICS to communicate with terminals attached to the 7770 Audio Response Unit. The error message is defined through the DFHTCT TYPE=7770MSG macro instruction. (See the section "Define Digital Response Messages for the 7770 Audio Response Unit".) GENPOLL: GENPOLL=YES must be specified for a multipoint binary synchronous communication line if one or more of the polling sequences in the DFTRMLST (pointed to by the label specified in the LISTADR operand) is a general poll sequence. If this operand is used, the 68 POLLPOS operand must be included in each DFHTCT TYPE=TERMINAL specification associated with the line. For TRMTYPE=2980 and TRMTYPE=3270, GENPOLL=YES is a default specification. POOLCNT: Applicable only to the CICS/OS system, this operand is used to specify the number of Terminal Control Table line entries (TCTLE's) to be included in the pool of TCTLE's for a line group comprised of local 3270 Information Display Systems. The pool of TCTLE's is used by CICS to support concurrent operations on the BTAM local line group. The number of TCTLE's specified should reflect the expected activity on the local line group and the anticipated maximum number of concurrent requests. For a local line group containing printers, the number specified should be the actual number of printers plus one to avoid locking out any screen keyboards when all printers are busy. When a READ or WRITE for a particular 3270 is issued, CICS allocates the first available TCTLE from the pool. This TCTLE is freed when the operation at the device is complete. For WRITE operations at a printer, the operation at the device is considered complete when the printing operation is complete. CICS supports as many concurrent operations on the line group as there are TCTLE's in the pool. If no TCTLE is available to support a requested operation, the request remains pending until a TCTLE becomes available. For CICS/OS, local 3270's can be arranged in line groups in any desired manner. TCTUAL: This operand is used to specify the length, in bytes (0-255), of the Process Control Information field (PCI) for all terminal entries (TCTTE's) associated with this line. The default is TCTUAL=O. If fields of different (variable) lengths are desired, the TCTUAL value can be specified in one or more DFHTCT TYPE=TERMINAL macro instructions for terminals associated with this line. In any case, the PCI field is generated for each terminal after the last terminal entry of the last line. The address of the PCI field is located at TCTTECIA; the length is located at TCTTECIL. For CICS/OS, PCI fields of fixed length (15 bytes) and/or variable length (0-255 bytes) can be specified via the TCTUA operand of the DFHSG TYPE=INITIAL macro instruction. In the case of a fixed-length PCI field (the address of which is located at TCTTECI), the TCTUAL operand need not be specified. In the case of a variable-length PCI field (the address of which is located at TCTTECIA), the TCTUAL operand should be specified in the DFHTCT TYPE=LINE macro instruction and/or DFHTCT TYPE=TERMINAL macro instruction. OUTQ: Required in all TCAM input process queue Terminal Control Table line entries (TCTLE's), the symbolic name identifies the corresponding TCAM output process queue TCTLE. Multiple input process queues may reference the same output process queue. POOL: By specifying POOL=YES on the TCAM output process queue, the POOL feature is supported for that TCAM line. The user should analyze the restrictions prior to specifying the POOL feature. For further information concerning line pool restrictions, see the section "CICS/TCAM Interface Considerations". 69 QUEUEID: This optional operand is used to specify a unique user identification for the TCAM process queue. The identification is an unframed, one-byte hexadecimal number (OO-FF) which is placed in both the input and output line entry at TCTLEQID to provide unique queue identification while executing a user exit. DESCRIBE TERMINAL TYPES The types of terminals on the system are described to CICS by the symbol DFHTCT TYPE=TERMINAL macro instruction. The expansion of this macro instruction is the Terminal Control Table terminal entry (TCTTE). These terminal definitions must immediately follow the corresponding line entry (DFHTCT TYPE=LINE). The sequential terminals (TRMTYPE=CRLP,DISK,TAPE) support only one entry each. A DFHTCT TYPE=TERMINAL macro instruction must be coded for each terminal on a line. On single dropped and multidropped terminals on non-switched lines, the DFHTCT TYPE=TERMINAL macro instruction must immediately follow the DFHTCT TYPE=LINE macro instruction. The DFHTCT TYPE=TERMINAL macro instruction entries must be contiguous for multidropped terminals on non-switched lines and for terminals in a terminal pool on switched lines. For TCAM, the user must specify a single TCTTE for the input process queue line. This may be considered to be a "dummy" TCTTE in that it does not relate to any physical terminal. On the output process queue line (TCTLE), the user identifies each terminal to be associated with that line set. Therefore, if the user has ten terminals associated with a particular TCAM process queue, he must code eleven DFHTCT TYPE=TERMINAL macro instructions; one follows the input DFHTCT TYPE=LINE macro instruction while the remaining ten follow the output DFHTCT TYPE=LINE macro instruction. The following operands can be used in the DFHTCT TYPE=TERMINAL macro instruction: symbol DFHTCT TYPE=TERMINAL, * TRMIDNT=name, * TRMPRTY=number, * TRMMODL=number,character, * TRMTYPE=1030,1050,1053,1130,2020,2260,L2260,2265, * 2740,2740/2760,2741C,2741E,2770,2780,2980, * 3275,3277,L3277,3284,L3284,3286,L3286,3735,7770, * SYS/3,SYS/7,S360,CRLP,DASD,TAPE,TWX,U/R, * CLASS=(CONV,BATCH,VIDEO,HARDCOPY,BISYNC,AUDIO), * LVUNIT=number, * LASTTRM=LINE,GACB,POOL, * TRMADDR=address,name, * TRMSTAT=(TRANSACTION,TRANSCEIVE,RECEIVE,'OUT OF SERVICE',* INPUT) , * COMPAT=NO, (number of characters,number of lines, * device type,model number), * FEATURE=(PTRADAPT,SELCTPEN,AUDALARM,COPY,BUFEXP, * DCKYBD,UCTRAN), * POLLPOS=number, * TRANSID=name, * STN2980=number, * TAB2980=number, * TIOAL=number, * TCTUAL=number 70 TRMIDNT: Used to supply a unique four-character symbolic identification to each terminal. The TRMIDNT parameter and the destination identification in the Destination control Table, when applicable, must be the same. The identification supplied will be left justified and padded with blanks to four characters if less than four characters are supplied. This is necessary as the system always searches for a four character match when searching tables. This operand may be omitted if POOL=YES is included in the DFHTCT TYPE=LINE specification. TRMPRTY: Used to establish terminal priority. This decimal value (000-255) is used in establishing the overall transaction processing priority. (Transaction processing priori ty is equal to the sum of the terminal priority, transaction priority, and operator priority, not to exceed 255.) The default is TRMPRTY=O. TRMMODL: Specifies the model number of the terminal associated with this communication line. If the device is one of the following, this operand must be included in either the DFHTCT TYPE=LINE or DFHTCT TYPE=TERMINAL specification: 1. 2. 3. 4. 5. 6. 7. Component of the 1050 Data Communication System 2740 Communication Terminal Model 2 Component of the 2980 General Banking Terminal System Component of the 3270 Information Display System 2740 Communication Terminal with 2760 Optical Image unit 2260 Display Station 2265 Display station TRMMODL=1 is used to specify the 2980 Teller Station Model 1, 3275 Display Station Model 1, 3277 Display station Model 1, 3284 Printer Model 1, or 3286 Printer Model 1. TRMMODL=1 is the default for the 3270 Information Display System. TRMMODL=2 is used to specify the 2740 Communication Terminal Model 2, 2980 Administrative Station Model 2, 3275 Display Station Model 2, 3277 Display station Model 2, 3284 Printer Model 2, or 3286 Printer Model 2. TRMMODL=4 is used to specify the 2980 Teller station Model 4. TRMMODL=5 is used to specify component polling of the keyboard for the 1050 Data Communication System using non-switched communication lines. Component selection character 5 (OB) must be coded in the polling tist (DFTRMLST). TRMMODL=6 is used to specify component polling of reader 1 for the 1050 Data Communication System using non-switched communication lines. Component selection character 6 (OD) must be coded in the polling list (DFTRMLST) • TRMMODL=7 is used to specify (1) the 2740 Communication Terminal with 2760 Optical Image Unit, or (2) component polling of reader 2 for the 1050 Data Communication System using non-switched communication lines. Component selection character 7 (OE) must be coded in the polling list (DFTRMLST). TRMMODL=O is used to specify an input component for the 1050 Data Communication System. Common polling character 0 (15) must be coded in the polling list (DFTRMLST). TRMMODL=O is the default specification for a 1050 Data Communication System. 71 The TRMMODL=character operand is used to specify the applicable screen format for a 2260/2265 Display station as follows: ~g£!fIFI~!11Qli ~~E£!lH! TRMMODL=A TRMMODL=B TRMMODL=C TRMMODL=D TRMMODL=E 6x40 12x40 12x80 15x64 12x80 FOEMA! 2260 2260 2260 2265 2265 For example, TRMMODL=A specifies a 2260 Display Station with a 6x40 screen format. TRMTYPE: This operand is used to specify the terminal type if (1) the terminal type has not already been specified in the DFHTCT TYPE=LINE macro instruction, or (2) the user wishes to override the TRMTYPE specification in the DFHTCT TYPE=LINE macro instruction. CRLP is the card reader and line printer (a pair of sequential devices simulating a terminal). DASD is the direct access device. TAPE is the magnetic tape device. A 1053 is a 1053 printer on a local or remote 2848 control unit. TWX is the Common Carrier Teletypewriter Exchange Terminal Station (Model 33/35). U/R is a general term that refers to any reader, printer, or punch. CLASS: This operand is used to indicate the device classification associated with a particular line. The applicable keyword parameters are: 1. 2. 3. 4. 5. 6. CONV BATCH VIDEO HARDCOPY BISYNC AUDIO Device with conversational type application Data collection type device Device with cathode ray tube Start/stop hard-copy device Binary synchronous device Audio response device LVUNIT: This operand is applicable only when TRMTYPE=L2260, TRMTYPE=L3277, TRMTYPE=L3284, or TRMTYPE=L3286 is specified, or when TRMTYPE=1053 is specified for a local 2260 line. LVUNIT specifies a decimal number from 1 to N which is used to identify the local video unit. The maximum value of N for local 2260 is 25. For local 3270, N maximum is 32 (use of Assembler D restricts N to a maximum of 31). For the CICS/DOS systems r the LVUNIT specification indicates the local video unit's relative position in the corresponding DFHTCT TYPE=SDSCI, LINELST=parameter specification. For the CICS/OS system, the LVUNIT specification indicates the local video unit's relative position in the concatenation of data definition (DD) statements for the corresponding DFHTCT TYPE=SDSCI specification. LASTTRM: This operand is used to indicate a "last terminal" condition. The applicable keyword parameters are: 1. 2. 72 GACB, used for GAM onlYr identifies both the last terminal entry on a given line entry and the last terminal entry on a graphics attention control block. LINE, used for BTAM non-switched line processing (except local 3270), BGAM (if GACB conditions do not apply), and TCAM (if POOL=YES has not been specified). / 3. PCOL, used for ETAM switched-line processing, for the local 3270 Informatien Display System, and for TeAM, identifies the last terminal in the pool. For TCAM, ECOL is use~ if ECOL=YES has been specified. TRMADDR: The TRMADDR=address operand specifies the device address associated with a given terminal and is required only for BTAM devices. (This operand is not required for some BTAM output devices; for example, a dial-up 2741.) Fer most non-switched lines, the hexadecimal addressing characters associated with the terminal must be specified. (This operand should not be used if the devices are local 2260's or local 3270's). For either binary synchronous devices or switched lines, the label of the BTAM DFTRMLST must be specified using the TRMADDR=name operand. ]Q1~: For a 3735, the BTAM DFTRMLST must be of the SWLST,AD type. For a TWX, TRMADDR is not required if ANSWRBK=TERMINAL is specified on the DFETCT TYPE=LINE macro instruction. ~RMS!AT: Specifies the type of activity that may occur at a given terminal. This terminal status is initially set in the TCTTE and is a combination of the processing status and the service status. possible status designaticns are TRANSACTION, TRANSCEIVE, RECEIVE, INPUT and/or 'aU! OF SERVICE'. A terminal with TRANSACTTON status is used in the processing of transactions such as inquiries or erder entries. A display station is normally classified as a TRANSACTION terminal. A hard-copy terminal to which no messages are sent withcut a terminal request and through which transactions are entered is a TRANSACTION terminal. If no other status designatien is made, the terminal status defaults to TRANSACTION. A terminal with TRANSCEIVE status is a TRANSACTION terminal but one to which messages are sent automatically by the user. The automatic transaction initiation created by a transient data destination reaching a trigger level sets a condition in an appropriate Terminal Control Table terminal entry. If the terminal status is TRANSCEIVE and if there is no transaction at the terminal, Terminal Control initiates the user-defined task. This task is expected to send messages to the terminal. A terminal with RECEIVE status is one to which messages are sent but from which nc input is allowed. An example of this type of terminal is one which is located in a remote location, such as a warehouse, is unattended, but may receive messages. No!~: RECEIVE should be specified for a System/7 with the station Centrol feature. This allows polling to be suspended until the System/7 is IPL'd by the host, at which time the status is changed to TRANSCEIVE. If the System/7 is IPL'd remotely, the master ter~inal must be used to change the terminal status to enable the System/7 to transmit. A terminal with INPUT status is one which can send messages to CICS tut cannot receive messages from CICS. ]Q!~: System messages may be routed to input terminals under certain ccnditions (e.g., Invalid Transaction Identification, ATP batch count) causing DFHTACP to be scheduled. For this reason, the user should code a Terminal Error Program (DFHTEP) to perform any user-required action. See DFHTEP Programming Considerations. 73 A terminal with an 'OUT OF SERVICE' designation is one which can neither receive messages nor transmit input. such terminals are not polled by CICS. The 'OUT OF SERVICE' parameter can be used in combination with TRANSACTION, TRANSCEIVE, or RECEIVE; if such a co.bination is nct specified, the terminal status defaults to TRANSACTION. All terminals except the master terminal can be designated as 'OUT OF SERVICE'. When appropriate, the terminals can be placed IN SERVICE by the master terminal and polling is resumed. COMPAT: This operand is used to indicate that the 2260/2265 terminal or 1053 printer specified in the "device type" parameter is to be simulated on the 3270 Information Display System. The keyword parameters are positional and must be replaced by a comma if they are omitted. The default is COMPAT=NO. The "number of characters" parameter is used to specify the screen Applicable parameters are 240, 480, and 960. size of the 2260/2265 terminal. The "number of lines" parameter is used to indicate the number of lines applicable to the 2260/2265 terminal or to insert new line (Nt) symbols into the 3284/3286 printer output data stream where Nt symbols are not provided by the user in the output data stream. Applicable parameter values are 6, 12, and 15. The default value for a 960-character screen is 12. The "device type" parameter is used to specify either a 1053, 2260, L2260, or 2265 terminal. The default is 2260. Note that the specification COMPAT=(960,15) results in an error condition since the 2260 (as~umed by default) cannct support 15 lines. The "model number" parameter is used to specify a model number for the 2260 terminal being simulated. This parameter provides an interface for any user-written application programs that currently test the TCTTEMN field before building device-dependent 2260 data streams. For further informaticn concerning the use of the COMPAT operand, see the section "2260 Ccmpatibility for the 3270". FEATURE: This operand is used to specify applicable features for the 3270 Infcrmation Display System and corresponding 3284 Printer Model 3 on the 3275 Display station. FEA!UBE=PTRADAPT specifies the Printer Adapter feature and corresponding 3284 Printer Model 3 on the 3275 Display Station. Note that a separate DFHTCT TYPE=TERMINAt macro instruction cannot be coded for the 3284 Printer Model 3 because the 3284 Model 3 shares the buffer of the 3275 Display Station. FEATURE=SELCTFEN specifies the Selector Pen feature for a 3275 Display Station or a 3277 Display Station. FEATURE=AUDAtARM specifies the Audible Alarm feature for a 3275 tisplay Station or a 3277 Display Station. FEATURE=COPY specifies the Copy featUre for a 3277 Display Station, 3284 Printer, or 3286 Printer attached to a 3271 Control unit. FEATURE=BUFEXP specifies the Buffer Expansion feature (RPQ835503) for the 2980 General Banking Terminal System. Applicable only to the 74 first terminal ~ntry of a control group, the BUFEXP parameter increases the statien buffer size to 96 characters. FEATURE=DCKYBD specifies the typewriter keyboard and/or operator censole keyboard for a 3275 Display station or a 3277 Display station. Both uppercase and lowercase data can be transmitted with either of these keyboards. 'FEATURE=UCTRAN specifies translation of all lowercase data to uppercase. If FEATURE=UCTRAN is specified, the EBCDIC and/or ASCII parameter must be specified through the UCTRAN operand of the DFHSG fROGRAM=TCP macro instruction. For further informatien concerning the use of the FEATURE operand, see the section "2260 Compatibility for the 3270". FCLLPCS: This operand is used to specify, as a decimal integer, the position (relative to 1) of the FoIling characters associated with this terminal in the DFTRMLST supplied for the line. If GENPCLL=YES is specified (or implied by default) for the line entry, POLLPOS=1 is specified for each terminal entry associated with control unit 1, FOtLPOS=2 is specified for each terminal entry associated with control unit 2, etc. TRANSID: The TRANSID operand is used to specify a four-character transaction code whose use is dependent upon the terminal type for which it has been specified. If the access method being used is TCAM, the TRANSID operand is applicable only to Terminal Control Table terminal entries associated with the TCAM output queue. For the 2740 Communication Terminal/2760 Optical Image unit combination (TRMTYPE=2740,TRMMODL=7), the TRANSID operand is used to specify the transacticn code of the transaction that is to be initiated when input is received from the 2760 and there is no active task. If input is received from the 2740, the first four characters of the input data stream are used as the transaction code. For the 3735 Programmable Buffered Terminal, the TRANSID operand is used to specify the transaction cede of the transaction that is to be initiated,for a batch transmission initiated by the terminal operator. If an inquiry message is received from the 3735, the transaction code used consists of the first four characters following the inquiry header (NULL I NULL). See Appendix G for an example of a user-written 3735 transaction. For all other terminals, the TRANSID operand is used to specify the transacticn code of a transaction that is to be initiated each time input is received from the terminal and there is no active task. If the TRANSID operand is omitted, the first fbur characters of the data passed in the TIOA, or, in the case of a formatted 3270 data stream, the four characters fellowing the first Set Buffer Address (SBA) order sequence, are used as the transaction code unless a TRANSID specification has been made in a DFHPC TYPE=RETURN request issued by the previous transaction. The transaction code used is the one supplied by the last specification of the TRANSID operand in the DFHPC macro instruction. The TFANSID oFerand is required for the following terminals. 1. 2. 1030 Badge Reader 2740 communication Terminal/2760 Optical Image unit combination 75 3. 3735 programmable Buffered Terminal if batched input processing is required STN2980: This oFerand is used to specify the station for which the alternate station address and no~mal station address are to be generatec for each terminal entry in the Terminal Cont~ol Table corresponding to a 2980 General Banking Terminal System. In response to a given STN2980 specification, an aFFropriate (hexadecimal) alternate station address and normal station address are generated by CICS as follows: ]~RM!1 40 F1 F2 F3 F8 5C 61 E2 E3 E8 !L1]]]!1] F4 F5 F6 F7 34 E4 E5 E6 E7 24 ~~!11Qli 0 1 2 3 4 5 6 7 8 9 For example, for normal station address X'40', the user specifies STN2980=0 ana the alternate station address X'F4 1 is generated. TAB2980: This operand is used to specify, as a single-digit hexadecimal value (O-F), the number of tabs to the passbook area as defined by the user and physically (uniquely) set on the terminal. The default is TAB2980=0. TIOAL: Applicable only to terminals on binary synchronous lines, this operand is used to specify the minimum size of the Terminal Input/Output Area (TIOA) to be passed to a transaction by the Terminal Control program. If the size of an input message exceeds the value specified in this operand, the size of the TIOA corresponds to the size of the message. ]ot~: The minumum size TIOA passed to a transaction which is running under cont~ol of 2260 Compatibility is governed by the CMPT60L operand in the generation of the Terminal Control program. TCTUAL: This ope~and is used to specify the length, in bytes (0-255), of the Process Centrol Information field (PCI) for this terminal. The default is the TCTUAL value specified in the DFHTCT TYPE=LINE macro instruction; if not specified in the DFHTCT TYPE=LINE macro instruction, the default is TCTUAL=O. DEFINE DIGITAL RESPONSE MESSAGES FOR 7770 AUDIO RESPONSE UNIT For CICS to communicate with an aUdio terminal (for example, the 2721 Portable Audio Terminal), two digital response messages (an error message and a ready message) must be defined in the Terminal Control Table for each line. This is accomplished by issuing the symbol DFHTCT TYPE=7770MSG, MESSAGE='message' * macro instruction, which must immediately precede the DFHTCT TYPE=FINAL macro inst~uction. To avoid confusion, these messages should be unique; 76 that is, these messages should not also be defined in applicaticn ~rograms. user-writt~n The ready message is used by CICS: 1. 2. 3. 4. In response to a valid Terainal Identification being entered subsequent to line ccnnection. When the sign-on sequence has been completed. When a 7770 Audio ResFonse Unit is connected to a line and no transaction is associated with the 7770. In response to a READ request if the request sequence was not a IoIRITE, READ. The error message is used by CICS: 1. 2. 3. 4. S. 6. 7. In response to an invalid ~erminal Identification being entered subsequent to line ccnnection. When a valid Terminal Identification has been entered but (1) the terminal has an "out of service" status, or (2) the terminal has an "in service" status but the Terminal Identification has already been entered on another line. In resFonse to an invalid Transaction Identification. In response to an error during the sign-on/sign-off sequence. If the input message is teo long. If the transaction associated with the 7770 is abnormally terminated. If a 32-second timeout occurs, or if a five-second time out occurs while entering infermation required by CICS. MESSAGE: This operand is used to define digital response messages for the 7770 Audio Response Unit. These messages must be constructed in the form of hexadecimal constants, enclosed within single quotes, and may contain up to 48 hexadecimal digits (24 bytes). The first two digits must contain binary zeros (00) to represent a one-byte "silence" track address on the 7770; subsequent digits may be used to represent up to 23 additional one-byte 7770 track addresses. Por further details, see the publicaticn ~Q~!~~~n~ ~g§~!!E~iQn l11Q ~~giQ B§§fon~~ Uni1 ]Qg~1 ~ (GA27-2712). I See Appendix B for an example of a typical digital response specification. I SPECIFY END OF TERMINAL CONTROL TABLE I The end of the Terminal Control Table is indicated to the control system by the I, DFHTCT TYFE=FINAL macro instruction, which must be contained on the last control card for the Terminal Ccptrol Table assembly. An Assembler END card that includes the label DFHTCTEA must te Frovided by the user to end the assembly. 77 TERMINAL CONTROL TABlE EXAMPLE Figure 2 illustrates the coding that is required to create a CICS Terminal Control Table. The terminal network described includes: 1. 2. 3. 4. ]Q!~: One DASD Two 2260 Two 2740 feature Two 1050 sequential terminal Display Stations and one 1053 printer (local attachment) Telecommunication terminals with the Station Control Data Communication terminals (dial-up) DFTRMLST macro definitions are required by BTAM devices. These entries should be coded immmediately preceding DFHTCT TYPE=LINE entries or immediately following DFHTCT TYPE=TERMINAL entries. To be applicable to CICS/OS, or if converting from CICS/DOS to CICS/OS, the fcllowing changes must be made to Figure 2: • The DDNAME o~erand must be included unless the name specified in the tSCNAME o~erand is an acceptable default. • The MODE, MACRY and NCP operands must be included unless the respective default values for these operands are acceptable. • The FLNNAME operand must be included to specify the name of the first communication line entry defined by the DFHTCT TYPE=LINE macro instruction. If converting from CICS/DOS to CICS/OS, operands applicable only to CICS/DOS need not be removed, since they are ignored by CICS/OS. For other examples of Terminal Control Appendix B. 78 ~able preparation, see DFHTCT TYPE=INITIAL DFHTCT TYPE=SDSCI, DEVADDR=SYS001, DEVICE= 2314, DSCNAME=DISKIN1 DFHTCT TYPE=SDSCI, DEVADDR=SYS006, DEVICE=2314, DSCNAME=DISKOT1 DFHTCT TYPE=LINE, ACCMETH=SEQUENTIAL, TRMTYPE=DASD, ISADSCN=DISKIN1, OSADSCN=DISKOT1, INAREAL=80 DFHTCT TYPE=TERMINAL, TRMIDNT=SAMB, TRMPRTY=11, TRMSTAT=TRANSCEIVE DFHTCT TYPE=SDSCI, CU=2848, DEVICE=L2260, LINELST=(037,038,039) , SWITCH=NO, DSCNAME=DTF60L DFHTCT TYPE=LINE, ACCMETH=BTAM, TRMTYPE=L2260, DSCNAME=DTF60L, INAREAL=960 DFHTCT TYPE=TERMINAL, TRMIDNT=L60A, TRMPRTY=64, LVUNIT=1 DFHTCT TYPE=TERMINAL, TRMIDNT=GAMB, TRMPRTY=63, L.VUNIT.=2 DFHTCT TYPE=TERMINAL, TRMIDNT=L600, TRMTYPE=1053, LVUNIT=3, TRMPRTY=32, TRMSTAT=RECEIVE, LASTTRM=LINE DFHTCT TYPE=SDSCI, CU=2703, DEVICE=2740, FEATURE=(STC,CHK), LINELST= (027) , SWITCH=NO, DSCNAME=DTF40MD Figure 2 (Part 1 of 2). START OP TCT SPECIFY DATA SET CONTROL INFORMATION * * * SPECIFY DATA SET CONTROL INFORMATION * * * DASD LINE ENTRY * * * * * * * * * * DASD TERMINAL ENTRY DASD SYMBOLIC NAME SPECIFY DATA SET CONTROL INFORMATION * * LOCAL 2260 LINE ENTRY 2260 TERMINAL ENTRY 2260 SYMBOLIC NAME * * * * * ** * FIRST UNIT ON A DTF 2260 TERMINAL ENTRY 2260 SYMBOLIC NAME * * * * * ** SECOND UNIT ON A DTF 1053 TERMINAL ENTRY THIRD UNIT ON A DTF * * SPECIFY DATA SET CONTROL INFORMATION Coding for terminal control table 79 * * * * * * PL2740L1 DFTRMLST OPENLST,(46,45) POLL LIST TERMINAL DFHTCT TYPE=LINE, 2740 LINE ENTRY * ACC~lETH=,.BTAM , TRMTYPE=2740, * TRMMODL=1, * DSCNAME=DTF40MD, * BTAMRLN= 1, * LISTADR=PL2740L1, POLL LIST NAME * INAREAL=240, FEATURE=(SCONTROL,CHECKING) DFHTCT TYPE=TERMINAL, 2740 TERMINAL ENTRY * TRMIDNT=T41L, 2740 SYMBOLIC NAME * TRMADDR=46, TERMINAL ADDRESS = L * TRMPRTY=127, * TRMSTAT=TRANSCEIVE DFHTCT TYPE=TERMINAL, 2740 TERMINAL ENTRY * 2740 SYMBOLIC NAME TRMIDNT=T41K, * TRMADDR=45, TERMINAL ADDRESS = K * TRMPRTY=128, * TRMSTAT=TRANSCEIVE, * LASTTRM=LINE LAST TERMINAL ON LINE SPECIFY DATA SET CONTROL DFHTCT TYPE=SDSCI, * CU=2703, INFORMATION DEVICE=1050, * LINELST= (031) , * SWITCH=YES, * DSCNAME=DTF1050 IDL1050 DFTRMLST DIALST,O, (6215,6415) DIL1050A DFTRMLST DIALST,7,1239876, (6213) DIL 10 SOB DFTRMLST DIALST, 7,1239875, (6413) DFHTCT TYPE=LINE, 1050 LINE ENTRY * ACCME TH=BTAM, TRMTYPE=1050, ** DSCN AME= DTF 1050, INAREAL=80, * BTAMRLN=1, * LISTADR=IDL1050, POLL LIST NAME * FEATURE=(AUTOANSR,AUTOCALL) , POOLADR=T50POOL, * ANSWRBK=TERMINAL T50POOL DFHTCT TYPE=TERMINAL, 1050 TERMINAL ENTRY * TRMIDNT=T50A, * TRMADDR=DIL1050A, * TRMPRTY=203, TRMSTAT=TRANSCEIVE 1050 TERMINAL ENTRY DFHTCT TYPE=TERMINAL, * TRMIDNT=T50B, TRMADDR=DIL1050B, * TRMPRTY=204, TRMSTAT=TRANSCEIVE, * LASTTRM=POOL LAST TERMINAL ON LINE DFHTCT TYPE=FINAL END OF TCT END DFHTCTBA POINT TO REQUIRED ENTRY LABEL * * * * * * * * Figure 2 (Part 2 of 2). Coding for terminal control table The File Control Table is used to describe to CICS any user data sets (f iles) that are processed by file management. (Note that sequential data sets should be defined as extrapartition destinations using the DFHDCT macro.) The DFHFCT macro instruction is used to generate entries in the table and to request the following services: 80 1. 2. 3. 4. Set up the open list for the data sets to be used when initializing and terminating the system. Describe characteristics of the data sets, such as access method used, record characteristics, types of service allowed. Define use of the data set as a cross index and provide the information to locate the next data set via indirect access. Define the segments and segment sets of a record. The data control information for each data set is included in the DFHFCT macro instruction. The indirect access and segmenting services are mutually exclusive; the entry for one data set cannot specify both services. The following operands can be included in the DFHFCT macro instruction: DFHFCT TYPE=INITIAL, SUFFIX=xx * DFHFCT TYPE=DATASET, DATASET=name, ACCMETH=BDAM,ISAM,DL/I, SERVREQ=(GET,PUT,UPDATE,NEWREC,INDACC,SEGMENT,BROWSE, KEY, NOEXCTL) , BLKKEYL=decimal value, EXTENT=number, CYLOFL=number, INDAREA=symbolic name, IN DSIZE=number, INDSKIP=YES, MSTIND=YES, NRECDS=number, IOSIZE=number, IOWORK=symbolic name, DEVICE=(n,m), SRCHM=YES,number, VERIFY=YES, RELTYPE=DEC,HEX,BLK, LRECL=(length,length) , BLKSIZE=(length,length) , RK P=nu mber , RECFORM=(format,characteristic,DCB record format), OPEN=INITIAL,DEFERRED, KEYLEN=length * * ** * * * * * ** * * ** * * * * * * * * * DFHFCT TYPE=INDACC, OBJDSID=name, IARLKP=number, IALKFL=length, IADADMI=RELREC,KEY, IADIII=hexadecimal character, DUP DS I D= n am e * DFHFCT TYPE=SEGHEAD, SEGLENG=length, INDDISP=number, TSEGIND=BIT,DISPLACEMENT * DFHFCT TYPE=SEGDEF, SEGNAME=name, SEGCHAR=(format,alignment) , S E GLENG=l ength * * * ** * * * * * 81 DFHFCT TYPE=SEGSET, SEGSET=name, SEGNAME=(name1, ••• ,nameN) * * DFHFCT TYPE=SEGLAST DFHFCT TYPE=F1NAL DFHFCT TYPE=LOGICMOD ESTABLISH CONTROL SECTION FOR FILE CONTROL TABLE The control section into which the File Control Table is assembled is established by means of the DFHFCT TYPE=INITIAL, SUFFIX=xx * macro instruction, which must be coded as the first statement in the source deck used to assemble the File Control Table. SUFFIX: This operand specifies a two-character alphameric suffix (other than 'NO' which is reserved) for the File Control Table being assembled. This suffix, if specified, is appended to the standard module name (DFHFCT) and is used to name the module on the linkage editor output library. If this operand is omitted, a suffix is not provided. DESCRIBE DATA SET FOR FILE MANAGEMENT The physical characteristics of a data set are described to CICS File Management by the DFHFCT TYPE=DATASET macro instruction. This macro instruction includes provide information abou~ the access method, record and the types of service allowed for the data set. is used to generate a DTF for CICS/DOS or a DCB for operands that characteristics, This information CICS/OS. If the DL/I facility of the IBM Information Management System (IMS/360) is to be accessed under CICS/OS, the DFHFCT TYPE=DATASET macro instruction is used to provide information about Data Language/I (DL/~ data bases. In this c~se, DATASET and ACCMETH are the only operands required. Physical characteristics of the DL/I data bases need not be specified since they are specified during generation of 1MS Data Base Descriptions (DBD's). The DFHFCT TYPE=DATASET macro instruction can include the following operands: DFHFCT TYPE=DATASET, DATASET=name, ACCMETH=BDAM,ISAM,DL/I, SERVREQ=(GET,PUT,UPDATE,NEWREC,INDACC,SEGMENT,BROWSE, KEY, NOEXCTL) , BLKKEYL=decimal value, EXTENT=number, CYLOFL=number, INDAREA=symbolic name, INDSIZE=number, INDSKIP=YES, MSTIND=YES, 82 * * * * * * * * * * * * N.RECDS=number, IOSIZE=number, IOWORK=symbolic name, DEVICE=(n,m) , SRCHM=YES,number, VERIFY=YES, RELTYPE=DEC,HEX,BLK, LRECL=(length,length), BLKSIZE=(length,length) , RKP=number, RECFORM=(fcrmat,characteristic,DCB record format), OPEN=INITIAL,DEFERRED, KEYLEN=length * * ** * * ** * * * * DATASET: Specifies the synbelic data set name te be used as the File Centrol Table entry fo~ a specific data set. This data set name can consist cf from one to seven characters in the CICS/DOS systems or from one to eight characters in the CICS/OS system. Since this data set name is used when generating the operating system control block (DCB/bTF), it must be the same as the DOS file name or the as DDNAME used in the job control statement defining the data set. For a DL/I data base the DATASET operand must specify the same data rase name as was specified in the Program Communication Block (PCB) statements of Program Specification Block (PSB) generation (PSBGEN). ACCMETH: Specifies the method of organizatien for a specific data set. ACCMETH=ISAM, ACCMETH=BDAM, or ACCMETE=DL/I must be specified. SEFVREQ: Used to define the types of service request that can be Frocessed against the data set. The parameters that can be included are as fellows: ', .. 1• 2. 3. 4. 5. 6. 7. 8. 9. ]Q1g~ GET PUT UPDATE Records on this data set may be read. Records may be written on this data set. Records may be updated on this data set. UPDATE requires that GET and PUT also be specified. NEWREC Records may be added to the data set. NEWREC requires that PUT also be specified. NEWREC must be specified for OS ISAM data sets with variable-length records if updating is to be performed. INrACC Data set is used as a cross index. If INrACC is specified, the DFEFCT TYPE=INrACC macro instruction must be coded immediately fellowing this DATASET definition. SEGMENT Records are segmented. If SEGMENT is specified, the DFHFCT TYPE=SEGHEAD, DFHFCT TYPE=SEGDEF, DFHFCT TYPE=SEGSET, and DFHFCT TYPE=SEGLAST macro instructions mu.st be coded immediately following this DATASET definition. BROWSE Records may be sequentially retrieved from the data set. When BROUSE is specified, DFHFCT TYPE=LOGICMOD must also be specified. KEY Records are to be retrieved by key from DAM data set. This parameter should be specified only if ACCMETH=BDAM. NCEXCTL Records are net te re placed under exclusive control when a read for update is requested. Unless this parameter is specified, a read-for-update will cause the record to be Flaced under exclusive central (within the crcs partition/region). INrACC and SEGMENT cannot both be coded for the same data set. 83 ·A data set used as a cross-index data set may not be defined as blocked BtAM. BIKKEYL: Specifies a decimal value from 1-255 which represents the physical key length for a direct access record. This operand must always be specified for ISAM data sets and DAM data sets with physical keys. If a DAM aata set contains blocked records, and deblocking is to be performed by using a logical key (that is, a key embedded within each logical record), the logical key length is specified by using the KEYLEN operand. If records are to be placed under exclusive control during update operations, the physical key may not exceed 225 bytes. EXTENT: Applicable only to the CICS/DOS systems, this operand represents the maximun number of extents that are specified for a data set. This operand is required if ACCMETH=ISAM. EXTENT=2 represents a minimum value (one for prime data area and one for cylinder index). If ACCMETH=BDAM, the presence of the EXTENT operand indicates that relative addressing (as opposed to actual addressing) is being used and the BELTYPE cperand must also be used. CYLOFL: Applicable only to the CICS/DOS systems, this operand is required only if ACCMETH=ISAM. It is used to specify the number of tracks per cylinder which are reserved for cylinder overflow records. INDAREA: This operand is applicable only if ACCMETH=ISAM and specifies the unique symbolic r.ame which is used by the DFHFCT macro to automatically generate a main storage area (within the File control Table) that will contain all or part of the cylinder index. This operand is required only if the cylinder index is to be processed in main storage. INDSIZE: This operand specifies the length (in bytes) of the cylinder index area specified in the INDAREA operand. The minimum number of bytes can be calculated as: (m+3) (keylength + 6) where "m" is the number of entries to be read into main storage at one time, 3 is the number of dummy entries, and 6 is an abbreviated pointer to the cylinder. If m is set to the number of prime data cylinders + 1, all of the cylinder index is read into main storage at one time. This operand is applicable only if ACCMETH=ISAM and the INDAREA operand is specified. INDSKIP: Applicable only ~o the CICS/DOS systems, the INDSKIP=YES operana indicates that the index skip feature is to be used if index entries reside in main storage. This operand is applicable only if ACCMETH=ISAM and the INDAREA operand are specified. MSTIND: Applicable only to the CICS/DOS systems, the MSTIND=YES operand indicates that a master index exists for the ISAM data set. This operand is applicable only if ACCMETH=ISAM and should be specified only if a master index exists for the data seti. NR!CDS: This dperand specifies the number of logical records in a block, and is called the blocking factor. This operand is applicable only to the CICS/DOS systems and only if ACCMETH=ISAM, and should be 84 specified only if the records are blecked. For DOS ISAM data sets with variable-length records within fixed-length blocks, this number has no relation to the actual number of records within the block. However, the number specified multiFlied by the LRECL parameter must equal the actual block size en the data set. rOSIZE: !his operand specifies the number of bytes in the main storage arEa used when acding records to an ISAM data set. This operand should be used only when SERVREQ=NEWREC is also specified. For CrCS/DOS systems, this operand causes a static work area to be generated as part of the PCT entry for the data set being defined. For the CICS/OS system, the rOWORK oFerand must also be used to supply a symbolic name te be associated with the work area. Por further details, refer to DTFrs generaticn in the publication, ~Q2 2YQ§~Yi§Q~ ~ng lLQ ~~~Q§ (GC24-5031) or ISAM data set processing in the publication, Q2 ]~1~ ~gngg§ID~n! 2§~~j~~§ (GC26-3746). ]Q!g: Under CrCS/DOS with multi FIe ISAM files, whenever NEWREC services are requested and some files specify rOSIZE while ethers do not, two ISAM logic modules will be link-edited into the system. To prevent this, specify IOSIZE for all ISAM files requesting NEWREC services. IOWORK: Applicable only to the crcS/OS-STANDARD system, this operand is used to specify the symbolic name of a main storage work area to be used by the acc~ss method when adding records to ISAM data sets. If the data set contains variable-length records, this operand must be specified. It is permissible for the same symbolic name to be specified in more than one data set definition, thus causing an area to be shared. CICS prevents the shared area from being used concurrently by more than one transaction. A static work area is generated within the PCT for each unique symbclic name encountered during PCT generation. The size of each area is equal to the largest IOSIZE specified for each symbolic name. DEVICE: Applicable only to the CICS/DOS systems, the DEVICE=(n,m) oFerand is used for both DAM and ISAM data sets. "n" and "m" specify 2311, 2314, 2321, or 3330. For DAM, "n" specifies the device type on which the data set resides. ("m" dces not apply to DAM.) Por rSAM, "n" specifies the device type on which the prime data area (and overflow area if present) reside. For ISAM, "m" specifies the device type containing the high-level index. If this operand is omitted, the default is DEVICE=(2314,2314). SRCHM: This operand is aFplicable only to DAM keyed data sets and provides for a multiple track search for keyed records. If this operand is omitted, multiple track search does not occur. For CrCS/DOS systems, SRCHM=YES is the only allowable form of the operand. If fixed-length keyed records are to be added to the file, SRCHM=YES must be specified. For the CICS/OS system, SRCHM=number is the only applicable form of the operand, where "number" represents the number of tracks or blocks to be searched. The default is SRCHM=O. For further details, see the SRCHM operand under DTFDA generation in the publication, ~Q§ 2~Q~!V~§Q~ Eng lLQ Hg£~Q§ (GC24-5031) or BDAM 85 data set processing in the publication, (GC26-3746) • Q2 Q212 ~2nsg~m~n! ~~r!i£~§ The VERIFY=YES operand indicates that the user wants to check VERIFY: the parity of disk records after they are written. If this operand is omitted, records are not verified after a write request. RELTYPE: This operand applies only to tAM data sets and specifies that relative addressing is being used in the block reference portion of the Record Identification field. If the RELTYPE operand is omitted, absolute addressing is assumed (that is, MBBCCHHR). If RELTYPE=DEC, the zoned decimal format is being used. If RELTYPE=HEX, the hexadecimal relative track and record format is being used. If RELTYPE=BLK (Crcs/os only), relative tlock addressing is being used. For further details, see "Data Base Considerations" in the CICS Application Programmer's Reference Manual (SH20-1 0 47) • IRECL: Specifies the maximum length (in bytes) of the logical record. For DOS ISAM data sets with variable-length records within fixed-length blocks, this numter has no relation to the actual length of any logical record. However, the number specified, multiplied by the NRECDS parameter, must equal the actual block size on the data set. This operand must always be specified. For CICS/DOS, this operand should contain only one value (parameter). This value should not be enclosed within parentheses. If the user of CICS/OS wishes to have a LRECL value generated in the DCE, he must specify that value in the second parameter of the operand; for example, LRECL=(50,50), where the first "50" pertains to the FCT and the second "50" pertains to the DCB. If the second parameter is not specified, the DCB is generated without a LRECL value. If the data set is BtAM organized, the second parameter should n~Y~r be specified. ]Q!~~ NRECDS=1,LRECL=blocksize, is not allowed. The most advantageous specification is NRECDS=2,LRECL=(blocksize/2). BIKSIZE: Specifies the length (in bytes) of the block. If blocks are variable-length, the length specified should be the maximum block length. If the NEWREC or BROWSE operands are used for DAM fixed-length data sets with keys, BLKSIZE must be (LREeL + BLKKEYL) for unblocked records or (LRECL * BLOCKING FACTOR + ELKKEYL) for blocked records. If blocks are undefined, for CICS/OS the length specified should be the maximum block length, for CICS/DOS the length should be the maximum block length + 8. This operand must always be specified. For CICS/DOS, this operand. should contain only one value (parameter). This value should not be enclosed within farentheses. If the user of CICS/OS wishes to have a BLKSIZE value generated in the DCE, he must specify that value in the second parameter of the operand; for exaRple, BLKSIZE=(250,250), where the first "250" pertains to the FCT and the second "250" pertains to the DCB. If the second paramete~ is not specified, the DCB is generated without a BLKSIZE value. The DCB value (second parameter) should always specify the true block size while the FCT value (first parameter) may, for DAM data sets, include the BLKKEYL value. In no case should the first BLKSIZE value specified, be less than the actual blocksize of the data set. 86 RKP: Specifies. the starting position of the key field in the record relative to the beginning of the record (position zero for DAM and rSAM data sets except position one for DOS ISAM data sets). with variable-length records, this operand must include the four-byte LLbb field at the beginning of each logical record. This operand must always be specified for data sets that have keys within each logical record or when crowsing. ]g.:t.§: SEBVREQ=EROWSE requires embedded keys in 'the data field in DOS ISAM, therefore the RKP parameter is required. In DOS ISAM, if records are unblocked, the following MNOTE will be generated in the DTFIS: O,'KEYLOC INVALID,PARAMETER IGNORED'. RECFORM: Describes the format and characteristics of records on the data set. If this operand is omitted, the default is UNDEFINED. For CrCS/DOS, if NEWREC is specified for undefined records, BLKSIZE must include an additional eight bytes for the ceunt field. The fermat of the data set is described using one of the following parameters: 1. 2. 3. FIXED VARIABLE UNDEFINED Records are fixed length. Records are variable length. Records are of undefined length. The characteristic of the data set is specified using one of the fcllowing parameters: 1. 2. ELCCKED UNBLOCKED Records are blocked. Records are not blocked. If the user of crcs/os wishes to have the record format specified in the DCB, he must specify that value in the third parameter of the operand; for exareple, RECFCRM=(FIXED,BLOCKED,FBS). If the third parameter is not specified, the record format is not specified in the DCB. ]Q!~: For CICS/OS ISAM data sets with BROWSE option specified, a DCB RECFM parameter of VB or FB is always generated regardless of whether or not the data set is blocked. OPEN: The OPEN operand is used to specify the initial status of the data set. OPEN=INITIAL causes the data set to be opened by System Initialization, while OPEN=DEFERRED will not open the data set until the user indicates he wishes it opened by using the Master Terminal Open/Close service function or the use of a DFHOC macro instruction in an applicatien prcgram. If this oFerand is omitted, the default is CFEN=INITIAL. KEYLEN: The KEYLEN operand is used to specify the length of the logical key for the deblecking of DAM data sets. This key is usually embedded and located through use of the RKP operand. The length of the recorded (physical) key for DAM and ISAM data sets is specified in the ELKKEYL oFerand, and may be different from the value specified for KEYLEN. This operand must always be specified when logical keys are used. DESCRIBE CBOSS-INtEX tATA SET RECOBD The record on a cross-index data set that points to the next data set to be read is describ8d using the 87 DFHFCT TYPE=INDACC macro instruction. This macro instruction may also contain information regarding duplicate records which may be referenced by this index record, including a pointer to a duplicate data set which contains additional identifying information. If this macro instruction is used, the SERVREQ operand of the DFHFCT !YPE=DA!ASET macro instruction must include GET and INDACC. For further information on indirect accessing, refer to "Data Base Considerations" in the CICS Application Programmer's Reference Manual (SH20-1047). The DFHFCT TYPE=INDACC macro instruction Can include the following cperands: DFHFCT TYPE=INtACC, OBJDSID=name, IARLKP=number, IALKPL=length, IAIADMI=RELREC,KEY, IADIII=hexadecimal character, DUPDSID=name * * * * * OBJDSID: specifies the name of the data set referenced by the cross-index data set record. This name can consist cf from one to seven characters in the CICS/DOS systems or from one to eight characters in the CICS/OS system. This operand must always be specified. IABLKP: specifies the relative location within the cross-index data set record of the Record Identification field which is to be used to access the object data set. The displacement is relative to the beginning of the record (position zero). This operand must always-be specifiea. IALKFL: Specifies tbe length (in bytes) of the Record Identification field that is to be used to access the object data set. This operand must always be specified. IADADMI: Supplies tbe argument type (RELREC or KEY) for the deblocking of a record from a blocked BDAM data set. IADADMI=RELREC signifies that the deblocking technique is relative record. IADADMI=KEY signifies that the aeblocking technique is key. This operand can be used only if the data set (file) to which this index data set points is the primary (target) data set. If this operand is omitted, and if the data set to which this index data set points is a blocked BDAM data set, the entire block is returned to thE user in the File Control area. IADIII: This operand is used to specify a one-byte user-assigned code which signifies that the data in the Record Identification field refers to a duplicate data set rather than the normal object data set. This code must be contained in the first position of the Record Identification field and must be different from any other data that would normally appear in this position. This operand must always be specified if a duplicates data set name is specified (DUPDSID). DUPDSID: This operand is used to specify the identification for the duplicate aata set associated with the cross-index data set. This identification can contain up to seven characters for CICS/DOS and up to eight characters for CICS/OS. This operand may be omitted if a d~plicates data set does not exist. 88 DEFINE HEADER OF SEGMENTED RECORD If the records on a data set are segmented, the DFHFCT TYPE=SEGHEAD macro instruction defines for File Management the header portion (root or control segment) of a segmented record. TYPE=SEGHEAD is the first of four operands which must be coded to specify segmented records. The DFHFCT TYPE=SEGHEAD macro instructisn includes the following operands: DFHFCT TYPE=SEGHEAD, SEGLENG=length, INDDISP=number, TSEGIND=BIT,DISPLACEMENT * * * specifies the length (in bytes) of the header portion (root SEGLENG: segment) of the record. This operand must always be specified. INDDISP: Provides the displacement of the segment indicator field relative to the beginning of the record (position zero). This operand must always be specified. TSEGIND: specifies the type of segment indicator field DISPLACEMENT). The default is TSEGIND=BIT. (BIT or DESCRIBE EACH SEGMENT OF A SEGMENTED RECORD Each segment of a segmented record is described by means of the DFHFCT TYPE=SEGDEF macro instruction. TYPE=SEGDEF must be coded for every segment in the record in the sequence in which it occurs within the record. Definition of the last segment must be followed by the TYPE=SEGLAST operand which must precede the coding of the TYPE=SEGSET operands to automatically generate SEGSET=ALL as the first segment pattern in the File Control Table. The DFHFCT TYPE=SEGDEF macro instruction includes the following operands: DFHFCT TYPE=SEGDEF, SEGNAME=name, SEGCHAR=(format,alignment) , SEGLENG=length SEGNAME: segment. * * * Specifies the eight-character symbolic name (label) of the This operand must always be specified. SEGCHAR: Indicates characteristics (format, alignment) of the segment. If the SEGCHAR operand is omitted, the defaults are FIXED format, BYTE alignment. If one characteristic is specified, both must be specified. The format of a segment is described using one of the following parameters: 89 1. 2. FIXED, the segment is fixed length. VARIABLE, the segment is variable length. The first byte of the segment indicates the length of the segment. When a segment is brought into main storage, the alignment is described using one of the following parameters: 1. 2. 3. 4. BYTE, the segment has no aligLment. HALF, the segment is halfword aligned. FULL, the segment is fullword aligned. DOUBLE, the segment is doubleword aligned. SEGLENG: Specifies the length (in bytes) of the segment; up to 255 bytes can be specified (the length of the largest segment allowed). If the segment is variable length, this value represents the maximum length. This operand must always be specified. DESCRIBE SEGMEN! SETS The pattern of segments for a particular data set is described using the DFHFCT TYPE=SEGSET macro instruction. As many segment sets as desired may be specified. The DFHFCT TYPE=SEGSET macro instruction includes the following operands: DFHFCT TYPE=SEGSET, SEGSET=name, SEGNAME=(name1, ••• ,nameN) * * SEGSET: Specifies the eight-character symbolic name (label) assigned to a particular pattern of segments. This label is used in coding the DFHFC macro instruction when segment services are required. The label may be the same as one of the segment names specified previously in a SEGDEF macro instruction but must be different from any other SEGSE~ name specified. The label ALL should not be used since CICS automatically creates a universal segment set with this label. This operand must always be specified. . SEGNAME: specifies the name of each segment to be included in the segment set, in the sequence in which the segment occurs in the segmented record. SEGNAME must the same name as that specified in a previous DFHFCT TYPE=SEGDEF macro instruction. SPECIFY LAST SEGMENT SET The end of the segment definitions and the end of the segment set definitions is indicated by the DFHFCT TYPE=SEGLAST macro instruction, which must be coded immediately following the last macro segment definition (TYPE=SEGDEF) and immediately following the last segment set (TYPE=SEGSET) for a data set. This macro instruction generates SEGSET=ALL, which includes all the segments in the record, as the first entry in the segment set portion of the File Control Table. 90 SPECIFY END OF FILE CONTEOL TABLE The end of the File Centrel Table is indicated by the DFHFCT TYPE=FINAL macro instruction, which creates a dummy table entry to signal the tacle end. This macro instruction is the last statement before the Assembler END statement, except in the CICS/DOS systems where the user may also elect te code the DFHFCT TYPE=LOGICMOD macro instruction. The Assembler END statement must include the label DFHFCTBA. CREA!E SUPERSET ISAM LOGIC MODULE (CICS/DOS only) A superset ISAM logic module can be assembled in the CICS/DOS systems cy issuing the DFHFCT TYPE=LOGICMOD macro instruction as the last statement before the Assembler END statement. The resulting logic module meets all the processing requirements for defined ISAM data sets with the following exception. If multiple ISAM data sets have been d.efined with the "add" function (SEBVBEC=NEWBEC) and some of the data sets have the "prime data in main sterage" characteristic (IOSIZE=number) while other data sets do not, an additional logic module is required to support those data sets which do not have the "prime data in main storage" characteristic. The user can circumvent this situation by ensuring that ISAM data sets with the "add" feature are all defined either with or without the "prime data in main storage" characteristics (IOSIZE=number). If the user is required to assemble an additional ISAM logic module, he is so notified in a series of diagnostic messages at the end of the File Control Table listing. Also included in these messages are the required parameter values he must ~pecify to create a superset logic module. ]Qi~: If SERVBEQ=BBOUSE is specified by any DFHFCT TYPE=DATASET macro instruction, then DFHTCT TYPE=LOGICMOD must also be specified in that File Control Table. Fer further details ccncerning logic module preparation, see the ~1~~L~2~ QE~!~!i2~~ gYig~· FIlE CeNTROL TABLE EXAMPLE Figure 3 illustrates ·the coding that is required to create a File Control Table for three data sets. The first data set in the table is a cross-index data set that provides indirect access to a master data set and may reference a duplicate data set. The master data set requires segmenting services. 91 DFHFCT TYPE=INITIAL DFHFCT 'IYPE=DATASET, DA'IASET=INDEX, ACCMETH=ISAM, SERVREQ=(GET, PUT, UPDATE, NEWREC, INtAct) , RECFORM=(FIXED,BLOCKED) LRECL=37, BLKSIZE=370, ELKKEYL=5 , * * * * * * * * * * * DFHFCT TYPE=INDACC, OBJDSID=MASTER, IARLKP=26, IALKFL=11, THIS tATA SET REFERENCES A DATA SET NAMED MASTER, WHOSE KEY IS FOUND AT POSITION 26 OF THIS RECORD. IT IS 11 CHARACTERS. IADIII=FF, IT MAY POINT TO A DUPLICATES IUPDSID=DUPLICA DATA SET NAMED DUPLICA. DFHFCT 'IYPE=DATASET, TABLE ENTRY FOR A EDAM tATASET=DUPLICA, DUFLICATES DATA SET WHICH ACCMETH=BDAM, CONTAINS KEYS TO THE MASTER LRECL=22, DA'IA SET. IT IS A READ-ONLY SERVREQ=(GET), DATA SET. RECFORM=(FIXED,UNBLOCKED), BLKSIZE=22 * * * * * * * * * * * * DFHFCT TYPE=DATASET, TABLE ENTRY FOR AN ISAM DATA DATASET=MASTER, SET WHICH MAY BE UPDATED AND ACCMETH=ISAM, ADDED TO, AND WHOSE RECORDS SERVREQ=(GET, ARE SEGMENTED. PUT, UPDATE, NEWREC, SEGMENT) , RECFORM=(FIXED,BLOCKED), LRECL=310, ELKSIZE=1550, RKP=11, ELKKEYL=5 * * * * * * * DFHFCT TYPE=SEGHEAD, SEGLENG=2, INDDISP=2, 'ISEGIND=BIT DFHFCT TYPE=SEGDEF, SEGNAME=SEGMENT1, SEGCHAR=(FIXED, DOUBLE) , SEGLENG=50 DFHFCT 'IYPE=SEGDEF, SEGNAME=SEGMENT2, SEGCHAR=(VARIABLE, HALF), SEGLENG=70 * * * * * * * * * * * Figure 3 (Part 1 of 2). 92 START OF FILE CONTROL TABLE TAELE ENTRY FOR AN ISAM DA'IA SET USED AS A CROSSINDEX DATA SET FOR A DATA SET NAMED MASTER. THIS DATA SET MAY BE UPIATED AND ADDED TO. SEGMENT HEAtER DESCRIPTION SEGMENT *1 OF THE RECORD IS A FIXED-LENGTH, I?OUBLEWORD ALIGNED FIELD. SEGMENT #2 OF THIS RECORD IS A VARIABLE LENGTH HALFWORD ALIGNED FIELD WHOSE MAXIMUM LENGTH IS 70 BY'IES. Coding for fi Ie control table * * * * * DFHFCT TYPE=SEGDEF, SEGMENT #3 OF THE RECORD IS SEGNAME=SEGMENT3, A FIXED-LENGTH UNALIGNED SEGLENG=45 FIELD DFHFCT TYPE=SEGLAST END OF SEGMENT DEFINITIONS DFHFCT TYPE=SEGSET, SEGSET=PATTERN1, SEGNAME=(SEGMENT1,SEGMENT2,SEGMENT3) DFHFCT TYPE=SEGLAST LAST SEGMENT ENTRY FOR MASTER DFHFCT TYPE=FINAL END OF FILE CONTROL TABLE DFHFCT TYPE=LOGICMOD CREATE DOS ISAM LOGIC MODULE END DFHFCTBA POINT TO REQUIRED ENTRY LABEL Figure 3 (Part 2 of 2). * * * * Coding for file control table The Destination Control Table (DCT) is used to describe to CICS the destination name and certain other characteristics of data that is transient to CICS (that is, to be processed by the Transient Data Control program). Entries are made to the DCT by coding the Destination Control Table macro instruction (DFHDCT). Sequential extrapartition destinations are used for storing data external to the CICS partition/region or for retrieving data from outside the partition/region. Data stored for this purpose includes data received from terminals or other data created internally as the result of some transaction requirement identified by a user-written program. Extrapartition data may be both input and output data and is processed using QSAM under CICS/OS or SAM under CICS/DOS. Destination Control Table macro instructions are also used to specify intrapartition destinations. A single data set is used as intermediate storage for data to be directed to multiple intrapartition data destinations. Intrapartition data may be ultimately either transmitted upon request to the destination terminal or retrieved sequentially from the temporary data set for other uses. The user can specify, through the Destination Control Table, that a task is to be created when a certain number of records (trigger level) has been accumulated for an intrapartition destination. Included in the Destination Control Table is the appropriate user-prepared data set control information for all resident extrapartition data sets~ This data set control information must follow the DFHDCT TYPE=INITIAL macro instruction. The extrapartition data sets supported under CICS are: blocked, unblocked, fixed, or variable. CICS provides the capability, in conjunction with the Dynamic Open/Close facility, to have nonresident (transient) data set control blocks and associated input/output areas and logic modules. Main storage normally encumbered for these storage areas is therefore available to the dynamic main storage area until the use of the storage ar€as is required. Nonresident data set control blocks are defined through the combination of DFHDCT TYPE=INITIAL and DFHDCT TYPE=SDSCI macro instructions. Whether the specified destinations are extrapartition or intrapartition (or indirect destinations pointing to either extrapartition or intrapartition destinations), the symbolic names of the destinations must be provided by the user. Refer to Appendix A for a listing of the required destination identification (DESTID) entries. 93 The following operands can be included in the Destination Control Table (DFHDCT) macro instruction: DFHDCT TYPE=INITIAL, SUFFIX=xx, TRNSUFX= (xx, ••• ) , SEPASMB=YES,NO * * * DFHDCT TYPE=SDSCI, DSCNAME=name, MODNAME=name, DEVICE=1403,1404,1443,1445,2311,2314,3330,TAPE, BLKSIZE=length, DEVADDR=symbolic address, RECFORM=FIXUNB,FIXBLK,VARUNB,VARBLK, FILABL=STD,NO, TYPEFLE=INPUT,OUTPUT,RDBACK, RECSIZE=length, REWIND=UNLOAD,NORWD,LEAVE,REREAD, TPMARK=NO, BUFNO=number, ERROPT=SKIP,IGNORE, SUFFIX=xx * * * * * * * * * * * * * * DFHDCT TYPE=EXTRA, DSCNAME=name, DESTID=name, OPEN=INITIAL,DEFERRED, RESIDNT=YES,NO * * * * DFHDCT TYPE=INTRA, DESTID=name, REUSE=YES,NO, TRIGLEV=number, DESTFAC=TERMINAL,FILE, TRANSID=name * * * * * DFHDCT TYPE=INDIRECT, DESTID=name, INDDEST=name * * DFHDCT TYPE=FINAL ESTABLISH CONTROL SECTION FOR DESTINATION CONTROL TABLE The entry point and beginning address for the Destination Control Table being defined are established by the DFHDCT TYPE=INITIAL, SUFFIX=xx, TRNSUFX= (xx, ••• ) , SEPASMB=YES,NO macro instruction. SUFFIX: Specifies a two-character alphameric suffix (other than 'NO' which is reserved) for the Destination Control Table being assembled. This suffix, if specified, is appended to the standard module name (DFHDCT) and is used to name the module on the linkage editor output library. If this operand is omitted, a suffix is not provided. 94 * * * TRNSUFX: Specifies a list of one- or two-character alphameric suffixes associated with nonresident data set control blocks. Any suffix appearing subsequently in the SUFFIX operand of the DFHDCT TYPE=SDSCI macro instruction must also appear in this list. These suffixes are used to punch the control cards for the CICS/DOS Linkage Editor (DFHLINK) or for the OS Linkage Editor (LINKEDIT). Up to 255 suffixes can be specified. Notg~ During link-edit of DFHDCT there is one unresolved ADCON in each phase created under direction of TRNSUFX in DFHDCT TYPE=INITIAL. This message does not imply an error. SEPASMB: The SEPASMB=YES operand is used to indicate that only data set control information is to be generated; that is, the DFHDCT TYPE=INITIAL, DFHDCT TYPE=SDSCI, and DFHDCT TYPE=FINAL macro instructions are the only DFHDCT macro instructions to be included. The default is SEPASMB=NO. SPECIFY DATA SET CONTROL INFORMATION The data set control blocks (DTF's in CICS/DOS; DCB's in CICS/OS) are generated in response to the DFHDCT TYPE=SDSCI macro instruction. This macro instruction is needed only for extrapartition transient data and must have a DFHDCT TYPE=EXTRA macro instruction associated with it for resident data set control blocks. Note that all DFHDCT TYPE=SDSCI macro instructions must be is~ued immediately following the DFHDCT TYPE=INITIAL macro instruction and preceding any DFHDCT TYPE=EXTRA, DFHDCT TYPE=INTRA, or DFHDCT TYPE=INDIRECT macro instructions. The DFHDCT TYPE=SDSCI macro instruction can include the following operands: DFHDCT TYPE=SDSCI, DSCNAME=name, MODNAME=name, DEVICE=1403,1404,1443,1445,2311,2314,3330,TAPE, BLKSIZE=length, DEVADDR=~ymbolic address, RECFORM=FIXUNB,FIXBLK,VARUNB,VARBLK, FILABL=STD,NO, TYPEFLE=INPUT,OUTPUT,RDBACK, RECSIZE=length, REWIND=UNLOAD,NORWD,LEAVE,REREAD, TPMARK=NO, BUFNO=number, ERROPT=SKIP,IGNORE, SUFFIX=xx * * * ** * ** * * * * * * DSCNAME: Specifies the data set control name. This name must be the same as that specified in the DSCNAME operand of the DFHDCT TYPE=EXTRA macro instruction and is limited to seven characters in CICS/DOS or eight characters in CICS/OS. For CICS/OS, the DSCNAME is also the DDNAME and DCBNAME. MODNAME: Applicable only to the CICS/DOS systems, this operand is used to specify the name of the logic module to be used to process the 95 transient data set. If this operand is omitted, a standard DOS name is generated for calling the logic module. This operand can be used in conjunction with the DOS Subset/Superset Logic Module facility to reduce the number of logic modules required to process sequential data sets (where supersetting is permissible). DEVICE: Applicable only to CICS/DOS, this operand specifies the type of input/output device. Valid device types are: 1403, 1404, 1443, 1445, 2311, 2314, 3330, and TAPE. This operand is ignored in CICS/OS; instead, the device specified through the data definition (DD) statement is used. BLKSIZE: Specifies the length (in bytes) of the block (maximum length for variable length records). For DOS disk output data sets, add eight bytes required by Logical IOCS for creation of the count field. DEVADDR: Applicable only to CICS/DOS, this operand specifies the symbolic unit address. This operand is not required for disk data sets when the symbolic address is provided via the CICS/DOS EXTENT card. RECFORM: Specifies the record format of the data set. Valid entries are: FIXUNB, FIXBLK, VARUNB, and VARBLK. For CICS/DOS, the default is RECFORM=FIXUNB. For CICS/OS, no default is provided; the record format specified in the data definition (DD) statement is used. FILABL: Applicable only to CICS/DOS, this operand specifies the type of label on tape data sets. Valid entries are STD or NO. The default is FILABL=NO. Indicates whether the data set is an input or output data TYPEFLE: set. The default is TYPEFLE=INPUT •. For CICS/OS, TYPEFLE=RDBACK specifies an input data set to be read backwards. !2ig: An extrapartition data set may be either INPUT ·or OUTPUT but not both. A system ABEND or unpredictable results may occur if output operations are specified for an INPUT data set or if input operations are specified for an OUTPUT data set. RECSIZE: Specifies the length (in bytes) of the record (maximum length for variable length records). REWIND: Indicates the disposition of a tape data set. Valid entries are UNLOAD and NORWD for CICS/DOS, and LEAVE and REREAD for CICS/OS. TPMARK: Applicable only to CICS/DOS, the TPMARK=NO operand indicates that the writing of a tapemark at end of data set (file) is to be suppressed. BUFNO: Specifies the number of buffers to be provided. For CICS/DOS, any value other than 2 defaults to 1. For CICS/OS, any number up to 255 may be specified; the default value is 1. 96 ERROPT: Specifies the error option to be performed in the event of error. Valid parameters are SKIP and IGNORE. ERROPT=SKIP causes the block that caused the error to be skipped. ERROPT=IGNORE causes the block to be accepted. The default is ERROPT=IGNORE. SUFFIX: Specifies a one- or two-character alphameric suffix for the nonresident data set control block being generated. The use of this operand indicates that the data set control block being generated is nonresident. Nonresident data set control blocks reside on the Real-Time Relocatable Library (DFHRPL) under the unique name DFHTRNxx, where "xx" is the suffix specified in this operand. The user-provided suffix characters must also be specified in the DFHDCT TYPE=INITIAL, TRNSUFX= (xx, ••• ) list. For each data set control block generated via the DFHDCT TYPE=SDSCI, SUFFIX=xx macro instruction, the same suffixed name must be specified in the preparation of the Program Processing Table (DFHPPT TYPE=ENTRY, PROGRAM=DFHTRNxx) • For further information on the above operands, refer to the publication QQ~ ~~ggrvi§Q£ ~nQ In~Y~LQut£gi Mac£Q§ (GC24-5037) or the publication Q~ ~ypervisQ£ ~nQ n~ta Man~ggmeni tl£££Q In§i~~iion2 (GC28-6647) • SPECIFY EXTRAPARTITION DESTINATIONS Destinations external to the system are specified using the DFHDCT TYPE=EXTRA macro instruction. This macro instruction must be coded once for every extra partition destination. Extrapartition destinations that use nonresident data set control blocks are not required to be associated with a specific data set definition. When such destinations are opened, a one- or two-character suffix must be supplied to the Dynamic Open/Close program that indicates which nonresident data set control blocks are to be used for the destinations. The DFHDCT TYPE=EXTRA macro instruction includes the following operands: DFHDCT TYPE=EXTRA, DSCNAI1E=name, DESTID=name, OPEN=INITIAL,DEFERRED, RESIDNT=YES,NO ** * * DSCNAME: Specifies the data set name the user must include in the DFHDCT TYPE=SDSCI macro instruction for destinations that use resident data set control blocks. This operand is not applicable for destinations that use nonresident data set control blocks. Nonresident data set control blocks are identified when the destination is opened. DESTID: Specifies the symbolic name of the extrapartition destination. The symbolic name is the same as that used in the transient data macro instruction (DFHTD) to specify the destination. Any destination identification of more than four characters is truncated on the right. Refer to Appendix A for a listing of the required destination identification entries. 97 OPEN: Applicable only to extrapartition destinations that use resident data set control blocks, this operand is used to specify how the data set associated with this destination is to be opened. OPEN=INITIAL indicates that the data set is to be opened during system initialization. OPEN=DEFERRED indicates that the user will open the data set during real-time execution of CICS. The default is OPEN=INITIAL for destinations that use resident data set control blocks. RESIDNT: Indicates whether this destination is to use resident or nonresident data set control blocks. The default is RESIDNT=YES. Those CICS/DOS extrapartition sequential disk data sets that are to be closed and re-opened by the dynamic Open/Close function of the Master Terminal Program must be defined as nonresident or records may be lost., SPECIFY INTRA PARTITION DESTINATIONS Destinations for messages that are to be logged temporarily by CICS are specified using the DFHDCT TYPE=INTRA macro instruction. This macro instruction must be coded once for every intrapartition destination. The DFHDCT TYPE=INTRA macro instruction can include the following operands: DFHDCT TYPE=INTRA, DESTID=name, REUSE=YES,NO, TRIGLEV=number, DESTFAC=TERMINAL,FILE, TRANSID=name DESTID: Specifies the symbolic name of the intrapartition destination. The symbolic name is the same as that used in the Transient Data macro instruction (DFHTD) to specify the destination. Any destination identification of more than four characters is truncated on the right. Refer to Appendix A for a listing of the required destination identification entries. If the ultimate destination of the data is a terminal and if automatic task initiation is associated with the destination, the name specified in the DESTID operand must be the same as the name specified in the TRMIDNT operand of the DFHTCT TYPE=TERMINAL macro instruction. The user may find it convenient to use the same naming convention for terminal destinations and data set destinations, regardless of whether automatic task initiation is requested. REUSE: REUSE=YES specifies that intra partition storage tracks for this destination are to be released as they are read and returned to the pool of available tracks. REUSE=NO specifies that intrapartition storage tracks for this destination are not to be released until a Transient Data PURGE macro instruction is issued; the PURGE macro instruction causes all tracks associated ·with this DESTID to be released. The ~efault is REUSE=YES. TRIGLEV: Specifies the number of data records (trigger level) to be accumulated for a destination before automatically requesting the creation of a task to prot~~s these records. The ultimate destination 98 * ** ** is normally a data set or terminal. If the TRANSID operand has been used, and if no trigger level has been specified, TRIG LEV defaults to a value of 1. The maximum which may be specified is 32767. (If the ultimate destination is a 2741 Communication terminal, the task to be initiated is not initiated until that terminal receives data.) If TRIGLEV=O, automatic task initiation does not occur; the data records accumulate until some program, however initiated, is executed and issues a DFHTD TYPE=GET macro instruction to access the records. If the execution of a DFHTD TYPE=PUT macro instruction results in the trigger level being reached (or exceeded) for a non-terminal destination, and if either a "maximum tasks" or "short on storage" condition exists for CICS, the task to be automatically initiated is not initiated until a subsequent PUT to the same destination occurs with the stress condition no longer existing. DESTFAC: If TRANSID has been specified, DESTFAC specifies the type of destination (TERMINAL or FILE) that the queue represents. If no destination is specified, the default is DESTFAC=TERMINAL. If DESTFAC=TERMINAL, task initiation to process the queue is by Terminal Control. If DESTFAC=FILE, task initiation is by Transient Data Control. TRANSID: Provides identification for the transaction that is to be automatically initiated when the trigger level is reached. If this operand is omitted, the application program must initiate the read operation. SPECIFY INDIRECT DATA DESTINATIONS "'--.- Indirect data destinations can be specified within the Destination Control Table using the DFHDCT TYPE=INDIRECT macro instruction. The indirect data destination does not point to an actual data set but instead points to another destination. For example, assume the user develops functional symbolic names for the destinations of several message types. These, in turn, may point to one actual destination. At a later time the user might choose to direct one of the message types to another destination. The user does not change his programs but only alters the indirect destination name. The DFHDCT TYPE=INDIRECT macro instruction can include the following operands: DFHDCT TYPE=INDIRECT, DESTID=name, INDDEST=name * * DESTID: Specifies the four-character symbolic name of a particular indirect destination. The symbolic name is the same as that used in the Transient Data macro instruction (DFHTD). Refer to Appendix A for a listing of the required destination identification entries. INDDEST: Specifies the symbolic identification of an intrapartition or extrapartition destination. This identification must be the same as the DESTID of the actual destination. 99 TERMINATE ENTRIES FOR THE DESTINATION CONTROL TABLE Entries for the Destination Control Table are terminated by the DFHDCT TYPE=FINAL macro instruction. This macro instruction must be the last statement in the assembly of every Destination Control Table before the Assembler END statement. The Assembler END statement must include the label DFHDCTBA. NONRESIDENT EXTRAPARTITION DATA SET DEFINITION The definition of nonresident extrapartition data sets is accomplished through use of the DFHDCT TYPE=INITIAL and DFHDCT TYPE=SDSCI macro instructions. The data set control blocks and associated input/output areas are generated and cataloged to the Real-Time Relocatable Program Library (DFHRPL) as a separate table for each nonresident data set control block to be used. There must be an entry in the Processing Program Table (PPT) for each nonresident data set control block. The format of the name is DFHTRNxx, where "xx" represents the suffix character(s) specified in the DFHDCT TYPE=SDSCI, SUFFIX=xx macro instruction. The PPT entry for these data set control blocks must include the RELOAD=YES operand. In CICS/OS, the necessary access methods are acquired when data sets are opened. Therefore references to transient access methods (logic modules) in the following discussion are applicable primarily to CICS/DOS. In the CICS/DOS systems, the logic modules for the nonresident data set control blocks may also be transient. If the use of nonresident logic modules is desired, the logic modules must be assembled and cataloged to DFHRPL prior to execution. The logic modules are assembled using the standard DOS SAM macro instructions and must be cataloged with the same program name generated by the nonresident data set control block for which it is to be used. The name can be found in the assembly of the data set control block. Unless otherwise specified in the DFHDCT TYPE=SDSCI macro instruction, this name is the standard DOS logic module name. The PPT entry for each nonresident logic module must include the RELOAD=YES operand. In CICS/DOS, if the DCT is generated to include the nonresident data set control block definitions, the logic modules for both the resident and nonresident data set control blocks are link edited into the DCT. To allow the logic modules to be transient, the DCT should be assembled including only the resident data set control block definitions (DFHDCT TYPE=SDSCI). A separate assembly can then be accomplished to generate only the nonresident data set control blocks. To perform this operation, include a DFHDCT TYPE=INITIAL, TRNSUFX=(xx, ••• ) ,SEPASMB=YES macro instruction, followed by DFHDCT TYPE=SDSCI macro instructions for all nonresident data set definitions, followed by the DFHDCT TYPE=FINAL macro instruction. DESTINATION CO~TBOL TABLE EXAMPLES Figure 4 contains an example of the coding required to generate a Destination Control Table that uses resident data set control blocks. 100 DFHDCT TYPE=INITIAL DFHDCT TYPE=SDSCI, DSCNAME=DFHXTRA, DEVADDR=SYSLST, DEVICE=1403, RECFORM=FIXUNB DFHDCT TY PE=EXTR A, DS CNAME= DF HXTRA, DESTID=CASH DFHDCT TYPE=INTRA, DESTID=GAMA DFHDCT TYPE=INTRA, DESTID=SAMA DFHDCT TYPE=INTRA, DESTID=DAMA, TRIGLEV=5, DESTFAC=TERMINAL, TRANSID=AUTO DFHDCT TYPE=FINAL END DFHDCTBA Figure 4. START OF DEST CONTROL TABLE SPECIFY DATA SET CONTROL INFO RELATED DESTINATION SYMBOLIC UNIT ADDRESS DEVICE TYPE RECORD FORMAT EXTRA PARTITION DESTINATION SYMBOLIC NAME INTRAPARTITION DESTINATION SYMBOLIC NAME SYMBOLIC NAME SYMBOLIC NAME TRANSACTION ID END OF DEST CONTROL TABLE POINT TO REQUIRED ENTRY LABEL DCT using resident data set control blocks ,-- 101 * * * * * * * * * * * * Figures 5 and 6 show how the generation of a DCT can include €xtrapartition destinations that use nonresident data set control blocks. Figure 5 shows a DCT with nonresident data set control blocks and resident logic modules. Figure 6 shows a DCT with nonresident data set control blocks and nonresiqent logic modules. DFHDCT TYPE=INITIAL, TRNSUFX=(AA,BB,CC,DD} , SUFFIX=22 DFHDCT TYPE=SDSCI, DSCNAME=TAPE1, RECFORM=FIXBLK, TYPEFLE=OUTPUT, BLKSIZE=2000, DEVADDR=SYS011, DEVICE=TAPE, BUFNO=2, RECSIZE=200, SUFFIX=AA DFHDCT TYPE=SDSCI, DSCNAME=TAPE2, RECFORM=FIXBLK, TYPEFLE=INPUT, BLKSIZE=2000, DEVADDR=SYS011, DEVICE=TAPE, BUFNO=2, RECSIZE=200, SUFFIX=BB DFHDCT TYPE=SDSCI, DSCNAME=TAPE3, RECFORM=FIXUNB, BLKSIZE=1240, TYPEFLE=INPUT, DEVADDR=SYS011, DEVICE=TAPE, SUFFIX=CC DFHDCT TYPE=SDSCI, DSCNAME=TAPE4, RECFORM=FIXUNB, BLKSIZE=1240, TYPEFLE=OUTPUT, DEVADDR=SYS011, DEVICE=TAPE, SUFFIX=DD DFHDCT TYPE=SDSCI, DSCNAME=PRINT, RECFORM=VARUNB, BLKSIZE=121, DEVADDR=SYSLST, DEVICE=1403 DFHDCT TYPE=EXTRA, DSCNAME=PRINT, DESTID=PRNT DFHDCT TYPE=EXTRA, RESIDNT=NO, DESTID=TAPE DFHDCT TYPE=FINAL END DFHDCTBA Figure 5. 102 DCT using nonresident data set control blocks and resident logic modules * * * * * * * * * * * ** * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * The assembly of the macro instructions contained in Figure 5 results in a Destination Control Table with suffix 22 (DFHDCT22) that contains one data set control block for the printer (TYPE=SDSCI,DESTID=PRNT). When the output of this generation is link edited, the logic modules for tape and printer are automatically included, and the four tape data set control blocks are cataloged separa~ely to DFHRPL as DFHTRNAA, DFHTRNBB, DFHTRNCC, and DFHTRNDD. the set can set The extrapartition destination (DESTID=TA?E) can be openEd through CICS Dynamic Open/Close program with any of the four suffix~d data control blocks (DFHTRNAA, DFHTRNBB, DFHTRNCC, or DFHTRNDD). It then be closed and reopened with any of the other nonresident data control blocks. Program Processing Table (PPT) entries must be included for the four data set control blocks cataloged separately. PPT entries must include the RELOAD=YES operand. DPHDCT TYPE=INITIAL, TRNSUFX=(AA,BB,CC,DD) , SEPASMB=YES DFHDCT TYPE=SDSCI, DSCNAME=TAPE1, RECFORM=PIXBLK, TYPEFLE=OUTPUT, BLKSIZE=2000, DEVADDR=SYS011, DEVICE=TAPE, BUFNO=2, RECSIZE=200, SUFFIX=AA DFHDCT TYPE=SDSCI, DSCNAME=TAPE2, RECFORM=FIXBLK, TYPEFLE=INPUT, BLKSIZE=2000, DEVADDR=SYS011, DEVICE=TAPE, BUFNO=2, RECSIZ E=200, SUFFIX=BB DFHDCT TYPE=SDSCI, DSCNAME=TAPE3, RECFORM=FIXUNB, BLKSIZE=1240, TYPEFLE=INPUT, DEVADDR=SYS011, DEVICE=TAPE, SUFFIX=CC DFHDCT TYPE=SDSCI, DSCNAME=TAPE4, RECFORM=FIXUNB, BLKSIZE=1240, TYPEFLE=OUTPUT, DEVADDR=SYS011, DEVICE=TAPE, SUFFIX=DD DFHDCT TYPE=FINAL END DFHDCTBA Figure 6 (Part 1 of 2). * * * * * * * * * * * * * ** * * * * * * * * * * * * * * * ** * * DCT using nonresident data set control blocks and nonresident logic modules 103 DFHDCT TYPE=INITIAL, SUFFIX=YY DFHDCT TYPE=SDSCI, DSCNAME=PRINT, RECFORM=VARUNB, BLKSIZE=121, DEVADDR=SYSLST, DEVICE=1403 DFHDCT TYPE=EXTRA, DSCNAME=PRINT, DESTID=PRNT DFHDCT TYPE=EXTRA, RESIDNT=NO, DESTID=TAPE DFHDCT TYPE=FINAL END DFHDCTBA Figure 6 (Part 2 of 2). * * * * * * * * ** DCT using nonresident data set control blocks and nonresident logic modules The result of the generation of the macro instructions contained in Figure 6 (Part 2 of 2) is a Destination Control Table with a suffix of YY (DFHDCTYY). The DCT contains one data set control block £or the printer (TYPE=SDSCI, DESTID=PRNT) and one logic module for the printer. The four data set control blocks for tape are generated by the assembly of the macro instructions contained in Figure 6 (Part 1 of 2). When the output of that assembly is link edited, the data set control blocks are cataloged as DFHTRNAA, DFHTRNBB, DFHTRNCC, and DFHTRNDD. However, the user must have cataloged the logic modules used by these four data set control blocks to DFHRPL using DFHLINK, and must have included entries in the PPT that specify the RELOAD=YES operand for those logic modules. When using the generated DCT of Figure 6, no storage is used for the data set control blocks or for the logic modules until the extra partition destination (DESTID=TAPE) is opened via the CICS Dynamic Open/Close program (DFHOCP). The Dynamic Open/Close program will ensure that only one logic module of the same name is in storage at anyone time. If the logic module is not resident in the DCT, the Dynamic Open/Close program frees the storage associated with the logic module when the data set is closed. For further details concerning the use of the Dynamic Open/Close facility, see the discussion of dynamic open/close in the "Master Terminal" section and the "Dynamic Open/Close Function" section of this manual. The Program Control Table is the means for the user to describe the control information to be used by CICS for identifying and initializing a newly-arrived transaction. Task Control uses a portion of each PCT entry for the purpose of accumulating transaction statistics. This table is required by the control system to verify the incoming transaction, supply the transaction priority and security key, supply the length of the Transaction Work Area, and keep transaction statistics. 104 The following operands can be included in the DFHPCT macro instruction: DFHPCT !YPE=INITIAL, SUFFIX=xx * DFHPCT TYPE=ENTRY, TRANSID=name, TRNPRTY=decimal value, TnANSEC=decimal value, TwASIZE=decimal value, PROGRAM=name, TPURGE=YES,NO, SPURGE=YES,NO, COMPAT=NO,FORMAT,FULLBUF * * * ** * * * DFHPCT TYPE=FINAL ESTABLISH CONTROL SECTION FOR PROGRAM CONTROL TABLE The control section into which the Program Control Table is assembled is established by the DFHPCT TYPE=INITIAL, SUFFIX=xx * macro instruction. This macro instruction must be coded as the first statement in the source deck used to assemble the Program Control Table. '- SUFFIX: Specifies a two-character alphameric suffix for the Program Control Table being assembled. This suffix, if specified, is appended to the standard module name (DFHPCT) and is used to name the module on the linkage editor output library. If this operand is omitted, a suffix is not provided. SPECIFY TRANSACTION CONTROL INFORMATION Transaction control information is provided to CICS program management services by the DFHPCT TYPE=ENTRY macro instruction. Included in this macro instruction is information on priority, security key, program identification, purge indicators, and size of the Transaction Work Area. The DFHPCT TYPE=ENTRY macro instruction includes the following operands: DFHPCT TYPE=ENTRY, TRANSID=name, TRNPRTY=decimal value, TRANSEC=decimal value, TWASIZE=decimal value, PROGRAM=name, TPURGE=YES,NO, SPURGE=YES,NO, COMPAT=NO,FORMAT,FULLBUF ** ** * * * * TRANSID: Used to specify the four-character identification assigned to the individual transaction. Note that TRANSID=DISC should not be 105 specified if terminals are to be supported on switched\lines. For further details concerning the use of terminals on switched lines, see the £IC~ 19£min~1 QE§ra1Q±~~ Guigg. TRNPRTY: Used to define the transaction priority. This three-position decimal value (000-255) is used in establishing the overall transaction processing priority. (Transaction processing priority is equal to the sum of the terminal priority, transaction priority, and operator priority, not to exceed 255.) If this operand is omitted, the default is TRNPRTY=OO 1. TRANSEC: Used to define the transaction security, the TRANSEC parameter is a three-position decimal value with a range 001 through 024. The default is TRANSEC=001. Used to define the Transaction Work Area required. A TWASIZE: five-position decimal value that determines the size (in bytes) of the Transaction Work Area to be acquired for this transaction. Refer to Appendix A for the minimum values that must be specified for programs provided by CICS. The default is TWASIZE=O. PROGRAM: Used to define the initial program identification; this operand specifies the name of the program to which control is to be given to process this transaction. TPURGE: Used to set the terminal error purge indicator. TPURGE=YES indicates that the terminal error purge indicator is to be set to allow the transaction to be purged when a terminal error occurs. The default is TPURGE=NO. SPURGE: Used to set the system stall purge indicator. SPURGE=NO indicates that the transaction is not purgeable when a system stall condition is detected. The default is SPURGE=NO. COMPAT: Used to flag those transactions that are to be run in 2260 compatibility mode on the 3270 Information Display System. The default is COMPAT=NO. COMPAT=FORMAT indicates that the transaction is to be run in FORMAT mode; COMPAT=FULLBUF indicates that the transaction is to be run in FULLBUF mode. For a discussion of FORMAT and FULLBUF modes of compatibility operation, see the section "2260 Compatibility for the 3270 11 • SPECIFY END OF PROGRAM CONTROL TABLE The end of the Program Control Table is indicated by the DFHPCT TYPE=FINAL macro instruction, which is the last statement in the assembly of the Program Control Table before the Assembler END statement. This macro instruction creates a dummy entry to signal the table end. The Assembler END statement must include the label DFHPCTBA. 106 PROGRAM CONTROL lABLE EXAMPLE Figure 7 illustrates the coding that is required to create a Program Control Table. The transactions include: 1. 2. 3. Three transactions of a higher priority than the default priority (TRNPRTY=1 is the default) Two transactions with security key protection Total of nine transactions See Appendix A for a list of all the entries required to create a Program Control Table. DFHPCT TYPE=INITIAL DFHPCT TYPE=ENTRY, TRANSID=COB1, TWASIZE=64, PROGRAM=COBPGM1 DFHPCT TYPE=ENTRY, TRANSID=COB2, TRNPRTY=100, TRANSEC=10, PROGRAM=COBPGM2 DFHPCT TYPE=ENTRY, TRANSID=COB3, TWASIZE=100, TRANSEC=5, PROGRAM=COBPGM3, TPURGE=YES DFHPCT TYPE=ENTRY, TRANSID=COB4, PROGRAM=COBPGM4, TPURGE=YES DFHPCT TYPE=ENTRY, TRANSID=CSAC, TRNPRTY=5, TWASIZE=40, PROGRAI1=DFHACP DFHPCT TYPE=ENTRY, TRANSI D=CSMT, TWASIZE=160, PROGRAM=DFHMTPA DFHPCT TYPE=ENTRY, TRANSID=CSST, TWASIZE=100, PROGRA M=DF HMTPA DFHPCT TYPE=ENTRY, TRANSID=CSTA, TWASIZE=OOO, PROGRAM=DFHTAJP DFHPCT TYPE=ENTRY, TRANSID=CSSN, TRNPRTY=99, TWASIZE=OOO, PROGRAM=DFHSNP, SPURGE=YES DFHPCT TYPE=P,INAL END DFHPCTBA Figure 7. * * * * * * * * * * * * * * * * ** * * * * * * * * * * * * * * * Coding for program control table 107 The Processing Program Table provides a means for the user to describe to Program Control the control information concerning the processing programs. In addition, Program Control uses portions of each table entry to retain certain information for maintaining control of the user's programs and to capture specified program statistics. This table is required by CICS to verify the processing program identification, to keep count of the number of transactions using that prog£am, to maintain the address of the processing program, to communicate to CICS the type of load used for the program, to maintain the direct access address and size of the program, and to maintain statistics on the processing program. The Processing Program Table macro instruction (DFHPPT) specifies processing programs to be recognized by CICS. The following operands can be included in the DFHPPT macro instruction: DFHPPT TYPE=INITIAL, SUFFIX=xx * DFHPPT TYPE=ENTRY, PROGRAM=name, PGMLANG=ASSEMBLER,COBOL,PL/I, RES=YES,NO, RELOAD=YES,NO * * * * DFHPPT TYPE=FINAL Those programs most often used during execution of CICS should be specified first during preparation of the Processing Program Table. ESTABLISH CONTROL SECTION FOR PROCESSING PROGRAM TABLE The control section into which the Processing Program Table is assembled is established by the DFHPPT TYPE=INITIAL, SUFFIX=xx * macro instruction, which must be coded as the first statement in the source deck used to assemble the Processing Program Table. SUFFIX: Specifies a two-character alphameric suffix for the Processing Program Table being assembled. This suffix, if specified, is appended to the standard module name (DFHPPT) and is used to name the module on the linkage editor output library. If this operand is omitted, a suffix is not provided. DESCRIBE PROCESSING PROGRAMS A specific processing program is described to CICS program management services by the DFHPPT TYPE=ENTRY macro instruction. Included is information on the program name and the type of program. The DFHPPT TYPE=ENTRY macro instruction includes the following operands: 108 DFHPPT TYFE=ENTRY, PRCGRAM=name, PGMLANG=ASSEMBLER,COBOL,PL/I, RES=YES,NO, RELOAD=YES,NO * * ** FROGBAM: Specifies the program identification, up to eight characters in length. The indicated program must have been previously link edited into the Real-Time Relocatable Program Library (DFHRPL). PGMLANG: Specifies the type of program. The default is PGMLANG=ASSEMBLER. omit this parameter when preparing PPT entries for BMS maps regardless of the cempiler used. RES: Used to indicate wnether or not the program is to be made resident in main storage when CICS is initialized. In the CICS/DOS-ENTRY system, the designated programs become permanently resident, and the size of dynamic storage (subFool 0) is reduced. For the CICS/DOS-STANDARD and CICS/OS~STANDARD systems, the designated programs are "packed" into the high portion of the user's dynamic main storage. The default is BES=NO. RELOAD: RELOAD=YES indicates that a fresh copy of the program is to be loaded by the Program Centrol pIogram each time a load request for that program is issued. It is the user's responsibility to release the storage, it is not automatically released when the transaction terminates. A Storage Control FREEMAIN, rather than a Program Control DELETE, must ce used to free the storage. The default is RELOAD=NO. If the Dynamic Open/Close program is to be used, RELOAD=YES must be specified in each PPT entry that defines a nonresident data set control block. RELOAD=YES must also be specified for all CICS/DOS transient logic modules. The Dynamic Open/Close program maintains a use count for the logic modules to ensure that only one copy is in main storage at any one time. If the logic module is resident in the Destination Control Table, no entry is necessary in the PP~. In the DOS-ENTRY System, storage for the prog~am is obtained from sub Fool o. SPECIFY END OF PBOCESSING PROGRAM TABLE The end of the processing program Table is indicated to the control system by the DFHPPT TYFE=FINAL macro instruction, which is the last statement in the assembly of the Processing Program Table before the Assembler END statement. This macro instruction creates a dummy entry to signal the tacle end. The Assembler END statement must include the label DFHPPTBA. FROCESSING FROGR!M TABLE EXAMPLE Figure 8 illustrates the coding that is required to create a Processing Program Table. The programs include: 1. 2. Four Assembler language programs, one of which is resident Four ANS CCBOI programs 109 See A~pendix A for a list of all the entries required to create a Processing Program Table. DFHPPT TYFE=INITIAL DFHPPT TYFE=ENTRY, PRCGEAM=COBPGM1, PGMLANG=COBOL DFHPPT TYPE=ENTRY, PROGRAM=COBPGM2, PGMLANG=CCBOL DFHPPT TYFE=ENTRY, PRCGRAM=COBPGM3, PGMLANG=COEOL, RELOAD=YES DFHPPT TYFE=ENTRY, PROGEAM=COBPGM4, PGMLANG=COEOL DFHPPT TYPE=ENTRY, PRCGEAM=DFHACP DFHPPT TYFE=ENTRY, PROGRAM=DFHTAJP DFHPPT TYFE=ENTRY, PROGEAM=DFHMTPA DFHPPT TYPE=ENTRY, PROGRAM=DFHSNP DFHPPT TYPE=FINAL END DFHPPTBA Figure 8. * * * * * * * * * * * * * Coding for processing program table The system service tables (optional) provide the user with increased centrol over the operation of CICS. The system service tables are: 1. Sign-on Table that contains the operator security and priority data to permit an o~eratoI to sign on the system. 2. Terminal List Tables that contain, by groups, the identification of terminals that are related logically; for example, the terminals in a remote location or all terminals whose operators are under the contrcl of a supervisor. A supervisor, through his table, may alter the status of a terminal under his control. For example, he could place a terminal in an out-of-service condition. The Sign~on Table and the Terminal List Tables reside on a direct access storage dEVicE and are called into main storage as required. The use of a Sign-on Table or a Terminal List Table requires that FCPLOAD=YES be specified for DFHSG PBOGRAM=PCP macro instruction. Refer to the CICS Terminal Operator's Guide for the terminal operator ~rocedures using the system service tables and programs. SIGN-ON TABLE (SNT) The Sign-on Table provides the means for permanently retaining terminal operator data. It is accessed when a terminal operator initiates the sign-cn procedure. During the sign-on procedure, the name of the terminal operator is entered at the terminal and is used to locate the appropriate operator entry in the table. The operator entry in the table contains data used 110 to verify the operator name and to establish a priority and a security key for the transactions which the operator subsequently enters. The priority value related to the operator is used to develop the task priority for processing a transaction. The operator's security key is used in a security check of all transactions subsequently entered. The security key which is placed in the appropriate Terminal Control Table entry for the operator is matched with the transaction security contained in the transaction's Program Control Table (PCT) entry. If the operator security key contains any position that matches the security value in the PCT entry, the transaction is accepted. Otherwise, a security check has occurred and the transaction is terminated. A security key of 1 is the default option in the creation of the Sign-on Table, the Program Control Table, and the Terminal Control Table; this value is present in the Terminal Control Table until altered by a sign-on procedure. The security key default option allows transactions with a transaction security of 1 to be entered into the system by the operator without the sign-on procedure. The Sign-on Table macro instruction (DFHSNT) specifies the terminal operator data for the users of CICS. A DFHSNT entry should be present in the Sign-on Table for each terminal operator who is expected to sign on. The Sign-on Table must be assembled, link edited with the name DFHSNT, and represented in the Processing Program Table (PPT). The following operands can be included in the DFHSNT macro instruction: DFHSNT TYPE=INITIAL DFHSNT TYPE=ENTRY, OPNAME='operator name', PASSWRD=password, OPIDENT=operator identification, SCTYKEY=(n1, ••• ,n24} , OPPRTY=operator priority * * * * * DFHSNT TYPE=FINAL The control section into which the Sign-on Table is assembled is established by the DFHSNT TYPE=INITIAL macro instruction, which must be coded as the first statement in the source deck used to assemble the Sign-on Table. 111 Each terminal operator is described to CICS through an entry in the Sign-on Table. These entries are made by issuing the DFHSNT TYPE=ENTRY macro instruction. Included in this macro instruction is information on password, operator identification, security key, and operator priority. The DFHSNT TYPE=ENTRY macro instruction includes the following operands: DFHSNT TYPE=ENTRY, OPNAME='operator name', PASSWRD=password, OPIDENT=operator identification, SCTYKEY=(n1, ••• ,n24) , OPPRTY=operator priority OPNAME: Specifies the name of the terminal operator for this table entry. The operator name may be 1 to 20 characters long and must be unique for each entry. The operator name in this entry must be matched exactly by the operator name entered in the sign-on procedure. PASSWRD: Specifies a four-character password (identification) created by the user. The password entered by a terminal operator as a part of the sign-on procedure must be matched exactly by the password in the operator's Sign-on Table entry. Passwords may be unique to each operator or the same for a logical group of operators. OPIDENT: Used to specify the three-character operator identification code assigned by the user to each operator. This code is placed in the appropriate Terminal control Table terminal entry (TCTTE) when the operator signs on so that the identity of the operator is known to CICS. This operator identification is made available to the master terminal when a security violation is detected. SCTYKEY: Specifies one or more decimal security-key values from 1 to 24. The security key for a terminal operator is comprised of those values which are to be matched with the transaction security of an appropriate program control table entry. The security key may be built with from 1 to 24 individual values. Each decimal value in the range of 1 to 24 specified in the operand of the SCTYKEY keyword has a corresponding bit position in a three-byte SCTYKEY field. The presence of each value in the operand causes the corresponding relative bit position to be set on. The transaction security in a Program Control Table entry is specified as only one of the possible 24 individual values. The same value must be contained in the operator's security key to allow the operator to process that transaction. The operator's security key is not limited to just one value and likely contains several values. The default is SCTYKEY=1. it is specified. It will also be a value whether or not OPPRTY: Specifies a decimal operator priority value from 0 to 255. An operator priority is assigned optionally by the user and is used in 112 * * * * * developing the task processing priority for each default is OPPRTY=O. 2£g£iiY End Q1 transactio~. The ~ign-Qn 1~~1~ The end of the Sign-on Table is indicated by the DFHSNT TYPE=FINAL macro instruction, which is the last statement in the assembly of the Sign-on Table before the Assembler END statement. This macro instruction creates a dummy entry to signal the table end. The Assembler END statement must include the label DFHSNTBA. Figure 9 contains an example of coding for the Sign-on Table. In this example, there are two cases of the operator name being actual names and one instance of the name being a function. The first operator has access to transactions whose transaction securities are 1,2,7, or 24. The other two operators have access to the same transactions as the first plus additional transactions. The second operator has a default priority of zero. DFHSNT TYPE=INITIAL DFHSNT TYPE=ENTRY, OPNAME='DON GIBSON', PASSWRD=DIST, OPIDENT=DG, SCTYKEY=(1,2,7,24) , OPPRTY=128 DFHSNT TYPE=ENTRY, OPNAME='R. J. JONES', PASSWRD=DIST, OPIDENT=RJJ, SCTYKEY=(1,2,7,9,24) DFHSNT TYPE=ENTRY, OPNAME='MASTER TERMINAL ", PASSWRD=MAST, OPIDENT=MT1, SCTYKEY=(1,2,3,4,7,9,24) , OPPRTY=255 DFHSNT TYPE=FINAL END DFHSNTBA Figure 9. * * * * * * ** * * * * * * Coding for sign-on table TRRMINAL LIST TABLES (TLT) The Terminal List Tables provide the user of CICS with the means of retaining the terminal identifications in logical groupings. A logical grouping of terminals could be all the terminals that are under the control of a supervisor. Each supervisor might have a Terminal List Table. All terminals which serve a similar function represent a logical grouping, or class of terminals. The user might create a grouping of terminal identifications to facilitate the dispatching of general messages to terminals. The system service programs of CICS use Terminal List Tables to perform terminal status change operations. A unique Terminal List 113 Table must be created for each supervisor who is to have the ability to alter the terminal status of any terminal under his control. Any operation which is to change the status of an entire group of terminals requires a Terminal List Table containing the identifications of all terminals in that group. Unique identification is assigned to each table by the user. The creation of the Terminal List Tables is accomplished through the assembly procedure by using the DFHTLT macro instruction. The following operands can be included in this macro instruction: DFHTLT TYPE=INITIAL, SUFFIX=xx * DFHTLT TYPE=ENTRY, TRMIDNT=terminal identification * DFHTLT TYPE=FINAL The Terminal List Table must be assembled and link edited with a name that conforms to the format: DFHTLTxx. The base name is DFHTLT. The two-character suffix (xx), uniquely identifying this table, consists of the same characters entered by a user of the system service programs for terminal status change. These two characters are appended to the base name (DFHTLT) for the retrieval process, and may represent either a supervisor's identification or the identification of a class of terminals. There must be an entry in the Processing Program Table (PPT) each Terminal List Table the user wishes to access. for The control section into which the Terminal List Table is assembled is established by the DFHTLT TYPE=INITIAL, SUFFIX=xx * macro instruction, which must be coded as the first statement in the source deck used to assemble the Terminal List Table. SUFFIX: This operand is used to specify a two-character suffix for the Terminal List Table being assembled. This suffix, if specified, is appended to the standard module name (DFHTLT) and is used to name the module on the linkage editor output library. If this operand is omitted, a suffix is not provided. §£eciiY !ermina1 lQggtifi£~iiQn The terminal identifications to be included in the Terminal List Table are specified through the DFHTLT TYPE=ENTRY, TRMIDNT=terminal identification list macro instruction. Any number of these macro instructions can appear in a Terminal List Table assembly. TRMIDNT: 114 Specifies a list of terminal identifications to be included * in the table. Any symbolic identification used must first have been defined in the TRMIDNT operand of the DFHTCT macro instruction. The end of the Terminal List Table is indicated by the DFHTLT TYPE=FINAL macro instruction, which is the last statement in the assembly of the Terminal List Table before the Assembler END statement. The Assembler END statement must include the label DFHTLTBA. Figure 10 illustrates the coding required to create a Terminal List Table. DFHTLT TYPE=INITIAL, SUFFIX=AA DFHTLT TYPE=ENTRY, TRMIDNT=(NYC,CHI,LA,WDC) DFHTLT TYPE=ENTRY, TRMIDNT=(SF,ATL) DFHTLT TYPE=FINAL END DFHTLTBA Figure 10. * * * Coding for terminal list table 115 CICS provides a technique for incorporating user-written source code into most of the CICS management programs. This source code may extend various CICS management functions. So long as the user conforms to certain restrictions and conventions, this facility should minimize the impact of CICS source code modifications when installing new releases of CICS. To include a user-written exit routine in a particular CICS management program, the user must place his source code in a CICS source library member (book) which has the naming convention: DFHxxEXT where xx is the two-character designation for the management program into which the user-written code is to be included. The two-character designations are: KC SC PC TC FC IC TD TS (Task Control) (Storage Control) (Program Control) (Terminal Control) (File Control) (Interval Control) (Transient Data Control) (Temporary Storage Control) The code provided by the user in a given member (book) may consist of more than one routine (function) depending upon the number of linkages provided in the particular CICS management program. For example, File Management provides linkage to user-written exit routines both before and after an input operation. Thus, user-supplied code in the member (book) DFHFCEXT might contain two routines, each identified by a unique symbolic name. Linkage from the CICS management program to the appropriate user-written exit routine is accomplished by one of the following methods: 1. An Assembler BAL instruction that uses the user-defined symbolic name as the "branch to" label and general register 14 as a return register. 2. Register 14 is loaded with an address constant for the user defined symbolic name and a BALR 14, 14 instruction is issued. Noig: The user-written exit routines are located at the end of the management programs. The length of some programs is such that the exit routines are not addressable by the program's base register(s). This situation forces the use of method two above, and requires the exit routine to establish its own addressability upon gaining control. Under method one at least some beginning part of the user exit routine is addressable by a management program base register. Another base register may be required for the rest of the exit routine. 116 The symbolic name of the exit routine is specified in the appropriate operand when the management program is generated. For example, in response to the DFHSG PROGRAM=SCP, XTYPREQ=ORANGE * specification, user exit linkage in the form of an Assembler BAL 14,ORANGE instruction is generated in the appropriate place in the storage Control program. In this example, source code similar to the following should have been provided by the user in the member (book) DFHSCEXT: ORANGE DS USER EXIT ENTRY OH User code BR 14 Upon entry to a user exit routine, registers can be saved in the CSA register save ar€a (CSAOSRSA). The following example shows the use of OS/DOS SAVE and RETURN macro instructions to save registers 4 through 6 and to use register 4 as a base register. ORANGE DS OH SAVE (4,6) BALR 4,0 USING *,4 RETURN (4,6) USER EXIT ENTRY SAVE REGS 4,5,6 IN CSAOSRSA USE REG 4 AS BASE R~G RESTORE REGS 4,5,6 AND RETURN VIA REG 14 Using the CSA for register saving is a non-reentrant method and therefore the exit routine should not issue any CICS or OS/DOS macro instructions that might require use of this CSA area. This includes releasing control to another task which might use this samE (or another) exit routine that saves registers in the CSA. When creating the CICS management program assembly jobs during system generation, a COpy DFHxxEXT statement is included immediately preceding the Assembler END statement. In the above example, the following would be generated: COpy DFHCSADS COpy DFHTCADS COpy DFHSCP COpy DFHSCEXT END DFHSCNA When coding user exits for CICS management programs, the user should adhere to the following conventions and guidelines: 117 1. Since user exits are essentially "in line" with the management programs, the coder should be familiar with the functions of the program to which the exit code is being added. 2. User-written exit routines must never alter the contents of registers that provide addressability to control blocks, unless the original contents are restored before return to the CICS management program. 3. User-written exit routines must never violate restrictions of the management programs. For example, an exit routine in Storage Control cannot issue a DFHSC TYPE=GETMAIN macro instruction. In general, it is best if exit routines do not issues requests for CICS services. 4. User-written exit routines must be coded in Assembler language. 5. Symbolic names (labels) used to define user exit entry points must not be duplicates of labels in the CICS management program. 6. Base register addressability for the user-written exit routine exists only to the extent of the base register(s) associated with the management program. The user exit must never alter the base register(s) of the management program. The user is responsible for saving registers and establishing addressability. 7. Register contents differ depending on the management program and particular exit function. However, the contents of the following registers are always constant: 14 13 12 Return address CSA address TCA address Depending on the management program and functional user exit, certain general registers contain information that the user may find useful. The following is a summary, by exit, of the contents of these registers: 118 REQQBli!1 SYSGEN EXIT ID]l!! DFHKCP XDSPCHR Before dispatch TCACBAR XTYPREQ Before request analysis TXACBAR XFETCH After load PPTCBAR DFHPCP PCECREG DFHICP TXA with task only) Address of PPT entry for loaded program Entry point address of loaded program After expiration of time interval ICECBAR XTYPREQ Before request analysis N.A. Address of Interval Control Element (ICE) just expired N.A. DFHSCP XTYPREQ Before request analysis N.A. N.A. DFHTCP XATTACH Before task attach TCTTEAR TCTLEAR TIOABAR Before output event TCTTEAR TCTLEAR TIOABAR After input event TCTTEAR TCTLEAR TIOABAR Address Address Address Address Address Address Address Address Address XOUTPUT Before output event FWACBAR FCTDSBAR XINPUT Before input event FCTDSBAR XINPUTC After input event FCTDSBAR FWA FCT entry data set FCT entry data set FCT entry data set FIOA XTYPREQ Before entry Analysis Address of Address of for target Address of for target Address of for target Address of N.A. XOUTPUT Before output event DCTCBAR XINPUT Before input event DCTCBAR XYTPREQ Before request analysis DCTCBAR Address of for target Address of for target Address of for target DCT entry destination DCT entry destination DCT entry destination XOUTPUT Before output event TSWKREG XINPUT After input event TSWKREG XTYPREQ Before request analysis TSDA XINPUT '-- TCA being XICEEXP XOUTPUT "- Address of dispatched Address of associated (CICS/DOSE DFHFCP DFHTDP DFHTSP l!ot~: FIOABAR N.A. of of of of of of of of of TCTTE TCTLE TIOA TCTTE TCTLE TIOA TCTTE TCTLE TIOA Address of data being read or written Address of data being read or written Address of data area specified by requesting program CICS provides a set of dummy exit members (books) as part of its distributed source library. These members contain only dummy labels and a BR 14 instruction, and should be replaced by user-written exit routines. 119 The CICS terminal error handling structure is based on the assumption that most users will want to expand and refine certain CICS operations in response to various terminal errors. Since it is impossible for CICS to anticipate all courses of action, the error handling facilities have been designed to allow the user maximum freedom in providing unique solutions for errors occurring within his terminal network. Three CICS components are involved in the detection and correction of terminal errors: 1. Terminal Control program (DFHTCP) 2. Terminal Abnormal Condition program (DFHTACP) 3. Terminal Error program (DFHTEP) DFHTCP and DFHTACP are provided by CICS to perform certain basic detection and correction functions. DFHTEP is provided by the user who wishes to expand or alter the basic functions performed by DFHTCP and DFHTACP. A dummy DFHTEP is distributed with CICS containing only a DFHPC TYPE=RETURN macro instruction. TERMINAL ABNORMAL CONDITION LINE ENTRY (TACLE) When an abnormal condition occurs that is associated with a terminal or line, DFHTCP places the terminal out of service and dynamically creates a Terminal Abnormal Condition Line Entry (TACLE) which is chained off the real line entry on which the error occurred. The TACLE contains all the error information necessary for proper evaluation of the error, plus special action indicators that can be manipulated to alter the error correction procedure. DFHTACP is then attached by the Terminal Control program and provided with a pointer to the real line entry (TCTLE) on which the error occurred. After performing certain basic error analysis and establishing default actions to be taken, DFHTACP gives control to DFHTEP by issuing a DFHPC TYPE=LINK macro instruction. DFHTACP passes the TACLE to DFHTEP so DFHTEP can examine the error and provide an alternate course of action. Once the user has performed his desired function in DFHTEP, he should return control to DFHTACP by issuing a DFHPC TYPE=RETURN macro instruction. DFHTACP then performs the necessary actions as dictated by the action flags within the TACLE. When DFHTEP receives control from DFHTACP, the TCA Facility Control Address (TCAFCAAA) contains the address of a TACLE. The TACLE is created by the Terminal control program when the error occurs and contains all the I/O error information provided by BTAM. To symbolically access the information contained in the TACLE, CICS provides two symbolic storage definitions (DSECT's) which can be copied into DFHTEP. These DSECT's are DFHTACLE and DFHTCTLE. DFHTACLE describes the first twelve bytes of the TACLE which contain CICS error information; DFHTCTLE describes the remainder of the TACLE which contains a copy of the Data Extent Control Block (DECB) at the time the error occurred, plus other valuable information. To establish addressability to the TACLE, DFHTEP must provide, upon entry, the instruction: L 120 TCTLEAR,TCAFCAAA LOAD TACLE BASE REGISTER where TCTLEAR is symbolically defined as the base register for the TACLE. If the user desires to access the real line entry in the TCT, its address is at location TCTLEDCE within the TACLE. It is the user's responsiblitity, under these circumstances, to maintain addressablity bEtween the TACLE and the real line entry. DFHTEF PROGRAMMING CONSIDERA~IONS There are some situaticns in which CICS may attempt to send a message to an inFut cnly terminal. These might be, for example, an Invalid Transaction Identification message, an ATP batch count, or a message erroneously sent by an aFFlication Erogram. The user should provide a Terminal Error Program (named DFHTEP) to re-route these messages to a system destination such as CSMT or CSTL or other destinations through the facilities of Transient Data or Interval Control. A simular situation exists when a message is sent to a 3735 terminal operating as an input batch device. An attempt to write to the 3735 before the receipt of the End of Transmission (EOT) gives control to DFHTACP. If no DFHTEP is provided, the current transaction will be abnormally terminated and the line will be disconnected. !he TACLE is the basic interface that should be used by user-written DFHTEP to d~termine the nature of the error that occurred and to indicate what course of actien is to be taken. Before giving DFHTEP control, "DFHTACP establishes certain default actions tc be taken, depending uFcn the error condition. within DFHTEP, the user may choese to accept the default action under certain circumstances and alter the action under ether circumstances. To indicate that an alternate action is to be taken, the user must modify the action flags contained in the two-byte field of the TACLE labeled TCTLEECB+1 and TCTLEECB+2 (the second and third bytes in the DECB copy). "--- The default actions scheduled by DFHTACP before entry to DFHTEP are described in the following; the error code is found in the TACLE at TCTLEPFL. 1 2 3 4 5 6 = = = = = = Line out of service Terminal cut of service Abend transaction switched line disconnected Disconnect switched line Release TCAM TIOA (X'80' (X '08 ' (X'04' (X'20' (X' 10' (X'80' at at at at at at TCTLEECB+1) TCTLEECB+1) TCTL E EC B+ 1) TCTLEECB+1) TCTLEECB+1) TCTLEECB+2) ERROR CODE ACTION SET ~X ~!]TA~~ (.2.x11]Q1I~ 1A]]1) X' 81' X' 82' (TCEMC MTL) (TCEMCTRL) Input msg exceeds read length Translation error (lCT does not correspond to TCP) X' 84' (TCEMCTCT) TCT search error a. switched line - Real terminal h. switched line - Dummy terminal c. Non-switched line X'85' (TCEMCROT) Invalid write request a. A write request was made to a terminal in INPUT status. b. A write request was made to a 3735 before 'EOT' (EOF condi tion) was received from the 3735 during 3 2 3 o 1 3 3 121 EInOR CODE (~!11].Q11~ ACTION SET 1A]]1) ~! ~:f]TA~R batch transmiEsion. X'S6' X' S 7' X' S S' (TCEMCPL) (TeEMCUI) (TCEMCIER) polling list error Unsolicited input a. TCAM Terminal "Receive Only"; Terminal "out of Service"; Task has not issued READ b. Input has occurred on an outof-service terminal. (3735) ETAM return code on read a. Local 3270 open failure, Invalid RLN, unreliable information (DOS), device under OPTEP b. All other conditions 2 6 2,6 o 2 2,3 1,3 X'S9' (TCEMCSM) Error status received frcm remote 3270·s. a. 3270 operation check 3 b. 3270 intervention required 0 c. 3270 all other conditions 2,3 d. 3735 all conditions 0 X' SA' (TCEMCTO) 7770 32-second timeout X' SB' (TCEMCOBE) Hardware buffer exceeded (shift character net pIoperly accounted for) X' SC' (TCEMCOER) ETAM return cede on write a. Local 3270 open failure, Invalid RLN, unreliable information (DOS), device under CLTEP b. All other conditions X'SD' X'SE' X' SF' (TCEMCOLZ) (TCEMCNOA) (TCEMCOAE) output length zero No output area provided Output area excEeded (TIOATDL value larger than output area) X' 94' X' 95' (TCEMCUC) (ICEMCUCS) unit unit a. b. check (actionE same as TCEMCUCS) check (should not occur) Not ETAM line or L3270 Switched line disabled (CICS/OS) in combination with following: Intervention sense c. Switched line d. Dummy terminal e. Non-switched line 3,5 3 2,3 1,3 3 3 3 1 4 3,4 1 2,3 Data check sense f. Real terminal g. Dummy terminal 2,3 1 Timeout sense h. READ text command/Start-Stop device i. Real terminal j. Dummy terminal 0 2,3 1 All other Eense 122 1 ACTION SET EBBOB CODE (.2111]Q1!f ] ! In::l! T A£~ 1!ln~1) X' 96' X' 97' (TCEMCUE) (TCEMCUES) Unit Unit a. b. c. X' 98' (TCEMCNR) (TCEMCUDT) (TCEMCICR) Negative response to addressing Undetermined unit error The terminal entries on the 'to' and 'from' device did not specify the COPY feature (3270). X' 99' X' 9B' exception (actions same as TCEMCUES) exception (shculd not occur) switched line 3,4 Real terminal 2,3 Dummy terminal 1 2,3 1,3 3 Tpe device address specified for the 'to' device does not exist on the control unit. The length of the COpy command was not specified as one. X'9C' (TCEMCIMB) Invalid message blcck received. a. An unidentified message block was received from a local or remote 3270. b. The type of input block received from a 3735 did not agree with the mode of the active transaction inquiry/batch. 2,3 2,3 X'9D' (TCEMCICM) An incomplete message was received from a remote 3270. The device terminated transmissicn prior to message completion (that is, EOT received prior to ETX). 2,3 X' 9F' (TCEMIDR) TeAM has issued-an invalid destinaticn return code to CICS. 3 X' AO' (TCEMCWOT) Invalid Read request: a. A Read request was issued to a terminal in RECEIVE status. h. A Read was issued to a 3735 terminal after EOT (EOF condition) was received from the terminal during batch transmission. X' A1 II (TCEMCIDB) 3 3 A transaction has requested a DFHTC TYPE=(RESET,DISCONNECT) on a switched binary synchronous line and no EOT has been receive~ from the terminal; this indicates more data is to fellow. Terminal Control issues a read to the terminal if an ~OT has been received. If the EOT is not received on that read, the error code is set and passed to DFHTACP. Following is a diagram of the Terminal Abnormal Condition Line Entry (TACLE) which is Foin~ed to by the TCAFCAAA field upon entry to DFHTEP: 123 TEBMINAL ABNORMAL CONDITION LINE ENTRY r-- I 0 * ------4 BYTES--------->** ******************************************************* 4 * * STORAGE ACCOUNTING AREA **---------------------------------------------------* * 1!..§Z·* <------ o 4 8 * TCTLEPSA * * TCTLEPCH * * * ACDRESS OF TRANSIEN! DATA OUTPUT AREA **---------------------------------------------------* * 8 * TCTLEFFL * C C 16 10 * * 14 18 40 28 TCTLEPTE * * * * * * *---------------------------------------------------* * TCTLEDCB * * 24 * * ERROR FLAGS * SPECIAL IND * TCTTE DISPLACEMENT * *---------------------------------------------------* TCTL~ECB BTAM * * * * * ACTION * BEGINNING * * RESERVED * RETURN * CODE OF DECB FLAGS *FOR DFHTACP* * * * *---------------------------------------------------* * 20 TCTLEPF2 NOT USED * * * ACTUAL LINE ENTRY ADDRESS **---------------------------------------------------* * * * NO! USED ** * *---------------------------------------------------** * * * * NO! USED TCTLECSW * * BSAM STATUS 44 * * * *---------------------------------------------------* * TCTLEALP * * 2C * ESAM * NOT USED * SENSE * * * ***************************************************** ~.!§£1~ce.ID§n1 12.§.f~ ]ex~ ~gg§ ].Y1§.§ 1~~..§1 l1..§~n.!ng 0 0 4 4 4 4 TCTLEPSA TCTLEPCH Storage accounting Pcinter to 100 bytes of user storage that can be used to write to Transient Data. This storage must not be freed by DFHTEP, as DFHTACP may reuse it. 8 8 1 TCTlEPFL Error flags Input error Translation error TCT search error Invalid write 81 82 84 85 124 86 87 88 89 Polling list error Unsolicited input Input event rejected status message received 7770 32-second timeout Hardware buffer exceeded output event rejected Output length of zero No output area Output area exceeded unit check unit check (should not occur) Unit exception unit exception (should not occur) Negative response Undetermined I/O error copy error (3270) Invalid message block Incomplete message Invalid TCAM destination Invalid read Invalid disconnect 8A 8B 8C 8D 8E 8F 94 95 96 97 98 99 9B 9C 9D 9F AO A1 (All code s not listed are reserved) 9 9 1 TCTLEPF2 Special indicator Dummy terminal 01 10 A 2 TCTLEPTE Displacement from line entry to terminal in error 12 C 48 TCTLEECB DECB/copy of line when error occurred Following is the definition of the action bits (0,3,4,5,6 and 7) and information bits (1 and 2) and is the only portion of the copy of the DECB that can be altered. They are located at label TCTLEECB+1. In the second interface byte (TCTLEECB+2), bit 0 is used to process TCAM unsolicited errors. Upon entry to TEP if this bit is set for unsolicited input, it indicates that the data is destined for a terminal entry that is either out of Service or in Receive Only status. If not set· in this manner, the terminal entry for which the data is destined has a task which has not issued a READ request. Upon entry to TEP, this data is on the Input Queue Terminal Entry ·storage chain, and is located by label TCTLEIOA in the TACLE. Upon return to TACP from TEP, this bit (if set) is used to free unsolicited data or to allow another time delay cycle if not set. 13 1 D Bit 0 TCTLEECB+1 Interface byte o••• Place line in service Place line out of service Information Bit Not used Non purgeable task exists 1 ••• Bit 1 • O•• • 1 •• 125 .!!§£.!. Bytg§ l!~l£.!. 1£Q~1 k1~ani!EI on terminal Bit 2 Information Bit Not used Switched line has been disconnected by BTAM • .0. • • 1• Bit 3 • •• 0 • •• 1 Bit 4 Bit 5 Bit 6 • 1 •• • • O. Bit 7 14 O••• 1 ••• .0 •• E 1 Bit 0 · ... • • 1. Take terminal's associated control unit off poll list · ... • •• 0 Do not abort WRITE or free terminal storage on task abend or no task present on terminal · ... • •• 1 Abort terminal WRITE requests and free terminal storage on task abend or no task present on terminal TCTLEECB+2 Interface byte 2 o••• Do not release TCAM TIOA Release TCAM unsolicited input TIOA 1 ••• Bit 1-7 15 20 42 44 F 14 2A 2C 1 4 2 1 Do not disconnect line Disconnect line Place terminal in service Place terminal out of service Do not abend task Abend task Leave terminal's associated control unit on poll list TCTLEECB+3 TCTLEDCB TCTLECSW TCTLEALP Reserved BTAM return code Actual line entry address BSAM status BSAM Sense The following factors should be considered when altering the action bits in the TACLE: 126 1. If the "task abend" flag is set by DFHTACP (X'04' at TCTLEECB+1), the "non-purgeable" flag (X'40') is also set if the task is non-purgeable. 2. If the "task abend" bit is on upon return to DFHTACP from DFHTEP and a non-purgeable task exists on the terminal, the terminal is placed out of service and the task remains attached to the terminal. . 3. If a dummy terminal is indicated (X'01') at TCTLEPF2, a disconnect request from DFHTEP is not honored by DFHTACP. (A dummy terminal is created whenever an error occurs on a terminal whose address does not exist in the TCT.) 4. The "switched line disconnected" bit is used by DFHTACP upon return from DFHTEP to logically disconnect the switched line that has been physically disconnected. If DFHTEP determines that the line has not been physically disconnected, DFHTEP may reset this bit. 5. If the "switched line disconnected" bit or the "disconnect switched line" bit is on, upon return from DFHTEP, the "task abend" bit should also be set to purge the task from the disconnected terminal. If this is the· case and if the task is not terminal purgeable, DFHTACP writes an INTERCEPT REQUIRED message to destination CSMT and places the terminal out of service. 6. The dummy terminal indicator at TCTLEPF2 is set on errors such as: (1) BTAM return on input, (2) binary synchronous outputs performed for TCP where no terminal is indicated, and (3) other errors where no terminal error conditions are indicated. Therefore, if Dummy Terminal is indicated, task abend and write abort are not set. The Dummy Terminal is only used to identify the line. 7. The write abort hit (bit 7 at TCTLEECB+2) task abend request in TACP as a default. the write abort bit is used as follows: is always set with Upon return from TACP, a. Causes the Terminal control write requests to be aborted. h. If the task is being abended and is terminal purgeable or task exists on the terminal, the Terminal storage will be freed. The following is an example of the logic steps necessary to design a portion of the Terminal Error program. In this example ten retries are provided per terminal; however, the logic could be used for any number of retries. The following assumptions are made: USER FIELD A (PCISA VE) Represents a six-byte field in the Process Control Information (PCI) area of the TCTTE (see the TCT macro definition of the TCTUAL operand). This field is used to preserve the count of input and output from the TCTTE when the first error occurs. These counts are contained in three-byte fields located at TCTTENI and TCTTENO within the TCTTE. USER FIELD B (PCICNT) Represents a user-defined field used to accumulate the count of recursive errors. It would most likely he in the Process Control Information (PCI) area of the TCTTE. SYSTEM COUNT (TCTTENI) Represents the six-byte field in the TCTTE that contains the terminal input and output counts (TCTTENI+TCTTENO). In the example, these two adjacent fields are considered as one six-byte field. Since this example requires access to the TCT terminal entry (TCTTE) to examine the SYSTEM COUNT and to also locate the Process Control Information (PCI) area, the DFHTCTTE symbolic storage definition is included so fields may be symbolically referenced. ************************************************************************ * * DFHTEP RECURSIVE RETRY ROUTINE * * ************************************************************************** 127 TEPBAR EQU TCTTEAR EQU PCIBAR EQU COPY EJECT COpy COPY EJECT PCIAREA DSECT PCISAVE DS PCICNT DS EJECT DFHTEP CSECT BALR USING L L * * * * * AH 2 9 8 DFHTCTTE TEP PROGRAM BASE BASE REGISTER FOR TCTTE BASE FOR PCI COPY TCTTE DEFINITION DFHTACLE DFHTCTLE COPY TACLE SYMBOLIC DEFINITIONS COPY DECB DEFINITION 6X PL2 USER FIELD A USER FIELD B TEPBAR,O *,TEPBAR TCTLEAR,TCAFCAAA TCTTEAR,TCTLEDCB ESTABLISH PROGRAM ADDRESSABILITY TCTTEAR,TCTLEPTE L PCIBAR,TCTTECIA USING PCIAREA,PCIBAR TM PCICNT+1,X'OC' BO CKCOUNT RESET MVC PC IC NT, = PL 2 ' + 0 ' * MVC PCISAVE(6) ,TCTTENI AP PCICNT,=P' l' CP PCICNT,=P'10' BNE RETRY ZAP MVC PCICNT ,=P' 0' PCISAVE(6) ,TCTTENI NORETRY PCISAVE(6) ,TCTTENI * * * * INCR * * * * B CKCOUNT CLC * * BNE RESET B INCR DS OH NORETRY DS OH * * * * *RETRY 128 LOAD TACLE ADDRESS LOAD TCTTE BASE WITH REAL LINE ADDRESS INCREMENT BASE BY THE TCTTE DISPLACEMENT~ THIS GIVES ADDRESSABILITY TO TCTTE. LOAD PCI AREA ADDRESS ESTABLISH ADDRESSABILITY HAS USER FIELD B EVER BEEN INITIALIZED TO A PACKED DECIMAL NUMBER? •• YES, SO COMPARE THE SYSTEM COUNT WITH THE EXISTING COUNT IN FIELD B; •• NO, SO INITIALIZE FIELD B TO A PACKED DECIMAL O. SAVE THE CURRENT SYSTEM COUNTS. THIS IS A NEW ERROR, OR FIRST TIME THROUGH INCREMENT THE NUMBER OF TIMES THIS SAME ERROR HAS OCCURRED. (RECURSIVE COUNT) HAS THE MAXIMUM RECURSIVE ERROR LIMIT BEEN REACHED? •• NO, SET ACTION INDICATORS FOR RETRY ATTEMPT CLEAR AND RESET USER FIELDS * FOR NEXT ERROR SET ACTION INDICATORS FOR NO-RETRY. HAS SYSTEM COUNT CHANGED SINCE LAST ENTRY TO TEP? •• YES; THAT MEANS THIS IS A NEW ERROR SINCE SOME I/O ACTIVITY HAS OCCURRED ON TERMINAL •• NO; THAT MEANS THIS IS A RECURSIVE ERROR, SO INCREMENT THE RECURSIVE COUNT AND CHECK FOR RETRY. THE USER WOULD INCLUDE HERE THE CODE NECESSARY TO ALTER THE FLAGS IN THE TACLE SO THAT A RETRY CAN BE PERFORMED ON THE TERMINAL. THE USER WOULD INCLUDE HERE THE CODE NECESSARY TO ALLOW DFHTACP TO TAKE FINAL ACTION ON THE TERMINAL (I.E., ABEND TASK, PUT LINE OUT OF SERVICE, ETC.) * The above example is intended only to serve as an illustration of a recursive error handling technique and the steps necessary to establish addressability to the applicable control blocks. BFRTEP ALTERNATE INTERFACE (CICS/OS only) An alternate interface is provided in the CICS/OS-STANDARD system for the purpose of maintaining compatibility with the CICS/OS-STANDARD Version 1 user who currently has code dependent upon this interface. This interface is provided when the user specifies V1CMPAT=YES in the BFHSG ~YPE=CSO macro instruction during system generation. Upon detection of an error, control is passed to DFHTEP for analysis; the TWA ccntains the following information: ] 1!]]1 Q~£:JBI!I01! 1 TnACOEA Contains the status byte from BTAM 1 TWACOBA+1 Contains the sense byte from BTAM 1 T~ACOEA+2 contains the teleprocessing OP code being issued 1 TlrIACOEA+3 Reserved 4 TWACOBA+4 contains the transaction ID if one exists for the terminal in error Y'I~.§ User-~ritten IFHTEP must place the line or terminal in service or cut of service if so desired. If the task is to ce abended, DFHTEP must place a X'FE' at label TWACOEA before returning control to DFHTACP. 7770 32-SECOND TIMEOUT CONSIDERATIONS If a terminal ccnnected to the 7770 Audio Response Unit goes "on hook" while no I/O operation is outstanding, the 7770 does not present the unit exception to the channel. This situation can occur when the terminal operator makes an inquiry and hangs up before receiving a response. After this occurs, all writes to the line appear to complete normally. All reads complete normally at the end of the 32-second timeout with a zero data length. When a 32-second timeout occurs, either the terminal operator has not entered anything for 32 seconds, or the terminal operator has hung up and the 7770 did not inform CICS. CICS cannot distinguish between these two conditions; therefore, CICS handles every 32-second timeout as an error condition. DFHTACP goes to DFHTEP with defaults of tISCCNNECT SWITCHED LINE and ABEND THE TRANSACTION. If DFHTEP does not disccnnect the switched line, CICS writes the "ready" message and initiates another read. 2740 MODEL 2 CONSIDEBATICNS When DFHTACP detects a negative resFonse from a 2740 Model 2, the write operation will be retried after a 26.64 second time delay. This delay allows for operator reaction time etc. If the delay time factor is to ce changed it may be done by storing the new time delay factor at TCTTEBC. The value is a positive binary number representing hundredths of seconds, (10 seconds would be a value of F'1000' or X'C00003E8'). The cause of the negative response may be determined by examining the field TCTLERSP. 129 Contents of TCTLERSP meanings are as follows: X'04' X'02' X 1 20' X'10' X'13' x'oa' Terminal Terminal Terminal Terminal Terminal Contents in in in in in of bid mode communicate mode communicate mode with document device down local mode communicate mode but out of paper buffer are being printed. Failure to set a time delay of a sufficiently large value may cause a loop at the terminal wherein pressing the reset key will not be recognized. To initial program load (IPL) the System/7 from CICS, the user must write a transacticn that issues an automatic transaction initiation request to either Interval Contrel br Transient Data Control. This transaction is usually initiated from the master terminal or from a seguential terminal. The initiated transaction is started on the System/7; it then writes the IPL records to the System/7. The 1PL records are prepared by the user and consist of: 1. 2. 3. UZERO, a utility module U~IPL, a utility module System/7 storage load UZERO and UTIEL are provided in object deck form on the MSP/7 distribution tape under member names CAAUZERO and CAAUTIPL, respectively. If link edited into the user-written application program, UZERO and UTIPL are available for transmission in a suitably translated format. The first two bytes of each of these modules is a count of the number of characters in the remainder of the module. These two bytes must be placed in the user's TIOA at TIOATDL by the application program. The remainder of the module is moved to TIOADBA. UZERO and UTIPL may then be transmitted to the System/7 by issuing the DFHTC TYPE=(WRITE, WAIT) macro instruction in the application program. The System/7 storage load is generated using the TELETRANS option of the MSP/7 Output Handler. The storage load is comprised of aO-character records that may be read via the Transient Data or File Control facilities of CICS and transmitted to the System/7 by issuing a series of DFHTC TYPE=(WRITE, WAIT) macro instructions. If a DFHPC Type=Return macre instruction is used to allow the System/7 to begin execution, the user must ensure that no automatically initiated transaction is scheduled to begin on the System/7 until at least 10 seconds have elapsed following execution of the DFHPC Type=Return macro instruction. For more informatien concerning the preparation of 1PL records for the System/7, SEe the publication ~Qg~l~~ ~Y2tem ~~Qg£E~§ (~~EL1) g~99~~~~jng guigg (GC34-0013). 2260-compatibility sUFPort for the 3270 Information Display System allows the user to run his currently operational 2260-based transactions frcm a 3270. 130 During CICS· system generation, the user must request 2260 compatibility to be included, thereby generating the necessary code to provide conversion of 2260 data streams fIom user-written application programs to the appropriate 3270 data stream format. When the 3270 operates with a "compatibility" transaction, incoming data from the 3270 is converted and presented to the user-written application program in 2260 format. In most cases, no changes are required to the user-written program. Because 2260 ccmpatibility is specified by transaction as well as by terminal, non-2260-based transactions have full access to all facilities of the 3270. Only when a 2260-compatible transaction is attached to a 2260-compatible 3270 does CICS perform the editing of the input and output data streams. If the transaction is not specified as 2260 compatible, or if the terminal is not specified as supporting 2260 compatibility, no editing occurs for the data streams. In that case, if the data streams are not valid 3270 data streams, the results are unpredictable. Two modes of compatibility operation aIe provided: FULLBUF. FeRMAT and 130.1 FORMAT mode takes full advantage of the 3270 formatting and data compression facilities, and is the preferred method of 2260 compatibility, particularly for the operation of remote 3270·s. However, some 2260 facilities cannot be supported under FORMAT mode. For information concerning which facilities are available, see the discussion under the topic "Screen Techniques". FULLBUF mode does not use the 3270 data compression facilities and must therefore be used when all lines of input data are desired. For each operator interaction involving a data entry key (ENTER, PF1 PF12), the number of characters transferred is approximately ~qual to the total number of characters on the simulated 2260 screen. The exact number of characters transferred varies depending upon whether the 3270 is local or remote and which model of the 2260 is being mapped onto which model of the 3270. Note~ A terminal is considered to be in compatibility mode from the time a 2260-compatible transaction is initiated until (1) the CLEAR key is depressed, or (2) a 3270 native mode transaction is initiated. For local 3270 operation, the extra data transfer of FULLBUF mode should be transparent to the user with regard to response time. For remote 3270 operation, the response time is a complex function of the present method of 2260 operation and the line speeds used for the 2260 and 3270; however, the increase in the response time (on a transaction basis) should be less than 20% at the same line speed. CICS TABLE PREPARATION FOR 2260 COMPATIBILITY Individual transactions can be flagged for FORMAT or FULLBUF 2260 compatibility through the DFHPCT TYPE=ENTRY macro instruction. The mode of compatibility chosen depends on the 2260 functions required for the application programs that run under this particular transaction code. The characteristics of the 2260/2265 terminal (which the 3277/3275 replaces) are specified by additional operands for the DFHTCT TYPE=TERMINAL macro instruction. They are as follows: COMPAT=NO, (number of characters,number of lines, device type,model number), FEATURE=(PTRADAPT,SELCTPEN,AUDALARM,COPY,BUFEXP, DCKYBD, UCTRAN) * * * The "number of characters" parameter is used to specify the screen size of the 2260/2265 terminal. Applicable parameter values are 240, 480, and 960. The "number of lines" parameter is used to indicate the number of lines applicable to the 2260/2265 terminal or to insert new line (NL) symbols into the 3284/3286 printer output data stream where NL symbols are not provided by the user in the output data stream. Applicable parameter values are 6, 12, and 15. The default value for a 960-character screen is 12. The "device type" parameter is used to specify a 2260 or 2265 terminal or a 1053 printer. The default is 2260. Note that the specification COMPAT=(960,15) results in an error condition since the 2260 (assumed by default) cannot support 15 lines. The "model number" parameter is used to specify a model number for the 2260 terminal being simulated. This parameter provides an interface 131 for any user-written application programs that currently test the TCTTETM field before building device-dependent 2260 data streams. The FEATURE operand has been included in the CICS DFHTCT TYPE=TERMINAL macro instruction to indicate the presence of 3270 Information Display System features (for example, Printer Adapter, Selector Pen, Audible Alarm, Copy feature, Buffer Expansion, uppercase translation, dual case keyboard) and to specify the corresponding 3284 Model 3 Printer on the 3275 Display station. BQig~ A separate DFHTCT TYPE=TERMINAL macro instruction cannot be coded for the 3284 Model 3 Printer because the 3284 Model 3 shares the buffer of the 3275 Display Station. 2260 MODEL-DEPENDENT DATA STREAM Some users require the capability of building 2260 device-dependent data streams. CICS allows the user to build such data streams by providing the terminal type at TCTTETT in the Terminal Control Table eTCT) and the terminal model number at TCTTETM in the TCT. The TCTTETT and TCTTETM fields always contain the 2260 or 2265 terminal type codes and user-assigned model number (as specified in the DFHTCT TYPE=TERMINAL macro instruction) whenever a transaction flagged for CICS 2260 compatibility is dispatched. At all other times, TCTTETT and TCTTETM contain the codes for the 3270 terminal. SCREEN TECHNIQUES Various techniques have been used for entering data using a 2260 screen and keyboard. The following are examples of four basic techniques that may be used. 1. Formatted 2260 screen technique; for example: ~ USER KEYED DATA XA X-CONSTANT DATA X X----XA x------x X------XA x----X X-----X X----XA X----X x--~- X------x With this technique, the constant data is optional and is sent to the user at the start of the transaction. Either FORMAT or FULLBUF mode may be specified, depending upon the user's formatting requirements. 132 2. 2260 tab feature technique; for example: ~ NAME: INITIAL: STREET: NUMBER: CITY: STATE: For CICS 2260 compatibility operation, the colon-tab character combination is replaced by 3270 "unprotected attribute" characters. FORMAT mode may be specified if data is always keyed into every field. FULLBUF mode must specified if any field is to be left blank. (Unlike the 2260, the 3270 does not transmit blank characters unless FULLBUF is specified.) If FULLBUF is not specified, any heading following the blank field is not transmitted to the application program. ~ INITIAL: JONES NAME: NUMBER: STREET: CITY: JA 1515 A STATE: NEW YORK -- FORMAT data stream: NAME:JONES INITIAL:J(NL) :1515(NL) :NEW YORK FULLBUF data stream: NAME:JONES 3. STREET: INITIAL:J (NL) NUMBER:1515(NL) CITY:NEW YOR .. "Endless screen" technique; for example: X NEW DATA A X X X--X OLD DATA X X X X X X ~ t:lE~ 0818 • X with this technique, the 2260 screen is treated as unformatted. The operator keys off the screen, and, wrapping around to the start of the screen, over keys any old data still there. The 2260 transmits a data stream delimited by SMI (start of message) and EOM (end of message) characters, irrespective of any screen wraparound. Either FORMAT or FULLBUF can be specified. In either case, CICS ensures that the data stream is correctly ordered before sending it to the 2260-based transaction. with this technique, there is a difference in operation between FORMAT and FULLBUF modes only in the case of a 480-character 2260 mapped onto a 480-character 3270. Use of FORMAT mode causes 133 the loss of the last character of every 2260 outp~t line. Use of FULLBUF mode limits the data loss to the last character position of the last line but at the expense of transferring a full 480 characters (479 characters plus one attribute character) for each interaction involving a data entry key. It is the responsibility of the user to determine whether his 2260 transaction can tolerate the loss of the last character of each output line. CICS appends a blank character to the end of each 2260 input line, except where the line is terminated prematurely by a new-line (NL) symbol. 4. "Change and enter" technique; for example: H J ~JONES ORIGINAL OLD ROAD EAST 1515 1 RECORD NEW YORK N. Y. 10010_ H J ~JONES UPDATED OLD ROAD WEST 1515 1 RECORD NEW YORK N. Y. 10010 The FORMAT data stream looks like this: JONES J H 1515 OLD ROAD WEST The FULLBUF data stream looks like this: JONES NEW YORK J H 1515 OLD ROAD WEST N. Y. 10010 The 2260 transaction sends an existing record to the screen. After making any necessary corrections to data fields, the operator depresses the ENTER key; the 2260 transaction receives the entire record in its updated version. . with this technique, FULLBUF must be specified for this transaction to ensure that the transaction receives a 2260-compatible data stream. 134 START OF MESSAGE INDICATOR (SMI) For the 2260, X'4A' is displayed as the SMI (~) character. If the SMI character is contained in an output data stream, it is displayed on the 3270 screen as follows: COUN!]! SM! SYM]Q1 ¢ U.S.A. U.K. France Germany $ ¢ or 9 0 At the user's discretion, a different character may be specified during CICS system generation to represent the SMI. Whatever character is chosen, it remains the same for all transactions. If an SMI character is not placed on the screen by the user's 2260 data stream, the operator must then key an SMI character somewhere on the screen. Failure to do so results in no data being transmitted to the application program. After the data has been read in, CICS 2260 compatibility transmits a single blank character to overwrite the SMI character. NEW LINE SYMBOL (NL) For CICS 2260 compatibility, the new line (NL) function is replaced by a field mark character followed by the NL key. Any incoming field mark characters are treated as 2260 NL characters, and the remiinder of the line is discarded. Including the NL symbol in the 2260 output data stream causes the substitution of a 3270 field mark character; the output continues at the beginning of the next line. (The 3270 field mark character displays as a semicolon.) LINE ADDRESSING For a 3270 operating under CICS compatibility, any requests for write at line address are honored. CICS 2260 compatibility converts the line address to the equivalent 3270 buffer address before transmitting the data stream to the screen. 2848 LOCK FEATURE The optional lock feature available on the 2848 Display Control Models 21 and 22 is supported by CICS 2260 compatibility. Any read/lock request is honored by CICS 2260 compatibility by leaving the 3270 keyboard inhibited. The keyboard is reset only if the transaction changes or if a WRITE macro instruction is issued by the application program. 2845/2848 TAB FEATURE The optional tab feature available on the 2845/2848 Display Control is supported by CICS 2260 compatibility. Any tab character (colon) found in the output data stream is replaced by an attribute byte. This attribute byte is converted back to a 2260 tab character on a read operation. 135 Because the tab feature uses an attribute byte, the terminal operator cannot key a tab character from the keyboard. The tab does not display on th~ screen, but is present in the user's input data stream. For proper operation, transactions using the tab technique are required to operate in FULLBUF mode. A tab character should not be inserted as the last character of a line. Because the tab feature uses an attribute byte, the cursor stops at the beginning of each line before stopping at the authorized attribute position, except in the case of 480/480 FULLBUF conversion. The cursor stops only at the authorized attribute position and the last position in the buffer. INITIATING TRANSACTIONS The terminal operator can initiate either 2260 compatibility or 3270 native mode transactions by entering the appropriate four-character CICS transaction code. While in compatibility mode, any start of Message Indicator (SMI) character in the input data stream is recognized by CICS; the succeeding four characters are interpreted as a CICS transaction code. The transaction code must be contiguous and may not span two fields. CICS then initiates the specified transaction. If the specified transaction is a 2260 compatibility transaction, CICS automatically formats the 3270 screen. To allow easy transition between 2260 compatibility and 3270 native mode transactions, some conventions should be followed. Three acceptable methods of transition between transactions are: 1. Clear the screen; then enter the transaction code and any data to be presented to the transaction. In this case, the operator must enter the transaction code at the first position of the screen. The transaction code may be preceded by the SMI character, in which case the next four characters are interpreted as the transaction code. A transaction code may not contain an SMI character. 2. For a terminal in compatibility mode, enter the SMI character, the transaction code, and data. If the transaction to be initiated is a compatibility transaction, all data from the SMI character to the cursor position is treated as a 2260 compatibility data stream and is mapped into 2260 format. For a native mode transaction, the data stream is identical with the data stream from an unformatted screen buffer. 3. For a terminal in native mode with a formatted screen, the SMI character and transaction code must be the first data characters in the data stream. If the transaction code calls for a compatibility transaction, the screen is formatted for 2260 compatibility but no data is presented to the transaction. 4. Always clear the screen before initiating a CICS transaction. 136 }73~ PRQQBAMMINQ £QM~ID~B!~lON~ (Not applicable to CICS/DOS-ENTRY) SYSTEM GENERATION BTAMDEV=3735D and ANSWRBK=EXIDVER must be included in the DFHSG PROGRAM=TCP macro instruction during system generation if support for the 3735 Programmable Buffered Terminal is to be generated for switched lines. TERMINAL CONTROL TABLE PREPARATION FEATURE=AUTOANSR must be specified in the DFHTCT TYPE=LINE macro instruction for all terminals on switched-line networks. To support the 3735 Programmable Buffered Terminal, the following must also be specified: 1. 2. 3. DFHTCT TYPE=LINE,ANSWRBK=EXIDVER. BTAM DFTRMLST macro instruction of the form: SWLST,AN; the user portion of each 3735 DFTRMLST entry must point to the corresponding TCTTE. DFHTCT TYPE=TERMINAL,TRMTYPE=3735. If FEATURE=AUTOCALL is specified in the DFHTCT TYPE=LINE macro instruction, the following must also be specified: 1. 2. BTAM DFTRMLST macro instruction of the form: SWLST,AD. DFHTCT TYPE=TERMINAL,TRMADDR=name, and for batch input, TRANSID=name. INQUIRY MODE CICS deletes the inquiry header on input and inserts it on output. Therefore, inquiry applications require that: 1. 2. 3. A single output record is transmitted. The output block does not exceed 233 bytes (plus a three-byte inquiry header). The output data stream does not contain characters which are invalid for a 3735. (See the 1732 R£Qgramm§£~§ Quig§, GC30-3001.) If multiple inquiries are required in a single connection on a switched line, the user must make provision in his DFHTEP program to keep the line open. To accomplish this he may check for the IOERROR - TIMEOUT condition, a WRITE TR or READ TQ instruction, and TCTTEMIQ set to a hexadecimal blank character (X'40') in TCTTEMCI. Most independent teleprocessing applications require a dedicated network. The Telecommunications Access Method (TCAM) permits multiple applications to share a single network, resulting in more efficient use of terminals and lines. The CICS/TCAM Interface enables CICS to run as an application under TCAM. TCAM is an optional access method that may be used alone or in combination with other access methods currently supported (BTAM, BSAM, and BGAM). 137 One practical use of the CICS/TCAM Interface is to run a "production" CICS in one region and a "test" CICS in another. Running in separate regions, the applications are protected from one another. Operating under TCAM, terminals and lines can be shared by the two CICS applications. Other TCAM applications such as the Time Sharing Option (TSO) can also be running concurrently. In most cases, CICS user tasks that run under BTAM can run under TCAM without modification to the task code. This assumes that the user has properly designed and coded his TCAM Message Control program (MCP). Modifications to his CICS Terminal Error program (DFHTEP) are required to take advantage of the new error codes used in the CICS/~CAM Interface. There are basic differences between TCAM and BTAM design methods. crcs was designed to operate in the BTAM environment. The CICS/TCAM Interface, although resolving most of the differences, must impose some restrictions when crcs is run in a TCAM environment. These restrictions as well as some of the ramifications of selecting various user options are addressed in this section. Also described are the user facilities available and how the user implements and operates his system via the interface. TCAM APPLICATION PROGRAM INTERFACE The TCAM Application Program Interface is a portion of the TCAM Message Control program (MCP). It consists of two types of control blocks, the Process Control Block (PCB) and the TPROCESS block. The PCB defines the application program interface of a partition/region in the system using TCAM. rts purpose is to control communication and storage protection across partition/region boundaries. It also defines the user-written message handler (MH) responsible for processing messages to and from the application program. Since a PCB is required for each application program running with the MCP, a PCB is required to define the CICS application program. The TPROCESS control block controls communication to and from the application program. A separate block is required for both ~nput and output to the application program. The application program ~s frequently referred to in TCAM as the Message processing program (MPP). A TPROCESS block is required for each input queue to CICS and for each output queue from eICS. In CICS there are corresponding Terminal Control Table line entries (TCTLE's) for each input queue and for each output queue (that is, for each TPROCESS block). DD cards (such as those shown in Figure 11) are used to correlate the TCAM control blocks with the crcs control blocks. The crcs Terminal Control Table contains the DCB. The DDNAME specified in the Terminal Control Table macro instruction (DFHTCT TYPE=SDSCI,DDNAME=name) names the DD card. In the DD card, the QNAME field names the TCAM TPROCESS block. No exceptions are required for crcs to the TCAM Application Program Interface just described. For additional information, refer to the 1CA~ f~Qgramm~~~§ gyid~ ~nQ Refe£~£~ ~~ll~al (GC30-2024). 138 MCP (TCAM) APPLICATION PROGRAM INTERFACE APPLICATION r'lESSAGE HANDLER MPP (CICS) ~I_~ ) STARTMH Figure 11. DD card correlation of TCAM and CICS control blocks CICS/TCAM INTERFACE A TCAM input process queue is considered to be a "line" to CICS. For each input process queue there is a CICS Terminal Control Table line entry (TCTLE). Note that TCAM requires the application program (CICS) to have a DCB for each TPROCESS block; separate TPROCESS blocks are required for input to and output from the application. Therefore, each TeAM output process queue is also considered to be a line and has a corresponding CICS TCTLE. Each TCTLE references its own DCB generated by the DFHTCT TYPE=SDSCI macro instruction in CICS. The CICS Terminal Control Table terminal entries (TCTTE's) define the terminals associated with a particular line entry (TCTLE). For each physical terminal communicating with CICS via TCAM, a corresponding TCTTE containing the terminal identification must be associated with a TCTLE. Duplicating individual TCTTE's for both the input TCTLE and the output TCTLE is avoided by attaching a single, special TCTTE to the input TCTLE and attaching all the individual TCTTE's to the output TCTLE. Although attached to the output TCTLE, they are used for both input and output processing. Each input record from TCAM must contain the source terminal identification (OPTCD=W specified in the CICS DFHTCT TYPE=SDSCI macro instruction). Using this identification as a search argument, the corresponding TCTTE can be located by CICS. Using the POOL feature (POOL=YES of the DFHTCT TYPE=LINE macro instruction), it is possible to establish a pool of common TCTTE's on the output TCTLE that do not contain terminal identifiers. As required, terminal identifiers are assigned to the TCTTE's or removed from association with the TCTTE's. This POOL feature necessarily imposes a number of restrictions and should be thoroughly understood before being implemented. For additional information, see the discussion of the POOL operand. 139 When TCAM is specified, CICS assumes that the user transaction data passed to it from the TCAM queue is in the proper format to be passed directly to the user task. Except for the removal of the source terminal identification, CICS does not alter the data it receives. It is the user's responsibility (via his MCP) to properly prepare the data, such as translating to EBCDIC, stripping line control characters, and deblocking. The user may optionally bypass the CICS routine that removes the source terminal identification by returning from the user-written input exit (XTCMIN) in TCP with a displacement of zero bytes. Similarly, CICS assumes that the user transaction data passed to it for TCAM has been properly formatted for direct placement on the TCAM output process queue. Except for the insertion of the destination identification and the device-dependent control character, CICS does not alter the data it receives. It is the user's responsibility (via his MCP) to properly prepare the data for the destination terminal, such as translating and inserting line control characters. Below is a generalized description of the sequence of events that occurs in CICS when interfacing with TCAM. A TCAM notifies CICS that it has data for a particular input TCTLE by posting its ECB. B CICS gets a TIOA and attaches it to the special input TCTTE in the TCTLE. C CICS issues a READ to TCAM which results in TCAM passing the data over the partition or region boundaries to the CICS TIOA. CICS indicates at this time that it has data to process. (See Figure 12.) D The input TCTLE points to the corresponding output TCTLE in response to the OUTQ specification of the DFHTCT TYPE=LINE macro instruction. E The individual TCTTE's on the output TCTLE are searched for a matching source terminal identification. If POOL=YES has been specified, a free TCTTE is assigned to this : source terminal identification. (See Figure 13.) F If an input user exit (XTCMIN) has been specified, CICS links to the user exit routine where the user may edit his input data prior to passin g it to his task. (See the discussion of XTCMIN in the section "TCAM User Exits". ) If no exit has been sped:tfied, CICS removes the eight-byte source terminal identification field inserted by TCAM. No other editing of the data is performed. 140 A check is made to determine whether a task is attached to the individual TCTTE. If not, go to Step H. G If a task is attached, a check is made to see if the task has issued a READ. If a READ request exists, go to Step J. If not, CICS halts the processing of data in the queue until the TCTTE becomes available or the attached task issues a READ. H CICS attaches the appropriate task. A user exit is available prior to the actual attach. (See the discussion of XATTACH in the section "TCAM User Exits".) If the task could not be attached (e.g., a "maximum task" or "short on storage" condition exists), CICS remembers it has data to process and exits DFHTCP. On the next scan, it again tries to attach the task. I Once a task is attached, CICS stores the TCAM segment identifier in the TCTTE (if segment processing was specified by including the C parameter in the OPTCD operand of the DFHTCT TYPE=SDSCI macro instruction). J CICS passes control to the attached task. TCAM INPUT PROCESS QUEUE INPUT TCTLE SPECIAL TCTTE TIGA Figure 12. CICS issues a TCAM read 141 TCAM INPUT PROCESS QUEUE INPUT TCTLE QUTQ= SPECIAL TCTTE (ABC) TIOA OUTPUT TCTLE INDIVIDUAL TCTTE'S Figure 13. 142 After TCAM read CICS attaches TIOA to corresponding TCTTE A The user issues a WRITE request in his application program. B The TCP terminal scan recognizes the WRITE request. C CICS checks to determine if an output user exit (XTCMOUT) has been specified. If specified, CICS links to the user exit routine where the user may edit his output data prior to passing it to TCAM. (See the discussion of XTCMOUT in the section "TCAM User Exits".) D CICS checks the four-byte TCTTE field TCTTEDES for a destination saved as a result of DEST=NAME or DEST=YES having been specified in the DFHTC TYPE=WRITE macro instruction. If present, CICS inserts it in the eightbyte destination field and left justifies the field, padding blanks to the right. Otherwise, CICS moves the source terminal identification from the TCTTE to the destination field. E CICS moves a one-byte communication control character into the ninth byte of the TCAM work area. See the section "Device Dependent Considerations". F CICS issues a TCAM WRITE to transfer the data to TCAM. G After checking for successful completion of the WRITE to TCAM, CICS posts the user task "dispatchable" if a task is still attached to the TCTTE. Otherwise, CICS frees the TCTTE for a new task. The CICS/TCAM Interface implementation has resulted in the expansion of the CICS Terminal Error program (DFHTEP) error codes and conditions previously existing in CICS. The additional codes and conditions are described in the section "Creating a Terminal Error Program {DFHTEP)". The DEST operand of the DFHTC TYPE=WRITE macro instruction can be used to route an output message to a destination defined by the user in the TCAM MCP. This operand can be used to send a message to a destination other than the source terminal (such as to another terminal, a list of terminals, or another application). If DEST=name is specified, "name" is stored in the four-byte field TCTTEDES. If DEST=YES is specified, it is the user's responsibility to have placed the destination name in TCTTEDES prior to issuing the WRITE macro instruction. CICS moves the data from TCTTEDES into the destination identification field prior to placing the data on the TCAM output process queue. The user may bypass the CICS routine that inserts the destination field by taking the XTCMOUT user exit and returning to CICS from the exit with a displacement of zero. In this case the user must ensure that the TCAM header is properly formatted for output. If the DEST operand is omitted, CICS inserts the source terminal identification from the TCTTE into the destination identification field. The CICS/TCAM Interface supports the TCAM segment processing capability. It permits segments of a message to be forwarded to CICS rather than waiting for the entire message to be received. If the user specifies segment processing (by including the parameter "C" in the OPTCD operand of the DFHTCT TYPE=SDSCI macro instruction), CICS passes the segment to the user and places the one-byte position field control byte in the TCTTE field labeled TCTTETCM. Similarly on output, the user must supply the control byte in TCTTETCM for CICS to pass to TCAM. For additional information on segment processing, refer to the discussion of the OPTCD operand of the application input and output DCB in the OS/MI! ~ng QS/MV! TCA~ gfQgf~~£~2 Qyide (GC30-2024). 143 In generating the TCAM Message Control program the user defines each physical terminal to TCAM by means of a TCAM TERMINAL macro instruction. since CICS also requires terminal definitions, the user must prepare a Terminal Control Table terminal entry (TCTTE) for each terminal through use of the DFHTCT TYPE=TERMINAL macro instruction. As a result, a one-far-one correlation exists between terminal definitions in TCAM and in CICS. In a highly restricted environment, this duplication of terminal definitions can be reduced through use of the POOL feature (DFHTCT TYPE=tINE,POOL=YES). Instead of a one-for-one relationship, a "pool" of generalized TCTTE's is defined for a TCAM process queue (line). When a transaction is received over the TCAM "line", a search is made for an available TCTTE in the pool. When one is found, it is assigned the source terminal identification for the duration of the task. Upon completion of the task, the TCTTE is available for reassignment. If there are no available TCTTE's to handle the next transaction from the line, the line remains locked until a TCTTE becomes available through task completion. The number of TCTTE's in the pool influences the degree of multitasking. Because the TCTTE's are not permanently assigned, the use of the POOL feature is possible only in a restricted environment. The POOL feature is applicable only for those applications in which each record received over the input process queue is a new transaction. Thus, the user should thoroughly analyze his environment before specifying the POOL=YES option in the DFHTCT TYPE=LINE macro instruction. The following are line pool restrictions of which the user must be aware: 144 1. Only one terminal type is permitted per TCAM line (process queue) because of certain device dependencies within CICS. 2. Tasks attached from transactions over the TCAM line are not permitted to issue Terminal Control READ requests. This includes GET, PAGE, and CONVERSE because they contain implied READ's. Violation of this restriction can cause a permanent line lock on the input process queue, thereby preventing any further transactions on the queue from reaching CICS. 3. Segment processing requires multiple READ's which can cause a permanent line lock. Therefore, segment processing (OPTCD=WUC) must not be specified. 4. Automatic task initiation is not applicable in the pool environment. 5. Statistics are accumulated for each TCTTE in the pool; however, the statistics cannot be correlated to the physical terminals. 6~ Only one sign on line pool at any is propagated to on is rejected. terminal entries accepted. 7. Master terminal functions require multiple READ's and cannot, therefore, be used on terminals with pooled TCTTE's. can exist for all terminal entries in a given one time. The first sign on received by CICS all terminals in the pool. Any subsequent sign A sign off clears the sign-on data from all in the pool; a subsequent sign on is then Line locking of two types can occur: (1) a temporary lock that resolves itself in time, and (2) a permanent lock that remains permanent unless the user takes action in his Terminal Error program. Adherence to the pool restrictions outlined in the previous topic should eliminate the permanent lock situation. A temporary line lock occurs when no TCTTE's are available in the pool and a new transaction appears on the input queue. CICS locks the queue until an existing task completes execution, thus freeing a TCTTE. In this case, the completion of existing tasks is not dependent upon additional input from the queue. A permanent line lock can occur when multiple reads are required to complete a task. For example, assume that there are two TCTTE's in the pool, that a task is attached to each, and that the segments in the input queue are in the following order: 1. 2. Segment #1 for a third transaction Subsequent segments for the two active' tasks Since no TCTTE is available in the pool for the third transaction, it must wait for a task to complete for a TCTTE to become available. Because the TCAM input queue is processed sequentially, tasks 1 and 2 are unable to receive their subsequent segments. Hence, they cannot complete, and the queue remains permanently locked (because line pool restriction 2 of the previous topic was not observed). Since a queue is a sequential data set, the SEcond record on the queue cannot be retrieved until the first record has been processed. To keep records flowing smoothly through the queue, it is essential that each record be processed as soon as it arrives. In the CICS/TCAM Interface, "processing the record" means detaching the TIOA (containing the record) from the special input TCTTE and attaching it to the individual TCTTE correlated to the actual physical terminal. Each individual TCTTE may be considered to be a "destination" for the purpose of this discussion. If a particular destination (TCTTE) is not ready to accept the current record on the queue, the queue necessarily "locks" until the destination can accept the record. Queue locks are only a problem when a queue is serving more than one destination. Then, if a queue locks, any new transaction on the queue or data records queued for existing tasks are not processed until the re~uired destination has accepted the current record. Since queue locks can adversely affect system performance, it is important that the user understand their cause and effect. Proper configuration of TCAM process queues and CICS Terminal control Tables, reduces to a minimum the occurrences and duration of queue locks. Because TCAM can read ahead from the terminals, it is possible for TCAM to present to CICS a new transaction record destined for a TCTTE that is already processing a task. Also, TCAM can present a data record for an existing task prior to that task issuing a READ request. In either case, CICS cannot "process" the record (as described above) until the TCTTE is ready to accept the new TIOA. Such input is called "unsolicited input". Three conditions can produce unsolicited input: (1) the CICS terminal for which the data is destined is OUT OF SERVICE, (2) the CICS terminal 145 for which the data is destined is in RECEIVE status, or (3) the CICS terminal for which the data is destined has an associated task that has not issued a READ and the period of time indicated by the NPDELAY specification has expired. In all cases, the action taken by the CICS/TCAM Interface is to place the input line OUT OF SERVICE and attach DFHTACP to process the error condition. The default action taken by DFHTACP (which can be altered by user-written DFHTEP) for conditions 1 and 2 is to discard the data and place the input line IN SERVICE. No default action is taken by DFHTACP for condition 3; therefore, the input line remains OUT OF SERVICE, thereby preventing CICS from reading any subsequent records from the input queue. To allow processing of input to continue, DFHTEP must take appropriate action. If the input line is placed IN SERVICE by DFHTEP, the CICS/TCAM Interface retries the operation; in this case, a count mechanism is recommended in DFHTEP to prevent a loop in the event the task never issues a READ. Alternative action, perhaps when a count limit is reached, might be to abend the task, dispose of the data, and place the line IN SERVICE. For further information concerning DFHTEP, see the section "Creating a Terminal Error Program". The problem of unsolicited input a separate TCAM input process queue However, as the number of terminals become prohibitive in terms of main can be eliminated entirely by having for each CICS terminal (TCTTE). increases, this solution may quickly storage requirGments. The user should analyze the type of traffic he anticipates over the queues. If he uses a 2770 Data Communication System or 2780 Data Transmission Terminal to read in volumes of cards, he should consider separate queues for these devices. The Asynchronous Transaction Processing (ATP) function in CICS should be seriously considered for processing batches of data to minimize the time between task READ requests. For conversational traffic with short-lived tasks, the sharing of queues is certainly feasible. The same TCAM output process queue can be specified for multiple input process queues. (See the discussion of the DFHTCT TYPE=LINE,OUTQ=symbolic name specification in the section "System Table Preparation".) The user need not be concerned with locking of the TCAM output process queue since TCAM requeues the data by final destination once it arrives over the output queue. It is possible for the TCAM output process queue to become congested due to lack of queuing space. In this case, CICS has a WRITE to the queue outstanding until TCAM accepts the data. TCAM DEVICE CONSIDERATIONS In the non-TCAM environment, the CICS Terminal Control program is responsible for polling and addressing terminals, code translation, transaction initiation, task and line synchronization, and the line control necessary to read from or write to a terminal. When TCAM is specified, Terminal Control relinquishes responsibility to the TCAM MCP for polling and addressing terminals, code translation, and line control. To take advantage of TCAM facilities, the user must accept the responsibility of coding in the MCP Message Handler functions such as code translation previously handled by the CICS Terminal Control program. For some terminal services, it is necessary for CICS to pass the user request on to the TCAM MCP Message Handler. A communication control byte in the TCAM work area has been established for this 146 purpose. It is passed to TCAM along with the eight-byte destination name field. Based on the communication byte, the user must execute the proper MCP Message Handler macro instructions to accomplish the necessary function. The terminal services parameters that do not set bits in the communications byte are WRITE, READ, WAIT, and SAVE. Bits in the communications byte are set for the 2260 parameters WRITEL and READL, the 2760 parameter OIU, and the DISCONNECT parameter. The CICS/TCAM Interface does not support the RESET parameter or the 3270 parameters READB and COPY. All messages to TeAM from CICS are prefixed with the standard CICS/TCAM communication byte. This byte is used to convey to TCAM request functions that cannot be issued within CICS (such as WRITEL to a 2260). Request functions maintained are DISCONNECT (X'08'), READL (X' 10'), and HRITEL (X' 20' ) • The following CICS screen control macro instructions are passed to the TCAM Message Control program (MCP): 1. 2. 3. DFHTC TYPE=WRITE,LINEADR=number DFHTC TYPE=WRITE,LINEADR=YES DFHTC TYPE= (WRITE,ERASE) These macro instructions are passed in the following format: f ,- . 8 Bytes I I J I J Start of message Destination ~---------Line addressing character specified) (if ~--------------Screen control (1 byte): X'AO', Set WRITE direct X'BO', LINEADR request X'EO', ERASE request L--_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Standard communication byte t ha t heads all messages to TCAM For a 2848 Control Unit Model 21 or 22, the communication byte is used to transmit READL and WRITEL requests to be executed by the TCAM MCP. 147 Messages passed to CICS from TCAM are of the following format: I '8 Bytes f I I ,~ .. tl--__ Message Destination Cursor (2 bytes) ~--------------Aid (1 byte) Messages passed from CICS to TCAM are of the following format: 18 Bytes .. I I I ,~ D estination I " I ,~ I H t I Message WCC (Write Control Character Command Escape character Standard CICS-to-TCAM communication byte All SOH% status messages input to CICS are passed to DFHTACP/DFHTEP. DFHTC TYPE=COPY and DFHTC TYPE=READB are not supported by the CICS/TCAM Interface. In addition to normal read/write functions, the ERASEAUP, CTLCHAR, UCTRAN, and COMPAT operands are also valid for the 3270. TCAM USER EXITS The three user exits applicable to the TCAM user are XATTACH, XTCMIN, and XTCMOUT. Whereas XATTACH is shared by other users, XTCMIN and XTCMOUT are applicable only to TCAM users and are used in place of the XINPUT and XOUTPUT exits used by others. SEe the section nCreating User Exits for CICS Management Programs" for further information concerning CICS user exits. This operand is used to generate linkage in the Terminal Control program TCAM module in TCP to a user-written exit routine. The linkage is generated at the point prior to issuing a Task Control ATTACH for a transaction identification received in response to polling. In the CICS/TCAM Interface this information is received over the TCAM input process queue. 148 This operand is used to generate linkage in the Terminal Control program TCAM module to a user-written exit routine. The linkage is generated at the point following the completion of any input event. If specified, the linkage is executed after the individual TCTTE is located, just before CICS checks to see if a task is attached to 'the TCTTE. At this time the TIOA contains the 12-byte storage accounting field and the work area from TCAM. The work area contains an eight-byte source terminal identfication header and the work unit (user data) • TIOADBA points to the user data area. The user has two options in returning from the user exit. If the user returns with a displacement of four bytes (an Assembler B 4(14) instruction), CICS removes the eight-byte source terminal identification field. Upon completion, the TIOA contains the 12-byte CICS storage accounting field and the work unit. (See Figure 14.) If the user returns from the exit with a zero displacement (an Assembler B 0(14) instruction), CICS does not alter the data in the TIOA. It is then the user's responsibility to handle the TCAM header. For a discussion of TCAM work areas and work units, refer to the section IIDefining the Application Program Work Area" in the Q.2:LliIT ~!l£ Q~Y1 1~AM ££Qgf~mmer~§ Guigg (GC30-2024). This operand is used to generate linkage in the Terminal Control program TCAM module to a user-written exit routine. The linkage is generated for output events at the point prior to placing data on the TCAM output process queue. The user has two options in returning from the exit. If the user returns from the exit with an Assembler B 4(14) instruction, CICS inserts in the TIOA, between the 12-byte CICS storage accounting field and the work unit, a TCAM header consisting of an eight-byte destination field and a one-byte communication control character required for TCAM. If the user returns from the exit with an Assembler B 0(14) instruction, CICS bypasses this insertion routine. It is then the user's responsibility to ensure that the TCAM header is properly formatted. Figure 14 shows the composition of the TCAM Work Area and the CICS Terminal Input/Output Area (TIOA) at the various stages of operation. On input, it shows the information available from the TCAM input process queue, the TIOA after input event completion, and the TIOA as it is passed to the user task after CICS has edited out the origin field. On output, it shows the TIOA (after CICS has edited in the destination field) in the format in which it is placed on the TCAM output process queue. The TCAM origin field contains the source terminal identification fteld. Since CICS uses four-byte Terminal ID's, the name is left-justified and the field is padded to the right with four blanks. ]gig: The TCAM destination field contains the destination identification for TCAM to properly route the data. If the user specifies the output user exit and returns from the exit with a zero displacement, CICS does not alter the TIOA work area. The user must provide the data length at TIOATDL and must prepare the work area for TCAM, including the eight-byte destination field and the communication control byte. 149 User Transaction Data TCAM WORK AREA from the input process queue Start \ of Work \ Area \ Start of Wor~ Unit End\of Work \\ Area \ \ \ \ \ \ \ \ \ TIOA after Input Event Completion: User Transaction Data CRQli]) I / I I I I I I I I / I I TIOA after CICS editing User Transaction Data / / / TIOA before output Event Completion after CICS insertion routine: \ \ \ User Transaction Data TIOA Start of Work Area Commu ni ca t ion Control Byte t End of Work Area The Work Area is placed on the TCAM output process queue Figure 14. Stages of the TCAM work area and CICS terminal input/output area (TIOA) CICS/TCAM STARTUP The TCAM MCP must be in operation prior to completing CICS system initialization. When the user brings up CICS with the CICS/TCAM Interface,CICS checks for the presence of a TCAM partition/region and issues the operator message: DFH1500 - CICS CHECKING FOR TCAM MCP If CICS discovers the MCP is not operational, the following messages are issued: DFH1520 - TCAM MCP IS NOT CURRENTLY AVAILABLE DFH1520 - REPLY RETRY OR CANCEL OR CONTINUE The operator must then respond: RETRY when the TCAM partition/region becomes active; or CANCEL to terminate CICS; or CONTINUE to continue initialization of CICS in the absence of the TCAM partitionl region. 150 If the operator responds CONTINUE, all DD cards that reference a TCAM queue must have been previously removed from the startup deck to avoid an abnormal termination of CICS. The CONTINUE response is applicable to a mixed BTAM/TCAM mode of operation when TCAM lines are not being used during execution of CICS. CICS/TCAM ABEND/RESTART If the TCAM Message Control program (MCP) terminates abnormally, any TCAM application programs currently active are automatically terminated abnormally, providing there is at least one open line group in the MCP. The CICS application program is no exception. For further information, see the discussion concerning "Coordinating MCP and Application Program Restarts" in the Q~~Il ~nQ Q~~Y1 1£!tl R£Qg£~~m~f~§ guide (GC30-2024). CICS does not provide RESTART capability. CICS/TCAM TERMINATION CICS is terminated in the normal manner. No modifications to termination procedures are required to support the CICS/TCAM Interface. If both CICS and TCAM are being terminated, CICS ahould be terminated first to avoid an abnormal termination of CICS. 151 Administration of a real-time data base/data communications (DB/DC) system involves considerations not ordinarily applicable to the traditional batch processing environment. These real-time DB/DC considerations include: 1. 2. 3. 4. 5. 6. Multiple application environment, often involving common or related data bases Managing data centrally on behalf of all applications Transactions arriving on a random nonscheduled basis for asynchronous (concurrent) processing upon arrival Transaction processing sometimes of long duration (for example, continuous 24-hour operation) Communication across multiple time zones (sometimes involving foreign as well as domestic interstate communication) Interface with multiple vendors of data processing services and equipment It is the responsibility of the system administrator to deal creatively with these new dimensions and complexities in data processing, seeing to it that the system is "tuned" for optimum performance and service. The dynamics of the database/data communication (DB/DC) environment make it necessary to be able to change system control parameters. certain of the parameters are changeable, if allowed by the system administrator or by the supervisor and terminal operators. Those facilities and the considerations for invoking them are described in the 1~£illinal QE~~~to£~2 Guig~ (SH20-1044). The primary system control is provided through the master terminal. The master terminal function is a logical rather than a physical consideration. This function can be invoked from any terminal that the system administrator allows, but is intended for use by a master terminal operator. In addition to the administrative terminal facilities described i.n the Ter!!!in~l Q~~ato£~2 Guidg, the master terminal may alter other system parameters that control the performance of the system. These control parameters are to be changed in the day-to-day operation of the system to effect the desired performance. They can also be changed in the process of tuning the system to obtain optimum performance under differing conditions. The terminal administration facilities are described in the Terminal The system administration functions intended-for---exclusive use from a master terminal are described below. QE§rato~~§ Q~igg. MASTER TERMINAL The Master Terminal program is a conversational program that leads the user through each transaction if sufficient information to perform the requested service was not entered in the original data entry. The services provided by the Master Terminal program allow the master terminal operator to: 152 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. Inquire about or change the partition exit time interval value. Inquire about or change the runaway task interval value. Inquire about or change the stall detection interval value. Inquire about or change the storage cushion size. Inquire about or change the maximum number of tasks value. Inquire about or change the maximum number of batch tasks value. Inquire about or change the maximum number of ATP tasks value. Inquire about or change the negative poll delay for a terminal. Inquire about or change the trigger level or a transient data intrapartition data set. Turn the CICS Trace function on or off. Inquire about or change the status of a single terminal. Change the status of a list of terminals. Change the status of a class of terminals. Change the status of all the terminals in the system. Inquire about or change the status of a line. Inquire about or change the status of a control unit. Inquire about or change the status of one or more data base data sets. Open one or more data base data sets. Open one or more transient data extrapartition data sets. Open the dump data set. Close one or more data base data sets. Close one or more transient data extra partition data sets. Close the dump data set. Switch the dump data set to the alternate dump data set. Inquire about the status of a program. Terminate a task. Terminate CICS. The partition/region exit time interval is the maximum interval of time that CICS will release control to the operating system in the event there are no transactions ready to resume processing. This binary time interval can be any three-to-ten-digit decimal value in the range from 100 to 27962020 milliseconds. A typical range of operation might be 100 to 2000 milliseconds. Any task given control through the Task Control program returns control to Task Control within a user-defined interval of time. Tasks not meeting this time requirement are considered to be in a runaway (logical loop) state and are deleted from the system. This binary time interval can be any three-to-ten-digit decimal value that is not less than the partition/region exit time interval and not greater than 27962020 milliseconds. A typical runaway task time interval might be 5000 milliseconds. If the runaway task time interval is set to zero, the feature is made inoperative. If CICS remains in an overload condition for the duration of the stall time interval, it is assumed that a system stall exists and corrective action is initiated. This binary time interval can be any three-to-five-digit decimal value that is not less than the partition/region exit time interval and not greater than 32767 milliseconds. A typical stall time interval might be 20000 milliseconds. '---._- 153 The system storage cushion is used by CICS to minimize system overload conditions. The cushion size does not actually change until the existing cushion is released. When the cushion is then regained, the cushion is of the size indicated by the new value. If a cushion size change is requested and the existing cushion is not released, the cushion size remains unchanged. The cushion size can be any two-to-five-digit decimal value (representing number of bytes) in the range from 20 to 65535. The negative poll delay function allows the user of CICS to delay the polling of BTAM devices on a line when negative responses are detected. This facility allows some control over the CPU overhead required to service negative poll interrupts. The request must be made in milliseconds and has a range from 0 to 20000. Once a terminal on that line enters into a conversational-mode transaction, that terminal receives a full poll until the transaction is completed. CICS limits the number of tasks that can be in the system at any one time to the number indicated by this user-defined value. This value can be changed dynamically in the range from 1 to 999. In the CICS/DOS-ENTRY system, the maximum number of tasks cannot be changed dynamically since the Rollout facility is initialized at a specified number during system initialization and cannot change unless CICS is reinitialized. The consecutive dispatch limit is valid only in the CICS/DOS-ENTRY system. When a transaction has performed the number of input/output operations (other than terminal input/output) specified by the consecutive dispatch limit, a task switch is initiated by CICS. The consecutive dispatch limit can be any value between 1 and 999. If a Transient Data intrapartition data set is marked for automatic task initiation, CICS automatically initiates the task when the specified number of requests for output operations (indicated by the trigger level for that destination) have been issued for that destination. The trigger level can be any value between 0 and 32767. If the CICS trace function is not generated as part of the nucleus, the trace function cannot be turned on. If the CICS function is generated as part of the CICS nucleus, turning it not remove it from the system; the trace function is still in storage, but is not executed. CICS trace off does main The status of data base data sets reflects one or more of the following: 154 1. 2. 3. 4. Read Update Add Exclusive control Optionally, the user can define two dump data sets (DFHDMPA and DPHDMPB), alternating between them during real-time execution of CICS. If there are two dump data sets, a 'switch' request closes the dump data set that is currently open and opens the other dump data set. This allows the user to print the CICS formatted dumps on the first dump data set without having to terminate CICS. The status of a program is comprised of the following: 1. 2. 3. 4. 5. 6. The language in which the program was written The size of the program in bytes Whether or not the program is permanently resident in main st~rage Whether or not the program is currently in main storage The number of times the program has been used The number of transactions that are currently using the program The optional CICS dynamic open/close facility allows the user to dynamically open/close his data sets as often as desirEd during the real-time execution of CICS. For example, this makes it possible for the user to defer the opening of data sets at System Initialization and open/close them later through the master terminal as they are needed. The dynamic open/close capability is applicable to File Management (data base data sets), Dump Management (dump data sets), and Transient Data Management (extrapartition data sets). Those CICS/DOS extrapartition sequential disk data sets that are to be closed and re-opened by the dynamic OPEN/CLOSE function of the Master Terminal Program must be defined as nonresident or records may be lost. The only time a task is not terminated upon request is when the requested task is currently reading from or writing to a terminal. CICS can be terminated from the master terminal by entering the transaction identification: CSMT The system responds: WHAT SERVICE IS REQUESTED? The master terminal operator should enter: SHUTDOWN 155 The system will respond: IS SHUTDOWN TO BE IMMEDIATE? The operator can respond with one of the following: NO NO, DUMP YES YES,DUMP If the system is to be terminated without regard to the existence of any active transactions (tasks), the operator should enter 'YES'. If the operator wishes to wait until there are no active transactions in the system, he should respond 'NO'. ]Ql§: If the user of the CICS/DOS-STANDARD system requests immediate termination of CICS while active transactions are communicating with terminals, unpredictable results could occur; that is, active terminals could receive input/output data from other active terminals within CICS. If the master terminal operator wishes to receive a main storage dump upon completion of the termination process, he should respond either 'YES,DUMP' or 'NO,DUMP'. If immediate termination is not requested, if Asynchronous Transaction Processing (ATP) is being used, and if there are batches currently in a HOLD status, the operator must respond: CATP STOP to complete the quiescing process. When termination is initiated, the following message is displayed on the system console and on the master terminal: DFH1701 - CICS IS BEING TERMINATED When termination is complete, the following message is displayed on the system console: DFH1702 - NORMAL TERMINATION COMPLETE If a dump is requested, the following message is displayed on the system console when termination is complete: DFH1791 - ABNORMAL TERMINATION COMPLETE DATE AND TIME OF DAY CONTROL In the course of normal operation, CICS maintains the current date and time of day within the Common System Area (CSA). The current (Julian) date of the form YYDDD is maintained in packed decimal representation at CSAJYDP, where YY is years and DDD is days. The current time of day is maintained in three formats: (1) in packed decimal at CSATODP of the form HHMMSSS, where HH is hours, MM is minutes, and SSS is seconds to tenths of a second, (2) in binary decimal at CSACTODB to hundredths of a second, and (3) in binary decimal timer units at CSATADJT to 300ths of a second. The current date is initially set by the CICS system Initialization program to agree with the date maintained by the operating ~ystem. The time of day values are updated during task dispatching to reflect the time of day maintained by the 156 operating system. The accuracy of these values depends upon the task mix and frequency of task switching occurrences. Since the time of day maintained by the operating system can be changed either by the operating system (for example, OS resetting the clock to zero at midnight) or by the console operator, CICS must recognize the situation where a "negative" change in the time of day has occurred, and must adjust expiration times maintained by CICS accordingly. If the optional time adjustment feature of CICS Time Management is not included in CICS, any change to the operating system time o~ day involving midnight is represented by CICS as a value larger than the previous value (for example, 1:00 a.m. is represented as 2500 hours); the date remains unchanged. If the optional time adjustment feature is included in CICS (by including the ICPTIME=YES operand in the DFHSG PROGRAM=ICP specification), and if either the time-ordered task synchronization feature or automatic task initiation feature of CICS Time Management is also included, any change to the operating system time of day is automatically reflected in the expiration times maintained by CICS; the date maintained by CICS is reset to agree with the data maintained by the operating system. In the case of CICS/OS, when the operating system time of day is set to zero at midnight (and the time adjustment feature has been included in CICS), CICS/OS adjusts the expiration times of day it maintains, changes the date, and then resets its time of day to zero. In the case of both CICS/OS and CICS/DOS, when the operating system time of day is changed by the console operator to a value less than the previous value, CICS adjusts the expiration times it maintains to reflect the negative value and then resets its date and time of day to those values maintained by the operating system. The optional time adjustment feature thus makes it possible for CICS to be operated on a continuous round-the-clock basis. The optional time adjustment feature is included in CICS by generating the Time Adjustment program (DFHTAJP) as part of the Control System Operational group (CSO). The user must provide a corresponding entry in the Processing Program Table (PPT) and the appropriate Transaction Identification (CSTA) as an entry in the Program Control Table (PCT) referencing DFHTAJP. When a negative change in the time of day maintained by the operating system is detected by CICS, transaction CSTA is automatically initiated. A message is then sent to the console operator informing him that the CICS time of day has been changed to reflect the change in the time of day maintained by the operating system. CICS does not recognize a change to just the date field. However, if transaction CSTA is initialized after the date maintained by the operating system has been changed, the date maintained by CICS is updated accordingly. SYSTEM STATISTICS Statistics maintained by the various CICS management programs can be displayed during the day in part or in their entirety on the request of any terminal operator whose security code allows the request of such information. Statistics are transmitted to the Transient Data destination CSSL as variable-length, unblocked records (maximum block size equal to 136) when the system is normally terminated or when requested by the terminal 157 operator. When requested by a terminal operator, an alternate destination may be specified. To request all system statistics, the following transaction is entered by the terminal operator: CSTT AOR destid To request selected statistics, the following transaction is entered by the terminal operator: CSTT SOR destid label,label,label,DONE The 'destid' is used to specify the four-character destination identification to which statistics are to be sent. If this field is blank (consisting of six blank characters between "SOR" and "label"), CSSL is the default destination. The 'label' corresponds to any of the following labels which request a particular set of statistics. TERM PROG FILE TASK STaR DUMP TRAN TEMP Terminal statistics Program statistics File statistics Task statistics Storage statistics Dump statistics Transient data statistics Temporary storage statistics The optional CICS Dynamic Open/Close facility allows the user to dynamically open/close his data sets as often as desired during the real-time execution of CICS. This makes it possible for the user to defer the opening of data sets during system initialization and open/close them later as they are needed. The dynamic open/close capability is applicable to File Management (data base data sets), Dump Management (dump data sets), and Transient Data Management (extrapartition data sets) and may be invoked via the Master Terminal program or through the use of the DFHOC macro instruction in an Assembler language application program. For a discussion of open/close via the Master Terminal program, see the section "Master Terminal" in this publication. The Open/Close macro instruction (DFHOC) is used to request any of the following services: 1. 2. 3. Noig~ Open, close, or switch dump data sets. Open or close data base data sets. Open or close transient data extra partition data sets. The DFHOC macro instruction is intended for use by the system programmer as a means of system control; it should not be used by the application programmer to open/close his data sets , as improper use of this macro instruction can cause serious degradation of system performance. The following operands can be included in the DFHOC macro instruction: 158 DFHOC TYPE=OPEN, * * * * * DA~ASE~=TRANSDATA,DATABASE,DUMP, lIS~ADR=(register), (symbolic register),YES, SYMEADR=symbclic address, DSE~ID= (name, (xx), ••• ), CHECK=symtolic address DFHOC TYPE=CLOSE, * BA~ASET=TRANSDATA,D~TAEASE,DUMP, * * * LIS'IADR= (register) , (symbolic register), YES, SYMEADR=symbclic address, DSETID= (name, ••• ) , CHECK=symtclic address * BFHOC TYPE=SWITCH, DA'IASET=DUMP OPEN DA~A SE'IS * (CPEN) The programmer can open a data set or series of data sets by issuing the DFHOC TYPE=OPEN, * * * * * DATASE~=TRANSDATA,DATABASE,DUMP, LIS~ADR= (register) , (symbolic register), YES, SYMEADR=symbelic address, DSE'IID= (name, (xx) , ••• ) , CHECK=symbolic address macro instruction. He must provide the parameters needed by specifying them in the macre instruction or, in the case of LISTADR, by placing the address of the parameter list (built by the user) in the TCA at TCAOCLA and specifying LISTADR=YES. ]Q1~: Parameters and/or parameter lists built in conjunction with this macro instructien should be built in the TWA or in storage acquired by th€ crcs Storage Contrel macro instruction as data in a program area could be lost. A discussion ef the operands that can be included in the DPHOC TYFE=OPEN macro instructicn follows. DATASET: Specifies whether the request is for a transient data extrapartition data set (TRANSDATA), a data base data set (DATABASE), cr a dump data set (DUMP). LISTADR: Not applicable if DATASET=DUMP is specified. Specifies the register or symbolic register name containing .the address of the open/close parameter list built by the user. If LISTADR=YES is specified, this address can be placed in the TCA at TCAOCLA. If the LISTADR operand and SYMBADE operand are omitted, execution of the DPHOC macrc instruction causes the list to be built for the user starting with the first byte of the TWA. In this case, it is the user's responsibility to make sure that the required space is available in the TWA. The space can be calculated using the formula: Space = (n x 12) + 4 where Un" is the decimal number of twelve-byte entries in the open/close parameter list and the "4" represents four bytes of hexadecimal P's to signify the end of the parameter list. 159 The symbolic storage definition (DFHOCLDS) of a parameter list entry is provided by CICS. The format of a twelve-byte entry in the open/close parameter list is: WORD 1: Four-byte Destination 10. WORD 2: Four bytes of the form bbxx where bb is two bytes of blanks and xx is a two-byte suffix of the data set central block created by the DCT assembly. The contents of this field are ignored when using resident control blocks. WORD 3: Error byte plus three-byte address of DCT entry (this informatien is supplied by CICS). WORDS 1 and 2: Data set name (left justified, padded with blanks). WORD 3: Error byte plus three-byte address of FCT entry (after cempletien) • In CICS/OS, the user can optionally specify, in WORD 2 of a TRANSDATA entry, the parameter list address pointing to a storage area. This storage area contains information to be placed into a dummy DCB before opening it. If an address is placed in this field, the first byte must be set to a hexadecimal FF. The symbolic storage definition (DFHOCODS) of this parameter list is ~rovid€d by CICS. The format of the parameter list is as fellows: Byte 1: Byte 2: Byte 3: Byte 4: Bytes 5,6: Bytes 7,8: Bytes 9-16: Open Options byte BUFNO byte RICFM byte EEROPT byte LRECL BLKSIZE DENAME The first eight bytes must contain the correct hexadecimal codes for the desired parameters, since the 16 bytes of the open/close parameter list are moved into the DCB. SYMEAtR: Not applicable if EATASET=DUMP is specified, this operand indicates the syncelic address of an open/close parameter list built by the user. If the SYMEADR and LISTADR operftnds are omitted, execution of the DFHOC maCIO instruction causes the parameter list to be built for the user starting with the first byte of the TWA. For a discussion of the parameter list, see the discussion of the LISTADR operand in this section. DSETID: Not applicable if DA!ASET=DUMP is coded or if the LISTADR or SYMBADR operand is used, this operand specifies the data set names or destination identifications to be used in constructing a parameter list. If a suffix is specified, it must ce separated from the name or destinatien identificatien by a comma and must be enclosed in parenthesis. If DA!ASE!=DA!ABASE is coded, up to 255 data set names can be specified with a single use of the DSETID operand. If DATASET=TRANSDATA is coded, up to 255 destination identifications can be specifed with a single use of the DSETID operand. If TYFE=OPEN is coded and if the destinations are nonresident, "xx", a two-character suffix of the data set contrel block (DCB for CICS/OS, DTF for CICS/DOS) must be provided 160 with each destination identification; if the destination is resident, the "xx" suffix is ignored. In CICSjOS, if "xx" consists of more than two characters, it is assumed to be the syrebc1ic address of a list of options and parameters. 160.1 to be moved into the DCB. For the format of this list, see the discussion of the LISTADR operand in this section. CHECK: Specifies the symbolic address of a user-written routine to which control is passed if any error is detected during the OPEN operation. The user-written routine is given control whenever TCAOCTR in the TCA contains a nonzero return code. It is the responsibility of the user to examine the return code in the TCA and, if necessary, examine the individual error codes in the list that was built either by the user or by the expansion of the DFHOC macro instruction. The error code appears in the first byte of the third word of each entry in the parameter list. Upon return from the Dynamic Open/Close program, TCAOCTR may contain one of the hexad~cimal codes: 00 - No error FF - Invalid request or, if TCAOCTR contains neither of these codes, it will contain one or . more of the following hexadecimal codes: 80 40 20 10 - Open error Close error No space available for OPEN Invalid control block name While performing the requested service on the list of data sets, the individual error bytes in the list entry are filled with a hexadecimal 00 or with the proper error code each time an error is encountered. If more than one error is encountered while processing the parameter list, TCAOCTR reflects all the errors and may show a bit configuration different from those shown above. For example, if there are six data sets to be opened, if four are successfully opened, if one has an invalid control block identification, and if one has an open error, the TCAOCTR field contains a hexadecimal 90. When there is not enough main storage available to open any data sets, TCAOCTR contains a hexadecimal 20, and all the entries contain a fullword (four bytes) of zeros in the third word. CLOSE DATA SETS (CLOSE) The programmer can close a data set or series of data sets by issuing the DFHOC TYPE=CLOSE, DATASET=TRANSDATA,DATABASE,DUMP, LISTADR=(register), (symbolic register),YES, SYMBADR=symbolic address, DSETID= (name, ••• ) , CHECK=symbolic address * * ** * macro instruction. The DATASET, LISTADR, SYMBADR, and CHECK operands have the same significance as for the DFHOC TYPE=OPEN macro instruction. The DESTID operand is used as follows. DSETID: Specifies the names of the data sets to be closed. No suffix is required. Up to 255 data set names can be specified with a single use of this operand. 161 SWITCH DUMP DATA SETS (SWITCH) The programmer can switch from the dump data set currently being used to the alternate dump data set by issuing the DFHOC TYPE=SWITCH, DATASET=DUMP macro instruction. This macro instruction causes the current dump data set, if open, to be closed, and the alternate dump data set to be opened. A TYPE=CLOSE,DATASET=DUMP macro instruction does not cause a switch but only closes the current dump data set. During the course of CICS execution, certain exceptional conditions can occur of which system administration should be aware. These conditions cause control system messages to be sent to appropriate destinations through the CICS Transient Data Control facility. The user interested in this information should direct it to the desired queue or log by defining the appropriate entries in the Destination Control Table (DCT). Although these control system messages may be routed to an extrapartition output log, it is strongly recommended that the user route them to a terminal (preferably hard copy) so that appropriate administrative action can be taken. Control system messages that originate in the Terminal Abnormal Condition program (DFHTACP) are time stamped; that is, the time that the exceptional condition occurred is printed as part of the message. The time is expressed in the form "hhmmsss", where "hh" represents hours, "mm" represents minutes, and "sss" represents seconds to tenths of a second. Control system messages that originate in the Abnormal Condition program (DFHACP) are not time stamped. The system actions described in connection with the following messages are the default actions provided by DFHTACP. These system actions are subject to modification by the user-written Terminal Error program (DFHTEP). In the CICS/DOS-ENTRY system, it is not always possible to determine the transaction identification. Therefore, in the following message, the program identification (PROG yyyyyyyy) may be substituted for the transaction identification in the case of the CICS/DOS-ENTRY system. 1. TCT SEARCH ERROR ON LINE W/TERM xxxx, hhmmsss TCT SEARCH ERROR ON LINE W/TERM xxxx, RELATIVE LINE zz, hhmmsss ~~ElanatiQnl BTAM input only. An invalid terminal address was received for a read operation on a line defined by terminal xxxx. If the line supports the TWX, relative line zz is also printed. ~yst§ID !£iiQn~ Terminal request for service is ignored and the data which was input is lost. The line associated with terminal xxxx is placed out of service on non-switched lines; the system continues polling other lines. On remote 2260 terminals, the control unit skip flag is turned on in the polling list and the line continues in service. 162 * E~ogr~mm~£ Action: Examine the Terminal Control !able to be sure there Is-ail-entry for every terminal on each line. Regenerate it to include a missing terminal. Bad transmission of data on remote 2260 terminals can cause this message to occur. 2. TRANSLATE ERROR AT TERM xxxx, TRANS yyyy, hhmmsss TRANSLATE ERROR ON LINE W/TERM xxxx, hhmmsss TRANSLATE ERROR ON LINE W/TERM xxxx, RELATIVE LINE zz, hhmmsss ~!El~natiQQ~ BTAM. Terminal type for Terminal Identification xxxx is not present in the Terminal Control Table, or the Terminal Control program was not generated to support the device type specified in the Terminal Control Table. ~ystgill !£tio~~ Request for service is ignored and the data is lost. The system continues polling. Terminal xxxx is put out of service. EfQg~Q£ ActiQn~ Regenerate the Terminal Control Table to provide the correct terminal type, or regenerate the Terminal Control program to support the required terminal type. 3. POLLING LIST ERROR ON LINE W/TERM xxxx, hhmmsss ]~ElanatiQn~ The address for a terminal identified as xxxx in the Terminal Control Table does not correspond to the polling list. ~ystQill !£tiQn~ The system continues processing. is put out of service. Terminal xxxx g£Qg£~me£ Action~ Examine the Terminal Control Table and polling list for discrepancies. If the assemblies of each are correct, check to see if the program has inadvertently affected either the table or the list. Correct the error and either regenerate the table or resubmit the program. 4. OUTPUT EVENT REJECTED AT TERM xxxx, TRANS yyyy, RETURN CODE zz, hhmmsss BTAM output only. The return code zz was generated by BTAM when the writ~ was attempted. E!£1~nation~ ~ystgill !£iiQn: The line (defined by terminal xxxx) is placed out of service, and the transaction yyyy is abended. g£Qg££~~£ A£tion: Take appropriate action as determined from the BTAM return code. 5. INPUT EVENT hhmmsss INPUT EVENT INPUT EVENT RETURN CODE REJECTED AT TERM xxxx, TRANS yyyy, RETURN CODE zz, REJECTED ON LINE W/TERM xxx x RETURN CODE zz, hhmmsss REJECTED ON LINE W/TERM xxxx, RELATIVE LINE aa, zz, hhmmsss 163 ]~E1~~1iQlll BTAM input only. Return code zz was generated by BTAM when the READ was attempted. ~ystgID !£!iQn~ The line defined by terminal xxxx and relative line aa (for switched lines) is placed out of service. The transaction yyyy is abended. RIogr~NIDgf !£tiolll Take appropriate action as determined from the BTAM return code. 6. TCT CODING OR TCP PROGRAM ERROR AT TERM xxxx, TRANS yyyy, hhmmsss TCT CODING OR TCP PROGRAM ERROR ON LINE W/TERM xxxx, hhmmsss TCT CODING OR TCP PROGRAM ERROR ON LINE W/TERM xxxx, RELATIVE LINE aa, hhmmsss ~~ElallatiQlll Generated as a result of a BTAM return code of 04 (BUSY), OC (invalid OPTYPE), or 10 (AUTOPOLL or program polling error) • RfQg£~mm~f Actiolll To further analyze the BTAM READ/WRITE return code, see the publication OS/36Q ~asi£ %g1§£Qill~ni£~!ion§ !££g§§ ~ethoQ, !§£§iQB l (GC30-2004). 7. OPEN FAILURE, USE LOPEN TO RECOVER ON LINE W/TERM xxxx, hhmmsss OPEN FAILURE, USE LOPEN TO RECOVER ON LINE W/TERM xxxx, RELATIVE LINE aa, hhmmsss ]~£lanatiQnl Generated as a result of BTAM return code 14 (line error during OPEN) • ~l§te!!! !£tionl None. RfQgf~mmef !£!iQn~ Use the Master Terminal facility to place the line in service. 8. MISSING DD CARD ON LINE W/TERM xxxx, RELATIVE LINE aa, hhmmsss ]xplan~tionl Generated as a result of BTAM return code 08 (invalid RLN). This error most commonly occurs as a result of omitting one of the DD cards of a switched-line pool. R~ogr~!!!mef !£tion~ Ensure that all DD cards for a switchedline Fool are present in the job stream used to bring up CICS. 9. 164 SHOULD NOT OCCUR RETURN CODE zz AT TERM xxxx, TRANS yyyy, hhmmsss SHOULD NOT OCCUR RETURN CODE zz ON LINE W/TERM xxxx, hhmmsss SHOULD NOT OCCUR RETURN CODE zz ON LINE W/TERM xxxx, RELATIVE LINE aa, hhmmsss ~!planatlQn~ Generated as a result of BTAM return codes 18, 1C, or 20. These return codes are undefined for CICS and indicate that the DCB probably contains dynamic buffering operands. RI~~mme~ !£iion~ Ensure that no buffering operands exist in the DCB for the line involved. 10. BUFFERED DEVICE BUFFER EXCEEDED AT TERM xxxx, TRANS yyyy, hhmmsss ~!21~natiQn~ On a device with the buffer receive feature (for example, the 2740-2), the output message length exceeded the hardware buffer size. 2Y§ig~ !£!ion~ storage is freed The write request is aborted, the terminal write (if possible), and the task is abended. ~~ggra~N~~ !£tiQn~ Ensure that the data length plus the carrier control characters does not exceed the hardware buffer size. 11. OUTPUT LENGTH ZERO AT TERM xxxx, TRANS yyyy, hhmmsss ~!El~n~tiQn~ A write was requested on terminal xxxx by transaction yyyy, but the contents of the TIOATDL field was zero. ~Y§!gN !£!lQn~ storage is freed The write request is aborted, the terminal write (if possible), and the task is abended. Rrog££mm~£ !£~Qn~ Ensure that the transaction in error initializes the TIOATDL field of the TIOA. 12. NO OUTPUT AREA PROVIDED AT TERM xxxx, TRANS yyyy, hhmmsss ]!21~n£tiQ~ A write was requested on terminal xxxx by transaction yyyy; the TCTTEDA field was not initialized. ~ystgill Aciion: abended. The write request is aborted and the task is ~IQgrammg~ !£tiQn~ Ensure that the transaction in progress obtains necessary storage and initializes the TCTTEDA field, as necessary. 13. OUTPUT AREA EXCEEDED AT TERM xxxx, TRANS yyyy, hhmmsss ~!plan£tiQn~ The Terminal 1/0 Area (TIOA) was not large enough to contain both the data and carrier control characters. 165 ~Y§tem Ac!iQn~ storage is freed The write request is aborted, the terminal write (if possible), and the task is abended. R~Qg~mmg£ ActiQn~ Ensure that the transaction in error obtains TIOA's large enough to contain messages in addition to carrier control characters. 14. UNIT CHECK AT TERM xxxx, TRANS yyyy, hhmmsss UNIT CHECK ON LINE W/TERM xxxx, hhmrnsss UNIT CHECK ON LINE W/TERM xxxx, RELATIVE LINE zz, hhmmsss ~ZE!£ngtiQ~~ A unit check error occurred on the line defined by terminal xxxx, transaction yyyy, and relative line zz (as appropriate) . ~~§!§N~£1ion~ The line is placed out of servicp. on GAM or SAM lines and on BTAM I/O errors (with the exception of Intervention, Data Check, or Time out error conditions). Intervention on a switched line causes the task to be abended and the line to be logically disconnected. Intervention on a non-switched line with a dummy (unidentified) terminal causes the line to be placed out of service; with a real terminal, causes the terminal to be placed out of service and the transaction (task) to be abended. Data check with a dummy terminal causes the line to be placed out of service; with a real terminal, causes the terminal to be placed out of service and the transaction to be abended. Time out on a Read Text command causes a MESSAGE TOO LONG response to be sent to the terminal. Time out with a dummy terminal causes the line to be placed out of service; with a real terminal, causes the terminal to be placed out of service and the transaction to be abended. R~Qgra~N~£ ActiQn~ Examine the System Console Log message generated by BTAM for this error and have the unit error corrected. 15. UNIT UNIT UNIT LINE CHECK SHOULD NOT OCCUR AT TERM xxxx, TRANS yyyy, hhmmsss CHECK SHOULD NOT OCCUR ON LINE W/TERM xxxx, hhmmsss CHECK SHOULD NOT OCCUR ON LINE W/TERM xxxx, RELATIVE zz, hhmmsss ]z]1gnatiQn~ A unit check error (which is undefined by BTAM) occurred on the line defined by terminal xxxx, transaction yyyy, and relative line zz (as appropriate). ~Y§i~m A£tion~ The line is placed out of service on GAM or SAM lines and on BTAM I/O errors (with the exception of Intervention, Data Check, or Time Out error conditions). Intervention and the line non-switched the terminal (task) to be 166 on a switched line causes the task to be abended to be logically disconnected. Intervention on a line with a dummy (unidentified) terminal causes to be placed out of service and the transaction abended. Data check with a dummy terminal causes the line to be placed out of service; with a real terminal, causes the terminal to be placed out of service and the transaction to be abended. Time out on a Read Text command causes a MESSAGE TOO LONG response to be sent to the terminal. Time out with a dummy terminal causes the line to be placed out of service; with a real terminal, causes the terminal to be placed out of service and the transaction to be abended. g!Qgf~~~g£ Action~ Examine the System Console Log message generated by BTAM for this error and have the unit error corrected. 16. UNIT EXCEPTION AT TERM xxxx, TRANS yyyy, hhmmsss UNIT EXCEPTION ON LINE W/TERM xxxx, hhmmsss UNIT EXCEPTION ON LINE W/TERM xxxx, RELATIVE LINE zz, hhmmsss ~!£1~natiQQ~ A unit exception error occurred on the line defined by terminal xxxx, transaction yyyy, and relative line zz (as appropriate). This error was posted 41 by BTAM. ~yst~~£tiQn~ with a switched line, the transaction is abended and the line is logically disconnected. With a dummy terminal, the line is placed out of service; with a real terminal, the terminal is placed out of service and the transaction is abended. R!Qg~~ill~£ ~£tiQn~ Examine the System Console Log message generated by BTAM for this error and have the unit error corrected. 17. UNIT UNIT UNIT LINE EXCEPTION SHOULD NOT OCCUR AT TERM xxxx, TRANS yyyy, hhmmsss EXCEPTION SHOULD NOT OCCUR ON LINE W/TERM xxxx, hhmmsss EXCEPTION SHOULD NOT OCCUR ON LINE W/TERM xxxx, RELATIVE zz, hhmmsss ~KE1~ti~ A unit exception errror (undefined by BTAM) occurred on the line defined by terminal xxxx, transaction yyyy, and relative line zz (as appropriate). ~y§~gm-A£tion~ With a switched line, the transaction is abended and the line is logically disconnected. With a dummy terminal, the line is placed out of service; with a real terminal, the terminal is placed out of service and the transaction is abended. g!Qg£~mN~E ~£!ion~ Examine the system Console Log message generated by BTAM for this error and have the unit error corrected. 18. NEGATIVE RESPONSE AT TERM xxxx, TRANS yyyy, hhmmsss NEGATIVE RESPONSE ON LINE W/TERM xxxx, hhmmsss NEGATIVE RESPONSE ON LINE W/TERM xxxx, RELATIVE LINE zz, hhmmsss EXE1~atiQ~ An invalid negative response occurred on the line defined by terminal xxxx, transaction yyyy, and relative line zz (as appropriate). 167 ~ystg.!!! !£tion1. The terminal is placed out of service and the transaction is abended. R~Qg£~'!!!~~ !£tion1. Examine the System Console Log message generated by BTAM for this error and have the unit error corrected. 19. UNDETERMINED UNIT ERROR AT TERM xxxx, TRANS yyyy, hhmmsss UNDETERMINED UNIT ERROR ON LINE Vi/TERM xxxx, hhmmsss UNDETERMINED UNIT ERROR ON LINE Vi/TERM xxxx, RELATIVE LINE zz, hhmmsss Qg§tinatig1!1. CSMT ]~Bl~D~tigll1. An I/O error (which was not unit check, unit exception, or negative response) occurred on the line defined by terminal xxxx, transacton yyyy, and relative line zz (as appropriate). ~yst~.!!! !£ii2n1. The line associated with terminal xxxx is placed out of service. R~Qg££ill.!!!g~ Ac1iQn1. Examine the System Console Log message generated by BTAM for this error and have the unit error corrected. 20. SECURITY VIOLATION HAS BEEN DETECTED TERM ID=xxxx, TRANS ID=xxxx, OPERATOR NAME=xxxxxxxx ]~plaDatign1. The operator at terminal xxxx has requested a transaction whose security key does not match the corresponding security key for the operator who is signed on. ~Y§igill !£1 ion1. Continues polling cycle. R~oqr~.!!!g~ !£iiol!1. Determine whether the operator should be allowed to request the transaction. If so, correct the security key for the operator in the Sign-on Table (DFHSNT). 21. INTERCEPT REQUIRED AT TERM xxxx, TRANS yyyy, hhmmsss ]~l~D~~~Qn: The task associated with terminal xxxx, transaction yyyy, and relative line zz (as appropriate) was to have been abnormally terminated, but TPURGE=NO was specified in the corresponding entry of the Program Control Table (peT). ~ystgill !ctiQl!: R~Qg~me~ The terminal is placed out of service. ActiQg: Use the Master Terminal facility to intercept or terminate the task. 168 22. TRANSACTION xxxx ABEND xxxx AT xxxx ]~£l£B~tion~ The identified transaction attached to the identified terminal has been abnormally terminated. The ABEND code indicates the origin or cause, and may be originated by the user or by CICS. Following are the ABEND codes for abnormal terminations initiated by CICS. AACA Abnormal Condition Invalid error code passed to DFHACP in the TCA at location TCAPCABR. A complete system dump is provided to assist in problem determination. AICA Interval control A runaway task condition has been detected and the task is being abnormally terminated. The condition indicates a possible logical loop within the user's program. AKCA Task Control Another CICS task has requested Task Control to abnormally terminate this task as a result of actions initiated by: • Terminal Abnormal Condition program (DFHTACP); the appropriate message is found at destination CSMT. • Task Termination portion of the Master Terminal facility. The Asynchronous Transaction Control program (DFHATP) terminates asynchronous tasks when: • User requests deletion of a batch via CWTR delete option while CICS is actively processing that batch; DFHATP abnormally terminates the task and purges all remaining data from the queues. • An asynchronous task tries to read more data than is available; DFHATP abnormally terminates the task. \ ~ AKCD Task Control Invalid code in the dispatch control indicator field. The invalid code can be found in the TCA at symbolic location TCATCDC. Valid Codes: X'10' Not dispatchable (not applicable to CICS/DOS-ENTRY) X'20' Dispatchable X'40' wait on list of events X'SO' wait on single event AKCP Task Control A stall condition has been detected and this task is being abnormally terminated. This task carries a code indicating it is purgeable. 169 AKCR Task Control The type of request code is invalid. The invalid code can be located in the TCA at symbolic location TCATCTR. Valid Codes: X'01' X'02' X'04' X'OS' X'10' X'11' X'12' X' 14' X'20' X'40' X'SO' AKCS Task Control The request exceeds available Subpool 1 storage. CICS/DOS-ENTRY only. APCC Program Control An attempt was made to execute an ANS COBOL program but ANS COBOL support was not generated in Program control. APCI Program Control An attempt was made to execute a PL/I program but PLII support was not generated in Program Control. APCL Program Control There is insufficient main storage available for the requested program. APCP Program Control An error occurred on the read of a requested program from the library. APCR Program Control Task request for service is invalid. The invalid code can be located in the TCA at TCAPCTR. Valid Codes: X' 01' X'02' X'04' X'OS' X '1 0' X'40' X'60' X'90' LINK XCTL LOAD DELETE RETURN ABEND ABEND with DUMP RETURN from Task Control program APCT Program Control A task issued a request for a program which is not in the PPT. The invalid program ID is in the TCA at TCAPCPI. APIA Program Interrupt A program check has occurred during the subject task execution. The PSW at the time of interrupt is saved in the task's TCA. ASCR storage Control The request for service is invalid. Valid codes: X'20' X' 40' 110 Enqueue Dequeue Reserved Reserved Task Origination Reserved Reserved Reserved Priority Change Task Wait Task Termination Released Storage Release Storage X'SO' Acquire storage ASCT storage Control The request exceeds available Subpool 1 storage. CICS/DOS-ENTRY only. ATDI Transient Data The type of destination code is invalid. The invalid code can be located in the DCT at symbolic location TDDCTDT. Valid Codes: X'20' X'40' X'SO' ATDT Transient Data Indirect Extrapartition Intrapartition Request for service is invalid. The invalid code is in the TCA and can be located at TCATDTR. Valid codes; X'20' Forced end of volume on extrapartition data set. X'40' Output service on intrapartition. X'SO' Input service on intrapartition. DLDY DL/I Interface A DL/I CA~L was issued, but the DL/I Interface dummy program under CICS/OS was loaded at system initialization. DLIA DL/I Interface An irrecoverable error occurred during execution of the CICS-DL/I Interface program under CICS/OS. The DLIA code is returned to all transactions from which DL/I CALL's are subsequently issued. DLPA DL/I Interface A DL/I abend (or pseudo abend) occurred during transaction processing. The ABEND code is found in the TCA at TCADLECB. ~Y§ig~ !£tioll: In addition to the dump services requested by application programs, CICS also requests dumps for abnormal conditions and places specific dump codes in the dumps for ready identification. !ctiQll: code. 23. Analyze the error condition indicated by the abend INVALID COPY REQUEST AT TERM xxxx, TRANS yyy, hhmmsss ]zB1gnatiQll.i. a. The Terminal Control Table Terminal entry of the "from" device did not specify the COpy feature. b. The device address specified for the "from" device does not exist on the requested control unit. c. The length specified for the COpy request was not one. 171 §!§1~m Action~ The transaction is abended. R~Qg~amm~~-A£!ion~ Ensure that the application program is aware of the device configuration as necessary. 24. INVALID MSG BLOCK ON LINE W/TERM xxxx, hhmmsss ~~Elan~!iQll~ a. b. An unidentifiable message was received from a remote 3270 device. The message block did not correspond with known identification patterns. The type of data block received from a 3735 was incorrect for the mode of the active CICS transaction. For example an inquiry message block was received for a batch transaction or conversely. This will probably occur if the 3735 is disconnected during a transaction and, upon reconnection, the operator initiates a different mode of operation. §y§te~-A£!ioQ~ The terminal is placed out of service and the transaction is abended. g~QgI~illIDgI Action~ For condition (a), ensure that the hardware difficulty is corrected. For condition (b), ensure that the terminal operator understands the correct operating and recovery procedures for 3735 transactions. 25. INCMPLT MSG BLOCK ON LINE W/TERM xxxx, hhmmsss INCMPLT MSG BLOCK AT TERM xxxx, TRANS yyyy, hhmmsss ~~Ela~tiQn~ An incomplete message was received on term xxxx; that is, end of transmission was received prematurely or prior to end of text. §!§iem_!£tiQQ~ The terminal is placed out of service and the transaction is abended. g&Qg~mm§~ Action~ Ensure that the hardware difficulty is corrected. 26. INTERV ON PRINTER ON LINE W/TERM xxxx, hhmmsss INTERV ON PRINTER AT TERM xxxx, TRANS yyyy, hhmmsss ~~£1~natiQ~ This message is sent to the 3270 Information Display System on a printer intervention situation: a. Normal out of paper condition, cover open, offline, etc. b. No printer present, but transaction request to start printer. c. Printer adapter feature not present. §I§t§m Action: No action is performed. gIQg~~I-A£tion: Ensure that the Terminal Control Table is properly defined and that the transaction requests proper printer operations. If the 3277 Display Station is plugged in the wrong position on the 3270 Information Display System, the operator may depress the CLEAR key to proceed. 172 21. INTERV REQUIRED ON LINE W/TERM xxxx, hhmmsss INTERV REQUIRED AT TERM xxxx, TRANS yyyy, hhmmsss This message occurs when an intervention situation arises on the 3210 Information Display System. ]ZE!gDgtiQn~ ~~QB~g~~~_Ac~ion~ 28. Correct the intervention situation. EBBOB STA!US MSG eeee RECEIVED CN LINE w/TERM xxxx, hhmmsss EBBOR STA!US MSG eeee RECEIVED AT TERM xxxx, TRANS yyyy, hhmmsss BTAM error status message "eeee" was received from a remote 3210 Infcrmation Display System cr from a 3135 Prcgrammable Buffered Terminal. For a remote 3210, an "intervention required" condition causes an INTERVENTION REQUIRED message in lieu of this message. ]~E.!gnE:ti.Q.D':' 2Y§!~~_Af!1Qn.:. The transaction is abended and the terminal is placed out of service; however, if operation check status is present and if the terminal is a 3210, the terminal is left in service. Analyze the error status to determine the proper course of acticn tc correct the unit erro~ or program error. ~fQgfsIDIDgf_Af!i.Q.D~ 29. UNSOLICITED INEUT CNLINE W/~ERM xxxx, hhmmsss Input has occurred on a control unit (general poll) for which the associated terminal is "out of service" or has a task that has not issued a DFHTC TYPE=READ macro instructicn. E~El~~tiQn: No action is performed by CICS. given to user-written DFHTEP. ~~steID ~~!1Qn: ~fQgfgIDIDg~ ~£!ion: Control is Code DFHTEP as dictated by envircnmental needs. 30. DESTINATIO~ dddd INVALID CNIINE W/TERM xxxx, hhmmsss DESTINATION addd INVALID AT TERM xxxx, TRANS yyyy, hhmmsss An application program has attempted to write to an invalid TCAM destination. ]~E.!~.D~tiQn: !f!iQn: request. ~~~ID Abend the transaction and abort the write EfQgf~ID~~~ !£!iQn: Ensure that application programs write to proper TCAM destinations. 113 31. INVALID RIAD REQUEST AT TERM xxxx, TRANS 111Y, hhmmsss ]Z12!s!H!1i£1! : a. A ~ransaction has requested a BEAD from a terminal that presently has a terminal status of RECEIVE. b. A transaction has issued a READ request to a 3135 terminal during batch transmission after receipt of the end-of-file (BOP) condi tion. ElsteID !£1i2n: Abort the READ request and abend the transaction. ~~Q~~g~~~ !£1ion: For condition (a), ensure that transactions de not issue DFHTC TYPE=READ macro instructions to terminals in RICEIVE status. For condition (b), ensure that the 3135 batch transacticn makes ~roper use of the EOF o~erand in the DFHTC macro instruction so that no reads are issued after the EOF condition has occ~rred. 32. INVALID WBI~E REQUEST AT TERM xxxx, TRANS Y1YY, hhmmsss ]Z12.!§:1!atjQn: a. A transaction has issued a WRITE to a terminal that presently has a terminal status of INPUT. b. A transaction has issued a WRITE to a 3135 during batch transmission prior to receipt of the 'EOF' condition. ~lsteID !£tion: transactien. Abort the WRITE request and abend the ~~Qg~§:mme~ !£!i2n: For condition (a), ensure that transactions do not issue WRITE requests to terminals in INPUT status. For condition (b), ensure that the 3735 batch transaction does not issue its first WRITE request b~fore receiving the EOF condition. 33. TIME OUT CNLINE W/TERM xxxx, hhmmsss TIME OUT AT TERM xxxx, TRANS YY11, hhmmsss ]~E12~~iQ1!: A 32-second timeout has occurred on a 7710 Audio Response Unit. §lsteID !£!ion: The 1110 terminal received an error message and is disccnnected, and the transaction abended. 34. DFHSF001 xxx 11YY1 ZZZ CSML The operator has signed off a terminal where: xxx YY11Y 114 = operator identification from Sign-on Table; = number of transactions processed; zzz = number of transaction 8rrors. ~ystg~ !£iion: CICS continues processing. The operator is no longer signed on the terminal. The message SIGN OFF IS COMPLETE is returned to the terminal. 175 The following destination identification entries are required and must be provided by the user in the DFHDCT TYPE=EXTRA, DFHDCT TYPE=INTRA, or DFHDCT TYPE=INDIRECT specification: 1. DESTID=CSMT 2. DESTID=CSTL 3. DESTID=CSSL 4. DESTID=CSML The Terminal Abnormal Condition program (DFHTACP) and Abnormal Condition program (DFHACP) write terminal error and abend messages, respectively, to this destination. DFHTACP writes terminal I/O error messages to this destination. statistics programs write data to this destination. Sign-off program outputs data to this destination. If the Transient Data Control program (DFHTDP) is not included in the generation of CICS, messages to these destinations are lost (ignored) • The following entries are required in the PCT and must be provided through the DFHPCT TYPE=ENTRY macro instruction. Minimum values for TWASIZE are indicated. l!Q1g: !RAl!.2.!~ RB OGRA l1 !J!ASIZ~ CAQP*** CATP*** CRDR*** CSAC CSFE** CSMT** CSOT** CSSF** CSSN** CSST** CSTA** CSTE CSTT CWTR*** 8888* 9999* DFHAQP DFHATP DFHRD1 DFHACP DFHFEP DFHMTPA DFHMTPA DFHSNP DFHSNP DFHMTPA DFHTAJP DFHTACP DFHSTKC DFHWT1 DFHSNP DFHSNP 100 100 100 40 100 160 100 0 0 100 0 0 100 160 0 0 Entries marked with a single asterisk are required only when numeric-only terminals are used to sign on. Entries marked with a double asterisk are required only when the associated program is desired. Entries marked with a triple asterisk are required only when the Asynchronous Transaction Processing facility is being used. Any transaction codes specified for the TRANSID parameter in any DFHTCT TYPE=TERMINAl macro instruction must also be included in the PCT. 176 Transaction code CSXX is reserved for 3270 support and should not be generated in the PCT. (CSXX is used to generate an "invalid transaction code" message when a zero length data message is received.) The user-assigned transaction security key for entries CSAC, CSSN, and CSSF must always be the value 1. A high priority (for example, 255) is recommended for transactions CSAC, CSTA, CSMT, CSOT, and CSST. A low priority (for example, 001) is recommended for transactions CSFE, CSSF, CSSN, and CSTT. CSMT, CSOT, and CSST do not run in 2260 compatibility mode. COMPAT=NO must be specified or the operand omitted. The following entries are required in the PPT and must be provided through the DFHPPT TYPE=ENTRY macro instruction: gROG.E!1:! l!!1:!] DFHACP Abnormal Condition program. DFHAQP Asynchronous Queue Purge program (required only if the Asynchronous Transaction Processing facility is being used). DFHATP Asynchronous Transaction Control program (required only if the Asynchronous Transaction Processing facility is being used). Basic Mapping Support program (required only if 3270 Basic Mapping support is desired). Terminal Test program (optional). Master Terminal program (required only if master terminal or system termination functions are desired). Dynamic Open/Close program (required only if dynamic open/close facility is desired). Asynchronous Transaction Input processing programs (required only if the Asynchronous Transaction Processing facility is being used). Sign-off program linked to by DFHSNP (required only if sign-on/sign-off function is desired). Sign-on program (required only if sign-on/signoff function is desired). Sign-on Table (required only if sign-on/sign-off function is desired). System Statistics program. System Termination program linked to by DFHMTP. 177 178 DFHSTTD Transient Data and Temporary Storage statistics program linked to by DFHSTKC. DFHSTTR Terminal and Data Base statistics program linked to by DFHSTKC. DFHTACP Terminal Abnormal Condition program. DFHTAJP optional Time Adjustment program that automatically adjusts the date and time of day maintained by CICS to reflect the date and time of day maintained by the operating system. DFHTDCP Device-Dependent Output program for 1030 terminals. DFHTEP Terminal Error program linked to by DFHTACP. DFHTRNxx non-resident data set control blocks as specified by the user in DCT. DFHWTl DFHWT2 Asynchronous Transaction output Processing programs (required only if the Asynchronous Transaction processing facility is being used) • DFHXITxx User-written exit routine used with Asynchronous Transaction Processing transactions CRDR and CWTR. User-specified name User-written program to edit input data and transfer control to the appropriate transaction. This section illustrates the coding required to prepare the CICS Terminal Control Table (TCT). The terminal network described includes: 1. start/stop transmission a. Multipoint line (serving more than one terminal) (1) 1030 Data Collection System (2) 2260 Display Sta tion (remote) b. Point-to-point line (serving only one terminal) (1) 2740 Communication Terminal and 2760 Optical Image unit (2) 2741 Communication Terminal with correspondence code c. switched line (dial-up) (1) 7770 Audio Response unit under CICS/OS (2) 7770 Audio Response unit under CICS/DOS (3) Common Carrier Teletypewriter Exchange Terminal (TWX) 2. Binary synchronous transmission a. Multipoint line (serving more than one terminal) (1) 2980 General Banking Terminal System (2) 3270 Informa tion Display System (remote) b. Point-to-point (serving only one terminal) (1) 2780 Data Transmission Terminal c. Switched line (dial-up) (1) 2770 Data Communication System (2) System/3 (3) 3735 Programmable Buffered ~erminal (CICS/OS only) 3. Transmission via sequential devices a. Card reader/line printer (1) 2540 Card Read Punch and 1403 Printer b. Disk (1) 2314 Direct Access Storage Facility 4. Transmission via devices locally attached a. Graphics devices (1) 2260 Display Station (local) (2) 3270 Information Display System (local) ',-- - Each of the following is a functional example if as shown in the first example, (1) the DFHTCT TYPE=INITIAL macro instruction is inserted at the beginning of each example, {2} the DFHTCT TYPE=FINAL macro instruction is inserted at the end of each example, and (3) an Assembler END card that includes the operand DFHTCTBA is inserted following the DFHTCT TYPE=FINAL macro instruction. DFHTCT TYPE=SDSCI, CU=270 2, DEVICE=1030, LINELST= (024) , SWITCH=NO, DSCNAME=DTF1030 OPL1030 DFTRMLST OPENLST,(64,62) DFHTCT TYPE=LINE, ACCMETH=BTAM, TRMTYPE=1030, DSCNAME=DTF1030, BTAMRLN=l, * * * ** * * * * 179 LISTADR=OPL1030, INAREAL=120 DFHTCT TYPE=TERMINAL, TRMIDNT=T30A, TR ANSID= 1 030, TRMADDR=64, TRMPRTY=202, TRMSTAT=TRANSCEIVE DFHTCT TYPE=TERMINAL, TRMIDNT=T30B, TRANSID=1030, TRMADDR=62, TRMPRTY=201, TRMSTAT=TRANSCEIVE, LASTTRM=LINE l26Q QI2RLAI 21!lION (REMOTE) DFHTCT TYPE=SDSCI, CU=2701, DEVICE=2260, LINELST=(026) , SWITCH=NO, DSCNAME=DTF60R OPL2260 DFTRMLST OPENLST,(40FF,41FF) DFHTCT TYPE=LINE, ACCMETH=BTAM, TRMTYPE=2260, TRMMODL=3, DSCNAME=DTF60R, BTAMRLN= 1, LISTADR=OPL2260, INAREAL=960 DFHTCT TYPE=TERMINAL, TRMIDNT=R60A, TRMADDR=40AO, TRMPRTY=61, TRMSTAT=TRANSCEIVE DFHTCT TYPE=TERMINAL, TRMIDNT=R60B, TRMADD R=40A 1, TRI1PRTY=62, TRMSTAT=TRANSCEIVE DFHTCT TYPE=TERMINAL, TRMIDNT=R530, TRMTYPE=1053, TRMADDR=40A4, TRMPRTY=32, TR!iSTAT=RECEIVE DFHTCT TYPE=TERMINAL, TRMIDNT=R65A, T RMT YP E= 226 5 , TRMADD R=4151 , TRMPRTY=64, TRMSTAT=TRANSCEIVE, LASTTRM=LINE DFHTCT TYPE=SDSCI, CU=2703, DEVICE=2740, FEATURE=(CHK,OIU), 180 * * * * * * * * * * * * * * * * * * * * * * * * * * ** * ** * * * * * * ** * ** * * * * * LINELST=(029) , SWITCH=NO, DSCNAME=DTF40B DFHTCT TYPE=LINE, ACCMETH=BTAM, TRMTYPE=2740/2760, FEATURE=CHECKING, DSCNAM E=DTF40 B, INAREAL=120, BTAMRLN=1 DFHTCT TYPE=TERMINAL, TRr1IDNT=T40C, TRANSID=2760, TRMPRTY=202, TRMSTAT=TRANSCEIVE, LASTTRM=LINE l.!!l1 ~Q~~uNI~!TIQ] 1]RMIM!1 DFHTCT TYPE=SDSCI, CU=2703, DEVICE=2741C, LINELST= (030) , SWITCH=NO, DSCNAME=DTF41C DFHTCT TYPE=LINE, ACCMETH=BTAM, TRMTYPE=2741C, DSCNAME=DTF41C, INAREAL=120, BTAMRLN=1 DFHTCT TYPE=TERMINA1, TRMIDN'1=T41A, TRMPRTY=129, TRMSTAT=TRANSCEIVE, LASTTRM=LINE "- DCB * * * * * * * * * * * * * DFHTCT TYPE=SDSCI, DEVICE=7770, DSCNAME=DCB7770, APPENDG=Z3 L1777) DFHTCT TYPE=LINE, ACCMETH=BTAM, TRMTYPE=7770, DSCNAME=DCB7770, INAREAL=256, BTAMRLN=1, FEATURE=AUTOANSR, ANSWRBK=TERMINAL, CONVTAB=ABB, RDYMSG=READY, ERRMSG=ERROR, POOLADR=T17770 L27770 DFHTCT TYPE=LINE, ACCMETH=BTAM, TRMTYPE=7770, DSCNAME=DCB7770, INAREAL=256, BTAMRLN=2, FEATURE=AUTOANSR, ANSWRBK=TERMINAL, * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 181 co NVTA B=ABB, L37770 DFHTCT L47770 DFHTCT T17770 DFHTCT T27770 DFHTCT T37770 DFHTCT T47770 DFHTCT READY DFHTCT ERROR DFHTCT IIIQ DTF RDYMSG=READY, ERRMSG=ERROR TYPE=LINE, ACCMETH=BTAM, TRMTYPE=7770, DSCNAME=DCB7770, INAREAL=256, BTAMRLN=3, FEATURE=AUTOANSR, ANSWRBK=TERMINAL, CONVTA B=ABB, RDYMSG=READY, ERRMSG=ERROR TYPE=LINE, ACCMETH=BTAM, TRMTYPE=7770, DSCNAME=DCB7770, INAREAL=256, BTAMRLN=4, FEATURE=AUTOANSR, ANSWRBK=TERMINAL, CONVTAB=ABB, RDYMSG=READY, ERRMSG=ERROR TYPE=TERMINAL, TRMIDNT=7771, TRMPRTY=30, TRMTYPE=7770, TRMSTAT=TRANSCEIVE TYPE=TERMINAL, TRMIDNT=7772, TRMPRTY=30, TRMTYPE=7770, TRMSTAT=TRANSCEIVE TYPE=TERMINAL, TRMIDNT=7773, TRMPRTY=30, TRMTYPE=7770, TRMSTAT=TRANSCEIVE TYPE=TERMINAL, TRMIDNT=7774, TRMPRTY=30, TRMTYPE=7770, TRMSTAT=TRANSCEIVE, LASTTRM=POOL TYPE=7770MSG, MESSAGE='001DOB' TYPE=7770MSG, MESSAGE='OOOAOF' AU~!Q E~SPO]~~ UNII UN~~E ~ICSLDO~ DFHTCT TYPE=SDSCI, DEVICE=7770, DSCNAME=DTF7770, SWITCH=YES, LINELST=(080,081,082,083) , BLKSIZE=256, FLNNAME=L17770 L17770 DFHTCT TYPE=LINE, ACCMETH=BTAM, TRMTYPE=7770, DSCNAME=DTF7770, 182 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * L27770 DFHTCT L37770 DFHTCT L47770 DFHTCT , '-.,-- T17770 DFHTCT T27770 DFHTCT T37770 DFHTCT T47770 DFHTCT READY DFHTCT ERROR DFHTCT "- INAREAL=256, BTAMRLN=1, FEATURE=AUTOANSR, ANSWRBK=TERMINAL, co NVTA B= ABB, RDYMSG=READY, ERRMSG=ERROR, POOLADR=T17770 TYPE=LINE, ACCMETH=BTAM, TRMTYPE=7770, DSCN AM E=DTF777 0, INAREAL=256, BTAMRLN=2, FEATURE=AUTOANSR, ANSWRBK=TERMINAL, CONVTA B=ABB, RDYMSG=READY, ERRMSG=ERROR TYPE=LINE, ACCMETH=BTAM, TRMTYPE=7770, DSCNAME=DTF7770, INAREAL=256, BTAMRLN=3, FEATURE=AUTOANSR, ANSWRBK=TERMINAL, CONVTAB=ABB, RDYMSG=READY, ERRMSG=ERROR TYPE=LINE, AC CMETH=BTAM, TRMTYPE=7770, DSCNAM E=DTF777 0, INAREAL=256, BTAMRLN=4, FEATURE=AUTOANSR, ANSWRBK=TERMINAL, CONVTA B=ABB, RDYMSG=READY, ERRMSG=ERROR TYPE=TERMINAL, TRMIDNT=7771, TRMPRTY=30, TRMTYPE=7770, TRMSTAT=TRANSCEIVE TYPE=TERMINAL, TRMIDNT=7772, TRMPRTY=30, TRMTYPE=7770, TRMSTAT=TRANSCEIVE TYPE=TERMINAL, TRMIDNT=7773, TRMPRTY=30, TRMTYPE=7770, TRMSTAT=TRANSCEIVE TYPE=TERMINAL, TRMIDNT=7774, TRMPRTY=30, TRMTYPE=7770, TRMSTAT=TRANSCEIVE, LASTTRM=POOL TYPE=7770MSG, MESSAGE='001DOB' TYPE=7770MSG, * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 183 MESSAGE='OOOAOF' DPHTCT TYPE=SDSCI, CU=2702, DEVICE=TW35, LINELST= (039) , SWITCH=YES, DSCNAME=TWXONE IDLTWX DFTRMLST IDLST,O,19,01B151FFC393C3CB052BEB1BB151E1E1E1E1A1 TWXIDA DFTRMLST IDLST,7,4931683,10,500AB222C3052B2B9AB1 DFHTCT TYPE=LINE, ACCMETH=BTAM, TRMTYPE=TWX, DSCNAME=TWXONE, INAREAL=120, BTAMRLN=1, LISTADR=IDLTWX, FEATURE=(AUTOANSR,AUTOCALL), POOLADR=TWXAUTO, ANSWRBK=AUTO TWXAUTO DPHTCT TYPE=TERMINAL, TRMIDNT=TWXA, TRMADDR=TWXIDA, TRMPRTY=201, TRMSTAT=TRANSCEIVE, LASTTRM=POOL DFHTCT TYPE=SDSCI, CU=2703, DEVICE=BSCMDMPT, BSCODE=EBCDIC, SWITCH=NO, DSCNAME=DTF2980 TCT29POL DFTRMLST AUTOWLST, (C1C1F02D,37373737) TCT29PA1 DFTRMLST OPENLST, (8181402D) TCT29PA2 DFTRMLST OPENLST, (8181F12D) TCT29PA3 DFTRMLST OPENLST, (8181F22D) DFHTCT TYPE=LINE, ACCMETH=BTAM, TRMTYPE=2980, DSCNAME=DTF2980, INAREAL=480, BTAMRLN=1, LISTADR=(TCT29POL,WRAP), PEATURE=AUTOPOLL DFHTCT TYPE=TERMINAL, TRMIDNT=T801, STN2980=O, TAB2980=04, POLLPOS=01, TRMADDR=TCT29PA1, TRMMODL=1, TRMPRTY=10, TIOAL=200, TRMSTAT=TRANSCEIVE DFHTCT TYPE=TERMINAL, TRMIDNT=T802, STN2980=1, TRMADDR=TCT29PA2, 184 * * * * * * * * * * * * * * * * * * * * * * * * POLL CU ADDRESS STATION 1 ADDRESS STATION 2 ADDRESS STATION 3 * * * * * * * * * * * * * * * * * * * * TRMMODL=2, TRMPRTY=10, TIOAL=200, * * * * * * * * * * * * TRMS~A~=TRANSCEIVE DFHTC'I TYPE=TERMINAL, TRMIDNT=T803, STN2980=2, TAE2980=02, TRMADDR=TCT29PA3, TRMMODL=4, TRMPRTY=10, TICAL=200, TRMS'IAT=TRANSCEIVE, LASTTRM=LINE ]Q1~: l11Q This is a functional example for CICS/DOS if the (C1C1F02D,37373737) parameters in the above TCT29POL DFTRMLST statement are changed to 3732,C1C1F02D. lB~~]~ATIOM ]1~g1AX ~1~1]~ POLL77 LSTR77A LSTn77B LSTR77C DFTRMLST AUTOWLST, (40407F7F2D,C1C17F7F2D,3737373737) CFTRMLST CPENLST,(6Q6040402D) DFTRMLST OPENLST,(616140402D) DFTRMLST CPENLST,(6161C1C12D) DFHTCT TYPE=SDSCI, DEVICE=BSCMDMPT, DSCNAME=REMOTE77, ESCOCE=EBCBIC DFHTCT TYPE=LINE, ACCME'IH=BTAM, TRMTYPE=3277, LISTADR=(POLL77,WRAP) , BTAMRLN=1, DSCNAME=REMOTE77, INAREAL=256, * ** * * * * * * * * * ** * * * * * * * * * * * * * * * * * * TR~MODL=2, FEATURE=AUTOPOLL DFHTCT TYPE=TERMINAL, TRMIDNT=R77A, TRMMODL=1, TRMTYPE=3275, TRMADDR=LSTR77A, POLLPOS=1, CCMPAT= (480,12,2260,2) , FEATURE=PTRACAPT, TIOAL=500 DFHTCT TYPE=TERMINAL, TRMIDNT=R7:JB, TRMADDR=LSTR77B, P01LPOS=2, COMPAT=(960,15,2265,2) , FEATURE=(COPY,DCKYEC,SELCTPEN) , TIOAL=1500 DFHTCT TYPE=TERMINAL, TRMIDNT=R77C, TRMTYPE=3286, FEATURE=COPY, TRMADDB=LSTR77C, LASTTRM=LINE, TRMSTA'I=TRANSCEIVE, TIOAL=1500 ]ot~: This is a functional example for CICS/DOS if (1) the (40407F7F2D, 185 ClC17F7F2D,3737373137) parameters in the above POLL?7 DFTRMLIST statement are changed to 3732,40407F7P2D,ClC17F7F2D, and (2) the LINELST=(029) and CU=2703 operands are included in the DFHTCT TYPE=SDSCI specification. ,678Q DA%A N2780 DFHTCT TYPE=SDSCI, BSCOtE=EBCDIC, DDNAME=DDN2780, DEVICE=2780, DSCNAME=DCBN2780, CU=2703, LI NELS!= (023) , FEATURE=(BSC,SLV), MODELST=O, CONFIG=PPT, SWITCH=NO, MA CRF= (R, W) DFHTCT TY'PE=LINE, TRMTYPE=2780, DSCNAME=DCBN2780, ACCMETH=BTAM, ETAMRLN= 1, BSCOIJE=EBCDIC, INAREAL=520 DFHTCT TYPE=TERMINAL, TRMIDN'I=T80A, LASTTRM=LINE, TRMTYPE=2780, TIOAL=100, TRMSTAT=TRANSCEIVE, TRMPRTY=126 l:11Q ]A1A D2770 186 ~]A~~~l~SIQn 1~]~1]A1 * * * * * * * * * * * * * * * * * * * * * * * ~~~~~Bl~ATIOn ~X~1~~ DFHTCT TYPE=SDSCI, BSCODE=EBCDIC, DDNAME=DDD2770, DEVICE=2770, DSCNAME=DCBD2770, MACRF= CR, W) , CU=2103, LINELST=(020) , FEATURE=(BSC,SLV) , MODELST=O, CONFIG=PPT, SWITCH=YES DFHTCT TYFE=LINE, TRMTYPE=2770, DSCNAME=DCBD2770, ACCMETH=BTAM, ETAMRLN=1, BSCOtE=EBCDIC, FCCLADR=D2770, INAREAL=520, FEA'IURE=AUTOANSR, LISTADB=LA2170, ANSWRBK=TEEMINAL DFHTC'I TYPE=TERMINAL, TRMIDN'I=D10A, LASTTRM=FOOL, TICAL=100, * * * * * * * * * * * * * * * * * * * * * * * * * TRMTYPE=2770, TRMADDR=TA2770, TRMSTAT=TRANSCEIVE, TRMPRTY=126 LA2770 DFTRMLST BSCLST,0,1,2D,2,1070 TA2770 DF~RMLS~ BSCLST,0,2,1070,1,2D * * * DFHTCT TYPE=SDSCI, BSCOtE=EBCDIC, DDNAME=DDDSYS3, DEVICE=SYS/3, * * * * * * * * * * * * * * * * * DSCNAM~=DCBDSYS3, MACRF= (R, il) , CU=2703,LINELST= (020) , FEATURE=(BSC,SLV), I10DELS'I=0, CONFIG=PPT, SiiITCH=YES DFHTCT TYPE=LINE, TRMTYPE=SYS/3, DSCNAME=DCEDSYS3, ACCMETH=BTAM, BTAMRLN=1, BSCOtE=EBCDIC, EOCLAD"R=SYS3D, INAREAL=500, FEATURE=AUTOANSR, LISTADR=LASYS3, ANSWRBK=TERMINAL SYS3D DFHTCT TYPE=TEBMINAL, TRMIDN'I=DSY3, LASTTRM=POOL, TICAL=100, TRMTYPE=SYS/3, TRMADDR=TASYS3, TRMSTA'I=TRANSCEIVE, TRMPRTY=126 LASYS3 DFTRMLST BSCLST,O,1,2D,2,1070 'lASYS3 DFTRMLST BSCLST,0,2,1070,1,2D ]12.2 A3735 ~.BQg13l!1111AB1] ~ 96 X 5 + 20 PAD * * * * * * * * * * lH!!FE]]Q ~~E111]!1 (Not applicable to CICS/DOS-Entry) * * * * * * * * * * * * * * * * DFHTCT TYPE=SDSCI, DEVICE=BSCMDSW, CU=2703, BSCOtE=EBCDIC, PSCNAME=DTF35D DFHTCT TYPE=LINE, ACCMETH=BTAM, TRMTYPE=3735, DSCNAME=DTF35D, INAREAL=480, ETAMRLN=1, LISTADR=LISTA, FEATURE=(AUTCANSR,AUTOCALL) , POCLADR=A3735, ESCODE=EBCDIC, ANSWRBK=EXIDVER DFHTCT 'IYPE=TERMINAL, TBMIDNT=3735, 187 TRMTYPE=3735, LASTTRM=POOL, TRMADDR=LISTB, TRMS!A~=TRANSCEIVE, TRANSID=37 35, TICAL=476 LISTA DF~RMLST SWLST,AN,11 ,4,2,1070, (98FOF3F5182D"A3735) LISTB DF'IRMLST S'HLST,AD,4,3374,8,0,1,2D, (98FOF3F5181C70,1) 12!!Q £~]~ B!!~ RY~fBL~Ql RB1]TE] DFHTCT TYPE=SDSCI, DEVADDR=SYSIPT, DEVICE=2540, DSCNAME=READER DFHTCT TYPE=SDSCI, DEVADDR=SYSLST, DEVICE=1403, DSCNAMF=PRINTER DFHTCT TYPE=LINE, ACCMETH=BSAM, TRMTYPE=CRLP, ISADSCN=READER, OSADSCN=PRINTER, INAREAL=80 DFHTC~ TYPE=TERMINAL, TRMIDN~=SAMA, TRMTYPE=CBLP, TRMS~A~=TRANSCEIVE 111!! ~1~R1!I ~I!IIQ!! * * * * * * * * * * * * * * .(LOCAL) DFHTCT TYPE=SDSCI, CU=2848, DEVICE=L2260, 188 * * * * * * * * * * * * * * ~l]!~I !~f]~~ ~lQ]!Q~ f!£~111! DFHTCT TYPE=SDSCI, DEVADDR=SYS001, DEVICE=2314, DSCNAME=DISKIN1 DFHTCT TYPF=SDSCI, DEVADDR=SYSOO6, DEVICE=2314, 1::S CNAM E=DISKOT 1 DFHTCT TYPE=LINE, ACCMETH=SEQOENTIAL, TRMTYPE=DASD, ISADSCN=DISKIN1, OSADSCN=DISKOT1, INAREAL=80 DFHTCT TYPE=TERMINAL, TRMIDNT=SAMB ,. TRMPRTY=11, TRMSTAT=(TRANSCEIVE,'OUT OF SERVICE' ) l26Q * * * * * * * * LINE1 DFHTCT DFHTCT DPHTCT DFHTCT 32]Q -'- T010 N0ig: LINELST= (021 ,022,023) , FEATURE=KBL, SWITCH=NO, FLNNAME=LINE1, DSCNAME=DTF60L TYPE=LINE, ACCMETH=BTAM, TRMTYPE=L2260, CLASS=VIDEO, DSCNAM E=DTF60L, INAREAL=960, FEATURE=KBRDLOCK TYPE=TERMINAL, TRMIDNT=L60A, LVUNIT=1, TRMPRTY=32, TRMSTAT=TRANSCEIVE TYPE=TERMINAL, TRMIDNT=L60B, LVUNIT=2, TRMPRTY=32, TRMSTAT=TRANSCEIVE TYPE=TERMINAL, TRMIDNT=L530, TRMTYPE=1053, LVUNIT=3, T3MPRTY=32, TRMSTAT=RECEIVE, LASTTRM=LINE lBE~RMATIQN QISPLAX ~X~1~~ * ** * ACCMETH=BGAM FOR CICS/OS * * * * * * * * * * * * * * * * * * * * (LOCAL) DFHTCT TYPE=SDSCI, DEVICE=L3277, DSCNAME=L3270 DFHTCT TYPE=LINE, ACCMETH=BTAM, DSCNAME=L3270, TRMMODL=2, TRMTYPE=L3277, POOLADR=TO 10, INAREAL=2500, POOLCNT=2 DFHTCT TYPE=TERMINAL, TRMIDNT=L77A, LVUNIT=1, FEATURE=(SELCTPEN,AUDALARM) , COMPAT=(480,12,2260,2) DFHTCT TYPE=TERMINAL, TRMIDNT=L77B, LVUNIT=2, TRMTYPE=L3277, LASTTRM=POOL, TRMSTAT=TRANSCEIVE * * * * * * * * * * * * * * * * * * This is a functional example for CICS/DOS if (1) the CU=3272 and LINELST=(030,031) operands are included in the DFHTCT TYPE=SDSCI specification, and (2) if the POOLCNT=2 operand is deleted from the DFHTCT TYPE=LINE specification. '- 189 The following illustrates the interrelationship between the TCAM Message Control program (MCP) and the TCAM Message Processing program (MPP). CICS is regarded as a Message Processing program by TCAM. CICS ~1PP DD CARDS / /QINI / /QOUTI / /R2260Itl / /R2260UT DD QNAME=RISI DD QrJAME=WI SI DD QNAME=R601 DD Qi~AME=R600 The following is an example of a CICS Terminal Control Table and a TCAM Message Control program. DFHTCT TYPE=INITIAL,SUFFIX=TV DFHTCT TY PE=S DSCI, DEV ICE=TCAM, DSCNAME=L1, DDNAME=QIN1, OPTCD=WU, MACRF=R, RECFM=U, BLKSIZE=500 DFHTCT TYPE=SDSCI, DEVICE=TCAM, DSCNAME=L2, DDNAME=QOUT1, OPTCD=WU, MACRF=W, RECFM=U, 190 * ** * * * * * * * * * * * / BLKSIZE=500 DFHTCT TYPE=LINE, ACCMETH=TCAM, QU:EUEID=F1, INAREAL=500, TRMTYPE=L2260, DSCNAME=L1, OU'IQ=OUTQ DFHTCT TYPE=TERMINAL, TRMIDNT=DMMY, TRMPRTY=32, LASTTRM=LINE OUTQ DFHTCT TYPE=LINE, ACCMETH=TCAM, QUEUEID=FO, INAREAL=500, TRMTYPE=L2260, tSCNAM:E=L2 DFHTCT TYPE=TERMINAL, TRMIDNT=TRM1, TRMPRTY=32 DFHTCT TYPE=TERMINAl, TRMIDNT=TRM2, LASTTRM=LINE, TRMPRTY=32 DFHTCT TYPE=SDSCI, DEVICE=TCAM, DSCNAME=R60IN, DDNAME=R2260IN, OP'ICD=WU, MACRF=R, RECFM=U, BLKSIZE=500 DFHTCT TYPE=SDSCI, DEVICE=TCAM, DSCNAME=R600UT, DDNAME=R2600UT, OP'ICD=WU, MACRF=W, RECFM=U, BLKSIZE=500 DFHTCT TYPE=LINE, ACCMETH=TCAM, INAREAL=500, DSCNAM:E=R60IN, OU'IQ=OUTQ60, TRMTYPE=2260 DFHTCT TYPE=TERMINAl, TRMIDNT=1260, TRMPRTY=32, LASTTRM=LINE OUTQ60 DFHTCT TYPE=LINE, ACCMETH=TCAM, INAREAL=500, DSCNAME=R600UT, TRMTYPE=2260 DFHTCT TYPE=TERMINAL, TRMPRTY=32, TRMIDNT=S60A DFHTCT TYPE=TERMINAL, TRMPRTY=32, TRMIDNT=S60B DFHTCT TYPE=TERMINAL, TRMPRTY=32, TRMIDN'I=S65A, * * * * * * * * * * * * * * * * * * * * * ** * * * * * * * * ** * * * ** * ** * ** * * * * * * * * '-- 191 LASTTRM=LINE DFHTCT TYPE=FINAL END DFHTCTEA MCPCICS TCAMINIT NOEXEC OPEN LINE FINISH LG2260 FG2260 QPROC RIS1 WIS1 R60I R600 S60A S60B S65A TRM1 192 CSECT INTRO LTR BZ ABEND OPEN TM BNO TM BNO WTO READY CLOSE L RETURN nCB DISK=NO, PROGID=TCAM/CICS, LNUNITS=40, MSUNITS=20, KEYLEN=133, CBOSSRF=4, DLQ=TRM1, S'IARTUP=CY, TRACE=10, LINETYP=BOTH, OL'IEST=O 15,15 OFENLINE 123,DUMP (LG2260, (INOUT) ,PG2260, (INOUT» LG2260+48,DCBOFLGS NOEXEC PG2260+48,DCBOFLGS NOEXEC 'TIME TO START APPLICATION PROGRAM' (LG2260" PG2260) 13,4 (13) (14,12) DSORG=TX, MACRF=(G,P) , CPRI=S, DDNAME=DDLG2260, MH=TOTCAM, PCI= (N, N) , BUFSIZE=464, INVLIST=(POLLST1",FOILST2),TEANS=EBCD DCB DSORG=TX,MACRF=(G,P),CPRI=S,DDNAME=DDPG2260, MH=MH2260,PCI=(N,N) ,BUFSIZE=464, INVLIST= (POLL60R,,) ,TRANS=2260 PCB MH=TOCICS, BUFSIZE=464, RESERVE= (20) TTABLE LAST=TRM2 TFROCESS FCB=QPROC, QUEUES=MO TFROCESS PCB=QPROC 'IFROCESS PCB=QPROC,QUEUES=MO 'IFROCESS PCB=QPROC TERMINAL QBY=T,DCB=PG2260,RLN=1,TERM=226R,QUEUES=MO, AtDR=40AOEOFF TERMINAL QBY=T,DCB=PG2260,RLN=1,TERM=226R,QUEUES=MO, ADDR=40A1EOFF TERMINAL QBY=T,DCB=PG2260,RLN=1,TERM=2265,QUEUES=MO, ADDR=4151EOFF TERMINAL CBY=L, DCB=LG2260, RLN= 1, TERM=226L, QUEUES=MO, AtDR="FFFFFFFF, SECTERM=YES * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * TRM2 POLLST1 POLLST2 POLL60n TOTCAM INMSG MH2260 TOCICS DCBOFLGS TERMINAL QBY=L, DCB=LG2260, RLN=2, TERM=226L, ADDR=FFFFFFFF, QUEUES=MO INVLIST ORDER= (TRM1+02) INVLIST ORDER= (TRM2+02) INVLIST ORDER=(S60A+40A040,S60B+40A140,S65A+415140) STARTMH LC=OUT INHDR CODE FORWARD DEST=C'RIS1' EQU INMSG INEND OUTHDR OUTEND STARTMH LC=OUT INHDR CODE SETSCAN 1 MSGEDIT «R"SCAN» FORWARD DEST=C'R60I' INMSG INEND OUTHDR SETSCAN 1 MSGEDIT ( (R, , SCAN) ) MSGFORM BLOCK=460 CODE OUTEND STARTMH LC=OUT INHDR CODE FORWARD DEST=PUT INEND OUTHDR OUTEND EQU X' 10' END * * * * * * 193 This section is intended to aid the system programmer in the preparation of the Terminal Control Table (TCT) as he uses operands of the DFHTCT macro instruction to: 1. 2. 3. Specify data set control information Describe communication lines Describe terminal types Included in this section is an indication of whether the operands of the DFHTCT macro instruction are: 1. 2. 3. 194 Optional or required Applicable only to CICS/DOS, only to CICS/OS, or to both CICS/DOS and CICS/OS Applicable or required only under special circumstances : D E V A D D DEVICE R D S C E F L R R 0 P E A I N T U M T E E E L S T N A R S C W U I T C H C 0 N F I G B S C M R 0 E D T E R L Y S T 0 D E T E L E R R M T S T B A D R D I M F D A L u C N l' A R N Ii F E S Y A M 'B L D K E S I M E Z D E G N C P 0 R E A P P C N 0 P T F A C E M D D N I * 1030 1050 1130 1403 R 1404 R 1442 R 1443 R 1445 R 2020 2260 L2260 2265 2311 R 2314 R 2501 R R 2520 2540 R 2740 2740/2760 2741C 2741E 2770 2780 2980 3275 3277 L3277 3284 L3284 3286 L3286 3330 R 3735 7770 BSCMDMPT BSCMDPPT BSCMDSW DASD R DISK R SYS/3 SYS/7 S360 TAPE R TW33 TW35 TCAM Not~: I i R 0 R 0 R 0 R R R R R I R :0 R 0 R R 0 R R R R R R 0 R 0 R 0 R 0 R 0 R 0 R 0 R 0 R 0 R R 0 R R 0 R R R 0 R R 0 R 0 R 0 R R R 0 R 0 R 0 R R 0 R 0 R R R 0'': R I 0 0 0 R R R J0 i 0 # * * * * *\* * * 0 ; iO 0 0 0 0 0 0 i 0 0 0 0 0 a R R R R R R R R R R 0 0 0 0 0 0 0 R R R R R R R R 0 R R R R R R R 0 R R R R R R R R R R R R R R R R R R R 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 R R R 0 0 a 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 o 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 !O 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 i 0 ! 0 I 0 0 0 0 R R R 0 0 0 R R R 0 0 0 0 0 0 0 0 R R 0 0 R R 0 0 0 0 0 0 0 R o Optional. * CICS/DOS only. 0 # 0 0 0 # # # # 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 # # # I j 0 I I I I I, I i 0 !R 0 : 0 0 I 0 0 " 0 0 0 0 0 -.- ---_. - -.---- .... 0 0 ---- -_.- _.,,- -_._0 __ .-_0. 0 -- ..- .. -- 0 0 0 0 0 0 0 0 0 0 0 # R 0 0 - 0 0 0 0 0-_.- 1-----" 0 -0- - - 1---_. 0 0 0 0 0 0 0 0 0 0 0 0 0 0 R R R 0 0 0 0 ----- _..----- ------ 0 0 --- 0 0 0 R R 0 R Required. 195 ~- ..-. i ClCS/OS only. A C C L C A M S E S T H TRMTYPE D S C N I 0 S S A D S C N A D A S M C E N I N T R A R E M M 0 A D L L B T A M R L N L I S T A D R F E A T U R E N P D E L A Y P a a L A D R A L I S N W S R T B A K T N B S C 0 D E C R D N Y M V T S A G B a E R R M S G G E N P 0 R3 0 R R3 0 R R2 0 R R3 0 R R3 0 R R3 0 R R3 0 R R2 a R R3 0 R R3 a R R3 0 ---R R3 a R -'---'R ~.f_~ . "_.. _._, R3 a R3 (f- R 2741E R3 0 R 2770 R3 a R 2780 R3 f--2980 0 R -_. -R3 0 R 3275 R3 0 R 3277 R3 0 R L3277 R3 0 R 3284 R3 0 R L3284 R3 0 R 3286 R3 a R L3286 R3 a R 3735 R3 a R 7770 R3 a R SYS/3 R3 a R SYS/7 R3 0 R S360 Rt a CRLP R Rt 0 DASD R Rt 0 TAPE R R3 0 R TWX Rl a R U/R ----- Not~: L C L L N T # R R R R .,,--.-.- -. R R R R 0 R R9 R9 R a R 0 R 0 R 0 R R R R R R R R R R R R R R R 0 R R R R 0 0 0 R R R R R R R R R R R R R R R R R R R R R a a R R R R R R RB R R R R R f..---.- a R~ R~ R 0 0 0 0 0 a a a a R R 0 0 0- R~ R~ R R R ~-- a a a a R 0 0 0 R a a R 0 0 R R R R~ 0 0 0 R6 0 0 0 0 0 R6 - - - 0 ..- --a..- r---- r---a 0 _.... --- ."- _9 . a 0 a -_Qf---.-- - - - - - 1 - - - - -0 0 a 0 0 a R6 R6 a R RS RS a ----- RO RO RO RO RO RO RO 0 R6 R6 0 R R5 R7 R R~ R R 0 --.-- R6 R6 R6 R6 R6 R6 1--a R6 a R6 a ---::- R6 0 R6 0 0 a a R - - r---' a ---- ---- a a a a a --a a R R6 R6 R6 R6 R6 R6 R6 R6 R6 R6 -- f---- RO RO RO RO RO RO RO RO RO RO RO RO RO RO RO a ---- __ ._--. 0 0 ----'. .- R "._--- 0 0 R _R~__ - -- _. __.- - - - - - f - - . - f - - ---- ------ ~---- 0 R 0 --- a -- --- ---- -,--- rR 0-0 0 0 a a a a 1fO 0 R a a a 0 R R a -_. 0 R R a a Required. Optional. i ClCS/OS only. TRMMODL may be specified in TYPE=LINE or TYPE=TERMlNAL. o Required if a terminal work area (PCl) field is to be defined for all terminal entries associated with this line. Specify ACCMETH=SAM, ACCMETH=BSAM, or ACCMETH=SEQUENTlAL. Specify ACCMETH=BGAM or ACCMETH=GRAPHlCS. Specify ACCMETH=BTAM or ACCMETH=TELECOMMUNICATlON. Required for switched (dial-up) lines and multipoint lines. Required if FEATURE=(AUTOANSR,AUTOCALL,SCONTROL). Required for first line in switched-line pool; specify ANSWRBK=EXlDVER for 3735 under ClCS/OS and CICS/DOS-STANDARD. 1 2 3 4 5 6 RO RO RO RO --Ifo R o * 196 R R T C T U A L a * 1030 1050 1053 OS 1053 DOS 1130 2020 2260 L2260 as L2260 DOS 2265 2740 2740/2760 P 0 RO RO RO RO RO 7 8 9 Checking required; other features optional. Required for component polling; default: poll all components. Required for the 2740 Model 2 or the 2740 with 2760. T R T R M I M P R TRMTYPE D N T Y 1030 1050 1053 OS 1053 DOS 1130 2020 2260 L2260 2265 2740 2740/2760 2741C 2141E 2770 2780 2980 3275 3277 L3277 3284 L3284 3286 L3286 3735 7770 SYS/3 SYS/7 S360 CRLP DASD TAPE TWX U/R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Noig: R o 1 2 3 4 5 T T C R L M A M S 0 S D L 0 0 R5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 R6 0 R 0 0 0 0 0 0 0 0 0 R 0 R 0 R 0 R 0 R 0 R 0 R 0 R 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 L L V A S T T R U N I T M 0 0 Rl 0 Rl 0 0 0 0 R 0 0 0 0 0 0 0 0 0 0 0 R 0 0 R 0 0 R 0 0 0 0 0 0 0 0 0 0 0 T T R R M M A S D T D A R T R3 R3 R2 R2 R4 R4 R3 R3 R3 R3 R4 R4 R R R R R R4 R3 R4 R3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 F E M A P T A U T R L L P T R A N S 0 I E S D 0 0 0 0 0 0 0 0 0 0 0 0 C P 0 0 S T N 2 9 8 0 T A B 2 9 8 T I 0 A L R 0 0 0 R 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 R R R R R 0 0 0 0 0 0 0 0 0 0 0 0 R R 0 0 0 0 0 0 0 R 0 0 0 0 0 0 0 0 0 0 0 0 0 T C T U A L R7 R7 R7 R7 R7 R7 R7 R7 R7 R7 R7 R7 R7 R7 R7 R7 R7 R7 R7 R7 R7 R7 R7 R7 R7 R7 R7 R7 R7 R7 R7 R7 R7 Required. Optional. Required only for local devices. Required only for remote devices; specify hexadecimal addressing characters. Required; specify hexadecimal addressing characters for non-switched lines; specify name of DFTRMLST for switched lines. (For TWX, not required if ANSWRBK=TERMINAL is specified) • Required for multipoint lines and for switched lines if FEATURE=AUTOCALL has been specified in the DFHTCT TYPE=LINE macro instruction; specify name of DFTRMLST. Required for component polling; defaults to polling all components. 197 6 7 198 Required for the 2740 Model 2 or the 2740 with 2760. Required for terminals when the user defines a 0-255 byte terminal work area (Process Control Information field). This section is intended to aid the system programmer in the preparation of the File Control Table (FCT) as he uses the DFHFCT TYPE=DATASET macro instruction to describe the physical characteristics of the data sets. These descriptions include information about the access method (BDAM or IS AM) and record characteristics for the data sets. CICS/DOS I SAM Q r:LJ ~ 0 0 H m BLKKElL EXTENT CYLOFL INDAREA INDSIZE INDSKIP MSTIND NRECDS IOSIZE IOWORK DEVICE SRCHM VERIFY RELTYPE LRECL BLKSIZE RKP RECPORM OPEN KEYLEN SERVREQ=KEY Not~: R o 1 2 3 4 5 6 7 8 Q r:LJ ~ H m :z; ::::> BLOCKED :>t r:LJ ~ ~ r:LJ ~ .......... ~ R R R R2 R3 R R R R2 R3 0 0 R4 R R4 05 05 0 0 0 0 0 0 0 0 0 R R R R R R 0 0 R R Rl :>t Rl CICS/OS DAM UNBLOt ~ ~ .......... I SAM BDAM BLOCKED UNBLOCKED :>t Q Q f4 J:il ~ 0 H ~ J:il .......... 0 ~ ~ R Rl Rl ~ 0 H .c:Q ::::> f4 ~ .......... J:il IX} :z; ~ 0 ~ R :>t :>t J:il ~ .......... ~ J:il .......... ~ ~ R R2 R3 R2 R3 05 05 05 05 0 0 0 0 0 0 0 0 Rl R R R7 R Rl R R6 R7 R Rl R R R7 R 0 0 0 0 0 0 0 Rl R R6 R7 R Rl R R R7 R Rl R R6 R7 R Rl R R R7 R R R R R R R R R Rl R R6 R7 R 0 Re 0 0 0 0 0 0 R ~ R 0 0 0 R :>t :>t 0 R" R R 0 R Required. Optional. Specifies relative type addressing; RELTYPE must also be specified. Required if main storage high-level index processing is used. Required if INDAREA is specified. Required only if a master index exists. Optional; used only if SERVREQ=NEWREC; for ISAM data sets under CICS/OS, IOWORK should also be specified. If SERVREQ=BROWSE or SERVREQ=NEWREC, this value must be BLKSIZE plus BLKKEYL. Required if key exists within logical records. Required if deblocking by key for BDAM (CICS/DOS and CICS/OS); required for variable-length ISAM records in fixed-length blocks (CreS/DOS only). 199 This section lists the CICS macro instructions used for system generation and table preparation. These macro instructions are written in Assembler language and, as all Assembler language instructions, are written in the following format: blank DFHxxxxx or symbol One or more operands separated by commas The name field of a CICS macro instruction must be left blank if the macro instruction is used in conjunction with a high-level language (ANS COBOL or PL/I); if a label is desired for the macro instruction, it may be placed on the card preceding the macro instruction. The operation field of a CICS macro instruction must begin before card column 16 and must contain the three-character combination "DFH" in the first three positions of the operation field. Up to five additional characters can be appended to DFH to complete the symbolic name for the appropriate program or table. Since DFH is reserved for CICS macro instructions, no other statement may begin with this three-character combination. The operand field of a CICS macro instruction contains one or more operands separated by commas. In this publication, parentheses are used to indicate those operands where more than one applicable parameter (keyword and otherwisej can be specified with a single use of the operand. Where parentheses are not used, only one parameter at a time can be specified as part of the operand; a choice must be made in the case of more than one applicable parameter. Since a blank character indicates the end of the operand field, the operand field must not contain blanks except after a comma on a continued card or after the last operand of the macro instruction. The first operand on a continuation card must begin in column 16. When a CICS macro instruction is coded on more than one card, each card containing part of the macro instruction (except the last card) must contain a character (for example, an asterisk) in column 72 indicating that the macro instruction has been continued on the next card. In the following listing of CICS macro instructions, default parameters (where applicable) are indicated by an underscore. An asterisk in card column 72 indicates that th~ macro instruction is continued on the next card. Because the flexibility and modularity of CICS allows a wide combination of options during system generation and table preparation, no attempt is made in this section to indicate which operands are optional and which are mandatory. For this information, refer to the previous sections of this pUblication. 200 DFHSG TYPE=INITIAL, STATUS=FIRST, ASMBLR=Assembler name, OPSYS=(VS1,VS2,number) , TRACE=lES,NO, TIMECTL=YES,NO, DSIZE=number,l, MPS=YES,NO, JOBNAME=jobname,CI~~, ACCTID=accounting information,~ICSQli!, PGMERID='programmer's name','~X~TE~ RROQRA~MEE', MSGLVL=Q, 1, DEVICE=2311,2314,3330, CONDCD= (code, operator) , ••• , (code, operator) ) , PRIORTY=nn, MSGCLAS=x,!, CLASS=jobclass,!, REGION=(n1K,n2K) , PROCNMS=procedure names, (DFli!~~Y~,Q~liLNKYl, DFHUP~!l,DF]AUPLK) , DL1=YES,.!ill, ATP=YES,!Q, PREFIX=prefix, TCTUA=(V1CMPAT,!ARIA~1]) DFHSG PROGRAM=CSO, MPS=XES,NO, NSD=number,2, DEVICE= 2311,2314,3330, SVC=number,20Q, CAA=appendage suffix, V1CMPAT=YES, TCAMSIP=YES * * * * * ** * * * ** ** ** * * * * * * * * * * * * * * DFHSG PROGRAM=CSS DFHSG PROGRAM=CSD DFHSG PROGRAM=CSU, DEVICE=(TAg~,~111,1J1~,3330) DFHSG PROGRAM=KCP, CONSEC=YES, RUNAWAY=YES, STALCTL=YES, ENQUEUE=YES, OPSECUR=YES, ICPTIME=YES, * * * * * * * * 201 ICPAUTO=YES, ICPSYNC=YES, SUFFlX=program suffix, XTYPREQ=symbolic name, XDSPCHR=symbolic name, DEVlCE=(2311,2314,3330) ** DFHSG PROGRAM=SCP, XTYPREQ=symbolic name, SUFFlX=program suffix * * DFHSG PROGRAM=PCP, * PCPLOAD=YE~,NO, LANG=(COBOL,PL/l) , HLLTR=YES,MQ, COBOL=(V2,V3,V4,SUBSET) , XFETCH=symbolic name, SUFFlX=program suffix DFHSG PROGRAM=PIP, SUFFlX=program suffix IN!~BVA1 CONTBQ1 RBQGR!~ * * * * * * (lCP) DFHSG PROGRAM=lCP, RUNAWAY=YES, ,lCPTlME=YES, lCPAUTO=YES, ICPSYNC=YES, SUFFIX=program suffix, XTYPREQ=symbolic name, XICEEXP=symbolic name, DUMMY=YES DFHSG PROGRAM=DCP, DEVICE=TAP~,2311,2314,3330, DEVADDR=nnn, CICSDMP=YES, SUFFIX=program suffix, DUMMY=YES DFHSG PROGRAM=TCP, ACCMETH=(BTAM,BSAM,SAM,BGAM,TCAM), DEVICE=(1403,1404,1442,1443,1445,2311,2314,3330, 2501,2520,2540,CRLP,DASD,DISK,TAPE) , BTAMDEV=(1030,1050,1050D,1053,1130,1130D,2020,2020D, 2260,L2260,2265,2740,2740D,2740-2,2741C,2741E, 2741DC,2741DE,2760,2770,2770D,2780,2780D, 2980/1,2980/2,2980/4,3275,3277,L3277,3284, 202 * * * * * * * * ** * * * ** * * * * * * * * * L3284,3286,L3286,3735D,7770,SYS/3,SYS/3D,SYS/7, SYS/7D,Sj360,S/360D,Sj370,S/370D,TWX,BISYNC), FEATURE=(AUTOANSW,AUTOPOLI,BUFFRECV,PSEUDOEIN), ANSWRBK=(EXIDVER,TERMINAL,AUTOMATIC,7770TERM,7770NULL), INI~RL=YES, LOCKF=YES, WRAFLST=YES, BscoDE=(~]~]!£,!~£!!,1]!]2~Qn~), AUTCTRN=YES, UCTRAN=]Q, (EBCDIC,ASCII) , COMPAT=]Q, (FORMAT,FULLBUF) , FMT2260=(§~~Q,12X40,12X80,15X64), FMT3270= l11~~Q, 24X80) , CMPT60L= (n1 ,n2,n3) , SMI=user character,~, TAB=YES,]Q, CCNVTAE= lA~],A]~) , XATTACH=symbolic name, XOU'IPUT=symbolic name, XINPUT=symbclic name, XTCMIN=symbolic name, XTCMOUT=symbolic name, TCM3270=YES, TCM7770=YES, BMS=YES,!Q, SUFFIX=program suffix * DFHSG PROGRAM=FCP, CONSEC=YES, FILSERV=(INDA,INIS,tAUPD,ISUPD,DAADD,ISADD,INDIRACC, EXCTL,INSEG,OUTSEG,DABLKNG,VLR,HEXAD,tECAD, ACTAD,IVBR,LOCATE,IBBOWSE,DBROWSE), SUFFIX=program suffix, XTYPEEQ=symbolic name, XOU~PUT=symbclic name, XINPUT=symbolic name, XINPUTC=symbolic name, DUMMY=YBS 1]!B~1]N1 ]!1! ~~N1]Q1 R~QQ]!~ * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (TDP) DFHSG PEOGRAM=TDP, INTRA=YES,TRANSINIT, EXTEA= (ACQUISITION, DISPOSITION) , SUFFIX=program suffix, * * * * ** * * DEVICE=~111,2314,3330, XTYPEEQ=symbclic name, XOU~PUT=symbolic name, XINPUT=symbolic name, DUMMY=YES DFHSG PROGBAM=TSP, DEVICE=2111,2314,3330, VIRTUAL=(VIRTUAL,REAI), SUFFIX=program suf£ix, XTYPEEQ=symbolic name, XOU~PUT=symbolic name, XINPUT=symbolic name, * * * * * ** 203 DUMMY=YES DFHSG PROGRAM=CSA, * * WRKAREA=number,21~, SUFFIX=program suffix DFHSG PROGRAM=MTF, TLT=YE.§,NO ~l]A~I£ ~~]]L~1Q'§] R]gg]!~ * (OCP) DFESG PROGRAM=OCP DFHSG PROGRAM=GAP DFHSG PROGRAM=HLL, LANG=(CCBOL,FL/I) , PL1= (O,l) ~]]~INA1 ~]R]NDE]l ~Q~1]Q1 R]Qg]A~ * * (TDCP) DFHSG PROGRAM=DDM DFRSG PROGBAM=ATP, INBUFF=number, OUTBUFF=number 1]]]lNA11 0 N QI ~l~~QQ'§ '§X'§1]~ g]~~]ATIQM DFHSG TYPE=FINAL 204 * * DFHSIT TYPE=CS~£I,DSECT, SUFFIX=xx, TRT=decimal value,Q, SCS=decimal value,200, SP1=decimal value,Q, DVT=2311,2314,3330, MSGLVL=O,l, TSBLK=decImal value,1&25, ICV=decimal value,100Q, ICVS=decimal value,~QQOO, ICVR=decimal value,5000, CDL=decimal'value,5-,--MXT=decimal value,~, TCT=xx, PPT=xx, PCT=xx, FCT=xx,NO, DCT=xx,NO, CSA=xx, KCP=xx, SCP=xx, PCP=xx, DCP=xx,NO, ICP=xx,NO, TCP=xx, FCP=xx, TDP=xx, TRP=xx,NO, PIP=xx, NO, TSP=xx,NO, OSCOR=decimal value,Q, PL1=YES,.!!Q, DL1=YES,.!!Q, PSB=name,CICSPSB, PSBPL=number,4~ DMBPL=number,~, BUFPL=number,g, AT P=YES, !iQ, ATPMT=number,l ATPMB=number,RXI §Eg£ifica!iog ~n~ Qllg, SIMODS=(!~,~l,£l,~~,~J,Ql,~l) or (!~, ~l, Cl , Ql,1!l) * ** * * * * * * ** * * ** * * * * ** * * * * * * ** * * ** ** * * * * * 205 TERM1NA1 cOl!I.BQ1 TAB1] (TCT) DFHTCT TYPE=INITIAL, SUFFIX=xx * DFHTCT TYPE=SDSCI, DEVADDR=SYSnnn, DEVICE=1030,1050,1130,1403,1404,1442,1443,1445, 2020,2260,L2260,2265,2311,2314,2501,2520, 2540,2740,2740/2760,2741C,2741E,2770,2780, 2980,3275,3277,L3277,3284,L3284,3286,L3286, 3330,3735,7770,BSCMDMPT,BSCMDPPT,BSCMDSW,DASD, DISK,SYS/3,SYS/1,S360,TAPE,TW33,TW35,TCAM, DSCNAME=name, * * * * ERROPT=~,R,W,C,N,RW,T, FEATURE=(STC,CHK,BSC,KBL,OIU,SIX,SXW,SIW,RIX, RXW,RIW,MAS,SLV,APL), LINELST=(nnn1, ••• ,nnn31), SWITCH=YES,!Q, CU=2701,2702,2703,2848,3272, CONFIG=PP!,MPT, BSCODE=EB~~!£,ASCII,TRANSCODE, MODELST=(nl, ••• ,n31), RETRY=number,l, TERMTST=YES,NO, LERBADR=symbolic address, DDNAME=name,ggi auli§ lQ DS£NA~], MACRF=(R,W), FLNNAME=name, NCP=number,l, MODE=(,CNTRL,! or B,A or B), BLKSIZE=length, RECFM=F,V,Q, SYNAD=symbolic name, OPTCD=W,WU,WC,wUC, APPENDG=appendage suffix symbol DFHTCT TYPE=LINE, ACCMETH=SAM,BSAM,BTAM,BGAM,TCAM,SEQUENTIAL,GRAPHIC, TELECOMMUNICATION, TRMTYPE=1030,1050,1053,1130,2020,2260,L2260,2265, 2740,2740/2760,2741C,2741E,2770,2780,2980, 3275,3277,L3277,3284,L3284,3286,L3286,3735,7770, SYS/3,SYS/7,S360,CRLP,DASD,TAPE,TWX,U/R, CLASS=(CONV,BATCH,VIDEO,HARDCOPY,BISYNC,AUDIO), DSCNAME=name, ISADSCN=name, OSADSCN=name, INAREAL=length, TRMMODL=number or character, BTAMRLN=number, LISTADR=(name,WRAP), FEATURE=(AUTOANSR,AUTOCALL,AUTOPOLL,CHECKING, SCONTROL,BUFFRECV,KBRDLOCK), NPDELAY=number, POOLADR=symbolic address, ANSWRBK=AUTOMATIC,TERMINAL,NULL,EXIDVER, LINSTAT='OYT OF SERVICE', BSCODE=EBCDI~,ASCII,TRANSCODE, CONVTAB=EBCDIC,ASCII,TRANSCODE,TEXTMODE,ABB,ABC, RDYMSG=symbolic address, ERRMSG=symbolic address, GENPOLL=YES, POOLCNT=number, TCTUAL=number,Q, 206 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * OUTQ=symbolic name, POOL=YES, QUEUEID=hexadecimal number * * symbol DFHTCT TYPE=TERMINAL, * TRMIDNT=name, * TRMPRTY=number,Q, * TRMMODL=number,character, * TRMTYPE=1030,1050,1053,1130,2020,2260,L2260,2265, * 2740,2740/2760,2741C,2741E,2770,2780,2980, * 3275,3277,L3277,3284,L3284,3286,L3286,3735,7770, * SYS/3,SYS/7,S360,CRLP,DASD,TAPE,TWX,U/R, * CLASS=(CONV,BATCH,VIDEO,HARDCOPY,BISYNC,AUDIO), * LVUNIT=number, * LASTTRM=LINE,GACB,POOL, * TRMADDR=address,name, * TRMSTAT=(1RAN~!~TIQli,TRANSCEIVE,RECEIVE,'OUT OF SERVICE',* INPUT) , * COMPAT=NO, (number of characters, number of lines, * device type,model number), * FEATURE=(PTRADAPT,SELCTPEN,AUDALARM,COPY,BUFEXP, * UCTRAN,DCKYBD) , * POLLPOS=number, * TRANSID=name, * STN2980=number, * TAB2980=number,Q, * TIOAL=number, * TCTUAL=number symbol DFHTCT TYPE=7770MSG, MESSAGE='message' * DFHTCT TYPE=FINAL "- .. DFHFCT TYPE=INITIAL, SUFFIX=xx * DFHFCT TYPE=DATASET, DATASET=name, ACCMETH=BDAM,ISAM,DL/I, SERVREQ=(GET,PUT,UPDATE,NEWREC,INDACC,SEGMENT,BROWSE, KEY, NOEXCTL) , BLKKEYL=decimal value, EXTENT=number, CYLOFL=number, INDAREA=symbolic name, INDSIZE=number, INDSKIP=YES, MSTIND=YES, NRECDS=number, IOSIZE=number, IOWORK=symbolic name, DEVICE= (n,m) , (231!!,231!!) , SRCHM=YES,number, VERIFY=YES, RELTYPE=DEC,HEX,BLK, LRECL=(length,length) , BLKSIZE=(length,length), RKP=number, RECFORM=(format,characteristic,DCB record format), OPEN:INITIAb,DEFERRED, KEYLEN=length * * * * * * * * * ** * * * * * * * ** * * * * 207 DFHFCT TYPE=INDACC, OBJDSID=name, IARLKP=number r IALKFL=length, IADADMI=RELRECrKEY, IADIII=hexadecimal character, DUPDSID=name DFHFCT TYPE=SEG~EAD, SEGLENG=length, INDDISP=number, TSEGIND=BIT,DISPLACEMENT * * * * * * * * * DFHFCT TYPE=SEGDEF, SEGNAME=name, SEGCHAR=(format,alignment} , SEGLENG=length * * * DFHFCT TYPE=SEGSET, SEGSET=name, SEGNAME=(name1, ••• ,nameN) * * DFHFCT TYPE=SEGLAST DFHFCT TYPE=FINAL DFHFCT TYPE=LOGICMOD DFHDCT TYPE=INITIAL, SUFFIX=xx, TRNSUFX= (xx, ••• ) , SEPASMB=YES,NO * * * DFHDCT TYPE=SDSCI, DSCNAME=name, MODNAME=name, DEVICE=1403,1404,1443,1445,2311,2314,3330,TAPE, BLKSIZE=length, DEVADDR=symbolic address, RECFORM=lIXUNB,FIXBLK,VARUNB,VARBLK,UNDEFINED, FILABL=STD,l!Q, TYPEFLE=INgUT,OUTPUT,RDBACK, RECSIZE=length, REWIND=UNLOAD,NORWD,LEAVE,REREAD, TPMARK=NO, BUFNO=number,l, ** * * * * * * * * * * * * ERROPT=SKIP,!~l!0R!, SUFFIX=xx DFHDCT TYPE=EXTRA, DSCNAME=name, DESTID=name, OPEN=!l!IT!AL,DEFERRED, RESIDNT=YE,2,NO * * * * DFHDCT TYPE=INTRA, DESTID=name, * * * * * REUSE=~,NO, TRIGLEV=number, DESTFAC=IERMINAL,FILE, TRANSID=name 208 DFHDCT TYPE=INDIRECT, DESTID=name, INDDEST=name * * DFHDCT TYPE=FINAL DFHPCT TYPE=INITIAL, SUFFIX=xx * DFHPCT TYPE=ENTRY, TRANSID=name, TRNPRTY=decimal value,QQ1, TRANSEC=decimal value,OOl, TWASIZE=decimal value,Q, PROGRAM=name, TPURGE=YES,l!Q, SPURGE=YES,!!Q, COMPAT=!!Q,FORMAT,FULLBUF * * ** * * * * DFHPCT TYPE=FINAL DFHPPT TYPE=INITIAL, SUFFIX=xx * DFHPPT TYPE=ENTRY, PROGRAM=name, * ** * PGMLANG=!~SEMB1~E,COBOL,PL/I, RES=YES,l!Q, RELOAD=YES,!!Q "-- DFHPPT TYPE=FINAL SIGN.=ON TAB1~ (S NT) DFHSNT TYPE=INITIAL DFHSNT TYPE=ENTRY, OPNAME='operator name', PASSWRD=password, OPIDENT=operator identification, SCTYKEY=security keY,l, OPPRTY=operator priority,Q * * * * * DFHSNT TYPE=FINAL 1~RMl!!!1 1 IS 1: 1ABLE~ (TLT) DFHTLT TYPE=INITIAL, SUFFIX=xx * DFHTLT TYPE=ENTRY, TRMIDNT=terminal identification * DFHTLT TYPE=FINAL 209 210 DFHOC TYPE=OPEN, DATASET=TRANSDATA,DATABASE,DUMP, LISTADR={register), (symbolic register) ,YES, SYMBADR=symbolic address, DSETID= (name, (xx) , ••• ) , CHECK=symbolic address * DFHOC TYPE=CLOSE, DATASET=TRANSDATA,DATABASE,DUMP, LISTADR={register), (symbolic register) ,YES, SYMBADR=symbolic address, DSETID= (name, ••• ) , CHECK=symbolic address * * * DFHOC TYPE=SWITCH, DATASET=DUMP * * * * * * * This section contains examples of user-written transactions. source coding is written in Assembler language. The The following example of a 1030 transaction: 1. Analyzes the terminal transaction code in the first byte of data. 2. Matches the transaction code with the entry in the Program Control Table (PCT) for the desired transaction. 3. Issues a Program Control XCTL macro instruction for the program name found in the table search. ]ot~: The 1030 transaction must take into account the size of the largest Transaction Work Area (TWA) needed by the program to which control is to be transferred. COpy COpy TCTTEAR EQU COpy TIOABAR EQU COpy PCTCBAR EQU COPY TRAN1030 CSECT ENTRY T1030 EQU BALR USING L L L PCTLOOP END TRANCTL MVC EQU CLC BE LA CLI BNE EQU DFHPC EQU MVC DFHPC END DFHCSADS DFHTCADS 7 DFHTCTTE 6 DFHTIOA 5 DFHPCTDS T1030 * 2,0 *,2 TCTTEAR,TCAFCAAA TIOABAR,TCTTEDA PCTCBAR,CSAPCTBA TIOADBA(80) ,TIOADBA+1 *PCTTI,TIOADBA TRANCTL PCTCBAR,PCTEA PCTTI,X'FF' PCTLOOP * TYPE=RETURN * TCAPCPI,PCTIPIA TYPE=XCTL T1030 COpy CSA SYMBOLIC STRG DEFN COPY TCA SYMBOLIC STRG DEFN TERM CONTROL TABLE ADDRESS REG COPY TCT SYMBOLIC STRG DEFN TERMINAL I/O AREA ADDRESS REG COPY TIOA SYMBOLIC STRG DEFN PROG CONTROL TABLE ADDRESS REG COpy PCT SYMBOLIC STRG DEFN CONTROL SECTION - 1030 INPUT ED 1030 INPUT EDIT ENTRY ADDRESS 1030 INPUT EDIT ENTRY ADDRESS ESTABLISH BASE ADDRESS REGISTER USING REGISTER 2 FOR BASE REG LOAD FACILITY CONTROL ADDRESS LOAD TERMINAL IIO AREA ADDRESS LOAD PROGRAM CONTROL TABLE AD DR SHIFT INPUT DATA ONE BYTE PROGRAM CTL TABLE SEARCH ENTRY COMPARE TRANSACTION IDENT GO TO TRANSFER CONTROL IF EQUAL ADVANCE TO NEXT TABLE ENTRY TEST FOR END OF TABLE CONTINUE SEARCH IF NOT EQUAL END OF TABLE SEARCH ENTRY PROGRAM CONTROL RETURN TRANSFER CONTROL ENTRY MOVE PROGRAM NAME TO TCA PROGRAM CONTROL TRANSFER CONTROL The following example of a 2760 transaction: 1. Analyzes input data that CICS has translated to EBCDIC representation. 211 2. Changes index numbers (11, 12) to frame numbers. 3. Converts horizontal/vertical coordinates received from the 2760 to points ranging from 1 to 252. These points represent screen positions arranged (top to bottom, left to right) on a screen of 21 vertical columns and 12 horizontal rows. 4. Indicates how to detect reserved points on the screen, some of which are built into the hardware and some of which are assigned by the user. 5. Shows a procedure for generating the necessary control (function) information and Move Amount Character codes so that CICS can transmit output data to the 2760. Before output transmission to the 2760 occurs, CICS translates the data to 2740 code. COpy COpy TCTTEAR EQU COpy TIOABAR EQU COpy PCTCBAR EQU COpy REG8 EQU REG9 EQU REG10 EQU REG1S EQU TRAN2760 CSECT ENTRY T2760 EQU BALR USING L L L BAL CLI BE CLI BE CLI BE CLI BE CLI BE CLI BE CLI BE CLI BE CLI BE CLI BE CLI BE CLI BE B FORWARDl EQU MVl 212 DFHCSADS DFHTCADS 7 DFHTCTTE 6 DFHTIOA 5 DFHPCTDS 8 9 10 15 T2760 * 2,0 *,2 TCTTEAR,TCAFCAAA TIOABAR,TCTTEDA PCTCBAR,CSAPCTBA REG10,COMPIHV POINTNO+ 1 ,132 FORWARD1 POINTNO+1,144 FORWARD2 POINTNO+1,156 FORWARD3 POINTNO+l,168 FORWARD4 POINTNO+1,180 FORWARD5 POINTNO+l,240 REVERSE1 POINTNO+l,228 REVERSE2 POINTNO+l,216 REVERSE3 POlNTNO+1,204 REVERSE4 POINTNO+1,192 REVERSES POINTNO+l,245 UNLOAD POINTNO+l,246 LOAD END * FUNCTION,X 1 F1 1 COpy CSA SYMBOLIC STRG DEFN COpy TCA SYMBOLIC STRG DEFN TERM CONTROL TABLE ADDRESS REG COpy TCT SYMBOLIC STRG DEFN TERMINAL I/O AREA ADDRESS REG COPY TIOA SYMBOLIC STRG DEFN PROG CONTROL TABLE ADDRESS REG COPY PCT SYMBOLIC STRG DEFN REGISTER EIGHT REGISTER NINE REGISTER TEN REGISTER FIFTEEN CONTROL SECTION - 2760 INPUT ED 2760 INPUT EDIT ENTRY ADDRESS 2760 INPUT EDIT ENTRY ADDRESS ESTABLISH BASE ADDRESS REGISTER USING REGISTER 2 FOR BASE REG LOAD FACILITY CONTROL ADDRESS LOAD TERMINAL I/O AREA ADDRESS LOAD PROGRAM CONTROL TABLE ADDR LINK TO COMPUTE Il, 12, H, & V FORWARD ONE FORWARD TWO FORWARD THREE FORWARD FOUR FORWARD FIVE REVERSE ONE REVERSE TWO REVERSE THREE REVERSE FOUR REVERSE FIVE UNLOAD LOAD FORWARD, AUTO EOM, MFA DISABLED MVC B FORWARD2 EQU MVI MVC B FORWARD3 EQU MVI MVC B FORWARD4 EQU MVI MVC B FORWARD5 EQU MVI MVC B REVERSE1 EQU MVI MVC B REVERSE2 EQU MVI MVC B REVERSE3 EQU MVI MVC B REVERSE4 EQU MVI MVC B REVERSE5 EQU MVI MVC B LOAD EQU MVI MVC UNLOAD EQU MVI MVC EQU LA STH MVC BAL MVC DFHTC B WR2760 B END COMPIHV EQU DFHPC EQU TR SR IC SLL SR IC AR STH TR ADVANCE,=H'1' WR2760 * FUNCTION,X'F1' ADVANCE,=H'2' WR2760 * FUNCTION, X' F1' ADVANCE#=H' 3' WR2760 * FUNCTION,X'P1' ADVANCE,=H'4' WR2760 * FUNCTION,X'F1' ADVANCE,=H'5' WR2160 *FUNCTION,X'40' ADVANCE,=H'1' WR2160 *FUNCTION,X'40' ADVANCE,=H' 2' WR2160 *FUNCTION,X'40' ADVANCE,=H'3' WR2160 * FORWARD ONE FRAME FORWARD, AUTO EOM, MFA DISABLED FORWARD TWO FRAMES FORWARD, AUTO EOM, MFA DISABLED FORWARD THREE FRAMES FORWARD, AUTO EOM, MFA DISABLED FORWARD FOUR FRAMES FORWARD, AUTO EOM, MFA DISABLED FORWARD FIVE FRAMES REVERSE, AUTO EOM, MFA DISABLED REVERSE ONE FRAME REVERSE, AUTO EOM, MFA DISABLED REVERSE TWO FRAMES REVERSE, AUTO EOM, MFA DISABLED REVERSE THREE FRAMES FUNCTION,X'40' ADVANCE,=H' 4' WR2160 REVERSE, AUTO EOM, MFA DISABLED REVERSE FOUR FRAMES * FUNCTION,X'40' ADVANCE, = H' 5' WR2760 REVERSE, AUTO EOM, MFA DISABLED REVERSE FIVE FRAMES * FUNCTION,X'F1' ADVANCE,=H'8' WR2760 LOAD FORWARD, AUTO EOM, MFA DISABLED FORWARD EIGHT FRAMES * FUNCTION,X'40' ADVANCE,=H'255' UNLOAD REVERSE, AUTO EOM, MFA DISABLED REVERSE 255 FRAMES *REG9,3 REG9,TIOATDL TIOADBA(1),FUNCTION REG10,COMPADV TIOADBA+ 1 (2) , ADVA NCE TYPE= (WRITE,OIU) END * TYPE=RETURN * TIOADBA+2(2),TRTBL REG9,REG9 REG9,TIOADBA+2 REG9,5 REG8,REG8 REG8,TIOADBA+3 REG8,REG9 REG8,FRAMENO TIOADBA+4(2),TRTBL LINK TO COMPUTE FRAME ADVANCE END OF TABLE SEARCH ENTRY PROGRAM CONTROL RETURN COMPUTE 11, 12, HORIZ, AND VERT TRANSLATE 2 CHARS 11 AND 12 CLEAR REGISTER NINE PLACE 11 IN REGISTER NINE MULTIPLY 11 BY 32 CLEAR REGISTER EIGHT PLACE 12 IN REGISTER EIGHT SUM OF I1X32 AND 12 IN REG 8 STORE 2760 FRAME NUMBER TRANSLATE 2 CHARS VERT & HORIZ 213 SR IC MH LR SR IC AR LA SR STH BR FRAMENO DC POINTNO DC TRTBL DC DC DC DC DC DC DC DC DC DC DC DC DC DC DC DC COMPADV DS LH SR LA DR STC STC TR BR FUNCTION DC ADVANCE DS LCXTRTBL DC DC END ~!AMg1~ QI ! REG8,REG8 CLEAR REGISTER EIGHT REG8,TIOADBA+5 PLACE HORIZONTAL IN REGISTER 8 REG8,=H'12' MULTIPLY HORIZONTAL BY TWELVE REG9,REG8 12H RESULT IN REGISTER NINE REG8,REG8 CLEAR REGISTER EIGHT REG8,TIOADBA+4 PLACE VERTICAL IN REGISTER 8 REG9,REG8 12H + V RESULT IN REGISTER NINE REG8,255 LOAD 255 IN REGISTER EIGHT 255-12H-V RESULT IN REGISTER 8 REG8,REG9 REG8,POINTNO STORE 2760 POINT NUMBER REG10 COMPUTE 11, I2, H, AND V EXIT H'O' 2760 FRAME NUMBER H'O' 2760 POINT NUMBER X'FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF' X'FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF' X'FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF' X'FFFFFPPFFFFFFFFFFFFFFFFFFFFFFFFF' X'OOFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF' X'03FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF' X'0205FFFFFFFFFFFFFFFFFFFFFFFFFFFF' X'FFFFFFFFFFFFFFFFFFFFFFFF01FFFFFF' X'FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF' X'FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF' X'FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF' X'FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF' X'FF070BOF13171B1FFFFFFFFFFFFFFFFF' X'FF060AOE12161A1EFFFFFFFFFFFFFFFF' X'FFFF090D1115191DFFFFFFFFFFFFFFFF' X'FF04080C1014181CFFFFFFFFFFFFFFFF' OH COMPUTE MANUAL FRAME ADVANCE REG9,ADVANCE LOAD 2760 MANUAL FRAME ADVANCE REG8,REG8 CLEAR REGISTER EIGHT REG15,32 LOAD DIVISOR OF 32 REG8,REG15 DIVIDE FRAME ADVANCE BY 32 REG9,ADVANCE STORE SECOND BYTE OF ADVANCE REG8,ADVANCE+1 STORE FIRST BYTE OF ADVANCE ADVANCE(2},LCXTRTBL TRANSLATE MANUAL FRAME ADVANCE REG10 COMPUTE FRAME ADVANCE EXIT X'OO' 2760 FUNCTION H'O' 2760 MANUAL FRAME ADVANCE X'407C6050F1619181F2A29282F3A39383' X'F4A49484F5A59585F6A69686F7A79787' T2760 373 2 lR~ACTIQN (Not applicable to CICS/DOS-ENTRY) The following example of a 3735 transaction: 1. Reads data from the 3735 and spools to an extrapartition data set. 2. Upon receipt of the end-of-file condition, writes an FDP header record, FDP records, an FDP trailer record, and data. 3. Sends a powerdown message. 4. Disconnects the line. COpy COpy COpy COpy COpy 214 DFHCSADS DFHTCADS DFHTCTTE DFHTIOA DFHTDIA COMMON SYSTEM AREA DSECT TASK CONTROL AREA DSECT TERMINAL CONT TABLE DSECT TERMINAL I/O AREA DSECT TRANSIENT DATA I/O AREA DSECT 'IC'ITEAR TIOAEAR TDIAEAR EASEREG WORK REG BLOOP HEADER WLCOFF TRAILER WLCOFD FINISH FORTY BLKLGTH HREC TREC FWRDiN EQU EQU EQU EQU EQU CSECT BALR USING L L DFHTC EQU DFHTD 3 4 5 6 7 TC~TE BASE REGISTER TIOA BASE REGISTER TDIA BASE REGISTER PRCGRAM BASE REGISTER WORK REGISTER BASEREG,O LeAD PROGRAM BASE REGISTER *,EASEREG TCITEAR,TCAFCAAA ADDRESSABILITY TO TERM CONT TBL TIOAEAR,TCTTEDA ADDRESSABILITY TO TERM I/O AREA EOF=HEADER TEST FOR END-OF-FIIE CONDI~ION * BATCH READ LOOP TYPE=PUT, WRITE DATA RECORD DESTID=OUTQ, TO OUTPUT QUEUE TtADDR=TIOAtBA DATA IS IN TIOA DFHTC TYPE=GET, READ NEXT RECORD ECF=HEADER AND TEST FOR END-OF-FILE L IIOAEAR,TCTTEDA AtDRESSABILITY TO TIOA B RLOOP LOOP EQU * WRITE FDP HEADER RECORD L TIOAEAR,TCTTEDA ADDR~SSABILITY TO TIOA MVC 'IIOATDL(7),HREC MOVE HEADER RECORD TO TIOA ST TIOABAR,TCTTEDA SPECIFY TIOA ADDRESS DFHTC TYPE=(PUT,SAVE) WRITE TO 3735, SAVE TIOA EQU * BATCH FDP WRITE LCOP DFHTD TYPE=GET, GET FDP RECORD DESTID=FDPQ, FRCM FDP QUEUE QUEZEFO=TRAILER SEND TRAILER WHEN DONE L TtIABAR,TCATDAA ADDRESSABILITY TO DATA MVC TIOADBA(240),0(TDIAEAR) MOVE tATA MVC TIOADBA+240 (236) ,240 (TDIABAR) TO TIOA MVC 'IIOATtL,BIKLGTH SET LENGTH FOR WRITE ST TIOAEAR,TCTTEDA SPECIFY TIOA ADDRESS DFHTC TYPE=(PUT,SAVE,NOTRANSLATE) WRITE TO 3735 B WLCOPF LOOP EQU * WRITE FDP TRAILER RECORD MVC TIOATDL(7) ,TREC MOVE TRAILER RECORD TO TIOA ST TIOAEAR,TCTTEDA SPECIFY TIOA ADDRESS DFHTC TYPE=(PUT,SAVE) WRITE TO 3735, SAVE TIOA EQU * BATCH DATA WRITE LOOP DFHTD TYPE=GET, GET DATA DESTID=DATQ, FROM DATA QUEUE QUEZERO=FINISH EXIT WHEN DONE L TDIABAR,TCATDAA ADDRESSABILITY TO DATA MVC TIOADBA (240) ,0 (TDIABAR) MOVE DATA MVC TIOADBA+240 (236) ,240 (TDIABAR) TO TIOA MVC IIOATDL,BlKLGTH SET LENGTH FOR WRITE ST TIOAEAR,TCTTEDA SPECIFY TIOA ADDRESS DFHTC TYPE=(PUT,SAVE) WRITE TO 3735, SAVE TIOA E WLCOPD LOOP EQU * END UP MVC TIOATDL(7),PWRDWN MOVE POWER DOWN MESSAGE TO TIOA DFHTC 'IYPE=PUT SEND POWEE DOWN MESSAGE DFHTC TYP~=DISC DISCONNECT LINE REQUEST DFHPC TYPE=RETUEN EXI~ EC H'40' DC H'476' DC H' 3' DC C' NULL F NULL X'OCC600' DC DC H'3' DC C' NULL E NULL DC X' 00C500' DC H' 3' DC C' 215 * * * * * * * tc LTORG :END 216 X'OOD700' POWER DOWN MESSAGE INDE~. This index has been prepared by an automated indexing program. Your comments and suggestions will be apprecia ted. The intent is to list primary pago references first. ASSEMBLER END CARD 44 ASSEMBLER END STATEIIENT 13,91,100,117,106,109,113,115 ASSEMBLER F 20 ASSEMBLE R H 20 ASSEMBLER LANGUAGE 13,118,200,211 ASSEMBLER LANGUAGE APPLICATION PROGRAM 158 ASSEMBLER NAME 19-20,13,201 FIRST THREE CHARACTERS OF THE 20 ASSEMBLER PROGRAM 48 ASSEMBLY 20,22,46-41,71 ATDI 171 ATP 14,16-17,19,22,44,53,204,146,156,49,201 205 ATP TASKS VALUE MAXIMUII NUMBER OF 153 ATPMT 53,49,205 ATPMT OPERAND 53 ATTACH 140-141 ATTRIBUTE BYTE 135-136 ATTRIBUTE POSITION AUDALARM 131,55,70,189,207 AUDIBLE ALARM 132 AUDIBLE ALARM FEATURE 74 AUDIO 62- 63,54-55,10,12,206-207 AUDIO RESPONSE DEVICE LV UNIT 72 AUDIO RESPONSE UNIT UNDER CICS/DOS 179,182 AUDIO RESPONSE UNIT UNDER CICS/OS 179,181 AUTOANSR 196,181-183,54,62,67,81),1811,186-188,206 AUTOANSW 32,34,15,203 AUTOCALL 137,196-197,54,62,67,80,184,188,206 AUTOMATIC 67,54,62,206 AUTOMATIC POLLING FEATURE 34 AUTOMATIC TASK INITIATION 98-99,144,154 AUTOPOLL 67,32,34,15,54,56,62,164,203,206 AVAILABLE TCTTE 144 -A- AACA 169 ABB 32,37,181-183,15,54,62,68,203,206 ABB CODE 68 ABB SPECIFIES CONVERSION 36 ABB TRANSMISSION CODE 36 ABC 32,37,15,54,62,68,203,206 ABC CODE 68 ABC SPECIFIES CONVERSION 36 ABC TRANSMISSION CODE 36 ABEND 173-174,129,146,192 ABENC CODE 169,171 ABEND CODE INDICATES 169 ABEND TASK 128 169 ABNORMAL CONDITION INVALID ERROR CODE ABNORMAL CONDITION LINE ENTRY DIAGRAM OF THE TERMIN AL 123 ABNORMAL CONDITION PROGRAM 23,162,177,176 ABNORMAL TERIIINATION COMPLETE DATE 156 ABORT 173-174 ABORT TERIIINAL WRITE REQUESTS 126 ACB'S 46 ACCESS 88,113,120-121,1,9,99,114 ACCESS DL/I ACCESS IIETHOD 6,32,63,82,199 ACCESSED UNDER CICS/OS 82 ACCMETH 82-84,32-33,37,196,24,62-63,66,182-183 191,79-80,189,15,54,81,92,179-181,184-185 186-189,202,206-207 ACCTID 19-20,14,201 ACQUISITION 39,15,203 ACQUISITION INDICATES INPUT 40 ACTAD 38,15,203 ACTION 140-143,124,153,171 ACTION QUEUE PURGE DYNAIIIC OPEN/CLOSE 17 ACTION SET 121-122 ACTIVE CICS TRANSACTION MODE OF THE 172 ACTIVE TASKS SINCE NO TCTTE 145 ACTUAL DESTINATION ADD 91 ADD DAl 6 38 ADD ISAM 7 ADDITIONAL ISAM LOGIC 1I0DULE 91 ADDITIONAL SENSEG STATEIIENT 45 50 ADDITIONAL SYSTEM INITIALIZATION /lODULES ADDR 192-193 ADDRESS ERROR BYTE PLUS THREE-BYTE 160 SYrlBOLIC 54,206,62,95-96,159,210,56,68,94,159,161 SYMBOLIC 208 ADDRESS DFHOC TYPE SYMBOLIC 159,210 ADDRESSABILITY 215,118,128 ADMINISTRATIVE TERIIINAL FACILITIES DESCRIBED 152 AICA 169 AKCA 169 ALIGNIIENT 89-90,81,208 ALTERNATE DUMP DATA SET 11-12,162,153 ALTERNATE STATION ADDRESS 75-76 AMERICAN STANDARD CODE 59,68 ANALYSIS DFHTDP 119 ANS COBOL 4,28,200 ANS COBOL VERSION 2 COIIPILER 28 ANS COBOL VERSION 3 COMPILER 28 ANS COBOL VERSION 4 COMPILER 28 ANSIIRBK 32-34,57,59,62,66,73,137,181-183,67-68 15,54,80,184,186-188,197,203,206 APAR NO. Pl0780 21,41 APCI 170 APIA 170 APL 56,58,54,206 APPENDAGE SUFFIX SYMBOL DFHTCT TYPE 54,206 APPENDAGE 7770 SVC APPENDAGE END 18 APPENDG 56,61,54,181,206 APPENDG OPERAND 24 APPENDIX 93,97-99,106-107,110 NONE 74 175 APPENDIX B 77-78,179 APPENDIX C 190 APPENDIX E 199 APPENDIX F 200 APPENDIX G 75 APPLICAT ION INPUT DISCUSSION OF THE OPTCD OPERAND OF THE 143 138,171-17 3,19,22,130,35,43,81, APPLICATION PROGBAM 133,135,139,142 USER-IlRITTEN 1,8,76,130 APPLICATION PROGRAM RESTARTS 151 APPLICATION PROGRAII 1I0RK AREA H9 APPLICATION PROGRAIIS THAT CURRENTLY TEST 74,132 APPLICATION UNDER TCAII 137 AREA 124,127,11,24,85,143 AREAS 1024-BYTE 21 1116,3,5,7,21,25,36,45,58,77,82,90 92, 100,105,108,111,114,121,132-133,135-136,139 H2, 144, 151, 190, 194, 199 ASCII 32-33,35,54,62,66,206,15,56- 57,68,203 ASIIBLR 19-20,13,201 ASSEMBLER 109,13,108,209 ASSEMBLER B 0 149 ASSEMBLER B 4 149 ASSEMBLER 0 USE OF 72 -B- BASE NAME 114,48 BASE REGISTER 128,117-118,121 BASIC ERROR RECOVERY PROCEDURES 57 BASIC MAPPING SUPPORT PROGRAM 177 BASIC SEQUENTIAL ACCESS IIETHOD 32 BASIC TELECOMIIUNICATIONS ACCESS IIETHOD 32,66 BATCH 62-63,54-55,70,72,206-207,3,152,215 BATCH IMS JOB 9 BATCH IIIS/360 PROGRAIIS EXECUTING 45 BATCH TRANSACTION IIAKES PROPER USE 174 BDAM 82-84,199,81,92,86,201 BCAII DATA SET 85 BGAM 62-63,65,32,12,131,196,15,54,189,202,206 BINARY 63-64,12,16,51-60,68,127,179 BINARY CODED DECIl'JAL INTERCHANGE CODE 59 BISAI! 45 BISYNC 32,54-55,62-63,70,12,206-201,15,203 BISYNC BINARY 33 BISYNC PARAIIETER INCLUDES 1130 34 BISYNC 2 34 BISYNCH DEVICES 61 BLK 86,81,83,201 BLKKEYL 86,82,84,81,199,201 BLKKEYL OPERAND 81 BLKKEYL VALUE 86 BLKSIZE 56,60,86,102-104,190-191,95-96,54,81,83 92,94,182,206-208 BLKSIZE BYTES 9-16 160 BLKSIZE PLUS BLKKEYL 199 BLKSIZE VALUE 86 BLOCK 84-86,60,96-91 BLOCK SIZE 44 BLOCKED 87 BLOCKED BDAII DATA SET 88 BLOCKING FACTOR 86,84 BLOCKS NUIIBER OF 1024-BYTE 52 1024-BYTE 52 BLOCKS FEATURE OF DL/I PRE-BUILT 46 BLOCKSIZE 86,64 BIIS 32,31,15,203 BNE 128 BR 14 !NSTRUCTION 119 BROIlSE OPERANDS 86 BSAII 62-63,65-66,32-33,137,196,15,54,124,188 202,206 BSAII DATA SET CONTROL NAIIE 64 BSAII STATUS 124 BSAM STATUS 44 126 BSCIIDIIPT 56,54,184-185,206 BSCMDPPT 56,54,206 BSCIIDSIl 56,54,181,206 BSCODE 32-33,35,56-57,59,68,54,186-188,206,15 62,184-185,203 BSCODE OPERAND BTAII 163,166-168,62-64,66,32-33,31,24,59,120 131,196,182-183,80,15,54,79,124,179-181,184 185-187,189,202,206 BTAII DEVICE TYPES 33 BTAM DEVICES 11,13 POLLI NG OF 154 BTAM DFTRIILST IIUST LABEL OF THE 13 BTAII ENVIRONIIENT 138 BTAII I/O ERRORS 166 BTAM INPUT ONLY 162,164 BTAM LINE ERROR LABEL OF THE 60 BTA II LINE GROUPS DEFAULTS 60 BTAII LOCAL LINE GIiOUP 69 BTAII IIANUAL 66 BTAII NON-SIlITCHED LINE 12 BTAII OUTPUT ONLY 163 217 88,157,160,185,189,194,199 GENERATION OF 13 CICS/DOS ENVIRONIIENT 11 CICS/DOS EXTENT CARD 96 CICS/DOS LINKAGE EDITOR 13,95 GENERATION OF THE 19 CICS/DOS OPERATIONS GUIDE 91 13 CICS/DOS REAL-TIllE RELOCATABL.E PROGRAM LIBRARY CICS/DOS REAL-TIllE SYSTEM 13 CICS/DOS SYSTEM DATA SETS RESIDE 50 CICS/DOS SYSTEII GENERATION NUIIBER TERIIINATION OF 20ll TERIIINATION OF lIli CICS/DOS SYSTEMS 56-60,83-85,19-21,23-24,31, 3l1-35, 50 CICS/DOS-ENTRY 53,68,137,169,187,214 CICS/DOS-ENTRY SYSTEII 26-27,50-51,6,38,41,53,109,154,162 CICS/DOS-STANDARD 53,6,109,196 CICS/DOS-STANDARD SYSTEM 6,22,41,53 CICS/OS 57-61,95-96,77-78,160,20,62,65,69,5 19,51,82,86,88,100,122,189,194,199 GENERATION OF 13 USER OF 86-87 CICS/OS APPLICATION PROGRAIIS OPTIONAL ACCESS 45 CICS/OS DATA LANGUAGE/I FACILITIES GENERATION OF 22,45 CICS/OS ENVIRONIIENT 11 CICS/OS ISAII DATA SETS 87 CICS/OS OPERATIONS GUIDE 39,46 CICS/OS STANDARD SYSTEII 21,24 CICS/OS STANDARD VERSION 2.3 41 CICS/OS SYSTEII 32,37,83,85,19,42-43,56,69,72,88 CICS/OS VERSION 1 19 CICS/OS VERSION 1 USERS 22,24 CICS/OS VERSION 2 19 CICS/OS 3 194 CICS/OS-STANDARD 22 20-22,57-58,60-61,52-53,24, CICS/OS-STANDARD SYSTEM 6,35,43,51,85,109,129 CICS/OS-STANDARD VERSION 1 USER 129 CICS/OS-STANDARD V1 5 CICS/OS-STANDARD V1 COIIPATIBILITY 33 CICS/OS-STANDARD V2 5 CICS/TCAII ABEND/RESTART 151 CICS/TCAM INTERFACE 145-146,138-139,147-148,150-151 CICS/TCAM INTERF ACE CONSIDERATIONS 37,69,137 CICS/TCAII INTERFACE ENABLES CICS 137 CICS/TCAM INTERF ACE IIIPLEIIENTATION 143 CICS/TCAM INTERFACE SUPPORTS 143 CICS/TCAM PROGRAM INTERRELATIONSHIP 190 CICS/TCAM STARTUP 150 151 CICS/TCAM TERIIINATION CICSGEN 20,201 CLASS 19,21,54-55,62-63,70,72,206-207,14,189 CLOSE 161-162,158-159,153,192,210 CLOSE DATA SETS 161,11 CLOSE ERROR 20 161 CNTRL 56,54,206 COBOL 28,43,108,14,16,18,202,109-110,204,209 COBOL DFHPPT TYPE 110 CODED DECIMAL INTERCHANGE CODE 2 68 CODES CODING 79-80,92-93,107,110,113,90,93,115,179 CODING DFHSG TYPE 45 COMMON CARRIER TELETYPEliRITER EXCHANGE TERMINAL 33,179,184 COMMON SYSTEM AREA 42,156 EXTENSION OF THE 5 COMMON SYSTEM AR EA KCP 51 COMMON TCTTE'S POOL OF 139 COMMON 1I0RK AREA OPTIONAL USER-DEFINED 5 COMMUNICATE 68,61,76,108 COMMUNICATION LINES 34,65-66,68,71 COMMUNICATION TERMINAL/2760 OPTICAL IMAGE UNIT 180 COMPAT 32,35-36,106,70,74,185,15,55,105,131,177 189,203,207,209 COMPAT OPERAND SINGLE USE OF THE 36 USE OF THE 74 COMPAT OPERANDS 148 COMPATIBILITY MODE 136,131 COMPATIBILITY OPERATION FULLBUF MODES OF 106 TIiO MODES OF 36,130 COMPATIBILITY TRANSACTION 136 CONFIG 56,59,54,186-187,206 CONSEC 26,14-15,38,201,203 CONSECUTIVE I/O NUl1BER OF 26 CONSECUTIVE I/O EVENTS NUl1BER OF 38 CONSOLE OPERATOR 157 CONTINUE RESPONSE 151 CONTROL DUMMY CONTROL PROGR DUMP 17 CONTROL PROGR FILE 17 CONTROL PROGR ABNORI!AL CONDITION 17 CONTROL PROGR CICS DUMMY CSA 17 CONTROL PROGR COM!!ON SYSTEI! AREA 17 CONTROL PROGR DUMP UTILITY 17 CCNTROL PROGR PROGRAM INTERRUPT 17 CONTROL PROGR SY STEM SERVICE PROGRAl1S 17 17 CCNTROL PROGR TABLE 1 CONTROL PROGR TEMPORARY STORAGE 17 CONTROL PROGR TRANSIENT DATA DUMMY 17 CONTROL PROGRAM GENERATED AS PART OF THE FILE 26 CONTROL SECTION 211-212,82,105,108,111,114 CONTROL SYSTEM DUMl1Y GROUP 25 CONTROL SYSTEM MANAGEMENT PROGRAMS 26 CONTROL SYSTEM MESSAGES 162 CONTROL SYSTEM OPERATIONAL GROUP 23,201 CONTROL SYSTEM SERVICE GROUP 24 CONTROL SYSTEM UTILITY GROUP 25 CONTROL UNIT 56,59,123,126,173 BTAM READ/WRITE RETURN CODE 164 BTAM RETURN CODE 121, 163-16l1, 122 BTAM SIiITCHED-LINE PROCESSING 73 BTAM-EXPANDED ID VERIFICATION 68 BTAMDEV 32-34,37,211,15,57,137,202 BTAMDEV OPERAND 34 BTAMDEV 2 32 BUFEXP 131,55,70,207 BUFEXP PARAMETER INCREASES 74 BUFFRECV 67,32,34,15,54,62,203,206 BUFNO 102-103,S5-96,94,208 BUFPL 52,lI5,49,205 BUILT 159-160,46,112,212 -C- CAA 23-2l1,14,201 CAA OPERANDS 23 CAAUTIPL 130 CALL'S INDICATE lIHAT TYPE OF 45 CARD READER 57,60,63,72 165-166 CARRIER CONTROL CHARACTERS CATP STOP 156 CDL 49,51,205 CHANNEL END/ABNORMAL END APPENDAGE ROUTINE 2l1,61 CHECK 85,141,159,161,210,128,161,163 CHECK OPERANDS 161 CHECKING FEATURE 57-58 CHK 56,58,54,79,180,206 CICS 178,190,201 ABNORMAL TERMINATION OF 151 ACCESSED DURING EXECUTION OF 52 ACTIVATE 11 AUTOMATIC TASK INITIATION FEATURE OF CICS OPTIONS DURING GENERATION OF lI5 DUMP MANAGEMENT FACILITY OF 11 FILE CONTROL FACILITI ES OF 130 GENERATION OF 13,18,176 INITIALIZATION OF 48 NAMES OF 22 NEll RELEASES OF 116 OPERATION OF 110 OS SUBTASK OF 9 REAL-TIME EXECUTION OF 24,155,158 USER OF 111,113,154 CICS APPLICATION PROGRAM 61,138,151 CICS ATTACHES TIOA 142 CICS CATALOGED PROCEDURES 19 CICS CHECKING 150 CICS CONFIGURATION 52 CICS COllTROL BLOCKS 138-139 CICS CONTROL TABLES 176 CICS DFHTCT TYPE 132,139 CICS DUlU' UTILITY PROGRAM 7 155,158 CICS DYNAMIC OPEN/CLOSE FACILITY ALLOIiS CICS DYNAdIC OPEN/CLOSE PROGRAM 103-1011 CICS EXECUTION COURSE OF 162 CICS EXECUTION DECK 24 CICS FILE MANAGEMENT 82 CICS FUNCTIONS CHOICE OF 10 CICS MACRO INSTRUCTIONS FOLLOWING LISTING OF 200 CICS MANAGEMENT FUNCTIONS 116 CICS MANAGEMENT PROGRAMS 39,116-118,37,40-lI2,10,27 30,5,13,27 ,28,1l18,1 0 CICS MASTER TERMINAL SIiITCH FUNCTION 11 CICS NUCLEUS 51 52,83,93 CICS PARTITION/REGION CICS PROGRAMS 6 ASSEMBLY OF 22 LINK EDIT OF 22 CICS SCREEN CONTROL IIACRO IN STRUCTIONS 1117 CICS STORAGE 12-BYTE 149 CICS SYNAD 61 CICS SYSTEM DATA SETS 22 CICS SYSTEII INITIALIZATION COMPLETING 150 CICS SYSTEM INITIALIZATION PROGRAM 6,156 CICS TABLE PREPARATION 131 CICS TASK 67 CICS TASK ISSUES 67 CICS TERMINAL 1l15-146 CICS TERMINAL CONTROL PROGRAII 1lI6 CICS TERIIINAL CONTROL TABLE 77,145,179,190 EXAIIPLE OF A 190 CICS TERIIINAL CONTROL TABLE CONTAINS 138 CICS TERMINAL ERROR HANDLING STRUCTURE 120 CICS TERMINAL ERROR PROGRAII 138 EXPANSION OF THE 143 CICS TERMINAL INPUT/OUTPUT AREA 1l19-150 CICS TERMINAL OPERATOR GUIDE 106,110 CICS TIOA 140 CICS TRACE FUNCTION 154,153 CICS TRACE TABLE 50 CICS TRANSACTION 136 CICS TRANSACTION ROLLOUT DA'rA SET 50 CICS TRANSIENT DATA CONTROL FACILITY 162 CICS USER EXITS 148 CICS USES FOUR-BYTE TERMINAL ID'S 149 CICS UTILITY PROGRAM 1 CICS 2260 COIIPATIBILITY 132,135 CICS. LOADLIB 22 CICS-DL/I INITIALIZATION 45 CICS-DL/I INTERFACE 52,45-46 CICS-DL/I INTERF ACE 1I0DULES LINK EDIT OF THE 22 CICS-DL/I INTERF ACE USES lI6 CICS-PROVIDED PROGRAMS CICS-PROVIDED UTILITY PROGRAM 11 CICS-TO-TCAM COIIMUNICATION BYTE ALL SOH 148 218 3211 66,14 CONTROL UNIT 31 REMOTE 3211 33 CONTROL UNIT 33 REMOT'! 3211 33 CONT ROL VALUE 66 CONV 62-63,54-55,70,12,206-201 Y CONVTAB 32-33,35-31,181-183,15,54,57,62,68,203 206 CONVTAB OPERAND SINGLE USE OF THE 36 COORDINATING MCP 151 COPY CSA SYMBOLIC STRG DEFN 211 COPY DPHXXEXT STATEMENT 111 COPY FEATURE 74,132,111 CREATE SUPERSET ISAM LOGIC MODULE 91 CREATING USER EXITS 39,37,40-42,27,30,28,148 CRLP 62-63,70,72,32,54-55,188,206-207,15,202 CSA 42,16-11,117,204,5,26,38,156,49,205 COMMON WORK AREA PORTION OF THE 42 CS ACTODB 156 CSAJYDP 156 CSAKCCDL 26,38 CSAOSRSA 111 CSAOSRSA BALR 4,0 111 CSAPCTBA 211-212 CSATADJT 156 CSD 11,25,201 CSD CONTROL SYSTEM UTILITY GROUP 201 CSD MACRO INSTRUCTION 30-31,39-40,42,18,25 CSECT 49-50,205 CSML 116 CSML EXPLANATION 174 CSMT 177,11,176,107,155 CSMT EXPLANATION 162-169,111-114 CSMT FILE SERVICE 1'UNCTIONS 38 CSO 14,11,23,2Dl,21,151 CSO MACRO INSTRUCTION 61,18 CSOT 177 CSS 17,24,201 CSS1' 171 CSSL 158,116 CSSN 117,107 CSST 171,107 CSTA 107,157,177 CSTT 177 CSU 14,17,25,201 CSXX 177 CTLCHAR 148 CU 56,59,79,54,80,179-181,184,186-189,206 CURRENT DATE 156 CURRENT DUMP DATA SET 162 CURRENT RECORD 145 CURRENTLY OPERATIONAL 2260-BASED TRANSACTIONS 35,130 CUSHION 154 CWA 5 CWTR 118 CYL01'L 82,84,81,207 DAUPD 38,15,203 DAY CICS TIME OF 157 OPERATING SYSTEM TIME OF 157 SPECIFIED TIME OF 30 TIME OF 156-157,178,1 DAY CONTROL TIME OF 156 DBD'S 46,82 DBROWSE 38,15,203 DCB 86-87,61,160-161,82,95,138-139,192-193.165,181 DCB RECORD FORMAT 81,83,207 DCB VALUE 86 DCBNAME 95 DCP 15,17,31,202,49,205 DCP MACRO INSTRUCTION 31 OCT 93,102,104,49,51,100,162,171,40,116,118,205,208 OCT ASSEMBLY 160 OCT ENTRY ADDRESS OF 119 DO 60-61,44,96,72,102-103 DO CARD 138,164 DDIR 46,22 DDNAME 56,60,138,95,160,190-192,511,186-181,206 DEBLOCKING TECHNIQUE 88 DEC 124-125,86,81,83,201 DECAD 38,15,203 DECB 61,120-121,1211 DECIMAL VALUE 49-51,105.53.82,84,81,201 DE1'AULT VALUE 67,21,53.14,71,96,131 DESCRIPTIOli 7170 AUDIO RESPONSE UNIT 71 DEST 1113,193,1112 DESTFAC 98-99,94.101,208 DESTID 102-104,93-911,101,176,208-209,215,97-99 DESTID OPERAND 161 DESTINATION 98-99.91,160,101,1112-1113,1115 ULTIMATE 98-99 DESTINATION CONTROL TABLE 93-94,100,110,71,911,109,162,176,103-1011 DESTINATION CONTROL TABLE BE1'ORE DESTINATION CONTROL TABLE CSA 51 DESTINATION CONTROL TABLE EXAMPLES 100 DESTINATION CONTROL TABLE MACRO INSTRUCTIONS 93 DESTINATION CONTROL TABLE USING 99 DESTINATION CSMT 169,127 DESTINATION FIELD EIGHT-BYTE 149,61 DESTINATION IDENTIFICATION 160,71,149 DETECTING PROGRAM 169 DEVADDR 31,102-104,56-51,79,95-96,188,15,54,911 101,202,206,208 DEVADDR VALUE 31 DEVICE ADDRESS 31,13,122,171 DEVICE DEPENDENT CONSIDERATIONS 143 DEVICE-DEPENDENT OUTPUT PROGRAM 17 8 DEVICE-DEPENDENT 2260 DATA STREAMS 711,132 D1'H 200 DFHACP 162,169,17,23,116-111 D1'HAQP 17,411.176-177 DFHASMV2 22,201 DFHATP 53,169,44.17,116-177 DFHAUPLK 22.201 DFHBMSMM 37,11,177 D1'HCAA70 18,23 D1'HCSA 17,51 DFHCSADS 211-212,214,111 .Dl'HDCP 17,51 DFHDCPDY 11 D1'HDCSA 17,52 Dl'HDCT 93-94,51,911 D1'HDCT MACRO 80 DFHDCT MACRO INSTRUCTION DFHDCT TYPE 97,93-911,98-99,116,95,102-103,208,100-101 DFHDCT22 103 Dl'HDEB10 18.23 DFHDLA 18,23 Dl'HDLDBD 46 DFHDLDBD TYPE 111 D1'HDLE 18,23 D1'HDLI 18,23 D1'HDLIDY 18,23 DFHDLPSB PSB 46 D1'HDLPSB TYPE 116 Dl'HDLQ 18,23,46 D1'HDMPA 7,155 D1'HDMPB 7,155 D1'HDUP 11,17,25 D1'HFCP 17,51,10 DFH1'CPDY 17 D1'HFCPXX 119 DFHFCT 51,82 D1'H1'CT MACRO 811 D1'H1'CT MACRO INSTRUCTION 80':81 DFHFCT TYPE 83,90,87-89,91,81-82,199,93,201-208,90 91-92 SERVREQ OPERAND 01' THE 88 D1'HFCTXX DESTINATION CONTROL TABLE 118 D1'H1'EP 17,25,176-171 D1'HGAP 17 D1'HIC MACRO INSTRUCTION 30 DFHICP 10,17,51 D1'HICPDY 17 D1'HKCP 10,17,51,119 D1'HKCPB1 TASK CONTROL MODULE 51 DFHLINK 19,21,6,95,13 GENERATION OF 19 D1'HLNKV2 22,201 D1'H!!TP 11,177 D1'HMTPA 176,17,177 D1'HMTPA D1'HPCT TYPE 107 D1'HMTPA D1'HPPT TYPE 110 D1'H!!TPB 11 DFHNPL 19 D1'HOC 158 DFHOC MACRO INSTRtJCTION 158 EXPANSION OF THE 161 -0- DAM 38,85-87,7-8 DAM DATA SETS 83-84,86,8 DAM PIX ED-LENGTH DATA SETS 86 DAM KEYED DATA SETS 85 DASD 62-63,32,56,54-55,206-201,70,72,15,79 188,202 DATA AREA PRI~E 84-85,9 DATA BASE BUFFER POOL SI ZE 52 DATA BASE CONSIDERATIONS 8,86,88 DATA BASE DESCRIPTIONS 46 DURING GENERATION OF IMS 82 DATA BASE STATISTICS PROGRAM 178 DATA BASE SYSTEM 2,9 DATA BASES 3,2,5.7,52,82 ADDRESS OF 119 DATA CHECK 166-167,58 DATA DEFINITION 60-61,96 DATA DESTINATION CSSL AS VARIABLE-LENGTH 151 DATA ENTRY KEY 36,131,134 DATA EVENT CONTROL BLOCK 61 DATA EXTENT CONTROL BLOCK 120 DATA FIELDS 87,134 DATA FORMAT 140 DATA LANGUAGE/I 2.9,22,45 DATA MANAGEMENT BLOCK 52 DATA MANAGEMENT BLOCK DIRECTORY 22 DATA MAN AGEMENT MACRO INSTRUCTIONS 60,97 DATA MANAGEMENT STATISTICS PROGRAM 23 DATA QUEUE 215 DATA RECORD 145,99 DATA SET DATA BASE 154-155,158-159 OBJECT 88 DATA SET CONTROL BLOCK 97-98,100,103-104.93,95,109 DATA SET CONTROL BLOCK DEFINITIONS 100 DATA SET CONTROL BLOCKS DATA SET CONTROL INFORMATION 51.63 DATA SET CONTROL NAME 64,95 DATA SET RECORD DESCRIBE CROS S-IN DEX 87 DATA SETS 86-81,92,82- 85,88,98,2,5,8-9,11 24,48,60,64,81,89-90.96,99,104,155,158 159,161,199 DATA LANGUAGE/I 9 NAMES OF THE 160,88,97,161 PHYSICAL CHARACTERISTICS OF THE 82,199 DATA STREAM 136,130,133,135 DATA WRITE LOOP DFHTD TYPE 215 DATABASE 160,159,210,161 DATASET 160,82,161-162.81,159,210,92,207 DATASET MACRO INSTRUCTION 82,199 219 USE OP THE 87,158 DFHOC TYPE 161,159,162,210 DPHOCLDS 159 DFHOCODS 160 DFHOCP 17,104 DPHPC MACRO INSTRUCTION 75 DFHPC TYPE 28,75,120,130 EXECUTION OF THE 130 DPHPCP 10,17,51,119 DPHPCT 51,105 DPHPCT MACRO INSTRUCTION 105 DFHPCT TYPE 105,131,176,106-107,209 DFHPCTXX 48-49 DFHPIP 51,17 DPHPLlI 43 DFHPL10I 43,18 DFHPPT 51,108 DFHPPT MACRO INSTRUCTION 108 DFHPPT TYPE 109,97,108,177,209,109-110 DFHPPTXX 48 DFHPRPR 18,43 DPHRDl 17,44,176-177 DFHRD2 17,44 DPHRPL 19,97,100,109,13 DPHRPL AS DFHTRNAA 103 DPHRPL USING DFHLINK 104 DPHRlIP70 18,23 DFHSAP 18,43 DPHSCEXT 117 DPHSCP 10,17,51,117 DPHSFP 17 , 25,171 DPHSG 13,18 DFHSG MACRO INSTRUCTION 13,5 DFHSG PROGRAM 23-24,30-31,38-39,41-42',26-29,32,42 43- 4 4 , 11 0, 137 , 157, 14 , 1 6, 1 8 , 201 ,25,68 , 117 201-204 DFHSG TYPE 23,29-30,13,19-20,44,129,201,204 OPERAND OP 24,27 PARAMETERS OF 21 TCTUA OPERAND OF THE 69 DFHSI 53 DFHSIP 23-24,17,19,11,52 EXCESS OP THE SIZE OF 52 SIZE OF 52 DFHSIP PLUS DPHSIT 48,50 DFHSIT MACRO INSTRUCTION 49 DFHSIT MACRO IIHICH DPHSIT TYPE 49,205 DPHSITXX TERMINAL CONTROL TABLE 48 DPHSIUS 53 DPHSNP 177,17,25,176,1 C7 DFHSNT 111,168,177 DFHSNT IIACRO INSTRUCTION 111 DPHSNT TYPE 112,111,209,113 DFHSTKC 177-178,11,23,176 DFHSTP 11,23,18,117 DPHSTTD 11,23,18,178 DPHSTTR 11,23,18,178 DFHTACLE 120,128 DPHTACP 123-124,126,128,120,162,169,23-24,146,178,17 129,121-122,176 DFHTACP/DPHTEP 148 DFHTAJP 157,17,23,176,178 DFHTC TYPE 141-148,130,123,142,173 DEST OPERAND OP THE 143 SERIES OF 130 DFHTCADS 211-212,214,117 DPHTCP 120,51,10,17 DFHTCT 53,55,51 DPHTCT MACRO 19 DFHTCT MACRO INSTRUCTION 53 OPERANDS OF THE 194 TRUDNT OPERAND OF THE 115 USES OPERANDS OF THE 194 DFHTCT TYPE 70-73,76,61-63,65-69,137,35,179,56,60 18-79,144,24,131-132,138-139,182,197,189,80 179-180,187,190-191,54-55,76-71,180-181,184 185-188,206 NAME OPERAND OF THE 57,62 OPTCD OPERAND OF THE 143,141 TRMIDNT OPERAND OF THE 98 DFHTCTBA TCAM MESSAGE CONTROL PROGRAM 192 DFHTCTLE 120,128 DFHTcrTE 211-212,214,128 DFHTCTXX FILE CONTROL TABLE 48 9 DFHTD 97-99 DFHTDCP 17,178 DFHTDIA 214 DPHTDP 11,51,176,10 DFHTDPDY 17 DPHTEP 123-124,126-127,120,23-24,143,11,121,129,138 162,146,178 USER-IiRITTEN 121,146,173 DPHTEP PROGRAM 131 DFHTEP PROGRAMMING CONSIDERATIONS 121 DFHTEP RECURSIVE RETRY ROUTINE 127 DFHTIOA 211""212,214 DFHTLT 114 DFHTLT MACRO INSTRUCTION 114 DPHTLT TYPE 114-115,209 DFHTLTXX 114 DFHTR 28 DFHTRNAA 103 DFHTRNBB 103-104 DFHTRNCC 103-104 DFHTRNDD 103-104 DPHTRNXX 97,100,178 DFHTRP 51,23,18 DFHTRPDY 23,50 DFHTSP 10,17,51 DFHTSPDY 17 DFHUPDV2 22,201 DFHlIT1 17,44,176,118 DFHlIT2 17,44 DPHXTRA 101 DFH1500 150 DFH1520 150 DFH1701 156 DFH1702 156 DFH1791 156 DFTRMLST 65-66,71,75,68 SPECIFY NAME OF 197 DFTRMLST ENTRIES SHOULD 66 DPTRMLST MACRO DEPINITIONS 77 DIAL-UP 33,179,77,196 DIAL-UP CONNECTION 67-68 DIRECT ACCESS 38,7-8,33 DIRECT ACCESS DEVICE 33,57,72 DIRECT ACCESS STORAGE DEVICE 63,110 DISCONNECT PARAMETER 147 DISCONNECT SIlITCHED LINE DEFAULTS OF 129 DISCONNECTS 147,123,126,121,214 DISK 32-33,56-57,70,192,1-2,11,15,54,119 202,206 DISPLACEIIENT 124-125,88-89 DISPLACEMENT SEGLENG 89 DISPLA Y STATION SMI 1920-CHARACTER 3275/3277 36 DISPLAY STATION 2 480-CHARACTER 3275/3277 36 DL/I 22,82,2,9,45,52,81,207 DL/I ABEND 171 DL/I APPLICATION PROGRAM 23 DL/I CALL EXECUTION PROGRAM 23 DL/I DATA BASE 83 DL/I INITIALIZATION PROGRAM 23 DL/I INTERFACE 171 DL/I INTERFACE DUMIIY PROGRAII 23 DL/I INTERFACE PROGRAM 23 DL/I MODULES DL/I REQUIRES USE OF 2 DL/I UNDER CICS DLIA 171 DLPA 111 DL1 23,19,22,45,52,14,46,49,201,205 DMB 52 DMB DIRECTORIES DURING CICS GENERATION 46 DMB DIRECTORY LI ST 46 DMBPL 52,45,49,205 DOS 28,1,20,29,122 DOS BASIC TELECOMMUNICATIONS ACCESS METHOD 58 DOS CORE IMAGE LIBRARY 53 DOS DISK OUTPUT DATA SETS 96 DOS FILE NAME 83 DOS ISAM DATA SETS 86,84 DOS IS AM VARIABLE-LENGTH RECORDS 9 DOS LBLTYP JOB CONTROL STATEMENT 24 DOS SUBSET COMPILER 28 DOS SUBSET/SUPERSET LOGIC MODULE FACILITY 96 DOS SUPERVISOR 85 DOS SYSTEII 20,23 DOS-ENTRY ONLY 24 DOS-ENTRY SYSTEM 109 DSCNAME 62-64,56-57, 95,102-~04, 190-191,79,182-183 80,206,54,94,101,179-181,184-189,208,97 DSCNAME OPERAND 77 DSECT 19,49,120,205 DSETID 159-161,210 DSETID OPERAND SINGLE USE OF THE 160 DSIZE 19-20,13,201 DTP 82,95,160,79,182 DTF40B DFHTCT TYPE 181 DTF40MD 80 DTP40MD FIGURE 2 79 DTF41C 181 DTF41C DFHTCT TYPE 181 DTF60L 79,189 DTF60L DFHTCT TYPE 79 DTF60L LINEl DFHTCT TYPE 189 DTF60R 180 DTF60R OPL2260 DFTRMLST OPENLST 180 DTF7770 182-183 DUMMY 15-16,29-31,38-42,166,10,202-203 DUMMY CONTROL SYSTEM OPERATIONAL PROGRAMS 17 DUMMY CSA 42 DUMMY CSA PROGRAM 52 DUMMY DPHTEP 120 DUII!!Y DUMP CONTROL PROGRAM 31 DUIIIIY FCP 51 DUIIIIY PILE CONTROL PROGRAII 39 DUIIIIY INTERVAL CONTROL PROGRAM 29-30 DUIIIIY PROGRAII 18,25,30-31,39-40,42 DUIIIIY TDP 51 DUIIIIY TEIIPORARY STORAGE CONTROL PROGRAII 42 DUMII! TERIIINAL 126-127,167 DUIIIIY TRANSIENT DATA CONTROL PROGRAII 40 DUMP 160,156,159,210,1,4,12,155,161,171 DUIII' APPENDIX G 210 DUMP CONTROL DATA SET ]1 DUIIP CONTROL PROGRAM 31,7 DUMP CONTROL PROGRAII ICP 51 DUMP DATA SET 11,15],155,158-159 DUMP MACRO INSTRUCTION 162 DUIIP IIANAGEIIENT 1,155,158 DUIIP IIANAGEIIENT 7 4 DUMP OPEN DATA SETS 159 DUMP UTILITY PROGRAM 4,12,25 DUIIP X'90 RETURN 170 DUPDSID 88,81,92,208 , DUPLICATES DATA SET 88,91,92 DYNAMIC OPEN/CLOSE FACILITY 93,177 USE OF THE 104 DYNAMIC OPEN/CLOSE FUNCTION 104 DYNAIIIC OPEN/CLOSE PROGRAII 43,109,161,177 186-188,203,184 220 -E- FIXED-LENGTH 92-93 FIXED-LENGTH DAII DATA SET RECORD 1 FlIED-LENGTH PCI FIELD CASE OF A 69 FIXUNB 95-96,94,102-103,101,208 FLAGS 124,126,128 FLNNAIIE 56,60,54,182,189,206 FIIT2260 32,36,15,203 FIIT3210 15,32,203 FORIIAT 32,36,105,130-131,81,89,201-208,15,19,66 83,81,114,136,149,203,209 DISCUSSION OF 106 FORIIAT IIODE 106 USE OF 133,36 FORMAT MODE TAKE$ FULL ADVANTAGE 36,131 FOUR-BYTE DESTINATION ID 160 FOUR-BYTE FIELD TCTTEDES 143 FOUR-BYTE LLBB FIELD 81 FREE TERIIINAL STORAGE 126 FULLBUF 32,36,15,130,133,203 FULLBUP CONVERSION CASE OF 480/480 136 FULLBUF IIODE 106,136,36,131 FULLBUF MODE LIIIITS USE OF 36,134 FULLBUF TRANSID 105 FULLBUP 2260 COIIPATIBILITY THROUGH 131 FUNCTION 212-213,l,lI,1, 91,113,116,135,146 SIGN-ON/SIGN-OFF 111 EBCDIC REPRESENTATION 211 ECB 140 END STATEIIENT 46-41 ENDLESS SCREEN 133 ENQUEUE 26,14,201 ENTER KEY 134 ENTRY INTERFACE PROGRAII 43 ENTRY IIACRO INSTRUCTION 13111116-171,105,108,112 2160 INPUT ED 212 ENVIRONIIENT 3,5,1,53,152 RES TRICTED 144 EOI' CONDITION 114,121,123 EOII 133 AUTO 212-213 EOT 123 EQU 211-213,215,193 ERASE 141 ERASEAUP 148 ERROPT 56-58,60,95,91,54,94,206,208 ERROR 163-164,170-111,125,128,161,57,95,91,120,181,183 ERROR CODES 121-123,143 ERROR CONDITION 121,129,146,171 ERROR IIESSAGE 16,68,114 ERROR STATUS 173,122 ERROR STATUS IIESSAGE 173 ESTABLISH BASE ADDRESS REGISTER USING ~11-212 ESTABLISH CONTROL SECTION 108 ESTABLISH SIGN-ON TABLE CONTROL SECTION 111 EVENT COIIPLETION TRANSIENT DATA CONTROL 10 EVENTS X '80 WAIT 38 EXCLUSIVE CONTROL EXCLUSIVE CONTROL DUIIP DATA SET 155 EXCTL 38,15,203 EXEC CARD 11 EXECUTE 170 EXECUTE CICS 10 EXECUTION UNDER CICS 4 EIIDVER 62,66,32,59,131,196,15,54,68,203,206 EXISTING CUSHION 154 EXISTING DFHTEP 24 EXIT 118,143,149,215 EXIT ROUTINE USER-IIRITTEN 39,31,40-42,116,119,21-28,30,148-149,118 EXIT ROUTINES 116,118 EIlTS DFHTCP 141 EXPAND 120,4 EXPIRATION TIllES 151 EXPLANATION CSTL 164-165,113 EXTENT 82,84,81,201 EXTRAPARTITION DATA SET 40,93,155,158,111,214 EXTRAPARTITION DESTINATION 103-104,99,101 EXTRAPARTITION IIVC 215 -G- GAl! 64,66,166 GAllA 101 GAP 11,43,204 GA21-2112 11 GC2l1-5031 85,60,91 GC26-3146 85 GC28-6550 24 GC28-66l11 60,91 GC28-610ll 21-22 GC30-20 04 60,66,164 GC30-2024 61,138,143,149,151 GC30-300 1 131 GC30-500 1 58-60,66 GC311-0013 130 GE 21,115 GENERATE LINKAGE 31,39-42,21,30,28,148-149 GENERATE SEGSET 89 GENERATE TCAM SUPPORT 24 GENPOLL 68-69,54,62,206 DISCUSSION OF 66 GH20-1028 50 GRAPHIC 62-63,196,54,206 GRAPHIC ATTENTION PROGRAII 43 GRAPHICS ACCESS METHOD 60 -1'- F. E. TERIIINAL TEST PROGRAII 25 FBS 81 FCP 15,11,38,203,49,205 PCP IIACRO INSTRUCTION 39 FCT 86,39,80,85,199,201,49,51,205 FCT VALUE 86 FDP HEADER RECORD 214 FDP RECORD 214-215 FDP TRAILER RECORD 214 FEATURE 56-58,32-35,66-61,70,14-15,131,196,182 FEATURE OPERAND 34,132 USE OF THE 15 FEATURE PROGR CICS PREPROCESSOR 18 FEATURE PROGR DL/I APPLICATION 18 PEATURE PROGR DL/I CALL EXECUTION 18 FEATURE PROGR DL/I INITIALIZATION 18 FEATURE PROGR DL/I INTERFACE DUIIIIY 18 FEATURE PROGR HIGH-LEVEL LANGUAGE PROGRAIIS 18 FEATURE PROGR PL/I INTER1'ACE 18 FEATURE PROGR PL/I-OPT ENTRY INTERFACE 18 FEATURE PROGR 1110 CHANIIEL/ABNORIIAL 18 FIELD OF THE TACLE LABELED TCTLEECB FILABL 95-96,94,208 FILE 98-99,94,6-8,23,80,88,96,208 FILE CONTROL 25-26,116 PILE CONTROL AREA 88 PILE CONTROL PROGRAII 2 25 FILE CONTROL TABLE 82,80,8,39,84,89,91-93 ASSEIIBLY 01' THE 48 DISCUSSION OF THE 9 PREPARATION OF THE 199 SPECIFY END OF 91 FILE CONTROL TABLE CONPIGURATOR 199 FILE CONTROL TABLE DCT 51 FILE CONTROL TABLE EXAIIPLE 91 FILE CONTROL TABLE LISTING END 01' THE 91 FILE IIANAGEIIENT 2,82,155,158,80,89,116 FILSERV 43,38,15,203 FILSERV OPERAND 38 FINAL DYNAIIIC OPEN/CLOSE IIACRO INSTRUCTIONS 209 FINAL FILE CONTROL TABLE 201 FINAL IIACRO INSTRUCTION 119,44,16-11,91,95,100,106, 109,113,115 FINAL PROGRAII CONTROL TABLE 209 FINAL SIGN-ON TABLE 209 FINAL SYSTEII INITIALIZATION TABLE 204 PINAL TERIIINAL LIST TABLES 209 FIOA XTYPREQ ADDRESS OF 119 PIXBLK 95-96,94,102-103,208 PIXED FORIIAT 89 FIXED LENGTH PCI FIELDS 01' 69 PCI'S OF 5 -H- HARDCOPY 62-63,54-55,10,12,206-201 HARDIlARE BUPFER 122 HARDIlARE BUFFER EXCEEDED 8C 125 HARDWARE BUFFER SIZE 165 HARDWARE DIFFICULTY 112 HDAII 45 HEADER 215,15 HEADER PORTION 89 HElAD 38,15,203 HEXADECIIIAL F'S REPRESENTS FOUR BYTES OF 159 HEXADECIIIAL FF 9,160 HEXADECII!AL RELATIVE TRACK 38,86 HIDAII 115 HIDAII DATA BASE INDEX DBD OF A 46 HIGH-LEVEL LANGUAGE FEATURE 18 HIGH-LEVEL LANGUAGE SUPPORT GROUP 43 HISAII lI5 CASE OF 52 HLL 16,18,lI3,204 HLLTR 28,14,202 HOLD STATUS 156 HSAII 45 -1- I/O ERROR 168 I/O ERROR INFORIIATION 120 I/O MACROS 85,60 I/O OPERATIONS 59 IADADIII 88,81,208 IADIII 88,81,92,208 IBROIlSE 38,15,203 ICE 30,119 ICP 14,11,29,202,20,45,49,205 ICP SPECIFICATION 151 ICPAUTO 29-30,26,14-15,202 ICPTIIIE 157,26,29,1l1,2Q1-202 ICVR 49,51,205 ICVS 49-50,205 ID VERIFICATION 58-59 IDENTIFICATION FIELD IEUASII 20 1115/360 2,9,45,82 1115/360 ACB LIBRARY 46 1115/360 CTL IIIS/360 VERSION 2 INSTALLATION OF THE 2,9 INAREAL 60,182-183,191,62, 6l1, 19-80, 54, 180-181,18l1 185-189,206 221 INAREAL VALUE 64 INDA 38,15,203 INDACC 82-83,88,81,207-208,92 INDAREA 82,84,81,199,207 INDAREA OPERAND 84 INDEX 46,92 INDEX DATA SET 92 INDEXED SEQUENTIAL ACCESS IIETHOD INDICATO~ 01 SPECIAL 125 INDICATORS 128 INDIRACC 38,15,203 INDIRECT 38,94,99,88,209 INDIRECT ACCESS 81 INDIRECT ACCESSING INDIRECT IIACRO INSTRUCTION 95,99 INDIRECT SPECIFICATION 176 INDSIZE 82,84,81,207 INDSKIP 82,84,81,207 INITIALIZATION TIllE OF 48-49 INITIALIZATION PROCESS 48-49 INITIALIZATION PSB 46 SPECIAL 45 INITIALIZES 48-49,165 INITRL 32-33,35,15,57,203 INPUT DATA SET 96 INPUT DFHTCT TYPE 70 INPUT EVENT REJECTED 163 INPUT LINE 146 INPUT PROCESS QUEUE 67,144 INPUT QUEUE 145,61,146 INPUT STATUS 73,121,174 INPUT STEP 140-141 INPUT TCTLE 139 INPUT TCTTE SPECIAL 145,140 INPUT TIOA BIT 1-7 126 INPUT TPROCESS QUEUE 64 INPUT USER EXIT 149,140 INPUT/OUTPUT IIACROS 97 INQUIRY 1I0DE 137 INSEG 38,15,203 INTEGRATED COlllIUNICATIONS ATTACH !lENT 59 INTERCEPT REQUIRED 168 INTERFACE DUIIIIY PROGRA!I UNDER CICS/OS 171 INTERV REQUIRED 173 INTERVAL CONTllOL 4,10,116,169 ENTRY POINT OF 30 OPTIONAL TIIIE-OF-DAY FEATURE OF 26,29 INTERVAL CONTllOL ELEIIENT 30 INTERVAL CONTROL PllOGRAII 29-30,45 IIACRO INSTRUCTIONS OF THE 20 INTERVAL CONTllOL PBOGRA!! BEING 30 INTERVAL CONTBOL PllOGRAII TCP 51 INTERVAL CONTllOL PllOGRAII 6 25 INTERVENTION 166,173,58 EXCEPTION OF 166 INTERVENTION REQUIRED IIESSAGE 173 INTRA 39-40,101,15,94- 95,98,176,203,208 INTRA IIACRO INSTRUCTION 98 INTRAPARTITION 171,93 INTRA PARTITION DATA SET DATA DEFINITION 44 INTRAPARTITION DATA SETS 7,40 INTRAPARTITION DESTINATION 93,101 INVALID COpy REQUEST 171 INVALID liES SAGE BLOCK 123,172 INVALID PROGllAII ID 170 INVALID REQUEST 161 INVALID TCAII DESTINATION AO 125 INVALID TERIIINAL ADDRESS 162 INVALID TRANSACTION IDENTIFICATION 77 INVALID WRITE REQUEST 174 INVLIST 192 INVLl:ST ORDER 193 IOERROR 137 IOSIZE 91,83,85,81,207 LARGEST 85 IOWORK 83,85,81,207 IPL 129 IPL RECORDS 129-130 PREPARATION OF 130 ISADD 38,15,203 ISADSCN 57,62,64,54,79,188,206 ISAII 82-85,7,81,199,92,207 ISAII DATA 92 ISAII DATA SET ORGANIZATIONS ISAII DATA SETS 84-85,87 ISMI DATA SETS UNDER CICS/OS 199 ISAII FILES REQUESTING NEWREC SERVICES 85 ISAII LOGIC 1I0DULE END DFHFCTBA 93 ISAII ORGANIZATION 9 ISAII SEQUENTIAL llECORD RETRIEVAL 19 38 ISAII VARIABLE-LENGTH RECORDS 38 ISSUE TERIIINAL CONTROL 144 ISUPD 38,15,203 IVBR 38,15,203 9 KEY 88,199,82-84,81,86-87,,207-208,9 KEYBOARD SPECIFY COMPONENT POLLING OF THE 65,71 KEYBOARD LOCK FEATURE OPERATIVE 35 KEYLEN 87,81,83,192,207 KEYLEN OPERAND 84,87 -L- LABEL 124-126,129,158,67-68,46-47,116,118,66,89 90,200 SYIIBOLIC 123, .121-122 LABEL DFHDCTBA 100 LABEL DFHFCTBA 91 106 LABEL DFHPCTBA LABEL DFHPPTBA 109 LABEL DFHSNTBA 113 LABEL DFHTCTBA MUST 77 LABEL DFHTLTBA 115 LABEL TCTLEECB 125 LABEL TCTLEIOA 125 LANG 28,14,16,18,43,202,204 LAST STATEIIENT 46-47,100,106,109,113,115 LAST TERIIINAL ENTRY 72 LENGTH 81,207-208,83-84,86-87,95-96,62,64,69 54,88-90,94,206,208,8-9,53,56,76,92 109,121,123,171 LENGTH DFHFCT TYPE 81,207-208 LERB 58,60 LEBB PARAMETERS 60 LEVEL TRIGGER 154,98-99,93,153 LIBRAllY MAINTENANCE PROGRAII 19 LIIIIT CONSECUTIVE DISPATCH 154 LINE ADDBESS 135 LINE ADDllESSING 135 LINE CONNECTION 59,76-77 LINE CONTROL CHAllACTERS 140 LINE CORRECTION FEATUllE 57-58 LINE DFHTCT TYPE 80,79,192 LINE DISCONNECTED 126-127 LINE ENTRY 66,77,70,125 LINE LOCKING 145 LINE IIACBO 65 LINE OUTQ60 DFHTCT TYPE 191 LINE POOL RESTRICTIONS 144 LINE POOL SPECIFICATION 144 LINE PRINTER 60,2,63,72 LINEADR 147 LINEADR llEQUEST X'EO 147 LINELST 62,72,56,59,79,54,80,179-182,184,186-187 189,206 LINES MULTIPOINT 179,196-197 NUMBER OP 70,74,131,55,207 LINK EDITED BEFORE STAGE I I 22 LINK MACRO INSTRUCTION 120 LINKAGE 37.39-42,149,116,148-149 LINKAGE EDITOR 46-47 LINKAGE EDITOll OUTPUT LIBRARY 50.55,82,94,105,108,114 LINKEDIT 95 LIST 163,35,46,97,159 ANSWERING 66 LIST ERllOR 163 LISTADR 160-161,62,66.80,159,210,54,180,184-187,206 LISTADR OPERAND DISCUSSION OF THE 160-161 LISTADR OPERAND MUST SPECIFY 66 LISTADR OPERANDS 159-160,68 LLBB 9 LOAD 11,43,49,212 LOAD MACllO INSTllUCTION 28 LOADED PROGRAIIS DUIIP DATA SET LOCAL 2260 UNDER DOS 65 LOCAL 2260'S 59-60,72-73,32,43 LOCAL 3270 INPORIIATION DISPLAY SYSTEII 67,69,64,73 LOCAL 3270'5 63,72-73,59 LOCK OPTYPES 58 LOCKF 32-33,35,15,57,203 LOGIC PLOW 140 LOGIC 1I0DULE 101),103-104,109,93,96 LOGICAL 113 LOGICAL IOCS 96 LOGICIIOD DESTINATION CONTROL TABLE 208 LOGICMOD ESTABLISH CONTROL SECTION 82 LOGICMOD MACRO INSTRUCTION 91 LRECL 86,81,83,92,207 LRECL PARAIIETEll lIUST EQUAL 85 LV UNIT 79,189,55,70,207 L 17770 DI'HTCT TYPE Ll7770 182 L2260 72,74,79,188-189,191,33,57 L2260 PARAMETEB 34 L3270 122,189 L3277 189,33-34,57,63,72 L3284 33-34,57,63,72 L3286 33,54,56,63,72,206 -J- JCL 20,22,10-11 JCL DURING STAGE I I 20 JOB 19,21,11 JOB CONTROL 10,20 JOB CONTROL LANGUAGE 22,10 JOBCLASS 19,21,14,201 JOBNAIIE 19-20,14,201 JULIAN 156 -11IIACRF 56,60,77,190-192,54,186-187,206 IIACRI' OPERAND 57 IIACRO CVT 38-39 IIACRO INSTRUCTION 200,130,173-174,5,18,28-29,48,70,94,99 159 LAST OPERAND OF THE 13,200 IIACRO INSTBUCTION DURING SYSTEII GENERATION 129,137 IIACRO INSTBUCTION HUST ASSEIIBLY OP THE 103-104 -K- KBL 56,58,54,189,206 KBRDLOCK 35,54,62,67,206 KCP 20-21,14,17,26,49,51,201,205 KCP IIACRO INSTRUCTION 29 222 EACH LOGICAL PAIR OF SEQUENTIAL SDSCI 62 MAIN STORAGE 84,91,6,10,21,41,90,109,154 AMOUNT OP 51-52,24 MAXIMUM AMOUNT OF 21 MAIN STORAGE AREA 84-85,1,55 MANAGEl'IENT AUTOMATIC TASK INITIATION FEATURE OP CICS TItlE 157 OPTIONAL TIME ADJUSTMENT PEATURE OF CICS TIME 157 RUNAIiAY TASK CONTROL FUNCTION OF CICS TIME 1 MANAGEMENT PROGRAM 116-118 MASTER INDEX EXISTS 84,199 MASTER TERMINAL 104,158,152,2,74,129; 155-156 MASTER TERMINAL PACILITY 43,164,168 MASTER TERMINAL OPEN/CLOSE SERVICE PUNCTION 87 MASTER TERMINAL OPERATOR 152,156 MASTER TERMINAL PROGRAM 42,158,152,177 IIAXIIIUII BLOCK LENGTH 86 IIAXIIIUII LENGTH 96,86,90 MBBCCHHR 86 MCP 140,151,2,138,147,190,150 !'ICP MESSAGE HANDLER MACRO INSTRUCTIONS 147 68,127,129,143,157,172,176,207 !'lESS AGE CONTROL PROGRAJ1 2 !'IESSAGE CURSOR 148 MESSAGE DFH4000 61 IIESSAGE INDICATOR ANY START OF 136 START OF 135,36 MESSAGE LINE START OF 147 MESSAGE LTORG END INDEX 138,190 !lESSAGE PROCESSING PROGRAM MESSAGE ROUTING 143 MESSAGE SIGN OFP 175 !'IESSAGE TOO LONG RESPONSE 166-167 !'lODE 56,60,54,136,206 MODE OPERAND 77 !'IODEL NUMBER 70,74,131,55,207 MODEL 33/35 33,63,67,72 MODELST 56,59,54,186-187,206 MODELST OPERAND MUST 77 MODULE 50,55,82,94,105,108,114 REMAINDER OF THE 130 !'IPP 138,190 !'IPS 19-20,23,14,201 !1PT 56,5f1,206 MSG BLOCK INC!'IPLT 172 IISGCLAS 19,21,14,201 !1SGLVL 49-50,19-20,14,201,205 MSP/7 130 !1SP/7 OUTPUT HANDLER TELETRANS OPTION OF THE 130 MSTIND 82,84,81,207 MTP 16-17,42,204 MULTIPLE ISAM DATA SETS 91 MULTIPLE TRACK SEARCH 85 III,\, 49,51,205 MXT OPERAND 53 MXT SPECIFICATION MINUS ONE 205 OPERATING SYSTEM 156-157,2,24,52,11,29,153,178 OPERATOR 168,174-175,42,19,21,111,14,67-68,201,5 34,110,112,134,156 OPERATOR GUIDE 152 OPERATOR IDENTIFICATION 112,111,174,209 OPERATOR NAIIE 112,111,168 OPERATOR PRIORITY 112,71,106 OPERATOR PRIORITY DPIISNT TYPE 111 OPERATOR PRIORITY, 0 209 OPERATOR SECURITY KEY 112,111 OPERATOR SIGN-ON TABLE ENTRY 112 OPPRTY 112-113,111,209 OPSYS 19,21,13,201 OPTCD 56,61,139,144,190-191,54,206 OPTION AL KEYBOARD LOCK PEATURE 35 OPTIONAL TIllE ADJUSTMENT PEATURE 157 ORDER DPIISIAS 53 OS 28,9,20,29,157 OS BASIC TELECOIIMUNICATIONS ACCESS IIETIIOD 60 OS DATA 85 OS DATA MANAGEIIENT SERVICES 85 OS DDNA!1E 83 OS IS All DATA SETS 83 OS JOB 9 OS JOB SCIIEDULER 21 OS LINKAGE EDITOR 6,95 OS/OOS SAVE USE OP 117 OS/IIPT 61,143,149,151 OS/MVT 21 OS/IIVT TCAM PROGRAIIIIER GUIDE 61,143,149 oS/!1n TCAM PROGRAMMER'S 151 OSAOSCN 57,62,64,54,79,188,206 OSCOR 51-52,49,205 OUTPUT 38,94-95,102-103,127,139,61,137-138,143,149 208 OUTPUT AREA EXCEEDED 165 OUTPUT DATA SET 96 OUTPUT DATA STREAII 36,74,130-131,135,137 OUTPUT DCB 143 OUTPUT DFIITCT TYP.E 70 OUTPUT EVENT REJECTED 163 OUTPUT EVENTS 37,149 OUTPUT LENGTII ZERO 165,122 OUTPUT LINE LOSS OF TilE LAST CIIARACTER OF EACII 134,36 OUTPUT TCTLE 139-140 OUTPUT TCTLE THAT 139 OUTPUT TPROCESS QUEUE 64 OUTPUT USER EXIT 149 OUTQ 191,54,62,69,146,207,215 OUTQ OPERAND 64 OUTQ OPERAND IIAY NOT 64 OUTSEG 38,15,203 OVERLAYS 53 -P- PARAMETER DASD GENERIC 33,57 PARA!1ETER LIST 160-161 PARAMETER LIST ADDRESS 159-160 PARA!'IETERS 74,131; 86, 159-160,68,143,185-186 PARTITION/REGION EXIT TI!1E INTERVAL 153 PASSiORD 112,111,209 PCB 138,45,52,83,192 PCB PAIRS 45 PCB STATEMENT 45 PCI 5,127-128,22,69,76,196,192 LENGTII OF TilE 5 PCI AREA ADDRESS USING PCIAREA 128 PCI FIELD 22,69 ADDRESS OP TilE 69 FIXED-LENGTH 15-BYTE 22 PCIBAR 128 PCICNT 127-128 PCISAVE 127-128 PCP 14,17,28,202,49,205 PCP MACRO INSTRUCTION 110 PCPLOAD 28,14,202 PCT 176-177,46,104,111,157,209,211,49,168,205 PCT ENTRY 46,111 PCTCBAR 211-212 peTEA 211 PCTIPIA 211 PCTTI 211 PDIR 46,22 PER!'IANENT LINE LOCK 144 PGMERID 19-20,14,201 PGMLANG 110,109,108,209 PHASE NAMES LAST TWO CHARACTERS OF THE 53 PIP 49,51,14,17,29,202,205 PL/I 14,16,18,28,46,43,52,108-109,200,202,204 209 PL/I APPLICATION PROGRAMS PL/I COMPILERS 43 PL/I P 43 PL/I INTERFACE PROGRAII 43 PL/I MACRO INSTRUCTION 18 PL/I OPTI!'IIZER 43 PL/I PROGRAMS 46 PLl 43,52,16,49,204-205 POINT-TO-POINT LINE 179 POINTER 124,88,120 9 POINTNO 212,214 POINTS 27-28,80,93,101,212 POLL LIST NAME 80 POLL LIST TERMINAL DPHTCT TYPE 80 POLLING 146,37,74,148 POLLING LIST 65-66,71,162-163 POLLING LIST ENTRIES 66 POLLING LIST ERROR 121 FOLLPOS 70,75,185,55,184,207 -N- NCP 56,60,54,206 NEGATIVE POLL DELAY 154,67,153 NEGATIVE RESPONSE 167-168,67,122 NEll LINE SYIIBOL 135 NEll TIOA 145 NEIiREC 82,85-87,199,91,81,92,207 NL 135,74,131,134 NL KEY 135 NL SYIIBOL 135 NO OPERAND 29,20,23,28 NO OPERAND INDICATES THAT 96,42 NOEICTL RECORDS 83 NON-SliITCHED LINES 162,166,70,197 NON-TCA!1 ENVIRONMENT 146 NONRESIDENT DATA SET CONTROL BLOCKS NONRESIDENT EXTRAPARTITION DATA SETS DEPINITION OF 100 NONRESIDENT LOGIC IIODULES 102,104 NORMAL STATION ADDRESS 75-76 NORIID 95-96,94,208 NRECDS 86,83-84,81,207 NRECDS PARA!1ETER 86 NSD 23-24,14,201 NULL 75,54,62,68,206 102-104,100,97,93 -0- OCP 17,43,204 OIU 56,58,54,180,206,213 ONE DASD SEQUENTIAL TERIIINAL 2 77 ONLINE TERMINAL TEST FACILITY 59-60 OPEN 97-98,87,160,158-159,81,83,94,153,155,162 192,207-208,210 OPEN ERROR 40 161 OPEN FAILURE 164 OPEN !1ACRO INSTRUCTION 161 OPEN !1ACRO INSTRUCTION FOLLOIiS 159 OPEN OPERATION 161 OPEN OPTION 60 OPEN TIllE 59 OPEN/CLOSE 158,7,155 OPEN/CLOSE IIACRO INSTRUCTION 158 OPEN/CLOSE PARAMETER LIST 159 OPEN/CLOSE PROGRAM THAT INDICATES IIHICH 97 OPERAND DFHTCTBA 179 OPERAND RESULTS OIlISSION OF AN 26,28-29,31-32,38,40-41 OPERANDS 13,200,82,85,51,56,88-90,95,97-99,105 108,112,165,177,189 223 DISCUSSION OF 66 fOLLPOS OPERAND MUST 69 POOL 70-73,11111,62,139-1110,69,1114-145,511-55,207 80,187-189 POOL FEATURE 69,139,11111 POOL OPERAND DISCUSSION OF THE 139 POOL READY DFHTCT TYPE 182-183 POOL SIZE 52 POOL 2980 GENERAL 1811 POOLADR 54,62,67,80,181,163-1811,186-189,206 PORTABLE AUDIO TERMINAL 2721 76 PPT 56,59,177,37,100,103,108-109,111,1111,157,170 209,49,511,186-167,205-206 PPT ENTRY 100 PREFIX. MACLtB 22 PREFIX. SOURCE 22 PRIMARY SYSTEM CONTROL 152 PRIr'IARY DATA SET 11-12 PRINTER ADAPTER 132 PRINTER ADAPTER FEATURE 711 PRIORITY 105-106,21,71,111,113 PRNT 103-1011 PRNT DF'HDCT TYPE 102,1011 PROCEDURE 19,22,212 PROCESS 1110-1111,145-1116,12,95,99,156 PROCESS CONTROL BLOCK 138 PROCESS CONTROL INFORMATION 127 PROCESS CONTROL INFORMATION FIELD 5,69,76,198 PROCESS TCAM UNSOLICITED ERRORS 125 PROCESSING PROGRAM TABLE 108-110,6,100,110-111,114,157,177 DURING PREPARATION OF' THE 37 END OF THE 109 SPECIFY END OF 109 PROCESSING PROGRAII TABLE MACRO INSTRUCTION 108 PROCESSING PROGRAM TABLE PCT 51 PROCNMS 19,22,14,201 PROCOPT 45 COMBINED 115 PROG CONTROL TABLE ADDRESS REG 211-212 PROGR CICS/DOS LINKAGE EDITOR DFHLINK 17 PROG R CONTROL SYSTEM DUIIMY PROGRAMS 17 PROGR PL/I-F ENTRY INTERFACE DFHPL 11 18 PROGRAM 20,25,97,107,110,109,155,163-1611,170,106,108 6,26,28,31-32,38,110-1111 ,177-178 ,3,23 25,27,29,42,48,51,105,110,176,209,211 PROGRAII CONTROL 28,6 PROGRAM INTERRUPT 29 PROGRA!! INTERRUPT CONTROL 29 PROGRAM SUFFIX DFHSG 14-16 PROGRA!! SUFFIX FILE CONTROL 203 PROGRA!! SUFFIX INTERVAL CONTROL 202 PROGRAM SUFFIX IIASTER TERMINAL 2011 PROGRAM SUFFIX' PROGRA!! CONTROL 202 STATUS OF A 155,153 TYPE OF 17-18,108-109 USER-SPECIFIED USER-WRITTEN 178 PROGRAM CODE 16-18 PROGRAM COMIIUNICATION BLOCK lI5,52,83 PROGRAM CONTROL 170,10,108,116 PROGRAM CONTROL DELETE 109 PROGRAII CONTROL TABLE 105,1011,107,116,107,111,157,176,211 SPECIFY END OF 106 PROGRAM CONTROL TABLE ENTRY 112 PROG RAM CONTROL TABLE EXAMPLE 107 PROGRAM CONTROL TABLE FCT 51 PROGRAM CONTROL XCTL MACRO INSTRUCTION 211 PROGRA!! DCP PROGRAM CONTROL 51 PROGRAM DYNAMIC OPEN/CLOSE 155 PROGRAII INTERRUPT 170 PROGRAII PROCESSING TABLE 103 PROGRAII NAME 177-178,20,116,106,108 PREPARATION OF THE 97 PROGRAM SPECIFICATION BLOCK 45,52 EIGHT-CHARACTER NAME OF THE 52 STATE!!ENTS OF 83 PROGRA!! SUFFIX 1 lI-16 ,26,29 ,31, 36-39,41-112,202-203 PROGRA!! TABLE 118,108,209 FIRST DURING PREPARATION OF THE PROCESSING 108 PROGRAII TABLE EXAMPLE 109 PROGRAII TSP PROGRAM INTERRUPT 51 PROGRAM UNDER CICS/OS DURING EXECUTION OF THE CICS-DL/I INTERFACE 171 PROGRAMMER ACTION 163-168,172-175 PROGRAMIIER GUIDE 211 PSB 116,52,115-116,83,119,205 PSB DIRECTORY 116 PSB NAIIE 116 PSBGEN 83 PSBPL 52,II5,lI9,205 PSEUDO-BINARY TRANSMISSION CODE 34 PSEUDOBIN 32,34,15,203 PTRADAPT 131,55,70,185,207 PTRADAPT SPECIFIES 711 PTTC/EBCD CODE 33 PUBLICATION DOS SUPERVISOR 97,60 PUBLICATION OS JOB CONTROL LANGUAGE 21-22 PUBLICATION OS SYSTEM PROGRAIIIIER'S 24 PUBLICATION OS/360 BASIC TELECOMMUNICATIONS ACCESS 1611 PUNCH/l lI03 PRINTER 188 USE OF 115 -QQUEUE CONS IDERATIONS 1115 QUEUE LOCKS 1 II 5 QUEUE PURGE PROGRAM 411,177 QUEUE SINCE TCAM REQUEUES LOCKING OF THE TCAM OUTPUT PROCESS 146 QUEUE TERIIINAL ENTRY STORAGE CHAIN 125 QUEUES 146,192-193,99, ll14-145, 169 224 QUEZERO 215 -R- RDBACK 911-95,208 RDYIISG 181-183,511,62,206 READ-ONLY 92 READ'S 11111 READB 148 READER 1 SPECIFY COIIPONENT POLLING OF 65,71 READER 2 COIIPONENT POLLING OF 65,71 READL 1117 READY 181-183,129,145 READY IIESSAGE 76,68 REAL LINE ENTRY 120-121 REAL TERIIINAL 166-167 CHECK SENSE F. 122 REAL-TIME EXECUTION 6,11 REAL-TIllE PRE-LOCATED PROGRAII LIBRARY 6,211 REAL-TIllE PRE-LOCATED PROGRAM LIBRARY DTF 23 REAL-TIllE RELOCATABLE LIBRARY 97' REAL-TIllE RELOCATABLE PROGRAII LIBRARY 19-21,6,100,109 REAL-TIllE RELOCATABLE PROGRAM LIBRARY 50 REAL-TIME SYSTEM ADIIINISTRATION 152 REAL-TIllE SYSTEII PROGRAMIIING 3 RECEIVE 70,73,1110,55,79,156,189,207 TERIIINAL STATUS OF 1711 RECEIVE ONLY STATUS 125 RECFII 56,61,190-191,511,206 RECFII BYTE BYTE II 160 RECFORII 87,95-96,102-1011,81,83,92,911,101,207-208 RECORD CHARACTERISTICS 81-82,87,199 RECORD DATA SET CICS DEFINITION OF A DOS ISAII VARIABLE-LENGTH RECORD FORIIAT 86-87,7,96 RECORD IDENTIFICATION FIELD RECORDS 86-87,83-85,7,92,1 liS, 61, 8, 89, 50, 87 90,96,99,157 RECURSIVE COUNT 128 RECWT 58 REFER 110,50,85,88,93,97-99,106,110,138,143,1119 200 REGION 19 REGISTER 159,210,118,161 SYIIBOLIC 159,210,161 RELATIVE LINE AA 163-164 RELATIVE LINE ZZ 162-1E3,166-168 RELEASE TCAII TIOA 121 RELOAD 109,100,103-1011 ,108 ,11 0, 209 RELOCATABLE PROGRAM LIBRARY 211 RELREC 88,81,208 RELREC S,IGNIFIES THAT 88 RELTYPE 86,81,83,207 RELTYPE OPERAim 86 RELTYPE OPERAND MUST ALSO 811 REMOTE 180,33,179,131 REMOTE BINARY 59 REMOTE DEVICES 56,58-59,197 REMOTE 3270 35,63,66,123,122,173 REMOTE 3270 INFORMATION DISPLAY SYSTEM 64,173 REMOTE 3270 OPERATION 131,36 REREAD 95-96,94,208 RES 109,108,209 RESET 123,128,157 RESET PARAMETER 147 RESIDENT 109,21,100,155,160 RESIDENT DATA SET CONTROL BLOCKS 100-101,97-98,95 RESIDENT LOGIC MODULES 102 RESIDENT PROGRAM SUFFIXES 51 RESIDNT 97-98,102, lOll, 94,208 55,64,95,117,120,129,1110,1118 RESPONSE DEVICE MULTIPLE PARAMETERS lU Y 63 RESPONSE TIME 131 ' RETRY 59,128 RETURN CODE ZZ 163-1611 RETURN MACRO INSTRUCTION 130,117,120 RETURN REQUEST 75 RETURN X' 110 ABEND X '60 ABEND 170 REUSE 98,94,208 RIW 56,58,54,206 RIX 56,58,54,206 RKP OPERAND THROUGH USE OF THE 87 RLN 192-193 ROLLOUT DATA SET DTF 27 ROLLOUT FACILITY 154 RPQ835503 74 RUN 106,138,21,35,41,130 RUN DFHDUP 11 RUNAWAY 29,26,ll1,153,201-202 RUNAWAY TASK TIME INTERVAL 153,34,51 -S- S/360 32-311,15,203 S/360D 32,34,15,203 S/360D SYSTEM/360 33 S/370 32-33,15,203 S/370,1130 34 SAM 32-33,196,62-63,15,511,202,206 SAil LINES 166 SAl! UNDER CICS/DOS 93 SAVE ll17,215,25,128 SCAN 193 SCONTROL 196,5l1,62,67,80,206 SCP 111,17,27,202,49,117,205 SCREEN 133-136,212 SCREEN FORMAT 65,72,36 SCREEN TECHNIQUES 131-132 SCS 49-50,205 SCTYKEY 112-113,111,209 SCTYKEY FIELD THREE-BYTE 112 SCTYKEY KEYWORD OPERAND OF THE 112 SDSCI 102-104,79,190-191,97,100,188,54,56,72,80 94-95,101,138,179-182,184-189,206,208 SDSCI I1ACRO INSTRUCTION 62,64,100,139,56,93,95,97,141,143 PARUETER OPERAND OF THE BTAI1 62 SDSCI SPECIFICATION 72,186,189 SEARCH ENTRY DFHPC TYPE END OF TABLE 211,213 SECURITY KEY 112,168,1011-105,111 SECURITY VIOLATION 168,112 SEGCHAR 89,92,81,208 SEGCHAR OPERAND 89 SEGDEF 83,89,92-93,81,90,208 SEGDEI' I1ACRO INSTRUCTION 90,89 SEGHEAD 89,83,81,92,208 SEGLAST 93 SEGLENG 92-93,81,90,208,89 SEGI1ENT 82-83,89- 90,92-93,7-8,81,144-145,90 1113,207 SEGI1ENT PROCESSING 143,1111 SEG!!ENT RECORDS 83 SEG!!ENT SET 8,90 SEGIIENTED RECORD 7-8,89-90 DEI'INE HEADER OF 89 DESCRIBE EACH SEGIIENT OF A 89 SEGNAI1E 92-93,81-82,90,208,89 SEGSET 90,83,82,93,208,90 SEGSET IIACRO INSTRUCTION INCLUDES 90 SEGSET OPERANDS 89 SELCTPEN 131,10,185,189,201 SELECTOR PEN 132 SELECTOR PEN FEATURE 111 SENSEG STATEIIENT 45 SEPAS!!B 95,100,911,103,208 SEQUENTIAL 196,53-54,62-63,19,188,206 SEQUENTIAL ACCESS IIETHOD 32 SEQUENTIAL DATA SET 60.61,1,1,11,145 SEQUENTIAL DEVICES 51,60,62,611,119 SERVICE PROGR TRANSMISSION ERROR 11 SERVREQ 199,81,91,82-83,81,92,201 SET LENGTH 215 SET REAL-TIllE RELOCATABLE PROGRAII LIBRARY SIGN-OF!' PROGRAII 25,17 6-111 SIGN-ON PROCEDURE 110-112 SIGN-ON PROGRAII 25,111 SIGN-ON TABLE 111,168,174,28,110,112-113,111 CREATION OF THE 111 END OF THE 113 SPECIFY END OF 113 USE OF A 110 SIGN-ON TA BLE BEFORE ASS EIIBLY OF THE 113 SIGN-ON TABLE EXAMPLE 113 SIGN-ON TABLE HACRO INSTRUCTION 111 SIIIODS 53,49,205 SINGLE TCTTE 10 SIW 56,58,54,206 SIX-BIT TRANSCODE 59 SIZE 1111,50,64,106,154 SKIP 95,91,94,208 SLAVE 58 SLV 56,58,511,186-181,206 SI11 32,36,135,133,136,15,203 Sill CHARACTER 136,135,36 SNT 110,209 SOURCE DECK 82,105,108,111,1111 SOR 158 SOURCE TERIIINAL IDENTIFICATION FIELD EIGHT-BYTE 140,149 SPECIFIC DATA SET 83 SPECIFICATION 13,16,53,65,12,86 SPECIFICATION COIIPAT 14,131 SPECIFIED SYSTEII INITIALIZATION TABLE 11 SPECII'IED TRANSACTION 136 SPECIFY DATA SET CONTROL 19-80 SPECIl'Y DATA SET CONTROL INFO 101 SPECIl'Y DATA SET CONTROL INFORIIATION 56,95,194 SPEC Il'Y EXIDVER 68 SPECIFY EXTRA PARTITION DESTINATIONS 91 SPECIl'Y HEXADECI!'IAL 191 SPECIFY INDIRECT DATA DESTINATIONS 99 SPECIl'Y INTRAPARTITION DESTINATIONS 96,93 SPECIFY IOSIZE 85 SPECIFY KEYLEN 45 SPECIFY LAST SEGIIENT SET 90 SPECIl'Y TERMINAL IDENTIFICATION 114 SPECIFY THAT INTRAPARTITION DATA SETS 40 SPECIFY TIOA ADDRESS DFHTC TYPE 215 SPECIFY TRANSACTION CONTROL INFORIIATION 105 SPECIFY USER-DEFINED PROCESS CONTROL INFORMATION 22 SPIll SPIE 29 SPURGE 106,105,101,209 SPl 49-50,205 SRCHII 83,85,81,201 SRCHI1 OPERAND UNDER DTFDA GENERATION 65 STAGE II 44,13 STANDARD CICS/TCAII COIIMUNICATION BYTE 141 STANDARD DOS LOGIC IIODULE NAIIE 100 STANDARD DOS NAIIE 96 STANDARD DOS SA!! IIACRO INSTRUCTIONS 100 STANDARD IIODULE NAIIE 50,55,82,94,105,108,1111 STANDARD SYSTEI1/360 RECORD FORIIATTING CONVENTIONS STANDARD SYSTEII/360 VARIABLE LENGTH 7 STANDARD TERIIINAL APPLICATIONS 1 START/STOP DEVICES 64 START/STOP TRANSMISSION 119 STATEI'IENT 60-61,96,10,46,72 STATION CONTROL FEATURE 58,61,73 STATISTICS 151-158,1411 STATISTICS PROGRAIIS 225 SUPERVISORY 23 STATISTICS PROGRAMS WRITE DATA 176 STATUS 19-20,22,13,201,68,73,11 STC 56,58,54,19,206 STD 95-96,94,208 STN2980 10,15-16,184-185,55,201 STORAGE 104,109,3,7,45,99,124,141 STORAGE CONTROL 170-171,116 BEI'ORE TASK DISPATCH 10 ENTRY POINT OF 21 STORAGE CONTROL CANNOT ISSUE 118 STORAGE CONTROL PREEIIAIN 109 STORAGE CONTROL PROGRAI1 21,202,111 STORAGE CONTROL PROGRAM PCP 51 STORAGE CUSHION SIZE 154,49,153 STORAGE DEFINITION DFHTCT SYIIBOLIC 19 DFHTCTTE SYMBOLIC 121 SYIIBOLIC 159-160 STORAGE ESTIIIATES 50 STORAGE IIANAGEMENT 1 STORAGE STATISTICS DYNAI'IIC OPEN/CLOSE I'UNCTION 158 STRG DEFN PCTCBAR EQU STIlT 29 SUBPOOL 0 109 SUBSET 28,14,202 SUFI'IX OPERAND 31 ANY USE OF THE 30-31,39-110,42 SVC 23-24,14,201 SVC DL/I INTERI' ACE 18 SWITCH 56,59,162,19,11,511,80,153,159,119-182,1811 186-181,189,206,210 SIlITCH DUIIP DATA SETS 162,158 SIlITCHED LINES 61,1611,161,106,191,34,10,129,131 SIlITCHED NETWORK 56,59 SWITCHED-LINE PROCESSING 61 SIlLST 131,13 LABEL OF A DFTRMLST IIACaO INSTRUCTION OF THE 66 SIll 56,58,54,206 SYIIBADR 160-161,159,210 SYIIBADR OPERAND 159-160 SYIIBOL DI'HTCT TYPE 10,62,16,55 SYIIBOL DI'TRMLST SIiLST 66 SYNAD 56,61,54,206 SYNAD ROUTINE 61 OWN 61 SYS/3 32-34.54-55,181,206-201,15,56,62.10,203 SYS/3D 32,34,15,203 SYS/3D SYSTEM/3 MODELS 6 33 SYS/1 54-55, 206~201, 32-33,15,56 ,62,10,203 SYSLST 102,104,101,188 SYSNNN 56,59,54,206 NNN OF 59 SYSTEII 4,11,10,5,51,59,152,156,1,3,5,1 20,23,46,48.61,10,81,85,91,110-111,138 152-154,151 CPU-TO-CPU CONTENTION 58 POINT-TO-POINT DIAL 58 SYSTEII ABEND 96 SYSTEII ACTION 162-168,171-175 SYSTEII ADIIINISTRATION 50-51,152 SYSTEII CONSOLE 156 SYSTEI1 CONSOLE LOG.IIESSAGE 166-168 SYSTEII CONTINUES PROCESSING 163 SYSTEM CONTROL FUNCTIONS 152 SYSTEII CONTROL TABLES CERTAIN USER-PREPARED 6 SYSTEM COUNT 121-128 SYSTEII DATA SET CONSIDERATIONS 6 SYSTEII GENERATION 4,13,131,10,20,48,200 INITIALIZATIO N OF 19,201 STAGE I I OF 21 SYSTEI! GENERATION MACRO INSTRUCTIONS 23-29,31-32,38-39,111-44 USE OF DFBSG 13 SYSTEII GENERATION PROGRAM NAME 11-18 SYSTEII INITIALIZATION 11,61,155,48,171 SYSTEII INITIALIZATION OVERLAYS PHASE NAMES OF THE 53 SYSTEII INITIALIZATION PROGRAII 23-24,11.48,13,19 SIZE OF THE 52 SYSTEII INITIALIZATION TABLE 26,115,48,46 SYSTEI'I INITIALIZATION TABLES FLEXIBILITY OF GENERATING SEVERAL 49 SYSTEII INITIALIZETION TABLE 38 SYSTEII !!AINTENANCE 5 SYSTEII PARTITION/REGION EIIT TIME INTEa~ AL 153,49-50 SYSTEII PROGRAMMER 3,194,199 SYSTEII PROGRAIIMING CONSIDERATIONS 116 SYSTEI1 REQUESTS IIIMEDIATl! TERIIINATION USER OF THE CICS/DOS-STANDARD 156 SYSTEII SERVICE PROGRAIIS 13,16,18 SYSTEII SERVICE TABLES 110,28 SYSTEII STATISTICS 151,111 SYSTEI1 TABLE PREPARATION 5,9,118,22,1116 SYSTEII TERIIINATION 155,11,18 SYSTEM TERIIINATION PROGRAII 23,111 SYSTEII/3 119 SYSTEII/3 IIODELS 6 33 SYSTEI1/360 IIODEL 20 33-34 SYSTEII/360 MODEL 25 34,59 SYSTEII/310 59 SYSTEII/1 129-130,13,58,61 SYSTEII/1 STORAGE LOAD 130 SYSTEII/1 STORAGE LOAD UZERO 130 SYSOOl 19,188 SYS006 19,188 SYS008 31 SYS011 102-103 -T- TAB 32,36,15,136,203 TABLE END 91,106,109,113 TABLE ENTRY 92 TABLE PREPARATION 200 TAB2980 70,76,184-185,55,207 TACLE 120-121,123,125-126 TACLE CONTAINS ALL 120 TACLE WHICH CONTAINS TACLE WORK AREA ADDRESS OF 124 TACP 125,127 TASK ABEND 126-127 TASK ATTACH USER EXIT 148 TASK CONTROL 169-170,26-27,10,38,116 TASK CONTROL AREA DSECT 214 TASK CONTROL ATTACH 37,148 TASK CONTROL PROGRAM 26,201 TASK CONTROL PROGRAM APCT 170 TASK CONTROL PROGRAM RETURNS CONTROL 153 TASK CONTROL PROGRAM SCP 51 TASK CONTROL TCA 42 TASK CONTROL WAIT MACRO INSTRUCTION 34 TASK INITIATION 99 TASK MANAGEMENT 1 TASK MANAGEMENT 2 TASKS MAXlflUM NUMBER OF 154,51,62 TASYS3 DFTRMLST BSCLST,O,2,1070,l,2D 3735 PROGRAMMABLE TA2770 187 TCA 169-171,159,161 TCA FACILITY CONTROL ADDRESS 120 TCADLECB 171 TCAFCAAA 211-212,215,120,126 TCAFCAAA FIELD 123 TCAM 32,62-65,70,72-73,75,56-57,61,144,146 142-143,137,24,123,139-141,143,145,147,149,151 190-191,54,206,15,202 CASE OF 64 DD CARD CORRELATION OF 139 UNDER CONTROL OF 2 TCAfI APPLICATION PROGRAM INTERFACE 138 TCAM APPLICATION PROGRAMS CURRENTLY ACTIVE 151 TCAM CONTROL BLOCKS 138 TCAM DEVICE CONSIDERATIONS 146 TCAM ENVIRONMENT 138 TCAM FACILITIES TAKE ADVANTAGE OF 146 TCAM HEADER 143,149 TCAM INPUT 57 TCAM INPUT PROCESS QUEUE 139,146-149 SEPARATE 146 TCAM INPUT QUEUE 145 TCAM LINE 144,67 TCAM LINES MIXED BTAM/TCAM MODE OF OPERATION WHEN 151 TCAM MCP 143,146-147,150 TCAM MCP MESSAGE HANDLER 146 TCAM MESSAGE CONTROL PROGRAM 190,138,144,147,151 PORTION OF THE 136 TCAM MESSAGE PROCESSING PROGRAM 190 TCAM OUTPUT PROCESS QUEUE 149,140.143.146.69 TCAM OUTPUT PROCESS QUEUE TCTLE 69 TCAM OUTPUT QUEUE 75 TCAM PARTITION/REGION PRESENCE OF A 150 TCAM PROCESS QUEUE 70,144 PARTICULAR 70 TCAM PROCESS QUEUES PROPER CONFIGURATION OF 145 TCAM PROGRAMMER GUIDE 136 TCAM QUEUE 140 TCAH TERHINAL MACRO INSTRUCTION HEANS OF A 144 TCAH TPROCESS BLOCK 13 6 TCAM USER EXITS 148,140-142 TCAM WORK AREA 146 COHPOSITION OF THE 149 STAGES OF THE 150 TCAM WORK AREAS DISCUSSION OF 149 TCAM WORK UNIT 61 TCAH WRITE MACRO INSTRUCTION 61 TCAM/CICS 192 TCAM/2260 DEVICE CONSIDERATIONS 147 TCAM/3270 DEVICE CONSIDERATIONS 148 TCAOCLA 159 TCAOCTR 161 TCAPCPI 170.211 TCAPCTR 170 TCATDAA 215 TCATDTR 171 TCEMCICM 123 TCEHCIDR 123 TCEMCIER 121 TCEHCIMB 123 TCEMCNOA 122 TCEMCOBE 122 TCEMCPL 121 TCEMCTO 122 TCEMCUI 121 TCEMCWOT 123 TCEHIDR 123 TCM3270 32,37,15,203 TCM7770 32,37,15,203 TCP 32.202.140,148.15,17,49.57.66.121,205 TCP HACRO INSTRUCTION 24,75 TCP PROGRAM ERROR 164 TCT 132.5,53,121,179.194,206,49,51,57.121,126 205 DURING PREPARATION OF THE TCT • • • TSP 51 TCT CODING 164 TCT END DFHTCTBA END OF 60 TCT SEARCH ERROR 162 TCT TERMINAL ENTRY 127 PARTICULAR 5 TCTLE 69,139,61,70.120,136,140 NUHBEa OF 69 187 226 TCTLE TIOABAR ADDRESS ADDRESS OF 119 TCTLE'S POOL OF 69 TCTLECSW 124,126 TCTLEDCB 124,126,128 TCTLEECB 124-127,121 TCTLEPCH 124 TCTLEPFL 124,121 TCTLEPF2 124-127 TCTLEPSA 124 TCTLEPTE 124-125,128 TCTLEQID 70 TeTTE 139,70,73.127-128,144.146,142-143,145,5,69 112.143,149,141 AREA OF THE 127 INDIVIDUAL 139-141,145,149 SPECIAL 139 TCTTE BASE REGISTER TIOABAR EQU 215 TCTTE FIELD 143 TCTTE HAY TCTTE TCTLEAR ADDRESS 119 ADDRESS OF TCTTE'S GENERALIZED 144 NUHBER OF 144 POOLED 144 TCTTEAR 211-212.215,128.119 TCTTECI 22,69 TCTTECIA 69,22,128 TCTTECIL 22,69 TCTTEDA 211-212.215 TCTTEDA FIELD 165 TCTTEDES 143 TCTTEMCI 137 TCTTENI 127-128 TCTTENO 127 TCTTETCM 143 TCTTETM 132 TCTTETT 132 TCTUA 19,22,14,201 TCTUAL 69-70,76.54-55,206-207,62 TCTUAL VALUE 76 TDIABAR 215 TDIADBA 215 TDP 15,17,39,203,49,205 TDP MACRO INSTRUCTION 41 TELECOMMUNICATIONS ACCESS METHOD 137,59,66 TEMPORARY STORAGE CONTROL 116 TEHPORARY STORAGE CONTROL PROGRAM 41-42,7,30 TEMPORARY STORAGE DATA SET 7,41 TEMPORARY STORAGE MANAGEMENT 2,4 TEMPORARY STORAGE PROGRAM 41 TElIPORARY STORAGE SERVICES 41 TEP 125,128,67 TERM 192-193,158 TERM CONTROL TABLE ADDRESS REG 211-212 TERMINAL 70,72-73,75-16,61-69,98-99,32,34,93 94,131,123,125-128,188,196,162-163,166-168,112 113-175,182-163,191,61-63,79-80,53-55,130 131,146,185,169,5.57-58.11,110,129,136,153 TERMINAL ABNORMAL CONDITION LINE ENTRY 120,124 TERMIN AL ABNORMAL CONDITION PROGRAM 23-24,162,169,176,178 TERHINAL ADDRESS 80 TERHINAL ADMINISTRATION FACILITIES 152 TERMINAL CONT TABLE DSECT 214 TERMINAL CONTROL 99,116,11 TERMINAL CONTROL 'PROGRAH 32,37,11,51,64,76,120,163,68 TERMINAL CONTROL PROGRAM FCP 51 TERMINAL CONTROL PROGRAM TCAM MODULE 37,148-149 TERHINAL CONTROL TABLE 163,172,55,22,53,76,79-80,111,132,206,68 75 DURING PREPARATION OF THE 35 END OF THE 71 EXTENSION OF THE 5 PREPARATION OF THE 131,194 SPECIFY END OF 77 TERMINAL CONTROL TABLE ASSEMBLY 55,71 TERMIN AL CONTROL TABLE CONFIGURATOR 194 TERMINAL CONTROL TABLE EXAMPLE 71 TERMINAL CONTROL TABLE LINE ENTRY 61,69,138-139 TERHINAL CONTROL TABLE HAcao INSTRUCTION 53,138 TERHINAL CONTROL TABLE PREPARATION EXAMPLES OF 179 TERHINAL CONTROL TCA ASSEHBLY OF 42 TERIIINAL CONTROL WRITE REQUESTS 127 TERIIINAL DEPENDENT CONTROL PROGRAH 44,204 TERMINAL ENTRY 66,71,122,125 TERHINAL CONTROL TABLE 70,13,75,112,139,144,171 TERHINAL ENVIRCNHENT 32-34,53 TERIIINAL ERROR PROGRAM 143,23,120.145-146,178 USER-WRITTEN 24,162 TERIIINAL ERROR PURGE INDICATOR 106 TERMIN AL FACILITY TASK TERMINATION PORTION OF THE HASTER 169 TERMIN AL FUNCTIONS REQUI BE MULTIPLE READ'S 144 TERIIINAL I/O AREA 165 TERHINAL I/O AREA ADDRESS L 211-212 TERMINAL I/O AREA ADDRESS REG 211-212 TERMINAL I/O AREA DSECT 214 TERHINAL IDENTIFICATION DFHTLT TYPE 114,209 TERMINAL IDENTIFICATIONS 113,34,61.17,114 LIST OF 114 TERMINAL INPUT/OUTPUT AREA MINIHUM SIZE OF THE 16 HINUHUH SIZE OF THE 64 TERMINAL LIST HACRO STATEflENT LABEL OF THE BTAfI DEFINE 66 TERflINAL LIST TABLE 113-114,28,43,114-115 END OF THE 115 SPECIFY END OF 115 TERflINAL LIST TABLE ASSEMBLY 114 TERflINAL LIST TABLE CONTROL SECTION 114 TERflIN AL LIST TA BLE EXAfI PLE 115 TERflINAL flACRO INSTRUCTION 61,63,65-66,69-70,131-132, 98,132,144 TERMINAL MANAGEMENT 8 64,71,132 TERMINAL MODEL NUMDER TERMINAL OPERATOR 157-158,129,75,112,152 TER MINAL OPERATOR GUIDE 152 TERMINAL REQUEST 162,73 TERMINAL SPECIFICATION 69,71 TERMINAL STATISTICS PROGRAM 23 TERMINAL STATUS 73 TERMINAL SYSTEM 75,184 TERMINAL SYS3D DFHTCT TYPE 187 TERMINAL TEST PROGRAM 177 TERMINAL TEST '1 4 163,72,75,63,70,132 TERMINAL TYPE TERMINAL IIRITE STORAGE 165-166 TERMINAL/2760 OPTICAL IMAGE UNIT COMBINATION 75 TERMINATE CICS 63,153,155,150 TERMIN ATE ENTRIES 100 TERIIINATING JCL 44 TERIIINATION PROGRAM 11 TERMTST 56,59-60,54,206 TEST 211,215,138 TEST MODULE 10 TIME 162,120,131,145 SPECIFIED INTERVAL OF 30,1 TIllE ADJUSTMENT PROGRAM 23,157 TIME INTERVAL 153 STALL TIME MANAGEMENT 1,4 TIME OUT 166-167,34,174 TIllE OUT ERROR CONDITIONS 166 TIllE SHARING OPTION 138 TIIIECTL 19-20,29,13,201 TIIIEOUT CONDITION 137 TIOA 150,64,75-76,140,145,149,165 TIOATDL FIELD OF THE 165 TIOA CONTAINS 149 TIOA CORRESPONDS SIZE OF THE 76 TIOA DFHFCP TIOA 1I0RK AREA 149 TIOA XINPUT ADDRESS OF 119 TIOA XOUTPUT ADDRESS OF 119 TIOABAR 211-212,215 TIOADBA 211,213-215,130 TIOADBA POINTS 149 TIOATDL 130,149,215,122 TLT 42-43,113,209,16,204 TOTCAII 192-193 TPMARK 95-96,94,208 TPROCESS BLOCK 138 TPROCESS CONTROL BLOCK CONTROLS COIIIIUNICATION 138 TPROCESS PCB 192 TPURGE 106-107,105,209 TRACE 19-20,154,13,28,50,192,201 TRACE CONTROL PROGRAM 23 TRACE FACILITY 50 TRACKS NUMBER OF 84-85 TRANS 17,192 TRANSACTION 165-168,172-174,70,73,75-76,136,130,129,204 106,111,62,64,130,1,3,5,9,46,48,55 77,123,132,144,152,154,207 2260-COMPATIBLE 130-131 TRANSACTION CODE 136,75,211 TRANSACTION CODE CSXX 177 TRANSAC'UON CONTROL PilOGRAII 44,169,177 TRANSACrION CSIIT DETAILED DESCRIPTION OF THE USE OF THE 11 TRANSACTION CSTA 157 TRANSACTION ID 129 TRANSACTION IDENTIFICATION 162,148,155 TRANSACTION INFUT PROCESSING DFHRD2 177 TRANSACTION INPUT PROCESSING PROGRAIIS 44 TRANSACTION OUTPUT PROCESSING DFHWT2 178 TRANSACTION OUTPUT PROCESSING PROGRAMS 44 TRANSACTION PRIORITY 106,71,104 TRANSACTION PROCESSING 22,146,156 TRANSACTION PROCESSING CONTROL PROGRAM 53 TRANSACTION PROCESSING FACILITY 177-178,53,176 TRANSACTION PROCESSING GROUP 44 TRANSACTION PROCESSING PRIORITY 71,106 TRANSACTION PROCESSING 9 4 TRANSACTION PROGRAII CONTROL TABLE 111 TRANSACTION ROLLOUT DATA SET 6 TRANSACTION STATUS 73 TRANSACTION TERIIINAL 73 TRANSACTION WORK AREA 106 LENGTH OF THE 104 SIZE OF THE 105 SIZE OF THE LARGEST 211 TRANSACTION XXXX ABEND XXXX 169 TRANSACTION YYYY 163-168 TRANSACTIONS EXArlPtES OF USER-IIRITTEN 211 TRANSACTIONS CSAC 177 TRANSACTIONS CSFE 177 TRANSCEIVE 70,73,80,55,180-188,207 TRANSCEIVl! DFHTCT TYPE 80,184-185,189,79,180 TRANSCEIVE STATUS 73 TRANSCODE 32,35,68,56,54,206,62,15,203 TRANSCODE INDICATES TRANSIIISSION 59 TRANSDATA 160,159,210,161 TRANSDATA ENTRY TRANSEC 106-107,105,209 TRANSID 107,98-99,70,75,180,55,94,101,105,137,176 181,188,207-209 TRANSID OPERAND 75,99 LAST SPECIFICATION OF THE 75 TRANSID PARAIIETER 176 TRANSID SPECIFICATION 75 TRANSIENT 93,100 TRANSIENT DATA 171,124,130,178 TRANSIENT DATA CONTROL 99,116,129 TRANSIENT DATA CONTROL PROGRAM 39-40,7,93,176 TRANSIENT DATA CONTROL PROGRAII DEING 40 TRANSIENT DATA CONTROL PllOGRAM 3 25 TRANSIENT DATA EXTRAPARTITION DATA SET TRANSIENT DATA INPUT/OUTPUT AREAS 6 154,153 TRANSIENT DATA INTRA PARTITION DATA SET TRANSIENT DATA MACRO INSTRUCTION 98-99,97 TRANSIENT DATA MANAGEIIENT 2,155,158 TRANSIENT DATA IIANAGEIIENT 10 4 51 TRANSIENT DATA PROGRAII TRP TRANSIENT DATA PURGE IIACRO INSTRUCTION 98 TRANSIENT DATA SERVICES 40 TRANSINIT 39,15,203 TRANSLATE ERROR 163 TRANSMIT READL 147 TRC 56 TRIGLEV 98-99,94,101,208 70,73,137,80,185,180,55,184,187-188,207 TRIIADDR 191,79-80,182-183,185,189,115,180,189,55,70 TRIIIDNT 114,181,184,186-188,207,209 TRIIIDNT PARAMETER . 71 62,64-65,70-72,75,184-185,54-55,185,206 TRIIIIODL 207,80,180,189 TR!!MODL MAY 196 65 TR!!MODL PARAIIETER 65 TR!!1I0DL PARAIIETER SETS 191,79-80,182-183,185,189,70-71,180,55,181 TRMPRTY 184,186-180,207 TR!!TYPE 62-63,70,72,75,69,137,182-183,191,79,180 185,54-55,80,186-189,206-207,179,181,184,188 TRIITYPE OPERAND 63 USE OF THE 63 TRIITYPE OPERAND MUST 63 TRMTYPE SPECIFICATION 72 TRNPRTY 107,106,105,209 TRNSUFX 97,100,95,102-103,94,208 TRP 49,51,205 TRT 49-50,205 TSBLK 49-50,205 TSDA 119 TSEGIND 89,81,92,208 TSO 138 TSP 16-17,41,203,30,49,205 'lilA 159,211 FIRST BYTE OF THE 159-160 'lilA CONTAINS 129 TWACOBA 129 TWASIZE 106,176,107,105,209 TIIX 70,72-73,32-33,184,67,162,179,54-55,62 63,206-207,15,197,203 TlIXAUTO 184 TW33 54,56,206 '11135 54,56,184,206 TYFULE 95-96,102-103,94,208 -U- U/R 54-55,62-63,70,72,206-207 32-33,35,70,75,131,148,15,55,57,203,207 UNIQUE NAME DFHTRNXX 97 UNIT CHECK 166;122,125 UNIT CHECK ERROR 166 UNIT ERROR 166-168,173,122 UNIT EXCEPTION 167-168,122,125,129 UNLOAD 95-96,94,200,212 UPDATE 82-83,81,92,207 UPDATE DAM 4 38 UPDATE ISAII 5 38 USE OF THE CICS/TCAM INTERFACE ONE PRACTICAL 138 USER DATA BASE CONSIDERATIONS 7 USER EXIT 10,116,70,141,149 USER EXIT ENTRY 117 USER EXIT ENTRY SAVE 117 USER EXTRAPARTITION DATA SETS USER FIELD 127-128 USER MUST PROVIDE 19,149,157 USER SPECIFIES 18,149 USER SPECIFIES V1CMPAT 129 USER TIOA 130 USER TRANSACTION DATA 140 USER IIRITTEN ASSEMBLER LANGUAGE PROGRAIIS 22 USER WRITTEN EXIT ROUTINE 37 USER DATA 66 UTIPL 130 UZERO 130 -V- V 41,56,61,54,206 V EXIT FRAMENO DC 214 VALID 57-58,60,48 VALID CODES 169-171 VALID ENTRIES 96 VALID TERIIINAL IDENTIFICATION 77 VALID TERIIINAL IDENTIFICATION BEING 76 VARBLK 95-96,94,208 VARIABLE 19,22,14,69,87,90,92-93,201 VARIABLE LENGTH 90,22,69,87 VARIABLE LENGTH BECORDS 96 VARIABLE LENGTH-RECORDS 13 38 VARIABLE-LENGTH ISAM RECORDS 199 VARIABLE-LENGTH PCI FIELD CASE OF A 69 VARIABLE-LENGTH RECORD DATA SET MUST 9 VARIABLE-LENGTH RECORD PORMAT CONVENTIONS 360/370 9 VARIABLE-LENGTH RECORDS 8,61,83-87 VARUNB 95-96,94,102,104,200 VIDEO 62-63,54-55,70,72,206-207,189 VIRTUAL 41,16,203 227 SPECIFICATION OF 41 VRC/LRC FEATURE 67 VS ENVIRON~ENT 21 Vsl 13,19,201 VS2 13,19,201 V1C~PAT 23-24,14,19,201 V1CO~PAT 14,19 V2 14,28,202 V3 28,14,202 V4 14,28,202 2740 57.58,67,75,33,79-80,180,197-198 2740 CO~~UNICATION TER~INAL 67,64-65,71,57,179 2740 CO~~UNICATION TER~INAL ~ODEL 2 64-65,33,67,71 2740 CO~~UNICATION TER~INAL ~ODELS 1 33 2740 ~ODEL 2 197-198 2740 MODEL 2 4 34 2740 TER~INAL ENTRY 80 2740, 2740/2760,2741C, 2741E, 2770,2780,2982 54-55,206-207,62,70 2740D 33 2741 CO~~UNICATION TER~INAL 33,179,99 2741C 181,33 2741DC 2741 CO~~UNICATION TER~INAL 33 2741E 33 2760 212,33,75,181,197-198 2760 OPTICAL I~AGE UNIT 58,65,71,179 2760 PARA~ETER OIU 147 2760 TRANSACTION Tl030 EXA~PLE OF A 211 2770 186-187,33 2770 DATA CO~~UNICATION SYSTE~ 33,146,179 2770 DATA COM~UNICATION SYSTE~ 21 33 2770D 33 2780 186,33,58 2780 DATA TRANS~ISSION TERMINAL 33,146,186 2780D 33 2845/2848 DISPLAY CONTROL 135 2845/2848 TAB FEATURE 135 2848 CONTROL UNIT ~ODEL 21 147 2848 DISPLAY CONTROL 1I0DELS 21 67,135 2848 DISPLAY CONTROL 5 LOCA L/REMOTE 33 2848 LOCK FEATURE 135 2848 MODELS 21 35 2980 ADHINISTRAT.J:VE STATION ~ODEL 2 65,71 2980 GENERAL BANKING TER~INAL SYSTE~ 74,179 2980 TELLER STATION ~ODEL 1 65,71 2980 TELLER STATION ~ODEL 4 65,71 32-SECOND TI~EOUT AS 3210 130-131,35-36,74-75,133,69,106,122,125,148,173 3270 BASIC ~APPING SUPPORT 117 3210 INFOR~ATION DISPLAY SYSTE~ 35-37,71,74,172-173, 179,65,106,185 3270 OPERATING UNDER CICS CO~PATIBILITY 135 3270 PARAMETERS READB 147 3275 DISPLAY STATION 74,33,66,132 BUPFER OF THE 74,132 3275 DISPLAY STATION MODEL 1 65,71 3275 DISPLAY STATION ~ODEL 2 65,71 3277 DISPLAY STATION 74,33,172 3277 DISPLAY STATION ~ODEL 1 65,71 3277 DISPLAY STATION ~ODEL 2 65,71 3284 ~ODEL 3 PRINTER 132 3284 PRINTER 33,74 3284 PRINTER ~ODEL 1 65,71 3284 PRINTER 1I0DEL 2 65,71 3284 PRINTER ~ODEL 3 74 3286 PRINTER 33,74 3286 PRINTER ~ODEL 1 65,71 3286 PRINTER 1I0DEL 2 65,71 360N-CB-482 28 360S-CB-545 28 360S-CQ-548 32 3735 5734-CBl 28 5734-CB2 28 5734-xx6 2,9 5736-CBl 28 5736-CB2 28 7770 181-183,63,68,76-77,33-34,59,61,129 7770 AUDIO RESPONSE UNIT 68,34,36-37,76-77,129,174 7770 CHANNEL/ABNOR~AL END APPENDAGE PROGRA~ 23 7770 ~ODEL 3' S 60 7770 OPERANDS 24 7770 READ/liRITE PROGRA~ 23 7770 SVC PROGRA~ 23 7770 SVC ROUTINE 24 7770 32-SECOND TIIIEOUT t22. 7770 32-SECOND TI~EOUT CONSIDERATIONS 129 7770~SG 182-183,55,76,207 7770~SG ~ACRO INSTRUCTION 68 7770NULL 34 7770TERM 34 -W- WAIT 130,147 WORK AREA 61,6,42,85,149 STATIC 85 WORK UNIT 61,149 WRAPLST 32-33,35,15,57,203 WRITE 163,165,173-174,130,147,42,146,213-215,69,76 124,135 WRITE ABORT BIT 127 WRITE CONTROL CHARACTER 148 WRITE DATA RECORD 215 WRITE ~ACRO INSTRUCTION 135,143,60,142 WRITE ~ACRO INSTRUCTION CAN 143 WRITE OPERATIONS 69 WRITE REQUEST 165-166,173-114,121,142,86 WRITE ST 215 WRITE TR 137 WRITEL REQUESTS 147 WRITES TER~INAL I/O ERROR ~ESSAGES 176 WRKAREA 42,16,204 WRKAREA OPERAND 42 -X- XATTACH 148,32,37,15,119,203 XDSPCHR 26-27,14,119,202 XFETCH 28,14,119,202 XICEEXP 29-30,15,119,202 32-33,37,15-16,38-42,57,203 XINPUT PLACE OF THE 148 XINPUTC 38-39,15,203 32-33,37,15-16,119,38-41,57,203 XOUTPUT XOUTPUT EXITS 148 148,140,149,32,37,15,140,203 XTC~IN 148-149,32,37,15,142,203 XTC~OUT 143 XTC~OUT USER EXIT XTYPREQ 14-16,117,119,26-27,29-30,38-41,202-203 -Y- YES OPERAND YES OPTION 29-30,35,100,103-104,157,31,39-40,42,95 144 -Z- ZERO 8E OUTPUT LENGTH OF 125 ZONED DECI~AL RELATIVE TRACK 38 184-185,33,164-165,23,38,107,124,153,192,212 -NU~ERIC- 1030 1030 1030 1030 1030 179-180,18,33,195-196 BADGE READER 2 75 DATA COLLECTION SYSTE~ 179 DATA COLLECTION SYSTE~ 2 33 TRANSACTION EXA~PLE OF A 211 1050 80,33,67 1050 CO~~UNICATION SYSTE~ 67 1050 DATA CO~~UNICATION SYSTE~ 65,71,33 1050 TER~INAL ENTRY 80 1050D 33 1053 72,74,33,79,180,189 1053 PRINTER 33,72,74,57,131 1053 PRINTER ~ODEL 4 63 2260 74,32-33,57,180,15,131-133,135,147.202 2260 CO~PATIBILITY 74-75,130,106,131 2260 CO~PATIBILITY ~ODE 36,106,177 2260 °DFHTCT TYPE 191 2260 DISPLAY STATION 33,179,188,65,72 960-CHARACTER 36 2260 DISPLAY STATION UNDER CICS/DOS 62,64 2260 DISPLAY STATION 2 240-CHARACTER 36 2260 DISPLAY STATION 7 64,71 2260 ~ODEL-DEPENDENT DATA STREAl! 132 2260 PARMETERS WRITEL 147 2260 SCREEN 132-133 2260 TER~INAL ENTRY 79 2260-BASED TRANSACTION 36,133 2260/2265 DISPLAY STATION AS FOLLOWS 65,72 2260/2265 TER~INAL 74,131 SCREEN SIZE OF THE 74,131 2265 DISPLAY STATION 64 2265 DISPLAY STATION F~T3270 36 2265 DISPLAY STATION TR~~ODL 71 2265 DISPLAY STATION 12 33 2265 DISPLAY STATION 4 36 2314 79,188,50,85,96 2314 DIRECT ACCESS STORAGE FACILITY 188 2701 56,59,180 2703 59,79-80,180-181,184,186-187 228 SH20-1043-6 Q (') ~ en -< en .-+ CD 3 .,-c 0 ~ Q) 3 3 ~ en" ::0 CD :"'" !S: Q) ~ .,-c 5· .-+ CD a. 5· c en ~ en :c I\J 9..... 0 .;::. tAl m International Business Machines Corporation Data Processing Division 1133 Westchester Avenue, White Plains, New York 10604 (U.S.A. only) IBM World Trade Corporation 821 United Nations Plaza, New York, New York 10017 (International)
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.3 Linearized : No XMP Toolkit : Adobe XMP Core 4.2.1-c043 52.372728, 2009/01/18-15:56:37 Producer : Adobe Acrobat 9.31 Paper Capture Plug-in Modify Date : 2010:03:20 09:02:37-08:00 Create Date : 2010:03:20 09:02:37-08:00 Metadata Date : 2010:03:20 09:02:37-08:00 Format : application/pdf Document ID : uuid:4755800d-cdbe-48a9-80c6-75f84e9e3dcb Instance ID : uuid:57ec57a8-dce4-4bbe-a319-680093ef334e Page Layout : SinglePage Page Mode : UseNone Page Count : 246EXIF Metadata provided by EXIF.tools