DOCSLIB.ORG

CICS TS for Z/OS 4.2: Operations and Utilities Guide Chapter 15

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
CICS TS for Z/OS 4.2: Operations and Utilities Guide Chapter 15 CICS Transaction Server for z/OS Version 4 Release 2 IBM Operations and Utilities Guide SC34-7213-01 CICS Transaction Server for z/OS Version 4 Release 2 IBM Operations and Utilities Guide SC34-7213-01 Note Before using this information and the product it supports, read the information in “Notices” on page 223. This edition applies to Version 4 Release 2 of CICS Transaction Server for z/OS (product number 5655-S97) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright IBM Corporation 1989, 2014. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Preface .............. vii Chapter 5. How to shut down CICS .. 29 What this book is about .......... vii CICS shutdown ............. 29 Who should read this book?......... vii Normal shutdown (PERFORM SHUTDOWN) .. 30 What you need to know to understand this book vii Immediate shutdown (PERFORM SHUTDOWN How to use this book ........... vii IMMEDIATE)............. 31 Notes on terminology ........... vii Shutting down CICS normally ........ 32 Softcopy links ............. viii Shutting down CICS immediately ....... 33 Shutdown command options ........ 34 Changes in CICS Transaction Server for z/OS, Version 4 Release 2 ....... ix Part 2. The CICS utility programs 35 Part 1. Operating CICS regions ... 1 Chapter 6. Reading log streams using batch jobs (for example, DFHJUP) ... 37 Chapter 1. Overview of CICS operations 3 SUBSYS=(LOGR,DFHLGCNV,...) keyword .... 37 What happens when you start CICS ...... 3 Using the SETBRCUR, REPBRCUR and The types of CICS startup ......... 3 DELBRCUR options for log stream processing .. 44 CICS actions on an initial start ....... 4 Using DFHJUP to read log streams ...... 45 CICS actions on a cold start ........ 4 DD statements for DFHJUP or your own batch job 46 CICS actions on a warm start ........ 5 Utility control statements for DFHJUP ..... 47 CICS actions on an emergency restart ..... 8 CONTROL statement .......... 48 CICS startup and the z/OS Communications OPTION statement ........... 49 Server session ............. 9 Options............... 49 End of CICS startup ........... 9 END statement ............ 54 Controlling CICS operation ......... 9 COMMENTS statement ......... 54 DFHJUP return codes ........... 54 Chapter 2. Starting up CICS regions .. 11 Managing the size of log streams ....... 54 System log ............. 54 Specifying system initialization parameters before General logs ............. 55 startup ................ 11 Log data accessible to DFHJUP ........ 55 The START system initialization parameter ... 12 Example of log data that is accessible to DFHJUP 56 Starting CICS as a batch job ......... 12 Diagnostic information in DFHJUP output .... 56 Starting CICS as a started task ........ 13 Examples of using DFHJUP ......... 57 Overriding system initialization parameters during Example 1 .............. 57 startup ................ 15 Example 2 .............. 58 Entering corrections to parameters at the console 15 Example 3 .............. 59 System console messages for CICS startup .... 16 Example 4 .............. 59 CICS Transaction Server resource usage collection Examples of the use of the OPTION parameters 60 for software pricing............ 19 Version 4 Release 2 format ........ 61 COMPAT41 format ........... 62 Chapter 3. Operating CICS in a OPTION parameter values ........ 64 multiregion environment ....... 21 Chapter 7. Statistics utility program Chapter 4. Operating CICS from a (DFHSTUP) ............. 67 console device ........... 23 Setting the statistics recording status, end-of-day Entering commands from a console device .... 23 time and recording interval ......... 67 Entering commands from TSO ....... 24 Support for Katakana devices ........ 69 Using JCL to initiate CICS commands ..... 24 Job to run the DFHSTUP program ....... 69 Console device messages .......... 25 The DFHSTUP extract statistics reporting function 72 Console message-formatting ........ 25 The DFH0STXR sample program ...... 72 Replying to messages .......... 26 The DFH0STXD sample program ...... 74 Replying to messages from transactions started at Using the extract statistics reporting function .. 76 console devices ............ 26 Control parameters of the DFHSTUP program... 78 Suppressing and rerouting messages ..... 27 © Copyright IBM Corp. 1989, 2014 iii Chapter 8. Recovery statistics program DFH$MOLS control statement descriptions ... 130 (DFH$STER) ............ 87 Abend codes and error messages for DFH$MOLS 138 Recovery Manager domain recovery messages... 87 101: INVALID, DUPLICATE, OR MISSING Statistics sample program, DFH$STER ..... 88 CONTROL CARD INFORMATION ..... 138 Installing DFH$STER ........... 88 102: ERROR - INCOMPATIBLE CONTROL CARD OPTIONS REQUESTED ...... 138 Chapter 9. Trace utility print program 103: SORT ENDED WITH NON-ZERO RET CODE; RC='nn'; REPORT IS TERMINATED .. 138 (DFHTU670) ............ 89 104: NO DATA FOR THIS CICS DATA The CICS trace utility program, DFHTU670 ... 89 SECTION; REPORT IS TERMINATED .... 139 The trace selection parameters for DFHTU670 ... 90 105: UNKNOWN CLASS IN CICS DATA Identifying trace entries from their SECTION; REPORT IS TERMINATED .... 139 transaction-attach entries ......... 95 106: NO VALID MONITORING RECORDS Rules for coding trace selection parameters ... 95 WERE READ; REPORT IS TERMINATED ... 139 Using IPCS to print trace records written to GTF .. 97 107: NO MONITORING RECORDS WERE The GTFTRACE subcommand of IPCS and SELECTED FOR PROCESSING; REPORT IS associated parameters .......... 97 TERMINATED ............ 139 Sample batch job to print CICS GTF trace entries 98 108: X‘nnnn’ - CONNECTOR NOT DEFINED; Invoking the CICS formatting routine from TSO 99 REPORT IS TERMINATED ........ 139 109: NO DICTIONARY ESTABLISHED; Chapter 10. Dump utilities (DFHDU670 REPORT IS TERMINATED ........ 140 and DFHPD670) .......... 101 110: NO DICTIONARY ESTABLISHED FOR Selecting output for the transaction dump utility NEW APPLID xxxxxxxx; REPORT IS program (DFHDU670) .......... 101 TERMINATED ............ 140 Format of the SYSIN control statements ... 102 112: There is no message text, but MVS abends Job control statements for the transaction dump U112 without a dump. ......... 140 utility program (DFHDU670) ........ 105 113: UNABLE TO OPEN DDNAME ‘INPUT’; Using IPCS to format and analyze CICS dumps: REPORT IS TERMINATED ........ 140 Overview............... 106 114: UNABLE TO OPEN DDNAME ‘xxxxxxxx’; Preparing to use IPCS to format CICS SDUMPs 107 REPORT IS TERMINATED ........ 141 The SDUMP options needed to support the 116: NO FILE RESOURCE ENTRIES..... 141 CICS dump exit ........... 107 117: NO TSQUEUE RESOURCE ENTRIES ... 141 Specifying DFHIPCSP CICS exit control data 118: UNABLE TO EXPAND A COMPRESSED needed .............. 108 RECORD, RC='nn'; REPORT IS TERMINATED . 141 Making the required CICS dump exit routines 119: UNABLE TO OPEN DDNAME 'xxxxxxxx'; available .............. 109 REPORT IS TERMINATED ........ 141 Selecting parts of the CICS internal trace table .. 109 120: UNEXPECTED CSRCESRV QUERY Using CICS-supplied dump exit routines to format ERROR, RC='nn'; REPORT IS TERMINATED .. 142 CICS SDUMPs ............. 110 121: NO DPL RESOURCE ENTRIES ..... 142 The CICS dump exit parameters ...... 111 Exceptions to the scope of the DEF parameter 112 Chapter 13. Load module scanner Examples of the use of level numbers .... 112 (DFHEISUP) ............ 143 The CICS670 dump exit component keywords 113 Creating a filter input file for the load module The dump summary and error index ..... 114 scanner ............... 144 Sample jobs to process a CICS SDUMP using the Creating a summary report using the load module CICS dump exit ............ 115 scanner ............... 147 Creating a detailed report using the load module Chapter 11. Monitoring dictionary scanner ............... 149 utility program (DFHMNDUP) ..... 119 Activating trace for the load module scanner ... 153 Generating a performance dictionary record using DFHMNDUP ............. 119 Chapter 14. Batch-enabling sample Parameters for the DFHMNDUP program .... 121 programs for RLS access-mode data Sample job illustrating the use of DFHMNDUP 122 sets (DFH0BATx) .......... 155 Preparing data sets for batch operations using the Chapter 12. Sample monitoring data DFH0BATx sample programs ........ 156 print program (DFH$MOLS) ..... 125 Installing the DFH0BATx sample programs .. 158 Processing CICS monitoring data ....... 126 Preparing input for the DFH0BATx sample Sample job stream for DFH$MOLS ...... 127 programs .............. 158 DFH$MOLS control statements summary .... 128 Rules for coding DFH$MOLS control statements 130 iv CICS TS for z/OS 4.2: Operations and Utilities Guide Chapter 15. Identify macro-level Setting an initial start without operator programs utility program intervention ............. 195 (DFHMSCAN) ........... 161 Examining the override record ...... 195 Resetting a warm or emergency start .... 196 How DFHMSCAN works ......... 161 Improving the performance of a cold start... 196 JCL to run DFHMSCAN.......... 162 Producing a summary report from DFHMSCAN 162 Producing a detailed report from DFHMSCAN .. 163 Chapter 20. BMS macro generation Limitations of the DFHMSCAN program .... 164 utility program (DFHBMSUP) ..... 199 DD statements for DFHBMSUP ....... 199 Chapter 16. Stagger end-of-day time Return codes from DFHBMSUP ....... 199 sample utility program (DFH$STED).. 165 Example of using DFHBMSUP ....... 200 Example of DFHBMSUP
Load more

