ICL Technical Journal Volume 4 Issue 4

Total Page:16

File Type:pdf, Size:1020Kb

ICL Technical Journal Volume 4 Issue 4 TECHniCAl j o u R m i Volume 4 Issue 4 November 1985 iC L T C p u n ip p i The ICL Technical Journal is published twice a year by 1/¼ in n n i Peter Peregrinus Ltd. on behalf of International JOURrlnL Computers Ltd. Editor J. Howlett ICL House, Putney, London SW15 1SW, UK Editorial Board J. Howlett (Editor) CJ. Hughes H.M. Cropper (British Telecom Research Laboratories) D.W. Davies K.H. Macdonald G.E. Felton J.M. Pinkerton M.D. Godfrey E.C.P. Portman All correspondence and papers to be considered for publication should be addressed to the Editor. 1986 subscription rates: annual subscription £16.00 UK, £19.00 overseas, airmail supplement £8.00, single copy £10.00. Cheques should be made out to ‘Peter Peregrinus Ltd.’, and sent to Peter Peregrinus Ltd., Station House, Nightingale Road, Hitchin, Herts. SG5 ISA, UK, telephone: Hitchin (s.t.d. 0462) 53331. The views expressed in the papers are those of the authors and do not necessarily represent ICL policy. Publisher Peter Peregrinus Ltd. PO Box 8, Southgate House, Stevenage, Herts. SGI 1HQ, UK This publication is copyright under the Berne Convention and the Inter­ national Copyright Convention. All rights reserved. Apart from any copying under the UK Copyright Act 1956, part 1, section 7, whereby a single copy of an article may be supplied, under certain conditions, for the purposes of research or private study, by a library of a class prescribed by the UK Board of Trade Regulations (Statutory Instruments 1957, No. 868), no part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means without the prior permission of the copyright owners. Permission is, however, not required to copy abstracts of papers or articles on condition that a full reference to the source is shown. Multiple copying of the contents of the publication without permission is always illegal. ©1985 International Computers Ltd. Printed by A.McLay & Co. Ltd., London and Cardiff ISSN 0142-1557 JCL TCCHNCfll JOURnflL Contents Volume 4 Issue 4 Foreword Asa W. Lanum 351 History of the ICL content-addressable file store (CAFS) J.W.S. Carmichael 352 History of the CAFS relational software A.T.F. Hutt 358 The CAFS system today and tomorrow G.McC. Haworth 365 Development of the CAFS-ISP controller product for Series 29 and 39 systems N. Macphail 393 CAFS-ISP: issues for the application designer R.M. Tagg 402 Using secondary indexes for large CAFS databases P.R. Wiles 419 Creating an end-user CAFS service C.E.H. Corbin 441 Textmaster — a document-retrieval system using CAFS- ISP M.H. Kay 455 ICL Technical Journal November 1985 349 CAFS and text: the view from academia L. Burnard 468 Secrets of the sky: the IRAS data at Queen Mary College D. Walker 483 CAFS file-correlation unit E. Babb 489 Patents relating to the ICL content-addressable file store CAFS 504 Notes on the authors 506 Subject index to Volume 4 511 Author index to Volume 4 518 350 ICL Technical Journal November 1985 Foreword On the 21st April 1985 it was announced that the Queen’s Award for Technological Achievement had been presented to ICL in recognition of the successful innovation represented by the development of CAFS-ISP. The problem of accessing large amounts of data in a structured manner, so as to present usable information within a reasonable time, began to be recognised as early as 1962. The CAFS system is a combined hardware and software solution to this problem. Additionally, it is especially well positioned because throughout the development there has been a clear understanding that any technological breakthroughs achieved in solving the problem must fit into the real world of existing customer data and equipment. The CAFS-ISP product clearly represents a breakthrough worthy of the Queen’s Award, and as such is one of the unique technological advances in the data-processing industry today. As a vehicle it is just now being recognised by other organisations trying to provide comparable data-access capabilities. This issue of the ICL Technical Journal reviews the history of the development of CAFS from the first recognition and formalisation of the problem through to the evolution of the physical solution, and also the history of the supporting software. In addition it illustrates the use of the product in the real world, showing how this has extended from the original closely defined problem of data access to include the processing of text and other forms of information by real users to solve real problems. Asa W. Lanum Director and General Manager, ICL Applied Systems ICL Technical Journal November 1985 351 History of the ICL content-addressable file store (CAFS) J.W.S. Carmichael ICL Mainframe Systems, Slough, Berkshire Abstract The paper is a chronological review of the development of CAFS from an original notion through successive stages of research, development and integration to a standard ICL product. It is essentially the author's historical review included in the 1985 Report of the CAFS Group Working Party of the ICL Computer Users Association. 1 Introduction The origin of CAFS as a concept was the explicit recognition that the activities of a living organisation of co-operating people are not totally ordered, so that their interactions must be regarded as an interplay of order and disorder. The use of information to maintain their organised behaviour is therefore also characterised by an element of disorder, in its fundamental sense of intrinsic unpredictability, and so, whenever a large amount of data is stored on magnetic media, some applications will require that it be accessed by search. The traditional approach to solving this problem has been to build indexes to cope with the more predictable searches. This is fine as far as it goes, but not all searches can be predicted, and if one tries to build indexes to cope with every eventuality - by, in effect, totally inverting the file - the task of managing the indexes, particularly when the data is volatile, can become intolerable. Two very relevant quotations from Vic Mailer1 are: ‘There are, in fact, instances where the indexes can occupy between two and four times the volume occupied by the data to which they refer a perfectly absurd situation’. \ .. It should not be assumed that indexable operations cover the totality of useful functions ... Indexes are really very primitive projections of files and consequently their utility should not always be taken for granted’. Content addressing, or associative processing, is a natural way of trying to circumvent these difficulties. Very natural, in fact, since we are all very familiar with the marvellous effects we can achieve using these techniques in retrieval from the memories in our heads. Laymen have always assumed that 352 ICL Technical Journal November 1985 computers work this way; look at the computers in 2001, Doctor Who or Blake’s Seven to see how ordinary people think they behave. In the early 1960s there was much speculation in the academic world on the potential value of associative stores, but few suggestions regarding prac­ ticable techniques for making such a store of adequate capacity at acceptable cost. In 1962 Gordon Scarrott, working with Roy Mitchell in the Ferranti computer department, was stimulated by this situation to point out to their management that if a store, of adequate capacity to be useful, conceptually rotates as a consequence of its operating principle - for example a magnetic drum or a delay line - then the mean time required for access by search is half the revolution time, exactly the same as for access to a known address. Hence associative access can be achieved with existing technology, without an additional access time penalty. However, in 1962 the concept of a ‘data base’ had not become common and consequently the need for store access by automated search was not widely recognised. Moreover, there were no resources available for exploratory development, and so no physical work was initiated at the time. 2 Initial project In 1969 George Coulouris, then lecturer in computer science at Imperial College, suggested to Gordon Scarrott a joint project with ICL’s Research & Advanced Development Centre to identify the intrinsic requirements for file storage and to propose ways for meeting such requirements - a suggestion that was immediately accepted. The late Roy Mitchell, then a senior member of the staff of RADC, took responsibility for the project, collaborating with John Evans, one of George Coulouris’s senior students. At that time moving-head disc storage devices were not in common use. Nevertheless, in December 1969 Roy Mitchell had proposed a combination of disc store, key store and comparator, search evaluation unit and retrieval unit. He coined the term ‘CAFS’ to refer to the system, a name by which this combination of mechanisms is still known. Initially there was some confusion about whether the ‘A’ stood for ‘addressable’ or ‘addressed’, but this issue has long been resolved in favour of ‘addressable’ since the system permits addressing by content but does not enforce it. It is noteworthy that most of the individual events (i.e. comparisons) in the CAFS searching system take place as soon as the data becomes available from the disc store, so that Roy Mitchell’s design was in effect a ‘data flow’ system as now defined. But of course the term ‘data flow’ was not used in 1969. Since CAFS is an engineering innovation, its most basic feature, the autonomous searching mechanism, should be regarded as a novel and advantageous synthesis of ends and means. Gordon Scarrott and Roy Mitchell proposed the means in 1962, George Coulouris and John Evans ICL Technical Journal November 1985 353 recognised the ends in 1969, and Roy Mitchell proposed the synthesis in 1969.
Recommended publications
  • IDMS Conversion
    IDMS Conversion The Modern Systems IDMS conversion includes the generation of a new relational database to replace the functionality, set relationships, indexes, and data structures that are currently part of the IDMS network database. The new target database can reside on or off the mainframe, and can use any of the standard relational database management systems (RDBMS): Microsoft SQL Server, Oracle or IBM DB2. Database Functionality DB-Shuttle™ provides The Modern Systems solution provides a complete replacement for all IDMS automated technology database functionality: that protects legacy assets, reduces • IDMS record layouts maintenance costs, • Group-level elements, Occurs and Redefines clauses within IDMS record provides agility and definitions flexibility, and enables • Set definitions (record-to-record relationships) Service-Oriented • System-owned indexes Architecture (SOA) • Bill-of-material structures within business-critical • Multi-member sets, multi-set relationships between two record types applications. • Duplicate CALC designations • Sorted sets, Chained sets and NEXT sets Relational Results The resulting database is fully relational. Primary keys, foreign keys and index definitions are automatically created. All constraints are generated into the resulting DDL. Table spaces, indexes, table names and column names are all generated according to your naming standards. Delivered Components As part of the delivery process, Modern Systems generates and delivers the following component types for installation in the new relational
    [Show full text]
  • Miami-Dade County
    MIAMI-DADE COUNTY Cognos Business Analytics and IDMS Integration at Miami-Dade County Abstract of the Program Miami-Dade County led the way as the first company in the world to successfully extract information from a CA IDMS network database using IBM Cognos Business Analytics. Miami- Dade County stores the majority of their critical data, such as Criminal Justice, Payroll, Traffic and Building information in CA IDMS mainframe databases and traditionally extracts this data using Computer Associates CA IDMS tools (CA ADS ADS/O and IDMS/Cobol/IDMS). Through the collaboration of CA Computer Associates, IBM, and Miami-Dade County, a driver was created for IBM Cognos to access this data directly by using Business Analytics tools without the need for exporting the data into a contemporary distributed environment. The problem or need for the program IDMS (Integrated Database Management System) is primarily a network (CODASYL) database management system for mainframes. Only CA tools could access IDMS data. IDMS mainframe technology did not have the capability to be accessed directly by contemporary business analytics software solutions. This limitation required data extraction, file transfer protocols, and script loading processes to expose IDMS, IMS, and DB2 mainframe data to contemporary technologies, including business analytics tools like IBM Cognos Analytics. Multiple data warehouses and operational data stores are loaded from the primary data sources originating from the IDMS mainframe platform and other relational data sources. More than 50 production IDMS databases are actively supported and used county-wide at Miami- Dade County. Access to data by the distributed world such as making the data available on an Oracle or MSSQL database requires adding multiple intermediate steps, using multiple technologies, and multiple points of failure to migrate data and make it available to analytic technologies.
    [Show full text]
  • CASE STUDY GE CAPITAL ASSESSING, CONVERTING, & REPLATFORMING a MASSIVE BUSINESS CRITICAL APPLICATION with ASTONISHING RESULTS Introduction
    CASE STUDY GE CAPITAL ASSESSING, CONVERTING, & REPLATFORMING A MASSIVE BUSINESS CRITICAL APPLICATION WITH ASTONISHING RESULTS Introduction GE Capital is the financial services unit of the American conglomerate General Electric, it provides commercial lending and leasing, as well as a range of financial services for consumers. Most of GE Capital’s commercial loans are to small and midsized companies, spread across multiple industries and geographies, and secured by tangible assets. GE Capital’s consumer lending activities are also diversified by product and geography and include operations in 55 countries. Project Summary GE Capital was looking to move their PMS suite of $ 2014 Net Income: $7.0 billion applications from ADS/O and COBOL/IDMS running 2014 Assets: $499 billion on a mainframe, to COBOL running with Oracle on Unix without changing the user interface in the Operations in 40+ Countries process. PMS was built by GE Capital in 1987 500,000+ Commercial Customers and began its life as a 20,000 account schedule system without any interfaces. 35,000+ Employees As with most homegrown systems, it was built out of necessity and to serve the business as it existed at the time. Over the decades, this small system grew in size and complexity to become the central nervous system of both GE Capital’s direct and indirect business units comprised of four highly customized implementations. With over 5 million account schedules, 382 interfaces, 1,700 concurrent users, and 3.5 million transactions per day running against 71 million lines of code, the PMS system had come a long way from its humble roots.
    [Show full text]
  • DATABASE SYSTEMS: a BRIEF TIMELINE Event Consequence Pre-1960S 1945 Magnetic Tapes Developed (The First Medium Replaced Punch Cards and Paper Tape
    DATABASE SYSTEMS: A BRIEF TIMELINE Event Consequence Pre-1960s 1945 Magnetic tapes developed (the first medium Replaced punch cards and paper tape. to allow searching). 1957 First commercial computer installed. 1959 McGee proposed the notion of generalized access to electronically stored data. 1959 IBM introduced the Ramac system. Read data in a non-sequential manner, and access to files became feasible. The '60s 1961 The first generalized DBMS-GE'S Integrated Formed the basis for Network Data Model Data Store (IDS)-designed by Bachman; developed by Conference on Data Systems wide distribution by 1964. Bachman Languages Database Task Group (CODASYL popularized data structure diagrams. DBTG). 1965- · Generalized file management systems Provided two-level conceptual/user view 1970 developed by numerous vendors. organization of data. · Information Management System (IMS) developed by IBM. Formed the basis for Hierarchical Data Model. · IMS DB/DC (database/data communication) System was the first Supported network views on top of the large-scale DB/DC system. hierarchies. · SABRE, developed by IBM and American Airlines. Allowed multiple-user access to data involving a communication network. The '70s Database technology experienced rapid Commercial systems followed CODASYL growth. DBTG Proposal, but none fully implemented it. IDMS system by B. F. Goodrich, Honeywell's IDS II, UNIVACs DMS 1100, Burroughs's DMS-II, CDCs DMS-170, Phillips's PHOLAS, and Digital's DBMS-11. Several integrated DB/DC systems: Cincom’s TOTAL plus ENVIRON/l. DBMS developed as an academic discipline and a research area. 1970 The relational model is developed by Ted Laid foundation for database theory. Codd, an IBM research fellow.
    [Show full text]
  • CA IDMS Best Practices Guide
    CA IDMS™ Best Practices Guide Version 18.0.00 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]
  • Tcvision IBM Mainframe Integration Through Change Data Capture Fact Sheet
    tcVISION IBM Mainframe Integration Through Change Data Capture Fact Sheet Mainframe data integration has taken on more urgency in recent years The tcVISION Solution as organizations seek to relocate mainframe workloads to lower-cost tcVISION is ready to meet new technologies and challenges. Thanks to platforms, modernize mainframe applications and leverage analytics for tcVISION’s flexible architecture, support for new targets—including AWS, customer insight and competitive advantage. These factors are driving specialty, NoSQL and analytic databases such as Exasol, IBM DB2 BLU adoption of Cloud (e.g., Amazon Web Services [AWS]) and Big Data as and MongoDB—, transport layers and protocols is being continuously strategic components in corporate technology architecture. added, quickly and with minimal effort. With tcVISION, real-time Cloud and Big Data integration can embrace both mainframe (IBM DB2, IMS/ tcVISION’s support for Cloud and Big Data as targets is fully integrated DB, DL/1, Software AG Adabas, CA IDMS, CA Datacom and alongside traditional Linux/Unix/Windows (LUW) targets such as Oracle VSAM), Cloud, and LUW (IBM DB2 LUW, Oracle, IBM Informix, Database, IBM DB2 LUW, Software AG Adabas LUW, IBM Informix, Sybase, Microsoft SQL Server, PostgreSQL, Software AG Adabas Sybase, Microsoft SQL Server, PostgreSQL and ODBC. LUW) sources. tcVISION can deliver replicated data to Cloud and Big Data targets Why tcVISION? through a variety of means: creating files, writing directly into Hadoop • Increasing number of enterprise applications that utilize their own HDFS, and via streaming using Apache Kafka as the transport layer. Data databases. can be packaged using standard JSON and CSV protocols. • Requirement for up-to-date information demands real-time, bi- directional data synchronization between mainframe and open systems.
    [Show full text]
  • IDMS File Access Guide
    IDMS File Access Guide Release 8.1.3 November 2013 IKAN Solutions N.V. Kardinaal Mercierplein 2 B-2800 Mechelen BELGIUM Copyright © 2013, IKAN Solutions N.V. No part of this document may be reproduced or transmitted in any form or by any means, electronically or mechanically, for any purpose, without the express written permission of IKAN Solutions N.V. MetaSuite, MetaStore Manager, MetaMap Manager and Generator Manager are trademarks of IKAN Solutions N.V. IDMS is a trademark of Computer Associates (CA Inc). Table of Contents Chapter 1 - About This Manual........................................................................... 1 1.1. Prerequisites ...........................................................................................................................................................1 1.2. Related Publications ...............................................................................................................................................1 Chapter 2 - MetaSuite File Access Overview...................................................... 3 Chapter 3 - CA-IDMS Concepts and Terminology .............................................. 4 3.1. Overview.................................................................................................................................................................4 3.2. CA-IDMS data structures........................................................................................................................................4 3.3. Records...................................................................................................................................................................4
    [Show full text]
  • CA-IDMS 15.0 Data Sharing Feature Allows Multiple Update Cvs
    CA-IDMS 15.0 Data Sharing Feature Allows Multiple Update CVs by Judith Kruntorad CA-IDMS 15.0 offers significant scalability and Members of a Data Sharing Group can share update access availability enhancements to CA-IDMS clients. Through to an area provided that: exploitation of Coupling Facility structures in a Parallel • Data Sharing is enabled for the area Sysplex environment, CA-IDMS Central Versions are now • Associated files for the area are assigned to shared cache able to share update access to the same database areas. • Attributes for the area and associated files are identical Additional features are also provided for improved 24 x 7 in all systems functionality, improved performance and productivity, and enhanced SQL Internally, each participating CV must now functionality. perform global transaction and page locking as well as global deadlock detection and resolution A Data Sharing Group (DSG) is a new for shared areas whenever a contention occurs. concept introduced with CA-IDMS 15.0. This is managed through the use of Coupling There is no syntax required to define a Data Facility structures. A cache structure must be Sharing Group. Rather a Data Sharing Group defined for the buffers for the shared files and comes into existence when two or more CVs a list and a lock structure must be defined for are started with identical values for the new use with global locking. XCF group services SYSIDMS parm of DSGROUP=group-name. Members and signaling services are used by CA-IDMS for sending of a Data Sharing Group enjoy many privileges including and receiving messages and monitoring Data Sharing the ability to share update access to areas, share access to Member status.
    [Show full text]
  • The Business Value of DB2 UDB for Z/OS
    Front cover The Business Value of DB2 UDB for z/OS Learn about the synergy of DB2 with IBM Eserver zSeries and z/OS Discover how you can benefit from the richness in function Be ready for On Demand Business Paolo Bruni Paul Bartak Rick Butler Sreeni Janaki John Pashley ibm.com/redbooks International Technical Support Organization The Business Value of DB2 UDB for z/OS June 2005 SG24-6763-00 Note: Before using this information and the product it supports, read the information in “Notices” on page ix. First Edition (June 2005) This edition applies to IBM DB2 Universal Database for z/OS Version 8 (program number 5625-DB2). © Copyright International Business Machines Corporation 2005. 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 . ix Trademarks . x Preface . xi The team that wrote this redbook. xii Become a published author . xiv Comments welcome. xiv Chapter 1. Evolution of the mainframe . 1 1.1 The evolution of z/Architecture . 2 1.1.1 Lower cost of entry to mainframes . 2 1.1.2 More options in pricing and performance . 2 1.1.3 Leveraging investment in existing applications . 3 1.2 Hardware. 4 1.3 Operating systems . 10 1.3.1 Value of z/OS . 10 1.3.2 Evolution of z/OS . 16 1.3.3 Other mainframe operating systems . 17 1.4 Processor . 18 1.5 Management . 19 1.6 Preparing new mainframers . 20 1.7 2000 through 2005: The era of on demand.
    [Show full text]
  • Treat Your CA IDMS™ and CA Datacom® Developers to Eclipse-Based Development
    MAINFRAME Treat Your CA IDMS™ and CA Datacom® Developers to Eclipse-Based Development David Ross Sr Principal Product Owner CA Technologies MFX137E For Informational Purposes Only Terms of This Presentation © 2017 CA. All rights reserved. All trademarks referenced herein belong to their respective companies. The presentation provided at CA World 2017 is intended for information purposes only and does not form any type of warranty. Some of the specific slides with customer references relate to customer's specific use and experience of CA products and solutions so actual results may vary. Certain information in this presentation may outline CA’s general product direction. This presentation shall not serve to (i) affect the rights and/or obligations of CA or its licensees under any existing or future license agreement or services agreement relating to any CA software product; or (ii) amend any product documentation or specifications for any CA software product. This presentation is based on current information and resource allocations as of November 1, 2017, and is subject to change or withdrawal by CA at any time without notice. The development, release and timing of any features or functionality described in this presentation remain at CA’s sole discretion. Notwithstanding anything in this presentation to the contrary, upon the general availability of any future CA product release referenced in this presentation, CA may make such release available to new licensees in the form of a regularly scheduled major product release. Such release may be made available to licensees of the product who are active subscribers to CA maintenance and support, on a when and if-available basis.
    [Show full text]
  • CA IDMS Product Brief
    Product Brief CA IDMS™ At a Glance Key Features CA IDMS™ is a cost-effective, reliable, highly-performant, and secure database management system for IBM Z that delivers outstanding business • Zowe Conformant REST API. value for hundreds of enterprises and government organizations around Flexibility to leverage modern the world. A powerful database engine providing network and relational tooling to address the skills access exploiting the latest hardware and software technologies including challenge and automate systems the IBM z Systems Integrated Information Processor (zIIP). management minimizing risk of system outages. Business Challenges • Zowe command line interface. Enabled use of modern scripting Data is a business’ most valuable asset fueling new apps and services languages. that differentiate it in the market. Because mission critical data lives on the mainframe, corporate database systems must be highly scalable to • Zowe CLI Plug-in. Enables users to interact with the mainframe in a handle ever-increasing business demands. These systems must be open familiar format. and extensible to support existing applications, and enable modern digital transformations without requiring costly rewrites and conversions. • Standard SQL. Query and update existing legacy databases without Companies need a reliable database repository with enterprise-wide, migration or conversion while high-volume workload and fault-tolerant capabilities. They also need preserving existing apps. transformation techniques designed to improve performance, scalability, • ODBC and JDBC drivers. Access platform support, standards compliance, and usability, while simultaneously data and reuse legacy application reducing costs. code through IDMS Server APIs. Without a unified way to get ahead of nonstop demands for data, your • MQ adapter. Interface for CA IDMS organization could continue to experience the following challenges: applications to send and receive messages that can be zIIP enabled.
    [Show full text]
  • Spring 2005 ISSN 1741-4229
    IIRRMMAA INFORMATION RISK MANAGEMENT & AUDIT JOURNAL ◆ SPECIALIST ROUP OF THE ◆ JOURNAL A G BCS volume 15 number 1 spring 2005 ISSN 1741-4229 Programme for members’ meetings 2004 – 2005 Tuesday 7 September 2004 Computer Audit Basics 2: Auditing 16:00 for 16:30 Late afternoon the Infrastructure and Operations KPMG Thursday 7 October 2004 Regulatory issues affecting IT in the 10:00 to 16:00 Full day Financial Industry Old Sessions House Tuesday 16 November 2004 Networks Attacks – quantifying and 10:00 to 16:00 Full day dealing with future threats Chartered Accountants Hall Tuesday 18 January 2005 Database Security 16:00 for 16:30 Late afternoon BCS Tuesday 15 March 2005 IT Governance 10:00 to 16:00 Full day BCS – The Davidson Building, 5 Southampton Street, London WC2 7HA Tuesday 17 May 2005 Computer Audit Basics 3: CAATS 16:00 for 16:30 Late afternoon Preceded by IRMA AGM BCS – The Davidson Building, 5 Southampton Street, London WC2 7HA AGM precedes the meeting Please note that these are provisional details and are subject to change. The late afternoon meetings are free of charge to members. For full day briefings a modest, very competitive charge is made to cover both lunch and a full printed delegate’s pack. For venue map see back cover. Contents of the Journal Technical Briefings Front Cover Editorial John Mitchell 3 Chairman’s Corner Alex Brewer 5 The Down Under Column Bob Ashton 6 Statistical Risk Cluster Analysis for Network Segmentation Vasilios Katos 7 Preparing for Freedom of Information in the UK Jack Vivrett 12 IRMA Presentation, 17 May 2005 – Computer Audit Basics 3 16 BCS Matters Colin Thompson 17 Members’ Benefits 20 Membership Application 21 Management Committee 23 Advertising in the Journal 24 IRMA Venues Map 24 GUIDELINES FOR POTENTIAL AUTHORS The Journal publishes various types of article.
    [Show full text]