Recommended publications
  • Cloud Enabling CICS
    Front cover Cloud Enabling IBM CICS Discover how to quickly cloud enable a traditional IBM 3270-COBOL-VSAM application Use CICS Explorer to develop and deploy a multi-versioned application Understand the benefits of threshold policy Rufus Credle Isabel Arnold Andrew Bates Michael Baylis Pradeep Gohil Christopher Hodgins Daniel Millwood Ian J Mitchell Catherine Moxey Geoffrey Pirie Inderpal Singh Stewart Smith Matthew Webster ibm.com/redbooks International Technical Support Organization Cloud Enabling IBM CICS December 2014 SG24-8114-00 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (December 2014) This edition applies to CICS Transaction Server for z/OS version 5.1, 3270-COBOL-VSAM application. © Copyright International Business Machines Corporation 2014. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . vii Trademarks . viii IBM Redbooks promotions . ix Preface . xi Authors. xii Now you can become a published author, too! . .xv Comments welcome. .xv Stay connected to IBM Redbooks . xvi Part 1. Introduction . 1 Chapter 1. Cloud enabling your CICS TS applications . 3 1.1 Did you know?. 4 1.2 Business value . 4 1.3 Solution overview . 5 1.4 Cloud computing in a CICS TS context. 6 1.5 Overview of the cloud-enabling technologies in CICS TS V5 . 11 1.5.1 Platform overview . 12 1.5.2 Application overview . 13 Chapter 2. GENAPP introduction. 15 2.1 CICS TS topology . 16 2.2 Application architecture. 17 2.2.1 GENAPP in a single managed region.
    [Show full text]
  • Syncsort for Z/VSE Programmer's Guide Release
    All rights reserved. This document contains proprietary and confidential material, and is only for use by licensees of the SyncSort for z/VSE proprietary software system. PROVEN performance SyncSort for z/ VSE Programmer's Guide Release 3. 7 SI-0328-G SyncSort is a registered trademark of Syncsort Incorporated 070809 © Syncsort Incorporated, 2009 All rights reserved. This document contains proprietary and confidential material, and is only for use by licensees of the SyncSort proprietary software system. This publication may not be reproduced in whole or in part, in any form, except with written permission from Syncsort Incorporated. SyncSort is a trademark of Syncsort Incorporated. All other company and product names used herein may be the trademarks of their respective companies. Table of Contents Summary of Changes . v Performance Improvements . v Data Utility Features. v Operating System . vi Messages. vi Chapter 1. Introduction . 1.1 An Introduction to SyncSort for z/VSE. 1.1 SyncSort’s Basic Functions . 1.1 SyncSort’s Data Utility and SortWriter Features . 1.2 Join Processing Sequence . 1.5 Sample SortWriter Report. 1.6 SyncSort’s Operational Features. 1.7 Structure of the Programmer’s Guide. 1.7 Related Reading. 1.9 Chapter 2. SyncSort Control Statements . 2.1 Control Statement Summary Chart . 2.3 Data Utility Processing Sequence. 2.17 Maximum Record Length Allowed . 2.23 Control Statement Examples . 2.25 Rules for Control Statements . 2.25 ALTSEQ Control Statement . 2.30 ANALYZE Control Statement. 2.32 DUPKEYS Control Statement . 2.33 Table of Contents i END Control Statement. 2.38 INCLUDE/OMIT Control Statement .
    [Show full text]
  • 13347 CICS Introduction and Overview
    CICS Introduction and Overview Ezriel Gross Circle Software Incorporated August 13th, 2013 (Tue) 4:30pm – 5:30pm Session 13347 Agenda What is CICS and Who Uses It Pseudo Conversational Programming CICS Application Services CICS Connectivity CICS Resource Definitions CICS Supplied Transactions CICS Web Services CICS The Product What is CICS? CICS is an online transaction processing system. Middleware between the operating system and business applications. Manages the user interface. Retrieves and modifies data. Handles the communication. CICS Customers Banks Mortgage Account Reconciliations Payroll Brokerage Houses Stock Trading Trade Clearing Human Resources Insurance Companies Policy Administration Accounts Receivables Claims Processing Batch Versus Online Programs The two ways to process input are batch and online. Batch requests are saved then processed sequentially. After all requests are processed the results are transmitted. Used for order entry processing such as warehouse applications. Online requests are received randomly and processed immediately. Results are transmitted as soon as they are available. Response time tends to be sub-second. Used for applications – such as: Credit Card Authorization. Transaction Processing Requirements Large volume of business transactions to be rapidly and accurately processed Multiple users, single/sysplex or distributed With potentially: – A huge number of users – Simultaneous access to data – A large volume of data residing in multiple database types – Intense security and data integrity controls necessary The access to the data is such that: – Each user has the perception of being the sole user of the system – A set of changes is guaranteed to be logically consistent. If a failure occurs, any intermediate results are undone before the system becomes available again – A completed set of changes is immediately visible to other users A Business Transaction A transaction has a 4-character id.
    [Show full text]
  • Introduction-To-Mainframes.Pdf
    Mainframe The term ‘MainFrame’ brings to mind a giant room of electronic parts that is a computer, referring to the original CPU cabinet in a computer of the mid-1960’s. Today, Mainframe refers to a class of ultra-reliable large and medium-scale servers designed for carrier-class and enterprise-class systems operations. Mainframes are costly, due to the support of symmetric multiprocessing (SMP) and dozens of central processors existing within in a single system. Mainframes are highly scalable. Through the addition of clusters, high-speed caches and volumes of memory, they connect to terabyte holding data subsystems. Mainframe computer Mainframe is a very large and expensive computer capable of supporting hundreds, or even thousands, of users simultaneously. In the hierarchy that starts with a simple microprocessor at the bottom and moves to supercomputers at the top, mainframes are just below supercomputers. In some ways, mainframes are more powerful than supercomputers because they support more simultaneous programs. But supercomputers can execute a single program faster than a mainframe. The distinction between small mainframes and minicomputers is vague, depending really on how the manufacturer wants to market its machines. Modern mainframe computers have abilities not so much defined by their single task computational speed (usually defined as MIPS — Millions of Instructions Per Second) as by their redundant internal engineering and resulting high reliability and security, extensive input-output facilities, strict backward compatibility with older software, and high utilization rates to support massive throughput. These machines often run for years without interruption, with repairs and hardware upgrades taking place during normal operation.
    [Show full text]
  • IBM Z Open Automation Utilities Provides New Services to Help Developers Work with IBM Z/OS Data Sets Directly from the Shell, Java, Or Python
    IBM United States Software Announcement 220-087, dated February 18, 2020 IBM Z Open Automation Utilities provides new services to help developers work with IBM z/OS data sets directly from the shell, Java, or Python Table of contents 1 Overview 3 Technical information 2 Key requirements 3 Ordering information 2 Planned availability date 5 Terms and conditions 2 Program number 9 Prices 2 Publications 9 Order now At a glance IBM Z(R) Open Automation Utilities helps z/OS(R) developers to automate tasks that access z/OS resources. It enables easier calling of z/OS utilities compared with JCL by providing a natural coding experience on UNIX System Services (USS) and interfaces in modern programming languages. Overview Job Control Language (JCL) has been used for a long time for performing or automating a set of steps on the IBM(R) z/OS operating system. Though JCL has evolved with the times, it is inevitably foreign to people familiar with environments such as Linux(R), UNIX, and Microsoft Windows. On z/OS, as an alternative to using JCL, developers can write scripts to automate tasks in the USS environment. Such scripts are easier to understand and to manage, and many open source tools are also available in USS. However, there is a gap in some cases, and z/OS developers have to fall back to submitting JCL jobs, which requires z/OS specific knowledge. In addition, JCL jobs are asynchronous, which means you must submit them to batch and wait for the result; thus, they do not fit in well with the rest of the script, which is typically synchronous.
    [Show full text]
  • 9228 Brown/JCL 01.K.Qxd 5/1/02 11:39 AM Page 1
    9228 Brown/JCL 01.k.qxd 5/1/02 11:39 AM Page 1 CHAPTER 1 INTRODUCTION 1.1 THE SHOCK OF JCL Your first use of JCL (Job Control Language) will be a shock. No doubt you have used personal computers costing $500 or $1,000 that had wonderfully human-engineered software, giving you an expectation of how easy it is to use a computer. Now, as you use a computer costing several million dollars, you may feel like a waif in a Dickens story standing in the shadow of a mas- sive mainframe computer saying meekly, “Please, sir, may I run my job?” It will come as a shock that its software is not wonderfully human engi- neered. The hardware and software design of large IBM mainframe computers date back to the days when Kennedy was president. JCL is a language that may be older than you are. It was designed at a time when user-friendliness was not even a gleam in the eye of its designers. This is easily demonstrated by taking the simple task of copying a file and contrasting how it is done through JCL with how it is done on the most popular personal computer system, Windows. To copy a file with Windows, you left-click twice on the MY COMPUTER icon, left-click on the C: drive icon, left-click twice on the folder containing the file, and right-click on the file to copy. On the resulting menu, you click on COPY and then left-click twice on the folder into which you want the file copied.
    [Show full text]
  • CICS Transaction Server for OS/390 Installation Guide
    CICS® Transaction Server for OS/390® Installation Guide Release 3 GC33-1681-30 CICS® Transaction Server for OS/390® Installation Guide Release 3 GC33-1681-30 Note! Before using this information and the product it supports, be sure to read the general information under “Notices” on page xi. Third edition (June 1999) This edition applies to Release 3 of CICS Transaction Server for OS/390, program number 5655-147, and to all subsequent versions, releases, and modifications until otherwise indicated in new editions. Make sure you are using the correct edition for the level of the product. This edition replaces and makes obsolete the previous edition, SC33-1681-00. The technical changes for this edition are summarized under ″Summary of changes″ and are indicated by a vertical bar to the left of a change. Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address given below. At the back of this publication is a page entitled “Sending your comments to IBM”. If you want to make comments, but the methods described are not available to you, please address them to: IBM United Kingdom Laboratories, Information Development, Mail Point 095, Hursley Park, Winchester, Hampshire, England, SO21 2JN. When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 1989, 1999. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
    [Show full text]
  • CA Datacom CICS Services Best Practices Guide
    CA Datacom® CICS Services Best Practices Guide Version 14.02 This Documentation, which includes embedded help systems and electronically distributed materials (hereinafter referred to as the “Documentation”), is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA. Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT.
    [Show full text]
  • Enterprise PL/I for Z/OS V5.3 Compiler and Runtime Migration Guide Part 1
    Enterprise PL/I for z/OS Version 5 Release 3 Compiler and Run-Time Migration Guide IBM GC27-8930-02 Note Before using this information and the product it supports, be sure to read the general information under “Notices” on page 181. Third Edition (September 2019) This edition applies to Version 5 Release 3 of Enterprise PL/I for z/OS, 5655-PL5, and to any subsequent releases until otherwise indicated in new editions or technical newsletters. Make sure you are using the correct edition for the level of the product. Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address below. A form for readers' comments is provided at the back of this publication. If the form has been removed, address your comments to: IBM Corporation, Department H150/090 555 Bailey Ave San Jose, CA, 95141-1099 United States of America When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Because IBM® Enterprise PL/I for z/OS® supports the continuous delivery (CD) model and publications are updated to document the features delivered under the CD model, it is a good idea to check for updates once every three months. © Copyright International Business Machines Corporation 1999, 2019. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Tables.................................................................................................................. xi Figures............................................................................................................... xiii About this book....................................................................................................xv Using your documentation........................................................................................................................
    [Show full text]
  • CICS System Services
    CICS System Services Mainframe CICS System Services July 2021 Rate Description Rate FY22/FY23 Debit Code CICS zIIP $0.1780/CICS Unit 5 CICS zIIP $0.1780/CICS Unit 6 All OCIO rates can be found at: https://cio.nebraska.gov/financial/serv-rates.html General Overview Customer Information Control System or CICS System Services provide an interactive transaction-based processing environment to host business applications that are reliable, scalable, and secure. CICS features include: • Ability to process a high volume of transactions. • Ability to efficiently support event processing, dynamic scripting, web browser (HTML), and 3270 presentation of data. • Ability to access multiple types of data structures, such as relational databases, hierarchical databases (IMS), and VSAM data sets. • Ability to support other application features such as; report printing, document imaging, application help functionality, and other z/OS automation capabilities. Service Details The service includes: • 24/7 CICS application and business event hosting with traditional 3270 and web browser presentation. • z/OS Enterprise mainframe security and protection for CICS application software, application data, and user security. • 24/7 Service Desk support. This includes ‘incident troubleshooting’ for CICS application environments. • Complete CICS application data backup and recovery services. • Complete CICS application disaster recovery facilities and services provided. Office of the CIO/ Mainframe CICS System Services | Contact: CIO Service Desk: 402.471.4636 or 800.982.2468 1 CICS System Services • z/OS System automation available for unique CICS application mainframe requirements. • CICS automated services to coordinate application “On-line” and “Batch” processes. • Automated software to generate CICS maps. • Automated software to assist applications with reporting (style sheets).
    [Show full text]
  • Appendix A: Current Environment Overview the Following Subsections Provide an Overview of the Current Technical Environment
    1 Appendix A: Current Environment Overview The following subsections provide an overview of the current technical environment. N-FOCUS – Nebraska’s Legacy Integrated Health and Human Services and Benefits Application Nebraska Family Online Client User System (N-FOCUS) is an integrated system that automates benefit/service delivery and case management for more than 30 DHHS programs, including Aid to Dependent Children (ADC), Supplemental Nutrition Assistance Program (SNAP), Child Welfare and Medicaid. The system was initially developed in partnership with Accenture as the prime Systems Integrator. N-FOCUS functions include client/case intake, eligibility determination, case management, service authorization, benefit payments, claims processing and payments, provider contract management, interfacing with other private, state and federal organizations, and management and government reporting. N-FOCUS was implemented in production in mid-1996 and is operational statewide. The typical N-FOCUS user is a DHHS or contracted employee. N-FOCUS supports over 2500 workers, operating from offices around the State as well as from 4 customer service centers and a centralized scanning facility. Some cases are assigned to specific workers; however, the majority of cases are managed via a universal caseload methodology coordinated by the customer service centers. N-FOCUS has both batch and online components and stores data in Db2 and SQL Server. The Db2 database has over 650 tables, some with a corresponding archive table. There are over 785 relationships between tables, 1278 indexes, and over 9665 attributes. There are over 1.7 billion rows of production data with over 193 million rows in one table with an average table size of 3.2 million rows.
    [Show full text]
  • Basic of Mainframe
    Basic of Mainframe Mainframe computer Mainframe is a very large and expensive computer capable of supporting hundreds, or even thousands, of users simultaneously. In the hierarchy that starts with a simple microprocessor at the bottom and moves to supercomputers at the top, mainframes are just below supercomputers. In some ways, mainframes are more powerful than supercomputers because they support more simultaneous programs. But supercomputers can execute a single program faster than a mainframe. The distinction between small mainframes and minicomputers is vague, depending really on how the manufacturer wants to market its machines. Modern mainframe computers have abilities not so much defined by their single task computational speed (usually defined as MIPS ² Millions of Instructions Per Second) as by their redundant internal engineering and resulting high reliability and security, extensive input- output facilities, strict backward compatibility with older software, and high utilization rates to support massive throughput. These machines often run for years without interruption, with repairs and hardware upgrades taking place during normal operation. Software upgrades are only non-disruptive when Parallel Sysplex is in place, with true workload sharing, so one system can take over another's application, while it is being refreshed. More recently, there are several IBM mainframe installations that have delivered over a decade of continuous business service as of 2007, with hardware upgrades not interrupting service. Mainframes are defined by high availability, one of the main reasons for their longevity, because they are typically used in applications where downtime would be costly or catastrophic. The term Reliability, Availability and Serviceability (RAS) is a defining characteristic of mainframe computers.
    [Show full text]